#6047 handle packages that are retired only in Branched but not Rawhide
Closed: Fixed 7 years ago Opened 9 years ago by till.

Currently we allow to retire packages in Branched even if they are not retired in Rawhide. Today I realized that if a package is retired in Branched (i.e. it will be blocked in f21), it will also not be shipped in Rawhide, even if it is not retired there, because currently if it is blocked in f21 it is also blocked in f22. It might make sense to only retire packages in Branched to not ship packages with broken deps, like it is currently proposed. However this does not mean that the package should be retired in Rawhide, to allow it being fixed for the next release. Therefore we should decide if we:

1) Allow retirement in Branched only for packages retired in Rawhide
2) Unblock packages in f22 if they are only retired in f21


The plan is to unblock pkgs in Rawhide, if a package is only retired in Branched. till is working on this.

I would like to add here that when it comes to retiring packages with broken deps, that should be done not only in Branched, but Rawhide too. The reason for this is that if something is broken in Branched, it's very likely to be broken in the same way in Rawhide too. If we don't clean up Rawhide, it soon becomes a broken mess that is difficulty to develop or use.

This is also what FESCo decided when it was discussed during the F21 cycle:

{{{
AGREED: FESCo agrees to dropping the packages with broken dependencies listed in #1368 from both F21 and rawhide (+7, -0, 0:0)

AGREED: We will do the broken deps cleanup on Final Freeze from now on in the future Fedora releases (+8, -0, 0:0)

There will be warning sent to the affected maintainers at least 3 weeks in advance (t8m, 19:31:36)
}}}

https://fedorahosted.org/fesco/ticket/1368#comment:6

lets get this done with the cleanup of f22 broken packages.

Metadata Update from @till:
- Issue assigned to till
- Issue set to the milestone: Fedora 22 Final

7 years ago

I believe this all handled okay now.

I believe this all handled okay now.

Metadata Update from @ausil:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

7 years ago

Login to comment on this ticket.

Metadata