#401 exception to revert ghc-6.12.3 to ghc-6.12.2 in rawhide
Closed None Opened 13 years ago by petersen.

= Proposal topic =

Revert ghc to 6.12.2 in rawhide until ghc-6.12.3 rebuilds completed in dist-f14-ghc.

= Overview =

ghc in rawhide is being upgraded from 6.12.2 to 6.12.3.
This required rebuilding all the libraries and packages
compiled with ghc (currently around 50 packages).

In the past we just let the dependency breakage hit
rawhide, but this time there were rightly complaints of
the amount of dep breakage in the Rawhide Report,
so I requested dist-f14-ghc, but this was already
after ghc-6.12.3 had been built in rawhide.

= Problem space =

To stop the large amount of dependency breakage in rawhide
and the Rawhide Report - doing the update and rebuilding in
dist-f14-ghc.

= Solution Overview =

Move ghc-6.12.3 from dist-f14 to dist-f14-ghc to keep
noise from Rawhide Report and move back all the rebuilt
packages back once ready.

In future be sure to build new versions of ghc in
dist-*-ghc buildroot and not rawhide.

= Active Ingredients =

Haskell SIG and Releng.

= Owners =

petersen


I am ok to an exception to the 'moving back in rawhide' here for several reasons:

  • Most people wouldn't have been able to upgrade to the new ghc due to deps in all the other ghc packages.
  • Those who did just have ghc itself installed and nothing else, and they wouldn't be affected by this.
  • This is just short term to allow fixing the other packages in the seperate tag.

So, +1 from me. If we could get other folks voting in ticket that would be nice. By next tuesday this will be moot I suspect.

Adding myself to cc, and also providing releng input, I'm in favor of making this go backwards. We aren't doing anybody any favors by keeping it broken.

I agree with the argument that nobody can have installed the broken version yet, so rolling it back quickly to get back to a nonbroken rawhide is the best course of action. +1

From email from tuxbrewr:

makes sense to me +1

That seems to have passed then.

This was approved, acted on and can be closed. ;)

Login to comment on this ticket.

Metadata