Thanks! So can I have a list of broken package sorted by Hackage dependencies, so I know which packages are used the most? Sounds like there is still work to be done.
Aloha, RK. On Thu, Aug 21, 2014 at 3:19 PM, Mateusz Kowalczyk <[email protected]> wrote: > On 08/21/2014 05:46 AM, Raahul Kumar wrote: > > How? Amazing well done! But seriously how was this achieved? > > > > > > On Thu, Aug 21, 2014 at 4:45 AM, Luca Bruno <[email protected]> > wrote: > > > >> Wow, awesome. > >> > >> > >> On Wed, Aug 20, 2014 at 8:33 PM, Peter Simons <[email protected]> wrote: > >> > >>> On Linux/x86_64, zero Haskell builds fail: > >>> > >>> http://hydra.cryp.to/jobset/nixpkgs/haskell-updates > >>> > >>> Let's hope that lasts. :-) > >>> > >>> Best regards, > >>> Peter > >>> > > It was achieved by marking broken things as broken so that they don't > come up as failures on Hydra all the time. Once the package is fixed > (upstream or otherwise) it can be built again and we have an extra > package building. > > The approach of marking stuff as broken allows one to see much better > which packages actually change build status. Users also get a message if > they try to compile a package marked as broken rather than have them try > to compile and fail which was horrible user experience. > > -- > Mateusz K. > _______________________________________________ > nix-dev mailing list > [email protected] > http://lists.science.uu.nl/mailman/listinfo/nix-dev >
_______________________________________________ nix-dev mailing list [email protected] http://lists.science.uu.nl/mailman/listinfo/nix-dev
