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

    Approved the thread.
  • 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! :)

  • 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! :)

  • chente

    Added the Label resolved
  • 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?

    OMV 7.2.1-1 (Sandworm) | x86-64 |

  • 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:

    Edited once, last by Appoxo: Update to my problem ().

  • I also have this issue. Unlike ilovecomputers, my core setup isn't Stretch but Buster, with backports enabled in OMV 5. When I change the sources.lst file to point to the archive, I do NOT get the following option.

    Code
    Do you want to accept these changes and continue updating from this repository? [y/N


    Instead, when I run apt update, I get...

    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.

    This implies that during Buster, a change to apt update design happened and you can't force a redirect to the archive. Either way, I went through the updating the server encryption keys, just in case. I did that also with gnupg, not gnupg1 (as that cannot be found). No keys required updating.



    I would prefer to do this over https and not have to overide secure. With regards to the backports issue with the files location that Appoxo is showing, that with backports turned off and the main repository can be made to work with archive, that backports shouldn't been needed.

    Buster is still active under LTS, so SOMEWHERE, there should be a correct path to be able to use for both Debian Buster itself and OMV 5 can use, to get full access to Bookworm and OMV 6 and 7.

    The question is, what is it?

    • New
    • Official Post

    Buster is still active under LTS, so SOMEWHERE, there should be a correct path to be able to use for both Debian Buster itself and OMV 5 can use, to get full access to Bookworm and OMV 6 and 7.

    The question is, what is it?

    LTS/Using - Debian Wiki


    change the repo to https if you want.

    omv 7.4.0-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.1 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Buster is still active under LTS, so SOMEWHERE, there should be a correct path to be able to use for both Debian Buster itself and OMV 5 can use, to get full access to Bookworm and OMV 6 and 7.

    The question is, what is it?

    What exactly is the question?

    Or better yet, what issues are you having?


    If you are trying to move from OMV5 to 6 and, after 7, all you need is to:

    Make a proper working clone backup of the OS drive.


    OMV5:

    sudo omv-changebackports NO

    sudo omv-update


    Errors?!?

    Post the outputs inside CODE boxes and wait for help


    No errors:

    sudo omv-release-upgrade

    GOTO OMV6


    OMV6:

    Accept any changes on the GUI to be sure that all SALT modules get updated.

    wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix5to6upgrade | sudo bash

    sudo omv-upgrade


    Errors?!?

    Post the outputs inside CODE boxes and wait for help


    No errors:

    sudo omv-release-upgrade

    GOTO OMV7


    OMV7

    Accept any changes on the GUI to be sure that all SALT modules get updated.

    wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/fix6to7upgrade | sudo bash


    sudo omv-upgrade


    Errors?!?

    Post the outputs inside CODE boxes and wait for help


    No errors:

    Give yourself a pat on the back.

    You are on latest version

  • So, ryecoaaron , getting there. After the Debian repositories were changed to LTS, the file list within OMV5 as above started showing the LTS files. They all updated successfully and now have an empty list of required files.

    However, when OMV Check is used, it gives the following output, which looks like it can't find the OMV files specifically because those are in a different repository? At least, that's how it reads.

    Is there an archive / LTS repository for these files / where have they moved to?

    So close....

    Thanks


    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; apt-get update 2>&1' with exit code '100': Get:1 file:/var/cache/openmediavault/archives InRelease Ign:1 file:/var/cache/openmediavault/archives InRelease Get:2 file:/var/cache/openmediavault/archives Release Ign:2 file:/var/cache/openmediavault/archives Release Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Hit:5 http://deb.debian.org/debian buster InRelease Hit:6 http://security.debian.org buster/updates InRelease Hit:7 http://security.debian.org/debian-security buster/updates InRelease Hit:8 http://linux.teamviewer.com/deb stable InRelease Ign:9 http://httpredir.debian.org/debian buster-backports InRelease Err:10 http://httpredir.debian.org/debian buster-backports Release 404 Not Found [IP: 199.232.54.132 80] Hit:11 https://download.docker.com/linux/debian buster InRelease Hit:12 http://packages.openmediavault.org/public usul InRelease Get:13 https://openmediavault-plugin-developers.github.io/packages/debian usul InRelease [3928 B] Get:14 https://openmediavault.github.io/packages usul InRelease [12.7 kB] Get:15 https://openmediavault-plugin-developers.github.io/packages/debian usul-extras InRelease [3918 B] Reading package lists... E: The repository 'http://httpredir.debian.org/debian buster-backports Release' no longer has a Release file.
  • Hello Soma,

    The issue, as others have had in this thread is that given OMV5 had gone into LTS, when the usual update requests are being requested, the files weren't being found because the core system files no longer exist in the original repository.

    As you can see from my reply to ryecoaaron that although it appears Debian 10 itself now is fully up to date including security, OMV5's repository appears to have moved. I'd be very happy to hear your feedback with those OMV5 errors above.

    Thanks

    • New
    • Official Post

    The issue, as others have had in this thread is that given OMV5 had gone into LTS, when the usual update requests are being requested, the files weren't being found because the core system files no longer exist in the original repository.

    As you can see from my reply to ryecoaaron that although it appears Debian 10 itself now is fully up to date including security, OMV5's repository appears to have moved. I'd be very happy to hear your feedback with those OMV5 errors above.

    Actually Debian 10 went into LTS. OMV 5 is long EOL.


    The OMV 5 errors would be fixed by disabling all repos in omv-extras or just uninstalling omv-extras (reinstall on OMV 6).

    omv 7.4.0-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.1 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Soma , following on with the attempted upgrade from OMV 5 to 6, still cannot run update / upgrade.

    Followed ryecoaaron's suggestion, and removed OMV-Extras from the GUI and rebooted.
    I entered sudo omv-changebackports NO and got an error saying sudo: omv-changebackports: command not found

    Looking through the following thread, a recommendation to use usrmerge.
    OMV 5 to 6 - command not recognised

    Looked like usrmerge installed correctly.

    Rebooted again. In OMV5 GUI under Update Management, no new updates were listed. I clicked on Check, there was a twenty second wait and it came back with this error.


    Code
    Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; apt-get update 2>&1' with exit code '100': Get:1 file:/var/cache/openmediavault/archives InRelease Ign:1 file:/var/cache/openmediavault/archives InRelease Get:2 file:/var/cache/openmediavault/archives Release Ign:2 file:/var/cache/openmediavault/archives Release Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Ign:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:3 file:/var/cache/openmediavault/archives Packages Get:4 file:/var/cache/openmediavault/archives Translation-en Ign:4 file:/var/cache/openmediavault/archives Translation-en Get:5 http://security.debian.org buster/updates InRelease [34.8 kB] Ign:6 http://httpredir.debian.org/debian buster-backports InRelease Hit:7 http://deb.debian.org/debian buster InRelease Get:8 http://security.debian.org/debian-security buster/updates InRelease [34.8 kB] Hit:9 http://packages.openmediavault.org/public usul InRelease Err:10 http://httpredir.debian.org/debian buster-backports Release 404 Not Found [IP: 199.232.54.132 80] Get:11 https://openmediavault.github.io/packages usul InRelease [12.7 kB] Get:12 http://security.debian.org buster/updates/main Sources [383 kB] Get:13 http://security.debian.org buster/updates/main amd64 Packages [605 kB] Get:14 http://security.debian.org buster/updates/main Translation-en [327 kB] Get:15 http://security.debian.org/debian-security buster/updates/main Sources [383 kB] Get:16 http://security.debian.org/debian-security buster/updates/main amd64 Packages [605 kB] Get:17 http://security.debian.org/debian-security buster/updates/main Translation-en [327 kB] Reading package lists... E: The repository 'http://httpredir.debian.org/debian buster-backports Release' no longer has a Release file.

    The output from both echo $PATH and sudo echo $PATH is

    /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games

    Any suggestions on what I need to do next?

    Thanks

    BSG

  • Any suggestions on what I need to do next?

    Please, try to post the outputs with proper line breaks. Reading the code like that is a nightmare.


    attempted upgrade from OMV 5 to 6, still cannot run update / upgrade.

    You have been messing with the repos and it's difficult to keep up.

    Also install/doing things just because, makes things worst.


    So, starting from the beginning:


    Outputs of:

    dpkg -l | grep openm

    ls -al /usr/sbin/omv-*


    Now, find out where the repo http://httpredir.debian.org/debian buster-backports is mentioned and delete/comment it

    In

    cat /etc/apt/sources.list


    And/or on any of the list files under:

    ls -al /etc/apt/sources.list.d/


    Run and post the output of omv-update with line breaks, please.

    • New
    • Official Post

    Followed ryecoaaron's suggestion, and removed OMV-Extras from the GUI and rebooted.
    I entered sudo omv-changebackports NO and got an error saying sudo: omv-changebackports: command not found

    The omv-changebackports command is provided by omv-extras. Should've run it before running omv-extras. But you can just delete the backports file from /etc/apt/sources.list.d/.

    omv 7.4.0-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.14 | compose 7.2.1 | k8s 7.2.0-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.8


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Soma ,

    Output from dpkg -l | grep openm

    Code
    $ dpkg -l | grep openm
    ii  openmediavault                      5.6.26-1                            all                                                                        openmediavault - The open network attached storage solution
    ii  openmediavault-autoshutdown         5.1.21                              all                                                                        OpenMediaVault AutoShutdown Plugin
    ii  openmediavault-flashmemory          5.0.9                               all                                                                        folder2ram plugin for OpenMediaVault
    ii  openmediavault-keyring              1.0                                 all                                                                        GnuPG archive keys of the OpenMediaVault archive
    ii  openmediavault-resetperms           5.0                                 all                                                                        Reset Permissions


    Given non code view makes it easier to read, the same below.


    $ dpkg -l | grep openm

    ii openmediavault 5.6.26-1 all openmediavault - The open network attached storage solution

    ii openmediavault-autoshutdown 5.1.21 all OpenMediaVault AutoShutdown Plugin

    ii openmediavault-flashmemory 5.0.9 all folder2ram plugin for OpenMediaVault

    ii openmediavault-keyring 1.0 all GnuPG archive keys of the OpenMediaVault archive

    ii openmediavault-resetperms 5.0 all Reset Permissions

    $


    Output from ls -al /usr/sbin/omv-*

    I am progressing with the rest of your instructions.

    Thanks

    BSG

  • Given non code view makes it easier to read, the same below.

    I was refering the way the code of the failed command was on post #16


    Look at how it's showing:


    I am progressing with the rest of your instructions.

    Post any output you run (command and output) to keep track on how the system is going.


    The omv-changebackports command is provided by omv-extras.

    When he removed omv-extras, shouldn't it also have removed the other plugins he has, due to dependencies?

    Namely, flashmemory, autoshutdown and resetperms?

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!