Bug#802362: marked as done (devscripts: [uscan] does not select newer dir)

[Osamu Aoki]

Hi,

Thanks James for following up.  

On Tue, Oct 20, 2015 at 12:42:05AM +0000, Debian Bug Tracking System wrote:
> Here's a fixed watch line for you.
> 
>       http://www.drumgizmo.org/releases/drumgizmo-(.+?)/drumgizmo-(.+?)\.tar\.gz
> 
> Although below is even better.
> 
>       http://www.drumgizmo.org/releases/drumgizmo-([\d.]+?)/drumgizmo-([\d.]+?)\.tar\.gz

These are good points for reminder in manpage.

Use as tight regex as possible with .+? or even better [\d\.]+?

These are good rules but quite frankly, I am feeling a bit strange for
this log reported in the bug.

  Found the following matching hrefs: drumgizmo-0.9.8.tar.gz (0.9.8) uscan
  debug: new version 0.9.8 uscan debug: new filename
  drumgizmo-0.9.8.tar.gz uscan debug: filenamemangled new filename
  drumgizmo-0.9.8.tar.gz uscan debug: downloadurlmangled upstream URL
  http://www.drumgizmo.org/releases/
  drumgizmo-0.9.8/drumgizmo-0.9.8.tar.gz Newest version on remote site is
  0.9.8, local version is 0.9.8.1 => remote site does not even have
  current version --
  Scan finished

Why it finds 0.9.8 as the newest when 0.9.8.1 exists?

In my recent multitar branch work, I vaguly remember moving  sorting of
directory for sub newest_dir() or somewhere else.  

Can you elaborate what options are used and what was your local source
tree version.

When I find time, I will look into this.

Good night.

Osamu