Am 16.08.2011 02:18, schrieb Dale:
Sebastian Beßler wrote:
But why was autounmask=y complaining but not autounmask=n?
The dependency of the virtual was missing both times so shouldn't emerge
spit some error out both times?
Greetings
Sebastian
Because autounmask=n assumes you
Sebastian Beßler wrote:
Am 16.08.2011 02:18, schrieb Dale:
Sebastian Beßler wrote:
But why was autounmask=y complaining but not autounmask=n?
The dependency of the virtual was missing both times so shouldn't emerge
spit some error out both times?
Greetings
Sebastian
On Tue, Aug 16, 2011 at 14:33, Dale rdalek1...@gmail.com wrote:
Well, it could be that I'm reading the error incorrectly too. Ask people
how much fun it is for me to figure out what the heck portage is puking on
my keyboard. I have had Alan explain it to me, what he says makes sense but
it
Pandu Poluan wrote:
On Tue, Aug 16, 2011 at 14:33, Dalerdalek1...@gmail.com wrote:
Well, it could be that I'm reading the error incorrectly too. Ask people
how much fun it is for me to figure out what the heck portage is puking on
my keyboard. I have had Alan explain it to me, what he
I just tried
emerge -DuN @world @system -va
and got:
These are the packages that would be merged, in order:
Calculating dependencies ... done!
[ebuild U ] perl-core/ExtUtils-ParseXS-3.20.0 [2.22.06] 0 kB
[ebuild U ] www-client/firefox-bin-5.0 [3.6.19]
USE=startup-notification
[ebuild
On Mon 15 August 2011 19:31:37 Sebastian Beßler did opine thusly:
I just tried
emerge -DuN @world @system -va
and got:
These are the packages that would be merged, in order:
Calculating dependencies ... done!
[ebuild U ] perl-core/ExtUtils-ParseXS-3.20.0 [2.22.06] 0 kB
[ebuild
Am 15.08.2011 20:02, schrieb Alan McKinnon:
It's not a bug, portage is doing what it should.
In the first case portage will try upgrade all packages to the latest
version. It sees that you asked it to try autounmask stuff, so it
wants to override your local mask for ExtUtils-ParseXS.
I
On Mon 15 August 2011 20:55:12 Sebastian Beßler did opine thusly:
Am 15.08.2011 20:02, schrieb Alan McKinnon:
It's not a bug, portage is doing what it should.
In the first case portage will try upgrade all packages to the
latest version. It sees that you asked it to try autounmask
Alan McKinnon wrote:
Do you have autounmask enabled or disabled in your config for portage?
That first example you gave strongly indicates you have it enabled.
I'm thinking the same thing. It seems to be enabled by default I
think. I know it is here and I didn't do it. It just sort
On Mon 15 August 2011 15:12:09 Dale did opine thusly:
Alan McKinnon wrote:
Do you have autounmask enabled or disabled in your config for
portage?
That first example you gave strongly indicates you have it
enabled.
I'm thinking the same thing. It seems to be enabled by default I
Am 15.08.2011 21:34, schrieb Alan McKinnon:
Do you have autounmask enabled or disabled in your config for portage?
I have it enabled because it is enabled by default. You have to explicit
disable it.
So, because it is enabled by default, I never asked portage to
autounmask anything for me.
On Mon, Aug 15, 2011 at 12:31 PM, Sebastian Beßler
sebast...@darkmetatron.de wrote:
Why is autounmask trying to unmask ExtUtils-ParseXS if it's not needed?
Should I report this as a bug?
I think it's only telling you what you should unmask. Setting
--autounmask=n simply makes it stop giving you
Sebastian Beßler wrote:
Am 15.08.2011 21:34, schrieb Alan McKinnon:
Do you have autounmask enabled or disabled in your config for portage?
I have it enabled because it is enabled by default. You have to explicit
disable it.
So, because it is enabled by default, I never asked portage
Am 15.08.2011 23:33, schrieb Paul Hartman:
Use --tree to get a better idea what package wants the newer ExtUtils-ParseXS
I narrowed it down to
emerge perl-core/Module-Build -vp
These are the packages that would be merged, in order:
Calculating dependencies ... done!
[ebuild
Sebastian Beßler wrote:
But why was autounmask=y complaining but not autounmask=n?
The dependency of the virtual was missing both times so shouldn't emerge
spit some error out both times?
Greetings
Sebastian
Because autounmask=n assumes you don't want to upgrade anything that is
15 matches
Mail list logo
