[SOLVED] dist upgrade to excalibur hits only security packages

mclien · 2025-11-04 14:40:54

I was attempting to upgrade one of my PCs,
so I adjusted the sources:

/etc/apt# cat sources.list.d/devuan.sources 
# Devuan 6 excalibur
## The new style method of using repositories to install software.
## This /etc/apt/sources.list.d/devuan.sources is new style and location file
## The /etc/apt/old.style.sources.list contains the same as this.
## https://linuxconfig.org/ubuntus-repository-configuration-ubuntu-sources-have-moved-to-etc-apt-sources-list-d-ubuntu-sources
 
## Normal excalibur sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: excalibur excalibur-backports excalibur-proposed-updates  excalibur-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
 
## excalibur security sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: excalibur-security
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

disabled the daedalus soureces, but get this:

t# apt-get update
Get:1 http://deb.devuan.org/merged excalibur-security InRelease [37.9 kB]
Fetched 37.9 kB in 15s (2,603 B/s) 
Reading package lists... Done

Why do I get no get on the othre sources?

I had to switch back once to daedalus, because I forgot to install usrmerge.

EDIT (solution):
If you copy with left/middle mousebutton from one VI to another, there will be spaces added to blank lines, with confuses the sources.list

Last edited by mclien (Yesterday 18:01:35)

rolfie · 2025-11-04 15:36:38

What about the sources.list? Does that still exist? It must be deleted or renamed.

Last edited by rolfie (2025-11-04 17:13:56)

mclien · 2025-11-04 17:11:10

renamed, which I meant by "disabled the daedalus sources"
Already did it that way with another machine.
Could it be, I need some cleanup from switchen the sources back and forth?

Strange thing is: Why does it get the security packages but not the normal packes from the same devuan.sources?

Last edited by mclien (2025-11-04 17:20:22)

rolfie · 2025-11-04 17:17:51

Then thats out of the way.

I don't see any obvious fault in the file. The only thing that catches my eyes are two blanks between "excalibur-proposed-updates excalibur-updates".

Well, I would check the devuan.sources file with nano if there is any "bad" character in there.

And maybe you give apt instead of apt-get a try. Nowadays I only use apt.

mclien · 2025-11-04 17:23:56

the devuan.sources is a copy of the one I used with a successful update on the other machine.
apt shows the same behaviour:

# apt update
Hit:1 http://deb.devuan.org/merged excalibur-security InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
22 packages can be upgraded. Run 'apt list --upgradable' to see them.

maybe a problem with http://deb.devuan.org/ ?

Last edited by mclien (2025-11-04 17:24:30)

mclien · 2025-11-04 17:34:29

for testing I changed the URI to

 apt-get update  http://de.deb.devuan.org/merged
Get:1 http://de.deb.devuan.org/merged excalibur-security InRelease [37.9 kB]
Get:2 http://de.deb.devuan.org/merged excalibur-security/main amd64 Packages [69.8 kB]
Get:3 http://de.deb.devuan.org/merged excalibur-security/main Translation-en [47.3 kB]
Get:4 http://de.deb.devuan.org/merged excalibur-security/non-free-firmware amd64 Packages [548 B]
Get:5 http://de.deb.devuan.org/merged excalibur-security/non-free-firmware Translation-en [306 B]
Fetched 156 kB in 4s (40.9 kB/s)       
Reading package lists... Done

Still only security, but more hits?

rolfie · 2025-11-04 17:40:23

Just did some experiments in a VM updated from Daedalus. It works when I split up the suites into a list of single entries. When they are all in one line like in your example "excalibur excalibur-backports excalibur-proposed-updates excalibur-updates" it does not work.

Miracle.

mclien · 2025-11-04 17:46:52

you mean like:

## Normal excalibur sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: excalibur 
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64

## excalibur-backports sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: excalibur-backports
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
[..]

wouldn't that defeat the elegance of the new format a bit?

Last edited by mclien (2025-11-04 17:50:48)

rolfie · 2025-11-04 17:51:34

Sure, but it seems to work. Anyway, it looks like this apt modernize-sources splits it up too.

Edith: the Suites in one line does work in a VM that was setup earlier on from a cli Daedalus netinstall upgraded to Excalibur, and then installing a Cinnamon DE. Don't understand where the differences are ...

The working one:

/etc/apt/sources.list.d# cat devuan.sources
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur excalibur-security excalibur-updates excalibur-backports
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

The other one on a Daedalus Upgrade isn't working:

/etc/apt/sources.list.d# cat devuan.sources
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur-updates
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur-security
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

Last edited by rolfie (2025-11-04 18:41:06)

rolfie · 2025-11-04 18:09:48

On a second try, now the upgraded system that did strike seems to accept the Suites in one line now:

/etc/apt/sources.list.d# cat devuan.sources
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur excalibur-updates excalibur-security
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
#Types: deb
#URIs: http://deb.devuan.org/merged/
#Suites: excalibur-updates
#Components: main contrib non-free non-free-firmware
#Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
#Types: deb
#URIs: http://deb.devuan.org/merged/
#Suites: excalibur-security
#Components: main contrib non-free non-free-firmware
#Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

/etc/apt/sources.list.d# cat devuan-backports.sources
# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur-backports
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

Now apt update does this:

/etc/apt/sources.list.d# apt update
OK:1 http://deb.devuan.org/merged excalibur-backports InRelease
OK:2 http://deb.devuan.org/merged excalibur InRelease
OK:3 http://deb.devuan.org/merged excalibur-updates InRelease
Holen:4 http://deb.devuan.org/merged excalibur-security InRelease [37,9 kB]
Es wurden 37,9 kB in 0 s geholt (145 kB/s).
Alle Pakete sind aktuell.

mclien · 2025-11-04 18:14:10

So both of the above work? (from post #9)
can you open it with vim to see if there any hidden CR/LF symbols?
EDIT:
My devuan.sources (generated by hand not with "apt mordernize-sources") is from a PC I did upgrade prior to the excalibur release (just a few days)
-on that machine, I get all sources with the "all suites in one line"

using the same file now on another machine gives the "only secure" result.

Last edited by mclien (2025-11-04 18:37:33)

rolfie · 2025-11-04 18:27:15

I have used nano on both VMs to edit the .sources, I never used vi or vim, I do not get along with these editors. I am sure the files are clean and pure linux text files.

Both VMs had sort of incomplete Suites in them.

I have no idea why I got so contradicting results. Now both VMs work with the Suites in a line.

mclien · 2025-11-04 18:30:21

something strange in the /etc/apt dir:
(kamin is the new pc, eline the old)

root@kamin:/etc/apt# ls -l
total 36
drwxr-xr-x 2 root root 4096 Mar  9  2024 apt.conf.d
drwxr-xr-x 2 root root 4096 May 28  2023 auth.conf.d
drwxr-xr-x 2 root root 4096 May 28  2023 keyrings
-rw-r--r-- 1 root root  150 Mar  9  2024 listchanges.conf
drwxr-xr-x 2 root root 4096 Mar 28  2021 listchanges.conf.d
drwxr-xr-x 2 root root 4096 May 28  2023 preferences.d
-rw-r--r-- 1 root root    0 Mar  9  2024 sources.list~
drwxr-xr-x 2 root root 4096 Nov  4 18:30 sources.list.d
-rw-r--r-- 1 root root 1358 Jul  7  2024 sources.list_daedalus
drwxr-xr-x 2 root root 4096 Nov  4 12:54 trusted.gpg.d

root@eline:/etc/apt# ls -l
total 36
drwxr-xr-x 2 root root 4096 Nov  1 10:33 apt.conf.d
drwxr-xr-x 2 root root 4096 May 28  2023 auth.conf.d
drwxr-xr-x 2 root root 4096 May 28  2023 keyrings
-rw-r--r-- 1 root root  147 Nov  1 10:27 listchanges.conf
drwxr-xr-x 2 root root 4096 Mar 28  2021 listchanges.conf.d
drwxr-xr-x 2 root root 4096 May 28  2023 preferences.d
-rw-r--r-- 1 root root    0 Oct 17 21:12 sources.list~
drwxr-xr-x 2 root root 4096 Nov  1 10:14 sources.list.d
-rw-r--r-- 1 root root 1209 Oct 26 16:04 sources.list_daedlus
drwxr-xr-x 2 root root 4096 Nov  1 10:27 trusted.gpg.d

I'm a bit confused about the timestamps of some dirs

mclien · 2025-11-04 18:35:19

As for the file: I would too, say those are clean text files.
BTW: it's the other was around with me: I do not get anĺong with nano (might be it is, that I'm used to vi since my first encounters with *nix systems in 1997, Solaris and IRIX in that case).

Seems I have to try the split version of the sources file on the new machine for reasons that might stay mysterious...

UPDATE:
splitting the file was in vain:

# Devuan 6 excalibur
## The new style method of using repositories to install software.
## This /etc/apt/sources.list.d/devuan.sources is new style and location file
## The /etc/apt/old.style.sources.list contains the same as this.
## https://linuxconfig.org/ubuntus-repository-configuration-ubuntu-sources-have-moved-to-etc-apt-sources-list-d-ubuntu-sources
 
## Normal excalibur sources
Types: deb
URIs: http://de.deb.devuan.org/merged
Suites: excalibur
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
 
## backports excalibur sources
Types: deb
URIs: http://de.deb.devuan.org/merged
Suites: excalibur-backports
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
 
## proposed-updates excalibur sources
Types: deb
URIs: http://de.deb.devuan.org/merged
Suites: excalibur-proposed-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
 
## updates excalibur sources
Types: deb
URIs: http://de.deb.devuan.org/merged
Suites: excalibur-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64
 
## excalibur security sources
Types: deb
URIs: http://de.deb.devuan.org/merged
Suites: excalibur-security
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

still:

root@kamin:/etc/apt/sources.list.d# apt-get update
Hit:1 http://de.deb.devuan.org/merged excalibur-security InRelease
Reading package lists... Done

Last edited by mclien (2025-11-04 18:44:12)

ralph.ronnquist · 2025-11-04 22:35:35

That blank line between the stanzas, does that contain any spaces or tab?

mclien · 2025-11-05 13:10:04

No.
But that wouldn't explain why it showed the same behaviour with the old style of the sources file.

PC was off over night, I now checked the devuan.sources file and I deleted and re-insert the blank lines.
Then I get a working update.

For testing I changed back to the short variant with all suites in one line (only excalibur-security in a separat stanza):
apt-get update, again, give me only security.

changing back to the previous working one, I still get only the security updates.

very un-deterministic

EDIT: quite often I get this behaviour (there was about 5sec between the error and the next execution of the command:

root@kamin:~# apt-get update 
Ign:1 http://de.deb.devuan.org/merged excalibur-security InRelease
Err:2 http://de.deb.devuan.org/merged excalibur-security Release
  404  Not Found [IP: 147.229.176.19 80]
Reading package lists... Done
E: The repository 'http://de.deb.devuan.org/merged excalibur-security Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@kamin:~# apt-get update 
Hit:1 http://de.deb.devuan.org/merged excalibur-security InRelease
Reading package lists... Done

EDIT2: reboot or halt -p do not change the situation, still only a hit on security packages.

As http://de.deb.devuan.org/ should be e repo pool: might there be some repos not up to date?

Last edited by mclien (2025-11-05 13:34:08)

mclien · 2025-11-05 18:44:47

OK, maybe there is something strange.
As I disabled the daedalus sources, it looked like this:

root@kamin:~# ls -l /etc/apt/ |grep sources
-rw-r--r-- 1 root root    0 Mar  9  2024 sources.list~
drwxr-xr-x 2 root root 4096 Nov  5 19:30 sources.list.d
-rw-r--r-- 1 root root 1358 Jul  7  2024 sources.list_daedalus

I just checked it again on a hunch:

root@kamin:~# ls -l /etc/apt/ |grep sources
-rw-r--r-- 1 root root    0 Nov  5 14:10 sources.list
-rw-r--r-- 1 root root    0 Mar  9  2024 sources.list~
drwxr-xr-x 2 root root 4096 Nov  5 19:30 sources.list.d
-rw-r--r-- 1 root root 1358 Jul  7  2024 sources.list_daedalus

Do I have a gap of knowledge here?
Where does the empty sources.list come from? Is that something generated from the sources.list~?

Anyways, deleting the two empty files, gives me:

root@kamin:~# ls -l /etc/apt/ |grep sources
drwxr-xr-x 2 root root 4096 Nov  5 19:30 sources.list.d
-rw-r--r-- 1 root root 1358 Jul  7  2024 sources.list_daedalus

And now I'm getting hits on all repos/suits. Just bugs me, that I don't get the whole picture here..

Last edited by mclien (2025-11-07 20:23:25)

mclien · 2025-11-07 20:45:16

Next PC, same problem.
This time I removed sources.list and sources.list~
And placed the new style devuan.sources in /etc/apt/sources.de/

Again only getting hits on security updates.

So the working solution from before seems to be coincidence not causality.
So I'm kind of back to square one.

(additionally the newest daedalus kernel seems to miss activating the USB subsystem on my chromebox. I have to start the old kernel to have a keyboard)

mclien · 2025-11-08 11:42:54

I just started the notebook, which I change to excalibur just a few days prior to the release.
So the new style devuan.sources there worked flawlessly in that process.

I did not change anything with that sources and now an apt-get update gives me

E: The repository '<any-of-the-non-secure-excalibur-repos> Release' no longer has a release  file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

(sorry for not c&p this, it's only om tty0 of the other machine)

So still no idea how to fix this reliable.

EDIT: similar errors of other debian derivates mostly suggest missing/faulty repos.
Is there a way to find which actual repo I hit with:
(at any given run on it)

http://deb.devuan.org/merged
http://de.deb.devuan.org/merged

(of course only one of those are used in any attempt)

EDIT2 (after a bit of digging):

$ curl -Is http://deb.devuan.org/merged | head -1
HTTP/1.1 301 Moved Permanently
$ curl -Is http://de.deb.devuan.org/merged | head -1
HTTP/1.1 301 Moved Permanently

As I understand it, that should be "200"
But then: why does it get the security updates and not the others?

Last edited by mclien (2025-11-08 11:55:28)

ralph.ronnquist · 2025-11-08 16:20:30

Can you post output of ls -l /etc/apt/sources.list*

rolfie · 2025-11-08 17:14:57

Updated my travelling laptop to Excalibur a few days ago. The upgrade went well what Devuan is concerned, have got some BIOS-related UEFI-hickup. Sources have been modernized today.

The original sources.list reads like this:

deb http://deb.devuan.org/merged excalibur main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged excalibur-security main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged/ excalibur-updates main contrib non-free non-free-firmware
deb http://deb.devuan.org/merged/ excalibur-backports main contrib non-free non-free-firmware

No issues neither with apt nor apt-get.

Modernize generated two files in /etc/apt/sources.list.d with the following contents:

devuan.sources:

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur-security
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur-updates
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

devuan-backports.sources:

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur-backports
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

Backports was missing the key, I just added the line from devuan.sources. As well apt as apt get work:

# apt update
OK:1 http://deb.devuan.org/merged excalibur InRelease
OK:2 http://deb.devuan.org/merged excalibur-security InRelease
OK:3 http://deb.devuan.org/merged excalibur-updates InRelease
OK:4 http://deb.devuan.org/merged excalibur-backports InRelease
Alle Pakete sind aktuell.                   
# apt-get update
OK:1 http://deb.devuan.org/merged excalibur InRelease
OK:2 http://deb.devuan.org/merged excalibur-security InRelease
OK:3 http://deb.devuan.org/merged excalibur-updates InRelease
OK:4 http://deb.devuan.org/merged excalibur-backports InRelease
Paketlisten werden gelesen… Fertig

Then I moved everything into one block in one file (devuan.sources) and set devuan-backports.sources to Enabled: no:

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: excalibur excalibur-security excalibur-updates excalibur-backports
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

Same result with apt and apt.get as before, works fine.

I use geany to edit the files. And I avoid de.deb.devuan.org. I just use the general round robin. There were some problems a while ago, recently I haven't seen any issues.

# ls -l /etc/apt/sources.list*
-rw-r--r-- 1 root root    0 14. Sep 2022  /etc/apt/sources.list~
-rw-r--r-- 1 root root  545  6. Nov 18:58 /etc/apt/sources.list.bak

/etc/apt/sources.list.d:
insgesamt 8
-rw-rw-r-- 1 root root 237  8. Nov 17:50 devuan-backports.sources
-rw-rw-r-- 1 root root 731  8. Nov 17:50 devuan.sources

I can't complain.

mclien · 2025-11-08 18:57:46

$ ls -l /etc/apt/sources.list*
-rw-r--r-- 1 root root 1104 Nov 12  2023 /etc/apt/sources.list_daedalus
 
/etc/apt/sources.list.d:
total 4
-rw-r--r-- 1 root root 1603 Nov  7 21:21 devuan.sources

I have somewhat erratic behaviour on both
deb.devuan.org and
de.deb.devuan.org

Last edited by mclien (2025-11-08 19:02:03)

mclien · 2025-11-08 20:27:30

Did a bit of experimenting.
I just did a:

traceroute deb.devuan.org

several times, which gave me quite different results from
"nework not reachable" to
ending with the (default) 30 hops, with no reached server
and some quick responses, from which I picked the fastest one with the fewest hops.

then I searched this:
https://pkgmaster.devuan.org/mirror_list.txt
with the domain name of that reply.
I exchanged the found mirror with the "deb.devuan.org" in devuan.sources.

Now I get hits on all suits without any fail so far.

Maybe something in my WAN setup is blocking things (or my ISP does)

Last edited by mclien (2025-11-08 20:30:23)

ralph.ronnquist · 2025-11-08 23:07:48

It appears your /etc/apt/sources.list.d/devuan.sources have blank lines that are not empty, but each contains a single space character. Therefore that whole file becomes treated as a single block of key: value pairs, where the last one for each key overrides all other.

I don't know which which editor you use to accomplish that single-space-character blank lines, but if you run the following command it will be happier:

sed 's/^\s*$//' -i /etc/apt/sources.list.d/devuan.sources

You can verify that the file is slightly smaller after the command, and if you first copy the file to /tmp/OLD you can compare them with diff or meld to see what I talked about already some posts ago.

mclien · Yesterday 10:24:21

Not the case here. Both versions have the same size.
I insert blank lines with the "o" command of vi, followed by [ESC], so no characters in those lines.

Still think something might be amiss with my nameserver, see my post #23
(replacing the deb.devuan.org with single mirror, which gave me a good result with traceroute, works fine)

Darn! you were right. I am notoriously copy and pasting with left/middle mouse button.
Turns our, if you open the working file in one vi, mark it there and drop that into another open vi, it will add the mentioned (by ralph.ronnquist) spaces in blank lines.

Sorry for being an annoyance.

Last edited by mclien (Yesterday 17:59:55)

The officially official Devuan Forum!

#1 2025-11-04 14:40:54

[SOLVED] dist upgrade to excalibur hits only security packages

#2 2025-11-04 15:36:38

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#3 2025-11-04 17:11:10

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#4 2025-11-04 17:17:51

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#5 2025-11-04 17:23:56

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#6 2025-11-04 17:34:29

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#7 2025-11-04 17:40:23

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#8 2025-11-04 17:46:52

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#9 2025-11-04 17:51:34

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#10 2025-11-04 18:09:48

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#11 2025-11-04 18:14:10

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#12 2025-11-04 18:27:15

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#13 2025-11-04 18:30:21

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#14 2025-11-04 18:35:19

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#15 2025-11-04 22:35:35

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#16 2025-11-05 13:10:04

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#17 2025-11-05 18:44:47

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#18 2025-11-07 20:45:16

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#19 2025-11-08 11:42:54

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#20 2025-11-08 16:20:30

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#21 2025-11-08 17:14:57

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#22 2025-11-08 18:57:46

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#23 2025-11-08 20:27:30

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#24 2025-11-08 23:07:48

Re: [SOLVED] dist upgrade to excalibur hits only security packages

#25 Yesterday 10:24:21

Re: [SOLVED] dist upgrade to excalibur hits only security packages

Board footer