Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 353649 - portage-2.2.0-alpha19 - Wildcard atoms do not support version operators and SLOT handling is buggy
Summary: portage-2.2.0-alpha19 - Wildcard atoms do not support version operators and S...
Status: CONFIRMED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Configuration (show other bugs)
Hardware: All Linux
: High normal with 1 vote (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on: 402197
Blocks:
  Show dependency tree
 
Reported: 2011-02-04 00:09 UTC by Matthias Maier
Modified: 2012-10-20 17:27 UTC (History)
0 users

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 Matthias Maier gentoo-dev 2011-02-04 00:09:52 UTC
The wildcard handling in portage.keywords is not consistent.
An example:

tamiko@bluebird ~ % eix -I libkdepim
[D] kde-base/libkdepim
     Available versions:  (4.4) 4.4.5 ~4.4.6 4.4.7 4.4.8 4.4.9!t ~4.4.10!t

So version 4.4.10 of branch 4.4 has an ~amd64-keyword.

It is possible to unmask version 4.4.10 by

  kde-base/libkdepim ~amd64
  kde-base/* ~amd64
  */libkdepim ~amd64
  */* ~amd64
  kde-base/libkdepim::gentoo ~amd64
  kde-base/*::gentoo ~amd64
  (etc..)

in package.keywords so that a

  # emerge -1p "=kde-base/libkdepim-4.4.10"

succeeds.

However:

  kde-base/*:4.5  

incorrectly unmasks the package in emerge. (kde-base/libkdepim:4.5 is handled correctly).

Furthermore

  =kde-base/*-4.4.10 

is handled as a bad package atom by emerge.

app-portage/eix does handle this two cases correctly. (Or differently - whatever the definition of correctly might be ;-) )

Reproducible: Always

Steps to Reproduce: