* Using cabal-1.2.3.0. [1 of 1] Compiling Main ( /dev/shm/portage/dev-haskell/network-2.0.1 /work/ghc-6.6.1/libraries/network/Setup.hs, /dev/shm/portage/dev-haskell/network -2.0.1/work/ghc-6.6.1/libraries/network/Setup.o ) Linking setup ... Configuring network-2.0.1... setup: At least the following dependencies are missing: parsec -any * * ERROR: dev-haskell/network-2.0.1 failed. * Call stack: [...] Solution: Put dev-haskell/parsec in DEPEND. Also, several keywords were mysteriously dropped without notifying the arches. Why, again?
(In reply to comment #0) > Configuring network-2.0.1... > setup: At least the following dependencies are missing: > parsec -any > Solution: Put dev-haskell/parsec in DEPEND. Yep, thanks. > Also, several keywords were mysteriously dropped without notifying the arches. > Why, again? Usually to satisfy repoman. For example I think at the time network-2.0.1 was added ghc-6.6 was not available on hppa and since this newer version of network needs ghc-6.6 we had do drop keywords for arches where ghc-6.6 was not yet available. You are always more than welcome to keyword any haskell herd package [~]hppa. If you like we can file a bug to suggest the most useful ones that would be nice to add ~hppa or stable.
(In reply to comment #1) > > Solution: Put dev-haskell/parsec in DEPEND. > > Yep, thanks. Thank you. > > Also, several keywords were mysteriously dropped without notifying the arches. > > Why, again? > > Usually to satisfy repoman. For example I think at the time network-2.0.1 was > added ghc-6.6 was not available on hppa and since this newer version of network > needs ghc-6.6 we had do drop keywords for arches where ghc-6.6 was not yet > available. You missed the second half of the question. No doubt you had good reason to drop the keywords, the question is why you didn't notify the relevant arch teams?
We need to get dev-haskell/parsec marked stable on at amd64 ppc sparc and x86 to be able to add it as a dep of network-2.0.1 which is already stable on those arches.
Latest unstable network has all the keywords. There is intermediate versions, which drop the keywords. Seems they were unkeyworded as ghc binaries were unavailable at that time (not an issue any more). We plan to dump older network ebuilds along with older ghc ebuilds. Is there a sense of restoring intermediate keywords? Do current intermediate keyword drops bring harm to arch teams?
dev-haskell/network got all keywords
