Summary: | portage incorrectly matches certain atoms when using =...* | ||
---|---|---|---|
Product: | Portage Development | Reporter: | SpanKY <vapier> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 472632 |
Description
SpanKY
2013-04-29 03:53:54 UTC
another example: c/a-1 != =c/a-1.0* imo, that should match, but portage doesn't think so currently (In reply to SpanKY from comment #1) > another example: > c/a-1 != =c/a-1.0* > > imo, that should match, but portage doesn't think so currently Well, PMS specifies "string prefix comparison" for this case: http://dev.gentoo.org/~ulm/pms/5/pms.html#x1-840008.2.6.1 (In reply to SpanKY from comment #0) > while writing some code in qpkg for testing version atoms, i noticed portage > gets this scenario wrong: > $ python -c 'import portage; > print portage.dep.match_from_list("=c/p-1-r1*", ["c/p-1_alpha1"])' > ['c/p-1_alpha1'] > that should of course be [] This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=889e19d27ac978dbbc9699bac152657675569ebd This is fixed in 2.1.12.4 and 2.2.0_alpha179. For comment #1, we might consider revising PMS? |