❦ 28 January 2022 22:52 +01, Sebastian Ramacher:
>> > http://bugs.debian.org/1004272
>> > I agree that it should have been announced somewhere in addition to the
>> > #debian-devel topic.
>>
>> Running unstable, are we at risk having problems? Are the packages
>> updated in the last few days
On 2022-01-28 20:36:32 +0100, Vincent Bernat wrote:
> ❦ 28 January 2022 12:34 +05, Andrey Rahmatullin:
>
> > http://bugs.debian.org/1004272
> > I agree that it should have been announced somewhere in addition to the
> > #debian-devel topic.
>
> Running unstable, are we at risk having problems?
❦ 28 January 2022 12:34 +05, Andrey Rahmatullin:
> http://bugs.debian.org/1004272
> I agree that it should have been announced somewhere in addition to the
> #debian-devel topic.
Running unstable, are we at risk having problems? Are the packages
updated in the last few days being rebuilt?
--
On 1/28/22 07:53, Ole Streicher wrote:
Hi,
I just observed that many of my packages that are currently in unstable
are not migrating because of
| Not touching package due to block request by elbrus (Follow the freeze
| policy when applying for an unblock)
where the "freeze policy" is linked
On Fri, Jan 28, 2022 at 07:53:02AM +0100, Ole Streicher wrote:
> I just observed that many of my packages that are currently in unstable
> are not migrating because of
>
> | Not touching package due to block request by elbrus (Follow the freeze
> | policy when applying for an unblock)
>
> where
Hi,
I just observed that many of my packages that are currently in unstable
are not migrating because of
| Not touching package due to block request by elbrus (Follow the freeze
| policy when applying for an unblock)
where the "freeze policy" is linked to the bookworm Freeze Timeline (?).
f.e.
6 matches
Mail list logo
