Processed: subversion Debian ci: r1516 - in src/1.9.x/debian: . patches

[Debian Bug Tracking System]

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

> tags 817002 pending
Bug #817002 [src:subversion] subversion: Build-Depends: swig2.0 but it is not 
installable in stretch
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#814991: marked as done (pkg-haskell-tools: FTBFS - build-dep libghc-debian-dev (<< 3.88) unsatisfiable as 3.89-1+b1 is current)

[Debian Bug Tracking System]

Your message dated Mon, 14 Mar 2016 03:38:02 +
with message-id 
and subject line Bug#814991: fixed in pkg-haskell-tools 0.10.2
has caused the Debian Bug report #814991,
regarding pkg-haskell-tools: FTBFS - build-dep libghc-debian-dev (<< 3.88) 
unsatisfiable as 3.89-1+b1 is current
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.)


-- 
814991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pkg-haskell-tools
Version: 0.10.1
Severity: serious
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.

[...]
 -> Attempting to parse the build-deps
 -> Considering build-dep debhelper (>= 9)
   -> Trying debhelper
 -> Considering build-dep pandoc
   -> Trying pandoc
 -> Considering build-dep haskell-devscripts (>= 0.9)
   -> Trying haskell-devscripts
 -> Considering build-dep cdbs
   -> Trying cdbs
 -> Considering build-dep ghc
   -> Trying ghc
 -> Considering build-dep ghc-prof
   -> Trying ghc-prof
 -> Considering build-dep libghc-debian-dev (>= 3.87)
   -> Trying libghc-debian-dev
 -> Considering build-dep libghc-debian-dev (<< 3.88)
  Tried versions: 3.89-1+b1
   -> Does not satisfy version, not trying
E: Could not satisfy build-dependency.


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


pkg-haskell-tools-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: pkg-haskell-tools
Source-Version: 0.10.2

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

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated pkg-haskell-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Mar 2016 22:30:08 -0400
Source: pkg-haskell-tools
Binary: pkg-haskell-tools
Architecture: source amd64
Version: 0.10.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description:
 pkg-haskell-tools - Debian Haskell Group tools
Closes: 814991
Changes:
 pkg-haskell-tools (0.10.2) unstable; urgency=medium
 .
   [ Joachim Breitner ]
   * dht make-all: Do not print "dpkg-deb" calls.
   * dht make-all: Bump a few dependencies.  closes: #814991.
   * dht upgrade: More robust debian/watch parsing
 .
   [ Sven Bartscher ]
   * Added dependencies on perl and perl libraries, as dh_perl didn't add
 them.
 .
   [ Clint Adams ]
   * upgrade: pass a static list of --exec-map's to cabal-debian
   * Fix thinko in libfile-slurp-perl dependency
   * Add libfile-slurp-perl to Build-Depends as well, since it seems to
 be necessary to generate man pages.
Checksums-Sha1:
 2791b0a7b21c961f9d62ff886ea4060f7f644d14 2322 pkg-haskell-tools_0.10.2.dsc
 5c35ed0f0549dce4ef94d9d0bd0109bc7f8575d1 17492 pkg-haskell-tools_0.10.2.tar.xz
 6bd07b2a957b8c9a781a9ec3267934c8afce53f9 473822 
pkg-haskell-tools-dbgsym_0.10.2_amd64.deb
 dc6be1613033dd64057e33db83f6c57efe50af26 1170032 
pkg-haskell-tools_0.10.2_amd64.deb
Checksums-Sha256:
 cac0464c22b70f779e053217d4dc07f680383a25db820052727de7ae59a454fb 2322 
pkg-haskell-tools_0.10.2.dsc
 8efb800eed1b373445a9e63cd86a4bad7ef4688818008d931a3253bca2b8ae68 17492 
pkg-haskell-tools_0.10.2.tar.xz
 032f669f22b5bbdff4f8734675abe75411d625c06d32dc2d75607d39d482db7b 473822 
pkg-haskell-tools-dbgsym_0.10.2_amd64.deb
 bb91781444eac477adef4b3988651d578e0b6564c31585ca9afa749314fb198c 1170032 
pkg-haskell-tools_0.10.2_amd64.deb
Files:
 957ea208173adda6a614b24429d35943 2322 haskell extra 
pkg-haskell-tools_0.10.2.dsc
 f56af90d3bf90f355be43dbd938839fa 17492 haskell extra 
pkg-haskell-tools_0.10.2.tar.xz
 6a92b6c86d742f9b0c1d8c5784805b3d 473822 debug extra 

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

[Drew Parsons]

On Sun, 2016-03-13 at 19:59 +0100, Emilio Pozuelo Monfort wrote:
> [Adding debian-wb-team back to Cc]
> 
> On 13/03/16 17:56, Drew Parsons wrote:
> > 
> > On Sun, 2016-03-13 at 17:35 +0100, Emilio Pozuelo Monfort wrote:
> > > 
> > > On 13/03/16 16:34, Drew Parsons wrote:
> > > > 
> > What would make mipsel different to other architectures or from the
> > earlier successful mipsel build?  It's the same petsc.
> petsc may be at the same version, but the environment has changed. 
> It may be a bug in another package (e.g. an rdep) or a bug in petsc
> that was latent until now.
> 
> > > 
> > > Have you checked if it builds fine on a porterbox?
> > I tried but sbuild wouldn't work inside the schroot environment on
> > etler.
> Did you read the MOTD? See https://dsa.debian.org/doc/schroot/

I missed that. I'll add it to my bookmarks.


> Anyway given the build queue is currently empty on mipsel, I've given
> it back. 
> Let's see if the problem is fixed now...

Thanks for that. It's showing a very different build failure now, as if
something is wrong with mpi (openmpi).

I'll follow those schroot instructions and look directly.


Drew

Processed: Re: Bug#817808: php-kolab: postrm is buggy, breaks upgrades

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #817808 [php-kolab] php-kolab: postrm is buggy, breaks upgrades
Added tag(s) pending.

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

Bug#817808: php-kolab: postrm is buggy, breaks upgrades

[Sandro Knauß]

Control: tags -1 +pending

Hi,

thanks for repothing.
Yes you are right, that the quoting was not correct but it is remove_model 
that is incorrect:

> remove_module () {
> local step=$1 module=$2 inifile=$2.ini package=$3 args=$4
> ...
> }

changed to: 

 remove_module () {
 local step=$1 module=$2 inifile=$2.ini package=$3 args="$4"
 ...
 }

this is correct:
 
> remove_module $1 kolab php-kolab "$*"
> remove_module $1 kolabdummy php-kolab "$*"

$* is actually all arguments as single argument $@ would split the args in 
different arguments, and $4 should get all aguments and with $@ $4 not get all 
arguments. But because dash automatically splits the arguments, we have to add 
quotes around $4.

Fixed already in git master d0a6e11

regards,

sandro


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

Bug#817041: marked as done (librem0: Missing run-time dependency on libre0)

[Debian Bug Tracking System]

Your message dated Mon, 14 Mar 2016 00:51:05 +
with message-id 
and subject line Bug#817041: fixed in rem 0.4.7-2
has caused the Debian Bug report #817041,
regarding librem0: Missing run-time dependency on libre0
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.)


-- 
817041: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librem0
Version: 0.4.7-1
Severity: serious

Hi!

This package provides a shared library that is not self-contained, and
it is missing a run-time dependency on libre0, as it uses some of its
symbols. The library should link against all libraries it uses directly,
because otherwise it is pushing an internal implementation detail towards
its users.

A very simple example to illustrate:

  $ echo 'int main() { return 0; }' >rem.c
  $ gcc -o rem rem.c -lrem
  [ lots of undefined references to missing symbols… ]

I guess there's just a «-lre» missing somewhere in the build system.

(I found this while trying to build a local baresip package, so thanks
for trying to get that in Debian. :)

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: rem
Source-Version: 0.4.7-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rem package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Mar 2016 13:30:47 +0100
Source: rem
Binary: librem0 librem-dev librem0-dbg
Architecture: source amd64
Version: 0.4.7-2
Distribution: unstable
Urgency: low
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jonas Smedegaard 
Description:
 librem-dev - library for real-time audio and video processing (development)
 librem0- toolkit library for real-time audio and video processing
 librem0-dbg - library for real-time audio and video processing - debug symbols
Closes: 817041
Changes:
 rem (0.4.7-2) unstable; urgency=low
 .
   [ Vasudev Kamath ]
   * Mark Debian Multimedia team as maintainer for the package.
 Add myself to Uploaders.
   * Add 1001_fix_libre_linking patch to fix the libre0 linking issue.
 Closes: Bug#817041. Thanks to Guillem Jover.
   * Add libre quirk to d-shlibmove.
 .
   [ Jonas Smedegaard ]
   * Add myself as uploader.
   * Declare compliance with Debian Policy 3.9.7.
   * Update copyright info:
 + Add myself as copyright holder.
 + Add copyright & licensing header to rules file.
 + Relicense packaging except patches as GPL-3+.
 + Fix upstream project name (according to upstream README).
 + Fix add upstream tarball source URL (preserving SVN URL as
   secondary source).
 + Fix use double-space as delimiter between copyright holders.
 + Update preferred form of contact, based on upstream README.
   * Add lintian overrides regarding license in License-Reference field.
 See bug#s786450.
   * Bump watch file to format 4.
   * Add lintian override regarding debhelper 9.
   * Add lintian override regarding GPL-licensed packaging.
Checksums-Sha1:
 6d6a768b036f437fb03eaef01d0ea621c7e8280d 2149 rem_0.4.7-2.dsc
 43e015e7aee804fb471bbc6311fedb8e72b55c37 6532 rem_0.4.7-2.debian.tar.xz
 6b4f38fcd43b0fdd82e5166d2789ffcf83e70d17 30464 librem-dev_0.4.7-2_amd64.deb
 96d2b5fcb0eaf788ce8a21cadfb80632728daba6 49618 librem0-dbg_0.4.7-2_amd64.deb
 4603da41b0b111fc6e9b1f1aa0c656efbe0aa07b 25826 librem0_0.4.7-2_amd64.deb
Checksums-Sha256:
 8f68bf2b9c8d043f054dfc1c23a61bdb5bc5cc73dfa334bdfd7a85d429eb1353 2149 
rem_0.4.7-2.dsc
 43b4415c78724a692caa0bda5871e779351fa7bf55d5ecb3854645f46d5746cf 6532 
rem_0.4.7-2.debian.tar.xz
 be83fa96844492c5d9d1b925fbd8426ef9302341f22a1e54fe5eaa7e39e8c790 30464 
librem-dev_0.4.7-2_amd64.deb
 fcaa9f271bb9c4a1bba8f4f13852ad853beaa47a3bec8e1979b917bce7314e74 49618 
librem0-dbg_0.4.7-2_amd64.deb
 706354405ddc74a5be3c7ade0ce0a1d5eb7775ad471599ecb163b536e8ce5b89 25826 

Bug#816042: Don't include in stretch

[Jonas Smedegaard]

Quoting Moritz Muehlenhoff (2016-02-26 22:31:43)
> asterisk hasn't seen a maintainer upload to unstable in 2015. It's 
> already excluded from testing due to an unrelated FTBFS bug. This bug 
> is used to ensure that it doesn't enter stretch unless maintenance 
> (especially for the lifetime of stable) is properly ensured again.

I am concerned about above, and about the silence in response to this 
bugreport.

Please do care for this package.

If noone else cares, I will consider step up and take over maintaining 
this package (but I really would prefer not to do so: I have plenty of 
other packages to look after already).

 - Jonas

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

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


signature.asc
Description: signature

Bug#816108: marked as done (pinball: FTBFS in sid pbuilder enviorment)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 23:36:52 +
with message-id 
and subject line Bug#816108: fixed in pinball 0.3.1-13.3
has caused the Debian Bug report #816108,
regarding pinball: FTBFS in sid pbuilder enviorment
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.)


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

The package fails to build in a local rebuild in a sid pbuilder enviroment.

libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
debian/rules:21: recipe for target 'override_dh_auto_configure' failed
make[1]: Leaving directory '/build/pinball-0.3.1'
debian/rules:12: recipe for target 'build' failed

Complete buildlog attached.


--
tobi


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/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)
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Sat Feb 27 15:17:04 UTC 2016
I: pbuilder-time-stamp: 1456586224
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/base.tgz]
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 7.0.50~), libgl1-mesa-dev, libpng-dev, libsdl1.2-dev, 
freeglut3-dev, libsdl-image1.2-dev, libsdl-mixer1.2-dev, libogg-dev, 
libvorbis-dev, sp, sgmlspl, docbook, docbook-utils, libaa1-dev, libasound2-dev, 
libtiff-dev, autoconf, automake, libtool, libltdl-dev (>= 2.2.6b)
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 12520 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
The following NEW packages will be installed:
  autoconf{a} automake{a} autotools-dev{a} bsdmainutils{a} debhelper{a} 
dh-strip-nondeterminism{a} docbook{a} docbook-dsssl{a} docbook-utils{a} file{a} 
fontconfig-config{a} fonts-dejavu-core{a} freeglut3{a} freeglut3-dev{a} 
gettext{a} gettext-base{a} groff-base{a} intltool-debian{a} jadetex{a} 
libaa1{a} libaa1-dev{a} libarchive-zip-perl{a} libasound2{a} libasound2-data{a} 
libasound2-dev{a} libasyncns0{a} libavahi-client3{a} libavahi-common-data{a} 
libavahi-common3{a} libbsd0{a} libcaca-dev{a} libcaca0{a} libcroco3{a} 
libcups2{a} libcupsfilters1{a} libcupsimage2{a} libdbus-1-3{a} 
libdirectfb-1.2-9{a} libdirectfb-dev{a} libdirectfb-extra{a} libdrm-amdgpu1{a} 
libdrm-dev{a} libdrm-intel1{a} libdrm-nouveau2{a} libdrm-radeon1{a} libdrm2{a} 
libelf1{a} libexpat1{a} libffi6{a} libfile-stripnondeterminism-perl{a} 
libflac-dev{a} libflac8{a} libfluidsynth1{a} libfontconfig1{a} libfreetype6{a} 
libfreetype6-dev{a} libgl1-mesa-dev{a} libgl1-mesa-glx{a} libglapi-mesa{a} 
libglib2.0-0{a} libglib2.0-bi
 n{a} libglib2.0-data{a} libglib2.0-dev{a} libglu1-mesa{a} libglu1-mesa-dev{a} 
libgnutls30{a} libgpm2{a} libgraphite2-3{a} libgs9{a} libgs9-common{a} 
libgssapi-krb5-2{a} libharfbuzz-icu0{a} libharfbuzz0b{a} libhogweed4{a} 

Bug#816108: pinball: diff for NMU version 0.3.1-13.3

[Markus Koschany]

Control: tags -1 patch pending

Dear maintainer,

I've prepared an NMU for pinball (versioned as 0.3.1-13.3) and
uploaded it to unstable. I am attaching the debdiff to this bug report.

Regards,

Markus
diff -Nru pinball-0.3.1/debian/changelog pinball-0.3.1/debian/changelog
--- pinball-0.3.1/debian/changelog	2014-08-23 14:16:55.0 +0200
+++ pinball-0.3.1/debian/changelog	2016-03-13 23:36:15.0 +0100
@@ -1,3 +1,14 @@
+pinball (0.3.1-13.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove depcomp in dh_auto_configure override and prevent the FTBFS.
+Thanks to Tobias Frost for the report. (Closes: #816108)
+  * Use dh_fixperms override for arch-only and fix building with
+dpkg-buildflag -A.
+Thanks to Santiago Vila for the report. (Closes: #806093)
+
+ -- Markus Koschany   Sun, 13 Mar 2016 23:34:47 +0100
+
 pinball (0.3.1-13.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru pinball-0.3.1/debian/rules pinball-0.3.1/debian/rules
--- pinball-0.3.1/debian/rules	2014-08-23 14:16:55.0 +0200
+++ pinball-0.3.1/debian/rules	2016-03-13 23:36:15.0 +0100
@@ -18,6 +18,7 @@
 
 .PHONY: override_dh_auto_configure
 override_dh_auto_configure:
+	$(RM) depcomp
 	libtoolize --install --copy
 	aclocal
 	autoheader
@@ -36,7 +37,7 @@
 	dh_install
 
 .PHONY: override_dh_fixperms
-override_dh_fixperms:
+override_dh_fixperms-arch:
 	dh_fixperms
 	chown root:games debian/pinball/usr/games/pinball
 	chmod 2755 debian/pinball/usr/games/pinball

Bug#809733: marked as done (activemq: CVE-2015-5254: unsafe deserialization)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 22:51:18 +
with message-id 
and subject line Bug#809733: fixed in activemq 5.13.2+dfsg-1
has caused the Debian Bug report #809733,
regarding activemq: CVE-2015-5254: unsafe deserialization
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.)


-- 
809733: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: activemq
Version: 5.6.0+dfsg-1
Severity: grave
Tags: security upstream fixed-upstream

Hi,

the following vulnerability was published for activemq. I'm not very
familiar with activemq itself, so I'm reporting this with initial
severity grave, but let me know if you disagree.

CVE-2015-5254[0]:
Unsafe deserialization

Upstream advisory is at [1]:
| Description:
|
| JMS Object messages depends on Java Serialization for marshaling/unmashaling
| of the message payload. There are a couple of places inside the broker where
| deserialization can occur, like web console or stomp object message
| transformation. As deserialization of untrusted data can leaed to security
| flaws as demonstrated in various reports, this leaves the broker vunerable to
| this attack vector. Additionally, applications that consume ObjectMessage type
| of messages can be vunerable as they deserlize objects on
| ObjectMessage.getObject() calls.
|
| Mitigation:
|
| Upgrade to Apache ActiveMQ 5.13.0. Additionally if you're using ObjectMessage
| message type, you need to explicitly list trusted packages. To see how to do
| that, please take a look at: http://activemq.apache.org/objectmessage.html

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-5254
[1] 
http://activemq.apache.org/security-advisories.data/CVE-2015-5254-announcement.txt

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: activemq
Source-Version: 5.13.2+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated activemq package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Mar 2016 22:53:35 +0100
Source: activemq
Binary: libactivemq-java libactivemq-java-doc activemq
Architecture: source all
Version: 5.13.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 activemq   - Java message broker - server
 libactivemq-java - Java message broker core libraries
 libactivemq-java-doc - Java message broker core libraries - documentation
Closes: 770455 808636 809733
Changes:
 activemq (5.13.2+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
 - Fixes FTBFS. (Closes: #808636)
 - Fixes CVE-2015-5254: unsafe deserialization and all other security
   vulnerabilities. (Closes: #809733)
   * Switch from cdbs to dh sequencer.
   * Use Files-Excluded mechanism and drop orig-tar.sh
   * Vcs-fields: Use https.
   * Use java7-runtime-headless as alternative dependency for activemq.
   * Declare compliance with Debian Policy 3.9.7.
   * Remove debian/maven.cleanIgnoreRules.
   * debian/patches:
 - Drop all CVE-* patches. Fixed upstream.
 - Drop activemq-admin.patch because this file does not exist anymore.
 - Drop disable_some_modules.diff and disable modules with
   libactivemq-java.poms instead.
 - Drop exclude-* patches.
 - Rebase init_debian_default_values.diff.
 - Drop javadoc_links.diff because the activemq-core module does not exist
   anymore.
 - Add disable-broker-test-dependency.patch and disable test dependencies
   which would cause a FTBFS.
 - Add exclude-geronimo-jca.patch and remove code that depends on geronimo
   jca.
 - Add 

Processed: pinball: diff for NMU version 0.3.1-13.3

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #816108 [src:pinball] pinball: FTBFS in sid pbuilder enviorment
Added tag(s) patch and pending.

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

Bug#808636: marked as done (activemq: FTBFS: package org.apache.kahadb.index does not exist)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 22:51:18 +
with message-id 
and subject line Bug#808636: fixed in activemq 5.13.2+dfsg-1
has caused the Debian Bug report #808636,
regarding activemq: FTBFS: package org.apache.kahadb.index does not exist
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.)


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

Dear Maintainer,

The package fails to build:

[INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ activemq-core 
---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1511 source files to 
/activemq-5.6.0+dfsg1/activemq-core/target/classes
[INFO] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/broker/MutableBrokerFilter.java:
 Some input files use unchecked or unsafe operations.
[INFO] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/broker/MutableBrokerFilter.java:
 Recompile with -Xlint:unchecked for details.
[INFO] -
[WARNING] COMPILATION WARNING : 
[INFO] -
[WARNING] bootstrap class path not set in conjunction with -source 1.6
[INFO] 1 warning
[INFO] -
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[37,31]
 package org.apache.kahadb.index does not exist
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[38,33]
 package org.apache.kahadb.journal does not exist
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[39,33]
 package org.apache.kahadb.journal does not exist
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[40,30]
 package org.apache.kahadb.page does not exist
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[41,30]
 package org.apache.kahadb.page does not exist
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[42,30]
 package org.apache.kahadb.page does not exist
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[43,30]
 package org.apache.kahadb.util does not exist
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[44,30]
 package org.apache.kahadb.util does not exist
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[45,30]
 package org.apache.kahadb.util does not exist
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[46,30]
 package org.apache.kahadb.util does not exist
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[61,5]
 cannot find symbol
  symbol:   class PageFile
  location: class org.apache.activemq.store.kahadb.plist.PListStore
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[62,13]
 cannot find symbol
  symbol:   class Journal
  location: class org.apache.activemq.store.kahadb.plist.PListStore
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[63,13]
 cannot find symbol
  symbol:   class LockFile
  location: class org.apache.activemq.store.kahadb.plist.PListStore
[ERROR] 
/activemq-5.6.0+dfsg1/activemq-core/src/main/java/org/apache/activemq/store/kahadb/plist/PListStore.java:[162,38]
 cannot find symbol
  symbol:   class VariableMarshaller
  location: class org.apache.activemq.store.kahadb.plist.PListStore

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

-- System Information:
Debian Release: stretch/sid
APT 

Bug#818127: libraw1394: FTBFS in stretch (TeX error, jadetex)

[Santiago Vila]

Package: src:libraw1394
Version: 2.1.1-2
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


kpathsea: Running mktexfmt pdfjadetex.fmt
mktexfmt: mktexfmt is using the following fmtutil.cnf files (in precedence 
order):
mktexfmt:   /usr/share/texmf/web2c/fmtutil.cnf
mktexfmt:   /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf
mktexfmt: mktexfmt is using the following fmtutil.cnf file for writing changes:
mktexfmt:   /sbuild-nonexistent/.texmf-config/web2c/fmtutil.cnf
/usr/bin/mktexfmt: mkdir(/sbuild-nonexistent/) failed, goodbye: Permission 
denied
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) 
(preloaded format=pdfjadetex)
 restricted \write18 enabled.
 I can't find the format file `pdfjadetex.fmt'!


The full build log is attached.

Thanks.

libraw1394_2.1.1-2_amd64-20160313-2336.gz
Description: application/gzip

Bug#725629: marked as done (vice: sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 22:27:31 +
with message-id 
and subject line Bug#725629: fixed in vice 2.4.dfsg+2.4.25-2
has caused the Debian Bug report #725629,
regarding vice: sometimes FTBFS: error while opening 
"src/arch/win32/res.rc.po.c" for reading: No such file or directory
to be marked as done.

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

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


-- 
725629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vice
Version: 2.4.dfsg-1
Severity: serious

On Sun, Oct 06, 2013 at 09:49:17PM +0100, Steven Chamberlain wrote:
> Please consider giving back vice for build on s390;  the same issue was
> occurring on kfreebsd-amd64 but I cannot reproduce it there.

Not really.  This smells like race condition.  Did you compare the build
logs?  Building with -jX with a large enough X may help.

> https://buildd.debian.org/status/fetch.php?pkg=vice=s390=2.4.dfsg-1=1377367526
> > PATH=../src:$PATH /usr/bin/xgettext --default-domain=vice --directory=.. 
> > --directory=.. \
> >   --add-comments --keyword=_ --keyword=N_ \
> >   --files-from=./POTFILES.in \
> >   -o ./vice.pot
> > /usr/bin/xgettext: error while opening "src/arch/win32/res.rc.po.c" for 
> > reading: No such file or directory

| $ ls src/arch/win32/res.rc.po.c
| ls: cannot access src/arch/win32/res.rc.po.c: No such file or directory

This file does not exist in the source code.  How does the build make
sure the file is built _before_ this rules fires?

Bastian

-- 
"What terrible way to die."
"There are no good ways."
-- Sulu and Kirk, "That Which Survives", stardate unknown
--- End Message ---
--- Begin Message ---
Source: vice
Source-Version: 2.4.dfsg+2.4.25-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated vice package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Mar 2016 19:35:18 +0100
Source: vice
Binary: vice
Architecture: source amd64
Version: 2.4.dfsg+2.4.25-2
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 vice   - Versatile Commodore Emulator
Closes: 725629 817125
Changes:
 vice (2.4.dfsg+2.4.25-2) unstable; urgency=low
 .
   * Try to prevent FTBFS due to build race (closes: #725629).
   * Remove $HOME variable to fix FTBFS on Ubuntu (closes: #817125).
Checksums-Sha1:
 e1b98fc96ed33537a344e97f90418b40743a5c76 2101 vice_2.4.dfsg+2.4.25-2.dsc
 d3df5a7401c0888eafc2b9e67652f2306dc630b1 24960 
vice_2.4.dfsg+2.4.25-2.debian.tar.xz
 6dc91b8a05799105a80c4b5a8e38adb7f6b568be 62500516 
vice-dbgsym_2.4.dfsg+2.4.25-2_amd64.deb
 503ad42d804c99aef7b72c4447603e594043b08f 4261666 
vice_2.4.dfsg+2.4.25-2_amd64.deb
Checksums-Sha256:
 fd10fc281cd2923c38771530ba68d75544f6f87d67e5ab70121d7b4399b507a4 2101 
vice_2.4.dfsg+2.4.25-2.dsc
 962da07efdbef437b5e9f447a91899441d9553a9afe888be68e4d77c60729b20 24960 
vice_2.4.dfsg+2.4.25-2.debian.tar.xz
 fef2ac56eec61415f1f47413aee304824c865883d406b1095bfde4d9f247575e 62500516 
vice-dbgsym_2.4.dfsg+2.4.25-2_amd64.deb
 4b605b251a21f0350351498f567dd2e45215320bdca0ee82edbeae96d6d147c8 4261666 
vice_2.4.dfsg+2.4.25-2_amd64.deb
Files:
 eda76d476194712ebbd2bd001541c46d 2101 contrib/otherosfs optional 
vice_2.4.dfsg+2.4.25-2.dsc
 8024351224e06d88e0ca391307c2e1b4 24960 contrib/otherosfs optional 
vice_2.4.dfsg+2.4.25-2.debian.tar.xz
 fba988749684fe4cc004c02e47c10ad1 62500516 contrib/debug extra 
vice-dbgsym_2.4.dfsg+2.4.25-2_amd64.deb
 82a4ce0ad2cc3bbb83676abd7fd46a26 4261666 contrib/otherosfs optional 
vice_2.4.dfsg+2.4.25-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW5eNNAAoJENzjEOeGTMi/tfQP/1e+1vMW4MJcE1uPNq3tZn+G
SGp8DWMpiE9TCs6TLOvwD/HETblg8fTWoE+H36xrsGaRCwHBox/VJXJ+jvX7+smL
BpenCIuqiYA5VOgUQaUAcu2ZKE8g9JYVWhhuk1mfe0CQExTz0z2G+vU/EQtq2cTB

Bug#756916: marked as done (vice: sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 22:27:31 +
with message-id 
and subject line Bug#725629: fixed in vice 2.4.dfsg+2.4.25-2
has caused the Debian Bug report #725629,
regarding vice: sometimes FTBFS: error while opening 
"src/arch/win32/res.rc.po.c" for reading: No such file or directory
to be marked as done.

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

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


-- 
725629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vice
Version: 2.4.dfsg+2.4.7-1
Severity: serious
Justification: FTBFS

Hi,

your package no longer builds on kfreebsd-amd64:
| Making all in po
| make[2]: Entering directory '/«BUILDDIR»/vice-2.4.dfsg+2.4.7/po'
| gcc -I.. -I../intl -g -O3   -Wall -Wno-inline ./intl2po.c -o intl2po
| ( if test 'x.' != 'x.'; then \
| posrcprefix='../'; \
|   else \
| posrcprefix="../"; \
|   fi; \
|   rm -f POTFILES-t POTFILES \
| && (sed -e '/^#/d' -e '/^[]*$/d' \
|   -e "s@.*@   $posrcprefix& @" < ./POTFILES.in \
|   | sed -e '$s/\\$//') > POTFILES-t \
| && chmod a-w POTFILES-t \
| && mv POTFILES-t POTFILES )
| PATH=../src:$PATH /usr/bin/xgettext --default-domain=vice --directory=.. 
--directory=.. \
|   --add-comments --keyword=_ --keyword=N_ \
|   --files-from=./POTFILES.in \
|   -o ./vice.pot
| /usr/bin/xgettext: error while opening "src/arch/win32/res.rc.po.c" for 
reading: No such file or directory
| make[2]: *** [vice.pot] Error 1

Full build log:
  
https://buildd.debian.org/status/fetch.php?pkg=vice=kfreebsd-amd64=2.4.dfsg%2B2.4.7-1=1406758769

Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Source: vice
Source-Version: 2.4.dfsg+2.4.25-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated vice package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Mar 2016 19:35:18 +0100
Source: vice
Binary: vice
Architecture: source amd64
Version: 2.4.dfsg+2.4.25-2
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 vice   - Versatile Commodore Emulator
Closes: 725629 817125
Changes:
 vice (2.4.dfsg+2.4.25-2) unstable; urgency=low
 .
   * Try to prevent FTBFS due to build race (closes: #725629).
   * Remove $HOME variable to fix FTBFS on Ubuntu (closes: #817125).
Checksums-Sha1:
 e1b98fc96ed33537a344e97f90418b40743a5c76 2101 vice_2.4.dfsg+2.4.25-2.dsc
 d3df5a7401c0888eafc2b9e67652f2306dc630b1 24960 
vice_2.4.dfsg+2.4.25-2.debian.tar.xz
 6dc91b8a05799105a80c4b5a8e38adb7f6b568be 62500516 
vice-dbgsym_2.4.dfsg+2.4.25-2_amd64.deb
 503ad42d804c99aef7b72c4447603e594043b08f 4261666 
vice_2.4.dfsg+2.4.25-2_amd64.deb
Checksums-Sha256:
 fd10fc281cd2923c38771530ba68d75544f6f87d67e5ab70121d7b4399b507a4 2101 
vice_2.4.dfsg+2.4.25-2.dsc
 962da07efdbef437b5e9f447a91899441d9553a9afe888be68e4d77c60729b20 24960 
vice_2.4.dfsg+2.4.25-2.debian.tar.xz
 fef2ac56eec61415f1f47413aee304824c865883d406b1095bfde4d9f247575e 62500516 
vice-dbgsym_2.4.dfsg+2.4.25-2_amd64.deb
 4b605b251a21f0350351498f567dd2e45215320bdca0ee82edbeae96d6d147c8 4261666 
vice_2.4.dfsg+2.4.25-2_amd64.deb
Files:
 eda76d476194712ebbd2bd001541c46d 2101 contrib/otherosfs optional 
vice_2.4.dfsg+2.4.25-2.dsc
 8024351224e06d88e0ca391307c2e1b4 24960 contrib/otherosfs optional 
vice_2.4.dfsg+2.4.25-2.debian.tar.xz
 fba988749684fe4cc004c02e47c10ad1 62500516 contrib/debug extra 
vice-dbgsym_2.4.dfsg+2.4.25-2_amd64.deb
 82a4ce0ad2cc3bbb83676abd7fd46a26 4261666 contrib/otherosfs optional 
vice_2.4.dfsg+2.4.25-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW5eNNAAoJENzjEOeGTMi/tfQP/1e+1vMW4MJcE1uPNq3tZn+G
SGp8DWMpiE9TCs6TLOvwD/HETblg8fTWoE+H36xrsGaRCwHBox/VJXJ+jvX7+smL
BpenCIuqiYA5VOgUQaUAcu2ZKE8g9JYVWhhuk1mfe0CQExTz0z2G+vU/EQtq2cTB
FgFMiOv04EwUhcADxxJh+Db6Bw84jUy6kgJIGGTc37SahapgP1laxTcNThs5Qwr0

Bug#818124: easymp3gain: FTBFS in stretch

[Santiago Vila]

Package: src:easymp3gain
Version: 0.5.0+svn135-6
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


-- Check for Lazbuild: /usr/bin/lazbuild
CMake Error at data/cmake/FindLazbuild.cmake:36 (message):
  Could not check LCL version (Lazbuild found?)
  Call Stack (most recent call first):
src/CMakeLists.txt:3 (find_package)


-- Configuring incomplete, errors occurred!
See also 
"/<>/easymp3gain-0.5.0+svn135/build/CMakeFiles/CMakeOutput.log".
debian/rules:21: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>/easymp3gain-0.5.0+svn135'
debian/rules:18: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


The full build log is attached.

Thanks.

easymp3gain_0.5.0+svn135-6_amd64-20160313-2250.gz
Description: application/gzip

Bug#818125: libsass-python: FTBFS in stretch

[Santiago Vila]

Package: src:libsass-python
Version: 0.9.3-1
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


AssertionError: {'mappings': 
';,CAAC,CACC,CAAC,CAAC;EACA,SAAS,EAAE,IAAK,G[84 chars]ss']} != {'mappings': 
';,AACE,CADD,CACC,CAAC,CAAC;EACA,SAAS,EAAE,I[89 chars]ss']}
  {'file': '../test/b.css',
  -  'mappings': ';,CAAC,CACC,CAAC,CAAC;EACA,SAAS,EAAE,IAAK,GACjB',
  ? -

+  'mappings': ';,AACE,CADD,CACC,CAAC,CAAC;EACA,SAAS,EAAE,IAAK,GACjB',
?++

   'names': [],
  'sources': ['../test/b.scss'],
 'version': 3}



The full build log is attached.

Thanks.

libsass-python_0.9.3-1_amd64-20160313-2251.gz
Description: application/gzip

Bug#818123: doublecmd: FTBFS in stretch

[Santiago Vila]

Package: src:doublecmd
Version: 0.6.6-1
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


/<>/src/./platform/unix/umyunix.pas(523,83) Error: (3069)
Call by var for arg no. 3 has to match exactly: Go t "UTF8String"
expected "AnsiString"


The full build log is attached.

Thanks.

doublecmd_0.6.6-1_amd64-20160313-2250.gz
Description: application/gzip

Bug#818122: docker.io: FTBFS in stretch

[Santiago Vila]

Package: src:docker.io
Version: 1.8.3~ds1-2
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:


---> Making bundle: dynbinary (in bundles/1.8.3/dynbinary)
/usr/share/gocode/src/github.com/opencontainers/runc/libcontainer/cgroups/utils.go:16:2:
 cannot find package "github.com/docker/go-units" in any of:
 /usr/lib/go/src/github.com/docker/go-units (from $GOROOT)
 /<>/.gopath/src/github.com/docker/go-units (from $GOPATH)
 /usr/share/gocode/src/github.com/docker/go-units
debian/rules:59: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:122: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2


The full build log is attached.

Thanks.

docker.io_1.8.3~ds1-2_amd64-20160313-2249.gz
Description: application/gzip

Bug#818121: consul-migrate: FTBFS in stretch

[Santiago Vila]

Package: src:consul-migrate
Version: 0.1.0-1
Severity: serious

Dear maintainer:

This package currently FTBFS in stretch:


=== RUN   TestMigrator_migrate
--- FAIL: TestMigrator_migrate (2.01s)
panic: runtime error: cgo argument has Go pointer to Go pointer [recovered]
panic: runtime error: cgo argument has Go pointer to Go pointer


The full build log is attached.

Thanks.

consul-migrate_0.1.0-1_amd64-20160313-2249.gz
Description: application/gzip

Bug#725629: vice: sometimes FTBFS: error while opening "src/arch/win32/res.rc.po.c" for reading: No such file or directory

[GCS]

On Tue, Mar 8, 2016 at 11:08 AM, Graham Inggs  wrote:
> This problem still occurs from time to time.
 While it's rare, it happens from time to time. :-( Even upstream
couldn't reliably reproduce it and hence no real solution exist to
prevent this. Now I try an other way, forcing the sequence it should
be built.

Regards,
Laszlo/GCS

Bug#809744: marked as done (/var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure')

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 21:34:34 +
with message-id 
and subject line Bug#809744: fixed in systemd 215-17+deb8u4
has caused the Debian Bug report #809744,
regarding /var/lib/dpkg/info/udev.prerm called with unknown argument 
'deconfigure'
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.)


-- 
809744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: udev
Version: 228-3
Severity: grave

Package installation Race Condition? Also filed bug 809743.

Unpacking libpam-systemd:i386 (228-3) over (228-2+b1) ...
dpkg: considering deconfiguration of ifupdown, which would be broken by 
installation of systemd ...
dpkg: yes, will deconfigure ifupdown (broken by systemd)
Preparing to unpack .../systemd_228-3_i386.deb ...
De-configuring ifupdown (0.8.4) ...
Unpacking systemd (228-3) over (228-2+b1) ...
dpkg: considering deconfiguration of udev, which would be broken by 
installation of ifupdown ...
dpkg: yes, will deconfigure udev (broken by ifupdown)
Preparing to unpack .../ifupdown_0.8.5_i386.deb ...
De-configuring udev (228-2+b1) ...
/var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'
dpkg: error processing archive /var/cache/apt/archives/ifupdown_0.8.5_i386.deb 
(--unpack):
 subprocess installed pre-removal script returned error exit status 1


Errors were encountered while processing:
 /var/cache/apt/archives/ifupdown_0.8.5_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
Setting up libudev1:i386 (228-3) ...
dpkg: dependency problems prevent configuration of ifupdown:
 systemd (228-3) breaks ifupdown (<< 0.8.5~) and is unpacked but not configured.
  Version of ifupdown to be configured is 0.8.4.
 udev (228-3) breaks ifupdown (<< 0.8.5~) and is unpacked but not configured.
  Version of ifupdown to be configured is 0.8.4.

dpkg: error processing package ifupdown (--configure):
 dependency problems - leaving unconfigured
Setting up udev (228-3) ...
--- End Message ---
--- Begin Message ---
Source: systemd
Source-Version: 215-17+deb8u4

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

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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd 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, 03 Mar 2016 19:51:22 +0100
Source: systemd
Binary: systemd systemd-sysv libpam-systemd libsystemd0 libsystemd-dev 
libsystemd-login0 libsystemd-login-dev libsystemd-daemon0 libsystemd-daemon-dev 
libsystemd-journal0 libsystemd-journal-dev libsystemd-id128-0 
libsystemd-id128-dev udev libudev1 libudev-dev udev-udeb libudev1-udeb 
libgudev-1.0-0 gir1.2-gudev-1.0 libgudev-1.0-dev python3-systemd systemd-dbg
Architecture: source amd64
Version: 215-17+deb8u4
Distribution: stable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Description:
 gir1.2-gudev-1.0 - libgudev-1.0 introspection data
 libgudev-1.0-0 - GObject-based wrapper library for libudev
 libgudev-1.0-dev - libgudev-1.0 development files
 libpam-systemd - system and service manager - PAM module
 libsystemd-daemon-dev - systemd utility library (transitional package)
 libsystemd-daemon0 - systemd utility library (deprecated)
 libsystemd-dev - systemd utility library - development files
 libsystemd-id128-0 - systemd 128 bit ID utility library (deprecated)
 libsystemd-id128-dev - systemd 128 bit ID utility library (transitional 
package)
 libsystemd-journal-dev - systemd journal utility library (transitional package)
 libsystemd-journal0 - systemd journal utility library (deprecated)
 libsystemd-login-dev - systemd login utility library (transitional package)
 libsystemd-login0 - systemd login utility library (deprecated)
 libsystemd0 - systemd utility library
 libudev-dev - libudev development files
 libudev1   - 

Bug#789162: marked as done (aptdaemon: CVE-2015-1323: information disclosure via simulate dbus method)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 21:35:33 +
with message-id 
and subject line Bug#789162: fixed in aptdaemon 0.45-2+deb7u1
has caused the Debian Bug report #789162,
regarding aptdaemon: CVE-2015-1323: information disclosure via simulate dbus 
method
to be marked as done.

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

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


-- 
789162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aptdaemon
Version: 1.1.1-4
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for aptdaemon, which AFICS
as well affects Debian.

CVE-2015-1323[0]:
information disclosure via simulate dbus method

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-1323
[1] http://www.ubuntu.com/usn/usn-2648-1/
[2] https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1449587

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: aptdaemon
Source-Version: 0.45-2+deb7u1

We believe that the bug you reported is fixed in the latest version of
aptdaemon, 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.
Guido Günther  (supplier of updated aptdaemon 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, 29 Feb 2016 08:33:47 +0100
Source: aptdaemon
Binary: aptdaemon python-aptdaemon python-aptdaemon.test aptdaemon-data 
python-aptdaemon-gtk python-aptdaemon.pkcompat python-aptdaemon.gtkwidgets 
python-aptdaemon.gtk3widgets
Architecture: source all
Version: 0.45-2+deb7u1
Distribution: oldstable-proposed-updates
Urgency: medium
Maintainer: Julian Andres Klode 
Changed-By: Guido Günther 
Description: 
 aptdaemon  - transaction based package management service
 aptdaemon-data - data files for clients
 python-aptdaemon - Python module for the server and client of aptdaemon
 python-aptdaemon-gtk - Transitional dummy package
 python-aptdaemon.gtk3widgets - Python GTK+ 3 widgets to run an aptdaemon client
 python-aptdaemon.gtkwidgets - Python GTK+ 2 widgets to run an aptdaemon client
 python-aptdaemon.pkcompat - PackageKit compatibilty for AptDaemon
 python-aptdaemon.test - Test environment for aptdaemon clients
Closes: 789162
Changes: 
 aptdaemon (0.45-2+deb7u1) oldstable-proposed-updates; urgency=medium
 .
   * Non maintainer upload
   * Add CVE-2015-1323.patch to address CVE-2015-1323 - taken from
 0.43+bzr805-0ubuntu10 (Closes: #789162)
Checksums-Sha1: 
 7055fbddda2b7f804eb561b5ab3422dea00379d3 2545 aptdaemon_0.45-2+deb7u1.dsc
 8e6ebcd396b4ffbe2901ca68b4625594ebb8a8c7 18952 
aptdaemon_0.45-2+deb7u1.debian.tar.xz
 b69772e774c49c00f1ea2a3349aa77a4faefa060 277740 aptdaemon_0.45-2+deb7u1_all.deb
 a6e285621112b7ad9362876d166f95454308ef38 92584 
python-aptdaemon_0.45-2+deb7u1_all.deb
 1f1e0752373d480e52b39773e11a2c6f79b1f915 91818 
python-aptdaemon.test_0.45-2+deb7u1_all.deb
 4d06fbda00c53d6454ba2e2e1eb976920614d3e0 191212 
aptdaemon-data_0.45-2+deb7u1_all.deb
 5b5f12c72343bfa3f1d9fe7840999e365c5037d2 13500 
python-aptdaemon-gtk_0.45-2+deb7u1_all.deb
 3ca6efd93a0149f6421b1e588b3550993ed10e9a 41856 
python-aptdaemon.pkcompat_0.45-2+deb7u1_all.deb
 806bde63b02a844679943d2477b63c7c5e0bae6d 26504 
python-aptdaemon.gtkwidgets_0.45-2+deb7u1_all.deb
 f2ecf5eabdf21331bd7aa323d2e23cac3250f0a5 27450 
python-aptdaemon.gtk3widgets_0.45-2+deb7u1_all.deb
Checksums-Sha256: 
 9b0040a7c76489a01775ed72173bf2c6a695f454a2a5c6bb45b6563f4159907c 2545 
aptdaemon_0.45-2+deb7u1.dsc
 8b036b8297ee5964bb521522a543e33a9195e2751359a5965204395b5e21352c 18952 
aptdaemon_0.45-2+deb7u1.debian.tar.xz
 ba219a6c636fcd043a796f45a9e8799787a9b5612cc5536b30e8ed10d207eae2 277740 
aptdaemon_0.45-2+deb7u1_all.deb
 5f2c48a4c2aca3cec7f06159ed939295d27163cedaa21c33f9c73efd70cc7c15 92584 
python-aptdaemon_0.45-2+deb7u1_all.deb
 

Bug#815125: [Fwd: [PATCH] x86/efi: Always map boot service regions into new EFI page tables]

[Zdravko Yanakiev]

Hi Ben,

This patch fixes the problem for me. Thanks for looking into this issue!

Zdravko Yanakiev

On 13.03.2016 14:52, Ben Hutchings wrote:
> You got dropped off the cc list for some of the discussion.  Please can
> you test Matt's latest patch (attached).
> 
> Ben.
> 



signature.asc
Description: OpenPGP digital signature

Bug#817199: transcode: should this package be removed?

[Sebastian Ramacher]

Hi

On 2016-03-09 16:42:20, Fabian Greffrath wrote:
> Am Dienstag, den 08.03.2016, 23:39 +0100 schrieb Sebastian Ramacher:
> > What do you think?
> 
> No objections, except for this:
> 
> $ apt-cache rdepends transcode
> transcode
> Reverse Depends:
>   transcode-doc
>   xjadeo
>   transcode-dbg
>   multimedia-video
>   python-mecavideo
>   dvdwizard
> 
> It appears that at least dvdwizard has a hard Depends on transcode.

Yes, dvdwizard would have to be RoQ-ed if we are going to remove transcode. But
it's also dead upstream and orphaned.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#817828: marked as done (php-mail-mime: Missing dependency on php-pear)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 19:47:12 +
with message-id 
and subject line Bug#817828: fixed in php-mail-mime 1.8.9-1+deb8u1
has caused the Debian Bug report #817828,
regarding php-mail-mime: Missing dependency on php-pear
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.)


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

Dear Maintainer,

please consider registering a hard dependency on the php-pear package
for php-mail-mime, as it will not work otherwise.

As seen in /usr/share/php/Mail/mime.php:
  66 require_once 'PEAR.php';   
  

This is the first effective line of code in this file.

Thank you!

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

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

Versions of packages php-mail-mime depends on:
ii  php5-common  5.6.17+dfsg-0+deb8u1

php-mail-mime recommends no packages.

php-mail-mime suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: php-mail-mime
Source-Version: 1.8.9-1+deb8u1

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

Debian distribution maintenance software
pp.
Prach Pongpanich  (supplier of updated php-mail-mime 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Mar 2016 14:25:09 +0700
Source: php-mail-mime
Binary: php-mail-mime
Architecture: source all
Version: 1.8.9-1+deb8u1
Distribution: jessie
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: Prach Pongpanich 
Description:
 php-mail-mime - PHP PEAR module for creating MIME messages
Closes: 817828
Changes:
 php-mail-mime (1.8.9-1+deb8u1) jessie; urgency=medium
 .
   * Add dependency on php-pear (Closes: #817828)
Checksums-Sha1:
 a3fbd809fb9219cde439258dbbfdff5b42442198 2069 php-mail-mime_1.8.9-1+deb8u1.dsc
 2bdbd42187f67f418b7becb23a1b885f5a71ec20 3864 
php-mail-mime_1.8.9-1+deb8u1.debian.tar.xz
 cc7f50b7d4e0e774edd403d91ed0b2b4f3f63f90 36386 
php-mail-mime_1.8.9-1+deb8u1_all.deb
Checksums-Sha256:
 a93bd2836714076428f29bcac00318d80412b06138d81f87a8b0a1dc6852c35c 2069 
php-mail-mime_1.8.9-1+deb8u1.dsc
 429201a1640be08f40fc239baa97f615d2aa1ade9c2a32d3709424660425308b 3864 
php-mail-mime_1.8.9-1+deb8u1.debian.tar.xz
 3c65a8e4bb00b0da95681c4186c82e1e5bf27beba8626e75d906346f16950435 36386 
php-mail-mime_1.8.9-1+deb8u1_all.deb
Files:
 b45e79762c7724bcde4121987448fef6 2069 php optional 
php-mail-mime_1.8.9-1+deb8u1.dsc
 7becfe65a8796e3bf07e1b9753b99b76 3864 php optional 
php-mail-mime_1.8.9-1+deb8u1.debian.tar.xz
 0bc1eae7b6a3e8eec9a97db937a9a9e2 36386 php optional 
php-mail-mime_1.8.9-1+deb8u1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJW5XipAAoJEDkJHoEjzhwJuasQAKHjN0POoCNNJtvhZ6P2Nzry
T+AHRfiJAe3sB+gKvpzsUDeJYyFWwT/sw0DAzIKPi8BSPezSLsP31DvXdxNaUwcV
bkuqZZ24oltmV7C3s+NogytYZod9R4D3cIAW7M8TR6f84o90gpuPTBS8lyAOHwk2
DWB1BWfTFpvzkUlZb/Lj5/TtpQ+g6vMFIjBH1Iz9WFpUOgb+DHurATSsKyf4EWqW
wDzmmVKiw+8cwW978KLZwS7nij+XR4SunnM05IBwA7Osk0cRwb5u+9f96zeTCZ7O
AhfUFss9kkpg+sKz+CubshndP61htdERdZuQFgyXMj5L4Um4UwoWa2jJOGD7Z3+Z
4f2mwRXvK5lo31MXZzTbmKMlh6SgmHh5d0Ftmzv1lo41m5BeaED8ECcsudwmjPvb
P0udcLpKOS/mDeq+lKzDJ9YQvHCBD9CjTXsQ6E1AGlIm49xIrMseddBLiamdlsO8
tCl95nyBkNV2sM7wrunuLOsiswjeXgRANohtsZX1ce2lyx+lMus37aIyvw3rrPc0
QcR1CHHAUBGMYJLBvxr3vsgikxNpJW/ggtrIdv4j2v6n/THxlxT4PXkk+DIgTTb2
WgoUDIyBhJ3pqdcXo/LqlgEcxecy6uc/tEBQP80nzeUDtae6kYc0btvSSCSvhfKn
sA4HQZEL1MHD4kqGFncY
=PoKc
-END PGP SIGNATURE End Message ---

Bug#813995: marked as done (flashcp writes to nand without being aware of bad blocks)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 19:47:11 +
with message-id 
and subject line Bug#813995: fixed in flash-kernel 3.35+deb8u3
has caused the Debian Bug report #813995,
regarding flashcp writes to nand without being aware of bad blocks
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.)


-- 
813995: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flash-kernel
Version: 3.35+deb8u2
Severity: critical
Justification: causes serious data loss
Control: block 806926 with -1

Hello,

when flash-kernel writes a kernel/initrd to NAND flash it uses plain
write(2) to /dev/mtdX (flash-kernel < 3.52) or flashcp
(flash-kernel >= 3.52). If the device being written to has bad blocks
these are tried to be erased and written by both approaches.

This results in a non-booting system at best. In general writing to bad
blocks can also affect other (otherwise good) blocks and so result in
loss of unrelated data. I never saw this in practise, but the
manufacturers of NAND flash say so.

I didn't check which machines are affected, but Netgear ReadyNAS 102/104
(which isn't in flash-kernel's database yet, but see below for the
obvious entry to add support for them and #806926) is affected and flash
kernel managed to break a ReadyNAS 102 already (non-permanently by good
fortune as far as I can tell up to now).
I guess there are several other machines affected though.

The right fix is to use nandwrite to write to NAND flash and only use
flashcp for NOR.

Something like

test -f /sys/class/mtd/mtdX/oobsize

could be used to detect if the device is NAND or NOR. But there might be
more reliable ways I'm not aware of.

I will debug/test a bit more with the broken rn102 (and its owner :-) to
maybe come up with a patch, but if someone beats me that's very welcome,
too.

Best regards
Uwe

-- System Information:
Debian Release: 8.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (500, 'testing'), (1, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 3.16.0-4-armmp (SMP w/1 CPU core)
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 flash-kernel depends on:
ii  debconf [debconf-2.0]  1.5.56
ii  devio  1.2-1
ii  initramfs-tools0.120
ii  linux-base 3.5
ii  ucf3.0030

Versions of packages flash-kernel recommends:
ii  u-boot-tools  2014.10+dfsg1-5

flash-kernel suggests no packages.

-- Configuration Files:
/etc/flash-kernel/db changed:
Machine: NETGEAR ReadyNAS 104
DTB-Id: armada-370-netgear-rn104.dtb
DTB-Append: yes
Mtd-Kernel: uImage
Mtd-Initrd: minirootfs
U-Boot-Kernel-Address: 0x0400
U-Boot-Initrd-Address: 0x0500
Required-Packages: u-boot-tools


-- debconf information:
  flash-kernel/linux_cmdline: quiet
--- End Message ---
--- Begin Message ---
Source: flash-kernel
Source-Version: 3.35+deb8u3

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

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

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

Debian distribution maintenance software
pp.
Uwe Kleine-König  (supplier of updated flash-kernel 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 10 Mar 2016 20:30:19 +0100
Source: flash-kernel
Binary: flash-kernel flash-kernel-installer
Architecture: source
Version: 3.35+deb8u3
Distribution: stable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Uwe Kleine-König 
Description:
 flash-kernel - utility to make certain embedded devices bootable
 flash-kernel-installer - Make the system bootable (udeb)
Closes: 794265 813995
Changes:
 flash-kernel (3.35+deb8u3) stable; urgency=medium
 .
   [ Karsten Merker ]
   * Disable the use of modprobe and udevadm in the mtdblock() function
 while running the testsuite.
 .
   [ Ian Campbell ]
   * Use /dev/mtdN when flashing, rather than needlessly going 

Bug#789162: marked as done (aptdaemon: CVE-2015-1323: information disclosure via simulate dbus method)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 19:47:10 +
with message-id 
and subject line Bug#789162: fixed in aptdaemon 1.1.1-4+deb8u1
has caused the Debian Bug report #789162,
regarding aptdaemon: CVE-2015-1323: information disclosure via simulate dbus 
method
to be marked as done.

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

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


-- 
789162: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aptdaemon
Version: 1.1.1-4
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for aptdaemon, which AFICS
as well affects Debian.

CVE-2015-1323[0]:
information disclosure via simulate dbus method

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2015-1323
[1] http://www.ubuntu.com/usn/usn-2648-1/
[2] https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1449587

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: aptdaemon
Source-Version: 1.1.1-4+deb8u1

We believe that the bug you reported is fixed in the latest version of
aptdaemon, 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.
Guido Günther  (supplier of updated aptdaemon 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, 29 Feb 2016 21:13:01 +0100
Source: aptdaemon
Binary: aptdaemon python3-aptdaemon python-aptdaemon python3-aptdaemon.test 
aptdaemon-data python-aptdaemon-gtk python3-aptdaemon.pkcompat 
python-aptdaemon.gtkwidgets python3-aptdaemon.gtk3widgets 
python-aptdaemon.gtk3widgets
Architecture: all source
Version: 1.1.1-4+deb8u1
Distribution: stable-proposed-updates
Urgency: medium
Maintainer: Julian Andres Klode 
Changed-By: Guido Günther 
Closes: 789162
Description: 
 aptdaemon-data - data files for clients
 aptdaemon  - transaction based package management service
 python3-aptdaemon.gtk3widgets - Python 3 GTK+ 3 widgets to run an aptdaemon 
client
 python3-aptdaemon.pkcompat - PackageKit compatibilty for AptDaemon
 python3-aptdaemon - Python 3 modules for the server and client of aptdaemon
 python3-aptdaemon.test - Test environment for aptdaemon clients
 python-aptdaemon.gtk3widgets - Python 2 GTK+ 3 widgets to run an aptdaemon 
client
 python-aptdaemon-gtk - Transitional dummy package
 python-aptdaemon.gtkwidgets - Python GTK+ 2 widgets to run an aptdaemon client
 python-aptdaemon - Python 2 modules for the server and client of aptdaemon
Changes:
 aptdaemon (1.1.1-4+deb8u1) stable-proposed-updates; urgency=medium
 .
   * Non maintainer upload
   * Add CVE-2015-1323.patch to address CVE-2015-1323 - taken from
 1.1.1-1ubuntu5.2 (Closes: #789162)
Checksums-Sha1: 
 814a3bc18969c5b67caeb0a4ded4a8a56fc12928 3077 aptdaemon_1.1.1-4+deb8u1.dsc
 978126e9b3fb799b89fca37d1b6fc8a605ff6e7a 27512 
aptdaemon_1.1.1-4+deb8u1.debian.tar.xz
 f379d43522587a5a31e87a0ef67b8a5a557b2c56 362346 
aptdaemon_1.1.1-4+deb8u1_all.deb
 106375d8e0d1080f195bcb3d40919bf61887830a 137440 
python3-aptdaemon_1.1.1-4+deb8u1_all.deb
 e087a5ed3a9f6a7f4b36d51cc1675c41a0342343 136818 
python-aptdaemon_1.1.1-4+deb8u1_all.deb
 53e89791b51721a3f418d9a3a3147a05a49f0a7e 157500 
python3-aptdaemon.test_1.1.1-4+deb8u1_all.deb
 eb74132fd0fbabdb7c607cc29a9e7ea81ed15966 251038 
aptdaemon-data_1.1.1-4+deb8u1_all.deb
 b2169cf39aed1e53ae0967f1140e3e225578ea79 73930 
python-aptdaemon-gtk_1.1.1-4+deb8u1_all.deb
 5321609c45479228dbecf6ae390077980bec3cbf 104652 
python3-aptdaemon.pkcompat_1.1.1-4+deb8u1_all.deb
 02a0036c4f634509900376b51bba9a5e7aac058d 84814 
python-aptdaemon.gtkwidgets_1.1.1-4+deb8u1_all.deb
 0cad2a2130307e27ee5d0556ae225e69a154d279 86022 
python3-aptdaemon.gtk3widgets_1.1.1-4+deb8u1_all.deb
 904944a87d1c8019a229ce7ee511e5b73a75f89f 85922 
python-aptdaemon.gtk3widgets_1.1.1-4+deb8u1_all.deb
Checksums-Sha256: 
 

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

[Emilio Pozuelo Monfort]

[Adding debian-wb-team back to Cc]

On 13/03/16 17:56, Drew Parsons wrote:

On Sun, 2016-03-13 at 17:35 +0100, Emilio Pozuelo Monfort wrote:

On 13/03/16 16:34, Drew Parsons wrote:


Source: petsc
Followup-For: Bug #816101

The petsc build failure on mipsel appears to be a transient problem
on
the build machine. Please try the mipsel build again.

Why? It has failed twice already.


What would make mipsel different to other architectures or from the
earlier successful mipsel build?  It's the same petsc.


petsc may be at the same version, but the environment has changed. It may be a 
bug in another package (e.g. an rdep) or a bug in petsc that was latent until now.



Have you checked if it builds fine on a porterbox?


I tried but sbuild wouldn't work inside the schroot environment on
etler.


Did you read the MOTD? See https://dsa.debian.org/doc/schroot/

Anyway given the build queue is currently empty on mipsel, I've given it back. 
Let's see if the problem is fixed now...


Emilio

Bug#817153: [reportbug-ng]

[Alex Goebel]

Package: reportbug-ng
Version: 1.31
Control: severity -1 important
Control: tags -1 unreproducible moreinfo

Works here, with icedove.


--- System information. ---
Architecture: amd64
Kernel: Linux 4.4.0-1-rt-amd64

Debian Release: stretch/sid
500 unstable ftp.debian.org
500 testing ftp.debian.org
10 unstable www.deb-multimedia.org
1 experimental ftp.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.

Processed: [reportbug-ng]

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #817153 [reportbug-ng] MUA is opened with empty email
Severity set to 'important' from 'grave'
> tags -1 unreproducible moreinfo
Bug #817153 [reportbug-ng] MUA is opened with empty email
Added tag(s) moreinfo and unreproducible.

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

Bug#807281: marked as done (crashes rendering SVGs with filters)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 18:30:38 +0100
with message-id <56e5a3be.2010...@debian.org>
and subject line Re: crashes a lot
has caused the Debian Bug report #807281,
regarding crashes rendering SVGs with filters
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.)


-- 
807281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librsvg2-2
Version: 2.40.12-1
Severity: grave

The update from .11 to .12 causes a lot of crashes here.
I noticed it due to dash-to-dock preferences no longer working [1]
This is apparently caused by librsvg. The attached .svg can be used to
make nautilus crash if the folder containing the file is opened.

Marking as RC so this buggy version doesn't migrate to testing

[1] https://github.com/micheleg/dash-to-dock/issues/262


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

Kernel: Linux 4.3.0-trunk-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 librsvg2-2 depends on:
ii  libc62.21-3
ii  libcairo21.14.4-1
ii  libcroco30.6.9-1
ii  libgdk-pixbuf2.0-0   2.32.2-1
ii  libglib2.0-0 2.46.2-1
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libxml2  2.9.2+zdfsg1-4

Versions of packages librsvg2-2 recommends:
ii  librsvg2-common  2.40.11-2

Versions of packages librsvg2-2 suggests:
ii  librsvg2-bin  2.40.11-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.40.13-2

On Mon, 07 Dec 2015 02:27:19 +0100 Michael Biebl  wrote:
> Package: librsvg2-2
> Version: 2.40.12-1
> Severity: grave
> 
> The update from .11 to .12 causes a lot of crashes here.
> I noticed it due to dash-to-dock preferences no longer working [1]
> This is apparently caused by librsvg. The attached .svg can be used to
> make nautilus crash if the folder containing the file is opened.
> 
> Marking as RC so this buggy version doesn't migrate to testing

This was fixed in 2.40.13-2 by cherry-picking
d937c691678803ceda6be701587d997ccd03a1da from upstream git.
The next upstream release 2.40.14 will also include this fix.

Marking the bug as done.


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



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

Bug#742347: [Pkg-javascript-devel] Bug#742347: Bug#742347: overview of the tilemill situation and alternatives (mapbox, kosmtik)

[Sebastiaan Couwenberg]

On 13-03-16 18:18, Jérémy Lal wrote:
> 2016-03-13 16:40 GMT+01:00 Antoine Beaupré :
> 
>>
>>  9. Oh, and finally one could mention another Mapbox project,
>> [Carto][], a commandline CSS tools that implements some sort of
>> standard CSS language that all those tools end up using to talk to
>> Mapnik, more or less. There are no RFPs for that.
>>
>>  [Carto]: https://github.com/mapbox/carto
> 
> 
> carto is in debian - it needs to be updated, though (node-carto)

mapnik-reference needs to be packaged for the new carto version, and
semver may need to be upgraded:

 Dependencies:
 NPM   Debian
 carto (0.15.3)node-carto (0.9.5-2)
 ├─ mapnik-reference (~8.5.0)  None
 │  └─ semver (^5.1.0) node-semver (2.1.0-2)
 ├─ optimist (~0.6.0)  node-optimist (0.6.1-1)
 └─ underscore (~1.6.0)underscore (1.7.0~dfsg-1)

 Build dependencies:
 NPM   Debian
 coveralls (~2.10.1)   None
 istanbul (~0.2.14)None
 jshint (0.2.x)None
 mocha (1.12.x)node-mocha (1.20.1-1)
 sax (0.1.x)   sax.js (0.5.5-1)

Kind Regards,

Bas

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

Bug#814992: marked as done (cabal-debian: FTBFS - build-dep libghc-optparse-applicative-dev (<< 0.12) unsatisfiable as 0.12.0.0-1 is current)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 17:19:32 +
with message-id 
and subject line Bug#814992: fixed in cabal-debian 4.31.9-1
has caused the Debian Bug report #814992,
regarding cabal-debian: FTBFS - build-dep libghc-optparse-applicative-dev (<< 
0.12) unsatisfiable as 0.12.0.0-1 is current
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.)


-- 
814992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cabal-debian
Version: 4.31-4
Severity: serious
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.

[...]
 -> Considering build-dep libghc-optparse-applicative-dev (>= 0.11)
   -> Trying libghc-optparse-applicative-dev
 -> Considering build-dep libghc-optparse-applicative-dev (<< 0.12)
  Tried versions: 0.12.0.0-1
   -> Does not satisfy version, not trying
E: Could not satisfy build-dependency.


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


cabal-debian-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: cabal-debian
Source-Version: 4.31.9-1

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

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated cabal-debian package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Mar 2016 12:43:11 -0400
Source: cabal-debian
Binary: cabal-debian
Architecture: source
Version: 4.31.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description:
 cabal-debian - Create a debianization for a cabal package
Closes: 814992
Changes:
 cabal-debian (4.31.9-1) unstable; urgency=medium
 .
   * New upstream release.
 - No longer conflicts with newer optparse-applicative.  closes: #814992.
Checksums-Sha1:
 36c533d3414364d8332160c2cfff1275eb01b4b3 2803 cabal-debian_4.31.9-1.dsc
 6046987a966bf4d694f787decf09914dc78f437d 132668 cabal-debian_4.31.9.orig.tar.gz
 c952f1fb4ee21f02123c4a5704801948f2968093 4044 
cabal-debian_4.31.9-1.debian.tar.xz
Checksums-Sha256:
 4cf207f1d6b94412d27e6c86d1a027d8193c0e97c6a6835777abb8caad9a20e8 2803 
cabal-debian_4.31.9-1.dsc
 e046eb64364023dc0e8c786c06b76e47f845c7be212403937d790ab1716f88e9 132668 
cabal-debian_4.31.9.orig.tar.gz
 99d99f9802d70e7b687969066edeeca54f032a2dd030ff195da1411734f633cf 4044 
cabal-debian_4.31.9-1.debian.tar.xz
Files:
 e35bee3e7b107b9ef1fb0633feb50f78 2803 haskell extra cabal-debian_4.31.9-1.dsc
 792984162526ae0150a01ce20bddb151 132668 haskell extra 
cabal-debian_4.31.9.orig.tar.gz
 adb36e74446d7494155e69bc4bb110e3 4044 haskell extra 
cabal-debian_4.31.9-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Debian!

iQJ8BAEBCgBmBQJW5Z0qXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NTgxRUM4NzQwNTNFNkM4MDc3OTFCOUI1
NTkyMzMxRTE5OUQzOEE4AAoJEFWSMx4ZnTioMFQP/3Vl9Fe3DJCTlQ6v6J8qNObJ
I7x+slwWEHG3ofcvRjLskpevPTeyH3e+Zym4f7F+1LbuhE58wQ+mNb+4H6iRhWsm
YvSv76PUew6Wj6RcExRZwzXHAOwvvDPX8jPdIOiqq2AbX1bdsBNcLPsAKQqWRqUj
bQd0aVVjW3PtHpItozD9682rARr0kGOmeNcnX31wpgRv4LCdNvbE/NbuTdN9oGLM
n5sNQWWWoBSfWAiMit1X5gzKLSGF+8F257qhIr1p3L5XeC5EMzHdEWyCa9vc3TWV
JrXWs2NqvXzoRHHI2w6XJoOrB1dnITFYKn99JXNJFMa1gVmSqTtkbge/3AM31VxV
Hcq9Kra2dgTyCEUwJbuVm7sjtuNG7D7ZV8dZ+3mVDo8egWd10pmkZbU5BIZnUZj7
XA7vYxt5xUIL3rQE0k0dVNypUoy8c6knHWxmbCYe0ggrQJE8YMR5U3S7vglavU3L
Ctg6b0OrzM2HvZMScvBafNDJ+wID2Tzw9pFXUm38HvSegajabFt5kdgG/fG6JprC
kAZ835mvI/2WMyfXJck9z55BTQfJ393+GsHMH2JIMo2Eh3b4nKfdjVzh3+sUjqfi
Cs1JxEzucSc9nhzSaaTT80dJk4OZCSVkrIusEwXZFebo5zJwvdZKxvb5amT1kzmY
fyZpZz8bacMmgXxIYyyt
=N41w
-END PGP SIGNATURE End Message ---

Bug#818040: marked as done (cmake: FTBFS in stretch. Test #368 fails)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 17:19:49 +
with message-id <e1af9gd-0007yh...@franck.debian.org>
and subject line Bug#818040: fixed in cmake 3.5.0-1
has caused the Debian Bug report #818040,
regarding cmake: FTBFS in stretch. Test #368 fails
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.)


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

Dear maintainer:

cmake currently fails to build from source in stretch.
There is a test which fails:

Start 368: RunCMake.CommandLine
368/415 Test #368: RunCMake.CommandLine 
...***Failed0.88 sec

The full build log is attached.

Thanks.

cmake_3.4.1-2_amd64-20160313-0052.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cmake
Source-Version: 3.5.0-1

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

Debian distribution maintenance software
pp.
Felix Geyer <fge...@debian.org> (supplier of updated cmake package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Mar 2016 15:16:37 +0100
Source: cmake
Binary: cmake cmake-data cmake-curses-gui cmake-qt-gui cmake-doc
Architecture: source
Version: 3.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian CMake Team <pkg-cmake-t...@lists.alioth.debian.org>
Changed-By: Felix Geyer <fge...@debian.org>
Description:
 cmake  - cross-platform, open-source make system
 cmake-curses-gui - curses based user interface for CMake (ccmake)
 cmake-data - CMake data files (modules, templates and documentation)
 cmake-doc  - extended documentation in various formats for CMake
 cmake-qt-gui - Qt4 based user interface for CMake (cmake-gui)
Closes: 809535 818040
Changes:
 cmake (3.5.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes fltk_wrap_ui segmentation fault. (Closes: #809535)
   * Pass correct buildsystem to dh_auto_test, fixes FTBFS. (Closes: #818040)
   * Change Vcs-* and Homepage to https URLs.
   * Migrate to dbgsym debug package.
Checksums-Sha1:
 c5b4db80d2eb1f3d7bec182c59f27c8d4e3314da 2431 cmake_3.5.0-1.dsc
 4a10116e061bbe806ffdd5164aca7780b0e98f4e 6861686 cmake_3.5.0.orig.tar.gz
 cd0d37a3546b362415609c5915738de1f840cbd1 26792 cmake_3.5.0-1.debian.tar.xz
Checksums-Sha256:
 28be61b050457e3903c9bef1accf897af9e4f6a271febd143aedcd156b1aa2e8 2431 
cmake_3.5.0-1.dsc
 92c83ad8a4fd6224cf6319a60b399854f55b38ebe9d297c942408b792b1a9efa 6861686 
cmake_3.5.0.orig.tar.gz
 56a93e273a465b9f996c2f4f805cbbf6eac7e9d574c57a27cefc749cd60580d0 26792 
cmake_3.5.0-1.debian.tar.xz
Files:
 cf4752324eeaaf42a7ffb184709c25b7 2431 devel optional cmake_3.5.0-1.dsc
 33c5d09d4c33d4ffcc63578a6ba8777e 6861686 devel optional cmake_3.5.0.orig.tar.gz
 4ed9fd6e0a34bd5a473263a8a903e1d8 26792 devel optional 
cmake_3.5.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJW5ZqZAAoJEP4ixv2DE11FCuYP/j6wfcUtkiV5XA184O70BvTa
CRMhE/rKag9MAHTvXvV2Dh3pXPjwlaVJ559W2k43PQhD1W++RKKRdifiofgGaiTA
YdYN0AqZjKoLnu+cYIRElCoIrjH2EKAPnlOqog6W8dRqcvTRSb3MEjKqSv9tEJ+G
rYQDh7Sso6pzKOZC7VTtEcXMQ2EoecJpDoE3gra0uMdR0lrRrLINokkobyQHTqj4
E4wxrqh7vyeRcdCK3GinJXqy0vco4d6oNBbKzdg8lEGkBi3tvngS4AQXSw62xCBm
yUzE4HNemvQm1RTteKJ6VkylamrS6QOJFI/65VjSdPexpeiuK6+AJqupRZtCpLs8
GmOIFD8WToGe5tJ8ee8Etu8I++ng7bW+GVGfvuhznRcn6pot3liMSRTojpBLhq+L
jmpsn1kGPfRh+7EWhHgLpkob378NkYZTQbalSTJpDdPeXFQJIWbhZjytPz0XmrsR
qFXmQuZ6qFIvdypAWxVyKovefroYPXvUsj9o6PEWVx1Z16AbcRiQi4wZ7bHGTZna
eC73HNpBQNw+iMGRoeNV2Liopw7XG/BEzSglRtpHyYVDHAOZ5xrur+GcUETEVDJl
+2wbWXFYNyy6cq+Jo02oEwfH/ViwrghmNGYjSQ47ps8k4KGqGZ8487i7eG/DD0uD
cGFrL+vf9QGoT1M3a/kw
=vv2R
-END PGP SIGNATURE End Message ---

Bug#742347: [Pkg-javascript-devel] Bug#742347: overview of the tilemill situation and alternatives (mapbox, kosmtik)

[Jérémy Lal]

2016-03-13 16:40 GMT+01:00 Antoine Beaupré :

>
>  9. Oh, and finally one could mention another Mapbox project,
> [Carto][], a commandline CSS tools that implements some sort of
> standard CSS language that all those tools end up using to talk to
> Mapnik, more or less. There are no RFPs for that.
>
>  [Carto]: https://github.com/mapbox/carto


carto is in debian - it needs to be updated, though (node-carto)

Jérémy

Bug#818069: Failed InfluxDB build

[Mark Rushakoff]

Santiago,

Your build failed at line 8221 due to a failed test (presumably a flaky
test on InfluxDB's side).

You were attempting to build 0.10.0, but the most recent version in the
0.10 series is 0.10.3, which contains many fixes to bugs present in 0.10.0.
I don't know for sure if that particular test has stabilized in 0.10.3, but
I would strongly recommend building 0.10.3 instead of 0.10.0.

Mark

Processed: affects 817139

[Debian Bug Tracking System]

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

> affects 817139 + sassc
Bug #817139 [pysassc] sassc: trying to overwrite 
'/usr/share/man/man1/sassc.1.gz', which is also in package pysassc 0.9.3-1
Added indication that 817139 affects sassc
> thanks
Stopping processing here.

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

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

[Drew Parsons]

On Sun, 2016-03-13 at 17:35 +0100, Emilio Pozuelo Monfort wrote:
> On 13/03/16 16:34, Drew Parsons wrote:
> > 
> > Source: petsc
> > Followup-For: Bug #816101
> > 
> > The petsc build failure on mipsel appears to be a transient problem
> > on
> > the build machine. Please try the mipsel build again.
> Why? It has failed twice already. 

What would make mipsel different to other architectures or from the
earlier successful mipsel build?  It's the same petsc.


> Have you checked if it builds fine on a porterbox?
> 


I tried but sbuild wouldn't work inside the schroot environment on
etler.

Processed: severity of 815608 is serious, tagging 815608

[Debian Bug Tracking System]

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

> severity 815608 serious
Bug #815608 [src:plum] plum: Removal dh_undocumented debhelper command
Severity set to 'serious' from 'important'
> tags 815608 + sid stretch
Bug #815608 [src:plum] plum: Removal dh_undocumented debhelper command
Ignoring request to alter tags of bug #815608 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: severity of 815605 is serious, tagging 815605

[Debian Bug Tracking System]

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

> severity 815605 serious
Bug #815605 [src:kon2] kon2: Removal dh_undocumented debhelper command
Severity set to 'serious' from 'important'
> tags 815605 + sid stretch
Bug #815605 [src:kon2] kon2: Removal dh_undocumented debhelper command
Ignoring request to alter tags of bug #815605 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: severity of 815611 is serious, tagging 815611

[Debian Bug Tracking System]

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

> severity 815611 serious
Bug #815611 [src:tsocks] tsocks: Removal dh_undocumented debhelper command
Severity set to 'serious' from 'important'
> tags 815611 + sid stretch
Bug #815611 [src:tsocks] tsocks: Removal dh_undocumented debhelper command
Ignoring request to alter tags of bug #815611 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: severity of 815603 is serious, tagging 815603

[Debian Bug Tracking System]

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

> severity 815603 serious
Bug #815603 [src:funny-manpages] funny-manpages: Removal dh_undocumented 
debhelper command
Severity set to 'serious' from 'important'
> tags 815603 + sid stretch
Bug #815603 [src:funny-manpages] funny-manpages: Removal dh_undocumented 
debhelper command
Ignoring request to alter tags of bug #815603 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: severity of 815610 is serious, tagging 815610

[Debian Bug Tracking System]

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

> severity 815610 serious
Bug #815610 [src:search-citeseer] search-citeseer: Removal dh_undocumented 
debhelper command
Severity set to 'serious' from 'important'
> tags 815610 + sid stretch
Bug #815610 [src:search-citeseer] search-citeseer: Removal dh_undocumented 
debhelper command
Ignoring request to alter tags of bug #815610 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: severity of 815609 is serious, tagging 815609

[Debian Bug Tracking System]

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

> severity 815609 serious
Bug #815609 [src:search-ccsb] search-ccsb: Removal dh_undocumented debhelper 
command
Severity set to 'serious' from 'important'
> tags 815609 + sid stretch
Bug #815609 [src:search-ccsb] search-ccsb: Removal dh_undocumented debhelper 
command
Ignoring request to alter tags of bug #815609 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: severity of 815604 is serious, tagging 815604

[Debian Bug Tracking System]

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

> severity 815604 serious
Bug #815604 [src:icebreaker] icebreaker: Removal dh_undocumented debhelper 
command
Severity set to 'serious' from 'important'
> tags 815604 + sid stretch
Bug #815604 [src:icebreaker] icebreaker: Removal dh_undocumented debhelper 
command
Ignoring request to alter tags of bug #815604 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: severity of 815607 is serious, tagging 815607

[Debian Bug Tracking System]

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

> severity 815607 serious
Bug #815607 [src:namazu2] namazu2: Removal dh_undocumented debhelper command
Severity set to 'serious' from 'important'
> tags 815607 + sid stretch
Bug #815607 [src:namazu2] namazu2: Removal dh_undocumented debhelper command
Ignoring request to alter tags of bug #815607 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: severity of 815606 is serious, tagging 815606

[Debian Bug Tracking System]

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

> severity 815606 serious
Bug #815606 [src:mova] mova: Removal dh_undocumented debhelper command
Severity set to 'serious' from 'important'
> tags 815606 + sid stretch
Bug #815606 [src:mova] mova: Removal dh_undocumented debhelper command
Ignoring request to alter tags of bug #815606 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

[Emilio Pozuelo Monfort]

On 13/03/16 16:34, Drew Parsons wrote:

Source: petsc
Followup-For: Bug #816101

The petsc build failure on mipsel appears to be a transient problem on
the build machine. Please try the mipsel build again.


Why? It has failed twice already. Have you checked if it builds fine on a 
porterbox?

Emilio

Bug#817124: marked as done (librarian-puppet requires 'rsync' gem but it doesn't exist)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 16:22:19 +
with message-id 
and subject line Bug#817124: fixed in librarian-puppet 2.2.1-2
has caused the Debian Bug report #817124,
regarding librarian-puppet requires 'rsync' gem but it doesn't exist
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.)


-- 
817124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librarian-puppet
Version: 2.2.1-1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi!

After the latest update of librarian-puppet, just running it triggers this 
error:

/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot 
load such file -- rsync (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/librarian/puppet/util.rb:1:in `'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in 
`require'
from /usr/lib/ruby/vendor_ruby/librarian/puppet/source/local.rb:1:in 
`'
[...]

There doesn't seem to be any gem available for this in Debian.

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

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 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 librarian-puppet depends on:
ii  puppet-common   3.8.5-1
ii  ruby1:2.3.0+1
ii  ruby-json   1.8.3-1+b2
ii  ruby-librarian  0.1.2-1
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  ruby2.2 [ruby-interpreter]  2.2.4-1
ii  ruby2.3 [ruby-interpreter]  2.3.0-4

librarian-puppet recommends no packages.

librarian-puppet suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW3p1xAAoJEJWkL+g1NSX5QIAP/iv78RKifK7DP0JHcBSG30T3
9w+bKTVz/KiacomnJ8Grgf/QQQ0CNpfviDZX+/EjkZxzLjhfDEK3kAwFwDYoZP4Z
EX5VhqcmqDmAQJrRYCey5FEI9PNiGxNXZQcz2yiO9r/QqQr2HDJg5ZcYylnEIA0x
mxvjQ77KW6FbuSmKQmhY1PSyGwVAr4gHfuuh/icjFf3u6LzDWWvAi/2uHhu/XpTu
ZIStil5U2oaWIOO0+9PCkNh7Qn4Rjfxg4hEYxLmQsVGmq9rPiQbgpgM/N5Dz9eks
xIc7RoaHhWZxIgT+JE0tzCa9oEZi+ag8ZU2y3JKM1wj+A7q7BXLOgYiRiKXdPqE0
PDFQKISWfNd4NDKYahJI4YpgidOmURMKsOEolIcgZ0vB3mCv3f2rEGqfSdb5O8Kf
aNP5Kmpgjwfynd8RtEzPxFPutqey9DIiQTLou/aGcEvx2HbMov8UdU5RQEh1kp6r
nevRskZMb7n1JSBtBKhjPqzHT7xg1YLGJHanURO3glbAn3McZbk+5kPvWh85pQ1p
ZkjjuAbgRua11qdpumzsdA3h9f/f8px3yMCja36LH6LWnHwBc6J6fP3czGyO/PaH
1F2Ek35w9dswiVPevTI6GQUgVqQ0Eekq2w8xPvRqtKJzuG5/L/goURlwEmKh2BJl
V9Bdic3wzEhB2U05vzpP
=r44l
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: librarian-puppet
Source-Version: 2.2.1-2

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

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated librarian-puppet 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: Fri, 11 Mar 2016 22:23:02 -0300
Source: librarian-puppet
Binary: librarian-puppet
Architecture: source
Version: 2.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Sebastien Badia 
Description:
 librarian-puppet - bundler for your puppet modules
Closes: 817124
Changes:
 librarian-puppet (2.2.1-2) unstable; urgency=medium
 .
   [ Michael Moll ]
   * Add patch to unbreak with ruby-puppet-forge 2.x
 .
   [ Sebastien Badia ]
   * Add missing dependencys (Closes: #817124)
   * d/patches: Refresh puppet_forge_2.1 and add missing DEP headers
 .
   [ Christian Hofstaedtler ]
   * Add dependencies check to 

Bug#818037: vorbis-tools: vcut always(?) segfaults

[Petter Reinholdtsen]

[Frank Heckenbach]
> Sorry for the brief description, but for what I can tell, that's
> really it. I tried various cases, and vcut always seems to just
> segfault. Here's one example:
>
> % head -c 50 /dev/zero | oggenc -Q -r -o 1.ogg -
> % vcut 1.ogg 2.ogg 3.ogg +1
> Processing: Cutting at 1,00 seconds
> Segmentation fault

I see the same, and this is the output from valgrind:

% valgrind vcut 1.ogg 2.ogg 3.ogg +1
==27037== Memcheck, a memory error detector
==27037== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==27037== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==27037== Command: vcut 1.ogg 2.ogg 3.ogg +1
==27037== 
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.22.so:
--27037-- Ignoring non-Dwarf2/3/4 block in .debug_info
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.22.so:
--27037-- Last block truncated in .debug_info; ignoring
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.22.so:
--27037-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--27037-- Ignoring non-Dwarf2/3/4 block in .debug_info
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--27037-- Ignoring non-Dwarf2/3/4 block in .debug_info
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--27037-- Ignoring non-Dwarf2/3/4 block in .debug_info
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--27037-- Last block truncated in .debug_info; ignoring
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--27037-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libm-2.22.so:
--27037-- Ignoring non-Dwarf2/3/4 block in .debug_info
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libm-2.22.so:
--27037-- Last block truncated in .debug_info; ignoring
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libm-2.22.so:
--27037-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
Processing: Cutting at 1.00 seconds
==27037== Invalid read of size 1
==27037==at 0x4C2E7E6: memcpy@@GLIBC_2.14 (vg_replace_strmem.c:1018)
==27037==by 0x5064202: ogg_stream_iovecin (in 
/usr/lib/x86_64-linux-gnu/libogg.so.0.8.2)
==27037==by 0x506435B: ogg_stream_packetin (in 
/usr/lib/x86_64-linux-gnu/libogg.so.0.8.2)
==27037==by 0x401A4D: ??? (in /usr/bin/vcut)
==27037==by 0x401BDB: ??? (in /usr/bin/vcut)
==27037==by 0x402029: ??? (in /usr/bin/vcut)
==27037==by 0x4023BA: ??? (in /usr/bin/vcut)
==27037==by 0x4025C2: ??? (in /usr/bin/vcut)
==27037==by 0x4014F7: ??? (in /usr/bin/vcut)
==27037==by 0x528B60F: (below main) (in /lib/x86_64-linux-gnu/libc-2.22.so)
==27037==  Address 0xfff001000 is not stack'd, malloc'd or (recently) free'd
==27037== 
==27037== 
==27037== Process terminating with default action of signal 11 (SIGSEGV)
==27037==  Access not within mapped region at address 0xFFF001000
==27037==at 0x4C2E7E6: memcpy@@GLIBC_2.14 (vg_replace_strmem.c:1018)
==27037==by 0x5064202: ogg_stream_iovecin (in 
/usr/lib/x86_64-linux-gnu/libogg.so.0.8.2)
==27037==by 0x506435B: ogg_stream_packetin (in 
/usr/lib/x86_64-linux-gnu/libogg.so.0.8.2)
==27037==by 0x401A4D: ??? (in /usr/bin/vcut)
==27037==by 0x401BDB: ??? (in /usr/bin/vcut)
==27037==by 0x402029: ??? (in /usr/bin/vcut)
==27037==by 0x4023BA: ??? (in /usr/bin/vcut)
==27037==by 0x4025C2: ??? (in /usr/bin/vcut)
==27037==by 0x4014F7: ??? (in /usr/bin/vcut)
==27037==by 0x528B60F: (below main) (in /lib/x86_64-linux-gnu/libc-2.22.so)
==27037==  If you believe this happened as a result of a stack
==27037==  overflow in your program's main thread (unlikely but
==27037==  possible), you can try to increase the size of the
==27037==  main thread stack using the --main-stacksize= flag.
==27037==  The main thread stack size used in this run was 8388608.
==27037== 
==27037== HEAP SUMMARY:
==27037== in use at exit: 97,967,813 bytes in 116 blocks
==27037==   total heap usage: 121 allocs, 5 frees, 97,996,535 bytes allocated
==27037== 
==27037== LEAK SUMMARY:
==27037==definitely lost: 0 bytes in 0 blocks
==27037==indirectly lost: 0 bytes in 0 blocks
==27037==  

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

[Lucas Kanashiro]

Attached the patch that solves this issue, just updating the
libmysqlclient15-dev build dependency to libmysqlclient-dev.

-- 
Lucas Kanashiro
diff -Nru qsf-1.2.7/debian/changelog qsf-1.2.7-new/debian/changelog
--- qsf-1.2.7/debian/changelog	2016-03-13 12:55:34.009146646 -0300
+++ qsf-1.2.7-new/debian/changelog	2016-03-13 13:04:08.581087168 -0300
@@ -1,3 +1,9 @@
+qsf (1.2.7-1.1) UNRELEASED; urgency=medium
+
+  * Add build dependency on libmysqlclient-dev (Closes:  #790457)
+
+ -- Lucas Kanashiro   Sun, 13 Mar 2016 12:52:28 -0300
+
 qsf (1.2.7-1) unstable; urgency=low
 
   * New upstream version:
diff -Nru qsf-1.2.7/debian/control qsf-1.2.7-new/debian/control
--- qsf-1.2.7/debian/control	2016-03-13 12:55:34.009146646 -0300
+++ qsf-1.2.7-new/debian/control	2016-03-13 12:55:34.013146678 -0300
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Nelson A. de Oliveira 
 Uploaders: Bartosz Fenski 
-Build-Depends: cdbs, patchutils, debhelper (>= 5), libgdbm-dev, libmysqlclient15-dev, libsqlite0-dev, bsdmainutils, man-db
+Build-Depends: cdbs, patchutils, debhelper (>= 5), libgdbm-dev, libmysqlclient-dev, libsqlite0-dev, bsdmainutils, man-db
 Standards-Version: 3.7.2
 
 Package: qsf

Processed: Re: Bug#817795: sysvinit-utils - Contains pre-depends loop

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 util-linux
Bug #817795 [sysvinit-utils] sysvinit-utils - Contains pre-depends loop
Bug reassigned from package 'sysvinit-utils' to 'util-linux'.
No longer marked as found in versions sysvinit/2.88dsf-59.3.
Ignoring request to alter fixed versions of bug #817795 to the same values 
previously set
> forcemerge 817857 -1
Bug #817857 {Done: Andreas Henriksson } [util-linux] 
util-linux: Depends/Breaks loop with Essential packages prevents upgrade from 
Jessie
Bug #817795 [util-linux] sysvinit-utils - Contains pre-depends loop
Severity set to 'serious' from 'grave'
Marked Bug as done
Marked as fixed in versions util-linux/2.27.1-6.
Marked as found in versions util-linux/2.27.1-5.
Merged 817795 817857

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

Bug#817795: sysvinit-utils - Contains pre-depends loop

[Andreas Henriksson]

Control: reassign -1 util-linux
Control: forcemerge 817857 -1

On Thu, Mar 10, 2016 at 02:52:22PM +0100, Petter Reinholdtsen wrote:
> [Bastian Blank]
> > In sysvinit-utils or somewhere of it's dependency chain is a
> > pre-dependency/conflict loop, which apt is unable to break.  This breaks
> > the upgrade from Jessie.
> 
> Could this be caused by util-linux?

Yes!

(On a related note, would be nice if we could do the Breaks/Depends
sysvinit-utils / util-linux switcheroo soon to properly describe
the relations and avoid similar upgrade issues again. Synchronized
uploads of sysvinit and util-linux is needed for that. Hopefully
this is a good task for one of the people who've shown interest
in adopting sysvinit to get started with.)

Regards,
Andreas Henriksson

Bug#742347: overview of the tilemill situation and alternatives (mapbox, kosmtik)

[Antoine Beaupré]

so I am not sure this RFP is still relevant anymore. there hasn't been a
tilemill release since 2012. here's a summary of a discussion that
happened in #742347 (for some reason, I sent the discussion
there... sorry).

 1. Mapbox people have released a new product in september 2014 named
[Mapbox studio classic][]. the code is a
[still freely available][] and seems to be a
[fork of tilemill][]. mapbox classic still has releases on github,
last one is from november 2015

 [Mapbox studio classic]: https://www.mapbox.com/mapbox-studio-classic/#linux
 [still freely available]: https://github.com/mapbox/mapbox-studio-classic
 [fork of tilemill]: 
https://github.com/mapbox/mapbox-studio-classic/blob/mb-pages/docs/-01-01-common-questions.md#how-is-mapbox-studio-related-to-tilemill#user-content-how-is-mapbox-studio-classic-related-to-tilemill

 2. It looks like Mapbox studio classic has some sort of
[Mapbox.com lock-in][], and there are certainly new copyright
issues, if only with the [bundled fonts][]. but it could probably
be packaged.

 [Mapbox.com lock-in]: 
https://github.com/mapbox/mapbox-studio-classic/blob/mb-pages/docs/-01-01-common-questions.md#can-i-use-git-with-a-style-or-source-project
 [bundled fonts]: 
https://github.com/mapbox/mapbox-studio-classic/blob/mb-pages/docs/-01-01-common-questions.md#what-cancant-i-do-with-pro-fonts

 3. Then there's [mapbox studio][], which is a
[full rewrite of mapbox][]. You need to "signup" somehow to get
access, even though parts of the code are free, namely the
[Mapbox GL studio][] project

 [Mapbox GL studio]: https://github.com/mapbox/mapbox-gl-native/
 [full rewrite of mapbox]: https://www.mapbox.com/help/upgrading-from-classic/
 [mapbox studio]: https://www.mapbox.com/mapbox-studio/

 4. The [Openstreetmap-carto][] developpers have mostly switched to
[kosmtik][] instead of Mapbox.

 [Openstreetmap-carto]: https://github.com/gravitystorm/openstreetmap-carto
 [kosmtik]: https://github.com/kosmtik/kosmtik

 5. In short: Mapbox studio classic is not as good as Tilemill, Mapbox
studio is very promising, but you still need to signup for access,
and kosmtik seems to be working right now. 

 6. Ross has an [ITP for kosmtik][]. The package is waiting on other
node dependencies to be uploaded (yes, again).
 
 [ITP for kosmtik]: https://bugs.debian.org/805308

 7. There is also an [ITP for Mapbox-studio][] yet it is unclear to me
what that one means because the source code to Mapbox-studio
doesn't seem to be available, as far as i can tell (and the ITP
doesn't say either).

 [ITP for Mapbox-studio]: https://bugs.debian.org/#761914

 8. There's no WNPP bug for Mapbox studio *classic* that I can
found. there's still an [RFP for tilemill][], which should
probably be closed now because the project seems dead and plenty
of alternatives exist. I wonder if node some dependencies that
were packaged for Tilemill actually now need to be *removed* from
Debian, because they have become useless leaf packages... I am
leaving the Tilemill RFP open for someone to clean that up.

 [RFP for tilemill]: https://bugs.debian.org/644767

 9. Oh, and finally one could mention another Mapbox project,
[Carto][], a commandline CSS tools that implements some sort of
standard CSS language that all those tools end up using to talk to
Mapnik, more or less. There are no RFPs for that.

 [Carto]: https://github.com/mapbox/carto

Phew! Sorry for the cross-posting among multiple bug reports, but
those tools all seem related in some way, and I kept on *not* finding
Mapbox while looking in the Tilemill RFP (and forgetting about
kosmtik).

With this point, I think all those tools are at least cross-referenced
and contributors can figure out where they want to put their energies
next.

A.

-- 
C'est avec les pierres de la loi qu'on a bâti les prisons,
et avec les briques de la religion, les bordels.
- Blake, William

Bug#730807: marked as done (Please make SP use PackageKit for Apt-write actions)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 15:37:24 +
with message-id 
and subject line Bug#730807: fixed in software-properties 0.96.9debian1+nmu1
has caused the Debian Bug report #730807,
regarding Please make SP use PackageKit for Apt-write actions
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.)


-- 
730807: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: software-properties
Version: 0.92.25debian1
Severity: wishlist
Tags: patch

Hi!
In order to replace gpk-prefs with software-properties-gtk in Debian,
and to make GPK replace the update-manager, as described in bug
#707706, it would be great to have SP use PackageKit.
PK does provide everything required for the functions SP needs, and it
can replace both QApt and Aptd, so we have a single backend to request
write-actions on Apt.
Having multiple package-manager daemons running in the background is a
bad thing and should be avoided.
So, here's an initial patch to make SP use PK, as discussed a long
time ago in IRC. Sorry for the locale- and whitespace cruft :-/
I couldn't test the driver-installation stuff, but that seems to be
disabled on Debian anyway and should not be an issue. Everything else
works (although the UI could need improvements and maybe a cancel
button ^^)
Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/


sp_0.92.25debian1-to-0.92.25debian2_+pk.debdiff
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: software-properties
Source-Version: 0.96.9debian1+nmu1

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated software-properties 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Sat, 12 Mar 2016 22:18:24 +0100
Source: software-properties
Binary: python3-software-properties software-properties-common 
software-properties-gtk software-properties-kde
Architecture: source all
Version: 0.96.9debian1+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Julian Andres Klode 
Changed-By: Matthias Klumpp 
Description:
 python3-software-properties - manage the repositories that you install 
software from
 software-properties-common - manage the repositories that you install software 
from (common)
 software-properties-gtk - manage the repositories that you install software 
from (gtk)
 software-properties-kde - manage the repositories that you install software 
from (qt)
Closes: 726723 730807
Changes:
 software-properties (0.96.9debian1+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload, with permission of juliank
   * Implement support for PackageKit (Closes: #730807)
   * Fix a few small quirks in debian/copyright
   * Wrap-and-sort debian/control
   * software-properties-drivers.desktop: Fix typo
 (NotShownIn -> NotShowIn)
   * Build with --parallel (Closes: #726723)
   * Autotests: Depend on xauth (should fix CI failure)
   * Add Vcs-* entries for the new Git repository
   * Stop building the Python2 module
Checksums-Sha1:
 e4981e1c67a4d4d20d3c95504f9652a447392900 2025 
software-properties_0.96.9debian1+nmu1.dsc
 97e58750041dc520df840f5bba618a085e8892a8 403612 
software-properties_0.96.9debian1+nmu1.tar.xz
 75650c62babbb66cc6118b0fcf3d5efc4190f64e 47364 
python3-software-properties_0.96.9debian1+nmu1_all.deb
 3ab683a554357195cae682213d94a495d4f60220 81466 
software-properties-common_0.96.9debian1+nmu1_all.deb
 bd10ed105fa625c05d673924316167e1dcc3 77270 
software-properties-gtk_0.96.9debian1+nmu1_all.deb
 3e922fbf0e3612c95943ebe0d1b0076a1affe473 50310 
software-properties-kde_0.96.9debian1+nmu1_all.deb
Checksums-Sha256:
 3b14aa6fc1ceda2ced4772cd0a7c5dbe4b02eac465c7114382322958f36736ac 2025 
software-properties_0.96.9debian1+nmu1.dsc
 80651edaf8ec048dbef0df1dd4f423c16be5256af93252212f8284d914eecdeb 403612 
software-properties_0.96.9debian1+nmu1.tar.xz
 

Bug#759918: marked as done (ruby-activerecord-nulldb-adapter: FTBFS: ERROR: Test "ruby2.1" failed: Failure/Error: cxn.select_values(""))

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 15:37:15 +
with message-id 
and subject line Bug#759918: fixed in ruby-activerecord-nulldb-adapter 0.3.2-1
has caused the Debian Bug report #759918,
regarding ruby-activerecord-nulldb-adapter: FTBFS: ERROR: Test "ruby2.1" 
failed:  Failure/Error: cxn.select_values("")
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.)


-- 
759918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759918
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-activerecord-nulldb-adapter
Version: 0.3.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: cxn.select_values("")
>  ArgumentError:
>wrong number of arguments (3 for 1..2)
>  # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:161:in 
> `select_rows'
>  # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:208:in 
> `block in select_values'
>  # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:239:in 
> `block in with_entry_point'
>  # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:254:in 
> `with_thread_local_variable'
>  # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:238:in 
> `with_entry_point'
>  # ./lib/active_record/connection_adapters/nulldb_adapter/core.rb:207:in 
> `select_values'
>  # ./spec/nulldb_spec.rb:234:in `block (2 levels) in '
> 
> Finished in 0.03349 seconds
> 33 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/nulldb_spec.rb:110 # NullDB should remember columns defined in 
> migrations
> rspec ./spec/nulldb_spec.rb:204 # NullDB should tag logged statements with 
> their entry point
> /usr/bin/ruby2.1 -S rspec ./spec/nulldb_spec.rb failed
> ERROR: Test "ruby2.1" failed: 

The full build log is available from:
   
http://aws-logs.debian.net/ftbfs-logs/2014/08/30/ruby-activerecord-nulldb-adapter_0.3.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.
--- End Message ---
--- Begin Message ---
Source: ruby-activerecord-nulldb-adapter
Source-Version: 0.3.2-1

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

Debian distribution maintenance software
pp.
Lucas Albuquerque Medeiros de Moura  (supplier of 
updated ruby-activerecord-nulldb-adapter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 05 Mar 2016 18:21:21 -0300
Source: ruby-activerecord-nulldb-adapter
Binary: ruby-activerecord-nulldb-adapter
Architecture: source
Version: 0.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Lucas Albuquerque Medeiros de Moura 
Description:
 ruby-activerecord-nulldb-adapter - ActiveRecord database adapters based on the 
Null Object pattern
Closes: 759918
Changes:
 ruby-activerecord-nulldb-adapter (0.3.2-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Sebastien Badia ]
   * Fix FTBFS bug with a upstream patch (Closes: #759918)
   * d/control:
 - Bump Standards-Version (no changes)
 - Wrap and sort, switch to cgit and HTTPS for homepage/vcs-browser
 .
   [ Lucas Albuquerque Medeiros de Moura ]
   * New upstream release.
   * Removing patches already applied 

Bug#814621: marked as done (diaspora-common: modifies conffiles (policy 10.7.3): /etc/diaspora.conf)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 15:34:48 +
with message-id 
and subject line Bug#814621: fixed in diaspora-installer 0.5.7.1+debian1
has caused the Debian Bug report #814621,
regarding diaspora-common: modifies conffiles (policy 10.7.3): 
/etc/diaspora.conf
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.)


-- 
814621: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diaspora-common
Version: 0.5.6.3+debian1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

  /etc/diaspora.conf


cheers,

Andreas


diaspora-common_0.5.6.3+debian1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: diaspora-installer
Source-Version: 0.5.7.1+debian1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated diaspora-installer 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Mar 2016 13:52:53 +0530
Source: diaspora-installer
Binary: diaspora-installer diaspora-common
Architecture: source
Version: 0.5.7.1+debian1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 diaspora-common - distributed social networking service - common files
 diaspora-installer - distributed social networking service - installer
Closes: 814621 818054
Changes:
 diaspora-installer (0.5.7.1+debian1) unstable; urgency=medium
 .
   [ Pirate Praveen ]
   * Install 0.5.7.1 version
   * Work around sigar bug (Closes: #818054)
 .
   [ Cédric Boutillier ]
   * Run wrap-and-sort on packaging files
   * Bump Standards-Version to 3.9.7 (no changes needed)
   * Use https:// in Vcs-* fields
   * Remove version in the gem2deb build-dependency
 .
   [ Balasankar C ]
   * Use ucf for handling conf files (Closes: #814621)
Checksums-Sha1:
 d75cbe875ecc95beb44dec1eb5c5dd5fad00a45b 1890 
diaspora-installer_0.5.7.1+debian1.dsc
 579dfd1b6563904f54f0038bcfb14a1bea499e88 28416 
diaspora-installer_0.5.7.1+debian1.tar.xz
Checksums-Sha256:
 4974e0b3e2d959229b0f218a0e8cae9c5730f44fac56b53eb24f2a125c4684ab 1890 
diaspora-installer_0.5.7.1+debian1.dsc
 df277f3b55410ea6cad8b40d107106cb76c13c0fb860a7883fdd42489fa02ffd 28416 
diaspora-installer_0.5.7.1+debian1.tar.xz
Files:
 fe2f9ff255e52b23910309d13ad7d1ec 1890 

Bug#818054: marked as done (diaspora fails to start with ruby2.3: symbol lookup error:...sigar.so: undefined symbol: sigar_skip_token)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 15:34:48 +
with message-id 
and subject line Bug#818054: fixed in diaspora-installer 0.5.7.1+debian1
has caused the Debian Bug report #818054,
regarding diaspora fails to start with ruby2.3: symbol lookup 
error:...sigar.so: undefined symbol: sigar_skip_token
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.)


-- 
818054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818054
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: diaspora-installer
version: 0.5.6.3+debian1
severity: grave
justification: makes package unusable

# sudo -H -E -u diaspora ./script/server start
Starting Diaspora in production mode with 1 Sidekiq worker(s).

ruby2.3: symbol lookup error:
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sigar-0.7.3/lib/sigar.so:
undefined symbol: sigar_skip_token



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: diaspora-installer
Source-Version: 0.5.7.1+debian1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated diaspora-installer 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Mar 2016 13:52:53 +0530
Source: diaspora-installer
Binary: diaspora-installer diaspora-common
Architecture: source
Version: 0.5.7.1+debian1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 diaspora-common - distributed social networking service - common files
 diaspora-installer - distributed social networking service - installer
Closes: 814621 818054
Changes:
 diaspora-installer (0.5.7.1+debian1) unstable; urgency=medium
 .
   [ Pirate Praveen ]
   * Install 0.5.7.1 version
   * Work around sigar bug (Closes: #818054)
 .
   [ Cédric Boutillier ]
   * Run wrap-and-sort on packaging files
   * Bump Standards-Version to 3.9.7 (no changes needed)
   * Use https:// in Vcs-* fields
   * Remove version in the gem2deb build-dependency
 .
   [ Balasankar C ]
   * Use ucf for handling conf files (Closes: #814621)
Checksums-Sha1:
 d75cbe875ecc95beb44dec1eb5c5dd5fad00a45b 1890 
diaspora-installer_0.5.7.1+debian1.dsc
 579dfd1b6563904f54f0038bcfb14a1bea499e88 28416 
diaspora-installer_0.5.7.1+debian1.tar.xz
Checksums-Sha256:
 4974e0b3e2d959229b0f218a0e8cae9c5730f44fac56b53eb24f2a125c4684ab 1890 
diaspora-installer_0.5.7.1+debian1.dsc
 df277f3b55410ea6cad8b40d107106cb76c13c0fb860a7883fdd42489fa02ffd 28416 
diaspora-installer_0.5.7.1+debian1.tar.xz
Files:
 fe2f9ff255e52b23910309d13ad7d1ec 1890 ruby optional 
diaspora-installer_0.5.7.1+debian1.dsc
 19fdb32edd7b786863c753a72bbae977 28416 ruby optional 
diaspora-installer_0.5.7.1+debian1.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJW5W9JAAoJEM4fnGdFEsIqEuEQAJHDlJD4BMWZlDYkZs7E1V2X
+3AKemdHwxF3qRTMjXkk4SwLY7E14thhYocJOAKC/OgKQJmgEtJx7UXkpokIVaWn
AQ5Y7LciXaMkCAvzIaSbrZWmTrKBPpiMKdqO30SvQ8mjTxZM+oBJYtnK1PR10Kcj
nDK8CQdtRInwvDUdi5Fjvj4ARK+JImASIcwcBZHHlSyzDsjqmuZSI1KUzFyAdqZc
C2FqdnrmU1X3wsCoZdMf6KBG16lRn698BH8ZamdZt0uZjR/ElEv9DDpvRoYScpiP
LwNHcRnnKv4fN9pZAMeSgF+GhpWLxv5l3URo69w0gXfTPhFLk6ET61HGR/RLqjY/
TSGOIpwiD2/P3qh+YtEV9Z7TPbE1kg8iGs+zo99HcFCqx2tKG4d7hhay63RKsbkC
qs0y9qXFySQ4fKicevwIahctx7vXIHVgMLvRHns+iXWdDUcZbyc8Lwg/mRWzeaae
4Sqjg50oYSHN9zN5grZhxMVhb/UwybLbB2u09y3y9+KlWKhSuS0KolOp4Zyd17yF
Fwmq4QoxFSUsXOS+gRJNQvKRZK3cJar/Imu4KhzIMdR73pAW3Tm7Vss81OQGuJLN
xtf/yo8CC8sXJ0HN1wrgapHtDONF/t8B+IGECue+6ZoBlyTwViCYUYntTOEROfhx
fkfAztf3lVHyYLGQe+eB
=oYqN
-END PGP SIGNATURE End Message ---

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

[Drew Parsons]

Source: petsc
Followup-For: Bug #816101

The petsc build failure on mipsel appears to be a transient problem on
the build machine. Please try the mipsel build again.


gb petsc_3.6.2.dfsg1-3+b3 . mipsel

Bug#818049: marked as done (debhelper: regression in 9.20160306: dh_compress -P broken)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 15:34:44 +
with message-id 
and subject line Bug#818049: fixed in debhelper 9.20160313
has caused the Debian Bug report #818049,
regarding debhelper: regression in 9.20160306: dh_compress -P broken
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.)


-- 
818049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 9.20160306
Severity: serious
Control: block 817885 with -1
Control: tag 817885 sid stretch
Control: block 817882 with -1
Control: tag 817882 sid stretch
Control: block 817878 with -1
Control: tag 817878 sid stretch

Hi,

a regression in dh_compress (probably ef24f64) makes several packages
FTBFS, e.g. cdrkit (#817878):


  [..]

  --- Building: cdrkit-doc
  dh_installdirs -pcdrkit-doc 
-P/home/lamby/temp/cdt.20160311082702.gjPy8bDWWc/cdrkit-1.1.11/debian/build/cdrkit-doc
 
  dh_installdocs   -pcdrkit-doc 
-P/home/lamby/temp/cdt.20160311082702.gjPy8bDWWc/cdrkit-1.1.11/debian/build/cdrkit-doc
  dh_installchangelogs -pcdrkit-doc 
-P/home/lamby/temp/cdt.20160311082702.gjPy8bDWWc/cdrkit-1.1.11/debian/build/cdrkit-doc
  dh_install   -pcdrkit-doc 
-P/home/lamby/temp/cdt.20160311082702.gjPy8bDWWc/cdrkit-1.1.11/debian/build/cdrkit-doc
  dh_link  -pcdrkit-doc 
-P/home/lamby/temp/cdt.20160311082702.gjPy8bDWWc/cdrkit-1.1.11/debian/build/cdrkit-doc
  dh_compress  -pcdrkit-doc 
-P/home/lamby/temp/cdt.20160311082702.gjPy8bDWWc/cdrkit-1.1.11/debian/build/cdrkit-doc
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/ANNOUNCEMENTs/AN-2.0':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/ANNOUNCEMENTs/AN-2.01':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/ANNOUNCEMENTs/AN-2.01.01a03':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/ANNOUNCEMENTs/AN-2.01.01a04':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/ANNOUNCEMENTs/AN-2.01.01a05':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/ANNOUNCEMENTs/AN-2.01.01a06':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/READMEs/README.ATAPI':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/READMEs/README.multi':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/READMEs/README.netscsid':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/changelog.Debian':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/genisoimage/README.eltorito':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/genisoimage/README.graft_dirs':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/genisoimage/README.hide':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/genisoimage/README.mkhybrid':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/genisoimage/README.releasenotes':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/icedax/FAQ':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/icedax/README':
 No such file or directory
  chmod: cannot access 
'../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/icedax/tracknames.pl':
 No such file or directory
  dh_compress: chmod a-x 
../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/ANNOUNCEMENTs/AN-2.0
 
../../../../../../../../debian/build/cdrkit-doc/usr/share/doc/cdrkit-doc/ANNOUNCEMENTs/AN-2.01
 

Bug#814316: Why does it always takes multiples days when 0-day exploits are in the wild

[Eric Valette]

This progams brings nothing if it is continuously lagging several days 
for critical bugs...




update-flashplugin-nonfree --status
Flash Player version installed on this system  : 11.2.202.569
Flash Player version available on upstream site: 11.2.202.577
flash-mozilla.so - auto mode
  link best version is /usr/lib/flashplugin-nonfree/libflashplayer.so
  link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so
  link flash-mozilla.so is /usr/lib/mozilla/plugins/flash-mozilla.so
/usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50

-- eric

Processed: tagging 815125

[Debian Bug Tracking System]

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

> tags 815125 + patch
Bug #815125 [src:linux] Boot failure in 4.4 related to EFI run-time calls
Bug #815779 [src:linux] Boot failure in 4.4 related to EFI run-time calls
Bug #816157 [src:linux] linux-image-4.4.0-1-amd64: Lenovo Ideapad Y700 failts 
to boot
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#817775: marked as done (diaspora: fails to install: Could not find gem 'responders (= 2.1.0)')

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 20:38:26 +0530
with message-id <56e5826a.9070...@autistici.org>
and subject line fixed in 0.5.5.1+debian-7
has caused the Debian Bug report #817775,
regarding diaspora: fails to install: Could not find gem 'responders (= 2.1.0)'
to be marked as done.

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

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


-- 
817775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diaspora
Version: 0.5.5.1+debian-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package diaspora.
  (Reading database ... 
(Reading database ... 43462 files and directories currently installed.)
  Preparing to unpack .../diaspora_0.5.5.1+debian-6_all.deb ...
  You already have a PostgreSQL database named 'diaspora_production'...
  Unpacking diaspora (0.5.5.1+debian-6) ...
  Setting up diaspora (0.5.5.1+debian-6) ...
  Setting up environment varibales...
  Using /etc/diaspora.conf...
  export RAILS_ENV=production
  export DB=postgres
  RAILS_ENV=production DB=postgres ENVIRONMENT_URL=https://localhost
  Verifying we have all required libraries...
  
uld not find gem 'responders (= 2.1.0)' in any of the gem sources listed in
  your Gemfile or available on this machine.

cheerr,
r processing package diaspora (--configure):
   subprocess installed post-installation script returned error exit status 7
  Errors were encountered while processing:
   diaspora

The diaspora package has
  Depends: ruby-responders (>= 2.1.0~),
which does not match the (= 2.1.0) from the gemfile.


Andreas


diaspora_0.5.5.1+debian-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
control: notfound -1 0.5.5.1+debian-7

Uploaded a version that fixes this issue.



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

Bug#818073: confirmed: only happens in chroots

[Pirate Praveen]

control: severity -1 normal

Just tested outside chroot and captcha is working.



signature.asc
Description: OpenPGP digital signature

Processed: confirmed: only happens in chroots

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #818073 [diaspora] captcha not working in sign up
Severity set to 'normal' from 'grave'

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

Bug#815125: [Fwd: [PATCH] x86/efi: Always map boot service regions into new EFI page tables]

[Ben Hutchings]

You got dropped off the cc list for some of the discussion.  Please can
you test Matt's latest patch (attached).

Ben.

-- 
Ben Hutchings
If at first you don't succeed, you're doing about average.
--- Begin Message ---
Some machines have EFI regions in page zero (physical address
0x) and historically that region has been added to the e820
map via trim_bios_range(), and ultimately mapped into the kernel page
tables. It was not mapped via efi_map_regions() as one would expect.

Alexis reports that with the new separate EFI page tables some boot
services regions, such as page zero, are not mapped. This triggers an
oops during the SetVirtualAddressMap() runtime call.

For the EFI boot services quirk on x86 we need to memblock_reserve()
boot services regions until after SetVirtualAddressMap(). Doing that
while respecting the ownership of regions that may have already been
reserved by the kernel was the motivation behind commit 7d68dc3f1003
("x86, efi: Do not reserve boot services regions within reserved
areas").

That patch was merged at a time when the EFI runtime virtual mappings
were inserted into the kernel page tables as described above, and the
trick of setting ->numpages (and hence the region size) to zero to
track regions that should not be freed in efi_free_boot_services()
meant that we never mapped those regions in efi_map_regions(). Instead
we were relying solely on the existing kernel mappings.

Now that we have separate page tables we need to make sure the EFI
boot services regions are mapped correctly, even if someone else has
already called memblock_reserve(). Instead of stashing a tag in
->numpages, set the EFI_MEMORY_RUNTIME bit of ->attribute. Since it
generally makes no sense to mark a boot services region as required at
runtime, it's pretty much guaranteed the firmware will not have
already set this bit.

For the record, the specific circumstances under which Alexis
triggered this bug was that an EFI runtime driver on his machine was
responding to the EVT_SIGNAL_VIRTUAL_ADDRESS_CHANGE event during
SetVirtualAddressMap().

The event handler for this driver looks like this,

  sub rsp,0x28
  lea rdx,[rip+0x2445] # 0xaa948720
  mov ecx,0x4
  call func_aa9447c0  ; call to ConvertPointer(4, & 0xaa948720)
  mov r11,QWORD PTR [rip+0x2434] # 0xaa948720
  xor eax,eax
  mov BYTE PTR [r11+0x1],0x1
  add rsp,0x28
  ret

Which is pretty typical code for an EVT_SIGNAL_VIRTUAL_ADDRESS_CHANGE
handler. The "mov r11, QWORD PTR [rip+0x2424]" was the faulting
instruction because ConvertPointer() was being called to convert the
address 0x, which when converted is left unchanged and
remains 0x.

The output of the oops trace gave the impression of a standard NULL
pointer dereference bug, but because we're accessing physical
addresses during ConvertPointer(), it wasn't. EFI boot services code
is stored at that address on Alexis' machine.

Reported-by: Alexis Murzeau 
Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815125
Cc: Maarten Lankhorst 
Cc: Matthew Garrett 
Cc: Borislav Petkov 
Cc: Ingo Molnar 
Cc: Ben Hutchings 
Cc: Raphael Hertzog 
Cc: Roger Shimizu 
Signed-off-by: Matt Fleming 
---
 arch/x86/platform/efi/quirks.c | 79 +-
 1 file changed, 62 insertions(+), 17 deletions(-)

diff --git a/arch/x86/platform/efi/quirks.c b/arch/x86/platform/efi/quirks.c
index 2326bf51978f..da35f957d4ed 100644
--- a/arch/x86/platform/efi/quirks.c
+++ b/arch/x86/platform/efi/quirks.c
@@ -164,6 +164,27 @@ efi_status_t efi_query_variable_store(u32 attributes, 
unsigned long size,
 EXPORT_SYMBOL_GPL(efi_query_variable_store);
 
 /*
+ * Helper function for efi_reserve_boot_services() to figure out if we
+ * can free regions in efi_free_boot_services().
+ *
+ * Use this function to ensure we do not free regions owned by somebody
+ * else. We must only reserve (and then free) regions:
+ *
+ * - Not within any part of the kernel
+ * - Not the bios reserved area (E820_RESERVED, E820_NVS, etc)
+ */
+static bool can_free_region(u64 start, u64 size)
+{
+   if (start + size > __pa_symbol(_text) && start <= __pa_symbol(_end))
+   return false;
+
+   if (!e820_all_mapped(start, start+size, E820_RAM))
+   return false;
+
+   return true;
+}
+
+/*
  * The UEFI specification makes it clear that the operating system is free to 
do
  * whatever it wants with boot services code after ExitBootServices() has been
  * called. Ignoring this recommendation a significant bunch of EFI 
implementations 
@@ -180,26 +201,50 @@ void __init efi_reserve_boot_services(void)
efi_memory_desc_t *md = p;
u64 start = md->phys_addr;
u64 size = md->num_pages << EFI_PAGE_SHIFT;
+   bool 

Bug#818073: possibly a chroot issue

[Pirate Praveen]

same error appears in diaspora-installer too, both running in cowbuilder
--login chroots



signature.asc
Description: OpenPGP digital signature

Bug#817990: marked as done (network-manager-iodine: Doesn't work with NetworkManager 1.1)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 13:06:13 +
with message-id 
and subject line Bug#817990: fixed in network-manager-iodine 1.1.0-1
has caused the Debian Bug report #817990,
regarding network-manager-iodine: Doesn't work with NetworkManager 1.1
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

nm-connection-editor prints:

** Message: vpn: 
(iodine,/etc/NetworkManager/VPN/nm-iodine-service.name) cannot load legacy-only 
plugin

And when I click Add, iodine isn't listed in the available connection
types.

- -- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (550, 'stable-updates'), (550, 'stable'), (530, 'testing'), (520, 
'unstable'), (510, 'experimental'), (500, 'unstable-debug'), (500, 
'testing-updates')
Architecture: amd64 (x86_64)

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

Versions of packages network-manager-iodine depends on:
ii  adduser   3.113+nmu3
ii  iodine0.7.0-3
ii  libc6 2.21-9
ii  libdbus-1-3   1.10.6-1
ii  libdbus-glib-1-2  0.102-1
ii  libglib2.0-0  2.46.2-3
ii  libnm-glib-vpn1   0.9.10.0-7
ii  libnm-glib4   0.9.10.0-7
ii  libnm-util2   0.9.10.0-7

network-manager-iodine recommends no packages.

network-manager-iodine suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJW5AhKAAoJENILQgJc2ie5VLgP/iOiq2nd47wiHnXTybtTlWv9
pLAp6KcxuoQGlfVD1/+9L0+k+VWvMVFW7BXEpCvU8L6XXEkAp87dIWXGGazFcR8t
lA5vEM7wbMGIu2gSl6262iq4Xh1GKYQ7pRs6Udf4D/xFqhb4OAhWvAKmgPSAeTVu
cgw0Yyba2goPUay2bcnYJda7UdjLQeHLrScLuLM7SG46gitB5oAPinEvClVWrhKS
UR4fGFX63KMPFyJaC6Ut5bMAZ3emD6XsBDOavta1/uJ5LG6ETVOlE3CvoDSY5C1O
TApPyrAQznGdmKPyCmzirnrLjENBgFZSS3QdjAGuCZfK0eEL2ifFTCkyS1yLNAuU
cAQsG+fNOTOTqqYBg7R3qk8hZ5FSmuIUnh+ANQ9WVfOmtAWehQ6cxcNXv7j3UPHz
+2uCb/42bdNwHN3T47orDdx6zKK3ru8H6DahVI0Kzb5JR3OKIjce6PgMODPpPC49
69RtQdkD7CSDbyaCsgfwj6dnoxeMbP3Y5aW3WK9ybSLCmxX5JJ4pRCwyNvW4ZoW8
EQJ8+ODLxKYYUt1JoxXnaFWSRlyhDWJN3kE+96Urbjll/tKISvvfUjBCzIpTs3ct
sMo7KaIxEKi8btEIFOORL92RI+ZI2Hi/JSnxj1W72oWF0QOUC4UHsQ/WW6HNTvDH
LAWjqcao1z7Qtq/N+igv
=v9kt
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: network-manager-iodine
Source-Version: 1.1.0-1

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated network-manager-iodine 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Mar 2016 13:28:32 +0100
Source: network-manager-iodine
Binary: network-manager-iodine network-manager-iodine-gnome
Architecture: amd64 source
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Closes: 771821 817990
Description: 
 network-manager-iodine-gnome - network management framework (iodine plugin 
GNOME GUI)
 network-manager-iodine - network management framework (iodine plugin core)
Changes:
 network-manager-iodine (1.1.0-1) unstable; urgency=medium
 .
   * [903e67b] Bump build-dep on libnm-gtk-dev.
 Thanks to Logan Rosen (Closes: #771821)
   * [872589b] Update dependencies for NM 1.1
 (Closes: #817990)
   * [37e1783] Use secure URL for gitweb
   * [7296140] Bump standards version - no source changes neede
   * [df03f98] Make override_dh_makeshlibs multiarch aware
Checksums-Sha1: 
 d71ec95f83e4d57ecfe311a2cb6c19672f566865 2219 
network-manager-iodine_1.1.0-1.dsc
 02fd261027418c8c399a3168cccff9aecd4d1a2a 38569 
network-manager-iodine_1.1.0.orig.tar.gz
 

Bug#818081: opam: Please apply upstream patch: remove insecure / no-check-certificate flags

[Ximin Luo]

Package: opam
Version: 1.2.2-4.1
Severity: grave
Tags: patch security
Justification: user security hole

Dear Maintainer,

Currently opam forces curl/wget to not check the certificate, allowing a MITM
to inject arbitrary code to users using opam, which eventually will likely be
run by them. This has been fixed upstream:

https://github.com/ocaml/opam/commit/3d43295df3bb9e67e60801d319bf82c2c8a84d24

I have backported the patch to the current version of opam in Debian; see the
attached file. I've also built this myself:

https://people.debian.org/~infinity0/apt/pool/contrib/o/opam

and installed it, ran it, and checked that things still work.

X

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

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

Versions of packages opam depends on:
ii  build-essential  11.7
ii  curl 7.47.0-1
ii  libbz2-1.0   1.0.6-8
ii  libc62.21-9
ii  opam-docs1.2.2-4.1
ii  tar  1.28-2.1
ii  unzip6.0-20
ii  wget 1.17.1-1+b1
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages opam recommends:
ii  aspcud 1:1.9.1-2
ii  darcs  2.10.2-1
ii  git1:2.7.0-1
ii  mercurial  3.5.2-2
ii  ocaml  4.02.3-6
ii  rsync  3.1.1-3

opam suggests no packages.

-- no debconf information
Description: remove insecure / no-check-certificate flags (see mail on opam-devel, #55 #2006)
Author: Hannes Mehnert 
Applied-Upstream: 3d43295df3bb9e67e60801d319bf82c2c8a84d24
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/core/opamSystem.ml
+++ b/src/core/opamSystem.ml
@@ -694,7 +694,7 @@
   let retry = string_of_int OpamGlobals.download_retry in
   let wget ~compress:_ ?checksum:_ dir src =
 let wget_args = [
-  "--content-disposition"; "--no-check-certificate";
+  "--content-disposition";
   "-t"; retry;
   src
 ] in
@@ -704,7 +704,7 @@
   in
   let curl command ~compress ?checksum:_ dir src =
 let curl_args = [
-  "--write-out"; "%{http_code}\\n"; "--insecure";
+  "--write-out"; "%{http_code}\\n";
   "--retry"; retry; "--retry-delay"; "2";
 ] @ (if compress then ["--compressed"] else []) @ [
 "-OL"; src

Processed: its a bug in sigar

[Debian Bug Tracking System]

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

> forwarded 818054 https://github.com/hyperic/sigar/issues/60
Bug #818054 [diaspora-installer] diaspora fails to start with ruby2.3: symbol 
lookup error:...sigar.so: undefined symbol: sigar_skip_token
Set Bug forwarded-to-address to 'https://github.com/hyperic/sigar/issues/60'.
> unblock 813237 by 818054
Bug #813237 [release.debian.org] transition: ruby2.3
813237 was blocked by: 818054
813237 was not blocking any bugs.
Removed blocking bug(s) of 813237: 818054
>
End of message, stopping processing here.

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

Processed: add found versions

[Debian Bug Tracking System]

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

> found 818073 0.5.5.1+debian-7
Bug #818073 [diaspora] captcha not working in sign up
There is no source info for the package 'diaspora' at version 
'0.5.5.1+debian-7' with architecture ''
Unable to make a source version for version '0.5.5.1+debian-7'
Marked as found in versions 0.5.5.1+debian-7.
>
End of message, stopping processing here.

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

Bug#818073: captcha not working in sign up

[Pirate Praveen]

package: diaspora
severity: grave
justification: makes package unusable

production log has this error.

[2016-03-13T11:00:13] INFO  PID-7890 TID-19665120
ActionController::Base: Completed 200 OK in 615ms (Views: 355.1ms |
ActiveRecord: 46.2ms)
[2016-03-13T11:00:13] INFO  PID-7887 TID-19665120 Rails: Started GET
"/simple_captcha?code=81a2c55b5c8815d1ce5aa98f6af4a1c8e0e29069=1457866812"
for 14.97.249.73 at 2016-03-13 11:00:13 +
[2016-03-13T11:00:14] FATAL PID-7887 TID-19665120 Rails:
StandardError (Error while running convert: convert: unable to read font
`(null)' @ error/annotate.c/RenderFreetype/1127.
convert: unable to read font `(null)' @
error/annotate.c/RenderFreetype/1127.
convert: no images defined `jpeg:-' @
error/convert.c/ConvertImageCommand/3210.
):
  lib/rack/chrome_frame.rb:39:in `call'
  lib/unicorn_killer.rb:35:in `call'





signature.asc
Description: OpenPGP digital signature

Bug#818072: warzone2100: FTBFS in stretch (new flex)

[Santiago Vila]

Package: src:warzone2100
Version: 3.1.1-2
Severity: serious

Dear maintainer:

This package currently fails to build from source in stretch:

resource_lexer.lpp: In function 'int res_lex_destroy()':
resource_lexer.lpp:154:5: error: redefinition of 'int res_lex_destroy()'
resource_lexer.cpp:1928:5: note: 'int res_lex_destroy()' previously defined here
 int res_lex_destroy  (void)
  ^
Makefile:475: recipe for target 'resource_lexer.o' failed

I suspect that the new flex is the reason.

The full build log is attached.

Thanks.

warzone2100_3.1.1-2_amd64-20160313-1047.gz
Description: application/gzip

Bug#788062: #788062 - os-prober corrupts partitions

[Thilo Six]

Hello RMs,
Hello SRMs,
Hello D-I folks,


i dare to write on this channels because there is a IMHO rather serious bug in
os-prober which up to now went below the radar of everyone it seems.
So this email in the first place is ment to make more people aware of this issue
and here is hope that someone will catch this up and fix it.

os-prober corrupts partitions
https://bugs.debian.org/788062

This bug leads to serious data loss and is TTBOMK also present in stable.
The original bugreport talks about LVM partitions being corrupted but to my
observations also simple partition layouts with extented partitions are being
hosed. Attached you will find a matching snippet from syslog where sda4 is a
extended partition.
Note the line where is says:
>>>WARNING<<< Wrong ufstype may corrupt your filesystem

IIRC i saw other messages where it talked s.th. about not valid QNX4 format.

On upgrading one machine jessie -> stretch grub asked me to choose the partition
to install so, because it said the ID/number of original partition would have
changed.

To sum it up: This one is set _valid_ to highest bug priority debian knows.


Side note:
Here i want to make crystal clear i do not blame maintainers or any other debian
folks. I am just saying there i a rather unfortunate situation which i hope will
now be handled.
Thanks for your time.


kind regards,

 Thilo
Mar 12 06:56:39 tosh os-prober: debug: running 
/usr/lib/os-probes/50mounted-tests on /dev/sda4
Mar 12 06:56:39 tosh kernel: [ 1919.296306] EXT4-fs (sda4): unable to read 
superblock
Mar 12 06:56:39 tosh kernel: [ 1919.299097] EXT4-fs (sda4): unable to read 
superblock
Mar 12 06:56:39 tosh kernel: [ 1919.302061] EXT4-fs (sda4): unable to read 
superblock
Mar 12 06:56:39 tosh kernel: [ 1919.311096] XFS (sda4): Invalid superblock 
magic number
Mar 12 06:56:39 tosh kernel: [ 1919.319151] FAT-fs (sda4): utf8 is not a 
recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Mar 12 06:56:39 tosh kernel: [ 1919.319345] FAT-fs (sda4): bogus number of 
reserved sectors
Mar 12 06:56:39 tosh kernel: [ 1919.320495] FAT-fs (sda4): Can't find a valid 
FAT filesystem
Mar 12 06:56:39 tosh kernel: [ 1919.323291] FAT-fs (sda4): utf8 is not a 
recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Mar 12 06:56:39 tosh kernel: [ 1919.323478] FAT-fs (sda4): bogus number of 
reserved sectors
Mar 12 06:56:39 tosh kernel: [ 1919.324698] FAT-fs (sda4): Can't find a valid 
FAT filesystem
Mar 12 06:56:39 tosh kernel: [ 1919.334709] MINIX-fs: unable to read superblock
Mar 12 06:56:39 tosh kernel: [ 1919.340084] attempt to access beyond end of 
device
Mar 12 06:56:39 tosh kernel: [ 1919.340093] sda4: rw=16, want=3, limit=2
Mar 12 06:56:39 tosh kernel: [ 1919.340098] hfsplus: unable to find HFS+ 
superblock
Mar 12 06:56:39 tosh kernel: [ 1919.343453] qnx4: no qnx4 filesystem (no root 
dir).
Mar 12 06:56:39 tosh kernel: [ 1919.347670] You didn't specify the type of your 
ufs filesystem
Mar 12 06:56:39 tosh kernel: [ 1919.347670]
Mar 12 06:56:39 tosh kernel: [ 1919.347670] mount -t ufs -o 
ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
Mar 12 06:56:39 tosh kernel: [ 1919.347670]
Mar 12 06:56:39 tosh kernel: [ 1919.347670] >>>WARNING<<< Wrong ufstype may 
corrupt your filesystem, default is ufstype=old
Mar 12 06:56:39 tosh kernel: [ 1919.353385] hfs: can't find a HFS filesystem on 
dev sda4


root ~ # fdisk -l /dev/sda
Disk /dev/sda: 238,5 GiB, 256060514304 bytes, 500118192 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x14e852ea

Device BootStart   End   Sectors   Size Id Type
/dev/sda1  *2048  31250431  31248384  14,9G 83 Linux
/dev/sda2   31250432  56641535  25391104  12,1G 83 Linux
/dev/sda3   56641536  97656831  41015296  19,6G 82 Linux swap / Solaris
/dev/sda4   97658878 500117503 402458626 191,9G  5 Extended
/dev/sda5   97658880 500117503 402458624 191,9G 83 Linux

Bug#818069: influxdb: FTBFS in stretch

[Santiago Vila]

Package: src:influxdb
Version: 0.10.0+dfsg1-1
Severity: serious

Dear maintainer: This package fails to build from source in stretch.

I'd love to say something about why it fails, but I really don't know.

The full build log is attached.

Thanks.

influxdb_0.10.0+dfsg1-1_amd64-20160313-1047.gz
Description: application/gzip

Bug#816101: petsc: FTBFS on mipsel - timeout while running the test suite

[Drew Parsons]

As far as I can tell this build failure is just some ephemeral problem
on the build machine.  The same code built before, and builds now on
mips and other architectures. Trigger a rebuild, maybe it will work
now.

The orte/plm warning is a red herring.  All architectures have the same
problem. It's a warning not an error.  In any case, I've uploaded
v3.6.3 and invoked plm rather than orte.  Hopefully once the new
version is pushed through, the mipsel build will clear.

Drew

Bug#818036: kpartx does not ship multipathd.service but tries to start/stop that service

[Ritesh Raj Sarraf]

Control: tag -1 +confirmed
Control: tag -1 +help


Hello Michael,


On Sat, 2016-03-12 at 23:52 +0100, Michael Biebl wrote:
> The maintainers scripts of kpartx try to start/stop
> multipathd.service
> That service unit is shipped in the multipath-tools package though.
> So this looks like an error in debian/rules.

It was my bad. For the last upload, I missed to install-test locally.


> Combining -a and -p doesn't really make sense.

Yes. But this workaround is needed for Reporoducible  Builds, until I
migrate them to the newer dh interface.

So my refined debian/rules, that fixes the problem is:

rrs@learner:~/.rrs-home/Community/Packaging/multipath-tools (master)$
git diff
diff --git a/debian/rules b/debian/rules
index 9714d03..d00f71e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -104,9 +104,9 @@ binary-indep: build-indep install-indep
dh_installchangelogs -i ChangeLog
dh_installdocs -i
dh_installexamples -i
-   dh_installinit -i -pmultipath-tools-boot --name=multipath-
tools-boot --no-start -- start 21 S .
-   dh_installinit -i -pmultipath-tools-boot
-   dh_installdebconf -i -pmultipath-tools-boot
+   dh_installinit -pmultipath-tools-boot --name=multipath-tools-
boot --no-start -- start 21 S .
+   dh_installinit -pmultipath-tools-boot
+   dh_installdebconf -pmultipath-tools-boot
dh_installman -i
dh_compress -i
dh_fixperms -i
@@ -123,13 +123,13 @@ binary-arch: build install
dh_installdocs -a
dh_installexamples -a
dh_lintian -a
-   dh_systemd_enable -a -pmultipath-tools multipathd.service
-   dh_installinit -a -pmultipath-tools
-   dh_installudev -a -pkpartx
-   dh_installudev -a -pmultipath-tools --name=multipath
+   dh_systemd_enable -pmultipath-tools multipathd.service
+   dh_installinit -pmultipath-tools
+   dh_installudev -pkpartx
+   dh_installudev -pmultipath-tools --name=multipath
dh_link -a lib/systemd/system/multipathd.service \
lib/systemd/system/multipath-tools.service
-   dh_systemd_start -a -pmultipath-tools multipathd.service
+   dh_systemd_start -pmultipath-tools multipathd.service
dh_installman -a
dh_makeshlibs -a --add-udeb=multipath-udeb
dh_link -a
2016-03-13 / 15:37:21 ♒♒♒  ☺  


But I have another problem now.

rrs@learner:/var/tmp/Debian-Build/Result$ sudo dpkg -i --force-all
kpartx_*.deb
Selecting previously unselected package kpartx.
(Reading database ... 429913 files and directories currently
installed.)
Preparing to unpack kpartx_0.5.0+git1.656f8865-6_amd64.deb ...
Failed to stop multipathd.service: Unit multipathd.service not loaded.
dpkg: warning: subprocess old pre-removal script returned error exit
status 5
dpkg: trying script from the new package instead ...
dpkg: error processing archive kpartx_0.5.0+git1.656f8865-6_amd64.deb
(--install):
 there is no script in the new version of the package - giving up
Failed to get unit file state for multipathd.service: No such file or
directory
multipathd.service is a disabled or a static unit, not starting it.
Errors were encountered while processing:
 kpartx_0.5.0+git1.656f8865-6_amd64.deb
2016-03-13 / 15:17:10 ♒♒♒  ☹  => 1  

Now locally, I've overridden this by fixing the postinst file by hand.

rrs@learner:/var/tmp/Debian-Build/Result$ sudo dpkg -i kpartx_*.deb
(Reading database ... 429913 files and directories currently
installed.)
Preparing to unpack kpartx_0.5.0+git1.656f8865-6_amd64.deb ...
Unpacking kpartx (0.5.0+git1.656f8865-6) over (0.5.0+git1.656f8865-6)
...
Setting up kpartx (0.5.0+git1.656f8865-6) ...
Processing triggers for man-db (2.7.5-1) ...
2016-03-13 / 15:18:51 ♒♒♒  ☺  


But I can't find much documentation on how to do it for others through
the packaging itself. Do you know about how to handle this situation ?



-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Processed: Re: Bug#818036: kpartx does not ship multipathd.service but tries to start/stop that service

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +confirmed
Bug #818036 [kpartx] kpartx does not ship multipathd.service but tries to 
start/stop that service
Added tag(s) confirmed.
> tag -1 +help
Bug #818036 [kpartx] kpartx does not ship multipathd.service but tries to 
start/stop that service
Added tag(s) help.

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

Bug#817112: marked as done (libvirglrenderer0 and libvirglrenderer-dev: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Sun, 13 Mar 2016 09:36:38 +
with message-id 
and subject line Bug#817112: fixed in virglrenderer 0.4.0-5
has caused the Debian Bug report #817112,
regarding libvirglrenderer0 and libvirglrenderer-dev: error when trying to 
install together
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.)


-- 
817112: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvirglrenderer-dev,libvirglrenderer0
Version: libvirglrenderer-dev/0.4.0-4
Version: libvirglrenderer0/0.4.0-4
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-03-08
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 libdrm2:amd64.
(Reading database ... 10939 files and directories currently installed.)
Preparing to unpack .../libdrm2_2.4.67-1_amd64.deb ...
Unpacking libdrm2:amd64 (2.4.67-1) ...
Selecting previously unselected package libepoxy0:amd64.
Preparing to unpack .../libepoxy0_1.3.1-1_amd64.deb ...
Unpacking libepoxy0:amd64 (1.3.1-1) ...
Selecting previously unselected package libexpat1:amd64.
Preparing to unpack .../libexpat1_2.1.0-7_amd64.deb ...
Unpacking libexpat1:amd64 (2.1.0-7) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Selecting previously unselected package libwayland-client0:amd64.
Preparing to unpack .../libwayland-client0_1.9.0-1_amd64.deb ...
Unpacking libwayland-client0:amd64 (1.9.0-1) ...
Selecting previously unselected package libwayland-server0:amd64.
Preparing to unpack .../libwayland-server0_1.9.0-1_amd64.deb ...
Unpacking libwayland-server0:amd64 (1.9.0-1) ...
Selecting previously unselected package libgbm1:amd64.
Preparing to unpack .../libgbm1_11.1.2-1_amd64.deb ...
Unpacking libgbm1:amd64 (11.1.2-1) ...
Selecting previously unselected package libvirglrenderer0.
Preparing to unpack .../libvirglrenderer0_0.4.0-4_amd64.deb ...
Unpacking libvirglrenderer0 (0.4.0-4) ...
Selecting previously unselected package libvirglrenderer-dev.
Preparing to unpack .../libvirglrenderer-dev_0.4.0-4_amd64.deb ...
Unpacking libvirglrenderer-dev (0.4.0-4) ...
dpkg: error processing archive 
/var/cache/apt/archives/libvirglrenderer-dev_0.4.0-4_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libvirglrenderer.so', which is 
also in package libvirglrenderer0 0.4.0-4
Processing triggers for libc-bin (2.22-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libvirglrenderer-dev_0.4.0-4_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


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/x86_64-linux-gnu/libvirglrenderer.so

This bug has been filed against 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 then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.
--- End Message ---
--- Begin Message ---
Source: virglrenderer
Source-Version: 0.4.0-5

We believe that the bug you reported is fixed in the latest version of
virglrenderer, 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 817...@bugs.debian.org,
and 

Bug#818066: FTBFS: pep8 module is now in python-pep8 package

[Edward Betts]

Source: nwdiag
Version: 1.0.3-4
Severity: serious
Justification: fails to build from source

Building the package fails in the test suite because the pep8 module is now in
the python-pep8 package.

The Build-Depends for this package need to be updated.

Here is the failing part of the build.

   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m nose
.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSSE..SSS.SSS.SSS.SSS.SSS.SSS.SSSE.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSS.SSSE
==
ERROR: Failure: ImportError (No module named pep8)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/nwdiag/tests/test_pep8.py", line 
6, in 
import pep8
ImportError: No module named pep8

==
ERROR: Failure: ImportError (No module named pep8)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/packetdiag/tests/test_pep8.py", 
line 6, in 
import pep8
ImportError: No module named pep8

==
ERROR: Failure: ImportError (No module named pep8)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 418, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/rackdiag/tests/test_pep8.py", 
line 6, in 
import pep8
ImportError: No module named pep8

--
Ran 312 tests in 3.979s

FAILED (SKIP=120, errors=3)

Bug#818054: eye is failing to load

[Pirate Praveen]

sudo -E -H -u diaspora bundle exec loader_eye -st -c config/eye.rb
ruby2.3: symbol lookup error:
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sigar-0.7.3/lib/sigar.so:
undefined symbol: sigar_skip_token



signature.asc
Description: OpenPGP digital signature

Processed: sigar gem fails for diaspora-installer

[Debian Bug Tracking System]

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

> block 813237 by 818054
Bug #813237 [release.debian.org] transition: ruby2.3
813237 was not blocked by any bugs.
813237 was not blocking any bugs.
Added blocking bug(s) of 813237: 818054
>
End of message, stopping processing here.

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

Bug#818060: FTBFS: pep8 module is now in python-pep8 package

[Edward Betts]

Source: shortuuid
Version: 0.4.3-1
Severity: serious
Justification: fails to build from source

Building the package fails in the test suite because the pep8 module is now in 
the python-pep8 package. 

The Build-Depends for this package need to be updated.

Here is the failing part of the build:

debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
set -e ; \
python2.7 build2.7/lib.*-2.7/shortuuid/tests.py
Traceback (most recent call last):
  File "build2.7/lib.linux-x86_64-2.7/shortuuid/tests.py", line 5, in 
import pep8
ImportError: No module named pep8
debian/rules:16: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

-- 
Edward.

Processed: severity of 817789 is serious

[Debian Bug Tracking System]

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

> severity 817789 serious
Bug #817789 [src:blockdiag] FTBFS: pep8 module is now in python-pep8 package
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#818057: FTBFS: pep8 module is now in python-pep8 package

[Edward Betts]

Source: actdiag
Version: 0.5.3-5
Severity: serious

The pep8 module is now in python-pep8 package, so the Build-Depends for this
package needs to be updated.

-- 
Edward.