Hi,
On Thu, Apr 02, 2015 at 12:26:13PM +0200, Vincent Prat wrote:
This morning I found out that a new release (0.2.4) of astroquery
was out on pypi, so I ran uscan to get the last source tarball.
Surprisingly, another version was downloaded: 0.3.dev2794.
Indeed, this version is more recent, but it looks like a development
release.
What should I do? Ignore the dev release, or use it?
If I have to ignore it, how can I do this using the watch file?
For me it is quite unusual to regard dev/beta/alpha in d/watch but
I have no idea about the motivation of the author of this file. The
following very primitive change:
$ git diff
diff --git a/debian/watch b/debian/watch
index d6d7d78..2131bc2 100644
--- a/debian/watch
+++ b/debian/watch
@@ -1,4 +1,4 @@
version=3
opts=dversionmangle=s/\+dfsg\d*//,\
uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/ \
- http://pypi.debian.net/astroquery/astroquery-(\d\S*)\.tar\.gz
+ http://pypi.debian.net/astroquery/astroquery-(\d[.prec\d]*)\.tar\.gz
will lead to:
$ uscan --verbose --report
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile line:
opts=dversionmangle=s/\+dfsg\d*//,uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/ http://pypi.debian.net/astroquery/astroquery-(\d[.prec\d]*)\.tar\.gz
-- Found the following matching hrefs:
/astroquery/astroquery-0.1.tar.gz (0.1)
/astroquery/astroquery-0.2.tar.gz (0.2)
/astroquery/astroquery-0.2.1.tar.gz (0.2.1)
/astroquery/astroquery-0.2.2.tar.gz (0.2.2)
/astroquery/astroquery-0.2.3.tar.gz (0.2.3)
/astroquery/astroquery-0.2.4.tar.gz (0.2.4)
Newest version on remote site is 0.2.4, local version is 0.2.3+dfsg
(mangled local version number 0.2.3)
=> Newer version available from
http://pypi.debian.net/astroquery/astroquery-0.2.4.tar.gz
-- Scan finished
and thus should solve your problem. It should be discussed what kind of
"releases" you really want to track in d/watch and implement this in the
watch file propely.
Hope this helps
Andreas.