You are not logged in.
Pages: 1
After recent upgrade of sed package it is now installed in /usr/bin/sed instead of the /bin/sed and with runit-init it breaks the boot process at runit stage 1 because scripts in /etc/rcS.d/ fail to run due to sed: not found.
I get this in boot process output:
- runit: enter stage: /etc/runit/1
/etc/rcS.d/S01mountkernfs.sh: 11: /lib/init/tmpfs.sh: sed: not found
/etc/rcS.d/S01mountkernfs.sh: 19: /lib/init/tmpfs.sh: sed: not found
...
/etc/rcS.d/S02eudev: 84: sed: not found
mkmod: missing operand after 'c!'
/etc/rcS.d/S03mountdevsubfs.sh: 11: /lib/init/tmpfs.sh: sed: not found
/etc/rcS.d/S03mountdevsubfs.sh: 19: /lib/init/tmpfs.sh: sed: not found
...
Setting up keyboard layout...done.
Starting boot logger: bootlogdActivating swap...done.
/etc/rcS.d/S01mountkernfs.sh: 11: /lib/init/tmpfs.sh: sed: not found
/etc/rcS.d/S01mountkernfs.sh: 19: /lib/init/tmpfs.sh: sed: not found
...
As a result everything is broken. X won't start due to no devices found and many other things don't work.
I fixed it by symlinking sed to /bin/ with
ln -s /usr/bin/sed /bin/sed
Anyhow, I'm interested, is it a consequence of the ongoing "merged /usr" revolution? And is Devuan going to merge /usr in the end or will create workarounds for things like this?
After reboot with the new version I got broken WiFi. Had to reinstall the old version (Feb10) from daedalus. But this is not Devuan's issue now, so the original issue is solved I guess.
Maybe the mirror isn't up to date? Perhaps you try deb.devuan.org/merged instead?
I've been trying different mirrors in Germany, Netherlands, Serbia and Russia, and they all had the non-existent version. The deb.devuan.org doesn't work for me because it takes forever to connect.
Right now I did apt update once again and finally there's the June 25 version available.
I think the issue is that May 2023 package has been removed.
Well... Yes, but why does apt think that this non-existent version is a candidate for upgrade?
Here's the apt policy firmware-iwlwifi output:
firmware-iwlwifi:
Installed: 20230210-5
Candidate: 20230515-3
Versions table:
20230515-3 500
500 http://devuan.sedf.de/merged excalibur/non-free-firmware amd64 Packages
500 http://devuan.sedf.de/merged excalibur/non-free-firmware i386 Packages
*** 20230210-5 100
100 /var/lib/dpkg/status
Shouldn't apt update get the actualized information about available candidates?
There's a problem with the firmware-iwlwifi package in the excalibur/testing branch.
On an upgrade attempt I get this:
Ign:1 http://devuan.sedf.de/merged excalibur/non-free-firmware amd64 firmware-iwlwifi all 20230515-3
Err:1 http://devuan.sedf.de/merged excalibur/non-free-firmware amd64 firmware-iwlwifi all 20230515-3
404 Not Found [IP: 151.101.86.132 80]
E: Failed to fetch http://devuan.sedf.de/merged/pool/DEBIAN/non-free-firmware/f/firmware-nonfree/firmware-iwlwifi_20230515-3_all.deb 404 Not Found [IP: 151.101.86.132 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
apt update and apt upgrade --fix-missing don't fix the issue.
It's not a connection issue because right now I have upgraded the other packages by marking the firmware-iwlwifi as "hold" with
apt-mark hold firmware-iwlwifi
. Obviously unless I mark it as "hold" the upgrade process fails due to the 404 error.
The link from the apt error message shows that there's no package with the given version (20230515-3) in Debian repos - it leads to 404 page. But there are two other versions:
20230210-5: http://ftp.debian.org/debian/pool/non-f … -5_all.deb
20230625-1: http://ftp.debian.org/debian/pool/non-f … -1_all.deb
PS: 2 days ago the same thing happened to firmware-misc-nonfree as well. I've been getting 404 errors for both iwlwifi and misc-nonfree packages, but then somehow the misc-nonfree one successfully upgraded. Yet the iwlwifi one still not upgradable.
Is this a known issue?
You didn't tell what DE you use, so assuming that you use XFCE as the Devuan's default DE, I think it's probably XFCE specific issue. Just tested it in MATE DE by adding UK layout and it works fine.
XFCE has a config file for keyboard layouts in ~/.config/xfce4/xfconf/xfce-perchannel-xml/keyboard-layout.xml. Check out the contents of this file. I think it should have uk in the layout property field, something like this <property name="XkbLayout" type="string" value="uk"/>. Or <property name="XkbLayout" type="string" value="uk,us"/> if you have both UK and US layouts.
also the idea of using a browser from github is a bit creepy, i consider everything on github controlled by microsoft. that problem is going to get worse before it gets better.
Uhm... https://github.com/torvalds/linux Houston, we have a problem!
I would like to add some more details on the issue and suggest a slightly different solution.
Since the issue is caused by the nvidia-persistenced package alone, I believe that the workaround with --no-install-recommends is not an optimal one. User likely might want to get the other recommended packages for nvidia-driver to be installed. The nvidia-settings (GUI tool for NVidia driver settings) is one of the recommended ones, for example. Also, for Steam-Proton the nvidia-driver-libs:i386 is required, and it is also marked as recommended for nvidia-driver (assuming that the user have enabled i386 architecture before the driver installation). And the linux kernel headers along with nvidia DKMS package (both are required to build the driver module during the installation)) are also in the recommended.
So, instead of using --no-install-recommends I think the better option would be to just not install nvidia-persistenced alone, and we can do that with apt-mark.
To prevent the installation of nvidia-persistenced and it's i386 version (if you have i386 packages enabled) do this:
$ sudo apt-mark hold nvidia-persistenced nvidia-persistenced:i386
After this you can just install the driver as usual. All the dependencies will be pulled and installed except the nvidia-persistenced.
In my case with Devuan Chemaera and 1050Ti all I need to do to install NVidia drivers and get them ready for Steam-Proton is:
1. Enable i386 packages for Steam and nvidia-driver-libs:i386 which is required by Steam:
$ sudo dpkg --add-architecture i386
$ sudo apt update
2. Put the problematic packages on hold:
$ sudo apt-mark hold nvidia-persistenced nvidia-persistenced:i386
2. Install the driver meta-package. It pulls all the other required packages like DKMS build tools, i386 libs, etc. recommended so they are getting installed automatically.
$ sudo apt install nvidia-driver
3. The last step is Steam:
$ sudo apt install steam
Probably in the case of the legacy 390 driver the steps for headers and DKMS were required. In case of current 460 driver everything is installed automatically thanks to the recommended packages auto installation process.
Pages: 1