Re: Need help writing watch file for unusual, troublesome case.
> This is a good starting point. Using filenamemangle anddownloadurlmangle you > can use the above for a working > watch file. Iattached it. As long as upstreams stays with this scheme > (besides it isa dead project), this should > work. Thank you for the watch file, Daniel. My primary machine is having some technical problems, so I can't test it out right now, but I will include it in the next xevil release. -Brandon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Need help writing watch file for unusual, troublesome case.
Am Dienstag, den 02.09.2008, 16:31 -0700 schrieb Brandon: > Creating a separate script wouldn't really make much sense in my case. > I was only fixing the watch file as a formality. Upstream is dead, so I > wouldn't be using it, but it would satisfy projects like dehs, and my > QA page warns me about my broken watch file. > > I think I will just use the watch file that I mentioned in my original > post. This one: > version=3 > http://www.xevil.com/xevil/dev/download.html (.*)/download_stable.shtml This is a good starting point. Using filenamemangle and downloadurlmangle you can use the above for a working watch file. I attached it. As long as upstreams stays with this scheme (besides it is a dead project), this should work. Regards, Daniel watch Description: application/fluid
Re: Need help writing watch file for unusual, troublesome case.
* Brandon <[EMAIL PROTECTED]> [080902 22:31]: > Also, xevil is a dead project. The latest release was years ago, and > Satan doesn't respond to email. Would you guys recommend not having a > watch file? I think especially with dead upstream a watch file is usefull. If upstream is active and knows you exists or you are on the webpage from time to time, then you will notice yourself. If upstream just wakes up, puts a new version and vanishes again then a watch file is almost the only chance you have to detect it... Also email addresses often change, sometimes it helps to look for other projects of the same person to see if there are other addresses now (sometimes there is even a mailinglist there also dedicated to the old project but not listed on the old project page directly). Hochachtungsvoll, Bernhard R. Link -- "Never contain programs so few bugs, as when no debugging tools are available!" Niklaus Wirth -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Need help writing watch file for unusual, troublesome case.
On Wed, Sep 3, 2008 at 4:30 AM, Brandon <[EMAIL PROTECTED]> wrote: > Also, xevil is a dead project. The latest release was years ago, and > Satan doesn't respond to email. Would you guys recommend not having a > watch file? Even if so, I would really like to know how I would solve > this problem, if it needed solving. For the future. Having dead projects in Debian isn't really a good idea, please fork the upstream code. I saw the comment at the bottom of this page, you might want to contact that guy to get him to help out: http://freshmeat.net/projects/xevil/ Please put it on one of the public project hosting sites (gna/savannah/sf/launchpad) so it can be more easily hijacked if you abandon it in the future. Please also use a DVCS like git so that it is easier for external people to backup the version control history. Also, you might want to join the Debian Games Team if you haven't already and maintain the packaging there. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Need help writing watch file for unusual, troublesome case.
Brandon <[EMAIL PROTECTED]> writes: > I have one more question about watch files. If I were to delete the > watch file (maybe upstream website will be taken down in the future?), > is there anything special I should do to override the missing > watch file warnings? Is there a signal to sites like dehs that a watch > file would be inappropriate for a specific project? I'm of the opinion that the right solution in such cases is not to override the warning, but to make the watch file consist entirely of comments explaining the situation. DEHS and lintian will both handle that correctly (i.e. not complain), and DEHS will use the comments as an explanation on the generated web page. -- \ "The opposite of a correct statement is a false statement. But | `\ the opposite of a profound truth may well be another profound | _o__) truth." —Niels Bohr | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Need help writing watch file for unusual, troublesome case.
Creating a separate script wouldn't really make much sense in my case. I was only fixing the watch file as a formality. Upstream is dead, so I wouldn't be using it, but it would satisfy projects like dehs, and my QA page warns me about my broken watch file. I think I will just use the watch file that I mentioned in my original post. This one: version=3 http://www.xevil.com/xevil/dev/download.html (.*)/download_stable.shtml It won't download the latest version (it downloads download_stable.shtml) But it checks the version just fine. I'll make a note in the watch file, saying what it can do, what it can't, and why that should be OK. Thanks for your help. If anyone knows how to make my watch file download the correct file, that would be great. I think it is impossible, though. I have one more question about watch files. If I were to delete the watch file (maybe upstream website will be taken down in the future?), is there anything special I should do to override the missing watch file warnings? Is there a signal to sites like dehs that a watch file would be inappropriate for a specific project? -Brandon signature.asc Description: PGP signature
Re: Need help writing watch file for unusual, troublesome case.
You are correct: my solution obviously doesn't work, since I didn't read carefully enough. > This would be an easy problem to solve with a script. It would just be > a few lines, and not much hassle. Russ Allbery's blog suggests a get-orig-source debian/rules target that he uses for packaging his own scripts: http://www.eyrie.org/~eagle/notes/debian/build-tools.html#scripts I'm not sure if this is kosher with regards to the debian/rules file of a package meant to go into the actual Debian archive, but it's at least something to consider if you want to script the grabbing of the file, which debian/watch of course does not support. Daniel Moerner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Need help writing watch file for unusual, troublesome case.
On Tue, 2 Sep 2008 14:25:04 -0700 "Daniel Moerner" <[EMAIL PROTECTED]> wrote: > I think your approach to the debian/watch file is sort of off, which > explains why it isn't working. You want to point it to a webpage > where it can get hrefs that match the given regular expression, so you > want the website to actually be specified as download_stable.shtml. > Something like this basically works and can be fine-tuned with a > better match for the source package: > > version=3 > http://www.xevil.com/xevil/dev/2.02r2/download_stable.shtml \ >(.*)\.zip > > This complains about the version name but at least works: > > -- Scanning for watchfiles in . > -- Found watchfile in ./debian > -- In debian/watch, processing watchfile line: > http://www.xevil.com/xevil/dev/2.02r2/download_stable.shtml > (.*)\.zip -- Found the following matching hrefs: > http://www.xevil.com/download/stable/xevilsrc2.02r2.zip > dpkg: version 'http://www.xevil.com/download/stable/xevilsrc2.02r2' > has bad syntax: epoch in version is not number > Newest version on remote site is > http://www.xevil.com/download/stable/xevilsrc2.02r2, local version is > 2.02r2 > dpkg: version 'http://www.xevil.com/download/stable/xevilsrc2.02r2' > has bad syntax: epoch in version is not number > => Newer version available from >http://www.xevil.com/download/stable/xevilsrc2.02r2.zip > -- Downloading updated package xevilsrc2.02r2.zip > -- Successfully downloaded updated package xevilsrc2.02r2.zip > -- Scan finished > > Cheers, > Daniel Moerner The watch file you suggest has more problems than you noticed. 1) Did you notice how your watch line actually includes the current version number? 2.02r2? That won't work for (hypothetical) future versions. 2) uscan complains about the version name because it is wrong. We can fix it by using this line instead: http://www.xevil.com/xevil/dev/2.02r2/download_stable.shtml \ http://www.xevil.com/download/stable/xevilsrc(.*).zip Unfortunately, this "fix" still has the problem of the current version number (2.02r2) being in the watch file. The whole reason I'm trouble is because you have to download http://www.xevil.com/xevil/dev/download.html in order to know what the latest version is, and the xevil source archive is not mentioned on that page. This would be an easy problem to solve with a script. It would just be a few lines, and not much hassle. Unfortunately, watch files, being very simple, seem to be completely unable to solve the partiular instance where both of the following are true (such as in this case) 1) Directory listings on upstream server are forbidden 2) Source archive is not mentioned in href on page where you find out the latest version number I think this problem may be unsolvable, short of creating a new watch file format (version 4). -Brandon signature.asc Description: PGP signature
Re: Need help writing watch file for unusual, troublesome case.
I think your approach to the debian/watch file is sort of off, which explains why it isn't working. You want to point it to a webpage where it can get hrefs that match the given regular expression, so you want the website to actually be specified as download_stable.shtml. Something like this basically works and can be fine-tuned with a better match for the source package: version=3 http://www.xevil.com/xevil/dev/2.02r2/download_stable.shtml \ (.*)\.zip This complains about the version name but at least works: -- Scanning for watchfiles in . -- Found watchfile in ./debian -- In debian/watch, processing watchfile line: http://www.xevil.com/xevil/dev/2.02r2/download_stable.shtml (.*)\.zip -- Found the following matching hrefs: http://www.xevil.com/download/stable/xevilsrc2.02r2.zip dpkg: version 'http://www.xevil.com/download/stable/xevilsrc2.02r2' has bad syntax: epoch in version is not number Newest version on remote site is http://www.xevil.com/download/stable/xevilsrc2.02r2, local version is 2.02r2 dpkg: version 'http://www.xevil.com/download/stable/xevilsrc2.02r2' has bad syntax: epoch in version is not number => Newer version available from http://www.xevil.com/download/stable/xevilsrc2.02r2.zip -- Downloading updated package xevilsrc2.02r2.zip -- Successfully downloaded updated package xevilsrc2.02r2.zip -- Scan finished Cheers, Daniel Moerner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Need help writing watch file for unusual, troublesome case.
On Tue, 02 Sep 2008, Brandon wrote: > The current upstream is: > http://www.xevil.com/download/stable/xevilsrc2.02r2.zip > Unfortunatley, the following watch line won't work: > http://www.xevil.com/download/stable/xevilsrc(*.).zip > because directory listings are (403) forbidden. > > Also, xevil is a dead project. The latest release was years ago, and > Satan doesn't respond to email. Would you guys recommend not having a > watch file? Even if so, I would really like to know how I would solve > this problem, if it needed solving. For the future. > > -Brandon Hi Brandon, If xevil is a 'dead project' having a watch file that doesn't do anything isn't very helpful either. Instead consider adding a lintian override or an empty watch file explaining why the watchfile is missing. BTW, IANADD, so listen to other opinions before doing something. Regards, Mauro -- JID: [EMAIL PROTECTED] http://lusers.com.ar/ 2B82 A38D 1BA5 847A A74D 6C34 6AB7 9ED6 C8FD F9C1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
