The repository 'https://archive.neon.kde.org noble Release' does not have a Release file

runlevel0 · January 6, 2025, 8:44pm

Since a month or ago or so, I get this weird error message:

unlevel0@thinkpad:~/work$ sudo apt update
[sudo] password for runlevel0: 
Get:1 https://archive.neon.kde.org/release noble InRelease [198 kB]
Hit:2 https://app.eduvpn.org/linux/v4/deb oracular InRelease               
Get:3 https://security.ubuntu.com/ubuntu noble-security InRelease [126 kB] 
Ign:4 https://archive.neon.kde.org noble InRelease                         
Err:5 https://archive.neon.kde.org noble Release                           
  404  Not Found [IP: 2a02:6ea0:c700::19 443]
[...]
Reading package lists... Done                                          
E: The repository 'https://archive.neon.kde.org noble Release' does not have 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.

The weird part: I have visited the URL and both, the http and the https ones are correct and the entry in the sources.list looks OK.

Note that the only edit on the sources.list files is that I have changed http for https, but that had null effect. None, niente, nada.

I did download and import the GPG signatures, both by downloading it to my drive and by using wget to import it remotely.

Here I get another weird result that I haven’t been able to pinpoint either:

runlevel0@thinkpad:~/Downloads$ gpg --import Release.gpg 
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0

It would make sense if it meant that the GPG signature was wrong. I don’t understand how this could be related to a HTTP 404 error, but I have seen a few issues with Debian-based distros failing with a 404 because one of the signatures was not found.

I do think that this is some issue with the repo itself, but I find it pretty weird that nobody else has noticed it. Well, maybe there aren’t these many KDE Neon users to begin with…

I am not sure if this issue is having any effect, and I am missing out important new Plasma updates (the Ubuntu updates work though), in which case I may have to think on jumping to a more mainstream distro (Arch, OpenSuSE Tumbleweed, whichever carries Plasma6).

Here’s my KDE version stuffz:

My KDE version

Operating System: KDE neon 6.2
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.8.0-51-generic (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 520
Manufacturer: LENOVO
Product Name: 20K5S4A901
System Version: ThinkPad X270 W10DG

Anybody has any ideas? May the KDE guys be up to some overhaul and forgot to update the GPG signature? Or is there anything else going on?

claydoh · January 6, 2025, 11:02pm

Probably a local system issue or network thing? Or a temporary problem somewhere along the line?

There are plenty of neon users, and there would definitely be many mentions and complaints if this was a non-local problem. Zero issues for any of my 3 systems here at two different locations, using different ISPs.

EDIT:

Actually, I think that your repo line may be incorrect.
The URL should not be:

https://archive.neon.kde.org/release

But should be

https://archive.neon.kde.org/user

Yes, there is a section in neon’s archive archive called “release”, but that is not used for production purposes.

I have no idea how or why you would be using this instead of user, unless you were testing something in the past and didn’t change it back, maybe?

You should just be able to edit
/etc/apt/sources.list.d/neon.sources

change ‘release’ to ‘user’ and try updating again.

The confusing part is that apt repos have a release file present in them so the error message is confusing, and I did not catch this at first.

claydoh · January 6, 2025, 11:18pm

I also think you may have a separate source file for this “Release” repo, instead, since you do have the current Plasma already installed.
6.2.5 just came out in the past week, which you would not have received this if you were only using the ‘release’ repo and not the correct “user” repo, since it has not been used for about a month.

Look in your /etc/apt/sources.list.d directory for duplicate content in any of the files – particularly a neon.list file perhaps.

Aranjedeath · January 7, 2025, 1:53am

two small followup questions: can you paste us at least the neon-relevant lines from your sources.list that you changed?

additionally, can you let us know if there are any neon.list or neon.sources in /etc/apt/sources.list.d/ and if yes, what are the contents of those files

Thank you.

runlevel0 · January 10, 2025, 6:04pm

@claydoh I changed the line from http to https to test if the issue persisted.
But there was no change.

I also think it’s local, but I wanted to ask first, not that I dismantle the whole system and I found out later that the issue was resolved by the maintainers and I had wasted my time. Wouldn’t have been the first time

Thanks !

runlevel0 · January 10, 2025, 6:44pm

Here, that’s /etc/apt/sources.list.d

runlevel0@thinkpad:/etc/apt/sources.list.d$ ls -l
total 20
-rw-r--r-- 1 root root 115 Dec 31 17:03 eduvpn-v4.list
-rw-r--r-- 1 root root  71 Dec 31 17:03 neon.list
-rw-r--r-- 1 root root 172 Jan  6 13:22 neon.sources
-rw-r--r-- 1 root root 209 Dec  1 08:50 org.kde.neon.packages.mozilla.org.sources
-rw-r--r-- 1 root root 124 Dec 24 22:16 preinstalled-pool.sources
runlevel0@thinkpad:/etc/apt/sources.list.d$

eduvpn-v4 is an app for a European academic VPN, the repo loads just fine.

the only line I changed in /etc/apt/sources.list is :

deb https://archive.neon.kde.org/release/ noble main

I added an “s” to make it https instead.
I did that because I was able to access the URL so that I knew it existed.

But it produces the same error with our without the “s”

Thanks and best wishes for 2025

claydoh · January 11, 2025, 12:48am

The issue still is that you have the wrong URL for the unused “release” pocket of the archives, instead of the User.

This pocket is used as a staging area waiting for all packages to be built and pushed out to User section of the archive when things are ready and complete. Using this can cause problems if there are packages missing/waiting.

I modified my repos to use Release, and do not see the error you are, but still, this should be fixed. You have the incorrect URL in either your neon.list or your neon.sources file. The former should not have any url but just messaging that the correct location has moved.

/etc/apt/sources.list.d/neon.list:

# KDE neon sources have moved to /etc/apt/sources.list.d/neon.sources`

and
/etc/apt/sources.list.d/neon.sources:

X-Repolib-Name: KDE neon noble user
Types: deb deb-src
URIs: http://archive.neon.kde.org/user
Suites: noble
Components: main
Signed-By: /etc/apt/keyrings/neon-archive-keyring.asc

It might also be wise to check your /etc/apt/sources.list (if present) as well as /etc/apt/sources.list.d/ubuntu.sources if you have that one instead.

claydoh · January 11, 2025, 12:58am

This is the issue. This line doesn’t belong in the main sources.list file, and has the incorrect URL in it.

You already have the correct source file at /etc/apt/sources.list.d/neon.sources.

Remove that line from /etc/apt/sources.list if your other files match what I posted above.

Sorry, I missed that when composing my previous reply.