Bug#235759: Bug#228486: No mention of german quotes in release-notes yet

Re: GOTO Masanori in [EMAIL PROTECTED] The locales for German style languages (e.g. [EMAIL PROTECTED]) unfortunately use an aesthetically unpleasing way of representing open quotation marks. You should mention that this only applies to non-utf-8 locales. de_DE.ISO-8859-1: | $rm

upgrading mysql (Release update: kde3.3, upload targets, kernels, infrastructure)

Re: Steve Langasek in [EMAIL PROTECTED] symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference (/usr/lib/libmysqlclient.so.10) I don't know this problem is missing GLIBC_2.2 symbols issue. It does not clear Christoph's problematic architecture.

Bug#356846: O: pth -- The GNU Portable Threads

Package: wnpp Severity: normal The current maintainer of pth, Luis Bustamante [EMAIL PROTECTED], has orphaned this package. If you want to be the new maintainer, please take it -- see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly.

Bug#855606: sqrt() regression on powerpc/jessie

Package: libc6 Version: 2.19-18+deb8u7 Severity: normal Tags: jessie The following C program produces different output on Jessie and Sid. I believe the Sid output is the correct one, and in fact this is the output that has been observed for the "point" (and "polygon") regression tests for

Bug#855606: sqrt() regression on powerpc/jessie

Re: James Cloos 2017-02-21 > The only ppc I have access to are those in the gcc farm and those (the > online ones anyway) only run fedora and aix, so I cannot test it > myself. > > Except that everything else reports: > > 0X 0X1.C48C6001F0ACP+3 Jessie:

Bug#710275: check for postgresql in NSS check

Re: Aurelien Jarno 2017-11-17 > @@ -22,6 +22,8 @@ glibc (2.25-0experimental4) UNRELEASED; urgency=medium >* debian/sysdeps/ppc64el.mk: disable lock elision. Closes:# 878071. >* debian/script.in/nohwcap.sh: fix alpha ev67 optimized package name. >

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

Re: Florian Weimer 2019-03-25 <87o95yhp3h@mid.deneb.enyo.de> > > For PostgreSQL, this means that the ordering of indexes on disk is > > becoming corrupt, and all "text" (varchar, char, ...) indexes need to > > be rebuilt. (And worse, if that is not done immediately, the tables > > might become

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

Re: Philipp Kern 2019-03-26 <66988de0-f9be-14c0-6b64-df64261fe...@philkern.de> > I suspect this is why MySQL keeps a whole zoo of collations internally > that never change. DB2 and Oracle bundle ICU for that reason, afaict. (But bundling software has other problems, as we all know...) > Is there

Glibc 2.28 breaks collation for PostgreSQL (and others?)

Hi, with the update to glibc 2.28, collation aka sort ordering is changing: $ echo $LANG de_DE.utf8 $ (echo 'a-a'; echo 'a a'; echo 'a+a'; echo 'aa') | sort stretch: aa a a a-a a+a buster: a a a+a a-a aa A vast number of locales is affected, including en_US, possibly all of

Re: Glibc 2.28 breaks collation for PostgreSQL (and others?)

Re: Paul Gevers 2019-04-06 > Regarding this PostgreSQL reindexing issue, is there anything we need to > mention in the release-notes? If this isn't fleshed out, but the most > likely answer is yes, than I'd appreciate it to receive a bug against > release-notes to remind us about it later on.

Bug#1004577: ldconfig -p coredumps

Re: Florian Weimer > > Package: libc-bin > > Version: 2.33-3 > > Severity: important > > > > In > > https://salsa.debian.org/python-team/packages/python-telethon/-/jobs/2413916 > > there is a diff generated between the two builds because a core file > > from `ldconfig -p` appears as

Bug#1004577: ldconfig -p coredumps

Package: libc-bin Version: 2.33-3 Severity: important In https://salsa.debian.org/python-team/packages/python-telethon/-/jobs/2413916 there is a diff generated between the two builds because a core file from `ldconfig -p` appears as /usr/lib/python3.10/dist-packages/core. Backtrace: [0] 18:56

Bug#1043250: tzdata: bring back top-level UTC

Control: severity -1 serious Re: Thorsten Glaser > >Why isn't Etc/UTC an alternative to UTC? > > It’s not as portable, it binds to the Olson database whereas > an otherwise unqualified UTC is pretty standard. Worse, if > Etc/UTC is not available, the fallback makes it assume Etc, > not UTC, as