OK that's three, so I have to ask, if packages aren't in any images at all, why are they included in freeze? Why not just FE everything that's not going to risk causing compose related problems?

Other packages can break packages other packages. E.g. by suddenly providing libxbyz.so.1 without actually providing it) or by obsoleting firefox, etc.

BetaFE +1

The installation seems to work now.

Also, practically speaking we don't actually know the set of packages that will affect the next compose. It's a the-map-is-the-territory problem: our processes are so complex that it's almost impossible to figure that out without actually...running the compose. We would have to add dry-run functionality in a whole ton of places to make that a Thing.

AGREED AcceptedBetaFE

Discussed during the 2021-03-08 blocker review meeting: [0]

The decision to classify this bug as an "AcceptedFreezeException (Beta)" was made as we agree that an FE is generally merited if a package fails to install due to the impact on people upgrading from previous stable releases, likely without updates-testing enabled. However, fixes will only be pushed if they involve minimal change and don't seem likely to endanger compose of release-blocking images.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-03-08/f34-blocker-review.2021-03-08-17.00.txt

The following votes have been closed:

• Accepted BetaFreezeException (+1, 0, -0)
  • +1 by lruzicka

Release F34 is no longer tracked by BlockerBugs, closing this ticket.