Processed: Raising severity to critical

2013-10-23 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 727177 critical
Bug #727177 [libnss-ldap] Upgrade of libnss-ldap to 265-1 causes important 
binaries to segfault
Severity set to 'critical' from 'normal'
> kthxbye
Stopping processing here.

Please contact me if you need assistance.
-- 
727177: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.138253160614464.transcr...@bugs.debian.org

Bug#727177: Raising severity to critical

2013-10-23 Thread Wolodja Wentland 
severity 727177 critical
kthxbye

I have just spoken to another user on IRC who reported identical problems
after upgrading libnss-ldap from 264-2.5 to 265-1. The problems (segfaults of
various binaries from other packages) seized once the user downgraded back to
264-2.5. 

I have not personally encountered this problem and asked the user to
provide any additional information about this bug he can think of, but simply
wanted to make sure that other users won't run into this by raising the
severity now.

thanks
-- 
Wolodja 

4096R/CAF14EFC
081C B7CD FF04 2BA9 94EA  36B2 8B7F 7D30 CAF1 4EFC


signature.asc
Description: Digital signature

Bug#727211: libsane: "Failed to start scanner: Invalid argument" when using a genesys supported scanner

2013-10-23 Thread Johan Spee 
Package: libsane
Version: 1.0.23-3
Severity: normal
Tags: upstream

Dear Maintainer,


I have attached a Canoscan Lide 110 scanner to my system that is running Debian
testing (with a bit of sid).
The scanner is recognized:

~$ lsusb
Bus 001 Device 006: ID 04a9:1909 Canon, Inc. CanoScan LiDE 110

~$  sane-find-scanner
found USB scanner (vendor=0x04a9 [Canon], product=0x1909 [CanoScan]) at
libusb:001:006


PROBLEM:
My scanner program (xsane, but simple-scan has similar problems) reports no
problems when starting up, but when a scan is started a dialog pops up: "Failed
to start scanner: Invalid argument". After that the scanner must be re-plugged
to be recognized by the system again.

I tried  Ubuntu 13.10 (live cd) and ran into the very same problem, which
suggets that my configuration is not to blame.

The hardware is fine too: No problems with Vuescan-linux or when attached to a
Win7 system.

 so the culprit is probably SANE, which uses genesys for this scanner:

~$ scanimage -L
device `genesys:libusb:001:006' is a Canon LiDE 110 flatbed scanner

~$ man sane-genesys
At  present,  the following scanners are known to work with this backend:
Canon LiDE .../110/...

~$ cat /etc/sane.d/genesys.conf
 # Canon LiDE 110
usb 0x04a9 0x1909

The genesis man-pages list the following files:

~$ man sane-genesys
FILES
/etc/sane.d/genesys.conf
/usr/lib/arch_triplet/sane/libsane-genesys.a
/usr/lib/arch_triplet/sane/libsane-genesys.so

However, /usr/lib/arch_triplet/ does not exist and no files that match libsane-
genesys.* can be found on my system.
The files libsane-genesys.a and libsane-genesys.so are part of the libsane-dev
package, but installing it makes no difference.

An internet search for "CanoScan LiDE 110" + "Invalid argument" results in many
hits, but no solution.



regards, and thanks for your help.

Johan Spee



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.10-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libsane depends on:
ii  acl2.2.52-1
ii  adduser3.113+nmu3
ii  libavahi-client3   0.6.31-2
ii  libavahi-common3   0.6.31-2
ii  libc6  2.17-93
ii  libcups2   1.6.3-1
ii  libexif12  0.6.21-1
ii  libgphoto2-2   2.4.14-2.3
ii  libgphoto2-port0   2.4.14-2.3
ii  libieee1284-3  0.2.11-12
ii  libjpeg8   8d-1
ii  libsane-common 1.0.23-3
ii  libtiff4   3.9.7-2
ii  libusb-1.0-0   2:1.0.17-1+b1
ii  libv4l-0   1.0.0-1
ii  multiarch-support  2.17-93
ii  udev   204-5

Versions of packages libsane recommends:
pn  libsane-extras  
ii  sane-utils  1.0.23-3

Versions of packages libsane suggests:
ii  avahi-daemon  0.6.31-2
ii  hplip 3.13.9-2
pn  hpoj  

-- Configuration Files:
/etc/sane.d/dll.conf changed:
net
abaton
agfafocus
apple
avision
artec
artec_eplus48u
as6e
bh
canon
canon630u
canon_dr
cardscan
coolscan
coolscan3
dell1600n_net
dmc
epjitsu
epson2
fujitsu
genesys
gt68xx
hp
hp3900
hpsj5s
hp3500
hp4200
hp5400
hp5590
hpljm1005
hs2p
ibm
kodak
kodakaio
kvs1025
kvs20xx
leo
lexmark
ma1509
magicolor
matsushita
microtek
microtek2
mustek
mustek_usb
mustek_usb2
nec
niash
pie
pixma
plustek
qcam
ricoh
rts8891
s9036
sceptre
sharp
sm3600
sm3840
snapscan
sp15c
tamarack
teco1
teco2
teco3
u12
umax
umax1220u
v4l
xerox_mfp
hpaio


-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20131023125858.8027.81186.reportbug@debian

Bug#727177: Upgrade of libnss-ldap to 265-1 causes important binaries to segfault

2013-10-23 Thread Wolfgang Scheicher 

I just did run into exactely the same issue.
No login possible after that update, when chrooting from a rescue system zsh 
did segfault.

i was lucky to find bash still usable and i managed to identify libnss-ldap as 
the cause and could sucessfully downgrade to 264-2.5


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/2818113.GSsiE4j9iv@hexen

Bug#725569: libpam-unix2: FTBFS: configure.in:36: error: required file './compile' not found

2013-10-23 Thread gregor herrmann 
On Thu, 17 Oct 2013 22:11:29 +0900, Hideki Yamane wrote:

> Hi,
> 
>  Attached patch would fix this FTBFS, could you consider to apply it,
>  please?

This package is orphaned, so I guess you won't get many answers but
should just go on with a QA upload :) 


Cheers,
gregor

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Rolling Stones


signature.asc
Description: Digital signature

Bug#727461: mod-gnutls: update config.{sub,guess} for the AArch64 port

2013-10-23 Thread Matthias Klose 
Package: src:mod-gnutls
Version: 0.5.10-2
Severity: normal
User: debian-...@lists.debian.org
Usertags: arm64

The package fails to build on arm64 (aarch64-linux-gnu), because the
config.{guess,sub} files are out of date, and are not updated during
the build.  If possible, please do not update these files directly,
but build-depend on autotools-dev instead, and use the tools provided
by autotools-dev to update these files.

  - For dh, call dh --with autotools_dev (yes, underscore).

  - For other rules files, call dh_autotools-dev_updateconfig before
calling configure (in the build or configure target), and call
dh_autotools-dev_restoreconfig before calling dh_clean in the clean
target.

After the build on any architecture, and before a clean, a grep for
aarch64 in the config.sub file(s) should print some lines.

The full build log can be found at:
http://people.debian.org/~doko/logs/arm64-20131023/logs/buildlog_ubuntu-trusty-arm64.mod-gnutls_0.5.10-2_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.

Please note that these build were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.

[...]
dvidir='${docdir}'
exec_prefix='NONE'
have_apr_memcache=''
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh=''
libdir='${prefix}/lib/aarch64-linux-gnu'
libexecdir='${prefix}/lib/aarch64-linux-gnu'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p=''
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target=''
target_alias=''
target_cpu=''
target_os=''
target_vendor=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "mod_gnutls"
#define PACKAGE_TARNAME "mod_gnutls"
#define PACKAGE_VERSION "0.5.10"
#define PACKAGE_STRING "mod_gnutls 0.5.10"
#define PACKAGE_BUGREPORT ""
#define PACKAGE_URL ""

configure: exit 1
dh_auto_configure: ./configure --build=aarch64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--libdir=${prefix}/lib/aarch64-linux-gnu 
--libexecdir=${prefix}/lib/aarch64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --with-apxs=/usr/bin/apxs2 returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory `/build/buildd/mod-gnutls-0.5.10'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1vz7bu-0003oh...@ravel.debian.org

Bug#727380: freewnn: update config.{sub,guess} for the AArch64 port

2013-10-23 Thread Matthias Klose 
Package: src:freewnn
Version: 1.1.1~a021+cvs20130302-3
Severity: normal
User: debian-...@lists.debian.org
Usertags: arm64

The package fails to build on arm64 (aarch64-linux-gnu), because the
config.{guess,sub} files are out of date, and are not updated during
the build.  If possible, please do not update these files directly,
but build-depend on autotools-dev instead, and use the tools provided
by autotools-dev to update these files.

  - For dh, call dh --with autotools_dev (yes, underscore).

  - For other rules files, call dh_autotools-dev_updateconfig before
calling configure (in the build or configure target), and call
dh_autotools-dev_restoreconfig before calling dh_clean in the clean
target.

After the build on any architecture, and before a clean, a grep for
aarch64 in the config.sub file(s) should print some lines.

The full build log can be found at:
http://people.debian.org/~doko/logs/arm64-20131023/logs/buildlog_ubuntu-trusty-arm64.freewnn_1.1.1~a021+cvs20130302-3_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.

Please note that these build were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.

[...]
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
if_disable_sub_bindir=''
if_enable_sub_bindir=''
includedir='${prefix}/include'
infodir='${prefix}/share/info'
ipv6=''
kWnn=''
libdir='${prefix}/lib/aarch64-linux-gnu'
libexecdir='${prefix}/lib/aarch64-linux-gnu'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='/usr/share/man'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''
unsafe_path=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "FreeWnn"
#define PACKAGE_TARNAME "FreeWnn"
#define PACKAGE_VERSION "1.1.1-cvs-a022"
#define PACKAGE_STRING "FreeWnn 1.1.1-cvs-a022"
#define PACKAGE_BUGREPORT "freewnn-users-ow...@lists.sourceforge.jp"
#define PACKAGE_URL ""

configure: exit 1
dh_auto_configure: ./configure --build=aarch64-linux-gnu --prefix=/usr 
--includedir=${prefix}/include --mandir=${prefix}/share/man 
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--libdir=${prefix}/lib/aarch64-linux-gnu 
--libexecdir=${prefix}/lib/aarch64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --prefix=/usr --mandir=/usr/share/man 
--enable-client=yes --disable-traditional-layout returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory `/build/buildd/freewnn-1.1.1~a021+cvs20130302'
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1vz7ay-0002zq...@ravel.debian.org

Bug#727457: mgp: update config.{sub,guess} for the AArch64 port

2013-10-23 Thread Matthias Klose 
Package: src:mgp
Version: 1.13a+upstream20090219-6
Severity: normal
User: debian-...@lists.debian.org
Usertags: arm64

The package fails to build on arm64 (aarch64-linux-gnu), because the
config.{guess,sub} files are out of date, and are not updated during
the build.  If possible, please do not update these files directly,
but build-depend on autotools-dev instead, and use the tools provided
by autotools-dev to update these files.

  - For dh, call dh --with autotools_dev (yes, underscore).

  - For other rules files, call dh_autotools-dev_updateconfig before
calling configure (in the build or configure target), and call
dh_autotools-dev_restoreconfig before calling dh_clean in the clean
target.

After the build on any architecture, and before a clean, a grep for
aarch64 in the config.sub file(s) should print some lines.

The full build log can be found at:
http://people.debian.org/~doko/logs/arm64-20131023/logs/buildlog_ubuntu-trusty-arm64.mgp_1.13a+upstream20090219-6_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.

Please note that these build were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.

[...]
Setting up x11proto-record-dev (1.14.2-1) ...
Setting up libxtst-dev:arm64 (2:1.2.2-1) ...
Setting up sharutils (1:4.11.1-1ubuntu2) ...
Setting up xutils-dev (1:7.7~1ubuntu5) ...
Setting up python3 (3.3.2-14ubuntu1) ...
running python rtupdate hooks for python3.3...
running python post-rtupdate hooks for python3.3...
Setting up dh-python (1.20131003-1) ...
Setting up apparmor-easyprof (2.8.0-0ubuntu31) ...
Setting up dh-apparmor (2.8.0-0ubuntu31) ...
Setting up debhelper (9.20130630ubuntu1) ...
Setting up devscripts (2.13.4) ...
Processing triggers for libc-bin ...
Checking correctness of source dependencies...
Toolchain package versions: libc6-dev_2.17-93ubuntu4 make_3.81-8.2ubuntu3 
dpkg-dev_1.16.12ubuntu1 gcc-4.8_4.8.1-10ubuntu8 g++-4.8_4.8.1-10ubuntu8 
binutils_2.23.52.20130913-0ubuntu1 libstdc++-4.8-dev_4.8.1-10ubuntu8 
libstdc++6_4.8.1-10ubuntu8
--
dpkg-source: warning: -sn is not a valid option for 
Dpkg::Source::Package::V3::quilt
gpgv: Signature made Mon Oct  1 12:37:39 2012 UTC using RSA key ID 7D86500B
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on 
./mgp_1.13a+upstream20090219-6.dsc
dpkg-source: info: extracting mgp in mgp-1.13a+upstream20090219
dpkg-source: info: unpacking mgp_1.13a+upstream20090219.orig.tar.gz
dpkg-source: info: unpacking mgp_1.13a+upstream20090219-6.debian.tar.gz
dpkg-source: info: applying 01_mgpnet_in.diff
dpkg-source: info: applying 04_tex2ps_bashism.diff
dpkg-source: info: applying 05_rakugaki_cursor.diff
dpkg-source: info: applying 568339.patch
dpkg-buildpackage: source package mgp
dpkg-buildpackage: source version 1.13a+upstream20090219-6
 dpkg-source --before-build mgp-1.13a+upstream20090219
dpkg-buildpackage: host architecture arm64
 /usr/bin/fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp install-stamp
[ ! -f Makefile ] || make distclean
rm -f `find . -name "*~"`
rm -rf debian/mgp debian/files* core debian/substvars
rm -f Makefile Imakefile *._man
dh_clean
dpkg-buildpackage: warning: debian/rules must be updated to support the 
'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be 
missing)
 debian/rules build
dh_testdir
./configure --prefix=/usr  --enable-locale --enable-freetype 
--enable-freetype-charset16 --enable-xft2 --disable-vflib --enable-gif 
aarch64-linux-gnu
configure: WARNING: you should use --build, --host, --target
checking whether make sets $(MAKE)... yes
checking build system type... Invalid configuration `aarch64-linux-gnu': 
machine `aarch64' not recognized
configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed
make: *** [build-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1vz7bq-0003mp...@ravel.debian.org

Bug#727395: libbinio: update config.{sub,guess} for the AArch64 port

2013-10-23 Thread Matthias Klose 
Package: src:libbinio
Version: 1.4+dfsg1-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: arm64

The package fails to build on arm64 (aarch64-linux-gnu), because the
config.{guess,sub} files are out of date, and are not updated during
the build.  If possible, please do not update these files directly,
but build-depend on autotools-dev instead, and use the tools provided
by autotools-dev to update these files.

  - For dh, call dh --with autotools_dev (yes, underscore).

  - For other rules files, call dh_autotools-dev_updateconfig before
calling configure (in the build or configure target), and call
dh_autotools-dev_restoreconfig before calling dh_clean in the clean
target.

After the build on any architecture, and before a clean, a grep for
aarch64 in the config.sub file(s) should print some lines.

The full build log can be found at:
http://people.debian.org/~doko/logs/arm64-20131023/logs/buildlog_ubuntu-trusty-arm64.libbinio_1.4+dfsg1-1_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.

Please note that these build were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.

[...]
Toolchain package versions: libc6-dev_2.17-93ubuntu4 make_3.81-8.2ubuntu3 
dpkg-dev_1.16.12ubuntu1 gcc-4.8_4.8.1-10ubuntu8 g++-4.8_4.8.1-10ubuntu8 
binutils_2.23.52.20130913-0ubuntu1 libstdc++-4.8-dev_4.8.1-10ubuntu8 
libstdc++6_4.8.1-10ubuntu8
--
gpgv: Signature made Thu Dec 20 00:42:43 2012 UTC using DSA key ID 5B713DF0
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on ./libbinio_1.4+dfsg1-1.dsc
dpkg-source: info: extracting libbinio in libbinio-1.4+dfsg1
dpkg-source: info: unpacking libbinio_1.4+dfsg1.orig.tar.gz
dpkg-source: info: applying libbinio_1.4+dfsg1-1.diff.gz
dpkg-buildpackage: source package libbinio
dpkg-buildpackage: source version 1.4+dfsg1-1
 dpkg-source --before-build libbinio-1.4+dfsg1
dpkg-buildpackage: host architecture arm64
 /usr/bin/fakeroot debian/rules clean
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null pop -a -R || test $? = 2
No patch removed
rm -rf .pc debian/stamp-patched
dh_testdir
dh_testroot
rm -f build-stamp configure-stamp
[ ! -f Makefile ] || /usr/bin/make distclean
dh_clean
dpkg-buildpackage: warning: debian/rules must be updated to support the 
'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be 
missing)
 debian/rules build
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null push -a || test $? = 2
Applying patch 00_fix_gcc4.4_FTBFS.diff
patching file src/binwrap.cpp

Applying patch removed_gfdl_doc.diff
patching file configure
patching file Makefile.in

Now at patch removed_gfdl_doc.diff
touch debian/stamp-patched
dh_testdir
./configure \
--host=aarch64-linux-gnu --build=aarch64-linux-gnu \
--prefix=/usr --infodir=\${prefix}/share/info \
CFLAGS="-g -O2 -Wformat -Werror=format-security" 
CPPFLAGS="-D_FORTIFY_SOURCE=2" CXXFLAGS="-g -O2 -Wformat 
-Werror=format-security" FFLAGS="-g -O2" LDFLAGS="-Wl,-Bsymbolic-functions 
-Wl,-z,relro" 
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... Invalid configuration `aarch64-linux-gnu': 
machine `aarch64' not recognized
configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed
make: *** [configure-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1vz7an-00033p...@ravel.debian.org

Bug#727448: libxcrypt: update config.{sub,guess} for the AArch64 port

2013-10-23 Thread Matthias Klose 
Package: src:libxcrypt
Version: 1:2.4-3
Severity: normal
User: debian-...@lists.debian.org
Usertags: arm64

The package fails to build on arm64 (aarch64-linux-gnu), because the
config.{guess,sub} files are out of date, and are not updated during
the build.  If possible, please do not update these files directly,
but build-depend on autotools-dev instead, and use the tools provided
by autotools-dev to update these files.

  - For dh, call dh --with autotools_dev (yes, underscore).

  - For other rules files, call dh_autotools-dev_updateconfig before
calling configure (in the build or configure target), and call
dh_autotools-dev_restoreconfig before calling dh_clean in the clean
target.

After the build on any architecture, and before a clean, a grep for
aarch64 in the config.sub file(s) should print some lines.

The full build log can be found at:
http://people.debian.org/~doko/logs/arm64-20131023/logs/buildlog_ubuntu-trusty-arm64.libxcrypt_1:2.4-3_FAILEDTOBUILD.txt
The last lines of the build log are at the end of this report.

Please note that these build were done in an Ubuntu development,
environment there may be a few false positives in these bug reports.

[...]
dpkg-source: info: unpacking libxcrypt_2.4.orig.tar.gz
dpkg-source: info: applying libxcrypt_2.4-3.diff.gz
dpkg-source: info: upstream files that have been modified: 
 libxcrypt-2.4/config.guess
 libxcrypt-2.4/config.sub
dpkg-buildpackage: source package libxcrypt
dpkg-buildpackage: source version 1:2.4-3
 dpkg-source --before-build libxcrypt-2.4
dpkg-buildpackage: host architecture arm64
 /usr/bin/fakeroot debian/rules clean
dh_testdir
dh_testroot
dh_quilt_unpatch
No patch removed
dh_quilt_unpatch: Compatibility levels before 5 are deprecated (level 4 in use)
rm -f build-stamp 
# Add here commands to clean up after the build process.
/usr/bin/make distclean
make[1]: Entering directory `/build/buildd/libxcrypt-2.4'
make[1]: *** No rule to make target `distclean'.  Stop.
make[1]: Leaving directory `/build/buildd/libxcrypt-2.4'
make: [clean] Error 2 (ignored)
dh_clean 
dh_clean: Compatibility levels before 5 are deprecated (level 4 in use)
dpkg-buildpackage: warning: debian/rules must be updated to support the 
'build-arch' and 'build-indep' targets (at least 'build-arch' seems to be 
missing)
 debian/rules build
dh_testdir
# Add here commands to configure the package.
CFLAGS="-Wall -g -O2" ./configure --host=aarch64-linux-gnu 
--build=aarch64-linux-gnu --prefix=/usr --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for aarch64-linux-gnu-gcc... aarch64-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether aarch64-linux-gnu-gcc accepts -g... yes
checking for aarch64-linux-gnu-gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of aarch64-linux-gnu-gcc... gcc3
checking whether make sets $(MAKE)... (cached) yes
checking build system type... Invalid configuration `aarch64-linux-gnu': 
machine `aarch64' not recognized
configure: error: /bin/bash ./config.sub aarch64-linux-gnu failed
make: *** [config.status] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1vz7bh-0003jr...@ravel.debian.org

Bug#727177: Upgrade of libnss-ldap to 265-1 causes important binaries to segfault

2013-10-23 Thread Damián Cinich 
Same here. I can not login to the system in any way, I am trying to
boot from a pen drive to downgrade libnss-ldap.


-- 
To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAEskrvSkoX=aBwgUeakgPtyNZOfewZVphBFXSt=dmirevej...@mail.gmail.com