On 11/25/2014 04:49 AM, Andreas K. Huettel wrote:
> Hi Alec,
>
>> I've been having a really strange issue with net-print/cups-filters for
>> the last few weeks, wondering whether or not it's a bug or I just have
>> something configured wrong. Somehow ${S} is defined as:
>>
>> /var/tmp/portage/net-print/cups-filters-1.0.53/work/cups-filters-3.2.10
>>
>> and the build predictably fails.
> this is a really weird error.
>
> The only idea that I have is that some unusual environment variable is set
> outside Portage, and then somehow leaks into the Portage internals.
>
> You could check (before running emerge) if you see the "3.2.10" anywhere in
> your environment ("set|less")... or if maybe $PV or $S is set outside emerge
> somewhere.
Wow, incredible. I never thought to check my environment, but these:
MODULE_VERSION=3.2.10
MODULE_VERSION_STACK=3.2.10
could be a problem? Both of these variables are for the modules
environment management package, which I use to manage switching between
ruby interpreters.
> If this doesnt go away, we can ask the portage guys for advice.
>
> Best,
> Andreas
>
This was also affecting dev-libs/stfl for me; unsetting MODULE_VERSION
causes this to succeed. The only eclasses they have in common are
"eutils" and "perl-module", if that's important.
Andreas, if this is a bug that needs fixing, let me know who to contact
get this dealt with.
Regards,
Alec
