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

Bug#944460: marked as done (unblock: glibc/2.29-3)

Your message dated Sun, 10 Nov 2019 14:29:04 +0100
with message-id <8b9be57a-23e6-7ddb-29f8-0a9a2bcd0a26@debian.org>
and subject line Re: Bug#944460: unblock: glibc/2.29-3
has caused the Debian Bug report #944460,
regarding unblock: glibc/2.29-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
944460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944460
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

glibc 2.29-3 is prevented to migrate to testing due to autopktest
regressions. However those regressions are unrelated to glibc and are
due to the postgresql transition.

Therefore would it be possible to ignore those tests and force glibc
into testing?

Thanks,
Aurelien

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

--- End Message ---
--- Begin Message --- 
Hi Aurelien,

On 10-11-2019 13:03, Aurelien Jarno wrote:
> Therefore would it be possible to ignore those tests and force glibc
> into testing?

Ignored those results.

Paul

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: