dist upgrade to excalibur hits only security packages

mclien · Yesterday 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.

rolfie · Yesterday 15:36:38

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

Last edited by rolfie (Yesterday 17:13:56)

mclien · Yesterday 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 (Yesterday 17:20:22)

rolfie · Yesterday 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 · Yesterday 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 (Yesterday 17:24:30)

mclien · Yesterday 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 · Yesterday 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 · Yesterday 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 (Yesterday 17:50:48)

rolfie · Yesterday 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 (Yesterday 18:41:06)

rolfie · Yesterday 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 · Yesterday 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 (Yesterday 18:37:33)

rolfie · Yesterday 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 · Yesterday 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 · Yesterday 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 (Yesterday 18:44:12)

ralph.ronnquist · Yesterday 22:35:35

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

mclien · Today 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 (Today 13:34:08)

The officially official Devuan Forum!

#1 Yesterday 14:40:54

dist upgrade to excalibur hits only security packages

#2 Yesterday 15:36:38

Re: dist upgrade to excalibur hits only security packages

#3 Yesterday 17:11:10

Re: dist upgrade to excalibur hits only security packages

#4 Yesterday 17:17:51

Re: dist upgrade to excalibur hits only security packages

#5 Yesterday 17:23:56

Re: dist upgrade to excalibur hits only security packages

#6 Yesterday 17:34:29

Re: dist upgrade to excalibur hits only security packages

#7 Yesterday 17:40:23

Re: dist upgrade to excalibur hits only security packages

#8 Yesterday 17:46:52

Re: dist upgrade to excalibur hits only security packages

#9 Yesterday 17:51:34

Re: dist upgrade to excalibur hits only security packages

#10 Yesterday 18:09:48

Re: dist upgrade to excalibur hits only security packages

#11 Yesterday 18:14:10

Re: dist upgrade to excalibur hits only security packages

#12 Yesterday 18:27:15

Re: dist upgrade to excalibur hits only security packages

#13 Yesterday 18:30:21

Re: dist upgrade to excalibur hits only security packages

#14 Yesterday 18:35:19

Re: dist upgrade to excalibur hits only security packages

#15 Yesterday 22:35:35

Re: dist upgrade to excalibur hits only security packages

#16 Today 13:10:04

Re: dist upgrade to excalibur hits only security packages

Board footer