Bug#988963: upgrade-reports: upgrade process requires a second "apt full-upgrade"
On Thu, May 27, 2021 at 09:48:29AM +0200, Paul Gevers wrote:
> Control: retitle -1 libgc1 and libgc1c2 have circular Conflict/Replaces
>
> Hi Bill,
>
> On 26-05-2021 23:21, Bill Allombert wrote:
> > On Wed, May 26, 2021 at 07:50:53PM +0000, Holger Levsen wrote:
> >> On Wed, May 26, 2021 at 12:00:46PM +0200, Bill Allombert wrote:
> >>> One way to fix that is to update libgc1c2 in stable to not
> >>> Conflict/Replaces with libgc1.
> >>
> >> while this is true, this is also not the most desireable fix, because
> >> it should be possible to update from *any* stable installation
> >> to the next stable, not just from the latest stable point release.
> >
> > I agree with you, but this is a general issue with circular dependencies
> > (and circular conflicts) that they can only be fixed cleanly by
> > updating stable and not testing.
> > That is why I have always strongly recommended to avoid them.
> >
> > (We could of course fix it in testing by renaming libgc1 to libgc1c4 or
> whatever
> > but that would create a much larger disruption than removing a useless Conflict
> > from stable).
>
> Do I understand you correctly that we're ready to reassign this bug to
> libgc1c2 and ask for the fix in buster?
To me there are two options:
- do nothing and document this in the release note
- fix it in stable.
but this is to the release team to decide.
We can reassign this bug to libgc1 but it is likely to be ignored
because it cannot be fixed in testing.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: