On Tue, Apr 22, 2008 at 03:14:11PM +1200, Francois Marier wrote:
> I renamed a tarball from logstalgia-0.9.0a.orig.tar.gz to
> logstalgia_0.9.0a.orig.tar.gz
> before running git-import-orig on it and unfortunately the upstream version
> was picked up
> as "0.9.0a.orig" instead of "0.9.0a".
I get: 0.9.0a as version with logstalgia_0.9.0a.orig.tar.gz:
^^^
py>
r=re.compile(r'^[a-z\d\-]+_(?P<version>[a-z\d\.\~\-]+)\.orig\.tar\.(gz|bz2)')
py> r.match('logstalgia_0.9.0a.orig.tar.gz').groupdict()
{'version': '0.9.0a'}
^^^^^^^^
for the correctly named tarball and I get:
with logstalgia-0.9.0a.orig.tar.gz:
^^^
py> r=re.compile(r'^[a-z\d\-]+-(?P<version>[a-z\d\.]+)\.tar\.(gz|bz2)')
py> r.match('logstalgia-0.9.0a.orig.tar.gz').groupdict()
{'version': '0.9.0a.orig'}
^^^^^^^^^^^^^
for the "incorrectly" named tarball.
This is expected since the later doesn't match the regex for Debian
upstream tarballs and so we use another regex for that (one that matches
what you usually download from upstream).
Did you expect anything different?
> Perhaps git-import-dsc should filter the ".orig" bit out.
^^^^^^^^^^^^^^
Just to be sure: you're talking only about git-import-orig here?
-- Guido
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
