Bug#841431: apt-cacher-ng: FTBFS on mips/mipsel: undefined reference to '__atomic_fetch_add_8'

[Eduard Bloch]

Control: retitle 841431 FTBFS on m68k/powerpcspe
Control: reopen 841431

I wanted to extend this patch to a couple of other architectures and
failed to commit the change prior to release :-(

To be fixed in an upstream release soon.

Regards,
Eduard.

Processed: Re: Bug#841431: apt-cacher-ng: FTBFS on mips/mipsel: undefined reference to '__atomic_fetch_add_8'

[Debian Bug Tracking System]

Processing control commands:

> retitle 841431 FTBFS on m68k/powerpcspe
Bug #841431 {Done: Eduard Bloch } [apt-cacher-ng] 
apt-cacher-ng: FTBFS on mips/mipsel: undefined reference to 
'__atomic_fetch_add_8'
Changed Bug title to 'FTBFS on m68k/powerpcspe' from 'apt-cacher-ng: FTBFS on 
mips/mipsel: undefined reference to '__atomic_fetch_add_8''.
> reopen 841431
Bug #841431 {Done: Eduard Bloch } [apt-cacher-ng] FTBFS on 
m68k/powerpcspe
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions apt-cacher-ng/1-2.

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

Processed: severity of 839938 is normal

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 839938 normal
Bug #839938 [network-manager-openvpn] Doesnt connect to server with this 
version (1.2.6-2, does with 1.2.4-1)
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#841469: marked as done (libopendbx: build-depends on firebird2.5-dev, which is no longer available)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 04:26:16 +
with message-id 
and subject line Bug#841469: fixed in libopendbx 1.4.6-11
has caused the Debian Bug report #841469,
regarding libopendbx: build-depends on firebird2.5-dev, which is no longer 
available
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libopendbx
Version: 1.4.6-10
Severity: serious

Your package build-depends on firebird2.5-dev, but that is no longer
available as firebird is at version 3.0. Thus your package is currently
unbuildable.

Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: libopendbx
Source-Version: 1.4.6-11

We believe that the bug you reported is fixed in the latest version of
libopendbx, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated libopendbx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Oct 2016 22:13:04 -0400
Source: libopendbx
Binary: libopendbx1 libopendbx1-dev libopendbx1-firebird libopendbx1-mssql 
libopendbx1-mysql libopendbx1-odbc libopendbx1-pgsql libopendbx1-sqlite 
libopendbx1-sqlite3 libopendbx1-sybase opendbx-utils opendbx-doc
Architecture: source
Version: 1.4.6-11
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenDBX Maintainers 

Changed-By: Scott Kitterman 
Description:
 libopendbx1 - Lightweight database access abstraction layer
 libopendbx1-dev - Lightweight database access abstraction layer (dev)
 libopendbx1-firebird - Firebird backend for OpenDBX
 libopendbx1-mssql - MSSQL backend for OpenDBX
 libopendbx1-mysql - MySQL backend for OpenDBX
 libopendbx1-odbc - ODBC backend for OpenDBX
 libopendbx1-pgsql - PostgreSQL backend for OpenDBX
 libopendbx1-sqlite - SQLite backend for OpenDBX
 libopendbx1-sqlite3 - SQLite3 backend for OpenDBX
 libopendbx1-sybase - Sybase ctlib backend for OpenDBX
 opendbx-doc - Opendbx documentation
 opendbx-utils - Utility applications using libopendbx
Closes: 841469
Changes:
 libopendbx (1.4.6-11) unstable; urgency=medium
 .
   * Wrap and sort
   * Build depend on firebird-dev instead of firebird2.5-dev (Closes: #841469)
   * Build depend on default-libmysqlclient-dev insted of libmysqlclient-dev
Checksums-Sha1:
 3a4bb25f6650e8f9fbc562a67e7277530292d7b1 3050 libopendbx_1.4.6-11.dsc
 e40bda7aaf5b84496053a896a181f37839d92f05 77332 
libopendbx_1.4.6-11.debian.tar.xz
Checksums-Sha256:
 17d0a99bab4b4a11a145c9cdb94b0facf75357f1937a3f9574264c89f1e5b388 3050 
libopendbx_1.4.6-11.dsc
 cc6994a8132c01eb7fe1a3acb314d6d352de568532750886ce5feb5f47dea999 77332 
libopendbx_1.4.6-11.debian.tar.xz
Files:
 667e0a500cf86c2ad74683f31592067e 3050 libs optional libopendbx_1.4.6-11.dsc
 84c4622caa027f0dec14c280ac30795e 77332 libs optional 
libopendbx_1.4.6-11.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYCXzyAAoJEHjX3vua1Zrx1PEP/0fyEaLFuJ8RMWbdTuley6cx
gK/Km040xgVWkQfh9Qep6oE37L4JLGlPkfyeUhXwDPvcdzkMlLINQq0sw7ZM0X2o
2KK3EAHw26AuchEK/hXRo1laxL2wYTimiAxqLDza1f0YSsH1jEM+fGTMhtD//aV/
0SfxyLWgOYoWHbJPt0nGYn4XdkjM7gE0yMCDwjh156kHBW2cL5iwWdiltpIU7fos
s4YhC2QVU5rHHcP5QOe4qHyPmIIua65xlo4bQ2NyDzoYae6A5yKQ2MrL0crzJLDe
FN8MmfbuLitJATMeRCM22NM7gsUSuCt+5/EpIMdcGpQ2Iu6N9DgFff6GYdAwlZLq
AaOepx/69YnMEuGJa7n39Hxic9wo/vSt8UnQ8GqDuW/Nwb/tzYOJYApNth5xOLac
n4A+4M/IYLL8NMM1fWbNu0F4P/XGMQATErn06cKFo5iD50JVbWLsiINmG8ogKaOg
3p/sOTL33UJmD+4XDFe4uk5tZhTIVz5rPYWIObu9+0jF3xrCFHoK4XBqf7T9nJgO
IAdNPBtKU8RJWIc+a7KLElh5hKamUunUJA1Jk5/iXxfdqo3U7mBV1CXMCpWJaSWF
3fMvDgTYqv9pz/E7lOLBFheSfLmFhl2mZ7xasrCAM9Z3q4Aa7wxFvXnVN2y7t+Yy
a6M3PJBkPaLvAo

Bug#841313: latex-cjk-japanese-wadalab: FTBFS: Create .afm and .pfa fonts from dg. \n Segmentation fault (core dumped)

[韓達耐]

Hi Hilmar

Thanks for the trace. I'm traveling now so I will need to test this.  At
home I only have access to amd64, but I'll test it on other architectures
too.
My guess is a behavioural change; the compiler warnings have been around
for quite a while and it's time to revisit some of the variable types.

Cheers

On 19 Oct 2016 22:01, "Hilmar Preuße"  wrote:

> Am 19.10.2016 um 17:20 schrieb Danai SAE-HAN (韓達耐):
>
> Hi all,
>
> It looks like a problem with the wftodm binary.  This is an important piece
>> in the creation of the fonts.
>> I will only have access to my PC next week Thursday (27 October 2016) to
>> check the C source code and replicate it on amd64.  Please bear with me
>> for
>> a while.
>>
>> I *think* I can reproduce the bug.
>
> Here is the gdb backtrace:
>
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  strlen () at ../sysdeps/x86_64/strlen.S:106
> 106 ../sysdeps/x86_64/strlen.S: No such file or directory.
> (gdb) bt
> #0  strlen () at ../sysdeps/x86_64/strlen.S:106
> #1  0x2ba08dfdbda3 in _IO_vfprintf_internal (s=s@entry=0x7ffd926eb3f0,
> format=, format@entry=0x5643d866b22e "/StdHW [ %s ]
> |-\n",
> ap=ap@entry=0x7ffd926eb518) at vfprintf.c:1637
> #2  0x2ba08dffcacb in __IO_vsprintf (
> string=0x7ffd926eb620 "/StdHW [ re{16 16} |-\n",
> format=0x5643d866b22e "/StdHW [ %s ] |-\n", args=args@entry
> =0x7ffd926eb518)
> at iovsprintf.c:42
> #3  0x2ba08dfe2327 in __sprintf (s=, format= out>)
> at sprintf.c:32
> #4  0x5643d866a8e2 in e_printf (form=, i0= out>,
> i1=, i2=, i3=,
> i4=, i5=1936353124, i6=-1838284703, i7=0,
> i8=-1909291776,
> i9=0) at wftodm.c:306
> #5  0x5643d866aa77 in output_pfa (file=1) at wftodm.c:255
> #6  0x5643d8669d3a in main (ac=, ag=)
> at wftodm.c:158
>
> And here is the function e_printf() in question:
>
> e_printf(form,i0,i1,i2,i3,i4,i5,i6,i7,i8,i9)
> char *form;
> {
>   int len,i;
>   unsigned char buf[4096];
>   sprintf(buf,form,i0,i1,i2,i3,i4,i5,i6,i7,i8,i9);
>   len=strlen(buf);
>   for(i=0;i e_putchar(buf[i]);
> }
>
> In line 255 (function output_pfa) it is called like this
>
> e_printf("/StdHW [ %s ] |-\n",StdHW);
>
> I /guess/ there is a thinks in string processing. Sorry, I don't have
> enough knowledge in C to help here. Does that ring anywhere a bell on your
> side? Is the problem reproducible e.g. in i386?
>
> Hilmar
> --
> http://www.hilmar-preusse.de.vu/   #206401 http://counter.li.org
>

Bug#841453: marked as done (linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 04:26:45 +
with message-id 
and subject line Bug#841453: fixed in linux-signed 2.8
has caused the Debian Bug report #841453,
regarding linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed 
to remove '/lib/modules/4.7.0-1-amd64': Directory not empty
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: linux-image-4.7.0-1-amd64
Version: 4.7.6-1
Severity: serious

I you have linux-image-4.7.0-1-amd64 installed, then upgrading to 
linux-image-4.7.0-1-amd64-unsigned fails:


# apt-get install linux-image-4.7.0-1-amd64-unsigned
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  linux-doc-4.7 (4.7.8-1)
  debian-kernel-handbook (1.0.17)
  grub-pc (2.02~beta3-1)
  | grub-efi-amd64 (2.02~beta3-1)
  | extlinux (3:6.03+dfsg-14)
Recommended packages:
  firmware-linux-free (3.4)
  irqbalance (1.1.0-2)
The following packages will be REMOVED:
  linux-image-4.7.0-1-amd64* (4.7.6-1)
The following NEW packages will be installed:
  linux-image-4.7.0-1-amd64-unsigned (4.7.8-1)
0 upgraded, 1 newly installed, 1 to remove and 35 not upgraded.
Need to get 36.8 MB of archives.
After this operation, 1709 kB disk space will be freed.
Do you want to continue? [Y/n]
Get:1 http://ftp.debian.org/debian unstable/main amd64 
linux-image-4.7.0-1-amd64-unsigned amd64 4.7.8-1 [36.8 MB]
Fetched 36.8 MB in 1s (28.7 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 14226 files and directories currently installed.)
Removing linux-image-4.7.0-1-amd64 (4.7.6-1) ...
W: Last kernel image has been removed, so removing the default symlinks
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-4.7.0-1-amd64
Selecting previously unselected package linux-image-4.7.0-1-amd64-unsigned.
(Reading database ... 10177 files and directories currently installed.)
Preparing to unpack .../linux-image-4.7.0-1-amd64-unsigned_4.7.8-1_amd64.deb ...
Unpacking linux-image-4.7.0-1-amd64-unsigned (4.7.8-1) ...
Setting up linux-image-4.7.0-1-amd64-unsigned (4.7.8-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.7.0-1-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-4.7.0-1-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-4.7.0-1-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.7.0-1-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.7.0-1-amd64
cp: cannot stat '/etc/modprobe.d/*': No such file or directory
(Reading database ... 14224 files and directories currently installed.)
Removing linux-image-4.7.0-1-amd64 (4.7.6-1) ...
Purging configuration files for linux-image-4.7.0-1-amd64 (4.7.6-1) ...
W: Last kernel image has been removed, so removing the default symlinks
rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty
dpkg: error processing package linux-image-4.7.0-1-amd64 (--purge):
subprocess installed post-removal script returned error exit status 1
Errors were encountered while processing:
linux-image-4.7.0-1-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages linux-image-4.7.0-1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.125
ii  kmod22-1.1
ii  linux-base  4.5

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: linux-signed
Source-Version: 2.8

We believe that the bug you reported is fixed in the latest version of
linux-signed, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux-signed package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-

Bug#841373: mv: cannot stat 'unpackchrome/opt/google/chrome/PepperFlash/libpepflashplayer.so': No such file or directory

[Trent W. Buck]

This is the same bug at Ubuntu; it has more analysis:

  
https://bugs.launchpad.net/ubuntu/+source/pepperflashplugin-nonfree/+bug/1632870

In short:

  * Google Chrome 54+ does not bundle libpepflashplayer.so.

  * pepperflashplugin-nonfree will have to get it from somewhere else;
either adobe.com directly, or Google's "redirector.gvtl.com" thing.

It looks like Ubuntu don't care about pepperflashplugin-nonfree,
because they recommend adobe-flashplugin from canonical-partners.

  https://wiki.ubuntu.com/Chromium/Getting-Flash

Debian has no equivalent.

Bug#841286: marked as done (jison depends on contrib packages (node-ebnf-parser, node-cjson))

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 06:57:26 +0530
with message-id <00d186d8-31e1-4c12-8384-4ab7c51ab...@onenetbeyond.org>
and subject line Re: jison depends on contrib packages (node-ebnf-parser, 
node-cjson)
has caused the Debian Bug report #841286,
regarding jison depends on contrib packages (node-ebnf-parser, node-cjson)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: jison
Version: 0.4.17+dfsg-3
Severity: serious
Justification: Policy §2.2.1

This package is in main, but it depends on node-ebnf-parser and node-cjson, 
which are both in contrib.


--
Jakub Wilk
--- End Message ---
--- Begin Message ---
On Thu, 20 Oct 2016 17:36:03 +0530 Pirate Praveen  wrote:
> These were uploaded in contrib because they were built using jison from
> npm (bootstrapping circular dependency). Now new versions of both these
> libs are uploaded to main. Once they are accepted into main, I'll close
> this bug.
> 

Both are in main now, closing
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message ---

Bug#841474: afl: FTBFS on armhf (illegal instruction on test-instr.c)

[Daniel Stender]

Package: afl
Version: 2.34b-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

>From 2.30b-1 onwards (the first package which was tried to build against 
>llvm-toolchain
> 3.7 on this arch), AFL build breaks with "illegal instruction" trying to 
> compile
test-instr.c with afl-clang-fast, now trying to build with clang 3.9 [1]:


[*] Testing the CC wrapper and instrumentation output...
unset AFL_USE_ASAN AFL_USE_MSAN AFL_INST_RATIO; AFL_QUIET=1 AFL_PATH=. 
AFL_CC=clang-3.9
../afl-clang-fast -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fPIE 
-fstack-protector-strong
-Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -g -Wno-pointer-sign
-DAFL_PATH=\"/usr/lib/afl\" -DBIN_PATH=\"/usr/bin\" -DVERSION=\"2.34b\"  
../test-instr.c -o
test-instr -fPIE -pie -Wl,-z,relro -Wl,-z,now
Illegal instruction


Julien Puydt has reported something similar for the flint package:
https://bugs.debian.org/798111 (Illegal instruction after compiling some code)

Strangely, the package builds fine in the porterbox and with a 
qemu-bootstrapped local
sbuild [2].

Thanks for any input (if this could be worked around in the AFL package),
I'll try to seek what's causing this in the build toolchain.
DS

[1] 
https://buildd.debian.org/status/fetch.php?pkg=afl&arch=armhf&ver=2.34b-2&stamp=1474836143

[2] 
http://www.danielstender.com/buildlogs/afl_2.34b-2_armhf-2016-10-20T23:40:16Z.build

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

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages afl depends on:
ii  build-essential  12.2
ii  libc62.24-3

Versions of packages afl recommends:
pn  afl-clang  
ii  afl-doc2.34b-2

Versions of packages afl suggests:
ii  gnuplot  5.0.4+dfsg1-3

-- no debconf information

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[Konstantin Demin]

2016-10-21 1:49 GMT+03:00 Ben Hutchings :
> It's a bug when a compiler fails to compile valid code.
>
> Ben.
>
> --
> Ben Hutchings
> Never put off till tomorrow what you can avoid all together.

Dear Ben, there are no actual bug in compiler, just a caveat to work with it.

Some time ago i had experience to build fully hardened nginx build,
and I was forced to build shared libraries with -fPIC but not -fPIE
due to linker errors.

Solution was to separate build to executable only and shared-libraries only;
this is semi-true: executable is successfully linked with -fPIC flag,
but it's not used in packaging because of executable already built with -fPIE.

This bug report is just another round of game with compiler/linker flags.
In my turn, I would rather define protective flags to provide backward
and forward compatibility.

-- 
SY,
Konstantin Demin
--- a/debian/rules.real
+++ b/debian/rules.real
@@ -168,6 +168,7 @@ else
 	echo 'override CROSS_COMPILE = $$(DEB_HOST_GNU_TYPE)-' >> '$(DIR)/.kernelvariables'
 	echo 'endif' >> '$(DIR)/.kernelvariables'
 endif
+	echo 'KCFLAGS += -fno-PIC -fno-PIE' >> '$(DIR)/.kernelvariables'
 ifdef CFLAGS_KERNEL
 	echo 'CFLAGS_KERNEL += $(CFLAGS_KERNEL)' >> '$(DIR)/.kernelvariables'
 	echo 'CFLAGS_MODULE += $(CFLAGS_KERNEL)' >> '$(DIR)/.kernelvariables'
 endif

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[S. R. Wright]

I agree.  When the version changes from 6.2.0-6 to 6.2.0-7,  only bug 
fixes should be included,  not changes in functionality.  In this case 
setting enable-default-pie essentially broke backwards compatibility.  
Kernel code that built in -6 failed to build in -7.  That, I agree,  
should be considered a bug,  and the change should be rolled back.


-- sRw

On 10/20/2016 05:49 PM, Ben Hutchings wrote:

On Fri, 2016-10-21 at 01:21 +0300, Konstantin Demin wrote:

It's not a GCC bug but kind of new feature.

It's a bug when a compiler fails to compile valid code.

Ben.


Take a look at this changelog entry:
  gcc-6 (6.2.0-7) unstable; urgency=medium

[ Matthias Klose ]
* Configure with --enable-default-pie and pass -z now when pie is enabled;
  on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x.
  Closes: #835148.

Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in
beginning of CFLAGS to build kernel successfully.

I'm currently looking for correct way to do this trick.

Bug#841471: fim: FTBFS on several architectures: default_font_byte_array.h:349:1: error: narrowing conversion of '905969664' from 'int' to 'unsigned char' inside { } [-Wnarrowing]

[Emilio Pozuelo Monfort]

Package: fim
Version: 0.5~rc2-1
Severity: serious

Your package failed to build on several architectures with this errors:

g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/libpng16 -I/usr/include -I/usr/include/SDL -D_GNU_SOURCE=1 
-D_REENTRANT -c -o FontServer.o FontServer.cpp
In file included from FontServer.cpp:184:0:
default_font_byte_array.h: In static member function 'static fim::fs_font* 
fim::FontServer::fs_consolefont(const fim_char_t**)':
default_font_byte_array.h:349:1: error: narrowing conversion of '905969664' 
from 'int' to 'unsigned char' inside { } [-Wnarrowing]
 };
 ^
default_font_byte_array.h:349:1: error: narrowing conversion of '67108864' from 
'int' to 'unsigned char' inside { } [-Wnarrowing]
default_font_byte_array.h:349:1: error: narrowing conversion of '33554432' from 
'int' to 'unsigned char' inside { } [-Wnarrowing]
default_font_byte_array.h:349:1: error: narrowing conversion of '268435456' 
from 'int' to 'unsigned char' inside { } [-Wnarrowing]
default_font_byte_array.h:349:1: error: narrowing conversion of '2852126720u' 
from 'unsigned int' to 'unsigned char' inside { } [-Wnarrowing]
[...]

This seems to be happening on big-endian architectures, so may be an
endianness issue.

Full logs at:

https://buildd.debian.org/status/package.php?p=fim

Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#841469: libopendbx: build-depends on firebird2.5-dev, which is no longer available

[Emilio Pozuelo Monfort]

Source: libopendbx
Version: 1.4.6-10
Severity: serious

Your package build-depends on firebird2.5-dev, but that is no longer
available as firebird is at version 3.0. Thus your package is currently
unbuildable.

Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#841470: witty: build-depends on firebird2.5-dev, which is no longer available

[Emilio Pozuelo Monfort]

Source: witty
Version: 3.3.5+dfsg-1.1
Severity: serious

Your package build-depends on firebird2.5-dev, but that is no longer
available as firebird is at version 3.0. Thus your package is currently
unbuildable.

Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#841288: marked as done (tigervnc-common: amd64 has dep libgnutls-deb0-28)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 22:55:15 +
with message-id 
and subject line Bug#841288: fixed in tigervnc 1.6.0+dfsg-4
has caused the Debian Bug report #841288,
regarding tigervnc-common: amd64 has dep libgnutls-deb0-28
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tigervnc-common
Version: 1.6.0+dfsg-3
Severity: normal

tigervnc-common needs libgnutls-deb0-28 on amd64 architecture.
I think this dep should be for arm64.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (980, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: tigervnc
Source-Version: 1.6.0+dfsg-4

We believe that the bug you reported is fixed in the latest version of
tigervnc, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ola Lundqvist  (supplier of updated tigervnc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Oct 2016 22:39:36 +0200
Source: tigervnc
Binary: tigervnc-common tigervnc-scraping-server tigervnc-standalone-server 
tigervnc-xorg-extension tigervnc-viewer
Architecture: source
Version: 1.6.0+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: TigerVNC Packaging Team 
Changed-By: Ola Lundqvist 
Description:
 tigervnc-common - Virtual network computing; Common software needed by servers
 tigervnc-scraping-server - VNC server uses screen scraping of an already 
running X server
 tigervnc-standalone-server - Standalone VNC server
 tigervnc-viewer - Virtual network computing client software for X
 tigervnc-xorg-extension - X server vnc extension
Closes: 841288
Changes:
 tigervnc (1.6.0+dfsg-4) unstable; urgency=medium
 .
   * Re-build to solve library dependency problem. Closes: #841288.
Checksums-Sha1:
 2fedc2c1a09c44842e219371900afc508174e00a 4425 tigervnc_1.6.0+dfsg-4.dsc
 2a0bcef78ba8acdaf2d907aa4933e18014b998d0 37432 
tigervnc_1.6.0+dfsg-4.debian.tar.xz
Checksums-Sha256:
 884b2465e6db4ebbc8f9088173bcf9b7a18a8a11ac3a3e6aba73e24223308517 4425 
tigervnc_1.6.0+dfsg-4.dsc
 24a520bc41ac77303008fc37d97f11a53e753587c0107ed7c8df4a5715992803 37432 
tigervnc_1.6.0+dfsg-4.debian.tar.xz
Files:
 798c52f11b4bbb9be2ece41bec76d327 4425 x11 optional tigervnc_1.6.0+dfsg-4.dsc
 a08c69ecc781619ae12335cf924d99a7 37432 x11 optional 
tigervnc_1.6.0+dfsg-4.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYCS1eAAoJEF6Q3PqUJodvBq8P/jcky5Q3tdb7CtjU3tRqHULL
MyBQC8IXzW0tvB1ZkTV24m1JpGtBPJ8kU8JeKQYG4OshnZ3nrWls0rsCwg5ZCX0p
UhkzJUt/7RNrdy8T+IBUY6AEykJ9Dago7vNlWGrdsfiVbMsKPlPc+VdBo63tRhG9
0EVidm1nxc92Xzz58W/xCN186gIRUEhd1iEQxkfrcOHKgTI0BidnYoIbS5ICsvrn
WGi6zedq8rJKeAHsdoIXfRE5hSMThGAwkObAe5eG34GZyOv5hogna9n6SGxUZh9e
ugw/DSgD3TqWMKuxn7RBwDP2UcIVbX/F7E7LmAfEfyrWx5s3hA2HKFsqnMSETKnu
deii1l6g2rqk7fbFEs7nEZ6Vew3RufqnKwBQHJnQxaDn00cKDLT9G1KYrx3/GVBC
9fEeiLSALg1BdxXioX6MXAbMQYys8CVs80wbJ2pGw6Gr+k/RsmpAIU2XTxOf/vnu
61Wc1+UROh6+ouQp0mQOtXKdV0bDlnP2Eyp/Ao5PIY4a7NMk2je92Eh/5CivSUtg
wfKWaNsMg6WkjG6C2rXsM9s6WtKHULxkTOziZrzWjh0AxU3eort6akA1kpcO3uFA
cuKvDGS0QFhj/pByTOEDj/MAyxUBBCy1msSIM/lxS72vEb3rxCWvdIveNZjt/Uow
0rkWFJFyF3TZ56aBzHjP
=DLIx
-END PGP SIGNATURE End Message ---

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[Ben Hutchings]

On Fri, 2016-10-21 at 01:21 +0300, Konstantin Demin wrote:
> It's not a GCC bug but kind of new feature.

It's a bug when a compiler fails to compile valid code.

Ben.

> Take a look at this changelog entry:
>  gcc-6 (6.2.0-7) unstable; urgency=medium
> 
>    [ Matthias Klose ]
>    * Configure with --enable-default-pie and pass -z now when pie is enabled;
>  on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x.
>  Closes: #835148.
> 
> Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in
> beginning of CFLAGS to build kernel successfully.
> 
> I'm currently looking for correct way to do this trick.
> 
> 
-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.



signature.asc
Description: This is a digitally signed message part

Bug#841098: not fixed in rygel 0.32.1-1

[Santiago Vila]

On Thu, Oct 20, 2016 at 10:14:11PM +0200, Andreas Henriksson wrote:

> The above mentioned upload was done as a source-only upload.
> It built successfully not only in my local environment but also on *all*
> architectures (and thus on atleast one buildd for each architecture).
> 
> This is obviously a problem in your environment.

No, I think it's not, because it also happened in the official
autobuilders several times. For example:

https://buildd.debian.org/status/fetch.php?pkg=rygel&arch=ppc64el&ver=0.32.0-2&stamp=1475601506

Quote:

PASS: rygel-searchable-container-test
PASS: rygel-object-creator-test
PASS: rygel-database-test
../build-aux/test-driver: line 107: 17241 Aborted "$@" > 
$log_file 2>&1
FAIL: rygel-media-engine-test
PASS: rygel-playbin-renderer-test
PASS: rygel-environment-test

It's more like a bug which happens randomly (with low probability) and
it's still unfixed, but definitely not a problem in my environment.

Thanks.

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

[Konstantin Demin]

It's not a GCC bug but kind of new feature.

Take a look at this changelog entry:
 gcc-6 (6.2.0-7) unstable; urgency=medium

   [ Matthias Klose ]
   * Configure with --enable-default-pie and pass -z now when pie is enabled;
 on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x.
 Closes: #835148.

Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in
beginning of CFLAGS to build kernel successfully.

I'm currently looking for correct way to do this trick.

-- 
SY,
Konstantin Demin

Processed: Re: Bug#841459: bgpdump: FTBFS with bash as /bin/sh

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 841459 pending
Bug #841459 [src:bgpdump] bgpdump: FTBFS with bash as /bin/sh
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841459: bgpdump: FTBFS with bash as /bin/sh

[Christoph Biedl]

tags 841459 pending
thanks

Chris Lamb wrote...

> bgpdump fails to build from source in unstable/amd64 when 
> /bin/sh is set to bash. It looks like the autoreconfing is
> generating an invalid ./configure script:

Thanks for the catch. The actual problem is using m4_esyscmd which
does not remove trailing newlines, resulting the trailing dot to
dropped into the next line, better use m4_esyscmd_s. Lesson learned,
upload based on a new upstream version will follow soon.

Regards,

Christoph


signature.asc
Description: Digital signature

Bug#841420: --enable-default-pie breaks kernel builds

[Bálint Réczey]

Control: tags -1 - patch

2016-10-20 18:48 GMT+02:00 Sven Joachim :
> On 2016-10-20 17:54 +0200, Bálint Réczey wrote:
>
>> Control: reassign -1 linux 4.7.8-1
>> Control: severity -1 serious
>> Control: tags -1 patch
>>
>> Hi David,
>>
>> 2016-10-20 14:02 GMT+02:00 David Weinehall :
>>> Package: gcc-6
>>> Severity: important
>>> Version: 6.2.0-7
>>>
>>> --enable-default-pie (first enabled in gcc-6 6.2.0-7) causes kernel
>>> builds to fail.  If the kernel is configured with the stack protector
>>> enabled it'll fail with a rather unhelpful error message claiming
>>> that the compiler doesn't support -fstack-protector,
>>> but the problem is in fact caused by:
>>>
>>> kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
>>>
>>> (The kernel is built with -mcmodel=kernel)
>>>
>>> I think it's fair to say that the kernel is kind of an important piece
>>> of software and that it's imperative that we don't break kernel builds...
>>
>> The kernel is very important indeed and it did break in our build test.
>> I'm sorry, somehow I missed filing bug for the linux package, just for
>> user-mode-linux.
>> The following patch fixes the FTBFS:
>>
>> --- linux-4.7.8/debian/rules.d/Makefile.inc
>> +++ linux-4.7.8/debian/rules.d/Makefile.inc
>> @@ -5,7 +5,8 @@
>>
>>  SHELL = /bin/sh -e
>>
>> -CC = $(CROSS_COMPILE)gcc
>> +CC = $(CROSS_COMPILE)gcc -no-pie
>> +LD = $(CROSS_COMPILE)ld -no-pie
>>  CXX = $(CROSS_COMPILE)g++
>>  CFLAGS := $(shell dpkg-buildflags --get CFLAGS) -Wall
>>  CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS) \
>>
>> Maybe the ld part is obsolete, I have not checked that.
>
> That patch might work for the Debian package, but has anybody contacted
> the upstream kernel developers about that?  At least the 4.8.3 vanilla
> kernel fails in the same way, I haven't tested 4.9-rc1 yet.

Fixing it upstream would certainly be better. I also haven't booted
the built image,
thus please use this patch only as inspiration. :-)

Cheers,
Balint

>
> FWIW, this issue has been discussed in Ubuntu for six months(!), see
> https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982.
>
> Cheers,
>Sven

Processed: Re: Bug#841420: --enable-default-pie breaks kernel builds

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #841420 [linux] --enable-default-pie breaks kernel builds
Bug #841368 [linux] gcc-6 6.2.0-7 breaks kernel build if stack protection is 
enabled
Removed tag(s) patch.
Removed tag(s) patch.

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

Processed: reassign 841453 to src:linux-signed

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 841453 src:linux-signed 2.7
Bug #841453 [linux-image-4.7.0-1-amd64] linux-image-4.7.0-1-amd64: can't 
upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': 
Directory not empty
Bug reassigned from package 'linux-image-4.7.0-1-amd64' to 'src:linux-signed'.
No longer marked as found in versions linux-signed/2.7.
Ignoring request to alter fixed versions of bug #841453 to the same values 
previously set
Bug #841453 [src:linux-signed] linux-image-4.7.0-1-amd64: can't upgrade to 
-unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not 
empty
Marked as found in versions linux-signed/2.7.
> thanks
Stopping processing here.

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

Bug#841288: [Pkg-tigervnc-devel] Bug#841288: Bug#841288: tigervnc-common: amd64 has dep libgnutls-deb0-28

[Ola Lundqvist]

Hi all

I have made a source-only upload. This way the problem shall be solved.

// Ola

On 20 October 2016 at 08:49, Ola Lundqvist  wrote:
> Hi
>
> I'm the one to blame. I built it on stable.
>
> The problem is easy to solve by stepping the revision and building on
> unstable.
>
> I can not do that today but hopefully later this week.
>
> // Ola
>
> On 19 October 2016 at 23:26, Axel Beckert  wrote:
>>
>> Control: severity -1 serious
>>
>> Hi,
>>
>> Jacek Szafarkiewicz wrote:
>> > tigervnc-common needs libgnutls-deb0-28 on amd64 architecture.
>> > I think this dep should be for arm64.
>>
>> Nope, the amd64 package has been built on Debian Stable instead of
>> Debian Unstable and then uploaded to Debian Unstable anyways.
>>
>> See https://packages.debian.org/search?keywords=libgnutls-deb0-28
>>
>> (arm64 from debports doesn't count anymore, it's already in Debian
>> proper for multiple years.)
>>
>> Nevertheless, this is definitely a serious issue and tigervnc on
>> amd64 needs to be rebuilt in a clean chroot, e.g. by requesting a
>> BinNMU for it. (Which the maintainer of the package should do.
>>
>> Without that, the package won't migrate to testing.
>>
>> Regards, Axel
>> --
>>  ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
>> : :' :  |  Debian Developer, ftp.ch.debian.org Admin
>> `. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
>>   `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
>>
>> ___
>> Pkg-tigervnc-devel mailing list
>> pkg-tigervnc-de...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel
>
>
>
>
> --
>  - Ola Lundqvist ---
> /  o...@debian.org Folkebogatan 26  \
> |  o...@inguza.com  654 68 KARLSTAD  |
> |  http://inguza.com/  +46 (0)70-332 1551   |
> \  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
>  ---
>
>
> ___
> Pkg-tigervnc-devel mailing list
> pkg-tigervnc-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-tigervnc-devel



-- 
 - Ola Lundqvist ---
/  o...@debian.org Folkebogatan 26  \
|  o...@inguza.com  654 68 KARLSTAD  |
|  http://inguza.com/  +46 (0)70-332 1551   |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---

Bug#841459: bgpdump: FTBFS with bash as /bin/sh

[Chris Lamb]

Source: bgpdump
Version: 1.4.99.15+hg127-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

bgpdump fails to build from source in unstable/amd64 when 
/bin/sh is set to bash. It looks like the autoreconfing is
generating an invalid ./configure script:

  #! /bin/sh
  # From configure.ac 1.4.99.15+hg127-2
  .
  # Guess values for system-dependent variables and create Makefiles.
  # Generated by GNU Autoconf 2.69 for libbgpdump 1.4.99.15.
  #

  […]

 dh_auto_configure
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking
  ./configure: line 3: .: filename argument required
  .: usage: . filename [arguments]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


bgpdump.1.4.99.15+hg127-2.unstable.amd64.log.txt.gz
Description: Binary data

Bug#825704: marked as done (swift-im: should it be removed from Debian?)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 09:35:08 +1300
with message-id <20161020203508.le7hnwx33wy7k...@survex.com>
and subject line Re: Bug#825704: swift-im: should it be removed from Debian?
has caused the Debian Bug report #825704,
regarding swift-im: should it be removed from Debian?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
825704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swift-im
Version: 2.0+dev6-1
Severity: serious

Dear maintainer,

swift-im:

* has few users https://qa.debian.org/popcon.php?package=swift-im
* has 2 unanswered RC bugs since 9 months #797279 #822131
* FTBFS
* several other bugs with no action taken (and waiting for the next big
  upstream is no reason for that, uploads fixing stuff can be done
  nevertheless; also, cherry-pick is a thing and stuff fixed in the next
  release could be backported; and if this is too much of a delta, then
  you should probably release it more often)
* no uploads since 2013
* hinders openssl decruft

This package looks all in all in a bad shape, and I wonder whether it
would be better to be without it instead.




RM: swift-im -- RoQA; FTBFS; RC-buggy; FTBFS; unmaintained; low popcon

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Sat, May 28, 2016 at 11:27:28PM +, Mattia Rizzolo wrote:
> swift-im:
> 
> * has few users https://qa.debian.org/popcon.php?package=swift-im
> * has 2 unanswered RC bugs since 9 months #797279 #822131
> * FTBFS
> * several other bugs with no action taken (and waiting for the next big
>   upstream is no reason for that, uploads fixing stuff can be done
>   nevertheless; also, cherry-pick is a thing and stuff fixed in the next
>   release could be backported; and if this is too much of a delta, then
>   you should probably release it more often)
> * no uploads since 2013
> * hinders openssl decruft

The recent upload of 3.0.4-1 addresses most of the above (including #797279 
which wasn't listed in the changelog entry, but was fixed and has now been
closed):

Format: 1.8
Date: Fri, 03 Jun 2016 15:56:20 +0100
Source: swift-im
Binary: libswiften3 libswiften-dev swift-im
Architecture: source amd64
Version: 3.0.4-1
Distribution: unstable
Urgency: low
Maintainer: Swift Package Maintainer 
Changed-By: Kevin Smith 
Description:
 libswiften-dev - XMPP library (development files)
 libswiften3 - XMPP library
 swift-im   - easy to use Jabber/XMPP chat client
Closes: 745807 757554 784532 810839 822131
Changes:
 swift-im (3.0.4-1) unstable; urgency=low
 .
   * New upstream release
   * Allow compiling with newer boosts. Closes: 810839, 822131
   * Switch to Qt5 instead of Qt4. Closes: 784532, 745807
   * Fix some platform detection in build system. Closes: 757554
   * Rewrite rules file with dh sequencer.
   * Drop -dbg package.

Hence closing this bug.

Cheers,
Olly--- End Message ---

Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

[Andreas Tille]

Hi Sascha,

On Thu, Oct 20, 2016 at 10:17:03PM +0200, Sascha Steinbiss wrote:
> Hi all,
> 
> I have pushed a fix (9aac9cb) to Git, solving the FTBFS. Before doing an 
> upload I would be very happy if an Autotools-savvy person could take another 
> closer look because admittedly I am not really sure about the cause of the 
> problem.

May be asking for comments on debian-mentors@l.d.o might make sense.
 
> I also had to disable a test (test_usage) that otherwise also seems to 
> (mysteriously?) fail in my building chroot, resulting in:
> 
> pty_allocate(nonfatal): posix_openpt(): Permission denied at 
> /usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
> pty_allocate(nonfatal): getpt(): No such file or directory at 
> /usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
> pty_allocate(nonfatal): openpty(): No such file or directory at 
> /usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
> pty_allocate(nonfatal): open(/dev/ptmx): Permission denied at 
> /usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
> Cannot open a pty at test/test.pl line 551.

Strange as well.

I do not feel really competent here and have no spare time cycles to
have a deeper look in the next week(s).

Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed: Re: Bug#841425: dia-common: Fails to install with old xml-core.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -newcomer
Bug #841425 [dia-common] dia-common: Fails to install with old xml-core.
Removed tag(s) newcomer.
> severity -1 grave
Bug #841425 [dia-common] dia-common: Fails to install with old xml-core.
Severity set to 'grave' from 'normal'
> reassign -1 xml-core 0.14
Bug #841425 [dia-common] dia-common: Fails to install with old xml-core.
Bug reassigned from package 'dia-common' to 'xml-core'.
No longer marked as found in versions dia/0.97.3+git20160930-1.
Ignoring request to alter fixed versions of bug #841425 to the same values 
previously set
Bug #841425 [xml-core] dia-common: Fails to install with old xml-core.
There is no source info for the package 'xml-core' at version '0.14' with 
architecture ''
Unable to make a source version for version '0.14'
Marked as found in versions 0.14.
> retitle -1 dh_installxmlcatalogs: xmlcorever must be increased to 0.14 for 
> sort
Bug #841425 [xml-core] dia-common: Fails to install with old xml-core.
Changed Bug title to 'dh_installxmlcatalogs: xmlcorever must be increased to 
0.14 for sort' from 'dia-common: Fails to install with old xml-core.'.
> affects -1 dia-common
Bug #841425 [xml-core] dh_installxmlcatalogs: xmlcorever must be increased to 
0.14 for sort
Added indication that 841425 affects dia-common

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

Bug#840974: [Debian-med-packaging] Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

[Chris Lamb]

Sascha Steinbiss wrote:

> I fully agree and that was why I was asking for some extra pair of
> eyeballs before uploading

Excellent. For some reason I read your message as "I'm going to upload
anyway but if someone can take a look that would be nice I guess."

Mea culpa.  :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#840974: [Debian-med-packaging] Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

[Sascha Steinbiss]

Hi Chris,

>> I would be very happy if an Autotools-savvy person could take another
>> closer look because admittedly I am not really sure about the cause
>> of the problem.
> […]
>> I also had to disable a test (test_usage) that otherwise also seems to
>> (mysteriously?) fail
> 
> These two comments make me a little nervous, alas. We should surely work
> out what was — at least roughly! — the issue instead of just patching
> them out, no?

I fully agree and that was why I was asking for some extra pair of eyeballs 
before uploading. Maybe someone from the team can share some insight or maybe a 
better solution, and my patch could simply serve as a pointer.

Cheers
Sascha

Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

[Chris Lamb]

Hi Sascha,


> I would be very happy if an Autotools-savvy person could take another
> closer look because admittedly I am not really sure about the cause
> of the problem.
[…]
> I also had to disable a test (test_usage) that otherwise also seems to
> (mysteriously?) fail

These two comments make me a little nervous, alas. We should surely work
out what was — at least roughly! — the issue instead of just patching
them out, no?


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#812160: qtwebkit: FTBFS with GCC 6: symbol changes

[James Clarke]

Hi Lisandro,
On Fri, Jan 22, 2016 at 01:42:25PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> Just for the sake of completeness, we are trying to remove this package from
> the archive. We still have quite a lot of packages to fix, but we hope to get
> this done before Stretch's release.

This is blocking src:kde4libs from being built on some of the ports,
which is obviously an important package. I see Pino committed a fix
almost 2 months ago; could one of you please upload this?

Regards,
James


signature.asc
Description: PGP signature

Bug#840974: samtools: FTBFS: configure.ac:69: error: macro PKG_CHECK_EXISTS is not defined; is a m4 file missing?

[Sascha Steinbiss]

Hi all,

I have pushed a fix (9aac9cb) to Git, solving the FTBFS. Before doing an upload 
I would be very happy if an Autotools-savvy person could take another closer 
look because admittedly I am not really sure about the cause of the problem.

I also had to disable a test (test_usage) that otherwise also seems to 
(mysteriously?) fail in my building chroot, resulting in:

pty_allocate(nonfatal): posix_openpt(): Permission denied at 
/usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
pty_allocate(nonfatal): getpt(): No such file or directory at 
/usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
pty_allocate(nonfatal): openpty(): No such file or directory at 
/usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
pty_allocate(nonfatal): open(/dev/ptmx): Permission denied at 
/usr/lib/x86_64-linux-gnu/perl5/5.24/IO/Pty.pm line 24.
Cannot open a pty at test/test.pl line 551.

Any comments welcome. Feel free to upload with any modifications if you want.

Cheers
Sascha


> On 16 Oct 2016, at 16:06, Chris Lamb  wrote:
> 
> Source: samtools
> Version: 1.3.1-2
> Severity: serious
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> samtools fails to build from source in unstable/amd64:
> 
>  […]
> 
> 
>  
> **
>  ** Starting build
>**
>  
> **
> 
>   Package:  samtools
>   Version:  1.3.1-2
>   Build architecture:   amd64
>   Date: Sun, 16 Oct 2016 16:05:23 +0200
>   Hostname: 80cae65f0728
>   Uname:Linux 80cae65f0728 4.7.0-1-amd64 #1 SMP Debian 
> 4.7.5-1 (2016-09-26) x86_64 GNU/Linux
>   /etc/timezone:Europe/Belgrade
> 
>  
> **
>  ** Installing build dependencies 
>**
>  
> **
> 
>  dh_testdir
>  dh_testroot
>  dh_prep
>  dh_testdir
>  dh_testroot
>  dh_install
>  dh_installdocs
>  dh_installchangelogs
>  dh_compress
>  dh_fixperms
>  dh_installdeb
>  dh_gencontrol
>  dh_md5sums
>  dh_builddeb
>  dpkg-deb: building package 'samtools-build-deps' in 
> '../samtools-build-deps_1.3.1-2_all.deb'.
> 
>  The package has been created.
>  Attention, the package has been created in the current directory,
>  not in ".." as indicated by the message above!
>  Selecting previously unselected package samtools-build-deps.
>  (Reading database ... 23458 files and directories currently installed.)
>  Preparing to unpack samtools-build-deps_1.3.1-2_all.deb ...
>  Unpacking samtools-build-deps (1.3.1-2) ...
>  Reading package lists...
>  Building dependency tree...
>  Reading state information...
>  Correcting dependencies... Done
>  The following additional packages will be installed:
>autoconf-archive bash-completion libhts-dev libhts1 libncurses5-dev
>libtinfo-dev tabix zlib1g-dev
>  Suggested packages:
>ncurses-doc
>  The following NEW packages will be installed:
>autoconf-archive bash-completion libhts-dev libhts1 libncurses5-dev
>libtinfo-dev tabix zlib1g-dev
>  0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
>  1 not fully installed or removed.
>  Need to get 2175 kB of archives.
>  After this operation, 12.3 MB of additional disk space will be used.
>  Get:1 http://httpredir.debian.org/debian sid/main amd64 bash-completion all 
> 1:2.1-4.3 [178 kB]
>  Get:2 http://httpredir.debian.org/debian sid/main amd64 libtinfo-dev amd64 
> 6.0+20160917-1 [77.3 kB]
>  Get:3 http://httpredir.debian.org/debian sid/main amd64 libncurses5-dev 
> amd64 6.0+20160917-1 [173 kB]
>  Get:4 http://httpredir.debian.org/debian sid/main amd64 libhts1 amd64 
> 1.3.1-3 [256 kB]
>  Get:5 http://httpredir.debian.org/debian sid/main amd64 libhts-dev amd64 
> 1.3.1-3 [315 kB]
>  Get:6 http://httpredir.debian.org/debian sid/main amd64 zlib1g-dev amd64 
> 1:1.2.8.dfsg-2+b1 [206 kB]
>  Get:7 http://httpredir.debian.org/debian sid/main amd64 autoconf-archive all 
> 20160916-1 [716 kB]
>  Get:8 http://httpredir.debian.org/debian sid/main amd64 tabix amd64 1.3.1-3 
> [254 kB]
>  Fetched 2175 kB in 0s (3409 kB/s)
>  Selecting previously unselected package bash-completion.
>  (Reading database ... 
> (Reading database ... 5%
> (Reading database ... 10%
> (Reading database ... 15%
> (Reading database ... 20%
> (Reading database ... 25%
> (Reading database ... 30%
> (Reading database ... 35%
> (Reading database ... 40%
> (Reading database ... 45%
> (Reading database ... 50%
> (Reading database ... 55%
> (Reading database ... 60%
> (Reading database ..

Bug#841098: marked as done (rygel: FTBFS (rygel-media-engine-test fails))

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 22:14:11 +0200
with message-id <20161020201411.ga27...@fatal.se>
and subject line Re: Bug#841098: not fixed in rygel 0.32.1-1
has caused the Debian Bug report #841098,
regarding rygel: FTBFS (rygel-media-engine-test fails)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841098: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:rygel
Version: 0.32.0-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with autoreconf,gnome
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf --as-needed
Copying file m4/codeset.m4
Copying file m4/extern-inline.m4
Copying file m4/fcntl-o.m4
Copying file m4/glibc2.m4
Copying file m4/glibc21.m4
Copying file m4/intdiv0.m4

[... snipped ...]

# TOTAL: 8
# PASS:  7
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: rygel-media-engine-test
=


(lt-rygel-media-engine-test:659): GStreamer-WARNING **: Element 'filesrc4' 
already has parent
**
ERROR:rygel-media-engine-test.c:2035:__lambda19_: code should not be reached
FAIL rygel-media-engine-test (exit status: 134)


Testsuite summary for Rygel 0.32.0

# TOTAL: 8
# PASS:  7
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to http://bugzilla.gnome.org/enter_bug.cgi?product=Rygel

Makefile:1762: recipe for target 'test-suite.log' failed
make[5]: *** [test-suite.log] Error 1
make[5]: Leaving directory '/<>/tests'
Makefile:1868: recipe for target 'check-TESTS' failed
make[4]: *** [check-TESTS] Error 2
make[4]: Leaving directory '/<>/tests'
Makefile:1990: recipe for target 'check-am' failed
make[3]: *** [check-am] Error 2
make[3]: Leaving directory '/<>/tests'
Makefile:596: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:887: recipe for target 'check' failed
make[1]: *** [check] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The build was made on a QEMU/KVM virtual machine with a single CPU using sbuild.

The relevant part of the build log is included above.

If you need a full build log, just say so, I have plenty of them.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 0.32.1-1

Hello Santiago Vila.

The above mentioned upload was done as a source-only upload.
It built successfully not only in my local environment but also on *all*
architectures (and thus on atleast one buildd for each architecture).

This is obviously a problem in your environment.

The debian bug tracking system is not a support forum. If you need
personal support, then you need to negotiate a support contract first.
The debian bug tracking system is not the place for this.

Regards,
Andreas Henriksson--- End Message ---

Bug#841453: linux-image-4.7.0-1-amd64: can't upgrade to -unsigned: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty

[Jakub Wilk]

Package: linux-image-4.7.0-1-amd64
Version: 4.7.6-1
Severity: serious

I you have linux-image-4.7.0-1-amd64 installed, then upgrading to 
linux-image-4.7.0-1-amd64-unsigned fails:


# apt-get install linux-image-4.7.0-1-amd64-unsigned
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  linux-doc-4.7 (4.7.8-1)
  debian-kernel-handbook (1.0.17)
  grub-pc (2.02~beta3-1)
  | grub-efi-amd64 (2.02~beta3-1)
  | extlinux (3:6.03+dfsg-14)
Recommended packages:
  firmware-linux-free (3.4)
  irqbalance (1.1.0-2)
The following packages will be REMOVED:
  linux-image-4.7.0-1-amd64* (4.7.6-1)
The following NEW packages will be installed:
  linux-image-4.7.0-1-amd64-unsigned (4.7.8-1)
0 upgraded, 1 newly installed, 1 to remove and 35 not upgraded.
Need to get 36.8 MB of archives.
After this operation, 1709 kB disk space will be freed.
Do you want to continue? [Y/n]
Get:1 http://ftp.debian.org/debian unstable/main amd64 
linux-image-4.7.0-1-amd64-unsigned amd64 4.7.8-1 [36.8 MB]
Fetched 36.8 MB in 1s (28.7 MB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 14226 files and directories currently installed.)
Removing linux-image-4.7.0-1-amd64 (4.7.6-1) ...
W: Last kernel image has been removed, so removing the default symlinks
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-4.7.0-1-amd64
Selecting previously unselected package linux-image-4.7.0-1-amd64-unsigned.
(Reading database ... 10177 files and directories currently installed.)
Preparing to unpack .../linux-image-4.7.0-1-amd64-unsigned_4.7.8-1_amd64.deb ...
Unpacking linux-image-4.7.0-1-amd64-unsigned (4.7.8-1) ...
Setting up linux-image-4.7.0-1-amd64-unsigned (4.7.8-1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.7.0-1-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-4.7.0-1-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-4.7.0-1-amd64
I: /initrd.img is now a symlink to boot/initrd.img-4.7.0-1-amd64
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.7.0-1-amd64
cp: cannot stat '/etc/modprobe.d/*': No such file or directory
(Reading database ... 14224 files and directories currently installed.)
Removing linux-image-4.7.0-1-amd64 (4.7.6-1) ...
Purging configuration files for linux-image-4.7.0-1-amd64 (4.7.6-1) ...
W: Last kernel image has been removed, so removing the default symlinks
rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty
dpkg: error processing package linux-image-4.7.0-1-amd64 (--purge):
subprocess installed post-removal script returned error exit status 1
Errors were encountered while processing:
linux-image-4.7.0-1-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)


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

Kernel: Linux 4.7.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages linux-image-4.7.0-1-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.125
ii  kmod22-1.1
ii  linux-base  4.5

--
Jakub Wilk

Bug#841440: marked as done (rdp-alignment: FTBFS with bash as /bin/sh)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 19:27:28 +
with message-id 
and subject line Bug#841440: fixed in rdp-alignment 1.2.0-2
has caused the Debian Bug report #841440,
regarding rdp-alignment: FTBFS with bash as /bin/sh
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rdp-alignment
Version: 1.2.0-1
Severity: serious
Justification: fails to build from source
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

rdp-alignment fails to build from source in unstable/amd64 when 
/bin/sh is set to bash due to usage of metacharacters with 'echo'
in debian/rules:

  […]

 jh_manifest
  Syntax error in debian/manifest (\tClass-Path: commons-cli.jar 
commons-lang.jar commons-io.jar rdp-readseq.jar) - perhaps you are missing a 
":"?
  jh_manifest: Unknown line in debian/manifest (\tClass-Path: commons-cli.jar 
commons-lang.jar commons-io.jar rdp-readseq.jar),
  debian/rules:9: recipe for target 'binary' failed
  make: *** [binary] Error 25

  […]

The full build log and patch is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


rdp-alignment.1.2.0-1.unstable.amd64.log.txt.gz
Description: Binary data
diff --git a/debian/rules b/debian/rules
index 99b93f2..facfef5 100755
--- a/debian/rules
+++ b/debian/rules
@@ -27,7 +27,7 @@ override_dh_auto_build:
cd src ; jar uf ../rdp-alignment.jar data
#Also set the manifest like so
echo usr/share/java/rdp-alignment.jar:>debian/manifest
-   echo '\tClass-Path: commons-cli.jar commons-lang.jar commons-io.jar 
rdp-readseq.jar' >>debian/manifest
-   echo '\tMain-Class: '`grep '^main.class=' nbproject/project.properties 
| cut -c 12-` >>debian/manifest
+   printf '\tClass-Path: commons-cli.jar commons-lang.jar commons-io.jar 
rdp-readseq.jar\n' >>debian/manifest
+   printf '\tMain-Class: '`grep '^main.class=' 
nbproject/project.properties | cut -c 12-`'\n' >>debian/manifest
 
 
--- End Message ---
--- Begin Message ---
Source: rdp-alignment
Source-Version: 1.2.0-2

We believe that the bug you reported is fixed in the latest version of
rdp-alignment, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated rdp-alignment package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Oct 2016 20:27:29 +0200
Source: rdp-alignment
Binary: rdp-alignment
Architecture: source all
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 rdp-alignment - Ribosomal Database Project (RDP) alignment tools package
Closes: 841440
Changes:
 rdp-alignment (1.2.0-2) unstable; urgency=medium
 .
   * Fix build when /bin/sh is set to bash (thanks for the patch to
 Chris Lamb --- End Message ---

Processed: tagging 841197

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 841197 + sid stretch
Bug #841197 {Done: Markus Koschany } [maven-enforcer] 
maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
Bug #841296 {Done: Markus Koschany } [maven-enforcer] 
maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
Bug #841362 {Done: Markus Koschany } [maven-enforcer] 
maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
Bug #841363 {Done: Markus Koschany } [maven-enforcer] 
maven-enforcer: makes several packages to FTBFS with "Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved"
Added tag(s) sid and stretch.
Added tag(s) stretch and sid.
Added tag(s) sid and stretch.
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

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

Bug#831922: marked as done (libjs-swfupload: FTBFS with dpkg-buildpackage -A: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 19:23:38 +
with message-id 
and subject line Bug#831922: fixed in libjs-swfupload 2.2.0.1+ds2-1
has caused the Debian Bug report #831922,
regarding libjs-swfupload: FTBFS with dpkg-buildpackage -A: dh_install: missing 
files, aborting
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
831922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjs-swfupload
Version: 2.2.0.1+ds1-2
Severity: important
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160720 qa-ftbfs qa-indep
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.  This rebuild was done by building only the architecture-independent
packages.  At the same time, a normal build succeeded, which points the
problem specifically to build-indep/binary-indep targets.

If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now. If not, debian/rules
should be modified so that the build-indep and binary-indep target generates
the architecture independent packages (and only those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if
you wish.

I file this bug as severity: important, but Santiago Vila, who led this
effort (kudos to him), got approval from the release team to consider those
bugs RC for stretch. The severity will be increased to 'serious' shortly.
See #830997 for details.

Relevant part (hopefully):
>  fakeroot debian/rules binary-indep
> dh binary-indep
>dh_testroot -i
>dh_prep -i
>dh_installdirs -i
>dh_auto_install -i
>dh_install -i
> dh_install: Cannot find (any matches for) "tmp/swfupload.swf" (tried in "." 
> and "debian/tmp")
> dh_install: missing files, aborting
> debian/rules:17: recipe for target 'binary-indep' failed
> make: *** [binary-indep] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/20/libjs-swfupload_2.2.0.1+ds1-2_unstable_archallonly.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libjs-swfupload
Source-Version: 2.2.0.1+ds2-1

We believe that the bug you reported is fixed in the latest version of
libjs-swfupload, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christian Welzel  (supplier of updated libjs-swfupload 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 10 Aug 2016 17:36:29 +0200
Source: libjs-swfupload
Binary: libjs-swfupload
Architecture: source
Version: 2.2.0.1+ds2-1
Distribution: unstable
Urgency: low
Maintainer: Christian Welzel 
Changed-By: Christian Welzel 
Description:
 libjs-swfupload - javascript library to use Flash's upload functionality
Closes: 831922
Changes:
 libjs-swfupload (2.2.0.1+ds2-1) unstable; urgency=low
 .
   * Split build target into build-arch and build-indep (Closes: #831922).
   * Bump standards version to 3.9.8.
   * Change Vcs-Git to secure uri.
   * Change old project URIs to fork by WordPress maintainers.
 Remove watch file.
   * Adapt the get-orig-source target of debian/rules to new archive.
   * Fix copyright file.
   * Add missing source for swfobject.js.
   * Adapt to new version ds2-1.
   * Remove patches now included in upstream.
Checksums-Sha1:
 2461e9c65fe9f5f012588931a95d30546e246853 1927 libjs-swfupload_2.2.0.1+ds2-1.dsc
 cbdafb150c0f4d505b93f8c27f81cd64ad86df1c 60100 
libjs-swfupload_2.2.0.1+ds2.orig.tar.gz
 853dbb6ca0df38458990746fb2248929f456c63f 10444 
libjs-swfupload_2.2.0.1+ds2-1.debian.tar.xz
Checksums-Sha256:
 cc3d9d5

Bug#841431: marked as done (apt-cacher-ng: FTBFS on mips/mipsel: undefined reference to '__atomic_fetch_add_8')

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 19:20:37 +
with message-id 
and subject line Bug#841431: fixed in apt-cacher-ng 1-2
has caused the Debian Bug report #841431,
regarding apt-cacher-ng: FTBFS on mips/mipsel: undefined reference to 
'__atomic_fetch_add_8'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-cacher-ng
Version: 1-1 
Severity: serious
Tags: sid, patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch


Build for mips and mipsel fails during apt-cacher-ng linking with error:
/usr/include/c++/6/bits/atomic_base.h:514: error: undefined reference to 
'__atomic_fetch_add_8'

Full build log is available here:
https://buildd.debian.org/status/fetch.php?pkg=apt-cacher-ng&arch=mipsel&ver=1-1&stamp=1476932907


libatomic1 provides 8-byte atomic operations for 32-bit MIPS, so linking 
apt-cacher-ng against latomic solves this issue.

The patch that includes this fix is attached.

Regards,
Dejan
--- ./debian/rules.orig	2016-10-20 14:27:34.0 +
+++ ./debian/rules	2016-10-20 14:58:43.0 +
@@ -11,11 +11,18 @@
 CFLAGS += $(CPPFLAGS)
 CXXFLAGS += $(CPPFLAGS)
 
+DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+
+# libatomic provides 8-bytes atomic operation for 32-bit MIPS
+ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
+ EXTRA_LIBS="-DEXTRA_LIBS_ACNG=-latomic"
+endif
+
 %:
 	dh $@ --parallel --with systemd
 
 override_dh_auto_configure:
-	dh_auto_configure -- -DSDINSTALL=on
+	dh_auto_configure -- -DSDINSTALL=on $(EXTRA_LIBS)
 
 # needs extra build deps and internet -> ignore
 override_dh_auto_test:
--- End Message ---
--- Begin Message ---
Source: apt-cacher-ng
Source-Version: 1-2

We believe that the bug you reported is fixed in the latest version of
apt-cacher-ng, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Eduard Bloch  (supplier of updated apt-cacher-ng package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 20 Oct 2016 20:25:39 +0200
Source: apt-cacher-ng
Binary: apt-cacher-ng
Architecture: source amd64
Version: 1-2
Distribution: unstable
Urgency: low
Maintainer: Eduard Bloch 
Changed-By: Eduard Bloch 
Description:
 apt-cacher-ng - caching proxy server for software repositories
Closes: 841431
Changes:
 apt-cacher-ng (1-2) unstable; urgency=low
 .
   [ Dejan Latinovic  ]
   * Fixing FTBFS on MIPS (extra libatomic dependency, closes: #841431)
 .
   [Eduard Bloch]
   * Extended mips/mipsel FTBFS patch to powerpcspe and m68k
Checksums-Sha1:
 fedaa4a47a18903be92a6d0f3d40d072ecd64052 2165 apt-cacher-ng_1-2.dsc
 0336c653d82e07365d2a8da9cf4392b256625f50 47076 apt-cacher-ng_1-2.debian.tar.xz
 f429c2e60af24238160c78e2ecb7ea1c8ee7dc99 240 
apt-cacher-ng-dbgsym_1-2_amd64.deb
 b849765b0de183d6b44f2b2d2f5465caeebc3634 518612 apt-cacher-ng_1-2_amd64.deb
Checksums-Sha256:
 57e3c6453c7a5601c1e9b5de3d9e6105ec3ca825bbaa6337f2c883bde7e51f29 2165 
apt-cacher-ng_1-2.dsc
 c68905fce514496e5e01b7e5013ed578bd7e6dc1cda770d0c97555b8440a62cd 47076 
apt-cacher-ng_1-2.debian.tar.xz
 a7d665be03465f688a3bf5297e5c694f80b5174c8bed2b4cf53df70b444111c5 240 
apt-cacher-ng-dbgsym_1-2_amd64.deb
 86fb60bb35245e8e6851a518595c3d06e847dabd2c261be42e40324a34909123 518612 
apt-cacher-ng_1-2_amd64.deb
Files:
 de4ac6e04c0d75a4f937509f7cd73552 2165 net optional apt-cacher-ng_1-2.dsc
 de3a315aace4c2686a8aa4e263c2c478 47076 net optional 
apt-cacher-ng_1-2.debian.tar.xz
 153eebdd120e9206b993318072893ee9 240 debug extra 
apt-cacher-ng-dbgsym_1-2_amd64.deb
 0122ab06bcaf46bc7af40d1316d6e95e 518612 net optional 
apt-cacher-ng_1-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJYCQ4WAAoJEGl0DlyzX+w8sy0QAI6v7MprBDfmt1Z9XTMyGiC4
4yt+tg/yzgqaUAEPa1GSs0U7asodlhqek/6c/g55V8kMXNhfYj//U1EOoPJ8TQAl
Lio5Kuqus3Prvmu7Pv7mCNjRcO+d8ELC3Qi591zN62sxGsLg2SlAHn3zQkt8vlYF
NV97JUnW+eOwoW5zelcQiWG/QIu4brymF3uRMF5CGIpd3HexTXnyw0ubXpO5P2u4
5MCyfB47PPkosNtlacl9JL8kQYfy+LSzxv9O/ks6BVZvdy2rHkImdhd/nE9iG6v5
o6yqE

Bug#841443: hmqv.h is missing: refered to by /usr/include/cryptopp/eccrypto.h

[Alexandre Viau]

Hello,

On 20/10/16 03:06 PM, László Böszörményi (GCS) wrote:
>  Working on the fix. May you share the program that you want to build?
> I would like to be sure there's no more headers I might have missed to
> install.

Thank you for the (really) fast answer!

I am building Ring (https://ring.cx).

The version I am building is not released yet, but we want to make sure
that we can build on Debian whenever we release it. ( I am the
maintainer for Ring but also part of the dev team).

If you really want to try building Ring (you don't have to), you could
use the following steps:

 - git clone g...@github.com:savoirfairelinux/ring-daemon.git
 - cd contrib
 - mkdir native
 - cd native
 - ../bootstrap
 - make (not -j4!)
 - cd ../../
 - ./autogen.sh
 - ./configure
 - make -j4

The build will fail with the following error:
 - /usr/include/cryptopp/eccrypto.h:19:18: fatal error: hmqv.h: No such
file or directory

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Bug#841447: md5deep: sudo md5deep -rel /* leads to system crash

[Julian Schwarz]

Package: md5deep
Version: 4.2-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

"md5deep -rel /*" crashes my system (reboot) with a for me unkown reason. 
"sha256deep -rel /*" crashes in the same way. This was tested on two
different machines running debian stable and one machine running debian 
unstable all showing the same issue.
A "md5deep -rel /* >> log.txt 2>&1" seems to run without crashing the system. 
While running "md5deep -rel /* >> log.txt" the log.txt
showed that it crashed on reading a file in /home/user and the file ending 
constisted out of NULLS, but a "md5deep -rel /home/*" runs
without any problem.


-- System Information:
Debian Release: 8.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages md5deep depends on:
ii  libc6   2.19-18+deb8u6
ii  libgcc1 1:4.9.2-10
ii  libstdc++6  4.9.2-10

md5deep recommends no packages.

md5deep suggests no packages.

-- debconf-show failed

Processed: found 841443 in 5.6.4-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 841443 5.6.4-1
Bug #841443 [libcrypto++] hmqv.h is missing: refered to by 
/usr/include/cryptopp/eccrypto.h
There is no source info for the package 'libcrypto++' at version '5.6.4-1' with 
architecture ''
Unable to make a source version for version '5.6.4-1'
Marked as found in versions 5.6.4-1.
> thanks
Stopping processing here.

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

Bug#841443: hmqv.h is missing: refered to by /usr/include/cryptopp/eccrypto.h

[GCS]

Hi Alexandre,

On Thu, Oct 20, 2016 at 8:46 PM, Alexandre Viau  wrote:
> It looks like hmqv.h is missing. It is refered by the following file:
>  - /usr/include/cryptopp/eccrypto.h
>
> The prevents the program I am working on to build.
 Working on the fix. May you share the program that you want to build?
I would like to be sure there's no more headers I might have missed to
install.

Thanks,
Laszlo/GCS

Bug#841443: hmqv.h is missing: refered to by /usr/include/cryptopp/eccrypto.h

[Alexandre Viau]

Package: libcrypto++
Severity: serious

Hello,

It looks like hmqv.h is missing. It is refered by the following file:
 - /usr/include/cryptopp/eccrypto.h

The prevents the program I am working on to build.

Cheers,

-- 
Alexandre Viau
av...@debian.org



signature.asc
Description: OpenPGP digital signature

Processed: retitle 839051 to bind9: CVE-2016-2848: A packet with malformed options can trigger an assertion failure

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 839051 bind9: CVE-2016-2848: A packet with malformed options can 
> trigger an assertion failure
Bug #839051 {Done: Salvatore Bonaccorso } [bind9] bind9: A 
packet with malformed options can trigger an assertion failure
Changed Bug title to 'bind9: CVE-2016-2848: A packet with malformed options can 
trigger an assertion failure' from 'bind9: A packet with malformed options can 
trigger an assertion failure'.
> thanks
Stopping processing here.

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

Processed: fixed 839051 in 1:9.8.4.dfsg.P1-6+nmu2+deb7u12

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 839051 1:9.8.4.dfsg.P1-6+nmu2+deb7u12
Bug #839051 {Done: Salvatore Bonaccorso } [bind9] bind9: A 
packet with malformed options can trigger an assertion failure
There is no source info for the package 'bind9' at version 
'1:9.8.4.dfsg.P1-6+nmu2+deb7u12' with architecture ''
Unable to make a source version for version '1:9.8.4.dfsg.P1-6+nmu2+deb7u12'
Marked as fixed in versions 1:9.8.4.dfsg.P1-6+nmu2+deb7u12.
> thanks
Stopping processing here.

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

Bug#839051: retitle 839051 to bind9: A packet with malformed options can trigger an assertion failure ...

[Salvatore Bonaccorso]

retitle 839051 bind9: A packet with malformed options can trigger an assertion 
failure
found 839051 1:9.8.4.dfsg.P1-6
tags 839051 + upstream fixed-upstream
close 839051 1:9.9.3.dfsg.P2-1
thanks

Processed: retitle 839051 to bind9: A packet with malformed options can trigger an assertion failure ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 839051 bind9: A packet with malformed options can trigger an 
> assertion failure
Bug #839051 [bind9] bind9: Unfixed crasher bug in wheezy LTS
Changed Bug title to 'bind9: A packet with malformed options can trigger an 
assertion failure' from 'bind9: Unfixed crasher bug in wheezy LTS'.
> found 839051 1:9.8.4.dfsg.P1-6
Bug #839051 [bind9] bind9: A packet with malformed options can trigger an 
assertion failure
Marked as found in versions bind9/1:9.8.4.dfsg.P1-6.
> tags 839051 + upstream fixed-upstream
Bug #839051 [bind9] bind9: A packet with malformed options can trigger an 
assertion failure
Added tag(s) fixed-upstream and upstream.
> close 839051 1:9.9.3.dfsg.P2-1
Bug #839051 [bind9] bind9: A packet with malformed options can trigger an 
assertion failure
Marked as fixed in versions bind9/1:9.9.3.dfsg.P2-1.
Bug #839051 [bind9] bind9: A packet with malformed options can trigger an 
assertion failure
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#840543: marked as done (node-ebnf-parser: FTBFS (Attempt to unlock test@*, which hasn't been locked))

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 18:01:36 +
with message-id 
and subject line Bug#840543: fixed in node-ebnf-parser 0.1.10+dfsg-3
has caused the Debian Bug report #840543,
regarding node-ebnf-parser: FTBFS (Attempt to unlock test@*, which hasn't been 
locked)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
840543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-ebnf-parser
Version: 0.1.10+dfsg-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>/node-ebnf-parser-0.1.10+dfsg'
npm install
npm ERR! Error: Attempt to unlock test@*, which hasn't been locked
npm ERR! at unlock (/usr/share/npm/lib/utils/locker.js:44:11)
npm ERR! at cb (/usr/share/npm/lib/cache/add-named.js:32:5)
npm ERR! at /usr/share/npm/lib/cache/add-named.js:41:20
npm ERR! at /usr/share/npm/lib/utils/locker.js:22:20
npm ERR! at /usr/share/npm/node_modules/inflight/inflight.js:22:7
npm ERR! at Array.forEach (native)
npm ERR! at res (/usr/share/npm/node_modules/inflight/inflight.js:21:9)
npm ERR! at /usr/lib/nodejs/once.js:17:15
npm ERR! at afterMkdir (/usr/share/npm/lib/cache/get-stat.js:53:14)
npm ERR! at /usr/lib/nodejs/mkdirp/index.js:34:29
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! 

npm ERR! System Linux 4.7.0-1-amd64
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /<>/node-ebnf-parser-0.1.10+dfsg
npm ERR! node -v v4.6.0
npm ERR! npm -v 1.4.21
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR! /<>/node-ebnf-parser-0.1.10+dfsg/npm-debug.log
npm ERR! not ok code 0
Makefile:5: recipe for target 'install' failed
make[1]: *** [install] Error 1
make[1]: Leaving directory '/<>/node-ebnf-parser-0.1.10+dfsg'
dh_auto_build: make -j1 returned exit code 2
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

When I try again, the error may be different. These are the errors I got:

npm ERR! Error: Attempt to unlock git://github.com/zaach/jison.git, which 
hasn't been locked
npm ERR! Error: Attempt to unlock lex-parser@0.1.0, which hasn't been locked
npm ERR! Error: Attempt to unlock test@*, which hasn't been locked

If I don't use sbuild but try to build it by hand, the error is also different:

npm install
npm WARN `git config --get remote.origin.url` returned wrong result 
(git://github.com/zaach/jison.git) undefined
npm WARN `git config --get remote.origin.url` returned wrong result 
(git://github.com/zaach/jison.git) undefined
npm ERR! git clone git://github.com/zaach/jison.git undefined
npm ERR! git clone git://github.com/zaach/jison.git undefined
npm ERR! not found: git
npm ERR! 
npm ERR! Failed using git.
npm ERR! This is most likely not a problem with npm itself.
npm ERR! Please check if you have git installed and in your PATH.

npm ERR! System Linux 4.7.0-1-amd64
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! cwd /tmp/20161012/node-ebnf-parser-0.1.10+dfsg
npm ERR! node -v v4.6.0
npm ERR! npm -v 1.4.21
npm ERR! code ENOGIT

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-ebnf-parser
Source-Version: 0.1.10+dfsg-3

We believe that the bug you reported is fixed in the latest version of
node-ebnf-parser, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-ebn

Processed: reassign 839296 to cdbs, forcibly merging 837006 839296

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 839296 cdbs
Bug #839296 [src:gdb] gdb: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** 
no python implementation resolved from binary package "stamp-autotools".  Stop.
Bug reassigned from package 'src:gdb' to 'cdbs'.
No longer marked as found in versions gdb/7.11.1-2.
Ignoring request to alter fixed versions of bug #839296 to the same values 
previously set
> forcemerge 837006 839296
Bug #837006 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837018 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837024 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837220 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837239 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837243 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837244 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837248 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837256 [cdbs] pygtksourceview: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837260 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837266 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837270 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837274 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837278 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #838359 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #838592 [cdbs] gnome-python-desktop: FTBFS: autotools.mk:44: *** no python 
implementation resolved from binary package "stamp-autotools".
Bug #839296 [cdbs] gdb: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no 
python implementation resolved from binary package "stamp-autotools".  Stop.
Added indication that 839296 affects pygtksourceview
Marked as found in versions cdbs/0.4.143.
Bug #837018 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837024 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837220 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837239 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837243 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837244 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837248 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837256 [cdbs] pygtksourceview: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837260 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837266 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837270 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837274 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837278 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #838359 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #838592 [cdbs] gnome-python-desktop: FTBFS: autotools.mk:44: *** no python 
implementation resolved from binary package "stamp-autotools".
Merged 837006 837018 837024 837220 837239 837243 837244 837248 837256 837260 
837266 837270 837274 837278 838359 838592 839296
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
837006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837006
837018: http://bugs.d

Processed: affects 837006

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 837006 + gdb
Bug #837006 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837018 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837024 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837220 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837239 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837243 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837244 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837248 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837256 [cdbs] pygtksourceview: FTBFS: 
/usr/share/cdbs/1/class/autotools.mk:44: *** no python implementation resolved 
from binary package "stamp-autotools".  Stop.
Bug #837260 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837266 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837270 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837274 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #837278 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #838359 [cdbs] cdbs: some packages FTBFS with 'no python implementation 
resolved from binary package "stamp-autotools"'
Bug #838592 [cdbs] gnome-python-desktop: FTBFS: autotools.mk:44: *** no python 
implementation resolved from binary package "stamp-autotools".
Bug #839296 [cdbs] gdb: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no 
python implementation resolved from binary package "stamp-autotools".  Stop.
Added indication that 837006 affects gdb
Added indication that 837018 affects gdb
Added indication that 837024 affects gdb
Added indication that 837220 affects gdb
Added indication that 837239 affects gdb
Added indication that 837243 affects gdb
Added indication that 837244 affects gdb
Added indication that 837248 affects gdb
Added indication that 837256 affects gdb
Added indication that 837260 affects gdb
Added indication that 837266 affects gdb
Added indication that 837270 affects gdb
Added indication that 837274 affects gdb
Added indication that 837278 affects gdb
Added indication that 838359 affects gdb
Added indication that 838592 affects gdb
Added indication that 839296 affects gdb
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
837006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837006
837018: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837018
837024: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837024
837220: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837220
837239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837239
837243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837243
837244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837244
837248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837248
837256: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837256
837260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837260
837266: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837266
837270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837270
837274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837274
837278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837278
838359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838359
838592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838592
839296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: limit source to lintian, tagging 841442

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source lintian
Limiting to bugs with field 'source' containing at least one of 'lintian'
Limit currently set to 'source':'lintian'

> tags 841442 + pending
Bug #841442 [src:lintian] lintian: FTBFS: fail tests::shared-libs-non-pic-i386
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 782720

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 782720 + patch
Bug #782720 [aspell-is] one filename is not valid utf-8
Ignoring request to alter tags of bug #782720 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#841442: lintian: FTBFS: fail tests::shared-libs-non-pic-i386

[Jakub Wilk]

Source: lintian
Version: 2.5.48
Severity: serious
Justification: fails to build from source

lintian FTBFS on i386:
| tests::shared-libs-non-pic-i386: diff -u 
t/tests/shared-libs-non-pic-i386/tags 
/home/jwilk/lintian-2.5.48/debian/test-out/tests/shared-libs-non-pic-i386/tags.shared-libs-non-pic-i386
| --- t/tests/shared-libs-non-pic-i386/tags 2015-10-05 20:08:38.0 
+
| +++ 
/home/jwilk/lintian-2.5.48/debian/test-out/tests/shared-libs-non-pic-i386/tags.shared-libs-non-pic-i386
   2016-10-20 17:45:44.831884940 +
| @@ -1 +0,0 @@
| -E: libbaz3-1: shlib-with-non-pic-code usr/lib/libbaz3.so.1.0.3b
| fail tests::shared-libs-non-pic-i386: output differs!
[...]
| Failed tests (1)
| tests::shared-libs-non-pic-i386
| debian/rules:48: recipe for target 'runtests' failed

--
Jakub Wilk

Bug#782720: aspell-is: diff for NMU version 0.51-0-4.1

[simon]

Control: tags 782720 + patch
Control: tags 782720 + pending

Dear maintainer,

I've prepared an NMU for aspell-is (versioned as 0.51-0-4.1).
This patch solves the bug of the file name that is not utf-8, 
if the maintainer renames the file in sources.

Regards.

Simon
diff -u aspell-is-0.51-0/debian/changelog aspell-is-0.51-0/debian/changelog
--- aspell-is-0.51-0/debian/changelog
+++ aspell-is-0.51-0/debian/changelog
@@ -1,3 +1,10 @@
+aspell-is (0.51-0-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fixed utf-8 filename bug (closes: #782720).
+
+ -- Simon Barotte   Sat, 15 Oct 2016 23:33:14 +0200
+
 aspell-is (0.51-0-4) unstable; urgency=low
 
   * Converted to use aspell-autobuildhash to build the dictionary hashes
diff -u aspell-is-0.51-0/debian/rules aspell-is-0.51-0/debian/rules
--- aspell-is-0.51-0/debian/rules
+++ aspell-is-0.51-0/debian/rules
@@ -4,6 +4,12 @@
 
 DICT_LANG := is
 
+configure/aspell-$(DICT_LANG)::
+	iconv -f ISO-8859-1 -t utf-8 Makefile.pre > Makefile_utf8.pre
+	rm Makefile.pre
+	mv Makefile_utf8.pre Makefile.pre
+	sed -ri 's/íslenska.alias/islenska.alias/' Makefile.pre
+
 install/aspell-$(DICT_LANG)::
 	for f in *.cwl; do \
 	gzip -9 -c "$$f" > "$(DEB_DESTDIR)/usr/share/aspell/"$$f".gz"; \

Processed: aspell-is: diff for NMU version 0.51-0-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 782720 + patch
Bug #782720 [aspell-is] one filename is not valid utf-8
Added tag(s) patch.
> tags 782720 + pending
Bug #782720 [aspell-is] one filename is not valid utf-8
Added tag(s) pending.

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

Bug#841440: rdp-alignment: FTBFS with bash as /bin/sh

[Chris Lamb]

Source: rdp-alignment
Version: 1.2.0-1
Severity: serious
Justification: fails to build from source
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

rdp-alignment fails to build from source in unstable/amd64 when 
/bin/sh is set to bash due to usage of metacharacters with 'echo'
in debian/rules:

  […]

 jh_manifest
  Syntax error in debian/manifest (\tClass-Path: commons-cli.jar 
commons-lang.jar commons-io.jar rdp-readseq.jar) - perhaps you are missing a 
":"?
  jh_manifest: Unknown line in debian/manifest (\tClass-Path: commons-cli.jar 
commons-lang.jar commons-io.jar rdp-readseq.jar),
  debian/rules:9: recipe for target 'binary' failed
  make: *** [binary] Error 25

  […]

The full build log and patch is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


rdp-alignment.1.2.0-1.unstable.amd64.log.txt.gz
Description: Binary data
diff --git a/debian/rules b/debian/rules
index 99b93f2..facfef5 100755
--- a/debian/rules
+++ b/debian/rules
@@ -27,7 +27,7 @@ override_dh_auto_build:
cd src ; jar uf ../rdp-alignment.jar data
#Also set the manifest like so
echo usr/share/java/rdp-alignment.jar:>debian/manifest
-   echo '\tClass-Path: commons-cli.jar commons-lang.jar commons-io.jar 
rdp-readseq.jar' >>debian/manifest
-   echo '\tMain-Class: '`grep '^main.class=' nbproject/project.properties 
| cut -c 12-` >>debian/manifest
+   printf '\tClass-Path: commons-cli.jar commons-lang.jar commons-io.jar 
rdp-readseq.jar\n' >>debian/manifest
+   printf '\tMain-Class: '`grep '^main.class=' 
nbproject/project.properties | cut -c 12-`'\n' >>debian/manifest
 
 

Processed: [bts-link] source package amule

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package amule
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #840674 (http://bugs.debian.org/840674)
> # Bug title: Amule crashes in Testing
> #  * https://github.com/amule-project/amule/issues/77
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 840674 + fixed-upstream
Bug #840674 [amule] Amule crashes in Testing
Added tag(s) fixed-upstream.
> usertags 840674 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#841129: marked as done (src:libjpeg-turbo: FTBFS on mips*: jsimd_mips.c:82:3: error: 'env' undeclared)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 17:09:07 +
with message-id 
and subject line Bug#841129: fixed in libjpeg-turbo 1:1.5.1-2
has caused the Debian Bug report #841129,
regarding src:libjpeg-turbo: FTBFS on mips*: jsimd_mips.c:82:3: error: 'env' 
undeclared
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libjpeg-turbo
Version: 1:1.5.1-1
Severity: serious
Tags: patch upstream

libjpeg-turbo fails to build from source on mips* with the following
error:

| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
-ffloat-store -c jsimd_mips_dspr2.S -fPIE -o jsimd_mips_dspr2.o >/dev/null 2>&1
| jsimd_mips.c: In function 'init_simd':
| jsimd_mips.c:82:3: error: 'env' undeclared (first use in this function)
|env = getenv("JSIMD_FORCEDSPR2");
|^~~
| jsimd_mips.c:82:3: note: each undeclared identifier is reported only once for 
each function it appears in
| Makefile:596: recipe for target 'jsimd_mips.lo' failed

The problem is that the env variable is not declared in the MIPS
specific code. The following simple patch fixes the issue:

--- libjpeg-turbo-1.5.1.orig/simd/jsimd_mips.c
+++ libjpeg-turbo-1.5.1/simd/jsimd_mips.c
@@ -63,6 +63,8 @@ parse_proc_cpuinfo(const char* search_st
 LOCAL(void)
 init_simd (void)
 {
+  char *env = NULL;
+
   if (simd_support != ~0U)
 return;

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: mips64el (mips64)

Kernel: Linux 4.7.0-1-5kc-malta
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: libjpeg-turbo
Source-Version: 1:1.5.1-2

We believe that the bug you reported is fixed in the latest version of
libjpeg-turbo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated libjpeg-turbo package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 20 Oct 2016 15:51:27 +0200
Source: libjpeg-turbo
Binary: libjpeg-dev libjpeg62-turbo-dev libjpeg62-turbo libturbojpeg0 
libturbojpeg0-dev libjpeg-turbo-progs
Architecture: source
Version: 1:1.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Description:
 libjpeg-dev - Development files for the JPEG library [dummy package]
 libjpeg-turbo-progs - Programs for manipulating JPEG files
 libjpeg62-turbo - libjpeg-turbo JPEG runtime library
 libjpeg62-turbo-dev - Development files for the libjpeg-turbo JPEG library
 libturbojpeg0 - TurboJPEG runtime library - SIMD optimized
 libturbojpeg0-dev - Development files for the TurboJPEG library
Closes: 841129
Changes:
 libjpeg-turbo (1:1.5.1-2) unstable; urgency=medium
 .
   * Declare env on MIPS on first use (Courtesy of Aurelien Jarno) (Closes: 
#841129)
Checksums-Sha1:
 a305ed66b33dc8de5df5c072c8aa6b5b414f4c07 2420 libjpeg-turbo_1.5.1-2.dsc
 ae8dc650d97aad0df13cba89b566b659e7485c82 78576 
libjpeg-turbo_1.5.1-2.debian.tar.xz
Checksums-Sha256:
 9f755bfafa4795f91c689cb742194559f6e543e35ba135e0d30f6b51eed1eba2 2420 
libjpeg-turbo_1.5.1-2.dsc
 0077c9e2b7ec2abe25c7a591e65a08750045a28dcd00207a928079a3d31b3cc4 78576 
libjpeg-turbo_1.5.1-2.debian.tar.xz
Files:
 e97447de85937686b2298764d4dc0270 2420 graphics optional 
libjpeg-turbo_1.5.1-2.dsc
 ef0ab6252d1ae8a2b9088ff3fe67478c 78576 graphics optional 
libjpeg-turbo_1.5.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYCM9ZXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHKcAP/3+rexMvJYBZpflkAKxUb1Wn
YcqpZGW4uLioyd1ZbIch5Zlg46JUvK1xpFlZHIPBTE8/eVc6L0Zn/4Zv8h+7t8ms
OX9GUipqqPKO9Tyy15lEtk3BoyzR1NR0SGuc9LYGPEPfaoNl6K6GdW6wmtASs

Bug#841438: --enable-default-pie breaks kernel build on amd64

[Niels Thykier]

Control: severity -1 normal

On Thu, 20 Oct 2016 17:48:52 +0100 Klaus Ethgen  wrote:
> 
> Package: gcc-6
> Version: 6.2.0-7
> Severity: critical
> 
> The --enable-default-pie option breaks make-kpkg and normal kernel
> builds as the kernel cannot be compiled with pie option.
> 
> [...]
> 
> - -- 
> Klaus Ethgen   http://www.ethgen.ch/

Hi Klaus,

There was consensus on enabling PIE by default via the
--enable-default-pie option.  If the make-kpkg and kernel packages now
FTBFS, we should reassign the bug to those packages.

Thanks,
~Niels

Processed: Re: --enable-default-pie breaks kernel build on amd64

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #841438 [gcc-6] --enable-default-pie breaks kernel build on amd64
Severity set to 'normal' from 'critical'

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

Bug#841438: --enable-default-pie breaks kernel build on amd64

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: gcc-6
Version: 6.2.0-7
Severity: critical

The --enable-default-pie option breaks make-kpkg and normal kernel
builds as the kernel cannot be compiled with pie option.

- -- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.7 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages gcc-6 depends on:
ii  binutils  2.27-9
ii  cpp-6 6.2.0-7
ii  gcc-6-base6.2.0-7
ii  libc6 2.24-5
ii  libcc1-0  6.2.0-7
ii  libgcc-6-dev  6.2.0-7
ii  libgcc1   1:6.2.0-7
ii  libgmp10  2:6.1.1+dfsg-1
ii  libisl15  0.17.1-1
ii  libmpc3   1.0.3-1
ii  libmpfr4  3.1.5-1
ii  libstdc++66.2.0-7
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages gcc-6 recommends:
ii  libc6-dev  2.24-5

Versions of packages gcc-6 suggests:
pn  gcc-6-doc 
pn  gcc-6-locales 
pn  gcc-6-multilib
pn  libasan3-dbg  
pn  libatomic1-dbg
pn  libcilkrts5-dbg   
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libmpx2-dbg   
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan0-dbg 

- -- no debconf information

- -- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Comment: Charset: ISO-8859-1

iQGcBAEBCgAGBQJYCPVeAAoJEKZ8CrGAGfas4eML/2Lzj5nMOI4LZN8W8M7G9yPE
t9wMtol2biR16UbyyVLVK3yT6uf3qsR+Z43+Eva/HD1hFgGySm7rpSRsCpJ8tN9n
qVFth4mF5O4q9sEA+d7p+xUqhkKP/GjY+a42gGwyimdtVQDyNeuYyph7ZCy9nDBT
QwB7khSpaLI2GSSB8Fmn+O0P5khKh1aJjox/OaKID57a+d2Usgdh23+eaCPt2dlz
6limIuzjR/G4TZe01K2UkyAv1zEdgM1mfDWku/W4yIA5Ld9J1mh0ljXhhZaoscqb
r7qRRyArrZj4RySInLL/uEOxO3ezuNR19Z9OA7J57zodhksNWGZef+87KJ1TV3cY
d/uIEhROKX9kXfAXgoSlTbXu982a6vm8u18gEjnxUbMzWSUPomhMUCjp2OODTea+
GwpM3nE7tKbsStz2esLE93hGg0xdKj/D1mQHdqiI8bd2zeHLsOi+H6lQMI+DN/CV
npd34DibnrkziQTAMoiCpCPENE5XUW6DktYK8I43SQ==
=xLja
-END PGP SIGNATURE-

Bug#841420: --enable-default-pie breaks kernel builds

[Sven Joachim]

On 2016-10-20 17:54 +0200, Bálint Réczey wrote:

> Control: reassign -1 linux 4.7.8-1
> Control: severity -1 serious
> Control: tags -1 patch
>
> Hi David,
>
> 2016-10-20 14:02 GMT+02:00 David Weinehall :
>> Package: gcc-6
>> Severity: important
>> Version: 6.2.0-7
>>
>> --enable-default-pie (first enabled in gcc-6 6.2.0-7) causes kernel
>> builds to fail.  If the kernel is configured with the stack protector
>> enabled it'll fail with a rather unhelpful error message claiming
>> that the compiler doesn't support -fstack-protector,
>> but the problem is in fact caused by:
>>
>> kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
>>
>> (The kernel is built with -mcmodel=kernel)
>>
>> I think it's fair to say that the kernel is kind of an important piece
>> of software and that it's imperative that we don't break kernel builds...
>
> The kernel is very important indeed and it did break in our build test.
> I'm sorry, somehow I missed filing bug for the linux package, just for
> user-mode-linux.
> The following patch fixes the FTBFS:
>
> --- linux-4.7.8/debian/rules.d/Makefile.inc
> +++ linux-4.7.8/debian/rules.d/Makefile.inc
> @@ -5,7 +5,8 @@
>
>  SHELL = /bin/sh -e
>
> -CC = $(CROSS_COMPILE)gcc
> +CC = $(CROSS_COMPILE)gcc -no-pie
> +LD = $(CROSS_COMPILE)ld -no-pie
>  CXX = $(CROSS_COMPILE)g++
>  CFLAGS := $(shell dpkg-buildflags --get CFLAGS) -Wall
>  CPPFLAGS := $(shell dpkg-buildflags --get CPPFLAGS) \
>
> Maybe the ld part is obsolete, I have not checked that.

That patch might work for the Debian package, but has anybody contacted
the upstream kernel developers about that?  At least the 4.8.3 vanilla
kernel fails in the same way, I haven't tested 4.9-rc1 yet.

FWIW, this issue has been discussed in Ubuntu for six months(!), see
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982.

Cheers,
   Sven

Bug#841427: unifdef: FTBFS under some locales (eg. fr_CH.UTF-8)

[Bob Proulx]

Chris Lamb wrote:
> unifdef fails to build from source in unstable/amd64 under some
> locales (eg. LANG="fr_CH.UTF-8").

Thank you for the report.  I am preparing a new package upload and
will fix this in that upload.

> This is due to hard-coded error messages in the testsuite:

I would say due to insufficient defensive setup of the test suite.
But the result is the same.  It fails if not being built in the C
locale. :-)

> - $(MAKE) test
> + LC_ALL=C $(MAKE) test
>   touch build-stamp

Agreed.

Thanks!
Bob


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 841368 linux 4.8.1-1
Bug #841368 [gcc-6] gcc-6 6.2.0-7 breaks kernel build if stack protection is 
enabled
Bug reassigned from package 'gcc-6' to 'linux'.
No longer marked as found in versions gcc-6/6.2.0-7.
Ignoring request to alter fixed versions of bug #841368 to the same values 
previously set
Bug #841368 [linux] gcc-6 6.2.0-7 breaks kernel build if stack protection is 
enabled
There is no source info for the package 'linux' at version '4.8.1-1' with 
architecture ''
Unable to make a source version for version '4.8.1-1'
Marked as found in versions 4.8.1-1.
> forcemerge 841420 841368
Bug #841420 [linux] --enable-default-pie breaks kernel builds
Bug #841368 [linux] gcc-6 6.2.0-7 breaks kernel build if stack protection is 
enabled
Severity set to 'serious' from 'normal'
There is no source info for the package 'linux' at version '4.7.8-1' with 
architecture ''
Unable to make a source version for version '4.7.8-1'
There is no source info for the package 'linux' at version '4.8.1-1' with 
architecture ''
Unable to make a source version for version '4.8.1-1'
Marked as found in versions 4.7.8-1.
Added tag(s) patch.
Bug #841420 [linux] --enable-default-pie breaks kernel builds
There is no source info for the package 'linux' at version '4.7.8-1' with 
architecture ''
Unable to make a source version for version '4.7.8-1'
There is no source info for the package 'linux' at version '4.8.1-1' with 
architecture ''
Unable to make a source version for version '4.8.1-1'
Marked as found in versions 4.8.1-1.
Merged 841368 841420
> thanks
Stopping processing here.

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

Bug#841420: --enable-default-pie breaks kernel builds

[S R Wright]

Concurring with Wolfgang;  pulling the source straight from kernel.org 
and using identical .config files will work with 6.2.0-6 but fail with 
6.2.0-7.   I was able to build and install 4.8.3 with no issues after 
back-revving gcc et. al. to 6.2.0-6


-- sRw


On 10/20/16 11:09, Wolfgang Walter wrote:

Hello,

with this version of gcc-6 I can't build vanilla kernels any more. It fails
with even with CC_STACKPROTECTOR_STRONG disabled:

scripts/kconfig/mconf  Kconfig
configuration written to .config

*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.

ksrc@ei:~/build/kernels/linux-4.8.3$ make
scripts/kconfig/conf  --silentoldconfig Kconfig
   CHK include/config/kernel.release
   CHK include/generated/uapi/linux/version.h
   CHK include/generated/utsrelease.h
   UPD include/generated/utsrelease.h
   CC  kernel/bounds.s
kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
  /*
  
Kbuild:45: recipe for target 'kernel/bounds.s' failed

make[1]: *** [kernel/bounds.s] Error 1
Makefile:1015: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2


I think this is a major regression if you can't build vanilla and stable
kernels any more.

Regards,

Bug#841420: --enable-default-pie breaks kernel builds

[Wolfgang Walter]

Hello,

with this version of gcc-6 I can't build vanilla kernels any more. It fails 
with even with CC_STACKPROTECTOR_STRONG disabled:

scripts/kconfig/mconf  Kconfig
configuration written to .config

*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.

ksrc@ei:~/build/kernels/linux-4.8.3$ make
scripts/kconfig/conf  --silentoldconfig Kconfig
  CHK include/config/kernel.release
  CHK include/generated/uapi/linux/version.h
  CHK include/generated/utsrelease.h
  UPD include/generated/utsrelease.h
  CC  kernel/bounds.s
kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
 /*
 
Kbuild:45: recipe for target 'kernel/bounds.s' failed
make[1]: *** [kernel/bounds.s] Error 1
Makefile:1015: recipe for target 'prepare0' failed
make: *** [prepare0] Error 2


I think this is a major regression if you can't build vanilla and stable 
kernels any more.

Regards,
-- 
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts

Processed: Re: Bug#841420: --enable-default-pie breaks kernel builds

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 linux 4.7.8-1
Bug #841420 [gcc-6] --enable-default-pie breaks kernel builds
Bug reassigned from package 'gcc-6' to 'linux'.
No longer marked as found in versions gcc-6/6.2.0-7.
Ignoring request to alter fixed versions of bug #841420 to the same values 
previously set
Bug #841420 [linux] --enable-default-pie breaks kernel builds
There is no source info for the package 'linux' at version '4.7.8-1' with 
architecture ''
Unable to make a source version for version '4.7.8-1'
Marked as found in versions 4.7.8-1.
> severity -1 serious
Bug #841420 [linux] --enable-default-pie breaks kernel builds
Severity set to 'serious' from 'important'
> tags -1 patch
Bug #841420 [linux] --enable-default-pie breaks kernel builds
Added tag(s) patch.

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

Bug#840900: zorp: FTBFS (vector: No such file or directory)

[SZALAY Attila]

Hi,

Zorp and libzorpll is highly bonded and therefore it has the same maintainer.

The problem is that I had to upgrade the libzorpll first and only was able to 
start upgrading the Zorp after that. But unfortunatelly I found an issue with 
compiling the Zorp (SSLv3 is removed from openssl), so I reported it upstream 
and now Im waiting while upstrea fix it.

Also, to prevent the issue to happen again, I created a new -dev package, which 
is version dependent. But unfortunately it is not helps in the current case.

This is an unfortunate event, but hopefully it will have been solved before the 
freeze. :)

On 2016. október 20. 11:29:26 CEST, peter green  wrote:
>>
>> I tried to build this package in stretch with "dpkg-buildpackage -A"
>> (which is what the "Arch: all" autobuilder would do to build it)
>> but it failed:
>A few notes on this bug (note: i'm just a derivative maintainer taking
>a 
>quick look at the bug, not a maintainer of this package)
>
>1. It is not specific to building with dpkg-buildpackage -A [1][2]
>2. The actual failure seems to be caused by indirectly including a C++ 
>header while building with a plain C compiler.
>3. There currently appears to be an (apparently uncoordinated)
>libzorpll 
>transition going on which I suspect may be the trigger for this bug.
>
>[1] 
>http://buildd.raspbian.org/status/fetch.php?pkg=zorp&arch=armhf&ver=3.9.5-7.1%2Bb3&stamp=1476485016
>[2] 
>https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zorp.html

Processed: Properly merge to the root cause

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 837658 serious
Bug #837658 [libfl-dev] libfl-dev: Please build libfl_pic.a with -fPIC
Severity set to 'serious' from 'important'
> unblock 840394 by 837658
Bug #840394 [src:motif] motif: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
840394 was blocked by: 837658
840394 was not blocking any bugs.
Removed blocking bug(s) of 840394: 837658
> reassign 840394 libfl-dev
Bug #840394 [src:motif] motif: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
Bug reassigned from package 'src:motif' to 'libfl-dev'.
No longer marked as found in versions motif/2.3.4-11.
Ignoring request to alter fixed versions of bug #840394 to the same values 
previously set
> reassign 841394 libfl-dev
Bug #841394 [src:filters] filters: FTBFS: relocation R_X86_64_PC32 against 
symbol `exit@@GLIBC_2.2.5' can not be used when making a shared object; 
recompile with -fPIC
Bug reassigned from package 'src:filters' to 'libfl-dev'.
No longer marked as found in versions filters/2.55-1.
Ignoring request to alter fixed versions of bug #841394 to the same values 
previously set
> forcemerge 837658 840394 841394
Bug #837658 [libfl-dev] libfl-dev: Please build libfl_pic.a with -fPIC
Bug #840394 [libfl-dev] motif: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
840394 was not blocked by any bugs.
840394 was not blocking any bugs.
Added blocking bug(s) of 840394: 835148
Added indication that 840394 affects motif,filters
The source libfl-dev and version 2.6.1-1 do not appear to match any binary 
packages
Marked as found in versions libfl-dev/2.6.1-1.
Bug #841394 [libfl-dev] filters: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
841394 was not blocked by any bugs.
841394 was not blocking any bugs.
Added blocking bug(s) of 841394: 835148
Added indication that 841394 affects motif,filters
The source libfl-dev and version 2.6.1-1 do not appear to match any binary 
packages
Marked as found in versions libfl-dev/2.6.1-1.
Merged 837658 840394 841394
> affects 837658 src:motif
Bug #837658 [libfl-dev] libfl-dev: Please build libfl_pic.a with -fPIC
Bug #840394 [libfl-dev] motif: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
Bug #841394 [libfl-dev] filters: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
Added indication that 837658 affects src:motif
Added indication that 840394 affects src:motif
Added indication that 841394 affects src:motif
> affects 837658 src:filters
Bug #837658 [libfl-dev] libfl-dev: Please build libfl_pic.a with -fPIC
Bug #840394 [libfl-dev] motif: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
Bug #841394 [libfl-dev] filters: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
Added indication that 837658 affects src:filters
Added indication that 840394 affects src:filters
Added indication that 841394 affects src:filters
> block 837658 by 841203
Bug #837658 [libfl-dev] libfl-dev: Please build libfl_pic.a with -fPIC
Bug #840394 [libfl-dev] motif: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
Bug #841394 [libfl-dev] filters: FTBFS: relocation R_X86_64_PC32 against symbol 
`exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with 
-fPIC
837658 was blocked by: 835148
837658 was not blocking any bugs.
Added blocking bug(s) of 837658: 841203
840394 was blocked by: 835148
840394 was not blocking any bugs.
Added blocking bug(s) of 840394: 841203
841394 was blocked by: 835148
841394 was not blocking any bugs.
Added blocking bug(s) of 841394: 841203
> thanks
Stopping processing here.

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

Bug#841431: apt-cacher-ng: FTBFS on mips/mipsel: undefined reference to '__atomic_fetch_add_8'

[Dejan Latinovic]

Package: apt-cacher-ng
Version: 1-1 
Severity: serious
Tags: sid, patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch


Build for mips and mipsel fails during apt-cacher-ng linking with error:
/usr/include/c++/6/bits/atomic_base.h:514: error: undefined reference to 
'__atomic_fetch_add_8'

Full build log is available here:
https://buildd.debian.org/status/fetch.php?pkg=apt-cacher-ng&arch=mipsel&ver=1-1&stamp=1476932907


libatomic1 provides 8-byte atomic operations for 32-bit MIPS, so linking 
apt-cacher-ng against latomic solves this issue.

The patch that includes this fix is attached.

Regards,
Dejan
--- ./debian/rules.orig	2016-10-20 14:27:34.0 +
+++ ./debian/rules	2016-10-20 14:58:43.0 +
@@ -11,11 +11,18 @@
 CFLAGS += $(CPPFLAGS)
 CXXFLAGS += $(CPPFLAGS)
 
+DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+
+# libatomic provides 8-bytes atomic operation for 32-bit MIPS
+ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
+ EXTRA_LIBS="-DEXTRA_LIBS_ACNG=-latomic"
+endif
+
 %:
 	dh $@ --parallel --with systemd
 
 override_dh_auto_configure:
-	dh_auto_configure -- -DSDINSTALL=on
+	dh_auto_configure -- -DSDINSTALL=on $(EXTRA_LIBS)
 
 # needs extra build deps and internet -> ignore
 override_dh_auto_test:

Bug#841429: homesick: FTBFS under some locales (eg. fr_CH.UTF-8)

[Chris Lamb]

Source: homesick
Version: 1.1.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

homesick fails to build from source in unstable/amd64 under some locales (eg. 
LANG="fr_CH.UTF-8") as the testsuite — which is curiously run in the install
target — uses local-sensitive strings to determine success.

  […]

  
┌──┐
  │ Run tests for ruby2.3 from debian/ruby-tests.rake   
 │
  
└──┘
  
  
RUBYLIB=/home/lamby/temp/cdt.20161020163846.S0SIG1t1l1.db.homesick/homesick-1.1.3/debian/homesick/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/homesick/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*_spec.rb
  [Coveralls] Set up the SimpleCov formatter.
  [Coveralls] Using SimpleCov's default settings.
  ..WARNING: Using the `raise_error` matcher without providing a 
specific error or message risks false positives, since `raise_error` will match 
when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially 
allowing the expectation to pass without even executing the method you are 
intending to call. Actual error raised was #. Instead consider providing a specific error class or message. This 
message can be suppressed by setting: 
`RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 
Called from 
/home/lamby/temp/cdt.20161020163846.S0SIG1t1l1.db.homesick/homesick-1.1.3/spec/homesick_cli_spec.rb:149:in
 `block (3 levels) in '.
  FF.F.
  
  Failures:
  
1) Homesick::CLI status says "nothing to commit" when there are no changes
   Failure/Error: expect(text).to match(%r{nothing to commit \(create/copy 
files and use "git add" to track\)$})
  
 expected "Sur la branche master\n\nValidation initiale\n\nrien à 
valider (créez/copiez des fichiers et utilisez \"git add\" pour les suivre)\n" 
to match /nothing to commit \(create\/copy files and use "git add" to track\)$/
 Diff:
 @@ -1,2 +1,6 @@
 -/nothing to commit \(create\/copy files and use "git add" to track\)$/
 +Sur la branche master
 +
 +Validation initiale
 +
 +rien à valider (créez/copiez des fichiers et utilisez "git add" pour 
les suivre)
   # ./spec/homesick_cli_spec.rb:441:in `block (3 levels) in '
  
2) Homesick::CLI status says "Changes to be committed" when there are 
changes
   Failure/Error: expect(text).to match(%r{Changes to be committed:.*new 
file:\s*home\/.some_rc_file}m)
  
 expected "Sur la branche master\n\nValidation 
initiale\n\nModifications qui seront validées :\n  (utilisez \"git rm --cached 
...\" pour désindexer)\n\n\tnouveau fichier : home/.some_rc_file\n\n" 
to match /Changes to be committed:.*new file:\s*home\/.some_rc_file/m
 Diff:
 @@ -1,2 +1,9 @@
 -/Changes to be committed:.*new file:\s*home\/.some_rc_file/m
 +Sur la branche master
 +
 +Validation initiale
 +
 +Modifications qui seront validées :
 +  (utilisez "git rm --cached ..." pour désindexer)
 +
 +  nouveau fichier : home/.some_rc_file
   # ./spec/homesick_cli_spec.rb:449:in `block (3 levels) in '
  
3) Homesick::CLI track commit has a commit message when the commit succeeds
   Failure/Error: expect(text).to match(/^\[master \(root-commit\) \w+\] 
Test message/)
  
 expected "[master (commit racine) 9bf3bd7] Test message\n 1 file 
changed, 0 insertions(+), 0 deletions(-)\n create mode 100644 
home/.a_random_rc_file\n" to match /^\[master \(root-commit\) \w+\] Test 
message/
 Diff:
 @@ -1,2 +1,4 @@
 -/^\[master \(root-commit\) \w+\] Test message/
 +[master (commit racine) 9bf3bd7] Test message
 + 1 file changed, 0 insertions(+), 0 deletions(-)
 + create mode 100644 home/.a_random_rc_file
   # ./spec/homesick_cli_spec.rb:609:in `block (4 levels) in '
  
  Finished in 2.87 seconds (files took 0.3813 seconds to load)
  71 examples, 3 failures
  
  Failed examples:
  
  rspec ./spec/homesick_cli_spec.rb:438 # Homesick::CLI status says "nothing to 
commit" when there are no changes
  rspec ./spec/homesick_cli_spec.rb:444 # Homesick::CLI status says "Changes to 
be committed" when there are changes
  rspec ./spec/homesick_cli_spec.rb:602 # Homesick::CLI track commit has a 
commit message when the commit succeeds
  
  [Covera

Bug#841428: tornado-pyvows: FTBFS: ValueError: No JSON object could be decoded

[Chris Lamb]

Source: tornado-pyvows
Version: 0.6.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

tornado-pyvows fails to build from source in unstable/amd64:

  […]

  /usr/bin/make test
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20161020163609.4UfnyHb5wN.db.tornado-pyvows/tornado-pyvows-0.6.1'
  INFO:tornado.access:200 GET / (127.0.0.1) 0.50ms
  INFO:tornado.access:200 GET / (127.0.0.1) 0.28ms
  INFO:tornado.access:200 POST / (127.0.0.1) 0.26ms
  INFO:tornado.access:200 GET /echo (127.0.0.1) 0.34ms
  INFO:tornado.access:200 GET /echo (127.0.0.1) 0.30ms
  INFO:tornado.access:200 GET /echo (127.0.0.1) 0.34ms
  INFO:tornado.access:200 POST / (127.0.0.1) 0.38ms
  INFO:tornado.access:204 HEAD / (127.0.0.1) 0.25ms
  INFO:tornado.access:200 GET / (127.0.0.1) 0.25ms
  INFO:tornado.access:200 POST / (127.0.0.1) 0.41ms
  INFO:tornado.access:200 POST / (127.0.0.1) 0.31ms
  INFO:tornado.access:200 POST / (127.0.0.1) 0.36ms
  INFO:tornado.access:200 POST / (127.0.0.1) 0.42ms
  INFO:tornado.access:200 GET / (127.0.0.1) 0.25ms
  INFO:tornado.access:200 GET /echo (127.0.0.1) 0.35ms
  INFO:tornado.access:200 GET /echo (127.0.0.1) 0.30ms
  
   
   Vows Results
   
  
  
  Post
  
   Error in topic:
  No JSON object could be decoded
  
  Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/pyvows/runner/gevent.py", line 
141, in _run_setup_and_topic
  topic = topic_func(*topic_list)
File 
"/home/lamby/temp/cdt.20161020163609.4UfnyHb5wN.db.tornado-pyvows/tornado-pyvows-0.6.1/vows/client_vows.py",
 line 25, in topic
  requestbin_id = json.loads(response.body)['name']
File "/usr/lib/python2.7/json/__init__.py", line 339, in loads
  return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 364, in decode
  obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.7/json/decoder.py", line 382, in raw_decode
  raise ValueError("No JSON object could be decoded")
  ValueError: No JSON object could be decoded
  
✗ OK » 63 honored • 1 broken • 94 skipped (0.112441s)
  
  Makefile:3: recipe for target 'test' failed
  make[2]: *** [test] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20161020163609.4UfnyHb5wN.db.tornado-pyvows/tornado-pyvows-0.6.1'
  debian/rules:7: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161020163609.4UfnyHb5wN.db.tornado-pyvows/tornado-pyvows-0.6.1'
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


tornado-pyvows.0.6.1-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#841427: unifdef: FTBFS under some locales (eg. fr_CH.UTF-8)

[Chris Lamb]

Source: unifdef
Version: 2.10-1
Severity: serious
Justification: fails to build from source
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

unifdef fails to build from source in unstable/amd64 under some
locales (eg. LANG="fr_CH.UTF-8").

This is due to hard-coded error messages in the testsuite:

  […]

  FAILED: multimissing.err: opts="-DFOO=1 -DFOOB=42 -UBAR" files="if1.c 
ifmissing.c if2.c" . ./multi-generic-sh
  --- multimissing.experr   2014-01-07 20:18:30.0 +0100
  +++ multimissing.err  2016-10-20 16:18:24.547467992 +0200
  @@ -1,4 +1,4 @@
   unifdef: can't open mifmissing.c: No such file or directory
  -diff: mifmissing.c~: No such file or directory
  -diff: mifmissing.c: No such file or directory
  -diff: mif2.c~: No such file or directory
  +diff: mifmissing.c~: Aucun fichier ou dossier de ce type
  +diff: mifmissing.c: Aucun fichier ou dossier de ce type
  +diff: mif2.c~: Aucun fichier ou dossier de ce type
  ..

  […]

The full build log & a patch is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


unifdef.2.10-1.unstable.amd64.log.txt.gz
Description: Binary data
diff --git a/debian/rules b/debian/rules
index f859264..17f632a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -8,7 +8,7 @@ build-arch: build-stamp
 
 build-stamp:
$(MAKE) $(shell dpkg-buildflags --export=cmdline)
-   $(MAKE) test
+   LC_ALL=C $(MAKE) test
touch build-stamp
 
 clean:

Processed: Re: Bug#841098: not fixed in rygel 0.32.1-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 841098 0.32.1-1
Bug #841098 {Done: Andreas Henriksson } [src:rygel] rygel: 
FTBFS (rygel-media-engine-test fails)
Marked as found in versions rygel/0.32.1-1; no longer marked as fixed in 
versions rygel/0.32.1-1 and reopened.
> thanks
Stopping processing here.

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

Bug#841131: marked as done (dump: FTBFS: aclocal-1.14: command not found)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 12:34:52 +
with message-id 
and subject line Bug#841131: fixed in dump 0.4b46-3
has caused the Debian Bug report #841131,
regarding dump: FTBFS: aclocal-1.14: command not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
841131: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dump
Version: 0.4b46-2
Severity: serious

dump fails to build from source on all architectures with the following
error:

| make[1]: Leaving directory '/«PKGBUILDDIR»'
|    dh_auto_build -a
|   make -j1
| make[1]: Entering directory '/«PKGBUILDDIR»'
| CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /«PKGBUILDDIR»/missing 
aclocal-1.14 -I m4
| /«PKGBUILDDIR»/missing: line 81: aclocal-1.14: command not found
| WARNING: 'aclocal-1.14' is missing on your system.
|  You should only need it if you modified 'acinclude.m4' or
|  'configure.ac' or m4 files included by 'configure.ac'.
|  The 'aclocal' program is part of the GNU Automake package:
|  
|  It also requires GNU Autoconf, GNU m4 and Perl in order to run:
|  
|  
|  
| Makefile:405: recipe for target 'aclocal.m4' failed
| make[1]: *** [aclocal.m4] Error 127
| make[1]: Leaving directory '/«PKGBUILDDIR»'
| dh_auto_build: make -j1 returned exit code 2
| debian/rules:31: recipe for target 'build-arch' failed

You can get a full build log for example there:

https://buildd.debian.org/status/fetch.php?pkg=dump&arch=s390x&ver=0.4b46-2&stamp=1476009177

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: dump
Source-Version: 0.4b46-3

We believe that the bug you reported is fixed in the latest version of
dump, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 841...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Zangerl  (supplier of updated dump package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 20 Oct 2016 19:24:44 +1000
Source: dump
Binary: dump
Architecture: source amd64
Version: 0.4b46-3
Distribution: unstable
Urgency: medium
Maintainer: Alexander Zangerl 
Changed-By: Alexander Zangerl 
Description:
 dump   - 4.4bsd dump and restore for ext2 filesystems
Closes: 841131
Changes:
 dump (0.4b46-3) unstable; urgency=medium
 .
   * updated build rules to ensure a suitable
 automake version is used (closes: #841131)
Checksums-Sha1:
 aa8acd9c8375a8860bc921b479eb6fb371992a86 1973 dump_0.4b46-3.dsc
 946505363e4c6a82bda6b93ad57f419671a75160 20432 dump_0.4b46-3.debian.tar.xz
 5b034e3df012fcffb1cdf9298d921508080034f8 133532 dump_0.4b46-3_amd64.deb
Checksums-Sha256:
 8815cfc0ac807c3249658d3b2f672ad64b73fabc7494f28c22825b2069420fba 1973 
dump_0.4b46-3.dsc
 0232007a2a4cd224c8cd91b09f83fcd719be638397b44697477592fbeb7d7f32 20432 
dump_0.4b46-3.debian.tar.xz
 388ade3da0287698c9b4443743186b90b83edb57deb1b9bf9cab59424104b20a 133532 
dump_0.4b46-3_amd64.deb
Files:
 aff92147d75729a6f2702883f9e3ffab 1973 utils optional dump_0.4b46-3.dsc
 2697d22c225401e3b9338e325bb7b479 20432 utils optional 
dump_0.4b46-3.debian.tar.xz
 97c13ca29383dd2bd2f3ed13c8f4b25f 133532 utils optional dump_0.4b46-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJYCI4UAAoJED06g4g30PqNUy4P/3fRlcuUBvJCZPpXH+gjtPF1
KrlT7LhggB4cYpLfKDduinLTC4W9m0Vtm4yvGwwHhdiGpHiFfAtkf+RstVVDhV6P
v79vIRMNkceYeRsn6z3wqZ7Yi4DpxlBsBwCRGNK+SHF3wcuDsR8FJuyAhbUoNvGy
DBCkcsjTFylceoQwcmK+JRm+X2Fbml7roQJK+lAJZBmQ99rR7SQrJzE6Ho+BvUG1
Xd2WGcM/Cr18tnIcACRnpXI7W15th5m/LGHoQTinrLpzW+m9xBKSBlp8sZuCfjXS
bqI5FJTN0XmgcTBUpZ0Nzti4AW3rHDvWg

Bug#841250: [Pkg-php-pecl] Bug#841250: php-facedetect: FTBFS: error with opencv 3.1

[Mathieu Parent]

2016-10-19 1:37 GMT+02:00 Nobuhiro Iwamatsu :
> Source: php-facedetect
> Version: 1.1.0+git20160406-2
> Severity: important
> Justification: fails to build from source
> Tags: patch
>
> Dear Maintainer,

Hello,

> I am scheduled to transition of opencv.
> This package is target to transition. I tested build with opencv 3.1.
> As a result, this FTBFS with opencv 3.1.
> Because libhighgui-dev and libcv-dev has been removed from opencv 3.1 package.
> We need to use libopencv-dev instead of these package. And currenct
> package disable
> support of opencv 3 by patches/0002-Revert-opencv3-support.patch.

I've local changes that work. The problem is it FTBFS opencv << 3.

Do you have more info on the expected date of fransition?

Regards

-- 
Mathieu

Bug#841421: python-opcua: FTBFS (build hangs)

[Santiago Vila]

Package: src:python-opcua
Version: 0.10.17-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=pybuild --with python2,python3
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python setup.py build 
running build
running build_py

[... snipped ...]

  File "/<>/tests/tests_history.py", line 29, in 
start_server_and_client
cls.srv.start()
  File "./opcua/server/server.py", line 274, in start
self.bserver.start()
  File "./opcua/server/binary_server_asyncio.py", line 97, in start
self._server = self.loop.run_coro_and_wait(coro)
  File "./opcua/common/utils.py", line 189, in run_coro_and_wait
return task.result()
  File "/usr/lib/python2.7/dist-packages/trollius/futures.py", line 285, in 
result
compat.reraise(type(self._exception), self._exception, exc_tb)
  File "/usr/lib/python2.7/dist-packages/trollius/tasks.py", line 259, in _step
result = coro.send(value)
  File "/usr/lib/python2.7/dist-packages/trollius/base_events.py", line 861, in 
create_server
% (sa, err.strerror.lower()))
error: [Errno 98] error while attempting to bind on address ('127.0.0.1', 
48530): address already in use

==
ERROR: setUpClass (tests_server.TestServer)
--
Traceback (most recent call last):
  File "/<>/tests/tests_server.py", line 34, in setUpClass
self.srv.start()
  File "./opcua/server/server.py", line 274, in start
self.bserver.start()
  File "./opcua/server/binary_server_asyncio.py", line 97, in start
self._server = self.loop.run_coro_and_wait(coro)
  File "./opcua/common/utils.py", line 189, in run_coro_and_wait
return task.result()
  File "/usr/lib/python2.7/dist-packages/trollius/futures.py", line 285, in 
result
compat.reraise(type(self._exception), self._exception, exc_tb)
  File "/usr/lib/python2.7/dist-packages/trollius/tasks.py", line 259, in _step
result = coro.send(value)
  File "/usr/lib/python2.7/dist-packages/trollius/base_events.py", line 874, in 
create_server
sock.listen(backlog)
  File "/usr/lib/python2.7/socket.py", line 228, in meth
return getattr(self._sock,name)(*args)
error: [Errno 98] Address already in use

--
Ran 59 tests in 13.396s

FAILED (errors=5, skipped=8)
cryptography is not installed, use of crypto disabled
cryptography is not installed, use of crypto disabled
WARNING: CRYPTO NOT AVAILABLE, CRYPTO TESTS DISABLED!!
make: *** wait: No child processes.  Stop.
make: *** Waiting for unfinished jobs
make: *** wait: No child processes.  Stop.
make[1]: *** wait: No child processes.  Stop.
make[1]: *** Waiting for unfinished jobs
make[1]: *** wait: No child processes.  Stop.
E: Build killed with signal TERM after 60 minutes of inactivity


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

If you could not reproduce this using sbuild on a single CPU virtual machine 
(as I did),
please do not downgrade or mark as unreproducible, I would then consider giving 
you access
to a virtual machine on which I can reproduce it so that you can as well.
(In such case, please contact me off-list for details).

Thanks.

Bug#841286: jison depends on contrib packages (node-ebnf-parser, node-cjson)

[Pirate Praveen]

On Wed, 19 Oct 2016 12:56:08 +0200 Jakub Wilk  wrote:

> This package is in main, but it depends on node-ebnf-parser and node-cjson, 
> which are both in contrib.

These were uploaded in contrib because they were built using jison from
npm (bootstrapping circular dependency). Now new versions of both these
libs are uploaded to main. Once they are accepted into main, I'll close
this bug.



signature.asc
Description: OpenPGP digital signature

Bug#838303: kde-plasma-desktop: KDE does not start after log in

[Maximiliano Curia]

Control: tag -1 + moreinfo

¡Hola Gabor!

El 2016-09-19 a las 16:33 +0100, Gabor Nagy escribió:
Package: kde-plasma-desktop 
Version: 5:91 
Severity: grave 
Justification: renders package unusable



On the 15th of September I have upgraded some packages


It might be useful to know the list of upgraded packages that broke your 
installation, this information can usually be obtained from the 
/var/log/dpkg.log* files.



  * What was the outcome of this action?


Next time when I started this computer, after the sddm login screen when I 
successfully log in, I can see a KDE loading splash screen as expected, but 
after the spalsh screen I see only a blank black screen, with the mouse pointer 
on the left edge. I can move the pointer up and down, but it doesn't move 
horizontally.


From this I would think that this could be a kscreen issue. There are some 
fixes in kscreen included in the plasma 5.8 release (in particular 
https://bugs.kde.org/show_bug.cgi?id=366067), it should be worth checking if 
upgrading your kde installation to plasma 5.8 fixes your desktop.


ii  plasma-desktop4:5.6.5-1 
ii  plasma-workspace  4:5.6.5.1-1 
ii  kwin-x11  4:5.7.0-1 


You had some mixed versions of plasma, given the plugins nature of some plasma 
parts mixing different versions is highly disrecommended, this should be 
prevented with the new packages.


Happy hacking,
--
"Executive ability is deciding quickly and getting somebody else to do the
work."
-- Pollard's Postulate
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Processed: Re: Bug#838303: kde-plasma-desktop: KDE does not start after log in

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #838303 [kde-plasma-desktop] kde-plasma-desktop: KDE does not start after 
log in
Added tag(s) moreinfo.

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

Bug#841352: libnftnl: FTBFS (testsuite error) on Big Endian Architectures

[Arturo Borrero Gonzalez]

On 19 October 2016 at 20:20, Gianfranco Costamagna
 wrote:
> Source: libnftnl
> Version: 1.0.6-2
> Severity: serious
>
> Hi, as you know, the current package is not migrating because of testsuite 
> failures on BE architectures.
>
> Unfortunately I don't have a patch, but in Ubuntu we are excluding them from 
> the testsuite
>

I know, I know.

Currently trying to find some spare time to fix this upstream, but no way.

Thanks for the pseudo-patch, I think I will apply it for now.

best regards.
-- 
Arturo Borrero González

Processed: forcibly merging 826356 830404

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 826356 830404
Bug #826356 [src:ktp-accounts-kcm] ktp-accounts-kcm: FTBFS libaccounts update 
need to fix install files.
Bug #830404 [src:ktp-accounts-kcm] ktp-accounts-kcm: FTBFS: dh_install: missing 
files, aborting
Severity set to 'grave' from 'serious'
Marked as fixed in versions ktp-accounts-kcm/16.04.1-1.
Added tag(s) patch.
Bug #826356 [src:ktp-accounts-kcm] ktp-accounts-kcm: FTBFS libaccounts update 
need to fix install files.
Added tag(s) sid and stretch.
Merged 826356 830404
> thanks
Stopping processing here.

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

Processed: Reassign

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 840853 qemu
Bug #840853 [python-guestfs] FTBFS with QEMU 2.7 - recipe for target 
'quickcheck' failed
Bug reassigned from package 'python-guestfs' to 'qemu'.
No longer marked as found in versions libguestfs/1:1.32.7-1.
Ignoring request to alter fixed versions of bug #840853 to the same values 
previously set
> retitle 840853 qemu 2.7 requires linuxboot_dma.bin but does not provide or 
> depend on it
Bug #840853 [qemu] FTBFS with QEMU 2.7 - recipe for target 'quickcheck' failed
Changed Bug title to 'qemu 2.7 requires linuxboot_dma.bin but does not provide 
or depend on it' from 'FTBFS with QEMU 2.7 - recipe for target 'quickcheck' 
failed'.
> affects 840853 + python-guestfs
Bug #840853 [qemu] qemu 2.7 requires linuxboot_dma.bin but does not provide or 
depend on it
Added indication that 840853 affects python-guestfs
> found 840853 1:2.7+dfsg-1
Bug #840853 [qemu] qemu 2.7 requires linuxboot_dma.bin but does not provide or 
depend on it
Marked as found in versions qemu/1:2.7+dfsg-1.
> thanks
Stopping processing here.

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

Bug#840853: Reassign

[Neil Williams]

reassign 840853 qemu
retitle 840853 qemu 2.7 requires linuxboot_dma.bin but does not provide or 
depend on it
affects 840853 + python-guestfs
found 840853 1:2.7+dfsg-1
thanks

Test scripts using python-guestfs fail with QEMU 2.7, as does the
guestfs tool itself. This appears to be because QEMU 2.7 cannot find
linuxboot_dma.bin in the following command used by guestfs:

/usr/bin/qemu-system-x86_64 \
-global virtio-blk-pci.scsi=off \
-nodefconfig \
-enable-fips \
-nodefaults \
-display none \
-machine accel=kvm:tcg \
-m 500 \
-no-reboot \
-rtc driftfix=slew \
-no-hpet \
-global kvm-pit.lost_tick_policy=discard \
-kernel /var/tmp/.guestfs-1000/appliance.d/kernel \
-initrd /var/tmp/.guestfs-1000/appliance.d/initrd \
-device virtio-scsi-pci,id=scsi \
-drive 
file=/tmp/libguestfsiuwwOX/scratch.1,cache=unsafe,format=raw,id=hd0,if=none \
-device scsi-hd,drive=hd0 \
-drive 
file=/var/tmp/.guestfs-1000/appliance.d/root,snapshot=on,id=appliance,cache=unsafe,if=none,format=raw
 \
-device scsi-hd,drive=appliance \
-device virtio-serial-pci \
-serial stdio \
-device sga \
-chardev socket,path=/tmp/libguestfsiuwwOX/guestfsd.sock,id=channel0 \
-device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \
-append 'panic=1 console=ttyS0 udevtimeout=6000 udev.event-timeout=6000 
no_timer_check lpj=10639240 acpi=off printk.time=1 cgroup_disable=memory 
root=/dev/sdb selinux=0 guestfs_verbose=1 TERM=screen'
Could not access KVM kernel module: No such file or directory
failed to initialize KVM: No such file or directory
Back to tcg accelerator.
Could not open option rom 'linuxboot_dma.bin': No such file or directory
Could not open option rom 'sgabios.bin': No such file or directory

The lack of sgabios.bin does not seem to affect this particular test.

The requirement for linuxboot_dma.bin is specific to QEMU 2.7 and is
not provided by the seabios package (which provides linuxboot_dma.bin).
As a workaround, symlinking linuxboot_dma.bin as linuxboot.bin
in /usr/share/seabios/ allows the guestfs operations to proceed.

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpQ9B2CLV9rC.pgp
Description: OpenPGP digital signature

Bug#834273: marked as done (kmailtransport: FTBFS in testing)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 10:25:34 +
with message-id 
and subject line Bug#834273: fixed in kmailtransport 16.04.2-3
has caused the Debian Bug report #834273,
regarding kmailtransport: FTBFS in testing
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
834273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kmailtransport
Version: 16.04.2-2
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:

--
cd /build/kmailtransport-16.04.2/obj-x86_64-linux-gnu/src && /usr/bin/c++   
-DKCOREADDONS_LIB -DKF5MailTransport_EXPORTS -DQT_CORE_LIB -DQT_DBUS_LIB 
-DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_DEBUG -DQT_NO_URL_CAST_FROM_STRING 
-DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB 
-DQT_XML_LIB -DTRANSLATION_DOMAIN=\"libmailtransport5\" -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE -I/build/kmailtransport-16.04.2/obj-x86_64-linux-gnu/src 
-I/build/kmailtransport-16.04.2/src -isystem /usr/include/KF5/KWallet -isystem 
/usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem 
/usr/include/KF5/AkonadiCore -isystem /usr/include/KF5/KCoreAddons -isystem 
/usr/include/KF5/KItemModels -isystem /usr/include/KF5/KMime -isystem 
/usr/include/KF5/Akonadi/KMime -isystem /usr
 /include/KF5/akonadi/kmime -isystem /usr/include/KF5/KI18n -isystem 
/usr/include/KF5/KIOCore -isystem /usr/include/KF5/KService -isystem 
/usr/include/KF5/KConfigCore -isystem /usr/include/KF5/KConfigGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/KF5/KWidgetsAddons -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
/usr/include/KF5/KAuth -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/KF5/KCompletion  -g -O2 
-fdebug-prefix-map=/build/kmailtransport-16.04.2=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align 
-Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
-Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -pedantic -fPIC 
-fvisibility=hid
 den -fvisibility-inlines-hidden   -DQT_NO_CAST_FROM_ASCII 
-DQT_NO_CAST_TO_ASCII -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -fPIC 
-fexceptions -o CMakeFiles/KF5MailTransport.dir/resourcesendjob.cpp.o -c 
/build/kmailtransport-16.04.2/src/resourcesendjob.cpp
In file included from /usr/include/KF5/AkonadiCore/exception.h:28:0,
 from /usr/include/KF5/AkonadiCore/item.h:26,
 from /build/kmailtransport-16.04.2/src/filteractionjob_p.h:25,
 from /build/kmailtransport-16.04.2/src/outboxactions_p.h:24,
 from /build/kmailtransport-16.04.2/src/outboxactions.cpp:20:
/usr/include/KF5/AkonadiCore/std_exception.h:1:40: fatal error: 
/usr/include/c++/5/exception: No such file or directory
 #include "/usr/include/c++/5/exception"
^
compilation terminated.
--

There are full logs available here:

https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/kmailtransport.html

Thanks.
--- End Message ---
--- Begin Message ---
Source: kmailtransport
Source-Version: 16.04.2-3

We believe that the bug you reported is fixed in the latest version of
kmailtransport, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 834...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated kmailtransport package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 20 Oct 201

Bug#836011: marked as done (akregator: Akregator keep crashing at exit, sometimes do not save recent feeds)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 10:25:21 +
with message-id 
and subject line Bug#836011: fixed in kdepim 4:16.04.3-2
has caused the Debian Bug report #836011,
regarding akregator: Akregator keep crashing at exit, sometimes do not save 
recent feeds
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
836011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: akregator
Version: 4:16.04.3-1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,


   * What led up to the situation?

Since a recent upgrade (less than a month ago). After reading a feed when
closing Akregator it will crash without saving feeds state. The next time it
will load like it didn't fetch any feed.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?

If I remaing in the welcome page I can synchronize without problems, and
Akregator will close correctly.

But If I read a post from a feed or load the list of post in a folder. It will
crash when closing Akregator.


   * What was the outcome of this action?

Run under gdb generates the following stack trace


#0  0x7fffd4079f48 in Akregator::SubscriptionListModel::index(int, int,
QModelIndex const&) const ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#1  0x75dac951 in QTreeView::isRowHidden(int, QModelIndex const&) const
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#2  0x75dac9d7 in QTreeView::isIndexHidden(QModelIndex const&) const ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#3  0x75da831c in QTreeView::visualRegionForSelection(QItemSelection
const&) const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#4  0x75d6b168 in QAbstractItemView::selectionChanged(QItemSelection
const&, QItemSelection const&) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#5  0x75db78da in QTreeView::selectionChanged(QItemSelection const&,
QItemSelection const&) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#6  0x75d70750 in
QAbstractItemView::setSelectionModel(QItemSelectionModel*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x75db5977 in QTreeView::setSelectionModel(QItemSelectionModel*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#8  0x75d6af45 in QAbstractItemView::setModel(QAbstractItemModel*) ()
from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#9  0x75db5724 in QTreeView::setModel(QAbstractItemModel*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#10 0x7fffd407843d in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#11 0x7fffd40918bc in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#12 0x7fffd40bc665 in
Akregator::MainWidget::setFeedList(QSharedPointer const&)
()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#13 0x7fffd40bc7ed in Akregator::MainWidget::slotOnShutdown() ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#14 0x7fffd40b2136 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#15 0x7fffd40b2908 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#16 0x7fffd40b2969 in ?? ()
   from /usr/lib/x86_64-linux-gnu/qt5/plugins/akregatorpart.so
#17 0x74fa6c7c in QMetaObject::activate(QObject*, int, int, void**) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x74f7fa13 in QCoreApplication::exec() ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00408828 in ?? ()
#20 0x743dc700 in __libc_start_main (main=0x4081b0, argc=1,
argv=0x7fffe478, init=, fini=,
rtld_fini=, stack_end=0x7fffe468)
at ../csu/libc-start.c:291
#21 0x00408ac9 in _start ()


   * What outcome did you expect instead?

I'd expect that it didn't crash when closing.




-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages akregator depends on:
ii  kinit5.23.0-1
ii  kio  5.23.0-1
ii  libc62.23-5
ii  libgcc1  1:6.1.1-11
ii  libkf5codecs55.23.0-1
ii  libkf5completion55.23.0-1
ii  libkf5configcor

Bug#840546: CVE-2016-7966 kdepimlibs jessie

[Sandro Knauß]

Hey Moritz,

ping. 

Are there anything missing before rolling out the patch inside jessie-
security? Can I help somehow / are you need input from my side?

Regards,

sandro

--
Am Freitag, 14. Oktober 2016, 21:23:45 CEST schrieb Moritz Muehlenhoff:
> On Fri, Oct 14, 2016 at 08:23:04PM +0200, Sandro Knauß wrote:
> > Hey,
> > 
> > I now back ported the second part of the fix of the CVE. I updated the
> > version deb8u1 from Scott. Should I create a deb8u2 for the additional
> > patch?
> > 
> > I attached the uptodate debdiff.
> 
> Thanks, please upload.
> 
> Cheers,
> Moritz



signature.asc
Description: This is a digitally signed message part.

Processed: A better title for Bug#834683

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 834683
Bug #834683 {Done: Stephan Sürken } [src:mini-buildd] 
mini-buildd: FTBFS too much often (failing tests)
Unarchived Bug 834683
> retitle 834683 mini-buildd: FTBFS, not enough entropy to generate keys
Bug #834683 {Done: Stephan Sürken } [src:mini-buildd] 
mini-buildd: FTBFS too much often (failing tests)
Changed Bug title to 'mini-buildd: FTBFS, not enough entropy to generate keys' 
from 'mini-buildd: FTBFS too much often (failing tests)'.
> thanks
Stopping processing here.

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

Bug#840900: zorp: FTBFS (vector: No such file or directory)

[peter green]

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
A few notes on this bug (note: i'm just a derivative maintainer taking a 
quick look at the bug, not a maintainer of this package)


1. It is not specific to building with dpkg-buildpackage -A [1][2]
2. The actual failure seems to be caused by indirectly including a C++ 
header while building with a plain C compiler.
3. There currently appears to be an (apparently uncoordinated) libzorpll 
transition going on which I suspect may be the trigger for this bug.


[1] 
http://buildd.raspbian.org/status/fetch.php?pkg=zorp&arch=armhf&ver=3.9.5-7.1%2Bb3&stamp=1476485016
[2] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zorp.html

Bug#832649: multi-display is broken (menu and panel appears only on external display)

[Maximiliano Curia]

¡Hola Pirate!

El 2016-09-06 a las 12:52 +0530, Pirate Praveen escribió:
That might be related, sadly, while it claims that's fixed for 5.8, it 
doesn't point to the corresponding commits, so we can only wait for 5.8.


Lets hope that fixes it.


plasma 5.8.2 should be available in archive now. Is this bug still 
reproducible for you with it?



--
Se necesitan voluntarios para dominar el mundo.
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#835753: marked as done (konsole: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Thu, 20 Oct 2016 11:22:57 +0200
with message-id <20161020092257.dwxiiafqpgcc2...@gnuservers.com.ar>
and subject line Re: Bug#835753: konsole: FTBFS: dh_install: missing files, 
aborting
has caused the Debian Bug report #835753,
regarding konsole: FTBFS: dh_install: missing files, aborting
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
835753: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: konsole
Version: 4:16.04.2-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for 'preinstall'.
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.16.04.2
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.16
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so" 
> to ""
> -- Installing: /<>/debian/tmp/usr/bin/konsole
> -- Set runtime path of "/<>/debian/tmp/usr/bin/konsole" to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/konsolepart.so
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/plugins/konsolepart.so"
>  to ""
> -- Installing: /<>/debian/tmp/usr/bin/konsoleprofile
> -- Installing: 
> /<>/debian/tmp/usr/share/konsole/BlackOnLightYellow.colorscheme
> -- Installing: 
> /<>/debian/tmp/usr/share/konsole/BlackOnRandomLight.colorscheme
> -- Installing: 
> /<>/debian/tmp/usr/share/konsole/BlackOnWhite.colorscheme
> -- Installing: 
> /<>/debian/tmp/usr/share/konsole/BlueOnBlack.colorscheme
> -- Installing: 
> /<>/debian/tmp/usr/share/konsole/GreenOnBlack.colorscheme
> -- Installing: 
> /<>/debian/tmp/usr/share/konsole/WhiteOnBlack.colorscheme
> -- Installing: /<>/debian/tmp/usr/share/konsole/Linux.colorscheme
> -- Installing: 
> /<>/debian/tmp/usr/share/konsole/DarkPastels.colorscheme
> -- Installing: 
> /<>/debian/tmp/usr/share/konsole/RedOnBlack.colorscheme
> -- Installing: 
> /<>/debian/tmp/usr/share/konsole/Solarized.colorscheme
> -- Installing: 
> /<>/debian/tmp/usr/share/konsole/SolarizedLight.colorscheme
> -- Installing: /<>/debian/tmp/usr/share/konsole/default.keytab
> -- Installing: /<>/debian/tmp/usr/share/konsole/linux.keytab
> -- Installing: /<>/debian/tmp/usr/share/konsole/solaris.keytab
> -- Installing: /<>/debian/tmp/usr/share/konsole/README.KeyTab
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/org.kde.konsole.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/metainfo/org.kde.konsole.appdata.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/kservicetypes5/terminalemulator.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/konsolepart.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/ServiceMenus/konsolehere.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kservices5/ServiceMenus/konsolerun.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/konsole/konsoleui.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/konsole/sessionui.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/konsole/partui.rc
> -- Installing: 
> /<>/debian/tmp/usr/share/knotifications5/konsole.notifyrc
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/HTML/en/konsole/index.cache.bz2
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/HTML/en/konsole/index.docbook
> -- Installing: 
> /<>/debian/tmp/usr/share/doc/HTML/en/konsole/draganddrop-contextmenu.png
> make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> dh_install  
> dh_install: Cannot find (any matches for) 
> "usr/share/appdata/org.kde.konsole.appdata.xml" (tried in "." and 
> "debian/tmp")
> dh_install: konsole missing files: 
> usr/share/appdata/org.kde.konsole.appdata.xml
> dh_install: missing files, aborting
> /usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: recipe for target 
> 'pre_install_dh_install' failed
> make[1]: *** [pre_install_dh_install] Error 255

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/konsole_16.04.2-1_unstable.log

A list of current common problems and possible solutions is av

Bug#841388: education-tasks and education-menus: error when trying to install together

[Holger Levsen]

Hi Ralf,

thanks for your timely bugreport, much appreciated!

On Thu, Oct 20, 2016 at 08:10:05AM +0200, Ralf Treinen wrote:
> Package: education-menus,education-tasks
> Version: education-menus/1.911
> Version: education-tasks'1.911@all, education-tasks/1.910
[...]
> Unpacking education-tasks (1.911) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/education-tasks_1.911_all.deb (--unpack):
>  trying to overwrite '/usr/share/tasksel/descs/debian-edu-tasks.desc', which 
> is also in package education-menus 1.911

wow. I'm surprised this didnt happen with 1.910 or before, because
education-tasks and education-menus both come from src:debian-edu and 
the only relevant change in 1.911 was moving the education-tasks binary
package from arch:any to arch:all. (The other changes just changed some
depends relationships.)

I'll look into this ASAP.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#841394: filters: FTBFS: relocation R_X86_64_PC32 against symbol `exit@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC

[Chris Lamb]

Source: filters
Version: 2.55-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

filters fails to build from source in unstable/amd64:

  […]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  filters
   Version:  2.55-1
   Build architecture:   amd64
   Date: Thu, 20 Oct 2016 10:02:51 +0200
   Hostname: 62b37bf9441f
   Uname:Linux 62b37bf9441f 4.7.0-1-amd64 #1 SMP Debian 4.7.5-1 
(2016-09-26) x86_64 GNU/Linux
   /etc/timezone:Europe/Belgrade
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'filters-build-deps' in 
'../filters-build-deps_2.55-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package filters-build-deps.
  (Reading database ... 23456 files and directories currently installed.)
  Preparing to unpack filters-build-deps_2.55-1_all.deb ...
  Unpacking filters-build-deps (2.55-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
bison flex libbison-dev libfl-dev
  Suggested packages:
bison-doc
  The following NEW packages will be installed:
bison flex libbison-dev libfl-dev
  0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 1733 kB of archives.
  After this operation, 3782 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 libfl-dev amd64 
2.6.1-1 [92.5 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 flex amd64 2.6.1-1 
[428 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libbison-dev amd64 
2:3.0.4.dfsg-1 [432 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 bison amd64 
2:3.0.4.dfsg-1 [780 kB]
  Fetched 1733 kB in 0s (44.4 MB/s)
  Selecting previously unselected package libfl-dev:amd64.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23460 files and directories currently installed.)
  Preparing to unpack .../0-libfl-dev_2.6.1-1_amd64.deb ...
  Unpacking libfl-dev:amd64 (2.6.1-1) ...
  Selecting previously unselected package flex.
  Preparing to unpack .../1-flex_2.6.1-1_amd64.deb ...
  Unpacking flex (2.6.1-1) ...
  Selecting previously unselected package libbison-dev:amd64.
  Preparing to unpack .../2-libbison-dev_2%3a3.0.4.dfsg-1_amd64.deb ...
  Unpacking libbison-dev:amd64 (2:3.0.4.dfsg-1) ...
  Selecting previously unselected package bison.
  Preparing to unpack .../3-bison_2%3a3.0.4.dfsg-1_amd64.deb ...
  Unpacking bison (2:3.0.4.dfsg-1) ...
  Setting up libfl-dev:amd64 (2.6.1-1) ...
  Processing triggers for libc-bin (2.24-5) ...
  Setting up libbison-dev:amd64 (2:3.0.4.dfsg-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up bison (2:3.0.4.dfsg-1) ...
  update-alternatives: using /usr/bin/bison.yacc to provide /usr/bin/yacc 
(yacc) in auto mode
  Setting up flex (2.6.1-1) ...
  Setting up filters-build-deps (2.55-1) ...
  
  
**
  ** Environment
  **
  
**
  
  
PATH=/home/lamby/git/projects/dotfiles/dotfiles/..//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
  HOSTNAME=62b37bf9441f
  TERM=xterm
  PAGER=more
  DISPLAY=:0
  DOCKER_IMAGE=lamby-debian-sid
  DEB_BUILD_OPT

Bug#822379: char : signed / unsigned

[Mathieu Malaterre]

It is funny that the test fails only on arch where 'char' is unsigned

Bug#841343: rakudo: FTBFS on arm64, powerpc and ppc64 - testsuite errors

[Dominique Dumont]

On Wednesday, 19 October 2016 17:36:25 CEST James Cowgill wrote:
> rakudo FTBFS on arm64, powerpc and ppc64 with errors in the testsuite.
> 
> arm64 times out during the 't/04-nativecall/02-simple-args.t' test.

Yes, see https://github.com/MoarVM/MoarVM/issues/428
and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841354

We'll handle powerpc and ppc64 once all arm arches are fine.

All the best

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#825379:

[Mohammed Sadiq]

Ping. I wish this to be in Debian Stretch. Thanks.