Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 584598 - app-portage/gentoolkit: eshowkw treats ebuilds with KEYWORDS="arch ~arch" as unstable
Summary: app-portage/gentoolkit: eshowkw treats ebuilds with KEYWORDS="arch ~arch" as ...
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Third-Party Tools (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage Tools Team
URL: https://projects.gentoo.org/pms/6/pms...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-30 20:12 UTC by Chí-Thanh Christopher Nguyễn
Modified: 2023-03-31 18:27 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chí-Thanh Christopher Nguyễn gentoo-dev 2016-05-30 20:12:21 UTC
Some packages like media-libs/elementary-1.17.0 set
KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sh ~sparc ~x86 ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~x86-interix ~x86-solaris ~x64-solaris amd64 x86" (in part via the eclass, but that is handled in bug 486392)

https://gitweb.gentoo.org/repo/gentoo.git/tree/media-libs/elementary/elementary-1.17.0.ebuild?id=dc476a8696977481fd245254220c1ad334dd8287

This apparently confuses ekeywords, who considers this package unstable, while emerge and eix consider it stable. repoman considers it unstable too.

PMS section 7.3.2 doesn't explicitly allow or forbid multiple keywords for the same arch.
Comment 1 Zac Medico gentoo-dev 2016-12-29 21:31:16 UTC
If the stable keyword is present, it should be safe for tools to ignore the corresponding unstable keyword, but we probably want repoman to at least give a warning message.
Comment 2 Diego Viola 2023-03-18 14:50:51 UTC
I think I experienced the same issue with enalyze, for example, `enalyze rebuild keywords` returns "app-misc/ranger ~amd64" among other things.

This doesn't make any sense because app-misc/ranger is stable, but when looking at the ebuild the keywords are "amd64 ~ppc ~riscv x86".
Comment 3 Diego Viola 2023-03-30 17:26:33 UTC
(In reply to Diego Viola from comment #2)
> I think I experienced the same issue with enalyze, for example, `enalyze
> rebuild keywords` returns "app-misc/ranger ~amd64" among other things.
> 
> This doesn't make any sense because app-misc/ranger is stable, but when
> looking at the ebuild the keywords are "amd64 ~ppc ~riscv x86".

I am unable to reproduce this on a fresh (stable) Gentoo install now.
Comment 4 Diego Viola 2023-03-30 20:30:45 UTC
I read that the tool will "show you what WAS installed, and then what WOULD be installed"... so this makes sense, I switched to ~amd64 (globally) and back several times, so if this is true, it makes sense why it appeared ~amd64 for app-misc/ranger and other packages.
Comment 5 Diego Viola 2023-03-31 05:32:05 UTC
(In reply to Diego Viola from comment #3)
> (In reply to Diego Viola from comment #2)
> > I think I experienced the same issue with enalyze, for example, `enalyze
> > rebuild keywords` returns "app-misc/ranger ~amd64" among other things.
> > 
> > This doesn't make any sense because app-misc/ranger is stable, but when
> > looking at the ebuild the keywords are "amd64 ~ppc ~riscv x86".
> 
> I am unable to reproduce this on a fresh (stable) Gentoo install now.

I am able to reproduce this after bumping e.g. /var/db/pkg/app-misc/ranger-1.9.3-r1/KEYWORDS (amd64 -> ~amd64).
Comment 6 Diego Viola 2023-03-31 18:27:30 UTC
Sorry for the confusion but I had a similar issue with enalyze, for some reason I assumed it was the same issue as this one, apparently it isn't. I can't reproduce this bug.