[gentoo-user] Haskell packages and keeptemp

[gentoo-user] Haskell packages and keeptemp

[Bryan Gardiner]

[-- 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 --]

Re: [gentoo-user] Haskell packages and keeptemp

[Michael Orlitzky]

On 09/20/2015 11:58 PM, Bryan Gardiner wrote:
> 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:
> 
> ...
> 
> 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.
> 

Please open a bug. Portage probably has its own reasons for handling
${T} the way it does.

The problem with the Haskell stuff is (in haskell-cabal.eclass),

  # Newer cabal can generate a package conf for us:
  ./setup register --gen-pkg-config="${T}/${P}.conf"
  ghc-install-pkg "${T}/${P}.conf"

and the cabal routine doesn't want to overwrite an existing file. I'm
sure this is easy to fix with an "rm -f" beforehand.

But, maybe the reason portage doesn't wipe the directory is because
portage doesn't wipe the directory. If doing so would be an improvement,
they might choose to fix it there instead.

Re: [gentoo-user] Haskell packages and keeptemp

[Bryan Gardiner]

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

On Mon, 21 Sep 2015 00:29:38 -0400
Michael Orlitzky <mjo@gentoo.org> wrote:

> Please open a bug. Portage probably has its own reasons for handling
> ${T} the way it does.

Yeah probably.  Filed https://bugs.gentoo.org/show_bug.cgi?id=560966,
thanks.

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

Re: [gentoo-user] Haskell packages and keeptemp

[J. Roeleveld]

On 21 September 2015 05:58:20 CEST, Bryan Gardiner <bog@khumba.net> wrote:
>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

Build logs usually (I didn't change anything for that) end up in
/var/log/portage

Did you check there?

--
Joost
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: [gentoo-user] Haskell packages and keeptemp

[Bryan Gardiner]

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

On Mon, Sep 21, 2015 at 07:29:39AM +0200, J. Roeleveld wrote:
> On 21 September 2015 05:58:20 CEST, Bryan Gardiner <bog@khumba.net> wrote:
> >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:
> >
> > <snip>
> >
> >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
> 
> Build logs usually (I didn't change anything for that) end up in
> /var/log/portage
> 
> Did you check there?

All I have there is /var/log/portage/elog which is because I
explicitly added "save" to PORTAGE_ELOG_SYSTEM.  I want the build.log
files, not just the elog output, do you have those in
/var/log/portage?

Thanks,
Bryan

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

Re: [gentoo-user] Haskell packages and keeptemp

[Alan McKinnon]

On 21/09/2015 08:41, Bryan Gardiner wrote:
> On Mon, Sep 21, 2015 at 07:29:39AM +0200, J. Roeleveld wrote:
>> On 21 September 2015 05:58:20 CEST, Bryan Gardiner <bog@khumba.net> wrote:
>>> 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:
>>>
>>> <snip>
>>>
>>> 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
>>
>> Build logs usually (I didn't change anything for that) end up in
>> /var/log/portage
>>
>> Did you check there?
> 
> All I have there is /var/log/portage/elog which is because I
> explicitly added "save" to PORTAGE_ELOG_SYSTEM.  I want the build.log
> files, not just the elog output, do you have those in
> /var/log/portage?

That's not quite what PORTAGE_ELOG_SYSTEM does. That is for elogs, not
build logs. You need this:

PORT_LOGDIR=/var/log/portage


-- 
Alan McKinnon
alan.mckinnon@gmail.com

Re: [gentoo-user] Haskell packages and keeptemp

[Bryan Gardiner]

On Mon, Sep 21, 2015 at 08:55:37AM +0200, Alan McKinnon wrote:
> On 21/09/2015 08:41, Bryan Gardiner wrote:
> > On Mon, Sep 21, 2015 at 07:29:39AM +0200, J. Roeleveld wrote:
> >> On 21 September 2015 05:58:20 CEST, Bryan Gardiner <bog@khumba.net> wrote:
> >>> 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:
> >>>
> >>> <snip>
> >>>
> >>> 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
> >>
> >> Build logs usually (I didn't change anything for that) end up in
> >> /var/log/portage
> >>
> >> Did you check there?
> > 
> > All I have there is /var/log/portage/elog which is because I
> > explicitly added "save" to PORTAGE_ELOG_SYSTEM.  I want the build.log
> > files, not just the elog output, do you have those in
> > /var/log/portage?
> 
> That's not quite what PORTAGE_ELOG_SYSTEM does. That is for elogs, not
> build logs. You need this:
> 
> PORT_LOGDIR=/var/log/portage

Aha, of course it makes sense that Portage has a proper feature for
this, and that the warning for keeptemp is (perhaps) justified :).
Thanks all for your help, that plus FEATURES="split-log -unmerge-logs"
is perfect.

Cheers,
Bryan