glibc - Debian Package Tracker

general

source: glibc (main)
version: 2.43-5
maintainer: GNU Libc Maintainers (archive) (DMD)
uploaders: Samuel Thibault [DMD] – Clint Adams [DMD] – Aurelien Jarno [DMD]
arch: all any
std-ver: 4.6.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.31-13+deb11u11
o-o-sec: 2.31-13+deb11u14
o-o-upd: 2.31-13+deb11u5
o-o-p-u: 2.31-13+deb11u11
oldstable: 2.36-9+deb12u14
old-sec: 2.36-9+deb12u7
stable: 2.41-12+deb13u3
stable-p-u: 2.41-12+deb13u4
testing: 2.43-4
unstable: 2.43-5
exp: 2.44-1

versioned links

2.31-13+deb11u5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.31-13+deb11u11: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.31-13+deb11u14: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.36-9+deb12u7: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.36-9+deb12u14: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.41-12+deb13u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.41-12+deb13u4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.43-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.43-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.44-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

glibc-doc (8 bugs: 0, 1, 7, 0)
glibc-source (1 bugs: 0, 0, 1, 0)
libc-bin (23 bugs: 0, 10, 13, 0)
libc-dev-bin (1 bugs: 0, 1, 0, 0)
libc-devtools (1 bugs: 0, 1, 0, 0)
libc-gconv-modules-extra
libc-l10n
libc0.3
libc0.3-dbg
libc0.3-dev (1 bugs: 0, 1, 0, 0)
libc0.3-udeb
libc6 (217 bugs: 0, 154, 63, 0)
libc6-amd64 (1 bugs: 0, 1, 0, 0)
libc6-dbg (1 bugs: 0, 0, 1, 0)
libc6-dev (31 bugs: 0, 17, 14, 0)
libc6-dev-amd64
libc6-dev-i386
libc6-dev-mips32
libc6-dev-mips64
libc6-dev-mipsn32
libc6-dev-powerpc
libc6-dev-ppc64
libc6-dev-sparc
libc6-dev-sparc64
libc6-dev-x32
libc6-i386 (2 bugs: 0, 1, 1, 0)
libc6-mips32
libc6-mips64
libc6-mipsn32
libc6-powerpc
libc6-ppc64
libc6-sparc
libc6-sparc64
libc6-udeb
libc6-x32 (1 bugs: 0, 1, 0, 0)
libc6.1
libc6.1-dbg
libc6.1-dev
libc6.1-udeb
locales (48 bugs: 0, 30, 18, 0)
locales-all (3 bugs: 0, 2, 1, 0)
nscd (29 bugs: 0, 26, 3, 0)

action needed

10 security issues in trixie high

There are 10 open security issues in trixie.

1 important issue:

CVE-2026-89092: The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system. Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack. During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server. In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated. There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash. Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.

9 issues left for the package maintainer to handle:

CVE-2026-5435: (needs triaging) The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to enforce the caller-supplied buffer length, and can result in an out-of-bounds write when printing TSIG records.
CVE-2026-6238: (needs triaging) The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.0.1 to version 2.43 fail to validate the RDATA content against the RDATA length in a DNS response when processing A6, CERT, LOC, TKEY or TSIG records, which may allow an attacker to craft a DNS response, causing a target application to crash or read uninitialized memory. These functions are for application debugging only and hence not in the path of code executed by the DNS resolver. Further, they have been deprecated since version 2.34 and should not be used by any new applications. Applications should consider porting away from these interfaces since they may be removed in future versions.
CVE-2026-6368: (needs triaging) Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
CVE-2026-6791: (needs triaging) When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
CVE-2026-18374: (needs triaging) Passing an effectively empty string to the `,ccs=` syntax extension of the mode argument in the `fopen` function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled. This usage pattern is not seen in applications in common GNU/Linux distributions and applications that process user-supplied values for `ccs` should not pass them through without validation.
CVE-2026-19499: (needs triaging)
CVE-2026-19542: (needs triaging)
CVE-2026-77117: (needs triaging)
CVE-2026-80489: (needs triaging)

You can find information about how to handle these issues in the security team's documentation.

2 issues that should be fixed with the next stable update:

CVE-2026-5450: Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version 2.7 to version 2.43 with a format width specifier with an explicit width greater than 1024 could result in a one byte heap buffer overflow.
CVE-2026-5928: Calling the ungetwc function on a FILE stream with wide characters encoded in a character set that has overlaps between its single byte and multi-byte character encodings, in the GNU C Library version 2.43 or earlier, may result in an attempt to read bytes before an allocated buffer, potentially resulting in unintentional disclosure of neighboring data in the heap, or a program crash. A bug in the wide character pushback implementation (_IO_wdefault_pbackfail in libio/wgenops.c) causes ungetwc() to operate on the regular character buffer (fp->_IO_read_ptr) instead of the actual wide-stream read pointer (fp->_wide_data->_IO_read_ptr). The program crash may happen in cases where fp->_IO_read_ptr is not initialized and hence points to NULL. The buffer under-read requires a special situation where the input character encoding is such that there are overlaps between single byte representations and multibyte representations in that encoding, resulting in spurious matches. The spurious match case is not possible in the standard Unicode character sets.

Created: 2026-03-21 Last update: 2026-09-11 06:02

5 security issues in forky high

There are 5 open security issues in forky.

5 important issues:

CVE-2026-18374: Passing an effectively empty string to the `,ccs=` syntax extension of the mode argument in the `fopen` function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled. This usage pattern is not seen in applications in common GNU/Linux distributions and applications that process user-supplied values for `ccs` should not pass them through without validation.
CVE-2026-19499:
CVE-2026-77117:
CVE-2026-80489:
CVE-2026-89092: The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system. Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack. During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server. In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated. There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash. Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.

Created: 2026-03-21 Last update: 2026-09-11 06:02

1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:

CVE-2026-89092: The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system. Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack. During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server. In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated. There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash. Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.

Created: 2026-09-11 Last update: 2026-09-11 06:02

12 security issues in bookworm high

There are 12 open security issues in bookworm.

1 important issue:

CVE-2026-89092: The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system. Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack. During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server. In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated. There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash. Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.

11 issues postponed or untriaged:

CVE-2026-5435: (needs triaging) The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to enforce the caller-supplied buffer length, and can result in an out-of-bounds write when printing TSIG records.
CVE-2026-5450: (needs triaging) Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version 2.7 to version 2.43 with a format width specifier with an explicit width greater than 1024 could result in a one byte heap buffer overflow.
CVE-2026-5928: (needs triaging) Calling the ungetwc function on a FILE stream with wide characters encoded in a character set that has overlaps between its single byte and multi-byte character encodings, in the GNU C Library version 2.43 or earlier, may result in an attempt to read bytes before an allocated buffer, potentially resulting in unintentional disclosure of neighboring data in the heap, or a program crash. A bug in the wide character pushback implementation (_IO_wdefault_pbackfail in libio/wgenops.c) causes ungetwc() to operate on the regular character buffer (fp->_IO_read_ptr) instead of the actual wide-stream read pointer (fp->_wide_data->_IO_read_ptr). The program crash may happen in cases where fp->_IO_read_ptr is not initialized and hence points to NULL. The buffer under-read requires a special situation where the input character encoding is such that there are overlaps between single byte representations and multibyte representations in that encoding, resulting in spurious matches. The spurious match case is not possible in the standard Unicode character sets.
CVE-2026-6238: (needs triaging) The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.0.1 to version 2.43 fail to validate the RDATA content against the RDATA length in a DNS response when processing A6, CERT, LOC, TKEY or TSIG records, which may allow an attacker to craft a DNS response, causing a target application to crash or read uninitialized memory. These functions are for application debugging only and hence not in the path of code executed by the DNS resolver. Further, they have been deprecated since version 2.34 and should not be used by any new applications. Applications should consider porting away from these interfaces since they may be removed in future versions.
CVE-2026-6368: (postponed; to be fixed through a stable update) Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
CVE-2026-6791: (postponed; to be fixed through a stable update) When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
CVE-2026-18374: (postponed; to be fixed through a stable update) Passing an effectively empty string to the `,ccs=` syntax extension of the mode argument in the `fopen` function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled. This usage pattern is not seen in applications in common GNU/Linux distributions and applications that process user-supplied values for `ccs` should not pass them through without validation.
CVE-2026-19499: (postponed; to be fixed through a stable update)
CVE-2026-19542: (postponed; to be fixed through a stable update)
CVE-2026-77117: (postponed; to be fixed through a stable update)
CVE-2026-80489: (postponed; to be fixed through a stable update)

Created: 2026-09-11 Last update: 2026-09-11 06:02

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

https://salsa.debian.org/api/v4/projects/glibc-team%2Fglibc API request failed: 401 Unauthorized at /srv/qa.debian.org/data/vcswatch/vcswatch line 410.

Created: 2026-01-29 Last update: 2026-09-11 04:31

A new upstream version is available: 2.44 high

A new upstream version 2.44 is available, you should consider packaging it.

Created: 2026-08-27 Last update: 2026-09-11 03:01

lintian reports 9 errors and 35 warnings high

Lintian reports 9 errors and 35 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2026-09-06 Last update: 2026-09-07 16:30

13 security issues in bullseye high

There are 13 open security issues in bullseye.

7 important issues:

CVE-2026-6368: Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
CVE-2026-6791: When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.
CVE-2026-18374: Passing an effectively empty string to the `,ccs=` syntax extension of the mode argument in the `fopen` function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled. This usage pattern is not seen in applications in common GNU/Linux distributions and applications that process user-supplied values for `ccs` should not pass them through without validation.
CVE-2026-19499:
CVE-2026-19542:
CVE-2026-77117:
CVE-2026-80489:

4 issues postponed or untriaged:

CVE-2026-5435: (postponed; to be fixed through a stable update) The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to enforce the caller-supplied buffer length, and can result in an out-of-bounds write when printing TSIG records.
CVE-2026-5450: (postponed; to be fixed through a stable update) Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version 2.7 to version 2.43 with a format width specifier with an explicit width greater than 1024 could result in a one byte heap buffer overflow.
CVE-2026-5928: (postponed; to be fixed through a stable update) Calling the ungetwc function on a FILE stream with wide characters encoded in a character set that has overlaps between its single byte and multi-byte character encodings, in the GNU C Library version 2.43 or earlier, may result in an attempt to read bytes before an allocated buffer, potentially resulting in unintentional disclosure of neighboring data in the heap, or a program crash. A bug in the wide character pushback implementation (_IO_wdefault_pbackfail in libio/wgenops.c) causes ungetwc() to operate on the regular character buffer (fp->_IO_read_ptr) instead of the actual wide-stream read pointer (fp->_wide_data->_IO_read_ptr). The program crash may happen in cases where fp->_IO_read_ptr is not initialized and hence points to NULL. The buffer under-read requires a special situation where the input character encoding is such that there are overlaps between single byte representations and multibyte representations in that encoding, resulting in spurious matches. The spurious match case is not possible in the standard Unicode character sets.
CVE-2026-6238: (postponed; to be fixed through a stable update) The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.0.1 to version 2.43 fail to validate the RDATA content against the RDATA length in a DNS response when processing A6, CERT, LOC, TKEY or TSIG records, which may allow an attacker to craft a DNS response, causing a target application to crash or read uninitialized memory. These functions are for application debugging only and hence not in the path of code executed by the DNS resolver. Further, they have been deprecated since version 2.34 and should not be used by any new applications. Applications should consider porting away from these interfaces since they may be removed in future versions.

2 ignored issues:

CVE-2023-4806: A flaw has been identified in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the _nss_*_gethostbyname2_r and _nss_*_getcanonname_r hooks without implementing the _nss_*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.
CVE-2023-4813: A flaw has been identified in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.

Created: 2026-08-10 Last update: 2026-08-30 22:31

7 security issues in buster high

There are 7 open security issues in buster.

4 important issues:

CVE-2024-33599: nscd: Stack-based buffer overflow in netgroup cache If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted by client requests then a subsequent client request for netgroup data may result in a stack-based buffer overflow. This flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.
CVE-2024-33600: nscd: Null pointer crashes after notfound response If the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache, the client request can result in a null pointer dereference. This flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.
CVE-2024-33601: nscd: netgroup cache may terminate daemon on memory allocation failure The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or xrealloc and these functions may terminate the process due to a memory allocation failure resulting in a denial of service to the clients. The flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.
CVE-2024-33602: nscd: netgroup cache assumes NSS callback uses in-buffer strings The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd. This vulnerability is only present in the nscd binary.

2 issues postponed or untriaged:

CVE-2023-4806: (needs triaging) A flaw was found in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the _nss_*_gethostbyname2_r and _nss_*_getcanonname_r hooks without implementing the _nss_*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.
CVE-2023-4813: (needs triaging) A flaw was found in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.

1 ignored issue:

CVE-2020-1751: An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.

Created: 2024-04-17 Last update: 2024-06-29 13:15

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 5-day delay is over. Check why.

Created: 2026-09-10 Last update: 2026-09-11 06:02

Depends on packages which need a new maintainer normal

The packages that glibc depends on which need a new maintainer are:

systemtap (#1114760)
- Build-Depends: systemtap-sdt-dev

Created: 2026-01-04 Last update: 2026-09-11 05:31

35 bugs tagged patch in the BTS normal

The BTS contains patches fixing 35 bugs (41 if counting merged bugs), consider including or untagging them.

Created: 2026-09-02 Last update: 2026-09-11 05:30

debian/patches: 84 patches to forward upstream low

Among the 84 debian patches available in version 2.43-5 of the package, we noticed the following issues:

84 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-09-05 23:00

Issues found with some translations low

Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.

Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.

Created: 2020-02-26 Last update: 2025-12-07 14:00

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.6.2).

Created: 2024-04-07 Last update: 2026-09-05 19:34

testing migrations

excuses:
- Migration status for glibc (2.43-4 to 2.43-5): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Autopkgtest for aide/0.19.3-1: i386: Pass ♻
- ∙ ∙ Autopkgtest for aioquic/1.3.0-1: i386: Pass ♻
- ∙ ∙ Autopkgtest for altree/1.3.2-4: amd64: Pass, arm64: Pass, armhf: Test triggered (failure will be ignored), i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Pass
- ∙ ∙ Autopkgtest for ann/1.1.2+doc-9: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Reference test triggered, but real test failed already ♻, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for atuin/18.20.0+ds-1: i386: Pass ♻
- ∙ ∙ Autopkgtest for beaker/1.13.0-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for binutils/2.47-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for caddy/2.11.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for cmake/4.3.4-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for cyrus-imapd/3.12.3-4: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for cython/3.1.6+dfsg-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for dipy/1.12.1-5: amd64: Pass, arm64: Pass, armhf: Ignored failure ♻ (reference ♻), i386: Ignored failure ♻ (reference ♻), ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for dolfin/2019.2.0~legacy20240219.1c52e83-30: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for dovecot/1:2.4.4+dfsg1-2: i386: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for dpdk/25.11.2-1: arm64: Pass ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for dracut/112-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for dua-cli/2.34.0-1: i386: Pass ♻
- ∙ ∙ Autopkgtest for epson-inkjet-printer-escpr/1.8.8-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for esys-particle: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for faketime/0.9.12-0.2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Reference test triggered, but real test failed already ♻, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for fenics-dolfinx/1:0.10.0.post5-8: amd64: Pass, arm64: Pass, armhf: Failed (not a regression) ♻ (reference ♻), i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for glibc/2.43-5: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for gnome-console/50.0-3: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
- ∙ ∙ Autopkgtest for gpgme1.0/2.1.2-1: amd64: Pass ♻, arm64: Pass ♻, i386: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for gr-framework/0.73.26+dfsg-1: amd64: Pass ♻, arm64: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for groonga/16.0.9+dfsg-2: amd64: Pass ♻, arm64: Pass ♻, i386: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for gsocket/1.4.43-5: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Pass, armhf: Pass, i386: Reference test triggered, but real test failed already ♻, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for gyoto/2.0.2-8: amd64: Pass, arm64: Pass, armhf: Pass, i386: Reference test triggered, but real test failed already ♻, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for haskell-futhark/0.25.32-3: amd64: Pass, arm64: Pass, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for hugo: amd64: Test triggered (failure will be ignored), arm64: Test triggered (failure will be ignored), armhf: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for icmake/13.05.01-1: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for jsonnet/0.20.0+ds-3.3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for lemonade/11.5.2-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for libcap-ng/0.9.3-1: i386: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for libdbd-mariadb-perl/1.22-1: amd64: No tests, superficial or marked flaky ♻, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻ (reference ♻), i386: Test triggered, ppc64el: No tests, superficial or marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
- ∙ ∙ Autopkgtest for libjsoncpp/1.9.8-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Reference test triggered, but real test failed already ♻, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for libmceliece/0~20260622-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for libpdl-io-hdf-perl/2.004-1: i386: Pass ♻
- ∙ ∙ Autopkgtest for libqb/2.0.9-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for libreoffice/4:26.8.0.3-2: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for libssc/0.4.4-1: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻
- ∙ ∙ Autopkgtest for liburing/2.15-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for libxml2/2.15.3+dfsg-1: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for link-grammar/5.13.0+dfsg-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for linux/7.1.12-1: arm64: Failed (not a regression) ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for macaulay2/1.26.06+ds-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for motif/2.3.8-5: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Reference test triggered, but real test failed already ♻, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for mypy/2.2.0-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for nodejs/24.19.0+dfsg+~cs24.13.3-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for notcurses/3.0.17+dfsg-3: amd64: Pass, arm64: Pass, armhf: Pass, i386: Reference test triggered, but real test failed already ♻, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for numba/0.65.1+dfsg-3: amd64: Pass, arm64: Pass, ppc64el: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for octave-datatypes/1.3.2-1: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for octave-general/2.1.4-1: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for octave-geometry/4.1.0-3: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for octave-image-acquisition/0.3.3-3: amd64: Pass ♻, arm64: Pass ♻ (reference ♻), armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for octave-interval/3.2.2-3: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for octave-level-set/0.3.1~git.2019.04.13-8: i386: Pass ♻
- ∙ ∙ Autopkgtest for octave-ltfat/2.6.0+dfsg-7: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for octave-nan/3.7.0-6: amd64: Pass ♻, arm64: Pass ♻ (reference ♻), armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for octave-optiminterp/0.3.7-4: amd64: Pass ♻, arm64: Pass ♻ (reference ♻), armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for octave-secs2d/0.0.8-17: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for octave-sparsersb/1.0.9-10: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for octave-struct/1.0.18-4: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for octave-vibes/0.2.0-10: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: Pass ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for open62541/1.4.18-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Reference test triggered, but real test failed already ♻, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for openbabel/3.1.1+dfsg-14: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for openjdk-21/21.0.12.1+1-1: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for openjdk-25/25.0.4+7-1: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for openjdk-26/26.0.2.1+1-1: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for openjdk-27/27~34ea-1: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Pass, i386: Pass, ppc64el: Test triggered (failure will be ignored), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for opensaml/3.3.1-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for openvswitch/3.7.1-3: amd64: Pass ♻, arm64: Pass ♻ (reference ♻), ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for oxigraph/0.5.9+ds-3: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for pg-cron/1.6.7-3: amd64: Pass ♻, arm64: Pass ♻ (reference ♻), ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-backports.zstd/1.7.0+ds-2: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Failed (not a regression) ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python-bx/0.15.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ (reference ♻), ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for python-fastcrc/0.3.6-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for python-pyproj/3.7.2-3: amd64: Pass ♻, arm64: Pass ♻, armhf: Pass ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: Pass ♻, riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for python3.13/3.13.15-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for python3.14/3.14.7-1: amd64: Pass, arm64: Pass, armhf: Failed (not a regression) ♻ (reference ♻), i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for pytorch/2.12.1+dfsg-1: amd64: Pass, arm64: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for qemu/1:11.1.0+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Regression ♻ (reference ♻)
- ∙ ∙ Autopkgtest for r-cran-huge/1.6-1: amd64: Pass ♻, arm64: Pass ♻, ppc64el: Pass ♻ (reference ♻), riscv64: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for rapidyaml/0.16.0+ds-2: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for ros-ros-comm/1.17.4+ds-4: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for rust-bacon/3.24.0+ds-2: i386: Pass ♻
- ∙ ∙ Autopkgtest for rust-cargo-c/0.10.16-2: i386: Pass ♻ (reference ♻)
- ∙ ∙ Autopkgtest for rust-gst-plugin-gtk4/0.15.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for rust-inquest/0.3.2-1: i386: Pass ♻
- ∙ ∙ Autopkgtest for rust-ntpd/1.9.0-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for rust-openpgp-card-state/0.3.1-1: i386: Pass ♻
- ∙ ∙ Autopkgtest for rust-parsec-service/1.5.0+dfsg-1: i386: Pass ♻
- ∙ ∙ Autopkgtest for rust-parsec-tool/0.7.0-8: i386: Pass ♻
- ∙ ∙ Autopkgtest for rust-rav1e/0.8.1-11: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for rust-rbw/1.15.0-1: i386: Pass ♻
- ∙ ∙ Autopkgtest for rust-rootasrole/4.0.1-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for rust-sequoia-octopus-librnp/1.11.1-8: i386: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for scikit-fmm/2025.06.23-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Reference test triggered, but real test failed already ♻, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for scikit-learn/1.9.0+dfsg-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for slm/3.6.2-1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test triggered, ppc64el: No tests, superficial or marked flaky ♻, riscv64: No tests, superficial or marked flaky ♻ (reference ♻)
- ∙ ∙ Autopkgtest for snapd/2.76.3-2: amd64: Pass, arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: No tests, superficial or marked flaky ♻, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for sqlalchemy/2.0.52+ds1-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), armhf: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for starship/1.26.0-1: i386: Pass ♻
- ∙ ∙ Autopkgtest for systemc/3.0.2-1: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Reference test triggered, but real test failed already ♻
- ∙ ∙ Autopkgtest for thunderbird/1:140.14.0esr-1: amd64: Pass, arm64: Test triggered (failure will be ignored), i386: Pass, ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for tokenizers/0.23.1+dfsg-2.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Test triggered, ppc64el: Pass, riscv64: Pass
- ∙ ∙ Autopkgtest for unrardll/0.1.7+ds1-6: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻, armhf: No tests, superficial or marked flaky ♻, i386: Test triggered, ppc64el: No tests, superficial or marked flaky ♻
- ∙ ∙ Autopkgtest for vim-youcompleteme/0+20240827+gitb6e8c64+ds-9: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- ∙ ∙ Autopkgtest for wasm-tools/1.239.0+ds-10: amd64: Pass, arm64: Pass, armhf: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored)
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/glibc.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- ∙ ∙ 6 days old (needed 5 days)
- Not considered

news

[rss feed]

[2026-09-05] Accepted glibc 2.43-5 (source) into unstable (Aurelien Jarno)
[2026-09-03] glibc 2.43-4 MIGRATED to testing (Debian testing watch)
[2026-08-23] Accepted glibc 2.43-4 (source) into unstable (Aurelien Jarno)
[2026-08-22] glibc 2.43-3 MIGRATED to testing (Debian testing watch)
[2026-08-10] Accepted glibc 2.44-1 (source) into experimental (Aurelien Jarno)
[2026-08-10] Accepted glibc 2.43-3 (source) into unstable (Aurelien Jarno)
[2026-07-11] Accepted glibc 2.41-12+deb13u4 (source) into proposed-updates (Debian FTP Masters) (signed by: Aurelien Jarno)
[2026-06-25] glibc 2.42-17 MIGRATED to testing (Debian testing watch)
[2026-06-18] Accepted glibc 2.42-17 (source) into unstable (Aurelien Jarno)
[2026-06-08] Accepted glibc 2.31-13+deb11u14 (source) into oldoldstable-security (Arnaud Rebillout)
[2026-05-14] glibc 2.42-16 MIGRATED to testing (Debian testing watch)
[2026-05-06] Accepted glibc 2.42-16 (source) into unstable (Aurelien Jarno)
[2026-05-03] Accepted glibc 2.41-12+deb13u3 (source) into proposed-updates (Debian FTP Masters) (signed by: Aurelien Jarno)
[2026-05-03] Accepted glibc 2.36-9+deb12u14 (source) into oldstable-proposed-updates (Debian FTP Masters) (signed by: Aurelien Jarno)
[2026-04-25] glibc 2.42-15 MIGRATED to testing (Debian testing watch)
[2026-04-19] Accepted glibc 2.42-15 (source) into unstable (Aurelien Jarno)
[2026-04-05] glibc 2.42-14 MIGRATED to testing (Debian testing watch)
[2026-03-28] Accepted glibc 2.43-2 (source) into experimental (Aurelien Jarno)
[2026-03-27] Accepted glibc 2.42-14 (source) into unstable (Aurelien Jarno)
[2026-03-03] Accepted glibc 2.41-12+deb13u2 (source) into proposed-updates (Debian FTP Masters) (signed by: Aurelien Jarno)
[2026-02-21] glibc 2.42-13 MIGRATED to testing (Debian testing watch)
[2026-02-10] Accepted glibc 2.42-13 (source) into unstable (Aurelien Jarno)
[2026-02-07] Accepted glibc 2.42-12 (source) into unstable (Aurelien Jarno)
[2026-02-01] glibc 2.42-11 MIGRATED to testing (Debian testing watch)
[2026-01-28] Accepted glibc 2.43-1 (source) into experimental (Aurelien Jarno)
[2026-01-27] Accepted glibc 2.42-11 (source) into unstable (Aurelien Jarno)
[2026-01-22] glibc 2.42-10 MIGRATED to testing (Debian testing watch)
[2026-01-20] glibc 2.42-9 MIGRATED to testing (Debian testing watch)
[2026-01-19] Accepted glibc 2.42-10 (source) into unstable (Aurelien Jarno)
[2026-01-18] Accepted glibc 2.42-9 (source) into unstable (Aurelien Jarno)

bugs [bug history graph]

all: 416 439
RC: 0
I&N: 270 287
M&W: 146 152
F&P: 0
patch: 35 41

links

homepage
lintian (9, 35)
buildd: logs, exp, reproducibility, cross
popcon
browse source code
other distros
security tracker
l10n (84, 97)
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.43-2ubuntu2.3
448 bugs (8 patches)
patches for 2.43-2ubuntu2.3