dpkg_1.18.21_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Jan 2017 20:29:58 +0100 Source: dpkg Binary: dpkg libdpkg-dev dpkg-dev libdpkg-perl dselect Architecture: source Version: 1.18.21 Distribution: unstable Urgency: medium Maintainer: Dpkg Developers Changed-By: Guillem Jover Description: dpkg - Debian package management system dpkg-dev - Debian package development tools dselect- Debian package management front-end libdpkg-dev - Debian package management static library libdpkg-perl - Dpkg perl modules Closes: 852820 Changes: dpkg (1.18.21) unstable; urgency=medium . [ Guillem Jover ] * Revert "Generate Testsuite-Restrictions fields from the test restrictions in dpkg-source into .dsc files". This change is contentious and should have been discussed more widely. Given that this has been live only for a couple of days, the impact should be minimal, but still something to take into account once and if this gets reintroduced. Closes: #852820 * Perl modules: - Map alternative or old ELF machine types to canonical ones. We need those to match on the encoded ABI, otherwise dpkg-shlibdeps will not be able to find the objects. . [ Updated man pages translations ] * German (Helge Kreutzmann). Checksums-Sha1: ec9cc1e1c8e817956c9a31734e34db82317d6f5a 2032 dpkg_1.18.21.dsc 44694e7f43d03b48362713d44207976f202c95a6 4519476 dpkg_1.18.21.tar.xz ba2e3fab059b8a3a8118927006fa5495c5eddf26 7301 dpkg_1.18.21_amd64.buildinfo Checksums-Sha256: 1a1ad2bd0abd5be01b151de19e08e7e735f17760897fe3c1a227cdaeb9ce4ef0 2032 dpkg_1.18.21.dsc 60f29cd0aa0eeb3e470ddc51d44b43fa0d3194c88b1f0cf0f07dfbba58c14e27 4519476 dpkg_1.18.21.tar.xz 075087b2c13988dbeef1ae002a93db3dc9d143cab94bf077cbb413ddba6e0726 7301 dpkg_1.18.21_amd64.buildinfo Files: 770abd5f6ae347748f1394a3bc618fa0 2032 admin required dpkg_1.18.21.dsc a8297e95775624fc8a7b289b61dff0a7 4519476 admin required dpkg_1.18.21.tar.xz 774750cf4c4513fd1ef34473f1e6740d 7301 admin required dpkg_1.18.21_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAliOStQACgkQuXK/PqSu V6PGhA//R+RoNYYFGxF2rU5SeRrUmUwe1k6RT38wRww3rtGN8wHK/HpIWwAtpl9n PWrCxzrkHv3M3ve/dtox6RlYUVsmwJ3pU18cPRbU9qVSFVH2F+8z/y+lZAjBPmdY D6+PUEbUAPQKZQi0z6tiY/S8ak2VMkv4PWajMNTwOuSSiikwoQLa+HCM77/7foIo 5Q6J9a/ZpIhYKYRtICCsxW5Eu8PjQ/6M0mHVvslJGOU0mm5tlUVfyk4i5z/B+BSW VASliwKv+4RSSPbias9g1yHEzmJz2hDaePB6w27xMS4g2C+gvRNWMsZm0YmjTgf8 Y28hSTwrBaH6youyM3vJCJbE3tulqo4yUB5H/rqyY0VHSZkDoeyp12nlm/kvhfzp GXoiKUWBc2O3FspyyXzMJKUFaKnCpNiNnLcgy8O0npjkea35jVdENIZEG8DgnlFw ZoJfRQPEmWsicGJHJK/jAEGggkkVsGDWQaEN0oz4PLtvatpN0uCWUV8WK40xHvg1 9ZcUr6hO+oRSDMDKDFdQQsaZmBpdeZh0+r5s8zOeAKOJlS+KHHOnAUAJJ3PBtsmM oSVhE0mwbKVmKh1ZXJa72WgNTaeTGb0EoXQJrGFKkDl3YTzXmeEKP1DnZSD9ZUQO c2E0qY93zHLyWRvpvYXRfnTRAXahrD3OWfWDsfLBpCHMm3+rx+Y= =iqQr -END PGP SIGNATURE- Thank you for your contribution to Debian.
Accepted dpkg 1.18.21 (source) into unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Jan 2017 20:29:58 +0100 Source: dpkg Binary: dpkg libdpkg-dev dpkg-dev libdpkg-perl dselect Architecture: source Version: 1.18.21 Distribution: unstable Urgency: medium Maintainer: Dpkg Developers Changed-By: Guillem Jover Description: dpkg - Debian package management system dpkg-dev - Debian package development tools dselect- Debian package management front-end libdpkg-dev - Debian package management static library libdpkg-perl - Dpkg perl modules Closes: 852820 Changes: dpkg (1.18.21) unstable; urgency=medium . [ Guillem Jover ] * Revert "Generate Testsuite-Restrictions fields from the test restrictions in dpkg-source into .dsc files". This change is contentious and should have been discussed more widely. Given that this has been live only for a couple of days, the impact should be minimal, but still something to take into account once and if this gets reintroduced. Closes: #852820 * Perl modules: - Map alternative or old ELF machine types to canonical ones. We need those to match on the encoded ABI, otherwise dpkg-shlibdeps will not be able to find the objects. . [ Updated man pages translations ] * German (Helge Kreutzmann). Checksums-Sha1: ec9cc1e1c8e817956c9a31734e34db82317d6f5a 2032 dpkg_1.18.21.dsc 44694e7f43d03b48362713d44207976f202c95a6 4519476 dpkg_1.18.21.tar.xz ba2e3fab059b8a3a8118927006fa5495c5eddf26 7301 dpkg_1.18.21_amd64.buildinfo Checksums-Sha256: 1a1ad2bd0abd5be01b151de19e08e7e735f17760897fe3c1a227cdaeb9ce4ef0 2032 dpkg_1.18.21.dsc 60f29cd0aa0eeb3e470ddc51d44b43fa0d3194c88b1f0cf0f07dfbba58c14e27 4519476 dpkg_1.18.21.tar.xz 075087b2c13988dbeef1ae002a93db3dc9d143cab94bf077cbb413ddba6e0726 7301 dpkg_1.18.21_amd64.buildinfo Files: 770abd5f6ae347748f1394a3bc618fa0 2032 admin required dpkg_1.18.21.dsc a8297e95775624fc8a7b289b61dff0a7 4519476 admin required dpkg_1.18.21.tar.xz 774750cf4c4513fd1ef34473f1e6740d 7301 admin required dpkg_1.18.21_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAliOStQACgkQuXK/PqSu V6PGhA//R+RoNYYFGxF2rU5SeRrUmUwe1k6RT38wRww3rtGN8wHK/HpIWwAtpl9n PWrCxzrkHv3M3ve/dtox6RlYUVsmwJ3pU18cPRbU9qVSFVH2F+8z/y+lZAjBPmdY D6+PUEbUAPQKZQi0z6tiY/S8ak2VMkv4PWajMNTwOuSSiikwoQLa+HCM77/7foIo 5Q6J9a/ZpIhYKYRtICCsxW5Eu8PjQ/6M0mHVvslJGOU0mm5tlUVfyk4i5z/B+BSW VASliwKv+4RSSPbias9g1yHEzmJz2hDaePB6w27xMS4g2C+gvRNWMsZm0YmjTgf8 Y28hSTwrBaH6youyM3vJCJbE3tulqo4yUB5H/rqyY0VHSZkDoeyp12nlm/kvhfzp GXoiKUWBc2O3FspyyXzMJKUFaKnCpNiNnLcgy8O0npjkea35jVdENIZEG8DgnlFw ZoJfRQPEmWsicGJHJK/jAEGggkkVsGDWQaEN0oz4PLtvatpN0uCWUV8WK40xHvg1 9ZcUr6hO+oRSDMDKDFdQQsaZmBpdeZh0+r5s8zOeAKOJlS+KHHOnAUAJJ3PBtsmM oSVhE0mwbKVmKh1ZXJa72WgNTaeTGb0EoXQJrGFKkDl3YTzXmeEKP1DnZSD9ZUQO c2E0qY93zHLyWRvpvYXRfnTRAXahrD3OWfWDsfLBpCHMm3+rx+Y= =iqQr -END PGP SIGNATURE-
Processing of dpkg_1.18.21_amd64.changes
dpkg_1.18.21_amd64.changes uploaded successfully to localhost along with the files: dpkg_1.18.21.dsc dpkg_1.18.21.tar.xz dpkg_1.18.21_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
[RFC/PATCH] dpkg frontend locking
Hi everyone,
I talked with guillem about this idea on IRC, but I decided to
write this down in an email for further discussion.
Currently, APT and other dpkg frontends have to acquire the dpkg
database lock at the start of their process and then have to release
the dlock before invoking dpkg and re-acquire it afterwards.
This leads to a race condition where another process could acquire
the database lock while another frontend is about to start a new
dpkg process.
The proposed fix for that is simple: Introduce a new lock called
the frontend lock.
Frontends will acquire both the frontend lock and the database
lock (in that order) and for invoking dpkg only release the
database lock while keeping the frontend lock.
Dpkg will acquire both locks, unless DPKG_FRONTEND_LOCKED is
set, in which case only the database lock is acquired and the
frontend lock is ignored.
Compatibility matrix:
Assuming two frontends (f1 running, f2 not) and a dpkg with the old
and new behavior each, it looks like this.
f1 f2 dpkgsituation
1. old old old Same as now (easy race)
2. old old new Same as now (easy race)
3. old new old still a race as f1 has no frontend lock
4. old new new still a race
5. new old old still a race possible.
6. new old new no race. dpkg will refuse to run by f2
because it will try to acquire the fe lock
hold by f1.
7. new new old the frontends can't run at the same time,
but dpkg could be run manually
8. new new new like 7, but without the manual dpkg backdoor
Branches:
apt: git fetch https://github.com/julian-klode/apt bugfix/big-lock
-> diff:
https://github.com/Debian/apt/compare/master...julian-klode:bugfix/big-lock?expand=1
dpkg: git fetch https://github.com/julian-klode/dpkg/compare/master
pu/frontend-lock
-> diff:
https://github.com/julian-klode/dpkg/compare/master...julian-klode:pu/frontend-lock
It's also trivial to add to python-apt, meaning that apt and the
whole python-apt ecosystem (including unattended-upgrades) will
be safe against interference from other package manager frontends.
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
