Debian repositories no longer have "Release file"

    Attempting to get my server up-to-date to upgrade to version 6 and I'm encountering errors when using `omv-upgrade` related to repositories.

    There are other similar issues on the forum, but not exactly like this. None have clear resolution steps printed either.




    Here's `/etc/apt/sources.list`:

    Code: /etc/apt/sources.list
    deb http://deb.debian.org/debian/ stretch main contrib non-free
deb http://deb.debian.org/debian/ stretch-updates main contrib non-free
deb http://deb.debian.org/debian-security stretch/updates main contrib non-free

# deb cdrom:[Debian GNU/Linux 10 _Buster_ - Official Snapshot amd64 LIVE/INSTALL Binary 20200921-17:33]/ buster contrib main non-free

# deb cdrom:[Debian GNU/Linux 10 _Buster_ - Official Snapshot amd64 LIVE/INSTALL Binary 20200921-17:33]/ buster contrib main non-free

# Line commented out by installer because it failed to verify:
# Line commented out by installer because it failed to verify:


    and here's `/etc/apt/sources.list.d/openmediavault.list`:

    Code: /etc/apt/sources.list.d/openmediavault.list
    deb http://packages.openmediavault.org/public/ usul main
deb https://openmediavault.github.io/packages/ usul main
# deb http://downloads.sourceforge.net/project/openmediavault/packages/ usul main

    I love computers. They make everything so much easier! :)

  • chente

    Hat das Thema freigeschaltet.

    OMV 5 is based on Debian 10 for which support ended on 10 Sep 2022. At that time its repositories were subject to being shuttered. This makes the usual update procedures infeasible.


    It might be possible to "convert" all the update scripts/programs to use the Debian 10 Long Term Support (LTS) repositories but I have no idea if anyone has even contemplated trying this.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Wowee, what a hassle.


    First I had to update`/etc/apt/sources.list` as follows, pointing to the archive repos for Debian 9 (`stretch`):


    Then I could run `apt update`, which prompted me to accept a change in 'Suite' value:

    Code
    E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'oldstable' to 'oldoldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] Y

    Then I received this error (which had been showing up before, but at this point they were the only remaining errors):

    Code
    W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://httpredir.debian.org/debian buster-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131


    To resolve, I first needed to run

    Code
    apt install gnupg1

    which allowed me to run these `apt-key` commands to get the public keys (apt-key ofc is deprecated, but we do what we must to avoid having to re-install this server from scratch):


    This now has `omv-upgrade` (and apt) down to this error:

    Code
    E: The repository 'https://archive.debian.org/debian stretch-updates 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.

    Digging deeper I realized that `stretch-updates` doesn't exist in the archive repo (makes sense), so I commented it out in sources.list, making my final sources.list:

    Now running `omv-upgrade` works!


    After a reboot, I was able to run `omv-release-upgrade` (I was on OMV 5.6.26.x). However, nothing ends up changing. Will need to double post to share the results from that.

    I love computers. They make everything so much easier! :)

    Zitat von gderf

    OMV 5 is based on Debian 10 for which support ended on 10 Sep 2022. At that time its repositories were subject to being shuttered. This makes the usual update procedures infeasible.


    It might be possible to "convert" all the update scripts/programs to use the Debian 10 Long Term Support (LTS) repositories but I have no idea if anyone has even contemplated trying this.

    I've managed to make a lot of progress, see previous post.


    Current results of `omv-release-upgrade`:

    I love computers. They make everything so much easier! :)

    SUCCESS! I'm now on OMV 6.9.12-2, having updated from OMV 5.6.26.


    This is a summary of the steps I took to resolve my issues. Here's hoping it helps anyone else with the same or similar issues.


    Issue 1: Debian `stretch` repositories have moved

    My `/etc/apt/sources.list` had three repositories in it, all of which threw errors when attempting to use `omv-upgrade` or any apt-based upgrade.

    Code: Original /etc/apt/sources.list
    deb http://deb.debian.org/debian/ stretch main contrib non-free
deb http://deb.debian.org/debian/ stretch-updates main contrib non-free
deb http://deb.debian.org/debian-security stretch/updates main contrib non-free

    I replaced these three out-of-date repositories with their archived locations:

    Code: Modified /etc/apt/sources.list
    deb https://archive.debian.org/debian/ stretch main contrib non-free
deb https://archive.debian.org/debian-security/ stretch/updates main contrib non-free

    Note that `stretch-updates` no longer exists and is not needed.


    Making these changes addressed the first set of errors regarding repositories missing a "Release" file. This error message was misleading because the real issue was that the repositories didn't exist at all, because they had been moved to the Debian archive.


    At this point, run `apt update` and accept the prompt below:

    Code
    E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'oldstable' to 'oldoldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] Y

    Issue 2: Add missing public keys used by repositories

    After running `apt update` and accepting the prompt, we still get the following error:

    Code
    W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://httpredir.debian.org/debian buster-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131

    To resolve this, we first need to install `gnupg1`(not `gnupg` nor `gnupg2`)

    Code
    apt install gnupg1

    After which, we can add the missing keys. Run these two commands:

    Code
    apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 0E98404D386FA1D9
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 6ED0E7B82643E131

    This adds the missing keys.


    Make the currently installed version up-to-date

    At this point, we can run `omv-upgrade` without errors. Run it, restart your computer. Run it again. Keep running it until it stops installing things.


    Finally: Let's upgrade to OMV 6

    After running `omv-upgrade`, it should be on the final version of OMV 5. This gives access to the `omv-release-upgrade` script, but it won't work with the archive repos we set up earlier. Time to edit `/etc/apt/sources.list` again!


    Change `/etc/apt/sources.list` to point to the mainline buster (Debian 10) repos:

    Code
    deb http://deb.debian.org/debian/ buster main contrib non-free
deb http://deb.debian.org/debian/ buster-updates main contrib non-free

    At this point, run `omv-release-upgrade`. It'll run for a while, then you need to restart. Congrats! You're now on OMV 6 (if you have the same set of issues that I did, anyway).

    I love computers. They make everything so much easier! :)

    Gefällt mir 2

  • chente

    Hat das Label gelöst hinzugefügt.
    • Neu
    Zitat von ilovecomputers

    SUCCESS! I'm now on OMV 6.9.12-2, having updated from OMV 5.6.26.

    Unfortunately it is still saying that there is no release file:


    Code
    Reading package lists... Done
E: The repository 'http://httpredir.debian.org/debian buster-backports 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.

    Me sources file looks like this:

    Any advice?

    • Neu
    Zitat von gio_kiborg

    Unfortunately it is still saying that there is no release file:


    Code
    Reading package lists... Done
E: The repository 'http://httpredir.debian.org/debian buster-backports 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.

    Me sources file looks like this:

    Any advice?

    Currently dealing with the same issue...

    I think the problem with the error The repository 'http://httpredir.debian.org/debian buster-backports Release' no longer has a Release file. comes from this source in /etc/apt/sources.list.d/openmediavault-kernel-backports.list which contains the following entry:

    Code
    deb http://httpredir.debian.org/debian buster-backports main contrib non-free

    But I am myself unsure on how to proceed as I am a full novice on this field and am not in the mood of bricking my (admittedly fragile) setup.

    OP or any of the mods willing to help us out?


    Edit: I had backports active in my omv-extras settings
    Got it from here: Disabling only kernel backports?

    The definition of a lurker ^^


    Main NAS: Raspberry Pi 4b 4GB with Docker on Raspberry OS Buster

    Backup NAS: Raspberry Pi 4b 4GB with Docker on Raspberry OS Buster


    Syncing Backup with Main over Rsync (just the NAS files) because no USB Raid :saint:

    Einmal editiert, zuletzt von Appoxo () aus folgendem Grund: Update to my problem

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden