Processed: Re: obex-data-server: FTBFS with libopenobex 1.7.1: src/ods-obex.c:408: undefined reference to `OBEX_FindInterfaces'

[Debian Bug Tracking System]

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

> tags 810521 + patch
Bug #810521 [src:obex-data-server] obex-data-server: FTBFS with libopenobex 
1.7.1: src/ods-obex.c:408: undefined reference to `OBEX_FindInterfaces'
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: all those bugs are really RC

[Debian Bug Tracking System]

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

> # all those bugs ought to be RC
> # I understand though that boost 1.5 is going to be removed so *shrugs*
> severity 747951 serious
Bug #747951 [src:boost1.55] boost1.55: FTBFS: bogus alignment assumptions
Severity set to 'serious' from 'important'
> severity 793222 serious
Bug #793222 [src:boost1.55] boost1.55: change of type in system_error might 
break with GCC-5
Severity set to 'serious' from 'important'
> severity 803392 serious
Bug #803392 [src:boost1.55] boost1.55: still FTBS with g++ 5 on sid and testing
Severity set to 'serious' from 'important'
> --
Stopping processing here.

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

Bug#791195: fixed in lttoolbox 3.3.2~r61000-3.1

[Tino Didriksen]

On 3 February 2016 at 02:57, Andreas Beckmann  wrote:

> On Thu, 20 Aug 2015 16:00:44 + Julien Cristau 
> wrote:
> >  lttoolbox (3.3.2~r61000-3.1) unstable; urgency=medium
> >  .
> >* Non-maintainer upload.
> >* Rename library packages for g++5 ABI transition (closes: 791195).
>
> This change was recently reverted and I'm not convinced that this was a
> good idea.



That was my doing, on the basis that the transition should never have
happened.

Because I wasn't properly subscribed to this bug (due to using my mail@
address which procmail can't handle), I never knew the transition was
pushed through against my wishes, until I went to update lttoolbox to a
newer release.

There are only 2 other packages that depend on lttoolbox: apertium and
apertium-lex-tools, and I maintain those as well. All 3 are part of the
same upstream project, and are updated together if there are breaking
changes.

And because lttoolbox 3.3 was not even in testing at the time, nothing
outside my control could have built up dependencies on it, and indeed
nothing has.

The v5 transition was entirely unnecessary for this package, and I very
strongly want it gone.

-- Tino Didriksen

Bug#791195: fixed in lttoolbox 3.3.2~r61000-3.1

[Julien Cristau]

On Wed, Feb  3, 2016 at 10:46:02 +0100, Tino Didriksen wrote:

> On 3 February 2016 at 02:57, Andreas Beckmann  wrote:
> 
> > On Thu, 20 Aug 2015 16:00:44 + Julien Cristau 
> > wrote:
> > >  lttoolbox (3.3.2~r61000-3.1) unstable; urgency=medium
> > >  .
> > >* Non-maintainer upload.
> > >* Rename library packages for g++5 ABI transition (closes: 791195).
> >
> > This change was recently reverted and I'm not convinced that this was a
> > good idea.
> 
> 
> 
> That was my doing, on the basis that the transition should never have
> happened.
> 
> Because I wasn't properly subscribed to this bug (due to using my mail@
> address which procmail can't handle), I never knew the transition was
> pushed through against my wishes, until I went to update lttoolbox to a
> newer release.
> 
> There are only 2 other packages that depend on lttoolbox: apertium and
> apertium-lex-tools, and I maintain those as well. All 3 are part of the
> same upstream project, and are updated together if there are breaking
> changes.
> 
> And because lttoolbox 3.3 was not even in testing at the time, nothing
> outside my control could have built up dependencies on it, and indeed
> nothing has.
> 
> The v5 transition was entirely unnecessary for this package, and I very
> strongly want it gone.
> 
You haven't given a single good reason to revert the change.  Maybe you
would have preferred it didn't, but you're coming 6 months late to that
party.

Cheers,
Julien

Bug#810521: obex-data-server: FTBFS with libopenobex 1.7.1: src/ods-obex.c:408: undefined reference to `OBEX_FindInterfaces'

[Nobuhiro Iwamatsu]

tags 810521 + patch
thanks

Hi,

I created a patch which fix this problem.
Could you check and apply this patch?

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


obex-data-server-0.4.5.debdiff
Description: Binary data

Bug#791195: fixed in lttoolbox 3.3.2~r61000-3.1

[Kartik Mistry]

On Wed, Feb 3, 2016 at 4:04 PM, Julien Cristau  wrote:
>> The v5 transition was entirely unnecessary for this package, and I very
>> strongly want it gone.
>>
> You haven't given a single good reason to revert the change.  Maybe you
> would have preferred it didn't, but you're coming 6 months late to that
> party.

Apologies!

What is the best way to fix this?

-- 
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com

Bug#808216: Removal of debmirror from testing

[Bob Proulx]

Bernhard wrote:
> Do you see any chance to prevent the autoremoval?
> I see you have a patch because of bug #808216.
> For me, this package works fine, because i don't use the diff-files.

I don't think 'grave' "renders package unusable" is correct for this
since it seems to only affect those using diff files.  I also don't
use diff files and had not noticed any breakage.  It would be a
tragedy if it were removed from Testing for being unsuable since the
package isn't actually unusable.  It is quite usable to many.  Most?
Well... At least some of us.  Who knows how many since there is no way
to tell how many use --diff=none or not.

Bob

Bug#813563: alsa-utils: Overwrite files from unrelated package

[Michael Rasmussen]

Package: alsa-utils
Version: 1.0.29-1+b1
Severity: critical
Justification: breaks unrelated software

This bug: #813528 actually should have been made here. Please link.

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

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

Versions of packages alsa-utils depends on:
ii  dialog  1.2-20150920-1
ii  kmod22-1
ii  libasound2  1.1.0-1
ii  libc6   2.21-7
ii  libncursesw56.0+20151024-2
ii  libsamplerate0  0.1.8-8
ii  libtinfo5   6.0+20151024-2
ii  lsb-base9.20160110
ii  whiptail0.52.18-2

alsa-utils recommends no packages.

alsa-utils suggests no packages.

-- no debconf information



This mail was virus scanned and spam checked before delivery.
This mail is also DKIM signed. See header dkim-signature.

Processed: reassign 813426 to dpkg

[Debian Bug Tracking System]

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

> reassign 813426 dpkg
Bug #813426 [imagemagick-6.q16] warning: /etc/alternatives/compare is dangling; 
it will be updated with best choice
Bug reassigned from package 'imagemagick-6.q16' to 'dpkg'.
No longer marked as found in versions imagemagick/8:6.9.2.10+dfsg-2.
Ignoring request to alter fixed versions of bug #813426 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: reopening 791195

[Debian Bug Tracking System]

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

> reopen 791195
Bug #791195 {Done: Julien Cristau } [src:lttoolbox] 
lttoolbox: library transition may be needed when GCC 5 is the default
'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 lttoolbox/3.3.2~r61000-3.1.
> thanks
Stopping processing here.

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

Processed: found 813426 in 1.18.4

[Debian Bug Tracking System]

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

> found 813426 1.18.4
Bug #813426 [dpkg] warning: /etc/alternatives/compare is dangling; it will be 
updated with best choice
Marked as found in versions dpkg/1.18.4.
> thanks
Stopping processing here.

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

Bug#813568: php-guzzle: FTBFS: DefaultCacheStorageTest::testCachesRequests strpos() expects parameter 1 to be string, array given

[Chris Lamb]

Source: php-guzzle
Version: 3.9.3+dfsg-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,

php-guzzle fails to build from source in unstable/amd64:

  [..]

  Autoload file vendor/autoload.php generated.
  
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160203084908.RlfJUCZUHm/php-guzzle-3.9.3+dfsg'
 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160203084908.RlfJUCZUHm/php-guzzle-3.9.3+dfsg'
  http_proxy= phpunit
  PHPUnit 5.1.3 by Sebastian Bergmann and contributors.
  
  .   61 / 1531 (  
3%)
  .  122 / 1531 (  
7%)
  .  183 / 1531 ( 
11%)
  .  244 / 1531 ( 
15%)
  .  305 / 1531 ( 
19%)
  .  366 / 1531 ( 
23%)
  .  427 / 1531 ( 
27%)
  .  488 / 1531 ( 
31%)
  .  549 / 1531 ( 
35%)
  .  610 / 1531 ( 
39%)
  .  671 / 1531 ( 
43%)
  .  732 / 1531 ( 
47%)
  ....S  793 / 1531 ( 
51%)
  S  854 / 1531 ( 
55%)
  .  915 / 1531 ( 
59%)
  .  976 / 1531 ( 
63%)
  E..E...FEE... 1037 / 1531 ( 
67%)
  . 1098 / 1531 ( 
71%)
  . 1159 / 1531 ( 
75%)
  . 1220 / 1531 ( 
79%)
  . 1281 / 1531 ( 
83%)
  ...S. 1342 / 1531 ( 
87%)
  . 1403 / 1531 ( 
91%)
  F...F 1464 / 1531 ( 
95%)
  . 1525 / 1531 ( 
99%)
  ..1531 / 1531 
(100%)
  
  Time: 9.1 seconds, Memory: 46.50Mb
  
  There were 4 errors:
  
  1) Guzzle\Tests\Plugin\Cache\DefaultCacheStorageTest::testCachesRequests
  strpos() expects parameter 1 to be string, array given
  
  
/home/lamby/temp/cdt.20160203084908.RlfJUCZUHm/php-guzzle-3.9.3+dfsg/tests/Guzzle/Tests/Plugin/Cache/DefaultCacheStorageTest.php:53
  
  2) 
Guzzle\Tests\Plugin\Cache\DefaultCacheStorageTest::testCachesMultipleRequestsWithVary
  strpos() expects parameter 1 to be string, array given
  
  
/home/lamby/temp/cdt.20160203084908.RlfJUCZUHm/php-guzzle-3.9.3+dfsg/tests/Guzzle/Tests/Plugin/Cache/DefaultCacheStorageTest.php:96
  
  3) 
Guzzle\Tests\Plugin\Cache\DefaultCacheStorageTest::testUsesStaleTimeDirectiveForTtd
 with data set #0 (Guzzle\Http\Message\Request Object (...), 
Guzzle\Http\Message\Response Object (...))
  strpos() expects parameter 1 to be string, array given
  
  
/home/lamby/temp/cdt.20160203084908.RlfJUCZUHm/php-guzzle-3.9.3+dfsg/tests/Guzzle/Tests/Plugin/Cache/DefaultCacheStorageTest.php:177
  
  4) 
Guzzle\Tests\Plugin\Cache\DefaultCacheStorageTest::testUsesStaleTimeDirectiveForTtd
 with data set #1 (Guzzle\Http\Message\Request Object (...), 
Guzzle\Http\Message\Response Object (...))
  strpos() expects parameter 1 to be string, array given
  
  
/home/lamby/temp/cdt.20160203084908.RlfJUCZUHm/php-guzzle-3.9.3+dfsg/tests/Guzzle/Tests/Plugin/Cache/DefaultCacheStorageTest.php:177
  
  --
  
  There were 3 failures:
  
  1) 
Guzzle\Tests\Plugin\Cache\DefaultCacheStorageTest::testEnsuresResponseIsStillPresent
  Failed asserting that Guzzle\Http\Message\Response Object 
&7235161d1a489634 (
  'body' => Guzzle\Http\EntityBody Object &723516141a489634 
(
  'contentEncoding' => false
  'rewindFunction' => null
  'stream' => resource(3521) of type (stream)
  'size' => null
  'cache' => Array &0 (
  'wrapper_type' => 'PHP'
  'stream_type' => 'TEMP'
  'mode' => 'w+b'
  'unread_bytes' => 0
  'seekable' => true
  'uri' => 'php://temp'

Bug#813569: profitbricks-client: FTBFS: Couldn't find index page for 'suds' (maybe misspelled?)

[Chris Lamb]

Source: profitbricks-client
Version: 1.0.0-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

profitbricks-client fails to build from source in unstable/amd64:

  [..]
  
  Build finished. The manual pages are in _build/man.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160203085036.rmpR9BoqGE/profitbricks-client-1.0.0/docs'
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160203085036.rmpR9BoqGE/profitbricks-client-1.0.0'
 dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:184: python2.7 setup.py test 
  running test
  Searching for suds
  
  Note: Bypassing https://pypi.python.org/simple/suds/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).
  
  Couldn't find index page for 'suds' (maybe misspelled?)
  Scanning index of all packages (this may take a while)
  
  Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).
  
  No local packages or download links found for suds
  error: Could not find suitable distribution for Requirement.parse('suds')
  E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
  dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 25

  [..]

The full build log is attached.


Regards,

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


profitbricks-client.1.0.0-2.unstable.amd64.log.txt.gz
Description: Binary data

Processed: blacs-mpi: diff for NMU version 1.1-33.2

[Debian Bug Tracking System]

Processing control commands:

> tags 813490 + pending
Bug #813490 [src:blacs-mpi] blacs-mpi: patch for blacs-mpi to build with 
openmpi1.10
Bug #813357 [src:blacs-mpi] blacs-mpi: FTBFS: /usr/bin/ld: cannot find -lmpi_f77
Added tag(s) pending.
Added tag(s) pending.

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

Bug#813490: blacs-mpi: diff for NMU version 1.1-33.2

[Mattia Rizzolo]

Control: tags 813490 + pending

Dear maintainer,

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

I used DELEYED/5 just because this bug is really recent, but since it's
now one blocker in a transition I already did it.
I'll be happy to reschedule the NMU as you see fit.

Regards.

-- 
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  `-
diffstat for blacs-mpi_1.1-33.1 blacs-mpi_1.1-33.2

 blacs-mpi-implementations.patch |2 +-
 changelog   |9 +
 control |2 +-
 control.in  |2 +-
 rules   |2 +-
 5 files changed, 13 insertions(+), 4 deletions(-)

diff -u blacs-mpi-1.1/debian/blacs-mpi-implementations.patch blacs-mpi-1.1/debian/blacs-mpi-implementations.patch
--- blacs-mpi-1.1/debian/blacs-mpi-implementations.patch
+++ blacs-mpi-1.1/debian/blacs-mpi-implementations.patch
@@ -76,7 +76,7 @@
 +   MPIdir = /usr/lib/openmpi
 +   MPILIBdir = $(MPIdir)/lib
 +   MPIINCdir = $(MPIdir)/include
-+   MPILIB = -L/usr/lib/openmpi/lib -lmpi -lmpi_f77
++   MPILIB = $$(pkg-config mpi-fort --libs)
 +   CC = mpicc.openmpi
 +   F77 = mpif90.openmpi
 +   TRANSCOMM = -DUseMpi2
diff -u blacs-mpi-1.1/debian/changelog blacs-mpi-1.1/debian/changelog
--- blacs-mpi-1.1/debian/changelog
+++ blacs-mpi-1.1/debian/changelog
@@ -1,3 +1,12 @@
+blacs-mpi (1.1-33.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use `pkg-config mpi-fort --libs` rather than hard-coded libs for
+openmpi.  Patch from Alastair McKinstry .
+Closes: #813490
+
+ -- Mattia Rizzolo   Wed, 03 Feb 2016 08:44:20 +
+
 blacs-mpi (1.1-33.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u blacs-mpi-1.1/debian/control blacs-mpi-1.1/debian/control
--- blacs-mpi-1.1/debian/control
+++ blacs-mpi-1.1/debian/control
@@ -8,7 +8,7 @@
 Priority: extra
 Maintainer: Muammar El Khatib 
 Standards-Version: 3.9.1
-Build-Depends: debhelper (>= 7), mpi-default-dev (>= 1.0), gfortran
+Build-Depends: debhelper (>= 7), mpi-default-dev (>= 1.0), gfortran, pkg-config
 Homepage: http://www.netlib.org/blacs/
 
 Package: libblacs-openmpi1
diff -u blacs-mpi-1.1/debian/control.in blacs-mpi-1.1/debian/control.in
--- blacs-mpi-1.1/debian/control.in
+++ blacs-mpi-1.1/debian/control.in
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Muammar El Khatib 
 Standards-Version: 3.9.1
-Build-Depends: debhelper (>= 7), mpi-default-dev (>= 1.0), gfortran
+Build-Depends: debhelper (>= 7), mpi-default-dev (>= 1.0), gfortran, pkg-config
 Homepage: http://www.netlib.org/blacs/
 
 Package: libblacs-openmpi1
diff -u blacs-mpi-1.1/debian/rules blacs-mpi-1.1/debian/rules
--- blacs-mpi-1.1/debian/rules
+++ blacs-mpi-1.1/debian/rules
@@ -57,7 +57,7 @@
 	  done;\
 	  cd .. ;\
 	  gcc -shared -Wl,-soname=lib$$i-openmpi.so.1 -o lib$$i-openmpi.so.1.1 \
-	-L/usr/lib/openmpi/lib/ $$(find tmp -name "*.o") -lmpi -lmpi_f77; \
+	$$(find tmp -name "*.o") $$(pkg-config mpi-fort --libs); \
 	  ln -fs lib$$i-openmpi.so.1.1 lib$$i-openmpi.so.1 ;\
 	  ln -fs lib$$i-openmpi.so.1 lib$$i-openmpi.so ;\
 	  rm -f tmp/tmp/* ; rmdir tmp/tmp ; rm tmp/* ;\


signature.asc
Description: PGP signature

Bug#813461: cqrlog: FTBFS: lcommon.pp(515,18) Error: (5038) identifier idents no member "family"

[Petr Hlozek]

This bug is caused by new fpc version 3.0. I'll fix it in next CQRLOG release.

-- 
http://HamQTH.com/ok2cqr
http://ok2cqr.com
http://cqrlog.com

Processed: Re: FTBFS: error: 'OBEX_TRANS_CUST' undeclared

[Debian Bug Tracking System]

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

> tags 811300 + patch
Bug #811300 [libsyncml] FTBFS: error: 'OBEX_TRANS_CUST' undeclared
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#811300: FTBFS: error: 'OBEX_TRANS_CUST' undeclared

[Nobuhiro Iwamatsu]

tags 811300 + patch
thanks

Hi,

I created a patch which fix this problem.
Could you check and apply this patch?

Best regards,
  Nobuhiro
-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


libsyncml-0.5.4.debdiff
Description: Binary data

Processed (with 1 error): forcibly merging 813426 813546

[Debian Bug Tracking System]

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

> forcemerge 813426 813546
Bug #813426 [imagemagick-6.q16] warning: /etc/alternatives/compare is dangling; 
it will be updated with best choice
Unable to merge bugs because:
package of #813546 is 'aptitude' not 'imagemagick-6.q16'
Failed to forcibly merge 813426: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: Re: ircp-tray: FTBFS with libopenobex 1.7.1: src/ircp_server.c:273: undefined reference to `OBEX_UnicodeToChar'

[Debian Bug Tracking System]

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

> tags 810562 + patch
Bug #810562 [src:ircp-tray] ircp-tray: FTBFS with libopenobex 1.7.1: 
src/ircp_server.c:273: undefined reference to `OBEX_UnicodeToChar'
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#810562: ircp-tray: FTBFS with libopenobex 1.7.1: src/ircp_server.c:273: undefined reference to `OBEX_UnicodeToChar'

[Nobuhiro Iwamatsu]

tags 810562 + patch
thanks

Hi,

I created a patch which fix this problem.
Could you check and apply this patch?

Best regards,
  Nobuhiro

-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6


ircp-tray-0.7.6.debdiff
Description: Binary data

Bug#813571: virtualenv: Broken dependencies

[Francisco José Rodríguez Bogado]

Package: virtualenv
Version: 1.11.6+ds-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm trying to install virtualenv on Sid. It depends on python3-virtualenv, that
depends on python-setuptools-whl *and* python-pip-whl. But python-pip-whl
(8.0.2-2) breaks python-setuptools-whl >=18.8-1, which is the version in Sid
repo. If I install python-setuptools-whl, apt-get removes python-pip-whl. So I
can't install python3-virtualenv neither python-virtualenv.

Thanks in advance.



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

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

Bug#813565: xserver-xorg-video-nvidia: This version is incompatible with the current unstable xserver abi

[Eric Valette]

Package: xserver-xorg-video-nvidia
Version: 355.11-1
Severity: critical
Justification: breaks unrelated software

sddm no more starts. starting xserverr manually via startx, nvidia driver
report ABI incompatibilities and suggest to pass -ignoreABI. Doing this
the xserver crash even before I can start my desktop.

So it does not follow the experimental rules that it should work with
unstable pacakges

-- Package-specific info:
uname -a:
Linux tri-yann4 4.4.1 #13 SMP PREEMPT Sun Jan 31 23:22:15 CET 2016 x86_64 
GNU/Linux

/proc/version:
Linux version 4.4.1 (valette@tri-yann4) (gcc version 5.3.1 20160121 (Debian 
5.3.1-7) ) #13 SMP PREEMPT Sun Jan 31 23:22:15 CET 2016

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  355.11  Wed Aug 26 16:35:41 PDT 
2015
GCC version:  gcc version 5.3.1 20160121 (Debian 5.3.1-7) 

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 
670] [10de:1189] (rev a1) (prog-if 00 [VGA controller])
Subsystem: CardExpert Technology GK104 [GeForce GTX 670] [10b0:1189]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia_current

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.265474] vgaarb: setting as boot device: PCI::01:00.0
[0.265476] vgaarb: device added: 
PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.265481] vgaarb: loaded
[0.265482] vgaarb: bridge control possible :01:00.0
[0.359208] Linux agpgart interface v0.103
[1.038950] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input11
[1.039063] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input12
[1.039169] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input13
[1.039287] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:02.0/:01:00.1/sound/card1/input14
[1.998544] nvidia: module license 'NVIDIA' taints kernel.
[2.007015] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[2.007407] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[2.007420] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  355.11  Wed Aug 
26 16:35:41 PDT 2015

Device node permissions:
crw-rw+ 1 root video 226, 0 Feb  3 08:12 /dev/dri/card0
video:x:44:valette,vdr,hts,sddm

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 valette valette 1722 Aug 20  2014 /etc/X11/xorg.conf
lrwxrwxrwx 1 rootroot  15 Feb  2 18:16 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 rootroot  49 Sep  2 08:50 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 rootroot  44 Feb  2 18:16 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 rootroot  48 Sep  2 08:50 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 rootroot  48 Sep  2 08:50 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 rootroot  43 Feb  2 18:16 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 rootroot  43 Feb  2 18:16 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 rootroot  50 Feb  2 18:16 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 rootroot  50 Feb  2 18:16 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 rootroot  52 Sep  2 08:50 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 rootroot  52 Sep  2 08:50 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 rootroot  47 Feb  2 18:16 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 rootroot  47 Feb  2 18:16 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 rootroot  51 Feb  2 18:16 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 rootroot  25 Feb  2 18:16 

Bug#813256: flex: diff for NMU version 2.6.0-3.1

[Salvatore Bonaccorso]

Control: tags 813256 + pending

Dear Manoj,

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

Regards,
Salvatore
diff -u flex-2.6.0/debian/changelog flex-2.6.0/debian/changelog
--- flex-2.6.0/debian/changelog
+++ flex-2.6.0/debian/changelog
@@ -1,3 +1,12 @@
+flex (2.6.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Comments in C style in skeleton.
+Fixes "flex: C++ style comment in C output".
+Thanks to Tim R??hsen  (Closes: #813256)
+
+ -- Salvatore Bonaccorso   Wed, 03 Feb 2016 09:14:07 +0100
+
 flex (2.6.0-3) unstable; urgency=low
 
   * Revert the help2man fix; it was creating errors in the diff.gz
only in patch2:
unchanged:
--- flex-2.6.0.orig/src/flex.skl
+++ flex-2.6.0/src/flex.skl
@@ -2350,7 +2350,7 @@
 		 * scanner will even need a stack. We use 2 instead of 1 to avoid an
 		 * immediate realloc on the next call.
  */
-		num_to_alloc = 1; // After all that talk, this was set to 1 anyways...
+		num_to_alloc = 1; /* After all that talk, this was set to 1 anyways... */
 		YY_G(yy_buffer_stack) = (struct yy_buffer_state**)yyalloc
 (num_to_alloc * sizeof(struct yy_buffer_state*)
 M4_YY_CALL_LAST_ARG);

Processed: flex: diff for NMU version 2.6.0-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 813256 + pending
Bug #813256 [flex] flex: C++ style comment in C output
Bug #813460 [flex] boxes: FTBFS: error: C++ style comments are not allowed in 
ISO C90
Added tag(s) pending.
Added tag(s) pending.

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

Processed: Re: [pkg-horde] Bug#813573: [php-horde] XSS vulnerability in menu bar

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + security upstream fixed-upstream pending
Bug #813573 [php-horde] [php-horde] XSS vulnerability in menu bar
Added tag(s) security, fixed-upstream, upstream, and pending.
> severity -1 grave
Bug #813573 [php-horde] [php-horde] XSS vulnerability in menu bar
Severity set to 'grave' from 'normal'
> forwarded -1 https://bugs.horde.org/ticket/14213
Bug #813573 [php-horde] [php-horde] XSS vulnerability in menu bar
Set Bug forwarded-to-address to 'https://bugs.horde.org/ticket/14213'.

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

Bug#812188: marked as done (debiandoc-sgml-doc-pt-br: FTBFS: make[1]: nsgmls: Command not found)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 12:05:16 +
with message-id 
and subject line Bug#812188: fixed in debiandoc-sgml-doc-pt-br 1.1.12
has caused the Debian Bug report #812188,
regarding debiandoc-sgml-doc-pt-br: FTBFS: make[1]: nsgmls: Command not found
to be marked as done.

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

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


-- 
812188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debiandoc-sgml-doc-pt-br
Version: 1.1.11
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,

debiandoc-sgml-doc-pt-br fails to build from source in unstable/amd64:

  [..]

  dh clean
 dh_testdir
 dh_auto_clean
make -j1 clean
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160121121515.djoqVn2ttF/debiandoc-sgml-doc-pt-br-1.1.11'
  /bin/rm -rf debiandoc-sgml.html debiandoc-sgml.pt_BR.txt
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160121121515.djoqVn2ttF/debiandoc-sgml-doc-pt-br-1.1.11'
 dh_clean
   debian/rules build
  dh build
 dh_testdir
 dh_update_autotools_config
 dh_auto_configure
 dh_auto_build
make -j1
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160121121515.djoqVn2ttF/debiandoc-sgml-doc-pt-br-1.1.11'
  nsgmls -wall -E20 -gues debiandoc-sgml.pt_BR.sgml
  make[1]: nsgmls: Command not found
  Makefile:27: recipe for target 'all' failed
  make[1]: *** [all] Error 127
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160121121515.djoqVn2ttF/debiandoc-sgml-doc-pt-br-1.1.11'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:14: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


debiandoc-sgml-doc-pt-br.1.1.11.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: debiandoc-sgml-doc-pt-br
Source-Version: 1.1.12

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

Debian distribution maintenance software
pp.
Osamu Aoki  (supplier of updated debiandoc-sgml-doc-pt-br 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 03 Feb 2016 20:48:20 +0900
Source: debiandoc-sgml-doc-pt-br
Binary: debiandoc-sgml-doc-pt-br
Architecture: source all
Version: 1.1.12
Distribution: unstable
Urgency: medium
Maintainer: Osamu Aoki 
Changed-By: Osamu Aoki 
Description:
 debiandoc-sgml-doc-pt-br - Documentation for DebianDoc-SGML in Brazilian 
Portuguese
Closes: 812188
Changes:
 debiandoc-sgml-doc-pt-br (1.1.12) unstable; urgency=medium
 .
   * Use onsgml for the migration from sp to opensp. Closes: #812188
Checksums-Sha1:
 34bc33e917cbb28dab787537643d9c4e9d9f2dd3 1694 
debiandoc-sgml-doc-pt-br_1.1.12.dsc
 ee0b8b6c008101781958d635086cecac17c902ec 10268 
debiandoc-sgml-doc-pt-br_1.1.12.tar.xz
 150d38797de7082674d0e20eb7e33c4d6c292852 17930 
debiandoc-sgml-doc-pt-br_1.1.12_all.deb
Checksums-Sha256:
 4ddd9c65f346dd51793dd19e7f20452efd144d3e045f6ea87f2794e3adb85c94 1694 
debiandoc-sgml-doc-pt-br_1.1.12.dsc
 75f75e096b9fcbc89fd0e548ebd74616395de4347f001be4e8a28ab22d6e3383 10268 
debiandoc-sgml-doc-pt-br_1.1.12.tar.xz
 d7636c45e5b1b39be5119bf539d484b3771d90f7bc10c9e8a988199fc95b1616 17930 
debiandoc-sgml-doc-pt-br_1.1.12_all.deb
Files:
 a3d7d3831c5859e1ae27f579318fb217 1694 doc optional 
debiandoc-sgml-doc-pt-br_1.1.12.dsc
 caa33c8127114d065e3e0125842b1401 10268 doc optional 
debiandoc-sgml-doc-pt-br_1.1.12.tar.xz
 bf420b150195d7a9f948ca769019b184 17930 doc optional 
debiandoc-sgml-doc-pt-br_1.1.12_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWseuEAAoJEB4TVogd2NeR5roQAJnPyJ1Kcrz/SAGy491pDUfM

Bug#752667: marked as done (ldirectord uses inet_ntop without importing it from the Socket library)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 09:41:57 +
with message-id 
and subject line Bug#752667: fixed in resource-agents 1:3.9.6-1
has caused the Debian Bug report #752667,
regarding ldirectord uses inet_ntop without importing it from the Socket library
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.)


-- 
752667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ldirectord
Version: 1:3.9.2-5+deb7u2
Severity: critical
Tags: upstream
Justification: causes serious data loss

Hi,

This is easy to fix, but it was hard to troubleshoot. Any load balancer
relying on simpletcp checks will fail when upgrade from squeeze to wheezy
basically because of this.

Other functionalities of ldirectord could be affected (we were hit just
by simpletc checks not working anymore).

Regards,

Juan

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

Kernel: Linux 3.2.0-64-generic (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Source: resource-agents
Source-Version: 1:3.9.6-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated 
resource-agents package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Feb 2016 17:17:34 +0100
Source: resource-agents
Binary: resource-agents ldirectord
Architecture: source
Version: 1:3.9.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Christoph Berg 
Description:
 ldirectord - Monitors virtual services provided by LVS
 resource-agents - Cluster Resource Agents
Closes: 569533 664645 672265 681818 690928 707878 709410 720453 739873 752667 
802990
Changes:
 resource-agents (1:3.9.6-1) unstable; urgency=medium
 .
   [ Christoph Berg ]
   * New upstream release.
 + ldirectord uses inet_ntop correctly. (Closes: #752667)
 + Xen handler supports "xl". (Closes: #672265)
 + Pure-FTPd RA creates pidfile directory. (Closes: #707878)
 + Removed bashism within Xinitd (Closes: #690928)
 + Bashism in pgsql agent fixed (Closes: #802990)
 + Upgrading from previous version fixed (Closes: #739873)
 + Crash fixed (Closes: #569533)
 + IPv6addr fixed (Closes: #709410)
 + findif doesn't require netmask anymore (Closes: #720453)
 + lxc agent fixed (Closes: #681818)
   * Update debian/copyright.
   * Bump dh compat to 9.
   * Rewrite ldirectord description, the old one was a mess.
   * Install upstream ldirectord.cf as example.
   * debian/ldirectord.init: remove "exec". (Closes: #664645)
   * debian/patches/mysql-path.patch: Now applies to heartbeat/mysql-common.sh.
   * Remove debian/patches/ocf-asterisk, went upstream.
   * Drop resource-agents-dev, it only contained a single line in a single file
 (but was Arch: any). Move agent_config.h to resource-agents.
   * Simplify debian/*.install.
   * Replace hardening-wrapper with buildflags.mk.
   * Build-Depend on systemd for systemd.pc.
   * Remove Python-Version from debian/control.
   * Write .tarball-version at build-time.
   * Add myself to Uploaders; bump Standards-Version.
 .
   [ Adrian Vondendriesch ]
   * Install upstream ldirectord.service file
   * Drop fix-gethostinfo-v2 patch. The original bug is fixed by upstream
 commit 9d91c7 and 0d4438.
   * Add myself to Uploaders.
   * Add VCS-Git and VCS-Homepage to debian/changelog.
   * Change debian/watch to track new upstream location.
Checksums-Sha1:
 5a7970befeab3eb00e599e0b1da014e7d815308c 2565 resource-agents_3.9.6-1.dsc
 452a16358d949d75ec209d2e240f9547c0655ba0 617790 
resource-agents_3.9.6.orig.tar.gz
 2b3fdb95923b465304dd38a8a1c02377ea59ed9a 16148 

Bug#739873: marked as done (ldirectord: Upgrade from sid: ldirectord fails to start: Error [8533] reading file /etc/ldirectord.cf at line $number: invalid address for virtual service)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 09:41:57 +
with message-id 
and subject line Bug#739873: fixed in resource-agents 1:3.9.6-1
has caused the Debian Bug report #739873,
regarding ldirectord: Upgrade from sid: ldirectord fails to start: Error [8533] 
reading file /etc/ldirectord.cf at line $number: invalid address for virtual 
service
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.)


-- 
739873: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ldirectord
Version: 1:3.9.5+git+a626847-1
Severity: serious
Justification: fails to upgrade from previous version, does not start anymore

Hi Martin and HA team

Upgrading ldirectord from unstable to the version in experimental
(1:3.9.5+git+a626847-1) causes the package not to upgrade correctly
and ldirectord not starting anymore. I played around in a vm setup
with the configuration below to reproduce:

root@sid:~# service ldirectord status
[] Running ldirectord: statusldirectord for /etc/ldirectord.cf is running 
with pid: 7537
root@sid:~# cat /etc/ldirectord.cf 
checktimeout=20
checkinterval=5
autoreload=yes
quiescent=no

# web service vip (http)
virtual=192.168.122.60:80
real=192.168.122.55 gate 1 "/", "It works"
real=192.168.122.56 gate 1 "/", "It works"
service=http
checkport=80
protocol=tcp
scheduler=wrr
checktype=negotiate
virtualhost="web-vip.local"
root@sid:~# apt-get -t experimental install ldirectord
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  ldirectord
1 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
Need to get 0 B/63.6 kB of archives.
After this operation, 5,120 B of additional disk space will be used.
(Reading database ... 27350 files and directories currently installed.)
Preparing to unpack .../ldirectord_1%3a3.9.5+git+a626847-1_all.deb ...
[] Running ldirectord: stopUnpacking ldirectord (1:3.9.5+git+a626847-1) 
over (1:3.9.3+git20121009-3) ...
Processing triggers for man-db (2.6.6-1) ...
Setting up ldirectord (1:3.9.5+git+a626847-1) ...
[] Running ldirectord: startUse of uninitialized value $ip_port in pattern 
match (m//) at /usr/sbin/ldirectord line 1789,  line 15.
Error [8533] reading file /etc/ldirectord.cf at line 7: invalid address for 
virtual service
invoke-rc.d: initscript ldirectord, action "start" failed.
dpkg: error processing package ldirectord (--configure):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 ldirectord
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@sid:~#

With the above configuration now ldirectord does not start anymore.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: resource-agents
Source-Version: 1:3.9.6-1

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated 
resource-agents package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Feb 2016 17:17:34 +0100
Source: resource-agents
Binary: resource-agents ldirectord
Architecture: source
Version: 1:3.9.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Christoph Berg 
Description:
 ldirectord - Monitors virtual services provided by LVS
 resource-agents - Cluster Resource Agents
Closes: 569533 664645 672265 681818 690928 707878 709410 720453 739873 752667 
802990
Changes:
 resource-agents (1:3.9.6-1) unstable; urgency=medium
 .
   [ Christoph Berg ]
   * New upstream release.
 + ldirectord uses inet_ntop correctly. (Closes: #752667)
 + Xen handler supports "xl". (Closes: #672265)
 + Pure-FTPd RA creates pidfile directory. (Closes: #707878)
 + 

Processed: forcibly merging 813426 813546

[Debian Bug Tracking System]

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

> forcemerge 813426 813546
Bug #813426 [dpkg] warning: /etc/alternatives/compare is dangling; it will be 
updated with best choice
Bug #813546 [dpkg] loop when package is in "Bu" state and one tries to install 
it
Severity set to 'serious' from 'normal'
Marked as found in versions dpkg/1.18.4.
Added tag(s) moreinfo.
Merged 813426 813546
> thanks
Stopping processing here.

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

Bug#813569: marked as done (profitbricks-client: FTBFS: Couldn't find index page for 'suds' (maybe misspelled?))

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 11:38:20 +
with message-id 
and subject line Bug#813569: fixed in profitbricks-client 1.0.1-1
has caused the Debian Bug report #813569,
regarding profitbricks-client: FTBFS: Couldn't find index page for 'suds' 
(maybe misspelled?)
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.)


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

Dear Maintainer,

profitbricks-client fails to build from source in unstable/amd64:

  [..]
  
  Build finished. The manual pages are in _build/man.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160203085036.rmpR9BoqGE/profitbricks-client-1.0.0/docs'
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160203085036.rmpR9BoqGE/profitbricks-client-1.0.0'
 dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:184: python2.7 setup.py test 
  running test
  Searching for suds
  
  Note: Bypassing https://pypi.python.org/simple/suds/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).
  
  Couldn't find index page for 'suds' (maybe misspelled?)
  Scanning index of all packages (this may take a while)
  
  Note: Bypassing https://pypi.python.org/simple/ (disallowed host; see 
http://bit.ly/1dg9ijs for details).
  
  No local packages or download links found for suds
  error: Could not find suitable distribution for Requirement.parse('suds')
  E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
  dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
  debian/rules:4: recipe for target 'build' failed
  make: *** [build] Error 25

  [..]

The full build log is attached.


Regards,

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


profitbricks-client.1.0.0-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: profitbricks-client
Source-Version: 1.0.1-1

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

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

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated 
profitbricks-client package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 03 Feb 2016 12:00:39 +0100
Source: profitbricks-client
Binary: python-profitbricks-client python-profitbricks-client-doc
Architecture: source all
Version: 1.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung 
Changed-By: Benjamin Drung 
Description:
 python-profitbricks-client - ProfitBricks Client
 python-profitbricks-client-doc - ProfitBricks Client documentation
Closes: 813569
Changes:
 profitbricks-client (1.0.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Use suds-jurko. (Closes: #813569)
   * Bump Standards-Version to 3.9.7
   * Install bash completion into /usr/share/bash-completion/completions
Checksums-Sha1:
 0b2ed09c97eeaf299b8ac557cd6249d7ab3dc2ca 2075 profitbricks-client_1.0.1-1.dsc
 1b650b2e10b976cb51139ffe72c96bc5dbd88fbe 32668 
profitbricks-client_1.0.1.orig.tar.xz
 bfb362565138bfab5d1f289058df489bea71ece7 2324 
profitbricks-client_1.0.1-1.debian.tar.xz
 a1243d9b451489008636e3e612ed828b04c84fd4 23472 
python-profitbricks-client-doc_1.0.1-1_all.deb
 ba840229ed48f8bff1fd8f9afbfe0fde6b5a628c 16078 
python-profitbricks-client_1.0.1-1_all.deb
Checksums-Sha256:
 59cc5aa815f95dabb6fdd8eeaa2cc8f5325757f166fbb5f4172d85ed75327a60 2075 
profitbricks-client_1.0.1-1.dsc
 dbb5620243a39f9fc5e2ce70529b47e5422fdbc4e8c52d4a3ff65f013c895974 32668 
profitbricks-client_1.0.1.orig.tar.xz
 

Bug#811203: marked as done (marble: build-depend on not-built anymore package libquazip-qt5-dev)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 13:01:06 +
with message-id 
and subject line Bug#811203: fixed in marble 4:15.12.1-1
has caused the Debian Bug report #811203,
regarding marble: build-depend on not-built anymore package libquazip-qt5-dev
to be marked as done.

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

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


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

Dear maintainer,

there is small uncoordinated transition concerning libquazip, where
binaries have been renamed.

please switch the build-dependency from libquazip-qt5-dev to
libquazip-dev.

-- 
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
--- End Message ---
--- Begin Message ---
Source: marble
Source-Version: 4:15.12.1-1

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

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

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated marble package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 01 Feb 2016 10:23:56 +0100
Source: marble
Binary: marble marble-maps marble-qt marble-data marble-plugins 
libmarblewidget-qt5-23 libastro1 libmarble-dev libastro-dev
Architecture: source amd64 all
Version: 4:15.12.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 libastro-dev - development files for the Marble astrononmy library
 libastro1  - Marble astronomy library
 libmarble-dev - development files for the Marble globe widget library
 libmarblewidget-qt5-23 - Marble globe widget library
 marble - globe and map widget
 marble-data - data files for Marble
 marble-maps - globe and map widget for mobile form factors
 marble-plugins - plugins for Marble
 marble-qt  - globe and map widget (no KDE dependencies)
Closes: 811203
Changes:
 marble (4:15.12.1-1) experimental; urgency=medium
 .
   * New upstream release (15.12.0).
   * Change libquazip-qt5-dev build dep to libquazip5-dev. (Closes:
 #811203) Thanks to Sebastiaan Couwenberg.
   * Drop patch: fix_qmake_fallback.diff
   * Update symbols files.
   * New upstream release (15.12.1).
Checksums-Sha1:
 7abbf9a79696fdfc8925d19d75e7c6d4bc70f0c8 3142 marble_15.12.1-1.dsc
 2cf8b5909b9a3f3b3d9fc17970dd0d3d3f0c1958 23768028 marble_15.12.1.orig.tar.xz
 5d2eed35a3455b55f6c459eb3bab01e8a9f5694d 93724 marble_15.12.1-1.debian.tar.xz
 262e74e88d8194397473be4ddf5f83e4d4bb4d02 31396 libastro-dev_15.12.1-1_amd64.deb
 455ec3938c1b05b28a9389994652e0ff1a8d8d1c 123024 libastro1_15.12.1-1_amd64.deb
 96d3780203947f7091f4c7d3f389faf5d50d251b 303334 
libmarble-dev_15.12.1-1_amd64.deb
 9d802f5007a538f32ff6bd99bbbe1b336705d72f 2021978 
libmarblewidget-qt5-23_15.12.1-1_amd64.deb
 378e8f3592f86b39a19e758db7b5462271220ffc 17243068 marble-data_15.12.1-1_all.deb
 97c88b54331723cfd7eee087624ed06bb9bfda78 102238 marble-maps_15.12.1-1_amd64.deb
 8eea8adbfcf7973869d716bb39a075615e82660e 1402122 
marble-plugins_15.12.1-1_amd64.deb
 dafb1baf6eb80bba75d8a812799bb7da1ddefa10 104994 marble-qt_15.12.1-1_amd64.deb
 c07c477c60f0ed93c4bc03f05893345a762db491 205672 marble_15.12.1-1_amd64.deb
Checksums-Sha256:
 46befe813362e43c3c8c2898504abf2d3b278c76ff5ae1a018127bea52c1550f 3142 
marble_15.12.1-1.dsc
 957297f5187f5e4f75d5a1379742bc4fd0d5c72b7e906d951d1828246a5bfe97 23768028 
marble_15.12.1.orig.tar.xz
 8cd7cd5f512852113b31d54d919fe8084c8a7ae705a69397bfc88cadacf844cd 93724 
marble_15.12.1-1.debian.tar.xz
 9288cf1d16ccb04ed7aea54af33211bcc61f8de588f76a58db948dbc43389f24 31396 
libastro-dev_15.12.1-1_amd64.deb
 

Bug#812409: marked as done (postgresql-prioritize: depends on unavailable postgresql-9.5.0)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 13:01:17 +
with message-id 
and subject line Bug#812409: fixed in postgresql-prioritize 1.0.4-1.2
has caused the Debian Bug report #812409,
regarding postgresql-prioritize: depends on unavailable postgresql-9.5.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.)


-- 
812409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-prioritize
Version: 1.0.4-1.1
Severity: serious
Tags: sid
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

After the binNMU against postgresql-9.5 it picked up a dependency on
postgresql-9.5.0 which does not exist. Probably some substvars have
changed with the new version.

Also Maintainer and Uploader are the same person with different
addresses.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: postgresql-prioritize
Source-Version: 1.0.4-1.2

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated 
postgresql-prioritize package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Feb 2016 11:37:54 +0100
Source: postgresql-prioritize
Binary: postgresql-9.5-prioritize
Architecture: source amd64
Version: 1.0.4-1.2
Distribution: unstable
Urgency: medium
Maintainer: Cyril Bouthors 
Changed-By: Christoph Berg 
Description:
 postgresql-9.5-prioritize - Get and set the nice priorities of PostgreSQL 
backends
Closes: 812409
Changes:
 postgresql-prioritize (1.0.4-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Update package for PostgreSQL 9.5. (Closes: #812409)
   * Update packaging to 3.0 (quilt) and pg_buildext.
Checksums-Sha1:
 47e799c7bc56dfb99db7e50e8a07cee11bb82df0 2098 
postgresql-prioritize_1.0.4-1.2.dsc
 c36e2fccd9d367d8b430a8f2bc9fddde33cfd055 2848 
postgresql-prioritize_1.0.4-1.2.debian.tar.xz
 9e49e3b897b7114a855bce9372afae4e6851d41b 2286 
postgresql-9.5-prioritize-dbgsym_1.0.4-1.2_amd64.deb
 94ed06b5afb8a31362fb2b79f22f400042223b16 6260 
postgresql-9.5-prioritize_1.0.4-1.2_amd64.deb
Checksums-Sha256:
 878ae41a9714cf17e772c033214399db2d05b1155b5ac38eb2b4fd6d264a0a97 2098 
postgresql-prioritize_1.0.4-1.2.dsc
 cc0196708b66314212bc7b57662c1ad883644c7dfc1439f0651fa1bf7d061546 2848 
postgresql-prioritize_1.0.4-1.2.debian.tar.xz
 54ccab24ac23a3d5e3d131435c1f393b9a8d87b8f181d0ca5d26d3c99713680d 2286 
postgresql-9.5-prioritize-dbgsym_1.0.4-1.2_amd64.deb
 efc2cfbdcbdba189de762f399fade37fd3243d094ddc161349ef36e4be6cf703 6260 
postgresql-9.5-prioritize_1.0.4-1.2_amd64.deb
Files:
 6b6b58adf36943ade9391079e232e892 2098 database optional 
postgresql-prioritize_1.0.4-1.2.dsc
 40ec1e13a3a295a952d668389ac25979 2848 database optional 
postgresql-prioritize_1.0.4-1.2.debian.tar.xz
 4be65d50d0c74315d287ca812b3b2806 2286 debug extra 
postgresql-9.5-prioritize-dbgsym_1.0.4-1.2_amd64.deb
 432ac33dbe425bc2bfc34b0e757d0c33 6260 database optional 
postgresql-9.5-prioritize_1.0.4-1.2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWsJYuAAoJEExaa6sS0qeuJ/UP/1UcS4fZd+JttN1la7cW4wJe
pOzXpL/d3J/LTht4A4FV60e23aX1uaWHkGujjogDbEB165AoEq7K6sUMnlRsL3VB
1AmmxXUEGZFFiTjzgnBlqyW6lHnBqRzPKmRqlK1nbJHKwiCM/BPjDd4nigaCFfBd
cwVbGhvIAlQs4CkbAH10w4IpZCYYmFBWwhXUj+/dy3UX+pmNcC9UjPMF33Z/5/2+
mXcO77tAO/JxyWeG0TIiDtrb/sWQxRNaCs6e//0VRLKUsJdttuBz8zyzL3AOg8JK
pgXJOecWIkCPO7yN4D8D0jzY/0Ulzb2mHX6pJTRuZK88WALTvjOZooewJ+xq/oHg
VoRDhBIJuUcenIO+FLnb3uIQw3PQFMKT13sf0L92aS3DW3FjGf+gxAz8/t3r/Stx
c5+YZoGi10LV4JZ6q9uqN8SeVSvMEGi6d5D5lk42iPqNukLhDSvepIief1bN3ZDO
vjjc+r3FIhuToWowFRkN2UT+oZJnv2TuBOiWLH93ue0sT+X0Jr4crukgzdntJtZd
K/ZaHMiWGRJhNYCSpiU/xs3sYR5+lb6eDo6X6OXF5flZsHJmXvpKDXflF8BrLJOH
NcONRti26gjcf0cBRivZsfr3v+mVwDx2WZL8IxxQ3AEmAE28prNeKnuPHVJ6rdUr
MkkyD8AzNjViXejEJLb2
=1DhE
-END PGP 

Bug#810636: marked as done (pgpool2: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 13:01:13 +
with message-id 
and subject line Bug#810636: fixed in pgpool2 3.4.3-1
has caused the Debian Bug report #810636,
regarding pgpool2: FTBFS: Error: debian/control needs updating from 
debian/control.in. Run 'pg_buildext updatecontrol'.
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.)


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

pgpool2 fails to build from source in unstable/amd64:

  [..]

  +Package: postgresql-9.5-pgpool2
   Architecture: any
  -Depends: postgresql-9.4, ${misc:Depends}, ${shlibs:Depends}, libpgpool0 (= 
${binary:Version})
  +Depends: postgresql-9.5, ${misc:Depends}, ${shlibs:Depends}, libpgpool0 (= 
${binary:Version})
   Description: connection pool server and replication proxy for PostgreSQL - 
modules
pgpool-II is a middleware that works between PostgreSQL servers and a
PostgreSQL database client.  This package contains support modules for
  - the PostgreSQL 9.4 server:
  + the PostgreSQL 9.5 server:
.
 * pgpool_adm
 * pgpool_recovery (PostgreSQL 9.1 and above)
  Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
updatecontrol'.
  If you are seeing this message in a buildd log, a sourceful upload is 
required.
  /usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target 
'debian/control' failed
  make: *** [debian/control] Error 1

  [..]

The full build log is attached.


Regards,

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


pgpool2.3.3.4-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: pgpool2
Source-Version: 3.4.3-1

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

Debian distribution maintenance software
pp.
Marco Nenciarini  (supplier of updated pgpool2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Feb 2016 22:56:38 +0100
Source: pgpool2
Binary: pgpool2 pgpool2-dbg libpgpool0 libpgpool-dev postgresql-9.5-pgpool2
Architecture: source amd64
Version: 3.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 

Changed-By: Marco Nenciarini 
Description:
 libpgpool-dev - pgpool control protocol library - headers
 libpgpool0 - pgpool control protocol library
 pgpool2- connection pool server and replication proxy for PostgreSQL
 pgpool2-dbg - debugging symbols for pgpool2 and libpgpool0
 postgresql-9.5-pgpool2 - connection pool server and replication proxy for 
PostgreSQL - mod
Closes: 810636
Changes:
 pgpool2 (3.4.3-1) unstable; urgency=medium
 .
   [ Marco Nenciarini ]
   * Imported Upstream version 3.4.3
   * Adapt packaging to 3.4 source layout
   * Disable parser and timestamp tests because they are broken
   * Bump Standards-Version to 3.9.6 (no changes required)
   * Remove old lintian overrides and svn-buildpackage config
   * Install the new pgpool.8 manpage
   * Add pgpool2-dbg debug package
   * Add myself to Uploaders
   * Remove support for pgpool extensions with Postgres versions less than 9.3
   * Fix jdbc tests when systemd is active
   * Build for PostgreSQL 9.5 (Closes: #810636)
 .
   [ Christoph Berg ]
   * Explicitly bind to 127.0.0.1 when running tests
Checksums-Sha1:
 85e211bc64e9cab303dbb09df321bced03632c28 2368 pgpool2_3.4.3-1.dsc
 187fb7b9060f4bf656774ca45cc7624fea6e16f6 2152319 pgpool2_3.4.3.orig.tar.gz
 8d6e3f98a18b6de331e9dbf6c2136ba3092d7f6e 11628 pgpool2_3.4.3-1.debian.tar.xz
 4dc7ed005393537f44c5adfd041e2798f18fae01 25044 libpgpool-dev_3.4.3-1_amd64.deb
 

Bug#810635: marked as done (pgespresso: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 13:01:09 +
with message-id 
and subject line Bug#810635: fixed in pgespresso 1.0-3
has caused the Debian Bug report #810635,
regarding pgespresso: FTBFS: Error: debian/control needs updating from 
debian/control.in. Run 'pg_buildext updatecontrol'.
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.)


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

Dear Maintainer,

pgespresso fails to build from source in unstable/amd64:

  [..]

   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: source package pgespresso
  dpkg-buildpackage: source version 1.0-2
  dpkg-buildpackage: source distribution unstable
  dpkg-buildpackage: source changed by Marco Nenciarini 
   dpkg-source --before-build pgespresso-1.0
  dpkg-buildpackage: host architecture amd64
   fakeroot debian/rules clean
  pg_buildext checkcontrol
  --- debian/control2014-08-08 14:22:01.0 +0100
  +++ debian/control.KUNjYT 2016-01-10 20:11:11.985261514 +
  @@ -9,9 +9,9 @@
   Homepage: https://github.com/2ndquadrant-it/pgespresso
   XS-Testsuite: autopkgtest
   
  -Package: postgresql-9.4-pgespresso
  +Package: postgresql-9.5-pgespresso
   Architecture: any
  -Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.4
  +Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.5
   Enhances: barman
   Description: extension for Barman, Backup and Recovery Manager for PostgreSQL
pgespresso is an extension that enhances Barman, Backup and Recovery
  Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
updatecontrol'.
  If you are seeing this message in a buildd log, a sourceful upload is 
required.
  /usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target 
'debian/control' failed
  make: *** [debian/control] Error 1

  [..]

The full build log is attached.


Regards,

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


pgespresso.1.0-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: pgespresso
Source-Version: 1.0-3

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

Debian distribution maintenance software
pp.
Marco Nenciarini  (supplier of updated pgespresso 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: Wed, 03 Feb 2016 12:03:15 +0100
Source: pgespresso
Binary: postgresql-9.5-pgespresso
Architecture: source amd64
Version: 1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Marco Nenciarini 
Changed-By: Marco Nenciarini 
Description:
 postgresql-9.5-pgespresso - extension for Barman, Backup and Recovery Manager 
for PostgreSQL
Closes: 810635
Changes:
 pgespresso (1.0-3) unstable; urgency=medium
 .
   * Add compatibility with PostgreSQL 9.5 (Closes: #810635)
   * Use https for anonymous git repository access in debian/control fields
   * Bump Standards-Version to 3.9.7.0 in debian/control. No changes required.
Checksums-Sha1:
 b094b3f7e88a7e3fb806e5051316b248bcc6ee41 1957 pgespresso_1.0-3.dsc
 069c1bf9ab476f8c353a0521cf42baa796543619 3708 pgespresso_1.0-3.debian.tar.xz
 946b7efdf03d27a1e96bd025383969a0a655aa6f 11234 
postgresql-9.5-pgespresso-dbgsym_1.0-3_amd64.deb
 b92b68794ada367d19dc3722ab3b0b0a3d846680 6026 
postgresql-9.5-pgespresso_1.0-3_amd64.deb
Checksums-Sha256:
 92b5da28d6e11b9be095574ff505e1c409a2a4ef141ef360a990662dac47cbaf 1957 
pgespresso_1.0-3.dsc
 c919f9c1aa32fc4bc41b32f3d7e584997ceed9d8330b11f23334a569b24808d8 3708 
pgespresso_1.0-3.debian.tar.xz
 a17eec1d35783585b1ea6b2c98e14d17fdd98981a0d18cfe9e5e2f124d4e88ba 11234 

Bug#808821: asymptote: failing to build on mips

[Julian Gilbey]

On Fri, Jan 29, 2016 at 11:22:33PM +0900, Norbert Preining wrote:
> Hi Julian,
> 
> On Fri, 29 Jan 2016, Julian Gilbey wrote:
> > I've reported it upstream; John Bowman responded to the last report
> > very quickly indeed (thanks, John!), so I suggest we wait a couple of
> > days before disabling mips.
> 
> Ok, sure enough.
> 
> > Alternatively, one could argue that it is just this one bug - it is
> > not the whole package which is affected - and exclude this one
> 
> I guess all the 3d related files will fail, which is rather 
> disappointing.
> 
> For now let us wait for John's answer. Did you open a new bug
> or reopen the old one?

It turns out that it is a compiler bug, or at least it is as far as we
can tell: the code works fine with -O0 but bombs with -O1.  See
https://sourceforge.net/p/asymptote/bugs/205/ for the full discussion.
I guess I should report this upstream - I guess against g++?  But
finding a minimal example will be hard.

Anyway, a workaround has been applied, and the code now appears to
compile fine under MIPS, so please do upgrade to version 2.37.  This,
incidentally, includes the elisp documentation bug patch, so that will
no longer be needed in the Debian package, and nor will the recently
applied patch from the git repo.

Best wishes,

   Julian

Bug#809298: marked as done (cargo: FTBFS: "configure: error: need curl")

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 13:00:26 +
with message-id 
and subject line Bug#809298: fixed in cargo 0.6.0-2
has caused the Debian Bug report #809298,
regarding cargo: FTBFS: "configure: error: need curl"
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.)


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

Dear Maintainer,

cargo fails to build from source in unstable/amd64 if wget is installed due to 
"wget | curl" build-depends. You just need to either change the B-D to specify 
curl explicitly in addition to wget or alternatively just specify curl.

  [..]

  # Configure to build cargo using the just-built stage0
  ./configure \
--prefix=/usr \
--disable-debug \
--enable-optimize \
--local-rust-root=/usr \

--local-cargo=/home/lamby/temp/cdt.20151229035953.Z4kmdk8OPp/cargo-0.6.0/cargo-stage0
  configure: looking for configure programs
  configure: found cmp
  configure: found mkdir
  configure: found printf
  configure: found cut
  configure: found head
  configure: found grep
  configure: found xargs
  configure: found cp
  configure: found find
  configure: found uname
  configure: found date
  configure: found tr
  configure: found sed
  configure: found cmake
  configure: error: need curl
  debian/rules:29: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151229035953.Z4kmdk8OPp/cargo-0.6.0'
  debian/rules:22: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


cargo.0.6.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: cargo
Source-Version: 0.6.0-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Feb 2016 14:04:39 +0100
Source: cargo
Binary: cargo cargo-doc
Architecture: source amd64 all
Version: 0.6.0-2
Distribution: unstable
Urgency: medium
Maintainer: Rust Maintainers 
Changed-By: Sylvestre Ledru 
Description:
 cargo  - Rust package manager
 cargo-doc  - Rust package manager, documentation
Closes: 809298
Changes:
 cargo (0.6.0-2) unstable; urgency=medium
 .
   * Introduce a cargo-doc package
   * Fails to build when wget is installed. Force curl
 (Closes: #809298)
   * Add the missing VCS- fields
   * Add myself among the uploaders
 .
   [ Angus Lee ]
   * Use local jquery.js
   * Correct cargo-doc.doc-base paths to HTML docs
Checksums-Sha1:
 abe981130e0595788256a16b9fab4d4a0863545d 2413 cargo_0.6.0-2.dsc
 14a8ab3a927b1bc8faa3a267013544ab12c7a72d 25036 cargo_0.6.0-2.debian.tar.xz
 29c9f249f0caaac78c6e8207fccb7719732f3dff 1653532 cargo-dbgsym_0.6.0-2_amd64.deb
 9e1b98d2b993c8c51fbfa649050e1d33351e9b37 997430 cargo-doc_0.6.0-2_all.deb
 ddb9113104f4283d956bb845d72033662f1d9e82 1601408 cargo_0.6.0-2_amd64.deb
Checksums-Sha256:
 6a95b7545566ae63c4aeddd82c591e7a5dda342b651138c888a993f11d8ea0bc 2413 
cargo_0.6.0-2.dsc
 17a21a27dd7baa50b7aba20e343d8bcf575362d3b5e55a0f61fa657daad248d4 25036 
cargo_0.6.0-2.debian.tar.xz
 4c8fe832cd82f7688b570891d679c3ad318cd93495f83cf6b32c0f45f1ae2972 1653532 
cargo-dbgsym_0.6.0-2_amd64.deb
 b3cd5f988a48919ff2705370659536591d5efb41bee7424a63f5e79596f196a5 997430 
cargo-doc_0.6.0-2_all.deb
 

Bug#811135: marked as done (FTBFS: debian/control needs updating from debian/control.in)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 13:01:11 +
with message-id 
and subject line Bug#811135: fixed in pgextwlist 1.4-1
has caused the Debian Bug report #811135,
regarding FTBFS: debian/control needs updating from debian/control.in
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.)


-- 
811135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pgextwlist
Version: 1.3-3
Severity: serious

pgextwlist fails to build in unstable:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> pg_buildext checkcontrol
> --- debian/control2014-07-27 09:13:41.0 +
> +++ debian/control.Mj7Bgx 2016-01-15 23:46:25.581097091 +
> @@ -10,10 +10,10 @@
>  Vcs-Browser: https://github.com/dimitri/pgextwlist
>  XS-Testsuite: autopkgtest
>  
> -Package: postgresql-9.4-pgextwlist
> +Package: postgresql-9.5-pgextwlist
>  Section: libs
>  Architecture: any
> -Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.4
> +Depends: ${shlibs:Depends}, ${misc:Depends}, postgresql-9.5
>  Description: PostgreSQL Extension Whitelisting
>   This extension implements extension whitelisting, and will actively prevent
>   users from installing extensions not in the provided list. Also, this
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext 
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is 
> required.
> /usr/share/postgresql-common/pgxs_debian_control.mk:9: recipe for target 
> 'debian/control' failed

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: pgextwlist
Source-Version: 1.4-1

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

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

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

Debian distribution maintenance software
pp.
Christoph Berg  (supplier of updated pgextwlist 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 02 Feb 2016 12:56:49 +0100
Source: pgextwlist
Binary: postgresql-9.5-pgextwlist
Architecture: source amd64
Version: 1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers 

Changed-By: Christoph Berg 
Description:
 postgresql-9.5-pgextwlist - PostgreSQL Extension Whitelisting
Closes: 811135
Changes:
 pgextwlist (1.4-1) unstable; urgency=medium
 .
   * New upstream version with 9.5 support. (Closes: #811135)
Checksums-Sha1:
 097fb38f2912c47f2cd3912bda9d52a785e7ec82 2016 pgextwlist_1.4-1.dsc
 4c980de30253a58c00caa5fbb14f1fdbe5016bb6 15549 pgextwlist_1.4.orig.tar.gz
 413ee4e80893b1418189254c07041480dfff0824 2808 pgextwlist_1.4-1.debian.tar.xz
 c4619ec0ddcb3a2b8e49b2c35995d55fbbc479bb 3452 
postgresql-9.5-pgextwlist-dbgsym_1.4-1_amd64.deb
 cdfc39d8a23e4d0e8674c18f92bb25f85fb9850d 11526 
postgresql-9.5-pgextwlist_1.4-1_amd64.deb
Checksums-Sha256:
 02aa0aaa29070ae97b5ed5c617f760db3a273db345bc943f384ce3ef5438c93c 2016 
pgextwlist_1.4-1.dsc
 bd11fef08873d82f950b0b8df200e49fad8786bf25c18ad0b9cafcbc178856ed 15549 
pgextwlist_1.4.orig.tar.gz
 68a23995a5dc10a2d674e4993e6ec7193fed44f97b356565d8edb87a42d16dbc 2808 
pgextwlist_1.4-1.debian.tar.xz
 c08fc6d60937d17207d5e6d8d9bcd61e040d70db23bd90db0f11d0b2a430fa6c 3452 
postgresql-9.5-pgextwlist-dbgsym_1.4-1_amd64.deb
 05d8243c91a49ef16924ee91cfb9d8243dc9597e3e956521da645e0c6ebbb341 11526 
postgresql-9.5-pgextwlist_1.4-1_amd64.deb
Files:
 dcccdf2e9e253c9aab8d87101afa4597 2016 database extra pgextwlist_1.4-1.dsc
 7fabda8400c5901e5a1a54e299d33dee 15549 database extra 
pgextwlist_1.4.orig.tar.gz
 9d83bb2df35953ea72fb43d5c120f42e 2808 database extra 
pgextwlist_1.4-1.debian.tar.xz
 6393961618746d3c782c1447f62ba882 3452 debug extra 
postgresql-9.5-pgextwlist-dbgsym_1.4-1_amd64.deb
 ffcd1f40b7b08b11b414b6f9476eacc6 11526 libs extra 
postgresql-9.5-pgextwlist_1.4-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

Bug#813406: [Pkg-samba-maint] Bug#813406: ctdb, raw sockets and CVE-2015-8543

[Adi Kriegisch]

Hi!

> There are two set of patches:
> - yours that basically keep the same behavior as pre-CVE-2015-8543 (proto=0)
I just desperately tried to get my cluster going again... ;-)

> - Amitay's that restore the intented behavior (proto=255)
[...] 
> I think I'll got for Amitay's patch which probably fixes a lot of
> weird behaviors I've seen pre-CVE-2015-8543 (i.e TCP connections not
> reset, Ip not properly relocated).
This is -- of course -- the way better approach!

> I plan to fix this for wheezy and jessie. stretch will come with next
> upstream release.
> 
> Givent the importance of the bug, I think it can go thru -security.
I think so too -- especially as it is some kind of regression.

Thank you very much for taking care of this!

-- Adi


signature.asc
Description: Digital signature

Bug#813643: numexpr: FTBFS: TypeError: 'float' object cannot be interpreted as an index

[Chris Lamb]

Source: numexpr
Version: 2.4.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

numexpr fails to build from source in unstable/amd64:

  [..]
  
  ==
  ERROR: test_reductions (__main__.test_numexpr)
  --
  Traceback (most recent call last):
File "numexpr/tests/test_numexpr.py", line 95, in test_reductions
  x = zeros(1e5) + .01  # checks issue #41
  TypeError: 'float' object cannot be interpreted as an index
  
  ==
  ERROR: test_reductions (__main__.test_numexpr2)
  --
  Traceback (most recent call last):
File "numexpr/tests/test_numexpr.py", line 95, in test_reductions
  x = zeros(1e5) + .01  # checks issue #41
  TypeError: 'float' object cannot be interpreted as an index
  
  --
  Ran 5434 tests in 5.111s
  
  FAILED (errors=2)
  debian/rules:59: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160203230943.1VeeSgqY1a/numexpr-2.4.3'
  debian/rules:18: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


numexpr.2.4.3-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#813641: multcomp: FTBFS: Error : package 'MASS' required by 'TH.data' could not be found

[Chris Lamb]

Source: multcomp
Version: 1.4-2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

multcomp fails to build from source in unstable/amd64:

  [..]

  * installing *source* package 'multcomp' ...
  ** package 'multcomp' successfully unpacked and MD5 sums checked
  ** R
  ** data
  *** moving datasets to lazyload DB
  ** demo
  ** inst
  ** preparing package for lazy loading
  Error : package 'MASS' required by 'TH.data' could not be found
  ERROR: lazy loading failed for package 'multcomp'
  * removing 
'/home/lamby/temp/cdt.20160203230629.amdKvAuzFF/multcomp-1.4-2/debian/r-cran-multcomp/usr/lib/R/site-library/multcomp'
  /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
  make: *** [R_any_arch] Error 1

  [..]

The full build log is attached.


Regards,

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


multcomp.1.4-2-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#802172: marked as done (ismrmrd: FTBFS on several arches)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 21:55:52 +
with message-id 
and subject line Bug#802172: fixed in ismrmrd 1.3.2-2
has caused the Debian Bug report #802172,
regarding ismrmrd: FTBFS on several arches
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.)


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

Your package failed to build on several architectures. Here's an excerpt from
the armel build:

*** 546 failures detected in test suite "ISMRMRD Unit Tests"
make[4]: *** [tests/CMakeFiles/check] Error 201

All logs available at:

https://buildd.debian.org/status/logs.php?pkg=ismrmrd=1.3.1-1

Emilio
--- End Message ---
--- Begin Message ---
Source: ismrmrd
Source-Version: 1.3.2-2

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

Debian distribution maintenance software
pp.
Ghislain Antony Vaillant  (supplier of updated ismrmrd 
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: Wed, 03 Feb 2016 19:32:00 +
Source: ismrmrd
Binary: libismrmrd1.3 libismrmrd-dev libismrmrd-doc ismrmrd-tools ismrmrd-schema
Architecture: source
Version: 1.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Ghislain Antony Vaillant 
Description:
 ismrmrd-schema - ISMRM Raw Data format (ISMRMRD) - XML schema
 ismrmrd-tools - ISMRM Raw Data format (ISMRMRD) - binaries
 libismrmrd-dev - ISMRM Raw Data format (ISMRMRD) - development files
 libismrmrd-doc - ISMRM Raw Data format (ISMRMRD) - documentation
 libismrmrd1.3 - ISMRM Raw Data format (ISMRMRD) - shared library
Closes: 802172
Changes:
 ismrmrd (1.3.2-2) unstable; urgency=medium
 .
   * d/control: use secure VCS-Git URI.
   * Add patch fixing FTBFS in testsuite.
 File: Use-explicit-64-bit-shifts-in-testsuite.patch.
 Thanks to Emilio Pozuelo Monfort (Closes: #802172)
   * Provide examples in doc package.
   * d/control: cme fix, wrap and sort.
   * Fix usage of embedded jquery.
Checksums-Sha1:
 2ea6da99e1cca390811fade5b061b54a12501661 2298 ismrmrd_1.3.2-2.dsc
 66d8ca538340ad7a6b405174fb2434ccc3ebcbbd 5184 ismrmrd_1.3.2-2.debian.tar.xz
Checksums-Sha256:
 f3d04f7030f21041819deaadecf933a708394529c57fdd64cc48467b37ad5e77 2298 
ismrmrd_1.3.2-2.dsc
 f63f61a1f1b8d1de2f6f1252e68e73b78963d9c9c7d12f1d234d478963b6b6b9 5184 
ismrmrd_1.3.2-2.debian.tar.xz
Files:
 f1ea9c0df7bb17c02cf8c55a91d60037 2298 science optional ismrmrd_1.3.2-2.dsc
 47b0ffb56ce1a56c78f6f86b5d45f02e 5184 science optional 
ismrmrd_1.3.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWslpaAAoJEEsEP825REVAxvUP/RPG9HEMng57fKqPCnbhPfc6
hBUa5Id18fjtAvA+jHGRlEVSwxYPNxJZLYTa+JxWvsYn6wg5TbnJcNlCJLdLue4d
tsEolfLvB0lliyVvNpk3AgTjGpgWXJbyY3M6mqLY7SK4xhOos5pQjOw2VhMCKW7f
1GgkfmoX5XNkV6ubbE/cW60Zr+eIIYnJXjmFGRNaDmQCjR6H40vZUCCU2Izt+bM1
wRXw7J0p2xX20a2fYqTD9HQRHQI3tAbczB1PSV8zGCRvkTLtqqbvTFetN8Oonp85
bm5BG9VacTCe7mNt+85diU3hnhS9qnScohd/iEm1mSfZQxkk4BwPs4aa7idBwN8D
G+MxPyjYa+bqfLgl9YtJqHbKMRZ89K/wqMADVCxMD2XPAW5F5Ap2eEbgZT/HAmtu
FQ7yHLwAKFzguBJYCZamwblFrt1vWFhMn+Ln8WQbVBWySbxrDiJXtIZEucmzzoQD
rHP5ttg+k0f+pxXqUS0s1RnW3X9+VLMui56qG89fdXCS5VcumB6VrOs6JuEHIMEV
b1br+mMXmOamp3j7qSHp7d1suEWT9DGEKE40EVZzf5l1EJvP2YXDXhh6PIM26diA
0i3KfeThrUNnhS50W6Ca4Xok15djl+R4DZdUSch4aQ3NmQbbKIztVnSCN3d2yLH+
caSA/x+yTvr9LRT5YG5y
=ag+L
-END PGP SIGNATURE End Message ---

Bug#813406: [Pkg-samba-maint] Bug#813406: ctdb, raw sockets and CVE-2015-8543

[Mathieu Parent]

2016-02-01 17:29 GMT+01:00 Adi Kriegisch :
> Package: ctdb
> Severity: grave
> Tags: patch,upstream
>
> Hi!
>
> The kernel upgrade for CVE-2015-8543 showed a bug in CTDB that leads to a
> broken cluster:
>   | s = socket(AF_INET, SOCK_RAW, htons(IPPROTO_RAW));
> htons(IPPROTO_RAW) leads to 0xff00 which causes "-1 EINVAL (Invalid
> argument)" because of CVE-2015-8543.
> The fix for the issue is quite simple: remove IPPROTO_RAW; to make the fix
> more consistent with what was used before, use IPPROTO_IP (which is 0).
>
> Error messages related to this bug are:
>   | We are still serving a public IP 'x.x.x.x' that we should not be serving. 
> Removing it
>   | common/system_common.c:89 failed to open raw socket (Invalid argument)
>   | Could not find which interface the ip address is hosted on. can not 
> release it
> and
>   | common/system_linux.c:344 failed to open raw socket (Invalid argument)
> As a result, IP addresses cannot be released and multiple nodes in the
> cluster serve the same address, which obviously does not work.

Thank you so much for finding this bug! I was wondering why my
clusters were crazy, blaming the network itself.

> Upstream bug: https://bugzilla.samba.org/show_bug.cgi?id=11705 and mailing
> list conversation: 
> https://lists.samba.org/archive/samba/2016-January/197389.html

There are two set of patches:
- yours that basically keep the same behavior as pre-CVE-2015-8543 (proto=0)
- Amitay's that restore the intented behavior (proto=255)

Also you patch only fixes 2 functions.

Amitay's patch also fixes references to ETHERTYPE_ARP (0x0806) and
ETH_P_ALL (0x0003)

I think I'll got for Amitay's patch which probably fixes a lot of
weird behaviors I've seen pre-CVE-2015-8543 (i.e TCP connections not
reset, Ip not properly relocated).

I plan to fix this for wheezy and jessie. stretch will come with next
upstream release.

Givent the importance of the bug, I think it can go thru -security.

Regards
-- 
Mathieu

Bug#813642: netty-3.9: FTBFS: mv: cannot stat 'debian/libnetty-3.9-java/usr/share/java/netty.jar': No such file or directory

[Chris Lamb]

Source: netty-3.9
Version: 3.9.0.Final-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,

netty-3.9 fails to build from source in unstable/amd64:

  [..]

  Install jar for netty into /usr/share/java
  [INFO] 

  [INFO] BUILD SUCCESS
  [INFO] 

  [INFO] Total time: 1.300 s
  [INFO] Finished at: 2016-02-03T23:09:38+01:00
  [INFO] Final Memory: 11M/298M
  [INFO] 

mh_resolve_dependencies --non-interactive --offline -plibnetty-3.9-java 
--base-directory=/home/lamby/temp/cdt.20160203230716.t87RFxqiA4/netty-3.9-3.9.0.Final
 --non-explore
  Analysing pom.xml...
  mv debian/libnetty-3.9-java/usr/share/java/netty.jar \
 debian/libnetty-3.9-java/usr/share/java/netty-3.9.0.Final.jar
  mv: cannot stat 'debian/libnetty-3.9-java/usr/share/java/netty.jar': No such 
file or directory
  debian/rules:7: recipe for target 'override_dh_auto_install' failed
  make[1]: *** [override_dh_auto_install] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160203230716.t87RFxqiA4/netty-3.9-3.9.0.Final'
  debian/rules:4: 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
   `-


netty-3.9.3.9.0.Final-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#813565: 358.16 is far more recent than the 355.11 witch is 7 month old. SO why was it uploaded to experimental?

[Eric Valette]

looking at nvidia driver page I really wonder why someone decided to 
upload this old, not ABI 20 compatible driver to experimental!


-- eric

Bug#813633: botan1.10: FTBFS with nocheck in DEB_BUILD_OPTIONS

[Thorsten Glaser]

Source: botan1.10
Version: 1.10.12-1
Severity: serious
Justification: Policy §4.9.1
X-Debbugs-Cc: debian-...@lists.debian.org

Your package FTBFS with nocheck in DEB_BUILD_OPTIONS:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
dh_auto_test -- check
LD_LIBRARY_PATH="/usr/lib/libeatmydata:/<>" ./check --validate
/bin/sh: 1: ./check: not found
debian/rules:34: recipe for target 'override_dh_auto_test' failed

Bug#798023: cssutils: diff for NMU version 1.0-4.1

[gregor herrmann]

Control: tags 798023 + pending

Dear maintainer,

Chris Knadle has prepared an NMU for cssutils (versioned as 1.0-4.1)
and I've uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Cranberries: Dreams
diff -Nru cssutils-1.0/debian/changelog cssutils-1.0/debian/changelog
--- cssutils-1.0/debian/changelog	2015-11-30 00:31:12.0 +0100
+++ cssutils-1.0/debian/changelog	2016-02-03 22:40:28.0 +0100
@@ -1,3 +1,12 @@
+cssutils (1.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches:
+- Add 02_fix_octal_escape.patch to fix FTBFS bug with Python 3.5
+  (Closes: #798023).
+
+ -- Christopher Knadle   Thu, 21 Jan 2016 05:21:33 -0500
+
 cssutils (1.0-4) unstable; urgency=high
 
   * Upload to unstable (Closes: #802063).
diff -Nru cssutils-1.0/debian/patches/02_fix_octal_escape.patch cssutils-1.0/debian/patches/02_fix_octal_escape.patch
--- cssutils-1.0/debian/patches/02_fix_octal_escape.patch	1970-01-01 01:00:00.0 +0100
+++ cssutils-1.0/debian/patches/02_fix_octal_escape.patch	2016-02-03 22:43:41.0 +0100
@@ -0,0 +1,18 @@
+Description: Fix octal escape on Python 3.5
+Origin: https://bitbucket.org/cthedot/cssutils/commits/866a29f7e03447199ba22fb114d42a7aab027db9/raw/
+Author: Daniel 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798023
+Bug-Upstream: https://bugs.python.org/issue22362
+Last-Updated: 2016-01-21
+
+--- a/src/cssutils/profiles.py
 b/src/cssutils/profiles.py
+@@ -102,7 +102,7 @@
+ 'nmstart': r'[_a-z]|{nonascii}|{escape}',
+ 'nonascii': r'[^\0-\177]',
+ 'unicode': r'\\[0-9a-f]{1,6}(\r\n|[ \n\r\t\f])?',
+-'escape': r'{unicode}|\\[ -~\200-\777]',
++'escape': r'{unicode}|\\[ -~\u0080-\u01ff]',
+ #   'escape': r'{unicode}|\\[ -~\200-\417]',
+ 'int': r'[-]?\d+',
+ 'nmchar': r'[\w-]|{nonascii}|{escape}',
diff -Nru cssutils-1.0/debian/patches/series cssutils-1.0/debian/patches/series
--- cssutils-1.0/debian/patches/series	2015-11-29 23:20:19.0 +0100
+++ cssutils-1.0/debian/patches/series	2016-02-03 22:40:28.0 +0100
@@ -1 +1,2 @@
 01_setup_fix.patch
+02_fix_octal_escape.patch


signature.asc
Description: Digital Signature

Processed: cssutils: diff for NMU version 1.0-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 798023 + pending
Bug #798023 [src:cssutils] cssutils: FTBFS with Python 3.5
Added tag(s) pending.

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

Processed: Block mopidy-youtube from transitioning to testing

[Debian Bug Tracking System]

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

> severity 795007 serious
Bug #795007 [mopidy-youtube] [mopidy-youtube] needs python-pafy from stable 
(not in sid...)
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#810771: marked as done (composer: FTBFS: ComposerSchemaTest::testRequiredProperties Failed asserting that two arrays are equal.)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 21:50:43 +
with message-id 
and subject line Bug#810771: fixed in composer 1.0.0~alpha11-2
has caused the Debian Bug report #810771,
regarding composer: FTBFS: ComposerSchemaTest::testRequiredProperties   Failed 
asserting that two arrays are equal.
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.)


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

composer fails to build from source in unstable/amd64:

  [..]

 debian/rules override_dh_auto_build
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160112041435.Yp3KRjMDp4/composer-1.0.0~alpha11'
  phpab \
--output src/Composer/autoload.php \
--template debian/autoload.php.tpl \
src/Composer
  phpab %development% - Copyright (C) 2009 - 2016 by Arne Blankerts
  
  Scanning directory src/Composer
  
  Autoload file src/Composer/autoload.php generated.
  
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160112041435.Yp3KRjMDp4/composer-1.0.0~alpha11'
 debian/rules override_dh_auto_test
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160112041435.Yp3KRjMDp4/composer-1.0.0~alpha11'
  phpunit --include-path src
  PHPUnit 5.1.3 by Sebastian Bergmann and contributors.
  
  ...  63 / 847 (  
7%)
  ... 126 / 847 ( 
14%)
  ... 189 / 847 ( 
22%)
  ... 252 / 847 ( 
29%)
  ... 315 / 847 ( 
37%)
  FF. 378 / 847 ( 
44%)
  ...S... 441 / 847 ( 
52%)
  ... 504 / 847 ( 
59%)
  ... 567 / 847 ( 
66%)
  ... 630 / 847 ( 
74%)
  ... 693 / 847 ( 
81%)
  ... 756 / 847 ( 
89%)
  ... 819 / 847 ( 
96%)
  847 / 847 
(100%)
  
  Time: 7.45 seconds, Memory: 40.00Mb
  
  There were 2 failures:
  
  1) Composer\Test\Json\ComposerSchemaTest::testRequiredProperties
  Failed asserting that two arrays are equal.
  --- Expected
  +++ Actual
  @@ @@
   Array (
   0 => Array (
   'property' => 'name'
   'message' => 'The property name is required'
  +'constraint' => 'required'
   )
   1 => Array (
   'property' => 'description'
   'message' => 'The property description is required'
  +'constraint' => 'required'
   )
   )
  
  
/home/lamby/temp/cdt.20160112041435.Yp3KRjMDp4/composer-1.0.0~alpha11/tests/Composer/Test/Json/ComposerSchemaTest.php:28
  
  2) Composer\Test\Json\ComposerSchemaTest::testMinimumStabilityValues
  empty string
  Failed asserting that two arrays are equal.
  --- Expected
  +++ Actual
  @@ @@
   Array (
   0 => Array (
   'property' => 'minimum-stability'
   'message' => 'Does not match the regex patt...table$'
  +'constraint' => 'pattern'
  +'pattern' => '^dev|alpha|beta|rc|RC|stable$'
   )
   )
  
  
/home/lamby/temp/cdt.20160112041435.Yp3KRjMDp4/composer-1.0.0~alpha11/tests/Composer/Test/Json/ComposerSchemaTest.php:49
  
  FAILURES!
  Tests: 847, Assertions: 1692, Failures: 2, Skipped: 1.
  debian/rules:17: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160112041435.Yp3KRjMDp4/composer-1.0.0~alpha11'
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


composer.1.0.0~alpha11-1.unstable.amd64.log.txt.gz
Description: Binary 

Bug#813597: python-openssl: exception when importing OpenSSL

[Daniel Monteiro Basso]

Package: python-openssl
Version: 0.15.1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Just dist-upgrade'd my system. After that, anything that depends on pyopenssl
stopped working, including pip.

In [1]: import cryptography

In [2]: cryptography.__version__
Out[2]: '1.2.1'

In [3]: import OpenSSL
---
AttributeErrorTraceback (most recent call last)
 in ()
> 1 import OpenSSL

/usr/lib/python2.7/dist-packages/OpenSSL/__init__.py in ()
  6 """
  7
> 8 from OpenSSL import rand, crypto, SSL
  9 from OpenSSL.version import __version__
 10

/usr/lib/python2.7/dist-packages/OpenSSL/rand.py in ()
  9 from six import integer_types as _integer_types
 10
---> 11 from OpenSSL._util import (
 12 ffi as _ffi,
 13 lib as _lib,

/usr/lib/python2.7/dist-packages/OpenSSL/_util.py in ()
  4 from six import PY3, binary_type, text_type
  5
> 6 from cryptography.hazmat.bindings.openssl.binding import Binding
  7 binding = Binding()
  8 ffi = binding.ffi

/usr/lib/python2.7/dist-
packages/cryptography/hazmat/bindings/openssl/binding.py in ()
 66 @ffi_callback("int (*)(unsigned char *, int)",
 67   name="Cryptography_rand_bytes",
---> 68   error=-1)
 69 def _osrandom_rand_bytes(buf, size):
 70 signed = ffi.cast("char *", buf)

/usr/lib/python2.7/dist-
packages/cryptography/hazmat/bindings/openssl/binding.py in wrapper(func)
 55 # def_extern() returns a decorator that sets the internal
 56 # function pointer and returns the original function
unmodified.
---> 57 ffi.def_extern(name=name, **kwargs)(func)
 58 callback = getattr(lib, name)
 59 else:

AttributeError: 'CompiledFFI' object has no attribute 'def_extern'



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

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

Versions of packages python-openssl depends on:
ii  python-cryptography  1.2.1-1
ii  python-six   1.10.0-1
pn  python:any   

python-openssl recommends no packages.

Versions of packages python-openssl suggests:
pn  python-openssl-dbg  
pn  python-openssl-doc  

-- no debconf information

Processed: Re: Bug#813597: python-openssl: exception when importing OpenSSL

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python-cryptography
Bug #813597 [python-openssl] python-openssl: exception when importing OpenSSL
Bug reassigned from package 'python-openssl' to 'python-cryptography'.
No longer marked as found in versions pyopenssl/0.15.1-2.
Ignoring request to alter fixed versions of bug #813597 to the same values 
previously set

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

Bug#813597: python-openssl: exception when importing OpenSSL

[Sandro Tosi]

control: reassign -1 python-cryptography

the crash in in cryptography, so reassigning accordingly

On Wed, Feb 3, 2016 at 2:54 PM, Daniel Monteiro Basso
 wrote:
> Package: python-openssl
> Version: 0.15.1-2
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
>* What led up to the situation?
>
> Just dist-upgrade'd my system. After that, anything that depends on pyopenssl
> stopped working, including pip.
>
> In [1]: import cryptography
>
> In [2]: cryptography.__version__
> Out[2]: '1.2.1'
>
> In [3]: import OpenSSL
> ---
> AttributeErrorTraceback (most recent call last)
>  in ()
> > 1 import OpenSSL
>
> /usr/lib/python2.7/dist-packages/OpenSSL/__init__.py in ()
>   6 """
>   7
> > 8 from OpenSSL import rand, crypto, SSL
>   9 from OpenSSL.version import __version__
>  10
>
> /usr/lib/python2.7/dist-packages/OpenSSL/rand.py in ()
>   9 from six import integer_types as _integer_types
>  10
> ---> 11 from OpenSSL._util import (
>  12 ffi as _ffi,
>  13 lib as _lib,
>
> /usr/lib/python2.7/dist-packages/OpenSSL/_util.py in ()
>   4 from six import PY3, binary_type, text_type
>   5
> > 6 from cryptography.hazmat.bindings.openssl.binding import Binding
>   7 binding = Binding()
>   8 ffi = binding.ffi
>
> /usr/lib/python2.7/dist-
> packages/cryptography/hazmat/bindings/openssl/binding.py in ()
>  66 @ffi_callback("int (*)(unsigned char *, int)",
>  67   name="Cryptography_rand_bytes",
> ---> 68   error=-1)
>  69 def _osrandom_rand_bytes(buf, size):
>  70 signed = ffi.cast("char *", buf)
>
> /usr/lib/python2.7/dist-
> packages/cryptography/hazmat/bindings/openssl/binding.py in wrapper(func)
>  55 # def_extern() returns a decorator that sets the internal
>  56 # function pointer and returns the original function
> unmodified.
> ---> 57 ffi.def_extern(name=name, **kwargs)(func)
>  58 callback = getattr(lib, name)
>  59 else:
>
> AttributeError: 'CompiledFFI' object has no attribute 'def_extern'
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing-updates
>   APT policy: (500, 'testing-updates'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages python-openssl depends on:
> ii  python-cryptography  1.2.1-1
> ii  python-six   1.10.0-1
> pn  python:any   
>
> python-openssl recommends no packages.
>
> Versions of packages python-openssl suggests:
> pn  python-openssl-dbg  
> pn  python-openssl-doc  
>
> -- no debconf information



-- 
Sandro "morph" Tosi
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#808043: linux-image-4.3.0-1-powerpc64: Fail to load md_mod with unknow symbol error

[Mathieu Malaterre]

The following link mentions issue with grsec and some version of the kernel:

https://forums.grsecurity.net/viewtopic.php?f=3=4200

Bug#812818: marked as done (should dipy be removeed from debian?)

[Debian Bug Tracking System]

Your message dated Wed, 3 Feb 2016 09:29:11 -0500
with message-id <20160203142911.gr18...@onerussian.com>
and subject line Re: Bug#812818: should dipy be removeed from debian?
has caused the Debian Bug report #812818,
regarding should dipy be removeed from debian?
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.)


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


Dear dipy maintainer,
I know this may sound a bit harsh and premature, but I'm concerned by
the state of dipy in Debian.
The package is currently uninstallable due to the removal of a
dependency (that has been deprecated for 5 years now), and  it's
unbuildable since more than 6 months (and the maintainers are aware of
it, as you can see in #785991#12).
A new upstream release since more or less that time.

From my restricted point of view there is no activity around it (I at
least se no changes in the public VCS).

As of now there are 2 RC bugs, the package is not in testing, there are
no reverse (build-)dependencies and the the popcon is resonably low.

Please, can you consider maintaining the package?  Keeping an unusable
thing in the archive is not going to help our users in any way.


-- 
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
--- End Message ---
--- Begin Message ---
Little update -- we are ready with upload of most recent dipy release
0.10.1 but now it is hunted by regressions due to recent upload numpy
beta  release.  upstream is working on them and I hope that soonish they
would be resolved one way or another.

With this note I would like to close this issue, since dipy project and
its maintenance in debian is alive and kicking, only the 'unstable'
nature of unstable forbids its upload (without e.g. blunt
disabling failing unittests).  So imho removal wouldn't be warranted
ATM, thus no reason for this "bug" to stay open.

On Tue, 26 Jan 2016, Yaroslav Halchenko wrote:

> > As of now there are 2 RC bugs, the package is not in testing, there are
> > no reverse (build-)dependencies and the the popcon is resonably low.

> > Please, can you consider maintaining the package?  Keeping an unusable
> > thing in the archive is not going to help our users in any way.

> Thanks for the buzz... we will fix it up in upcoming days

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

Bug#813644: ruby-albino: FTBFS: assert_match %(# é), code

[Chris Lamb]

Source: ruby-albino
Version: 1.3.3-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,

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

  [..]

  
RUBYLIB=/home/lamby/temp/cdt.20160203231145.5acNUVZ0Oi/ruby-albino-1.3.3/debian/ruby-albino/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-albino/usr/share/rubygems-integration/all
 ruby2.2 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.2 -I"lib"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/*_test.rb" 
  Loaded suite /usr/lib/ruby/vendor_ruby/rake/rake_test_loader
  Started
  .F
  
===
  Failure:
\#\ \u00E9<\/span>/> expected to be =~
<"# 
\u00E9\n\n\n">.
  test_works_with_utf8_strings(AlbinoTest)
  
/home/lamby/temp/cdt.20160203231145.5acNUVZ0Oi/ruby-albino-1.3.3/test/albino_test.rb:42:in
 `test_works_with_utf8_strings'
   39:   def test_works_with_utf8_strings
   40: code = Albino.new("# é", :bash).colorize
   41: assert_match %r(highlight), code
=> 42: assert_match %(# é), code
   43:   end
   44: 
   45:   def test_works_with_files
  
===
  
  
  Finished in 2.846354828 seconds.
  --
  22 tests, 30 assertions, 1 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
  95.4545% passed
  --
  7.73 tests/s, 10.54 assertions/s
  rake aborted!
  Command failed with status (1): [ruby -I"lib"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/**/*_test.rb" ]
  
  Tasks: TOP => default => test
  (See full trace by running task with --trace)
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160203231145.5acNUVZ0Oi/ruby-albino-1.3.3/debian/ruby-albino
 returned exit code 1
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

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


ruby-albino.1.3.3-3.unstable.amd64.log.txt.gz
Description: Binary data

Bug#813647: Further information.

[C. Morgan Hamill]

This thread upstream might be relevant:
http://permalink.gmane.org/gmane.comp.handhelds.openembedded.core/75201
--
Morgan Hamill

Bug#812149: retext: program crash

[Erik Haller]

​- Does this error happen every time you start ReText? Or only for some

*Yes. Happens everytime. No special documents.*

  special documents? (If the latter, can you attach one of them?)

- Did you configure ReText for custom language for spell checking?


*I did not configure any language setting. I enabled spell checking. ​I
​just discovered that it only crashes when spell checking is enabled.*

*​script output:*

*​Script started on Wed 03 Feb 2016 03:57:29 PM PST*
*erik@incense:~$ python3*
*Python 3.5.1+ (default, Jan 13 2016, 15:09:18) *
*[GCC 5.3.1 20160101] on linux*
*Type "help", "copyright", "credits" or "license" for more information.*
*>>> import enchant*
*>>> enchant.Dict('en_US')._Dict__describe()*
*('en_US', 'myspell', 'Myspell Provider',
'/usr/lib/i386-linux-gnu/enchant/libenchant_myspell.so')*
*>>> *
*erik@incense:~$ exit*

*Script done on Wed 03 Feb 2016 03:57:59 PM PST*


*​*
*LANG=en_US.utf8 is set in my shell.*

On Sat, Jan 30, 2016 at 2:27 AM, Dmitry Shachnev  wrote:

> Control: tags -1 +moreinfo
>
> Hi Erik,
>
> On Wed, Jan 20, 2016 at 05:32:44PM -0800, Erik wrote:
> > Ran: retext docs/api.md and received the below output:
> >
> > Traceback (most recent call last):
> >   File "/usr/share/retext/ReText/highlighter.py", line 129, in
> highlightBlock
> > if not self.dictionary.check(match.group(0)):
> >   File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 634,
> in check
> > self._check_this()
> >   File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 606,
> in _check_this
> > _EnchantObject._check_this(self,msg)
> >   File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 176,
> in _check_this
> > raise Error(msg)
> > enchant.errors.Error: Dict unusable: the underlying C-library object has
> been freed.
>
> I cannot reproduce this error.
> Can you please provide me the following details:
>
> - Does this error happen every time you start ReText? Or only for some
>   special documents? (If the latter, can you attach one of them?)
>
> - Did you configure ReText for custom language for spell checking?
>
> - Can you please run python3 console and check what is the enchant provider
>   there? For example:
>
>   >>> import enchant
>   >>> enchant.Dict('en_US')._Dict__describe()
>   ('en_US', 'aspell', 'Aspell Provider',
> '/usr/lib/x86_64-linux-gnu/enchant/libenchant_aspell.so')
>
>   ... and paste all the output here.
>   If you are using a different language, replace en_US with code of that
> language.
>
> Thanks in advance,
>
> --
> Dmitry Shachnev
>

Bug#813647: connman: daemon no longer starts after upgrade

[C. Morgan Hamill]

Package: connman
Version: 1.21-1.2+b2
Severity: grave
Justification: renders package unusable

Connman fails to start. See the attached 'connmand.out' for the segfault
which is printed on running `connmand -n --debug`.

Thanks for your help.
--
Morgan Hamill

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

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

Versions of packages connman depends on:
ii  dbus 1.10.6-1
ii  init-system-helpers  1.24
ii  libc62.21-7
ii  libdbus-1-3  1.10.6-1
ii  libglib2.0-0 2.46.2-3
ii  libgnutls30  3.4.8-2
ii  libreadline6 6.3-8+b4
ii  libxtables11 1.6.0-2
ii  lsb-base 9.20160110

Versions of packages connman recommends:
ii  bluez  5.36-1
pn  ofono  
ii  wpasupplicant  2.3-2.3

Versions of packages connman suggests:
pn  indicator-network  

-- no debconf information
connmand[5781]: Connection Manager version 1.21
connmand[5781]: src/dbus.c:__connman_dbus_init() 
connmand[5781]: src/main.c:parse_config() parsing main.conf
connmand[5781]: src/inotify.c:__connman_inotify_init() 
connmand[5781]: src/technology.c:__connman_technology_init() 
connmand[5781]: src/storage.c:storage_load() Loading /var/lib/connman/settings
connmand[5781]: src/storage.c:storage_load() Loading /var/lib/connman/settings
connmand[5781]: src/notifier.c:__connman_notifier_init() 
connmand[5781]: src/agent.c:__connman_agent_init() 
connmand[5781]: src/service.c:__connman_service_init() 
connmand[5781]: src/agent.c:connman_agent_driver_register() Registering driver 
0x6be180 name service
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_d637d70df97b_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_546f6d4e546f6d735f58656e2077696669_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fec4bf467024_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_616e7369626c65_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_9af97dbef0dd_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_494e46494e4954554d6b677a7a_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_4c41504c2d5075626c6963_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_476f6f676c6520537461726275636b73_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fe5400fc3e5f_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_44415649442031_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_aed21fe1c27c_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_73756265746861_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_42444c7075626c6963_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_feb7764a17b1_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_537461706c6573486f7473706f74_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fe2ae7117c92_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_776972656c657373_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_56696c6c6167652043616665204775657374204e6574776f726b_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_434f4646454520484f555345_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_416d7472616b436f6e6e656374_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_61747477696669_managed_none/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_da67ab1d3186_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/wifi_5ce0c5bea51e_4c61204d6f6e617263612042616b657279_managed_psk/settings
connmand[5781]: src/storage.c:storage_load() Loading 
/var/lib/connman/ethernet_fe0095c5787b_cable/settings
connmand[5781]: src/storage.c:storage_load() Loading 

Bug#813444: marked as done (mbtserver: FTBFS with timblserver 1.8)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2016 03:51:23 +
with message-id 
and subject line Bug#813444: fixed in mbtserver 0.9-1
has caused the Debian Bug report #813444,
regarding mbtserver: FTBFS with timblserver 1.8
to be marked as done.

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

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


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

mbtserver FTBFS with timblserver 1.8 that I just moved from experimental
to sid:

/usr/bin/make  all-recursive
make[2]: Entering directory '/build/mbtserver-0.7'
Making all in src
make[3]: Entering directory '/build/mbtserver-0.7/src'
g++ -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-I/usr/include/libxml2 -I/usr/include/libxml2 -I/usr/include/libxml2 -fopenmp 
-c -o MbtServer.o MbtServer.cxx
g++ -DHAVE_CONFIG_H -I. -I..  -I../include -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-I/usr/include/libxml2 -I/usr/include/libxml2 -I/usr/include/libxml2 -fopenmp 
-c -o MbtServerBase.o MbtServerBase.cxx
MbtServerBase.cxx:35:40: fatal error: timblserver/TimblServerAPI.h: No such 
file or directory
compilation terminated.
Makefile:308: recipe for target 'MbtServerBase.o' failed
make[3]: *** [MbtServerBase.o] Error 1
make[3]: Leaving directory '/build/mbtserver-0.7/src'
Makefile:323: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1

There is a new upstream release 0.10 reported by the watch file and
a new upstream release v3.2.15 on github.


Andreas
--- End Message ---
--- Begin Message ---
Source: mbtserver
Source-Version: 0.9-1

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

Debian distribution maintenance software
pp.
Joost van Baal-Ilić  (supplier of updated mbtserver 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: Thu, 04 Feb 2016 03:48:35 +0100
Source: mbtserver
Binary: mbtserver
Architecture: source amd64
Version: 0.9-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Joost van Baal-Ilić 
Description:
 mbtserver  - Server extensions for the MBT tagger
Closes: 813444
Changes:
 mbtserver (0.9-1) unstable; urgency=low
 .
   * New upstream release (missed 0.8, released 2014-06)
 - Fixes "mbtserver: FTBFS with timblserver 1.8". Thanks Andreas Beckmann
   (Closes: #813444).
   * debian/control: migrated version control from Subversion to git (still on
 Debian's Alioth).  Thanks Jeremy T. Bouse.
   * debian/control: change libtimblserver3-dev into libtimblserver4-dev build
 depends.
   * debian/control: more strict build dependency: now libmbt1-dev (>= 3.2.10),
 as suggested in upstream configure.ac.
   * debian/control, debian/rules: use dh-autoreconf so that 'debian/rules
 clean' does what we want.
Checksums-Sha1:
 81c5b6294c52780099c6a9107ff85e9fedc672fb 1755 mbtserver_0.9-1.dsc
 cbf31e8f265055398e86b57fc57fecbc50e9e7ac 657873 mbtserver_0.9.orig.tar.gz
 61c586103ef47d7c008f951656768f7e30bbb8a5 4292 mbtserver_0.9-1.debian.tar.xz
 4e986d1a874b7d225858f3eef8bca428ccb1a95f 214466 
mbtserver-dbgsym_0.9-1_amd64.deb
 d8937cb4cc1fbbeab8bc448c56b0a84ee419df4a 312884 mbtserver_0.9-1_amd64.deb
Checksums-Sha256:
 4eaf6ea5d0502a0c40741bef466801503ef033a563089bca46764421301ad813 1755 
mbtserver_0.9-1.dsc
 4a2a1a39398ca933eb0982b1b3c1e10bc32d515dc6221e232b781c017e67ee64 657873 
mbtserver_0.9.orig.tar.gz
 d7e24b79d7746249415d68f282fa32d8d2c8dca30387d1c16ed9c645cc743aea 4292 
mbtserver_0.9-1.debian.tar.xz
 59a5e8172d608809a1b61c5a00a9113cb13e7ace9920f83cb9e139c8e830cc49 214466 
mbtserver-dbgsym_0.9-1_amd64.deb
 

Bug#809292: marked as done (slugimage: FTBFS: Ran out of flash space in - 0x00010 bytes too large.)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2016 03:52:50 +
with message-id 
and subject line Bug#809292: fixed in slugimage 1:0.1+20160202.fe8b64a-1
has caused the Debian Bug report #809292,
regarding slugimage: FTBFS: Ran out of flash space in  - 0x00010 
bytes too large.
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.)


-- 
809292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slugimage
Version: 1:0.0+r104-5
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,

slugimage fails to build from source in unstable/amd64. The tmpnam() warnings 
might be be a false-positive from the testsuite's point of view, although the 
method is indeed deprecated in the latest Perl.

  [..]

  Running test ./slugos/large-flashdisk... --- 
./slugos/large-flashdisk.expected2006-12-28 08:41:44.0 +0100
  +++ /tmp/do-test.380  2015-12-29 00:50:02.270030213 +0100
  @@ -1 +1,4 @@
  +Calling POSIX::tmpnam() is deprecated at ../slugimage line 996.
  +Calling POSIX::tmpnam() is deprecated at ../slugimage line 1009.
  +Calling POSIX::tmpnam() is deprecated at ../slugimage line 1017.
   Ran out of flash space in  - 0x00010 bytes too large.
  not ok
  Running test ./slugos/standard... Calling POSIX::tmpnam() is deprecated at 
../slugimage line 996.
  Calling POSIX::tmpnam() is deprecated at ../slugimage line 1009.
  Calling POSIX::tmpnam() is deprecated at ../slugimage line 1017.
  ok
  Makefile:5: recipe for target 'test' failed
  make[1]: *** [test] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20151229004955.DQkH00QubC/slugimage-0.0+r104'
  dh_auto_test: make -j1 test returned exit code 2
  debian/rules:12: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


slugimage.1:0.0+r104-5.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: slugimage
Source-Version: 1:0.1+20160202.fe8b64a-1

We believe that the bug you reported is fixed in the latest version of
slugimage, 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.
Martin Michlmayr  (supplier of updated slugimage 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: Wed, 03 Feb 2016 18:29:45 -0800
Source: slugimage
Binary: slugimage
Architecture: source all
Version: 1:0.1+20160202.fe8b64a-1
Distribution: unstable
Urgency: low
Maintainer: Marc Singer 
Changed-By: Martin Michlmayr 
Description:
 slugimage  - NSLU2 firmware image manipulation utility
Closes: 809292
Changes:
 slugimage (1:0.1+20160202.fe8b64a-1) unstable; urgency=low
 .
   * Add Vcs-Browser field.
   * Use debhelper 9.
   * Increase Standards-Version to 3.9.6.
   * Use 3.0 (quilt) format.
   * Remove Rod Whitby from Uploaders.
   * Update debian/rules get-orig-source to fetch from GitHub.
   * Update to git 2016-02-02 (fe8b64a):
 - Use tempfile from File::Temp (Closes: #809292)
Checksums-Sha1:
 d3c829aa9b9c709a4018504dd21488e729e60787 1967 
slugimage_0.1+20160202.fe8b64a-1.dsc
 31edc8d1ec971f895fd0eb1ed59e704885474bad 15206 
slugimage_0.1+20160202.fe8b64a.orig.tar.gz
 f558ed42057cb78c7b46eada87ee8a62b7b1ce8a 2428 
slugimage_0.1+20160202.fe8b64a-1.debian.tar.xz
 15c2acab344d12b76977d80f47ee31004785fc81 13164 
slugimage_0.1+20160202.fe8b64a-1_all.deb
Checksums-Sha256:
 617992134b612a8844ec808490f64ac392d5b99d3b63ed0736664c49aea3c97b 1967 
slugimage_0.1+20160202.fe8b64a-1.dsc
 808dd2400e70d9483faf0d83676def23f07812598f7fd8d203668e151e3beb44 15206 
slugimage_0.1+20160202.fe8b64a.orig.tar.gz
 4ab23391bb4012aeae7666508c7aea18f3c2bc898c4be3735f71328ae980bbbf 2428 
slugimage_0.1+20160202.fe8b64a-1.debian.tar.xz
 

Bug#812818: should dipy be removeed from debian?

[Mattia Rizzolo]

ok, fair enough.
thanks for your work!

On Wed, Feb 3, 2016 at 2:29 PM Yaroslav Halchenko  wrote:

> Little update -- we are ready with upload of most recent dipy release
> 0.10.1 but now it is hunted by regressions due to recent upload numpy
> beta  release.  upstream is working on them and I hope that soonish they
> would be resolved one way or another.
>
> With this note I would like to close this issue, since dipy project and
> its maintenance in debian is alive and kicking, only the 'unstable'
> nature of unstable forbids its upload (without e.g. blunt
> disabling failing unittests).  So imho removal wouldn't be warranted
> ATM, thus no reason for this "bug" to stay open.
>
> On Tue, 26 Jan 2016, Yaroslav Halchenko wrote:
>
> > > As of now there are 2 RC bugs, the package is not in testing, there are
> > > no reverse (build-)dependencies and the the popcon is resonably low.
>
> > > Please, can you consider maintaining the package?  Keeping an unusable
> > > thing in the archive is not going to help our users in any way.
>
> > Thanks for the buzz... we will fix it up in upcoming days
>
> > Cheers!
> --
> 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
>

Processed: forcibly merging 813455 813426

[Debian Bug Tracking System]

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

> forcemerge 813455 813426
Bug #813455 [dpkg] [dpkg] dpkg-maintscript-helper dir_to_symlink should be 
transparent to arch:all arch:any package
Bug #813426 [dpkg] warning: /etc/alternatives/compare is dangling; it will be 
updated with best choice
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'
Bug #813455 [dpkg] [dpkg] dpkg-maintscript-helper dir_to_symlink should be 
transparent to arch:all arch:any package
Added tag(s) moreinfo.
Bug #813546 [dpkg] loop when package is in "Bu" state and one tries to install 
it
Merged 813426 813455 813546
> thanks
Stopping processing here.

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

Processed: notfound 813597 in python-cryptography/1.2.1-1, closing 813597

[Debian Bug Tracking System]

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

> notfound 813597 python-cryptography/1.2.1-1
Bug #813597 [python-cryptography] python-openssl: exception when importing 
OpenSSL
No longer marked as found in versions python-cryptography/1.2.1-1.
> close 813597
Bug #813597 [python-cryptography] python-openssl: exception when importing 
OpenSSL
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#813596: coq-float: FTBFS: make[2]: *** No rule to make target 'depend'. Stop.

[Chris Lamb]

Source: coq-float
Version: 1:8.4-5
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,

coq-float fails to build from source in unstable/amd64:

  [..]

  "coqdep" -c -R "." Float "Rpow.v" > "Rpow.v.d" || ( RV=$?; rm -f "Rpow.v.d"; 
exit ${RV} )
  "coqdep" -c -R "." Float "MSB.v" > "MSB.v.d" || ( RV=$?; rm -f "MSB.v.d"; 
exit ${RV} )
  "coqdep" -c -R "." Float "sTactic.v" > "sTactic.v.d" || ( RV=$?; rm -f 
"sTactic.v.d"; exit ${RV} )
  "coqdep" -c -R "." Float "Ct2/FboundI.v" > "Ct2/FboundI.v.d" || ( RV=$?; rm 
-f "Ct2/FboundI.v.d"; exit ${RV} )
  "coqdep" -c -R "." Float "Ct2/FnormI.v" > "Ct2/FnormI.v.d" || ( RV=$?; rm -f 
"Ct2/FnormI.v.d"; exit ${RV} )
  make[2]: *** No rule to make target 'depend'.  Stop.
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160203150051.4L9HxmH46z/coq-float-8.4'
  debian/rules:29: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160203150051.4L9HxmH46z/coq-float-8.4'
  debian/rules:17: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


coq-float.1:8.4-5.unstable.amd64.log.txt.gz
Description: Binary data

Bug#813597: Versions

[Tristan Seligmann]

Control: found -1 python-cryptography/1.2.1-1
Control: tag -1 + moreinfo

Could you check and report what versions of python-cffi and
python-cffi-backend you have installed? (ie. dpkg -l python-cffi
python-cffi-backend)

Also the output of "import cffi; cffi" from the same Python interpreter
session as the one where you experience the import-time error.

Processed: Re: Bug#791195: fixed in lttoolbox 3.3.2~r61000-3.1

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.3.2~r63423-1
Bug #791195 [src:lttoolbox] lttoolbox: library transition may be needed when 
GCC 5 is the default
Marked as found in versions lttoolbox/3.3.2~r63423-1.

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

Bug#791195: fixed in lttoolbox 3.3.2~r61000-3.1

[Andreas Beckmann]

Control: found -1 3.3.2~r63423-1

On 2016-02-03 11:45, Kartik Mistry wrote:
> On Wed, Feb 3, 2016 at 4:04 PM, Julien Cristau  wrote:
>>> The v5 transition was entirely unnecessary for this package, and I very
>>> strongly want it gone.
>>>
>> You haven't given a single good reason to revert the change.  Maybe you
>> would have preferred it didn't, but you're coming 6 months late to that
>> party.
> 
> Apologies!
> 
> What is the best way to fix this?

Probably reverting the reverted transition, therefore reopening this bug.

You can drop the v5 suffix once upstream bumps the SOVERSION again and
you have to rename the package anyway.


Andreas

Bug#813597: Versions

[Daniel Monteiro Basso]

Yep, that was it, I was using a local (pip installed) version of cffi.
I apologize for wasting your time guys. Thank you for the help.

Cheers,
Daniel

On Wed, 2016-02-03 at 15:53 +, Tristan Seligmann wrote:
> Could you check and report what versions of python-cffi and
> python-cffi-backend you have installed? (ie. dpkg -l python-cffi
> python-cffi-backend)

python-cffi & backend 1.5.0-1

> Also the output of "import cffi; cffi" from the same Python
> interpreter session as the one where you experience the import-time
> error.

import cffi; cffi

1.1.0

Bug#813641: multcomp: FTBFS: Error : package 'MASS' required by 'TH.data' could not be found

[Dirk Eddelbuettel]

On 3 February 2016 at 23:31, Chris Lamb wrote:
| Source: multcomp
| Version: 1.4-2-1
| Severity: serious
| Justification: fails to build from source
| User: reproducible-bui...@lists.alioth.debian.org
| Usertags: ftbfs
| X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
| 
| Dear Maintainer,
| 
| multcomp fails to build from source in unstable/amd64:
| 
|   [..]
| 
|   * installing *source* package 'multcomp' ...
|   ** package 'multcomp' successfully unpacked and MD5 sums checked
|   ** R
|   ** data
|   *** moving datasets to lazyload DB
|   ** demo
|   ** inst
|   ** preparing package for lazy loading
|   Error : package 'MASS' required by 'TH.data' could not be found
|   ERROR: lazy loading failed for package 'multcomp'
|   * removing 
'/home/lamby/temp/cdt.20160203230629.amdKvAuzFF/multcomp-1.4-2/debian/r-cran-multcomp/usr/lib/R/site-library/multcomp'
|   /usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
|   make: *** [R_any_arch] Error 1

Thanks. It is actually a bug in TH.data (aka r-cran-th.data) which should
pull MASS (aka r-cran-mass) in.  Rebuilding that one now; will rebuild this
one in a day or so.

Dirk
 
|   [..]
| 
| The full build log is attached.
| 
| 
| Regards,
| 
| -- 
|   ,''`.
|  : :'  : Chris Lamb
|  `. `'`  la...@debian.org / chris-lamb.co.uk
|`-
| [DELETED ATTACHMENT multcomp.1.4-2-1.unstable.amd64.log.txt.gz, Untyped 
binary data]

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#810643: marked as done (python-axiom: FTBFS: test_sequence.TestSequenceOperations.test_slices: Second list contains 3 additional elements.)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2016 07:15:11 +
with message-id 

and subject line Fixed upstream
has caused the Debian Bug report #810643,
regarding python-axiom: FTBFS: 
test_sequence.TestSequenceOperations.test_slices: Second list contains 3 
additional elements.
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.)


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

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

  [..]

  
  axiom.test.test_sequence.TestSequenceOperations.test_slices
  
===
  [FAIL]
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160110203943.qbfpd3MfZm/python-axiom-0.7.4/debian/python-axiom/usr/lib/python2.7/site-packages/axiom/test/test_query.py",
 line 1239, in testOneColumnAndStrings
  self.assertEquals(sorted(q), sorted(e))
File "/usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py", line 
437, in assertEqual
  super(_Assertions, self).assertEqual(first, second, msg)
File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
  assertion_func(first, second, msg=msg)
File "/usr/lib/python2.7/unittest/case.py", line 742, in assertListEqual
  self.assertSequenceEqual(list1, list2, msg, seq_type=list)
File "/usr/lib/python2.7/unittest/case.py", line 724, in assertSequenceEqual
  self.fail(msg)
  twisted.trial.unittest.FailTest: Lists differ: [] != [D(four=u'd2.four', 
id='2', on...
  
  Second list contains 3 additional elements.
  First extra element 0:
  D(four=u'd2.four', id='2', one='d2.one', three='d2.three', two='d2.two', 
storeID=2)@0x7f64eccee3d0
  
  - []
  + [D(four=u'd2.four', id='2', one='d2.one', three='d2.three', two='d2.two', 
storeID=2)@0x7f64eccee3d0,
  +  D(four=u'd1.four', id='1', one='d1.one', three='d1.three', two='d1.two', 
storeID=1)@0x7f64eccee510,
  +  D(four=u'd3.four', id='3', one='d3.one', three='d3.three', two='d3.two', 
storeID=3)@0x7f64ecceedd0]
  
  axiom.test.test_query.WildcardQueries.testOneColumnAndStrings
  
===
  [FAIL]
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160110203943.qbfpd3MfZm/python-axiom-0.7.4/debian/python-axiom/usr/lib/python2.7/site-packages/axiom/test/test_query.py",
 line 1221, in testOneString
  self.assertEquals(self.query(D, D.one.like('d1.one')), [self.d1])
File "/usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py", line 
437, in assertEqual
  super(_Assertions, self).assertEqual(first, second, msg)
File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
  assertion_func(first, second, msg=msg)
File "/usr/lib/python2.7/unittest/case.py", line 742, in assertListEqual
  self.assertSequenceEqual(list1, list2, msg, seq_type=list)
File "/usr/lib/python2.7/unittest/case.py", line 724, in assertSequenceEqual
  self.fail(msg)
  twisted.trial.unittest.FailTest: Lists differ: [] != [D(four=u'd1.four', 
id='1', on...
  
  Second list contains 1 additional elements.
  First extra element 0:
  D(four=u'd1.four', id='1', one='d1.one', three='d1.three', two='d1.two', 
storeID=1)@0x7f64ed529150
  
  - []
  + [D(four=u'd1.four', id='1', one='d1.one', three='d1.three', two='d1.two', 
storeID=1)@0x7f64ed529150]
  
  axiom.test.test_query.WildcardQueries.testOneString
  
===
  [FAIL]
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160110203943.qbfpd3MfZm/python-axiom-0.7.4/debian/python-axiom/usr/lib/python2.7/site-packages/axiom/test/test_query.py",
 line 1296, in testOtherTable
  self.query(D, D.one.startswith(C.name)), [self.d1])
File "/usr/lib/python2.7/dist-packages/twisted/trial/_synctest.py", line 
437, in assertEqual
  super(_Assertions, self).assertEqual(first, second, msg)
File "/usr/lib/python2.7/unittest/case.py", line 513, in assertEqual
  assertion_func(first, second, msg=msg)
File "/usr/lib/python2.7/unittest/case.py", line 742, in assertListEqual
  self.assertSequenceEqual(list1, list2, msg, seq_type=list)
  

Bug#808821: asymptote: failing to build on mips

[Norbert Preining]

> I just checked, not released by now, but as soon as it is I will update
> the Debian repository.

Now imported, and building right now. Let us hope that MIPS this
time works out ;-)

Norbert


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

Bug#812469: fixed by update

[-]

This bug has disappeared for me after the following update (copy-paste from
Synaptic History):


Removed the following packages:
libgdome2-cpp-smart0c2a

Upgraded the following packages:
adwaita-icon-theme (3.16.2.1-2) to 3.18.0-2
gir1.2-gtk-2.0 (2.24.28-1) to 2.24.29-1
gir1.2-gtk-3.0 (3.16.6-1) to 3.18.6-1
gir1.2-gtk-vnc-2.0 (0.5.3-1.3) to 0.5.3-1.3+b1
gir1.2-gtkclutter-1.0 (1.4.4-3+b1) to 1.6.6-1
gir1.2-gtksource-3.0 (3.10.2-1) to 3.18.2-1
gir1.2-nmgtk-1.0 (0.9.8.8-1) to 1.0.10-1
gir1.2-vte-2.91 (0.40.2-2) to 0.42.1-2+b1
gpicview (0.2.4-1) to 0.2.4-2+b2
gtk-3-examples (3.16.6-1) to 3.18.6-1
gtk2-engines-pixbuf (2.24.28-1) to 2.24.29-1
libappindicator3-1 (0.4.92-3) to 0.4.92-3.1
libcolord-gtk1 (0.1.25-1.1) to 0.1.26-1
libgail18 (2.24.28-1) to 2.24.29-1
libgtk-3-0 (3.16.6-1) to 3.18.6-1
libgtk-3-bin (3.14.5-1) to 3.18.6-1
libgtk-3-common (3.16.6-1) to 3.18.6-1
libgtk-3-dev (3.16.6-1) to 3.18.6-1
libgtk-vnc-2.0-0 (0.5.3-1) to 0.5.3-1.3+b1
libgtk2.0-0 (2.24.28-1) to 2.24.29-1
libgtk2.0-0:i386 (2.24.28-1) to 2.24.29-1
libgtk2.0-bin (2.24.28-1) to 2.24.29-1
libgtk2.0-common (2.24.22-1) to 2.24.29-1
libgtk2.0-dev (2.24.28-1) to 2.24.29-1
libgtkmathview-bin (0.8.0-10) to 0.8.0-13
libgtkmathview0c2a (0.8.0-10) to 0.8.0-13
libgtkmm-3.0-1v5 (3.16.0-2+b1) to 3.18.0-1
libgtksourceview-3.0-1 (3.18.1-1) to 3.18.2-1
libgtksourceview-3.0-common (3.18.1-1) to 3.18.2-1
libgtksourceview-3.0-doc (3.10.2-1) to 3.18.2-1
libgtksourceview2.0-common (2.10.5-1) to 2.10.5-2
libjavascriptcoregtk-3.0-0 (2.4.7-1) to 2.4.9-3
libkeybinder0 (0.3.0-3) to 0.3.1-1
libnm-gtk-common (0.9.10.0-2) to 1.0.10-1
libnm-gtk0 (0.9.10.0-2) to 1.0.10-1
libvte-2.91-0 (0.40.2-2) to 0.42.1-2+b1
libvte-2.91-common (0.40.2-2) to 0.42.1-2
libwebkitgtk-3.0-0 (2.4.7-1) to 2.4.9-3
libwebkitgtk-3.0-common (2.4.7-1) to 2.4.9-3
libxrandr-dev (2:1.4.2-1+b1) to 2:1.5.0-1
libxrandr2 (2:1.4.2-1+b1) to 2:1.5.0-1
libxrandr2:i386 (2:1.4.2-1+b1) to 2:1.5.0-1
python-keybinder (0.3.0-3) to 0.3.1-1
xarchiver (1:0.5.2+20130119+dfsg-3) to 1:0.5.4-2

Installed the following packages:
libgdome2-cpp-smart0v5 (0.2.6-6.2+b1)


I think, that the problem  was in gtk-3.0 libraries.

Bug#808821: asymptote: failing to build on mips

[Norbert Preining]

> Now imported, and building right now. Let us hope that MIPS this
> time works out ;-)

Ok, after adding dh_autoreconf (and dh ... --with autoreconf) to get
a proper configure script, building here in a clean chroot 
succeeded.

Unfortunately with warnings that I graciously ignore:

cd .. && ../asy -dir ../base -config "" -render=0 -f png -o png/ markers1.asy
failed to create directory /nonexistent/.asy.

Before uploading I am now building the current package on MIPS
(minkus) to see if it really works out.

Norbert


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

Processed: reassign 813528 to alsa-utils, forcibly merging 813563 813528

[Debian Bug Tracking System]

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

> reassign 813528 alsa-utils
Bug #813528 [alsa-utils-1.1.0-1] alsa-utils-1.1.0-1: Overwrite files from 
unrelated package
Warning: Unknown package 'alsa-utils-1.1.0-1'
Bug reassigned from package 'alsa-utils-1.1.0-1' to 'alsa-utils'.
Ignoring request to alter found versions of bug #813528 to the same values 
previously set
Ignoring request to alter fixed versions of bug #813528 to the same values 
previously set
> forcemerge 813563 813528
Bug #813563 [alsa-utils] alsa-utils: Overwrite files from unrelated package
Bug #813473 [alsa-utils] alsa-utils: Upgrade failed with bacula-console-qt 
installed
Bug #813479 [alsa-utils] file conflicts without conflicts: header
Bug #813528 [alsa-utils] alsa-utils-1.1.0-1: Overwrite files from unrelated 
package
Severity set to 'serious' from 'critical'
Added indication that 813528 affects bacula-console-qt,bareos-bat
Marked as found in versions alsa-utils/1.1.0-1.
Bug #813479 [alsa-utils] file conflicts without conflicts: header
Removed indication that 813479 affects bacula-console-qt and bareos-bat
Added indication that 813479 affects bacula-console-qt,bareos-bat
Removed indication that 813473 affects bareos-bat and bacula-console-qt
Added indication that 813473 affects bacula-console-qt,bareos-bat
Removed indication that 813563 affects bareos-bat and bacula-console-qt
Added indication that 813563 affects bacula-console-qt,bareos-bat
Bug #813473 [alsa-utils] alsa-utils: Upgrade failed with bacula-console-qt 
installed
Merged 813473 813479 813528 813563
> thanks
Stopping processing here.

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

Bug#813573: marked as done ([php-horde] XSS vulnerability in menu bar)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2016 07:21:36 +
with message-id 
and subject line Bug#813573: fixed in php-horde 5.2.9+debian0-1
has caused the Debian Bug report #813573,
regarding [php-horde] XSS vulnerability in menu bar
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.)


-- 
813573: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-horde
Version: 5.2.8+debian0-1

Hello,

According to: http://lists.horde.org/archives/announce/2016/001140.html

Regards
-- 
Mathieu Parent
--- End Message ---
--- Begin Message ---
Source: php-horde
Source-Version: 5.2.9+debian0-1

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

Debian distribution maintenance software
pp.
Mathieu Parent  (supplier of updated php-horde 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: Wed, 03 Feb 2016 23:40:14 +0100
Source: php-horde
Binary: php-horde
Architecture: source all
Version: 5.2.9+debian0-1
Distribution: unstable
Urgency: medium
Maintainer: Horde Maintainers 
Changed-By: Mathieu Parent 
Description:
 php-horde  - ${phppear:summary}
Closes: 813573
Changes:
 php-horde (5.2.9+debian0-1) unstable; urgency=medium
 .
   * New upstream version 5.2.9+debian0
 - Fixes XSS vulnerability in menu bar (Closes: #813573)
   * Update patch
Checksums-Sha1:
 899bfbce9984b27a758f7d9669cadb171224703c 2005 php-horde_5.2.9+debian0-1.dsc
 b46542b6d7a1013f25aac481de2824a943d69f29 2927951 
php-horde_5.2.9+debian0.orig.tar.gz
 64456bb5b203cefeac5a348e6779a8e47a6d142b 7612 
php-horde_5.2.9+debian0-1.debian.tar.xz
 2ffdf34348b859cd46429fcafd2839f71f299914 1746568 
php-horde_5.2.9+debian0-1_all.deb
Checksums-Sha256:
 3bae0d495edf9416117ff2a8615fc68fa0db63a2ebb10519a352a5aa49c18913 2005 
php-horde_5.2.9+debian0-1.dsc
 6dc07a47912b14adef5eb019d4defe23255091cd99e2385e2b9a300f1f459761 2927951 
php-horde_5.2.9+debian0.orig.tar.gz
 c2a9e0eba3346fbb589a722e59b3d2c358d69b5307c5e41e50d6b8250610d47e 7612 
php-horde_5.2.9+debian0-1.debian.tar.xz
 8af2834d94136d12836b0249f80ae97d20d208f060da8f618d1d550aca9318b0 1746568 
php-horde_5.2.9+debian0-1_all.deb
Files:
 eb8bc6049e60a1d2a4f45bb9a2e191f1 2005 php extra php-horde_5.2.9+debian0-1.dsc
 20f926160a2596c8180e8aa09e27f27a 2927951 php extra 
php-horde_5.2.9+debian0.orig.tar.gz
 4c8885f612bc6f913a7fdebd7850106d 7612 php extra 
php-horde_5.2.9+debian0-1.debian.tar.xz
 b63cbdb973919b95e57b9c93212a0c89 1746568 php extra 
php-horde_5.2.9+debian0-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWsvcTAAoJEK4DmARmaB+lPDwQALhK/bQ9o7y7o5MDFggOi/g8
v32btVfARQK71rahDfUaXqVBsxN5As8JvLdOoSerRJZ8+teC1fBLLIluM7axqxmj
mVlAFD/o/I9PWoi+sLtokjFkuvcYLl083W2AwzQoosqY67ApVWkdhsNpos1d/MHD
+RLgiYZ53/PASW2te55OeNO3T8MtwoaGbWILGtvw8Zs6lsENxgNm9kBJX09PkNju
kiKkHD/aPJEwnkYm22XwcA3/70/gwzXjcJ4lDQhgROj30tLt+KFWyM3zyIDfp58h
DAWuucVpqbva22D1tS9WD7VLvz/0+89Z7PozJIrKA69460gpGWWdX9YQhLajetgh
VV2QFR7YnrU4x0WGyRghNFY6C3O18oq9cjytX261m5LFMXM1/qoZL3cuu0pPDqsG
uceGE3D1mONSW6rVXI9BpR8sqFAj4I//+PcvDHid9vBYHslfydStqEvZDXbuivnX
Obh+ete5jb4ciBI1JDEAzLupISzUc0EaxxpRyS6y5lT32tQ7mFQTB3N7mzQtRyij
7ZRxx8IaTvYcQeTGmx7Ln5i1da6HDYpkHVpS/d7Gf+vshYDzNrxfMdE2sOtfPNhP
qu+Y14GhpT7rz1/U/pejBVLId8PUqzOy3IJYJHRXtSY/MOfsarhJSMRgB4uVowAH
POmFJAiqLB3ySytvXheh
=SqGP
-END PGP SIGNATURE End Message ---

Processed: Bug#786317 marked as pending

[Debian Bug Tracking System]

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

> tag 786317 pending
Bug #786317 [src:python-peak.util] python-peak.util: deprecation of 
python-support
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#786317: marked as pending

[Daniele Tricoli]

tag 786317 pending
thanks

Hello,

Bug #786317 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-peak.util.git;a=commitdiff;h=cb740f0

---
commit cb740f058dac0dfee8663eda06a6327300b1f53c
Author: Daniele Tricoli 
Date:   Thu Feb 4 04:46:25 2016 +0100

Update changelog

diff --git a/debian/changelog b/debian/changelog
index 999ad42..8668eda 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -6,8 +6,24 @@ python-peak.util (20160204-1) UNRELEASED; urgency=low
   [ Daniele Tricoli ]
   * New release.
 - Add peak.util.proxies 0.9. (Closes: #732826)
+  * Replace deprecated dh_pysupport with dh_python2. (Closes: #786317)
+  * Switch watch files to pypi.debian.net.
+  * debian/compat
+- Bump debhelper compatibility level to 9.
+  * debian/control
+- Update Vcs fields for git migration.
+- Bump Standards-Version to 3.9.7 (no changes needed).
+- Bump debhelper Build-Depends to (>=9).
+- Add Add X-Python-Version.
+- Mention ProxyTypes in Description field.
+  * debian/copyright
+- Add ProxyTypes source location.
+- Update copyright years.
+- Update Format URI.
+  * debian/rules
+- Make get-orig-source comply to Policy 4.9.
 
- -- Daniele Tricoli   Thu, 04 Feb 2016 01:28:05 +0100
+ -- Daniele Tricoli   Thu, 04 Feb 2016 04:42:00 +0100
 
 python-peak.util (20110909-1) unstable; urgency=low
 

Bug#813445: marked as done (frog: FTBFS with timblserver 1.8)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2016 05:49:27 +
with message-id 
and subject line Bug#813445: fixed in frog 0.12.20-1
has caused the Debian Bug report #813445,
regarding frog: FTBFS with timblserver 1.8
to be marked as done.

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

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


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

Hi,

frog FTBFS with timblserver 1.8 that I just moved from experimental
to sid:

[...]
g++ -DHAVE_CONFIG_H -I. -I..  -I../include  -DSYSCONF_PATH=\"/etc\" 
-DPYTHONDIR=\"/usr/lib/python2.7/dist-packages/frog\" -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -fopenmp 
-I/usr/include  -I/usr/include/libxml2 -fopenmp -I/usr/include/libxml2 
-I/usr/include/libxml2 -I/usr/include/libxml2 -I/usr/include/libxml2 
-I/usr/include/python2.7 -c -o Frog.o Frog.cxx
Frog.cxx:46:40: fatal error: timblserver/TimblServerAPI.h: No such file or 
directory
compilation terminated.
Makefile:454: recipe for target 'Frog.o' failed
make[3]: *** [Frog.o] Error 1
make[3]: Leaving directory '/build/frog-0.12.17/src'
Makefile:354: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/build/frog-0.12.17'
Makefile:285: recipe for target 'all' failed
make[1]: *** [all] Error 2

The watch file reports a new upstream release 0.13.0


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: frog
Source-Version: 0.12.20-1

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

Debian distribution maintenance software
pp.
Joost van Baal-Ilić  (supplier of updated frog 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: Thu, 04 Feb 2016 06:13:31 +0100
Source: frog
Binary: frog libfrog1
Architecture: source amd64
Version: 0.12.20-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Joost van Baal-Ilić 
Description:
 frog   - tagger and parser for natural languages (runtime)
 libfrog1   - tagger and parser for Dutch language (library)
Closes: 734151 813445
Changes:
 frog (0.12.20-1) unstable; urgency=low
 .
   * New upstream release.  (Missed: 0.12.18, released 2014-09-16; 0.12.19,
 released 2014-12-01)
 - Fixes "frog: FTBFS with timblserver 1.8". Thanks Andreas Beckmann
   (Closes: #813445).
   * debian/control: update description (thanks Ko van der Sloot).
   * debian/copyright: Now _really_ no longer point to the versionless
 symlink to license files.
   * debian/{control,copyright,rules,watch}: migrated version control
 from Subversion to git (still on Debian's Alioth).  Change version
 control tags from Subversion to git.
   * debian/watch: more strict.
   * debian/control: change Build-Depends
 - "libtimblserver3-dev | libtimblserver-dev" into "libtimblserver4-dev",
 - "libfolia2-dev | libfolia-dev" into libfolia-dev (>= 0.13-1~),
 - "libticcutils2-dev | libticcutils-dev" into "libticcutils2-dev (>= 0.5)",
 - "libucto2-dev | libucto-dev" into "libucto-dev (>= 0.8.0)".
   * debian/control: In the default configuration, frog attempts to use the
 ucto tokenizer, and gives a cryptic error message when it is not found.
 Therefore: add "Recommends: ucto" to Package frog.  Thanks Andreas van
 Cranenburgh (Closes: #734151).
   * Acknowledge NMU 0.12.17-7.1, thanks Luk Claes.
   * .gitignore: added.
Checksums-Sha1:
 e0643fe47451808ecfd7ab812bdacb3bf60c5e47 1886 frog_0.12.20-1.dsc
 8141bda88ff4a7be36f807f1e8187c4e27c967d5 494254 frog_0.12.20.orig.tar.gz
 c2af37396ac8c1b8bc86506bf0f40a07bb6a5c97 6376 frog_0.12.20-1.debian.tar.xz
 ea40efac25afecc8928b2780387a35991cba71a3 881648 frog-dbgsym_0.12.20-1_amd64.deb
 b9e17af62287ff5bfb6686fb50734c2e47fc9ecd 79488 

Bug#813601: marked as done (linux-image-3.16: kernel panic when umounting rootfs)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2016 04:20:28 +
with message-id <1454559628.3989.20.ca...@decadent.org.uk>
and subject line Re: linux-image-3.16: kernel panic when umounting rootfs
has caused the Debian Bug report #813601,
regarding linux-image-3.16: kernel panic when umounting rootfs
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.)


-- 
813601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813601
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt11-1+deb8u6
Severity: critical
Tags: patch
Justification: breaks the whole system

Dear Maintainer,

This upstream commit is missing:
da362b09e42e umount: Do not allow unmounting rootfs.
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=da362b09e42e

The commit log of this patch explains how to reproduce the kernel panic (see 
below).

Note that this patch depends on
5ff9d8a65ce8 vfs: Lock in place mounts from more privileged users
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5ff9d8a65ce8

Regards,
Nicolas


-- 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-ckt11-1+deb8u6 (2015-11-09)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/6WIND-debian8 ro 
console=ttyS0,115200n8 quiet

** Not tainted

** Kernel log:
[0.307242] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[0.307253] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[0.307264] intel_idle: does not run on family 6 model 60
[0.307286] GHES: HEST is not enabled!
[0.307371] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[0.329356] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 
16550A
[0.351248] 00:06: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 
16550A
[0.351502] Linux agpgart interface v0.103
[0.351588] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 
0x60,0x64 irq 1,12
[0.352073] serio: i8042 KBD port at 0x60,0x64 irq 1
[0.352077] serio: i8042 AUX port at 0x60,0x64 irq 12
[0.352274] mousedev: PS/2 mouse device common for all mice
[0.352437] input: AT Translated Set 2 keyboard as 
/devices/platform/i8042/serio0/input/input0
[0.352569] rtc_cmos 00:00: RTC can wake from S4
[0.352748] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
[0.352818] rtc_cmos 00:00: alarms up to one day, 114 bytes nvram, hpet irqs
[0.352848] ledtrig-cpu: registered to indicate activity on CPUs
[0.352913] AMD IOMMUv2 driver by Joerg Roedel 
[0.352914] AMD IOMMUv2 functionality not available on this system
[0.352966] TCP: cubic registered
[0.353150] NET: Registered protocol family 10
[0.353323] mip6: Mobile IPv6
[0.353326] NET: Registered protocol family 17
[0.353330] mpls_gso: MPLS GSO support
[0.353567] registered taskstats version 1
[0.353776] rtc_cmos 00:00: setting system clock to 2016-02-03 14:33:55 UTC 
(1454510035)
[0.353809] PM: Hibernation image not present or could not be loaded.
[0.354519] Freeing unused kernel memory: 1204K (818ee000 - 
81a1b000)
[0.354521] Write protecting the kernel read-only data: 8192k
[0.355897] Freeing unused kernel memory: 924K (880001519000 - 
88000160)
[0.356232] Freeing unused kernel memory: 216K (8800017ca000 - 
88000180)
[0.363665] systemd-udevd[65]: starting version 215
[0.364044] random: systemd-udevd urandom read with 1 bits of entropy 
available
[0.372312] SCSI subsystem initialized
[0.376219] libata version 3.00 loaded.
[0.379153] Floppy drive(s): fd0 is 1.44M
[0.390411] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[0.390939] ata_piix :00:01.1: version 2.13
[0.391593] virtio-pci :00:03.0: irq 40 for MSI/MSI-X
[0.391603] virtio-pci :00:03.0: irq 41 for MSI/MSI-X
[0.391612] virtio-pci :00:03.0: irq 42 for MSI/MSI-X
[0.391742] scsi0 : ata_piix
[0.391844] scsi1 : ata_piix
[0.391882] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc020 irq 14
[0.391883] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc028 irq 15
[0.392532] FDC 0 is a S82078B
[0.548567] ata2.01: NODEV after polling detection
[0.548740] ata1.01: NODEV after polling detection
[0.548943] ata2.00: ATAPI: QEMU DVD-ROM, 2.3.0, max UDMA/100
[0.549085] ata1.00: ATA-7: QEMU HARDDISK, 2.3.0, max UDMA/100
[0.549086] ata1.00: 62914560 sectors, multi 16: 

Bug#812796: tokyocabinet: testsuite sometimes failes

[Tobias Frost]

Source: tokyocabinet
Followup-For: Bug #812796

I'm be able to reproduce this on a ppc64el porter box.

Could be caused by https://bugzilla.redhat.com/show_bug.cgi?id=572594, though I
did not come along to test this. 

--
tobi

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

Kernel: Linux 4.0.5-revert-done (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: sysvinit (via /sbin/init)

Bug#813426: [Pkg-gmagick-im-team] Bug#813426: warning: /etc/alternatives/compare is dangling; it will be updated with best choice

[roucaries bastien]

On Wed, Feb 3, 2016 at 8:47 AM, Vincent Fourmond  wrote:
> control: severity -1 serious
>
>   Hello,
>
> On Wed, Feb 3, 2016 at 12:52 AM, 積丹尼 Dan Jacobson  wrote:
>>
>> What  a   mess.
>
>   I can only agree...

It is experimental
>
>> Preparing to unpack .../libmagickwand-6.q16-2_8%3a6.9.2.10+dfsg-2_i386.deb 
>> ...
>> Unpacking libmagickwand-6.q16-2:i386 (8:6.9.2.10+dfsg-2) over 
>> (8:6.9.2.10+dfsg-1) ...
>> Preparing to unpack .../imagemagick-6-doc_8%3a6.9.2.10+dfsg-2_all.deb ...
>> Unpacking imagemagick-6-doc (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) ...
>> Preparing to unpack .../imagemagick-doc_8%3a6.9.2.10+dfsg-2_all.deb ...
>> Unpacking imagemagick-doc (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) ...
>> Preparing to unpack .../libmagickcore-6.q16-2_8%3a6.9.2.10+dfsg-2_i386.deb 
>> ...
>> Unpacking libmagickcore-6.q16-2:i386 (8:6.9.2.10+dfsg-2) over 
>> (8:6.9.2.10+dfsg-1) ...
>> Preparing to unpack .../imagemagick-6-common_8%3a6.9.2.10+dfsg-2_all.deb ...
>> Unpacking imagemagick-6-common (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) 
>> ...
>> dpkg: warning: unable to delete old directory '/etc/etc/ImageMagick-6': 
>> Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/etc': Directory not empty
>> Preparing to unpack .../libfftw3-single3_3.3.4-2+b1_i386.deb ...
>> Unpacking libfftw3-single3:i386 (3.3.4-2+b1) over (3.3.4-2) ...
>> Preparing to unpack .../libdebconfclient0_0.204_i386.deb ...
>> Unpacking libdebconfclient0:i386 (0.204) over (0.203) ...
>> Processing triggers for man-db (2.7.5-1) ...
>> Processing triggers for systemd (228-4+b1) ...
>> Processing triggers for libc-bin (2.22-0experimental1) ...
>> Processing triggers for doc-base (0.10.7) ...
>> Processing 1 changed doc-base file...
>> Registering documents with scrollkeeper...
>> Setting up libdebconfclient0:i386 (0.204) ...
>> Processing triggers for libc-bin (2.22-0experimental1) ...
>> Preparing to unpack .../isc-dhcp-client_4.3.3-7_i386.deb ...
>> Unpacking isc-dhcp-client (4.3.3-7) over (4.3.3-6) ...
>> Preparing to unpack .../isc-dhcp-common_4.3.3-7_i386.deb ...
>> Unpacking isc-dhcp-common (4.3.3-7) over (4.3.3-6) ...
>> Preparing to unpack .../libboost-iostreams1.58.0_1.58.0+dfsg-4.1+b1_i386.deb 
>> ...
>> Unpacking libboost-iostreams1.58.0:i386 (1.58.0+dfsg-4.1+b1) over 
>> (1.58.0+dfsg-4.1) ...
>> Preparing to unpack .../libgnutls30_3.4.8-3_i386.deb ...
>> Unpacking libgnutls30:i386 (3.4.8-3) over (3.4.8-2) ...
>> Preparing to unpack .../libasound2-data_1.1.0-1_all.deb ...
>> Unpacking libasound2-data (1.1.0-1) over (1.0.29-1) ...
>> Preparing to unpack .../libasound2_1.1.0-1_i386.deb ...
>> Unpacking libasound2:i386 (1.1.0-1) over (1.0.29-1) ...
>> Preparing to unpack .../alsa-utils_1.1.0-1_i386.deb ...
>> Unpacking alsa-utils (1.1.0-1) over (1.0.29-1+b1) ...
>> Preparing to unpack .../archives/bdf2psf_1.136_all.deb ...
>> Unpacking bdf2psf (1.136) over (1.135) ...
>> Preparing to unpack .../debian-policy_3.9.7.0_all.deb ...
>> Unpacking debian-policy (3.9.7.0) over (3.9.6.1) ...
>> Preparing to unpack .../dosfstools_3.99.0~git20160127-2_i386.deb ...
>> Unpacking dosfstools (3.99.0~git20160127-2) over (3.0.28-2) ...
>> Preparing to unpack .../imagemagick_8%3a6.9.2.10+dfsg-2_all.deb ...
>> dpkg-query: no packages found matching imagemagick:all
>> dpkg-query: package 'imagemagick' is not installed
>> Use dpkg --info (= dpkg-deb --info) to examine archive files,
>> and dpkg --contents (= dpkg-deb --contents) to list their contents.
>> dpkg-query: package 'imagemagick' is not installed
>> Use dpkg --info (= dpkg-deb --info) to examine archive files,
>> and dpkg --contents (= dpkg-deb --contents) to list their contents.
>> dpkg-query: package 'imagemagick' is not installed
>> Use dpkg --info (= dpkg-deb --info) to examine archive files,
>> [...]
>> Use dpkg --info (= dpkg-deb --info) to examine archive files,
>> and dpkg --contents (= dpkg-deb --contents) to list their contents.
>
>   This looks like a dpkg bug -- dpkg doesn't like so much switching
> from arch:any to arch:all, as far as I can tell.
>
>   BTW, you show a very long list of warning messages, did they stop by
> themselves ? If yes, I'm very curious why.
>
>> dpkg-maintscript-helper: error: directory '/usr/share/doc/imagemagick' 
>> contains files not owned by package imagemagick:all, cannot switch to symlink
>> dpkg: error processing archive 
>> /var/cache/apt/archives/imagemagick_8%3a6.9.2.10+dfsg-2_all.deb (--unpack):
>>  subprocess new pre-installation script returned error exit status 1
>> Preparing to unpack .../imagemagick-6.q16_8%3a6.9.2.10+dfsg-2_i386.deb ...
>> Unpacking imagemagick-6.q16 (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) ...
>> Preparing to unpack .../iso-codes_3.65-1_all.deb ...
>
>   Thanks !
>
>   Vincent
>
> ___
> Pkg-gmagick-im-team mailing list
> pkg-gmagick-im-t...@lists.alioth.debian.org
> 

Bug#813426: [Pkg-gmagick-im-team] Bug#813426: warning: /etc/alternatives/compare is dangling; it will be updated with best choice

[roucaries bastien]

On Wed, Feb 3, 2016 at 8:47 AM, Vincent Fourmond  wrote:
> control: severity -1 serious
>
>   Hello,
>
> On Wed, Feb 3, 2016 at 12:52 AM, 積丹尼 Dan Jacobson  wrote:
>>
>> What  a   mess.
>
>   I can only agree...
>
>> Preparing to unpack .../libmagickwand-6.q16-2_8%3a6.9.2.10+dfsg-2_i386.deb 
>> ...
>> Unpacking libmagickwand-6.q16-2:i386 (8:6.9.2.10+dfsg-2) over 
>> (8:6.9.2.10+dfsg-1) ...
>> Preparing to unpack .../imagemagick-6-doc_8%3a6.9.2.10+dfsg-2_all.deb ...
>> Unpacking imagemagick-6-doc (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) ...
>> Preparing to unpack .../imagemagick-doc_8%3a6.9.2.10+dfsg-2_all.deb ...
>> Unpacking imagemagick-doc (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) ...
>> Preparing to unpack .../libmagickcore-6.q16-2_8%3a6.9.2.10+dfsg-2_i386.deb 
>> ...
>> Unpacking libmagickcore-6.q16-2:i386 (8:6.9.2.10+dfsg-2) over 
>> (8:6.9.2.10+dfsg-1) ...
>> Preparing to unpack .../imagemagick-6-common_8%3a6.9.2.10+dfsg-2_all.deb ...
>> Unpacking imagemagick-6-common (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) 
>> ...
>> dpkg: warning: unable to delete old directory '/etc/etc/ImageMagick-6': 
>> Directory not empty
>> dpkg: warning: unable to delete old directory '/etc/etc': Directory not empty
>> Preparing to unpack .../libfftw3-single3_3.3.4-2+b1_i386.deb ...
>> Unpacking libfftw3-single3:i386 (3.3.4-2+b1) over (3.3.4-2) ...
>> Preparing to unpack .../libdebconfclient0_0.204_i386.deb ...
>> Unpacking libdebconfclient0:i386 (0.204) over (0.203) ...
>> Processing triggers for man-db (2.7.5-1) ...
>> Processing triggers for systemd (228-4+b1) ...
>> Processing triggers for libc-bin (2.22-0experimental1) ...
>> Processing triggers for doc-base (0.10.7) ...
>> Processing 1 changed doc-base file...
>> Registering documents with scrollkeeper...
>> Setting up libdebconfclient0:i386 (0.204) ...
>> Processing triggers for libc-bin (2.22-0experimental1) ...
>> Preparing to unpack .../isc-dhcp-client_4.3.3-7_i386.deb ...
>> Unpacking isc-dhcp-client (4.3.3-7) over (4.3.3-6) ...
>> Preparing to unpack .../isc-dhcp-common_4.3.3-7_i386.deb ...
>> Unpacking isc-dhcp-common (4.3.3-7) over (4.3.3-6) ...
>> Preparing to unpack .../libboost-iostreams1.58.0_1.58.0+dfsg-4.1+b1_i386.deb 
>> ...
>> Unpacking libboost-iostreams1.58.0:i386 (1.58.0+dfsg-4.1+b1) over 
>> (1.58.0+dfsg-4.1) ...
>> Preparing to unpack .../libgnutls30_3.4.8-3_i386.deb ...
>> Unpacking libgnutls30:i386 (3.4.8-3) over (3.4.8-2) ...
>> Preparing to unpack .../libasound2-data_1.1.0-1_all.deb ...
>> Unpacking libasound2-data (1.1.0-1) over (1.0.29-1) ...
>> Preparing to unpack .../libasound2_1.1.0-1_i386.deb ...
>> Unpacking libasound2:i386 (1.1.0-1) over (1.0.29-1) ...
>> Preparing to unpack .../alsa-utils_1.1.0-1_i386.deb ...
>> Unpacking alsa-utils (1.1.0-1) over (1.0.29-1+b1) ...
>> Preparing to unpack .../archives/bdf2psf_1.136_all.deb ...
>> Unpacking bdf2psf (1.136) over (1.135) ...
>> Preparing to unpack .../debian-policy_3.9.7.0_all.deb ...
>> Unpacking debian-policy (3.9.7.0) over (3.9.6.1) ...
>> Preparing to unpack .../dosfstools_3.99.0~git20160127-2_i386.deb ...
>> Unpacking dosfstools (3.99.0~git20160127-2) over (3.0.28-2) ...
>> Preparing to unpack .../imagemagick_8%3a6.9.2.10+dfsg-2_all.deb ...
>> dpkg-query: no packages found matching imagemagick:all
>> dpkg-query: package 'imagemagick' is not installed
>> Use dpkg --info (= dpkg-deb --info) to examine archive files,
>> and dpkg --contents (= dpkg-deb --contents) to list their contents.
>> dpkg-query: package 'imagemagick' is not installed
>> Use dpkg --info (= dpkg-deb --info) to examine archive files,
>> and dpkg --contents (= dpkg-deb --contents) to list their contents.
>> dpkg-query: package 'imagemagick' is not installed
>> Use dpkg --info (= dpkg-deb --info) to examine archive files,
>> [...]
>> Use dpkg --info (= dpkg-deb --info) to examine archive files,
>> and dpkg --contents (= dpkg-deb --contents) to list their contents.
>
>   This looks like a dpkg bug -- dpkg doesn't like so much switching
> from arch:any to arch:all, as far as I can tell.
>
>   BTW, you show a very long list of warning messages, did they stop by
> themselves ? If yes, I'm very curious why.
>
>> dpkg-maintscript-helper: error: directory '/usr/share/doc/imagemagick' 
>> contains files not owned by package imagemagick:all, cannot switch to symlink
>> dpkg: error processing archive 
>> /var/cache/apt/archives/imagemagick_8%3a6.9.2.10+dfsg-2_all.deb (--unpack):
>>  subprocess new pre-installation script returned error exit status 1
>> Preparing to unpack .../imagemagick-6.q16_8%3a6.9.2.10+dfsg-2_i386.deb ...
>> Unpacking imagemagick-6.q16 (8:6.9.2.10+dfsg-2) over (8:6.9.2.10+dfsg-1) ...
>> Preparing to unpack .../iso-codes_3.65-1_all.deb ...


This one is #813455

Bastien

>   Thanks !
>
>   Vincent
>
> ___
> Pkg-gmagick-im-team mailing list
> pkg-gmagick-im-t...@lists.alioth.debian.org
> 

Bug#813584: libelf: Do not ship in stretch

[Laurent Bigonville]

Source: libelf
Version: 0.8.13-5
Severity: serious
Tags: stretch sid

Hi,

src:libelf doesn't seems to be used by any other packages in debian
(except src:elk on i386 because it FTBFS).

It is dead upstream and superseeded by src:elfutils.

It could probably be removed completely from the archive, but I'll let
somebody else decide for this.

Cheers,

Laurent Bigonville

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

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

Bug#808821: asymptote: failing to build on mips

[Norbert Preining]

Hi Julian,

> It turns out that it is a compiler bug, or at least it is as far as we
> can tell: the code works fine with -O0 but bombs with -O1.  See
> https://sourceforge.net/p/asymptote/bugs/205/ for the full discussion.

BIG BIG BIG THANKS! I have followed the bug report from the very
beginning, and you have done an awful great job. Big thanks.

> I guess I should report this upstream - I guess against g++?  But
> finding a minimal example will be hard.

>From my experience with gcc bugs is that nobody cares as long as you
cannot reproduce it with the very very very latest gcc (6?) and
I guess you don't want to go to that length. But feel free.

> compile fine under MIPS, so please do upgrade to version 2.37.  This,

I just checked, not released by now, but as soon as it is I will update
the Debian repository.

Big thanks again, and also thanks for the heads up about the elisp patch.

All the best

Norbert


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

Processed: Versions

[Debian Bug Tracking System]

Processing control commands:

> found -1 python-cryptography/1.2.1-1
Bug #813597 [python-cryptography] python-openssl: exception when importing 
OpenSSL
Marked as found in versions python-cryptography/1.2.1-1.
> tag -1 + moreinfo
Bug #813597 [python-cryptography] python-openssl: exception when importing 
OpenSSL
Added tag(s) moreinfo.

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

Processed: fixed 791195 in 3.3.2~r61000-3.1

[Debian Bug Tracking System]

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

> fixed 791195 3.3.2~r61000-3.1
Bug #791195 [src:lttoolbox] lttoolbox: library transition may be needed when 
GCC 5 is the default
Marked as fixed in versions lttoolbox/3.3.2~r61000-3.1.
> thanks
Stopping processing here.

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

Bug#813068: marked as done (neutron-linuxbridge-agent: fails to upgrade from 'sid' - trying to overwrite /etc/neutron/plugins/ml2/linuxbridge_agent.ini)

[Debian Bug Tracking System]

Your message dated Wed, 03 Feb 2016 17:41:09 +
with message-id 
and subject line Bug#813068: fixed in neutron 2:8.0.0~b2-3
has caused the Debian Bug report #813068,
regarding neutron-linuxbridge-agent: fails to upgrade from 'sid' - trying to 
overwrite /etc/neutron/plugins/ml2/linuxbridge_agent.ini
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.)


-- 
813068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: neutron-linuxbridge-agent
Version: 1:8.0.0~b2-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Unpacking neutron-linuxbridge-agent (1:8.0.0~b2-2) over (1:7.0.0-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/neutron-linuxbridge-agent_1%3a8.0.0~b2-2_all.deb 
(--unpack):
   trying to overwrite '/etc/neutron/plugins/ml2/linuxbridge_agent.ini', which 
is also in package neutron-common 1:7.0.0-4
  Running in chroot, ignoring request.
  invoke-rc.d: policy-rc.d denied execution of start.


cheers,

Andreas


neutron-linuxbridge-agent_1:8.0.0~b2-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: neutron
Source-Version: 2:8.0.0~b2-3

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated neutron 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: Thu, 28 Jan 2016 07:34:12 +
Source: neutron
Binary: python-neutron neutron-server neutron-common neutron-plugin-nec-agent 
neutron-l3-agent neutron-dhcp-agent neutron-metadata-agent 
neutron-metering-agent neutron-openvswitch-agent neutron-linuxbridge-agent 
neutron-plugin-linuxbridge-agent neutron-plugin-openvswitch-agent
Architecture: source all
Version: 2:8.0.0~b2-3
Distribution: experimental
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 neutron-common - OpenStack virtual network service - common files
 neutron-dhcp-agent - OpenStack virtual network service - DHCP agent
 neutron-l3-agent - OpenStack virtual network service - l3 agent
 neutron-linuxbridge-agent - OpenStack virtual network service - Linux bridge 
agent
 neutron-metadata-agent - OpenStack virtual network service - metadata agent
 neutron-metering-agent - OpenStack virtual network service - metering agent
 neutron-openvswitch-agent - OpenStack virtual network service - Open vSwitch 
agent
 neutron-plugin-linuxbridge-agent - transitional dummy package for switching to 
Neutron Linuxbridge a
 neutron-plugin-nec-agent - OpenStack virtual network service - NEC agent
 neutron-plugin-openvswitch-agent - transitional dummy package for switching to 
Neutron OpenVswitch a
 neutron-server - OpenStack virtual network service - server
 python-neutron - OpenStack virtual network service - Python library
Closes: 810728 811530 813068
Changes:
 neutron (2:8.0.0~b2-3) experimental; urgency=medium
 .
   * Bumped EPOCH to align with Ubuntu.
   * Allow unit test to fail, because they do in Trusty.
   * Do not -X/usr/bin when calling dh_install.
   * Fixed auth_protocol to be http and not https by default.
   * Drop Provides: argparse (Closes: #810728).
   * neutron-linuxbridge-agent Breaks + Replaes older neutron-common
 (Closes: #813068).
   * New pt_BR.po debconf translation (Closes: #811530).
Checksums-Sha1:
 07684c4164ffeb76afce5edec19734a90d12b716 4473 neutron_8.0.0~b2-3.dsc
 c52a501b3948a07dc0ac1a420fb3211fa6f3acd7 39968 

Bug#799774:

[Jurica Stanojkovic]

Hello,

This issue is resolved upstream.
https://github.com/node-xmpp/node-expat/commit/c129cb37c6f04f09190a3912f44f3976b813b973

With changes from this commit package does build successfully on amd64 and i386.
Tests pass.
Test results:
gyp info ok 
NODE_DISABLE_COLORS=1 nodejs test.js
···-··· ✓ OK » 30 honored ∙ 1 pending (1.010s) 
  touch debian/stamp-node-gyp-build


On mipsel package does build, but later tests fail:
Test results:

gyp info ok 
NODE_DISABLE_COLORS=1 nodejs test.js
···-···(node) util.print is deprecated. Use console.log 
instead.

✗ Errored » callback not fired 
  in stop and resume 
  in node-expat 
  in undefined✗ Errored » callback not fired 
  in Stream interface read file 
  in node-expat 
  in undefined(node) util.puts is deprecated. Use console.log instead.
✗ Errored » 26 honored ∙ 1 errored ∙ 1 pending ∙ 4 dropped

debian/rules:52: recipe for target 'debian/stamp-node-gyp-build' failed

I will look at this issue further.

Please consider including this change.

If needed, I could create a patch with changes from upstream.

Regards,
Jurica

Processed (with 2 errors): Found in versions

[Debian Bug Tracking System]

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

> notfound 818473 alsa-utils/1.0.29-1
Failed to remove found on 818473: Unable to read any bugs successfully.

> notfound 813479 alsa-utils/1.0.29-1
Bug #813479 [alsa-utils] file conflicts without conflicts: header
Bug #813473 [alsa-utils] alsa-utils: Upgrade failed with bacula-console-qt 
installed
Bug #813563 [alsa-utils] alsa-utils: Overwrite files from unrelated package
No longer marked as found in versions alsa-utils/1.0.29-1.
No longer marked as found in versions alsa-utils/1.0.29-1.
No longer marked as found in versions alsa-utils/1.0.29-1.
> notfound 813563 alsa-utils/1.0.29-1
Bug #813563 [alsa-utils] alsa-utils: Overwrite files from unrelated package
Bug #813473 [alsa-utils] alsa-utils: Upgrade failed with bacula-console-qt 
installed
Bug #813479 [alsa-utils] file conflicts without conflicts: header
Ignoring request to alter found versions of bug #813563 to the same values 
previously set
Ignoring request to alter found versions of bug #813473 to the same values 
previously set
Ignoring request to alter found versions of bug #813479 to the same values 
previously set
> affects 818473 + bacula-console-qt bareos-bat
Failed to mark 818473 as affecting package(s): Unable to read any bugs 
successfully.

> --
Stopping processing here.

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

Processed: Found in versions

[Debian Bug Tracking System]

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

> notfound 813473 alsa-utils/1.0.29-1
Bug #813473 [alsa-utils] alsa-utils: Upgrade failed with bacula-console-qt 
installed
Bug #813479 [alsa-utils] file conflicts without conflicts: header
Bug #813563 [alsa-utils] alsa-utils: Overwrite files from unrelated package
Ignoring request to alter found versions of bug #813473 to the same values 
previously set
Ignoring request to alter found versions of bug #813479 to the same values 
previously set
Ignoring request to alter found versions of bug #813563 to the same values 
previously set
> affects 813473 + bacula-console-qt bareos-bat
Bug #813473 [alsa-utils] alsa-utils: Upgrade failed with bacula-console-qt 
installed
Bug #813479 [alsa-utils] file conflicts without conflicts: header
Bug #813563 [alsa-utils] alsa-utils: Overwrite files from unrelated package
Added indication that 813473 affects bacula-console-qt and bareos-bat
Added indication that 813479 affects bacula-console-qt and bareos-bat
Added indication that 813563 affects bacula-console-qt and bareos-bat
> --
Stopping processing here.

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

Processed: bug 813568 is forwarded to https://github.com/guzzle/guzzle3/issues/67

[Debian Bug Tracking System]

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

> forwarded 813568 https://github.com/guzzle/guzzle3/issues/67
Bug #813568 [src:php-guzzle] php-guzzle: FTBFS: 
DefaultCacheStorageTest::testCachesRequests   strpos() expects parameter 1 to 
be string, array given
Set Bug forwarded-to-address to 'https://github.com/guzzle/guzzle3/issues/67'.
> thanks
Stopping processing here.

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

Bug#813601: linux-image-3.16: kernel panic when umounting rootfs

[Nicolas Dichtel]

Package: src:linux
Version: 3.16.7-ckt11-1+deb8u6
Severity: critical
Tags: patch
Justification: breaks the whole system

Dear Maintainer,

This upstream commit is missing:
da362b09e42e umount: Do not allow unmounting rootfs.
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=da362b09e42e

The commit log of this patch explains how to reproduce the kernel panic (see 
below).

Note that this patch depends on
5ff9d8a65ce8 vfs: Lock in place mounts from more privileged users
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5ff9d8a65ce8

Regards,
Nicolas


-- 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-ckt11-1+deb8u6 (2015-11-09)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=/dev/mapper/6WIND-debian8 ro 
console=ttyS0,115200n8 quiet

** Not tainted

** Kernel log:
[0.307242] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[0.307253] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[0.307264] intel_idle: does not run on family 6 model 60
[0.307286] GHES: HEST is not enabled!
[0.307371] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[0.329356] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 
16550A
[0.351248] 00:06: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 
16550A
[0.351502] Linux agpgart interface v0.103
[0.351588] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 
0x60,0x64 irq 1,12
[0.352073] serio: i8042 KBD port at 0x60,0x64 irq 1
[0.352077] serio: i8042 AUX port at 0x60,0x64 irq 12
[0.352274] mousedev: PS/2 mouse device common for all mice
[0.352437] input: AT Translated Set 2 keyboard as 
/devices/platform/i8042/serio0/input/input0
[0.352569] rtc_cmos 00:00: RTC can wake from S4
[0.352748] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
[0.352818] rtc_cmos 00:00: alarms up to one day, 114 bytes nvram, hpet irqs
[0.352848] ledtrig-cpu: registered to indicate activity on CPUs
[0.352913] AMD IOMMUv2 driver by Joerg Roedel 
[0.352914] AMD IOMMUv2 functionality not available on this system
[0.352966] TCP: cubic registered
[0.353150] NET: Registered protocol family 10
[0.353323] mip6: Mobile IPv6
[0.353326] NET: Registered protocol family 17
[0.353330] mpls_gso: MPLS GSO support
[0.353567] registered taskstats version 1
[0.353776] rtc_cmos 00:00: setting system clock to 2016-02-03 14:33:55 UTC 
(1454510035)
[0.353809] PM: Hibernation image not present or could not be loaded.
[0.354519] Freeing unused kernel memory: 1204K (818ee000 - 
81a1b000)
[0.354521] Write protecting the kernel read-only data: 8192k
[0.355897] Freeing unused kernel memory: 924K (880001519000 - 
88000160)
[0.356232] Freeing unused kernel memory: 216K (8800017ca000 - 
88000180)
[0.363665] systemd-udevd[65]: starting version 215
[0.364044] random: systemd-udevd urandom read with 1 bits of entropy 
available
[0.372312] SCSI subsystem initialized
[0.376219] libata version 3.00 loaded.
[0.379153] Floppy drive(s): fd0 is 1.44M
[0.390411] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[0.390939] ata_piix :00:01.1: version 2.13
[0.391593] virtio-pci :00:03.0: irq 40 for MSI/MSI-X
[0.391603] virtio-pci :00:03.0: irq 41 for MSI/MSI-X
[0.391612] virtio-pci :00:03.0: irq 42 for MSI/MSI-X
[0.391742] scsi0 : ata_piix
[0.391844] scsi1 : ata_piix
[0.391882] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc020 irq 14
[0.391883] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc028 irq 15
[0.392532] FDC 0 is a S82078B
[0.548567] ata2.01: NODEV after polling detection
[0.548740] ata1.01: NODEV after polling detection
[0.548943] ata2.00: ATAPI: QEMU DVD-ROM, 2.3.0, max UDMA/100
[0.549085] ata1.00: ATA-7: QEMU HARDDISK, 2.3.0, max UDMA/100
[0.549086] ata1.00: 62914560 sectors, multi 16: LBA48 
[0.549551] ata2.00: configured for MWDMA2
[0.549639] ata1.00: configured for MWDMA2
[0.549763] scsi 0:0:0:0: Direct-Access ATA  QEMU HARDDISK0
PQ: 0 ANSI: 5
[0.550243] scsi 1:0:0:0: CD-ROMQEMU QEMU DVD-ROM 2.3. 
PQ: 0 ANSI: 5
[0.553232] sd 0:0:0:0: [sda] 62914560 512-byte logical blocks: (32.2 
GB/30.0 GiB)
[0.553251] sd 0:0:0:0: [sda] Write Protect is off
[0.553253] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[0.553259] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[0.553858]  sda: sda1
[0.553979] sd 0:0:0:0: [sda] Attached SCSI disk
[0.560526] sr0: scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[0.560527] cdrom: Uniform CD-ROM driver Revision: 3.20
[0.560626] sr 1:0:0:0: Attached scsi CD-ROM sr0
[0.561096] sd 0:0:0:0: Attached 

Bug#813611: Passwords are stored as MD5

[Sven Bartscher]

Package: simpleid
Version: 0.8.1-14
Severity: grave
Tags: security

The identity files (in /var/lib/simpleid/identities) expect user
passwords to be given as MD5 hashes of the actual passwords, but MD5
is generally considered broken and should probably not be used to
store user passwords.

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

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

Processed: found 813054 in 43.0.4-1

[Debian Bug Tracking System]

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

> # does not seem specific to 44.0
> found 813054 43.0.4-1
Bug #813054 [iceweasel] Evil licence
Marked as found in versions iceweasel/43.0.4-1.
> thanks
Stopping processing here.

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

Bug#813597: notfound 813597 in python-cryptography/1.2.1-1, closing 813597

[Tristan Seligmann]

notfound 813597 python-cryptography/1.2.1-1
close 813597 
thanks

Processed: found 788721 in 43.0.4-1

[Debian Bug Tracking System]

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

> # does not seem specific to 39.0~b1 and 44.0
> found 788721 43.0.4-1
Bug #788721 [src:iceweasel] [src:iceweasel] Some sources are not included in 
your package
Marked as found in versions iceweasel/43.0.4-1.
> thanks
Stopping processing here.

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

Processed: forward

[Debian Bug Tracking System]

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

> forwarded 812668 baue...@gmail.com
Bug #812668 [mailfilter] mailfilter: FTBFS - error: no match for 'operator='
Set Bug forwarded-to-address to 'baue...@gmail.com'.
> --
Stopping processing here.

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

Processed: Found in versions

[Debian Bug Tracking System]

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

> found 813473 alsa-utils/1.1.0-1
Bug #813473 [alsa-utils] alsa-utils: Upgrade failed with bacula-console-qt 
installed
Bug #813479 [alsa-utils] file conflicts without conflicts: header
Bug #813563 [alsa-utils] alsa-utils: Overwrite files from unrelated package
Marked as found in versions alsa-utils/1.1.0-1.
Marked as found in versions alsa-utils/1.1.0-1.
Marked as found in versions alsa-utils/1.1.0-1.
> --
Stopping processing here.

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