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
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:
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
On 11/25/2014 10:41 AM, Andreas K. Huettel wrote:
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:
Am Dienstag 25 November 2014, 12:56:00 schrieb Alec Ten Harmsel:
I am just wondering, though,
why aren't all internal variables prefixed with PORTAGE_ or the like to
prevent this sort of thing?
it's not really internal, just defined in an eclass... and these are regular
environment
Hey guys,
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
6 matches
Mail list logo
