tag 766322 pending
thanks
Hello,
Bug #766322 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=edeed56
---
commit edeed5695089a283a0abffcf0044fc9bf1c3a0b8
Author: Guillem Jover <[email protected]>
Date: Wed Oct 22 14:04:30 2014 +0200
dpkg: Make sure to always switch to the next dependtry after no progress
We might get into a situation where we are making no progress, and
dependencies_ok() is still telling us that we can make progress by
fixing some triggers awaited package, but if those packages require
a dependency cycle to be broken we will get stuck and not progress to
the next dependtry.
Add an additional hard limit where we will jump dependtry, in case we
are not making any progress. This is a safety net that was removed when
triggers got introduced, but that only became active when adding the
dependency checks to trigproc(), although it was never future-proof.
Regression introduced in commit 10440009b68f59eeed4cb1b56547e3cf356aa540
and commit e121d882c92099d1f1aa9eedd0c0e90806a44efa.
Closes: #766242, #766322
diff --git a/debian/changelog b/debian/changelog
index 149f4da..01419f4 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,10 @@ dpkg (1.17.20) UNRELEASED; urgency=low
[ Guillem Jover ]
* Add a requeueing insertion protection for process_queue().
+ * Make sure to always switch to the next dependtry after we have made no
+ progress for a while. Regression stemming from non future proof changes
+ introduced with the initial triggers implementation in dpkg 1.14.17
+ combined with changes in dpkg 1.17.19. Closes: #766242, #766322
[ Updated programs translations ]
* German (Sven Joachim).
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
