Bug#808180: libc6: does not start qtcreator v3.5 and v3.6 "Segmentation fault."

2015-12-16 Thread lukash
Package: libc6 Version: 2.19-22 Severity: normal Tags: upstream Dear Maintainer, run with gdb: $ gdb qtcreator (gdb) run Starting program: ~/Qt5.5.1/Tools/QtCreator/bin/qtcreator [Thread debugging using libthread_db enabled] Using host libthread_db library

Bug#808181: libc6: Upgrade can make the linker unusable

2015-12-16 Thread Dima Kogan
Package: libc6 Severity: normal Hi. I had libc6= 2.19-22 binutils = 2.25-4 and all was well. Then I upgraded to libc6 = 2.21-4 (currently latest in sid). As a result, even the most basic build-time linking would fail. For instance, with a trivial hello-world program: $ gcc-5 -o tst

Displays with a smile

2015-12-16 Thread ExpoFun
This e-mail contains graphics, if you don't see them ยป view it online. ( http://www.expofun.be/index.php?option=com_acymailing=archive=view=29=sPV0Y8X3=88859-PN9zyFi7GIjcPA=component ) Nieuwsbrief ExpoFun 16 december 2015 Beste Rossignol M-R, Op zoek naar displays om te exposeren ? Ontdek ze

Bug#808180: libc6: does not start qtcreator v3.5 and v3.6 "Segmentation fault."

2015-12-16 Thread Samuel Thibault
Hello, lukash, on Wed 16 Dec 2015 23:49:47 +0300, wrote: > (gdb) run > Starting program: ~/Qt5.5.1/Tools/QtCreator/bin/qtcreator > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7fffec5cb700 (LWP 1282)] >

Fixing the armhf linker path

2015-12-16 Thread Aurelien Jarno
At the beginning of the armhf port the hard-float dynamic linker has been chosen to be '/lib/arm-linux-gnueabihf/ld-linux.so.3'. However it has been standardized later as '/lib/ld-linux-armhf.so.3' [1]. We have changed it in Debian, and added a patch to the glibc [2] to temporarily support both

Re: Fixing the armhf linker path

2015-12-16 Thread Emilio Pozuelo Monfort
On 16/12/15 23:30, Aurelien Jarno wrote: > At the beginning of the armhf port the hard-float dynamic linker has > been chosen to be '/lib/arm-linux-gnueabihf/ld-linux.so.3'. However it > has been standardized later as '/lib/ld-linux-armhf.so.3' [1]. We have > changed it in Debian, and added a

Bug#808181: libc6: Upgrade can make the linker unusable

2015-12-16 Thread Aurelien Jarno
On 2015-12-16 13:15, Dima Kogan wrote: > Package: libc6 > Severity: normal > > Hi. I had > > libc6= 2.19-22 > binutils = 2.25-4 > > and all was well. Then I upgraded to libc6 = 2.21-4 (currently latest in > sid). As a result, even the most basic build-time linking would fail. > For

Bug#808143: bg_BG locale should use colon as time separator, not comma

2015-12-16 Thread Aurelien Jarno
On 2015-12-16 12:43, Damyan Ivanov wrote: > Package: locales > Version: 2.21-4 > Severity: normal > Tags: upstream patch > > The time format specified in the bg_BG locale is: > > $ locale -k t_fmt t_fmt_ampm date_fmt > t_fmt="%k,%M,%S" > t_fmt_ampm="%l,%M,%S" > date_fmt="%a %b %e %H:%M:%S %Z

Bug#808143: bg_BG locale should use colon as time separator, not comma

2015-12-16 Thread Damyan Ivanov
Package: locales Version: 2.21-4 Severity: normal Tags: upstream patch The time format specified in the bg_BG locale is: $ locale -k t_fmt t_fmt_ampm date_fmt t_fmt="%k,%M,%S" t_fmt_ampm="%l,%M,%S" date_fmt="%a %b %e %H:%M:%S %Z %Y" t_fmt[_ampm] should use colons instead of commas, like