[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Processed: now regressed in testing



On 2022-09-22 09:03, Debian Bug Tracking System wrote:
> Processing commands for control@bugs.debian.org:
> 
> > reassign 1014729 src:wcc 0.0.2+dfsg-4.1
> Bug #1014729 [src:glibc, src:wcc] glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument
> Bug reassigned from package 'src:glibc, src:wcc' to 'src:wcc'.
> No longer marked as found in versions wcc/0.0.2+dfsg-4.1 and glibc/2.34-0experimental4.
> Ignoring request to alter fixed versions of bug #1014729 to the same values previously set
> Bug #1014729 [src:wcc] glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument
> Marked as found in versions wcc/0.0.2+dfsg-4.1.
> > severity 1014729 serious
> Bug #1014729 [src:wcc] glibc 2.34 breaks wcc autopkgtest on amd64: open: Invalid argument
> Severity set to 'serious' from 'important'
> > thanks
> Stopping processing here.

Unfortunately I haven't found time to work on that. As we know that a
binNMU fixes the issue, should we just do that?

Regards
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net


Reply to: