tag 766557 pending
thanks
Hello,
Bug #766557 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=317083c
---
commit 317083c11091dcd9e2b1a36677964aaaa0b53c1c
Author: Guillem Jover <[email protected]>
Date: Fri Oct 24 15:18:11 2014 +0200
dpkg: Perform trigger cycle detection earlier or later depending on
dependtry
Do trigger cycle detection after dependency checks in dependtry <= 1,
and before dependency cycle breaking in dependtry > 1. This makes sure
to always catch trigger cycles, but still gives the opportunity to try
to process triggers for packages that are not yet ready in the first
dependtry, but which might be a bit later on, without wrongly detecting
avoidable and bogus trigger cycles.
Closes: #766557
diff --git a/debian/changelog b/debian/changelog
index c7756c8..ca8b889 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -14,6 +14,12 @@ dpkg (1.17.21) UNRELEASED; urgency=low
And a new --await option to dpkg-trigger. This might allow possibly
switching the default meaning after a transition period no shorter than
two minor versions, so in 1.19.x or 1.20.x. Perhaps.
+ * Do trigger cycle detection after dependency checks in dependtry <= 1,
+ and before dependency cycle breaking in dependtry > 1. This makes sure
+ to always catch trigger cycles, but still gives the opportunity to try
+ to process triggers for packages that are not yet ready in the first
+ dependtry, but which might be a bit later on, without wrongly detecting
+ avoidable and bogus trigger cycles. Closes: #766557
[ Updated programs translations ]
* Catalan (Guillem Jover).
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
