This bug was fixed in the package apt - 1.4.6~17.04.1
---
apt (1.4.6~17.04.1) zesty; urgency=medium
* apt.systemd.daily: Do not pass -d to unattended-upgrade for the download
job. This actually enables debugging. Instead check if unattended-upgrade
supports an option
This bug was fixed in the package apt - 1.2.24
---
apt (1.2.24) xenial; urgency=medium
* Microrelease covering fixes of 1.4.6
* Fix parsing of or groups in build-deps with ignored packages (LP: #1694697)
* apt.systemd.daily: Use unattended-ugrade --download-only if available.
Ah, i did not upgrade libapt-pkg5.0 as i wanted to leave some packages
for the auto-upgrader test case.
Upgrading those two:
ii libapt-inst2.0:amd641.4.6~17.04.1
amd64deb package format runtime library
ii libapt-pkg5.0:amd64
I'd say you forgot to upgrade libapt-pkg5.0 - the test is run in CI and
autopkgtest too, so it's highly unlikely to not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694697
Title:
Using:
ii apt 1.4.6~17.04.1
amd64
# apt-get build-dep -s ./segv.dsc
Note, using file './segv.dsc' to get the build dependencies
Reading package lists... Done
Building dependency tree
Reading state information... Done
Using:
ii apt 1.2.24
amd64commandline package manager
And executing:
(1) apt-get build-dep -s ./segv.dsc should succeed instead of crash
(2) apt-get build-dep -s ./failure.dsc should complain about
Hello Julian, or anyone else affected,
Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.24 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: apt (Ubuntu Zesty)
Status: New => In Progress
** Changed in: apt (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: apt (Ubuntu Xenial)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This affects all active releases AFAICT, so we should issue SRUs for
these. It's questionable how to test the pre-1.1 release in trusty,
though - they do not support build-dep from a file, so the test will be
more complex - maybe it's not really worth it.
** Also affects: apt (Ubuntu Trusty)
This bug was fixed in the package apt - 1.4.5
---
apt (1.4.5) unstable; urgency=medium
* Fix parsing of or groups in build-deps with ignored packages (LP:
#1694697)
-- Julian Andres Klode Wed, 31 May 2017 14:52:25
+0200
** Changed in: apt (Ubuntu)
Fixed in upstream release 1.4.5. Now we only need to wait for it to sync
:)
** Description changed:
[Impact]
If the last alternative(s) of an Or group is ignored, because it does
not match an architecture list, we would end up keeping the or flag,
effectively making the next AND an OR.
** Changed in: apt (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1694697
Title:
build-depends keeps OR flag if end of or group is ignored
To
This also causes crashes in python-apt due to a off-by-one error in size
checking there, see 1694702
** Description changed:
+ [Impact]
If the last alternative(s) of an Or group is ignored, because it does
not match an architecture list, we would end up keeping the or flag,
effectively
13 matches
Mail list logo