Hi, and thanks for your replies --------message d'origine -------- De: Russ Allbery <[email protected]> A: [email protected] Sujet: Re: debian/bug-control: report bug against unofficial debianpackages Date: Mon, 05 Nov 2012 12:46:29 -0800
> > what can happen if a user reports a bug against one of my packages by > > using 'reportbug' ? > > Must I explicitly add 'Send-To: [email protected]' in debian/bug-control > > to avoid conflicts with Debian BTS ? > > I use Bugs: mailto:<address> as a source package header in debian/control > instead. --------message d'origine -------- De: Thibaut Paumard <[email protected]> A: [email protected] Sujet: Re: debian/bug-control: report bug against unofficial debianpackages Date: Mon, 05 Nov 2012 18:19:39 +0100 > > The .dsc and .tar.gz files in the personal repository are exactly > > the sames than those I have uploaded on mentors.debian.net. If the > > answer to the previous question is YES, must I send a different > > version on mentors, even if the package is not sponsored (because > > if it is sponsored a day, the source will be modified and the > > personal repository will disappear) ? > > Actually, I consider it a good idea for both packages to differ: the > packages you provide on your personal repository can be considered > pre-releases of the upcoming official Debian package and their version > should perhaps be of the form: x.y.z-1~rc1 to sort strictly before > x.y.z-1, which will be the first package in Debian. > > This way, when your package gets finally included in Debian, your > users will automatically get it as a routine update. --------message d'origine -------- De: Arno Töll<[email protected]> A: [email protected] Sujet: Re: debian/bug-control: report bug against unofficial debianpackages Date: Mon, 05 Nov 2012 17:52:04 +0100 > > The .dsc and .tar.gz files in the personal repository are exactly the > > sames than those I have uploaded on mentors.debian.net. If the answer to > > the previous question is YES, must I send a different version on mentors, > > even if the package is not sponsored (because if it is sponsored a day, > > the source will be modified and the personal repository will disappear) ? > > Yes, you may need to do so. Alternatively you can just upload the > package including the debian/bug-control file you mentioned to mentors > and hope your future sponsor will hopefully detect it and ask you to > remove it by then. So now, I'm a little bit confused... @Thibaut: Given that I'm a 'git' beginner, I don't know exactly how to deal with *parallel* versions. More exactly, how to manage the changelog entries? If I ship x.y.z~rc1 in my personal repository for each x.y.z version that I upload on mentors.debian.net, as you suggest me, does it mean that for each version, there should be TWO entries in the changelog, as: bilibop (0.4.2) unstable; urgency=low * Remove debian/bug-control -- full name <email> $(date -R) bilibop (0.4.2~rc1) unstable; urgency=low * blah blah * foo bar -- full name <email> $(date -R) bilibop (0.4.1) unstable; urgency=low * Remove debian/bug-control -- full name <email> $(date -R) bilibop (0.4.1~rc1) unstable; urgency=low * blah blah -- full name <email> $(date -R) Or should the changelogs differ, as: --> In personal repository: bilibop (0.4.2~rc1) unstable; urgency=low * blah blah * foo bar -- full name <email> $(date -R) bilibop (0.4.1~rc1) unstable; urgency=low * blah blah -- full name <email> $(date -R) --> In mentors.debian.net: bilibop (0.4.2~rc1) unstable; urgency=low * blah blah * foo bar -- full name <email> $(date -R) bilibop (0.4.1~rc1) unstable; urgency=low * blah blah -- full name <email> $(date -R) I presume the first solution is not good, and the last is bad. Idea? For my own convenience, I would prefer to continue to provide the same .dsc and .tar.gz files in the two places, as suggested by Arno; but using 'Bugs: mailto:<address>' in debian/control (maybe preceeded by a comment) instead of debian/bug-control, as suggested by Russ; by this way, future sponsor should easily detect the thing. This will lead to the need of a new version (for example from 0.5.2, with 'Bugs:' field in debian/control, to 0.5.3, without 'Bugs:' field in debian/control), then 'users will automatically get it as a routine update' too. Is this well ? Cheers, quidame -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
