Bug#864597: upgrade-reports: jessie -> stretch: gnome fails to upgrade: cycle found while processing triggers

[Julien Cristau]

On 06/15/2017 10:02 AM, Michael Biebl wrote:
> Hi
> 
> Am 12.06.2017 um 20:33 schrieb Andreas Beckmann:
>> Switching desktop-file-utils or/and shared-mime-info to -noawait
>> triggers does not solve the problem.
> 
> So afaics there is nothing that can be done from the Debian GNOME team
> side, right?
> 
>> I can confirm that the ca-certificates-java change triggered the bug
>> (i.e. backing it out makes the problem go away, but this is not a solution).
>>
>> I can also confirm that the changes I suggested in #863820 (adding
>> adding Breaks: tzdata-java to gcc-6-base) would fix this upgrade path.
>> It shakes the upgrade order quite well for this case ...
>> (I can post the log if someone is interested.)
>> According to piuparts, the upgrade paths of about 860 packages in
>> jessie2stretch-rcmd would be affected by this change (because
>> tzdata-java gets installed in jessie). These can be retested quickly.
> 
> I see that #863820 is still open and apparently also affects other
> upgrade paths. Shouldn't this be bumped to RC?
> What are we going to do about this? A failure to dist-upgrade our
> default desktop environment is pretty bad.
> Is there some known workaround which we could document in the release
> notes at least?
> From what I can see, wouldn't it be better to drop the the Breaks:
> tzdata-java from openjdk-8-jdk-headless again?
> 
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?

>From what I can see #863820 is at most a normal-severity issue.  Not
upgrading some packages is way way better than a failed upgrade.

Cheers,
Julien