Bug#807097: [Python-modules-team] Bug#807097: python-django: Undeclared removal of previously supported features causes crashes

[Brian May]

Neil Williams  writes:

>> From your stack trace it would appear that the calling application -
>> django-hijack - doesn't actually use add_to_builtins, however it uses
>> the file from django-compat that tries to import the symbol anyway.
>
> ARRRGGHHH! OK, that looks like hijack should test the import more
> carefully to identify the right support.

Think the problem is in django-compat, not django-hijack???

Somebody needs to package the latest django-compat, and this problem
should go away.
-- 
Brian May 

Processed: reassign 807348 to src:gnutls28, forcibly merging 805863 807348

[Debian Bug Tracking System]

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

> reassign 807348 src:gnutls28
Bug #807348 [gnutls28] libgnutls-deb0-28: In multiarch, 3.3.19-1:i386 conflict 
with 3.3.18-1:amd64
Bug reassigned from package 'gnutls28' to 'src:gnutls28'.
Ignoring request to alter found versions of bug #807348 to the same values 
previously set
Ignoring request to alter fixed versions of bug #807348 to the same values 
previously set
> # binaries cannot be there without a build.
> forcemerge 805863 807348
Bug #805863 [src:gnutls28] gnutls28: FTBFS on amd64 - testsuite failures
Bug #807348 [src:gnutls28] libgnutls-deb0-28: In multiarch, 3.3.19-1:i386 
conflict with 3.3.18-1:amd64
Set Bug forwarded-to-address to 
'http://mid.gmane.org/20151124184945.GB4525%40downhill.g.la'.
Severity set to 'serious' from 'important'
Marked as found in versions gnutls28/3.4.7-1 and gnutls28/3.3.19-1.
Merged 805863 807348
> thanks
Stopping processing here.

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

Bug#807371: apt hostname resoloution failure

[Niels Thykier]

peter green:
> Package: apt
> Version: 1.1.3
> Severity: grave
> 
> When running apt in a Debian stretch armhf chroot on my odriod u2 DNS
> resoloution fails. ping is able to resolve the hostname.
> 
> [...]
> 
> The chroot is on a host system running a vendor 3.0.90 kernel, no idea
> if that is relavent. At the very least if there is a problem running on
> older kernels there should be a warning before the updated packages are
> installed.
> 
> The issue seems to be new in the 1.1 series of apt versions.
> 
> The issue definately seems to be somehow related to dns lookups. If I
> add the hostname to /etc/resolv.conf then apt seems to work.
> 
> Any thoughts on how to debug this.
> 

Is this chroot managed with/created by pbuilder/cowbuilder?

There is currently some bugs against pbuilder/cowbuilder where it fails
to update resolv.conf.  This leaves the chroot without DNS if it was
created in a different network than the one the machine is currently in.

Thanks,
~Niels

Processed (with 1 error): reassign 807348 to gnutls28, forcibly merging 805863 807348

[Debian Bug Tracking System]

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

> reassign 807348 gnutls28
Bug #807348 [libgnutls-deb0-28] libgnutls-deb0-28: In multiarch, 3.3.19-1:i386 
conflict with 3.3.18-1:amd64
Bug reassigned from package 'libgnutls-deb0-28' to 'gnutls28'.
No longer marked as found in versions gnutls28/3.3.19-1.
Ignoring request to alter fixed versions of bug #807348 to the same values 
previously set
> # binaries cannot be there without a build.
> forcemerge 805863 807348
Bug #805863 [src:gnutls28] gnutls28: FTBFS on amd64 - testsuite failures
Unable to merge bugs because:
package of #807348 is 'gnutls28' not 'src:gnutls28'
Failed to forcibly merge 805863: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#797793: samtools update seems to breaks even more tests

[Afif Elghraoui]

Hi, Andreas,

على الإثنين  7 كانون الأول 2015 ‫01:10، كتب Andreas Tille:
> 
> Hmmm, I have seen commit 7c93b9c0d42c415ef3296e6ee4a7d61b6fc34cb8 but I
> remain with failures even on amd64. :-(
> 
> 
> ...
> File "../doc/tss.rst", line 211, in tss.rst
> Failed example:
> for almnt in sortedbamfile[ window ]:
> print almnt   #doctest:+ELLIPSIS +NORMALIZE_WHITESPACE
> Exception raised:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/doctest.py", line 1315, in __run
> compileflags, 1) in test.globs
>   File "", line 1, in 
> for almnt in sortedbamfile[ window ]:
>   File 
> "/build/htseq-0.6.1p1/build/lib.linux-x86_64-2.7/HTSeq/__init__.py", line 
> 975, in __getitem__
> self.sf = pysam.AlignmentFile( self.filename, "rb" )
> AttributeError: 'module' object has no attribute 'AlignmentFile'
> **


This error appears like you're somehow using an old version of pysam
because AlignmentFile was introduced in 0.8.1. Are you sure you're not
accidentally building with a Jessie chroot (where pysam is at version
0.7.7) rather than an Unstable one?

[...]
> 
> 
> Strange that you can not reproduce this.
> 

I just made sure my working directory was clean and tried building
again. It still works for me...

regards
Afif


-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Processed: your mail

[Debian Bug Tracking System]

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

> severity 788740 serious
Bug #788740 [src:hexer] hexer: FTBFS with glibc-2.21 and gcc-5
Severity set to 'serious' from 'normal'
> # hexer now FTBFS in unstable
> thanks
Stopping processing here.

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

Bug#795762: marked as done (ruby-twitter-stream: FTBFS: /usr/bin/ruby2.1 /usr/bin/rspec --pattern ./spec/\*/\*_spec.rb failed)

[Debian Bug Tracking System]

Your message dated Tue, 8 Dec 2015 10:59:54 +0530
with message-id <5ad2.4020...@debian.org>
and subject line fixed
has caused the Debian Bug report #795762,
regarding ruby-twitter-stream: FTBFS: /usr/bin/ruby2.1 /usr/bin/rspec --pattern 
./spec/\*/\*_spec.rb 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.)


-- 
795762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-twitter-stream
Version: 0.1.16-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-twitter-stream fails to build from source on unstable/amd64:

  [..]
  Failed examples:
  
  rspec ./spec/twitter/json_stream_spec.rb:25 # Twitter::JSONStream
  authentication should connect with basic auth credentials
  rspec ./spec/twitter/json_stream_spec.rb:30 # Twitter::JSONStream
  authentication should connect with oauth credentials
  rspec ./spec/twitter/json_stream_spec.rb:50 # Twitter::JSONStream on
  create should define default properties
  rspec ./spec/twitter/json_stream_spec.rb:60 # Twitter::JSONStream on
  create should connect to the proxy if provided
  rspec ./spec/twitter/json_stream_spec.rb:90 # Twitter::JSONStream on
  valid stream should add no params
  rspec ./spec/twitter/json_stream_spec.rb:95 # Twitter::JSONStream on
  valid stream should add custom params
  rspec ./spec/twitter/json_stream_spec.rb:100 # Twitter::JSONStream on
  valid stream should parse headers
  rspec ./spec/twitter/json_stream_spec.rb:106 # Twitter::JSONStream on
  valid stream should parse headers even after connection close
  rspec ./spec/twitter/json_stream_spec.rb:112 # Twitter::JSONStream on
  valid stream should extract records
  rspec ./spec/twitter/json_stream_spec.rb:117 # Twitter::JSONStream on
  valid stream should allow custom headers
  rspec ./spec/twitter/json_stream_spec.rb:122 # Twitter::JSONStream on
  valid stream should deliver each item
  rspec ./spec/twitter/json_stream_spec.rb:137 # Twitter::JSONStream on
  valid stream should swallow StandardError exceptions when delivering
  items
  rspec ./spec/twitter/json_stream_spec.rb:146 # Twitter::JSONStream on
  valid stream propagates out runtime errors when delivering items
  rspec ./spec/twitter/json_stream_spec.rb:154 # Twitter::JSONStream on
  valid stream should send correct user agent
  rspec ./spec/twitter/json_stream_spec.rb:212 # Twitter::JSONStream on
  network failure should timeout on inactivity
  rspec ./spec/twitter/json_stream_spec.rb:218 # Twitter::JSONStream on
  network failure should not reconnect on inactivity when not configured
  to auto reconnect
  rspec ./spec/twitter/json_stream_spec.rb:224 # Twitter::JSONStream on
  network failure should reconnect with SSL if enabled
  rspec ./spec/twitter/json_stream_spec.rb[1:4:4:1] #
  Twitter::JSONStream on network failure it should behave like network
  failure should reconnect on network failure
  rspec ./spec/twitter/json_stream_spec.rb[1:4:4:2] #
  Twitter::JSONStream on network failure it should behave like network
  failure should not reconnect on network failure when not configured to
  auto reconnect
  rspec ./spec/twitter/json_stream_spec.rb[1:4:4:3] #
  Twitter::JSONStream on network failure it should behave like network
  failure should reconnect with 0.25 at base
  rspec ./spec/twitter/json_stream_spec.rb[1:4:4:4] #
  Twitter::JSONStream on network failure it should behave like network
  failure should reconnect with linear timeout
  rspec ./spec/twitter/json_stream_spec.rb[1:4:4:5] #
  Twitter::JSONStream on network failure it should behave like network
  failure should stop reconnecting after 100 times
  rspec ./spec/twitter/json_stream_spec.rb[1:4:4:6] #
  Twitter::JSONStream on network failure it should behave like network
  failure should notify after reconnect limit is reached
  rspec ./spec/twitter/json_stream_spec.rb:240 # Twitter::JSONStream on
  no data received should call no data callback after no data received
  for 90 seconds
  rspec ./spec/twitter/json_stream_spec.rb[1:6:1:1] #
  Twitter::JSONStream on server unavailable it should behave like
  network failure should reconnect on network failure
  rspec ./spec/twitter/json_stream_spec.rb[1:6:1:2] #
  Twitter::JSONStream on server unavailable it should behave like
  network failure should not reconnect on network failure when not
  configured to auto reconnect
  rspec ./spec/twitter/json_stream_spec.rb[1:6:1:3] #
 

Bug#806231: marked as done (rasdaemon: FTBFS: autoreconf: Command not found)

[Debian Bug Tracking System]

Your message dated Tue, 08 Dec 2015 03:44:26 +
with message-id 
and subject line Bug#806231: fixed in rasdaemon 0.5.6-2
has caused the Debian Bug report #806231,
regarding rasdaemon: FTBFS: autoreconf: 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.)


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

Builds of rasdaemon in minimal environments (notably, on the
autobuilders) have been failing:

  dh build-arch  --with autotools-dev
 dh_testdir -a
 dh_autotools-dev_updateconfig -a
 debian/rules override_dh_auto_configure
  make[1]: Entering directory '/«PKGBUILDDIR»'
  autoreconf
  make[1]: autoreconf: Command not found
  debian/rules:27: recipe for target 'override_dh_auto_configure' failed
  make[1]: *** [override_dh_auto_configure] Error 127
  make[1]: Leaving directory '/«PKGBUILDDIR»'
  debian/rules:22: recipe for target 'build-arch' failed
  make: *** [build-arch] Error 2

Please declare a build dependency on autoconf in addition to
autotools-dev, and check with pbuilder or the like that you haven't
missed anything else.  (In particular, I suspect you might also need
to list automake and libtool.)

Thanks!
--- End Message ---
--- Begin Message ---
Source: rasdaemon
Source-Version: 0.5.6-2

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

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

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

Debian distribution maintenance software
pp.
ahs3  (supplier of updated rasdaemon 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, 07 Dec 2015 19:22:01 -0700
Source: rasdaemon
Binary: rasdaemon
Architecture: source amd64
Version: 0.5.6-2
Distribution: unstable
Urgency: medium
Maintainer: Al Stone 
Changed-By: ahs3 
Description:
 rasdaemon  - utility to receive RAS error tracings
Closes: 806231 806412
Changes:
 rasdaemon (0.5.6-2) unstable; urgency=medium
 .
   * Closes: #806412 -- add in build-depends on dh-autoreconf
   * Closes: #806231 -- add in build-depends on autoconf
   * Test properly with pbuilder this time
Checksums-Sha1:
 7d6f0cd3e944b58a6cb29fa31f516a4cc58faaf4 1853 rasdaemon_0.5.6-2.dsc
 4ead3ce3307edc764485d8271d389be8941c74b7 3884 rasdaemon_0.5.6-2.debian.tar.xz
 e4296a453b4171e4bdcea6605b98d3917d47a526 70698 rasdaemon_0.5.6-2_amd64.deb
Checksums-Sha256:
 9950095fab313a6dc0f4b32a377cd595f40ae2dd760a47e927363de36ec00a83 1853 
rasdaemon_0.5.6-2.dsc
 9a23fba29fcc2c8fb73b839356ed3648b6cfce6aa81822c64051188941284c6e 3884 
rasdaemon_0.5.6-2.debian.tar.xz
 a51c5984134bf0bd4cf51ac8ed98e62763c997f1b283b9cd4b7f9424c6eac31b 70698 
rasdaemon_0.5.6-2_amd64.deb
Files:
 daef5525e80dcde13483a08a24110ea5 1853 admin optional rasdaemon_0.5.6-2.dsc
 8f9b6126d4fa489cea6994b5e6bbd73c 3884 admin optional 
rasdaemon_0.5.6-2.debian.tar.xz
 9421dd7842da38683680202191b6f4a0 70698 admin optional 
rasdaemon_0.5.6-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBVmZCK1MMsALXYbFsAQjK9A//W9zLUMRrlMtPTyQbqBPGMXwbzX/w57gk
yYTbks+sqdj1SG56zUj4P/MVLXNFgbzcKUhcWDo/SnQgWR73OhASBTAadcIpExst
AsJJMoiGZGIgzTXJgyqEGtBvqZug/W32xhpuKTOBPcbB5//JUX+97tOrSrCa6eZ/
LgQX09EzXDSLzzuYqX8jPgCTqiTRFF25Gi/u1MuScG1QiAKGetkWFu0XeV8ajbuH
1JuGzRvwvo8TkMKwgqtcWvwN1oQeeBFatRuVcej1/LvgfpkujtXsNzaVtzQffDpv
y6MM4TwgBGuzkSvaA74NHQqa3NqOnA2d78pPYHUwvRPOvAl31DMyorsYDCizReTD
DzIpiZRF4wiAz5ne7HwX93FtnJUal6z2pXunudz/4frXQaAhOcSSza5u+mEX4M68
S8EG2V+0xb3O3KcZLzAaOxXn0YVw1SeQYW4V44+pCsdIiGNs2a5bqdmrMtLeLe/e
wZYk+WjGjM35q87cbeGuWKz+LUxnN1EtVSiTgB1g3X5cNKMejzA48Pem0xWvrnxQ
OuowEmvhx87rarWpDOdQwafCS0O7Ur7+wZET9Uw2ryz5WYSTtTuvfoDSM7ZvuaOG
GP4yKyI4gl7nrPHESLNx8pe29zQrwfEsLP/0oJCLmnuAF1HFcBn4FZpBIR0PsmpD
+fCz3Q15dbY=
=mKGJ
-END PGP SIGNATURE End Message ---

Bug#806412: marked as done (rasdaemon: Missing Build-Depends on dh-autoreconf)

[Debian Bug Tracking System]

Your message dated Tue, 08 Dec 2015 03:44:26 +
with message-id 
and subject line Bug#806412: fixed in rasdaemon 0.5.6-2
has caused the Debian Bug report #806412,
regarding rasdaemon: Missing Build-Depends on dh-autoreconf
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.)


-- 
806412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rasdaemon
Version: 0.5.6-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
Tags: patch

Dear Maintainer,

rasdaemon fails to build from source in unstable/amd64 dueto missing
Build-Depends on dh-autoreconf:

  [..]

  I: Building the build Environment
  I: extracting base tarball
  [/var/cache/pbuilder/unstable-reproducible-base.tgz]
  I: copying local configuration
  I: mounting /proc filesystem
  I: mounting /run/shm filesystem
  I: mounting /dev/pts filesystem
  I: Mounting /dev/shm
  I: Mounting /sys
  I: policy-rc.d already exists
  I: Installing the build-deps
   -> Attempting to satisfy build-dependencies
   -> Creating pbuilder-satisfydepends-dummy package
  Package: pbuilder-satisfydepends-dummy
  Version: 0.invalid.0
  Architecture: amd64
  Maintainer: Debian Pbuilder Team
  
  Description: Dummy package to satisfy dependencies with aptitude -
  created by pbuilder
   This package was created automatically by pbuilder to satisfy the
   build-dependencies of the package being currently built.
  Depends: debhelper (>= 9), autotools-dev, quilt, libsqlite3-dev,
  libgettextpo-dev, dh-systemd
  dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
  '/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
  Selecting previously unselected package pbuilder-satisfydepends-dummy.
  (Reading database ... 20353 files and directories currently
  installed.)
  Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
  Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
  dpkg: pbuilder-satisfydepends-dummy: dependency problems, but
  configuring anyway as you requested:
   pbuilder-satisfydepends-dummy depends on autotools-dev; however:
Package autotools-dev is not installed.
   pbuilder-satisfydepends-dummy depends on quilt; however:
Package quilt is not installed.
   pbuilder-satisfydepends-dummy depends on libsqlite3-dev; however:
Package libsqlite3-dev is not installed.
   pbuilder-satisfydepends-dummy depends on libgettextpo-dev; however:
Package libgettextpo-dev is not installed.
   pbuilder-satisfydepends-dummy depends on dh-systemd; however:
Package dh-systemd is not installed.
  
  Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Initializing package states...
  Writing extended state information...
  Building tag database...
  pbuilder-satisfydepends-dummy is already installed at the requested
  version (0.invalid.0)
  pbuilder-satisfydepends-dummy is already installed at the requested
  version (0.invalid.0)
  The following NEW packages will be installed:
autotools-dev{a} dh-systemd{a} diffstat{a} libgettextpo-dev{a} 
libgettextpo0{a} libsqlite3-dev{a} quilt{a} 
  The following packages are RECOMMENDED but will NOT be installed:
less 
  0 packages upgraded, 7 newly installed, 0 to remove and 0 not
  upgraded.
  Need to get 1315 kB of archives. After unpacking 3914 kB will be used.
  Writing extended state information...
  Get: 1 http://ftp.de.debian.org/debian/ unstable/main autotools-dev
  all 20150820.1 [71.7 kB]
  Get: 2 http://ftp.de.debian.org/debian/ unstable/main diffstat amd64
  1.60-1 [30.4 kB]
  Get: 3 http://ftp.de.debian.org/debian/ unstable/main libgettextpo0
  amd64 0.19.6-1 [143 kB]
  Get: 4 http://ftp.de.debian.org/debian/ unstable/main libgettextpo-dev
  amd64 0.19.6-1 [160 kB]
  Get: 5 http://ftp.de.debian.org/debian/ unstable/main libsqlite3-dev
  amd64 3.9.2-1 [580 kB]
  Get: 6 http://ftp.de.debian.org/debian/ unstable/main quilt all 0.63-3
  [312 kB]
  Get: 7 http://ftp.de.debian.org/debian/ unstable/main dh-systemd all
  1.24 [18.7 kB]
  Fetched 1315 kB in 0s (6658 kB/s)
  debconf: delaying package configuration, since apt-utils is not
  installed
  Selecting previously unselected package autotools-dev.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30

Bug#750719: marked as done (sockjs-client: FTBFS against uglify 2.x series - Cannot call method 'parse' of undefined)

[Debian Bug Tracking System]

Your message dated Tue, 08 Dec 2015 03:44:52 +
with message-id 
and subject line Bug#750719: fixed in sockjs-client 0.3.4+dfsg-2
has caused the Debian Bug report #750719,
regarding sockjs-client: FTBFS against uglify 2.x series - Cannot call method 
'parse' of undefined
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.)


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

Source: sockjs-client
Severity: important


Dear maintainer,

your package fails to build from source with uglify version 2.4.13-1,
which is now in experimental and will be soon migrated to unstable.

Here a snip of buildlog:

 [.] Rendering lib/trans-receiver-htmlfile.js
 [.] Rendering lib/trans-receiver-xhr.js
 [.] Rendering lib/test-hooks.js
TypeError: Cannot call method 'parse' of undefined
at minify (/tmp/buildd/sockjs-client-0.3.4+dfsg/bin/render.coffee:47:25)
at Object.tags.include_and_minify 
(/tmp/buildd/sockjs-client-0.3.4+dfsg/bin/render.coffee:72:18)
at render (/tmp/buildd/sockjs-client-0.3.4+dfsg/bin/render.coffee:90:32)
at /tmp/buildd/sockjs-client-0.3.4+dfsg/bin/render.coffee:136:23
at main (/tmp/buildd/sockjs-client-0.3.4+dfsg/bin/render.coffee:139:7)
at Object. 
(/tmp/buildd/sockjs-client-0.3.4+dfsg/bin/render.coffee:144:3)
at Object. 
(/tmp/buildd/sockjs-client-0.3.4+dfsg/bin/render.coffee:146:4)
at Module._compile (module.js:456:26)
at Object.exports.run 
(/usr/lib/coffee-script/lib/coffee-script/coffee-script.js:83:25)
at compileScript 
(/usr/lib/coffee-script/lib/coffee-script/command.js:177:29)
Makefile:10: recipe for target 'sockjs.js' failed
make[2]: *** [sockjs.js] Error 1
make[2]: Leaving directory '/tmp/buildd/sockjs-client-0.3.4+dfsg'
debian/rules:48: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/tmp/buildd/sockjs-client-0.3.4+dfsg'
debian/rules:51: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Thanks in advance,

Leo.
--- End Message ---
--- Begin Message ---
Source: sockjs-client
Source-Version: 0.3.4+dfsg-2

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated sockjs-client 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, 08 Dec 2015 02:17:07 +
Source: sockjs-client
Binary: libjs-sockjs
Architecture: source
Version: 0.3.4+dfsg-2
Distribution: unstable
Urgency: low
Maintainer: Tonnerre LOMBARD 
Changed-By: Mattia Rizzolo 
Description:
 libjs-sockjs - WebSocket emulation - Javascript client
Closes: 750719
Changes:
 sockjs-client (0.3.4+dfsg-2) unstable; urgency=low
 .
   [ Mattia Rizzolo ]
   * Team Upload.
   * debian/watch: import watch file from sepwatch.  Thanks bartm!
   * debian/control: bump Standards-Version to 3.9.6.
 .
   [ Tonnerre LOMBARD ]
   * Modify build coffeescript to work with uglifyjs 2.0. Closes: #750719
Checksums-Sha1:
 5d3ab81d2f59adbd8bfd0d4afa6756405aa1c58e 2020 sockjs-client_0.3.4+dfsg-2.dsc
 97f2178fb180859172d053de45be142f9cbc9bcc 6036 
sockjs-client_0.3.4+dfsg-2.debian.tar.xz
Checksums-Sha256:
 a127c3ded3b9e6bb9f83239ab7b4ffd2862966303339a08b236867c337545376 2020 
sockjs-client_0.3.4+dfsg-2.dsc
 b80642a466480806f86169f7ab84fed3bf5730880fa2f5a02d33a13572416cb4 6036 
sockjs-client_0.3.4+dfsg-2.debian.tar.xz
Files:
 793b0a7a21f085592ca0265756d06700 2020 web optional 
sockjs-client_0.3.4+dfsg-2.dsc
 432cd83974d14404588ad3af4c0b0dce 6036 web optional 
sockjs-client_0.3.4+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWZj6GAAoJEEsEP825REVALasP/RkQytc/xD8ozsskSLrFMwSf
wYXgn+JTzbQ8U+P1AxtLQnrYJEyQzCuoO6XF1wUVRApCJnHIMPzpR+wuOd0MKW72
holwn9m2S7VTFLj0bVFjqy4bybRa0Bo61GMg71OH568gg5eMzZIIYumWWeGGUadj
NrqLcIpSG01yMEcVt9N4ugLxoq9vnyN3EZo9mBs9x2sVAe1zcJH/DfrLJp55Dc8P
CNAp9qQPkcfSSthN

Bug#807371: apt hostname resoloution failure

[peter green]

Package: apt
Version: 1.1.3
Severity: grave

When running apt in a Debian stretch armhf chroot on my odriod u2 DNS 
resoloution fails. ping is able to resolve the hostname.


root@odroidu2:/# apt-get update
Err:1 http://mirror.bytemark.co.uk/debian stretch InRelease
  Could not resolve 'mirror.bytemark.co.uk'
Reading package lists... Done
W: Failed to fetch 
http://mirror.bytemark.co.uk/debian/dists/stretch/InRelease  Could not 
resolve 'mirror.bytemark.co.uk'
W: Some index files failed to download. They have been ignored, or old 
ones used instead.

root@odroidu2:/# ping mirror.bytemark.co.uk
PING mirror.bytemark.co.uk (212.110.161.69) 56(84) bytes of data.
64 bytes from mirror.bytemark.co.uk (212.110.161.69): icmp_seq=1 ttl=57 
time=20.8 ms


The chroot is on a host system running a vendor 3.0.90 kernel, no idea 
if that is relavent. At the very least if there is a problem running on 
older kernels there should be a warning before the updated packages are 
installed.


The issue seems to be new in the 1.1 series of apt versions.

The issue definately seems to be somehow related to dns lookups. If I 
add the hostname to /etc/resolv.conf then apt seems to work.


Any thoughts on how to debug this.

Bug#807368: polymake ticket notification: #879: polymake 2.14r1 fails to build with gmp 6.1

[polymake Trac site]

#879: polymake 2.14r1 fails to build with gmp 6.1
-+-
 Reporter:  bremner  |  Owner:  joswig
 Type:  defect   | Status:  new
 Priority:  major|  Milestone:  3.0
Component:  UNKNOWN  |Version:  development
 Keywords:   |
-+-
 build fails with

 error: call of overloaded 'gcd(mpz_class&, mpz_class&)' is ambiguous

 See

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

 for a more detailed log.

 On a related note, I see libnormaliz is included in Debian now.

--
Ticket URL: 
polymake 
The polymake project

Bug#807331: [Pkg-samba-maint] Bug#807331: Bug#807331: samba: Fails to build from source when not being able to download docbook.xsl

[Jelmer Vernooij]

On Mon, Dec 07, 2015 at 04:07:40PM +0100, John Paul Adrian Glaubitz wrote:
> On 12/07/2015 03:38 PM, Jelmer Vernooij wrote:
> >> That could explain the problem on sparc64 and x32, but it doesn't
> >> segfault on my amd64 machine, yet the download fails. I can run xsltproc
> >> with the URL in my sbuild chroot and it is able to download and parse
> >> the file. However, when I sbuild samba, it still fails. I can't really
> >> wrap my head around what happens here.
> > Do you have /dev/shm available in your sbuild chroot, per that bug?
> 
> Ok, this *does* fix the problem actually. I have to bind-mount dev
> into my chroot and set the permissions to 777. Vry strange that
> xsltproc does not fail when I chroot into my sbuild environment and
> call it directly, but it fails when the samba Python scripts call it.
> 
> In any case, thanks a lot for helping me to pin-point the issue. This
> is indeed a bug in xsltproc then and we can therefore close this bug
> again!
> 
> I will make the necessary modifications to all buildds in question!

You're welcome. Thank you for fixing the buildds, much appreciated!

Cheers,

Jelmer

Bug#807368: polymake fails to build with gmp 6.1

[Matthias Klose]

Package: src:polymake
Version: 2.14r1-1
Severity: serious
Tags: sid stretch

Fails to build with gmp 6.1:

error: call of overloaded 'gcd(mpz_class&, mpz_class&)' is ambiguous

[...]
make[2]: Entering directory 
'/home/packages/tmp/polymake-2.14r1/build.x86_64/bundled/group/apps/matroid'
g++ -c -o projective_plane.o -fPIC -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security 
-I/home/packages/tmp/polymake-2.14r1/include/core-wrappers 
-I/home/packages/tmp/polymake-2.14r1/include/core 
-I/home/packages/tmp/polymake-2.14r1/bundled/group/include/app-wrappers 
-I/home/packages/tmp/polymake-2.14r1/bundled/group/include/apps 
-I../../../../../bundled/lrs/include/app-wrappers 
-I../../../../../bundled/lrs/include/apps 
-I../../../../../bundled/cdd/include/app-wrappers 
-I../../../../../bundled/cdd/include/apps 
-I/home/packages/tmp/polymake-2.14r1/include/app-wrappers 
-I/home/packages/tmp/polymake-2.14r1/include/apps -I/usr/include/cdd 
-I../../../../../bundled/group/external/permlib/include -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -ftemplate-depth-200 
-Wall -Wno-strict-aliasing -Wno-parentheses -fwrapv -fopenmp 
-DPOLYMAKE_APPNAME=matroid -DNDEBUG -DPOLYMAKE_DEBUG=0 -O2 -MD 
/home/packages/tmp/polymake-2.14r1/bundled/group/apps/matroid/src/projective_plane.cc
g++ -shared -L/usr/local/lib -fstack-protector -o ../../lib/matroid.so 
projective_plane.o -Wl,-z,relro -Wl,-z,relro -fopenmp  -lmpfr -lgmp -lpthread 
make[2]: Leaving directory 
'/home/packages/tmp/polymake-2.14r1/build.x86_64/bundled/group/apps/matroid'
make[2]: Entering directory 
'/home/packages/tmp/polymake-2.14r1/build.x86_64/bundled/libnormaliz/apps/polytope'
/usr/bin/perl /home/packages/tmp/polymake-2.14r1/support/guarded_compiler.pl 
g++ -c -o normaliz.o -fPIC -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security 
-I/home/packages/tmp/polymake-2.14r1/include/core-wrappers 
-I/home/packages/tmp/polymake-2.14r1/include/core 
-I/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/include/app-wrappers 
-I/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/include/apps 
-I/home/packages/tmp/polymake-2.14r1/include/app-wrappers 
-I/home/packages/tmp/polymake-2.14r1/include/apps -fopenmp -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -ftemplate-depth-200 
-Wall -Wno-strict-aliasing -Wno-parentheses -fwrapv -fopenmp 
-DPOLYMAKE_APPNAME=polytope -DNDEBUG -DPOLYMAKE_DEBUG=0 -O2 -MD  
-I/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/external/libnormaliz  
-I/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/apps/polytope 
-I/home/packages/tmp/polymake-2.14r1/apps/polytope -include src/normaliz.cc 
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/apps/polytope/src/perl/wrap-normaliz.cc
In file included from 
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/external/libnormaliz/libnormaliz-all.cpp:37:0,
 from 
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/apps/polytope/src/normaliz.cc:39,
 from :0:
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/external/libnormaliz/HilbertSeries.cpp:
 In member function 'void 
libnormaliz::HilbertSeries::computeHilbertQuasiPolynomial() const':
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/external/libnormaliz/HilbertSeries.cpp:358:26:
 error: call of overloaded 'gcd(mpz_class&, mpz_class&)' is ambiguous
 g = gcd(g,quasi_denom);
  ^
In file included from 
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/external/libnormaliz/libnormaliz-all.cpp:25:0,
 from 
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/apps/polytope/src/normaliz.cc:39,
 from :0:
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/external/libnormaliz/integer.cpp:77:22:
 note: candidate: Integer libnormaliz::gcd(const Integer&, const Integer&) 
[with Integer = __gmp_expr<__mpz_struct [1], __mpz_struct [1]>]
 template<> mpz_class gcd(const mpz_class& a, const mpz_class& b) {
  ^
In file included from 
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/apps/polytope/src/normaliz.cc:18:0,
 from :0:
/usr/include/gmpxx.h:3083:1: note: candidate: __gmp_expr::value_type, __gmp_binary_expr<__gmp_expr, 
__gmp_expr, __gmp_gcd_function> > gcd(const __gmp_expr&, const 
__gmp_expr&) [with T = __mpz_struct [1]; U = __mpz_struct [1]; V = 
__mpz_struct [1]; W = __mpz_struct [1]; typename __gmp_resolve_expr::value_type = __mpz_struct [1]]
 __GMP_DEFINE_BINARY_FUNCTION(gcd, __gmp_gcd_function)
 ^
In file included from 
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/external/libnormaliz/libnormaliz-all.cpp:26:0,
 from 
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/apps/polytope/src/normaliz.cc:39,
 from :0:
/home/packages/tmp/polymake-2.14r1/bundled/libnormaliz/external/libnormaliz/vector_operations.cpp:
 In instantiation of 'Integer libnormaliz::v_gcd(const s

Bug#807323: gparted needs policykit-1 but its neither in depends or recommends

[Phillip Susi]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 12/07/2015 11:57 AM, shirish शिरीष wrote:
> Yup, have udisks2 installed.

Just to confirm, can you run /usr/lib/udisks2/udisks2-inhibit and
verify that you get that error?


-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJWZiC8AAoJEBB5UWFcu6UWdjoH/R9bl1ScxaDvNw0dAw5hYTjQ
xVOJ/zbk9DiC11H4xrPC2sLCKlomQnP9Vd7OFbVgX7tOZs0ANly270/VuB1nzqlv
AtfkOy1NEyoAuUXvLPh8CR/kV4a81qFej2wuh+PuyJuUyvBy4/pcSLkcWBvYCkQD
cQZzzXFtxE44u7M3tWr3odYWcg0S7vduUVg12GmnB6yqZYTIVFmjv5FUo/S8IXFW
Sw8WLE3Vzl/m8lLKjeh9Xk3whdcAoLWVpTUC5zbC5pCUw2/qGBUrEwR6hbYWDbim
9FSAnBHydoE8L+cDEh8mOl1IHLoqnWp7JdF0JWWFSZ58qFfAe6iGxGFU12x0xUQ=
=t2mk
-END PGP SIGNATURE-

Processed: Re: Bug#807365: cowbuilder: network broken in cowbuilder - cannot resolve any hostname

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 pbuilder 0.221
Bug #807365 [cowbuilder] cowbuilder: network broken in cowbuilder - cannot 
resolve any hostname
Bug reassigned from package 'cowbuilder' to 'pbuilder'.
No longer marked as found in versions cowdancer/0.75.
Ignoring request to alter fixed versions of bug #807365 to the same values 
previously set
Bug #807365 [pbuilder] cowbuilder: network broken in cowbuilder - cannot 
resolve any hostname
Marked as found in versions pbuilder/0.221.
> forcemerge 806386 -1
Bug #806386 [pbuilder] pbuilder: No more updates /etc/resolv.conf inside the 
chroot, hence no more DNS inside chroot after network change
Bug #807046 [pbuilder] pbuilder: how does name resolution work
Bug #807365 [pbuilder] cowbuilder: network broken in cowbuilder - cannot 
resolve any hostname
Severity set to 'important' from 'grave'
Marked as found in versions pbuilder/0.221.1.
Bug #807046 [pbuilder] pbuilder: how does name resolution work
Merged 806386 807046 807365
> tag 806386 + pending
Bug #806386 [pbuilder] pbuilder: No more updates /etc/resolv.conf inside the 
chroot, hence no more DNS inside chroot after network change
Bug #807046 [pbuilder] pbuilder: how does name resolution work
Bug #807365 [pbuilder] cowbuilder: network broken in cowbuilder - cannot 
resolve any hostname
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.

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

Bug#807365: cowbuilder: network broken in cowbuilder - cannot resolve any hostname

[Mattia Rizzolo]

control: reassign -1 pbuilder 0.221
control: forcemerge 806386 -1
control: tag 806386 + pending

On Tue, Dec 08, 2015 at 08:05:55AM +0900, Norbert Preining wrote:
> probably since one of the updates of pbuilder, cowbuilder stopped 
> being able to resolve host names:

yeah, my fault, fix coming..
-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#807365: cowbuilder: network broken in cowbuilder - cannot resolve any hostname

[Norbert Preining]

Package: cowbuilder
Version: 0.75
Severity: grave
Justification: renders package unusable

Dear all,

probably since one of the updates of pbuilder, cowbuilder stopped 
being able to resolve host names:
# cowbuilder --login --save-after-login
 -> Copying COW directory
  forking: rm -rf /var/cache/pbuilder/build/cow.11509 
  forking: cp -al /var/cache/pbuilder/base.cow 
/var/cache/pbuilder/build/cow.11509 
I: removed stale ilistfile /var/cache/pbuilder/build/cow.11509/.ilist
 -> Invoking pbuilder
  forking: pbuilder login --buildplace /var/cache/pbuilder/build/cow.11509 
--no-targz --internal-chrootexec chroot /var/cache/pbuilder/build/cow.11509 
cow-shell 
W: /root/.pbuilderrc does not exist
I: Running in no-targz mode
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: entering the shell


root@wienerschnitzel:/# apt-get update
Err http://ftp2.jp.debian.org sid InRelease
  
Err http://ftp2.jp.debian.org sid Release.gpg
  Could not resolve 'ftp2.jp.debian.org'
Reading package lists... Done
W: Failed to fetch http://ftp2.jp.debian.org/debian/dists/sid/InRelease  

W: Failed to fetch http://ftp2.jp.debian.org/debian/dists/sid/Release.gpg  
Could not resolve 'ftp2.jp.debian.org'

W: Some index files failed to download. They have been ignored, or old ones 
used instead.



Same happens with any other host. Network seems to be unusable.

Thanks

Norbert


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

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

Versions of packages cowbuilder depends on:
ii  cowdancer  0.75
ii  libc6  2.21-3
ii  pbuilder   0.221.1

cowbuilder recommends no packages.

cowbuilder suggests no packages.

-- no debconf information

Bug#807019: tracking bin-num - broken unison due to binnmu upload

[Norbert Preining]

Dear Stéphane,

> But I now understand the problem: unison2.40.102 uses Obj.magic (i.e. an
> unsafe coercion) to cast a format string into a string. The previous
> unison version was compiled with OCaml 4.01.0, where format strings were
> indeed strings. The new version was compiled with OCaml 4.02.3, where it
> is no longer the case. unison2.32.52 should suffer from the same problem.

Uhh, thanks for tracking this down.

> The change done in unison 2.48 to overcome this looks pretty big... I'm
> not sure I'll be able/willing to provide a unison2.40.102 any more.

That would be a pity.

> Moreover, this package was created to provide compatibility with
> previous Debian releases, but another change in OCaml 4.02 makes it

Unfortunately I am even running old-stable, but till now had no
problems using 2.40 with the unison from old-stable. I will need
to look into that how I can keep that running.

Thanks a lot and all the best

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#787486: marked as done (ppl: FTBFS with swi-prolog 7.x)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2015 22:42:10 +
with message-id 
and subject line Bug#787486: fixed in ppl 1:1.1-7.1
has caused the Debian Bug report #787486,
regarding ppl: FTBFS with swi-prolog 7.x
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

In an up to date sid chroot, ppl compilation fails with

ppl_swiprolog.cc: At global scope:
ppl_swiprolog.cc:4565:1: error: invalid conversion from 'void*' to 
'pl_function_t {aka void (*)()}' [-fpermissive]
 };
 ^
ppl_swiprolog.cc:4565:1: error: invalid conversion from 'void*' to 
'pl_function_t {aka void (*)()}' [-fpermissive]
ppl_swiprolog.cc:4565:1: error: invalid conversion from 'void*' to 
'pl_function_t {aka void (*)()}' [-fpermissive]
ppl_swiprolog.cc:4565:1: error: invalid conversion from 'void

this error message is repeated about 2000 times.

I'm happy to provide the full build log if you can't duplicate this; it's more 
than 600K so I'll leave it out initially.

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQGcBAEBCAAGBQJVbUk+AAoJEPIClx2kp54spFcL/0KFGl2yawm3SAKreef6izcJ
DLoxkwU0WrxzLA+G7zKktP1wdUgihGhOJOycPBCsqUNJr0qS6e83XziXqREct7F8
xgXa2pJpYIEdiv53Yw2UibkbCSEIXiQhzrXPIUZNm+woxD3MWqw1EeyrkREpYu+j
5JICSD1cqFVQo43PgErdudl7NhUDnwde5nnmlebgFq9wfdcnqvdm7+MUGxC+L1Rr
GBm7XPNwf3V72PGFss+yGQzcn+V28+//TGBeOqWTGQj3QqfiF1Ci4ZiO7P/RohQ/
qY1qHFWi9WNKkj8QLWBpZL5/XJT3GNQqn/H5frLlFI77qiPsGITJB+o1dLkt1Jlw
hTh22YeGCckk9/bguDx6lxKb/Zm8C/k188LD+qu0YFm8v8AEpo7ijDO+BAwlHm0B
+Qlo3K7upA70lmcM71BNRM46FLihxL2pkxfYLR10iya8N4JGXAN7Sh09Kd6DlUGt
nMnSkkM5vLmLVemYYXY/g0KqllTyAIGWro7+l9c6FA==
=ZaRS
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: ppl
Source-Version: 1:1.1-7.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated ppl 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, 07 Dec 2015 22:04:41 +0100
Source: ppl
Binary: libppl13v5 libppl-dev ppl-dev libppl-c4
Architecture: source amd64
Version: 1:1.1-7.1
Distribution: unstable
Urgency: medium
Maintainer: Michael Tautschnig 
Changed-By: Matthias Klose 
Description:
 libppl-c4  - Parma Polyhedra Library (C interface)
 libppl-dev - Parma Polyhedra Library (development)
 libppl13v5 - Parma Polyhedra Library (runtime library)
 ppl-dev- Parma Polyhedra Library (development binaries)
Closes: 787486
Changes:
 ppl (1:1.1-7.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build failure with with swi-prolog 7.x (Roberto Bagnara).
 Closes: #787486.
Checksums-Sha1:
 c8eab79be3126db3d49c30d22b54f1888ac23f47 2004 ppl_1.1-7.1.dsc
 a63a4ab4b90b45081dc687518e574c0d3e39064b 12376 ppl_1.1-7.1.debian.tar.xz
 1f77712c16227ba390d58806711fa0828ddd5265 941574 libppl-c4_1.1-7.1_amd64.deb
 bfd327271c56b6256f8718b527ec21aa564ddfeb 2051962 libppl-dev_1.1-7.1_amd64.deb
 44f481b6ac8b2e9c97850459751dec46eb2a8022 600368 libppl13v5_1.1-7.1_amd64.deb
 91345f34daa897943af28b2ed8b56ac81bdaa6f4 201762 ppl-dev_1.1-7.1_amd64.deb
Checksums-Sha256:
 31707b8ce36ede9dba6e9bb9d492786a28cafc8bb664c3eb26cdaa006a51eb57 2004 
ppl_1.1-7.1.dsc
 d2b5f6cd376f96ad8d0fb305caf894dccc426dfd35b5e9eeba755a78a7bf5d6c 12376 
ppl_1.1-7.1.debian.tar.xz
 1166f4101986a7af169f8fd358c6f2b2acc9d4ed0fb6c68ed02f49e4aa38d4fe 941574 
libppl-c4_1.1-7.1_amd64.deb
 b3ae1a87a7c37f173a0c892a05375eac718d34017e961fef328f2df4d401cf37 2051962 
libppl-dev_1.1-7.1_amd64.deb
 4a7

Bug#804603: marked as done (courier: FTBFS: undefined reference to `SSLv3_method')

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2015 22:39:20 +
with message-id 
and subject line Bug#804603: fixed in courier 0.73.1-1.7
has caused the Debian Bug report #804603,
regarding courier: FTBFS: undefined reference to `SSLv3_method'
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.)


-- 
804603: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: courier
Version: 0.73.1-1.6
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build, as openssl have dropped sslv3 support:

./.libs/libcouriertls.a(libcouriertls.o): In function `tls_create':
/courier-0.73.1/libs/tcpd/libcouriertls.c:530: undefined reference to 
`SSLv3_method'
collect2: error: ld returned 1 exit status
Makefile:524: recipe for target 'couriertls' failed

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/courier.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: courier
Source-Version: 0.73.1-1.7

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

Debian distribution maintenance software
pp.
Dominic Hargreaves  (supplier of updated courier 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, 06 Dec 2015 21:32:12 +
Source: courier
Binary: courier-base courier-maildrop courier-mlm courier-mta courier-faxmail 
courier-webadmin sqwebmail courier-pcp courier-pop courier-imap courier-ldap 
courier-doc courier-ssl courier-mta-ssl courier-pop-ssl courier-imap-ssl
Architecture: source
Version: 0.73.1-1.7
Distribution: unstable
Urgency: medium
Maintainer: Stefan Hornburg (Racke) 
Changed-By: Dominic Hargreaves 
Description:
 courier-base - Courier mail server - base system
 courier-doc - Courier mail server - additional documentation
 courier-faxmail - Courier mail server - Fax<->mail gateway
 courier-imap - Courier mail server - IMAP server
 courier-imap-ssl - Courier mail server - IMAP over SSL
 courier-ldap - Courier mail server - LDAP support
 courier-maildrop - Courier mail server - mail delivery agent
 courier-mlm - Courier mail server - mailing list manager
 courier-mta - Courier mail server - ESMTP daemon
 courier-mta-ssl - Courier mail server - ESMTP over SSL
 courier-pcp - Courier mail server - PCP server
 courier-pop - Courier mail server - POP3 server
 courier-pop-ssl - Courier mail server - POP3 over SSL
 courier-ssl - Courier mail server - SSL/TLS Support
 courier-webadmin - Courier mail server - web-based administration frontend
 sqwebmail  - Courier mail server - webmail server
Closes: 804603
Changes:
 courier (0.73.1-1.7) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Don't assume availability of SSLv3 support in OpenSSL
 (Closes: #804603)
Checksums-Sha1:
 b8286822f76530f61cc000b0843aa6b1265e37fd 2942 courier_0.73.1-1.7.dsc
 78fd2f3b045e0996a472a11059bc34b488353cf0 111573 courier_0.73.1-1.7.diff.gz
Checksums-Sha256:
 8358313a5e9fd7946bed250b6a8cf286a17cb547e8bcd6b2af5c437214bd7616 2942 
courier_0.73.1-1.7.dsc
 ea2b3227f68e915dcc7589e1ba803307770f7bbd232e269529cfc321bd179f91 111573 
courier_0.73.1-1.7.diff.gz
Files:
 84620f6b3f80a1a9456218b83e609d05 2942 mail optional courier_0.73.1-1.7.dsc
 4aa3428d103ceb38b699a0c8da5a30f0 111573 mail optional 
courier_0.73.1-1.7.diff.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWZKvbAAoJEMAFfnFNaU+y7E0P/1tNs05KZsLdqYL5WVzhduRm
7vi7umeP1ukeT84zN+lJawzVsg2tp+6r1Qz0IIV3/lGMk2qOtSi3E6LFyiTNsbD4
HRixYhY2KXAin/sn0THuy2SGjqlryka6alTwgTkGCLGK485Cgc3AlQMZornReDJe
tZcUW6vy6w/J36AYXWFYYgDNCcBGTiBTy6CncUkkeDifC+YN45WHvemkJ1uVmGsq
5tHi1jhyU0kO8+Tch45WYhKxlAvt7gruVhWIezi4fZo2CR6jLfiaUGBEt1Ki8iMP
umS2KNbZ1eP62YZ2lWH7BrmQk7wadug/x115LmuMm6sMLLnLvwdtO62EVEivCFBc
1ixcgQ+ynvRZ7qJ3VQQXcp7hV+c

Bug#800574: Bug#807244: libegl1-nvidia: Programs crash due to elisian-unlock on skylake processor with nvidia driver 352.63-1 (experimental)

[Andreas Beckmann]

Dear libc maintainers,

we recently got a bug report regarding the TSX-NI / lock elision bug in
combination with the non-free nvidia driver (#807244). Since that is
supposed to be fixed with the libc in experimental (and now sid as
well), perhaps you could take a look why this still happens.
Several forum posts denote that "compiling glibc without
--enable-lock-elision" works around that issue.

A few ideas from my side, but since I don't have the hardware to test, I
cannot check anything:
* that specific CPU needs to be blacklisted / is incorrectly whitelisted
* nvidia utilizes a code path in libc that is not covered by the current
patch (and that code path is not used by any other application)
* nvidia does call something it shouldn't call directly ... thus
circumenting the runtime-disabling of the specific routines in libc6
* nvidia code does issue the problematic instructions itself (but the
backtrace points to libc, so this sounds unlikely)

Is there some way to check at runtime how lock elision is handled by
libc (on a concrete system)?

Andreas

On 2015-12-06 17:53, Jelle Haandrikman wrote:
> On a system with an Nvidia GTX 970, Intel Skylake i5-6600k running driver
> 352.63-1 (experimental) several programs crash due to TSX-NI / elision unlock.
> This affects sddm, unlocking kscreen, vlc and deleting files using dolphin.
> 
> Other people also have found this issue.
> http://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/nvidia-linux/825702-nvidia-s-latest-binary-driver-is-causing-problems-for-some-skylake-linux-users
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800574 #800574
> https://devtalk.nvidia.com/default/topic/893325/newest-and-beta-linux-driver-causing-segmentation-fault-core-dumped-on-all-skylake-platforms/
> 
> Bug #800574 suggest to disable elisian-unlock in glibc. Which is already
> incorporated in experimental. This does not alleviate the issue. See the 
> "steps
> to reproduce" below. The same bug suggests that the nvidia driver still has
> problems. I also run intel-microcode update, but that doesn't solve anything.

> Step to reproduce: gdb vlc
> output:
> (gdb) run
> Starting program: /usr/bin/vlc
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> VLC media player 2.2.1 Terry Pratchett (Weatherwax) (revision 
> 2.2.1-0-ga425c42)
> 
> Program received signal SIGSEGV, Segmentation fault.
> __lll_unlock_elision (lock=0x726d0d08, private=0)
> at ../sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
> 29  ../sysdeps/unix/sysv/linux/x86/elision-unlock.c: No such file or
> directory.
> (gdb) bt
> #0  __lll_unlock_elision (lock=0x726d0d08, private=0)
> at ../sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
> #1  0x7247f26c in ?? () from /usr/lib/x86_64-linux-gnu/libEGL.so.1
> #2  0x7240fa22 in ?? () from /usr/lib/x86_64-linux-gnu/libEGL.so.1
> #3  0x7fffd960 in ?? ()
> #4  0x72493ea1 in ?? () from /usr/lib/x86_64-linux-gnu/libEGL.so.1
> #5  0x7fffd960 in ?? ()
> #6  0x77def59e in _dl_close_worker (map=,
> force=)
> at dl-close.c:291
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
> 
> /usr/lib/x86_64-linux-gnu/libEGL.so.1 -> /usr/lib/x86_64-linux-
> gnu/nvidia/libEGL.so.1
> 
> "dmesg|grep pthread" result:
> breetai@mainbak:~$ dmesg |grep pthread
> [73330.105569] traps: vlc[16815] general protection ip:7f47ac388950
> sp:7ffe3908ad98 error:0 in libpthread-2.22.so[7f47ac376000+18000]
> [78860.282876] traps: dolphin[18294] general protection ip:7fc3b0c1b950
> sp:7ffd0a0828d8 error:0 in libpthread-2.22.so[7fc3b0c09000+18000]
> [90812.515421] traps: krunner[20723] general protection ip:7f930fa19950
> sp:7ffc9b5cd988 error:0 in libpthread-2.22.so[7f930fa07000+18000]
> [90826.164341] traps: akonadi_migrati[21161] general protection 
> ip:7f33b7e39950
> sp:7fff9d61bef8 error:0 in libpthread-2.22.so[7f33b7e27000+18000]
> [92621.782318] traps: vlc[21962] general protection ip:7f4241467950
> sp:7ffd8fa98f68 error:0 in libpthread-2.22.so[7f4241455000+18000]
> breetai@mainbak:~$
> 
> 
> installed packages:
> System runs testing.
> 
> libc6:amd64 2.22-0experimental0 from experimental
> nvidia-driver   352.63-1from experimental
> intel-microcode 3.20151106.1from testing
> vlc 2.2.1-5+b1  from testing

Bug#807171: marked as done (libmemcached fails to build its manual pages)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2015 22:04:11 +
with message-id 
and subject line Bug#807171: fixed in libmemcached 1.0.18-4.1
has caused the Debian Bug report #807171,
regarding libmemcached fails to build its manual pages
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.)


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

Package: src:libmemcached
Version: 1.0.18-4
Severity: serious
Tags: sid stretch

libmemcached fails to build in unstable, trying to build the manual pages:

make -j5  man
make[3]: Entering directory '/home/packages/tmp/libmemcached-1.0.18'
make[3]: warning: -jN forced in submake: disabling jobserver mode.
WARNING: master file /home/packages/tmp/libmemcached-1.0.18/docs/index.rst not 
found

Exception occurred:
   File "/usr/lib/python2.7/dist-packages/sphinx/environment.py", line 1272, in 
get_doctree

 f = open(doctree_filename, 'rb')
IOError: [Errno 2] No such file or directory: 
u'/home/packages/tmp/libmemcached-1.0.18/man/.doctrees/hashkit_create.doctree'
The full traceback has been saved in /tmp/sphinx-err-aDYVFd.log, if you want to 
report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!

Makefile:10361: recipe for target 'man' failed
make[3]: *** [man] Error 1
make[3]: Leaving directory '/home/packages/tmp/libmemcached-1.0.18'
Makefile:10376: recipe for target 'man/memaslap.1' failed
make[2]: *** [man/memaslap.1] Error 2
make[2]: Leaving directory '/home/packages/tmp/libmemcached-1.0.18'
Makefile:3712: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/packages/tmp/libmemcached-1.0.18'
dh_auto_build: make -j1 returned exit code 2
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2

# Sphinx version: 1.3.1
# Python version: 2.7.10 (CPython)
# Docutils version: 0.12 release
# Jinja2 version: 2.8
# Last messages:
#   not yet created
#   building [mo]: targets for 0 po files that are out of date
#   building [man]: all manpages
#   updating environment:
#   0 added, 0 changed, 0 removed
#   WARNING: master file /home/packages/tmp/libmemcached-1.0.18/docs/index.rst not found
#   looking for now-outdated files...
#   none found
#   writing...
#   hashkit_clone.3 {
# Loaded extensions:
#   alabaster (0.7.6) from /usr/lib/python2.7/dist-packages/alabaster/__init__.pyc
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx/cmdline.py", line 240, in main
app.build(opts.force_all, filenames)
  File "/usr/lib/python2.7/dist-packages/sphinx/application.py", line 264, in build
self.builder.build_update()
  File "/usr/lib/python2.7/dist-packages/sphinx/builders/__init__.py", line 240, in build_update
self.build(['__all__'], to_build)
  File "/usr/lib/python2.7/dist-packages/sphinx/builders/__init__.py", line 316, in build
self.write(docnames, list(updated_docnames), method)
  File "/usr/lib/python2.7/dist-packages/sphinx/builders/manpage.py", line 70, in write
tree = self.env.get_doctree(docname)
  File "/usr/lib/python2.7/dist-packages/sphinx/environment.py", line 1272, in get_doctree
f = open(doctree_filename, 'rb')
IOError: [Errno 2] No such file or directory: u'/home/packages/tmp/libmemcached-1.0.18/man/.doctrees/hashkit_create.doctree'

--- End Message ---
--- Begin Message ---
Source: libmemcached
Source-Version: 1.0.18-4.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libmemcached 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, 07 Dec 2015 21:37:57 +0100
Source: libmemcached
Binary: libmemcached11 libmemcached-dev libmemcached-dbg libmemcachedutil2 
libhashkit2 libhashkit-dev libmemcached-tools
Architecture: source amd64
Version: 

Bug#807350: marked as done (django-restricted-resource: FTBFS with Django 1.9: django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2015 21:51:33 +
with message-id 
and subject line Bug#807350: fixed in django-restricted-resource 2015.11-2
has caused the Debian Bug report #807350,
regarding django-restricted-resource: FTBFS with Django 1.9: 
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
to be marked as done.

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

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


-- 
807350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-restricted-resource
Version: 2015.11-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,

django-restricted-resource fails to build from source in unstable/amd64:

  [..]

  self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in
run_command
  cmd_obj.run()
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py",
line 157, in run
  self.with_project_on_sys_path(self.run_tests)
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py",
line 138, in with_project_on_sys_path
  func()
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py",
line 178, in run_tests
  testRunner=self._resolve_as_ep(self.test_runner),
File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
  self.parseArgs(argv)
File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
  self.createTests()
File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
  self.module)
File "/usr/lib/python2.7/unittest/loader.py", line 130, in
loadTestsFromNames
  suites = [self.loadTestsFromName(name, module) for name in names]
File "/usr/lib/python2.7/unittest/loader.py", line 115, in
loadTestsFromName
  test = obj()
File

"/home/lamby/temp/cdt.20151207215919.KS07bteFb8/django-restricted-resource-2015.11/django_restricted_resource/test_project/tests.py",
line 24, in run_tests
  return
  run_tests_for("django_restricted_resource.test_project.settings")
File "/usr/lib/python2.7/dist-packages/django_testproject/tests.py",
line 58, in run_tests_for
  failures = runner(test_labels)
File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line
532, in run_tests
  old_config = self.setup_databases()
File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line
482, in setup_databases
  self.parallel, **kwargs
File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line
726, in setup_databases
  serialize=connection.settings_dict.get("TEST",
  {}).get("SERIALIZE", True),
File
"/usr/lib/python2.7/dist-packages/django/db/backends/base/creation.py",
line 70, in create_test_db
  run_syncdb=True,
File
"/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 91, in call_command
  app_name = get_commands()[name]
File "/usr/lib/python2.7/dist-packages/django/utils/lru_cache.py",
line 100, in wrapper
  result = user_function(*args, **kwds)
File
"/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 71, in get_commands
  for app_config in reversed(list(apps.get_app_configs())):
File "/usr/lib/python2.7/dist-packages/django/apps/registry.py",
line 137, in get_app_configs
  self.check_apps_ready()
File "/usr/lib/python2.7/dist-packages/django/apps/registry.py",
line 124, in check_apps_ready
  raise AppRegistryNotReady("Apps aren't loaded yet.")
  django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
  debian/rules:8: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory
  
'/home/lamby/temp/cdt.20151207215919.KS07bteFb8/django-restricted-resource-2015.11'
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


django-restricted-resource.2015.11-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: django-restricted-resource
Source-Version: 2015.11-2

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

A summary of t

Bug#672391: marked as done (Please consider chaging dependency of libsigc++1.2 to 2.0)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2015 21:50:35 +
with message-id 
and subject line Bug#672391: fixed in asc 2.6.1.0-1
has caused the Debian Bug report #672391,
regarding Please consider chaging dependency of libsigc++1.2 to 2.0
to be marked as done.

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

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


-- 
672391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asc
Version: 2.4.0.0-2
Severity: normal

Hello,

I would like to ask you to consider changing the build-depends from
libsigc++-1.2-dev to libsigc++-2.0-dev.

The version in 1.2 is very old, unsupported (last release on 2005,
more than 7 years ago) and it should probably be removed from Debian
when possible.

There are only 3 packages in the whole archive depending on it (versus
150+ for 2.0), and this is one of them.

Regards.


--- End Message ---
--- Begin Message ---
Source: asc
Source-Version: 2.6.1.0-1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated asc 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: Mon, 07 Dec 2015 18:20:59 +0100
Source: asc
Binary: asc asc-data
Architecture: source
Version: 2.6.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 asc- turn-based strategy game
 asc-data   - data files for the Advanced Strategic Command game
Closes: 672391
Changes:
 asc (2.6.1.0-1) unstable; urgency=medium
 .
   [ Moritz Muehlenhoff ]
   * Remove myself from uploaders.
 .
   [ Markus Koschany ]
   * Imported Upstream version 2.6.1.0.
   * Switch to libsigc++-2.0-dev. (Closes: #672391)
   * Add get-orig-source target.
   * Update my e-mail address.
   * Drop spelling-errors.patch. Merged upstream.
   * Declare compliance with Debian Policy 3.9.6.
   * d/rules: Remove export DEB_BUILD_OPTIONS = nocheck
   * Override dh_auto_test to prevent a FTBFS due to non-functional tests.
   * Add reproducible-build.patch and make the build reproducible.
   * Move the package to Git.
   * Add clean file and ensure that the game can be built twice in a row.
Checksums-Sha1:
 7c4db9e27855abe560bac53c1d88b5bedd4155b2 2427 asc_2.6.1.0-1.dsc
 3731e8016143d3c83364f67f4ac7d8e7491b7a50 42569531 asc_2.6.1.0.orig.tar.bz2
 bcf93e0976c4aff47bb76a4af03e16f5e7494106 20096 asc_2.6.1.0-1.debian.tar.xz
Checksums-Sha256:
 0429b79e89820a4d0859e40ab2b5a383bdada76d92d97cdd1a7aad11ae353aaf 2427 
asc_2.6.1.0-1.dsc
 9a1e58e73ba8fdf5d5ac85cdb66804bf688dce2940a8a9c26796de6b6d4f8ddb 42569531 
asc_2.6.1.0.orig.tar.bz2
 4772180aa89ef0353e85bd6a10739bdfdfb0d7935c1574b9bae447bc43b70e5a 20096 
asc_2.6.1.0-1.debian.tar.xz
Files:
 080e359a197cf94923e0528dd7b78bf5 2427 games optional asc_2.6.1.0-1.dsc
 b8668c378e730e982458d5c082e7e0ca 42569531 games optional 
asc_2.6.1.0.orig.tar.bz2
 99202f08970d2e81e71a33ad6f760e5e 20096 games optional 
asc_2.6.1.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWZe0WXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRBQ0YzRDA4OEVGMzJFREVGNkExQTgzNUZE
OUFEMTRCOTUxM0I1MUU0AAoJENmtFLlRO1Hkc5QQAKcWCce53NxQM/yRQBv4LcM3
bGQsE2NY+VlJGTyRie0CGMQInTbMkp++W3qHUXxdovUZ10tDJo1ii+p0/+KuKtiH
dNC5WbT6k5MyPuJFU4v2HTKW+sELQh9PbNcOumcMf6EGxGdDFWMWT3FV217+iib8
xCz8e7W6ryiy5JxpJ3PAVD+SmFASQV3UfC5uBpDpnKRp2NReBZt4s0JlqHdyjhyl
u7TB+h5En/RwxvEJUh8ACvX3q1mEWtoeRYd4VCK2jH7+0oMTj6iPD0hbcjJTul1I
RhP4QHNcKhzhFQxYan4WqSVBz8skXz/2bvY+iVDFeHnvVDuKJ579zk8Bzz/FGrde
aMOJVBuwUEZLy36MCIY7KUkB3cpPYAZRyGRmaAfu+VHvdQySE+EVuOJY5FA0nC5e
pSLwvTtzsnBKueYkN7hbDtF45Wk6TSTjOmMZg0o5BR5/z4AP4BYpBl4z3b8ardeH
2vLGxzJ1bSrmbcD1xxdogHbBMQek11EEmQXkVnJ4trfyX8lCbBkwUf972CYjKrJc
PXtOWN0W51p48zifxuAUBRig2i/8Yi/4200Zkz34eKEJ37D3nu1qQVnNeM5lPFHg
0n9fozqZzOGAzeMYqbJzxei99pBJNseDhMKzyTrU5f8EYRulnXW6UUJKSmuNkHJX
kXi/leuKS3TchSK/hIMG
=0/eK
-END PGP SIGNATURE End Message ---

Bug#791858: marked as done (keepassx: CVE-2015-8378: canceling export operation creates cleartext copy of all of the user's KeePassX password database entries)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2015 21:47:06 +
with message-id 
and subject line Bug#791858: fixed in keepassx 0.4.3+dfsg-0.1+deb8u1
has caused the Debian Bug report #791858,
regarding keepassx: CVE-2015-8378: canceling export operation creates cleartext 
copy of all of the user's KeePassX password database entries
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.)


-- 
791858: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: keepassx
Version: 0.4.3+dfsg-0.1
Severity: important
Tags: newcomer

Dear Maintainer,

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

   * What led up to the situation?
Klick on file/export_to/KeepassX XML-File
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Test and check the functions on keepass. This will be save an invisivle .xml
file in your home directory.
   * What was the outcome of this action?
The Passwortlist is accessible in plaintext

   * What outcome did you expect instead?
This effekt is also in my arch / manjaro-linux-package of keepassx

Thanks for help Hopefully! :-)



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

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

Versions of packages keepassx depends on:
ii  libc6   2.19-18
ii  libgcc1 1:4.9.2-10
ii  libqt4-xml  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtcore4  4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui4   4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libstdc++6  4.9.2-10
ii  libx11-62:1.6.2-3
ii  libxtst62:1.2.2-1+b1

keepassx recommends no packages.

keepassx suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: keepassx
Source-Version: 0.4.3+dfsg-0.1+deb8u1

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated keepassx 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: SHA1

Format: 1.8
Date: Sat, 05 Dec 2015 13:15:11 -0500
Source: keepassx
Binary: keepassx
Architecture: source amd64
Version: 0.4.3+dfsg-0.1+deb8u1
Distribution: jessie
Urgency: medium
Maintainer: Reinhard Tartler 
Changed-By: Reinhard Tartler 
Description:
 keepassx   - Cross Platform Password Manager
Closes: 791858
Changes:
 keepassx (0.4.3+dfsg-0.1+deb8u1) jessie; urgency=medium
 .
   * Add patch that fixes CVE-2015-8378 (Closes: #791858)
Checksums-Sha1:
 136e0cbda11f93c331285e51a32c3377ea6fef84 1825 
keepassx_0.4.3+dfsg-0.1+deb8u1.dsc
 0425698eec90dc967b322662e53f0c11104040cd 12532 
keepassx_0.4.3+dfsg-0.1+deb8u1.debian.tar.xz
 fdd8eeb6c4a8187fe303e5d30e0c2111c9831cf8 749354 
keepassx_0.4.3+dfsg-0.1+deb8u1_amd64.deb
Checksums-Sha256:
 b4e45bf7c0073aa8f63d836f6609ec6b1bdad8f4b5fa7e316e371491b2d2262c 1825 
keepassx_0.4.3+dfsg-0.1+deb8u1.dsc
 2ed1be589b8ed76586b87cfc0de8835e088bbd5466739a3df1784c821d17c9f5 12532 
keepassx_0.4.3+dfsg-0.1+deb8u1.debian.tar.xz
 d6037acc1b3e4b134cd2707ab7fec85c24b01f68b0655e06f9fc9907a887447b 749354 
keepassx_0.4.3+dfsg-0.1+deb8u1_amd64.deb
Files:
 4efaf78ea4223104b79559878ee19779 1825 utils optional 
keepassx_0.4.3+dfsg-0.1+deb8u1.dsc
 0f6e9240fcef9b7ec478e7b979f695fd 12532 utils optional 
keepassx_0.4.3+dfsg-0.1+deb8u1.debian.tar.xz
 dbb363054bf18cdbc0439a3c07c6e204 749354 utils optional 
keepassx_0.4.3+dfsg-0.1+deb8u1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Debian Powered!

iQGcBAEBAgAGBQJWZNFnAAoJEIuAbIZKeKRFAswMALBoW4g2rH3eJYD6MYkZPuH+
5f1SxOjwVOqHFapWDLb1XtmiegyrzAaqOZtJsmCq8vDqPyydoK04ylfej1ffalCp
NMECG2cYjCGAE4QGB5AD+Jz/TefK+hHaTpgts903FPq8G/+zIsJRp4N1A1HkS+a0
wcPuB6gIL9/iMshRLn4h+TckjmB13ouC55CX7Ifw2zdfMlaDtg/i1KprR2IhDnwT
VyHPpHVFv+4NmzjL0K72lChzknTIKPxVmbpyOlA93l18

Bug#804499: ruby-gsl: GSL transition requires rebuild

[Sebastiaan Couwenberg]

On Wed, 18 Nov 2015 12:16:24 +0100 Balint Reczey  wrote:
> I have prepared the fix in git [2] but tamuanova [3] needs to be transitioned
> first since it is a build dependency and can't be installed together with
> libgsl-dev > 2.0.

Thanks to Anton Gladky tamuanova has been updated for GSL 2, that
removes it as a blocker for this issue.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#802579: binutils changed ld.bfd / ld.gold files and symlinks

[Sven Joachim]

On 2015-12-07 11:39 +0800, YunQiang Su wrote:

> On Sat, 14 Nov 2015 02:20:40 +0100 Matthias Klose  wrote:
>> Control: severity -1 serious
>>
>> binutils built from the 2.26 branch is now in unstable.
>>
>>
>
> I uploaded this packages with the attached patch to 3-days delay.

Thanks for taking care of hardening-wrapper, but I am afraid your
changes are not quite correct.

> diff -Nru hardening-wrapper-2.7/debian/hardening-wrapper.links 
> hardening-wrapper-2.8+nmu1/debian/hardening-wrapper.links
> --- hardening-wrapper-2.7/debian/hardening-wrapper.links  2013-09-14 
> 03:55:36.0 +0800
> +++ hardening-wrapper-2.8+nmu1/debian/hardening-wrapper.links 2015-12-07 
> 11:33:14.0 +0800
> @@ -1,12 +1,13 @@
>  #!/bin/sh
>  # programatically build links (change debian/h-w.{preinst,postrm} too)
> -for ver in 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9
> +eval $(dpkg-architecture -a)
> +for ver in 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 5
>  do
>  echo usr/bin/hardened-cc usr/bin/gcc-$ver
>  echo usr/bin/hardened-c++ usr/bin/g++-$ver
>  done
>  cat < -usr/bin/hardened-ld usr/bin/ld.bfd
> -usr/bin/hardened-ld usr/bin/ld.gold
> +usr/bin/hardened-ld usr/bin/${DEB_BUILD_MULTIARCH}-ld.bfd
> +usr/bin/hardened-ld usr/bin/${DEB_BUILD_MULTIARCH}-ld.gold

DEB_BUILD_MULTIARCH is not the right variable, you want
DEB_HOST_GNU_TYPE instead - except on {,kfreebsd-,hurd-}i386, where
binutils is configured for i686{-linux,-kfreebsd,}-gnu rather than
i586{-linux,-kfreebsd,}-gnu currently reported by dpkg-architecture.

> diff -Nru hardening-wrapper-2.7/debian/hardening-wrapper.postrm 
> hardening-wrapper-2.8+nmu1/debian/hardening-wrapper.postrm
> --- hardening-wrapper-2.7/debian/hardening-wrapper.postrm 2013-09-14 
> 03:55:52.0 +0800
> +++ hardening-wrapper-2.8+nmu1/debian/hardening-wrapper.postrm
> 2015-12-07 10:48:44.0 +0800
> @@ -6,17 +6,19 @@
>   --rename --remove /usr/bin/"$1" || true
>  }
>  
> +eval $(dpkg-architecture -a)

You can't really use dpkg-architecture in maintainer scripts, since
hardening-wrapper does not depend on dpkg-dev.  Even if it were to do
that, the result is not necessarily correct, e.g. hardening-wrapper
could have a different architecture than dpkg.

Cheers,
   Sven

Bug#805222: [Pkg-php-pecl] Bug#805222: php-apcu: FTBFS: PHP Fatal error: Call to a member function getFilelist() on null

[Mathieu Parent (Debian)]

2015-12-07 17:21 GMT+01:00 Ondřej Surý :
> Control: reassign -1 php-pear
> Control: found -1 php-pear/5.6.16+dfsg-1
> Control: affects -1 php5-apcu
>
> Hi,
>
> thank you for the report, after some debugging it seems this is a
> generic error in PEAR instead of bug just in the php-apcu. This should
> not affect no users, but it probably broke all PHP extensions, since it
> stops honoring packagingroot after calling PEAR_Registry->setConfig()
>
> I have a fix ready and PHP building, and I am ccing Fedora and SuSE
> maintainers.
>
> Mathieu, this also applies to your standalone src:php-pear:

OK thanks.

> diff --git a/PEAR/Command/Install.php b/PEAR/Command/Install.php
> index 9d572ed..3b1fec9 100644
> --- a/PEAR/Command/Install.php
> +++ b/PEAR/Command/Install.php
> @@ -848,7 +848,7 @@ Run post-installation scripts in package ,
> if any exist.
>  $pkg = &$instreg->getPackage($param->getPackage(),
>  $param->getChannel());
>  // $pkg may be NULL if install is a 'fake' install via
>  --packagingroot
>  if (is_object($pkg)) {
> -$pkg->setConfig($this->config);
> +$pkg->setConfig($this->config, false);
>  if ($list = $pkg->listPostinstallScripts()) {
>  $pn =
>  $reg->parsedPackageNameToString(array('channel' =>
> $param->getChannel(), 'package' =>
> $param->getPackage()), true);
>
>
> This fixes the issue right now, but it should be probably reported
> upstream to have a correct fix (since this might break other stuff :)),
> but my PEAR account doesn't work right now, so it might take me a while
> to report this to upstream.

You can propose a PR instead: https://github.com/pear/pear-core/pulls

Cheers
-- 
Mathieu Parent

Bug#807355: python-django-compressor: FTBFS: ImportError: cannot import name unittest

[Chris Lamb]

Source: python-django-compressor
Version: 1.5-3
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,

python-django-compressor fails to build from source in unstable/amd64:

  [..]  
  
  ==
  ERROR: compressor.tests.test_filters
  (unittest.loader.ModuleImportFailure)
  --
  ImportError: Failed to import test module:
  compressor.tests.test_filters
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in
_find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in
_get_module_from_name
  __import__(name)
File

"/home/lamby/temp/cdt.20151207220219.jZR1UtVc3q/python-django-compressor-1.5/compressor/tests/test_filters.py",
line 10, in 
  from django.utils import unittest
  ImportError: cannot import name unittest
  
  
  --
  Ran 98 tests in 0.200s
  
  FAILED (errors=56)
  Creating test database for alias 'default'...
  Destroying test database for alias 'default'...
  debian/rules:19: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory
  '/home/lamby/temp/cdt.20151207220219.jZR1UtVc3q/python-django-compressor-1.5'
  debian/rules:11: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-django-compressor.1.5-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807351: python-debian: FTBFS: SystemError: E:Unable to parse package file (1)

[Chris Lamb]

Source: python-debian
Version: 0.1.27
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,

python-debian fails to build from source in unstable/amd64:

  [..]
  test_reverse (test_debtags.TestDebtags) ... ok
  
  ==
  ERROR: apt_pkg does not support comments within multiline fields
  --
  Traceback (most recent call last):
File

"/home/lamby/temp/cdt.20151207220143.ZwB98jWQ6C/python-debian-0.1.27/tests/test_deb822.py",
line 922, in test_iter_paragraphs_comments_use_apt_pkg
  fh, use_apt_pkg=True))
File "../lib/debian/deb822.py", line 376, in iter_paragraphs
  for section in parser:
  SystemError: E:Unable to parse package file  (1)
  
  --
  Ran 166 tests in 0.371s
  
  FAILED (errors=1)
  debian/rules:28: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory
  '/home/lamby/temp/cdt.20151207220143.ZwB98jWQ6C/python-debian-0.1.27'
  debian/rules:13: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-debian.0.1.27.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807350: django-restricted-resource: FTBFS with Django 1.9: django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

[Chris Lamb]

Source: django-restricted-resource
Version: 2015.11-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,

django-restricted-resource fails to build from source in unstable/amd64:

  [..]

  self.run_command(cmd)
File "/usr/lib/python2.7/distutils/dist.py", line 972, in
run_command
  cmd_obj.run()
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py",
line 157, in run
  self.with_project_on_sys_path(self.run_tests)
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py",
line 138, in with_project_on_sys_path
  func()
File "/usr/lib/python2.7/dist-packages/setuptools/command/test.py",
line 178, in run_tests
  testRunner=self._resolve_as_ep(self.test_runner),
File "/usr/lib/python2.7/unittest/main.py", line 94, in __init__
  self.parseArgs(argv)
File "/usr/lib/python2.7/unittest/main.py", line 149, in parseArgs
  self.createTests()
File "/usr/lib/python2.7/unittest/main.py", line 158, in createTests
  self.module)
File "/usr/lib/python2.7/unittest/loader.py", line 130, in
loadTestsFromNames
  suites = [self.loadTestsFromName(name, module) for name in names]
File "/usr/lib/python2.7/unittest/loader.py", line 115, in
loadTestsFromName
  test = obj()
File

"/home/lamby/temp/cdt.20151207215919.KS07bteFb8/django-restricted-resource-2015.11/django_restricted_resource/test_project/tests.py",
line 24, in run_tests
  return
  run_tests_for("django_restricted_resource.test_project.settings")
File "/usr/lib/python2.7/dist-packages/django_testproject/tests.py",
line 58, in run_tests_for
  failures = runner(test_labels)
File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line
532, in run_tests
  old_config = self.setup_databases()
File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line
482, in setup_databases
  self.parallel, **kwargs
File "/usr/lib/python2.7/dist-packages/django/test/runner.py", line
726, in setup_databases
  serialize=connection.settings_dict.get("TEST",
  {}).get("SERIALIZE", True),
File
"/usr/lib/python2.7/dist-packages/django/db/backends/base/creation.py",
line 70, in create_test_db
  run_syncdb=True,
File
"/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 91, in call_command
  app_name = get_commands()[name]
File "/usr/lib/python2.7/dist-packages/django/utils/lru_cache.py",
line 100, in wrapper
  result = user_function(*args, **kwds)
File
"/usr/lib/python2.7/dist-packages/django/core/management/__init__.py",
line 71, in get_commands
  for app_config in reversed(list(apps.get_app_configs())):
File "/usr/lib/python2.7/dist-packages/django/apps/registry.py",
line 137, in get_app_configs
  self.check_apps_ready()
File "/usr/lib/python2.7/dist-packages/django/apps/registry.py",
line 124, in check_apps_ready
  raise AppRegistryNotReady("Apps aren't loaded yet.")
  django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
  debian/rules:8: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory
  
'/home/lamby/temp/cdt.20151207215919.KS07bteFb8/django-restricted-resource-2015.11'
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


django-restricted-resource.2015.11-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807347: txaws: FTBFS: twisted.trial.unittest.FailTest: '500' != 500

[Chris Lamb]

Source: txaws
Version: 0.2.3-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,

txaws fails to build from source in unstable/amd64:

  [..]
  
  txaws.ec2.tests.test_client.QueryTestCase.test_submit_non_EC2_400
  
===
  [FAIL]
  Traceback (most recent call last):
File

"/home/lamby/temp/cdt.20151207215711.OLxXnJQQOq/txaws-0.2.3/txaws/tests/test_exception.py",
line 18, in test_creation
  self.assertEquals(error.status, 500)
File "/usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py",
line 437, in assertEqual
  super(_Assertions, self).assertEqual(first, second, msg)
File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
  assertion_func(first, second, msg=msg)
File "/usr/lib/python2.7/unittest/case.py", line 506, in
_baseAssertEqual
  raise self.failureException(msg)
  twisted.trial.unittest.FailTest: '500' != 500
  
  txaws.tests.test_exception.AWSErrorTestCase.test_creation
  
---
  Ran 437 tests in 0.633s
  
  FAILED (skips=56, failures=9, successes=372)
  debian/rules:14: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory
  '/home/lamby/temp/cdt.20151207215711.OLxXnJQQOq/txaws-0.2.3'
  debian/rules:6: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


txaws.0.2.3-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807349: dwww: FTBFS: error: expected identifier or '(' before '__extension__'

[Chris Lamb]

Source: dwww
Version: 1.12.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,

dwww fails to build from source in unstable/amd64:

  [..]

  gcc -c -D_FORTIFY_SOURCE=2 -DVERSION='"1.12.1"' -g -O2
  -fstack-protector-strong -Wformat -Werror=format-security -Wall
  -Wextra -Wstrict-prototypes -Wmissing-prototypes -Werror -g  -o
  _build/dwww-cache.o dwww-cache.c
  In file included from /usr/include/string.h:634:0,
   from dwww-cache.c:30:
  /usr/include/publib/strutil.h:67:7: error: expected identifier or '('
  before '__extension__'
   char *strndup(const char *, size_t);
 ^
  Makefile:25: recipe for target '_build/dwww-cache.o' failed
  make[2]: *** [_build/dwww-cache.o] Error 1
  common.mk:190: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory
  '/home/lamby/temp/cdt.20151207215750.Wr0BRL256Q/dwww-1.12.1'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


dwww.1.12.1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807346: python-django-openstack-auth: FTBFS:

[Chris Lamb]

Source: python-django-openstack-auth
Version: 2.0.0-3
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,

python-django-openstack-auth fails to build from source in
unstable/amd64:

  [..]
  
  ==
  ERROR: test_switch_with_next (tests.OpenStackAuthTestsV3)
  --
  Traceback (most recent call last):
File

"/home/lamby/temp/cdt.20151207215322.HOuGTibadH/python-django-openstack-auth-2.0.0/openstack_auth/tests/tests.py",
line 732, in test_switch_with_next
  self.test_switch(next='/next_url')
File

"/home/lamby/temp/cdt.20151207215322.HOuGTibadH/python-django-openstack-auth-2.0.0/openstack_auth/tests/tests.py",
line 720, in test_switch
  response = self.client.get(url, form_data)
File "/usr/lib/python2.7/dist-packages/django/test/client.py", line
503, in get
  **extra)
File "/usr/lib/python2.7/dist-packages/django/test/client.py", line
304, in get
  return self.generic('GET', path, secure=secure, **r)
File "/usr/lib/python2.7/dist-packages/django/test/client.py", line
380, in generic
  return self.request(**r)
File "/usr/lib/python2.7/dist-packages/django/test/client.py", line
467, in request
  six.reraise(*exc_info)
File
"/usr/lib/python2.7/dist-packages/django/core/handlers/base.py",
line 149, in get_response
  response = self.process_exception_by_middleware(e, request)
File
"/usr/lib/python2.7/dist-packages/django/core/handlers/base.py",
line 147, in get_response
  response = wrapped_callback(request, *callback_args,
  **callback_kwargs)
File
"/usr/lib/python2.7/dist-packages/django/contrib/auth/decorators.py",
line 23, in _wrapped_view
  return view_func(request, *args, **kwargs)
File

"/home/lamby/temp/cdt.20151207215322.HOuGTibadH/python-django-openstack-auth-2.0.0/openstack_auth/views.py",
line 229, in switch
  redirect_to = request.REQUEST.get(redirect_field_name, '')
  AttributeError: 'WSGIRequest' object has no attribute 'REQUEST'
  
  --
  Ran 44 tests in 0.466s
  
  FAILED (errors=10)
  Creating test database for alias 'default'...
  Destroying test database for alias 'default'...
  debian/rules:26: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 10
  make[1]: Leaving directory
  
'/home/lamby/temp/cdt.20151207215322.HOuGTibadH/python-django-openstack-auth-2.0.0'
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


python-django-openstack-auth.2.0.0-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#807244: libegl1-nvidia: Programs crash due to elisian-unlock on skylake processor with nvidia driver 352.63-1 (experimental)

[Jelle Haandrikman]

Hi,

On 2015-12-07 19:46, Luca Boccassi wrote:


Hi Jelle,

Thanks for the report.

Unfortunately there is nothing we can do about this, Nvidia needs to 
fix

it, so we can only wait. :-(

Kind regards,
Luca Boccassi

Hi Luca

Thank you for the response.

I think it's better to have registered bug with a good description and 
make the problem public. That way every distro can point to Nvidia to 
say they have work to do. Also people with the same problem don't have 
to puzzle for themselves and suffer quietly. The problem is now properly 
documented and when Nvidia finally fixes this, we can close it.


best regards,
Jelle

Bug#807244: libegl1-nvidia: Programs crash due to elisian-unlock on skylake processor with nvidia driver 352.63-1 (experimental)

[Luca Boccassi]

On Sun, 2015-12-06 at 17:53 +0100, Jelle Haandrikman wrote:
> Package: libegl1-nvidia
> Version: 352.63-1
> Severity: critical
> Justification: breaks unrelated software
> 
> Dear Maintainer,
> 
> On a system with an Nvidia GTX 970, Intel Skylake i5-6600k running driver
> 352.63-1 (experimental) several programs crash due to TSX-NI / elision unlock.
> This affects sddm, unlocking kscreen, vlc and deleting files using dolphin.
> 
> Other people also have found this issue.
> http://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/nvidia-linux/825702-nvidia-s-latest-binary-driver-is-causing-problems-for-some-skylake-linux-users
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800574 #800574
> https://devtalk.nvidia.com/default/topic/893325/newest-and-beta-linux-driver-causing-segmentation-fault-core-dumped-on-all-skylake-platforms/
> 
> Bug #800574 suggest to disable elisian-unlock in glibc. Which is already
> incorporated in experimental. This does not alleviate the issue. See the 
> "steps
> to reproduce" below. The same bug suggests that the nvidia driver still has
> problems. I also run intel-microcode update, but that doesn't solve anything.
> 
> The driver in testing and unstable (nvidia v. 340) doesn't work with the 
> nvidia
> GTX 970, so I need to run the experimental version.

Hi Jelle,

Thanks for the report.

Unfortunately there is nothing we can do about this, Nvidia needs to fix
it, so we can only wait. :-(

Kind regards,
Luca Boccassi


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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 807244 upstream
Bug #807244 [libegl1-nvidia] libegl1-nvidia: Programs crash due to 
elisian-unlock on skylake processor with nvidia driver 352.63-1 (experimental)
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: adjust severity

[Debian Bug Tracking System]

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

> severity 807040 important
Bug #807040 [xserver-xorg-video-nouveau] general: System hangs and then 
restarts (kernel panic)
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#805222: marked as done (php-apcu: FTBFS: PHP Fatal error: Call to a member function getFilelist() on null)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2015 18:29:15 +
with message-id 
and subject line Bug#805222: fixed in php5 5.6.16+dfsg-2
has caused the Debian Bug report #805222,
regarding php-apcu: FTBFS: PHP Fatal error:  Call to a member function 
getFilelist() on null
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.)


-- 
805222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-apcu
Version: 4.0.7-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

/usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
doc_dir=/usr/share/doc/php5-apcu -d test_dir=/usr/share/php/tests install 
--offline --nodeps -P /php-apcu-4.0.7/debian/php5-apcu --nobuild 
./apcu-4.0.7/package.xml
PHP Fatal error:  Call to a member function getFilelist() on null in 
/usr/share/php/PEAR/Command/Install.php on line 747
dh_auto_install: /usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
doc_dir=/usr/share/doc/php5-apcu -d test_dir=/usr/share/php/tests install 
--offline --nodeps -P /php-apcu-4.0.7/debian/php5-apcu --nobuild 
./apcu-4.0.7/package.xml returned exit code 255
debian/rules:9: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 10
make[1]: Leaving directory '/php-apcu-4.0.7'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/php-apcu.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: php5
Source-Version: 5.6.16+dfsg-2

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated php5 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: Mon, 07 Dec 2015 17:15:51 +0100
Source: php5
Binary: php5 php5-common libapache2-mod-php5 libapache2-mod-php5filter php5-cgi 
php5-cli php5-phpdbg php5-fpm libphp5-embed php5-dev php5-dbg php-pear 
php5-curl php5-enchant php5-gd php5-gmp php5-imap php5-interbase php5-intl 
php5-ldap php5-mcrypt php5-readline php5-mysql php5-mysqlnd php5-odbc 
php5-pgsql php5-pspell php5-recode php5-snmp php5-sqlite php5-sybase php5-tidy 
php5-xmlrpc php5-xsl
Architecture: source amd64 all
Version: 5.6.16+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP Maintainers 
Changed-By: Ondřej Surý 
Description:
 libapache2-mod-php5 - server-side, HTML-embedded scripting language (Apache 2 
module)
 libapache2-mod-php5filter - server-side, HTML-embedded scripting language 
(apache 2 filter mo
 libphp5-embed - HTML-embedded scripting language (Embedded SAPI library)
 php-pear   - PEAR - PHP Extension and Application Repository
 php5   - server-side, HTML-embedded scripting language (metapackage)
 php5-cgi   - server-side, HTML-embedded scripting language (CGI binary)
 php5-cli   - command-line interpreter for the php5 scripting language
 php5-common - Common files for packages built from the php5 source
 php5-curl  - CURL module for php5
 php5-dbg   - Debug symbols for PHP5
 php5-dev   - Files for PHP5 module development
 php5-enchant - Enchant module for php5
 php5-fpm   - server-side, HTML-embedded scripting language (FPM-CGI binary)
 php5-gd- GD module for php5
 php5-gmp   - GMP module for php5
 php5-imap  - IMAP module for php5
 php5-interbase - interbase/firebird module for php5
 php5-intl  - internationalisation module for php5
 php5-ldap  - LDAP module for php5
 php5-mcrypt - MCrypt module for php5
 php5-mysql

Bug#807341: git-repair: uses non-random tempdir /tmp/tmprepo.0/.git/

[Jonas Smedegaard]

Package: git-repair
Version: 1.20150106-2
Severity: grave
Tags: security
Justification: user security hole

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

git-repair uses /tmp/tmprepo.0/.git/ which is clearly static, and I
believe therefore (on non-hardened systems) insecure.

 - Jonas

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWZc+/AAoJECx8MUbBoAEhfMsP/0TcaMfVoWdkFqwY4+4gFjFn
0iRp1AZgNA8pnrgdcnQNFIm6PvarOQZZ6K62cg7OfiuEIyji+u8DV8Pl741TPWr2
cJWaIPMWY5CX9hKRJMikE4JsxtmdNoZ+iXzGj/Mv50jx+SJL2AT1cjTi9kgoq9uE
FtyJAv0hooTenuKQzQz54dSiKQFfnVC7IoCYeMm/nPiveE9+CmaGg19IGUoy921Q
cXU9cmBk1Qv0aU9ErSa9FZl3mr+Q7+EbN30Qa5LciZMR2PFbG9CdkdWBXia14j3P
ZsIlyogcwukqtEu20jh54jaG3n0FnfMFOcvW6bi4RckwcL6FXp2h8U992vY3teCe
B/882vP+aNLeRhub+a/p4xUWsq5Z+Sbf1UX4iXT9hZRQ3mRyfwxy44Okh46tFLQe
tn7xoj676wPbZhx/j8cdh2S2sXQBTwg7wwRDz0ngM9YA5477sqPf0aoPcG5yRdgp
Herfwwblcny5LD868eEM2WuIygX4BRhfzAXPqgQYr46BVU3fUkVJeEwMqt4XKaXd
IFV0TG4B+mgTewe1NYQOtmkRIg/6owp9YS/bQq4yhUos5gITzB2vaFVWsAHejFHI
K1XInYeBv33vhmnfsnjAc+G1xVJzFZfUHZvjPb9144f/hkMnwQZhXP877qQndQtt
k3+PtInTNWBmgAxZEF1x
=0nH4
-END PGP SIGNATURE-

Bug#807171: libmemcached fails to build its manual pages

[Matthias Klose]

On 07.12.2015 08:44, Michael Fladischer wrote:

I'm unable to reproduce this FTBFS in a clean cowbuilder environment.
Could it be that this is a side-effect of parallel builds that Ubuntu
has enabled?


Parallel builds are enabled on the Debian buildds as well. I checked the issue 
in sid/unstable chroot.



If this is the case, feel free to do a NMU with your patch included as
I currently lack the time to investigate this further.


Ok, doing so.

Bug#806243: libminc: FTBFS on mipsel

[Steve Robbins]

Thanks Jurica.  Is there any difference in fpu?  Soft vs. Hard?  Extra 
precision bits?

On December 7, 2015 9:53:05 AM CST, Jurica Stanojkovic 
 wrote:
>> Jurica: is everything else the same between your good/bad
>environments, 
>> specifically: libc, compiler, and libnetcdf?  I mean: I assume they
>are both 
>> running 'sid', but are the specific versions of each package the
>same?
>
>Yes, i am using sbuild (sid) and environment should be the same.
>libc, compiler and libnetcdf are the same (same versions). 
>I have checked all build logs.
>
>Kernels are not the same:
>3.6.11+ on loongson
>3.7.10 on netlogic-xlp
>4.1.0 on cavium
>but i do not suggest that kernel is issue here.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#807323: gparted needs policykit-1 but its neither in depends or recommends

[shirish शिरीष]

On 07/12/2015, Phil Susi  wrote:
> Do you have udisks2 installed?  The only connection I can think of from
> gparted to policykit is through udisks, as the gparted script tries to
> run udisks-inhibit to stop auto mounting.  I'm guessing that is where
> this bug needs reassigned.
>



Yup, have udisks2 installed.

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

Processed: [bts-link] source package owncloud

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package owncloud
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #804651 (http://bugs.debian.org/804651)
> # Bug title: owncloud: renaming a folder can destroy all contained files
> #  * https://github.com/owncloud/core/issues/13391
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 804651 + fixed-upstream
Bug #804651 [owncloud] owncloud: renaming a folder can destroy all contained 
files
Added tag(s) fixed-upstream.
> usertags 804651 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#805222: [Pkg-php-pecl] Bug#805222: php-apcu: FTBFS: PHP Fatal error: Call to a member function getFilelist() on null

[Ondřej Surý]

Control: reassign -1 php-pear
Control: found -1 php-pear/5.6.16+dfsg-1
Control: affects -1 php5-apcu

Hi,

thank you for the report, after some debugging it seems this is a
generic error in PEAR instead of bug just in the php-apcu. This should
not affect no users, but it probably broke all PHP extensions, since it
stops honoring packagingroot after calling PEAR_Registry->setConfig()

I have a fix ready and PHP building, and I am ccing Fedora and SuSE
maintainers.

Mathieu, this also applies to your standalone src:php-pear:

diff --git a/PEAR/Command/Install.php b/PEAR/Command/Install.php
index 9d572ed..3b1fec9 100644
--- a/PEAR/Command/Install.php
+++ b/PEAR/Command/Install.php
@@ -848,7 +848,7 @@ Run post-installation scripts in package ,
if any exist.
 $pkg = &$instreg->getPackage($param->getPackage(),
 $param->getChannel());
 // $pkg may be NULL if install is a 'fake' install via
 --packagingroot
 if (is_object($pkg)) {
-$pkg->setConfig($this->config);
+$pkg->setConfig($this->config, false);
 if ($list = $pkg->listPostinstallScripts()) {
 $pn =
 $reg->parsedPackageNameToString(array('channel' =>
$param->getChannel(), 'package' =>
$param->getPackage()), true);


This fixes the issue right now, but it should be probably reported
upstream to have a correct fix (since this might break other stuff :)),
but my PEAR account doesn't work right now, so it might take me a while
to report this to upstream.

Cheers,
Ondrej

On Sun, Nov 15, 2015, at 22:18, Chris West (Faux) wrote:
> Source: php-apcu
> Version: 4.0.7-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
>   /usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d 
> include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin -d 
> php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d 
> doc_dir=/usr/share/doc/php5-apcu -d test_dir=/usr/share/php/tests install 
> --offline --nodeps -P /php-apcu-4.0.7/debian/php5-apcu --nobuild 
> ./apcu-4.0.7/package.xml
> PHP Fatal error:  Call to a member function getFilelist() on null in
> /usr/share/php/PEAR/Command/Install.php on line 747
> dh_auto_install: /usr/bin/pear -c debian/pearrc -d download_dir=/tmp -d
> include_path=/usr/share/php -d php_bin=/usr/bin/php -d bin_dir=/usr/bin
> -d php_dir=/usr/share/php -d data_dir=/usr/share/php/data -d
> doc_dir=/usr/share/doc/php5-apcu -d test_dir=/usr/share/php/tests install
> --offline --nodeps -P /php-apcu-4.0.7/debian/php5-apcu --nobuild
> ./apcu-4.0.7/package.xml returned exit code 255
> debian/rules:9: recipe for target 'override_dh_auto_install' failed
> make[1]: *** [override_dh_auto_install] Error 10
> make[1]: Leaving directory '/php-apcu-4.0.7'
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/php-apcu.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> ___
> Pkg-php-pecl mailing list
> pkg-php-p...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-pecl


-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

Processed: Re: [Pkg-php-pecl] Bug#805222: php-apcu: FTBFS: PHP Fatal error: Call to a member function getFilelist() on null

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 php-pear
Bug #805222 [src:php-apcu] php-apcu: FTBFS: PHP Fatal error:  Call to a member 
function getFilelist() on null
Bug reassigned from package 'src:php-apcu' to 'php-pear'.
No longer marked as found in versions php-apcu/4.0.7-1.
Ignoring request to alter fixed versions of bug #805222 to the same values 
previously set
> found -1 php-pear/5.6.16+dfsg-1
Bug #805222 [php-pear] php-apcu: FTBFS: PHP Fatal error:  Call to a member 
function getFilelist() on null
The source php-pear and version 5.6.16+dfsg-1 do not appear to match any binary 
packages
Marked as found in versions php-pear/5.6.16+dfsg-1.
> affects -1 php5-apcu
Bug #805222 [php-pear] php-apcu: FTBFS: PHP Fatal error:  Call to a member 
function getFilelist() on null
Added indication that 805222 affects php5-apcu

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

Bug#806243: libminc: FTBFS on mipsel

[Jurica Stanojkovic]

> Jurica: is everything else the same between your good/bad environments, 
> specifically: libc, compiler, and libnetcdf?  I mean: I assume they are both 
> running 'sid', but are the specific versions of each package the same?

Yes, i am using sbuild (sid) and environment should be the same.
libc, compiler and libnetcdf are the same (same versions). 
I have checked all build logs.

Kernels are not the same:
3.6.11+ on loongson
3.7.10 on netlogic-xlp
4.1.0 on cavium
but i do not suggest that kernel is issue here.

Bug#807019: tracking bin-num - broken unison due to binnmu upload

[Stéphane Glondu]

Le 06/12/2015 12:15, Norbert Preining a écrit :
> * is there a way to track down who uploaded -3+b1?

For "who", I don't know. But for "why", cf
/usr/share/doc/unison2.40.102/changelog.Debian.amd64.gz:
> unison2.40.102 (2.40.102-3+b1) sid; urgency=low, binary-only=yes
> 
>   * Binary-only non-maintainer upload for amd64; no source changes.
>   * Rebuild against ncurses 6.0.
> 
>  -- amd64 / i386 Build Daemon (babin)   Fri, 
> 31 Jul 2015 09:50:21 +0200

...which is strange, because unison doesn't use ncurses AFAICT. Also,
the date is misleading; it corresponds to the last sourceful upload, not
the binNMU.

But I now understand the problem: unison2.40.102 uses Obj.magic (i.e. an
unsafe coercion) to cast a format string into a string. The previous
unison version was compiled with OCaml 4.01.0, where format strings were
indeed strings. The new version was compiled with OCaml 4.02.3, where it
is no longer the case. unison2.32.52 should suffer from the same problem.

The change done in unison 2.48 to overcome this looks pretty big... I'm
not sure I'll be able/willing to provide a unison2.40.102 any more.
Moreover, this package was created to provide compatibility with
previous Debian releases, but another change in OCaml 4.02 makes it
incompatible anyway (both communicating unisons need to be compiled with
the same version of OCaml in practice, which won't be the case any more
when one side is Debian stable, and the other Debian testing). IMHO,
that's a design flaw in Unison that cannot be easily fixed.

-- 
Stéphane

Bug#807331: marked as done (samba: Fails to build from source when not being able to download docbook.xsl)

[Debian Bug Tracking System]

Your message dated Mon, 7 Dec 2015 16:07:40 +0100
with message-id <5665a0bc.6010...@physik.fu-berlin.de>
and subject line Re: [Pkg-samba-maint] Bug#807331: Bug#807331: samba: Fails to 
build from source when not being able to download docbook.xsl
has caused the Debian Bug report #807331,
regarding samba: Fails to build from source when not being able to download 
docbook.xsl
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.)


-- 
807331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.1.21+dfsg-2
Severity: serious
Justification: fails to build from source (sometimes)

Hello!

The samba package fails to build from source when it can't download the external
stylesheet docbook.xsl which is downloaded from sourceforge.net:

Checking for stylesheet 
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl : not 
found

and consequently won't build the manpages which then results in:

#Remove unused vfstest manpage as there is no more vfstest apparently
rm /<>/samba-4.1.21+dfsg/debian/tmp/usr/share/man/man1/vfstest.1
rm: cannot remove 
'/<>/samba-4.1.21+dfsg/debian/tmp/usr/share/man/man1/vfstest.1': No 
such file or directory
debian/rules:93: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>/samba-4.1.21+dfsg'
debian/rules:69: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

I'm not sure why exactly the download of the stylesheet fails. It fails on the
sparc64 and x32 buildds and on my personal sbuild amd64 chroot, all of them
are up-to-date. Since I can download the stylesheet from the very same machine
I am using for amd64 builds:

glaubitz@z6:~> wget 
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
--2015-12-07 14:51:42--  
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
Resolving docbook.sourceforge.net (docbook.sourceforge.net)... 216.34.181.96
Connecting to docbook.sourceforge.net 
(docbook.sourceforge.net)|216.34.181.96|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15230 (15K) [application/xslt+xml]
Saving to: ‘docbook.xsl’

docbook.xsl
100%[==>]  
14.87K  64.5KB/s   in 0.2s   

2015-12-07 14:51:50 (64.5 KB/s) - ‘docbook.xsl’ saved [15230/15230]

glaubitz@z6:~>

it must be some extra sbuild/schroot configuration or additional package that 
the samba build
scripts rely on to be able to download the stylesheet. However, I think it's 
generally
bad when a package in Debian can no longer be build from source just because a 
file on
a third party server is missing or corrupted. That being said, I think it's 
also a
potential security problem when the buildds blindly download files from third 
party
servers.

Cheers,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
On 12/07/2015 03:38 PM, Jelmer Vernooij wrote:
>> That could explain the problem on sparc64 and x32, but it doesn't
>> segfault on my amd64 machine, yet the download fails. I can run xsltproc
>> with the URL in my sbuild chroot and it is able to download and parse
>> the file. However, when I sbuild samba, it still fails. I can't really
>> wrap my head around what happens here.
> Do you have /dev/shm available in your sbuild chroot, per that bug?

Ok, this *does* fix the problem actually. I have to bind-mount dev
into my chroot and set the permissions to 777. Vry strange that
xsltproc does not fail when I chroot into my sbuild environment and
call it directly, but it fails when the samba Python scripts call it.

In any case, thanks a lot for helping me to pin-point the issue. This
is indeed a bug in xsltproc then and we can therefore close this bug
again!

I will make the necessary modifications to all buildds in question!

Thanks,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913--- End Message ---

Bug#807331: [Pkg-samba-maint] Bug#807331: Bug#807331: samba: Fails to build from source when not being able to download docbook.xsl

[Jelmer Vernooij]

On Mon, Dec 07, 2015 at 03:23:00PM +0100, John Paul Adrian Glaubitz wrote:
> On 12/07/2015 03:03 PM, Jelmer Vernooij wrote:
> > The root cause is probably this bug: http://bugs.debian.org/750593
> 
> That could explain the problem on sparc64 and x32, but it doesn't
> segfault on my amd64 machine, yet the download fails. I can run xsltproc
> with the URL in my sbuild chroot and it is able to download and parse
> the file. However, when I sbuild samba, it still fails. I can't really
> wrap my head around what happens here.
Do you have /dev/shm available in your sbuild chroot, per that bug?

Have you tried building the Samba manpages in your schroot, e.g. smb.conf.5?
That's the one that actually needs it.

Cheers,

Jelmer

Bug#807331: [Pkg-samba-maint] Bug#807331: samba: Fails to build from source when not being able to download docbook.xsl

[John Paul Adrian Glaubitz]

On 12/07/2015 03:03 PM, Jelmer Vernooij wrote:
> Are you sure that it is actually attempting to download the file from a remote
> server? The docbook-xsl package should make sure that it is just using a local
> copy of that file, even when Samba is referencing the URL.

No, I am not 100% sure yet. I am still trying to debug the issue.

> The root cause is probably this bug: http://bugs.debian.org/750593

That could explain the problem on sparc64 and x32, but it doesn't
segfault on my amd64 machine, yet the download fails. I can run xsltproc
with the URL in my sbuild chroot and it is able to download and parse
the file. However, when I sbuild samba, it still fails. I can't really
wrap my head around what happens here.

I will do more debugging and see whether I can pin-point the actual
problem.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#802671: Tentative patches for version 1.44

[Raphael Hertzog]

On Fri, 04 Dec 2015, Markus Koschany wrote:
> thanks for your work on this bug. We intend to upload version 1.51 of
> bouncycastle to unstable this weekend since we were able to upgrade all
> reverse-dependencies except one so far. Are there any new information
> regarding the patches for Jessie? Shall we still wait with an upload or
> is it safe to use the three existing patches?

Upstream told me that the supplementary fixes will be released in
version 1.54 as they are not urgent and that we can release the current
set of fixes for now.

He suggested to run the ECPointTest unit tests against the backported code
though. I did not check yet what this involves... and whether unit tests
are run automatically during build or not.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#807331: [Pkg-samba-maint] Bug#807331: samba: Fails to build from source when not being able to download docbook.xsl

[Jelmer Vernooij]

On Mon, Dec 07, 2015 at 02:54:57PM +0100, John Paul Adrian Glaubitz wrote:
> Package: samba
> Version: 2:4.1.21+dfsg-2
> Severity: serious
> Justification: fails to build from source (sometimes)
> 
> Hello!
> 
> The samba package fails to build from source when it can't download the 
> external
> stylesheet docbook.xsl which is downloaded from sourceforge.net:
> 
> Checking for stylesheet 
> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl : not 
> found
> 
> and consequently won't build the manpages which then results in:
> 
> #Remove unused vfstest manpage as there is no more vfstest apparently
> rm /<>/samba-4.1.21+dfsg/debian/tmp/usr/share/man/man1/vfstest.1
> rm: cannot remove 
> '/<>/samba-4.1.21+dfsg/debian/tmp/usr/share/man/man1/vfstest.1': No 
> such file or directory
> debian/rules:93: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 1
> make[1]: Leaving directory '/<>/samba-4.1.21+dfsg'
> debian/rules:69: recipe for target 'binary' failed
> make: *** [binary] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2
> 
> I'm not sure why exactly the download of the stylesheet fails. It fails on the
> sparc64 and x32 buildds and on my personal sbuild amd64 chroot, all of them
> are up-to-date. Since I can download the stylesheet from the very same machine
> I am using for amd64 builds:

Are you sure that it is actually attempting to download the file from a remote
server? The docbook-xsl package should make sure that it is just using a local
copy of that file, even when Samba is referencing the URL.

The root cause is probably this bug: http://bugs.debian.org/750593

Cheers,

Jelmer

Bug#807331: samba: Fails to build from source when not being able to download docbook.xsl

[John Paul Adrian Glaubitz]

Package: samba
Version: 2:4.1.21+dfsg-2
Severity: serious
Justification: fails to build from source (sometimes)

Hello!

The samba package fails to build from source when it can't download the external
stylesheet docbook.xsl which is downloaded from sourceforge.net:

Checking for stylesheet 
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl : not 
found

and consequently won't build the manpages which then results in:

#Remove unused vfstest manpage as there is no more vfstest apparently
rm /<>/samba-4.1.21+dfsg/debian/tmp/usr/share/man/man1/vfstest.1
rm: cannot remove 
'/<>/samba-4.1.21+dfsg/debian/tmp/usr/share/man/man1/vfstest.1': No 
such file or directory
debian/rules:93: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
make[1]: Leaving directory '/<>/samba-4.1.21+dfsg'
debian/rules:69: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

I'm not sure why exactly the download of the stylesheet fails. It fails on the
sparc64 and x32 buildds and on my personal sbuild amd64 chroot, all of them
are up-to-date. Since I can download the stylesheet from the very same machine
I am using for amd64 builds:

glaubitz@z6:~> wget 
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
--2015-12-07 14:51:42--  
http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl
Resolving docbook.sourceforge.net (docbook.sourceforge.net)... 216.34.181.96
Connecting to docbook.sourceforge.net 
(docbook.sourceforge.net)|216.34.181.96|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 15230 (15K) [application/xslt+xml]
Saving to: ‘docbook.xsl’

docbook.xsl
100%[==>]  
14.87K  64.5KB/s   in 0.2s   

2015-12-07 14:51:50 (64.5 KB/s) - ‘docbook.xsl’ saved [15230/15230]

glaubitz@z6:~>

it must be some extra sbuild/schroot configuration or additional package that 
the samba build
scripts rely on to be able to download the stylesheet. However, I think it's 
generally
bad when a package in Debian can no longer be build from source just because a 
file on
a third party server is missing or corrupted. That being said, I think it's 
also a
potential security problem when the buildds blindly download files from third 
party
servers.

Cheers,
Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#769146: openntpd: fails to upgrade from 'sid' - trying to overwrite /etc/apparmor.d/usr.sbin.ntpd

[Martin-Éric Racine]

Package: openntpd
Followup-For: Bug #769146

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

It should be noted that this bug was filed in November 2014.

Since then, openntpd has been removed from Testing due to this bug being marked 
as Serious and not having been acted upon within a reasonable time.

Whichever solution the maintainers of openntpd, ntp and apparmor decide to go 
with, a timely response would be appreciated. In any case, letting the package 
get removed from the archive because nobody dares to make a decision in one 
direction or another should be avoided.

- -- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (1001, 'testing'), (1001, 'stable'), (1001, 'oldstable')
Architecture: i386 (i586)

Kernel: Linux 3.16.0-4-586
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openntpd depends on:
ii  adduser  3.113+nmu3
ii  init-system-helpers  1.24
ii  libc62.19-22
ii  libssl1.0.0  1.0.2d-1
ii  netbase  5.3

openntpd recommends no packages.

openntpd suggests no packages.

- -- Configuration Files:
/etc/default/openntpd changed [not included]

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWZd/MAAoJEK4fgnfEtNe2F3kP/j/B9sN2FwupCrBm1SqcTXNI
4+5XI9HYfUDeEw9C6IU+YCxNr5NkV1pFbzAOsd8QnRWIudrhpZvycAzkL9adBgX/
Tq/7Za6Zh93M8YIVrxN9ggGZttsf7T8hI1EOeF/NkLDPiZ+LIDQMdXnoTTvSi/wo
6SuI8Gtdpsvs2PRCnOxx3T6WGWF3Hz2Oe7P/rLd77UZXnevML+JZpwoDGc6L4STR
lP83/pBIVt3SfJsFYQTWb+LfwZWnvM40Bzny2NZzqIt3ntZ+JYYhKJ+bgVmCwmTn
+Y15Fnm/MkaorfX8yDf7yijq0J94qThJpCpMe4W07UcgsMWRJlk/KAgrqL3b6HhL
AsMyZloFg26Hs/Ekp0snCBKz/wIWI4KP4x/y/Tat/HG8fx0q6tUOJrvr0vjmTDZ6
D+/iekAWdFswqLYqJvBsvIhwm1sWDKvM4dKd5vDyH0tUunsUMS+mm5y/buqqED+W
9wdby7gHx1UB9R6aFL3PMB8dqr5uGjuLbooIj2JvMw8pE5MGYpDOub6gup8r44TV
NMSodJtrgtkY1opcxToUelKkxoZVJMpvLh46Y9TSWd0qvPpCOR3YZWXG5QobOcvS
WXOwRq1ye2I2ulRR3WNCUtYzxDg+k++TxP86bhnxoCZSwiQO2MF606f+Mk0W5ijd
6huz5H6/rACTPy3sVmhr
=zcM7
-END PGP SIGNATURE-

Bug#807328: [Pkg-mozext-maintainers] Bug#807328: flashblock doesn't work with 38.4.0 iceweacel

[David Prévot]

Control: tag -1 moreinfo

Hi,

Thanks for your interest in packaged extensions.

> Package: xul-ext-flashblock
> Version: 1.5.19-1
> Severity: grave

> the current version of the flashblock installed from the debian package

The 1.5.19-1 version of flashblock is only available for Stretch currently.

> doesn't work with the current version of Iceweasel installed from the
> security repository:
> iceweasel:amd64/stable 38.4.0esr-1~deb8u1 uptodate

That is the Iceweasel version from Jessie.

> I have tried to reinstall the previous version [2] and this one still
> works fine. I have no idea why the newer version doesn't work but maybe
> the debian package should be reverted back to 1.5.18?

Can you please reinstall the actual package from Jessie, i.e., the
1.5.18-1 version, and report back if it works? If it doesn’t work, can you
please install the latest version (1.5.20-1) from unstable, and report
back?

Regards

David

Processed: Re: [Pkg-mozext-maintainers] Bug#807328: flashblock doesn't work with 38.4.0 iceweacel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #807328 [xul-ext-flashblock] flashblock doesn't work with 38.4.0 iceweacel
Added tag(s) moreinfo.

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

Bug#807323: gparted needs policykit-1 but its neither in depends or recommends

[Phil Susi]

Do you have udisks2 installed?  The only connection I can think of from
gparted to policykit is through udisks, as the gparted script tries to
run udisks-inhibit to stop auto mounting.  I'm guessing that is where
this bug needs reassigned.

On 12/7/2015 7:33 AM, shirish शिरीष wrote:
> Package: gparted
> Version: 0.19.0-3+b2
> Justification: renders package unusable
> Severity: grave
> 
> Dear Maintainer,
> This is how gparted currently looks.
> 
> [$] aptitude show gparted
> 
> Package: gparted
> State: installed
> Automatically installed: no
> Version: 0.19.0-3+b2
> Priority: optional
> Section: gnome
> Maintainer: Phillip Susi 
> Architecture: amd64
> Uncompressed Size: 6,245 k
> Depends: libatkmm-1.6-1v5 (>= 2.22.1), libc6 (>= 2.14), libgcc1 (>=
> 1:4.1.1), libglib2.0-0 (>= 2.12.0), libglibmm-2.4-1v5 (>= 2.44.0),
> libgtk2.0-0 (>= 2.14.0), libgtkmm-2.4-1v5 (>= 1:2.24.0),
> libpangomm-1.4-1v5 (>= 2.36.0), libparted-fs-resize0 (>= 3.1),
> libparted2 (>=3.1), libsigc++-2.0-0v5 (>= 2.2.0), libstdc++6 (>= 5.2),
> libuuid1 (>= 2.16)
> Suggests: xfsprogs, reiserfsprogs, reiser4progs, jfsutils, ntfs-3g,
> dosfstools, mtools, yelp, kpartx, dmraid, dmsetup, gpart
> Breaks: udisks2 (< 2.1.5)
> Description: GNOME partition editor
>  GParted uses libparted to detect and manipulate devices and partition
> tables while several (optional) filesystem tools provide support for
> filesystems not included in libparted.
> Homepage: http://gparted.sourceforge.net
> 
> It's only if I run it as root that I come to know that why it is
> failing otherwise it fails silently as shared in #658316
> 
> [$] gksudo gparted
> [$]
> 
> Although running sudo has the desired effect :-
> 
> ─[$] sudo gparted
> 
> :25]
> /var/lib/polkit-1/localauthority/90-mandatory.d does not exist. Please
> install policykit-1
> 
> Aside from not telling what is needed, I am under the impression that
> policykit is not a favorite in the Debian community, especially
> systemd maintainer Michael Biebl. I did hear rumors of policykit being
> deprecated and some part/binary of systemd probably doing that.
> 
> Maybe you could look into that as well.
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (600, 'testing'), (1, 'experimental'), (1, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages gparted depends on:
> ii  libatkmm-1.6-1v5  2.24.1-1
> ii  libc6 2.21-0experimental4
> ii  libgcc1   1:5.2.1-23
> ii  libglib2.0-0  2.46.2-1
> ii  libglibmm-2.4-1v5 2.46.2-1
> ii  libgtk2.0-0   2.24.28-1
> ii  libgtkmm-2.4-1v5  1:2.24.4-2+b1
> ii  libpangomm-1.4-1v52.38.1-1
> ii  libparted-fs-resize0  3.2-10
> ii  libparted23.2-10
> ii  libsigc++-2.0-0v5 2.6.2-1
> ii  libstdc++65.2.1-23
> ii  libuuid1  2.27.1-1
> 
> gparted recommends no packages.
> 
> Versions of packages gparted suggests:
> pn  dmraid 
> ii  dmsetup2:1.02.110-1
> ii  dosfstools 3.0.28-2
> ii  gpart  1:0.3-1
> pn  jfsutils   
> ii  kpartx 0.5.0+git1.656f8865-1
> ii  mtools 4.0.18-2
> ii  ntfs-3g1:2015.3.14AR.1-1
> pn  reiser4progs   
> ii  reiserfsprogs  1:3.6.24-3.1
> ii  xfsprogs   4.2.0
> ii  yelp   3.16.1-1
> 
> -- no debconf information
> 
> 

Bug#807328: flashblock doesn't work with 38.4.0 iceweacel

[Michal Hocko]

Package: xul-ext-flashblock
Version: 1.5.19-1
Severity: grave

Hi,
the current version of the flashblock installed from the debian package
doesn't work with the current version of Iceweasel installed from the
security repository:
iceweasel:amd64/stable 38.4.0esr-1~deb8u1 uptodate

No flash content is blocked but it is loaded automatically instead. I
have checked the plugin upstream [1] and there is a remark about 38.4.0
not being supported: "Not available for Firefox 38.4.0"

I have tried to reinstall the previous version [2] and this one still
works fine. I have no idea why the newer version doesn't work but maybe
the debian package should be reverted back to 1.5.18?

[1] https://addons.mozilla.org/en-US/firefox/addon/flashblock/
[2]
https://addons.mozilla.org/en-US/firefox/addon/flashblock/versions/?page=1#version-1.5.18.1-signed

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

Kernel: Linux 4.4.0-rc3-5-g2255702db401 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

xul-ext-flashblock depends on no packages.

Versions of packages xul-ext-flashblock recommends:
ii  iceweasel  38.4.0esr-1~deb8u1

xul-ext-flashblock suggests no packages.

-- no debconf information

-- 
Michal Hocko

Bug#801608: marked as done (ntop: build-depends on non-existent librrd2-dev)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2015 13:34:24 +
with message-id 
and subject line Bug#801608: fixed in ntop 3:5.0.1+dfsg1-2.2
has caused the Debian Bug report #801608,
regarding ntop: build-depends on non-existent librrd2-dev
to be marked as done.

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

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


-- 
801608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ntop
Version: 3:5.0.1+dfsg1-2.1
Usertags: goto-cc
Severity: serious
Justification: FTBFS

As of its version 1.5.4-3, rrdtool no longer Provides: librrd2-dev from
librrd-dev. This breaks the build of ntop. Changing the build-dependency to
librrd-dev should fix the problem.

Best,
Michael



pgpP3yiSKzGZp.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ntop
Source-Version: 3:5.0.1+dfsg1-2.2

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

Debian distribution maintenance software
pp.
Giovani Augusto Ferreira  (supplier of updated ntop 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: SHA1

Format: 1.8
Date: Wed, 02 Dec 2015 01:59:31 -0200
Source: ntop
Binary: ntop ntop-dbg ntop-data
Architecture: source
Version: 3:5.0.1+dfsg1-2.2
Distribution: unstable
Urgency: medium
Maintainer: Ludovico Cavedon 
Changed-By: Giovani Augusto Ferreira 
Description:
 ntop   - display network usage in web browser
 ntop-data  - display network usage in a web browser (data files)
 ntop-dbg   - display network usage in web browser (debug symbols)
Closes: 801608
Changes:
 ntop (3:5.0.1+dfsg1-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: fixed the build-dependency to librrd-dev (Closes: #801608).
Checksums-Sha1:
 8379b4903b97506a46fce1e8bcb859469a08a15e 2137 ntop_5.0.1+dfsg1-2.2.dsc
 09ced9082c8e5e46b4bda0d4e45584e76a40107a 124876 
ntop_5.0.1+dfsg1-2.2.debian.tar.xz
Checksums-Sha256:
 3d2b8c91d5bf0ea6ea18d466c63614578d07b90d49a228d5f4cae83e77e4c4c6 2137 
ntop_5.0.1+dfsg1-2.2.dsc
 11ba871c083190c581de420c69ee209d8020378ef58141a2bff94877b6a2f542 124876 
ntop_5.0.1+dfsg1-2.2.debian.tar.xz
Files:
 b9dd321c569a96bee523fac33774c206 2137 net optional ntop_5.0.1+dfsg1-2.2.dsc
 6f112213bc67319cc95cf0e0d459222b 124876 net optional 
ntop_5.0.1+dfsg1-2.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWXuvnAAoJEN5juccE6+nvaogP/jSlAVCQUb0z2AyJJkWBJafz
QZrGg/zm48CnaDXPEKRRXedwqlkFA7IzUoOIggC2gXAZBCBNhyIQfuEyz9cRRZ2S
sXcx8oyTq9WqEoVr4YoVj3R/ipevj+1vgpAJEyradGFL1eckrrvTDshFp4+oOdxT
uve+CGLITRLRKV3+fc0392nEGbcp6/FNG7cQi8r/iqTy2pgCIsHxef2wNpa4Uat0
affIRa4vXYelqmoUbCpWo8qBBexr9sCi8b8J+OQHEOoYV2rtp29rVii/xYMQCCbZ
K6W4ubVpsMQ8aOfkvYS/6v/eryDcoRKNufDilIHjOf7aN6h0HrfnZORnI7vMpSIP
FTXaLf1JPt+ZlyPMay/Lkq8ES4AT1YgaDON9DfZVHMxAo7r+gyZ0D4+saU4rj/+/
z2uyS8f6nh9svt6jFENeAxUVMxTXJSrvYS5mbNjTG7IlfOO45KAKDyLCXCgbZO/p
wiVj5z7Yn+6P02YckV3Y36Svd36dE1of3Azrrie9mE9uxyN+X8IkMuhR3aK0Su0K
+67+r+2X2uetzAZ6UEzhF56GAMcmzVGaJ3qbK//USsKt61rdMNnUS4VDIdm+ZUBa
INAdrsPOoBx+QKYFsle555vj8qzzFADnMH86G5Lv7hZE8LZVjfFrThODNUCQFunl
BIzNRrnMVbUwMtVKrSzE
=OdLm
-END PGP SIGNATURE End Message ---

Bug#799711: marked as done (php7.0-cli: fails to upgrade from 'sid' - trying to overwrite /usr/share/man/man1/phar.1.gz)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2015 12:50:46 +
with message-id 
and subject line Bug#799711: fixed in php7.0 7.0.0-4
has caused the Debian Bug report #799711,
regarding php7.0-cli: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/man/man1/phar.1.gz
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.)


-- 
799711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php7.0-cli
Version: 7.0.0~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package php7.0-cli.
  Preparing to unpack .../php7.0-cli_7.0.0~rc1-1_amd64.deb ...
  Unpacking php7.0-cli (7.0.0~rc1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/php7.0-cli_7.0.0~rc1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/phar.1.gz', which is also in 
package php5-cli 5.6.13+dfsg-2
  Errors were encountered while processing:
   /var/cache/apt/archives/php7.0-cli_7.0.0~rc1-1_amd64.deb


cheers,

Andreas


php5-cli=5.6.13+dfsg-2_php7.0-cli=7.0.0~rc1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: php7.0
Source-Version: 7.0.0-4

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated php7.0 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: Mon, 07 Dec 2015 11:58:02 +0100
Source: php7.0
Binary: libapache2-mod-php7.0 libphp7.0-embed php7.0 php7.0-cgi php7.0-cli 
php7.0-common php7.0-dbg php7.0-dev php7.0-fpm php7.0-modules-source 
php7.0-phpdbg php7.0-recode php7.0-sqlite3 php7.0-sybase php7.0-gd php7.0-ldap 
php7.0-intl php7.0-json php7.0-pgsql php7.0-opcache php7.0-imap php7.0-mysql 
php7.0-tidy php7.0-snmp php7.0-pspell php7.0-curl
Architecture: source amd64 all
Version: 7.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP Maintainers 
Changed-By: Ondřej Surý 
Description:
 libapache2-mod-php7.0 - server-side, HTML-embedded scripting language (Apache 
2 module)
 libphp7.0-embed - HTML-embedded scripting language (Embedded SAPI library)
 php7.0 - server-side, HTML-embedded scripting language (metapackage)
 php7.0-cgi - server-side, HTML-embedded scripting language (CGI binary)
 php7.0-cli - command-line interpreter for the PHP scripting language
 php7.0-common - Common files for packages built from the PHP source
 php7.0-curl - CURL module for PHP
 php7.0-dbg - Debug symbols for PHP7.0
 php7.0-dev - Files for PHP7.0 module development
 php7.0-fpm - server-side, HTML-embedded scripting language (FPM-CGI binary)
 php7.0-gd  - GD module for PHP
 php7.0-imap - IMAP module for PHP
 php7.0-intl - Internationalisation module for PHP
 php7.0-json - JSON module for PHP
 php7.0-ldap - LDAP module for PHP
 php7.0-modules-source - PHP 7.0 modules source package
 php7.0-mysql - MySQL module for PHP
 php7.0-opcache - Zend OpCache module for PHP
 php7.0-pgsql - PostgreSQL module for PHP
 php7.0-phpdbg - server-side, HTML-embedded scripting language (PHPDBG binary)
 php7.0-pspell - pspell module for PHP
 php7.0-recode - recode module for PHP
 php7.0-snmp - SNMP module for PHP
 php7.0-sqlite3 - SQLite3 module for PHP
 php7.0-sybase - Sybase module for PHP
 php7.0-tidy - tidy module for PHP
Closes: 799711
Changes:
 php7.0 (7.0.0-4) unstable; urgency=medium
 .
   * Add Replaces: php5-cli to php7.0-cli (Closes: #799711)
Checksums-Sha1:
 7269bbc5565bb52f8092b0175e7dbd48875d 4843 php7.0_7.0.0-4.dsc
 59a272c777229a14cda9b488b729e6d3775231d3 52820 php7.0_7.0.0-4.debian.tar.xz
 9d62fa7

Processed: block 796345 with 807324

[Debian Bug Tracking System]

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

> block 796345 with 807324
Bug #796345 [release.debian.org] transition: perl 5.22
796345 was blocked by: 788073 790532 804603 795127 787468 802939 787493 787453 
807038 799118 787450 796923 804590
796345 was blocking: 798309 801659 801660 801661 801662 801663
Added blocking bug(s) of 796345: 807324
> thanks
Stopping processing here.

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

Bug#807324: libio-pty-perl: FTBFS with perl 5.22 in experimental (MakeMaker changes)

[Dominic Hargreaves]

Source: libio-pty-perl
Version: 1:1.08-1
Severity: serious
Justification: transition imminent
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition makemaker-prefix
Tags: sid stretch

This package FTBFS with perl 5.22.0-2, which removed support for a long-
obsolete way of overriding PREFIX when calling 'make install' with
ExtUtils::MakeMaker, as described in the lintian tag
debian-rules-makemaker-prefix-is-deprecated[1] and the Debian Perl
policy[2]:


ERROR: Can't create '/usr/lib/x86_64-linux-gnu/perl5/5.22/IO'
mkdir /usr/lib/x86_64-linux-gnu/perl5/5.22/IO: Permission denied at 
/usr/share/perl/5.22/ExtUtils/Install.pm line 477.


 at -e line 1.
Makefile:824: recipe for target 'pure_vendor_install' failed

The fix is to use DESTDIR instead of PREFIX; please see the lintian
`description for examples. Alternatively, newer versions of debhelper
can automatically call make install with the correct arguments when
using the dh7 style rules files.

The perl 5.22 is due to start this week, so apologies for the late
submission of this bug; for some reason my previous testing of this
issue overlooked libio-pty-perl.

Cheers,
Dominic.

[1] 

[2] 

Bug#807323: gparted needs policykit-1 but its neither in depends or recommends

[shirish शिरीष]

Package: gparted
Version: 0.19.0-3+b2
Justification: renders package unusable
Severity: grave

Dear Maintainer,
This is how gparted currently looks.

[$] aptitude show gparted

Package: gparted
State: installed
Automatically installed: no
Version: 0.19.0-3+b2
Priority: optional
Section: gnome
Maintainer: Phillip Susi 
Architecture: amd64
Uncompressed Size: 6,245 k
Depends: libatkmm-1.6-1v5 (>= 2.22.1), libc6 (>= 2.14), libgcc1 (>=
1:4.1.1), libglib2.0-0 (>= 2.12.0), libglibmm-2.4-1v5 (>= 2.44.0),
libgtk2.0-0 (>= 2.14.0), libgtkmm-2.4-1v5 (>= 1:2.24.0),
libpangomm-1.4-1v5 (>= 2.36.0), libparted-fs-resize0 (>= 3.1),
libparted2 (>=3.1), libsigc++-2.0-0v5 (>= 2.2.0), libstdc++6 (>= 5.2),
libuuid1 (>= 2.16)
Suggests: xfsprogs, reiserfsprogs, reiser4progs, jfsutils, ntfs-3g,
dosfstools, mtools, yelp, kpartx, dmraid, dmsetup, gpart
Breaks: udisks2 (< 2.1.5)
Description: GNOME partition editor
 GParted uses libparted to detect and manipulate devices and partition
tables while several (optional) filesystem tools provide support for
filesystems not included in libparted.
Homepage: http://gparted.sourceforge.net

It's only if I run it as root that I come to know that why it is
failing otherwise it fails silently as shared in #658316

[$] gksudo gparted
[$]

Although running sudo has the desired effect :-

─[$] sudo gparted

:25]
/var/lib/polkit-1/localauthority/90-mandatory.d does not exist. Please
install policykit-1

Aside from not telling what is needed, I am under the impression that
policykit is not a favorite in the Debian community, especially
systemd maintainer Michael Biebl. I did hear rumors of policykit being
deprecated and some part/binary of systemd probably doing that.

Maybe you could look into that as well.

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

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

Versions of packages gparted depends on:
ii  libatkmm-1.6-1v5  2.24.1-1
ii  libc6 2.21-0experimental4
ii  libgcc1   1:5.2.1-23
ii  libglib2.0-0  2.46.2-1
ii  libglibmm-2.4-1v5 2.46.2-1
ii  libgtk2.0-0   2.24.28-1
ii  libgtkmm-2.4-1v5  1:2.24.4-2+b1
ii  libpangomm-1.4-1v52.38.1-1
ii  libparted-fs-resize0  3.2-10
ii  libparted23.2-10
ii  libsigc++-2.0-0v5 2.6.2-1
ii  libstdc++65.2.1-23
ii  libuuid1  2.27.1-1

gparted recommends no packages.

Versions of packages gparted suggests:
pn  dmraid 
ii  dmsetup2:1.02.110-1
ii  dosfstools 3.0.28-2
ii  gpart  1:0.3-1
pn  jfsutils   
ii  kpartx 0.5.0+git1.656f8865-1
ii  mtools 4.0.18-2
ii  ntfs-3g1:2015.3.14AR.1-1
pn  reiser4progs   
ii  reiserfsprogs  1:3.6.24-3.1
ii  xfsprogs   4.2.0
ii  yelp   3.16.1-1

-- no debconf information


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

Bug#806721: marked as done (boinc: non-free files)

[Debian Bug Tracking System]

Your message dated Mon, 07 Dec 2015 12:19:06 +
with message-id 
and subject line Bug#806721: fixed in boinc 7.6.19+dfsg-1
has caused the Debian Bug report #806721,
regarding boinc: non-free files
to be marked as done.

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

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


-- 
806721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boinc
Version: 7.6.17+dfsg-1exp1
Severity: serious

File "clientscr/progress/simt" is licensed under non-free Monotype license:

   This typeface is the property of Monotype Imaging Inc. and its use by you
   is covered under the terms of a license agreement. You have obtained this
   typeface software either directly from Monotype Imaging or together with
   software distributed by one of the licencees of Monotype Imaging.



   This software is a valuable asset of Monotype Imaging. Unless you have
   entered into a specific license agreement granting you additional rights,
   your use of this software is limited to use on up to five (5) workstation
   for your own publishing use. You may not copy or distribute this software.

The following images

android/BOINC/res/drawable-ldpi/acctmgrb.png


android/BOINC/res/drawable-ldpi/cogsb.png   


android/BOINC/res/drawable-ldpi/connectchargerb.png 


android/BOINC/res/drawable-ldpi/helpb.png   


android/BOINC/res/drawable-ldpi/magnifierb.png  


android/BOINC/res/drawable-ldpi/refreshw.png


android/BOINC/res/drawable-ldpi/speechbubbleb.png   


android/BOINC/res/drawable-ldpi/sqplusb.png 


android/BOINC/res/drawable-ldpi/wirelessb.png   


android/BOINC/res/drawable-mdpi/acctmgrb.png


android/BOINC/res/drawable-mdpi/cogsb.png   


android/BOINC/res/drawable-mdpi/connectchargerb.png 


android/BOINC/res/drawable-mdpi/helpb.png   


android/BOINC/res/drawable-mdpi/magnifierb.png  


android/BOINC/res/drawable-mdpi/refreshw.png


android/BOINC/res/drawable-mdpi/speechbubbleb.png   


android/BOINC/res/drawable-mdpi/sqplusb.png 


android/BOINC/res/drawable-mdpi/wirelessb.png   
  

Processed: block 807305 by 802414

[Debian Bug Tracking System]

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

> block 807305 by 802414
Bug #807305 [prospector] prospector: new upstream release
807305 was blocked by: 807306 795038
807305 was not blocking any bugs.
Added blocking bug(s) of 807305: 800788 and 802414
> thanks
Stopping processing here.

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

Bug#807097: [Python-modules-team] Bug#807097: python-django: Undeclared removal of previously supported features causes crashes

[Neil Williams]

reassign 807097 django-hijack
retitle 807097 incompatible with django1.9
found 807097 1.0.10-1
thanks

On Sun, 06 Dec 2015 20:21:17 +1100
Brian May  wrote:

> Sorry, accidentally sent private response by mistake. Resending.
> 
> Neil Williams  writes:
> 
> > Downgrading to 1.8 in testing fixes the problem, so if this isn't
> > the root cause, something else in 1.9 is producing a misleading
> > traceback. There's no reference to add-to-builtins in the
> > lava-server code that I can find.  
> 
> django-compat 1.0.7 has:
> 
> try:
> from django.template.base import add_to_builtins
> except ImportError:  # Django < 1.8
> from django.template import add_to_builtins
> 
> So looks like Django 1.8 does have it, but it moved. Which perhaps
> should have been a warning that maybe this was a private symbol not
> intended for apps to use.
> 
> 
> django-compat 1.0.8 has in the release notes:
> 
> add_to_builtins was removed for Django 1.9, still available for
> Django < 1.9
> 
> The relevant code is now:
> 
> if django.VERSION < (1, 8):
> from django.template import add_to_builtins
> elif django.VERSION < (1, 9):
> from django.template.base import add_to_builtins
> else:
> pass  # Removed in 1.9. Use template settings instead
> 
> 
> I don't know what version of django-compat you have, however I think
> it must be < 1.0.8
> 
> From your stack trace it would appear that the calling application -
> django-hijack - doesn't actually use add_to_builtins, however it uses
> the file from django-compat that tries to import the symbol anyway.

ARRRGGHHH! OK, that looks like hijack should test the import more
carefully to identify the right support.
 
> Looks like this should be fixed with django-compat 1.0.8
> 
> As far as I can tell, django-compat isn't packaged for Debian.

The binary is python-django-compat.

https://tracker.debian.org/pkg/django-compat

> It looks like the latest release of django-hijack 2.0.0 requires
> django-compat >= 1.0.8

Many thanks for this, Brian. I had indeed misinterpreted that traceback
- and there was another database issue hiding behind the scenes which is
now in review upstream as well. I now have lava-server working again
with python-django 1.9-1 - and unit tests passing - but only if
python-django-hijack is not installed alongside django1.9.

Re-assigning to django-hijack. Django1.9 is revealing a bug in
django-hijack - so I'll add a Conflicts on django-hijack (<= 1.0.10-1)
to the lava-server package.

Sorry about this, I hadn't spotted hijack in the traceback from the
unit tests and it didn't make sense initially that this would be the
problem with the from django.template import Origin,
TemplateDoesNotExist traceback.

-- 


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



pgpqYm1KOIuhF.pgp
Description: OpenPGP digital signature

Processed: Re: [Python-modules-team] Bug#807097: python-django: Undeclared removal of previously supported features causes crashes

[Debian Bug Tracking System]

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

> reassign 807097 django-hijack
Bug #807097 [python-django] python-django: Undeclared removal of previously 
supported features causes crashes
Bug reassigned from package 'python-django' to 'django-hijack'.
No longer marked as found in versions python-django/1.9-1.
Ignoring request to alter fixed versions of bug #807097 to the same values 
previously set
> retitle 807097 incompatible with django1.9
Bug #807097 [django-hijack] python-django: Undeclared removal of previously 
supported features causes crashes
Changed Bug title to 'incompatible with django1.9' from 'python-django: 
Undeclared removal of previously supported features causes crashes'
> found 807097 1.0.10-1
Bug #807097 [django-hijack] incompatible with django1.9
There is no source info for the package 'django-hijack' at version '1.0.10-1' 
with architecture ''
Unable to make a source version for version '1.0.10-1'
Marked as found in versions 1.0.10-1.
> thanks
Stopping processing here.

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

Processed: Re: Processed (with 1 error): Re: Processed (with 1 error): moodle #747084 #80731 must not be in jessie without proper long term support / future of Moodle in Debian stable/unstable

[Debian Bug Tracking System]

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

> reassign 807317 moodle
Bug #807317 [src:moodle] moodle: future of Moodle in Debian stable/unstable
Bug reassigned from package 'src:moodle' to 'moodle'.
No longer marked as found in versions moodle/2.6.3-1.
Ignoring request to alter fixed versions of bug #807317 to the same values 
previously set
> forcemerge 747084 807317
Bug #747084 [moodle] must not be in jessie without proper long term support
Bug #807317 [moodle] moodle: future of Moodle in Debian stable/unstable
Marked as found in versions moodle/2.6.2-1.
Merged 747084 807317
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Processed (with 1 error): moodle #747084 #80731 must not be in jessie without proper long term support / future of Moodle in Debian stable/unstable

[Debian Bug Tracking System]

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

> forcemerge 747084 807317
Bug #747084 [moodle] must not be in jessie without proper long term support
Unable to merge bugs because:
package of #807317 is 'src:moodle' not 'moodle'
Failed to forcibly merge 747084: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#754565: marked as done (Non free icc profile)

[Debian Bug Tracking System]

Your message dated Mon, 7 Dec 2015 12:34:24 +0100
with message-id <20151207113424.gm21...@dijkstra.uvt.nl>
and subject line Re: Bug #754565: moodle: Non free icc profile
has caused the Debian Bug report #754565,
regarding Non free icc profile
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.)


-- 
754565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:moodle
version:2.6.3-1
severity: serious
user: lintian.debian.org
usertag: license-problem-md5sum-non-free-file

Hi,

Your package include a non free file:
lib/tcpdf/include/sRGB.icc usual name is sRGB_IEC61966-2-1_black_scaled.icc. 

Does not allow modification See also 
https://packages.debian.org/sid/icc-profiles.

Please remove this file from your package.

Bastien
--- End Message ---
--- Begin Message ---
version: 2.7.2+dfsg-3

Hi,

Bastien, thanks for reporting this issue.  It was fixed in version
2.7.2+dfsg-3, Jan 2015:

  * Remove lib/tcpdf/include/sRGB.icc from upstream source since it does
not allow modification (usually known as
sRGB_IEC61966-2-1_black_scaled.icc).  FWIW: this file was not installed
by the Moodle 2.6.3 Debian package.

Bye,

Joost



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

Processed (with 1 error): moodle #747084 #80731 must not be in jessie without proper long term support / future of Moodle in Debian stable/unstable

[Debian Bug Tracking System]

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

> forcemerge 747084 80731
Bug #747084 [moodle] must not be in jessie without proper long term support
Unable to merge bugs because:
package of #80731 is 'apt' not 'moodle'
Failed to forcibly merge 747084: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: Re: Bug#803477: petsc: FTBFS against mpich

[Debian Bug Tracking System]

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

> block 803477 by 807318
Bug #803477 [src:petsc] petsc: FTBFS against mpich
803477 was not blocked by any bugs.
803477 was blocking: 800556
Added blocking bug(s) of 803477: 807318
> thanks
Stopping processing here.

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

Bug#803477: petsc: FTBFS against mpich

[Drew Parsons]

block 803477 807318
thanks

Testing the petsc build on s390x yields this error

 #  error 'Please use the same version of GCC and g++ for compiling MPICH and 
user MPI programs'

The error comes from /usr/include/mpich/mpicxx.h:

#ifdef __GNUC__ 
# if __GNUC__ >= 5 
#  if __GNUC_MINOR__ > 2 && 2 == 2 
#  error 'Please use the same version of GCC and g++ for compiling MPICH and 
user MPI programs'
#  endif
# endif 
#endif


So mpich on s390x was built with gcc 5.2.  But current gcc used by 
/usr/bin/mpicc.mpich is 5.3.


Looks like mpich needs to be rebuilt on s390x.  I've flagged this in bug#807318


Drew.

Bug#807318: libmpich-dev: should add Depends: to match hard-wired gcc dependency in mpicxx.h

[Drew Parsons]

Package: libmpich-dev
Version: 3.1-6
Severity: grave
Justification: renders package unusable

/usr/include/mpich/mpicxx.h has a hardwired dependency on the gcc used
to build mpich (gcc 5.2):

#ifdef __GNUC__ 
# if __GNUC__ >= 5 
#  if __GNUC_MINOR__ > 2 && 2 == 2 
#  error 'Please use the same version of GCC and g++ for compiling MPICH and 
user MPI programs'
#  endif
# endif 
#endif

But the current gcc (on s390x) is 5.3.  So an error is thrown when
building client programs (cf. Bug#803477), making mpich mostly
unusable on this architecture. 


libmpich-dev has a dependency on gcc.  But because the version in
mpicxx.h has been hardwired like this, I think that means libmpich-dev
should have a versioned Depends: gcc (<=4:5.2), Conflicts: gcc (>4:5.2)

In any case, mpich needs to be rebuilt, on s390x at least, to
update the gcc dependency in mpicxx.h.


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

Processed: moodle #754565 clone / retitle

[Debian Bug Tracking System]

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

> clone 754565 -1
Bug #754565 [src:moodle] Non free icc profile
Bug 754565 cloned as bug 807317
> retitle -1 moodle: future of Moodle in Debian stable/unstable
Bug #807317 [src:moodle] Non free icc profile
Changed Bug title to 'moodle: future of Moodle in Debian stable/unstable' from 
'Non free icc profile'
> thanks
Stopping processing here.

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

Bug#782361: netgen crashes on launch

[the2nd]

Hi,

i got netgen working (on Ubuntu 15.10) with the following steps:

apt-get install python3.4-dev libfreeimage3 libgl2ps0 libnglib-4.9.13 
liboce-foundation8 liboce-modeling8 liboce-ocaf-lite8 liboce-ocaf8 
liboce-visualization8 libpython-all-dev libtcl8.5 libtk8.5 libxss-dev 
libxt-dev python-all tcl-dev tcl8.6-dev tix-dev tk-dev tk8.6-dev 
x11proto-scrnsaver-dev mesa-common-dev libglu1-mesa-dev libxmu-dev


tar xvfzp Togl-1.7.tar.gz
cd Togl-1.7/
./configure
make
make install
echo "/usr/lib/Togl1.7/" > /etc/ld.so.conf.d/libTogl.conf
ldconfig
cd ..

tar xvfzp netgen-6.0-beta.tar.gz
cd netgen-6.0-beta/
./configure --with-togl=/usr/lib/Togl1.7/
make -j 3
make install

export NETGENDIR="/opt/netgen/bin"
netgen

I guess the important part is libTogl. After this commands netgen works. 
Both, the old and and the beta version.


Hope this helps someone.

regards
the2nd

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 807040 xserver-xorg-video-nouveau
Bug #807040 [general] general: System hangs and then restarts (kernel panic)
Bug reassigned from package 'general' to 'xserver-xorg-video-nouveau'.
Ignoring request to alter found versions of bug #807040 to the same values 
previously set
Ignoring request to alter fixed versions of bug #807040 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#787271: Bug #787271: moodle: dpkg-source fails to extract old-old-stable version of moodle

[Joost van Baal-Ilić]

Hi,

Thanks for reporting this issue.

I am not quite sure how to deal with this bug.

Maybe we should do nothing: Debian ships moodle only in
squeeze/oldoldstable and in sid/unstable.  Moodle is Unsupported in squeeze-lts,
see e.g. https://security-tracker.debian.org/tracker/CVE-2015-5342.  See
https://security-tracker.debian.org/tracker/source-package/moodle for what
would need to be done to support moodle in oldoldstable...

If it is sane to invest time in this; the slightly related fix at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753219#10 might be helpful.

Bye,

Joost




signature.asc
Description: Digital signature

Bug#807168: debian-installer-netboot-images: required resources not declared as build-dependencies (fetches via network)

[Jonas Smedegaard]

Quoting Didier 'OdyX' Raboud (2015-12-07 12:52:26)
> Control: tags -1 +wontfix
> 
> Le dimanche, 6 décembre 2015, 18.02:48 Jonas Smedegaard a écrit :
>> debian-installer-netboot-images source package is less than 6k in 
>> size. Clearly the main part of the resulting binary packages come 
>> from fetching resources over the network (apparently using wget). 
>> Debian Policy includes the following in §4.2:
>>> If build-time dependencies are specified, it must be possible to 
>>> build the package and produce working binaries on a system with only 
>>> essential and build-essential packages installed and also those 
>>> required to satisfy the build-time relationships (including any 
>>> implied relationships).
>>
>> I can only interpret above as disallowing fetching resources over the 
>> network using wget.
>
> d-i-n-i does (it's own) trust-path checking upon download, and it's 
> doing so because there's (currently) no way to have these files local 
> through Build-Depends.
>
> The specificity of the resulting packages is that they are arch-all 
> while containing arch-specific files. Their value comes from the fact 
> that you can install netboot images for all Debian architectures 
> (through arch:all packages) on any Debian architecture, without having 
> to add add these archs through multiarch.
>
> So the alternative would be to build these arch:all packages in the 
> debian-installer build-arch target, but that wouldn't pass the 
> incoming processing, as far as I know, as dak currently considers that 
> there will be only one arch:all changes file per source.
>
> Now talkin' crazy; we could also (ab)use byhand processing to produce 
> these packages on the archive side; but using the archive to produce 
> packages isn't really something we want to dive into.

Thanks for clarifying.


> So, the situation is known to not be Policy-compliant, but at least 
> there's trust-path checking. In this specific case, I value the 
> existance of these packages in their current form higher than Policy- 
> compliance, thereby tagging +wontfix. But I'm open to ideas!
>
> What would you propose?

Seems to me the underlying issue is that those parts fetched with wget 
is not provided in any binary package.  Does that sound correct to you?

I have filed bug#807312 about that, and marked it as blocking this one.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: block 807168 with 807312

[Debian Bug Tracking System]

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

> block 807168 with 807312
Bug #807168 [src:debian-installer-netboot-images] 
debian-installer-netboot-images: required resources not declared as 
build-dependencies (fetches via network)
807168 was not blocked by any bugs.
807168 was not blocking any bugs.
Added blocking bug(s) of 807168: 807312
> thanks
Stopping processing here.

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

Bug#807266: [php-maint] Bug#807266: FTBFS on stretch

[Ondřej Surý]

Control: severity -1 minor

I will fix that, but there are no real build failures in Debian, so I
don't see a reason for severity: serious here

O.

On Sun, Dec 6, 2015, at 22:03, Mateusz Łukasik wrote:
> Package: src:php7.0
> Version: 7.0.0-1
> Severity: serious
> Tags: patch, stretch
> 
> Dear Maintainer,
> 
> php7.0 is fail to build on testing because libsystemd-daemon-dev not 
> exists in stretch repository, it should be replaced by libsystemd-dev in 
> B-D. See my patch for that.
> 
> 
> Mateusz
> ___
> pkg-php-maint mailing list
> pkg-php-ma...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint
> Email had 1 attachment:
> + php7.0_7.0.0-1.1.debdiff
>   1k (text/plain)


-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server

Bug#797793: samtools update seems to breaks even more tests

[Andreas Tille]

Hi Afif,

On Sun, Dec 06, 2015 at 01:41:43PM -0800, Afif Elghraoui wrote:
> > I sent an email around the same time as yours announcing the patch is in
> > git. I didn't realize this was the central issue of the bug report. If
> > that's the case, I think you should just add the "Closes..." statement
> > to the changelog. :)
> > 
> 
> Yes, this isn't the central issue of the bug report, but we are now back
> to the original status, but there are at least no additional test
> failures on i386 than what was originally reported.

Hmmm, I have seen commit 7c93b9c0d42c415ef3296e6ee4a7d61b6fc34cb8 but I
remain with failures even on amd64. :-(


...
I: VER=0.6.1p1
python2.7 test/test.py
Doctest of tss.rst:
**
File "../doc/tss.rst", line 41, in tss.rst
Failed example:
for almnt in bamfile:
   if almnt.aligned:
  coverage[ almnt.iv ] += 1
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/doctest.py", line 1315, in __run
compileflags, 1) in test.globs
  File "", line 1, in 
for almnt in bamfile:
  File "/build/htseq-0.6.1p1/build/lib.linux-x86_64-2.7/HTSeq/__init__.py", 
line 943, in __iter__
sf = pysam.AlignmentFile(self.filename, "rb")
AttributeError: 'module' object has no attribute 'AlignmentFile'
**
File "../doc/tss.rst", line 211, in tss.rst
Failed example:
for almnt in sortedbamfile[ window ]:
print almnt   #doctest:+ELLIPSIS +NORMALIZE_WHITESPACE
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/doctest.py", line 1315, in __run
compileflags, 1) in test.globs
  File "", line 1, in 
for almnt in sortedbamfile[ window ]:
  File "/build/htseq-0.6.1p1/build/lib.linux-x86_64-2.7/HTSeq/__init__.py", 
line 975, in __getitem__
self.sf = pysam.AlignmentFile( self.filename, "rb" )
AttributeError: 'module' object has no attribute 'AlignmentFile'
**
File "../doc/tss.rst", line 220, in tss.rst
Failed example:
almnt.iv.length = fragmentsize
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/doctest.py", line 1315, in __run
compileflags, 1) in test.globs
  File "", line 1, in 
almnt.iv.length = fragmentsize
NameError: name 'almnt' is not defined
...
**
File "../doc/tss.rst", line 331, in tss.rst
Failed example:
almnt.iv.length = fragmentsize
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/doctest.py", line 1315, in __run
compileflags, 1) in test.globs
  File "", line 1, in 
almnt.iv.length = fragmentsize
NameError: name 'almnt' is not defined
**
File "../doc/tss.rst", line 332, in tss.rst
Failed example:
almnt
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/doctest.py", line 1315, in __run
compileflags, 1) in test.globs
  File "", line 1, in 
almnt
NameError: name 'almnt' is not defined
**
1 items had failures:
  11 of  37 in tss.rst
***Test Failed*** 11 failures.
11 of 37 tests failed.

Doctest of overview.rst:
All 0 tests passed.

Doctest of tour.rst:
**
File "../doc/tour.rst", line 189, in tour.rst
Failed example:
for a in itertools.islice( bam_reader, 5 ):  # printing first 5 reads
   print a
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python2.7/doctest.py", line 1315, in __run
compileflags, 1) in test.globs
  File "", line 1, in 
for a in itertools.islice( bam_reader, 5 ):  # printing first 5 reads
  File "/build/htseq-0.6.1p1/build/lib.linux-x86_64-2.7/HTSeq/__init__.py", 
line 943, in __iter__
sf = pysam.AlignmentFile(self.filename, "rb")
AttributeError: 'module' object has no attribute 'AlignmentFile'
**
1 items had failures:
   1 of  80 in tour.rst
***Test Failed*** 1 failures.
1 of 80 tests failed.


Strange that you can not reproduce this.

Kind regards

Andreas. 

-- 
http://fam-tille.de

Processed: Re: [php-maint] Bug#807266: FTBFS on stretch

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #807266 [src:php7.0] FTBFS on stretch
Severity set to 'minor' from 'serious'

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

Bug#736800: marked as done ([src:moodle] Sourceless flash file)

[Debian Bug Tracking System]

Your message dated Mon, 7 Dec 2015 09:32:06 +0100
with message-id <20151207083206.gi21...@dijkstra.uvt.nl>
and subject line Bug: #736800 [src:moodle] Sourceless flash file: done
has caused the Debian Bug report #736800,
regarding [src:moodle] Sourceless flash file
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.)


-- 
736800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:moodle
Version:  2.5.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: source-contains-prebuilt-flash-object
X-Debbugs-CC: ftpmas...@debian.org

moodle 2.5.4-1 (source)

lib/flowplayer/flowplayer-3.2.16.swf
lib/flowplayer/flowplayer.audio-3.2.10.swf
lib/flowplayer/flowplayer.controls-3.2.15.swf
webservice/amf/testclient/AMFTester.swf

Please avoid flash particularly sourceless. 

Bastien
--- End Message ---
--- Begin Message ---
version: 2.7.2-2


Since moodle (2.7.2-2), November 2014, debian/source/include-binaries
includes

 debian/missing-sources/flash-release_3_2_18.tar.gz
 debian/missing-sources/flash-release_3_2_16.tar.gz

: we do ship the missing sources.  FWIW, the binary moodle .deb does
not install the flash player.

This fixes the problem at the Debian side.  The problem at upstream
is tracked in https://tracker.moodle.org/browse/MDL-44093.

Thanks, Bye,

Joost



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

Processed: forcibly merging 802618 807015

[Debian Bug Tracking System]

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

> forcemerge 802618 807015
Bug #802618 {Done: Julien Cristau } [xserver-xorg-core] 
keyboard/mouse support broken - mising dep on libpam-systemd?
Bug #807015 [xserver-xorg-core] xinit: startx freezes, mouse and keyboard don't 
work
Severity set to 'serious' from 'grave'
Marked Bug as done
Marked as fixed in versions xorg-server/2:1.17.3-1.
Merged 802618 807015
> thanks
Stopping processing here.

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

Bug#807020: ghc: FTBFS on armel: selected processor does not support `strd r0, r1, [r7, #64]' in ARM mode

[Joachim Breitner]

Hi,

this is unfortunate, but known. GHC (and hence all of Haskell) will be
removed from the archive soonish.

See  https://lists.debian.org/debian-arm/2015/11/msg00010.html and
https://lists.debian.org/debian-arm/2015/12/msg00020.html

Greetings,
Joachim

Am Freitag, den 04.12.2015, 11:14 +0100 schrieb Emilio Pozuelo Monfort:
> Source: ghc
> Version: 7.10.3-2
> Severity: serious
> 
> Your package failed to build on armel:
> 
> "inplace/bin/ghc-stage1" -static  -H32m -O -lffi -optl-pthread -optl-
> B/usr/bin/ld.gold -Iincludes -Iincludes/dist -Iincludes/dist-
> derivedconstants/header -Iincludes/dist-ghcconstants/header -Irts
> -Irts/dist/build -DCOMPILING_RTS -this-package-key rts -dcmm-
> lint  -i -irts -irts/dist/build -irts/dist/build/autogen
> -Irts/dist/build -Irts/dist/build/autogen   -O2-c
> rts/StgStartup.cmm -o rts/dist/build/StgStartup.o
> /tmp/ghc074d_0/ghc_7.s: Assembler messages:
> 
> /tmp/ghc074d_0/ghc_7.s:96:0:
>  Error: selected processor does not support `ldrd r0,r1,[r3,#64]'
> in ARM mode
> 
> /tmp/ghc074d_0/ghc_7.s:99:0:
>  Error: selected processor does not support `strd r0,r1,[r3,#64]'
> in ARM mode
> 
> /tmp/ghc074d_0/ghc_7.s:210:0:
>  Error: selected processor does not support `ldrd r0,r1,[r7,#64]'
> in ARM mode
> 
> /tmp/ghc074d_0/ghc_7.s:214:0:
>  Error: selected processor does not support `strd r0,r1,[r7,#64]'
> in ARM mode
> rts/ghc.mk:236: recipe for target 'rts/dist/build/StgStartup.o'
> failed
> 
> Full log at:
> 
> https://buildd.debian.org/status/fetch.php?pkg=ghc&arch=armel&ver=7.1
> 0.3-2&stamp=1449207555
> 
> Emilio
> 
> ___
> Pkg-haskell-maintainers mailing list
> pkg-haskell-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-haskell-m
> aintainers
> 
-- 
Joachim "nomeata" Breitner
Debian Developer
  nome...@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F
  JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata



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