Bug#798170: Almost done

[Michael Hanke]

FTR: I was able to build the latest upstream release (2.0.0) against the
QWT package (6.1) in experimental. However, a linking problem (get's
linked against Qt4 and Qt5) causes the main GUI to segfault. I contacted
upstream to get this solved. Will upload to experimental once this is
done.

Processed (with 1 error): Re: untouched Django 1.7 bugs

[Debian Bug Tracking System]

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

> # This package hasn't had an upstream update since 2009, is orphaned,
> # and probably isn't Django 1.7 compatible...
> severity 755600 grave
Bug #755600 [src:djagios] djagios: Please ensure it works with Django 1.7
Severity set to 'grave' from 'important'
> thanks a lot
Unknown command or malformed arguments to command.
> --
Stopping processing here.

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

Bug#809707: sprockets 3.3 cannot find favico.js

[Pirate Praveen]

package: ruby-sprockets
version: 3.3.0-1
severity: grave
justification: fails to find assets previously found by 2.12

Sprockets::FileNotFound: couldn't find file 'favico.js' with type
'application/javascript'

It was noticed by autopkgtest in ruby-rails-assets-favico.js and
confirmed by checking gem installed rails-assets-favico.js from
rails-assets.org

rails new foo
cd foo

cat >> app/assets/javascripts/application.js <> Gemfile 

Bug#798438: marked as done (procps: FTBFS: Makefile:526: recipe for target 'check-DEJAGNU' failed)

[Debian Bug Tracking System]

Your message dated Sun, 03 Jan 2016 06:34:13 +
with message-id 
and subject line Bug#798438: fixed in procps 2:3.3.11-3
has caused the Debian Bug report #798438,
regarding procps: FTBFS: Makefile:526: recipe for target 'check-DEJAGNU' 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.)


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

procps fails to build from source in unstable/amd64:

  [..]

  Using /usr/share/dejagnu/baseboards/unix.exp as board description file
  for target.
  Using /usr/share/dejagnu/config/unix.exp as generic interface file for
  target.
  Using ./config/unix.exp as tool-and-target-specific interface file.
  Running ./vmstat.test/vmstat.exp ...
  
=== vmstat Summary ===
  
  # of expected passes5
  # of unsupported tests  1
  /tmp/buildd/procps-3.3.10/vmstat version 3.3.10
  
  WARNING: Couldn't find tool init file
  Test Run By pbuilder1 on Sun Sep  6 03:45:05 2015
  Native configuration is x86_64-pc-linux-gnu
  
=== w tests ===
  
  Schedule of variations:
  unix
  
  Running target unix
  Using /usr/share/dejagnu/baseboards/unix.exp as board description file
  for target.
  Using /usr/share/dejagnu/config/unix.exp as generic interface file for
  target.
  Using ./config/unix.exp as tool-and-target-specific interface file.
  Running ./w.test/w.exp ...
  
=== w Summary ===
  
  # of expected passes7
  /tmp/buildd/procps-3.3.10/w version 3.3.10
  
  Makefile:526: recipe for target 'check-DEJAGNU' failed
  make[4]: *** [check-DEJAGNU] Error 1
  make[4]: Leaving directory '/tmp/buildd/procps-3.3.10/testsuite'
  Makefile:598: recipe for target 'check-am' failed
  make[3]: *** [check-am] Error 2
  make[3]: Leaving directory '/tmp/buildd/procps-3.3.10/testsuite'
  Makefile:1132: recipe for target 'check-recursive' failed
  make[2]: *** [check-recursive] Error 1
  make[2]: Leaving directory '/tmp/buildd/procps-3.3.10'
  Makefile:1423: recipe for target 'check' failed
  make[1]: *** [check] Error 2
  make[1]: Leaving directory '/tmp/buildd/procps-3.3.10'
  dh_auto_test: make -j1 check returned exit code 2
  debian/rules:24: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/procps_3.3.10-4.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sun Sep  6 03:43:15 GMT+12 2015
I: pbuilder-time-stamp: 1441554195
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
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.20120115), dh-exec (>= 0.3), libncurses5-dev, 
libncursesw5-dev, dejagnu, libnuma-dev, dh-autoreconf, pkg-config, 
libsystemd-dev (>= 209)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20259 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 dh-exec (>= 0.3); however:
  Package dh-ex

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

[Brian May]

Alexander Wirt  writes:

>> This should be integrated in the backports.d.o repositories.
> Backports is not for fixing bugs in stable.

I think there is a misunderstanding here.

This is not about fixing unison in stable. "unison" 2.40.102-2 in stable
works fine. It is not broken. There is nothing to fix. It works fine
when talking to other stable servers.
 
The package called "unison2.40.102" version 2.40.102-3+b1 in testing and
unstable is broken. This broken package is not in stable. If it can't
get fixed, it probably should get removed.

The most recent "unison" package, version 2.48.3-1 in testing and
unstable is not broken. Unfortunately it is not compatable with the
version in stable.

This is about letting stable users use the latest bleeding each version
so that they can have compatability with unison 2.48 in unstable which
is not broken. Which I believe is inline with what backports is for.
-- 
Brian May 

Bug#805688: marked as done (python-django-mptt: FTBFS: ImportError: Failed to import test module: tests.myapp.tests)

[Debian Bug Tracking System]

Your message dated Sun, 03 Jan 2016 04:50:40 +
with message-id 
and subject line Bug#805688: fixed in python-django-mptt 0.8.0-1
has caused the Debian Bug report #805688,
regarding python-django-mptt: FTBFS: ImportError: Failed to import test module: 
tests.myapp.tests
to be marked as done.

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

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


-- 
805688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-mptt
Version: 0.7.3-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:

I: pybuild base:184: cd /python-django-mptt-0.7.3/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m unittest discover -v 
tests.myapp.tests (unittest.loader.ModuleImportFailure) ... ERROR

==
ERROR: tests.myapp.tests (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: tests.myapp.tests
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 "tests/myapp/tests.py", line 17, in 
from django.contrib.auth.models import Group, User
  File "/usr/lib/python2.7/dist-packages/django/contrib/auth/__init__.py", line 
7, in 
from django.middleware.csrf import rotate_token
  File "/usr/lib/python2.7/dist-packages/django/middleware/csrf.py", line 14, 
in 
from django.utils.cache import patch_vary_headers
  File "/usr/lib/python2.7/dist-packages/django/utils/cache.py", line 26, in 

from django.core.cache import caches
  File "/usr/lib/python2.7/dist-packages/django/core/cache/__init__.py", line 
34, in 
if DEFAULT_CACHE_ALIAS not in settings.CACHES:
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 48, in 
__getattr__
self._setup(name)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 42, in 
_setup
% (desc, ENVIRONMENT_VARIABLE))
ImproperlyConfigured: Requested setting CACHES, but settings are not 
configured. You must either define the environment variable 
DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.


--
Ran 1 test in 0.000s

FAILED (errors=1)
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/python-django-mptt-0.7.3/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest 
discover -v 

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-django-mptt
Source-Version: 0.8.0-1

We believe that the bug you reported is fixed in the latest version of
python-django-mptt, 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.
Brian May  (supplier of updated python-django-mptt 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, 03 Jan 2016 15:22:59 +1100
Source: python-django-mptt
Binary: python-django-mptt python3-django-mptt python-django-mptt-doc
Architecture: source all
Version: 0.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Brian May 
Description:
 python-django-mptt - Modified Preorder Tree Traversal Django application
 python-django-mptt-doc - Modified Preorder Tree Traversal Django application
 python3-django-mptt - Modified Preorder Tree Traversal Django application
Closes: 805688
Changes:
 python-django-mptt (0.8.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fixes FTBFS error. Closes:

Bug#805688: marked as pending

[Brian May]

tag 805688 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/python-django-mptt.git;a=commitdiff;h=7c58480

---
commit 7c58480ddf19e9b8d00afbd4347993bbec89124b
Author: Brian May 
Date:   Sun Jan 3 15:36:43 2016 +1100

Release version 0.8.0-1

diff --git a/debian/changelog b/debian/changelog
index ff98304..b13114a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-django-mptt (0.8.0-1) unstable; urgency=medium
+
+  * New upstream release.
+  * Fixes FTBFS error. Closes: #805688.
+  * Maintainer not responding to emails. Setting maintainer to DPMT.
+
+ -- Brian May   Sun, 03 Jan 2016 15:22:59 +1100
+
 python-django-mptt (0.7.4-1) unstable; urgency=medium
 
   * New upstream release.

Processed: Bug#805688 marked as pending

[Debian Bug Tracking System]

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

> tag 805688 pending
Bug #805688 [src:python-django-mptt] python-django-mptt: FTBFS: ImportError: 
Failed to import test module: tests.myapp.tests
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#806366: marked as done (python-passlib: FTBFS with Django 1.9)

[Debian Bug Tracking System]

Your message dated Sun, 03 Jan 2016 04:39:21 +
with message-id 
and subject line Bug#806366: fixed in python-passlib 1.6.5-4
has caused the Debian Bug report #806366,
regarding python-passlib: FTBFS with Django 1.9
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.)


-- 
806366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-passlib
Version: 1.6.5-3
Severity: important
User: python-dja...@packages.debian.org
Usertags: django19 django19-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest release candidate, I noticed that python-passlib
FTBFS with 1.9~rc2.

Please update your package to work with Django 1.9 as I will uploading
it to unstable once it is released in early December 2015 (and at the
same time raising the severity of this bug to RC).

Typical issues include:

 * "django.utils.importlib" has been removed in favour of just
   "importlib"

 * Template builtins have been removed, removing
   "template.base.builtins", "django.template.base.add_to_builtins",
   etc. You can read more here:
   
https://chris-lamb.co.uk/posts/importerror-cannot-import-name-add_to_builtins-under-django-19

 * "django.forms.models.save_instance" has been removed:

   -
   
https://github.com/django/django/commit/8656cfc4e01332426e5e4b78c20a4e9ec443b293
   -
   
https://github.com/django/django/commit/b11564fd36587b1077bf7d77b62b7879cc08c382

 * "django.utils.unittest" has been removed in favour of just
   "unittest"


The full build log is attached.


Regards,

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


python-passlib_1.6.5-3_amd64.build.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-passlib
Source-Version: 1.6.5-4

We believe that the bug you reported is fixed in the latest version of
python-passlib, 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.
Brian May  (supplier of updated python-passlib 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, 03 Jan 2016 14:32:44 +1100
Source: python-passlib
Binary: python-passlib python3-passlib
Architecture: source all
Version: 1.6.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Brian May 
Description:
 python-passlib - comprehensive password hashing framework
 python3-passlib - comprehensive password hashing framework
Closes: 806366
Changes:
 python-passlib (1.6.5-4) unstable; urgency=medium
 .
   * Disable Django tests.
   * I believe none of the packages that depend on python-passlib use the
 Django stuff.
   * Can be reversed as soon as
 https://bitbucket.org/ecollins/passlib/issues/68/tests-fail-with-django-19
 is fixed.
   * Closes: #806366.
Checksums-Sha1:
 727620142d0fe78c794349ef0be649e738441c11 2184 python-passlib_1.6.5-4.dsc
 ec7a4d6270306fa61c46d63cc2467a0f8b691c4b 417044 
python-passlib_1.6.5.orig.tar.gz
 12c7d1aafd90a44c5e6084f9f5f6a90fd3615743 14144 
python-passlib_1.6.5-4.debian.tar.xz
 9a94cb5ebe07efaf768d145c4a2981a9d0863bdf 219118 python-passlib_1.6.5-4_all.deb
 3ed84f36039671a7794e019c5d65ea12567679a0 218390 python3-passlib_1.6.5-4_all.deb
Checksums-Sha256:
 ca8b73d607fd2c28a2ea9530f3ccde64e6d6bdbcef64ffb0c0cf68248f153c0e 2184 
python-passlib_1.6.5-4.dsc
 a83d34f53dc9b17aa42c9a35c3fbcc5120f3fcb07f7f8721ec45e6a27be347fc 417044 
python-passlib_1.6.5.orig.tar.gz
 e3ef9b9b049883853db9004885a48009413c4dd810766869c7399b180c9bf399 14144 
python-passlib_1.6.5-4.debian.tar.xz
 daef8728cf047b4d82000afe8b271470d0e91aef09514c0528fd3894097919d3 219118 
python-passlib_1.6.5-4_all.deb
 015029534cfd02aa557452bc739610d8198ef290428bc856087c524c5ace326f 218390 
python3-passlib_1.6.5-4_all.deb
Files:
 45742cf3116a97d3ae16f948ca20f446 2184 python extra python-passlib_1.6.5-4.dsc
 d2edd6c42cde136a538b48d90a06ad67 417044 python extra 
python-passlib_1.6.5.orig.tar.gz
 29f5184b3a87a43a60147f2bbc7eed75 14144 python extra 
python-passlib_1.6.5-4.debi

Bug#808527: marked as done (xpdf: FTBFS: XPDFViewer.cc: error: no matching function for call to ‘PSOutputDev::PSOutputDev)

[Debian Bug Tracking System]

Your message dated Sun, 03 Jan 2016 04:10:17 +
with message-id 
and subject line Bug#807087: fixed in xpdf 3.03-18
has caused the Debian Bug report #807087,
regarding xpdf: FTBFS: XPDFViewer.cc: error: no matching function for call to 
‘PSOutputDev::PSOutputDev
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.)


-- 
807087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xpdf
Version: 3.03-17
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

build/XPDFViewer.cc: In static member function ‘static void 
XPDFViewer::printPrintCbk(Widget, XtPointer, XtPointer)’:
build/XPDFViewer.cc:3718:68: error: no matching function for call to 
‘PSOutputDev::PSOutputDev(char*, PDFDoc*&, NULL, int&, int&, PSOutMode, int, 
int, GBool)’
   xpdfParams->getPSPaperHeight(), xpdfParams->getPSDuplex());
^
In file included from build/XPDFViewer.cc:49:0:
/usr/include/poppler/PSOutputDev.h:113:3: note: candidate: 
PSOutputDev::PSOutputDev(PSOutputFunc, void*, char*, PDFDoc*, const 
std::vector&, PSOutMode, int, int, GBool, GBool, int, int, int, int, 
GBool, GBool, PSOutCustomCodeCbk, void*)
   PSOutputDev(PSOutputFunc outputFuncA, void *outputStreamA,
   ^
/usr/include/poppler/PSOutputDev.h:113:3: note:   no known conversion for 
argument 1 from ‘char*’ to ‘PSOutputFunc {aka void (*)(void*, const char*, 
int)}’
/usr/include/poppler/PSOutputDev.h:98:3: note: candidate: 
PSOutputDev::PSOutputDev(const char*, PDFDoc*, char*, const std::vector&, 
PSOutMode, int, int, GBool, GBool, int, int, int, int, GBool, GBool, 
PSOutCustomCodeCbk, void*)
   PSOutputDev(const char *fileName, PDFDoc *docA,
   ^
/usr/include/poppler/PSOutputDev.h:98:3: note:   no known conversion for 
argument 4 from ‘int’ to ‘const std::vector&’
/usr/include/poppler/PSOutputDev.h:93:7: note: candidate: 
PSOutputDev::PSOutputDev(const PSOutputDev&)
 class PSOutputDev: public OutputDev {
   ^
/usr/include/poppler/PSOutputDev.h:93:7: note:   candidate expects 1 argument, 
9 provided
build/XPDFViewer.cc:3765:72: error: no matching function for call to 
‘PSOutputDev::PSOutputDev(char*, PDFDoc*&, NULL, int&, int&, PSOutMode, int, 
int, GBool)’
   xpdfParams->getPSPaperHeight(), xpdfParams->getPSDuplex());
^
In file included from build/XPDFViewer.cc:49:0:
/usr/include/poppler/PSOutputDev.h:113:3: note: candidate: 
PSOutputDev::PSOutputDev(PSOutputFunc, void*, char*, PDFDoc*, const 
std::vector&, PSOutMode, int, int, GBool, GBool, int, int, int, int, 
GBool, GBool, PSOutCustomCodeCbk, void*)
   PSOutputDev(PSOutputFunc outputFuncA, void *outputStreamA,
   ^
/usr/include/poppler/PSOutputDev.h:113:3: note:   no known conversion for 
argument 1 from ‘char*’ to ‘PSOutputFunc {aka void (*)(void*, const char*, 
int)}’
/usr/include/poppler/PSOutputDev.h:98:3: note: candidate: 
PSOutputDev::PSOutputDev(const char*, PDFDoc*, char*, const std::vector&, 
PSOutMode, int, int, GBool, GBool, int, int, int, int, GBool, GBool, 
PSOutCustomCodeCbk, void*)
   PSOutputDev(const char *fileName, PDFDoc *docA,
   ^
/usr/include/poppler/PSOutputDev.h:98:3: note:   no known conversion for 
argument 4 from ‘int’ to ‘const std::vector&’
/usr/include/poppler/PSOutputDev.h:93:7: note: candidate: 
PSOutputDev::PSOutputDev(const PSOutputDev&)
 class PSOutputDev: public OutputDev {
   ^
/usr/include/poppler/PSOutputDev.h:93:7: note:   candidate expects 1 argument, 
9 provided
: recipe for target 'build/XPDFViewer.o' failed
make[1]: *** [build/XPDFViewer.o] Error 1
make[1]: Leaving directory '/xpdf-3.03'
debian/rules:37: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

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

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

We believe that the bug you reported is fixed in the latest version of
xpdf, 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 bu

Bug#807087: marked as done (xpdf: FTBFS with Poppler 0.38.0)

[Debian Bug Tracking System]

Your message dated Sun, 03 Jan 2016 04:10:17 +
with message-id 
and subject line Bug#807087: fixed in xpdf 3.03-18
has caused the Debian Bug report #807087,
regarding xpdf: FTBFS with Poppler 0.38.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.)


-- 
807087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xpdf
Version: 3.03-17
Severity: important

Hi,

xpdf fails to build with Poppler 0.38.0, which is currently in
experimental and targeted for unstable; extract of build log is:


g++ -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2 -I/usr/include/poppler -I/usr/include/poppler/goo 
-I/usr/include/poppler/splash -Wno-write-strings -Wno-format-extra-args 
-DHAVE_DIRENT_H -DSYSTEM_XPDFRC=\"/etc/xpdf/xpdfrc\"  -c -o build/XPDFViewer.o 
build/XPDFViewer.cc
build/XPDFViewer.cc: In static member function 'static void 
XPDFViewer::printPrintCbk(Widget, XtPointer, XtPointer)':
build/XPDFViewer.cc:3718:68: error: no matching function for call to 
'PSOutputDev::PSOutputDev(char*, PDFDoc*&, NULL, int&, int&, PSOutMode, int, 
int, GBool)'
   xpdfParams->getPSPaperHeight(), xpdfParams->getPSDuplex());
^
In file included from build/XPDFViewer.cc:49:0:
/usr/include/poppler/PSOutputDev.h:113:3: note: candidate: 
PSOutputDev::PSOutputDev(PSOutputFunc, void*, char*, PDFDoc*, const 
std::vector&, PSOutMode, int, int, GBool, GBool, int, int, int, int, 
GBool, GBool, PSOutCustomCodeCbk, void*)
   PSOutputDev(PSOutputFunc outputFuncA, void *outputStreamA,
   ^
/usr/include/poppler/PSOutputDev.h:113:3: note:   no known conversion for 
argument 1 from 'char*' to 'PSOutputFunc {aka void (*)(void*, const char*, 
int)}'
/usr/include/poppler/PSOutputDev.h:98:3: note: candidate: 
PSOutputDev::PSOutputDev(const char*, PDFDoc*, char*, const std::vector&, 
PSOutMode, int, int, GBool, GBool, int, int, int, int, GBool, GBool, 
PSOutCustomCodeCbk, void*)
   PSOutputDev(const char *fileName, PDFDoc *docA,
   ^
/usr/include/poppler/PSOutputDev.h:98:3: note:   no known conversion for 
argument 4 from 'int' to 'const std::vector&'
/usr/include/poppler/PSOutputDev.h:93:7: note: candidate: 
PSOutputDev::PSOutputDev(const PSOutputDev&)
 class PSOutputDev: public OutputDev {
   ^
/usr/include/poppler/PSOutputDev.h:93:7: note:   candidate expects 1 argument, 
9 provided
build/XPDFViewer.cc:3765:72: error: no matching function for call to 
'PSOutputDev::PSOutputDev(char*, PDFDoc*&, NULL, int&, int&, PSOutMode, int, 
int, GBool)'
   xpdfParams->getPSPaperHeight(), xpdfParams->getPSDuplex());
^
In file included from build/XPDFViewer.cc:49:0:
/usr/include/poppler/PSOutputDev.h:113:3: note: candidate: 
PSOutputDev::PSOutputDev(PSOutputFunc, void*, char*, PDFDoc*, const 
std::vector&, PSOutMode, int, int, GBool, GBool, int, int, int, int, 
GBool, GBool, PSOutCustomCodeCbk, void*)
   PSOutputDev(PSOutputFunc outputFuncA, void *outputStreamA,
   ^
/usr/include/poppler/PSOutputDev.h:113:3: note:   no known conversion for 
argument 1 from 'char*' to 'PSOutputFunc {aka void (*)(void*, const char*, 
int)}'
/usr/include/poppler/PSOutputDev.h:98:3: note: candidate: 
PSOutputDev::PSOutputDev(const char*, PDFDoc*, char*, const std::vector&, 
PSOutMode, int, int, GBool, GBool, int, int, int, int, GBool, GBool, 
PSOutCustomCodeCbk, void*)
   PSOutputDev(const char *fileName, PDFDoc *docA,
   ^
/usr/include/poppler/PSOutputDev.h:98:3: note:   no known conversion for 
argument 4 from 'int' to 'const std::vector&'
/usr/include/poppler/PSOutputDev.h:93:7: note: candidate: 
PSOutputDev::PSOutputDev(const PSOutputDev&)
 class PSOutputDev: public OutputDev {
   ^
/usr/include/poppler/PSOutputDev.h:93:7: note:   candidate expects 1 argument, 
9 provided
: recipe for target 'build/XPDFViewer.o' failed


Thanks,
-- 
Pino
--- End Message ---
--- Begin Message ---
Source: xpdf
Source-Version: 3.03-18

We believe that the bug you reported is fixed in the latest version of
xpdf, 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.
Michael Gilbert  (supplier of updated 

Bug#809266: marked as done (doomsday: FTBFS: src/vector1.c:933:19: error: incompatible type for argument 2 of 'V3d_Set')

[Debian Bug Tracking System]

Your message dated Sun, 03 Jan 2016 03:52:49 +
with message-id 
and subject line Bug#809266: fixed in doomsday 1.15.7-1
has caused the Debian Bug report #809266,
regarding doomsday: FTBFS: src/vector1.c:933:19: error: incompatible type for 
argument 2 of 'V3d_Set'
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.)


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

doomsday fails to build from source in unstable/amd64:

  [..]

  src/vector1.c:933:19: error: incompatible type for argument 2 of 'V3d_Set'
   V3d_Set(dest, srcf[VX], srcf[VY], srcf[VZ]);
 ^
  src/vector1.c:885:6: note: expected 'vectorcompd_t {aka double}' but argument 
is of type 'const float *'
   void V3d_Set(pvec3d_t vec, vectorcompd_t x, vectorcompd_t y, vectorcompd_t z)
^
  src/vector1.c:933:29: error: incompatible type for argument 3 of 'V3d_Set'
   V3d_Set(dest, srcf[VX], srcf[VY], srcf[VZ]);
   ^
  src/vector1.c:885:6: note: expected 'vectorcompd_t {aka double}' but argument 
is of type 'const float *'
   void V3d_Set(pvec3d_t vec, vectorcompd_t x, vectorcompd_t y, vectorcompd_t z)
^
  src/vector1.c:933:39: error: incompatible type for argument 4 of 'V3d_Set'
   V3d_Set(dest, srcf[VX], srcf[VY], srcf[VZ]);
 ^
  src/vector1.c:885:6: note: expected 'vectorcompd_t {aka double}' but argument 
is of type 'const float *'
   void V3d_Set(pvec3d_t vec, vectorcompd_t x, vectorcompd_t y, vectorcompd_t z)
^
  src/vector1.c: In function 'V3d_Sum':
  src/vector1.c:945:25: error: invalid operands to binary + (have 'const double 
*' and 'const double *')
   dest[VX] = src1[VX] + src2[VX];
   ^
  src/vector1.c:946:25: error: invalid operands to binary + (have 'const double 
*' and 'const double *')
   dest[VY] = src1[VY] + src2[VY];
   ^
  src/vector1.c:947:25: error: invalid operands to binary + (have 'const double 
*' and 'const double *')
   dest[VZ] = src1[VZ] + src2[VZ];
   ^
  src/vector1.c: In function 'V3d_DotProduct':
  src/vector1.c:959:18: error: invalid operands to binary * (have 'const double 
*' and 'const double *')
   return a[VX] * b[VX] + a[VY] * b[VY] + a[VZ] * b[VZ];
^
  src/vector1.c:959:34: error: invalid operands to binary * (have 'const double 
*' and 'const double *')
   return a[VX] * b[VX] + a[VY] * b[VY] + a[VZ] * b[VZ];
^
  src/vector1.c:959:50: error: invalid operands to binary * (have 'const double 
*' and 'const double *')
   return a[VX] * b[VX] + a[VY] * b[VY] + a[VZ] * b[VZ];
^
  src/vector1.c: In function 'V3d_DotProductf':
  src/vector1.c:966:30: warning: passing argument 2 of 'V3d_DotProduct' from 
incompatible pointer type [-Wincompatible-pointer-types]
   return V3d_DotProduct(a, b);
^
  src/vector1.c:957:8: note: expected 'const double (*)[3]' but argument is of 
type 'vectorcompd_t * {aka double *}'
   double V3d_DotProduct(const_pvec3d_t a, const_pvec3d_t b)
  ^
  src/vector1.c: In function 'V3d_CrossProduct':
  src/vector1.c:971:25: error: invalid operands to binary * (have 'const double 
*' and 'const double *')
   dest[VX] = src1[VY] * src2[VZ] - src1[VZ] * src2[VY];
   ^
  src/vector1.c:971:47: error: invalid operands to binary * (have 'const double 
*' and 'const double *')
   dest[VX] = src1[VY] * src2[VZ] - src1[VZ] * src2[VY];
 ^
  src/vector1.c:972:25: error: invalid operands to binary * (have 'const double 
*' and 'const double *')
   dest[VY] = src1[VZ] * src2[VX] - src1[VX] * src2[VZ];
   ^
  src/vector1.c:972:47: error: invalid operands to binary * (have 'const double 
*' and 'const double *')
   dest[VY] = src1[VZ] * src2[VX] - src1[VX] * src2[VZ];
 ^
  src/vector1.c:973:25: error: invalid operands to binary * (have 'const double 
*' and 'const double *')
   dest[VZ] = src1[VX] * src2[VY] - src1[VY] * src2[VX];
   ^
  src/vector1.c

Bug#808209: amanda-common: Depends on virtual package "perl5" which will is gone with perl/5.22

[Dominic Hargreaves]

On Sat, Jan 02, 2016 at 09:56:53PM +, Jose M Calhariz wrote:
> On Mon, Dec 21, 2015 at 12:03:20PM +, Dominic Hargreaves wrote:
> > On Sun, Dec 20, 2015 at 07:43:40PM +0100, gregor herrmann wrote:
> > > Control: tag -1 + pending
> > > 
> > > On Thu, 17 Dec 2015 10:28:58 +, Dominic Hargreaves wrote:
> > > 
> > > > The perl 5.22 transition just started (see
> > > > https://lists.debian.org/debian-devel-announce/2015/12/msg5.html)
> > > > and we seem to have missed that this package depends on the deprecated
> > > > virtual package "perl5" like some other packages did.
> > > 
> > > Looks like the maintainer has a fix ready and is looking for a
> > > sponsor:
> > > 
> > > http://blog.calhariz.com/post/2015/12/20/Preview-of-amanda-3.3.7p1-1
> > 
> > Hi Jose,
> > 
> > In terms of an immediate uninstallability, would you be happy to have
> > an NMU with just the perl5 fix, until the new package can be reviewed and
> > sponsored? I'd be happy to do the former.
> 
> Are you still available to review a new version of amanda?  I have
> acknowledge the NMU work and publish the last changes in collab-maint.

Hi Jose,

I'm afraid not - my interest in amanda was simply to make good the
late breakage caused by the perl transition (thanks to gregor for doing
that), and I won't have a chance to review the new release any time soon.

Best wishes,
Dominic.

Bug#806326: marked as done (apache2: trying to overwrite '/etc/apache2/mods-available/macro.load', which is also in package libapache2-mod-macro 1.1.11-2)

[Debian Bug Tracking System]

Your message dated Sun, 03 Jan 2016 00:17:09 +
with message-id 
and subject line Bug#806326: fixed in apache2 2.4.10-10+deb8u4
has caused the Debian Bug report #806326,
regarding apache2: trying to overwrite 
'/etc/apache2/mods-available/macro.load', which is also in package 
libapache2-mod-macro 1.1.11-2
to be marked as done.

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

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


-- 
806326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apache2
Severity: serious
Version: 2.4.10-10+deb8u3

Hi,

I'm quite surprised that I didn't notice the following (much) earlier:

When upgrading a box from Wheezy to Jessie, I ran into this file
conflict:

Unpacking apache2 (2.4.10-10+deb8u3) over (2.2.22-13+deb7u6) ...
dpkg: error processing archive 
/var/cache/apt/archives/apache2_2.4.10-10+deb8u3_amd64.deb (--unpack):
 trying to overwrite '/etc/apache2/mods-available/macro.load', which is also in 
package libapache2-mod-macro 1.1.11-2
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

Sounds like a missing Breaks/Replaces in the apache2 package in (at
least) Jessie.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.10-10+deb8u4

We believe that the bug you reported is fixed in the latest version of
apache2, 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.
Stefan Fritsch  (supplier of updated apache2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 Nov 2015 15:02:23 +0100
Source: apache2
Binary: apache2 apache2-data apache2-bin apache2-mpm-worker apache2-mpm-prefork 
apache2-mpm-event apache2-mpm-itk apache2.2-bin apache2.2-common 
libapache2-mod-proxy-html libapache2-mod-macro apache2-utils apache2-suexec 
apache2-suexec-pristine apache2-suexec-custom apache2-doc apache2-dev 
apache2-dbg
Architecture: source amd64 all
Version: 2.4.10-10+deb8u4
Distribution: jessie
Urgency: medium
Maintainer: Debian Apache Maintainers 
Changed-By: Stefan Fritsch 
Description:
 apache2- Apache HTTP Server
 apache2-bin - Apache HTTP Server (modules and other binary files)
 apache2-data - Apache HTTP Server (common files)
 apache2-dbg - Apache debugging symbols
 apache2-dev - Apache HTTP Server (development headers)
 apache2-doc - Apache HTTP Server (on-site documentation)
 apache2-mpm-event - transitional event MPM package for apache2
 apache2-mpm-itk - transitional itk MPM package for apache2
 apache2-mpm-prefork - transitional prefork MPM package for apache2
 apache2-mpm-worker - transitional worker MPM package for apache2
 apache2-suexec - transitional package for apache2-suexec-pristine
 apache2-suexec-custom - Apache HTTP Server configurable suexec program for 
mod_suexec
 apache2-suexec-pristine - Apache HTTP Server standard suexec program for 
mod_suexec
 apache2-utils - Apache HTTP Server (utility programs for web servers)
 apache2.2-bin - Transitional package for apache2-bin
 apache2.2-common - Transitional package for apache2
 libapache2-mod-macro - Transitional package for apache2-bin
 libapache2-mod-proxy-html - Transitional package for apache2-bin
Closes: 789914 791902 803177 803472 806326
Changes:
 apache2 (2.4.10-10+deb8u4) jessie; urgency=medium
 .
   * Add versioned replaces/breaks for libapache2-mod-macro to apache2,
 for the config files in /etc. Closes: #806326
   * Fix split-logfile to work with current perl. Closes: #803472
   * Fix tests on deferred mpm switch. Add special casing for mpm_itk,
 which is not an mpm anymore, despite the name. Closes: #789914
 Closes: #791902
   * Fix secondary-init-script to not source the main init script with 'set -e'.
 Closes: #803177
Checksums-Sha1:
 942b0

Bug#789914: marked as done (apache2: fails to install: ERROR: Module mpm_event is enabled - cannot proceed due to conflicts. It needs to be disabled first!)

[Debian Bug Tracking System]

Your message dated Sun, 03 Jan 2016 00:17:09 +
with message-id 
and subject line Bug#789914: fixed in apache2 2.4.10-10+deb8u4
has caused the Debian Bug report #789914,
regarding apache2: fails to install: ERROR: Module mpm_event is enabled - 
cannot proceed due to conflicts. It needs to be disabled first!
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.)


-- 
789914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apache2.2-common
Version: 2.4.12-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

This bug was triggered when installing (the dependencies of)
fusionforge-web 6.0.1-1 in a minimal piuparts chroot.

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

[...]
  Setting up apache2-bin (2.4.12-2) ...
  Setting up libapache2-mpm-itk (2.4.7-02-1.1) ...
  Package apache2 is not configured yet. Will defer actions by package 
libapache2-mpm-itk.
  Setting up apache2-utils (2.4.12-2) ...
  Setting up apache2-data (2.4.12-2) ...
  Setting up apache2 (2.4.12-2) ...
  Enabling module mpm_event.
  Enabling module authz_core.
  Enabling module authz_host.
  Enabling module authn_core.
  Enabling module auth_basic.
  Enabling module access_compat.
  Enabling module authn_file.
  Enabling module authz_user.
  Enabling module alias.
  Enabling module dir.
  Enabling module autoindex.
  Enabling module env.
  Enabling module mime.
  Enabling module negotiation.
  Enabling module setenvif.
  Enabling module filter.
  Enabling module deflate.
  Enabling module status.
  Enabling conf charset.
  Enabling conf localized-error-pages.
  Enabling conf other-vhosts-access-log.
  Enabling conf security.
  Enabling conf serve-cgi-bin.
  Enabling site 000-default.
  info: mpm_prefork: No action required
  info: Executing deferred 'a2enmod mpm_itk' for package libapache2-mpm-itk
  ERROR: Module mpm_event is enabled - cannot proceed due to conflicts. It 
needs to be disabled first!
  ERROR: Could not enable dependency mpm_prefork for mpm_itk, aborting
  dpkg: error processing package apache2 (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of libapache2-mod-php5:
   libapache2-mod-php5 depends on apache2 (>= 2.4); however:
Package apache2 is not configured yet.
  
  dpkg: error processing package libapache2-mod-php5 (--configure):
   dependency problems - leaving unconfigured
[...]


cheers,

Andreas


fusionforge-web_6.0.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.10-10+deb8u4

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

Debian distribution maintenance software
pp.
Stefan Fritsch  (supplier of updated apache2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 28 Nov 2015 15:02:23 +0100
Source: apache2
Binary: apache2 apache2-data apache2-bin apache2-mpm-worker apache2-mpm-prefork 
apache2-mpm-event apache2-mpm-itk apache2.2-bin apache2.2-common 
libapache2-mod-proxy-html libapache2-mod-macro apache2-utils apache2-suexec 
apache2-suexec-pristine apache2-suexec-custom apache2-doc apache2-dev 
apache2-dbg
Architecture: source amd64 all
Version: 2.4.10-10+deb8u4
Distribution: jessie
Urgency: medium
Maintainer: Debian Apache Maintainers 
Changed-By: Stefan Fritsch 
Description:
 apache2- Apache HTTP Server
 apache2-bin - Apache HTTP Server (modules and other binary files)
 apache2-data - Apache HTTP Server (common files)
 apache2-dbg - Apache debugging symbols
 apache2-dev - Apache HTTP Server (development headers)
 apache2-doc - Apache HTTP Server (on-site documentation)
 apache2-mpm-event - transitional event MPM package for apache2
 apache2-mpm-itk - transitional itk MPM package for apac

Processed: tagging 788723

[Debian Bug Tracking System]

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

> tags 788723 - jessie-ignore
Bug #788723 {Done: Markus Frosch } [src:icinga] 
[src:icinga] Some sources are not included in your package
Removed tag(s) jessie-ignore.
> thanks
Stopping processing here.

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

Processed: limit source to procps, tagging 733758, tagging 789322, tagging 764590, tagging 798438 ...

[Debian Bug Tracking System]

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

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

> tags 733758 + pending
Bug #733758 [procps] [free] -s option only works if -c option is used
Added tag(s) pending.
> tags 789322 + pending
Bug #789322 [procps] /usr/bin/pmap: [pmap] integer overflow on maps over 2GiB 
on 32-bit platform
Added tag(s) pending.
> tags 764590 + pending
Bug #764590 [procps] procps: fails to build from source in sid on amd64
Added tag(s) pending.
> tags 798438 + pending
Bug #798438 [src:procps] procps: FTBFS: Makefile:526: recipe for target 
'check-DEJAGNU' failed
Added tag(s) pending.
> tags 763795 + pending
Bug #763795 [procps] [vmstat] crash in testsuite during arm64 build: crash bug 
in vmstat
Added tag(s) pending.
> tags 762928 + pending
Bug #762928 [procps] [top] changed output, removed information
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#809198: marked as done (maildirsync broken with perl 5.22)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 23:35:59 +
with message-id 
and subject line Bug#809198: fixed in maildirsync 1.2-2.1
has caused the Debian Bug report #809198,
regarding maildirsync broken with perl 5.22
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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

As of perl 5.22, “use UNIVERSAL (…)” is a fatal error:


% sed '13q;d' /usr/bin/maildirsync 
use UNIVERSAL qw(isa);
% /usr/bin/maildirsync
UNIVERSAL does not export anything at /usr/bin/maildirsync line 13.
BEGIN failed--compilation aborted at /usr/bin/maildirsync line 13.
%

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

Kernel: Linux 4.3.0-1-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: sysvinit (via /sbin/init)

Versions of packages maildirsync depends on:
ii  perl  5.22.1-3

Versions of packages maildirsync recommends:
ii  openssh-client [rsh-client]  1:7.1p1-5
ii  ssh  1:7.1p1-5

Versions of packages maildirsync suggests:
ii  bzip2  1.0.6-8

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIVAwUBVoDrCvhx3EthBlqjAQj5+A//SBV+ucrjnZvbA7uTeyRppWYzeY2acIWg
FdWWQ+y9dlLOQN6DiI/2lBSDvnw7Rae7gIs4QPRV2xl2wZh1yvUVZ7NVU4EZAH03
t9ce7S6m4VPvDOokCnDPqOBLFJ6HwjUq2ahQymGVvjAW/dQh/1a0d2nfcsUbIyTU
eY/aToYZAMmVpF+zor9jeoo8+LliXUjwJQ3nHAB7wshNQhmPWaIYPJxsCAMhN/mU
BlwZCcrZeSO9o5QmfVOxDq8KiXRHbdnuhnDh1M64EyiUOM9czIVtwEISrvtAQhcZ
ULi8WWBI/v13OI9YeJz/9Ex77CgGe1XgaYs0eOP9lb8v5FQzgbLykyaX1Uqg6ukZ
N1lcNz1j8ZN7y40C3wLirnWTmMjJ4tEnwNdwgk7Vip5/cyMRCn0zz/LNP240ATC0
wxrtTzDcKBZl45dst/uABQbSI1ZWsphsfLN20qWbM05rmgkh9oiKnT5phr08vvZU
QWEt+5oN3jpSO+JJmP2zlE/4x1XhwnoypIvw1kHacwUKw+cneTfrlqft0kpd8Mfb
q4vsSxHhQr+rUTtibEIzurNtmUmZLilnnyUu3uQElivBeKgzhH7EKq6aTOCXESBC
ir01le7kBibugEV/ZAFX3k1F9woZ7aOdulKHpvrAq11jPjS2t/Ulq+Et1O/U9/KW
iwsTm6Z5nY8=
=kC6a
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: maildirsync
Source-Version: 1.2-2.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated maildirsync package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Dec 2015 00:06:24 +0100
Source: maildirsync
Binary: maildirsync
Architecture: source all
Version: 1.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Carlos Alberto Silombria Ibarra 
Changed-By: gregor herrmann 
Description:
 maildirsync - simple and efficient Maildir synchronisation utility
Closes: 809198
Changes:
 maildirsync (1.2-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "maildirsync broken with perl 5.22":
 add patch use-UNIVERSAL.patch, taken from upstream's svn repo.
 Also remove the disabled maildirsync.pl.diff patch which did something
 similar but with ref, which is not recommended (cf. perldoc -f ref).
 (Closes: #809198)
Checksums-Sha1:
 e7d137355c1c00bb4f75e5e699f609b134d6dbf9 1871 maildirsync_1.2-2.1.dsc
 822829eb74a823ddd1017363bb7632f239fee8b2 4712 maildirsync_1.2-2.1.debian.tar.xz
 46d9d72259047c4ec0d85871c080f5685abce378 23564 maildirsync_1.2-2.1_all.deb
Checksums-Sha256:
 730872e49e636af4c26ed0ae23d8f3bf83a430f59125ac052fa0f8be0ddcf9be 1871 
maildirsync_1.2-2.1.dsc
 9c26b9c7216653c3857fa0268133d437d68b87caff5558c8a9a37b7bf34a75c3 4712 
maildirsync_1.2-2.1.debian.tar.xz
 fbc0415e15c5249b393378e22d1c78909ff0351f596dd0e299e9318f4ccb620c 23564 
maildirsync_1.2-2.1_all.deb
Files:
 fd5acb7315ded3754baad9be48b250b9 18

Bug#780103: marked as done (maildirsync: please re-enable maildirsync.pl.diff patch)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 23:35:59 +
with message-id 
and subject line Bug#809198: fixed in maildirsync 1.2-2.1
has caused the Debian Bug report #809198,
regarding maildirsync: please re-enable maildirsync.pl.diff patch
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.)


-- 
809198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: maildirsync
Version: 1.2-2
Severity: normal

Dear Maintainer,

when maildirsync starts, it outputs the following warning:

UNIVERSAL->import is deprecated and will be removed in a future perl at
/usr/bin/maildirsync line 13.

>From the changelog for version 1.2-2 it reads:

  * Deleted patch maildirsync.pl.diff, was aplied on the source.

Unfortunately, it doesn't seem it was really applied. On the bright
side, though, the patch is still there and the fix should be as easy as
re-enabling it within the series file.

Thank you,
Gian Piero.

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

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

Versions of packages maildirsync depends on:
ii  perl  5.20.2-2

Versions of packages maildirsync recommends:
ii  openssh-client [rsh-client]  1:6.7p1-3

Versions of packages maildirsync suggests:
ii  bzip2  1.0.6-7+b2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: maildirsync
Source-Version: 1.2-2.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated maildirsync package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Dec 2015 00:06:24 +0100
Source: maildirsync
Binary: maildirsync
Architecture: source all
Version: 1.2-2.1
Distribution: unstable
Urgency: medium
Maintainer: Carlos Alberto Silombria Ibarra 
Changed-By: gregor herrmann 
Description:
 maildirsync - simple and efficient Maildir synchronisation utility
Closes: 809198
Changes:
 maildirsync (1.2-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "maildirsync broken with perl 5.22":
 add patch use-UNIVERSAL.patch, taken from upstream's svn repo.
 Also remove the disabled maildirsync.pl.diff patch which did something
 similar but with ref, which is not recommended (cf. perldoc -f ref).
 (Closes: #809198)
Checksums-Sha1:
 e7d137355c1c00bb4f75e5e699f609b134d6dbf9 1871 maildirsync_1.2-2.1.dsc
 822829eb74a823ddd1017363bb7632f239fee8b2 4712 maildirsync_1.2-2.1.debian.tar.xz
 46d9d72259047c4ec0d85871c080f5685abce378 23564 maildirsync_1.2-2.1_all.deb
Checksums-Sha256:
 730872e49e636af4c26ed0ae23d8f3bf83a430f59125ac052fa0f8be0ddcf9be 1871 
maildirsync_1.2-2.1.dsc
 9c26b9c7216653c3857fa0268133d437d68b87caff5558c8a9a37b7bf34a75c3 4712 
maildirsync_1.2-2.1.debian.tar.xz
 fbc0415e15c5249b393378e22d1c78909ff0351f596dd0e299e9318f4ccb620c 23564 
maildirsync_1.2-2.1_all.deb
Files:
 fd5acb7315ded3754baad9be48b250b9 1871 mail optional maildirsync_1.2-2.1.dsc
 94f9535a904d59cc6e9ad3c40f6457b4 4712 mail optional 
maildirsync_1.2-2.1.debian.tar.xz
 f4f5e0f8efd803d1f3939c15dfbbec05 23564 mail optional 
maildirsync_1.2-2.1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJWhGP9XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGzdkQAMUZiV6URQsSRwy+Go+AVuQc
DqpsxX2ssJX07LWi2eGVq2kBOvdKOMCL7yBgOOjUHe/Nr1MoL64uAgl54oyvLiU5
8txjoAtVk2c0p+a3saIS80z/WIycDXn+/C5LLTRFBG/bb7XYyLvbc4xiMW0KVFlZ
DCrR3m3wNcxpr/rIMHJlo3fE0CEeHmgaRQY/v0MjaaeQQHinBHKC35A072EG4CPl
J9CjxKRdgw42usVFd8uFtBQvm9cepglJibYAIP9lxlqvn+YB+zIOV1i763hH93ie
eMCLqwpUD3e1C47uyu7kIpC4IkUJlDlsg6ULESMz+OVZSMpYy0zBBcOJ54JzQSDF
BI+mTPN3RQPLKhGoKUTCxsZkV/MKds/4cCVWRYtjTK1WcOcY1F5Quj7Qp/cArwMz
GQBCAkX/SwIpldPPox4

Bug#808321: marked as done (votca-csg-scripts: Depends on virtual package "perl5" which will is gone with perl/5.22)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 23:22:41 +
with message-id 
and subject line Bug#808321: fixed in votca-csg 1.2.4-2.1
has caused the Debian Bug report #808321,
regarding votca-csg-scripts: Depends on virtual package "perl5" which will is 
gone with perl/5.22
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.)


-- 
808321: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: votca-csg-scripts
Version: 1.2.4-2
Severity: serious
Justification: package uninstallable
Tags: sid patch
User: debian-p...@lists.debian.org
Usertags: perl-5.22-transition

The perl 5.22 transition recently started (see
https://lists.debian.org/debian-devel-announce/2015/12/msg5.html)
and we seem to have missed that this package depends on the deprecated
virtual package "perl5" like some other packages did.

The perl 5.22 packages don't provide perl5, making this package
uninstallable.

I'm sorry that we overlooked this prior to the unstable upload. Please
find below a patch fixing this. Let me know if you'd like this
to be NMUed without further delay.

--- votca-csg-1.2.4/debian/control.orig 2015-12-18 16:24:34.699700722 +
+++ votca-csg-1.2.4/debian/control  2015-12-18 16:24:40.027652244 +
@@ -49,7 +49,7 @@
 
 Package: votca-csg-scripts
 Architecture: all
-Depends: bash (>= 4), perl5, ${misc:Depends}, ${python:Depends}
+Depends: bash (>= 4), perl, ${misc:Depends}, ${python:Depends}
 Description: VOTCA's coarse-graining scripts
  VOTCA is a software package which focuses on the analysis of molecular
  dynamics data, the development of systematic coarse-graining techniques as


Cheers,
Dominic.
--- End Message ---
--- Begin Message ---
Source: votca-csg
Source-Version: 1.2.4-2.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated votca-csg 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: Wed, 30 Dec 2015 23:29:50 +0100
Source: votca-csg
Binary: libvotca-csg2-dev libvotca-csg2 votca-csg-scripts votca-csg-tutorials 
votca-csg
Architecture: all source
Version: 1.2.4-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: gregor herrmann 
Closes: 808321
Description: 
 libvotca-csg2 - VOTCA's coarse-graining library
 libvotca-csg2-dev - VOTCA's coarse-graining library, development kit
 votca-csg  - VOTCA's coarse-graining engine
 votca-csg-scripts - VOTCA's coarse-graining scripts
 votca-csg-tutorials - VOTCA's coarse-graining tutorials
Changes:
 votca-csg (1.2.4-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "Depends on virtual package "perl5" which will is gone with
 perl/5.22": replace perl5 with perl in debian/control.
 (Closes: #808321)
Checksums-Sha1: 
 b0a620bbbccfaf9bf9bf9a6b1d8d327c20b2ec88 2755 votca-csg_1.2.4-2.1.dsc
 5d1ad52d3bd103a81b3b0e000f2a0d752e33cb9e 5252 votca-csg_1.2.4-2.1.debian.tar.xz
 fd59f01a557c39562d02f935baf247445dace599 48294 
votca-csg-scripts_1.2.4-2.1_all.deb
 3c27dbf293e71cf1b480d6770918814396887d65 2156314 
votca-csg-tutorials_1.2.4-2.1_all.deb
Checksums-Sha256: 
 828ad73a27938221d6b0245af2c7a9ce001c5573f44434767f5a1bcf6abca308 2755 
votca-csg_1.2.4-2.1.dsc
 f4838db92a1782183f3104e5cbd805ca3d50caebd42a34fd8d3e4176748416e1 5252 
votca-csg_1.2.4-2.1.debian.tar.xz
 c180c4c7aff4e509990a4d3729d5156ed17e6e9920d1d7e580f01d8c02ad8262 48294 
votca-csg-scripts_1.2.4-2.1_all.deb
 9342985be18da4cb6fc73eaa788ad7e4d70df496c557662720559642c527b067 2156314 
votca-csg-tutorials_1.2.4-2.1_all.deb
Files: 
 74a69984ad8645fb963e9647fd17b3fe 2755 science optional votca-csg_1.2.4-2.1.dsc
 68df01f6af5ce9d9abd18f86271cdea3 5252 science optional 
votca-csg_1.2.4-2.1.debian.tar.xz
 6f7a558869bb71225dbd9cf6af105579 48294 science optional 
votca-csg-scripts_1.2.4-2.1_all.deb
 679d27c951a0ec79b7c2301768221b2e 2156314 science optional 
votca-csg-tutorials_1.2.4-2.1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCg

Processed: tagging 788723

[Debian Bug Tracking System]

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

> tags 788723 + jessie-ignore
Bug #788723 {Done: Markus Frosch } [src:icinga] 
[src:icinga] Some sources are not included in your package
Added tag(s) jessie-ignore.
> thanks
Stopping processing here.

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

Bug#804590: [Debian-ha-maintainers] Bug#804590: redhat-cluster: build-depends on libcorosync-dev which is no longer built

[Ferenc Wagner]

Jonathan Wiltshire  writes:

> On Mon, Dec 14, 2015 at 02:22:54AM +0100, Ferenc Wagner wrote:
>
>> The redhat-cluster package will be removed from the archive, we don't
>> intend to fix it.
>
> Here's the hit list then:

[gfs2-utils, lvm2, ocfs2-tools]

That's fine, once pacemaker passes NEW, we can upload the new DLM
package and adjust the above to use it instead of redhat-cluster.
-- 
Thanks,
Feri.

Bug#809350: marked as done (linux-image-4.3.0-1-686-pae: SSDs report disk errors)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 23:00:45 +
with message-id 
and subject line Bug#809082: fixed in linux 4.3.3-3
has caused the Debian Bug report #809082,
regarding linux-image-4.3.0-1-686-pae: SSDs report disk errors
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.)


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

Dear Maintainer,

When booted up the linux-image-4.3.0-1-686-pae package, 4 hosts started to 
report errors on the SSDs:

Thinkpad X301,Intel X18-M/X25-M/X25-V G2 SSDs
Thinkpad W700,Samsung SSD 840 EVO 120GB
Thinkpad X201,Samsung SSD 840 Series
ZOTAC H67ITX-C-E/i3-3220T,SAMSUNG 470 Series SSD

The errors are pretty much the same on all hosts:

Dec 29 17:19:26 toothless kernel: [  382.252069] ata1.00: exception Emask 0x60 
SAct 0x700 SErr 0x800 action 0x6 frozen
Dec 29 17:19:26 toothless kernel: [  382.252077] ata1.00: irq_stat 0x2000, 
host bus error
Dec 29 17:19:26 toothless kernel: [  382.252081] ata1: SError: { HostInt }
Dec 29 17:19:26 toothless kernel: [  382.252086] ata1.00: failed command: WRITE 
FPDMA QUEUED
Dec 29 17:19:26 toothless kernel: [  382.252094] ata1.00: cmd 
61/70:40:98:d9:16/06:00:03:00:00/40 tag 8 ncq 843776 out
Dec 29 17:19:26 toothless kernel: [  382.252094]  res 
40/00:54:00:10:94/00:00:03:00:00/40 Emask 0x60 (host bus error)
Dec 29 17:19:26 toothless kernel: [  382.252098] ata1.00: status: { DRDY }
Dec 29 17:19:26 toothless kernel: [  382.252102] ata1.00: failed command: WRITE 
FPDMA QUEUED
Dec 29 17:19:26 toothless kernel: [  382.252109] ata1.00: cmd 
61/48:48:08:e0:16/19:00:03:00:00/40 tag 9 ncq 3313664 out
Dec 29 17:19:26 toothless kernel: [  382.252109]  res 
40/00:54:00:10:94/00:00:03:00:00/40 Emask 0x60 (host bus error)
Dec 29 17:19:26 toothless kernel: [  382.252113] ata1.00: status: { DRDY }
Dec 29 17:19:26 toothless kernel: [  382.252117] ata1.00: failed command: READ 
FPDMA QUEUED
Dec 29 17:19:26 toothless kernel: [  382.252124] ata1.00: cmd 
60/08:50:00:10:94/00:00:03:00:00/40 tag 10 ncq 4096 in
Dec 29 17:19:26 toothless kernel: [  382.252124]  res 
40/00:54:00:10:94/00:00:03:00:00/40 Emask 0x60 (host bus error)
Dec 29 17:19:26 toothless kernel: [  382.252129] ata1.00: status: { DRDY }
Dec 29 17:19:26 toothless kernel: [  382.252134] ata1: hard resetting link
Dec 29 17:19:26 toothless kernel: [  382.572088] ata1: SATA link up 3.0 Gbps 
(SStatus 123 SControl 300)
Dec 29 17:19:26 toothless kernel: [  382.572546] ata1.00: ACPI cmd 
ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Dec 29 17:19:26 toothless kernel: [  382.572552] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Dec 29 17:19:26 toothless kernel: [  382.572557] ata1.00: ACPI cmd 
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Dec 29 17:19:26 toothless kernel: [  382.573214] ata1.00: ACPI cmd 
ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
Dec 29 17:19:26 toothless kernel: [  382.573220] ata1.00: ACPI cmd 
f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out
Dec 29 17:19:26 toothless kernel: [  382.573225] ata1.00: ACPI cmd 
ef/10:03:00:00:00:a0 (SET FEATURES) filtered out
Dec 29 17:19:26 toothless kernel: [  382.573452] ata1.00: configured for 
UDMA/133
Dec 29 17:19:26 toothless kernel: [  382.573472] ata1: EH complete
Dec 29 17:19:26 toothless kernel: [  382.573552] ata1.00: Enabling 
discard_zeroes_data
Dec 29 17:19:27 toothless kernel: [  383.220074] ata1.00: exception Emask 0x60 
SAct 0x38 SErr 0x800 action 0x6 frozen
Dec 29 17:19:27 toothless kernel: [  383.220082] ata1.00: irq_stat 0x2000, 
host bus error
Dec 29 17:19:27 toothless kernel: [  383.220085] ata1: SError: { HostInt }
Dec 29 17:19:27 toothless kernel: [  383.220091] ata1.00: failed command: WRITE 
FPDMA QUEUED

Etc, ad nauseam.

After booting back to 4.2, fsck fixed some errors, on other hosts data loss 
happened and some applications had to be reinstalled. But the hosts and disks 
are stable with 4.2.

Regards,

Gergely Tomka

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
not available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub [8086:2a40] (rev 07)
Subsystem: Lenovo Device [17aa:20e0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SER

Bug#808563: marked as done (Boot with 4.3: SATA errors. Returning to 4.2: no errors)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 23:00:45 +
with message-id 
and subject line Bug#809082: fixed in linux 4.3.3-3
has caused the Debian Bug report #809082,
regarding Boot with 4.3: SATA errors. Returning to 4.2: no errors
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.)


-- 
809082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.3.3-2
Severity: important

I am getting these errors (sort -u'd here) with linux-image-4.3.0-1-686-pae

 res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: cmd 61/d0:d8:80:9e:10/05:00:26:00:00/40 tag 27 ncq 761856 out
ata1.00: configured for UDMA/133
ata1.00: exception Emask 0x60 SAct 0x1800 SErr 0x800 action 0x6 frozen
ata1.00: exception Emask 0x60 SAct 0x1f8 SErr 0x800 action 0x6 frozen
ata1.00: exception Emask 0x60 SAct 0xfe SErr 0x800 action 0x6 frozen
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: irq_stat 0x2000, host bus error
ata1.00: status: { DRDY }
ata1: EH complete
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1: SError: { HostInt }
ata1: hard resetting link

Switching back to 4.2.6-3 solves it.

Did it twice so far. Consistent results.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.3.3-3

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 16:45:46 +
Source: linux
Binary: linux-source-4.3 linux-support-4.3.0-1 linux-doc-4.3 linux-manual-4.3 
linux-libc-dev linux-headers-4.3.0-1-all linux-headers-4.3.0-1-all-alpha 
kernel-image-4.3.0-1-alpha-generic-di nic-modules-4.3.0-1-alpha-generic-di 
nic-wireless-modules-4.3.0-1-alpha-generic-di 
nic-shared-modules-4.3.0-1-alpha-generic-di 
serial-modules-4.3.0-1-alpha-generic-di 
usb-serial-modules-4.3.0-1-alpha-generic-di 
ppp-modules-4.3.0-1-alpha-generic-di pata-modules-4.3.0-1-alpha-generic-di 
cdrom-core-modules-4.3.0-1-alpha-generic-di 
scsi-core-modules-4.3.0-1-alpha-generic-di 
scsi-modules-4.3.0-1-alpha-generic-di 
scsi-common-modules-4.3.0-1-alpha-generic-di 
scsi-extra-modules-4.3.0-1-alpha-generic-di 
loop-modules-4.3.0-1-alpha-generic-di btrfs-modules-4.3.0-1-alpha-generic-di 
ext4-modules-4.3.0-1-alpha-generic-di isofs-modules-4.3.0-1-alpha-generic-di 
jfs-modules-4.3.0-1-alpha-generic-di xfs-modules-4.3.0-1-alpha-generic-di 
fat-modules-4.3.0-1-alpha-generic-di
 md-modules-4.3.0-1-alpha-generic-di multipath-modules-4.3.0-1-alpha-generic-di 
usb-modules-4.3.0-1-alpha-generic-di 
usb-storage-modules-4.3.0-1-alpha-generic-di 
fb-modules-4.3.0-1-alpha-generic-di input-modules-4.3.0-1-alpha-generic-di 
event-modules-4.3.0-1-alpha-generic-di mouse-modules-4.3.0-1-alpha-generic-di 
nic-pcmcia-modules-4.3.0-1-alpha-generic-di 
pcmcia-modules-4.3.0-1-alpha-generic-di 
nic-usb-modules-4.3.0-1-alpha-generic-di sata-modules-4.3.0-1-alpha-generic-di 
core-modules-4.3.0-1-alpha-generic-di crc-modules-4.3.0-1-alpha-generic-di 
crypto-modules-4.3.0-1-alpha-generic-di 
crypto-dm-modules-4.3.0-1-alpha-generic-di ata-modules-4.3.0-1-alpha-generic-di 
nbd-modules-4.3.0-1-alpha-generic-di squashfs-modules-4.3.0-1-alpha-generic-di 
virtio-modules-4.3.0-1-alpha-generic-di zlib-modules-4.3.0-1-alpha-generic-di 
fuse-modules-4.3.0-1-alpha-generic-di srm-modules-4.3.0-1-alpha-generic-di 
linux-headers-4.3.0-1-common linux-image-4.3.0-1-alpha-generic
 linux-headers-4.3.0-1-alpha-generic linux-image-4.3.0-1-alpha-smp 
linux-headers-4.3.0-1-alpha-smp linux-headers-4.3.0-1-all-amd64 
kernel-image-4.3.0-1-amd64-di nic-modules-4.3.0-1-amd64-di 
nic-wireless-modules-4.3.0-1-amd64-di nic-shared-modules-4.3.0-1-amd64-di 
serial-modules-4.3.0-1-amd64-di usb-serial-modules-4.3.0-1-amd64-di 
ppp-modules-4.3.0-1-amd64-di pata-modules-4.3.0-1-amd64-di 
cdrom-core-modules-4.3.0-1-amd64-di fire

Bug#809082: marked as done (Linux kernel 4.3.3 PAE causes disk errors)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 23:00:45 +
with message-id 
and subject line Bug#809082: fixed in linux 4.3.3-3
has caused the Debian Bug report #809082,
regarding Linux kernel 4.3.3 PAE causes disk errors
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.)


-- 
809082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-686-pae
Version: 4.3+70: i386
Severity: grave

Package: linux-image-4.3.0-1-686-pae
Version: 4.3.3-2

This is an FYI to update this kernel as soon as the fix is released.

Linux kernel 4.3.3 has a serious bug in its PAE support, which causes all kinds 
of disk access
errors.
The bug has been reported upstream at:
https://bugzilla.kernel.org/show_bug.cgi?id=109661
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.3.3-3

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 16:45:46 +
Source: linux
Binary: linux-source-4.3 linux-support-4.3.0-1 linux-doc-4.3 linux-manual-4.3 
linux-libc-dev linux-headers-4.3.0-1-all linux-headers-4.3.0-1-all-alpha 
kernel-image-4.3.0-1-alpha-generic-di nic-modules-4.3.0-1-alpha-generic-di 
nic-wireless-modules-4.3.0-1-alpha-generic-di 
nic-shared-modules-4.3.0-1-alpha-generic-di 
serial-modules-4.3.0-1-alpha-generic-di 
usb-serial-modules-4.3.0-1-alpha-generic-di 
ppp-modules-4.3.0-1-alpha-generic-di pata-modules-4.3.0-1-alpha-generic-di 
cdrom-core-modules-4.3.0-1-alpha-generic-di 
scsi-core-modules-4.3.0-1-alpha-generic-di 
scsi-modules-4.3.0-1-alpha-generic-di 
scsi-common-modules-4.3.0-1-alpha-generic-di 
scsi-extra-modules-4.3.0-1-alpha-generic-di 
loop-modules-4.3.0-1-alpha-generic-di btrfs-modules-4.3.0-1-alpha-generic-di 
ext4-modules-4.3.0-1-alpha-generic-di isofs-modules-4.3.0-1-alpha-generic-di 
jfs-modules-4.3.0-1-alpha-generic-di xfs-modules-4.3.0-1-alpha-generic-di 
fat-modules-4.3.0-1-alpha-generic-di
 md-modules-4.3.0-1-alpha-generic-di multipath-modules-4.3.0-1-alpha-generic-di 
usb-modules-4.3.0-1-alpha-generic-di 
usb-storage-modules-4.3.0-1-alpha-generic-di 
fb-modules-4.3.0-1-alpha-generic-di input-modules-4.3.0-1-alpha-generic-di 
event-modules-4.3.0-1-alpha-generic-di mouse-modules-4.3.0-1-alpha-generic-di 
nic-pcmcia-modules-4.3.0-1-alpha-generic-di 
pcmcia-modules-4.3.0-1-alpha-generic-di 
nic-usb-modules-4.3.0-1-alpha-generic-di sata-modules-4.3.0-1-alpha-generic-di 
core-modules-4.3.0-1-alpha-generic-di crc-modules-4.3.0-1-alpha-generic-di 
crypto-modules-4.3.0-1-alpha-generic-di 
crypto-dm-modules-4.3.0-1-alpha-generic-di ata-modules-4.3.0-1-alpha-generic-di 
nbd-modules-4.3.0-1-alpha-generic-di squashfs-modules-4.3.0-1-alpha-generic-di 
virtio-modules-4.3.0-1-alpha-generic-di zlib-modules-4.3.0-1-alpha-generic-di 
fuse-modules-4.3.0-1-alpha-generic-di srm-modules-4.3.0-1-alpha-generic-di 
linux-headers-4.3.0-1-common linux-image-4.3.0-1-alpha-generic
 linux-headers-4.3.0-1-alpha-generic linux-image-4.3.0-1-alpha-smp 
linux-headers-4.3.0-1-alpha-smp linux-headers-4.3.0-1-all-amd64 
kernel-image-4.3.0-1-amd64-di nic-modules-4.3.0-1-amd64-di 
nic-wireless-modules-4.3.0-1-amd64-di nic-shared-modules-4.3.0-1-amd64-di 
serial-modules-4.3.0-1-amd64-di usb-serial-modules-4.3.0-1-amd64-di 
ppp-modules-4.3.0-1-amd64-di pata-modules-4.3.0-1-amd64-di 
cdrom-core-modules-4.3.0-1-amd64-di firewire-core-modules-4.3.0-1-amd64-di 
scsi-core-modules-4.3.0-1-amd64-di scsi-modules-4.3.0-1-amd64-di 
scsi-common-modules-4.3.0-1-amd64-di scsi-extra-modules-4.3.0-1-amd64-di 
loop-modules-4.3.0-1-amd64-di btrfs-modules-4.3.0-1-amd64-di 
ext4-modules-4.3.0-1-amd64-di isofs-modules-4.3.0-1-amd64-di 
jfs-modules-4.3.0-1-amd64-di ntfs-modules-4.3.0-1-amd64-di 
xfs-modules-4.3.0-1-amd64-di fat-modules-4.3.0-1-amd64-di 
md-modules-4.3.0-1-amd64-di multipath-modules-4.3.0-1-amd64-di 
usb-modules-4.3.0-1-amd64-di usb-sto

Bug#802418: marked as done (thepeg: FTBFS: elf_open: Invalid argument)

[Debian Bug Tracking System]

Your message dated Sat, 2 Jan 2016 23:48:59 +0100
with message-id <20160102224859.ga32...@ramacher.at>
and subject line Re: Bug#802418: thepeg: FTBFS: elf_open: Invalid argument
has caused the Debian Bug report #802418,
regarding thepeg: FTBFS: elf_open: Invalid argument
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.)


-- 
802418: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thepeg
Version: 1.8.0-1
Severity: serious
Justification: fails to build from source
Tags: sid 
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 (maybe it's dh-exec being broken, who knows
what that error is actually from):

make[1]: Leaving directory '/thepeg-1.8.0'
mv debian/tmp//usr/lib/x86_64-linux-gnu/ThePEG/lib* 
debian/tmp//usr/lib/x86_64-linux-gnu
sed -i -e 's,/.*debian/tmp,,' \
debian/tmp//usr/lib/x86_64-linux-gnu/ThePEG/ThePEGDefaults.rpo
chrpath -d debian/tmp/usr/bin/runThePEG
chrpath -d debian/tmp/usr/bin/setupThePEG
chrpath -d debian/tmp//usr/lib/x86_64-linux-gnu/ThePEG/HepMCAnalysis.so
chrpath -d debian/tmp//usr/lib/x86_64-linux-gnu/ThePEG/RivetAnalysis.so
open: No such file or directory
elf_open: Invalid argument
debian/rules:62: recipe for target 'install-arch' failed
make: *** [install-arch] Error 1
dpkg-buildpackage: error: debian/rules binary gave error exit status 2

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

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

On 2015-10-19 23:14:07, Chris West (Faux) wrote:
> Source: thepeg
> Version: 1.8.0-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid 
> 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 (maybe it's dh-exec being broken, who knows
> what that error is actually from):
> 
> make[1]: Leaving directory '/thepeg-1.8.0'
> mv debian/tmp//usr/lib/x86_64-linux-gnu/ThePEG/lib* 
> debian/tmp//usr/lib/x86_64-linux-gnu
> sed -i -e 's,/.*debian/tmp,,' \
>   debian/tmp//usr/lib/x86_64-linux-gnu/ThePEG/ThePEGDefaults.rpo
> chrpath -d debian/tmp/usr/bin/runThePEG
> chrpath -d debian/tmp/usr/bin/setupThePEG
> chrpath -d debian/tmp//usr/lib/x86_64-linux-gnu/ThePEG/HepMCAnalysis.so
> chrpath -d debian/tmp//usr/lib/x86_64-linux-gnu/ThePEG/RivetAnalysis.so
> open: No such file or directory
> elf_open: Invalid argument
> debian/rules:62: recipe for target 'install-arch' failed
> make: *** [install-arch] Error 1
> dpkg-buildpackage: error: debian/rules binary gave error exit status 2

This looks like a transient issue. thepeg no longer fails to build, so I'm
closing the issue.

Cheers
-- 
Sebastian Ramacher


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

Bug#808769: [Pkg-samba-maint] Bug#808769: Bug#808769: Bug#808769: LDB build failure isn't a regression

[Jelmer Vernooij]

On Sun, Jan 03, 2016 at 11:36:18AM +1300, Andrew Bartlett wrote:
> On Sat, 2016-01-02 at 22:22 +, Jelmer Vernooij wrote:
> > On Sun, Jan 03, 2016 at 11:00:44AM +1300, Andrew Bartlett wrote:
> > > On Sat, 2016-01-02 at 21:51 +, Jelmer Vernooij wrote:
> > > > On Sun, Jan 03, 2016 at 10:38:12AM +1300, Andrew Bartlett wrote:
> > > > > On Thu, 2015-12-31 at 18:53 +1300, Andrew Bartlett wrote:
> > > > > > Just a quick note to say that the LDB build failure isn't a
> > > > > > regression 
> > > > > > - whatever is going on here has always been going on, it just
> > > > > > wasn't
> > > > > > tested before ldb 1.1.23.
> > > > > 
> > > > > > That said, fixing this is going to require gdb on a s390.  Is
> > > > > > the
> > > > > > porterbox where that should be done?
> > > > > > 
> > > > > > https://db.debian.org/machines.cgi?host=zelenka
> > > > > > 
> > > > > > How do I get on such a machine?
> > > > > 
> > > > > I've asked (but not yet got, which is reasonable over the
> > > > > holidays)
> > > > > access to this machine.
> > > > FWIW this issue is reproducible on other platforms than s390 too.
> > > 
> > > Can you get me details?
> > Sorry, I don't really have any other than that I've managed to hit it
> > a few times while building locally on my amd64 laptop.
> 
> Can we re-submit it and see if it flaps to success this time?
> 
> Given it doesn't show up under valgrind or under multiple runs (Fedora
> x64, git master) here, this is going to be difficult.

I think it was consistently failing when I encountered it (on my
laptop, not in a chroot), and both s390 buildd builds (and the ubuntu
build) failed too so it is not likely to be flaky there:

https://buildd.debian.org/status/logs.php?pkg=ldb&ver=2%3A1.1.24-1&arch=s390x

Unfortunately it seems to pass on my laptop now, though I am not sure
what has changed to make it pass there.

Cheers,

Jelmer


signature.asc
Description: PGP signature

Processed: libgetdata: diff for NMU version 0.9.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 799340 + patch
Bug #799340 [libgetdata-doc] libgetdata-doc: fails to upgrade from 'testing' - 
trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz
Added tag(s) patch.
> tags 799340 + pending
Bug #799340 [libgetdata-doc] libgetdata-doc: fails to upgrade from 'testing' - 
trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz
Added tag(s) pending.

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

Bug#808769: [Pkg-samba-maint] Bug#808769: Bug#808769: LDB build failure isn't a regression

[Andrew Bartlett]

On Sat, 2016-01-02 at 22:22 +, Jelmer Vernooij wrote:
> On Sun, Jan 03, 2016 at 11:00:44AM +1300, Andrew Bartlett wrote:
> > On Sat, 2016-01-02 at 21:51 +, Jelmer Vernooij wrote:
> > > On Sun, Jan 03, 2016 at 10:38:12AM +1300, Andrew Bartlett wrote:
> > > > On Thu, 2015-12-31 at 18:53 +1300, Andrew Bartlett wrote:
> > > > > Just a quick note to say that the LDB build failure isn't a
> > > > > regression 
> > > > > - whatever is going on here has always been going on, it just
> > > > > wasn't
> > > > > tested before ldb 1.1.23.
> > > > 
> > > > > That said, fixing this is going to require gdb on a s390.  Is
> > > > > the
> > > > > porterbox where that should be done?
> > > > > 
> > > > > https://db.debian.org/machines.cgi?host=zelenka
> > > > > 
> > > > > How do I get on such a machine?
> > > > 
> > > > I've asked (but not yet got, which is reasonable over the
> > > > holidays)
> > > > access to this machine.
> > > FWIW this issue is reproducible on other platforms than s390 too.
> > 
> > Can you get me details?
> Sorry, I don't really have any other than that I've managed to hit it
> a few times while building locally on my amd64 laptop.

Can we re-submit it and see if it flaps to success this time?

Given it doesn't show up under valgrind or under multiple runs (Fedora
x64, git master) here, this is going to be difficult.

Andrew Bartlett

-- 
Andrew Bartlett   http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT  http://catalyst.net.nz/services/samba

Bug#799340: libgetdata: diff for NMU version 0.9.0-2.1

[Jonathan Wiltshire]

Control: tags 799340 + patch
Control: tags 799340 + pending

Dear maintainer,

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

Regards.

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

diff -Nru libgetdata-0.9.0/debian/changelog libgetdata-0.9.0/debian/changelog
--- libgetdata-0.9.0/debian/changelog	2015-11-21 01:47:20.0 +
+++ libgetdata-0.9.0/debian/changelog	2016-01-02 22:23:50.0 +
@@ -1,3 +1,11 @@
+libgetdata (0.9.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Correct Breaks/Replaces on libgetdata-doc, remove those added
+in previous uploads (Closes: #799340)
+
+ -- Jonathan Wiltshire   Sat, 02 Jan 2016 22:23:48 +
+
 libgetdata (0.9.0-2) unstable; urgency=medium
 
   * Breaks/Replace fix for libgetdata-tools. Closes: #799340.
diff -Nru libgetdata-0.9.0/debian/control libgetdata-0.9.0/debian/control
--- libgetdata-0.9.0/debian/control	2015-11-21 01:47:51.0 +
+++ libgetdata-0.9.0/debian/control	2016-01-02 22:20:13.0 +
@@ -14,8 +14,8 @@
 Section: doc
 Architecture: all
 Depends: ${misc:Depends}
-Breaks: libgetdata-dev (<< 0.8.9-2)
-Replaces: libgetdata-dev (<< 0.8.9-2)
+Breaks: libgetdata-tools (<< 0.8.9-2)
+Replaces: libgetdata-tools (<< 0.8.9-2)
 Suggests: libgetdata-dev
 Description: library to read/write dirfile data - API and standards documents
  The GetData Project is the reference implementation of the Dirfile Standards, 
@@ -28,8 +28,6 @@
 Architecture: any
 Depends: libgetdata5 (= ${binary:Version}), libgetdata++3 (= ${binary:Version}), libfgetdata2 (= ${binary:Version}), libf95getdata2 (= ${binary:Version}), ${misc:Depends}
 Suggests: libgetdata-doc
-Breaks: libgetdata-doc (<< 0.8.9-2)
-Replaces: libgetdata-dev (<< 0.8.9-2)
 Description: library to read/write dirfile data - devel files (C, C++, F77, F95)
  The GetData Project is the reference implementation of the Dirfile Standards, 
  a filesystem-based, column-oriented database format for time-ordered binary 
@@ -82,8 +80,6 @@
 
 Package: libgetdata-tools
 Section: libs
-Breaks: libgetdata-doc (<< 0.8.9-2)
-Replaces: libgetdata-dev (<< 0.8.9-2)
 Architecture: any
 Depends: libgetdata5 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
 Description: library to read/write dirfile data - extra tools


signature.asc
Description: Digital signature

Bug#808769: [Pkg-samba-maint] Bug#808769: Bug#808769: LDB build failure isn't a regression

[Jelmer Vernooij]

On Sun, Jan 03, 2016 at 11:00:44AM +1300, Andrew Bartlett wrote:
> On Sat, 2016-01-02 at 21:51 +, Jelmer Vernooij wrote:
> > On Sun, Jan 03, 2016 at 10:38:12AM +1300, Andrew Bartlett wrote:
> > > On Thu, 2015-12-31 at 18:53 +1300, Andrew Bartlett wrote:
> > > > Just a quick note to say that the LDB build failure isn't a
> > > > regression 
> > > > - whatever is going on here has always been going on, it just
> > > > wasn't
> > > > tested before ldb 1.1.23.
> > > 
> > > > That said, fixing this is going to require gdb on a s390.  Is the
> > > > porterbox where that should be done?
> > > > 
> > > > https://db.debian.org/machines.cgi?host=zelenka
> > > > 
> > > > How do I get on such a machine?
> > > 
> > > I've asked (but not yet got, which is reasonable over the holidays)
> > > access to this machine.
> > FWIW this issue is reproducible on other platforms than s390 too.
> 
> Can you get me details?
Sorry, I don't really have any other than that I've managed to hit it
a few times while building locally on my amd64 laptop.

Cheers,

Jelmer


signature.asc
Description: PGP signature

Bug#808769: [Pkg-samba-maint] Bug#808769: LDB build failure isn't a regression

[Jelmer Vernooij]

On Sat, Jan 02, 2016 at 09:51:34PM +, Jelmer Vernooij wrote:
> On Sun, Jan 03, 2016 at 10:38:12AM +1300, Andrew Bartlett wrote:
> > On Thu, 2015-12-31 at 18:53 +1300, Andrew Bartlett wrote:
> > > Just a quick note to say that the LDB build failure isn't a
> > > regression 
> > > - whatever is going on here has always been going on, it just wasn't
> > > tested before ldb 1.1.23.
> > 
> > > That said, fixing this is going to require gdb on a s390.  Is the
> > > porterbox where that should be done?
> > > 
> > > https://db.debian.org/machines.cgi?host=zelenka
> > > 
> > > How do I get on such a machine?
> > 
> > I've asked (but not yet got, which is reasonable over the holidays)
> > access to this machine.
> FWIW this issue is reproducible on other platforms than s390 too.
+xnox, who is working on Ubuntu on s390 and was asking about this
specific issue earlier :)

Jelmer


signature.asc
Description: PGP signature

Bug#808769: [Pkg-samba-maint] Bug#808769: LDB build failure isn't a regression

[Andrew Bartlett]

On Sat, 2016-01-02 at 21:51 +, Jelmer Vernooij wrote:
> On Sun, Jan 03, 2016 at 10:38:12AM +1300, Andrew Bartlett wrote:
> > On Thu, 2015-12-31 at 18:53 +1300, Andrew Bartlett wrote:
> > > Just a quick note to say that the LDB build failure isn't a
> > > regression 
> > > - whatever is going on here has always been going on, it just
> > > wasn't
> > > tested before ldb 1.1.23.
> > 
> > > That said, fixing this is going to require gdb on a s390.  Is the
> > > porterbox where that should be done?
> > > 
> > > https://db.debian.org/machines.cgi?host=zelenka
> > > 
> > > How do I get on such a machine?
> > 
> > I've asked (but not yet got, which is reasonable over the holidays)
> > access to this machine.
> FWIW this issue is reproducible on other platforms than s390 too.

Can you get me details?

Thanks,

Andrew Bartlett

-- 
Andrew Bartlett   http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT  http://catalyst.net.nz/services/samba

Bug#804590: [Debian-ha-maintainers] Bug#804590: redhat-cluster: build-depends on libcorosync-dev which is no longer built

[Jonathan Wiltshire]

On Mon, Dec 14, 2015 at 02:22:54AM +0100, Ferenc Wagner wrote:
> The redhat-cluster package will be removed from the archive, we don't
> intend to fix it.

Here's the hit list then:

===
Checking reverse dependencies...
# Broken Depends:
gfs2-utils: gfs2-cluster [amd64 arm64 armel armhf i386 mips mipsel powerpc 
ppc64el s390x]
gfs2-utils [amd64 arm64 armel armhf i386 mips mipsel powerpc 
ppc64el s390x]
lvm2: clvm [amd64 arm64 armel armhf i386 mips mips64el mipsel powerpc ppc64el 
s390x]

# Broken Build-Depends:
gfs2-utils: libccs-dev (>= 3.1.0)
libcman-dev (>= 3.1.0)
libdlm-dev (>= 3.1.0)
libdlmcontrol-dev (>= 3.1.0)
libfence-dev (>= 3.1.0)
liblogthread-dev (>= 3.1.0)
lvm2: libdlm-dev (> 2)
ocfs2-tools: libdlm-dev
 libdlmcontrol-dev

Dependency problem found.
===


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51



signature.asc
Description: Digital signature

Bug#808209: amanda-common: Depends on virtual package "perl5" which will is gone with perl/5.22

[Jose M Calhariz]

On Mon, Dec 21, 2015 at 12:03:20PM +, Dominic Hargreaves wrote:
> On Sun, Dec 20, 2015 at 07:43:40PM +0100, gregor herrmann wrote:
> > Control: tag -1 + pending
> > 
> > On Thu, 17 Dec 2015 10:28:58 +, Dominic Hargreaves wrote:
> > 
> > > The perl 5.22 transition just started (see
> > > https://lists.debian.org/debian-devel-announce/2015/12/msg5.html)
> > > and we seem to have missed that this package depends on the deprecated
> > > virtual package "perl5" like some other packages did.
> > 
> > Looks like the maintainer has a fix ready and is looking for a
> > sponsor:
> > 
> > http://blog.calhariz.com/post/2015/12/20/Preview-of-amanda-3.3.7p1-1
> 
> Hi Jose,
> 
> In terms of an immediate uninstallability, would you be happy to have
> an NMU with just the perl5 fix, until the new package can be reviewed and
> sponsored? I'd be happy to do the former.

Are you still available to review a new version of amanda?  I have
acknowledge the NMU work and publish the last changes in collab-maint.

> 
> Apologies again for the late notice of this breakage.
> 
> Thanks,
> Dominic.
> 
>

Kind regards
Jose M Calhariz

-- 
--
A utopia e o derradeiro reduto dos que não desesperaram da
liberdade.
-- Tristao de Ataide Alceu Amoroso Lima


signature.asc
Description: Digital signature

Bug#808769: [Pkg-samba-maint] Bug#808769: LDB build failure isn't a regression

[Jelmer Vernooij]

On Sun, Jan 03, 2016 at 10:38:12AM +1300, Andrew Bartlett wrote:
> On Thu, 2015-12-31 at 18:53 +1300, Andrew Bartlett wrote:
> > Just a quick note to say that the LDB build failure isn't a
> > regression 
> > - whatever is going on here has always been going on, it just wasn't
> > tested before ldb 1.1.23.
> 
> > That said, fixing this is going to require gdb on a s390.  Is the
> > porterbox where that should be done?
> > 
> > https://db.debian.org/machines.cgi?host=zelenka
> > 
> > How do I get on such a machine?
> 
> I've asked (but not yet got, which is reasonable over the holidays)
> access to this machine.
FWIW this issue is reproducible on other platforms than s390 too.

Cheers,

Jelmer


signature.asc
Description: PGP signature

Bug#808769: LDB build failure isn't a regression

[Andrew Bartlett]

On Thu, 2015-12-31 at 18:53 +1300, Andrew Bartlett wrote:
> Just a quick note to say that the LDB build failure isn't a
> regression 
> - whatever is going on here has always been going on, it just wasn't
> tested before ldb 1.1.23.

> That said, fixing this is going to require gdb on a s390.  Is the
> porterbox where that should be done?
> 
> https://db.debian.org/machines.cgi?host=zelenka
> 
> How do I get on such a machine?

I've asked (but not yet got, which is reasonable over the holidays)
access to this machine.

In the meantime, what should we do about this blocking the recent
security fix from getting into testing?  This could take a while to
resolve, even once I get access.

Thanks,

Andrew Bartlett

-- 
Andrew Bartlett   http://samba.org/~abartlet/
Authentication Developer, Samba Team  http://samba.org
Samba Developer, Catalyst IT  http://catalyst.net.nz/services/samba

Bug#789614: FTBFS with OCaml 4.02.2: Some fatal warnings were triggered

[Eriberto Mota]

Control: tags 789614 pending

Hi,

I did a new upload, now to 9-day/DELAY queue. This new upload updates
the upstream homepage. So, the new d/changelog is:

 virt-top (1.0.7-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Added the debian/patches/0005-fix-FTBFS-with-OCaml.patch to fix a FTBFS
   with OCaml 4.02.2. Thanks to Stéphane Glondu .
   (Closes: #789614)
   * Bumped Standards-Version to 3.9.6.
   * New upstream homepage. (Closes: #809681)
   * Updated the debian/watch file to use the new upstream source place.

I attached a debdiff.

Regards,

Eriberto


virt-top.debdiff
Description: Binary data

Processed: Re: FTBFS with OCaml 4.02.2: Some fatal warnings were triggered

[Debian Bug Tracking System]

Processing control commands:

> tags 789614 pending
Bug #789614 [src:virt-top] FTBFS with OCaml 4.02.2: Some fatal warnings were 
triggered
Ignoring request to alter tags of bug #789614 to the same tags previously set

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

Bug#809682: pinentry-qt4: pinentry dialog does not support pasting from clipboard

[Kynn Jones]

Package: pinentry-qt4
Version: 0.8.3-2
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

The bug described here applies not only to the pinentry-qt4 package
but also to pinentry-gtk2 package.

The pinentry password dialog does not support paste in any form, as
far as I can tell.  Neither Ctrl-V nor Ctrl-Shift-V work, nor is
pasting supported through a right-click-accessible context-specific
menu.

Furthermore, the documentation does not describe any support for
pasting passwords from the clipboard.  (In fact, it does not even
explicitly state that pasting is not supported.  This blanket ignoring
password-pasting in the documentation makes the situation only more
irritating, because the user needs to work harder to determine that a
commonly expected feature is in fact not supported.)

In the abscence of support for pasting the password from the
clipboard, the user is forced to type the password in.  This
represents a security threat for two reasons:

1. typing passwords is vulnerable to keyloggers;
2. the need to type passwords encourages users to choose short, and
therefore insecure, passwords.

The second point above is particularly important: *pinentry forces
users to adopt a highly insecure practice.*



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

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

Versions of packages pinentry-qt4 depends on:
ii  libc6 2.19-18+deb8u1
ii  libgcc1   1:4.9.2-10
ii  libncursesw5  5.9+20140913-1+b1
ii  libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1
ii  libstdc++64.9.2-10
ii  libtinfo5 5.9+20140913-1+b1

pinentry-qt4 recommends no packages.

Versions of packages pinentry-qt4 suggests:
ii  pinentry-doc  0.8.3-2

-- no debconf information

Bug#724382: marked as done (Please stop build depending on automake1.9)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 18:51:46 +
with message-id 
and subject line Bug#809674: Removed package(s) from unstable
has caused the Debian Bug report #724382,
regarding Please stop build depending on automake1.9
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.)


-- 
724382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpsdrive
Version: 2.10~pre4-6.dfsg-5.2
Severity: wishlist
Usertags: automake-cleanup-2013

As documented in
http://lists.debian.org/debian-devel/2013/05/msg01459.html, I will be
removing automake1.4, automake1.9 and automake1.10 from the archive.
Your package has a build dependency on one (or more) of these
packages.

In many cases these dependencies are unnecessary as there is typically
no build time dependency on automake for most packages. If it is
required, you should update the dependency to "automake" or
"automake1.11". If you need any assistance with making your package
work with a newer version of automake, please let me know, but it
should be relatively painless for the most part.

I plan to ask for the removal of automake1.4, automake1.9 and
automake1.10 in approximately one month. Once they removed this bug's
severity will be upgraded to "serious".
--- End Message ---
--- Begin Message ---
Version: 2.10~pre4-6.dfsg-5.3+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#646446: marked as done (gpsdrive: FTBFS: mapnik.cpp:33:15: error: 'mapnik::Image32' has not been declared)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 18:51:46 +
with message-id 
and subject line Bug#809674: Removed package(s) from unstable
has caused the Debian Bug report #646446,
regarding gpsdrive: FTBFS: mapnik.cpp:33:15: error: 'mapnik::Image32' has not 
been declared
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.)


-- 
646446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpsdrive
Version: 2.10~pre4-6.dfsg-5.1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20111022 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> if x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. 
> -DLOCALEDIR=\"/usr/share/locale\" -DDATADIR=\"/usr/share\" 
> -DLIBDIR=\"/usr/lib\" -DFRIENDSSERVERVERSION=\"2\"   -DMAPNIK -I/usr/include/ 
> -I/usr/local/include -I/opt/boost_1_35/include/boost-1_35 
> -I/usr/local/include/freetype2 -I/usr/include/freetype2 -I. -L/usr/local/lib 
> -I. -I. -I.. -pthread -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/glib-2.0/include   -DDBUS_API_SUBJECT_TO_CHANGE=1-g -O2  -MT 
> mapnik.o -MD -MP -MF ".deps/mapnik.Tpo" -c -o mapnik.o mapnik.cpp; \
>   then mv -f ".deps/mapnik.Tpo" ".deps/mapnik.Po"; else rm -f 
> ".deps/mapnik.Tpo"; exit 1; fi
> mapnik.cpp:33:15: error: 'mapnik::Image32' has not been declared
> mapnik.cpp:35:15: error: 'mapnik::Layer' has not been declared
> mapnik.cpp:36:15: error: 'mapnik::Envelope' has not been declared
> mapnik.cpp: In function 'void mapnik::render_mapnik()':
> mapnik.cpp:346:5: error: 'Envelope' was not declared in this scope
> mapnik.cpp:346:14: error: expected primary-expression before 'double'
> mapnik.cpp:346:14: error: expected ';' before 'double'
> mapnik.cpp:351:23: error: 'class mapnik::Map' has no member named 'zoomToBox'
> mapnik.cpp:351:33: error: 'box' was not declared in this scope
> mapnik.cpp:353:5: error: 'Image32' was not declared in this scope
> mapnik.cpp:353:13: error: expected ';' before 'buf'
> mapnik.cpp:354:33: error: type/value mismatch at argument 1 in template 
> parameter list for 'template class mapnik::agg_renderer'
> mapnik.cpp:354:33: error:   expected a type, got 'Image32'
> mapnik.cpp:354:38: error: invalid type in declaration before '(' token
> mapnik.cpp:354:57: error: 'buf' was not declared in this scope
> mapnik.cpp:354:60: error: expression list treated as compound expression in 
> initializer [-fpermissive]
> mapnik.cpp:355:9: error: request for member 'apply' in 'ren', which is of 
> non-class type 'int'
> mapnik.cpp:357:53: error: 'class mapnik::Map' has no member named 
> 'getCurrentExtent'
> mapnik.cpp:367:5: error: 'Envelope' is not a member of 'mapnik'
> mapnik.cpp:367:22: error: expected primary-expression before 'double'
> mapnik.cpp:367:22: error: expected ';' before 'double'
> mapnik.cpp:368:26: error: 'ext' was not declared in this scope
> make[4]: *** [mapnik.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2011/10/22/gpsdrive_2.10~pre4-6.dfsg-5.1_lsid64.buildlog

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

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.


--- End Message ---
--- Begin Message ---
Version: 2.10~pre4-6.dfsg-5.3+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#674213: marked as done (gpsdrive: not installable in sid)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 18:51:46 +
with message-id 
and subject line Bug#809674: Removed package(s) from unstable
has caused the Debian Bug report #674213,
regarding gpsdrive: not installable in sid
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.)


-- 
674213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpsdrive
Version: 2.10~pre4-6.dfsg-5.1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi, gpsdrive is not installable in amd64/sid since October 14, 2011, since
it depends on libmapnik0.7 which is only available in squeeze.

-Ralf.


--- End Message ---
--- Begin Message ---
Version: 2.10~pre4-6.dfsg-5.3+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#808513: marked as done (python-django-treebeard: FTBFS: raise AppRegistryNotReady("Apps aren't loaded yet."))

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 18:49:07 +
with message-id 
and subject line Bug#808513: fixed in python-django-treebeard 4.0+dfsg-1
has caused the Debian Bug report #808513,
regarding python-django-treebeard: FTBFS: raise 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.)


-- 
808513: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-treebeard
Version: 3.0+dfsg-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:

Running Sphinx v1.3.3
making output directory...
loading pickled environment... not yet created
loading intersphinx inventory from http://docs.python.org/3/objects.inv...
WARNING: intersphinx inventory 'http://docs.python.org/3/objects.inv' not 
fetchable due to : 
loading intersphinx inventory from 
https://docs.djangoproject.com/en/1.6/_objects/...
WARNING: intersphinx inventory 
'https://docs.djangoproject.com/en/1.6/_objects/' not fetchable due to : 
building [mo]: targets for 0 po files that are out of date
building [html]: targets for 13 source files that are out of date
updating environment: 13 added, 0 changed, 0 removed
reading sources... [  7%] admin
reading sources... [ 15%] al_tree

Exception occurred:
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 124, in 
check_apps_ready
raise AppRegistryNotReady("Apps aren't loaded yet.")
AppRegistryNotReady: Apps aren't loaded yet.
The full traceback has been saved in /tmp/sphinx-err-XKYqh4.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:35: recipe for target 'html' failed
make[2]: *** [html] Error 1
make[2]: Leaving directory '/python-django-treebeard-3.0+dfsg/docs'
debian/rules:13: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: python-django-treebeard
Source-Version: 4.0+dfsg-1

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated 
python-django-treebeard package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 19:21:45 +0100
Source: python-django-treebeard
Binary: python-django-treebeard python3-django-treebeard 
python-django-treebeard-doc
Architecture: source all
Version: 4.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-treebeard - Efficient implementations of tree data structures 
for Django
 python-django-treebeard-doc - Efficient implementations of tree data 
structures for Django (doc
 python3-django-treebeard - Efficient implementations of tree data structures 
for Django (Pyt
Closes: 808513
Changes:
 python-django-treebeard (4.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release.
   * Add patch to initialize django in the sphinx configuration when building
 the documentation (Closes: #808513).
   * Add patch to use local opjects.inv files for intersphinx mappings.
   * Add patch to remove djangodocs extension from sphinx configuration.
   * Drop patch to remove unneeded pytest idmaker hack. It was merged
 upstream.
   * Refresh patch to remove version information from the jquery-ui
 filename.
   * Exclude djangodocs s

Bug#809574: marked as done (heirloom-mailx: FTBFS: sslv3 methods have gone away)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 18:46:22 +
with message-id 
and subject line Bug#809609: Removed package(s) from unstable
has caused the Debian Bug report #809574,
regarding heirloom-mailx: FTBFS: sslv3 methods have gone away
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.)


-- 
809574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: heirloom-mailx
Version: 12.5-5
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:

cc -Wl,-z,relro aux.o base64.o cache.o cmd1.o cmd2.o cmd3.o cmdtab.o collect.o 
dotlock.o edit.o fio.o getname.o getopt.o head.o hmac.o imap.o imap_search.o 
junk.o lex.o list.o lzw.o macro.o maildir.o main.o md5.o mime.o names.o nss.o 
openssl.o pop3.o popen.o quit.o send.o sendout.o smtp.o ssl.o strings.o temp.o 
thread.o tty.o v7.local.o vars.o version.o `grep '^[^#]' LIBS`  -o mailx
openssl.o: In function `ssl_select_method':
/heirloom-mailx-12.5/openssl.c:220: undefined reference to `SSLv3_client_method'
collect2: error: ld returned 1 exit status
Makefile:92: recipe for target 'mailx' failed
make[2]: *** [mailx] Error 1
make[2]: Leaving directory '/heirloom-mailx-12.5'

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Version: 12.5-5+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#759044: marked as done (tribler: Please update to use wxpython3.0)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 18:42:41 +
with message-id 
and subject line Bug#806652: Removed package(s) from unstable
has caused the Debian Bug report #759044,
regarding tribler: Please update to use wxpython3.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.)


-- 
759044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tribler
Version: 6.2.0+git20130731.149555fa-2
Severity: important
Tags: sid jessie
User: freewx-ma...@lists.alioth.debian.org
Usertags: wxpy3.0
Control: block 755757 by -1

We're aiming to migrate the archive to using wxpython3.0 instead of
wxwidgets2.8, and hope to drop wxwidgets2.8 before jessie is released.
This transition is already underway, and is being tracked by the release
team here:

https://release.debian.org/transitions/html/wxpython3.0.html

The wxPython 3.0 API mostly adds to the wxPython2.8 API.  Many packages
work with wxPython 3.0 without any changes, but there are a few
incompatibilities.  For example, wx.Color is no longer supported as
an alias for wx.Colour, and some constants which were deprecated in 2.8
have been removed.  All the removed constants I'm aware of were set to 0
in wxPython 2.8, so removing them is still compatible with 2.8.

To assist updating to wxPython 3.0, I've put together a script which
will help make the mechanical changes required.  This is in a git repo
on collab-maint along with a README about using it and updating packages
for wxPython 3.0 in general:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git

The script has some options to control the sorts of changes it makes -
see the README and --help output for more information - you can view
the latest version of the README online here:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README

I've developed this script by trying to convert 20+ packages.  Please
try it out on your package - in many cases, it should be enough to get
your package working (if it doesn't already) - if it does, please upload
(and close this bug).

If the script doesn't do the job, please let me know (or improve the
script if you can figure out what it needs to do to get your package
working).

Another issue you may hit is that wxWidgets 3.0 now defaults to enabling
its "WXDEBUG" checks for incorrect API usage, so some applications will
emit scary sounding "assertion failures".  These are unlikely to
actually be new, just in a default build of 2.8, such incorrect uses
were handled quietly behind the scenes.  Sometimes these are easy to
fix, but if not you can easily patch the application to tell wx 3.0 to
handle them in the same way wx 2.8 does - details of how to do so are in
the README:

http://anonscm.debian.org/cgit/collab-maint/wx-migration-tools.git/tree/README

I'm happy to sponsor uploads for this transition, though if you have an
active sponsor already check with them first - I don't want to tread on
anyone's toes.

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Version: 6.3.1+git20140902.9a5a2604-3+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#762062: marked as done (wxwidgets2.8: Should not be included in jessie)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 18:43:56 +
with message-id 
and subject line Bug#785079: Removed package(s) from unstable
has caused the Debian Bug report #762062,
regarding wxwidgets2.8: Should not be included in jessie
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.)


-- 
762062: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wxwidgets2.8
Version: 2.8.12.1+dfsg2-2
Severity: serious
Justification: In the package maintainer's opinion this package is unsuitable 
for release

We should not release jessie with wxwidgets2.8.

We have packages of wxwidgets3.0 and wxpython3.0 which are newer
upstream releases of the software in wxwidgets2.8, and most of the
reverse dependencies have already been migrated - by the release freeze
for jessie, we should be down to a very small number of reverse
dependencies unmigrated, most of which we have agreement to remove.

The wxWidgets library is a large and complex piece of software, and
2.8.x is unmaintained upstream.  Even before 3.0 was released, 2.8 was
neglected - the last release was 2.8.12 on 2011-03-28.  By the time
jessie releases, this release will be close to 4 years old.  By the EOL
of jessie (assuming no LTS), it'll be almost 7 years old.

The wx maintainer team in Debian is not a strong one - I've been the
only active member in recent times, though Gianfranco Costamagna has
started to get involved more recently.  Neither of us are interested
in continuing to maintain wxwidgets2.8.

Meanwhile, upstream are currently working towards a new stable release
series, with 3.2.0 slated to be released "in the beginning of 2015" -
source: http://trac.wxwidgets.org/wiki/Roadmap

Historically, upstream's prediction of release dates have tended to be
rather optimistic, but even if they're off by a whole year, we'll still
have a new upstream release series in the lifetime of jessie, which
means some applications will be wanting wxwidgets3.2 packaged in
jessie+1 because they rely on new features added in it.  And we really
don't want to be trying to maintain packages of three different upstream
releases of wx concurrently.

Cheers,
Olly
--- End Message ---
--- Begin Message ---
Version: 2.8.12.1+dfsg2-2+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Luca Falavigna (the ftpmaster behind the curtain)--- End Message ---

Bug#809596: marked as done (sympy: FTBFS: sympy-0.7.6.pdf build fails (pdftex missing?))

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 18:35:11 +
with message-id 
and subject line Bug#809596: fixed in sympy 0.7.6.1-1
has caused the Debian Bug report #809596,
regarding sympy: FTBFS: sympy-0.7.6.pdf build fails (pdftex missing?)
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.)


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

copying TeX support files...
done
build succeeded, 99 warnings.
sed -i "s/pdflatex/xelatex/g" _build/latex/Makefile

Build finished; the LaTeX files are in _build/latex.
Run `make all' in that directory to run these through xelatex.
make[2]: Leaving directory '/sympy-0.7.6/doc'
make[2]: Entering directory '/sympy-0.7.6/doc/_build/latex'
xelatex  'sympy-0.7.6.tex'
This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015/Debian) (preloaded 
format=xelatex)
 restricted \write18 enabled.
entering extended mode
(./sympy-0.7.6.tex
LaTeX2e <2015/10/01> patch level 2
Babel <3.9m> and hyphenation patterns for 2 languages loaded.
(./sphinxmanual.cls
Document Class: sphinxmanual 2009/06/02 Document class (Sphinx manual)
(/usr/share/texlive/texmf-dist/tex/latex/base/report.cls
Document Class: report 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)))
(/usr/share/texlive/texmf-dist/tex/latex/cmap/cmap.sty

Package cmap Warning: pdftex not detected - exiting.

) (/usr/share/texlive/texmf-dist/tex/latex/tools/bm.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
(/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/l3xdvipdfmx.def))
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)
(/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-patches.sty)
(/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1enc.def)
(/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1lmr.fd))
(/usr/share/texlive/texmf-dist/tex/xelatex/xunicode/xunicode.sty
(/usr/share/texmf/tex/latex/tipa/t3enc.def
(/usr/share/texlive/texmf-dist/tex/latex/euenc/eu1lmss.fd))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/graphics.cfg)
(/usr/share/texlive/texmf-dist/tex/xelatex/xetex-def/xetex.def
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
(/usr/share/texlive/texmf-dist/tex/latex/fontspec/fontspec.cfg)))
(./fncychap.sty) (/usr/share/texlive/texmf-dist/tex/latex/tools/longtable.sty)
(./sphinx.sty (/usr/share/texlive/texmf-dist/tex/latex/fancyhdr/fancyhdr.sty)
(/usr/share/texlive/texmf-dist/tex/latex/base/textcomp.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/ts1enc.def))
(/usr/share/texlive/texmf-dist/tex/latex/fancybox/fancybox.sty
Style option: `fancybox' v1.4 <2010/05/15> (tvz)
) (/usr/share/texlive/texmf-dist/tex/latex/titlesec/titlesec.sty)
(./tabulary.sty (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
For additional information on amsmath, use the `?' option.
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
(/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty)
(/usr/share/texlive/texmf-dist/tex/latex/framed/framed.sty)
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/color.cfg))
(/usr/share/texlive/texmf-dist/tex/latex/fancyvrb/fancyvrb.sty
Style option: `fancyvrb' v2.7a, with DG

Processed: fixed 809602 in 2.4.1-2

[Debian Bug Tracking System]

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

> fixed 809602 2.4.1-2
Bug #809602 [bnd] javamail: FTBFS: [ERROR] Java heap space -> [Help 1]
Marked as fixed in versions bnd/2.4.1-2.
> thanks
Stopping processing here.

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

Processed: closing 809602

[Debian Bug Tracking System]

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

> close 809602
Bug #809602 [bnd] javamail: FTBFS: [ERROR] Java heap space -> [Help 1]
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#809283: marked as done (libuv: FTBFS: dh_install: cp: cannot stat 'debian/tmp/debian/tmp/dh-exec.AUyQ2PO5/usr/lib/x86_64-linux-gnu/libuv.so.0.10': No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 17:49:41 +
with message-id 
and subject line Bug#809283: fixed in dh-exec 0.23
has caused the Debian Bug report #809283,
regarding libuv: FTBFS: dh_install: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.AUyQ2PO5/usr/lib/x86_64-linux-gnu/libuv.so.0.10':
 No such file or directory
to be marked as done.

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

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


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

libuv fails to build from source in unstable/amd64:

  [..]

 debian/rules override_dh_auto_install
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20151229000733.Wcv23SXMSm/libuv-0.10.36'
  dh_auto_install
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151229000733.Wcv23SXMSm/libuv-0.10.36'
 dh_install
  cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.AUyQ2PO5/usr/lib/x86_64-linux-gnu/libuv.so.0.10':
 No such file or directory
  dh_install: cp --reflink=auto -a 
debian/tmp/debian/tmp/dh-exec.AUyQ2PO5/usr/lib/x86_64-linux-gnu/libuv.so.0.10 
debian/libuv0.10/usr/lib/x86_64-linux-gnu// returned exit code 1
  debian/rules:14: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

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


libuv.0.10.36-3.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: dh-exec
Source-Version: 0.23

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

Debian distribution maintenance software
pp.
Gergely Nagy  (supplier of updated dh-exec 
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, 02 Jan 2016 18:05:04 +0100
Source: dh-exec
Binary: dh-exec
Architecture: source
Version: 0.23
Distribution: unstable
Urgency: high
Maintainer: Gergely Nagy 
Changed-By: Gergely Nagy 
Description:
 dh-exec- Scripts to help with executable debhelper files
Closes: 809283
Changes:
 dh-exec (0.23) unstable; urgency=high
 .
   * Fix the DH_CONFIG_ACT_ON_PACKAGES support so that it works on packages
 with dots in their name too. Thanks to Chris Lamb, Luca Bruno, Niels
 Thykier, and Mattia Rizzolo for the report and help in tracking down
 the issue. (Closes: #809283)
   * Urgency set to high, because the above regression causes other
 packages to FTBFS.
Checksums-Sha1:
 19bd72e6b1e175d081fd77df674d71367979a0c3 1658 dh-exec_0.23.dsc
 eb9c28bce61adf70b41ef912fd64b956270b4603 34268 dh-exec_0.23.tar.xz
Checksums-Sha256:
 f9d516b414865a5fe3ad0a0c2e7f7e9f61261776875ef3bbdf2c623a4397231d 1658 
dh-exec_0.23.dsc
 578da63559564f1d19c4270f6a305263003d6c3011473c0fb7756b08c2bc1dd7 34268 
dh-exec_0.23.tar.xz
Files:
 9a7b874c21b0247dba0e895ae68a3605 1658 devel extra dh-exec_0.23.dsc
 7f37d90a1018af608c1df78a9c0adf2c 34268 devel extra dh-exec_0.23.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWiAjZAAoJEKwekLrEM/aPw78P/24uuY5lfxuhbOxBJxaJAV1n
eJxFMBy/BzYNm4kVwyCClwBe2Pejfemm02RguXuqfXhgnfb3+VVdJIlyfLa3Hzk6
WUbAdrTJNp1+UfY9qf1XMGXVJa6HcPGRpScqWEquVFql/Y6X5WbcVjBIAjUSaw2j
4oIqSooRAAyBD+mZ4KKnqVYCnDVwb+/fhaWFNKaZ2lwUMFyIGnYV+zTp2dqB9OGj
qX7KdCZ+EjGhfnerebqEHVWkAc/RboCfK/Iae3Q+u42KoY+rEwkNX4ESC7M18WCW
+lxxGIEp4IYNzIWuPPTK2koa0dFQoTSRmWavd2gsdelm8T/HgT2RQK1YzqDoLVAm
JSSLsPBUBWZY/rWSFudMe2xB+pWVSNaK0T39QfazfppWd/rmUE0Rb/W0TFB20hGS
2dctXcbPtAODt+iB2/xJ4w52PzkWWfJ52SY4EIwIrFdW/jSnJpOoBnvgcB1TDImL
IqUXJ6SL3l4eTqIG11ZuKmkNvDkv31O3jFFtEwNDfJdRH8Ihajgzr+BJIdPuazF7
bxN5ypb90N2dKAWoqQua9dWFf/a/sVgzOLxE4qnFV0AXTwjx6Mq3BPDY3HahX+FF
JwuYouFyYpyBZwrYuqoMxETbR0iKefRQuGeTl+gnbk17L9mEa2NTxfpX8rHC18gi
WC0NoxswsY7FtYyr+v9U
=Xzbq
-END PGP SIGNATURE End Message ---

Bug#807645: marked as done (ifupdown package fails to configure itself (by dpkg))

[Debian Bug Tracking System]

Your message dated Sat, 2 Jan 2016 18:35:19 +0100
with message-id <20160102173519.gp8...@sliepen.org>
and subject line Re: Bug#807645: ifupdown package fails to configure itself (by 
dpkg)
has caused the Debian Bug report #807645,
regarding ifupdown package fails to configure itself (by dpkg)
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.)


-- 
807645: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ifupdown
Version: 0.8.2
Severity: serious
Justification: fail to configure itself

  Hi,

  I just upgraded ifupdown and it fails to configure itself.
I've added "set -x" to /var/lib/dpkg/info/ifupdown.postinst and
a final "echo done $?" at the end of /lib/systemd/systemd-sysv-install. Here
are the results:

# LC_ALL=C dpkg -a --configure
Setting up ifupdown (0.8.2) ...
+ MYNAME=ifupdown.postinst
+ [ configure = configure ]
+ addgroup --quiet --system netdev
+ [ configure = configure ]
+ [ ! -f /etc/network/interfaces ]
+ [ configure = configure ]
+ [ -x /etc/init.d/networking ]
+ update-rc.d networking defaults
+ [ configure = configure ]
+ [ -e /etc/udev/rules.d/z60_ifupdown.rules ]
+ dpkg-maintscript-helper rm_conffile /etc/default/ifupdown 0.7~+ ifupdown -- 
configure 0.7.54
+ dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown 0.7~+ ifupdown -- 
configure 0.7.54
+ dpkg-maintscript-helper rm_conffile /etc/init.d/ifupdown-clean 0.7~beta1 
ifupdown -- configure 0.7.54
+ [ configure = configure -a -e /bin/systemctl ]
+ [ -z 0.7.54 ]
+ dpkg --compare-versions 0.7.54 lt 0.8
+ echo Enabling networking.service.
Enabling networking.service.
+ systemctl enable networking.service
Synchronizing state of networking.service with SysV init with 
/lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable networking
done 0
Failed to execute operation: File exists
dpkg: error processing package ifupdown (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 ifupdown
#

So, something is wrong with the "systemctl enable networking.service" call but
is is not the /lib/systemd/systemd-sysv-install invocation.

Using "strace -f -o /tmp/strace.out2 systemctl enable networking.service" did
not help me to find which file is already existing.

  Regards,
Vincent

-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'oldstable-updates'), (500, 
'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 
'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, mipsel

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

Versions of packages ifupdown depends on:
ii  adduser   3.113+nmu3
ii  iproute2  4.3.0-1
ii  libc6 2.19-22
ii  lsb-base  9.20150917

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.3.3-5

Versions of packages ifupdown suggests:
ii  ppp 2.4.7-1+1
pn  rdnssd  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.8.4

On Sat, Jan 02, 2016 at 06:18:35PM +0100, Marco d'Itri wrote:

> > Can you check whether 0.8.4 works better? That one uses dh-systemd.
> Sorry, I forgot to update the bug: since the next release I was unable 
> to reproduce the bug.

No problem, closing the bug then.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


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

Bug#802950: norwegian: FTBFS when awk is mawk

[Petter Reinholdtsen]

[Robert Luberda]
> `--source' seems to be supported by GNU awk only.

Tollef, what is your view here?  Should the build be changed to
always use gawk, or rewritten to not use --source?
-- 
Happy hacking
Petter Reinholdtsen

Bug#790765: FTBFS: [munched.A] Error 1

[Petter Reinholdtsen]

[Tollef Fog Heen]
> Indeed it does.  Seems to be caused by
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794152

This bug is fixed in ispell now.  Should this bug be closed as fixed too?
-- 
Happy hacking
Petter Reinholdtsen

Bug#807645: ifupdown package fails to configure itself (by dpkg)

[Marco d'Itri]

On Jan 02, Guus Sliepen  wrote:

> Can you check whether 0.8.4 works better? That one uses dh-systemd.
Sorry, I forgot to update the bug: since the next release I was unable 
to reproduce the bug.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#809671: should openmeeg be removed from Debian?

[Mattia Rizzolo]

On Sat, Jan 02, 2016 at 12:04:07PM -0500, Yaroslav Halchenko wrote:
> On Sat, 02 Jan 2016, Mattia Rizzolo wrote:
> I would not call it dead upstream.  It is a research project after all -
> so people develop it whenever there is need.

ok, sorry, I must have looked to either the wrong place, or in the wrong
way.

> I will look into fixing packaging up one way or another within a
> week or two, ok?  and if I upload new release, I will close this one

that's cool, thanks for fixing it!

-- 
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#809293: marked as done (linux-image-3.16.0-4-amd64: network regression in 3.16.7-ckt20-1+deb8u1 breaks ipv6 ike/ipsec negotiations)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 17:06:48 +
with message-id 
and subject line Bug#808293: fixed in linux-2.6 2.6.32-48squeeze18
has caused the Debian Bug report #808293,
regarding linux-image-3.16.0-4-amd64: network regression in 
3.16.7-ckt20-1+deb8u1 breaks ipv6 ike/ipsec negotiations
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.)


-- 
808293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u1
Severity: normal

Following the recent kernel security update, racoon(8) from ipsec-tools
can no longer negotiate an IPSec security association with an ipv6 peer.
IPv4 does not appear affected.

Racoon logs the following:
Dec 28 13:20:42 amarth racoon: ERROR: recvmsg (Resource temporarily unavailable)
Dec 28 13:20:42 amarth racoon: ERROR: failed to receive isakmp packet at 
isakmp.c:238: Resource temporarily unavailable

This happens when trying to read an IKE (udp port 500) message from the
peer.

Downgrading to 3.16.7-ckt11-1+deb8u3 resolves the problem.

My first guess was that it was related to the recently added
net-add-validation-for-the-socket-syscall-protocol.patch fix, so I tried
backing that out, but it didn't help. Then I realized that there were a
lot more changes between 3.16.7-ckt11-1+deb8u3 and 3.16.7-ckt20-1+deb8u1
than what were described in the DSA. I'm attempting to identify the
specific commit (at least to the debian packaging repo, if not the
actual ckt kernel)

Thanks
Noah

-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt20-1+deb8u1 (2015-12-14)

** Command line:
BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/amarth--vg-root ro include 
console=tty1 console=ttyS0,115200

** Not tainted

** Kernel log:
[7.248625] systemd[1]: Starting Syslog Socket.
[7.264080] systemd[1]: Listening on Syslog Socket.
[7.269054] systemd[1]: Starting Journal Service...
[7.292065] systemd[1]: Started Journal Service.
[7.537734] systemd-udevd[205]: starting version 215
[7.922679] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[7.930230] ACPI: Power Button [PWRF]
[8.020609] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[8.041411] ipmi message handler version 39.2
[8.093982] intel_rng: FWH not detected
[8.098337] IPMI System Interface driver.
[8.102708] ipmi_si: probing via SMBIOS
[8.106607] ipmi_si: SMBIOS: io 0xca8 regsize 1 spacing 4 irq 0
[8.112626] ipmi_si: Adding SMBIOS-specified kcs state machine
[8.118574] ipmi_si: Trying SMBIOS-specified kcs state machine at i/o 
address 0xca8, slave address 0x20, irq 0
[8.152503] input: PC Speaker as /devices/platform/pcspkr/input/input6
[8.177073] EDAC MC: Ver: 3.0.0
[8.192219] EDAC MC0: Giving out device to module i5000_edac.c controller 
I5000: DEV :00:10.0 (POLLED)
[8.201979] EDAC PCI0: Giving out device to module i5000_edac controller 
EDAC PCI controller: DEV :00:10.0 (POLLED)
[8.313606] [drm] Initialized drm 1.1.0 20060810
[8.328595] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.2)
[8.364313] ipmi_si ipmi_si.0: Found new BMC (man_id: 0x0002a2, prod_id: 
0x0100, dev_id: 0x20)
[8.373025] ipmi_si ipmi_si.0: IPMI kcs interface initialized
[8.414596] iTCO_vendor_support: vendor-support=0
[8.419814] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[8.425511] iTCO_wdt: Found a 631xESB/632xESB TCO device (Version=2, 
TCOBASE=0x0860)
[8.433453] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[8.613050] [drm] radeon kernel modesetting enabled.
[8.618713] [drm] initializing kernel modesetting (RV100 0x1002:0x515E 
0x1028:0x01B2).
[8.626780] [drm] register mmio base: 0xFC2D
[8.631475] [drm] register mmio size: 65536
[8.635822] radeon :0e:0d.0: VRAM: 128M 0xD800 - 
0xDFFF (16M used)
[8.644525] radeon :0e:0d.0: GTT: 512M 0xB800 - 
0xD7FF
[8.652220] [drm] Detected VRAM RAM=128M, BAR=128M
[8.657090] [drm] RAM width 16bits DDR
[8.660836] [TTM] Zone  kernel: Available graphics memory: 1026588 kiB
[8.667472] [TTM] Initializing pool allocator
[8.673206] [TTM] Initializing DMA pool allocator
[8.679313] [drm] radeon: 16M of VRAM memory ready
[8.685456] [drm] radeon: 512M of GTT memory ready.
[8.693034] [drm] GART: num cpu pages 131072, num gpu pages 131072

Bug#808293: marked as done (Regression in short UDP reads caused by "net: Fix skb csum races when peeking")

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 17:06:48 +
with message-id 
and subject line Bug#808293: fixed in linux-2.6 2.6.32-48squeeze18
has caused the Debian Bug report #808293,
regarding Regression in short UDP reads caused by "net: Fix skb csum races when 
peeking"
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.)


-- 
808293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freeradius
Version: 2.1.12+dfsg-1.2
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

I just upgraded libc and kernel image:
# tail /var/log/apt/history.log

Start-Date: 2015-12-18  09:22:57
Commandline: apt-get upgrade -y
Upgrade: linux-libc-dev:i386 (3.2.68-1+deb7u6, 3.2.73-2+deb7u1), 
linux-image-3.2.0-4-686-pae:i386 (3.2.68-1+deb7u6, 3.2.73-2+deb7u1)
End-Date: 2015-12-18  09:23:15

Start-Date: 2015-12-18  10:30:59
Commandline: apt-get install strace
Install: strace:i386 (4.5.20-2.3)
End-Date: 2015-12-18  10:31:04

After reboot, I noticed that freeradius stopped processing requests.
This is freeradius -X output:
# freeradius -X
FreeRADIUS Version 2.1.12, for host i486-pc-linux-gnu, built on Dec 16 2012 at 
22:03:33
Copyright (C) 1999-2009 The FreeRADIUS server project and contributors.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
You may redistribute copies of FreeRADIUS under the terms of the
GNU General Public License v2.
Starting - reading configuration files ...
including configuration file /etc/freeradius/radiusd.conf
including configuration file /etc/freeradius/proxy.conf
including configuration file /etc/freeradius/clients.conf
including files in directory /etc/freeradius/modules/
including configuration file /etc/freeradius/modules/preprocess
including configuration file /etc/freeradius/modules/redis
including configuration file /etc/freeradius/modules/ippool
including configuration file /etc/freeradius/modules/expiration
including configuration file /etc/freeradius/modules/detail.log
including configuration file /etc/freeradius/modules/expr
including configuration file /etc/freeradius/modules/digest
including configuration file /etc/freeradius/modules/files
including configuration file /etc/freeradius/modules/attr_filter
including configuration file /etc/freeradius/modules/linelog
including configuration file /etc/freeradius/modules/echo
including configuration file /etc/freeradius/modules/detail.example.com
including configuration file /etc/freeradius/modules/chap
including configuration file /etc/freeradius/modules/soh
including configuration file /etc/freeradius/modules/passwd
including configuration file /etc/freeradius/modules/rediswho
including configuration file /etc/freeradius/modules/dynamic_clients
including configuration file /etc/freeradius/modules/checkval
including configuration file /etc/freeradius/modules/mschap
including configuration file /etc/freeradius/modules/acct_unique
including configuration file /etc/freeradius/modules/perl
including configuration file /etc/freeradius/modules/detail
including configuration file /etc/freeradius/modules/attr_rewrite
including configuration file /etc/freeradius/modules/sql_log
including configuration file /etc/freeradius/modules/replicate
including configuration file /etc/freeradius/modules/smbpasswd
including configuration file /etc/freeradius/modules/mac2ip
including configuration file /etc/freeradius/modules/etc_group
including configuration file /etc/freeradius/modules/pam
including configuration file /etc/freeradius/modules/mac2vlan
including configuration file /etc/freeradius/modules/unix
including configuration file /etc/freeradius/modules/policy
including configuration file /etc/freeradius/modules/always
including configuration file /etc/freeradius/modules/exec
including configuration file /etc/freeradius/modules/pap
including configuration file /etc/freeradius/modules/opendirectory
including configuration file /etc/freeradius/modules/counter
including configuration file /etc/freeradius/modules/ldap
including configuration file /etc/freeradius/modules/ntlm_auth
including configuration file /etc/freeradius/modules/realm
including configuration file /etc/freeradius/modules/smsotp
including configuration file /etc/freeradius/modules/cui
including configuration file /etc/freeradius/modules/radutmp
including configuration file /etc/freeradius/modules/krb5
including configuration file /etc/freeradius/modules/wimax
including configuration file /etc/freeradius/modules/inner-eap
including configuration file /et

Bug#808374: marked as done (linux-image-3.16.0-4-686-pae: FreeRADIUS EAP-TLS stopped working when kernel was updated)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 17:06:48 +
with message-id 
and subject line Bug#808293: fixed in linux-2.6 2.6.32-48squeeze18
has caused the Debian Bug report #808293,
regarding linux-image-3.16.0-4-686-pae: FreeRADIUS EAP-TLS stopped working when 
kernel was updated
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.)


-- 
808293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u1
Severity: important

Dear Maintainer,

After updating the kernel with the latest security release FreeRADIUS
seem to be unable to process the UDP packets it is receiving.  As you
can see in this strace there's some error occuring with the recvfrom()
that is triggered by the incoming packet.  Downgrading the kernel to
linux-image-3.16.0-4-686-pae:i386 3.16.7-ckt11-1+deb8u6 makes it work
again.

This is a i686 domU on a X86_64 XEN host if that matters.


When using current kernel:

execve("/usr/sbin/freeradius", ["freeradius", "-s"], [/* 21 vars */]) = 0
brk(0)  = 0x9e47000
access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or
directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb77c5000
mmap2(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb77c2000
[...]
select(10, [4 6 7 8 9], NULL, NULL, NULL) = 1 (in [6])
recvfrom(6, 0xbf9909c8, 4, 2, 0xbf990948, 0xbf990944) = -1 EAGAIN
(Resource temporarily unavailable)
select(10, [4 6 7 8 9], NULL, NULL, NULL) = 1 (in [6])
recvfrom(6, 0xbf9909c8, 4, 2, 0xbf990948, 0xbf990944) = -1 EAGAIN
(Resource temporarily unavailable)
select(10, [4 6 7 8 9], NULL, NULL, NULL) = 1 (in [6])
recvfrom(6, 0xbf9909c8, 4, 2, 0xbf990948, 0xbf990944) = -1 EAGAIN
(Resource temporarily unavailable)
select(10, [4 6 7 8 9], NULL, NULL, NULL) = ? ERESTARTNOHAND (To be
restarted if no handler)
--- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL,
si_value={int=1851877730, ptr=0x6e616962}} ---
exit_group(2)   = ?
+++ exited with 2 +++

When using the linux-image-3.16.0-4-686-pae:i386 3.16.7-ckt11-1+deb8u6
kernel - which is working:

select(10, [4 6 7 8 9], NULL, NULL, NULL) = 1 (in [6])
recvfrom(6, "\1\f\0\244", 4, MSG_PEEK, {sa_family=AF_INET,
sin_port=htons(39163), sin_addr=inet_addr("192.168.20.25")}, [16]) = 4
getsockname(6, {sa_family=AF_INET, sin_port=htons(1812),
sin_addr=inet_addr("0.0.0.0")}, [16]) = 0
recvfrom(6, "\1\f\0\244", 4, MSG_PEEK, {sa_family=AF_INET,
sin_port=htons(39163), sin_addr=inet_addr("192.168.20.25")}, [16]) = 4
getsockname(6, {sa_family=AF_INET, sin_port=htons(1812),
sin_addr=inet_addr("0.0.0.0")}, [16]) = 0
recvmsg(6, {msg_name(16)={sa_family=AF_INET, sin_port=htons(39163),
sin_addr=inet_addr("192.168.20.25")},
msg_iov(1)=[{"\1\f\0\244_\7\317Y\232\343U\306\6
\\\312\31\2775\315\1\10nobody\4\6\300\250"..., 164}], msg_controllen=24,
{cmsg_len=24, cmsg_level=SOL_IP, cmsg_type=, ...}, msg_flags=0}, 0) = 164

I don't have any clue as to what change has caused the problem though..

/Andreas Sundstrom


-- Package-specific info:
** Version:
Linux version 3.16.0-4-686-pae (debian-ker...@lists.debian.org) (gcc
version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt20-1+deb8u1
(2015-12-14)

** Command line:
root=UUID=4692e988-b453-4884-bbf0-43c29565b821 ro  quiet

** Not tainted

** Kernel log:
[1.558784] xenbus_probe_frontend: Device with no driver:
device/vbd/51760
[1.558785] xenbus_probe_frontend: Device with no driver:
device/vbd/51776
[1.558786] xenbus_probe_frontend: Device with no driver:
device/vbd/51792
[1.558787] xenbus_probe_frontend: Device with no driver:
device/vbd/51808
[1.558788] xenbus_probe_frontend: Device with no driver:
device/vbd/51824
[1.558789] xenbus_probe_frontend: Device with no driver:
device/vbd/51840
[1.558790] xenbus_probe_frontend: Device with no driver:
device/vbd/51856
[1.558791] xenbus_probe_frontend: Device with no driver: device/vif/0
[1.558871] rtc_hctosys: unable to open rtc device (rtc0)
[1.558896] PM: Hibernation image not present or could not be loaded.
[1.559264] Freeing unused kernel memory: 656K (c1671000 - c1715000)
[1.560167] Write protecting the kernel text: 4612k
[1.560455] Write protecting the kernel read-only data: 1456k
[1.560457] NX-protecting the kernel data: 3580k
[1.579136] systemd-udevd[63]: starting version 215
[1.579513] random: systemd-udevd urandom read with 16 bits of
entropy available
[1.591625] xen_netfront: Initialising Xen v

Bug#808431: marked as done (linux-source-3.16: FreeRADIUS stopped working when kernel was updated to 3.16.7-ckt20)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 17:06:48 +
with message-id 
and subject line Bug#808293: fixed in linux-2.6 2.6.32-48squeeze18
has caused the Debian Bug report #808293,
regarding linux-source-3.16: FreeRADIUS stopped working when kernel was updated 
to 3.16.7-ckt20
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.)


-- 
808293: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-source-3.16
Version: 3.16.7-ckt-20
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
Upgrading the Kernel from 3.16.7-ckt11 to 3.16.7-ckt20 (compiled from
source each) broke FreeRADIUS. The freeradius daemon stopped responding to udp
auth queries from locally installed hostapd wifi daemon. Wifi clients using
EAP-TLS auth cannot authenticate an more.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Downgrade to Kernel 3.16.7-ckt11 fixed the issue.

   * What was the outcome of this action?
   * What outcome did you expect instead?

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



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: linux-2.6
Source-Version: 2.6.32-48squeeze18

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux-2.6 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 03:31:10 +
Source: linux-2.6
Binary: linux-tools-2.6.32 linux-source-2.6.32 linux-doc-2.6.32 
linux-manual-2.6.32 linux-patch-debian-2.6.32 firmware-linux-free 
linux-support-2.6.32-5 linux-base linux-libc-dev linux-headers-2.6.32-5-all 
linux-headers-2.6.32-5-all-alpha linux-headers-2.6.32-5-common 
linux-image-2.6.32-5-alpha-generic linux-headers-2.6.32-5-alpha-generic 
linux-image-2.6.32-5-alpha-smp linux-headers-2.6.32-5-alpha-smp 
linux-image-2.6.32-5-alpha-legacy linux-headers-2.6.32-5-alpha-legacy 
linux-headers-2.6.32-5-all-amd64 linux-image-2.6.32-5-amd64 
linux-headers-2.6.32-5-amd64 linux-image-2.6.32-5-amd64-dbg 
linux-headers-2.6.32-5-common-openvz linux-image-2.6.32-5-openvz-amd64 
linux-headers-2.6.32-5-openvz-amd64 linux-image-2.6.32-5-openvz-amd64-dbg 
linux-headers-2.6.32-5-common-vserver linux-image-2.6.32-5-vserver-amd64 
linux-headers-2.6.32-5-vserver-amd64 linux-image-2.6.32-5-vserver-amd64-dbg 
linux-headers-2.6.32-5-common-xen linux-image-2.6.32-5-xen-amd64 
linux-headers-2.6.32-5-xen-amd64
 linux-image-2.6.32-5-xen-amd64-dbg xen-linux-system-2.6.32-5-xen-amd64 
linux-headers-2.6.32-5-all-armel linux-image-2.6.32-5-iop32x 
linux-headers-2.6.32-5-iop32x linux-image-2.6.32-5-ixp4xx 
linux-headers-2.6.32-5-ixp4xx linux-image-2.6.32-5-kirkwood 
linux-headers-2.6.32-5-kirkwood linux-image-2.6.32-5-orion5x 
linux-headers-2.6.32-5-orion5x linux-image-2.6.32-5-versatile 
linux-headers-2.6.32-5-versatile linux-headers-2.6.32-5-all-hppa 
linux-image-2.6.32-5-parisc linux-headers-2.6.32-5-parisc 
linux-image-2.6.32-5-parisc-smp linux-headers-2.6.32-5-parisc-smp 
linux-image-2.6.32-5-parisc64 linux-headers-2.6.32-5-parisc64 
linux-image-2.6.32-5-parisc64-smp linux-headers-2.6.32-5-parisc64-smp 
linux-headers-2.6.32-5-all-i386 linux-image-2.6.32-5-486 
linux-headers-2.6.32-5-486 linux-image-2.6.32-5-686 linux-headers-2.6.32-5-686 
linux-image-2.6.32-5-686-bigmem linux-headers-2.6.32-5-686-bigmem 
linux-image-2.6.32-5-686-bigmem-dbg linux-image-2.6.32-5-openvz-686
 linux-headers-2.6.32-5-openvz-686 linux-image-2.6.32-5-openvz-686-dbg 
linux-image-2.6.32-5-vserver-686 linux-headers-2

Bug#809671: should openmeeg be removed from Debian?

[Yaroslav Halchenko]

On Sat, 02 Jan 2016, Mattia Rizzolo wrote:
> openmeeg is in a very bad state, it's unbuildable, and has an unfixed RC
> bug since more than 2 years.
> It missed the Jessie release, and I don't see any work going on either
> upstream or in debian.

well -- there is work done upstream.  Not super active but project is
live

Debian:

> ATM it has 2 RC bug, last maintainer upload 2012-06-25, and a lowish
> popcon (Inst < 200, but most are No Files or Old).

> Furthermore it is currently uninstallable due to the removal of
> python-support.

> Thanks for considering.

> RM: openmeeg -- RoQA; unmaintained; RC-buggy; dead upstream; low popcon

I would not call it dead upstream.  It is a research project after all -
so people develop it whenever there is need.

I will look into fixing packaging up one way or another within a
week or two, ok?  and if I upload new release, I will close this one

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

Bug#802414: marked as done (python-requirements-detector: FTBFS: AttributeError: 'Call' object has no attribute 'starargs')

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 17:04:51 +
with message-id 
and subject line Bug#800788: fixed in astroid 1.4.1-1
has caused the Debian Bug report #800788,
regarding python-requirements-detector: FTBFS: AttributeError: 'Call' object 
has no attribute 'starargs'
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.)


-- 
800788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-requirements-detector
Version: 0.4-2
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:

==
ERROR: test_subscript_assign (tests.test_detection.DependencyDetectionTest)
--
Traceback (most recent call last):
  File "/python-requirements-detector-0.4/tests/test_detection.py", line 81, in 
test_subscript_assign
self._test_setup_py('subscript_assign.py', 'Django==1.5.0', 
'django-gubbins==1.1.2')
  File "/python-requirements-detector-0.4/tests/test_detection.py", line 63, in 
_test_setup_py
dependencies = from_setup_py(filepath)
  File "/python-requirements-detector-0.4/requirements_detector/detect.py", 
line 201, in from_setup_py
ast = AstroidBuilder(MANAGER).string_build(contents)
  File "/usr/lib/python3/dist-packages/astroid/builder.py", line 139, in 
string_build
module = self._data_build(data, modname, path)
  File "/usr/lib/python3/dist-packages/astroid/builder.py", line 177, in 
_data_build
module = rebuilder.visit_module(node, modname, node_file, package)
  File "/usr/lib/python3/dist-packages/astroid/rebuilder.py", line 148, in 
visit_module
newnode.body = [self.visit(child, newnode) for child in node.body]
  File "/usr/lib/python3/dist-packages/astroid/rebuilder.py", line 148, in 

newnode.body = [self.visit(child, newnode) for child in node.body]
  File "/usr/lib/python3/dist-packages/astroid/rebuilder.py", line 161, in visit
return self._transform(visit_method(node, parent))
  File "/usr/lib/python3/dist-packages/astroid/rebuilder.py", line 238, in 
visit_assign
newnode.value = self.visit(node.value, newnode)
  File "/usr/lib/python3/dist-packages/astroid/rebuilder.py", line 161, in visit
return self._transform(visit_method(node, parent))
  File "/usr/lib/python3/dist-packages/astroid/rebuilder.py", line 331, in 
visit_callfunc
if node.starargs is not None:
AttributeError: 'Call' object has no attribute 'starargs'

...

--
Ran 26 tests in 0.083s

FAILED (errors=8)
E: pybuild pybuild:262: test: plugin custom failed with: exit code=1: 
LC_ALL=C.UTF-8 python3.5 -m nose --verbose
dh_auto_test: pybuild --test --test-nose -i python{version} -p 3.5 3.4 --dir . 
returned exit code 13

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated astroid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Jan 2016 16:36:00 +
Source: astroid
Binary: python-astroid python3-astroid
Architecture: source all
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-astroid - rebuild a new abstract syntax tree from Python's AST
 python3-astroid - rebuild a new abstract syntax tree from Python's AST 
(Python3)
Closes: 790884 800788
Changes:
 astroid (1.4.1-1) unstable; urgency=medium
 .

Bug#800788: marked as done (python3-astroid: not fit for Python 3.5)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 17:04:51 +
with message-id 
and subject line Bug#800788: fixed in astroid 1.4.1-1
has caused the Debian Bug report #800788,
regarding python3-astroid: not fit for Python 3.5
to be marked as done.

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

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


-- 
800788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-astroid
Version: 1.3.8-1
Severity: normal
Control: affects -1 src:python-requirements-detector

Hi,

just wanted to share the info that current python3-astroid is running into
a problem with Python 3.5. I've discovered this [1] through the tests of
python3-requirements-detector [2].

Best,
DS

[1] 
https://bitbucket.org/logilab/astroid/issues/187/call-object-has-no-attribute-starargs

[2] 
http://ci.debian.net/data/packages/unstable/amd64/p/python-requirements-detector/20151001_223040.autopkgtest.log.gz

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

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

Versions of packages python3-astroid depends on:
ii  python3-logilab-common  1.0.2-1
ii  python3-six 1.9.0-5
pn  python3:any 

python3-astroid recommends no packages.

python3-astroid suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: astroid
Source-Version: 1.4.1-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated astroid package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Jan 2016 16:36:00 +
Source: astroid
Binary: python-astroid python3-astroid
Architecture: source all
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-astroid - rebuild a new abstract syntax tree from Python's AST
 python3-astroid - rebuild a new abstract syntax tree from Python's AST 
(Python3)
Closes: 790884 800788
Changes:
 astroid (1.4.1-1) unstable; urgency=medium
 .
   * New upstream release
 - add support for Python 3.5; Closes: #800788
 - correctly handle multiprocessing; Closes: #790884
   * debian/copyright
 - extend packaging copyright years
   * debian/control
 - add wrapt and lazy_object_proxy to b-d, needed to trigger the packages
   dependencies detection
Checksums-Sha1:
 81006568b6adb78d156a10b41cf896972e3246e6 2163 astroid_1.4.1-1.dsc
 56c1e9387035ff9c930c1e2a3f3e6a1e5b21ed00 179485 astroid_1.4.1.orig.tar.gz
 04da702a0e3647c6a591c195b58efa635e266f7d 3496 astroid_1.4.1-1.debian.tar.xz
 fb46ab089ed552996492cd3dfd2a90fbb1f00bee 86336 python-astroid_1.4.1-1_all.deb
 5273fb8a96843f79d51898297c1d45b383c37d01 86202 python3-astroid_1.4.1-1_all.deb
Checksums-Sha256:
 8c0cdf520eec7db429241cf33a5b9bdf700b6220af5ab4f30b229bad9747efdc 2163 
astroid_1.4.1-1.dsc
 2417a2c62f07bb77485efb6dd94567ac165808a4248ecb09754116662ffa9fc2 179485 
astroid_1.4.1.orig.tar.gz
 ebad6358e61f21569ceec8d30eac75f6b1da7323e30d0ac471d399c2b8261818 3496 
astroid_1.4.1-1.debian.tar.xz
 0b90a780f3d31a91cf3bce4ad962f842374470f80c327cdc0969689e856365e4 86336 
python-astroid_1.4.1-1_all.deb
 d54c7fd553c815c2b1c770a527668aa7209c7f142443b03b7320064bf36704c2 86202 
python3-astroid_1.4.1-1_all.deb
Files:
 8af27e1d3a1c137beb8fe428533ccb7a 2163 python optional astroid_1.4.1-1.dsc
 a75975473d7d1d381dbd6f8370251f1a 179485 python optional 
astroid_1.4.1.orig.tar.gz
 3924951c258ddcee4f153109636ba99c 3496 python optional 
astroid_1.4.1-1.debian.tar.xz
 3d18c87c7db98f613f90ad2d8c3e31f1 86336 python optional 
python-astroid_1.4.1-1_all.deb
 045aeb2b74640e2d4f44f4cf83505f4e 86202 python optional 
python3-astroid_1.4.1-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWh/zbAAoJEIefPJk4AalPIwQQAJCT5R2RSJ32L

Processed: your mail

[Debian Bug Tracking System]

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

> # this FTBFS is due to dh-exec
> reassign 809283 dh-exec 0.18
Bug #809283 [src:libuv] libuv: FTBFS: dh_install: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.AUyQ2PO5/usr/lib/x86_64-linux-gnu/libuv.so.0.10':
 No such file or directory
Bug reassigned from package 'src:libuv' to 'dh-exec'.
No longer marked as found in versions libuv/0.10.36-3.
Ignoring request to alter fixed versions of bug #809283 to the same values 
previously set
Bug #809283 [dh-exec] libuv: FTBFS: dh_install: cp: cannot stat 
'debian/tmp/debian/tmp/dh-exec.AUyQ2PO5/usr/lib/x86_64-linux-gnu/libuv.so.0.10':
 No such file or directory
Marked as found in versions dh-exec/0.18.
> --
Stopping processing here.

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

Bug#809646: marked as done (New xterm deletes content of SHELL environment)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 16:41:16 +
with message-id 
and subject line Bug#809646: fixed in xterm 322-1
has caused the Debian Bug report #809646,
regarding New xterm deletes content of SHELL environment
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.)


-- 
809646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: xterm
Version: 321-1
Severity: important

Today I installed the newest version of xterm. After that, most of the
stuff in my terminal was not working anymore. (For that I would like to
set the bug severity to even grave as many of my stuff, even unrelated
stuff is not working anymore.)

I found out very fast that the new xterm clears the environment variable
$SHELL. But many things on unix depends on that variable!

After downgrading to 320-1 I was back online and could write this
bugreport.

So please take out version 321-1 as fast as possible unless it does more
harm! This version is broken to a way to make it unusable!

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

Kernel: Linux 4.2.6 (SMP w/8 CPU cores)
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages xterm depends on:
ii  libc6   2.21-6
ii  libfontconfig1  2.11.0-6.3
ii  libice6 2:1.0.9-1+b1
ii  libtinfo5   6.0+20151024-2
ii  libutempter01.1.6-1
ii  libx11-62:1.6.3-1
ii  libxaw7 2:1.0.13-1
ii  libxft2 2.3.2-1
ii  libxmu6 2:1.1.2-2
ii  libxpm4 1:3.5.11-1+b1
ii  libxt6  1:1.1.5-1
ii  xbitmaps1.1.1-2

Versions of packages xterm recommends:
ii  x11-utils  7.7+3

Versions of packages xterm suggests:
pn  xfonts-cyrillic  

- -- no debconf information

- -- 
Klaus Ethgen  http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQGcBAEBCgAGBQJWh6xmAAoJEKZ8CrGAGfas08AL/RJJJz6/smvgaOZl9gPN06BC
tm8iahNPs4aqaf87hJaRXoi+tGO7l6BFjpRiYzsFrV2ywQnxf0bzQeBxZKFbuPlA
14a2by3ZINmNuLmDVthHhEylVsfnENzUAUh/GlZ3od2OuEaLxJZjxNmRBTHl+OaY
UH2h4V2CWeScDRd4WQayIfRl6uUDysEsuzzKZN0NuqStEUG9FzEHK3TnOLAogMX4
rGTAJdGM8GhDIcUM9+i2ue8yO/E/NIZip1oCPAnuNT/HjEsUi6LgnajSGlIk13T/
cjmFD7JyaGD0FDgtlmcuTS5kLTxeUmO1CB51+/cnxvC8e5SjGOhnl1jFiMCHDm9P
Ej9k8O2pU16KL1wxvLeK1hPZK+jverPyZ9XSRa9+coxtwx+Nco/QoPFuFfu6c6iK
8hE+F5rZK4mfoQ8/oBZ/j5Qx9gJyICTAzkOho/gonnSfFCS4c+w2tWYopLk+krx6
2z0LJofAPLLlqubNYwMc2V8t5alMTbvEI1eWK2KXzg==
=bpOL
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: xterm
Source-Version: 322-1

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

Debian distribution maintenance software
pp.
Sven Joachim  (supplier of updated xterm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 16:17:27 +0100
Source: xterm
Binary: xterm
Architecture: source
Version: 322-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Sven Joachim 
Description:
 xterm  - X terminal emulator
Closes: 809646
Changes:
 xterm (322-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fix regression due to incorrect fix for compiler warning when
   allocating storage for /etc/shells (Closes: #809646).
   * Update years in debian/copyright.
Checksums-Sha1:
 60582db3e9291af9315ad586486ad09724b3e2d1 2049 xterm_322-1.dsc
 d2709c46c767a4e38ebf5f9e1dd30d640129263d 1227531 xterm_322.orig.tar.gz
 8b5a6f278cdf8b6b30c917509fc2f72fb6f8587f 102034 xterm_322-1.diff.gz
Checksums-Sha256:
 447a2d4a07ebd05a91ed2c2bc974133be72f13eb05b38b6b66bded870d1ba7e4 2049 
xterm_322-1.dsc
 9adb41b53f76a3fccaa65d47a87d336094a523985d1d6a6b8cc468375ed109d6

Bug#800788: marked as pending

[Sandro Tosi]

tag 800788 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/astroid.git;a=commitdiff;h=937188d

---
commit 937188d3916c120e5493294c7f16fabe52400894
Author: Sandro Tosi 
Date:   Sun Nov 29 22:19:28 2015 +

New upstream release

diff --git a/debian/changelog b/debian/changelog
index 6dc9ae0..04b30b9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+astroid (1.4.1-1) UNRELEASED; urgency=medium
+
+  * New upstream release
+- add support for Python 3.5; Closes: #800788
+- correctly handle multiprocessing; Closes: #790884
+
+ -- Sandro Tosi   Sun, 29 Nov 2015 22:18:52 +
+
 astroid (1.3.8-1) unstable; urgency=medium
 
   * New upstream release

Processed: Bug#800788 marked as pending

[Debian Bug Tracking System]

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

> tag 800788 pending
Bug #800788 [python3-astroid] python3-astroid: not fit for Python 3.5
Bug #802414 [python3-astroid] python-requirements-detector: FTBFS: 
AttributeError: 'Call' object has no attribute 'starargs'
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#806344: marked as done (django-auth-ldap: FTBFS with Django 1.9)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 16:34:58 +
with message-id 
and subject line Bug#806344: fixed in django-auth-ldap 1.2.7+dfsg-1
has caused the Debian Bug report #806344,
regarding django-auth-ldap: FTBFS with Django 1.9
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.)


-- 
806344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-auth-ldap
Version: 1.2.6+dfsg-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django19 django19-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest release candidate, I noticed that django-auth-ldap
FTBFS with 1.9~rc2.

Please update your package to work with Django 1.9 as I will uploading
it to unstable once it is released in early December 2015 (and at the
same time raising the severity of this bug to RC).

Typical issues include:

 * "django.utils.importlib" has been removed in favour of just
   "importlib"

 * Template builtins have been removed, removing
   "template.base.builtins", "django.template.base.add_to_builtins",
   etc. You can read more here:
   
https://chris-lamb.co.uk/posts/importerror-cannot-import-name-add_to_builtins-under-django-19

 * "django.forms.models.save_instance" has been removed:

   -
   
https://github.com/django/django/commit/8656cfc4e01332426e5e4b78c20a4e9ec443b293
   -
   
https://github.com/django/django/commit/b11564fd36587b1077bf7d77b62b7879cc08c382

 * "django.utils.unittest" has been removed in favour of just
   "unittest"


The full build log is attached.


Regards,

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


django-auth-ldap_1.2.6+dfsg-1_amd64.build.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: django-auth-ldap
Source-Version: 1.2.7+dfsg-1

We believe that the bug you reported is fixed in the latest version of
django-auth-ldap, 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.
Michael Fladischer  (supplier of updated django-auth-ldap 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 16:22:15 +0100
Source: django-auth-ldap
Binary: python-django-auth-ldap python-django-auth-ldap-doc
Architecture: source all
Version: 1.2.7+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-auth-ldap - Django LDAP authentication backend
 python-django-auth-ldap-doc - Django LDAP authentication backend 
(documentation)
Closes: 806344
Changes:
 django-auth-ldap (1.2.7+dfsg-1) unstable; urgency=medium
 .
   [ Michael Fladischer ]
   * New upstream release (Closes: #806344).
   * Bump debhelper compatibility and version to 9.
   * Clean django_auth_ldap.egg-info/requires.txt to allow two builds in a row.
 .
   [ SVN-Git Migration ]
   * git-dpm config
   * Update Vcs fields for git migration
Checksums-Sha1:
 dd1e9615a757a8f388ca2e3dfd6fb85953a20f4a 2339 django-auth-ldap_1.2.7+dfsg-1.dsc
 6a8e13472ccac13bcd62daaa8c16a7281da83dc2 100858 
django-auth-ldap_1.2.7+dfsg.orig.tar.gz
 3755930ae73fb0fe7ab4d04645931ecbbaf12490 11540 
django-auth-ldap_1.2.7+dfsg-1.debian.tar.xz
 2635a61b7d9cf002fa75368391b9a0ac7b9ff986 48520 
python-django-auth-ldap-doc_1.2.7+dfsg-1_all.deb
 f2cac427f9a313fe32b8dc9fbe149dd52801613a 23614 
python-django-auth-ldap_1.2.7+dfsg-1_all.deb
Checksums-Sha256:
 abfdcd0d83e9058df9a44bfc62b2dafcf3eca801b1389f42001c868c25609778 2339 
django-auth-ldap_1.2.7+dfsg-1.dsc
 3ba682c9fff41d561d88ac3b217f3dabfdc0832910b99d1f887e53d30f784ba1 100858 
django-auth-ldap_1.2.7+dfsg.orig.tar.gz
 78b942b940cb59850aa29a5ebd4e0da43f789c120a9d564e28e04168d10c9b6a 11540 
django-auth-ldap_1.2.7+dfsg-1.debian.tar.xz
 00cf1213212aaada964af3f01bcdec03751b459f32014016e7c8539f10919088 48520 
python-django-auth-ldap-doc_1.2.7+dfsg-1_all.deb
 a90ff92c11b0016bc92c3551e4af97f2481245f802d28609d859a987e0b3af9a 23614 
python-django-auth-ldap_1.2.7+dfsg-1_all.deb
Files:
 8fe560

Bug#808646: marked as done (django-auth-ldap: FTBFS: ImportError: cannot import name unittest)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 16:34:58 +
with message-id 
and subject line Bug#806344: fixed in django-auth-ldap 1.2.7+dfsg-1
has caused the Debian Bug report #806344,
regarding django-auth-ldap: FTBFS: ImportError: cannot import name unittest
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.)


-- 
806344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-auth-ldap
Version: 1.2.6+dfsg-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:

for python in python2.7; do \
  PYTHONPATH=".:test" $python test/manage.py test django_auth_ldap; \
done
E
==
ERROR: django_auth_ldap.tests (unittest.loader.ModuleImportFailure)
--
ImportError: Failed to import test module: django_auth_ldap.tests
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 "/django-auth-ldap-1.2.6+dfsg/django_auth_ldap/tests.py", line 48, in 

from django.utils import unittest
ImportError: cannot import name unittest


--
Ran 1 test in 0.000s

FAILED (errors=1)
Creating test database for alias 'default'...
Destroying test database for alias 'default'...

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: django-auth-ldap
Source-Version: 1.2.7+dfsg-1

We believe that the bug you reported is fixed in the latest version of
django-auth-ldap, 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.
Michael Fladischer  (supplier of updated django-auth-ldap 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 16:22:15 +0100
Source: django-auth-ldap
Binary: python-django-auth-ldap python-django-auth-ldap-doc
Architecture: source all
Version: 1.2.7+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-auth-ldap - Django LDAP authentication backend
 python-django-auth-ldap-doc - Django LDAP authentication backend 
(documentation)
Closes: 806344
Changes:
 django-auth-ldap (1.2.7+dfsg-1) unstable; urgency=medium
 .
   [ Michael Fladischer ]
   * New upstream release (Closes: #806344).
   * Bump debhelper compatibility and version to 9.
   * Clean django_auth_ldap.egg-info/requires.txt to allow two builds in a row.
 .
   [ SVN-Git Migration ]
   * git-dpm config
   * Update Vcs fields for git migration
Checksums-Sha1:
 dd1e9615a757a8f388ca2e3dfd6fb85953a20f4a 2339 django-auth-ldap_1.2.7+dfsg-1.dsc
 6a8e13472ccac13bcd62daaa8c16a7281da83dc2 100858 
django-auth-ldap_1.2.7+dfsg.orig.tar.gz
 3755930ae73fb0fe7ab4d04645931ecbbaf12490 11540 
django-auth-ldap_1.2.7+dfsg-1.debian.tar.xz
 2635a61b7d9cf002fa75368391b9a0ac7b9ff986 48520 
python-django-auth-ldap-doc_1.2.7+dfsg-1_all.deb
 f2cac427f9a313fe32b8dc9fbe149dd52801613a 23614 
python-django-auth-ldap_1.2.7+dfsg-1_all.deb
Checksums-Sha256:
 abfdcd0d83e9058df9a44bfc62b2dafcf3eca801b1389f42001c868c25609778 2339 
django-auth-ldap_1.2.7+dfsg-1.dsc
 3ba682c9fff41d561d88ac3b217f3dabfdc0832910b99d1f887e53d30f784ba1 100858 
django-auth-ldap_1.2.7+dfsg.orig.tar.gz
 78b942b940cb59850aa29a5ebd4e0da43f789c120a9d564e28e04168d10c9b6a 11540 
django-auth-ldap_1.2.7+dfsg-1.debian.tar.xz
 00cf1213212aaada964af3f01bcdec03751b459f32014016e7c8539f10919088 48520 
python-django-aut

Bug#809671: should openmeeg be removed from Debian?

[Mattia Rizzolo]

Source: openmeeg
Version: 2.0.0.dfsg-5.2
Severity: serious

Dear maintainer,

openmeeg is in a very bad state, it's unbuildable, and has an unfixed RC
bug since more than 2 years.
It missed the Jessie release, and I don't see any work going on either
upstream or in debian.

ATM it has 2 RC bug, last maintainer upload 2012-06-25, and a lowish
popcon (Inst < 200, but most are No Files or Old).

Furthermore it is currently uninstallable due to the removal of
python-support.


Thanks for considering.


RM: openmeeg -- RoQA; unmaintained; RC-buggy; dead upstream; low popcon

-- 
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#807645: ifupdown package fails to configure itself (by dpkg)

[Guus Sliepen]

On Sat, Dec 26, 2015 at 03:27:48PM +0100, Marco d'Itri wrote:

> > Hm, that sounds like a bug in systemd or in some other component that it
> > calls during "systemctl enable networking.service". Marco, can you see
> > from your strace logs what process did that dbus call?
> Just "systemctl enable networking.service".
> 
> > The current version of ifupdown calls systemctl from postinst "by hand",
> > but the next version will use dh-systemd, maybe that will fix this issue
> > as well, but I'm not sure.
> The problem is that networking.service is already enabled (by insserv), 
> but I expected the command to be idempotent anyway:

Hm, it is idempotent on my machines, and I can't reproduce the issue
you're having, whatever state I put networking.service in before
upgrading the package.

Can you check whether 0.8.4 works better? That one uses dh-systemd.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Processed: Re: Bug#809658: ifupdown: Upgrade 0.8.5 Removes 48 Unrelated Packages e.g. linux-image, xorg, udev (Sid Unstable)

[Debian Bug Tracking System]

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

> found 809658 0.8.5
Bug #809658 [ifupdown] ifupdown: Upgrade 0.8.5 Removes 48 Unrelated Packages 
e.g. linux-image, xorg, udev (Sid Unstable)
Marked as found in versions ifupdown/0.8.5.
> notfound 809658 0.8.4
Bug #809658 [ifupdown] ifupdown: Upgrade 0.8.5 Removes 48 Unrelated Packages 
e.g. linux-image, xorg, udev (Sid Unstable)
No longer marked as found in versions ifupdown/0.8.4.
> severity 809658 normal
Bug #809658 [ifupdown] ifupdown: Upgrade 0.8.5 Removes 48 Unrelated Packages 
e.g. linux-image, xorg, udev (Sid Unstable)
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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

Bug#809658: ifupdown: Upgrade 0.8.5 Removes 48 Unrelated Packages e.g. linux-image, xorg, udev (Sid Unstable)

[Guus Sliepen]

found 809658 0.8.5
notfound 809658 0.8.4
severity 809658 normal
thanks

On Sat, Jan 02, 2016 at 08:25:56AM -0500, Cindy Sue Causey wrote:

> Hi.. First, thank you all for the work you do!
> 
> Next: I ran my usual "apt-get update" today. Found ifupdown needing upgraded 
> in Sid Unstable along with ~20+ other packages. When the upgrade process 
> began, I received an apt-get advisement that 48 packages were going to be 
> removed.
> 
> Being familiar with this occurrence at this point, I manually installed 
> packages one by one and determined ifupdown to be the package performing the 
> removals. The following (extensive) output is what I receive when attempting 
> to install ifupdown by itself:

Some files are being moved from the systemd and udev packages to the
ifupdown package. As part of that, the ifupdown package declares that it
breaks with older versions of systemd and udev. Normally that should
cause apt to defer updating ifupdown until systemd and udev packages are
available with the right version, but in this case it thinks it can also
solve the dependencies by kicking out udev and systemd and installing
sysvinit.

There is nothing wrong with ifupdown itself, neither with apt or
anything else. This is normal and will be resolved once new versions of
systemd and udev are uploaded. This is also in no way critical, since
nothing is actually broken on your system. I'll keep the bug open in any
case until the the transition is complete.

> My latest practice under these circumstances is to set the affecting package 
> to the side and wait for developers' newer release of the same.

That's the correct practice :) You are running the unstable
distribution, so unfortunately this kind of issue will pop up once in a
while, but it is normal. If you want to avoid this problem, run can run
testing instead.

> Thank you again for all your work!

You're welcome :)

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: Digital signature

Processed: Bug#806344 marked as pending

[Debian Bug Tracking System]

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

> tag 806344 pending
Bug #806344 [src:django-auth-ldap] django-auth-ldap: FTBFS with Django 1.9
Bug #808646 [src:django-auth-ldap] django-auth-ldap: FTBFS: ImportError: cannot 
import name unittest
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#806344: marked as pending

[Michael Fladischer]

tag 806344 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/django-auth-ldap.git;a=commitdiff;h=26952c4

---
commit 26952c48114a1dff3aae14a070edd6d45898d1bc
Author: Michael Fladischer 
Date:   Sat Jan 2 16:44:33 2016 +0100

New upstream release (Closes: #806344).

diff --git a/debian/changelog b/debian/changelog
index e8e46ed..701814e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+django-auth-ldap (1.2.7+dfsg-1) unstable; urgency=medium
+
+  [ Michael Fladischer ]
+  * New upstream release (Closes: #806344).
+  * Bump debhelper compatibility and version to 9.
+  * Clean django_auth_ldap.egg-info/requires.txt to allow two builds in a row.
+
+  [ SVN-Git Migration ]
+  * git-dpm config
+  * Update Vcs fields for git migration
+
+ -- Michael Fladischer   Sat, 02 Jan 2016 16:22:15 +0100
+
 django-auth-ldap (1.2.6+dfsg-1) unstable; urgency=medium
 
   * New upstream release.

Bug#809668: monodevelop FTBFS on buildds, build-dependencies in build-depends-indep when they should probablly be in build-depends

[peter green]

Package: monodevelop
Version: 5.10.0.871-1
Severity: serious

Monodevelop (which recently changed one of it's binary packages from 
arch all to arch any) failed to build on the buildds with.

dh clean --with cli,autoreconf
dh: unable to load addon cli: Can't locate Debian/Debhelper/Sequence/cli.pm in 
@INC (you may need to install the Debian::Debhelper::Sequence::cli module) 
(@INC contains: /etc/perl /usr/local/lib/aarch64-linux-gnu/perl/5.20.2 
/usr/local/share/perl/5.20.2 /usr/lib/aarch64-linux-gnu/perl5/5.20 
/usr/share/perl5 /usr/lib/aarch64-linux-gnu/perl/5.20 /usr/share/perl/5.20 
/usr/local/lib/site_perl .) at (eval 13) line 2.
BEGIN failed--compilation aborted at (eval 13) line 2.

Looking on packages.debian.org that file is provided by cli-common-dev

Looking at packages.debian.org it seems that nearly all of the 
build-depenencies are in build-depends-indep. The error posted above 
shows that cli-common-dev and dh-autoreconf need to mov e to 
build-depends. I strongly suspect others need to move to but I have not 
done tests to determine exactly which.

Bug#809283: [debhelper-devel] libuv: FTBFS: dh_install: cp: cannot stat 'debian/tmp/debian/tmp/dh-exec.AUyQ2PO5/usr/lib/x86_64-linux-gnu/libuv.so.0.10': No such file or directory

[Niels Thykier]

Luca BRUNO:
> On Mon, 28 Dec 2015 23:14:03 + Chris Lamb  wrote:
> 
>> Source: libuv
>> Version: 0.10.36-3
>> Usertags: ftbfs
>  
>> [...]
>>   [..]
>>  dh_install
>>   cp: cannot stat 'debian/tmp/debian/tmp/dh-exec.AUyQ2PO5/usr/lib/x86_64-
> linux-gnu/libuv.so.0.10': No such file or directory
>>   dh_install: cp --reflink=auto -a debian/tmp/debian/tmp/dh-
> exec.AUyQ2PO5/usr/lib/x86_64-linux-gnu/libuv.so.0.10 
> debian/libuv0.10/usr/lib/x86_64-linux-gnu// returned exit code 1
>>   [..]
> 
> The double "debian/tmp/" looks a bit fishy there.
> I guess either debhelper or dh-exec are over-substituting ${DESTDIR}, or 
> started prepending one time too much.
> 
> Ciao, Luca 
> 
> [...]

Hi,

Assuming you specified "debian/tmp/" directly in your install
file, then a duplicate "debian/tmp" is expected on a failure (in compat
7 or later).

Since compat 7, debhelper will do a fallback to debian/tmp/
if  does not exist (or the wildcard matches nothing).
Notably, debhelper does not check whether  already starts
with "debian/tmp/" or not before trying.

Thanks,
~Niels





signature.asc
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 808246 https://sourceware.org/bugzilla/show_bug.cgi?id=19421
Bug #808246 [src:linux] Stretch fails to install on OpenPOWER systems
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=19421'.
>
End of message, stopping processing here.

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

Bug#809646: New xterm deletes content of SHELL environment

[Thomas Dickey]

On Sat, Jan 02, 2016 at 02:23:21PM +0100, Sven Joachim wrote:
> Control: severity -1 grave
> 
> Am 02.01.2016 um 11:54 schrieb Klaus Ethgen:
> 
> > Package: xterm
> > Version: 321-1
> > Severity: important
> >
> > Today I installed the newest version of xterm. After that, most of the
> > stuff in my terminal was not working anymore. (For that I would like to
> > set the bug severity to even grave as many of my stuff, even unrelated
> > stuff is not working anymore.)
> >
> > I found out very fast that the new xterm clears the environment variable
> > $SHELL.
> 
> Ouch, sorry for not noticing that in advance.  I'm pretty sure it was
> not intended.

true - the suggested fix that I applied worked, but had a compiler warning.
My fix for _that_ was incorrect.  This works (for me):

--- /usr/build/xterm/xterm-321+/main.c  2015-12-29 15:19:35.0 +
+++ /usr/build/xterm/xterm-321a/main.c  2016-01-02 14:12:19.0 +
@@ -1,7 +1,7 @@
-/* $XTermId: main.c,v 1.776 2015/12/29 15:19:35 tom Exp $ */
+/* $XTermId: main.c,v 1.777 2016/01/02 14:12:19 tom Exp $ */
 
 /*
- * Copyright 2002-2014,2015 by Thomas E. Dickey
+ * Copyright 2002-2015,2016 by Thomas E. Dickey
  *
  * All Rights Reserved
  *
@@ -3248,8 +3248,8 @@
 if (validProgram(pathname)
&& stat(ok_shells, &sb) == 0
&& (sb.st_mode & S_IFMT) == S_IFREG
-   && (sb.st_size != 0)
-   && (sb.st_size < (off_t) (((size_t) ~0) - 2))
+   && ((size_t) sb.st_size > 0)
+   && ((size_t) sb.st_size < (((size_t) ~0) - 2))
&& (blob = calloc((size_t) sb.st_size + 2, sizeof(char))) != 0) {
if ((fp = fopen(ok_shells, "r")) != 0) {
rc = fread(blob, sizeof(char), (size_t) sb.st_size, fp);

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://invisible-island.net


signature.asc
Description: Digital signature

Bug#797168: linbox: FTBFS on powerpc (SIGILL in test-optimization)

[Mathieu Malaterre]

I would be tempted to just close the bug:

https://buildd.debian.org/status/fetch.php?pkg=linbox&arch=powerpc&ver=1.3.2-1.1%2Bb2&stamp=1449702720

But it would be nice to diagnose what magically happened ...

Processed: retitle 806587 to RM: coherence -- RoQA; dead upstream, relies on gstreamer 0.10 ...

[Debian Bug Tracking System]

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

> retitle 806587 RM: coherence -- RoQA; dead upstream, relies on gstreamer 0.10
Bug #806587 [ftp.debian.org] RM: coherence - dead upstream, relies on gstreamer 
0.10
Changed Bug title to 'RM: coherence -- RoQA; dead upstream, relies on gstreamer 
0.10' from 'RM: coherence - dead upstream, relies on gstreamer 0.10'
> severity 806587 normal
Bug #806587 [ftp.debian.org] RM: coherence -- RoQA; dead upstream, relies on 
gstreamer 0.10
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#809658: ifupdown: Upgrade 0.8.5 Removes 48 Unrelated Packages e.g. linux-image, xorg, udev (Sid Unstable)

[Cindy Sue Causey]

Package: ifupdown
Version: 0.8.4
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

Hi.. First, thank you all for the work you do!

Next: I ran my usual "apt-get update" today. Found ifupdown needing upgraded in 
Sid Unstable along with ~20+ other packages. When the upgrade process began, I 
received an apt-get advisement that 48 packages were going to be removed.

Being familiar with this occurrence at this point, I manually installed 
packages one by one and determined ifupdown to be the package performing the 
removals. The following (extensive) output is what I receive when attempting to 
install ifupdown by itself:

+++
The following packages will be REMOVED:
  blueman bluez colord gvfs gvfs-daemons iio-sensor-proxy initramfs-tools
  libpam-systemd linux-image-4.1.0-1-amd64 network-manager
  network-manager-gnome policykit-1 policykit-1-gnome systemd systemd-sysv
  udev udisks2 upower xfce4-power-manager xfce4-power-manager-plugins xorg
  xserver-xorg xserver-xorg-core xserver-xorg-input-all
  xserver-xorg-input-evdev xserver-xorg-input-mouse
  xserver-xorg-input-synaptics xserver-xorg-input-vmmouse
  xserver-xorg-input-wacom xserver-xorg-video-all xserver-xorg-video-ati
  xserver-xorg-video-cirrus xserver-xorg-video-fbdev xserver-xorg-video-intel
  xserver-xorg-video-mach64 xserver-xorg-video-mga xserver-xorg-video-neomagic
  xserver-xorg-video-nouveau xserver-xorg-video-openchrome
  xserver-xorg-video-qxl xserver-xorg-video-r128 xserver-xorg-video-radeon
  xserver-xorg-video-savage xserver-xorg-video-sisusb xserver-xorg-video-tdfx
  xserver-xorg-video-trident xserver-xorg-video-vesa xserver-xorg-video-vmware
The following NEW packages will be installed:
  sysvinit-core
The following packages will be upgraded:
  ifupdown
1 upgraded, 1 newly installed, 48 to remove and 23 not upgraded.
Need to get 204 kB of archives.
After this operation, 243 MB disk space will be freed.
+++

A quick trip to "apt-show-versions [package-name]" shows all of ifupdown's 
depends to at least appear current.

My latest practice under these circumstances is to set the affecting package to 
the side and wait for developers' newer release of the same.

Thank you again for all your work!

Cindy Sue :)


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

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

Versions of packages ifupdown depends on:
ii  adduser  3.113+nmu3
ii  init-system-helpers  1.24
ii  iproute2 4.3.0-1
ii  libc62.21-6
ii  lsb-base 9.20150917

Versions of packages ifupdown recommends:
ii  isc-dhcp-client [dhcp-client]  4.3.3-5

Versions of packages ifupdown suggests:
ii  ppp 2.4.7-1+1
pn  rdnssd  

-- no debconf information

Processed: Re: Bug#809646: New xterm deletes content of SHELL environment

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #809646 [xterm] New xterm deletes content of SHELL environment
Severity set to 'grave' from 'important'

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

Bug#808635: marked as done (celery-haystack: FTBFS: ImportError: No module named importlib)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 13:04:01 +
with message-id 
and subject line Bug#806343: fixed in celery-haystack 0.10-1
has caused the Debian Bug report #806343,
regarding celery-haystack: FTBFS: ImportError: No module named importlib
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.)


-- 
806343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: celery-haystack
Version: 0.9-1
Severity: serious
Justification: fails to build from source
Tags: sid 
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:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/celery-haystack-0.9'
PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="PYTHONPATH=. HAYSTACK=v2 python2.7 
/usr/bin/django-admin test --settings=celery_haystack.test_settings" 
dh_auto_test
I: pybuild base:184: PYTHONPATH=. HAYSTACK=v2 python2.7 /usr/bin/django-admin 
test --settings=celery_haystack.test_settings
Traceback (most recent call last):
  File "/usr/bin/django-admin", line 21, in 
management.execute_from_command_line()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 350, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 324, in execute
django.setup()
  File "/usr/lib/python2.7/dist-packages/django/__init__.py", line 18, in setup
apps.populate(settings.INSTALLED_APPS)
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 85, in 
populate
app_config = AppConfig.create(entry)
  File "/usr/lib/python2.7/dist-packages/django/apps/config.py", line 90, in 
create
module = import_module(entry)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/usr/lib/python2.7/dist-packages/haystack/__init__.py", line 57, in 

signal_processor_class = loading.import_class(signal_processor_path)
  File "/usr/lib/python2.7/dist-packages/haystack/utils/loading.py", line 32, 
in import_class
module_itself = importlib.import_module(module_path)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/celery-haystack-0.9/celery_haystack/signals.py", line 6, in 
from .utils import enqueue_task
  File "/celery-haystack-0.9/celery_haystack/utils.py", line 2, in 
from django.utils.importlib import import_module
ImportError: No module named importlib
E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: 
PYTHONPATH=. HAYSTACK=v2 python2.7 /usr/bin/django-admin test 
--settings=celery_haystack.test_settings
dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
debian/rules:12: recipe for target 'override_dh_auto_test' failed

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

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: celery-haystack
Source-Version: 0.10-1

We believe that the bug you reported is fixed in the latest version of
celery-haystack, 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.
Michael Fladischer  (supplier of updated celery-haystack 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 13:53:06 +0100
Source: celery-haystack
Binary: python-django-celery-haystack python3-django-celery-haystack
Architecture: source all
Version: 0.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-celery-haystack - utilize Celery for automatic haystack index 
updates
 python3-django-celery-haystack - utilize Celery for automatic haystack index 
updates (Python3 vers
Closes: 806343
Changes:
 celery-haystack (0.10-1) unstable; urgency=medi

Bug#806343: marked as done (celery-haystack: FTBFS with Django 1.9)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 13:04:01 +
with message-id 
and subject line Bug#806343: fixed in celery-haystack 0.10-1
has caused the Debian Bug report #806343,
regarding celery-haystack: FTBFS with Django 1.9
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.)


-- 
806343: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: celery-haystack
Version: 0.9-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django19 django19-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest release candidate, I noticed that celery-haystack
FTBFS with 1.9~rc2.

Please update your package to work with Django 1.9 as I will uploading
it to unstable once it is released in early December 2015 (and at the
same time raising the severity of this bug to RC).

Typical issues include:

 * "django.utils.importlib" has been removed in favour of just
   "importlib"

 * Template builtins have been removed, removing
   "template.base.builtins", "django.template.base.add_to_builtins",
   etc. You can read more here:
   
https://chris-lamb.co.uk/posts/importerror-cannot-import-name-add_to_builtins-under-django-19

 * "django.forms.models.save_instance" has been removed:

   -
   
https://github.com/django/django/commit/8656cfc4e01332426e5e4b78c20a4e9ec443b293
   -
   
https://github.com/django/django/commit/b11564fd36587b1077bf7d77b62b7879cc08c382

 * "django.utils.unittest" has been removed in favour of just
   "unittest"


The full build log is attached.


celery-haystack_0.9-1_amd64.build.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: celery-haystack
Source-Version: 0.10-1

We believe that the bug you reported is fixed in the latest version of
celery-haystack, 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.
Michael Fladischer  (supplier of updated celery-haystack 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Jan 2016 13:53:06 +0100
Source: celery-haystack
Binary: python-django-celery-haystack python3-django-celery-haystack
Architecture: source all
Version: 0.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michael Fladischer 
Description:
 python-django-celery-haystack - utilize Celery for automatic haystack index 
updates
 python3-django-celery-haystack - utilize Celery for automatic haystack index 
updates (Python3 vers
Closes: 806343
Changes:
 celery-haystack (0.10-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #806343).
Checksums-Sha1:
 598ace0fcb6922c179bf9055b8e809ff8a92b549 2514 celery-haystack_0.10-1.dsc
 5c227a82c052ea84b05b12da0c9f5f3aa4d8e85e 8299 celery-haystack_0.10.orig.tar.gz
 4222ea30c6ddc1223d04be24dbee99fafe01aa65 2988 
celery-haystack_0.10-1.debian.tar.xz
 13f24e81f0f32891b6fe1e98eff09df06598b6d1 9222 
python-django-celery-haystack_0.10-1_all.deb
 4ce9fc386f4d0a9fae6c9d2a7eb0d18f8bf7b620 9346 
python3-django-celery-haystack_0.10-1_all.deb
Checksums-Sha256:
 851b0c1f50c3e18fd626f2ac637270d27ca132b4f3862523b6066c60fce827ab 2514 
celery-haystack_0.10-1.dsc
 b6e2a3c70071bef0838ca1a7d9f14fae6c2ecf385704092e59b82147a1ee552e 8299 
celery-haystack_0.10.orig.tar.gz
 b9ef8ea2a0e45b3bc923766dc9b0a936ef5c2aef761d667ea5d4c77c68e85b59 2988 
celery-haystack_0.10-1.debian.tar.xz
 41693c341f495e5fb140894308e02a7d1efc3eab581dd65e5b0973f5b3c25fc2 9222 
python-django-celery-haystack_0.10-1_all.deb
 a83e9d7a6c6f47e30c1202c08dbe3e72c00590c4fbfb6310821f593c4dfb76d3 9346 
python3-django-celery-haystack_0.10-1_all.deb
Files:
 daa8f66e89d06cb73b14bb7d23922c32 2514 python optional 
celery-haystack_0.10-1.dsc
 6e398fd8f69b6d55682dbc9bd22a6fa1 8299 python optional 
celery-haystack_0.10.orig.tar.gz
 7eda432546b5195c81dff33f8f795bed 2988 python optional 
celery-haystack_0.10-1.debian.tar.xz
 cd6990d79b2893d9d938bf90e414446e 9222 python optional 
python-django-celery-haystack_0.10-1_all.deb
 928d478884dc605e872db1e2f895ae00 9346 python optional 
python3

Bug#809650: linuxdcpp: FTBFS: msgcat: error while opening "build/release/glade/po/glade.pot" for reading

[Chris Lamb]

Source: linuxdcpp
Version: 1.1.0-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,

linuxdcpp fails to build from source in unstable/amd64:

  [..]

  dcpp/po/sk.po:7: warning: header field 'Language' missing in header
  Compiling message catalog build/locale/sl/LC_MESSAGES/libdcpp.mo from 
dcpp/po/sl.po
  dcpp/po/sl.po:7: warning: header field 'Language-Team' still has the initial 
default value
  dcpp/po/sl.po:7: warning: header field 'Language' missing in header
  Compiling message catalog build/locale/sq/LC_MESSAGES/libdcpp.mo from 
dcpp/po/sq.po
  dcpp/po/sq.po:7: warning: header field 'Language-Team' still has the initial 
default value
  dcpp/po/sq.po:7: warning: header field 'Language' missing in header
  Compiling message catalog build/locale/sr/LC_MESSAGES/libdcpp.mo from 
dcpp/po/sr.po
  dcpp/po/sr.po:7: warning: header field 'Language' missing in header
  Compiling message catalog build/locale/sv/LC_MESSAGES/libdcpp.mo from 
dcpp/po/sv.po
  dcpp/po/sv.po:7: warning: header field 'Language' missing in header
  Compiling message catalog build/locale/sv/LC_MESSAGES/linuxdcpp.mo from 
po/sv.po
  po/sv.po:7: warning: header field 'Language' missing in header
  Compiling message catalog build/locale/tr/LC_MESSAGES/libdcpp.mo from 
dcpp/po/tr.po
  dcpp/po/tr.po:7: warning: header field 'Language-Team' still has the initial 
default value
  dcpp/po/tr.po:7: warning: header field 'Language' missing in header
  Compiling message catalog build/locale/uk/LC_MESSAGES/libdcpp.mo from 
dcpp/po/uk.po
  dcpp/po/uk.po:7: warning: header field 'Language-Team' still has the initial 
default value
  dcpp/po/uk.po:7: warning: header field 'Language' missing in header
  Compiling message catalog build/locale/zh_CN/LC_MESSAGES/libdcpp.mo from 
dcpp/po/zh_CN.po
  dcpp/po/zh_CN.po:7: warning: header field 'Language' missing in header
  Compiling message catalog build/locale/zh_TW/LC_MESSAGES/libdcpp.mo from 
dcpp/po/zh_TW.po
  dcpp/po/zh_TW.po:7: warning: header field 'Language-Team' still has the 
initial default value
  dcpp/po/zh_TW.po:7: warning: header field 'Language' missing in header
  Extracting messages to build/release/glade/po/glade.pot from 
glade/downloadqueue.glade glade/favoritehubs.glade glade/favoriteusers.glade 
glade/finishedtransfers.glade glade/hash.glade glade/hub.glade 
glade/mainwindow.glade glade/privatemessage.glade glade/publichubs.glade 
glade/search.glade glade/settingsdialog.glade glade/sharebrowser.glade 
glade/transfers.glade
  xgettext: warning: file 'glade/downloadqueue.glade' extension 'glade' is 
unknown; will try C
  xgettext: warning: file 'glade/favoritehubs.glade' extension 'glade' is 
unknown; will try C
  xgettext: warning: file 'glade/favoriteusers.glade' extension 'glade' is 
unknown; will try C
  xgettext: warning: file 'glade/finishedtransfers.glade' extension 'glade' is 
unknown; will try C
  xgettext: warning: file 'glade/hash.glade' extension 'glade' is unknown; will 
try C
  xgettext: warning: file 'glade/hub.glade' extension 'glade' is unknown; will 
try C
  xgettext: warning: file 'glade/mainwindow.glade' extension 'glade' is 
unknown; will try C
  xgettext: warning: file 'glade/privatemessage.glade' extension 'glade' is 
unknown; will try C
  xgettext: warning: file 'glade/publichubs.glade' extension 'glade' is 
unknown; will try C
  xgettext: warning: file 'glade/search.glade' extension 'glade' is unknown; 
will try C
  xgettext: warning: file 'glade/settingsdialog.glade' extension 'glade' is 
unknown; will try C
  glade/settingsdialog.glade:483: warning: unterminated character constant
  glade/settingsdialog.glade:3861: warning: unterminated character constant
  xgettext: warning: file 'glade/sharebrowser.glade' extension 'glade' is 
unknown; will try C
  xgettext: warning: file 'glade/transfers.glade' extension 'glade' is unknown; 
will try C
  Extracting messages to build/release/gui/po/linux.pot from 
linux/UserCommandMenu.cc linux/WulforUtil.cc linux/bookentry.cc 
linux/dialogentry.cc linux/downloadqueue.cc linux/entry.cc 
linux/favoritehubs.cc linux/favoriteusers.cc linux/finishedtransfers.cc 
linux/hashdialog.cc linux/hub.cc linux/mainwindow.cc linux/privatemessage.cc 
linux/publichubs.cc linux/search.cc linux/settingsdialog.cc 
linux/settingsmanager.cc linux/sharebrowser.cc linux/transfers.cc 
linux/treeview.cc linux/wulfor.cc linux/wulformanager.cc linux/IntlUtil.hh 
linux/UserCommandMenu.hh linux/WulforUtil.hh linux/bookentry.hh 
linux/dialogentry.hh linux/downloadqueue.hh linux/entry.hh 
linux/favoritehubs.hh linux/favoriteusers.hh linux/finishedtransfers.hh 
linux/func.hh linux/hashdialog.hh linux/hub.hh linux/mainwindow.hh 
linux/privatemessage.hh linux/publichubs.hh linux/search.hh 
linux/settingsdialog.hh linux/settingsmanager.hh linux/sharebrowser.hh 
linux/transfers.hh linux/treeview.hh linux/versi

Bug#809247: xboxdrv: FTBFS: Checking for C++ library X11... no

[Andrey Rahmatullin]

On Sat, Jan 02, 2016 at 11:48:21AM +, Chris Lamb wrote:
> > >   libx11-dev must be installed!
> > >   debian/rules:9: recipe for target 'override_dh_auto_build' failed
> >
> > Interesting, I've seen the failed build on reproducible servers for a long
> > time and tried to reproduce that several times in the past
> 
> I can reproduce locally if that helps? :)
Thanks, but as I've said I could reproduce it this time :)

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#809247: xboxdrv: FTBFS: Checking for C++ library X11... no

[Chris Lamb]

> >   libx11-dev must be installed!
> >   debian/rules:9: recipe for target 'override_dh_auto_build' failed
>
> Interesting, I've seen the failed build on reproducible servers for a long
> time and tried to reproduce that several times in the past

I can reproduce locally if that helps? :)

(Whilst I might link to the logs, I never report FTBFS "straight" from the 
reproducible servers without confirming myself.)


Regards,

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

Bug#808640: marked as done (custodia: FTBFS: Could not find any downloads that satisfy the requirement sphinx<1.3.0)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 11:19:18 +
with message-id 
and subject line Bug#808640: fixed in custodia 0.1.0-3
has caused the Debian Bug report #808640,
regarding custodia: FTBFS: Could not find any downloads that satisfy the 
requirement sphinx<1.3.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.)


-- 
808640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: custodia
Version: 0.1.0-2
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:

Downloading/unpacking sphinx<1.3.0
  Cannot fetch index base URL https://pypi.python.org/simple/
  Could not find any downloads that satisfy the requirement sphinx<1.3.0
Cleaning up...
No distributions at all found for sphinx<1.3.0
Storing debug log for failure in /tmp/.pip/pip.log

ERROR: could not install deps [sphinx < 1.3.0]; v = 
InvocationError('/custodia-0.1.0/.tox/sphinx/bin/pip install sphinx < 1.3.0 
(see /custodia-0.1.0/.tox/sphinx/log/sphinx-1.log)', 1)
___ summary 
ERROR:   py27: could not install deps [pytest, coverage, 
-r/custodia-0.1.0/requirements.txt, cryptography]; v = 
InvocationError('/custodia-0.1.0/.tox/py27/bin/pip install pytest coverage 
-r/custodia-0.1.0/requirements.txt cryptography (see 
/custodia-0.1.0/.tox/py27/log/py27-1.log)', 1)
ERROR:   py34: could not install deps [pytest, coverage, 
-r/custodia-0.1.0/requirements.txt, cryptography]; v = 
InvocationError('/custodia-0.1.0/.tox/py34/bin/pip install pytest coverage 
-r/custodia-0.1.0/requirements.txt cryptography (see 
/custodia-0.1.0/.tox/py34/log/py34-1.log)', 1)
ERROR:   doc: could not install deps [doc8, docutils, markdown]; v = 
InvocationError('/custodia-0.1.0/.tox/doc/bin/pip install doc8 docutils 
markdown (see /custodia-0.1.0/.tox/doc/log/doc-1.log)', 1)
ERROR:   sphinx: could not install deps [sphinx < 1.3.0]; v = 
InvocationError('/custodia-0.1.0/.tox/sphinx/bin/pip install sphinx < 1.3.0 
(see /custodia-0.1.0/.tox/sphinx/log/sphinx-1.log)', 1)
Makefile:26: recipe for target 'test' failed

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

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

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated custodia 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, 02 Jan 2016 13:10:19 +0200
Source: custodia
Binary: custodia python-custodia python3-custodia
Architecture: source all
Version: 0.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 custodia   - Modular and pluggable Secrets Manager
 python-custodia - Python bindings to Custodia -- Modular and pluggable Secrets 
Mana
 python3-custodia - Python3 bindings to Custodia -- Modular and pluggable 
Secrets Man
Closes: 808640
Changes:
 custodia (0.1.0-3) unstable; urgency=medium
 .
   * fix-tox-env-for-machine-installed-python-version.diff: Look harder
 for local extensions.
   * dont-install-deps.diff: Don't try to install deps from the network,
 and disable doc target. (Closes: #808640)
   * control: Add python-{flake8,pep8-naming,sphinx} to build-deps.
Checksums-Sha1:
 6b3aa44d99fadcabbf7172ea5dc870111807bbcd 2251 custodia_0.1.0-3.dsc
 46dbc2ac1d830458187c0f5f74304e4b03e202eb 47516 custodia_0.1.0.orig.tar.gz
 01b1b217bddf808de83d8193e992fd239fb64e56 3344 custodia_0.1.0-3.debian.tar.xz
 b574ef10a4b4ce726e024a47b5266148ff76570c 6768 custodia_0.1.0-3_all.deb
 10801e344fcbf4d2a27bbfccc0a5d590432eb2f5 18048 python-custod

Bug#809247: xboxdrv: FTBFS: Checking for C++ library X11... no

[Andrey Rahmatullin]

On Mon, Dec 28, 2015 at 04:48:35PM +, Chris Lamb wrote:
>   make[1]: Entering directory 
> '/home/lamby/temp/cdt.20151228174715.Cxokh7su4k/xboxdrv-0.8.5'
>   scons CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" CCFLAGS="-g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
> -fPIE -fstack-protector-strong -Wformat -Werror=format-security" 
> LINKFLAGS="-fPIE -pie -Wl,-z,relro -Wl,-z,now"
>   scons: Reading SConscript files ...
>   Checking for C++ library X11... no
>   libx11-dev must be installed!
>   debian/rules:9: recipe for target 'override_dh_auto_build' failed
Interesting, I've seen the failed build on reproducible servers for a long
time and tried to reproduce that several times in the past and I think it
built successfully. Now it fails in my sbuild too so I will look into this
(libx11-dev still gets installed).


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#809617: marked as done (qupzilla: SIGABRTs without libqt5xcbqpa5)

[Debian Bug Tracking System]

Your message dated Sat, 02 Jan 2016 11:04:43 +
with message-id 
and subject line Bug#809617: fixed in qupzilla 1.8.9~dfsg1-2
has caused the Debian Bug report #809617,
regarding qupzilla: SIGABRTs without libqt5xcbqpa5
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.)


-- 
809617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qupzilla
Version: 1.8.9~dfsg1-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

qupzilla fails to start for me:

| $ qupzilla
| Fatal: This application failed to start because it could not find or load the 
Qt platform plugin "xcb".
|
| Available platform plugins are: linuxfb, minimal, minimalegl, offscreen.
|
| Reinstalling the application may fix this problem.
|
| Aborted (core dumped)

This used to work in the not-too-distant past[1].
Installing libqt5xcbqpa5 fixes it, and qupzilla then works as expected.
(I have apt set to install only true dependencies, not suggests or recomends.)


Trying to start qupzilla outside of X fails with

| Fatal: QXcbConnection: Could not connect to display

Hence I'm assuming that qupzilla truly requires X, and thus should
depend on libqt5xcbqpa5, as suggested in its package description.

Thanks for your work on Debian,
Jan

[1]
I'm not digging deeper into the list of recently updated packages
because the fix seems obvious. If you want me to try to pinpoint the
exact change that broke it, please holler.

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

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

Versions of packages qupzilla depends on:
ii  libc6 2.21-4
ii  libgcc1   1:5.3.1-4
ii  libgl1-mesa-glx [libgl1]  11.0.8-1
ii  libqt5core5a  5.5.1+dfsg-10
ii  libqt5dbus5   5.5.1+dfsg-10
ii  libqt5gui55.5.1+dfsg-10
ii  libqt5network55.5.1+dfsg-10
ii  libqt5printsupport5   5.5.1+dfsg-10
ii  libqt5script5 5.5.1+dfsg-2
ii  libqt5sql55.5.1+dfsg-10
ii  libqt5sql5-sqlite 5.5.1+dfsg-10
ii  libqt5webkit5 5.5.1+dfsg-2
ii  libqt5widgets55.5.1+dfsg-10
ii  libqupzilla1  1.8.9~dfsg1-1
ii  libstdc++65.3.1-4

qupzilla recommends no packages.

qupzilla suggests no packages.

-- debconf-show failed


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: qupzilla
Source-Version: 1.8.9~dfsg1-2

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated qupzilla package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Jan 2016 11:15:48 +0100
Source: qupzilla
Binary: qupzilla libqupzilla1 libqupzilla-dev
Architecture: source amd64
Version: 1.8.9~dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 libqupzilla-dev - development files for qupzilla's shared library
 libqupzilla1 - shared library and header files for qupzilla
 qupzilla   - lightweight web browser based on libqtwebkit
Closes: 809617
Changes:
 qupzilla (1.8.9~dfsg1-2) unstable; urgency=medium
 .
   * added a dependency on libqt5xcbqpa5. Closes: #809617
Checksums-Sha1:
 1a98c35e2ca98a1ce7da4ae7c61f1cf721e0d919 2027 qupzilla_1.8.9~dfsg1-2.dsc
 0258f0e483b769a46f2bbbc4b0d3455f69d33cd9 9700 
qupzilla_1.8.9~dfsg1-2.debian.tar.xz
 90d34a64becf4ff0ead0cdf16c60b6b468472b4e 23592 
libqupzilla-dev_1.8.9~dfsg1-2_amd64.deb
 375dcae2e347eb0fec1c1117dfc9655e28ac7934 2027306 
libqupzilla1_1.8.9~dfsg1-2_amd64.deb
 1de993153a3e49d16fc9cc3b08f92e2347330a2e 864386 
qupzilla_1.8.9~dfsg1-2_amd64.deb
Checksums-Sha256:
 0c5c3a201b98c8d54cba0b4c9b5e350

Bug#809271: [Pkg-freeipa-devel] Bug#809271: freeipa: FTBFS: configure: error: libpdb does not have make_pdb_method

[Timo Aaltonen]

On 01.01.2016 22:58, Alexander Bokovoy wrote:
> On Mon, 28 Dec 2015 21:29:58 + Chris Lamb  wrote:
>> Source: freeipa
>> Version: 4.0.5-6
>> Severity: serious
>> Justification: fails to build from source
>> User: reproducible-bui...@lists.alioth.debian.org
>> Usertags: ftbfs
>> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
>> 
>> Dear Maintainer,
>> 
>> freeipa fails to build from source in unstable/amd64:
> This issue is fixed with FreeIPA 4.2.0 (Samba renamed its own library
> from libpdb to libsamba-passdb to avoid clash with another library named
> the same way).
> 
> See 
> https://git.fedorahosted.org/cgit/freeipa.git/commit/?id=d57efb74bb6ad91b029f39ed4e482c41f8ba
> for details. The commit should apply with minor changes to 4.0.5 as well.

4.1.4 seems to have it too, which has been on experimental for a few
months and I'll probably upload it to unstable soon. 4.3.0 is being
prepared in git, though it still needs BIND 9.10.x to happen first..


-- 
t

Processed: reopening 809260

[Debian Bug Tracking System]

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

> reopen 809260
Bug #809260 {Done: Chris Lamb } [cacti] cacti: Latest Squeeze 
LTS update of Cacti breaks graph viewing  (graph preview still works)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions cacti/0.8.7g-1+squeeze9+deb6u12.
> thanks
Stopping processing here.

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

Processed: Re: Bug#809602: javamail: FTBFS: [ERROR] Java heap space -> [Help 1]

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/bndtools/bnd/issues/724
Bug #809602 [src:javamail] javamail: FTBFS: [ERROR] Java heap space -> [Help 1]
Set Bug forwarded-to-address to 'https://github.com/bndtools/bnd/issues/724'.
> reassign -1 bnd 2.4.1-1
Bug #809602 [src:javamail] javamail: FTBFS: [ERROR] Java heap space -> [Help 1]
Bug reassigned from package 'src:javamail' to 'bnd'.
No longer marked as found in versions javamail/1.5.4-1.
Ignoring request to alter fixed versions of bug #809602 to the same values 
previously set
Bug #809602 [bnd] javamail: FTBFS: [ERROR] Java heap space -> [Help 1]
Marked as found in versions bnd/2.4.1-1.

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

Bug#809602: javamail: FTBFS: [ERROR] Java heap space -> [Help 1]

[Emmanuel Bourg]

Control: forwarded -1 https://github.com/bndtools/bnd/issues/724
Control: reassign -1 bnd 2.4.1-1

I confirm this is a bnd issue. This was fixed in bnd 3.0.

The fix is trivial I'll backport it.

Bug#803294: prepare for giflib5

[Matthias Klose]

any update on this? this is only fixed in experimental, not in unstable.

Bug#803291: prepare for giflib5

[Matthias Klose]

On 15.12.2015 23:04, Christian Welzel wrote:

Am 28.10.2015 um 15:53 schrieb Matthias Klose:


Planning an update of giflib to the current version 5.1.1. Giflib
slightly changes it's API, requiring soureful changes.


I'll look into this, and fix some other issues with the package on
the way. Currently looking for some source for the swf.


any update on this?

Bug#775623: Contribute to fixing the bug

[venkat]

Hi,
This is the first bug I am trying to fix. So, I want to ask a few questions:
1) Is it solvable by a person with no experience in fixing bugs such as 
myself?
2) If yes, can you please tell how to reproduce the bug on by Debian 
machine and maybe give a few pointers on how to fix the bug?
3) If no, can you please tell what would be a good place/bug to start 
working on for a beginner like myself?

Your help would be much appreciated.
Venkat