You are not logged in.
Pages: 1
Hello!
I've downloaded an image https://arm-files.devuan.org/RaspberryP … 2-0243.zip and installed it. It works fine, but I see 3 obsolete packages:
root@devuanpi:~# apt list '?obsolete'
Listing... Done
linux-headers-bcm2710-rpi-3/now 6.1.54-1 arm64 [installed,local]
linux-image-bcm2710-rpi-3/now 6.1.54-1 arm64 [installed,local]
raspberrypi-sys-mods/now 20220224 arm64 [installed,local]
root@devuanpi:~# apt-cache policy linux-image-bcm2710-rpi-3
linux-image-bcm2710-rpi-3:
Installed: 6.1.54-1
Candidate: 6.1.54-1
Version table:
*** 6.1.54-1 100
100 /var/lib/dpkg/status
…
The sources file /etc/apt/sources.list was:
deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
I replaced it with
deb http://pl.deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
deb http://pl.deb.devuan.org/merged daedalus-updates main contrib non-free non-free-firmware
deb http://pl.deb.devuan.org/merged daedalus-security main contrib non-free non-free-firmware
deb http://pl.deb.devuan.org/merged daedalus-backports main contrib non-free non-free-firmware
but still the same — 3 obsolete packages.
I'm afraid they will never be updated.
Is there any way to add an official repository for them?
Also, where can I found script/pipeline which creates these images? could you please add this information into https://arm-files.devuan.org/README.txt?
Last edited by vazhnov (2023-10-11 19:52:17)
Offline
1. I too have obsoleted packages, all pi-specific, having also installed one of the arm64 .zip images for Daedalus recently (an rpi-4-devuan-daedalus .... .zip for my Pi 400:
$ apt list '?obsolete'
Listing... Done
linux-headers-bcm2711-rpi-4/now 6.1.54-1 arm64 [installed,local]
linux-image-bcm2711-rpi-4/now 6.1.54-1 arm64 [installed,local]
pi-bluetooth/now 0.1.13 all [installed,local]
raspberrypi-sys-mods/now 20220224 arm64 [installed,local]
rpi-eeprom-images/now 16.1-1 arm64 [installed,local]
rpi-eeprom/now 16.1-1 arm64 [installed,local]
Yet I do not recall instructing any specific pi packages to be upgraded unless it was part of the proposed apt updates/upgrades.
I noted earlier, at about the time that some linux headers didn't install/upgrade (although I can't remember whether it was during my previous installation --an attempted upgrade from Devuan Chimaera to Daedalus or during this Daedalus zip installation) that there were one or more failures reported with the initramfs, including at reboot. So perhaps these images or upgrades don't work fully automatically for Pis? There is no /boot/cmdline.txt at present in my /boot directory, somehow; a line in that file is perhaps akin to the kernel line in non-Raspberry Linux systems. Yet that cmdline.txt has been useful in part to get apparmor activated in the previous installation, when the file was present (adding lsm="apparmor" in that file, as indicated elsewhere). Maybe, in part, if the cmdline.txt were present, perhaps the initramfs would help to avoid obsoleted linux-header packages?
2. Do you need the backports line in the sources.list? I wonder if that is also impeding some from packages from getting upgraded; I thought I had read that the backports repo is a more recent addition to the stable Daedalus release. I suppose however that you might have had to instruct apt to use a backport for some specific packages, anyway --it's just a thought.
Could anyone else chime in to help vazhnov, please? Thank you.
Last edited by ExposeGlobalistsMadness (2023-10-10 22:22:28)
Offline
It's a community build. The packages aren't obsolete, but custom made. Meaning, they aren't officially supported.
Source; https://github.com/pyavitz/rpi-img-builder
Devuan fork; https://github.com/dyne/rpi-img-builder
Offline
c0rnelius c0rnelius, thank you for links!
So, these Raspberry PI builds doesn't have possibility to update these custom-made packages automatically (as other packages, with apt). Sad. I think this should be described somewhere in chapter "Known issues".
Offline
The kernel can be updated if you build it ur self using the github repo. There is also a deb-eeprom script on the pi4 images that can be used to update the eeprom package. Warning: I no longer have a Pi4, so I have no idea how well it works anymore and honestly I'm sure the script needs to be updated and made easier to use.
As for pi-bluetooth and sys-mods. There isn't much to do there, as they are basically just debs that install scripts and udev rules and such.
Offline
Thanks also for the additional insights on eeprom, pi-bluetooth and sys-mods, c0rnelius, they are appreciated.
Offline
Just FYI: I've installed Debian OS image https://raspi.debian.net/tested/2023061 … orm.img.xz and it has no obsolete packages.
After the first boot, I successfully updated all the packages, including Linux kernel:
root@rpi3-20230612:~# uname -a
Linux rpi3-20230612 6.1.0-9-arm64 #1 SMP Debian 6.1.27-1 (2023-05-08) aarch64 GNU/Linux
root@rpi3-20230612:~# apt-get -V --no-install-recommends dist-upgrade
…
The following NEW packages will be installed:
linux-image-6.1.0-13-arm64 (6.1.55-1)
The following packages will be upgraded:
base-files (12.4 => 12.4+deb12u2)
…
linux-image-arm64 (6.1.27-1 => 6.1.55-1)
After reboot:
root@rpi3-20230612:~# uname -a
Linux rpi3-20230612 6.1.0-13-arm64 #1 SMP Debian 6.1.55-1 (2023-09-29) aarch64 GNU/Linux
root@rpi3-20230612:~# apt-cache policy linux-image-6.1.0-13-arm64
linux-image-6.1.0-13-arm64:
Installed: 6.1.55-1
Candidate: 6.1.55-1
Version table:
*** 6.1.55-1 500
500 http://deb.debian.org/debian bookworm/main arm64 Packages
100 /var/lib/dpkg/status
Firmware packages:
root@rpi3-20230612:~# dpkg -l|grep -i firmware
ii bluez-firmware 1.2-9 all Firmware for Bluetooth devices
ii firmware-brcm80211 20230210-5 all Binary firmware for Broadcom/Cypress 802.11 wireless cards
ii firmware-linux-free 20200122-1 all Binary firmware for various drivers in the Linux kernel
ii raspi-firmware 1.20220830+ds-1 all Raspberry Pi family GPU firmware and bootloaders
Their /etc/apt/sources.list is
deb http://deb.debian.org/debian bookworm main non-free-firmware non-free
deb http://deb.debian.org/debian bookworm-updates main non-free-firmware non-free
deb http://security.debian.org/debian-security bookworm-security main non-free-firmware non-free
# Backports are _not_ enabled by default.
# Enable them by uncommenting the following line:
# deb http://deb.debian.org/debian bookworm-backports main non-free-firmware
Offline
Pages: 1