Re: libemail-address-perl, no "squeeze update of ..." mail sent, yet

2015-09-29 Thread Mike Gabriel

Hi Raphael,

On  Di 29 Sep 2015 13:55:06 CEST, Raphael Hertzog wrote:


On Tue, 29 Sep 2015, Mike Gabriel wrote:

Is there a reason that no "squeeze update of ..." mail has been sent for
libemail-address-perl, yet, (i.e., when triaging the latest security issue
in that package)?


Yes, the fix is so easy that sending the above mail would take more time
than fixing the package and the package is part of the Perl team which
is rather happy when we do the work and push our update in their
git repository (I believe all DD have write access to their git
repositories).


ok. Thanks for the answer. Will continue with fixing  
libemail-address-perl, then.


Best,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpmJJQxRI81T.pgp
Description: Digitale PGP-Signatur


libemail-address-perl, no "squeeze update of ..." mail sent, yet

2015-09-29 Thread Mike Gabriel

Hi all,

I just took over updating libemail-address-perl in squeeze-lts via  
secure-testing SVN repo.


Is there a reason that no "squeeze update of ..." mail has been sent  
for libemail-address-perl, yet, (i.e., when triaging the latest  
security issue in that package)?


Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgptW_0f7VawL.pgp
Description: Digitale PGP-Signatur


Re: libemail-address-perl, no "squeeze update of ..." mail sent, yet

2015-09-29 Thread Raphael Hertzog
On Tue, 29 Sep 2015, Mike Gabriel wrote:
> Is there a reason that no "squeeze update of ..." mail has been sent for
> libemail-address-perl, yet, (i.e., when triaging the latest security issue
> in that package)?

Yes, the fix is so easy that sending the above mail would take more time
than fixing the package and the package is part of the Perl team which
is rather happy when we do the work and push our update in their
git repository (I believe all DD have write access to their git
repositories).

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/



Re: libemail-address-perl, no "squeeze update of ..." mail sent, yet

2015-09-29 Thread Mike Gabriel

Hi again,

On  Di 29 Sep 2015 15:06:23 CEST, Mike Gabriel wrote:


Hi Raphael,

On  Di 29 Sep 2015 13:55:06 CEST, Raphael Hertzog wrote:


On Tue, 29 Sep 2015, Mike Gabriel wrote:

Is there a reason that no "squeeze update of ..." mail has been sent for
libemail-address-perl, yet, (i.e., when triaging the latest security issue
in that package)?


Yes, the fix is so easy that sending the above mail would take more time
than fixing the package and the package is part of the Perl team which
is rather happy when we do the work and push our update in their
git repository (I believe all DD have write access to their git
repositories).


ok. Thanks for the answer. Will continue with fixing  
libemail-address-perl, then.


Best,
Mike


another question about this simple fix-up (SORRY)...

As it seems the issue is only referenced via a TEMP-* ID [1] in the  
Debian Security Tracker. Furthermore, no bug is referenced there [1],  
either. And... the issue is already fixed in testing/unstable.


Shall I file a new bug with exact affected versions (as found in  
jessie, wheezy, squeeze-lts) and attach it to the TEMP-* security  
tracker ID and then reference that new bug in my squeeze-lts upload?


Thanks for input,
Mike

[1] https://security-tracker.debian.org/tracker/TEMP-000-F41FA7
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpOnyJgi_sN2.pgp
Description: Digitale PGP-Signatur


Re: libemail-address-perl, no "squeeze update of ..." mail sent, yet

2015-09-29 Thread Mike Gabriel

Hi again,

On  Di 29 Sep 2015 15:06:23 CEST, Mike Gabriel wrote:


Hi Raphael,

On  Di 29 Sep 2015 13:55:06 CEST, Raphael Hertzog wrote:


On Tue, 29 Sep 2015, Mike Gabriel wrote:

Is there a reason that no "squeeze update of ..." mail has been sent for
libemail-address-perl, yet, (i.e., when triaging the latest security issue
in that package)?


Yes, the fix is so easy that sending the above mail would take more time
than fixing the package and the package is part of the Perl team which
is rather happy when we do the work and push our update in their
git repository (I believe all DD have write access to their git
repositories).


ok. Thanks for the answer. Will continue with fixing  
libemail-address-perl, then.


Best,
Mike


another question about this simple fix-up (SORRY)...

As it seems the issue is only referenced via a TEMP-* ID [1] in the  
Debian Security Tracker. Furthermore, no bug is referenced there [1],  
either. And... the issue is already fixed in testing/unstable.


Shall I file a new bug with exact affected versions (as found in  
jessie, wheezy, squeeze-lts) and attach it to the TEMP-* security  
tracker ID and then reference that new bug in my squeeze-lts upload?


Thanks for input,
Mike

[1] https://security-tracker.debian.org/tracker/TEMP-000-F41FA7
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgpSnmK_kM4Gj.pgp
Description: Digitale PGP-Signatur


Re: libemail-address-perl, no "squeeze update of ..." mail sent, yet

2015-09-29 Thread Raphael Hertzog
On Tue, 29 Sep 2015, Mike Gabriel wrote:
> another question about this simple fix-up (SORRY)...
> 
> As it seems the issue is only referenced via a TEMP-* ID [1] in the Debian
> Security Tracker. Furthermore, no bug is referenced there [1], either.
> And... the issue is already fixed in testing/unstable.

Then you don't put any reference in the changelog except
maybe a clear description and the upstream commit ?

But you pay attention to this to properly mark the entry
as solved in the security tracker:
https://lists.debian.org/debian-lts/2015/09/msg00058.html

> Shall I file a new bug with exact affected versions (as found in jessie,
> wheezy, squeeze-lts) and attach it to the TEMP-* security tracker ID and
> then reference that new bug in my squeeze-lts upload?

I don't think that it's required.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/