libera/#devuan/ Friday, 2024-01-19

blizzowI have something a little weird going on in my fresh daedalus install on a thinkpad X1 Extreme 5th Gen. The USB-C ports don't work.02:10
blizzowThey used to work in poopOS but seem to have stopped. I can't find any switch on the machine to enable or disable the USB-C ports. I haven't changed BIOS.02:11
blizzowI see nothing in dmesg.02:11
rrqwhat does "USB-C ports don't work" mean?02:14
ham5urgI did an testing upgrade an fall into the same trap as many others.02:18
ham5urgWhen I do a '/usr/lib/usrmerge/convert-usrmerge', I get an error like02:18
ham5urgBoth /lib/udev/rules.d/60-libsane1.rules and /usr/lib/udev/rules.d/60-libsane1.rules exist.02:18
ham5urgIndeed, both directories have many identical files.02:19
ham5urgHow to process from here on?02:19
gnarfaceblizzow: you sure it's not just a permissions issue? how'd you test?02:20
blizzowgnarface, I have both usb a and c ports on the laptop. the a ports work fine.02:26
blizzowThe c ports, not so much.02:26
ham5urgShould I remove all links from /lib/udev/rules.d/ ?02:26
ham5urgAnd rerun /usr/lib/usrmerge/convert-usrmerge ?02:27
ham5urgWhat a mess02:27
gnarfaceham5urg: stick around, i'm sure someone has advice02:28
ham5urgYes, I won't reboot soon :D02:29
ham5urgDid an 'apt dist-upgrade' before knew about convert-usrmerge02:29
gnarfaceblizzow: that didn't tell me how you tested it02:29
u-amarsh04I check the dates of the files concerned02:30
blizzowI plugged a device (usb hd) into the c ports and it didn't work. I grabbed a different cable and plugged it into the a ports and it worked.02:30
blizzowI grabbed an adapter/dock and plugged it into the c ports and did get this:02:31
blizzow[ 6341.399472] ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-95)02:31
blizzowThe only thing I found was a message to a kernel mailing list saying a reboot while the usbc was plugged in seems to have it show up. I did not try that yet.02:32
blizzowThe other solution I saw was to use a different kernel.02:32
gnarfaceblizzow: kernel or modules difference is all i can think of too02:33
gnarfaceblizzow: looks like kernel 6.5 is in daedalus-backports, maybe try that02:34
blizzowI might give that a shot. Or just wait out ceres until the usrmerge issues are fixed.02:34
rwpham5urg, I don't know anything about /usr/lib/usrmerge/convert-usrmerge but AFAIK those identical files are now declared to be accidentally forked and if they truly are identical then remove the /lib one.02:34
rwpThe plan would be to repeat that process until /lib and /bin are both completely empty.  Then symlink them to the /usr versions.02:35
rwpCaution for the main commands cp, mv, ln that you don't break them while the movement is in progress because of shared libraries.  Use ldd $(command -v ln) to see what I am talking about.  Those libs are in /lib and if they disappear then the command stops working.02:37
ham5urgEasier to make a fresh install, isn't it?02:38
rwpNote that klibc-utils with /usr/lib/klibc/bin/* includes most of the basic commands statically linked or use in initramfs images and that can be a good rescue if that bad case happens.02:38
u-amarsh04I had to use an Devuan live image on DVD to mount the hard disk and move files on the boot hard disk's /lib02:38
rwpAFAIK there is no installer for Unstable/Testing and one usually installs Stable and then upgrades.  But UsrMerge makes that a problem.02:39
u-amarsh04my older pc has been migrated and upgraded from a Debian install in June 2004, never re-installed since then02:39
ham5urgu-amarsh04, did you documented your process?02:39
ham5urgwau since 200402:39
rwpAlso there have been reports of Desktops Environments being broken on Testing due to UsrMerge right now too.02:39
u-amarsh04ham5urg, not on the /lib side, but on dev1galaxy.org under hardware and system configuration02:40
rwpu-amarsh04 is the one who gave me the hint that /usr/lib/klibc/bin/* static binaries were available.  That was a good hint!02:40
u-amarsh04be careful that the /usr/lib/klibc/bin/* binaries are more limited than the usual versions02:41
ham5urgu-amarsh04, this https://dev1galaxy.org/viewtopic.php?id=6290 ?02:41
rwpI think they previously used BusyBox but I guess they don't anymore.02:41
u-amarsh04ham5urg, yes02:42
rwpEven after UsrMerge migration I would expect various breakage because for example cpio moved binaries from /bin to /usr/bin which is okay but then forgot to update the postinst and prerm scripts dealing with update-alternatives and are still using the old locations.02:43
u-amarsh04I stated in the thread mentioned above that package acl appeared to do the right thing as far as having symbolic links created02:44
ham5urgOh man, as I'm reading a question arises. Will this be the end for Devuan as a whole?02:45
onefangThat'll be "not a support question", best take it to #devuan-offtopic02:46
u-amarsh04I wish that the Debian people who decided on usrmerge tested everything themselves and documented a proper process for packages maintainers to avoid breakage02:46
golinuxham5urg: I am going to wait until the dust settles before getting off of chimaera. It is the transitional period that is so fragile.03:12
fluffywolfI've done two daedalus upgrades.  neither went well, and tons of things ended up broken.  lots of anti-features in new packages, too.03:24
fluffywolfbookworm wasn't ready for release imho.03:24
debdogmy experience was: fresh installs work. some ubgrades went _really_ terribly.03:25
fluffywolfdaedalus is by far the worst debian/devuan upgrade experience I've had, and I've been using debian since...  bo?  I don't even remember now.03:28
fluffywolfit was on my new shiny 486/33 with 4mb ram...03:28
Xenguygolinux, Yeah, give me the trailing edge, or give me death03:33
XenguyThe future with its usrmerge/systemd BS is just depressing03:33
fluffywolfI upgraded a 16 year old debian install through to chimaera, through every release, with no real issues...  but chimaera to daedalus fucking sucks.03:34
XenguyThis June or so I'll be forced to upgrade to Chimaera03:34
XenguyWhich is fine, except for wicd03:35
fluffywolfupgrading to chimarea is pretty smooth, if I remember correctly.03:35
fluffywolfwicd still works on chimaera.03:35
XenguyUmmm, hrm03:35
fluffywolfit and everything it depends on has been removed from repos, but if installed it keeps working fine.03:36
XenguySheesh, looks like you're right, thank you03:36
Xenguyhttps://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=wicd&x=submit03:36
XenguyWhy did I think that wicd disappeared after Beowulf ?03:37
XenguyThat's great news for me, if so03:38
fluffywolfhrmm, I thought it had been removed from the chimaera repos, but apparently I'm wrong.  I know it's gone in daedalus.03:39
XenguyYep03:39
fluffywolfpython is really harmful to the linux ecosystem, imho.03:39
u-amarsh04when upgrading some really old installation (pre-Devuan days) I found that I had to search for packages that had been removed but not purged and had files left behind: doing a search in aptitude for ~c found them03:39
Xenguywicd is a good example of that perhaps03:40
XenguySoftware that has no staying power03:40
u-amarsh04perl upgrades can be "fun" also waiting for all the packages that are installed to catch up03:40
XenguyGood ol' perl03:41
XenguyThose were the days03:41
fluffywolfu-amarsh04:  but they keep working.  unlike python, where they change the language and abi with every fucking single minor interpreter version bump, often in ways that prevent older software from continuing to work.03:41
fluffywolfyour software works with 3.7?  too bad it won't run on 3.11!  haha!  fuck you!03:41
XenguyThe disregard for backward compatibility seems cavalier, but there may be details I don't understand03:42
fluffywolfyou shouldn't be using older software.  get with the program.03:42
fluffywolfwe tell you what software you should be using.03:43
XenguyRight, the new software that no longer exists because...03:43
XenguyLather, rinse, repeat03:43
fluffywolfpoettering would fit in great with the python devs.03:43
Xenguy^^ How Rome must have felt when the 'barbarians' arrived...03:44
fluffywolfdebian packages usually depend on exact python interpreter versions, and of course you can't install multiple versions at once...03:45
fluffywolfPackage: borgbackup   Depends: python3-pkg-resources, python3 (<< 3.12), python3 (>= 3.11~)03:46
fluffywolf>11 and <12.03:46
fluffywolfheh03:46
XenguyWeird03:46
fluffywolfpython causes 90% of packaging-related issues every time I upgrade anything, despite being used for such a small portion of software.03:46
fluffywolfnothing weird about it...  it won't work with 3.10 or 3.12.  heh.03:47
fluffywolfbecause python fucking breaks everything even with minor version bumps03:47
fluffywolfin both directions.  never forwards or backwards compatible.03:47
golinuxXenguy: No wicd in chimaera . . . :(03:59
golinuxYou can thank python304:00
XenguyThat's what I thought golinux , but pkginfo reports otherwise, so not sure anymore04:00
golinuxThat OK because I don't have wifi. It just connects. fsr helped me set it uplike that.04:02
rrqXenguy: afaict "wicd" in daedalus is a dummy package that pulls in some of the other guis to replace it04:23
Xenguyrrq, pkginfo lists wicd in chimaera, which surprised me, as I thought beowulf was the last of wicd04:25
rrqyes, there exists a "wicd" package, but it does not bring the old wicd software; it merely makes a dependency to bring in04:26
rrqnetwork-manager-gnome or network-manager or connman-gtk or cmst or cunnman-ui as substitute04:26
golinuxI'd forgotten about that . . .04:27
* rrq thinks it's like asking for potatoes and get cabbage04:28
DelTomixthe cabbages they are on cabgmaster.devuan.org? :-)04:32
al1r4dwicd.. ah old one =))04:32
Xenguyrrq, Aha, things are starting to make sense now, thank you04:40
XenguyFor clarifying04:40
XenguyDid you hear that fluffywolf ?04:41
rwpSpeaking of upgrades...  Is anyone successfully running irssi on Daedalus?  It starts, starts to connect, but never actually successfully connects.  irssi is a casualty of Daedalus for me.05:24
rwpThe last thing irssi reports is "[Libera] Waiting for CAP LS response..." which leads me to wonder if the problem is in the connection.  But it works on Chimaera okay.05:25
rwpI should build up a chimaera chroot so I can run the chimaera version on the exact same machine and verify that the only difference is chimaera-daedalus.05:26
brocashelmnot sure, but i've been able to get weechat to work05:29
brocashelmi would then install the chimaera version and block the daedalus version if that's the case, or do a source installation from upstream05:31
rwpI am debootstrap'ing a chimaera chroot on the laptop and will give that a test.05:49
rwpI installed chimaera into a chroot, installed irssi, copied my ~/.irssi directory into it, and everything worked perfectly.  A-B testing shows it works on Chimaera and (for me anyway) fails on Daedalus.05:58
rwpI guess I do now have a way to run this, in the chroot.  Like I am doing typing this right now.05:59
rwpI guess the next thing is to see if the chimaera package installs on daedalus and try just the version change.05:59
rrqrwp: I run irssi on daedalus, but with a znc proxy that goes to libera06:00
rwpI guess I should also try it on a Debian Bookworm equivalent system and see if it fails there too.06:00
rrqwith=via06:00
rwpI am usually (like now on my old laptop) running emacs-erc through znc through irssi so I could try that connection too.06:01
rrqmy daedalus is an upgrade from chimaera06:02
rwpMy Daedalus laptop is a pristine installation.06:03
rwpI'll make a copy of the chimaera chroot and upgrade it to daedalus and see if irssi continues to work or not.06:03
rwpMy working chimaera upgraded to daedalus stops working.06:30
rwpI had exactly the same result in upstream Debian for Bullseye (irssi working) and Bookworm (irssi not working).07:39
grayrider1QUESTION:  ANYONE KNOW THE PASSWORDS FOR THE "TRIAL" RASPBERRY PI IMAGES?07:55
al1r4droot:toor(?)08:14
grayrider1root toor doesn't work; devuan devuan not; pi raspberry not; blah blah08:29
grayrider1tried blank pwds, too ... no go08:29
cousin_luigi^grayrider1: Are you connecting via ssh?10:24
grmlWith the current daedalus netinstall iso I get prompted for a missing regulatory.db. How do I get it? I have ethernet connected during install.11:35
rktagrml was me, question remains.12:18
cousin_luigirkta: wireless-regdb ?12:26
rktacousin_luigi: The prompt mentions 'regulatory.db'12:27
cousin_luigirkta: What prompt?12:28
rktaWhen installing, during configuring of the network, I get a prompt about that file missing.12:29
cousin_luigioh, uhmm12:30
cousin_luigiPossibly not supplied by the iso or not installed in the correct order. Can you skip it?12:31
cousin_luigi(since you use wired, but perhaps this is a bug worth reporting)12:31
rktaI aborted the install and fixed my system in the mean time. Yes, was thinking about a bug.12:32
onefangplatform regulatory.0: firmware: failed to load regulatory.db (-2)12:33
onefangplatform regulatory.0: Direct firmware load for regulatory.db failed with error -212:33
onefangcfg80211: failed to load regulatory.db12:33
onefangThat sort of "prompt"?12:34
rktaNo, in the TUI, I get a prompt, with buttons to abort and continue, about that missing file with the option to load it from some media.12:35
onefangI get that every time I boot.  I think that's the "This is what the WiFi laws in your country allow".  WiFi works fine anyway.12:35
rktaI'm talking about the installer.12:36
onefangDid you try "continue"?12:36
rktaLike I said, I managed to fix my system, hence I did not continue the install.12:37
rrqrkta: did you take the prior "load components" step?12:38
rktarrq: I'd think yes, but I might be wrong... I can reboot later and try to reproduce.12:41
rrqthanks12:42
rktarrq: You are right, I must have skipped this step. Sorry for the noise.12:51
rrqthanks though :)12:51
rktabtw, since when does one need a non-free-firmware repo? Wasn't firmware not included in non-free? Or did I mess up my sources.lst some time...12:56
brocashelmrkta: for things like the intel, broadcom, realtek, etc. wifi drivers that are proprietary, as well as the intel-microcode, amd64-microcode, firmware-amd-graphics, etc. packages; debian moved those out of non-free, in case you'd need them12:57
brocashelmas of bookworm/daedalus, you need to append "non-free-firmware" on your sources.list file12:58
brocashelmexample: deb http://deb.devuan.org/merged/ daedalus main contrib non-free non-free-firmware12:58
rktabrocashelm: I found out after rebooting, when my system was borked. I guess I should have read the release/upgrade notes more carefully I guess. :D12:59
brocashelmyeah, i can see the pros and cons of such a move; once that's out of the way, it's smooth sailing13:00
brocashelmnow, we are faced with excalibur (testing) and ceres (unstable) having the misfortunes of usrmerge changing where the kernel loads firmware from (i.e. instead of /lib, it's /usr/lib sans any symlink for backwards compatibility with legacy setups)13:01
rktaI'm more and more disappointed with the linux world.13:04
djphDebian's done things this way for 20 years ...13:12
djphoh no nvm, misread, ignore me13:13
adam_free2airhaven't yet looked into this in depth, but perhaps overlayfs is worth looking into as a tool to help redress usrmerge issues?14:51
cousin_luigiJoril: Pardon my stalking, but is it normal that with radicale, entries seem to go one way only? I can't push existing ones from my phone and I can't receive new ones from my pc.15:47
cousin_luigiadam_free2air: Good grief, adding another layer of complexity to make thing simpler?15:47
cousin_luigithings*15:47
Jorilcousin_luigi: Well that's strange, I push events from my phone and read them from PC all the time... I'm using CalDAV-sync on the phone and Thunderbird on the PC15:51
adam_free2aircousin_luigi: there is rarely 'good' grief. we should think about dealing with this with a mininum amount of maintenance in the long term as well as a minimum amount of grief and complexity. other suggestions welcome.22:04

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!