#devuan

01:46:27 <Nrml> Coming back to report on my installation of Devuan Daedalus Preview 20221128, as promised.

01:47:02 <Nrml> I just installed it in a KVM VPS I purchased from Contabo during Black Friday promo

01:48:23 <Nrml> gnarface: yep, with just one issue I would like to report

01:48:56 <Nrml> The issue happened at the "Configure the package manager" step

01:50:41 <Nrml> Here's the error screen, after accepting the default options: https://i.imgur.com/1Oucqzx.png

01:52:07 <Nrml> And here's how /etc/apt/sources.list ended up after the install: https://i.imgur.com/1qK6TOb.png

01:52:39 <Nrml> Apart from that, the install was completely smooth

01:53:26 <Nrml> Machine rebooted with the openssh-server I opted to install, logged in using the account I created, all perfect

01:53:59 <Nrml> And curiously enough, `apt-get install` is working, just installed a package (despite the mess in /etc/apt/sources.list as depicted above)

01:54:41 <Nrml> So I will be moving ahead with this install. Just would like to hear about the issue I reported.

01:55:00 <Nrml> Should I worry? Is there anything I should do to my /etc/apt/sources.list?

01:59:05 <rrq> daedalus doesn't get a security side-repsitory until the release, so it's all fine like that

02:00:02 <Nrml> rrq: I tried uncommenting the commented-out lines and then ran `apt-get update`, got the following error:

02:00:05 <Nrml> E: The repository 'http://deb.devuan.org/merged daedalus-security Release' does not have a Release file.

02:00:08 <Nrml> N: Updating from such a repository can't be done securely, and is therefore disabled by default.

02:00:26 <Nrml> rrq: so this is expected and should self-cure after Daedalus is released?

02:01:02 <rrq> correct. well, you'll have to then edit your sources.list yourself of course.

02:04:18 <Nrml> rrq: I can keep the lines uncommented (as `apt-get update` seems to be updating the main repo) and just wait for Daedalus to be released and the security repo to be created, right?

02:04:45 <Nrml> I mean, the security repo will be created with the same URL etc that's already there

02:05:14 <rrq> I think they need to be commented for updating your local meta data..

02:06:17 <Nrml> because things seem to be working perfectly, both `apt-get update` (except for the security repo) and `apt-get install` is working with no issues

02:08:38 <gnarface> all that'll happen bad is you're gonna get errors whenever you try to update the package cache, but i think it should still work

02:08:57 <gnarface> personally i'd leave them commented until the official release just because i don't like errors but they probably won't hurt anything

02:09:25 <gnarface> if you're scripting something it might be a complication because the process won't exit 0 but if you're not updating it much you probably won't notice

02:09:41 <Nrml> Thanks gnarface and rrq for the help, and all the Devuan community for another job exceedingly well done. May Devuan live long and true!

02:10:18 <onefang> Commenting out so you don't see the errors is good, then you're more likely to spot any real errors.

02:13:13 <Nrml> onefang: thanks for the tip, will keep it in mind -- but I would rather see the errors as a reminder that I'm still missing security updates, than to silence it and eventually forget it all ;-)

09:58:37 <onefang> That MIDI keyboard / drum pads / controllers is all cleaned up, put back together, and working fine. Now I gotta sort out the software. Seems most needs jack, and I only had alsa. I'm gonna need to get jack behaving. Hydrogen is working fine for the drums, Piano Booster for the keyboard.

10:28:42 <gnarface> i've heard from other sources that most the serious audio studio stuff does rely on jack

18:04:41 <rwp> Most of the mirrors are impossible to mirror using https because the names will never match.

18:04:52 <rwp> The security of the system was designed without requiring https.

18:05:38 <rwp> Yes. SHA hashes that are GPG signed by the keyring.

18:06:33 <rwp> deb.devuan.org is a round-robin list of other file server systems. They all have names that are different.

18:07:13 <onefang> But you can access them directly via their own name using HTTPS.

18:07:36 <rwp> Check out the mirror list at https://www.devuan.org/get-devuan

18:07:54 <talismanick> Well, if it's good enough for Debian too...

18:09:25 <rwp> talismanick, Are you installing a new system or upgrading an existing system?

18:09:37 <onefang> It's summer and I just turned the heater on. "Good" is relative. lol

18:10:23 <rwp> onefang, You need to be in offtopic so I can comment that it was -15C here this morning.

18:10:57 <rwp> talismanick, If you are installing a fresh system then you should use an https mirror to download the install image.

18:11:29 <rwp> If you are upgrading then using an http://deb.devuan.org round-robin mirror is best. It's secure due to the keyring.

18:11:59 <rwp> Using https for deb repositories has several subtle problems. Like the system clock must be set. That snags Raspberry Pi users quite often.

18:14:13 <rwp> When we talk about "repos" that name is most often for the package database at deb.devuan.org and not the install images from the other mirror sites.

18:20:19 <onefang> We got package mirrors, which is what we call repos, and listed at https://pkgmaster.devuan.org/mirror_list.txt. This is used for apt sources.list. Then we have the ISO / filo mirrors, for the install images, listod at https://www.devuan.org/get-devuan.

18:20:43 <onefang> deb.devuan.org is a round robin DNS for the former.

18:27:16 <golinux> talismanick: Have you seen the migration instructions here https://www.devuan.org/os/install ?

18:36:27 <talismanick> speaking of which, what do I do differently from the Bullseye->Chimaera update guide for runit?

18:39:08 <talismanick> aside from changing sysvinit-core to runit-init (right?)

18:39:58 <rwp> I have *installed* selecting runit but I haven't *converted* a system to runit. But I think you just need to apt-get install the desired runit* packages and then reboot. But don't trust me on that since I haven't done it.

18:41:38 <talismanick> rwp: `apt -f install` is what changes out the init regardless, right?

18:42:12 <rwp> Not that specific command. That's to resolve and repair a broken package dependency.