Hi, On Fri, 2008-09-12 at 19:15 +0200, Daniel Leidert wrote: > Please check the attached watch file. If I run it, it says: > > Newest version on remote site is 0.0.21, local version is > .*/xmlto-([\d\.]+)\.tar\.bz2 > > Well, the so called "local version" is part of the watch file and not > part of debian/changelog. How can it be the _local_ version? > > I'm not sure, if my pattern maybe catched a case, which is not yet > supported. In this case, please tell me. However, the local version > should not be poisoned by a part of the debian/watch file.
As far as I can see, uscan is behaving exactly as documented, albeit not as would be useful to you. Apologies for the slightly verbose quote: [uscan(1)] In the case of an HTTP site, the URL obtained by stripping everything after the trailing slash will be downloaded and searched for hrefs (links of the form <a href=...>) to either the full URL pattern given, or to the absolute part (everything without the http://host.name/ part), or to the basename (just the part after the final ‘/’). Everything up to the final slash is taken as a verbatim URL, as long as there are no parentheses (‘(’ and ’)’) in this part of the URL: if it does, the directory name will be matched in the same way as the final component of the URL as described below. [...] The pattern (after the final slash) is a Perl regexp [...] The current (upstream) version can be specified as the second parameter in the watchfile line. [/uscan(1)] i.e. the URL "https://fedorahosted.org/xmlto/browser/"; is retrieved and searched for hrefs matching "xmlto-([\d\.]+)\.tar\.bz2". The href with the highest version number is then retrieved. The URL form you've used is equivalent to "https://fedorahosted.org/xmlto/browser/ xmlto-([\d\.]+)\.tar\.bz2"; i.e. it contains two parameters, albeit written as a single parameter. As per the above quote, the next parameter is therefore the current version number - the local version isn't being "polluted" by the pattern in the watch file, rather the watch file is specifying that the pattern *is* the local version. In summary, I don't think uscan currently supports the multiple levels of indirection used by the trac browser on that site; I'm happy for someone to prove me wrong however :-). I also don't think the error message is a bug, as explained above, although I appreciate that its somewhat confusing in this case until you break down how the watchfile is being parsed. Regards, Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
