Download | Devuan.org | Git | Bugs | Packages

The officially official Devuan Forum!

You are not logged in.

Pages: 1

#1 Re: Installation » [SOLVED] The key(s) in the keyring are ignored as the file has an unsupported f » 2025-11-07 07:59:35

jonny101

Okay I think I solved it by just deleting the keyring files that produced the warnings. Maybe they were just outdated?

#2 Installation » [SOLVED] The key(s) in the keyring are ignored as the file has an unsupported f » 2025-11-07 05:16:46

jonny101
Replies: 1

After the upgrade Daedalus -> Excalibur I get following warnings every time I do an apt update:

[sudo] Passwort für jonny: 
Holen:1 http://deb.devuan.org/merged excalibur InRelease [48,0 kB]
Holen:2 http://deb.devuan.org/merged excalibur-updates InRelease [37,6 kB]         
OK:3 https://oph.mdrjr.net/meveric all InRelease            
Holen:4 http://deb.devuan.org/merged excalibur-security InRelease [37,9 kB]
OK:5 https://oph.mdrjr.net/meveric bookworm InRelease       
Es wurden 124 kB in 1 s geholt (102 kB/s).                  
Alle Pakete sind aktuell.                   
Warnung: http://deb.devuan.org/merged/dists/excalibur/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/devuan-keyring-2016-archive.asc are ignored as the file has an unsupported filetype.
Warnung: http://deb.devuan.org/merged/dists/excalibur/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/devuan-keyring-2022-archive.asc are ignored as the file has an unsupported filetype.
Warnung: https://oph.mdrjr.net/meveric/dists/all/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/devuan-keyring-2016-archive.asc are ignored as the file has an unsupported filetype.
Warnung: https://oph.mdrjr.net/meveric/dists/all/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/devuan-keyring-2022-archive.asc are ignored as the file has an unsupported filetype.
Warnung: http://deb.devuan.org/merged/dists/excalibur-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/devuan-keyring-2016-archive.asc are ignored as the file has an unsupported filetype.
Warnung: http://deb.devuan.org/merged/dists/excalibur-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/devuan-keyring-2022-archive.asc are ignored as the file has an unsupported filetype.
Warnung: https://oph.mdrjr.net/meveric/dists/bookworm/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/devuan-keyring-2016-archive.asc are ignored as the file has an unsupported filetype.
Warnung: https://oph.mdrjr.net/meveric/dists/bookworm/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/devuan-keyring-2022-archive.asc are ignored as the file has an unsupported filetype.
Warnung: http://deb.devuan.org/merged/dists/excalibur-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/devuan-keyring-2016-archive.asc are ignored as the file has an unsupported filetype.
Warnung: http://deb.devuan.org/merged/dists/excalibur-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/devuan-keyring-2022-archive.asc are ignored as the file has an unsupported filetype.

Does anybody have a clue why?
Thank you for any help you can provide!

#3 Re: Other Issues » [SOLVED] uncomplete SSH disconnect on reboot » 2024-08-12 08:01:08

jonny101

@ralph.ronnquist That did the trick! big_smile Thanks a lot! I will make an alias with this one...

#4 Re: Other Issues » [SOLVED] uncomplete SSH disconnect on reboot » 2024-08-12 06:23:49

jonny101

Unfortunately I can't type anything because the console becomes unresponsive. So the only options I have are:

a. close that terminal and start a new one or
b. wait for that session to time-out (which gives me a client_loop: send disconnect: Broken pipe error afterwards.

Although I'm not very familiar with init.d my guess is that I need to change something in the way the services are shutdown (maybe the order) but I don't know where to start.

#5 Other Issues » [SOLVED] uncomplete SSH disconnect on reboot » 2024-08-12 05:33:43

jonny101
Replies: 5

Hi everybody,

I've got the following SSH issue bugging me when rebooting my Devuan 5 machine.

devuan@DevuanRpi:~$ sudo reboot 

Broadcast message from root@DevuanRpi (pts/1) (Mon Aug 12 07:02:06 2024):

The system is going down for reboot NOW!

Broadcast message from root@DevuanRpi (pts/1) (Mon Aug 12 07:02:06 2024):

The system is going down for reboot NOW!
devuan@DevuanRpi:~$ █

It seems as if the reboot proceeds faster than the SSH service is able to logout - thus my terminal becomes unresponsive for 15+ minutes.
Now it is not that big of a disturbance but quite an annoyance. Besides I would like to understand the reason for this.

Could somebody help me please?

#6 Re: Documentation » log2ram with sysv » 2024-07-28 09:28:30

jonny101

Okay after researching for another hour or so I found that log2ram is the successor of a project called transientlog which in turn was born out of an article from debian-administration.org called A transient /var/log - back in 2010 when systemd wasn't yet relevant.

Therefore I was able to apply transientlog almost without modification to my Devuan 5 install and for now it seems to work. It creates a RAM drive on startup and copies all log files into it. On shutdown/reboot it does the opposite. It copies all log files from the RAM drive to the eMMC card. The only thing I modified was the size of the RAM drive - from 25M to 90M because my log folder was already 38M in size.

I will keep monitoring the script to see if it is stable and report my findings.

#7 Documentation » log2ram with sysv » 2024-07-28 05:18:25

jonny101
Replies: 9

Hi everybody,

i just got Devuan working on my Odroid N2+ using the maveric image as starting point (works flawlessly 🥰).

Now in order to spare the eMMC I used to run log2ram on it but log2ram is dependent on systemd.
According to the developer it should also work with init.d only the init script is needed.

My question is, does anyone use log2ram with sysvinit or knows another simple tool I could use to write logs to ram? I have no experience with sysv so far and thought I'd ask before starting to tinker myself.

Thank you.

#8 Re: Installation » Upgrade to Daedalus did not upgrade kernel » 2024-06-21 08:42:29

jonny101

Then he wants to install

apparmor linux-image-6.1.0-21-arm64

I think this is it! Thanks a lot @delgado!

#9 Re: Installation » Upgrade to Daedalus did not upgrade kernel » 2024-06-21 06:02:10

jonny101

Hi! Thank you for your reply!

It says:

raspberrypi-linux-image/now 5.10.74-v8-1~rpi2+3 arm64  [Installiert,lokal]

So I guess it's installed? But it seems to be a special kernel for the Raspberry Pi 3 🤔

#10 Installation » Upgrade to Daedalus did not upgrade kernel » 2024-06-20 08:45:56

jonny101
Replies: 4

Hi there,

yesterday I upgraded the Chimaera 4.0 image to Daedalus 5.0 on my Raspberry Pi 3b+. I was happy to see that everything really went flawlessly. Just the kernel stayed at 5.10.74-v8.

How can I upgrade the kernel as well?

Thanks in advance!

Pages: 1

Board footer

Forum Software