Re: try to keep a watch file into your package
On Fri, 28 Jan 2005 13:05:56 +0100, Bluefuture [EMAIL PROTECTED] wrote: If there is no way, other than following mailing list, to know upstream version and the upstream author doesn't want to help you there is no way for dehs to follow upstream release, but this is not the case of apg. I think that this watch file works fine: version=2 http://www.adel.nursat.kz/apg/download.shtml download/apg-([^b]+)\.tar\.gz debian uupdate Yes, it works fine, even without the uupdate. A classic case of read the man page to its end. Thanks for the heads-up, apg's watch file is now fixed. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fon: *49 621 72739834
Re: try to keep a watch file into your package
Il giorno mer, 26-01-2005 alle 09:02 +0100, Free Ekanayaka ha scritto: Thanks for this effort. Would it make sense to support queries of dehs by maintainer email address? This ways it would be easier for people to check the status of their own packages. This functionality is already implemented at http://dehs.alioth.debian.org Cheers, Blue -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: try to keep a watch file into your package
What do you do with packages that have uncooperative upstream and thus a watch file is not possible? apg's web host, for example, doesn't support directory listings, so I had to resort on checking the fingerprint of the download web page to find out whether there is a new release. Greetings Marc If there is no way, other than following mailing list, to know upstream version and the upstream author doesn't want to help you there is no way for dehs to follow upstream release, but this is not the case of apg. I think that this watch file works fine: version=2 http://www.adel.nursat.kz/apg/download.shtml download/apg-([^b]+)\.tar\.gz debian uupdate Cheers, Blue -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: try to keep a watch file into your package
|--== bluefuture writes: b Il giorno mer, 26-01-2005 alle 09:02 +0100, Free Ekanayaka ha scritto: Thanks for this effort. Would it make sense to support queries of dehs by maintainer email address? This ways it would be easier for people to check the status of their own packages. b This functionality is already implemented at http://dehs.alioth.debian.org Ooops, I missed it! Thanks. Cheers, Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: try to keep a watch file into your package
|--== bluefuture writes: b The dehs system now is regular running again every two days on alioth b (and so also on the info feed to developer.php on qa). b Looking at no_watch page[1] there are: b Total source packages without watch file: 6324 b Total source packages: 8285 b %: 76,33% b But seems also that there are: b 1621 packages that had no watch filel had a dehs automatic generated b watch file that had passed uscan test. b If every developer could download, check and if necessary fix the b automatic generated watch file and the put the file in his package b source we could fix the info in developers.php and the status on dehs b for some of the 6324 packages without watch file. b Every developer could find his automatic generated watch file going on b his dehs own maintainer/package page from dehs homepage[2] on alioth. Thanks for this effort. Would it make sense to support queries of dehs by maintainer email address? This ways it would be easier for people to check the status of their own packages. Cheers, Free -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: try to keep a watch file into your package
On Tue, 25 Jan 2005 13:28:16 +0100, Bluefuture [EMAIL PROTECTED] wrote: Native packages are already not included in the dehs system. What do you do with packages that have uncooperative upstream and thus a watch file is not possible? apg's web host, for example, doesn't support directory listings, so I had to resort on checking the fingerprint of the download web page to find out whether there is a new release. Greetings Marc -- -- !! No courtesy copies, please !! - Marc Haber |Questions are the | Mailadresse im Header Mannheim, Germany | Beginning of Wisdom | http://www.zugschlus.de/ Nordisch by Nature | Lt. Worf, TNG Rightful Heir | Fon: *49 621 72739834
Re: try to keep a watch file into your package
Il giorno mar, 25-01-2005 alle 07:49 +0100, Goswin von Brederlow ha scritto: Bluefuture [EMAIL PROTECTED] writes: The dehs system now is regular running again every two days on alioth (and so also on the info feed to developer.php on qa). Looking at no_watch page[1] there are: Total source packages without watch file: 6324 Total source packages: 8285 %: 76,33% What is the number if you exclude native packages? Native packages are already not included in the dehs system. MfG Goswin -- Bluefuture [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: try to keep a watch file into your package
Il giorno mar, 25-01-2005 alle 13:56 +0100, Wouter Verhelst ha scritto: I'm not convinced having a watch file is always useful. I agree with you. I would hope a maintainer would follow the announcements of the software I agree with this. Dehs/Watch is not a system for bypassing upstream mailing list, announcement, chat. he packages and upload only its latest stable upstream version, as opposed to just the latest version, whatever that may be; and that the maintainer would only upload a new upstream version if the change is meaningful (for instance, if a new upstream version only includes changes relevant for, say, the FreeBSD and Microsoft Windows ports of their application, it's useless to upload the latest version). If there are other (more detailed and reliable) ways of finding out what the latest upstream version is, having a watch file isn't really necessary. As you can see on alioth pages, dehs, for packages with a valid (or automatic generated watch file) try to keep the upstream changelog/news from the new upstream version not in sync with debian version, as you can see by clicking upstream version number (where available)[1] or on your maintainer/package page on dehs.alioth. As another point, I myself have become the upstream maintainer of the NBD tools since about a year now, IIRC (while I have been maintaining packages for NBD since July 2001 or so). I could have changed the NBD packages to be native ones, but I opted not to do so; however, since I release them myself, I'm quite aware when there is a new NBD upstream package. Having a watch file is unnecessary bloat, then. In this cases watch file (if the package doesn't become native) could be intended as an info tool for debian user community and for all other developer that are not the maintainer or the upstream author of your package (this is another goal of dehs i hope). These are just two examples where having a watch file isn't really necessary; I can imagine that there are a lot more. That's not to say that your effort isn't appreciated or that it is even completely useless; only that it is to be remembered that a watch file, while often useful, isn't always necessary and might in some cases even be a bad idea. Considering the above, if 76% of packages do have a watch file and the other 24% do not, it might be reasonable to assume that a high number of those that do not yet have a watch file do not actually need one. The problem is that 76% of packages doesn't had a watch file and only the 24% had one. Of course, as I said, this does not have to mean that /none/ of those packages actually do not need a watch file; in fact, I just downloaded the automatically generated watch file for one of my other packages where a watch file /is/ useful (since the upstream maintainer doesn't do announcements) ;-) There is always, as above, the second Dehs goals as an info tools for user and other developers that doesn't maintain your package and for this reason doesn't follow the upstream mailing list/announcement developing activity. Cheers, Blue [1] http://dehs.alioth.debian.org/no_updated.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: try to keep a watch file into your package
Bluefuture [EMAIL PROTECTED] writes: The dehs system now is regular running again every two days on alioth (and so also on the info feed to developer.php on qa). Looking at no_watch page[1] there are: Total source packages without watch file: 6324 Total source packages: 8285 %: 76,33% What is the number if you exclude native packages? MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
