On Dec 25, 2007 11:19 PM, [EMAIL PROTECTED] wrote:
I'm using the same HaXML you are, actually.
Interesting ... unmerge quits by itself, but with the same error.
I am tempted to delete haskell itself, as far as possible, and see if
the haxml unmerge would get any further.
What if you tried
On Wed, Dec 26, 2007 at 11:40:53AM -0800, Jason Dusek wrote:
On Dec 25, 2007 11:19 PM, [EMAIL PROTECTED] wrote:
I'm using the same HaXML you are, actually.
Interesting ... unmerge quits by itself, but with the same error.
I am tempted to delete haskell itself, as far as possible, and
On Wed, 26 Dec 2007 13:51:15 -0800, [EMAIL PROTECTED] wrote:
What if you tried deleting HaXML from /var/lib/portage/world and
then remerging it? It would skip the `prerm` action and just
overwrite everything.
Nah, no luck. Emerge -p shows it still knows that haxml is a remerge,
not a
[EMAIL PROTECTED] wrote:
Jason Dusek wrote:
What if you tried deleting HaXML from /var/lib/portage/world
and then remerging it? It would skip the `prerm` action and
just overwrite everything.
Nah, no luck. Emerge -p shows it still knows that haxml is a
remerge, not a merge from scratch.
On Wed, Dec 26, 2007 at 03:35:10PM -0800, Jason Dusek wrote:
Okay, I figured it out -- remove it from /var/lib/portage/world
and remove /var/db/pkg/dev-haskell/haxml-1.13.2 (I moved it to
my home directory). Now when you run `emerge haxml --pretend`,
it will show it as new.
The merge worked,
On Wed, Dec 26, 2007 at 06:05:14PM -0800, [EMAIL PROTECTED] wrote:
I'll post more when ghc-updater is done.
ghc-updater ran fine, or at least didn't hang. There was one error:
src/lib/HsShellScript/Commands.chs:21:0:
Failed to load interface for `Text.ParserCombinators.Parsec':
[EMAIL PROTECTED] wrote:
ghc-updater ran fine, or at least didn't hang. There was one
error:
src/lib/HsShellScript/Commands.chs:21:0:
Failed to load interface for
`Text.ParserCombinators.Parsec':
Perhaps you haven't installed the profiling
libraries
On Mon, Dec 24, 2007 at 10:57:10PM -0800, Jason Dusek wrote:
On Dec 23, 2007 8:23 AM, [EMAIL PROTECTED] wrote:
Emerging haxml directly repeats the greedy performance, and when I
kill it, it gives me this message:
* The 'prerm' phase of the 'dev-haskell/haxml-1.13.2' package has failed
On Dec 25, 2007 6:26 AM, [EMAIL PROTECTED] wrote:
On Mon, Dec 24, 2007 at 10:57:10PM -0800, Jason Dusek wrote:
On Dec 23, 2007 8:23 AM, [EMAIL PROTECTED] wrote:
Emerging haxml directly repeats the greedy performance...
Does deleting the ebuild (not haxml, just that particular ebuild,
On Tue, Dec 25, 2007 at 05:26:31PM -0800, Jason Dusek wrote:
On Dec 25, 2007 6:26 AM, [EMAIL PROTECTED] wrote:
On Mon, Dec 24, 2007 at 10:57:10PM -0800, Jason Dusek wrote:
On Dec 23, 2007 8:23 AM, [EMAIL PROTECTED] wrote:
Emerging haxml directly repeats the greedy performance...
On Dec 23, 2007 8:23 AM, [EMAIL PROTECTED] wrote:
Emerging haxml directly repeats the greedy performance, and when I
kill it, it gives me this message:
* The 'prerm' phase of the 'dev-haskell/haxml-1.13.2' package has failed
* with exit value -1. The problem occurred while executing the
In a routine upgrade, I get the following message from several
haskell components:
* The package dev-haskell/cabal is not correctly installed for
* the currently active version of ghc (6.8.2). Please
* run ghc-updater or re-emerge dev-haskell/cabal.
So I tried running ghc-updater, and it
12 matches
Mail list logo
