Bug#762611: locales: problems for en_CA:en

2014-09-23 Thread westlake

Package: locales
Version: 2.19-10
Severity: important

applying en_CA.UTF-8 to locales is problematic

dpkg-reconfigure locales displays ncurses screens and two languages were 
selected, later output gives



Generating locales (this might take a while)...
  en_CA.UTF-8...Killed
 done
  en_US.UTF-8...Killed
 done
Generation complete.
*** update-locale: Error: invalid locale settings:  LANGUAGE=en_CA:en 
LANG=en_CA.UTF-8



I'm doing this over an ssh session, but it should still be passing
(I'm noticing env variable LC_CTYPE still remains to 'C')

thanks


--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/5421c08e.7070...@videotron.ca



Bug#760902: libc6: ld-linux-x86-64.so.2 segfaults with LD_BIND_NOW=yes on binaries generated by golang

2014-09-23 Thread Jakub Wilk

Control: forcemerge 710521 -1

* Paul Wise p...@debian.org, 2014-09-09, 22:02:
Confirmed with strace that this is caused by a SIGSEGV in libc6 in the 
following packages:


aptly heartbleeder golang-go.tools

These command-lines cause a segfault:

LD_BIND_NOW=yes /usr/bin/aptly
LD_BIND_NOW=yes /usr/bin/heartbleeder
LD_BIND_NOW=yes /usr/bin/present
LD_BIND_NOW=yes /usr/bin/godoc
LD_BIND_NOW=yes /usr/bin/updater
LD_BIND_NOW=yes /usr/bin/builder

Interestingly the issue doesn't happen with docker.io and some of the 
other executables in golang-go.tools even though they are written in 
Go.


This was already known as #710521, but thanks for providing fresh 
examples. :-)


BTW, piuparts knows which packages adequate(1) tripped over:
https://piuparts.debian.org/sid/inadequate_exit_issue.html

I've filed a new bug against adequate: #762615

--
Jakub Wilk


--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140923191828.ga4...@jwilk.net



Processed: Re: Bug#760902: libc6: ld-linux-x86-64.so.2 segfaults with LD_BIND_NOW=yes on binaries generated by golang

2014-09-23 Thread Debian Bug Tracking System
Processing control commands:

 forcemerge 710521 -1
Bug #710521 [libc6] ldd -r /usr/bin/go segfaults
Bug #760902 [libc6] libc6: ld-linux-x86-64.so.2 segfaults with LD_BIND_NOW=yes 
on some binaries generated by golang
Added indication that 760902 affects osdsh,golang-go
Marked as found in versions eglibc/2.18-4 and eglibc/2.17-3.
Merged 710521 760902

-- 
710521: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710521
760902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b760902.141149991331767.transcr...@bugs.debian.org



Bug#762611: locales: problems for en_CA:en

2014-09-23 Thread Aurelien Jarno
On Tue, Sep 23, 2014 at 02:48:46PM -0400, westlake wrote:
 Package: locales
 Version: 2.19-10
 Severity: important
 
 applying en_CA.UTF-8 to locales is problematic
 
 dpkg-reconfigure locales displays ncurses screens and two languages
 were selected, later output gives
 
 
 Generating locales (this might take a while)...
   en_CA.UTF-8...Killed

The problem seems to come from the Killed. Do you have any things in
the logs showing why the process has been killed? Are you running on a
low memory machine without enough swap?

Aurelien
 

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


-- 
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140923202539.gn...@hall.aurel32.net



Bug#762611: locales: problems for en_CA:en

2014-09-23 Thread westlake
You're right, the problem was free ram, how could I have missed that? 
lol. Sorry for the false positive, there's zero bug in this(been filing 
other more significant bugs lately here with kvm). fwiw there was 31 meg 
free on this 128 Mb and apparently this wasn't enough to process 
dpkg-reconfigure properly. There is a memory stats that is shown in one 
of the logs so it definitely was a memory issue.


thanks


--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/54220eb1.4030...@videotron.ca