Dear developers,

how are you dealing with packages during freeze?

Are package versions, which are now in testing frozen even when they are not
working? Or do you exchange not working versions from testing against working
versikns from unstable shortly before the release?

I just ask, because in the last days I discovered some packages, which are not
working in testing, but working in unstable.

One example is "bootcd" which in testing is (grave) version 3.22 and in
unstable (already fixed!) version 3.23. But version 3.23 is not being
transferred to testing since months.

Doesn't that not brake releases?

Best regards

Hans-J. Ullrich

On Fri, Dec 24, 2010 at 13:57:33 +0100, Hans-J. Ullrich wrote:

> Dear developers,
>
> how are you dealing with packages during freeze?
>
> Are package versions, which are now in testing frozen even when they are not
> working? Or do you exchange not working versions from testing against working
> versikns from unstable shortly before the release?
>
> I just ask, because in the last days I discovered some packages, which are not
> working in testing, but working in unstable.
>
> One example is "bootcd" which in testing is (grave) version 3.22 and in
> unstable (already fixed!) version 3.23. But version 3.23 is not being
> transferred to testing since months.
>
> Doesn't that not brake releases?
>
Bugs don't get fixed in testing if they don't get reported. There's no
release critical bug filed against the bootcd package in testing.

Cheers,
Julien

Am Freitag, 24. Dezember 2010 schrieb Julien Cristau:
> On Fri, Dec 24, 2010 at 13:57:33 +0100, Hans-J. Ullrich wrote:
> > Dear developers,
> >
> > how are you dealing with packages during freeze?
> >
> > Are package versions, which are now in testing frozen even when they are
> > not working? Or do you exchange not working versions from testing
> > against working versikns from unstable shortly before the release?
> >
> > I just ask, because in the last days I discovered some packages, which
> > are not working in testing, but working in unstable.
> >
> > One example is "bootcd" which in testing is (grave) version 3.22 and in
> > unstable (already fixed!) version 3.23. But version 3.23 is not being
> > transferred to testing since months.
> >
> > Doesn't that not brake releases?
>
> Bugs don't get fixed in testing if they don't get reported. There's no
> release critical bug filed against the bootcd package in testing.
>
> Cheers,
> Julien

Yeah, the bug was reported, the bug was fixed, but the version with the fix is
not beein updated in testing.

Cheers

Hans

On Fri, Dec 24, 2010 at 3:05 PM, Hans-J. Ullrich <hans.ullrich@loop.de> wrote:
> Yeah, the bug was reported, the bug was fixed, but the version with the fix is
> not beein updated in testing.

Link to bug report?

Olaf


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTin0Z+ifSgmqsPKxs-ViOR3uhFhYb=sNXizN2cGp@mail.gmail.com">http://lists.debian.org/AANLkTin0Z+ifSgmqsPKxs-ViOR3uhFhYb=sNXizN2cGp@mail.gmail.com

Am Freitag, 24. Dezember 2010 schrieb Olaf van der Spek:
> On Fri, Dec 24, 2010 at 3:05 PM, Hans-J. Ullrich <hans.ullrich@loop.de>
wrote:
> > Yeah, the bug was reported, the bug was fixed, but the version with the
> > fix is not beein updated in testing.
>
> Link to bug report?
>
> Olaf

This is the link:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562560

Hans

On 12/24/2010 03:45 PM, Hans-J. Ullrich wrote:
> Am Freitag, 24. Dezember 2010 schrieb Olaf van der Spek:
>> On Fri, Dec 24, 2010 at 3:05 PM, Hans-J. Ullrich
>> <hans.ullrich@loop.de>
> wrote:
>>> Yeah, the bug was reported, the bug was fixed, but the version
>>> with the fix is not beein updated in testing.
>>
>> Link to bug report?
>>
>> Olaf
>
> This is the link:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562560
>

FTR, it has been unblocked by Julien. It will migrate during next
britney's run.

Regards,

--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4D14B6AD.5070608@debian.org">http://lists.debian.org/4D14B6AD.5070608@debian.org

Am Freitag, 24. Dezember 2010 schrieb Mehdi Dogguy:
> On 12/24/2010 03:45 PM, Hans-J. Ullrich wrote:
> > Am Freitag, 24. Dezember 2010 schrieb Olaf van der Spek:
> >> On Fri, Dec 24, 2010 at 3:05 PM, Hans-J. Ullrich
> >> <hans.ullrich@loop.de>
> >
> > wrote:
> >>> Yeah, the bug was reported, the bug was fixed, but the version
> >>> with the fix is not beein updated in testing.
> >>
> >> Link to bug report?
> >>
> >> Olaf
> >
> > This is the link:
> >
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562560
>
> FTR, it has been unblocked by Julien. It will migrate during next
> britney's run.
>
> Regards,

Yes, thank you very much. I tested version 3.23 and everything is working fine
so far.

Great!

Best regards

Hans

On Fri, Dec 24, 2010 at 15:45:37 +0100, Hans-J. Ullrich wrote:

> Am Freitag, 24. Dezember 2010 schrieb Olaf van der Spek:
> > On Fri, Dec 24, 2010 at 3:05 PM, Hans-J. Ullrich <hans.ullrich@loop.de>
> wrote:
> > > Yeah, the bug was reported, the bug was fixed, but the version with the
> > > fix is not beein updated in testing.
> >
> > Link to bug report?
> >
> > Olaf
>
> This is the link:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562560
>
You filed that bug at "normal" severity. That does not indicate a
non-working package, so it stays below the radar…

Cheers,
Julien

> > This is the link:
> >
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562560
> >
> You filed that bug at "normal" severity. That does not indicate a
> non-working package, so it stays below the radar…

I believe Patrick Schoenfeld downgraded the bug.

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=12;bug=562560#12

d


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 874oa3htqj.fsf@zancas.localnet">http://lists.debian.org/874oa3htqj.fsf@zancas.localnet