On 2/10/24 13:40, Holger Levsen wrote:
On Sat, Feb 10, 2024 at 12:16:48PM +, Holger Levsen wrote:
I'm also of the opinion that *someone* should do this for all these bugs
but I am too lazy to do it myself.
sebas...@debian.org has thankfully done this, 15min before I wrote the above.
On Sat, Feb 10, 2024 at 12:16:48PM +, Holger Levsen wrote:
> I'm also of the opinion that *someone* should do this for all these bugs
> but I am too lazy to do it myself.
sebas...@debian.org has thankfully done this, 15min before I wrote the above.
--
cheers,
Holger
⢀⣴⠾⠻⢶⣦⠀
On Fri, Feb 09, 2024 at 10:01:06AM -0600, John Goerzen wrote:
> So at the moment, I am unclear why there are bugs filed with severity
> serious that apparently cannot be fixed. Shouldn't they be normal with
> a tag wontfix until the relevant dpkg changes are in unstable?
I've downgraded those in
Hi,
Am Fri, Feb 09, 2024 at 06:46:58PM +0100 schrieb Andreas Metzler:
> Looking at "your" bug #1062097 it looks like you were unlucky, mine all
> had a fat warning "NOTICE: these changes must not be uploaded to
> unstable yet!".
I also was trapping into that pitfall when I was intending to fix
On 2024-02-09 John Goerzen wrote:
[...]
> So at the moment, I am unclear why there are bugs filed with severity
> serious that apparently cannot be fixed. Shouldn't they be normal with
> a tag wontfix until the relevant dpkg changes are in unstable?
> To put it another way, I'm not seeing why
Hi everyone,
Thanks to all that have put so much time and thought into the time_t
migration. I am late to this party and am trying to figure my way
through it.
Quite a few of my packages are marked for removal from testing because
time_t migration bugs have been filed with severity serious.
6 matches
Mail list logo
