public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bryan Gardiner <bog@khumba.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Haskell packages and keeptemp
Date: Sun, 20 Sep 2015 20:58:20 -0700	[thread overview]
Message-ID: <20150920205820.19c3bb32@khumba.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

Hi gentoo-users,

I thought I would set FEATURES=keeptemp in make.conf so I would have
build logs around for reference.  This causes problems with Haskell
packages, which fail during the second build after setting this,
because the build's temp/ hasn't been cleaned from the previous build:

> >>> Install http-client-tls-0.2.2 into /var/tmp/portage/dev-haskell/http-client-tls-0.2.2/image/ category dev-haskell
> ./setup copy --destdir=/var/tmp/portage/dev-haskell/http-client-tls-0.2.2/image/
> Installing library in
> /var/tmp/portage/dev-haskell/http-client-tls-0.2.2/image/usr/lib64/http-client-tls-0.2.2/ghc-7.10.2
> Creating package registration file:
> /var/tmp/portage/dev-haskell/http-client-tls-0.2.2/temp/http-client-tls-0.2.2.conf
> ghc-pkg: cannot create: /var/tmp/portage/dev-haskell/http-client-tls-0.2.2/temp/http-client-tls-0.2.2.conf.d already exists
>  * ERROR: dev-haskell/http-client-tls-0.2.2::haskell failed (install phase):
>  *   Failed to initialize empty local db

Am I wrong in expecting ${T} to be wiped at the start of a build,
regardless of the package, so that this isn't a problem?  I'm not sure
why you'd want old temp/ state to carry forward to the next build.

- Bryan

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

             reply	other threads:[~2015-09-21  3:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-21  3:58 Bryan Gardiner [this message]
2015-09-21  4:29 ` [gentoo-user] Haskell packages and keeptemp Michael Orlitzky
2015-09-21  5:03   ` Bryan Gardiner
2015-09-21  5:29 ` J. Roeleveld
2015-09-21  6:41   ` Bryan Gardiner
2015-09-21  6:55     ` Alan McKinnon
2015-09-21 15:37       ` Bryan Gardiner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150920205820.19c3bb32@khumba.net \
    --to=bog@khumba.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox