Bug#778680: marked as done (mysql-ocaml: Build-Depends on libmysqlclient15-dev which will no longer exists)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2015 05:48:58 +
with message-id 
and subject line Bug#778680: fixed in mysql-ocaml 1.2.0-2
has caused the Debian Bug report #778680,
regarding mysql-ocaml: Build-Depends on libmysqlclient15-dev which will no 
longer exists
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.)


-- 
778680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-ocaml
Version: 1.1.2-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu vivid ubuntu-patch



*** /tmp/tmphq3TA_/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

This will only affect you post-jessie, when we move Debian to MySQL 5.6
also.

  * Build-Depend on libmysqlclient-dev instead of libmysqlclient15-dev
specifically, since that was replaced by libmysqlclient18 in the transition
to MySQL 5.5 and is no longer provided by MySQL 5.6.


Thanks for considering the patch.

*** /tmp/tmphq3TA_/mysql-ocaml_1.1.2-3ubuntu1.debdiff
diff -Nru mysql-ocaml-1.1.2/debian/changelog mysql-ocaml-1.1.2/debian/changelog
diff -Nru mysql-ocaml-1.1.2/debian/control mysql-ocaml-1.1.2/debian/control
--- mysql-ocaml-1.1.2/debian/control2013-12-08 14:03:54.0 +
+++ mysql-ocaml-1.1.2/debian/control2015-02-18 12:29:51.0 +
@@ -7,7 +7,7 @@
  Mehdi Dogguy 
 Build-Depends:
  debhelper (>= 7.0.50~),
- libmysqlclient15-dev,
+ libmysqlclient-dev,
  dh-ocaml (>= 0.9),
  ocaml-nox (>= 3.11),
  camlp4 (>= 3.11),

HTH,

Robie


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: mysql-ocaml
Source-Version: 1.2.0-2

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

Debian distribution maintenance software
pp.
Mehdi Dogguy  (supplier of updated mysql-ocaml 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, 16 Jul 2015 19:52:44 +
Source: mysql-ocaml
Binary: libmysql-ocaml libmysql-ocaml-dev
Architecture: source amd64
Version: 1.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Mehdi Dogguy 
Description:
 libmysql-ocaml - OCaml bindings for MySql (runtime package)
 libmysql-ocaml-dev - OCaml bindings for MySql (development package)
Closes: 778680
Changes:
 mysql-ocaml (1.2.0-2) unstable; urgency=medium
 .
   * Team upload upload.
   * Build-Depends on libmysqlclient-dev instead of libmysqlclient15-dev
 (Closes: #778680).
Checksums-Sha1:
 3e42e7f23c1541e427035640b793ce78e93dfbed 2156 mysql-ocaml_1.2.0-2.dsc
 50a21812956e161273bf0b695a9c8f5e1eb5b1a6 3680 mysql-ocaml_1.2.0-2.debian.tar.xz
 be021ed9369fc9e6cea80d67341efe6955e703b4 51384 
libmysql-ocaml-dev_1.2.0-2_amd64.deb
 8841fc17dc6fb6526642cf42bb176bb078661a67 14964 libmysql-ocaml_1.2.0-2_amd64.deb
Checksums-Sha256:
 919e8415b8d9906a0fd35c974589592d280f4d492ebd85dd2b472efc0ceba37c 2156 
mysql-ocaml_1.2.0-2.dsc
 ef52cf1d76a274baa851028773584a11f23f39f5a28b759436895bb2ec0dc148 3680 
mysql-ocaml_1.2.0-2.debian.tar.xz
 c00ff245715abe2cde3bf11395c4654846a2df9964b23b6bc9b6b7f2e5364a84 51384 
libmysql-ocaml-dev_1.2.0-2_amd64.deb
 8240f957fe2106cdf21418fa0a4fd7297acaf9ccf0a8044f265a8981e02a8d19 14964 
libmysql-ocaml_1.2.0-2_amd64.deb
Files:
 8d08ebf22c8045b68b382f52b0ddca94 2156 ocaml optional mysql-ocaml_1.2.0-2.dsc
 a70b3094ba1bdeb66b392e36be0019bb 3680 ocaml optional 
mysql-ocaml_1.2.0-2.debian.tar.xz
 6f41aef680f40a036b7358335e6a237f 51384 ocaml optional 
libmysql-ocaml-dev_1.2.0-2_amd64.deb
 815c117fe3b6c8939f1bb22b16720d71 14964 ocaml optional 
libmysql-ocaml_1.2.0-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJVqLFAAAoJEDO+GgqMLtj/EvkQAN3cPJhYodQ8ebVFhtk8N370
k7I5mZlEd0OqhDkmUk/vGZpj0s4ULlhydKooYH/FiSuKXpnY6fdLQXwFQ4CyMWqn
ejw/3H8e1WXO5NbrQn8ElilidfTyBbDTklfpjQj/XaSqZ+qX3efcK43PSfoKTQRk
q/YLmsaHmGk2Gi/0CVKEHO3B9QKVfUDAbcs63XZ9k5tzKHDIwp/IJTqm0747h/rT
C0EpfAAh1M/4OZktV/qw3j8ct7CowX+dR0kRPAUASfP5RfLcMPPM27hp1RzyTOQK
2Po+EQhdspTrKwjFkPWe

Processed: reassign 770229 to src:cyassl, found 770229 in 2.9.4+dfsg-3 ..., cloning 770229 ...

[Debian Bug Tracking System]

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

> reassign 770229 src:cyassl
Bug #770229 {Done: Felix Lechner } [wolfssl] 
CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904
Bug reassigned from package 'wolfssl' to 'src:cyassl'.
Ignoring request to alter found versions of bug #770229 to the same values 
previously set
Ignoring request to alter fixed versions of bug #770229 to the same values 
previously set
> found 770229 2.9.4+dfsg-3
Bug #770229 {Done: Felix Lechner } [src:cyassl] 
CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904
Marked as found in versions cyassl/2.9.4+dfsg-3 and reopened.
> retitle 770229 cyassl: CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 
> CVE-2014-2904 CVE-2014-6491 CVE-2014-6494 CVE-2014-6495 CVE-2014-6496 
> CVE-2014-6500
Bug #770229 [src:cyassl] CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904
Changed Bug title to 'cyassl: CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 
CVE-2014-2904 CVE-2014-6491 CVE-2014-6494 CVE-2014-6495 CVE-2014-6496 
CVE-2014-6500' from 'CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904'
> clone 770229 -1
Bug #770229 [src:cyassl] cyassl: CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 
CVE-2014-2904 CVE-2014-6491 CVE-2014-6494 CVE-2014-6495 CVE-2014-6496 
CVE-2014-6500
Bug 770229 cloned as bug 792646
> reassign -1 src:wolfssl
Bug #792646 [src:cyassl] cyassl: CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 
CVE-2014-2904 CVE-2014-6491 CVE-2014-6494 CVE-2014-6495 CVE-2014-6496 
CVE-2014-6500
Bug reassigned from package 'src:cyassl' to 'src:wolfssl'.
No longer marked as found in versions cyassl/2.9.4+dfsg-3.
Ignoring request to alter fixed versions of bug #792646 to the same values 
previously set
> retitle -1 wolfssl: CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904
Bug #792646 [src:wolfssl] cyassl: CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 
CVE-2014-2904 CVE-2014-6491 CVE-2014-6494 CVE-2014-6495 CVE-2014-6496 
CVE-2014-6500
Changed Bug title to 'wolfssl: CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 
CVE-2014-2904' from 'cyassl: CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 
CVE-2014-2904 CVE-2014-6491 CVE-2014-6494 CVE-2014-6495 CVE-2014-6496 
CVE-2014-6500'
> fixed -1 3.4.8+dfsg-1
Bug #792646 [src:wolfssl] wolfssl: CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 
CVE-2014-2904
Marked as fixed in versions wolfssl/3.4.8+dfsg-1.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791467: plowshare: javascript usage puts user at risk of remote code execution

[Carl Suster]

Yes, this is exactly what I'm doing if you take a look at the blocking bugs
for this present bug. I've patched the package to remove javascript support
and I'm waiting on a mentor to upload to unstable and then approval to
upload to stable.

I'll work out if there is a viable alternative fix in the future.

Carl

Bug#784350: marked as done (node-gaze unusable due to missing dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 17 Jul 2015 03:28:28 +
with message-id 
and subject line Bug#792425: Removed package(s) from unstable
has caused the Debian Bug report #784350,
regarding node-gaze unusable due to missing dependencies
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.)


-- 
784350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784350
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-gaze
Version: 0.6.4-1
Severity: grave
Justification: renders package unusable

The node-gaze package currently in testing & unstable is unusable due to
missing dependencies.

npm2deb created packaging that only depended on node-globule (>= 0.1.0),
but that missed the addional dependencies listed in the package.json.

The missing dependencies were added to the packaging in git, but the
fixed revision cannot be uploaded before the missing dependencies pass
the NEW queue:

 * node-nextback (>= 0.1.0)
   http://ftp-master.debian.org/new/node-nextback_0.1.0-1.html
 
 * node-absolute-path (>= 0.0.0)
   http://ftp-master.debian.org/new/node-absolute-path_0.0.0-1.html

This RC should get node-gaze removed from and out of testing until its
dependencies are in order.

The missing dependencies are the cause for the failing CI checks:

 http://ci.debian.net/packages/n/node-gaze/unstable/amd64/
--- End Message ---
--- Begin Message ---
Version: 0.6.4-1+rm

Dear submitter,

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#774149: Workaround working

[shirish शिरीष]

Dear Rogério,
I would simply say go ahead with your plan. If you are able to resolve
the issues with a new release, then nothing like it. I am already
subscribed to the package in case a new one comes out :)

Although at my end, it is also ntfs which shows the same problem as
external usb-hdd.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: found 791751 in 2.4.40+dfsg-2, closing 791751, found 790806 in 4:5.3.2-1 ..., tagging 791770 ...

[Debian Bug Tracking System]

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

> # spurious build failure, does not affect stable, mark as found in some 
> version, close without fixed version, otherwise the bts gets confused
> found 791751 2.4.40+dfsg-2
Bug #791751 {Done: Ryan Tandy } [openldap] openldap: Fails to 
build on mipsel
There is no source info for the package 'openldap' at version '2.4.40+dfsg-2' 
with architecture ''
Unable to make a source version for version '2.4.40+dfsg-2'
Marked as found in versions 2.4.40+dfsg-2; no longer marked as fixed in 
versions 2.4.40+dfsg-2 and reopened.
> close 791751
Bug #791751 [openldap] openldap: Fails to build on mipsel
Marked Bug as done
> found 790806 4:5.3.2-1
Bug #790806 {Done: Maximiliano Curia } [kinfocenter] 
kinfocenter: installation fails due to conflict with kde-l10n-engb
Marked as found in versions kinfocenter/4:5.3.2-1.
> notfound 790806 kde-workspace/4:4.11.13-2
Bug #790806 {Done: Maximiliano Curia } [kinfocenter] 
kinfocenter: installation fails due to conflict with kde-l10n-engb
No longer marked as found in versions kde-workspace/4:4.11.13-2.
> tags 791770 + stretch sid
Bug #791770 [dhelp] dhelp: Depends on obsolete ruby-bdb
Added tag(s) sid and stretch.
> # verified in local rebuilds that the packages ftbfs in sid but not in jessie
> found 788696 2.1.4-1
Bug #788696 {Done: Jérémy Lal } [node-iconv] node-iconv: 
call of overloaded ‘New(long unsigned int&)’ is ambiguous
Marked as found in versions node-iconv/2.1.4-1.
> tags 787643 + sid stretch
Bug #787643 {Done: Clint Adams } [src:haskell-hopenpgp-tools] 
haskell-hopenpgp-tools: FTBFS: Module `Data.Conduit.OpenPGP.Filter' does not 
export `Exp(..)'
Added tag(s) stretch and sid.
> tags 788696 + sid stretch
Bug #788696 {Done: Jérémy Lal } [node-iconv] node-iconv: 
call of overloaded ‘New(long unsigned int&)’ is ambiguous
Added tag(s) sid and stretch.
> tags 790094 + sid stretch
Bug #790094 [flush] FTBFS: glibmm incompatability(?): macro "bind_property" 
requires 4 arguments, but only 3 given
Added tag(s) sid and stretch.
> tags 790776 + sid stretch
Bug #790776 [openscad] FTBFS: error adding symbols: DSO missing from command 
line
Added tag(s) sid and stretch.
> tags 789978 + sid stretch
Bug #789978 {Done: Julian Wollrath } [src:lua-discount] 
FTBFS: lua5.2: test_discount.lua:49: attempt to index global 'lu' (a nil value)
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
787643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787643
788696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788696
789978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789978
790094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790094
790776: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790776
790806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790806
791751: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791751
791770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 769905 wolfssl
Bug #769905 {Done: Felix Lechner } [src:wolfssl] 
cyassl: please disable SSLv3
Bug reassigned from package 'src:wolfssl' to 'wolfssl'.
Ignoring request to alter found versions of bug #769905 to the same values 
previously set
Ignoring request to alter fixed versions of bug #769905 to the same values 
previously set
> reassign 770229 wolfssl
Bug #770229 {Done: Felix Lechner } [src:wolfssl] 
CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904
Bug reassigned from package 'src:wolfssl' to 'wolfssl'.
Ignoring request to alter found versions of bug #770229 to the same values 
previously set
Ignoring request to alter fixed versions of bug #770229 to the same values 
previously set
>
End of message, stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 770229 src:wolfssl
Bug #770229 {Done: Felix Lechner } [wolfssl] 
CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904
Bug reassigned from package 'wolfssl' to 'src:wolfssl'.
Ignoring request to alter found versions of bug #770229 to the same values 
previously set
Ignoring request to alter fixed versions of bug #770229 to the same values 
previously set
>
End of message, stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 770229 wolfssl
Bug #770229 {Done: Felix Lechner } [src:cyassl] 
CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904
Bug reassigned from package 'src:cyassl' to 'wolfssl'.
Ignoring request to alter found versions of bug #770229 to the same values 
previously set
No longer marked as fixed in versions wolfssl/3.4.8+dfsg-1.
>
End of message, stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#789942: mapnik-vector-tile: FTBFS with mapnik 3.0(?): mapnik/graphics.hpp: No such file or directory

[Sebastiaan Couwenberg]

On 06/25/2015 07:49 PM, Sebastiaan Couwenberg wrote:
> On 06/25/2015 03:53 PM, Chris West (Faux) wrote:
>> Package: mapnik-vector-tile
>> Version: 0.5.1+dfsg-1.3
>> [...]
>> I believe this is due to libmapnik-dev pulling in mapnik 3.0.
> 
> For mapnik 3 support mapnik-vector-tile v0.7 or later is required,
> Jérémy updated the packaging in git to 0.8.0 recently but this hasn't
> been uploaded yet. Uploading that probably resolves this issue.

mapnik-vector-tile (0.8.0+dfsg-1) fails to build with mapnik
(3.0.0+ds-2) as well. It's missing clipper.hpp:

 In file included from ../src/vector_tile_processor.cpp:2:0:
 ../src/vector_tile_processor.ipp:38:23: fatal error: clipper.hpp: No
such file or directory
  #include "clipper.hpp"
   ^
 compilation terminated.
 gyp/mapnik_vector_tile_impl.target.mk:152: recipe for target
'Release/obj.target/mapnik_vector_tile_impl/src/vector_tile_processor.o'
failed

This appear to be provided by an external dependency, that was added to
the Makefile in v0.8.1. That release also adds a dependency on a MapBox
specific pbf.hpp, so there are two missing build dependencies for
mapnik-vector-tile:

 1. https://github.com/mapnik/clipper
 2. https://github.com/mapbox/pbf.hpp

These build dependencies will need to be packaged before
mapnik-vector-tile can be fixed.

Kind Regards,

Bas

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790274: python-pyftpdlib: FTBFS: Failure in test_on_incomplete_file_sent

[Andreas Beckmann]

Followup-For: Bug #790274

Similar failure while rebuilding in a clean jessie pbuilder environment:

[...]
   debian/rules override_dh_auto_test
make[1]: Entering directory '/tmp/buildd/python-pyftpdlib-1.2.0'
PYTHONPATH=. python test/test_ftpd.py
Traceback (most recent call last):
  File "test/test_ftpd.py", line 63, in 
import pyftpdlib.__main__
  File "/tmp/buildd/python-pyftpdlib-1.2.0/pyftpdlib/__main__.py", line 45, in 

from pyftpdlib.servers import FTPServer
  File "/tmp/buildd/python-pyftpdlib-1.2.0/pyftpdlib/servers.py", line 521, in 

class MultiprocessFTPServer(_SpawnerBase):
  File "/tmp/buildd/python-pyftpdlib-1.2.0/pyftpdlib/servers.py", line 525, in 
MultiprocessFTPServer
_lock = multiprocessing.Lock()
  File "/usr/lib/python2.7/multiprocessing/__init__.py", line 176, in Lock
return Lock()
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 147, in 
__init__
SemLock.__init__(self, SEMAPHORE, 1, 1)
  File "/usr/lib/python2.7/multiprocessing/synchronize.py", line 75, in __init__
sl = self._semlock = _multiprocessing.SemLock(kind, value, maxvalue)
OSError: [Errno 13] Permission denied
debian/rules:8: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/tmp/buildd/python-pyftpdlib-1.2.0'
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790256: marked as done (libsysactivity: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 22:34:02 +
with message-id 
and subject line Bug#790256: fixed in libsysactivity 0.6.5-5
has caused the Debian Bug report #790256,
regarding libsysactivity: FTBFS: Test failures
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.)


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

>From my pbuilder build log:

...
Linking C executable swap
cd /tmp/buildd/libsysactivity-0.6.5/build/test && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/swap.dir/link.txt --verbose=1
/usr/bin/cc  -g -O2 -fPIE -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG  -fPIE -pie 
-Wl,-z,relro -Wl,-z,now CMakeFiles/swap.dir/test_swap.c.o  -o swap -rdynamic 
../src/Linux/libsysactivity.so.0.6.5 -lpthread -lm 
make[4]: Leaving directory '/tmp/buildd/libsysactivity-0.6.5/build'
/usr/bin/cmake -E cmake_progress_report 
/tmp/buildd/libsysactivity-0.6.5/build/CMakeFiles  6
[100%] Built target swap
make[3]: Leaving directory '/tmp/buildd/libsysactivity-0.6.5/build'
/usr/bin/cmake -E cmake_progress_start 
/tmp/buildd/libsysactivity-0.6.5/build/CMakeFiles 0
make[2]: Leaving directory '/tmp/buildd/libsysactivity-0.6.5/build'
cd build && LD_LIBRARY_PATH="/tmp/buildd/libsysactivity-0.6.5/build/src/Linux" 
ctest -V --force-new-ctest-process -E "^data_storage|disk|process\$"
UpdateCTestConfiguration  from 
:/tmp/buildd/libsysactivity-0.6.5/build/DartConfiguration.tcl
UpdateCTestConfiguration  from 
:/tmp/buildd/libsysactivity-0.6.5/build/DartConfiguration.tcl
Test project /tmp/buildd/libsysactivity-0.6.5/build
Constructing a list of tests
Done constructing a list of tests
Checking test dependency graph...
Checking test dependency graph end
test 1
Start 1: cpu

1: Test command: /tmp/buildd/libsysactivity-0.6.5/build/test/cpu
1: Test timeout computed to be: 9.99988e+06
1: /tmp/buildd/libsysactivity-0.6.5/test/test_cpu.c:125 ERROR: sa_open_cpu(): 
Operation not supported
1/4 Test #1: cpu ..***Failed0.00 sec
test 2
Start 2: memory

2: Test command: /tmp/buildd/libsysactivity-0.6.5/build/test/memory
2: Test timeout computed to be: 9.99988e+06
2: /tmp/buildd/libsysactivity-0.6.5/test/test_memory.c:144 ERROR: 
sa_open_memory(): Operation not supported
2/4 Test #2: memory ...***Failed0.00 sec
test 3
Start 3: network

3: Test command: /tmp/buildd/libsysactivity-0.6.5/build/test/network
3: Test timeout computed to be: 9.99988e+06
3: /tmp/buildd/libsysactivity-0.6.5/test/test_network.c:99 ERROR: 
sa_open_net(): Operation not supported
3/4 Test #3: network ..***Failed0.00 sec
test 4
Start 4: swap

4: Test command: /tmp/buildd/libsysactivity-0.6.5/build/test/swap
4: Test timeout computed to be: 9.99988e+06
4: /tmp/buildd/libsysactivity-0.6.5/test/test_swap.c:85 ERROR: sa_open_swap(): 
Operation not supported
4/4 Test #4: swap .***Failed0.00 sec

0% tests passed, 4 tests failed out of 4

Total Test time (real) =   0.01 sec

The following tests FAILED:
  1 - cpu (Failed)
  2 - memory (Failed)
  3 - network (Failed)
  4 - swap (Failed)
Errors while running CTest
debian/rules:55: recipe for target 'override_dh_auto_test-arch' failed
make[1]: *** [override_dh_auto_test-arch] Error 8
make[1]: Leaving directory '/tmp/buildd/libsysactivity-0.6.5'
debian/rules:31: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: libsysactivity
Source-Version: 0.6.5-5

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated 
libsysactivity 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

Bug#792631: python-librtmp: Build-Depends on no longer available python-cffi-dbg and python3-cffi-dbg

[Andreas Beckmann]

Source: python-librtmp
Version: 0.2.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

python-cffi stopped building python-cffi-dbg and python3-cffi-dbg,
causing your package to FTBFS in sid.


Andreas


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#774149: Workaround working

[Rogério Brito]

Hi, Mathieu.

On Jul 16 2015, Mathieu Malaterre wrote:
> On Wed, Jul 15, 2015 at 10:38 PM, Rogério Brito  wrote:
> > BTW, one very important question: are the problems with usbmount only
> > apparent when using fuse filesystems or are they also apparent when using
> > filesystems supported by the kernel (e.g., vfat or ext4)?
>
> vfat & ext4 usbkey were ok for me. So I suspect this is only FUSE-related.

Ah, thanks for the confirmation of my suspicion.

I just got a few external HDs that came preformatted in NTFS and I would
like to keep them as NTFS for the sake of:

* Storing files larger than 4GB (namely, videos that I grab from youtube via
  my package youtube-dl or tarballs of backups).
* Compatibility with other systems, in the (hopefully, rare) event that shit
  happens and I have to restore things from them.

Unfortunately, mounting NTFS filesystems with ntfs-3g with the default
options that udisks2 provides by default (and this applies to every modern
Linux system nowadays running any desktop environment) are a nightmare.

In particular, the lack of the option `big_writes` makes even modern amd64
CPUs burn so many cycles, while putting the option `big_writes` alleviates a
*lot* the CPU load and things get, from my own tests, about a 3 fold
speedup.  That's the difference between a file transfer taking 1 hour
vs. it taking 3 hours.

This is one of the positive sides of usbmount in relation to udisks/udisks2,
which I think that may justify usbmount still be maintained.

What do you guys think of this?  If I continue developing usbmount, I will
move it to github (as I previously mentioned), since that way the code gets
a lot more visibility and I like the workflow much more than via patchbombs
being sent to my e-mail address. :)

I would also be willing to give commit access to anybody that shows good
contributions to the repository.


Thanks for the feedback,

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: 752738 notfound in version 1.0.1-1

[Debian Bug Tracking System]

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

> notfound 752738 sikulix/1.1.0~beta1-1
Bug #752738 {Done: Gilles Filippini } [sikuli-ide] sikuli-ide 
throws java.lang.NoClassDefFoundError on start
Ignoring request to alter found versions of bug #752738 to the same values 
previously set
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#788533: mapnik: FTBFS: virtual memory exhausted: Cannot allocate memory (Was: Bug#756867: transition: gdal)

[Sebastiaan Couwenberg]

On 07/16/2015 11:20 PM, Jérémy Lal wrote:
> 2015-07-16 7:40 GMT+02:00 Sebastiaan Couwenberg :
>> On 07/16/2015 12:45 AM, Jérémy Lal wrote:
>> Failing to build on a release architecture is generally an RC bug, which
>> prevents testing migration.
>>
> I'm very surprised by this. The opposite was explained to me on
> #debian-devel by
> by Julien Cristau (cc-ing him in case he can tell me how i got this the
> wrong way).
> Is this written somewhere ?

I guess that's implied by the severity description:

"
 serious
is a severe violation of Debian policy (roughly, it violates a
"must" or "required" directive), or, in the package maintainer's or
release manager's opinion, makes the package unsuitable for release.
"

https://www.debian.org/Bugs/Developer#severities

Kind Regards,

Bas

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#789797: marked as done (sikuli-script.sh doesn't contain name of class to execute)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 21:21:17 +
with message-id 
and subject line Bug#789797: fixed in sikuli 1.0~x~rc3.tesseract3-dfsg1-12
has caused the Debian Bug report #789797,
regarding sikuli-script.sh doesn't contain name of class to execute
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.)


-- 
789797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsikuli-script-java
Version: 1.0~x~rc3.tesseract3-dfsg1-11
Severity: serious

Hi guys,

Something weird has happened to the executable-scripts patch - I think
the "count" numbers in the hunk are messed up somehow. Even though the
patch looks fine, the script sikuli-script/target/sikuli-script.sh has
contents

  #!/bin/sh
  exec /usr/bin/java \
  -cp \
  /usr/share/java/guava.jar:\
  /usr/share/java/jnr-posix.jar:\
  /usr/share/java/jaffl.jar:\
  /usr/share/java/jna.jar:\
  /usr/share/java/asm3.jar:\
  /usr/share/java/asm3-commons.jar:\
  /usr/share/java/antlr3-runtime.jar:\
  /usr/share/java/jnr-constants.jar:\
  /usr/share/java/jnr-ffi.jar:\
  /usr/share/java/jython.jar:\
  /usr/share/java/sikuli-script.jar \
  -Dfile.encoding=UTF-8 \
  -Dpython.home=/usr/share/jython \
  -Dpython.path="/usr/share/sikuli/Lib" \

that is, `org.sikuli.script.SikuliScript "$@"' is missing from the end.
This basically means that /usr/bin/sikuli is broken.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
--- End Message ---
--- Begin Message ---
Source: sikuli
Source-Version: 1.0~x~rc3.tesseract3-dfsg1-12

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

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

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

Debian distribution maintenance software
pp.
Gilles Filippini  (supplier of updated sikuli 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, 16 Jul 2015 22:40:16 +0200
Source: sikuli
Binary: sikuli-ide libsikuli-script-java libsikuli-script-jni 
libsikuli-script-doc
Architecture: source all amd64
Version: 1.0~x~rc3.tesseract3-dfsg1-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Java maintainers 

Changed-By: Gilles Filippini 
Description:
 libsikuli-script-doc - Documentation for libsikuli-script-java
 libsikuli-script-java - Visual scripting API for jython
 libsikuli-script-jni - Native libs for libsikuli-java
 sikuli-ide - IDE to develop sikuli scripts and use them as junit test cases
Closes: 789797
Changes:
 sikuli (1.0~x~rc3.tesseract3-dfsg1-12) unstable; urgency=medium
 .
   * Fix erroneous line count in patch executable-wrappers.patch
(closes: #789797).
Checksums-Sha1:
 c80ecf768056da0afa3be7238a7e265a468735f4 2360 
sikuli_1.0~x~rc3.tesseract3-dfsg1-12.dsc
 c40f2e5241c85c78dae660394a1776af9a5c73d9 17952 
sikuli_1.0~x~rc3.tesseract3-dfsg1-12.debian.tar.xz
 e94812e8b15028f3b94c63fade83f55fec08fb4f 1997200 
libsikuli-script-doc_1.0~x~rc3.tesseract3-dfsg1-12_all.deb
 09eb3b1c0f933001ef211ce3dd1a5e788dd0f9c0 140354 
libsikuli-script-java_1.0~x~rc3.tesseract3-dfsg1-12_all.deb
 c677eed6531df56f11d51f07ff39f35ae7b398d7 122976 
libsikuli-script-jni_1.0~x~rc3.tesseract3-dfsg1-12_amd64.deb
 20460f7cbe4cf2eec7ccf5a3ee612f261caef44f 484294 
sikuli-ide_1.0~x~rc3.tesseract3-dfsg1-12_all.deb
Checksums-Sha256:
 a51b3b2e82f18338fca555f41f225843e6b5e8a4ac5749b79718943283f8e311 2360 
sikuli_1.0~x~rc3.tesseract3-dfsg1-12.dsc
 7f452e9ca543ade3623c36b4bad7492ed44c3de9faf68e6e04f605ff433fd395 17952 
sikuli_1.0~x~rc3.tesseract3-dfsg1-12.debian.tar.xz
 3088c0535534a55295ce7abaa01b117be5a7e1084426cb29c1f68cda3ddfa35b 1997200 
libsikuli-script-doc_1.0~x~rc3.tesseract3-dfsg1-12_all.deb
 3ce45194fd201b91dbd26ecbdb419c111cf4e8c15a6d94d09b14a6d1b8d67454 140354 
libsikuli-script-java_1.0~x~rc3.tesseract3-dfsg1-12_all.deb
 d6c15db97dfb74be85c92efd238e86ee7cd60ca1691ab3495df304a8d9dc83ab 122976 
libsikuli-script-jni_1.0~x~rc3.tesseract3-dfsg1-12_amd64.deb
 62cc33fee0a54319932

Bug#788533: mapnik: FTBFS: virtual memory exhausted: Cannot allocate memory (Was: Bug#756867: transition: gdal)

[Jérémy Lal]

2015-07-16 7:40 GMT+02:00 Sebastiaan Couwenberg :

> On 07/16/2015 12:45 AM, Jérémy Lal wrote:
> > 2015-07-16 0:41 GMT+02:00 Sebastiaan Couwenberg :
> >
> >> On 07/16/2015 12:35 AM, Jérémy Lal wrote:
> >>> 2015-07-16 0:20 GMT+02:00 Sebastiaan Couwenberg :
> >>>
>  On 06/28/2015 12:46 PM, Jérémy Lal wrote:
> > 2015-06-20 13:34 GMT+02:00 Sebastiaan Couwenberg  >:
> >> On 06/19/2015 06:35 PM, Jérémy Lal wrote:
> >>> 2015-06-19 18:22 GMT+02:00 Emilio Pozuelo Monfort <
> po...@debian.org
> >>> :
> >>>
>  (Moving the discussion to #788533; #756867 bcc'ed)
> 
>  On 19/06/15 14:40, Sebastiaan Couwenberg wrote:
> > The mips* FTBFS are a recurring problem for the mapnik package,
> >> previous
> > builds were no different. I'll try to get it to build on a
> >> porterbox,
> > but I expect intervention from the buildd admins will be required
>  like
> > last time to make sure only the buildds with the most resources
> try
>  to
> > build mapnik.
> >
> > See: https://bugs.debian.org/742149
> >  https://bugs.debian.org/729121
> 
>  I'm not sure there are buildds with more RAM. Note that the
> package
> >> failed
>  in
>  the exact same way on kfreebsd-i386, which has 3GB of RAM + 4GB of
>  swap.
>  Since
>  all these arches are 32bits, more memory is probably not going to
>  help.
> 
>  Instead, perhaps you can make the build take less memory, e.g. by
> >> reducing
>  the
>  optimizations (-O1?) or using some flags such as the linker's
>  --no-keep-memory.
> >>>
> >>>
> >>> Mapnik 2.2 used to pass builds with some of those options, also
> with
> >>> removing
> >>> -ftemplate-depth-300.
> >>> That last option i restored with mapnik 3.0, to see what would
> happen
> >> with
> >>> upstream options,
> >>> since so much has changed in that project.
> >>> I'm preparing now an upload with that option removed.
> >>
> >> The new uploaded didn't resolve the build failures, it still failed
> on
> >> {hurd,kfreebsd}-i386 & mips*.
> >>
> >> Since it's a recurring problem on mips*, maybe exclude these
> >> architectures and request removal of the package on mips*.
> >
> > I've requested removal of the old mapnik 2.2 libs on the three
>  architectures
> > where it fails. I've been told that's the only thing needed to allow
> > migration to testing.
> > https://bugs.debian.org/789720
> 
>  The subsequent mapnik (3.0.0+ds-1) upload failed to build on the same
>  archs again. I've just pushed a change to exclude mips* from the list
> of
>  architectures that will prevent them from building mapnik.
> 
>  mapnik still can't migrate because the old python-mapnik binaries
>  (#790043) and the outstanding RC bugs.
> 
>  https://release.debian.org/migration/testing.pl?package=mapnik
> 
>  I'd like to upload mapnik (3.0.0+ds-2) as it currently exists in git
> to
>  get the mips* exclusion and static libraries for the python-mapnik
> build
>  into the archive. After that we can request removal of the mapnik
>  package for mips & mipsel.
> 
>  Jérémy, do you have anything you want to add before the upload?
> 
> >>>
> >>> ok for python-mapnik (and the transition package python-mapnik2)
> >>>
> >>> As far as i understand, you just need
> >>> Architecture: any
> >>> and removal of the previous 2.2 versions on mips and mipsel that were
> in
> >>> testing
> >>> to get mapnik to go in testing on other architectures again.
> >>> That is already done...
> >>
> >> So do you want to revert the Architecture change?
> >>
> >>
> > Yes.
> > Unless someone explains how i'm wrong, of course :)
>
> Failing to build on a release architecture is generally an RC bug, which
> prevents testing migration.
>
> Kind Regards,
>
> Bas
>
>
I'm very surprised by this. The opposite was explained to me on
#debian-devel by
by Julien Cristau (cc-ing him in case he can tell me how i got this the
wrong way).
Is this written somewhere ?

Jérémy

Bug#792622: missing licenses in debian/copyright

[Thorsten Alteholz]

Package: gnumach
Version: 2:1.5+git20150704-1
Severity: serious
User: alteh...@debian.org
Usertags: ftp
X-Debbugs-CC: ftpmas...@ftp-master.debian.org
thanks

Dear Maintainer,

please add all missing licenses to your debian/copyright. At least I found 
files under:

 MPL (linux/pcmcia-cs/include/pcmcia/*)
 GPL-3 (i386/grub/*)
 GFDL (doc/mach*)
Maybe there are others missing.

Thanks!
  Thorsten


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: 752738 notfound in version 1.0.1-1

[Debian Bug Tracking System]

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

> notfound 752738 sikuli/1.0.1-1
Bug #752738 {Done: Gilles Filippini } [sikuli-ide] sikuli-ide 
throws java.lang.NoClassDefFoundError on start
Ignoring request to alter found versions of bug #752738 to the same values 
previously set
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: 752738 notfound in version 1.0.1-1

[Debian Bug Tracking System]

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

> notfound 752738 1.0.1-1
Bug #752738 {Done: Gilles Filippini } [sikuli-ide] sikuli-ide 
throws java.lang.NoClassDefFoundError on start
Ignoring request to alter found versions of bug #752738 to the same values 
previously set
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#778135: marked as done (syrthes: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 22:08:26 +0200
with message-id <55a80f3a.40...@debian.org>
and subject line Re: Bug#778135: syrthes: ftbfs with GCC-5
has caused the Debian Bug report #778135,
regarding syrthes: ftbfs with GCC-5
to be marked as done.

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

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


-- 
778135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:syrthes
Version: 4.1.1-dfsg1-5
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/syrthes_4.1.1-dfsg1-5_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]

  Installation of syrthes-post on architecture Debian 

Installation of  syrthesseq  on architecture Debian

make syrthesseq  NOM_ARCH=Debian SYRTHES4_HOME='/«PKGBUILDDIR»' 2>&1 | tee 
syrthesseq.log
syrthesseqINSTALL 0

  Installation of syrthesmpi on architecture Debian 

  Installation of syrthescfd on architecture Debian 
- you ve chosen not to install "gui" 
function report
NO file ERREUR.log

-
Before using SYRTHES, each user must source
the /«PKGBUILDDIR»/arch/Debian/bin/syrthes.profile file before using 
the code.

The easiest way is to put the following lines in each of the users
 '.profile' or '.bashrc' (depending on the shell)

syrthesprofile=/«PKGBUILDDIR»/arch/Debian/bin/syrthes.profile
#(adjust path to your system)
if [ -f $syrthesprofile ] ; then 
  . $syrthesprofile
fi

-

Warning : installation of some composants failed

Check log files for more information

# ERREUR.log should be empty
if [ -s "src/syrthes-install/ERREUR.log" ]; then \
  cat "src/syrthes-install/ERREUR.log" && false; \
fi
syr_cfd_coupling.c:222:33: error: 'EXIT_FAILURE' undeclared (first use in this 
function)
make[3]: *** [/«PKGBUILDDIR»/build//syr_cfd_coupling.o] Error 1
make[2]: *** [syrthescfd] Error 2
../syrthescfd.log:syr_cfd_coupling.c:222:33: error: 'EXIT_FAILURE' undeclared 
(first use in this function)
../syrthescfd.log:make[3]: *** [/«PKGBUILDDIR»/build//syr_cfd_coupling.o] 
Error 1
../syrthescfd.log:make[2]: *** [syrthescfd] Error 2
make[1]: *** [override_dh_auto_build] Error 1
debian/rules:42: recipe for target 'override_dh_auto_build' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [build-arch] Error 2
debian/rules:32: recipe for target 'build-arch' failed
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Version: 4.3.0-dfsg1-1

Hi Brett,

Brett Johnson a écrit le 15/07/2015 21:23 :
> tags 778135 +patch
> thanks
> 
> gcc5 has changed inline function semantics to match C99 standard,
> but packages does not conform to C99. Fix by telling gcc to use
> gnu89 standard instead.

Thanks a lot for taking care of this issue. But I've just checked a
build against gcc-5 and, while I can reproduce the FTBFS with release
4.1.1-dfsg1-5, the release 4.3.0-dfsg1-1 builds successfully.

Hence closing this bug.

Thanks,

_g.




signature.asc
Description: OpenPGP digital signature
--- End Message ---

Processed: Patch tags.

[Debian Bug Tracking System]

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

> tags 778152 +patch
Bug #778152 [src:uaputl] uaputl: ftbfs with GCC-5
Added tag(s) patch.
> tags 778135 +patch
Bug #778135 [src:syrthes] syrthes: ftbfs with GCC-5
Added tag(s) patch.
> tags 778129 +patch
Bug #778129 [src:squeak-plugins-scratch] squeak-plugins-scratch: ftbfs with 
GCC-5
Added tag(s) patch.
> --
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#792617: elasticsearch: CVE-2015-5377 CVE-2015-5531

[Salvatore Bonaccorso]

Source: elasticsearch
Version: 1.0.3+dfsg-5
Severity: grave
Tags: security upstream fixed-upstream
Justification: user security hole

Hi,

the following vulnerabilities were published for elasticsearch.
Reporting them right now as severity grave since some details are
missed so feel free to downgrade.

CVE-2015-5377[0]:
Remote code execution vulnerability

CVE-2015-5531[1]:
Directory traversal vulnerability

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-5377
[1] https://security-tracker.debian.org/tracker/CVE-2015-5531
[2] https://www.elastic.co/blog/elasticsearch-1-7-0-and-1-6-1-released#security

Regards,
Salvatore


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Patch submitted for wrong bug

[Debian Bug Tracking System]

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

> tags 778058 - patch
Bug #778058 [src:percona-xtradb-cluster-galera-2.x] 
percona-xtradb-cluster-galera-2.x: ftbfs with GCC-5
Removed tag(s) patch.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#778058: Patch submitted for wrong bug

[Josh Gadeken]

tags 778058 - patch
thanks

Sorry, I accidentally submitted this patch to the wrong bug number.

--
Josh Gadeken
Linux for HP Helion OpenStack, Hewlett-Packard


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#778039: Patch for GCC 5 build issue

[Josh Gadeken]

tags 778039 + patch
thanks

Here's a fix for the GCC 5 build issue. I added 
"-Wno-error=format-security" to the GNUmakefile. The package 
successfully builds and links using GCC 5 with this change.


It looks like GCC 5 / gobjc 5 sets "-Werror=format-security" by default. 
Please see the "Environment variables" section at

https://wiki.debian.org/Hardening#Environment_variables for more info.

--
Josh Gadeken
Linux for HP Helion OpenStack, Hewlett-Packard
Description: Fix GCC 5 build error. 
  Add -Wno-error=format-security to ADDITIONAL_CFLAGS and ADDITIONAL_OBJCFLAGS.

Author: Josh Gadeken 
Bug-Debian: https://bugs.debian.org/778058

--- oolite-1.77.1.orig/GNUmakefile
+++ oolite-1.77.1/GNUmakefile
@@ -33,8 +33,8 @@ ifeq ($(GNUSTEP_HOST_OS),mingw32)
 else
 ADDITIONAL_INCLUDE_DIRS  = -Isrc/SDL -Isrc/Core -Isrc/BSDCompat -Isrc/Core/Scripting -Isrc/Core/Materials -Isrc/Core/Entities -Isrc/Core/OXPVerifier -Isrc/Core/Debug -Isrc/Core/Tables
 ADDITIONAL_OBJC_LIBS = -lgnustep-base -lstdc++
-ADDITIONAL_CFLAGS= -Wall -DLINUX -DNEED_STRLCPY
-ADDITIONAL_OBJCFLAGS = -Wall -std=c99 -DLOADSAVEGUI -DLINUX -DXP_UNIX -Wno-import
+ADDITIONAL_CFLAGS= -Wall -DLINUX -DNEED_STRLCPY -Wno-error=format-security
+ADDITIONAL_OBJCFLAGS = -Wall -std=c99 -DLOADSAVEGUI -DLINUX -DXP_UNIX -Wno-import -Wno-error=format-security
 oolite_LIB_DIRS  += -L/usr/X11R6/lib/
 ifeq ($(use_deps),yes)
 oolite_LIB_DIRS  += -Ldeps/Linux-deps/$(HOST_ARCH)/lib_linker

Processed: Patch for GCC 5 build issue

[Debian Bug Tracking System]

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

> tags 778039 + patch
Bug #778039 [src:oolite] oolite: ftbfs with GCC-5
Added tag(s) patch.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Patch for GCC 5 build issue

[Debian Bug Tracking System]

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

> tags 778058 + patch
Bug #778058 [src:percona-xtradb-cluster-galera-2.x] 
percona-xtradb-cluster-galera-2.x: ftbfs with GCC-5
Added tag(s) patch.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#778058: Patch for GCC 5 build issue

[Josh Gadeken]

tags 778058 + patch
thanks

Here's a fix for the GCC 5 build issue. I added 
"-Wno-error=format-security" to the GNUmakefile. The package 
successfully builds and links using GCC 5 with this change.


It looks like GCC 5 / gobjc 5 sets "-Werror=format-security" by default. 
Please see the "Environment variables" section at

https://wiki.debian.org/Hardening#Environment_variables for more info.

--
Josh Gadeken
Linux for HP Helion OpenStack, Hewlett-Packard
Description: Fix GCC 5 build error. 
  Add -Wno-error=format-security to ADDITIONAL_CFLAGS and ADDITIONAL_OBJCFLAGS.

Author: Josh Gadeken 
Bug-Debian: https://bugs.debian.org/778058

--- oolite-1.77.1.orig/GNUmakefile
+++ oolite-1.77.1/GNUmakefile
@@ -33,8 +33,8 @@ ifeq ($(GNUSTEP_HOST_OS),mingw32)
 else
 ADDITIONAL_INCLUDE_DIRS  = -Isrc/SDL -Isrc/Core -Isrc/BSDCompat -Isrc/Core/Scripting -Isrc/Core/Materials -Isrc/Core/Entities -Isrc/Core/OXPVerifier -Isrc/Core/Debug -Isrc/Core/Tables
 ADDITIONAL_OBJC_LIBS = -lgnustep-base -lstdc++
-ADDITIONAL_CFLAGS= -Wall -DLINUX -DNEED_STRLCPY
-ADDITIONAL_OBJCFLAGS = -Wall -std=c99 -DLOADSAVEGUI -DLINUX -DXP_UNIX -Wno-import
+ADDITIONAL_CFLAGS= -Wall -DLINUX -DNEED_STRLCPY -Wno-error=format-security
+ADDITIONAL_OBJCFLAGS = -Wall -std=c99 -DLOADSAVEGUI -DLINUX -DXP_UNIX -Wno-import -Wno-error=format-security
 oolite_LIB_DIRS  += -L/usr/X11R6/lib/
 ifeq ($(use_deps),yes)
 oolite_LIB_DIRS  += -Ldeps/Linux-deps/$(HOST_ARCH)/lib_linker

Processed: [bts-link] source package midgard2-core

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package midgard2-core
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #774630 (http://bugs.debian.org/774630)
> # Bug title: CVE-2014-8148: midgard-core configures D-Bus system bus to be 
> insecure
> #  * https://github.com/midgardproject/midgard-core/issues/208
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 774630 + fixed-upstream
Bug #774630 [midgard2-common] CVE-2014-8148: midgard-core configures D-Bus 
system bus to be insecure
Added tag(s) fixed-upstream.
> usertags 774630 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 774630 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#792615: FTBFS on powerpc and s390x: assert-error MTH0108.als at or around line 58

[Martin Michlmayr]

Package: afnix
Version: 2.5.1-1
Severity: serious

2.5.1-1 fails to build on powerpc and s390x:

running: MTH0108.als
exception : assert-error
in file   : MTH0108.als at or around line 58
afnix-aexec: failure MTH0108.als
make[6]: *** [MTH0108.als] Error 1
make[5]: *** [test] Error 2

See 
https://buildd.debian.org/status/fetch.php?pkg=afnix&arch=s390x&ver=2.5.1-1&stamp=1436815369

-- 
Martin Michlmayr
Linux for HP Helion, Hewlett-Packard


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#792549: marked as done (libecm0-dev-common: fails to upgrade from 'testing' - trying to overwrite /usr/include/ecm.h)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 19:05:06 +
with message-id 
and subject line Bug#792549: fixed in gmp-ecm 6.4.4+ds-2
has caused the Debian Bug report #792549,
regarding libecm0-dev-common: fails to upgrade from 'testing' - trying to 
overwrite /usr/include/ecm.h
to be marked as done.

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

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


-- 
792549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libecm0-dev-common
Version: 6.4.4+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libecm0-dev-common.
  Preparing to unpack .../libecm0-dev-common_6.4.4+ds-1_all.deb ...
  Unpacking libecm0-dev-common (6.4.4+ds-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libecm0-dev-common_6.4.4+ds-1_all.deb (--unpack):
   trying to overwrite '/usr/include/ecm.h', which is also in package 
libecm-dev 6.4.4-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libecm0-dev-common_6.4.4+ds-1_all.deb


cheers,

Andreas


libecm-dev=6.4.4-2_libecm0-dev-common=6.4.4+ds-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gmp-ecm
Source-Version: 6.4.4+ds-2

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated gmp-ecm 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, 16 Jul 2015 16:07:37 +
Source: gmp-ecm
Binary: gmp-ecm libecm0 libecm0-dev libecm0-dev-common libecm0-dbg libecm-dev
Architecture: source amd64 all
Version: 6.4.4+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Description:
 gmp-ecm- Factor integers using the Elliptic Curve Method
 libecm-dev - transitional dummy package
 libecm0- factor integers using the Elliptic Curve Method -- lib
 libecm0-dbg - factor integers using the Elliptic Curve Method -- debug
 libecm0-dev - factor integers using the Elliptic Curve Method -- libdev
 libecm0-dev-common - factor integers using the Elliptic Curve Method -- header
Closes: 792549
Changes:
 gmp-ecm (6.4.4+ds-2) unstable; urgency=medium
 .
   * RC bug fix release (Closes: 792549), stabilize libdev transition.
Checksums-Sha1:
 cac95550e6275f0b1e12b2c451bdaf1367524f40 2348 gmp-ecm_6.4.4+ds-2.dsc
 8ffe6a33f850ac49ab2eecdbdb61be46cc9784c0 17216 gmp-ecm_6.4.4+ds-2.debian.tar.xz
 191e72604e22691af2203e0ccf00c3773ccd1305 28734 gmp-ecm_6.4.4+ds-2_amd64.deb
 11bbc29a145c023fd627255ba51b4b08d98cac9d 832 libecm-dev_6.4.4+ds-2_all.deb
 4b6964bf12e667a4e0d4f621f1c9ad216eb08938 420344 
libecm0-dbg_6.4.4+ds-2_amd64.deb
 dbf9f1e51f8a84ac80b972382137d7c227ab8091 115272 
libecm0-dev-common_6.4.4+ds-2_all.deb
 a05d3232006b9f786f4ec69fb8631cb00590851e 149248 
libecm0-dev_6.4.4+ds-2_amd64.deb
 c20a394a201773e2d454f31ee5499499deec57dd 251030 libecm0_6.4.4+ds-2_amd64.deb
Checksums-Sha256:
 0d378aab7cbf347c913412ecfaddda97eef92331e479a05fa0da4b13a7c09b25 2348 
gmp-ecm_6.4.4+ds-2.dsc
 c6f80622b53746c8ce048697a50c3d8db574d7e1a7103ea2b692d85726c63c01 17216 
gmp-ecm_6.4.4+ds-2.debian.tar.xz
 a424236e1254edbf0b2b3ef08a7a346c4fee135236521d351bcb2f886b6b00bd 28734 
gmp-ecm_6.4.4+ds-2_amd64.deb
 720137ee272ef92eda64addaea0c32e826d4729eeb197ff611f1a4fc1349278d 832 
libecm-dev_6.4.4+ds-2_all.deb
 4cb0682c539af0f6f1e831759e2588227d0659f7c9c134753b9adf852c38f415 420344 
libecm0-dbg_6.4.4+ds-2_amd64.deb
 f2699a7295572f1f87d4650c8915ecc6a2b9d799b0d73f0733098bd1026e3bd7 115272 
libecm0-dev-common_6.4.4+ds-2_all.deb
 49e4fecc2ba073dd6d85f17186d0b6fcc56c

Bug#778129: squeak-plugins-scratch: ftbfs with GCC-5

[Brett Johnson]

tags 778129 +patch
thanks

Inline function semantics have changed in the C11 standard, which causes
this build failure. Fixed by compiling with "-std=gnu89", until upstream
updates the source to comply with C11.

--- squeak-plugins-scratch-1.4.0.2~svn.r83.orig/debian/rules2012-07-23 
20:12:46.0
+
+++ squeak-plugins-scratch-1.4.0.2~svn.r83/debian/rules 2015-07-16 
18:47:41.684780247 +
@@ -3,6 +3,7 @@
 export DH_ALWAYS_EXCLUDE=.svn

 LDFLAGS=-Wl,-z,defs -Wl,--as-needed -Wl,--no-undefined
+CFLAGS=-std=gnu89

 config: config-stamp
 config-stamp:

-- 
Brett Johnson 


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#778134: synaptic: ftbfs with GCC-5

[Brett Johnson]

The ABI error which caused this original build failure appears to now
have been changed to a warning originating in /usr/include/xapian/version.h

It warns that the application is being built with a different compiler than
that which built the xapian library.

In any case, this is not specifically a gcc5 bug, nor a synaptic bug, and it
builds fine now with a ABI warning, even with libxapian being compiled using
GCC 4.9.2. My build log is at:

 http://people.linux.hp.com/~brett/logs/synaptic-0.81.4/buildlog.txt

-- 
Brett Johnson 


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791467: plowshare: javascript usage puts user at risk of remote code execution

[plowshare4-bug@discard.email]

> I am in the process of packaging the new upstream version of plowshare.
> There has been a significant change so that the core framework (of shell
> scripts) is kept entirely separate to the scripts which use this API to
> implement support for specific external sites.
 
While separating the core from the scripts that support the individual
sites is definitely a step in the right direction, I think that
relying entirely on audits of those scripts is a bad idea. There are
many such scripts, new scripts for new cyberlocker sites are
frequently added, and existing scripts updated to take account of
changes to the sites they support.
 
Therefore, performing such audits would be like playing a game of whack-a-mole.
 
Moreover there is a trade-off: the stricter the scripts are about what
javascript they accept, the more likely they will be broken by small changes
so the websites.
 
Lastly, you've got to wonder how effective malicious code detection
can be if it's implemented entirely using unix shell tools (and presumably
operates purely on the syntactic level).
 
For these reasons, you really do need a sandboxed javascript interpreter
if you want to avoid the possibility of malicious code execution.
Maybe other js interpreters (v8, spidermonkey) are easier to sandbox?
 
Until you find a way of sandboxing the JS interpreter, I'd recommend
disabling the javascript support.

Processed: Re: Bug#788557: freerdp: FTBFS: list sub-command REMOVE_DUPLICATES requires list to be present

[Debian Bug Tracking System]

Processing control commands:

> tag -1 fixed-upstream
Bug #788557 [src:freerdp] freerdp: FTBFS: list sub-command REMOVE_DUPLICATES 
requires list to be present
Added tag(s) fixed-upstream.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#788557: freerdp: FTBFS: list sub-command REMOVE_DUPLICATES requires list to be present

[Andreas Cadhalpun]

Control: tag -1 fixed-upstream

Hi,

On 12.06.2015 19:15, Andreas Cadhalpun wrote:
> freerdp currently fails to build in sid/stretch with the following error:
> CMake Error at channels/client/CMakeLists.txt:33 (list):
>   list sub-command REMOVE_DUPLICATES requires list to be present.

This is fixed-upstream as part of commit [1].
However, there are more issues, but current git HEAD compiles fine.
(It just runs into a test failure...)

Best regards,
Andreas

1: 
https://github.com/FreeRDP/FreeRDP/commit/1b663ceffe51008af7ae9749e5b7999b2f7d6698?diff=unified


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777917: marked as done (ipgrab: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 18:19:37 +
with message-id 
and subject line Bug#777917: fixed in ipgrab 0.9.10-1.1
has caused the Debian Bug report #777917,
regarding ipgrab: ftbfs with GCC-5
to be marked as done.

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

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


-- 
777917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ipgrab
Version: 0.9.10-1
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/ipgrab_0.9.10-1_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
/«PKGBUILDDIR»/src/tftp.c:174: undefined reference to `get_packet_bytes'
/«PKGBUILDDIR»/src/tftp.c:182: undefined reference to `display_minimal_string'
/«PKGBUILDDIR»/src/tftp.c:183: undefined reference to `display_minimal_string'
/«PKGBUILDDIR»/src/tftp.c:184: undefined reference to `display_minimal'
/«PKGBUILDDIR»/src/tftp.c:129: undefined reference to `get_packet_bytes'
/«PKGBUILDDIR»/src/tftp.c:136: undefined reference to 
`get_packet_apparentbytesleft'
/«PKGBUILDDIR»/src/tftp.c:141: undefined reference to `my_malloc'
/«PKGBUILDDIR»/src/tftp.c:144: undefined reference to `get_packet_bytes'
/«PKGBUILDDIR»/src/tftp.c:149: undefined reference to `display_minimal_string'
/«PKGBUILDDIR»/src/tftp.c:150: undefined reference to `display_minimal_string'
/«PKGBUILDDIR»/src/tftp.c:151: undefined reference to `display_minimal'
/«PKGBUILDDIR»/src/tftp.c:188: undefined reference to `display_strmap'
/«PKGBUILDDIR»/src/tftp.c:189: undefined reference to `display'
/«PKGBUILDDIR»/src/tftp.c:107: undefined reference to `display_strmap'
/«PKGBUILDDIR»/src/tftp.c:108: undefined reference to `display_string'
/«PKGBUILDDIR»/src/tftp.c:109: undefined reference to `display_string'
/«PKGBUILDDIR»/src/tftp.c:234: undefined reference to `display_strmap'
/«PKGBUILDDIR»/src/tftp.c:235: undefined reference to `display'
/«PKGBUILDDIR»/src/tftp.c:236: undefined reference to `display_string'
/«PKGBUILDDIR»/src/tftp.c:155: undefined reference to `display_strmap'
/«PKGBUILDDIR»/src/tftp.c:156: undefined reference to `display'
/«PKGBUILDDIR»/src/tftp.c:157: undefined reference to `display'
udp.o: In function `dump_udp':
/«PKGBUILDDIR»/src/udp.c:50: undefined reference to `set_layer'
/«PKGBUILDDIR»/src/udp.c:53: undefined reference to `stats_update'
/«PKGBUILDDIR»/src/udp.c:59: undefined reference to `get_packet_bytes'
/«PKGBUILDDIR»/src/udp.c:87: undefined reference to `display_header_banner'
/«PKGBUILDDIR»/src/udp.c:90: undefined reference to `display_strmap'
/«PKGBUILDDIR»/src/udp.c:91: undefined reference to `display_strmap'
/«PKGBUILDDIR»/src/udp.c:92: undefined reference to `display'
/«PKGBUILDDIR»/src/udp.c:93: undefined reference to `display'
/«PKGBUILDDIR»/src/udp.c:102: undefined reference to `hexbuffer_flush'
/«PKGBUILDDIR»/src/udp.c:77: undefined reference to `display_minimal_string'
/«PKGBUILDDIR»/src/udp.c:78: undefined reference to `display_minimal'
/«PKGBUILDDIR»/src/udp.c:79: undefined reference to `display_minimal_string'
/«PKGBUILDDIR»/src/udp.c:80: undefined reference to `display_minimal'
/«PKGBUILDDIR»/src/udp.c:81: undefined reference to `display_minimal_string'
collect2: error: ld returned 1 exit status
make[3]: *** [ipgrab] Error 1
Makefile:248: recipe for target 'ipgrab' failed
make[3]: Leaving directory '/«PKGBUILDDIR»/src'
make[2]: *** [all-recursive] Error 1
Makefile:216: recipe for target 'all-recursive' failed
make[2]: Leaving dire

Bug#792361: redmine: dpkg --configure broken when installing ruby packages

[Antonio Terceiro]

hello Praveen,

On Thu, Jul 16, 2015 at 07:58:08PM +0530, Pirate Praveen wrote:
> On Tuesday 14 July 2015 06:33 PM, Antonio Terceiro wrote:
> > This has nothing to do with redmine, but with the fact that
> > ruby-jquery-rails was upgraded to a version that breaks the redmine
> > dependency checking.
> 
> Can I upload ruby-jquery-rails3 to fix the situation?

this would remedy the original problem temporarily, but will create
another one. It took us more than 1.5 years to get rid of ruby-rack1.4¹

¹ https://tracker.debian.org/pkg/ruby-rack1.4

I would rather revert ruby-jquery-rails to the previous version using an
upstream version number such as 4.0.4.REALLY.3.1.2, and work on doing a
_planned_ update of all of these moving parts, staging the changes in
experimental and being sure of what we are doing before doing it in
unstable.

> jquery-rails 4.0.4 require railties >= 4.2 as well.

I think we _need_ to start checking this type of thing _before_ updating
packages blindly ... this is not the first nor the second time this type
of issue happens.

> What is the plan for
> updating to rails 4.2?

No specific plans yet, but we need to do it.

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Processed: notfound 789106 in 0.3.1, found 789106 in 0.3.1-1, tagging 789106, tagging 790624, tagging 788773 ...

[Debian Bug Tracking System]

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

> # verified in local rebuilds that the packages ftbfs in sid but not in jessie
> notfound 789106 0.3.1
Bug #789106 [libpam-sshauth] FTBFS: missing build-dep on zlib: pkg-config fails
There is no source info for the package 'libpam-sshauth' at version '0.3.1' 
with architecture ''
Unable to make a source version for version '0.3.1'
No longer marked as found in versions 0.3.1.
> found 789106 0.3.1-1
Bug #789106 [libpam-sshauth] FTBFS: missing build-dep on zlib: pkg-config fails
Marked as found in versions libpam-sshauth/0.3.1-1.
> tags 789106 + sid stretch
Bug #789106 [libpam-sshauth] FTBFS: missing build-dep on zlib: pkg-config fails
Added tag(s) sid and stretch.
> tags 790624 + sid stretch
Bug #790624 [openms] FTBFS: undefined reference to symbol 
'_ZNK4QDir6mkpathERK7QString'
Added tag(s) sid and stretch.
> tags 788773 + sid stretch
Bug #788773 {Done: Julian Gilbey } [proxytunnel] FTBFS: DSO 
missing from command line: MD5_Final@@OPENSSL_1.0.0
Added tag(s) sid and stretch.
> tags 789982 + sid stretch
Bug #789982 [python-fedora] FTBFS: pybuild: AttributeError: 'module' object has 
no attribute '_vendor'
Added tag(s) sid and stretch.
> tags 787339 + sid stretch
Bug #787339 {Done: Anton Gladky } [qtiplot] FTBFS:  ap.h: No 
such file or directory
Added tag(s) stretch and sid.
> tags 789985 + sid stretch
Bug #789985 {Done: Andreas Tille } [r-bioc-shortread] FTBFS: 
IRanges_defines.h: fatal error: S4Vectors_defines.h: No such file or directory
Added tag(s) sid and stretch.
> tags 789990 + sid stretch
Bug #789990 {Done: Timo Aaltonen } [src:389-ds-console] 
FTBFS: AttributeAlias.java: error: package com.netscape.management.client.util 
does not exist
Added tag(s) sid and stretch.
> tags 791777 + sid stretch
Bug #791777 [src:ruby-dataobjects-sqlite3] FTBFS: ERROR: Test ruby2.1 failed. 
Exiting
Added tag(s) sid and stretch.
> tags 791789 + sid stretch
Bug #791789 {Done: Youhei SASAKI } [src:ruby-grib] 
FTBFS: ERROR: Test ruby2.1 failed. Exiting.
Added tag(s) stretch and sid.
> tags 791781 + sid stretch
Bug #791781 [src:ruby-multimap] FTBFS: nested_multimap_ext.c:13:55: error: 
invalid type argument of '->' (have 'int')
Added tag(s) sid and stretch.
> tags 791786 + sid stretch
Bug #791786 {Done: Christian Hofstaedtler } 
[src:ruby-redcloth] FTBFS: ERROR: Test ruby2.1 failed. Exiting.
Added tag(s) stretch and sid.
> tags 791779 + sid stretch
Bug #791779 [src:ruby-tokyocabinet] FTBFS: uninitialized constant Config 
(NameError)
Added tag(s) stretch and sid.
> tags 791784 + sid stretch
Bug #791784 [src:ruby-serialport] FTBFS: error: call to 'rb_check_safe_str' 
declared with attribute error: rb_check_safe_str() and Check_SafeStr() are 
obsolete
Added tag(s) sid and stretch.
> tags 791775 + sid stretch
Bug #791775 {Done: Christian Hofstaedtler } [src:ruby-yajl] 
FTBFS: ERROR: Test ruby2.1 failed. Exiting
Added tag(s) stretch and sid.
> tags 792493 + sid stretch
Bug #792493 [src:xmms2] xmms2: FTBFS: uses obsolete ruby Config::CONFIG
Added tag(s) sid and stretch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
787339: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787339
788773: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788773
789106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789106
789982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789982
789985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789985
789990: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789990
790624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790624
791775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791775
791777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791777
791779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791779
791781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791781
791784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791784
791786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791786
791789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791789
792493: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Block mapnik python binding bug with python-mapnik ITP

[Debian Bug Tracking System]

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

> #790043 mapnik: no longer builds python bindings
> #792539 ITP: python-mapnik
> block 790043 by 792539
Bug #790043 [src:mapnik] mapnik: no longer builds python bindings
790043 was not blocked by any bugs.
790043 was not blocking any bugs.
Added blocking bug(s) of 790043: 792539
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#792609: gstreamermm-1.0: FTBFS: symbols not quite as expected

[Aaron M. Ucko]

Source: gstreamermm-1.0
Version: 1.4.3+dfsg-1
Severity: serious
Justification: fails to build from source

Builds of gstreamermm-1.0 have failed due to discrepancies in the set
of defined symbols.  Per

https://buildd.debian.org/status/package.php?compact=compact&p=gstreamermm-1.0,ujson

this problem has been occurring even on architectures such as arm64
with the same general characteristics as amd64; perhaps something
relevant changed in the build environment over the past few weeks.
Could you please take a look?

Thanks!


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#778047: marked as done (opensaml2: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 16:05:18 +
with message-id 
and subject line Bug#778047: fixed in opensaml2 2.5.3-2.1
has caused the Debian Bug report #778047,
regarding opensaml2: ftbfs with GCC-5
to be marked as done.

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

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


-- 
778047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opensaml2
Version: 2.5.3-2
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/opensaml2_2.5.3-2_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
EGREP='/bin/grep -E'
EXEEXT=''
FGREP='/bin/grep -F'
GREP='/bin/grep'
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
LD='/usr/bin/ld -m elf_x86_64'
LDFLAGS='-fPIE -pie -Wl,-z,relro -Wl,-z,now -lpthread -Wl,--as-needed'
LIBOBJS=''
LIBS='-lz  '
LIBTOOL='$(SHELL) $(top_builddir)/libtool'
LIPO=''
LN_S='ln -s'
LOG4CPP_CONFIG=''
LOG4SHIB_CONFIG=''
LTLIBOBJS=''
MAKEINFO='${SHELL} /«PKGBUILDDIR»/build-aux/missing makeinfo'
MANIFEST_TOOL=':'
MKDIR_P='/bin/mkdir -p'
NM='/usr/bin/nm -B'
NMEDIT=''
OBJDUMP='objdump'
OBJEXT='o'
OTOOL64=''
OTOOL=''
PACKAGE='opensaml'
PACKAGE_BUGREPORT='https://issues.shibboleth.net/'
PACKAGE_NAME='opensaml'
PACKAGE_STRING='opensaml 2.5.3'
PACKAGE_TARNAME='opensaml'
PACKAGE_URL=''
PACKAGE_VERSION='2.5.3'
PATH_SEPARATOR=':'
PKG_CONFIG='/usr/bin/pkg-config'
PTHREAD_CC='gcc'
PTHREAD_CFLAGS=''
PTHREAD_LIBS=''
RANLIB='ranlib'
SED='/bin/sed'
SET_MAKE=''
SHELL='/bin/bash'
STRIP='strip'
VERSION='2.5.3'
ac_ct_AR='ar'
ac_ct_CC='gcc'
ac_ct_CXX='g++'
ac_ct_DUMPBIN=''
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: opensaml2
Source-Version: 2.5.3-2.1

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated opensaml2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Jul 2015 17:15:55 +0200
Source: opensaml2
Binary: libsaml8 libsaml2-dev opensaml2-tools opensaml2-schemas libsaml2-doc
Architecture: source amd64 all
Version: 2.5.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Shib Team 
Changed-By: Matthias Klose 
Description:
 libsaml2-dev - Security Assertion Markup Language library (development)
 libsaml2-doc - Security Assertion Markup Language library (API docs)
 libsaml8   - Security Assertion Markup Language library (runtime)
 opensaml2-schemas - Security Assertion Markup Language library (XML schemas)
 opensaml2-tools - Security Assertion Markup Language command-line tools
Closes: 778047
Changes:
 opensaml2 (2.5.3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Call cpp with -P in boost config. Closes: #778047.
Checksums-Sha1:
 5133c9c501ad9bbed8caf4c19c646aaf08aac59b 2370 opensaml2_2.5.3-2.1.dsc
 551c88390d0be5a4d423aa3dd719

Bug#792595: marked as done (mediatomb-common: Licence clash with libmp4v2 (MPL) and mediatomb GPL-+2)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 12:01:57 -0400
with message-id 

and subject line Unreproducible
has caused the Debian Bug report #792595,
regarding mediatomb-common: Licence clash with libmp4v2 (MPL) and mediatomb 
GPL-+2
to be marked as done.

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

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


-- 
792595: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mediatomb-common
Version: 0.12.1-47-g7ab7616-1
Severity: serious

Dear Maintainer,

In mediatomb 0.12.1-7 libmp4v2 support has been disabled due to licence
problem and now libmp4v2 support has been enabled again...

Could you explain ?

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

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

Versions of packages mediatomb-common depends on:
ii  libavformat56  6:11.4-2
ii  libavutil546:11.4-2
ii  libc6  2.19-19
ii  libcurl3-gnutls7.43.0-1
ii  libexif12  0.6.21-2
ii  libexpat1  2.1.0-6+b3
ii  libffmpegthumbnailer4  2.0.8-2+b4
ii  libflac8   1.3.1-2
ii  libgcc11:5.1.1-14
ii  libjs-prototype1.7.1-3
ii  libmagic1  1:5.22+15-2
ii  libmozjs185-1.01.8.5-1.0.0+dfsg-4.3
ii  libmysqlclient18   5.6.25-2
ii  libnspr4   2:4.10.8-2
ii  libsqlite3-0   3.8.10.2-1
ii  libstdc++6 5.1.1-14
ii  libtag1c2a 1.9.1-2.1
ii  libuuid1   2.26.2-6
ii  zlib1g 1:1.2.8.dfsg-2+b1

mediatomb-common recommends no packages.

mediatomb-common suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
> Dear Maintainer,
>
> In mediatomb 0.12.1-7 libmp4v2 support has been disabled due to licence
> problem and now libmp4v2 support has been enabled again...
>
> Could you explain ?

Not sure what there is to explain since nothing about libmp4v2 has changed.

It still is compiled with "--disable-libmp4v2" and the package does
not depend on libmp4v2 in any architecture as partially shown by the
i386 example in the submitted bug report.

> Versions of packages mediatomb-common depends on:
> ii  libavformat56  6:11.4-2
> ii  libavutil546:11.4-2
> ii  libc6  2.19-19
> ii  libcurl3-gnutls7.43.0-1
> ii  libexif12  0.6.21-2
> ii  libexpat1  2.1.0-6+b3
> ii  libffmpegthumbnailer4  2.0.8-2+b4
> ii  libflac8   1.3.1-2
> ii  libgcc11:5.1.1-14
> ii  libjs-prototype1.7.1-3
> ii  libmagic1  1:5.22+15-2
> ii  libmozjs185-1.01.8.5-1.0.0+dfsg-4.3
> ii  libmysqlclient18   5.6.25-2
> ii  libnspr4   2:4.10.8-2
> ii  libsqlite3-0   3.8.10.2-1
> ii  libstdc++6 5.1.1-14
> ii  libtag1c2a 1.9.1-2.1
> ii  libuuid1   2.26.2-6
> ii  zlib1g 1:1.2.8.dfsg-2+b1
>
> mediatomb-common recommends no packages.
>
> mediatomb-common suggests no packages.
>
> -- no debconf information

The buildd logs show that the libmp4v2-dev  does not get installed either.

The only changes about libmp4v2 were updating the old libmp4v2 patch
that updated the code for newer libmp4v versions and reverting a
upstream commit which forced compilation with older libmp4v2 versions
but this was fixed by the 1st patch I mentioned.

I'm closing this bug but feel free to reopen if there is still an issue.

Hope this helps,
Miguel--- End Message ---

Bug#792595: Unreproducible

[Miguel A . Colón Vélez]

> Dear Maintainer,
>
> In mediatomb 0.12.1-7 libmp4v2 support has been disabled due to licence
> problem and now libmp4v2 support has been enabled again...
>
> Could you explain ?

Not sure what there is to explain since nothing about libmp4v2 has changed.

It still is compiled with "--disable-libmp4v2" and the package does
not depend on libmp4v2 in any architecture as partially shown by the
i386 example in the submitted bug report.

> Versions of packages mediatomb-common depends on:
> ii  libavformat56  6:11.4-2
> ii  libavutil546:11.4-2
> ii  libc6  2.19-19
> ii  libcurl3-gnutls7.43.0-1
> ii  libexif12  0.6.21-2
> ii  libexpat1  2.1.0-6+b3
> ii  libffmpegthumbnailer4  2.0.8-2+b4
> ii  libflac8   1.3.1-2
> ii  libgcc11:5.1.1-14
> ii  libjs-prototype1.7.1-3
> ii  libmagic1  1:5.22+15-2
> ii  libmozjs185-1.01.8.5-1.0.0+dfsg-4.3
> ii  libmysqlclient18   5.6.25-2
> ii  libnspr4   2:4.10.8-2
> ii  libsqlite3-0   3.8.10.2-1
> ii  libstdc++6 5.1.1-14
> ii  libtag1c2a 1.9.1-2.1
> ii  libuuid1   2.26.2-6
> ii  zlib1g 1:1.2.8.dfsg-2+b1
>
> mediatomb-common recommends no packages.
>
> mediatomb-common suggests no packages.
>
> -- no debconf information

The buildd logs show that the libmp4v2-dev  does not get installed either.

The only changes about libmp4v2 were updating the old libmp4v2 patch
that updated the code for newer libmp4v versions and reverting a
upstream commit which forced compilation with older libmp4v2 versions
but this was fixed by the 1st patch I mentioned.

I'm closing this bug but feel free to reopen if there is still an issue.

Hope this helps,
Miguel


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#777917: NMU diff

[Martin Michlmayr]

The NMU diff is attached.
-- 
Martin Michlmayr
Linux for HP Helion, Hewlett-Packard
diff -urN a/debian/changelog b/debian/changelog
--- a/debian/changelog	2010-05-17 02:14:02.0 -0400
+++ b/debian/changelog	2015-07-16 11:08:50.0 -0400
@@ -1,3 +1,12 @@
+ipgrab (0.9.10-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build failure with GCC 5.  Patch from Tim Potter. (Closes: #777917)
+  * Fix build failure with clang.  Patch from Arthur Marble. (Closes:
+#739562)
+
+ -- Martin Michlmayr   Thu, 16 Jul 2015 11:04:54 -0400
+
 ipgrab (0.9.10-1) unstable; urgency=low
 
   * New upstream release
diff -urN a/debian/patches/clang-ftbfs.patch b/debian/patches/clang-ftbfs.patch
--- a/debian/patches/clang-ftbfs.patch	1969-12-31 19:00:00.0 -0500
+++ b/debian/patches/clang-ftbfs.patch	2015-07-16 11:15:55.0 -0400
@@ -0,0 +1,14 @@
+Description: Fix build failure with clang
+Author: Arthur Marble
+
+--- ipgrab-0.9.10.orig/src/icmpv6.c
 ipgrab-0.9.10/src/icmpv6.c
+@@ -205,7 +205,7 @@ void dump_icmpv6(packet_t *pkt)
+ case ICMPV6_TYPE_NEIGHBORSOLICIT:
+   /* Skip 4 unused bytes */
+   if ( skip_packet_bytes (pkt,4) == 0 )
+- return 0;
++ return;
+ 
+   /* Next 16 bytes are an IPv6 address */
+   if (get_packet_bytes((u_int8_t *) &v6addr, pkt, 16) == 0)
diff -urN a/debian/patches/series b/debian/patches/series
--- a/debian/patches/series	2010-05-17 13:33:13.0 -0400
+++ b/debian/patches/series	2015-07-16 11:15:48.0 -0400
@@ -1,2 +1,3 @@
 segfault_amd64.patch
 spelling.patch
+clang-ftbfs.patch
diff -urN a/debian/rules b/debian/rules
--- a/debian/rules	2010-05-17 01:06:56.0 -0400
+++ b/debian/rules	2015-07-16 11:17:55.0 -0400
@@ -8,6 +8,8 @@
 # This is the debhelper compatability version to use.
 #export DH_COMPAT=3
 
+export CFLAGS=-g -O2 -std=gnu89
+
 configure: configure-stamp
 configure-stamp:
 	dh_testdir

Bug#777910: NMU patch

[Martin Michlmayr]

The NMU patch is attached.
-- 
Martin Michlmayr
Linux for HP Helion, Hewlett-Packard
diff -u icheck-0.9.7/debian/changelog icheck-0.9.7/debian/changelog
--- icheck-0.9.7/debian/changelog
+++ icheck-0.9.7/debian/changelog
@@ -1,3 +1,11 @@
+icheck (0.9.7-6.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build failure with compilers that default to C99 (clang
+and GCC 5).  Thanks to Tim Potter for the patch.  Closes: #777910
+
+ -- Martin Michlmayr   Thu, 16 Jul 2015 10:25:07 -0400
+
 icheck (0.9.7-6.1) unstable; urgency=high
 
   * Non-maintainer upload.
only in patch2:
unchanged:
--- icheck-0.9.7.orig/ext/CParse-Parser-PerlXS/PerlXS.xs
+++ icheck-0.9.7/ext/CParse-Parser-PerlXS/PerlXS.xs
@@ -1718,11 +1718,11 @@
   if (try_parse(self, punctuator, "*"))
 croak("Unhandled foo[*] construct");
 
-  bool restrict = false;
+  bool is_restrict = false;
   SV *expr = &PL_sv_undef;
   if (try_parse(self, type_qualifier, "restrict"))
 {
-  restrict = true;
+  is_restrict = true;
 }
   else
 {
@@ -1732,7 +1732,7 @@
   if (!try_parse(self, punctuator, "]"))
 return NULL;
 
-  return new_obj2("CParse::Declarator::Array", expr ? expr : &PL_sv_undef, restrict ? sv_2mortal(newSViv(1)) : &PL_sv_undef);
+  return new_obj2("CParse::Declarator::Array", expr ? expr : &PL_sv_undef, is_restrict ? sv_2mortal(newSViv(1)) : &PL_sv_undef);
 }
 
 static SV *

Bug#749915: marked as done (icheck: "restrict" used as variable (keyword in C99))

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 15:39:34 +
with message-id 
and subject line Bug#777910: fixed in icheck 0.9.7-6.2
has caused the Debian Bug report #777910,
regarding icheck: "restrict" used as variable (keyword in C99)
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.)


-- 
777910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: icheck
Version: 0.9.7-6.1
Severity: wishlist
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

The code uses "restrict" as the name of a local variable here:

http://sources.debian.net/src/icheck/0.9.7-6.1/ext/CParse-Parser-PerlXS/PerlXS.xs?hl=1721#L1721

This will fail the build in C99 mode, or when using Clang:

http://clang.debian.net/logs/2014-01-14/icheck_0.9.7-6.1_unstable_clang.log

Changing the name of that variable will fix the problem.

Best,
Michael



pgppg5fRq3rC4.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: icheck
Source-Version: 0.9.7-6.2

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

Debian distribution maintenance software
pp.
Martin Michlmayr  (supplier of updated icheck 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, 16 Jul 2015 10:25:07 -0400
Source: icheck
Binary: icheck
Architecture: source amd64
Version: 0.9.7-6.2
Distribution: unstable
Urgency: medium
Maintainer: Erinn Clark 
Changed-By: Martin Michlmayr 
Description:
 icheck - C interface ABI/API checker
Closes: 777910
Changes:
 icheck (0.9.7-6.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build failure with compilers that default to C99 (clang
 and GCC 5).  Thanks to Tim Potter for the patch.  Closes: #777910
Checksums-Sha1:
 b47affe83c564b6080736a2d56a2348a153086cc 1635 icheck_0.9.7-6.2.dsc
 319bdd48ec1cc5c01941e3ec7fd5d497269ce338 3358 icheck_0.9.7-6.2.diff.gz
 2a43c6355977ace136e088b4078d48a075635b65 70092 icheck_0.9.7-6.2_amd64.deb
Checksums-Sha256:
 ac2bcab5f5cba0c46c3ee188d52ba8b6b226a120879b0801b5ed64e36e9713eb 1635 
icheck_0.9.7-6.2.dsc
 9ae2bd426a219d894424db5737b16082dd4bfaf260395d860b906ea6dee58b50 3358 
icheck_0.9.7-6.2.diff.gz
 c43955dd1d6db4d38bbf426163304d3763e95750e6a6f9d2e418bddfa201f5f5 70092 
icheck_0.9.7-6.2_amd64.deb
Files:
 4d5bf106d0a0f1472f32c831af4a58d3 1635 devel optional icheck_0.9.7-6.2.dsc
 27a7095d409a270f0cab45828550a1cc 3358 devel optional icheck_0.9.7-6.2.diff.gz
 347d140df6ea575867609466d1872ad6 70092 devel optional 
icheck_0.9.7-6.2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJVp8zGAAoJED0Hh6qvbGHd0SEQAIE6vbWcMdtzTSM5FiNsejU8
9X1D1MMfyPIhIRdhc/ixP0mTScNy0RnwDl6McfyB17221Tk+Q3mh59zxYoCcG5nL
Mv7/yUF7SWXimEKb9Z/PYRafddsbTK6OvzqrftGAx52mSrT9wrpDewyRt45PXCOg
0/8j+VbXkH42xANsNaCs1/aeQBFYHwZ+jyHd2vVau8Didt4xeFcCtBjHSPUUL3MB
N5BMt95oPhghdmxzfr6Rr4rwJkrFuJ1ogtmWKywD2Hv4NYZ9kuHJE/I8Z3zH39Sa
0lbIbw75fotQ9APyDO5QPMwUXxvQ5HEFQkyFKWnpkZeux4bIef7mRMwinGYAL0go
2IE+aBvjEvTtd2l20TUSuXkanzwkM4+wTIuFP9BlZjqyJRLXl//dWxQkXVKj+Hm5
y4QDC+T6u7FWheg1XIilcg6MpgDSSUnnOYa8SJH2HmJCMoIePBj5Xn0VDCBnuwLQ
j3bS4644yBdPbxPorAmygim/xd9UI25ceZeyIscWY+Ai3IpmOdLVIecwVNXfAyev
DXo1DXWgmXl8JKmWEYPrrWs90gihr5IyXcjdxde4D+INVE/Or0UalnJhXbvkzL8L
gTyXG5Z3tIelAVF3y2fyBCzOtrHZd37EA2vYV14ZFmOzqq9RVqYy+rPbo8z+3lMw
HiFISr+CUPTMDA7SOFlG
=p7UL
-END PGP SIGNATURE End Message ---

Bug#777910: marked as done (icheck: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 15:39:34 +
with message-id 
and subject line Bug#777910: fixed in icheck 0.9.7-6.2
has caused the Debian Bug report #777910,
regarding icheck: ftbfs with GCC-5
to be marked as done.

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

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


-- 
777910: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:icheck
Version: 0.9.7-6.1
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/icheck_0.9.7-6.1_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
./typegen.pl > typegen.c.new
mv typegen.c.new typegen.c
gcc -std=gnu99 -o typegen typegen.c
./typegen > CType/Native.pm.new
mv CType/Native.pm.new CType/Native.pm
(cd ext/CParse-Parser-PerlXS && perl Makefile.PL INSTALLDIRS=vendor 
INSTALLVENDORLIB=/usr/share/icheck/perl5 
INSTALLVENDORARCH=/usr/lib/icheck/perl5 OPTIMIZE="-O2 -Wall -g")
Generating a Unix-style Makefile
Writing Makefile for CParse::Parser::PerlXS
Writing MYMETA.yml and MYMETA.json
/usr/bin/make -C ext/CParse-Parser-PerlXS
make[2]: Entering directory '/«PKGBUILDDIR»/ext/CParse-Parser-PerlXS'
cp PerlXS.pm blib/lib/CParse/Parser/PerlXS.pm
Running Mkbootstrap for CParse::Parser::PerlXS ()
chmod 644 PerlXS.bs
/usr/bin/perl /usr/share/perl/5.20/ExtUtils/xsubpp  -typemap 
/usr/share/perl/5.20/ExtUtils/typemap  PerlXS.xs > PerlXS.xsc && mv PerlXS.xsc 
PerlXS.c
cc -c  -I. -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv -fno-strict-aliasing 
-pipe -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -Wall 
-g   -DVERSION=\"0.1\" -DXS_VERSION=\"0.1\" -fPIC 
"-I/usr/lib/x86_64-linux-gnu/perl/5.20/CORE"   PerlXS.c
PerlXS.xs: In function 'try_direct_declarator_array_suffix':
PerlXS.xs:1721:17: error: expected identifier or '(' before '=' token
   bool restrict = false;
 ^
PerlXS.xs:1725:16: error: expected identifier or '(' before '=' token
   restrict = true;
^
PerlXS.xs:1735:76: error: expected expression before 'restrict'
   return new_obj2("CParse::Declarator::Array", expr ? expr : &PL_sv_undef, 
restrict ? sv_2mortal(newSViv(1)) : &PL_sv_undef);
^
PerlXS.xs:202:59: note: in definition of macro 'new_obj2'
 #define new_obj2(class, arg1, arg2) new_obj4(class, arg1, arg2, NULL, NULL)
   ^
PerlXS.xs:202:37: error: too few arguments to function 'new_obj4'
 #define new_obj2(class, arg1, arg2) new_obj4(class, arg1, arg2, NULL, NULL)
 ^
PerlXS.xs:1735:10: note: in expansion of macro 'new_obj2'
   return new_obj2("CParse::Declarator::Array", expr ? expr : &PL_sv_undef, 
restrict ? sv_2mortal(newSViv(1)) : &PL_sv_undef);
  ^
PerlXS.xs:173:1: note: declared here
 new_obj4 (char *class, SV *arg1, SV *arg2, SV *arg3, SV *arg4)
 ^
PerlXS.xs:1736:1: warning: control reaches end of non-void function 
[-Wreturn-type]
 }
 ^
make[2]: *** [PerlXS.o] Error 1
Makefile:334: recipe for target 'PerlXS.o' failed
make[2]: Leaving directory '/«PKGBUILDDIR»/ext/CParse-Parser-PerlXS'
make[1]: *** [parser-perlxs] Error 2
Makefile:208: recipe for target 'parser-perlxs' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
make: *** [debian/build-stamp] Error 2
debian/rules:5: recipe for target 'debian/build-stamp' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: icheck
Source-

Bug#792595: mediatomb-common: Licence clash with libmp4v2 (MPL) and mediatomb GPL-+2

[grossepoubelle]

Package: mediatomb-common
Version: 0.12.1-47-g7ab7616-1
Severity: serious

Dear Maintainer,

In mediatomb 0.12.1-7 libmp4v2 support has been disabled due to licence
problem and now libmp4v2 support has been enabled again...

Could you explain ?

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

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

Versions of packages mediatomb-common depends on:
ii  libavformat56  6:11.4-2
ii  libavutil546:11.4-2
ii  libc6  2.19-19
ii  libcurl3-gnutls7.43.0-1
ii  libexif12  0.6.21-2
ii  libexpat1  2.1.0-6+b3
ii  libffmpegthumbnailer4  2.0.8-2+b4
ii  libflac8   1.3.1-2
ii  libgcc11:5.1.1-14
ii  libjs-prototype1.7.1-3
ii  libmagic1  1:5.22+15-2
ii  libmozjs185-1.01.8.5-1.0.0+dfsg-4.3
ii  libmysqlclient18   5.6.25-2
ii  libnspr4   2:4.10.8-2
ii  libsqlite3-0   3.8.10.2-1
ii  libstdc++6 5.1.1-14
ii  libtag1c2a 1.9.1-2.1
ii  libuuid1   2.26.2-6
ii  zlib1g 1:1.2.8.dfsg-2+b1

mediatomb-common recommends no packages.

mediatomb-common suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: limit source to nagios3, tagging 791840

[Debian Bug Tracking System]

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

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

> tags 791840 + pending
Bug #791840 [src:nagios3] nagios3: FTBFS on sid due to unsatisfiable 
build-dependency on libgd2-(no)xpm-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#783552: Useless (superseded by native features)

[Mike Gabriel]

HI David,

On  Di 28 Apr 2015 00:11:59 CEST, David Prévot wrote:


Package: xul-ext-fullscreen
Version: 1.0.4-1
Severity: serious

[Filled as RC by a team member to see it autoremoved from testing if
 nobody disagrees. Please, do downgrade it with an explanation if you
 disagree.]

As far as I can tell, the native fullscreen feature (F11) of current
iceweasel versions provides the actual fullscreen this extension used to
provide (I was an happy user of it with my 9” screen eeepc a few years
ago).

There hasn’t been any upstream release since almost four years, and the
popcon is very low.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).


I have looked into iceweasel and fullscreen stuff today.

My proposal: remove the current fullscreen-extension package from  
Debian and package ff-fullscreen [1].


I have started working on ff-fullscreen already (for a customer  
project). It needs some patches here and there, but works well with  
Iceweasel in jessie.


Mike

[1] https://addons.mozilla.org/de/firefox/addon/ff_fullscreen/
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


pgp4jtjSVLbAy.pgp
Description: Digitale PGP-Signatur

Bug#777910: Fix for gcc5 compile failure

[Martin Michlmayr]

* Potter, Tim (Cloud Services)  [2015-07-15 22:39]:
> The maintainer has signed up for LowThresholdNMU so I recommend that
> this package be NMU’d with this patch to close this bug.

Thanks, Tim, will do.

-- 
Martin Michlmayr
Linux for HP Helion, Hewlett-Packard


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#792361: redmine: dpkg --configure broken when installing ruby packages

[Pirate Praveen]

On Tuesday 14 July 2015 06:33 PM, Antonio Terceiro wrote:
> This has nothing to do with redmine, but with the fact that
> ruby-jquery-rails was upgraded to a version that breaks the redmine
> dependency checking.

Can I upload ruby-jquery-rails3 to fix the situation?

jquery-rails 4.0.4 require railties >= 4.2 as well. What is the plan for
updating to rails 4.2?



signature.asc
Description: OpenPGP digital signature

Bug#792586: openstack-dashboard - fails to install: SyntaxError: Undefined variable: '$brand-danger'.

[Bastian Blank]

Package: openstack-dashboard
Version: 2015.1.0+2015.06.09.git15.e63af6c598-1
Severity: serious

openstack-dashboard fails to install:

| Found 'compress' tags in:
| 
/usr/share/openstack-dashboard/openstack_dashboard/templates/_stylesheets.html
| /usr/lib/python2.7/dist-packages/horizon/templates/horizon/_conf.html
| 
/usr/lib/python2.7/dist-packages/horizon/templates/horizon/_scripts.html
| Compressing... WARNING:scss:File to import not found or unreadable: 
'/horizon/lib/bootstrap_datepicker/datepicker3.css' (:0)
| WARNING:scss:File to import not found or unreadable: 
'/horizon/lib/rickshaw.css' (:0)
| WARNING:scss:File to import not found or unreadable: '/custom/variables' 
(:0)
| WARNING:scss:File to import not found or unreadable: 
'/bootstrap/scss/bootstrap/variables' 
(/usr/share/openstack-dashboard/static/dashboard/scss/_variables.scss:8)
| CommandError: An error occured during rendering 
/usr/share/openstack-dashboard/openstack_dashboard/templates/_stylesheets.html: 
Error evaluating expression:
| $brand-danger
| 
| From /usr/share/openstack-dashboard/static/dashboard/scss/_variables.scss:8
| ...imported from :0
| Traceback:
|   File "/usr/lib/python2.7/dist-packages/scss/expression.py", line 130, in 
evaluate_expression
| return ast.evaluate(self, divide=divide)
|   File "/usr/lib/python2.7/dist-packages/scss/expression.py", line 359, in 
evaluate
| raise SyntaxError("Undefined variable: '%s'." % self.name)
| SyntaxError: Undefined variable: '$brand-danger'.
| dpkg: error processing package openstack-dashboard (--configure):
|  subprocess installed post-installation script returned error exit status 1

Bastian

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

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


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790530: marked as done (astropy-utils: bump Breaks+Replaces to python-pyfits (<< 1:3.0.7-4~))

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 13:19:52 +
with message-id 
and subject line Bug#790530: fixed in python-astropy 1.0.3-3
has caused the Debian Bug report #790530,
regarding astropy-utils: bump Breaks+Replaces to python-pyfits (<< 1:3.0.7-4~)
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.)


-- 
790530: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: astropy-utils
Version: 1.0.3-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + pyfits-utils

Hi,

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

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

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

  Selecting previously unselected package astropy-utils.
  Preparing to unpack .../astropy-utils_1.0.3-2_all.deb ...
  Unpacking astropy-utils (1.0.3-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/astropy-utils_1.0.3-2_all.deb (--unpack):
   trying to overwrite '/usr/bin/fitsdiff', which is also in package 
pyfits-utils 1:3.3-3
  Preparing to unpack .../pyfits-utils_1%3a3.3-4_all.deb ...
  Unpacking pyfits-utils (1:3.3-4) over (1:3.3-3) ...
  Preparing to unpack .../python-pyfits_1%3a3.3-4_amd64.deb ...
  Unpacking python-pyfits (1:3.3-4) over (1:3.3-3) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/astropy-utils_1.0.3-2_all.deb


The upload of pyfits-utils 1:3.3-4 finally turned this into a
transitional package, so update the Breaks+Replaces accordingly.

The (<< 1:3.3-2) given in #782817 was wrong to start with :-(


cheers,

Andreas


pyfits-utils_1:3.3-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-astropy
Source-Version: 1.0.3-3

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated python-astropy 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, 16 Jul 2015 10:46:32 +0200
Source: python-astropy
Binary: python-astropy python3-astropy python-astropy-doc astropy-utils
Architecture: source all amd64
Version: 1.0.3-3
Distribution: unstable
Urgency: low
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Description:
 astropy-utils - Command line tools from astropy
 python-astropy - Core functionality for performing astrophysics with Python
 python-astropy-doc - Core functionality for performing astrophysics with 
Python (doc)
 python3-astropy - Core functionality for performing astrophysics with Python3
Closes: 790530
Changes:
 python-astropy (1.0.3-3) unstable; urgency=low
 .
   * Extend Suggests, and build/test-depend on scipy for more extended tests
   * Fix conflicts/replaces of astropy-utils with pyfits-utils. Closes: #790530
   * Temporarily remove dh_strip_nondeterminism
   * Override image-file-in-usr-lib lintian
Checksums-Sha1:
 1c44e855dc1c1a45331139cc89eab537284d37ac 2691 python-astropy_1.0.3-3.dsc
 7c8db050d79615ea6b5723d0abd5b1a1ac3f7173 13880 
python-astropy_1.0.3-3.debian.tar.xz
 7a5ac6fe096ef24bb2be22fcab20eb53fb48448f 13798 astropy-utils_1.0.3-3_all.deb
 4b5293d395ebf8c07b5f1c360f4594b6e68f5e7b 10054178 
python-astropy-doc_1.0.3-3_all.deb
 aa203407fc3a684f18dc4404fe563be3e4287865 2622122 
python-astropy_1.0.3-3_amd64.deb
 0f90dc9402e9872409c3476e8ff9975bf2e06741 2609598 
python3-astropy_1.0.3-3_amd64.deb
Checksums-Sha256:
 8ae770c0eef38806ad8e79e55335e8e9e90990cbd4e57b98e52cc4a3a0a1f7a4 2691 
python-astropy_1.0.3-3.dsc
 0ddf17bbdd38cde4e8bc3da7c819d2e466cc5ed0ee8c6e962137412f94f05cbd 13880 
python-astropy_1.0.3-3.debian.tar.xz
 b8451f4afbe3360ebab2bf3fc713b86d8c18d5b82b4ec800ff12f5dd70095285 13798 
astropy-utils_1.0.3-3_all.deb
 a930216ed4f1b4cccf6cdb58a7bd85aab

Processed: re: FTBFS in unstable due to build-depends on libmysqlclient15-dev

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #790453 [libnss-mysql-bg] FTBFS in unstable due to build-depends on 
libmysqlclient15-dev
Added tag(s) patch.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790453: FTBFS in unstable due to build-depends on libmysqlclient15-dev

[Hideki Yamane]

control: tags -1 patch

Hi,

 Here's a tiny patch for this FTBFS.
 

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane
diff -Nru libnss-mysql-bg-1.5/debian/changelog libnss-mysql-bg-1.5/debian/changelog
--- libnss-mysql-bg-1.5/debian/changelog	2012-04-18 18:56:45.0 +0900
+++ libnss-mysql-bg-1.5/debian/changelog	2015-07-16 16:40:11.0 +0900
@@ -1,3 +1,11 @@
+libnss-mysql-bg (1.5-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/conttrol
+- s/libmysqlclient15-dev/libmysqlclient-dev/ to fix FTBFS (Closes: #790453)
+
+ -- Hideki Yamane   Thu, 16 Jul 2015 16:38:54 +0900
+
 libnss-mysql-bg (1.5-3) unstable; urgency=low
 
   * Add patch from Harald Weidner to follow the Debian policy in the way shadow
diff -Nru libnss-mysql-bg-1.5/debian/control libnss-mysql-bg-1.5/debian/control
--- libnss-mysql-bg-1.5/debian/control	2012-04-18 18:45:06.0 +0900
+++ libnss-mysql-bg-1.5/debian/control	2015-07-16 16:38:52.0 +0900
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Emmanuel Lacour 
-Build-Depends: debhelper (>= 9), libmysqlclient15-dev, quilt (>= 0.40), autotools-dev, dh-autoreconf
+Build-Depends: debhelper (>= 9), libmysqlclient-dev, quilt (>= 0.40), autotools-dev, dh-autoreconf
 Standards-Version: 3.9.3
 
 Package: libnss-mysql-bg

Bug#784671: fixed in gdm3 3.14.1-8

[Mert Dirik]

> Source: gdm3
> Binary: gdm3 libgdm1 libgdm-dev gir1.2-gdm3
> Architecture: source amd64
> Version: 3.14.1-8
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian GNOME Maintainers 


> Changed-By: Laurent Bigonville 
> Description:
> gdm3 - GNOME Display Manager
> gir1.2-gdm3 - GObject introspection data for the GNOME Display Manager
> libgdm-dev - GNOME Display Manager (development files)
> libgdm1 - GNOME Display Manager (shared library)
> Closes: 784671
> Changes:
> gdm3 (3.14.1-8) unstable; urgency=medium
> .
> * d/p/07_fix_caribou_path.patch: Fix the path to the caribou daemon 
in the

> autostart desktop file (Closes: #784671)

Any chance this will be pushed to jessie-pu?


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791830: marked as done (bedtools: FTBFS on mipsel)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 12:48:51 +
with message-id 
and subject line Bug#791830: fixed in bedtools 2.24.0-2
has caused the Debian Bug report #791830,
regarding bedtools: FTBFS on mipsel
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.)


-- 
791830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bedtools
Severity: serious
Tags: upstream
Justification: fails to build from source

Dear maintainer,

as you can see at buildd [0], bedtools FTBFS on mipsel.

I just want to let you know I've reproduced the issue locally in my mipsel 
machine and I'm working towards a fix.

best regards.
--- End Message ---
--- Begin Message ---
Source: bedtools
Source-Version: 2.24.0-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated bedtools 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, 16 Jul 2015 14:33:38 +0200
Source: bedtools
Binary: bedtools bedtools-test
Architecture: source amd64 all
Version: 2.24.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 bedtools   - suite of utilities for comparing genomic features
 bedtools-test - test data for the bedtools package
Closes: 791830
Changes:
 bedtools (2.24.0-2) unstable; urgency=medium
 .
   * Tests need bgzip from tabix package
   * Add missing input files for tests
   * link to genomes files in autopkgtests to enable more tests passing
   * Fix MIPS build issue (Thanks for picking the patch from upstream
 Arturo Borrero Gonzalez )
 Closes: #791830
Checksums-Sha1:
 3707fa6b3f0b9f9fd6f5610d676eda45db133fa4 2071 bedtools_2.24.0-2.dsc
 4d0b500e22c6312dbe9a36aaef8a5ba152598aaf 9256 bedtools_2.24.0-2.debian.tar.xz
 bb1b9fb4d91df607b49e134062efad252b607c90 622760 bedtools_2.24.0-2_amd64.deb
 744e42314666d0687092dd1d2dbdce5df6bb64e2 10411174 
bedtools-test_2.24.0-2_all.deb
Checksums-Sha256:
 a9cca6c400f6179c35835f54c57cbd480efd5dc75090924113e2b6dfd76349e3 2071 
bedtools_2.24.0-2.dsc
 3c91808ba151a9d8157212acba2323569faaf7aad9dca0735e93ada846326a3c 9256 
bedtools_2.24.0-2.debian.tar.xz
 5e134d497bdada0b2d1b1048c1c1f51be535e2cd92a8741429fb76a09607a2bc 622760 
bedtools_2.24.0-2_amd64.deb
 bb813f1bc4a1e2e26ede6cee04963fbe8463fac050c9b7a23e6024cdbbc7ed91 10411174 
bedtools-test_2.24.0-2_all.deb
Files:
 fcd33afa6592d63c53185dbaefc7266a 2071 science optional bedtools_2.24.0-2.dsc
 88133a3e540eb3f43ddda54c9c23d18d 9256 science optional 
bedtools_2.24.0-2.debian.tar.xz
 af70200d70afbff5f395db4294534588 622760 science optional 
bedtools_2.24.0-2_amd64.deb
 d9bbfa4ceccb21b8fc2383dcf2454f68 10411174 science optional 
bedtools-test_2.24.0-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJVp6YjAAoJEFeKBJTRxkbRIasP/0gnJ05FtM/wXuDuNMEBpSGN
AS5HQhY1UmeNGqOZxvspJx2+Q3lv+PARxwCxQW/gfX2S7sr26vEhINon3cKS00vs
zTCrm2roO0bjEY6kDav2u4a6fwEk3rNpcSD/+4vt24iq0KhQBtiEVOJ6pyGW3/gb
fMCmNrJmu7J49yui98ZXJIEEIhgyV4IT0MhzAY0N6NHd23P0AcXqqdZElOCtYhDB
lA/V9lQGFQNdyATps1NyHyftH3apoOD40Cwc2Q8PEMyf8geiJPM+R/S74qTrp3ON
NMnUlqGnfx31qskLaLkRCDJftBwTbpR3TJ1knDZ5OzG/5AbTMS8EuHu5HJ+7aXV3
VqS5k68Qv6eopdqTxybVX6OZufWJTLjsuwIJygOoXcQhm7knTgp4cZ9LT6JB6a+M
NklugRAQTRG4Nqp27EiJ5frGeD/TRz3bCskWOLnOmKra35h5Ql/nGiFbZXbC1IDv
Q8OnZLWVsD+qfjhsI9blxDU9NUEG5kE+k64XuTGEGsX8ajgfu7CNbpnryQ6CyGji
Ru6J2LvKEm1oPTwTnPJ5tcrUJpfyt5iK7XnD2j5CgpDJNEQCPgj5D0VNds2TC0es
I5xEshQ11ZzekgIT4Dj+g91Gnu69LCGsvWg2TheCA7DrmkEqhe8XbbmHd43s2BU6
bvIX+YazXX6oFZNLOVnX
=qbzs
-END PGP SIGNATURE End Message ---

Bug#791891: marked as done (kde-config-touchpad: fails to upgrade from 'sid' - trying to overwrite /usr/share/icons/hicolor/128x128/devices/input-touchpad.png)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 08:09:18 -0400
with message-id <3622126.tfHXG7okch@kitterma-e6430>
and subject line Package will be removed
has caused the Debian Bug report #791891,
regarding kde-config-touchpad: fails to upgrade from 'sid' - trying to 
overwrite /usr/share/icons/hicolor/128x128/devices/input-touchpad.png
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.)


-- 
791891: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-config-touchpad
Version: 4:5.1.95-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package kde-config-touchpad.
  Preparing to unpack .../kde-config-touchpad_4%3a5.1.95-1_amd64.deb ...
  Unpacking kde-config-touchpad (4:5.1.95-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-touchpad_4%3a5.1.95-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/share/icons/hicolor/128x128/devices/input-touchpad.png', which is also in 
package plasma-desktop-data 4:5.3.2-1
  Processing triggers for systemd (222-1) ...
  Errors were encountered while processing:
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
   /var/cache/apt/archives/kde-config-touchpad_4%3a5.1.95-1_amd64.deb

Maybe this bug needs to be reassigned to plasma-desktop-data
since that has a newer version (5.3.2) than kde-config-touchpad (5.1.95).


cheers,

Andreas


plasma-desktop-data=4%5.3.2-1_kde-config-touchpad=4%5.1.95-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
kcm-touchpad was only in experimental and will be removed, so this bug should 
just be closed.--- End Message ---

Processed: tag patch #791830 bedtools

[Debian Bug Tracking System]

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

> tags 791830 patch
Bug #791830 [src:bedtools] bedtools: FTBFS on mipsel
Added tag(s) patch.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#788561: Bug RC #788561 (python3-memcache not Python 3 compatible)

[Thomas Goirand]

On 07/13/2015 11:02 AM, Hugo Lefeuvre wrote:
> Hi Thomas,
> 
>> Yes, that's the way to go. I think it's better to go directly for the
>> removal of python3-memcached in fact.
> 
> I've prepared the diff that I'd like to suggest to the release team.
> Could you have a look at it ? The diff is in attachement.
> 
> I've decided to just make the package stops building python3-memcache. I
> haven't reverted the upstream changes you made on the package; I think
> it wouldn't be really useful, and it will surely make the backporting 
> process harder.
> 
> Thanks !
> 
> Cheers,
>  Hugo

The diff looks ok, and I do support this. Please push it to the release
team. I really think this is the most reasonable course of action we can
do in Jessie.

Cheers,

Thomas Goirand (zigo)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#791830: patch fix for bedtools FTBFS on mipsel

[Arturo Borrero Gonzalez]

control: -1 tags + patch

Dear maintainer,

find attached a patch to fix the FTBFS issue on mipsel.
The patch was generated from a upstream commit [0].

I tested it in my mipsel machine and it works :-)

Thanks, best regards.

[0] 
https://github.com/arq5x/bedtools2/commit/b47dbefcb57f8e6c4fe397f64346338620740b71

-- 
Arturo Borrero González
From b47dbefcb57f8e6c4fe397f64346338620740b71 Mon Sep 17 00:00:00 2001
From: arq5x 
Date: Wed, 15 Jul 2015 15:15:23 -0600
Subject: [PATCH] settle on uint32_t signature for QuickString. Resolves #267
 and #271?

---
 src/coverageFile/coverageFile.cpp |   24 
 src/utils/general/QuickString.cpp |   27 ++-
 src/utils/general/QuickString.h   |6 +++---
 3 files changed, 29 insertions(+), 28 deletions(-)

diff --git a/src/coverageFile/coverageFile.cpp b/src/coverageFile/coverageFile.cpp
index 859cfdc..0fb544b 100644
--- a/src/coverageFile/coverageFile.cpp
+++ b/src/coverageFile/coverageFile.cpp
@@ -83,11 +83,11 @@ void CoverageFile::giveFinalReport(RecordOutputMgr *outputMgr) {
 		float depthPct = (float)basesAtDepth / (float)_totalQueryLen;
 
 		_finalOutput = "all\t";
-		_finalOutput.append(depth);
+		_finalOutput.append(static_cast(depth));
 		_finalOutput.append("\t");
-		_finalOutput.append(basesAtDepth);
+		_finalOutput.append(static_cast(basesAtDepth));
 		_finalOutput.append("\t");
-		_finalOutput.append(_totalQueryLen);
+		_finalOutput.append(static_cast(_totalQueryLen));
 		_finalOutput.append("\t");
 		format(depthPct);
 
@@ -138,7 +138,7 @@ size_t CoverageFile::countBasesAtDepth(size_t depth) {
 
 void CoverageFile::doCounts(RecordOutputMgr *outputMgr, RecordKeyVector &hits)
 {
-	_finalOutput = hits.size();
+	_finalOutput = static_cast(hits.size());
 	outputMgr->printRecord(hits.getKey(), _finalOutput);
 }
 
@@ -147,9 +147,9 @@ void CoverageFile::doPerBase(RecordOutputMgr *outputMgr, RecordKeyVector &hits)
 	//loop through all bases in query, printing full record and metrics for each
 	const Record * queryRec = hits.getKey();
 	for (size_t i= 0; i < _queryLen; i++) {
-		_finalOutput = i +1;
+		_finalOutput = static_cast(i+1);
 		_finalOutput.append("\t");
-		_finalOutput.append(_depthArray[i]);
+		_finalOutput.append(static_cast(_depthArray[i]));
 
 		outputMgr->printRecord(queryRec, _finalOutput);
 	}
@@ -181,11 +181,11 @@ void CoverageFile::doHist(RecordOutputMgr *outputMgr, RecordKeyVector &hits)
 		size_t numBasesAtDepth = iter->second;
 		float coveredBases = (float)numBasesAtDepth / (float)_queryLen;
 
-		_finalOutput = depth;
+		_finalOutput = static_cast(depth);
 		_finalOutput.append("\t");
-		_finalOutput.append(numBasesAtDepth);
+		_finalOutput.append(static_cast(numBasesAtDepth));
 		_finalOutput.append("\t");
-		_finalOutput.append(_queryLen);
+		_finalOutput.append(static_cast(_queryLen));
 		_finalOutput.append("\t");
 		format(coveredBases);
 
@@ -199,11 +199,11 @@ void CoverageFile::doDefault(RecordOutputMgr *outputMgr, RecordKeyVector &hits)
 	size_t nonZeroBases = _queryLen - countBasesAtDepth(0);
 	float coveredBases = (float)nonZeroBases / (float)_queryLen;
 
-	_finalOutput = hits.size();
+	_finalOutput = static_cast(hits.size());
 	_finalOutput.append("\t");
-	_finalOutput.append(nonZeroBases);
+	_finalOutput.append(static_cast(nonZeroBases));
 	_finalOutput.append("\t");
-	_finalOutput.append(_queryLen);
+	_finalOutput.append(static_cast(_queryLen));
 	_finalOutput.append("\t");
 	format(coveredBases);
 
diff --git a/src/utils/general/QuickString.cpp b/src/utils/general/QuickString.cpp
index 0757009..a83263e 100644
--- a/src/utils/general/QuickString.cpp
+++ b/src/utils/general/QuickString.cpp
@@ -105,11 +105,11 @@ QuickString &QuickString::operator = (uint32_t val) {
 	return *this;
 }
 
-QuickString &QuickString::operator = (size_t val) {
-	clear();
-	append(val);
-	return *this;
-}
+// QuickString &QuickString::operator = (size_t val) {
+// 	clear();
+// 	append(val);
+// 	return *this;
+// }
 
 QuickString &QuickString::operator = (float val) {
 	clear();
@@ -158,10 +158,11 @@ QuickString &QuickString::operator += (uint32_t num) {
 	return *this;
 }
 
-QuickString &QuickString::operator += (size_t num) {
-	append(num);
-	return *this;
-}
+// QuickString &QuickString::operator += (size_t num) {
+// 	append(num);
+// 	return *this;
+// }
+
 QuickString &QuickString::operator += (float num) {
 	append(num);
 	return *this;
@@ -273,12 +274,12 @@ void QuickString::append(int num) {
 }
 
 void QuickString::append(uint32_t num) {
-	int2str((int)num, *this, true);
+ 	int2str((int)num, *this, true);
 }
 
-void QuickString::append(size_t num) {
-	int2str((int)num, *this, true);
-}
+// void QuickString::append(size_t num) {
+// 	int2str((int)num, *this, true);
+// }
 
 void QuickString::append(float num) {
 	append(ToString(num));
diff --git a/src/utils/general/QuickString.h b/src/utils/general/QuickString.h
index b43fdfc..6e6fa94 100644
--- a/src/utils/general/QuickString.h
+++ b/src/utils/genera

Bug#792535: marked as done (makepasswd: Is GPL-2 licensed, but (explicitly) uses OpenSSL)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 11:49:17 +
with message-id 
and subject line Bug#792535: fixed in makepasswd 1.10-10
has caused the Debian Bug report #792535,
regarding makepasswd: Is GPL-2 licensed, but (explicitly) uses OpenSSL
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.)


-- 
792535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: makepasswd
Version: 1.10-9
Severity: serious

The program in your package makes use of the OpenSSL
library, but is GPL-licensed. Depending on interpretation,
this might mean that the package is not redistributable.
(And a core dump of a process is definitely not distributable,
preventing debugging)

I'd advise switching to something else instead that
has a GPL-compatible license.

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

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

Versions of packages makepasswd depends on:
ii  libcrypt-openssl-random-perl  0.04-2+b1
ii  libcrypt-passwdmd5-perl   1.3-10
ii  perl  5.20.2-6

makepasswd recommends no packages.

makepasswd suggests no packages.

-- no debconf information

-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.

Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
- If you don't I might ignore you.
--- End Message ---
--- Begin Message ---
Source: makepasswd
Source-Version: 1.10-10

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated makepasswd 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, 16 Jul 2015 11:45:20 +0100
Source: makepasswd
Binary: makepasswd
Architecture: source all
Version: 1.10-10
Distribution: unstable
Urgency: low
Maintainer: Colin Watson 
Changed-By: Colin Watson 
Description:
 makepasswd - Generate and encrypt passwords
Closes: 792535
Changes:
 makepasswd (1.10-10) unstable; urgency=low
 .
   * Move debian/source.lintian-overrides to preferred location of
 debian/source/lintian-overrides.
   * Convert from Crypt::OpenSSL::Random to Bytes::Random::Secure (closes:
 #792535).
Checksums-Sha1:
 b66805739e2f0c4aef7e01db3e6007e5d6155774 1848 makepasswd_1.10-10.dsc
 2ac863741c3bebecc6ea11a14aa8a0d2c6dc7a92 8158 makepasswd_1.10-10.diff.gz
 0dbae295d87c2102e327243f740d5f55c6f893eb 11744 makepasswd_1.10-10_all.deb
Checksums-Sha256:
 02df62f3ca8684951eb6a4eadefb6b0bcc0eb04bf0fc58cf172abd9938991a0f 1848 
makepasswd_1.10-10.dsc
 f552c468789c8ed326fd1506c93f04378085a198e332ac206539367948c4ad93 8158 
makepasswd_1.10-10.diff.gz
 c33b576fc391c91fe82da5bcbb69f8edeb4d535fce3cc80f155e45dea687b501 11744 
makepasswd_1.10-10_all.deb
Files:
 3b87b530a1d571d9a994118d20111f51 1848 admin optional makepasswd_1.10-10.dsc
 e9ec121ed24c08f7b9b21b325f3a9fef 8158 admin optional makepasswd_1.10-10.diff.gz
 dd7b7cfae046221e49b649662f729423 11744 admin optional 
makepasswd_1.10-10_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Colin Watson  -- Debian developer

iQIVAwUBVaeWPjk1h9l9hlALAQgf/g//aplkSOaPQkxStg1LTxq291E+bHDOx7Bk
QiduQJodkI9dlCexwPUhVwO8iMvPuY0S8nCR008fqz89Lez8HMXv8R4FwHXchF1O
iSKdwSLJZeDiElZO0L/+1xUpJv3wx0rCJfNfxbw7XxdM8vh+EG1FQ+2CMk09yAqD
J8T4ww6+SIcssLeeI8UZU6iUSSJkNjZj5EikI+J2ZtY2setrGaiugn7pcTcjy1Br
SIwC6GEHi5j8PAdH/aMRONbhhgdHD7d9bd0PC3sQ3g3O6olgymPcwglBs6143gMO
Ret4IUb0dZ18IY2jJWJVADh4ekwhhl3C1bxd58uRBEkzX7S+xFz3K9ma24JW9TZ0
U8bNtN1PL6PjAayx1aB9ZtiB5zzreEg/GA1e/ltMWy1WAaAE1rMkXKRr5f85iaHn
joLtE41hB73th/KC2zZIYaGF/pPLb45OjiW9lSlCNNWEX2mXInqe53xn7e1nQS7b
1jRvc3LEkt7pmqNJ5GEH3Z4gbV6Bom2xX3HNTEbtJf57OstwFRHRijXE/MWMKKoz
oEtF2NBpcV1jCrYmgsXzTnKJwc+IrxRxGnQ

Bug#792524: NVIDIA issue

[Daniel Pocock]

Regardless of whether the gnome-shell/mutter log line means anything, I
don't think the NVIDIA driver should be failing with a seg fault, so I
also filed a copy of the stack on the NVIDIA forum:

https://devtalk.nvidia.com/default/topic/856765/linux/crash-report/


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#792498: [pkg-go] Bug#792498: prometheus.postinst: adduser: not found

[Martín Ferrari]

On 15/07/15 14:43, Jakub Wilk wrote:
> Package: prometheus
> Version: 0.14.0+ds-1
> Severity: serious
> Justification: Policy §3.5

Thanks for reporting!

I have just commited the fix to Git and will upload soon.


-- 
Martín Ferrari (Tincho)


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#770229: marked as done (CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 11:00:22 +
with message-id 
and subject line Bug#770229: fixed in wolfssl 3.4.8+dfsg-1
has caused the Debian Bug report #770229,
regarding CVE-2014-2901 CVE-2014-2902 CVE-2014-2903 CVE-2014-2904
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.)


-- 
770229: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyassl
Severity: grave
Tags: security

Please see https://marc.info/?l=oss-security&m=139779940032403&w=2

On a related note:
I noticed that mysql/mariadb hasn't switched to using cyassl. Without
any rev deps we should rather avoid including it in jessie IMO and
base on cyassl for jessie+1.

Cheers,
Moritz

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

Kernel: Linux 3.16-2-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
--- End Message ---
--- Begin Message ---
Source: wolfssl
Source-Version: 3.4.8+dfsg-1

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

Debian distribution maintenance software
pp.
Felix Lechner  (supplier of updated wolfssl 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: Sun, 26 Apr 2015 08:23:52 -0700
Source: wolfssl
Binary: libcyassl5 libwolfssl0 libwolfssl-dev libwolfssl0-dbg
Architecture: source amd64
Version: 3.4.8+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Felix Lechner 
Changed-By: Felix Lechner 
Description:
 libcyassl5 - transitional dummy package with compatibility links
 libwolfssl-dev - Development files for the WolfSSL encryption library
 libwolfssl0 - WolfSSL encryption library
 libwolfssl0-dbg - Debug symbols for the WolfSSL encryption library
Closes: 769905 770229
Changes:
 wolfssl (3.4.8+dfsg-1) unstable; urgency=medium
 .
   * Name of package changed from 'cyassl' to 'wolfssl'
   * New upstream release
   * Disabled automatic downgrade to SSLv3 in release 3.2.0 (Closes: #769905)
   * Fixed CVE-2014-2901, CVE-2014-2902, CVE-2014-2903 and CVE-2014-2904
   in release 3.2.0 (Closes: #770229)
   * Fixed TEMP-000-2D36D7 in release 3.2.0
   * Added build option '--enable-chacha'
   * Added build option '--enable-poly1305'
   * Added build option '--enable-hashdrbg'
   * Added build option '--use-fastmath'
   * Added build option '--enable-ecc25519'
   * Added build flag TFM_TIMING_RESISTANT
   * Added build flag TFM_NO_ASM
   * Added Build-Depends: libpcap0.8-dev for sniffer testing
   * Removed obsolete build option '--enable-gcc-hardening'
   * Removed LT_LIB_M in configure.ac to avoid linking uselessly with libm
   * Enabled tests
   * Added Exclude-Files: in 'copyright' for automatic repackaging
   * Added repacksuffix=+dfsg in 'watch'
   * Updated to Standards-Version: 3.9.6
   * Added dummy package for 'libcyassl5'
   * Replaces: libcyassl5 (<< 3.4.2-1~)
   * Breaks: libcyassl5 (<< 3.4.2-1~)
   * Provides: libcyassl5
   * Created compatibility symlinks for libcyassl.so.5.0.0
Checksums-Sha1:
 9e0f3d2d4256a143406c54b6b7a14454879fb98d 1646 wolfssl_3.4.8+dfsg-1.dsc
 8f00d26ca0355f21d2490776ea71b797332b4f1a 954905 wolfssl_3.4.8+dfsg.orig.tar.gz
 dce7e7021dfccf739f4bf05cfda26effed3294a1 9944 
wolfssl_3.4.8+dfsg-1.debian.tar.xz
 c89b87fb49ce12251053cda7004189a7fbec48c7 3726 libcyassl5_3.4.8+dfsg-1_amd64.deb
 b3a185fb45dac0cb1c2666be7845217ce42b8e9c 951792 
libwolfssl-dev_3.4.8+dfsg-1_amd64.deb
 f56210bc559dc2bba2cf6c663ee2e56110af1488 655158 
libwolfssl0-dbg_3.4.8+dfsg-1_amd64.deb
 43fccdc810a9f2cb72d032498118e2da40909f4b 216062 
libwolfssl0_3.4.8+dfsg-1_amd64.deb
Checksums-Sha256:
 7ce5b446167a2171f940a7d94b6c96fb876d11b7d6d5995c3bebf2f20b553b76 1646 
wolfssl_3.4.8+dfsg-1.dsc
 a9bc053a44e7ac93e783ee41ce7d63b26c9e4783c71c842659902fee1113c1fb 954905 
wolfssl_3.4.8+dfsg.orig.tar.gz
 d2d726ce3c4e1d30974f0473b9571b516f0a715681a36425bf4629a6531b05fc 9944 
wolfssl_3.4.8+

Processed: tagging 791910, tagging 784778, tagging 789988, tagging 790526, tagging 791771, tagging 790772 ...

[Debian Bug Tracking System]

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

> # verified in local rebuilds that the package ftbfs in sid but not in jessie
> tags 791910 + sid stretch
Bug #791910 {Done: Markus Koschany } [byzanz] byzanz: FTBFS 
due to -Werror + -Wdeprecated-declarations
Added tag(s) sid and stretch.
> tags 784778 + sid stretch
Bug #784778 {Done: Michael Hanke } [condor] FTBFS: no matching 
function for call to 'condor_sockaddr::condor_sockaddr(const soap::*)'
Added tag(s) stretch and sid.
> tags 789988 + sid stretch
Bug #789988 [eclipse-mylyn-tasks-github] FTBFS: The import 
org.eclipse.egit.ui.internal.FilteredCheckboxTree cannot be resolved
Added tag(s) sid and stretch.
> tags 790526 + sid stretch
Bug #790526 [gri] FTBFS: Fatal error occurred, no output PDF file produced
Added tag(s) sid and stretch.
> tags 791771 + sid stretch
Bug #791771 [ruby-bdb] ruby-bdb: FTBFS; dead upstream
Added tag(s) stretch and sid.
> tags 790772 + sid stretch
Bug #790772 {Done: Rolf Leggewie } [scanbd] FTBFS: The 
pkg-config script could not be found or is too old.
Added tag(s) stretch and sid.
> # no previous builds on !x86 - not a regression
> retitle 790855 sdrangelove: FTBFS on !x86 due to unconditional use of -msse2 
> and immintrin.h
Bug #790855 [sdrangelove] sdrangelove: FTBFS on mipsel
Changed Bug title to 'sdrangelove: FTBFS on !x86 due to unconditional use of 
-msse2 and immintrin.h' from 'sdrangelove: FTBFS on mipsel'
> severity 790855 important
Bug #790855 [sdrangelove] sdrangelove: FTBFS on !x86 due to unconditional use 
of -msse2 and immintrin.h
Severity set to 'important' from 'serious'
> found 791830 2.24.0-1
Bug #791830 [src:bedtools] bedtools: FTBFS on mipsel
Marked as found in versions bedtools/2.24.0-1.
> tags 789991 + stretch sid
Bug #789991 [src:golang-gocheck] FTBFS: Test failures including 
FixtureS.TestPanicOnSetUpSuite, FixtureS.TestPanicOnSetUpTest
Added tag(s) sid and stretch.
> tags 788767 + stretch sid
Bug #788767 [src:monav] monav: FTBFS with gcc 4.9/mapnik 3.0.0: requires flags 
for c++11 support
Added tag(s) stretch and sid.
> tags 786743 + stretch sid
Bug #786743 [src:obnam] obnam: ftbfs, git command not found
Added tag(s) stretch and sid.
> tags 785511 + stretch sid
Bug #785511 {Done: Sergey B Kirpichev } [src:parser] 
parser: FTBFS with g++-4.9: ... operator new(std::size_t) ... has a different 
exception specifier
Added tag(s) sid and stretch.
> tags 790767 + sid stretch
Bug #790767 [zodb] FTBFS: ImportError: cannot import name component_re
Added tag(s) sid and stretch.
> tags 790631 + sid stretch
Bug #790631 {Done: Ron Lee } [xf86-input-wacom] FTBFS: 
implicit declaration of function 'fstat'
Added tag(s) sid and stretch.
> tags 790628 + sid stretch
Bug #790628 [nwchem] FTBFS: No rule to make target ... 
/LINUX64/libnwdft.a(rt_tddft_input.o)
Added tag(s) sid and stretch.
> tags 791772 + sid stretch
Bug #791772 {Done: Cédric Boutillier } [src:ruby-bluecloth] 
FTBFS: ERROR: Test ruby2.1 failed. Exiting
Added tag(s) sid and stretch.
> tags 789980 + sid stretch
Bug #789980 [src:python-mongoengine] FTBFS: from pymongo import ... 
ImportError: cannot import name Connection
Added tag(s) sid and stretch.
> tags 791415 + sid stretch
Bug #791415 [wings3d] FTBFS: erlang:now/0: Deprecated BIF
Added tag(s) sid and stretch.
> tags 787312 + sid stretch
Bug #787312 {Done: ChangZhuo Chen (陳昌倬) } [src:pycangjie] 
pycangjie is FTBFS
Added tag(s) sid and stretch.
> tags 790630 + sid stretch
Bug #790630 [udevil] FTBFS: implicit declaration of function 'stat' / 'S_ISBLK'
Added tag(s) sid and stretch.
> tags 791776 + sid stretch
Bug #791776 [src:ruby-dataobjects-mysql] FTBFS: 
rspec/core/example_group.rb:656:in method_missing: undefined method its 
(NoMethodError
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
784778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784778
785511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785511
786743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786743
787312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787312
788767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788767
789980: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789980
789988: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789988
789991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789991
790526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790526
790628: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790628
790630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790630
790631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790631
790767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790767
790772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790772
790855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790855
791415: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791415
791771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791771
791772: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791772
791776: http://bugs

Bug#792568: libdap17v5: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libdap.so.17.1.0

[Andreas Beckmann]

Package: libdap17v5
Version: 3.14.0-3~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libdap17v5:amd64.
  Preparing to unpack .../libdap17v5_3.14.0-3~exp1_amd64.deb ...
  Unpacking libdap17v5:amd64 (3.14.0-3~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libdap17v5_3.14.0-3~exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libdap.so.17.1.0', which is 
also in package libdap17:amd64 3.14.0-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libdap17v5_3.14.0-3~exp1_amd64.deb


cheers,

Andreas


libdap17=3.14.0-2_libdap17v5=3.14.0-3~exp1.log.gz
Description: application/gzip

Bug#792558: marked as done (zotero-standalone: Zotero-standalone no longer runs in testing)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 10:48:08 +
with message-id 

and subject line 
has caused the Debian Bug report #792558,
regarding zotero-standalone: Zotero-standalone no longer runs in testing
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.)


-- 
792558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zotero-standalone
Version: 4.0.26.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
   * What led up to the situation?

Attempt to use zotero standalone in conjunction with Chromium.

I alredy attemped this in the past, but went back to Iceweasel and Zotero for
Firefox.

For various reasons, I'd like to give Chromium another go.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Starting from the menu : nothing happens.
Starting from a terminal : I see exactly this :
charpent@SAP5057241:~$ zotero

(process:7443): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size
== 0' failed
Error: Platform version '24.5.0' is not compatible with
minVersion >= 31.0
maxVersion <= 40.*


   * What was the outcome of this action?

No functional Zotero

   * What outcome did you expect instead?

A Zotero Window.

Note : Google shows that similar problems have been reported, implying
different version of xulrunner. the /usr/share/zotero-
standalone/application.ini file specivies min and max version for *gecko*. I do
not know what this refers to.




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

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

Versions of packages zotero-standalone depends on:
ii  iceweasel   38.1.0esr-2
ii  xulrunner-17.0  17.0.10esr-1~deb7u1
ii  xulrunner-24.0  24.5.0esr-1
ii  xulrunner-2929.0.1-2

zotero-standalone recommends no packages.

zotero-standalone suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
-- 
Michele Cane, Ph.D.
--- End Message ---

Bug#777919: marked as done (irda-utils: ftbfs with GCC-5)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 10:35:34 +
with message-id 
and subject line Bug#777919: fixed in irda-utils 0.9.18-13
has caused the Debian Bug report #777919,
regarding irda-utils: ftbfs with GCC-5
to be marked as done.

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

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


-- 
777919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:irda-utils
Version: 0.9.18-12
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-5/g++-5, but succeeds to build with gcc-4.9/g++-4.9. The
severity of this report may be raised before the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc5-20150205/irda-utils_0.9.18-12_unstable_gcc5.log
The last lines of the build log are at the end of this report.

To build with GCC 5, either set CC=gcc-5 CXX=g++-5 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t experimental install g++ 

Common build failures are C11 as the default C mode, new warnings
resulting in build failures with -Werror turned on, or new/dropped
symbols in Debian symbols files.  For other C/C++ related build failures
see the porting guide at http://gcc.gnu.org/gcc-5/porting_to.html

[...]
 inline void parse_obex(GNetBuf *buf, GString *str, int cmd);
 ^
gcc -O2 -W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include 
-I../include/ -c obex.c
obex.c:265:8: warning: 'g_netbuf_get_len' is static but used in inline function 
'parse_obex' which is not static
  len = g_netbuf_get_len(buf);
^
In file included from obex.c:32:0:
irdadump.h:225:13: warning: inline function 'parse_ui_irlmp' declared but never 
defined
 inline void parse_ui_irlmp(GNetBuf *buf, GString *str, int type);
 ^
irdadump.h:223:13: warning: inline function 'parse_irlmp' declared but never 
defined
 inline void parse_irlmp(GNetBuf *buf, GString *str,
 ^
gcc -O2 -W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include 
-I../include/ -c ircomm.c
In file included from ircomm.c:31:0:
irdadump.h:225:13: warning: inline function 'parse_ui_irlmp' declared but never 
defined
 inline void parse_ui_irlmp(GNetBuf *buf, GString *str, int type);
 ^
irdadump.h:223:13: warning: inline function 'parse_irlmp' declared but never 
defined
 inline void parse_irlmp(GNetBuf *buf, GString *str,
 ^
irdadump.h:222:13: warning: inline function 'parse_obex' declared but never 
defined
 inline void parse_obex(GNetBuf *buf, GString *str, int cmd);
 ^
gcc -O2 -W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include 
-I../include/ -c netbuf.c
gcc -O2 -W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include 
-I../include/ -c capture.c
ar cru  lib_irdadump.a irdadump.o irlap.o irlmp.o obex.o ircomm.o netbuf.o 
capture.o
ranlib lib_irdadump.a
gcc -O2 -W -Wall -I. `pkg-config --cflags glib-2.0` -I/usr/include 
-I../include/ -c main.c
In file included from main.c:41:0:
./irdadump.h:225:13: warning: inline function 'parse_ui_irlmp' declared but 
never defined
 inline void parse_ui_irlmp(GNetBuf *buf, GString *str, int type);
 ^
./irdadump.h:223:13: warning: inline function 'parse_irlmp' declared but never 
defined
 inline void parse_irlmp(GNetBuf *buf, GString *str,
 ^
./irdadump.h:222:13: warning: inline function 'parse_obex' declared but never 
defined
 inline void parse_obex(GNetBuf *buf, GString *str, int cmd);
 ^
gcc -O2 -W -Wall -I. `pkg-config --cflags glib-2.0` -o  irdadump main.o 
lib_irdadump.a `pkg-config --libs glib-2.0`
lib_irdadump.a(irlap.o): In function `parse_irlap_frame':
irlap.c:(.text+0x843): undefined reference to `parse_irlmp'
irlap.c:(.text+0xa7f): undefined reference to `parse_ui_irlmp'
collect2: error: ld returned 1 exit status
make[1]: *** [irdadump] Error 1
Makefile:42: recipe for target 'irdadump' failed
make[1]: Leaving directory '/«PKGBUILDDIR»/irdadump'
make: *** [build-stamp] Error 2
debian/rules:23: recipe for target 'build-stamp' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: irda-utils
Source-Version: 0.9.1

Bug#792558: zotero-standalone: Zotero-standalone no longer runs in testing

[CHARPENTIER Emmanuel]

Dear Michael,

On 16/07/2015 11:57, Michele Cane wrote:
> Hi Emmanuel,
>
> Please try to uninstall all xulrunner instances and only leave iceweasel.

That worked ! Thank you VERY MUCH !

Emmanuel Charpentier

> Thanks
>
> On Thu, Jul 16, 2015 at 11:54 AM Emmanuel Charpentier
>  > wrote:
>
> Package: zotero-standalone
> Version: 4.0.26.2-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
> * What led up to the situation?
>
> Attempt to use zotero standalone in conjunction with Chromium.
>
> I alredy attemped this in the past, but went back to Iceweasel and
> Zotero for
> Firefox.
>
> For various reasons, I'd like to give Chromium another go.
>
> * What exactly did you do (or not do) that was effective (or
>   ineffective)?
>
> Starting from the menu : nothing happens.
> Starting from a terminal : I see exactly this :
> charpent@SAP5057241:~$ zotero
>
> (process:7443): GLib-CRITICAL **: g_slice_set_config: assertion
> 'sys_page_size
> == 0' failed
> Error: Platform version '24.5.0' is not compatible with
> minVersion >= 31.0
> maxVersion <= 40.*
>
>
> * What was the outcome of this action?
>
> No functional Zotero
>
> * What outcome did you expect instead?
>
> A Zotero Window.
>
> Note : Google shows that similar problems have been reported, implying
> different version of xulrunner. the /usr/share/zotero-
> standalone/application.ini file specivies min and max version for
> *gecko*. I do
> not know what this refers to.
>
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>APT prefers testing
>APT policy: (650, 'testing'), (500, 'testing-updates'), (500,
> 'testing-proposed-updates'), (60, 'unstable'), (55, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores)
> Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages zotero-standalone depends on:
> ii  iceweasel   38.1.0esr-2
> ii  xulrunner-17.0  17.0.10esr-1~deb7u1
> ii  xulrunner-24.0  24.5.0esr-1
> ii  xulrunner-2929.0.1-2
>
> zotero-standalone recommends no packages.
>
> zotero-standalone suggests no packages.
>
> -- no debconf information
>
> --
> Michele Cane, Ph.D.

Processed: your mail

[Debian Bug Tracking System]

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

> severity 792492 normal
Bug #792492 [poedit] poedit: abort opening any po-file
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#789444: marked as done (mate-indicator-applet: Cannot install mate-indicator-applet due to duplicate .mo file in both the packages)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 10:21:16 +
with message-id 
and subject line Bug#789444: fixed in mate-indicator-applet 1.10.0-1~exp2
has caused the Debian Bug report #789444,
regarding mate-indicator-applet: Cannot install mate-indicator-applet due to 
duplicate .mo file in both the packages
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.)


-- 
789444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mate-indicator-applet
Version: 1.10.0-1~exp1
Justification: renders package unusable
Severity: grave

Dear Maintainer,
I was upgrading mate-indicator-applet when ran into this :-

[$] sudo aptitude install mate-indicator-applet=1.10.0-1~exp1
mate-indicator-applet-common=1.10.0-1~exp1 -y

The following NEW packages will be installed:
  mate-indicator-applet-common
The following packages will be upgraded:
  mate-indicator-applet
1 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 93.6 kB of archives. After unpacking 553 kB will be freed.
Get: 1 http://httpredir.debian.org//debian/ experimental/main
mate-indicator-applet-common all 1.10.0-1~exp1 [64.2 kB]
Get: 2 http://httpredir.debian.org//debian/ experimental/main
mate-indicator-applet amd64 1.10.0-1~exp1 [29.4 kB]
Fetched 93.6 kB in 2s (36.6 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
apt-listchanges: Mailing root: apt-listchanges: changelogs for debian
D01: ensure_diversions: new, (re)loading
D01: ensure_statoverrides: new, (re)loading
Selecting previously unselected package mate-indicator-applet-common.
(Reading database ... 918691 files and directories currently installed.)
Preparing to unpack .../mate-indicator-applet-common_1.10.0-1~exp1_all.deb ...
D01: process_archive oldversionstatus=not installed
Unpacking mate-indicator-applet-common (1.10.0-1~exp1) ...
dpkg: error processing archive
/var/cache/apt/archives/mate-indicator-applet-common_1.10.0-1~exp1_all.deb
(--unpack):
 trying to overwrite
'/usr/share/locale/oc/LC_MESSAGES/mate-indicator-applet.mo', which is
also in package mate-indicator-applet 1.8.0-4
Preparing to unpack .../mate-indicator-applet_1.10.0-1~exp1_amd64.deb ...
D01: process_archive oldversionstatus=installed
Unpacking mate-indicator-applet (1.10.0-1~exp1) over (1.8.0-4) ...
D01: process_archive updating info directory
D01: generating infodb hashfile
Processing triggers for hicolor-icon-theme (0.13-1) ...
D01: ensure_diversions: same, skipping
D01: cmpversions a='0:1.18.1' b='0:1.16' r=2
D01: cmpversions a='0:1.18.1' b='0:1.16' r=2
Errors were encountered while processing:
 /var/cache/apt/archives/mate-indicator-applet-common_1.10.0-1~exp1_all.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
D01: ensure_diversions: new, (re)loading
D01: process queue pkg mate-indicator-applet:amd64 queue.len 0
progress 1, try 1
dpkg: dependency problems prevent configuration of mate-indicator-applet:
 mate-indicator-applet depends on mate-indicator-applet-common (=
1.10.0-1~exp1); however:
  Package mate-indicator-applet-common is not installed.

dpkg: error processing package mate-indicator-applet (--configure):
 dependency problems - leaving unconfigured
D01: cmpversions a='0:1.18.1' b='0:1.16' r=2
D01: cmpversions a='0:1.18.1' b='0:1.16' r=2
Errors were encountered while processing:
 mate-indicator-applet

Current status: 1 broken [+1], 1 update [-1].

Also :-

[$] aptitude why mate-indicator-applet-common

B   mate-indicator-applet Depends mate-indicator-applet-common (= 1.10.0-1~exp1)

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

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

Versions of packages mate-indicator-applet depends on:
ii  libatk1.0-0   2.16.0-2
ii  libc6 2.19-18
ii  libcairo2 1.14.2-2
ii  libfontconfig12.11.0-6.3
ii  libfreetype6  2.5.2-4
ii  libgdk-pixbuf2.0-02.31.4-2
ii  libglib2.0-0  2.45.2-1
ii  libgtk2.0-0   2.24.28-1
ii  libindicator7 0.5.0-2

Bug#791842: marked as done (libgdchart-gd2: FTBFS on sid due to unsatisfiable build-dependency on libgd2-(no)xpm-dev)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 10:20:56 +
with message-id 
and subject line Bug#791842: fixed in libgdchart-gd2 0.11.5-8
has caused the Debian Bug report #791842,
regarding libgdchart-gd2: FTBFS on sid due to unsatisfiable build-dependency on 
libgd2-(no)xpm-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.)


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

Dear maintainer,

your package libgdchart-gd2 ftbfs in current sid due to it
Build-Depending on either libgd2-xpm-dev or libgd2-noxpm-dev with
versioned restriction. The source package providing those packages
dropped those transitive packages on libgd-dev in favour of a
Provide, though a versioned dependecy won't be satisfy by a virtual
package.

Suggested action is swapping that build-dependency with one on
libgd-dev, alternatively you can remove the version constraints and
keep the old package name, though that's not suggested since they
already were only transitive packages.

Thanks for maintaining libgdchart-gd2!

-- 
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: Digital signature
--- End Message ---
--- Begin Message ---
Source: libgdchart-gd2
Source-Version: 0.11.5-8

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libgdchart-gd2 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, 16 Jul 2015 12:02:51 +0200
Source: libgdchart-gd2
Binary: libgdchart-gd2-noxpm-dev libgdchart-gd2-xpm-dev libgdchart-gd2-noxpm 
libgdchart-gd2-xpm
Architecture: source amd64
Version: 0.11.5-8
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Andreas Tille 
Description:
 libgdchart-gd2-noxpm - Generate graphs using the GD library
 libgdchart-gd2-noxpm-dev - Generate graphs using the GD library (development 
version)
 libgdchart-gd2-xpm - Generate graphs using the GD library
 libgdchart-gd2-xpm-dev - Generate graphs using the GD library (development 
version)
Closes: 791842
Changes:
 libgdchart-gd2 (0.11.5-8) unstable; urgency=medium
 .
   * Team upload
   * Standards-Version: 3.9.6
   * debhelper 9
   * Build-Depends: libgd-dev instead of libgd2-noxpm-dev (>> 2.0.28)
 Closes: #791842
Checksums-Sha1:
 be14e6da067954f92e92489c95d2804fb177f863 2257 libgdchart-gd2_0.11.5-8.dsc
 ffe76e376ab8610f2a235e8e03928fc5f5a7ec61 7256 
libgdchart-gd2_0.11.5-8.debian.tar.xz
 57477a64996276024c1b6eaac31ecb173130ad89 50494 
libgdchart-gd2-noxpm-dev_0.11.5-8_amd64.deb
 d6878ec140756c456b552ebc2aab7d3cd5fc0a8a 43408 
libgdchart-gd2-noxpm_0.11.5-8_amd64.deb
 a4bc2fc659adbbb58438a1ed91ec353b1f7c7a5f 50510 
libgdchart-gd2-xpm-dev_0.11.5-8_amd64.deb
 4dfedb1330ba029cbbff6abe2cc90a221c454496 43408 
libgdchart-gd2-xpm_0.11.5-8_amd64.deb
Checksums-Sha256:
 3eb4288518a287b53e1033649d8953ab3cfc5a5d5cd43f424c2b77de9d2353d4 2257 
libgdchart-gd2_0.11.5-8.dsc
 c65d757b198d146855f2b940a343b5d2644a58bbe7c56487ff70a3261b858957 7256 
libgdchart-gd2_0.11.5-8.debian.tar.xz
 e11b44c9885bd4f6945cf552764025793f503288057893637c456fda77144504 50494 
libgdchart-gd2-noxpm-dev_0.11.5-8_amd64.deb
 a4ada2ec17613c43e4cd83d1c4b303b27f9adcd17b8d0fdd27eac5e6b8252858 43408 
libgdchart-gd2-noxpm_0.11.5-8_amd64.deb
 4a0257f1968358e95d296d09f5ac31e8c1981aeb49d55cea9142219732bc5cc4 50510 
libgdchart-gd2-xpm-dev_0.11.5-8_amd64.deb
 6d01e94fab820019ab8755e75e3444515b88e0164b3806c514d4f3c08c2f4333 43408 
libgdchart-gd2-xpm_0.11.5-8_amd64.deb
Files:
 fbc567416af0cf13ada4514a17ea4b6b 2257 libs optional libgdchart-gd2_0.11.5-8.dsc
 13e04756b3cfbea98041a9647b368005 7256 libs opti

Bug#792562: flashplugin-nonfree: please update flashplugin-nonfree checksums for 11.2.202.491

[Matt Roberds]

Package: flashplugin-nonfree
Version: 1:3.2+wheezy1
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

   * What led up to the situation?

Attempt to update the Adobe Flash plugin to the latest version
(11.2.202.491 as of this report).

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I ran update-flashplugin-nonfree --status; it reported that I had
11.2.202.481 on my system now, and that 11.2.202.491 is available
upstream.

I then ran update-flashplugin-nonfree --install; it downloaded and
installed something.

   * What was the outcome of this action?

I ran update-flashplugin-nonfree --status again; it reported that I
had 11.2.202.481 on my system now, and that 11.2.202.491 is available
upstream.

   * What outcome did you expect instead?

I expected to have 11.2.202.491 installed on my system.

Extra information:

I believe this may be the same problem as bug 789808 ; it may be
happening again because of the new change in the upstream version.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789808

I made a copy of the update-flashplugin-nonfree script and modified it
to exit after creating the checksums.txt file.  I examined the
checksums.txt file it created and the last line referred to 11.2.202.481
, but I expected it to refer to 11.2.202.491 .

For the log below, I first made sure /var/cache/flashplugin-nonfree was
cleared out, and then I ran the standard, unmodified version of the
update-flashplugin-nonfree script.

Thanks for your help!

### Log of actions - cut here ###

# cd /var/cache/flashplugin-nonfree/
/var/cache/flashplugin-nonfree# ls
junk
/var/cache/flashplugin-nonfree# cd

~# update-flashplugin-nonfree --status --verbose
options :  --status --verbose --
temporary directory: /tmp/flashplugin-nonfree.HaCQvQMGYl
importing public key ...
selected action = --status
Flash Player version installed on this system  : 11.2.202.481
Flash Player version available on upstream site: 11.2.202.491
flash-mozilla.so - auto mode
  link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50
Current 'best' version is '/usr/lib/flashplugin-nonfree/libflashplayer.so'.
end of action --status
cleaning up temporary directory /tmp/flashplugin-nonfree.HaCQvQMGYl ...
end of update-flashplugin-nonfree

~# update-flashplugin-nonfree --install --verbose
options :  --install --verbose --
temporary directory: /tmp/flashplugin-nonfree.Afhmo5NLfJ
importing public key ...
selected action = --install
installed version = 11.2.202.481
upstream version = 11.2.202.491
wgetoptions= -nd -P .   -v --progress=dot:default downloading 
http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp10.sha512.amd64.pgp.asc 
...
--2015-07-16 04:28:38-- 
http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp10.sha512.amd64.pgp.asc
Resolving people.debian.org (people.debian.org)... 5.153.231.30, 
2001:41c8:1000:21::21:30
Connecting to people.debian.org (people.debian.org)|5.153.231.30|:80... 
connected.

HTTP request sent, awaiting response... 301 Moved Permanently
Location: 
https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp10.sha512.amd64.pgp.asc 
[following]
--2015-07-16 04:28:38-- 
https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp10.sha512.amd64.pgp.asc
Connecting to people.debian.org (people.debian.org)|5.153.231.30|:443... 
connected.

HTTP request sent, awaiting response... 200 OK
Length: 1267 (1.2K) [text/plain]
Saving to: `./fp10.sha512.amd64.pgp.asc'

 0K . 100% 13.2M=0s

2015-07-16 04:28:39 (13.2 MB/s) - `./fp10.sha512.amd64.pgp.asc' saved 
[1267/1267]


verifying PGP fp10.sha512.amd64.pgp.asc ...
wgetoptions= -nd -P .   -v --progress=dot:default  -O 
/tmp/flashplugin-nonfree.Afhmo5NLfJ/install_flash_player_11_linux.x86_64.tar.gz
--2015-07-16 04:28:39-- 
https://fpdownload.adobe.com/get/flashplayer/pdc/11.2.202.481/install_flash_player_11_linux.x86_64.tar.gz

Resolving fpdownload.adobe.com (fpdownload.adobe.com)... 23.193.172.246
Connecting to fpdownload.adobe.com 
(fpdownload.adobe.com)|23.193.172.246|:443... connected.

HTTP request sent, awaiting response... 200 OK
Length: 7250105 (6.9M) [application/x-gzip]
Saving to: 
`/tmp/flashplugin-nonfree.Afhmo5NLfJ/install_flash_player_11_linux.x86_64.tar.gz'


 0K .. .. .. .. ..  0% 1.21M 6s
50K .. .. .. .. ..  1% 1.53M 5s
   100K .. .. .. .. ..  2% 2.56M 4s
   150K .. .. .. .. ..  2% 2.32M 4s
   200K .. .. .. .. ..  3% 2.44M 4s
   250K .. .. .. .. ..  4% 3.62M 3s
   300K .. .. .. .. ..  4% 2.87M 3s
   350K .. .. .. .. ..  5% 3

Processed: Bug#789444 marked as pending

[Debian Bug Tracking System]

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

> tag 789444 pending
Bug #789444 [mate-indicator-applet] mate-indicator-applet: Cannot install 
mate-indicator-applet due to duplicate .mo file in both the packages
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#789348: marked as done (mate-applets: Unable to install mate-applets because of a file conflict in mate-applets-common)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 10:08:13 +
with message-id 
and subject line Bug#789348: fixed in mate-applets 1.10.0+dfsg1-1~exp2
has caused the Debian Bug report #789348,
regarding mate-applets: Unable to install mate-applets because of a file 
conflict in mate-applets-common
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.)


-- 
789348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mate-applets
Version: 1.10.0+dfsg1-1~exp1
Justification: renders package unusable
Severity: grave

Dear Maintainer,
I was trying to install mate-applets when ran into this :-

[$] sudo aptitude install mate-applets=1.10.0+dfsg1-1~exp1
mate-applets-common=1.10.0+dfsg1-1~exp1
The following packages will be upgraded:
  mate-applets mate-applets-common
The following partially installed packages will be configured:
  mate-sensors-applet{b}
2 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 965 kB of archives. After unpacking 387 kB will be freed.
The following packages have unmet dependencies:
 mate-sensors-applet : Depends: mate-sensors-applet-common (=
1.10.1+dfsg1-1~exp1) but it is not going to be installed.
The following actions will resolve these dependencies:

 Remove the following packages:
1) mate-sensors-applet



Accept this solution? [Y/n/q/?] Y
The following packages will be REMOVED:
  libmate-sensors-applet-plugin0{u} mate-sensors-applet{a}
The following packages will be upgraded:
  mate-applets mate-applets-common
2 packages upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
Need to get 965 kB of archives. After unpacking 668 kB will be freed.
Do you want to continue? [Y/n/?] Y
Get: 1 http://httpredir.debian.org//debian/ experimental/main
mate-applets amd64 1.10.0+dfsg1-1~exp1 [221 kB]
Get: 2 http://httpredir.debian.org//debian/ experimental/main
mate-applets-common all 1.10.0+dfsg1-1~exp1 [743 kB]
Fetched 965 kB in 12s (78.9 kB/s)
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
apt-listchanges: Mailing root: apt-listchanges: changelogs for debian
D01: ensure_diversions: new, (re)loading
D01: process queue pkg mate-sensors-applet:amd64 queue.len 1
progress 1, try 1
D01: deferred_remove package mate-sensors-applet:amd64
D01: checking dependencies for remove 'mate-sensors-applet:amd64'
(Reading database ... 918842 files and directories currently installed.)
Removing mate-sensors-applet (1.10.1+dfsg1-1~exp1) ...
D01: removal_bulk package mate-sensors-applet:amd64
D01: ensure_diversions: same, skipping
D01: removal_bulk cleaning info directory
D01: removal_bulk purging? foundpostrm=1
D01: removal done
D01: process queue pkg libmate-sensors-applet-plugin0:amd64
queue.len 0 progress 1, try 1
D01: deferred_remove package libmate-sensors-applet-plugin0:amd64
D01: checking dependencies for remove 'libmate-sensors-applet-plugin0:amd64'
Removing libmate-sensors-applet-plugin0 (1.10.1+dfsg1-1~exp1) ...
D01: removal_bulk package libmate-sensors-applet-plugin0:amd64
D01: ensure_diversions: same, skipping
D01: removal_bulk cleaning info directory
D01: removal_bulk purging? foundpostrm=1
D01: removal done
Processing triggers for libc-bin (2.19-18) ...
D01: ensure_diversions: same, skipping
D01: cmpversions a='0:1.18.1' b='0:1.16' r=2
D01: cmpversions a='0:1.18.1' b='0:1.16' r=2
D01: ensure_diversions: new, (re)loading
D01: ensure_statoverrides: new, (re)loading
(Reading database ... 918807 files and directories currently installed.)
Preparing to unpack .../mate-applets_1.10.0+dfsg1-1~exp1_amd64.deb ...
D01: process_archive oldversionstatus=installed
Unpacking mate-applets (1.10.0+dfsg1-1~exp1) over (1.8.1+dfsg1-3) ...
D01: process_archive updating info directory
D01: generating infodb hashfile
Preparing to unpack .../mate-applets-common_1.10.0+dfsg1-1~exp1_all.deb ...
D01: process_archive oldversionstatus=installed
Unpacking mate-applets-common (1.10.0+dfsg1-1~exp1) over (1.8.1+dfsg1-3) ...
dpkg: error processing archive
/var/cache/apt/archives/mate-applets-common_1.10.0+dfsg1-1~exp1_all.deb
(--unpack):
 trying to overwrite
'/usr/share/dbus-1/services/org.mate.panel.applet.DriveMountAppletFactory.service',
which is also in package mate-applets 1.10.0+dfsg1-1~exp1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for dbus (1.9.16-2) ...
D01: ensure_diversions: same, skipping
Processing triggers for man-db (2.7.0.2-5) ...
D01:

Bug#789444: marked as pending

[Mike Gabriel]

tag 789444 pending
thanks

Hello,

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


http://git.debian.org/?p=pkg-mate/mate-indicator-applet.git;a=commitdiff;h=b065415

---
commit b06541519fa386ce9b11615723064ff546582ebb
Author: Mike Gabriel 
Date:   Thu Jul 16 12:08:23 2015 +0200

upload to experimental (debian/1.10.0-1~exp2)

diff --git a/debian/changelog b/debian/changelog
index b1e392a..61d21e8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+mate-indicator-applet (1.10.0-1~exp2) experimental; urgency=medium
+
+  * debian/control:
++ Drop R (mate-indicator-applets-common).
++ Fix B (mate-indicator-applets-common). The new -common package
+  breaks mate-applets-indicator (<< 1.9), not (<< 1.8). (Closes:
+  #789444).
+
+ -- Mike Gabriel   Thu, 16 Jul 2015 12:05:32 +0200
+
 mate-indicator-applet (1.10.0-1~exp1) experimental; urgency=low
 
   [ Martin Wimpress ]


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#792034: marked as done (designate: Package is missing designate services)

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 10:00:21 +
with message-id 
and subject line Bug#792034: fixed in designate 2015.1.0-2
has caused the Debian Bug report #792034,
regarding designate: Package is missing designate services
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.)


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

Dear Maintainer,


   * What led up to the situation?

apt-get install designate

   * What was the outcome of this action?

2 services introduced in Kilo (designate-mdns & designate-pool-manager) are not 
included in an install
These are critical to designate functioning.


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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages designate depends on:
ii  designate-agent2015.1.0-1
ii  designate-api  2015.1.0-1
ii  designate-central  2015.1.0-1
ii  designate-common   2015.1.0-1
ii  dpkg   1.18.1

designate recommends no packages.

designate suggests no packages.
--- End Message ---
--- Begin Message ---
Source: designate
Source-Version: 2015.1.0-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated designate 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, 14 Jul 2015 19:25:17 +0200
Source: designate
Binary: python-designate designate-common designate designate-api 
designate-central designate-agent designate-sink designate-mdns 
designate-pool-manager designate-doc
Architecture: source all
Version: 2015.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 designate  - OpenStack DNS as a Service - metapackage
 designate-agent - OpenStack DNS as a Service - agent
 designate-api - OpenStack DNS as a Service - API server
 designate-central - OpenStack DNS as a Service - central daemon
 designate-common - OpenStack DNS as a Service - common files
 designate-doc - OpenStack DNS as a Service - doc
 designate-mdns - OpenStack DNS as a Service - mdns
 designate-pool-manager - OpenStack DNS as a Service - pool manager
 designate-sink - OpenStack DNS as a Service - sink
 python-designate - OpenStack DNS as a Service - Python libs
Closes: 792034
Changes:
 designate (2015.1.0-2) unstable; urgency=medium
 .
   * Added -mdns and -pool-manager services through new .deb which were missing.
 Thanks to Graham Hayes  for the report (Closes: #792034)
   * Removed all individual debian/*.logrotate files, using only a single
 designate-common.logrotate file now.
   * Added do-not-use-namespace-oslo.concurrency.patch.
Checksums-Sha1:
 0270e5b45ab4b56019821ad9a35987ea3b165de0 3744 designate_2015.1.0-2.dsc
 d8e8d2bfb77a64419cafabcb20c437ceb1605a0e 14256 
designate_2015.1.0-2.debian.tar.xz
 90aef69d81beb5d398832c08b6f226be8c57c5cd 6012 
designate-agent_2015.1.0-2_all.deb
 3f464e0bf445b324ff913f2a0b8c813787892a8b 15800 designate-api_2015.1.0-2_all.deb
 220f1ad956873b8158619df17878c10b77a4768a 6026 
designate-central_2015.1.0-2_all.deb
 fd68a69857fce8d191a7f3f79692036b6cd9d6d6 19272 
designate-common_2015.1.0-2_all.deb
 0bfe0464670e94ab0e78df08a2f3c22327def40d 234662 
designate-doc_2015.1.0-2_all.deb
 b196e0aeb0f886d19240b38c277fa3450e3e160f 6006 designate-mdns_2015.1.0-2_all.deb
 34b4627fdd4eb5c0214085573b77bf1b15f5009b 6024 
designate-pool-manager_2015.1.0-2_all.deb
 071b475a6eac4161328d634e0aa45253be1b7881 6008 designate-sink_2015.1.0-2_all.deb
 21eea370d120f063d3c104f19c1d31725504f891 3304 designate_2015.1.0-2_all.deb
 49746fa631d8a2272208ab71733741f2bf182c7a 206232 
python-designate_2015.1.0-2_all.deb
Checksums-Sha256:
 a2591aa71e1691fd7423ae59ea07ad802abebed27914

Bug#792558: zotero-standalone: Zotero-standalone no longer runs in testing

[Michele Cane]

Hi Emmanuel,

Please try to uninstall all xulrunner instances and only leave iceweasel.

Thanks

On Thu, Jul 16, 2015 at 11:54 AM Emmanuel Charpentier <
emmanuel.charpent...@sap.aphp.fr> wrote:

> Package: zotero-standalone
> Version: 4.0.26.2-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>* What led up to the situation?
>
> Attempt to use zotero standalone in conjunction with Chromium.
>
> I alredy attemped this in the past, but went back to Iceweasel and Zotero
> for
> Firefox.
>
> For various reasons, I'd like to give Chromium another go.
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>
> Starting from the menu : nothing happens.
> Starting from a terminal : I see exactly this :
> charpent@SAP5057241:~$ zotero
>
> (process:7443): GLib-CRITICAL **: g_slice_set_config: assertion
> 'sys_page_size
> == 0' failed
> Error: Platform version '24.5.0' is not compatible with
> minVersion >= 31.0
> maxVersion <= 40.*
>
>
>* What was the outcome of this action?
>
> No functional Zotero
>
>* What outcome did you expect instead?
>
> A Zotero Window.
>
> Note : Google shows that similar problems have been reported, implying
> different version of xulrunner. the /usr/share/zotero-
> standalone/application.ini file specivies min and max version for *gecko*.
> I do
> not know what this refers to.
>
>
>
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers testing
>   APT policy: (650, 'testing'), (500, 'testing-updates'), (500,
> 'testing-proposed-updates'), (60, 'unstable'), (55, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores)
> Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages zotero-standalone depends on:
> ii  iceweasel   38.1.0esr-2
> ii  xulrunner-17.0  17.0.10esr-1~deb7u1
> ii  xulrunner-24.0  24.5.0esr-1
> ii  xulrunner-2929.0.1-2
>
> zotero-standalone recommends no packages.
>
> zotero-standalone suggests no packages.
>
> -- no debconf information
>
-- 
Michele Cane, Ph.D.

Bug#792492: poedit: abort opening any po-file

[Václav Slavík]

Let me jump in as the upstream author: this is with absolute certainly not in 
any way related to "libstdc++6 upgrade" nor to any outdated libraries.

Just read the backtrace that Thomas helpfully provided: it shows that the 
LucenePlusPlus library asserts on reading what is probably corrupted data. This 
should be filed as a bug with LucenePlusPlus, as it should never assert on 
inputs and should throw an exception instead.

The other grave bug is of course that apparently Poedit/LucenePlusPlus 
corrupted the data in the first place when saving. I have some spurious reports 
of this corruption happening on other platforms, but this is the first 
confirmation I have that it was caused by Poedit itself while editing. 
Apparently, LucenePlusPlus's supposed ACID properties don't exist in real life 
in the C++ port (not the first problem). Pity there isn't a backtrace from the 
time of crash, that could be useful.

To "fix" this to get Poedit working again, I'm afraid the only solution is to 
delete the local TM in ~/.local/share/poedit/TranslationMemory (or try to 
recover it with Lucene tools).

Vaclav


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: Bug#789348 marked as pending

[Debian Bug Tracking System]

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

> tag 789348 pending
Bug #789348 [mate-applets] mate-applets: Unable to install mate-applets because 
of a file conflict in mate-applets-common
Added tag(s) pending.
> thanks
Stopping processing here.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#792558: zotero-standalone: Zotero-standalone no longer runs in testing

[Emmanuel Charpentier]

Package: zotero-standalone
Version: 4.0.26.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
   * What led up to the situation?

Attempt to use zotero standalone in conjunction with Chromium.

I alredy attemped this in the past, but went back to Iceweasel and Zotero for
Firefox.

For various reasons, I'd like to give Chromium another go.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Starting from the menu : nothing happens.
Starting from a terminal : I see exactly this :
charpent@SAP5057241:~$ zotero

(process:7443): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size
== 0' failed
Error: Platform version '24.5.0' is not compatible with
minVersion >= 31.0
maxVersion <= 40.*


   * What was the outcome of this action?

No functional Zotero

   * What outcome did you expect instead?

A Zotero Window.

Note : Google shows that similar problems have been reported, implying
different version of xulrunner. the /usr/share/zotero-
standalone/application.ini file specivies min and max version for *gecko*. I do
not know what this refers to.




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

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

Versions of packages zotero-standalone depends on:
ii  iceweasel   38.1.0esr-2
ii  xulrunner-17.0  17.0.10esr-1~deb7u1
ii  xulrunner-24.0  24.5.0esr-1
ii  xulrunner-2929.0.1-2

zotero-standalone recommends no packages.

zotero-standalone suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#789348: marked as pending

[Mike Gabriel]

tag 789348 pending
thanks

Hello,

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

http://git.debian.org/?p=pkg-mate/mate-applets.git;a=commitdiff;h=4d8e6fa

---
commit 4d8e6fa716e173e3802dcf916ac76a5b72fa530f
Author: Mike Gabriel 
Date:   Thu Jul 16 11:50:00 2015 +0200

upload to experimental (debian/1.10.0+dfsg1-1~exp2)

diff --git a/debian/changelog b/debian/changelog
index f8db4bd..341bdde 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+mate-applets (1.10.0+dfsg1-1~exp2) experimental; urgency=medium
+
+  * debian/mate-applets.install:
++ Fix duplicate files in mate-applets and mate-applets-common.
+  (Closes: #789348).
+
+ -- Mike Gabriel   Thu, 16 Jul 2015 11:36:55 +0200
+
 mate-applets (1.10.0+dfsg1-1~exp1) experimental; urgency=medium
 
   * New upstream release.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#790911: marked as done (FTBFS: src/sna/sna_driver.c: error: implicit declaration of function 'fstat')

[Debian Bug Tracking System]

Your message dated Thu, 16 Jul 2015 09:37:45 +
with message-id 
and subject line Bug#790911: fixed in xserver-xorg-video-intel 2:2.99.917-2
has caused the Debian Bug report #790911,
regarding FTBFS: src/sna/sna_driver.c: error: implicit declaration of function 
'fstat'
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.)


-- 
790911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xserver-xorg-video-intel
Version: 2:2.99.917-1
Severity: serious
Tags: sid
Justification: fails to build from source (but built successfully in the past)
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Dear Maintainer,

The package fails to build:
.../../../src/sna/sna_driver.c: In function 'sna_handle_uevents':
.../../../src/sna/sna_driver.c:799:2: error: implicit declaration of function 
'fstat' [-Werror=implicit-function-declaration]
  if (fstat(sna->kgem.fd, &s) || memcmp(&s.st_rdev, &udev_devnum, sizeof 
(dev_t))) {
  ^
.../../../src/sna/sna_driver.c:799:2: warning: nested extern declaration of 
'fstat' [-Wnested-externs]

Probably the same cause / fix as https://bugs.debian.org/790631 , but I'm 
guessing "missing header".

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/xserver-xorg-video-intel.html

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

Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: xserver-xorg-video-intel
Source-Version: 2:2.99.917-2

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

Debian distribution maintenance software
pp.
Vincent Cheng  (supplier of updated xserver-xorg-video-intel 
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, 16 Jul 2015 01:00:41 -0700
Source: xserver-xorg-video-intel
Binary: xserver-xorg-video-intel xserver-xorg-video-intel-dbg
Architecture: source
Version: 2:2.99.917-2
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Vincent Cheng 
Description:
 xserver-xorg-video-intel - X.Org X server -- Intel i8xx, i9xx display driver
 xserver-xorg-video-intel-dbg - X.Org X server -- Intel i8xx, i9xx display 
driver (debug symbols)
Closes: 775200 787142 790911
Changes:
 xserver-xorg-video-intel (2:2.99.917-2) unstable; urgency=medium
 .
   [ Robert Ancell ]
   * debian/patches/fix-sna-fstat-include.patch:
   * debian/patches/fix-uxa-fstat-include.patch:
 - Fix missing include for fstat (Closes: #790911)
 .
   [ Alessio Treglia ]
   * fix-yuv-to-rgb-shared-on-intel-gen8.patch: Fix faulty yuv2rgb translation
 on Intel Generation 8 Graphics. (LP: #1449892, Closes: #787142)
 .
   [ Timo Aaltonen ]
   * rules: Fix valgrind-enabling check.
   * source: Add extend-diff-ignore to not complain about symlinks.
   * README.source: Mention that dpkg-source complains about symlinks
 which are real files on the tarball, and add a command to clean
 those before source build (copied from libdrm).
 .
   [ Adam Borowski ]
   * Add x32 to the list of architectures. (Closes: #775200)
 .
   [ Vincent Cheng ]
   * Explicitly declare source format 1.0.
   * Update valgrind build-dependency architecture list.
Checksums-Sha1:
 96a377657920459a4fe60f86e74b509307e77f81 3112 
xserver-xorg-video-intel_2.99.917-2.dsc
 99f5cbae4e8460d3ed513b959a9f3c0a23ac68c3 948068 
xserver-xorg-video-intel_2.99.917-2.diff.gz
Checksums-Sha256:
 37b1047a77ae7aa7296608fb9cfef05b1ab87d804ff0994bb390c5c0b664d48f 3112 
xserver-xorg-video-intel_2.99.917-2.dsc
 84b0a0eb16902e9a27f480030a733cdc6b09f642d2133d60f296e16f00c5bbcd 948068 
xserver-xorg-video-intel_2.99.917-2.diff.gz
Files:
 8bb89aedc289a26d2851bdbd2a418521 3112 x11 optional 
xserver-xorg-video-intel_2.99.917-2.dsc
 a22651

Bug#792549: libecm0-dev-common: fails to upgrade from 'testing' - trying to overwrite /usr/include/ecm.h

[Andreas Beckmann]

Package: libecm0-dev-common
Version: 6.4.4+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libecm0-dev-common.
  Preparing to unpack .../libecm0-dev-common_6.4.4+ds-1_all.deb ...
  Unpacking libecm0-dev-common (6.4.4+ds-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libecm0-dev-common_6.4.4+ds-1_all.deb (--unpack):
   trying to overwrite '/usr/include/ecm.h', which is also in package 
libecm-dev 6.4.4-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libecm0-dev-common_6.4.4+ds-1_all.deb


cheers,

Andreas


libecm-dev=6.4.4-2_libecm0-dev-common=6.4.4+ds-1.log.gz
Description: application/gzip

Bug#792548: ruby-hashie,ruby-rash: error when trying to install together

[Andreas Beckmann]

Package: ruby-hashie,ruby-rash
Version: 3.4.2-1
Severity: serious
Tags: sid
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 0.4.0-1

Architecture: amd64
Distribution: sid

Hi,

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

  Selecting previously unselected package ruby-rash.
  Preparing to unpack .../ruby-rash_0.4.0-1_all.deb ...
  Unpacking ruby-rash (0.4.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-rash_0.4.0-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/hashie/rash.rb', which is 
also in package ruby-hashie 3.4.2-1
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-rash_0.4.0-1_all.deb


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

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

  usr/lib/ruby/vendor_ruby/hashie/rash.rb

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

Cheers,

Andreas

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


ruby-hashie=3.4.2-1_ruby-rash=0.4.0-1.log.gz
Description: application/gzip

Processed: ruby-hashie,ruby-rash: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.4.0-1
Bug #792548 [ruby-hashie,ruby-rash] ruby-hashie,ruby-rash: error when trying to 
install together
There is no source info for the package 'ruby-hashie' at version '0.4.0-1' with 
architecture ''
Marked as found in versions ruby-rash/0.4.0-1.

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


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#774149: Workaround working

[Mathieu Malaterre]

On Wed, Jul 15, 2015 at 10:38 PM, Rogério Brito  wrote:

> BTW, one very important question: are the problems with usbmount only
> apparent when using fuse filesystems or are they also apparent when using
> filesystems supported by the kernel (e.g., vfat or ext4)?
>
>
vfat & ext4 usbkey were ok for me. So I suspect this is only FUSE-related.