Bug#181494: cleanup this bug

2006-08-09 Thread Adrian Bunk
tags 181494 -sid clone 181494 -1 retitle 181494 glibc: contains non-free docs retitle -1 glibc: contains possibly non-free code tags -1 -fixed-in-experimental thanks Some cleanups for the bug that should have been done long ago: - remove the wrong sid tag - split the two issues into two bugs -

Bug#382175: cleanup this bug

2006-08-22 Thread Adrian Bunk
On Thu, Aug 17, 2006 at 03:16:17PM -0400, Branden Robinson wrote: submitter 382175 Branden Robinson [EMAIL PROTECTED] thanks On Mon, Aug 14, 2006 at 06:45:08PM +, Brian M. Carlson wrote: On Sun, Aug 13, 2006 at 10:51:54PM -0400, Branden Robinson wrote: On Wed, Aug 09, 2006 at

Bug#155939: The dependencies of libc6 must handle packages that break without db1

2002-08-09 Thread Adrian Bunk
On Fri, 9 Aug 2002, Ben Collins wrote: I don't see a way how this could be handled outside the dependencies of libc6. One possible solution is to create a libdb1g package in oldlibs and let the libc6 in sarge depend on this package (the dependency can be dropped after sarge is released).

Bug#165921: libc6: Please use debconf for the Restarting services question

2002-10-22 Thread Adrian Bunk
Package: libc6 Version: 2.3.1-3 Severity: wishlist When upgrading from an older version libc6 asks the Restarting services question. It would be nice if this would be asked via debconf to make automated upgrades easier. TIA Adrian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject

Bug#165921: acknowledged by developer (Re: Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade)

2002-11-08 Thread Adrian Bunk
reopen 165921 thanks On Thu, Nov 07, 2002 at 01:18:14PM -0600, Debian Bug Tracking System wrote: ... Sorry, We cannot make libc6 depend on debconf. That would make debconf more essential than libc6. You can see the circular dep problem. These questions are only relevant when upgrading libc6.

Bug#165921: acknowledged by developer (Re: Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade)

2002-11-09 Thread Adrian Bunk
On Fri, Nov 08, 2002 at 10:12:24AM -0500, Ben Collins wrote: On Fri, Nov 08, 2002 at 01:51:47PM +0100, Adrian Bunk wrote: Technically the following solution should be possible (pseudocode): Not to mention that even if debconf is installed, nothing says that the system (especially during

Bug#165921: acknowledged by developer (Re: Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade)

2002-11-09 Thread Adrian Bunk
reopen 165921 thanks On Fri, Nov 08, 2002 at 10:11:11AM -0500, Ben Collins wrote: On Fri, Nov 08, 2002 at 01:51:47PM +0100, Adrian Bunk wrote: reopen 165921 thanks On Thu, Nov 07, 2002 at 01:18:14PM -0600, Debian Bug Tracking System wrote: ... Sorry, We cannot make libc6 depend

Bug#170385: libc6 should conflict with wine ( 0.0.20021007-1) and perhaps other packages

2002-11-23 Thread Adrian Bunk
Package: libc6 Version: 2.3.1-5 Severity: grave libc6 should conflict with wine ( 0.0.20021007-1) because earlier wine packages don't work with glibc 2.3 (see #165323). Technically the usage of __libc_fork was a bug in Wine. Without a conflict in libc6 many people doing a partial upgrade from

Bug#170385: It seems this bug isn't fixed

2003-01-14 Thread Adrian Bunk
The changelog of glibc 2.3.1-6 says: - debian/control.in/libc: Conflict against wine ( 0.0.20021007-1) (Closes: #170385) Also conflict against php4 ( 4:4.2.3-5) There seems to be neither a conflict with libwine nor a conflict with php4 in libc6 2.3.1-9. cu Adrian --

This problem can be solved from within gcc

2003-06-01 Thread Adrian Bunk
reassign 194339 gcc-3.3 retitle 194339 __thread problem with woody backports of gcc 3.3 thanks I had to solve the same problem in my backport of gcc 3.3 to woody [1]. There are no changes to the glibc packages in woody needed, gcc already includes a fix. The problem is that the build of the

Bug#165921: libc6: Please use debconf for the Restarting services question

2002-10-22 Thread Adrian Bunk
Package: libc6 Version: 2.3.1-3 Severity: wishlist When upgrading from an older version libc6 asks the Restarting services question. It would be nice if this would be asked via debconf to make automated upgrades easier. TIA Adrian

Bug#165921: acknowledged by developer (Re: Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade)

2002-11-08 Thread Adrian Bunk
reopen 165921 thanks On Thu, Nov 07, 2002 at 01:18:14PM -0600, Debian Bug Tracking System wrote: ... Sorry, We cannot make libc6 depend on debconf. That would make debconf more essential than libc6. You can see the circular dep problem. These questions are only relevant when upgrading libc6.

Bug#165921: acknowledged by developer (Re: Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade)

2002-11-09 Thread Adrian Bunk
On Fri, Nov 08, 2002 at 10:12:24AM -0500, Ben Collins wrote: On Fri, Nov 08, 2002 at 01:51:47PM +0100, Adrian Bunk wrote: Technically the following solution should be possible (pseudocode): Not to mention that even if debconf is installed, nothing says that the system (especially during

Bug#165921: acknowledged by developer (Re: Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade)

2002-11-09 Thread Adrian Bunk
reopen 165921 thanks On Fri, Nov 08, 2002 at 10:11:11AM -0500, Ben Collins wrote: On Fri, Nov 08, 2002 at 01:51:47PM +0100, Adrian Bunk wrote: reopen 165921 thanks On Thu, Nov 07, 2002 at 01:18:14PM -0600, Debian Bug Tracking System wrote: ... Sorry, We cannot make libc6 depend

Bug#170385: libc6 should conflict with wine ( 0.0.20021007-1) and perhaps other packages

2002-11-23 Thread Adrian Bunk
Package: libc6 Version: 2.3.1-5 Severity: grave libc6 should conflict with wine ( 0.0.20021007-1) because earlier wine packages don't work with glibc 2.3 (see #165323). Technically the usage of __libc_fork was a bug in Wine. Without a conflict in libc6 many people doing a partial upgrade from

Bug#184705: wine in testing is recent enough

2003-03-14 Thread Adrian Bunk
Hi Silas, I'm surprised about your bug report. The wine package in testing is recent enough to fulfill the conflict in libc6. The conflict in libc6 is _really_ needed (older Wine packages don't work with libc6 2.3). Are you using apt pinning? If yes please disable apt pinning and test whether

Bug#187991: bug#1536: mutt-1.5.4i: Segment fault with long lines when LANG=*.UTF-8

2003-04-27 Thread Adrian Bunk
On Sun, Apr 27, 2003 at 05:59:24PM +0200, Anders Helmersson wrote: On Sat, 2003-04-26 at 19:38:11 +0200, Thomas Roessler wrote: With mutt -F your colors -n -f segfault, I can't reproduce this. (Latest CVS checkout; Redhat 7.3.) The problem seems to be related to regex. The segfault occurs

This problem can be solved from within gcc

2003-05-31 Thread Adrian Bunk
reassign 194339 gcc-3.3 retitle 194339 __thread problem with woody backports of gcc 3.3 thanks I had to solve the same problem in my backport of gcc 3.3 to woody [1]. There are no changes to the glibc packages in woody needed, gcc already includes a fix. The problem is that the build of the

#213745: dictd doesn't run: Suggestion how to fix this issue

2003-10-10 Thread Adrian Bunk
severity 213745 grave thanks First of all, I consider this bug RC since it causes some breakage for users. There should be a solution that doesn't require manual intervention of the user installing dictd. This seems to be a complicated problem: - dictd databases should be UTF-8 encoded - if

Bug#215903: locales installs uncompressed manual pages

2003-10-15 Thread Adrian Bunk
Package: locales Version: 2.3.2-8 Severity: normal locales ships the following uncompressed manual pages: /usr/share/man/man8/locale-gen.8 /usr/share/man/man5/locale.alias.5 /usr/share/man/man5/locale.gen.5 Section 12.1. of your policy says: -- snip -- ... Manual pages should be

Bug#220983: libc6 must conflict with cyrus-imapd ( 1.5.19-15)

2003-11-15 Thread Adrian Bunk
Package: libc6 Version: 2.3.2.ds1-10 Severity: grave #219618 is a result of the errno warning message in cyrus-imapd. I'm personally knowing a person who had mail bounces since this error message confused other programs.

Bug#204643: glibc: Could you add NPTL?

2003-08-14 Thread Adrian Bunk
Package: glibc Version: 2.3.2-2 Severity: wishlist Could you add NPTL? Now that kernel 2.6 is coming nearer it would be nice to have it available. TIA Adrian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#215903: locales installs uncompressed manual pages

2003-10-15 Thread Adrian Bunk
Package: locales Version: 2.3.2-8 Severity: normal locales ships the following uncompressed manual pages: /usr/share/man/man8/locale-gen.8 /usr/share/man/man5/locale.alias.5 /usr/share/man/man5/locale.gen.5 Section 12.1. of your policy says: -- snip -- ... Manual pages should be

Bug#218717: Wine doesn't work with NPTL

2003-11-02 Thread Adrian Bunk
As a note: Wine doesn't seem to work with NPTL. Workaround:   LD_ASSUME_KERNEL=2.4.22 wine ... This needs to be handled in Wine, and the conflict of libc6 with Wine will need to be raised after it will be fixed in Wine. cu Adrian -- Is there not promise of rain? Ling Tan asked

Bug#220983: libc6 must conflict with cyrus-imapd ( 1.5.19-15)

2003-11-15 Thread Adrian Bunk
Package: libc6 Version: 2.3.2.ds1-10 Severity: grave #219618 is a result of the errno warning message in cyrus-imapd. I'm personally knowing a person who had mail bounces since this error message confused other programs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Bug#235759: Comentar on which replacement for German quotes

2004-03-28 Thread Adrian Bunk
Hi, as a German native speaker with some interest on typography but virtually no knowledge on UTF-8 some comments: The common quotes in German today are double open quotes (low position) U201E together with double closed quote (high position) U201C The current conversion ,,text looks

Bug#235759: Comentar on which replacement for German quotes

2004-03-30 Thread Adrian Bunk
On Mon, Mar 29, 2004 at 11:02:11PM +0200, Denis Barbier wrote: On Mon, Mar 29, 2004 at 02:47:42AM +0200, Adrian Bunk wrote: [...] I am a bit surprised that this discussion and all patches sent only cover de_DE, although there are altogether three common de_ locales plus two others

Bug#165921: acknowledged by developer (Re: Bug#165921: libc6: Please use debconf to warn of likely breakage on major upgrade)

2004-10-11 Thread Adrian Bunk
On Sun, Oct 10, 2004 at 12:12:17PM +0900, GOTO Masanori wrote: At Sat, 9 Nov 2002 11:56:07 +0100, Adrian Bunk wrote: If you are upgrading to woody, one can also assume you have read the upgrade part of the woody release notes. The libc6 issues would be documented there. Please read

Bug#55615: libc6-bin-2.1.2-11 conflicts with locales_2.0.7.19981211-6

2000-01-19 Thread Adrian Bunk
Package: libc6-bin Version: 2.1.2-11 Hi, libc6-bin-2.1.2-11 conflicts with locales_2.0.7.19981211-6 because they both ship a /usr/bin/locale . You have to update locales before (locales_2.1.2-11.0.1 worked fine for me). The exact error message was: trying to overwrite `/usr/bin/locale',

Bug#64074: This bug seems to be RC

2000-05-22 Thread Adrian Bunk
severity 64074 important thanks This bug seems to be RC. The submitter said: However, neither apache nor ssh run afterwards. Since one might try to upgrade with only ssh connection to the box this can be a major problem (Severity: important??) I can see no comment on this bug in the BTS, and

Bug#322768: libc6: sshd after upgrade not working

2005-08-12 Thread Adrian Bunk
Package: libc6 Version: 2.3.5-3 Severity: critical After upgrading from the sarge libc6, sshd on my computer no longer accepted connections. Restarting sshd fixed the problem. It seems the restart services question in the postinst should be asked for upgrades from 2.3.5 . I've set the

Bug#322768: libc6: sshd after upgrade not working

2005-08-13 Thread Adrian Bunk
On Sat, Aug 13, 2005 at 12:02:48PM +0900, GOTO Masanori wrote: At Fri, 12 Aug 2005 20:50:25 +0200, Adrian Bunk wrote: After upgrading from the sarge libc6, sshd on my computer no longer accepted connections. Restarting sshd fixed the problem. It seems the restart services question

Re: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Adrian Bunk
On Sun, Nov 06, 2016 at 05:41:34PM -0200, Henrique de Moraes Holschuh wrote: > On Sun, 06 Nov 2016, Ben Hutchings wrote: > > It's worth noting that TSX is broken in 'Haswell' processors and is > > supposed to be disabled via a microcode update. I don't know whether > > glibc avoids using it on

Re: Bug#842796: libc recently more aggressive about pthread locks in stable ?

2016-11-06 Thread Adrian Bunk
On Sun, Nov 06, 2016 at 08:04:39AM +0100, Petter Reinholdtsen wrote: > [Henrique de Moraes Holschuh] > > And what should we do about Debian stretch, then? > > I believe a good start would be to add an assert() in a test version of > glibc and then run all the autopkgtest scripts on the packages

Bug#844315: tzdata version breaks dist-upgrade leaving version from oldstable security installed

2016-11-14 Thread Adrian Bunk
On Mon, Nov 14, 2016 at 12:54:27PM +0100, Marcel Meckel wrote: > Package: tzdata > Version: 2016i-0+deb7u1 > Severity: critical > > Upgrading a fully updated wheezy system (incl. security repo) to > jessie (incl. security repo) results in tzdata not being updated > because the version in

Re: Bug#845523: dar: FTBFS: undefined reference to `__memcpy_chk'

2016-11-24 Thread Adrian Bunk
reassign 845521 libc6-dev 2.24-6 reassign 845523 libc6-dev 2.24-6 forcemerge 845521 845523 retitle 845521 libc6-dev: static linking with stack protector fails: undefined reference to `__memcpy_chk' affects 845521 src:dar src:aide thanks On Thu, Nov 24, 2016 at 09:54:34AM +0100, Chris Lamb wrote:

Bug#873097: glibc: FTBFS on *all* architectures except m68k, powerpcspe, sh4

2017-08-24 Thread Adrian Bunk
On Thu, Aug 24, 2017 at 04:48:55PM +0200, Thorsten Glaser wrote: > Source: glibc > Version: 2.24-16 > Severity: serious > Justification: fails to build from source (but built successfully in the past) > > cf. https://buildd.debian.org/status/package.php?p=glibc > > For over three days now,

Bug#889050: dateutils FTBFS with tzdata >= 2018b-1

2018-02-01 Thread Adrian Bunk
Source: dateutils Version: 0.4.1-2 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dateutils.html ... FAIL: dzone.007 === $ dzone --next Asia/Singapore 2014-02-22 --- "expected output 5c83cb99" 2019-03-06 07:12:58.247403471 -1200 +++ "actual

Bug#915321: Mutex creation failed

2018-12-02 Thread Adrian Bunk
Control: unmerge -1 915339 Control: reassign -1 r-cran-later 0.7.4+dfsg-1 Control: retitle -1 r-cran-later: Mutex creation failed with glibc 2.28 Control: forwarded -1 https://github.com/r-lib/later/issues/77 Control: block 915339 by -1 Control: retitle 915339 libc6 needs Conflicts with unfixed

Bug#918583: libc6: version in nocache Breaks is incorrect

2019-01-07 Thread Adrian Bunk
Package: libc6 Version: 2.28-4 Severity: serious Breaks: ..., nocache (<< 1.0-1),... 1.0-1 is the version in stable, so this is basically a nop. It should be Breaks: nocache (<< 1.1-1~)

Re: Options for 64-bit time_t support on 32-bit architectures

2019-07-19 Thread Adrian Bunk
[ only speaking for myself ] On Thu, Jul 18, 2019 at 11:05:53PM +0200, Florian Weimer wrote: >... > The consequence is that in order to build 32-bit-time_t libraries > (Gtk, for example), an old glibc needs to be kept around. In > practice, it would probably mean that it is impossible to

Re: Options for 64-bit time_t support on 32-bit architectures

2019-07-19 Thread Adrian Bunk
On Fri, Jul 19, 2019 at 07:13:28PM +0200, Florian Weimer wrote: > * Adrian Bunk: >... > For comparison, the original plan was to provide a macro, perhaps > -D_TIME_BITS=32 and -D_TIME_BITS=64, to select at build time which ABI > set is used (“dual ABI”). To me this would sound li