Debian watch file doesn't work

Bug #180131 reported by Miguel Ruiz
4
Affects Status Importance Assigned to Milestone
gshutdown (Ubuntu)
Fix Released
Low
Luca Falavigna

Bug Description

Binary package hint: gshutdown

According to http://qa.ubuntuwire.com/uehs/no_upstream.php this package has problems to execute uscan (wrong syntax in debian watch file).

Related branches

Miguel Ruiz (mruiz)
Changed in gshutdown:
assignee: nobody → mruiz
status: New → In Progress
assignee: mruiz → nobody
status: In Progress → Confirmed
Changed in gshutdown:
assignee: nobody → dktrkranz
importance: Undecided → Low
status: Confirmed → In Progress
Revision history for this message
Luca Falavigna (dktrkranz) wrote :

A test uscan run reported the following output:
dktrkranz@moses:~/gshutdown/gshutdown-0.2$ uscan --verbose --report
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile line:
   http://gshutdown.tuxfamily.org/release/gshutdown-(.*)\.tar\.gz debian uupdate
-- Found the following matching hrefs:
     gshutdown-0.1.tar.gz
     gshutdown-0.2.tar.gz
     gshutdown-0.2rc1.tar.gz
Newest version on remote site is 0.2rc1, local version is 0.2
 => Newer version available from
    http://gshutdown.tuxfamily.org/release/gshutdown-0.2rc1.tar.gz
-- Scan finished
dktrkranz@moses:~/gshutdown/gshutdown-0.2$

0.2 is greater than 0.2rc, but watch file considers it not up-to-date.
A temporary solution could be using ([0-9.]*) instead of (.*), but it will probably miss future release candidates.

Changed in gshutdown:
assignee: dktrkranz → mruiz
Revision history for this message
Miguel Ruiz (mruiz) wrote :

Hi Luca,

If we use ([0-9.]*) or ([\d\.]*) we have the following:

mruiz@hardy:~/devel/fixes/watch/gshutdown/gshutdown-0.2$ uscan -verbose
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile line:
   http://gshutdown.tuxfamily.org/release/gshutdown-([0-9.]*)\.tar\.gz debian uupdate
-- Found the following matching hrefs:
     gshutdown-0.1.tar.gz
     gshutdown-0.2.tar.gz
Newest version on remote site is 0.2, local version is 0.2
 => Package is up to date
-- Scan finished

This confirm your comment ... we missed a version (gshutdown-0.2rc1). What we should do ?

Cheers!

Revision history for this message
Luca Falavigna (dktrkranz) wrote :

I think we can use ([\d\.]*) safely. Since rc1 version is now obsolete and we are not sure new RCs will follow, we can ignore them for now unless a better regex is provided.

Revision history for this message
Miguel Ruiz (mruiz) wrote :

Luca:

I'm attaching a new solution; also dpkg saves the day again:

mruiz@platypus:~$ dpkg --compare-versions 0.2rc1 gt 0.2 ; echo $?
0

That means: 0.2rc1 is greater than 0.2 :S . Is a good solution to avoid RC versions for this package.

Cheers!

Revision history for this message
Daniel Holbach (dholbach) wrote :

Luca: will you take care of this one?

Revision history for this message
Luca Falavigna (dktrkranz) wrote :

Uploaded, thanks ;)

Changed in gshutdown:
assignee: mruiz → dktrkranz
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gshutdown - 0.2-0ubuntu2

---------------
gshutdown (0.2-0ubuntu2) hardy; urgency=low

  * debian/watch:
    + Updated download page syntax. (LP: #180131)
  * debian/rules:
    + Fixed a lintian warning (debian-rules-ignores-make-clean-error).

 -- Miguel Ruiz <email address hidden> Fri, 04 Jan 2008 22:48:55 -0300

Changed in gshutdown:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.