Bug#845082: (no subject)

[Antonio Valentino]

Hi Graham,

On Tue, 29 Nov 2016 08:08:10 +0200 Graham Inggs  wrote:
> On 29 November 2016 at 00:29, Breno Leitao  wrote:
> > We just created a pull request to have this fixed upstream.
> 
> Thanks!
> 
> > Should we create a Debian patch also?
> 
> This bug is tagged 'pending' and there's already a patch in the
> packaging git [1].
> I did notice the patch uses round() while your PR uses llround().
> Antonio, should that be changed?

I have just updated the patch to use the same code that has been merged
upstream.

Now just waiting for a sponsor to upload it.

>
> [1] 
> https://anonscm.debian.org/cgit/debian-science/packages/numexpr.git/commit/?id=5c1edd14c6cf8f1258514faca2010380be75bb37
>


best regards

-- 
Antonio Valentino

Processed: reopening 828413, severity of 828413 is important, unblock 827061 with 828413

[Debian Bug Tracking System]

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

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

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

Bug#845416:

[Michael Pratt]

It looks like this package just needs a rebuild. I was able to get a
working deb by simply downloading the source package and doing a manual
build of the package without making any changes.

Bug#830376: marked as done (tpb: FTBFS: dpkg-buildpackage: error: dpkg-source -b tpb-0.6.4 gave error exit status 2)

[Debian Bug Tracking System]

Your message dated Wed, 30 Nov 2016 03:33:20 +
with message-id 
and subject line Bug#830376: fixed in tpb 0.6.4-9
has caused the Debian Bug report #830376,
regarding tpb: FTBFS: dpkg-buildpackage: error: dpkg-source -b tpb-0.6.4 gave 
error exit status 2
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.)


-- 
830376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tpb
Version: 0.6.4-8
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 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):
>  fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp 
> # Add here commands to clean up after the build process.
> [ ! -f Makefile ] || /usr/bin/make distclean
> rm -f config.log
> test -r /usr/share/misc/config.sub && \
>   cp -f /usr/share/misc/config.sub config.sub
> test -r /usr/share/misc/config.guess && \
>   cp -f /usr/share/misc/config.guess config.guess
> debconf-updatepo
> dh_clean
>  dpkg-source -b tpb-0.6.4
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building tpb using existing ./tpb_0.6.4.orig.tar.gz
> dpkg-source: warning: ignoring deletion of directory autom4te.cache
> dpkg-source: warning: ignoring deletion of file autom4te.cache/output.0, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file autom4te.cache/requests, use 
> --include-removal to override
> dpkg-source: warning: ignoring deletion of file autom4te.cache/traces.0, use 
> --include-removal to override
> dpkg-source: info: local changes detected, the modified files are:
>  tpb-0.6.4/config.guess
>  tpb-0.6.4/config.sub
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/tpb_0.6.4-8.diff.K0DV8g
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b tpb-0.6.4 gave error exit status 2
> 
> Build finished at 20160706-2122

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/tpb_0.6.4-8_unstable_reb.normal.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: tpb
Source-Version: 0.6.4-9

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

Debian distribution maintenance software
pp.
Prach Pongpanich  (supplier of updated tpb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 29 Nov 2016 11:17:21 +0700
Source: tpb
Binary: tpb
Architecture: source
Version: 0.6.4-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Prach Pongpanich 
Description:
 tpb- program to use the IBM ThinkPad(tm) special keys
Closes: 830376
Changes:
 tpb (0.6.4-9) unstable; urgency=medium
 .
   [ Prach Pongpanich ]
   * QA upload.
   * Set Debian QA Group as maintainer.
   * Remove manual patch config.*.
   * Add Vcs- fields to collab-maint.
 .
   [ Andrey Rahmatullin ]
   * Non-maintainer upload.
   * Add Build-Depends: libfreetype6-dev (Closes: #830376).
   * Replace manual config.* manipulations with dh_autotools-dev*.
Checksums-Sha1:
 4a4eb039a6ae56eecad2e70ab164dc5ce870ffad 1921 tpb_0.6.4-9.dsc
 defd5c668c84dd06996670692a512ec567aaf7f5 17080 tpb_0.6.4-9.debian.tar.xz
Checksums-Sha256:
 c2d4d05b03d25e08421310f4b2fb1c0d1b171d05892cf8b7c105cdce17707cff 1921 
tpb_0.6.4-9.dsc
 

Bug#843073: Debian Installer Stretch Alpha 8 release

[Guillem Jover]

On Mon, 2016-11-21 at 17:23:19 +0100, Marco d'Itri wrote:
> On Nov 21, Guillem Jover  wrote:
> > Oh, and forgot to mention, this issue has been known for over 8
> > months, and now there's this need to be pushy and rush things, etc.
> > I certainly do not appreciate that.

> No, not really: it was not clear (e.g. I could never reproduce it) until 
> very recently.

Well, it seems it was reproducible enough, that dpkg in Tanglu got a
workaround for it:

  


Regards,
Guillem

Processed: Proper version tracking

[Debian Bug Tracking System]

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

> fixed 829181 1.1-2.1
Bug #829181 {Done: Eriberto Mota } [src:louie] louie: 
FTBFS: dh_clean: Please specify the compatibility level in debian/compat
Marked as fixed in versions louie/1.1-2.1.
> thanks
Stopping processing here.

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

Bug#844944: Patch available from upstream

[Peter Eckersley]

tag 844944 +patch
thanks

There's a proposed patch here:

https://github.com/certbot/certbot/pull/3827/files


On Tue, Nov 22, 2016 at 09:43:20PM -0500, Harlan Lieberman-Berg wrote:
> tag 844944 +upstream
> forwarded 844944 https://github.com/certbot/certbot/issues/3817
> thanks
> 
> This looks related to the openssl version bump.  Sending upstream for
> them to take a look.
> 
> Sincerely,
> -- 
> Harlan Lieberman-Berg
> ~hlieberman
> 
> ___
> Letsencrypt-devel mailing list
> letsencrypt-de...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/letsencrypt-devel
> 

-- 
Peter Eckersleyp...@eff.org
Chief Computer Scientist  Tel  +1 415 436 9333 x131
Electronic Frontier FoundationFax  +1 415 436 9993

Processed: Patch available from upstream

[Debian Bug Tracking System]

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

> tag 844944 +patch
Bug #844944 [src:python-acme] python-acme: FTBFS: dh_auto_test: pybuild --test 
-i python{version} -p 2.7 returned exit code 13
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#846300: ruby-distribution: FTBFS randomly (failing tests)

[Santiago Vila]

Package: src:ruby-distribution
Version: 0.7.3+dfsg-1
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i -O--buildsystem=ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby

[... snipped ...]


  8) Distribution::Poisson Distribution::Poisson::Ruby_ it should behave like 
poisson engine should return correct p_value
 # No exact p_value
 Failure/Error: @engine.p_value(pr,l).should eq(k)
 
   expected: 1
    got: 2
 
   (compared using ==)
 Shared Example Group: "poisson engine" called from 
/<>/ruby-distribution-0.7.3+dfsg/spec/poisson_spec.rb:61
 # 
/<>/ruby-distribution-0.7.3+dfsg/spec/poisson_spec.rb:40:in `block (5 
levels) in '
 # 
/<>/ruby-distribution-0.7.3+dfsg/spec/poisson_spec.rb:38:in `upto'
 # 
/<>/ruby-distribution-0.7.3+dfsg/spec/poisson_spec.rb:38:in `block (4 
levels) in '
 # 
/<>/ruby-distribution-0.7.3+dfsg/spec/poisson_spec.rb:37:in `each'
 # 
/<>/ruby-distribution-0.7.3+dfsg/spec/poisson_spec.rb:37:in `block (3 
levels) in '

  9) Distribution::Poisson Distribution::Poisson::GSL_ it should behave like 
poisson engine should return correct p_value
 # No Distribution::Poisson::GSL_.p_value
 # /<>/ruby-distribution-0.7.3+dfsg/spec/poisson_spec.rb:34


Failures:

  1) Distribution::Beta Distribution::Beta::Ruby_ it should behave like Beta 
engine should return correct p_value
 Failure/Error: @engine.p_value(pr,a, b).should 
be_within(1e-09).of(x/100.0)
   expected 0.98994635582 to be within 1.0e-09 of 0.99
 Shared Example Group: "Beta engine" called from 
/<>/ruby-distribution-0.7.3+dfsg/spec/beta_spec.rb:63
 # /<>/ruby-distribution-0.7.3+dfsg/spec/beta_spec.rb:44:in 
`block (4 levels) in '
 # /<>/ruby-distribution-0.7.3+dfsg/spec/beta_spec.rb:40:in 
`upto'
 # /<>/ruby-distribution-0.7.3+dfsg/spec/beta_spec.rb:40:in 
`block (3 levels) in '

Finished in 1.89 seconds (files took 0.31514 seconds to load)
144 examples, 1 failure, 9 pending

Failed examples:

rspec 
'/<>/ruby-distribution-0.7.3+dfsg/spec/beta_spec.rb[1:2:1:3]' 
# Distribution::Beta Distribution::Beta::Ruby_ it should behave like Beta 
engine should return correct p_value

/usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb failed
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install 
/<>/ruby-distribution-0.7.3+dfsg/debian/ruby-distribution returned 
exit code 1
debian/rules:18: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>/ruby-distribution-0.7.3+dfsg'
debian/rules:15: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


The failure happens randomly. Sometimes it fails, sometimes it does not.

I attach two failed logs, but there is also another build failure here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-distribution.html

If the tests are not designed to never fail, I suggest them to be disabled.

Thanks.

ruby-distribution_0.7.3+dfsg-1_amd64-20161129T021725Z.gz
Description: application/gzip


ruby-distribution_0.7.3+dfsg-1_amd64-20161129T102851Z.gz
Description: application/gzip

Bug#845385: Privilege escalation via removal

[Emmanuel Bourg]

Le 29/11/2016 à 23:45, Markus Koschany a écrit :

> I don't understand why this is a security issue when
> /etc/tomcat8/Catalina/attack is owned by root:root after the purge and
> the tomcat8 user doesn't even exist anymore.

My understanding is that the file is left with execution permissions for
all users and setgid root after the purge. Any local user can then take
control of the system.

Emmanuel Bourg

Bug#846295: marked as done (octave: Octave can't find correct library files on installation)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 15:19:58 -0800
with message-id <20161129231958.npbwa7g3qrkrb...@galago.mtmxr.com>
and subject line Re: Bug#846295: octave: Octave can't find correct library 
files on installation
has caused the Debian Bug report #846295,
regarding octave: Octave can't find correct library files on installation
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.)


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


Package: octave
Version: 4.0.3-2+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

I attempted to install the Octave package on my Debian Stretch system using
both Aptitude and apt-get. Both methods resulted in the same error:

Setting up octave (4.0.3-2+b1) ...
/usr/local/libexec/octave/4.0.0/exec/x86_64-unknown-linux-gnu/octave-gui: 
error
while loading shared libraries: libgl2ps.so.0: cannot open shared object 
file:

No such file or directory
dpkg: error processing package octave (--configure):

The .deb file seems to be looking for the wrong version of the lib file. The
newer version is libgl2ps.so.1

I set up a soft link from the old version to the new, re-ran the install and
now get a new error that the installer can't find libcholmod.so.2.1.2.

Maybe the .deb file is completely out of date.

Gary Roach




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

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

Versions of packages octave depends on:
ii  libamd2  1:4.5.3-2
ii  libarpack2   3.4.0-1+b1
ii  libasound2   1.1.2-1
ii  libatlas3-base [liblapack.so.3]  3.10.3-1
ii  libblas3 [libblas.so.3]  3.6.1-2
ii  libc62.24-5
ii  libcamd2 1:4.5.3-2
ii  libccolamd2  1:4.5.3-2
ii  libcholmod3  1:4.5.3-2
ii  libcolamd2   1:4.5.3-2
ii  libcxsparse3 1:4.5.3-2
ii  libfftw3-double3 3.3.5-1
ii  libfftw3-single3 3.3.5-1
ii  libfltk-gl1.31.3.3-8+b1
ii  libfltk1.3   1.3.3-8+b1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.2.0-13
ii  libgl1-mesa-glx [libgl1] 12.0.4-2
ii  libglpk404.60-2+b1
ii  libglu1-mesa [libglu1]   9.0.0-2.1
ii  libgomp1 6.2.0-13
ii  liblapack3 [liblapack.so.3]  3.6.1-2
ii  liboctave3v5 4.0.3-2+b1
ii  libosmesa6   12.0.4-2
ii  libportaudio219+svn20140130-1.1
ii  libqhull72015.2-1
ii  libqrupdate1 1.1.2-2
ii  libqscintilla2-12v5  2.9.3+dfsg-4
ii  libqt4-network   4:4.8.7+dfsg-11
ii  libqt4-opengl4:4.8.7+dfsg-11
ii  libqtcore4   4:4.8.7+dfsg-11
ii  libqtgui44:4.8.7+dfsg-11
ii  libsndfile1  1.0.27-1
ii  libstdc++6   6.2.0-13
ii  libumfpack5  1:4.5.3-2
ii  libx11-6 2:1.6.3-1
ii  octave-common4.0.3-2
ii  texinfo  6.3.0.dfsg.1-1+b1

Versions of packages octave recommends:
ii  default-jre-headless  2:1.8-57
ii  gnuplot-x11   5.0.5+dfsg1-4
ii  libatlas3-base3.10.3-1
ii  octave-info   4.0.3-2
ii  pstoedit  3.70-3+b1

Versions of packages octave suggests:
pn  octave-doc  
pn  octave-htmldoc  

-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, Nov 29, 2016 at 14:11:46 -0800, Gary Roach wrote:
> Mike,
> 
> You were dead on. I deleted the local files and octave loaded fine. I don't
> know where those files came from and I wouldn't have found them in a million
> years. Sorry to muck up the bug reporting system with a non-bug but thank
> you very very much.

No problem, closing report.

-- 
mike--- End Message ---

Bug#845385: Privilege escalation via removal

[Markus Koschany]

I think the solution is quite simple.

Let's replace

chown -Rhf root:root /etc/tomcat8/ || true

with

rm -rf /etc/tomcat8

I mean purge means purge. Remove all files, don't leave anything behind.

As another improvement suggestion for Tomcat 9, we could stop deleting
the tomcat user on purge and let the admin decide. I believe this is
even consensus within the project and will protect against reusing files
with the old GID and UID for something unintended.





signature.asc
Description: OpenPGP digital signature

Bug#846113: polygraph loses SSL support when compiled with OpenSSL 1.1

[Adrian Bunk]

On Tue, Nov 29, 2016 at 11:50:21PM +0100, Sebastian Andrzej Siewior wrote:
> On 2016-11-28 16:49:35 [+0200], Adrian Bunk wrote:
> > Package: polygraph
> > Version: 4.3.2-4
> > Severity: serious
> > Tags: patch
> > Control: block 827061 by -1
> > 
> > ...
> > checking for CRYPTO_lock in -lcrypto... no
> > checking for CRYPTO_add_lock in -lcrypto... no
> > ...
> > 
> > Not a perfect solution but an option for stretch is the patch below to 
> > use OpenSSL 1.0.2
> > 
> > The "| libssl-dev (<< 1.1.0~)" is added for backports.
> 
> could we please keep the bug reporting the way we had it? That means to
> note that fails to properly build against openssl 1.1 which will remain
> open with severity important if the package stays with openssl 1.0.
> 
> > --- debian/control.old  2016-11-28 11:13:51.0 +
> > +++ debian/control  2016-11-28 11:13:57.0 +
> > @@ -6,7 +6,7 @@
> >   debhelper (>= 9),
> >   dh-autoreconf,
> >   libncurses5-dev,
> > - libssl-dev,
> > + libssl1.0-dev | libssl-dev (<< 1.1.0~),
> >   zlib1g-dev,
> >  Standards-Version: 3.9.8
> >  Homepage: http://www.web-polygraph.org
> 
> I though we agreed not to tag this as a patch

Where did I agree to that?

> but as a hint what can be
> done if the maintainer chooses to stay with 1.0.

Reality in Debian is that a large amount of packages is not well 
maintained, polygraph is actually orphaned.

> Do you expect this bug
> to be closed once it switches to libsl1.0-dev?

The thing I do care about is not the patch tag, the thing I do care 
about is that we are not losing any packages in stretch due to the
whole OpenSSL situation.

A patch tag makes it visible that there is a solution for the RC issue 
in stretch.

Who is going to do the uploads for the ~ 100 not well maintained 
packages that need to be switched to 1.0.2?

Will you do these?
It should be your job for making dual 1.0.2/1.1 work.

Or will you at least sponsor me, if I send you a batch of 100 NMUs and 
QA uploads switching packages to 1.0.2?

> Sebastian

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#845729: libtspi-dev must not force OpenSSL 1.1 on packages that are not ready

[Sebastian Andrzej Siewior]

On 2016-11-26 11:31:49 [+0200], Adrian Bunk wrote:
> Package: libtspi-dev
> Version: 0.3.14+fixed1-1
> Severity: serious
> Control: block 827061 by -1
> 
> libtspi-dev must not force OpenSSL 1.1 on packages that
> are not ready for 1.1
> 
> At least opencryptoki (#828465) and tpm-tools (#828577)
> are not even compiling with OpenSSL 1.1
>
> Options to solve this issue:
> - fix all r-(b)deps to compile and work with OpenSSL 1.1, or
> - use OpenSSL 1.0.2 in stretch

tpm-tools does not build and has hints to solve the openssl issue. So it
is actually just opencryptoki.

Sebastian

Bug#846299: lighttpd depends on systemd

[Gianluigi Tiesi]

Source: lighttpd
Version: 1.4.43-1
Severity: serious

lighttpd 1.4.39-1 depends on lsb-base (>= 3.2-14) | systemd (>= 29.1)

while lighttpd 1.4.43-1 depends on lsb-base AND systemd,
is it intentional?

1.4.39-1 just works fine without systemd

Regards


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#845385: Privilege escalation via removal

[Markus Koschany]

> I don't understand why this is a security issue when
> /etc/tomcat8/Catalina/attack is owned by root:root after the purge and
> the tomcat8 user doesn't even exist anymore.

Nevermind. I missed the "world". However dpkg warns about that
/etc/tomcat8/Catalina is not empty on purge, so the admin will be
informed that something requires his attention. Besides all tomcat
processes are killed on purge.



signature.asc
Description: OpenPGP digital signature

Bug#846078: [pycogent/pycogent] Random failures of test suite (#103)

[Santiago Vila]

On Tue, Nov 29, 2016 at 09:31:05AM +0100, Andreas Tille wrote:

> Thanks a lot for this quick and helpful response.  I've prepared a
> package featuring this verbose output and uploaded it to the Debian
> mirror.  Santiago, I wonder whether you can run your tests with
> python-cogent_1.9-5 to possibly reproduce the failures.  This should
> give a hint what actual test might cause the problem.

I built 1.9-5 two hundred times and it failed 16 times.
I put the build logs here to not clutter the BTS:

https://people.debian.org/~sanvila/python-cogent/

[ Not confident enough to CC all the funny email addresses in the previous
  email, free free to forward this to whoever may be interested ].

Thanks.

Bug#846113: polygraph loses SSL support when compiled with OpenSSL 1.1

[Sebastian Andrzej Siewior]

On 2016-11-28 16:49:35 [+0200], Adrian Bunk wrote:
> Package: polygraph
> Version: 4.3.2-4
> Severity: serious
> Tags: patch
> Control: block 827061 by -1
> 
> ...
> checking for CRYPTO_lock in -lcrypto... no
> checking for CRYPTO_add_lock in -lcrypto... no
> ...
> 
> Not a perfect solution but an option for stretch is the patch below to 
> use OpenSSL 1.0.2
> 
> The "| libssl-dev (<< 1.1.0~)" is added for backports.

could we please keep the bug reporting the way we had it? That means to
note that fails to properly build against openssl 1.1 which will remain
open with severity important if the package stays with openssl 1.0.

> --- debian/control.old2016-11-28 11:13:51.0 +
> +++ debian/control2016-11-28 11:13:57.0 +
> @@ -6,7 +6,7 @@
>   debhelper (>= 9),
>   dh-autoreconf,
>   libncurses5-dev,
> - libssl-dev,
> + libssl1.0-dev | libssl-dev (<< 1.1.0~),
>   zlib1g-dev,
>  Standards-Version: 3.9.8
>  Homepage: http://www.web-polygraph.org

I though we agreed not to tag this as a patch but as a hint what can be
done if the maintainer chooses to stay with 1.0. Do you expect this bug
to be closed once it switches to libsl1.0-dev?

Sebastian

Bug#845385: Privilege escalation via removal

[Markus Koschany]

On Wed, 23 Nov 2016 09:35:34 +1100 Paul Szabo 
wrote:
> Package: tomcat8
> Version: 8.0.14-1+deb8u4
> Severity: critical
> Tags: security
> 
> Having installed tomcat8, the directory /etc/tomcat8/Catalina is set
> writable by group tomcat8, as per the postinst script. Then the tomcat8
> user, in the situation envisaged in DSA-3670 and DSA-3720, see also
>   http://seclists.org/fulldisclosure/2016/Oct/4
> could use something like commands
>   touch /etc/tomcat8/Catalina/attack
>   chmod 2747 /etc/tomcat8/Catalina/attack
> to create a file:
>   # ls -l /etc/tomcat8/Catalina/attack
>   -rwxr-Srwx 1 tomcat8 tomcat8 0 Nov 23 09:00 /etc/tomcat8/Catalina/attack
> Then if the tomcat8 package is removed (purged?), the postrm script runs
>   chown -Rhf root:root /etc/tomcat8/
> and that will leave the file world-writable, setgid root:
>   # ls -l /etc/tomcat8/Catalina/attack
>   -rwxr-Srwx 1 root root 0 Nov 23 09:00 /etc/tomcat8/Catalina/attack
> allowing "group root" access to the world.

I don't understand why this is a security issue when
/etc/tomcat8/Catalina/attack is owned by root:root after the purge and
the tomcat8 user doesn't even exist anymore.

Markus




signature.asc
Description: OpenPGP digital signature

Processed: Update bug status

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #840377 [src:pyepl] pyepl: Please remove build dependency on jade
Severity set to 'serious' from 'normal'

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

Bug#844143: marked as done (eclipse-titan: FTBFS: pattern_la.l:38:24: fatal error: pattern_p.hh: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 21:48:50 +
with message-id 
and subject line Bug#844143: fixed in eclipse-titan 6.1.0-1
has caused the Debian Bug report #844143,
regarding eclipse-titan: FTBFS: pattern_la.l:38:24: fatal error: pattern_p.hh: 
No such file or directory
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.)


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

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/<>/common'
> bison -d -o config_preproc_p.tab.cc -p config_process_ config_preproc_p.y
> flex -B -s -Cr -Cfe -oconfig_preproc_la.cc config_preproc_la.l
> bison -d pattern_uni.y
> bison -d pattern_p.y
> flex -B -s -Cr -Cfe -opattern_la.cc pattern_la.l
> config_preproc_p.y:51.1-13: warning: deprecated directive, use '%name-prefix' 
> [-Wdeprecated]
>  %name-prefix="config_preproc_yy"
>  ^
> pattern_uni.y:80.1-13: warning: deprecated directive, use '%name-prefix' 
> [-Wdeprecated]
>  %name-prefix="pattern_uni"
>  ^
> pattern_uni.y:81.1-8: warning: deprecated directive, use '%output' 
> [-Wdeprecated]
>  %output="pattern_uni.cc"
>  
>   (dep)NetworkHandler.cc
> pattern_p.y:127.1-13: warning: deprecated directive, use '%name-prefix' 
> [-Wdeprecated]
>  %name-prefix="pattern_yy"  (dep)  JSON_Tokenizer.cc
> 
>  ^
> pattern_p.y:128.1-8: warning: deprecated directive, use '%output' 
> [-Wdeprecated]
>  %output="pattern_p.cc"
>  
>   (dep)ModuleVersion.cc
>   (dep)Path2.cc
>   (dep)Quadruple.cc
>   (dep)config_preproc.cc
>   (dep)path.c
>   (dep)userinfo.c
>   (dep)new.cc
>   (dep)memory.c
>   (dep)pattern_la.cc
> pattern_la.l:38:24: fatal error: pattern_p.hh: No such file or directory
>  #include "pattern_p.hh"
> ^
> compilation terminated.
>   (dep)config_preproc_la.cc
>   (dep)config_preproc_p.tab.cc
>   (dep)pattern_uni.cc
>   (dep)pattern_p.cc
>   (dep)pattern_la.cc
> gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -DYY_NO_INPUT -DNDEBUG  -DLINUX 
> -DUSE_EPOLL -DYY_NO_INPUT -DNDEBUG  -DLINUX -DUSE_EPOLL -D_REENTRANT -Wall 
> -std=gnu9x -O2 -fPIC memory.c -o memory.o
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -DYY_NO_INPUT -DNDEBUG  -DLINUX 
> -DUSE_EPOLL -DYY_NO_INPUT -DNDEBUG  -DLINUX -DUSE_EPOLL -D_REENTRANT -g -O2 
> -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wno-long-long -O2 -fPIC -Wall -Wno-long-long 
> -O2 -fPIC new.cc -o new.o
> gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -DYY_NO_INPUT -DNDEBUG  -DLINUX 
> -DUSE_EPOLL -DYY_NO_INPUT -DNDEBUG  -DLINUX -DUSE_EPOLL -D_REENTRANT -Wall 
> -std=gnu9x -O2 -fPIC userinfo.c -o userinfo.o
> gcc -c -Wdate-time -D_FORTIFY_SOURCE=2 -DYY_NO_INPUT -DNDEBUG  -DLINUX 
> -DUSE_EPOLL -DYY_NO_INPUT -DNDEBUG  -DLINUX -DUSE_EPOLL -D_REENTRANT -Wall 
> -std=gnu9x -O2 -fPIC path.c -o path.o
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -DYY_NO_INPUT -DNDEBUG  -DLINUX 
> -DUSE_EPOLL -DYY_NO_INPUT -DNDEBUG  -DLINUX -DUSE_EPOLL -D_REENTRANT -g -O2 
> -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wno-long-long -O2 -fPIC -Wall -Wno-long-long 
> -O2 -fPIC config_preproc.cc -o config_preproc.o
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -DYY_NO_INPUT -DNDEBUG  -DLINUX 
> -DUSE_EPOLL -DYY_NO_INPUT -DNDEBUG  -DLINUX -DUSE_EPOLL -D_REENTRANT -g -O2 
> -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wno-long-long -O2 -fPIC -Wall -Wno-long-long 
> -O2 -fPIC Quadruple.cc -o Quadruple.o
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -DYY_NO_INPUT -DNDEBUG  -DLINUX 
> -DUSE_EPOLL -DYY_NO_INPUT -DNDEBUG  -DLINUX -DUSE_EPOLL -D_REENTRANT -g -O2 
> -fdebug-prefix-map=/<>=. 
> -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wno-long-long -O2 -fPIC -Wall -Wno-long-long 
> -O2 -fPIC Path2.cc -o Path2.o
> g++ -c -Wdate-time -D_FORTIFY_SOURCE=2 -DYY_NO_INPUT -DNDEBUG  -DLINUX 
> -DUSE_EPOLL 

Processed: liquidsoap: diff for NMU version 1.1.1-7.2

[Debian Bug Tracking System]

Processing control commands:

> tags 845363 + pending
Bug #845363 [src:liquidsoap] liquidsoap: removal of libschroedinger
Added tag(s) pending.

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

Bug#844479: RE:Bug#844479: zeromq3: zeromq 4.2.0 breaks tango

[Julian Taylor]

On Thu, 24 Nov 2016 11:56:15 + Luca Boccassi
 wrote:
> On Thu, 2016-11-24 at 09:58 +, PICCA Frederic-Emmanuel wrote:
> > Hello,
> > 
> > I just opened a bug for tango
> > 
> > https://github.com/tango-controls/cppTango/issues/312
> > 
> > 
> > what is the deadline where we can take the decision to upload or not zeromq 
> > 4.2.0 into Debian testing ?
> > 
> > This will let also some time in order to check if this 4.2.0 do not have 
> > other size effect of dependeings softwares.
> > 
> > Thanks
> > 
> > Fred
> 
> Hi,
> 
> Thanks for opening a bug upstream.
> 
> There is no ABI breakage so there is time for the migration until at
> least the 5th of February.
> 
> I see 3 alternatives here:
> 
> 1) Upstream fixes it
> 2) A patch to revert the internal buffer alignment is added here
> 3) Ship stretch with 4.1.x
> 
> 1 - is of course the preferred way. 2 - is also feasible, but I think
> the consensus upstream is that we don't want to commit to any specific
> guarantee about internal implementation, as it ties down development too
> much. So it would have to be an out-of-tree patch, and I can provide
> that if needed.
> 
> The zeromq mailing list is the right place to discuss this if anyone
> strongly disagrees, we are open to have a discussion about anything and
> everything of course. There are differing opinions about these issues
> that range the whole spectrum, from "if users depend on it it's not a
> bug, it's a feature" to "let's break everything everytime", and anywhere
> in between.
> 
> I'm doing my best to commit to semantic versioning and API/ABI
> compatibility guarantees, going beyond that is very difficult.
> 
> The third option is the worst case scenario. Note that we haven't
> deprecated 4.1.x yet. I wanted to, given it's ABI compatible with 4.2.x,
> but if push came to shove I guess it will have to stay around.
> 

Nitpick, alignment is part of the ABI so it is not compatible.

But on how to fix this. Given [0] you seem to be just passing out the
pointer to your internal buffer written without padding out to the user
via zmq_msg_data (?)

The documentation of that function states that you must not access
zmq_msg_t directly, so if nobody actual does do so regardless zmq can
change this structure and stay compatible?
If so can zmq insert alignment padding between the message headers and
the payload so zmq_msg_data returns aligned data?

This would be very good for compatibility, on non-x86 arches it might
even be better for performance. Unaligned access can be very slow on
some of the less powerful cpus.

(Also even on x86 you can get into alignment issues due to these
buffers, in particular with numerical applications where
auto-vectorization by the compilers is involved)

[0] http://lists.zeromq.org/pipermail/zeromq-dev/2016-November/031096.html

Processed: Update bug status

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #837510 [src:mozart] mozart: Please replace build dependency on sp with 
opensp
Severity set to 'serious' from 'normal'

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

Bug#806032: marked as done (gftp: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 21:49:01 +
with message-id 
and subject line Bug#806032: fixed in gftp 2.0.19-5
has caused the Debian Bug report #806032,
regarding gftp: FTBFS when built with dpkg-buildpackage -A (No such file or 
directory)
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.)


-- 
806032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gftp
Version: 2.0.19-4
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install
make -j1 install DESTDIR=/<>/debian/tmp 
AM_UPDATE_INFO_DIR=no
make[2]: Entering directory '/<>'
Making install in docs
make[3]: Entering directory '/<>/docs'
Making install in sample.gftp
make[4]: Entering directory '/<>/docs/sample.gftp'
make[5]: Entering directory '/<>/docs/sample.gftp'
make[5]: Nothing to be done for 'install-exec-am'.
test -z "/usr/share/gftp" || mkdir -p -- 
"/<>/debian/tmp/usr/share/gftp"
 /usr/bin/install -c -m 644 'COPYING' 
'/<>/debian/tmp/usr/share/gftp/COPYING'
 /usr/bin/install -c -m 644 'bookmarks' 
'/<>/debian/tmp/usr/share/gftp/bookmarks'
 /usr/bin/install -c -m 644 'connect.xpm' 
'/<>/debian/tmp/usr/share/gftp/connect.xpm'
 /usr/bin/install -c -m 644 'deb.xpm' 
'/<>/debian/tmp/usr/share/gftp/deb.xpm'
 /usr/bin/install -c -m 644 'diff.xpm' 
'/<>/debian/tmp/usr/share/gftp/diff.xpm'
 /usr/bin/install -c -m 644 'dir.xpm' 
'/<>/debian/tmp/usr/share/gftp/dir.xpm'

[... snipped ...]

make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
convert -geometry 32x32 /<>/debian/tmp/usr/share/pixmaps/gftp.png 
/<>/debian/tmp/usr/share/pixmaps/gftp.xpm
install -m 755 /<>/docs/parse-netrc.pl 
/<>/debian/gftp-common/usr/share/doc/gftp-common/examples
install: cannot create regular file 
'/<>/debian/gftp-common/usr/share/doc/gftp-common/examples': No 
such file or directory
debian/rules:29: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:16: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


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

Thanks.
--- End Message ---
--- Begin Message ---
Source: gftp
Source-Version: 2.0.19-5

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated gftp 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 

Bug#845363: liquidsoap: diff for NMU version 1.1.1-7.2

[Sebastian Ramacher]

Control: tags 845363 + pending

Dear maintainer,

I've prepared an NMU for liquidsoap (versioned as 1.1.1-7.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru liquidsoap-1.1.1/debian/changelog liquidsoap-1.1.1/debian/changelog
--- liquidsoap-1.1.1/debian/changelog	2016-01-10 14:23:25.0 +0100
+++ liquidsoap-1.1.1/debian/changelog	2016-11-29 22:37:34.0 +0100
@@ -1,3 +1,12 @@
+liquidsoap (1.1.1-7.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Andreas Cadhalpun ]
+  * Drop support for libschroedinger. (Closes: #845363)
+
+ -- Sebastian Ramacher   Tue, 29 Nov 2016 22:37:34 +0100
+
 liquidsoap (1.1.1-7.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru liquidsoap-1.1.1/debian/control liquidsoap-1.1.1/debian/control
--- liquidsoap-1.1.1/debian/control	2016-01-10 14:09:26.0 +0100
+++ liquidsoap-1.1.1/debian/control	2016-11-29 22:35:41.0 +0100
@@ -42,7 +42,6 @@
  libportaudio-ocaml-dev (>= 0.2.0),
  libpulse-ocaml-dev (>= 0.1.2),
  libsamplerate-ocaml-dev (>= 0.1.2),
- libschroedinger-ocaml-dev (>= 0.1.0-3),
  libsdl-ocaml-dev,
  libshine-ocaml-dev,
  libsoundtouch-ocaml-dev (>= 0.1.7),
@@ -142,7 +141,6 @@
  liquidsoap-plugin-portaudio,
  liquidsoap-plugin-pulseaudio,
  liquidsoap-plugin-samplerate,
- liquidsoap-plugin-schroedinger,
  liquidsoap-plugin-sdl,
  liquidsoap-plugin-shine,
  liquidsoap-plugin-soundtouch,
@@ -497,7 +495,7 @@
  .
  This package provides support for Ogg stream decoding and encoding in
  Liquidsoap. This plugin is only useful when used with one of vorbis,
- speex, flac, theora or schroedinger plugin.
+ speex, flac or theora plugin.
 
 Package: liquidsoap-plugin-opus
 Architecture: any
@@ -587,24 +585,6 @@
  This package provides support for audio samplerate conversion using
  libsamplerate in Liquidsoap.
 
-Package: liquidsoap-plugin-schroedinger
-Architecture: any
-Depends:
- liquidsoap (= ${binary:Version}),
- ${misc:Depends},
- ${ocaml:Depends},
- ${shlibs:Depends}
-Description: audio streaming language -- Schroedinger plugin
- Liquidsoap is a powerful tool for building complex audio streaming systems,
- typically targeting internet radios (e.g. icecast streams).
- .
- It consists of a simple script language, in which you can create, combine and
- transform audio sources. Its design makes liquidsoap flexible and easily
- extensible.
- .
- This package provides support ogg/dirac video decoding and encoding using
- libschroedinger in Liquidsoap.
-
 Package: liquidsoap-plugin-sdl
 Architecture: any
 Depends:
diff -Nru liquidsoap-1.1.1/debian/files liquidsoap-1.1.1/debian/files
--- liquidsoap-1.1.1/debian/files	1970-01-01 01:00:00.0 +0100
+++ liquidsoap-1.1.1/debian/files	2016-11-29 22:36:20.0 +0100
@@ -0,0 +1 @@
+liquidsoap_1.1.1-7.2_source.buildinfo sound optional
diff -Nru liquidsoap-1.1.1/debian/liquidsoap-plugin-schroedinger.install liquidsoap-1.1.1/debian/liquidsoap-plugin-schroedinger.install
--- liquidsoap-1.1.1/debian/liquidsoap-plugin-schroedinger.install	2016-01-10 12:10:14.0 +0100
+++ liquidsoap-1.1.1/debian/liquidsoap-plugin-schroedinger.install	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-usr/lib/liquidsoap/*/plugins/schroedinger.cm*
diff -Nru liquidsoap-1.1.1/debian/rules liquidsoap-1.1.1/debian/rules
--- liquidsoap-1.1.1/debian/rules	2016-01-10 13:56:35.0 +0100
+++ liquidsoap-1.1.1/debian/rules	2016-11-29 22:35:41.0 +0100
@@ -9,7 +9,7 @@
 DEFAULT_FONT := /usr/share/fonts/truetype/ttf-liberation/LiberationSans-Regular.ttf
 
 DEB_CONFIGURE_EXTRA_FLAGS := \
-  --enable-ogg-dynamic-plugin --enable-schroedinger-dynamic-plugin --enable-flac-dynamic-plugin \
+  --enable-ogg-dynamic-plugin --enable-flac-dynamic-plugin \
   --enable-speex-dynamic-plugin --enable-vorbis-dynamic-plugin --enable-theora-dynamic-plugin \
   --enable-sdl-dynamic-plugin --enable-gavl-dynamic-plugin --enable-mad-dynamic-plugin \
   --enable-faad-dynamic-plugin --enable-xmlplaylist-dynamic-plugin --enable-lastfm-dynamic-plugin \
@@ -41,7 +41,7 @@
 -Nliquidsoap-plugin-ladspa -Nliquidsoap-plugin-lastfm -Nliquidsoap-plugin-mad \
 -Nliquidsoap-plugin-ogg -Nliquidsoap-plugin-oss -Nliquidsoap-plugin-portaudio \
 -Nliquidsoap-plugin-pulseaudio -Nliquidsoap-plugin-samplerate \
--Nliquidsoap-plugin-schroedinger -Nliquidsoap-plugin-soundtouch -Nliquidsoap-plugin-speex \
+-Nliquidsoap-plugin-soundtouch -Nliquidsoap-plugin-speex \
 -Nliquidsoap-plugin-taglib -Nliquidsoap-plugin-theora -Nliquidsoap-plugin-voaacenc \
 -Nliquidsoap-plugin-vorbis -Nliquidsoap-plugin-xmlplaylist -Nliquidsoap-plugin-lame \
 -Nliquidsoap-plugin-dssi -Nliquidsoap-plugin-lo -Nliquidsoap-plugin-camlimages \


signature.asc
Description: PGP signature

Processed: Update bug status

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #832491 [aboot] aboot: please remove build dependency on obsolete package sp
Severity set to 'serious' from 'normal'

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

Bug#846295: octave: Octave can't find correct library files on installation

[Mike Miller]

On Tue, Nov 29, 2016 at 13:20:26 -0800, Gary Roach wrote:
> I attempted to install the Octave package on my Debian Stretch system using
> both Aptitude and apt-get. Both methods resulted in the same error:
> 
> Setting up octave (4.0.3-2+b1) ...
> /usr/local/libexec/octave/4.0.0/exec/x86_64-unknown-linux-gnu/octave-gui:
> error
> while loading shared libraries: libgl2ps.so.0: cannot open shared object
> file:
> No such file or directory
> dpkg: error processing package octave (--configure):
> 
> The .deb file seems to be looking for the wrong version of the lib file. The
> newer version is libgl2ps.so.1
> 
> I set up a soft link from the old version to the new, re-ran the install and
> now get a new error that the installer can't find libcholmod.so.2.1.2.
> 
> Maybe the .deb file is completely out of date.

Actually the above error indicates that you probably have a locally
built /usr/local/bin/octave that is found in $PATH before the
apt-provided /usr/bin/octave.

Can you delete your local installation and try again to verify that the
package is working correctly?

-- 
mike

Bug#845362: marked as done (libquicktime: removal of libschroedinger)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 21:33:58 +
with message-id 
and subject line Bug#845362: fixed in libquicktime 2:1.2.4-9
has caused the Debian Bug report #845362,
regarding libquicktime: removal of libschroedinger
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.)


-- 
845362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libquicktime
Version: 2:1.2.4-8
Severity: serious
Tags: patch
Control: block 845037 by -1

Dear Maintainer,

libschroedinger contains various possibly security relevant bugs and is
no longer maintained upstream. Therefore it has been decided to remove
it from Debian. (see bug #845037)

Before it can be removed, all reverse dependencies have to stop using it.

Attached is a patch dropping the build-dependency on libschroedinger-dev,
which is sufficient to achieve this.

Best regards,
Andreas
--- a/debian/control
+++ b/debian/control
@@ -25,7 +25,6 @@ Build-Depends:
  libpng-dev,
  libpopt-dev,
  libraw1394-dev [linux-any],
- libschroedinger-dev,
  libsdl1.2-dev,
  libswscale-dev (>= 6:10~),
  libvorbis-dev,

--- End Message ---
--- Begin Message ---
Source: libquicktime
Source-Version: 2:1.2.4-9

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated libquicktime 
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: Tue, 29 Nov 2016 22:06:34 +0100
Source: libquicktime
Binary: libquicktime2 libquicktime-dev libquicktime-doc quicktime-utils 
quicktime-x11utils
Architecture: source
Version: 2:1.2.4-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Sebastian Ramacher 
Description:
 libquicktime-dev - library for reading and writing Quicktime files 
(development)
 libquicktime-doc - library for reading and writing Quicktime files 
(documentation)
 libquicktime2 - library for reading and writing Quicktime files
 quicktime-utils - library for reading and writing Quicktime files (utilities)
 quicktime-x11utils - library for reading and writing Quicktime files (x11 
utilities)
Closes: 845362
Changes:
 libquicktime (2:1.2.4-9) unstable; urgency=medium
 .
   * Team upload.
   * debian/control:
 - Bump Standards-Version
 - Remove libschroedinger-dev from B-D. (Closes: #845362)
   * debian/rules: Pass -Xlqt_ to dh_makeshlibs to ignore plugins when 
generating
 symbol file.
Checksums-Sha1:
 9225d6cec001e37bc056ae56cbea2cedc7834ed7 2696 libquicktime_1.2.4-9.dsc
 358846cad9a688b5f86c8794e44f12b39dca9b67 21064 
libquicktime_1.2.4-9.debian.tar.xz
Checksums-Sha256:
 6ac2afe7869d51d0e40a305045871db6b3214a55dea07f2ab66d02f0e8ebb275 2696 
libquicktime_1.2.4-9.dsc
 10203fb089faf5a866cc0be3e0d9569f9d7b845ce026f0129072aad07f7e9ba0 21064 
libquicktime_1.2.4-9.debian.tar.xz
Files:
 894b088fd6e60ee5c823c4109d9897ef 2696 devel optional libquicktime_1.2.4-9.dsc
 cbe91f9ceef7b448f8a7a90bef319c71 21064 devel optional 
libquicktime_1.2.4-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAlg97s0ACgkQafL8UW6n
GZP8cxAAhlxEUg1TUTrnoiwpfpJf26Rbqml3sTPf0YKg3ZiZTCEI3EPuV2yKJrWu
o9WtJCx56xU7TWdZmUJ10gYpnwePwKiyyQVe4KM1U7PR7OcaCSr/P9awp17Sglt/
mdHS20avxQ+3KBqzAvAU3aaw8EnHUSstRjTdl1Vg+vG4yDSAmCql42Gy+oEPJktM
nDWTEYNy4T7PLKB4IhCurImzEhve3YTDZEqOsk6EiYHpHMSPhbweIgEunG+UmsV+
wTyoeSvtQAj5zd8I6pnmj1Y+SsBX8+DW6Ir74jDh1hWB65Bo/5/ujtBPqWSYpAc+
M+y1XXqboB5aprxIRh0WrYDYzz9TcUDlwMJMN7iUR2rnzxpHdMcKsX3UYiWCFk+I
O91SDzYKCwZagutyIuxi7hG7ohLp9nZHTRdxLOO1aZoeBo1KztrDKb/gYy7vTTjE
5WHqtZubkEi+yret6WOrZrKts/SoIM/+7SPxM0f1g+ZLUbdBr2/sSJmgauNxCEj0
mr4NUbPFH6ewa0thbtDhLZdHApleutyrvJlZiLjqWG/+NOfvdQTkEqWZT4cpATnN
ql4QJ73dvA5Rxa+7OFOnjXw7vK1k2Fi0TnTgvx2yjpdrMowZ9BBJWc1KSUbMvK+P
R3j/UW6eijH5qH1ODgJaydeW4Qs9shA/vKHxzYf9XDTWUBzX4vw=
=mmo4
-END PGP SIGNATURE End 

Processed: limit source to lintian, tagging 844903, tagging 843406, tagging 818962, tagging 843595

[Debian Bug Tracking System]

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

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

> tags 844903 + pending
Bug #844903 [src:lintian] lintian: FTBFS: Tests failures
Added tag(s) pending.
> tags 843406 + pending
Bug #843406 [lintian] lintian: embedded openssl library in openssl1.0 source 
package
Added tag(s) pending.
> tags 818962 + pending
Bug #818962 [lintian] fix the php-script-but-no-phpX-cli-dep error
Added tag(s) pending.
> tags 843595 + pending
Bug #843595 [lintian] [lintian] Detect non free unicode code and embeded copy
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#840458: marked as done (linbox: FTBFS on i386: illegal instruction in test-{cra,charpoly})

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 21:21:42 +
with message-id 
and subject line Bug#840458: fixed in givaro 4.0.2-4
has caused the Debian Bug report #840458,
regarding linbox: FTBFS on i386: illegal instruction in test-{cra,charpoly}
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.)


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

The i386 build of linbox failed:

  ../build-aux/test-driver: line 107: 16085 Illegal instruction "$@" > 
$log_file 2>&1
  FAIL: test-cra
  [...]
  ../build-aux/test-driver: line 107: 16135 Illegal instruction "$@" > 
$log_file 2>&1
  FAIL: test-charpoly

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: givaro
Source-Version: 4.0.2-4

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

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

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

Debian distribution maintenance software
pp.
Doug Torrance  (supplier of updated givaro 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: Tue, 29 Nov 2016 11:01:05 -0500
Source: givaro
Binary: libgivaro-dev libgivaro9 libgivaro-doc givaro-user-doc givaro-dev-doc
Architecture: source all amd64
Version: 4.0.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Description:
 givaro-dev-doc - Developer Documentation for Givaro (obsolete)
 givaro-user-doc - User Documentation for Givaro (obsolete)
 libgivaro-dev - arithmetic and algebraic computations - development files
 libgivaro-doc - Documentation for Givaro
 libgivaro9 - arithmetic and algebraic computations
Closes: 840458
Changes:
 givaro (4.0.2-4) unstable; urgency=medium
 .
   [ Doug Torrance ]
   * debian/rules
 - Add --disable-simd to override_dh_auto_configure target; build without
   vectorized instructions, which are not available on all processors
   (Closes: #840458).
 .
   [ Tobias Hansen ]
   * debian/rules
 - Use flag -ffloat-store on i386, since --disable-simd causes a similar
   test failure as previously on mips64el and s390x.
Checksums-Sha1:
 ef0ae4326973375f2ad3b1521c5fbb61fc69e3e4 2432 givaro_4.0.2-4.dsc
 a8dd9007fc1fdb6b6ccde58e40b52a4d985dff0f 16196 givaro_4.0.2-4.debian.tar.xz
 6aa519e68e24988afe12e79d13cf459e3052dbb9 12688 givaro-dev-doc_4.0.2-4_all.deb
 9a9f3a983c393056e9c628b4b6345887b08466a1 12710 givaro-user-doc_4.0.2-4_all.deb
 cbd4b4fcf4ad27d54805fad8e9066dd5f91639f1 9327 givaro_4.0.2-4_amd64.buildinfo
 71ff6a644fb4b01624d1d3302073c36623e3044e 301788 libgivaro-dev_4.0.2-4_amd64.deb
 a92294f1b29b98615c07b596aaad0994f03fe7f9 2543194 libgivaro-doc_4.0.2-4_all.deb
 4388d71ca724b15ddbd6bde460cfa11172f9e56b 744482 
libgivaro9-dbgsym_4.0.2-4_amd64.deb
 b27f089d4c4b56b611eabb1c619a5e38b0912ebe 73392 libgivaro9_4.0.2-4_amd64.deb
Checksums-Sha256:
 e6b8f64db327bbb588078f8331af48dc7c3c8b61b20148bb408a13c92dbadd0b 2432 
givaro_4.0.2-4.dsc
 56ae9e05b2d621867570a8a2d47f1eb531c0a96838f0d208ed802f643a2eb247 16196 
givaro_4.0.2-4.debian.tar.xz
 92a96dffc89d6b9555e1ea5766faa1ebd4508e541bc8df412315590f761fc9e5 12688 
givaro-dev-doc_4.0.2-4_all.deb
 92eb67e35b7b273e6a08b033dc76143f6efac931ec7d2e1992d12f82494a 12710 
givaro-user-doc_4.0.2-4_all.deb
 cec4f2bd6a3768dca54cc75e4c045e512367a8ca52638c6dbcf955c33bcae1c9 9327 
givaro_4.0.2-4_amd64.buildinfo
 d8b2e39d44d532cb875eb9dde308a48922cec08ea5a5b13770a5289a9615215e 301788 
libgivaro-dev_4.0.2-4_amd64.deb
 126c2ac89360a6575fcef7fff1434b8008c0e21a00377dd8f273099b5b0e7936 2543194 
libgivaro-doc_4.0.2-4_all.deb
 4324e7bd818f633f07d5235fb6d117e1633fe0b92c0a8d6d8a2444f67e59a762 744482 

Bug#846144: liferea: FTBFS randomly (build hangs)

[Santiago Vila]

On Tue, Nov 29, 2016 at 09:56:08PM +0100, Paul Gevers wrote:
> Control: tags -1 help
> 
> Hi Santiago,
> 
> On 28-11-16 18:04, Santiago Vila wrote:
> > I tried to build this package in stretch with "dpkg-buildpackage -A"
> > (which is what the "Arch: all" autobuilder would do to build it)
> 
> As a data point, I always upload source-only when allowed, the buildds
> have always build the all package in one go. So I am curious to learn
> what the difference is between your build daemons and the official ones.

There is not necessarily a difference. Packages break all the time
when any of their build-dependencies change behaviour slightly.

The official build daemons only build packages once, when they are uploaded,
and I build packages all the time.

So a successful build log of an upload made 44 days ago does not mean
the package has to build ok today.

There is also the random factor. Autobuilders build packages once.
When packages fail randomly, as in this case, nobody notices about
that if the autobuilders were lucky for that particular time.

But if a package only builds successfully with probability p < 1,
chances are that it will fail in my autobuilder some day.

> > If (after trying many times, as it's random) you could not reproduce
> > this using sbuild on a single CPU virtual machine (as I did), please do
> > not downgrade or mark as unreproducible, I would then consider giving
> > you access to a virtual machine on which I can reproduce it so that
> > you can as well. (In such case, please contact me off-list for details).
> 
> Do you think it may help to disable parallelism?

Do you mean, for the purposes of reproducing the error, or for the
purposes of avoiding it? :-)

I have this in my .sbuildrc

$ENV{'DEB_BUILD_OPTIONS'} = 'parallel=1';

to disable parallelism. I do this because I'm interested to know the
time it takes to build a given package, so the figures I get are always
in the "same scale" regardless of having a multi-core machine or not.

So if you want to build the packages as closely as I do (to reproduce
the bug), I would try using a single CPU and disabling parallelism that way.

> Apart from that I have
> no idea what I could test. I already had a hard time to come up with the
> work around for /usr/bin/g-ir-scanner failing without an x-session (bug
> 839397)¹. It seems introspection isn't very robust lately.
> 
> My laptop has 2 CPU's but I've never used sbuild before.

Try sbuild. It's not difficult to setup if you follow the README.

Thanks.

Bug#846270: marked as done (fakechroot: preload library not found, aborting.)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 21:21:25 +
with message-id 
and subject line Bug#846270: fixed in fakechroot 2.19-3
has caused the Debian Bug report #846270,
regarding fakechroot: preload library not found, aborting.
to be marked as done.

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

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


-- 
846270: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fakechroot
Version: 2.19-2
Severity: grave
Justification: renders package unusable

servo:~ 0$ fakechroot true
fakechroot: preload library not found, aborting.
servo:~ 1$

I think that pretty much covers it.  Renders the debirf package unusable.

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

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

Versions of packages fakechroot depends on:
ii  libfakechroot  2.19-2

fakechroot recommends no packages.

fakechroot suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fakechroot
Source-Version: 2.19-3

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

Debian distribution maintenance software
pp.
Piotr Roszatycki  (supplier of updated fakechroot 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: Tue, 29 Nov 2016 21:05:31 +0100
Source: fakechroot
Binary: fakechroot libfakechroot
Architecture: source all amd64
Version: 2.19-3
Distribution: unstable
Urgency: high
Maintainer: Piotr Roszatycki 
Changed-By: Piotr Roszatycki 
Description:
 fakechroot - gives a fake chroot environment - utilities
 libfakechroot - gives a fake chroot environment - runtime
Closes: 846270
Changes:
 fakechroot (2.19-3) unstable; urgency=high
 .
   * Correct autoconf variables for configure. The paths should be
 compatible with non-symlinked /bin directory. Closes: #846270.
Checksums-Sha1:
 f05784c729356690134aa3d87fd109255cf1a901 2021 fakechroot_2.19-3.dsc
 83281c45b3ff4ac4caa569bed2fb4e8714234bfd 9160 fakechroot_2.19-3.debian.tar.xz
 f693648c62a71cdd89f5694c5988821aa8463bd0 29046 fakechroot_2.19-3_all.deb
 f4dd0a213f50bfa12a1c1e8ee001dd9eb3629607 5361 fakechroot_2.19-3_amd64.buildinfo
 621e272acd618b34dbd8d424b109ac3310adf380 120162 
libfakechroot-dbgsym_2.19-3_amd64.deb
 d4018cf38cf5e0413900df5314bdd39a572710da 44024 libfakechroot_2.19-3_amd64.deb
Checksums-Sha256:
 5e5135a1c9d600015a642b375fd52d811e36ca61456baeed762fe7c03ff2c769 2021 
fakechroot_2.19-3.dsc
 af1f47c9477107b29b1810719d0480192fcfd53a69b91aa7df4ea224b92e823b 9160 
fakechroot_2.19-3.debian.tar.xz
 5941d5c8671bcf78fcb5dbc35eeff12dacc546e5bab1a4929e2f7f9404d85778 29046 
fakechroot_2.19-3_all.deb
 94914f2d9411e1cafdfcc115d3d5248aaf1c8b69c0ca6af8490433cf32e65326 5361 
fakechroot_2.19-3_amd64.buildinfo
 8c13e451571630d058464851edf05402833263355c13d082acc2e4a9aba1c7c2 120162 
libfakechroot-dbgsym_2.19-3_amd64.deb
 08ef5f9f3cd39e083e4ff77b311429cc8db3e552a5f2b3e0e5830478c482d706 44024 
libfakechroot_2.19-3_amd64.deb
Files:
 bef1b2066c19f85ea49d83a636e1da3a 2021 utils optional fakechroot_2.19-3.dsc
 e0b3678291cd061160cee8dea0ffae2d 9160 utils optional 
fakechroot_2.19-3.debian.tar.xz
 31baabfe509f1255787c1380c526f253 29046 utils optional fakechroot_2.19-3_all.deb
 2cb1e54dcae177d2aedab2caa97fd124 5361 utils optional 
fakechroot_2.19-3_amd64.buildinfo
 cac8e5f632fbdcf278793cef3ff7fa3c 120162 debug extra 
libfakechroot-dbgsym_2.19-3_amd64.deb
 418fc017506d679e73539cd363a7836e 44024 libs optional 
libfakechroot_2.19-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEEsz+SLrYKbvWv/49VmIX88Q5XJwFAlg95csSHGRleHRlckBk
ZWJpYW4ub3JnAAoJEFZiF/PEOVyc72QQAJtypy1f/0Miu4+JcM2gTx3JQaF1HtWU

Bug#844800: marked as done (alljoyn-core-1509: FTBFS: common/crypto/openssl/CryptoAES.cc:286:92: error: 'AES_ctr128_encrypt' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 21:19:21 +
with message-id 
and subject line Bug#844800: fixed in alljoyn-core-1509 15.09a-5
has caused the Debian Bug report #844800,
regarding alljoyn-core-1509: FTBFS: common/crypto/openssl/CryptoAES.cc:286:92: 
error: 'AES_ctr128_encrypt' was not declared in this scope
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.)


-- 
844800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alljoyn-core-1509
Version: 15.09a-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):
> g++ -o build/linux/x86_64/release/obj/common/crypto/CryptoAES.o -c -std=c++11 
> -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
> -fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
> -fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
> -Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC -DNDEBUG -DROUTER 
> -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
> -Ibuild/linux/x86_64/release/dist/cpp/inc 
> -Ibuild/linux/x86_64/release/dist/c/inc 
> -Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
> -Icommon/crypto -Ibuild/linux/x86_64/release/dist/cpp/inc 
> common/crypto/openssl/CryptoAES.cc
> common/crypto/openssl/CryptoAES.cc: In member function 'QStatus 
> qcc::Crypto_AES::Encrypt_CCM(const void*, void*, size_t&, const 
> qcc::KeyBlob&, const void*, size_t, uint8_t)':
> common/crypto/openssl/CryptoAES.cc:286:92: error: 'AES_ctr128_encrypt' was 
> not declared in this scope
>  AES_ctr128_encrypt(T.data, U.data, 16, >key, ivec.data, 
> ecount_buf.data, );
>   
>   ^
> common/crypto/openssl/CryptoAES.cc: In member function 'QStatus 
> qcc::Crypto_AES::Decrypt_CCM(const void*, void*, size_t&, const 
> qcc::KeyBlob&, const void*, size_t, uint8_t)':
> common/crypto/openssl/CryptoAES.cc:339:104: error: 'AES_ctr128_encrypt' was 
> not declared in this scope
>  AES_ctr128_encrypt(U.data, T.data, sizeof(T.data), >key, 
> ivec.data, ecount_buf.data, );
>   
>   ^
> scons: *** [build/linux/x86_64/release/obj/common/crypto/CryptoAES.o] Error 1
> scons: building terminated because of errors.
> debian/rules:39: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/alljoyn-core-1509_15.09a-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: alljoyn-core-1509
Source-Version: 15.09a-5

We believe that the bug you reported is fixed in the latest version of
alljoyn-core-1509, 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.
Thorsten Alteholz  (supplier of updated alljoyn-core-1509 
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: Tue, 29 Nov 2016 18:01:37 +0100
Source: alljoyn-core-1509
Binary: liballjoyn1509 liballjoyn-dev-1509 liballjoyn-c1509 
liballjoyn-c-dev-1509 alljoyn-daemon-1509 liballjoyn-common-dev-1509
Architecture: source amd64
Version: 15.09a-5
Distribution: sid
Urgency: medium
Maintainer: Debian IoT Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 alljoyn-daemon-1509 - AllJoyn daemon 

Bug#844838: marked as done (alljoyn-core-1604: FTBFS: common/crypto/openssl/CryptoAES.cc:285:92: error: 'AES_ctr128_encrypt' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 21:19:33 +
with message-id 
and subject line Bug#844838: fixed in alljoyn-core-1604 16.04a-3
has caused the Debian Bug report #844838,
regarding alljoyn-core-1604: FTBFS: common/crypto/openssl/CryptoAES.cc:285:92: 
error: 'AES_ctr128_encrypt' was not declared in this scope
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.)


-- 
844838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alljoyn-core-1604
Version: 16.04a-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):
> g++ -o build/linux/x86_64/release/obj/common/crypto/CryptoAES.o -c -std=c++11 
> -Wall -Werror -pipe -fno-exceptions -fno-strict-aliasing 
> -fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
> -fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
> -Wno-unknown-pragmas -Wunused-parameter -Os -m64 -fPIC -DNDEBUG -DROUTER 
> -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX -D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC 
> -Ibuild/linux/x86_64/release/dist/cpp/inc 
> -Ibuild/linux/x86_64/release/dist/c/inc 
> -Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc 
> -Icommon/crypto -Ibuild/linux/x86_64/release/dist/cpp/inc 
> common/crypto/openssl/CryptoAES.cc
> common/crypto/openssl/CryptoAES.cc: In member function 'QStatus 
> qcc::Crypto_AES::Encrypt_CCM(const void*, void*, size_t&, const 
> qcc::KeyBlob&, const void*, size_t, uint8_t)':
> common/crypto/openssl/CryptoAES.cc:285:92: error: 'AES_ctr128_encrypt' was 
> not declared in this scope
>  AES_ctr128_encrypt(T.data, U.data, 16, >key, ivec.data, 
> ecount_buf.data, );
>   
>   ^
> common/crypto/openssl/CryptoAES.cc: In member function 'QStatus 
> qcc::Crypto_AES::Decrypt_CCM(const void*, void*, size_t&, const 
> qcc::KeyBlob&, const void*, size_t, uint8_t)':
> common/crypto/openssl/CryptoAES.cc:338:104: error: 'AES_ctr128_encrypt' was 
> not declared in this scope
>  AES_ctr128_encrypt(U.data, T.data, sizeof(T.data), >key, 
> ivec.data, ecount_buf.data, );
>   
>   ^
> scons: *** [build/linux/x86_64/release/obj/common/crypto/CryptoAES.o] Error 1
> scons: building terminated because of errors.
> debian/rules:39: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/alljoyn-core-1604_16.04a-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: alljoyn-core-1604
Source-Version: 16.04a-3

We believe that the bug you reported is fixed in the latest version of
alljoyn-core-1604, 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.
Thorsten Alteholz  (supplier of updated alljoyn-core-1604 
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: Tue, 29 Nov 2016 20:01:37 +0100
Source: alljoyn-core-1604
Binary: liballjoyn1604 liballjoyn-dev-1604 liballjoyn-c1604 
liballjoyn-c-dev-1604 alljoyn-daemon-1604 liballjoyn-common-dev-1604
Architecture: source amd64
Version: 16.04a-3
Distribution: sid
Urgency: medium
Maintainer: Debian IoT Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 alljoyn-daemon-1604 - AllJoyn daemon 

Bug#846295: octave: Octave can't find correct library files on installation

[Gary Roach]

Package: octave
Version: 4.0.3-2+b1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

I attempted to install the Octave package on my Debian Stretch system using
both Aptitude and apt-get. Both methods resulted in the same error:

Setting up octave (4.0.3-2+b1) ...
/usr/local/libexec/octave/4.0.0/exec/x86_64-unknown-linux-gnu/octave-gui: 
error
while loading shared libraries: libgl2ps.so.0: cannot open shared object 
file:

No such file or directory
dpkg: error processing package octave (--configure):

The .deb file seems to be looking for the wrong version of the lib file. The
newer version is libgl2ps.so.1

I set up a soft link from the old version to the new, re-ran the install and
now get a new error that the installer can't find libcholmod.so.2.1.2.

Maybe the .deb file is completely out of date.

Gary Roach




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

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

Versions of packages octave depends on:
ii  libamd2  1:4.5.3-2
ii  libarpack2   3.4.0-1+b1
ii  libasound2   1.1.2-1
ii  libatlas3-base [liblapack.so.3]  3.10.3-1
ii  libblas3 [libblas.so.3]  3.6.1-2
ii  libc62.24-5
ii  libcamd2 1:4.5.3-2
ii  libccolamd2  1:4.5.3-2
ii  libcholmod3  1:4.5.3-2
ii  libcolamd2   1:4.5.3-2
ii  libcxsparse3 1:4.5.3-2
ii  libfftw3-double3 3.3.5-1
ii  libfftw3-single3 3.3.5-1
ii  libfltk-gl1.31.3.3-8+b1
ii  libfltk1.3   1.3.3-8+b1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.2.0-13
ii  libgl1-mesa-glx [libgl1] 12.0.4-2
ii  libglpk404.60-2+b1
ii  libglu1-mesa [libglu1]   9.0.0-2.1
ii  libgomp1 6.2.0-13
ii  liblapack3 [liblapack.so.3]  3.6.1-2
ii  liboctave3v5 4.0.3-2+b1
ii  libosmesa6   12.0.4-2
ii  libportaudio219+svn20140130-1.1
ii  libqhull72015.2-1
ii  libqrupdate1 1.1.2-2
ii  libqscintilla2-12v5  2.9.3+dfsg-4
ii  libqt4-network   4:4.8.7+dfsg-11
ii  libqt4-opengl4:4.8.7+dfsg-11
ii  libqtcore4   4:4.8.7+dfsg-11
ii  libqtgui44:4.8.7+dfsg-11
ii  libsndfile1  1.0.27-1
ii  libstdc++6   6.2.0-13
ii  libumfpack5  1:4.5.3-2
ii  libx11-6 2:1.6.3-1
ii  octave-common4.0.3-2
ii  texinfo  6.3.0.dfsg.1-1+b1

Versions of packages octave recommends:
ii  default-jre-headless  2:1.8-57
ii  gnuplot-x11   5.0.5+dfsg1-4
ii  libatlas3-base3.10.3-1
ii  octave-info   4.0.3-2
ii  pstoedit  3.70-3+b1

Versions of packages octave suggests:
pn  octave-doc  
pn  octave-htmldoc  

-- no debconf information

Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[Julian Taylor]

On 29.11.2016 15:10, Tobias Hansen wrote:
> On Thu, 3 Nov 2016 20:25:23 +0100 Julian Taylor
>  wrote:
>> On 03.11.2016 20:17, Sandro Tosi wrote:
 Looks like your last upload fixed the build on most architectures. However 
 the
 package still failed to build on arm64.

 https://buildd.debian.org/status/package.php?p=pyzmq
>>>
>>> Hey Julian, do you have time to look at the failures in the
>>> https://buildd.debian.org/status/package.php?p=pyzmq ? it looks like
>>> upstream released 16.0.0 so it might worth a shot packaging it to see
>>> if that solves them. thanks!!
>>>
>>
>> I have packaged it though the tests are also unreliable on x86, still
>> needs to be looked at.
>>
> 
> Could it be that zeromq3 4.2.0 (which is now in unstable) helps?
> 
> It would be nice if this could be fixed before the soft freeze on
> January 5. We are trying to get sagemath (currently not uploaded yet) to
> migrate to testing before that date and it could become a problem to
> have different versions of pyzmq (and zeromq3) in unstable and testing.
> 


No luck still hangs sometimes and I still had no time to properly look
into it :/
Also the decision to not provide aligned even 4 byte aligned payload
buffers in zmq 4.2 as indicated in #844479 is going to be a minefield in
our arches without unaligned access ...

Bug#845362: marked as pending

[Sebastian Ramacher]

tag 845362 pending
thanks

Hello,

Bug #845362 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=pkg-multimedia/libquicktime.git;a=commitdiff;h=b1c9046

---
commit b1c9046859eac9dedf6a9539e59fde4862d0a55d
Author: Sebastian Ramacher 
Date:   Tue Nov 29 22:06:53 2016 +0100

Finalize changelog

diff --git a/debian/changelog b/debian/changelog
index 82ee55c..13c5676 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+libquicktime (2:1.2.4-9) unstable; urgency=medium
+
+  * debian/control:
+- Bump Standards-Version
+- Remove libschroedinger-dev from B-D. (Closes: #845362)
+  * debian/rules: Pass -Xlqt_ to dh_makeshlibs to ignore plugins when 
generating
+symbol file.
+
+ -- Sebastian Ramacher   Tue, 29 Nov 2016 22:06:34 +0100
+
 libquicktime (2:1.2.4-8) unstable; urgency=medium
 
   * Team upload.

Processed: Bug#845362 marked as pending

[Debian Bug Tracking System]

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

> tag 845362 pending
Bug #845362 [src:libquicktime] libquicktime: removal of libschroedinger
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: found 845241 in 8:6.7.7.10-4

[Debian Bug Tracking System]

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

> found 845241 8:6.7.7.10-4
Bug #845241 {Done: Bastien Roucariès } 
[src:imagemagick] Prevent fault in MSL interpreter
Marked as found in versions imagemagick/8:6.7.7.10-4.
> thanks
Stopping processing here.

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

Processed: Re: Bug#846144: liferea: FTBFS randomly (build hangs)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #846144 [src:liferea] liferea: FTBFS randomly (build hangs)
Added tag(s) help.

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

Bug#846144: liferea: FTBFS randomly (build hangs)

[Paul Gevers]

Control: tags -1 help

Hi Santiago,

On 28-11-16 18:04, Santiago Vila wrote:
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would do to build it)

As a data point, I always upload source-only when allowed, the buildds
have always build the all package in one go. So I am curious to learn
what the difference is between your build daemons and the official ones.

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

Do you think it may help to disable parallelism? Apart from that I have
no idea what I could test. I already had a hard time to come up with the
work around for /usr/bin/g-ir-scanner failing without an x-session (bug
839397)¹. It seems introspection isn't very robust lately.

My laptop has 2 CPU's but I've never used sbuild before.

Paul

¹ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839397



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#828351: inn2: FTBFS with openssl 1.1.0

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #828351 [src:inn2] inn2: FTBFS with openssl 1.1.0
Added tag(s) fixed-upstream and patch.

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

Bug#828351: inn2: FTBFS with openssl 1.1.0

[Sebastian Andrzej Siewior]

control: tags -1 patch fixed-upstream

On 2016-06-27 15:56:40 [+0200], Julien ÉLIE wrote:
> I suggest to release a 2.6.0-3 Debian package containing upstream commits
> 9988 and 10024.  (And, while we're at it, also upstream commit 9986 that
> removes TCP_NODELAY for nnrpd.)
> It will normally permits INN to build against OpenSSL 1.1.0.

This is also what Redhat did except for the TCP_NODELAY thing.
  https://bugzilla.redhat.com/show_bug.cgi?id=1387660

Please find attached a patch against the package which includes the
three three patches mentioned here and was sbuild tested.
Should I NMU it?

Sebastian
From: Sebastian Andrzej Siewior 
Date: Tue, 29 Nov 2016 21:10:31 +0100
Subject: [PATCH] cherry-pick patches for OpenSSL 1.1.0 support and TCP_NODELAY

Signed-off-by: Sebastian Andrzej Siewior 
---
 debian/changelog|  9 +++
 debian/patches/changeset_branches_2.6_10024 | 45 ++
 debian/patches/changeset_branches_2.6_9986  | 82 +
 debian/patches/changeset_branches_2.6_9988  | 95 +
 debian/patches/series   |  3 +
 debian/rules|  1 +
 6 files changed, 235 insertions(+)
 create mode 100644 debian/patches/changeset_branches_2.6_10024
 create mode 100644 debian/patches/changeset_branches_2.6_9986
 create mode 100644 debian/patches/changeset_branches_2.6_9988

diff --git a/debian/changelog b/debian/changelog
index 7985664277f2..73931da6d2af 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+inn2 (2.6.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport upstream fixes to get it built against openssl 1.1.0 and run
+./autogen to get configure script updated (Closes: #828351).
+  * Backport a patch to drop to drop TCP_NODELAY.
+
+ -- Sebastian Andrzej Siewior   Tue, 29 Nov 2016 21:09:07 +0100
+
 inn2 (2.6.0-2) unstable; urgency=medium
 
   * Stop rnews from segfaulting while starting. (Closes: #809774)
diff --git a/debian/patches/changeset_branches_2.6_10024 b/debian/patches/changeset_branches_2.6_10024
new file mode 100644
index ..c0130929576e
--- /dev/null
+++ b/debian/patches/changeset_branches_2.6_10024
@@ -0,0 +1,45 @@
+Description: Fix build with OpenSSL 1.1.0 - a few X509_xxx types are now opaque
+Author: iulius
+Origin: upstream
+
+Check that the current certificate returned by
+X509_STORE_CTX_get_current_cert() is not NULL.  In the switch part,
+err_cert is not NULL though because otherwise the error would have been
+different than X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT.
+
+---
+ nnrpd/tls.c |   15 ++-
+ 1 file changed, 10 insertions(+), 5 deletions(-)
+
+--- a/nnrpd/tls.c
 b/nnrpd/tls.c
+@@ -244,9 +244,13 @@ verify_callback(int ok, X509_STORE_CTX *
+ err = X509_STORE_CTX_get_error(ctx);
+ depth = X509_STORE_CTX_get_error_depth(ctx);
+ 
+-X509_NAME_oneline(X509_get_subject_name(err_cert), buf, sizeof(buf));
+-if ((tls_serveractive) && (tls_loglevel >= 1))
+-  Printf("Peer cert verify depth=%d %s", depth, buf);
++if (err_cert != NULL) {
++X509_NAME_oneline(X509_get_subject_name(err_cert), buf, sizeof(buf));
++if ((tls_serveractive) && (tls_loglevel >= 1)) {
++Printf("Peer cert verify depth=%d %s", depth, buf);
++}
++}
++
+ if (ok==0)
+ {
+   syslog(L_NOTICE, "verify error:num=%d:%s", err,
+@@ -260,9 +264,10 @@ verify_callback(int ok, X509_STORE_CTX *
+ 	verify_error = X509_V_ERR_CERT_CHAIN_TOO_LONG;
+ 	}
+ }
+-switch (ctx->error) {
++
++switch (err) {
+ case X509_V_ERR_UNABLE_TO_GET_ISSUER_CERT:
+-	X509_NAME_oneline(X509_get_issuer_name(ctx->current_cert), buf, sizeof(buf));
++	X509_NAME_oneline(X509_get_issuer_name(err_cert), buf, sizeof(buf));
+ 	syslog(L_NOTICE, "issuer= %s", buf);
+ 	break;
+ case X509_V_ERR_CERT_NOT_YET_VALID:
diff --git a/debian/patches/changeset_branches_2.6_9986 b/debian/patches/changeset_branches_2.6_9986
new file mode 100644
index ..bbabbebd2220
--- /dev/null
+++ b/debian/patches/changeset_branches_2.6_9986
@@ -0,0 +1,82 @@
+Description: nnrpd:  keep TCP_NODELAY only for BSD/OS systems
+Author: iulius
+Origin: upstream
+
+Fixed slow nnrpd responses for a few NNTP commands.  The TCP_NODELAY
+option was unconditionally set whereas only BSD/OS systems needed it.
+Modern networking stacks do not need such tweaks.
+
+Thanks to Christian Mock for having discovered that.
+
+---
+ configure.ac |6 ++
+ doc/pod/news.pod |6 ++
+ nnrpd/nnrpd.c|   11 ---
+ 3 files changed, 20 insertions(+), 3 deletions(-)
+
+--- a/configure.ac
 b/configure.ac
+@@ -203,6 +203,12 @@ dnl (like asprintf) that we use.
+ [Define if compiling on Linux to get prototypes for some functions.])
+ ;;
+ 
++dnl Detect BSD/OS for later use in nnrpd code.
++*-bsdi*)
++

Processed: perlpanel: diff for NMU version 1:0.9.1+cvs20051225-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 817616 + pending
Bug #817616 [src:perlpanel] perlpanel: Removal of debhelper compat 4
Added tag(s) pending.

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

Bug#817616: perlpanel: diff for NMU version 1:0.9.1+cvs20051225-2.1

[Sebastian Ramacher]

Control: tags 817616 + pending

Dear maintainer,

Christoph Biedl has prepared an NMU for perlpanel (versioned as
1:0.9.1+cvs20051225-2.1) and I have uploaded it for him to DELAYED/2. Please
feel free to tell me if I should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -u perlpanel-0.9.1+cvs20051225/debian/compat perlpanel-0.9.1+cvs20051225/debian/compat
--- perlpanel-0.9.1+cvs20051225/debian/compat
+++ perlpanel-0.9.1+cvs20051225/debian/compat
@@ -1 +1 @@
-4
+9
diff -u perlpanel-0.9.1+cvs20051225/debian/changelog perlpanel-0.9.1+cvs20051225/debian/changelog
--- perlpanel-0.9.1+cvs20051225/debian/changelog
+++ perlpanel-0.9.1+cvs20051225/debian/changelog
@@ -1,3 +1,10 @@
+perlpanel (1:0.9.1+cvs20051225-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Raise debhelper compat to 9. Closes: #817616
+
+ -- Christoph Biedl   Wed, 02 Nov 2016 22:47:57 +0100
+
 perlpanel (1:0.9.1+cvs20051225-2) unstable; urgency=low
 
   * Makefile: 
diff -u perlpanel-0.9.1+cvs20051225/debian/control perlpanel-0.9.1+cvs20051225/debian/control
--- perlpanel-0.9.1+cvs20051225/debian/control
+++ perlpanel-0.9.1+cvs20051225/debian/control
@@ -2,7 +2,7 @@
 Section: x11
 Priority: optional
 Maintainer: Marc 'HE' Brockschmidt 
-Build-Depends: debhelper (>= 4), dpatch, gettext, libgtk2-perl, libgtk2-gladexml-perl, libgnome2-wnck-perl, libxml-simple-perl, liblocale-gettext-perl
+Build-Depends: debhelper (>= 9), dpatch, gettext, libgtk2-perl, libgtk2-gladexml-perl, libgnome2-wnck-perl, libxml-simple-perl, liblocale-gettext-perl
 Standards-Version: 3.7.3
 
 Package: perlpanel


signature.asc
Description: PGP signature

Bug#846270: fakechroot: preload library not found, aborting.

[Piotr Roszatycki]

tags 846270 - unreproducible

On Tue, Nov 29, 2016 at 8:33 PM, Jameson Graef Rollins
 wrote:
> + fakechroot_detect='/usr/bin/fakechroot: line 163: /usr/bin/echo: No such 
> file or directory'

Ok thanks,

This bug is appearing on systems which were upgraded from stable to
testing or unstable. It is because for new systems /bin is symlink to
/usr/bin.

I will upload new package with fix very soon.

-- 
Piotr Roszatycki

Processed (with 5 errors): Re: Bug#846270: fakechroot: preload library not found, aborting.

[Debian Bug Tracking System]

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

> tags 846270 - unreproducible
Bug #846270 [fakechroot] fakechroot: preload library not found, aborting.
Removed tag(s) unreproducible.
> On Tue, Nov 29, 2016 at 8:33 PM, Jameson Graef Rollins
Unknown command or malformed arguments to command.
>  wrote:
Unknown command or malformed arguments to command.
> > + fakechroot_detect='/usr/bin/fakechroot: line 163: /usr/bin/echo: No such 
> > file or directory'
Unknown command or malformed arguments to command.
> Ok thanks,
Unknown command or malformed arguments to command.
> This bug is appearing on systems which were upgraded from stable to
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

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

Bug#846270: fakechroot: preload library not found, aborting.

[Jameson Graef Rollins]

On Tue, Nov 29 2016, Piotr Roszatycki  wrote:
> I can't reproduce this bugs. Can you run, ie.:
>
> $ bash -x fakechroot true
>
> please?

servo:~ 0$ bash -x fakechroot true
+ FAKECHROOT_VERSION=2.19
+ '[' '' = true ']'
+ fakechroot_lib=libfakechroot.so
+ fakechroot_paths=no
+ fakechroot_sysconfdir=/etc/fakechroot
+ fakechroot_confdir=
+ fakechroot_environment=
+ fakechroot_bindir=
+ '[' no = no ']'
+ fakechroot_paths=
++ getopt --version
+ fakechroot_getopttest='getopt from util-linux 2.29'
+ case $fakechroot_getopttest in
++ getopt -q -l lib: -l elfloader: -l use-system-libs -l config-dir: -l 
environment: -l bindir: -l version -l help -- +l:d:sc:e:b:vh true
+ fakechroot_opts=' -- '\''true'\'''
+ '[' 0 -ne 0 ']'
+ eval set -- ' -- '\''true'\'''
++ set -- -- true
+ '[' 2 -gt 0 ']'
+ fakechroot_opt=--
+ shift
+ case "$fakechroot_opt" in
+ break
+ '[' -z '' ']'
+ fakechroot_next_cmd true
+ '[' true = fakeroot ']'
+ '[' -n true -a true '!=' -v -a true '!=' -h ']'
++ basename -- true
+ fakechroot_environment=true
+ '[' -n '' ']'
+ fakechroot_paths=
+ fakechroot_lib=libfakechroot.so
++ LD_LIBRARY_PATH=
++ LD_PRELOAD=libfakechroot.so
++ FAKECHROOT_DETECT=1
++ /usr/bin/echo
+ fakechroot_detect='/usr/bin/fakechroot: line 163: /usr/bin/echo: No such file 
or directory'
+ case "$fakechroot_detect" in
+ fakechroot_libfound=no
+ '[' no = no ']'
+ fakechroot_die 'fakechroot: preload library not found, aborting.'
+ echo 'fakechroot: preload library not found, aborting.'
fakechroot: preload library not found, aborting.
+ exit 1
servo:~ 1$ 

> $ LD_LIBRARY_PATH= LD_PRELOAD=libfakechroot.so ldd /bin/true

servo:~ 1$ LD_LIBRARY_PATH= LD_PRELOAD=libfakechroot.so ldd /bin/true
linux-vdso.so.1 (0x7fff7770f000)
libfakechroot.so => 
/usr/lib/x86_64-linux-gnu/fakechroot/libfakechroot.so (0x7f58fb554000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f58fb1b6000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f58fafb2000)
/lib64/ld-linux-x86-64.so.2 (0x55aeea27)
servo:~ 0$ 

hth.

jamie.


signature.asc
Description: PGP signature

Bug#846059: marked as done (libmath-bigint-gmp-perl: FTBFS: Failed 1/12 test programs (t/bigintpm.t))

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 19:34:38 +
with message-id 
and subject line Bug#846059: fixed in libmath-bigint-gmp-perl 1.6001-1
has caused the Debian Bug report #846059,
regarding libmath-bigint-gmp-perl: FTBFS: Failed 1/12 test programs 
(t/bigintpm.t)
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.)


-- 
846059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmath-bigint-gmp-perl
Version: 1.51-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

libmath-bigint-gmp-perl fails to build from source in unstable/amd64:

  […]
  
  Test Summary Report
  ---
  t/bigintpm.t   (Wstat: 1536 Tests: 3913 Failed: 6)
Failed tests:  2541-2546
Non-zero exit status: 6
Parse errors: Bad plan.  You planned 3919 tests but ran 3913.
  Files=12, Tests=6795,  3 wallclock secs ( 0.52 usr  0.05 sys +  2.09 cusr  
0.06 csys =  2.72 CPU)
  Result: FAIL
  Failed 1/12 test programs. 6/6795 subtests failed.
  Makefile:993: recipe for target 'test_dynamic' failed
  make[1]: *** [test_dynamic] Error 255
  make[1]: Leaving directory '«BUILDDIR»'
  dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
  debian/rules:6: recipe for target 'binary' failed
  make: *** [binary] Error 2

  […]

The full build log is attached.


Regards,

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


libmath-bigint-gmp-perl.1.51-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: libmath-bigint-gmp-perl
Source-Version: 1.6001-1

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libmath-bigint-gmp-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Nov 2016 20:15:52 +0100
Source: libmath-bigint-gmp-perl
Binary: libmath-bigint-gmp-perl
Architecture: source
Version: 1.6001-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 846059
Description: 
 libmath-bigint-gmp-perl - module for arbitrary precision arithmetic using GMP
Changes:
 libmath-bigint-gmp-perl (1.6001-1) unstable; urgency=medium
 .
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
   * Remove Jonathan Yu from Uploaders. Thanks for your work!
   * New upstream release.
 Closes: #846059
   * Bump versioned (build) dependency on Math::BigInt.
Checksums-Sha1: 
 8c534cf8fc75970e4313fd1ee8f6cfb0f53acc31 2476 
libmath-bigint-gmp-perl_1.6001-1.dsc
 58737f900ecb60aac9aa62d8a86889a332038cbd 2293530 
libmath-bigint-gmp-perl_1.6001.orig.tar.gz
 df482e6849abf7cf5e8dd8ba362f1e3263912972 4036 
libmath-bigint-gmp-perl_1.6001-1.debian.tar.xz
Checksums-Sha256: 
 bf0524890377a4184634bb601ae913a616461b929a11a56cdcf45037956dee44 2476 
libmath-bigint-gmp-perl_1.6001-1.dsc
 62800b5a5bcefdb7cf709d2f4749801cfab41c3dd536e22fa8515b3662460a40 2293530 
libmath-bigint-gmp-perl_1.6001.orig.tar.gz
 5ec43734b3b1e11f4ee0b715a979232facf7f9c6dcb6beab16853c126ca619cc 4036 
libmath-bigint-gmp-perl_1.6001-1.debian.tar.xz
Files: 
 fd5f0b6b4333ebba1a600b62bc7fd0cb 2476 perl optional 
libmath-bigint-gmp-perl_1.6001-1.dsc
 c1697f2f2aaa640faf56fbd268cd54c1 2293530 perl optional 
libmath-bigint-gmp-perl_1.6001.orig.tar.gz
 086225ae02a9e758331aa8eaa2449baf 4036 perl optional 
libmath-bigint-gmp-perl_1.6001-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlg91BZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ

Bug#828230: marked as done (alljoyn-core-1504: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 19:33:28 +
with message-id 
and subject line Bug#828230: fixed in alljoyn-core-1504 15.04b-8
has caused the Debian Bug report #828230,
regarding alljoyn-core-1504: FTBFS with openssl 1.1.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.)


-- 
828230: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alljoyn-core-1504
Version: 15.04b-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/alljoyn-core-1504_15.04b-1_amd64-20160529-1403

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: alljoyn-core-1504
Source-Version: 15.04b-8

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated alljoyn-core-1504 
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: Tue, 29 Nov 2016 16:01:37 +0100
Source: alljoyn-core-1504
Binary: liballjoyn1504 liballjoyn-dev-1504 liballjoyn-c1504 
liballjoyn-c-dev-1504 alljoyn-daemon-1504 liballjoyn-common-dev-1504
Architecture: source amd64
Version: 15.04b-8
Distribution: sid
Urgency: medium
Maintainer: Debian IoT Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 alljoyn-daemon-1504 - AllJoyn daemon service
 liballjoyn-c-dev-1504 - AllJoyn C development library
 liballjoyn-c1504 - AllJoyn C run-time library
 liballjoyn-common-dev-1504 - AllJoyn common development files
 liballjoyn-dev-1504 - AllJoyn C++ development library
 liballjoyn1504 - AllJoyn C++ run-time library
Closes: 828230
Changes:
 alljoyn-core-1504 (15.04b-8) unstable; urgency=medium
 .
   * move maintenance to debian-iot team
   * debian/rules: activate tests again
   * debian/rules: use builtin crypt (Closes: #828230)
   don't use openssl until hassle has ended
   * debian/control: add dependency for lsb-base (>= 3.0-6)
Checksums-Sha1:
 9222abbb480e82d716a1785914b4d00a2c0cc2d7 2685 alljoyn-core-1504_15.04b-8.dsc
 e738e28633a22c5fac834d226750071320ef4e24 4648648 
alljoyn-core-1504_15.04b.orig.tar.gz
 4f5c1609f04aed254bbb0d6612e24b5714a90b34 11632 
alljoyn-core-1504_15.04b-8.debian.tar.xz
 61ed524fef1ccdd36c4aeca51206f3fc1113b472 6736 
alljoyn-core-1504_15.04b-8_amd64.buildinfo
 cb2b7ec43883dbc0fd6b9e6402862e02ffe641b7 358872 
alljoyn-daemon-1504_15.04b-8_amd64.deb
 393fad2df277a47928a395e5ce2d684e72717b87 245216 
liballjoyn-c-dev-1504_15.04b-8_amd64.deb
 d383ff37c174c338612900e2761c6566cc163825 311522 
liballjoyn-c1504_15.04b-8_amd64.deb
 f0d216a26484289c4029bec3e74ec52641e8a8be 123050 
liballjoyn-common-dev-1504_15.04b-8_amd64.deb
 21ff9bdfd0c15e90fb7fa3591c1bca32ce828179 764370 
liballjoyn-dev-1504_15.04b-8_amd64.deb
 11c0b1c8bf0739d61c3451d5f8357917ce95501a 4184026 
liballjoyn1504_15.04b-8_amd64.deb
Checksums-Sha256:
 b8b389b1df57ce3cd1cccd35f107a070f9080c571286a30a44bccd8ded187eed 2685 
alljoyn-core-1504_15.04b-8.dsc
 0c9813ffdc142a055bd1d27e1eda7bd46c8bff87e0f5a793d0aa5c9c13a09920 4648648 
alljoyn-core-1504_15.04b.orig.tar.gz
 d610d8fc31434b50d79bfa0ca7177fa3dac3d24dedc909a9d9da377370f50998 11632 
alljoyn-core-1504_15.04b-8.debian.tar.xz
 ff44671201d4baba2a750f9728b0faaac8c44f7ae38d2001e93acba94f33d376 6736 

Bug#846088: Alladin License in krb5

[Benjamin Kaduk]

On Mon, Nov 28, 2016 at 10:17:35AM -0500, Sam Hartman wrote:
> To be clear I've contacted upstream off-list and we'll see what we find
> in the next few days.

Upstream has relicensed the file; we can pull that in for the next upload.

-Ben
> 

Processed: Re: Bug#846088: Alladin License in krb5

[Debian Bug Tracking System]

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

> tags 846088 pending
Bug #846088 [krb5] Alladin License in krb5
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#840458: [Debian-science-sagemath] linbox: FTBFS on i386: illegal instruction in test-{cra, charpoly}

[Doug Torrance]

Yes, please do.

On Tue, Nov 29, 2016, 1:52 PM Tobias Hansen  wrote:

> On 11/29/2016 06:01 PM, Tobias Hansen wrote:
> > On 11/29/2016 03:53 PM, Doug Torrance wrote:
> >> Control: reassign -1 src:givaro
> >>
> >> On 11/29/2016 09:58 AM, Tobias Hansen wrote:
> >>> I think I figured out at least the test failures with "Illegal
> >>> instruction" on i386. The problem is that givaro is built using cpu
> >>> extensions that are not allowed.
> >>>
> >>> Jerome figured out in [1] that the problem happens when givaro code is
> >>> called. And sure enough:
> >>>
> >>> objdump -S /usr/lib/i386-linux-gnu/libgivaro.so.9.0.0 | grep
> >>> '\b\(ymm\|zmm\|vfm\)'
> >>> 15411:c4 e3 79 6b 8b a4 29 vfmaddsd
> >>> %xmm2,-0x1d65c(%ebx),%xmm0,%xmm1
> >>> 154d1:c4 e3 69 6b 8b ac 29 vfmaddsd
> >>> %xmm0,-0x1d654(%ebx),%xmm2,%xmm1
> >>>
> >>> And in the i386 build logs for givaro there are these flags:
> >>> -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -msse4a -mavx
> >>> -mfma4 -mfpmath=sse
> >>>
> >>> Do you have time in the next days to disable these flags? Otherwise I
> >>> can do it. (I'm not sure if some of these flags (mmx, sse ?) are
> allowed
> >>> on i386 and didn't find that info. Ximin, do you know this?)
> >>
> >> Sure, I can take a look.  I think it should be a simple --disable-simd
> >> in d/rules (we did the same in fflas-ffpack).
> >>
> >> Doug
> >
> > Thanks! I tried building it but now there seems to be an issue similar
> > to [1]:
> >
> > FAIL: test-ringarith
> > 
> >
> > 997167681959697!=997167682008849 failed (at line 123)
> > x y failed !
> > MEDmax failed !
> > FAIL test-ringarith (exit status: 255)
> >
> > And it even fails when setting the flag -ffp-contract=off .
> > Note that now the failure seems to be related to ModularExtended
> > instead of ModularExtended (MEDmax instead of MEFmax in the error
> > message).
> >
> > Best,
> > Tobias
> >
> > [1] https://github.com/linbox-team/givaro/issues/25
>
> Ok, a workaround is to set -ffloat-store (like the Fedora package). I
> pushed this change to the git repo. Can I upload this?
>
> Best,
> Tobias
>

Bug#846270: fakechroot: preload library not found, aborting.

[Piotr Roszatycki]

tags 846270 unreproducible
thanks

Hi.

I can't reproduce this bugs. Can you run, ie.:

$ bash -x fakechroot true

please?

Also:

$ LD_LIBRARY_PATH= LD_PRELOAD=libfakechroot.so ldd /bin/true

would be helpful.

Thanks!

On Tue, Nov 29, 2016 at 7:13 PM, Jameson Graef Rollins
 wrote:
> Package: fakechroot
> Version: 2.19-2
> Severity: grave
> Justification: renders package unusable
>
> servo:~ 0$ fakechroot true
> fakechroot: preload library not found, aborting.
> servo:~ 1$
>
> I think that pretty much covers it.  Renders the debirf package unusable.
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (600, 'testing'), (500, 'stable'), (200, 'unstable'), (101, 
> 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.8.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages fakechroot depends on:
> ii  libfakechroot  2.19-2
>
> fakechroot recommends no packages.
>
> fakechroot suggests no packages.
>
> -- no debconf information



-- 
Piotr Roszatycki

Processed: Re: Bug#846270: fakechroot: preload library not found, aborting.

[Debian Bug Tracking System]

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

> tags 846270 unreproducible
Bug #846270 [fakechroot] fakechroot: preload library not found, aborting.
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#811750: marked as done (FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 19:05:19 +
with message-id 
and subject line Bug#811750: fixed in re 0.1-6.1
has caused the Debian Bug report #811750,
regarding FTBFS with GCC 6: narrowing conversion
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.)


-- 
811750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811750
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: re
Version: 0.1-6
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> make[1]: Entering directory '/<>'
> g++ -fsigned-char -Wno-write-strings -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wl,-z,relro src/re_cmd.c src/ru32call.c src/ru32cp.c 
> src/ru32var.c src/ru32lat.c  src/ru32fi.c src/ru32au.c src/ru32mau.c 
> src/ru32un.c -ore
> src/ru32cp.c:92:1: error: narrowing conversion of '136' from 'int' to 'char' 
> inside { } [-Wnarrowing]
>  };
>  ^
> 
> src/ru32cp.c:92:1: error: narrowing conversion of '152' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '160' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '164' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '144' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '166' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '167' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '169' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '171' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '172' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '173' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '174' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '176' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '177' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '145' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '181' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '182' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '183' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> src/ru32cp.c:92:1: error: narrowing conversion of '187' from 'int' to 'char' 
> inside { } [-Wnarrowing]
> debian/rules:5: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: re
Source-Version: 0.1-6.1

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated re package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Nov 2016 22:58:31 +0500
Source: re
Binary: re
Architecture: source
Version: 0.1-6.1
Distribution: unstable
Urgency: medium
Maintainer: Aigars 

Bug#829181: marked as done (louie: FTBFS: dh_clean: Please specify the compatibility level in debian/compat)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 17:00:23 -0200
with message-id 

and subject line Re: louie: FTBFS: dh_clean: Please specify the compatibility 
level in debian/compat
has caused the Debian Bug report #829181,
regarding louie: FTBFS: dh_clean: Please specify the compatibility level in 
debian/compat
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.)


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

Dear Maintainer,

louie fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  louie
   Version:  1.1-2
   Build architecture:   amd64
   Date: Fri, 01 Jul 2016 10:45:08 +0200
   Hostname: 13e4dbf267c5
   Uname:Linux 13e4dbf267c5 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 
(2016-06-25) x86_64 GNU/Linux
   /etc/timezone:Africa/Johannesburg
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'louie-build-deps' in 
'../louie-build-deps_1.1-2_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package louie-build-deps.
  (Reading database ... 23081 files and directories currently installed.)
  Preparing to unpack louie-build-deps_1.1-2_all.deb ...
  Unpacking louie-build-deps (1.1-2) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
cdbs libexpat1-dev libpython-dev libpython2.7 libpython2.7-dev python-dev
python-setuptools python2.7-dev
  Suggested packages:
python-setuptools-doc
  The following NEW packages will be installed:
cdbs libexpat1-dev libpython-dev libpython2.7 libpython2.7-dev python-dev
python-setuptools python2.7-dev
  0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 29.6 MB of archives.
  After this operation, 46.5 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 cdbs all 0.4.142 
[80.7 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libpython2.7 amd64 
2.7.12-1 [1069 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libexpat1-dev amd64 
2.2.0-1 [128 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libpython2.7-dev 
amd64 2.7.12-1 [27.8 MB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libpython-dev amd64 
2.7.11-2 [19.8 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 python2.7-dev amd64 
2.7.12-1 [282 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 python-dev amd64 
2.7.11-2 [1128 B]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 python-setuptools all 
20.10.1-1.1 [203 kB]
  Fetched 29.6 MB in 0s (57.9 MB/s)
  Selecting previously unselected package cdbs.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23085 files and directories currently 

Bug#846273: ga FTBFS on ppc64el: test failures

[Adrian Bunk]

Source: ga
Version: 5.4~beta~r10636+dfsg-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=ga=ppc64el=5.4~beta~r10636+dfsg-3=1479951299

...
make[5]: Entering directory '/«BUILDDIR»/ga-5.4~beta~r10636+dfsg'
make[6]: Entering directory '/«BUILDDIR»/ga-5.4~beta~r10636+dfsg'
PASS: ma/test-coalesce.x
PASS: ma/test-inquire.x
XFAIL: ma/testf.x
FAIL: global/testing/elempatch.x
PASS: global/testing/getmem.x
PASS: global/testing/mtest.x
FAIL: global/testing/mulmatpatchc.x
FAIL: global/testing/normc.x
PASS: global/testing/ntestc.x
FAIL: global/testing/ntestfc.x
FAIL: global/testing/packc.x
FAIL: global/testing/patch_enumc.x
PASS: global/testing/print.x
E: Caught signal ‘Terminated’: terminating immediately
Makefile:8215: recipe for target 'check-recursive' failed
make[3]: *** [check-recursive] Terminated

Bug#846272: ga FTBFS on !x86 !ppc: error: unknown type name 'PAD_LOCK_T'

[Adrian Bunk]

Source: ga
Version: 5.4~beta~r10636+dfsg-3
Severity: serious

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

...
libtool: compile:  mpicc -DHAVE_CONFIG_H -I. -I./src/devices/sockets 
-I./src/include -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -c src/locks/locks.c  
-fPIC -DPIC -o src/locks/.libs/locks.o
src/locks/locks.c:16:1: error: unknown type name 'PAD_LOCK_T'
 PAD_LOCK_T *_armci_int_mutexes;
 ^~
 ...

Bug#840458: [Debian-science-sagemath] linbox: FTBFS on i386: illegal instruction in test-{cra, charpoly}

[Tobias Hansen]

On 11/29/2016 06:01 PM, Tobias Hansen wrote:
> On 11/29/2016 03:53 PM, Doug Torrance wrote:
>> Control: reassign -1 src:givaro
>>
>> On 11/29/2016 09:58 AM, Tobias Hansen wrote:
>>> I think I figured out at least the test failures with "Illegal
>>> instruction" on i386. The problem is that givaro is built using cpu
>>> extensions that are not allowed.
>>>
>>> Jerome figured out in [1] that the problem happens when givaro code is
>>> called. And sure enough:
>>>
>>> objdump -S /usr/lib/i386-linux-gnu/libgivaro.so.9.0.0 | grep
>>> '\b\(ymm\|zmm\|vfm\)'
>>> 15411:c4 e3 79 6b 8b a4 29 vfmaddsd
>>> %xmm2,-0x1d65c(%ebx),%xmm0,%xmm1
>>> 154d1:c4 e3 69 6b 8b ac 29 vfmaddsd
>>> %xmm0,-0x1d654(%ebx),%xmm2,%xmm1
>>>
>>> And in the i386 build logs for givaro there are these flags:
>>> -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -msse4a -mavx
>>> -mfma4 -mfpmath=sse
>>>
>>> Do you have time in the next days to disable these flags? Otherwise I
>>> can do it. (I'm not sure if some of these flags (mmx, sse ?) are allowed
>>> on i386 and didn't find that info. Ximin, do you know this?)
>>
>> Sure, I can take a look.  I think it should be a simple --disable-simd
>> in d/rules (we did the same in fflas-ffpack).
>>
>> Doug
> 
> Thanks! I tried building it but now there seems to be an issue similar
> to [1]:
> 
> FAIL: test-ringarith
> 
> 
> 997167681959697!=997167682008849 failed (at line 123)
> x y failed !
> MEDmax failed !
> FAIL test-ringarith (exit status: 255)
> 
> And it even fails when setting the flag -ffp-contract=off .
> Note that now the failure seems to be related to ModularExtended
> instead of ModularExtended (MEDmax instead of MEFmax in the error
> message).
> 
> Best,
> Tobias
> 
> [1] https://github.com/linbox-team/givaro/issues/25

Ok, a workaround is to set -ffloat-store (like the Fedora package). I
pushed this change to the git repo. Can I upload this?

Best,
Tobias

Processed: affects 846270

[Debian Bug Tracking System]

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

> affects 846270 + debirf
Bug #846270 [fakechroot] fakechroot: preload library not found, aborting.
Added indication that 846270 affects debirf
> thanks
Stopping processing here.

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

Bug#841704: marked as done (reel: Will FTBFS after March 2017)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 18:35:25 +
with message-id 
and subject line Bug#841704: fixed in reel 0.6.1-2
has caused the Debian Bug report #841704,
regarding reel: Will FTBFS after March 2017
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.)


-- 
841704: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: reel
Version: 0.6.1-1
Severity: serious
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that reel will FTBFS after March 2017 due to pregenerated certificates
that are then used during the tests:

  $ openssl x509 -enddate -noout -in tmp/certs/server.crt notAfter=Mar 14 
12:36:36 2017 GMT

Marking as RC severity as ths is during the stretch or (hopefully not)
sooner.

I would either:

a) Generate the certificates on build. This is the preferable option
   as it also implicitly shows what commands were used to generate
   the certifacates and these options can be modified.

b) Regenerate the certificates so that they expire in, say, 100 years.


 [0] https://reproducible-builds.org/

Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: reel
Source-Version: 0.6.1-2

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

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

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

Debian distribution maintenance software
pp.
Hleb Valoshka <375...@gmail.com> (supplier of updated reel 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: Tue, 29 Nov 2016 16:59:51 +0300
Source: reel
Binary: reel
Architecture: source all
Version: 0.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Hleb Valoshka <375...@gmail.com>
Description:
 reel   - Celluloid::IO-powered HTTP server
Closes: 841704
Changes:
 reel (0.6.1-2) unstable; urgency=medium
 .
   * Add ruby-certificate-authority as build dependency (Closes: #841704)
   * Patch: Put certificates and logs to /tmp
Checksums-Sha1:
 3b516311bf011d303397e6faaf9baa8999c43957 2188 reel_0.6.1-2.dsc
 5c7a493fa718701dd1cddb06dab0a0ecb2d61edd 3380 reel_0.6.1-2.debian.tar.xz
 e7a9e9a06f65fd56e220554ba83a47f2407e784f 20028 reel_0.6.1-2_all.deb
 c3e73f53feea395f342e46663371419b6f39ec93 6441 reel_0.6.1-2_amd64.buildinfo
Checksums-Sha256:
 f402abffd0f3ee5461993f5ecad77dcb37d07d78f8a727e17ac4e0c4d0c56a68 2188 
reel_0.6.1-2.dsc
 24bc5b61ef94719e6ef66c0b2aa24b33bcc2a1a159895a881b2f3b918e2c657b 3380 
reel_0.6.1-2.debian.tar.xz
 e9303732834513ef73a2a4564e22e146c426ee3dcaa8f286cb21bc6a42ccb1c9 20028 
reel_0.6.1-2_all.deb
 e96b1dc0cb56f5be226cec00ea81d2577d917d06590d0685441905be808a9560 6441 
reel_0.6.1-2_amd64.buildinfo
Files:
 2e8f7bc116342454accb56894dd6ddee 2188 ruby optional reel_0.6.1-2.dsc
 58d043fa2e6e5bc60e92be24aa4288a6 3380 ruby optional reel_0.6.1-2.debian.tar.xz
 25eebb9a8ab8325a050a4aa4cd58de01 20028 ruby optional reel_0.6.1-2_all.deb
 94c2577586ef424f19ccfbd0aff7348b 6441 ruby optional 
reel_0.6.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAlg9x6IACgkQ+COicpiD
yXxk4Q/+JNxBLNAfWcEa+izVRtBdfzcxIgEk43hMaI6+hfwFMQqIAuZmd1arc8fe
6yiA1TeqU5O0McuKx6C6SceMt+afolrNIVV5uQHDhNJqw89C4v+M0Q1WCDiirth/
w5diindwkViEaXzyz8xkCzR2i2ENaHqSUIbN0KH+xa/eAZ70iD3fx6LnWlFgb3i5
gBv6mwBwjN/Q+qYUVWdwB1Ffj8tTpbCvqaioPyl99dC4Fvp4OrborvU7RgVOQdWa
ykHJLwJNFr2Q5uvqDKlGY1CRI8zYxjx+gOL55UPUQqwBNd6yv5d9kYKZjnceeCaz
I+PVj3RRwjh+dGOzlGoTv+G/lxvy6FQvJq6FbmJq/OlejoFZmPgQ6GlZdkNX2RNg
wJ/OKrlkl/GTe9irj0TRKP+1YuoUxbLR7Ze/O10oHnkamOggXhI3CIPq7dJk/aYk
szfLCL/P/kzas/OwY7aleNxDhm0k1bIC3m62IXPpuzexWXb0SsbNyt7zdw+EsTVO
PC9ZD1XqkqMGBLpWQsO53xp/hM7IQXWSHJGlePgRMWWVO8w2n5rwlTEgErwe8SgP
tYbB0cH6oce0iCH+kwXjAgcQcLQd20aqQDUXhn3aRyU4TDnq+caQgNMuumQZtyK6

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

[Andreas Tille]

On Tue, Nov 29, 2016 at 05:52:01PM +, Holger Levsen wrote:
> I'm sorry about not being able to reply right now. Gotta catch another
> train in 30 or 90min…
> 
> (I peeked into your replies very briefly and saw that I cannot reply quickly…)

OK, take your time, have a nice travel - but please delay your planed
NMU until we can *really* discuss the issue.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#846270: fakechroot: preload library not found, aborting.

[Jameson Graef Rollins]

Package: fakechroot
Version: 2.19-2
Severity: grave
Justification: renders package unusable

servo:~ 0$ fakechroot true
fakechroot: preload library not found, aborting.
servo:~ 1$

I think that pretty much covers it.  Renders the debirf package unusable.

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

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

Versions of packages fakechroot depends on:
ii  libfakechroot  2.19-2

fakechroot recommends no packages.

fakechroot suggests no packages.

-- no debconf information

Bug#840458: linbox: FTBFS on i386: illegal instruction in test-{cra,charpoly}

[Adrian Bunk]

On Tue, Nov 29, 2016 at 02:58:53PM +, Tobias Hansen wrote:
>...
> (I'm not sure if some of these flags (mmx, sse ?) are allowed
> on i386 and didn't find that info. Ximin, do you know this?)

None of these is allowed on i386.

The baseline for i386 in stretch is the Pentium Pro,
that has neither MMX nor SSE.

Please also double-check the compiler flags used on amd64:
MMX and SSE/SSE2 are allowed (and enabled by default) there,
but no more recent SSE versions.

Except when the software uses autodetection for features at runtime,
it is usually a bad idea if there is any kind of hw feature compiler
flag setting when building a Debian package.

> Best,
> Tobias
>...

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#840458: linbox: FTBFS on i386: illegal instruction in test-{cra,charpoly}

[Tobias Hansen]

On 11/29/2016 03:53 PM, Doug Torrance wrote:
> Control: reassign -1 src:givaro
> 
> On 11/29/2016 09:58 AM, Tobias Hansen wrote:
>> I think I figured out at least the test failures with "Illegal
>> instruction" on i386. The problem is that givaro is built using cpu
>> extensions that are not allowed.
>>
>> Jerome figured out in [1] that the problem happens when givaro code is
>> called. And sure enough:
>>
>> objdump -S /usr/lib/i386-linux-gnu/libgivaro.so.9.0.0 | grep
>> '\b\(ymm\|zmm\|vfm\)'
>> 15411:c4 e3 79 6b 8b a4 29 vfmaddsd
>> %xmm2,-0x1d65c(%ebx),%xmm0,%xmm1
>> 154d1:c4 e3 69 6b 8b ac 29 vfmaddsd
>> %xmm0,-0x1d654(%ebx),%xmm2,%xmm1
>>
>> And in the i386 build logs for givaro there are these flags:
>> -mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -msse4a -mavx
>> -mfma4 -mfpmath=sse
>>
>> Do you have time in the next days to disable these flags? Otherwise I
>> can do it. (I'm not sure if some of these flags (mmx, sse ?) are allowed
>> on i386 and didn't find that info. Ximin, do you know this?)
> 
> Sure, I can take a look.  I think it should be a simple --disable-simd
> in d/rules (we did the same in fflas-ffpack).
> 
> Doug

Thanks! I tried building it but now there seems to be an issue similar
to [1]:

FAIL: test-ringarith


997167681959697!=997167682008849 failed (at line 123)
x y failed !
MEDmax failed !
FAIL test-ringarith (exit status: 255)

And it even fails when setting the flag -ffp-contract=off .
Note that now the failure seems to be related to ModularExtended
instead of ModularExtended (MEDmax instead of MEFmax in the error
message).

Best,
Tobias

[1] https://github.com/linbox-team/givaro/issues/25

Bug#846266: solid: FTBFS on mipsel and m68k - src/solid/predicate_parser.c: No such file or directory

[James Cowgill]

Source: solid
Version: 5.28.0-1
Severity: serious
Tags: patch

Hi,

So I've had a look at the mips FTBFS, and while I have not been able to
reproduce it there does seem to be a parallel build race going on with
the bison/flex parser generation.

In src/solid/CMakeLists.txt, the parser is generated using bison_target
which uses add_custom_command under the hood. The output file is then
added to the list of sources creating a file-level dependency from the
KF5Solid target to the bison/flex generation command. However, the list
of sources is later used as part of the KF5Solid_static target. Since
file-level dependencies cannot cross between targets, the bison
generation happens twice completely independently as part of the two
targets. If you are very unlucky, the generation in one target can
happen at the same time as the compilation of the parser in the other
target causing a collision.

The attached patch should fix that by putting the generation in a
separate target and manually adding a dependency on it. This forces the
parser to be generated before anything is compiled.

As a side node, there seems to be a bug in CMake 3.7.0 which causes
bison targets to be remade repeatedly, but it looks like it'll be fixed
in 3.7.1.

Thanks,
James
--- a/src/solid/CMakeLists.txt
+++ b/src/solid/CMakeLists.txt
@@ -9,6 +9,7 @@ endif()
 set(solid_LIB_SRCS ${solid_LIB_SRCS} ${solid_QM_LOADER})
 
 add_library(KF5Solid  ${solid_LIB_SRCS})
+add_dependencies(KF5Solid SolidParserTarget)
 target_include_directories(KF5Solid PUBLIC "$")
 generate_export_header(KF5Solid BASE_NAME Solid)
 add_library(KF5::Solid ALIAS KF5Solid)
@@ -87,6 +88,7 @@ install(TARGETS KF5Solid EXPORT KF5SolidTargets ${KF5_INSTALL_TARGETS_DEFAULT_AR
 ### static lib for tests  ###
 
 add_library(KF5Solid_static STATIC ${solid_LIB_SRCS})
+add_dependencies(KF5Solid_static SolidParserTarget)
 set_target_properties(KF5Solid_static PROPERTIES COMPILE_FLAGS -DSOLID_STATIC_DEFINE=1)
 
 target_link_libraries(KF5Solid_static PUBLIC Qt5::Core)
diff --git a/src/solid/devices/CMakeLists.txt b/src/solid/devices/CMakeLists.txt
index b841b54..a020825 100644
--- a/src/solid/devices/CMakeLists.txt
+++ b/src/solid/devices/CMakeLists.txt
@@ -90,6 +90,7 @@ flex_target(SolidLexer
 )
 add_flex_bison_dependency(SolidLexer SolidParser)
 list(APPEND solid_LIB_SRCS ${BISON_SolidParser_OUTPUTS} ${FLEX_SolidLexer_OUTPUTS})
+add_custom_target(SolidParserTarget DEPENDS ${BISON_SolidParser_OUTPUTS} ${FLEX_SolidLexer_OUTPUTS})
 
 include(devices/backends/fakehw/CMakeLists.txt)
 


signature.asc
Description: OpenPGP digital signature

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

[Holger Levsen]

Hi Andreas (& Ole),

On Tue, Nov 29, 2016 at 05:04:31PM +0100, Andreas Tille wrote:
> I wonder what your opinion about the two existing answers might be.  You
> requested a discussion about your proposed patch but you did not took
> part in the last 36 hours.
> 
> I hope you are fine and kind regards

it's been almost 48h since I filed those bugs, of those I've spent >36h
traveling & sleeping & doing important "errands" and then I got busy preparing
a talk about jenkins.debian.net I'll give tomorrow noon, then I'll be
traveling & sleep again & some more important RL duties. I hope to reply on
Thursday… (and *maybe* I'll some time tomorrow…) 

I'm sorry about not being able to reply right now. Gotta catch another
train in 30 or 90min…

(I peeked into your replies very briefly and saw that I cannot reply quickly…)


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#846263: design-design cannot enter stretch due to dependency on bookletimposer

[Adrian Bunk]

Package: design-desktop-graphics
Version: 3.0.3
Severity: serious

debian-design (- to 3.0.3)
Maintainer: Debian Design Team
182 days old (needed 5 days)
Invalidated by dependency
Depends: debian-design bookletimposer (not considered)
Not considered


Likely the solution should be to drop bookletimposer from
the dependencies, see #834007 for details.

Bug#845082: numexpr FTBFS on ppc64el: test failures

[Fernando Seiti Furusato]

X-Debbugs-Cc: gin...@debian.org, bren...@br.ibm.com

On 11/29/2016 03:18 PM, Fernando Seiti Furusato wrote:
> Also I had to consider a ci failure on appveyor, that is why I also
> included a verification for msvc version on the PR.

By the way, it has been merged upstream.



signature.asc
Description: OpenPGP digital signature

Bug#845082: numexpr FTBFS on ppc64el: test failures

[Fernando Seiti Furusato]

Hello.

At first I tried to fix that with round().
Problem is round() returns the same type as the argument so the cast
happens anyway.
I would recommend using the latest version, with llround(), which
returns long long.

Also I had to consider a ci failure on appveyor, that is why I also
included a verification for msvc version on the PR.

Regards.

-- 
Fernando Seiti Furusato
IBM Linux Technology Center




signature.asc
Description: OpenPGP digital signature

Bug#828330: canl-c/gridsite: FTBFS with openssl 1.1.0

[Adrian Bunk]

On Tue, Nov 15, 2016 at 08:22:10PM +0100, Stefan Fritsch wrote:
> Hi again,
> 
> On Saturday, 12 November 2016 07:51:40 CET Stefan Fritsch wrote:
> > If these two packages cannot transition to openssl 1.1.0 before apache2
> > does, I suggest that you build with openssl 1.0.2 explicitly and then
> > downgrade the bugs and unlink them from the transition bug. I don't have
> > much hope that apache2 will transition in time for stretch release.
> 
> since there is now some discussion about this on debian-devel and debian-
> release, maybe you should wait a bit with any actions.

If I understand it correctly, the solution for gridsite is something 
like the patch below for a build dependency on apache2-ssl-dev.

I also left an explicit build dependency on libssl1.0-dev as reminder 
that a Breaks will be required when Apache will change the OpenSSL 
version used for buster.

--- debian/control.old  2016-11-29 16:37:39.0 +
+++ debian/control  2016-11-29 16:37:59.0 +
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Mattias Ellert 
-Build-Depends: debhelper, apache2-dev (>= 2.4), libxml2-dev, 
libcurl4-openssl-dev, libssl-dev, libcanl-c-dev, gsoap, libtool, libtool-bin, 
doxygen, sharutils, dh-apache2, pkg-config
+Build-Depends: debhelper, apache2-dev (>= 2.4), libxml2-dev, 
libcurl4-openssl-dev, libssl1.0-dev | libssl-dev (<< 1.1.0~), apache2-ssl-dev, 
libcanl-c-dev, gsoap, libtool, libtool-bin, doxygen, sharutils, dh-apache2, 
pkg-config
 Standards-Version: 3.9.8
 Homepage: https://wiki.metacentrum.cz/gswiki/
 Vcs-Svn: http://svn.nordugrid.org/repos/packaging/debian/gridsite


> Cheers,
> Stefan

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#846233: vim-command-t is not installable in unstable

[Sam Morris]

On Tue, 2016-11-29 at 14:59 +0200, Adrian Bunk wrote:
> Package: vim-command-t
> Version: 4.0-2.1
> Severity: serious
> 
> The following packages have unmet dependencies:
>  vim-command-t : Depends: libruby2.3 (< 2.3.2) but 2.3.3-1 is to be
> installed

Thanks for this. The package needs a rebuild against the newer ruby2.3-
dev. I've uploaded a new version to mentors.debian.net and requested an
upload from my sponsor. In the meantime, a simple rebuild will fix this
on your own system.

-- 
Sam Morris 
PGP: rsa4096/CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9


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

Processed: limit source to vim-command-t, tagging 846233

[Debian Bug Tracking System]

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

> limit source vim-command-t
Limiting to bugs with field 'source' containing at least one of 'vim-command-t'
Limit currently set to 'source':'vim-command-t'

> tags 846233 + pending
Bug #846233 [vim-command-t] vim-command-t is not installable in unstable
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Merge duplicates and move to correct package

[Debian Bug Tracking System]

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

> reassign 846137 salt-common 2016.3.4+ds-1
Bug #846137 [src:salt-formula-ceilometer] salt-formula-ceilometer: FTBFS: 
Failing test (KeyError: 'VERSION_ID')
Bug reassigned from package 'src:salt-formula-ceilometer' to 'salt-common'.
No longer marked as found in versions salt-formula-ceilometer/2016.4.1-3.
Ignoring request to alter fixed versions of bug #846137 to the same values 
previously set
Bug #846137 [salt-common] salt-formula-ceilometer: FTBFS: Failing test 
(KeyError: 'VERSION_ID')
Marked as found in versions salt/2016.3.4+ds-1.
> reassign 846229 salt-common 2016.3.4+ds-1
Bug #846229 [src:salt-formula-heat] salt-formula-heat: FTBFS (KeyError: 
'VERSION_ID')
Bug reassigned from package 'src:salt-formula-heat' to 'salt-common'.
No longer marked as found in versions salt-formula-heat/2016.4.1-3.
Ignoring request to alter fixed versions of bug #846229 to the same values 
previously set
Bug #846229 [salt-common] salt-formula-heat: FTBFS (KeyError: 'VERSION_ID')
Marked as found in versions salt/2016.3.4+ds-1.
> forcemerge 846137 846229
Bug #846137 [salt-common] salt-formula-ceilometer: FTBFS: Failing test 
(KeyError: 'VERSION_ID')
Bug #846229 [salt-common] salt-formula-heat: FTBFS (KeyError: 'VERSION_ID')
Merged 846137 846229
> affects 846137 src:salt-formula-heat src:salt-formula-ceilometer
Bug #846137 [salt-common] salt-formula-ceilometer: FTBFS: Failing test 
(KeyError: 'VERSION_ID')
Bug #846229 [salt-common] salt-formula-heat: FTBFS (KeyError: 'VERSION_ID')
Added indication that 846137 affects src:salt-formula-heat and 
src:salt-formula-ceilometer
Added indication that 846229 affects src:salt-formula-heat and 
src:salt-formula-ceilometer
> thanks
Stopping processing here.

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

Bug#846137: marked as done (salt-formula-ceilometer: FTBFS: Failing test (KeyError: 'VERSION_ID'))

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 18:22:03 +0200
with message-id <20161129162203.syciugwxrrigt...@bunk.spdns.de>
and subject line This was fixed in 2016.3.4+ds-2
has caused the Debian Bug report #846137,
regarding salt-formula-ceilometer: FTBFS: Failing test (KeyError: 'VERSION_ID')
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.)


-- 
846137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: salt-formula-ceilometer
Version: 2016.4.1-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

salt-formula-ceilometer fails to build from source in unstable/amd64:

  […]

 dh_auto_test
make -j1 test
  make[1]: Entering directory '«BUILDDIR»'
  [ ! -d tests ] || (cd tests; ./run_tests.sh)
  /usr/bin/salt-call
  [ERROR   ] Could not cache minion ID: [Errno 13] Permission denied: 
'/etc/salt/minion_id'
  [WARNING ] Failed to open log file, do you have permission to write to 
/var/log/salt/minion?
  [ERROR   ] An un-handled exception was caught by salt's global exception 
handler:
  KeyError: 'VERSION_ID'
  Traceback (most recent call last):
File "/usr/bin/salt-call", line 11, in 
  salt_call()
File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 372, in 
salt_call
  client.run()
File "/usr/lib/python2.7/dist-packages/salt/cli/call.py", line 48, in run
  caller = salt.cli.caller.Caller.factory(self.config)
File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 79, in 
factory
  return ZeroMQCaller(opts, **kwargs)
File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 274, in 
__init__
  super(ZeroMQCaller, self).__init__(opts)
File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 102, in 
__init__
  self.minion = salt.minion.SMinion(opts)
File "/usr/lib/python2.7/dist-packages/salt/minion.py", line 605, in 
__init__
  opts['grains'] = salt.loader.grains(opts)
File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 705, in grains
  ret = fun()
File "/usr/lib/python2.7/dist-packages/salt/grains/core.py", line 1308, in 
os_data
  if os_release['VERSION_ID'] == "7":
  KeyError: 'VERSION_ID'
  Traceback (most recent call last):
File "/usr/bin/salt-call", line 11, in 
  salt_call()
File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 372, in 
salt_call
  client.run()
File "/usr/lib/python2.7/dist-packages/salt/cli/call.py", line 48, in run
  caller = salt.cli.caller.Caller.factory(self.config)
File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 79, in 
factory
  return ZeroMQCaller(opts, **kwargs)
File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 274, in 
__init__
  super(ZeroMQCaller, self).__init__(opts)
File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 102, in 
__init__
  self.minion = salt.minion.SMinion(opts)
File "/usr/lib/python2.7/dist-packages/salt/minion.py", line 605, in 
__init__
  opts['grains'] = salt.loader.grains(opts)
File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 705, in grains
  ret = fun()
File "/usr/lib/python2.7/dist-packages/salt/grains/core.py", line 1308, in 
os_data
  if os_release['VERSION_ID'] == "7":
  KeyError: 'VERSION_ID'
  [ERROR] Execution of ceilometer.agent_cluster failed
  [ERROR] Execution failed
  Makefile:22: recipe for target 'test' failed
  make[1]: *** [test] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  dh_auto_test: make -j1 test returned exit code 2
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2
  
  
**
  ** Detected network access during build   
  **
  
**
  
   00:00:00.00 IP 3bd46bd9d6c3.40316 > 10.0.1.1.domain: 31921+ ? 
3bd46bd9d6c3.chris-lamb.co.uk. (47)
   00:00:00.031782 IP 10.0.1.1.domain > 3bd46bd9d6c3.40316: 31921 NXDomain* 
0/0/0 (47)
   00:00:00.031961 IP 3bd46bd9d6c3.48787 > 10.0.1.1.domain: 29323+ ? 
3bd46bd9d6c3. (30)

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / 

Bug#846229: marked as done (salt-formula-heat: FTBFS (KeyError: 'VERSION_ID'))

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 18:22:03 +0200
with message-id <20161129162203.syciugwxrrigt...@bunk.spdns.de>
and subject line This was fixed in 2016.3.4+ds-2
has caused the Debian Bug report #846137,
regarding salt-formula-heat: FTBFS (KeyError: 'VERSION_ID')
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.)


-- 
846137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:salt-formula-heat
Version: 2016.4.1-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
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
make install - Install into DESTDIR
make test- Run tests

[... snipped ...]

salt_call()
  File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 372, in 
salt_call
client.run()
  File "/usr/lib/python2.7/dist-packages/salt/cli/call.py", line 48, in run
caller = salt.cli.caller.Caller.factory(self.config)
  File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 79, in 
factory
return ZeroMQCaller(opts, **kwargs)
  File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 274, in 
__init__
super(ZeroMQCaller, self).__init__(opts)
  File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 102, in 
__init__
self.minion = salt.minion.SMinion(opts)
  File "/usr/lib/python2.7/dist-packages/salt/minion.py", line 605, in __init__
opts['grains'] = salt.loader.grains(opts)
  File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 705, in grains
ret = fun()
  File "/usr/lib/python2.7/dist-packages/salt/grains/core.py", line 1308, in 
os_data
if os_release['VERSION_ID'] == "7":
KeyError: 'VERSION_ID'
Traceback (most recent call last):
  File "/usr/bin/salt-call", line 11, in 
salt_call()
  File "/usr/lib/python2.7/dist-packages/salt/scripts.py", line 372, in 
salt_call
client.run()
  File "/usr/lib/python2.7/dist-packages/salt/cli/call.py", line 48, in run
caller = salt.cli.caller.Caller.factory(self.config)
  File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 79, in 
factory
return ZeroMQCaller(opts, **kwargs)
  File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 274, in 
__init__
super(ZeroMQCaller, self).__init__(opts)
  File "/usr/lib/python2.7/dist-packages/salt/cli/caller.py", line 102, in 
__init__
self.minion = salt.minion.SMinion(opts)
  File "/usr/lib/python2.7/dist-packages/salt/minion.py", line 605, in __init__
opts['grains'] = salt.loader.grains(opts)
  File "/usr/lib/python2.7/dist-packages/salt/loader.py", line 705, in grains
ret = fun()
  File "/usr/lib/python2.7/dist-packages/salt/grains/core.py", line 1308, in 
os_data
if os_release['VERSION_ID'] == "7":
KeyError: 'VERSION_ID'
[ERROR] Execution of heat.server_cluster failed
[ERROR] Execution failed
Makefile:22: recipe for target 'test' failed
make[1]: *** [test] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 test returned exit code 2
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


A similar failure may be found here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/salt-formula-heat.html

This is probably triggered by some build-dependency which changed behaviour.
In case it helps, I'm building on stretch and this is my build history:

[ every build before is successful ]
Status: successful  salt-formula-heat_2016.4.1-3_amd64-20161123T092142Z
Status: failed  salt-formula-heat_2016.4.1-3_amd64-20161129T021816Z
[ every build after fails ]

Thanks.
--- End Message ---
--- Begin Message ---
Version: 2016.3.4+ds-2


salt (2016.3.4+ds-2) unstable; urgency=medium

  * Workaround-wrong-oscodename-grain.patch: Fix salt-minion startup issue when
VERSION_ID is not defined in /etc/os-release.

 -- Benjamin Drung 

Bug#846002: blends-tasks must be priority:standard and not make a mess out of tasksel menu

[Andreas Tille]

Hi Holger,

On Sun, Nov 27, 2016 at 05:38:27PM +0100, Holger Levsen wrote:
> I also plan to NMU blends-dev to set blends-tasks back to priority:optional,
> probably on Thursday or Friday this week. (To give some time to discussion, 
> but soon, to not let this slip for to long.)

I wonder what your opinion about the two existing answers might be.  You
requested a discussion about your proposed patch but you did not took
part in the last 36 hours.

I hope you are fine and kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#845105: marked as done (mk-freebsd: bsd.cpu.mk sets -mfloat-abi=softfp on armhf)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 16:03:45 +
with message-id 
and subject line Bug#845105: fixed in freebsd-buildutils 10.3~svn296373-4
has caused the Debian Bug report #845105,
regarding mk-freebsd: bsd.cpu.mk sets -mfloat-abi=softfp on armhf
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.)


-- 
845105: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freebsd-mk
Version: 10.3~svn296373-3
Severity: serious
Control: affects -1 src:ctfutils

https://buildd.debian.org/status/logs.php?pkg=ctfutils=armhf

The root cause of this ctfutils FTBFS is that -mfloat-abi=softfp
is passed to the compiler on armhf, which seems to come from
/usr/share/mk-freebsd/bsd.cpu.mk
--- End Message ---
--- Begin Message ---
Source: freebsd-buildutils
Source-Version: 10.3~svn296373-4

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

Debian distribution maintenance software
pp.
Steven Chamberlain  (supplier of updated freebsd-buildutils 
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: Tue, 29 Nov 2016 15:30:28 +
Source: freebsd-buildutils
Binary: freebsd-buildutils freebsd-mk
Architecture: source all
Version: 10.3~svn296373-4
Distribution: unstable
Urgency: medium
Maintainer: GNU/kFreeBSD Maintainers 
Changed-By: Steven Chamberlain 
Description:
 freebsd-buildutils - Utilities for building FreeBSD sources
 freebsd-mk - FreeBSD makefile templates for bmake
Closes: 845105
Changes:
 freebsd-buildutils (10.3~svn296373-4) unstable; urgency=medium
 .
   * Add Build-Depends: dpkg-dev (>= 1.16.1.1) and use buildflags.mk
 to set CFLAGS, respecting DEB_BUILD_OPTIONS flags such as noopt
   * Enable hardening=+all, which includes PIE, relro and stack protector
   * Use architecture.mk instead of individual calls to dpkg-architecture
   * Create a new MACHINE_ARCH armv6hf for linux armhf and kfreebsd-armhf
 (Closes: #845105)
Checksums-Sha1:
 32a158ba2ac9dedd1a67ccf05d6e0fa64922ea4f 1942 
freebsd-buildutils_10.3~svn296373-4.dsc
 769301828687701e25b072af66a98adb1c2a06a7 24344 
freebsd-buildutils_10.3~svn296373-4.debian.tar.xz
 03f248ba1344d51ccf474e16681301463b2442b2 6773 
freebsd-buildutils_10.3~svn296373-4_all.buildinfo
 5e801416617af461f4bf96ece85571d7affa9cd8 49898 
freebsd-mk_10.3~svn296373-4_all.deb
Checksums-Sha256:
 3ecfaa84d552f7047acec5f02626e729e6e6d18fc10ec06d6686f0af6cbc55af 1942 
freebsd-buildutils_10.3~svn296373-4.dsc
 5fa0b5c27a495e2b1108d22016cdd47f5481f68da6e69ff4201128d8936ecbc8 24344 
freebsd-buildutils_10.3~svn296373-4.debian.tar.xz
 e93e688230f211786c99b5a4e5b0a00aa3c23049cfa11ac0ce27dba10cea4b3a 6773 
freebsd-buildutils_10.3~svn296373-4_all.buildinfo
 6b07b6eacbeeba174fa526f679671fac18b18699ff99d2df1460128439afa8c1 49898 
freebsd-mk_10.3~svn296373-4_all.deb
Files:
 dab7f3557ee4ae0921102f2d39ea186c 1942 devel extra 
freebsd-buildutils_10.3~svn296373-4.dsc
 dcadbe0c389768a907272f024ca741d6 24344 devel extra 
freebsd-buildutils_10.3~svn296373-4.debian.tar.xz
 6643eda3c75d7d47717870ec800d2dfb 6773 devel extra 
freebsd-buildutils_10.3~svn296373-4_all.buildinfo
 97abe705da340ee321cb287323bf5764 49898 devel extra 
freebsd-mk_10.3~svn296373-4_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJYPaKRAAoJELrpzbaMAu5Ta8gH/Ap3rFVEXTiGZyQ1Z3G/eup5
d5DvJsXn8IX99ZtAigchzpRDhSCmlmeViWOcwDsbBuKec41hNKPMUV0Hb5eRRAOr
G9MH1Mk/yfYLnMu9wZET6Rc9zpJ9Mog2dsBdMzf1ZZ3J3f/fo0VkVz5/5gb4Vy1q
yj7lI9PNMTqjj/c0CaSGCWtZb3+QArtN8pztg1LsPQZvvSRLVEHXHRbehSbrLS9s
wNDiSfUKqI+NpoNRdglO2d90JlzVf+ccb4FBPOtnKoKqU1XIERVkRMRKylMDPF9X
M7sjznnZecZLZGhvWH1ePhW041Ms6xnYwi8V9a12bhBgqc+dTOJ9UPNPmXFS4A8=
=Cjf1
-END PGP SIGNATURE End Message ---

Processed: fixed 835542 in 2.5.39-8+deb8u2

[Debian Bug Tracking System]

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

> fixed 835542 2.5.39-8+deb8u2
Bug #835542 [flex] flex: comparison between signed and unsigned integer 
expressions
Marked as fixed in versions flex/2.5.39-8+deb8u2.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> affects 840458 src:linbox
Bug #840458 [src:givaro] linbox: FTBFS on i386: illegal instruction in 
test-{cra,charpoly}
Added indication that 840458 affects src:linbox
>
End of message, stopping processing here.

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

Bug#840458: linbox: FTBFS on i386: illegal instruction in test-{cra,charpoly}

[Doug Torrance]

Control: reassign -1 src:givaro

On 11/29/2016 09:58 AM, Tobias Hansen wrote:

I think I figured out at least the test failures with "Illegal
instruction" on i386. The problem is that givaro is built using cpu
extensions that are not allowed.

Jerome figured out in [1] that the problem happens when givaro code is
called. And sure enough:

objdump -S /usr/lib/i386-linux-gnu/libgivaro.so.9.0.0 | grep
'\b\(ymm\|zmm\|vfm\)'
15411:  c4 e3 79 6b 8b a4 29vfmaddsd 
%xmm2,-0x1d65c(%ebx),%xmm0,%xmm1
154d1:  c4 e3 69 6b 8b ac 29vfmaddsd 
%xmm0,-0x1d654(%ebx),%xmm2,%xmm1

And in the i386 build logs for givaro there are these flags:
-mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -msse4a -mavx
-mfma4 -mfpmath=sse

Do you have time in the next days to disable these flags? Otherwise I
can do it. (I'm not sure if some of these flags (mmx, sse ?) are allowed
on i386 and didn't find that info. Ximin, do you know this?)


Sure, I can take a look.  I think it should be a simple --disable-simd 
in d/rules (we did the same in fflas-ffpack).


Doug

Processed: Re: linbox: FTBFS on i386: illegal instruction in test-{cra,charpoly}

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:givaro
Bug #840458 [src:linbox] linbox: FTBFS on i386: illegal instruction in 
test-{cra,charpoly}
Bug reassigned from package 'src:linbox' to 'src:givaro'.
No longer marked as found in versions linbox/1.4.2-1.
Ignoring request to alter fixed versions of bug #840458 to the same values 
previously set

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

Processed: reopening 835542

[Debian Bug Tracking System]

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

> reopen 835542
Bug #835542 {Done: Salvatore Bonaccorso } [flex] flex: 
comparison between signed and unsigned integer expressions
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions flex/2.5.39-8+deb8u2.
> thanks
Stopping processing here.

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

Bug#844081: Reproducer

[Filip Pytloun]

Hello Christian,

I tried to execute the script during build process.

Here is a couple of outputs from machine where this build is sometimes
failing:

[(0, 9), (0.0001, 9), (0.001, 8), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 10), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 8), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 9), (0.0001, 10), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 9), (0.0001, 9), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 10), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 9), (0.0001, 10), (0.001, 6), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 6), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 9), (0.0001, 9), (0.001, 6), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 9), (0.0001, 10), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 6), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 10), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 10), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 7), (0.01, 0), (0.1, 0), (1, 0)]
[(0, 10), (0.0001, 9), (0.001, 6), (0.01, 0), (0.1, 0), (1, 0)]

Filip

On 2016/11/27 00:38, Christian Geier wrote:
> Hi Filip,
> could you perhaps run the attached file on the test machine (with
> `py.test vdir_test.py`, py.test is needed for the creation of a temp
> directory).
> 
> On my machine the output looks like this:
> [(0, 10), (0.0001, 8), (0.001, 0), (0.01, 0), (0.1, 0), (1, 0)]
> 
> Similar experiments before made me choose the current delay.
> 
> Best regards,
> Christian
> 
> Quoting Filip Pytloun (2016-11-24 00:20:50)
> > On 2016/11/24 00:00, Santiago Vila wrote:
> > > Try using a chroot without union-type=overlay.
> > 
> > Unfortunately it will result in the same error :-/

> import os
> import time
> 
> 
> def get_etag_from_file(f):
> '''Get mtime-based etag from a filepath or file-like object.
> 
> This function will flush/sync the file as much as necessary to obtain a
> correct mtime.
> '''
> stat = os.stat(f)
> mtime = getattr(stat, 'st_mtime_ns', None)
> if mtime is None:
> mtime = stat.st_mtime
> return '{:.9f}'.format(mtime)
> 
> 
> def test_etag(tmpdir):
> fpath = os.path.join(str(tmpdir), 'foo')
> stats = dict()
> for delay in [0, 0.0001, 0.001, 0.01, 0.1, 1]:
> failed = list()
> for one in range(10):
> 
> file_ = open(fpath, 'w')
> file_.write('foo')
> file_.close()
> 
> old_etag = get_etag_from_file(fpath)
> time.sleep(delay)
> 
> file_ = open(fpath, 'w')
> file_.write('bar')
> file_.close()
> 
> new_etag = get_etag_from_file(fpath)
> 
> if old_etag == new_etag:
> failed.append(
> (one, new_etag)
> )
> stats[delay] = len(failed)
> print(sorted(stats.items()))
> assert False  # here to make sure we get the print output via py.test



signature.asc
Description: Digital signature

Bug#846254: compile error with gcc-6

[Thorsten Alteholz]

Package: googletest
Version: 1.8.0-3
Severity: serious
thanks

Hi,

building the alljoyn packages (alljoyn-core-1504, alljoyn-core-1509, 
alljoyn-core-1604) with googletest and gcc-6 gives the following compile 
error. I guess the "#include " jusst needs to be replaced by "#include 
" for gcc-6 now.


Thanks!
 Thorsten



g++ -o build/linux/x86_64/release/obj/about/unittest/gtest-all.o -c -Wall 
-Werror -pipe -std=gnu++0x -fno-exceptions -fno-strict-aliasing 
-fno-asynchronous-unwind-tables -fno-unwind-tables -ffunction-sections 
-fdata-sections -D_FORTIFY_SOURCE=2 -fPIC -Wno-long-long -Wno-deprecated 
-Wno-unknown-pragmas -Os -m64 -fPIC -Wno-deprecated-declarations -DNDEBUG 
-DROUTER -DQCC_OS_GROUP_POSIX -DQCC_OS_LINUX 
-D_GLIBCXX_USE_C99_FP_MACROS_DYNAMIC -DQCC_CPU_X86 -DQCC_CPU_X86_64 
-DGTEST_HAS_RTTI=0 -Ibuild/linux/x86_64/release/dist/cpp/inc 
-Ibuild/linux/x86_64/release/dist/c/inc 
-Ibuild/linux/x86_64/release/dist/cpp/inc/alljoyn -Icommon/inc -I/usr/src/gtest 
-I/usr/src/gtest/include /usr/src/gtest/src/gtest-all.cc

In file included from /usr/src/gtest/src/gtest.cc:38:0,
 from /usr/src/gtest/src/gtest-all.cc:42:
/usr/include/c++/6/math.h:63:12: error: 'std::fpclassify' has not been declared
 using std::fpclassify;
^~
/usr/include/c++/6/math.h:64:12: error: 'std::isfinite' has not been declared
 using std::isfinite;
^~~~
/usr/include/c++/6/math.h:65:12: error: 'std::isinf' has not been declared
 using std::isinf;
^
/usr/include/c++/6/math.h:66:12: error: 'std::isnan' has not been declared
 using std::isnan;
^
/usr/include/c++/6/math.h:67:12: error: 'std::isnormal' has not been declared
 using std::isnormal;
^~~~
/usr/include/c++/6/math.h:68:12: error: 'std::signbit' has not been declared
 using std::signbit;
^~~
/usr/include/c++/6/math.h:69:12: error: 'std::isgreater' has not been declared
 using std::isgreater;
^
/usr/include/c++/6/math.h:70:12: error: 'std::isgreaterequal' has not been 
declared

 using std::isgreaterequal;
^~
/usr/include/c++/6/math.h:71:12: error: 'std::isless' has not been declared
 using std::isless;
^~
/usr/include/c++/6/math.h:72:12: error: 'std::islessequal' has not been 
declared

 using std::islessequal;
^~~
/usr/include/c++/6/math.h:73:12: error: 'std::islessgreater' has not been 
declared

 using std::islessgreater;
^
/usr/include/c++/6/math.h:74:12: error: 'std::isunordered' has not been 
declared

 using std::isunordered;
^~~
scons: *** [build/linux/x86_64/release/obj/about/unittest/gtest-all.o] Error 1
scons: building terminated because of errors.

Bug#846252: kf5-kdepim-apps-libs: FTBFS: recipe for target 'kaddressbookgrantlee/src/CMakeFiles/KF5KaddressbookGrantlee.dir/all' failed

[Chris Lamb]

Source: kf5-kdepim-apps-libs
Version: 4:16.04.2-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

kf5-kdepim-apps-libs fails to build from source in unstable/amd64:

  […]

  [ 94%] Building CXX object 
composereditor-ng/src/CMakeFiles/KF5ComposerEditorNG.dir/KF5ComposerEditorNG_automoc.cpp.o
  cd «BUILDDIR»/obj-x86_64-linux-gnu/composereditor-ng/src && /usr/bin/c++   
-DKCOREADDONS_LIB -DKF5ComposerEditorNG_EXPORTS -DQT_CORE_LIB -DQT_DBUS_LIB 
-DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII 
-DQT_NO_DEBUG -DQT_NO_URL_CAST_FROM_STRING -DQT_PRINTSUPPORT_LIB 
-DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER -DQT_WEBKITWIDGETS_LIB 
-DQT_WEBKIT_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB 
-DTRANSLATION_DOMAIN=\"libcomposereditorng\" -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE 
-I/home/lamby/temp/cdt.20161129152646.Y5NBB7gEQp.db.kf5-kdepim-apps-libs/kf5-kdepim-apps-libs-16.04.2/obj-x86_64-linux-gnu/composereditor-ng/src
 
-I/home/lamby/temp/cdt.20161129152646.Y5NBB7gEQp.db.kf5-kdepim-apps-libs/kf5-kdepim-apps-libs-16.04.2/composereditor-ng/src
 -isystem /usr/include/KF5/KDEWebKit -isystem /usr/include/KF5 -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/KF5/KPIMTextEdit -isystem /usr/include/KF5/KTextWidgets -isystem 
/usr/include/KF5/SonnetUi -isystem /usr/include/KF5/KI18n -isystem 
/usr/include/KF5/SonnetCore -isystem /usr/include/KF5/PimCommon -isystem 
/usr/include/KF5/pimcommon -isystem /usr/include/KF5/KIMAP -isystem 
/usr/include/KF5/KMime -isystem /usr/include/KF5/AkonadiCore -isystem 
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KItemModels -isystem 
/usr/include/KF5/AkonadiWidgets -isystem /usr/include/KF5/KContacts -isystem 
/usr/include/KF5/Akonadi/Contact -isystem /usr/include/KF5/akonadi/contact 
-isystem /usr/include/KF5/KIOCore -isystem /usr/include/KF5/KService -isystem 
/usr/include/KF5/KConfigCore -isystem /usr/include/KF5/KConfigWidgets -isystem 
/usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem 
/usr/include/KF5/KConfigGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml 
-isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/KIOWidgets -isystem 
/usr/include/KF5/KJobWidgets -isystem /usr/include/KF5/KCompletion -isystem 
/usr/include/KF5/KXmlGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport  -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161129152646.Y5NBB7gEQp.db.kf5-kdepim-apps-libs/kf5-kdepim-apps-libs-16.04.2=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-exceptions 
-Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -pedantic -fPIC -fvisibility=hidden 
-fvisibility-inlines-hidden   -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII 
-fPIC -fexceptions -std=gnu++11 -o 
CMakeFiles/KF5ComposerEditorNG.dir/KF5ComposerEditorNG_automoc.cpp.o -c 
/home/lamby/temp/cdt.20161129152646.Y5NBB7gEQp.db.kf5-kdepim-apps-libs/kf5-kdepim-apps-libs-16.04.2/obj-x86_64-linux-gnu/composereditor-ng/src/KF5ComposerEditorNG_automoc.cpp
  make[4]: Leaving directory '«BUILDDIR»/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:565: recipe for target 
'kaddressbookgrantlee/src/CMakeFiles/KF5KaddressbookGrantlee.dir/all' failed
  make[3]: *** 
[kaddressbookgrantlee/src/CMakeFiles/KF5KaddressbookGrantlee.dir/all] Error 2
  make[3]: *** Waiting for unfinished jobs
  [ 95%] Linking CXX shared library libKF5ComposerEditorNG.so
  cd «BUILDDIR»/obj-x86_64-linux-gnu/composereditor-ng/src && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/KF5ComposerEditorNG.dir/link.txt --verbose=1
  /usr/bin/c++  -fPIC -g -O2 -fdebug-prefix-map=«BUILDDIR»=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fno-exceptions 
-Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -pedantic -Wl,--no-undefined -Wl,--fatal-warnings 
-Wl,--enable-new-dtags -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined -shared 
-Wl,-soname,libKF5ComposerEditorNG.so.5 -o libKF5ComposerEditorNG.so.5.2.2 

Bug#828413: marked as done (libssh: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 15:27:01 +
with message-id 
and subject line Bug#828413: fixed in libssh 0.7.3-2
has caused the Debian Bug report #828413,
regarding libssh: FTBFS with openssl 1.1.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.)


-- 
828413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libssh
Version: 0.6.3-4.3
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libssh_0.6.3-4.3_amd64-20160529-1444

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: libssh
Source-Version: 0.7.3-2

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated libssh 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: Tue, 29 Nov 2016 15:58:36 +0100
Source: libssh
Binary: libssh-4 libssh-gcrypt-4 libssh-dev libssh-gcrypt-dev libssh-doc
Architecture: source
Version: 0.7.3-2
Distribution: unstable
Urgency: medium
Maintainer: Laurent Bigonville 
Changed-By: Laurent Bigonville 
Description:
 libssh-4   - tiny C SSH library (OpenSSL flavor)
 libssh-dev - tiny C SSH library. Development files (OpenSSL flavor)
 libssh-doc - tiny C SSH library. Documentation files
 libssh-gcrypt-4 - tiny C SSH library (gcrypt flavor)
 libssh-gcrypt-dev - tiny C SSH library. Development files (gcrypt flavor)
Closes: 828413 845197
Changes:
 libssh (0.7.3-2) unstable; urgency=medium
 .
   * debian/control: Explicitly build against openssl1.0 for now as libssh
 doesn't support 1.1 yet (Closes: #828413, #845197)
   * debian/copyright: Fix short licence for files in the public domain.
   * debian/copyright: More fixes to the copyright file
   * debian/rules: Enable all hardening flags
Checksums-Sha1:
 95eaad7fe597cbae1d5d2296d953b73320c1dd71 1959 libssh_0.7.3-2.dsc
 08a96bba2a32b8c40e1d6560bb5ed9c58957f243 16940 libssh_0.7.3-2.debian.tar.xz
Checksums-Sha256:
 b72824a809186e2ed8a3bd4b7f199c81f7441da41e955a54b1e116408529bd1a 1959 
libssh_0.7.3-2.dsc
 88611ddfb2c84573de142903a883091f9cd4b09479cd4dd4ea8096c32cd44547 16940 
libssh_0.7.3-2.debian.tar.xz
Files:
 6c03ea71c4e6f2581c2c0258958a7427 1959 libs optional libssh_0.7.3-2.dsc
 d98561a05a37ff37558117ad90237143 16940 libs optional 
libssh_0.7.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAlg9l8QRHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9XyaggAiJNPziRUbB1bksQqpYZXaNjn2cFkkU1C
G28x+3NNbxuHQnnlhUrR7rjSQmt/bk+iTi6ewdm6C7QqZ/toXwfSso1V+PTE0UPb
Hbqb9MqvLA7OHA5oZ3khHRPR6zT/5TGaiFuVB3Z259C8FpZiD8fhKMQlTiwWLGKP
TKY9XbDZKptacbv7hd7xhgYLnrHGugs/jLurK+KISZVUnufp93oEPf/u3//LnD+l
+afR+bpxDd+SvpyXX33IXPtbOc9KD8dkMFXW7FeKB2tjP+UoGdUTZ8bX0yfKxyrw
bFvGa/FlYypzHMYibY9d5q16wn6rS3+LYSLI7JviA6V4+w/QNzp4LQ==
=r4uD
-END PGP SIGNATURE End Message ---

Bug#828473: marked as done (opensmtpd: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 15:27:57 +
with message-id 
and subject line Bug#828473: fixed in opensmtpd 6.0.2p1-1
has caused the Debian Bug report #828473,
regarding opensmtpd: FTBFS with openssl 1.1.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.)


-- 
828473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828473
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opensmtpd
Version: 5.7.3p2-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/opensmtpd_5.7.3p2-1_amd64-20160529-1501

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: opensmtpd
Source-Version: 6.0.2p1-1

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

Debian distribution maintenance software
pp.
Ryan Kavanagh  (supplier of updated opensmtpd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 Nov 2016 15:51:28 -0500
Source: opensmtpd
Binary: opensmtpd
Architecture: source amd64
Version: 6.0.2p1-1
Distribution: unstable
Urgency: medium
Maintainer: Ryan Kavanagh 
Changed-By: Ryan Kavanagh 
Description:
 opensmtpd  - secure, reliable, lean, and easy-to configure SMTP server
Closes: 828473 829336 832008 834280
Changes:
 opensmtpd (6.0.2p1-1) unstable; urgency=medium
 .
   * Added Brazilian Portuguese debconf templates translation (Closes: #829336)
   * Added missing dependency on ed (Closes: #834280)
   * Switch B-D to libssl1.0-dev while upstream determines how to best
 transition to OpenSSL 1.1 (Closes: #828473)
   * Fix manpage formatting issues (Closes: #832008)
   * Added missing dependency on lsb-base
   * Add missing build-dependency on zlib1g-dev
   * Add lintian override for spelling mistake in copyright text
Checksums-Sha1:
 490df8ab6d35d748c49e36caebf9212ca3c5a6aa 3094 opensmtpd_6.0.2p1-1.dsc
 386e1115c5cbe91f67ce0854594197846b4bb5d9 695513 opensmtpd_6.0.2p1.orig.tar.gz
 be442d23fc4348ea7b274fc2fbe36465cee97054 24992 
opensmtpd_6.0.2p1-1.debian.tar.xz
 8fba7683d1b3ed279fb45e087e13a08c2134b3be 1064356 
opensmtpd-dbgsym_6.0.2p1-1_amd64.deb
 a887d25841d0d499d900f108f9f90dc8bdc1db47 5382 
opensmtpd_6.0.2p1-1_amd64.buildinfo
 cf65cb14d5d54dd1c3b43b773385296ac837fd6b 267638 opensmtpd_6.0.2p1-1_amd64.deb
Checksums-Sha256:
 dbbc972cdde728b15466d4da73e28da276d71ae39f1437f80dcdf3e16de1220b 3094 
opensmtpd_6.0.2p1-1.dsc
 2af9b6d08784c7e546bf124bb61e311a6aa0c9835507710a76f5c242383190ac 695513 
opensmtpd_6.0.2p1.orig.tar.gz
 5a001429f90bfeb7686253e246cd2a56ee90c4e732382a4aa5751eb727797cf5 24992 
opensmtpd_6.0.2p1-1.debian.tar.xz
 4b2eb3f8efe32acb691ab3f946574e4cb1621f4f1ad35e1a50fdf7bf1d06d402 1064356 
opensmtpd-dbgsym_6.0.2p1-1_amd64.deb
 490fe5274928751f0edc34963ff0a1d06525661b61d4d11e5d3764b2e7880161 5382 
opensmtpd_6.0.2p1-1_amd64.buildinfo
 f3ee3028dae1717928d2e534af72a35861b06ba964c122ab24a8303fcdba314f 267638 
opensmtpd_6.0.2p1-1_amd64.deb
Files:
 0dae34688e2890e384464eeb4f909c88 3094 mail extra opensmtpd_6.0.2p1-1.dsc
 1ebc232624f2e2e31010c810ea0a3b88 695513 mail extra 
opensmtpd_6.0.2p1.orig.tar.gz
 c77e41919adc06e1c3438840182dd908 24992 mail extra 
opensmtpd_6.0.2p1-1.debian.tar.xz
 750d9deb9c3574c4507a93975e48 1064356 debug extra 
opensmtpd-dbgsym_6.0.2p1-1_amd64.deb
 ad4a01ef120b6f618a9e97895eaaee02 5382 mail extra 
opensmtpd_6.0.2p1-1_amd64.buildinfo
 

Bug#844975: marked as done (courier: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 15:22:13 +
with message-id 
and subject line Bug#844975: fixed in courier 0.76.3-2
has caused the Debian Bug report #844975,
regarding courier: FTBFS with openssl 1.1.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.)


-- 
844975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: courier
Version: 0.76.3-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):
> make[3]: Entering directory '/<>'
> make[3]: Nothing to be done for 'install-perms-local'.
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> cd /<>/courier && ./perms.sh > 
> /<>/debian/tmp/install-perms-list.dat
> install -m 644 debian/init-d-script-courier 
> /<>/debian/tmp/usr/lib/courier/
> for man1 in addcr courier-config; do \
> pod2man --center='Debian GNU/Linux Documentation' --release='Debian 
> GNU/Linux '`cat /etc/debian_version` --section=1 debian/${man1}.pod > 
> /<>/debian/tmp/usr/share/man/man1/${man1}.1; \
> done
> for man8 in sharedindexinstall sharedindexsplit webgpg webmaild; do \
> pod2man --center='Debian GNU/Linux Documentation' --release='Debian 
> GNU/Linux '`cat /etc/debian_version` --section=8 debian/${man8}.pod > 
> /<>/debian/tmp/usr/share/man/man8/${man8}.8; \
> done
> rm -f 
> /<>/debian/tmp/usr/lib/courier/sqwebmail/html/en-us/ISPELLDICT
> rm -f /<>/debian/tmp/usr/lib/courier/perlfilter-example.pl
> rm -f /<>/debian/tmp/etc/courier/quotawarnmsg.example
> perl -i -pe 's%^#!\s?perl%#!/usr/bin/perl%' 
> /<>/debian/tmp/usr/share/courier/webadmin/*.pl
> rm -f /<>/debian/tmp/usr/sbin/showmodules
> for f in /<>/debian/tmp/etc/courier/*.dist; do \
>   mv ${f} ${f%.dist}; \
> done
> rm /<>/debian/tmp/etc/courier/*.authpam
> install -d -m 755 /<>/debian/tmp/etc/pam.d
> install -m 644 debian/common-session.pam 
> /<>/debian/tmp/etc/pam.d/esmtp
> install -m 644 debian/common-session.pam 
> /<>/debian/tmp/etc/pam.d/imap
> install -m 644 debian/common-session.pam 
> /<>/debian/tmp/etc/pam.d/pop3
> install -m 644 debian/common-password.pam 
> /<>/debian/tmp/etc/pam.d/webmail
> install -m 644 debian/common-password.pam 
> /<>/debian/tmp/etc/pam.d/calendar
> chmod 644 /<>/debian/tmp/usr/lib/courier/faxmail/init
> rm -f \
>   /<>/debian/tmp/etc/courier/maildrop \
>   /<>/debian/tmp/usr/bin/mailbot \
>   /<>/debian/tmp/usr/bin/maildrop \
>   /<>/debian/tmp/usr/bin/makemime \
>   /<>/debian/tmp/usr/bin/reformail \
>   /<>/debian/tmp/usr/bin/reformime \
>   /<>/debian/tmp/usr/share/man/man1/mailbot.1 \
>   /<>/debian/tmp/usr/share/man/man1/maildrop.1 \
>   /<>/debian/tmp/usr/share/man/man1/makemime.1 \
>   /<>/debian/tmp/usr/share/man/man1/reformail.1 \
>   /<>/debian/tmp/usr/share/man/man1/reformime.1 \
>   /<>/debian/tmp/usr/share/man/man7/maildropex.7 \
>   /<>/debian/tmp/usr/share/man/man7/maildropfilter.7 \
>   /<>/debian/tmp/usr/share/man/man7/maildropgdbm.7
> dh_install --list-missing
>   install -d debian/courier-base//usr/bin
>   cp --reflink=auto -a debian/tmp/usr/bin/courier-config 
> debian/courier-base//usr/bin/
>   cp --reflink=auto -a 
> ./debian/tmp/dh-exec.w3GWHmPn/usr/bin/deliverquota.courier 
> debian/courier-base/usr/bin//
>   cp --reflink=auto -a debian/tmp/usr/bin/maildiracl 
> debian/courier-base//usr/bin/
>   cp --reflink=auto -a debian/tmp/usr/bin/maildirkw 
> debian/courier-base//usr/bin/
>   cp --reflink=auto -a 
> ./debian/tmp/dh-exec.w3GWHmPn/usr/bin/maildirmake.courier 
> debian/courier-base/usr/bin//
>   cp --reflink=auto -a 
> ./debian/tmp/dh-exec.w3GWHmPn/usr/bin/makedat.courier 
> debian/courier-base/usr/bin//
>   cp --reflink=auto -a debian/tmp/usr/bin/testmxlookup 
> debian/courier-base//usr/bin/
>   install -d debian/courier-base//usr/lib/courier/courier
>   cp --reflink=auto -a debian/tmp/usr/lib/courier/courier/makedatprog 
> debian/courier-base//usr/lib/courier/courier/
>   cp --reflink=auto -a debian/tmp/usr/lib/courier/makedat 
> debian/courier-base//usr/lib/courier/
>   cp --reflink=auto -a debian/tmp/usr/lib/courier/perlfilter-ratelimit.pl 
> debian/courier-base//usr/lib/courier/
>   cp --reflink=auto -a debian/tmp/usr/lib/courier/makeimapaccess 
> debian/courier-base//usr/lib/courier/
>   install -d debian/courier-base//usr/sbin
>   cp --reflink=auto -a 

Bug#840458: linbox: FTBFS on i386: illegal instruction in test-{cra,charpoly}

[Tobias Hansen]

Hi Doug,

I think I figured out at least the test failures with "Illegal
instruction" on i386. The problem is that givaro is built using cpu
extensions that are not allowed.

Jerome figured out in [1] that the problem happens when givaro code is
called. And sure enough:

objdump -S /usr/lib/i386-linux-gnu/libgivaro.so.9.0.0 | grep
'\b\(ymm\|zmm\|vfm\)'
   15411:   c4 e3 79 6b 8b a4 29vfmaddsd 
%xmm2,-0x1d65c(%ebx),%xmm0,%xmm1
   154d1:   c4 e3 69 6b 8b ac 29vfmaddsd 
%xmm0,-0x1d654(%ebx),%xmm2,%xmm1

And in the i386 build logs for givaro there are these flags:
-mmmx -mpopcnt -msse -msse2 -msse3 -msse4.1 -msse4.2 -msse4a -mavx
-mfma4 -mfpmath=sse

Do you have time in the next days to disable these flags? Otherwise I
can do it. (I'm not sure if some of these flags (mmx, sse ?) are allowed
on i386 and didn't find that info. Ximin, do you know this?)

Best,
Tobias

[1] https://github.com/linbox-team/linbox/issues/44

On Tue, 11 Oct 2016 14:02:24 -0400 "Aaron M. Ucko"  wrote:
> Source: linbox
> Version: 1.4.2-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> The i386 build of linbox failed:
> 
>   ../build-aux/test-driver: line 107: 16085 Illegal instruction "$@" > 
> $log_file 2>&1
>   FAIL: test-cra
>   [...]
>   ../build-aux/test-driver: line 107: 16135 Illegal instruction "$@" > 
> $log_file 2>&1
>   FAIL: test-charpoly
> 
> Could you please take a look?
> 
> Thanks!
> 
> -- 
> Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
> http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
> 
> 

Bug#820023: marked as done (openjdk-9-jdk,openjdk-9-jdk-headless: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 15:40:56 +0100
with message-id <855754fa-bb1f-08a1-4b9a-96c15d230...@ubuntu.com>
and subject line openjdk-9 file conflicts are fixed
has caused the Debian Bug report #820023,
regarding openjdk-9-jdk,openjdk-9-jdk-headless: error when trying to install 
together
to be marked as done.

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

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


-- 
820023: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-9-jdk,openjdk-9-jdk-headless
Version: 9~b112-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Hi,

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

  Selecting previously unselected package openjdk-9-jdk-headless:amd64.
  Preparing to unpack .../openjdk-9-jdk-headless_9~b112-2_amd64.deb ...
  Unpacking openjdk-9-jdk-headless:amd64 (9~b112-2) ...
  Selecting previously unselected package openjdk-9-jdk:amd64.
  Preparing to unpack .../openjdk-9-jdk_9~b112-2_amd64.deb ...
  Unpacking openjdk-9-jdk:amd64 (9~b112-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/openjdk-9-jdk_9~b112-2_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also in 
package openjdk-9-jdk-headless:amd64 9~b112-2
  Processing triggers for libc-bin (2.22-5) ...
  Processing triggers for systemd (229-3) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/openjdk-9-jdk_9~b112-2_amd64.deb


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

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

  usr/lib/jvm/java-9-openjdk-amd64/include/jawt.h
  usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h

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

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


openjdk-9-jdk=9~b112-2_openjdk-9-jdk-headless=9~b112-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 9~b144-1

the openjdk-9 file conflicts are fixed.--- End Message ---

Bug#832846: marked as done (guacamole-client: FTBFS: Could not resolve dependencies for project org.glyptodon.guacamole:guacamole-common:jar:0.8.0)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 12:18:25 +
with message-id 
and subject line guacamole-client_0.9.9+dfsg-1_amd64.changes ACCEPTED into 
unstable
has caused the Debian Bug report #832846,
regarding guacamole-client: FTBFS: Could not resolve dependencies for project 
org.glyptodon.guacamole:guacamole-common:jar:0.8.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.)


-- 
832846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: guacamole-client
Version: 0.8.3-1.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/«PKGBUILDDIR»'
> dh_auto_build -- install
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/«PKGBUILDDIR» 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/«PKGBUILDDIR»/debian 
> -Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo install -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] guacamole-common
> [INFO] guacamole-ext
> [INFO] guacamole-common-js
> [INFO] guacamole
> [INFO] guacamole-client
> [INFO]
>  
> [INFO] 
> 
> [INFO] Building guacamole-common 0.8.0
> [INFO] 
> 
> [WARNING] The POM for javax.servlet:servlet-api:jar:debian is missing, no 
> dependency information available
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] guacamole-common ... FAILURE [  0.142 
> s]
> [INFO] guacamole-ext .. SKIPPED
> [INFO] guacamole-common-js  SKIPPED
> [INFO] guacamole .. SKIPPED
> [INFO] guacamole-client ... SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 0.281 s
> [INFO] Finished at: 2016-07-28T10:36:20+00:00
> [INFO] Final Memory: 7M/153M
> [INFO] 
> 
> [ERROR] Failed to execute goal on project guacamole-common: Could not resolve 
> dependencies for project org.glyptodon.guacamole:guacamole-common:jar:0.8.0: 
> Cannot access central (https://repo.maven.apache.org/maven2) in offline mode 
> and the artifact javax.servlet:servlet-api:jar:debian has not been downloaded 
> from it before. -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/«PKGBUILDDIR» 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/«PKGBUILDDIR»/debian 
> -Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo install -DskipTests 
> -Dnotimestamp=true -Dlocale=en_US returned exit code 1
> make[1]: *** [override_dh_auto_build] Error 1

The full build log is available from:
   

Bug#816440: marked as done (openjdk-9-jdk: file conflict jawt.h)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 15:40:56 +0100
with message-id <855754fa-bb1f-08a1-4b9a-96c15d230...@ubuntu.com>
and subject line openjdk-9 file conflicts are fixed
has caused the Debian Bug report #816440,
regarding openjdk-9-jdk: file conflict jawt.h
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.)


-- 
816440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-9-jdk
Version: 9~b107-1

Running with a clean experimental chroot, openjdk-9-jdk has a file
conflict with openjdk-9-jdk-headless (9~b107-1).

Here is the truncated output of "apt-get install openjdk-9-jdk":
Unpacking openjdk-9-jdk:amd64 (9~b107-1) ...
dpkg: error processing archive
/var/cache/apt/archives/openjdk-9-jdk_9~b107-1_amd64.deb (--unpack):
trying to overwrite
'/usr/lib/jvm/java-9-openjdk-amd64/include/jawt.h', which is also in
package openjdk-9-jdk-headless:amd64 9~b107-1

https://piuparts.debian.org/experimental/fail/openjdk-9-jdk_9~b107-1.log

Thanks,
Joe Ferguson
--- End Message ---
--- Begin Message ---
Version: 9~b144-1

the openjdk-9 file conflicts are fixed.--- End Message ---

Bug#818265: Bug#818187: Bug#818265: Bug#818187: zeromq3 migrated without any transition being done

[Tobias Hansen]

On Thu, 3 Nov 2016 20:25:23 +0100 Julian Taylor
 wrote:
> On 03.11.2016 20:17, Sandro Tosi wrote:
> >> Looks like your last upload fixed the build on most architectures. However 
> >> the
> >> package still failed to build on arm64.
> >>
> >> https://buildd.debian.org/status/package.php?p=pyzmq
> > 
> > Hey Julian, do you have time to look at the failures in the
> > https://buildd.debian.org/status/package.php?p=pyzmq ? it looks like
> > upstream released 16.0.0 so it might worth a shot packaging it to see
> > if that solves them. thanks!!
> > 
> 
> I have packaged it though the tests are also unreliable on x86, still
> needs to be looked at.
> 

Could it be that zeromq3 4.2.0 (which is now in unstable) helps?

It would be nice if this could be fixed before the soft freeze on
January 5. We are trying to get sagemath (currently not uploaded yet) to
migrate to testing before that date and it could become a problem to
have different versions of pyzmq (and zeromq3) in unstable and testing.

Best,
Tobias

Bug#844303: marked as done (ncrack: FTBFS: configure:6846: error: ./configure failed for opensshlib)

[Debian Bug Tracking System]

Your message dated Tue, 29 Nov 2016 13:48:50 +
with message-id 
and subject line Bug#844303: fixed in ncrack 0.5-3
has caused the Debian Bug report #844303,
regarding ncrack: FTBFS: configure:6846: error: ./configure failed for 
opensshlib
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.)


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

Dear Maintainer,

ncrack fails to build from source in unstable/amd64:

  […]

  | main ()
  | {
  | #if BYTE_ORDER != BIG_ENDIAN
  |  not big endian
  | #endif
  | 
  |   ;
  |   return 0;
  | }
  configure:5000: result: no
  configure:5019: checking if struct in_addr is a wacky huge structure (some 
Sun boxes)
  configure:5033: gcc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  conftest.c: In function 'main':
  conftest.c:25:20: error: 'struct in_addr' has no member named '_S_un'
   struct in_addr i; i._S_un._S_addr;
  ^
  configure:5033: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME ""
  | #define PACKAGE_TARNAME ""
  | #define PACKAGE_VERSION ""
  | #define PACKAGE_STRING ""
  | #define PACKAGE_BUGREPORT ""
  | #define PACKAGE_URL ""
  | #define STDC_HEADERS 1
  | #define HAVE_SYS_TYPES_H 1
  | #define HAVE_SYS_STAT_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_MEMORY_H 1
  | #define HAVE_STRINGS_H 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_STDINT_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_PWD_H 1
  | #define HAVE_TERMIOS_H 1
  | /* end confdefs.h.  */
  | #include 
  | int
  | main ()
  | {
  | struct in_addr i; i._S_un._S_addr;
  |   ;
  |   return 0;
  | }
  configure:5053: gcc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 conftest.c >&5
  conftest.c: In function 'main':
  conftest.c:26:20: error: 'struct in_addr' has no member named 'S_un'
   struct in_addr i; i.S_un.S_addr;
  ^
  configure:5053: $? = 1
  configure: failed program was:
  | /* confdefs.h */
  | #define PACKAGE_NAME ""
  | #define PACKAGE_TARNAME ""
  | #define PACKAGE_VERSION ""
  | #define PACKAGE_STRING ""
  | #define PACKAGE_BUGREPORT ""
  | #define PACKAGE_URL ""
  | #define STDC_HEADERS 1
  | #define HAVE_SYS_TYPES_H 1
  | #define HAVE_SYS_STAT_H 1
  | #define HAVE_STDLIB_H 1
  | #define HAVE_STRING_H 1
  | #define HAVE_MEMORY_H 1
  | #define HAVE_STRINGS_H 1
  | #define HAVE_INTTYPES_H 1
  | #define HAVE_STDINT_H 1
  | #define HAVE_UNISTD_H 1
  | #define HAVE_PWD_H 1
  | #define HAVE_TERMIOS_H 1
  | /* end confdefs.h.  */
  | #include 
  | #include 
  | int
  | main ()
  | {
  | struct in_addr i; i.S_un.S_addr;
  |   ;
  |   return 0;
  | }
  configure:5061: result: no
  configure:5071: checking for strerror
  configure:5071: gcc -o conftest -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c  >&5
  configure:5071: $? = 0
  configure:5071: result: yes
  configure:5082: checking for signal
  configure:5082: gcc -o conftest -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now conftest.c  >&5
  configure:5082: $? = 0
  configure:5082: result: yes
  configure:5103: checking for type of 6th argument to recvfrom()
  configure:5124: g++ -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161114094640.hgJKENrOpY.db.ncrack/ncrack-0.5=.
 -fstack-protector-strong -Wformat -Werror=format-security -O2 -Wall 
-fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 conftest.cpp >&5
  configure:5124: $? = 0
  configure:5138: result: socklen_t
  configure:5178: checking openssl/ssl.h usability
  configure:5178: gcc -c -g -O2 

Processed: Bug#844303 marked as pending

[Debian Bug Tracking System]

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

> tag 844303 pending
Bug #844303 [src:ncrack] ncrack: FTBFS: configure:6846: error: ./configure 
failed for opensshlib
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#844303: marked as pending

[Raphaël Hertzog]

tag 844303 pending
thanks

Hello,

Bug #844303 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=pkg-security/ncrack.git;a=commitdiff;h=efb1647

---
commit efb164731990e7e476b5fcb8ccb0191bc768f637
Author: Raphaël Hertzog 
Date:   Tue Nov 29 14:35:30 2016 +0100

Build against libssl1.0-dev. Closes: #844303

diff --git a/debian/changelog b/debian/changelog
index e459e03..3108e84 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ncrack (0.5-3) unstable; urgency=medium
+
+  * Team upload.
+  * Build against libssl1.0-dev. Closes: #844303
+
+ -- Raphaël Hertzog   Tue, 29 Nov 2016 14:33:33 +0100
+
 ncrack (0.5-2) unstable; urgency=medium
 
   * Fix FTBS due to missing build-depends on zlib1g-dev (Closes: #835787).

Bug#846234: tortoisehg is not installable in unstable

[Adrian Bunk]

Source: tortoisehg
Version: 3.9-1
Severity: serious

The following packages have unmet dependencies:
 tortoisehg : Depends: mercurial (< 4.0~) but 4.0-1 is to be installed