Packages with security updates kept back

    • Official Post

    Is there a way to just reset all of my apt sources and apt preferences to the defaults for OMV 7?

    sudo rm -v /etc/apt/sources.list.d/*

    sudo find /etc/apt/preferences.d/ -type f ! -name 'openmediavault-local.pref' -print -delete

    sudo omv-salt deploy run apt

    sudo omv-aptclean repos

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    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!

  • sudo rm -v /etc/apt/sources.list.d/*

    sudo find /etc/apt/preferences.d/ -type f ! -name 'openmediavault-local.pref' -print -delete

    sudo omv-salt deploy run apt

    sudo omv-aptclean repos

    Thanks, I tried this but unfortunately no change.

  • Maybe the output of the following commands is helpful:

    Code
    cat /etc/apt/apt.conf.d/* | grep "APT::Default-Release"

    and

    Code
    apt-cache policy

    Thank you, the first command returned nothing. The second one:


    • Official Post

    I tried this but unfortunately no change.

    Output would be helpful. We can't see your system.


    Your system still has the regular debian repo pinned at 990. omv and omv-extras are not doing this and it is causing the problem. What is the output of: ls -al /etc/apt/preferences.d/

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    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!

  • Output would be helpful. We can't see your system.


    Your system still has the regular debian repo pinned at 990. omv and omv-extras are not doing this and it is causing the problem. What is the output of: ls -al /etc/apt/preferences.d/

    Code
    total 16
    drwxr-xr-x  2 root root 4096 Jul 11 19:48 .
    drwxr-xr-x 14 root root 4096 Feb 21 20:28 ..
    -rw-r--r--  1 root root  299 Jul 11 19:47 openmediavault-kernel-backports.pref
    -rw-r--r--  1 root root   44 May  4  2017 openmediavault-local.pref
    • Official Post

    That doesn't make much sense. What about: sudo grep -r 990 /etc/apt/*

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    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!

  • That doesn't make much sense. What about: sudo grep -r 990 /etc/apt/*

    returns nothing. Is that bad? This is the contents of /etc/apt:


    • Official Post

    Is that bad?

    It isn't good because it pins the regular debian repo packages higher than the debian security repo packages. I don't know how it is doing that based the output you have given me. The only ways I know to pin a repo/package are in /etc/apt/

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    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!

    • Official Post

    Can you post the output of:


    sudo apt-mark showhold

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    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!

    • Official Post

    No output for that one.

    I have zero ideas on how that repo is pinned like that then.

    I would be a second test-person with the same problem and the same outputs here. Perhaps it aligns with the mergerfs-problem I had days ago

    Yes, you have the same debian issue pinned at 990 issue. OMV and omv-extras are not doing this though. And based on output I have asked for, I don't know how it can possibly be pinned at 990. Unless someone wants to send me an image of their OS disk, someone with the issue is going to have to figure it out.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    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!

  • There seems to be some exotic apt configuration here. Can we see the whole output of head -vn -0 /etc/apt/apt.conf.d/* and cat /etc/apt/apt.conf andecho $APT_CONFIG?


    Also maybe cat /etc/apt/preferences and head -vn -0 /etc/apt/preferences.d/*.


    If none of this has helpful output, I am out of ideas as well.

  • I have zero ideas on how that repo is pinned like that then.

    Yes, you have the same debian issue pinned at 990 issue. OMV and omv-extras are not doing this though. And based on output I have asked for, I don't know how it can possibly be pinned at 990. Unless someone wants to send me an image of their OS disk, someone with the issue is going to have to figure it out.

    I'm also stumped, I searched for the number 990 in the entirety of /etc/apt and it doesn't appear anywhere. I have no idea where it could be getting that priority from.

  • There seems to be some exotic apt configuration here. Can we see the whole output of head -vn -0 /etc/apt/apt.conf.d/* and cat /etc/apt/apt.conf andecho $APT_CONFIG?


    Also maybe cat /etc/apt/preferences and head -vn -0 /etc/apt/preferences.d/*.


    If none of this has helpful output, I am out of ideas as well.

    Here you go:

    Code
    root@joe:~# cat /etc/apt/apt.conf
    APT::Default-Release "bookworm";
    Code
    root@joe:~# echo $APT_CONFIG
    Code
    root@joe:~# cat /etc/apt/preferences
    cat: /etc/apt/preferences: No such file or directory
  • Code
    root@joe:~# cat /etc/apt/apt.conf
    APT::Default-Release "bookworm";

    That's your problem. Where does this file come from? This sets bookworm as target release (priority 990) and prevents packages from bookworm-security from being installed: https://wiki.debian.org/AptCon…with_APT::Default-Release


    Removing this file (/etc/apt/apt.conf) should solve your problem.

    • Official Post

    Removing this file (/etc/apt/apt.conf) should solve your problem.

    Thanks for finding that!

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    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!

    • Official Post

    That's your problem. Where does this file come from? This sets bookworm as target release (priority 990) and prevents packages from bookworm-security from being installed: https://wiki.debian.org/AptCon…with_APT::Default-Release


    Removing this file (/etc/apt/apt.conf) should solve your problem.

    Thanks for your investigation.


    The issue will be fixed in next version, see https://github.com/openmediava…42c957a7f0efae4bbee7931ed.

Participate now!

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