Bug#764630: RFS: javatools 0.48 [RC]
On Sun, Dec 14, 2014 at 6:50 PM, Markus Koschany a...@gambaru.de wrote: [...] Actually what was the reasoning behind the choice to use a custom shell script like jarwrapper instead of jexec to register executable jars with binfmt-misc? This question also came up in the bug report. Here is my guess: `jexec` only works with openjdk installed. At one point debian had multiple java implementation (sun, kaffe...). These days only two really remains, so maybe an easier solution would be to have a `gcj-exec` provided by `gcj-jdk` to mimic openjdk package. Which means it would be much easier to handle the LD_LIBRARY_PATH issue within the `gcj-exec` executable. jarwrapper is only really needed with a custom jre installation... 2cts -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#727800: kmail: KMail goes bonkers following Qt update
On Sunday 14 December 2014 21:35:45 Diane Trout wrote: The migration bug is the one kmail bug I've been able to reproduce repeteadly. I have a work-around patch that basically does akonadictl restart when the migrator says Migration Done Oh, I haven't followed that advice. I'll try again, hopefully this week. I haven't figured out how to reproduce the other kmail bugs. And yes, one of KDE's design choices is that everything is integrated, so not shipping kmail2 would be very difficult if not impossible. You might also want to check out the current versions of evolution or thunderbird. Both are also quite decent mail clients. This is becoming increasingly off-topic, I'll respond on the mailing list. Thanks, Shai. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771778: Acknowledgement (squid3: Pinger segfault with libc)
Hai Luigi, Thank you for having a loot. Your close. I didnt change any dependecies to other librarys. What i did, get every package squid3 depended on and recompiled these also back to wheezy. the total bundle of packages needed by squid3 was used. ( so about the same as a backported package ) I didnt change anything in any file. just by : apt-get build-dep squid3 apt-get build-dep libecap2 apt-get source squid3 -b apt-get source libecap2 -b But thank you for providing the backported packages, i did a rebuild just because there wasnt any squid3 backported packages. I'll go test this out. I'll report back. Greetz, Louis -Oorspronkelijk bericht- Van: Luigi Gangitano [mailto:lu...@debian.org] Verzonden: vrijdag 12 december 2014 18:46 Aan: L.P.H. van Belle; 771...@bugs.debian.org CC: cont...@bugs.debian.org; pkg-squid-de...@lists.alioth.debian.org Onderwerp: Re: Bug#771778: Acknowledgement (squid3: Pinger segfault with libc) notfound 771778 3.4.8-2 severity 771778 normal tags 771778 +unreproducible +wontfix thanks This is on debian wheezy, squid recompiled from jesse with icap and i did rebuild to a deb : squidclamav 6.11 bug 760303, which looks like it. Hi, If I read correctly, you took the jessie sources and recompiled it on wheezy, changing dependencies to another library. Then you filed a Release-Criticl bug on the jessie version because your custom built package does not work. I’ve just downgraded your bug and tagged it as unreproducible (we don’t have a copy of your package to test) and wontfix (we don’t provide supporto to packages not provided by Debian build infrastructure). Since this segfault may still affect the backport version od 3.4.8-4 that I just uploaded, I’m keeping this bug report open. Please install that package from back ports (it uses libecap, just like the jessie version) and test if the bug is still there. Best regards, L -- Luigi Gangitano -- lu...@debian.org -- gangit...@lugroma3.org GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 GPG: 4096R/2BA97CED: 8D48 5A35 FF1E 6EB7 90E5 0F6D 0284 F20C 2BA9 7CED -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751658: [suricata] affected version by CVE-2013-5919
Hi, Victor Julien (upstream developer), reports that this CVE affects 1.X series, and 2.0.X series is not affected. So, jessie an sid are good. -- Arturo Borrero González -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691902: Unable to shutdown Debian Wheezy via normal means
Hi Joachim, yes I did but it didn't help. Although I have to say I also have a usb mouse and keyboard connected to the USB port. I'm unable to unplug it because the pc is in a datacenter. On 15/12/2014 6:45, Joachim Fahrner wrote: Hi Maarten, did you try uninstalling acpi-support-base? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771778: Info received (Bug#771778: Acknowledgement (squid3: Pinger segfault with libc))
Hai Luigi, Sorry to ask, but are you in the position to create an amd64 packages. im only having amd64 machines.. ( sorry ) Greetz, Louis -Oorspronkelijk bericht- Van: ow...@bugs.debian.org [mailto:ow...@bugs.debian.org] Verzonden: maandag 15 december 2014 9:21 Aan: L.P.H. van Belle Onderwerp: Bug#771778: Info received (Bug#771778: Acknowledgement (squid3: Pinger segfault with libc)) Thank you for the additional information you have supplied regarding this Bug report. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Luigi Gangitano lu...@debian.org If you wish to submit further information on this problem, please send it to 771...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- 771778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772700: vt2-6 still not available with base system
On 12/12/14 16:55, Michael Biebl wrote: Am 12.12.2014 um 17:18 schrieb Simon McVittie: Any reason not to prefer Wants=getty@tty2.service ... getty@tty6.service and ExecStart=/bin/true? The issue apparently is, that Conditions are evaluated way too late and have no influence on the dependency graph. Fair enough. With the suggested static-getty.service, you'd always get the traditional behaviour of having 6 gettys (with the only difference that with dbus installed, they are started on demand). It's unclear to me why you don't want to make use of that feature, if available. Can you elaborate? IMO it simplifies testing if we're using the same code path regardless of whether dbus is installed. Not a strong objection if you strongly prefer the on-demand setup. I'm still a bit wary about having dbus turn up in minimal chroots, but perhaps bumping it up to Priority: important wouldn't be so bad - that would put it in a normal or fakechroot debootstrap, but not minbase or buildd. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772040: syncevolution-http: syncevo-http-server script uses SSLv3, no TLS support
On Sun, Dec 14, 2014 at 23:01:49 +, Adam D. Barratt wrote:
On Thu, 2014-12-04 at 17:05 +0100, Tino Mettler wrote:
syncevo-http-server only supports SSLv3 and no TLS connections when using
HTTPS. This is
1. a potential security risk, as shown by the poodle attack
2. a problem with the SyncML client of syncevolution in sid and jessie, as
SSLv3 connections won't work anymore ('Error performing TLS handshake:
GnuTLS internal error.') when using HTTPS. So the Syncevolution SyncML
client can't connect to the SyncML server provided by the same version of
syncevolution.
The fix is rather small. A patch against upstream (no debdiff) is attached.
- sslmethod = SSL.SSLv3_METHOD):
+ sslmethod = SSL.TLSv1_METHOD):
Is there a reason not to use SSLv23_METHOD here? Note that TLSv1_METHOD
only enables support for TLS 1.0 - it will _not_ support TLS 1.1 or 1.2.
If what you're looking for is any version of TLS, then you want to be
using SSLv23_METHOD and setting the OP_NO_SSLv2 and OP_NO_SSLv3 flags.
Hi,
thanks for all the hints. I tried to find documentation regarding this
when I crafted the patch, but failed. This is the reason for just using
TLSv1_METHOD.
With your new keywords I found proper documentation. I'll look into it,
but I think the current state is valid and way better than before.
Regards,
Tino
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created
Thomas Goirand tho...@goirand.fr writes: I have found out what happened. Indeed, this issue is that we're not calling dh_systemd_enable. Or rather, openstack-pkg-tools is generating the *.service files in the override_dh_installinit target, which happens after the dh_systemd_enable in the standard dh sequence. So I wrote this: # Generate the systemd unit file # Note: because dh_systemd_enable is called by the # dh sequencer *before* dh_installinit, we have # to process it manually. for i in `ls debian/*.init.in` ; do \ pkgos-gen-systemd-unit $$i ; \ MYSERVICE=`echo $$i | sed 's/debian\///'` ; \ MYSERVICE=`echo $$MYSERVICE | sed 's/.init.in/.service/'` ; \ dh_systemd_enable $$MYSERVICE ; \ done in the override_dh_installinit. I don't see a reason why this should not work, but I wonder why you don't just add an override_dh_systemd_enable target wich first uses pkgos to generate the service files and then just calls dh_systemd_enable. This seems like the more obvious solution to me. Having this in a separate target would probably also make it possible to build packages without systemd by just not build depending on dh-systemd. This works, then, except for keystone where there's no #DEBHELPER# in the postinst (because I wanted to keep the control of when invoke-rc.d is called, ie after the daemon starts, the admin tenant is created, and the keystone endpoint is registered). This means that for Keystone, we need to manually add what dh_systemd_enable does. Then I've been asking myself what would happen in Wheezy, and it's looking like the only thing that will happen is that it's going to add a dependency on init-system-helpers, which IMO is quite fine, because it's already available from the official wheezy-backports. I don't understand the problem you are trying to solve here. Why are you not just adding the #DEBHELPER# at the end of the postinst where you want it to be? I don't see how the debhelper inserted snippets don't give you control over where they are called. But maybe I'm missing something. Gaudenz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773165: pciutils: new 3.3.0 upstream release
Package: pciutils Version: 3.2.1-3 Severity: wishlist Hi Anibal! pciutils 3.3.0 was released on 2014-11-10. Here's the changelog entry: 2014-11-10 Martin Mares m...@ucw.cz * Released as 3.3.0. (celebrating a one-year anniversary of the previous version :)) * Device names exported by BIOS are displayed on Linux. * On Linux systems, HWDB is used to look up device names when our ID database gives no match. (More precisely, HWDB is consulted after local pci.ids, but before using network to query online pci.ids.) Thanks to Tom Gundersen for the initial patch. * Added experimental back-end for OS X / Darwin. Thanks to Richard Yao for providing it. * Filters now support matching by device class. Original patch by Matthew Wilcox, wrappers for ABI compatibility by me. * Interrupt Pin and Interrupt Line registers are displayed for bridge devices, too. * Several portability bugs have been fixed. * Several typos have been fixed. Also, use of questionable constructs in man pages has been reduced. * PCIe link capabilities now include the ASPMOptComp bit. * The CRS Software Visibility bit is now decoded properly. * Updated pci.ids to the current snapshot of the database. -- Matt Taggart tagg...@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#773152: unblock: rpm/4.11.3-1.1
Control: tags -1 - moreinfo Hi, On Mon, Dec 15, 2014 at 06:16:10AM +, Adam D. Barratt wrote: For the record, this is in DELAYED/5. Please remove the moreinfo tag once the package reaches unstable. I've uploaded it directly to unstable with the maintainer's permission, so I'm removing the moreinfo tag now. -- Matt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772114: zotero-standalone: zotero does not start anymore
Thanks, I installed the latest xulrunner and now it works Kind Regards, On 12/13/2014 03:16 PM, Michele Cane wrote: Thank Mike. Could the submitter check which version(s) of xulrunner is(are) installed on the system. and eventually remove all but the latest. Cheers Mike On Tue Dec 09 2014 at 23:35:02 Mike Hommey m...@glandium.org mailto:m...@glandium.org wrote: On Fri, Dec 05, 2014 at 09:53:09AM +, Michele Cane wrote: Hi, If I am correct this is an issue with iceweasel. For some reason iceweasel version results as 10.0.12 instead of 31.3. I do not have access to a stable machine right now. I'll try to test it later tonight but I think I'll assign this bug to the iceweasel package. Where would that 10.0.12 version come from? I don't see it coming from iceweasel, there must be something fishy with how zotero starts up, and my guess is that the bug reporter has xulrunner 10.0.0.12 on their machine. Mike
Bug#773166: unblock fdroidserver/0.2.1-4
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
unblock fdroidserver/0.2.1-4
Fix RC bug to keep this package in testing, its related to all these:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769912
It turned out to be non-trivial to change fdroidserver to also be able to use
the system provided Android SDK utils (i.e. /usr/bin/aapt vs.
~/Documents/android-sdk/build-tools/21.1.2/aapt) so the debdiff isn't super
short. But these are literally only changes needed for this functionality to
work. It is still important that fdroidserver be able to use a user-installed
Android SDK because lots of the SDK is not yet in Debian. The 0.2.1-4 update
means that a user can maintain an app repo using only packages in Debian, but
in order to build Android apps, they still need to install the Android SDK.
$ debdiff fdroidserver_0.2.1-3.dsc fdroidserver_0.2.1-4.dsc
diff -Nru fdroidserver-0.2.1/debian/changelog
fdroidserver-0.2.1/debian/changelog
--- fdroidserver-0.2.1/debian/changelog 2014-10-10 04:43:45.0 +0200
+++ fdroidserver-0.2.1/debian/changelog 2014-12-14 22:23:11.0 +0100
@@ -1,3 +1,11 @@
+fdroidserver (0.2.1-4) unstable; urgency=medium
+
+ * Recommend android-tools-adb, aapt, zipalign to provide essential utilities
+ * include upstream commits that allow use of system-provided SDK utilities
+(Closes: #769912)
+
+ -- Hans-Christoph Steiner h...@eds.org Sun, 14 Dec 2014 20:22:07 +0100
+
fdroidserver (0.2.1-3) unstable; urgency=low
* fix local sync perms
diff -Nru fdroidserver-0.2.1/debian/control fdroidserver-0.2.1/debian/control
--- fdroidserver-0.2.1/debian/control 2014-10-10 04:12:19.0 +0200
+++ fdroidserver-0.2.1/debian/control 2014-12-14 22:06:17.0 +0100
@@ -18,11 +18,14 @@
Architecture: all
Depends: ${python:Depends},
${misc:Depends}
-Recommends: openjdk-7-jre-headless,
+Recommends: android-tools-adb,
+aapt,
+openjdk-7-jre-headless,
openjdk-7-jdk,
opensc,
rsync,
-wget
+wget,
+zipalign
Suggests: bzr,
git,
gradle,
diff -Nru
fdroidserver-0.2.1/debian/patches/do-not-set-sdk_path-in-config.py-if-using-system-pro.patch
fdroidserver-0.2.1/debian/patches/do-not-set-sdk_path-in-config.py-if-using-system-pro.patch
---
fdroidserver-0.2.1/debian/patches/do-not-set-sdk_path-in-config.py-if-using-system-pro.patch
1970-01-01 01:00:00.0 +0100
+++
fdroidserver-0.2.1/debian/patches/do-not-set-sdk_path-in-config.py-if-using-system-pro.patch
2014-12-14 22:23:11.0 +0100
@@ -0,0 +1,139 @@
+From 5f5bcd2e11f45277b865400de14ea8e820318804 Mon Sep 17 00:00:00 2001
+From: Hans-Christoph Steiner h...@eds.org
+Date: Tue, 9 Dec 2014 15:20:29 +0100
+Forwarded: not-needed
+Origin: upstream, https://gitlab.com/fdroid/fdroidserver/merge_requests/31
+Subject: [PATCH 7/7] do not set sdk_path in config.py if using system-provided
+ aapt
+
+By not setting sdk_path when /usr/bin/aapt is found, sdk_path then defaults
+to $ANDROID_HOME when its used. Since in this case, aapt will be used from
+the system path, using aapt entirely ignores sdk_path. If the user runs
+`fdroid build` in this setup, sdk_path will be $ANDROID_HOME, so it should
+check the env vars for it, but maybe that doesn't actually work like that
+yet.
+---
+ examples/config.py | 2 +-
+ fdroidserver/common.py | 9 ++---
+ fdroidserver/init.py | 49 -
+ 3 files changed, 35 insertions(+), 25 deletions(-)
+
+--- a/examples/config.py
b/examples/config.py
+@@ -9,7 +9,7 @@
+ # Override the path to the Android NDK, $ANDROID_NDK by default
+ # ndk_path = /path/to/android-ndk
+ # Build tools version to be used
+-build_tools = 20.0.0
++# build_tools = 20.0.0
+
+ # Command for running Ant
+ # ant = /path/to/ant
+--- a/fdroidserver/common.py
b/fdroidserver/common.py
+@@ -161,7 +161,7 @@ def find_sdk_tools_cmd(cmd):
+ '''find a working path to a tool from the Android SDK'''
+
+ tooldirs = []
+-if 'sdk_path' in config and os.path.exists(config['sdk_path']):
++if config is not None and 'sdk_path' in config and
os.path.exists(config['sdk_path']):
+ # try to find a working path to this command, in all the recent
possible paths
+ if 'build_tools' in config:
+ build_tools = os.path.join(config['sdk_path'], 'build-tools')
+@@ -192,7 +192,11 @@ def find_sdk_tools_cmd(cmd):
+ def test_sdk_exists(c):
+ if 'sdk_path' not in c:
+ logging.error('sdk_path' not set in config.py!)
+-return False
++if 'aapt' in c and os.path.isfile(c['aapt']):
++return True
++else:
++logging.error('sdk_path' not set in config.py!)
++return False
+ if c['sdk_path'] is None:
+ # c['sdk_path'] is set to the value of ANDROID_HOME by default
+ logging.error('No
Bug#772898: win32-loader testing and newer fails with TRANSLATE error
Control: clone -1 -2 Control: retitle -2 nmu: nsis_2.46-9 Control: user -2 release.debian@packages.debian.org Control: usertag -2 +binnmu (Release Team, please see below :) ) Hi Bernhard Cyril, Many thanks for the detailed analysis! Le dimanche, 14 décembre 2014, 15.47:47 Bernhard Übelacker a écrit : Looks similar to bug #654380. (There mingw defaulted to produce dlls depending also on some other mingw dlls) There the upstream bug report [2] mentions that plugins must not depend on a shared libgcc. So I assume that the plugins must not depend on a shared libwinpthread-1.dll either. The package build of win32-loader uses this file /usr/share/nsis/Plugins/NSISdl.dll which comes from packge nsis-common. If plugins must not depend on other dlls, then also other projects or users are affected, who want to build their installers with Jessie/testing. However, when I try to rebuild package nsis-common I get a nsisdl.dll which does not suffer from this dependency. Unfortunately I cannot find a build log for amd64, just for i386 [3]. That one was build with g++-mingw-w64-i686 i386 4.9.0-2+13. My attempt uses g++-mingw-w64-i686 amd64 4.9.1-7+14.2. The changelog for g++-mingw-w64-i686 [4] shows this entry: gcc-mingw-w64 (14) unstable; urgency=medium * Provide compilers using Windows and POSIX threads. The default setup uses Windows threads, thus avoiding the dependency on the pthreads DLL (Closes: #748353, #750741). So probably the solution could be only these 2 steps? - to rebuild package nsis-common with the current g++-mingw-w64-i686 package This looks like it, indeed. I'm hereby cloning this bug into an NSIS binNMU request: @Release Team, could we please schedule binNMUs for nsis ? nmu nsis_2.46-9 . ALL . -m Rebuild with gcc-mingw-w64 14 to ensure that NSISdl.dll doesn't depend on a shared libwinpthread-1 - rebuild win32-loader with the newly built nsis-common package installed I'll upload win32-loader when nsis is available from the mirrors. Many thanks, cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773110: ITP: openorienteering-mapper -- orienteering mapmaking program
Hi Gaudenz, The software looks very interesting, thanks for ITP'ing it! One comment though: Le dimanche, 14 décembre 2014, 14.32:42 Gaudenz Steinlin a écrit : OpenOrienteering Mapper is an orienteering mapmaking program and provides a free alternative to the existing proprietary OCAD solution. Its main advantages compared to it are: . * Open Source: the program is completely free, every programmer can improve it. * Cross-platform: the program works on Android, Windows, Mac OS X and Linux. I don't feel that much of this is of interest in a Debian package description: I would rather focus on what the software actually _does_. Also the OCAD acronym is not explained. While it is under continuous development and considered in beta state, it has been used to produce maps for classical orienteering, MTBO and radio orienteering races. All required functions for drawing maps are implemented and the program works very stable. So it can be considered ready for productive use, although it is like always a good idea to keep backups of your files. I wouldn't include this paragraph either, as it feels slightly generic; it doesn't really help to determine whether I should install that software or not. Cheers, OdyX -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773168: remove afsql from default modules
Package: syslog-ng Version: 3.3.5-4 the module afsql is listed as default, although split into different package. That causes syslog complain about missing default module everytime it's reloaded. Please remove the module from list of default modules. Thank you. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. 2B|!2B, that's a question! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770706: [PKG-Openstack-devel] Bug#770706: Bug#770706: Bug#770706: Bug#770706: Bug#770706: Bug#770706: keystone.service does not start, /var/run/keystone not created
On 12/15/2014 04:44 PM, Gaudenz Steinlin wrote: I don't see a reason why this should not work, but I wonder why you don't just add an override_dh_systemd_enable target wich first uses pkgos to generate the service files and then just calls dh_systemd_enable. This seems like the more obvious solution to me. True, I could just have used the override there instead of in the installinit, however, I'm happy to have dh_systemd_enable to run normally when there's a debian/something.service the normal way. Having this in a separate target would probably also make it possible to build packages without systemd by just not build depending on dh-systemd. I don't see why you would like to do this. The dh-systemd utility is available in Wheezy backports, and even if the OpenStack packages do support systemd now, we don't have to use that as init system... This works, then, except for keystone where there's no #DEBHELPER# in the postinst (because I wanted to keep the control of when invoke-rc.d is called, ie after the daemon starts, the admin tenant is created, and the keystone endpoint is registered). This means that for Keystone, we need to manually add what dh_systemd_enable does. Then I've been asking myself what would happen in Wheezy, and it's looking like the only thing that will happen is that it's going to add a dependency on init-system-helpers, which IMO is quite fine, because it's already available from the official wheezy-backports. I don't understand the problem you are trying to solve here. Why are you not just adding the #DEBHELPER# at the end of the postinst where you want it to be? I don't see how the debhelper inserted snippets don't give you control over where they are called. But maybe I'm missing something. I just wanted to do things by hand myself for keystone, but all the other packages have it. Nothing to worry about IMO (the only thing I'm worried about is the unblock requests ...). Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771778: Info received (Bug#771778: Acknowledgement (squid3: Pinger segfault with libc))
Hi Louis, Packages in debian are built by our auto-building machines for each architecture. A version for amd64 has been built and uploaded and is waiting to be added to the repository. It will show up shortly. You can find a report on the autobuilding here: https://buildd.debian.org/status/package.php?p=squid3suite=wheezy-backports Regards, L -- Luigi Gangitano -- lu...@debian.org -- gangit...@lugroma3.org GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 GPG: 4096R/2BA97CED: 8D48 5A35 FF1E 6EB7 90E5 0F6D 0284 F20C 2BA9 7CED -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766591: [lintian] false positives on license-problem-cc-by-nc-sa
Hello Adam, thanks for your link. I don't know them. So I think I can close this bug. CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#773032: squid3: prompting due to modified conffiles which were not modified by the user: /etc/squid3/squid.conf
Hi Andreas, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded… Can you please provide more information on this process? Which version was the original install before the upgrade to 3.8.4-4? This is a violation of policy 10.7.3, see https://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which says [These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens.” I suspect that this comes from the fix we applied for #768170 which was a more critical bug while upgrading from Wheezy, since a line that was active by default in previous configuration now makes squid3 unable to start after upgrade. We choose to comment out that line during upgrade, in a script modifying /etc/squid3/squid.conf. In our tests we did not experience the behavior you reported, so I need more information to confirm that this is the case. Regards, L -- Luigi Gangitano -- lu...@debian.org -- gangit...@lugroma3.org GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26 GPG: 4096R/2BA97CED: 8D48 5A35 FF1E 6EB7 90E5 0F6D 0284 F20C 2BA9 7CED -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751638: reported upstream
I've forwarded the bug to upstream https://bugs.freedesktop.org/show_bug.cgi?id=87320 -- Salvo Tomaselli Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di senso, ragione ed intelletto intendesse che noi ne facessimo a meno. -- Galileo Galilei http://ltworf.github.io/ltworf/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773169: unblock: syncevolution/1.4.99.4-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package syncevolution It fixes #772040 and contains no other changes. I'll consider adsbs hints in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772040#15 in a later version. However, I want to make syncevolution work again and fix the SSLv3 only thing first. unblock syncevolution/1.4.99.4-3 -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12.7-05353-g11687ee (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash 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#773170: insserv: refuses to start postfix at boot because dnsmasq is disabled
Package: insserv Version: 1.16.0-5 Severity: critical Justification: breaks unrelated software Dear Maintainer, insserv refuses to start postfix at boot, because I have configured dnsmasq to be disabled. I don't use dnsmasq as a DNS cache, but as a DHCP server for when I create an ad-hoc network, so dnsmasq active or not has totally no effect on the ability of my system to resolve names. As you can see, postfix can be manually started (and works fine), but it can't be started at boot automatically. # systemctl enable postfix Synchronizing state for postfix.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d postfix defaults insserv: FATAL: service dnsmasq has to be enabled to use service postfix insserv: exiting now! update-rc.d: error: insserv rejected the script header *** Error in `systemctl': double free or corruption (fasttop): 0x7f9c9443e9c0 *** Annullato # service postfix start # service dnsmasq status ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled) Drop-In: /run/systemd/generator/dnsmasq.service.d └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf Active: inactive (dead) # service postfix status ● postfix.service - LSB: Postfix Mail Transport Agent Loaded: loaded (/etc/init.d/postfix) Drop-In: /run/systemd/generator/postfix.service.d └─50-postfix-$mail-transport-agent.conf Active: active (running) since lun 2014-12-15 10:52:31 CET; 11s ago Process: 1204 ExecStart=/etc/init.d/postfix start (code=exited, status=0/SUCCESS) CGroup: /system.slice/postfix.service ├─1325 /usr/lib/postfix/master ├─1326 pickup -l -t fifo -u -c └─1327 qmgr -l -t fifo -u dic 15 10:52:31 hal9000 postfix[1204]: Starting Postfix Mail Transport Agent: postfix. dic 15 10:52:31 hal9000 systemd[1]: Started LSB: Postfix Mail Transport Agent. dic 15 10:52:31 hal9000 postfix/master[1325]: daemon started -- version 2.11.3, configuration /etc/postfix -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.17.2d (SMP w/4 CPU cores; PREEMPT) 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 insserv depends on: ii libc62.19-13 ii libdbus-1-3 1.9.4-1 insserv recommends no packages. Versions of packages insserv suggests: pn bootchart2 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#773172: linux: Easier PCI Stub support with CONFIG_PCI_STUB=y
Source: linux Severity: wishlist Dear Maintainer, Using the kernel commandline option pci-stub.ids= is a very popular and easy way of preventing device drivers from attaching to devices that are meant to be assigned (PCI passthrough via Vt-d/IOMMU) to virtual machines. Currently Debian's default kernel images do not support this parameter because pci-stub has been configured as a module. Loading the module via /etc/modules or /etc/initramfs-tools/modules does not seem to guarantee that the pci-stub module gets loaded before other device drivers have a chance to snatch up the devices that need to be stubbed. I propose we change the default from CONFIG_PCI_STUB=m to CONFIG_PCI_STUB=y so that Debian can support the widely popular practice of specifying pci-stub.ids on the kernel commandline. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.17.0-trunk-amd64 (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) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773171: epoll_ctl failed increasing number of open file descriptors
Package: rsyslog Version: 5.8.11-3 Severity: Important Rsyslog doesn't release sockets causing the continuous increase of open file descriptors till the MaxOpenFiles reached (epoll_ctl failed message is an consequence of this behaviour). Looks like it's caused by the bug in GunTLS session handling. Review https://bugzilla.redhat.com/show_bug.cgi?id=848852 for reference. The patch has been implemented already, but causing some performance issues unfortunately. Would be good to review the code and include it in the updates. -- Peter Viskup
Bug#328318: pci.ids copies
Hi Matt $ apt-file search pci.ids fusioninventory-agent: /usr/share/fusioninventory/pci.ids Actually, the fusioninventory package use the correct pci.ids file, see: http://sources.debian.net/src/fusioninventory-agent/1:2.3.10.1-1/debian/patches/pciutils-pciids.diff/ Even if fusioninventory-agent, don't use it, this pci.ids should not be installed. I will adjust the package. Thanks for pointing this. Best regards, -- Gonéri Le Bouder signature.asc Description: PGP signature
Bug#773173: grub2: Support generating entry menus for other supported init system in advanced mode
Source: grub2
Version: 2.02~beta2-18
Severity: wishlist
Dear Maintainer,
It would be good to have the option to other supported init system for linux
in the advanced option entry.
We should only list installed init systems that are not set as the
default, as
well as supporting various way of being set as default (either by GRUB
variables
or with init symlinks).
Note that OS vendor may have a different supported init system (ubuntu
would only support, and thus list, upstart and systemd for instance)
Please find attached a patch supporting that. I used git-dpm to generate
it, but not really familiar with this tool yet (seems that it's showing
in the main branch after git-dpm dch as if it was inline and hides
debian/patches/patch_name, so I hope this is all correct.
-- System Information:
Debian Release: jessie/sid
APT prefers vivid-updates
APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500,
'vivid'), (400, 'vivid-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-25-generic (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
From fcc1bd90d3ac427a7358cafa2a9ae0ecc5ba7fd7 Mon Sep 17 00:00:00 2001
From: Didier Roche didro...@ubuntu.com
Date: Mon, 15 Dec 2014 09:55:02 +0100
Subject: [PATCH] Generate alternatives init entries in advanced menu
For linux and linux-xen, enables generating alternatives init entries.
We generate those from a list of supported init alternatives, and if they
are installed, but not default (either pointed by init=/sbin/init or overidden
in GRUB_CMDLINE_LINUX_DEFAULT), add a corresponding entry to the advanced menu.
Add GRUB_DISABLE_OTHERINITS as an option to mask those generated entries.
Note that the list of init alternatives may be restricted by the OS vendor.
Patch-Name: add-other-inits.patch
---
docs/grub.texi | 19 +++
util/grub-mkconfig.in | 6 +-
util/grub.d/10_linux.in | 24
util/grub.d/20_linux_xen.in | 34 +-
4 files changed, 73 insertions(+), 10 deletions(-)
diff --git a/docs/grub.texi b/docs/grub.texi
index af020ec..cf30505 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -1374,11 +1374,13 @@ A command to configure the serial port when using the serial console.
Command-line arguments to add to menu entries for the Linux kernel.
@item GRUB_CMDLINE_LINUX_DEFAULT
-Unless @samp{GRUB_DISABLE_RECOVERY} is set to @samp{true}, two menu
+Unless @samp{GRUB_DISABLE_RECOVERY} is set to @samp{true}, at least two menu
entries will be generated for each Linux kernel: one default entry and one
-entry for recovery mode. This option lists command-line arguments to add
-only to the default menu entry, after those listed in
-@samp{GRUB_CMDLINE_LINUX}.
+entry for recovery mode. There will be additional entries if other init systems
+are installed unless @samp{GRUB_DISABLE_OTHERINITS} is set to @samp{true}.
+This option lists command-line arguments to add only to non recovery menu
+entry, after those listed in @samp{GRUB_CMDLINE_LINUX}. Any init= will be
+of course stripped for non default init system menu entry.
@item GRUB_CMDLINE_NETBSD
@itemx GRUB_CMDLINE_NETBSD_DEFAULT
@@ -1409,6 +1411,11 @@ disable the use of UUIDs, set this option to @samp{true}.
If this option is set to @samp{true}, disable the generation of recovery
mode menu entries.
+@item GRUB_DISABLE_OTHERINITS
+If this option is set to @samp{true}, disable the generation of additional
+menu entries for each non default installed init systems.
+Note that the list of init alternatives may be restricted by the OS vendor.
+
@item GRUB_VIDEO_BACKEND
If graphical video support is required, either because the @samp{gfxterm}
graphical terminal is in use or because @samp{GRUB_GFXPAYLOAD_LINUX} is set,
@@ -1504,6 +1511,10 @@ This option sets the English text of the string that will be displayed in
parentheses to indicate that a boot option is provided to help users recover
a broken system. The default is recovery mode.
+@item GRUB_OTHERINITS_TITLE
+This option sets the English text of the string that will be displayed in
+parentheses to indicate that a boot option is provided to help users booting
+with other installed init systems. The default is with init_system_name.
@end table
The following options are still accepted for compatibility with existing
diff --git a/util/grub-mkconfig.in b/util/grub-mkconfig.in
index 4641563..fb43b4d 100644
--- a/util/grub-mkconfig.in
+++ b/util/grub-mkconfig.in
@@ -190,6 +190,9 @@ if [ x${GRUB_RECOVERY_TITLE} = x ]; then
GRUB_RECOVERY_TITLE=recovery mode
fi
+if [ x${GRUB_OTHERINITS_TITLE} = x ]; then
+ GRUB_OTHERINITS_TITLE=with %s
+fi
# These are defined in this script, export them here so that user can
# override them.
@@ -242,7 +245,8 @@ export GRUB_DEFAULT \
Bug#741464: grub-pc-bin: hangs after displaying boot menu
Thu, 16 Oct 2014 17:57:20 +0200 Sven Joachim svenj...@gmx.de wrote: On 2014-10-13 16:25 +0200, Colin Watson wrote: On Wed, Mar 12, 2014 at 08:24:31PM +0100, Sven Joachim wrote: After upgrading the grub packages and rebooting my laptop, grub displayed the boot menu and then was hung. The countdown before booting the default kernel was not started and grub did not accept any keyboard input. I had to boot a rescue system from a USB stick, chroot into my installation and downgrade to 2.00-22 to get back to a working system. Sorry for the delay in replying to this. Could you please post the output of: sudo debconf-show grub-pc ? Is there anything else interesting about your system, since this is not something I can reproduce? I have diverted /sbin/update-grub to maintain /boot/grub/grub.cfg by hand, as you suggested in bug #578576. Therefore the debconf data are probably not too interesting. Bearing in mind the period of time involved, it might also be worth trying with 2.02~beta2-14 now that you have rescue media to hand. I have managed to install 2.02~beta2-15 on a USB stick which is much easier to recover, and the offending command which causes grub to freeze is terminal_input at_keyboard, which I have been using for obtaining a German keyboard layout (see #686817 on that matter; I'm sure there was an even older bug, but cannot find it now). If I remove that statement, grub works. From the grub command line I can insmod at_keyboard without problems, but terminal_input at_keyboard freezes grub. I tried to reproduce this in a virtual machine (using kvm), but under kvm everything seems to work fine including the german keyboard layout. When I tried it on real hardware I could reproduce the problem, but instead of freezing I got garbage input after switching terminal_input to at_keyboard. Kind regards, Jeroen Dekkers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773174: unblock: debdelta/0.55 , or discuss on the matter
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Dear Release team, I uploaded a new version of debdelta ; unfortunately (my fault) I did not realize that this time the freeze policy is so tight. Please unblock package debdelta, or let us discuss if there is some set of changes that you are willing to let into Jessie. Note that the package 'debdelta' contains both the server code and the client code . The server code is quite old, but this is not a problem, since few people (if any) need to use the server code. (The up-to-date server code is in GIT, and is in use in the server that generates deltas for 'debdelta-upgrade' , that is the client tool). The client code is agnostic, it can apply deltas generated by server code that is much more advanced than what is shipped in the package (as long as the GPG key matches!) Let me highlight all the changes between the version 0.50+2 in stable, and 0.55 in unstable; I will list them in decreasing order of importance. 'S' means : affects server code 'C' means : affects client code 'P' means : affects packaging 1C) ship new GPG key; the key currently available in the clients in wheezy and in testing will expire 2015-08-24 so it will need to be updated during the lifetime of Jessie. 2P) Bug fix: owned and unowned files after purge (policy 6.8 + 10.7.3), (Closes: #617481). These are all the changes in debian/postrm and debian/postinst that you see in the debdiff 3C) Portuguese translation (Closes: #760731). 4C) add a stanza in etc/sources.conf to tell the client where to find deltas for backports 5P) ship in .dsc , and then build, only what is committed in git archive; so the following files are not shipped any more debdelta-0.55/contrib/debmirror-delta-security.ubuntu debdelta-0.55/old/README debdelta-0.55/old/README.upgrade debdelta-0.55/po/pt.po debdelta-0.55/preunpacking/tarpu.py 6CS) close unneeded file descriptor when invoking subprocesses 7P) bump Standards Version (no change) 8C) do not get confused by broken symlinks 9P) debian/rules : add build-arch, build-indep 10S) support data.tar.xz, with XZ parameter autodetection 11P) update location of GIT repository in debian/control 12S) add ability to cache intermediate data 13C) wait for subprocesses to avoid zombies 15CS) change code to be more ready for a future switch to Python 3 , and some other minor code improvements If you think that there are too many changes, but some of the above changes may enter into testing (and then in Jessie) please tell me which one, and I will upload a new version. All server-code related changes may be omitted w/o affecting the client. I attach the 'cleaned up' debdiff. In this debdiff I deleted all references to the files listed in (5P) that simply disappeared from the package, and the portuguese translation. I also deleted duplicates (since my package uses symlinks, each change is reported 5 times by debdiff). If you wish, unblock debdelta/0.55 otherwise please tell me which changes may be accepted. I personally would love to see changes 1 to 4 included; these do not really affect the code, but have large positive impact. Thanks and sorry for the mess. a. signature.asc Description: Digital signature
Bug#772793: cpio: CVE-2014-9112
On Fri, 12 Dec 2014, Aníbal Monsalve Salazar wrote: Patches: http://git.savannah.gnu.org/cgit/cpio.git/commit/?id=746f3ff6 http://git.savannah.gnu.org/cgit/cpio.git/commit/?id=54d1c42a http://git.savannah.gnu.org/cgit/cpio.git/commit/?id=58df4f1b There seem to be additional issues with the fix for i386: https://bugzilla.redhat.com/show_bug.cgi?id=1167571#c9 (not verified by myself, just noticed in Red Hat's Bugzilla). Regards, Salvatore Dear debian-devel, I uploaded cpio 2.11+dfsg-3 to experimental with the upstream patches listed above. Please test it. It didn't segfault when I run it on amd64 as reported in Red Hat's Bugzilla. There are two supplementary relevant fixes that have been committed upstream: http://git.savannah.gnu.org/cgit/cpio.git/commit/?id=fd262d11 http://git.savannah.gnu.org/cgit/cpio.git/commit/?id=f6a8a2cb The latter only fixes the test suite in some architectures but the former fixes a NULL pointer dereference... whether it has some security implications can be debated but it looks a good idea to include it too. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773032: squid3: prompting due to modified conffiles which were not modified by the user: /etc/squid3/squid.conf
On 2014-12-15 10:43, Luigi Gangitano wrote: Can you please provide more information on this process? Which version was the original install before the upgrade to 3.8.4-4? The wheezy version. I suspect that this comes from the fix we applied for #768170 which was a more critical bug while upgrading from Wheezy, since a line that was active by default in previous configuration now makes squid3 unable to start after upgrade. We choose to comment out that line during upgrade, in a script modifying /etc/squid3/squid.conf. That must be done in the postinst, after dpkg has handled the conffiles. If the configuration was unmodified, dpkg will install the new one and the offending lines will be gone before the postinst tries to fix them. Doing this in the preinst will cause dpkg to always see a locally modified conffile. In our tests we did not experience the behavior you reported, so I need more information to confirm that this is the case. Try a pristine wheezy install with shipped configuration and distupgrade with DEBIAN_FRONTEND=noninteractive Andreas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773168: [Syslog-ng-maintainers] Bug#773168: remove afsql from default modules
Control: reassign -1 syslog-ng-core Control: forcemerge -1 650814 Matus == Matus UHLAR - fantomas uh...@fantomas.sk writes: Matus the module afsql is listed as default, although split into different Matus package. That causes syslog complain about missing default module everytime Matus it's reloaded. Please remove the module from list of default Matus modules. This is the same as #650814, which has been fixed in syslog-ng = 3.4 (and thus in testing and sid, and in wheezy-backports too). There are no plans to fix the issue in the 3.3 branch. If you wish to stick with 3.3 (and not use 3.5 from backports), I'd recommend either installing syslog-ng-mod-sql, or passing --default-modules to syslog-ng, to override its default. -- |8] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773175: unblock: povray/3.7.0.0-7
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package povray
Fixes an upgrade issue from squeeze: dpkg prompting about modified
conffiles due to unconditionally renaming the old ones in the preinst.
* povray in squeeze was in non-free
* wheezy did not ship povray at all
Switch to dpkg-maintscript-helper mv_conffile to do this properly.
(no bug filed, Severity: serious)
Fix some bashisms by using bash as the interpreter for these scripts.
(#772356, important)
unblock povray/3.7.0.0-7
diff -Nru povray-3.7.0.0/debian/changelog povray-3.7.0.0/debian/changelog
--- povray-3.7.0.0/debian/changelog 2014-09-29 17:55:20.0 +0200
+++ povray-3.7.0.0/debian/changelog 2014-12-15 11:06:09.0 +0100
@@ -1,3 +1,25 @@
+povray (1:3.7.0.0-7) unstable; urgency=medium
+
+ * 40_bashism.diff: Use bash as the interpreter for scripts that use
+non-posix extensions of the 'read' builtin (allanim.sh, allscene.sh,
+portfolio.sh). Patch all scripts consistently. (Closes: #772356)
+
+ -- Andreas Beckmann a...@debian.org Mon, 15 Dec 2014 11:05:58 +0100
+
+povray (1:3.7.0.0-6) unstable; urgency=medium
+
+ * povray.maintscript: New. Use dpkg-maintscript-helper to rename the
+conffiles from the squeeze package: /etc/povray/3.6/povray.{ini,conf} to
+/etc/povray/3.7/povray.{ini,conf}. Needs ${misc:Pre-Depends}.
+ * povray.preinst: Remove. Directly renaming the directory resulted in dpkg
+prompting about modified conffiles.
+ * povray.postinst: New. Remove the empty directory after
+dpkg-maintscript-helper handled the conffiles.
+ * Update Vcs-Browser URL.
+ * Bump Standards-Version to 3.9.6, no changes needed.
+
+ -- Andreas Beckmann a...@debian.org Sun, 14 Dec 2014 01:47:17 +0100
+
povray (1:3.7.0.0-5) unstable; urgency=medium
* povray-includes: No longer use a symlinked doc directory to restore
diff -Nru povray-3.7.0.0/debian/control povray-3.7.0.0/debian/control
--- povray-3.7.0.0/debian/control 2014-09-29 17:55:20.0 +0200
+++ povray-3.7.0.0/debian/control 2014-12-15 11:06:09.0 +0100
@@ -17,13 +17,14 @@
libopenexr-dev,
libsdl-dev,
libxpm-dev,
-Standards-Version: 3.9.5
+Standards-Version: 3.9.6
Homepage: http://www.povray.org
Vcs-Git: git://anonscm.debian.org/collab-maint/povray.git
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/povray.git
+Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/povray.git
Package: povray
Architecture: any
+Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}, ${misc:Depends}
Recommends: povray-includes
Suggests: povray-doc, povray-examples
diff -Nru povray-3.7.0.0/debian/patches/40_bashism.diff povray-3.7.0.0/debian/patches/40_bashism.diff
--- povray-3.7.0.0/debian/patches/40_bashism.diff 2014-09-29 17:55:20.0 +0200
+++ povray-3.7.0.0/debian/patches/40_bashism.diff 2014-12-15 11:06:09.0 +0100
@@ -1,6 +1,50 @@
+Author: Andreas Beckmann a...@debian.org
+Description: use bash as interpreter for scripts using non-posix extensions for read
+Bug-Debian: https://bugs.debian.org/772356
+
--- a/unix/scripts/portfolio.sh
+++ b/unix/scripts/portfolio.sh
-@@ -86,7 +86,7 @@
+@@ -1,4 +1,4 @@
+-#!/bin/sh
++#!/bin/bash
+ # ==
+ # POV-Ray 3.7
+ # portfolio.sh - render the POV-Ray portfolio
+@@ -86,7 +86,7 @@ if [ ! -d $SCENE_DIR ] ; then
+ echo so this script does not work.
+ echo Try reinstalling POV-Ray.
+ echo --
+- read
++ read dontcare
+ exit
+ fi
+
+--- a/unix/scripts/allanim.sh
b/unix/scripts/allanim.sh
+@@ -1,4 +1,4 @@
+-#!/bin/sh
++#!/bin/bash
+ # ==
+ # POV-Ray 3.7
+ # allanim.sh - render all POV-Ray sample animations
+@@ -89,7 +89,7 @@ if [ ! -d $SCENE_DIR ] ; then
+ echo so this script does not work.
+ echo Try reinstalling POV-Ray.
+ echo --
+- read
++ read dontcare
+ exit
+ fi
+
+--- a/unix/scripts/allscene.sh
b/unix/scripts/allscene.sh
+@@ -1,4 +1,4 @@
+-#!/bin/sh
++#!/bin/bash
+ # ==
+ # POV-Ray 3.7
+ # allscene.sh - render all POV-Ray sample scenes
+@@ -95,7 +95,7 @@ if [ ! -d $SCENE_DIR ] ; then
echo so this script does not work.
echo Try reinstalling POV-Ray.
echo --
diff -Nru povray-3.7.0.0/debian/povray.maintscript povray-3.7.0.0/debian/povray.maintscript
--- povray-3.7.0.0/debian/povray.maintscript 1970-01-01 01:00:00.0 +0100
+++ povray-3.7.0.0/debian/povray.maintscript 2014-12-15 11:06:09.0 +0100
@@ -0,0 +1,2 @@
+mv_conffile /etc/povray/3.6/povray.ini /etc/povray/3.7/povray.ini 1:3.7~
+mv_conffile /etc/povray/3.6/povray.conf
Bug#772551: Suricata: missing library libhtp-0.5.12.so.1
Dear maintainer This problem also concerns the armhf architecture Regards, Manuel VIVES -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773176: snd-gtk-alsa not available?
Package: snd-gtk Severity: wishlist Is there a reason an alsa build of snd-gtk is not provided? (considering snd is built with alsa, I don't think it's a technical limitation). -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') 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: 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#773177: gcc-defaults: enable multilib on mips64*
Source: gcc-defaults
Version: 1.135
Severity: important
Tags: patch
Hi,
This patch enables multilib on mips64 and mips64el. Currently gcc-4.9
build-depends on g++-multilib on mips64el, but that package isn't built
by gcc-defaults.
While I was doing the modifications, I also enabled gccgo on mips64
since it's built by gcc-4.9 as well. I didn't enable gcj in the
gcj_archs field because gcj seems to be broken on mips64el (I haven't
investigated why).
Thanks,
James
From 55efad3ed9530dbfddce85bfce8cc272f162363e Mon Sep 17 00:00:00 2001
From: James Cowgill james...@cowgill.org.uk
Date: Mon, 15 Dec 2014 10:39:41 +
Subject: [PATCH] Add mips64 and mips64el to gcc-defaults
---
debian/control | 12 ++--
debian/rules | 6 +++---
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/debian/control b/debian/control
index 07beb43..bef210f 100644
--- a/debian/control
+++ b/debian/control
@@ -44,7 +44,7 @@ Description: GNU C++ compiler
Package: g++-multilib
Priority: optional
-Architecture: amd64 i386 kfreebsd-amd64 mips mipsel powerpc ppc64 s390 s390x sparc sparc64 x32
+Architecture: amd64 i386 kfreebsd-amd64 mips mips64 mips64el mipsel powerpc ppc64 s390 s390x sparc sparc64 x32
Depends: cpp (= ${version:cpp}), gcc-multilib (= ${version:cpp}), g++ (= ${version:cpp}), g++-${pv:gpp}-multilib ${reqv:gpp}, ${misc:Depends}
Description: GNU C++ compiler (multilib files)
This is the GNU C++ compiler, a fairly portable optimizing compiler for C++.
@@ -67,7 +67,7 @@ Description: GNU Objective-C compiler
Package: gobjc-multilib
Priority: optional
-Architecture: amd64 i386 kfreebsd-amd64 mips mipsel powerpc ppc64 s390 s390x sparc sparc64 x32
+Architecture: amd64 i386 kfreebsd-amd64 mips mips64 mips64el mipsel powerpc ppc64 s390 s390x sparc sparc64 x32
Depends: cpp (= ${version:cpp}), gcc-multilib (= ${version:cpp}), gobjc (= ${version:gcc}), gobjc-${pv:gobjc}-multilib ${reqv:gobjc}, ${misc:Depends}
Description: GNU Objective-C compiler (multilib files)
This is the GNU Objective-C compiler, which compiles Objective-C on
@@ -92,7 +92,7 @@ Description: GNU Objective-C++ compiler
Package: gobjc++-multilib
Priority: optional
-Architecture: amd64 i386 kfreebsd-amd64 mips mipsel powerpc ppc64 s390 s390x sparc sparc64 x32
+Architecture: amd64 i386 kfreebsd-amd64 mips mipsel mips64 mips64el powerpc ppc64 s390 s390x sparc sparc64 x32
Depends: cpp (= ${version:cpp}), gobjc-multilib (= ${version:cpp}), gobjc++ (= ${version:gcc}), gobjc++-${pv:gobjcxx}-multilib ${reqv:gobjcxx}, ${misc:Depends}
Description: GNU Objective-C++ compiler (multilib files)
This is the GNU Objective-C++ compiler, which compiles Objective-C++ on
@@ -116,7 +116,7 @@ Description: GNU Fortran 95 compiler
Package: gfortran-multilib
Priority: optional
-Architecture: amd64 i386 kfreebsd-amd64 mips mipsel powerpc ppc64 s390 s390x sparc sparc64 x32
+Architecture: amd64 i386 kfreebsd-amd64 mips mips64 mips64el mipsel powerpc ppc64 s390 s390x sparc sparc64 x32
Depends: cpp (= ${version:cpp}), gcc-multilib (= ${version:cpp}), gfortran (= ${version:gcc}), gfortran-${pv:gfort}-multilib ${reqv:gfort}, ${misc:Depends}
Description: GNU Fortran 95 compiler (multilib files)
This is the GNU Fortran compiler, which compiles Fortran 95 on platforms
@@ -139,7 +139,7 @@ Description: Go compiler, based on the GCC backend
Package: gccgo-multilib
Priority: optional
-Architecture: amd64 i386 mips mipsel powerpc ppc64 s390 s390x x32
+Architecture: amd64 i386 mips mips64 mips64el mipsel powerpc ppc64 s390 s390x x32
Depends: cpp (= ${version:cpp}), gcc-multilib (= ${version:cpp}), gccgo (= ${version:ggo}), gccgo-${pv:ggo}-multilib ${reqv:ggo}, ${misc:Depends}
Description: Go compiler, based on the GCC backend (multilib files)
This is the GNU Go compiler, which compiles Go on platforms supported by
@@ -239,7 +239,7 @@ Description: GNU C compiler
Package: gcc-multilib
Priority: optional
-Architecture: amd64 i386 kfreebsd-amd64 mips mipsel powerpc ppc64 s390 s390x s390x sparc sparc64 x32
+Architecture: amd64 i386 kfreebsd-amd64 mips mips64 mips64el mipsel powerpc ppc64 s390 s390x s390x sparc sparc64 x32
Depends: cpp (= ${version:cpp}), gcc (= ${version:gcc}), gcc-${pv:gcc}-multilib ${reqv:gcc}, ${misc:Depends}, linux-libc-dev (= 3.0.0-2) [linux-any]
Breaks: gcc-4.9-arm-linux-gnueabihf, gcc-4.9-arm-linux-gnueabi, gcc-4.9-powerpc-linux-gnu, gcc-4.9-powerpc64el-linux-gnu, gcc-4.9-mipsel-linux-gnu
Description: GNU C compiler (multilib files)
diff --git a/debian/rules b/debian/rules
index 59bf438..b1b689a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -259,10 +259,10 @@ gcj_native_archs = alpha amd64 armel armhf arm64 hppa i386 ia64 mips mipsel \
powerpc powerpcspe ppc64 ppc64el s390 s390x sh4 sparc sparc64 x32 \
kfreebsd-amd64 kfreebsd-i386 hurd-i386
-multilib_archs = amd64 i386 kfreebsd-amd64 mips mipsel powerpc ppc64 \
- s390 s390x sparc sparc64 x32
+multilib_archs = amd64 i386 kfreebsd-amd64 mips mips64 mips64el mipsel \
Bug#773178: unblock: biomaj-watcher/1.2.2-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-CC: debian-...@lists.debian.org
Please unblock package biomaj-watcher
biomaj-watcher depended on tomcat6. Jessie uses Tomcat8 a,d biomaj-watcher
does not work anymore. This fix release changes the package to use tomcat8
and fixes bug 769348
Here is debdiff:
diff -Nru biomaj-watcher-1.2.2/debian/changelog
biomaj-watcher-1.2.2/debian/changelog
--- biomaj-watcher-1.2.2/debian/changelog 2014-06-23 09:13:13.0
+0200
+++ biomaj-watcher-1.2.2/debian/changelog 2014-12-15 11:26:27.0
+0100
@@ -1,3 +1,9 @@
+biomaj-watcher (1.2.2-2) unstable; urgency=medium
+
+ * Switch to Tomcat 8 (Closes: #769348).
+
+ -- Olivier Sallou osal...@debian.org Mon, 15 Dec 2014 08:03:09 +0100
+
biomaj-watcher (1.2.2-1) unstable; urgency=medium
* New usptream release:
diff -Nru biomaj-watcher-1.2.2/debian/control
biomaj-watcher-1.2.2/debian/control
--- biomaj-watcher-1.2.2/debian/control 2014-06-23 09:13:56.0 +0200
+++ biomaj-watcher-1.2.2/debian/control 2014-12-15 08:04:53.0 +0100
@@ -21,7 +21,7 @@
Package: biomaj-watcher
Architecture: all
-Depends: ${misc:Depends}, default-jdk, tomcat6 (=6.0.32-3), biomaj (=
1.2.1), debconf,
+Depends: ${misc:Depends}, default-jdk, tomcat8 , biomaj (= 1.2.1),
debconf,
liblog4j1.2-java, libjsch-java (= 0.1.42),libjdom1-java (= 1.1),
libcommons-lang-java (=2.4),
libcommons-logging-java (=1.1),libquartz-java(=1.6),libxerces2-java,
unzip, zip, libgnumail-java
Description: biological data-bank updater - web interface
diff -Nru biomaj-watcher-1.2.2/debian/patches/series
biomaj-watcher-1.2.2/debian/patches/series
--- biomaj-watcher-1.2.2/debian/patches/series 2014-01-09
16:25:31.0 +0100
+++ biomaj-watcher-1.2.2/debian/patches/series 2014-12-15
10:37:02.0 +0100
@@ -1 +1,2 @@
prevent_jobs_file_move
+use_tomcat8
diff -Nru biomaj-watcher-1.2.2/debian/patches/use_tomcat8
biomaj-watcher-1.2.2/debian/patches/use_tomcat8
--- biomaj-watcher-1.2.2/debian/patches/use_tomcat8 1970-01-01
01:00:00.0 +0100
+++ biomaj-watcher-1.2.2/debian/patches/use_tomcat8 2014-12-15
10:40:03.0 +0100
@@ -0,0 +1,17 @@
+Subject: adapt xml for Tomcat8
+Description: use tomcat8, this impact the context descriptor
+Author: Olivier Sallou osal...@debian.org
+Last-Updated: 2014-12-15
+Forwarded: No
+--- a/usr/share/biomaj-watcher/bin/WatcherConfigurator.java
b/usr/share/biomaj-watcher/bin/WatcherConfigurator.java
+@@ -45,7 +45,8 @@
+ PrintWriter pw = new PrintWriter(biomajConf + /BmajWatcher.xml);
+
+ pw.println(?xml version=\1.0\ encoding=\UTF-8\?);
+- pw.println(Context path=\/BmajWatcher\
docBase=\/usr/share/java/webapps/biomaj-watcher\ reloadable=\false\
allowLinking=\true\);
++ pw.println(Context path=\/BmajWatcher\
docBase=\/usr/share/java/webapps/biomaj-watcher\ reloadable=\false\
);
++ pw.println(Resources allowLinking=\true\/);
+
+ pw.println(Parameter name=\ADMIN_LOGIN\ value=\ +
params.get(app_login) + \ override=\false\/);
+
diff -Nru biomaj-watcher-1.2.2/debian/postinst
biomaj-watcher-1.2.2/debian/postinst
--- biomaj-watcher-1.2.2/debian/postinst 2014-01-09 16:25:31.0 +0100
+++ biomaj-watcher-1.2.2/debian/postinst 2014-12-15 11:05:48.0 +0100
@@ -49,8 +49,8 @@
ln -s /usr/share/java/gnumail.jar
/usr/share/java/webapps/biomaj-watcher/WEB-INF/lib/gnumail.jar
#cp /usr/share/biomaj/lib/biomaj.jar /var/lib/tomcat6/shared/
- rm -f /var/lib/tomcat6/shared/biomaj.jar
- cp /usr/share/biomaj/lib/biomaj.jar
/var/lib/tomcat6/shared/biomaj.jar
+ rm -f /usr/share/java/webapps/biomaj-watcher/WEB-INF/lib/biomaj.jar
+ cp /usr/share/biomaj/lib/biomaj.jar
/usr/share/java/webapps/biomaj-watcher/WEB-INF/lib/biomaj.jar
# Install latest definition
cp /usr/share/java/webapps/biomaj-watcher/jobs.xsd
/etc/biomaj-watcher/jobs.xsd
@@ -62,24 +62,17 @@
# Update logs
set_perms /var/log/biomaj
- #chown -R tomcat6 /etc/biomaj/db_properties
- chown -R tomcat6 /usr/share/java/webapps/biomaj-watcher
- #chmod -R 775 /etc/biomaj/db_properties
- #chown -R tomcat6 /var/log/biomaj
- #chmod -R 775 /var/log/biomaj
- #chown -R tomcat6 /var/lib/biomaj
- #chmod -R 775 /var/lib/biomaj
- chown -R tomcat6 /etc/biomaj-watcher
+ chown -R tomcat8 /usr/share/java/webapps/biomaj-watcher
+ chown -R tomcat8 /etc/biomaj-watcher
# Update context
java -cp $biomajwatcher_root/bin UpdateToBiomaj1_2
/usr/share/java/webapps/biomaj-watcher admin
- chown -R tomcat6 /etc/biomaj-watcher
- #cp /etc/biomaj-watcher/BmajWatcher*.xml
/var/lib/tomcat6/conf/Catalina/localhost/
- rm -f /etc/tomcat6/Catalina/localhost/BmajWatcher.xml
- rm -f /etc/tomcat6/Catalina/localhost/BmajWatcher#logs.xml
- ln -s /etc/biomaj-watcher/BmajWatcher.xml
/etc/tomcat6/Catalina/localhost/BmajWatcher.xml
- ln -s /etc/biomaj-watcher/BmajWatcher#logs.xml
Bug#773179: qpidd: unowned directories after purge: /var/{log,spool}/qpid/
Package: qpidd Version: 0.16-9 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned directories 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 Filing this as important as having a piuparts clean archive is a release goal since lenny. The maintainer scripts create (and later remove) a file in that directory. Manual directory removal may be not appropriate as this directory is shared between several packages. If the package would ship this as an empty directory, dpkg would take care of the creation and removal (if it's empty). From the attached log (scroll to the bottom...): 0m40.7s ERROR: FAIL: Package purging left files on system: /var/log/qpid/ not owned /var/spool/qpid/ not owned cheers, Andreas qpidd_0.16-9.log.gz Description: application/gzip
Bug#773180: (pre-approval) unblock: dbus with #773107 fixed
Package: release.debian.org Severity: wishlist User: release.debian@packages.debian.org Usertags: unblock I just uploaded a dbus version to experimental with more robust owner/permissions setting for dbus-daemon-launch-helper (debdiff attached). Would you be willing to consider equivalent changes via unstable (probably as dbus/1.8.12-2) for jessie? Context: while upgrading a wheezy system to jessie, I hit the same man-db - man-db trigger cycle that Paul Gevers reported in https://bugs.debian.org/771730#20. This left dbus system services in a temporarily broken state, because dbus had been unpacked but not configured. With https://bugs.debian.org/773107 fixed, this broken state would be avoided. I have tested the experimental dbus in an upgrade (a real system) and a new installation (minimal cdebootstrap), and it correctly leaves dbus-daemon-launch-helper 4754 root:messagebus in both cases. Regards, S diffstat for dbus-1.9.4 dbus-1.9.4 changelog | 13 + dbus.postinst |5 +++-- dbus.postrm |6 ++ dbus.preinst | 20 4 files changed, 42 insertions(+), 2 deletions(-) diff -Nru dbus-1.9.4/debian/changelog dbus-1.9.4/debian/changelog --- dbus-1.9.4/debian/changelog 2014-11-24 13:58:25.0 + +++ dbus-1.9.4/debian/changelog 2014-12-15 08:18:25.0 + @@ -1,3 +1,16 @@ +dbus (1.9.4-2) experimental; urgency=medium + + * postinst: use dpkg-statoverride to set the permissions for +dbus-daemon-launch-helper (expected to be 04754 root:messagebus) +as suggested in Policy §10.9. This avoids a temporarily broken state +when an upgraded dbus is unpacked but not yet configured (Closes: #773107) + * preinst: opportunistically set up the same dpkg-statoverride entry +if the group already exists, to avoid the same broken state during +upgrades from older versions without needing Pre-Depends: adduser + * postrm: delete the dpkg-statoverride entry on purge + + -- Simon McVittie s...@debian.org Mon, 15 Dec 2014 08:18:15 + + dbus (1.9.4-1) experimental; urgency=medium * New upstream release 1.9.4 diff -Nru dbus-1.9.4/debian/dbus.postinst dbus-1.9.4/debian/dbus.postinst --- dbus-1.9.4/debian/dbus.postinst 2014-11-24 13:58:25.0 + +++ dbus-1.9.4/debian/dbus.postinst 2014-12-15 08:18:25.0 + @@ -31,9 +31,10 @@ --disabled-password \ --group $MESSAGEUSER +# The preinst might have done this already, or a sysadmin might have +# set up their own dpkg-statoverride. Keep this in sync with the preinst. if ! dpkg-statoverride --list $LAUNCHER /dev/null 21; then -chown root:$MESSAGEUSER $LAUNCHER -chmod 4754 $LAUNCHER +dpkg-statoverride --update --add root $MESSAGEUSER 4754 $LAUNCHER fi # This is idempotent, so it's OK to do every time. The system bus' init diff -Nru dbus-1.9.4/debian/dbus.postrm dbus-1.9.4/debian/dbus.postrm --- dbus-1.9.4/debian/dbus.postrm 2014-11-24 13:58:25.0 + +++ dbus-1.9.4/debian/dbus.postrm 2014-12-15 08:18:25.0 + @@ -7,6 +7,12 @@ rm -f /var/lib/dbus/machine-id rmdir /var/lib/dbus || true + + LAUNCHER=/usr/lib/dbus-1.0/dbus-daemon-launch-helper + + if dpkg-statoverride --list $LAUNCHER /dev/null 21 ; then + dpkg-statoverride --remove $LAUNCHER + fi fi #DEBHELPER# diff -Nru dbus-1.9.4/debian/dbus.preinst dbus-1.9.4/debian/dbus.preinst --- dbus-1.9.4/debian/dbus.preinst 1970-01-01 01:00:00.0 +0100 +++ dbus-1.9.4/debian/dbus.preinst 2014-12-15 08:18:25.0 + @@ -0,0 +1,20 @@ +#!/bin/sh + +set -e + +MESSAGEUSER=messagebus +LAUNCHER=/usr/lib/dbus-1.0/dbus-daemon-launch-helper + +# Avoid having the new $LAUNCHER temporarily go back to +# its permissions and ownership from the .deb (0755 root:root). +# We do this opportunistically - only if $MESSAGEUSER already exists +# (i.e. dbus is installed or has been installed in the past) - to avoid having +# to pre-depend on adduser, and we don't do it if the postinst or +# the sysadmin has already set up a dpkg-statoverride. +# Keep this in sync with the postinst. +if getent group $MESSAGEUSER /dev/null \ +! dpkg-statoverride --list $LAUNCHER /dev/null 21; then +dpkg-statoverride --update --add root $MESSAGEUSER 4754 $LAUNCHER +fi + +#DEBHELPER#
Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping
On Monday 15. December 2014 07.34.07 Jonas Meurer wrote: Thanks for your feedback. Can you provide me with some further information? Yes, I hope so! :-) Which init system do you use? Is this systemd, sysvinit or something completely different? I think it is systemd (no conscious decision from my side): kjetil@owl:~$ ls -l /sbin/init lrwxrwxrwx 1 root root 20 Nov 28 06:55 /sbin/init - /lib/systemd/systemd Did I get you right, that unlocking the encrypted root fs (sda5_crypt) works as expected (i.e. you see a prompt asking for passphrase) while at unlocking the encrypte home fs (owl-home_crypt) no prompt is displayed? Yes, that is correct. The main difference is, that the root fs is unlocked in initramfs, while the home fs is unlocked by a initscript. OK! In case that you use systemd: I know that systemd introduced some internal magic to handle encrypted devices at startup and to my knowledge this is tried before the initscript from my packages are started. So could you try the following: press return a few times when the system boot stops waiting for the passphrase of you encrypted home partition (without prompt) and see, whether it continues afterwards - optionally showing the expected prompt afterwards? H. Not sure about it. After hitting return a couple of times, it scrolls on, and there is another prompt that looks identical. If I continue hitting return, I get to the the maintainance prompt, where I can type the root passwd ot Ctrl+D. Anyway, I don't know if this ends up in a log somewhere? I certainly can't find the phrase passphrase by grepping all logs in /var/log (expect some installer logs). I managed to snap some real screenshots with my mobile phone. Don't know if that could help? Anyway, there's something that I suppose could be related, since /usr is currently mounted just after /home: [ 20.600434] systemd[1]: /usr appears to be on its own filesytem and is not already mounted. This is not a supported setup. Some things will probably break (sometimes even silently) in mysterious ways. Consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken for more information. [ 20.689337] systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory. So, my idea was that /usr didn't need to be encrypted, and since it can also be mounted ro, I figured it could be a good idea to make a separate partition for it. But that seems to have been a Bad Idea, perhaps cryptsetup needs something in /usr that isn't there when /home is mounted? Sorry to bother you with extra debugging work, but unfortunately you seem to be the only one suffering from this bug so far. No problem! One of the reasons why i run testing is of course to help bring out such issues to help you guys fixing it before it goes stable, so this is something I had expected to deal with. :-) I wish I could do more to help, but alas, ENOTIME. Cheers, Kjetil
Bug#773181: rsbackup: unowned files after purge (policy 6.8, 10.8): /etc/rsbackup/local
Package: rsbackup Version: 1.1-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 (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...): 0m31.4s ERROR: FAIL: Package purging left files on system: /etc/rsbackup/ owned by: rsbackup /etc/rsbackup/localnot owned cheers, Andreas rsbackup_1.1-2.log.gz Description: application/gzip
Bug#773174: debdiff
The debdiff
a.
diff -Nru debdelta-0.50+2/debdelta debdelta-0.55/debdelta
--- debdelta-0.50+2/debdelta2012-11-07 11:09:14.0 +0100
+++ debdelta-0.55/debdelta 2014-11-30 18:31:13.0 +0100
@@ -62,6 +62,7 @@
possible values are: xdelta xdelta-bzip xdelta3 bsdiff
-M Mb maximum memory to use (for 'bsdiff' or 'xdelta')
--clean-deltas delete deltas if newer deb is not in archive
+--cache cache parsed version of Packages.bz2 as Packages.debdelta_cache
)
## implement : --searchsearch in the directory of the above debs for older
versions
@@ -119,13 +120,23 @@
-import sys , os , tempfile , string ,getopt , tarfile , shutil , time,
traceback, ConfigParser, subprocess, time, tarfile, stat, hashlib, random
+import sys , os , tempfile , string ,getopt , tarfile , shutil , time,
traceback, ConfigParser, subprocess, time, tarfile, stat, hashlib, random, gzip
+
+try:
+import debian.deb822
+debian_deb822 = debian.deb822
+except ImportError:
+debian_deb822 = None
+
+import cPickle as pickle
from statimport ST_SIZE, ST_MTIME, ST_MODE, S_IMODE, S_IRUSR, S_IWUSR,
S_IXUSR
from os.path import abspath, expanduser
from copyimport copy
-from types import StringType, UnicodeType, FunctionType, TupleType, ListType,
DictType
+from types import FunctionType
+
+string_types = (str, unicode) # change this for python3
def get_termsize():
import termios, fcntl, struct
@@ -208,6 +219,8 @@
DO_PREDICTOR = False
+DO_CACHE = False #cache parsed version of Packages.bz2 as
Packages.debdelta_cache
+
#see README.features
DISABLEABLE_FEATURES=['xz', 'lzma', 'xdelta3-fifo']
DISABLED_FEATURES=[]
@@ -217,7 +230,10 @@
DPKG_MULTIARCH=( 0 == os.system('dpkg --assert-multi-arch 2 /dev/null') )
-if os.path.dirname(sys.argv[0]) == '/usr/lib/apt/methods' :
+
+if __name__ != __main__:
+ action = None
+elif os.path.dirname(sys.argv[0]) == '/usr/lib/apt/methods' :
action = None
else:
action=(os.path.basename(sys.argv[0]))[3:]
@@ -238,7 +254,7 @@
( opts, argv ) = getopt.getopt(sys.argv[1:], 'vkhdM:n:A' ,
('help','info','needsold','dir=','no-act','alt=','old=','delta-algo=',
'max-percent=','deb-policy=','clean-deltas','clean-alt','no-md5','debug','forensicdir=','forensic=',
-'signing-key=', accept-unsigned, gpg-home=,
disable-feature=, test, format=) )
+'signing-key=', accept-unsigned, gpg-home=,
disable-feature=, test, format=,cache) )
except getopt.GetoptError,a:
sys.stderr.write(sys.argv[0] +': '+ str(a)+'\n')
raise SystemExit(3)
@@ -328,6 +344,7 @@
sys.stderr.write(_(Error: output format `%s' is unknown.) % v + '\n')
raise SystemExit(3)
DEB_FORMAT=v
+elif o == '--cache': DO_CACHE=True
else:
sys.stderr.write(_(Error: option `%s' is unknown, try --help) % o +
'\n')
raise SystemExit(3)
@@ -346,6 +363,11 @@
print ' Warning, /proc not mounted, using bogus BOGOMIPS'
BOGOMIPS=3000.0
+SP=subprocess.Popen(['hostname','-f'], shell=False, stdout=subprocess.PIPE)
+HOSTID=hashlib.md5( SP.stdout.read() ).hexdigest()
+SP.wait()
+del SP
+
TMPDIR = ( os.getenv('TMPDIR') or '/tmp' ).rstrip('/')
if KEEP:
@@ -376,7 +398,7 @@
various routines
def my_popen_read(cmd):
- return subprocess.Popen(cmd, shell=True, stdout=subprocess.PIPE).stdout
+ return subprocess.Popen(cmd, shell=True, stdout=subprocess.PIPE,
stdin=open(os.devnull), close_fds=True).stdout
def freespace(w):
assert(os.path.exists(w))
@@ -478,6 +500,88 @@
p.close()
return ar_list
+
+
+class cache_sequence(object):
+ cache_filename=None
+ cache=None
+ exists=None
+ broken=None
+ def __init__(self, filename):
+manages a cache file that store a sequence of python object
+self.cache_filename=os.path.splitext(filename)[0]+'.debdelta_cache'
+self.cache=None
+self.broken=None
+self.exists=os.path.isfile(self.cache_filename) and \
+ os.path.getmtime(filename) os.path.getmtime(self.cache_filename)
+
+ def __iter__(self):
+assert self.exists and not self.cache
+self.cache=gzip.GzipFile(self.cache_filename)
+return self
+
+ def next(self):
+assert self.cache
+try:
+ return pickle.load(self.cache)
+except EOFError:
+ self.cache=None
+ raise StopIteration
+except Exception, e:
+ print 'Cache file is broken (%r), deleting %r' % (e, self.cache_filename)
+ if ACT: os.unlink(self.cache_filename)
+ self.cache=None
+ self.broken=True
+ # do not kill program
+ raise StopIteration
+
+ def __prepare_for_write__(self):
+if not self.cache:
+ if DEBUG: print ' Creating cache file :', self.cache_filename
+ self.cache=gzip.GzipFile(self.cache_filename,'w')
+
+ def close(self):
+if
Bug#773182: php5-pgsql: pg_lo_export does not work with postgesql 9.1
Package: php5-pgsql
Version: 5.4.35-0+deb7u2
Severity: normal
Dear Maintainer,
this is about a problem with the php5-pgsql package.
It works fine and as expectet with postgresql 8.4.
However after upgrading to postgresql 9.1 the pg_lo_export function does
not work.
It returnes TRUE, the file is created, but has zero length and does not
contain the BLOB.
The Problem is neither with postgresql 9.1, nore with libpq, because it
works fine from the pgsql-client.
Something like
SELECT lo_export(coverdat.cover, /tmp/HONK) from coverdat WHERE maj = 77;
works fine!
Calling the funktion from within php5
i.e.
function my_coverdat ($handle, $major, $tmp_name) {
$full_name = '/tmp/HONK';
$my_oid = my_get_oid ($handle, $major);
pg_query($handle, begin);
$result = pg_lo_export($handle, $my_oid, $full_name);
pg_query($handle, commit);
}
does not.
$result is TRUE, but the file HONK is empty!
The same unmodified funktion works fine with postgresql 8.4.
Sorry if this description is kind of unclear, but I'm not a programmer.
Regards Friedhelm
-- System Information:
Debian Release: 7.7
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages php5-pgsql depends on:
ii dpkg 1.16.15
ii libapache2-mod-php5 [phpapi-20100525+lfs] 5.4.35-0+deb7u2
ii libc6 2.13-38+deb7u6
ii libpq5 9.1.14-0+deb7u1
ii php5-common5.4.35-0+deb7u2
ii ucf3.0025+nmu3
php5-pgsql recommends no packages.
php5-pgsql 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#764005: targetcli: Upgrade issues from 2.1-1
Control: severity -1 serious This is a regression, and breaks upgrading systems using targetcli for storage. It's RC. /release-team-hat -- 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#773183: (pre-approval) unblock: systemd with #770504 fixed
Package: release.debian.org
Severity: wishlist
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org
Would you be willing to let the systemd maintainers cherry-pick the
attached into a jessie-targeted version?
It is a trivial change (escalate the level of a log line from info to
warning) and would make it much easier to diagnose and fix circular
dependencies between units. At the moment, systemd logs the first unit
in the cycle and the points at which it tried breaking the cycle,
but the other units involved are not logged unless 'debug' or
a non-default 'systemd.log_level' is present on the kernel command-line.
S
From 14fe721b5f6d8457cc8737fa75f2ed79e7fa534b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= zbys...@in.waw.pl
Date: Sun, 2 Nov 2014 12:10:42 -0500
Subject: [PATCH] Raise level of 'Found dependency...' lines
This way they always show up together with 'Found ordering cycle...'.
Ordering cycles are a serious error and a major pain to debug. If
quiet is enabled, only the first and the last line of output are
shown:
systemd[1]: Found ordering cycle on basic.target/start
systemd[1]: Breaking ordering cycle by deleting job timers.target/start
systemd[1]: Job timers.target/start deleted to break ordering cycle starting with basic.target/start
which isn't particularly enlightening. So just show the whole message
at the same level.
Bug-RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1158206
Bug-Debian: https://bugs.debian.org/770504
Origin: upstream, 218, commit:14fe721b5f6d
---
src/core/transaction.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/core/transaction.c b/src/core/transaction.c
index 488cb86..bbaa6da 100644
--- a/src/core/transaction.c
+++ b/src/core/transaction.c
@@ -376,9 +376,9 @@ static int transaction_verify_order_one(Transaction *tr, Job *j, Job *from, unsi
for (k = from; k; k = ((k-generation == generation k-marker != k) ? k-marker : NULL)) {
/* logging for j not k here here to provide consistent narrative */
-log_info_unit(j-unit-id,
- Found dependency on %s/%s,
- k-unit-id, job_type_to_string(k-type));
+log_warning_unit(j-unit-id,
+ Found dependency on %s/%s,
+ k-unit-id, job_type_to_string(k-type));
if (!delete hashmap_get(tr-jobs, k-unit)
!unit_matters_to_anchor(k-unit, k)) {
--
2.1.3
Bug#770504: systemd: log all members of cyclic dependencies (loops)
On Fri, 05 Dec 2014 at 07:27:35 +0100, Martin Pitt wrote: But still exists in unstable's/testing's 215 version, but important bugs don't qualify for jessie any more as per freeze policy. If someone wants to convince the release team, by all means go ahead, of course -- I'm happy to cherry-pick it into unstable. I've asked the RT. S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773061: aptitude-robot: Hangs with dpkg zombies under some (not yet 100% clear) circumstances
Control: tag -1 - patch
Hi,
while the patch indeed fixes all my current cases, it still doesn't
seem the correct fix:
Axel Beckert wrote:
So the main issue is that aptitude is connected to some terminal, wants
to get rid of some output, but there is nothing which takes the
output.
I'm not yet 100% sure about the correct fix, mostly because I still have
no idea which change made this issue appear.
Besides the manual workaround mentioned above, I've found two other
changes which cause the issue to vanish in the example above:
1) If I remove the yes '' | the issue is gone.
But the yes is necessary for the cases which are not covered by
--force-conf{def,old} e.g. first installs with config files already
present. See commit 169ee18d77a6a80248bdbd1d95cf626638219cb5 and the
changelog entry for 1.2.15-1.
2) If I add a /dev/null behind the aptitude call:
yes '' | aptitude install -y /dev/null
The /dev/null was actually present in aptitude-robot-session
until the yes '' | was added, but it seems that nowadays both are
necessary to avoid the drawbacks of (1) mentioned above.
So I assume that the following patch will fix the issue:
Despite it may not look so, that patch is effectively just a revert of
169ee18d77a6a80248bdbd1d95cf626638219cb5 and hence only replaces one
issue with another, because
→ echo bar /tmp/bar.txt
→ bash -c 'echo foo | cat -v /tmp/bar.txt'
bar
→ dash -c 'echo foo | cat -v /tmp/bar.txt'
bar
i.e. the initial yes '' | in the patch would be ignored.
Need to dig deeper...
Regards, Axel
--
,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772949: RFS: imageio/1.0-1 [ITP] -- Library for reading and writing a wide range of image formats
I have added this package to the debian-science imageanalysis and debian-med imaging-dev tasks. Cheers, - Ghis
Bug#773184: vim-addon-mw-utils: purging removes directories owned by vim-common: /var/lib/vim/addons/, /var/lib/vim/
Package: vim-addon-mw-utils Version: 0.1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package removes directories that were installed by another package. If a directory is used by several packages, all should ship it as part of the package (possibly empty, using $package.dirs to create it), and no package should mkdir/rmdir it in the maintainer scripts as dpkg will take care of this. Do not work around dpkg bugs failing to do the removal properly. From the attached log (scroll to the bottom...): 0m42.5s ERROR: FAIL: After purging files have disappeared: /var/lib/vim/ owned by: vim-common /var/lib/vim/addons/ owned by: vim-common This part of the postrm looks faulty: case $1 in purge) if [ -d /var/lib/vim/addons/autoload/ ]; then rmdir -p --ignore-fail-on-non-empty /var/lib/vim/addons/autoload || : fi ;; * /var/lib/vim/addons/autoload does not sound specific to this package * -p removes parent directories cheers, Andreas vim-addon-mw-utils_0.1-4.log.gz Description: application/gzip
Bug#773154: grub-mkconfig no longer works
On Mon, Dec 15, 2014 at 11:40:54AM +0800, 積丹尼 Dan Jacobson wrote: # grub-mkconfig -o /tmp/g # ls -l /tmp/g ls: cannot access /tmp/g: No such file or directory # grub-mkconfig|wc 0 0 0 sh -x /usr/sbin/grub-mkconfig ... may provide some more useful clues. -- Colin Watson [cjwat...@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#773117: fixed in duplicity 0.6.24-2
Hi Alexander, On Montag, 15. Dezember 2014, Alexander Zangerl wrote: duplicity (0.6.24-2) unstable; urgency=low * applied patch to allow key id formats other than the short 8-char hex form (closes: #773117) wow, that was quick, thanks! Will you try to get this fix into jessie too? cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#773185: qprint: bogus error message on invalid escape sequence
Package: qprint Version: 1.0.dfsg.2-2 Severity: minor $ printf '=' | qprint -d Error: bad equal sign escape = 0x 0x at byte 18446744073709551614 (0xFFFE) of input. Of course the input file was not *that* long. :-) -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages qprint depends on: ii libc6 2.19-13 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773186: qprint: infinite loop on invalid input
Package: qprint Version: 1.0.dfsg.2-2 Usertags: afl $ printf '= ' | qprint -d Error: invalid character 0x in soft line break sequence at byte 1 (0x1) of input. Error: invalid character 0x in soft line break sequence at byte 1 (0x1) of input. Error: invalid character 0x in soft line break sequence at byte 1 (0x1) of input. Error: invalid character 0x in soft line break sequence at byte 1 (0x1) of input. Error: invalid character 0x in soft line break sequence at byte 1 (0x1) of input. [...ad infinitum...] This bug was found using American fuzzy lop: https://packages.debian.org/experimental/afl -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (990, 'unstable'), (500, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages qprint depends on: ii libc6 2.19-13 -- Jakub Wilk -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772342: debian-edu-config: mounting homedirs via NFS doesn't work reliably
Hi Wolfgang, (I guess my question is pretty obvious, but I want to be sure...) On Sonntag, 14. Dezember 2014, Wolfgang Schweer wrote: Added a default (desktop=kde) workstation: NFS mount fails all the time. this is due to the old (=not from sid) network-manager being installed and used? But: NFS mount seems to work reliably with network-manager v. 0.9.10.0-4 (unstable) installed. The network interface is now brought up pretty fast (took up to about 30 seconds before). Maybe now the right sequence of services is given. nice! Thanks for your continous work on this! Totally awesome! cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#771825: release-notes: Update information on non-systemd Jessie upgrades and installations
On Sun, 2014-12-14 at 17:01 +, Brian Potkin wrote: On Thu 04 Dec 2014 at 12:02:27 +0100, Svante Signell wrote: +It is also a good idea to install +systemitem role=package sysvinit-core, sysvint and sysvinit-utils +/systemitem as the first packages when upgrading. What is gained by doing this? If pinning is used sysvinit-core is installed. Are you sure? I'm not. Pinning is a help for apt and aptitude to resolve which packages to install. If sysvinit-core is installed before a dist-upgrade is done why bother with pinning? Other packages might install systemd-sysv by mistake? As was the case with libpam-systemd before the Depends: of libpam-systemd was changed to systemd-shim | systemd-sysv? Pinning helps you to avoid such mistakes. Aren't sysvint and sysvinit-utils already on the system and upgraded without doing anything special with them beforehand? Not sure about this either. Are you? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773187: remmina-plugin-rdp is not installable due to broken dependencies
package: remmina-plugin-rdp version: 1.1.1-2 severity: grave $ sudo apt-get install remmina-plugin-rdp Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: remmina-plugin-rdp : Depends: libfreerdp-client1.1 (= 1.1.0~beta1+git20130629) but it is not going to be installed Depends: libfreerdp-codec1.1 (= 1.1.0~beta1+git20130629) but it is not going to be installed Depends: libfreerdp-core1.1 (= 1.1.0~beta1+git20130629) but it is not going to be installed Depends: libfreerdp-gdi1.1 (= 1.1.0~beta1+git20130629) but it is not going to be installed Depends: libfreerdp-locale1.1 (= 1.1.0~beta1+git20130629) but it is not going to be installed E: Unable to correct problems, you have held broken packages. pravi@savannah:~/Documents/society/Pirate_Movement/diasporaYatra/website$ apt-cache policy remmina-plugin-rdp remmina-plugin-rdp: Installed: (none) Candidate: 1.1.1-2 Version table: 1.1.1-2 0 500 http://kartolo.sby.datautama.net.id/debian/ unstable/main amd64 Packages pravi@savannah:~/Documents/society/Pirate_Movement/diasporaYatra/website$ apt-cache policy libfreerdp-client1.1 libfreerdp-client1.1: Installed: (none) Candidate: 1.1.0~git20140921.1.440916e+dfsg1-2+b1 Version table: 1.1.0~git20140921.1.440916e+dfsg1-2+b1 0 500 http://kartolo.sby.datautama.net.id/debian/ unstable/main amd64 Packages pravi@savannah:~/Documents/society/Pirate_Movement/diasporaYatra/website$ signature.asc Description: OpenPGP digital signature
Bug#773036: Debdiff
libetpan-dev has the same problems as libetpan-dbg and needs to be
fixed, too.
On Sat, 13 Dec 2014 20:26:48 + bastien ROUCARIES
roucaries.bast...@gmail.com wrote:
The following unstested patch should work
not quite ...
diff -Nru libetpan-1.5/debian/changelog libetpan-1.5/debian/changelog
--- libetpan-1.5/debian/changelog 2014-06-11 18:38:34.0 +0200
+++ libetpan-1.5/debian/changelog 2014-12-13 20:13:37.0 +0100
@@ -1,3 +1,9 @@
+libetpan (1.5-2) unstable; urgency=medium
+
+ * Fix symlink to dir problem introduced in 1.4.1-1 (Closes: #773033).
+
+ -- Bastien Roucariès roucaries.bastien+deb...@gmail.com Sat, 13 Dec 2014
20:13:31 +0100
+
libetpan (1.5-1) unstable; urgency=medium
* New upstream release: not really, identical to 1.4.1 but version
diff -Nru libetpan-1.5/debian/control libetpan-1.5/debian/control
--- libetpan-1.5/debian/control 2014-06-11 18:38:34.0 +0200
+++ libetpan-1.5/debian/control 2014-12-13 20:15:38.0 +0100
@@ -57,6 +57,7 @@
Multi-Arch: same
Priority: extra
Depends: libetpan17 (= ${binary:Version}), ${misc:Depends}
+Pre-Depends: dpkg (= 1.17.5)
Pre-Depends: ${misc:Pre-Depends}
if you use .maintscript files, see below
Description: debugging symbols for libetpan
libEtPan! is a mail library. It may be used for low-level mail handling:
network protocols (IMAP/NNTP/POP3/SMTP over TCP/IP with or without SSL),
diff -Nru libetpan-1.5/debian/libetpan-dbg.postinst
libetpan-1.5/debian/libetpan-dbg.postinst
--- libetpan-1.5/debian/libetpan-dbg.postinst 1970-01-01 01:00:00.0
+0100
+++ libetpan-1.5/debian/libetpan-dbg.postinst 2014-12-13 20:24:23.0
+0100
@@ -0,0 +1,8 @@
+#!/bin/sh
+
+set -e
+
+dpkg-maintscript-helper symlink_to_dir \
+ /usr/share/doc/libetpan-dbg/ /usr/share/doc/libetpan15/
1.5-2~
-- $@
+
+#DEBHELPER#
The trailing slashes (at least the first one) make the call useless -
it's not the symlink being tested, but the resolved directory behind it.
For the second it should be sufficient to use the relative path.
This manual code duplication (in 3 maintainer scripts) can be reduced by
using .maintscript files, for libetpan-dbg it could look like this
(completely untested!):
libetpan-dbg.maintscript:
symlink_to_dir /usr/share/doc/libetpan-dbg libetpan15 1.5-2~
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754218: boot hangs forever on LSB job raise network interfaces
Hi *, I ran into the same problem. The boot time has increased almost by one minute since an upgrade recently. $ sudo systemd-analyze blame 1min 1.970s networking.service 1.158s systemd-udev-settle.service 1.145s uml-utilities.service 409ms tor.service ... After having a look at the log files I found out that the DHCP client tries to get an address on eth0. But I'm on WLAN (wlan0) and there isn't even a cable plugged in on eth0. As soon as I comment the eth0 lines in /etc/network/interfaces out, the problem is gone. But I guess that's not a proper solution. My /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp $ systemd sudo systemctl status networking.service networking.service - LSB: Raise network interfaces. Loaded: loaded (/etc/init.d/networking) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf Active: active (running) since Mon 2014-12-15 12:57:02 CET; 20min ago Process: 1951 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS) CGroup: /system.slice/networking.service └─2176 dhclient -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases eth0 $ sudo journalctl _SYSTEMD_UNIT=networking.service -- Logs begin at Mon 2014-12-15 12:55:59 CET, end at Mon 2014-12-15 13:19:21 CET. -- Dec 15 12:56:01 k0ld dhclient[2156]: Internet Systems Consortium DHCP Client 4.3.1 Dec 15 12:56:01 k0ld dhclient[2156]: Copyright 2004-2014 Internet Systems Consortium. Dec 15 12:56:01 k0ld dhclient[2156]: All rights reserved. Dec 15 12:56:01 k0ld dhclient[2156]: For info, please visit https://www.isc.org/software/dhcp/ Dec 15 12:56:01 k0ld dhclient[2156]: Dec 15 12:56:01 k0ld networking[1951]: Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1 Dec 15 12:56:01 k0ld networking[1951]: Copyright 2004-2014 Internet Systems Consortium. Dec 15 12:56:01 k0ld networking[1951]: All rights reserved. Dec 15 12:56:01 k0ld networking[1951]: For info, please visit https://www.isc.org/software/dhcp/ Dec 15 12:56:01 k0ld dhclient[2156]: Listening on LPF/eth0/f0:de:f1:90:28:7f Dec 15 12:56:01 k0ld dhclient[2156]: Sending on LPF/eth0/f0:de:f1:90:28:7f Dec 15 12:56:01 k0ld dhclient[2156]: Sending on Socket/fallback Dec 15 12:56:01 k0ld dhclient[2156]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Dec 15 12:56:01 k0ld networking[1951]: Listening on LPF/eth0/f0:de:f1:90:28:7f Dec 15 12:56:01 k0ld networking[1951]: Sending on LPF/eth0/f0:de:f1:90:28:7f Dec 15 12:56:01 k0ld networking[1951]: Sending on Socket/fallback Dec 15 12:56:01 k0ld networking[1951]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7 Dec 15 12:56:08 k0ld dhclient[2156]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 Dec 15 12:56:08 k0ld networking[1951]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 Dec 15 12:56:21 k0ld dhclient[2156]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 Dec 15 12:56:21 k0ld networking[1951]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 Dec 15 12:56:37 k0ld dhclient[2156]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 Dec 15 12:56:37 k0ld networking[1951]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 Dec 15 12:56:53 k0ld dhclient[2156]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 Dec 15 12:56:53 k0ld networking[1951]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9 Dec 15 12:57:02 k0ld dhclient[2156]: No DHCPOFFERS received. Dec 15 12:57:02 k0ld dhclient[2156]: No working leases in persistent database - sleeping. Dec 15 12:57:02 k0ld networking[1951]: No DHCPOFFERS received. Dec 15 12:57:02 k0ld networking[1951]: No working leases in persistent database - sleeping. Dec 15 12:57:02 k0ld networking[1951]: done. Dec 15 13:00:20 k0ld dhclient[2176]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8 Dec 15 13:00:28 k0ld dhclient[2176]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13 Dec 15 13:00:41 k0ld dhclient[2176]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18 Dec 15 13:00:59 k0ld dhclient[2176]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 Dec 15 13:01:19 k0ld dhclient[2176]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 2 Dec 15 13:01:21 k0ld dhclient[2176]: No DHCPOFFERS received. Dec 15 13:01:21 k0ld dhclient[2176]: No working leases in persistent database - sleeping. Dec 15 13:04:11 k0ld dhclient[2176]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 Dec 15 13:04:17 k0ld dhclient[2176]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 Dec 15 13:04:29 k0ld dhclient[2176]: DHCPDISCOVER on eth0 to
Bug#712206: New upload to mentors
Hi, Thanks Alexandre. I've uploaded a new version to mentors with your suggested changes in d/changelog. Still crossing my fingers that someone will take a look at it and upload it to experimental (if no issues are found). I will file some wishlist bugs to all packages that depend on pyusb to make sure that they are compatible with pyusb1.0. Thanks Regards Ruben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773188: enhanceio-dkms: the enhanceio module fails to build on Kernel 3.18
Package: enhanceio-dkms
Version: 0+git20130620-4
Severity: important
Tags: patch
Dear Maintainer,
The enhanceio kernel module from this package fails to build on kernels
starting from version 3.18. The reason is the removal of the deprecated
function smp_mb__after_clear_bit. The proper fix is to replace it with
smp_mb__after_atomic. I include a patch for the enhanceio package which
implements these changes. I also published them on my GitHub fork of
enhanceio [1]. There is still an outstanding pull request to merge these
changes and those fixing 3.17 into the upstream repository [2].
Thanks for maintaining this package,
Philipp
[1] https://github.com/tukss/EnhanceIO
[2] https://github.com/stec-inc/EnhanceIO/pull/84
-- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.17.0-trunk-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: systemd (via /run/systemd/system)
Versions of packages enhanceio-dkms depends on:
ii dkms 2.2.0.3-2
Versions of packages enhanceio-dkms recommends:
ii enhanceio 0+git20130620-4
ii libgcc-4.8-dev 4.8.3-18
enhanceio-dkms suggests no packages.
-- no debconf information
diff -Nru enhanceio-0+git20130620/debian/changelog
enhanceio-0+git20130620/debian/changelog
--- enhanceio-0+git20130620/debian/changelog2014-11-20 05:03:15.0
+0100
+++ enhanceio-0+git20130620/debian/changelog2014-12-15 12:38:50.0
+0100
@@ -1,3 +1,10 @@
+enhanceio (0+git20130620-4.1~edelmann1) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * New patch for compatibility with Linux 3.18.
+
+ -- Philipp Edelmann edelm...@fs.tum.de Mon, 15 Dec 2014 12:37:56 +0100
+
enhanceio (0+git20130620-4) experimental; urgency=medium
[ Philipp Edelmann edelm...@fs.tum.de ]
diff -Nru enhanceio-0+git20130620/debian/patches/kernel-3.18.patch
enhanceio-0+git20130620/debian/patches/kernel-3.18.patch
--- enhanceio-0+git20130620/debian/patches/kernel-3.18.patch1970-01-01
01:00:00.0 +0100
+++ enhanceio-0+git20130620/debian/patches/kernel-3.18.patch2014-12-15
12:36:54.0 +0100
@@ -0,0 +1,96 @@
+--- a/Driver/enhanceio/eio_conf.c
b/Driver/enhanceio/eio_conf.c
+@@ -101,6 +101,10 @@
+ return 0;
+ }
+
++#if (LINUX_VERSION_CODE KERNEL_VERSION(3,15,0))
++#define smp_mb__after_atomic smp_mb__after_clear_bit
++#endif
++
+ /*
+ * Check if the System RAM threshold requested memory, don't care
+ * if threshold is set to 0. Return value is 0 for fail and 1 for success.
+@@ -1853,7 +1857,7 @@
+ dmc-next_cache = cache_list_head;
+ cache_list_head = dmc;
+ clear_bit(EIO_UPDATE_LIST, (void *)eio_control-synch_flags);
+- smp_mb__after_clear_bit();
++ smp_mb__after_atomic();
+ wake_up_bit((void *)eio_control-synch_flags, EIO_UPDATE_LIST);
+
+ prev_set = -1;
+@@ -1918,7 +1922,7 @@
+ nodepp = ((*nodepp)-next_cache);
+ }
+ clear_bit(EIO_UPDATE_LIST, (void *)eio_control-synch_flags);
+- smp_mb__after_clear_bit();
++ smp_mb__after_atomic();
+ wake_up_bit((void *)eio_control-synch_flags, EIO_UPDATE_LIST);
+ bad5:
+ eio_kcached_client_destroy(dmc);
+@@ -2072,7 +2076,7 @@
+ nodepp = ((*nodepp)-next_cache);
+ }
+ clear_bit(EIO_UPDATE_LIST, eio_control-synch_flags);
+- smp_mb__after_clear_bit();
++ smp_mb__after_atomic();
+ wake_up_bit((void *)eio_control-synch_flags, EIO_UPDATE_LIST);
+
+ out:
+@@ -2397,7 +2401,7 @@
+ TASK_UNINTERRUPTIBLE);
+ if (eio_reboot_notified == EIO_REBOOT_HANDLING_DONE) {
+ clear_bit(EIO_HANDLE_REBOOT, (void *)eio_control-synch_flags);
+- smp_mb__after_clear_bit();
++ smp_mb__after_atomic();
+ wake_up_bit((void *)eio_control-synch_flags,
+ EIO_HANDLE_REBOOT);
+ return NOTIFY_DONE;
+@@ -2425,12 +2429,12 @@
+ eio_md_store(dmc);
+ }
+ clear_bit(EIO_UPDATE_LIST, (void *)eio_control-synch_flags);
+- smp_mb__after_clear_bit();
++ smp_mb__after_atomic();
+ wake_up_bit((void *)eio_control-synch_flags, EIO_UPDATE_LIST);
+
+ eio_reboot_notified = EIO_REBOOT_HANDLING_DONE;
+ clear_bit(EIO_HANDLE_REBOOT, (void *)eio_control-synch_flags);
+- smp_mb__after_clear_bit();
++ smp_mb__after_atomic();
+ wake_up_bit((void *)eio_control-synch_flags, EIO_HANDLE_REBOOT);
+ return NOTIFY_DONE;
+ }
+--- a/Driver/enhanceio/eio_ttc.c
b/Driver/enhanceio/eio_ttc.c
+@@ -36,6 +36,11 @@
+ #define wait_on_bit_lock_action wait_on_bit_lock
+ #endif
+
++#if (LINUX_VERSION_CODE KERNEL_VERSION(3,15,0))
++#define smp_mb__after_atomic smp_mb__after_clear_bit
++#endif
++
++
+ static struct rw_semaphore
Bug#769556: libonig2-dbg: package fails to upgrade properly from wheezy
Followup-For: Bug #769556
Control: found -1 5.9.5-3.1
The previous fixes do not work since the dpkg-maintscript-helper call
gets the wrong version. Also putting dpkg-maintscript-helper in
case $1 in ...) blocks is not the recommended usage ... and causes a lot
of manual code duplication ...
Since the package already uses debhelper 9, this can be greatly
simplified by using .maintscript files, it should probably look like
this (completely untested) for a maintainer upload:
libonig2-dbg.maintscript:
symlink_to_dir /usr/share/doc/libonig2-dbg /usr/share/doc/libonig2 5.9.5-4~
(for a NMU use version 5.9.5-3.2~)
The manually added maintainer scripts can be deleted again and in
debian/control the explicit versioned pre-dependency on dpkg should be
replaced by ${misc:Pre-Depends}
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768189: please check my debconf setup
So I setup the debconf question, and everything seems to be in place, but I can't get it to actually show me the question when it installs. Can someone check it out and see what I missed? This is the first time I've ever done a debconf question. Its in the package git: http://anonscm.debian.org/cgit/collab-maint/macchanger.git .hc signature.asc Description: OpenPGP digital signature
Bug#773187: bin rebuild is not sufficient
a binary only rebuild won't fix it as it can't satisfy build-deps as well. pravi@savannah:~/forge/debian/remmina-1.1.1$ sudo apt-get build-dep remmina-plugin-rdp [sudo] password for pravi: Reading package lists... Done Building dependency tree Reading state information... Done Picking 'remmina' as source package instead of 'remmina-plugin-rdp' The following packages have unmet dependencies: libfreerdp-dev : Depends: libwinpr-dev (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-cache1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-client1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-codec1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-common1.1.0 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-core1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-crypto1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-gdi1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-locale1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-primitives1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-rail1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libfreerdp-utils1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed Depends: libxfreerdp-client1.1 (= 1.1.0~git20140921.1.440916e+dfsg1-2+b1) but it is not going to be installed E: Build-dependencies for remmina-plugin-rdp could not be satisfied. signature.asc Description: OpenPGP digital signature
Bug#773189: libvirt-daemon: Haswell microcode update breaks CPU detection
Package: libvirt-daemon Version: 1.2.9-6 Severity: important Dear Maintainer, The intel-microcode 3.20140913.1 update disables TSX-NI (transactional memory instructions). When a server running libvirt is rebooted with this update, libvirt no longer considers the machine to have a Haswell CPU: dietrich ~ # virsh capabilities | grep -A1 'archx86_64' archx86_64/arch modelSandyBridge/model This causes a problem as any VMs that require a Haswell CPU, which would have worked previously, now fail to start altogether. Commenting out the two cpuinfo flags relevant to TSX-NI from /usr/share/libvirt/cpu_map.xml fixes this for me: --- cpu_map.xml.orig2014-11-24 11:47:47.0 + +++ cpu_map.xml 2014-12-15 12:33:21.485278484 + @@ -507,13 +507,13 @@ feature name='movbe'/ feature name='fsgsbase'/ feature name='bmi1'/ - feature name='hle'/ + !--feature name='hle'/-- feature name='avx2'/ feature name='smep'/ feature name='bmi2'/ feature name='erms'/ feature name='invpcid'/ - feature name='rtm'/ + !--feature name='rtm'/-- /model model name='Broadwell' HTH, Chris -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (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 libvirt-daemon depends on: ii libapparmor12.9.0-2 ii libaudit1 1:2.4-1+b1 ii libavahi-client30.6.31-4+b2 ii libavahi-common30.6.31-4+b2 ii libblkid1 2.25.2-3 ii libc6 2.19-13 ii libcap-ng0 0.7.4-2 ii libdbus-1-3 1.8.12-1 ii libdevmapper1.02.1 2:1.02.90-2 ii libfuse22.9.3-15+b1 ii libgnutls-deb0-28 3.3.8-5 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-6 ii libpcap0.8 1.6.2-2 ii libpciaccess0 0.13.2-3+b1 ii librados2 0.80.7-1 ii librbd1 0.80.7-1 ii libsasl2-2 2.1.26.dfsg1-12 ii libselinux1 2.3-2 ii libssh2-1 1.4.3-4 ii libsystemd0 215-7 ii libudev1215-7 ii libvirt01.2.9-6 ii libxen-4.4 4.4.1-5 ii libxenstore3.0 4.4.1-5 ii libxml2 2.9.1+dfsg1-4 ii libyajl22.1.0-2 Versions of packages libvirt-daemon recommends: ii libxml2-utils2.9.1+dfsg1-4 ii netcat-openbsd 1.105-7 pn qemu-kvm | qemu none Versions of packages libvirt-daemon suggests: ii libvirt-daemon-system 1.2.9-6 -- 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#742048: systemd-remount-fs.service fails for split-usr
Having the same issue I've inspected systemd target dependency graph, it looks like this (in the start order omitting redundant 'hop' dependencies): systemd-remount-fs.service - local-fs-pre.target - usr.mount - local-fs.target, therefore I consider this is a system configuration bug. laptop-mode-tools is not installed, no manual configuration involved. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773190: rails-assets gem should be fetched from rails-assets.org
package: rubygems version: 1:2.1.0.1 severity: wishlist since all rails-assets gems are available from rails-assets.org, gem fetch or gem install or gem list -r should fetch it from rails-assets.org signature.asc Description: OpenPGP digital signature
Bug#773191: python-ogg-dbg: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE
Package: python-ogg-dbg
Version: 1.3+repack-6
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:
wheezy - jessie
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...):
2m15.8s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/python-ogg-dbg/changelog.Debian.gz (python-ogg-dbg) !=
/usr/share/doc/python-ogg/changelog.Debian.gz (python-ogg)
/usr/share/doc/python-ogg-dbg/changelog.gz (python-ogg-dbg) !=
/usr/share/doc/python-ogg/changelog.gz (python-ogg)
/usr/share/doc/python-ogg-dbg/copyright (python-ogg-dbg) !=
/usr/share/doc/python-ogg/copyright (python-ogg)
cheers,
Andreas
python-ogg-dbg_1.3+repack-6.log.gz
Description: application/gzip
Bug#773192: disable DSA key generation by default
Package: openssh-server Version: all During installation (or maybe the first startup, i'm not sure), the openssh-server generates 1024bit DSA keys. This key length is no longer considered secure and therefore should be disabled, or created with a longer key length. However, not all SSH implementations support DSA keys longer than 1024 bits, so i suggest disabling DSA key generation. According to NIST, 1024 bit keys are disallowed after 2013, see: http://csrc.nist.gov/publications/nistpubs/800-131A/sp800-131A.pdf This bug is somehow related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481133 , but it's not a duplicate. Thank you, Stefan Safar
Bug#772342: debian-edu-config: mounting homedirs via NFS doesn't work reliably
On Mon, Dec 15, 2014 at 01:03:50PM +0100, Holger Levsen wrote: this is due to the old (=not from sid) network-manager being installed and used? Yes, atm version 0.9.10.0-3; network-manager v. 0.9.10.0-4 was the only package installed from unstable to make NFS mount work. Wolfgang signature.asc Description: Digital signature
Bug#772870: fusionforge-plugin-mediawiki: Trigger cycle causes dpkg to fail processing
Hi, On Sun, Dec 14, 2014 at 02:28:26PM +0100, Guillem Jover wrote: On Fri, 2014-12-12 at 17:35:36 +0100, Thorsten Glaser wrote: So, with -noawait, the triggers just run later, but the dependency is satisfied early, right? Think of it as an asynchronouse notification that something changed in another package vs a notification that the triggering package needs something to be processed to be able to declare itself as configured. In case of -noawait, the triggering package never gets placed in a triggers-awaited state, so it can always satisfy dependencies when it has been configured. So far my tests show that 'apt-get upgrade' doesn't start the noawait triggers. The fusionforge-plugin-mediawiki is marked 'triggers-pending' but apparently the user has to do something more manually, which is not satisfying. Any suggestion? On Fri, 2014-12-12 at 17:40:43 +0100, b...@debian.org wrote: There's one point I'd like to clarify: how comes we never had any issues with this? E.g. I don't see any warning here: http://buildbot.fusionforge.org/job/fusionforge-53-functests-deb/os=debian7/33/consoleFull dpkg was buggy and never performed dependency satisfiability checks when trying to process triggers. This was fixed in dpkg 1.17.17. Well we didn't have any issue here either :/ http://buildbot.fusionforge.org/job/fusionforge-53-functests-deb/os=debian8/33/consoleFull However I can reproduce the problem by upgrading/downgrading mediawiki. How exactly did you trigger this bug? ;) -- Sylvain -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773187: remmina-plugin-rdp is not installable due to broken dependencies
tags 773187 + moreinfo unreproducible thanks Hi! 2014-12-15 13:13 GMT+01:00 Pirate Praveen prav...@debian.org: package: remmina-plugin-rdp version: 1.1.1-2 severity: grave $ sudo apt-get install remmina-plugin-rdp [...] The following packages have unmet dependencies: [...] I just tried to install remmina-plugin-rdp in a clean sid chroot, and it seems everything is working fine. Is your apt mirror not up-to-date? Cheers, Luca -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773193: Trackpoint not working on IBM Thinkpad T42
Package: linux-image-3.16.0-4-586 Version: 3.16.7-2 Dear Maintainers, Using an IBM Thinkpad T42 with Jessie, the trackpoint does not seem to be fully detected, and so I can't use it : I can see it with dmidecode -t 21 : # dmidecode 2.12 SMBIOS version fixup (2.33 - 2.3). SMBIOS 2.3 present. Handle 0x0033, DMI type 21, 7 bytes Built-in Pointing Device Type: Track Point Interface: PS/2 Buttons: 3 Handle 0x0034, DMI type 21, 7 bytes Built-in Pointing Device Type: Touch Pad Interface: PS/2 Buttons: 0 But it is not listed in /proc/bus/input/devices : I: Bus=0011 Vendor=0001 Product=0001 Version=ab54 N: Name=AT Translated Set 2 keyboard P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input0 U: Uniq= H: Handlers=sysrq kbd event0 B: PROP=0 B: EV=120013 B: KEY=4 200 3803078 f800d001 fedf ffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0005 Version= N: Name=Lid Switch P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input2 U: Uniq= H: Handlers=event1 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name=Sleep Button P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name=Power Button P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor=1014 Product=5054 Version=4101 N: Name=ThinkPad Extra Buttons P: Phys=thinkpad_acpi/input0 S: Sysfs=/devices/platform/thinkpad_acpi/input/input5 U: Uniq= H: Handlers=kbd rfkill event4 B: PROP=0 B: EV=13 B: KEY=1884 0 0 10 0 0 0 1501b 2004 0 1104000 e 0 0 0 B: MSC=10 I: Bus=0019 Vendor= Product=0006 Version= N: Name=Video Bus P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:02/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 0 0 0 0 I: Bus=0011 Vendor=0002 Product=0007 Version=2cb1 N: Name=SynPS/2 Synaptics TouchPad P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input7 U: Uniq= H: Handlers=mouse0 event6 B: PROP=1 B: EV=b B: KEY=6420 0 3 0 0 0 0 0 0 0 0 B: ABS=1103 Maybe there is something I should change to activate it, but I don't know what : I already tried to enable and to disable it in the BIOS (as suggested on some forums), with no result. I am almost sure it was working perfectly with previous versions of the kernel : I will try and let you know. Thanks for your time and work, YvanM [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 3.16.0-4-586 (debian-ker...@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-13) ) #1 Debian 3.16.7-2 (2014-11-06) [0.00] Disabled fast string operations [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009efff] usable [0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved [0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x2ff5] usable [0.00] BIOS-e820: [mem 0x2ff6-0x2ff76fff] ACPI data [0.00] BIOS-e820: [mem 0x2ff77000-0x2ff78fff] ACPI NVS [0.00] BIOS-e820: [mem 0x2ff8-0x2fff] reserved [0.00] BIOS-e820: [mem 0xff80-0x] reserved [0.00] Notice: NX (Execute Disable) protection missing in CPU! [0.00] SMBIOS 2.3 present. [0.00] DMI: IBM 23744WG/23744WG, BIOS 1RETDRWW (3.23 ) 06/18/2007 [0.00] e820: update [mem 0x-0x0fff] usable == reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] e820: last_pfn = 0x2ff60 max_arch_pfn = 0x10 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-C write-protect [0.00] D-DBFFF uncachable [0.00] DC000-D write-back [0.00] E-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask FE000 write-back [0.00] 1 base 02000 mask FF000 write-back [0.00] 2 base 02FF8 mask 8 uncachable [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] PAT not supported by CPU. [0.00] initial memory mapped: [mem
Bug#772342: debian-edu-config: mounting homedirs via NFS doesn't work reliably
Hi Wolfgang, thanks for confirming! On Montag, 15. Dezember 2014, Wolfgang Schweer wrote: Yes, atm version 0.9.10.0-3; network-manager v. 0.9.10.0-4 was the only package installed from unstable to make NFS mount work. ok, cool, 0.9.10.0-4 should migrate to jessie in four days: https://packages.qa.debian.org/n/network-manager.html says Too young, only 1 of 5 days old. Ignoring block request by freeze, due to unblock request by nthykier. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#772628: Patch for kmod package to support compression
Hi, On Mon, Dec 15, 2014 at 02:45:21AM +0100, Marco d'Itri wrote: On Dec 15, Tomas Janousek t...@nomi.cz wrote: I'm attaching a patch for the Debian package which enables building with xz/zlib. Why enable support for both? Because we don't know what the users will use. I used xz as I don't mind waiting a bit when doing make -j4 modules_install and want to save as much space as possible, but I can very well imagine that gzip would be a good compromise between speed and compression ratio for many people. -- Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742473: lightyears sound patch acceptance
Siegfried, Could you take another look at this when you get a chance? I don't know much about debian packaging/freeze, but it would be great if this fix could get into Jessie. Without it, the packaged version of the game is nearly unplayable. -Allan
Bug#773194: base: Fails to add Facebook Online Account - Your popup is too small to display this page
Package: base Severity: important Dear Maintainer, It was unable to add Facebook account to Online Account's in System Setings - Online Account's Add - Facebook: After login got this error message: Your popup is too small to display this page Please enlarge it to proceed But window size is fixed and can not be enlarged. Thanks -- System Information: Debian Release: Kali Linux 1.0.9 Architecture: i386 (i686) Kernel: Linux 3.14-kali1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768189: RC and fixed
Control: severity 768189 grave I'm bumping the severity to 'grave' since this new behavior seemed to shock a few users ;). Also, because I just fixed it with a debconf question. As for expectations, Debian runs more than just daemons automatically. You can see some other examples of things that run automatically in /etc/network/if-*.d. For example, 'wireless-tools', 'bridge-utils', etc. signature.asc Description: OpenPGP digital signature
Bug#770449: ITP, RFS for Caml Crush package
On 12/12/2014 17:53, Stéphane Glondu wrote: Le 02/12/2014 13:34, Thomas Calderon a écrit : 1. I have split the debian-related files from the master branch. I will now use upstream and debian branches instead. Therefore, release tarballs will not contain this directory. $ tar tf ../caml-crush_1.0.4.orig.tar.gz|grep debian caml-crush-1.0.4/debian/ caml-crush-1.0.4/debian/caml-crush-clients.install caml-crush-1.0.4/debian/caml-crush-clients.lintian-overrides caml-crush-1.0.4/debian/caml-crush-server.init [...] Is that intentional? 2. You were right, there was no valid reason to have the SOs directly in /usr/lib, I moved them to /usr/lib/triplet/caml-crush. This has indeed the positive effect of suppressing the lintian issues. 3. I switched to the Debian-pkcs11proxyd system account and group. 4. Since we rely on OCaml native compilers, I switched from the ocaml-nox build dependency to ocaml-native-compilers and have Architecture: any instead. 5. Since Caml Crush does not (yet) support using bytecode-only architecture, we rely on ocaml-native-compilers to restrict the supported architectures. Fine. I have uploaded a new version on mentors.debian.net Also, could you make a single changelog entry for the initial release? Cheers, Hi Stéphane, I've fixed the remaining debian directory in the upstream archive (issue related to a misplaced git tag) and I have issued a single Changelog for the Initial release. The latest version is available on mentors.debian.net Regards, -- Cordialement, Thomas Calderon Laboratoire architectures matérielles et logicielles Sous-direction expertise ANSSI Tél: 01 71 75 88 55 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698386: cmake --find-package ignores multi-arch dir
Just in case this would explain: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698386#117 There is currently an issue with cmake and multi-arch dirs in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768877#23 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773140: unblock: rabbitmq-server/3.3.5-1.1
Control: tags -1 + moreinfo On 2014-12-14 23:07, Matt Kraai wrote: Is it OK to uploade rabbitmq-server/3.3.5-1.1 to testing-proposed-updates? 773134 reports that it is insecure because it trusts the X-Forwarded-For HTTP header. The following patches were applied upstream to fix this: * http://hg.rabbitmq.com/rabbitmq-management/rev/c3c41177a11a * http://hg.rabbitmq.com/rabbitmq-management/rev/35e916df027d rabbitmq-server/3.4.1-1 is already in unstable. That new upstream version was uploaded at urgency=high the day before the freeze, with no explanation other than new upstream release. Given that 3.4.0 had been out for a fortnight by that point, it looks very much like trying to game the freeze. :-( rabbitmq-server maintainers, are there any other RC bugs that you're planning to file on the package? Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773195: unblock macchanger/1.7.0-4
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
unblock macchanger/1.7.0-4
The new behavior of this package to automatically enable itself surprised some
users, and broke one's custom wifi setup. So this update adds a debconf
question to prompt the user whether to run it automatically or not.
$ debdiff /tmp/macchanger_1.7.0-3.2.dsc macchanger_1.7.0-4.dsc
diff -Nru macchanger-1.7.0/debian/changelog macchanger-1.7.0/debian/changelog
--- macchanger-1.7.0/debian/changelog 2014-11-29 13:50:42.0 +0100
+++ macchanger-1.7.0/debian/changelog 2014-12-15 14:11:01.0 +0100
@@ -1,3 +1,9 @@
+macchanger (1.7.0-4) unstable; urgency=low
+
+ * add debconf option to prompt whether to automatically run (Closes: #768189)
+
+ -- Hans-Christoph Steiner h...@eds.org Mon, 15 Dec 2014 12:07:44 +0100
+
macchanger (1.7.0-3.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru macchanger-1.7.0/debian/config macchanger-1.7.0/debian/config
--- macchanger-1.7.0/debian/config 1970-01-01 01:00:00.0 +0100
+++ macchanger-1.7.0/debian/config 2014-12-15 14:07:56.0 +0100
@@ -0,0 +1,23 @@
+#!/bin/sh -e
+
+# Source debconf library.
+. /usr/share/debconf/confmodule
+
+
+if [ -f /etc/default/macchanger ]; then
+ENABLE_ON_POST_UP_DOWN=false
+. /etc/default/macchanger
+
+if [ $ENABLE_ON_POST_UP_DOWN = true ]; then
+db_set macchanger/automatically_run true
+else
+db_set macchanger/automatically_run false
+fi
+fi
+
+db_input high macchanger/automatically_run || true
+db_go
+
+#DEBHELPER#
+
+exit 0
diff -Nru macchanger-1.7.0/debian/default macchanger-1.7.0/debian/default
--- macchanger-1.7.0/debian/default 1970-01-01 01:00:00.0 +0100
+++ macchanger-1.7.0/debian/default 2014-12-15 14:11:01.0 +0100
@@ -0,0 +1,11 @@
+# before bringing up any network interface, run macchanger. Careful, this is
+# not guaranteed to prevent leaking your real MAC address before the new one
+# gets assigned!
+#
+ENABLE_ON_POST_UP_DOWN=false
+
+
+# by default, macchanger runs on all network interfaces but loopback (lo). If
+# you only want it to run on specific network interfaces, set them here:
+#
+#ENABLE_INTERFACES=wlan0
diff -Nru macchanger-1.7.0/debian/if-pre-up.d/macchanger
macchanger-1.7.0/debian/if-pre-up.d/macchanger
--- macchanger-1.7.0/debian/if-pre-up.d/macchanger 2014-11-29
13:50:42.0 +0100
+++ macchanger-1.7.0/debian/if-pre-up.d/macchanger 1970-01-01
01:00:00.0 +0100
@@ -1,32 +0,0 @@
-#!/bin/sh
-#
-# randomize MAC address before connecting to wifi or ethernet
-#
-# This script should always be run in if-pre-up.d, but unfortunately
-# NetworkManager does not run if-pre-up.d scripts before it sets up a network
-# connection (https://bugzilla.gnome.org/show_bug.cgi?id=387832).
-# if-post-down.d scripts are run, so there is a symlink to this script
-# there. That means when running network config from the terminal, macchanger
-# will be run twice, but it'll only be run in if-post-down.d when using
-# NetworkManager.
-
-package=macchanger
-
-. /etc/default/${package}
-
-LOGFILE=/var/log/${package}.log
-
-if [ $ENABLE_ON_POST_DOWN != yes ]; then
-echo disabled in /etc/default/${package} $LOGFILE
-exit
-fi
-
-echo IFACE = $IFACE $LOGFILE
-
-# quit if we're called for the loopback
-if [ $IFACE = lo ]; then
-echo ignoring loopback $LOGFILE
- exit 0
-fi
-
-/usr/bin/${package} -e $IFACE $LOGFILE 21
diff -Nru macchanger-1.7.0/debian/ifupdown.sh
macchanger-1.7.0/debian/ifupdown.sh
--- macchanger-1.7.0/debian/ifupdown.sh 1970-01-01 01:00:00.0 +0100
+++ macchanger-1.7.0/debian/ifupdown.sh 2014-12-15 14:07:56.0 +0100
@@ -0,0 +1,32 @@
+#!/bin/sh
+#
+# randomize MAC address before connecting to wifi or ethernet
+#
+# This script should always be run in if-pre-up.d, but unfortunately
+# NetworkManager does not run if-pre-up.d scripts before it sets up a network
+# connection (https://bugzilla.gnome.org/show_bug.cgi?id=387832).
+# if-post-down.d scripts are run, so there is a symlink to this script
+# there. That means when running network config from the terminal, macchanger
+# will be run twice, but it'll only be run in if-post-down.d when using
+# NetworkManager.
+
+package=macchanger
+
+. /etc/default/${package}
+
+LOGFILE=/var/log/${package}.log
+
+if [ $ENABLE_ON_POST_UP_DOWN != true ]; then
+echo disabled in /etc/default/${package} $LOGFILE
+exit
+fi
+
+echo IFACE = $IFACE $LOGFILE
+
+# quit if we're called for the loopback
+if [ $IFACE = lo ]; then
+echo ignoring loopback $LOGFILE
+exit 0
+fi
+
+/usr/bin/${package} -e $IFACE $LOGFILE 21
diff -Nru macchanger-1.7.0/debian/install macchanger-1.7.0/debian/install
--- macchanger-1.7.0/debian/install 2014-11-29 13:50:42.0 +0100
+++ macchanger-1.7.0/debian/install 2014-12-15 11:44:29.0 +0100
@@ -1,2 +1,2 @@
-debian/if-pre-up.d/macchanger
Bug#748055: (no subject)
I have the same problem here on wheezy and jessie with wheezy debian-goodies 0.61 # checkrestart -v Found 1 processes using old versions of upgraded files (1 distinct program) Process /usr/sbin/mysqld (PID: 3017) List of deleted files in use: Running:['dpkg-query', '--search', '/usr/sbin/mysqld'] Reading line: mysql-server-core-5.5: /usr/sbin/mysqld (1 distinct packages) These processes do not seem to have an associated init script to restart them: mysql-server-core-5.5: 3017/usr/sbin/mysqld with jessie debian-goodies 0.63 # checkrestart -v Found 1 processes using old versions of upgraded files (1 distinct program) Process /usr/sbin/mysqld (PID: 22038) List of deleted files in use: /[aio] /[aio] ... /[aio] /[aio] Running:['dpkg-query', '--search', '/usr/sbin/mysqld'] Reading line: mysql-server-core-5.5: /usr/sbin/mysqld (1 distinct packages) These processes do not seem to have an associated init script to restart them: mysql-server-core-5.5: 22038/usr/sbin/mysqld If I restart mysql or reboot the server the problem still exist kind regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772440: Bug #772440: linux-image-3.16.0-4-amd64: Built-in display dimmed black if external monitor is plugged in
control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=87286
control: tags -1 patch
control: tags -1 jessie
I filed a bug for the backlight control issue on freedesktop.org.
There are 2 possible solutions:
1.) Disable native backlight and return to use acpi, as it was in 3.14.
2.) Fix intel_backlight
I don't know which one the upstream solution will be, but I guess for
Jessie native backlight should just be disabled (which fixes both the
inital brightness level and the control issue). See attached patch.
The same is already done for other product classes in 3.16.7-ckt2-1. And
looking at the bugreports at freedesktop even more will be added to
disable native backlight in the next time.
So probably just wait for now to see if the patch gets applied and
backported upstream.
Greets
jre
commit ea05c0cd09531bc9834cd176f17d9b7da24cae5f
Author: jre-winesim jre.wine...@gmail.com
Date: Mon Dec 15 14:17:13 2014 +0100
disable native backlight
diff --git a/drivers/acpi/video.c b/drivers/acpi/video.c
index f1e3496..24d7444 100644
--- a/drivers/acpi/video.c
+++ b/drivers/acpi/video.c
@@ -694,6 +694,15 @@ static struct dmi_system_id video_dmi_table[] __initdata = {
DMI_MATCH(DMI_PRODUCT_NAME, HP ENVY 15 Notebook PC),
},
},
+ {
+ /* https://bugs.freedesktop.org/show_bug.cgi?id=87286 */
+ .callback = video_disable_native_backlight,
+ .ident = SAMSUNG 900X3C/900X3D/900X3E/900X4C/900X4D,
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, SAMSUNG ELECTRONICS CO., LTD.),
+ DMI_MATCH(DMI_PRODUCT_NAME, 900X3C/900X3D/900X3E/900X4C/900X4D),
+ },
+ },
{}
};
Bug#750728: libsane: error opening hp printer 3050: invalid argument
reassign 750728 libsane/1.0.24-1.1+b1 retitle 750728 libsane: error opening hp printer 3050: invalid argument tags 750728 + moreinfo thanks Hello Thomas, I think that your bug is in sane-backends. I reassign to libsane. Your are using hpaio as backend? CU Jörg -- New: GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D GPG key (long) : 09F89F3C8CA1D25D GPG Key: 8CA1D25D CAcert Key S/N : 0E:D4:56 Old (will be revoked after 2014-12-31): pgp Fingerprint: 7D13 3C60 0A10 DBE1 51F8 EBCB 422B 44B0 BE58 1B6E pgp Key: BE581B6E Jörg Frings-Fürst D-54526 Niederkail Threema: SYR8SJXB IRC: j_...@freenode.net j_...@oftc.net signature.asc Description: This is a digitally signed message part
Bug#773196: git-bzr: leaves alternatives after purge: /etc/alternatives/git-remote-bzr
Package: git-bzr Version: 2:0.2+20140705-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: 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. This was observed on the upgrade path wheezy-backports - jessie. Since this seems to be an obsolete alternative, it should be cleaned up in the postinst, probably in the git-remote-bzr package. 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...): 1m49.5s INFO: Warning: Package purging left files on system: /etc/alternatives/git-remote-bzr - /usr/lib/git-core/git-remote-bzr--git not owned /etc/alternatives/git-remote-bzr.1.gz - /usr/share/man/man1/git-remote-bzr--git.1.gz not owned cheers, Andreas git-bzr_2:0.2+20140705-1.log.gz Description: application/gzip
Bug#768189: Bug#773195: unblock macchanger/1.7.0-4
Hi, adding debian-l10n-engl...@lists.debian.org to cc: to get feedback and advice. On Montag, 15. Dezember 2014, Hans-Christoph Steiner wrote: diff -Nru macchanger-1.7.0/debian/po/templates.pot macchanger-1.7.0/debian/po/templates.pot --- macchanger-1.7.0/debian/po/templates.pot 1970-01-01 01:00:00.0 +0100 +++ macchanger-1.7.0/debian/po/templates.pot2014-12-15 [...] +msgid Would you like your MAC automatically changed? [...]+ This then gives you a new MAC every time you plug... I believe addressing users directly like this is frowned upon and not recommended, (at least it's not done in d-i, TTBOMK). AFAIK it's better to use wordings like Should the MAC address automatically get changed? instead of the first msgid above. cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#773197: origami package replaced by a completely different package
Package: origami Version: 1.2.7-1 Severity: serious https://packages.debian.org/jessie/origami and https://packages.debian.org/sid/origami are totally different. I assume this is a slip-up by the uploader of the sid version, which should get a new name. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772793: cpio: CVE-2014-9112
Hi, On Fri, 12 Dec 2014, Aníbal Monsalve Salazar wrote: I uploaded cpio 2.11+dfsg-3 to experimental with the upstream patches listed above. Please test it. It didn't segfault when I run it on amd64 as reported in Red Hat's Bugzilla. You need to use dh_autoreconf (dh --with autoreconf) if you want to run the new tests that the upstream patches are providing. Right now the build log https://buildd.debian.org/status/fetch.php?pkg=cpioarch=i386ver=2.11%2Bdfsg-3stamp=1418386587 doesn't show the new tests (symlink-bad-length and symlink-long) being executed. (You can compare this with the logs of the squeeze-lts update that I just uploaded) Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773198: wfrog: Make sure wfrog works with pyusb1.0
Package: wfrog Version: 0.8.2+svn953-1 Severity: wishlist Dear Maintainer, python-usb 1.0 will soon (hopefully) be uploaded to experimental. It would be nice to ensure that wfrog also works with this version of pyusb. Hopefully it works well without any changes. A version of pyusb can be found on: http://mentors.debian.net/package/pyusb Regards, Ruben -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wfrog depends on: ii python2.7.8-2 ii python-cheetah2.4.4-3 ii python-lxml 3.4.0-1 ii python-pygooglechart 0.3.0-1 ii python-serial 2.6-1.1 ii python-usb1.0.0b2-1 ii python-yaml 3.11-2 wfrog recommends no packages. wfrog 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#773199: python-yubico: Make sure python-yubico works with pyusb1.0
Package: python-yubico Version: 1.1.0-2 Severity: wishlist Dear Maintainer, python-usb 1.0 will soon (hopefully) be uploaded to experimental. It would be nice to ensure that python-yubico also works with this version of pyusb. Hopefully it works well without any changes. A version of pyusb1.0 can be found on: http://mentors.debian.net/package/pyusb Regards, Ruben -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-yubico depends on: ii python 2.7.8-2 ii python-support 1.0.15 ii python-usb 1.0.0b2-1 python-yubico recommends no packages. python-yubico 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#773200: pymissile: Make sure pymissile works with pyusb1.0
Package: pymissile Version: 0.0.20060725-4 Severity: wishlist Dear Maintainer, python-usb 1.0 will soon (hopefully) be uploaded to experimental. It would be nice to ensure that pymissile also works with this version of pyusb. Hopefully it works well without any changes. A version of pyusb1.0 can be found on: http://mentors.debian.net/package/pyusb Regards, Ruben -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pymissile depends on: ii python2.7.8-2 ii python-urwid 1.2.1-2+b1 ii python-usb1.0.0b2-1 pymissile recommends no packages. pymissile 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#773201: python-nxt: Make sure python-nxt works with pyusb1.0
Package: python-nxt Version: 2.2.2-2 Severity: wishlist Dear Maintainer, python-usb 1.0 will soon (hopefully) be uploaded to experimental. It would be nice to ensure that python-nxt also works with this version of pyusb. Hopefully it works well without any changes. A version of pyusb1.0 can be found on: http://mentors.debian.net/package/pyusb Regards, Ruben -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-nxt depends on: ii python2.7.8-2 ii python-bluez 0.20-1 ii python-usb1.0.0b2-1 python-nxt recommends no packages. python-nxt 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#773202: python-expeyes: Make sure python-expeyes works with pyusb1.0
Package: python-expeyes Version: 3.3.1-1 Severity: wishlist Dear Maintainer, python-usb 1.0 will soon (hopefully) be uploaded to experimental. It would be nice to ensure that python-expeyes also works with this version of pyusb. Hopefully it works well without any changes. A version of pyusb1.0 can be found on: http://mentors.debian.net/package/pyusb Regards, Ruben -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-expeyes depends on: ii python 2.7.8-2 ii python-scipy 0.14.0-2 ii python-serial 2.6-1.1 ii python-usb 1.0.0b2-1 ii qtiplot0.9.8.9-9+b3 Versions of packages python-expeyes recommends: ii expeyes-doc-en [expeyes-doc] 3.3.1-1 ii udev 215-8 Versions of packages python-expeyes suggests: pn python-pygrace 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#768189: Bug#773195: unblock macchanger/1.7.0-4
Holger Levsen wrote: adding debian-l10n-engl...@lists.debian.org to cc: to get feedback and advice. On Montag, 15. Dezember 2014, Hans-Christoph Steiner wrote: diff -Nru macchanger-1.7.0/debian/po/templates.pot macchanger-1.7.0/debian/po/templates.pot Is this only in the git version or something? Oh, okay, found it. --- macchanger-1.7.0/debian/po/templates.pot 1970-01-01 01:00:00.0 +0100 +++ macchanger-1.7.0/debian/po/templates.pot 2014-12-15 [...] +msgid Would you like your MAC automatically changed? [...]+ This then gives you a new MAC every time you plug... I believe addressing users directly like this is frowned upon and not recommended, (at least it's not done in d-i, TTBOMK). AFAIK it's better to use wordings like Should the MAC address automatically get changed? instead of the first msgid above. Indeed, in the short description line it shouldn't even be a full sentence. It ought to be something like this (and it should have come through d-l-e for review before it went to translators): Template: macchanger/automatically_run Type: boolean Default: false _Description: Change MAC automatically? Please specify whether macchanger should be set up to run automatically every time a network device is brought up or down. This gives a new MAC address whenever you attach or detach an ethernet cable, or enable/disable wifi. But wait, how can it give a new MAC address for a DEconfigured network interface? Shouldn't it be just: Template: macchanger/automatically_run Type: boolean Default: false _Description: Change MAC automatically? Please specify whether macchanger should be set up to run automatically every time a network device is brought up or down. This gives a new MAC address whenever you reattach an ethernet cable or reenable wifi. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package --- templates.orig 2014-12-15 14:18:20.308009214 + +++ templates 2014-12-15 14:20:27.212552090 + @@ -1,7 +1,7 @@ Template: macchanger/automatically_run Type: boolean Default: false -_Description: Would you like your MAC automatically changed? - macchanger can be set up to automatically run everytime a network device - is brought up or down. This then gives you a new MAC every time you plug - or unplug an ethernet cable, or enable/disable wifi. +_Description: Change MAC automatically? + Please specify whether macchanger should be set up to run automatically + every time a network device is brought up or down. This gives a new MAC + address whenever you reattach an ethernet cable or reenable wifi. Template: macchanger/automatically_run Type: boolean Default: false _Description: Change MAC automatically? Please specify whether macchanger should be set up to run automatically every time a network device is brought up or down. This gives a new MAC address whenever you reattach an ethernet cable or reenable wifi.
Bug#771730: let dpkg from sid PLEASE URGENTLY migrate to jessie
Hi! I’m reporting two problems with the dpkg version in jessie: ① I’ve recently tried to upgrade a system from wheezy to jessie and failed (due to trigger cycles) until I installed dpkg from sid first. That means that the version from sid is still better than the version that is currently in jessie, even if the fix may be incomplete. Please make this bug (#771730) not a blocker for migration, and have it migrate quickly. ② In #772870 it was suggested that FusionForge switch to noawait triggers. This works in wheezy and sid, but not in jessie, until, you guessed it, dpkg from sid is installed. So, please let dpkg migrate quickly. (I won’t ask for an unblock directly because there may still be other regressions/issues, thus I’m asking dpkg’s maintainers to request that.) Thanks, //mirabilos (hats: Sysadmin; FusionForge contributor) -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773197: origami package replaced by a completely different package
Hello, On Mon, Dec 15, 2014 at 03:02:10PM +0100, Robert Bihlmeyer wrote: Package: origami Version: 1.2.7-1 Severity: serious https://packages.debian.org/jessie/origami and https://packages.debian.org/sid/origami are totally different. I assume this is a slip-up by the uploader of the sid version, which should get a new name. I acknowldge my mistake here. I don't know how I missed the fact that there was already an existing origami package, and I am very sorry for this. I will fix this imediately be re-uploading the original package with a larger version number. Christer, how to you prefer me to handle the versioning of the package? I can use either a) 1:0.7.4-2 or b) 1.2.7+really0.7.4-1 a) is a little worse IMO since that epoch will have to stay there forever. the ugly bits in b) can go away as soon as the new upstream version is 1.2.7 -- Antonio Terceiro terce...@debian.org signature.asc Description: Digital signature
Bug#773201: python-nxt: Make sure python-nxt works with pyusb1.0
On Monday, December 15, 2014 15:16:12 Ruben Undheim wrote: Package: python-nxt Version: 2.2.2-2 Severity: wishlist Dear Maintainer, python-usb 1.0 will soon (hopefully) be uploaded to experimental. It would be nice to ensure that python-nxt also works with this version of pyusb. Hopefully it works well without any changes. A version of pyusb1.0 can be found on: http://mentors.debian.net/package/pyusb There's a patch in the upstream bug tracker for python-nxt. Scott K signature.asc Description: This is a digitally signed message part.
Bug#772217: fixed in cmtk 3.2.2-1.1
thank you guys for helping with the cmtk package! And sorry for being
slow to respond/react
Upstream also issued a patch to address bashisms, see it attached.
it seems that we are still at -1.2 in the archive so I could issue -2
with this one or if you are at it already -- just go ahead with NMU and
I will absorb it later into VCS
(http://git.debian.org/?p=pkg-exppsy/cmtk.git)
cheers
On Sun, 14 Dec 2014, Adam D. Barratt wrote:
Control: reopen -1
On Sun, 2014-12-14 at 21:48 +, Michael Gilbert wrote:
cmtk (3.2.2-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Fix bashisms in shell scripts (closes: #772217).
Unfortunately the fixes are incorrect in some cases:
+- if [[ ${line} =~ ^\} ]]; then
++ if [ ${line} =~ ^\} ]; then
Even bash doesn't support =~ outside of its [[ extension.
Regards,
Adam
--
Yaroslav O. Halchenko, Ph.D.
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Research Scientist,Psychological and Brain Sciences Dept.
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419
WWW: http://www.linkedin.com/in/yarik
From 008f9d42626a64378f9d5565798d225556842484 Mon Sep 17 00:00:00 2001
From: torsten_at_home torsten_at_home@42a5c34f-2066-0410-bec5-ba365beb4995
Date: Thu, 11 Dec 2014 16:47:59 +
Subject: [PATCH] FIX: bashisms
git-svn-id: https://www.nitrc.org/svn/cmtk/trunk@5374 42a5c34f-2066-0410-bec5-ba365beb4995
---
core/scripts/cmtk_functions.sh.in | 6 --
core/scripts/groupwise_reformat.in | 6 --
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/core/scripts/cmtk_functions.sh.in b/core/scripts/cmtk_functions.sh.in
index 2e1ebf7..ba7226f 100755
--- a/core/scripts/cmtk_functions.sh.in
+++ b/core/scripts/cmtk_functions.sh.in
@@ -1,6 +1,8 @@
#!/bin/sh
##
+## Copyright 2014 Google Inc.
+##
## Copyright 2007-2011, 2014 SRI International
##
## This file is part of the Computational Morphometry Toolkit.
@@ -32,9 +34,9 @@ export CMTK_BINARY_DIR=${CMTK_BINARY_DIR:-@CMTK_BINARY_DIR_CONFIG@}
# Check whether we have lockfile tool available and include proper script with locking functions
if which lockfile /dev/null; then
-source ${CMTK_BINARY_DIR}/cmtk_locking_procmail.sh
+. ${CMTK_BINARY_DIR}/cmtk_locking_procmail.sh
else
-source ${CMTK_BINARY_DIR}/cmtk_locking.sh
+. ${CMTK_BINARY_DIR}/cmtk_locking.sh
fi
# For convenience and readability
diff --git a/core/scripts/groupwise_reformat.in b/core/scripts/groupwise_reformat.in
index 848d31c..803597f 100755
--- a/core/scripts/groupwise_reformat.in
+++ b/core/scripts/groupwise_reformat.in
@@ -1,6 +1,8 @@
-#!/bin/sh
+#!/bin/bash
##
+## Copyright 2014 Google Inc.
+##
## Copyright 2012, 2014 SRI International
##
## Copyright 2012 Torsten Rohlfing
@@ -46,7 +48,7 @@ fi
# put all arguments starting with - into reformat options
reformatOptions=
while [[ $1 =~ ^- ]]; do
-reformatOptions+=$1
+reformatOptions+=${1}
shift
done
--
2.1.3
signature.asc
Description: Digital signature
Bug#712206: Wishlist bugs created for all direct pyusb dependencies
Hi, I have now created wishlist bugs for all the direct pyusb dependencies: wfrog: #773198 python-yubico: #773199 pymissile: #773200 python-nxt: #773201 python-expeyes: #773202 Regards Ruben -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772645: lists.debian.org: Please create debian-moderat...@lists.debian.org
Since Raphael asked for support, I am hereby publicly declaring that I support such idea and the list creation. Cheers, Ondrej On Tue, Dec 9, 2014, at 15:31, Raphael Hertzog wrote: Package: lists.debian.org Severity: wishlist Hello, with the adoption of the code of conduct, more and more people started to respond to persons who do not follow its spirit, to let them know that the message was inappropriate in one way or another. Some do it publicly and other do it privately. This is good. Unfortunately, when such a message is sent publicly on the same mailing list, it oftens degenerates in a small sub-thread. This is bad because it generates useless tension and because its brings down the signal/noise ratio on the given list. At the same time, those discussions are also necessary to have some balance and remember collectively that we do not want to over-regulate our mailing lists either. Thus I would like to have a new mailing list called debian-moderat...@lists.debian.org that moderators (i.e. contributors who are telling others that their behaviour was inappropriate, or contributors refuting such claims) would use. The complaint would go the interested person and would be carbon copied to this list. This has multiple benefits: - people acting as moderators get a better feel of what can be done and what can't be done (by following what others are doing they auto-regulate themselves) - listmasters can monitor the list to detect regular offenders and take more informed decisions for (temporary) bans - meta-discussions no longer pollute our work mailing lists To not exclude moderators who are unwilling to send complaints publicly, I believe that the mailing list should be private (but archived with archives accessible to DD only) and only open to Debian developers by default. Possibly non-DD could join but they would need the invitation of a DD. A copy of this mail is sent to debian-project, both to have some public discussion of this idea (in that case, please do not keep the bug in copy), and to sollicit a few ack from other DD who are already doing that kind of moderation work (or would like to start doing it in a more organized way). Thank you. FTR, this idea was initially submitted in a debian-private thread discussing the code of conduct. -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-project-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141209143104.ga19...@home.ouaza.com -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
