Bug#845037: libschroedinger-1.0-0: is this package fit for stretch?

[Sebastian Dröge]

On Sun, 2016-11-20 at 11:57 +0100, Moritz Muehlenhoff wrote:

> > Thus I think stretch would be better of without this library.
> > 
> > As replacement, ffmpeg has a decent dirac decoder and also a
> > vc2 encoder, which is the intra-only subset of dirac that
> > got standardized by the SMPTE.
> 
> Andreas, thanks for filing this bug. Fully agreed from my side.

I tend to agree here. Note however that VC2 is only a subset of Dirac,
so we'll definitely lose some (probably unimportant) functionality
here.

Current reverse dependencies are
 ffmpeg
 gmerlin-avdecoder
 gst-plugins-bad1.0
 libquicktime
 liquidsoap
 lives
 ocaml-schroedinger
 vlc

Except for the ocaml bindings, this should all be a matter of simply
disabling the functionality.

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

Processed: Sent upstream

[Debian Bug Tracking System]

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

> forwarded 844233 
> https://bitbucket.org/ecollins/passlib/issues/82/non-deterministic-test-failure
Bug #844233 [src:python-passlib] python-passlib: FTBFS with probability of 
0.46% due to non-deterministic testsuite
Set Bug forwarded-to-address to 
'https://bitbucket.org/ecollins/passlib/issues/82/non-deterministic-test-failure'.
> tags 844233 +upstream
Bug #844233 [src:python-passlib] python-passlib: FTBFS with probability of 
0.46% due to non-deterministic testsuite
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: Re: Bug#844239: request-tracker4: FTBFS: t/web/gnupg-select-keys-on-update.t failure

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #844239 [request-tracker4] request-tracker4: FTBFS: 
t/web/gnupg-select-keys-on-update.t failure
Bug #844842 [request-tracker4] rt-authen-externalauth: FTBFS: build-dependency 
not installable: request-tracker4
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
> tag -1 unreproducible
Bug #844239 [request-tracker4] request-tracker4: FTBFS: 
t/web/gnupg-select-keys-on-update.t failure
Bug #844842 [request-tracker4] rt-authen-externalauth: FTBFS: build-dependency 
not installable: request-tracker4
Added tag(s) unreproducible.
Added tag(s) unreproducible.

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

Bug#844239: request-tracker4: FTBFS: t/web/gnupg-select-keys-on-update.t failure

[Niko Tyni]

Control: severity -1 important
Control: tag -1 unreproducible

On Mon, Nov 21, 2016 at 12:45:19AM +0100, Emilio Pozuelo Monfort wrote:
> On 20/11/16 21:32, Niko Tyni wrote:
> > On Sun, Nov 13, 2016 at 07:13:54PM +0200, Niko Tyni wrote:
> >> Package: request-tracker4
> >> Version: 4.2.13-3
> >> Severity: serious
> >>
> >> This package failed to build on the 'all' buildd:
> >>
> >>   
> >> https://buildd.debian.org/status/fetch.php?pkg=request-tracker4=all=4.2.13-3=1477439960
> >>
> >>   #   Failed test 'problems with passphrase'
> >>   #   at t/web/gnupg-select-keys-on-update.t line 40.
> >>   # searched: "\x{0a}\x{0a}\x{0a}  
> >> \x{0a} >>   #   can't find: "unable to sign outgoing email messages"
> >>   # LCSS: " message"
> >>   # LCSS context: " > 
> > I can't reproduce this locally, and neither can others. It obviously
> > worked for Dominic when he uploaded it.
> > 
> > @w-b-team: could you please give it back to see if this persists on
> > the buildds?
> > 
> > gb request-tracker4_4.2.13-3 . all
> 
> Given back.

Thanks. That worked, so downgrading & tagging for now.

I see it's in NEW now, seems like an arch:all glitch in dak...
-- 
Niko

Bug#845182: yaskkserv: systemd support are broken

[Youhei SASAKI]

Package: yaskkserv
Version: 1.1.0-1
Severity: grave

Dear Maintainer,

1. This version provide "yaskkserv.service", but missing Build-Depends
   "libsystemd-dev", need /usr/include/systemd/sd-daemon.h

   Thus this daemon does not provide the feature of systemd socket activation.

2. The "yaskkerv.service" provided this version depends
   "yaskkserv.socket". But "yaskkserv.socket" was not privided.

3. In systemd Unit file, we can't use shell expression.
   If you parse shell expression, use /bin/sh as follows:

  ExecStart=/bin/sh -c ". /etc/default/yaskkserv; exec 
/usr/sbin/$YASKKSERV_BIN --no-daemonize $DAEMON_OPTS $DIC_LIST"

Git format-patch attached.

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

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

Versions of packages yaskkserv depends on:
ii  libc62.24-5
ii  libgcc1  1:6.2.1-4
ii  libgnutls-openssl27  3.5.6-7
ii  libgnutls30  3.5.6-7
ii  libstdc++6   6.2.1-4
ii  lsb-base 9.20161101
ii  skkdic   20160507-1

Versions of packages yaskkserv recommends:
ii  skkdic-extra  20160507-1

yaskkserv suggests no packages.

-- Configuration Files:
/etc/default/yaskkserv changed:
YASKKSERV_BIN="yaskkserv_hairy"
SIMPLE_OPTS="--log-level=1 --max-connection=512 --port=1178"
NORMAL_OPTS="${SIMPLE_OPTS}"
HAIRY_OPTS="${NORMAL_OPTS} --server-completion-midasi-length=2048 
--server-completion-midasi-string-size=262144 --server-completion-test=1 
--google-japanese-input=notfound --google-japanese-input-timeout=1"
DAEMON_OPTS="${HAIRY_OPTS}"
LOCAL_DICS="\
/usr/local/share/skkdic/SKK-JISYO.chibutsu \
/usr/local/share/skkdic/SKK-JISYO.tanudic4 \
/usr/local/share/skkdic/SKK-JISYO.matsucon \
/usr/local/share/skkdic/SKK-JISYO.hatenakey
"
PKG_DICS="/etc/alternatives/SKK-JISYO \
SKK-JISYO.jinmei \
SKK-JISYO.geo \
SKK-JISYO.propernoun \
SKK-JISYO.not_wrong
"
DICS="${PKG_DICS} ${LOCAL_DICS}"
for DIC in ${DICS}
do
DICBN=`basename $DIC`
DIC_LIST="${DIC_LIST} /usr/share/yaskkserv/${DICBN}.yaskkserv"
done


-- no debconf information
From 6d87ebab1a1c18db30e81d3e62233b124fa376de Mon Sep 17 00:00:00 2001
From: Youhei SASAKI 
Date: Mon, 21 Nov 2016 16:00:43 +0900
Subject: [PATCH] Fix systemd support

Signed-off-by: Youhei SASAKI 
---
 debian/control   | 2 +-
 debian/rules | 2 +-
 debian/yaskkserv.install | 1 +
 debian/yaskkserv.service | 3 +--
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/debian/control b/debian/control
index cb683ec..af2722d 100644
--- a/debian/control
+++ b/debian/control
@@ -4,7 +4,7 @@ Priority: extra
 Maintainer: KURASHIKI Satoru 
 Uploaders: Tatsuya Kinoshita 
 Homepage: http://umiushi.org/~wac/yaskkserv/
-Build-Depends: debhelper (>= 9), libgnutls28-dev
+Build-Depends: debhelper (>= 9.20160709~), libgnutls28-dev, libsystemd-dev
 Standards-Version: 3.9.8
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/yaskkserv.git
 Vcs-Browser: https://anonscm.debian.org/git/collab-maint/yaskkserv.git
diff --git a/debian/rules b/debian/rules
index e5c6cc1..fb0dfb1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,7 +9,7 @@ export DEB_LDFLAGS_MAINT_APPEND = -defs
 export DH_VERBOSE=1
 
 %:
-   dh $@
+   dh $@ --with systemd
 
 override_dh_auto_configure:
./configure --prefix=$(CURDIR)/debian/yaskkserv/usr --compiler=g++ 
--enable-google-japanese-input --enable-google-suggest
diff --git a/debian/yaskkserv.install b/debian/yaskkserv.install
index b8d1e0a..1654449 100644
--- a/debian/yaskkserv.install
+++ b/debian/yaskkserv.install
@@ -1 +1,2 @@
 debian/update-skkdic-yaskkserv usr/sbin
+debian/yaskkserv.socketlib/systemd/system/
diff --git a/debian/yaskkserv.service b/debian/yaskkserv.service
index 543284e..41b19a4 100644
--- a/debian/yaskkserv.service
+++ b/debian/yaskkserv.service
@@ -5,8 +5,7 @@ Requires=yaskkserv.socket
 
 [Service]
 User=nobody
-EnvironmentFile=-/etc/default/yaskkserv
-ExecStart=/usr/sbin/${YASKKSERV_BIN} --no-daemonize ${DAEMON_OPTS} ${DIC_LIST}
+ExecStart=/bin/sh -c ". /etc/default/yaskkserv; exec /usr/sbin/$YASKKSERV_BIN 
--no-daemonize $DAEMON_OPTS $DIC_LIST"
 
 [Install]
 WantedBy=multi-user.target
-- 
2.10.2

Bug#844834: marked as done (libapache2-mod-auth-openid: FTBFS: build-dependency not installable: libopkele-dev (>= 2.0.4+git20140305.9651b55))

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 06:48:36 +
with message-id 
and subject line Bug#844834: fixed in libapache2-mod-auth-openid 0.8-3
has caused the Debian Bug report #844834,
regarding libapache2-mod-auth-openid: FTBFS: build-dependency not installable: 
libopkele-dev (>= 2.0.4+git20140305.9651b55)
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.)


-- 
844834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libapache2-mod-auth-openid
Version: 0.8-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 (>= 10), apache2-dev, libopkele-dev (>= 
> 2.0.4+git20140305.9651b55), pkg-config, automake, libtool, apache2-bin
> Filtered Build-Depends: debhelper (>= 10), apache2-dev, libopkele-dev (>= 
> 2.0.4+git20140305.9651b55), pkg-config, automake, libtool, apache2-bin
> dpkg-deb: building package 
> 'sbuild-build-depends-libapache2-mod-auth-openid-dummy' in 
> '/<>/resolver-9gGuct/apt_archive/sbuild-build-depends-libapache2-mod-auth-openid-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   
> sbuild-build-depends-libapache2-mod-auth-openid-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-9gGuct/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-9gGuct/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-9gGuct/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-9gGuct/apt_archive ./ Sources [414 B]
> Get:5 copy:/<>/resolver-9gGuct/apt_archive ./ Packages [507 B]
> Fetched 1878 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 libapache2-mod-auth-openid 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-libapache2-mod-auth-openid-dummy : Depends: 
> libopkele-dev (>= 2.0.4+git20140305.9651b55) but it is not going to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/libapache2-mod-auth-openid_0.8-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: libapache2-mod-auth-openid
Source-Version: 0.8-3

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

Debian distribution maintenance software
pp.
NIIBE Yutaka  (supplier of updated libapache2-mod-auth-openid 
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

Bug#844975: courier: FTBFS with openssl 1.1.0

[Adrian Bunk]

Control: retitle -1 courier: FTBFS with openssl 1.1.0
Control: block 827061 by -1

The root cause of this bug seems to be:

...
checking openssl/ssl.h usability... yes
checking openssl/ssl.h presence... yes
checking for openssl/ssl.h... yes
checking for SSL_load_error_strings in -lssl... no
checking for OPENSSL_cleanup in -lssl... no
...


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: courier: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 courier: FTBFS with openssl 1.1.0
Bug #844975 [src:courier] courier: FTBFS: dh_install: missing files, aborting
Changed Bug title to 'courier: FTBFS with openssl 1.1.0' from 'courier: FTBFS: 
dh_install: missing files, aborting'.
> block 827061 by -1
Bug #827061 [release.debian.org] transition: openssl
827061 was blocked by: 844947 828324 844303 828437 844271 828591 828613 835799 
828271 828438 844833 828330 828557 828509 828231 828537 828398 828603 828402 
828409 828373 828268 844920 828446 837960 835786 828246 828566 828604 828394 
828240 828549 828476 828425 828265 835796 828413 828339 828399 828553 828593 
828523 828252 828491 827076 828254 828454 828592 828416 828504 828395 828550 
828291 828308 828546 828419 828281 828612 828269 828543 828410 828588 828457 
828292 828279 808669 828517 828579 828448 828384 835797 828397 828577 828459 
828538 828433 828388 844907 828389 828467 828396 828524 828257 828333 828276 
828536 828289 828405 828082 828505 828242 828313 828564 828298 828461 828322 
828581 828352 828400 828326 828506 829452 828278 828347 828272 828532 828235 
828541 828296 828473 828616 828572 828320 843871 828451 828466 828539 828474 
828507 843682 828602 828548 828490 828259 828595 828510 828261 828610 828367 
828243 828547 828575 828599 828293 828516 828530 828083 828139 828309 828321 
828434 828361 828401 828422 828414 828297 828568 828430 844366 828335 828515 
828597 828607 828346 828239 828495 828266 828447 828392 828334 828533 828486 
828260 828480 828500 828420 828512 828574 844311 828464 828489 827068 828617 
828456 828569 828484 828340 828249 828563 835804 844906 828300 828443 828294 
828618 828453 828385 828349 828245 845030 835585 828578 828534 841635 828253 
828251 828562 828275 828264 828584 828280 844534 836419 828522 844503 809271 
828503 828526 828600 828585 828381 829465 828142 828544 828282 844706 828390 
835800 828615 828317 828327 828307 828427 843988 835811 828237 828332 828369 
828283 828244 828380 828527 828470 845106 828234 828359 828295 828501 828594 
828304 828428 828356 828358 828556 828415 828407 844254 828442 828412 828375 
828354 828315 828406 828529 828589 828439 828587 835790 828306 828310 828481 
828508 844234 828325 828468 828465 828238 828571 828493 835785 828558 828270 
845016 828229 828418 835549 828277 828256 828494 828302 828560 828440 828378 
828528 828565 835793 828393 828341 828561 828314 828383 828471 828449 822380 
828488 828478 828263 828355 828329 828336 828370 828228 828287 828511 828368 
828614 828482 828382 828431 828477 828288 828284 828542 828311 828520 844951 
828429 828376 828458 828582 828417 828318 844664 828366 828248 844347 828518 
828496 828513 828423 828555 828345 828596 828426 828576 828525 828285 843532 
828479 828273 828290 828472 828374 828445 844904 828348 828502 828262 828364 
828338 828331 828452 828377 828232 828319 828514 844948 828323 828521 828387 
828554 828598 828342 828586 828301 835794 828241 828424 828435 828403 828519 
828316 828305 835789 828531 828498 828463 828545 828499 828360 828605 844949 
828551 828230 828573 828552 828274 828362 828619 828386 828328 828559 828343 
828267 828421 828450 828455 828312 828462 828372 828570 828337 828601 828365 
814600 828350 828608 844916 835798 828303 828580 828583 844301 828460 828344 
828127 828492 828379 828371 844345 828363 828432 828606 844213 828436 844945 
828357 828391 844663 828286 828567 828258 828483 828485 844926 828487 828590 
828497 828535 828444 828233 828469 828540 828250 828609 828255 828351 828620 
828611 828411 828404 828441
827061 was not blocking any bugs.
Added blocking bug(s) of 827061: 844975

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

Processed: tagging 844293

[Debian Bug Tracking System]

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

> tags 844293 + help
Bug #844293 [src:criu] criu: FTBFS: ld: unrecognized option 
'-specs=/usr/share/dpkg/no-pie-link.specs'
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#755632: marked as done (python-django-voting: Please ensure it works with Django 1.7)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 06:18:57 +
with message-id 
and subject line Bug#845118: Removed package(s) from unstable
has caused the Debian Bug report #755632,
regarding python-django-voting: Please ensure it works with Django 1.7
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.)


-- 
755632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-voting
Version: 0.2-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django17

Hello,

your package python-django-voting depends on python-django. As you might
know, Django 1.7 will be soon available and as each new upstream major
version, it brings many changes, some of them which are backwards
incompatible (after a deprecation period covering 2 major versions):
https://docs.djangoproject.com/en/1.7/releases/1.7/
https://docs.djangoproject.com/en/1.7/releases/1.7/#backwards-incompatible-changes-in-1-7

We intend to upload Django 1.7 to unstable as soon as it is available
because we really want the latest version in jessie and the freeze is
approaching fast. In preparation of that, I have uploaded a release
candidate in experimental.

Please test your package against Django 1.7 in experimental. If a new
upstream version of your package is required, please package it now.
If you can't upload it to unstable because it only works with Django 1.7,
feel free to upload it to experimental too.

If the current package works fine, please close this bug (or retitle it as
a suggestion to implement Python 3 support and drop its severity to
wishlist[1]). If it's broken, please tag it as confirmed. If it's not
broken, but would benefit from further work, please tag it as confirmed
but reduce the severity.

If you have experimental in your sources.list you can install the latest
version easily:
$ sudo apt-get install -t experimental python-django python3-django

[1] We have recently added Python 3 support with the addition of
python3-django. Consider doing the same if your package is a Django
application/library.

Thank you for your help!

PS: I will raise the "confirmed" bugs that are still of severity
"important" to "serious" once we upload Django 1.7 to unstable.
--- End Message ---
--- Begin Message ---
Version: 0.2-1+rm

Dear submitter,

as the package python-django-voting has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/845118

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#844188: marked as done (pdf2htmlex: FTBFS with fontforge due to use of library_version_configuration structure)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 07:09:56 +0100
with message-id <147970859652.8302.4011811217099121731@localhost>
and subject line Re: pdf2htmlex: FTBFS with fontforge due to use of 
library_version_configuration structure
has caused the Debian Bug report #844188,
regarding pdf2htmlex: FTBFS with fontforge due to use of 
library_version_configuration structure
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.)


-- 
844188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pdf2htmlex
Severity: serious
User: pkg-fonts-de...@lists.alioth.debian.org
Usertags: fontforge-transition

Dear Maintainer,

pdf2htmlex fails to build with new fontforge uploaded to unstable. The build
logs can be found here ¹. This mainly happening due to use of
*library_version_configuration* structure which is not public in new fontforge.

I also tried building pdf2htmlex by removing patch _allow-old-libfontforge_ and
pdf2htmlex builds fine. Since new fontforge is already in unstable it should be
now safe to drop this patch.

¹ https://angband.pl/tmp/ff13/failed/pdf2htmlex_amd64.build

Best Regards,

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

Kernel: Linux 4.8.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)
--- End Message ---
--- Begin Message ---
Hi,

On Sun, 13 Nov 2016 12:48:05 +0530 Vasudev Kamath  
wrote:
> pdf2htmlex fails to build with new fontforge uploaded to unstable. The build
> logs can be found here ¹. This mainly happening due to use of
> *library_version_configuration* structure which is not public in new 
> fontforge.
> 
> I also tried building pdf2htmlex by removing patch _allow-old-libfontforge_ 
> and
> pdf2htmlex builds fine. Since new fontforge is already in unstable it should 
> be
> now safe to drop this patch.

it seems that 0.14.6+ds-3 built fine on all architectures.

Thus, closing.

cheers, josch


signature.asc
Description: signature
--- End Message ---

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Stepan Golosunov]

20.11.2016 в 22:35:26 +0100 Jan Niehusmann написал:
> On Mon, Nov 21, 2016 at 01:03:19AM +0400, Stepan Golosunov wrote:
> > So far I do not know why using libssl1.1 together with a
> > libssl1.0.2-using Qt wouldn't work.
> 
> Well I don't know enough about the dynamic linker and about the internals
> of openssl to know if (indirectly) linking to both libraries at the same
> time is fine.

Indirectly linking with both libraries is supposed to work due to
symbol versioning.  If it wasn't than OpenSSL transition wouldn't have
started.  And parts of Qt are already linked with libssl1.1 (via
libpq5).  Problems could (and did in previous transition) arise if
code (Qt or application) is initializing one libssl while parts of
application are using another but this is supposed to be fixed for
libssl1.1.

And the problem with Qt is that it is not actually linked with OpenSSL
but uses it via dlopen.  My reading of dlsym(3) suggests that it
should work but I could be misreading the documentation or it can be
incorrect.

> If it was, that would be great news. Many mails in the thread "OpenSSL
> 1.1.0" on debian-devel seem to be based on the assumption that such
> linking could cause bugs, and therefore packages can only transition in
> clusters of packages linking to the same version of openssl.

If application passes OpenSSL objects between the two libraries than
it won't work.

> Still, qt is only an example - the same holds true for other libraries
> linking to openssl1.0-dev. There may be cases where your 2nd case
> ('Application passes OpenSSL objects from libssl1.1 to ...') is more
> probable than with qt.

I expect that if libcurl3 is linked with libssl1.0.2 there would be more
problematic applications (as applications need to link with
libssl1.0.2 and run initialization in this case) than if curl is
linked with libssl1.1 (as applications not using
CURLOPT_SSL_CTX_FUNCTION-like functionality are free to link with
whatever libssl they want or not to link with it at all).

> The safest way to avoid hidden bugs would still be changing SONAME and
> package name, so package maintainers would be aware of the change and
> could check their packages for compatibility.
> 
> But yes, it may be less work to somehow identify affected packages and
> handle them directly instead of forcing all packages depending on curl
> through a transition. Identifying those packages in a reliable way could
> be difficult, though.

If libcurl3 is linked with libssl1.1 then maintainer needs to
explicitly break his application (like happened with zurl 1.7.1-1).
The rest just need to be recompiled (and they need to be recompiled in
any case).

The part of the bug where dependencies are insufficiently tough and
libcurl does not change its SONAME exists independently of which
libssl it is linked to (as long as that libssl is different from the
one used in jessie).

Bug#833288: marked as done (would FTBFS now with cython 0.24.1 MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int')

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 00:31:39 -0500
with message-id <20161121053139.yuaj7jowd5ov4...@hopa.kiewit.dartmouth.edu>
and subject line Re: [Python-apps-team] Bug#833288: would FTBFS now with cython 
0.24.1 MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int'
has caused the Debian Bug report #833288,
regarding would FTBFS now with cython 0.24.1 MACS2/IO/PeakIO.pyx:632:49: Cannot 
assign type 'float' to 'int'
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.)


-- 
833288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: macs
Version: 2.1.1.20160309-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

I have just uploaded cython 0.24.1 into sid and while testing reverse build
depends found that macs fails to build.  Here is the log extract:

building 'MACS2.Signal' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 
-c MACS2/Signal.c -o build/temp.linux-x86_64-2.7/MACS2/Signal.o -w -O3 
-ffast-math
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-2.7/MACS2/Signal.o -o 
/build/macs-2.1.1.20160309/.pybuild/pythonX.Y_2.7/build/MACS2/Signal.so
cythoning MACS2/IO/PeakIO.pyx to MACS2/IO/PeakIO.c

Error compiling Cython file:

...
pileup = float(fields[5])
pscore = float(fields[6])
fc = float(fields[7])
qscore = float(fields[8])
peakname = rstrip(fields[9])
add(chrom, start, end, summit, qscore, pileup, pscore, fc, qscore,
^


MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int'
building 'MACS2.IO.PeakIO' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python2.7 -c MACS2/IO/PeakIO.c -o 
build/temp.linux-x86_64-2.7/MACS2/IO/PeakIO.o -w -O3 -ffast-math
MACS2/IO/PeakIO.c:1:2: error: #error Do not use this file, it is the result of 
a failed Cython compilation.
 #error Do not use this file, it is the result of a failed Cython compilation.
  ^
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:274: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
debian/rules:16: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 25
make[1]: Leaving directory '/build/macs-2.1.1.20160309'
debian/rules:13: recipe for target 'build' failed
make: *** [build] Error 2


cheers!

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

Kernel: Linux 4.5.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)
--- End Message ---
--- Begin Message ---
Version: 0.25.2~b0-1

fresh cython was uploaded and I am reconfirming that it fixed this
FTBFS:

macs_2.1.1.20160309-1.dsc   FAILED ok

so FAILED before and builds now so closing this one

On Wed, 16 Nov 2016, Gianfranco Costamagna wrote:

> Hi,


> > I'm currently going to test a build for the attached patch, will upload in 
> > deferred/5 in case everything is good.

> confirmed a successful build with the package on [1].

> dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
> not NFS-safe
> dpkg-gencontrol: warning: package macs: unused substitution variable 
> ${python:Versions}
> dpkg-gencontrol: warning: 

Bug#835674: marked as done (macs: FTBFS: MACS2/IO/PeakIO.c:1:2: error: #error Do not use this file, it is the result of a failed Cython compilation.)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 00:31:39 -0500
with message-id <20161121053139.yuaj7jowd5ov4...@hopa.kiewit.dartmouth.edu>
and subject line Re: [Python-apps-team] Bug#833288: would FTBFS now with cython 
0.24.1 MACS2/IO/PeakIO.pyx:632:49: Cannot assign type 'float' to 'int'
has caused the Debian Bug report #833288,
regarding macs: FTBFS: MACS2/IO/PeakIO.c:1:2: error: #error Do not use this 
file, it is the result of a failed Cython compilation.
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.)


-- 
833288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macs
Version: 2.1.1.20160309-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):
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python2.7 -c MACS2/IO/PeakIO.c -o 
> build/temp.linux-x86_64-2.7/MACS2/IO/PeakIO.o -w -O3 -ffast-math
> MACS2/IO/PeakIO.c:1:2: error: #error Do not use this file, it is the result 
> of a failed Cython compilation.
>  #error Do not use this file, it is the result of a failed Cython compilation.
>   ^
> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> E: pybuild pybuild:276: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python setup.py build 
> dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
> debian/rules:16: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 25

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/macs_2.1.1.20160309-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 ---
Version: 0.25.2~b0-1

fresh cython was uploaded and I am reconfirming that it fixed this
FTBFS:

macs_2.1.1.20160309-1.dsc   FAILED ok

so FAILED before and builds now so closing this one

On Wed, 16 Nov 2016, Gianfranco Costamagna wrote:

> Hi,


> > I'm currently going to test a build for the attached patch, will upload in 
> > deferred/5 in case everything is good.

> confirmed a successful build with the package on [1].

> dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
> not NFS-safe
> dpkg-gencontrol: warning: package macs: unused substitution variable 
> ${python:Versions}
> dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is 
> not NFS-safe
> dpkg-gencontrol: warning: package macs: unused substitution variable 
> ${python:Versions}
>dh_md5sums -O--buildsystem=pybuild
>dh_builddeb -O--buildsystem=pybuild
> dpkg-deb: building package 'macs-dbgsym' in 
> '../macs-dbgsym_2.1.1.20160309-1_amd64.deb'.
> dpkg-deb: building package 'macs' in '../macs_2.1.1.20160309-1_amd64.deb'.
>  dpkg-genbuildinfo
> dpkg-genbuildinfo: warning: File::FcntlLock not available; using flock which 
> is not NFS-safe
>  dpkg-genchanges  >../macs_2.1.1.20160309-1_amd64.changes
> dpkg-genchanges: info: including full source code in upload
>  dpkg-source --after-build macs-2.1.1.20160309


> [1] 
> http://debomatic-amd64.debian.net/distribution#unstable/cython/0.24.1-2.1/buildlog

> in deferred/5

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik--- End Message ---

Bug#845179: FTBFS with super-fresh cython -- seems to carry pre-cythoned sources which get rebuilt during clean

[Yaroslav Halchenko]

Source: slixmpp
Version: 1.2.1-2
Severity: serious
Justification: fails to build from source

While preparing for upload of fresh cython (0.25.2~b0-1) and running build of
rdepends python-aiohttp failed to build with

 fakeroot debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
   dh_testdir -O--buildsystem=pybuild
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/slixmpp-1.2.1'
dh_auto_clean
I: pybuild base:184: python3.5 setup.py clean 
Compiling slixmpp/stringprep.pyx because it depends on 
/usr/lib/python3/dist-packages/Cython/Includes/libc/string.pxd.
[1/1] Cythonizing slixmpp/stringprep.pyx
running clean
removing '/build/slixmpp-1.2.1/.pybuild/pythonX.Y_3.5/build' (and everything 
under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.5' does not exist -- can't clean it
make -C docs clean
make[2]: Entering directory '/build/slixmpp-1.2.1/docs'
rm -rf _build/*
make[2]: Leaving directory '/build/slixmpp-1.2.1/docs'
make[1]: Leaving directory '/build/slixmpp-1.2.1'
   dh_clean -O--buildsystem=pybuild
 dpkg-source -b slixmpp-1.2.1
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building slixmpp using existing ./slixmpp_1.2.1.orig.tar.gz
dpkg-source: warning: ignoring deletion of directory slixmpp.egg-info
dpkg-source: warning: ignoring deletion of file slixmpp.egg-info/top_level.txt, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file slixmpp.egg-info/SOURCES.txt, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file slixmpp.egg-info/requires.txt, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
slixmpp.egg-info/dependency_links.txt, use --include-removal to override
dpkg-source: warning: ignoring deletion of file slixmpp.egg-info/PKG-INFO, use 
--include-removal to override
dpkg-source: info: local changes detected, the modified files are:
 slixmpp-1.2.1/slixmpp/stringprep.c
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/slixmpp_1.2.1-2.diff.hICiN3
dpkg-source: info: you can integrate the local changes with dpkg-source --commit


so you can see that clean does recythonizing, which modifies shipped with
upstream tarball slixmpp-1.2.1/slixmpp/stringprep.c

as a quick solution (besides cleansing the sources pkg) I think you
could make use of  dh_autoreconf so it memorizes changed files



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

Kernel: Linux 4.6.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)

Bug#845178: FTBFS with super-fresh cython -- seems to carry pre-cythoned sources which get rebuilt during clean

[Yaroslav Halchenko]

Source: python-aiohttp
Version: 1.1.5-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

While preparing for upload of fresh cython (0.25.2~b0-1) and running build of
rdepends python-aiohttp failed to build with

dh_auto_clean
I: pybuild base:184: python3.5 setup.py clean 
Compiling aiohttp/_websocket.pyx because it depends on 
/usr/lib/python3/dist-packages/Cython/Includes/libc/string.pxd.
[1/1] Cythonizing aiohttp/_websocket.pyx
running clean
removing '/build/python-aiohttp-1.1.5/.pybuild/pythonX.Y_3.5/build' (and 
everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.5' does not exist -- can't clean it
I: pybuild base:184: python3.5-dbg setup.py clean 
running clean
removing '/build/python-aiohttp-1.1.5/.pybuild/pythonX.Y-dbg_3.5/build' (and 
everything under it)
setup.py:65: ResourceWarning: unclosed file <_io.TextIOWrapper 
name='README.rst' mode='r' encoding='ANSI_X3.4-1968'>
  return open(os.path.join(os.path.dirname(__file__), f)).read().strip()
setup.py:65: ResourceWarning: unclosed file <_io.TextIOWrapper 
name='CHANGES.rst' mode='r' encoding='ANSI_X3.4-1968'>
  return open(os.path.join(os.path.dirname(__file__), f)).read().strip()
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.5' does not exist -- can't clean it
make[1]: Leaving directory '/build/python-aiohttp-1.1.5'
   dh_clean -O--buildsystem=pybuild
 dpkg-source -b python-aiohttp-1.1.5
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building python-aiohttp using existing 
./python-aiohttp_1.1.5.orig.tar.gz
dpkg-source: info: local changes detected, the modified files are:
 python-aiohttp-1.1.5/aiohttp/_websocket.c
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/python-aiohttp_1.1.5-1.diff.8c7_89
dpkg-source: info: you can integrate the local changes with dpkg-source --commit


so you can see that clean does recythonizing, which modifies shipped with
upstream tarball python-aiohttp-1.1.5/aiohttp/_websocket.c

as a quick solution (besides cleansing the sources pkg) I think you
could make use of  dh_autoreconf so it memorizes changed files

Cheers,

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

Kernel: Linux 4.6.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)

Bug#845173: Cannot handle new debs with data component XZ compressed in parallel

[Carlos Maddela]

My fixes based on the latest git repo are available in the bugfixes
branch of https://github.com/e7appew/debdelta.git.

My fixes based on the latest version in sid are represented in the
attached debdiff patch.
diff -Nru debdelta-0.55/debdelta debdelta-0.55+nmu1/debdelta
--- debdelta-0.55/debdelta  2014-12-01 04:31:13.0 +1100
+++ debdelta-0.55+nmu1/debdelta 2016-11-21 15:11:41.0 +1100
@@ -676,7 +676,14 @@
 return join(v.split('%3a'),':')
   else:
 return v
-  
+
+def delta_base_name(pkg, old_ver, new_ver, arch, ext='.debdelta'):
+  assert(':' not in pkg)
+  return pkg + \
+ '_' + version_mangle(old_ver) + \
+ '_' + version_mangle(new_ver) + \
+ '_' + arch + ext
+
 def tempo():
   TD = abspath(tempfile.mkdtemp(prefix='debdelta',dir=TMPDIR))
   for i in 'OLD','NEW','PATCH' :
@@ -2761,6 +2768,7 @@
 "tries to guess the parameters used to compress, returns a string of 
options ; if check=True and it fails, returns False "
 par=''
 crc=''
+thread=''
 z=tempfile.NamedTemporaryFile(suffix='.xz',delete=False)
 #unfortunately 'xz --list' does not work on pipes!
 shutil.copyfileobj(o,z)
@@ -2779,6 +2787,8 @@
 if par and par != a[15]:
   print "  warning : this xz -- compressed file was compressed with 
variable blocks options ?! '%s' != '%s'" & (par,a[15])
 par=a[15]
+if not thread and a[12]=='cu':
+  thread='-T2'
 #print ' guessed par crc ',par,crc
 if crc:
   crc=crc.lower()
@@ -2799,6 +2809,8 @@
   w.append(par)
 if crc:
   w+=['-C',crc]
+if thread:
+  w.append(thread)
 w.append('-')
 if VERBOSE > 2 : print '   Testing XZ options ',w
 
w=subprocess.Popen(w,stdin=y.stdout,stdout=subprocess.PIPE,close_fds=True)
@@ -2815,8 +2827,10 @@
   return False
 if crc:
   crc=' -C '+crc
+if thread:
+  thread=' '+thread
 os.unlink(z.name)
-return par+crc
+return par+crc+thread
 
   ### helper sh functions for script, for delta_tar()
 
@@ -3885,8 +3899,7 @@
   continue
 
 assert( old['Package'] == pa and pa == new['Package'] )
-deltabasename = pa +'_'+  version_mangle(old['Version']) +\
-'_'+ version_mangle(new['Version']) +'_'+ar+'.debdelta'
+deltabasename = delta_base_name(pa, old['Version'], new['Version'], ar)
 
 if 'Filename' in new:
   deltadirname=delta_dirname(os.path.dirname(new['Filename']),DIR)
@@ -4693,13 +4706,13 @@
   deb_path=string.join(deb_path[(thepoolindex):],'/')
   
   #try all possible variants of the filename
-  newdebs=[p.name+'_'+candidate_version+'_'+arch+'.deb',
+  newdebs=[p.shortname+'_'+candidate_version+'_'+arch+'.deb',
os.path.basename(deb_uri)]
   if ':' in candidate_version:
 a=candidate_version.split(':')
-newdebs.append(p.name+'_'+a[1]+'_'+arch+'.deb')
-newdebs.append(p.name+'_'+a[0]+'%3A'+a[1]+'_'+arch+'.deb')
-newdebs.append(p.name+'_'+a[0]+'%3a'+a[1]+'_'+arch+'.deb')
+newdebs.append(p.shortname+'_'+a[1]+'_'+arch+'.deb')
+newdebs.append(p.shortname+'_'+a[0]+'%3A'+a[1]+'_'+arch+'.deb')
+newdebs.append(p.shortname+'_'+a[0]+'%3a'+a[1]+'_'+arch+'.deb')
   
   for newdeb in newdebs:
 if os.path.exists(DEB_DIR+'/'+newdeb) or \
@@ -4727,9 +4740,8 @@
   assert(a[0] == 'http')
 
   #delta name
-  delta_name=p.name.split(':')[0]+'_'+version_mangle(installed_version)+\
-  '_'+ version_mangle(candidate_version)+'_'+\
-  arch+'.debdelta'
+  delta_name = delta_base_name(p.shortname, installed_version,
+   candidate_version, arch)
 
   uri=delta_uri_base+'/'+os.path.dirname(deb_path)+'/'+delta_name
   
@@ -5114,9 +5126,8 @@
   continue
 
 #delta name
-delta_name=p.name+'_'+version_mangle(installed_version)+\
-'_'+ version_mangle(candidate_version)+'_'+\
-arch+'.debdelta'
+delta_name = delta_base_name(p.shortname, installed_version,
+ candidate_version, arch)
   
 uri=delta_uri_base+'/'+os.path.dirname(deb_path)+'/'+delta_name
 
diff -Nru debdelta-0.55/debdeltas debdelta-0.55+nmu1/debdeltas
--- debdelta-0.55/debdeltas 2014-12-01 04:31:13.0 +1100
+++ debdelta-0.55+nmu1/debdeltas2016-11-21 15:11:41.0 +1100
@@ -676,7 +676,14 @@
 return join(v.split('%3a'),':')
   else:
 return v
-  
+
+def delta_base_name(pkg, old_ver, new_ver, arch, ext='.debdelta'):
+  assert(':' not in pkg)
+  return pkg + \
+ '_' + version_mangle(old_ver) + \
+ '_' + version_mangle(new_ver) + \
+ '_' + arch + ext
+
 def tempo():
   TD = abspath(tempfile.mkdtemp(prefix='debdelta',dir=TMPDIR))
   for i in 'OLD','NEW','PATCH' :
@@ -2761,6 +2768,7 @@
 "tries to guess the parameters used 

Bug#841575: [pkg-go] Bug#841575: docker-registry: FTBFS: Tests failures

[Tianon Gravi]

On 20 November 2016 at 20:31, Tianon Gravi  wrote:
> I wasn't able to dig into the details yet, but looking at the log I
> noticed the following which I believe is the real test failure output:

That being said, I currently get the (more severe IMO) failure when
trying to build locally:

> src/github.com/docker/distribution/registry/registry.go:13:2: cannot find 
> package "github.com/Sirupsen/logrus/formatters/logstash" in any of:
> /<>/obj-x86_64-linux-gnu/src/github.com/docker/distribution/vendor/github.com/Sirupsen/logrus/formatters/logstash
>  (vendor tree)
> /usr/lib/go-1.7/src/github.com/Sirupsen/logrus/formatters/logstash (from 
> $GOROOT)
> /<>/obj-x86_64-linux-gnu/src/github.com/Sirupsen/logrus/formatters/logstash
>  (from $GOPATH)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#844872: marked as done (libreadline-java: FTBFS: org_gnu_readline_Readline.c:700:37: error: 'CPFunction' undeclared (first use in this function))

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 04:33:27 +
with message-id 
and subject line Bug#844872: fixed in libreadline-java 0.8.0.1+dfsg-5
has caused the Debian Bug report #844872,
regarding libreadline-java: FTBFS: org_gnu_readline_Readline.c:700:37: error: 
'CPFunction' undeclared (first use in this function)
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.)


-- 
844872: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844872
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libreadline-java
Version: 0.8.0.1+dfsg-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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):
> gcc -I /usr/lib/jvm/default-java/include -I 
> /usr/lib/jvm/default-java/include/linux -I /usr/lib/jvm/default-java/include 
> -I /usr/lib/jvm/default-java/include/linux -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -O2 -fdebug-prefix-map=/<>/libreadline-java-0.8.0.1+dfsg=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC -DPOSIX -fPIC 
> -DPOSIX -DJavaEditline \
>-c org_gnu_readline_Readline.c
> org_gnu_readline_Readline.c:188:15: warning: initialization from incompatible 
> pointer type [-Wincompatible-pointer-types]
>/* const */ _library_version,
>^
> org_gnu_readline_Readline.c:188:15: note: (near initialization for 
> 'globalStringInternals[0]')
> org_gnu_readline_Readline.c: In function 
> 'Java_org_gnu_readline_Readline_setCompleterImpl':
> org_gnu_readline_Readline.c:700:37: error: 'CPFunction' undeclared (first use 
> in this function)
>  rl_completion_entry_function = (CPFunction *) java_completer;
>  ^~
> org_gnu_readline_Readline.c:700:37: note: each undeclared identifier is 
> reported only once for each function it appears in
> org_gnu_readline_Readline.c:700:49: error: expected expression before ')' 
> token
>  rl_completion_entry_function = (CPFunction *) java_completer;
>  ^
> Makefile:109: recipe for target 'org_gnu_readline_Readline.o' failed
> make[5]: *** [org_gnu_readline_Readline.o] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/11/18/libreadline-java_0.8.0.1+dfsg-4_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: libreadline-java
Source-Version: 0.8.0.1+dfsg-5

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated libreadline-java 
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: Sun, 20 Nov 2016 20:07:32 -0800
Source: libreadline-java
Binary: libreadline-java libreadline-java-doc
Architecture: source amd64 all
Version: 0.8.0.1+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Description:
 libreadline-java - GNU readline and BSD editline wrappers for Java
 libreadline-java-doc - API docs for readline/editline wrappers for Java
Closes: 770584 844872
Changes:
 libreadline-java (0.8.0.1+dfsg-5) unstable; urgency=medium
 .
   * Address FTBFS with libedit 3.1-20160903-1 (Closes: #844872)
   * Remove Niels Thykier from Uploaders. (Closes: #770584)
 - Thank you for all of your help Niels!
   * Bump Standards-Version to 3.9.8.
   * Freshen debian/copyright.
   * Drop Conflicts/Provides on ancient 

Bug#841575: [pkg-go] Bug#841575: docker-registry: FTBFS: Tests failures

[Tianon Gravi]

On 21 October 2016 at 06:10, Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

I wasn't able to dig into the details yet, but looking at the log I
noticed the following which I believe is the real test failure output:

> === RUN   Test
>
> --
> FAIL: configuration_test.go:167: ConfigSuite.TestMarshalRoundtrip
>
> configuration_test.go:171:
> c.Assert(err, IsNil)
> ... value *errors.errorString = {s:"Invalid loglevel  Must 
> be one of [error, warn, info, debug]"} ("Invalid loglevel  Must be one of 
> [error, warn, info, debug]")
>
> time="2016-10-21T01:11:44Z" level=warning msg="Ignoring unrecognized 
> environment variable REGISTRY_DUCKS"
> time="2016-10-21T01:11:44Z" level=warning msg="Ignoring unrecognized 
> environment variable REGISTRY_REPORTING_ASDF"
> OOPS: 19 passed, 1 FAILED
> --- FAIL: Test (0.01s)
> FAIL
> exit status 1
> FAIL github.com/docker/distribution/configuration 0.015s

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#844872: Pending fixes for bugs in the libreadline-java package

[pkg-java-maintainers]

tag 844872 + pending
thanks

Some bugs in the libreadline-java package are closed in revision
ba9c39e58e62271dbae11a3a0938b5bd6c4d19fc in branch 'master' by tony
mancill

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/libreadline-java.git/commit/?id=ba9c39e

Commit message:

add patch for FTBFS against libedit 3.1-20160903 (closes: #844872)

Processed: Pending fixes for bugs in the libreadline-java package

[Debian Bug Tracking System]

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

> tag 844872 + pending
Bug #844872 [src:libreadline-java] libreadline-java: FTBFS: 
org_gnu_readline_Readline.c:700:37: error: 'CPFunction' undeclared (first use 
in this function)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837480: marked as done (gb: FTBFS with bindnow and PIE enabled)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 04:18:19 +
with message-id 
and subject line Bug#837480: fixed in gb 0.4.2-2
has caused the Debian Bug report #837480,
regarding gb: 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.)


-- 
837480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gb
Version: 0.4.2-1
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):
...
=== RUN   TestReadFailuresIgnored
--- PASS: TestReadFailuresIgnored (0.00s)
PASS
ok  github.com/constabulary/gb/importer 0.004s
=== RUN   TestTest
a
a
b
a
d.v1
c
f
e
cmd/f
extest
extest
external_only_test
notestfiles
/usr/bin/ld: -r and -pie may not be used together
collect2: error: ld returned 1 exit status
# cgoonlynotest
testonly
extestonly
g
g
ldflags
/usr/bin/ld: -r and -pie may not be used together
collect2: error: ld returned 1 exit status
# cgotest
testflags
main
--- FAIL: TestTest (3.16s)
test_test.go:96: Test(cgoonlynotest): want , got exit status 1
test_test.go:84: skipping test, goversion 1.60 is above
maxgoversion 1.50
test_test.go:96: Test(cgotest): want , got exit status 1
=== RUN   TestTestPackage
--- PASS: TestTestPackage (0.09s)

...

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

Thanks,
Balint
--- End Message ---
--- Begin Message ---
Source: gb
Source-Version: 0.4.2-2

We believe that the bug you reported is fixed in the latest version of
gb, 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.
Tianon Gravi  (supplier of updated gb 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: Sun, 20 Nov 2016 20:02:59 -0800
Source: gb
Binary: gb golang-github-constabulary-gb-dev
Architecture: source
Version: 0.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Tianon Gravi 
Description:
 gb - project based build tool for Go
 golang-github-constabulary-gb-dev - project based build tool for Go (source)
Closes: 837480
Changes:
 gb (0.4.2-2) unstable; urgency=medium
 .
   * Backport "-no-pie" testing patch from upstream PR #655 (Closes: #837480)
Checksums-Sha1:
 4781fd79e1ef9f9881d909e8c573d8663bb98cab 2162 gb_0.4.2-2.dsc
 af02753a894f706c11aa0ddee862f1e737036fd4 4688 gb_0.4.2-2.debian.tar.xz
Checksums-Sha256:
 a239a4ddfed75c3aa76ab32e5c50e8ca750fa71ef9fd6a2c221edf2e352391fa 2162 
gb_0.4.2-2.dsc
 951cf5f0ed4f6f03e082c546de3305c30b726aca9378491ca76d5b19e5941dc8 4688 
gb_0.4.2-2.debian.tar.xz
Files:
 f78f1ce195af3f59ac53c983001872d2 2162 devel extra gb_0.4.2-2.dsc
 d16206606c652dd58e90cda4efb97f36 4688 devel extra gb_0.4.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIvBAEBCgAZBQJYMnIlEhx0aWFub25AZGViaWFuLm9yZwAKCRADapwlvzV91OFP
EACkzBYPaCM89PrBD2tAoUT+sOaNpsxsxRjTOBhVrAG3B+hXX9/wnlPTB9Xs4OUR
4cgWMTIPrPA8gj/Ps8wTzrX4/VTmf/fXnMrMwqUpw2SG8Ugr+EtzLwYGrtsTZ33W
rieKnGf9v5W0iEF0kcf4woSbHbbo6sC9AVftvZVPnxApHkMfAr/y5SxDCUNupygI
Gdse37JlVVKtwO9GWjoFHuKIZ5QFjcW/Cv9Mcch+P6g1Iw1WFF+5M9gAwp4r0uHY
FVDk/E2oUd0mTO5Ct0ELwMg/vA92EoHCXbKrj+T5XVoENb9VAtnmCbhdQNZbGlBi
LTB+3S+2UxpuvT6oCkJ+E+QS9LFzO9ZJSZL3M88sKq3MzvmDAhmgQ/Mi9k8WmzHT
lj/QsCd6x846TbjGSKsBE3cdmYZgYEMrqP1FAknv1yHqXypBtlBCuPIRY4EJSFNd
6mR8sec+/+5uHp5NeMt6zUbiu+fOPdwZ/kJpxk0GKubeImTtuQKxJD2WbXA+wjOu
CGv09j0J8FO9CRXLEPaTdCBa0TvnD3R1UgWWeXhF5iWJUpsh4ONnb+YC3s/Guv57

Bug#837480: Pending fixes for bugs in the gb package

[pkg-go-maintainers]

tag 837480 + pending
thanks

Some bugs in the gb package are closed in revision
032c421a524ba63c18483d058eb931bc188a2e37 in branch 'master' by Tianon
Gravi

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/gb.git/commit/?id=032c421

Commit message:

Backport "-no-pie" testing patch from upstream PR #655 (Closes: #837480)

Processed: Pending fixes for bugs in the gb package

[Debian Bug Tracking System]

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

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

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

Bug#835686: docker.io: FTBFS: .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: cannot use _API_CreateContainer_Handler (type func(interface {}, "golang.org/x/net/context".Contex

[Tianon Gravi]

On 28 August 2016 at 03:23, Lucas Nussbaum  wrote:
>> ---> Making bundle: dynbinary (in bundles/1.11.2/dynbinary)
>> Building: bundles/1.11.2/dynbinary/docker-1.11.2
>> # github.com/docker/containerd/api/grpc/types
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: 
>> cannot use _API_CreateContainer_Handler (type func(interface {}, 
>> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
>> error)) as type grpc.methodHandler in field value
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1141: 
>> cannot use _API_UpdateContainer_Handler (type func(interface {}, 
>> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
>> error)) as type grpc.methodHandler in field value
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1145: 
>> cannot use _API_Signal_Handler (type func(interface {}, 
>> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
>> error)) as type grpc.methodHandler in field value
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1149: 
>> cannot use _API_UpdateProcess_Handler (type func(interface {}, 
>> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
>> error)) as type grpc.methodHandler in field value
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1153: 
>> cannot use _API_AddProcess_Handler (type func(interface {}, 
>> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
>> error)) as type grpc.methodHandler in field value
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1157: 
>> cannot use _API_CreateCheckpoint_Handler (type func(interface {}, 
>> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
>> error)) as type grpc.methodHandler in field value
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1161: 
>> cannot use _API_DeleteCheckpoint_Handler (type func(interface {}, 
>> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
>> error)) as type grpc.methodHandler in field value
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1165: 
>> cannot use _API_ListCheckpoint_Handler (type func(interface {}, 
>> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
>> error)) as type grpc.methodHandler in field value
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1169: 
>> cannot use _API_State_Handler (type func(interface {}, 
>> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
>> error)) as type grpc.methodHandler in field value
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1173: 
>> cannot use _API_Stats_Handler (type func(interface {}, 
>> "golang.org/x/net/context".Context, func(interface {}) error) (interface {}, 
>> error)) as type grpc.methodHandler in field value
>> .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1173: too 
>> many errors
>> debian/rules:60: recipe for target 'override_dh_auto_build' failed
>> make[1]: *** [override_dh_auto_build] Error 1

I did some digging/testing on this, and found that _this_ particular
failure is actually due to #835736, which was fixed with
src:containerd 0.2.1~ds1-3.

However, we do currently FTBFS, just with different failures:

---> Making bundle: dynbinary (in bundles/1.11.2/dynbinary)
Building: bundles/1.11.2/dynbinary/docker-1.11.2
# github.com/docker/docker/api/server/router/container
api/server/router/container/exec.go:39: execConfig.Container undefined
(type *types.ExecConfig has no field or method Container)
# github.com/docker/docker/api/client
api/client/attach.go:51: unknown types.ContainerAttachOptions field
'ContainerID' in struct literal
api/client/attach.go:69: not enough arguments in call to
cli.client.ContainerAttach
api/client/build.go:239: not enough arguments in call to cli.client.ImageBuild
api/client/commit.go:68: unknown types.ContainerCommitOptions field
'ContainerID' in struct literal
api/client/commit.go:69: unknown types.ContainerCommitOptions field
'RepositoryName' in struct literal
api/client/pull.go:70: undefined:
"github.com/docker/engine-api/client".RequestPrivilegeFunc
api/client/push.go:64: undefined:
"github.com/docker/engine-api/client".RequestPrivilegeFunc
api/client/trust.go:322: undefined:
"github.com/docker/engine-api/client".RequestPrivilegeFunc
api/client/trust.go:402: undefined:
"github.com/docker/engine-api/client".RequestPrivilegeFunc
api/client/utils.go:49: undefined:
"github.com/docker/engine-api/client".RequestPrivilegeFunc
api/client/commit.go:69: too many errors
# github.com/docker/containerd/api/grpc/types
../containerd/api/grpc/types/api.pb.go:832: undefined:
grpc.SupportPackageIsVersion3
# github.com/docker/docker/api/server/router/network
api/server/router/network/network_routes.go:78: create.Name undefined
(type 

Bug#845173: Cannot handle new debs with data component XZ compressed in parallel

[Carlos Maddela]

Package: debdelta
Version: 0.55
Severity: grave
Tags: patch

Ever since dpkg 1.18.14 or 1.18.15 was released there haven't been too
many usable debdeltas available for download. The reason being that debs
that have their data component compressed in XZ format are now being
done so in parallel, which produces a file that debdelta cannot
reproduce.

For example, trying to create a debdelta results in:

> $ debdelta -vv fluid-soundfont-gm_3.1-5_all.deb 
> fluid-soundfont-gm_3.1-5.1_all.deb /tmp/patch.debdelta
>  OLD: Package: fluid-soundfont-gm Version: 3.1-5 Architecture: all 
> Installed-Size: 145368
>  NEW: Package: fluid-soundfont-gm Version: 3.1-5.1 Architecture: all 
> Installed-Size: 145169
>   debdelta.conf says we will skip:  []
>   studying  debian-binary  of len 0kB
>   studying  control.tar.gz  of len 0kB
>   time lost so far in finding correspondence 0.00
>   compute delta for 0 (1kB) and 1 (10kB)
>   delta is 7.57% of 1, speed: 1942kB /sec
>   studying  data.tar.xz  of len 116822kB
>  Tried XZ options but failed:  --lzma2=dict=8MiB crc64
>  Tried XZ options but failed:  -9e crc64
>  Tried XZ options but failed:  -9 crc64
>  Tried XZ options but failed:  -6e crc64
> debdelta : Cannot guess XZ parameters (non retriable

I have a patch which I will make available shortly...

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

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 debdelta depends on:
ii  binutils2.27.51.20161118-2
ii  bzip2   1.0.6-8
ii  libbz2-1.0  1.0.6-8
ii  libc6   2.24-5
ii  python  2.7.11-2
ii  zlib1g  1:1.2.8.dfsg-2+b3

Versions of packages debdelta recommends:
ii  bsdiff   4.3-19
ii  gnupg-agent  2.1.15-9
ii  gnupg2   2.1.15-9
ii  lzma 9.22-2
ii  python-apt   1.1.0~beta5
ii  python-debian0.1.29
ii  xdelta   1.1.3-9.1
ii  xdelta3  3.0.11-dfsg-1
ii  xz-utils [lzma]  5.2.2-1.3

Versions of packages debdelta suggests:
ii  debdelta-doc  0.55+nmu1

-- no debconf information

Bug#842806: docker.io: Can't connect to the daemon

[Tianon Gravi]

On 2 November 2016 at 00:25, Kurt Roeckx  wrote:
> I'm guessing this is something systemd sets up, but that I might
> need to manually set up if not using it?

Ah yeah, sounds like it -- did you install recommends when installing
docker.io?  That should've pulled in the "cgroupfs-mount" package,
which performs this function for sysvinit (but is a no-op for
systemd).  Some folks also prefer to configure their cgroups manually
via /etc/fstab (hence why that package is in Recommends instead of
Depends), but I personally find that a bit too tedious; YMMV. :)

Any objections to lowering the severity of this bug?  This sounds like
a system configuration issue, not necessarily a package-level issue,
so the most we could do is maybe fuddle Depends or add a blurb in
README.Debian. :(

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process

[Tianon Gravi]

severity 843530 important
thanks

On 8 November 2016 at 09:52, Tianon Gravi  wrote:
> Ouch, looks like we're now hitting
> https://github.com/opencontainers/runc/issues/1175, which doesn't
> appear to have a Docker or runc workaround yet (although adding
> "systemd.legacy_systemd_cgroup_controller=yes" to your system boot
> parameters should do the trick for now). :(

So, following that thread now, it looks like systemd upstream has
reverted that particular change (which likely isn't quite in Debian
yet, at least not stretch), but they do plan to reintroduce it again
later.

Given that there's not much more we (Debian) can directly do to
fix/overcome this beyond documenting it in README.Debian (which I plan
to commit in Git shortly), I've decreased the severity of this report.
Hopefully the runc maintainers will figure out a reasonable way to
support the unified hierarchy sometime in the near future. :(


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Processed: Re: Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process

[Debian Bug Tracking System]

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

> severity 843530 important
Bug #843530 [docker.io] docker.io: docker broken: oci runtime error: could not 
synchronize with container process
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#832103: docker.io: Can't run images after upgrading to 1.11.2~ds1-6

[Tianon Gravi]

severity 832103 important
thanks

On 31 August 2016 at 12:02, Felipe Sateler  wrote:
> Ack.
>
> Anyway, isn't this a condition docker can detect (mismatch between
> binaries and the running daemon)? In that case it could print a
> suitable help message for the user.

Yeah, I haven't been able to dig into exactly what the mismatch is,
but I've found that even on my Gentoo machine, even just recompiling
the exact same version of containerd/runc (which often leads to the
same set of bits, even!) without restarting Docker can cause container
starting issues (so even if we did restart Docker during upgrade, it
wouldn't restart Docker during containerd/runc upgrade and we'd be
hosed again, especially since Docker runs its own instance of
containerd).

I don't think there's really much we (Debian) can do here besides
adding a note in README.Debian (do folks generally read that?), and as
such I've decreased the severity of this report.


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Processed: Re: Bug#832103: docker.io: Can't run images after upgrading to 1.11.2~ds1-6

[Debian Bug Tracking System]

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

> severity 832103 important
Bug #832103 [docker.io] docker.io: Can't run images after upgrading to 
1.11.2~ds1-6
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#836991: golang-doc: fails to upgrade from 'jessie': error: directory '/usr/lib/go' contains files not owned by package golang-go:i386, cannot switch to symlink

[Tianon Gravi]

On 7 September 2016 at 14:18, Andreas Beckmann  wrote:
>   Preparing to unpack .../golang-go_2%3a1.7~1_i386.deb ...
>   dpkg-maintscript-helper: error: directory '/usr/lib/go' contains files not 
> owned by package golang-go:i386, cannot switch to symlink
>   dpkg: error processing archive 
> /var/cache/apt/archives/golang-go_2%3a1.7~1_i386.deb (--unpack):
>subprocess new pre-installation script returned error exit status 1

Any thoughts or hrefs on the "correct" way to fix this in the
packaging?  (Or a simple way to figure out _which_ files don't belong
so we can evaluate more clearly?)

I don't want to just add "rm -rf" to the preinst, but if piuparts is
noticing the problem, it's bound to be something we've done wrong in
the jessie packaging of "golang-go". :(

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#845171: wine-development: FTBFS: ld aborts or segfaults

[Jens Reyer]

Source: wine-development
Version: 1.9.22-1
Justification: FTBFS on i386, armel and armhf
Severity: serious
Tags: help


wine-development 1.9.22-1 (in stretch) built successfully on all
architectures when it was uploaded to unstable, but fails to
build in a stretch environment on i386 now (amd64 is still fine).
Exactly the same for 1.9.23-1 on i386 in a sid environment:

gcc -m32 -o wineserver async.o atom.o change.o class.o clipboard.o completion.o 
console.o debugger.o device.o \
  directory.o event.o fd.o file.o handle.o hook.o mach.o mailslot.o main.o 
mapping.o mutex.o \
  named_pipe.o object.o process.o procfs.o ptrace.o queue.o region.o registry.o 
request.o \
  semaphore.o serial.o signal.o snapshot.o sock.o symlink.o thread.o timer.o 
token.o trace.o \
  unicode.o user.o window.o winstation.o -Wl,--rpath,\$ORIGIN/../libs/wine \
  ../libs/port/libwine_port.a -lwine -L../libs/wine 
-specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro -Wl,-z,now 
-Wl,-rpath,/usr/lib/i386-linux-gnu/wine-development
collect2: fatal error: ld terminated with signal 6 [Aborted]
compilation terminated.
ld: malloc.c:2403: sysmalloc: Assertion `(old_top == initial_top (av) && 
old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse 
(old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
Makefile:732: recipe for target 'wineserver' failed
make[2]: *** [wineserver] Error 1
make[2]: Leaving directory '/build/wine-development-1.9.22/server'
Makefile:19180: recipe for target 'server' failed
make[1]: *** [server] Error 2
make[1]: *** Waiting for unfinished jobs
[...]
dh_auto_build: make -j4 returned exit code 2
debian/rules:100: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2



Further a local rebui1d of .9.22-1 failed on i386 on
2016-11-05[1], but succeeded again on 2016-11-07.

1.9.23-1 didn't build on armel[2], armhf[3] and kfreebsd-i386[4]
when it was uploaded to unstable, and failed on debomatic today
(the error message changed though).

These other failures are not exactly identical, but also happen
in ld. I assume they are all related.

I'm at a loss here what the reason for the failures is. I assume
it's somehow related to build-dependencies being rebuilt with pie
and bindnow and/or something in binutils (I found a similar recent
bugreport (#844847, xorp: FTBFS: collect2: fatal error: ld
terminated with signal 6 [Aborted]) which was reassigned to
binutils.)

However wine 1.8.5-1 still builds fine (wine and wine-development
are nearly identical, only the upstream version differs). If my
assumption was true, I'd expect wine to fail, too. Maybe it will
do so soon.

So what to do now?

I hope someone can help here.

If wine(-development) gets removed from the archive we need a fix
uploaded by December 25th to get it in Stretch (or find a solution
with the release team).

Greets
jre




[1] 1.9.22-1:i386, local rebuild on 2016-11-05
gcc -m32 -o wine-installed main.o \
  -Wl,--rpath,\$ORIGIN/`../tools/makedep -R /usr/lib/wine-development 
/usr/lib/i386-linux-gnu/wine-development` -Wl,--enable-new-dtags \
  -Wl,--export-dynamic -Wl,-Ttext-segment=0x7c00 
-Wl,-z,max-page-size=0x1000 -lwine -lpthread \
  ../libs/port/libwine_port.a -L../libs/wine -Wl,-z,relro -Wl,-z,now 
-Wl,-rpath,/usr/lib/i386-linux-gnu/wine-development
*** Error in `/usr/bin/ld': free(): invalid next size (fast): 0x57050ae0 ***
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x6733a)[0xf74ec33a]
/lib/i386-linux-gnu/libc.so.6(+0x6df77)[0xf74f2f77]
/lib/i386-linux-gnu/libc.so.6(+0x6e736)[0xf74f3736]
/usr/lib/i386-linux-gnu/libbfd-2.27.51-system.20161102.so(objalloc_free+0x3d)[0xf774011d]
/usr/lib/i386-linux-gnu/libbfd-2.27.51-system.20161102.so(bfd_hash_table_free+0x1c)[0xf76858ec]
/usr/lib/i386-linux-gnu/libbfd-2.27.51-system.20161102.so(+0x30568)[0xf768c568]
/usr/lib/i386-linux-gnu/libbfd-2.27.51-system.20161102.so(bfd_fopen+0x1c3)[0xf768ce13]
/usr/lib/i386-linux-gnu/libbfd-2.27.51-system.20161102.so(bfd_openr+0x25)[0xf768ce65]
/usr/bin/ld(+0x29d69)[0x5659cd69]
/usr/bin/ld(+0x2a385)[0x5659d385]
/usr/bin/ld(+0x2b1bf)[0x5659e1bf]
/usr/bin/ld(+0x1a2e6)[0x5658d2e6]
/usr/bin/ld(main+0x61f)[0x5657a3df]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf749d276]
/usr/bin/ld(+0x7aeb)[0x5657aaeb]
=== Memory map: 
56573000-566ad000 r-xp  08:06 10898403   
/usr/bin/i686-linux-gnu-ld.bfd
566ad000-566b1000 r--p 00139000 08:06 10898403   
/usr/bin/i686-linux-gnu-ld.bfd
566b1000-566b3000 rw-p 0013d000 08:06 10898403   
/usr/bin/i686-linux-gnu-ld.bfd
566b3000-566b4000 rw-p  00:00 0 
56e65000-57088000 rw-p  00:00 0  [heap]
f730-f7321000 rw-p  00:00 0 
f7321000-f740 ---p  00:00 0 
f745-f746c000 r-xp  08:06 11026496   

Bug#843898: Something to try

[Sebastian P . Luque]

On Sun, 20 Nov 2016 21:01:08 +,
Tobias Hansen  wrote:

[...]

>> $ ls -alh ~/.local/lib/python2.7/site-packages/backports/ total 12K
>> drwxr-xr-x 3 sluque sluque 4.0K Oct 30 16:16 .  drwx-- 20 sluque
>> sluque 4.0K Oct 30 16:18 ..  drwxr-xr-x 2 sluque sluque 4.0K Oct 30
>> 16:16 configparser

> What happens if you rename that for a moment? Does it fix the problem?

No; same result.

-- 
Seb

Bug#845169: ruby-carrierwave: FTBFS in testing (unknown option '--initialize-insecure')

[Santiago Vila]

Package: src:ruby-carrierwave
Version: 0.10.0+gh-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=ruby --with ruby
   dh_testdir -i -O--buildsystem=ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>/ruby-carrierwave-0.10.0+gh'
chmod +x debian/start_mysqld_and_auto_install.sh
debian/start_mysqld_and_auto_install.sh
2016-11-15 18:34:38 0 [Warning] TIMESTAMP with implicit DEFAULT value is 
deprecated. Please use --explicit_defaults_for_timestamp server option (see 
documentation for more details).
2016-11-15 18:34:38 0 [Note] /usr/sbin/mysqld (mysqld 5.6.30-1) starting as 
process 5845 ...
2016-11-15 18:34:38 5845 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Table 'mysql.plugin' doesn't exist
2016-11-15 18:34:38 5845 [ERROR] Can't open the mysql.plugin table. Please run 
mysql_upgrade to create it.
2016-11-15 18:34:38 5845 [Note] InnoDB: Using atomics to ref count buffer pool 
pages
2016-11-15 18:34:38 5845 [Note] InnoDB: The InnoDB memory heap is disabled
2016-11-15 18:34:38 5845 [Note] InnoDB: Mutexes and rw_locks use GCC atomic 
builtins
2016-11-15 18:34:38 5845 [Note] InnoDB: Memory barrier is not used
2016-11-15 18:34:38 5845 [Note] InnoDB: Compressed tables use zlib 1.2.8
2016-11-15 18:34:38 5845 [Note] InnoDB: Using Linux native AIO
2016-11-15 18:34:38 5845 [Note] InnoDB: Not using CPU crc32 instructions
2016-11-15 18:34:38 5845 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-11-15 18:34:39 5845 [Note] InnoDB: Completed initialization of buffer pool
2016-11-15 18:34:39 5845 [Note] InnoDB: The first specified data file ./ibdata1 
did not exist: a new database to be created!
2016-11-15 18:34:39 5845 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
2016-11-15 18:34:39 5845 [Note] InnoDB: Database physically writes the file 
full: wait...
2016-11-15 18:34:39 5845 [Note] InnoDB: Setting log file ./ib_logfile101 size 
to 48 MB
2016-11-15 18:34:39 5845 [Note] InnoDB: Setting log file ./ib_logfile1 size to 
48 MB
2016-11-15 18:34:40 5845 [Note] InnoDB: Renaming log file ./ib_logfile101 to 
./ib_logfile0
2016-11-15 18:34:40 5845 [Warning] InnoDB: New log files created, LSN=45781
2016-11-15 18:34:40 5845 [Note] InnoDB: Doublewrite buffer not found: creating 
new
2016-11-15 18:34:40 5845 [Note] InnoDB: Doublewrite buffer created
2016-11-15 18:34:40 5845 [Note] InnoDB: 128 rollback segment(s) are active.
2016-11-15 18:34:40 5845 [Warning] InnoDB: Creating foreign key constraint 
system tables.
2016-11-15 18:34:40 5845 [Note] InnoDB: Foreign key constraint system tables 
created
2016-11-15 18:34:40 5845 [Note] InnoDB: Creating tablespace and datafile system 
tables.
2016-11-15 18:34:40 5845 [Note] InnoDB: Tablespace and datafile system tables 
created.
2016-11-15 18:34:40 5845 [Note] InnoDB: Waiting for purge to start
2016-11-15 18:34:40 5845 [Note] InnoDB: 5.6.30 started; log sequence number 0
2016-11-15 18:34:40 5845 [ERROR] /usr/sbin/mysqld: unknown option 
'--initialize-insecure'
2016-11-15 18:34:40 5845 [ERROR] Aborting

2016-11-15 18:34:40 5845 [Note] Binlog end
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'partition'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'ARCHIVE'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'BLACKHOLE'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_SYS_DATAFILES'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_SYS_TABLESPACES'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN_COLS'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_SYS_FOREIGN'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_SYS_FIELDS'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_SYS_COLUMNS'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_SYS_INDEXES'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_SYS_TABLESTATS'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_SYS_TABLES'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_FT_INDEX_TABLE'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_FT_INDEX_CACHE'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_FT_CONFIG'
2016-11-15 18:34:40 5845 [Note] Shutting down plugin 'INNODB_FT_BEING_DELETED'
2016-11-15 18:34:40 5845 [Note] Shutting 

Bug#845167: lemonldap-ng: FTBFS randomly (failing tests)

[Santiago Vila]

Package: src:lemonldap-ng
Version: 1.9.5-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with systemd
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
/usr/bin/make configure STORAGECONFFILE=/etc/lemonldap-ng/lemonldap-ng.ini \
PERLOPTIONS="INSTALLDIRS=vendor"
make[2]: Entering directory '/<>'
Warning: prerequisite Mouse 0 not found.
Checking if your kit is complete...
Looks good
"\x{00c3}" does not map to ascii at /usr/share/perl/5.24/ExtUtils/MakeMaker.pm 
line 1185.

[... snipped ...]

Expect 200, get 401

#   Failed test 'Headername1 is set to "Auth-User"'
#   at t/62-Lemonldap-NG-Handler-Nginx.t line 44.
Expect Headername1 => "Auth-User", get $VAR1 = {
  'Content-Type' => 'text/html',
  'Content-Length' => 324,
  'Location' => 
'http://auth.example.com/?url=aHR0cDovL3Rlc3QxLmV4YW1wbGUuY29tLw=='
};


#   Failed test 'Headervalue1 is set to "dwho"'
#   at t/62-Lemonldap-NG-Handler-Nginx.t line 46.
Expect Headervalue1 => "dwho", get $VAR1 = {
  'Content-Type' => 'text/html',
  'Content-Length' => 324,
  'Location' => 
'http://auth.example.com/?url=aHR0cDovL3Rlc3QxLmV4YW1wbGUuY29tLw=='
};


#   Failed test 'Code is 403'
#   at t/62-Lemonldap-NG-Handler-Nginx.t line 53.
Expect 403, get 401
# Looks like you failed 4 tests of 15.
t/62-Lemonldap-NG-Handler-Nginx.t  
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/15 subtests 
t/99-pod.t ... ok

Test Summary Report
---
t/62-Lemonldap-NG-Handler-Nginx.t  (Wstat: 1024 Tests: 15 Failed: 4)
  Failed tests:  9-11, 13
  Non-zero exit status: 4
Files=14, Tests=104,  3 wallclock secs ( 0.04 usr  0.00 sys +  2.17 cusr  0.14 
csys =  2.35 CPU)
Result: FAIL
Failed 1/14 test programs. 4/104 subtests failed.
Makefile:949: recipe for target 'test_dynamic' failed
make[2]: *** [test_dynamic] Error 255
make[2]: Leaving directory '/<>/lemonldap-ng-handler'
Makefile:324: recipe for target 'handler_test' failed
make[1]: *** [handler_test] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test returned exit code 2
debian/rules:20: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The build was made on several QEMU/KVM virtual machines with one CPU using 
sbuild.
The failure happens randomly. Sometimes it fails, sometimes it does not.

The failing tests are not always the same. As a summary, these are the
three which I have seen to fail so far:

t/60-Lemonldap-NG-Handler-PSGI.t
t/61-Lemonldap-NG-Handler-PSGI-Server.t
t/62-Lemonldap-NG-Handler-Nginx.t

I attach several build logs.

Thanks.

lemonldap-ng_1.9.5-1_amd64-20161115T150604Z.gz
Description: application/gzip


lemonldap-ng_1.9.5-1_amd64-20161117T141317Z.gz
Description: application/gzip


lemonldap-ng_1.9.5-1_amd64-20161117T141808Z.gz
Description: application/gzip


lemonldap-ng_1.9.5-1_amd64-20161120T225244Z.gz
Description: application/gzip


lemonldap-ng_1.9.5-1_amd64-20161120T225252Z.gz
Description: application/gzip


lemonldap-ng_1.9.5-1_amd64-20161120T230228Z.gz
Description: application/gzip

Bug#845164: ruby-spy: FTBFS randomly (failing tests)

[Santiago Vila]

Package: src:ruby-spy
Version: 0.4.3-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_testdir -i -O--buildsystem=ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby

[... snipped ...]

TestAnyInstanceOf#test_it_overides_all_methods = 0.00 s = .
Spy::TestSubroutine#test_hook_mimics_class_protected_visibility = 0.00 s = .
Spy::TestSubroutine#test_hook_mimics_protected_visibility = 0.00 s = .
Spy::TestSubroutine#test_spy_can_hook_record_and_unhook_a_meta_method = 0.00 s 
= .
Spy::TestSubroutine#test_spy_cannot_hook_a_non_existent_method = 0.00 s = .
Spy::TestSubroutine#test_spy_hook_raises_an_error_on_an_already_hooked_method = 
0.00 s = .
Spy::TestSubroutine#test_has_been_called_with? = 0.00 s = .
Spy::TestSubroutine#test_that_method_spy_keeps_arity = 0.00 s = .
Spy::TestSubroutine#test_spy_get_can_retrieve_a_spy = 0.00 s = .
Spy::TestSubroutine#test_hook_mimics_class_private_visibility = 0.00 s = .
Spy::TestSubroutine#test_spy_and_return_can_call_a_block_that_recieves_a_block 
= 0.00 s = .
Spy::TestSubroutine#test_hook_mimics_private_visibility = 0.00 s = .
Spy::TestSubroutine#test_spy_hook_records_number_of_calls = 0.00 s = .
Spy::TestSubroutine#test_spy_can_hook_and_record_a_method_call_on_a_constant = 
0.00 s = .
Spy::TestSubroutine#test_spy_can_unhook_a_method = 0.00 s = .
Spy::TestSubroutine#test_spy_and_return_can_call_a_block_raises_when_there_is_an_arity_mismatch
 = 0.00 s = .
Spy::TestSubroutine#test_spy_can_hook_a_non_existent_method_if_param_set = 0.00 
s = .
Spy::TestSubroutine#test_spy_and_return_returns_the_set_value = 0.00 s = .
Spy::TestSubroutine#test_hook_mimics_class_public_visibility = 0.00 s = .
Spy::TestSubroutine#test_spy_and_return_can_call_a_block = 0.00 s = .
Spy::TestSubroutine#test_spy_can_hook_and_record_a_method_call = 0.00 s = .
Spy::TestSubroutine#test_spy_can_hook_and_record_a_meta_method_call_on_a_constant
 = 0.00 s = .
Spy::TestSubroutine#test_hook_mimics_public_visibility = 0.00 s = .
Spy::TestSubroutine#test_spy_on_hook_and_saves_spy = 0.00 s = .

Finished in 0.043358s, 1476.0886 runs/s, 2606.2189 assertions/s.

  1) Failure:
TestSpy#test_spy_on_hooks_and_saves_spy_with_array 
[/<>/test/integration/test_subroutine_spying.rb:31]:
--- expected
+++ actual
@@ -1 +1 @@
-[#, @singleton_method=true, @was_hooked=true, 
@calls=[#, 
@called_from="/<>/test/integration/test_subroutine_spying.rb:26:in 
`test_spy_on_hooks_and_saves_spy_with_array'", @args=[nil], @block=nil, 
@result="hello">], @do_not_check_plan_arity=false, @hooked=false, 
@method_owner=#, @original_method_visibility=:public, 
@arity_range=1..1, @original_method=#, 
@hook_opts={:visibility=>:public}, 
@plan=#/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:120>>,
 #, 
@singleton_method=true, @was_hooked=true, @calls=[#, 
@called_from="/<>/test
 /integration/test_subroutine_spying.rb:27:in 
`test_spy_on_hooks_and_saves_spy_with_array'", @args=[], @block=nil, 
@result="world">], @do_not_check_plan_arity=false, @hooked=false, 
@method_owner=#, @original_method_visibility=:public, 
@arity_range=0..0, @original_method=#, 
@hook_opts={:visibility=>:public}, 
@plan=#/debian/ruby-spy/usr/lib/ruby/vendor_ruby/spy/subroutine.rb:120>>]
+[#, @singleton_method=true, @was_hooked=true, 
@calls=[#, @called_from="/<>/test/integration/test_api.rb:12:in 
`test_assert_received'", @args=[:hello], @block=nil, @result=nil>], 
@do_not_check_plan_arity=false, @hooked=false, 
@method_owner=#, @original_method_visibility=:public, 
@arity_range=1..1, @original_method=#, 
@hook_opts={:visibility=>:public}>, #, 
@singleton_method=true, @was_hooked=true, @calls=[#, 
@called_from="/<>/test/integration/test_api.rb:25:in 
`test_have_received'", @args=[:foo], @block=nil, @result=nil>], 
@do_not_check_plan_arity=false, @hooked=false, @meth
 od_owner=#, @original_method_visibility=:public, 
@arity_range=1..1, @original_method=#, 
@hook_opts={:visibility=>:public}>, #, 
@singleton_method=true, @was_hooked=true, @calls=[#, 
@called_from="/<>/test/integration/test_api.rb:17:in 
`test_assert_received_with'", @args=[:world], @block=nil, @result=nil>], 
@do_not_check_plan_arity=false, @hooked=false, 
@method_owner=#, @original_method_visibility=:public, 
@arity_range=1..1, @original_method=#, 
@hook_opts={:visibility=>:public}>, #, 
@singleton_method=true, 

Bug#828589: uw-imap: FTBFS with openssl 1.1.0

[Magnus Holmgren]

torsdag 3 november 2016 kl. 00:23:37 CET skrev  Sebastian Andrzej Siewior:
> On 2016-09-12 17:00:28 [+0200], Kurt Roeckx wrote:
> > > But this problem existed before 1.1.0 support (this patch).
> > > What do you recommend here? The builtin usage
> > > (X509_VERIFY_PARAM_set_hostflags()) looks simple. The alternative
> > > X509_check_host() is 1.0.2+ and since it can not be applied to stable I
> > > don't see the point. I would add this for 1.1.0 and keep the current
> > > validation for < 1.1.0.
> > 
> > We don't want to upload this to Debian stable in any case.  But if
> > it's only doing the right thing with 1.1.0 that works for me.
> 
> So I've been looking at this again. The patch attached should do what
> you asked for. It is so untested that EA is already using it…

I'm thinking we can and should keep using CTX functions (e.g. 
SSL_CTX_get0_param()), which minimizes the amount of changes. And your 
cert_verify() seems to essentially do the same things as the existing 
ssl_open_verify().

> Ehm. One thing: The callback that uw-imap invokes
>   scq(err_str_cpy, "hostname", cert_subj)
> 
> expects to pass the hostname of the connection. I have no idea how to
> obtain it at that point. 

ssl_start_work() puts it in a static variable that ssl_open_verify() reads.

I have tested my patch to the extent that I get a validation error when I use 
"mailutil check" with an IP address, but not when I use the hostname. I 
haven't tested all kinds of SAN shenanigans, but I suppose we can trust 
OpenSSL here. The error message is of course different since we rely on the 
built-in validation routine instead of our ssl_validate_cert().

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer --- a/src/osdep/unix/ssl_unix.c
+++ b/src/osdep/unix/ssl_unix.c
@@ -227,8 +227,16 @@ static char *ssl_start_work (SSLSTREAM *
 /* disable certificate validation? */
   if (flags & NET_NOVALIDATECERT)
 SSL_CTX_set_verify (stream->context,SSL_VERIFY_NONE,NIL);
-  else SSL_CTX_set_verify (stream->context,SSL_VERIFY_PEER,ssl_open_verify);
+  else {
+#if OPENSSL_VERSION_NUMBER >= 0x1010  
+  X509_VERIFY_PARAM *param = SSL_CTX_get0_param(stream->context);
+  X509_VERIFY_PARAM_set_hostflags(param, X509_CHECK_FLAG_NO_PARTIAL_WILDCARDS);
+  X509_VERIFY_PARAM_set1_host(param, host, 0);
+#endif
+
+  SSL_CTX_set_verify (stream->context,SSL_VERIFY_PEER,ssl_open_verify);
 /* set default paths to CAs... */
+  }
   SSL_CTX_set_default_verify_paths (stream->context);
 /* ...unless a non-standard path desired */
   if (s = (char *) mail_parameters (NIL,GET_SSLCAPATH,NIL))
@@ -266,6 +274,7 @@ static char *ssl_start_work (SSLSTREAM *
   if (SSL_write (stream->con,"",0) < 0)
 return ssl_last_error ? ssl_last_error : "SSL negotiation failed";
 /* need to validate host names? */
+#if OPENSSL_VERSION_NUMBER < 0x1010
   if (!(flags & NET_NOVALIDATECERT) &&
   (err = ssl_validate_cert (cert = SSL_get_peer_certificate (stream->con),
 host))) {
@@ -275,6 +284,7 @@ static char *ssl_start_work (SSLSTREAM *
 sprintf (tmp,"*%.128s: %.255s",err,cert ? cert->name : "???");
 return ssl_last_error = cpystr (tmp);
   }
+#endif
   return NIL;
 }
 
@@ -312,7 +322,7 @@ static int ssl_open_verify (int ok,X509_
  *	host to validate against
  * Returns: NIL if validated, else string of error message
  */
-
+#if OPENSSL_VERSION_NUMBER < 0x1010
 static char *ssl_validate_cert (X509 *cert,char *host)
 {
   int i,n;
@@ -342,6 +352,7 @@ static char *ssl_validate_cert (X509 *ce
   else ret = "Unable to locate common name in certificate";
   return ret;
 }
+#endif
 
 /* Case-independent wildcard pattern match
  * Accepts: base string


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

Bug#844239: [request-tracker-maintainers] Bug#844239: request-tracker4: FTBFS: t/web/gnupg-select-keys-on-update.t failure

[Emilio Pozuelo Monfort]

On 20/11/16 21:32, Niko Tyni wrote:
> On Sun, Nov 13, 2016 at 07:13:54PM +0200, Niko Tyni wrote:
>> Package: request-tracker4
>> Version: 4.2.13-3
>> Severity: serious
>>
>> This package failed to build on the 'all' buildd:
>>
>>   
>> https://buildd.debian.org/status/fetch.php?pkg=request-tracker4=all=4.2.13-3=1477439960
>>
>>   #   Failed test 'problems with passphrase'
>>   #   at t/web/gnupg-select-keys-on-update.t line 40.
>>   # searched: "\x{0a}\x{0a}\x{0a}  
>> \x{0a}>   #   can't find: "unable to sign outgoing email messages"
>>   # LCSS: " message"
>>   # LCSS context: " 
> I can't reproduce this locally, and neither can others. It obviously
> worked for Dominic when he uploaded it.
> 
> @w-b-team: could you please give it back to see if this persists on
> the buildds?
> 
> gb request-tracker4_4.2.13-3 . all

Given back.

Emilio

Bug#845143: marked as done (cross-toolchain-base: FTBFS in stage1 gcc: libiberty uses libc headers)

[Debian Bug Tracking System]

Your message dated Mon, 21 Nov 2016 00:33:17 +0100
with message-id <6f5e8018-4a94-fb0a-8bd6-0b871eb38...@debian.org>
and subject line Re: Bug#845143: cross-toolchain-base: FTBFS in stage1 gcc: 
libiberty uses libc headers
has caused the Debian Bug report #845143,
regarding cross-toolchain-base: FTBFS in stage1 gcc: libiberty uses libc headers
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.)


-- 
845143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cross-toolchain-base
Version: 13
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

Hi Matthias,

Since a few gcc-6 uploads, cross-toolchain-base FTBFS. I don't know
exactly which version made it break, but 6.2.1-4 is known to be broken
and 6.2.0-13 is known to not have this issue (which is different from
#844866). The symptom is:

| config.status: creating config.h
| config.status: config.h is unchanged
| config.status: executing default commands
| if [ x"" != x ]; then \
|   /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ 
-B/usr/s390x-linux-gnu/bin/ -B/usr/s390x-linux-gnu/lib/ -isystem 
/usr/s390x-linux-gnu/include -isystem /usr/s390x-linux-gnu/sys-include -isystem 
/<>/gcc/build/sys-include 
--sysroot=/<>/debian/tmp.s390x   -c -DHAVE_CONFIG_H -g -O2  -I. 
-I../../../src/libiberty/../include  -W -Wall -Wwrite-strings -Wc++-compat 
-Wstrict-prototypes -pedantic  -D_GNU_SOURCE  ../../../src/libiberty/regex.c -o 
pic/regex.o; \
| else true; fi
| if [ x"" != x ]; then \
|   /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ 
-B/usr/s390x-linux-gnu/bin/ -B/usr/s390x-linux-gnu/lib/ -isystem 
/usr/s390x-linux-gnu/include -isystem /usr/s390x-linux-gnu/sys-include -isystem 
/<>/gcc/build/sys-include 
--sysroot=/<>/debian/tmp.s390x   -c -DHAVE_CONFIG_H -g -O2  -I. 
-I../../../src/libiberty/../include  -W -Wall -Wwrite-strings -Wc++-compat 
-Wstrict-prototypes -pedantic  -D_GNU_SOURCE   ../../../src/libiberty/regex.c 
-o noasan/regex.o; \
| else true; fi
| /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ 
-B/usr/s390x-linux-gnu/bin/ -B/usr/s390x-linux-gnu/lib/ -isystem 
/usr/s390x-linux-gnu/include -isystem /usr/s390x-linux-gnu/sys-include -isystem 
/<>/gcc/build/sys-include 
--sysroot=/<>/debian/tmp.s390x   -c -DHAVE_CONFIG_H -g -O2  -I. 
-I../../../src/libiberty/../include  -W -Wall -Wwrite-strings -Wc++-compat 
-Wstrict-prototypes -pedantic  -D_GNU_SOURCE ../../../src/libiberty/regex.c -o 
regex.o
| ../../../src/libiberty/regex.c:52:25: fatal error: sys/types.h: No such file 
or directory
|  #  include 
|  ^
| compilation terminated.
| Makefile:1166: recipe for target 'regex.o' failed
| make[5]: *** [regex.o] Error 1
| make[5]: Leaving directory 
'/<>/gcc/build/s390x-linux-gnu/libiberty'
| Makefile:11866: recipe for target 'all-target-libiberty' failed
| make[4]: *** [all-target-libiberty] Error 2
| make[4]: Leaving directory '/<>/gcc/build'
| Makefile:861: recipe for target 'all' failed
| make[3]: *** [all] Error 2
| make[3]: Leaving directory '/<>/gcc/build'

It occurs during the stage1 gcc build while building libiberty. The
issue is independent of the target architecture. s390x just happens to
be the first one tried by cross-toolchain-base. We see that regex.c
includes libc headers, but a stage1 build should not be using libc
headers. I looked into the recent gcc-6 packaging commits and couldn't
identify an obvious cause. I also looked into recently successful cross
compiler builds an it seems that formerly libiberty was only built for
the host architecture and not for the target architecture in stage1.

I am Ccing d-cross@l.d.o to gain more eyeballs for the issue. Any ideas?

Helmut
--- End Message ---
--- Begin Message ---
Version: 14--- End Message ---

Bug#844701: dpkg: buggy dpkg 1.8.11 and above ? Package: dpkg

[shirish शिरीष]

in-line :-

On 21/11/2016, Guillem Jover  wrote:
> Hi!
>
> On Mon, 2016-11-21 at 01:47:45 +0530, shirish शिरीष wrote:
>> The patch didn't work :(
>
> Well that it didn't work was actually also very useful! Because in
> your case it should not have worked due to having debug output
> enabled. If you retry it again w/o debugging enabled it should work,
> and the attached patch should make it impervious to debug settings.
>
>> So it seems some issue is still there. I'll reboot and see if the
>> issue still persists.
>
> Yes and no. The original problem should be gone (the problem with the
> exit code, the new problem with the non-empty output string due to the
> debug output is new, but very welcome as it should make the code more
> robust. Thanks for that. Attached new patch.
>
> (BTW reboot should not in general fix this kind of issues. :)

Hi Gulllem,

I don't know whether the NEW patch you shared should have been on top
of the OLD patch or should do from scratch, hence did it from scratch
. Sorry, am new to this patching business :)

Anyways, think it got through but for some reason dpkg died/failed it
says , see -

─[$] sudo aptitude reinstall cme libconfig-model-perl
libconfig-model-dpkg-perl fonts-arphic-uming

The following packages will be REINSTALLED:
  cme fonts-arphic-uming libconfig-model-dpkg-perl libconfig-model-perl

0 packages upgraded, 0 newly installed, 4 reinstalled, 0 to remove and
45 not upgraded.

Need to get 0 B/8,465 kB of archives. After unpacking 0 B will be used.
D01: ensure_diversions: new, (re)loading
D01: ensure_statoverrides: new, (re)loading
(Reading database ... 1207479 files and directories currently installed.)
Preparing to unpack .../0-fonts-arphic-uming_0.2.20080216.2-7_all.deb ...
D01: process_archive oldversionstatus=broken due to postinst failure
D01: ensure_diversions: same, skipping
D01: cmpversions a='0:0.2.20080216.2-7' b='0:0.2.20080216.2-6~' r=1
D01: cmpversions a='0:0.2.20080216.2-7' b='0:0.2.20080216.2-1' r=6
D01: ensure_diversions: same, skipping
Unpacking fonts-arphic-uming (0.2.20080216.2-7) over (0.2.20080216.2-7) ...
D01: ensure_diversions: same, skipping
D01: process_archive updating info directory
D01: generating infodb hashfile
Preparing to unpack .../1-cme_1.015-1_all.deb ...
D01: process_archive oldversionstatus=broken due to postinst failure
D01: ensure_diversions: same, skipping
D01: cmpversions a='0:1.015-1' b='0:1.008-1~' r=1
D01: ensure_diversions: same, skipping
Unpacking cme (1.015-1) over (1.015-1) ...
D01: ensure_diversions: same, skipping
D01: process_archive updating info directory
D01: generating infodb hashfile
Preparing to unpack .../2-libconfig-model-perl_2.094-1_all.deb ...
D01: process_archive oldversionstatus=broken due to postinst failure
D01: ensure_diversions: same, skipping
D01: cmpversions a='0:2.094-1' b='0:2.070-1~' r=2
D01: cmpversions a='0:2.094-1' b='0:2.073-1~' r=2
D01: cmpversions a='0:2.094-1' b='0:2.070-1~' r=2
D01: cmpversions a='0:2.094-1' b='0:2.075-2~' r=2
D01: ensure_diversions: same, skipping
Unpacking libconfig-model-perl (2.094-1) over (2.094-1) ...
D01: ensure_diversions: same, skipping
D01: process_archive updating info directory
D01: generating infodb hashfile
Preparing to unpack .../3-libconfig-model-dpkg-perl_2.085_all.deb ...
D01: process_archive oldversionstatus=broken due to postinst failure
D01: ensure_diversions: same, skipping
D01: cmpversions a='0:2.085' b='0:2.070~' r=1
D01: ensure_diversions: same, skipping
Unpacking libconfig-model-dpkg-perl (2.085) over (2.085) ...
D01: ensure_diversions: same, skipping
D01: process_archive updating info directory
D01: generating infodb hashfile
D01: cmpversions a='0:2016.03.30' b='0:2016.05.24' r=-2
D01: cmpversions a='0:1.18.15+nmu1' b='0:1.16' r=2
D01: cmpversions a='0:1.18.15+nmu1' b='0:1.16' r=2
D01: cmpversions a='0:1.18.15+nmu1' b='0:1.16' r=2
D01: ensure_diversions: new, (re)loading
D01: process queue pkg fonts-arphic-uming:all queue.len 5 progress 1, try 1
Setting up fonts-arphic-uming (0.2.20080216.2-7) ...
D01: deferred_configure updating conffiles
D01: cmpversions a='0:0.2.20080216.2-7' b='0:0.2.20080216.2-6~' r=1
D01: cmpversions a='0:0.2.20080216.2-7' b='0:0.2.20080216.2-1' r=6
D01: ensure_diversions: same, skipping
D01: process queue pkg cme:all queue.len 4 progress 1, try 1
D01: process queue pkg libconfig-model-perl:all queue.len 4
progress 2, try 1
Setting up libconfig-model-perl (2.094-1) ...
D01: deferred_configure updating conffiles
D01: cmpversions a='0:2.094-1' b='0:2.070-1~' r=2
D01: cmpversions a='0:2.094-1' b='0:2.073-1~' r=2
D01: cmpversions a='0:2.094-1' b='0:2.070-1~' r=2
D01: cmpversions a='0:2.094-1' b='0:2.075-2~' r=2
D01: ensure_diversions: same, skipping
D01: process queue pkg 

Processed: Here is a working patch, provided by Teppo Mäenpää

[Debian Bug Tracking System]

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

> tag 725768 patch
Bug #725768 [tkcvs] tkcvs: depends on tk8.4|tk8.5 and calls /usr/bin/wish
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#725768: Here is a working patch, provided by Teppo Mäenpää

[Martin Quinson]

tag 725768 patch
thanks

Hello,

attached is a trival patch (provided by Teppo Mäenpää). I just tested,
and it works rather well: the package builds and installs like a charm
with this change. Once installed, tkdiff seems to work (at least, it
starts).

Tim, could you please take care of this grave bug so that your package
could reintegrate testing? If not, could someone NMU this package,
please?

Thanks in advance, 
Mt.

-- 
There are only two kinds of programming languages: those people always
bitch about and those nobody uses.   -- Bjarne Stroustrup.


signature.asc
Description: PGP signature

Bug#838228: marked as done (src:lakai: maintainer address bounces)

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 23:18:20 +
with message-id 
and subject line Bug#838228: fixed in lakai 0.1-2
has caused the Debian Bug report #838228,
regarding src:lakai: maintainer address bounces
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.)


-- 
838228: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838228
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lakai
Version: 0.1-1
Severity: serious

The maintainer address for lakai bounces, see below.

Ansgar

Mail Delivery System  writes:
> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   f...@agnula.org
> No Such User Here
>
> Reporting-MTA: dns; server211.web-hosting.com
>
> Action: failed
> Final-Recipient: rfc822;f...@agnula.org
> Status: 5.0.0
>
> From: Debian FTP Masters 
> Subject: lakai_0.1-1.1_source.changes ACCEPTED into unstable
> To: Gustavo Soares de Lima , Free Ekanayaka 
> ,  
> Date: Sat, 17 Sep 2016 23:48:29 + (18 hours, 6 minutes, 38 seconds ago)
>
>
>
> Accepted:
>
> Format: 1.8
> Date: Wed, 07 Sep 2016 16:41:52 +
> Source: lakai
> Binary: lakai
> Architecture: source
> Version: 0.1-1.1
> Distribution: unstable
> Urgency: medium
> Maintainer: Free Ekanayaka 
> Changed-By: Gustavo Soares de Lima 
> Description:
>  lakai  - transfers samples between a PC and an AKAI sampler
> Closes: 449603 450202 817516 835651
> Changes:
>  lakai (0.1-1.1) unstable; urgency=medium
>  .
>* Non-maintainer upload.
>* debian/compat:
>- Update level to 9. (Closes: #817516)
>* debian/control:
>- Added Homepage. (Closes: #835651)
>- Bumped level debhelper to 9.
>- Bumped Standards-Version to 3.9.8.
>* debian/watch:
>- Update. (Closes: #449603, #450202).
> Checksums-Sha1:
>  eb85a022cc9c158c575d0dd8d43e7076c804bc5d 1617 lakai_0.1-1.1.dsc
>  245deda9478e93c005f0a93182b7b806317422b6 2299 lakai_0.1-1.1.diff.gz
> Checksums-Sha256:
>  4b94353b8c53f3cd0ed9cf30c96afdde349d528c24c6f8d76dd835ffe5932b5e 1617 
> lakai_0.1-1.1.dsc
>  811672d01e70007ca2c2631d4149b9efe44289a32cd033ae88af4e87765c37a4 2299 
> lakai_0.1-1.1.diff.gz
> Files:
>  ad8d9d6e95cd7de55b83b9a0d7228f5c 1617 sound optional lakai_0.1-1.1.dsc
>  15b143eaaa70c852ed5d02f935464f9a 2299 sound optional lakai_0.1-1.1.diff.gz
>
>
>
> Thank you for your contribution to Debian.
> --
--- End Message ---
--- Begin Message ---
Source: lakai
Source-Version: 0.1-2

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

Debian distribution maintenance software
pp.
Free Ekanayaka  (supplier of updated lakai 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: Sun, 20 Nov 2016 21:07:22 +
Source: lakai
Binary: lakai
Architecture: source amd64
Version: 0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Free Ekanayaka 
Description:
 lakai  - transfers samples between a PC and an AKAI sampler
Closes: 488901 664387 838228
Changes:
 lakai (0.1-2) unstable; urgency=medium
 .
   * Set maintainer to Debian Multimedia (Closes: #838228)
   * Drop build dependency on dpatch (Closes: #664387)
   * Port debian/copyright to format 1.0
   * Fix various lintian warnings (Closes: #488901)
   * Add Vcs control headers
Checksums-Sha1:
 a0ac7d2c1180ac4da70fbebc767c13cf36f97c56 1825 lakai_0.1-2.dsc
 05842736cf539a17c3de3bb2014bb83f9a6b1c58 2468 lakai_0.1-2.diff.gz
 e2183bfcb4197a2590edac3911e217581d01efac 16222 lakai-dbgsym_0.1-2_amd64.deb
 475a230172bf075ad8f1d46843d1da3fd207f6a6 37158 lakai_0.1-2_amd64.deb
Checksums-Sha256:
 

Processed: Part of the OpenSSL transition

[Debian Bug Tracking System]

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

> block 827061 by 845016 845030 845106
Bug #827061 [release.debian.org] transition: openssl
827061 was blocked by: 844311 835804 828549 828334 828500 835797 828389 828586 
828275 828409 828406 828139 828420 828272 828286 828512 828271 828577 828397 
828509 844303 828606 828250 828615 828416 828304 828445 814600 828476 828414 
844904 828302 828515 828438 828255 844951 828263 828362 828240 828324 828570 
828395 828288 828521 828504 835799 828541 828375 828306 828493 828442 828358 
828497 828292 828594 828323 828410 828440 828563 828579 828551 828264 828485 
828366 828280 828486 828479 828468 828278 822380 828472 828581 828617 828559 
837960 828315 828456 828388 828244 828600 828569 828349 828568 828603 828377 
828426 828290 828505 828233 828491 828448 828616 828367 828345 835785 828312 
844534 828319 828418 828346 844663 835793 828285 828343 828301 828513 828276 
835800 828369 828228 828265 828614 828597 828519 828571 828610 828313 828524 
828544 828399 828329 828281 828602 828262 828391 828480 828314 828582 828470 
844347 828593 844301 828327 828547 828253 828539 828417 828242 828361 844907 
828333 828589 828429 828401 828297 828620 844920 828473 828307 828351 828451 
828082 828608 828522 828528 828542 828394 828252 828578 828277 828517 828331 
828585 828548 828499 828303 828580 828422 828469 828439 828371 828423 828435 
828337 828390 843988 828575 828425 844948 828516 828461 828489 828573 844706 
828595 828511 828372 828368 828599 828496 828083 843682 828235 829465 828419 
828415 828428 828384 828555 835796 828449 841635 828458 836419 828562 828598 
828383 828260 835786 828481 844213 828492 828530 828482 828552 828381 828436 
828295 828453 844906 828359 828538 843532 828450 828536 828412 844664 828354 
828498 828248 844945 828533 828502 828590 828365 828535 828467 828553 828380 
828560 828601 828432 828609 828567 828554 844947 828465 835585 828471 828344 
828387 828308 844345 828287 808669 828488 828404 827076 828378 828400 828572 
828379 828462 828336 828127 844916 828503 828574 828386 828463 828558 828514 
828561 828532 828525 828261 828398 828374 828484 828269 828583 828330 828434 
828444 828483 828591 809271 828273 828529 828443 828523 828454 828293 828352 
828576 828342 828411 828238 828587 828249 844366 828283 828546 828510 828256 
828309 835798 828543 828393 828259 828237 828229 828282 828370 828245 828527 
828460 828495 828556 828316 828350 828526 828618 828321 828328 835789 828332 
828234 828407 828619 828251 828537 828296 828254 828364 828501 844949 828142 
828518 828239 828607 828507 828592 828289 828534 828341 828564 828550 828433 
828490 827068 828356 828310 828402 828274 828531 828477 828317 828284 828405 
828373 828376 835790 828305 828457 828508 828360 835811 828506 828363 828325 
828279 844833 828413 828403 828357 828232 828447 828540 828322 828430 828382 
828311 828545 828584 828474 828294 835794 828464 828231 843871 828446 828246 
828487 828612 828266 828565 828320 844254 828478 828396 828385 828557 828424 
828355 828268 828291 828452 828335 828494 828605 828257 828267 828340 828437 
844234 828392 828270 828243 828241 828298 835549 828326 828455 828588 844271 
828318 844926 828431 828520 828230 828427 828566 828300 828596 828604 828258 
828348 828421 828338 828441 828347 844503 829452 828613 828611 828339 828459 
828466
827061 was not blocking any bugs.
Added blocking bug(s) of 827061: 845106, 845016, and 845030
> thanks
Stopping processing here.

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

Bug#844701: dpkg: buggy dpkg 1.8.11 and above ? Package: dpkg

[Guillem Jover]

Hi!

On Mon, 2016-11-21 at 01:47:45 +0530, shirish शिरीष wrote:
> The patch didn't work :(

Well that it didn't work was actually also very useful! Because in
your case it should not have worked due to having debug output
enabled. If you retry it again w/o debugging enabled it should work,
and the attached patch should make it impervious to debug settings.

> So it seems some issue is still there. I'll reboot and see if the
> issue still persists.

Yes and no. The original problem should be gone (the problem with the
exit code, the new problem with the non-empty output string due to the
debug output is new, but very welcome as it should make the code more
robust. Thanks for that. Attached new patch.

(BTW reboot should not in general fix this kind of issues. :)

Thanks,
Guillem
diff --git i/scripts/dpkg-maintscript-helper.sh w/scripts/dpkg-maintscript-helper.sh
index f20d82647..54d42d9b5 100755
--- i/scripts/dpkg-maintscript-helper.sh
+++ w/scripts/dpkg-maintscript-helper.sh
@@ -49,8 +49,9 @@ rm_conffile() {
 	[ "${CONFFILE}" != "${CONFFILE#/}" ] || \
 		error "conffile '$CONFFILE' is not an absolute path"
 	# Use --compare-versions to validate the version number.
-	[ -z "$(dpkg --compare-versions -- "$LASTVERSION" eq '0' 2>&1)" ] || \
-		error "version '$LASTVERSION' is not valid"
+	VERSIONCHECK="$(dpkg -D0 --compare-versions -- "$LASTVERSION" eq '0' 2>&1 || true)"
+	[ -z "$VERSIONCHECK" ] || \
+		error "version '$LASTVERSION' is not valid: $VERSIONCHECK"
 
 	debug "Executing $0 rm_conffile in $DPKG_MAINTSCRIPT_NAME" \
 	  "of $DPKG_MAINTSCRIPT_PACKAGE"
@@ -163,8 +164,9 @@ mv_conffile() {
 	[ "${NEWCONFFILE}" != "${NEWCONFFILE#/}" ] || \
 		error "new-conffile '$NEWCONFFILE' is not an absolute path"
 	# Use --compare-versions to validate the version number.
-	[ -z "$(dpkg --compare-versions -- "$LASTVERSION" eq '0' 2>&1)" ] || \
-		error "version '$LASTVERSION' is not valid"
+	VERSIONCHECK="$(dpkg -D0 --compare-versions -- "$LASTVERSION" eq '0' 2>&1 || true)"
+	[ -z "$VERSIONCHECK" ] || \
+		error "version '$LASTVERSION' is not valid: $VERSIONCHECK"
 
 	debug "Executing $0 mv_conffile in $DPKG_MAINTSCRIPT_NAME" \
 	  "of $DPKG_MAINTSCRIPT_PACKAGE"

Bug#844914: rsyslog: FTBFS: Tests failures

[Michael Biebl]

Am 20.11.2016 um 23:24 schrieb Michael Biebl:
> Am 20.11.2016 um 17:55 schrieb Rainer Gerhards:
>> 2016-11-20 17:45 GMT+01:00 Michael Biebl :
>>> Am 20.11.2016 um 16:17 schrieb Rainer Gerhards:
 Lucas found the right root cause: It looks like the preload lib is not
 loaded on that platform. See
 https://github.com/rsyslog/rsyslog/issues/1268
>>>
>>> I'm not sure. I can't reproduce the issue with a standard Debian
>>> /etc/hosts which contains separate lines for localhost and the hostname.
>>
>> Well, the key point of the override library is that gethostname()
>> ALWAYS returns "", no matter how the system is configured. So if the
>> configured name is returned, the preload (or lib) did not work. I'd
>> outrule that the lib does not work, as it is ultra-small:
> 
> The override library is definitely loaded. I added some logging output
> to getLocalHostname to print out hnbuf. This logs localhost.
> Later on, rsyslog decides to use foo as hostname non-theless.
> 
> So my guess, rsyslog uses another code path (not based on gethostname)
> to determine the hostname.

I added some printf debug statements to runtime/net.c

Looking at getLocalHostname(), we do get an empty hostname from
gethostname() (from the overriden library) and at
https://github.com/rsyslog/rsyslog/blob/master/runtime/net.c#L1157

hnbuf is set to localhost (as expected).

At https://github.com/rsyslog/rsyslog/blob/master/runtime/net.c#L1164
dot is NULL so it calls gethostbyname() and iterates over the aliases.
This is where things go wrong. If I have an entry like this

127.0.0.1 foo localhost

fqdn is set to foo and this is what's returned from getLocalHostname.

Rainer, is that info sufficient for you to take it from here?



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#844914: rsyslog: FTBFS: Tests failures

[Michael Biebl]

Am 20.11.2016 um 17:55 schrieb Rainer Gerhards:
> 2016-11-20 17:45 GMT+01:00 Michael Biebl :
>> Am 20.11.2016 um 16:17 schrieb Rainer Gerhards:
>>> Lucas found the right root cause: It looks like the preload lib is not
>>> loaded on that platform. See
>>> https://github.com/rsyslog/rsyslog/issues/1268
>>
>> I'm not sure. I can't reproduce the issue with a standard Debian
>> /etc/hosts which contains separate lines for localhost and the hostname.
> 
> Well, the key point of the override library is that gethostname()
> ALWAYS returns "", no matter how the system is configured. So if the
> configured name is returned, the preload (or lib) did not work. I'd
> outrule that the lib does not work, as it is ultra-small:

The override library is definitely loaded. I added some logging output
to getLocalHostname to print out hnbuf. This logs localhost.
Later on, rsyslog decides to use foo as hostname non-theless.

So my guess, rsyslog uses another code path (not based on gethostname)
to determine the hostname.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#844701: dpkg: buggy dpkg 1.8.11 and above ? Package: dpkg

[shirish शिरीष]

at bottom :-

On 21/11/2016, shirish शिरीष  wrote:
> at bottom :-



> Trying with the new versions got this (again) -
>
> [$] sudo aptitude reinstall cme libconfig-model-perl
> libconfig-model-dpkg-perl fonts-arphic-uming
> [1:46:39]
> The following packages will be REINSTALLED:
>   cme fonts-arphic-uming libconfig-model-dpkg-perl libconfig-model-perl
> 0 packages upgraded, 0 newly installed, 4 reinstalled, 0 to remove and
> 45 not upgraded.
> Need to get 0 B/8,465 kB of archives. After unpacking 0 B will be used.
> D01: ensure_diversions: new, (re)loading
> D01: ensure_statoverrides: new, (re)loading
> (Reading database ... 1207479 files and directories currently installed.)
> Preparing to unpack .../0-fonts-arphic-uming_0.2.20080216.2-7_all.deb ...
> D01: process_archive oldversionstatus=broken due to postinst failure
> dpkg-maintscript-helper: error: version '0.2.20080216.2-1' is not
> valid: D01: cmpversions a='0:0.2.20080216.2-1' b='0:0' r=302
> dpkg: warning: subprocess old pre-removal script returned error exit status
> 1
> dpkg: trying script from the new package instead ...
> dpkg-maintscript-helper: error: version '0.2.20080216.2-1' is not
> valid: D01: cmpversions a='0:0.2.20080216.2-1' b='0:0' r=302
> dpkg: error processing archive
> /tmp/apt-dpkg-install-KUG6gL/0-fonts-arphic-uming_0.2.20080216.2-7_all.deb
> (--unpack):
>  subprocess new pre-removal script returned error exit status 1
> D01: ensure_diversions: same, skipping
> dpkg-maintscript-helper: error: version '0.2.20080216.2-6~' is not
> valid: D01: cmpversions a='0:0.2.20080216.2-6~' b='0:0' r=302
> dpkg: error while cleaning up:
>  subprocess installed post-installation script returned error exit status 1
> D01: ensure_diversions: same, skipping
> Preparing to unpack .../1-cme_1.015-1_all.deb ...
> D01: process_archive oldversionstatus=broken due to postinst failure
> dpkg-maintscript-helper: error: version '1.008-1~' is not valid:
> D01: cmpversions a='0:1.008-1~' b='0:0' r=1
> dpkg: warning: subprocess old pre-removal script returned error exit status
> 1
> dpkg: trying script from the new package instead ...
> dpkg-maintscript-helper: error: version '1.008-1~' is not valid:
> D01: cmpversions a='0:1.008-1~' b='0:0' r=1
> dpkg: error processing archive
> /tmp/apt-dpkg-install-KUG6gL/1-cme_1.015-1_all.deb (--unpack):
>  subprocess new pre-removal script returned error exit status 1
> D01: ensure_diversions: same, skipping
> dpkg-maintscript-helper: error: version '1.008-1~' is not valid:
> D01: cmpversions a='0:1.008-1~' b='0:0' r=1
> dpkg: error while cleaning up:
>  subprocess installed post-installation script returned error exit status 1
> D01: ensure_diversions: same, skipping
> Preparing to unpack .../2-libconfig-model-perl_2.094-1_all.deb ...
> D01: process_archive oldversionstatus=broken due to postinst failure
> dpkg-maintscript-helper: error: version '2.075-2~' is not valid:
> D01: cmpversions a='0:2.075-2~' b='0:0' r=1
> dpkg: warning: subprocess old pre-removal script returned error exit status
> 1
> dpkg: trying script from the new package instead ...
> dpkg-maintscript-helper: error: version '2.075-2~' is not valid:
> D01: cmpversions a='0:2.075-2~' b='0:0' r=1
> dpkg: error processing archive
> /tmp/apt-dpkg-install-KUG6gL/2-libconfig-model-perl_2.094-1_all.deb
> (--unpack):
>  subprocess new pre-removal script returned error exit status 1
> D01: ensure_diversions: same, skipping
> dpkg-maintscript-helper: error: version '2.070-1~' is not valid:
> D01: cmpversions a='0:2.070-1~' b='0:0' r=1
> dpkg: error while cleaning up:
>  subprocess installed post-installation script returned error exit status 1
> D01: ensure_diversions: same, skipping
> Preparing to unpack .../3-libconfig-model-dpkg-perl_2.085_all.deb ...
> D01: process_archive oldversionstatus=broken due to postinst failure
> dpkg-maintscript-helper: error: version '2.070~' is not valid:
> D01: cmpversions a='0:2.070~' b='0:0' r=1
> dpkg: warning: subprocess old pre-removal script returned error exit status
> 1
> dpkg: trying script from the new package instead ...
> dpkg-maintscript-helper: error: version '2.070~' is not valid:
> D01: cmpversions a='0:2.070~' b='0:0' r=1
> dpkg: error processing archive
> /tmp/apt-dpkg-install-KUG6gL/3-libconfig-model-dpkg-perl_2.085_all.deb
> (--unpack):
>  subprocess new pre-removal script returned error exit status 1
> D01: ensure_diversions: same, skipping
> dpkg-maintscript-helper: error: version '2.070~' is not valid:
> D01: cmpversions a='0:2.070~' b='0:0' r=1
> dpkg: error while cleaning up:
>  subprocess installed post-installation script returned error exit status 1
> D01: ensure_diversions: same, skipping
> D01: cmpversions a='0:2016.03.30' b='0:2016.05.24' r=-2
> D01: cmpversions a='0:1.18.15+nmu1' b='0:1.16' r=2
> D01: cmpversions a='0:1.18.15+nmu1' b='0:1.16' r=2
> 

Bug#841606: marked as done (dleyna-server: FTBFS: upnp.h:119:1: error: unknown type name 'GUPnPContextManager')

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 22:18:59 +
with message-id 
and subject line Bug#841606: fixed in dleyna-server 0.4.0-1.1
has caused the Debian Bug report #841606,
regarding dleyna-server: FTBFS: upnp.h:119:1: error: unknown type name 
'GUPnPContextManager'
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.)


-- 
841606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dleyna-server
Version: 0.4.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):
> /bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../..   -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/dleyna-1.0 -I/usr/include/gupnp-1.0 -I/usr/include/gssdp-1.0 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid -pthread 
> -I/usr/include/gssdp-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/gupnp-1.0 -I/usr/include/gssdp-1.0 -I/usr/include/libsoup-2.4 
> -I/usr/include/libxml2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
> -I/usr/include/gupnp-av-1.0 -pthread -I/usr/include/gupnp-dlna-2.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -include config.h -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wno-format-extra-args -c -o server.lo server.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/dleyna-1.0 -I/usr/include/gupnp-1.0 -I/usr/include/gssdp-1.0 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid -pthread 
> -I/usr/include/gssdp-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/gupnp-1.0 -I/usr/include/gssdp-1.0 -I/usr/include/libsoup-2.4 
> -I/usr/include/libxml2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid 
> -I/usr/include/gupnp-av-1.0 -pthread -I/usr/include/gupnp-dlna-2.0 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -include config.h -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wno-format-extra-args -c server.c  -fPIC -DPIC -o 
> .libs/server.o
> In file included from async.h:33:0,
>  from server.c:34:
> upnp.h:119:1: error: unknown type name 'GUPnPContextManager'
>  GUPnPContextManager *dls_upnp_get_context_manager(dls_upnp_t *upnp);
>  ^~~
> server.c: In function 'prv_control_point_start_service':
> server.c:1303:7: warning: passing argument 2 of 'dls_manager_new' from 
> incompatible pointer type [-Wincompatible-pointer-types]
>dls_upnp_get_context_manager(
>^~~~
> In file included from server.c:39:0:
> manager.h:35:16: note: expected 'GUPnPContextManager * {aka struct 
> _GUPnPContextManager *}' but argument is of type 'int *'
>  dls_manager_t *dls_manager_new(dleyna_connector_id_t connection,
> ^~~
> Makefile:553: recipe for target 'server.lo' failed
> make[3]: *** [server.lo] 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 

Processed: nfstrace: googletest related build failure

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 nfstrace: googletest related build failure
Bug #844859 [src:nfstrace] nfstrace: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
reference to `pthread_create'
Changed Bug title to 'nfstrace: googletest related build failure' from 
'nfstrace: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
reference to `pthread_create''.

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

Bug#844859: nfstrace: googletest related build failure

[Adrian Bunk]

Control: retitle -1 nfstrace: googletest related build failure

The actual error is:

...
CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
  add_library cannot create target "gmock" because another target with the
  same name already exists.  The existing target is a static library created
  in source directory "/usr/src/googletest/googlemock".  See documentation
  for policy CMP0002 for more details.
Call Stack (most recent call first):
  /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
  /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
  add_library cannot create target "gmock_main" because another target with
  the same name already exists.  The existing target is a static library
  created in source directory "/usr/src/googletest/googlemock".  See
  documentation for policy CMP0002 for more details.
Call Stack (most recent call first):
  /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
  /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
  install TARGETS given target "gmock" which does not exist in this
  directory.
...


16:11 < debfx> bunk: seems to be related to the /usr/src/gmock -> 
   googletest/googlemock symlink that googletest 1.8.0-1 introduced

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: cppformat: googletest related build failure

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 cppformat: googletest related build failure
Bug #844843 [src:cppformat] cppformat: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
reference to `pthread_create'
Changed Bug title to 'cppformat: googletest related build failure' from 
'cppformat: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
reference to `pthread_create''.

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

Bug#844843: cppformat: googletest related build failure

[Adrian Bunk]

Control: retitle -1 cppformat: googletest related build failure

The actual error is:

...
CMake Error at 
/usr/src/googletest/googletest/cmake/internal_utils.cmake:149 (add_library):
  add_library cannot create target "gmock" because another target with the
  same name already exists.  The existing target is a static library created
  in source directory "/usr/src/googletest/googlemock".  See documentation
  for policy CMP0002 for more details.
Call Stack (most recent call first):
  /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
  /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
  add_library cannot create target "gmock_main" because another target with
  the same name already exists.  The existing target is a static library
  created in source directory "/usr/src/googletest/googlemock".  See
  documentation for policy CMP0002 for more details.
Call Stack (most recent call first):
  /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
  /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
  install TARGETS given target "gmock" which does not exist in this
  directory.


-- Performing Test HAVE_FNO_DELETE_NULL_POINTER_CHECKS
-- Performing Test HAVE_FNO_DELETE_NULL_POINTER_CHECKS - Success
-- Performing Test HAVE_FNO_EXCEPTIONS_FLAG
-- Performing Test HAVE_FNO_EXCEPTIONS_FLAG - Success
-- Configuring incomplete, errors occurred!
...




< debfx> bunk: seems to be related to the /usr/src/gmock -> 
 googletest/googlemock symlink that googletest 1.8.0-1 introduced


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#844874: opensurgsim: googletest related build failure

[Adrian Bunk]

Control: retitle -1 opensurgsim: googletest related build failure

The actual error is:

...
-- Found GoogleMock: /usr/src/gmock  
CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 
(add_library):
  add_library cannot create target "gmock" because another target with the
  same name already exists.  The existing target is a shared library created
  in source directory "/usr/src/googletest/googlemock".  See documentation
  for policy CMP0002 for more details.
Call Stack (most recent call first):
  /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
  /usr/src/gmock/CMakeLists.txt:84 (cxx_library)


CMake Error at 
/usr/src/googletest/googletest/cmake/internal_utils.cmake:149 (add_library):
  add_library cannot create target "gmock_main" because another target with
  the same name already exists.  The existing target is a shared library
  created in source directory "/usr/src/googletest/googlemock".  See
  documentation for policy CMP0002 for more details.
Call Stack (most recent call first):
  /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 
(cxx_library_with_type)
  /usr/src/gmock/CMakeLists.txt:89 (cxx_library)


CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install):
  install TARGETS given target "gmock" which does not exist in this
  directory.


-- Found Doxygen: /usr/bin/doxygen (found version "1.8.12") 
-- Found MathJax: /usr/share/javascript/mathjax  
-- Using local MathJax: /usr/share/javascript/mathjax
-- Configuring incomplete, errors occurred!
...




16:11 < debfx> bunk: seems to be related to the /usr/src/gmock -> 
   googletest/googlemock symlink that googletest 1.8.0-1 introduced



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: opensurgsim: googletest related build failure

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 opensurgsim: googletest related build failure
Bug #844874 [src:opensurgsim] opensurgsim: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
reference to `pthread_create'
Changed Bug title to 'opensurgsim: googletest related build failure' from 
'opensurgsim: FTBFS: 
./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined 
reference to `pthread_create''.

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

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Jan Niehusmann]

On Mon, Nov 21, 2016 at 01:03:19AM +0400, Stepan Golosunov wrote:
> So far I do not know why using libssl1.1 together with a
> libssl1.0.2-using Qt wouldn't work.

Well I don't know enough about the dynamic linker and about the internals
of openssl to know if (indirectly) linking to both libraries at the same
time is fine.

If it was, that would be great news. Many mails in the thread "OpenSSL
1.1.0" on debian-devel seem to be based on the assumption that such
linking could cause bugs, and therefore packages can only transition in
clusters of packages linking to the same version of openssl.

Still, qt is only an example - the same holds true for other libraries
linking to openssl1.0-dev. There may be cases where your 2nd case
('Application passes OpenSSL objects from libssl1.1 to ...') is more
probable than with qt.

The safest way to avoid hidden bugs would still be changing SONAME and
package name, so package maintainers would be aware of the change and
could check their packages for compatibility.

But yes, it may be less work to somehow identify affected packages and
handle them directly instead of forcing all packages depending on curl
through a transition. Identifying those packages in a reliable way could
be difficult, though.

Jan

Bug#844393: blhc: diff for NMU version 0.07-0.2

[Joao Eriberto Mota Filho]

Control: tags 844393 + patch
Control: tags 844393 + pending

Dear maintainer,

I've prepared an NMU for blhc (versioned as 0.07-0.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards,

Eriberto

diff -Nru blhc-0.07/debian/changelog blhc-0.07/debian/changelog
--- blhc-0.07/debian/changelog  2016-09-10 21:40:10.0 -0300
+++ blhc-0.07/debian/changelog  2016-11-20 19:09:48.0 -0200
@@ -1,3 +1,12 @@
+blhc (0.07-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/10_support-dpkg-debarch-to-debtuple.patch: created to add
+support new dpkg versions which use debarch_to_debtuple. Thanks to Simon
+Ruderich . (Closes: #844393)
+
+ -- Joao Eriberto Mota Filho   Sun, 20 Nov 2016 19:09:48 
-0200
+
 blhc (0.07-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru blhc-0.07/debian/patches/10_support-dpkg-debarch-to-debtuple.patch 
blhc-0.07/debian/patches/10_support-dpkg-debarch-to-debtuple.patch
--- blhc-0.07/debian/patches/10_support-dpkg-debarch-to-debtuple.patch  
1969-12-31 21:00:00.0 -0300
+++ blhc-0.07/debian/patches/10_support-dpkg-debarch-to-debtuple.patch  
2016-11-20 19:09:48.0 -0200
@@ -0,0 +1,32 @@
+Description: add support new dpkg versions which use debarch_to_debtuple.
+ (Closes: #844393)
+Author: Simon Ruderich 
+Last-Update: 2016-11-16
+Index: blhc-0.07/bin/blhc
+===
+--- blhc-0.07.orig/bin/blhc
 blhc-0.07/bin/blhc
+@@ -1022,14 +1022,21 @@ foreach my $file (@ARGV) {
+ 
+ # Option or auto detected.
+ if ($arch) {
+-# The following was partially copied from dpkg-dev 1.18.10
++# The following was partially copied from dpkg-dev 1.18.15
+ # (/usr/share/perl5/Dpkg/Vendor/Debian.pm, _add_hardening_flags()),
+ # copyright Raphaël Hertzog , Kees Cook
+ # , Canonical, Ltd. licensed under GPL version 2 or
+ # later. Keep it in sync.
+ 
+ require Dpkg::Arch;
+-my ($abi, $os, $cpu) = Dpkg::Arch::debarch_to_debtriplet($arch);
++my ($os, $cpu);
++# Recent dpkg versions use a quadruplet for arch. Support both.
++eval {
++(undef, undef, $os, $cpu) = 
Dpkg::Arch::debarch_to_debtuple($arch);
++};
++if ($@) {
++(undef, $os, $cpu) = Dpkg::Arch::debarch_to_debtriplet($arch);
++}
+ 
+ # Disable unsupported hardening options.
+ if ($os !~ /^(?:linux|kfreebsd|knetbsd|hurd)$/
diff -Nru blhc-0.07/debian/patches/series blhc-0.07/debian/patches/series
--- blhc-0.07/debian/patches/series 1969-12-31 21:00:00.0 -0300
+++ blhc-0.07/debian/patches/series 2016-11-20 19:09:48.0 -0200
@@ -0,0 +1 @@
+10_support-dpkg-debarch-to-debtuple.patch

Processed: blhc: diff for NMU version 0.07-0.2

[Debian Bug Tracking System]

Processing control commands:

> tags 844393 + patch
Bug #844393 [blhc] blhc still uses dpkg architecture triplets
Added tag(s) patch.
> tags 844393 + pending
Bug #844393 [blhc] blhc still uses dpkg architecture triplets
Added tag(s) pending.

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

Processed: bug 842205 is forwarded to https://github.com/alastair/python-musicbrainzngs/issues/211

[Debian Bug Tracking System]

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

> forwarded 842205 https://github.com/alastair/python-musicbrainzngs/issues/211
Bug #842205 [src:musicbrainzngs] musicbrainzngs: FTBFS: UsageError: 
authorization required; use auth(user, pass) first
Set Bug forwarded-to-address to 
'https://github.com/alastair/python-musicbrainzngs/issues/211'.
> thanks
Stopping processing here.

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

Bug#844835: orthanc: FTBFS: build-dependency not installable: libssl-dev

[Sébastien Jodogne]

Dear Gert,


orthnac build depends on libdcmtk-dev, and this pulls in libssl1.0-dev
(since dcmtk (a) does not yet support openssl-1.1 and (b) it is used by
programs that require QT which conflicts with openssl-1.1).

libssl1.0-dev conflicts with libssl-dev, and hence the build failure.

The solution is to remove libssl-dev from the build dependencies, since
libdcmtk-dev already takes care of pulling the right version in.


Many thanks for this helpful explanation! I have just pushed your fix, 
together with two other patches [1]. Everything now looks fine in pbuilder.


Andreas, please would kindly sponsor the upload? Once again, thanks to 
both of you for your help!


Regards,
Sébastien-


[1] https://anonscm.debian.org/cgit/debian-med/orthanc.git/log/

Bug#844794: marked as done (zaqar: FTBFS: build-dependency not installable: python-autobahn (>= 0.10.1))

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 21:18:48 +
with message-id 
and subject line Bug#844714: fixed in pycparser 2.17-2
has caused the Debian Bug report #844714,
regarding zaqar: FTBFS: build-dependency not installable: python-autobahn (>= 
0.10.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.)


-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zaqar
Version: 3.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 53~), po-debconf, python-all, python-pbr (>= 1.8), 
> python-setuptools, python-sphinx, mongodb, python-autobahn (>= 0.10.1), 
> python-babel (>= 2.3.4), python-coverage, python-ddt (>= 1.0.1), 
> python-enum34, python-falcon, python-fixtures (>= 3.0.0), python-futurist (>= 
> 0.11.0), python-hacking (>= 0.10.0), python-iso8601 (>= 0.1.11), 
> python-jsonschema, python-keystoneclient (>= 1:1.6.0), 
> python-keystonemiddleware (>= 4.0.0), python-memcache (>= 1.56), python-mock 
> (>= 2.0), python-msgpack, python-openstackdocstheme (>= 1.5.0), 
> python-oslo.cache (>= 1.5.0), python-oslo.config (>= 1:3.14.0), 
> python-oslo.context (>= 2.9.0), python-oslo.i18n (>= 2.1.0), python-oslo.log 
> (>= 2.0.0), python-oslo.policy (>= 1.9.0), python-oslo.serialization (>= 
> 2.0.0), python-oslo.utils (>= 3.16.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-pymongo (>= 3.0.2), python-redis, 
> python-requests (>= 2.10.0), python-six (>= 1.9.0), python-sqlalchemy (>= 
> 1.0.10), python-stevedore (>= 1.16.0), python-tempest (>= 1:12.1.0), 
> python-testtools (>= 1.4.0), python-trollius, python-webob, python-websocket, 
> subunit, tempest (>= 1:12.1.0), testrepository
> Filtered Build-Depends: debhelper (>= 9), dh-python, dh-systemd, 
> openstack-pkg-tools (>= 53~), po-debconf, python-all, python-pbr (>= 1.8), 
> python-setuptools, python-sphinx, mongodb, python-autobahn (>= 0.10.1), 
> python-babel (>= 2.3.4), python-coverage, python-ddt (>= 1.0.1), 
> python-enum34, python-falcon, python-fixtures (>= 3.0.0), python-futurist (>= 
> 0.11.0), python-hacking (>= 0.10.0), python-iso8601 (>= 0.1.11), 
> python-jsonschema, python-keystoneclient (>= 1:1.6.0), 
> python-keystonemiddleware (>= 4.0.0), python-memcache (>= 1.56), python-mock 
> (>= 2.0), python-msgpack, python-openstackdocstheme (>= 1.5.0), 
> python-oslo.cache (>= 1.5.0), python-oslo.config (>= 1:3.14.0), 
> python-oslo.context (>= 2.9.0), python-oslo.i18n (>= 2.1.0), python-oslo.log 
> (>= 2.0.0), python-oslo.policy (>= 1.9.0), python-oslo.serialization (>= 
> 2.0.0), python-oslo.utils (>= 3.16.0), python-oslosphinx (>= 2.5.0), 
> python-oslotest (>= 1:1.10.0), python-pymongo (>= 3.0.2), python-redis, 
> python-requests (>= 2.10.0), python-six (>= 1.9.0), python-sqlalchemy (>= 
> 1.0.10), python-stevedore (>= 1.16.0), python-tempest (>= 1:12.1.0), 
> python-testtools (>= 1.4.0), python-trollius, python-webob, python-websocket, 
> subunit, tempest (>= 1:12.1.0), testrepository
> dpkg-deb: building package 'sbuild-build-depends-zaqar-dummy' in 
> '/<>/resolver-01x08j/apt_archive/sbuild-build-depends-zaqar-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-zaqar-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-01x08j/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-01x08j/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-01x08j/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-01x08j/apt_archive ./ Sources [771 B]
> Get:5 copy:/<>/resolver-01x08j/apt_archive ./ Packages [853 B]
> Fetched 2587 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 zaqar build dependencies (apt-based resolver)
> -
> 
> Installing 

Bug#844791: marked as done (openmeeg: FTBFS: build-dependency not installable: libvtk6-dev)

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 21:18:48 +
with message-id 
and subject line Bug#844714: fixed in pycparser 2.17-2
has caused the Debian Bug report #844714,
regarding openmeeg: FTBFS: build-dependency not installable: libvtk6-dev
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.)


-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openmeeg
Version: 2.3.0~20160502-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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.0.50~), cmake, doxygen, python-numpy, 
> swig | swig2.0, python-dev (>= 2.4), libatlas-base-dev, libvtk6-dev, 
> libtiff-dev | libtiff4-dev, libmatio-dev (>= 1.5)
> Filtered Build-Depends: debhelper (>= 7.0.50~), cmake, doxygen, python-numpy, 
> swig, python-dev (>= 2.4), libatlas-base-dev, libvtk6-dev, libtiff-dev, 
> libmatio-dev (>= 1.5)
> dpkg-deb: building package 'sbuild-build-depends-openmeeg-dummy' in 
> '/<>/resolver-cKsSN5/apt_archive/sbuild-build-depends-openmeeg-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-openmeeg-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-cKsSN5/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-cKsSN5/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-cKsSN5/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-cKsSN5/apt_archive ./ Sources [429 B]
> Get:5 copy:/<>/resolver-cKsSN5/apt_archive ./ Packages [507 B]
> Fetched 1893 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 openmeeg 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-openmeeg-dummy : Depends: libvtk6-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/openmeeg_2.3.0~20160502-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: pycparser
Source-Version: 2.17-2

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated pycparser 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: Sun, 20 Nov 2016 21:49:30 +0100
Source: pycparser
Binary: python-pycparser python3-pycparser
Architecture: source
Version: 2.17-2
Distribution: unstable
Urgency: medium
Maintainer: 

Bug#844832: marked as done (yade: FTBFS: build-dependency not installable: libvtk6-dev)

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 21:18:48 +
with message-id 
and subject line Bug#844714: fixed in pycparser 2.17-2
has caused the Debian Bug report #844714,
regarding yade: FTBFS: build-dependency not installable: libvtk6-dev
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.)


-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yade
Version: 2016.06a-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: cmake, debhelper (>= 9), freeglut3-dev, help2man, 
> ipython (>= 5), libboost-all-dev, libbz2-dev, libcgal-dev, libeigen3-dev (>= 
> 3.2.1-2), libgl1-mesa-dev, libgts-dev, libloki-dev, libmetis-dev, 
> libopenblas-dev, libqglviewer-dev-qt5, libsuitesparse-dev, libvtk6-dev, 
> libxi-dev, libxmu-dev, pyqt5-dev-tools, python-all-dev, python-gts, 
> python-imaging, python-matplotlib, python-minieigen, python-numpy, 
> python-sip, python-pyqt5, python-tk, python-xlib, zlib1g-dev, dvipng, 
> graphviz, libjs-jquery, lmodern, python-bibtex, python-sphinx, 
> texlive-fonts-recommended, texlive-generic-extra, texlive-latex-extra, 
> texlive-latex-recommended, texlive-pictures, texlive-xetex, tipa
> Filtered Build-Depends: cmake, debhelper (>= 9), freeglut3-dev, help2man, 
> ipython (>= 5), libboost-all-dev, libbz2-dev, libcgal-dev, libeigen3-dev (>= 
> 3.2.1-2), libgl1-mesa-dev, libgts-dev, libloki-dev, libmetis-dev, 
> libopenblas-dev, libqglviewer-dev-qt5, libsuitesparse-dev, libvtk6-dev, 
> libxi-dev, libxmu-dev, pyqt5-dev-tools, python-all-dev, python-gts, 
> python-imaging, python-matplotlib, python-minieigen, python-numpy, 
> python-sip, python-pyqt5, python-tk, python-xlib, zlib1g-dev, dvipng, 
> graphviz, libjs-jquery, lmodern, python-bibtex, python-sphinx, 
> texlive-fonts-recommended, texlive-generic-extra, texlive-latex-extra, 
> texlive-latex-recommended, texlive-pictures, texlive-xetex, tipa
> dpkg-deb: building package 'sbuild-build-depends-yade-dummy' in 
> '/<>/resolver-dm1LPf/apt_archive/sbuild-build-depends-yade-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-yade-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-dm1LPf/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-dm1LPf/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-dm1LPf/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-dm1LPf/apt_archive ./ Sources [645 B]
> Get:5 copy:/<>/resolver-dm1LPf/apt_archive ./ Packages [707 B]
> Fetched 2315 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 yade 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-yade-dummy : Depends: libvtk6-dev but it is not going 
> to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/yade_2016.06a-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: 

Bug#844714: marked as done (pycparser needs sourceful upload for new python-ply)

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 21:18:48 +
with message-id 
and subject line Bug#844714: fixed in pycparser 2.17-2
has caused the Debian Bug report #844714,
regarding pycparser needs sourceful upload for new python-ply
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.)


-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pycparser
Version: 2.17-1
Severity: grave
Justification: renders package unusable

Hi,

this package can't be installed:

The following packages have unmet dependencies:
 python-pycparser : Depends: python-ply-lex-3.5 but it is not
 installable
 Depends: python-ply-yacc-3.5 but it is not
 installable

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

Kernel: Linux 4.8.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)
--- End Message ---
--- Begin Message ---
Source: pycparser
Source-Version: 2.17-2

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated pycparser 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: Sun, 20 Nov 2016 21:49:30 +0100
Source: pycparser
Binary: python-pycparser python3-pycparser
Architecture: source
Version: 2.17-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Stefano Rivera 
Description:
 python-pycparser - C parser in Python
 python3-pycparser - C parser in Python 3
Closes: 844714
Changes:
 pycparser (2.17-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bumped debhelper compat level to 10
   * d/control: Removed pre-wheezy dependency version
 .
   [ Stefano Rivera ]
   * Build with python-ply 3.9 (Closes: #844714)
Checksums-Sha1:
 99ae45de9cfbb0cb48ef52d61edb8d462a2a8dda 1841 pycparser_2.17-2.dsc
 5d5a527b851f4e22554e8544f9cdccc0e0c9431c 4748 pycparser_2.17-2.debian.tar.xz
Checksums-Sha256:
 af19ff0df21924223d21eb2254688275b09e0fe7acb8e2965f9b647d2cb0f55a 1841 
pycparser_2.17-2.dsc
 7d38f968b362104969db88c0cfdab9cf6f7d67ffdfcf66f79f0a3e8e642ce729 4748 
pycparser_2.17-2.debian.tar.xz
Files:
 e24ace4f70150a1903c5001ff2887cb5 1841 python optional pycparser_2.17-2.dsc
 6d0bfc3f7c8edf31b47ed6315ac4e9c0 4748 python optional 
pycparser_2.17-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQExBAEBCgAbBQJYMg2gFBxzdGVmYW5vckBkZWJpYW4ub3JnAAoJEOrxkryqPw9R
dt0IAImSjNTyqrhfSUOAG0VDiBIPv7Lx79VoanZcs0MBlxc4UDlo9B5B2UTw8uIC
AHLotReyCtkT1epvsylLPJnc+MTe+c2VVffSnBqnhm71fsQKpVjXW1bVpit8dQmd
d7ywJq+lQaBt+hDetYqtwx6A8IzhbssMcJXi5iR+avpUom3bTmOM+PlW+OliVviB
qVI4FV3pRfCv96feRO0ZSRucIj/RpDZlZZrkTPuzQQbn33CLpZqanquBnguw5LMy
Hqv5ZcFIZvZ6tMT1t4n3iZvGGnSiQqrGKyu1FlQdoip7rLX+D9eIuy0qqBWgSQ1s
C9jEMQRI7+//75GqniuVtiXc5x0=
=Dnk5
-END PGP SIGNATURE End Message ---

Bug#844823: marked as done (swift-plugin-s3: FTBFS: build-dependency not installable: python-swift)

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 21:18:48 +
with message-id 
and subject line Bug#844714: fixed in pycparser 2.17-2
has caused the Debian Bug report #844714,
regarding swift-plugin-s3: FTBFS: build-dependency not installable: python-swift
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.)


-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swift-plugin-s3
Version: 1.11-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 (>= 9), dh-python, openstack-pkg-tools, 
> python-all, python-pbr, python-setuptools, python-sphinx, python-boto, 
> python-coverage, python-fixtures (>= 1.3.1), python-hacking (>= 0.11.0), 
> python-lxml, python-mock, python-nose, python-nose-exclude, 
> python-openstack.nose-plugin, python-openstackclient, python-requests (>= 
> 2.8.1), python-requests-mock (>= 0.7.0), python-six (>= 1.9.0), python-swift
> Filtered Build-Depends: debhelper (>= 9), dh-python, openstack-pkg-tools, 
> python-all, python-pbr, python-setuptools, python-sphinx, python-boto, 
> python-coverage, python-fixtures (>= 1.3.1), python-hacking (>= 0.11.0), 
> python-lxml, python-mock, python-nose, python-nose-exclude, 
> python-openstack.nose-plugin, python-openstackclient, python-requests (>= 
> 2.8.1), python-requests-mock (>= 0.7.0), python-six (>= 1.9.0), python-swift
> dpkg-deb: building package 'sbuild-build-depends-swift-plugin-s3-dummy' in 
> '/<>/resolver-o5XF5g/apt_archive/sbuild-build-depends-swift-plugin-s3-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-swift-plugin-s3-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-o5XF5g/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-o5XF5g/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-o5XF5g/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-o5XF5g/apt_archive ./ Sources [507 B]
> Get:5 copy:/<>/resolver-o5XF5g/apt_archive ./ Packages [589 B]
> Fetched 2059 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 swift-plugin-s3 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-swift-plugin-s3-dummy : Depends: python-swift but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/swift-plugin-s3_1.11-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: pycparser
Source-Version: 2.17-2

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

Debian 

Bug#844811: marked as done (therion: FTBFS: build-dependency not installable: libvtk6-dev)

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 21:18:48 +
with message-id 
and subject line Bug#844714: fixed in pycparser 2.17-2
has caused the Debian Bug report #844714,
regarding therion: FTBFS: build-dependency not installable: libvtk6-dev
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.)


-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: therion
Version: 5.3.16-10
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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: dpkg (>= 1.16.2), debhelper (>= 9), perl (>= 5.5), tcl, 
> libvtk6-dev, libwxgtk3.0-dev, libfreetype6-dev, libjpeg-dev, libpng-dev, 
> pkg-config, texlive-base, libproj-dev, therion, texlive-metapost, 
> imagemagick, ghostscript
> Filtered Build-Depends: dpkg (>= 1.16.2), debhelper (>= 9), perl (>= 5.5), 
> tcl, libvtk6-dev, libwxgtk3.0-dev, libfreetype6-dev, libjpeg-dev, libpng-dev, 
> pkg-config, texlive-base, libproj-dev, therion, texlive-metapost, 
> imagemagick, ghostscript
> dpkg-deb: building package 'sbuild-build-depends-therion-dummy' in 
> '/<>/resolver-wUIWtU/apt_archive/sbuild-build-depends-therion-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-therion-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-wUIWtU/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-wUIWtU/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-wUIWtU/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-wUIWtU/apt_archive ./ Sources [457 B]
> Get:5 copy:/<>/resolver-wUIWtU/apt_archive ./ Packages [536 B]
> Fetched 1950 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 therion 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-therion-dummy : Depends: libvtk6-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/therion_5.3.16-10_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: pycparser
Source-Version: 2.17-2

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated pycparser 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: Sun, 20 Nov 2016 21:49:30 +0100
Source: pycparser
Binary: python-pycparser 

Bug#844827: marked as done (swift: FTBFS: build-dependency not installable: python-xattr (>= 0.4))

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 21:18:48 +
with message-id 
and subject line Bug#844714: fixed in pycparser 2.17-2
has caused the Debian Bug report #844714,
regarding swift: FTBFS: build-dependency not installable: python-xattr (>= 0.4)
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.)


-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swift
Version: 2.10.0-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 (>= 9), dh-exec, dh-python, dh-systemd, 
> openstack-pkg-tools (>= 48~), python-all, python-pbr, python-setuptools (>= 
> 20.6.8), python-sphinx, python-coverage, python-cryptography (>= 1.0), 
> python-dnspython (>= 1.14.0), python-eventlet (>= 0.17.4), python-greenlet 
> (>= 0.3.1), python-keystoneclient (>= 1:1.3.0), python-mock, python-netifaces 
> (>> 0.10.1), python-nose, python-nose-exclude, python-nosehtmloutput, 
> python-nosexcover, python-openssl, python-openstack.nose-plugin, 
> python-openstackdocstheme (>= 1.0.3), python-os-api-ref, python-os-testr (>= 
> 0.4.1), python-oslosphinx, python-pastedeploy (>= 1.3.3), python-pyeclib (>= 
> 1.2.0), python-six (>= 1.9.0), python-swiftclient, python-xattr (>= 0.4)
> Filtered Build-Depends: debhelper (>= 9), dh-exec, dh-python, dh-systemd, 
> openstack-pkg-tools (>= 48~), python-all, python-pbr, python-setuptools (>= 
> 20.6.8), python-sphinx, python-coverage, python-cryptography (>= 1.0), 
> python-dnspython (>= 1.14.0), python-eventlet (>= 0.17.4), python-greenlet 
> (>= 0.3.1), python-keystoneclient (>= 1:1.3.0), python-mock, python-netifaces 
> (>> 0.10.1), python-nose, python-nose-exclude, python-nosehtmloutput, 
> python-nosexcover, python-openssl, python-openstack.nose-plugin, 
> python-openstackdocstheme (>= 1.0.3), python-os-api-ref, python-os-testr (>= 
> 0.4.1), python-oslosphinx, python-pastedeploy (>= 1.3.3), python-pyeclib (>= 
> 1.2.0), python-six (>= 1.9.0), python-swiftclient, python-xattr (>= 0.4)
> dpkg-deb: building package 'sbuild-build-depends-swift-dummy' in 
> '/<>/resolver-Rc7xQs/apt_archive/sbuild-build-depends-swift-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-swift-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Rc7xQs/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Rc7xQs/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-Rc7xQs/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-Rc7xQs/apt_archive ./ Sources [622 B]
> Get:5 copy:/<>/resolver-Rc7xQs/apt_archive ./ Packages [702 B]
> Fetched 2287 B in 0s (203 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install swift 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-swift-dummy : Depends: python-xattr (>= 0.4) but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/swift_2.10.0-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

Bug#844814: marked as done (swauth: FTBFS: build-dependency not installable: swift-proxy (>= 2.2.0))

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 21:18:48 +
with message-id 
and subject line Bug#844714: fixed in pycparser 2.17-2
has caused the Debian Bug report #844714,
regarding swauth: FTBFS: build-dependency not installable: swift-proxy (>= 
2.2.0)
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.)


-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: swauth
Version: 1.2.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 (>= 9), dh-python, openstack-pkg-tools (>= 
> 48~), python-all, python-pbr, python-setuptools, python-sphinx, 
> python-eventlet (>= 0.18.4), python-mock, python-nose, swift-proxy (>= 
> 2.2.0), python-swiftclient, python-six (>= 1.9.0)
> Filtered Build-Depends: debhelper (>= 9), dh-python, openstack-pkg-tools (>= 
> 48~), python-all, python-pbr, python-setuptools, python-sphinx, 
> python-eventlet (>= 0.18.4), python-mock, python-nose, swift-proxy (>= 
> 2.2.0), python-swiftclient, python-six (>= 1.9.0)
> dpkg-deb: building package 'sbuild-build-depends-swauth-dummy' in 
> '/<>/resolver-JtOzb2/apt_archive/sbuild-build-depends-swauth-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-swauth-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-JtOzb2/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-JtOzb2/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-JtOzb2/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-JtOzb2/apt_archive ./ Sources [456 B]
> Get:5 copy:/<>/resolver-JtOzb2/apt_archive ./ Packages [536 B]
> Fetched 1949 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 swauth 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-swauth-dummy : Depends: swift-proxy (>= 2.2.0) but it 
> is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/swauth_1.2.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: pycparser
Source-Version: 2.17-2

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated pycparser 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: Sun, 20 Nov 2016 21:49:30 +0100

Bug#844840: marked as done (python-autobahn: FTBFS: unsatisfiable build-dependencies: python-nacl, python3-nacl)

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 21:18:48 +
with message-id 
and subject line Bug#844714: fixed in pycparser 2.17-2
has caused the Debian Bug report #844714,
regarding python-autobahn: FTBFS: unsatisfiable build-dependencies: 
python-nacl, python3-nacl
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.)


-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-autobahn
Version: 0.14.1+dfsg1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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 (>= 9), dh-python, python-all, 
> python-setuptools, python-sphinx, python3-all, python3-setuptools, 
> python-cbor, python-concurrent.futures (>= 2.1.5), python-enchant, python-lz4 
> (>= 0.2.1), python-mock (>= 1.3), python-msgpack (>= 0.4.0), python-nacl, 
> python-pytest (>= 2.6), python-qrcode, python-six, python-snappy (>= 0.5), 
> python-sphinx-rtd-theme, python-sphinxcontrib.spelling, python-trollius (>= 
> 2.0), python-twisted (>= 11.1), python-txaio (>= 2.5.1), python-unittest2 (>= 
> 1.1.0), python-zope.interface (>= 3.6), python3-cbor, python3-enchant, 
> python3-lz4 (>= 0.2.1), python3-mock (>= 1.3), python3-msgpack (>= 0.4.0), 
> python3-nacl, python3-pytest (>= 2.6.4), python3-six, python3-snappy (>= 
> 0.5), python3-twisted (>= 11.1), python3-txaio (>= 2.5.1), python3-unittest2 
> (>= 1.1.0), python3-zope.interface (>= 3.6)
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-setuptools, python-sphinx, python3-all, python3-setuptools, 
> python-cbor, python-concurrent.futures (>= 2.1.5), python-enchant, python-lz4 
> (>= 0.2.1), python-mock (>= 1.3), python-msgpack (>= 0.4.0), python-nacl, 
> python-pytest (>= 2.6), python-qrcode, python-six, python-snappy (>= 0.5), 
> python-sphinx-rtd-theme, python-sphinxcontrib.spelling, python-trollius (>= 
> 2.0), python-twisted (>= 11.1), python-txaio (>= 2.5.1), python-unittest2 (>= 
> 1.1.0), python-zope.interface (>= 3.6), python3-cbor, python3-enchant, 
> python3-lz4 (>= 0.2.1), python3-mock (>= 1.3), python3-msgpack (>= 0.4.0), 
> python3-nacl, python3-pytest (>= 2.6.4), python3-six, python3-snappy (>= 
> 0.5), python3-twisted (>= 11.1), python3-txaio (>= 2.5.1), python3-unittest2 
> (>= 1.1.0), python3-zope.interface (>= 3.6)
> dpkg-deb: building package 'sbuild-build-depends-python-autobahn-dummy' in 
> '/<>/resolver-0Z7JHe/apt_archive/sbuild-build-depends-python-autobahn-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-python-autobahn-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-0Z7JHe/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-0Z7JHe/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-0Z7JHe/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-0Z7JHe/apt_archive ./ Sources [605 B]
> Get:5 copy:/<>/resolver-0Z7JHe/apt_archive ./ Packages [686 B]
> Fetched 2254 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 python-autobahn 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-python-autobahn-dummy : Depends: python-nacl but it is 
> not going to be installed
>   Depends: python3-nacl but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken 

Bug#844808: marked as done (nifti2dicom: FTBFS: build-dependency not installable: libvtk6-qt-dev)

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 21:18:48 +
with message-id 
and subject line Bug#844714: fixed in pycparser 2.17-2
has caused the Debian Bug report #844714,
regarding nifti2dicom: FTBFS: build-dependency not installable: libvtk6-qt-dev
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.)


-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nifti2dicom
Version: 0.4.11-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 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.3.16), cdbs, cmake (>= 2.6.4), 
> qtbase5-dev | libqt4-dev (>= 4.4), libinsighttoolkit4-dev (>= 4.3.0) | 
> libinsighttoolkit3-dev, libfftw3-dev, libtclap-dev (>= 1.2.0), libvtk6-qt-dev 
> | libvtk6-dev (<< 6.2) | libvtk5-qt4-dev
> Filtered Build-Depends: debhelper (>= 7.3.16), cdbs, cmake (>= 2.6.4), 
> qtbase5-dev, libinsighttoolkit4-dev (>= 4.3.0), libfftw3-dev, libtclap-dev 
> (>= 1.2.0), libvtk6-qt-dev
> dpkg-deb: building package 'sbuild-build-depends-nifti2dicom-dummy' in 
> '/<>/resolver-T3mUdd/apt_archive/sbuild-build-depends-nifti2dicom-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-nifti2dicom-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-T3mUdd/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-T3mUdd/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/resolver-T3mUdd/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-T3mUdd/apt_archive ./ Sources [457 B]
> Get:5 copy:/<>/resolver-T3mUdd/apt_archive ./ Packages [509 B]
> Fetched 1923 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 nifti2dicom 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-nifti2dicom-dummy : Depends: libvtk6-qt-dev but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/nifti2dicom_0.4.11-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: pycparser
Source-Version: 2.17-2

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated pycparser 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: Sun, 20 Nov 2016 21:49:30 +0100
Source: pycparser
Binary: python-pycparser python3-pycparser

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Stepan Golosunov]

20.11.2016 в 21:29:35 +0100 Jan Niehusmann написал:
> On Mon, Nov 21, 2016 at 12:02:45AM +0400, Stepan Golosunov wrote:
> > It would be a grave bug in such application if it does not have a
> > working version, yes.  Whether or not it would be a serious bug in
> > lubcurl3 depends on how many and how important such applications are.
> > (And how difficult they are to fix.)
> 
> As there are applications which depend on libcurl and qt, and it seems
> like qt can't be ported to openssl 1.1 in time for stretch, fixing such
> applications would mean uploading a version of curl linked to openssl
> 1.0. This could be a new package, or a statically linked version etc. -
> IMHO all worse than just linking the curl package with openssl 1.0 until
> (close to) all packages are ready for a transition to openssl 1.1.

So far I do not know why using libssl1.1 together with a
libssl1.0.2-using Qt wouldn't work.  So far I can imagine the
following reasons:

1. Application relies on Qt initializing the library.  That was the
cause of breakage during libssl1.0.0 -> libssl1.0.2 transition, but
is not applicable now as libssl1.1 does not require explicit
initialization.

2. Application passes OpenSSL objects from libssl1.1 to Qt (or vice
versa).  Why one would do it?

3. dlsym(3) is used with RTLD_DEFAULT or RTLD_NEXT.  Does not seem to
be the case.

4. dlsym(3) finds wrong library.  Manual page suggests that should not
be the case.

…

Is any of the above applicable?

Bug#843898: Something to try

[Tobias Hansen]

On 11/20/2016 08:29 PM, Sebastian P. Luque wrote:
> On Sun, 20 Nov 2016 19:17:49 +,
> Tobias Hansen  wrote:
> 
>> If you google this you see that tons of people have similar issues:
>> https://github.com/ipython/ipython/issues/9656
>> https://github.com/ipython/ipython/issues/9815
>> https://github.com/chrippa/backports.shutil_get_terminal_size/issues/9
> 
>> The most common "solution" there is reinstalling something with
>> pip. My suspicion is that the people who see this on Debian also used
>> pip and there is something interfering. Did you guys use pip (or
>> something else to install Python modules not from Debian) and have a
>> backports module or backports.shutil_get_terminal_size itself
>> installed there?
> 
> I do use pip within virtual environments, but these shouldn't interfere.
> 
> First, as per Julien's request, here's my output:
> 
> $ python
> Python 2.7.12+ (default, Sep  1 2016, 20:27:38) 
> [GCC 6.2.0 20160927] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
 from  backports.shutil_get_terminal_size import get_terminal_size
> Traceback (most recent call last):
>   File "", line 1, in 
> ImportError: No module named shutil_get_terminal_size
> 
> When using pip within virtual environments, packages/modules get
> installed in ~/.local/lib/python2.7 in my case.  There I see one
> potentially interfering backports module, which shows these contents:
> 
> $ ls -alh ~/.local/lib/python2.7/site-packages/backports/
> total 12K
> drwxr-xr-x  3 sluque sluque 4.0K Oct 30 16:16 .
> drwx-- 20 sluque sluque 4.0K Oct 30 16:18 ..
> drwxr-xr-x  2 sluque sluque 4.0K Oct 30 16:16 configparser
> 
> 

What happens if you rename that for a moment? Does it fix the problem?

Bug#844796: gnome-shell: FTBFS: /<>/src/tmp-introspect2qs0g0tu/.libs/ShellMenu-0.1: error while loading shared libraries: libmutter-clutter-1.0.so: cannot open shared object file: No such

[Emilio Pozuelo Monfort]

On 20/11/16 14:08, Michael Biebl wrote:
> Am 20.11.2016 um 08:31 schrieb Lucas Nussbaum:
>> Hi,
>>
>> On 20/11/16 at 01:33 +0100, Michael Biebl wrote:
>>> Builds fine in a stretch chroot.
>>
>> Have you tried in a sid chroot? I just tried and can still reproduce it.
>> (but I did not manage to further isolate the problem)
> 
> My point that something unrelated to gnome-shell has changed which now
> causes it to FTBFS.

Seems to be the new gcc-6. Not sure whether this is a bug in gcc or if
gnome-shell is doing something wrong with rpath and -L flags for
libmutter-clutter-1.0.so.

Emilio

Processed: Bug#844714 marked as pending

[Debian Bug Tracking System]

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

> tag 844714 pending
Bug #844714 [python-pycparser] pycparser needs sourceful upload for new 
python-ply
Bug #844791 [python-pycparser] openmeeg: FTBFS: build-dependency not 
installable: libvtk6-dev
Bug #844794 [python-pycparser] zaqar: FTBFS: build-dependency not installable: 
python-autobahn (>= 0.10.1)
Bug #844808 [python-pycparser] nifti2dicom: FTBFS: build-dependency not 
installable: libvtk6-qt-dev
Bug #844811 [python-pycparser] therion: FTBFS: build-dependency not 
installable: libvtk6-dev
Bug #844814 [python-pycparser] swauth: FTBFS: build-dependency not installable: 
swift-proxy (>= 2.2.0)
Bug #844823 [python-pycparser] swift-plugin-s3: FTBFS: build-dependency not 
installable: python-swift
Bug #844827 [python-pycparser] swift: FTBFS: build-dependency not installable: 
python-xattr (>= 0.4)
Bug #844832 [python-pycparser] yade: FTBFS: build-dependency not installable: 
libvtk6-dev
Bug #844840 [python-pycparser] python-autobahn: FTBFS: unsatisfiable 
build-dependencies: python-nacl, python3-nacl
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
844714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844714
844791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844791
844794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844794
844808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844808
844811: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844811
844814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844814
844823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844823
844827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844827
844832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844832
844840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#844714: marked as pending

[Stefano Rivera]

tag 844714 pending
thanks

Hello,

Bug #844714 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=python-modules/packages/pycparser.git;a=commitdiff;h=96eddb4

---
commit 96eddb45e02cc0b13ea677d7544ddd43ef4630c8
Author: Stefano Rivera 
Date:   Sun Nov 20 21:51:19 2016 +0100

Build with python-ply 3.9 (Closes: #844714)

diff --git a/debian/changelog b/debian/changelog
index cc8650c..b3978c6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,13 @@
-pycparser (2.17-2) UNRELEASED; urgency=medium
+pycparser (2.17-2) unstable; urgency=medium
 
+  [ Ondřej Nový ]
   * Bumped debhelper compat level to 10
   * d/control: Removed pre-wheezy dependency version
 
- -- Ondřej Nový   Sat, 19 Nov 2016 12:24:45 +0100
+  [ Stefano Rivera ]
+  * Build with python-ply 3.9 (Closes: #844714)
+
+ -- Stefano Rivera   Sun, 20 Nov 2016 21:49:30 +0100
 
 pycparser (2.17-1) unstable; urgency=medium
 

Bug#845152: systemd-docker FTBFS in stretch due to missing golang-github-docker-docker-dev

[Adrian Bunk]

Source: systemd-docker
Version: 0.2.1+dfsg-2
Severity: serious
Tags: stretch
Control: block -1 by 832103 835686 842806 843530

systemd-docker build-depends on golang-github-docker-docker-dev,
which is not in stretch due to #832103, #835686, #842806, #843530

Processed: systemd-docker FTBFS in stretch due to missing golang-github-docker-docker-dev

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 832103 835686 842806 843530
Bug #845152 [src:systemd-docker] systemd-docker FTBFS in stretch due to missing 
golang-github-docker-docker-dev
845152 was not blocked by any bugs.
845152 was not blocking any bugs.
Added blocking bug(s) of 845152: 842806, 832103, 835686, and 843530

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

Processed: nomad FTBFS in stretch due to missing golang-github-docker-docker-dev

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 832103 835686 842806 843530
Bug #845151 [src:nomad] nomad FTBFS in stretch due to missing 
golang-github-docker-docker-dev
845151 was not blocked by any bugs.
845151 was not blocking any bugs.
Added blocking bug(s) of 845151: 842806, 835686, 843530, and 832103

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

Bug#845151: nomad FTBFS in stretch due to missing golang-github-docker-docker-dev

[Adrian Bunk]

Source: nomad
Version: 0.4.0+dfsg-1
Severity: serious
Tags: stretch
Control: block -1 by 832103 835686 842806 843530

nomad build-depends on golang-github-docker-docker-dev,
which is not in stretch due to #832103, #835686, #842806, #843530

Processed: containerd FTBFS in stretch due to missing golang-github-docker-docker-dev

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 832103 835686 842806 843530
Bug #845149 [src:containerd] containerd FTBFS in stretch due to missing 
golang-github-docker-docker-dev
845149 was not blocked by any bugs.
845149 was not blocking any bugs.
Added blocking bug(s) of 845149: 843530, 835686, 842806, and 832103

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

Processed: gitlab-ci-multi-runner FTBFS in stretch due to missing golang-github-docker-docker-dev

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 832103 835686 842806 843530
Bug #845150 [src:gitlab-ci-multi-runner] gitlab-ci-multi-runner FTBFS in 
stretch due to missing golang-github-docker-docker-dev
845150 was not blocked by any bugs.
845150 was not blocking any bugs.
Added blocking bug(s) of 845150: 843530, 842806, 835686, and 832103

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

Bug#845149: containerd FTBFS in stretch due to missing golang-github-docker-docker-dev

[Adrian Bunk]

Source: containerd
Version: 0.2.1~ds1-3
Severity: serious
Tags: stretch
Control: block -1 by 832103 835686 842806 843530

containerd build-depends on golang-github-docker-docker-dev,
which is not in stretch due to #832103, #835686, #842806, #843530

Bug#845150: gitlab-ci-multi-runner FTBFS in stretch due to missing golang-github-docker-docker-dev

[Adrian Bunk]

Source: gitlab-ci-multi-runner
Version: 1.7.1+dfsg-2
Severity: serious
Tags: stretch
Control: block -1 by 832103 835686 842806 843530

gitlab-ci-multi-runner build-depends on golang-github-docker-docker-dev,
which is not in stretch due to #832103, #835686, #842806, #843530

Bug#845148: consul FTBFS in stretch due to missing golang-github-fsouza-go-dockerclient-dev

[Adrian Bunk]

Source: consul
Version: 0.6.4~dfsg-3
Severity: serious
Tags: stretch
Control: block -1 by 832103 835686 842806 843530

consul build-depends on golang-github-fsouza-go-dockerclient-dev,
which is not in stretch due to #832103, #835686, #842806, #843530

Processed: consul FTBFS in stretch due to missing golang-github-fsouza-go-dockerclient-dev

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 832103 835686 842806 843530
Bug #845148 [src:consul] consul FTBFS in stretch due to missing 
golang-github-fsouza-go-dockerclient-dev
845148 was not blocked by any bugs.
845148 was not blocking any bugs.
Added blocking bug(s) of 845148: 843530, 835686, 832103, and 842806

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

Bug#845147: golang-github-appc-docker2aci FTBFS on i386 and arm*: error calling MarshalJSON for type types.Labels: bad arch

[Adrian Bunk]

Source: golang-github-appc-docker2aci
Version: 0.14.0+dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=golang-github-appc-docker2aci

...
--- FAIL: TestFetchingMultipleLayersV22 (0.00s)
server.go:16: path requested: /v2/
server.go:16: path requested: 
/v2/docker2aci/dockerv22test/manifests/v0.1.0
server.go:16: path requested: 
/v2/docker2aci/dockerv22test/blobs/sha256:06ed250f2530f71b93917021a4ab8ad00dc794cdb3d38624ccc76cb396bc797d
server.go:16: path requested: 
/v2/docker2aci/dockerv22test/blobs/sha256:228b9a6eb6a46656e31afc554598f366258faed297af6ee9bc1a3837f602e6e4
server.go:16: path requested: 
/v2/docker2aci/dockerv22test/blobs/sha256:d55b253d87d1338c84d70093dddafdd4761c36e49389fef217e5557d8b16bce8
v22_test.go:354: error generating ACI: error writing manifest: json: 
error calling MarshalJSON for type schema.ImageManifest: json: error calling 
MarshalJSON for type types.Labels: bad arch "386" for linux (must be one of: 
[amd64 i386 aarch64 aarch64_be armv6l armv7l armv7b ppc64 ppc64le s390x])
FAIL
exit status 1
FAILgithub.com/appc/docker2aci/lib/tests0.033s
?   github.com/appc/docker2aci/pkg/log  [no test files]
dh_auto_test: go test -v -p 1 github.com/appc/docker2aci 
github.com/appc/docker2aci/lib github.com/appc/docker2aci/lib/common 
github.com/appc/docker2aci/lib/internal 
github.com/appc/docker2aci/lib/internal/backend/file 
github.com/appc/docker2aci/lib/internal/backend/repository 
github.com/appc/docker2aci/lib/internal/docker 
github.com/appc/docker2aci/lib/internal/tarball 
github.com/appc/docker2aci/lib/internal/types 
github.com/appc/docker2aci/lib/internal/typesV2 
github.com/appc/docker2aci/lib/internal/util 
github.com/appc/docker2aci/lib/tests github.com/appc/docker2aci/pkg/log 
returned exit code 1
debian/rules:4: recipe for target 'build-arch' failed
make: *** [build-arch] Error 1
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

Bug#844239: [request-tracker-maintainers] Bug#844239: request-tracker4: FTBFS: t/web/gnupg-select-keys-on-update.t failure

[Niko Tyni]

On Sun, Nov 13, 2016 at 07:13:54PM +0200, Niko Tyni wrote:
> Package: request-tracker4
> Version: 4.2.13-3
> Severity: serious
> 
> This package failed to build on the 'all' buildd:
> 
>   
> https://buildd.debian.org/status/fetch.php?pkg=request-tracker4=all=4.2.13-3=1477439960
> 
>   #   Failed test 'problems with passphrase'
>   #   at t/web/gnupg-select-keys-on-update.t line 40.
>   # searched: "\x{0a}\x{0a}\x{0a}  
> \x{0a}   #   can't find: "unable to sign outgoing email messages"
>   # LCSS: " message"
>   # LCSS context: "

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Jan Niehusmann]

On Mon, Nov 21, 2016 at 12:02:45AM +0400, Stepan Golosunov wrote:
> It would be a grave bug in such application if it does not have a
> working version, yes.  Whether or not it would be a serious bug in
> lubcurl3 depends on how many and how important such applications are.
> (And how difficult they are to fix.)

As there are applications which depend on libcurl and qt, and it seems
like qt can't be ported to openssl 1.1 in time for stretch, fixing such
applications would mean uploading a version of curl linked to openssl
1.0. This could be a new package, or a statically linked version etc. -
IMHO all worse than just linking the curl package with openssl 1.0 until
(close to) all packages are ready for a transition to openssl 1.1.

Jan

Processed: pike8.0: build-depends on heimdal-dev, which is to be removed from testing

[Debian Bug Tracking System]

Processing control commands:

> block 837728 with -1
Bug #837728 [release.debian.org] RM: heimdal/1.7~git20150920+dfsg-4
837728 was blocked by: 837628 806264 837716 836885 837724
837728 was not blocking any bugs.
Added blocking bug(s) of 837728: 845146

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

Bug#843898: Something to try

[Sebastian P . Luque]

On Sun, 20 Nov 2016 19:17:49 +,
Tobias Hansen  wrote:

> If you google this you see that tons of people have similar issues:
> https://github.com/ipython/ipython/issues/9656
> https://github.com/ipython/ipython/issues/9815
> https://github.com/chrippa/backports.shutil_get_terminal_size/issues/9

> The most common "solution" there is reinstalling something with
> pip. My suspicion is that the people who see this on Debian also used
> pip and there is something interfering. Did you guys use pip (or
> something else to install Python modules not from Debian) and have a
> backports module or backports.shutil_get_terminal_size itself
> installed there?

I do use pip within virtual environments, but these shouldn't interfere.

First, as per Julien's request, here's my output:

$ python
Python 2.7.12+ (default, Sep  1 2016, 20:27:38) 
[GCC 6.2.0 20160927] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from  backports.shutil_get_terminal_size import get_terminal_size
Traceback (most recent call last):
  File "", line 1, in 
ImportError: No module named shutil_get_terminal_size

When using pip within virtual environments, packages/modules get
installed in ~/.local/lib/python2.7 in my case.  There I see one
potentially interfering backports module, which shows these contents:

$ ls -alh ~/.local/lib/python2.7/site-packages/backports/
total 12K
drwxr-xr-x  3 sluque sluque 4.0K Oct 30 16:16 .
drwx-- 20 sluque sluque 4.0K Oct 30 16:18 ..
drwxr-xr-x  2 sluque sluque 4.0K Oct 30 16:16 configparser


-- 
Seb

Bug#845146: pike8.0: build-depends on heimdal-dev, which is to be removed from testing

[Emilio Pozuelo Monfort]

Source: pike8.0
Version: 8.0.276-1
Severity: serious
Control: block 837728 with -1

Hi,

Your package build-depends on heimdal-dev, but heimdal is going to be
removed from testing (and possibly from the archive). See bugs
#837728 and #834654 for the reasoning.

You should stop build-depending on heimdal-dev. Possibly switching to
MIT Kerberos is an option.

Cheers,
Emilio

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

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

Processed: Re: Bug#836597: lightspark: FTBFS on powerpc: segmentation fault during configure

[Debian Bug Tracking System]

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

> severity 836597 important
Bug #836597 [src:lightspark] lightspark: FTBFS on powerpc: segmentation fault 
during configure
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#844701: dpkg: buggy dpkg 1.8.11 and above ? Package: dpkg

[shirish शिरीष]

at bottom :-

On 20/11/2016, Guillem Jover  wrote:
> Control: retitle -1 dpkg-maintscript-helper: Version comparison fails for
> supposedly valid versions
> Control: severity -1 serious
>
> Hi!
>
> On Fri, 2016-11-18 at 14:02:39 +0530, shirish शिरीष wrote:
>> Package: dpkg
>> Version: 1.18.14
>> Severity: normal
>
>> It seems the bug is in dpkg 1.18.11 and above. I was suffering from
>> some sort of broken packages. I shared my issue at
>> http://unix.stackexchange.com/questions/323817/debian-strech-update-broken-seems-buggy-dpkg
>> . It took quite some time but it seems that dpkg at least 1.18.14 is
>> somewhat broken/buggy in its implementation. In dpkg 1.18.10 I am able
>> to fix the broken packages. These happened a few more times. I did run
>> a few checks
>> http://unix.stackexchange.com/questions/324151/how-to-find-out-half-configured-broken-packages-in-debian
>> but found nothing untoward.
>
> Please include your reports inline, instead of referencing outside
> resources, because this means those details might disappear (in the
> future) in case those sites are shutdown, or it requires maintainers
> to be online to check them.
>
> Ok, so this is about the dpkg-maintscript-helper failing on the
> version validation check for supposedly valid versions. This was
> recently reported on IRC too, but we were unable to reproduce it. If
> you can still reproduce it, I'd appreciate if you could apply the
> attached patch to your installed dpkg-maintscript-helper script
> (from a dpkg version > 1.18.11) and rerun the failing package.
>
> Oh, I think I know what's wrong now, the attached patch should in
> principle fix that.
>
> Thanks,
> Guillem
>


Dear Guillem,

The patch didn't work :(

First let me share the changes file that got generated, maybe the
rebuild I did was wrong - please check -

┌─[shirish@debian] - [~/games] - [5845]
└─[$] cat dpkg_1.18.15+nmu1_amd64.changes

[1:44:47]
Format: 1.8
Date: Mon, 21 Nov 2016 01:04:02 +0530
Source: dpkg
Binary: dpkg libdpkg-dev dpkg-dev libdpkg-perl dselect
Architecture: source amd64 all
Version: 1.18.15+nmu1
Distribution: UNRELEASED
Urgency: medium
Maintainer: Dpkg Developers 
Changed-By: shirish 
Description:
 dpkg   - Debian package management system
 dpkg-dev   - Debian package development tools
 dselect- Debian package management front-end
 libdpkg-dev - Debian package management static library
 libdpkg-perl - Dpkg perl modules
Changes:
 dpkg (1.18.15+nmu1) UNRELEASED; urgency=medium
 .
   * Non-maintainer upload.
   * Apply d-m-h fix from #844701
Checksums-Sha1:
 8e50f097f70d621071e1e22384c1d68da7693929 1169 dpkg_1.18.15+nmu1.dsc
 16aa8483b0ce8d9eb1f0daebca6da84578226966 4617028 dpkg_1.18.15+nmu1.tar.xz
 3f3eae9de5bb31e178a4acb32654e68410902bda 1238392
dpkg-dbgsym_1.18.15+nmu1_amd64.deb
 3877d627c7c70bd98f16ee0b71d80c69667a6885 1581332 dpkg-dev_1.18.15+nmu1_all.deb
 b678906567a0c8ba089a5eb109855eba608f60e7 2067816 dpkg_1.18.15+nmu1_amd64.deb
 6130872887cd4eeba0b0cc0d0c7354322709dfe7 280736
dselect-dbgsym_1.18.15+nmu1_amd64.deb
 58eb460ab48e1c802ee7ae439dc0295424ef7742 1270868 dselect_1.18.15+nmu1_amd64.deb
 41e17c39ced6f55b9e72d042255a7a9b647b2e8e 1040980
libdpkg-dev_1.18.15+nmu1_amd64.deb
 a38005cde488603a7ee5de9ce7bc307c79277bb9 1242182
libdpkg-perl_1.18.15+nmu1_all.deb
Checksums-Sha256:
 2c8cf8ab1256814aa7115009a4620da913b27935351872335cd429ae4e7a9c70 1169
dpkg_1.18.15+nmu1.dsc
 47390a1ca4a296852ef3c25c0bdc82217e49738438882a980e8da28dca0d809e
4617028 dpkg_1.18.15+nmu1.tar.xz
 4a47a968b5dd4b1e87c99e5de9e3fd31b610ebb1891989de3a72ef08afb3405b
1238392 dpkg-dbgsym_1.18.15+nmu1_amd64.deb
 a05ae6dcefd5bc9affe355c8dd4106b42f795678fa4de31bc063a9784fc845ab
1581332 dpkg-dev_1.18.15+nmu1_all.deb
 b9682da9975541f385b47cf1148028deea4a48a51156293589b124c6f706d7b7
2067816 dpkg_1.18.15+nmu1_amd64.deb
 d75479bb9005788d96e839ae8b2dde56701993ac6421df1f5aaf79634f008a48
280736 dselect-dbgsym_1.18.15+nmu1_amd64.deb
 8b317f45808d408485c566b9748522d63d556bcec7525dcaa442a9720073dd27
1270868 dselect_1.18.15+nmu1_amd64.deb
 e45e67c3ab034ed3d1bf9f268daba92ee3cc406c3b75ef2bd0354ec79dc30d7f
1040980 libdpkg-dev_1.18.15+nmu1_amd64.deb
 d75ff545c612a7eb5f4563bb3619cd33ea4d4baff6cade9452e94bb1e7b7a412
1242182 libdpkg-perl_1.18.15+nmu1_all.deb
Files:
 faab0ae6b71c8216a634cbef6759d122 1169 admin required dpkg_1.18.15+nmu1.dsc
 69eeaa680e11f291860217a9536e93dc 4617028 admin required
dpkg_1.18.15+nmu1.tar.xz
 91961eae15e20a3bf2ad614cf42ee4ab 1238392 debug extra
dpkg-dbgsym_1.18.15+nmu1_amd64.deb
 aa361b4cde6020393c75a601c51f54e6 1581332 utils optional
dpkg-dev_1.18.15+nmu1_all.deb
 325a9629e03781c027f884a17ada0550 2067816 admin required
dpkg_1.18.15+nmu1_amd64.deb
 75dbcd90ada67522d79206b65519865e 280736 debug extra
dselect-dbgsym_1.18.15+nmu1_amd64.deb
 e490b38b2b132c26670635628e302941 1270868 admin optional
dselect_1.18.15+nmu1_amd64.deb
 0d206c14b1ffd5cb6b09608e9774b3bf 1040980 libdevel optional

Bug#836597: lightspark: FTBFS on powerpc: segmentation fault during configure

[Emilio Pozuelo Monfort]

Control: tags -1 important

On 20/11/16 13:58, Andrey Rahmatullin wrote:
> Control: tags -1 + unreproducible
> 
> On Sun, Sep 04, 2016 at 01:56:41PM +0200, Emilio Pozuelo Monfort wrote:
>> Source: lightspark
>> Version: 0.7.2+git20150512-2.1
>> Severity: serious
>>
>> Your package fails to build on powerpc:
>>
>> -- Found assembler: /usr/bin/nasm
>> -- LLVM llvm-config found at: /usr/bin/llvm-config
>> -- LLVM version: 3.6.2
>> Segmentation fault
>>
>> Logs at:
>>
>> https://buildd.debian.org/status/logs.php?pkg=lightspark=0.7.2%2Bgit20150512-2.1%2Bb3=powerpc
>>
>> Emilio
> This doesn't happen on partch. We'll see after uploading a version that
> fixes FTBFS on other architectures.

OK. Anyway, downgrading as powerpc is no longer a release architecture.

Cheers,
Emilio

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Stepan Golosunov]

20.11.2016 в 20:01:25 +0100 Jan Niehusmann написал:
> On Sun, Nov 20, 2016 at 07:40:22PM +0400, Stepan Golosunov wrote:
> > If SONAME change is needed it is needed when linking libcurl with
> > libssl1.0.2 too.  (But when linking libcurl with libssl1.0.2 more
> > applications are affected due to the need of explicit initialization.)
> 
> Upstream documentation suggests that this is not true:
> 
> "Minor releases that change the last digit, e.g. 1.0.1 vs. 1.0.2, can
> and are likely to contain new features, but in a way that does not break
> binary compatibility. This means that an application compiled and
> dynamically linked with 1.0.0 does not need to be recompiled when the
> shared library is updated to 1.0.2."
> (https://www.openssl.org/policies/releasestrat.html)
> 
> But of course, in practice, there may have been unintended ABI changes
> - so yes, may be a SONAME change is nessary for 1.0.2 as well. I just
> don't know.

SONAME for OpenSSL 1.0.2 in Debian was changed because it was
recompiled with different options to remove some deprecated (but
widely used) functions.  And if application initializes libssl1.0.0
then libssl1.0.2 is left uninitialized and does not work correctly,
while libssl1.1 does not need explicit initialization at all.

OpenSSL libraries have lots of global state, so passing pointers
created with libssl1.0.2 to libssl1.0.0 isn't safe.  Different
features and implementation details of the two libraries are likely to
cause problems too in that case.

> Still, for 1.1 the SONAME change is definitely necessary.

Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and
compiled with OpenSSL 1.0 will probably suffice in that case.

Bug#844638: marked as done (lua-sec needs Breaks: prosody (<< 0.9.11~))

[Debian Bug Tracking System]

Your message dated Sun, 20 Nov 2016 22:03:09 +0200
with message-id <20161120200309.hkszvaaxj5yrk...@bunk.spdns.de>
and subject line This was fixed in lua-sec 0.6-2
has caused the Debian Bug report #844638,
regarding lua-sec needs Breaks: prosody (<< 0.9.11~)
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.)


-- 
844638: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: prosody
Version: 0.9.10-1
Severity: grave

Prosody needs lua 5.1 it seems, but the latest version of lua-sec does
not seem to offer this anymore. Therefore prosody is not able to
initialize TLS anymore:

... tls error   Unable to initialize TLS: LuaSec (required for encryption) was 
not found

This results in a server that is no longer accessible in a standard
encrypted way and thus either makes the service unusable or unsafe.

Re-installing lua-sec 0.5 from stable fixes the issue.

Michael

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

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

Versions of packages prosody depends on:
ii  adduser 3.115
ii  libc6   2.24-5
ii  libidn111.33-1
ii  libssl1.0.2 1.0.2j-1
ii  lua-expat [lua5.1-expat]1.3.0-3
ii  lua-filesystem [lua5.1-filesystem]  1.6.3-1
ii  lua-sec [lua5.1-sec]0.5-1
ii  lua-socket [lua5.1-socket]  3.0~rc1+git+321c0c9-1
ii  lua5.1  5.1.5-8.1+b2
ii  ssl-cert1.0.38

Versions of packages prosody recommends:
ii  lua-event [lua5.1-event]  0.4.3-2
--- End Message ---
--- Begin Message ---
Version: 0.6-2

This was fixed in lua-sec 0.6-2

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--- End Message ---

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Stepan Golosunov]

20.11.2016 в 23:38:48 +0400 Stepan Golosunov написал:
> 20.11.2016 в 20:01:25 +0100 Jan Niehusmann написал:
> > Still, for 1.1 the SONAME change is definitely necessary.
> 
> Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and
> compiled with OpenSSL 1.0 will probably suffice in that case.

No, that won't be sufficient.  One must also ensure that applications
compiled with libssl1.1-using libcurl3 also depend on such
libcurl3 (both for the sake of applications using
CURLOPT_SSL_CTX_FUNCTION and applications dropping OpenSSL
initialization).

Bug#844018: libcurl3: Building with OpenSSL 1.1 breaks packages using both OpenSSL 1.0 and curl

[Stepan Golosunov]

20.11.2016 в 20:48:44 +0100 Jan Niehusmann написал:
> On Sun, Nov 20, 2016 at 11:38:49PM +0400, Stepan Golosunov wrote:
> > > Still, for 1.1 the SONAME change is definitely necessary.
> > 
> > Breaks: against applications using CURLOPT_SSL_CTX_FUNCTION and
> > compiled with OpenSSL 1.0 will probably suffice in that case.
> 
> Wouldn't this still be a serious bug as it would - explicitly - break
> those applications?

It would be a grave bug in such application if it does not have a
working version, yes.  Whether or not it would be a serious bug in
lubcurl3 depends on how many and how important such applications are.
(And how difficult they are to fix.)