Backports Priority
The pin-priority for jessie-backports should be decreased to prevent accidental flooding of backports packages upon update/upgrade. In Debian, it was set to 100 since wheezy or maybe squeeze.
-
agreed... but why is it different for us. As far as I know we've changed nothing that should effect this??
-
This is because
NotAutomatic: yes
andButAutomaticUpgrades: yes
are missing from Devuan release file:$ head -n 15 /var/lib/apt/lists/auto.mirror.devuan.org_merged_dists_jessie-backports_InRelease -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Origin: Devuan Label: jessie-backports Suite: jessie-backports Version: 1.0.0 Codename: jessie Date: Thu, 17 Nov 2016 22:31:28 UTC Valid-Until: Thu, 24 Nov 2016 22:31:28 UTC Architectures: alpha amd64 arm64 armel armhf hppa i386 ia64 mips mipsel powerpc ppc64el s390x sparc Components: main contrib non-freeMD5Sum: f18ab950857243675c384f7e31106cf7 26160 non-free/binary-amd64/Packages.xz 862f58bd69e3e2f722294a73e054369d 120 non-free/binary-amd64/Release 43f7166d54c25d6e45d03143ec9f8fbb 30103 non-free/binary-amd64/Packages.gz
-
assigned to @nextime
-
@gajdusek - Ah, right! Thanks for that insight
@nextime , can you please add
NotAutomatic: yes
and
ButAutomaticUpgrades: yes
to jessie-backports, -proposed and -proposed-updates for both /devuan and /merged
thanks :D
Edited by Daniel Reurich -
i've tested the new devuan_jessie_RC_amd64_minimal-live.iso
however i wonder why these 45 packages are from backports
- bash-completion 1:2.1-4.3~bpo8+1
- brltty 5.3.1-1~bpo8+1
- dmidecode 3.0-2~bpo8+1
- dvtm 0.15-1~bpo8+1
- e2fslibs:amd64 1.43.3-1~bpo8+1
- e2fsprogs 1.43.3-1~bpo8+1
- geoip-database 20170111-1~bpo8+1
- gettext-base 0.19.8.1-1~bpo8+1
- htop 2.0.2-1~bpo8+1
- ifupdown 0.8.13~bpo8+1
- irssi 1.0.2-1~bpo8+1
- libasprintf0c2:amd64 0.19.8.1-1~bpo8+1
- libassuan0:amd64 2.4.3-2~bpo8+1
- libbrlapi0.6:amd64 5.3.1-1~bpo8+1
- libcomerr2:amd64 1.43.3-1~bpo8+1
- libcups2:amd64 2.2.1-8~bpo8+1
- libcupsimage2:amd64 2.2.1-8~bpo8+1
- libfastjson4:amd64 0.99.4-1~bpo8+1
- libgcrypt20:amd64 1.7.6-1~bpo8+1
- libgeoip1:amd64 1.6.7-2~bpo8+1
- libglib2.0-0:amd64 2.48.0-1~bpo8+1
- libgpg-error0:amd64 1.26-2~bpo8+1
- libksba8:amd64 1.3.5-2~bpo8+1
- liblognorm5:amd64 2.0.1-1.1~bpo8+1
- libpcap0.8:amd64 1.8.1-3~bpo8+1
- libpulse0:amd64 7.1-2~bpo8+1
- libss2:amd64 1.43.3-1~bpo8+1
- libssl1.0.0:amd64 1.0.2k-1~bpo8+1
- libsystemd0:amd64 230-7~bpo8+2
- libudev1:amd64 230-7~bpo8+2
- linux-base 4.3~bpo8+1
- linux-libc-dev:amd64 4.9.13-1~bpo8+1
- live-boot 1:20160511~bpo8+1
- live-boot-doc 1:20160511~bpo8+1
- live-boot-initramfs-tools 1:20160511~bpo8+1
- manpages 4.09-2~bpo8+1
- manpages-dev 4.09-2~bpo8+1
- mosh 1.2.5-1~bpo8+1
- mtr-tiny 0.86-1~bpo8+1
- openssl 1.0.2k-1~bpo8+1
- pinentry-curses 0.9.7-5~bpo8+1
- rsyslog 8.23.0-2~bpo8+1
- tar 1.29b-1~bpo8+1
- tmux 2.3-4~bpo8+1
- udev 230-7~bpo8+2
it seems that backports priority is set to normal (500)
-
Update both jessie and also ascii -backports, -proposed and -proposed-updates repos in dak, so, the /devuan repo is done, at the next updgrade also the /merged one should be ok as amprolla take the headers from the /devuan one and copy them as they are.
-
@CenturionDan please take care to check when the /merged repo will be updated in max a couple of days and if it's ok close the ticket or mention me for further needs on that
-
closed