Apt warnings after update OMV to 5.6.3

  • Code
    All packages are up to date.
    W: Target Sources (main/source/Sources) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/openmediavault-os-security.list:2
    W: Target Sources (contrib/source/Sources) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/openmediavault-os-security.list:2
    W: Target Sources (non-free/source/Sources) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/openmediavault-os-security.list:2
    W: Target Sources (main/source/Sources) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/openmediavault-os-security.list:2
    W: Target Sources (contrib/source/Sources) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/openmediavault-os-security.list:2
    W: Target Sources (non-free/source/Sources) is configured multiple times in /etc/apt/sources.list:10 and /etc/apt/sources.list.d/openmediavault-os-security.list:2
    root@omv:~#
  • I bet this is related to the new feature in 5.6.3.1 that allows OMV to install security updates automatically.

    It's probably safe to ignore these warnings until a fix is forthcoming, unless you feel adventurous and want to edit /etc/apt/sources.list ...

  • The update should have removed the security repo from /etc/apt/sources.list and put it in /etc/apt/sources.list.d/openmediavault-os-security.list.


    Does: sudo omv-salt deploy run apt fix it?

    omv 5.6.4 usul | 64 bit | 5.11 proxmox kernel | omvextrasorg 5.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • The update should have removed the security repo from /etc/apt/sources.list and put it in /etc/apt/sources.list.d/openmediavault-os-security.list.


    Does: sudo omv-salt deploy run apt fix it?

    Not for me.


    This what it said afterwards:


    But when doing another apt update the error is still there.

    Usul 5.5.23-1

    running in Proxmox on

    Mobo: Asus H87I-Plus (C2) Socket 1150
    RAM: 8GB (2x 4096MB) Kingston ValueRAM DDR3-1600 DIMM CL11 Single
    CPU: Intel Pentium G3220 2x 3.00GHz So.1150 BOX
    PS: 300 Watt be quiet! System Power 7 Bulk Non-Modular 80+ Bronze
    OS: 64GB SanDisk Solid State Disk (SDSSDP-064G-G25)
    Data: 2x 4000GB WD Red WD40EFRX
    Case: Chenbro SR30169 mini ITX (4 bay) - but removed that crappy backplane :)

  • Confirmed. I ran the same omv-salt deploy run apt command followed by apt update, and it still happened.


    Went to edit /etc/apt/sources.list, commenting out line 10 (the security updates repo), ran the above commands again, and now it's fixed.


    But will the change to sources.list stick, or will OMV eventually overwrite it?

  • Went to edit /etc/apt/sources.list, commenting out line 10 (the security updates repo), ran the above commands again, and now it's fixed.

    This is my plan B but I wanted to check first if maybe there is something like a "OMV solution".

    Usul 5.5.23-1

    running in Proxmox on

    Mobo: Asus H87I-Plus (C2) Socket 1150
    RAM: 8GB (2x 4096MB) Kingston ValueRAM DDR3-1600 DIMM CL11 Single
    CPU: Intel Pentium G3220 2x 3.00GHz So.1150 BOX
    PS: 300 Watt be quiet! System Power 7 Bulk Non-Modular 80+ Bronze
    OS: 64GB SanDisk Solid State Disk (SDSSDP-064G-G25)
    Data: 2x 4000GB WD Red WD40EFRX
    Case: Chenbro SR30169 mini ITX (4 bay) - but removed that crappy backplane :)

  • But when doing another apt update the error is still there.

    Well, it seems it removes the security repository from /etc/apt/sources.list.d/openmediavault-os-security.list and then re-adds it to the same file. So there is no attempt above to remove the securiry repository from /etc/apt/sources.list to fix the issue. Thus, the error is the same.

  • If you are on 5.6.3, it should remove it. Here is the code - https://github.com/openmediava…ploy/apt/default.sls#L104 THat said, it should be a one time fix.

    I'm on 5.6.3.1 and it is still present, just checked it a minute ago.

    Not a big issue though, I'm just mentioning it for the records.

    Well, it seems it removes the security repository from /etc/apt/sources.list.d/openmediavault-os-security.list and then re-adds it to the same file. So there is no attempt above to remove the securiry repository from /etc/apt/sources.list to fix the issue. Thus, the error is the same.

    Thanks for the clarification! :thumbup:

    I would just go ahead and do it. My guess is the "OMV solution" will be a future update (bug fix).

    I will do so once it bothers me enough ;)



    As mentioned already: I guessed how to solve this (and was confirmed by you), I was just curious wether I'm the only one and thought I added my comment, maybe this is helpful to the dev's.

    Usul 5.5.23-1

    running in Proxmox on

    Mobo: Asus H87I-Plus (C2) Socket 1150
    RAM: 8GB (2x 4096MB) Kingston ValueRAM DDR3-1600 DIMM CL11 Single
    CPU: Intel Pentium G3220 2x 3.00GHz So.1150 BOX
    PS: 300 Watt be quiet! System Power 7 Bulk Non-Modular 80+ Bronze
    OS: 64GB SanDisk Solid State Disk (SDSSDP-064G-G25)
    Data: 2x 4000GB WD Red WD40EFRX
    Case: Chenbro SR30169 mini ITX (4 bay) - but removed that crappy backplane :)

  • I have the same problem trying to upgrade to openmediavault (5.6.4-1).

    Setting up Salt environment ...

    Processing system modifications ...

    dpkg: error processing package openmediavault (--configure):

    installed openmediavault package post-installation script subprocess returned error exit status 1

    Errors were encountered while processing:

    openmediavault

    E: Sub-process /usr/bin/dpkg returned an error code (1)


    Any way to fix this error?

  • I have the same problem trying to upgrade to openmediavault (5.6.4-1).

    No, you don't have the same problem. While the thread is about having a repository listed multiple times as APT source, your's is that the postinst script fails in the configure target. So please start a new thread.

  • Hi all,


    same issue here with teamviewer repo from today morning:

    EDIT:

    now i see i have the same sources in 2 lists, where should i remove them?

    omv 5.6 in proxmox 6.3-6 - AMD Ryzen 1700 - 16GB DDR4 :thumbup:

    Edited 2 times, last by Mio ().

  • now i see i have the same sources in 2 lists, where should i remove them?

    Remove it in /etc/apt/sources.list. As was written above:

    The update should have removed the security repo from /etc/apt/sources.list and put it in /etc/apt/sources.list.d/openmediavault-os-security.list.


    My (working) files look like this now:

    Code
    # cat /etc/apt/sources.list
    deb http://deb.debian.org/debian buster main contrib non-free
    deb-src http://deb.debian.org/debian buster main contrib non-free
    deb http://security.debian.org/ buster/updates main contrib non-free
    deb-src http://security.debian.org/ buster/updates main contrib non-free
    deb http://deb.debian.org/debian buster-updates main contrib non-free
    deb-src http://deb.debian.org/debian buster-updates main contrib non-free
    Code
    # cat /etc/apt/sources.list.d/openmediavault-os-security.list
    deb http://security.debian.org/debian-security buster/updates main contrib non-free
    deb-src http://security.debian.org/debian-security buster/updates main contrib non-free
  • You still have the security repo in /etc/apt/sources.list. That needs to be removed.

    omv 5.6.4 usul | 64 bit | 5.11 proxmox kernel | omvextrasorg 5.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • Hi all,


    same issue here with teamviewer repo from today morning:

    EDIT:

    now i see i have the same sources in 2 lists, where should i remove them?

    The other task, regarding

    Code
    E: Failed to fetch http://linux.teamviewer.com

    is solved in here

Participate now!

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