Bug#1033592: Command "apt-get --target-release ..." may not work when "Pin-Priority" higher than 990 is used in "/etc/apt/preferences"

A workaround I use currently is: apt download $(sed --regexp-extended 's/^(.+)$/\1\/SUITE/' PACKAGES.txt) where "SUITE" is for example "sid" or "stable". Regards, Jmkr

Bug#1033592: Command "apt-get --target-release ..." may not work when "Pin-Priority" higher than 990 is used in "/etc/apt/preferences"

I just forgot to add that, at least according to APT-GET(8), priority 990 is used also in the current stable, testing and unstable versions: Package: apt Version: 2.2.4 Version: 2.6.0 Regards, Jmkr

Bug#1033592: Command "apt-get --target-release ..." may not work when "Pin-Priority" higher than 990 is used in "/etc/apt/preferences"

Package: apt Version: 1.8.2.3 Severity: minor Dear Maintainers, on my system (Debian 10 with some backports) I have pinned most packages to Debian Buster with priority 1000 (in "/etc/apt/preferences"). This is my attempt to handle unattended upgrades upgrading a package that had the same