Bug#788011: mutt fails to connect to imaps after update
Control: severity -1 important On 2015-06-07 Michal Hocko msts...@gmail.com wrote: Package: libgnutls-openssl27 Version: 3.3.15-5 Severity: critical Hi, mutt fails to connect to imaps:// server after updating from 3.3.15-2 to this version. It is not exactly clear to me what is wrong but it complains with the following message: gnutls_handshake: A TLS fatal alert has been received.(Bad record MAC)) mutt starts working again after downgrading to 3.3.15-2. I am sorry but I have no idea what additional information might be useful so please let me know what to provide to help debug the issue. [...] Hello, could you provide the name the server you were trying to use to faciliate reproducing the issue? 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' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788073: spamassassin: uninstallable with perl 5.22 owing to perl-modules dep
tags 788073 + pending thanks On Mon, Jun 08, 2015 at 12:01:50PM +0100, Dominic Hargreaves wrote: spamassassin depends on perl-modules (= 5.10) | libio-zlib-perl (= 1.04); however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. Fixed in svn. Given you already depend on perl, the above dependency clause should be dropped altogether - and given that = 5.10 has been in Debian for many releases, the dependency on perl could become unversioned. Also fixed in svn. Thanks noah signature.asc Description: Digital signature
Bug#788121: xhprof: add ppc64el support
Package: xhprof
Version: 0.9.4-2
Severity: important
Tags: patch
xhprof does not compile on ppc64el architecture because it contains a timing
x86 assembly instruction.
This bugs contains a backported patch from a submitted upstream solution that
adds support for this new architecture. The original submission could be seen
at:
https://github.com/clbr/xhprof/commit/6fe6c8ad11627f480deead2d99ab0fa6b0adf8a0
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: ppc64el (ppc64le)
Kernel: Linux 3.16.0-4-powerpc64le (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Index: xhprof-0.9.4/extension/xhprof.c
===
--- xhprof-0.9.4.orig/extension/xhprof.c
+++ xhprof-0.9.4/extension/xhprof.c
@@ -1219,10 +1219,22 @@ void hp_sample_check(hp_entry_t **entrie
* @author cjiang
*/
inline uint64 cycle_timer() {
- uint32 __a,__d;
uint64 val;
+
+#if defined(__i386__) || defined(__x86_64__)
+ uint32 __a,__d;
asm volatile(rdtsc : =a (__a), =d (__d));
(val) = ((uint64)__a) | (((uint64)__d)32);
+
+/* The builtin is available starting with GCC 4.8 */
+#elif defined(__powerpc__) \
+ ( __GNUC__ 4 || (__GNUC__ == 4 __GNUC_MINOR__ = 8))
+ val = __builtin_ppc_get_timebase();
+
+#else
+#error Unsupported platform
+#endif
+
return val;
}
Bug#786955: dgit should switch dependency from realpath to recent coreutils
Hi, 2015-06-08 16:20 GMT+02:00 Ian Jackson ijack...@chiark.greenend.org.uk: Petr Čech writes (Bug#786955: dgit should switch dependency from realpath to recent coreutils): Package: dgit Version: 0.22.1 Severity: normal ... as of coreutils 8.23-1 realpath has been merged into the mail package. Please adjust dependencies accordingly. I would suggest this: coreutils (= 8.23-1~) | realpath Thanks for the report. I'll make this change at an appropriate point. I have two questions, though: - You say into the mail package but then you talk about coreutils. What does the mail package refer to ? It should read into the main package. Sorry for confusion. - Does the existing coreutils have a Provides ? If so then good. If not then this bug needs a higher severity as current sid dgit would be uninstallable otherwise. No, realpath is provided as a transitional package. Bye, Petr Thanks, Ian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787976: grilo-plugins-0.2: grilo-plugins crashes in video_sanitize_string
On Sun, Jun 07, 2015 at 11:58:17AM +0200, Eugenio Accorsi wrote: grilo plugins crashes taking totem down with it (it depends on some file name I think) Upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=748604 I rebuilded the package using the 4 patches in the bugreport and grilo don't crash anymore. Thanks for the bug report. I'll try to take care of it this week and upload a new version. Berto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727918: libcwd: Ubuntu has a patch using autotools-dev
Source: libcwd Version: 1.0.4-1.1 Tags: patch The Ubuntu patch linked to from https://tracker.debian.org/pkg/libcwd works: http://patches.ubuntu.com/libc/libcwd/libcwd_1.0.4-1.1ubuntu2.patch md5sum: acf00c83832abc1842f327578ce3e634 libcwd_1.0.4-1.1ubuntu2.patch -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788116: gdm3: Please update to 3.16.1.1
Package: gdm3 Version: 3.14.1-7 Severity: wishlist Tags: patch Dear Maintainer, given that almost 70% of GNOME is now up-to-date in unstable/sid, it would be great if also gdm3 could be updated soon. Aiming for it, I've spent some spare time on updating the packaging and attached you'll find a debdiff from 3.14.1-7 to 3.16.1.1-1 (first eventual revision of this new upstream release). While it's known to fail[1] due to a classic autopoint-vs-intltoolize issue, I hope this initial update could help sprinting the upgrade. Cheers. [1] http://debomatic-amd64.debian.net/distribution#experimental/gdm3/3.16.1.1-1/buildlog -- System Information: Debian Release: stretch/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'buildd-experimental'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdm3 depends on: ii accountsservice 0.6.40-2 ii adduser 3.113+nmu3 ii dconf-cli 0.24.0-2 ii dconf-gsettings-backend 0.24.0-2 ii debconf [debconf-2.0] 1.5.56 ii gir1.2-gdm3 3.14.1-7 ii gnome-session [x-session-manager] 3.16.0-1 ii gnome-session-bin 3.16.0-1 ii gnome-settings-daemon 3.14.2-3 ii gnome-shell 3.14.4-1 ii gnome-terminal [x-terminal-emulator] 3.16.2-1 ii gsettings-desktop-schemas 3.16.1-1 ii libaccountsservice0 0.6.40-2 ii libaudit1 1:2.4.2-1 ii libc6 2.19-18 ii libcanberra-gtk3-00.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-02.31.4-2 ii libgdm1 3.14.1-7 ii libglib2.0-0 2.44.1-1 ii libglib2.0-bin2.44.1-1 ii libgtk-3-03.14.5-1 ii libpam-modules1.1.8-3.1 ii libpam-runtime1.1.8-3.1 ii libpam-systemd220-5 ii libpam0g 1.1.8-3.1 ii librsvg2-common 2.40.9-2 ii libselinux1 2.3-2 ii libsystemd0 220-5 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.3-1 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-1 ii libxrandr22:1.4.2-1+b1 ii lsb-base 4.1+Debian13+nmu1 ii metacity [x-window-manager] 1:3.14.3-1 ii mutter [x-window-manager] 3.14.4-2+b1 ii policykit-1 0.105-8 ii ucf 3.0030 ii x11-common1:7.7+9 ii x11-xserver-utils 7.7+4 ii xterm [x-terminal-emulator] 318-2 Versions of packages gdm3 recommends: ii at-spi2-core 2.16.0-1 ii desktop-base 8.0.2 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+2 ii xserver-xephyr 2:1.17.1-2 ii xserver-xorg 1:7.7+9 ii zenity 3.16.2-1 Versions of packages gdm3 suggests: ii gnome-orca3.16.2-1 ii libpam-gnome-keyring 3.16.0-2 -- debconf information: * shared/default-x-display-manager: gdm3 gdm3/daemon_name: /usr/sbin/gdm3 -- Matteo F. Vescovi || Debian Developer GnuPG KeyID: 4096R/0x8062398983B2CF7A diff -Nru gdm3-3.14.1/debian/changelog gdm3-3.16.1.1/debian/changelog --- gdm3-3.14.1/debian/changelog2015-04-04 09:20:26.0 +0200 +++ gdm3-3.16.1.1/debian/changelog 2015-06-08 09:48:19.0 +0200 @@ -1,3 +1,27 @@ +gdm3 (3.16.1.1-1) experimental; urgency=medium + + * Team upload + + * New upstream release +- debian/gdm3.install: empty install path dropped +- debian/patches/: patchset re-worked against v3.16.1.1 + - 08_frequent-users_greeter.patch refreshed + - 09_default_session.patch refreshed + - 16_xserver_path.patch refreshed + - 17_switch_on_finish.patch refreshed + - 18_all_displays_transient.patch dropped + - 19_switch_kill_greeter.patch refreshed + - 90_config_comments.patch refreshed + - 91_dconf_database_path.patch refreshed + - 92_systemd_unit.patch refreshed + - 93_disable_gvfs.patch refreshed + - 94_retain_xorg_log.patch refreshed + - 95_systemd-import-language-into-daemon-environment.patch dropped +(applied upstream) + - 96_plymouth-quit.patch dropped (applied upstream)
Bug#788106: debiandoc-sgml: debiandoc2pdf does not set -progname to kpsewhich
On Tue, Jun 09, 2015 at 01:34:02AM +0900, Osamu Aoki wrote: Hi, On Mon, Jun 08, 2015 at 07:09:43PM +0300, Ilya Anfimov wrote: Package: debiandoc-sgml Version: 1.2.29-1 Severity: normal Dear Maintainer, I have some specifics in kpse path search library configuration, and latex packages do not appear there by default. Whould you be so kind to add -progname pdflatex to kpsewhich calls in debiandoc2pdf, so to check exact availability of that packages for pdflatex? $ dpkg -S kpsewhich texlive-binaries: /usr/share/man/man1/kpsewhich.1.gz texlive-binaries: /usr/bin/kpsewhich $ zgrep kpsewhich `dpkg -L debiandoc-sgml` /usr/bin/debiandoc2latexpdf:if ! kpsewhich \ /usr/bin/debiandoc2latexpdf:if ! kpsewhich \ /usr/bin/debiandoc2latexpdf:if ! kpsewhich \ /usr/bin/debiandoc2latexps:if ! kpsewhich \ /usr/bin/debiandoc2latexps:if ! kpsewhich \ /usr/bin/debiandoc2latexps:if ! kpsewhich \ /usr/bin/debiandoc2latexdvi:if ! kpsewhich \ /usr/bin/debiandoc2latexdvi:if ! kpsewhich \ /usr/bin/debiandoc2latexdvi:if ! kpsewhich \ /usr/bin/debiandoc2ps:if ! kpsewhich \ /usr/bin/debiandoc2ps:if ! kpsewhich \ /usr/bin/debiandoc2ps:if ! kpsewhich \ /usr/bin/debiandoc2dvi:if ! kpsewhich \ /usr/bin/debiandoc2dvi:if ! kpsewhich \ /usr/bin/debiandoc2dvi:if ! kpsewhich \ /usr/bin/debiandoc2pdf:if ! kpsewhich \ /usr/bin/debiandoc2pdf:if ! kpsewhich \ /usr/bin/debiandoc2pdf:if ! kpsewhich \ I do not understand what you are after. Please assume me as total newbie for latex. What is add -progname pdflatex? I have no idea what you are asking. Please report woth log of what you did and where in the installed files needs to be changed. (Patch to the source is even better.) Oh, sorry. The patch is attached. kpathsearch library, used by texlive programs to find it's files in local filesystem, asks for program name for search con- fig. Usually most TeX and even LaTeX style files and top-level addons could be found without specifing program name, to simplify searching in distinct tex flavours -- tex, latex, luatex, pdfla- tex, ... However, this is changed on my system, and debiandoc2... scripts reports uninstalled latex packages despite the fact that packages are installed latex/pdflatex runs just fine from debiandoc. Attached patch adds -progname to respective calls to kpsewich. Index: debiandoc-sgml-1.2.29/tools/bin/template === --- debiandoc-sgml-1.2.29.orig/tools/bin/template +++ debiandoc-sgml-1.2.29/tools/bin/template @@ -155,10 +155,17 @@ then fi @@@end-latexpdf-active@@@ -@@@start-latexdvi-latexps-latexpdf-active@@@ +@@@start-latexdvi-latexps-active@@@ ## -- ## check for presence of used latex styles -if ! kpsewhich \ +if ! kpsewhich -progname latex \ +@@@end-latexdvi-latexps-active@@@ +@@@start-latexpdf-active@@@ +## -- +## check for presence of used pdflatex styles +if ! kpsewhich -progname pdflatex \ +@@@end-latexpdf-active@@@ +@@@start-latexdvi-latexps-latexpdf-active@@@ fancyhdr.sty \ helvet.sty \ hyperref.sty \ @@ -174,10 +181,17 @@ then fi @@@end-latexdvi-latexps-latexpdf-active@@@ -@@@start-latexdvi-latexps-latexpdf-active@@@ +@@@start-latexdvi-latexps-active@@@ ## -- ## check for presence of used latex styles -if ! kpsewhich \ +if ! kpsewhich -progname latex \ +@@@end-latexdvi-latexps-active@@@ +@@@start-latexpdf-active@@@ +## -- +## check for presence of used pdflatex styles +if ! kpsewhich -progname pdflatex \ +@@@end-latexpdf-active@@@ +@@@start-latexdvi-latexps-latexpdf-active@@@ footmisc.sty \ paralist.sty \ vmargin.sty \ @@ -189,10 +203,17 @@ then fi @@@end-latexdvi-latexps-latexpdf-active@@@ -@@@start-latexdvi-latexps-latexpdf-active@@@ +@@@start-latexdvi-latexps-active@@@ ## -- ## check for presence of used latex styles -if ! kpsewhich \ +if ! kpsewhich -progname latex \ +@@@end-latexdvi-latexps-active@@@ +@@@start-latexpdf-active@@@ +## -- +## check for presence of used pdflatex styles +if ! kpsewhich -progname pdflatex \ +@@@end-latexpdf-active@@@ +@@@start-latexdvi-latexps-latexpdf-active@@@ wasysym.sty \ /dev/null 21 then
Bug#788042:
I did some more testing, and I believe it may be an upstream issue. Removing the xdg-utils package results in it opening. However, oddly, while xdg-utils is installed, the window name of the failure message is Exo open.
Bug#788011: mutt fails to connect to imaps after update
On 2015-06-08 Michal Hocko msts...@gmail.com wrote: On Mon, Jun 08, 2015 at 07:23:31PM +0200, Andreas Metzler wrote: [...] could you provide the name the server you were trying to use to faciliate reproducing the issue? This is a company mail server so I am not sure it would help you. It depends whether it is accessible from the internet. ;-) Are there any commands I can run to give you sufficient information? mutt with -d 5 doesn't tell more than the error message I've already provided. As a first step you could check whether gnutls-cli can still connect and if not post a full log (gnutls-cli -d 4711 -p imaps host) Please make sure your system is up-to-date sid, *partial* upgrades are currently broken due to the nettle transition. 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' -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788109: wishlist: would be good to offer an alsa binary for systems without pulseaudio
Package: gqrx-sdr
Version: 2.3.1-2.0.1
Severity: wishlist
Dear Maintainer,
Hi. I recently installed gqrx-sdr from jessie (2.3.1-2) and found that
it required pulseaudio. I don't run pulse on this system as it breaks
some other software.
Although gqrx-sdr installed okay without the pulseaudio daemon being
installed, gqrx did not start successfully. AFAIK, there is no way to
disable libpulse at runtime.
I decided to recompile with the attached patch to build an alsa binary.
This works. I'd like to see this supported by debian, perhaps by
building two packages, gqrx-pulse and gqrx-alsa. Please consider this
and other options to support a non-pulseaudio system.
Thank you.
-Chris
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages gqrx-sdr depends on:
ii libboost-program-options1.55.0 1.55.0+dfsg-3
ii libboost-system1.55.0 1.55.0+dfsg-3
ii libc6 2.19-18
ii libgcc1 1:4.9.2-10
ii libgnuradio-analog3.7.5 3.7.5-5
ii libgnuradio-audio3.7.5 3.7.5-5
ii libgnuradio-blocks3.7.5 3.7.5-5
ii libgnuradio-fft3.7.53.7.5-5
ii libgnuradio-filter3.7.5 3.7.5-5
ii libgnuradio-osmosdr0.1.30.1.3-2
ii libgnuradio-pmt3.7.53.7.5-5
ii libgnuradio-runtime3.7.53.7.5-5
ii libqt4-network 4:4.8.6+git64-g5dc8b2b+dfsg-3
ii libqt4-svg 4:4.8.6+git64-g5dc8b2b+dfsg-3
ii libqtcore4 4:4.8.6+git64-g5dc8b2b+dfsg-3
ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3
ii libstdc++6 4.9.2-10
ii libvolk0.0.03.7.5-5
gqrx-sdr recommends no packages.
gqrx-sdr suggests no packages.
-- no debconf information
Description: build without pulse audio support
.
gqrx-sdr (2.3.1-2.0.1) unstable; urgency=low
.
* Build without pulse audio
Author: Chris Ruvolo cruv...@gmail.com
--- gqrx-sdr-2.3.1.orig/gqrx.pro
+++ gqrx-sdr-2.3.1/gqrx.pro
@@ -30,8 +30,8 @@ CONFIG += link_pkgconfig
unix:!macx {
packagesExist(libpulse libpulse-simple) {
# Comment out to use gr-audio (not recommended with ALSA and Funcube Dongle Pro)
-AUDIO_BACKEND = pulse
-message(Gqrx configured with pulseaudio backend)
+#AUDIO_BACKEND = pulse
+#message(Gqrx configured with pulseaudio backend)
}
}
Bug#787767: [uscan] wrong sort order during recursive scanning
On Thursday 04 June 2015 17:07:42 Daniel Leidert wrote: Now why does it do that? Further why does it output 7..5 instead of 7.0.5 in the output above? Perl '||' operator is used on '0' version field instead of '//' (defined-or) Might this be related to the wrong result? yes. I've fixed the bug. Will archive it soon All the best -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788117: pep8: please update pep8
Source: pep8 Version: 1.5.7-2 Severity: wishlist Please update pep8 in Debian. It's a preliminary needed for my ITP of Prospector [1] (currently needs = 1.6.0). Thanks in advance, Daniel Stender [1] https://bugs.debian.org/781165 ITP: prospector -- Python code analysis tool -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788118: RM: libzabbix-api-perl -- ROM; Obsolted, superseeded by Zabbix2-API, to be used with Zabbix 1.x
Package: ftp.debian.org Severity: normal Hi FTP masters ROM is partially correct, I'm member of the Debian Perl Group but not in Uploaders of the package. libzabbix-api-perl should be removed from unstable as it is obsolted, superseeded by Zabbix2::API. Quoting upstream: If you are using Zabbix 2.x though (which you probably are if you are running a system recent enough to have a perl that emits warnings on given/when), consider using Zabbix2-API instead. It has more dependencies but I am working on it much more often than Zabbix-API. If you are really using Zabbix 1.8.x, there is a branch on the Zabbix-API github repository with some work done towards compatibility with Perl 5.8, which may be of interest to you as well (no given/when there, so presumably no warnings). https://rt.cpan.org/Public/Bug/Display.html?id=97183#txn-1387462 Dmitry Smirnov agreed on the removal, see #788006 Could you please remove libzabbix-api-perl from unstable? Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788011: mutt fails to connect to imaps after update
On Mon, Jun 08, 2015 at 07:23:31PM +0200, Andreas Metzler wrote: [...] Hello, Hi, could you provide the name the server you were trying to use to faciliate reproducing the issue? This is a company mail server so I am not sure it would help you. Are there any commands I can run to give you sufficient information? mutt with -d 5 doesn't tell more than the error message I've already provided. -- Michal Hocko -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#786487: wordpress: 4.2.2 needs php-getid3 from unstable, request for backport or dependency version downgrade
On lun., 2015-06-08 at 15:53 +0200, Alessandro Ghedini wrote: Sure, whatever. I'll just let someone else from the team handle wordpress from now on. Hey, I'll process the wordpress DSA sometimes during the week, when I have time processing the backlog on the bug and understanding precisely the issue. Regards, -- Yves-Alexis Perez - Debian Security signature.asc Description: This is a digitally signed message part
Bug#788113: proot: FTBFS on arm64
Source: proot
Version: 5.1.0-1
Tags: patch
Some arm64 stuff was missing from the latest release.
This patch adds it. It built when I tried it, but I
haven't done any other testing.
diff -ru proot-5.1.0.orig/src/arch.h proot-5.1.0/src/arch.h
--- proot-5.1.0.orig/src/arch.h
+++ proot-5.1.0/src/arch.h
@@ -125,6 +125,9 @@
#define OFFSETOF_STAT_UID_32 0
#define OFFSETOF_STAT_GID_32 0
+#define EXEC_PIC_ADDRESS 0x5000
+#define INTERP_PIC_ADDRESS 0x6f00
+
#elif defined(ARCH_X86)
#define SYSNUMS_HEADER1 syscall/sysnums-i386.h
diff -ru proot-5.1.0.orig/src/loader/assembly-arm64.h proot-5.1.0/src/loader/assembly-arm64.h
--- /dev/null
+++ proot-5.1.0/src/loader/assembly-arm64.h
@@ -0,0 +1,93 @@
+/* -*- c-set-style: KR; c-basic-offset: 8 -*-
+ *
+ * This file is part of PRoot.
+ *
+ * Copyright (C) 2014 STMicroelectronics
+ *
+ * This program is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU General Public License as
+ * published by the Free Software Foundation; either version 2 of the
+ * License, or (at your option) any later version.
+ *
+ * This program is distributed in the hope that it will be useful, but
+ * WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
+ * 02110-1301 USA.
+ */
+
+#define BRANCH(stack_pointer, destination) do { \
+ asm volatile ( \
+ // Restore initial stack pointer. \n\t \
+ mov sp, %0\n\t \
+ \n\t \
+ // Clear rtld_fini. \n\t \
+ mov x0, #0\n\t \
+ \n\t \
+ // Start the program. \n\t \
+ br %1 \n \
+ : /* no output */\
+ : r (stack_pointer), r (destination) \
+ : memory, sp, x0); \
+ __builtin_unreachable();\
+ } while (0)
+
+#define PREPARE_ARGS_1(arg1_)\
+ register word_t arg1 asm(x0) = arg1_; \
+
+#define PREPARE_ARGS_3(arg1_, arg2_, arg3_) \
+ PREPARE_ARGS_1(arg1_)\
+ register word_t arg2 asm(x1) = arg2_; \
+ register word_t arg3 asm(x2) = arg3_; \
+
+#define PREPARE_ARGS_4(arg1_, arg2_, arg3_, arg4_) \
+ PREPARE_ARGS_3(arg1_, arg2_, arg3_) \
+ register word_t arg4 asm(x3) = arg4_;
+
+#define PREPARE_ARGS_6(arg1_, arg2_, arg3_, arg4_, arg5_, arg6_) \
+ PREPARE_ARGS_3(arg1_, arg2_, arg3_)\
+ register word_t arg4 asm(x3) = arg4_;\
+ register word_t arg5 asm(x4) = arg5_;\
+ register word_t arg6 asm(x5) = arg6_;
+
+#define OUTPUT_CONTRAINTS_1 \
+ r (arg1)
+
+#define OUTPUT_CONTRAINTS_3 \
+ OUTPUT_CONTRAINTS_1, \
+ r (arg2), r (arg3)
+
+#define OUTPUT_CONTRAINTS_4 \
+ OUTPUT_CONTRAINTS_3, \
+ r (arg4)
+
+#define OUTPUT_CONTRAINTS_6\
+ OUTPUT_CONTRAINTS_3,\
+ r (arg4), r (arg5), r (arg6)
+
+#define SYSCALL(number_, nb_args, args...) \
+ ({ \
+ register word_t number asm(w8) = number_; \
+ register word_t result asm(x0); \
+ PREPARE_ARGS_##nb_args(args) \
+ asm volatile (\
+svc #0x \n\t \
+: =r (result) \
+: r (number), \
+OUTPUT_CONTRAINTS_##nb_args \
+: memory); \
+ result; \
+ })
+
+#define OPENAT 56
+#define CLOSE 57
+#define MMAP 222
+#define MMAP_OFFSET_SHIFT 0
+#define EXECVE 221
+#define EXIT 93
+#define PRCTL 167
+
diff -ru proot-5.1.0.orig/src/loader/loader.c proot-5.1.0/src/loader/loader.c
--- proot-5.1.0.orig/src/loader/loader.c
+++ proot-5.1.0/src/loader/loader.c
@@ -39,6 +39,8 @@
#include loader/assembly-x86_64.h
#elif defined(ARCH_ARM_EABI)
#include loader/assembly-arm.h
+#elif defined(ARCH_ARM64)
+#include loader/assembly-arm64.h
#elif defined(ARCH_X86)
#include loader/assembly-x86.h
#else
@@ -134,7 +136,11 @@
/* Fall through. */
case LOAD_ACTION_OPEN:
+#ifdef OPENAT
+ fd = SYSCALL(OPENAT, 4, AT_FDCWD, stmt-open.string_address, O_RDONLY, 0);
+#else
fd = SYSCALL(OPEN, 3, stmt-open.string_address, O_RDONLY, 0);
+#endif
if (unlikely((int) fd 0))
FATAL();
Bug#788115: gnome-shell: 3.16: Lockscreen keyboard shortcut needs gnome-settings-daemon 3.16
Package: gnome-shell Version: 3.16.2-1 Severity: normal gnome-shell 3.16 requires gnome-settings-daemon 3.16, otherwise the keyboard shortcuts to lock the screen do not work anymore, as the D-Bus signature of a method seems to have changed. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (990, 'unstable'), (100, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii evolution-data-server3.16.2-4 ii gir1.2-accountsservice-1.0 0.6.40-2 ii gir1.2-atspi-2.0 2.16.0-1 ii gir1.2-caribou-1.0 0.4.18.1-1 ii gir1.2-clutter-1.0 1.22.2-1 ii gir1.2-freedesktop 1.44.0-1+b1 ii gir1.2-gcr-3 3.16.0-1 ii gir1.2-gdesktopenums-3.0 3.16.1-1 ii gir1.2-gdm3 3.14.1-7 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.44.0-1+b1 ii gir1.2-gnomebluetooth-1.03.16.1-1 ii gir1.2-gnomedesktop-3.0 3.16.2-2 ii gir1.2-gtk-3.0 3.16.3-2 ii gir1.2-gweather-3.0 3.16.1-1 ii gir1.2-ibus-1.0 1.5.9-1 ii gir1.2-mutter-3.03.16.2-1 ii gir1.2-networkmanager-1.01.0.2-2 ii gir1.2-nmgtk-1.0 1.0.2-1 ii gir1.2-pango-1.0 1.36.8-3 ii gir1.2-polkit-1.00.105-8 ii gir1.2-soup-2.4 2.50.0-2 ii gir1.2-telepathyglib-0.120.24.1-1 ii gir1.2-telepathylogger-0.2 0.8.1-1 ii gir1.2-upowerglib-1.00.99.3-1+b1 ii gjs 1.42.0-1 ii gnome-backgrounds3.16.0-1 ii gnome-icon-theme-symbolic3.12.0-1 ii gnome-settings-daemon3.16.2-1 ii gnome-shell-common 3.16.2-1 ii gnome-themes-standard3.16.2-1 ii gsettings-desktop-schemas3.16.1-1 ii libatk-bridge2.0-0 2.16.0-1 ii libatk1.0-0 2.16.0-2 ii libc62.19-18 ii libcairo21.14.2-2 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libclutter-1.0-0 1.22.2-1 ii libcogl-pango20 1.20.0-2 ii libcogl201.20.0-2 ii libcroco30.6.8-3+b1 ii libdbus-glib-1-2 0.102-1 ii libecal-1.2-18 3.16.2-4 ii libedataserver-1.2-203.16.2-4 ii libgcr-base-3-1 3.16.0-1 ii libgdk-pixbuf2.0-0 2.31.4-2 ii libgirepository-1.0-11.44.0-1+b1 ii libgjs0e [libgjs0-libmozjs-24-0] 1.42.0-1 ii libglib2.0-0 2.44.1-1 ii libgstreamer1.0-01.4.5-2 ii libgtk-3-0 3.16.3-2 ii libical1a1.0-1.3 ii libjson-glib-1.0-0 1.0.4-1 ii libmozjs-24-024.2.0-3 ii libmutter0f 3.16.2-1 ii libnm-glib4 1.0.2-2 ii libnm-util2 1.0.2-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-0 1.36.8-3 ii libpolkit-agent-1-0 0.105-8 ii libpolkit-gobject-1-00.105-8 ii libpulse-mainloop-glib0 6.0-2 ii libpulse06.0-2 ii libsecret-1-00.18.2-1 ii libstartup-notification0 0.12-4 ii libsystemd0 220-5 ii libtelepathy-glib0 0.24.1-1 ii libx11-6 2:1.6.3-1 ii libxfixes3 1:5.0.1-2+b2 ii mutter 3.16.2-1 ii python3 3.4.2-2 ii telepathy-mission-control-5 1:5.16.3-1 Versions of packages gnome-shell recommends: ii
Bug#788110: jessie-pu: package libio-socket-ssl-perl/2.002-2+deb8u1
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Hi stable release managers,
I would like to propose an update for libio-socket-ssl-perl through
jessie-pu to address #788035. Upstream fixed that in 2.006:
- make PublicSuffix::_default_data thread safe
Full changelog:
+libio-socket-ssl-perl (2.002-2+deb8u1) jessie; urgency=medium
+
+ * Add 0001-make-PublicSuffix-_default_data-thread-safe-by-stori.patch.
+Make PublicSuffix::_default_data thread safe by storing the default data
+inside a function inside within __DATA__.
+Thanks to Jonny Schulz i...@bloonix.org for the report (Closes: #788035)
+
+ -- Salvatore Bonaccorso car...@debian.org Mon, 08 Jun 2015 09:28:47 +0200
Attached is the proposed debdiff. Could you consider it for the next
jessie point release (yes I know will only be in some months ;-)).
Regards,
Salvatore
diff -Nru libio-socket-ssl-perl-2.002/debian/changelog libio-socket-ssl-perl-2.002/debian/changelog
--- libio-socket-ssl-perl-2.002/debian/changelog 2014-11-01 23:43:45.0 +0100
+++ libio-socket-ssl-perl-2.002/debian/changelog 2015-06-08 13:51:54.0 +0200
@@ -1,3 +1,12 @@
+libio-socket-ssl-perl (2.002-2+deb8u1) jessie; urgency=medium
+
+ * Add 0001-make-PublicSuffix-_default_data-thread-safe-by-stori.patch.
+Make PublicSuffix::_default_data thread safe by storing the default data
+inside a function inside within __DATA__.
+Thanks to Jonny Schulz i...@bloonix.org for the report (Closes: #788035)
+
+ -- Salvatore Bonaccorso car...@debian.org Mon, 08 Jun 2015 09:28:47 +0200
+
libio-socket-ssl-perl (2.002-2) unstable; urgency=medium
* Add 0001-use-only-ICANN-part-in-public-suffix-list.patch.
diff -Nru libio-socket-ssl-perl-2.002/debian/patches/0001-make-PublicSuffix-_default_data-thread-safe-by-stori.patch libio-socket-ssl-perl-2.002/debian/patches/0001-make-PublicSuffix-_default_data-thread-safe-by-stori.patch
--- libio-socket-ssl-perl-2.002/debian/patches/0001-make-PublicSuffix-_default_data-thread-safe-by-stori.patch 1970-01-01 01:00:00.0 +0100
+++ libio-socket-ssl-perl-2.002/debian/patches/0001-make-PublicSuffix-_default_data-thread-safe-by-stori.patch 2015-06-08 13:51:54.0 +0200
@@ -0,0 +1,64 @@
+From fbf66f20daf5df2bc70509870ba98e61de7e56e1 Mon Sep 17 00:00:00 2001
+From: Steffen Ullrich steffen_ullr...@genua.de
+Date: Sat, 22 Nov 2014 21:39:18 +0100
+Subject: [PATCH] make PublicSuffix::_default_data thread safe by storing the
+ default data inside a function inside within __DATA__
+
+---
+ lib/IO/Socket/SSL/PublicSuffix.pm | 19 ++-
+ 1 file changed, 14 insertions(+), 5 deletions(-)
+
+diff --git a/lib/IO/Socket/SSL/PublicSuffix.pm b/lib/IO/Socket/SSL/PublicSuffix.pm
+index a84aacd..8d3fa9b 100644
+--- a/lib/IO/Socket/SSL/PublicSuffix.pm
b/lib/IO/Socket/SSL/PublicSuffix.pm
+@@ -292,7 +292,7 @@ sub public_suffix {
+ my $data;
+ sub _default_data {
+ if ( ! defined $data ) {
+- $data = do { local $/; DATA };
++ $data = _builtin_data();
+ $data =~s{^// ===END ICANN DOMAINS.*}{}ms
+ or die cannot find END ICANN DOMAINS;
+ }
+@@ -309,8 +309,15 @@ sub update_self_from_url {
+ local $/ = \n;
+ while ($fh) {
+ $code .= $_;
+- $code =~m{\A__DATA__\r?\n\Z} and last;
++ m{'END_BUILTIN_DATA'} and last;
+ }
++my $tail;
++while ($fh) {
++ m{\AEND_BUILTIN_DATA\r?\n} or next;
++ $tail = $_;
++ last;
++}
++$tail .= do { local $/; $fh };
+ close($fh);
+
+ require LWP::UserAgent;
+@@ -335,11 +342,10 @@ sub update_self_from_url {
+ }
+
+ open( $fh,':utf8',$dst ) or die open $dst: $!;
+-print $fh $code;
++print $fh $code.$tail;
+ }
+
+-1;
+-__DATA__
++sub _builtin_data { return 'END_BUILTIN_DATA' }
+ // This Source Code Form is subject to the terms of the Mozilla Public
+ // License, v. 2.0. If a copy of the MPL was not distributed with this
+ // file, You can obtain one at http://mozilla.org/MPL/2.0/.
+@@ -9154,3 +9160,6 @@ za.net
+ za.org
+
+ // ===END PRIVATE DOMAINS===
++
++END_BUILTIN_DATA
++1;
+--
+2.1.4
+
diff -Nru libio-socket-ssl-perl-2.002/debian/patches/series libio-socket-ssl-perl-2.002/debian/patches/series
--- libio-socket-ssl-perl-2.002/debian/patches/series 2014-11-01 23:43:45.0 +0100
+++ libio-socket-ssl-perl-2.002/debian/patches/series 2015-06-08 13:51:54.0 +0200
@@ -1 +1,2 @@
0001-use-only-ICANN-part-in-public-suffix-list.patch
+0001-make-PublicSuffix-_default_data-thread-safe-by-stori.patch
Bug#788112: beets: no manpage for package
Source: beets Version: 1.3.13 Severity: wishlist Dear Maintainer, wishlist for manpage package beets -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787391: transition: evolution-data-server
Control: tag -1 confirmed On 2015-06-03 19:13, Emilio Pozuelo Monfort wrote: I have uploaded evolution-data-server 3.16 to experimental, which bumps the SONAMEs of its libraries. Please go ahead as soon as you're ready. -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787364: ifup@.service does not start any more with systemd 220
Package: udev Followup-For: Bug #787364 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I am getting ifup working automatically with udev 218-10 but udev 219-10 fails to do an automatic ifup. *** End of the template - remove these template lines *** -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.1.0-rc7 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: sysvinit (via /sbin/init) Versions of packages udev depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii libacl12.2.52-2 ii libblkid1 2.26.2-6 ii libc6 2.19-18 ii libkmod2 20-1 ii libselinux12.3-2 ii libudev1 218-10 ii lsb-base 4.1+Debian13+nmu1 ii procps 2:3.3.9-9 ii util-linux 2.26.2-6 udev recommends no packages. udev suggests no packages. -- debconf-show failed P: /devices/LNXSYSTM:00 E: DEVPATH=/devices/LNXSYSTM:00 E: MODALIAS=acpi:LNXSYSTM: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/AWY0001:00 E: DEVPATH=/devices/LNXSYSTM:00/AWY0001:00 E: MODALIAS=acpi:AWY0001: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:00 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:01 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:01 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:02 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:02 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:03 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:03 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:04 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:04 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXCPU:05 E: DEVPATH=/devices/LNXSYSTM:00/LNXCPU:05 E: MODALIAS=acpi:LNXCPU: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXPWRBN:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00 E: DRIVER=button E: MODALIAS=acpi:LNXPWRBN: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 E: EV=3 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: KEY=10 0 E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw E: NAME=Power Button E: PHYS=LNXPWRBN/button/input0 E: PRODUCT=19/0/1/0 E: PROP=0 E: SUBSYSTEM=input E: USEC_INITIALIZED=367852 P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event2 N: input/event2 E: BACKSPACE=guess E: DEVNAME=/dev/input/event2 E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event2 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_PATH=acpi-LNXPWRBN:00 E: ID_PATH_TAG=acpi-LNXPWRBN_00 E: MAJOR=13 E: MINOR=66 E: SUBSYSTEM=input E: TAGS=:power-switch: E: USEC_INITIALIZED=421415 E: XKBLAYOUT=us E: XKBMODEL=pc102 E: XKBOPTIONS=lv3:rwin_switch,compose:lwin,terminate:ctrl_alt_bksp E: XKBVARIANT=altgr-intl P: /devices/LNXSYSTM:00/LNXSYBUS:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00 E: MODALIAS=acpi:LNXSYBUS: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00 E: MODALIAS=acpi:PNP0A03: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C02:04 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C02:04 E: MODALIAS=acpi:PNP0C02: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0C02:00 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:00/PNP0C02:00 E: MODALIAS=acpi:PNP0C02: E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:01 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:01 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:02 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:02 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:03 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:03 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:04 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:04 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:05 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:05 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:06 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:06 E: SUBSYSTEM=acpi P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07 E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07 E:
Bug#788111: dateutils: Problems with input and output formats
Package: dateutils Version: 0.3.1-1.1 Severity: normal Dear Maintainer, The input format %y does not work as per the documentation. Only %Y works: andrewg@xen:~$ dateutils.ddiff -i %y%m%d%H%M%S -f %S now 20150407075744 ddiff: cannot make sense of `20150407075744' using the given input formats andrewg@xen:~$ dateutils.ddiff -i %Y%m%d%H%M%S -f %S now 20150407075744 -5393469 Also, the output format %d doesn't work when used by itself (but does work in combination with other format specifiers, strangely): andrewg@xen:~$ dateutils.ddiff -i %Y%m%d%H%M%S -f %d %S 20150407075744 now 62 36520 andrewg@xen:~$ dateutils.ddiff -i %Y%m%d%H%M%S -f %d 20150407075744 now 0 andrewg@xen:~$ dateutils.ddiff -i %Y%m%d%H%M%S -f %S 20150407075744 now 5393331 -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.0.4-x86-linode75 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dateutils depends on: ii libc6 2.19-18 dateutils recommends no packages. dateutils suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788114: dpkg-source: cannot unpack on tmpfs - 'Invalid cross-device link'
Package: dpkg-dev Version: 1.18.1 Severity: normal When unpacking in /tmp, which is a tmpfs, $ dpkg-source -x ipsec-tools_0.8.2+20140711-3.dsc dpkg-source: info: extracting ipsec-tools in ipsec-tools-0.8.2+20140711 dpkg-source: info: unpacking ipsec-tools_0.8.2+20140711.orig.tar.gz dpkg-source: error: unable to rename /tmp/ipsec-tools_0.8.2+20140711.orig.tar.gz.tmp-extract.30RfU/ipsec-tools-0.8.2 to ipsec-tools-0.8.2+20140711: Invalid cross-device link -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-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 Init: systemd (via /run/systemd/system) Versions of packages dpkg-dev depends on: ii base-files8 ii binutils 2.25-4 ii bzip2 1.0.6-7+b2 ii libdpkg-perl 1.18.1 ii make 4.0-8.1 ii patch 2.7.3-1 ii xz-utils 5.1.1alpha+20120614-2+b3 Versions of packages dpkg-dev recommends: ii build-essential 11.7 ii clang-3.5 [c-compiler] 1:3.5-9 ii fakeroot 1.20.2-1 ii gcc [c-compiler] 4:4.9.2-1 ii gcc-4.4 [c-compiler] 4.4.7-8 ii gcc-4.6 [c-compiler] 4.6.4-7 ii gcc-4.7 [c-compiler] 4.7.4-3 ii gcc-4.8 [c-compiler] 4.8.4-1 ii gcc-4.9 [c-compiler] 4.9.2-10 ii gcc-5 [c-compiler] 5-20150205-1 ii gnupg1.4.18-6 ii gnupg2 2.0.26-4 ii gpgv 1.4.18-6 ii libalgorithm-merge-perl 0.08-2 Versions of packages dpkg-dev suggests: ii debian-keyring 2014.12.10 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787891: gem2deb: [PATCH] please make generation of gemspec file from metadata.yml reproducible
On 06/06/15 at 13:42 -0300, Juan Picca wrote: Bug #779631 fixes this problem too, but in a better manner for me. Indeed, that's a better place to fix that. Lucas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788120: ikiwiki: Upgrade from wheezy to jessie leaves svn-backed wiki in non-updating state
Package: ikiwiki Version: 3.20141016.2 Severity: important Tags: upstream We upgraded from wheezy to jessie We have an SVN-backed ikiwiki with CGI enabled After upgrading, editing via the web interface/CGI failed with an obscure error about no element found, similar to https://ikiwiki.info/forum/using_svn+ssh_with_ikiwiki/ Editing and committing via SVN resulted in a silent failure of the post-commit hook. Running ikiwiki-mass-rebuild revealed the problem: ikiwiki's own working copy of the wiki needed svn upgrade running on it as SVN had updated versions. Once this was done, a mass-rebuild put us back in working order. It would be nice if the upgrade process automatically ran svn update. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages ikiwiki depends on: ii libhtml-parser-perl 3.71-1+b3 ii libhtml-scrubber-perl 0.11-1 ii libhtml-template-perl 2.95-1 ii libjson-perl2.61-1 ii libtext-markdown-discount-perl 0.11-1+b1 ii liburi-perl 1.64-1 ii libyaml-libyaml-perl0.41-6 ii perl5.20.2-3+deb8u1 Versions of packages ikiwiki recommends: ii gcc [c-compiler] 4:4.9.2-2 ii gcc-4.4 [c-compiler] 4.4.7-2 ii gcc-4.9 [c-compiler] 4.9.2-10 ii git [git-core] 1:2.1.4-2.1 ii libauthen-passphrase-perl0.008-1 ii libc6-dev [libc-dev] 2.19-18 ii libcgi-formbuilder-perl 3.09-2 ii libcgi-pm-perl 4.09-1 ii libcgi-session-perl 4.48-1 ii libcrypt-ssleay-perl 0.58-1+b2 ii libgravatar-url-perl 1.06-1 ii liblwpx-paranoidagent-perl 1.10-5 ii libmail-sendmail-perl0.79.16-1 ii libnet-openid-consumer-perl 1.15-1 ii librpc-xml-perl 0.78-2 ii libterm-readline-gnu-perl1.24-2+b1 ii libtimedate-perl 2.3000-2 ii libxml-simple-perl 2.20-1 ii mercurial3.1.2-2+deb8u1 ii subversion 1.8.10-6 Versions of packages ikiwiki suggests: pn dvipng none ii file1:5.22+15-2 ii gettext 0.19.3-2 pn ghostscript none pn graphviznone pn libfile-mimeinfo-perl none pn libhighlight-perl none ii libhtml-tree-perl 5.03-1 ii liblocale-gettext-perl 1.05-8+b1 pn libmagickcore-extra none ii libmailtools-perl 2.13-1 pn libnet-amazon-s3-perl none pn libnet-inet6glue-perl none pn libsearch-xapian-perl none pn libsort-naturally-perl none pn libsparkline-phpnone pn libtext-csv-perlnone pn libtext-multimarkdown-perl none pn libtext-textile-perlnone pn libtext-typography-perl none pn libtext-wikicreole-perl none pn libtext-wikiformat-perl none pn libxml-feed-perlnone pn libxml-writer-perl none pn perlmagick none pn po4anone pn polygen none ii python 2.7.9-1 ii python-docutils 0.12+dfsg-1 pn texlive none pn tidynone pn viewvc | gitweb | viewcvs none pn xapian-omeganone -- Configuration Files: /etc/ikiwiki/wikilist changed: www-data /home/splice/wiki/ikiwiki.setup -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#775016: ITP: hovercraft -- impress.js presentations by reStructuredText
I've lost the interest in this package. If somebody else wants to pick up the preparatory works you're welcome (but please mention me in deb/copyright). Please see the (therefore closed) RFS [1] for latest status info of this and the preliminary packages. [1] https://bugs.debian.org/780793 -- http://qa.debian.org/developer.php?login=debian%40danielstender.com 4096R/DF5182C8 46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788119: iceweasel: huge memory usage on linkedin.com profiles
Package: iceweasel
Version: 38.0.1-2~bpo80+1
Severity: important
Dear Maintainer,
* What led up to the situation?
when browsing linkedin.com
* What exactly did you do (or not do) that was effective (or
ineffective)?
go to linkedin.com and click on a user profile
* What was the outcome of this action?
iceweasel stops responding and start using *all* ram and swap available
tested in safe mode and the problem is still here
my computer is *very* slow when using swap
-- Package-specific info:
-- Extensions information
Name: Adblock Edge
Location: ${PROFILE_EXTENSIONS}/{fe272bd1-5f76-4ea4-8501-a05d35d823fc}.xpi
Status: enabled
Name: AdDetector
Location: ${PROFILE_EXTENSIONS}/19b15b40-23f9-11e4-8c21-0800200c9...@jetpack.xpi
Status: enabled
Name: Ageless
Location: ${PROFILE_EXTENSIONS}/2341n...@gmail.com.xpi
Status: enabled
Name: Aptana Debugger
Location: ${PROFILE_EXTENSIONS}/debug...@aptana.com
Status: enabled
Name: Cache Status
Location: ${PROFILE_EXTENSIONS}/ca...@status.org
Status: enabled
Name: CacheViewer2
Location: ${PROFILE_EXTENSIONS}/cachevi...@scriptkitz.ml
Status: enabled
Name: Carbon Light theme
Status: user-disabled
Name: Clean Links
Location: ${PROFILE_EXTENSIONS}/{158d7cb3-7039-4a75-8e0b-3bd0a464edd2}.xpi
Status: enabled
Name: Debian buttons
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{8fb11c5b-84eb-4da0-9128-292eacce2dcb}
Package: xul-ext-debianbuttons
Status: enabled
Name: DownThemAll!
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{DDC359D1-844A-42a7-9AA1-88A850A938A8}
Package: xul-ext-downthemall
Status: enabled
Name: DuckDuckGo Plus
Location: ${PROFILE_EXTENSIONS}/jid1-zadieub7xoz...@jetpack.xpi
Status: enabled
Name: Extended Statusbar
Location: ${PROFILE_EXTENSIONS}/{daf44bf7-a45e-4450-979c-91cf07434c3d}.xpi
Status: enabled
Name: File Hosting Download Manager Disabler greasemonkey-user-script
Status: enabled
Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: enabled
Name: FireTray
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{9533f794-00b4-4354-aa15-c2bbda6989f8}
Package: xul-ext-firetray
Status: user-disabled
Name: Flagfox
Location: ${PROFILE_EXTENSIONS}/{1018e4d6-728f-4b20-ad56-37578a4de76b}.xpi
Status: enabled
Name: Flash and Video Download
Location: ${PROFILE_EXTENSIONS}/{bee6eb20-01e0-ebd1-da83-080329fb9a3a}
Status: enabled
Name: Form History Control
Location: ${PROFILE_EXTENSIONS}/formhist...@yahoo.com
Status: enabled
Name: Gestione sessioni
Location: ${PROFILE_EXTENSIONS}/{1280606b-2510-4fe0-97ef-9b5a22eafe30}.xpi
Status: enabled
Name: Github Comment Enhancer greasemonkey-user-script
Status: enabled
Name: Github User Info greasemonkey-user-script
Status: enabled
Name: Greasemonkey
Location: ${PROFILE_EXTENSIONS}/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}.xpi
Status: enabled
Name: hideTwitterPromoted greasemonkey-user-script
Status: enabled
Name: HTML5 Video Everywhere!
Location: ${PROFILE_EXTENSIONS}/html5-video-everywh...@lejenome.me.xpi
Status: enabled
Name: HTTPS Finder
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{6bdc61ae-7b80-44a3-9476-e1d121ec2238}
Package: xul-ext-https-finder
Status: enabled
Name: HTTPS-Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywh...@eff.org
Status: enabled
Name: I don't care about cookies
Location: ${PROFILE_EXTENSIONS}/jid1-kkzogwgsw3a...@jetpack.xpi
Status: enabled
Name: Italiano (IT) Language Pack locale
Location:
/usr/lib/iceweasel/browser/extensions/langpack...@iceweasel.mozilla.org.xpi
Package: iceweasel-l10n-it
Status: enabled
Name: La7.tv direct link greasemonkey-user-script
Status: enabled
Name: LinkedIn service
Status: enabled
Name: Loading Bar
Location: ${PROFILE_EXTENSIONS}/loading...@xertoz.se.xpi
Status: enabled
Name: MAFIAAFire: ThePirateBay Dancing!
Location: ${PROFILE_EXTENSIONS}/thepirate...@mafiaafire.com.xpi
Status: enabled
Name: No Flash
Location: ${PROFILE_EXTENSIONS}/jid1-cplltty501t...@jetpack.xpi
Status: enabled
Name: Novell Moonlight
Location: ${PROFILE_EXTENSIONS}/moonli...@novell.com
Status: enabled
Name: Open Livestreamer
Location: ${PROFILE_EXTENSIONS}/jid1-y6bhymm8goz...@jetpack.xpi
Status: enabled
Name: Original Content greasemonkey-user-script
Status: enabled
Name: Pastel Gradient theme
Status: user-disabled
Name: Perspectives
Location:
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/perspecti...@cmu.edu
Package: xul-ext-perspectives
Status: enabled
Name: Privacy Badger Firefox
Location: ${PROFILE_EXTENSIONS}/jid1-mnnxcxisbpn...@jetpack.xpi
Status: enabled
Name: Rai.tv native video player and direct links greasemonkey-user-script
Status: enabled
Name: Resurrect Pages
Location: ${PROFILE_EXTENSIONS}/{0c8fbd76-bdeb-4c52-9b24-d587ce7b9dc3}.xpi
Status: enabled
Name: RightToClick
Location: ${PROFILE_EXTENSIONS}/{cd617375-6743-4ee8-bac4-fbf10f35729e}.xpi
Bug#788129: autofs: unowned files after purge (policy 6.8, 10.8): /etc/autofs.conf
Package: autofs Version: 5.1.1-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 1m0.0s ERROR: FAIL: Package purging left files on system: /etc/autofs.conf not owned cheers, Andreas autofs_5.1.1-1.log.gz Description: application/gzip
Bug#788140: cipux-storage: FTBFS with perl 5.22 due to perl-modules dep
Source: cipux-storage Version: 3.4.0.2-6 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788142: libcal-dav-perl: FTBFS with perl 5.22 due to perl-modules dep
Source: libcal-dav-perl Version: 0.6-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788145: libnetsds-perl: FTBFS with perl 5.22 due to perl-modules dep
Source: libnetsds-perl Version: 1.301-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788144: libnetsds-kannel-perl: FTBFS with perl 5.22 due to perl-modules dep
Source: libnetsds-kannel-perl Version: 1.300-5 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788143: libical-parser-sax-perl: FTBFS with perl 5.22 due to perl-modules dep
Source: libical-parser-sax-perl Version: 1.09-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787689: [armhf] Internal compiler error while building qtbase (qt5)
* Matthias Klose d...@debian.org [2015-06-08 03:20]: could you attach the preprocessed source together with the options to trigger this ICE? and maybe ask the ARM porters for help. I'm looking into it. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788152: sympa: FTBFS with perl 5.22 due to perl-modules dep
Source: sympa Version: 6.1.23~dfsg-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10) | libcgi-pm-perl (= 3.35) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libcgi-pm-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libcgi-pm-perl (unversioned, given the age of 3.35) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788156: debian-installer: Debian-Installer does not detect disks HP G9
Package: debian-installer Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, Installing Debian 8.1 via PXE on an HP DL360 Gen9 server. HP updated the firmware of the Smart Array P440ar Controller to Version 2.14 on March 31st, 2015. Debian-Installer is able to detect the disks with Version 1.18 of the Smart Array Firmware, but the update of the Smart Array Firmware to 2.14 causes Debian-Installer to fail to detect the disks and prevents installing Debian. -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788135: cipux-object: FTBFS with perl 5.22 due to perl-modules dep
Source: cipux-object Version: 3.4.0.5-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition 3.4.0.3-4.1 contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788136: cipux-passwd: FTBFS with perl 5.22 due to perl-modules dep
Source: cipux-passwd Version: 3.4.0.3-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656451: apparmor-profiles: unowned files after purge (policy 6.8, 10.8)
Followup-For: Bug #656451 Looks like the unowned files have returned: 0m47.7s ERROR: FAIL: Package purging left files on system: /etc/apparmor.d/local/bin.ping not owned /etc/apparmor.d/local/sbin.klogd not owned /etc/apparmor.d/local/sbin.syslog-ng not owned /etc/apparmor.d/local/sbin.syslogd not owned /etc/apparmor.d/local/usr.bin.chromium-browser not owned /etc/apparmor.d/local/usr.lib.dovecot.anvilnot owned /etc/apparmor.d/local/usr.lib.dovecot.auth not owned /etc/apparmor.d/local/usr.lib.dovecot.config not owned /etc/apparmor.d/local/usr.lib.dovecot.deliver not owned /etc/apparmor.d/local/usr.lib.dovecot.dict not owned /etc/apparmor.d/local/usr.lib.dovecot.dovecot-auth not owned /etc/apparmor.d/local/usr.lib.dovecot.dovecot-lda not owned /etc/apparmor.d/local/usr.lib.dovecot.imap not owned /etc/apparmor.d/local/usr.lib.dovecot.imap-login not owned /etc/apparmor.d/local/usr.lib.dovecot.lmtp not owned /etc/apparmor.d/local/usr.lib.dovecot.log not owned /etc/apparmor.d/local/usr.lib.dovecot.managesieve not owned /etc/apparmor.d/local/usr.lib.dovecot.managesieve-loginnot owned /etc/apparmor.d/local/usr.lib.dovecot.pop3 not owned /etc/apparmor.d/local/usr.lib.dovecot.pop3-login not owned /etc/apparmor.d/local/usr.lib.dovecot.ssl-params not owned /etc/apparmor.d/local/usr.sbin.avahi-daemonnot owned /etc/apparmor.d/local/usr.sbin.dnsmasq not owned /etc/apparmor.d/local/usr.sbin.dovecot not owned /etc/apparmor.d/local/usr.sbin.identd not owned /etc/apparmor.d/local/usr.sbin.mdnsd not owned /etc/apparmor.d/local/usr.sbin.nmbdnot owned /etc/apparmor.d/local/usr.sbin.nscdnot owned /etc/apparmor.d/local/usr.sbin.smbdnot owned /etc/apparmor.d/local/usr.sbin.smbldap-useradd not owned /etc/apparmor.d/local/usr.sbin.traceroute not owned Andreas apparmor-profiles_2.9.2-3.log.gz Description: application/gzip
Bug#788124: By default, produces a configuration incompatible with Apache 2.4
Package: puppet-module-puppetlabs-apache Version: 1.1.1-1 Unless apache_version is set to 2.4 in the apache class, the module produces a configuration for apache 2.2, which is not packaged in Jessie. Furthermore, the configuration produced is not compatible with Apache 2.4: it tries to load modules that do not exist anymore, among others. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788138: cipux-rpc: FTBFS with perl 5.22 due to perl-modules dep
Source: cipux-rpc Version: 3.4.0.9-3 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788139: cipux-rpc-client: FTBFS with perl 5.22 due to perl-modules dep
Source: cipux-rpc-client Version: 3.4.0.7-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788141: cipux-task: FTBFS with perl 5.22 due to perl-modules dep
Source: cipux-task Version: 3.4.0.7-4 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788146: libperl6-export-attrs-perl: FTBFS with perl 5.22 due to perl-modules dep
Source: libperl6-export-attrs-perl Version: 0.0.3-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788157: bind9utils: dnssec-keygen creates keys with wrong permissions for debian
Package: bind9utils Version: 1:9.9.5.dfsg-9 Severity: important Dear Maintainer, dnssec-keygen creates *.private files with mode 0600, but /etc/bind belongs to root and is only setguid bind. This means that by default bind9 (running as bind) cannot read them. Manual intervention is required to chmod the resulting files to 0640. Andrew Gallagher. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.0.4-x86-linode75 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bind9utils depends on: ii libbind9-901:9.9.5.dfsg-9 ii libc6 2.19-18 ii libcap21:2.24-8 ii libcomerr2 1.42.12-1.1 ii libdns100 1:9.9.5.dfsg-9 ii libgssapi-krb5-2 1.12.1+dfsg-19 ii libisc95 1:9.9.5.dfsg-9 ii libisccc90 1:9.9.5.dfsg-9 ii libisccfg901:9.9.5.dfsg-9 ii libk5crypto3 1.12.1+dfsg-19 ii libkrb5-3 1.12.1+dfsg-19 ii libpython2.7-stdlib [python-argparse] 2.7.9-2 ii libssl1.0.01.0.1k-3 ii libxml22.9.1+dfsg1-5 ii python 2.7.9-1 bind9utils recommends no packages. bind9utils suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788156: debian-installer: Debian-Installer does not detect disks HP G9
control: -1 moreinfo On Mon, Jun 08, 2015 at 03:23:00PM -0700, Sean Mottles wrote: } an HP DL360 Gen9 server, Smart Array P440ar Controller,Version 2.14 Please provide more information. Such as: * PCI ID * name of kernel module, a special the name of the kernel module with the working version Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788011: mutt fails to connect to imaps after update
On Mon, Jun 08, 2015 at 07:48:54PM +0200, Andreas Metzler wrote: On 2015-06-08 Michal Hocko msts...@gmail.com wrote: [...] Are there any commands I can run to give you sufficient information? mutt with -d 5 doesn't tell more than the error message I've already provided. As a first step you could check whether gnutls-cli can still connect and if not post a full log (gnutls-cli -d 4711 -p imaps host) Thanks, this helps to get mutt out of the picture. The imap server is using a self-signed certificate which I didn't have in my trusted database, so I've added it now. This made gnutls-cli with 3.3.15-2 version of the library happy and the above command connected to the server. This is not the case for the updated version (3.3.15-5) of the library, though. It complains about Bad record MAC like mutt (see the full log attached - I just have scrubbed INT: hash message because I wasn't really sure what they mean and didn't feel comfortable to reveal them without understanding) and fails to connect. Please make sure your system is up-to-date sid, *partial* upgrades are currently broken due to the nettle transition. I am running testing with some packages from unstable/experimental. Which packages should I be careful about? -- Michal Hocko |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1869 |3| ASSERT: common.c:1869 |3| ASSERT: common.c:1869 |3| ASSERT: common.c:1869 |3| ASSERT: common.c:1869 |3| ASSERT: common.c:1869 |3| ASSERT: common.c:1869 |3| ASSERT: common.c:1869 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1869 |3| ASSERT: common.c:1869 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: common.c:1052 |3| ASSERT: dn.c:994 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:994 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:994 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:994 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:994 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:994 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:994 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |3| ASSERT: dn.c:990 |5| REC[0xb78c10]: Allocating epoch #0 |3| ASSERT: gnutls_constate.c:586 |5| REC[0xb78c10]: Allocating epoch #1 |4|
Bug#788123: linux-image-3.16.0-4-686-pae: lvcreate --snap does not work with dm_snapshot: Unknown symbol
Package: src:linux Version: 3.16.7-ckt11-1 Severity: normal Dear Maintainer, after upgrading from Wheezy to Jessie my backup fails as LVM snapshots are not longer possible. root@server:~# root@server:~# lvcreate --size 500m --snapshot --name snap_var /dev/vg00/lvVar modprobe: ERROR: could not insert 'dm_snapshot': Unknown symbol in module, or unknown parameter (see dmesg) /sbin/modprobe failed: 1 Can't process LV snap_var: snapshot target support missing from kernel? Failed to suspend origin lvVar root@server:~# dmesg shows: [95913.884784] dm_snapshot: Unknown symbol dm_hold (err 0) [95913.885030] dm_snapshot: Unknown symbol dm_internal_suspend (err 0) [95913.885481] dm_snapshot: Unknown symbol dm_internal_resume (err 0) root@server:~# uname -a Linux server 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) i686 GNU/Linux root@server:~# On an amd64 Box LVM snapshop still works. root@server:~# modinfo dm-snapshot filename: /lib/modules/3.16.0-4-686-pae/kernel/drivers/md/dm-snapshot.ko alias: dm-snapshot-merge alias: dm-snapshot-origin license:GPL author: Joe Thornber description:device-mapper snapshot target depends:dm-bufio,dm-mod intree: Y vermagic: 3.16.0-4-686-pae SMP mod_unload modversions 686 parm: snapshot_copy_throttle:A percentage of time allocated for copy on write (uint) root@server:~# apt-file search /lib/modules/3.16.0-4-686-pae/kernel/drivers/md/dm-snapshot.ko linux-image-3.16.0-4-686-pae: /lib/modules/3.16.0-4-686-pae/kernel/drivers/md/dm-snapshot.ko linux-image-3.16.0-4-686-pae-dbg: /usr/lib/debug/lib/modules/3.16.0-4-686-pae/kernel/drivers/md/dm-snapshot.ko root@server:~# modprobe dm-mod is OK and does not change anything Kind regards Chris -- Package-specific info: ** Version: Linux version 3.16.0-4-686-pae (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-686-pae root=/dev/mapper/vg00-lvRoot ro quiet ** Not tainted ** Kernel log: [ 2072.373200] Btrfs loaded [ 2072.390178] fuse init (API version 7.23) [ 2121.850672] exim4[24595]: segfault at e965012f ip b6a8b614 sp bfcb32a0 error 7 in libgnutls-deb0.so.28.41.0[b69d7000+13a000] [ 2122.587981] exim4[24600]: segfault at 9f8673d3 ip b6af0614 sp bff37560 error 6 in libgnutls-deb0.so.28.41.0[b6a3c000+13a000] [ 2589.477474] exim4[24643]: segfault at 55d9ed6c ip b6a63614 sp bfc90f20 error 6 in libgnutls-deb0.so.28.41.0[b69af000+13a000] [ 2590.190405] exim4[24648]: segfault at fd20789d ip b6ade614 sp bfe8e080 error 7 in libgnutls-deb0.so.28.41.0[b6a2a000+13a000] [ 2878.819837] exim4[25408]: segfault at 31f7b5ae ip b6a6f614 sp bf98c540 error 6 in libgnutls-deb0.so.28.41.0[b69bb000+13a000] [ 2879.566363] exim4[25413]: segfault at ecc748cb ip b6ac4614 sp bfab9780 error 7 in libgnutls-deb0.so.28.41.0[b6a1+13a000] [ 4121.214227] exim4[26551]: segfault at c3882f1e ip b6a8c614 sp bffba8e0 error 7 in libgnutls-deb0.so.28.41.0[b69d8000+13a000] [ 4121.973905] exim4[26556]: segfault at 4152468c ip b6aa1614 sp bff940f0 error 6 in libgnutls-deb0.so.28.41.0[b69ed000+13a000] [ 7717.485533] exim4[27717]: segfault at 1ff9b944 ip b6a0a614 sp bf80e080 error 6 in libgnutls-deb0.so.28.41.0[b6956000+13a000] [ 7718.209919] exim4[27722]: segfault at 7760fe71 ip b6abd614 sp bf7cad80 error 6 in libgnutls-deb0.so.28.41.0[b6a09000+13a000] [11317.515794] exim4[28890]: segfault at 29a7e0af ip b6ad2614 sp bfae7ed0 error 6 in libgnutls-deb0.so.28.41.0[b6a1e000+13a000] [11318.306754] exim4[28895]: segfault at 6ebef9d8 ip b6a16614 sp bfa693c0 error 6 in libgnutls-deb0.so.28.41.0[b6962000+13a000] [14917.429909] exim4[30067]: segfault at 33348c56 ip b6a5b614 sp bfc7de30 error 6 in libgnutls-deb0.so.28.41.0[b69a7000+13a000] [14918.182586] exim4[30072]: segfault at a5eb7103 ip b6a20614 sp bfec4770 error 6 in libgnutls-deb0.so.28.41.0[b696c000+13a000] [18518.430052] exim4[31284]: segfault at 1f207396 ip b6aad614 sp bfc3b700 error 6 in libgnutls-deb0.so.28.41.0[b69f9000+13a000] [18519.187772] exim4[31289]: segfault at 5f478af3 ip b6acf614 sp bf974ef0 error 6 in libgnutls-deb0.so.28.41.0[b6a1b000+13a000] [18694.499719] dm_snapshot: Unknown symbol dm_hold (err 0) [18694.499963] dm_snapshot: Unknown symbol dm_internal_suspend (err 0) [18694.501588] dm_snapshot: Unknown symbol dm_internal_resume (err 0) [18695.047603] FAT-fs (dm-11): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [18695.050224] FAT-fs (dm-11): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [18695.062189] ufs was compiled with read-only support, can't be mounted as read-write [18695.066772] FAT-fs (dm-11): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [18695.067218] FAT-fs (dm-11): utf8 is not a recommended IO charset
Bug#788125: Missing directory referenced in SSL configuration
Package: puppet-module-puppetlabs-apache
Version: 1.1.1-1
In my manifest, I have:
class { '::apache’:
apache_version = 2.4,
...
}
class { 'apache::mod::ssl': }
In /etc/apache2/mods-enabled/ssl.conf, one can find:
Mutex file:${APACHE_RUN_DIR}/ssl_mutex
When I start apache, I get the following error:
Jun 8 22:33:06 vulturnus apache2[17654]: Starting web server: apache2 failed!
Jun 8 22:33:06 vulturnus apache2[17654]: The apache2 configtest failed. ...
(warning).
Jun 8 22:33:06 vulturnus apache2[17654]: Output of config test was:
Jun 8 22:33:06 vulturnus apache2[17654]: AH00526: Syntax error on line 13 of
/etc/apache2/mods-enabled/ssl.conf:
Jun 8 22:33:06 vulturnus apache2[17654]: Invalid Mutex directory in argument
file:/var/run/apache2/ssl_mutex
Jun 8 22:33:06 vulturnus apache2[17654]: Action 'configtest' failed.
Jun 8 22:33:06 vulturnus apache2[17654]: The Apache error log may have more
information.
Jun 8 22:33:06 vulturnus systemd[1]: apache2.service: control process exited,
code=exited status=1
Jun 8 22:33:06 vulturnus systemd[1]: Failed to start LSB: Apache2 web server.
Jun 8 22:33:06 vulturnus systemd[1]: Unit apache2.service entered failed state.
The problem is that the directory /var/run/apache2/ssl_mutex does not exist and
is not created by the startup script or Apache. Creating it fixes the problem
temporarily, but as /run is a tmpfs, at the next reboot the directory will be
gone and the problem will be there again.
In more recent version of puppetlabs/apache, they set the Mutex parameter to
‘default’. Backporting the following change would fix the issue:
https://github.com/puppetlabs/puppetlabs-apache/commit/2093c1e763ffa0760bbe92cb7ba912979062daae
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788127:
Actually, SSLv2 is not even supported by Apache 2.4. So that line is just useless. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788130: murano-agent: unowned files after purge (policy 6.8, 10.8): /etc/murano-agent/muranoagent.conf
Package: murano-agent Version: 2015.1.0-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8 (or 10.8): https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails Filing this as important as having a piuparts clean archive is a release goal since lenny. If the package would ship the directories as empty directories, dpkg would care for their creation and removal. From the attached log (scroll to the bottom...): 1m30.9s ERROR: FAIL: Package purging left files on system: /etc/murano-agent/ not owned /etc/murano-agent/muranoagent.conf not owned /var/lib/murano-agent/ not owned /var/lib/murano-agent/cache/ not owned /var/log/murano-agent/ not owned cheers, Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788131: cipux: FTBFS with perl 5.22 due to perl-modules dep
Source: cipux Version: 3.4.0.13-4 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition cipux contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this makes cipux FTBFS with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788133: cipux-cat-web: FTBFS with perl 5.22 due to perl-modules dep
Source: cipux-cat-web Version: 3.4.0.3-4.1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition 3.4.0.3-4.1 contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788134: cipux-dog: FTBFS with perl 5.22 due to perl-modules dep
Source: cipux-dog Version: 3.4.0.0-6 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition 3.4.0.3-4.1 contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788137: cipux-rbac-simple: FTBFS with perl 5.22 due to perl-modules dep
Source: cipux-rbac-simple Version: 3.4.0.0-4 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788155: perl-modules: ExtUtils::MakeMaker installs perl modules in the wrong directory
Package: perl-modules Version: 5.20.2-3+deb8u1 Severity: important While there were no problems with Debian up to Debian 7, ExtUtils::MakeMaker now installs perl modules in the wrong directory. For instance, I build Math-MPFR-3.24 with: unset PERL_LOCAL_LIB_ROOT PERL_MB_OPT PERL_MM_OPT mkdir $HOME/testdir perl Makefile.PL PREFIX=$HOME/testdir make Then: $ make install [...] Appending installation info to /home/vlefevre/testdir/lib/x86_64-linux-gnu/perl/5.20.2/perllocal.pod Files found in blib/arch: installing files in blib/lib into architecture dependent library tree Installing /home/vlefevre/testdir/lib/x86_64-linux-gnu/perl/5.20.2/auto/Math/MPFR/MPFR.so Installing /home/vlefevre/testdir/lib/x86_64-linux-gnu/perl/5.20.2/auto/Math/MPFR/Prec/Prec.so Installing /home/vlefevre/testdir/lib/x86_64-linux-gnu/perl/5.20.2/auto/Math/MPFR/Random/Random.so Installing /home/vlefevre/testdir/lib/x86_64-linux-gnu/perl/5.20.2/auto/Math/MPFR/V/V.so Installing /home/vlefevre/testdir/lib/x86_64-linux-gnu/perl/5.20.2/Math/MPFR.pm Installing /home/vlefevre/testdir/lib/x86_64-linux-gnu/perl/5.20.2/Math/MPFR/Prec.pm Installing /home/vlefevre/testdir/lib/x86_64-linux-gnu/perl/5.20.2/Math/MPFR/Random.pm Installing /home/vlefevre/testdir/lib/x86_64-linux-gnu/perl/5.20.2/Math/MPFR/V.pm Installing /home/vlefevre/testdir/man/man3/Math::MPFR.3pm This is wrong because perl won't search the modules in $PREFIX/lib/x86_64-linux-gnu/perl/5.20.2. $ PERL5LIB=$HOME/testdir/lib/perl perl -MMath::MPFR -e '' Can't locate Math/MPFR.pm in @INC (you may need to install the Math::MPFR module) (@INC contains: /home/vlefevre/testdir/lib/perl /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .). BEGIN failed--compilation aborted. The perlrun(1) man page says: PERL5LIBA list of directories in which to look for Perl library files before looking in the standard library and the current directory. Any architecture-specific and version-specific directories, such as version/archname/, version/, or archname/ under the specified locations are automatically included if they exist, with this lookup done at interpreter startup time. [...] To follow the PERL5LIB convention, the files should not have been installed in $PREFIX/lib/x86_64-linux-gnu/perl/5.20.2 but in $PREFIX/lib/perl/5.20.2/x86_64-linux-gnu-thread-multi for which I do not get an error. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages perl-modules depends on: ii dpkg 1.17.25 ii perl-base 5.20.2-3+deb8u1 Versions of packages perl-modules recommends: ii libarchive-extract-perl0.72-1 ii libcgi-pm-perl 4.09-1 ii libmodule-build-perl 0.421000-2 ii libmodule-pluggable-perl 5.1-1 ii libpackage-constants-perl 0.04-1 ii libpod-latex-perl 0.61-1 ii libterm-ui-perl0.42-1 ii libtext-soundex-perl 3.4-1+b2 ii perl 5.20.2-3+deb8u1 Versions of packages perl-modules suggests: pn libb-lint-perl none pn libcpanplus-dist-build-perl none pn libcpanplus-perl none pn libfile-checktree-perl none ii liblog-message-perl 0.8-1 ii liblog-message-simple-perl 0.10-2 pn libobject-accessor-perl none -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788158: python-yaql: leaves alternatives after purge: /usr/bin/yaql
Package: python-yaql Version: 0.2.6-2 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removedetails The leftover files are actually alternatives that were installed by the package but have not been properly removed. While there is ongoing discussion how to remove alternatives correctly (see https://bugs.debian.org/71621 for details) the following strategy should work for regular cases: * 'postinst configure' always installs the alternative * 'prerm remove' removes the alternative * 'postrm remove' and 'postrm disappear' remove the alternative In all other cases a maintainer script is invoked (e.g. upgrade, deconfigure) the alternatives are not modified to preserve user configuration. Removing the alternative in 'prerm remove' avoids having a dangling link once the actual file gets removed, but 'prerm remove' is not called in all cases (e.g. unpacked but not configured packages or disappearing packages) so the postrm must remove the alternative again (update-alternatives gracefully handles removal of non-existing alternatives). Note that the arguments for adding and removing alternatives differ, for removal it's 'update-alternatives --remove name path'. Filing this as important as having a piuparts clean archive is a release goal since lenny. From the attached log (scroll to the bottom...): 1m9.2s INFO: Warning: Package purging left files on system: /etc/alternatives/yaql - /usr/bin/python2-yaqlnot owned /usr/bin/yaql - /etc/alternatives/yaqlnot owned This was observed after an upgrade test: stretch - sid. cheers, Andreas python-yaql_0.2.6-2.log.gz Description: application/gzip
Bug#788162: fish-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: fish-dbg
Version: 2.1.2+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
stretch - sid
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
From the attached log (usually somewhere in the middle...):
0m53.9s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/fish-dbg/NEWS.Debian.gz (fish-dbg) !=
/usr/share/doc/fish-common/NEWS.Debian.gz (fish-common)
/usr/share/doc/fish-dbg - fish-common
/usr/share/doc/fish-dbg/changelog.Debian.gz (fish-dbg) !=
/usr/share/doc/fish-common/changelog.Debian.gz (fish-common)
/usr/share/doc/fish-dbg - fish-common
/usr/share/doc/fish-dbg/copyright (fish-dbg) !=
/usr/share/doc/fish-common/copyright (fish-common)
/usr/share/doc/fish-dbg - fish-common
cheers,
Andreas
fish-dbg_2.1.2+dfsg1-1.log.gz
Description: application/gzip
Bug#788127: SSLv3 is not disabled
Package: puppet-module-puppetlabs-apache
Version: 1.1.1-1
In my manifest, I have:
class { '::apache’:
apache_version = 2.4,
...
}
class { 'apache::mod::ssl': }
In /etc/apache2/mods-enabled/ssl.conf, one can find:
SSLProtocol all -SSLv2
So SSLv3 is still enabled, as opposed to the default configuration of the
apache2 package, where one can find:
SSLProtocol all -SSLv3
Since there is a general consensus that SSLv3 is weak, it should be disabled by
default, as it is in most Debian packages. The parameter should be changed in
templates/mod/ssl.conf.erb.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788128: libfile-scan-perl: most probably outdated, should be removed?
Package: libfile-scan-perl Version: 1.43-2 Severity: serious X-Debbugs-Cc: mimedef...@packages.debian.org This module was last updated upstream in 2005. For a module that deals with virus scanning, that seems like a very long time. Is there any reason to keep this package around, or should we rather have it removed? The only reverse dependency is mimedefang, which Suggests and Build-Depends on libfile-scan-perl. I'm cc'ing the maintainer. Christoph, do you think we should keep libfile-scan-perl? -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788132: python3-pep8 ships a different version of pep8.py in comparison with pep8 package
Package: python3-pep8 Version: 1.5.7-2 Severity: normal Dear Maintainer, I was investigating a pep8 related problem in Ubuntu[0], after some triaging I found that python3-pep8 package comes with a very different version of pep8.py than the one provided in pep8 package. I rebuilt the package and this problem is reproducible, but checking debian/rules I couldn't find what could be producing this strange behaviour. Here is the output of my terminal: root@debian-sid:~# dpkg -l python3-pep8 pep8 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii pep81.5.7-2 all Python PEP 8 code style checker - python2 ii python3-pep81.5.7-2 all Python PEP 8 code style checker - python3 root@debian-sid:~# python -c import pep8; print(pep8.__version__) 1.5.7 root@debian-sid:~# python -c import pep8; print(pep8.__file__) /usr/lib/python2.7/dist-packages/pep8.pyc root@debian-sid:~# python3 -c import pep8; print(pep8.__version__) 1.4.6 root@debian-sid:~# python3 -c import pep8; print(pep8.__file__) /usr/lib/python3/dist-packages/pep8.py root@debian-sid:~# diff -u /usr/lib/python2.7/dist-packages/pep8.py /usr/lib/python3/dist-packages/pep8.py | diffstat pep8.py | 698 1 file changed, 316 insertions(+), 382 deletions(-) Best, [0] https://bugs.launchpad.net/ubuntu/+source/python-hacking/+bug/1429521 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-999-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-pep8 depends on: ii python3-setuptools 17.0-1 pn python3:any none python3-pep8 recommends no packages. python3-pep8 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#656451: [pkg-apparmor] Bug#656451: apparmor-profiles: unowned files after purge (policy 6.8, 10.8)
Hi, On 09.06.2015 00:13, Andreas Beckmann wrote: Followup-For: Bug #656451 Looks like the unowned files have returned: 0m47.7s ERROR: FAIL: Package purging left files on system: /etc/apparmor.d/local/bin.ping not owned /etc/apparmor.d/local/sbin.klogd not owned /etc/apparmor.d/local/sbin.syslog-ng not owned [...] debian/rules calls /usr/bin/dh_apparmor if it exists. Since it doesn't build-depend on itself this is not the case in a minimal build environment. It should be possible to call the dh_apparmor from the source tree by setting DH_AUTOSCRIPTDIR to debian/debhelper/. More generally is there a good reason why dh_apparmor creates the /etc/apparmor.d/local/profile files in postinst instead of installing them as regular conffiles? That way we'd get the file removal handling for free. Cheers, Felix -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788163: libdatrie-dev: copyright file missing after upgrade (policy 12.5)
Package: libdatrie-dev
Version: 0.2.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.
This was observed on the following upgrade paths:
jessie - sid
From the attached log (scroll to the bottom...):
0m50.9s DUMP:
MISSING COPYRIGHT FILE: /usr/share/doc/libdatrie-dev/copyright
# ls -lad /usr/share/doc/libdatrie-dev
drwxr-xr-x 2 root root 40 May 4 01:04 /usr/share/doc/libdatrie-dev
# ls -la /usr/share/doc/libdatrie-dev/
total 0
drwxr-xr-x 2 root root 40 May 4 01:04 .
drwxr-xr-x 100 root root 2140 May 4 01:04 ..
Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
cheers,
Andreas
libdatrie-dev_0.2.9-1.log.gz
Description: application/gzip
Bug#788122: libfile-scan-perl: make the build reproducible
Package: libfile-scan-perl
Version: 1.43-2
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness timestamp
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
This package can't currently be built reproducibly
because the code generated by Makefile.PL embeds
a timestamp and uses unsorted hash keys.
Two patches attached. The test suite is very minimal,
so eyeballs would be welcome.
--
Niko Tyni nt...@debian.org
From 7a16ea0eef83cfee6db7cdeee2ca0afdec6effe7 Mon Sep 17 00:00:00 2001
From: Niko Tyni nt...@debian.org
Date: Mon, 8 Jun 2015 22:55:27 +0300
Subject: [PATCH 1/2] Don't put a timestamp in generated Scan.pm
This is done to make the build reproducible.
---
Makefile.PL | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Makefile.PL b/Makefile.PL
index dadcfd6..a8cc8b5 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -152,9 +152,8 @@ sub make_module {
sub get_code {
my $patterns = shift;
- my $today = string_date();
my $code = ENDOFCODE1;
-# generated in: $today
+# generated data follows
sub get_app_sign {
\$_ = pop;
--
2.1.4
From eab4aff7f62428d05f8b4243dfd4e6f0ceaab3b8 Mon Sep 17 00:00:00 2001
From: Niko Tyni nt...@debian.org
Date: Mon, 8 Jun 2015 22:55:36 +0300
Subject: [PATCH 2/2] Make the Scan.pm generation reproducible by sorting hash
keys
---
Makefile.PL | 24 ++--
1 file changed, 14 insertions(+), 10 deletions(-)
diff --git a/Makefile.PL b/Makefile.PL
index a8cc8b5..8a3db0d 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -159,7 +159,7 @@ sub get_app_sign {
\$_ = pop;
ENDOFCODE1
my $c = 0;
- for my $key (keys(%{$app_signatures})) {
+ for my $key (sort keys(%{$app_signatures})) {
$c++;
$conversion{$key} = $c;
my $n = length($key)/2;
@@ -223,10 +223,11 @@ ENDOFCODE3
$code .= \t\t\t\t/ . $script_lang-{'in'}-{$sl} . /os and \$script = \$sl\, last TEST;\n;
}
$code .= \t\t\t}\n\t\t}\n\t\tif(\$script) {\n;
- for my $sl (keys(%{$script_lang-{'in'}})) {
+ for my $sl (sort keys(%{$script_lang-{'in'}})) {
if(scalar(keys(%{$patterns-{$sl}-{'0'}}))) {
$code .= \t\t\tif(\$script eq \$sl\) {\n;
- while(my($key, $value) = each(%{$patterns-{$sl}-{'0'}})) {
+ for my $key (sort keys %{$patterns-{$sl}-{'0'}}) {
+my $value = $patterns-{$sl}-{'0'}{$key};
$code .= \t\t\t\t/$value/s and \$virus = \$key\, last LINE;\n;
}
$code .= \t\t\t}\n;
@@ -237,16 +238,18 @@ ENDOFCODE3
/\\/script[^]*/s and \$script = ;
} else {
ENDOFCODE4
- for my $sl (keys(%{$script_lang-{'out'}})) {
- while(my($key, $value) = each(%{$patterns-{$sl}-{'0'}})) {
+ for my $sl (sort keys(%{$script_lang-{'out'}})) {
+ for my $key (sort keys %{$patterns-{$sl}-{'0'}}) {
+ my $value = $patterns-{$sl}-{'0'}{$key};
$code .= \t\t\t/$value/s and \$virus = \$key\, last LINE;\n;
}
}
$code .= \t\t}\n;
if(scalar(keys(%{$script_lang-{'mix'}}))) {
$code .= \t\tunless(\$script eq \HTMLJS\) {\n;
- for my $sl (keys(%{$script_lang-{'mix'}})) {
- while(my($key, $value) = each(%{$patterns-{$sl}-{'0'}})) {
+ for my $sl (sort keys(%{$script_lang-{'mix'}})) {
+ for my $key (sort keys %{$patterns-{$sl}-{'0'}}) {
+my $value = $patterns-{$sl}-{'0'}{$key};
$code .= \t\t\t/$value/s and \$virus = \$key\, last LINE;\n;
}
}
@@ -300,7 +303,7 @@ ENDOFCODE6
}
ENDOFCODE7
my $lcode = ;
- for my $key (keys(%{$app_signatures})) {
+ for my $key (sort keys(%{$app_signatures})) {
my $c = $conversion{$key};
$lcode .= ($lcode) ? \t\t} els : \t\t;
$lcode .= if(\$type == $c) {\n;
@@ -337,13 +340,14 @@ sub subgene {
my $tab = shift;
my $code = ;
- for my $limit (keys(%{$pat})) {
+ for my $limit (sort keys(%{$pat})) {
my $tabs = $tab;
if($limit) {
$code .= $tabs . if($limit) \{\n;
$tabs .= \t;
}
- while(my($key, $value) = each(%{$pat-{$limit}})) {
+ for my $key (sort keys %{$pat-{$limit}}) {
+ my $value = $pat-{$limit}{$key};
$code .= $tabs . /$value/s and \$virus = \$key\, last LINE;\n;
}
$code .= $tab\}\n if($limit);
--
2.1.4
Bug#788161: python-llfuse-dbg, python3-llfuse-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-llfuse-dbg,python3-llfuse-dbg
Version: 0.40+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
jessie - sid
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
From the attached log (usually somewhere in the middle...):
2m36.8s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/python-llfuse-dbg/changelog.Debian.gz (python-llfuse-dbg) !=
/usr/share/doc/python-llfuse/changelog.Debian.gz (python-llfuse)
/usr/share/doc/python-llfuse-dbg - python-llfuse
/usr/share/doc/python-llfuse-dbg/changelog.gz (python-llfuse-dbg) !=
/usr/share/doc/python-llfuse/changelog.gz (python-llfuse)
/usr/share/doc/python-llfuse-dbg - python-llfuse
/usr/share/doc/python-llfuse-dbg/copyright (python-llfuse-dbg) !=
/usr/share/doc/python-llfuse/copyright (python-llfuse)
/usr/share/doc/python-llfuse-dbg - python-llfuse
2m26.9s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/python3-llfuse-dbg/changelog.Debian.gz (python3-llfuse-dbg) !=
/usr/share/doc/python3-llfuse/changelog.Debian.gz (python3-llfuse)
/usr/share/doc/python3-llfuse-dbg - python3-llfuse
/usr/share/doc/python3-llfuse-dbg/changelog.gz (python3-llfuse-dbg) !=
/usr/share/doc/python3-llfuse/changelog.gz (python3-llfuse)
/usr/share/doc/python3-llfuse-dbg - python3-llfuse
/usr/share/doc/python3-llfuse-dbg/copyright (python3-llfuse-dbg) !=
/usr/share/doc/python3-llfuse/copyright (python3-llfuse)
/usr/share/doc/python3-llfuse-dbg - python3-llfuse
cheers,
Andreas
python-llfuse-dbg_0.40+dfsg-1.log.gz
Description: application/gzip
Bug#775238: ITP: svg.path -- Python library providing SVG path
I've lost interest in this package being a preliminary for Hovercraft [1]. If somebody wants to take up the preparatory work [2] that's all right with me (but if you would please mention me in deb/copyright). [1] https://bugs.debian.org/775016 RFP: hovercraft -- impress.js presentations by reStructuredText [2] svn://anonscm.debian.org/python-modules/packages/svg.path/trunk/ -- http://www.danielstender.com/entwicklerblog GnuPG key: 4096R/DF5182C8 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680272: REMINDER: 's contact info
Title: Join Brewster 680...@bugs.debian.org Mobile Number Confirm/Update for Brian Minton For your safety, this link expires in 48 hours Featured on: Your Contacts, Synced Anywhere Why did you receive this email? 11 East 4th St. #2F New York, NY 10003 Unsubscribe -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#788149: libtest-xpath-perl: FTBFS with perl 5.22 due to perl-modules dep
Source: libtest-xpath-perl Version: 0.16-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788148: libtemplate-plugin-class-perl: FTBFS with perl 5.22 due to perl-modules dep
Source: libtemplate-plugin-class-perl Version: 0.13-3 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10) | libmodule-build-perl however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) This build-dependency should probably be replaced with libmodule-build-perl since libmodule-build-perl is in any case being removed from the perl core. This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#783381: upgrade from wheezy to jessie on a PowerMac G4 Silver/Confirmation
On Mon, 2015-06-08 at 22:56 +0200, Alois Zoitl wrote: Hi, thanks. Looks like there is no Gnome for non Intel platforms. With XFCE and lightdm I got graphics partly working. Still rad and blue is exchanged. [...] GNOME Shell requires either 3D accelerated graphics or 'llvmpipe' which currently only works on x86. For PowerMacs with an ATI Radeon GPU, the firmware-nonfree package is needed. Ben. -- Ben Hutchings 73.46% of all statistics are made up. signature.asc Description: This is a digitally signed message part
Bug#783381: upgrade from wheezy to jessie on a PowerMac G4 Silver/Confirmation
Hi, thanks. Looks like there is no Gnome for non Intel platforms. With XFCE and lightdm I got graphics partly working. Still rad and blue is exchanged. But I don't want to hijack this bug for the graphics problems ;-) Regards, Alois On Sat, Jun 6, 2015 at 1:57 PM, Manfred Stock manfred.stock+deb...@gmail.com wrote: Package: upgrade-reports, linux-image-3.16.0-4-powerpc Followup-For: Bug #783381 Hi, And now to the graphics problems :-( on my system, I could improve the situation by replacing GDM3 with Lightdm, and Gnome3 with the Awesome or Fluxbox window manager (since they actually started and displayed something, which was not the case with GDM or Gnome, they just displayed an error along the lines of something went wrong, with a logout button). However, I then got some kind of crash/lockup when I executed eg. dmesg in an xterm (mouse pointer still visible/movable, but otherwise, nothing changed, and restarting X iirc just got me a black screen with mouse pointer). I could improve that by adding append=radeon.agpmode=-1 to the yaboot config of the kernel I'm booting, which disables AGP mode, but so far seems to result in a stable system (I have the feeling that it feels slower on certain UI updates though, but I'm not sure about his). So far, I've found some bug reports [1,2,3] which might be related to these issues, but haven't tried anything further. Still don't have working suspend to disk/ram though, but that could actually be related to the graphics issues and/or my workaround. Kind regards Manfred [1] https://bugs.debian.org/762047 [2] https://bugs.debian.org/782066 [3] https://bugs.debian.org/683796 -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: powerpc (ppc) Kernel: Linux 3.16.0-4-powerpc Locale: LANG=de_CH.utf8, LC_CTYPE=de_CH.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) -- To unsubscribe, send mail to 783381-unsubscr...@bugs.debian.org.
Bug#788126: libboost1.55-dev: Contains files with missing or questionable licenses
Package: libboost1.55-dev Version: 1.55.0+dfsg-3 Severity: serious Justification: Policy 2.3 Dear Maintainer, Several files in this package do not seem to be covered by any license described in the copyright file. Most serious: interprocess/sync/xsi/advanced_xsi_semaphore.hpp : No license mentioned at all python/detail/python22_fixed.h : Explicitly All rights reserved Probably fine but questionable and IMHO should be documented at least as they will fail in automated checks: algorithm/cxx14/mismatch.hpp : Refers to non-existing LICENSE10.txt, probably typo And some non-standard license headers in: rational.hpp math/common_factor_rt.hpp test/utils/runtime/cla/detail/argument_value_usage.hpp shared_container_iterator.hpp program_options/detail/utf8_codecvt_facet.hpp Aside: The latter files contain in some cases boostinspect:nolicense, indicating that someone at some point tried to avoid this license mess, however that activity seems to have died... Given the popularity of the library and the regularity of license slip-ups a more long-term solution than manual review/fixing would be nice to have. And apologies if Severity: serious was the incorrect choice. Thanks, Reimar Döffinger -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (700, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, armhf, armel, ppc64el Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages libboost1.55-dev depends on: ii libstdc++-4.9-dev [libstdc++-dev] 4.9.2-18 ii libstdc++-5-dev [libstdc++-dev]5.1.1-9 libboost1.55-dev recommends no packages. Versions of packages libboost1.55-dev suggests: pn libboost-atomic1.55-dev none pn libboost-chrono1.55-dev none pn libboost-context1.55-dev none pn libboost-coroutine1.55-devnone pn libboost-date-time1.55-devnone pn libboost-exception1.55-devnone pn libboost-filesystem1.55-dev none pn libboost-graph-parallel1.55-dev none pn libboost-graph1.55-devnone pn libboost-iostreams1.55-devnone pn libboost-locale1.55-dev none pn libboost-log1.55-dev none pn libboost-math1.55-dev none pn libboost-mpi-python1.55-dev none pn libboost-mpi1.55-dev none pn libboost-program-options1.55-dev none pn libboost-python1.55-dev none pn libboost-random1.55-dev none pn libboost-regex1.55-devnone pn libboost-serialization1.55-devnone pn libboost-signals1.55-dev none pn libboost-system1.55-dev none pn libboost-test1.55-dev none pn libboost-thread1.55-dev none pn libboost-timer1.55-devnone pn libboost-wave1.55-dev none pn libboost1.55-doc none pn libboost1.55-tools-devnone pn libmpfrc++-devnone pn libntl-devnone -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788147: libtap-parser-sourcehandler-pgtap-perl: FTBFS with perl 5.22 due to perl-modules dep
Source: libtap-parser-sourcehandler-pgtap-perl Version: 3.29-1 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.14) | libtest-harness-perl (= 3.23) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) This build-dependency should probably be replaced with perl (= 5.14) | libtest-harness-perl (= 3.23) (or just 'perl', unless you care about being able to backport to oldstable). This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788151: module-build-cipux: FTBFS with perl 5.22 due to perl-modules dep
Source: module-build-cipux Version: 0.4.0-7 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788150: libticket-simple-perl: FTBFS with perl 5.22 due to perl-modules dep
Source: libticket-simple-perl Version: 0.0.2-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned build-depends: perl-modules (= 5.10.0) | libmodule-build-perl (= 0.2808) and perl-modules (= 5.8.0-7~) | libtest-simple-perl however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) libmodule-build-perl is being removed from perl/perl-modules in any case, so the correct fix is to just build-depend on libmodule-build-perl (unversioned, given the age of 0.2808) - and to drop the libtest-simple-perl related dep. This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788153: mrtg: uninstallable with perl 5.22 due to perl-modules dep
Source: mrtg Version: 2.17.4-2 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned depends: perl-modules (= 5.6.0) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) Given that you already depend on perl, you can just drop this clause altogether. This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788154: slack: uninstallable with perl 5.22 due to perl-modules dep
Source: slack Version: 0.15.2-6 Severity: important User: debian-p...@lists.debian.org Usertags: perl-5.22-transition This package contains a versioned depends: perl-modules (= 5.6.1-7) however the package description states that perl-modules should be considered an internal implementation detail of perl and shoudn't be depended upon. With the perl 5.22 work in experimental, perl-modules is gone, and this causes the FTBFS issue with sbuild. (It's still provided, but this doesn't work with versioned depends.) Given that you already depend on perl, you can just drop this clause altogether (and probably the version of the perl dependency, given the age). This bug will become RC nearer the time of the perl 5.22 transition to unstable. Cheers, Dominic. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788159: bind9 tries to write temporary DNSSEC files to /etc/bind instead of /var/cache/bind
Package: bind9 Version: 1:9.9.5.dfsg-9 Severity: important Dear Maintainer, I have enabled inline signing in bind9, but even though I have set directory /var/cache/bind it tries to write temporary files into /etc/bind (which fails because the debian file ownerships are sensible and don't allow that sort of thing). Jun 8 23:44:39 xen named[7604]: zone andrewg.com/IN (signed): reconfiguring zone keys Jun 8 23:44:39 xen named[7604]: zone web/IN (signed): reconfiguring zone keys Jun 8 23:44:39 xen named[7604]: /etc/bind/db.andrewg.signed.jnl: create: permission denied Jun 8 23:44:39 xen named[7604]: zone andrewg.com/IN (signed): zone_rekey:dns_journal_open - unexpected error I have to break policy and set /etc/bind to group-writable to get this to work. Andrew Gallagher. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.0.4-x86-linode75 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bind9 depends on: ii adduser3.113+nmu3 ii bind9utils 1:9.9.5.dfsg-9 ii debconf [debconf-2.0] 1.5.56 ii init-system-helpers1.22 ii libbind9-901:9.9.5.dfsg-9 ii libc6 2.19-18 ii libcap21:2.24-8 ii libcomerr2 1.42.12-1.1 ii libdns100 1:9.9.5.dfsg-9 ii libgssapi-krb5-2 1.12.1+dfsg-19 ii libisc95 1:9.9.5.dfsg-9 ii libisccc90 1:9.9.5.dfsg-9 ii libisccfg901:9.9.5.dfsg-9 ii libk5crypto3 1.12.1+dfsg-19 ii libkrb5-3 1.12.1+dfsg-19 ii liblwres90 1:9.9.5.dfsg-9 ii libssl1.0.01.0.1k-3 ii libxml22.9.1+dfsg1-5 ii lsb-base 4.1+Debian13+nmu1 ii net-tools 1.60-26+b1 ii netbase5.3 bind9 recommends no packages. Versions of packages bind9 suggests: pn bind9-doc none ii dnsutils1:9.9.5.dfsg-9 pn resolvconf none pn ufw none -- Configuration Files: /etc/bind/named.conf.local changed: // // Add local zone definitions here. include /etc/bind/zones.andrewg; /etc/bind/named.conf.options 0367900f381d5c83cf34009440f3d211 [Errno 2] No such file or directory: u'/etc/bind/named.conf.options 0367900f381d5c83cf34009440f3d211' -- debconf information: bind9/run-resolvconf: true bind9/different-configuration-file: bind9/start-as-user: bind -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788160: elinks: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: elinks
Version: 0.12~pre6-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.
This was observed on the following upgrade paths:
For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
For other overwritten locations anything interesting may happen.
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
From the attached log (usually somewhere in the middle...):
0m32.0s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/elinks/changelog.Debian.gz (elinks) !=
/usr/share/doc/elinks-data/changelog.Debian.gz (elinks-data)
/usr/share/doc/elinks - elinks-data
/usr/share/doc/elinks/changelog.gz (elinks) !=
/usr/share/doc/elinks-data/changelog.gz (elinks-data)
/usr/share/doc/elinks - elinks-data
/usr/share/doc/elinks/copyright (elinks) !=
/usr/share/doc/elinks-data/copyright (elinks-data)
/usr/share/doc/elinks - elinks-data
/usr/share/doc/elinks/examples (elinks) !=
/usr/share/doc/elinks-data/examples (elinks-data)
/usr/share/doc/elinks - elinks-data
/usr/share/doc/elinks/examples/elinks.config (elinks) !=
/usr/share/doc/elinks-data/examples/elinks.config (?)
/usr/share/doc/elinks - elinks-data
cheers,
Andreas
elinks_0.12~pre6-7.log.gz
Description: application/gzip
Bug#788023: tilda: Uses obsolete vte3 which is going away
Package: tilda Followup-For: Bug #788023 Upstream bug : https://github.com/lanoxx/tilda/issues/94 Regards, Rodolphe -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788014: [pkg-ntp-maintainers] Bug#788014: does not start at bootup
On Mon, Jun 08, 2015 at 09:14:09AM +0200, Evgeni Golov wrote: Hi Kurt, On Sun, Jun 07, 2015 at 11:25:44PM +0200, Kurt Roeckx wrote: Jun 07 21:18:53 genshi.die-welt.net ntpd[650]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING This last line is clearly a problem. There are at least 2 processes that try to bind() to udp port 123. Did you try a ps to see if there is still one running? Sorry, forgot to mention this in the initial report. I ran ps after bootup and there was no ntp procs running. Note that the first and second line have a different PID. You however seem to have at least a third PID mentioned there. Can you try installing lockfile-progs and see if the problem goes away? Yes, that helped. ps aoutput looks like this after boot: root@genshi:~# ps aux |grep ntp root 568 0.0 0.1 20072 2440 ?S09:10 0:00 /bin/sh /etc/network/if-up.d/ntpdate root 570 0.0 0.0 6268 628 ?S09:10 0:00 lockfile-create /var/lock/ntpdate root 622 0.0 0.1 22452 3724 ?Ss 09:10 0:00 /bin/sh /etc/init.d/ntp start root 663 0.0 0.0 6268 632 ?S09:10 0:00 lockfile-create /var/lock/ntpdate Could it be ntpdate which is fucking up the start of ntpd here before? Yes, and ntpdate recommends lockfile-progs ... Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785672: Critical ext4 data corruption bug
It seems that 4.0.0-2 won't build on amd64: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787004 As 3.16.7-ckt11-1 never hit Sid it seems we currently have no Sid kernel without the ext4 corruption bug? Also, does anyone have a link to any documentation explaining the Debian linux-image naming scheme as I'm losing track: 4.0.0-1 = 4.0.2 kernel 4.0.0-2 = 4.0.4 kernel 3.16.0-4 = 3.16.7-ckt* kernel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788108: qtlocation-opensource-src: Please switch to geoclue 2
Source: qtlocation-opensource-src Version: 5.3.2-2 Severity: important Hi, I would like to remove geoclue from the archive and qtlocation is the only remaning non leaf package to use it. The package should switch to geoclue 2 instead, not sure how far upstream is regarding this. Cheers, Laurent Bigonville -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788107: tightvnc: add support for ppc64el arch
Source: tightvnc Version: 1.3.9 Severity: important Tags: patch This patch adds support for the ppc64el architecture on tightVNC. The patch basically defines the endianess and bit width for this new architecture. I tested the patch on version 1.3.10 as 1.3.9 and it works fine. The upstream bug and patch submission could be seen at: https://sourceforge.net/p/vnc-tight/bugs/1353/ -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16.0-4-powerpc64le (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) From 25adb1614419b72a986c229cb01870c1b3e38c0b Mon Sep 17 00:00:00 2001 From: Lauri Kasanen c...@gmx.com Date: Fri, 5 Jun 2015 07:45:09 -0300 Subject: [PATCH 2/2] Add ppc64el support Signed-off-by: Lauri Kasanen c...@gmx.com --- Xvnc/config/cf/Imake.cf | 4 Xvnc/config/cf/linux.cf | 8 +++- Xvnc/include/Xmd.h | 2 +- Xvnc/programs/Xserver/include/servermd.h | 23 +++ 4 files changed, 35 insertions(+), 2 deletions(-) Index: tightvnc-1.3.9/Xvnc/config/cf/Imake.cf === --- tightvnc-1.3.9.orig/Xvnc/config/cf/Imake.cf +++ tightvnc-1.3.9/Xvnc/config/cf/Imake.cf @@ -724,6 +724,10 @@ XCOMM Keep cpp from replacing path eleme # define Mc68020Architecture # undef mc68000 # endif /* mc68000 */ +# ifdef __powerpc64__ +# define Ppc64Architecture +# undef __powerpc64__ +# endif # ifdef powerpc # define PpcArchitecture # undef powerpc Index: tightvnc-1.3.9/Xvnc/config/cf/linux.cf === --- tightvnc-1.3.9.orig/Xvnc/config/cf/linux.cf +++ tightvnc-1.3.9/Xvnc/config/cf/linux.cf @@ -297,7 +297,13 @@ XCOMM binutils: (LinuxBinUtilsMajorVersi #define ServerExtraDefines -DGCCUSESGAS XFree86ServerDefines #endif /* s390xArchitecture */ -#ifdef PowerPCArchitecture +#ifdef Ppc64Architecture +#define DefaultCCOptions-fsigned-char +#define OptimizedCDebugFlags -O2 +#define LinuxMachineDefines -D__powerpc64__ +#define ServerOSDefines XFree86ServerOSDefines -DDDXTIME -DPART_NET +#define ServerExtraDefines -DGCCUSESGAS XFree86ServerDefines -D_XSERVER64 +#elif defined(PowerPCArchitecture) #define DefaultCCOptions-fsigned-char #define OptimizedCDebugFlags -O2 #define LinuxMachineDefines -D__powerpc__ Index: tightvnc-1.3.9/Xvnc/include/Xmd.h === --- tightvnc-1.3.9.orig/Xvnc/include/Xmd.h +++ tightvnc-1.3.9/Xvnc/include/Xmd.h @@ -59,7 +59,7 @@ SOFTWARE. #ifdef CRAY #define WORD64/* 64-bit architecture */ #endif -#if defined(__alpha) || defined(__alpha__) || defined(__x86_64__) +#if defined(__alpha) || defined(__alpha__) || defined(__x86_64__) || defined(__powerpc64__) #define LONG64/* 32/64-bit architecture */ #endif #ifdef __sgi Index: tightvnc-1.3.9/Xvnc/programs/Xserver/include/servermd.h === --- tightvnc-1.3.9.orig/Xvnc/programs/Xserver/include/servermd.h +++ tightvnc-1.3.9/Xvnc/programs/Xserver/include/servermd.h @@ -407,8 +407,31 @@ SOFTWARE. #if defined (linux) defined(__powerpc__) +#ifdef __powerpc64__ +# define BITMAP_SCANLINE_UNIT 64 +# define BITMAP_SCANLINE_PAD 64 +# define LOG2_BITMAP_PAD 6 +# define LOG2_BYTES_PER_SCANLINE_PAD 3 + +/* Add for handling protocol XPutImage and XGetImage; see comment in + * Alpha section. + */ +#define INTERNAL_VS_EXTERNAL_PADDING +#define BITMAP_SCANLINE_UNIT_PROTO 32 + +#define BITMAP_SCANLINE_PAD_PROTO 32 +#define LOG2_BITMAP_PAD_PROTO 5 +#define LOG2_BYTES_PER_SCANLINE_PAD_PROTO 2 +#endif /* linux/ppc64 */ + +#if defined(__LITTLE_ENDIAN__) +#define IMAGE_BYTE_ORDER LSBFirst +#define BITMAP_BIT_ORDER LSBFirst +#else #define IMAGE_BYTE_ORDER MSBFirst #define BITMAP_BIT_ORDER MSBFirst +#endif + #define GLYPHPADBYTES 4 #define GETLEFTBITS_ALIGNMENT 1
Bug#788065: libtool-bin: prevents working with staged installs
On Mon, Jun 08, 2015 at 05:56:26PM +0900, Norbert Preining wrote: Package: libtool-bin Version: 2.4.2-1.11 Severity: normal Hi, while trying/evaluation new software, I usually to staged installs, that is: ./configure make make install prefix=/usr/local/pkgs/SOMEPKGS graft -i SOMEPKGS (graft, or stash, or something similar). That would nicely, as at the end the files show up in their proper locations. Unfortunately libtool is just not able to handle this, as far as I see, as I get warnings: libtool: install: error: cannot install `justenoughlibtexpdf.la' to a directory not ending in /usr/local/lib/sile *yes* ... I know that, but afterwards the lib *will* be in this directory. That should not happen, programs should *do* what the users advises them to do, even if they themselves think that this is incorrect. Programs are stupid, and automated checks are prone to fail. Please remove this check, or convert it into a warning. If that check is removed, it will just create a broken file instead. Please see the manual: https://www.gnu.org/software/libtool/manual/html_node/Install-mode.html Kurt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788006: libzabbix-api-perl: should package be removed?
On Mon, 8 Jun 2015 06:28:04 Salvatore Bonaccorso wrote: Hi Dimitry, On Mon, Jun 08, 2015 at 11:36:38AM +1000, Dmitry Smirnov wrote: On Sun, 7 Jun 2015 20:17:43 Salvatore Bonaccorso wrote: Should the libzabbix-api-perl package possibly be dropped from Debian for stretch? (thus filled as serious, with reasoning not fit for release with stretch). Agreed, let's remove. Old 1.8 API is obsolete and for current Zabbix2 a new package is needed, apparently. I did not use libzabbix-api-perl for a while and just realised how much it aged... Thanks for your quick reply! Are you going to fill the removal request? Since I introduced this package to Debian I feel that probably I should have filled removal request... I see that you've already did that (#788118) and I am grateful to you for your help. Thank you. -- All the best, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part.
Bug#788168: python-greenlet-doc: copyright file missing after upgrade (policy 12.5)
Package: python-greenlet-doc
Version: 0.4.7-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.
This was observed on the following upgrade paths:
jessie - sid
From the attached log (scroll to the bottom...):
MISSING COPYRIGHT FILE: /usr/share/doc/python-greenlet-doc/copyright
# ls -lad /usr/share/doc/python-greenlet-doc
drwxr-xr-x 2 root root 40 May 16 22:35 /usr/share/doc/python-greenlet-doc
# ls -la /usr/share/doc/python-greenlet-doc/
total 0
drwxr-xr-x 2 root root 40 May 16 22:35 .
drwxr-xr-x 114 root root 2440 May 16 22:35 ..
Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile
Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase
It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.mainstscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.
cheers,
Andreas
python-greenlet-doc_0.4.7-1.log.gz
Description: application/gzip
Bug#788173: rescue-mode: kfreebsd rescue fails with can't create /dev/md
package: rescue-mode version: 1.51 severity: important x-debbugs-cc: debian-...@lists.debian.org Adding the line set kFreeBSD.rescue/enable=true in a grub entry and booting the kfreebsd installer fails when executing rescue-mode. The error is: mkdir: can't create directory '/dev/md': Operation not supported /dev is mounted rw and also doing mkdir manually fails the same. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788174: kfreebsd-10: installer rescue mode grub entry
package: src:kfreebsd-10 version: 10.1~svn274115-4 severity: wishlist It would be nice if the kfreebsd installer were to include a rescue mode grub boot option. In the meantime manually adding set kFreeBSD.rescue/enable=true according to the kfreebsd FAQ is possible: https://wiki.debian.org/Debian_GNU/kFreeBSD_FAQ#Q._How_to_use_the_rescue_mode_of_the_installer Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774149: Is there a workaround for the Can't mount ntfs drive (Transport endpoint is not connected)
In-line :-
On 6/8/15, Rogério Brito rbr...@ime.usp.br wrote:
Hi.
Hi Rogério,
snipped
I guess that you meant udisks2, right? If that's your situation, I guess
that you can safely remove usbmount and use only udisks2.
In fact, I don't think that usbmount is useful anymore with udisks2 and
other things. Especially if you are using a desktop environment.
I meant udisks2 as well as pmount, although do not know if both
provide the same service or not.
I did remove usbmount and I'm on a desktop environment. Could you
advise if udisks2 is good by itself or do I need to also use pmount. I
am on a desktop in a desktop environment (mate) :) .
My use-case is I want the usb thumb-drives/ external disks to mount
automatically.
Hope this helps,
--
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A 2C2F 9F3D C7A4 E1C4 D2D8
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788156: detect disks HP G9
Control: tag -1 moreinfo stop On Mon, Jun 08, 2015 at 11:03:03PM +, Debian Bug Tracking System wrote: Processing control commands: -1 moreinfo Unknown command or malformed arguments to command. Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788112: src:beets: didn't say pkg installed via pip; additional info
Package: src:beets Followup-For: Bug #788112 Dear Maintainer, -pkg beets has no manpage when installed via python-pip -posted June 08 2015 at https://github.com/sampsyo/beets/issues/1501#issuecomment-110141520 sampsyo commented 2 hours ago Yes, this is sad. But alas, it is not fixable (in the current Python packaging context). Here's a little bit of background: Here's another bug on another project where this is an issue with ordinary Python installs: ansible/ansible#7790 Here's a Stack Overflow question on the topic that peters out with a no good way to do this yet: http://stackoverflow.com/questions/3657209/python-installing-man-pages-in-distutils-based-project The setuptools developer documentation, which is surprisingly unhelpful on this topic: https://pythonhosted.org/setuptools/setuptools.html#developer-s-guide One blog post about a programmer shamefully resorting to an external instal.sh: http://empt1e.blogspot.com/2010/08/installing-man-pages-with-distutils.html A bug report for another project that hacked together a rather dirty solution, got some flak for it, and eventually dropped the behavior: daltonmatos/wsgid#2 So the official position of this project, somewhat mournfully, is that this needs to be handled by the OS-specific package manager, if any. -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#655465: No thumbnails created in Gnome 3.2.1
Package: gnome-xcf-thumbnailer Version: 1.0-1.1 Followup-For: Bug #655465 Dear Maintainer, I confirm that the bug is still open a possible fix working for me is creating /usr/share/thumbnailers/gnome-xcf.thumbnailer with this inside [Thumbnailer Entry] TryExec=gnome-xcf-thumbnailer Exec=gnome-xcf-thumbnailer %i %o MimeType=image/x-xcf;image/x-compressed-xcf; -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-xcf-thumbnailer depends on: ii gconf23.2.6-3 ii libc6 2.19-18 ii libglib2.0-0 2.42.1-1 ii libpng12-01.2.50-2+b2 gnome-xcf-thumbnailer recommends no packages. gnome-xcf-thumbnailer suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788171: libvirt-daemon: segfault in libvirtd on qemu live migration
Package: libvirt-daemon Version: 1.2.9-9 Severity: important Dear Maintainer, I can confirm that the archived bug #773503 is not fixed. libvirtd still segfaults on live migration. Last message in #773503 may give some clue. Thank you! -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (900, 'stable'), (400, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libvirt-daemon depends on: ii libapparmor12.9.0-3 ii libaudit1 1:2.4-1+b1 ii libavahi-client30.6.31-5 ii libavahi-common30.6.31-5 ii libblkid1 2.25.2-6 ii libc6 2.19-18 ii libcap-ng0 0.7.4-2 ii libdbus-1-3 1.8.16-1 ii libdevmapper1.02.1 2:1.02.90-2.2 ii libfuse22.9.3-15+deb8u1 ii libgnutls-deb0-28 3.3.8-6 ii libnetcf1 1:0.2.3-4.1 ii libnl-3-200 3.2.24-2 ii libnl-route-3-200 3.2.24-2 ii libnuma12.0.10-1 ii libparted2 3.2-7 ii libpcap0.8 1.6.2-2 ii libpciaccess0 0.13.2-3+b1 ii librados2 0.80.7-2 ii librbd1 0.80.7-2 ii libsasl2-2 2.1.26.dfsg1-13 ii libselinux1 2.3-2 ii libssh2-1 1.4.3-4.1 ii libsystemd0 215-17+deb8u1 ii libudev1215-17 ii libvirt01.2.9-9 ii libxen-4.4 4.4.1-9 ii libxenstore3.0 4.4.1-9 ii libxml2 2.9.1+dfsg1-5 ii libyajl22.1.0-2 Versions of packages libvirt-daemon recommends: pn libxml2-utils none ii netcat-openbsd 1.105-7 ii qemu-kvm1:2.1+dfsg-12 Versions of packages libvirt-daemon suggests: ii libvirt-daemon-system 1.2.9-9 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#784854: RFS: gtk3-engines-unico/1.0.3+14.04.20140109+repack1-1 [ITA] [RC]
Hi Vincent, I've removed bzr from the build dependencies. After fiddling with the get-orig-source a bit, I realized that I can't get the same checksum either when running it multiple times. According to a 'diff' of 'tar -tvf' output, the only difference between these generated tarballs was the source files' timestamps. This is probably because bzr is used to fetch the sources every time get-orig-source is ran, and it saves the current time (of checkout) as the timestamp of the files, instead of the code's modification date. For this, there appears to be a wishlist bug filed: https://bugs.launchpad.net/bzr/+bug/245170 Best, James On 07/06/15 11:17 PM, Vincent Cheng wrote: Hi James, (Sorry for the late reply!) On Tue, May 19, 2015 at 11:28 AM, James Lu glol...@hotmail.com wrote: Hello Vincent, Okay, I've uploaded a newer version of the package that should fix the problems you mentioned. Earlier, I was trying to manually sync up both Karolina's and upstream's debian/ folders (they had different content, like build-dep versions, etc.), and I must have missed the watch file. I also added a get-orig-source to debian/rules, which pulls the revision from Launchpad bzr, removes the INSTALL symlink, and then repacks. debian/clean is removed and the changelog is also more verbose now. You don't need to declare a build-dep on bzr because it's only used by d/rules get-orig-source, not during the build itself (to be precise, Policy §7.7 specifies the specific d/rules targets in which the dependencies listed in various d/control fields must be satisfied to invoke them; get-orig-source is not one of these targets), so please remove bzr from your build-deps. The orig tarball you've uploaded to mentors seems to differ from a tarball that I've generated locally using your get-orig-source target (i.e. hashsums don't match). Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776026: (no subject)
The only part of the patch I don't like is the hard-coding of the timestamp. I don't have a better idea, but before I apply this I'm going to see if upstream has any suggestions. I'll include in that bug report the other two fixes which look good. pgpypITBp1bsR.pgp Description: OpenPGP digital signature
Bug#659321: ooo-thumbnailer: No thumbnail generated in Gnome 3 Nautilus
Package: ooo-thumbnailer Version: 0.2-5 Followup-For: Bug #659321 Dear Maintainer, I can confirm the bug is still open and the solution proposed is working for me -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (700, 'stable'), (500, 'stable-updates'), (500, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ooo-thumbnailer depends on: ii gconf2 3.2.6-3 ii imagemagick 8:6.8.9.9-5 ii unzip6.0-16 ooo-thumbnailer recommends no packages. ooo-thumbnailer suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#788176: diodon: possible not to depend on zeitgeist?
It should perhaps further be noted that zeitgeist seems no longer be developer or maybe even dead upstream,... the last entries on their mailing lists are from 2013, and upstream states in several locations that there's no further active development. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#439888: memtailor
Dependency update: memtailor has been accepted into Debian unstable. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
