On 10/26/21 7:40 PM, Paul Gevers wrote:
Hi Nilesh,
On 26-10-2021 15:59, Nilesh Patra wrote:
Since this bug is already fixed in unstable, it is causing a huge number
of autoremovals,
so I'm decreasing the severity for time being, to avoid temporary and
un-necessary testing removal noise. --
control: severity -1 important
Hi Paul,
Thanks for reporting
On Sun, 17 Oct 2021 21:52:24 +0200 Paul Gevers wrote:
If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally,
Hi Nilesh,
On 26-10-2021 16:23, Nilesh Patra wrote:
>> It was closed when I submitted it. It's the
>> other RC bug you need to worry about.
>
> This one right?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993042
Yes.
> Federico closed it a few hours earlier, and I re-opened and
Hi Nilesh,
On 26-10-2021 15:59, Nilesh Patra wrote:
> Since this bug is already fixed in unstable, it is causing a huge number
> of autoremovals,
> so I'm decreasing the severity for time being, to avoid temporary and
> un-necessary testing removal noise. -- Hope that's OK
As long as you'll be
Source: nim
Version: 1.4.6+really1.4.2-2
Severity: serious
Control: close -1 1.4.8-3
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 993042
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
5 matches
Mail list logo
