Processed: python-rsa: diff for NMU version 3.1.4-1.1
Processing control commands: > tags 804430 + patch Bug #804430 [src:python-rsa] python-rsa: FTBFS: ImportError: No module named unittest2 Added tag(s) patch. > tags 804430 + pending Bug #804430 [src:python-rsa] python-rsa: FTBFS: ImportError: No module named unittest2 Added tag(s) pending. -- 804430: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#804430: python-rsa: diff for NMU version 3.1.4-1.1
Control: tags 804430 + patch Control: tags 804430 + pending Dear maintainer, I've prepared an NMU for python-rsa (versioned as 3.1.4-1.1). and Regards. -- Dariusz Dwornikowski, Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 1.6.2 BTiCW | tel. +48 61 665 23 71 diff -Nru python-rsa-3.1.4/debian/changelog python-rsa-3.1.4/debian/changelog --- python-rsa-3.1.4/debian/changelog 2015-11-23 11:09:55.0 +0100 +++ python-rsa-3.1.4/debian/changelog 2015-11-24 08:48:39.0 +0100 @@ -1,3 +1,13 @@ +python-rsa (3.1.4-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Added python modules to Build-Depends (Closes: #804430) +- python-unittest2, python3-unittest2 +- python-asn1, python3-asn1 + * Added d/patches/fix_tests.patch fixing imports in tests + + -- Dariusz Dwornikowski Mon, 23 Nov 2015 17:24:51 +0100 + python-rsa (3.1.4-1) unstable; urgency=medium * New upstream release diff -Nru python-rsa-3.1.4/debian/control python-rsa-3.1.4/debian/control --- python-rsa-3.1.4/debian/control 2015-11-23 11:09:55.0 +0100 +++ python-rsa-3.1.4/debian/control 2015-11-24 08:47:03.0 +0100 @@ -8,6 +8,10 @@ , python3-all , python-setuptools , python3-setuptools + , python-unittest2 + , python3-unittest2 + , python3-pyasn1 + , python-pyasn1 Standards-Version: 3.9.5 Homepage: http://stuvel.eu/rsa X-Python-Versioni: >= 2.7 diff -Nru python-rsa-3.1.4/debian/patches/fix_tests.patch python-rsa-3.1.4/debian/patches/fix_tests.patch --- python-rsa-3.1.4/debian/patches/fix_tests.patch 1970-01-01 01:00:00.0 +0100 +++ python-rsa-3.1.4/debian/patches/fix_tests.patch 2015-11-24 08:49:49.0 +0100 @@ -0,0 +1,26 @@ +Subject: Fixes import of constants in tests +Author: Dariusz Dwornikowski +Forwarded: no +Last-Update: 2015-11-24 +--- a/tests/test_strings.py b/tests/test_strings.py +@@ -6,7 +6,7 @@ + + import rsa + +-from constants import unicode_string ++from tests.constants import unicode_string + + class StringTest(unittest2.TestCase): + +--- a/tests/constants.py b/tests/constants.py +@@ -3,7 +3,7 @@ + from rsa._compat import have_python3 + + if have_python3: +-from py3kconstants import * ++from tests.py3kconstants import * + else: + from py2kconstants import * + diff -Nru python-rsa-3.1.4/debian/patches/series python-rsa-3.1.4/debian/patches/series --- python-rsa-3.1.4/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ python-rsa-3.1.4/debian/patches/series 2015-11-24 08:42:02.0 +0100 @@ -0,0 +1 @@ +fix_tests.patch signature.asc Description: PGP signature
Bug#805156: libstoragemgmt: FTBFS: failed to find required module pywbem
On Mon, 2015-11-23 at 19:49 +0100, Kurt Roeckx wrote: > > It still fails on some arches like sparc64 and x32. I'm guessing > some build-depedency still didn't get fixed there. I think it is the python-m2crypto library, which python-pywbem depends on. The failing architectures have an older version of the library. -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." signature.asc Description: This is a digitally signed message part
Bug#805926: GNOME GMail broken on Jessie
Package: gnome-gmail Version: 1.8.3-1 Severity: grave The gnome-gmail package is broken in Jessie for a couple of reasons.First, IMAP authentication, which used for file attachments, now requires OAuth2 authentication. OAuth2 support was first added in 1.9-1. Second, access to configuration settings is broken for a fresh Jessie install. Version 1.8.3 still used GNOME 2's gconf for configuration data. Later versions of gnome-gmail, through at least 1.9.3, resolve these problems and retain compatibility with Jessie. -- "Le mieux est l'ennemi du bien" - Voltaire
Bug#804840: marked as done (stormbaancoureur: FTBFS: No rule to make target '/usr/lib/libode.a')
Your message dated Tue, 24 Nov 2015 03:38:25 + with message-id and subject line Bug#804840: fixed in stormbaancoureur 2.1.6-1.1 has caused the Debian Bug report #804840, regarding stormbaancoureur: FTBFS: No rule to make target '/usr/lib/libode.a' 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.) -- 804840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: stormbaancoureur Version: 2.1.6-1 Severity: serious Control: block 804285 by -1 On a rebuild against the new ode, your package failed to build with: make[1]: *** No rule to make target '/usr/lib/libode.a', needed by 'stormbaancoureur'. Stop. Full logs at: https://buildd.debian.org/status/logs.php?pkg=stormbaancoureur&ver=2.1.6-1%2Bb1 Emilio --- End Message --- --- Begin Message --- Source: stormbaancoureur Source-Version: 2.1.6-1.1 We believe that the bug you reported is fixed in the latest version of stormbaancoureur, 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 804...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Bombe (supplier of updated stormbaancoureur package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 22 Nov 2015 18:38:09 +0100 Source: stormbaancoureur Binary: stormbaancoureur stormbaancoureur-data Architecture: source all amd64 Version: 2.1.6-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Andreas Bombe Description: stormbaancoureur - simulated obstacle course for automobiles stormbaancoureur-data - game data for Stormbaan Coureur Closes: 804840 Changes: stormbaancoureur (2.1.6-1.1) unstable; urgency=medium . * Non-maintainer upload. * Remove remaining hard coded libode paths from Makefile including a prerequisite on a system installed library with wrong path (Closes: #804840) Checksums-Sha1: 25c87820bf045b20d4841ebb3028460857f51c1c 2281 stormbaancoureur_2.1.6-1.1.dsc 1504ba1cb551619aee0462535cb9839dcbd98cb1 13679 stormbaancoureur_2.1.6-1.1.diff.gz 919b8a8381420c1a213c642b0b263dfcb6388f4c 2797926 stormbaancoureur-data_2.1.6-1.1_all.deb 460ae2d708bcefd65d19179a7423227f97165f5b 82124 stormbaancoureur_2.1.6-1.1_amd64.deb Checksums-Sha256: 510b70ecd17263c9e05c92cd8da17eace7389ae6079a775685334d435a3956df 2281 stormbaancoureur_2.1.6-1.1.dsc 4f2e375c4262fc9561b865997c32f400ade448fafd392ac98a1d6c756ef3aaba 13679 stormbaancoureur_2.1.6-1.1.diff.gz aa00def1c7b3515f49e236122855c37fbc94400cf9f5005973ce5cc885d3b8ce 2797926 stormbaancoureur-data_2.1.6-1.1_all.deb 9f9d5a181c78c78c8b5353bd8e458e60b24316ea8820c595776b77d27f56e3ab 82124 stormbaancoureur_2.1.6-1.1_amd64.deb Files: 5dc9144ec8094297e665c1b556b4ecb2 2281 games extra stormbaancoureur_2.1.6-1.1.dsc 44c2382e3a6593d8249ed0cc3d0b3cc2 13679 games extra stormbaancoureur_2.1.6-1.1.diff.gz 77c763c51ed25b36c1181f2d17c305d0 2797926 games extra stormbaancoureur-data_2.1.6-1.1_all.deb 93b55d8c54dfaf058bf62ad14bea05e6 82124 games extra stormbaancoureur_2.1.6-1.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJWUf6rAAoJEDFkcFsdox1MJfEQAJ2h8XPi5gS+x5rPfk8ki8mO t7TzXp4nNxPDAho5QIttQMrf8FpfgMq+i4v+XG3kaL/63n9UyLfoOYsDOzaOPq8u fLG/Ypc4URRkfNcq8wfSVgy+RoCG2MbuJ4cLQWL5BZiN929Kg4HrwmTpyoPxwKFa cfw3Tsr4jaD4nDqVHsUNFUbv3gaY7/26DBXp+O6P/5Ydl3AJXw1l4fnnAiiz3vnv ie0A30XEK3p/twTSPaiZL9ZoLUT0G0poCGEZapAexRuMSMfShdXB4h79HFbr3FeA JbKp8+NUm4uVcw0Z7PNWfD/SJ0XOyFIHta9tTaIJ+cX/jiAZMSLy3zF6CA86vxx2 TY+AjlPUsd/ZeRXmgen26vgKOSxhK/5h48XGTm+dT9s3noKLS5/+8wmNcGkwt67v Aork/Py9qdUXfSvlLci/8ZrTv0Os9bHG8oAmtSdGNUzluyf7uny0cGiSlLqM9IbD PLQrgKzUNBJo7y2jUgxoE4YALvSAxUf9oi8UHuW/QsXWOjZ9a4F5BHhO0w9C8LGj TzMcEYtoF8aweFiFC+nJ9i7GaneWQ5wxIdUywyjfuJzrvRNC9BY7mP6G6UScqNzU nhudaXRGNq3ozq6UpZ1nUza7zuUsOP9H7FR/vPRfE9PhVikt+u9Zb7VJibbX2GAY m2GEMfMJk1fukjuS7Rv9 =c+PJ -END PGP SIGNATURE End Message ---
Bug#805863: gnutls28: FTBFS on amd64 - testsuite failures
Hi, On Mon, 2015-11-23 at 20:11 +0100, Andreas Metzler wrote: > On 2015-11-23 James Cowgill wrote: > > Source: gnutls28 > > Version: 3.3.19-1 > > Severity: serious > > > Hi, > > > The latest upload of gnutls28 failed to build on amd64 (but build > > sucessfully elsewhere). This failure also looks similar to the FTBFS of > > 3.4.7-1 in experimental. > [...] > > Can you reproduce this? I yesterday had a successful build on up to > date sid. Yes I can reproduce this, although only the x509-auth.scm test failed for me. There also seems to be a slight random factor since it doesn't fail all of the time if I repeatedly run that test within the chroot :/ James signature.asc Description: This is a digitally signed message part
Bug#804183: upgrade to 1.10.4-1 creates circular inclusion
On Tue, 2015-11-24 at 01:13 +, Simon McVittie wrote:
> On 23/11/15 20:11, Brent S. Elmer Ph.D. wrote:
> > My system may have been in an odd state due to this bug causing the
> > 1.10.4-1 upgrade to perpetuate the circular dependency. How do I
> > get
> > my system to a good state again?
>
> Before doing anything to try to solve it, please show me the output
> of:
>
> ls -la /etc/dbus-1/
>
> Ideally, what you want (with uninteresting date/ownership/size
> columns
> removed to avoid linewrapping) is something like this:
>
> drwxr-xr-x [...] .
> drwxr-xr-x [...] ..
> lrwxrwxrwx [...] session.conf -> /usr/share/dbus-1/session.conf
> drwxr-xr-x [...] session.d
> lrwxrwxrwx [...] system.conf -> /usr/share/dbus-1/system.conf
> drwxr-xr-x [...] system.d
>
> *.dpkg-{dist,old,new} files are also OK. *.dpkg-bak are OK but only
> if
> they are real files, not if they are symlinks into /usr/share/dbus-
> 1/;
> if in doubt, rename them out of the way.
>
> If /etc/dbus-1/s*.conf.bak is a symlink into /usr/share/dbus-1/,
> delete
> that symlink.
>
> For completeness, also check that /usr/share/dbus-1/session.conf and
> /usr/share/dbus-1/system.conf are real files, not symlinks. If not,
> move
> them out of the way, then reinstall dbus (something like "sudo dpkg
> -i
> /var/cache/apt/archives/dbus_1.10.4-1_*.deb" should work).
>
> Having reached a stable state, "sudo service dbus reload" should
> work.
> Please substitute your favourite way of running things as root if
> that
> isn't sudo.
>
> I'm reluctant to add any additional workarounds in the dbus package
> to
> try to sort out your system automatically, because the bad situation
> could only be hit by downgrading (which is unsupported anyway), and
> the
> more special-case code I add to the maintainer scripts, the more
> likely
> it is that I'll accidentally cause some regression for someone else.
>
> S
>
$ ls -la /etc/dbus-1/
total 32
drwxr-xr-x 4 root root 4096 Nov 23 13:56 .
drwxr-xr-x 163 root root 12288 Nov 23 13:57 ..
lrwxrwxrwx 1 root root30 Nov 23 13:56 session.conf ->
/usr/share/dbus-1/session.conf
lrwxrwxrwx 1 root root30 Nov 3 13:23 session.conf.dpkg-bak ->
/usr/share/dbus-1/session.conf
-rw-r--r-- 1 root root 828 Sep 15 17:09 session.conf.dpkg-new
drwxr-xr-x 2 root root 4096 May 27 17:12 session.d
lrwxrwxrwx 1 root root29 Nov 23 13:56 system.conf ->
/usr/share/dbus-1/system.conf
lrwxrwxrwx 1 root root29 Nov 3 13:23 system.conf.dpkg-bak ->
/usr/share/dbus-1/system.conf
-rw-r--r-- 1 root root 823 Sep 15 17:09 system.conf.dpkg-new
drwxr-xr-x 2 root root 4096 Nov 23 13:57 system.d
Bug#804183: upgrade to 1.10.4-1 creates circular inclusion
On 23/11/15 20:11, Brent S. Elmer Ph.D. wrote:
> My system may have been in an odd state due to this bug causing the
> 1.10.4-1 upgrade to perpetuate the circular dependency. How do I get
> my system to a good state again?
Before doing anything to try to solve it, please show me the output of:
ls -la /etc/dbus-1/
Ideally, what you want (with uninteresting date/ownership/size columns
removed to avoid linewrapping) is something like this:
drwxr-xr-x [...] .
drwxr-xr-x [...] ..
lrwxrwxrwx [...] session.conf -> /usr/share/dbus-1/session.conf
drwxr-xr-x [...] session.d
lrwxrwxrwx [...] system.conf -> /usr/share/dbus-1/system.conf
drwxr-xr-x [...] system.d
*.dpkg-{dist,old,new} files are also OK. *.dpkg-bak are OK but only if
they are real files, not if they are symlinks into /usr/share/dbus-1/;
if in doubt, rename them out of the way.
If /etc/dbus-1/s*.conf.bak is a symlink into /usr/share/dbus-1/, delete
that symlink.
For completeness, also check that /usr/share/dbus-1/session.conf and
/usr/share/dbus-1/system.conf are real files, not symlinks. If not, move
them out of the way, then reinstall dbus (something like "sudo dpkg -i
/var/cache/apt/archives/dbus_1.10.4-1_*.deb" should work).
Having reached a stable state, "sudo service dbus reload" should work.
Please substitute your favourite way of running things as root if that
isn't sudo.
I'm reluctant to add any additional workarounds in the dbus package to
try to sort out your system automatically, because the bad situation
could only be hit by downgrading (which is unsupported anyway), and the
more special-case code I add to the maintainer scripts, the more likely
it is that I'll accidentally cause some regression for someone else.
S
Bug#805917: marked as done (nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input)
Your message dated Tue, 24 Nov 2015 00:49:11 +
with message-id
and subject line Bug#805917: fixed in nvidia-graphics-drivers 352.63-1
has caused the Debian Bug report #805917,
regarding nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input
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.)
--
805917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Version: 304.22-1
Severity: serious
Tags: security
http://nvidia.custhelp.com/app/answers/detail/a_id/3808
http://people.canonical.com/~ubuntu-security/cve/2015/CVE-2015-7869.html
[...] This report also details an advisory regarding integer overflow issues
in the underlying kernel mode driver.
[...] The integer overflow issues affect both Windows and Linux-based GPU
drivers. These issues affect all GPU products and are not specific to
any GPU class device.
Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 352.63-1
We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 805...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann (supplier of updated nvidia-graphics-drivers
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 24 Nov 2015 01:32:50 +0100
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin xserver-xorg-video-nvidia
libgl1-nvidia-glx libgl1-nvidia-glx-i386 libegl1-nvidia libgles1-nvidia
libgles2-nvidia libnvidia-eglcore nvidia-alternative nvidia-kernel-support
nvidia-kernel-dkms nvidia-kernel-source nvidia-vdpau-driver nvidia-smi
nvidia-cuda-mps libcuda1 libcuda1-i386 libnvidia-compiler libnvcuvid1
libnvidia-encode1 libnvidia-ifr1 libnvidia-fbc1 libnvidia-ml1
nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1 nvidia-detect
Architecture: source
Version: 352.63-1
Distribution: experimental
Urgency: medium
Maintainer: Debian NVIDIA Maintainers
Changed-By: Andreas Beckmann
Description:
libcuda1 - NVIDIA CUDA Driver Library
libcuda1-i386 - NVIDIA CUDA 32-bit runtime library${nvidia:LegacyDesc}
libegl1-nvidia - NVIDIA binary EGL libraries${nvidia:LegacyDesc}
libgl1-nvidia-glx - NVIDIA binary OpenGL libraries${nvidia:LegacyDesc}
libgl1-nvidia-glx-i386 - NVIDIA binary OpenGL 32-bit
libraries${nvidia:LegacyDesc}
libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x libraries${nvidia:LegacyDesc}
libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x libraries${nvidia:LegacyDesc}
libnvcuvid1 - NVIDIA CUDA Video Decoder runtime library
libnvidia-compiler - NVIDIA runtime compiler library
libnvidia-eglcore - NVIDIA binary EGL core libraries${nvidia:LegacyDesc}
libnvidia-encode1 - NVENC Video Encoding runtime library
libnvidia-fbc1 - NVIDIA OpenGL-based Framebuffer Capture runtime library
libnvidia-ifr1 - NVIDIA OpenGL-based Inband Frame Readback runtime library
libnvidia-ml1 - NVIDIA Management Library (NVML) runtime library
nvidia-alternative - allows the selection of NVIDIA as GLX provider
nvidia-cuda-mps - NVIDIA CUDA Multi Process Service (MPS)
nvidia-detect - NVIDIA GPU detection utility
nvidia-driver - NVIDIA metapackage${nvidia:LegacyDesc}
nvidia-driver-bin - NVIDIA driver support binaries${nvidia:LegacyDesc}
nvidia-kernel-dkms - NVIDIA binary kernel module DKMS
source${nvidia:LegacyDesc}
nvidia-kernel-source - NVIDIA binary kernel module source${nvidia:LegacyDesc}
nvidia-kernel-support - NVIDIA binary kernel module support
files${nvidia:LegacyDesc}
nvidia-libopencl1 - NVIDIA OpenCL ICD Loader library
nvidia-opencl-common - NVIDIA OpenCL driver
nvidia-opencl-icd - NVIDIA OpenCL installable client driver (ICD)
nvidia-smi - NVIDIA System Management Interface
nvidia-vdpau-driver - Video Decode and Presentation API for Unix - NVIDIA
driver
xserver-xorg-video-nvidia - NVIDIA binary Xorg driver${nvidia:LegacyDesc}
Closes: 805917
Changes:
nvidia-graphics-drivers (352.63-1) experimental; urgency=medium
.
* New upstream long lived branch release 3
Processed: found 805917 in 310.14-1, found 805917 in 340.24-1, found 805917 in 343.22-1 ..., cloning 805917 ...
Processing commands for cont...@bugs.debian.org: > found 805917 310.14-1 Bug #805917 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Marked as found in versions nvidia-graphics-drivers/310.14-1. > found 805917 340.24-1 Bug #805917 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Marked as found in versions nvidia-graphics-drivers/340.24-1. > found 805917 343.22-1 Bug #805917 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Marked as found in versions nvidia-graphics-drivers/343.22-1. > found 805917 352.21-1 Bug #805917 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Marked as found in versions nvidia-graphics-drivers/352.21-1. > fixed 805917 340.96-2 Bug #805917 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Marked as fixed in versions nvidia-graphics-drivers/340.96-2. > clone 805917 -1 -2 Bug #805917 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Bug 805917 cloned as bugs 805918-805919 > reassign -1 src:nvidia-graphics-drivers-legacy-304xx 304.108-2 Bug #805918 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Bug reassigned from package 'src:nvidia-graphics-drivers' to 'src:nvidia-graphics-drivers-legacy-304xx'. No longer marked as found in versions nvidia-graphics-drivers/340.24-1, nvidia-graphics-drivers/343.22-1, nvidia-graphics-drivers/310.14-1, nvidia-graphics-drivers/352.21-1, and nvidia-graphics-drivers/304.22-1. No longer marked as fixed in versions nvidia-graphics-drivers/340.96-2. Bug #805918 [src:nvidia-graphics-drivers-legacy-304xx] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Marked as found in versions nvidia-graphics-drivers-legacy-304xx/304.108-2. > retitle -1 nvidia-graphics-drivers-legacy-304xx: CVE-2015-7869: Unsanitized > User Mode Input Bug #805918 [src:nvidia-graphics-drivers-legacy-304xx] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Changed Bug title to 'nvidia-graphics-drivers-legacy-304xx: CVE-2015-7869: Unsanitized User Mode Input' from 'nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input' > reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6 Bug #805919 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Bug reassigned from package 'src:nvidia-graphics-drivers' to 'src:nvidia-graphics-drivers-legacy-340xx'. No longer marked as found in versions nvidia-graphics-drivers/304.22-1, nvidia-graphics-drivers/352.21-1, nvidia-graphics-drivers/340.24-1, nvidia-graphics-drivers/310.14-1, and nvidia-graphics-drivers/343.22-1. No longer marked as fixed in versions nvidia-graphics-drivers/340.96-2. Bug #805919 [src:nvidia-graphics-drivers-legacy-340xx] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Marked as found in versions nvidia-graphics-drivers-legacy-340xx/340.76-6. > retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2015-7869: Unsanitized > User Mode Input Bug #805919 [src:nvidia-graphics-drivers-legacy-340xx] nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input Changed Bug title to 'nvidia-graphics-drivers-legacy-340xx: CVE-2015-7869: Unsanitized User Mode Input' from 'nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input' > thanks Stopping processing here. Please contact me if you need assistance. -- 805917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805917 805918: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805918 805919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#805917: nvidia-graphics-drivers: CVE-2015-7869 Unsanitized User Mode Input
Source: nvidia-graphics-drivers Version: 304.22-1 Severity: serious Tags: security http://nvidia.custhelp.com/app/answers/detail/a_id/3808 http://people.canonical.com/~ubuntu-security/cve/2015/CVE-2015-7869.html [...] This report also details an advisory regarding integer overflow issues in the underlying kernel mode driver. [...] The integer overflow issues affect both Windows and Linux-based GPU drivers. These issues affect all GPU products and are not specific to any GPU class device. Andreas
Bug#797087: marked as done (debian-design: FTBFS: "reclass" unexpectedly returned exit value 7)
Your message dated Mon, 23 Nov 2015 22:48:50 + with message-id and subject line Bug#797087: fixed in debian-design 3.0.1 has caused the Debian Bug report #797087, regarding debian-design: FTBFS: "reclass" unexpectedly returned exit value 7 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.) -- 797087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debian-design Version: 3 Severity: serious Tags: sid stretch Justification: FTBFS This package FTBFS in a clean sid chroot: cd content/desktop/animation/ \ && boxer compose \ --nodedir /«PKGBUILDDIR»/nodes \ --skeldir /«PKGBUILDDIR»/skel \ --suite jessie \ desktop-animation Class 'Admin.apt.aptitude' (in ancestry of node './desktop-animation') not found under yaml_fs:///usr/share/boxer/jessie/classes Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/reclass/storage/yaml_fs/__init__.py", line 93, in get_class path = os.path.join(self.classes_uri, self._classes[name]) KeyError: 'Admin.apt.aptitude' "reclass" unexpectedly returned exit value 74 at (eval 168) line 12. at /usr/share/perl5/Boxer/Task/Classify.pm line 69 make[1]: *** [content/desktop/animation/preseed.cfg] Error 74 Makefile:17: recipe for target 'content/desktop/animation/preseed.cfg' failed make[1]: Leaving directory '/«PKGBUILDDIR»' make: *** [content/desktop/preseed.cfg] Error 2 Cheers, Dominic. --- End Message --- --- Begin Message --- Source: debian-design Source-Version: 3.0.1 We believe that the bug you reported is fixed in the latest version of debian-design, 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 797...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated debian-design 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, 23 Nov 2015 23:03:53 +0100 Source: debian-design Binary: design-data design-desktop design-desktop-graphics design-desktop-animation design-desktop-web design-desktop-strict Architecture: source all Version: 3.0.1 Distribution: unstable Urgency: medium Maintainer: Debian Design Team Changed-By: Jonas Smedegaard Description: design-data - recipes to install Debian Design blends design-desktop - Debian Design desktop for visual designers - common parts design-desktop-animation - Debian Design desktop for animation designers design-desktop-graphics - Debian Design desktop for graphics designers design-desktop-strict - Debian Design desktop for visual designers - strict design-desktop-web - Debian Design desktop for web designers Closes: 797087 Changes: debian-design (3.0.1) unstable; urgency=medium . * Update skeleton files to support boxer 4+ format. Build-depend on recent boxer. Closes: Bug#797087. Thanks to Dominic Hargreaves. * Update node files to support boxer-data 7+ classes. * Use boxer-data 10.3 classes. Package design-desktop: + Include more GTK+ office tools, Xfce components, and audio tools. + Include popularity-contest. Package design-desktop-graphics: + Include more font tools, image optimizers, and PDF tools. Package design-desktop-strict: + Avoid xfce4-mixer. + Avoid fewer LibreOffice components. * Update TODOs: + Maybe include of KDE-base Krita. Thanks to Martin Steigerwald. + Maybe add font design blend. + Check murrine-themes/QtGTKStyle bug. + Include nodes in -data package when skel tweaks are upstreamed. * Ignore quote-escaped newline 'foo\''n'bar' pattern in testsuite. Checksums-Sha1: 6d83a84f7107bd2e7badf3153063cc2bf4ca85eb 2062 debian-design_3.0.1.dsc 29654941468da7bf2b505f79295d18114bd49ae9 5520 debian-design_3.0.1.tar.xz c579e99e93186a687db958424ba887b625a24c94 11840 design-data_3.0.1_all.deb 4de7ad2a313756f060b1557bfc91fafac4490ed9 6796 design-desktop-animation_3.0.1_all.deb c73b494e35bd8cd23824610b5677b5b54cbee723 7018 design-desktop-graphics_3.0.1_all.deb 8f1b8cf65438300d69c6b50e16e05ac65fd91fbe 6908 design-desktop-
Bug#800170: marked as done (funnelweb-doc: Please migrate a supported debhelper compat level)
Your message dated Mon, 23 Nov 2015 22:18:59 +
with message-id
and subject line Bug#800170: fixed in funnelweb-doc 3.2d-4
has caused the Debian Bug report #800170,
regarding funnelweb-doc: Please migrate a supported debhelper compat level
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.)
--
800170: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: funnelweb-doc
Severity: important
Usertags: deprecated-debhelper-compat-leq-3
Hi,
The package funnelweb-doc is using a debhelper compat level of 3 or less
according to lintian. These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).
* Please migrate the package to a supported debhelper compat level.
- Compat 9 is recommended
- Compat 5 is the bare minimum (compat 4 will be removed soon as
well)
* If your package uses any of the following tools, please remove them
from the rules files. Neither of them does anything except warn
about their deprecation.
- dh_desktop
- dh_scrollkeeper (deadline: January 1st 2016)
- dh_suidregister
- dh_undocumented
* Please note that your package might have been flagged for using
e.g. "DH_COMPAT=2 dh_foo ...".
- This will still cause issues when the compat level is removed.
* If the package has been relying on dh_install being lenient about
missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].
* Deadline:
- compat 1+2: November 1st 2015
- compat 3: January 1st 2016
If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.
Thanks,
~Niels
[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: funnelweb-doc
Source-Version: 3.2d-4
We believe that the bug you reported is fixed in the latest version of
funnelweb-doc, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 800...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yann Dirson (supplier of updated funnelweb-doc 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, 23 Nov 2015 22:56:49 +0100
Source: funnelweb-doc
Binary: funnelweb-doc
Architecture: source all
Version: 3.2d-4
Distribution: unstable
Urgency: medium
Maintainer: Yann Dirson
Changed-By: Yann Dirson
Description:
funnelweb-doc - Documentation for funnelweb
Closes: 354783 800170
Changes:
funnelweb-doc (3.2d-4) unstable; urgency=medium
.
* Switch to debhelper compat v9 (Closes: #800170).
* Use ${misc:Depends}.
* Rewrite debian/rules to use dh, with a special hack to cope with the
"binary" directory.
* Don't ship annoying background.gif, which is even either reported as
corrupt or just ignored by all tested programs (Closes: #354783).
* Removed "Apps/" component in doc-base section.
* Removed erroneous commas in doc-base file.
* Change section to "optional" to match archive override file.
* Bumped Standards-Version to 3.9.6.
Checksums-Sha1:
7d74ccc4bcaf109a2ff9fa30fb1fb62ac5189666 1665 funnelweb-doc_3.2d-4.dsc
d881ba6afb68e7213e197535bf712e3719aaa399 2805 funnelweb-doc_3.2d-4.diff.gz
8028a995e1ac79cb77baef1c9642750b2223112c 160076 funnelweb-doc_3.2d-4_all.deb
Checksums-Sha256:
6e0e2eab61b0042cb05069a20b100845d626da8625c05be918f150728f7cfa39 1665
funnelweb-doc_3.2d-4.dsc
a482f8359cb28c9a8acf2d62dc00686132a73785f772226cfdf5140e4e98a482 2805
funnelweb-doc_3.2d-4.diff.gz
ff8f5fb09b0f1122d1623cb757792fd9482814c18e509d89d285931b9a13079e 160076
funnelweb-doc_3.2d-4_all.deb
Files:
d4b593de24959c5cfa49d858fa90d0df 1665 doc optional funnelweb-doc_3.2d-4.dsc
5b2c0d1a95ade32a69fc1cb5ba37f43a 2805 doc optional funnelweb-doc_3.2d-4.diff.gz
a81f535a5ebf5e18cdc037d0724a5010 160076 doc optional
funnelweb-doc_3.2d-4_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIVAwUBVlOOhw2F8pYlo/n9AQjPfhAAty8wldxB6Rgw5hqHONe8nTC3v39oJh2o
+48xZJlORL01kDVLhLTXEATt77fJS5iPKGAVpQnpr4TLGZpqUWWWva8u19UCYQlw
0WY3xg4fqLpII
Bug#803439: marked as done (libzeroc-ice3.5-cil: fails to install: E: installing Assembly /usr/lib/cli/libzeroc-ice3.5/Ice.dll failed)
Your message dated Mon, 23 Nov 2015 22:19:51 + with message-id and subject line Bug#803439: fixed in zeroc-ice 3.5.1-6.3 has caused the Debian Bug report #803439, regarding libzeroc-ice3.5-cil: fails to install: E: installing Assembly /usr/lib/cli/libzeroc-ice3.5/Ice.dll failed to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 803439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libzeroc-ice3.5-cil Version: 3.5.1-6.2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): Selecting previously unselected package libzeroc-ice3.5-cil. (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 8847 files and directories currently installed.) Preparing to unpack .../libzeroc-ice3.5-cil_3.5.1-6.2_all.deb ... Unpacking libzeroc-ice3.5-cil (3.5.1-6.2) ... Setting up libzeroc-ice3.5-cil (3.5.1-6.2) ... * Installing 6 assemblies from libzeroc-ice3.5-cil into Mono E: installing Assembly /usr/lib/cli/libzeroc-ice3.5/Ice.dll failed E: Installation of libzeroc-ice3.5-cil with /usr/share/cli-common/runtimes.d/mono failed dpkg: error processing package libzeroc-ice3.5-cil (--configure): subprocess installed post-installation script returned error exit status 29 Errors were encountered while processing: libzeroc-ice3.5-cil cheers, Andreas libzeroc-ice3.5-cil_3.5.1-6.2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: zeroc-ice Source-Version: 3.5.1-6.3 We believe that the bug you reported is fixed in the latest version of zeroc-ice, 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 803...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christopher Knadle (supplier of updated zeroc-ice 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, 19 Nov 2015 20:35:26 -0500 Source: zeroc-ice Binary: zeroc-ice35 ice35-translators ice35-services libicestorm35v5 libicegrid35v5 libicebox35v5 icebox libicepatch2-35v5 libglacier2-35v5 libfreeze35v5 libicedb35v5 ice35-slice libzeroc-ice35v5 libicessl35v5 libiceutil35v5 libicexml35v5 libslice35v5 libzeroc-ice35-dev libzeroc-ice35-dbg python-zeroc-ice python3-zeroc-ice php-zeroc-ice libzeroc-ice3.5-cil ruby-zeroc-ice libzeroc-ice3.5-java icegrid-gui Architecture: source Version: 3.5.1-6.3 Distribution: unstable Urgency: medium Maintainer: Francisco Moya Changed-By: Christopher Knadle Closes: 791848 803439 Description: ice35-services - Services bundled into ZeroC Ice ice35-slice - Slice definitions for Ice services ice35-translators - Slice translators to several languages icebox - Plugin-based meta-application for ZeroC Ice icegrid-gui - GUI for IceGrid service libfreeze35v5 - Libraries implementing a persistence framework for ZeroC Ice libglacier2-35v5 - Libraries implementing a firewall service for ZeroC Ice libicebox35v5 - Libraries implementing a plugin framework for ZeroC Ice libicedb35v5 - Libraries for persistent backends for ZeroC Ice libicegrid35v5 - Libraries implementing grid-like services for ZeroC Ice libicepatch2-35v5 - Libraries implementing a distribution service for ZeroC Ice libicessl35v5 - Ice for C++ SSL plug-in libicestorm35v5 - Libraries implementing an event service for ZeroC Ice libiceutil35v5 - Ice for C++ misc utility library libicexml35v5 - ZeroC I
Bug#802976: Should this package be removed?
On Fri, Nov 13, 2015 at 07:38:41PM +0100, Thibaut Girka wrote: > Le 13 novembre 2015 18:42:55 CET, "Moritz Mühlenhoff" a > écrit : > >On Tue, Oct 27, 2015 at 03:32:17PM +0100, Thibaut Girka wrote: > >> On Sun, Oct 25, 2015 at 09:22:53PM +0100, Moritz Mühlenhoff wrote: > >> > On Sun, Oct 25, 2015 at 07:51:20PM +0100, Thibaut Girka wrote: > >> > > On Sun, Oct 25, 2015 at 07:41:29PM +0100, Moritz Muehlenhoff > >wrote: > >> > > > Package: bluemindo > >> > > > Severity: serious > >> > > > > >> > > > - Dead upstream (the current 0.3 release is from 2009) > >> > > > >> > > A new major version is on the way and should be released soon. > >> > > >> > Sounds good. Is there a rough timeline for that? > >> > >> It should be released in early november. > >> As for the package itself, I might start working on it during the > >> next weekend or so. > > > >Hi, > >has the new version been released? It's not on the website. > > Not yet. It's nearing release, but the developer is currently looking for > user feedback. An excellent way to gather user feedback is to upload it to the unstable development branch of a popular Linux distro :-) Cheers, Moritz
Bug#805664: golang-go.tools: FTBFS: code.google.com/p/go.net/html expects import "golang.org/x/net/html"
[+cc tianon, who touched this package most recently] [+cc paultag, for all things ftp master knowledge] I’m a bit confused by this report, I must say. I thought that with commit https://anonscm.debian.org/cgit/pkg-go/packages/golang-go.tools.git/commit/?id=b4ec506c6331c363e0ac9997e8e78a4c73e5f563 we had addressed any sort of weirdness with the old version, but this bug report is against version 0.0~hg20140703-4, which you shouldn’t be able to install on a testing/unstable system. On https://packages.qa.debian.org/g/golang-golang-x-tools.html, I also see: There were override disparities found in suite unstable: golang-go.tools-dev: Override says devel - extra, .deb says oldlibs - extra golang-go.tools: Override says devel - extra, .deb says oldlibs - extra Not sure if that’s related at all. Any hints as to what’s going on are appreciated. On Fri, Nov 20, 2015 at 9:00 PM, Chris West (Faux) < solo-debianb...@goeswhere.com> wrote: > Source: golang-go.tools > Version: 0.0~hg20140703-4 > Severity: serious > Justification: fails to build from source > Tags: sid > User: reproducible-bui...@lists.alioth.debian.org > Usertags: ftbfs > X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org > > Dear Maintainer, > > The package fails to build offline, such as on the builders: > > go install -v code.google.com/p/go [...] go.tools/refactor/eg > src/code.google.com/p/go.tools/cmd/html2article/conv.go:21:2: code in > directory /golang-go.tools-0.0~hg20140703/obj-x86_64-linux-gnu/src/ > code.google.com/p/go.net/html expects import "golang.org/x/net/html" > src/code.google.com/p/go.tools/cmd/html2article/conv.go:22:2: code in > directory /golang-go.tools-0.0~hg20140703/obj-x86_64-linux-gnu/src/ > code.google.com/p/go.net/html/atom expects import " > golang.org/x/net/html/atom" > src/code.google.com/p/go.tools/playground/socket/socket.go:38:2: code in > directory /golang-go.tools-0.0~hg20140703/obj-x86_64-linux-gnu/src/ > code.google.com/p/go.net/websocket expects import " > golang.org/x/net/websocket" > > Full build log: > https://reproducible.debian.net/rb-pkg/unstable/amd64/golang-go.tools.html > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > -- Best regards, Michael
Bug#805224: Overwrites config file
tags 805224 + upstream patch
forwarded 805224 https://github.com/wking/rss2email/pull/72
thanks
Hi Martin,
Thanks for reporting this bug. I informed upstream of this issue and
prepare a patch. I will upload a fixed version shortly.
Have a nice day!
--
Etienne Millon
From 6ce465dac257c29a9f43fe16fd3bafd6a383a445 Mon Sep 17 00:00:00 2001
From: Etienne Millon
Date: Mon, 23 Nov 2015 20:45:02 +0100
Subject: [PATCH] r2e new: do not overwrite existing config
Bug-Debian: https://bugs.debian.org/805224
Forwarded: https://github.com/wking/rss2email/pull/72
If a configuration file already exists, "r2e new" will overwrite it.
This was reported in the following bug report:
https://bugs.debian.org/805224
This adds a check when running "r2e new" that will exit if the configuration
file already exists.
Signed-off-by: Etienne Millon
---
rss2email/command.py | 2 ++
rss2email/error.py | 6 ++
rss2email/feeds.py | 3 +++
3 files changed, 11 insertions(+)
--- a/rss2email/command.py
+++ b/rss2email/command.py
@@ -31,6 +31,8 @@
if args.email:
_LOG.info('set the default target email to {}'.format(args.email))
feeds.config['DEFAULT']['to'] = args.email
+if feeds.configfile_exists():
+raise _error.ConfigAlreadyExistsError(feeds=feeds)
feeds.save()
def email(feeds, args):
--- a/rss2email/error.py
+++ b/rss2email/error.py
@@ -258,3 +258,9 @@
def __init__(self, **kwargs):
message = 'error reading OPML'
super(OPMLReadError, self).__init__(message=message, **kwargs)
+
+
+class ConfigAlreadyExistsError (FeedsError):
+def __init__(self, feeds=None):
+message = 'configuration file already exists'
+super().__init__(feeds=feeds, message=message)
--- a/rss2email/feeds.py
+++ b/rss2email/feeds.py
@@ -337,6 +337,9 @@
'cannot convert data file from version {} to {}'.format(
version, self.datafile_version))
+def configfile_exists(self):
+return _os.path.exists(self.configfiles[-1])
+
def save(self):
_LOG.debug('save feed configuration to {}'.format(self.configfiles[-1]))
for feed in self:
signature.asc
Description: Digital signature
Bug#805904: emacs24: FTBFS anywhere after 24.5+1-4
Source: emacs24 Version: 24.5+1-4 Severity: serious Justification: 4 With version 24.5+1-4 emacs24 fails to build on all archs because of a missing file. For example, you can find the build log for i386 here: https://buildd.debian.org/status/fetch.php?pkg=emacs24&arch=i386&ver=24.5%2B1-4&stamp=1446934624 And the error is: make[1]: Entering directory '/«BUILDDIR»/emacs24-24.5+1' cp -a debian/emacs24-el/usr/share/emacs/24.5/lisp/version.el.gz \ debian/elgz-canary cp: cannot stat 'debian/emacs24-el/usr/share/emacs/24.5/lisp/version.el.gz': No such file or directory debian/rules:613: recipe for target 'override_dh_strip_nondeterminism' failed -- System Information: Debian Release: stretch/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable') Architecture: sparc64 Kernel: Linux 4.3.0-gentoo (SMP w/1 CPU core) Locale: LANG=en_SG.UTF-8, LC_CTYPE=en_SG.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect
Bug#804183: upgrade to 1.10.4-1 creates circular inclusion
I just installed 1.10.4-1 and the circular inclusion came back. Setting up dbus (1.10.4-1) ... A reboot is required to replace the running dbus-daemon. Please reboot the system when convenient. Error org.freedesktop.DBus.Error.Failed: Circular inclusion of file '/etc/dbus-1/system.conf.dpkg-bak' Setting up dbus-x11 (1.10.4-1) ... My system may have been in an odd state due to this bug causing the 1.10.4-1 upgrade to perpetuate the circular dependency. How do I get my system to a good state again? Just upgrading to 1.10.4-1 does not fix the circular dependency for me. Help please.
Processed: Re: Bug#805224: Overwrites config file
Processing commands for cont...@bugs.debian.org: > tags 805224 + upstream patch Bug #805224 [rss2email] Overwrites config file Added tag(s) upstream and patch. > forwarded 805224 https://github.com/wking/rss2email/pull/72 Bug #805224 [rss2email] Overwrites config file Set Bug forwarded-to-address to 'https://github.com/wking/rss2email/pull/72'. > thanks Stopping processing here. Please contact me if you need assistance. -- 805224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#803658: boot hangs before cryptsetup passphrase prompt
On Sun, Nov 22, 2015 at 10:19:12PM +, Ben Hutchings wrote: > On Sun, 01 Nov 2015 15:18:46 +0100 Stefano Zacchiroli wrote: > > Package: src:linux > > Version: 4.2.3-2 > > Can you test whether this is fixed in 4.2.6-1 or 4.3-1~exp1? I'll answer this first, as it was quicker to test. I've tried the following debian-packaged kernels: $ dpkg -l 'linux-image*' | grep ^ii ii linux-image-3.16.0-4-amd643.16.7-ckt11-1 amd64Linux 3.16 for 64-bit PCs ii linux-image-4.1.0-2-amd64 4.1.6-1amd64Linux 4.1 for 64-bit PCs ii linux-image-4.2.0-1-amd64 4.2.6-1amd64Linux 4.2 for 64-bit PCs ii linux-image-4.3.0-trunk-amd64 4.3-1~exp1 amd64Linux 4.3 for 64-bit PCs Results: - work: 3.16.7, 4.1.6 - don't work: 4.2.6, 4.3 As an additional data point, before your mail I already had installed all kernels above except 4.3, which I just installed from experimental. It seems to me that: (a) it's due to something fairly recent and that is still lingering around in 4.3; (b) it is not something transient --- in particular I was thinking at something weird that might have happened one off with the initram creation just for 4.2, but that doesn't seem the case. I'll follow-up in separate mail providing the other debug information you've asked. It might take a couple of days though, as I'm currently traveling. Thanks for your help! Cheers. -- Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Former Debian Project Leader . . . . . @zacchiro . . . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club »
Bug#803936: marked as done (goplay: not installable using aptitude with "apt-xapian-index.postinst: update-python-modules: not found")
Your message dated Mon, 23 Nov 2015 19:49:35 +
with message-id
and subject line Bug#793681: fixed in apt-xapian-index 0.47+nmu1
has caused the Debian Bug report #793681,
regarding goplay: not installable using aptitude with
"apt-xapian-index.postinst: update-python-modules: not found"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
793681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: goplay
Severity: grave
Justification: renders package unusable
Dear Maintainer,
goplay failed to install using aptitude with "apt-xapian-index.postinst:
update-python-modules: not found":
# aptitude install goplay
The following NEW packages will be installed:
apt-xapian-index{a} goplay libept1.4.16{a} libfltk-images1.3{a} libfltk1.3{a}
python-xapian{a}
The following packages are RECOMMENDED but will NOT be installed:
games-thumbnails
0 packages upgraded, 6 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1275 kB of archives. After unpacking 4128 kB will be used.
Do you want to continue? [Y/n/?]
Selecting previously unselected package python-xapian.
(Reading database ... 211875 files and directories currently installed.)
Preparing to unpack .../python-xapian_1.2.21-2.1_amd64.deb ...
Unpacking python-xapian (1.2.21-2.1) ...
Selecting previously unselected package apt-xapian-index.
Preparing to unpack .../apt-xapian-index_0.47_all.deb ...
Unpacking apt-xapian-index (0.47) ...
Selecting previously unselected package libept1.4.16:amd64.
Preparing to unpack .../libept1.4.16_1.0.14+b1_amd64.deb ...
Unpacking libept1.4.16:amd64 (1.0.14+b1) ...
Preparing to unpack .../libfltk1.3_1.3.3-4_amd64.deb ...
Unpacking libfltk1.3:amd64 (1.3.3-4) ...
Selecting previously unselected package libfltk-images1.3:amd64.
Preparing to unpack .../libfltk-images1.3_1.3.3-4_amd64.deb ...
Unpacking libfltk-images1.3:amd64 (1.3.3-4) ...
Selecting previously unselected package goplay.
Preparing to unpack .../goplay_0.9.1_amd64.deb ...
Unpacking goplay (0.9.1) ...
Processing triggers for man-db (2.7.4-1) ...
Processing triggers for menu (2.1.47) ...
Processing triggers for mime-support (3.59) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Setting up python-xapian (1.2.21-2.1) ...
Setting up apt-xapian-index (0.47) ...
apt-xapian-index: Building new index in background...
/var/lib/dpkg/info/apt-xapian-index.postinst: 43: /var/lib/dpkg/info/apt-
xapian-index.postinst: update-python-modules: not found
dpkg: error processing package apt-xapian-index (--configure):
subprocess installed post-installation script returned error exit status 127
Setting up libept1.4.16:amd64 (1.0.14+b1) ...
Setting up libfltk1.3:amd64 (1.3.3-4) ...
Setting up libfltk-images1.3:amd64 (1.3.3-4) ...
dpkg: dependency problems prevent configuration of goplay:
goplay depends on apt-xapian-index; however:
Package apt-xapian-index is not configured yet.
dpkg: error processing package goplay (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.19-22) ...
Errors were encountered while processing:
apt-xapian-index
goplay
== How can you help? (doc: https://wiki.debian.org/how-can-i-help )
==
- Show old opportunities as well as new ones: how-can-i-help --old -
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package. Trying to recover:
Setting up apt-xapian-index (0.47) ...
apt-xapian-index: Building new index in background...
/var/lib/dpkg/info/apt-xapian-index.postinst: 43: /var/lib/dpkg/info/apt-
xapian-index.postinst: update-python-modules: not found
dpkg: error processing package apt-xapian-index (--configure):
subprocess installed post-installation script returned error exit status 127
dpkg: dependency problems prevent configuration of goplay:
goplay depends on apt-xapian-index; however:
Package apt-xapian-index is not configured yet.
dpkg: error processing package goplay (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
apt-xapian-index
goplay
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: apt-xapian-index
Source-Version: 0.47+nmu1
We believe
Bug#793681: marked as done (/var/lib/dpkg/info/apt-xapian-index.postinst: 43: /var/lib/dpkg/info/apt-xapian-index.postinst: update-python-modules: not found)
Your message dated Mon, 23 Nov 2015 19:49:35 + with message-id and subject line Bug#793681: fixed in apt-xapian-index 0.47+nmu1 has caused the Debian Bug report #793681, regarding /var/lib/dpkg/info/apt-xapian-index.postinst: 43: /var/lib/dpkg/info/apt-xapian-index.postinst: update-python-modules: not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 793681: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793681 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: apt-xapian-index Version: 0.47 Severity: important Hi! apt-xapian-index fails to install (stretch vmdebootstrap) [0]. Note, I had to install[1] reportbug later to report this bug so the package list might be somewhat disturbed. Christoph [1] Get:1 http://mirror.sieglitzhof.net/debian/ stretch/main python-support all 1.0.15 [33.6 kB] Get:2 http://mirror.sieglitzhof.net/debian/ stretch/main python-defusedxml all 0.4.1-2 [35.5 kB] Get:3 http://mirror.sieglitzhof.net/debian/ stretch/main python-wstools all 0.4.3-3 [141 kB] Get:4 http://mirror.sieglitzhof.net/debian/ stretch/main python-soappy all 0.12.22-1 [69.0 kB] Get:5 http://mirror.sieglitzhof.net/debian/ stretch/main python-debianbts all 1.12 [8,144 B] Get:6 http://mirror.sieglitzhof.net/debian/ stretch/main python-reportbug all 6.6.3 [126 kB] Get:7 http://mirror.sieglitzhof.net/debian/ stretch/main reportbug all 6.6.3 [123 kB] [0] # apt install apt-xapian-index Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: iso-codes libxapian22 python-apt python-apt-common python-chardet python-debian python-pkg-resources python-six python-xapian xz-utils Suggested packages: app-install-data python-xdg isoquery xapian-tools python-apt-dbg python-apt-doc xapian-doc The following NEW packages will be installed: apt-xapian-index iso-codes libxapian22 python-apt python-apt-common python-chardet python-debian python-pkg-resources python-six python-xapian xz-utils 0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded. Need to get 4,410 kB of archives. After this operation, 23.4 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://mirror.sieglitzhof.net/debian/ stretch/main libxapian22 amd64 1.2.21-1 [995 kB] Get:2 http://mirror.sieglitzhof.net/debian/ stretch/main python-apt-common all 1.0.0~beta3 [91.1 kB] Get:3 http://mirror.sieglitzhof.net/debian/ stretch/main python-apt amd64 1.0.0~beta3 [171 kB] Get:4 http://mirror.sieglitzhof.net/debian/ stretch/main xz-utils amd64 5.1.1alpha+20120614-2.1 [219 kB] Get:5 http://mirror.sieglitzhof.net/debian/ stretch/main python-xapian amd64 1.2.21-2 [309 kB] Get:6 http://mirror.sieglitzhof.net/debian/ stretch/main python-pkg-resources all 17.0-1 [73.2 kB] Get:7 http://mirror.sieglitzhof.net/debian/ stretch/main python-chardet all 2.3.0-1 [96.2 kB] Get:8 http://mirror.sieglitzhof.net/debian/ stretch/main python-six all 1.9.0-3 [13.6 kB] Get:9 http://mirror.sieglitzhof.net/debian/ stretch/main python-debian all 0.1.27 [71.5 kB] Get:10 http://mirror.sieglitzhof.net/debian/ stretch/main apt-xapian-index all 0.47 [58.5 kB] Get:11 http://mirror.sieglitzhof.net/debian/ stretch/main iso-codes all 3.59-1 [2,312 kB] Fetched 4,410 kB in 1s (2,457 kB/s) Selecting previously unselected package libxapian22. (Reading database ... 41254 files and directories currently installed.) Preparing to unpack .../libxapian22_1.2.21-1_amd64.deb ... Unpacking libxapian22 (1.2.21-1) ... Selecting previously unselected package python-apt-common. Preparing to unpack .../python-apt-common_1.0.0~beta3_all.deb ... Unpacking python-apt-common (1.0.0~beta3) ... Selecting previously unselected package python-apt. Preparing to unpack .../python-apt_1.0.0~beta3_amd64.deb ... Unpacking python-apt (1.0.0~beta3) ... Selecting previously unselected package xz-utils. Preparing to unpack .../xz-utils_5.1.1alpha+20120614-2.1_amd64.deb ... Unpacking xz-utils (5.1.1alpha+20120614-2.1) ... Selecting previously unselected package python-xapian. Preparing to unpack .../python-xapian_1.2.21-2_amd64.deb ... Unpacking python-xapian (1.2.21-2) ... Selecting previously unselected package python-pkg-resources. Preparing to unpack .../python-pkg-resources_17.0-1_all.deb ... Unpacking python-pkg-resources (17.0-1) ... Selecting previously unselected package python-chardet. Preparing to unpack .../python-chardet_2.3.0-1_all.deb ... Unpacking python-chardet (2.3.0-1) ... Selecting previously unselected package python-six. Pre
Bug#793681: /var/lib/dpkg/info/apt-xapian-index.postinst: 43: /var/lib/dpkg/info/apt-xapian-index.postinst: update-python-modules: not found
On Fri, 13 Nov 2015, Sven Joachim wrote: > First it needs to be fixed in unstable, and this bug hasn't seen any > activity in the last eight weeks. :( I have prepared an NMU that worked > for me, if you want to sponsor it, please apply the attached patch. I sponsored the NMU and pushed the change to the git repository in collab-maint. Do you want to handle the stable upload as well? I can sponsor your upload obviously. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Bug#805863: gnutls28: FTBFS on amd64 - testsuite failures
On 2015-11-23 Andreas Metzler wrote: > On 2015-11-23 James Cowgill wrote: > > Source: gnutls28 > > Version: 3.3.19-1 > > Severity: serious > > Hi, > > The latest upload of gnutls28 failed to build on amd64 (but build > > sucessfully elsewhere). This failure also looks similar to the FTBFS of > > 3.4.7-1 in experimental. > [...] > Can you reproduce this? I yesterday had a successful build on up to > date sid. Might be -jx with x >1, I will have to retry tomorrow.
Bug#805737: marked as done (apache2: mpm_prefork: crash when started with -X)
Your message dated Mon, 23 Nov 2015 19:19:27 + with message-id and subject line Bug#805737: fixed in apache2 2.4.17-3 has caused the Debian Bug report #805737, regarding apache2: mpm_prefork: crash when started with -X 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.) -- 805737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libembperl-perl Version: 2.5.0-4 Severity: serious Tags: sid stretch X-Debbugs-Cc: apac...@packages.debian.org This package fails to build on current sid. Testing mod_perl mode... #0 ascii... ok #1 pure.htm...ERR:Status read failed: Connection reset by peer The test apache2 process is crashing with this backtrace: Core was generated by `/usr/sbin/apache2 -X -f /home/niko/tmp/libembperl-perl-2.5.0/test/conf/httpd.co'. Program terminated with signal SIGSEGV, Segmentation fault. #0 ap_mpm_pod_check (pod=0x0) at mpm_unix.c:459 459 mpm_unix.c: No such file or directory. (gdb) bt #0 ap_mpm_pod_check (pod=0x0) at mpm_unix.c:459 #1 0x7f280ff3cb17 in child_main (child_num_arg=child_num_arg@entry=0, child_bucket=child_bucket@entry=0) at prefork.c:732 #2 0x7f280ff3cd32 in make_child (s=0x7f2811a2c470, slot=slot@entry=0, bucket=bucket@entry=0) at prefork.c:767 #3 0x7f280ff3e292 in prefork_run (_pconf=, plog=0x7f2811a27028, s=0x7f2811a2c470) at prefork.c:979 #4 0x56038855f9ae in ap_run_mpm (pconf=0x7f2811a53028, plog=0x7f2811a27028, s=0x7f2811a2c470) at mpm_common.c:94 #5 0x560388559040 in main (argc=4, argv=0x7ffed5563c88) at main.c:777 This regressed with apache2 upgrade from 2.4.16-3 to 2.4.17-2, so I'm cc'ing the apache2 maintainers in case they have ideas. -- Niko Tyni nt...@debian.org --- End Message --- --- Begin Message --- Source: apache2 Source-Version: 2.4.17-3 We believe that the bug you reported is fixed in the latest version of apache2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 805...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefan Fritsch (supplier of updated apache2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 23 Nov 2015 19:52:09 +0100 Source: apache2 Binary: apache2 apache2-data apache2-bin apache2-utils apache2-suexec-pristine apache2-suexec-custom apache2-doc apache2-dev apache2-dbg Architecture: source amd64 all Version: 2.4.17-3 Distribution: unstable Urgency: medium Maintainer: Debian Apache Maintainers Changed-By: Stefan Fritsch Description: apache2- Apache HTTP Server apache2-bin - Apache HTTP Server (modules and other binary files) apache2-data - Apache HTTP Server (common files) apache2-dbg - Apache debugging symbols apache2-dev - Apache HTTP Server (development headers) apache2-doc - Apache HTTP Server (on-site documentation) apache2-suexec-custom - Apache HTTP Server configurable suexec program for mod_suexec apache2-suexec-pristine - Apache HTTP Server standard suexec program for mod_suexec apache2-utils - Apache HTTP Server (utility programs for web servers) Closes: 805737 Changes: apache2 (2.4.17-3) unstable; urgency=medium . * mpm_prefork: Fix segfault if started with -X. Closes: #805737 Checksums-Sha1: fa29782ab6371022383fe4060a758a8b897eb3f9 2633 apache2_2.4.17-3.dsc e2fc75dc232a26a0a2bad7574bce0cf068edc63e 347284 apache2_2.4.17-3.debian.tar.xz f87341e6b5ff895ae4780a53f748cc6cfb2494d7 1075882 apache2-bin_2.4.17-3_amd64.deb 0ae4e59fccbad66058567a5ff2feb45ac24e9478 162912 apache2-data_2.4.17-3_all.deb 7c035a8f9ad49ecc4be8953966462e6a4a246c8d 2122364 apache2-dbg_2.4.17-3_amd64.deb 737a2f77e7a6572f2a5f7f7be979d3353b05658e 293118 apache2-dev_2.4.17-3_amd64.deb 2b7b72872cd2f8f735c098902f1e5e3ee9c82753 2764864 apache2-doc_2.4.17-3_all.deb 5484dcbdde2ae6e3a333732a85673fb30e3246af 139434 apache2-suexec-custom_2.4.17-3_amd64.deb 1f791ccaeedbc447fbaf5b2d4ee05a9cd7ceb6ae 137934 apache2-suexec-pristine_2.4.17-3_amd64.deb da2a30b7a179a467c61e6dba27bfadd3b8858f06 201878 apache2-utils_2.4.17-3_amd64.deb 070c18e1ba
Bug#805863: gnutls28: FTBFS on amd64 - testsuite failures
On 2015-11-23 James Cowgill wrote: > Source: gnutls28 > Version: 3.3.19-1 > Severity: serious > Hi, > The latest upload of gnutls28 failed to build on amd64 (but build > sucessfully elsewhere). This failure also looks similar to the FTBFS of > 3.4.7-1 in experimental. [...] Can you reproduce this? I yesterday had a successful build on up to date sid. cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Processed: Re: Bug#805817: Should instanbul be removed?
Processing commands for cont...@bugs.debian.org: > reassign 805817 ftp.debian.org Bug #805817 [istanbul] Should instanbul be removed? Bug reassigned from package 'istanbul' to 'ftp.debian.org'. No longer marked as found in versions istanbul/0.2.2-10.1. Ignoring request to alter fixed versions of bug #805817 to the same values previously set > retitle 805817 RM: instanbul - dead upstream, depends on gstreamer 0.10 Bug #805817 [ftp.debian.org] Should instanbul be removed? Changed Bug title to 'RM: instanbul - dead upstream, depends on gstreamer 0.10' from 'Should instanbul be removed?' > thanks Stopping processing here. Please contact me if you need assistance. -- 805817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#805817: Should instanbul be removed?
reassign 805817 ftp.debian.org retitle 805817 RM: instanbul - dead upstream, depends on gstreamer 0.10 thanks On Sun, Nov 22, 2015 at 10:11:09PM +0100, Luca Bruno wrote: > On Sunday 22 November 2015 20:30:14 Moritz Muehlenhoff wrote: > > > should instanbul be removed? > > Yes, I think so. > I'll proceed asking for its removal. Thanks. Let's just reassign this bug. Cheers, Moritz
Bug#805156: libstoragemgmt: FTBFS: failed to find required module pywbem
On Mon, Nov 23, 2015 at 07:05:17PM +0100, Kurt Roeckx wrote: > On Mon, Nov 23, 2015 at 05:36:10PM +0530, Ritesh Raj Sarraf wrote: > > Can you please try verify that, and then close this bug report ? > > It seems to work. It still fails on some arches like sparc64 and x32. I'm guessing some build-depedency still didn't get fixed there. Kurt
Processed: found 805817 in 0.2.2-10.1, found 805863 in 3.3.19-1, found 805863 in 3.4.7-1, tagging 805736 ...
Processing commands for cont...@bugs.debian.org: > found 805817 0.2.2-10.1 Bug #805817 [istanbul] Should instanbul be removed? Marked as found in versions istanbul/0.2.2-10.1. > found 805863 3.3.19-1 Bug #805863 [src:gnutls28] gnutls28: FTBFS on amd64 - testsuite failures Marked as found in versions gnutls28/3.3.19-1. > found 805863 3.4.7-1 Bug #805863 [src:gnutls28] gnutls28: FTBFS on amd64 - testsuite failures Marked as found in versions gnutls28/3.4.7-1. > tags 805736 + sid Bug #805736 [subliminal] subliminal: unusable due to weird dependency of stevedore Added tag(s) sid. > tags 804369 + sid stretch Bug #804369 [netexpect] netexpect: FTBFS with wireshark 2.0.0~rc2+g74e5b56-1 from experimental Added tag(s) sid and stretch. > tags 766631 + sid Bug #766631 [turnserver] FTBFS ppc64el: Remove deprecated SVID_SOURCE Added tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 766631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766631 804369: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804369 805736: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805736 805817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805817 805863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 805737 to apache2, found 805737 in 2.4.17-1, affects 805737 ...
Processing commands for cont...@bugs.debian.org: > reassign 805737 apache2 Bug #805737 [libembperl-perl] libembperl-perl: FTBFS: apache2 crash during test suite Bug reassigned from package 'libembperl-perl' to 'apache2'. No longer marked as found in versions libembperl-perl/2.5.0-4. Ignoring request to alter fixed versions of bug #805737 to the same values previously set > found 805737 2.4.17-1 Bug #805737 [apache2] libembperl-perl: FTBFS: apache2 crash during test suite Marked as found in versions apache2/2.4.17-1. > affects 805737 libembperl-perl Bug #805737 [apache2] libembperl-perl: FTBFS: apache2 crash during test suite Added indication that 805737 affects libembperl-perl > retitle 805737 apache2: mpm_prefork: crash when started with -X Bug #805737 [apache2] libembperl-perl: FTBFS: apache2 crash during test suite Changed Bug title to 'apache2: mpm_prefork: crash when started with -X' from 'libembperl-perl: FTBFS: apache2 crash during test suite' > thanks Stopping processing here. Please contact me if you need assistance. -- 805737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#800576: gitk --all doesn’t work anymore in some locales
tags 800576 + upstream fixed-upstream thanks I can confirm that the (trivial) upstream change mentioned by Jerome above fixes this issue. Ulrich
Processed: Re: gitk --all doesn’t work anymore in some locales
Processing commands for cont...@bugs.debian.org: > tags 800576 + upstream fixed-upstream Bug #800576 [gitk] gitk --all doesn’t work anymore in some locales Bug #801784 [gitk] gitk de_DE.UTF-8: Error in startup script: bad menu entry index "Ansicht bearbeiten ..." Added tag(s) fixed-upstream and upstream. Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 800576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800576 801784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#805156: marked as done (libstoragemgmt: FTBFS: failed to find required module pywbem)
Your message dated Mon, 23 Nov 2015 19:05:17 +0100
with message-id <20151123180517.ga6...@roeckx.be>
and subject line Re: Bug#805156: libstoragemgmt: FTBFS: failed to find required
module pywbem
has caused the Debian Bug report #805156,
regarding libstoragemgmt: FTBFS: failed to find required module pywbem
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.)
--
805156: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libstoragemgmt
Version: 1.2.3-1
Severity: serious
Control: block 797926 by -1
Hi,
Your package is failing to build with the following error:
checking for python2.7... /usr/bin/python2.7
checking Check for Python major version... 2
checking whether /usr/bin/python2.7 version is >= 2.6... yes
checking for /usr/bin/python2.7 version... 2.7
checking for /usr/bin/python2.7 platform... linux2
checking for /usr/bin/python2.7 script directory...
${prefix}/lib/python2.7/dist-packages
checking for /usr/bin/python2.7 extension module directory...
${exec_prefix}/lib/python2.7/dist-packages
checking python2.7 module: pywbem... no
configure: error: failed to find required module pywbem
debian/rules:15: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
An full log can be seen at:
https://buildd.debian.org/status/fetch.php?pkg=libstoragemgmt&arch=amd64&ver=1.2.3-1%2Bb1&stamp=1446729834
Kurt
--- End Message ---
--- Begin Message ---
On Mon, Nov 23, 2015 at 05:36:10PM +0530, Ritesh Raj Sarraf wrote:
> Can you please try verify that, and then close this bug report ?
It seems to work.
Kurt--- End Message ---
Bug#805737: libembperl-perl: FTBFS: apache2 crash during test suite
reassign 805737 apache2 found 805737 2.4.17-2 affects 805737 libembperl-perl retitle 805737 apache2 crash when started with -X thanks On Saturday 21 November 2015 22:42:00, Niko Tyni wrote: > The test apache2 process is crashing with this backtrace: > Core was generated by `/usr/sbin/apache2 -X -f > /home/niko/tmp/libembperl-perl-2.5.0/test/conf/httpd.co'. Program > terminated with signal SIGSEGV, Segmentation fault. #0 > ap_mpm_pod_check (pod=0x0) at mpm_unix.c:459 > 459 mpm_unix.c: No such file or directory. > (gdb) bt > #0 ap_mpm_pod_check (pod=0x0) at mpm_unix.c:459 > #1 0x7f280ff3cb17 in child_main > (child_num_arg=child_num_arg@entry=0, > child_bucket=child_bucket@entry=0) at prefork.c:732 sounds like it should be fixed by this commit: https://svn.apache.org/viewvc?view=revision&revision=r1711479 "Fix crash in ap_mpm_pod_check call caused by NULL dereference of its parameter when starting httpd as single process (httpd -X)." > This regressed with apache2 upgrade from 2.4.16-3 to 2.4.17-2, so > I'm cc'ing the apache2 maintainers in case they have ideas. The crash is easily reproduced on the command line with: apache2ctl stop apache2ctl -X # different shell curl http://localhost/
Bug#805117: marked as done (kannel-sqlbox: FTBFS: Can't satisfy build-depends)
Your message dated Mon, 23 Nov 2015 17:48:57 + with message-id and subject line Bug#805117: fixed in kannel-sqlbox 0.7.2-4 has caused the Debian Bug report #805117, regarding kannel-sqlbox: FTBFS: Can't satisfy build-depends 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.) -- 805117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kannel-sqlbox Version: 0.7.2-3 Severity: serious Control: block 797926 by -1 Hi, You have a build-depedency on kannel-dev (<< 1.4.4), but the current version in unstable is 1.4.4-1+b1. Kurt --- End Message --- --- Begin Message --- Source: kannel-sqlbox Source-Version: 0.7.2-4 We believe that the bug you reported is fixed in the latest version of kannel-sqlbox, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 805...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonas Smedegaard (supplier of updated kannel-sqlbox 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, 23 Nov 2015 17:41:18 +0100 Source: kannel-sqlbox Binary: kannel-sqlbox Architecture: source amd64 Version: 0.7.2-4 Distribution: unstable Urgency: medium Maintainer: Jonas Smedegaard Changed-By: Jonas Smedegaard Description: kannel-sqlbox - SQL helper application for Kannel WAP and SMS gateway Closes: 805117 Changes: kannel-sqlbox (0.7.2-4) unstable; urgency=medium . * Update README.source to emphasize that control.in file is *not* a show-stopper for contributions, referring to wiki page for details. * Enable support for FreeTDS. * Update package relations: + Stop build-depend on packages on behalf of kannel-dev: Corrected since kannel 1.4.3-1 - i.e. satisfied even in oldstable. + Tighten build-dependency on kannel-dev: Needed for FreeTDS support. + Relax to build-depend unversioned on cdbs devscripts debhelper: Needed versions satisfied even in oldstable. + Have kannel depend versioned on kannel-dev, and drop upper bounds build-dependency: Makes lock on upstream version binNMUable. Closes: Bug#805117. Thanks to Kurt Roeckx. * Update copyright info: + Rewrite using machine-readable format 1.0. + Use License-Grant and License-Reference fields. Thanks to Ben Finney. * Add lintian override regarding license in License-Reference field. See bug#786450. * Bump debhelper compatibility level to 9. * Add lintian override regarding debhelper 9. * Declare compliance with Debian Policy 3.9.6. * Unfuzz patch 1001. * Add patch 1002 cherry-picked upstream to fix resolve kannel linkage. * Git-ignore quilt dir. Checksums-Sha1: fe31e4c400faf3cabfec17bcc43dcbd29a63ca83 2058 kannel-sqlbox_0.7.2-4.dsc 67bb679c765e71d059a66eef006f85b9d4573186 6608 kannel-sqlbox_0.7.2-4.debian.tar.xz fe52ec88dd9e494157522a02080717f2fc78ffeb 307798 kannel-sqlbox_0.7.2-4_amd64.deb Checksums-Sha256: 292f3d81b4810c0cc75bb6eb4d658882045c032a5f1359a8e57ae365bf646521 2058 kannel-sqlbox_0.7.2-4.dsc 4ea77e48b0c0e7195b4ca2bf1f0413b0dd38339a3788b0a718399fd51620b3fb 6608 kannel-sqlbox_0.7.2-4.debian.tar.xz 67c87bc3356fbd6c99820c85bbe61c4ad01771f7d9b9421387f1fb28c074daa9 307798 kannel-sqlbox_0.7.2-4_amd64.deb Files: 647cb624bde8f6250fbe74433e978860 2058 net optional kannel-sqlbox_0.7.2-4.dsc a4d7fd3ca3fc2857364bc63187773fe0 6608 net optional kannel-sqlbox_0.7.2-4.debian.tar.xz 2e1ea9d5f13671fcd64a7e300de96f72 307798 net optional kannel-sqlbox_0.7.2-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWU07+AAoJECx8MUbBoAEhbfsP/1dOEkmzjtph88aOQ5u3YelJ tv5Hw0TKSl9UvhAIoSTJbmqwaFHYJq0UrnEr/ZvJwFH3RlIOe1WK70qL/8/Hrls3 aHV7Ay/tkthAPhPI7dEzAPFSkDwm1VV3fJvqwiK/UJMYRVqkWX9kOXjQNogq9KSq 16PTG3fQRsYOzQPUfIojYyXp96Hh+dumV/0KYaHmrs6iE6oUyrvc5hzcO5U48KbZ ZQJWp86wev6iqhXA1yU66srL1ToCvFRHaH0PcUkwIKAjg1Byx2Z6kdnrfOuFaUxb fihLFMOBrJeYr+FdWrMG0+ia8Hqd8+DAsoQ3JYeceQUVKlaa1MpvDxCoU4X2/1ci XTfaL0mDTWjNgpoxME/HL3OP/UrBxSmi3RqIdWsBOUjSGO9lHA+qrAP81HbJk3Qk CM0Uq7N1rdVUkjHbS34nBGDDDBN+uifDk1E7vtafA3N4ChOxsclCY0nN2ud/yapH azC/tFTVMoxVUFZcFx1gacmRHNW/cDof2qmw
Bug#805880: linux-image 3.2.73-1 causes video to hang at boot
Hola! Tengo el mismo resultado con las actualizaciones linux-image y con image-headers, la ultima estable que no deja inutilizada a mi computadoa es la 3.2.68-1+deb, En Debian Wheezy. Saludos! On Mon, 23 Nov 2015 09:56:18 -0500 Thomas Guyot-Sionnest wrote: > Package: linux-image-3.2.0-4-amd64 > Version: 3.2.73-1 > Severity: critical > > Hi, > > This morning I updated my Dell D630 laptop running Debian Wheezy; upon > reboot the video got stuck on a black screen with only the mouse > visible, but not moving. Upon quick investigation it appears to be a > kworker thread getting stuck: > > Nov 23 09:12:25 kernel: [ 8.919834] Process kworker/u:1 (pid: 168, > threadinfo 880119314000, task 8801192d3840) > Nov 23 09:12:25 kernel: [ 8.919995] a02d4685 > 0046 880119f38000 88011954 > Nov 23 09:12:25 kernel: [ 8.920115] 880119f39770 > 0001 880119d37c05 880119540020 > Nov 23 09:12:25 kernel: [ 8.920115] a02d618b > 880119f39780 88011954 > Nov 23 09:12:25 kernel: [ 8.920115] [] ? > i915_gem_retire_requests_ring+0x15/0x172 [i915] > Nov 23 09:12:25 kernel: [ 8.920115] [] ? > i915_gem_retire_requests+0x68/0x78 [i915] > Nov 23 09:12:25 kernel: [ 8.920115] [] ? > i915_gem_retire_work_handler+0x58/0x122 [i915] > Nov 23 09:12:25 kernel: [ 8.920115] [] ? > process_one_work+0x161/0x269 > Nov 23 09:12:25 kernel: [ 8.920115] [] ? > worker_thread+0xc2/0x145 > Nov 23 09:12:25 kernel: [ 8.920115] [] ? > manage_workers.isra.25+0x15b/0x15b > Nov 23 09:12:25 kernel: [ 8.920115] [] ? > kthread+0x76/0x7e > Nov 23 09:12:25 kernel: [ 8.920115] [] ? > kernel_thread_helper+0x4/0x10 > Nov 23 09:12:25 kernel: [ 8.920115] [] ? > kthread_worker_fn+0x139/0x139 > Nov 23 09:12:25 kernel: [ 8.920115] [] ? > gs_change+0x13/0x13 > Nov 23 09:12:25 kernel: [ 8.920115] RSP > > This issue appears to have been reported to the LKML already: > https://lkml.org/lkml/2015/10/1/861 > > The kernel was updated from 3.2.68-1+deb7u3 to 3.2.73-1. According to > the package's changelog > (http://metadata.ftp-master.debian.org/changelogs//main/l/linux/linux_3.2.73-1_changelog) > the issue may have been introduced in version 3.2.71-1: > > [ Ben Hutchings ] > * drm, agp: Update to 3.4.109: > [...] > - drm/radeon: Use drm_calloc_ab for CS relocs > > This is the exact commit pointed out as the culprit in the reply to the > LKML post I pointed out. > > As expected, downgrading the package back to 3.2.68-1+deb7u3 resolved > the issue >
Bug#805876: marked as done (libclass-accessor-chained-perl: FTBFS with perl 5.22: missing dependency on Module::Build)
Your message dated Mon, 23 Nov 2015 17:08:25 + with message-id and subject line Bug#805876: fixed in libclass-accessor-chained-perl 0.01.1~debian-4 has caused the Debian Bug report #805876, regarding libclass-accessor-chained-perl: FTBFS with perl 5.22: missing dependency on Module::Build 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.) -- 805876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libclass-accessor-chained-perl Version: 0.01.1~debian-3 Severity: serious Justification: will FTBFS with upcoming transition User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch This package FTBFS with perl 5.22, which is in experimental and due to transition to unstable soon: perl Build.PL --installdirs vendor --config "optimize=-g -O2 -fstack-pro tector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2" --config "ld =x86_64-linux-gnu-gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-se curity -Wl,-z,relro" Can't locate Module/Build.pm in @INC (you may need to install the Module::Build module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.0 /u sr/local/share/perl/5.22.0 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_pe rl /usr/lib/x86_64-linux-gnu/perl-base .) at Build.PL line 2. BEGIN failed--compilation aborted at Build.PL line 2. dh_auto_configure: perl Build.PL --installdirs vendor --config optimize=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 --config ld=x86_64-linux-gnu-gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro returned exit code 2 The problem is solved by build-depending on libmodule-build-perl (which used to be bundled with perl until 5.22). Cheers, Dominic. --- End Message --- --- Begin Message --- Source: libclass-accessor-chained-perl Source-Version: 0.01.1~debian-4 We believe that the bug you reported is fixed in the latest version of libclass-accessor-chained-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 805...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libclass-accessor-chained-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 23 Nov 2015 17:50:58 +0100 Source: libclass-accessor-chained-perl Binary: libclass-accessor-chained-perl Architecture: source Version: 0.01.1~debian-4 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 805876 Description: libclass-accessor-chained-perl - Perl module providing chained accessors Changes: libclass-accessor-chained-perl (0.01.1~debian-4) unstable; urgency=medium . * Team upload. * Add explicit build dependency on libmodule-build-perl. (Closes: #805876) * debian/watch: add dversionmangle, drop uupdate. Checksums-Sha1: 63f887e9977cca09938207b140066698b42c6ab3 2456 libclass-accessor-chained-perl_0.01.1~debian-4.dsc 024c908aecb2d8fc33774ab6df5bcc4214309046 2096 libclass-accessor-chained-perl_0.01.1~debian-4.debian.tar.xz Checksums-Sha256: 1336b1036396c22916e9e0d41ac172b2d22ae0f58ab24c87b32359c4e31b3da5 2456 libclass-accessor-chained-perl_0.01.1~debian-4.dsc 77a8f3deefb49a96aa8f7aaadce862e40a4225bdee25e50b5f29f74059c224e8 2096 libclass-accessor-chained-perl_0.01.1~debian-4.debian.tar.xz Files: 075bf9610fb68d29f803e727e89b0456 2456 perl optional libclass-accessor-chained-perl_0.01.1~debian-4.dsc 257c45287ebd49a5586f83bef489b8a2 2096 perl optional libclass-accessor-chained-perl_0.01.1~debian-4.debian.tar.xz -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJWU0RSXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGy2kQALM1OS+k+y0xhikkTR+4Lc73 yT3Xn0SOq2RCqa3E9Bl7ro8gz5Lyzc6POnR0sHSv+8aHbfvVoaRkil5zEEhpvaWD vjp9KC7y+qZx8/1W4hQTSUW3ZUfEiqmkKwMjUeBlzJeN1bWR6AgaQGXPJyidGU4f U5Czp4DabWD4mXcriPivU
Bug#805880: linux-image 3.2.73-1 causes video to hang at boot
Likely the same bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801467 https://lists.debian.org/debian-user/2015/10/msg00175.html -- Thomas
Bug#801467: base: Same problem here
On Tue, 10 Nov 2015 11:08:57 +0200 Apostolos wrote: > Package: base > Followup-For: Bug #801467 > > I have exactly the same problem with Dmitry, and resolved it with acpi=off > Hi, I just submitted Bug #805880 - then after looking at critical bugs in wheezy I think this one could be related... Regards, -- Thomas
Bug#805880: linux-image 3.2.73-1 causes video to hang at boot
Package: linux-image-3.2.0-4-amd64 Version: 3.2.73-1 Severity: critical Hi, This morning I updated my Dell D630 laptop running Debian Wheezy; upon reboot the video got stuck on a black screen with only the mouse visible, but not moving. Upon quick investigation it appears to be a kworker thread getting stuck: Nov 23 09:12:25 kernel: [8.919834] Process kworker/u:1 (pid: 168, threadinfo 880119314000, task 8801192d3840) Nov 23 09:12:25 kernel: [8.919995] a02d4685 0046 880119f38000 88011954 Nov 23 09:12:25 kernel: [8.920115] 880119f39770 0001 880119d37c05 880119540020 Nov 23 09:12:25 kernel: [8.920115] a02d618b 880119f39780 88011954 Nov 23 09:12:25 kernel: [8.920115] [] ? i915_gem_retire_requests_ring+0x15/0x172 [i915] Nov 23 09:12:25 kernel: [8.920115] [] ? i915_gem_retire_requests+0x68/0x78 [i915] Nov 23 09:12:25 kernel: [8.920115] [] ? i915_gem_retire_work_handler+0x58/0x122 [i915] Nov 23 09:12:25 kernel: [8.920115] [] ? process_one_work+0x161/0x269 Nov 23 09:12:25 kernel: [8.920115] [] ? worker_thread+0xc2/0x145 Nov 23 09:12:25 kernel: [8.920115] [] ? manage_workers.isra.25+0x15b/0x15b Nov 23 09:12:25 kernel: [8.920115] [] ? kthread+0x76/0x7e Nov 23 09:12:25 kernel: [8.920115] [] ? kernel_thread_helper+0x4/0x10 Nov 23 09:12:25 kernel: [8.920115] [] ? kthread_worker_fn+0x139/0x139 Nov 23 09:12:25 kernel: [8.920115] [] ? gs_change+0x13/0x13 Nov 23 09:12:25 kernel: [8.920115] RSP This issue appears to have been reported to the LKML already: https://lkml.org/lkml/2015/10/1/861 The kernel was updated from 3.2.68-1+deb7u3 to 3.2.73-1. According to the package's changelog (http://metadata.ftp-master.debian.org/changelogs//main/l/linux/linux_3.2.73-1_changelog) the issue may have been introduced in version 3.2.71-1: [ Ben Hutchings ] * drm, agp: Update to 3.4.109: [...] - drm/radeon: Use drm_calloc_ab for CS relocs This is the exact commit pointed out as the culprit in the reply to the LKML post I pointed out. As expected, downgrading the package back to 3.2.68-1+deb7u3 resolved the issue NB: I set the severity as critical considering it renders the system unusable (you have to ssh in if enabled; possibly booting up in text mode might work too) and the update replaces the old, working, kernel so that you can't just pick an older version in Grub. Regards, -- Thomas
Bug#804360: marked as done (paprefs: FTBFS)
Your message dated Mon, 23 Nov 2015 16:37:10 +0200 with message-id and subject line fixed in paprefs 0.9.10-2 has caused the Debian Bug report #804360, regarding paprefs: FTBFS 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.) -- 804360: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804360 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: paprefs Version: 0.9.10-1+b2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 paprefs is currently FTBFS. Additionally, it currently needs Gstreamer 0.10, which is being removed from the archive. It would need to be migrated to Gstreamer 1.0. Last, Git changes to the Debian packaging I uploaded when I was still involved in the package's maintenance remain to be released. - -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (1001, 'testing'), (1001, 'stable'), (1001, 'oldstable') Architecture: i386 (i586) Kernel: Linux 3.16.0-4-586 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages paprefs depends on: ii gconf-service 3.2.6-3 ii gnome-icon-theme3.12.0-1 ii libatk1.0-0 2.18.0-1 ii libatkmm-1.6-1v52.24.1-1 ii libc6 2.19-22 ii libcairo2 1.14.4-1 ii libcairomm-1.0-1v5 1.12.0-1 ii libdbus-1-3 1.10.2-1 ii libdbus-glib-1-20.102-1 ii libfontconfig1 2.11.0-6.3 ii libfreetype62.6-2 ii libgcc1 1:5.2.1-23 ii libgconf-2-43.2.6-3 ii libgconfmm-2.6-1v5 2.28.0-2 ii libgdk-pixbuf2.0-0 2.32.1-1 ii libglade2-0 1:2.6.4-2 ii libglademm-2.4-1v5 2.6.7-5+b1 ii libglib2.0-02.46.1-1 ii libglibmm-2.4-1v5 2.46.1-1 ii libgtk2.0-0 2.24.28-1 ii libgtkmm-2.4-1v51:2.24.4-2+b1 ii libpango-1.0-0 1.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libpangoft2-1.0-0 1.38.1-1 ii libpangomm-1.4-1v5 2.38.1-1 ii libpulse0 7.0-1+b1 ii libsigc++-2.0-0v5 2.6.1-3 ii libstdc++6 5.2.1-23 ii libxml2 2.9.2+zdfsg1-4 ii pulseaudio-module-gconf 7.0-1+b1 ii pulseaudio-module-zeroconf 7.0-1+b1 paprefs recommends no packages. paprefs suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWPj9zAAoJEK4fgnfEtNe2E6cQALJUeLzTeaWNjn3Cu73cd1mI Nxhh+A7XYZSCyyFn0qAtWFB4+ilFFv5y/Lukzt0MTBYz0ySjdmYmJCP4GS5ASvw3 sN4bMqullGzBYzJ+aIl/3URsYQOrcP7bvz4e9z1ojav3Gitt7McJoNTrMnZjOzMY uGAUywhjsGa5U7q3DkauqIjxwqoRgVxvkKuJvw6uD0Rhkgo9s+tWDjpDfB5BBPWv itO4T3M5G5IWGMEF6rc6dSSQuownv8wfAT+voSAv3yPotKY35pEjjXUPDNDVWRjL S0RKNzZBld8lXRP+ZzHG/mTd1f7MV6bxZpug6oyBszDF57tw4Uz4iznOCtSlvGmb 0kFIZ8xvInAWQLCbBE2zb5MaTyQT4WdLzwwWsnAuUukPrkwwd2qZqsyN6BlGXCNN HfEcAO2QCZlD/pSJ7qvV9HLiF98OTpuRqhspReCNJnAiDS+Pyf9LRqbbu5WGLxMC 7UyTSR3X9F6bWkp49zdDVeaQMjOccpCAxQj2ibwhh/PgOnfLmmcabjeu0usMtepZ t2sULnakzw4BXZ/PTu6wIZQMSLkug0hQTaIaVo6YDo3yfRi/+rjhmueL9rGDnTqY HqX591+rmjytsNVp2QUibXhHSwZa7JA+mw94KgLKvO5u3e8qXCm/wIsucjZlEVMQ /lzbUJC2QKgv+4goqa73 =6do2 -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Pending changes were uploaded as paprefs 0.9.10-2 Apparently, the FTBFS condition resolved itself as well. As far as I can tell, this is now fixed. -- Martin-Éric--- End Message ---
Bug#802618: xserver-xorg-legacy works
Installing libpam-systemd does not seem to have any effect. Installing xserver-xorg-legacy brings back mouse and keyboard. Regards, Oleg
Processed: python-jmespath: diff for NMU version 0.4.1-1.1
Processing control commands: > tags 804557 + patch Bug #804557 [src:python-jmespath] python-jmespath: FTBFS: ImportError: No module named nose.tools Added tag(s) patch. > tags 804557 + pending Bug #804557 [src:python-jmespath] python-jmespath: FTBFS: ImportError: No module named nose.tools Added tag(s) pending. -- 804557: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#804557: python-jmespath: diff for NMU version 0.4.1-1.1
Control: tags 804557 + patch Control: tags 804557 + pending Dear maintainer, I've prepared an NMU for python-jmespath (versioned as 0.4.1-1.1). Please feel free to tell me if I should delay it longer. Regards. -- Dariusz Dwornikowski, Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 1.6.2 BTiCW | tel. +48 61 665 23 71 diff -Nru python-jmespath-0.4.1/debian/changelog python-jmespath-0.4.1/debian/changelog --- python-jmespath-0.4.1/debian/changelog 2015-11-23 14:49:57.0 +0100 +++ python-jmespath-0.4.1/debian/changelog 2015-11-23 11:20:41.0 +0100 @@ -1,3 +1,10 @@ +python-jmespath (0.4.1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Added python-nose and python3-nose to Build-Deps (Closes: #804557) + + -- Dariusz Dwornikowski Mon, 23 Nov 2015 11:18:41 +0100 + python-jmespath (0.4.1-1) unstable; urgency=medium * New upstream release diff -Nru python-jmespath-0.4.1/debian/control python-jmespath-0.4.1/debian/control --- python-jmespath-0.4.1/debian/control 2015-11-23 14:49:57.0 +0100 +++ python-jmespath-0.4.1/debian/control 2015-11-23 11:20:03.0 +0100 @@ -8,6 +8,8 @@ , python-setuptools , python3-all , python3-setuptools + , python-nose + , python3-nose Standards-Version: 3.9.5 Homepage: https://github.com/boto/jmespath Vcs-Git: git://anonscm.debian.org/python-modules/packages/python-jmespath.git signature.asc Description: PGP signature
Bug#805876: libclass-accessor-chained-perl: FTBFS with perl 5.22: missing dependency on Module::Build
Source: libclass-accessor-chained-perl Version: 0.01.1~debian-3 Severity: serious Justification: will FTBFS with upcoming transition User: debian-p...@lists.debian.org Usertags: perl-5.22-transition Tags: sid stretch This package FTBFS with perl 5.22, which is in experimental and due to transition to unstable soon: perl Build.PL --installdirs vendor --config "optimize=-g -O2 -fstack-pro tector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2" --config "ld =x86_64-linux-gnu-gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-se curity -Wl,-z,relro" Can't locate Module/Build.pm in @INC (you may need to install the Module::Build module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.0 /u sr/local/share/perl/5.22.0 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_pe rl /usr/lib/x86_64-linux-gnu/perl-base .) at Build.PL line 2. BEGIN failed--compilation aborted at Build.PL line 2. dh_auto_configure: perl Build.PL --installdirs vendor --config optimize=-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 --config ld=x86_64-linux-gnu-gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro returned exit code 2 The problem is solved by build-depending on libmodule-build-perl (which used to be bundled with perl until 5.22). Cheers, Dominic.
Bug#784070: marked as done (mdadm Software RAID1 with GPT on Debian 8.0.0 amd64 - Does not mount/boot on disk removal)
Your message dated Mon, 23 Nov 2015 12:33:47 + with message-id and subject line Bug#784070: fixed in mdadm 3.3.4-1.1 has caused the Debian Bug report #784070, regarding mdadm Software RAID1 with GPT on Debian 8.0.0 amd64 - Does not mount/boot on disk removal 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.) -- 784070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mdadm Version: 3.3.2-5 Severity: critical -- Package-specific info: --- mdadm.conf CREATE owner=root group=disk mode=0660 auto=yes HOMEHOST MAILADDR root ARRAY /dev/md1 metadata=1.2 UUID=856fee1e:feccb34a:f798724a:36e91658 name=FluffyBunny:1 ARRAY /dev/md0 metadata=1.2 UUID=b597bb3c:f50fff2a:f395548b:ccbb48d1 name=FluffyBunny:0 --- /etc/default/mdadm INITRDSTART='all' AUTOCHECK=true START_DAEMON=true DAEMON_OPTIONS="--syslog" VERBOSE=false --- /proc/mdstat: Personalities : [raid1] md1 : active (auto-read-only) raid1 sdb2[0] sdc2[1] sdd2[2] 7808000 blocks super 1.2 [3/3] [UUU] md0 : active raid1 sdd3[2] sdc3[1] sdb3[0] 1945569280 blocks super 1.2 [3/3] [UUU] bitmap: 0/15 pages [0KB], 65536KB chunk unused devices: --- /proc/partitions: major minor #blocks name 1101048575 sr0 80 976762584 sda 81 976761560 sda1 8 16 1953514584 sdb 8 17 1024 sdb1 8 187812096 sdb2 8 19 1945700352 sdb3 8 32 1953514584 sdc 8 33 1024 sdc1 8 347812096 sdc2 8 35 1945700352 sdc3 8 48 1953514584 sdd 8 49 1024 sdd1 8 507812096 sdd2 8 51 1945700352 sdd3 90 1945569280 md0 917808000 md1 --- LVM physical volumes: LVM does not seem to be used. --- mount output sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=2041852,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,relatime,size=3270412k,mode=755) /dev/md0 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=22,pgrp=1,timeout=300,minproto=5,maxproto=5,direct) mqueue on /dev/mqueue type mqueue (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) --- initrd.img-3.16.0-4-amd64: 92433 blocks 599bbf3fe6093157a26863dcb59cdf5d ./scripts/local-top/mdadm da9588388e9d3dbd528a6e7aa2dd3fe7 ./sbin/mdadm 5e35b64dad54196cb721776566c04545 ./lib/modules/3.16.0-4-amd64/kernel/drivers/md/raid456.ko a446065a313394c333967e3540d32923 ./lib/modules/3.16.0-4-amd64/kernel/drivers/md/raid10.ko b9e70a0d04a34eecc2fff9722a27af99 ./lib/modules/3.16.0-4-amd64/kernel/drivers/md/dm-mod.ko faf18e3ae8bbb882f45fa147450ba375 ./lib/modules/3.16.0-4-amd64/kernel/drivers/md/multipath.ko 9bd0a33fa738d559a1c4ff83cace11ba ./lib/modules/3.16.0-4-amd64/kernel/drivers/md/linear.ko b0d26ac52a08e149dd76407ede65366f ./lib/modules/3.16.0-4-amd64/kernel/drivers/md/md-mod.ko 7a737d39c9b208cb27ada8751b601bd9 ./lib/modules/3.16.0-4-amd64/kernel/drivers/md/raid1.ko f5f26f436a749b8d908e4155764e5d64 ./lib/modules/3.16.0-4-amd64/kernel/drivers/md/raid0.ko 4fa29a08bf629f67a
Bug#781172: marked as done (base: Stock Debian Jessie - can't boot off degraded raid1?)
Your message dated Mon, 23 Nov 2015 12:33:47 + with message-id and subject line Bug#784070: fixed in mdadm 3.3.4-1.1 has caused the Debian Bug report #784070, regarding base: Stock Debian Jessie - can't boot off degraded raid1? 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.) -- 784070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: base Severity: important Dear Maintainer, Install a Wheezy VM using debian-7.8.0-amd64-netinst.iso create a raid1 mirror in the drive setup mount / on /dev/md0 and install base system to it login grub-install /dev/vdb poweroff disable either drive /dev/vda or /dev/vdb (give VM access to only 1 drive) computer boots # cat /proc/mdstat Personalities : [raid1] md0 : active raid1 vda1[1] 8382400 blocks super 1.2 [2/1] [_U] Sweet. Install a Jessie VM using debian-jessie-DI-rc1-amd64-netinst.iso create a raid1 mirror in the drive setup mount / on /dev/md0 and install base system to it login grub-install /dev/vdb poweroff disable either drive /dev/vda or /dev/vdb (give VM access to only 1 drive) ALERT! /dev/disk/by-uuid/ does not exist. Dropping to a shell! (where is the uuid of /dev/md0) # cat /proc/mdstat Personalities : md0 : inactive vda1[0](S) 8382464 blocks super 1.2 Both refer to md0 by UUID in fstab. When I remove the "quiet" from the kernel boot args, this is the last line I see repeated over and over again until finally I get the error I described above: running /scripts/local-block I'm admitedly not a raid expert, but this seems to be really missing the point. Part of the reason I want a raid1 is so it can survive this type of scenario. I googled around and surprisingly came up with very few leads. I found a Ubuntu wiki (https://help.ubuntu.com/community/Installation/SoftwareRAID#Boot_from_Degraded_Disk) that discussed how to force it to boot a degraded raid but seemed to do nothing here on debian. I found a kernel boot arg that promised to do the same (http://serverfault.com/questions/196445/boot-debian-while-raid-array-is-degraded), but it didn't work either. What am I missing here? Shouldn't this work by default? I think a lot of people will get caught off guard by this thinking their startup drive is mirrored but the server won't boot without some manual intervention? Actually, I was not able to get it to boot at all. -- System Information: Debian Release: 7.8 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-0.bpo.4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Source: mdadm Source-Version: 3.3.4-1.1 We believe that the bug you reported is fixed in the latest version of mdadm, 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 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yann Soubeyrand (supplier of updated mdadm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 10 Nov 2015 11:18:39 +0100 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source amd64 Version: 3.3.4-1.1 Distribution: unstable Urgency: medium Maintainer: Debian mdadm maintainers Changed-By: Yann Soubeyrand Description: mdadm - tool to administer Linux MD arrays (software RAID) mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb) Closes: 784070 Changes: mdadm (3.3.4-1.1) unstable; urgency=medium . * Non-maintainer upload. * disable-incremental-assembly.patch: incremental assembly prevents booting in degraded mode (Closes: #784070) Checksums-Sha1: 538bcb637865f75ee99ea965d4d3bc6c8796eae3 1970 mdadm_3.3.4-1.1.dsc ed9fc1607b26421817207330cfe47111ee143639 86312 mdadm_3.3.4-1.1.debian.tar.xz 2a023be08c8ae49155dd70b1f4a766331c824b68 257110 mdadm-udeb_3.3.4-1.1_amd64.udeb c361786547cf777ffe66ad9d495abc92ed40c0f5 433738 mdadm_3.3.4-1.1_amd64.deb Checksums-Sha256: 22585dc6c20b173b433bff0a31028273d5da789f66bab1b61939416557de77c2 1970 mdadm_3.3.4-1.1.dsc 16dd
Bug#784823: marked as done (Regression - mdadm in jessie will not boot degraded raid1 array)
Your message dated Mon, 23 Nov 2015 12:33:47 + with message-id and subject line Bug#784070: fixed in mdadm 3.3.4-1.1 has caused the Debian Bug report #784070, regarding Regression - mdadm in jessie will not boot degraded raid1 array 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.) -- 784070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mdadm Version: 3.3.2-5 This version of mdadm will not boot a degraded RAID1 array with a missing disk. When booting under the above circumstances, I am dropped to a busybox shell with disk not found message. I have confirmed this on physical and virtual machines. This bug appears to be happening to other people. For example: http://arstechnica.com/civis/viewtopic.php?f=16&t=1271945 The wheezy version (3.2.5-5) will boot under these circumstances. Manually installing the wheezy version in Jessie results in creation of a bootable initrd (and successful boot up). This is a severe error for my usage (being inaccessible hosts with RAID1 disks). Let me know if I can provide additional information. Damien --- End Message --- --- Begin Message --- Source: mdadm Source-Version: 3.3.4-1.1 We believe that the bug you reported is fixed in the latest version of mdadm, 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 784...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yann Soubeyrand (supplier of updated mdadm package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 10 Nov 2015 11:18:39 +0100 Source: mdadm Binary: mdadm mdadm-udeb Architecture: source amd64 Version: 3.3.4-1.1 Distribution: unstable Urgency: medium Maintainer: Debian mdadm maintainers Changed-By: Yann Soubeyrand Description: mdadm - tool to administer Linux MD arrays (software RAID) mdadm-udeb - tool to administer Linux MD arrays (software RAID) (udeb) Closes: 784070 Changes: mdadm (3.3.4-1.1) unstable; urgency=medium . * Non-maintainer upload. * disable-incremental-assembly.patch: incremental assembly prevents booting in degraded mode (Closes: #784070) Checksums-Sha1: 538bcb637865f75ee99ea965d4d3bc6c8796eae3 1970 mdadm_3.3.4-1.1.dsc ed9fc1607b26421817207330cfe47111ee143639 86312 mdadm_3.3.4-1.1.debian.tar.xz 2a023be08c8ae49155dd70b1f4a766331c824b68 257110 mdadm-udeb_3.3.4-1.1_amd64.udeb c361786547cf777ffe66ad9d495abc92ed40c0f5 433738 mdadm_3.3.4-1.1_amd64.deb Checksums-Sha256: 22585dc6c20b173b433bff0a31028273d5da789f66bab1b61939416557de77c2 1970 mdadm_3.3.4-1.1.dsc 16dd6b77c14a15afa23e077f0c157c17ef5cc6054b17ccb38cf5af86f7bf55bd 86312 mdadm_3.3.4-1.1.debian.tar.xz b6e1d3d178be5556891634712bd4cb5219deade34d2dc1c31620601c2d8134d8 257110 mdadm-udeb_3.3.4-1.1_amd64.udeb 325ea8354c039ca1fd1bbfad1d19335d36ea9fddbc2cb1eb30500f7e5930dc52 433738 mdadm_3.3.4-1.1_amd64.deb Files: 9b3fca39d06b53b8914cd914ef4c3418 1970 admin optional mdadm_3.3.4-1.1.dsc 3bcd96d08533e7905d1e340dcb3358e4 86312 admin optional mdadm_3.3.4-1.1.debian.tar.xz 5aeb025930deab41eb93ed0194336177 257110 debian-installer optional mdadm-udeb_3.3.4-1.1_amd64.udeb 00c829f7f356f48b0a6b25966265a10e 433738 admin optional mdadm_3.3.4-1.1_amd64.deb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJWUwU2AAoJEFh5eVc0QmhOAu8QAK3LZNClmLKPoYMe4gPhahbQ LO5blpxTp4TiUfRVcf+3xtXDV6JhoRgz6c8c0kwzjOMK7zZg4vO0DVbHTjgEvFBY z0l0r1/LzSqJm17O7LaV5lGWWko4D1lcZp8XoSwb5HwYLIALaeB2RNyThPMSZpnL nmTHjzCOp/YESJcohOfa8AxG89HA5E1KNcVy8yr0yXQYUxsl316/VbtsOJqvkiiH PEwLS4A3N3naTtEdOdouhauidoaEF0X62z7kobZHgvi83t3O0Rre+Sjd4Uz3Udqy eDONrx2ZgxcTV9RBWg669eDyJ7w1Fb9NrQ7dHVES0Jgdn+S2h63gpLuAS1YumOZp fW/juwnOm0haU8cjIhtuPtcLUvcEB2uoggW5DCg3CPSvTpl/zQCOpIXX01mJ23P5 C4dComSWHcLgH/5PBkKYJs9DlvS4F0bBxOSUhVesLA5FG7VJ23gugebsPZeeNbKu GOMIDE9sOQxM9GEFcwTG8AIWEtDemh1jNzfRcFqH1NECeGbJ/XPrjNjKAQnLsJI8 vNgpJtePQ9fhX0+bSSqkVjQQYMVw0nO1rivPNJq6ez67Z+YNhRRjuWcN19OyhuW4 rAcBVUwOFoLNkFFEQmOc6om5mDqRvISsEiyZ9LD67nOTaP/dNojWMP+tyqQG+Vrv o1VHja3YbXohwbfHmveF =X6q1 -END PGP SIGNATURE End Message ---
Bug#805156: libstoragemgmt: FTBFS: failed to find required module pywbem
On Mon, 2015-11-16 at 20:51 +0530, Ritesh Raj Sarraf wrote: > On Sun, 2015-11-15 at 18:39 +0100, Kurt Roeckx wrote: > > It still fails on the buildds. > > Only for the rebuilds with 1.2.3-1+b1, which is with libssl 1.0.2. > > The older build, 1.2.3-1, built successfully with libssl 1.0.0. > > So either this has to do with libssl or pywbem. So this bug finally led to libstoragemgmt's removal from the archive. This is still not a bug in libstoragemgmt. If you trigger a build now, it will build successfully. Can you please try verify that, and then close this bug report ? -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention." signature.asc Description: This is a digitally signed message part
Bug#805828: [debian-mysql] Bug#805828: mysql-server-5.6: upgrade didn't work, package unusable, mysql does not start
Hello, After creating the "/etc/mysql/conf.d directory" I try to do a fresh install with : --- apt-get install mysql-server Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: mysql-server-5.6 mysql-server-core-5.6 Suggested packages: tinyca The following NEW packages will be installed: mysql-server mysql-server-5.6 mysql-server-core-5.6 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 10,2 MB of archives. After this operation, 79,4 MB of additional disk space will be used. Do you want to continue? [O/n] Ask 2 times for root password Get:1 http://ftp.fr.debian.org/debian/ stretch/main mysql-server-core- 5.6 amd64 5.6.27-2 [4 379 kB] Get:2 http://ftp.fr.debian.org/debian/ stretch/main mysql-server-5.6 amd64 5.6.27-2 [5 676 kB] Get:3 http://ftp.fr.debian.org/debian/ stretch/main mysql-server all 5.6.27-2 [102 kB] Preconfiguring packages ... Fetched 10,2 MB in 4s (2 160 kB/s) Selecting previously unselected package mysql-server-core-5.6. (Reading database ... 539834 files and directories currently installed.) Preparing to unpack .../mysql-server-core-5.6_5.6.27-2_amd64.deb ... Unpacking mysql-server-core-5.6 (5.6.27-2) ... Selecting previously unselected package mysql-server-5.6. Preparing to unpack .../mysql-server-5.6_5.6.27-2_amd64.deb ... Unpacking mysql-server-5.6 (5.6.27-2) ... Selecting previously unselected package mysql-server. Preparing to unpack .../mysql-server_5.6.27-2_all.deb ... Unpacking mysql-server (5.6.27-2) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for systemd (227-2) ... Setting up mysql-server-core-5.6 (5.6.27-2) ... Setting up mysql-server-5.6 (5.6.27-2) ... update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode 2015-11-23 12:29:26 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details). 2015-11-23 12:29:26 0 [Note] /usr/sbin/mysqld (mysqld 5.6.27-2) starting as process 21919 ... Setting up mysql-server (5.6.27-2) ... Processing triggers for systemd (227-2) ... -- All is OK, mysql is started and I can connect to the database, the /etc/mysql directory contains : -- ls -alR .: total 40 drwxr-xr-x 4 root root 4096 nov. 23 12:29 . drwxr-xr-x 218 root root 16384 nov. 23 12:03 .. drwxr-xr-x 2 root root 4096 nov. 23 12:24 conf.d -rw--- 1 root root 333 nov. 23 12:03 debian.cnf -rwxr-xr-x 1 root root 1193 nov. 11 13:18 debian-start lrwxrwxrwx 1 root root24 nov. 23 12:29 my.cnf -> /etc/alternatives/my.cnf -rw-r--r-- 1 root root 682 nov. 10 12:49 mysql.cnf drwxr-xr-x 2 root root 4096 nov. 23 12:29 mysql.conf.d ./conf.d: total 8 drwxr-xr-x 2 root root 4096 nov. 23 12:24 . drwxr-xr-x 4 root root 4096 nov. 23 12:29 .. ./mysql.conf.d: total 16 drwxr-xr-x 2 root root 4096 nov. 23 12:29 . drwxr-xr-x 4 root root 4096 nov. 23 12:29 .. -rw-r--r-- 1 root root 3027 nov. 10 12:49 mysqld.cnf -rw-r--r-- 1 root root 21 nov. 10 12:49 mysqld_safe_syslog.cnf --- The "conf.d" directory doesn't contain any file. I will now reload some data ... JPP
Bug#805863: gnutls28: FTBFS on amd64 - testsuite failures
Source: gnutls28 Version: 3.3.19-1 Severity: serious Hi, The latest upload of gnutls28 failed to build on amd64 (but build sucessfully elsewhere). This failure also looks similar to the FTBFS of 3.4.7-1 in experimental. https://buildd.debian.org/status/fetch.php?pkg=gnutls28&arch=amd64&ver=3.3.19-1&stamp=1448215393 > Making check in tests > make[4]: Entering directory '/«PKGBUILDDIR»/guile/tests' > make check-TESTS > make[5]: Entering directory '/«PKGBUILDDIR»/guile/tests' > make[6]: Entering directory '/«PKGBUILDDIR»/guile/tests' > PASS: errors.scm > PASS: anonymous-auth.scm > PASS: pkcs-import-export.scm > PASS: session-record-port.scm > PASS: x509-certificates.scm > PASS: priorities.scm > PASS: openpgp-keys.scm > ../../build-aux/test-driver: line 107: 22622 Segmentation fault "$@" > > $log_file 2>&1 > FAIL: x509-auth.scm > PASS: openpgp-keyring.scm > PASS: srp-base64.scm > ../../build-aux/test-driver: line 107: 22689 Segmentation fault "$@" > > $log_file 2>&1 > FAIL: openpgp-auth.scm > > Testsuite summary for GnuTLS 3.3.19 > > # TOTAL: 11 > # PASS: 9 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 2 > # XPASS: 0 > # ERROR: 0 > > See guile/tests/test-suite.log > Please report to b...@gnutls.org > > Makefile:1492: recipe for target 'test-suite.log' failed > make[6]: *** [test-suite.log] Error 1 Thanks, James signature.asc Description: This is a digitally signed message part
Bug#805828: [debian-mysql] Bug#805828: mysql-server-5.6: upgrade didn't work, package unusable, mysql does not start
Hello, As the machine is a "test machine" I try some "tricks" to get the database "on" with no success. I save copies of some "error.log" files and I enclose them here. After having no success I remove the mysql-server package (remove -- purge) and reinstall from scratch. I get also a "no success" try, as I have a message (in debconf) : --- An error occurred while setting the password for the MySQL administrative user. This may have happened because the account already has a password, or because of a communication problem with the MySQL server. You should check the account's password after the package installation. Please read the /usr/share/doc/mysql-server-5.6/README.Debian file for more information. --- The file "/var/lib/mysql/k2000.err" contains : 151123 12:05:05 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql /usr/sbin/mysqld: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2 - No such file or directory) Fatal error in defaults handling. Program aborted 151123 12:05:05 mysqld_safe mysqld from pid file /var/lib/mysql/k2000.pid ended --- The /var/lib/mysql (no symlink) contains only : /var/lib/mysql# ls -al total 16 drwx-- 3 mysql mysql 4096 nov. 23 12:07 . drwxr-xr-x 102 root root 4096 nov. 23 12:03 .. -rw-r--r-- 1 mysql root 0 nov. 23 12:15 debian-5.6.flag -rw-r- 1 mysql mysql 945 nov. 23 12:15 k2000.err drwx-- 2 mysql root 4096 nov. 23 12:03 mysql --- and the install process locked, I have to kill the synaptic process which was freezed. Regards JPP2015-11-22 21:53:52 4936 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 2015-11-22 21:53:52 4936 [Note] Plugin 'FEDERATED' is disabled. mysqld: Table 'mysql.plugin' doesn't exist 2015-11-22 21:53:52 4936 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 2015-11-22 21:53:52 4936 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-11-22 21:53:52 4936 [Note] InnoDB: The InnoDB memory heap is disabled 2015-11-22 21:53:52 4936 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-11-22 21:53:52 4936 [Note] InnoDB: Memory barrier is not used 2015-11-22 21:53:52 4936 [Note] InnoDB: Compressed tables use zlib 1.2.8 2015-11-22 21:53:52 4936 [Note] InnoDB: Using Linux native AIO 2015-11-22 21:53:52 4936 [Note] InnoDB: Using CPU crc32 instructions 2015-11-22 21:53:52 4936 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-11-22 21:53:52 4936 [Note] InnoDB: Completed initialization of buffer pool 2015-11-22 21:53:52 4936 [Note] InnoDB: Highest supported file format is Barracuda. 2015-11-22 21:53:53 4936 [Note] InnoDB: 128 rollback segment(s) are active. 2015-11-22 21:53:53 4936 [Note] InnoDB: Waiting for purge to start 2015-11-22 21:53:53 4936 [Note] InnoDB: 5.6.27 started; log sequence number 1600618 2015-11-22 21:53:53 4936 [Note] Recovering after a crash using /var/log/mysql/mysql-bin 2015-11-22 21:53:53 4936 [Note] Starting crash recovery... 2015-11-22 21:53:53 4936 [Note] Crash recovery finished. 2015-11-22 21:53:53 4936 [Note] Server hostname (bind-address): '192.168.2.8'; port: 3306 2015-11-22 21:53:53 4936 [Note] - '192.168.2.8' resolves to '192.168.2.8'; 2015-11-22 21:53:53 4936 [Note] Server socket created on IP: '192.168.2.8'. 2015-11-22 21:53:53 4936 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.user' doesn't exist 2015-11-22 21:43:49 4810 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead. 2015-11-22 21:43:49 4810 [Note] Plugin 'FEDERATED' is disabled. mysqld: Table 'mysql.plugin' doesn't exist 2015-11-22 21:43:49 4810 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it. 2015-11-22 21:43:49 4810 [Note] InnoDB: Using atomics to ref count buffer pool pages 2015-11-22 21:43:49 4810 [Note] InnoDB: The InnoDB memory heap is disabled 2015-11-22 21:43:49 4810 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-11-22 21:43:49 4810 [Note] InnoDB: Memory barrier is not used 2015-11-22 21:43:49 4810 [Note] InnoDB: Compressed tables use zlib 1.2.8 2015-11-22 21:43:49 4810 [Note] InnoDB: Using Linux native AIO 2015-11-22 21:43:49 4810 [Note] InnoDB: Using CPU crc32 instructions 2015-11-22 21:43:49 4810 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-11-22 21:43:49 4810 [Note] InnoDB: Completed initialization of buffer pool 2015-11-22 21:43:49 4810 [Note] InnoDB: Highest supported file format is Barracuda. 2015-11-22 21:43:49 4810
Bug#798703: marked as done (wreport: ABI transition needed for libstdc++ v5)
Your message dated Mon, 23 Nov 2015 12:03:24 +0100 with message-id <20151123110324.ga6...@enricozini.org> and subject line Version 3.3 has been uploaded has caused the Debian Bug report #798703, regarding wreport: ABI transition needed for libstdc++ v5 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.) -- 798703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wreport Version: 2.14-1 Severity: serious Justification: breaks ABI without a package rename Tags: sid stretch User: debian-...@lists.debian.org Usertags: libstdc++-cxx11 Background[1]: libstdc++6 introduces a new ABI to conform to the C++11 standard, but keeps the old ABI to not break existing binaries. Packages which are built with g++-5 from experimental (not the one from testing/unstable) are using the new ABI. Libraries built from this source package export some of the new __cxx11 or B5cxx11 symbols, dropping other symbols. If these symbols are part of the API of the library, then this rebuild with g++-5 will trigger a transition for the library. In the case of wreport, std::string appears in functions in public headers (for example Var::format), so it seems very likely that a transition is needed. The transition normally consists of renaming the affected library packages, adding a v5 suffix (libwreport2v5). The SONAME should not be changed when doing this. If an upgrade to a new upstream SONAME is already planned, and that SONAME has never been available in Debian compiled with g++-4, then an alternative way to carry out the transition would be to bump the SONAME. These follow-up transitions for libstdc++ are not going through exactly the normal transition procedure, because many entangled transitions are going on at the same time, and the usual ordered transition procedure does not scale that far. When all the C++ libraries on which this library depends have started their transitions in unstable if required, this library should do the same, closing this bug; the release team will deal with binNMUs as needed. Looking at the build-dependencies of wreport, the only C++ library seems to be libwibble, which is static (and was already rebuilt). So this sub-transition is ready to start. The package might be NMU'd if there is no maintainer response. The release team have declared a 2 day NMU delay[2] for packages involved in the libstdc++ transition, in order to get unstable back to a usable state in a finite time. Regards, S [1] https://wiki.debian.org/GCC5#libstdc.2B-.2B-_ABI_transition [2] https://lists.debian.org/debian-devel-announce/2015/08/msg0.html --- End Message --- --- Begin Message --- Hello, version 3.3 of wreport has been uploaded, and it has built with gcc5: it looks like these bugs can be closed now. Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini signature.asc Description: PGP signature --- End Message ---
Processed (with 1 error): duplicate
Processing commands for cont...@bugs.debian.org:
> forcemerge 732739 691973
Bug #732739 [wicd] wicd daemon fails to start if /etc/resolv.conf is a broken
symlink
Bug #691973 {Done: David Paleino } [wicd] wicd-daemon.py
clobbers /etc/resolv.conf
Failed to forcibly merge 732739: Not altering archived bugs; see unarchive.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
691973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691973
732739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#805793: plainbox: Maintainer email is moderated mailing list
Hi Thank you for posting this bug. I will change the mailing list configuration to be non-moderated as we don't get that much spam to warrant this. Thanks ZK On Sun, Nov 22, 2015 at 4:25 PM, Tobias Frost wrote: > Source: plainbox > Severity: serious > Justification: Policy 3.3 > > Dear Maintainer, > > as per Policy 3.3 it is a violation of a must requirement, therefore RC, if > the Maintainer field moderates Debian-originated mails. > See also the Developer Reference 5.12 > > The maintainer must be specified in the Maintainer control field with > their correct name and a working email address. The email address given > in the Maintainer control field must accept mail from those role > accounts in Debian used to send automated mails regarding the package. > This includes non-spam mail from the bug-tracking system, all mail from > the Debian archive maintenance software, and other role accounts or > automated processes that are commonly agreed on by the project.[7] If > one person or team maintains several packages, they should use the same > form of their name and email address in the Maintainer fields of those > packages. > > -- System Information: > Debian Release: 8.2 > APT prefers stable > APT policy: (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.0.5-revert-done (SMP w/4 CPU cores) > Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: sysvinit (via /sbin/init) > > -- > Checkbox-devel mailing list > checkbox-de...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/checkbox-devel
Processed (with 1 error): duplicate
Processing commands for cont...@bugs.debian.org: > merge 732739 691973 Bug #732739 [wicd] wicd daemon fails to start if /etc/resolv.conf is a broken symlink Unable to merge bugs because: severity of #691973 is 'serious' not 'wishlist' done of #691973 is 'David Paleino ' not '' Failed to merge 732739: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 691973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691973 732739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#805828: [debian-mysql] Bug#805828: mysql-server-5.6: upgrade didn't work, package unusable, mysql does not start
Hi JP, thank you for your bugreport. Have you tried setting your datadir to the absolute folder (without any symlinks?) The log msg you reported states that your mysql database is missing. Can you provide older log messages? Cheers B 2015-11-22 22:02 GMT+01:00 jpp : > Package: mysql-server-5.6 > Version: 5.6.27-2 > Severity: critical > Justification: causes serious data loss > > Hello, > > I am using the "unstable" release and after the previous update Mysql is > unusable. > The configuration files where updated and the result is an unusable > database. > Mysql won't start giving me stranges messages. > The /var/lib/mysql is a symlinj to another location on another disk. > I saw that some configuration options where not ok : > innodb_data_home_dir = > innodb_data_file_path = > /var/lib/mysql/ibdata1:1024M;/var/lib/mysql/ibdata2:1024M:autoextend > No directory for innodb_data_home_dir ? > The "bind address" which was "0.0.0.0" has disapeared. > I try some workaround. If I use : > innodb_data_home_dir = /var/lib/mysql/ > innodb_data_file_path = ibdata1:1024M;ibdata2:1024M:autoextend > I get messages complaining on system error reading files. > > After a while I delete all "ib" files and relaunch the service with no > success, > the "ib..." files were recreated but the error.log mentionned that it can > bind > to this > address (127.0.0.1) and asking if another mysql process was running (this > is > not the case). > > I try to use a specific address "bind 192.168.2.8" and mysql does not start > with messages : > > 2015-11-22 21:53:53 4936 [Note] InnoDB: Waiting for purge to start > 2015-11-22 21:53:53 4936 [Note] InnoDB: 5.6.27 started; log sequence number > 1600618 > 2015-11-22 21:53:53 4936 [Note] Recovering after a crash using > /var/log/mysql > /mysql-bin > 2015-11-22 21:53:53 4936 [Note] Starting crash recovery... > 2015-11-22 21:53:53 4936 [Note] Crash recovery finished. > 2015-11-22 21:53:53 4936 [Note] Server hostname (bind-address): > '192.168.2.8'; > port: 3306 > 2015-11-22 21:53:53 4936 [Note] - '192.168.2.8' resolves to > '192.168.2.8'; > 2015-11-22 21:53:53 4936 [Note] Server socket created on IP: '192.168.2.8'. > 2015-11-22 21:53:53 4936 [ERROR] Fatal error: Can't open and lock privilege > tables: Table 'mysql.user' doesn't exist > > The upgrade was not successful and I get a fully crashed database. > > Regards > > JP P > > PS : I save some distinct error logs. > > > > > > -- System Information: > Debian Release: stretch/sid > APT prefers testing-updates > APT policy: (500, 'testing-updates'), (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.3.0-x (SMP w/8 CPU cores) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages mysql-server-5.6 depends on: > ii adduser3.113+nmu3 > ii debconf [debconf-2.0] 1.5.58 > ii init-system-helpers1.24 > ii initscripts2.88dsf-59.2 > ii libaio10.3.110-2 > ii libc6 2.19-22 > ii libdbi-perl1.634-1 > ii libgcc11:5.2.1-23 > ii libstdc++6 5.2.1-23 > ii libwrap0 7.6.q-25 > ii lsb-base 9.20150917 > ii mysql-client-5.6 5.6.27-2 > ii mysql-common 5.6.27-2 > ii mysql-server-core-5.6 5.6.27-2 > ii passwd 1:4.2-3.1 > ii perl 5.20.2-6 > ii psmisc 22.21-2.1 > ii zlib1g 1:1.2.8.dfsg-2+b1 > > Versions of packages mysql-server-5.6 recommends: > ii libhtml-template-perl 2.95-2 > > Versions of packages mysql-server-5.6 suggests: > ii bsd-mailx [mailx] 8.1.2-0.20150408cvs-1 > pn tinyca > > -- Configuration Files: > /etc/logcheck/ignore.d.paranoid/mysql-server-5_6 [Errno 13] Permission > denied: u'/etc/logcheck/ignore.d.paranoid/mysql-server-5_6' > /etc/logcheck/ignore.d.server/mysql-server-5_6 [Errno 13] Permission > denied: u'/etc/logcheck/ignore.d.server/mysql-server-5_6' > /etc/logcheck/ignore.d.workstation/mysql-server-5_6 [Errno 13] Permission > denied: u'/etc/logcheck/ignore.d.workstation/mysql-server-5_6' > /etc/mysql/mysql.cnf [Errno 2] No such file or directory: > u'/etc/mysql/mysql.cnf' > /etc/mysql/mysql.conf.d/mysqld.cnf changed: > [mysqld_safe] > socket = /var/run/mysqld/mysqld.sock > nice= 0 > [mysqld] > user= mysql > pid-file= /var/run/mysqld/mysqld.pid > socket = /var/run/mysqld/mysqld.sock > basedir = /usr > datadir = /var/lib/mysql > tmpdir = /tmp > lc-messages-dir = /usr/share/mysql > skip-external-locking > port= 3306 > bind-address= 192.168.2.8 > key_buffer_size = 16M > max_allowed_packet = 16M > thread_stack= 192K > thread_cache_size = 8 > myisam-recover = BACKUP > max_connections= 16 > query_cache_limit = 1M > query_cache_size
