Re: cgiirc Hijacking

2006-06-21 Thread Martin Zobel-Helas
Hi Florian, On Wed, Jun 21, 2006 at 07:34:49PM +0200, Florian Weimer <[EMAIL PROTECTED]> wrote: > * Mario Holbe: > > > We did. 0.5.4-6sarge1 was on s.d.o as soon as possible. Since there were > > no newer version in unstable, the version on s.d.o should have had > > automatically override even

Re: cgiirc Hijacking

2006-06-21 Thread Florian Weimer
* Mario Holbe: > We did. 0.5.4-6sarge1 was on s.d.o as soon as possible. Since there were > no newer version in unstable, the version on s.d.o should have had > automatically override even the unstable version. Of course, if you > don't source in s.d.o, you don't get security updates :) In this c

Re: cgiirc Hijacking

2006-06-21 Thread Jeroen van Wolffelaar
On Wed, Jun 21, 2006 at 08:07:28AM +0200, Mario 'BitKoenig' Holbe wrote: > Joe Smith <[EMAIL PROTECTED]> wrote: > > As I understand it, there is no good reason to have s.d.o in > > my sources list, as the packages in there are for sarge, and may not be > > compatible with the current sid ABI. > >

Re: cgiirc Hijacking

2006-06-20 Thread Mario 'BitKoenig' Holbe
Joe Smith <[EMAIL PROTECTED]> wrote: > As I understand it, there is no good reason to have s.d.o in > my sources list, as the packages in there are for sarge, and may not be > compatible with the current sid ABI. This is nonsense. If this should really be the way you understand it, please ask your

Re: cgiirc Hijacking

2006-06-20 Thread Jeroen van Wolffelaar
On Tue, Jun 20, 2006 at 10:45:27PM +0200, Thijs Kinkhorst wrote: > On Tue, 2006-06-20 at 13:18 -0300, Margarita Manterola wrote: > > Who told you that the sarge fix would propagate? > > > > Packages don't *propagate* from stable. If you want a package that > > was uploaded to stable to go to unst

Re: cgiirc Hijacking

2006-06-20 Thread Steve Langasek
On Tue, Jun 20, 2006 at 01:18:11PM -0300, Margarita Manterola wrote: > >> This is a sponsored uploaded package that only had 1 upload, and > >had a > >> DSA[3] issued which is still not fixed outside of sarge. > >We made that DSA happen. > >And we were told more than once, that the sarge fix

Re: cgiirc Hijacking

2006-06-20 Thread Thijs Kinkhorst
On Tue, 2006-06-20 at 13:18 -0300, Margarita Manterola wrote: > Who told you that the sarge fix would propagate? > > Packages don't *propagate* from stable. If you want a package that > was uploaded to stable to go to unstable, an upload is needed. You > should have asked for a sponsor. Well, a

Re: cgiirc Hijacking

2006-06-20 Thread Joe Smith
"Mario 'BitKoenig' Holbe" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] On Tue, Jun 20, 2006 at 01:18:11PM -0300, Margarita Manterola wrote: In cases where a security bug is being fixed, you usually try to upload the package as soon as possible. If your sponsor is on We did

Re: cgiirc Hijacking

2006-06-20 Thread Mario 'BitKoenig' Holbe
On Tue, Jun 20, 2006 at 01:18:11PM -0300, Margarita Manterola wrote: > In cases where a security bug is being fixed, you usually try to > upload the package as soon as possible. If your sponsor is on We did. 0.5.4-6sarge1 was on s.d.o as soon as possible. Since there were no newer version in unst

Re: cgiirc Hijacking

2006-06-20 Thread Margarita Manterola
On 6/20/06, Elrond <[EMAIL PROTECTED]> wrote: On Mon, Jun 19, 2006 at 07:02:50PM -0300, Damián Viano wrote: > I've seen cgiirc[1] in a bad state for some time now, I tried to contact > the maintainer (Mario Holbe) more than a month ago, offering my help and > my work[2]. No answer so far. M

Re: cgiirc Hijacking

2006-06-20 Thread Elrond
On Mon, Jun 19, 2006 at 07:02:50PM -0300, Damián Viano wrote: > Hi, > > I've seen cgiirc[1] in a bad state for some time now, I tried to contact > the maintainer (Mario Holbe) more than a month ago, offering my help and > my work[2]. No answer so far. Mario and I were busy. And I was tryin

cgiirc Hijacking

2006-06-19 Thread Damián Viano
Hi, I've seen cgiirc[1] in a bad state for some time now, I tried to contact the maintainer (Mario Holbe) more than a month ago, offering my help and my work[2]. No answer so far. This is a sponsored uploaded package that only had 1 upload, and had a DSA[3] issued which is still