Bug#647079: whatsnewfm: New name and URL for freshmeat.net (parser broken)
The unstable package has been fixed and an updated package has just been submitted for stable. And I just released, that I now have two versions calles 0.7.2-1 -- the first fixed version for unstable and the new minimal fix for stable. Should I change it to something like 0.7.2-1stable? Or is this handled by the distribution field? I ended up changing the stable version number to 0.7.2-0+squeeze1 but the git repo now reflects this (and I've corrected the tags in there too). I did not even change the package description, so it still says freshmeat.net, is that ok? The release managers suggested that we fix that as well, so I've renamed the URL in the package description too. Cheers, Francois signature.asc Description: Digital signature
Bug#647079: whatsnewfm: New name and URL for freshmeat.net (parser broken)
Hi Francois, On Sat, Nov 05, 2011 at 11:37:17PM +1300, Francois Marier wrote: On 2011-11-01 at 13:51:25, Christian Garbs wrote: Now I'm looking for somebody to sponsor my upload. I'm happy to sponsor this upload, but I think you might want to fix a few minor things first: Ooops, I ran the new build under stable, not in my sid-chroot. If fixed those minor things and some more. I would have submitted a pull request for these, but I don't think you have a public packaging repo :) Now there is one and you have write access :) https://github.com/mmitch/whatsnewfm-debian The branches are as follows: master: Main development in unstable. squeeze: The backported fix for squeeze/stable. cgarbs.de: Squeeze rebuild for my personal repository. For unstable, I've provided the following packages: http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-2_all.deb http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-2.diff.gz http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-2.dsc http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-2_i386.build http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-2_i386.changes http://www.cgarbs.de/tmp/whatsnewfm_0.7.2.orig.tar.gz I'd be happy if you would sponsor them. What has to be done to get this update into stable (or volatile)? Currently the package is completely unusuable, waiting for the next stable release is not really an option. For stable (and/or squeze-updates, which is the new name for volatile), what you'd need I think is a package where the only change is the new upstream version (no other changes to the packaging). On the squeeze branch, I took the old squeeze package and simply updated the upstream package. I did not even change the package description, so it still says freshmeat.net, is that ok? And I just released, that I now have two versions calles 0.7.2-1 -- the first fixed version for unstable and the new minimal fix for stable. Should I change it to something like 0.7.2-1stable? Or is this handled by the distribution field? If you give the OK, I will build the packages, sign them and post the URLs here. Then I believe you need to let debian-release know about the package so that they can approve it http://lists.debian.org/debian-release/ before it gets uploaded to a different queue. If you prepare the package, I can take care of this part if you like. This would be great! Thanks Christian -- Christian.Garbs.http://www.cgarbs.de Good health is merely the slowest rate at which one can die. signature.asc Description: Digital signature
Bug#647079: whatsnewfm: New name and URL for freshmeat.net (parser broken)
Hi Christian, On 2011-11-01 at 13:51:25, Christian Garbs wrote: Official Debian packages are prepared for uploading: (these links time out in 30 days): http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-1.diff.gz http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-1.dsc http://www.cgarbs.de/tmp/whatsnewfm_0.7.2.orig.tar.gz Now I'm looking for somebody to sponsor my upload. I'm happy to sponsor this upload, but I think you might want to fix a few minor things first: 1- in the package description, there is a typo in the new URL: freecode.net - freecode.com 2- Standards-Version should now be 3.9.2 3- you could make the urgency medium to speed up the wheezy transition I would have submitted a pull request for these, but I don't think you have a public packaging repo :) What has to be done to get this update into stable (or volatile)? Currently the package is completely unusuable, waiting for the next stable release is not really an option. For stable (and/or squeze-updates, which is the new name for volatile), what you'd need I think is a package where the only change is the new upstream version (no other changes to the packaging). Then I believe you need to let debian-release know about the package so that they can approve it http://lists.debian.org/debian-release/ before it gets uploaded to a different queue. If you prepare the package, I can take care of this part if you like. Cheers, Francois -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#647079: whatsnewfm: New name and URL for freshmeat.net (parser broken)
A new upstream version of whatsnewfm has been released: http://www.cgarbs.de/whatsnewfm.en.html Inofficial Debian packages are available from my repository: http://www.cgarbs.de/stuff/deb-repository.html#whatsnewfm deb http://www.cgarbs.de/stuff ./ deb-src http://www.cgarbs.de/stuff ./ Official Debian packages are prepared for uploading: (these links time out in 30 days): http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-1_all.deb http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-1.diff.gz http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-1.dsc http://www.cgarbs.de/tmp/whatsnewfm_0.7.2.orig.tar.gz http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-1_i386.build http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-1_i386.changes http://www.cgarbs.de/tmp/whatsnewfm_0.7.2-1_source.changes Now I'm looking for somebody to sponsor my upload. What has to be done to get this update into stable (or volatile)? Currently the package is completely unusuable, waiting for the next stable release is not really an option. Regards Christian -- Christian.Garbs.http://www.cgarbs.de Micro$oft's error excuse #113: It's not a bug, it's a feature. signature.asc Description: Digital signature
Bug#647079: whatsnewfm: New name and URL for freshmeat.net (parser broken)
Package: whatsnewfm Version: 0.7.1-1 Severity: grave Tags: patch Justification: renders package unusable Freshmeat.net is now known as freecode.com which breaks the parser (it's looking for freshmeat.net URLs in the newsletter). A patch to fix this is available here: https://github.com/mmitch/whatsnewfm/pull/1 Cheers, Francois -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
