View previous topic :: View next topic |
Author |
Message |
MikeSummers n00b
Joined: 31 May 2003 Posts: 38 Location: Kansas City
|
Posted: Wed Feb 13, 2013 1:52 pm Post subject: package.mask not working with package.keywords? |
|
|
I need net-libs/nodejs on my 64-bit system so in /etc/portage/package.keywords I add:
Code: | net-libs/nodejs ~amd64 |
and nodejs-0.9.3-r1 emerges just fine.
The latest version of nodejs (0.9.9) looks to have some unsatisfied dependency on v8 so I add this to package.mask:
Code: | <net-libs/nodejs-0.9.9 | and get:
Code: |
# emerge -pvDN nodejs
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ~] net-libs/nodejs-0.9.9 [0.9.3-r1] 0 kB
Total: 1 package (1 upgrade), Size of downloads: 0 kB
|
Any ideas what's going on? |
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Wed Feb 13, 2013 2:06 pm Post subject: Re: package.mask not working with package.keywords? |
|
|
MikeSummers wrote: | The latest version of nodejs (0.9.9) looks to have some unsatisfied dependency on v8 so I add this to package.mask:
Code: | <net-libs/nodejs-0.9.9 |
Any ideas what's going on? |
Well, if you mean that you do not want nodejs-0.9.9, then what you should put in you package.mask is
=net-libs/nodejs-0.9.9
or
If you mean that you are perfectly happy with your nodejs-0.9.3-r1 and do not want upper revisions then put :
>net-libs/nodejs-0.9.3-r1
In no case, you should <net-libs/nodejs-0.9.9 because there you are masking everything but the release you actually do not want. _________________
Last edited by aCOSwt on Wed Feb 13, 2013 3:03 pm; edited 1 time in total |
|
Back to top |
|
|
MikeSummers n00b
Joined: 31 May 2003 Posts: 38 Location: Kansas City
|
Posted: Wed Feb 13, 2013 2:24 pm Post subject: Re: package.mask not working with package.keywords? |
|
|
Thanks for the reply.
Is the Wiki version specifier page wrong then?
I ran this test and the results are still surprising
Code: |
# cat package.mask ; emerge -pv nodejs
=net-libs/nodejs-0.9.9
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ~] net-libs/nodejs-0.9.3-r1 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
# cat package.mask ; emerge -pv nodejs
>net-libs/nodejs-0.9.9
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ~] net-libs/nodejs-0.9.9 [0.9.3-r1] 0 kB
Total: 1 package (1 upgrade), Size of downloads: 0 kB
# cat package.mask ; emerge -pv nodejs
<net-libs/nodejs-0.9.9
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ~] net-libs/nodejs-0.9.9 [0.9.3-r1] 0 kB
Total: 1 package (1 upgrade), Size of downloads: 0 kB
|
aCOSwt wrote: | MikeSummers wrote: | The latest version of nodejs (0.9.9) looks to have some unsatisfied dependency on v8 so I add this to package.mask:
Code: | <net-libs/nodejs-0.9.9 |
Any ideas what's going on? |
Well, if you mean that you do not want nodejs-0.9.9, then what you should put in you package.mask is
=net-libs/nodejs-0.9.9
or
If you mean that you are perfectly happy with your nodejs-0.9.3-r1 and do not want upper revisions then put :
>net-libs/nodejs-0.9.3-r1
In no case, you should <net-libs/nodejs-0.9.9 because there you are masking everything but the release you actually want. |
|
|
Back to top |
|
|
MikeSummers n00b
Joined: 31 May 2003 Posts: 38 Location: Kansas City
|
Posted: Wed Feb 13, 2013 2:28 pm Post subject: |
|
|
It's a bug in the interaction between package.keywords and package.mask.
Dropping the package.mask specifier and going with
Code: | <net-libs/nodejs-0.9.9 ~amd64 |
in package.keywords gives
Code: | Calculating dependencies... done!
[ebuild R ~] net-libs/nodejs-0.9.3-r1 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
|
|
|
Back to top |
|
|
albright Advocate
Joined: 16 Nov 2003 Posts: 2588 Location: Near Toronto
|
Posted: Wed Feb 13, 2013 2:48 pm Post subject: |
|
|
I don't see the bug
in the first case, you masked 0.9.9 so it rebult
the newest unmasked version (0.9.3)
in the second case, you masked everything greater
than 0.9.9 (of which there are none) so it
wanted to upgrade
in the third case, you masked everything less than
0.9.9 so again it wanted to upgrade to 0.9.9
I don't see any bad behaviour here so if you
can take the time please explain the problem _________________ .... there is nothing - absolutely nothing - half so much worth
doing as simply messing about with Linux ...
(apologies to Kenneth Graeme) |
|
Back to top |
|
|
Veldrin Veteran
Joined: 27 Jul 2004 Posts: 1945 Location: Zurich, Switzerland
|
Posted: Wed Feb 13, 2013 3:26 pm Post subject: |
|
|
Quote: | It's a bug in the interaction between package.keywords and package.mask. |
Could you explain where? IMO it works as is should.
your first example says, mask net-libs/nodejs-0.9.9, therefore net-libs/nodejs-0.9.3-r1 is the next best option.
your second example says, mask all packages versions larger than 0.9.9. as net-libs/nodejs-0.9.9 is not larger than net-libs/nodejs-0.9.9, therefore it emerges it.
your third examples is like the second on, but if the version is less that 0.9.9. and net-libs/nodejs-0.9.9 is not less than net-libs/nodejs-0.9.9, therefore it emerges it. _________________ read the portage output!
If my answer is too concise, ask for an explanation. |
|
Back to top |
|
|
MikeSummers n00b
Joined: 31 May 2003 Posts: 38 Location: Kansas City
|
Posted: Wed Feb 13, 2013 3:38 pm Post subject: |
|
|
Ah, sorry for being so dense about this, my thinking about "mask" was inverted... and the setting in keywords works as it's really an unmask.
Thanks. |
|
Back to top |
|
|
|