sudo apt update
34 packages can be upgraded. Run ‘apt -upgraded’ to them.
Notice: Missing Signed-By in the sources.list(5) entry for ‘Index of /reform-debian-repo/’
Help please.
Bob
This is by design. The repo is not signed because there isn’t a meaningfully secure way in which signing could be automated on our end (it would be too much work/too expensive for us to make automated signing really secure and we don’t want to pretend something is secure, so we don’t do it). But the repo is served over HTTPS, so at least the HTTP traffic is authenticated.
How are making it work?
thanks
The message you see is of type “notice” (as indicated by it prefixed with “Notice:”) and as such is not an error and not even a warning. As a message of “notice” type it is just trying to inform you of something. It doesn’t want to tell you that something went wrong.
Also
sudo apt upgrade
get:
Errors were encountered while processing:
/tmp/apt-dpkg-instal1-XzL0C8/11-linux-Image-6.11,5-mnt-reform-arm54_6.11.5-1+reforn20241105T103359Z_arn64.deb Error: Sub-process /us/bin/dpkg returmed an errar code (1)
Help
uh that sounds bad.
Can you copypaste the relevant parts from your “apt upgrade” output? What you wrote has some spelling mistakes. Did you type that by hand? You can use copypaste which will be faster and will not contain innocent typos.
Hi, this is probably not the error message you got back when you originally received the dpkg error. We’d need that error message. You should still be able to obtain in from /var/log/apt/term.log. But since you got that error, every subsequent run of sudo apt upgrade will now suggest to you to run apt --fix-broken install which in theory is the right thing to do but I also see that you are without a network connection. It would be easiest to fix your problem if you had internet. Is there a way for you to connect to an ethernet network if you don’t have wifi?
That photo nicely shows everything that’s going on. Thank you!
So, some packages on a Debian system are packaged in a way such that you can install multiple versions of them at the same time. One example are shared libraries with different SONAME and in your screenshot you see that you still have old versions of libfmt9 or libperl5.38t64 installed. When a transition happens to a new version and as you upgrade packages depending on them, there will come the point where nothing depends on them anymore. At that point the package is still installed but its original reason for being installed is gone. If this happens to a package, apt will suggest that you can autoremove the package. This is what you see in your screenshot where apt tells you “Use ‘sudo apt autoremove’ to remove them”. Other than shared libraries, another typical package affected by this is the linux kernel itself. You can have multiple versions of the linux kernel installed at the same time. But the kernel image itself as well as the initramfs live in a partition called /boot. This partition is “only” 488 MB small, so it can only hold a certain number of copies of linux. In your screenshot one can see that apt suggests that you can autoremove six versions of the linux kernel. Why should you follow apt’s suggestion? You see one reason for doing so further down. Above the “error” marked in red you see the message “failed to write (No space left on device)”. This is telling you that dpkg failed to install a new version of the linux package because you ran out of space on your disk, likely in /boot. Fixing this should be as easy as first running:
sudo apt autoremove
This will remove a bunch of packages, most importantly the six old versions of the linux kernel which are currently crowding your /boot. And then you run:
sudo apt --fix-broken install
Which will try installing the most recent kernel image again and that should now succeed as you cleaned up old kernel images.
On Debian stable installations you usually only need to run sudo apt autoremove once every 2 years because you’ll not do considerable upgrades more often than that. All the other package upgrades in that time will be security related upgrades which typically do not lead to anything getting marked for autoremoval. But on your Pocket Reform you are running Debian unstable and from the kernels you have installed one can see that you have upgraded your system regularly. This means, that you should also run sudo apt autoremove more regularly.
You are not the first running into this. This is a related topic: /boot too small?
2 Likes
Uff… this is annoying. I don’t mean that you are annoying me but that this is a very annoying issue and I am very surprised that apt lets you get into this situation in the first place. So the problem is, that for “apt autoremove” to work, apt suggests you run “apt --fix-broken install” but that cannot work because your /boot is too small.
I fear you have to fix this situation manually. Unless somebody else has an idea?
You can manually remove one of the old kernel images suggested by apt like this:
sudo apt remove linux-image-6.10.7-mnt-reform-arm64
If apt doesn’t let you do this, try going one level deeper:
sudo dpkg -r linux-image-6.10.7-mnt-reform-arm64
I hope this helps!