Bug#852114: marked as done (stenographer-common: fails to install: /usr/sbin/stenokeys: line 71: -r: command not found)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2017 08:46:35 +0100
with message-id <1ed06cd2-8558-4971-97ae-42aa8055b...@debian.org>
and subject line Re: stenographer-common: fails to install: 
/usr/sbin/stenokeys: line 71: -r:  command not found
has caused the Debian Bug report #852114,
regarding stenographer-common: fails to install: /usr/sbin/stenokeys: line 71: 
-r: command not found
to be marked as done.

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

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


-- 
852114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: stenographer-common
Version: 0.0~git20161206.0.66a8e7e-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package stenographer-common.
  (Reading database ... 
(Reading database ... 6653 files and directories currently installed.)
  Preparing to unpack 
.../stenographer-common_0.0~git20161206.0.66a8e7e-2_all.deb ...
  Unpacking stenographer-common (0.0~git20161206.0.66a8e7e-2) ...
  Setting up stenographer-common (0.0~git20161206.0.66a8e7e-2) ...
  Warning: The home dir /var/lib/stenographer you specified can't be accessed: 
No such file or directory
  Adding system user `stenographer' (UID 150) ...
  Adding new group `stenographer' (GID 150) ...
  Adding new user `stenographer' (UID 150) with group `stenographer' ...
  Not creating home directory `/var/lib/stenographer'.
  /usr/sbin/stenokeys: line 71: -r: command not found
  mkdir: cannot create directory '': No such file or directory
  dpkg: error processing package stenographer-common (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   stenographer-common


cheers,

Andreas


stenographer-common_0.0~git20161206.0.66a8e7e-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Hi Andreas,

thanks for reporting this.

> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.

[…]
>   /usr/sbin/stenokeys: line 71: -r: command not found
>   mkdir: cannot create directory '': No such file or directory

Fixed in the latest upload (0.0~git20161206.0.66a8e7e-3). I wanted to confirm 
that piuparts completes successfully now (which it does), so I didn’t close the 
bug from the changelog.

Cheers
Sascha



signature.asc
Description: Message signed with OpenPGP
--- End Message ---

Processed: Re: Bug#852264: gbp buildpackage: doesn't pass options correctly anymore

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #852264 [git-buildpackage] gbp buildpackage: doesn't pass options correctly 
anymore
Severity set to 'important' from 'serious'
> tags -1 unreproducible
Bug #852264 [git-buildpackage] gbp buildpackage: doesn't pass options correctly 
anymore
Added tag(s) unreproducible.

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

Bug#852264: gbp buildpackage: doesn't pass options correctly anymore

[Guido Günther]

control: severity -1 important
control: tags -1 unreproducible

Hi Raphaël,

On Mon, Jan 23, 2017 at 12:18:08AM +0100, Raphaël Halimi wrote:
> Package: git-buildpackage
> Version: 0.8.10
> Severity: serious
> 
> Hi,
> 
> I was trying to backport a package with this command, which used to work
> as expected for as long as I can remember:
> 
> DIST=jessie gbp buildpackage -v0.9-1
> 
> ...but now gbp exits with the message:
> 
> gbp:error: 'BUILDER=pbuilder GIT_PBUILDER_AUTOCONF=no
> /usr/bin/git-pbuilder -v0.9-1' failed: it exited with 2
> 
> A couples of lines above, I can see:
> 
> I: Generating source changes file for original dsc
> dpkg-genchanges: error: unknown option ''-v0.9-1''

I'm not seeing double quotes here. We changed quoting in 80a1c39
(0.8.10) so there might be a bug but I can't reproduce this with
pbuilder 0.227 and 0.228.1.

> Is it the extra pair of quotes that confuse dpkg-genchanges ?
> 
> The bug may come from some other tool in the chain (maybe pbuilder,
> which was recently changed regarding the source package building phase),
> but I'm not sure how to debug 

* Please use reportbug so you supply dependency information
* Please use sane severities

Can you please provide the full command, the full output and the
versions as reported by reportbug?
Cheers,
 -- Guido

Bug#852283: libopenblas-dev: missing on mips64el

[Graham Inggs]

Source: openblas
Version: 0.2.19-1
Severity: serious

Hi Maintainer

Architecture: mips64el was added to libopenblas-base but not libopenblas-dev.
Was this an oversight?

Regards
Graham

Processed: bug 832931 is forwarded to https://jira.mariadb.org/browse/MDEV-11877

[Debian Bug Tracking System]

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

> forwarded 832931 https://jira.mariadb.org/browse/MDEV-11877
Bug #832931 [src:mariadb-10.0] mariadb-10.0: FTBFS on powerpc
Set Bug forwarded-to-address to 'https://jira.mariadb.org/browse/MDEV-11877'.
> thanks
Stopping processing here.

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

Bug#832931: mariadb built successfully on powerpc

[Otto Kekäläinen]

It seems this is still not fixed, so I filed it upstream:
https://jira.mariadb.org/browse/MDEV-11877

Bug#850997: android-platform-tools-base: FTBFS: InstantRunVerifier.java:172: error: method diffList in class InstantRunVerifier cannot be applied to given types;

[Petter Reinholdtsen]

Hi

This RC bug is going to get several android tools thrown out of Stretch.  Is
there any hope to have a fix in place in time to rescue them?

-- 
Happy hacking
Petter Reinholdtsen

Bug#826069: libghemical5v5: breaks color rendering and atom generation in ghemical

[Petter Reinholdtsen]

[Carlo Segre]
> When installed from sid, ghemical will only render in greyscale instead of 
> color.  In addition, building a molecule atom-by-atom is not functional.
> 
> In order to get ghemical working again, I have to revert to the wheezy version
> as there is no version available in jessie.

This RC bug will cause ghemical to be removed from Stretch in a few days.  Is 
there
any hope for a fix in time to rescue it?
-- 
Happy hacking
Petter Reinholdtsen

Processed: your mail

[Debian Bug Tracking System]

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

> found 832931 10.0.29-0+deb8u1
Bug #832931 [src:mariadb-10.0] mariadb-10.0: FTBFS on powerpc
Marked as found in versions mariadb-10.0/10.0.29-0+deb8u1.
>
End of message, stopping processing here.

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

Bug#852259: newlisp: Dynamic library loading is broken

[Sergio Durigan Junior]

On Sunday, January 22 2017, Adrian Bunk wrote:

> I was originally interested in how to get the dependency on
> libmysqlclient18 (which will not be part of stretch) updated,
> but it turned out dynamic library loading in newlisp is broken.
>
>
> (set 'files '(
> "/usr/local/lib/libmysqlclient.so.20.0" ; OpenBSD 4.9
> "/usr/lib/libmysqlclient.so" ; Linux, UNIX
> "/usr/lib/mysql/libmysqlclient.so" ; Linux Fedora
> "/usr/lib64/mysql/libmysqlclient.so" ; Linux Fedora CentOS 6.x
> "/usr/lib/x86_64-linux-gnu/libmysqlclient.so" ; Ubuntu 12.04 LTS
> "/usr/local/mysql/lib/libmysqlclient.so" ; Linux, UNIX
> "/usr/local/mysql/lib/libmysqlclient.dylib" ; MacOS X
> "/usr/lib/libmysqlclient.dylib" ; MacOS X
> ))
>
>
> This looks like a random collection of files that worked for
> random people, not like someone who knows what (s)he is doing
> and where the problems are.

You're right, this came directly from upstream and should have been
adjusted for Debian.  Sorry about that.

> There are several things that wrong with this.
>
> One problem is that the libmysqlclient18 package does not ship
> the .so symlink.
>
> Another is trying to open libraries from /usr/local,
> whenever such libraries exist using them from a Debian
> package only causes problems.

Agreed.  These should not be a problem to fix.

> But the worst is that this cannot work properly with multiarch.
> On my multiarch enabled system I might be using either the
> i386 newlisp package or the amd64 newlisp package.
> I might have both the i386 and the amd64 version of the library
> to load installed.
> As long as newlisp searches in the same paths in both cases,
> it is guaranteed to not find the correct library in at least
> one case.

Hm, I totally understand the problem, but I've been struggling to find a
good solution for this.  Of course, I don't want to search on all the
valid paths for all architectures supported by Debian.  Instead, the
solution would be to check the supported archs on the fly and adjust the
paths accordingly.  What do you think?

> Other libraries used by newlisp have exactly the same problem.

Thanks for the heads up.  I'll fix them as well.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Paul Wise]

On Mon, Jan 23, 2017 at 3:10 AM, Adam Borowski wrote:

> https://github.com/googlei18n/glyphsLib/issues/74

Wasn't aware of glyphsLib/fontmake, thanks for the link!

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#848757: marked as done (ruby-http: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: @socket.connect)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2017 01:20:18 +
with message-id 
and subject line Bug#848757: fixed in ruby-http 1.0.2-4
has caused the Debian Bug report #848757,
regarding ruby-http: FTBFS: ERROR: Test "ruby2.3" failed:   Failure/Error: 
@socket.connect
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.)


-- 
848757: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-http
Version: 1.0.2-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 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):
>   Failure/Error: @socket.connect
> 
>   OpenSSL::SSL::SSLError:
> SSL_connect returned=1 errno=0 state=unknown state: sslv3 alert 
> unsupported certificate
>   # ./lib/http/timeout/null.rb:24:in `connect'
>   # ./lib/http/timeout/null.rb:24:in `connect_ssl'
>   # ./lib/http/timeout/null.rb:33:in `start_tls'
>   # ./lib/http/connection.rb:161:in `start_tls'
>   # ./lib/http/connection.rb:37:in `initialize'
>   # ./lib/http/client.rb:62:in `new'
>   # ./lib/http/client.rb:62:in `perform'
>   # ./lib/http/client.rb:43:in `request'
>   # ./lib/http/chainable.rb:18:in `get'
>   # ./spec/lib/http_spec.rb:138:in `block (5 levels) in '
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `instance_exec'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:254:in `block in run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in `block in 
> with_around_and_singleton_context_hooks'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in `block in 
> with_around_example_hooks'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `block in run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:602:in 
> `run_around_example_hooks_for'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:464:in `run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:453:in 
> `with_around_example_hooks'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:496:in 
> `with_around_and_singleton_context_hooks'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:251:in `run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:627:in `block 
> in run_examples'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in `map'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:623:in 
> `run_examples'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:589:in `run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `block 
> in run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `map'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `block 
> in run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `map'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `block 
> in run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `map'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:590:in `run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (3 
> levels) in run_specs'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `map'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:113:in `block (2 
> levels) in run_specs'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1835:in 
> `with_suite_hooks'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:112:in `block in 
> run_specs'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/reporter.rb:77:in `report'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:111:in `run_specs'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:87:in `run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
>   # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
>   # /usr/bin/rspec:4:in `'
> 
> Top 10 slowest examples (10.03 seconds, 81.5% of total time):
>   HTTP::Client timeouts with a global timeout it resets state when reusing 
> connections does not timeout
> 4.05 seconds ./spec/support/http_handling_shared.rb:98
>   HTTP::Client timeouts with a per operation timeout read of 2.5 does 

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Lisandro Damián Nicanor Pérez Meyer]

On domingo, 22 de enero de 2017 22:07:45 ART Sylvestre Ledru wrote:
> Le 22/01/2017 à 21:02, Lisandro Damián Nicanor Pérez Meyer a écrit :
> > Control: tag -1 patch
> > 
> > I'm attaching a patch based on Rebecca's. I simply used a CMake variable
> > to
> > avoid harcoding a path. Note it's the patch itself and not a debdiff: you
> > need to add it to quilt's series file.
> 
> OK, you haven't pass the arg to LDFLAGS to make sure that libclang or
> liblldb get it,
> is that on purpose?

Actually I thought that that script was kind of global, but I might be wrong. 
I'm about to test this.
 
> > Sylvestre: if you can please try to build this one too. Once built there
> > are two things to test:
> > 
> > - Are the symbols versioned? For this creating a temporary symbols files
> > is
> > enough. Ping me if you don't know how to do this.
> 
> Just libclang is (the C lib).
> I haven't done it for the rest because it is C++ and not commitment
> from upstream on API stability  (on contraire)

Ah, I meant another thing. I normally use symbols files to check if symbols 
are versioned or not, I'm not talking about shipping them, just to check the 
patch worked as intended.



-- 
7: Hay diferencia entre "cortar" un archivo y "borrarlo" o "eliminarlo"
* Depende cuando se "cuelgue" Windows
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#848523: More info

[Lisandro Damián Nicanor Pérez Meyer]

tag 848523 unreproducible moreinfo
thanks

Hi Ben!

For what it's worth I have not seen this behavior. Please tell us which video 
card you have and which drivers are you using for it.

Thanks!

-- 
Never attribute to malice that which is adequately explained by stupidity.
  http://en.wikipedia.org/wiki/Hanlon's_razor

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Processed: More info

[Debian Bug Tracking System]

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

> tag 848523 unreproducible moreinfo
Bug #848523 [kwin-x11] kwin-x11: Fails to start
Added tag(s) moreinfo and unreproducible.
> thanks
Stopping processing here.

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

Bug#831244: marked as done (ruby-eventmachine: FTBFS: Build hangs minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2017 01:04:20 +
with message-id 
and subject line Bug#831244: fixed in ruby-eventmachine 1.0.7-4
has caused the Debian Bug report #831244,
regarding ruby-eventmachine: FTBFS: Build hangs minutes of inactivity
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.)


-- 
831244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-eventmachine
Version: 1.0.7-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 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]: *** Waiting for unfinished jobs
> make[1]: *** wait: No child processes.  Stop.
> make: *** wait: No child processes.  Stop.
> make: *** Waiting for unfinished jobs
> make: *** wait: No child processes.  Stop.
> rake aborted!
> SignalException: SIGTERM
> 
> Tasks: TOP => default
> (See full trace by running task with --trace)
>   test_with_some_connections: 
> Finished in 9015.452909124 seconds.
> 39 tests, 64 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 
> notifications
> 100% passed
> 0.00 tests/s, 0.01 assertions/s
> Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/ruby-eventmachine_1.0.7-3_unstable_gcc5.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: ruby-eventmachine
Source-Version: 1.0.7-4

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

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

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

Debian distribution maintenance software
pp.
Christian Hofstaedtler  (supplier of updated ruby-eventmachine 
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: Mon, 23 Jan 2017 00:36:45 +
Source: ruby-eventmachine
Binary: ruby-eventmachine
Architecture: source
Version: 1.0.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Christian Hofstaedtler 
Description:
 ruby-eventmachine - Ruby/EventMachine library
Closes: 831244
Changes:
 ruby-eventmachine (1.0.7-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Antonio Terceiro ]
   * move rakelib/ back on clean target
 .
   [ Cédric Boutillier ]
   * Bump debhelper compatibility level to 9
   * Use https:// in Vcs-* fields
   * Bump Standards-Version to 3.9.8 (no changes needed)
   * Run wrap-and-sort on packaging files
 .
   [ Christian Hofstaedtler ]
   * Disable flaky inoty test (Closes: #831244)
Checksums-Sha1:
 c6fc03e652564cd89a0edeb9ba336af45d27f199 2279 ruby-eventmachine_1.0.7-4.dsc
 f2b5c50d32cc44a3b3a759d82e4ab350bcab6486 6560 
ruby-eventmachine_1.0.7-4.debian.tar.xz
Checksums-Sha256:
 e2a92d5521f4d1251693f983950bca040b52f355aff82e69f5c6117af1b37f68 2279 
ruby-eventmachine_1.0.7-4.dsc
 dae20e25eb16b33812d1a8e115853e8d8c51875e307558bd21117c237620e1df 6560 
ruby-eventmachine_1.0.7-4.debian.tar.xz
Files:
 9f0d3a61271ea26afd8c99ff8c445b8f 2279 ruby optional 
ruby-eventmachine_1.0.7-4.dsc
 a91431ad2963e891646958524f546b54 6560 ruby optional 
ruby-eventmachine_1.0.7-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAliFUPgACgkQXBPW25MF
LgNMYg//Z0VkE0e2RzzYT6OdIvGmzMLmSA/MMRz6//lUKx7tPDS3xF2iLIB0CKQm
ZBeJefycbfA1Q97caqr4jT7pqV1Po5hnwebw2N+XmFQQbREWT7LkN850B6tEkz9d
4B3aLjW4qhGeltMHwTmCjdk+qtqHpbwiKEgmnxrbRRxpcIElK+WTi551pL4NSht/
hBKUcbyjHM0IRK9SypeAGQLQm0gh193cVnHn/oQYsIH0dzrOsjKOXGWpFoEg6BUL

Bug#840789: marked as done (ruby-gettext: FTBFS: Error: test_relative(TestToolsXGetText::TestReference): NoMethodError: undefined method `stub' for #

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2017 01:49:12 +0100
with message-id <20170123004912.ga19...@percival.namespace.at>
and subject line Re: #840789: ruby-gettext: FTBFS: Error: test_relative ...  
undefined method `stub
has caused the Debian Bug report #840789,
regarding ruby-gettext: FTBFS: Error: 
test_relative(TestToolsXGetText::TestReference): NoMethodError: undefined 
method `stub' for #
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.)


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

Dear Maintainer,

ruby-gettext fails to build from source in unstable/amd64:

  [..]

  Error: test_email(TestToolsMsgInit::TestTranslator::TestChanged): 
NoMethodError: undefined method `stub' for 
#
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:26:in
 `setup'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:42:in
 `block (2 levels) in run'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `chdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `block in run'
  /usr/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:40:in
 `run'
  
===
  E
  
===
  Error: test_name(TestToolsMsgInit::TestTranslator::TestChanged): 
NoMethodError: undefined method `stub' for 
#
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:26:in
 `setup'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:42:in
 `block (2 levels) in run'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `chdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `block in run'
  /usr/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:40:in
 `run'
  
===
  E
  
===
  Error: test_no_email(TestToolsMsgInit::TestTranslator::TestNotChanged): 
NoMethodError: undefined method `stub' for 
#
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:26:in
 `setup'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:42:in
 `block (2 levels) in run'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `chdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `block in run'
  /usr/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:40:in
 `run'
  
===
  E
  
===
  Error: test_no_name(TestToolsMsgInit::TestTranslator::TestNotChanged): 
NoMethodError: undefined method `stub' for 
#
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:26:in
 `setup'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:42:in
 `block (2 levels) in run'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `chdir'
  
/home/lamby/temp/cdt.20161014234743.mNsWwcvjGP.db.ruby-gettext/ruby-gettext-3.2.2/test/tools/test_msginit.rb:41:in
 `block in run'
  /usr/lib/ruby/2.3.0/tmpdir.rb:89:in `mktmpdir'
  

Bug#852152: kernel 4.9: NVIDIA: Failed to load the NVIDIA kernel module

[積丹尼 Dan Jacobson]

And, on your Description be sure to say
"Building the kernel module has been tested up to Linux ..."
"But not necessarily running it (as we don't have all the same hardware
as the user."

Bug#851841: xonsh: jobs and backgrounding broken

[Christian Hofstaedtler]

* Gordon Ball  [170123 00:23]:
> I have upgraded the bug to severity:serious to prevent migration, so
> stretch will get 0.4.7 and unstable will be updated when patches for 0.5
> are available.

That clearly did not work. 0.5.2+dfsg-1 is now in stretch.

  -ch

Bug#852238: marked as done ([cantata] depends on libqt5sql5-sqlite)

[Debian Bug Tracking System]

Your message dated Mon, 23 Jan 2017 00:03:29 +
with message-id 
and subject line Bug#852238: fixed in cantata 2.0.1.ds1-2
has caused the Debian Bug report #852238,
regarding [cantata] depends on libqt5sql5-sqlite
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.)


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


Package: cantata
Version: 2.0.1.ds1-1
Severity: grave

Hi,
without sqllite cantata will segfault afer reading the music libary

ssf@blackbox:~$ cantata
QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers:
Segmentation fault


--- System information. ---
Architecture:
Kernel: Linux 4.8.0-2-amd64

Debian Release: stretch/sid
500 unstable ftp.de.debian.org
500 testing ftp.de.debian.org
500 stable dl.google.com

--- Package information. ---
Depends (Version) | Installed
===-+-===
libavcodec57 (>= 7:3.0) | 7:3.2.2-1
OR libavcodec-extra57 (>= 7:3.0) |
libavformat57 (>= 7:3.0) | 7:3.2.2-1
libavutil55 (>= 7:3.0) | 7:3.2.2-1
libc6 (>= 2.14) | 2.24-8
libcddb2 | 1.3.2-5
libcdparanoia0 (>= 3.10.2+debian) | 3.10.2+debian-11
libebur128-1 (>= 1.1.0) | 1.2.0-1
libgcc1 (>= 1:3.0) | 1:6.3.0-2
libmpg123-0 (>= 1.6.2) | 1.23.8-1
libmtp9 (>= 1.1.3) | 1.1.12-1
libmusicbrainz5cc2v5 (>= 5.1) | 5.1.0+git20150707-6
libqt5concurrent5 (>= 5.0.2) | 5.7.1+dfsg-3
libqt5core5a (>= 5.5.0) | 5.7.1+dfsg-3
libqt5dbus5 (>= 5.0.2) | 5.7.1+dfsg-3
libqt5gui5 (>= 5.2.0) | 5.7.1+dfsg-3
libqt5network5 (>= 5.0.2) | 5.7.1+dfsg-3
libqt5sql5 (>= 5.0.2) | 5.7.1+dfsg-3
libqt5svg5 (>= 5.0.2) | 5.7.1~20161021-2
libqt5widgets5 (>= 5.2.0) | 5.7.1+dfsg-3
libqt5xml5 (>= 5.0.2) | 5.7.1+dfsg-3
libstdc++6 (>= 5.2) | 6.3.0-2
libtag-extras1 (>= 1.0.0) | 1.0.1-3.1
libtag1v5 (>= 1.9.1-2.4) | 1.11.1-0.1
libudev1 (>= 183) | 232-8
libvlc5 (>= 1.1.0) | 2.2.4-13
zlib1g (>= 1:1.1.4) | 1:1.2.8.dfsg-4


Recommends (Version) | Installed
==-+-===
liburi-perl | 1.71-1


Suggests (Version) | Installed
-+-===
mpd | 0.19.21-1
media-player-info |
--- End Message ---
--- Begin Message ---
Source: cantata
Source-Version: 2.0.1.ds1-2

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated cantata 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: Mon, 23 Jan 2017 10:31:12 +1100
Source: cantata
Binary: cantata
Architecture: source
Version: 2.0.1.ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Stuart Prescott 
Closes: 852238
Description: 
 cantata- Qt client for the music player daemon (MPD)
Changes:
 cantata (2.0.1.ds1-2) unstable; urgency=medium
 .
   * Add missing dependency on libqt5sql5-sqlite (Closes: #852238).
Checksums-Sha1: 
 ff15a70f77e179c3790399423335f8a202596f33 2357 cantata_2.0.1.ds1-2.dsc
 baa9bde3f84d07cf7cd3d5d8b15e06e69dd0f487 12420 
cantata_2.0.1.ds1-2.debian.tar.xz
Checksums-Sha256: 
 a8efaf7f769cc755298bc1ba031f4620741d48ebdd58179647da3897e443a242 2357 
cantata_2.0.1.ds1-2.dsc
 9083ce4b94fc1b73e165cd3f5cb22f286d6a90b87a2889e42768ac4b6fe91ad5 12420 
cantata_2.0.1.ds1-2.debian.tar.xz
Files: 
 d4c0ab1f997bfc701a2df5dbf5ec5589 2357 sound optional cantata_2.0.1.ds1-2.dsc
 8e693a64d0ba0410b1a27a689ecdec02 12420 sound optional 
cantata_2.0.1.ds1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYhUYiAAoJELvBfrsTlvL3/iIP/RkrKviWaJDkE4/naUSAnLop
K6sv37W3czCY9/WSZGytmN37YsRavtlnzlw8dF7x/8ZFFE1mz0EmSreOEwJ+byLN
s8Ay/I7uDi2nP4hzuWICra6ZXmjhojW3BPS0anQc/xEgC2d30gYQIz4sSG56mY8o
tBCnWKFeDk/wyv41O1EtO1upCzDCC17euy7UKAJM1uFj4Bm3g41pFIwT6FqfZuOd
AWZZ70FAfJiwkcXixJmGd7GA178cRFNOFWpK0fouJBOqcX/+1JJJqTUk+r+6uhUa
LjaFHuX4DZVXLfCUvr8lyHxCHx2pPn9iGlyLOLZVX+OGMxYeKy1YnrcbxJ8bUnXI

Bug#852152: kernel 4.9: NVIDIA: Failed to load the NVIDIA kernel module

[積丹尼 Dan Jacobson]

By the way,

AB> What is the exact error you get from the kernel when loading the module?
AB> You should find this in e.g. dmesg or the journald equivalent of
AB> /var/log/messages.

Well often important items just fly by on the screen, not logged
anywhere.
Bug#852229: failing to log output at boot time
Bug#852194: make a /run/initramfs/messages

AB> There is another bug with your bug report: it didn't run the bug script
AB> that should have collected more information ...

Hmmm, you are right. I did
< /dev/null reportbug --template --no-bug-script $@

But anyway the patch fixed it. Thanks.

Processed: Bug#852238 marked as pending

[Debian Bug Tracking System]

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

> tag 852238 pending
Bug #852238 [cantata] [cantata] depends on libqt5sql5-sqlite
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#852238: marked as pending

[Stuart Prescott]

tag 852238 pending
thanks

Hello,

Bug #852238 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/cantata.git;a=commitdiff;h=39b0d0d

---
commit 39b0d0dd72b17228382d972a09da2c862951fcb6
Author: Stuart Prescott 
Date:   Mon Jan 23 10:31:25 2017 +1100

Add changelog for upload

diff --git a/debian/changelog b/debian/changelog
index 47daba5..9295708 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cantata (2.0.1.ds1-2) unstable; urgency=medium
+
+  * Add missing dependency on libqt5sql5-sqlite (Closes: #852238).
+
+ -- Stuart Prescott   Mon, 23 Jan 2017 10:31:12 +1100
+
 cantata (2.0.1.ds1-1) unstable; urgency=medium
 
   * New upstream release.

Bug#852152: kernel 4.9: NVIDIA: Failed to load the NVIDIA kernel module

[Luca Boccassi]

On Sun, 2017-01-22 at 22:54 +0100, Andreas Beckmann wrote:
> On 2017-01-22 03:30, Dan Jacobson wrote:
> > Even though your package Description says
> > "Building the kernel module has been tested up to Linux 4.9."
> 
> > Maybe BUILDING yes, but not RUNNING, no.
> 
> Further testing is not possible without sufficiently old hardware.
> 
> > With 4.9 you will get: NVIDIA: Failed to load the NVIDIA kernel module
> 
> What is the exact error you get from the kernel when loading the module?
> You should find this in e.g. dmesg or the journald equivalent of
> /var/log/messages.
> 
> There is another bug with your bug report: it didn't run the bug script
> that should have collected more information ...
> 
> 
> Andreas

I've committed the fix to branches/304, do you have time to prepare an
upload before the 25th (so that it migrates to stretch before the 5th)?

Thanks!

Kind regards,
Luca Boccassi


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

Bug#852152: kernel 4.9: NVIDIA: Failed to load the NVIDIA kernel module

[積丹尼 Dan Jacobson]

Yes I can confirm that now
I can run X windows on
linux-image-4.9.0-1-amd64
Thank you!
However at the same time
my formerly working backup
linux-image-4.8.0-2-amd64
is now broken. Please make
sure your fixes don't "fix"
more than was intended! Thanks.

Bug#848748: intent to NMU #848748: blockdiag FTBFS

[Rebecca N. Palmer]

Attached is a proposed NMU fixing this bug (identical to my original
patch other than adding the changelog entry; the olefile issue noted
above was a bug in pillow, which has now been fixed).

As the execnet issue (#840823) now also appears to have a fix,
this will allow blockdiag's ~30 rdeps to stay in stretch.
diff -Nru blockdiag-1.5.3+dfsg/debian/changelog 
blockdiag-1.5.3+dfsg/debian/changelog
--- blockdiag-1.5.3+dfsg/debian/changelog   2016-10-11 02:21:04.0 
+0100
+++ blockdiag-1.5.3+dfsg/debian/changelog   2017-01-22 22:14:34.0 
+
@@ -1,3 +1,10 @@
+blockdiag (1.5.3+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't fail tests on a harmless wand warning. Closes: #848478
+
+ -- Rebecca N. Palmer   Sun, 22 Jan 2017 22:13:59 
+
+
 blockdiag (1.5.3+dfsg-1) unstable; urgency=medium
 
   * New upstream release. Closes: #801314
diff -Nru 
blockdiag-1.5.3+dfsg/debian/patches/848748-exception-ignored-in-Image-del.patch 
blockdiag-1.5.3+dfsg/debian/patches/848748-exception-ignored-in-Image-del.patch
--- 
blockdiag-1.5.3+dfsg/debian/patches/848748-exception-ignored-in-Image-del.patch 
1970-01-01 01:00:00.0 +0100
+++ 
blockdiag-1.5.3+dfsg/debian/patches/848748-exception-ignored-in-Image-del.patch 
2017-01-09 22:32:13.0 +
@@ -0,0 +1,38 @@
+Description: Fix test failure with wand 0.4.1+
+ 
+wand 0.4.1 added an Image.destroy()
+(https://sources.debian.net/src/wand/0.4.4-1/wand/image.py/#L2760) that
+iterates over self.sequence (the frames of an animation) to free their
+memory; this throws an exception on single images (where
+self.sequence=None), but as this is called from __del__, this
+exception is warned about then ignored
+(https://docs.python.org/3/reference/datamodel.html#object.__del__),
+and hence is not an error in normal use.
+
+However, blockdiag tests that use capture_stderr fail on any output
+containing "Traceback", including this warning message.
+
+This patch ignores this message to allow blockdiag to build.
+
+Author: Rebecca Palmer 
+Bug-Debian: https://bugs.debian.org/848748
+Forwarded: no
+
+--- blockdiag-1.5.3+dfsg.orig/src/blockdiag/tests/utils.py
 blockdiag-1.5.3+dfsg/src/blockdiag/tests/utils.py
+@@ -64,7 +64,14 @@ def capture_stderr(func):
+ 
+ func(*args, **kwargs)
+ 
+-if re.search('(ERROR|Traceback)', sys.stderr.getvalue()):
++filtered_stderr=re.sub(r"""Exception ignored in: >
++Traceback \(most recent call last\):
++  File "/usr/lib/python3/dist-packages/wand/resource\.py", line [0-9]+, in 
__del__
++self\.destroy\(\)
++  File "/usr/lib/python3/dist-packages/wand/image\.py", line [0-9]+, in 
destroy
++for i in range\(0, len\(self\.sequence\)\):
++TypeError: object of type 'NoneType' has no 
len\(\)""","",sys.stderr.getvalue())#this is the expected result of freeing a 
single image (as opposed to an animation) in wand 0.4, not a blockdiag bug - 
#848748
++if re.search('(ERROR|Traceback)', filtered_stderr):
+ raise AssertionError('Caught error')
+ finally:
+ if sys.stderr.getvalue():
diff -Nru blockdiag-1.5.3+dfsg/debian/patches/series 
blockdiag-1.5.3+dfsg/debian/patches/series
--- blockdiag-1.5.3+dfsg/debian/patches/series  2016-10-11 01:32:49.0 
+0100
+++ blockdiag-1.5.3+dfsg/debian/patches/series  2017-01-09 21:50:32.0 
+
@@ -1 +1,2 @@
 Fixed-remote-image-resouces.patch
+848748-exception-ignored-in-Image-del.patch

Bug#852264: gbp buildpackage: doesn't pass options correctly anymore

[Raphaël Halimi]

Package: git-buildpackage
Version: 0.8.10
Severity: serious

Hi,

I was trying to backport a package with this command, which used to work
as expected for as long as I can remember:

DIST=jessie gbp buildpackage -v0.9-1

...but now gbp exits with the message:

gbp:error: 'BUILDER=pbuilder GIT_PBUILDER_AUTOCONF=no
/usr/bin/git-pbuilder -v0.9-1' failed: it exited with 2

A couples of lines above, I can see:

I: Generating source changes file for original dsc
dpkg-genchanges: error: unknown option ''-v0.9-1''

Is it the extra pair of quotes that confuse dpkg-genchanges ?

The bug may come from some other tool in the chain (maybe pbuilder,
which was recently changed regarding the source package building phase),
but I'm not sure how to debug this.

Regards,

-- 
Raphaël Halimi



signature.asc
Description: OpenPGP digital signature

Bug#852263: mustache-d FTBFS on ppc64el: Unknown compiler "ldc2"

[Adrian Bunk]

Source: mustache-d
Version: 0.1.3-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=mustache-d=ppc64el=0.1.3-1=1484949441=0

...
make[1]: Entering directory '/«PKGBUILDDIR»'
mkdir build
(cd build && meson --prefix=/usr --buildtype=plain ..)
WARNING: You are using 'ANSI_X3.4-1968' which is not a a Unicode-compatible 
locale.
WARNING: You might see errors if you use UTF-8 strings as filenames, as 
strings, or as file contents.
WARNING: Please switch to a UTF-8 locale for your platform.
The Meson build system
Version: 0.37.1
Source dir: /«PKGBUILDDIR»
Build dir: /«PKGBUILDDIR»/build
Build type: native build
Project name: mustache-d

Meson encountered an error in file meson.build, line 1, column 0:
Unknown compiler "ldc2"
debian/rules:15: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1

Bug#852216: kodi: FTBFS on mips64el

[Bálint Réczey]

Control: tags -1 confirmed pending

2017-01-22 17:32 GMT+01:00 Adrian Bunk :
> Control: retitle -1 kodi FTBFS with libcec 4
> Control: found -1 2:17.0~rc2+dfsg1-1
>
> On Sun, Jan 22, 2017 at 05:03:33PM +0100, Julien Cristau wrote:
>> Source: kodi
>> Version: 2:17.0~rc3+dfsg1-1
>> Severity: serious
>> Justification: fails to build from source (but built successfully in the 
>> past)
>>
>> kodi FTBFS on the mips64el buildd:
>>
>> > PeripheralCecAdapter.cpp: In member function 'virtual void 
>> > PERIPHERALS::CPeripheralCecAdapter::Announce(ANNOUNCEMENT::AnnouncementFlag,
>> >  const char*, const char*, const CVariant&)':
>> > PeripheralCecAdapter.cpp:169:25: error: 'CEC::libcec_configuration {aka 
>> > struct CEC::libcec_configuration}' has no member named 
>> > 'bPowerOnScreensaver'
>> >  if (m_configuration.bPowerOnScreensaver == 1 && !bIgnoreDeactivate &&
>> >  ^~~
>>...
>
> This is actually not mips64el specific, just timing of the kodi build.
> kodi FTBFS with libcec 4.
>
> This is the libcec transition (#849189).

I plan uploading a new kodi package possibly with other fixes in the next days.

Cheers,
Balint


>
>> Cheers,
>> Julien
>
> 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
>
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Processed: Re: Bug#852216: kodi: FTBFS on mips64el

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed pending
Bug #852216 [src:kodi] kodi FTBFS with libcec 4
Added tag(s) confirmed and pending.

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

Bug#852261: profanity FTBFS on armel/armhf/mips/mipsel: prof_whole_occurrences_tests failed

[Adrian Bunk]

Source: profanity
Version: 0.5.0-0.1
Severity: serious

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

...
[ RUN  ] prof_whole_occurrences_tests
_lists_equal(prof_occurrences("boothj5", "boothj5", 0, TRUE, ), expected)
tests/unittests/test_common.c:441: error: Failure!
[  FAILED  ] prof_whole_occurrences_tests
[ RUN  ] returns_no_commands
[   OK ] returns_no_commands
[ RUN  ] returns_commands
[   OK ] returns_commands
[ RUN  ] returns_empty_list_when_none
[   OK ] returns_empty_list_when_none
[ RUN  ] returns_added_feature
[   OK ] returns_added_feature
[ RUN  ] resets_features_on_close
[   OK ] resets_features_on_close
[ RUN  ] returns_all_added_features
[   OK ] returns_all_added_features
[ RUN  ] does_not_add_duplicate_feature
[   OK ] does_not_add_duplicate_feature
[ RUN  ] removes_plugin_features
[   OK ] removes_plugin_features
[ RUN  ] does_not_remove_feature_when_more_than_one_reference
[   OK ] does_not_remove_feature_when_more_than_one_reference
[==] 412 test(s) run.
[  PASSED  ] 411 test(s).
[  FAILED  ] 1 test(s), listed below:
[  FAILED  ] prof_whole_occurrences_tests
FAIL tests/unittests/unittests (exit status: 1)


Testsuite summary for profanity 0.5.0

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

See ./test-suite.log
Please report to boothj5...@gmail.com

Makefile:3403: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1

Bug#852259: newlisp: Dynamic library loading is broken

[Adrian Bunk]

Package: newlisp
Version: 10.7.0-3
Severity: serious

I was originally interested in how to get the dependency on
libmysqlclient18 (which will not be part of stretch) updated,
but it turned out dynamic library loading in newlisp is broken.


(set 'files '(
"/usr/local/lib/libmysqlclient.so.20.0" ; OpenBSD 4.9
"/usr/lib/libmysqlclient.so" ; Linux, UNIX
"/usr/lib/mysql/libmysqlclient.so" ; Linux Fedora
"/usr/lib64/mysql/libmysqlclient.so" ; Linux Fedora CentOS 6.x
"/usr/lib/x86_64-linux-gnu/libmysqlclient.so" ; Ubuntu 12.04 LTS
"/usr/local/mysql/lib/libmysqlclient.so" ; Linux, UNIX
"/usr/local/mysql/lib/libmysqlclient.dylib" ; MacOS X
"/usr/lib/libmysqlclient.dylib" ; MacOS X
))


This looks like a random collection of files that worked for
random people, not like someone who knows what (s)he is doing
and where the problems are.

There are several things that wrong with this.

One problem is that the libmysqlclient18 package does not ship
the .so symlink.

Another is trying to open libraries from /usr/local,
whenever such libraries exist using them from a Debian
package only causes problems.

But the worst is that this cannot work properly with multiarch.
On my multiarch enabled system I might be using either the
i386 newlisp package or the amd64 newlisp package.
I might have both the i386 and the amd64 version of the library
to load installed.
As long as newlisp searches in the same paths in both cases,
it is guaranteed to not find the correct library in at least
one case.

Other libraries used by newlisp have exactly the same problem.

Bug#852258: rt-authen-externalauth: FTBFS: Your installed version of RT (4.4.1-2) is too new

[Chris Lamb]

Source: rt-authen-externalauth
Version: 0.26-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,

rt-authen-externalauth fails to build from source in unstable/amd64:

  […]

  dh build
 dh_testdir
 dh_update_autotools_config
 debian/rules override_dh_auto_configure
  make[1]: Entering directory '«BUILDDIR»'
  PREFIX=/usr/share/request-tracker4 dh_auto_configure
perl -I. Makefile.PL INSTALLDIRS=vendor "OPTIMIZE=-g -O2 
-fdebug-prefix-map=«BUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" 
"LD=x86_64-linux-gnu-gcc -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20170123104007.6o1i5bkY3w.db.rt-authen-externalauth/rt-authen-externalauth-0.26=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro"
  Cannot determine perl version info from lib/RT/Authen/ExternalAuth.pm
  
   Error: Your installed version of RT (4.4.1-2) is too new; this extension
  only works with versions older than 4.4.0.
  
  Using RT configuration from /usr/share/request-tracker4/lib/RT.pm:
  html   => /usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/html
  lib=> /usr/share/request-tracker4/plugins/RT-Authen-ExternalAuth/lib
  dh_auto_configure: perl -I. Makefile.PL INSTALLDIRS=vendor OPTIMIZE=-g -O2 
-fdebug-prefix-map=«BUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 LD=x86_64-linux-gnu-gcc 
-g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20170123104007.6o1i5bkY3w.db.rt-authen-externalauth/rt-authen-externalauth-0.26=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
returned exit code 2
  debian/rules:11: recipe for target 'override_dh_auto_configure' failed
  make[1]: *** [override_dh_auto_configure] Error 2
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


rt-authen-externalauth.0.26-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#852152: kernel 4.9: NVIDIA: Failed to load the NVIDIA kernel module

[Andreas Beckmann]

On 2017-01-22 03:30, Dan Jacobson wrote:
> Even though your package Description says
> "Building the kernel module has been tested up to Linux 4.9."

> Maybe BUILDING yes, but not RUNNING, no.

Further testing is not possible without sufficiently old hardware.

> With 4.9 you will get: NVIDIA: Failed to load the NVIDIA kernel module

What is the exact error you get from the kernel when loading the module?
You should find this in e.g. dmesg or the journald equivalent of
/var/log/messages.

There is another bug with your bug report: it didn't run the bug script
that should have collected more information ...


Andreas

Bug#849756: sssd-ldap fails to connect to ldaps:// due to problem with non-blocking socket

[Petter Reinholdtsen]

[Timo Aaltonen]
> I hope to get 1.15 in stretch.. they'd just need to release it first and
> time is running short.

What about uploading a patched version while you wait, in case the new release
is delayed, to make sure a fix is included before the freeze?

-- 
Happy hacking
Petter Reinholdtsen

Bug#851110: marked as done (freedink: violates font license)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 21:50:13 +
with message-id 
and subject line Bug#851110: fixed in freedink 108.4+dfsg-1
has caused the Debian Bug report #851110,
regarding freedink: violates font license
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.)


-- 
851110: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freedink
Version: 108.4-1
Severity: serious
User: pkg-fonts-de...@lists.alioth.debian.org
Usertags: license-violation
X-Debbugs-CC: pkg-fonts-de...@lists.alioth.debian.org

Your source package contains an GPL/LGPL font:

share/freedink/LiberationSans-Regular.ttf

This looks to be from here:

https://fedorahosted.org/liberation-fonts/

The font's source code appears to be here:

https://git.fedorahosted.org/cgit/liberation-fonts.git/tree/src

Your source package does not contain the font source code, therefore
your distribution of the font constitutes a violation of the license.

Please notify your upstream that they are violating the font license.

Please remove the font from the source package and depend on the
fonts-liberation binary font package instead.

Please contact your upstream and ask them to use fontconfig or similar
to get fonts for use by the software instead of using a specific font.

This message is brought to you by the Debian Fonts Task Force:

http://wiki.debian.org/Fonts

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: freedink
Source-Version: 108.4+dfsg-1

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

Debian distribution maintenance software
pp.
Sylvain Beucler  (supplier of updated freedink package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Jan 2017 21:06:51 +0100
Source: freedink
Binary: freedink-engine freedink-engine-dbg freedink
Architecture: source amd64 all
Version: 108.4+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Sylvain Beucler 
Description:
 freedink   - humorous top-down adventure and role-playing game
 freedink-engine - humorous top-down adventure and role-playing game (engine)
 freedink-engine-dbg - debugging symbols for freedink
Closes: 851110
Changes:
 freedink (108.4+dfsg-1) unstable; urgency=medium
 .
   * Stub out share/freedink/LiberationSans-Regular.ttf (Closes: #851110)
   * debian/watch: mangle '+dfsg'
   * Bump Standards-Version to 3.9.8 (no changes)
Checksums-Sha1:
 f6ab8550102947ee2ec0acdbe4c064bb8dc86242 1861 freedink_108.4+dfsg-1.dsc
 09f57d17ba8432057ca4d395d109e91d3b184515 1823341 
freedink_108.4+dfsg.orig.tar.gz
 9a0ec7a2c0c4fd69c75f2be33fc95bc04cd50f9d 22112 
freedink_108.4+dfsg-1.debian.tar.xz
 2903c268caa9d26d7269822af71ba9c2ccf64042 573532 
freedink-engine-dbg_108.4+dfsg-1_amd64.deb
 e46c35315841a25f0d0e37547c398e43fc1051f6 237622 
freedink-engine_108.4+dfsg-1_amd64.deb
 157347d9fa12aa63ae4408e94c91a76d315b7a31 1100 freedink_108.4+dfsg-1_all.deb
 040a02ebb825f1bff4e093d5909a4efad6c8d500 9802 
freedink_108.4+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 98af80374b6ca321c7cd6eebdafb6a873b0f50bec3079276ff0b204089d84c1a 1861 
freedink_108.4+dfsg-1.dsc
 f6cbc21ee63eec0c0a0bfd95bd7858209e1323c3ca8fc6ab46dcd2d814e9e5a0 1823341 
freedink_108.4+dfsg.orig.tar.gz
 7dafa6420862ead4d0c71d9ae826662ddf138c284a7637d15952cc72d8669f34 22112 
freedink_108.4+dfsg-1.debian.tar.xz
 b8435d331fcdde142fb9d30c9f9eb37f5e87395f0e8925c337d3c35ebf4cd745 573532 
freedink-engine-dbg_108.4+dfsg-1_amd64.deb
 b30811703d06e1c2a0062e6869edbf8a0f0704d40d41d2f70a26d1f7b196a056 237622 
freedink-engine_108.4+dfsg-1_amd64.deb
 8cc804168c85a9c50c95b157bc158114bc3af7cc36ca29f924bf8790bc9449ce 1100 
freedink_108.4+dfsg-1_all.deb
 fcd03b91363e2364610a580a92663ac8718dcf8ee8036675aca62462daafda84 9802 
freedink_108.4+dfsg-1_amd64.buildinfo
Files:
 

Bug#851771: CVE-2016-6175 and 851771

[Ola Lundqvist]

Hi Salvatore

I started checking the CVEs for php-gettext and I'm not sure I follow
the information for CVE-2016-6175.
Maybe you have more data than I do.

The vulnerability is that a malicous user that have permission to
craft .mo files in the target filesystem could execute any php code on
that system.
I find that a quite unlikely attack vector. Based on this I also think
the bug should have a different priority than grave.

Or have I missed anything crucial?

I'm asking as I plan to mark this one as no-dsa for wheezy.

Best regards

// Ola

PS. There is another bug on the same package and that one should
probably have a grave bug filed, but that is another story.
DS.

-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comFolkebogatan 26\
|  o...@debian.org   654 68 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---

Bug#835941: marked as done (starpu-contrib: non-standard gcc/g++ used for build (gcc-5))

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 21:35:28 +
with message-id 
and subject line Bug#835941: fixed in starpu-contrib 1.2.0+dfsg-3
has caused the Debian Bug report #835941,
regarding starpu-contrib: non-standard gcc/g++ used for build (gcc-5)
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.)


-- 
835941: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: starpu-contrib
Version: 1.1.4+dfsg-6
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-5, gcc-5-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-6/g++-6.

Please keep this report open until the package uses the default
compiler version (or gcc-6) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.

The severity of this report is likely to be raised before the release,
so that the gcc-5 package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: starpu-contrib
Source-Version: 1.2.0+dfsg-3

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated starpu-contrib 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Jan 2017 21:05:52 +0100
Source: starpu-contrib
Binary: libstarpu-contrib-dev libstarpu-contrib-1.2-0 
libstarpu-contribfft-1.2-0 libstarpu-contribmpi-1.2-0 starpu-contrib-tools 
starpu-contrib-examples libsocl-contrib-1.2-0
Architecture: source amd64
Version: 1.2.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 libsocl-contrib-1.2-0 - Task scheduler for heterogeneous multicore machines
 libstarpu-contrib-1.2-0 - Task scheduler for heterogeneous multicore machines
 libstarpu-contrib-dev - Task scheduler for heterogeneous multicore machines - 
dev
 libstarpu-contribfft-1.2-0 - Task scheduler for heterogeneous multicore 
machines
 libstarpu-contribmpi-1.2-0 - Task scheduler for heterogeneous multicore 
machines
 starpu-contrib-examples - Task scheduler for heterogeneous multicore machines 
- exs
 starpu-contrib-tools - Task scheduler for heterogeneous multicore machines - 
tools
Closes: 835941
Changes:
 starpu-contrib (1.2.0+dfsg-3) unstable; urgency=medium
 .
   * Run the full testsuite even if there are failures.
   * control [contrib]: Build-Depend on clang-3.8 instead of gcc-5
   * rules: Pass -ccbin clang-3.8 (Closes: Bug#835941).
   * patches/nvcc_noccbin: Avoid overriding our -ccbin option.
Checksums-Sha1:
 4e459154e689bc0730f073f60d84c30577312103 3036 starpu-contrib_1.2.0+dfsg-3.dsc
 31dd43d4b04f7fc0f9c5c27c4257fda4039abef6 11064 
starpu-contrib_1.2.0+dfsg-3.debian.tar.xz
 102c293ca94fe74277f4387d7ec9a35f2b730d01 250152 
libsocl-contrib-1.2-0-dbgsym_1.2.0+dfsg-3_amd64.deb
 5ab1973ffb54f37c68ac81a39d9834e5579dd7f9 43844 
libsocl-contrib-1.2-0_1.2.0+dfsg-3_amd64.deb
 dde31ab4d89b2a12ddf6fc62522c0b5b97f8a869 2414522 
libstarpu-contrib-1.2-0-dbgsym_1.2.0+dfsg-3_amd64.deb
 2152054f5c1dc2a1aa074e20f1d501641671cb9f 357960 
libstarpu-contrib-1.2-0_1.2.0+dfsg-3_amd64.deb
 859d3d86c786cb2891cdaf37e9d558e0c821781c 520080 
libstarpu-contrib-dev_1.2.0+dfsg-3_amd64.deb
 1ff13c18d0ad961961440ca9cc4db5a8007dcdf2 95772 
libstarpu-contribfft-1.2-0-dbgsym_1.2.0+dfsg-3_amd64.deb
 6cbbb208b763f881f05c6e942f78abcc7ccad41f 35288 
libstarpu-contribfft-1.2-0_1.2.0+dfsg-3_amd64.deb
 188ed0c9a05d6fbd0fc505f5ef16125a0b474482 330566 
libstarpu-contribmpi-1.2-0-dbgsym_1.2.0+dfsg-3_amd64.deb
 33ba81eb0f376e548a2ac594c8be40dd1b20bbac 67024 
libstarpu-contribmpi-1.2-0_1.2.0+dfsg-3_amd64.deb
 eafdea006d838abad07d2c544317f9322712dbc1 5169918 

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Rebecca N. Palmer]

On 22/01/17 21:07, Sylvestre Ledru wrote:
> , you haven't pass the arg to LDFLAGS to make sure that libclang or
> liblldb get it,
> is that on purpose?

My original intent was to avoid passing it to those parts of LLVM that
already use a "version" (actually which-symbols-are-public) script, as
I suspect having two version scripts is an error; you're right that
there might be other parts of LLVM that would benefit.

>> - Are the symbols versioned? For this creating a temporary symbols files is 
>> enough. Ping me if you don't know how to do this.
> Just libclang is (the C lib).
> I haven't done it for the rest because it is C++ and not commitment
> from upstream on API stability

The lack of API stability is exactly why we need symbol versioning
(otherwise we could just make everything use 3.9).  We're not proposing
to ship this .symbols file (which would be a compatibility statement),
just use it to check whether symbol versioning was successfully enabled.

>> - Install and test LLVM 3.9 with stuff built with previous versions, like 
>> for 
>> example kdevelop ;-) Everything should just work.

kdevelop (#846410) has already been fixed by moving it to all-3.9; if
you need a test case, I suggest the pocl-opencl-icd + blender one above.

Bug#852254: openjpa: FTBFS (Cannot access central (https://repo.maven.apache.org/maven2) in offline mode)

[Santiago Vila]

Package: src:openjpa
Version: 2.4.0-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibopenjpa-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
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=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo install -DskipTests 
-Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.openjpa:openjpa-kernel:jar:2.4.0
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-jar-plugin is missing. @ line 134, column 12
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.openjpa:openjpa-persistence-jdbc:jar:2.4.0
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 896, column 12
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.openjpa:openjpa-xmlstore:jar:2.4.0
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 77, column 12
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.openjpa:openjpa-slice:jar:2.4.0
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 125, column 12
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] OpenJPA Utilities Library
[INFO] OpenJPA Kernel
[INFO] OpenJPA JDBC
[INFO] OpenJPA Persistence
[INFO] OpenJPA Persistence JDBC
[INFO] OpenJPA XML Store
[INFO] OpenJPA Slice
[INFO] OpenJPA JEST
[INFO] OpenJPA Aggregate Jar
[INFO] OpenJPA Parent POM
[INFO] 
[INFO] 
[INFO] Building OpenJPA Utilities Library 2.4.0
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
openjpa-lib ---
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
resources, i.e. build is platform dependent!
[INFO] Copying 9 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ openjpa-lib ---
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding 
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] Compiling 161 source files to /<>/openjpa-lib/target/classes
[INFO] 
/<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/rop/SoftRandomAccessResultList.java:
 Some input files use or override a deprecated API.
[INFO] 
/<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/rop/SoftRandomAccessResultList.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
/<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/util/concurrent/NullSafeConcurrentHashMap.java:
 Some input files use unchecked or unsafe operations.
[INFO] 
/<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/util/concurrent/NullSafeConcurrentHashMap.java:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (set subversion revision) @ openjpa-lib 
---
[WARNING] Parameter tasks is deprecated, use target instead
[INFO] Executing tasks

main:
 [exec] Execute failed: java.io.IOException: Cannot run program 
"svnversion" (in directory 

Bug#852255: projectreactor: FTBFS (No cached version of com.esotericsoftware.minlog:minlog:debian)

[Santiago Vila]

Package: src:projectreactor
Version: 2.0.8-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=gradle --with maven_repo_helper
   dh_testdir -i -O--buildsystem=gradle
   dh_update_autotools_config -i -O--buildsystem=gradle
   dh_auto_configure -i -O--buildsystem=gradle
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- :reactor-core:install :reactor-net:install 
:reactor-bus:install :reactor-stream:install -x javadoc
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian -Ddebian.package=projectreactor :reactor-core:install 
:reactor-net:install :reactor-bus:install :reactor-stream:install -x javadoc
Initialized native services in: /<>/.gradle/native
Starting Build
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using SubsetScriptTransformer.
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using BuildScriptTransformer.
Loading the Maven rules...
Compiling settings file '/<>/settings.gradle' using 
SubsetScriptTransformer.
Compiling settings file '/<>/settings.gradle' using 
BuildScriptTransformer.
Settings evaluated using settings file '/<>/settings.gradle'.
Projects loaded. Root project using build file '/<>/build.gradle'.
Included projects: [root project 'reactor', project ':reactor-alloc', project 
':reactor-bus', project ':reactor-core', project ':reactor-groovy', project 
':reactor-groovy-extensions', project ':reactor-logback', project 
':reactor-net', project ':reactor-stream']
Keep-alive timer started
Adding Debian repository to project 'reactor'
Adding Debian repository to project 'reactor-alloc'
Adding Debian repository to project 'reactor-bus'
Adding Debian repository to project 'reactor-core'
Adding Debian repository to project 'reactor-groovy'
Adding Debian repository to project 'reactor-groovy-extensions'
Adding Debian repository to project 'reactor-logback'
Adding Debian repository to project 'reactor-net'
Adding Debian repository to project 'reactor-stream'
Evaluating root project 'reactor' using build file 
'/<>/build.gradle'.
Compiling build file '/<>/build.gradle' using 
SubsetScriptTransformer.
Replacing org.springframework.build.gradle:propdeps-plugin:jar:0.0.7  
->  org.springframework.build.gradle:propdeps-plugin:jar:debian
Ignoring io.spring.gradle:spring-io-plugin:jar:0.0.4.RELEASE
Ignoring com.github.jengelman.gradle.plugins:shadow:jar:1.2.0
Compiling build file '/<>/build.gradle' using 
BuildScriptTransformer.
Compiling script '/<>/gradle/setup.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/gradle/setup.gradle' using 
BuildScriptTransformer.
Compiling script '/<>/gradle/ide.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/gradle/ide.gradle' using 
BuildScriptTransformer.
Adding task debianMavenPom to project 'reactor'
Configuring javadoc links
Evaluating project ':reactor-alloc' using build file 
'/<>/reactor-alloc/build.gradle'.
Adding task debianMavenPom to project 'reactor-alloc'
Configuring javadoc links
Evaluating project ':reactor-bus' using build file 
'/<>/reactor-bus/build.gradle'.
Adding task debianMavenPom to project 'reactor-bus'
Configuring javadoc links
Evaluating project ':reactor-core' using build file 
'/<>/reactor-core/build.gradle'.
Adding task debianMavenPom to project 'reactor-core'
Configuring javadoc links
Evaluating project ':reactor-groovy' using build file 
'/<>/reactor-groovy/build.gradle'.
Adding task debianMavenPom to project 'reactor-groovy'
Configuring javadoc links
Evaluating project ':reactor-groovy-extensions' using build file 
'/<>/reactor-groovy-extensions/build.gradle'.
Adding task debianMavenPom to project 'reactor-groovy-extensions'
Configuring javadoc links
Evaluating project ':reactor-logback' using build file 
'/<>/reactor-logback/build.gradle'.
Adding task debianMavenPom to project 'reactor-logback'
Configuring javadoc links
Evaluating project ':reactor-net' using build file 
'/<>/reactor-net/build.gradle'.
Adding task debianMavenPom to project 'reactor-net'
Configuring javadoc links
Evaluating project ':reactor-stream' using build file 
'/<>/reactor-stream/build.gradle'.
Adding task debianMavenPom to project 'reactor-stream'
Configuring javadoc links
All projects evaluated.
Selected primary task ':reactor-core:install' from project :reactor-core
Selected primary task 

Bug#838112: uctodata: fails to upgrade from 'jessie' - trying to overwrite /etc/ucto/es.abr

[Andreas Beckmann]

On 2017-01-22 09:48, Adrian Bunk wrote:
> es.abr was a conffile in the jessie ucto, that needs additional treatment.
> 
> The solution might be using mv_conffile from dpkg-maintscript-helper(1) 
> in a .maintscript to move the conffile to the new name spa.abr and the 
> new package (es.abr is now a symlink), but Andreas should comment on 
> that since he knows this better.

TL;DR: You have an ambitious task before you.

Let me see if I understand what's going on.

Renaming conffiles and changing the owning package at the same time is a
PITA.
You add an extra point by making the old name a symlink to the new one,
owned by the new package

In jessie, everything in /etc/ucto was owned by ucto.
In sid, a lot more stuff is in /etc/ucto, and either owned by uctodata
or libucto2, a m-a:same library package. These come from 2 different
source packages.

Yuck. While putting conffiles in m-a:same packages is allowed, I highly
discourage this. Even if I haven't seen this fail once, yet. I'm just
afraid, someone has to clean up a mess caused by this at some point in
the future. and I'm afraid, I won't keep my fingers out of then :-(

Before we start: Are these really conffiles? Supposed to be modified by
the local admin? Or are these rather data files that are not supposed to
be updated locally? And would better live in /usr/share in that case?

And nearly everything from jessie's /etc/ucto content is now renamed and
a symlink.

Can't you just fork the project? I'd suggest 'hpgb' and then use
/etc/hpgb for the conffiles. Oh, I forgot: we are in freeze, so no new
source packages ...

Oh yeah, it well be a mess. But we will do it right. Including making
dpkg forget about the old conffiles.

Right now, all upgrade attempts from jessie to stretch should always
have failed, so there is no further messed up state inbetween that
should be supported for clean upgrades.

can we move the conffiles from libucto2 to a new package, e.g.
ucto-common (which would be either m-a:foreign or m-a:allowed, but I
always mess up these two, I need to look up what's right?

* Which version introduced the new layout?
* can you give me a list of
  + removed conffiles
  + renamed conffiles (old name, new name, new owning package, whether
they have a compat symlink, did the content change between jessie and sid)

Do you *really* need the compat symlinks?

OK, packaging is in git. Need to check whether I have write permissions
there ...

rough plan:

ucto uses d-m-h move-conffile (but provides no new version, so the old
conffile should "disappear" and dpkg should forget about it.
Maybe it's better to rm_conffile it instead.

uctodata will probably need a Conflicts against ucto (<< current+fixed~)


Andreas

Bug#852253: kryo-serializers: FTBFS (Cannot access central (https://repo.maven.apache.org/maven2) in offline mode)

[Santiago Vila]

Package: src:kryo-serializers
Version: 0.22-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibkryo-serializers-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--buildsystem=maven
/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=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
-Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building kryo serializers 0.22
[INFO] 
[WARNING] The POM for com.esotericsoftware.minlog:minlog:jar:debian is missing, 
no dependency information available
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2.737 s
[INFO] Finished at: 2017-01-22T20:50:34+00:00
[INFO] Final Memory: 7M/19M
[INFO] 
[ERROR] Failed to execute goal on project kryo-serializers: Could not resolve 
dependencies for project de.javakaffee:kryo-serializers:bundle:0.22: Cannot 
access central (https://repo.maven.apache.org/maven2) in offline mode and the 
artifact com.esotericsoftware.minlog:minlog: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=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


It also fails here, where you can get a full build log if you need it:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kryo-serializers.html

In case it helps: My build history (for stretch) shows that something
happened between 2017-01-16 and 2017-01-21:

[...]
Status: successful  kryo-serializers_0.22-3_amd64-20170116T195523Z
Status: failed  kryo-serializers_0.22-3_amd64-20170121T150952Z
[...]

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

Thanks.

Bug#828082: bind9: FTBFS with openssl 1.1

[Michael Gilbert]

On Sun, Jan 22, 2017 at 6:26 AM, Luca Boccassi wrote:
> This will allow a clean rebuild for backporting purposes. Would really
> appreciate a lot if this change could be made :-)

There are no jessie backports of bind.

Best wishes,
Mike

Bug#852245: python2-pyro4: Pyro4 require python selectors or selectors34 which are unavailable

[Marcin Kulisz]

Package: python2-pyro4
Version: 4.53-1
Severity: grave
Justification: renders package unusable

When trying to import Pyro4 in python2.7 following pops up (example is from
ipython but exactly the same output is from the app when trying to use it):

In [1]: import Pyro4
---
ImportError   Traceback (most recent call last)
 in ()
> 1 import Pyro4

/usr/lib/python2.7/dist-packages/Pyro4/__init__.pyc in ()
 64
 65 # import the required Pyro symbols into this package
---> 66 from Pyro4.core import URI, Proxy, Daemon, callback, batch, async, 
oneway, expose, behavior, current_context
 67 from Pyro4.naming import locateNS, resolve
 68 from Pyro4.futures import Future

/usr/lib/python2.7/dist-packages/Pyro4/core.py in ()
 19 from Pyro4 import errors, threadutil, socketutil, util, constants, 
message
 20 from Pyro4.socketserver.threadpoolserver import SocketServer_Threadpool
---> 21 from Pyro4.socketserver.multiplexserver import SocketServer_Multiplex
 22
 23 __all__ = ["URI", "Proxy", "Daemon", "current_context", "callback", 
"batch", "async", "expose", "behavior", "oneway"]

/usr/lib/python2.7/dist-packages/Pyro4/socketserver/multiplexserver.py in 
()
 16 import selectors
 17 except ImportError:
---> 18 import selectors34 as selectors
 19 from Pyro4 import socketutil, errors, util
 20 import Pyro4.constants

ImportError: No module named selectors34


'selectors34' is a backport of python3.4 'selectors' to python2.7, which is
replacement for python2.7 'select'.
Problem is that 'selectors34' is not packaged thus not available in Stretch and
I'm afraid it's too late for it to be allowed in.

Therefore I see following options:
1. Revert python2-pyro4 (src:Pyro4) to 4.43-1 this one is using 'select' thus
  doesn't require 'selectors34'.
2. Patch 4.53-1 with something like this:

if sys.version_info[:2] == (2,7):
   import select as selectors
else:
import selectors

in the socetserver/multiplexserver.py instead of try except for importing it
and purge requires.txt file from the egg-info.

3. Package selectors34 and convince release managers to allow it in.

Processed: Move to the correct package

[Debian Bug Tracking System]

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

> reassign 653959 citadel-server 8.14-2
Bug #653959 [src:citadel-server] citadel-server was auto-selected and installed 
by dist-upgrade for what appears to be no good reason, and apt-get purge 
citadel-server failed to back out all system changes
Warning: Unknown package 'src:citadel-server'
Bug reassigned from package 'src:citadel-server' to 'citadel-server'.
Ignoring request to alter found versions of bug #653959 to the same values 
previously set
Ignoring request to alter fixed versions of bug #653959 to the same values 
previously set
Bug #653959 [citadel-server] citadel-server was auto-selected and installed by 
dist-upgrade for what appears to be no good reason, and apt-get purge 
citadel-server failed to back out all system changes
Marked as found in versions citadel/8.14-2.
> thanks
Stopping processing here.

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

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Sylvestre Ledru]

Le 22/01/2017 à 21:02, Lisandro Damián Nicanor Pérez Meyer a écrit :
> Control: tag -1 patch
>
> I'm attaching a patch based on Rebecca's. I simply used a CMake variable to 
> avoid harcoding a path. Note it's the patch itself and not a debdiff: you 
> need 
> to add it to quilt's series file.
OK, you haven't pass the arg to LDFLAGS to make sure that libclang or
liblldb get it,
is that on purpose?
> Sylvestre: if you can please try to build this one too. Once built there are 
> two things to test:
>
> - Are the symbols versioned? For this creating a temporary symbols files is 
> enough. Ping me if you don't know how to do this.
Just libclang is (the C lib).
I haven't done it for the rest because it is C++ and not commitment
from upstream on API stability  (on contraire)
> - Install and test LLVM 3.9 with stuff built with previous versions, like for 
> example kdevelop ;-) Everything should just work.
>
> Of course I'm also trying to do this myself but if you can try it yourself 
> the 
> better.
Thanks. Julien also mentioned that we should bump shlibs.

S




signature.asc
Description: OpenPGP digital signature

Bug#765504: marked as done (xshisen: segfaults on program start (i386))

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 20:54:18 +
with message-id 
and subject line Bug#765504: fixed in xshisen 1:1.51-5
has caused the Debian Bug report #765504,
regarding xshisen: segfaults on program start (i386)
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.)


-- 
765504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xshisen
Version: 1:1.51-4.1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
unknown

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
installed xshisen in a VBox VM running up-to-date Jessie/i386 with lxde-core 
via apt-get
tried to start the program via lxterminal by invoking 'xshisen'

   * What was the outcome of this action?
xshisen window briefly (<1sec) appears with an empty green background
program crashes with segmentation fault

   * What outcome did you expect instead?
proper start of xshisen

   ** additional info
xshisen starts properly in a Jessie/amd64 VM


*** End of the template - remove these template lines ***


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

Kernel: Linux 3.16-2-686-pae (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

Versions of packages xshisen depends on:
ii  libc6   2.19-11
ii  libgcc1 1:4.9.1-15
ii  libice6 2:1.0.9-1
ii  libsm6  2:1.2.2-1
ii  libstdc++6  4.9.1-15
ii  libx11-62:1.6.2-3
ii  libxm4  2.3.4-5+b1
ii  libxmu6 2:1.1.2-1
ii  libxpm4 1:3.5.11-1
ii  libxt6  1:1.1.4-1

xshisen recommends no packages.

xshisen suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xshisen
Source-Version: 1:1.51-5

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated xshisen package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Jan 2017 20:57:48 +0100
Source: xshisen
Binary: xshisen
Architecture: source
Version: 1:1.51-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 xshisen- Shisen-sho puzzle game for X11
Closes: 675005 738081 765504 833581
Changes:
 xshisen (1:1.51-5) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to the QA team. (Closes: #675005)
   * Fix segfault on start on i386 et al, thanks Alexey Shilin.
 (Closes: #765504)
   * Make the build reproducible. (Closes: #833581)
   * Provide a desktop menu entry, no icon yet. (Closes: #738081)
Checksums-Sha1:
 7c8d406feab676589fccb83632cc149214d72fa1 1497 xshisen_1.51-5.dsc
 f5ef0c362618d3c3a86a7f5fecad86d4eabc48c8 11628 xshisen_1.51-5.debian.tar.xz
Checksums-Sha256:
 3a591b6ea94922b6a60568a50372df23bbc72c30f619be9d2ffe70a5d4738b2a 1497 
xshisen_1.51-5.dsc
 4a9421500475cf04a0cb32de033bab2f400723d9255e8e103ccbf9f99c025f7c 11628 
xshisen_1.51-5.debian.tar.xz
Files:
 22028498e057e05e569d91125360ac18 1497 games optional xshisen_1.51-5.dsc
 af64b1c2eecd966a3572636482101df4 11628 games optional 
xshisen_1.51-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFIBAEBCAAyFiEE/Zzi2Nd1S3irJ5u9LDtDb+rGgQEFAliFEYsUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQLDtDb+rGgQGsNAf/bNSDebhfWWapmMkaZEyywdcMSLHc
Cc2JQcmYSpNULV8FnLJlXmUgKVJXflt3SE1rKIibSjEW0JsUMMbTyCIWllm5Dqi+
/LCg/7KBV8diSriNBAo+oTMS1yeIwYv82zNMm2T8iuPZdJfKXxOz8TAXu8bSDKLt
L4nv3QzXtLAAohEKCejFMpblcnv7HVJW/UlUq2MXG6uwB5Dl4tD8zRfAo0n75nlX
8qPPPC8gHOr9Pw+YjOjKb6R6fq3tf6tjZGWoCB+cX4bWUUlU1Xha4PzQtUDsGDWX
vPle+7VKHl5qJ9+DuwSYfmQB0TkyPI1+3C5Xdnq4EaQ6rJIlLTDvaBZhVg==
=kaXF
-END PGP SIGNATURE End Message ---

Bug#840931: marked as done (libimobiledevice4 GnuTLS settings broken with iOS 10)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 20:51:21 +
with message-id 
and subject line Bug#840931: fixed in libimobiledevice 1.2.0+dfsg-3.1
has caused the Debian Bug report #840931,
regarding libimobiledevice4 GnuTLS settings broken with iOS 10
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.)


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

Package: libimobiledevice4
Version: 1.1.6+dfsg-3.1

On devices (iPhones) upgraded to iOS 10, there are errors that prevent 
connecting. I did not find this in deb bugs.


This was fixed in master upstream, using TLS1.0 instead of SSL3.0. We 
should really get this fixed in jessie (in 1.1.6), otherwise iOS 10 
devices become unusable with Debian.


Requires two commits:
13bf235cac2201747de11652cf14fe2714ca0718
72643b2b83990b9cf97cc84b285b30763d44a72d

After these, rebuilding and reinstalling, the iOS 10 devices works fine 
for me.


Nathan

Patch:
--- libimobiledevice-1.1.6+dfsg.orig/src/idevice.c
+++ libimobiledevice-1.1.6+dfsg/src/idevice.c
@@ -777,7 +777,7 @@ idevice_error_t idevice_connection_enabl
 }
 BIO_set_fd(ssl_bio, (int)(long)connection->data, BIO_NOCLOSE);

-SSL_CTX *ssl_ctx = SSL_CTX_new(SSLv3_method());
+SSL_CTX *ssl_ctx = SSL_CTX_new(TLSv1_method());
 if (ssl_ctx == NULL) {
 debug_info("ERROR: Could not create SSL context.");
 BIO_free(ssl_bio);
@@ -838,7 +838,7 @@ idevice_error_t idevice_connection_enabl
gnutls_certificate_allocate_credentials(_data_loc->certificate);
gnutls_certificate_client_set_retrieve_function(ssl_data_loc->certificate, 
internal_cert_callback);

 gnutls_init(_data_loc->session, GNUTLS_CLIENT);
-gnutls_priority_set_direct(ssl_data_loc->session, 
"NONE:+VERS-SSL3.0:+ANON-DH:+RSA:+AES-128-CBC:+AES-256-CBC:+SHA1:+MD5:+COMP-NULL", 
NULL);
+gnutls_priority_set_direct(ssl_data_loc->session, 
"NONE:+VERS-TLS1.0:+ANON-DH:+RSA:+AES-128-CBC:+AES-256-CBC:+SHA1:+MD5:+COMP-NULL", 
NULL);
 gnutls_credentials_set(ssl_data_loc->session, 
GNUTLS_CRD_CERTIFICATE, ssl_data_loc->certificate);

 gnutls_session_set_ptr(ssl_data_loc->session, ssl_data_loc);
--- End Message ---
--- Begin Message ---
Source: libimobiledevice
Source-Version: 1.2.0+dfsg-3.1

We believe that the bug you reported is fixed in the latest version of
libimobiledevice, 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.
Nicolas Boulenguez  (supplier of updated libimobiledevice 
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, 03 Jan 2017 01:32:36 +0100
Source: libimobiledevice
Binary: libimobiledevice6 libimobiledevice-dev libimobiledevice6-dbg 
python-imobiledevice libimobiledevice-utils libimobiledevice-doc
Architecture: source
Version: 1.2.0+dfsg-3.1
Distribution: unstable
Urgency: medium
Maintainer: gtkpod Maintainers 
Changed-By: Nicolas Boulenguez 
Description:
 libimobiledevice-dev - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice-doc - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice-utils - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice6 - Library for communicating with the iPhone and iPod Touch
 libimobiledevice6-dbg - Library for communicating with iPhone and iPod Touch 
devices
 python-imobiledevice - Library for communicating with iPhone and iPod Touch 
devices
Closes: 840931 847977
Changes:
 libimobiledevice (1.2.0+dfsg-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upstream commits replacing SSL3.0 with TLS1.0. Closes: #840931, #847977.
 Also fix related bug in GNUTLS pairing record generation, see
 https://github.com/libimobiledevice/libimobiledevice/issues/413.
Checksums-Sha1:
 c781204295f3ea7b818031806730281cbbbc9b0d 2782 
libimobiledevice_1.2.0+dfsg-3.1.dsc
 16544820115a968fc086f310767864bf63cc92ac 14668 

Bug#847977: marked as done (libimobiledevice6: GnuTLS error: Error in the pull function (iOS 10.1.1))

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 20:51:21 +
with message-id 
and subject line Bug#840931: fixed in libimobiledevice 1.2.0+dfsg-3.1
has caused the Debian Bug report #840931,
regarding libimobiledevice6: GnuTLS error: Error in the pull function (iOS 
10.1.1)
to be marked as done.

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

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


-- 
840931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libimobiledevice6
Version: 1.2.0+dfsg-3
Severity: important

Hello,

Library does not work with iOS 10.1.1.

```
$ ideviceinfo 
GnuTLS error: Error in the pull function.
ERROR: Could not connect to lockdownd, error code -5
```

This is probably relevant:

https://github.com/libimobiledevice/libimobiledevice/issues/413


Thanks,

George

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

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

Versions of packages libimobiledevice6 depends on:
ii  libc62.24-8
ii  libgcrypt20  1.7.3-2
ii  libgnutls30  3.5.7-2
ii  libplist31.12-3.1
ii  libtasn1-6   4.9-4
ii  libusbmuxd4  1.0.10-3

Versions of packages libimobiledevice6 recommends:
ii  usbmuxd  1.1.0-2+b1

Versions of packages libimobiledevice6 suggests:
pn  libusbmuxd-tools  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libimobiledevice
Source-Version: 1.2.0+dfsg-3.1

We believe that the bug you reported is fixed in the latest version of
libimobiledevice, 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.
Nicolas Boulenguez  (supplier of updated libimobiledevice 
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, 03 Jan 2017 01:32:36 +0100
Source: libimobiledevice
Binary: libimobiledevice6 libimobiledevice-dev libimobiledevice6-dbg 
python-imobiledevice libimobiledevice-utils libimobiledevice-doc
Architecture: source
Version: 1.2.0+dfsg-3.1
Distribution: unstable
Urgency: medium
Maintainer: gtkpod Maintainers 
Changed-By: Nicolas Boulenguez 
Description:
 libimobiledevice-dev - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice-doc - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice-utils - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice6 - Library for communicating with the iPhone and iPod Touch
 libimobiledevice6-dbg - Library for communicating with iPhone and iPod Touch 
devices
 python-imobiledevice - Library for communicating with iPhone and iPod Touch 
devices
Closes: 840931 847977
Changes:
 libimobiledevice (1.2.0+dfsg-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upstream commits replacing SSL3.0 with TLS1.0. Closes: #840931, #847977.
 Also fix related bug in GNUTLS pairing record generation, see
 https://github.com/libimobiledevice/libimobiledevice/issues/413.
Checksums-Sha1:
 c781204295f3ea7b818031806730281cbbbc9b0d 2782 
libimobiledevice_1.2.0+dfsg-3.1.dsc
 16544820115a968fc086f310767864bf63cc92ac 14668 
libimobiledevice_1.2.0+dfsg-3.1.debian.tar.xz
Checksums-Sha256:
 cf7debc5ea75d9586a4af547672348d8b1dd19ef3737cc3708272c6a513f0802 2782 
libimobiledevice_1.2.0+dfsg-3.1.dsc
 a38d5b79fcbde163ef54bbd2971b000e2e7377befcbea2841ec0d7720a20cc9d 14668 
libimobiledevice_1.2.0+dfsg-3.1.debian.tar.xz
Files:
 925b73d93a511815eb752f8154abd3c4 2782 libs optional 
libimobiledevice_1.2.0+dfsg-3.1.dsc
 8c84aa85903c4fce0be65728f0c20345 14668 libs optional 
libimobiledevice_1.2.0+dfsg-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAliCa/sTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jZmTEACNQ7MMgZXNTAQqNVIoDz75Xsv+qXBY

Bug#847977: marked as done (libimobiledevice6: GnuTLS error: Error in the pull function (iOS 10.1.1))

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 20:51:21 +
with message-id 
and subject line Bug#847977: fixed in libimobiledevice 1.2.0+dfsg-3.1
has caused the Debian Bug report #847977,
regarding libimobiledevice6: GnuTLS error: Error in the pull function (iOS 
10.1.1)
to be marked as done.

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

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


-- 
847977: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libimobiledevice6
Version: 1.2.0+dfsg-3
Severity: important

Hello,

Library does not work with iOS 10.1.1.

```
$ ideviceinfo 
GnuTLS error: Error in the pull function.
ERROR: Could not connect to lockdownd, error code -5
```

This is probably relevant:

https://github.com/libimobiledevice/libimobiledevice/issues/413


Thanks,

George

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

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

Versions of packages libimobiledevice6 depends on:
ii  libc62.24-8
ii  libgcrypt20  1.7.3-2
ii  libgnutls30  3.5.7-2
ii  libplist31.12-3.1
ii  libtasn1-6   4.9-4
ii  libusbmuxd4  1.0.10-3

Versions of packages libimobiledevice6 recommends:
ii  usbmuxd  1.1.0-2+b1

Versions of packages libimobiledevice6 suggests:
pn  libusbmuxd-tools  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libimobiledevice
Source-Version: 1.2.0+dfsg-3.1

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated libimobiledevice 
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, 03 Jan 2017 01:32:36 +0100
Source: libimobiledevice
Binary: libimobiledevice6 libimobiledevice-dev libimobiledevice6-dbg 
python-imobiledevice libimobiledevice-utils libimobiledevice-doc
Architecture: source
Version: 1.2.0+dfsg-3.1
Distribution: unstable
Urgency: medium
Maintainer: gtkpod Maintainers 
Changed-By: Nicolas Boulenguez 
Description:
 libimobiledevice-dev - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice-doc - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice-utils - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice6 - Library for communicating with the iPhone and iPod Touch
 libimobiledevice6-dbg - Library for communicating with iPhone and iPod Touch 
devices
 python-imobiledevice - Library for communicating with iPhone and iPod Touch 
devices
Closes: 840931 847977
Changes:
 libimobiledevice (1.2.0+dfsg-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upstream commits replacing SSL3.0 with TLS1.0. Closes: #840931, #847977.
 Also fix related bug in GNUTLS pairing record generation, see
 https://github.com/libimobiledevice/libimobiledevice/issues/413.
Checksums-Sha1:
 c781204295f3ea7b818031806730281cbbbc9b0d 2782 
libimobiledevice_1.2.0+dfsg-3.1.dsc
 16544820115a968fc086f310767864bf63cc92ac 14668 
libimobiledevice_1.2.0+dfsg-3.1.debian.tar.xz
Checksums-Sha256:
 cf7debc5ea75d9586a4af547672348d8b1dd19ef3737cc3708272c6a513f0802 2782 
libimobiledevice_1.2.0+dfsg-3.1.dsc
 a38d5b79fcbde163ef54bbd2971b000e2e7377befcbea2841ec0d7720a20cc9d 14668 
libimobiledevice_1.2.0+dfsg-3.1.debian.tar.xz
Files:
 925b73d93a511815eb752f8154abd3c4 2782 libs optional 
libimobiledevice_1.2.0+dfsg-3.1.dsc
 8c84aa85903c4fce0be65728f0c20345 14668 libs optional 
libimobiledevice_1.2.0+dfsg-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEYtlNMqmXIhEvWffytSqc9EkN/I0FAliCa/sTHG5pY29sYXNA
ZGViaWFuLm9yZwAKCRC1Kpz0SQ38jZmTEACNQ7MMgZXNTAQqNVIoDz75Xsv+qXBY

Bug#840931: marked as done (libimobiledevice4 GnuTLS settings broken with iOS 10)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 20:51:21 +
with message-id 
and subject line Bug#847977: fixed in libimobiledevice 1.2.0+dfsg-3.1
has caused the Debian Bug report #847977,
regarding libimobiledevice4 GnuTLS settings broken with iOS 10
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.)


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

Package: libimobiledevice4
Version: 1.1.6+dfsg-3.1

On devices (iPhones) upgraded to iOS 10, there are errors that prevent 
connecting. I did not find this in deb bugs.


This was fixed in master upstream, using TLS1.0 instead of SSL3.0. We 
should really get this fixed in jessie (in 1.1.6), otherwise iOS 10 
devices become unusable with Debian.


Requires two commits:
13bf235cac2201747de11652cf14fe2714ca0718
72643b2b83990b9cf97cc84b285b30763d44a72d

After these, rebuilding and reinstalling, the iOS 10 devices works fine 
for me.


Nathan

Patch:
--- libimobiledevice-1.1.6+dfsg.orig/src/idevice.c
+++ libimobiledevice-1.1.6+dfsg/src/idevice.c
@@ -777,7 +777,7 @@ idevice_error_t idevice_connection_enabl
 }
 BIO_set_fd(ssl_bio, (int)(long)connection->data, BIO_NOCLOSE);

-SSL_CTX *ssl_ctx = SSL_CTX_new(SSLv3_method());
+SSL_CTX *ssl_ctx = SSL_CTX_new(TLSv1_method());
 if (ssl_ctx == NULL) {
 debug_info("ERROR: Could not create SSL context.");
 BIO_free(ssl_bio);
@@ -838,7 +838,7 @@ idevice_error_t idevice_connection_enabl
gnutls_certificate_allocate_credentials(_data_loc->certificate);
gnutls_certificate_client_set_retrieve_function(ssl_data_loc->certificate, 
internal_cert_callback);

 gnutls_init(_data_loc->session, GNUTLS_CLIENT);
-gnutls_priority_set_direct(ssl_data_loc->session, 
"NONE:+VERS-SSL3.0:+ANON-DH:+RSA:+AES-128-CBC:+AES-256-CBC:+SHA1:+MD5:+COMP-NULL", 
NULL);
+gnutls_priority_set_direct(ssl_data_loc->session, 
"NONE:+VERS-TLS1.0:+ANON-DH:+RSA:+AES-128-CBC:+AES-256-CBC:+SHA1:+MD5:+COMP-NULL", 
NULL);
 gnutls_credentials_set(ssl_data_loc->session, 
GNUTLS_CRD_CERTIFICATE, ssl_data_loc->certificate);

 gnutls_session_set_ptr(ssl_data_loc->session, ssl_data_loc);
--- End Message ---
--- Begin Message ---
Source: libimobiledevice
Source-Version: 1.2.0+dfsg-3.1

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

Debian distribution maintenance software
pp.
Nicolas Boulenguez  (supplier of updated libimobiledevice 
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, 03 Jan 2017 01:32:36 +0100
Source: libimobiledevice
Binary: libimobiledevice6 libimobiledevice-dev libimobiledevice6-dbg 
python-imobiledevice libimobiledevice-utils libimobiledevice-doc
Architecture: source
Version: 1.2.0+dfsg-3.1
Distribution: unstable
Urgency: medium
Maintainer: gtkpod Maintainers 
Changed-By: Nicolas Boulenguez 
Description:
 libimobiledevice-dev - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice-doc - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice-utils - Library for communicating with iPhone and iPod Touch 
devices
 libimobiledevice6 - Library for communicating with the iPhone and iPod Touch
 libimobiledevice6-dbg - Library for communicating with iPhone and iPod Touch 
devices
 python-imobiledevice - Library for communicating with iPhone and iPod Touch 
devices
Closes: 840931 847977
Changes:
 libimobiledevice (1.2.0+dfsg-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Upstream commits replacing SSL3.0 with TLS1.0. Closes: #840931, #847977.
 Also fix related bug in GNUTLS pairing record generation, see
 https://github.com/libimobiledevice/libimobiledevice/issues/413.
Checksums-Sha1:
 c781204295f3ea7b818031806730281cbbbc9b0d 2782 
libimobiledevice_1.2.0+dfsg-3.1.dsc
 16544820115a968fc086f310767864bf63cc92ac 14668 

Processed: Missing dependency is RC

[Debian Bug Tracking System]

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

> severity 739864 serious
Bug #739864 [libvorbisidec-dev] libvorbisidec-dev needs libogg-dev
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#852092: marked as done (eztrace-contrib: FTBFS since nvidia-cuda-toolkit switched from gcc-5 to clang-3.8)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 20:50:20 +
with message-id 
and subject line Bug#852092: fixed in eztrace-contrib 1.1-5-5
has caused the Debian Bug report #852092,
regarding eztrace-contrib: FTBFS since nvidia-cuda-toolkit switched from gcc-5 
to clang-3.8
to be marked as done.

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

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


-- 
852092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hwloc-contrib
Version: 1.11.5-1
Severity: serious
Justification: fails to build from source

Hi,

please check whether you can get hwloc-contrib (partially) built with
clang-3.8, e.g. using

  nvcc -ccbin clang-3.8

The dependency change in nvidia-cuda-toolkit was done since gcc-5 is
planned to be removed from stretch and cuda does not support gcc-6.


Andreas
--- End Message ---
--- Begin Message ---
Source: eztrace-contrib
Source-Version: 1.1-5-5

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated eztrace-contrib 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Jan 2017 21:02:31 +0100
Source: eztrace-contrib
Binary: libeztrace0-contrib
Architecture: source amd64
Version: 1.1-5-5
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 libeztrace0-contrib - Automatic execution trace generation for HPC - 
development files
Closes: 852092
Changes:
 eztrace-contrib (1.1-5-5) unstable; urgency=medium
 .
   * patches/nvcc: Take into account NVCCFLAGS, and pass -ccbin clang-3.8
 there (Closes: #852092).
   * control: Build-Depend on clang-3.8.
Checksums-Sha1:
 a38aa644f446973214af757e4359f82047476825 2353 eztrace-contrib_1.1-5-5.dsc
 20a7fa0681e86112c03180b62d41afbd25060db5 11380 
eztrace-contrib_1.1-5-5.debian.tar.xz
 baf3000f7d5466e0a37a75540f6616172348b447 8931 
eztrace-contrib_1.1-5-5_amd64.buildinfo
 d5723b37214c78bdb1c9a3744af1449ecaacc173 81826 
libeztrace0-contrib-dbgsym_1.1-5-5_amd64.deb
 db7f620c0d0e3c5c917a6e63c3ec885543c60286 81026 
libeztrace0-contrib_1.1-5-5_amd64.deb
Checksums-Sha256:
 4ee66686da573308b28d3e1ab469aa52ee542501917e9590ddd0ec9eadb37807 2353 
eztrace-contrib_1.1-5-5.dsc
 0f6304f8c903a7c637ab3ede6ac742e5447badc24a09bd1c7637cd175e018e90 11380 
eztrace-contrib_1.1-5-5.debian.tar.xz
 5bf88be1e6db60334fa5573f5ead85c1be7ba7ad69b1e29752309f68ca5559cd 8931 
eztrace-contrib_1.1-5-5_amd64.buildinfo
 cf489554a6e280c79d1c66acdb8b109d01b8cb2b1eb29aa95a7ef99d94374856 81826 
libeztrace0-contrib-dbgsym_1.1-5-5_amd64.deb
 6d6bc1f9bca8560db0077e1002b9e2771b1a624b9722247db4876cf0d5ff28ca 81026 
libeztrace0-contrib_1.1-5-5_amd64.deb
Files:
 09634b4453a9f29d2de68ec2cc45e67c 2353 contrib/devel extra 
eztrace-contrib_1.1-5-5.dsc
 db5dfff9cdeaba23e8eeb2877c0d7a7c 11380 contrib/devel extra 
eztrace-contrib_1.1-5-5.debian.tar.xz
 e97f30404d20b60350ec976a4697 8931 contrib/devel extra 
eztrace-contrib_1.1-5-5_amd64.buildinfo
 6d71c716717d159c7ac2dc4a0fc20c94 81826 contrib/debug extra 
libeztrace0-contrib-dbgsym_1.1-5-5_amd64.deb
 96e27a7030dc71f3b32ac7b8cad42258 81026 contrib/libs extra 
libeztrace0-contrib_1.1-5-5_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEaw+sIYVmRulKotIAoAMZaCdBSIAFAliFEGUACgkQoAMZaCdB
SIBuvA//curWjfU370WVfodg87gmkwyykcUpyeoyi/Mv6qcve9oMKrRQGYmX2r5z
DoWC85AxzHq9v4PqsE8KAbKibfbwcQRioXygmtbERlaShIlhu+JkbtVxzOnAf1gn
iffIuH6r8Ek3RuQdyeH9U/6GjydjhMHaLasbC9SOjqO8iDVPIEGayNHo2yGW3ecY
ryESzv3Eqx+guuKQYHFAOn/Dz8aep9RLK09L5f04a6cj5biPcKnzPM1uCVSoCCxp
8AqIxCH78gVhMin27GyL+iTG9gV28tg3ky+Pb2YBr8yMlv9jxL0luNQnoQ2DBhCB
Dop8PDFxyeJo/9nh9gWPNJIPIrWE4zQ4xs+WP+59ODQT3+6/zrWc634ymT1cgSvF
UuWyhQ/I9gKRIJDv8JE78OfvOx9ENFxsKPEHCFdW42/OAejfhJ1+xvKiYfywUNUN
a1446dTMePHlDFr0RQiKav8bBkL0BXjKkKqaWrTuq+1/P3Ya2Q8WzuEuoFZ0waqX
Jzhh4Vdu2GElJVBwfKy0BR+K1T6ClsLi4sWiAv37sWvLNiucHlIUsd7nIYb8B0uB

Processed: Version tracking fixes

[Debian Bug Tracking System]

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

> found 851997 2.4.0-1
Bug #851997 [jabberd2] No TLS encryption possible
Marked as found in versions jabberd2/2.4.0-1.
> notfound 651291 20111203-1
Bug #651291 [gcc-snapshot] gcc-snapshot contains evil gfdl licensed man pages
No longer marked as found in versions gcc-snapshot/20111203-1.
> notfound 653959 wheezy
Bug #653959 [src:citadel-server] citadel-server was auto-selected and installed 
by dist-upgrade for what appears to be no good reason, and apt-get purge 
citadel-server failed to back out all system changes
Warning: Unknown package 'src:citadel-server'
The source 'citadel-server' and version 'wheezy' do not appear to match any 
binary packages
No longer marked as found in versions citadel-server/wheezy.
Warning: Unknown package 'src:citadel-server'
> thanks
Stopping processing here.

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

Bug#670981: marked as done (proftpd-basic: fail to configuration file proftpd.conf and unable to determine IP)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 22:28:02 +0200
with message-id <20170122202802.p6hhoifnkeke6qfy@localhost>
and subject line No answer to request for more information
has caused the Debian Bug report #670981,
regarding proftpd-basic: fail to configuration file proftpd.conf and unable to 
determine IP
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.)


-- 
670981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: proftpd-basic
Version: 1.3.4a-2
Severity: serious
Tags: patch
Justification: fails to build from source

Dear Maintainer,
Hi, proftpd-basic failure to be installed, I installed by compiling and
downloading the source code. The faults are:
[Number]: warning: unable to determine IP address of 'hostname'
[Number]: error: no valid servers configured
[Number]: Fatal: error processing configuration file '/ usr / local / etc /
proftpd.conf'



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

Kernel: Linux 3.3.2 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
The submitter didn't answer to the request for more information.

cu
Adrian

-- 

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

Bug#852020: marked as done (libpng12.so.0: Unable to install upgrade)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 22:22:35 +0200
with message-id <20170122202235.i2ctrbfmopixx2zq@localhost>
and subject line Re: Bug#852020: Further Investigation
has caused the Debian Bug report #852020,
regarding libpng12.so.0: Unable to install upgrade
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.)


-- 
852020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpng12-0
Version: 1.2.50-2+deb8u2
Severity: grave
File: libpng12.so.0
Justification: renders package unusable

Dear Maintainer,

I was unable to upgrade the package yesterday and today as it tells me it can 
not install a new version of /usr/lib/x86_64-linux-gnu/libpng12.so.0 because 
the file was not found.


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

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

Versions of packages libpng12-0:amd64 depends on:
ii  libc6  2.19-18+deb8u7
ii  multiarch-support  2.19-18+deb8u7
ii  zlib1g 1:1.2.8.dfsg-2+b1

libpng12-0:amd64 recommends no packages.

libpng12-0:amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Control: reassign -1 usrmerge

On Sun, Jan 22, 2017 at 03:22:49AM +0100, Bachsau wrote:
> I further investigated this error and it seems it has to do with my system
> already using the new directory structure, where /lib is symlinked to
> /usr/lib and your packages tries to place an aditional symlink in
> /usr/lib/x86_64-linux-gnu/libpng12.so.0 which would then link to itself.
> However, /usr/lib is never accessed when loading x86_64-linux-gnu libraries,
> so it should be save to remove this part from the package.

Thanks for the update.

Merged /usr is mostly working in stretch.

Merged /usr is not supported at all in jessie,
and it is not a surprise when something breaks.

The latest usrmerge package in stretch already conflicts with
libpng12-0 (<< 1.2.54-4~), so this is already fixed there.

cu
Adrian

-- 

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

Processed: Version tracking fix

[Debian Bug Tracking System]

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

> found 848303 1.8-1.1
Bug #848303 [electrum] electrum: Transactions not accepted by network
Marked as found in versions electrum/1.8-1.1.
> thanks
Stopping processing here.

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

Bug#852092: hwloc-contrib: FTBFS since nvidia-cuda-toolkit switched from gcc-5 to clang-3.8

[Andreas Beckmann]

On 2017-01-22 17:59, Samuel Thibault wrote:
> hwloc-contrib doesn't actually use nvcc, it just uses some headers and
> links against libcudart

I messed up and filed it against the next package I was testing, the
actual failure is in extrace-contrib ... bug was immediately retitled
and reassigned


andreas

Bug#852092: hwloc-contrib: FTBFS since nvidia-cuda-toolkit switched from gcc-5 to clang-3.8

[Samuel Thibault]

Control: tags -1 + pending

Samuel Thibault, on Sun 22 Jan 2017 17:59:40 +0100, wrote:
> Andreas Beckmann, on Sat 21 Jan 2017 17:18:39 +0100, wrote:
> > Justification: fails to build from source
> 
> Err, does it really?  I've just tried with an updated pbuilder, with
> nvidia-cuda-dev 8.0.44-3, and that indeed didn't pull gcc-5.

Ok, so it was actually meant for eztrace-contrib :) I have uploaded a
fixed package.

Samuel

Processed: Re: Bug#852092: hwloc-contrib: FTBFS since nvidia-cuda-toolkit switched from gcc-5 to clang-3.8

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #852092 [src:eztrace-contrib] eztrace-contrib: FTBFS since 
nvidia-cuda-toolkit switched from gcc-5 to clang-3.8
Added tag(s) pending.

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

Processed: Re: Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #848368 [src:llvm-toolchain-3.9] llvm-toolchain-3.9: Please add ELF symbols 
versions to the libraries
Ignoring request to alter tags of bug #848368 to the same tags previously set

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

Bug#848368: llvm-toolchain-3.9: Please add ELF symbols versions to the libraries

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 patch

I'm attaching a patch based on Rebecca's. I simply used a CMake variable to 
avoid harcoding a path. Note it's the patch itself and not a debdiff: you need 
to add it to quilt's series file.

I'm trying to get LLVM built into barriere.d.o. So far I've got to test 
failing but definitely due to non-related stuff, one due to a filesystem thing 
(maybe the host ran out of space for a moment?) and the other one due to lack 
of fakeroot on my side while running the tests, which I'm trying to re do now.

Sylvestre: if you can please try to build this one too. Once built there are 
two things to test:

- Are the symbols versioned? For this creating a temporary symbols files is 
enough. Ping me if you don't know how to do this.

- Install and test LLVM 3.9 with stuff built with previous versions, like for 
example kdevelop ;-) Everything should just work.

Of course I'm also trying to do this myself but if you can try it yourself the 
better.

Cheers, Lisandro.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
Description: add a simple linker script to version LLVM symbols
 This patch adds a very simple linker script to version the lib's symbols
 and thus trying to avoid crashes if an application loads two different
 LLVM versions (as long as they do not share data between them).
Author: Rebecca N. Palmer 
Author: Lisandro Damían Nicanor Pérez Meyer 
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848368

---
 tools/llvm-shlib/CMakeLists.txt|2 +-
 tools/llvm-shlib/simple_version_script.map |1 +
 2 files changed, 2 insertions(+), 1 deletion(-)

Index: llvm-toolchain-3.9-3.9.1/tools/llvm-shlib/CMakeLists.txt
===
--- llvm-toolchain-3.9-3.9.1.orig/tools/llvm-shlib/CMakeLists.txt
+++ llvm-toolchain-3.9-3.9.1/tools/llvm-shlib/CMakeLists.txt
@@ -42,7 +42,7 @@ set_property(TARGET LLVM PROPERTY VERSIO
 list(REMOVE_DUPLICATES LIB_NAMES)
 if("${CMAKE_SYSTEM_NAME}" STREQUAL "Linux" OR "${CMAKE_SYSTEM_NAME}" STREQUAL "GNU" OR "${CMAKE_SYSTEM_NAME}" STREQUAL "kFreeBSD") # FIXME: It should be "GNU ld for elf"
   # GNU ld doesn't resolve symbols in the version script.
-  set(LIB_NAMES -Wl,--whole-archive ${LIB_NAMES} -Wl,--no-whole-archive)
+  set(LIB_NAMES -Wl,--version-script,${CMAKE_CURRENT_SOURCE_DIR}/simple_version_script.map -Wl,--whole-archive ${LIB_NAMES} -Wl,--no-whole-archive)
 elseif("${CMAKE_SYSTEM_NAME}" STREQUAL "Darwin")
   set(LIB_NAMES -Wl,-all_load ${LIB_NAMES})
 endif()
Index: llvm-toolchain-3.9-3.9.1/tools/llvm-shlib/simple_version_script.map
===
--- /dev/null
+++ llvm-toolchain-3.9-3.9.1/tools/llvm-shlib/simple_version_script.map
@@ -0,0 +1 @@
+LLVM_3.9 { global: *; };


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

Processed: Bug also applies to stretch

[Debian Bug Tracking System]

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

> found 849333 0.5.7-1
Bug #849333 [src:faker] faker: Non-determistically FTBFS due to tests sometimes 
exposing UnboundLocalError
Marked as found in versions faker/0.5.7-1.
> found 849652 0.5.7-1
Bug #849652 [src:faker] faker: FTBFS on 32-bit: ValueError: timestamp out of 
range for platform time_t
Marked as found in versions faker/0.5.7-1.
> tags 833157 stretch
Bug #833157 [src:sugar-base-0.88] sugar-base-0.88: don't release with Stretch
Added tag(s) stretch.
> tags 832491 stretch
Bug #832491 [aboot] aboot: please remove build dependency on obsolete package sp
Added tag(s) stretch.
> tags 808654 stretch
Bug #808654 [src:fedmsg] fedmsg: FTBFS offline: Download error on 
https://pypi.python.org/simple/Twisted_Core/
Bug #827738 [src:fedmsg] fedmsg: Package unusable in sid 
(pkg_resources.DistributionNotFound: The 'Twisted_Core')
Added tag(s) stretch.
Added tag(s) stretch.
> tags 805660 stretch
Bug #805660 [src:datanommer.consumer] datanommer.consumer: FTBFS: 
test_duplicate_msg_id fails
Bug #812649 [src:datanommer.consumer] datanommer.consumer: FTBFS - 
AttributeError: assert_called_once
Added tag(s) stretch.
Added tag(s) stretch.
> tags 784181 stretch
Bug #784181 [src:razorqt] razorqt: Razor-Qt dead upstream, superseded by LXDE-Qt
Added tag(s) stretch.
> tags 749258 stretch
Bug #749258 [tunesviewer] tunesviewer: depends on python-webkit which is 
deprecated
Added tag(s) stretch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
749258: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749258
784181: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784181
805660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805660
808654: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808654
812649: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812649
827738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827738
832491: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832491
833157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833157
849333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849333
849652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#831236: marked as done (klog: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 21:51:51 +0200
with message-id <20170122195151.wkce2fmtfvoues3r@localhost>
and subject line This bug was fixed in 0.9.2.5-1
has caused the Debian Bug report #831236,
regarding klog: FTBFS: dh_install: missing files, aborting
to be marked as done.

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

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


-- 
831236: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: klog
Version: 0.9.2.3-1.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 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»'
> make[1]: Nothing to be done for 'install'.
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> touch debian/stamp-makefile-install
> Adding cdbs dependencies to debian/klog.substvars
> dh_installdirs -pklog \
>   
> # Install pixmaps.
> dh_install klog usr/bin
> dh_install: Cannot find (any matches for) "translations/*.qm" (tried in "." 
> and "debian/tmp")
> dh_install: klog missing files: translations/*.qm
> dh_install: missing files, aborting
> make: *** [install/klog] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/klog_0.9.2.3-1.1_unstable_gcc5.log

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

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


klog (0.9.2.5-1) unstable; urgency=medium

  * Included the translation files to fix the bug that prevents some builds. 
...
 -- Jaime Robles   Sat, 24 Dec 2016 15:40:48 +


cu
Adrian

-- 

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

Bug#852202: systemd 232-13 aborts during upgrade and subsequent boots

[David Taylor]

Hi Michael,

On Sun, 22 Jan 2017, Michael Biebl wrote:

Am 22.01.2017 um 18:20 schrieb David Taylor:

On Sun, 22 Jan 2017, Michael Biebl wrote:

Am 22.01.2017 um 14:14 schrieb David Taylor:


I built the systemd_232-13 package locally from source, so I'm not 
sure how useful the core file would be to you.  I have reproduced the

backtrace below.


If you built 232-13 from source, can you cherry-pick the upstream patch
and see if that fixes your issue? We might then cherry-pick that patch
in the official package as well.
I can prepare packages if you prefer that.


I cherry-picked the two commits referenced by the upstream issue #4747: 


d112eae7da77899be245ab52aa1747d4675549f1 device: Avoid calling unit_free(NULL) 
in device setup logic (#4748)
c9d5c9c0e19eea79ca0f09fe58e5c0b76b8001e2 core: make unit_free() accept NULL 
pointers

They have resolved the problem -- 232-13 plus those two patches is now 
running successfully on my machine.



The above bug report suggests a problem with unicode partition labels.
Do you have such a partition?


I didn't think so, but double-checking in /dev/disk/by-partlabel shows I do
have an NTFS partition with the label †††:

# ls -l /dev/disk/by-partlabel/
total 0
lrwxrwxrwx 1 root root 10 Jan 22 13:19
††† -> ../../sdb3


Ah, ok. So this is a dual boot system, I assume.


Yes, dual boot with Windows 10.


Is /dev/sdb3 the partition holding the actual Windows 10 system? [1]
suggests that the partition layout is System | MSR | Windows | Recovery


Yes, it's the main Windows partition.


If you boot Windows, what's the partion label shown there? Is it the
default label created by the Windows installer?


blkid shows:

/dev/sdb1: LABEL="SYSTEM" UUID="5C7A-5FAE" TYPE="vfat" PARTLABEL="EFI system 
partition" PARTUUID="8bc4e64e-f2b7-47da-8048-ab445242bf
/dev/sdb2: PARTLABEL="Microsoft reserved partition" 
PARTUUID="dd5c4d6d-dd1b-4908-b83e-e6b44d12ca63"
/dev/sdb3: LABEL="win550s" UUID="886450D76450C998" TYPE="ntfs" 
PARTLABEL="†††" PARTUUID="77178a46-30b6-11e5-9bd1-5ce0c5c724c2"

Windows displayes the volume label as win550s (which I set, manually when 
installing).

For some reason the GPT partition label has been set to †††, 
although the two other Windows partitions have sensible partition labels.


--
David Taylor

Bug#852238: [cantata] depends on libqt5sql5-sqlite

[HJ]

Package: cantata
Version: 2.0.1.ds1-1
Severity: grave

Hi,
without sqllite cantata will segfault afer reading the music libary

ssf@blackbox:~$ cantata
QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers:
Segmentation fault


--- System information. ---
Architecture:
Kernel: Linux 4.8.0-2-amd64

Debian Release: stretch/sid
500 unstable ftp.de.debian.org
500 testing ftp.de.debian.org
500 stable dl.google.com

--- Package information. ---
Depends (Version) | Installed
===-+-===
libavcodec57 (>= 7:3.0) | 7:3.2.2-1
OR libavcodec-extra57 (>= 7:3.0) |
libavformat57 (>= 7:3.0) | 7:3.2.2-1
libavutil55 (>= 7:3.0) | 7:3.2.2-1
libc6 (>= 2.14) | 2.24-8
libcddb2 | 1.3.2-5
libcdparanoia0 (>= 3.10.2+debian) | 3.10.2+debian-11
libebur128-1 (>= 1.1.0) | 1.2.0-1
libgcc1 (>= 1:3.0) | 1:6.3.0-2
libmpg123-0 (>= 1.6.2) | 1.23.8-1
libmtp9 (>= 1.1.3) | 1.1.12-1
libmusicbrainz5cc2v5 (>= 5.1) | 5.1.0+git20150707-6
libqt5concurrent5 (>= 5.0.2) | 5.7.1+dfsg-3
libqt5core5a (>= 5.5.0) | 5.7.1+dfsg-3
libqt5dbus5 (>= 5.0.2) | 5.7.1+dfsg-3
libqt5gui5 (>= 5.2.0) | 5.7.1+dfsg-3
libqt5network5 (>= 5.0.2) | 5.7.1+dfsg-3
libqt5sql5 (>= 5.0.2) | 5.7.1+dfsg-3
libqt5svg5 (>= 5.0.2) | 5.7.1~20161021-2
libqt5widgets5 (>= 5.2.0) | 5.7.1+dfsg-3
libqt5xml5 (>= 5.0.2) | 5.7.1+dfsg-3
libstdc++6 (>= 5.2) | 6.3.0-2
libtag-extras1 (>= 1.0.0) | 1.0.1-3.1
libtag1v5 (>= 1.9.1-2.4) | 1.11.1-0.1
libudev1 (>= 183) | 232-8
libvlc5 (>= 1.1.0) | 2.2.4-13
zlib1g (>= 1:1.1.4) | 1:1.2.8.dfsg-4


Recommends (Version) | Installed
==-+-===
liburi-perl | 1.71-1


Suggests (Version) | Installed
-+-===
mpd | 0.19.21-1
media-player-info |

Bug#852048: prospector: dependencies can't be satisfied in testing/sid

[Daniel Stender]

Control: retitle -1 pycodestyle >= 2.1.0 breaks prospector 0.12.4

[CC-ing the pycodestyle maintainers]

OUCH!

In the upstream repo it's said that there are API changes in pycodestyle > 2.0.0
= 2.1.0 [1], and therefore 2.0.0 is pinned. I've missed that, and also the 
DEP-8 tests
of prospector kept on succeeding.

I'm studying the CHANGES of pycodestyle [2] right now ... I think it's "change 
all references
... to say pycodestyle; #530".

BTW, there are API changes in pydocstyle (formerly pep257) > 1.0.0, that's also 
pinned and
I didn't updated that yet for that reason [3].

Daniel

[1] 
https://github.com/landscapeio/prospector/commit/95e09816534853616d42877dcb8b9dc0f71a38e8

[2] https://github.com/PyCQA/pycodestyle/blob/master/CHANGES.txt

[3] https://bugs.debian.org/846591 (pydocstyle: newer version available)

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/

Processed: prospector: dependencies can't be satisfied in testing/sid

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 pycodestyle >= 2.1.0 breaks prospector 0.12.4
Bug #852048 [prospector] prospector: dependencies can't be satisfied in 
testing/sid
Changed Bug title to 'pycodestyle >= 2.1.0 breaks prospector 0.12.4' from 
'prospector: dependencies can't be satisfied in testing/sid'.

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

Bug#851339: [Pkg-fonts-devel] Bug#851339: Bug#851339: Bug#851339: Bug#851339: fonts-firacode: package in Debian with non-Debian build dependencies

[Adam Borowski]

On Sun, Jan 22, 2017 at 09:02:09PM +0800, Paul Wise wrote:
> Ultimately we need something to change in the upstream fonts community
> though; either one of the existing font tools needs to add Glyphs
> support or Glyphsapp folks need to release some sort of free toolkit
> for it. Otherwise this is going to get annoying.

https://github.com/googlei18n/glyphsLib/issues/74

-- 
Autotools hint: to do a zx-spectrum build on a pdp11 host, type:
  ./configure --host=zx-spectrum --build=pdp11

Bug#812768: python-whoosh: diff for NMU version 2.7.0-1.1

[Simon McVittie]

Control: tags 812768 + patch
Control: tags 812768 + pending

Dear maintainer,

I've prepared an NMU for python-whoosh (versioned as 2.7.0-1.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

I've also pushed the changes to collab-maint git: please revert any
that you don't think are valid before the next maintainer upload.

Regards,
smcv
diffstat for python-whoosh-2.7.0 python-whoosh-2.7.0

 changelog   |   27 +
 control |8 -
 missing/english-words.10.gz |binary
 patches/series  |1 
 patches/test_vector_unicode-Cope-with-updated-Python-unicode-data.patch |   46 ++
 rules   |4 
 source/include-binaries |1 
 7 files changed, 83 insertions(+), 4 deletions(-)

diff -Nru python-whoosh-2.7.0/debian/changelog python-whoosh-2.7.0/debian/changelog
--- python-whoosh-2.7.0/debian/changelog	2015-05-07 12:26:13.0 +0100
+++ python-whoosh-2.7.0/debian/changelog	2017-01-22 18:57:02.0 +
@@ -1,3 +1,30 @@
+python-whoosh (2.7.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload, incorporating changes from collab-maint git.
+
+  [ Tobias Frost ]
+  * Team upload (collab-maint)
+  * d/control:
+- Replace VCS-* with https:// ones.
+- d/control: Bump S-V to 3.9.8 -- no changes required
+
+  [ Simon McVittie ]
+  * Add sphinxdoc-common to Build-Depends. The sphinxdoc debhelper
+addon is required for the 'clean' target, so installing it in
+Build-Depends-Indep is not enough.
+  * debian/missing/english-words.10.gz: Add missing file from upstream
+2.7.0 tag. The unit tests require this file. (Closes: #812768)
+- debian/source/include-binaries: Include it in the tarball.
+- debian/rules: Copy the missing file into tests/ before building.
+  Delete it during clean.
+  * d/p/test_vector_unicode-Cope-with-updated-Python-unicode-data.patch:
+Add patch to make a test pass under Python 3.5. It makes outdated
+assumptions about how Python maps Cherokee text to lower-case.
+  * debian/rules: Disable HTTP network access to avoid Sphinx contacting
+docs.python.org (Policy §4.9)
+
+ -- Simon McVittie   Sun, 22 Jan 2017 18:57:02 +
+
 python-whoosh (2.7.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru python-whoosh-2.7.0/debian/control python-whoosh-2.7.0/debian/control
--- python-whoosh-2.7.0/debian/control	2015-05-07 12:26:13.0 +0100
+++ python-whoosh-2.7.0/debian/control	2017-01-22 18:57:02.0 +
@@ -2,14 +2,14 @@
 Section: python
 Priority: optional
 Maintainer: أحمد المحمودي (Ahmed El-Mahmoudy) 
-Build-Depends: debhelper (>= 9), dh-python, python-setuptools, python3-setuptools
+Build-Depends: debhelper (>= 9), dh-python, python-setuptools, python3-setuptools, sphinx-common
 Build-Depends-Indep: python3-sphinx (>= 1.0.7+dfsg), python-all (>= 2.6.6-2), python3-all, python-pytest, python3-pytest
-Standards-Version: 3.9.6
+Standards-Version: 3.9.8
 Homepage: http://bitbucket.org/mchaput/whoosh/
 X-Python-Version: >= 2.5
 X-Python3-Version: >= 3.2
-Vcs-Git: git://anonscm.debian.org/collab-maint/python-whoosh.git
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/python-whoosh.git
+Vcs-Git: https://anonscm.debian.org/git/collab-maint/python-whoosh.git
+Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/python-whoosh.git
 
 Package: python-whoosh
 Architecture: all
Binary files /tmp/HdzQCBlDBX/python-whoosh-2.7.0/debian/missing/english-words.10.gz and /tmp/HrvBWJW43E/python-whoosh-2.7.0/debian/missing/english-words.10.gz differ
diff -Nru python-whoosh-2.7.0/debian/patches/series python-whoosh-2.7.0/debian/patches/series
--- python-whoosh-2.7.0/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ python-whoosh-2.7.0/debian/patches/series	2017-01-22 18:57:02.0 +
@@ -0,0 +1 @@
+test_vector_unicode-Cope-with-updated-Python-unicode-data.patch
diff -Nru python-whoosh-2.7.0/debian/patches/test_vector_unicode-Cope-with-updated-Python-unicode-data.patch python-whoosh-2.7.0/debian/patches/test_vector_unicode-Cope-with-updated-Python-unicode-data.patch
--- python-whoosh-2.7.0/debian/patches/test_vector_unicode-Cope-with-updated-Python-unicode-data.patch	1970-01-01 01:00:00.0 +0100
+++ python-whoosh-2.7.0/debian/patches/test_vector_unicode-Cope-with-updated-Python-unicode-data.patch	2017-01-22 18:57:02.0 +
@@ -0,0 +1,46 @@
+From: Simon McVittie 
+Date: Sun, 22 Jan 2017 17:48:21 +
+Subject: test_vector_unicode: Cope with updated Python unicode data
+
+This particular text uses Cherokee letters: for example, the first 

Processed: python-whoosh: diff for NMU version 2.7.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 812768 + patch
Bug #812768 [python-whoosh] python-whoosh: FTBFS - tests fail with "No such 
file or directory: ... english-words.10.gz"
Added tag(s) patch.
> tags 812768 + pending
Bug #812768 [python-whoosh] python-whoosh: FTBFS - tests fail with "No such 
file or directory: ... english-words.10.gz"
Added tag(s) pending.

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

Bug#838483: gprbuild starts failing with "no native compiler found for language 'ada'"

[Nicolas Boulenguez]

Source: gprbuild
Followup-For: Bug #838483
Control: affects 839209 gprbuild

Upload of 2015-6 may fix some symptoms, but not those caused by #839209.

Bug#851014: marked as done (python-xmp-toolkit: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 18:04:45 +
with message-id 
and subject line Bug#851014: fixed in python-xmp-toolkit 
2.0.1+git20140309.5437b0a-4
has caused the Debian Bug report #851014,
regarding python-xmp-toolkit: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 2.7 returned exit code 13
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.)


-- 
851014: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851014
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xmp-toolkit
Version: 2.0.1+git20140309.5437b0a-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170111 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build  --with python2,python3,sphinxdoc --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/utils.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/files.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/exempi.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/core.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/__init__.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/consts.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> copying libxmp/version.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_2.7/build/libxmp
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/utils.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/files.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/exempi.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/core.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/__init__.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/consts.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
> copying libxmp/version.py -> 
> /<>/python-xmp-toolkit-2.0.1+git20140309.5437b0a/.pybuild/pythonX.Y_3.5/build/libxmp
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py test 
> running test
> running egg_info
> creating python_xmp_toolkit.egg-info
> writing requirements to python_xmp_toolkit.egg-info/requires.txt
> writing python_xmp_toolkit.egg-info/PKG-INFO
> writing top-level names to python_xmp_toolkit.egg-info/top_level.txt
> writing dependency_links to python_xmp_toolkit.egg-info/dependency_links.txt
> writing manifest file 'python_xmp_toolkit.egg-info/SOURCES.txt'
> reading manifest file 'python_xmp_toolkit.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'python_xmp_toolkit.egg-info/SOURCES.txt'
> running build_ext
> test_jpeg (test.test_roundtrip.TestRoundTrip)
> Create XMP from scratch to store in a jpeg. ... ok
> test_sturm_und_drang (test.test_roundtrip.TestRoundTrip)
> Should be able to write a property which includes umlauts. ... ok
> test_tiff (test.test_roundtrip.TestRoundTrip)
> Write to a TIFF that does not already have the XMP tag. ... ok
> test_3 (test.test_exempi.TestExempi)
> Corresponds to test3.cpp ... ok
> test_bad_formats (test.test_exempi.TestExempi)
> Verify check_file_format on PDF, Adobe Illustrator, XMP. ... skipped 'Issue 
> 26'
> test_bgo (test.test_exempi.TestExempi)
> Corresponds to test-bgo.cpp ... 

Bug#852214: marked as done (musl 1.1.16 fails to build on armhf)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 17:49:58 +
with message-id 
and subject line Bug#852214: fixed in musl 1.1.16-2
has caused the Debian Bug report #852214,
regarding musl 1.1.16 fails to build 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.)


-- 
852214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: musl
Version: 1.1.16-1
Severity: serious
Forwarded: http://www.openwall.com/lists/musl/2017/01/04/6

Since 1.1.16-1 musl doesn't build on armhf [0]:

> cc -std=c99 -nostdinc -ffreestanding -fexcess-precision=standard 
> -frounding-math -Wa,--noexecstack -D_XOPEN_SOURCE=700 -I./arch/arm 
> -I./arch/generic -Iobj/src/internal -I./src/internal -Iobj/include 
> -I./include -Wdate-time -D_FORTIFY_SOURCE=2 -g -pipe -fno-unwind-tables 
> -fno-asynchronous-unwind-tables -ffunction-sections -fdata-sections 
> -Werror=implicit-function-declaration -Werror=implicit-int 
> -Werror=pointer-sign -Werror=pointer-arith -include vis.h 
> -Wa,-mimplicit-it=always -Wa,-mthumb -g -O2 
> -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -c -o obj/src/thread/arm/atomics.lo 
> src/thread/arm/atomics.s
> src/thread/arm/atomics.s: Assembler messages:
> src/thread/arm/atomics.s:59: Error: invalid constant (1) after fixup
> src/thread/arm/atomics.s:74: Error: invalid constant (1) after fixup

The issue is also caused by a change in binutils 2.27.51.20161105-1,
which has more strict checking of assembly files [1] [2].

I noticed that 1.1.16-1 builds fine on rebootstrap [3]. The difference
seems to be that thumb2 support is not detected and disabled.
(I could also confirm that building without -Wa,-mthumb succeeds.)

[0]: 
https://buildd.debian.org/status/fetch.php?pkg=musl=armhf=1.1.16-1=1483481970=0
[1]: https://sourceware.org/ml/binutils/2017-01/msg00081.html
[2]: 
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=bada43421274615d0d5f629a61a60b7daa71bc15
[3]: 
https://jenkins.debian.net/view/rebootstrap/job/rebootstrap_musl-linux-arm64_gcc6/20/


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: musl
Source-Version: 1.1.16-2

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated musl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Jan 2017 18:18:26 +0100
Source: musl
Binary: musl musl-dev musl-tools
Architecture: source
Version: 1.1.16-2
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Description:
 musl   - standard C library
 musl-dev   - standard C library development files
 musl-tools - standard C library tools
Closes: 851686 852214
Changes:
 musl (1.1.16-2) unstable; urgency=medium
 .
   [ Breno Leitao ]
   * Enable building on ppc64el. (Closes: #851686)
 .
   [ Reiner Herrmann ]
   * Fix build failure on armhf with newer binutils. (Closes: #852214)
Checksums-Sha1:
 c9665c4e47a106c17351e5de0f000d7fcc657027 2975 musl_1.1.16-2.dsc
 d5335c21720a53e5b3cf7e955517cdebc7696e5b 10956 musl_1.1.16-2.debian.tar.xz
Checksums-Sha256:
 1669de742f7f976ffc90de773c738f7fd5a1d847a3e72f5c053aa421f22818f4 2975 
musl_1.1.16-2.dsc
 5aaa4b8d6e7e11135014a6c75332a5f50ddb71c08abea8d836bae2649225c64b 10956 
musl_1.1.16-2.debian.tar.xz
Files:
 83dd7bc8b824a0f0a072dcb8faf471ac 2975 libs extra musl_1.1.16-2.dsc
 ac9866b2c0f7125625459d1081e430a1 10956 libs extra musl_1.1.16-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2Pb6feok2Q1urHM7zPBJKNsO6qcFAliE6nwACgkQzPBJKNsO
6qcDwBAAteYEHOO8AILMPVps4zTTYuOoiqOg3rM5D0Je5vot5tLwiyhc3C1TZ/VY
Tl85IHkKfxlykhTMgtUyXExcvh+N+jj9KMMpze0/PBqZQ8kn282ISZ1XuAoGziKe
thmP+DRG78gooPeJ6wIiWvmRjFlOlWhoVxzoXH8idiojg963T7Hv/btJMTn3LoP/
rrw2+/GL3NBXDWtiNlUV0WvVsA3AoXnYIoDnP9BioBtdr9PcMJO3lt709osgXuVm

Bug#852202: systemd 232-13 aborts during upgrade and subsequent boots

[Michael Biebl]

Control: found -1 232-8

Hi David

Am 22.01.2017 um 18:20 schrieb David Taylor:
> On Sun, 22 Jan 2017, Michael Biebl wrote:
> 
>> Control: tags -1 + moreinfo
>>
>> Am 22.01.2017 um 14:14 schrieb David Taylor:
>>> Currently running systemd_231-9, first experienced this problem when
>>> trying to upgrade to 232-8, 232-13 is still giving the same problem.
>>
>> Upgrading from -9 to -8? I guess you mistyped this.
>> What is the first version you encountered the problem? Which version was
>> still working fine? Were other changes made to the system?
> 
> No typo - the first failed upgrade was from 231-9 to 232-8.  Nothing
> else changed at that time (except other package upgrades, but they seem
> irrelevant, given that downgrading to 231-9 leaves a working system and
> upgrading to either 232-8 or 232-13 leaves it failing to boot.)

Ok, marking this accordingly as found in 232-8. Otherwise 232-13 won't
migrate to testing.

> I built the systemd_232-13 package locally from source, so I'm not sure
> how useful the core file would be to you.  I have reproduced the
> backtrace below.

If you built 232-13 from source, can you cherry-pick the upstream patch
and see if that fixes your issue? We might then cherry-pick that patch
in the official package as well.
I can prepare packages if you prefer that.


>> The above bug report suggests a problem with unicode partition labels.
>> Do you have such a partition?
> 
> I didn't think so, but double-checking in /dev/disk/by-partlabel shows I do
> have an NTFS partition with the label †††:
> 
> # ls -l /dev/disk/by-partlabel/
> total 0
> lrwxrwxrwx 1 root root 10 Jan 22 13:19
> ††† -> ../../sdb3

Ah, ok. So this is a dual boot system, I assume.

Is /dev/sdb3 the partition holding the actual Windows 10 system? [1]
suggests that the partition layout is
System | MSR | Windows | Recovery

If you boot Windows, what's the partion label shown there? Is it the
default label created by the Windows installer?

The reason I'm asking is that I want to get a better idea which / how
many users are affected.



Regards,
Michael


[1]
https://msdn.microsoft.com/en-us/windows/hardware/commercialize/manufacture/desktop/configure-uefigpt-based-hard-drive-partitions
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#851724: python-llfuse: FTBFS (failing tests)

[Nikolaus Rath]

On Jan 22 2017, Santiago Vila  wrote:
> On Sat, Jan 21, 2017 at 04:12:28PM -0800, Nikolaus Rath wrote:
>
>> Are you able to reproduce this with Python 3.5?
>
> I don't know. I'm just building the package from source.
>
> The package currently build-depends on both python-all-dev and 
> python3-all-dev.
>
> By "trying with Python 3.5" you mean removing the build-dependency on
> python-all-dev?

Sorry, this was a little terse. The build process runs with unit tests
with all available Python versions, starting with 2.x. However, it
aborts on the first failed test. I was wondering if in any of your
builds it ever made it through the 2.7 tests and then failed when
testing with 3.x.

You could force this behavior by removing the "-x" from test/pytest.ini
(in this case it attempts to run all tests). Removing the build-depends
may work as well, I'm not 100% sure.


Best,
Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

 »Time flies like an arrow, fruit flies like a Banana.«

Processed: Re: Bug#852202: systemd 232-13 aborts during upgrade and subsequent boots

[Debian Bug Tracking System]

Processing control commands:

> found -1 232-8
Bug #852202 [systemd] systemd 232-13 aborts during upgrade and subsequent boots
Marked as found in versions systemd/232-8.

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

Bug#852202: systemd 232-13 aborts during upgrade and subsequent boots

[David Taylor]

On Sun, 22 Jan 2017, Michael Biebl wrote:


Control: tags -1 + moreinfo

Am 22.01.2017 um 14:14 schrieb David Taylor:

Currently running systemd_231-9, first experienced this problem when
trying to upgrade to 232-8, 232-13 is still giving the same problem.


Upgrading from -9 to -8? I guess you mistyped this.
What is the first version you encountered the problem? Which version was
still working fine? Were other changes made to the system?


No typo - the first failed upgrade was from 231-9 to 232-8.  Nothing 
else changed at that time (except other package upgrades, but they seem 
irrelevant, given that downgrading to 231-9 leaves a working system and 
upgrading to either 232-8 or 232-13 leaves it failing to boot.)



During upgrade or boot systemd aborts due to an assertion failure:

Broadcast message from systemd-journald@ (Sun 2017-01-22 12:59:45 GMT):
systemd[1]: Caught , dumped core as pid 1535.
Message from syslogd@ Jan 22 12:59:45 ...
 systemd[1]: Caught , dumped core as pid 1535.

Broadcast message from systemd-journald@ (Sun 2017-01-22 12:59:45 GMT):
systemd[1]: Freezing execution.
Message from syslogd@deb550s at Jan 22 12:59:45 ...
 systemd[1]: Freezing execution.

syslog shows:

systemd[1]: Assertion 'u' failed at ../src/core/unit.c:521, function 
unit_free(). Aborting.

A similar problem appears to have been fixed upstream:
https://github.com/systemd/systemd/issues/4747


Can you attach the core file (should be found at /core) from the crash
with the exact systemd version you were using.


I built the systemd_232-13 package locally from source, so I'm not sure how 
useful the core file would be to you.  I have reproduced the backtrace below.

If you need any more details (or feel the core would still be useful) let me
know.

Reading symbols from /bin/systemd...Reading symbols from 
/usr/lib/debug/.build-id/24/30880e7d50808599be7bb2bafe54dab1a14bb8.debug...done.
done.
[New LWP 5370]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/lib/systemd/systemd --system --deserialize 19'.
Program terminated with signal SIGABRT, Aborted.

(gdb) bt
#0  0x7f7f747302f7 in kill () at ../sysdeps/unix/syscall-template.S:84
#1  0x560a0a3188aa in crash (sig=6) at ../src/core/main.c:189
#2  
#3  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
#4  0x7f7f7473140a in __GI_abort () at abort.c:89
#5  0x7f7f75ebd4c2 in log_assert_failed (text=, file=, line=,
   func=) at ../src/basic/log.c:795
#6  0x560a0a3838c1 in unit_free (u=) at 
../src/core/unit.c:521
#7  0x560a0a32c4a0 in device_setup_unit.lto_priv.274 
(m=m@entry=0x560a0ab5e800, dev=dev@entry=0x560a0ac26690,
   path=path@entry=0x560a0ac2cef0 "/dev/disk/by-partlabel/", '†' , main=main@entry=false)
   at ../src/core/device.c:369
#8  0x560a0a32cc20 in device_process_new.lto_priv.276 (m=0x560a0ab5e800, 
dev=0x560a0ac26690) at ../src/core/device.c:420
#9  0x560a0a36bf15 in device_enumerate.lto_priv.149 (m=0x560a0ab5e800) at 
../src/core/device.c:689
#10 0x560a0a360a1f in manager_enumerate (m=) at 
../src/core/manager.c:1141
#11 0x560a0a312389 in manager_startup (fds=0x560a0ab5f2d0, 
serialization=, m=0x560a0ab5e800)
   at ../src/core/manager.c:1269
#12 main (argc=4, argv=) at ../src/core/main.c:1774



The above bug report suggests a problem with unicode partition labels.
Do you have such a partition?


I didn't think so, but double-checking in /dev/disk/by-partlabel shows I do
have an NTFS partition with the label †††:

# ls -l /dev/disk/by-partlabel/
total 0
lrwxrwxrwx 1 root root 10 Jan 22 13:19 ††† -> 
../../sdb3
lrwxrwxrwx 1 root root 10 Jan 22 13:19 EFI\x20system\x20partition -> ../../sdb1
lrwxrwxrwx 1 root root 10 Jan 22 13:19 Microsoft\x20reserved\x20partition -> 
../../sdb2

I'm not sure where that PARTLABEL came from (I definitely didn't choose 
it), but the filesystem is part of a Windows 10 install.



Can you reproduce the problem reliably? Do you know how we can reproduce
the problem?


Yes, the problem occurs every time I upgrade the package (or reboot with 
the upgraded package installed).  I assume you could reboot it by 
creating an NTFS filesystem with PARTLABEL="†††"


--
David Taylor

Bug#840823: marked as done (execnet: testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen] FAILED)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 17:18:33 +
with message-id 
and subject line Bug#840823: fixed in execnet 1.4.1-3
has caused the Debian Bug report #840823,
regarding execnet: 
testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen]
 FAILED
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.)


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

Dear maintainer:

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


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

[... snipped ...]

testing/test_gateway.py::TestBasicGateway::test_gateway_status_no_real_channel[thread-ssh]
 SKIPPED
testing/test_gateway.py::TestBasicGateway::test_gateway_status_no_real_channel[thread-proxy]
 PASSED
testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen]
 FAILED
=== short test summary info 
SKIP [3] /<>/testing/conftest.py:148: no python3.2 found
SKIP [3] /<>/testing/conftest.py:148: no jython found
SKIP [3] /<>/testing/conftest.py:148: no python2.6 found
SKIP [3] /<>/testing/conftest.py:148: no pypy found
SKIP [3] /<>/testing/conftest.py:148: no python3.3 found
SKIP [36] /usr/lib/python2.7/dist-packages/_pytest/config.py:1142: no 'gspecs' 
option found

=== FAILURES ===
___ TestBasicGateway.test_gateway_status_busy[thread-popen] 

self = 
gw = 

def test_gateway_status_busy(self, gw):
numchannels = gw.remote_status().numchannels
ch1 = gw.remote_exec("channel.send(1); channel.receive()")
ch2 = gw.remote_exec("channel.receive()")
ch1.receive()
status = gw.remote_status()
assert status.numexecuting == 2  # number of active execution threads
assert status.numchannels == numchannels + 2
ch1.send(None)
ch2.send(None)
ch1.waitclose()
ch2.waitclose()
for i in range(10):
status = gw.remote_status()
if status.numexecuting == 0:
break
else:
>   pytest.fail("did not get correct remote status")
E   Failed: did not get correct remote status

testing/test_gateway.py:88: Failed
 pytest-warning summary 
WI1 /<>/testing/conftest.py:21 'pytest_runtest_setup' hook uses 
deprecated __multicall__ argument
WC1 None pytest_funcarg__specsocket: declaring fixtures using 
"pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 
4.0.  Please remove the prefix and use the @pytest.fixture decorator instead.
WC1 None pytest_funcarg__specssh: declaring fixtures using "pytest_funcarg__" 
prefix is deprecated and scheduled to be removed in pytest 4.0.  Please remove 
the prefix and use the @pytest.fixture decorator instead.
 Interrupted: stopping after 1 failures 
= 1 failed, 135 passed, 51 skipped, 3 pytest-warnings in 8.69 seconds ==
E: pybuild pybuild:276: test: plugin custom failed with: exit code=2: python2.7 
-m pytest -v -x -rs testing/
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
debian/rules:8: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
debian/rules:5: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

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

Bug#852227: libp11-kit0: Temporarily block migration of 0.23.3-4 to testing

[Andreas Metzler]

Package: libp11-kit0
Version: 0.23.3-4
Severity: serious

p11-kit 0.23.3-4 breaks the GnuTLS testsuite. Let's keep it out of
testing until we know which package needs to be fixed.

https://lists.freedesktop.org/archives/p11-glue/2017-January/000637.html

cu Andreas

Bug#847282: imagemagick-doc: fails to upgrade wheezy -> jessie -> stretch

[Bastien ROUCARIES]

control: severity -1 important

Let decrease the severity to something not RC. I need to know if the
problem is in dpkg or imagemagick. And I do not want to block the
security update of imagemagick.

On Sat, Jan 21, 2017 at 11:04 PM, Andreas Beckmann  wrote:
> Followup-For: Bug #847282
> Control: found -1 8:6.9.7.0+dfsg-2
>
> Hi,
>
> there are still a few traces left from this bug:
>
>   Preparing to unpack .../imagemagick-doc_8%3a6.9.7.0+dfsg-2_all.deb ...
>   dpkg-maintscript-helper: error: directory '/usr/share/doc/imagemagick-doc' 
> contains files not owned by package imagemagick-doc:all, cannot switch to 
> symlink
>   dpkg: error processing archive 
> /var/cache/apt/archives/imagemagick-doc_8%3a6.9.7.0+dfsg-2_all.deb (--unpack):
>subprocess new pre-installation script returned error exit status 1
>
> some info from the chroot:
>
> # ls -la /usr/share/doc/imagemagick-doc
> total 176
> drwxr-xr-x   4 root root   220 Jan 21 21:57 .
> drwxr-xr-x 117 root root  2500 Jan 21 21:59 ..
> -rw-r--r--   1 root root   991 Nov 25 20:45 NEWS.Debian.gz
> -rw-r--r--   1 root root 32429 Nov 25 20:45 changelog.Debian.gz
> -rw-r--r--   1 root root 77347 Oct 25  2014 changelog.gz
> -rw-r--r--   1 root root 42835 Nov 25 20:45 copyright
> drwxr-xr-x   3 root root  1040 Jan 21 21:57 images
> lrwxrwxrwx   1 root root21 Apr  7  2016 images.dpkg-backup -> 
> ../imagemagick/images
> -rw-r--r--   1 root root 18947 Nov 26 18:00 index.html
> drwxr-xr-x   5 root root  1340 Jan 21 21:57 www
> lrwxrwxrwx   1 root root18 Apr  7  2016 www.dpkg-backup -> 
> ../imagemagick/www
>
> # dpkg -S /usr/share/doc/imagemagick-doc/*
> imagemagick-doc: /usr/share/doc/imagemagick-doc/NEWS.Debian.gz
> imagemagick-doc: /usr/share/doc/imagemagick-doc/changelog.Debian.gz
> imagemagick-doc: /usr/share/doc/imagemagick-doc/changelog.gz
> imagemagick-doc: /usr/share/doc/imagemagick-doc/copyright
> imagemagick-doc: /usr/share/doc/imagemagick-doc/images
> dpkg-query: no path found matching pattern 
> /usr/share/doc/imagemagick-doc/images.dpkg-backup
> imagemagick-doc: /usr/share/doc/imagemagick-doc/index.html
> imagemagick-doc: /usr/share/doc/imagemagick-doc/www
> dpkg-query: no path found matching pattern 
> /usr/share/doc/imagemagick-doc/www.dpkg-backup
>
>
> Andreas

Processed: Re: Bug#847282: imagemagick-doc: fails to upgrade wheezy -> jessie -> stretch

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #847282 [imagemagick-doc] imagemagick-doc: fails to upgrade wheezy -> 
jessie -> stretch
Severity set to 'important' from 'serious'

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

Bug#852092: hwloc-contrib: FTBFS since nvidia-cuda-toolkit switched from gcc-5 to clang-3.8

[Samuel Thibault]

Hello,

Andreas Beckmann, on Sat 21 Jan 2017 17:18:39 +0100, wrote:
> Justification: fails to build from source

Err, does it really?  I've just tried with an updated pbuilder, with
nvidia-cuda-dev 8.0.44-3, and that indeed didn't pull gcc-5.

> please check whether you can get hwloc-contrib (partially) built with
> clang-3.8, e.g. using
> 
>   nvcc -ccbin clang-3.8

hwloc-contrib doesn't actually use nvcc, it just uses some headers and
links against libcudart

Samuel

Processed: Re: Bug#848285 closed by Julien Cristau <jcris...@debian.org> (Re: Bug#852042: nmu: jackd2_1.9.10+20150825git1ed50c92~dfsg-4)

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 jackd2/1.9.10+20150825git1ed50c92~dfsg-4+b1
Bug #848285 {Done: Julien Cristau } [jackd2] jackd2: spits 
verbose output and exits immediately when the client stops sending audio
The source jackd2 and version 1.9.10+20150825git1ed50c92~dfsg-4+b1 do not 
appear to match any binary packages
Marked as fixed in versions jackd2/1.9.10+20150825git1ed50c92~dfsg-4+b1.

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

Bug#848285: closed by Julien Cristau <jcris...@debian.org> (Re: Bug#852042: nmu: jackd2_1.9.10+20150825git1ed50c92~dfsg-4)

[Francesco Poli]

Control: fixed -1 jackd2/1.9.10+20150825git1ed50c92~dfsg-4+b1


On Sun, 22 Jan 2017 16:27:03 + Debian Bug Tracking System wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the jackd2 package:
> 
> #848285: jackd2: spits verbose output and exits immediately when the client 
> stops sending audio
> 
> It has been closed by Julien Cristau .

Many thanks to all people involved in fixing the bug in GCC and in
fixing the resulting issue in Jackd!

I am looking forward to seeing the binNMU migrate to Debian testing.

In the meanwhile, apt-listbugs users risk seeing the package unpinned
and upgraded to the buggy version currently in testing, just because
this bug report has been closed with -done without version info.
I know that 1.9.10+20150825git1ed50c92~dfsg-4+b1 is not a source
version, but I guess that adding it as a fixed version should not harm
the BTS version tracking and would probably make apt-listbugs understand
that the bug was *not* closed as invalid, just fixed in a binNMU...
I am adding such a fixed version, I hope nobody will get angry because
of this.



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpSLU9QyrFHS.pgp
Description: PGP signature

Bug#852076: marked as done (mpgrafic: mips build of mpgrafic gives zero record size)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 17:31:04 +0100 (CET)
with message-id 
and subject line Done: Re: Bug#852076: mpgrafic: mips build of mpgrafic gives 
zero record size
has caused the Debian Bug report #852076,
regarding mpgrafic: mips build of mpgrafic gives zero record size
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.)


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

Package: mpgrafic
Version: 0.3.7.8-1
Severity: serious
Tags: upstream
Justification: fails to build from source

Dear Maintainer,

Description:

After installing mpgrafics-0.3.7.8-1 on mips by the debian buildd system,
`make check' runs `regression-test-0.3.7.8.sh', which runs
`mpirun -n 1 --mca plm_rsh_agent sh ${srcdir}/src/mpgrafic --np=32 < 
${srcdir}/Input.stdin
and gives the output:

 Record size0  is different from expected4096

and then fatally exits (as it should in such a case).

Log:

https://buildd.debian.org/status/fetch.php?pkg=mpgrafic=mips=0.3.7.8-1=1484927169=0
(line 1010 of the raw html file)

Analysis:

The error is presumably triggered at line 308 (v0.3.7.8-1) of
src/grafic_io.f90 - taille_tampon is read by f77_parallel_read() in
src/parallel_io.c .  The function f77_parallel_read() is a front end to
parallel_read(), in the same .c file, which calls pread()  to read
bytes from a disk file into a buffer.

The disk file is (previously to this) written by a similar hierarchy
of f90 and C functions to `white-outfile.dat' (assuming that
`Input.stdin' is the source package input file above).

Hypothesis:

This looks like an endianness/word size problem - bytes are written to
disk and read from disk as a raw sequence of bytes without any
casting, neither in writing nor in reading.

Proposed solution method:

On a real or emulated mips machine, a quick hack would be to play
around with casting and byte-swapping to find a way that the test
script is successful.

An acceptable solution would be to make changes that are not
machine dependent. The AC_C_BIGENDIAN should probably be added to configure.ac
and then the preprocessor macro WORDS_BIGENDIAN could be used.
See the autoconf documentation for details.

Appropriate use of casting and USE_ISO_C in src/grafic_io.f90 would
probably give a more elegant and robust solution in terms of
portability.

-- System Information:
Debian Release: sid
Architecture: mips
--- End Message ---
--- Begin Message ---

Version: 0.3.8-1

Upstream changes seem to have fixed this. Use of iso_C_binding in 
src/grafic_io.f90

https://gcc.gnu.org/onlinedocs/gfortran/ISO_005fC_005fBINDING.html

and of less implementation-dependent C typing of integers in
src/parallel_io.c (e.g. int32_t instead of long)

https://en.wikipedia.org/wiki/C_data_types#Fixed-width_integer_types

was sufficient for the Debian buildd on mips to successfully run
regresssion-test-0.3.7.9.sh . Look at earlier versions of Output.stdout.np32
to see that the expected output has changed only in the least significant
decimal places.

This bug seems *not* to have been an endianness issue.

The following change generates an error consistent with the bug:

- in src/grafic_io.f90, replace the four lines

integer(c_int32_t), target :: taille_tampon

by

integer(c_int8_t), target :: taille_tampon--- End Message ---

Bug#852216: kodi: FTBFS on mips64el

[Adrian Bunk]

Control: retitle -1 kodi FTBFS with libcec 4
Control: found -1 2:17.0~rc2+dfsg1-1

On Sun, Jan 22, 2017 at 05:03:33PM +0100, Julien Cristau wrote:
> Source: kodi
> Version: 2:17.0~rc3+dfsg1-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> kodi FTBFS on the mips64el buildd:
> 
> > PeripheralCecAdapter.cpp: In member function 'virtual void 
> > PERIPHERALS::CPeripheralCecAdapter::Announce(ANNOUNCEMENT::AnnouncementFlag,
> >  const char*, const char*, const CVariant&)':
> > PeripheralCecAdapter.cpp:169:25: error: 'CEC::libcec_configuration {aka 
> > struct CEC::libcec_configuration}' has no member named 'bPowerOnScreensaver'
> >  if (m_configuration.bPowerOnScreensaver == 1 && !bIgnoreDeactivate &&
> >  ^~~
>...

This is actually not mips64el specific, just timing of the kodi build.
kodi FTBFS with libcec 4.

This is the libcec transition (#849189).

> Cheers,
> Julien

cu
Adrian

-- 

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

Processed: Re: Bug#852216: kodi: FTBFS on mips64el

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 kodi FTBFS with libcec 4
Bug #852216 [src:kodi] kodi: FTBFS on mips64el
Changed Bug title to 'kodi FTBFS with libcec 4' from 'kodi: FTBFS on mips64el'.
> found -1 2:17.0~rc2+dfsg1-1
Bug #852216 [src:kodi] kodi FTBFS with libcec 4
Marked as found in versions kodi/2:17.0~rc2+dfsg1-1.

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

Bug#852202: systemd 232-13 aborts during upgrade and subsequent boots

[Michael Biebl]

Control: tags -1 + moreinfo

Am 22.01.2017 um 14:14 schrieb David Taylor:
> Currently running systemd_231-9, first experienced this problem when
> trying to upgrade to 232-8, 232-13 is still giving the same problem.

Upgrading from -9 to -8? I guess you mistyped this.
What is the first version you encountered the problem? Which version was
still working fine? Were other changes made to the system?

> During upgrade or boot systemd aborts due to an assertion failure:
> 
> Broadcast message from systemd-journald@ (Sun 2017-01-22 12:59:45 GMT):
> systemd[1]: Caught , dumped core as pid 1535.
> Message from syslogd@ Jan 22 12:59:45 ...
>  systemd[1]: Caught , dumped core as pid 1535.
> 
> Broadcast message from systemd-journald@ (Sun 2017-01-22 12:59:45 GMT):
> systemd[1]: Freezing execution.
> Message from syslogd@deb550s at Jan 22 12:59:45 ...
>  systemd[1]: Freezing execution.
> 
> syslog shows:
> 
> systemd[1]: Assertion 'u' failed at ../src/core/unit.c:521, function 
> unit_free(). Aborting.  
> 
> A similar problem appears to have been fixed upstream:
> https://github.com/systemd/systemd/issues/4747

Can you attach the core file (should be found at /core) from the crash
with the exact systemd version you were using.

The above bug report suggests a problem with unicode partition labels.
Do you have such a partition?

Can you reproduce the problem reliably? Do you know how we can reproduce
the problem?




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



signature.asc
Description: OpenPGP digital signature

Bug#852130: redmine: fails to install, remove, and install again

[Antonio Terceiro]

On Sat, Jan 21, 2017 at 08:46:22PM +0100, Andreas Beckmann wrote:
> Package: redmine
> Version: 3.3.1-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install,
> remove (but not purge), and install again.
> Before the second installation the package is in config-files-remaining
> state. The configuration is remaining from the last version that was
> successfully configured - which is the same version that is going to be
> installed again.

Hi,

First of all thanks for your work on piuparts.

However, I am not able to reproduce this without piuparts. I tried
install/remove/install by hand on a clean chroot twice, and even
automating it with a script like this:

export DEBIAN_FRONTEND=noninteractive
apt-get install -qy redmine
apt-get remove -qy redmine
apt-get install -qy redmine

The process piuparts uses for these tests seems a little convoluted. I
imagine piuparts does things this way for Very Good Reasons™ (trying to
minimize false positives, and failures in one package being blamed on
another, etc), but I am not sure how well it represents actual usage.

Would you have any tips for reproducing this failure outside of piuparts?


signature.asc
Description: PGP signature

Processed: Re: Bug#852202: systemd 232-13 aborts during upgrade and subsequent boots

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #852202 [systemd] systemd 232-13 aborts during upgrade and subsequent boots
Added tag(s) moreinfo.

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

Bug#848285: marked as done (jackd2: spits verbose output and exits immediately when the client stops sending audio)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 17:23:56 +0100
with message-id <20170122162356.v4rhoasuc7idk...@betterave.cristau.org>
and subject line Re: Bug#852042: nmu: jackd2_1.9.10+20150825git1ed50c92~dfsg-4
has caused the Debian Bug report #848285,
regarding jackd2: spits verbose output and exits immediately when the client 
stops sending audio
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.)


-- 
848285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jackd2
Version: 1.9.10+20150825git1ed50c92~dfsg-4
Severity: grave
Justification: renders package unusable

Hello and thanks for maintaining jackd2!

After the upgrade

  [UPGRADE] jackd2:amd64 1.9.10+20150825git1ed50c92~dfsg-3 -> 
1.9.10+20150825git1ed50c92~dfsg-4
  [UPGRADE] jackd2-firewire:amd64 1.9.10+20150825git1ed50c92~dfsg-3 -> 
1.9.10+20150825git1ed50c92~dfsg-4
  [UPGRADE] libjack-jackd2-0:amd64 1.9.10+20150825git1ed50c92~dfsg-3 -> 
1.9.10+20150825git1ed50c92~dfsg-4

I experienced a grave bug: as soon as the client (audacious, firefox through
ALSA redirection in ~/.asoundrc, ...) stops sending audio to the jackd
sound server, the latter spits a bunch of output messages and exits
immediately (as if the --temporary option were passed, no!, even worse!).

Steps to reproduce:

  0) run jackd with the following command line:

 $ jackd --realtime -d alsa --device hw:1 --softmode --hwmeter --rate 44100 
&

  1) run, e.g., audacious (configured to use the Jack output plugin)

  2) play some audio: everything seems to work, even though jackd seems
 to have become more verbose than ever, with a long sequence of
 output lines similar to:

 [...]
 Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
 Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
 Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
 Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
 Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
 Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
 [...]

  3) click on the stop button in the audacious interface: jackd spits the
 following output and exits immediately:

 Jack: JackSocketServerChannel::Execute : fPollTable i = 1 fd = 9
 Jack: JackSocketServerChannel::Execute : fPollTable i = 2 fd = 10
 Jack: JackRequest::DeactivateClient
 Jack: JackEngine::ClientDeactivate ref = 2 name = audacious
 Jack: JackEngine::PortDisconnect ref = -1 src = 9 dst = 65535
 Jack: JackEngine::PortDisconnect ref = -1 src = 9 dst = 3
 Jack: JackGraphManager::Disconnect port_src = 9 port_dst = 3
 Jack: JackConnectionManager::Disconnect port_src = 9 port_dst = 3
 Jack: JackConnectionManager::Disconnect port_src = 3 port_dst = 9
 Jack: JackConnectionManager::DecConnectionRef: ref1 = 2 ref2 = 0
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::PortDisconnect ref = -1 src = 10 dst = 65535
 Jack: JackEngine::PortDisconnect ref = -1 src = 10 dst = 4
 Jack: JackGraphManager::Disconnect port_src = 10 port_dst = 4
 Jack: JackConnectionManager::Disconnect port_src = 10 port_dst = 4
 Jack: JackConnectionManager::Disconnect port_src = 4 port_dst = 10
 Jack: JackConnectionManager::DirectDisconnect last: ref1 = 2 ref2 = 0
 Jack: JackConnectionManager::DecConnectionRef: ref1 = 2 ref2 = 0
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::ClientNotify: no callback for notification = 12
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackEngine::ClientNotify: no callback for notification = 10
 Jack: JackConnectionManager::DirectDisconnect last: ref1 = 2 ref2 = 1
 Jack: JackGraphManager::DisconnectRefNum cur_index = 3 ref1 = 2 ref2 = 1
 Jack: JackConnectionManager::DirectDisconnect last: ref1 = 1 ref2 = 2
 Jack: JackGraphManager::DisconnectRefNum cur_index = 3 ref1 = 1 ref2 = 2
 Jack: 

Bug#852216: kodi: FTBFS on mips64el

[Julien Cristau]

Source: kodi
Version: 2:17.0~rc3+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

kodi FTBFS on the mips64el buildd:

> PeripheralCecAdapter.cpp: In member function 'virtual void 
> PERIPHERALS::CPeripheralCecAdapter::Announce(ANNOUNCEMENT::AnnouncementFlag, 
> const char*, const char*, const CVariant&)':
> PeripheralCecAdapter.cpp:169:25: error: 'CEC::libcec_configuration {aka 
> struct CEC::libcec_configuration}' has no member named 'bPowerOnScreensaver'
>  if (m_configuration.bPowerOnScreensaver == 1 && !bIgnoreDeactivate &&
>  ^~~

Full log at
https://buildd.debian.org/status/fetch.php?pkg=kodi=mips64el=2%3A17.0~rc3%2Bdfsg1-1=1484804663=0

Cheers,
Julien

Bug#852122: marked as done (sidedoor-sudo: fails to install: cp: cannot create regular file '/etc/sudoers.d/sidedoor': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 15:50:37 +
with message-id 
and subject line Bug#852122: fixed in sidedoor 0.2.0-2
has caused the Debian Bug report #852122,
regarding sidedoor-sudo: fails to install: cp: cannot create regular file 
'/etc/sudoers.d/sidedoor': 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.)


-- 
852122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sidedoor-sudo
Version: 0.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package sidedoor-sudo.
  (Reading database ... 
(Reading database ... 4861 files and directories currently installed.)
  Preparing to unpack .../sidedoor-sudo_0.2.0-1_all.deb ...
  Unpacking sidedoor-sudo (0.2.0-1) ...
  Setting up sidedoor-sudo (0.2.0-1) ...
  
  Creating config file /etc/sudoers.d/sidedoor with new version
  cp: cannot create regular file '/etc/sudoers.d/sidedoor': No such file or 
directory
  dpkg: error processing package sidedoor-sudo (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   sidedoor-sudo


cheers,

Andreas


sidedoor-sudo_0.2.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sidedoor
Source-Version: 0.2.0-2

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

Debian distribution maintenance software
pp.
Dara Adib  (supplier of updated sidedoor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Jan 2017 01:41:58 -0500
Source: sidedoor
Binary: sidedoor sidedoor-sudo
Architecture: source all
Version: 0.2.0-2
Distribution: sid
Urgency: medium
Maintainer: Dara Adib 
Changed-By: Dara Adib 
Description:
 sidedoor   - SSH connection daemon
 sidedoor-sudo - SSH connection daemon - sudoers entry
Closes: 852122
Changes:
 sidedoor (0.2.0-2) unstable; urgency=medium
 .
   * Fixes to sidedoor-sudo.
 - Add sudo to Depends. (Closes: #852122)
 - Allow package removal even if disabling with ucf fails.
Checksums-Sha1:
 ade4befdccca03ded119b333e271d4c75809c79d 2030 sidedoor_0.2.0-2.dsc
 cf0596918e9f711fef1525cbc3d1c038e612e5f5 16474 sidedoor_0.2.0.orig.tar.gz
 e8ece2e8dacb92674f003770b65cbd920aa716c5 6192 sidedoor_0.2.0-2.debian.tar.xz
 731f52315bbe3713978b9bfa84bb0b202d5891b3 3010 sidedoor-sudo_0.2.0-2_all.deb
 ad57812305e683f451c03c348249e0dbc83a4ba5 12306 sidedoor_0.2.0-2_all.deb
 cfed4ac568df7500b9c7edda687747a506df247a 4648 sidedoor_0.2.0-2_amd64.buildinfo
Checksums-Sha256:
 66ebb882e93ac7640a35be662c9b836b881db9a33baef2a3f47f5c622996e681 2030 
sidedoor_0.2.0-2.dsc
 467986d82e656e83759e82e8a796eb5b2ddd02608d46381dc5129f83741dc45b 16474 
sidedoor_0.2.0.orig.tar.gz
 d919360c0ae215cfbc7fdeffe6a53ed386a2f8c4013ea49374ec8c4240e5ebec 6192 
sidedoor_0.2.0-2.debian.tar.xz
 61045bf94603cee7d88bb4ec00f1ffda3207c86fcc8a4d3a89592b3cfcadbd09 3010 
sidedoor-sudo_0.2.0-2_all.deb
 e6421a17ec3633e2dd5874cd5c47684941abed5c47c04050c07313b2634ce5d5 12306 
sidedoor_0.2.0-2_all.deb
 afde013f9260c822615a4ca8c800627e86ae6d73f011344563330d08b2b89293 4648 
sidedoor_0.2.0-2_amd64.buildinfo
Files:
 48d65087996955d3a229c29d5d4cdea8 2030 net optional sidedoor_0.2.0-2.dsc
 b00c4eb38c6feae620761139ffbd40aa 16474 net optional sidedoor_0.2.0.orig.tar.gz
 b80fd220782ab8eedb17e151a6937dc8 6192 net optional 
sidedoor_0.2.0-2.debian.tar.xz
 7ea98133d630bda98a1c988155747103 3010 net optional 
sidedoor-sudo_0.2.0-2_all.deb
 894374727c95ebb67b12551976c0e42a 12306 net optional sidedoor_0.2.0-2_all.deb
 da0942a7266d881c4dd48f482e65cc58 4648 net optional 

Bug#851564: marked as done (nslcd fails to start: postinst sets tls_cacertdir wrong)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 15:49:31 +
with message-id 
and subject line Bug#851564: fixed in nss-pam-ldapd 0.9.7-2
has caused the Debian Bug report #851564,
regarding nslcd fails to start: postinst sets tls_cacertdir wrong
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.)


-- 
851564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nslcd
Version: 0.9.4-3+deb8u2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after upgrading Debian Jessie to release 8.7 (from 8.6)the package nslcd
renders unusable because the nslcd daemon fails to start

The error message as reported by /var/log/daemon.log is:

Jan 16 11:45:28 v303855 nslcd[20591]: Starting LDAP connection daemon:
nslcdnslcd: /etc/nslcd.conf:52: tls_cacertfile: too may arguments

Which references the setting
tls_cacertfile dir /etc/ssl/certs/

The aforementioned setting is probably added to the file via the
postinstall script of the nslcd package.  If one removes the line
tls_cacertfile dir /etc/ssl/certs from the file /etc/nslcd.conf and runs
# dpkg --configrue -a
the line reappers and nslcd is still unable to start.

Regards

Thomas Wallrafen


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

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

Versions of packages nslcd depends on:
ii  adduser3.113+nmu3
ii  debconf [debconf-2.0]  1.5.56
ii  libc6  2.19-18+deb8u7
ii  libgssapi-krb5-2   1.12.1+dfsg-19+deb8u2
ii  libldap-2.4-2  2.4.40+dfsg-1+deb8u2

Versions of packages nslcd recommends:
ii  bind9-host [host]   1:9.9.5.dfsg-9+deb8u9
ii  ldap-utils  2.4.40+dfsg-1+deb8u2
iu  libnss-ldapd [libnss-ldap]  0.9.4-3+deb8u2
ii  libpam-ldap 184-8.7+b1
ii  nscd2.19-18+deb8u7
iu  nslcd-utils 0.9.4-3+deb8u2

Versions of packages nslcd suggests:
pn  kstart  

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: nss-pam-ldapd
Source-Version: 0.9.7-2

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

Debian distribution maintenance software
pp.
Arthur de Jong  (supplier of updated nss-pam-ldapd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Jan 2017 16:00:00 +0100
Source: nss-pam-ldapd
Binary: nslcd pynslcd libnss-ldapd libpam-ldapd nslcd-utils
Architecture: source amd64 all
Version: 0.9.7-2
Distribution: unstable
Urgency: medium
Maintainer: Arthur de Jong 
Changed-By: Arthur de Jong 
Description:
 libnss-ldapd - NSS module for using LDAP as a naming service
 libpam-ldapd - PAM module for using LDAP as an authentication service
 nslcd  - daemon for NSS and PAM lookups using LDAP
 nslcd-utils - utilities for querying LDAP via nslcd
 pynslcd- daemon for NSS and PAM lookups via LDAP - Python version
Closes: 836720 851564
Changes:
 nss-pam-ldapd (0.9.7-2) unstable; urgency=medium
 .
   * recommend ca-certificate which is needed due to adding tls_cacertfile by
 default (see #750949) and the checking of tls_cacertfile in 0.9.7
 (closes: #836720)
   * fix parsing of nslcd.conf tls_cacert option in package configuration
 (closes: #851564)
   * add dependency on lsb-base for init script (thanks lintian)
Checksums-Sha1:
 5eb0507d208caa7854ca1f5a35debaa824d7fdcc 2391 nss-pam-ldapd_0.9.7-2.dsc
 f2ee5790ec0aeb7fdcedd10e79a9c754d0a6ddf4 131720 
nss-pam-ldapd_0.9.7-2.debian.tar.xz
 878d04809d8b14e04dbf22c5965e94a05f702f55 45482 
libnss-ldapd-dbgsym_0.9.7-2_amd64.deb
 9424f50743a1e31e9402e1f1e94b1b4c769f9cc5 66210 libnss-ldapd_0.9.7-2_amd64.deb
 66ef7f8b751bcb73311f6aca2f52fcfc0e8f2aae 26730 

Bug#850762: marked as done (setserial: missing dependency on lsb-base)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 15:50:31 +
with message-id 
and subject line Bug#850762: fixed in setserial 2.17-50
has caused the Debian Bug report #850762,
regarding setserial: missing dependency on lsb-base
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.)


-- 
850762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: setserial
Version: 2.17-49.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package setserial.
  (Reading database ... 
(Reading database ... 4394 files and directories currently installed.)
  Preparing to unpack .../setserial_2.17-49.1_amd64.deb ...
  Unpacking setserial (2.17-49.1) ...
  Setting up setserial (2.17-49.1) ...
  removing the old setserial entry in the rcn.d directories
  Update complete.
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  /etc/init.d/setserial: 35: .: Can't open /lib/lsb/init-functions
  dpkg: error processing package setserial (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   setserial


cheers,

Andreas


setserial_2.17-49.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: setserial
Source-Version: 2.17-50

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated setserial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Jan 2017 15:39:00 +0100
Source: setserial
Binary: setserial
Architecture: source amd64
Version: 2.17-50
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 setserial  - controls configuration of serial ports
Closes: 830887 850762
Changes:
 setserial (2.17-50) unstable; urgency=medium
 .
   * ack NMU, thanks to Martin Pitt and Christian Hofstaedtler for
 taking care of this
   * debian/control: add dependency to lsb-base (Closes: #850762)
   * debian/postrm: take care of old files (Closes: #830887)
Checksums-Sha1:
 2ec6576e0963bc5fdef95fe984699d06ee6a94dd 1867 setserial_2.17-50.dsc
 68824494a0b5700f7e999564a59358bf34f79eb1 52437 setserial_2.17.orig.tar.gz
 68d3f60df5ba58f465f9046c9ba4b88463262bfa 54940 setserial_2.17-50.debian.tar.xz
 ca0969dfd3c0e3b5cdcdd0e9409f0743b3fbaee8 15454 
setserial-dbgsym_2.17-50_amd64.deb
 b6649f725d33b0b99f40e1f0e9404adaae339b6e 4666 setserial_2.17-50_amd64.buildinfo
 9b65255f3e75b5a6a3353a398367334c0c4bcc20 50508 setserial_2.17-50_amd64.deb
Checksums-Sha256:
 d8117c2b3c33e8723882f79c5478631f0e2278e7926a10684b3b926c879bd7ae 1867 
setserial_2.17-50.dsc
 7e4487d320ac31558563424189435d396ddf77953bb23111a17a3d1487b5794a 52437 
setserial_2.17.orig.tar.gz
 93e647c350e769996a7cf4e561618f181c8700d503227752e6066d69a81a32e5 54940 
setserial_2.17-50.debian.tar.xz
 225cac709dc2b42dcb521f95f3cde84b8cbc9c9aa6d01ca05f58bdefd0933f84 15454 
setserial-dbgsym_2.17-50_amd64.deb
 0006c88a4a502bee0eb0d0c30d7f3cb027db98398ec8421f6edb315814ccca4e 4666 
setserial_2.17-50_amd64.buildinfo
 ea8ae74214ebcda7af8ff9cef0d0811c5af8a6a935e8cf15ef088d6efe82b942 50508 
setserial_2.17-50_amd64.deb
Files:
 8daa714d3d27d8c09d12cc4b73d2a892 1867 comm extra setserial_2.17-50.dsc
 

Bug#852214: musl 1.1.16 fails to build on armhf

[Reiner Herrmann]

Source: musl
Version: 1.1.16-1
Severity: serious
Forwarded: http://www.openwall.com/lists/musl/2017/01/04/6

Since 1.1.16-1 musl doesn't build on armhf [0]:

> cc -std=c99 -nostdinc -ffreestanding -fexcess-precision=standard 
> -frounding-math -Wa,--noexecstack -D_XOPEN_SOURCE=700 -I./arch/arm 
> -I./arch/generic -Iobj/src/internal -I./src/internal -Iobj/include 
> -I./include -Wdate-time -D_FORTIFY_SOURCE=2 -g -pipe -fno-unwind-tables 
> -fno-asynchronous-unwind-tables -ffunction-sections -fdata-sections 
> -Werror=implicit-function-declaration -Werror=implicit-int 
> -Werror=pointer-sign -Werror=pointer-arith -include vis.h 
> -Wa,-mimplicit-it=always -Wa,-mthumb -g -O2 
> -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fPIC -c -o obj/src/thread/arm/atomics.lo 
> src/thread/arm/atomics.s
> src/thread/arm/atomics.s: Assembler messages:
> src/thread/arm/atomics.s:59: Error: invalid constant (1) after fixup
> src/thread/arm/atomics.s:74: Error: invalid constant (1) after fixup

The issue is also caused by a change in binutils 2.27.51.20161105-1,
which has more strict checking of assembly files [1] [2].

I noticed that 1.1.16-1 builds fine on rebootstrap [3]. The difference
seems to be that thumb2 support is not detected and disabled.
(I could also confirm that building without -Wa,-mthumb succeeds.)

[0]: 
https://buildd.debian.org/status/fetch.php?pkg=musl=armhf=1.1.16-1=1483481970=0
[1]: https://sourceware.org/ml/binutils/2017-01/msg00081.html
[2]: 
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=bada43421274615d0d5f629a61a60b7daa71bc15
[3]: 
https://jenkins.debian.net/view/rebootstrap/job/rebootstrap_musl-linux-arm64_gcc6/20/


signature.asc
Description: Digital signature

Processed: bug 844943 is forwarded to https://github.com/mozilla/bleach/issues/229

[Debian Bug Tracking System]

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

> forwarded 844943 https://github.com/mozilla/bleach/issues/229
Bug #844943 [src:python-bleach] python-bleach: FTBFS: ImportError: No module 
named sanitizer
Changed Bug forwarded-to-address to 
'https://github.com/mozilla/bleach/issues/229' from 
'https://github.com/mozilla/bleach/issues/212'.
> thanks
Stopping processing here.

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

Bug#851966: marked as done (texlive-bibtex-extra: biblatex breaks compatibility with biber)

[Debian Bug Tracking System]

Your message dated Sun, 22 Jan 2017 15:34:36 +
with message-id 
and subject line Bug#851966: fixed in texlive-extra 2016.20170118-2
has caused the Debian Bug report #851966,
regarding texlive-bibtex-extra: biblatex breaks compatibility with biber
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.)


-- 
851966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-bibtex-extra
Version: 2016.20170118-1
Severity: grave
Justification: renders package unusable

The new version of biblatex in this package cannot be used with biber.
That makes this biblatex unusable.

Output looks like:
$ biber project
INFO - This is Biber 2.6
INFO - Logfile is 'project.blg'
INFO - Reading 'project.bcf'
ERROR - Error: Found biblatex control file version 3.3, expected version 3.2.
This means that your biber (2.6) and biblatex (3.7) versions are incompatible.
See compat matrix in biblatex or biber PDF documentation.
INFO - ERRORS: 1

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

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

Versions of packages texlive-bibtex-extra depends on:
ii  tex-common  6.06
ii  texlive-base2016.20170118-1
ii  texlive-binaries2016.20160513.41080.dfsg-1
ii  texlive-latex-base  2016.20170118-1

texlive-bibtex-extra recommends no packages.

texlive-bibtex-extra suggests no packages.

Versions of packages tex-common depends on:
ii  dpkg  1.18.18
ii  ucf   3.0036

Versions of packages tex-common suggests:
ii  debhelper  10.2.3

Versions of packages texlive-bibtex-extra is related to:
ii  tex-common6.06
ii  texlive-binaries  2016.20160513.41080.dfsg-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2016.20170118-2

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 22 Jan 2017 22:35:05 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-formats-extra texlive-generic-extra texlive-plain-extra 
texlive-latex-extra texlive-fonts-extra texlive-music texlive-games 
texlive-pstricks texlive-publishers texlive-humanities texlive-science 
texlive-htmlxml etoolbox texlive-fonts-extra-doc texlive-humanities-doc 
texlive-latex-extra-doc texlive-science-doc texlive-pstricks-doc 
texlive-publishers-doc
Architecture: source all
Version: 2016.20170118-2
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 etoolbox   - TeX Live: transitional dummy package
 texlive-bibtex-extra - TeX Live: BibTeX additional styles
 texlive-extra-utils - TeX Live: TeX auxiliary programs
 texlive-font-utils - TeX Live: Graphics and font utilities
 texlive-fonts-extra - TeX Live: Additional fonts
 texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra
 texlive-formats-extra - TeX Live: Additional formats
 texlive-games - TeX Live: Games typesetting
 texlive-generic-extra - TeX Live: Generic additional packages
 texlive-htmlxml - TeX Live: HTML/SGML/XML support
 texlive-humanities - TeX Live: Humanities packages
 texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities
 texlive-latex-extra - TeX Live: LaTeX additional packages
 texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra
 texlive-music - TeX Live: Music packages
 texlive-plain-extra - TeX Live: Plain TeX packages