Bug 165349

Summary:	repoman's version verification doesn't match portage version rules
Product:	Portage Development	Reporter:	Brian Harring (RETIRED) <ferringb>
Component:	Repoman	Assignee:	Portage team <dev-portage>
Status:	RESOLVED FIXED
Severity:	normal	CC:	flameeyes
Priority:	High	Keywords:	InVCS
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	162453
Attachments:	patch to use portage.versions.ververify

Description Brian Harring (RETIRED) gentoo-dev

2007-02-04 22:06:31 UTC

repoman has it's own 'fun' set of regexes embedded into it for version verification; as such, it actually limits allowed versions to a rather old set of rules.

Comment 1 Brian Harring (RETIRED) gentoo-dev

2007-02-04 22:08:13 UTC

Created attachment 109178 [details, diff]
patch to use portage.versions.ververify

split against rev 5789; mangles repoman to use ververify instead of it's own homegrown regexes.

Comment 2 Diego Elio Pettenò (RETIRED) gentoo-dev

2007-02-04 22:09:55 UTC

And for practical use 101, I need this fixed for alsa-driver-1.0.14_rc2_p3234 ...

Comment 3 Zac Medico gentoo-dev

2007-02-05 00:01:06 UTC

Thanks, this is in svn r5888.

Comment 4 Marius Mauch (RETIRED) gentoo-dev

2007-02-05 10:49:00 UTC

Should note that this was done on purpose to prevent people from adding ebuilds that would only work with >=2.1 (and likely cause trouble with earlier versions). Not much of an issue though by now.

Comment 5 Zac Medico gentoo-dev

2007-02-05 23:19:42 UTC

(In reply to comment #4)
> Not much of an issue though by now.

I did some testing with 2.0.x and it seemed to handle it pretty well.

This has been released in 2.1.2-r8.