Bug#747863: systemd service fails by default and causes package install failure

[Laurent Bigonville]

On Wed, 04 Mar 2015 18:40:12 +0100 Michael Biebl 
wrote:
> There are two ways how this could be addressed, I think:
> 
> 1/ disabled systemd services shouldn't be started by invoke-rc.d
> This is a bug in sysv-rc and should be fixed irregardless of nut [1]
> 
> 
> 2/ nut could work-around this (for jessie), by using a dh_installinit
> --error-handler function, which simply ignores a non-zero return code
> when the service is started unconfigured and fails.

I'm already looking at implementing 2). But I don't have a lot of time
ATM :/

I'll try to work on this this weekend, but cannot promis anything

Cheers,

Laurent Bigonville
 
> 
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768450


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

Bug#777122: marked as done (patch: regression patching files via directory symlinks)

[Debian Bug Tracking System]

Your message dated Sat, 07 Mar 2015 07:19:00 +
with message-id 
and subject line Bug#777122: fixed in patch 2.7.5-1
has caused the Debian Bug report #777122,
regarding patch: regression patching files via directory symlinks
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.)


-- 
777122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: patch
Version: 2.7.4-1
Severity: serious
Justification: causes FTBFS in other packages

Hi,

I think patch now refuses a legitimate use of directory symlinks,
causing nvidia-graphics-drivers to FTBFS.
It does not involve creating symlinks and only uses relative "forward" symlinks
for directories, not the files involved, reproduce as follows:

mkdir -p a/link b/link
echo hello > a/link/file
echo world > b/link/file
diff -u a/link/file b/link/file > the.patch
rm -f a/link/file b/link/file
rmdir a/link b/link a b

mkdir dir
ln -s dir link
echo hello > dir/file

$ cat link/file
hello

$ patch -p1 --debug 32 < the.patch
Resolving path "link/" (failed)
Refusing to follow symbolic link link

$ patch -p1 --follow-symlinks --debug 32 < the.patch
Resolving path "link/" (failed)
Refusing to follow symbolic link link

The description of the --follow-symlinks option did not sound like it
was intended for this case (but rather for symlinks to file targets),
but I tried it anyway.

Looking at the code, getting into a ELOOP situation here sounds like a
logic flaw.


Andreas
--- End Message ---
--- Begin Message ---
Source: patch
Source-Version: 2.7.5-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 07 Mar 2015 06:27:14 +
Source: patch
Binary: patch
Architecture: source amd64
Version: 2.7.5-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 patch  - Apply a diff file to an original
Closes: 777122
Changes:
 patch (2.7.5-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fix symlink directory regression (closes: #777122).
   * Update Standards-Version to 3.9.6 .
Checksums-Sha1:
 63aee4f9f8b13d4734557c745db78216d99d7787 1795 patch_2.7.5-1.dsc
 8fd8f8f8ba640d871bce1bd33c7fd5e2ebe03a1e 727704 patch_2.7.5.orig.tar.xz
 9208549344c913cf055622f7db9ae34f184a7d3b 8116 patch_2.7.5-1.debian.tar.xz
 f5218d69afa4e63dd6bdebc838917ec5927d8868 109154 patch_2.7.5-1_amd64.deb
Checksums-Sha256:
 909ac12aa395f8b32a4524dcea67207567e99d2560e2a833ba577ec64c4cc1bd 1795 
patch_2.7.5-1.dsc
 fd95153655d6b95567e623843a0e77b81612d502ecf78a489a4aed7867caa299 727704 
patch_2.7.5.orig.tar.xz
 c5b9797658fdc1c150072fc9568279bd62c591b2fc43fa6d33750a9a4e8f0ddd 8116 
patch_2.7.5-1.debian.tar.xz
 4216a864e12ac63833bca0131b93efd867cde5c9847a2a05c608eeec3dbb3b79 109154 
patch_2.7.5-1_amd64.deb
Files:
 a99f533a1d63f0369703e9169214100b 1795 vcs standard patch_2.7.5-1.dsc
 e3da7940431633fb65a01b91d3b7a27a 727704 vcs standard patch_2.7.5.orig.tar.xz
 916187a32b65aafca7b41c49168e9351 8116 vcs standard patch_2.7.5-1.debian.tar.xz
 26ab690459b20ce8c6bcaa4f421f49c0 109154 vcs standard patch_2.7.5-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJU+qUQAAoJENzjEOeGTMi/WnMQAJVaQypf/xFlIKdZztwDQWRB
8Tq/rwRTp75ewwMhdaKCYPE+N/9LOp6bTsLxOyfQHJWM3ZNAf/dXmYkOqD0uN0fK
SIXZPFkbGogj84DapBZbkg3kGj1YuiKmj3pPBVVqxMZ1ykUYNgrpNXy3JA7YJR0c
zsPpj7qXK2YmLzGtnQsj65nVTFz2uRaErFUWyipXn+rD541K0ESf0M6nLbGf9LQA
28vT9GODL01Hy5pglKf8HU8zy7wLBSz+9asXFqldkgA7/QFPAg6245Vz1U9DL8e4
Neka+NE+6b+/IAJ2a/AE+Z5EJOE2dKsgz4oExZGoSnBXO/HfecpCGEjGSDmlZdCH
ezFXHoh79GgqmAFhaTBZ0r6PvSc7cQ4C/WEUndIosx3MnQC35ikMXjtbRQOw5xqw
+KCssK6sE9xptRB4wV/mVdtJj2VIu5rnOtQWNwVSFS0NH//3eKVg3GSPAdyjp3C1
yeThj4eLBz2L7LIDRjjtq30LjY8dFzBBvceEU3vTrrpHVdso1YSnkdXDrbot+tuc
hrsupPcMRQs+QMtk3FEt7zYuK4Mh86Lyr5m9PfT1fbDIfqLUghMshXRJCrL5yFgg
KqHnZw8OR2RK4JHU3h11TWlvORplmLIFsmxvyD3R

Bug#776483: python-imaging: no smooth upgrade path from wheezy due to python-imaging-tk becoming a virtual package

[Cameron Norman]

I have prepared an NMU with the transitional package that Andreas 
recommended.
diff -Nru pillow-2.6.1/debian/changelog pillow-2.6.1/debian/changelog
--- pillow-2.6.1/debian/changelog	2014-10-13 11:31:22.0 -0700
+++ pillow-2.6.1/debian/changelog	2015-03-06 18:39:18.0 -0800
@@ -1,3 +1,10 @@
+pillow (2.6.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add python-imaging-tk transitional package. Closes: #776483.
+
+ -- Cameron Norman   Fri, 06 Mar 2015 18:37:54 -0800
+
 pillow (2.6.1-1) unstable; urgency=medium
 
   * Pillow 2.6.1 release.
diff -Nru pillow-2.6.1/debian/control pillow-2.6.1/debian/control
--- pillow-2.6.1/debian/control	2014-10-13 11:31:43.0 -0700
+++ pillow-2.6.1/debian/control	2015-03-06 18:49:47.0 -0800
@@ -94,6 +94,12 @@
  .
  This package contains the extension built for the Python debug interpreter.
 
+Package: python-imaging-tk
+Architecture: all
+Depends: python-pil.imagetk
+Description: transitional dummy package for smooth upgrades to python-pil.imagetk
+ This package can be safely removed.
+
 Package: python-sane
 Architecture: any
 Multi-Arch: same

Processed: python-imaging patch

[Debian Bug Tracking System]

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

> tags 776483 + patch
Bug #776483 [python-imaging] python-imaging: no smooth upgrade path from wheezy 
due to python-imaging-tk becoming a virtual package
Added tag(s) patch.
>
End of message, stopping processing here.

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


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

Bug#775624: marked as done (procps: FTBFS in jessie: dh_auto_test: make -j1 check returned exit code 2)

[Debian Bug Tracking System]

Your message dated Fri, 06 Mar 2015 21:34:33 +
with message-id 
and subject line Bug#775624: fixed in procps 2:3.3.9-9
has caused the Debian Bug report #775624,
regarding procps: FTBFS in jessie: dh_auto_test: make -j1 check returned exit 
code 2
to be marked as done.

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

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


-- 
775624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: procps
Version: 2:3.3.9-8
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20150117 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> make[4]: Entering directory '/«PKGBUILDDIR»/testsuite'
> Making a new site.exp file ...
> srcdir='.'; export srcdir; \
> EXPECT=expect; export EXPECT; \
> if /bin/bash -c "runtest --version" > /dev/null 2>&1; then \
>   exit_status=0; l='pmap slabtop sysctl kill free lib pgrep pkill ps pwdx 
> uptime vmstat w'; for tool in $l; do \
> if runtest  --tool $tool --srcdir $srcdir ; \
> then :; else exit_status=1; fi; \
>   done; \
> else echo "WARNING: could not find 'runtest'" 1>&2; :;\
> fi; \
> exit $exit_status
> WARNING: Couldn't find tool init file
> Test Run By user on Sat Jan 17 22:44:49 2015
> Native configuration is x86_64-pc-linux-gnu
> 
>   === pmap tests ===
> 
> Schedule of variations:
> unix
> 
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using ./config/unix.exp as tool-and-target-specific interface file.
> Running ./pmap.test/pmap.exp ...
> 
>   === pmap Summary ===
> 
> # of expected passes  11
> /«PKGBUILDDIR»/pmap version 3.3.9
> 
> WARNING: Couldn't find tool init file
> Test Run By user on Sat Jan 17 22:44:50 2015
> Native configuration is x86_64-pc-linux-gnu
> 
>   === slabtop tests ===
> 
> Schedule of variations:
> unix
> 
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using ./config/unix.exp as tool-and-target-specific interface file.
> Running ./slabtop.test/slabtop.exp ...
> 
>   === slabtop Summary ===
> 
> # of unsupported tests1
> WARNING: Couldn't find tool init file
> Test Run By user on Sat Jan 17 22:44:50 2015
> Native configuration is x86_64-pc-linux-gnu
> 
>   === sysctl tests ===
> 
> Schedule of variations:
> unix
> 
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using ./config/unix.exp as tool-and-target-specific interface file.
> Running ./sysctl.test/sysctl_read.exp ...
> 
>   === sysctl Summary ===
> 
> # of expected passes  5
> /«PKGBUILDDIR»/sysctl version 3.3.9
> 
> WARNING: Couldn't find tool init file
> Test Run By user on Sat Jan 17 22:44:50 2015
> Native configuration is x86_64-pc-linux-gnu
> 
>   === kill tests ===
> 
> Schedule of variations:
> unix
> 
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using ./config/unix.exp as tool-and-target-specific interface file.
> Running ./kill.test/kill.exp ...
> 
>   === kill Summary ===
> 
> # of expected passes  5
> /«PKGBUILDDIR»/kill version 3.3.9
> 
> WARNING: Couldn't find tool init file
> Test Run By user on Sat Jan 17 22:44:50 2015
> Native configuration is x86_64-pc-linux-gnu
> 
>   === free tests ===
> 
> Schedule of variations:
> unix
> 
> Running target unix
> Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
> target.
> Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
> Using ./config/unix.exp as tool-and-target-specific interface file.
> Running ./free.test/free.exp ...
> 
>   === free Summary ===
> 
> # of expected passes  11
> /«PKGBUILDDIR»/free version 3.3.9
> 
> WARNING: Couldn't find tool init file
> Test Run By user on Sat Jan 17 22:44:52 2015
> Native configuration is x86_64-pc-linux-gnu
> 
>   === lib tests ===

Bug#778266: marked as done (libarchive: Directory traversal)

[Debian Bug Tracking System]

Your message dated Fri, 06 Mar 2015 21:17:06 +
with message-id 
and subject line Bug#778266: fixed in libarchive 3.0.4-3+wheezy1
has caused the Debian Bug report #778266,
regarding libarchive: Directory traversal
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.)


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

Hi,
please see http://www.openwall.com/lists/oss-security/2015/01/16/7
for details.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: libarchive
Source-Version: 3.0.4-3+wheezy1

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

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

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

Debian distribution maintenance software
pp.
Alessandro Ghedini  (supplier of updated libarchive package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 05 Mar 2015 11:26:19 +0100
Source: libarchive
Binary: libarchive-dev libarchive12 bsdtar bsdcpio
Architecture: source amd64
Version: 3.0.4-3+wheezy1
Distribution: wheezy-security
Urgency: high
Maintainer: Debian Libarchive Maintainers 
Changed-By: Alessandro Ghedini 
Description: 
 bsdcpio- Implementation of the 'cpio' program from FreeBSD
 bsdtar - Implementation of the 'tar' program from FreeBSD
 libarchive-dev - Multi-format archive and compression library (development 
files)
 libarchive12 - Multi-format archive and compression library (shared library)
Closes: 778266
Changes: 
 libarchive (3.0.4-3+wheezy1) wheezy-security; urgency=high
 .
   * Fix directory traversal vulnerability in bsdcpio (Closes: #778266)
Checksums-Sha1: 
 d3e5470de797444de108360c4f6225d2f14735b2 2265 libarchive_3.0.4-3+wheezy1.dsc
 81bf817aa512ad67af583c7a2dab79743e418899 3632806 libarchive_3.0.4.orig.tar.gz
 8239e0cc558dc8da53c42d80adb0aceb53ffde5a 13095 
libarchive_3.0.4-3+wheezy1.debian.tar.gz
 82266d953797e356fb35d55d56b3417678cbbc93 472376 
libarchive-dev_3.0.4-3+wheezy1_amd64.deb
 18f891bca66622199b17bdfbbf04e0323ab17f90 303536 
libarchive12_3.0.4-3+wheezy1_amd64.deb
 b78a66f3d9e2a0b57ae6e952ae5a03ae96fd3f79 54722 bsdtar_3.0.4-3+wheezy1_amd64.deb
 b24bb470c2d24ee90799934ba02cf76c8227cb95 41090 
bsdcpio_3.0.4-3+wheezy1_amd64.deb
Checksums-Sha256: 
 a0ae302f4448b79f345be2ee81874a07e6d351470db32cac926b530676e5a3d7 2265 
libarchive_3.0.4-3+wheezy1.dsc
 76e8d7c7b100ec4071e48c1b7d3f3ea1d22b39db3e45b7189f75b5ff4df90fac 3632806 
libarchive_3.0.4.orig.tar.gz
 94fb184a4da403608b5148f0d735029aca3ce0b7c7805a8fd86aaf84ee80782c 13095 
libarchive_3.0.4-3+wheezy1.debian.tar.gz
 81c9bbf443792e0d08d5ec989551a82dfd2054382bcae8ef5a22c83b92383535 472376 
libarchive-dev_3.0.4-3+wheezy1_amd64.deb
 80560e1227c6e72231410d06b16857587982ccb273595ff6c246bdda97fc98f6 303536 
libarchive12_3.0.4-3+wheezy1_amd64.deb
 45bb89a03b00580272513a01be9de7ccea4913b8b306e982402ba184fcb6f22d 54722 
bsdtar_3.0.4-3+wheezy1_amd64.deb
 fde1185fa26dee4b05b8095044c302870ef757b7380003b101814f551720f95a 41090 
bsdcpio_3.0.4-3+wheezy1_amd64.deb
Files: 
 7ba517dfed36c2a4524e3197ae929ae4 2265 libs optional 
libarchive_3.0.4-3+wheezy1.dsc
 af443ca9a10ddbcbf00f7ae34ca7fc16 3632806 libs optional 
libarchive_3.0.4.orig.tar.gz
 2825020a140d808a9ebf640e45947fbe 13095 libs optional 
libarchive_3.0.4-3+wheezy1.debian.tar.gz
 dca903e8077090060cd3e19703c8c952 472376 libdevel optional 
libarchive-dev_3.0.4-3+wheezy1_amd64.deb
 f990fbb40a827f7f59ff5d0d7b36eb42 303536 libs optional 
libarchive12_3.0.4-3+wheezy1_amd64.deb
 9b47bcffa5f3d32ab8f0e1b0928e17be 54722 utils optional 
bsdtar_3.0.4-3+wheezy1_amd64.deb
 b128ff2861d1c31259da15568b943b72 41090 utils optional 
bsdcpio_3.0.4-3+wheezy1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJU+KF0AAoJEK+lG9bN5XPLgfgP/AxEudGWw/Ey9ZZLXx0i7FPv
MA/WqNxOlwHHKcljPFASPW1+v/qV/c9M1rBteyixOaqcEtohuI1poIuaIlUk5PCl
ZeUBV8Dgvh4QdsXXccDIl0IYeUr608DLgSHLK4TInsTvPPLdwDIF0sHJ78W+Jwoc
GkVr8jPU9gCyFai1sG97aQRTb6k4HiHcJL3bjCzQegZ576wR7COFT0pkANvpiHXi
QmaAamUTnhGI/Ls+o5XCrjvdSVHUB4iwfOvVEuO4HXOIhW3GDG5UFEvoZd2tWN0d
q3Q

Bug#779331: marked as done (maven downloads and runs completely unauthed jars via HTTP)

[Debian Bug Tracking System]

Your message dated Fri, 06 Mar 2015 21:17:11 +
with message-id 
and subject line Bug#779331: fixed in maven 3.0.4-3+deb7u1
has caused the Debian Bug report #779331,
regarding maven downloads and runs completely unauthed jars via HTTP
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.)


-- 
779331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: maven
Version: 3.0.4-3
Severity: grave
Tags: security

By default, maven versions before v3.2.3 downloads from Maven Central using
plain HTTP and do not check any kind of signature on the code before running
it.  This is a very bad situation, making it quite easy for malicious actors
take over the machines where maven is used:

http://blog.ontoillogical.com/blog/2014/07/28/how-to-take-over-any-java-developer/

Luckily, there is a simple step that greatly improves the situation.  HTTPS is
now fully supported on maven central, so Debian's maven should also default to
HTTPS.  A user can set this in ~/.m2/settings.xml, and it works fine with the
Debian version of maven.  But this really needs to be the default, and it
should just be a matter of adding this config information to
/etc/maven/settings.xml

http://central.sonatype.org/pages/consumers.html#apache-maven




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: maven
Source-Version: 3.0.4-3+deb7u1

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated maven 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: Fri, 27 Feb 2015 17:56:07 +0100
Source: maven
Binary: maven
Architecture: source all
Version: 3.0.4-3+deb7u1
Distribution: stable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description: 
 maven  - Java software project management and comprehension tool
Closes: 779331
Changes: 
 maven (3.0.4-3+deb7u1) stable; urgency=high
 .
   * Team upload.
   * Use a secure connection by default to download artifacts
 from the Maven Central repository (Closes: #779331)
Checksums-Sha1: 
 4d63a82a0f2c9aa9cbdf42bda59cc35e0986c854 2504 maven_3.0.4-3+deb7u1.dsc
 95c29f95f34664a87c28e14aabdc1a0aad4fe37b 14603 
maven_3.0.4-3+deb7u1.debian.tar.gz
 73c8337239edfa12a5ffdb7ea37361685a3fda72 1293492 maven_3.0.4-3+deb7u1_all.deb
Checksums-Sha256: 
 8a0dbba189c06d64b1dc083cb2b6df2d69f7618f466dd573d4483cb5bd163705 2504 
maven_3.0.4-3+deb7u1.dsc
 49c2b9bc24eb25baeb00da34539a6797fbb6ec7b11e9572877d5f02ace4b2471 14603 
maven_3.0.4-3+deb7u1.debian.tar.gz
 3c06782f6581c3598f30fc402f76b88fc6e6cbffd6dd7714d06e0cd609b38794 1293492 
maven_3.0.4-3+deb7u1_all.deb
Files: 
 d27d12e5cb9756ccfd5dc8a541d5c5ec 2504 java optional maven_3.0.4-3+deb7u1.dsc
 88c2d10e6577ba3981eab8f0ed0a6a25 14603 java optional 
maven_3.0.4-3+deb7u1.debian.tar.gz
 5f855c9dd4d0ee072973054c63ecad93 1293492 java optional 
maven_3.0.4-3+deb7u1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJU9YNlAAoJEPUTxBnkudCsMrMP/Rg26ZrSFjEcl0xxoqdY8Z61
3H+NNIMQlERWraXePMwU5ago7v89T0fpj342oJw23bKESiOVuIM2mN5tspekPXls
cDL9l3wU9Hzava3n8GuPLZZCb5DtkKcwowZxKD5+FljLuwmD2+wvQ5Psxx8hnKft
D7ArcGtc1/2duxQL5mZLFgPRjsDGjXtdj4HrbglmaZU0OgQKv3gEoV8a8AdkQIAb
L0syzD9+DfuMJXCyBZxaXARCr6hU2kkuujWyBb/7OidKUCQQZpFM3ETGRYswxahN
f+6iaqcYdHm8sd7IyO7DCGhgkf8zlCbVo85oHCcA1NDJwP4TXOEfIZEVMdKyyQB1
B6ST4rCbcmADh5bEZcPHn9LKkM4o4Jt0LL1wqkgkaQGICoA1t++8kChf/AG0gMcS
qA4BxsnUxbx1BdwVH5w6XewB0dh+7gKWNG1MPVX9ialWHiu1ZoCKssYxfOlCiRHs
b9ooDisxIr5WJEXRh+rDx8VVgpilaOCjeSP+RtUOhweFrHyLWqZMjsD6vLg2aPhC
dwCT92S5z6yKX96Xp0uXOYvO0OVxP8VKqjXgj4rbRuYoogwpfQLX8SejXlrg2s28
UIZun8qEgSQzeNZlYq+IhK/1qLuAr21jnlxwj5k/bBTw2EeZklSZiqRaMFGhNlON
LH+BaFgzzyCV+ylbLQDs
=6bOO
-END PGP SIGNATURE End Message ---

Bug#775624: procps: FTBFS in jessie: dh_auto_test: make -j1 check returned exit code 2

[Craig Small]

On Thu, Mar 05, 2015 at 08:31:23AM +0100, Niels Thykier wrote:
> Is there anything holding up this bug from being fixed?
> 
> If the linux patch will solve this then please CC the linux maintainers
> and ask them to apply it (assuming it was not included in their
> 3.16.7-ckt7-1 upload).
> 
> Otherwise, if the test is broken, then please patch out the test.
Just my forgetfullness. I'm building the package now and should be
uploaded in 30 mins or so.  I'm not sure what this linux fix is but
procps will handle either the "old" way or "new" way.

 - craig

-- 
Craig Small (@smallsees)   http://enc.com.au/   csmall at : enc.com.au
Debian GNU/Linux   http://www.debian.org/   csmall at : debian.org
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5


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

Bug#779871: marked as done (python-awsauth, python-requests-aws, python3-awsauth, python3-requests-aws: error when trying to install together)

[Debian Bug Tracking System]

Your message dated Fri, 06 Mar 2015 19:28:37 +
with message-id 
and subject line Bug#779951: Removed package(s) from unstable
has caused the Debian Bug report #779871,
regarding python-awsauth, python-requests-aws, python3-awsauth, 
python3-requests-aws: 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.)


-- 
779871: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-awsauth,python-requests-aws,python3-awsauth,python3-requests-aws
Version: 0.1.6-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

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 python-requests-aws.
  Preparing to unpack .../python-requests-aws_0.1.6-1_all.deb ...
  Unpacking python-requests-aws (0.1.6-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-requests-aws_0.1.6-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/awsauth.py', which is 
also in package python-awsauth 0.1.5-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python-requests-aws_0.1.6-1_all.deb

  Selecting previously unselected package python3-requests-aws.
  Preparing to unpack .../python3-requests-aws_0.1.6-1_all.deb ...
  Unpacking python3-requests-aws (0.1.6-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-requests-aws_0.1.6-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/awsauth.py', which is 
also in package python3-awsauth 0.1.5-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-requests-aws_0.1.6-1_all.deb

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

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

  usr/lib/python2.7/dist-packages/awsauth.py

  usr/lib/python3/dist-packages/awsauth.py

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

Cheers,

Andreas

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


python-awsauth=0.1.5-1_python-requests-aws=0.1.6-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.1.6-1+rm

Dear submitter,

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

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

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

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

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

Bug#779871: python-awsauth, python-requests-aws, python3-awsauth, python3-requests-aws: error when trying to install together

[Scott Kitterman]

On Thursday, March 05, 2015 08:14:35 PM Andreas Beckmann wrote:
> Package:
> python-awsauth,python-requests-aws,python3-awsauth,python3-requests-aws
> Version: 0.1.6-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
> 
> Architecture: amd64
> Distribution: sid

src:python-requests-aws and src:requests-aws are the same upstream package.  
src:requests-aws was there first and is in both Jessie and Sid, so I'll remove 
src:python-requests-aws.

Scott K

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

Processed: tagging 777191

[Debian Bug Tracking System]

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

> tags 777191 - jessie
Bug #777191 [grub-efi-amd64] grub-efi-amd64 on Debian Jessie cannot boot zfs 
native root filesystem running the latest git code soon to be 0.6.4 tagged - 
official release
Removed tag(s) jessie.
> thanks
Stopping processing here.

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


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

Processed: closing 779950

[Debian Bug Tracking System]

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

> close 779950 0.19-1
Bug #779950 [libperl-apireference-perl] libperl-apireference-perl: 0.18 FTBFS 
with Perl 5.20.2
Marked as fixed in versions libperl-apireference-perl/0.19-1.
Bug #779950 [libperl-apireference-perl] libperl-apireference-perl: 0.18 FTBFS 
with Perl 5.20.2
Marked Bug as done
> thanks
Stopping processing here.

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


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

Bug#779950: libperl-apireference-perl: 0.18 FTBFS with Perl 5.20.2

[Niko Tyni]

Package: libperl-apireference-perl
Version: 0.18-1
Severity: serious
Control: done -1 0.19-1

The version of this package in jessie, 0.18, doesn't know about
Perl 5.20.2 which recently entered jessie. The test suite fails:

 echo Current Perl is `perl -MConfig -we'printf("%d_%03d_%03d.pm", 
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
 Current Perl is 5_020_002.pm
 test -f lib/Perl/APIReference/V`perl -MConfig -we'printf("%d_%03d_%03d.pm", 
$Config{PERL_REVISION}, $Config{PERL_VERSION}, $Config{PERL_SUBVERSION})'`
 make[1]: *** [regenerated-stamp] Error 1
 debian/rules:8: recipe for target 'regenerated-stamp' failed

Support for Perl 5.20.2 was introduced in 0.19, currently in sid.
I'm filing this bug mainly to track the issue in jessie.
-- 
Niko Tyni   nt...@debian.org


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

Bug#775913: vala-0.26: diff for NMU version 0.26.1-1.1

[Salvatore Bonaccorso]

Hi Gregor,

On Fri, Mar 06, 2015 at 05:02:52PM +0100, gregor herrmann wrote:
> Control: tags 775913 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for vala-0.26 (versioned as 0.26.1-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

Thanks a lot for preparing that update! Note (but cannot check right
now again), that it looks that any binary build with the buggy
bindings package that use Gst.MapInfo() function are affected as well.
See https://bugzilla.redhat.com/show_bug.cgi?id=1177840, so possibly
shotwell. sources.debian.net might reveal others[*] :(

 [*] possibly rygel as well

Regards,
Salvatore


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

Processed: user release.debian....@packages.debian.org, usertagging 774795, tagging 774795

[Debian Bug Tracking System]

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

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 774795 jessie-can-defer
There were no usertags set.
Usertags are now: jessie-can-defer.
> tags 774795 + jessie-ignore
Bug #774795 [mysql-server-5.5] php5, mysql-server-5.5: php5 FTBFS on ppc64el 
due to mysql assertion failure "InnoDB: Failing assertion: node->n_pending == 0"
Added tag(s) jessie-ignore.
> thanks
Stopping processing here.

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


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

Processed: tagging 777257, found 619370 in 0.1.8

[Debian Bug Tracking System]

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

> tags 777257 + pending
Bug #777257 [src:r8168] Contains non-free firmware
Added tag(s) pending.
> found 619370 0.1.8
Bug #619370 [apt-p2p] apt-p2p: fails to purge - command (deluser|adduser) in 
postrm not found
Marked as found in versions apt-p2p/0.1.8.
> thanks
Stopping processing here.

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


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

Bug#779933: python-qgis: fails to install, trying to overwrite other packages files: /usr/lib/python2.7/dist-packages/pyspatialite/dump.py

[Sebastiaan Couwenberg]

Control: tags -1 pending

Hi Andreas,

Thanks for your work on piuparts.

On 03/06/2015 03:44 PM, Andreas Beckmann wrote:
>   Unpacking python-qgis (2.8.1+dfsg1-1~exp1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/python-qgis_2.8.1+dfsg1-1~exp1_amd64.deb (--unpack):
>trying to overwrite 
> '/usr/lib/python2.7/dist-packages/pyspatialite/dump.py', which is also in 
> package python-pyspatialite 3.0.1-6

I've fixed the qgis package to not build the internal pyspatialite and
use the Debian package instead.

The interal build was erroniously re-enabled after merging the upstream
package changes.

Kind Regards,

Bas

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


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

Processed: Re: Bug#779933: python-qgis: fails to install, trying to overwrite other packages files: /usr/lib/python2.7/dist-packages/pyspatialite/dump.py

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #779933 [python-qgis] python-qgis: fails to install, trying to overwrite 
other packages files: /usr/lib/python2.7/dist-packages/pyspatialite/dump.py
Added tag(s) pending.

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


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

Bug#775913: vala-0.26: diff for NMU version 0.26.1-1.1

[gregor herrmann]

Control: tags 775913 + pending

Dear maintainer,

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

Regards.

-- 
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Element Of Crime: No god anymore
diff -Nru vala-0.26-0.26.1/debian/changelog vala-0.26-0.26.1/debian/changelog
--- vala-0.26-0.26.1/debian/changelog	2014-10-15 21:56:24.0 +0200
+++ vala-0.26-0.26.1/debian/changelog	2015-03-06 16:58:16.0 +0100
@@ -1,3 +1,14 @@
+vala-0.26 (0.26.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "CVE-2014-8154: Heap-buffer overflow in vala-gstreamer bindings
+at Gst.MapInfo()": add patch mapinfo.date-array-length.patch,
+taken from upstream git:
+https://git.gnome.org/browse/vala/commit/?id=22126ebad3b2133db39bcf301c29c8b78b440f1a
+(Closes: #775913)
+
+ -- gregor herrmann   Fri, 06 Mar 2015 16:58:06 +0100
+
 vala-0.26 (0.26.1-1) unstable; urgency=medium
 
   * Team upload.
diff -Nru vala-0.26-0.26.1/debian/patches/mapinfo.date-array-length.patch vala-0.26-0.26.1/debian/patches/mapinfo.date-array-length.patch
--- vala-0.26-0.26.1/debian/patches/mapinfo.date-array-length.patch	1970-01-01 01:00:00.0 +0100
+++ vala-0.26-0.26.1/debian/patches/mapinfo.date-array-length.patch	2015-03-06 16:43:01.0 +0100
@@ -0,0 +1,20 @@
+From 22126ebad3b2133db39bcf301c29c8b78b440f1a Mon Sep 17 00:00:00 2001
+From: Evan Nemerson 
+Date: Mon, 10 Nov 2014 11:09:09 -0800
+Subject: gstreamer-1.0: fix MapInfo.data array length
+
+(cherry picked from commit 3092537db65887e24a3d3e87a27caf9c5295e4f7)
+
+diff --git a/vapi/gstreamer-1.0.vapi b/vapi/gstreamer-1.0.vapi
+index 92909bd..2f3dfeb 100644
+--- a/vapi/gstreamer-1.0.vapi
 b/vapi/gstreamer-1.0.vapi
+@@ -2202,7 +2202,7 @@ namespace Gst {
+ 	public struct MapInfo {
+ 		public weak Gst.Memory memory;
+ 		public Gst.MapFlags flags;
+-		[CCode (array_length = false, array_null_terminated = true)]
++		[CCode (array_length_cname = "size", array_length_type = "gsize")]
+ 		public weak uint8[] data;
+ 		public size_t size;
+ 		public size_t maxsize;
diff -Nru vala-0.26-0.26.1/debian/patches/series vala-0.26-0.26.1/debian/patches/series
--- vala-0.26-0.26.1/debian/patches/series	2014-10-15 21:56:24.0 +0200
+++ vala-0.26-0.26.1/debian/patches/series	2015-03-06 16:42:37.0 +0100
@@ -0,0 +1 @@
+mapinfo.date-array-length.patch


signature.asc
Description: Digital Signature

Processed: vala-0.26: diff for NMU version 0.26.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 775913 + pending
Bug #775913 [src:vala-0.26] vala-0.26: CVE-2014-8154: Heap-buffer overflow in 
vala-gstreamer bindings at Gst.MapInfo()
Added tag(s) pending.

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


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

Bug#779902: /tmp can be mounted as tmpfs against user's will

[Michael Biebl]

Am 06.03.2015 um 16:04 schrieb Michael Biebl:
> I think, PrivateTmp=yes pulling in tmp.mount is a bug and I would simply
> revert b46a529c [1] or replace unit_require_mounts_for with  a After
> dependency [2] only.


The check to add a hard Requires Dependency, is to test for a fragment
path [3]. If we extend that and check also if the unit is actually
enabled, this would solve our problem afaics.

Michael


[3] http://cgit.freedesktop.org/systemd/systemd/tree/src/core/mount.c#n280

-- 
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

Bug#779902: /tmp can be mounted as tmpfs against user's will

[Michael Biebl]

Am 06.03.2015 um 10:10 schrieb Martin Pitt:
> Control: found -1 215-12
> Control: tag -1 confirmed
> 
> Ça va Didier,
> 
> Didier Roche [2015-03-06  9:36 +0100]:
>> In debian, tmp.mount is disabled through a distro-patch by default. It means
>> we don't want user's system to get /tmp on tmpfs without explicit enablement
>> (either by enabling tmp.mount unit or via fstab).
>>
>> We noticed that starting an unit using "PrivateTmp=yes" will pull tmp.mount
>> (which mounts /tmp on tmpfs) in its requirements chain (even if this unit is
>> condition fail).
> 
> Confirmed. "systemctl start colord" or "systemd-timesyncd" will start
> tmp.mount and thus overmount the existing /tmp in the running system.
> I reproduced that in a clean sid VM (with LXDE, but I suppose that
> doesn't matter much).

The odd thing though is, that PrivateTmp=yes does not trigger the start
of tmp.mount during boot at least on all the test systems I have.

Do we know, why that is? A Required=tmp.mount should always start the
referenced unit, but it seemingly doesn't.

>> We need to find a way to ensure that tmp.mount is never accidentally
>> trigger, while still enabling the user using fstab to enable /tmp as tmpfs.
>> Enabling the unit to get the same effect would be a nice addition.
> 
> I dislike masking it, as that will most probalby lead to problems with
> units which have a Requires=tmp.mount (directly or indirectly), these
> would block on a masked unit.
> 
> I think the best way forward is to either not ship the unit at all and
> document in README.Debian to add /tmp as tmpfs in fstab [1], or ship
> it in /usr/share/doc/systemd/ as an example, and document how to
> enable it from there.
> 
> Michael, WDYT?

This would also mean, to revert the existing work to migrate the
RAMTMP=yes setting and clean up existing symlinks.
Not really a fan of that, tbh.

I think, PrivateTmp=yes pulling in tmp.mount is a bug and I would simply
revert b46a529c [1] or replace unit_require_mounts_for with  a After
dependency [2] only.

Michael


[1] http://cgit.freedesktop.org/systemd/systemd/commit/?id=b46a529c
[2] http://cgit.freedesktop.org/systemd/systemd/tree/src/core/mount.c#n265



-- 
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

Bug#779902: /tmp can be mounted as tmpfs against user's will

[Didier Roche]

Le 06/03/2015 16:04, Michael Biebl a écrit :

Am 06.03.2015 um 10:10 schrieb Martin Pitt:

Control: found -1 215-12
Control: tag -1 confirmed

Ça va Didier,

Didier Roche [2015-03-06  9:36 +0100]:

In debian, tmp.mount is disabled through a distro-patch by default. It means
we don't want user's system to get /tmp on tmpfs without explicit enablement
(either by enabling tmp.mount unit or via fstab).

We noticed that starting an unit using "PrivateTmp=yes" will pull tmp.mount
(which mounts /tmp on tmpfs) in its requirements chain (even if this unit is
condition fail).

Confirmed. "systemctl start colord" or "systemd-timesyncd" will start
tmp.mount and thus overmount the existing /tmp in the running system.
I reproduced that in a clean sid VM (with LXDE, but I suppose that
doesn't matter much).

The odd thing though is, that PrivateTmp=yes does not trigger the start
of tmp.mount during boot at least on all the test systems I have.

Do we know, why that is? A Required=tmp.mount should always start the
referenced unit, but it seemingly doesn't.


For reference, I dig a little bit into it and asked on the upstream ML: 
http://lists.freedesktop.org/archives/systemd-devel/2015-March/029072.html


Let's see if the bug we are seeing is really due to tmp.mount not being 
explicitly referenced anywhere.



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

Bug#779931: [Pkg-utopia-maintainers] Bug#779931: "sk_disk_check_sleep_mode: Operation not supported" for USB3 HDD docking based on JMicron 152d:0551

[Michael Biebl]

Am 06.03.2015 um 15:30 schrieb Gianluca Oglietti:
> Package: libatasmart4
> Version: 0.19-3
> Severity: grave
> Justification: causes non-serious data loss
> 
> Dear Maintainer,
> 
> I bought a new HDD docking station (for 2 HDDs) based on JMicron JMB551 
> chipset
> but I discover an issue that could cause data loss.
> 
> If I mount some partitions of 2 HDDs connected to my laptop via USB 3.0 using
> this docking station all works fine until the JMBB551 go in "sleep mode". This
> kind of docking station, in fact, have an "intelligent sleep function" that 
> put
> the HDDs in sleep mode when there aren't R/W data operations for at least 5
> minutes.
> 
> Every 10 minutes udisksd control the state of SMART attributes of the attached
> HDDs but when the docking is in "sleep mode" we notice the error
> "sk_disk_check_sleep_mode: Operation not supported" and the USB connection to
> the docking is resetted as you can see in the next udisksd log:

If checking the SMART state of the sleeping disk resets the USB
connection, then this sounds like a kernel bug.


-- 
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

Bug#779873: mariadb-server-core-10.0: missing breaks+replaces mysql-client-5.[56] for /usr/bin/innochecksum takeover

[Andreas Beckmann]

On 2015-03-06 15:47, Otto Kekäläinen wrote:
> Cool, I didn't know that piuparts also test mysql->mariadb migration
> scenarios. Issue fixed in git now.

I don't test migration (but maybe that could be done as well somehow),
but co-installability of packages sharing some files.
(But for the issues that occur on "carefully crafted" upgrade paths, I
usually just use the piuparts templates.)

Andreas


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

Bug#779873: [debian-mysql] Bug#779873: mariadb-server-core-10.0: missing breaks+replaces mysql-client-5.[56] for /usr/bin/innochecksum takeover

[Otto Kekäläinen]

Cool, I didn't know that piuparts also test mysql->mariadb migration
scenarios. Issue fixed in git now.

Thanks for reporting!


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

Bug#779933: python-qgis: fails to install, trying to overwrite other packages files: /usr/lib/python2.7/dist-packages/pyspatialite/dump.py

[Andreas Beckmann]

Package: python-qgis
Version: 2.8.1+dfsg1-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package python-qgis.
  (Reading database ... 16341 files and directories currently installed.)
  Preparing to unpack .../python-qgis_2.8.1+dfsg1-1~exp1_amd64.deb ...
  Unpacking python-qgis (2.8.1+dfsg1-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python-qgis_2.8.1+dfsg1-1~exp1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/python2.7/dist-packages/pyspatialite/dump.py', 
which is also in package python-pyspatialite 3.0.1-6
  Errors were encountered while processing:
   /var/cache/apt/archives/python-qgis_2.8.1+dfsg1-1~exp1_amd64.deb


cheers,

Andreas


python-qgis_2.8.1+dfsg1-1~exp1.log.gz
Description: application/gzip

Bug#779931: "sk_disk_check_sleep_mode: Operation not supported" for USB3 HDD docking based on JMicron 152d:0551

[Gianluca Oglietti]

Package: libatasmart4
Version: 0.19-3
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

I bought a new HDD docking station (for 2 HDDs) based on JMicron JMB551 chipset
but I discover an issue that could cause data loss.

If I mount some partitions of 2 HDDs connected to my laptop via USB 3.0 using
this docking station all works fine until the JMBB551 go in "sleep mode". This
kind of docking station, in fact, have an "intelligent sleep function" that put
the HDDs in sleep mode when there aren't R/W data operations for at least 5
minutes.

Every 10 minutes udisksd control the state of SMART attributes of the attached
HDDs but when the docking is in "sleep mode" we notice the error
"sk_disk_check_sleep_mode: Operation not supported" and the USB connection to
the docking is resetted as you can see in the next udisksd log:


14:37:52.873:[3496]:[NOTICE]: udisks daemon version 2.1.3 starting [main.c:146,
main()]
14:37:52.874:[3496]:[DEBUG]: Entering main event loop [main.c:171, main()]
14:37:52.885:[3496]:[INFO]: Initialization (device probing)
[udiskslinuxprovider.c:445, udisks_linux_provider_start()]
14:37:52.900:[3496]:[INFO]: Initialization (coldplug 1/2)
[udiskslinuxprovider.c:457, udisks_linux_provider_start()]
14:37:52.900:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop0
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.902:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop1
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.902:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop2
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.903:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop3
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.903:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop4
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.904:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop5
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.904:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop6
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.905:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop7
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.905:[3496]:[DEBUG]: uevent add
/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.907:[3496]:[DEBUG]: uevent add
/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.908:[3496]:[DEBUG]: uevent add
/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda2
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.909:[3496]:[DEBUG]: uevent add
/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda3
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.910:[3496]:[DEBUG]: uevent add
/sys/devices/pci:00/:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sr0
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.911:[3496]:[INFO]: Initialization (coldplug 2/2)
[udiskslinuxprovider.c:457, udisks_linux_provider_start()]
14:37:52.911:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop0
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.911:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop1
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.912:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop2
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.912:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop3
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.912:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop4
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.913:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop5
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.913:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop6
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.913:[3496]:[DEBUG]: uevent add /sys/devices/virtual/block/loop7
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.914:[3496]:[DEBUG]: uevent add
/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.914:[3496]:[DEBUG]: uevent add
/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
[udiskslinuxprovider.c:902, udisks_linux_provider_handle_uevent()]
14:37:52.915:[3496]:[DEBUG]: uevent add

Bug#779922: debian-installer: Installation freezes with "The attempt to mount a files system with type ext4 in SCSI1 (0, 0, 0), partition #1 (sda) at / failed."

[Cyril Brulebois]

Control: severity -1 important
Control: tag -1 - d-i

Hi Igor,

and thanks for your report.

Igor Liferenko  (2015-03-06):
> Package: debian-installer
> Severity: critical
> Tags: d-i
> Justification: breaks the whole system

Ajusting severity since there's no system to break at this point. Also,
released images don't suffer from this issue.

> I take debian testing weekly build from
> http://cdimage.debian.org/cdimage/weekly-builds/i386/jigdo-dvd/debian-testing-i386-DVD-1.jigdo,
> add preseed to it and install in qemu.
> Preseed contains this:
> 
> d-i partman-auto/method string regular
> d-i partman-auto/choose_recipe select atomic
> d-i partman-partitioning/confirm_write_new_label boolean true
> d-i partman/confirm_nooverwrite boolean true
> d-i partman/choose_partition select finish
> d-i partman/confirm boolean true
> 
> Qemu image is created as:
> 
> qemu-img create -f qcow2 newcd-qemu.qcow2 10G
> 
> Previous debian testing builds caused no problem with the same setup (I test 
> each week).
> 
> Problem arised with latest debian testing build (from 02.03.2015).
> 
> Installation freezes with the following error ("Partition disks" stage):
> 
> The attempt to mount a files system with type ext4 in SCSI1 (0,0,0), 
> partition #1 (sda) at / failed.
> 
> You may resume partitioning from the partitioning menu.
> Do you want to resume partitioning?
> - No
> - Yes
> 
> Relevant parts of installer log from qemu follow:
> partman: mke2fs 1.42.12 (29-Aug-2014)
> kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0)

This was reported as #779651 against installation-reports and as #779616
against debian-cd. We're trying to figure out what to do in the latter.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: Re: Bug#779922: debian-installer: Installation freezes with "The attempt to mount a files system with type ext4 in SCSI1 (0, 0, 0), partition #1 (sda) at / failed."

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #779922 [debian-installer] debian-installer: Installation freezes with "The 
attempt to mount a files system with type ext4 in SCSI1 (0, 0, 0), partition #1 
(sda) at / failed."
Severity set to 'important' from 'critical'
> tag -1 - d-i
Bug #779922 [debian-installer] debian-installer: Installation freezes with "The 
attempt to mount a files system with type ext4 in SCSI1 (0, 0, 0), partition #1 
(sda) at / failed."
Removed tag(s) d-i.

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


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

Bug#779922: debian-installer: Installation freezes with "The attempt to mount a files system with type ext4 in SCSI1 (0, 0, 0), partition #1 (sda) at / failed."

[Igor Liferenko]

Package: debian-installer
Severity: critical
Tags: d-i
Justification: breaks the whole system

Dear Maintainer,

I take debian testing weekly build from
http://cdimage.debian.org/cdimage/weekly-builds/i386/jigdo-dvd/debian-testing-i386-DVD-1.jigdo,
add preseed to it and install in qemu.
Preseed contains this:

d-i partman-auto/method string regular
d-i partman-auto/choose_recipe select atomic
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/confirm_nooverwrite boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true

Qemu image is created as:

qemu-img create -f qcow2 newcd-qemu.qcow2 10G

Previous debian testing builds caused no problem with the same setup (I test 
each week).

Problem arised with latest debian testing build (from 02.03.2015).

Installation freezes with the following error ("Partition disks" stage):

The attempt to mount a files system with type ext4 in SCSI1 (0,0,0), partition 
#1 (sda) at / failed.

You may resume partitioning from the partitioning menu.
Do you want to resume partitioning?
- No
- Yes

Relevant parts of installer log from qemu follow:


main-menu INFO: Menu item 'disk-detect' selected
kernel: sda: unknown partition table
main-menu: INFO: Menu item 'partman-base' selected
anna-install: Installing partman-auto-lvm
anna: DEBUG: retrieving crc-modules-3.16.0-4-586-di 3.16.7-ckt7-1
anna: DEBUG: retrieving lvm2-udeb 2.02.111-2
anna: DEBUG: retrieving partman-auto-lvm 56
anna: DEBUG: retrieving partman-lvm 105
anna-install: Installing partman-auto-crypto
anna: DEBUG: retrieving partman-auto-crypto 22
anna: DEBUG: retrieving partman-crypto 78
kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0)
kernel: raid6: mmxx158 MB/s
kernel: raid6: mmxx276 MB/s
kernel: raid6: sse1x1   70 MB/s
kernel: raid6: sse1x2   78 MB/s
kernel: raid6: sse2x1   157 MB/s
kernel: raid6: sse2x2   123 MB/s
kernel: raid6: using algorithm sse2x1 (157 MB/s)
kernel: raid6: using intx1 recovery algorithm
kernel: xor: measuring software checksum speed
kernel: pIII_sse : 430.000 MB/sec
kernel: prefetch64-sse: 429.000 MB/sec
kernel: xor: using function: pIII_sse (430.000 MB/sec)
kernel: btrfs: Unknown symbol pagecache_get_page_fixed (err 0)
kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0)
kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0)
kernel: jfs: Unknown symbol pagecache_get_page_fixed (err 0)
kernel: SGI XFS with ACLs, security attributes, realtime, large block/inode 
numbers, no debug enabled
md-devices: mdadm: No arrays found in config file or automatically
kernel: device-mapper: uevent: version 1.0.3
kernel: device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: 
dm-de...@redhat.com
partman: No matching physical volumes found
partman: Reading all physical volumes. This may take a while...
partman: No volume groups found
partman-lvm: No volume groups found
kernel: sda: unknown partition table
kernel: sda: unknown partition table
kernel: sda: unknown partition table
kernel: sda: sda1 sda2 < sda5 >
kernel: Adding 477189k swap on /dev/sda5. Priority:-1 extents:1 across:477189k 
FS
partman: mke2fs 1.42.12 (29-Aug-2014)
kernel: ext4: Unknown symbol pagecache_get_page_fixed (err 0)

-- System Information:
Debian Release: 8.0
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (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)


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

Processed: user release.debian....@packages.debian.org, usertagging 779420, tagging 779420

[Debian Bug Tracking System]

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

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 779420 jessie-can-defer
There were no usertags set.
Usertags are now: jessie-can-defer.
> tags 779420 + jessie-ignore
Bug #779420 [debconf-i18n,debconf-utils] debconf-{i18n,utils}: dependency on 
debconf too weak
Added tag(s) jessie-ignore.
> thanks
Stopping processing here.

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


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

Processed: user release.debian....@packages.debian.org, usertagging 779251, tagging 779251

[Debian Bug Tracking System]

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

> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 779251 jessie-can-defer
There were no usertags set.
Usertags are now: jessie-can-defer.
> tags 779251 + jessie-ignore
Bug #779251 [libvlc5] libvlc5: dependency on libvlccore8 too weak
Added tag(s) jessie-ignore.
> thanks
Stopping processing here.

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


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

Bug#779909: 389-ds-base: CVE-2014-8105 CVE-2014-8112

[Moritz Muehlenhoff]

Package: 389-ds-base
Severity: grave
Tags: security
Justification: user security hole

Hi,
please see 
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-8112
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-8105

Cheers,
Moritz


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

Processed: Re: Bug#775877: gnome-session: No mouse pointer after login

[Debian Bug Tracking System]

Processing control commands:

> tags 775877 + moreinfo
Bug #775877 [gnome-session] gnome-session: No mouse pointer after login
Added tag(s) moreinfo.

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


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

Bug#775877: gnome-session: No mouse pointer after login

[Simon McVittie]

Control: tags 775877 + moreinfo

On Tue, 20 Jan 2015 at 21:43:09 -0500, Aron Podrigal wrote:
>   Jan 20 16:46:18 jessie gnome-session[1888]: **
>   Jan 20 16:46:18 jessie gnome-session[1888]:
>   
> GLib-GIO:ERROR:/tmp/buildd/glib2.0-2.42.1/./gio/gdbusconnection.c:4231:invoke_set_property_in_idle_cb:
>   assertion failed: (error != NULL)
>   Jan 20 16:46:18 jessie gnome-session[1888]:
>   x-session-manager[1888]: WARNING: Application
>   'gnome-settings-daemon.desktop' killed by signal 6
>   Jan 20 16:46:18 jessie x-session-manager[1888]: WARNING:
>   Application 'gnome-settings-daemon.desktop' killed by signal 6

This seems likely to be the problem: gnome-settings-daemon crashed with
an assertion failure.

If you can get a backtrace from that crash
(), or indicate how a developer
can reproduce it, that would be really useful.

If you create another user account on the same computer, does the same
thing happen for that account?

S


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

Processed: Re: Bug#775877: gnome-session: No mouse pointer after login

[Debian Bug Tracking System]

Processing control commands:

> tags 775877 + moreinfo
Bug #775877 [gnome-session] gnome-session: No mouse pointer after login
Ignoring request to alter tags of bug #775877 to the same tags previously set

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


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

Bug#768133: marked as done (evince print only blank page in landscape / okular work)

[Debian Bug Tracking System]

Your message dated Fri, 06 Mar 2015 09:40:03 +
with message-id 
and subject line Bug#768133: fixed in evince 3.14.1-2
has caused the Debian Bug report #768133,
regarding evince print only blank page in landscape / okular work
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.)


-- 
768133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: evince
Version: 3.14.1-1
Severity: important


Attached a PDF which print only a white paper with evince/jessie.
Same PDF work fine with okular, the printout is as expected.


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

Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages evince depends on:
ii  evince-common  3.14.1-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-12
ii  libcairo-gobject2  1.14.0-2.1
ii  libcairo2  1.14.0-2.1
ii  libevdocument3-4   3.14.1-1
ii  libevview3-3   3.14.1-1
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libglib2.0-0   2.42.0-2
ii  libgtk-3-0 3.14.4-1
ii  libnautilus-extension1a3.14.0-1
ii  libpango-1.0-0 1.36.8-2
ii  libpangocairo-1.0-01.36.8-2
ii  libsecret-1-0  0.18-1+b1
ii  libxml22.9.1+dfsg1-4
ii  shared-mime-info   1.3-1
ii  zlib1g 1:1.2.8.dfsg-2

Versions of packages evince recommends:
ii  dbus-x11  1.8.8-2
ii  gvfs  1.22.1-1

Versions of packages evince suggests:
ii  nautilus  3.14.0-1
ii  poppler-data  0.4.7-1
pn  unrar 

-- no debconf information


pdf_print_evince_fail.pdf
Description: Adobe PDF document
--- End Message ---
--- Begin Message ---
Source: evince
Source-Version: 3.14.1-2

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated evince 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, 06 Mar 2015 08:36:46 +
Source: evince
Binary: evince evince-dbg evince-gtk evince-common libevdocument3-4 
libevview3-3 libevince-dev gir1.2-evince-3.0
Architecture: all source
Version: 3.14.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 768133
Description: 
 evince-common - Document (PostScript, PDF) viewer - common files
 evince-dbg - Document (PostScript, PDF) viewer - debugging symbols
 evince - Document (PostScript, PDF) viewer
 evince-gtk - Document (PostScript, PDF) viewer (GTK+ version)
 gir1.2-evince-3.0 - GObject introspection data for the evince libraries
 libevdocument3-4 - Document (PostScript, PDF) rendering library
 libevince-dev - Document (PostScript, PDF) rendering library - development 
files
 libevview3-3 - Document (PostScript, PDF) rendering library - Gtk+ widgets
Changes:
 evince (3.14.1-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Chris Kuehl ]
   * Add debian/patches/revert-69b474fce1.patch (Closes: #768133)
 - from upstream git, reverts commit which broke landscape printing
Checksums-Sha1: 
 82da3ab2fd1a0a0ad4b80d03297efa26a99668b7 2182688 evince-common_3.14.1-2_all.deb
 c1e8b4a77fb67591aa8aa214d6489ce80dad64f0 3080 evince_3.14.1-2.dsc
 d467dbe2c9fa839a0d11a5cf6a234459b5153f98 24844 evince_3.14.1-2.debian.tar.xz
Checksums-Sha256: 
 5da2a514a0ee9000d84e63cfb5204e1e174bb5562f3fb16a5169281418410406 2182688 
evince-common_3.14.1-2_all.deb
 37e9ba3cfa7ee03808f1858dba9a3df84351ea02f94f3747e61876627f0b8b0f 3080 
evince_3.14.1-2.dsc
 317a30632553e65ee5165d1b3da49870255ab6de3a8b4a79cad124b78152e07b 24844 
evince_3.14.1-2.debian.tar.xz
Files: 
 4b7fb7d74ab864b4da4805e95e28d485 2182688 gnome o

Bug#779717: marked as done (FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file)

[Debian Bug Tracking System]

Your message dated Fri, 06 Mar 2015 09:39:43 +
with message-id 
and subject line Bug#779717: fixed in chromium-browser 41.0.2272.76-2
has caused the Debian Bug report #779717,
regarding FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file
to be marked as done.

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

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


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

$ chromium
[0304/210821:FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 41.0.2272.76-2

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
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: Fri, 06 Mar 2015 00:59:50 +
Source: chromium-browser
Binary: chromium chromium-dbg chromium-l10n chromium-inspector chromedriver
Architecture: source i386 all
Version: 41.0.2272.76-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Maintainers 

Changed-By: Michael Gilbert 
Description:
 chromedriver - web browser - WebDriver support
 chromium   - web browser
 chromium-dbg - web browser - debugging symbols
 chromium-inspector - web browser - page inspection support
 chromium-l10n - web browser - language packs
Closes: 779717
Changes:
 chromium-browser (41.0.2272.76-2) unstable; urgency=medium
 .
   * Install v8 natives and snapshot blob files (closes: #779717).
 - Thanks to Jason Rhinelander.
Checksums-Sha1:
 71b192da3dada19fd7a2f9869af8deded901a971 4032 
chromium-browser_41.0.2272.76-2.dsc
 d3868d8228c75bf5e7398a210fa8b2d3aade31ce 178088 
chromium-browser_41.0.2272.76-2.debian.tar.xz
 1d7b097c6a1810277691d75fdd66250760f26535 38331648 
chromium_41.0.2272.76-2_i386.deb
 9ec5b7c6cb09d7f3691692e26d8d947be100707a 633098982 
chromium-dbg_41.0.2272.76-2_i386.deb
 c4c592775a5aad775bea7cce8a608ceb9b62ba35 3020894 
chromium-l10n_41.0.2272.76-2_all.deb
 10c4cad10d155b2796d5e5676b4d1377166cc40f 861932 
chromium-inspector_41.0.2272.76-2_all.deb
 dad625ad2c2d0b33471c77b2d187ecd07f78ee20 2109146 
chromedriver_41.0.2272.76-2_i386.deb
Checksums-Sha256:
 0961b91ef64f4cb802090be39c51b438be2d9959f8a933fe2ac2bab056f8520b 4032 
chromium-browser_41.0.2272.76-2.dsc
 6e75e9ad354590b66869b7f5f5061921b7f951450caae8185d6e3de6f9933c7a 178088 
chromium-browser_41.0.2272.76-2.debian.tar.xz
 85fccddc6f1b4c3c2b0e87cf8a96915454cad58ff07c99634aa69f0d508d7be2 38331648 
chromium_41.0.2272.76-2_i386.deb
 0f8ecf1e689d778dec07d2e7d97e9f1e7b0b5a4d27bb83aeaa94387aac086101 633098982 
chromium-dbg_41.0.2272.76-2_i386.deb
 8f4771022327dc4b03cd1a49d0e08927ad671851762f14349522b28f27902585 3020894 
chromium-l10n_41.0.2272.76-2_all.deb
 95051c69796b8069a71f6ed431c4ce170c7959a2af169ebcd6c9194d95d776f8 861932 
chromium-inspector_41.0.2272.76-2_all.deb
 36d119b514ce384f8e5097389c631ddaf9011816ada669d1a6fbb9b652243485 2109146 
chromedriver_41.0.2272.76-2_i386.deb
Files:
 c62c93cb88a4c272b73626103cc222a1 4032 web optional 
chromium-browser_41.0.2272.76-2.dsc
 598872fc33ae1cfd2ad3bc5973823b48 178088 web optional 
chromium-browser_41.0.2272.76-2.debian.tar.xz
 527b575f94f6d4b9c8a007d9f58b2d14 38331648 web optional 
chromium_41.0.2272.76-2_i386.deb
 18ef20da0beba4690a77e2d3145418b2 633098982 debug extra 
chromium-dbg_41.0.2272.76-2_i386.deb
 db389930e8841348d24d7fd5db553eab 3020894 localization optional 
chromium-l10n_41.0.2272.76-2_all.deb
 bc64be40b5ba2b725fce4395006f91ee 861932 web optional 
chromium-inspector_41.0.2272.76-2_all.deb
 573bc2614d2b84dc50afed97804f961f 2109146 web optional 
chromedriver_41.0.2272.76-2_i386.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQQcBAEBCgAGBQJU+RSqAAoJELjWss0C1vRzG8QgAJFHD+B/37bXyA26awsDHwXK
e6SDA4aechWEG1Hvieso9nH5APsm7w2g9D/2j1YBqnUzI1RKK0DoWIGocCAQ6+eP
3gPBU3MwoisSVLhqR22/8OQJAfPKogprcST6nuZjdmJBnXgfNdyhp6NLQCR8ayzg
uNMjXU2andV5kj2jY

Bug#779717: FATAL:isolate_holder.cc(70)] Couldn't mmap v8 natives data file

[Sergio Fernández]

Jason, could you please put the unofficial package somewhere to test it?

-- 
Sergio Fernández
http://www.wikier.org


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

Processed: Re: Bug#779902: /tmp can be mounted as tmpfs against user's will

[Debian Bug Tracking System]

Processing control commands:

> found -1 215-12
Bug #779902 [systemd] /tmp can be mounted as tmpfs against user's will
Marked as found in versions systemd/215-12.
> tag -1 confirmed
Bug #779902 [systemd] /tmp can be mounted as tmpfs against user's will
Added tag(s) confirmed.

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


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

Bug#779902: /tmp can be mounted as tmpfs against user's will

[Martin Pitt]

Control: found -1 215-12
Control: tag -1 confirmed

Ça va Didier,

Didier Roche [2015-03-06  9:36 +0100]:
> In debian, tmp.mount is disabled through a distro-patch by default. It means
> we don't want user's system to get /tmp on tmpfs without explicit enablement
> (either by enabling tmp.mount unit or via fstab).
> 
> We noticed that starting an unit using "PrivateTmp=yes" will pull tmp.mount
> (which mounts /tmp on tmpfs) in its requirements chain (even if this unit is
> condition fail).

Confirmed. "systemctl start colord" or "systemd-timesyncd" will start
tmp.mount and thus overmount the existing /tmp in the running system.
I reproduced that in a clean sid VM (with LXDE, but I suppose that
doesn't matter much).

> We need to find a way to ensure that tmp.mount is never accidentally
> trigger, while still enabling the user using fstab to enable /tmp as tmpfs.
> Enabling the unit to get the same effect would be a nice addition.

I dislike masking it, as that will most probalby lead to problems with
units which have a Requires=tmp.mount (directly or indirectly), these
would block on a masked unit.

I think the best way forward is to either not ship the unit at all and
document in README.Debian to add /tmp as tmpfs in fstab [1], or ship
it in /usr/share/doc/systemd/ as an example, and document how to
enable it from there.

Michael, WDYT?

Thanks,

Martin

[1] I have "none /tmp tmpfs defaults 0 0" in fstab
-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)


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

Bug#779902: /tmp can be mounted as tmpfs against user's will

[Didier Roche]

Package: systemd
Severity: serious

In debian, tmp.mount is disabled through a distro-patch by default. It 
means we don't want user's system to get /tmp on tmpfs without explicit 
enablement (either by enabling tmp.mount unit or via fstab).


We noticed that starting an unit using "PrivateTmp=yes" will pull 
tmp.mount (which mounts /tmp on tmpfs) in its requirements chain (even 
if this unit is condition fail).

For instance:
systemctl show -p Requires -p RequiresMountsFor systemd-timesyncd.service
Requires=-.mount tmp.mount
RequiresMountsFor=/var/lib/systemd/clock /tmp /var/tmp

Note that multiple units are using the private tmp feature like cups.

Also, if the unit is restarted (like an upgrade involving cups), /tmp 
will as well be remounted as tmpfs, which can wipe /tmp content to new 
process and get some annoying side-effects.



We need to find a way to ensure that tmp.mount is never accidentally 
trigger, while still enabling the user using fstab to enable /tmp as 
tmpfs. Enabling the unit to get the same effect would be a nice addition.

Processed: Re: Bug#776683: snmpd: SNMPd still tries to query PCI Bus

[Debian Bug Tracking System]

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

> severity 776683 normal
Bug #776683 [snmpd] snmpd: SNMPd still tries to query PCI Bus
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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


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