Bug#410152: pilot-link: udev rules need updating
Package: pilot-link
Version: 0.12.1-5
Severity: minor
pilot-link comes with some handy dandy udev rules
(/usr/share/pilot-link/udev/60-libpisock.rules) to help get permissions
right when plugging in a device. However, these rules no longer work with
the current version of udev in Debian.
The version of udev in Debian now (0.103) expects various rules to use
ATTRS{...} instead of the old SYSFS{...}, but the rules file still uses the
SYSFS syntax, which prevents it from functioning properly.
AFAICT, replacing all instances of SYSFS with ATTRS in the rules file makes
it work as intended, or at least it does for me.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.2-van2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages pilot-link depends on:
ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries
ii libpisock90.12.1-5 library for communicating with a P
ii libpng12-01.2.15~beta5-1 PNG library - runtime
ii libreadline5 5.2-2 GNU readline and history libraries
pilot-link recommends no packages.
-- debconf information:
shared/pilot/port: None
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392472: gpar2: Which Package?
Package: gpar2 Version: 0.3-2 Followup-For: Bug #392472 AFAICT, all packages gpar2 depends on directly are up to date in testing, and I'm seeing the same error as the original reporter. Which package specifically needs to be update to work properly with gpar2? If it depends on a particular minimum version of a package to work, shouldn't it depend/conflict explicitly? -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19.2-van2 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gpar2 depends on: ii desktop-file-utils 0.11-1 Utilities for .desktop files ii libatk1.0-0 1.12.4-1 The ATK accessibility toolkit ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libfontconfig1 2.4.2-1 generic font configuration library ii libgcc1 1:4.1.1-21 GCC support library ii libglib2.0-02.12.4-2 The GLib library of C routines ii libglibmm-2.4-1c2a 2.12.0-1 C++ wrapper for the GLib toolkit ( ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface ii libgtkmm-2.4-1c2a 1:2.8.8-1C++ wrappers for GTK+ 2.4 (shared ii libpango1.0-0 1.14.8-4 Layout and rendering of internatio ii libpar2-0 0.2-1A library for performing comman ta ii libsigc++-2.0-0c2a 2.0.17-2 type-safe Signal Framework for C++ ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-5X11 client-side library ii libxcursor1 1.1.7-4 X cursor management library ii libxext61:1.0.1-2X11 miscellaneous extension librar ii libxfixes3 1:4.0.1-5X11 miscellaneous 'fixes' extensio ii libxi6 1:1.0.1-4X11 Input extension library ii libxinerama11:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender1 1:0.9.1-3X Rendering Extension client libra ii shared-mime-info0.19-2 FreeDesktop.org shared MIME databa gpar2 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#388006: nfs-common: init script does not write rpc.idmapd.pid
Package: nfs-common Version: 1:1.0.10-1 Severity: normal The mount program looks for /var/run/rpc.idmapd.pid to detect if idmapd is running. The init script for nfs-common will start idmapd, but does not invoke it in a way that creates that pid file. Thus all nfs4 mount attempts cause mount to warn that all user ids will be mapped to the anonymous one. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.13-van1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages nfs-common depends on: ii adduser3.97 Add and remove users and groups ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libcomerr2 1.39-1common error description library ii libevent1 1.1a-1An asynchronous event notification ii libgssapi2 0.10-3A mechanism-switch gssapi library ii libkrb53 1.4.4~beta1-1 MIT Kerberos runtime libraries ii libnfsidmap1 0.16-3An nfs idmapping library ii librpcsecgss3 0.14-2allows secure rpc communication us ii lsb-base 3.1-15Linux Standard Base 3.1 init scrip ii portmap5-20 The RPC portmapper ii sysvinit 2.86.ds1-15 System-V-like init utilities ii ucf2.0014Update Configuration File: preserv nfs-common recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#261352: joe: Perl highliting fixed upstream
Package: joe Version: 3.3-5 Followup-For: Bug #261352 While the $` issue seems to be fixed somewhere between 3.1 and 3.3, a very similar bug regarding using variables named $q still exists in 3.3. The changelog for upstream indicates that this (along with several other bugs) was fixed either in 3.4 or 3.5. Would be nice to get that new upstream version into Debian. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.13-van1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages joe depends on: ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libncurses5 5.5-3 Shared libraries for terminal hand joe recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#732753: xserver-xorg-video-intel: Backlight changes very slow in gnome, server picks "wrong" interface
On 2013-12-21 09:38, Julien Cristau wrote: Please report this upstream at bugs.freedesktop.org following the instructions at https://01.org/linuxgraphics/documentation/how-report-bugs and let us know the bug number for tracking. I've submitted https://bugs.freedesktop.org/show_bug.cgi?id=72959 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#733133: xwiimote: xwiikeymap often fails to connect to new wiimotes
Package: xwiimote Version: 0.3+20120630-5+b1 Severity: normal The xwiikeymap tool attempts to configure new wiimotes as they connect, but it has a glitch. tools/xwiikeymap.c line 218 has a short sleep after a new device appears, but this sleep is too short. Extending it from 10ms to 100ms works for me. Upstream seems to have abandoned xwiikeymap (it is no longer in the github repo), in favor of the xorg input driver, which I see has an ITP for debian, but no package yet yet. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages xwiimote depends on: ii libc6 2.17-97 ii libncurses5 5.9+20130608-1 ii libtinfo5 5.9+20130608-1 ii libxwiimote1 0.3+20120630-5+b1 xwiimote recommends no packages. xwiimote 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#713612: vdpau-video: FTBFS: utils_glx.h:163:5: error: unknown type name 'PFNGLMULTITEXCOORD2FPROC'
Package: vdpau-video Version: 0.7.3-2 Followup-For: Bug #713612 I know debian-multimedia.org is persona non grata in some portions of the debian circle, but they do have patches for this (and other FTBFS problems) in vdpau-video-dmo 0.7.4-dmo1. The dmo patches for 0.7.4 apply cleanly to the debian 0.7.3-2 source package, and allowed me to build it from source properly. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606165: Support python3
Package: pylint
Version: 1.1.0-1
Followup-For: Bug #606165
I got annoyed with this and decided to try to fix it. Attached patch I
think gets about 90% of the way there.
The big thing that is broken is that the unit tests fail under python3
because they're written for python2 and need 2to3 run across a copy of them
to have any hope. This doesn't stop the package from building, however.
Some of the unit tests are failing under python2, but I don't think that's
the fault of these changes.
Something is slightly haywire with the package build knowing which version
of python is used for which binary package, and so the python2 package
generates these warnings:
dpkg-gencontrol: warning: package pylint: unused substitution variable
${python3:Depends}
dpkg-gencontrol: warning: package pylint: unused substitution variable
${python:Versions}
Not sure how to fix that, or if it even needs fixing?
diff -urN pylint-1.1.0/debian/changelog pylint-1.1.0-py3/debian/changelog
--- pylint-1.1.0/debian/changelog 2014-01-25 17:49:23.0 -0500
+++ pylint-1.1.0-py3/debian/changelog 2014-01-25 17:50:20.051156610 -0500
@@ -1,3 +1,10 @@
+pylint (1.1.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add python3 support experimentally
+
+ -- Matthew Gabeler-Lee (Cheetah) Sat, 25 Jan 2014 17:49:57 -0500
+
pylint (1.1.0-1) unstable; urgency=low
* New upstream release
diff -urN pylint-1.1.0/debian/control pylint-1.1.0-py3/debian/control
--- pylint-1.1.0/debian/control 2014-01-25 17:49:23.0 -0500
+++ pylint-1.1.0-py3/debian/control 2014-01-25 18:45:44.147319953 -0500
@@ -3,8 +3,8 @@
Priority: optional
Maintainer: Python Applications Packaging Team
Uploaders: Sylvain Thénault , Alexandre Fayolle , Sandro Tosi
-Build-Depends: debhelper (>= 9), python (>= 2.6.6-3~)
-Build-Depends-Indep: python-logilab-common (>= 0.53.0), python-astroid, python-unittest2
+Build-Depends: debhelper (>= 9), python (>= 2.6.6-3~), python3 (>= 3.3.2-17)
+Build-Depends-Indep: python-logilab-common (>= 0.53.0), python3-logilab-common (>= 0.53.0), python-astroid, python3-astroid, python-unittest2
Standards-Version: 3.9.5
XS-Python-Version: >= 2.6
Homepage: http://www.pylint.org/
@@ -19,6 +19,31 @@
Pylint is a Python source code analyzer which looks for programming
errors, helps enforcing a coding standard and sniffs for some code
smells (as defined in Martin Fowler's Refactoring book)
+ .
+ Pylint can be seen as another PyChecker since nearly all tests you
+ can do with PyChecker can also be done with Pylint. However, Pylint
+ offers some more features, like checking length of lines of code,
+ checking if variable names are well-formed according to your coding
+ standard, or checking if declared interfaces are truly implemented,
+ and much more.
+ .
+ Additionally, it is possible to write plugins to add your own checks.
+ .
+ The package also ships the following additional commands:
+ .
+ * pyreverse: an UML diagram generator
+ * symilar: an independent similarities checker
+ * epylint: Emacs and Flymake compatible Pylint
+ * pylint-gui: a graphical interface (reason for python-tk recommends)
+
+Package: pylint3
+Architecture: all
+Depends: ${python3:Depends}, ${misc:Depends}, python3-logilab-common (>= 0.53.0), python3-astroid
+Recommends: python3-tk
+Description: python code static checker and UML diagram generator (python3 version)
+ Pylint is a Python source code analyzer which looks for programming
+ errors, helps enforcing a coding standard and sniffs for some code
+ smells (as defined in Martin Fowler's Refactoring book)
.
Pylint can be seen as another PyChecker since nearly all tests you
can do with PyChecker can also be done with Pylint. However, Pylint
diff -urN pylint-1.1.0/debian/pylint3.docs pylint-1.1.0-py3/debian/pylint3.docs
--- pylint-1.1.0/debian/pylint3.docs 1969-12-31 19:00:00.0 -0500
+++ pylint-1.1.0-py3/debian/pylint3.docs 2014-01-25 17:51:18.554738004 -0500
@@ -0,0 +1,2 @@
+#doc/*
+README
diff -urN pylint-1.1.0/debian/pylint3.examples pylint-1.1.0-py3/debian/pylint3.examples
--- pylint-1.1.0/debian/pylint3.examples 1969-12-31 19:00:00.0 -0500
+++ pylint-1.1.0-py3/debian/pylint3.examples 2014-01-25 17:51:44.986551571 -0500
@@ -0,0 +1 @@
+examples/*
diff -urN pylint-1.1.0/debian/pylint3.manpages pylint-1.1.0-py3/debian/pylint3.manpages
--- pylint-1.1.0/debian/pylint3.manpages 1969-12-31 19:00:00.0 -0500
+++ pylint-1.1.0-py3/debian/pylint3.manpages 2014-01-25 17:51:18.554738004 -0500
@@ -0,0 +1 @@
+man/*.1
diff -urN pylint-1.1.0/debian/rules pylint-1.1.0-py3/debian/rules
--- pylint-1.1.0/debian/rules 2014-01-25 17:49:23.0 -0500
+++ pylint-1.1.0-py3/debian/rules 2014-01-25 18:48:18.418266396 -0500
@@ -3,39 +3,71 @@
# Uncomment this to turn on verbose mode.
#export DH_VERBOSE=1
-PYVERS := $(shell pyversions -s -v)
+PYVERS2 := $(shell pyversions -s -v)
+PYVERS3 := $(shell py
Bug#737898: i8kmon: no UI visible
Package: i8kutils Version: 1.40 Severity: normal With the gnome 3 desktop, the i8kmon UI does not appear. I suspect this may be related to gnome changing the rules on docked tray apps, but I'm not sure how to verify this. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages i8kutils depends on: ii acpi 1.7-1 ii libc6 2.17-97 ii tcl8.5.0-2.1 ii tk 8.5.0-2.1 i8kutils recommends no packages. i8kutils 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#737896: i8kutils: Missing Depends: acpitool (or: bug handling not-installed optional program)
Package: i8kutils
Version: 1.40
Severity: normal
If acpitool is not installed, i8kmon fails to run:
couldn't execute "acpitool": no such file or directory
while executing
"exec acpitool -a"
("eval" body line 1)
invoked from within
"eval exec $cmd2"
(procedure "read_ac_status" line 13)
invoked from within
"read_ac_status"
(procedure "read_i8k_status" line 27)
invoked from within
"read_i8k_status"
(procedure "check_status" line 10)
invoked from within
"check_status"
(procedure "status_timer" line 9)
invoked from within
"status_timer"
(procedure "main" line 7)
invoked from within
"main"
invoked from within
"if {$tcl_interactive == 0} {
main
vwait forever
}"
(file "/usr/bin/i8kmon" line 690)
Looking at the source, it looks like i8kmon is trying to allow either the
acpi or acpitool programs to provide the info it needs, but it is not
handling this correctly. I don't know enough TCL to know how to fix this,
but installing acpitool works as a workaround.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages i8kutils depends on:
ii acpi 1.7-1
ii libc6 2.17-97
ii tcl8.5.0-2.1
ii tk 8.5.0-2.1
i8kutils recommends no packages.
i8kutils 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#606165: Support python3
Package: pylint Version: 0.27.0-1 Followup-For: Bug #606165 3 years on... I see that a 1.0.0 upstream update package is "pending", but looking in the subversion repo for the debian packaging, it still doesn't have python 3.x support. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages pylint depends on: ii python 2.7.5-5 ii python-logilab-astng 0.23.1-1 ii python-logilab-common 0.59.1-1 ii python-support 1.0.15 Versions of packages pylint recommends: pn python-tk pylint 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#710275: postgresql-9.1: Needs restart on libc upgrade
On 2013-12-18 04:49, Christoph Berg wrote: a late followup here: which kind of authentication do you have configured there? I'd assume the problem only affects "pam". Actually I'm only using md5 and ident with a username map. (I'm downgrading the bug to normal because "pam" is not the default configuration.) No problem. I'm also no longer using 9.1, and there hasn't been another big libc upgrade to see if the issue still affects 9.3. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703472: iceweasel freezes in _MD_WaitUnixProcess after mailcap "test" command terminates
Package: iceweasel
Version: 26.0-1
Followup-For: Bug #703472
I'm not sure how to represent this to the debian BTS (clone this bug?), but
it appears that this also affects icedove, at least version 24.1.1-1.
-- Package-specific info:
-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: enabled
Name: Add-on Compatibility Reporter
Location: ${PROFILE_EXTENSIONS}/compatibil...@addons.mozilla.org.xpi
Status: enabled
Name: All-in-One Gestures
Location: ${PROFILE_EXTENSIONS}/{8b86149f-01fb-4842-9dd8-4d7eb02fd055}
Status: enabled
Name: Certificate Patrol
Location: ${PROFILE_EXTENSIONS}/certpat...@psyc.eu.xpi
Status: enabled
Name: Cookie Monster
Location: ${PROFILE_EXTENSIONS}/{45d8ff86-d909-11db-9705-005056c8}.xpi
Status: enabled
Name: Default theme
Location:
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled
Name: DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}
Status: user-disabled
Name: DownThemAll!
Location: ${PROFILE_EXTENSIONS}/{DDC359D1-844A-42a7-9AA1-88A850A938A8}.xpi
Status: user-disabled
Name: Element Hiding Helper for Adblock Plus
Location: ${PROFILE_EXTENSIONS}/elemhidehel...@adblockplus.org.xpi
Status: enabled
Name: Evernote Web Clipper
Location: ${PROFILE_EXTENSIONS}/{E0B8C461-F8FB-49b4-8373-FE32E9252800}
Status: enabled
Name: Fox To Phone
Location: ${PROFILE_EXTENSIONS}/sendtoph...@martinezdelizarrondo.com.xpi
Status: enabled
Name: FoxyProxy Standard
Location: ${PROFILE_EXTENSIONS}/foxypr...@eric.h.jung
Status: enabled
Name: Greasemonkey
Location: ${PROFILE_EXTENSIONS}/{e4a8a97b-f2ed-450b-b12d-ee082ba24781}.xpi
Status: enabled
Name: InlineDisposition
Location: ${PROFILE_EXTENSIONS}/{123647d5-da43-4344-bfe2-fc093bdf8f5e}.xpi
Status: user-disabled
Name: Linkification
Location: ${PROFILE_EXTENSIONS}/{35106bca-6c78-48c7-ac28-56df30b51d2a}.xpi
Status: enabled
Name: Mozilla Archive Format
Location: ${PROFILE_EXTENSIONS}/{7f57cf46-4467-4c2d-adfa-0cba7c507e54}.xpi
Status: user-disabled
Name: PasswordMaker
Location: ${PROFILE_EXTENSIONS}/{5872365e-67d1-4afd-9480-fd293bebd20d}.xpi
Status: enabled
Name: Policy Manager
Location: ${PROFILE_EXTENSIONS}/{CE494EE3-65A1-4f63-8FC1-645217F86979}.xpi
Status: enabled
Name: Referrer Control
Location: ${PROFILE_EXTENSIONS}/referrercont...@qixinglu.com.xpi
Status: enabled
Name: ReloadEvery
Location: ${PROFILE_EXTENSIONS}/{888d99e7-e8b5-46a3-851e-1ec45da1e644}.xpi
Status: enabled
Name: Saved Password Editor
Location: ${PROFILE_EXTENSIONS}/savedpasswordedi...@daniel.dawson.xpi
Status: enabled
Name: Searchbar Autosizer
Location: ${PROFILE_EXTENSIONS}/{655397ca-4766-496b-b7a8-3a5b176ee4c2}.xpi
Status: enabled
Name: SPDY indicator
Location: ${PROFILE_EXTENSIONS}/spdyindica...@chengsun.github.com.xpi
Status: enabled
Name: Stylish
Location: ${PROFILE_EXTENSIONS}/{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}.xpi
Status: enabled
Name: Stylish Sync
Location: ${PROFILE_EXTENSIONS}/{0e3fc079-afbb-4a00-87e5-9486062d0f9c}.xpi
Status: enabled
Name: Tab notifier
Location: ${PROFILE_EXTENSIONS}/tabnotif...@unusoft.it.xpi
Status: enabled
Name: User Agent Switcher
Location: ${PROFILE_EXTENSIONS}/{e968fc70-8f95-4ab9-9e79-304de2a71ee1}.xpi
Status: user-disabled
Name: WebPG for Firefox
Location: ${PROFILE_EXTENSIONS}/webpg-fire...@curetheitch.com
Status: user-disabled
Name: xda-developers forum - suppress minimum page width userstyle
Status: enabled
-- Plugins information
Name: Gnome Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: enabled
Name: Google Talk Plugin
Location: /opt/google/talkplugin/libnpgoogletalk.so
Package: google-talkplugin
Status: enabled
Name: Google Talk Plugin Video Accelerator
Location: /opt/google/talkplugin/libnpgtpo3dautoplugin.so
Package: google-talkplugin
Status: enabled
Name: Google Talk Plugin Video Renderer
Location: /opt/google/talkplugin/libnpo1d.so
Package: google-talkplugin
Status: enabled
Name: IcedTea-Web Plugin (using IcedTea-Web 1.3.2 (1.3.2-1))
Location: /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-7-plugin:amd64
Status: enabled
Name: Shockwave Flash (11,2,202,310)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: enabled
-- Addons package information
ii gnome-shell3.8.4-5 amd64graphical shell for the GNOME des
ii google-talkplu 4.9.1.0-1amd64Google Talk Plugin
ii icedtea-7-plug 1.3.2-1 amd64web browser plugin based on OpenJ
ii iceweasel 26.0-1 amd64Web browser based on Firefox
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (c
Bug#703472: iceweasel freezes in _MD_WaitUnixProcess after mailcap "test" command terminates
Package: iceweasel Version: 26.0-1 Followup-For: Bug #703472 I've found a workaround for this issue, for both iceweasel and icedove. Launch the app from a terminal (xterm, etc.), backgrounded, and then dismiss the terminal. I.e. open a terminal and run "iceweasel &" or "icedove &", and then "exit". This seems to keep the zombies at bay. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#734930: libswt-webkit-gtk-3-jni: Prefers to load libwebkitgtk-1.0 over libwebkitgtk-3.0, and then crashes
Package: libswt-webkit-gtk-3-jni Version: 3.8.2-3 Severity: important It seems that this package prefers to load libwebkitgtk-1.0 over libwebkigtk-3.0, even though it only seems to work with 3.0. The upshot of this (for me), is that if libwebkitgtk-1.0-0 is installed (e.g. because I want to use gimp), then eclipse crashses as soon as anything loads webkit, such as a javadoc tooltip. I.e. eclipse is totally unusable. If I uninstall libwebkitgtk-1.0-0 (and leave -3.0-0 installed) eclipse works fine. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libswt-webkit-gtk-3-jni depends on: ii libc6 2.17-97 ii libswt-gtk-3-jni 3.8.2-3 libswt-webkit-gtk-3-jni recommends no packages. libswt-webkit-gtk-3-jni 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#735524: samba: Unbounded per-client logging
Package: samba Version: 2:4.1.3+dfsg-2 Severity: minor Debian's default smb.conf has the directive log file = /var/log/samba/log.%m which is all well and good. But, other than log.smbd and log.nmbd, none of these are rotated or pruned. In the "old" days, this never seemed to be a problem, but in modern days of tablets (with apps with CIFS implementations that use a different hostname every time they launch) and IPv6 (with randomly selected privacy addresses), I find that this is causing this directory to grow, at least in number of files, wildly. I see two sensible options: 1) Adjust the logrotate configuration to rotate /var/log/samba/log.*, remove the notifempty, and add nocreate. 2) Add a tmpreaper script that will remove old per-client logs after some reasonable period of time, with appropriate options so that it doesn't eat the main server log files and their rotation history. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages samba depends on: ii adduser 3.113+nmu3 ii dpkg1.17.5 ii libasn1-8-heimdal 1.6~git20131117+dfsg-3 ii libbsd0 0.6.0-1 ii libc6 2.17-97 ii libcomerr2 1.42.9-2 ii libhdb9-heimdal 1.6~git20131117+dfsg-3 ii libkdc2-heimdal 1.6~git20131117+dfsg-3 ii libkrb5-26-heimdal 1.6~git20131117+dfsg-3 ii libldb1 1:1.1.16-1 ii libpam-modules 1.1.3-9 ii libpam-runtime 1.1.3-9 ii libpopt01.16-8 ii libpython2.72.7.6-4 ii libroken18-heimdal 1.6~git20131117+dfsg-3 ii libtalloc2 2.1.0-1 ii libtdb1 1.2.12-1 ii libtevent0 0.9.19-1 ii lsb-base4.1+Debian12 ii multiarch-support 2.17-97 ii procps 1:3.3.4-2 ii python 2.7.5-5 ii python-dnspython1.11.1-1 ii python-ntdb 1.0-2 ii python-samba2:4.1.3+dfsg-2 pn python2.7:any ii samba-common2:4.1.3+dfsg-2 ii samba-common-bin2:4.1.3+dfsg-2 ii samba-dsdb-modules 2:4.1.3+dfsg-2 ii samba-libs 2:4.1.3+dfsg-2 ii tdb-tools 1.2.12-1 ii update-inetd4.43 Versions of packages samba recommends: pn attr ii logrotate 3.8.6-1 pn samba-vfs-modules Versions of packages samba suggests: pn bind9 pn bind9utils pn ctdb pn ldb-tools ii ntp1:4.2.6.p5+dfsg-3 pn smbldap-tools pn winbind -- Configuration Files: /etc/logrotate.d/samba changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702201: samba: logrotate script for nmbd.log does not wait long enough.
Package: samba
Version: 2:4.1.3+dfsg-2
Followup-For: Bug #702201
The easiest workaround is to add "delaycompress" to the logrotate config so
that logrotate renames the log file on the first rotate, and compresses it
on the second rotate.
-- Configuration Files:
/etc/logrotate.d/samba changed:
/var/log/samba/log.smbd {
weekly
missingok
rotate 7
postrotate
/etc/init.d/smbd reload > /dev/null
endscript
compress
delaycompress
notifempty
}
/var/log/samba/log.nmbd {
weekly
missingok
rotate 7
postrotate
[ ! -f /var/run/samba/nmbd.pid ] || kill -HUP `cat
/var/run/samba/nmbd.pid`
endscript
compress
delaycompress
notifempty
}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#735620: yafc: bash_completion helper broken and in wrong directory
Package: yafc
Version: 1.3.1-1
Severity: minor
The completion helper script is installed as:
/usr/share/bash-completions/completions/yafc
it should be:
/usr/share/bash-completion/completions/yafc
After relocating the file, unfortunately it still didn't work. I was able
to fix it easily enough, however, by comparing with other simple working
completions:
### begin diff
--- /usr/share/bash-completion/completions/yafc.orig2014-01-16
19:43:09.767412420 -0500
+++ /usr/share/bash-completion/completions/yafc 2014-01-16 19:44:23.936038313
-0500
@@ -1,6 +1,5 @@
# bash completion for yafc
-have yafc &&
_yafc()
{
local cur
@@ -15,7 +14,7 @@
return 0
} &&
-complete -F _yafc $default yafc
+complete -F _yafc -o default yafc
# Local variables:
# mode: shell-script
### end diff
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages yafc depends on:
ii libbsd0 0.6.0-1
ii libc62.17-97
ii libedit2 3.1-20130712-2
ii libgssapi3-heimdal 1.6~git20131117+dfsg-3
ii libhcrypto4-heimdal 1.6~git20131117+dfsg-3
ii libroken18-heimdal 1.6~git20131117+dfsg-3
ii libssh-4 0.5.4-1
yafc recommends no packages.
yafc 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#730656: nautilus-dropbox: Colorized output broken
Package: nautilus-dropbox Version: 1.6.0-2 Severity: normal The output of dropbox ls or dropbox filestatus --list is supposed to be colorized when running on a terminal. However, the colorized output is never used because in /usr/bin/dropbox, ~ line 832, there is this: texts[col].replace(original_texts[col], display_texts[col]) Which should be: texts[col] = texts[col].replace(original_texts[col], display_texts[col]) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nautilus-dropbox depends on: ii libatk1.0-0 2.10.0-2 ii libc62.17-93 ii libcairo-gobject21.12.16-2 ii libcairo21.12.16-2 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-0 2.36.4-1 ii libgtk-3-0 3.8.4-1 ii libnautilus-extension1a 3.8.2-2 ii libpango-1.0-0 1.36.0-1 ii libpangocairo-1.0-0 1.36.0-1 ii policykit-1 0.105-4 ii procps 1:3.3.4-2 ii python-gpgme 0.2-3 ii python-gtk2 2.24.0-3+b1 pn python:any Versions of packages nautilus-dropbox recommends: pn libappindicator1 Versions of packages nautilus-dropbox suggests: pn nautilus -- 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#750942: clamav-freshclam: Cron update setting creates logrotate mail spam
On 06/14/2014 07:57 AM, Andreas Cadhalpun wrote: > I modified freshclam's init script to only print a warning and exit > with status code 0, if reload-log is called, but freshclam is set to > update via cron, see [1]. > > Can you confirm that this fixes your problem? Confirmed. The warning is issued to stdout, so the logrotate postrotate script's ">/dev/null" suppresses it. Thank you for your help :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#748055: debian-goodies: checkrestart false positive for MySQL
Package: debian-goodies Version: 0.63 Followup-For: Bug #748055 I have this problem too. The source is that checkrestart sees "/[aio]" from lsof, and concludes that is a "problem". Key output from checkrestart -v: Found 3 processes using old versions of upgraded files (2 distinct programs) Process /usr/sbin/mysqld (PID: 7048) List of deleted files in use: /[aio] This is the only deleted file from mysqld that checkrestart -v reports on. I'm running $ apt-show-versions -p mysql-server-5.5 mysql-server-5.5:amd64/testing 5.5.37-1 uptodate -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debian-goodies depends on: ii curl 7.37.0-1 ii dctrl-tools [grep-dctrl] 2.23 ii dialog1.2-20140219-1 ii perl 5.18.2-4 ii python2.7.6-2 ii whiptail 0.52.15-3+b1 Versions of packages debian-goodies recommends: ii lsof 4.86+dfsg-1 Versions of packages debian-goodies suggests: ii popularity-contest 1.61 ii xdg-utils 1.1.0~rc1+git20111210-7.1 ii zenity 3.12.1-1 -- 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#751729: debian-goodies: checkrestart: False positive with PostgreSQL data files
Package: debian-goodies Version: 0.63 Severity: normal The checkrestart tool is returning false positives on the postgresql server due to how it appears to handle some of its data files: $ sudo checkrestart -v ... Process /usr/lib/postgresql/9.3/bin/postgres (PID: 7242) List of deleted files in use: /XX/postgresql/9.3/main/pg_xlog/000100E40058 (deleted) Process /usr/lib/postgresql/9.3/bin/postgres (PID: 9439) List of deleted files in use: /XX/postgresql/9.3/main/pg_xlog/000100E4005C (deleted) Process /usr/lib/postgresql/9.3/bin/postgres (PID: 8395) List of deleted files in use: /XX/postgresql/9.3/main/pg_xlog/000100E4005C (deleted) I've replaced some non-relevant local filesystem paths with "XX" above. I checked the checkrestart script in case my relocation of postgresql's data files from /var/lib/ to a locally configured path might have caused this, butit looks like that is not the case. The only references to /var/lib in checkrestart are for nagios, and there are no explicit postgresql references I can find. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debian-goodies depends on: ii curl 7.37.0-1 ii dctrl-tools [grep-dctrl] 2.23 ii dialog1.2-20140219-1 ii perl 5.18.2-4 ii python2.7.6-2 ii whiptail 0.52.15-3+b1 Versions of packages debian-goodies recommends: ii lsof 4.86+dfsg-1 Versions of packages debian-goodies suggests: ii popularity-contest 1.61 ii xdg-utils 1.1.0~rc1+git20111210-7.1 ii zenity 3.12.1-1 -- 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#745046: apt: Fails to report dependency problems for /experimental package
Package: apt Version: 1.0.1 Severity: normal Trying to install a package from experimental, apt-get is (apparently) failing to resolve dependencies, but is also failing to report or return any error related to that: $ sudo apt-get install gedit/experimental Reading package lists... Done Building dependency tree Reading state information... Done Selected version '3.12.0-1' (Debian:experimental [amd64]) for 'gedit' The following extra packages will be installed: gedit 0 upgraded, 0 newly installed, 0 to remove and 26 not upgraded. $ echo $? 0 It does behave reasonably if I use "apt-get -t experimental install gedit". -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "0"; APT::Install-Suggests "0"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^linux-image-amd64$"; APT::NeverAutoRemove:: "^linux-headers-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^linux-headers-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-amd64$"; APT::NeverAutoRemove:: "^.*-modules-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^.*-modules-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-amd64$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-amd64$"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-image"; APT::VersionedKernelPackages:: "linux-headers"; APT::VersionedKernelPackages:: "linux-image-extra"; APT::VersionedKernelPackages:: "linux-signed-image"; APT::VersionedKernelPackages:: "kfreebsd-image"; APT::VersionedKernelPackages:: "kfreebsd-headers"; APT::VersionedKernelPackages:: "gnumach-image"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::VersionedKernelPackages:: "linux-backports-modules-.*"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Never-MarkAuto-Sections:: "oldlibs"; APT::Never-MarkAuto-Sections:: "restricted/oldlibs"; APT::Never-MarkAuto-Sections:: "universe/oldlibs"; APT::Never-MarkAuto-Sections:: "multiverse/oldlibs"; APT::Periodic ""; APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "7"; APT::Update ""; APT::Update::Post-Invoke-Success ""; APT::Update::Post-Invoke-Success:: "test -x /usr/bin/apt-show-versions || exit 0 ; apt-show-versions -i"; APT::Update::Post-Invoke-Success:: "/usr/bin/test -e /usr/share/dbus-1/system-services/org.freedesktop.PackageKit.service && /usr/bin/test -S /var/run/dbus/system_bus_socket && /usr/bin/gdbus call --system --dest org.freedesktop.PackageKit --object-path /org/freedesktop/PackageKit --timeout 4 --method org.freedesktop.PackageKit.StateHasChanged cache-update > /dev/null; /bin/echo > /dev/null"; APT::Default-Release "testing"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Architectures:: "i386"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "1"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "2"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-9n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "3"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-9"; APT::Compressor::bzip2::UncompressArg ""; APT::Compressor::bzip2::UncompressArg:: "-d"; APT::Compressor::xz ""; APT::Compressor::xz::Name "xz"; APT::Compressor::xz::Extension ".xz"; APT::Compressor::xz::Binary "xz"; APT::Compressor::xz::Cost "4"; APT::Compressor::xz::CompressArg ""; APT::Compressor::xz::CompressArg:: "-6"; A
Bug#740402: nvidia-kernel-dkms: Dropped hardware support without notice
Package: nvidia-kernel-dkms Version: 331.49-1 Severity: normal In the past, the nvidia driver packages have warned when upgrading to a version that dropped hardware support, and in many cases have provided a legacy- package version that retained that support. As of 319.82-1, the nvidia package no longer has support for my GPU, but I didn't find this out until after it was fully installed. -- Package-specific info: uname -a: Linux cheetah.fastcat.org 3.12-1-amd64 #1 SMP Debian 3.12.6-2 (2013-12-29) x86_64 GNU/Linux /proc/version: Linux version 3.12-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.2 (Debian 4.8.2-10) ) #1 SMP Debian 3.12.6-2 (2013-12-29) lspci 'VGA compatible controller [0300]': 0b:00.0 VGA compatible controller [0300]: NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev ff) (prog-if ff) !!! Unknown header type 7f dmesg: [3789457.124392] nvidia :0b:00.0: Refused to change power state, currently in D3 [3789457.124471] vgaarb: device changed decodes: PCI::0b:00.0,olddecodes=none,decodes=none:owns=none [3789457.124508] NVRM: The NVIDIA GPU :0b:00.0 (PCI ID: 10de:0614) [3789457.124508] NVRM: installed in this system is not supported by the 319.82 [3789457.124508] NVRM: NVIDIA Linux driver release. Please see 'Appendix [3789457.124508] NVRM: A - Supported NVIDIA GPU Products' in this release's [3789457.124508] NVRM: README, available on the Linux driver download page [3789457.124508] NVRM: at www.nvidia.com. [3789457.124537] nvidia: probe of :0b:00.0 failed with error -1 [3789457.124554] NVRM: The NVIDIA probe routine failed for 1 device(s). [3789457.124555] NVRM: None of the NVIDIA graphics adapters were initialized! [3789665.836241] nvidia :0b:00.0: Refused to change power state, currently in D3 [3789665.836322] vgaarb: device changed decodes: PCI::0b:00.0,olddecodes=none,decodes=none:owns=none [3789665.836360] NVRM: The NVIDIA GPU :0b:00.0 (PCI ID: 10de:0614) [3789665.836360] NVRM: installed in this system is not supported by the 319.82 [3789665.836360] NVRM: NVIDIA Linux driver release. Please see 'Appendix [3789665.836360] NVRM: A - Supported NVIDIA GPU Products' in this release's [3789665.836360] NVRM: README, available on the Linux driver download page [3789665.836360] NVRM: at www.nvidia.com. [3789665.836406] nvidia: probe of :0b:00.0 failed with error -1 [3789665.836437] NVRM: The NVIDIA probe routine failed for 1 device(s). [3789665.836439] NVRM: None of the NVIDIA graphics adapters were initialized! [3790021.213198] nvidia :0b:00.0: Refused to change power state, currently in D3 [3790021.213280] vgaarb: device changed decodes: PCI::0b:00.0,olddecodes=none,decodes=none:owns=none [3790021.213321] NVRM: The NVIDIA GPU :0b:00.0 (PCI ID: 10de:0614) [3790021.213321] NVRM: installed in this system is not supported by the 331.49 [3790021.213321] NVRM: NVIDIA Linux driver release. Please see 'Appendix [3790021.213321] NVRM: A - Supported NVIDIA GPU Products' in this release's [3790021.213321] NVRM: README, available on the Linux driver download page [3790021.213321] NVRM: at www.nvidia.com. [3790021.213364] nvidia: probe of :0b:00.0 failed with error -1 [3790021.213398] NVRM: The NVIDIA probe routine failed for 1 device(s). [3790021.213400] NVRM: None of the NVIDIA graphics adapters were initialized! [3790021.213888] NVRM: NVIDIA init module failed! OpenGL and NVIDIA library files installed: lrwxrwxrwx 1 root root 15 Oct 15 11:29 /etc/alternatives/glx -> /usr/lib/nvidia lrwxrwxrwx 1 root root 48 Jul 20 2013 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 root root 48 Jul 20 2013 /etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so lrwxrwxrwx 1 root root 43 Oct 15 11:29 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 43 Oct 15 11:29 /etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1 lrwxrwxrwx 1 root root 51 Oct 15 11:29 /etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> /usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1 lrwxrwxrwx 1 root root 25 Oct 15 11:29 /etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so lrwxrwxrwx 1 root root 42 Oct 15 11:29 /etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> /etc/nvidia/nvidia-blacklists-nouveau.conf lrwxrwxrwx 1 root root 36 Oct 15 11:29 /etc/alternatives/glx--nvidia-bug-report.sh -> /usr/lib/nvidia/nvidia-bug-report.sh lrwxrwxrwx 1 root root 29 Oct 15 11:29 /etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so lrwxrwxrwx 1 root root 22 Jul 20 2013 /etc/alternatives/libGL.so-master -> /usr/lib/mesa-diverted lrwxrwxrwx 1 root root 23 Oct 15 11:29 /etc/alternatives/nvidia -> /usr/lib/nvidia/cu
Bug#739835: ~ vs. filename expansion
Package: bash-completion Version: 1:2.1-2 Followup-For: Bug #739835 Dear Maintainer, Now that jessie has upgrade to bash 4.3, this is pretty much making bash-completion unusable! The patch referenced JuanJo Ciarlante definitely fixes the problem for me. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bash-completion depends on: ii bash 4.3-2 ii dpkg 1.17.6 bash-completion recommends no packages. bash-completion 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#743651: autofs5: does not support recursive mount (regression to #626473)
Package: autofs Version: 5.0.8-1 Followup-For: Bug #743651 Another variant of this problem: Attempting to automount an aufs "view" with automounted branches. A quick look through the code makes me wonder why the locking option was done as a compile time thing. It's used in very few places, and could fairly easily be turned into a runtime thing. Also, I'm pretty sure that #556910 is the same issue as this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#747088: python-appdirs: Upgrade failure
Package: python-appdirs Version: 1.2.0+git20130326-1 Severity: important Attempting to upgrade this package fails! Unpacking python-appdirs (1.3.0-1) over (1.2.0+git20130326-1) ... dpkg: error processing archive /var/cache/apt/archives/python-appdirs_1.3.0-1_all.deb (--unpack): unable to open '/usr/share/pyshared/appdirs-1.3.0.egg-info/dependency_links.txt.dpkg-new': No such file or directory Hmm, well, /usr/share/pyshared/appdirs-1.3.0.egg-info is a file! Uninstalling the package (and everything that depends on it :( ) and reinstalling does work around the problem, and now the .egg-info item is a directory. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-appdirs depends on: pn python:any python-appdirs recommends no packages. python-appdirs 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#750942: clamav-freshclam: Cron update setting creates logrotate mail spam
Package: clamav-freshclam
Version: 0.98.4~rc1+dfsg-3
Severity: normal
If freshclam is set to update via cron, then there is no freshclam pid (but
the init script always creates an empty pid file), and thus I get an email
every day, thus:
/etc/cron.daily/logrotate:
pkill: pidfile not valid
Try `pkill --help' for more information.
Because the logrotate script calls "/etc/init.d/clamav-freshclam reload-log
>/dev/null", which calls pkill pointing at the empty (and thus invalid) pid
/file.
-- Package-specific info:
--- configuration ---
#Automatically Generated by clamav-base postinst
#To reconfigure clamd run #dpkg-reconfigure clamav-base
#Please read /usr/share/doc/clamav-base/README.Debian.gz for details
LocalSocket /var/run/clamav/clamd.ctl
FixStaleSocket true
LocalSocketGroup clamav
LocalSocketMode 666
TemporaryDirectory /tmp
User clamav
AllowSupplementaryGroups true
ScanMail true
ScanArchive true
ArchiveBlockEncrypted false
MaxDirectoryRecursion 15
FollowDirectorySymlinks false
FollowFileSymlinks false
ReadTimeout 180
MaxThreads 12
MaxConnectionQueueLength 15
LogSyslog false
LogRotate true
LogFacility LOG_LOCAL6
LogClean false
LogVerbose false
PidFile /var/run/clamav/clamd.pid
DatabaseDirectory /var/lib/clamav
SelfCheck 3600
Foreground false
Debug false
ScanPE true
MaxEmbeddedPE 10M
ScanOLE2 true
ScanHTML true
MaxHTMLNormalize 10M
MaxHTMLNoTags 2M
MaxScriptNormalize 5M
MaxZipTypeRcg 1M
ScanSWF true
DetectBrokenExecutables true
ExitOnOOM false
LeaveTemporaryFiles false
AlgorithmicDetection true
ScanELF true
IdleTimeout 30
PhishingSignatures true
PhishingScanURLs true
PhishingAlwaysBlockSSLMismatch false
PhishingAlwaysBlockCloak false
DetectPUA false
ScanPartialMessages false
HeuristicScanPrecedence false
StructuredDataDetection false
CommandReadTimeout 5
SendBufTimeout 200
MaxQueue 100
ExtendedDetectionInfo true
OLE2BlockMacros false
ScanOnAccess false
AllowAllMatchScan true
ForceToDisk false
DisableCertCheck false
StreamMaxLength 10M
LogFile /var/log/clamav/clamav.log
LogTime true
LogFileUnlock false
LogFileMaxSize 0
Bytecode true
BytecodeSecurity TrustSigned
BytecodeTimeout 6
OfficialDatabaseOnly false
CrossFilesystems true
# Automatically created by the clamav-freshclam postinst
# Comments will get lost when you reconfigure the clamav-freshclam package
DatabaseOwner clamav
UpdateLogFile /var/log/clamav/freshclam.log
LogVerbose false
LogSyslog false
LogFacility LOG_LOCAL6
LogFileMaxSize 0
LogRotate true
LogTime no
Foreground false
Debug false
MaxAttempts 5
DatabaseDirectory /var/lib/clamav/
DNSDatabaseInfo current.cvd.clamav.net
AllowSupplementaryGroups false
PidFile /var/run/clamav/freshclam.pid
ConnectTimeout 30
ReceiveTimeout 30
TestDatabases yes
ScriptedUpdates yes
CompressLocalDatabase no
SafeBrowsing false
Bytecode true
DatabaseMirror db.local.clamav.net
DatabaseMirror database.clamav.net
DatabaseMirror db.us.clamav.net
--- data dir ---
total 124900
-rw-r--r-- 1 clamav clamav 373760 May 24 00:29 bytecode.cld
-rw-r--r-- 1 clamav clamav 62787584 Jun 8 13:57 daily.cld
-rw-r--r-- 1 clamav clamav 64720632 Sep 18 2013 main.cvd
-rw--- 1 clamav clamav 1248 Jun 8 14:03 mirrors.dat
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages clamav-freshclam depends on:
ii clamav-base0.98.4~rc1+dfsg-3
ii debconf [debconf-2.0] 1.5.53
ii libc6 2.18-7
ii libclamav6 0.98.4~rc1+dfsg-3
ii libssl1.0.01.0.1g-4
ii logrotate 3.8.7-1
ii lsb-base 4.1+Debian12
ii ucf3.0029
ii zlib1g 1:1.2.8.dfsg-1
clamav-freshclam recommends no packages.
Versions of packages clamav-freshclam suggests:
pn apparmor
pn clamav-docs
-- Configuration Files:
/etc/logrotate.d/clamav-freshclam changed:
/var/log/clamav/freshclam.log {
rotate 12
weekly
compress
delaycompress
missingok
create 640 clamav adm
postrotate
/etc/init.d/clamav-freshclam reload-log > /dev/null
endscript
}
-- debconf information:
* clamav-freshclam/LogRotate: true
* clamav-freshclam/NotifyClamd: false
* clamav-freshclam/SafeBrowsing: false
* clamav-freshclam/autoupdate_freshclam: cron
* clamav-freshclam/http_proxy:
* clamav-freshclam/Bytecode: true
* clamav-freshclam/PrivateMirror:
* clamav-freshclam/update_interval: 1
clamav-freshclam/proxy_user:
clamav-freshclam/mirrors.txt-note:
clamav-freshclam/internet_interface:
* clamav-freshclam/local_mirror: db.local.clamav.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697696: closed by Sandro Tosi (Re: Bug#697696: diffstat: Doesn't fetch terminal width correctly)
reopen 697696 thanks On Sun, 13 Jan 2013, Debian Bug Tracking System wrote: Delivery to the following recipient failed permanently: chee...@fastcat.org Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 451 451-209.85.212.171 is not yet authorized to deliver mail from 451 to . Please try later. (state 13). I don't see a reason to keep this bug opened when I can't contact the submitter, closing. Apparently google has SMTP FAIL ... 451 is a temporary error, used in this case for greylisting. Anyways, my point in the bug report is that fetching the COLUMNS environment variable is a no-op, it is completely non-functional. To get the terminal size, you need to do something e.g. with termcap or termios or such. Alternately, one way to work around this without sucking in a dependency like that would be to rename /usr/bin/diffstat to diffstat.real, and have a trivial shell script like the following for /usr/bin/diffstat to make the COLUMNS variable visible to the real diffstat program: #!/bin/bash export COLUMNS exec "`dirname "$0"`"/diffstat.real "$@" -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697696: closed by Sandro Tosi (Re: Bug#697696: diffstat: Doesn't fetch terminal width correctly)
Sandro Tosi wrote: >On Mon, Jan 14, 2013 at 5:20 PM, Matthew Gabeler-Lee > wrote: >> Anyways, my point in the bug report is that fetching the COLUMNS >environment >> variable is a no-op, it is completely non-functional. > >have you tried it? Yes ... hence the bug report ... >$ diff -urNad pp-1.6.2 pp-1.6.3 | diffstat Try with a diff with long paths and an even wider window, e.g. paths > 80 chars and a terminal / window > 100 columns. It will not use the full terminal width, but instead use its minimum histogram width of 10 chars. >$ diff -urNad pp-1.6.2 pp-1.6.3 | COLUMNS=20 diffstat Aah, but here you are explicitly setting the COLUMNS value. My point was that, unless you do something to explicitly expose COLUMNS to diffstat, it isn't available. In your first sample, if you ran it under gdb, you would find that the fetch of the COLUMNS environment var returned NULL. You can demonstrate that simply by just running "env | grep COLUMNS". COLUMNS is an automatic / magic variable, at least in bash, and is not exported to sub-processes by default, so fetching it from a sub-process is not a functional way to query the terminal size. I don't know if other shells behave differently from bash in that regard. My point to the report is that if diffstat wants to find out the terminal size, it should actually query the terminal, instead of hoping that the user would have told their shell to tell diffstat what the terminal size is. If I have to manually send the COLUMNS variable to diffstat, it's no better than a command line option. Exporting COLUMNS from the shell by default is a poor option, I think, because it can cause many programs you might launch from the shell to then not react to terminal size changes, as they will treat having it set as a request to override whatever the reported terminal size is. I actually use that feature sometimes to make reading man pages easier in otherwise very large terminal windows. If using the termcap type facilities is too "heavy weight" for diffstat, it could farm out to stty or some other program that does query the terminal size "properly".
Bug#680663: apt-show-versions: bash-completion _comp_dpkg_installed_packages error
Package: apt-show-versions Version: 0.20 Followup-For: Bug #680663 The original report is correct that this is the same problem as 658773, and it has the same solution. Trivial patch attached. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6-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/bash Versions of packages apt-show-versions depends on: ii apt 0.9.7.6 ii libapt-pkg-perl 0.1.26+b1 ii perl [libstorable-perl] 5.14.2-15 apt-show-versions recommends no packages. apt-show-versions suggests no packages. -- Configuration Files: /etc/bash_completion.d/apt-show-versions changed [not included] -- no debconf information --- apt-show-versions.bash_completion.orig 2013-01-03 10:40:25.560502275 -0500 +++ apt-show-versions.bash_completion 2013-01-03 10:40:42.568639744 -0500 @@ -27,7 +27,7 @@ return 0 ;; -p|--package) -COMPREPLY=( $(_comp_dpkg_installed_packages $cur) ) +COMPREPLY=( $(_xfunc dpkg _comp_dpkg_installed_packages $cur) ) return 0 ;; -stf|--status-file) @@ -44,7 +44,7 @@ COMPREPLY=( $(compgen -W "$opts" -- $cur) ) return 0 else -COMPREPLY=( $(_comp_dpkg_installed_packages $cur) ) +COMPREPLY=( $(_xfunc dpkg _comp_dpkg_installed_packages $cur) ) return 0 fi }
Bug#697415: RFP: hdhomerun-config-gui -- GUI Configuration utility for Silicon Dust HD HomeRun
Package: wnpp Severity: wishlist * Package name: hdhomerun-config-gui Version : 20120405 Upstream Author : Sillicon Dust * URL : http://www.silicondust.com/support/hdhomerun/downloads/linux/ * License : GPLv3 Programming Lang: C++ Description : GUI Configuration utility for Silicon Dust HD HomeRun GUI Configuration utility for Silicon Dust HD HomeRun This package supports the Silicon Dust HDHomeRun. The HDHomeRun is a networked, two tuner digital TV tuner compatible with MythTV, SageTV, and VLC. (Description from Ubuntu) Since this package is already packaged for (Myth)Ubuntu, it should be fairly straight forward to pull into Debian. The command line companion to this (libhdhomerun, hdhomerun-config) is already packaged in Debian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#697696: diffstat: Doesn't fetch terminal width correctly
Package: diffstat
Version: 1.55-3
Severity: normal
Diffstat tries to get the terminal width to auto-scale the histogram, but
the method it uses simply doesn't work, at least with bash.
The method it uses is getenv("COLUMNS"). Unfortunately, at least with bash,
the COLUMNS variable is normally a "magic" variable, it doesn't really exist
in the environment, and so diffstat always thinks the terminal is 80 chars
wide, which often results in forcing the histogram to only be its minimum 10
chars wide, no matter how big the terminal window is.
Workaround: export COLUMNS
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.6-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/bash
Versions of packages diffstat depends on:
ii libc6 2.13-37
diffstat recommends no packages.
diffstat 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#694547: gmpc: Doesn't show in Gnome applications list
Package: gmpc Version: 11.8.16-5 Severity: important The gmpc application no longer appears in the gnome applications menu. In the gnome menu editor, gmpc does appear in the (disabled) Debian menu hierarchy. Investigating a bit, it appears that /usr/share/applications/gmpc.desktop is slightly corrupt. There is a stray newline for the Name[ca] entry. The original source of that appears to be po/ca.po. Removing that newline from the desktop file causes gmpc to immediately re-appear in the applications list. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-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/bash Versions of packages gmpc depends on: ii gmpc-data 11.8.16-5 ii libc6 2.13-35 pn libcairo2 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-02.33.12+really2.32.4-3 ii libgtk2.0-0 2.24.10-2 ii libmpd1 0.20.0-1.1 ii libpango1.0-0 1.30.0-1 ii libsoup2.4-12.38.1-2 ii libsqlite3-03.7.13-1 ii libunique-1.0-0 1.1.6-4 ii libx11-62:1.5.0-1 ii libxml2 2.8.0+dfsg1-6 ii zlib1g 1:1.2.7.dfsg-13 gmpc recommends no packages. Versions of packages gmpc suggests: ii gmpc-plugins 11.8.16-1 pn mpd -- 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#684738: dh-make-drupal: drupal version specifier broken
Package: dh-make-drupal
Version: 1.1-1
Severity: important
Something in dh-make-drupal seems to have broken when trying to use the -d
or --drupal-version option to specify building for something other than the
default (now drupal 7).
For example:
$ dh-make-drupal -d 6 ctools
/usr/bin/dh-make-drupal:676:in `rescue in fetch_data': Could not open 6
/project website at http://drupal.org/project/6 (IOError)
from /usr/bin/dh-make-drupal:673:in `fetch_data'
from /usr/bin/dh-make-drupal:734:in `for'
from /usr/bin/dh-make-drupal:147:in `fetch_info'
from /usr/bin/dh-make-drupal:99:in `initialize'
from /usr/bin/dh-make-drupal:1106:in `new'
from /usr/bin/dh-make-drupal:1106:in `run'
from /usr/bin/dh-make-drupal:1120:in `'
$ dh-make-drupal ctools -d 6
/usr/bin/dh-make-drupal:789:in `choose': No suitable version found for
/Drupal true (level>=recommended) (EOFError)
from /usr/bin/dh-make-drupal:147:in `fetch_info'
from /usr/bin/dh-make-drupal:99:in `initialize'
from /usr/bin/dh-make-drupal:1106:in `new'
from /usr/bin/dh-make-drupal:1106:in `run'
from /usr/bin/dh-make-drupal:1120:in `'
This breaks tarball builds too:
$ dh-make-drupal -d 6 -t ctools-6.x-1.9.tar.gz -V 1.9 ctools
/usr/bin/dh-make-drupal:231:in `block in ck_orig_tarball': Downloaded file
/ctools-6.x-1.9.tar.gz has an unexpected directory hierarchy (ctools/
/(RuntimeError)
) - Aborting.
from /usr/bin/dh-make-drupal:225:in `map'
from /usr/bin/dh-make-drupal:225:in `ck_orig_tarball'
from /usr/bin/dh-make-drupal:179:in `initialize'
from /usr/bin/dh-make-drupal:1110:in `new'
from /usr/bin/dh-make-drupal:1110:in `run'
from /usr/bin/dh-make-drupal:1120:in `'
$ dh-make-drupal -t ctools-6.x-1.9.tar.gz -V 1.9 ctools -d 6
W: No list of core modules available for Drupal version true - Cannot infer
what to exclude, including everything.
dpkg-buildpackage: source package drupaltrue-mod-ctools
dpkg-buildpackage: source version 1.9-1
dpkg-buildpackage: source changed by Matthew Gabeler-Lee <>
dpkg-buildpackage: host architecture amd64
dpkg-source --before-build drupaltrue-mod-ctools-1.9
fakeroot debian/rules clean
dh clean
dh_testdir
dh_auto_clean
dh_clean
dpkg-source -b drupaltrue-mod-ctools-1.9
dpkg-source: error: can't build with source format '3.0 (quilt)': no
upstream tarball found at
../drupaltrue-mod-ctools_1.9.orig.tar.{bz2,gz,lzma,xz}
dpkg-buildpackage: error: dpkg-source -b drupaltrue-mod-ctools-1.9 gave
error exit status 255
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.3.5 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dh-make-drupal depends on:
ii build-essential 11.5
ii debhelper9.20120608
ii libruby 4.9
ii ruby 4.9
ii ruby-hpricot 0.8.6-3
ii ruby1.8 [ruby] 1.8.7.358-4
dh-make-drupal recommends no packages.
Versions of packages dh-make-drupal suggests:
ii drupal6 6.26-1.1
-- 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#685024: deborphan: orphaner fails with multiarch
Package: deborphan Version: 1.7.28.8 Severity: normal After enabling multi-arch in dpkg (mostly to get wine stuff working), deborphan / orphaner is not working properly. Instead of displaying just the package name as it would before, it now displays packagename:arch. When orphaner goes to try and remove such a package, it has issues, at least with arch=all packages. apt-get says it cannot find the package name. My best guess is that it is running apt-get remove packagename:arch, and apt- get appears not to like that, at least for arch=all, though if it's doing that for all packages, apt-get is OK with arch=amd64. I would presume that stripping the arch off what's passed to apt-get remove is dangerous, as a package could be orphaned for one arch but not another. Unless this is really a bug with apt-get, I guess orphaner needs to split up the packages to be removed in any pass by architecture and run apt-get once for each arch. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-3-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/bash Versions of packages deborphan depends on: ii libc6 2.13-33 Versions of packages deborphan recommends: ii apt 0.9.7.2 ii dialog1.1-20120215-2 ii gettext-base 0.18.1.1-9 deborphan 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#704689: gzip: Overwrite prompt always overwrites
Package: gzip Version: 1.5-1.1 Severity: important When run from a terminal, gzip will prompt the user whether they want to ovewrite the output file if it already exists. For some reason, which I have not yet been able to identify, the debian build always overwrites, no matter what the user says. Rebuilding gzip from source on my machine with DEB_BUILD_OPTIONS=noopt produces a binary that behaves correctly. Building it from source without that option produces a binary that fails. Since that suggests gcc might be part of the problem, my gcc version is: gcc (Debian 4.7.2-5) 4.7.2 -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gzip depends on: ii dpkg 1.16.10 ii install-info 4.13a.dfsg.1-10 ii libc6 2.13-38 gzip recommends no packages. Versions of packages gzip suggests: ii less 444-4 -- 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#694829: libtiff4 is not Multi-Arch compatible
Package: libtiff4 Version: 3.9.6-9 Severity: normal Installing libtiff4 in a multiarch environment (e.g. i386 on an amd64 native for me) fails: Unpacking libtiff4:i386 (from .../libtiff4_3.9.6-9_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libtiff4_3.9.6-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libtiff4/changelog.Debian.gz', which is different from other instances of package libtiff4:i386 -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6.4 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libtiff4 depends on: ii libc6 2.13-37 ii libjbig0 2.0-2 ii libjpeg8 8d-1 ii multiarch-support 2.13-37 ii zlib1g 1:1.2.7.dfsg-13 libtiff4 recommends no packages. libtiff4 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#259864: debget -a arch pkg
Package: debian-goodies Version: 0.61 Followup-For: Bug #259864 I was trying to use the "other" apt syntax for specifying an architecture (apt-get install packagename:arch), and it looks like debget gets most of the way there, it just needs some slightly smarter regex fu. $ debget libtiff4:amd64 (libtiff4:amd64 -> 3.9.6-9) < exits with error code 1, looks like it's because it runs with -e > $ ( set -x ; . /usr/bin/debget libtiff4:amd64 ) + . /usr/bin/debget libtiff4:amd64 ++ LC_ALL=C ++ '[' 1 -eq 0 ']' ++ case $1 in ++ set +e ++ apt-get -q2 --print-uris --reinstall install dpkg ++ '[' 0 -ne 0 ']' ++ ls --color=auto /var/lib/apt/lists/ ++ grep Release ++ set -e ++ for pkgspec in '$*' ++ set +e ++ apt-get -q2 --print-uris --reinstall install libtiff4:amd64 ++ '[' 0 -ne 0 ']' ++ set -e ++ apt-cache show libtiff4:amd64 ++ grep '^Ver' ++ read version +++ echo Version: 3.9.6-9 +++ sed -ne '$s/^.*: \(.*\).*$/\1/p' ++ version=3.9.6-9 ++ echo '(libtiff4:amd64 -> 3.9.6-9)' (libtiff4:amd64 -> 3.9.6-9) ++ read version +++ apt-get -q2 --print-uris --reinstall install libtiff4:amd64 +++ grep -F /libtiff4:amd64_ ++ aptdata= NB: apt-get -q2 --print-uris --reinstall install libtiff4:amd64 prints the correct URI, sort of: $ apt-get -q2 --print-uris --reinstall install libtiff4:amd64 'http://ftp.us.debian.org/debian/pool/main/t/tiff3/libtiff4_3.9.6-9_amd64.deb' libtiff4_3.9.6-9_amd64.deb 201908 MD5Sum:8665f1954dce043eae89908c3055e8a1 'http://ftp.us.debian.org/debian/pool/main/t/tiff3/libtiff4_3.9.6-9_i386.deb' libtiff4_3.9.6-9_i386.deb 200790 MD5Sum:b77f99baa7a74a7f570a3ca1c48d8005 NB2: My system is amd64 natively, I've run dpkg --add-architecture i386 and such to get multiarch going, as you can see from the info below. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6.8 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debian-goodies depends on: ii curl 7.26.0-1 ii dctrl-tools [grep-dctrl] 2.22.2 ii dialog1.1-20120215-2 ii perl 5.14.2-15 ii python2.7.3~rc2-1 ii whiptail 0.52.14-10 Versions of packages debian-goodies recommends: ii lsof 4.86+dfsg-1 Versions of packages debian-goodies suggests: ii popularity-contest 1.56 ii xdg-utils 1.1.0~rc1+git20111210-6 ii zenity 3.4.0-2 -- 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#694829: libtiff4 is not Multi-Arch compatible
On Mon, 3 Dec 2012, Jay Berkenbilt wrote: Can you double check to make sure that you are installing the same version for amd64 and i386? It looks like the version you have for amd64 might be different from the version you are trying to install on i386. $ sudo apt-get remove libtiff4:i386 ... $ apt-show-versions |grep libtiff4 libtiff4/testing uptodate 3.9.6-9 $ sudo apt-get install libtiff4:i386=3.9.6-9 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: libtiff4:i386 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/201 kB of archives. After this operation, 514 kB of additional disk space will be used. (Reading database ... 169041 files and directories currently installed.) Unpacking libtiff4:i386 (from .../libtiff4_3.9.6-9_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libtiff4_3.9.6-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libtiff4/changelog.Debian.gz', which is different from other instances of package libtiff4:i386 Errors were encountered while processing: /var/cache/apt/archives/libtiff4_3.9.6-9_i386.deb Hmm ... $ $ $ md5sum libtiff*/usr/share/doc/libtiff4/changelog.Debian.gz 69013408b8c415bbfcfebebb442afae3 libtiff4_3.9.6-9_amd64/usr/share/doc/libtiff4/changelog.Debian.gz 69013408b8c415bbfcfebebb442afae3 libtiff4_3.9.6-9_i386/usr/share/doc/libtiff4/changelog.Debian.gz $ md5sum /usr/share/doc/libtiff4/changelog.Debian.gz e92a8f99ac326b5ce23231fa83907fd5 /usr/share/doc/libtiff4/changelog.Debian.gz Hmm ... $ sudo apt-get --reinstall install libtiff4:amd64 ... $ md5sum /usr/share/doc/libtiff4/changelog.Debian.gz 69013408b8c415bbfcfebebb442afae3 /usr/share/doc/libtiff4/changelog.Debian.gz $ sudo apt-get install libtiff4:i386 I have no idea how the changelog file had the wrong content, even though apt thought it was the same version, but you're right, this was an error in my installation somehow. -- -Matt "Reality is that which, when you stop believing in it, doesn't go away". -- Philip K. Dick GPG pubkey fingerprint: A57F B354 FD30 A502 795B 9637 3EF1 3F22 A85E 2AD1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706097: coreutils: chmod --recursive --changes fails to stat items in subdirectories
Package: coreutils Version: 8.20-3 Severity: normal Tags: upstream Under some circumstances, combining the --recursive and --changes arguments to chmod can cause it to report errors checking the new permissions of subdirectories. Test case: $ cd /tmp $ mkdir -p a/b $ chmod -R g+s a $ chmod -Rc o-rwx a mode of `a' changed from 2755 (rwxr-sr-x) to 2750 (rwxr-s---) chmod: getting new attributes of `b': No such file or directory The problem lies in src/chmod.c, function mode_changed, line ~123, the call to stat. The file path passed is just the filename, not the recursive path, and so the stat call fails. A more subtle error happens if the filename is valid in the current directory from which chmod is invoked, since it will then be comparing the mode bits of two unrelated items. All other calls to stat and chmod related functions use the *at variants that take a directory fd for path resolution. This call needs to be updated to do the same. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.5 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages coreutils depends on: ii dpkg 1.16.10 ii install-info 4.13a.dfsg.1-10 ii libacl1 2.2.51-8 ii libattr1 1:2.4.46-8 ii libc6 2.13-38 ii libselinux1 2.1.9-5 coreutils recommends no packages. coreutils 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#710275: postgresql-9.1: Needs restart on libc upgrade
Package: postgresql-9.1 Version: 9.1.9-1 Severity: important When upgrading libc6, it appears that postgresql is one of the services that needs to be restarted for authentication to work properly. After updating libc6 from 2.13 to 2.17 (testing), I was unable to authenticate to my databases until I restarted postgresql. After a restart, all was fine. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages postgresql-9.1 depends on: ii libc6 2.17-3 ii libcomerr2 1.42.5-1.1 ii libgssapi-krb5-2 1.10.1+dfsg-5 ii libkrb5-3 1.10.1+dfsg-5 ii libldap-2.4-2 2.4.31-1+nmu2 ii libpam0g 1.1.3-9 ii libpq5 9.1.9-1 ii libssl1.0.01.0.1e-2 ii libxml22.8.0+dfsg1-7+nmu1 ii locales2.17-3 ii postgresql-client-9.1 9.1.9-1 ii postgresql-common 134wheezy3 ii ssl-cert 1.0.32 ii tzdata 2013b-2 postgresql-9.1 recommends no packages. Versions of packages postgresql-9.1 suggests: pn locales-all ii oidentd [ident-server] 2.0.8-5 -- 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#702715: tortoisehg: broken pyqt4 version check
Package: tortoisehg Version: 2.4-2 Severity: grave Followup-For: Bug #702715 This bug has now "landed". As the packages in testing / unstable now stand, you cannot use tortoisehg. Even worse, for reasons I cannot quite understand, it does not print any error message about this situation, nor does it even exit with a failure code, which will leave many users very confused. There is code to print an error message, but it never makes it out to the console. I cannot test the version of tortoisehg in experimental, because it is not compatible with any packaged version of mercurial (the version in unstable is too old, and the version in experimental is too new). I was able to manually patch /usr/share/pyshared/tortoisehg/hgqt/qtlib.py using information from the upstream ticket to fix the issue, specifically applying an equivalent change to https://bitbucket.org/tortoisehg/thg/commits/e571f9b3eadc. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tortoisehg depends on: ii mercurial 2.2.2-3 ii python 2.7.3-5 ii python-gobject 3.8.2-1 ii python-qscintilla2 2.7.1-1 ii python-qt4 4.10.1-1 Versions of packages tortoisehg recommends: ii libjs-jquery 1.7.2+dfsg-2 ii libjs-underscore 1.1.6-1+deb7u1 pn python-iniparse pn python-pygments Versions of packages tortoisehg suggests: pn tortoisehg-nautilus -- 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#703998: debsecan: Don't report on already installed fixes
Package: debsecan Version: 0.4.16+nmu1 Severity: wishlist Today debsecan alerted me about CVE-2013-1824 (a php5 issue). Based on the PTS page for php5 and my system update schedule, I can say with near certainty that I installed the fixed version of php5 more than two weeks before it sent the report. Even if I'm mistaken on the two weeks, I certainly had installed the fixed version before the report was generated. When running with --only-fixed, it would be much more useful to tell me about fixes I have not yet installed than about fixes I installed some time ago. As it stands, between this and #588065, the signal to noise ratio on debsecan's reports is so low as to make it nearly useless for me. At the very least, it is important to have the report differentiate between installed fixes and available but not yet installed fixes. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages debsecan depends on: ii debconf [debconf-2.0] 1.5.49 ii python 2.7.3-4 ii python-apt 0.8.8.2 Versions of packages debsecan recommends: ii cron 3.0pl1-124 ii exim4 4.80-7 ii exim4-daemon-light [mail-transport-agent] 4.80-7 debsecan suggests no packages. -- debconf information: * debsecan/source: * debsecan/mailto: root * debsecan/suite: wheezy * debsecan/report: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703998: debsecan: Don't report on already installed fixes
On 2013-03-26 14:27, Florian Weimer wrote: * Matthew Gabeler-Lee: Today debsecan alerted me about CVE-2013-1824 (a php5 issue). Based on the PTS page for php5 and my system update schedule, I can say with near certainty that I installed the fixed version of php5 more than two weeks before it sent the report. Even if I'm mistaken on the two weeks, I certainly had installed the fixed version before the report was generated. The fact that CVE-2013-1824 was fixed in an older DSA was only recorded yesterday. As a a result, there was an unfixed -> fixed transition. I suppose it should be possible to suppress reporting it in cases where the version number does not actually change. If I'm understanding what you're saying correctly (not quite sure I am), I'm a little worried that it might cause an alert to be suppressed even when a vulnerable version is still installed. The alternate method I'm suggesting is to suppress reports for unfixed->fixed if the installed version is >= the fixed version. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701140: dh-make-perl: Patch to understand packages named -vX.Y.Z
Package: dh-make-perl
Version: 0.75-1
Severity: important
Tags: patch
dh-make-perl doesn't seem to understand packages that have a name like
Foo-Bar-v1.0.0, only ones named Foo-Bar-1.0.0. Attached tiny patch fixes
this.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.7.4 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dh-make-perl depends on:
ii debhelper 9.20120909
ii dpkg-dev1.16.9
ii fakeroot1.18.4-2
ii libapt-pkg-perl 0.1.26+b1
ii libarray-unique-perl0.08-1
ii libclass-accessor-perl 0.34-1
ii libdpkg-perl1.16.9
ii libemail-address-perl 1.895-1
ii libemail-date-format-perl 1.002-1
ii libfile-which-perl 1.09-1
ii liblist-moreutils-perl 0.33-1+b1
ii libmodule-depends-perl 0.16-1
ii libparse-debcontrol-perl2.005-3
ii libparse-debianchangelog-perl 1.2.0-1
ii libsoftware-license-perl0.103004-2
ii libtie-ixhash-perl 1.21-2
ii libwww-mechanize-perl 1.71-1
ii libyaml-perl0.81-1
ii make3.81-8.2
ii perl5.14.2-18
ii perl-modules [libmodule-corelist-perl] 5.14.2-18
Versions of packages dh-make-perl recommends:
ii apt-file 2.5.1
ii git 1:1.7.10.4-1+wheezy1
pn pristine-tar
dh-make-perl suggests no packages.
-- no debconf information
diff --git a/lib/DhMakePerl/Command/make.pm b/lib/DhMakePerl/Command/make.pm
index 4ce91d4..68092ba 100644
--- a/lib/DhMakePerl/Command/make.pm
+++ b/lib/DhMakePerl/Command/make.pm
@@ -272,7 +272,7 @@ sub setup_dir {
}
elsif ( $dist = find_cpan_distribution( $self->cfg->cpan ) ) {
my $ver;
-if ( $dist->base_id =~ /-(\d[\d._]*)\./ ) {
+if ( $dist->base_id =~ /-v?(\d[\d._]*)\./ ) {
$self->mod_cpan_version($1);
}
else {
Bug#701140: dh-make-perl: Patch to understand packages named -vX.Y.Z
On 2013-02-22 08:41, gregor herrmann wrote: On Thu, 21 Feb 2013 20:31:39 -0500, Matthew Gabeler-Lee wrote: dh-make-perl doesn't seem to understand packages that have a name like Foo-Bar-v1.0.0, only ones named Foo-Bar-1.0.0. Attached tiny patch fixes this. Thanks for your bug report and patch. This sounds all reasonable; what surprises me a bit is that I never encountered this issue. Do you happen to remember which CPAN dist and which dh-make-perl invocation triggered this bug? Indeed I do: Net-BitTorrent-Protocol-v1.0.0 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701140: dh-make-perl: Patch to understand packages named -vX.Y.Z
On 2013-02-22 10:58, gregor herrmann wrote: Summary: 1) I'm confused :) 2) The errors come from git, and we really seem to have a version problem somewhere. Not sure if this is the problem you are facing. 3) Could you please provide the dh-make-perl invocation and output on your system, maybe then it gets clearer ... I was using cpan2deb, but it didn't seem from the man page like it should make a difference. Clearly it does, however. I have 0.75 from /testing here, I (foolishly?) thought 0.76 wouldn't be that much different. With that version, I get this: $ cpan2deb Net-BitTorrent-Protocol Going to read '/usr/src/build/cpan/Metadata' Database was generated on Thu, 21 Feb 2013 21:17:02 GMT Going to read 1 yaml file from /usr/src/build/cpan/build/ CPAN: Time::HiRes loaded ok (v1.972101) DONE Restored the state of none (in 0.0987 secs) Unable to determine the version of Net-BitTorrent-Protocol-v1.0.0 My patch fixes (for me) that error in the last line and let me build a .deb. But, if I use "dh-make-perl --cpan" instead of "cpan2deb", I get output equivalent to yours. If I use "dh-make-perl --build --cpan", I get the output with the git complaint, but the package does build. Now I'm confused ;) Hopefully something here helps you be less confused. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701717: getmail4: New upstream release (4.39.0)
Package: getmail4 Version: 4.32.0-2 Severity: wishlist There is a new upstream release which addresses several (to me) important issues. Most notably, it makes getmail behave rationally when interrupted via Ctrl-C. Also, it looks like it should contain a fix for #513116 (see the release notes for 4.38.0). There are several other desirable new features in the intervening releases, which are especially useful to anyone trying to use getmail to backup a full IMAP account with folder structure, esp. a GMail account. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.7.4 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages getmail4 depends on: ii python 2.7.3-4 getmail4 recommends no packages. getmail4 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#702977: tt-rss: Missing Depends: libphp-simplepie
Package: tt-rss Version: 1.7.2+dfsg-1 Severity: grave Justification: renders package unusable tt-rss needs simplepie to do anything with RSS feeds, AFAICT. But the package does not have a Depends, or even a Recommends or Suggests on libphp-simplepie. Without that package, I cannot subscribe to or download any feeds. Doing anything like that produces errors like this in the apache error log: PHP Fatal error: require_once(): Failed opening required 'lib/simplepie/simplepie.inc' (include_path='/usr/share/tt-rss/www/include:.:/usr/share/php:/usr/share/pear') in /usr/share/tt-rss/www/include/rssfuncs.php on line 167, -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tt-rss depends on: ii dbconfig-common1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.49 ii libjs-dojo-core1.7.2+dfsg-1 ii libjs-dojo-dijit 1.7.2+dfsg-1 ii libjs-scriptaculous1.9.0-2 ii libphp-phpmailer 5.1-1 ii php-gettext1.0.11-1 ii php5 5.4.4-14 ii php5-cli 5.4.4-14 ii php5-mysql 5.4.4-14 ii php5-pgsql 5.4.4-14 Versions of packages tt-rss recommends: ii apache2 2.2.22-13 ii apache2-mpm-prefork [httpd] 2.2.22-13 ii lighttpd [httpd] 1.4.31-3 ii php5-gd 5.4.4-14 Versions of packages tt-rss suggests: ii mysql-client 5.5.28+dfsg-1 ii mysql-client-5.5 [mysql-client]5.5.28+dfsg-1 ii mysql-server 5.5.28+dfsg-1 ii postgresql-client-9.1 [postgresql-client] 9.1.8-1 pn sphinxsearch -- Configuration Files: /etc/default/tt-rss changed [not included] /etc/tt-rss/config.php changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#707212: logrotate script error
Package: tt-rss Version: 1.7.8+dfsg-2 Followup-For: Bug #707212 Also, the logrotate script doesn't send output to /dev/null, so it will spam the administrator every day. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tt-rss depends on: ii dbconfig-common1.8.47+nmu1 ii debconf [debconf-2.0] 1.5.49 ii libapache2-mod-php55.4.4-15 ii libjs-dojo-core1.7.2+dfsg-1 ii libjs-dojo-dijit 1.7.2+dfsg-1 ii libjs-scriptaculous1.9.0-2 ii libphp-phpmailer 5.1-1 ii libphp-simplepie 1.2.1-3 ii php-gettext1.0.11-1 ii php5 5.4.4-15 ii php5-cli 5.4.4-15 ii php5-mysql 5.4.4-15 ii php5-pgsql 5.4.4-15 ii phpqrcode 1.1.4-1 Versions of packages tt-rss recommends: ii apache2 2.2.22-13 ii apache2-mpm-prefork [httpd] 2.2.22-13 ii lighttpd [httpd] 1.4.31-4 ii php5-gd 5.4.4-15 Versions of packages tt-rss suggests: ii mysql-client 5.5.30+dfsg-1.1 ii mysql-client-5.5 [mysql-client]5.5.30+dfsg-1.1 ii mysql-server 5.5.30+dfsg-1.1 ii php-apc3.1.13-1 ii postgresql-client-9.1 [postgresql-client] 9.1.9-1 pn sphinxsearch -- Configuration Files: /etc/default/tt-rss changed [not included] /etc/logrotate.d/tt-rss changed [not included] /etc/tt-rss/apache.conf changed [not included] /etc/tt-rss/config.php changed [not included] -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#625917: drupal7
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#639964: apt: regression from 0.8.15.5: sources with no component give error processing Release file
Package: apt Version: 0.8.15.6 Severity: important As of apt 0.8.15.6, sources.list entries that use the "deb http://... path/" format instead of the "deb http://... release component" format fail (for me). For example, I have the following entries in my sources.list: deb-src http://iguanaworks.net/downloads/debian source/ deb http://iguanaworks.net/downloads/debian binary-amd64/ With apt 0.8.15.5, apt-get update reports no errors. With apt 0.8.15.6, I get these errors: W: Failed to fetch http://iguanaworks.net/downloads/debian/source/Release Unable to find expected entry 'Sources' in Release file (Wrong sources.list entry or malformed file) W: Failed to fetch http://iguanaworks.net/downloads/debian/binary-amd64/Release Unable to find expected entry 'Packages' in Release file (Wrong sources.list entry or malformed file) The latter Release file currently looks like this: Archive: karmic Component: contrib Origin: IguanaWorks Label: IguanaWorks Debian/Ubuntu Repository Architecture: amd64 Which is the same set of keys that the ftp.us.debian.org Release file(s) have AFAICT. >From searching around, I'm wondering if this may be related to an older (fixed) bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622250 -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "0"; APT::Install-Suggests "0"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image.*"; APT::NeverAutoRemove:: "^kfreebsd-image.*"; APT::NeverAutoRemove:: "^linux-restricted-modules.*"; APT::NeverAutoRemove:: "^linux-ubuntu-modules-.*"; APT::NeverAutoRemove:: "^gnumach$"; APT::NeverAutoRemove:: "^gnumach-image.*"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Never-MarkAuto-Sections:: "oldlibs"; APT::Never-MarkAuto-Sections:: "restricted/oldlibs"; APT::Never-MarkAuto-Sections:: "universe/oldlibs"; APT::Never-MarkAuto-Sections:: "multiverse/oldlibs"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::Default-Release "testing"; APT::Architectures ""; APT::Architectures:: "amd64"; Dir "/"; Dir::State "var/lib/apt/"; Dir::State::lists "lists/"; Dir::State::cdroms "cdroms.list"; Dir::State::mirrors "mirrors/"; Dir::State::extended_states "extended_states"; Dir::State::status "/var/lib/dpkg/status"; Dir::Cache "var/cache/apt/"; Dir::Cache::archives "archives/"; Dir::Cache::srcpkgcache "srcpkgcache.bin"; Dir::Cache::pkgcache "pkgcache.bin"; Dir::Etc "etc/apt/"; Dir::Etc::sourcelist "sources.list"; Dir::Etc::sourceparts "sources.list.d"; Dir::Etc::vendorlist "vendors.list"; Dir::Etc::vendorparts "vendors.list.d"; Dir::Etc::main "apt.conf"; Dir::Etc::netrc "auth.conf"; Dir::Etc::parts "apt.conf.d"; Dir::Etc::preferences "preferences"; Dir::Etc::preferencesparts "preferences.d"; Dir::Etc::trusted "trusted.gpg"; Dir::Etc::trustedparts "trusted.gpg.d"; Dir::Bin ""; Dir::Bin::methods "/usr/lib/apt/methods"; Dir::Bin::dpkg "/usr/bin/dpkg"; Dir::Media ""; Dir::Media::MountPath "/media/apt"; Dir::Log "var/log/apt"; Dir::Log::Terminal "term.log"; Dir::Log::History "history.log"; Dir::Ignore-Files-Silently ""; Dir::Ignore-Files-Silently:: "~$"; Dir::Ignore-Files-Silently:: "\.disabled$"; Dir::Ignore-Files-Silently:: "\.bak$"; Dir::Ignore-Files-Silently:: "\.dpkg-[a-z]+$"; Acquire ""; Acquire::cdrom ""; Acquire::cdrom::mount "/media/cdrom/"; Acquire::http ""; Acquire::http::timeout "10"; Acquire::ftp ""; Acquire::ftp::timeout "10"; Acquire::Retries "3"; Acquire::Languages ""; Acquire::Languages:: "en"; Acquire::Languages:: "none"; DPkg ""; DPkg::Pre-Install-Pkgs ""; DPkg::Pre-Install-Pkgs:: "/usr/sbin/dpkg-preconfigure --apt || true"; DPkg::Post-Invoke ""; DPkg::Post-Invoke:: "if [ -x /usr/sbin/localepurge ] && [ $(ps w -p $PPID | grep -c remove) != 1 ]; then /usr/sbin/localepurge; else exit 0; fi"; CommandLine ""; CommandLine::AsString "apt-config dump"; -- (no /etc/apt/preferences present) -- -- /etc/apt/sources.list -- # testing deb http://ftp.us.debian.org/debian/ testing main non-free contrib deb-src http://ftp.us.debian.org/debian/ testing main non-free contrib # unstable deb http://ftp.us.debian.org/debian/ unstable main non-free contrib deb-src http://ftp.us.debian.org/debian/ unstable main non-free contrib # experimental #deb http://ftp.us.debian.org/debian/ experimental main non-free contrib #deb-src http://ftp.us.debian.org/debian/ experimental main non-free contrib # security/testing (usually dead) #deb http://security.debian.org/ testing/updates main contrib non-free #deb-src http://security.debian.org/ testing/updates main contrib non-free # media packages deb http://www.debian-multimedia.or
Bug#714279: fontconfig-config: Not correct view anti-aliasing fonts and incorrect visualization.
Package: fontconfig-config Version: 2.10.2-2 Followup-For: Bug #714279 I encountered the same problems. By fiddling some configuration bits, I was able to restore the previous "good" font rendering: 1. Fix the symlink for /etc/fonts/conf.d/11-lcdfilter-default.conf (it was pointing to /etc/fonts/conf.avail/, but the file is now in /usr/share/fontconfig/conf.avail/. 2. Change "append" back to "assign" in contradiction to the comments in 10-autohint.conf, 10-subpixel-rgb.conf, and 11-lcdfilter-default.conf. 3. Run fc-cache -f and restart apps to get new configuration to be fully active. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fontconfig-config depends on: ii debconf [debconf-2.0] 1.5.50 ii fonts-freefont-ttf [ttf-freefont] 20120503-1 ii gsfonts-x110.22 ii ttf-bitstream-vera 1.10-8 ii ttf-dejavu-core2.33+svn2514-3 ii ttf-freefont 20120503-1 ii ucf3.0027 fontconfig-config recommends no packages. fontconfig-config suggests no packages. -- debconf information: * fontconfig/subpixel_rendering: Always * fontconfig/enable_bitmaps: false * fontconfig/hinting_type: Native -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#716664: Grive needs updating to 0.3.0
Package: grive Version: 0.2.0-1 Followup-For: Bug #716664 If you check GitHub and the main grive website carefully, you'll notice that 0.3.0 is not a finalized release yet. That said, it would be nice to have a pre-release snapshot from github available, at least in /experimental, since the new version appears to have numerous bug fixes and improvements. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717778: checkinstall: mkdir -p fails (fstrans broken again?)
Package: checkinstall Version: 1.6.2-4 Severity: important If a make install step does a mkdir -p that needs to create multiple directories, it fails, every time. This breaks using checkinstall with quite a lot of packages. Demonstrating this needs only a 2 line Makefile as a "package": install: mkdir -p /usr/local/bug/bug/bug The resulting error: = Installation results === mkdir -p /usr/local/bug/bug/bug mkdir: cannot create directory `/usr/local/bug': No such file or directory make: *** [install] Error 1 As with prior instances of similar bugs (at least similar symptomatically), this can be worked around by using --fstrans=no. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages checkinstall depends on: ii dpkg-dev 1.16.10 ii file 1:5.14-2 ii libc6 2.17-7 Versions of packages checkinstall recommends: ii make 3.81-8.2 Versions of packages checkinstall suggests: ii gettext 0.18.2.1-1 -- 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#718428: completion: diff -c should trigger labels
Package: mercurial Version: 2.6.2-1 Severity: minor Invoking completion after the -c argument to diff should invoke the labels (branches, tags, bookmarks, ...) completion, not file completion as it does now. Not sure if other mercurial commands have an equivalent -c argument, diff is the only one that comes to mind. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages mercurial depends on: ii libc6 2.17-7 ii mercurial-common 2.6.2-1 ii python2.7.5-2 ii ucf 3.0027+nmu1 Versions of packages mercurial recommends: ii openssh-client 1:6.2p2-6 Versions of packages mercurial suggests: pn kdiff3 | kdiff3-qt | kompare | meld | tkcvs | mgdiff pn qct ii tk8.4 [wish] 8.4.20-1 ii tk8.5 [wish] 8.5.14-2 ii vim 2:7.3.923-3 -- 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#715482: gnome-calculator: (Wrong calculation results!) `Malformed expression' after changing number bases.
Package: gnome-calculator Version: 3.8.2-1 Followup-For: Bug #715482 The first bug (which is driving me batsh*t crazy) appears to have been fixed upstream between 3.9.4 and 3.9.90, based on some quick testing of building upstream source from git. The only functional change between those two releases is: https://git.gnome.org/browse/gnome-calculator/commit/?id=917faf -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gnome-calculator depends on: ii dconf-gsettings-backend [gsettings-backend] 0.16.1-1 ii libatk1.0-0 2.8.0-2 ii libc62.17-92 ii libglib2.0-0 2.36.4-1 ii libgtk-3-0 3.8.2-3 ii libpango-1.0-0 1.32.5-5+b1 ii libxml2 2.9.1+dfsg1-3 Versions of packages gnome-calculator recommends: ii gnome-icon-theme 3.8.2-2 ii gvfs 1.16.3-1 pn yelp gnome-calculator 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#725755: php-wikidiff2: Incomplete / incorrect php.ini installation
Package: php-wikidiff2 Version: 0.0.1+svn109581-1+b1 Severity: important php-wikidiff2 installs its php.ini snippet into /etc/php5/conf.d, but the common usage of it with mediawiki and apache does not read this directory. It should be putting the ini snippet in /etc/php5/mods-available and then a symlink in /etc/php5/apache2/conf.d -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#725980: geoip-database-contrib: Cron job should be quieter
Package: geoip-database-contrib Version: 1.13 Severity: wishlist The cron job installed by geoip-database-contrib mails the full wget output, including the (long) download progress. This seems a bit excessive. I see two options: 1) The cron entry sends stdout to /dev/null, but not stderr. It could send both to /dev/null. 2) Pass an argument to the update script to tell it to be quiet, which it would in turn pass to wget. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-2-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages geoip-database-contrib depends on: ii debconf [debconf-2.0] 1.5.51 ii dpkg 1.16.10 ii ucf3.0027+nmu1 ii wget 1.14-2 geoip-database-contrib recommends no packages. Versions of packages geoip-database-contrib suggests: ii cron 3.0pl1-124 -- debconf information: * geoip-database-contrib/install-cronjob: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#721752: isc-dhcp-server: Always listens on all interfaces
Package: isc-dhcp-server Version: 4.2.4-7 Severity: normal It seems that the isc-dhcp-server daemon always listens for dhcp requests on all interfaces, even when given a specific interface to bind to. The dnsmasq program appears to have the same bug. The result is that having a dhcp server for a local physical subnet cannot co-exist with virtual subnets created by libvirt, and now I can either have network access for my VMs, or network access for my physical devices, but not both. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages isc-dhcp-server depends on: ii debconf [debconf-2.0] 1.5.50 ii debianutils4.4 ii isc-dhcp-common4.2.4-7 ii libc6 2.17-92 ii lsb-base 4.1+Debian12 isc-dhcp-server recommends no packages. Versions of packages isc-dhcp-server suggests: pn isc-dhcp-server-ldap -- Configuration Files: /etc/dhcp/dhcpd.conf changed [not included] -- debconf information: isc-dhcp-server/config_warn: * isc-dhcp-server/interfaces: eth1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#721751: dnsmasq-base: Always listens on all interfaces
Package: dnsmasq-base Version: 2.66-4 Severity: normal It seems that the dnsmasq daemon always listens for dhcp requests on all interfaces, even when given a specific interface to bind to. The isc-dhcp-server program appears to have the same bug. The result is that having a dhcp server for a local physical subnet cannot co-exist with virtual subnets created by libvirt, and now I can either have network access for my VMs, or network access for my physical devices, but not both. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dnsmasq-base depends on: ii adduser 3.113+nmu3 ii libc62.17-92 ii libdbus-1-3 1.6.12-1 ii libidn11 1.28-1 ii libnetfilter-conntrack3 1.0.4-1 ii libnfnetlink01.0.1-2 dnsmasq-base recommends no packages. dnsmasq-base 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#722534: vnstat: Provide /etc/network/if-*.d script(s) to avoid counter problems
Package: vnstat Version: 1.11-2 Severity: wishlist vnstat has some documented issues around what happens when an interface is brought down and then back up, and it has some options (I think mostly the --reset option) to help deal with this. It would be nice if there were /etc/network/if-*.d (not sure which one is appropriate) that made the appropriate vnstat calls to deal with this. My scenario: I cycled a bridge interface, and ended up with millions of terabytes (2^24 I believe) of traffic recorded for that moment on that interface. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages vnstat depends on: ii adduser 3.113+nmu3 ii libc62.17-92+b1 vnstat recommends no packages. Versions of packages vnstat suggests: ii vnstati 1.11-2 -- Configuration Files: /etc/vnstat.conf changed [not included] -- 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#720051: unrar-nonfree: Please bring back libunrar, possibly add sfx
Source: unrar-nonfree Version: 1:5.0.10-1 Severity: normal With the update to unrar 5.0, the libunrar package appears to be gone. Please bring it back :) Packaging the output of the sfx target might be useful too. NB: to build the lib for 5.0, I had to add -fPIC to the compile flags. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#723620: mediawiki: Default installation does not work (Apache 2.4 problem)
Package: mediawiki Version: 1:1.19.8+dfsg-1 Severity: important Dear Maintainer, * What led up to the situation? Installed clean new Debian wheezy system. Installed Apache 2.4 with default options. Installed mediawiki with default options. Enabled mediawiki apache configuration, including alias configuration. Attempted to access http://localhost/mediawiki/ * What was the outcome of this action? Attempting to access the page produces a 403 Forbidden error, and this message in the apache error log: AH01630: client denied by server configuration: /var/lib/mediawiki/ * What outcome did you expect instead? Default install should work! * What exactly did you do (or not do) that was effective (or ineffective)? The problem seems to do with the change in syntax for Apache 2.4 allow/deny rules. Prior bug#669832 mentions a fix that worked for me (change in the allow/deny syntax in /etc/mediawiki/apache.conf). However, that bug was marked closed without such a fix being applied to the mediawiki package. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#723622: php-wikidiff2: Configuration sent as output instead of executing
Package: php-wikidiff2 Version: 0.0.1+svn109581-1+b1 Severity: important Using a default installation of Debian testing, with Apache 2.4, the contents of /etc/mediawiki-extensions/extensions-available/wikidiff2.php are being sent as output instead of executing. AFAICT, this is because the file starts with "
Bug#723669: gptsync: Doesn't understand linux filesystem gpt partition type
Package: gptsync Version: 0.14-2 Severity: normal gptsync doesn't understand gpt partitions with code 8300 / guid 0FC63DAF-8483-4772-8E79-3D69D8477DE4, the linux filesystem type. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages gptsync depends on: ii libc6 2.17-92+b1 gptsync recommends no packages. gptsync 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#723620: [Pkg-mediawiki-devel] Bug#723620: mediawiki: Default installation does not work (Apache 2.4 problem)
Thorsten Glaser wrote: >On Tue, 17 Sep 2013, Matthew Gabeler-Lee wrote: > >> The problem seems to do with the change in syntax for Apache 2.4 >allow/deny >> rules. Prior bug#669832 mentions a fix that worked for me (change in >the >> allow/deny syntax in /etc/mediawiki/apache.conf). However, that bug >was >> marked closed without such a fix being applied to the mediawiki >package. > >Hm, people told me it was enough. But I have got an idea. > >Can you please run: > >$ sudo a2enmod access_compat > >Then try again? If that helps, I’ll just call that from >the postinst maintainer script, like we do in FusionForge. First thing I checked, but that module was already enabled, I think by the default install, or possibly by phpmyadmin, which was the only other apache package I had installed at that point. This is not the first time I've seen access_compat fail to work as expected, though I'm not sure if that's a bug, or a limitation in the module. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#723620: [Pkg-mediawiki-devel] Bug#723620: mediawiki: Default installation does not work (Apache 2.4 problem)
Thorsten Glaser wrote: >On Tue, 17 Sep 2013, Matthew Gabeler-Lee wrote: > >> The problem seems to do with the change in syntax for Apache 2.4 >allow/deny >> rules. Prior bug#669832 mentions a fix that worked for me (change in >the >> allow/deny syntax in /etc/mediawiki/apache.conf). However, that bug >was >> marked closed without such a fix being applied to the mediawiki >package. > >Hm, people told me it was enough. But I have got an idea. > >Can you please run: > >$ sudo a2enmod access_compat > >Then try again? If that helps, I’ll just call that from >the postinst maintainer script, like we do in FusionForge. First thing I checked, but that module was already enabled, I think by the default install, or possibly by phpmyadmin, which was the only other apache package I had installed at that point. This is not the first time I've seen access_compat fail to work as expected, though I'm not sure if that's a bug, or a limitation in the module. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#723620: [Pkg-mediawiki-devel] Bug#723620: mediawiki: Default installation does not work (Apache 2.4 problem)
On 2013-09-19 05:30, Thorsten Glaser wrote: On Thu, 19 Sep 2013, Thorsten Glaser wrote: Since the bug occurs for you but not for me, can you try … or actually, try the attached file, jmw already committed something. Yup, that works, which is no surprise since it's exactly what I did to fix it manually, with the added version conditionals to support older apache versions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714216: zenity: Manpage gives incorrect list of available window icons
Package: zenity Version: 3.8.0-1 Severity: minor Tags: upstream >From the manpage: --window-icon=ICONPATH Set the window icon with the path to an image. Alternatively, one of the four stock icons can be used: 'error', 'info', 'ques‐ tion' or 'warning' In fact, the list of valid stock icons comes from libnotify, and can be found in the freedesktop.org specifications at: http://standards.freedesktop.org/icon-naming-spec/icon-naming-spec-latest.html The 'error' value seems to be mapped to dialog-error, but none of the other stock icon names in the manpage seem to work (a default / fallback icon is used), while their dialog-foo counterpart does. I spot checked several other stock icons (using the --notification mode) from the freedesktop.org spec, and all of them worked too. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.2 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages zenity depends on: ii libc6 2.17-3 ii libgdk-pixbuf2.0-0 2.28.2-1 ii libglib2.0-02.36.1-2build1 ii libgtk-3-0 3.4.2-6 ii libnotify4 0.7.5-2 ii libpango-1.0-0 1.32.5-5+b1 ii libwebkitgtk-3.0-0 1.8.1-3.4 ii libx11-62:1.6.0-1 ii zenity-common 3.8.0-1 zenity recommends no packages. zenity 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#675299: bash-completion: sudo -u should complete usernames
Package: bash-completion Version: 1:1.99-3 Severity: normal Completion for sudo should understand some of sudo's options, most importantly (for me), the -u option. sudo -u completes commands as if the -u was not there. Following on from that, sudo -u user doesn't complete commands, and sudo -u user command doesn't do completion for the command. Ideally most or all of sudo's options should be understood, or at least the ones that take an argument recognized as such so that they don't break command completion later on the command line. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.3.5 (SMP w/12 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages bash-completion depends on: ii bash 4.2-2 bash-completion recommends no packages. bash-completion 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#799784: network-manager: VPN connect timer kills reconnect after password fail
Package: network-manager Version: 1.0.6-1 Severity: normal I'm experiencing this with network-manager-openvpn, but a quick grep through the source suggests it is a bug in the core network-manager vpn support and not in the openvpn plugin itself. Scenario: * Start a VPN connection that requires entering secrets (e.g. openvpn with the PAM plugin on the server) * Accidentally fat-finger the password * Reconnect immediately and type the password correctly this time * Wait a minute and watch NM kill the successfully started VPN Syslog: Starting the connection and fat fingering the password: Sep 22 09:50:23 xyzzy NetworkManager[848]: (nm-openvpn-service:20864): nm-openvpn-WARNING **: (nm-openvpn-service.c:1269):nm_openvpn_start_openvpn_binary: runtime check failed: (priv->mgt_path == NULL) Sep 22 09:50:23 xyzzy NetworkManager[848]: VPN plugin state changed: starting (3) Sep 22 09:50:23 xyzzy NetworkManager[848]: nm-openvpn-Message: openvpn started with pid 22961 Sep 22 09:50:23 xyzzy NetworkManager[848]: VPN connection 'xyzzy' (Connect) reply received. Sep 22 09:50:23 xyzzy nm-openvpn[22961]: OpenVPN 2.3.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Sep 8 2015 Sep 22 09:50:23 xyzzy nm-openvpn[22961]: library versions: OpenSSL 1.0.2d 9 Jul 2015, LZO 2.08 Sep 22 09:50:23 xyzzy nm-openvpn[22961]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sep 22 09:50:23 xyzzy nm-openvpn[22961]: NOTE: chroot will be delayed because of --client, --pull, or --up-delay Sep 22 09:50:23 xyzzy nm-openvpn[22961]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay Sep 22 09:50:23 xyzzy nm-openvpn[22961]: UDPv4 link local: [undef] Sep 22 09:50:23 xyzzy nm-openvpn[22961]: UDPv4 link remote: [AF_INET]xyzzyip:xyzzyport Sep 22 09:50:25 xyzzy nm-openvpn[22961]: [server] Peer Connection Initiated with [AF_INET]xyzzyip:xyzzyport Sep 22 09:50:27 xyzzy nm-openvpn[22961]: AUTH: Received control message: AUTH_FAILED Sep 22 09:50:27 xyzzy nm-openvpn[22961]: SIGUSR1[soft,auth-failure] received, process restarting Sep 22 09:50:27 xyzzy NetworkManager[848]: VPN plugin failed: login-failed (0) Sep 22 09:50:27 xyzzy NetworkManager[848]: VPN plugin state changed: stopped (6) Sep 22 09:50:27 xyzzy NetworkManager[848]: VPN plugin state change reason: login-failed (10) Sep 22 09:50:27 xyzzy NetworkManager[848]: (nm-openvpn-service:20864): nm-openvpn-WARNING **: Password verification failed Sep 22 09:50:27 xyzzy NetworkManager[848]: error disconnecting VPN: Could not process the request because no VPN connection was active. Oops, reconnect! Sep 22 09:50:31 xyzzy NetworkManager[848]: (nm-openvpn-service:20864): nm-openvpn-WARNING **: (nm-openvpn-service.c:1269):nm_openvpn_start_openvpn_binary: runtime check failed: (priv->mgt_path == NULL) Sep 22 09:50:31 xyzzy NetworkManager[848]: nm-openvpn-Message: openvpn started with pid 23033 Sep 22 09:50:31 xyzzy NetworkManager[848]: VPN plugin state changed: starting (3) Sep 22 09:50:31 xyzzy NetworkManager[848]: VPN connection 'xyzzy' (Connect) reply received. Sep 22 09:50:31 xyzzy nm-openvpn[23033]: OpenVPN 2.3.7 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Sep 8 2015 Sep 22 09:50:31 xyzzy nm-openvpn[23033]: library versions: OpenSSL 1.0.2d 9 Jul 2015, LZO 2.08 Sep 22 09:50:32 xyzzy nm-openvpn[23033]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Sep 22 09:50:32 xyzzy nm-openvpn[23033]: NOTE: chroot will be delayed because of --client, --pull, or --up-delay Sep 22 09:50:32 xyzzy nm-openvpn[23033]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay Sep 22 09:50:32 xyzzy nm-openvpn[23033]: UDPv4 link local: [undef] Sep 22 09:50:32 xyzzy nm-openvpn[23033]: UDPv4 link remote: [AF_INET]xyzzyip:xyzzyport Sep 22 09:50:33 xyzzy nm-openvpn[23033]: [server] Peer Connection Initiated with [AF_INET]xyzzyip:xyzzyport Sep 22 09:50:35 xyzzy nm-openvpn[23033]: TUN/TAP device tap0 opened Sep 22 09:50:35 xyzzy nm-openvpn[23033]: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --tap -- tap0 1500 1574 xyzzy 255.255.255.0 init Sep 22 09:50:35 xyzzy NetworkManager[848]: (tap0): new Tun device (carrier: OFF, driver: 'tun', ifindex: 6) Sep 22 09:50:35 xyzzy NetworkManager[848]: devices added (path: /sys/devices/virtual/net/tap0, iface: tap0) Sep 22 09:50:35 xyzzy NetworkManager[848]: device added (path: /sys/devices/virtual/net/tap0, iface: tap0): no ifupdown configuration found. Sep 22 09:50:35 xyzzy NetworkManager[848]: VPN connection 'xyzzy' (IP Config Get) reply received. Sep 22 09:50:35 xyzzy NetworkManager[848]: VPN connection 'xyzzy' (IP4 Config Get) reply received. Sep 22 09:50:35 xyzzy NetworkManager[848]: VPN plugin state changed: started (4) Sep 22 09:50:35 xyzzy NetworkManager[848]: VPN connectio
Bug#836324: tightvncserver: Typing gives wrong keys in some apps
On Sat, 3 Sep 2016, Ola Lundqvist wrote: Also interesting that the problem goes away with vnc4server. I just came across tigervnc which has the tight protocol support and does not suffer from this bug. The tigervnc website says it's based on the newer vnc4 branch of tightvnc that never got released, so this may be a bugfix in vnc4 that was not in the older tightvnc 1.3 code. What client software do you use? I tried many, including vinagre, remmina, and the uber-basic vncviewer, all had exactly the same problem. FWIW, since tigervnc does everything (for me) that tightvnc did, and doesn't have this bug, switching to that package functions as a "fix" for this for me, and I'm no longer concerned about tightvnc, esp. since it seems to be effectively unmaintained upstream, at least for open source linux packaging. -- -Matt "Reality is that which, when you stop believing in it, doesn't go away". -- Philip K. Dick GPG fingerprint: 0061 15DF D282 D4A9 57CE 77C5 16AF 1460 4A3C C4E9
Bug#842952: firefox: Things that are still bad with GTK+3 enabled
fixed 842952 50.0-1 thanks On 11/03/2016 10:24 AM, Sylvestre Ledru wrote: > In the future, please report a bug per issue and create a meta bug to > keep track of them. > > It makes the life of the maintainer harder. Sorry for that. Having just installed 50.0-1, both the annoyances I mentioned seem to be fixed. The addressbar issue may have been fixed by another package upgrade in between, I'm not sure. The black bars issue was definitely fixed just by installing the new version of firefox. The widget size issue that ano...@users.sourceforge.net reported is still present, but as you note that shouldn't be lumped into this, and it doesn't bother me too much, so I'm marking this fixed ... assuming my noob interaction with the control address doesn't go wrong ;)
Bug#862100: snort: Email alerts don't work in default config
Package: snort Version: 2.9.7.0-5 Severity: important The default configuration of snort offers to setup an e-mail alert ... which will NEVER work in the default configuration, because the alerting script only seems to work with textual log files, while the default config only generates the binary unified2 format log file. Nothing in the debconf prompting for the alert setup even hints that this might be a problem, leading to a false sense of security by the administrator installing the package. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-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 snort depends on: ii adduser 3.115 ii debconf [debconf-2.0]1.5.60 ii libc62.24-10 ii libdaq2 2.0.4-3+b1 ii libdumbnet1 1.12-7+b1 ii liblzma5 5.2.2-1.2+b1 ii libpcap0.8 1.8.1-3 ii libpcre3 2:8.39-3 ii logrotate3.11.0-0.1 ii net-tools1.60+git20161116.90da8a0-1 ii rsyslog [system-log-daemon] 8.24.0-1 ii snort-common 2.9.7.0-5 ii snort-common-libraries 2.9.7.0-5 ii snort-rules-default 2.9.7.0-5 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages snort recommends: ii iproute2 4.9.0-1 Versions of packages snort suggests: pn snort-doc -- Configuration Files: /etc/default/snort changed [not included] -- debconf information: * snort/stats_treshold: 1 * snort/send_stats: true * snort/interface: enp1s0 * snort/please_restart_manually: * snort/address_range: 172.22.0.0/23 * snort/stats_rcpt: beech...@beechwoods.com * snort/invalid_interface: snort/config_parameters: * snort/options: * snort/startup: boot * snort/disable_promiscuous: false
Bug#858923: libpam-winbind: Cannot change password via passwd (pam) in default config
Package: libpam-winbind Version: 2:4.5.8+dfsg-1 Followup-For: Bug #858923 The common recommendation for how to fix this issue, as long as you don't have too much else in the way of "interesting" module stacking is to remove use_authtok from the pam_winbind entry. But that will get clobbered the next time pam-auth-update gets run AFAICT. So I thought the next best solution would be to edit /usr/share/pam-configs/winbind to change the template entry for winbind. But that's not a conf file, so it too will get clobbered, this time on package upgrade. Making /usr/share/pam-configs/winbind a conffile would at least allow reasonable sysadmin workarounds. While others disagree, I'd go so far as to say that removing use_authtok should be the default, as the simple PAM configs are going to be vastly more common than the complex stacking ones that might be adversely affected by that. Another way around this I guess might be to have a special PAM module that's not part of the normal stack whose sole purpose is to force the prompt for the new password to happen, and then make all the "real" modules use use_authtok, including pam_unix. That's a more complex and invasive change, though. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-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) Versions of packages libpam-winbind depends on: ii dpkg1.18.23 ii libbsd0 0.8.3-1 ii libc6 2.24-10 ii libpam-runtime 1.1.8-3.5 ii libpam0g1.1.8-3.5 ii libtalloc2 2.1.8-1 ii libwbclient02:4.5.8+dfsg-1 ii samba-common2:4.5.8+dfsg-1 ii samba-libs 2:4.5.8+dfsg-1 ii winbind 2:4.5.8+dfsg-1 libpam-winbind recommends no packages. Versions of packages libpam-winbind suggests: ii libnss-winbind 2:4.5.8+dfsg-1 -- no debconf information
Bug#827593: new upstream (2.9.8.3)
On 03/17/2017 12:59 PM, Matthew Gabeler-Lee wrote: > Further, I would note that upstream has now officially End of Life'd 2.9.7.x And now they have discontinued providing rules for 2.9.7.x, making the Debian provided package ever closer to useless.
Bug#858759: pepperflashplugin-nonfree: Option --quiet is broken
Package: pepperflashplugin-nonfree Version: 1.8.3+nmu1 Severity: normal Can't pass --quiet arg any more: $ sudo /usr/sbin/update-pepperflashplugin-nonfree --install --quiet Can't be verbose and quiet at the same time. Usage: wget [OPTION]... [URL]... gzip: stdin: unexpected end of file tar: Child returned status 1 tar: Error is not recoverable: exiting now -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/12 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 pepperflashplugin-nonfree depends on: ii binutils 2.27.90.20170124-2 ii ca-certificates20161130 ii debconf [debconf-2.0] 1.5.60 ii gnupg 2.1.18-6 ii libatk1.0-02.22.0-1 ii libcairo2 1.14.8-1 ii libcurl3-gnutls7.52.1-3 ii libfontconfig1 2.11.0-6.7+b1 ii libfreetype6 2.6.3-3+b2 ii libgcc11:6.3.0-6 ii libglib2.0-0 2.50.3-1 ii libgtk2.0-02.24.31-2 ii libnspr4 2:4.12-6 ii libnss32:3.26.2-1 ii libpango-1.0-0 1.40.4-1 ii libpango1.0-0 1.40.4-1 ii libstdc++6 6.3.0-6 ii libx11-6 2:1.6.4-3 ii libxext6 2:1.3.3-1+b2 ii libxt6 1:1.1.5-1 ii wget 1.18-5 pepperflashplugin-nonfree recommends no packages. Versions of packages pepperflashplugin-nonfree suggests: pn chromium pn hal pn ttf-dejavu ii ttf-mscorefonts-installer 3.6 ii ttf-xfree86-nonfree4.2.1-5 -- no debconf information
Bug#858923: libpam-winbind: Cannot change password via passwd (pam) in default config
Package: libpam-winbind Version: 2:4.5.6+dfsg-1 Severity: normal Domain-only users cannot change their password in the default configuration. Ubuntu has a bug for this with a workaround, though the workaround has its own issues: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/570944 It appears there is a problem with having use_authtok in the winbind line for the password pam service. However, there are other issues in some configurations with removing that option. I've tried the workaround suggested there: removing use_authtok from the winbind entry in /etc/pam.d/common-password, and it worked for me -- my environment doesn't have the concerns with removing that item that may apply to others. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/12 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 libpam-winbind depends on: ii dpkg1.18.23 ii libbsd0 0.8.3-1 ii libc6 2.24-9 ii libpam-runtime 1.1.8-3.5 ii libpam0g1.1.8-3.5 ii libtalloc2 2.1.8-1 ii libwbclient02:4.5.6+dfsg-1 ii samba-common2:4.5.6+dfsg-1 ii samba-libs 2:4.5.6+dfsg-1 ii winbind 2:4.5.6+dfsg-1 libpam-winbind recommends no packages. Versions of packages libpam-winbind suggests: ii libnss-winbind 2:4.5.6+dfsg-1 -- no debconf information
Bug#859141: tigervnc-standalone-server: Wrapper script is unreasonably intolerant of slightly slow or busy systems
Package: tigervnc-standalone-server Version: 1.7.0+dfsg-6 Severity: normal The /usr/bin/tigervncserver wrapper script gives up and kills the server it just started if it doesn't have its VNC-TCP and X11-unix sockets up and running within one second. If a machine is a bit bogged down, this can prevent starting the server at all, for no good reason. It seems like 10-60 seconds would be a much more reasonable timeout here. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-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) Versions of packages tigervnc-standalone-server depends on: ii libaudit1 1:2.6.7-1 ii libc6 2.24-9 ii libgcc1 1:6.3.0-10 ii libgcrypt20 1.7.6-1 ii libgl1-mesa-glx [libgl1] 13.0.5-1 ii libgnutls30 3.5.8-3 ii libjpeg62-turbo 1:1.5.1-2 ii libpam0g 1.1.8-3.5 ii libpixman-1-0 0.34.0-1 ii libselinux1 2.6-3+b1 ii libstdc++66.3.0-10 ii libsystemd0 232-19 ii libx11-6 2:1.6.4-3 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.2-3 ii libxfont2 1:2.0.1-3 ii libxshmfence1 1.2-1+b2 pn perl:any ii x11-xkb-utils 7.7+3+b1 ii xauth 1:1.0.9-1+b2 ii xkb-data 2.19-1 ii zlib1g1:1.2.8.dfsg-5 Versions of packages tigervnc-standalone-server recommends: ii libgl1-mesa-dri13.0.5-1 pn tigervnc-common ii x11-xserver-utils 7.7+7+b1 ii xfonts-base1:1.0.4+nmu1 Versions of packages tigervnc-standalone-server suggests: ii xfonts-100dpi1:1.0.4+nmu1 ii xfonts-75dpi 1:1.0.4+nmu1 ii xfonts-scalable 1:1.0.3-1.1 -- no debconf information
Bug#859733: snort: Please provide snort-dev package for compiling so_rules
Source: snort Version: 2.9.7.0-5 Severity: wishlist Currently, if you install snort from debian, you can't compile so rules from sources, because the header files needed to do so (e.g. sf_snort_plugin_api.h) are not distributed as part of any of the Debian packages. Having a snort-dev package that contains all the headers/etc. needed for compiling so_rules would be useful. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-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)
Bug#827593: new upstream (2.9.8.3)
Source: snort Version: 2.9.7.0-5 Followup-For: Bug #827593 Further, I would note that upstream has now officially End of Life'd 2.9.7.x -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-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)
Bug#837788: munin: systemd control scripts are missing
Package: munin Version: 2.0.33-1 Followup-For: Bug #837788 I argue this merits worse than "important" -- in a default install of Stretch currently, munin doesn't work at all. Also worthy of note is this workaround: sudo rm /lib/systemd/system/munin.service sudo systemctl enable munin sudo systemctl start munin This takes it back to using the sysvinit script with systemd. I don't know if this might cause difficulties with future upgrades, but it at least gets munin running again for me. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/12 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 munin depends on: ii cron [cron-daemon]3.0pl1-128+b1 ii fonts-dejavu-core 2.37-1 ii libdate-manip-perl6.57-1 pn libdigest-md5-perl ii libfile-copy-recursive-perl 0.38-1 ii libhtml-template-perl 2.95-2 ii libio-socket-inet6-perl 2.72-2 ii liblog-log4perl-perl 1.48-1 ii libperl5.24 [libtime-hires-perl] 5.24.1-1 ii librrds-perl 1.6.0-1+b2 pn libstorable-perl ii liburi-perl 1.71-1 ii lsb-base 9.20161125 ii munin-common 2.0.33-1 ii perl 5.24.1-1 ii rrdtool 1.6.0-1+b2 Versions of packages munin recommends: ii libcgi-fast-perl 1:2.12-1 pn munin-doc ii munin-node2.0.33-1 Versions of packages munin suggests: ii apache2 [httpd] 2.4.25-3 ii libapache2-mod-fcgid 1:2.3.9-1+b1 ii libnet-ssleay-perl1.80-1 ii lynx [www-browser]2.8.9dev11-1 ii w3m [www-browser] 0.5.3-34 -- Configuration Files: /etc/cron.d/munin changed [not included] /etc/munin/apache.conf changed [not included] /etc/munin/apache24.conf changed [not included] /etc/munin/munin.conf changed [not included] -- no debconf information
Bug#837788: munin: systemd control scripts are missing
On Fri, 10 Mar 2017, Simon McVittie wrote: However, Matthew Gabeler-Lee's reply: I argue this merits worse than "important" -- in a default install of Stretch currently, munin doesn't work at all. suggests that there may be something else going on. Matthew, please could you describe what you did (before applying any workarounds), what you expected to happen, and what actually happened, including any syslog, Journal or web server log messages that look potentially relevant? On closer inspection, I think I need to retract my prior statement. I had a problem with munin "not working at all" -- i.e. not collecting data / updating charts, which correlated with an upgrade of the munin package. But on closer inspection, I realize two things happened that day, and it was actually the other thing that "broke" munin, and it was a mistake interpreting the munin status pages that made me thing the sysvinit workaround "fixed" it. The sysvinit hack "fixing" things was a false positive, and it was really fixing the other problem (a network issue preventing data collection from most nodes) that made munin start working for me. I think the suggestion that this in fact is not a bug and is just a confusion with how munin works is correct. It is in fact /etc/cron.d/munin that does the "service" work of munin. Apologies for the confusion! -- -Matt "Reality is that which, when you stop believing in it, doesn't go away". -- Philip K. Dick GPG fingerprint: 0061 15DF D282 D4A9 57CE 77C5 16AF 1460 4A3C C4E9
Bug#855969: gitolite3: Please package ukm tool from contrib
Package: gitolite3 Version: 3.6.1-2+deb8u1 Severity: wishlist The upstream gitolite source includes a very useful "contrib" tool 'ukm' to help with key management. It would be nice if the Debian package included this tool in some fashion. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-1-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)
Bug#856311: avahi-daemon: Won't start due to rlimit nproc, confused by lxc containers
Package: avahi-daemon Version: 0.6.32-2 Severity: normal On one of my systems, avahi-daemon can't start due to its default rlimit-nproc value of 3. In my case this seems to be because an lxc container running on this host is using the same uid for avahi as the host system, but for a different function. Even if it was using it for the same function, the rlimit-nproc is enforcing in the wrong scope it seems. Feb 27 10:28:34 hostname avahi-daemon[23274]: Found user 'avahi' (UID 104) and group 'avahi' (GID 110). Feb 27 10:28:34 hostname avahi-daemon[23274]: Successfully dropped root privileges. Feb 27 10:28:34 hostname avahi-daemon[23274]: chroot.c: fork() failed: Resource temporarily unavailable Feb 27 10:28:34 hostname avahi-daemon[23274]: failed to start chroot() helper daemon. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/12 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 avahi-daemon depends on: ii adduser 3.115 ii bind9-host [host]1:9.10.3.dfsg.P4-12 ii dbus 1.10.16-1 ii host 1:9.10.3.dfsg.P4-12 ii init-system-helpers 1.47 ii libavahi-common3 0.6.32-2 ii libavahi-core7 0.6.32-2 ii libc62.24-9 ii libcap2 1:2.25-1 ii libdaemon0 0.14-6 ii libdbus-1-3 1.10.16-1 ii libexpat12.2.0-2 ii lsb-base 9.20161125 Versions of packages avahi-daemon recommends: ii libnss-mdns 0.10-8 Versions of packages avahi-daemon suggests: pn avahi-autoipd -- no debconf information
Bug#861156: tt-rss: Needs new Dojo to render UI properly
Package: tt-rss Version: 17.1+git20170410+dfsg-2 Severity: important Since updating to the new 17.1 package of tt-rss, some parts of the UI no longer render correctly. Immediately noticeable is the feed icons are all gone, despite the usual "clear cookies, shift-reload" after updates. Scanning around, I find this thread that indicates upstream expects to have Dojo 1.12, but Debian / this tt-rss package only has 1.11, so I suspect this is the crux of the issue. https://tt-rss.org/oldforum/viewtopic.php?f=10&t=4024 For reference, with the older Dojo, the immediate problem of feed icons seems to be placing an as a child of another , which no browser will render AFAICT. I suspect in the newer Dojo, the node it's placing the image into is no longer another image. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-2-amd64 (SMP w/12 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 tt-rss depends on: ii dbconfig-common 2.0.8 ii dbconfig-mysql 2.0.8 ii debconf [debconf-2.0] 1.5.60 ii init-system-helpers 1.47 ii libapache2-mod-php7.0 [libapache2-mod-php] 7.0.16-3 ii libjs-dojo-core 1.11.0+dfsg-1 ii libjs-dojo-dijit1.11.0+dfsg-1 ii libjs-scriptaculous 1.9.0-2 ii libphp-phpmailer5.2.14+dfsg-2.3 ii lsb-base9.20161125 ii php 1:7.0+49 ii php-mbstring1:7.0+49 ii php-mysql 1:7.0+49 ii php-php-gettext 1.0.12-0.1 ii php-xml 1:7.0+49 ii php7.0 [php]7.0.16-3 ii php7.0-cgi [php-cgi]7.0.16-3 ii php7.0-cli [php-cli]7.0.16-3 ii php7.0-json [php-json] 7.0.16-3 ii php7.0-mbstring [php-mbstring] 7.0.16-3 ii php7.0-pgsql [php-pgsql]7.0.16-3 ii php7.0-xml [php-xml]7.0.16-3 ii phpqrcode 1.1.4-2 Versions of packages tt-rss recommends: ii apache2 [httpd] 2.4.25-3 ii ca-certificates 20161130 ii lighttpd [httpd]1.4.45-1 ii php-curl1:7.0+49 ii php-gd 1:7.0+49 ii php7.0-curl [php-curl] 7.0.16-3 ii php7.0-gd [php-gd] 7.0.16-3 ii php7.0-mcrypt [php-mcrypt] 7.0.16-3 Versions of packages tt-rss suggests: ii php-apc 4.0.10-1 ii php5-apcu [php-apc] 4.0.10-1 ii sphinxsearch 2.2.11-1.1 -- Configuration Files: /etc/default/tt-rss changed [not included] /etc/tt-rss/apache.conf changed [not included] /etc/tt-rss/config.php changed [not included] -- debconf information excluded
Bug#861262: sphinxsearch: service restart on upgrades or otherwise always fails
Package: sphinxsearch Version: 2.2.11-1.1 Severity: important Every time something tries to restart sphinxsearch, it fails, leaving the sphinxsearch service in a failed state and the daemon not running. This happens on package upgrades, or restarts for library upgrades, or restarts for config changes, or anything that tries to restart sphinxsearch. It looks like the stop request returns before it is actually stopped, which causes the following start request to fail because the old copy is still running. One thing I notice once it's up and running is that the PID in /var/run/sphinxsearch/searchd.pid is NOT the pid of the top level searchd process, but rather the PID of its immediate child. I'm not sure if there's a "supervisor" process being used here or what. Example flow: $ sudo service sphinxsearch restart Job for sphinxsearch.service failed because the control process exited with error code. See "systemctl status sphinxsearch.service" and "journalctl -xe" for details. $ sudo service sphinxsearch status ● sphinxsearch.service - LSB: Fast standalone full-text SQL search engine Loaded: loaded (/etc/init.d/sphinxsearch; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2017-04-26 11:57:41 EDT; 3s ago Docs: man:systemd-sysv-generator(8) Process: 25416 ExecStop=/etc/init.d/sphinxsearch stop (code=exited, status=0/SUCCESS) Process: 25421 ExecStart=/etc/init.d/sphinxsearch start (code=exited, status=1/FAILURE) Tasks: 0 (limit: 4915) Memory: 4.7M CPU: 9ms CGroup: /system.slice/sphinxsearch.service Apr 26 11:57:41 hostname systemd[1]: Stopping LSB: Fast standalone full-text SQL search engine... Apr 26 11:57:41 hostname sphinxsearch[25416]: Stopping sphinxsearch: sphinxsearch. Apr 26 11:57:41 hostname systemd[1]: Stopped LSB: Fast standalone full-text SQL search engine. Apr 26 11:57:41 hostname systemd[1]: Starting LSB: Fast standalone full-text SQL search engine... Apr 26 11:57:41 hostname sphinxsearch[25421]: Starting sphinxsearch: /usr/bin/searchd already running. Apr 26 11:57:41 hostname systemd[1]: sphinxsearch.service: Control process exited, code=exited status=1 Apr 26 11:57:41 hostname systemd[1]: Failed to start LSB: Fast standalone full-text SQL search engine. Apr 26 11:57:41 hostname systemd[1]: sphinxsearch.service: Unit entered failed state. Apr 26 11:57:41 hostname systemd[1]: sphinxsearch.service: Failed with result 'exit-code'. $ sudo service sphinxsearch restart $ sudo service sphinxsearch status ● sphinxsearch.service - LSB: Fast standalone full-text SQL search engine Loaded: loaded (/etc/init.d/sphinxsearch; generated; vendor preset: enabled) Active: active (running) since Wed 2017-04-26 11:57:55 EDT; 3min 14s ago Docs: man:systemd-sysv-generator(8) Process: 25416 ExecStop=/etc/init.d/sphinxsearch stop (code=exited, status=0/SUCCESS) Process: 25443 ExecStart=/etc/init.d/sphinxsearch start (code=exited, status=0/SUCCESS) Tasks: 8 (limit: 4915) Memory: 11.4M CPU: 225ms CGroup: /system.slice/sphinxsearch.service ├─25447 /usr/bin/searchd └─25448 /usr/bin/searchd Apr 26 11:57:55 hostname sphinxsearch[25443]: Sphinx 2.2.11-id64-release (95ae9a6) Apr 26 11:57:55 hostname sphinxsearch[25443]: Copyright (c) 2001-2016, Andrew Aksyonoff Apr 26 11:57:55 hostname sphinxsearch[25443]: Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com) Apr 26 11:57:55 hostname sphinxsearch[25443]: precaching index 'wiki_main' Apr 26 11:57:55 hostname sphinxsearch[25443]: [249B blob data] Apr 26 11:57:55 hostname sphinxsearch[25443]: [250B blob data] Apr 26 11:57:55 hostname sphinxsearch[25443]: Copyright (c) 2001-2016, Andrew Aksyonoff Apr 26 11:57:55 hostname sphinxsearch[25443]: Copyright (c) 2008-2016, Sphinx Technologies Inc (http://sphinxsearch.com) Apr 26 11:57:55 hostname sphinxsearch[25443]: sphinxsearch. Apr 26 11:57:55 hostname systemd[1]: Started LSB: Fast standalone full-text SQL search engine. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/12 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 sphinxsearch depends on: ii adduser 3.115 ii libc6 2.24-9 ii libexpat1 2.2.0-2 ii libgcc1 1:6.3.0-14 ii libmariadbclient18 10.1.22-3 ii libpq5 9.6.2-2 ii libstdc++6 6.3.0-14 ii libstemmer0d0+svn585-1+b2 ii zlib1g 1:1.2.8.dfsg-5 sphinxsearch recommends no packages. sphinxsearch suggests no packages. -- Configuration Files: /etc/cron.d/sphinxsearch changed [not included] /etc/default/sphinxsearch changed [not included] -- no debconf information
Bug#861156: tt-rss: Needs new Dojo to render UI properly
On 04/26/2017 02:56 PM, Sebastian Reichel wrote: > I can't reproduce this. I tested the release before uploading and everything > (incl. feed icons) worked and still works as expected in my installation. Hmm, interesting. Do you have different dojo packages installed vs. my report somehow? Can you check with the DOM inspector tools in your browser to see if you have the same img-as-a-child-of-an-img odditiy that I got? I'm seeing my problem in multiple browsers on multiple machines, in normal and incognito/private modes, chrome guest profiles (so no addins/extensions), including after flushing caches and cookies. The feed icon elements are /there/ in the DOM, it's just the browsers are refusing to render the nested image. If I use the DOM tree editor in Firefox to hack on the element type of the outer image, I can get the icon to display.
Bug#861156: tt-rss: Needs new Dojo to render UI properly
On 04/26/2017 05:23 PM, Matthew Gabeler-Lee wrote:
> On 04/26/2017 02:56 PM, Sebastian Reichel wrote:
>> I can't reproduce this. I tested the release before uploading and everything
>> (incl. feed icons) worked and still works as expected in my installation.
> Hmm, interesting. Do you have different dojo packages installed vs. my
> report somehow?
>
> Can you check with the DOM inspector tools in your browser to see if you
> have the same img-as-a-child-of-an-img odditiy that I got?
Argh, I figured it out. Somehow my
/usr/share/tt-rss/www/lib/{dojo,dijit} were not symlinks but a static
copy from $deity knows where. Probably leftovers from me trying to work
around the last time an upgrade to those libraries was needed.
Replacing those snapshots with proper symlinks fixed things.
Feel free to close this as "user shot self in foot" :)
Bug#794477: ruby-mysql2: Unversioned dependency on libmysqlclient18 leads to unusable package in testing
Package: ruby-mysql2 Version: 0.3.18-1 Severity: important The contents of the ruby-mysql2 package effectively have a versioned dependency on libmysqlclient18, but the package itself does not specify a version dependency. This leads to the current version of ruby-mysql2 in testing being unusable until the new version of mysql migrates to testing. Witness: Setting up redmine (3.0~20140825-8) ... Populating database for redmine instance "default". This may take a while. rake aborted! Incorrect MySQL client library version! This gem was compiled for 5.6.25 but the client library is 5.5.43. If the ruby library is going to complain about the mysql library version, seems the package dependencies should reflect that. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/12 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 ruby-mysql2 depends on: ii libc6 2.19-19 ii libgmp10 2:6.0.0+dfsg-7 ii libmysqlclient18 5.5.43-0+deb8u1 ii libruby2.1 2.1.5-3 ii ruby 1:2.1.5.1 ii ruby-eventmachine 1.0.7-3 ii zlib1g 1:1.2.8.dfsg-2+b1 ruby-mysql2 recommends no packages. ruby-mysql2 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#795313: openvpn: CapabilityBoundingSet breaks auth pam plugin
Package: openvpn Version: 2.3.7-1 Severity: important With the update from 2.3.4-5 to 2.3.7-1 (testing), my vpn configurations using the auth pam plugin broke. After much digging, I finally isolated this to the addition of the CapabilityBoundingSet entry in the systemd service definition. If I comment that out, everything works again. I've marked this as important because I suspect the auth pam plugin sees wide usage, and because the nature of the way that module writes its debug data and how systemd runs openvpn means that no matter how high you turn the verbosity in openvpn, you won't actually receive any of the diagnostic data from the plugin to help figure out what the problem is, and if you run openvpn on the console, the capabilities limitation isn't applied and the problem won't appear to debug. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-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) Versions of packages openvpn depends on: ii debconf [debconf-2.0] 1.5.57 ii init-system-helpers1.23 ii initscripts2.88dsf-59.2 ii iproute2 4.0.0-1 ii libc6 2.19-19 ii liblzo2-2 2.08-1.2 ii libpam0g 1.1.8-3.1 ii libpkcs11-helper1 1.11-4 ii libssl1.0.01.0.2d-1 ii libsystemd0224-1 Versions of packages openvpn recommends: pn easy-rsa Versions of packages openvpn suggests: ii openssl 1.0.2d-1 pn resolvconf -- debconf information excluded
Bug#817929: mosh fails to connect, giving a UDP error
On 03/24/2016 12:31 AM, john hood wrote: > I haven't been able to chase these glibc details down. Do you have > pointers to specifics for this? My assessment was based just on reading the referenced glibc-help thread, and the commit it referenced -- https://sourceware.org/git/gitweb.cgi?p=glibc.git;a=commitdiff;h=beff1d132c16aedd87a3f1bc7b572c8e69819015 The commit contains this comment ahead of the "trampoline" generation: /* libpthread once had its own fork, though there was no apparent reason for it. There is no use in having a separate symbol in libpthread, but the historical ABI requires it. For static linking, there is no need to provide anything here--the libc version will be linked in. For shared library ABI compatibility, there must be __fork and fork symbols in libpthread.so; so we define them using IFUNC to redirect to the libc function. */ There is also some further discussion on the glibc thread since it was first referenced here. To summarize some key items from that: "this is a bug. Could you report it in Bugzilla here, please?" "The commit you identified, beff1d132c16aedd87a3f1bc7b572c8e69819015, assumes that __libc_fork has been relocated before the IFUNC resolver for the libpthread fork definition runs, which is not always true." https://sourceware.org/bugzilla/show_bug.cgi?id=19861 So it looks like, contrary to my assessment (I said I wasn't an expert :), this *is* a glibc bug. But the mosh workaround is probably still necessary in the short term.
Bug#819466: alien: DEB->RPM does not setup Provides for shared libraries properly
Package: alien Version: 8.95 Severity: normal Example: Converting the debian liblockfile1 and lockfile-progs to RPM packages, because CentOS packages totally broken and useless versions of these. The converted lockfile-progs has these Requires: libc.so.6 libc.so.6(GLIBC_2.0) liblockfile.so.1 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 But the converted liblockfile1 only has these Provides: liblockfile1 = 1.09-7 liblockfile1(x86-32) = 1.09-7 Note that the provides and requires for the shared library are totally disjoint, resulting in the application RPM not being installable! -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-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) Versions of packages alien depends on: ii cpio 2.11+dfsg-5 ii debhelper 9.20160313 ii dpkg-dev 1.18.4 ii make 4.1-9 ii perl 5.22.1-9 ii rpm4.12.0.1+dfsg1-3+b2 ii rpm2cpio 4.12.0.1+dfsg1-3+b2 alien recommends no packages. Versions of packages alien suggests: ii bzip21.0.6-8 pn lintian ii patch2.7.5-1 ii xz-utils [lzma] 5.1.1alpha+20120614-2.1 -- no debconf information
Bug#819598: bluetooth: Can't use bluetooth 4 / LE HID devices
Package: bluetooth Version: 5.36-1 Severity: normal Tags: upstream I'm having the same problem as described in this Ubuntu ticket: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1546603 My log entries, for completeness: Mar 30 20:43:56 hostname bluetoothd[1525]: Error reading PNP_ID value: Attribute requires authentication before read/write Mar 30 20:43:56 hostname bluetoothd[1525]: Unable to register GATT service with handle 0x0009 for device C6:E5:C2:98:9B:58 Mar 30 20:43:56 hostname bluetoothd[1525]: Unable to register GATT service with handle 0x000e for device C6:E5:C2:98:9B:58 Mar 30 20:43:57 hostname bluetoothd[1525]: Report Map read failed: Attribute requires authentication before read/write Mar 30 20:43:57 hostname bluetoothd[1525]: Protocol Mode characteristic read failed: Attribute requires authentication before read/write Mar 30 20:43:57 hostname bluetoothd[1525]: HID Information read failed: Attribute requires authentication before read/write Mar 30 20:43:57 hostname bluetoothd[1525]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Mar 30 20:43:57 hostname bluetoothd[1525]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Mar 30 20:43:57 hostname bluetoothd[1525]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Mar 30 20:43:57 hostname bluetoothd[1525]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Mar 30 20:43:57 hostname bluetoothd[1525]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Mar 30 20:43:57 hostname bluetoothd[1525]: Read Report Reference descriptor failed: Attribute requires authentication before read/write I'm using a Microsoft Bluetooth Mouse 3600 for reference. It is a BT4/LE device. It pairs and connects just fine, but no HID events make it through (at least not through to X) -- no pointer movement, clicks, or scrolls. Some deep time with Google suggests that this issue affects quite a few folks (not just Debian, includes keyboards as well as other mice) and _may_ be fixed by this upstream patch: http://www.spinics.net/lists/linux-bluetooth/msg66469.html AKA http://git.kernel.org/cgit/bluetooth/bluez.git/commit/?id=064f48ad6dd0eb4becb94f5492b6c78218065f19 Which I think is included in the latest upstream release (5.38). I haven't had the chance yet to test/verify this. I see #816815 is also requesting an update to newer upstream to support newer hardware, though not related to this specific issue. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages bluetooth depends on: ii bluez 5.36-1 bluetooth recommends no packages. Versions of packages bluetooth suggests: ii bluez-cups 5.36-1 ii bluez-obexd 5.36-1 -- no debconf information
Bug#819598: (no subject)
Addenda: I meant #816865, not 816815 Upgrading bluez locally gets rid of the prior errors, but produces other errors, and the mouse still doesn't work (at first, but keep reading) I cleared the previous pairing and tried to re-pair, just to be "safe" Mar 30 21:20:56 hostname bluetoothd[1421]: GATT service objects disabled Mar 30 21:20:56 hostname kernel: [ 36.700194] Bluetooth: SMP security requested but not available The last line repeats every ~15 *milliseconds* until it times out and gives up. That sounds like https://bugzilla.kernel.org/show_bug.cgi?id=104011 Following the suggestion there (bluetoothctl power off / power on) I was able to pair and use the mouse! The kernel.org ticket suggests it will be temporarily broken again when I reboot, and that the root cause of that is a udev rule causing the bluetooth host to be brought up in "legacy mode".
Bug#820255: joe: Character range searching doesn't work in UTF8 locale
Package: joe Version: 4.1-2 Severity: normal Create a file with some text ... e.g. this bug report ... with lots of upper and lower case letters. Start editing with LANG=en_US.UTF-8 Search for "\[a-z]" or "\[A-Z]" or "\[0-9]" -- no matches found. Search for "\[0123456789]" -- matches found! Change LANG to C, try again -- both work properly. Change LANG to en_US.ISO-8859-15 -- both work properly. Seems to be a problem with UTF8 I infer. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-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) Versions of packages joe depends on: ii libc62.22-5 ii libncurses5 6.0+20160319-1 ii libtinfo56.0+20160319-1 joe recommends no packages. joe suggests no packages. -- Configuration Files: /etc/joe/ftyperc changed [not included] /etc/joe/joerc changed [not included] -- no debconf information
Bug#814578: laptop-mode-tools throttles pstate-managed CPUs to half speed on battery power
Package: laptop-mode-tools Version: 1.69.2-1 Followup-For: Bug #814578 I have this problem too, but it's even worse for me. The throttling to "50%" ends up mapping to "always stuck at the bog minimum slowest speed possible". cpufreq-info -c 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 800 MHz - 3.00 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 800 MHz and 3.00 GHz. The governor "powersave" may decide which speed to use within this range. Even running burnP6 * nCPUs from cpuburn won't bump it off the bare minimum 800MHz when on battery. My cpu is a: model name : Intel(R) Core(TM) i7-4500U CPU @ 1.80GHz Which I guess explains why "50%" is "800MHz" -- 3GHz is the max turbo freq, 800MHz is presumably the only step close to 1800/2=900 MHz. >From what I've read, preventing the CPU from bumping up to higher frequencies can actually *increase* power consumption because it forces the CPU to stay awake longer before returning to an idle low power / sleep state. Needless to say I'm fixing this locally in my config files, but I would suggest that the current defaults should be revisited as producing poor behavior, and possibly being misguided. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages laptop-mode-tools depends on: ii init-system-helpers 1.29 ii lsb-base 9.20160110 ii psmisc 22.21-2.1+b1 ii util-linux 2.27.1-6 Versions of packages laptop-mode-tools recommends: ii ethtool 1:4.5-1 ii hdparm 9.48+ds-1 ii net-tools 1.60+git20150829.73cef8a-2 ii python-qt4 4.11.4+dfsg-1+b3 pn sdparm ii udev229-3 ii wireless-tools 30~pre9-9 Versions of packages laptop-mode-tools suggests: ii acpid 1:2.0.26-1 -- no debconf information
Bug#826717: firefox: Native notifications no longer working after upgrade
Package: firefox Version: 46.0.1-1+b1 Followup-For: Bug #826717 This is A OK with me, because the GNOME notifications didn't work most of the time. With some websites (Google Calendar for one), it was 100% failure. I believe I found a page somewhere where someone had tracked it down to a problem with notifications that gave a custom image URL that required traversing an HTTP 302 redirect to retrieve the actual image. This was a common enough bug that there's this add-on: https://addons.mozilla.org/en-US/firefox/addon/no-native-notifications/
