Re: How to deal with wireshark CVE affecting Squeeze

2015-04-22 Thread Raphael Hertzog
On Tue, 21 Apr 2015, Bálint Réczey wrote: FTR the package has been accepted on the same day. However I have not seen DLA-198-1 on debian-lts-announce@l.d.o (did your forget to sign it?). I tried sending it several times even after subscirbing the list but they did not go throught. I have

Re: How to deal with wireshark CVE affecting Squeeze

2015-04-14 Thread Holger Levsen
On Dienstag, 14. April 2015, Bálint Réczey wrote: squeeze-lts, both in *.changes and *.changelog. The binary package names changed quite a lot so I think entering NEW was reasonable. ah. makes sense :) signature.asc Description: This is a digitally signed message part.

Re: How to deal with wireshark CVE affecting Squeeze

2015-04-14 Thread Holger Levsen
Hi Balint, On Dienstag, 14. April 2015, Bálint Réczey wrote: I have prepared the DLA and uploaded the fixed package but it ended up in NEW. Dear FTP Masters, please accept it. what distribution did you use in debian/changelog? cheers, Holger signature.asc Description: This is a

Re: How to deal with wireshark CVE affecting Squeeze

2015-04-11 Thread Ben Hutchings
On Sun, 2015-04-12 at 01:05 +0200, Bálint Réczey wrote: [...] I assume this situation is not unique to Wireshark. What do you think, what would be the best for the LTS project in Wireshark's case and what is the general LTS strategy in similar cases? I think the best approach would be either:

Re: How to deal with wireshark CVE affecting Squeeze

2015-04-11 Thread Bálint Réczey
Hi Raphael, 2015-04-10 23:59 GMT+02:00 Raphael Hertzog hert...@debian.org: Hello Balint, I would like to clarify the situation of wireshark in squeeze. In https://bugs.debian.org/774312 you requested to mark the package as not-supported and this has now been done. So in theory I should tag