Re: debian/bug-control: report bug against unofficial debianpackages
Le 07/11/2012 15:30, bilibop project a écrit :
> Hi, and thanks for your replies
>
> --------message d'origine --------
> De: Russ Allbery <rra@debian.org>
> A: debian-mentors@lists.debian.org
> 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: quidame@poivron.org' 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 <thibaut@debian.org>
> A: debian-mentors@lists.debian.org
> 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<arno@debian.org>
> A: debian-mentors@lists.debian.org
> 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:
>
Hi,
You can do like for backports.debian.org packages: keep the official
package changelog, and simply add an entry for the backport. Real life
example:
iceweasel (10.0.10esr-1~bpo60+1) squeeze-backports; urgency=low
* Rebuild for squeeze-backports.
-- Mike Hommey <glandium@debian.org> Fri, 26 Oct 2012 13:37:26 +0000
iceweasel (10.0.10esr-1) unstable; urgency=high
* New upstream release.
* Fixes for mfsa2012-90, also known as CVE-2012-4194 and CVE-2012-4196.
-- Mike Hommey <glandium@debian.org> Fri, 26 Oct 2012 15:19:35 +0200
iceweasel (10.0.9esr-1) unstable; urgency=high
* New upstream release.
* Fixes for mfsa2012-89, also known as CVE-2012-4192 and CVE-2012-4193.
-- Mike Hommey <glandium@debian.org> Sat, 13 Oct 2012 00:05:54 +0200
Reply to: