Aurelien Jarno pushed to branch stretch at GNU Libc Maintainers / glibc
Commits:
ae220df6 by Aurelien Jarno at 2018-12-20T23:50:21Z
debian/patches/git-updates.diff: update from upstream stable branch:
* debian/patches/git-updates.diff: update from upstream stable branch:
- Fix a data corruptio
#
# bts-link upstream status pull for source package libc6,nocache
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #916415 (http://bugs.debian.org/91
Processing control commands:
> notfound -1 glibc/2.28-2
Bug #882255 {Done: Aurelien Jarno } [libc6-amd64]
libc6-amd64: Multilib causes catastrophic system failure during upgrade to libc
2.25
No longer marked as found in versions glibc/2.28-2.
--
882255: https://bugs.debian.org/cgi-bin/bugrepor
control: notfound -1 glibc/2.28-2
On 2018-12-20 09:55, Florin Iucha wrote:
> Package: libc6-dev
> Version: 2.28-2
> Followup-For: Bug #882255
Please do not reuse unrelated bug for reporting new ones.
> Trying to compile a personal project using Clang7 and maximum warning
> settings, it produced
Package: libc6-dev
Version: 2.28-2
Followup-For: Bug #882255
Dear Maintainer,
Trying to compile a personal project using Clang7 and maximum warning
settings, it produced the following warning:
error: disabled expansion of recursive macro
[-Werror,-Wdisabled-macro-expansion]
/usr/include/x86_64-
Package: glibc-source
Version: 2.24-11+deb9u3
We are using slurm, which uses a lot of pthreads, and it keeps exercising this
bug that has already
been reported upstream
(https://sourceware.org/bugzilla/show_bug.cgi?id=20116#c5), which was introduced
after glibc 2.19 and has been fixed in glibc
6 matches
Mail list logo
