Bug 403790

Summary: Update failure: archive is not yet available?
Product: [KDE Neon] neon Reporter: Nate Graham <nate>
Component: Packages Unstable EditionAssignee: Neon Bugs <neon-bugs>
Status: RESOLVED NOT A BUG    
Severity: normal CC: fundatillus, jr, neon-bugs, sitter
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Archive is not yet available error
`pkmon` log of update progress

Description Nate Graham 2019-01-31 03:59:05 UTC
Created attachment 117754 [details]
Archive is not yet available error

I tried to update my Neon Dev Unstable VM today and repeatedly got the following error message (see attached screenshot) from Discover. This reproduced four times.
Comment 1 Nate Graham 2019-01-31 03:59:32 UTC
Created attachment 117755 [details]
`pkmon` log of update progress
Comment 2 Nate Graham 2019-02-03 16:38:13 UTC
Looks fixed now.
Comment 3 Harald Sitter 2019-02-04 10:51:27 UTC
*** Bug 403870 has been marked as a duplicate of this bug. ***
Comment 4 fundatillus 2019-02-05 13:24:18 UTC
Still occurring as of Tue Feb  5 13:23:20 UTC 2019.
Comment 5 fundatillus 2019-02-05 13:27:32 UTC
Apt doesn't check for the Release file every time you run apt update, so this error seems intermittent. But it seems to happen every time apt checks for the Release file in http://archive.neon.kde.org/user. 

Err:26 http://archive.neon.kde.org/user bionic Release                                                                                                                                                                
  404  Not Found [IP: 195.181.169.22 80]
Reading package lists... Done
E: The repository 'http://archive.neon.kde.org/user bionic 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.
Comment 6 Harald Sitter 2019-02-05 13:33:31 UTC
Yup, unfortunately this isn't actually a bug in the software we can do anything about, something is awry with the servers. The KDE sysadmins are on it though.