Bug#838266: Salvaging pylibtiff to Debian Python team or removing it from Debian?

[Maximiliano Curia]

¡Hola Andreas!

El 2016-10-21 a las 09:36 +0200, Andreas Tille escribió:
the former maintainer of pylibtiff inside Debian Med team Mathieu 
Malaterre does not care for the package any more and thus I tried 
my luck to salvage it.  I have no personal interest in this package 
nor does it have any rdepends.  There is no direct connection to 
the Debian Med topic but since there are some users according to 
popcon[1] it might be worth saving.


I won't be able to work on this in the foreseeable future, but I can probably 
help with the mentioned errors.


 File "/usr/lib/python2.7/dist-packages/libtiff/libtiff_ctypes.py", line 36 
   print 'You should add %r to PATH environment variable and reboot.' % (os.path.dirname (lib)) 
^ 
SyntaxError: invalid syntax


This looks valid, but probably fails if using:
from __future__ import print_function
you can probably fix this by adding the parenthesis needed for the function 
invocation:

print('You should add %r to PATH environment variable and reboot.' % 
(os.path.dirname (lib)))

 File "/usr/lib/python2.7/dist-packages/libtiff/optparse_gui.py", line 201 
   print(msg, file=sys.stderr) 
  ^ 
SyntaxError: invalid syntax


This is probably failing because of a missing:
from __future__ import print_function
at the beginning of the file (it needs to be added before any other import).

In python2 print is a statement that you use as print "Hi", in python3 it's a
function that you use as print("Hi"), using the __future__ snippet you can use 
(in python 2.7) print as a function, this is generally a good idea as it eases 
the migration to python3 process.


Happy hacking,
--
"If you have too many special cases, you are doing it wrong." -- Craig Zarouni
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Processed: found 841665 in 7.6.33+dfsg-1

[Debian Bug Tracking System]

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

> # do not mark only in bpo version ...
> found 841665 7.6.33+dfsg-1
Bug #841665 [boinc-client] boinc-client: The boinc-client init script has a 
badly constructed parameter for xhost
Marked as found in versions boinc/7.6.33+dfsg-1.
> thanks
Stopping processing here.

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

Bug#837820: marked as done (libiptcdata: FTBFS due to undeclared build dependencies)

[Debian Bug Tracking System]

Your message dated Sat, 22 Oct 2016 05:30:40 +
with message-id 
and subject line Bug#837820: fixed in libiptcdata 1.0.4-6
has caused the Debian Bug report #837820,
regarding libiptcdata: FTBFS due to undeclared build dependencies
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.)


-- 
837820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libiptcdata
Version: 1.0.4-4
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk-doc-tools

Hi,

your package libiptcdata declares a build dependency on gtk-doc-tools.
gtk-doc-tools in turn depends on gnome-common, which in turn pulls in packages
like gettext, intltool or pkg-config.

The dependency on gnome-common was originally added for the GNOME_GTKDOC_CHECK
macro which has been deprecated and replaced by GTK_DOC_CHECK a long time ago.

As gnome-common has been declared deprecated by GNOME upstream [1], we would
like to drop this dependency from gtk-doc-tools.

We did a test of all reverse build dependencies of gtk-doc-tools and libiptcdata
failed to build due to now missing build dependencies which are no longer
pulled in by gtk-doc-tools.

A complete build log is available at
https://people.debian.org/~biebl/gtk-doc-tools/libiptcdata.log

We have uploaded that gtk-doc-tools package as 1.25-4 to experimental as well,
so you can test your package against this version.

Common build-failures and their fixes:

a/ configure.ac:32: error: possibly undefined macro: AC_PROG_INTLTOOL

   make[1]: intltoolize: Command not found

   → Build-Depends: intltool

b/ ./configure: line 5461: syntax error near unexpected token `yes'
   ./configure: line 5461: `GNOME_COMPILE_WARNINGS(yes)'

   ./configure: line 14801: GNOME_CODE_COVERAGE: command not found

   → Build-Depends: gnome-common (for GNOME_* macros)

c/ ./configure: line 17439: syntax error near unexpected token 
`$WARN_CFLAGS_EXTRA,'
   ./configure: line 17439: `AX_APPEND_COMPILE_FLAGS($WARN_CFLAGS_EXTRA, 
WARN_CFLAGS)'

   ./configure: line 2629: syntax error near unexpected token `git-directory'
   ./configure: line 2629: `AX_IS_RELEASE(git-directory)'

   → Build-Depends: autoconf-archive (for AX_* macros)

d/ ./configure: line 12518: intltool-update: command not found
   checking for intltool >= 0.40.0...  found
   ./configure: error: Your intltool is too old.  You need intltool 0.40.0 or 
later.

   → Build-Depends: intltool

e/ make[1]: intltoolize: Command not found

   → Build-Depends: intltool

f/ ./autogen.sh calls gnome-autogen.sh

   → Build-Depends: gnome-common


Please add the required build-dependencies to your package so once we upload
gtk-doc-tools_1.25-4 to unstable your package doesn't FTBFS.

Regards,
Michael


[1] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
Source: libiptcdata
Source-Version: 1.0.4-6

We believe that the bug you reported is fixed in the latest version of
libiptcdata, 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 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ian Wienand  (supplier of updated libiptcdata 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: Sat, 22 Oct 2016 13:01:07 +1100
Source: libiptcdata
Binary: libiptcdata0-dev libiptcdata0-dbg libiptcdata-doc libiptcdata-bin 
libiptcdata0 python-iptcdata
Architecture: source amd64 all
Version: 1.0.4-6
Distribution: unstable
Urgency: medium
Maintainer: Ian Wienand 
Changed-By: Ian Wienand 
Description:
 libiptcdata-bin - Library to parse IPTC metadata (programs)
 libiptcdata-doc - Library to parse IPTC metadata (documentation)
 libiptcdata0 - Library to parse IPTC metadata
 libiptcdata0-dbg - Library to parse IPTC metadata (debug files)
 libiptcdata0-dev - Library to parse IPTC metadata (development files)
 python-iptcdata - Python bindings for the iptcdata library
Closes: 837820
Changes:
 libiptcdata (1.0.4-6) unstable; urgency=medium
 .
   * Update build dependencies 

Processed: tagging 841508

[Debian Bug Tracking System]

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

> tags 841508 + pending
Bug #841508 [dia] dia: fails to upgrade from 'jessie' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/dia/libaadl_objects.so
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841628: marked as done (gitano: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sat, 22 Oct 2016 05:28:51 +
with message-id <e1bxort-00082k...@franck.debian.org>
and subject line Bug#841628: fixed in gitano 0.1-2
has caused the Debian Bug report #841628,
regarding gitano: FTBFS: Tests failures
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.)


-- 
841628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitano
Version: 0.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> Running step "GIVEN a standard instance"
> Running step "WHEN testinstance adminkey runs config gitano-admin set 
> project.archived true"
> Running step "THEN server-side gitano-admin.git file cgitrc contains 
> hide=1"
> Running scenario Pushing shallow history
> DATADIR is /tmp/tmprTY8Oy/Pushing_shallow_history/datadir
> HOME for tests is /tmp/tmprTY8Oy/Pushing_shallow_history/datadir/HOME
> Running step "GIVEN a standard instance"
> Running step "WHEN testinstance, using adminkey, clones gitano-admin.git 
> as local-shallow with depth 1"
> Running step "WHEN testinstance adminkey runs create remote-shallow.git"
> Running step "WHEN testinstance adminkey runs config remote-shallow.git 
> set git.receive.shallowUpdate true"
> Running step "WHEN testinstance, using adminkey, pushes local-shallow to 
> remote-shallow.git"
> Running step "THEN server-side remote-shallow.git file shallow exists"
> Failed scenarios:
> - Keyrings can gain and lose keys
> ERROR: Test suite FAILED in 1 scenarios
> Makefile:183: recipe for target 'test' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/gitano_0.1-1_unstable.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: gitano
Source-Version: 0.1-2

We believe that the bug you reported is fixed in the latest version of
gitano, 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.
Daniel Silverstone <dsilv...@digital-scurf.org> (supplier of updated gitano 
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: Sat, 22 Oct 2016 10:48:55 +0900
Source: gitano
Binary: gitano
Architecture: source all
Version: 0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Daniel Silverstone <dsilv...@digital-scurf.org>
Changed-By: Daniel Silverstone <dsilv...@digital-scurf.org>
Description:
 gitano - Git service manager
Closes: 841628
Changes:
 gitano (0.1-2) unstable; urgency=medium
 .
   * Add gnupg to Build-Depends and Depends. (Closes: #841628)
Checksums-Sha1:
 b14be4b5cc342e561e6ac5c00d775ba4207458e8 1482 gitano_0.1-2.dsc
 aa39296596af6ceabe659dadc760041d75b37d18 2556 gitano_0.1-2.debian.tar.xz
 6f571f6b66243228860a45af33ff3a92286080e5 58072 gitano_0.1-2_all.deb
Checksums-Sha256:
 ae6f6d739e43032cbad8a74e7f53d6238dd06f9585037330d3301c1c11af225b 1482 
gita

Bug#837420: Bug#835148: please do not make GCC incompatible, we have dpkg-buildflags for this! (was Re: Bug#837420: Processed: PIE FTBFS are now RC)

[Christian Seiler]

On 10/22/2016 01:00 AM, Thorsten Glaser wrote:
> Bálint Réczey dixit:
> 
>> AFAIK the linux package is the only problematic package were the
>> maintainer refused to disable PIE from packaging scripts.
> 
> So, how are you supposed to do that now, instead of filtering
> -fPIE from CFLAGS and -pie from LDFLAGS?
> 
> Christian/zumbi: do you take care of dietlibc, or should I?

Yes, I fully intend to fix that - which is why I tagged the bug
report "confirmed" when it was first reported, even while it
was still of lower severity. I just had a lot of other stuff
come up and didn't get to it yet. I had actually planned to
take some time on Sunday for this, even before the severity of
this bug was bumped.

Also, I'd really appreciate it if you talked to me and zumbi
first before escalating the bug report and asking for a revert
of archive-wide changes in the name of the dietlibc package.
Because from my perspective I'm in favor of the change (hence
the "confirmed" on the bug when it was first reported, and I
did follow the threads on debian-devel related to this) and we
could have had this discussion amongst ourselves without
involving the gcc maintainers, who probably have to deal with
enough things already. Many thanks.

Regards,
Christian

Bug#841548: Processed: Re: Bug#841548: autopkgtest: FTBFS: Tests failures

[Changwoo Ryu]

It happens to me when upgrading imagemagick from 6.8.9.9-7.2+b1 to
6.9.6.2+dfsg-2.

Processed: set owner

[Debian Bug Tracking System]

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

> owner 841548 !
Bug #841548 [python3-wand] autopkgtest: FTBFS: Tests failures
Bug #841653 [python3-wand] Importing wand.image fails
Owner recorded as Changwoo Ryu .
Owner recorded as Changwoo Ryu .
> thanks
Stopping processing here.

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

Bug#841665: boinc-client: The boinc-client init script has a badly constructed parameter for xhost

[Preston Maness]

Howdy,

So far as I know, the systemd init system uses the .service file, which
doesn't use the old boinc init script:

/etc/systemd/system/multi-user.target.wants/boinc-client.service

The current method for granting access to the Xserver for boinc is to
drop a file here:

/etc/X11/Xsession.d/36x11-common_xhost-boinc

which does follow the recommended xhost command format:

```
BOINC_USER=boinc

if type xhost >/dev/null 2>&1; then
  id -u $BOINC_USER >/dev/null 2>&1 && xhost +SI:localuser:$BOINC_USER || :
fi
```

That file is sourced and ran whenever a display manager invokes an Xorg
session. On my machine with systemd, this is my xhost output:

```
$ xhost
access control enabled, only authorized clients can connect
SI:localuser:boinc
SI:localuser:preston
$
```

I'm guessing that non-systemd users are probably still using the init
script though, so we should still address this in any case.

Cheers,

Preston Maness

On 10/21/2016 03:42 PM, Mike Brennan wrote:
> Package: boinc-client
> Version: 7.6.33+dfsg-1~bpo8+1
> Severity: grave
> Tags: security
> Justification: user security hole
> 
> Dear Maintainers,
> 
> boinc-client shell script is used by init/systemd to start the boinc client 
> daemon (typically running as user=boinc)
> 
> In order for boinc to access GPU hardware -  xhost is used to grant access to 
> boinc.
> 
> At line 109-110
> ---
> # grant the boinc client to perform GPU computing
>xhost local:boinc || echo -n "xhost error ignored, GPU computing may 
> not be possible"
> 
> 
> the correct syntax stould be 
>xhost +si:localuser:boinc
> or more correctly for the this script
>xhost +si:localuser:$BOINC_USER
> 
> The impact of using this incorrect syntax - is not to error, but grant ALL 
> local users access.  
> (This could be a very old or different maybe BSD syntax)
> 
> The intention of the script to grant ONLY user=boinc access, instead all 
> local users have access.
> 
> For example a little test.
> 
> agentb@dejon:/etc/init.d$ xhost
> access control enabled, only authorized clients can connect
> SI:localuser:agentb
> 
> agentb@dejon:/etc/init.d$ xhost local:random-string
> non-network local connections being added to access control list
> 
> agentb@dejon:/etc/init.d$ xhost
> access control enabled, only authorized clients can connect
> LOCAL:
> SI:localuser:boinc
> SI:localuser:agentb
> 
> Hope this is clear, and thank you for maintaining boinc!
> 
> Cheers
> Mike
> 
> 
> -- Package-specific info:
> -- Contents of /etc/default/boinc-client:
> # This file is /etc/default/boinc-client, it is a configuration file for the
> # /etc/init.d/boinc-client init script.
> 
> # Set this to 1 to enable and to 0 to disable the init script.
> ENABLED="1"
> 
> # Set this to 1 to enable advanced scheduling of the BOINC core client and
> # all its sub-processes (reduces the impact of BOINC on the system's
> # performance).
> SCHEDULE="1"
> 
> # The BOINC core client will be started with the permissions of this user.
> BOINC_USER="boinc"
> 
> # This is the data directory of the BOINC core client.
> BOINC_DIR="/var/lib/boinc-client"
> 
> # This is the location of the BOINC core client, that the init script uses.
> # If you do not want to use the client program provided by the boinc-client
> # package, you can specify here an alternative client program.
> #BOINC_CLIENT="/usr/local/bin/boinc"
> BOINC_CLIENT="/usr/bin/boinc"
> 
> # Here you can specify additional options to pass to the BOINC core client.
> # Type 'boinc --help' or 'man boinc' for a full summary of allowed options.
> #BOINC_OPTS="--allow_remote_gui_rpc"
> BOINC_OPTS=""
> 
> # Scheduling options
> 
> # Set SCHEDULE="0" if prefering to run with upstream default priority
> # settings.
> 
> # Nice levels. When systems are truly busy, e.g. because of too many active
> # scientific applications started by the boinc client, there is a chance for
> # the boinc client not to be granted sufficient opportunity to check for
> # scientific applications to be alive and make the (wrong) decision to
> # terminate the scientific app. This is particularly an issue with many
> # apps started in parallel on modern multi-core systems and extra overheads
> # for the download and uploads of files with the project servers. Another
> # concern is the latency for scientific applications to communicate with the
> # graphics card, which should be low. All such values should be set and
> # controled from within the BOINC client. The Debian init script also sets
> # extra constrains via chrt on real time performance and via ionice on 
> # I/O performance, which is beyond the regular BOINC client. It then was
> # too easy to use that code to also constrain minimal nice levels. We still
> # think about how to best distinguish GPU applications from regular apps.
> 

Bug#837562: marked as done (libembperl-perl: FTBFS with bindnow and PIE enabled)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 23:57:24 +
with message-id 
and subject line Bug#837562: fixed in libembperl-perl 2.5.0-9
has caused the Debian Bug report #837562,
regarding libembperl-perl: FTBFS with bindnow and PIE enabled
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.)


-- 
837562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libembperl-perl
Version: 2.5.0-8
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: FTBFS on amd64 with extra hardening

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64 with patched GCC and dpkg.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64.

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part (hopefully):
...
Writing Embperl.bs
chmod 644 "Embperl.bs"
PERL_DL_NONLAZY=0 PERL_USE_UNSAFE_INC=1 "/usr/bin/perl" "-Iblib/lib"
"-Iblib/arch" test.pl
loading...Can't load
'/<>/blib/arch/auto/Embperl/Embperl.so' for module Embperl:
/<>/blib/arch/auto/Embperl/Embperl.so: undefined symbol:
ap_hook_open_logs at /usr/lib/x86_64-linux-gnu/perl/5.22/DynaLoader.pm
line 187.
 at test.pl line 1916.
Compilation failed in require at test.pl line 1916.
BEGIN failed--compilation aborted at test.pl line 1916.

Test terminated with fatal error
Use of uninitialized value $EPHTTPD in string ne at test.pl line 1300.
Makefile:1619: recipe for target 'test_dynamic' failed
make[1]: *** [test_dynamic] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/libembperl-perl_2.5.0-8_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Source: libembperl-perl
Source-Version: 2.5.0-9

We believe that the bug you reported is fixed in the latest version of
libembperl-perl, 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 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Florian Schlichting  (supplier of updated libembperl-perl 
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: Sat, 22 Oct 2016 00:44:25 +0200
Source: libembperl-perl
Binary: libembperl-perl
Architecture: source amd64
Version: 2.5.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Florian Schlichting 
Description:
 libembperl-perl - system for building dynamic websites with Perl
Closes: 837562
Changes:
 libembperl-perl (2.5.0-9) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Remove Jonathan Yu from Uploaders. Thanks for your work!
 .
   [ Florian Schlichting ]
   * Opt out of bindow (closes: #837562)
   * Override bindnow lintian tag
   * Fix all spelling mistakes lintian noticed
Checksums-Sha1:
 24d99add71ac1c935328e7388680ed03513db3a3 2247 libembperl-perl_2.5.0-9.dsc
 5745e2c3fed1f543534ec208e87703d066ef6ec6 27588 
libembperl-perl_2.5.0-9.debian.tar.xz
 84d9f4fa7bd647a05104800f9d56065651d665b9 1064624 
libembperl-perl-dbgsym_2.5.0-9_amd64.deb
 a19f04d4b6e84a97696d433171719e8e9f6fee3c 748896 
libembperl-perl_2.5.0-9_amd64.deb
Checksums-Sha256:
 1de240aa939d5de8d70c9f65835bc5ed645e5bf980b96e33c690f51e61bd377c 2247 
libembperl-perl_2.5.0-9.dsc
 21270fcc7b30c7b0281af0f11296e576d7943332a590ddf7cbfeca6fe06da7ce 27588 
libembperl-perl_2.5.0-9.debian.tar.xz
 5c1f256de9ce1ccd3ecd3ad8f7ab121390cc3664e8b652ac946806a3bbd061f3 1064624 
libembperl-perl-dbgsym_2.5.0-9_amd64.deb
 181e985899648a7945f92f03c0b0ad1406dbf1aaf1b0302862b280c2151dcbb0 748896 
libembperl-perl_2.5.0-9_amd64.deb
Files:
 872ed2855ecf308aee96a7e3c30e5149 2247 perl optional libembperl-perl_2.5.0-9.dsc
 d59ee2140087fce79290ce28f76823de 27588 perl optional 
libembperl-perl_2.5.0-9.debian.tar.xz
 6fcb448c05a986f55e31469ea2c487a8 1064624 debug 

Bug#839522: marked as done (ruby-roadie-rails: FTBFS: ERROR: Test "ruby2.3" failed: RuntimeError:)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 21:51:35 -0200
with message-id <20161021235135.5fdrjouffqqgi...@debian.org>
and subject line Re: Bug#839522: ruby-roadie-rails: FTBFS: ERROR: Test 
"ruby2.3" failed: RuntimeError:
has caused the Debian Bug report #839522,
regarding ruby-roadie-rails: FTBFS: ERROR: Test "ruby2.3" failed: RuntimeError:
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.)


-- 
839522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-roadie-rails
Version: 1.1.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 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):
>  RuntimeError:
>No output present. Did the application crash?
>  # ./spec/support/rails_app.rb:35:in `read_providers'
>  # ./spec/integration_spec.rb:77:in `block (4 levels) in '
> 
> Finished in 5.6 seconds (files took 0.66281 seconds to load)
> 105 examples, 5 failures
> 
> Failed examples:
> 
> rspec ./spec/integration_spec.rb:48 # Integrations with Rails 4.2.x inlines 
> styles for multipart emails
> rspec ./spec/integration_spec.rb:52 # Integrations with Rails 4.2.x 
> automatically inlines styles with automatic mailer
> rspec ./spec/integration_spec.rb:56 # Integrations with Rails 4.2.x 
> automatically inlines styles with automatic mailer and forced delivery
> rspec ./spec/integration_spec.rb:60 # Integrations with Rails 4.2.x inlines 
> no styles when roadie_options are nil
> rspec ./spec/integration_spec.rb:76 # Integrations with Rails 4.2.x has a 
> AssetPipelineProvider together with a FilesystemProvider
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation failed
> ERROR: Test "ruby2.3" failed: 

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/01/ruby-roadie-rails_1.1.0-1_unstable.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 ---
On Sat, Oct 01, 2016 at 04:19:18PM +0200, Lucas Nussbaum wrote:
> Source: ruby-roadie-rails
> Version: 1.1.0-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161001 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):
> >  RuntimeError:
> >No output present. Did the application crash?
> >  # ./spec/support/rails_app.rb:35:in `read_providers'
> >  # ./spec/integration_spec.rb:77:in `block (4 levels) in  > (required)>'
> > 
> > Finished in 5.6 seconds (files took 0.66281 seconds to load)
> > 105 examples, 5 failures
> > 
> > Failed examples:
> > 
> > rspec ./spec/integration_spec.rb:48 # Integrations with Rails 4.2.x inlines 
> > styles for multipart emails
> > rspec ./spec/integration_spec.rb:52 # Integrations with Rails 4.2.x 
> > automatically inlines styles with automatic mailer
> > rspec ./spec/integration_spec.rb:56 # Integrations with Rails 4.2.x 
> > automatically inlines styles with automatic mailer and forced delivery
> > rspec ./spec/integration_spec.rb:60 # Integrations with Rails 4.2.x inlines 
> > no styles when roadie_options are nil
> > rspec ./spec/integration_spec.rb:76 # Integrations with Rails 4.2.x has a 
> > AssetPipelineProvider together with a FilesystemProvider
> > 
> > /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> > documentation failed
> > ERROR: Test "ruby2.3" failed: 
> 
> If the failure looks somehow time/timezone related:
> Note that this rebuild was performed without the 'tzdata' package
> installed 

Bug#837562: Pending fixes for bugs in the libembperl-perl package

[pkg-perl-maintainers]

tag 837562 + pending
thanks

Some bugs in the libembperl-perl package are closed in revision
541b0e9c6d9f88c7ca1929866d2e7effd13c388f in branch 'master' by
Florian Schlichting

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libembperl-perl.git/commit/?id=541b0e9

Commit message:

Opt out of bindow (closes: #837562)

quoting Niko from the bug:

My understanding is that the Apache module parts (mod_embperl) get
compiled into Embperl.so, but don't get used unless the thing is loaded
by Apache. The 'bindnow' hardening is incompatible with this scheme;
from the ld(1) documentation for '-z now':

  When generating an executable or shared library, mark it to tell the
  dynamic linker to resolve all symbols when the program is started, or
  when the shared library is linked to using dlopen, instead of deferring
  function call resolution to the point when the function is first called.

So when perl dlopens Embperl.so without Apache, the ap_* functions
aren't needed but still get loaded (unsuccessfully).

Processed: Pending fixes for bugs in the libembperl-perl package

[Debian Bug Tracking System]

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

> tag 837562 + pending
Bug #837562 [src:libembperl-perl] libembperl-perl: FTBFS with bindnow and PIE 
enabled
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837420: Bug#835148: please do not make GCC incompatible, we have dpkg-buildflags for this! (was Re: Bug#837420: Processed: PIE FTBFS are now RC)

[Bálint Réczey]

Hi,

2016-10-22 1:00 GMT+02:00 Thorsten Glaser :
> Bálint Réczey dixit:
>
>>AFAIK the linux package is the only problematic package were the
>>maintainer refused to disable PIE from packaging scripts.
>
> So, how are you supposed to do that now, instead of filtering
> -fPIE from CFLAGS and -pie from LDFLAGS?

This reverts defaulting to no-PIE:
CC = $(CC) -no-pie
LD = $(LD) -no-pie

Very often appending -no-pie works, too, but not when compiling shared
libraries.
See:  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77464

If you show the FTBFS you are facing I can help more.

Cheers,
Balint

>
> Christian/zumbi: do you take care of dietlibc, or should I?
>
> Thanks,
> //mirabilos
> --
> Stéphane, I actually don’t block Googlemail, they’re just too utterly
> stupid to successfully deliver to me (or anyone else using Greylisting
> and not whitelisting their ranges). Same for a few other providers such
> as Hotmail. Some spammers (Yahoo) I do block.

Bug#725417: Thanks a lot

[James Cowgill]

Hi,

On 21/10/16 22:36, Santiago Garcia Mantinan wrote:
> Hi!
> 
> I've been preparing a new version of mbr which will change the format and
> not overwrite the disk-id, but I have not finished yet and I don't have time
> lately, so your upload is very welcome.

Great!

If you want, I could reschedule my NMU to skip the delayed queue and go
straight in (I doubt it would make too much difference though).

James



signature.asc
Description: OpenPGP digital signature

Bug#841252: marked as done (libtk-filedialog-perl: Control-W is deprecated in $W variable, needs to be changed to $^W with literal ^ character)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 23:06:15 +
with message-id 
and subject line Bug#841252: fixed in libtk-filedialog-perl 1.3-5
has caused the Debian Bug report #841252,
regarding libtk-filedialog-perl: Control-W is deprecated in $W variable, needs 
to be changed to $^W with literal ^ character
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.)


-- 
841252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtk-filedialog-perl
Version: 1.3-4
Severity: normal

Dear Maintainer,

When starting the "athena" program (from the horae package), the following 
error appears

Unrecognized character \x17; marked by <-- HERE after nSave) = $<-- HERE
near column 22 at /usr/share/perl5/Tk/FileDialog.pm line 610.
at /usr/lib/x86_64-linux-gnu/perl5/5.24/Tk/widgets.pm line 14.
Compilation failed in require at
/usr/lib/x86_64-linux-gnu/perl5/5.24/Tk/widgets.pm line 14.
at /usr/bin/athena line 76.
BEGIN failed--compilation aborted at /usr/bin/athena line 82.

It turns out that this is because of code in /usr/share/perl5/Tk/FileDialog.pm
which appears close to line 604:

  PRIVATE METHODS AND SUBROUTINES 
sub IsNum {
my($parm) = @_;
my($warnSave) = $^W;
$^W = 0;
my($res) = (($parm + 0) eq $parm);
$^W = $warnSave;
return $res;
}

The character "^W" is actually the single character Control-W instead of the 
"^" character followed by "W".  This use is deprecated and can be fixed by 
replacing the Control-W in the three lines above. 

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

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

Versions of packages libtk-filedialog-perl depends on:
ii  perl 5.24.1~rc3-3
ii  perl-tk  1:804.033-1+b3

libtk-filedialog-perl recommends no packages.

libtk-filedialog-perl suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libtk-filedialog-perl
Source-Version: 1.3-5

We believe that the bug you reported is fixed in the latest version of
libtk-filedialog-perl, 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.
Florian Schlichting  (supplier of updated 
libtk-filedialog-perl 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: Fri, 21 Oct 2016 23:18:37 +0200
Source: libtk-filedialog-perl
Binary: libtk-filedialog-perl
Architecture: source all
Version: 1.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Florian Schlichting 
Description:
 libtk-filedialog-perl - highly configurable file dialog widget for Perl/Tk
Closes: 841252
Changes:
 libtk-filedialog-perl (1.3-5) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * debian/copyright: Replace DEP5 Format-Specification URL from
 svn.debian.org to anonscm.debian.org URL.
   * Change Vcs-Git to canonical URI (git://anonscm.debian.org)
   * Change search.cpan.org based URIs to metacpan.org based URIs
 .
   [ Axel Beckert ]
   * debian/copyright: migrate pre-1.0 format to 1.0 using "cme fix dpkg-
 copyright"
 .
   [ gregor herrmann ]
   * Strip trailing slash from metacpan URLs.
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * Change bugtracker URL(s) to HTTPS.
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Remove Jay Bonci from Uploaders. Thanks for your work!
   * Remove Tim Retout from Uploaders. Thanks for your work!
 .
   [ Florian Schlichting ]
   * Add test.patch for basic usage testing
   * Add unrecognized_character_x17.patch (closes: #841252)
   * Bump dh compat to level 9
   * 

Bug#841627: marked as done (psi: FTBFS: Verifying Qt build environment ... ./configure: 316: ./configure: Bad substitution)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 23:07:59 +
with message-id <e1bxiut-0002zy...@franck.debian.org>
and subject line Bug#841627: fixed in psi 0.15-3
has caused the Debian Bug report #841627,
regarding psi: FTBFS: Verifying Qt build environment ... ./configure: 316: 
./configure: Bad substitution
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.)


-- 
841627: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841627
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psi
Version: 0.15-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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[1]: Entering directory '/<>'
> qt-qconf
> Project name: Psi
> Profile: psi.pro
> Deps: qt4* buildmodeapp* qca* zlib* x11* universal qdbus growl whiteboarding 
> xss aspell enchant spell* conf* recursiveprl*
> 
> 'configure' written.
> 'configure.exe' written.
> ./configure --prefix=/usr --qtdir=/usr/share/qt4/ --no-separate-debug-info # 
> --enable-debug
> Configuring Psi ...
> Verifying Qt build environment ... ./configure: 316: ./configure: Bad 
> substitution
> debian/rules:13: recipe for target 'override_dh_auto_configure' failed
> make[1]: *** [override_dh_auto_configure] Error 2

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/psi_0.15-2_unstable.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: psi
Source-Version: 0.15-3

We believe that the bug you reported is fixed in the latest version of
psi, 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.
Jan Niehusmann <j...@debian.org> (supplier of updated psi 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: Fri, 21 Oct 2016 22:21:01 +0200
Source: psi
Binary: psi
Architecture: source
Version: 0.15-3
Distribution: unstable
Urgency: low
Maintainer: Jan Niehusmann <j...@debian.org>
Changed-By: Jan Niehusmann <j...@debian.org>
Description:
 psi- Jabber client using Qt
Closes: 759334 841627
Changes:
 psi (0.15-3) unstable; urgency=low
 .
   * Build against libminizip-dev package (Closes: Bug#759334)
   * Use packaged ./configure script, as qconf-2.1-1 in sid
 is incompatible with psi's build setup. (Closes: Bug#841627)
   * Set INSTALL_ROOT when calling dh_auto_install.
   * Set Standards-Version to 3.9.7 (no further changes)
Checksums-Sha1:
 0093c76c9d01075ce11dc1abc1f041933ad3f28d 1563 psi_0.15-3.dsc
 6c134a24cc8907b32710dd60a47fd8a91d244609 10524 psi_0.15-3.debian.tar.xz
Checksums-Sha256:
 1299132895dfd322dc5f88aa46c2ac452c95c5b8f88ac42e16f12697d1777e0e 1563 
psi_0.15-3.dsc
 cd0e8d88b6570f1dc737752a65d6424cae2be74c40f67a3b00fb9915a96ff0f9 10524 
psi_0.15-3.debian.tar.xz
Files:
 07b1be177e891d87d67df5264998c947 1563 net optional psi_0.15-3.dsc
 6fbec456ef5b2c2d09baef256cac31cf 10524 net optional psi_0.15-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJYCoc2AAoJEMJAzpldAmsRq14L/isns/dgSwUiXQrfI8CqgHoF
N5oABsLVdSk4HO9UhqPZvL8q5mhOe5BgVH8hfEs/dAVurSt99wl/o/K2QHfkn6

Bug#841250: marked as done (php-facedetect: FTBFS: error with opencv 3.1)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 23:07:40 +
with message-id 
and subject line Bug#841250: fixed in php-facedetect 1.1.0+git20160406-3
has caused the Debian Bug report #841250,
regarding php-facedetect: FTBFS: error with opencv 3.1
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.)


-- 
841250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-facedetect
Version: 1.1.0+git20160406-2
Severity: important
Justification: fails to build from source
Tags: patch

Dear Maintainer,

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.

-
make[1]: Entering directory '/build/php-facedetect-1.1.0+git20160406'
/bin/bash /build/php-facedetect-1.1.0+git20160406/libtool
--mode=compile cc  -I. -I/build/php-facedetect-1.1.0+git20160406
-DPHP_ATOM_INC -I/build/php-facedetect-1.1.0+git20160406/include
-I/build/php-facedetect-1.1.0+git20160406/main
-I/build/php-facedetect-1.1.0+git20160406 -I/usr/include/php/20151012
-I/usr/include/php/20151012/main -I/usr/include/php/20151012/TSRM
-I/usr/include/php/20151012/Zend -I/usr/include/php/20151012/ext
-I/usr/include/php/20151012/ext/date/lib  -Wdate-time
-D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H  -g -O2
-fdebug-prefix-map=/build/php-facedetect-1.1.0+git20160406=. -fPIE
-fstack-protector-strong -Wformat -Werror=format-security   -c
/build/php-facedetect-1.1.0+git20160406/facedetect.c -o facedetect.lo
libtool: compile:  cc -I. -I/build/php-facedetect-1.1.0+git20160406
-DPHP_ATOM_INC -I/build/php-facedetect-1.1.0+git20160406/include
-I/build/php-facedetect-1.1.0+git20160406/main
-I/build/php-facedetect-1.1.0+git20160406 -I/usr/include/php/20151012
-I/usr/include/php/20151012/main -I/usr/include/php/20151012/TSRM
-I/usr/include/php/20151012/Zend -I/usr/include/php/20151012/ext
-I/usr/include/php/20151012/ext/date/lib -Wdate-time
-D_FORTIFY_SOURCE=2 -DHAVE_CONFIG_H -g -O2
-fdebug-prefix-map=/build/php-facedetect-1.1.0+git20160406=.
-fstack-protector-strong -Wformat -Werror=format-security -c
/build/php-facedetect-1.1.0+git20160406/facedetect.c  -fPIC -DPIC -o
.libs/facedetect.o
/build/php-facedetect-1.1.0+git20160406/facedetect.c: In function
'zm_info_facedetect':
/build/php-facedetect-1.1.0+git20160406/facedetect.c:69:48: error:
'CV_VERSION' undeclared (first use in this function)
  php_info_print_table_row(2, "OpenCV version", CV_VERSION);
^~
/build/php-facedetect-1.1.0+git20160406/facedetect.c:69:48: note: each
undeclared identifier is reported only once for each function it
appears in
Makefile:194: recipe for target 'facedetect.lo' failed
-

I attached a patch that revice this problem.
Could you check this patch and apply?

Best regards,
  Nobuhiro
diff -Nru php-facedetect-1.1.0+git20160406/debian/changelog php-facedetect-1.1.0+git20160406/debian/changelog
--- php-facedetect-1.1.0+git20160406/debian/changelog	2016-04-20 04:23:11.0 +0900
+++ php-facedetect-1.1.0+git20160406/debian/changelog	2016-10-18 00:35:24.0 +0900
@@ -1,3 +1,13 @@
+php-facedetect (1.1.0+git20160406-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update B-D.
+Change from libhighgui-dev and libcv-dev to libopencv-dev.
+  * Support OpenCV 3.
+Remove 0002-Revert-opencv3-support.patch
+
+ -- Nobuhiro Iwamatsu   Tue, 18 Oct 2016 00:35:24 +0900
+
 php-facedetect (1.1.0+git20160406-2) unstable; urgency=medium
 
   * Add ${php:Depends} to d/control (Closes: #821824)
diff -Nru php-facedetect-1.1.0+git20160406/debian/control php-facedetect-1.1.0+git20160406/debian/control
--- php-facedetect-1.1.0+git20160406/debian/control	2016-04-20 04:23:11.0 +0900
+++ php-facedetect-1.1.0+git20160406/debian/control	2016-10-18 00:35:24.0 +0900
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debian PHP PECL Maintainers 
 Uploaders: Mathieu Parent 
-Build-Depends: debhelper (>= 9), php-dev, dh-php, libhighgui-dev, libcv-dev
+Build-Depends: debhelper (>= 9), php-dev, dh-php, libopencv-dev
 Standards-Version: 3.9.7
 Vcs-Git: https://anonscm.debian.org/git/pkg-php/php-facedetect.git
 Vcs-Browser: 

Bug#837420: Bug#835148: please do not make GCC incompatible, we have dpkg-buildflags for this! (was Re: Bug#837420: Processed: PIE FTBFS are now RC)

[Thorsten Glaser]

Bálint Réczey dixit:

>AFAIK the linux package is the only problematic package were the
>maintainer refused to disable PIE from packaging scripts.

So, how are you supposed to do that now, instead of filtering
-fPIE from CFLAGS and -pie from LDFLAGS?

Christian/zumbi: do you take care of dietlibc, or should I?

Thanks,
//mirabilos
-- 
Stéphane, I actually don’t block Googlemail, they’re just too utterly
stupid to successfully deliver to me (or anyone else using Greylisting
and not whitelisting their ranges). Same for a few other providers such
as Hotmail. Some spammers (Yahoo) I do block.

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> notfound 837685 1.0~rc-3
Bug #837685 [src:psi4] psi4: FTBFS with bindnow and PIE enabled
The source 'psi4' and version '1.0~rc-3' do not appear to match any binary 
packages
No longer marked as found in versions psi4/1.0~rc-3.
> found 837685 1:1.0~rc-3
Bug #837685 [src:psi4] psi4: FTBFS with bindnow and PIE enabled
Marked as found in versions psi4/1:1.0~rc-3.
> thanks
Stopping processing here.

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

Processed: PIE FTBFS are now RC

[Debian Bug Tracking System]

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

> severity 837561 serious
Bug #837561 [src:kvmtool] kvmtool: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> severity 837572 serious
Bug #837572 [src:open-coarrays] open-coarrays: FTBFS with bindnow and PIE 
enabled
Severity set to 'serious' from 'important'
> severity 837573 serious
Bug #837573 [src:picolisp] picolisp: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> severity 837576 serious
Bug #837576 [src:sbcl] sbcl: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> notfound 837576 1.3.8-1
Bug #837576 [src:sbcl] sbcl: FTBFS with bindnow and PIE enabled
The source 'sbcl' and version '1.3.8-1' do not appear to match any binary 
packages
No longer marked as found in versions sbcl/1.3.8-1.
> found 837576 2:1.3.8-1
Bug #837576 [src:sbcl] sbcl: FTBFS with bindnow and PIE enabled
Marked as found in versions sbcl/2:1.3.8-1.
> severity 837577 serious
Bug #837577 [src:t38modem] t38modem: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> severity 837578 serious
Bug #837578 [src:terminix] terminix: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> severity 837579 serious
Bug #837579 [src:user-mode-linux] user-mode-linux: FTBFS with bindnow and PIE 
enabled
Severity set to 'serious' from 'important'
> severity 837582 serious
Bug #837582 [src:yabause] yabause: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> forcemerge 841542 837674
Bug #841542 [src:parmap] parmap: FTBFS: ocamlfind: Cannot mkdir 
/usr/local/lib/ocaml/4.02.3/parmap: Permission denied
Bug #837674 [src:parmap] parmap: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
Added tag(s) sid and stretch.
Merged 837674 841542
> retitle 837674 parmap: FTBFS: ocamlfind: Cannot mkdir 
> /usr/local/lib/ocaml/4.02.3/parmap: Permission denied
Bug #837674 [src:parmap] parmap: FTBFS with bindnow and PIE enabled
Bug #841542 [src:parmap] parmap: FTBFS: ocamlfind: Cannot mkdir 
/usr/local/lib/ocaml/4.02.3/parmap: Permission denied
Changed Bug title to 'parmap: FTBFS: ocamlfind: Cannot mkdir 
/usr/local/lib/ocaml/4.02.3/parmap: Permission denied' from 'parmap: FTBFS with 
bindnow and PIE enabled'.
Ignoring request to change the title of bug#841542 to the same title
> severity 837667 serious
Bug #837667 [src:acl2] acl2: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> severity 837685 serious
Bug #837685 [src:psi4] psi4: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
837561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837561
837572: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837572
837573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837573
837576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837576
837577: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837577
837578: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837578
837579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837579
837582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837582
837667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837667
837674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837674
837685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837685
841542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: PIE FTBFS are now RC

[Debian Bug Tracking System]

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

> severity 837570 serious
Bug #837570 [src:msrtool] msrtool: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> severity 837567 serious
Bug #837567 [src:mlton] mlton: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> affects 837567 src:urweb
Bug #837567 [src:mlton] mlton: FTBFS with bindnow and PIE enabled
Added indication that 837567 affects src:urweb
> severity 837566 serious
Bug #837566 [src:mjpegtools] mjpegtools: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> severity 837565 serious
Bug #837565 [liblpsolve55-dev] liblpsolve55-dev: Please build liblpsolve55.a 
with -fPIC
Severity set to 'serious' from 'important'
> affects 837565 src:mccs
Bug #837565 [liblpsolve55-dev] liblpsolve55-dev: Please build liblpsolve55.a 
with -fPIC
Added indication that 837565 affects src:mccs
> severity 837563 serious
Bug #837563 [src:libsecret] libsecret: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> severity 837562 serious
Bug #837562 [src:libembperl-perl] libembperl-perl: FTBFS with bindnow and PIE 
enabled
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#837659: This bug is actually in ocaml-nox

[Adrian Bunk]

Control: reassign -1 ocaml-nox
Control: affects -1 src:hivex

Relevant part of config.log:

...
configure:30935: checking for function caml_raise_with_args
/usr/bin/ld: /usr/lib/ocaml/libcamlrun.a(stacks.o): relocation 
R_X86_64_32 against `.rodata.str1.8' can not be used when making a 
shared object; recompile with -fPIC
...
/usr/bin/ld: /usr/lib/ocaml/libcamlrun.a(fix_code.o): relocation 
R_X86_64_32 against undefined symbol `caml_code_fragments_table' can not 
be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
File "_none_", line 1:
Error: Error while building custom runtime system
configure:30949: result: not found
...


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: This bug is actually in ocaml-nox

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ocaml-nox
Bug #837659 [src:hivex] hivex: FTBFS with bindnow and PIE enabled
Bug reassigned from package 'src:hivex' to 'ocaml-nox'.
No longer marked as found in versions hivex/1.3.13-2.
Ignoring request to alter fixed versions of bug #837659 to the same values 
previously set
> affects -1 src:hivex
Bug #837659 [ocaml-nox] hivex: FTBFS with bindnow and PIE enabled
Added indication that 837659 affects src:hivex

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

Bug#725417: Thanks a lot

[Santiago Garcia Mantinan]

Hi!

I've been preparing a new version of mbr which will change the format and
not overwrite the disk-id, but I have not finished yet and I don't have time
lately, so your upload is very welcome.

Thanks again. Regards.
-- 
Manty/BestiaTester -> http://manty.net

Processed: Pending fixes for bugs in the libtk-filedialog-perl package

[Debian Bug Tracking System]

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

> tag 841252 + pending
Bug #841252 [libtk-filedialog-perl] libtk-filedialog-perl: Control-W is 
deprecated in $W variable, needs to be changed to $^W with literal ^ character
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: This is the same bug

[Debian Bug Tracking System]

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

> reassign 841595 cdbs
Bug #841595 [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 #841595 to the same values 
previously set
> forcemerge 837006 841595
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.
Bug #838592 [cdbs] gnome-python-desktop: FTBFS: autotools.mk:44: *** no python 
implementation resolved from binary package "stamp-autotools".
Removed indication that 838592 affects gdb and pygtksourceview
Added indication that 838592 affects pygtksourceview,gdb
Removed indication that 837006 affects gdb and pygtksourceview
Added indication that 837006 affects pygtksourceview,gdb
Removed indication that 837018 affects pygtksourceview and gdb
Added indication that 837018 affects pygtksourceview,gdb
Removed indication that 837024 affects gdb and pygtksourceview
Added indication that 837024 affects pygtksourceview,gdb
Removed indication that 837220 affects gdb and pygtksourceview
Added indication that 837220 affects pygtksourceview,gdb
Removed indication that 837239 affects pygtksourceview and gdb
Added indication that 837239 affects pygtksourceview,gdb
Removed indication that 837243 affects gdb and pygtksourceview
Added indication that 837243 affects pygtksourceview,gdb
Removed indication that 837244 affects gdb and pygtksourceview
Added indication that 837244 affects pygtksourceview,gdb
Removed indication that 837248 affects pygtksourceview and gdb
Added indication that 837248 affects pygtksourceview,gdb
Removed indication that 837256 affects gdb and pygtksourceview
Added indication that 837256 affects pygtksourceview,gdb
Removed indication that 837260 affects gdb and pygtksourceview
Added indication that 837260 affects pygtksourceview,gdb
Removed indication that 837266 affects pygtksourceview and gdb
Added indication that 837266 affects pygtksourceview,gdb
Removed indication that 837270 affects pygtksourceview and gdb
Added indication that 837270 affects pygtksourceview,gdb
Removed indication that 837274 affects gdb and pygtksourceview
Added indication that 837274 affects pygtksourceview,gdb
Removed indication that 837278 affects gdb and pygtksourceview
Added indication that 837278 affects pygtksourceview,gdb
Removed indication that 838359 affects gdb and pygtksourceview
Added indication that 838359 affects pygtksourceview,gdb
Removed indication that 839296 affects pygtksourceview and gdb
Added indication that 839296 affects pygtksourceview,gdb
Bug #841595 [cdbs] gdb: FTBFS: /usr/share/cdbs/1/class/autotools.mk:44: *** no 
python implementation resolved from binary package 

Bug#841252: Pending fixes for bugs in the libtk-filedialog-perl package

[pkg-perl-maintainers]

tag 841252 + pending
thanks

Some bugs in the libtk-filedialog-perl package are closed in revision
5d92d5cb5750e1f90823f69bce0c1eb6219ce945 in branch 'master' by
Florian Schlichting

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libtk-filedialog-perl.git/commit/?id=5d92d5c

Commit message:

Add unrecognized_character_x17.patch (closes: #841252)

Processed: These all have the same root cause

[Debian Bug Tracking System]

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

> reassign 841555 src:p4est
Bug #841555 [src:deal.ii] deal.ii: FTBFS: build-dependency not installable: 
libp4est-dev
Bug reassigned from package 'src:deal.ii' to 'src:p4est'.
No longer marked as found in versions deal.ii/8.4.2-1.
Ignoring request to alter fixed versions of bug #841555 to the same values 
previously set
> reassign 840776 src:p4est
Bug #840776 [libp4est-dev] libp4est-dev: No version available for OpenMPI 2
Bug reassigned from package 'libp4est-dev' to 'src:p4est'.
No longer marked as found in versions p4est/1.1-2.
Ignoring request to alter fixed versions of bug #840776 to the same values 
previously set
> forcemerge 837058 840776 841555
Bug #837058 [src:p4est] p4est: FTBFS due to test failures
Bug #841555 [src:p4est] deal.ii: FTBFS: build-dependency not installable: 
libp4est-dev
836917 was blocked by: 822021 838299 835680 837530 837061 837030 837058 837532 
837911 837914 837059 839361 812036 811907 837915 837055 825934 830440 837109 
831164 837012 811651 837062 815348 817690
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 841555
Added indication that 841555 affects src:deal.ii
Marked as found in versions p4est/1.1-2 and p4est/1.1-3.
Bug #840776 [src:p4est] libp4est-dev: No version available for OpenMPI 2
Severity set to 'serious' from 'normal'
836917 was blocked by: 837109 837061 837030 830440 812036 837059 841555 837062 
839361 837915 837532 825934 817690 815348 838299 822021 811651 837911 837012 
811907 835680 837055 837058 837530 831164 837914
836917 was not blocking any bugs.
Added blocking bug(s) of 836917: 840776
Added indication that 840776 affects src:deal.ii
Marked as found in versions p4est/1.1-3 and p4est/1.1-2.
Added tag(s) sid and stretch.
Bug #837058 [src:p4est] p4est: FTBFS due to test failures
Added tag(s) stretch and sid.
Merged 837058 840776 841555
> thanks
Stopping processing here.

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

Processed: Lowering severity of #841292 related bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #841556 [src:mpd] mpd: FTBFS: iso9660.h:277:45: error: flexible array 
member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
Severity set to 'important' from 'serious'
> tags -1 -stretch
Bug #841556 [src:mpd] mpd: FTBFS: iso9660.h:277:45: error: flexible array 
member 'iso9660_dir_s::filename' not at end of 'struct iso9660_pvd_s'
Removed tag(s) stretch.

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

Processed: Lowering severity of #841292 related bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #841544 [src:guymager] guymager: FTBFS: aaff.cpp:82:22: error: flexible 
array member 't_AffSegmentHeader::Name' not at end of 'struct _t_Aaff'
Severity set to 'important' from 'serious'
> tags -1 -stretch
Bug #841544 [src:guymager] guymager: FTBFS: aaff.cpp:82:22: error: flexible 
array member 't_AffSegmentHeader::Name' not at end of 'struct _t_Aaff'
Removed tag(s) stretch.

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

Bug#841304: Lowering severity of #841292 related bugs

[Adrian Bunk]

Control: severity -1 important
Control: tags -1 -stretch

I am lowering the severity of these bugs exposed by
#841292 (gcc-6: flexible array support broken).

gcc 6 has the problematic change reverted, so this shouldn't be
a problem for stretch.

This is expected to be a FTBFS with gcc >= 7,
so these will need fixing for buster.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Lowering severity of #841292 related bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #841304 [glibc] invalid code in glibc tests
Severity set to 'important' from 'serious'
> tags -1 -stretch
Bug #841304 [glibc] invalid code in glibc tests
Ignoring request to alter tags of bug #841304 to the same tags previously set

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

Processed: Lowering severity of #841292 related bugs

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #841624 [src:libcdio] libcdio: FTBFS: ../../include/cdio/iso9660.h:277:45: 
error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct 
iso9660_pvd_s'
Severity set to 'important' from 'serious'
> tags -1 -stretch
Bug #841624 [src:libcdio] libcdio: FTBFS: ../../include/cdio/iso9660.h:277:45: 
error: flexible array member 'iso9660_dir_s::filename' not at end of 'struct 
iso9660_pvd_s'
Removed tag(s) stretch.

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

Processed: Move to the correct package

[Debian Bug Tracking System]

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

> reassign 841615 libmono-cecil-cil
Bug #841615 [src:cecil-flowanalysis] cecil-flowanalysis: FTBFS: 
build-dependency not installable: libmono-cecil-cil-dev (>= 0.9.5)
Bug reassigned from package 'src:cecil-flowanalysis' to 'libmono-cecil-cil'.
No longer marked as found in versions 
cecil-flowanalysis/0.1~vcs20110809.r1.b34edf6-3.
Ignoring request to alter fixed versions of bug #841615 to the same values 
previously set
> retitle 841615 libmono-cecil-cil is not installable in unstable
Bug #841615 [libmono-cecil-cil] cecil-flowanalysis: FTBFS: build-dependency not 
installable: libmono-cecil-cil-dev (>= 0.9.5)
Changed Bug title to 'libmono-cecil-cil is not installable in unstable' from 
'cecil-flowanalysis: FTBFS: build-dependency not installable: 
libmono-cecil-cil-dev (>= 0.9.5)'.
> affects 841615 src:cecil-flowanalysis
Bug #841615 [libmono-cecil-cil] libmono-cecil-cil is not installable in unstable
Added indication that 841615 affects src:cecil-flowanalysis
> thanks
Stopping processing here.

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

Processed: Move to the correct package

[Debian Bug Tracking System]

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

> reassign 841612 libmodpbase64-dev
Bug #841612 [src:aseprite] aseprite: FTBFS: modp_b64.h:31:25: fatal error: 
modp_stdint.h: No such file or directory
Bug reassigned from package 'src:aseprite' to 'libmodpbase64-dev'.
No longer marked as found in versions aseprite/1.1.6+ds-1.
Ignoring request to alter fixed versions of bug #841612 to the same values 
previously set
> retitle 841612 libmodpbase64-dev: modp_stdint.h is missing
Bug #841612 [libmodpbase64-dev] aseprite: FTBFS: modp_b64.h:31:25: fatal error: 
modp_stdint.h: No such file or directory
Changed Bug title to 'libmodpbase64-dev: modp_stdint.h is missing' from 
'aseprite: FTBFS: modp_b64.h:31:25: fatal error: modp_stdint.h: No such file or 
directory'.
> affects 841612 src:aseprite
Bug #841612 [libmodpbase64-dev] libmodpbase64-dev: modp_stdint.h is missing
Added indication that 841612 affects src:aseprite
> thanks
Stopping processing here.

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

Bug#841665: boinc-client: The boinc-client init script has a badly constructed parameter for xhost

[Mike Brennan]

Package: boinc-client
Version: 7.6.33+dfsg-1~bpo8+1
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainers,

boinc-client shell script is used by init/systemd to start the boinc client 
daemon (typically running as user=boinc)

In order for boinc to access GPU hardware -  xhost is used to grant access to 
boinc.

At line 109-110
---
# grant the boinc client to perform GPU computing
   xhost local:boinc || echo -n "xhost error ignored, GPU computing may not 
be possible"


the correct syntax stould be 
   xhost +si:localuser:boinc
or more correctly for the this script
   xhost +si:localuser:$BOINC_USER

The impact of using this incorrect syntax - is not to error, but grant ALL 
local users access.  
(This could be a very old or different maybe BSD syntax)

The intention of the script to grant ONLY user=boinc access, instead all local 
users have access.

For example a little test.

agentb@dejon:/etc/init.d$ xhost
access control enabled, only authorized clients can connect
SI:localuser:agentb

agentb@dejon:/etc/init.d$ xhost local:random-string
non-network local connections being added to access control list

agentb@dejon:/etc/init.d$ xhost
access control enabled, only authorized clients can connect
LOCAL:
SI:localuser:boinc
SI:localuser:agentb

Hope this is clear, and thank you for maintaining boinc!

Cheers
Mike


-- Package-specific info:
-- Contents of /etc/default/boinc-client:
# This file is /etc/default/boinc-client, it is a configuration file for the
# /etc/init.d/boinc-client init script.

# Set this to 1 to enable and to 0 to disable the init script.
ENABLED="1"

# Set this to 1 to enable advanced scheduling of the BOINC core client and
# all its sub-processes (reduces the impact of BOINC on the system's
# performance).
SCHEDULE="1"

# The BOINC core client will be started with the permissions of this user.
BOINC_USER="boinc"

# This is the data directory of the BOINC core client.
BOINC_DIR="/var/lib/boinc-client"

# This is the location of the BOINC core client, that the init script uses.
# If you do not want to use the client program provided by the boinc-client
# package, you can specify here an alternative client program.
#BOINC_CLIENT="/usr/local/bin/boinc"
BOINC_CLIENT="/usr/bin/boinc"

# Here you can specify additional options to pass to the BOINC core client.
# Type 'boinc --help' or 'man boinc' for a full summary of allowed options.
#BOINC_OPTS="--allow_remote_gui_rpc"
BOINC_OPTS=""

# Scheduling options

# Set SCHEDULE="0" if prefering to run with upstream default priority
# settings.

# Nice levels. When systems are truly busy, e.g. because of too many active
# scientific applications started by the boinc client, there is a chance for
# the boinc client not to be granted sufficient opportunity to check for
# scientific applications to be alive and make the (wrong) decision to
# terminate the scientific app. This is particularly an issue with many
# apps started in parallel on modern multi-core systems and extra overheads
# for the download and uploads of files with the project servers. Another
# concern is the latency for scientific applications to communicate with the
# graphics card, which should be low. All such values should be set and
# controled from within the BOINC client. The Debian init script also sets
# extra constrains via chrt on real time performance and via ionice on 
# I/O performance, which is beyond the regular BOINC client. It then was
# too easy to use that code to also constrain minimal nice levels. We still
# think about how to best distinguish GPU applications from regular apps.
BOINC_NICE_CLIENT=10
BOINC_NICE_APP_DEFAULT=19
#BOINC_NICE_APP_GPU=5# not yet used

# ionice classes. See manpage of ionice (1) in the util-linux package.
BOINC_IONICE_CLIENT=3# idle
#BOINC_IONICE_APP_DEFAULT=3  # idle, not yet used
#BOINC_IONICE_APP_GPU=2  # best effort, not yet used


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

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

Versions of packages boinc-client depends on:
ii  adduser3.113+nmu3
ii  ca-certificates20141019+deb8u1
ii  debconf [debconf-2.0]  1.5.56
ii  init-system-helpers1.22
ii  libboinc7  7.6.33+dfsg-1~bpo8+1
ii  libc6  2.19-18+deb8u6
ii  libcurl3   7.38.0-4+deb8u4
ii  libgcc11:4.9.2-10
ii  libstdc++6 4.9.2-10
ii  libx11-6   2:1.6.2-3
ii  libxss11:1.2.2-1
ii  python 2.7.9-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

boinc-client 

Processed: Move PIE bugs to the correct packages

[Debian Bug Tracking System]

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

> severity 837686 serious
Bug #837686 [src:psicode] psicode: FTBFS with bindnow and PIE enabled
Severity set to 'serious' from 'important'
> reassign 837686 libint-dev
Bug #837686 [src:psicode] psicode: FTBFS with bindnow and PIE enabled
Bug reassigned from package 'src:psicode' to 'libint-dev'.
No longer marked as found in versions psicode/3.4.0-6.
Ignoring request to alter fixed versions of bug #837686 to the same values 
previously set
> retitle 837686 libint-dev: Please build static libraries with -fPIC
Bug #837686 [libint-dev] psicode: FTBFS with bindnow and PIE enabled
Changed Bug title to 'libint-dev: Please build static libraries with -fPIC' 
from 'psicode: FTBFS with bindnow and PIE enabled'.
> affects 837686 src:psicode
Bug #837686 [libint-dev] libint-dev: Please build static libraries with -fPIC
Added indication that 837686 affects src:psicode
> reassign 837569 libpsi3-dev
Bug #837569 [src:mpqc3] mpqc3: FTBFS with bindnow and PIE enabled
Bug reassigned from package 'src:mpqc3' to 'libpsi3-dev'.
No longer marked as found in versions mpqc3/0.0~git20160216-3.
Ignoring request to alter fixed versions of bug #837569 to the same values 
previously set
> retitle 837569 libpsi3-dev Please build static libraries with -fPIC
Bug #837569 [libpsi3-dev] mpqc3: FTBFS with bindnow and PIE enabled
Changed Bug title to 'libpsi3-dev Please build static libraries with -fPIC' 
from 'mpqc3: FTBFS with bindnow and PIE enabled'.
> affects 837569 src:mpqc3
Bug #837569 [libpsi3-dev] libpsi3-dev Please build static libraries with -fPIC
Added indication that 837569 affects src:mpqc3
> thanks
Stopping processing here.

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

Bug#841513: marked as done (golang-github-azure-go-autorest: FTBFS in sid: cannot use map[string]interface {} literal (type map[string]interface {}) as type jwt.Claims in assignment)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 21:55:45 +0200
with message-id <9e83ee92-ac9b-7eb2-6a58-bfb880969...@tincho.org>
and subject line Re: [pkg-go] Bug#841513: golang-github-azure-go-autorest: 
FTBFS in sid: cannot use map[string]interface {} literal (type 
map[string]interface {}) as type jwt.Claims in assignment
has caused the Debian Bug report #841513,
regarding golang-github-azure-go-autorest: FTBFS in sid: cannot use 
map[string]interface {} literal (type map[string]interface {}) as type 
jwt.Claims in assignment
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.)


-- 
841513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-azure-go-autorest
Version: 7.2.0+REALLY.7.0.4-1
Severity: serious

Hi,

the "older" version now FTBFS in sid (arch:all buildd):

https://buildd.debian.org/status/fetch.php?pkg=golang-github-azure-go-autorest=all=7.2.0%2BREALLY.7.0.4-1=1476210593

   dh_auto_build -i -O--buildsystem=golang
go install -v -p 1 github.com/Azure/go-autorest/autorest 
github.com/Azure/go-autorest/autorest/azure 
github.com/Azure/go-autorest/autorest/azure/example 
github.com/Azure/go-autorest/autorest/date 
github.com/Azure/go-autorest/autorest/mocks 
github.com/Azure/go-autorest/autorest/to
github.com/Azure/go-autorest/autorest
github.com/Azure/go-autorest/autorest/date
github.com/dgrijalva/jwt-go
github.com/Azure/go-autorest/autorest/azure
# github.com/Azure/go-autorest/autorest/azure
src/github.com/Azure/go-autorest/autorest/azure/token.go:147: cannot use 
map[string]interface {} literal (type map[string]interface {}) as type 
jwt.Claims in assignment:
map[string]interface {} does not implement jwt.Claims (missing Valid 
method)
golang.org/x/crypto/pkcs12/internal/rc2
golang.org/x/crypto/pkcs12
github.com/Azure/go-autorest/autorest/mocks
github.com/Azure/go-autorest/autorest/to
dh_auto_build: go install -v -p 1 github.com/Azure/go-autorest/autorest 
github.com/Azure/go-autorest/autorest/azure 
github.com/Azure/go-autorest/autorest/azure/example 
github.com/Azure/go-autorest/autorest/date 
github.com/Azure/go-autorest/autorest/mocks 
github.com/Azure/go-autorest/autorest/to returned exit code 2
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2


Andreas
--- End Message ---
--- Begin Message ---
On 21/10/16 11:52, Andreas Beckmann wrote:
> Source: golang-github-azure-go-autorest
> Version: 7.2.0+REALLY.7.0.4-1
> Severity: serious
> 
> Hi,
> 
> the "older" version now FTBFS in sid (arch:all buildd):

This was an artifact of the reverted versions being uploaded in close
proximity. I have requested a rebuild of the this package and it has
completed successfully.

-- 
Martín Ferrari (Tincho)--- End Message ---

Processed: Merge duplicate libmysqlclient_r bugs

[Debian Bug Tracking System]

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

> reassign 825084 src:resiprocate
Bug #825084 [repro] Package links against libmysqlclient_r
Bug reassigned from package 'repro' to 'src:resiprocate'.
No longer marked as found in versions 1.10.1-2.
Ignoring request to alter fixed versions of bug #825084 to the same values 
previously set
> forcemerge 841603 825084
Bug #841603 [src:resiprocate] resiprocate: FTBFS: ld: cannot find 
-lmysqlclient_r
Bug #841603 [src:resiprocate] resiprocate: FTBFS: ld: cannot find 
-lmysqlclient_r
Added tag(s) patch.
Bug #825084 [src:resiprocate] Package links against libmysqlclient_r
Severity set to 'serious' from 'normal'
Marked as found in versions resiprocate/1:1.10.2-1.
Added tag(s) stretch and sid.
Merged 825084 841603
> tags 825084 +patch
Bug #825084 [src:resiprocate] Package links against libmysqlclient_r
Bug #841603 [src:resiprocate] resiprocate: FTBFS: ld: cannot find 
-lmysqlclient_r
Ignoring request to alter tags of bug #825084 to the same tags previously set
Ignoring request to alter tags of bug #841603 to the same tags previously set
> reassign 825086 src:mysql++
Bug #825086 [libmysql++3v5] Package links against libmysqlclient_r
Bug reassigned from package 'libmysql++3v5' to 'src:mysql++'.
No longer marked as found in versions mysql++/3.2.2+pristine-1.
Ignoring request to alter fixed versions of bug #825086 to the same values 
previously set
> forcemerge 841621 825086
Bug #841621 [src:mysql++] mysql++: FTBFS: checking for MySQL library 
directory... configure: error: Didn't find mysqlclient_r library in 
'/usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/lib64 
/usr/lib/x86_64-linux-gnu/lib /usr/lib/x86_64-linux-gnu/lib64/mysql 
/usr/lib/x86_64-linux-gnu/lib/mysql'
Bug #825086 [src:mysql++] Package links against libmysqlclient_r
Severity set to 'serious' from 'normal'
Marked as found in versions mysql++/3.2.2+pristine-1.
Added tag(s) sid and stretch.
Bug #841621 [src:mysql++] mysql++: FTBFS: checking for MySQL library 
directory... configure: error: Didn't find mysqlclient_r library in 
'/usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/lib64 
/usr/lib/x86_64-linux-gnu/lib /usr/lib/x86_64-linux-gnu/lib64/mysql 
/usr/lib/x86_64-linux-gnu/lib/mysql'
Added tag(s) patch.
Merged 825086 841621
> tags 825086 +patch
Bug #825086 [src:mysql++] Package links against libmysqlclient_r
Bug #841621 [src:mysql++] mysql++: FTBFS: checking for MySQL library 
directory... configure: error: Didn't find mysqlclient_r library in 
'/usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/lib64 
/usr/lib/x86_64-linux-gnu/lib /usr/lib/x86_64-linux-gnu/lib64/mysql 
/usr/lib/x86_64-linux-gnu/lib/mysql'
Ignoring request to alter tags of bug #825086 to the same tags previously set
Ignoring request to alter tags of bug #841621 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#839176: marked as done (libgv-python: adequate reports broken-symlink of _gv.x86_64-linux-gnu.so to libgv_python27.so)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 19:24:45 +
with message-id 
and subject line Bug#839176: fixed in graphviz 2.38.0-16
has caused the Debian Bug report #839176,
regarding libgv-python: adequate reports broken-symlink of 
_gv.x86_64-linux-gnu.so to libgv_python27.so
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.)


-- 
839176: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839176
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgv-python
Version: 2.38.0-15+b1
Severity: normal
User: debian...@lists.debian.org
Usertags: broken-symlink adequate

Dear Maintainer,
Adequate reports broken symlink

libgv-python: broken-symlink
/usr/lib/python2.7/dist-packages/_gv.x86_64-linux-gnu.so ->
libgv_python27.so

┌─[shirish@debian] - [/usr/lib/python2.7/dist-packages] - [10056]
└─[$] ll -h | grep libgv

lrwxrwxrwx  1 root root   17 Aug 28 16:47 _gv.x86_64-linux-gnu.so ->
libgv_python27.so
-rw-r--r--  1 root root  96K Aug 28 16:47 libgv_python27.x86_64-linux-gnu.so

I am not familiar with the functionality that libgv provides other
than to say it's part of graphviz but it *seems* that the symlink
should have pointed to libgv_python27.x86_64-linux-gnu.so

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

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

Versions of packages libgv-python depends on:
ii  libc6 2.23-5
ii  libcdt5   2.38.0-15+b1
ii  libcgraph62.38.0-15+b1
ii  libgcc1   1:6.1.1-11
ii  libgvc6   2.38.0-15+b1
ii  libpython2.7  2.7.12-3
ii  libstdc++66.1.1-11
ii  python2.7.11-2
pn  python:any

libgv-python recommends no packages.

libgv-python suggests no packages.

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Source: graphviz
Source-Version: 2.38.0-16

We believe that the bug you reported is fixed in the latest version of
graphviz, 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 839...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated graphviz 
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 19:43:26 +0200
Source: graphviz
Binary: graphviz libgv-guile libgv-lua libgv-perl libgv-python libgv-ruby 
libgv-tcl libcgraph6 libcdt5 libpathplan4 libgvc6 libgvc6-plugins-gtk libgvpr2 
libxdot4 libgraphviz-dev graphviz-doc graphviz-dev
Architecture: source amd64 all
Version: 2.38.0-16
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 graphviz   - rich set of graph drawing tools
 graphviz-dev - transitional package for graphviz-dev rename
 graphviz-doc - additional documentation for graphviz
 libcdt5- rich set of graph drawing tools - cdt library
 libcgraph6 - rich set of graph drawing tools - cgraph library
 libgraphviz-dev - graphviz libs and headers against which to build applications
 libgv-guile - Guile bindings for graphviz
 libgv-lua  - Lua bindings for graphviz
 libgv-perl - Perl bindings for graphviz
 libgv-python - Python bindings for graphviz
 libgv-ruby - Ruby bindings for graphviz
 libgv-tcl  - Tcl bindings for graphviz
 libgvc6- rich set of graph drawing tools - gvc library
 libgvc6-plugins-gtk - rich set of graph drawing tools - gtk plugins
 libgvpr2   - rich set of graph drawing tools - gvpr library
 libpathplan4 - rich set of graph drawing tools - pathplan library
 libxdot4   - rich set of graph drawing tools - xdot 

Bug#837687: snort builds with --disable-static-daq

[Adrian Bunk]

Adding --disable-static-daq CONFFLAGS fixed the build for me.

Why does snort want to link with the static library by default?
If the shared library is also fine this is a proper fix.
If it is not, libdaq_static.a must be recompiled with -fPIC.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#841388: marked as done (education-tasks and education-menus: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 18:49:22 +
with message-id 
and subject line Bug#841388: fixed in debian-edu 1.912
has caused the Debian Bug report #841388,
regarding education-tasks and education-menus: error when trying to install 
together
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.)


-- 
841388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: education-menus,education-tasks
Version: education-menus/1.911
Version: education-tasks'1.911@all, education-tasks/1.910
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-10-20
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Preconfiguring packages ...
Selecting previously unselected package desktop-profiles.
(Reading database ... 10972 files and directories currently installed.)
Preparing to unpack .../desktop-profiles_1.4.22_all.deb ...
Unpacking desktop-profiles (1.4.22) ...
Selecting previously unselected package education-menus.
Preparing to unpack .../education-menus_1.911_amd64.deb ...
Unpacking education-menus (1.911) ...
Selecting previously unselected package education-tasks.
Preparing to unpack .../education-tasks_1.911_all.deb ...
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
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/education-tasks_1.911_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/share/tasksel/descs/debian-edu-tasks.desc

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Source: debian-edu
Source-Version: 1.912

We believe that the bug you reported is fixed in the latest version of
debian-edu, 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.
Holger Levsen  (supplier of updated debian-edu 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: Fri, 21 Oct 2016 20:16:46 +0200
Source: debian-edu
Binary: education-tasks education-menus education-astronomy education-chemistry 
education-common education-desktop-gnome education-desktop-kde 
education-desktop-lxde education-desktop-mate education-desktop-other 
education-desktop-xfce education-development education-electronics 
education-geography education-graphics education-lang-da 
education-lang-da-desktop education-lang-da-desktop-kde education-lang-de 
education-lang-de-desktop education-lang-de-desktop-kde education-lang-es 

Processed: Re: cl-plplot: FTBFS: The alien function "c_plwid" is undefined.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ftp.debian.org
Bug #759904 [src:cl-plplot] cl-plplot: FTBFS: The alien function "c_plwid" is 
undefined.
Bug reassigned from package 'src:cl-plplot' to 'ftp.debian.org'.
No longer marked as found in versions cl-plplot/0.6.0-4.
Ignoring request to alter fixed versions of bug #759904 to the same values 
previously set
> affects -1 cl-plplot
Bug #759904 [ftp.debian.org] cl-plplot: FTBFS: The alien function "c_plwid" is 
undefined.
Added indication that 759904 affects cl-plplot
> retitle -1 RM: cl-plplot -- RoQA; FTBFS
Bug #759904 [ftp.debian.org] cl-plplot: FTBFS: The alien function "c_plwid" is 
undefined.
Changed Bug title to 'RM: cl-plplot -- RoQA; FTBFS' from 'cl-plplot: FTBFS: The 
alien function "c_plwid" is undefined.'.

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

Bug#759904: cl-plplot: FTBFS: The alien function "c_plwid" is undefined.

[Steve Langasek]

Control: reassign -1 ftp.debian.org
Control: affects -1 cl-plplot
Control: retitle -1 RM: cl-plplot -- RoQA; FTBFS

The cl-plplot package has been FTBFS in unstable since 2014.  It was
orphaned that same year, with an upload that apparently was not built
against clean unstable.  There has been no sign of activity since.  Please
remove this package from unstable.

The package is also affected by serious bug #794850.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Bug#841548: autopkgtest: FTBFS: Tests failures

[Martin Pitt]

Control: reassign -1 python3-wand
Control: forcemerge 841653 -1


Martin Pitt [2016-10-21 20:22 +0200]:
> |  File "/tmp/autopkgtest.2SwpBj/build.7IV/real-tree/debian/tests/t", line 2, 
> in 
> | from wand.image import Image
> |   File 
> "/tmp/autopkgtest.2SwpBj/deps/usr/lib/python3/dist-packages/wand/image.py", 
> line 21, in 
> | from .color import Color
> |   File 
> "/tmp/autopkgtest.2SwpBj/deps/usr/lib/python3/dist-packages/wand/color.py", 
> line 12, in 
> | from .version import QUANTUM_DEPTH
> |   File 
> "/tmp/autopkgtest.2SwpBj/deps/usr/lib/python3/dist-packages/wand/version.py", 
> line 95, in 
> | *map(int, MAGICK_RELEASE_DATE_STRING.split('-')))
> | TypeError: Required argument 'month' (pos 2) not found
> 
> So it looks like imagemagic changed recently, so at first sight I'll
> just need to adjust the test case to that.

Turns out this is an actual bug in python3-wand, not a bug in the
tests. I reported this as https://bugs.debian.org/841653 and make this
a duplicate.

Thanks,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Processed: Re: Bug#841548: autopkgtest: FTBFS: Tests failures

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python3-wand
Bug #841548 [src:autopkgtest] autopkgtest: FTBFS: Tests failures
Bug reassigned from package 'src:autopkgtest' to 'python3-wand'.
No longer marked as found in versions autopkgtest/4.1.
Ignoring request to alter fixed versions of bug #841548 to the same values 
previously set
> forcemerge 841653 -1
Bug #841653 [python3-wand] Importing wand.image fails
Bug #841548 [python3-wand] autopkgtest: FTBFS: Tests failures
Marked as found in versions wand/0.3.9-1.
Bug #841653 [python3-wand] Importing wand.image fails
Added tag(s) confirmed, sid, and stretch.
Merged 841548 841653

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

Bug#837581: Move to the correct package

[Adrian Bunk]

Control: reassign -1 xfslibs-dev
Control: retitle -1 xfslibs-dev: Don't put the .so symlink to /lib/*.so
Control: affects -1 src:xfsdump

The root cause of this bug is that /usr/lib/libhandle.a is being used 
instead of /lib/libhandle.so

This was already not right before, but now it became fatal.

The correct solution for this bug is:
- move libhandle.so.1 to /lib//
- move libhandle.so to /usr/lib//

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: Move to the correct package

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 xfslibs-dev
Bug #837581 [src:xfsdump] xfsdump: FTBFS with bindnow and PIE enabled
Bug reassigned from package 'src:xfsdump' to 'xfslibs-dev'.
No longer marked as found in versions xfsdump/3.1.6+nmu1.
Ignoring request to alter fixed versions of bug #837581 to the same values 
previously set
> retitle -1 xfslibs-dev: Don't put the .so symlink to /lib/*.so
Bug #837581 [xfslibs-dev] xfsdump: FTBFS with bindnow and PIE enabled
Changed Bug title to 'xfslibs-dev: Don't put the .so symlink to /lib/*.so' from 
'xfsdump: FTBFS with bindnow and PIE enabled'.
> affects -1 src:xfsdump
Bug #837581 [xfslibs-dev] xfslibs-dev: Don't put the .so symlink to /lib/*.so
Added indication that 837581 affects src:xfsdump

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

Bug#841653: Importing wand.image fails

[Martin Pitt]

Package: python3-wand
Severity: serious
Version: 0.3.9-1

Hello,

In current sid, at least in a minimal chroot, this module is broken:

  # apt-get install -y python3-wand
  # python3 -c 'import wand.image'
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/wand/image.py", line 21, in 
  from .color import Color
File "/usr/lib/python3/dist-packages/wand/color.py", line 12, in 
  from .version import QUANTUM_DEPTH
File "/usr/lib/python3/dist-packages/wand/version.py", line 95, in 
  *map(int, MAGICK_RELEASE_DATE_STRING.split('-')))
  TypeError: Required argument 'month' (pos 2) not found

This must have happened relatively recently. This is spotted by
autopkgtest's testsuite, and Lukas just reported that it's now failing
(#841548). It was still working on October 7 when I did the last
upload.

Thanks for considering,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Bug#841545: marked as done (liborlite-perl: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 18:27:43 +
with message-id <e1bxexf-0006gr...@franck.debian.org>
and subject line Bug#841545: fixed in liborlite-perl 1.98-2
has caused the Debian Bug report #841545,
regarding liborlite-perl: FTBFS: Tests failures
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.)


-- 
841545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liborlite-perl
Version: 1.98-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> #  $got->[2] = '0'
> # $expected->[2] = '4'
> ok 4 - An object of class 'My::Foo' isa 'My::Foo'
> ok 5 - Round trip ok
> ok
> 
> Test Summary Report
> ---
> t/10_cleanup.t (Wstat: 5632 Tests: 2 Failed: 0)
>   Non-zero exit status: 22
> t/11_cleanup.t (Wstat: 5632 Tests: 4 Failed: 0)
>   Non-zero exit status: 22
> Files=25, Tests=533,  2 wallclock secs ( 0.11 usr  0.02 sys +  1.38 cusr  
> 0.12 csys =  1.63 CPU)
> Result: FAIL
> Failed 2/25 test programs. 0/533 subtests failed.
> Makefile:752: recipe for target 'test_dynamic' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/liborlite-perl_1.98-1_unstable.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: liborlite-perl
Source-Version: 1.98-2

We believe that the bug you reported is fixed in the latest version of
liborlite-perl, 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.
gregor herrmann <gre...@debian.org> (supplier of updated liborlite-perl 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: Fri, 21 Oct 2016 19:48:42 +0200
Source: liborlite-perl
Binary: liborlite-perl
Architecture: source
Version: 1.98-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <pkg-perl-maintain...@lists.alioth.debian.org>
Changed-By: gregor herrmann <gre...@debian.org>
Closes: 831312 841545
Description: 
 liborlite-perl - lightweight SQLite-specific ORM
Changes:
 liborlite-perl (1.98-2) unstable; urgency=medium
 .
   [ Nathan Handler ]
   * Email change: Nathan Handler -> nhand...@debian.org
 .
   [ Salvatore Bonaccorso ]
   * Change Vcs-Git to canonical URI (git://anonscm.debian.org)
   * Change search.cpan.org based URIs to metacpan.org based URIs
 .
   [ gregor herrmann ]
   * Strip trailing slash from metacpan URLs.
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-Browser URL to cgit web frontend
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Remove Franck Joncourt from Uploaders.
 Thanks to Tobias Frost (Closes: #831312)
 .
   [ gregor herrmann ]
   * Remove Brian Cassidy, Jaldhar H. Vyas, Jonathan Yu, Nathan Handler,
 Rene Mayorga from Uploaders. Thanks for your work!
   * Refresh debian/patches/fix_pod_spelling (offset).

Bug#840311: marked as done (golang-google-cloud: FTBFS in testing (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 18:26:30 +
with message-id 
and subject line Bug#840311: fixed in golang-google-cloud 0.0~git20160615-4
has caused the Debian Bug report #840311,
regarding golang-google-cloud: FTBFS in testing (failing tests)
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.)


-- 
840311: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-google-cloud
Version: 0.0~git20160615-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=golang --with=golang
   dh_testdir -i -O--buildsystem=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
dh_auto_configure: "google.golang.org/cloud" is already installed. Please check 
for circular dependencies.

   dh_auto_build -i -O--buildsystem=golang
go install -v -p 1 google.golang.org/cloud 
google.golang.org/cloud/bigquery google.golang.org/cloud/bigtable 
google.golang.org/cloud/bigtable/bttest 
google.golang.org/cloud/bigtable/cmd/cbt 
google.golang.org/cloud/bigtable/cmd/loadtest 
google.golang.org/cloud/bigtable/internal/cbtrc 
google.golang.org/cloud/bigtable/internal/cluster_data_proto 
google.golang.org/cloud/bigtable/internal/cluster_service_proto 
google.golang.org/cloud/bigtable/internal/data_proto 
google.golang.org/cloud/bigtable/internal/rpc_status_proto 
google.golang.org/cloud/bigtable/internal/service_proto 
google.golang.org/cloud/bigtable/internal/table_data_proto 
google.golang.org/cloud/bigtable/internal/table_service_proto 
google.golang.org/cloud/compute/metadata google.golang.org/cloud/container 
google.golang.org/cloud/datastore 
google.golang.org/cloud/datastore/internal/proto 
google.golang.org/cloud/datastore/internal/type_proto 
google.golang.org/cloud/examples/bigquery/concat_table 
google.golang.org/cloud/examples
 /bigquery/load google.golang.org/cloud/examples/bigquery/query 
google.golang.org/cloud/examples/bigquery/read 
google.golang.org/cloud/examples/bigtable/bigtable-hello 
google.golang.org/cloud/examples/bigtable/search 
google.golang.org/cloud/examples/pubsub/cmdline 
google.golang.org/cloud/examples/pubsub/consumer 
google.golang.org/cloud/examples/storage/appengine 
google.golang.org/cloud/examples/storage/appenginevm 
google.golang.org/cloud/internal google.golang.org/cloud/internal/opts 
google.golang.org/cloud/internal/testutil 
google.golang.org/cloud/internal/transport google.golang.org/cloud/logging 
google.golang.org/cloud/logging/apiv2/config 
google.golang.org/cloud/logging/apiv2/logging 
google.golang.org/cloud/logging/apiv2/metrics google.golang.org/cloud/pubsub 
google.golang.org/cloud/storage
golang.org/x/net/context
golang.org/x/oauth2/internal
golang.org/x/oauth2
google.golang.org/cloud/internal

[... snipped ...]

2016/10/10 12:25:56 bttest: GC MaxNumVersions(1) deleted 109 cells.
2016/10/10 12:25:56 bttest: GC MaxNumVersions(1) deleted 113 cells.
2016/10/10 12:25:56 bttest: GC MaxNumVersions(1) deleted 117 cells.
2016/10/10 12:25:56 bttest: GC MaxNumVersions(1) deleted 90 cells.
2016/10/10 12:25:56 bttest: GC MaxNumVersions(1) deleted 112 cells.
2016/10/10 12:25:56 bttest: GC MaxNumVersions(1) deleted 1 cells.
--- FAIL: TestConcurrentMutationsAndGC (0.11s)
inmem_test.go:83: Concurrent mutations and GCs haven't completed after 
100ms
FAIL
exit status 1
FAILgoogle.golang.org/cloud/bigtable/bttest 0.118s

[ ... ]
dh_auto_test: go test -v -p 1 google.golang.org/cloud 
google.golang.org/cloud/bigquery google.golang.org/cloud/bigtable 
google.golang.org/cloud/bigtable/bttest 
google.golang.org/cloud/bigtable/cmd/cbt 
google.golang.org/cloud/bigtable/cmd/loadtest 
google.golang.org/cloud/bigtable/internal/cbtrc 
google.golang.org/cloud/bigtable/internal/cluster_data_proto 
google.golang.org/cloud/bigtable/internal/cluster_service_proto 
google.golang.org/cloud/bigtable/internal/data_proto 
google.golang.org/cloud/bigtable/internal/rpc_status_proto 
google.golang.org/cloud/bigtable/internal/service_proto 
google.golang.org/cloud/bigtable/internal/table_data_proto 
google.golang.org/cloud/bigtable/internal/table_service_proto 
google.golang.org/cloud/compute/metadata google.golang.org/cloud/container 

Processed: Re: Bug#841548: autopkgtest: FTBFS: Tests failures

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed
Bug #841548 [src:autopkgtest] autopkgtest: FTBFS: Tests failures
Added tag(s) confirmed.

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

Bug#841388: marked as pending

[Holger Levsen]

tag 841388 pending
thanks

Hello,

Bug #841388 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=debian-edu/debian-edu.git;a=commitdiff;h=5a02445

---
commit 5a024457cee19751c3b463378be2b17c838b8b45
Author: Holger Levsen 
Date:   Fri Oct 21 19:47:23 2016 +0200

debian/control.stub: mark education-tasks as Multi-Arch: foreign. (Closes: 
#841388)

diff --git a/debian/changelog b/debian/changelog
index fb397e3..832feb2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+debian-edu (1.912) UNRELEASED; urgency=medium
+
+  * debian/control.stub: mark education-tasks as Multi-Arch: foreign.
+(Closes: #841388)
+
+ -- Holger Levsen   Fri, 21 Oct 2016 19:43:29 +0200
+
 debian-edu (1.911) unstable; urgency=medium
 
   * Turn education-tasks into an arch:all package. Since at least wheezy the

Processed: Bug#841388 marked as pending

[Debian Bug Tracking System]

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

> tag 841388 pending
Bug #841388 [education-menus,education-tasks] education-tasks and 
education-menus: error when trying to install together
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841548: autopkgtest: FTBFS: Tests failures

[Martin Pitt]

Control: tag -1 confirmed

Hello Lucas,


Lucas Nussbaum [2016-10-21 15:09 +0200]:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):

Not quite, the interesting portion is this:

|  File "/tmp/autopkgtest.2SwpBj/build.7IV/real-tree/debian/tests/t", line 2, 
in 
| from wand.image import Image
|   File 
"/tmp/autopkgtest.2SwpBj/deps/usr/lib/python3/dist-packages/wand/image.py", 
line 21, in 
| from .color import Color
|   File 
"/tmp/autopkgtest.2SwpBj/deps/usr/lib/python3/dist-packages/wand/color.py", 
line 12, in 
| from .version import QUANTUM_DEPTH
|   File 
"/tmp/autopkgtest.2SwpBj/deps/usr/lib/python3/dist-packages/wand/version.py", 
line 95, in 
| *map(int, MAGICK_RELEASE_DATE_STRING.split('-')))
| TypeError: Required argument 'month' (pos 2) not found

So it looks like imagemagic changed recently, so at first sight I'll
just need to adjust the test case to that.

I'll look into this ASAP, thanks for the report!

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

Bug#841364: clementine: no sound at all, "GStreamer encountered a general stream error."

[Thomas Pierson]

Hi Dio,

On 21/10/2016 18:53, Dio Oktarianos Putra wrote:
> Yeah, my clementine has that problem too which clementine need to depend on 
> gstreamer-0.10-ffmpeg.
> 
> But unfortunately, it's only avaliable on debian wheezy 
> (https://packages.debian.org/wheezy/gstreamer0.10-ffmpeg) and if you're using 
> >= jessie, it's only can be solved by deb-multimedia repo and install 
> gstreamer-0.10-ffmpeg manually.

In Stretch/Sid there are no Gstreamer0.10 and there are no Gstreamer
ffmpeg codecs anymore. The equivalent package you are looking for is
probably gstreamer1.0-libav. But this is only a set of optional plugins,
not a depend.

In fact, maybe you have the same gstreamer error message but I think you
have a totally different issue. And you are using unofficial
repositories like www.deb-multimedia.org which are known to be very
buggy and to cause breakages with many official packages.

So, don't hesitate to open a new bug report but please retry first with
a clean system without any unofficial package.

Thanks,
Thomas Pierson

Bug#837420: Bug#835148: please do not make GCC incompatible, we have dpkg-buildflags for this! (was Re: Bug#837420: Processed: PIE FTBFS are now RC)

[Bálint Réczey]

Hi Thorsten

2016-10-21 19:11 GMT+02:00 Thorsten Glaser :
> Adrian Bunk dixit:
>
>>gcc-6 6.2.0-7 uploaded to unstable on Tue 18 Oct 2016 defaults to PIE,
>>see #835148 for details.
>
> Oh, thanks.
>
> This is *so* *totally* the wrong approach, especially as we
> have dpkg-buildflags, which was introduced *precisely* for
> this purpose, and to make Debian’s GCC not incompatible even
> more with the rest of the world.

You may have missed them, but there was several lengthy threads [1]
on debian-devel discussing the possible solutions including the
inapplicability of dpkg-buildflags for this problem.

However, if you do have a better _working_ solution for enabling PIE
archive-wide, please share that.

I'm exploring possible options like patching (upstream) GCC to disable
PIE for kernel or patching (upstream) kernel to disable PIE when it can
be disabled.

AFAIK the linux package is the only problematic package were the
maintainer refused to disable PIE from packaging scripts.

Cheers,
Balint

[1] https://lists.debian.org/debian-devel/2016/05/msg00229.html

Bug#841545: Pending fixes for bugs in the liborlite-perl package

[pkg-perl-maintainers]

tag 841545 + pending
thanks

Some bugs in the liborlite-perl package are closed in revision
c3d278d44143a67246910d90a2365edc49b88eee in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/liborlite-perl.git/commit/?id=c3d278d

Commit message:

Add patch to fix SQLite VACUUM usage in test suite.

Thanks: Lucas Nussbaum for the bug report.
Closes: #841545

Processed: Pending fixes for bugs in the liborlite-perl package

[Debian Bug Tracking System]

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

> tag 841545 + pending
Bug #841545 [src:liborlite-perl] liborlite-perl: FTBFS: Tests failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841580: marked as done (pushpin: FTBFS: mkdir: cannot create directory '/usr/lib/pushpin': Permission denied)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 17:52:26 +
with message-id <e1bxdzw-0002b5...@franck.debian.org>
and subject line Bug#841580: fixed in pushpin 1.12.0-2
has caused the Debian Bug report #841580,
regarding pushpin: FTBFS: mkdir: cannot create directory '/usr/lib/pushpin': 
Permission denied
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.)


-- 
841580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pushpin
Version: 1.12.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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[5]: Entering directory '/<>/src/runner/runner'
> install -m 755 -p ../../../pushpin /usr/bin/pushpin
> install: cannot create regular file '/usr/bin/pushpin': Permission denied
> Makefile:347: recipe for target 'install_target' failed
> make[5]: [install_target] Error 1 (ignored)
> strip /usr/bin/pushpin
> strip: '/usr/bin/pushpin': No such file
> Makefile:347: recipe for target 'install_target' failed
> make[5]: [install_target] Error 1 (ignored)
> mkdir: cannot create directory '/usr/lib/pushpin': Permission denied
> Makefile:357: recipe for target 'install_libfiles' failed
> make[5]: *** [install_libfiles] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/pushpin_1.12.0-1_unstable.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: pushpin
Source-Version: 1.12.0-2

We believe that the bug you reported is fixed in the latest version of
pushpin, 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.
Jan Niehusmann <j...@debian.org> (supplier of updated pushpin 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: Fri, 21 Oct 2016 17:56:34 +0200
Source: pushpin
Binary: pushpin
Architecture: source
Version: 1.12.0-2
Distribution: unstable
Urgency: medium
Maintainer: Jan Niehusmann <j...@debian.org>
Changed-By: Jan Niehusmann <j...@debian.org>
Description:
 pushpin- HTTP reverse proxy server for streaming and long-polling services
Closes: 841580
Changes:
 pushpin (1.12.0-2) unstable; urgency=medium
 .
   * Set INSTALL_ROOT when calling dh_auto_install. (Closes: Bug#841580)
   * Depend on lsb-base (>= 3.0-6) to fix lintian warning
 init.d-script-needs-depends-on-lsb-base
Checksums-Sha1:
 70e4c746f4504b7c93bf352e217084ba396f24d2 1731 pushpin_1.12.0-2.dsc
 404adc1226e95b5c0b03268e478ef9915ead7e4d 19512 pushpin_1.12.0-2.debian.tar.xz
Checksums-Sha256:
 1d65fbb36f61cf9ac010ee43a897e015ef6424b8e36cbf552787595fa418bc49 1731 
pushpin_1.12.0-2.dsc
 f388b9356f36dd9467c67d5ebc97171e00c6011b0dac6133bb1b4cde60fa19e5 19512 
pushpin_1.12.0-2.debian.tar.xz
Files:
 dcb71842000ac9e45cd1c2031999dcf5 1731 net extra pushpin_1.12.0-2.dsc
 6bcb2a76ea8db1c244d79b5d4f675c0f 19512 net extra pushpin_1.12.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCgAGBQJYCj3OAAoJEMJAzpldAmsRr9YL+gO1i8wut0CGQZZWFqDEHaNV
u6eB2hRFg0tRDT0QmwYQ5SS3OcyJjqZe76flOh8WmjAhsJ

Processed: Pending fixes for bugs in the golang-google-cloud package

[Debian Bug Tracking System]

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

> tag 840311 + pending
Bug #840311 [src:golang-google-cloud] golang-google-cloud: FTBFS in testing 
(failing tests)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841562: marked as done (libvideo-fourcc-info-perl: FTBFS: dh_auto_build: perl Build returned exit code 255)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 17:45:08 +
with message-id <e1bxdss-0001zk...@franck.debian.org>
and subject line Bug#841562: fixed in libvideo-fourcc-info-perl 1.005-4
has caused the Debian Bug report #841562,
regarding libvideo-fourcc-info-perl: FTBFS: dh_auto_build: perl Build returned 
exit code 255
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.)


-- 
841562: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvideo-fourcc-info-perl
Version: 1.005-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
>  debian/rules build
> dh build
> dh: Compatibility levels before 9 are deprecated (level 8 in use)
>dh_testdir
>dh_update_autotools_config
>dh_auto_configure
> dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in 
> use)
>   perl -I. Build.PL --installdirs vendor
> Checking prerequisites...
>   recommends:
> *  Video::Info::Magic is not installed
> 
> ERRORS/WARNINGS FOUND IN PREREQUISITES.  You may wish to install the versions
> of the modules indicated above before proceeding with this installation
> 
> Run 'Build installdeps' to install missing prerequisites.
> 
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'Video-FourCC-Info' version '1.005'
>dh_auto_build
> dh_auto_build: Compatibility levels before 9 are deprecated (level 8 in use)
>   perl Build
> DBD::SQLite::db do failed: unknown database fourcc at inc/My/Builder.pm line 
> 77, <$fh> line 749.
> Building Video-FourCC-Info
> Opening database source file
> Creating database structure
> Inserting database data
> Optimizing database
> dh_auto_build: perl Build returned exit code 255
> debian/rules:4: recipe for target 'build' failed
> make: *** [build] Error 2

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/21/libvideo-fourcc-info-perl_1.005-3_unstable.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: libvideo-fourcc-info-perl
Source-Version: 1.005-4

We believe that the bug you reported is fixed in the latest version of
libvideo-fourcc-info-perl, 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.
gregor herrmann <gre...@debian.org> (supplier of updated 
libvideo-fourcc-info-perl 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: Fri, 21 Oct 2016 19:17:43 +0200
Source: libvideo-fourcc-info-perl
Binary: libvideo-fourcc-info-perl
Architecture: source
Version: 1.005-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <pkg-perl-maintain...@lists.alioth.debian.org>
Changed-By: gregor herrmann <gre...@debian.org>
Closes: 841562
Description: 
 libvideo-fourcc-info-perl - Perl module to find information about codecs from 
its FourCC
Changes:
 libvideo-fourcc-info-perl (1.005-4) unstable; urgency=medium
 .
   * Team upload.
 .
   

Bug#840311: Pending fixes for bugs in the golang-google-cloud package

[pkg-go-maintainers]

tag 840311 + pending
thanks

Some bugs in the golang-google-cloud package are closed in revision
52c087cfe9eb28f69c2422ca726c6936701f43c0 in branch 'master' by
Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-google-cloud.git/commit/?id=52c087c

Commit message:

Increase timeouts in tests to avoid build failures. Closes: #840311.

Bug#841573: marked as done (libdbix-class-perl: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 17:44:44 +
with message-id <e1bxds4-0001we...@franck.debian.org>
and subject line Bug#841573: fixed in libdbix-class-perl 0.082840-3
has caused the Debian Bug report #841573,
regarding libdbix-class-perl: FTBFS: Tests failures
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.)


-- 
841573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdbix-class-perl
Version: 0.082840-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> ok 2 - Overload/bless performance acceptable
> ok 3 # skip Not checking for bless handling as performance is OK
> 1..3
> # Auto checked 0 references for leaks - none detected
> ok
> t/zzz_sqlite_deadlock.t . skipped: Skipping test 
> on plain module install
> 
> Test Summary Report
> ---
> t/resultset/update_delete.t   (Wstat: 512 Tests: 49 
> Failed: 2)
>   Failed tests:  24-25
>   Non-zero exit status: 2
> Files=308, Tests=13392, 112 wallclock secs ( 2.17 usr  0.55 sys + 104.22 cusr 
>  5.84 csys = 112.78 CPU)
> Result: FAIL
> Failed 1/308 test programs. 2/13392 subtests failed.
> Makefile:1697: recipe for target 'test_dynamic' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/21/libdbix-class-perl_0.082840-2_unstable.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: libdbix-class-perl
Source-Version: 0.082840-3

We believe that the bug you reported is fixed in the latest version of
libdbix-class-perl, 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.
gregor herrmann <gre...@debian.org> (supplier of updated libdbix-class-perl 
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: Fri, 21 Oct 2016 18:46:33 +0200
Source: libdbix-class-perl
Binary: libdbix-class-perl
Architecture: source
Version: 0.082840-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group <pkg-perl-maintain...@lists.alioth.debian.org>
Changed-By: gregor herrmann <gre...@debian.org>
Closes: 841573
Description: 
 libdbix-class-perl - extensible and flexible object <-> relational mapper
Changes:
 libdbix-class-perl (0.082840-3) unstable; urgency=medium
 .
   * Add patch to adjust testsuite to libsqlite3-0 >= 3.14.
 Thanks to Lucas Nussbaum for the bug report, and to Peter Rabbitson for
 the help with the fix. (Closes: #841573)
Checksums-Sha1: 
 3949b8cd2d4f9b2348d8b4132e15859c58c1eb45 3387 libdbix-class-perl_0.082840-3.dsc
 17f76132d86af491e828d3d7d69319451a92ae8f 14792 
libdbix-class-perl_0.082840-3.debian.tar.xz
Checksums-Sha256: 
 4e20522e22d1e84ac9ea2815a8af493b60940c0a54d9797c34729853a9746330 3387 
libdbix-class-perl_0.082840-3.dsc
 7704d8c5cb7debce7e4ecd84714c93d4e0b610e2cc2028369c6d43241207718c 14792 
libdbix-class-perl_0.082840-3.debian.tar.xz
Files: 
 66c889fd35b5403717e911269fe82df1 3387 perl optiona

Bug#841511: python-bitbucket-api, python-bitbucket: error when trying to install together

[陳昌倬]

On Fri, Oct 21, 2016 at 11:42:03AM +0200, Andreas Beckmann wrote:
> This is a serious bug as it makes installation fail, and violates
> sections 7.6.1 and 10.1 of the policy. An optimal solution would
> consist in only one of the packages installing that file, and renaming
> or removing the file in the other package. Depending on the
> circumstances you might also consider Replace relations or file
> diversions. If the conflicting situation cannot be resolved then, as a
> last resort, the two packages have to declare a mutual
> Conflict. Please take into account that Replaces, Conflicts and
> diversions should only be used when packages provide different
> implementations for the same functionality.

I has checked the code, and these two packages provide very different
implementation of bitbucket API. So I think the solution is mutual
Conflict.

Another solution is removing python-bitbucket-api since I only need
python3-bitbucket-api for git-repo (#840371), and it is Python3 only.
Not sure if that is a good solution, but it can solve the problem too.


-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = EC9F 905D 866D BE46 A896  C827 BE0C 9242 03F4 552D
  BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Processed: Pending fixes for bugs in the libvideo-fourcc-info-perl package

[Debian Bug Tracking System]

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

> tag 841562 + pending
Bug #841562 [src:libvideo-fourcc-info-perl] libvideo-fourcc-info-perl: FTBFS: 
dh_auto_build: perl Build returned exit code 255
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841562: Pending fixes for bugs in the libvideo-fourcc-info-perl package

[pkg-perl-maintainers]

tag 841562 + pending
thanks

Some bugs in the libvideo-fourcc-info-perl package are closed in
revision f7ee99334d491f39357b27f7908d491f7cda9206 in branch 'master'
by gregor herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libvideo-fourcc-info-perl.git/commit/?id=f7ee993

Commit message:

Add patch to fix SQLite VACUUM command.

Thanks: Lucas Nussbaum for the bug report.
Closes: #841562

Bug#837420: please do not make GCC incompatible, we have dpkg-buildflags for this! (was Re: Bug#837420: Processed: PIE FTBFS are now RC)

[Thorsten Glaser]

Adrian Bunk dixit:

>gcc-6 6.2.0-7 uploaded to unstable on Tue 18 Oct 2016 defaults to PIE,
>see #835148 for details.

Oh, thanks.

This is *so* *totally* the wrong approach, especially as we
have dpkg-buildflags, which was introduced *precisely* for
this purpose, and to make Debian’s GCC not incompatible even
more with the rest of the world.

Matthias, please do revert this.

Thanks,
//mirabilos
-- 
Solange man keine schmutzigen Tricks macht, und ich meine *wirklich*
schmutzige Tricks, wie bei einer doppelt verketteten Liste beide
Pointer XORen und in nur einem Word speichern, funktioniert Boehm ganz
hervorragend.   -- Andreas Bogk über boehm-gc in d.a.s.r

Bug#841639: obmenu does not start [RESOLVED]

[byanbyanroryan]

Sorry, apparently it was my menu.xml file.  I changed tabs to spaces and 
deleted an ampersand inside an id value, and it works now.

Processed: Re: Bug#841634: virtualbox: Package unusable

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #841634 {Done: Gianfranco Costamagna } 
[virtualbox] virtualbox: Missing file /usr/lib/virtualbox/VBoxRT.so
Added tag(s) pending.

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

Bug#841634: virtualbox: Package unusable

[Gianfranco Costamagna]

control: tags -1 pending

I uploaded a fix a few minutes ago, please test 5.1.8-dfsg-6
thanks

G.





Il Venerdì 21 Ottobre 2016 18:33, Andrea  ha scritto:
Package: virtualbox
Version: 5.1.8-dfsg-4
Followup-For: Bug #841634

Tried purging and reinstalling virtualbox and virtualbox-qt, problem persists.
Package is unusable.

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

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

Versions of packages virtualbox depends on:
ii  adduser   3.115
ii  init-system-helpers   1.45
ii  libc6 2.24-5
ii  libcurl3-gnutls   7.50.1-1
ii  libdevmapper1.02.12:1.02.133-1
ii  libgcc1   1:6.2.0-9
ii  libgsoap102.8.35-3
ii  libpng16-16   1.6.25-2
ii  libpython3.5  3.5.2-6+b1
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libssl1.0.2   1.0.2j-1
ii  libstdc++66.2.0-9
ii  libvncserver1 0.9.10+dfsg-3+b1
ii  libvpx4   1.6.0-2
ii  libx11-6  2:1.6.3-1
ii  libxcursor1   1:1.1.14-1+b1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-2
ii  python3   3.5.1-4
pn  python3:any   
ii  virtualbox-dkms [virtualbox-modules]  5.1.8-dfsg-4
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages virtualbox recommends:
ii  libgl1-mesa-glx [libgl1]  12.0.3-1
ii  libqt5core5a  5.6.1+dfsg-3+b1
ii  libqt5opengl5 5.6.1+dfsg-3+b1
ii  libqt5widgets55.6.1+dfsg-3+b1
ii  virtualbox-qt 5.1.8-dfsg-4

Versions of packages virtualbox suggests:
pn  vde2
ii  virtualbox-guest-additions-iso  5.1.8-1

-- no debconf information

Bug#841573: Pending fixes for bugs in the libdbix-class-perl package

[pkg-perl-maintainers]

tag 841573 + pending
thanks

Some bugs in the libdbix-class-perl package are closed in revision
29957fe83392988fb0f9139e2e8094e6455acc88 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libdbix-class-perl.git/commit/?id=29957fe

Commit message:

Add patch to adjust testsuite to libsqlite3-0 >= 3.14.

Thanks: Lucas Nussbaum for the bug report, and to Peter Rabbitson for the 
help with the fix.
Closes: #841573

Bug#841553: marked as done (partclone: FTBFS: configure: error: *** Reiser4 depend library (libaal) not found)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 16:54:28 +
with message-id <e1bxd5q-0004pr...@franck.debian.org>
and subject line Bug#841613: fixed in reiser4progs 1.1.0-2
has caused the Debian Bug report #841613,
regarding partclone: FTBFS: configure: error: *** Reiser4 depend library 
(libaal) 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.)


-- 
841613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: partclone
Version: 0.2.88-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> configure: checking  for Reiser4 Library and Header files ... ...
> checking reiser4/libreiser4.h usability... yes
> checking reiser4/libreiser4.h presence... yes
> checking for reiser4/libreiser4.h... yes
> checking for aal_device_open in -laal... no
> configure: error: *** Reiser4 depend library (libaal) not found
>   "tail -v -n +0 config.log"

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/partclone_0.2.88-1_unstable.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: reiser4progs
Source-Version: 1.1.0-2

We believe that the bug you reported is fixed in the latest version of
reiser4progs, 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.
Felix Zielcke <fziel...@z-51.de> (supplier of updated reiser4progs 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: Fri, 21 Oct 2016 16:39:50 +0200
Source: reiser4progs
Binary: reiser4progs libreiser4-dev
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Felix Zielcke <fziel...@z-51.de>
Changed-By: Felix Zielcke <fziel...@z-51.de>
Description:
 libreiser4-dev - Reiser4's filesystem access and manipulation library. Devel 
files
 reiser4progs - administration utilities for the Reiser4 filesystem
Closes: 841613
Changes:
 reiser4progs (1.1.0-2) unstable; urgency=medium
 .
   * Build-depend on libaal >= 1.0.6-2 to fix FTBFS (Closes: #841613)
Checksums-Sha1:
 a4b05f22be49e05a515a446252939dbfe03b839c 1887 reiser4progs_1.1.0-2.dsc
 acf3d9d0d96bff975c0c6fb400387e547a11bb32 8036 
reiser4progs_1.1.0-2.debian.tar.xz
Checksums-Sha256:
 03de1bf935fca181d91251a901a1a96a7472f762480e319300617c73236b45ae 1887 
reiser4progs_1.1.0-2.dsc
 e620b3ba76cc7f8a40332a4e7f962269ff621ea0009d243f87c6827c34c40f7c 8036 
reiser4progs_1.1.0-2.debian.tar.xz
Files:
 d1860371eaf676107a01d1f5edf4d856 1887 admin optional reiser4progs_1.1.0-2.dsc
 541cb22f81c8c533705a2257eacbdd7c 8036 admin optional 
reiser4progs_1.1.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYCimcAAoJELdtuf/wtr8fyEMP/3ngwJYNJ4lHrD4CsyBGHOEZ
b3FZXdmt0ooi7+SI8YnOhDeeVQ2kKxlVzein/m+ZLDeuXMYmjaP6nIflKOM8z5hn
pW4qnIUV7nObppTo+iUYfq3ac6oMgyxz1YQ9Lu41PYR7FcltX5OttYQGtmD1lsOS
evybc+S3YhvrNuLZeCPanTN1IbrZqf5gbOqsTfKSWsHOxve1eC9FTxf+YegcmtHo
RJftDMNX9t3pMcARjn/Y4DdH0fgZgrnrxkN5tjYttfUp7Cf+wCK7KlDQ4noPcS3e
5pF2mjgj9uQJJg4rIB8B6FNV1zoZnUTX+

Bug#841364: clementine: no sound at all, "GStreamer encountered a general stream error."

[Dio Oktarianos Putra]

Package: clementine
Version: 1.2.3+dfsg-2+b1
Followup-For: Bug #841364

Dear Maintainer,

Yeah, my clementine has that problem too which clementine need to depend on 
gstreamer-0.10-ffmpeg.

But unfortunately, it's only avaliable on debian wheezy 
(https://packages.debian.org/wheezy/gstreamer0.10-ffmpeg) and if you're using 
>= jessie, it's only can be solved by deb-multimedia repo and install 
gstreamer-0.10-ffmpeg manually.


-- 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/2 CPU cores)
Locale: LANG=id_ID.UTF-8, LC_CTYPE=id_ID.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages clementine depends on:
ii  gstreamer0.10-plugins-base   0.10.36-2
ii  gstreamer0.10-plugins-good   0.10.31-3+nmu4+b1
ii  gstreamer0.10-plugins-ugly   0.10.19-2.1
ii  libc62.19-18+deb8u6
ii  libcdio130.83-4.2
ii  libchromaprint0  1.2-dmo2
ii  libechonest2.1   2.1.0-2
ii  libfftw3-double3 3.3.4-2
ii  libgcc1  1:4.9.2-10
ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u5
ii  libglib2.0-0 2.42.1-1+b1
ii  libgpod4 0.8.3-1.1+b1
ii  libgstreamer-plugins-base0.10-0  0.10.36-2
ii  libgstreamer0.10-0   0.10.36-1.5
ii  libimobiledevice41.1.6+dfsg-3.1
ii  liblastfm1   1.0.8-2
ii  libmtp9  1.1.8-1+b1
ii  libprojectm2 2.1.0+dfsg-1+b1
ii  libprotobuf9 2.6.1-1
ii  libqca2  2.0.3-6
ii  libqjson00.8.1-3
ii  libqt4-dbus  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-network   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-opengl4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-sql   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-sql-sqlite4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqt4-xml   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtcore4   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqxt-gui0  0.6.2-1+b1
ii  libstdc++6   4.9.2-10
ii  libtag1c2a   1.9.1-2.1
ii  libusb-1.0-0 2:1.0.19-1
ii  libx11-6 2:1.6.2-3
ii  libxml2  2.9.1+dfsg1-5+deb8u3
ii  projectm-data2.1.0+dfsg-1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages clementine recommends:
ii  gstreamer0.10-alsa  0.10.36-2

clementine suggests no packages.

-- no debconf information

Bug#841634: marked as done (virtualbox: Missing file /usr/lib/virtualbox/VBoxRT.so)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 16:56:52 +
with message-id 
and subject line Bug#841634: fixed in virtualbox 5.1.8-dfsg-5
has caused the Debian Bug report #841634,
regarding virtualbox: Missing file /usr/lib/virtualbox/VBoxRT.so
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.)


-- 
841634: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox
Version: 5.1.8-dfsg-4
Severity: grave

Dear Maintainer,

Virtualbox doesn't start :

$ virtualbox 
VirtualBox: supR3HardenedVerifyFileInternal: Failed to open 
"/usr/lib/virtualbox/VBoxRT.so": No such file or directory (2)

$ apt-file search VBoxRT.so
virtualbox: /usr/lib/virtualbox/components/VBoxRT.so

Christian

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

Kernel: Linux 4.1.34 (SMP w/8 CPU cores; PREEMPT)
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)

Versions of packages virtualbox depends on:
ii  adduser   3.115
ii  init-system-helpers   1.45
ii  libc6 2.24-5
ii  libcurl3-gnutls   7.50.1-1
ii  libdevmapper1.02.12:1.02.133-1
ii  libgcc1   1:6.2.0-9
ii  libgsoap102.8.35-3
ii  libpng16-16   1.6.25-2
ii  libpython3.5  3.5.2-6+b1
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libssl1.0.2   1.0.2j-1
ii  libstdc++66.2.0-9
ii  libvncserver1 0.9.10+dfsg-3+b1
ii  libvpx4   1.6.0-2
ii  libx11-6  2:1.6.3-1
ii  libxcursor1   1:1.1.14-1+b1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-2
ii  python3   3.5.1-4
pn  python3:any   
ii  virtualbox-dkms [virtualbox-modules]  5.1.8-dfsg-4
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages virtualbox recommends:
ii  libgl1-mesa-glx [libgl1]  12.0.3-1
ii  libqt5core5a  5.6.1+dfsg-3+b1
ii  libqt5opengl5 5.6.1+dfsg-3+b1
ii  libqt5widgets55.6.1+dfsg-3+b1
ii  virtualbox-qt 5.1.8-dfsg-4

Versions of packages virtualbox suggests:
pn  vde2
ii  virtualbox-guest-additions-iso  5.1.8-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: virtualbox
Source-Version: 5.1.8-dfsg-5

We believe that the bug you reported is fixed in the latest version of
virtualbox, 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.
Gianfranco Costamagna  (supplier of updated 
virtualbox 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: Fri, 21 Oct 2016 17:28:00 +0200
Source: virtualbox
Binary: virtualbox-qt virtualbox virtualbox-dkms virtualbox-source 
virtualbox-guest-dkms virtualbox-guest-source virtualbox-guest-x11 
virtualbox-guest-utils
Architecture: source
Version: 5.1.8-dfsg-5
Distribution: unstable
Urgency: high
Maintainer: Debian Virtualbox Team 

Changed-By: Gianfranco Costamagna 
Description:
 virtualbox - x86 virtualization solution - base binaries
 virtualbox-dkms - x86 virtualization solution - kernel module sources for dkms
 virtualbox-guest-dkms - x86 virtualization solution - guest addition module 
source for dk
 virtualbox-guest-source - x86 virtualization solution - guest addition module 
source
 virtualbox-guest-utils - x86 

Bug#837675: marked as done (libaal-dev: Please build libaal.a with -fPIC)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 16:54:28 +
with message-id 
and subject line Bug#841613: fixed in reiser4progs 1.1.0-2
has caused the Debian Bug report #841613,
regarding libaal-dev: Please build libaal.a with -fPIC
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.)


-- 
841613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libaal-dev
Version: 1.0.6-1
Severity: important
User: bal...@balintreczey.hu
Usertags: pie-bindnow-20160906
Justification: makes partclone FTBFS with extra hardening
Affects: partclone reiser4progs

Dear Maintainers,

During a rebuild of all packages in sid, partclone
failed to build on amd64 with patched GCC and dpkg. The root
cause seems to be that libaal.a is shipped as a non-PIC library.

The rebuild tested if packages are ready for a transition
enabling PIE and bindnow for amd64 (and selected architectures).

For more information about the changes to sid's dpkg and GCC please
visit:
 https://wiki.debian.org/Hardening/PIEByDefaultTransition

Relevant part of partclone's build log:
...
checking for aal_device_open in -laal... no
configure: error: *** Reiser4 depend library (libaal) not found
...

The full build log is available from:
 
https://people.debian.org/~rbalint/build-logs/pie-bindnow-20160906/partclone_0.2.88-1_amd64.build.gz

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Source: reiser4progs
Source-Version: 1.1.0-2

We believe that the bug you reported is fixed in the latest version of
reiser4progs, 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.
Felix Zielcke  (supplier of updated reiser4progs 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: Fri, 21 Oct 2016 16:39:50 +0200
Source: reiser4progs
Binary: reiser4progs libreiser4-dev
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Felix Zielcke 
Changed-By: Felix Zielcke 
Description:
 libreiser4-dev - Reiser4's filesystem access and manipulation library. Devel 
files
 reiser4progs - administration utilities for the Reiser4 filesystem
Closes: 841613
Changes:
 reiser4progs (1.1.0-2) unstable; urgency=medium
 .
   * Build-depend on libaal >= 1.0.6-2 to fix FTBFS (Closes: #841613)
Checksums-Sha1:
 a4b05f22be49e05a515a446252939dbfe03b839c 1887 reiser4progs_1.1.0-2.dsc
 acf3d9d0d96bff975c0c6fb400387e547a11bb32 8036 
reiser4progs_1.1.0-2.debian.tar.xz
Checksums-Sha256:
 03de1bf935fca181d91251a901a1a96a7472f762480e319300617c73236b45ae 1887 
reiser4progs_1.1.0-2.dsc
 e620b3ba76cc7f8a40332a4e7f962269ff621ea0009d243f87c6827c34c40f7c 8036 
reiser4progs_1.1.0-2.debian.tar.xz
Files:
 d1860371eaf676107a01d1f5edf4d856 1887 admin optional reiser4progs_1.1.0-2.dsc
 541cb22f81c8c533705a2257eacbdd7c 8036 admin optional 
reiser4progs_1.1.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYCimcAAoJELdtuf/wtr8fyEMP/3ngwJYNJ4lHrD4CsyBGHOEZ
b3FZXdmt0ooi7+SI8YnOhDeeVQ2kKxlVzein/m+ZLDeuXMYmjaP6nIflKOM8z5hn
pW4qnIUV7nObppTo+iUYfq3ac6oMgyxz1YQ9Lu41PYR7FcltX5OttYQGtmD1lsOS
evybc+S3YhvrNuLZeCPanTN1IbrZqf5gbOqsTfKSWsHOxve1eC9FTxf+YegcmtHo
RJftDMNX9t3pMcARjn/Y4DdH0fgZgrnrxkN5tjYttfUp7Cf+wCK7KlDQ4noPcS3e
5pF2mjgj9uQJJg4rIB8B6FNV1zoZnUTX+gkKEb0WRuvUIi2ZzElMU/L3BYAoYSNQ
AHqb1WYh11GRuIDASeCUx4QiE2/TD9b1zMG8rqD49spqkenlssNR2WbA6qmEaRvo
BjYPnRrIDWhEbxV0ggxXn68UR/ezfZPciSfsvHyiNpYcHdVJdHurg/2gwT3GH+BI
8EdZ+15EIX16+AxHjJD5T9+0gobrVqdbZEfiul5QsLbBWRlMx37a/uMqnCw6M1Md
QECjDvXXI8/rgCf+dqr2eFtqiz+RHRW0ANahE+6BetK8n/hqcORNig0xtYRhcHQh
IZCmyxc4UmbXWn+BnWyDADNlWCfZgzuj0d97UAslqx8v7DcIFgH0HpfW7KSOHwDo
9915ROVw9El4Ynjcaqwh
=6WbY
-END PGP SIGNATURE End Message ---

Bug#841613: marked as done (reiser4progs: FTBFS: configure: error: libaal not found; install libaal available at http://www.namesys.com/snapshots)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 16:54:28 +
with message-id <e1bxd5q-0004pr...@franck.debian.org>
and subject line Bug#841613: fixed in reiser4progs 1.1.0-2
has caused the Debian Bug report #841613,
regarding reiser4progs: FTBFS: configure: error: libaal not found; install 
libaal available at http://www.namesys.com/snapshots
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.)


-- 
841613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: reiser4progs
Version: 1.1.0-1.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> checking for special C compiler options needed for large files... no
> checking for _FILE_OFFSET_BITS value needed for large files... no
> configure: WARNING: Can't detect right _FILE_OFFSET_BITS. Will be forced to 
> 64bit.
> checking size of off_t... 8
> checking for aal_device_open in -laal... no
> configure: error: libaal not found; install libaal available at 
> http://www.namesys.com/snapshots
> debian/rules:43: recipe for target 'configure-reiser4progs-stamp' failed

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/reiser4progs_1.1.0-1.1_unstable.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: reiser4progs
Source-Version: 1.1.0-2

We believe that the bug you reported is fixed in the latest version of
reiser4progs, 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.
Felix Zielcke <fziel...@z-51.de> (supplier of updated reiser4progs 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: Fri, 21 Oct 2016 16:39:50 +0200
Source: reiser4progs
Binary: reiser4progs libreiser4-dev
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Felix Zielcke <fziel...@z-51.de>
Changed-By: Felix Zielcke <fziel...@z-51.de>
Description:
 libreiser4-dev - Reiser4's filesystem access and manipulation library. Devel 
files
 reiser4progs - administration utilities for the Reiser4 filesystem
Closes: 841613
Changes:
 reiser4progs (1.1.0-2) unstable; urgency=medium
 .
   * Build-depend on libaal >= 1.0.6-2 to fix FTBFS (Closes: #841613)
Checksums-Sha1:
 a4b05f22be49e05a515a446252939dbfe03b839c 1887 reiser4progs_1.1.0-2.dsc
 acf3d9d0d96bff975c0c6fb400387e547a11bb32 8036 
reiser4progs_1.1.0-2.debian.tar.xz
Checksums-Sha256:
 03de1bf935fca181d91251a901a1a96a7472f762480e319300617c73236b45ae 1887 
reiser4progs_1.1.0-2.dsc
 e620b3ba76cc7f8a40332a4e7f962269ff621ea0009d243f87c6827c34c40f7c 8036 
reiser4progs_1.1.0-2.debian.tar.xz
Files:
 d1860371eaf676107a01d1f5edf4d856 1887 admin optional reiser4progs_1.1.0-2.dsc
 541cb22f81c8c533705a2257eacbdd7c 8036 admin optional 
reiser4progs_1.1.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYCimcAAoJELdtuf/wtr8fyEMP/3ngwJYNJ4lHrD4CsyBGHOEZ
b3FZXdmt0ooi7+SI8YnOhDeeVQ2kKxlVzein/m+ZLDeuXMYmjaP6nIflKOM8z5hn
pW4qnIUV7nObppTo+iUYfq3ac6oMgyxz1YQ9Lu41PYR7FcltX5OttYQGtmD1lsOS
evybc+S3Yh

Bug#841566: marked as done (tarantool-lts: FTBFS: Could not find mysql development files)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 16:56:02 +
with message-id <e1bxd6w-0004w2...@franck.debian.org>
and subject line Bug#841566: fixed in tarantool-lts 1.5.5.36.gc9ed18a-1
has caused the Debian Bug report #841566,
regarding tarantool-lts: FTBFS: Could not find mysql development files
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.)


-- 
841566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tarantool-lts
Version: 1.5.5-18-g2998d20-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
>  debian/rules build
> test -x debian/rules
> mkdir -p "build-area"
> CDBS WARNING:DEB_DH_INSTALLINIT_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> set -e;   mv ./third_party/libeio/config.guess 
> ./third_party/libeio/config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./third_party/libeio/config.guess;   mv 
> ./third_party/libev/config.guess ./third_party/libev/config.guess.cdbs-orig; 
> cp --remove-destination /usr/share/misc/config.guess 
> ./third_party/libev/config.guess;
> set -e;   mv ./third_party/libeio/config.sub 
> ./third_party/libeio/config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./third_party/libeio/config.sub;   mv 
> ./third_party/libev/config.sub ./third_party/libev/config.sub.cdbs-orig; cp 
> --remove-destination /usr/share/misc/config.sub 
> ./third_party/libev/config.sub;
> cd build-area && cmake /<>/. -DCMAKE_INSTALL_PREFIX="/usr" 
> -DCMAKE_SKIP_RPATH=ON -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc/tarantool -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_INSTALL_LIBDIR=/usr/lib -DCMAKE_BUILD_TYPE=RelWithDebugInfo 
> -DENABLE_CLIENT=true -DWITH_MYSQL=ON -DWITH_POSTGRESQL=ON
> -- The C compiler identification is GNU 6.2.0
> -- The CXX compiler identification is GNU 6.2.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Check if the system is big endian
> -- Searching 16 bit integer
> -- Looking for sys/types.h
> -- Looking for sys/types.h - found
> -- Looking for stdint.h
> -- Looking for stdint.h - found
> -- Looking for stddef.h
> -- Looking for stddef.h - found
> -- Check size of unsigned short
> -- Check size of unsigned short - done
> -- Using unsigned short
> -- Check if the system is big endian - little endian
> -- Building for Linux
> -- Performing Test HAVE_STD_C11
> -- Performing Test HAVE_STD_C11 - Success
> -- Performing Test HAVE_STD_GNU99
> -- Performing Test HAVE_STD_GNU99 - Success
> -- Performing Test HAVE_STD_CXX11
> -- Performing Test HAVE_STD_CXX11 - Success
> -- Performing Test HAVE_STD_GNUXX0X
> -- Performing Test HAVE_STD_GNUXX0X - Success
> -- Performing Test HAVE_OPENMP
> -- Performing Test HAVE_OPENMP - Success
> -- Performing Test CC_HAS_WNO_UNUSED_CONST_VARIABLE
> -- Performing Test CC_HAS_WNO_UNUSED_CONST_VARIABLE - Success
> -- Performing Test CC_HAS_WNO_UNUSED_RESULT
> -- Performing Test CC_HAS_WNO_UNUSED_RESULT - Success
> -- Performing Test CC_HAS_WNO_UNUSED_VALUE
> -- Performing Test CC_HAS_WNO_UNUSED_VALUE - Success
> -- Performing Test CC_HAS_FNO_STRICT_ALIASING
> -- Performing Test CC_HAS_FNO_STRICT_ALIASING - Success
> -- Performing Test CC_HAS_WNO_COMMENT
> -- Performing Test CC_HAS_WNO_COMMENT - Success
> -- Performing Test CC_HAS_WNO_PARENTHESES
> -- Performing Test CC_HAS_WNO_PARENTHESES - Success
> -- Performing Test CC_HAS_WNO_UNDEFINED_INLINE
> -- Performing Test CC_HAS_WNO_UNDEFINED_INLINE - Success
> -- Performing Test CC_HAS_SSE2_INTRINSICS
> -- Performing Test CC_HAS_SSE2_INTRINSICS - Success
> -- Performing Test 

Processed: Pending fixes for bugs in the libdbix-class-perl package

[Debian Bug Tracking System]

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

> tag 841573 + pending
Bug #841573 [src:libdbix-class-perl] libdbix-class-perl: FTBFS: Tests failures
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#841547: marked as done (statcvs: FTBFS: [javac] /<>/src-temp/net/sf/statcvs/charts/SymbolicNameAnnotation.java:39: error: SymbolicNameAnnotation is not abstract and does not overr

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 16:55:41 +
with message-id <e1bxd6b-0004jv...@franck.debian.org>
and subject line Bug#841547: fixed in statcvs 1:0.7.0.dfsg-6
has caused the Debian Bug report #841547,
regarding statcvs: FTBFS: [javac] 
/<>/src-temp/net/sf/statcvs/charts/SymbolicNameAnnotation.java:39: 
error: SymbolicNameAnnotation is not abstract and does not override abstract 
method removeChangeListener(AnnotationChangeListener) in Annotation
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.)


-- 
841547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: statcvs
Version: 1:0.7.0.dfsg-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
>  debian/rules build
> test -x debian/rules
> mkdir -p "."
> jh_linkjars
> jh_build -J   
> touch debian/jh_build_stamp
> cd . && /usr/lib/jvm/default-java/bin/java -classpath 
> /usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/junit.jar:/usr/share/java/jcommon.jar:/usr/share/java/jfreechart.jar:/usr/share/java/jdom1.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dcompile.debug=true 
> -Dcompile.optimize=true -Dbuild.compiler=modern -buildfile build.xml jar 
> javadoc
> Buildfile: /<>/build.xml
> 
> init:
> [mkdir] Created dir: /<>/build
> 
> filter:
>  [copy] Copying 155 files to /<>/src-temp
>  [copy] Copied 19 empty directories to 1 empty directory under 
> /<>/src-temp
>  [copy] Copying 8 files to /<>/src-temp
> 
> compile:
> [javac] /<>/build.xml:60: warning: 'includeantruntime' was 
> not set, defaulting to build.sysclasspath=last; set to false for repeatable 
> builds
> [javac] Compiling 141 source files to /<>/build
> [javac] warning: [options] bootstrap class path not set in conjunction 
> with -source 1.4
> [javac] warning: [options] source value 1.4 is obsolete and will be 
> removed in a future release
> [javac] warning: [options] target value 1.4 is obsolete and will be 
> removed in a future release
> [javac] warning: [options] To suppress warnings about obsolete options, 
> use -Xlint:-options.
> [javac] 
> /<>/src-temp/net/sf/statcvs/charts/SymbolicNameAnnotation.java:39:
>  error: SymbolicNameAnnotation is not abstract and does not override abstract 
> method removeChangeListener(AnnotationChangeListener) in Annotation
> [javac] public class SymbolicNameAnnotation implements XYAnnotation {
> [javac]^
> [javac] Note: Some input files use or override a deprecated API.
> [javac] Note: Recompile with -Xlint:deprecation for details.
> [javac] 1 error
> [javac] 4 warnings
> 
> BUILD FAILED
> /<>/build.xml:60: Compile failed; see the compiler error output 
> for details.
> 
> Total time: 2 seconds
> /usr/share/cdbs/1/class/ant.mk:39: recipe for target 'debian/stamp-ant-build' 
> failed
> make: *** [debian/stamp-ant-build] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/statcvs_0.7.0.dfsg-5_unstable.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: statcvs
Source-Version: 1:0.7.0.dfsg-6

We believe that the bug you reported is fixed in the latest version of
stat

Bug#840732: marked as done (qbrew: FTBFS: install: cannot create regular file '/usr/bin/qbrew': Permission denied)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 16:53:32 +
with message-id 
and subject line Bug#840732: fixed in qbrew 0.4.1-7
has caused the Debian Bug report #840732,
regarding qbrew: FTBFS: install: cannot create regular file '/usr/bin/qbrew': 
Permission denied
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.)


-- 
840732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qbrew
Version: 0.4.1-6
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,

qbrew fails to build from source in unstable/amd64:

  [..]

  Setting up qt5-qmake:amd64 (5.6.1+dfsg-3+b1) ...
  Processing triggers for libc-bin (2.24-3) ...
  Processing triggers for udev (231-9) ...
  Setting up x11proto-gl-dev (1.4.17-1) ...
  Processing triggers for systemd (231-9) ...
  Setting up libmtdev1:amd64 (1.1.5-1) ...
  Setting up libpciaccess0:amd64 (0.13.4-1) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up libxkbcommon0:amd64 (0.6.1-1) ...
  Setting up libgudev-1.0-0:amd64 (230-3) ...
  Setting up libdrm-radeon1:amd64 (2.4.71-1) ...
  Setting up liborc-0.4-0:amd64 (1:0.4.26-1) ...
  Setting up libpcre16-3:amd64 (2:8.39-2) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libdrm-nouveau2:amd64 (2.4.71-1) ...
  Setting up x11-common (1:7.7+16) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libdbus-1-3:amd64 (1.10.12-1) ...
  Setting up libavahi-common-data:amd64 (0.6.32-1) ...
  Setting up libwayland-server0:amd64 (1.11.0-2) ...
  Setting up libwebp6:amd64 (0.5.1-2) ...
  Setting up libqt5core5a:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libgstreamer-plugins-base1.0-0:amd64 (1.8.3-1) ...
  Setting up libqt5dbus5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up fontconfig-config (2.11.0-6.7) ...
  Setting up libqt5network5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up x11proto-core-dev (7.0.29-1) ...
  Setting up libwacom2:amd64 (0.22-1) ...
  Setting up libdrm-amdgpu1:amd64 (2.4.71-1) ...
  Setting up libxshmfence-dev:amd64 (1.2-1) ...
  Setting up libgbm1:amd64 (12.0.3-1) ...
  Setting up libqt5test5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libinput10:amd64 (1.5.0-1) ...
  Setting up libharfbuzz0b:amd64 (1.2.7-1+b1) ...
  Setting up libxau-dev:amd64 (1:1.0.8-1) ...
  Setting up libdrm-intel1:amd64 (2.4.71-1) ...
  Setting up libxdmcp-dev:amd64 (1:1.1.2-1.1) ...
  Setting up libqt5clucene5:amd64 (5.6.1-2) ...
  Setting up libqt5xml5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libqt5sql5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libice6:amd64 (2:1.0.9-1+b1) ...
  Setting up libavahi-common3:amd64 (0.6.32-1) ...
  Setting up libxcb1:amd64 (1.12-1) ...
  Setting up x11proto-input-dev (2.3.2-1) ...
  Setting up libqt5concurrent5:amd64 (5.6.1+dfsg-3+b1) ...
  Setting up libxcb-xkb1:amd64 (1.12-1) ...
  Setting up libqt5qml5:amd64 (5.6.1-11) ...
  Setting up libxcb-xinerama0:amd64 (1.12-1) ...
  Setting up libxcb-present0:amd64 (1.12-1) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.7) ...
  Setting up qtbase5-dev-tools (5.6.1+dfsg-3+b1) ...
  Setting up libxcb-dri2-0:amd64 (1.12-1) ...
  Setting up libsm6:amd64 (2:1.2.2-1+b1) ...
  Setting up libxcb-dri3-0:amd64 (1.12-1) ...
  Setting up libxcb-glx0:amd64 (1.12-1) ...
  Setting up libxcb-randr0:amd64 (1.12-1) ...
  Setting up libxcb-xfixes0:amd64 (1.12-1) ...
  Setting up libxcb-icccm4:amd64 (0.4.1-1) ...
  Setting up libxcb-render0:amd64 (1.12-1) ...
  Setting up libxcb-util0:amd64 (0.3.8-3) ...
  Setting up libdrm-dev:amd64 (2.4.71-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxkbcommon-x11-0:amd64 (0.6.1-1) ...
  Setting up libxcb-sync1:amd64 (1.12-1) ...
  Setting up libx11-xcb1:amd64 (2:1.6.3-1) ...
  Setting up x11proto-xext-dev (7.3.0-1) ...
  Setting up libxcomposite1:amd64 (1:0.4.4-1) ...
  Setting up libxcb-shm0:amd64 (1.12-1) ...
  Setting up libxcb-shape0:amd64 (1.12-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libxcb1-dev:amd64 (1.12-1) ...
  Setting up libxcb-glx0-dev:amd64 (1.12-1) ...
  Setting up libavahi-client3:amd64 (0.6.32-1) ...
  Setting up libxcb-keysyms1:amd64 (0.4.0-1) ...
  Setting up libx11-dev:amd64 (2:1.6.3-1) 

Bug#841634: virtualbox: Missing file /usr/lib/virtualbox/VBoxRT.so

[Martin Steigerwald]

Am Freitag, 21. Oktober 2016, 18:37:13 CEST schrieb Martin Steigerwald:
> Hello Christian,
> 
> > $ virtualbox
> > VirtualBox: supR3HardenedVerifyFileInternal: Failed to open
> > "/usr/lib/virtualbox/VBoxRT.so": No such file or directory (2)
> > 
> > $ apt-file search VBoxRT.so
> > virtualbox: /usr/lib/virtualbox/components/VBoxRT.so
> 
> Which is a symlink to /usr/lib/virtualbox/VBoxRT.so, a broken one as the
> file does not exist as you found already:
> 
> merkaba:~> ls -l /usr/lib/virtualbox/components/VBoxRT.so
> lrwxrwxrwx 1 root root 12 Okt 20 14:34 /usr/lib/virtualbox/components/
> VBoxRT.so -> ../VBoxRT.so
> merkaba:~> file /usr/lib/virtualbox/components/VBoxRT.so
> /usr/lib/virtualbox/components/VBoxRT.so: broken symbolic link to
> ../VBoxRT.so

Downgrading to the version in testing fixes this issue for me:

merkaba:~> apt-show-versions | grep virtualbox
virtualbox:amd64/testing 5.1.6-dfsg-2+b1 uptodate
virtualbox:i386 not installed
virtualbox-dkms:all/testing 5.1.6-dfsg-2 uptodate
virtualbox-ext-pack:all/testing 5.1.6-2 uptodate
virtualbox-guest-additions-iso:all 5.1.8-1 newer than version in archive
virtualbox-qt:amd64/testing 5.1.6-dfsg-2+b1 uptodate
virtualbox-qt:i386 not installed

Thanks,
-- 
Martin

Processed: Fix for the naspro-core FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #837001 [src:naspro-core] naspro-core: FTBFS: fs.c:106:3: error: 
'readdir_r' is deprecated [-Werror=deprecated-declarations]
Added tag(s) patch.

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

Bug#837001: Fix for the naspro-core FTBFS

[Adrian Bunk]

Control: tags -1 +patch

readdir_r() is deprecated in glibc 2.24, and the result is a FTBFS
when a package both uses readdir_r() and builds with -Werror

This works around the issue by making deprecation warnings non-fatal.

--- debian/rules.old2016-10-21 16:26:50.0 +
+++ debian/rules2016-10-21 16:27:10.0 +
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+export DEB_CFLAGS_MAINT_APPEND = -Wno-error=deprecated-declarations
+
 export NATURALDOCS=/usr/bin/naturaldocs
 
 %:


cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#841634: virtualbox: Missing file /usr/lib/virtualbox/VBoxRT.so

[Martin Steigerwald]

Hello Christian,

> $ virtualbox
> VirtualBox: supR3HardenedVerifyFileInternal: Failed to open
> "/usr/lib/virtualbox/VBoxRT.so": No such file or directory (2)
> 
> $ apt-file search VBoxRT.so
> virtualbox: /usr/lib/virtualbox/components/VBoxRT.so

Which is a symlink to /usr/lib/virtualbox/VBoxRT.so, a broken one as the file 
does not exist as you found already:

merkaba:~> ls -l /usr/lib/virtualbox/components/VBoxRT.so
lrwxrwxrwx 1 root root 12 Okt 20 14:34 /usr/lib/virtualbox/components/
VBoxRT.so -> ../VBoxRT.so
merkaba:~> file /usr/lib/virtualbox/components/VBoxRT.so
/usr/lib/virtualbox/components/VBoxRT.so: broken symbolic link to ../VBoxRT.so

Thanks,
-- 
Martin

Bug#837420: Processed: PIE FTBFS are now RC

[Adrian Bunk]

On Fri, Oct 21, 2016 at 03:59:36PM +, Thorsten Glaser wrote:
> > PIE FTBFS are now RC
> 
> I don’t know whose stupid idea this is, but…
> 
> >> severity 837420 serious
> >Bug #837420 [src:dietlibc] dietlibc: FTBFS with bindnow and PIE enabled
> >Severity set to 'serious' from 'important'
> 
> … this can’t be right — a library cannot be built PIE, it must be
> built PIC instead.
>...

gcc-6 6.2.0-7 uploaded to unstable on Tue 18 Oct 2016 defaults to PIE,
see #835148 for details.

I did check that dietlibc does now FTBFS in unstable, and this is due to 
the compiler enabling PIE by default.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

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

[Eric Valette]

On 21/10/2016 16:36, Ben Hutchings wrote:

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




I disagree: you fix debian code but upstream kernel is also affected.
I wanted to compile the upstream 4.4.26 for the COW fixe and cannot.
Please revert.



It is absolutely supported (so long as you enable the necessary
features) and is common practice.  However, any bugs in some other
version of the kernel should not be assigned to src:linux.


Thanks Ben. BTW : I was originally arguing against the move to linux:src 
for a bug I opened on gcc because I was compiling upstream vanilla 
kernel code. (I never open a bug in linux:src as I barely use it except 
at first install).


I also dislike, gcc advocates forcibly merging bugs people have 
discovered rebuilding debian kernel from source and bug discovered 
compiling upstream vanilla kernel from source not even flagging them 
"upstream".


Nice game : they broke gcc with their patches (even if for possible good 
technical security reasons), and then, when bug are detected, even if 
bug report (like mine) explicitly specified upstream vanilla kernel code 
they reaffect it to linux:src asking for someone else to clean up the mess.


I do think (like you wrote elsewhere) that fixing debian kernel build is 
not a solution: until the needed patches are applied upstream, tagged 
for stable and have been propagated to the various LTS kernel,theses 
patches needs to be reverted.



-- eric

Bug#841503: marked as done (cryptsetup: initramfs cryptroot hook fails when /etc/cryptsetup-initramfs/conf-hook does not exist yet)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 16:39:06 +
with message-id 
and subject line Bug#841503: fixed in cryptsetup 2:1.7.2-5
has caused the Debian Bug report #841503,
regarding cryptsetup: initramfs cryptroot hook fails when 
/etc/cryptsetup-initramfs/conf-hook does not exist yet
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.)


-- 
841503: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cryptsetup
Version: 2:1.7.2-4
Severity: serious
Justification: upgrade fails

When cryptsetup is upgraded at the same time than the kernel
and when the kernel is configured before cryptsetup, the
kernel fails to configure with this error:

Paramétrage de linux-image-4.7.0-1-amd64 (4.7.6-1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.7.0-1-amd64
/usr/share/initramfs-tools/hooks/cryptroot: 663: .: Can't open 
/etc/cryptsetup-initramfs/conf-hook
E: /usr/share/initramfs-tools/hooks/cryptroot failed with return 2.
update-initramfs: failed for /boot/initrd.img-4.7.0-1-amd64 with 2.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2

The problem is that /etc/cryptsetup-initramfs/conf-hook is a conffile
and it is thus put into place only during the configuration of the
package and not an unpack time.

You should thus improve /usr/share/initramfs-tools/hooks/cryptroot to
tolerate the lack of /etc/cryptsetup-initramfs/conf-hook.

Thank you!

-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
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)

Versions of packages cryptsetup depends on:
ii  cryptsetup-bin 2:1.7.2-4
ii  debconf [debconf-2.0]  1.5.59
ii  dmsetup2:1.02.133-1
ii  libc6  2.24-3

Versions of packages cryptsetup recommends:
ii  busybox 1:1.22.0-19
ii  console-setup   1.151
ii  initramfs-tools [linux-initramfs-tool]  0.125
ii  kbd 2.0.3-2

Versions of packages cryptsetup suggests:
ii  dosfstools  4.0-2
pn  keyutils
ii  liblocale-gettext-perl  1.07-3+b1

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:1.7.2-5

We believe that the bug you reported is fixed in the latest version of
cryptsetup, 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.
Jonas Meurer  (supplier of updated cryptsetup 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: Fri, 21 Oct 2016 18:10:56 +0200
Source: cryptsetup
Binary: cryptsetup cryptsetup-bin libcryptsetup4 libcryptsetup-dev 
cryptsetup-udeb libcryptsetup4-udeb
Architecture: source amd64
Version: 2:1.7.2-5
Distribution: unstable
Urgency: high
Maintainer: Debian Cryptsetup Team 

Changed-By: Jonas Meurer 
Description:
 cryptsetup - disk encryption support - startup scripts
 cryptsetup-bin - disk encryption support - command line tools
 cryptsetup-udeb - disk encryption support - commandline tools (udeb) (udeb)
 libcryptsetup-dev - disk encryption support - development files
 libcryptsetup4 - disk encryption support - shared library
 libcryptsetup4-udeb - disk encryption support - shared library (udeb) (udeb)
Closes: 841503
Changes:
 cryptsetup (2:1.7.2-5) unstable; urgency=high
 .
   [ Guilhem Moulin ]
   * debian/upstream/signing-key.asc: add upstream's armored OpenPGP key,
 fingerprint 2A29 1824 3FDE 4664 8D06  86F9 D9B0 577B D93E 98FC.
   * debian/watch: add "pgpsigurlmangle" option so uscan(1) can automatically
 verify cryptographic signatures on release tarballs.
 .
   [ Jonas Meurer ]
   * debian/initramfs/cryptroot-hook: only source 

Bug#841634: virtualbox: Package unusable

[Andrea]

Package: virtualbox
Version: 5.1.8-dfsg-4
Followup-For: Bug #841634

Tried purging and reinstalling virtualbox and virtualbox-qt, problem persists.
Package is unusable.

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

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

Versions of packages virtualbox depends on:
ii  adduser   3.115
ii  init-system-helpers   1.45
ii  libc6 2.24-5
ii  libcurl3-gnutls   7.50.1-1
ii  libdevmapper1.02.12:1.02.133-1
ii  libgcc1   1:6.2.0-9
ii  libgsoap102.8.35-3
ii  libpng16-16   1.6.25-2
ii  libpython3.5  3.5.2-6+b1
ii  libsdl1.2debian   1.2.15+dfsg1-4
ii  libssl1.0.2   1.0.2j-1
ii  libstdc++66.2.0-9
ii  libvncserver1 0.9.10+dfsg-3+b1
ii  libvpx4   1.6.0-2
ii  libx11-6  2:1.6.3-1
ii  libxcursor1   1:1.1.14-1+b1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-2
ii  python3   3.5.1-4
pn  python3:any   
ii  virtualbox-dkms [virtualbox-modules]  5.1.8-dfsg-4
ii  zlib1g1:1.2.8.dfsg-2+b1

Versions of packages virtualbox recommends:
ii  libgl1-mesa-glx [libgl1]  12.0.3-1
ii  libqt5core5a  5.6.1+dfsg-3+b1
ii  libqt5opengl5 5.6.1+dfsg-3+b1
ii  libqt5widgets55.6.1+dfsg-3+b1
ii  virtualbox-qt 5.1.8-dfsg-4

Versions of packages virtualbox suggests:
pn  vde2
ii  virtualbox-guest-additions-iso  5.1.8-1

-- no debconf information

Bug#841591: migrate: FTBFS: Tests failures

[Thomas Goirand]

On 10/21/2016 03:19 PM, Lucas Nussbaum wrote:
> Source: migrate
> Version: 0.10.0-5
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161021 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):
>> # work even without python-migrate being installed
>> mkdir -p debian/bin
>> cp debian/migrate-for-tests debian/bin/migrate
>> sed -i "s#REPLACE_THIS_PATH#/<>#" debian/bin/migrate
>> # Create a minimalist egg-info, so that "import migrate"
>> # works and gets the correct version
>> mkdir -p sqlalchemy_migrate-0.10.0.egg-info
>> echo "Metadata-Version: 1.1" >sqlalchemy_migrate-0.10.0.egg-info/PKG-INFO
>> echo "Name: sqlalchemy-migrate" >>sqlalchemy_migrate-0.10.0.egg-info/PKG-INFO
>> echo "Version: 0.10.0" >>sqlalchemy_migrate-0.10.0.egg-info/PKG-INFO
>> # Launch the actual tests
>> /<>/debian/test.sh
>> ===> Preparing MySQL temp folder
>> mysql_install_db: [ERROR] unknown option '--force'
>> 2016-10-21 01:06:35 [ERROR]   Unrecognized options
>> debian/rules:58: recipe for target 'override_dh_auto_test' failed

FYI, I already know about this issue. This is related to MySQL 5.7,
which has different options for initializing the db. This patch fixes
the problem:

https://review.openstack.org/389570

and it will be uploaded soon.

Cheers,

Thomas Goirand (zigo)

Bug#811068: FTBFS: FAIL: check_vcnc: ../../test-driver: line 107: 77018 Aborted

[Santiago Vila]

Here is a backtrace for the "check_vcnc" failing test.

Note: This happens randomly, it takes several times trying "make check"
to get a segfault, and sometimes the test which fails is another
different one (this is why I provided the bt for #839444 first).


Core was generated by 
`/build/libgda5-5.2.4/tests/data-models/.libs/lt-check_vcnc'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fc037628f99 in vcontext_object_weak_notify_cb 
(context=0x55cce38fecf0, old_context_object=0x55cce3910060)
at gda-vconnection-data-model.c:607
607 g_mutex_unlock (context->vtable->context.mutex);
[Current thread is 1 (Thread 0x7fc037caaf40 (LWP 25407))]
(gdb) bt
#0  0x7fc037628f99 in vcontext_object_weak_notify_cb 
(context=0x55cce38fecf0, old_context_object=0x55cce3910060)
at gda-vconnection-data-model.c:607
#1  0x7fc037317b0f in ?? () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#2  0x7fc037318c05 in g_object_unref () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3  0x55cce16d2102 in check_simultanous_select_forward 
(virtual=0x55cce3398040) at check_vcnc.c:456
#4  main (argc=, argv=) at check_vcnc.c:95

Thanks.

Bug#837420: Processed: PIE FTBFS are now RC

[Thorsten Glaser]

> PIE FTBFS are now RC

I don’t know whose stupid idea this is, but…

>> severity 837420 serious
>Bug #837420 [src:dietlibc] dietlibc: FTBFS with bindnow and PIE enabled
>Severity set to 'serious' from 'important'

… this can’t be right — a library cannot be built PIE, it must be
built PIC instead.

@dietlibc maintainers: a solution for this (probably a proper one,
even) is to strip out -fpie/-fPIE from those CFLAGS and -pie from
those LDFLAGS we get from dpkg-buildflags during build, similar to
what mksh does for the builds against dietlibc:

if test $noopt = 1; then
x=-O0
else
x=-O2
fi
test $nodbg = 1 || x="$x -g"
dCFLAGS=$(dpkg-buildflags --get CFLAGS 2>/dev/null) || dCFLAGS=$x
# drop optimisation, debugging and PIC flags for mksh-static
for x in $dCFLAGS; do
case $x in
(-O*|-g*|-fPIE) ;;
(*) sCFLAGS="$sCFLAGS $x" ;;
esac
done
# add debugging flags right back, but more portable
test $nodbg = 1 || sCFLAGS="$sCFLAGS -g"

The first ($x) is for when dpkg-buildflags fails or does not
exist (backports), so it can probably be ignored. Then, we
drop -g* (like -gstabs and other fancy options that dietlibc
probably doesn’t like), anything PIE-related, and -Os (because
we set CC='diet -Os gcc').

HTH & HAND,
//mirabilos
-- 
21:49⎜ I have a question guys,
 ⎜Can I use my PC as SMTP server, I use Windows 7 .
 ⎜Already googled and Installed IIS
 ⎜but Still I can't send E-mail

Bug#841579: marked as done (libdr-tarantool-perl: FTBFS: build-dependency not installable: tarantool (< 1.6))

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 19:04:35 +0300
with message-id <20161021160435.gq9...@vdsl.uvw.ru>
and subject line Re: Bug#841579: libdr-tarantool-perl: FTBFS: build-dependency 
not installable: tarantool (< 1.6)
has caused the Debian Bug report #841579,
regarding libdr-tarantool-perl: FTBFS: build-dependency not installable: 
tarantool (< 1.6)
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.)


-- 
841579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdr-tarantool-perl
Version: 0.45-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 7), cdbs, libanyevent-perl, 
> libdevel-globaldestruction-perl, libjson-xs-perl, tarantool (<< 1.6) | 
> tarantool-lts, aspell-en, libtest-spelling-perl, liblist-moreutils-perl
> Filtered Build-Depends: debhelper (>= 7), cdbs, libanyevent-perl, 
> libdevel-globaldestruction-perl, libjson-xs-perl, tarantool (<< 1.6), 
> aspell-en, libtest-spelling-perl, liblist-moreutils-perl
> dpkg-deb: building package 'sbuild-build-depends-libdr-tarantool-perl-dummy' 
> in 
> '/<>/resolver-ot91zA/apt_archive/sbuild-build-depends-libdr-tarantool-perl-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-libdr-tarantool-perl-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-ot91zA/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-ot91zA/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-ot91zA/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-ot91zA/apt_archive ./ Sources [433 B]
> Get:5 copy:/<>/resolver-ot91zA/apt_archive ./ Packages [515 B]
> Fetched 1905 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install libdr-tarantool-perl build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-libdr-tarantool-perl-dummy : Depends: tarantool (< 1.6) 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/21/libdr-tarantool-perl_0.45-1_unstable.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 ---
16 Oct 0.45-1 was uploaded. The upload fixed the FTBFS, too. So I
close the ticket.

On 15:04 Fri 21 Oct

Processed: Merge with the actual bug

[Debian Bug Tracking System]

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

> reassign 837404 libbg1-dev
Bug #837404 [src:cvm] cvm: FTBFS with bindnow and PIE enabled
Bug reassigned from package 'src:cvm' to 'libbg1-dev'.
No longer marked as found in versions cvm/0.96-1.2.
Ignoring request to alter fixed versions of bug #837404 to the same values 
previously set
> severity 837709 serious
Bug #837709 {Done: Balint Reczey } [libbg1-dev] 
libbg1-dev: Please build libinstaller.a with -fPIC
Severity set to 'serious' from 'important'
> forcemerge 837709 837404
Bug #837709 {Done: Balint Reczey } [libbg1-dev] 
libbg1-dev: Please build libinstaller.a with -fPIC
Bug #837404 [libbg1-dev] cvm: FTBFS with bindnow and PIE enabled
Marked Bug as done
Added indication that 837404 affects ucspi-unix
Marked as fixed in versions bglibs/1.106-2.1.
The source libbg1-dev and version 1.106-2 do not appear to match any binary 
packages
Marked as found in versions libbg1-dev/1.106-2.
Merged 837404 837709
> retitle 837404 libbg1-dev: Please build libinstaller.a with -fPIC
Bug #837404 {Done: Balint Reczey } [libbg1-dev] cvm: 
FTBFS with bindnow and PIE enabled
Bug #837709 {Done: Balint Reczey } [libbg1-dev] 
libbg1-dev: Please build libinstaller.a with -fPIC
Changed Bug title to 'libbg1-dev: Please build libinstaller.a with -fPIC' from 
'cvm: FTBFS with bindnow and PIE enabled'.
Ignoring request to change the title of bug#837709 to the same title
> affects 837404 src:cvm
Bug #837404 {Done: Balint Reczey } [libbg1-dev] 
libbg1-dev: Please build libinstaller.a with -fPIC
Bug #837709 {Done: Balint Reczey } [libbg1-dev] 
libbg1-dev: Please build libinstaller.a with -fPIC
Added indication that 837404 affects src:cvm
Added indication that 837709 affects src:cvm
> thanks
Stopping processing here.

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

Bug#835705: marked as done (umbrello: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 18:10:50 +0200
with message-id <20161021161050.ipnlrulbpb3ps...@gnuservers.com.ar>
and subject line Re: Bug#835705: umbrello: FTBFS: dh_install: missing files, 
aborting
has caused the Debian Bug report #835705,
regarding umbrello: 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.)


-- 
835705: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: umbrello
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[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[4]: Nothing to be done for 'preinstall'.
> make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> Install the project...
> /usr/bin/cmake -P cmake_install.cmake
> -- Install configuration: "Debian"
> -- Installing: /<>/debian/tmp/usr/bin/umbrello
> -- Installing: 
> /<>/debian/tmp/usr/share/applications/org.kde.umbrello.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/metainfo/org.kde.umbrello.appdata.xml
> -- Installing: 
> /<>/debian/tmp/usr/share/kxmlgui5/umbrello/umbrelloui.rc
> -- Installing: /<>/debian/tmp/usr/share/umbrello/xmi2docbook.xsl
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/docbook2xhtml.xsl
> -- Installing: /<>/debian/tmp/usr/share/umbrello/xmi.css
> -- Installing: /<>/debian/tmp/usr/share/umbrello/common.ent
> -- Installing: /<>/debian/tmp/usr/share/umbrello/layouts
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/class-vertical.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/activity-vertical.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/class-horizontal.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/activity-export.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/usecase-default.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/state-vertical.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/state-export.desktop
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/layouts/class-export.desktop
> -- Installing: /<>/debian/tmp/usr/share/umbrello/pics/actor.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/aggregation.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-horizontal-left.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-horizontal-right.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-vertical-top.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-vertical-bottom.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-vertical-center.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/align-horizontal-center.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/distribute-vertical.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/distribute-horizontal.png
> -- Installing: /<>/debian/tmp/usr/share/umbrello/pics/anchor.png
> -- Installing: /<>/debian/tmp/usr/share/umbrello/pics/andline.png
> -- Installing: /<>/debian/tmp/usr/share/umbrello/pics/arrow.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/association.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/choice-rhomb.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/choice-round.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/combined_fragment.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/component.png
> -- Installing: /<>/debian/tmp/usr/share/umbrello/pics/region.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/composition.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/containment.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVglobal_meth.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVglobal_var.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVimplementation_meth.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVimplementation_signal.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVimplementation_slot.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVimplementation_var.png
> -- Installing: 
> /<>/debian/tmp/usr/share/umbrello/pics/CVnamespace.png
> -- Installing: 
> 

Bug#837712: Processed: severity of 837712 is serious

[Mark Brown]

On Fri, Oct 21, 2016 at 05:45:39PM +0200, Lucas Nussbaum wrote:
> On 21/10/16 at 16:32 +0100, Mark Brown wrote:

> > > Bug #837712 [src:xemacs21] xemacs21: FTBFS with bindnow and PIE enabled
> > > Severity set to 'serious' from 'important'

> > I've still not seen any usable reproduction instructions.

> Well it fails to build in a standard, up-to-date unstable chroot here.
> That was what I implied with the '# now fails in unstable' comment in my
> BTS control message.

> You cannot reproduce it? Could you send a build log so that we could
> diff it with mine?

Oh, someone uploaded these compilers to unstable?  Nice :(  I'll go take
a look.  Comments in the BTS messages really aren't visible, the
messages are very noisy so it's hard to spot them.


signature.asc
Description: PGP signature

Bug#835282: marked as done (rocs: FTBFS: dh_install: Cannot find (any matches for) "usr/share/appdata/org.kde.rocs.appdata.xml" (tried in "." and "debian/tmp"))

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 18:03:17 +0200
with message-id <20161021160317.vxq53rk56rbuu...@gnuservers.com.ar>
and subject line Re: Bug#835282: rocs: FTBFS: dh_install: Cannot find (any 
matches for) "usr/share/appdata/org.kde.rocs.appdata.xml" (tried in "." and 
"debian/tmp")
has caused the Debian Bug report #835282,
regarding rocs: FTBFS: dh_install: Cannot find (any matches for) 
"usr/share/appdata/org.kde.rocs.appdata.xml" (tried in "." and "debian/tmp")
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.)


-- 
835282: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rocs
Version: 4:16.04.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,

rocs fails to build from source in unstable/amd64:

  [..]

  [ 12%] Built target rocs_automoc
  [ 12%] Built target TestProject_automoc
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu'
  make -f libgraphtheory/CMakeFiles/rocsgraphtheory.dir/build.make 
libgraphtheory/CMakeFiles/rocsgraphtheory.dir/build
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu'
  make[5]: Nothing to be done for 
'libgraphtheory/CMakeFiles/rocsgraphtheory.dir/build'.
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu'
  [ 36%] Built target rocsgraphtheory
  make -f 
libgraphtheory/fileformats/tgf/CMakeFiles/tgffileformat.dir/build.make 
libgraphtheory/fileformats/tgf/CMakeFiles/tgffileformat.dir/depend
  make -f 
libgraphtheory/fileformats/tgf/autotests/CMakeFiles/TestTgfFileFormat.dir/build.make
 
libgraphtheory/fileformats/tgf/autotests/CMakeFiles/TestTgfFileFormat.dir/depend
  make -f 
libgraphtheory/fileformats/tikz/CMakeFiles/tikzfileformat.dir/build.make 
libgraphtheory/fileformats/tikz/CMakeFiles/tikzfileformat.dir/depend
  make -f 
libgraphtheory/fileformats/tikz/autotests/CMakeFiles/TestTikzFileFormat.dir/build.make
 
libgraphtheory/fileformats/tikz/autotests/CMakeFiles/TestTikzFileFormat.dir/depend
  make -f 
libgraphtheory/fileformats/dot/CMakeFiles/dotfileformat.dir/build.make 
libgraphtheory/fileformats/dot/CMakeFiles/dotfileformat.dir/depend
  make -f 
libgraphtheory/fileformats/dot/autotests/CMakeFiles/TestDotFileFormat.dir/build.make
 
libgraphtheory/fileformats/dot/autotests/CMakeFiles/TestDotFileFormat.dir/depend
  make -f 
libgraphtheory/fileformats/gml/CMakeFiles/gmlfileformat.dir/build.make 
libgraphtheory/fileformats/gml/CMakeFiles/gmlfileformat.dir/depend
  make -f 
libgraphtheory/fileformats/gml/autotests/CMakeFiles/TestGmlFileFormat.dir/build.make
 
libgraphtheory/fileformats/gml/autotests/CMakeFiles/TestGmlFileFormat.dir/depend
  make -f 
libgraphtheory/fileformats/rocs1/CMakeFiles/rocs1fileformat.dir/build.make 
libgraphtheory/fileformats/rocs1/CMakeFiles/rocs1fileformat.dir/depend
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu'
  cd 
/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1 
/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/libgraphtheory/fileformats/tgf
 
/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu
 
/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu/libgraphtheory/fileformats/tgf
 
/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu/libgraphtheory/fileformats/tgf/CMakeFiles/tgffileformat.dir/DependInfo.cmake
 --color=
  make[5]: Entering directory 
'/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu'
  cd 
/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu
 && /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1 
/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/libgraphtheory/fileformats/tgf/autotests
 
/home/lamby/temp/cdt.20160824083942.KtQYasuoCx.db.rocs/rocs-16.04.1/obj-x86_64-linux-gnu
 

Bug#841566: marked as done (tarantool-lts: FTBFS: Could not find mysql development files)

[Debian Bug Tracking System]

Your message dated Fri, 21 Oct 2016 18:56:23 +0300
with message-id <20161021155623.gp9...@vdsl.uvw.ru>
and subject line Re: Bug#841566: tarantool-lts: FTBFS: Could not find mysql 
development files
has caused the Debian Bug report #841566,
regarding tarantool-lts: FTBFS: Could not find mysql development files
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.)


-- 
841566: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841566
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tarantool-lts
Version: 1.5.5-18-g2998d20-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
>  debian/rules build
> test -x debian/rules
> mkdir -p "build-area"
> CDBS WARNING:DEB_DH_INSTALLINIT_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> set -e;   mv ./third_party/libeio/config.guess 
> ./third_party/libeio/config.guess.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.guess ./third_party/libeio/config.guess;   mv 
> ./third_party/libev/config.guess ./third_party/libev/config.guess.cdbs-orig; 
> cp --remove-destination /usr/share/misc/config.guess 
> ./third_party/libev/config.guess;
> set -e;   mv ./third_party/libeio/config.sub 
> ./third_party/libeio/config.sub.cdbs-orig; cp --remove-destination 
> /usr/share/misc/config.sub ./third_party/libeio/config.sub;   mv 
> ./third_party/libev/config.sub ./third_party/libev/config.sub.cdbs-orig; cp 
> --remove-destination /usr/share/misc/config.sub 
> ./third_party/libev/config.sub;
> cd build-area && cmake /<>/. -DCMAKE_INSTALL_PREFIX="/usr" 
> -DCMAKE_SKIP_RPATH=ON -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_INSTALL_SYSCONFDIR=/etc/tarantool -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
> -DCMAKE_INSTALL_LIBDIR=/usr/lib -DCMAKE_BUILD_TYPE=RelWithDebugInfo 
> -DENABLE_CLIENT=true -DWITH_MYSQL=ON -DWITH_POSTGRESQL=ON
> -- The C compiler identification is GNU 6.2.0
> -- The CXX compiler identification is GNU 6.2.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Check if the system is big endian
> -- Searching 16 bit integer
> -- Looking for sys/types.h
> -- Looking for sys/types.h - found
> -- Looking for stdint.h
> -- Looking for stdint.h - found
> -- Looking for stddef.h
> -- Looking for stddef.h - found
> -- Check size of unsigned short
> -- Check size of unsigned short - done
> -- Using unsigned short
> -- Check if the system is big endian - little endian
> -- Building for Linux
> -- Performing Test HAVE_STD_C11
> -- Performing Test HAVE_STD_C11 - Success
> -- Performing Test HAVE_STD_GNU99
> -- Performing Test HAVE_STD_GNU99 - Success
> -- Performing Test HAVE_STD_CXX11
> -- Performing Test HAVE_STD_CXX11 - Success
> -- Performing Test HAVE_STD_GNUXX0X
> -- Performing Test HAVE_STD_GNUXX0X - Success
> -- Performing Test HAVE_OPENMP
> -- Performing Test HAVE_OPENMP - Success
> -- Performing Test CC_HAS_WNO_UNUSED_CONST_VARIABLE
> -- Performing Test CC_HAS_WNO_UNUSED_CONST_VARIABLE - Success
> -- Performing Test CC_HAS_WNO_UNUSED_RESULT
> -- Performing Test CC_HAS_WNO_UNUSED_RESULT - Success
> -- Performing Test CC_HAS_WNO_UNUSED_VALUE
> -- Performing Test CC_HAS_WNO_UNUSED_VALUE - Success
> -- Performing Test CC_HAS_FNO_STRICT_ALIASING
> -- Performing Test CC_HAS_FNO_STRICT_ALIASING - Success
> -- Performing Test CC_HAS_WNO_COMMENT
> -- Performing Test CC_HAS_WNO_COMMENT - Success
> -- Performing Test CC_HAS_WNO_PARENTHESES
> -- Performing Test CC_HAS_WNO_PARENTHESES - Success
> -- Performing Test CC_HAS_WNO_UNDEFINED_INLINE
> -- Performing Test CC_HAS_WNO_UNDEFINED_INLINE - Success
> -- Performing Test CC_HAS_SSE2_INTRINSICS
> -- Performing Test CC_HAS_SSE2_INTRINSICS - Success
>

Bug#841551: emacs25: FTBFS: segmentation fault

[Sven Joachim]

On 2016-10-21 15:35 +0200, Lucas Nussbaum wrote:

> Source: emacs25
> Version: 25.1+1-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161021 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):
>> [...]
>> Loading /<>/emacs25-25.1+1/debian/build-x/lisp/tooltip.el 
>> (source)...
>> Finding pointers to doc strings...
>> Finding pointers to doc strings...done
>> Dumping under the name emacs
>> Makefile:736: recipe for target 'bootstrap-emacs' failed
>> make[3]: *** [bootstrap-emacs] Segmentation fault
>> make[3]: Leaving directory '/<>/emacs25-25.1+1/debian/build-x/src'
>> Makefile:400: recipe for target 'src' failed
>> make[2]: *** [src] Error 2

Apparently emacs cannot be built as a position independent executable,
for whatever reason.  Cherry-picking the following commit from the
emacs-25 branch should help:
http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-25=99892eeec8990884ef38601f14038ec6dc227741

See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24682 for more
information.

Cheers,
   Sven