Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers
- To: Cyril Brulebois <kibi@debian.org>, Julien Cristau <jcristau@debian.org>
- Cc: Michael Biebl <biebl@debian.org>, 864597@bugs.debian.org, lool@debian.org, ross@debian.org, Dmitry Smirnov <onlyjob@debian.org>, joss@debian.org, pkg-freedesktop-maintainers@lists.alioth.debian.org, Debian GNOME Maintainers <pkg-gnome-maintainers@lists.alioth.debian.org>, Guillem Jover <guillem@debian.org>, Matthias Klose <doko@debian.org>, debian-release <debian-release@lists.debian.org>, Aurelien Jarno <aurel32@debian.org>
- Subject: Re: Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers
- From: Andreas Beckmann <anbe@debian.org>
- Date: Thu, 15 Jun 2017 17:14:29 +0200
- Message-id: <[🔎] b59796cb-95bf-ba2e-27ae-9eeecbeeb294@debian.org>
- In-reply-to: <[🔎] 20170615131617.GA6521@mraw.org>
- References: <[🔎] 20170611091305.26084.86113.reportbug@armor.home> <4e9599f0-badd-f3a8-31fb-85bef5f92eda@thykier.net> <b8022083-fb92-7332-0b16-d3de1db34e39@debian.org> <[🔎] 4de44d25-1f1e-7b4f-169e-309d5e1cb9b6@debian.org> <[🔎] 6fac18fb-d72a-5af7-f05a-924fa53fbafc@debian.org> <[🔎] 20170615131617.GA6521@mraw.org>
On 2017-06-15 15:16, Cyril Brulebois wrote:
> Julien Cristau <jcristau@debian.org> (2017-06-15):
>> It sounds like openjdk-8 added two Breaks recently, one or both of
>> which are causing trouble, and none of which fix anything as bad as
>> this. So I think we should remove the Breaks on tzdata-java from
>> openjdk-8-jdk-headless, and remove the Breaks on ca-certificates-java
>> from openjdk-8-jre-headless. Would that fix the current issue?
What I had tested was reverting the recent ca-certificates-java change,
i.e. switching the dependency on
openjdk-8-jre-headless | java7-runtime-headless
back to
openjdk-7-jre-headless | java7-runtime-headless
(or similar)
That change was made later than the one in openjdk-8 and it proved to be
sufficient in my piuparts test to fix^Wnot activate that trigger cycle.
Andreas
Reply to: