Re: Q on fixed-in-experimental
Colin Watson wrote: On Thu, Apr 20, 2006 at 02:18:15AM +0200, Laszlo Boszormenyi wrote: On Thu, 2006-04-20 at 00:14 +0100, Neil Williams wrote: When a bug is tagged fixed-in-experimental, does that bug number still have to appear in debian/changelog for the next upload to unstable or will the BTS be updated when the package in experimental is replaced? It has to appear in changelog. I know how to filter the BTS to show bugs with these tags, just wondering if it's automated. Can't be automated. An automatic system can't figure out if the fix is still in the package or maybe dropped from the unstable upload due to cause other problems. To clarify, it still has to appear in debian/changelog, but it doesn't have to be in the most recent version; leaving it in the version where you fixed the problem is good enough. together with -v to dpkg-buildpackage / debuild so the bugs actually get into the Closes: line of the .changes so they actually get closed. Regards, Rene signature.asc Description: Digital signature
Re: Q on fixed-in-experimental
On Thu, Apr 20, 2006 at 12:14:58AM +0100, Neil Williams wrote: When a bug is tagged fixed-in-experimental, does that bug number still have to appear in debian/changelog for the next upload to unstable or will the BTS be updated when the package in experimental is replaced? I know how to filter the BTS to show bugs with these tags, just wondering if it's automated. fixed-in-experimental is just an informative tag, and doesn't have any functional consecquence; it is really obsoleted by versioning, which does. If you mail [EMAIL PROTECTED] with a Version: $v pseudoheader, where v is the version in experimental, and later upload to unstable a version derived from the version in experimental, the BTS will consider that bug fixed in sid, too. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Q on fixed-in-experimental
When a bug is tagged fixed-in-experimental, does that bug number still have to appear in debian/changelog for the next upload to unstable or will the BTS be updated when the package in experimental is replaced? I know how to filter the BTS to show bugs with these tags, just wondering if it's automated. -- Neil Williams = http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ signature.asc Description: OpenPGP digital signature
Re: Q on fixed-in-experimental
On Thu, 2006-04-20 at 00:14 +0100, Neil Williams wrote: When a bug is tagged fixed-in-experimental, does that bug number still have to appear in debian/changelog for the next upload to unstable or will the BTS be updated when the package in experimental is replaced? It has to appear in changelog. I know how to filter the BTS to show bugs with these tags, just wondering if it's automated. Can't be automated. An automatic system can't figure out if the fix is still in the package or maybe dropped from the unstable upload due to cause other problems. Laszlo/GCS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Q on fixed-in-experimental
On Thu, Apr 20, 2006 at 02:18:15AM +0200, Laszlo Boszormenyi wrote: On Thu, 2006-04-20 at 00:14 +0100, Neil Williams wrote: When a bug is tagged fixed-in-experimental, does that bug number still have to appear in debian/changelog for the next upload to unstable or will the BTS be updated when the package in experimental is replaced? It has to appear in changelog. I know how to filter the BTS to show bugs with these tags, just wondering if it's automated. Can't be automated. An automatic system can't figure out if the fix is still in the package or maybe dropped from the unstable upload due to cause other problems. To clarify, it still has to appear in debian/changelog, but it doesn't have to be in the most recent version; leaving it in the version where you fixed the problem is good enough. -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
