Hi Dominique, Thanks for bringing this up. I looked at the failing packages and I found a fairly large number of Haskell packages (ghc-*) that are unresolvable. The same packages build fine in the development project (devel:languages:haskell) and this is where I check on a regular basis that everything is green. The unresolvable packages are the result of an idiosyncrasy of Haskell that has no stable ABI for libraries. Our RPMs cater for this fact by including an ABI hash in the RPM's metadata. A Haskell package does not only depend on another Haskell package but on a Haskell package with a certain ABI hash. So the unresolvable packages actually build require packages that are uninstallable because the ABI hash on one of their dependencies changed because of an update. To fix this we need to rebuild all Haskell packages that depend on a Haskell package each time that package is updated. What can I do to help get Haskell back in shape on TW? Peter Dominique Leuenberger / DimStar wrote:
Hi all,
as a provocative* counter to the thread that we have too few packages in Tumbleweed, I would like to raise (again) awareness that I would also appreciate if people would take care of the stuff that actually IS in Tumbleweed.
Getting a package IN there is not as difficult as some seem to believe, but I would like to stress that this is no hit'n'run game.
Currently, TW keeps on having a rough 50 packages in failing state (some change here and there, some stay forever). Emails are sent after 7 days of failure - so I will keep this mail here 'short' to stuff failing for > 10 days (having given people a chance to read the mails). Packages with pending submissions to Factory are also excluded.
So, this leaves us with this list of packages that still is in need of handling:
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org