Bug#679172: marked as done (libc-2.11.3.so: ls[8213]: segfault in libc-2.11.3.so)

2012-06-29 Thread Debian Bug Tracking System
Your message dated Fri, 29 Jun 2012 23:09:51 -0500 with message-id <20120630040906.GA3486@burratino> and subject line [a...@users.sourceforge.net: Re: ls[8213]: segfault in libc-2.11.3.so] has caused the Debian Bug report #679172, regarding libc-2.11.3.so: ls[8213]: segfault in libc-2.11.3.so to b

Bug#678358: marked as done (hurd should not define AF_LINK .....)

2012-06-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jun 2012 03:04:55 + with message-id and subject line Bug#678358: fixed in eglibc 2.13-34 has caused the Debian Bug report #678358, regarding hurd should not define AF_LINK . to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#677919: marked as done (eglibc: [INTL:sk] Slovak po-debconf translation)

2012-06-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jun 2012 03:04:55 + with message-id and subject line Bug#677919: fixed in eglibc 2.13-34 has caused the Debian Bug report #677919, regarding eglibc: [INTL:sk] Slovak po-debconf translation to be marked as done. This means that you claim that the problem has been dea

Bug#674412: marked as done (tcc: undefined symbol '__builtin_expect' on pthread_cleanup_push() call)

2012-06-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jun 2012 03:04:55 + with message-id and subject line Bug#674412: fixed in eglibc 2.13-34 has caused the Debian Bug report #674412, regarding tcc: undefined symbol '__builtin_expect' on pthread_cleanup_push() call to be marked as done. This means that you claim that

Bug#677624: marked as done (multiarch-support should be priority: required)

2012-06-29 Thread Debian Bug Tracking System
Your message dated Sat, 30 Jun 2012 03:04:55 + with message-id and subject line Bug#677624: fixed in eglibc 2.13-34 has caused the Debian Bug report #677624, regarding multiarch-support should be priority: required to be marked as done. This means that you claim that the problem has been deal

r5298 - glibc-package/trunk/debian

2012-06-29 Thread Aurelien Jarno
Author: aurel32 Date: 2012-06-30 02:45:42 + (Sat, 30 Jun 2012) New Revision: 5298 Modified: glibc-package/trunk/debian/changelog Log: Upload to unstable Modified: glibc-package/trunk/debian/changelog === --- glibc-package/tru

r5297 - glibc-package/trunk/debian/patches

2012-06-29 Thread Aurelien Jarno
Author: aurel32 Date: 2012-06-30 00:06:58 + (Sat, 30 Jun 2012) New Revision: 5297 Modified: glibc-package/trunk/debian/patches/series Log: Fix commit r5295 Modified: glibc-package/trunk/debian/patches/series === --- glibc-pac

r5296 - in glibc-package/trunk/debian: . control.in

2012-06-29 Thread Aurelien Jarno
Author: aurel32 Date: 2012-06-29 23:29:16 + (Fri, 29 Jun 2012) New Revision: 5296 Modified: glibc-package/trunk/debian/changelog glibc-package/trunk/debian/control glibc-package/trunk/debian/control.in/main Log: * control.in/main: switch multiarch-support to priority: required. Clo

r5295 - in glibc-package/trunk/debian: . patches po

2012-06-29 Thread Aurelien Jarno
Author: aurel32 Date: 2012-06-29 23:22:51 + (Fri, 29 Jun 2012) New Revision: 5295 Modified: glibc-package/trunk/debian/changelog glibc-package/trunk/debian/patches/series glibc-package/trunk/debian/po/sk.po Log: * Update Slovak debconf translation, by Ivan Mas?\195?\161r. Closes: #

Bug#671715: libc6: Fail to upgrade from 2.13-27 to newer version !

2012-06-29 Thread Aurelien Jarno
On Wed, May 23, 2012 at 07:07:05PM +0200, Aurelien Jarno wrote: > On Sun, May 06, 2012 at 11:14:56AM +0200, Mourad Jaber wrote: > > Package: libc6 > > Version: 2.13-27 > > Severity: important > > > > Dear Maintainer, > > > >* What led up to the situation? > > My system (debian/testing) is usi

Processed: tagging 677919

2012-06-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 677919 + pending Bug #677919 [eglibc] eglibc: [INTL:sk] Slovak po-debconf translation Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 677919: http://bugs.debian.org/cgi-bin/bugreport.cgi

Processed: Re: Bug#679172: libc-2.11.3.so: ls[8213]: segfault in libc-2.11.3.so

2012-06-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tag 679172 + moreinfo Bug #679172 [libc6-i686] libc-2.11.3.so: ls[8213]: segfault in libc-2.11.3.so Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 679172: http://bugs.debian.org/cgi-bin/bug

Bug#679172: libc-2.11.3.so: ls[8213]: segfault in libc-2.11.3.so

2012-06-29 Thread Aurelien Jarno
tag 679172 + moreinfo thanks On Tue, Jun 26, 2012 at 10:31:46PM +0200, a...@users.sourceforge.net wrote: > Package: libc6-i686 > Version: 2.11.3-3 > Severity: normal > File: libc-2.11.3.so > > > Just found this in /var/log/kern.log and /var/log/messages: > > ls[8213]: segfault at 1ebbc787 ip b7

Bug#635192: Processed: Bug#679198: bash: [on native FreeBSD] unable to set FD_CLOEXEC flag

2012-06-29 Thread Robert Millan
2012/6/29 Steven Chamberlain : > #679198 is this bug.  Did you mean #635192? Yes, sorry. > In /usr/include/i386-kfreebsd-gnu/bits/fcntl.h : > >> #if _POSIX_C_SOURCE >= 200809L >> #define O_TTY_INIT      0x0008      /* Restore default termios >> attributes */ >> /* Defining O_CLOEXEC would br

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Christian PERRIER
Quoting Helge Kreutzmann (deb...@helgefjell.de): > Hello, > you are listed as contact person/author of the following locale: > > tr_CY > > This locale comes with a statement > > % Distribution and use is free, also > % for commercial purposes. Recai Oktas is also a Debian developer. CC'ing his

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Børre Gaup
Bearjadat, geassemánu 29. b. 2012 07.03.15 Christian PERRIER čálii: > I add to the CC list another mail address I know about Boerre > Gaup. Also CC'ing Petter Reinholdtsen, ou Debian Wizard for everything > related to Norway, in case he would have alternate ways to reach Boerre. > > Quoting Helge

Processed: Re: Bug#679198: bash: [on native FreeBSD] unable to set FD_CLOEXEC flag

2012-06-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 679198 by 635192 Bug #679198 [bash] bash: Fails to upgrade in kFreeBSD jails 679198 was not blocked by any bugs. 679198 was not blocking any bugs. Added blocking bug(s) of 679198: 635192 > thanks Stopping processing here. Please contact me

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Onur Tolga Sehitoglu
On 06/29/2012 12:30 PM, Helge Kreutzmann wrote: > Hello, > you are listed as contact person/author of the following locale: > > tr_TR > > This locale comes with a statement > > % Distribution and use is free, also > % for commercial purposes. > > Thus it does not allow modification; it is unclear,

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Helge Kreutzmann
Hello, you are listed as contact person/author of the following locale: tt_RU@iqtelif This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As dis

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Helge Kreutzmann
Hello, you are listed as contact person/author of the following locale: tt_RU This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed i

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Helge Kreutzmann
Hello, you are listed as contact person/author of the following locale: tr_TR This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed i

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Helge Kreutzmann
Hello, you are listed as contact person/author of the following locale: tr_CY This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed i

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Helge Kreutzmann
Hello, you are listed as contact person/author of the following locale: tl_PH This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed i

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Eddy Petrișor
2012/6/27 Helge Kreutzmann : > Hello, > you are listed as contact person/author of the following locale: > > ro_RO > > This locale comes with a statement > > % Distribution and use is free, also > % for commercial purposes. > > Thus it does not allow modification; it is unclear, however, if this >

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Helge Kreutzmann
Hello, you are listed as contact person/author of the following locale: tk_TM This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed i

Bug#555168: Unclear license situation for (e)glibc locales provided by you

2012-06-29 Thread Helge Kreutzmann
Hello, you are listed as contact person/author of the following locale: tg_TJ This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed i