Discussion:
(masked by: missing keyword)
sean
2005-10-29 12:17:07 UTC
Permalink
What is the proper way to over ride a package that is (masked by:
missing keyword)?
From what I read it is supposed to be done with the package.keywords
file in /etc/portage.
But I must be doing something wrong with format.

Specifically I am trying to install openoffice 2.0 on my amd64 system. I
have unmasked it, but the keyword is still blocking me.

Thanks
Sean
--
gentoo-***@gentoo.org mailing list
Dale
2005-10-29 12:33:19 UTC
Permalink
This is how my unmasked packages looks:

net-www/netscape-flash ~x86
app-sci/foldingathome ~x86

Just replace with what applies to you of course. That is in
package.keywords file of course.

Dale
Post by sean
missing keyword)?
From what I read it is supposed to be done with the package.keywords
file in /etc/portage.
But I must be doing something wrong with format.
Specifically I am trying to install openoffice 2.0 on my amd64 system.
I have unmasked it, but the keyword is still blocking me.
Thanks
Sean
sean
2005-10-29 16:14:46 UTC
Permalink
Post by Dale
net-www/netscape-flash ~x86
app-sci/foldingathome ~x86
Hi Dale,

I can get it unmasked, I just can't clear the keyword.

This is what is currently in my keyword file.

app-office/openoffice -*
app-office/openoffice ~amd64

This is my unmask, which is working.
=app-office/openoffice-2.0.0

Thanks
Sean
--
gentoo-***@gentoo.org mailing list
Holly Bostick
2005-10-29 13:18:32 UTC
Permalink
missing keyword)? From what I read it is supposed to be done with the
package.keywords file in /etc/portage. But I must be doing something
wrong with format.
Specifically I am trying to install openoffice 2.0 on my amd64
system. I have unmasked it, but the keyword is still blocking me.
Thanks Sean
'Missing keyword' is a very specific state, different from masking,
keyword ~arch, or other kinds of blocks;
From packages.gentoo.org
openoffice
Description: OpenOffice.org, a full office productivity suite.
Releases alpha amd64 arm hppa ia64 mips ppc ppc64 ppc macos s390 sparc x86
2.0.0 - - - - - - ~ - -
- - ~

You see that "-" under the alpha, amd64, arm, hppa and all other
architectures than ppc and x86?

Those "-" are missing keywords. This package is only rated (as unstable)
for ppc and x86 architectures. On all other arches, the build is so
unstable, or so untested, that it is not keyworded at all.

Which is why the legend on p.g.o says

"- not available"

Now, if you really really want to test such a build in the name of
science, you can of course do so, but you will have to jump through a
hoop or two because you really are not meant to be using this package
unless you mean to help troubleshoot:

First thing to do is to add to /etc/portage/package.keywords:

app-office/openoffice -*

This will unmask the build with the missing keyword.

Try running the emerge again, but there's a fair likelihood that you
will hit a further mask, like package.mask.

If so, you should again consider if you *really* want to unmerge this
package; if it's masked up the wazoo, are you sure that you have the
time and energy to deal with the problems it apparently has, and help
solve them? If not, find an alternative (like openoffice-bin, which is
marked as unstable for amd64).

If so, then add the package to /etc/portage/package.unmask

=app-office/openoffice-2.0.0

and see how far you get.

Be warned, it's quite possible that the package will not compile, or
will have problems compiling-- openoffice is quite hard to compile under
the best of circumstances, and these are not them. There have been a lot
of changes, both in the program itself (hence the 2.0 version) and in
the supporting infrastructure (gtk libraries, freedesktop.org specs, X
itself not to mention the deeper backend libraries), and how these
things are going to interact on a 'sensitive' system architecture is
anybody's guess.

But of course, somebody has to take the plunge and report back for the
issue to progress any further, so if you want to do that, good luck.

If you don't want to do that, but rather just use the program, unmask
and install the bin package.

HTH,
Holly
--
gentoo-***@gentoo.org mailing list
sean
2005-10-29 16:14:30 UTC
Permalink
Post by Holly Bostick
missing keyword)? From what I read it is supposed to be done with the
package.keywords file in /etc/portage. But I must be doing something
wrong with format.
Specifically I am trying to install openoffice 2.0 on my amd64
system. I have unmasked it, but the keyword is still blocking me.
Thanks Sean
'Missing keyword' is a very specific state, different from masking,
keyword ~arch, or other kinds of blocks;
From packages.gentoo.org
openoffice
Description: OpenOffice.org, a full office productivity suite.
Releases alpha amd64 arm hppa ia64 mips ppc ppc64 ppc macos s390 sparc x86
2.0.0 - - - - - - ~ - -
- - ~
You see that "-" under the alpha, amd64, arm, hppa and all other
architectures than ppc and x86?
Those "-" are missing keywords. This package is only rated (as unstable)
for ppc and x86 architectures. On all other arches, the build is so
unstable, or so untested, that it is not keyworded at all.
Which is why the legend on p.g.o says
"- not available"
Now, if you really really want to test such a build in the name of
science, you can of course do so, but you will have to jump through a
hoop or two because you really are not meant to be using this package
app-office/openoffice -*
This will unmask the build with the missing keyword.
Try running the emerge again, but there's a fair likelihood that you
will hit a further mask, like package.mask.
If so, you should again consider if you *really* want to unmerge this
package; if it's masked up the wazoo, are you sure that you have the
time and energy to deal with the problems it apparently has, and help
solve them? If not, find an alternative (like openoffice-bin, which is
marked as unstable for amd64).
If so, then add the package to /etc/portage/package.unmask
=app-office/openoffice-2.0.0
and see how far you get.
Be warned, it's quite possible that the package will not compile, or
will have problems compiling-- openoffice is quite hard to compile under
the best of circumstances, and these are not them. There have been a lot
of changes, both in the program itself (hence the 2.0 version) and in
the supporting infrastructure (gtk libraries, freedesktop.org specs, X
itself not to mention the deeper backend libraries), and how these
things are going to interact on a 'sensitive' system architecture is
anybody's guess.
But of course, somebody has to take the plunge and report back for the
issue to progress any further, so if you want to do that, good luck.
If you don't want to do that, but rather just use the program, unmask
and install the bin package.
HTH,
Holly
Hi Holly,

I can get it unmasked, I just can't clear the keyword.

This is what is currently in my keyword file.

app-office/openoffice -*
app-office/openoffice ~amd64

This is my unmask, which is working.
=app-office/openoffice-2.0.0

Thanks
Sean
--
gentoo-***@gentoo.org mailing list
Holly Bostick
2005-10-29 16:32:41 UTC
Permalink
Post by sean
Hi Holly,
I can get it unmasked, I just can't clear the keyword.
This is what is currently in my keyword file.
app-office/openoffice -* app-office/openoffice ~amd64
This is my unmask, which is working. =app-office/openoffice-2.0.0
Thanks Sean
Ha (not laughing at you)-- this is a silly mistake that I know is silly
because I've made it myself until I figured out the trick.

Put both unmasks on the same line.

The second line is overriding the first (masks, like keywords and USE
flags) are not cumulative over subsequent entries.

If you do it like this
Post by sean
app-office/openoffice -*
app-office/openoffice ~amd64
The first line unmasks just the -*, then the second line remasks
everything and unmasks amd64.

But if you do it like this
Post by sean
app-office/openoffice -* ~amd64
both masks will be unmasked.

Hope this helps.

Holly
--
gentoo-***@gentoo.org mailing list
Ciaran McCreesh
2005-10-29 20:40:14 UTC
Permalink
On Sat, 29 Oct 2005 08:17:07 -0400 sean <***@comcast.net> wrote:
| Specifically I am trying to install openoffice 2.0 on my amd64
| system. I have unmasked it, but the keyword is still blocking me.

Unmasking it won't do you any good. It won't work.
--
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
Tim Kruse
2005-10-31 01:00:03 UTC
Permalink
Post by sean
missing keyword)?
The only way I know of is to change the ebuild. But don't do
this on the ebuild in your normal portage dir (it will be
overridden after the next sync). Copy the ebuild to
'${PORTDIR_OVERLAY}/category/name/package.ebuild' and do your
changes there (in this case
'${PORTDIR_OVERLAY}/app-office/openoffice/openoffice-2.0.0.ebuild')

Now you have to add your architecture into the KEYWORDS variable
(here: KEYWORDS="amd64") and it should work. (Perhaps you have to
update your portage cache, I don't know).

But, as Ciaran said, don't do it with openoffice-2.0.0, because
it won't work under amd64.
Post by sean
From what I read it is supposed to be done with the package.keywords
file in /etc/portage.
But I must be doing something wrong with format.
I'm not really sure, but you can't unmask packages marked by
missing keyword with any of these files in /etc/portage
(specially /etc/portage/package.keywords) IIRC. With these files
you can unmask packages masked by
/usr/portage/profiles/package.unmask (/etc/portage/package.mask)
or marked testing in the ebuild (~amd64) if are running a stable
gentoo (read: set ACCEPT_KEYWORDS="amd64" in /etc/make.conf)
(/etc/portage/package.keywords)

You can do lots more here. Read 'man portage' for details.
Post by sean
Specifically I am trying to install openoffice 2.0 on my amd64 system. I
have unmasked it, but the keyword is still blocking me.
As mentioned above it won't work.

So long,
tkr
--
You can't hurt me!! I have an ASSUMABLE MORTGAGE!!
Loading...