Bug#296079: conflict: /etc/ipsec.conf already used by openswan

Package: ipsec-tools Version: 1:0.5-2 Severity: grave Justification: renders package unusable Unpacking replacement ipsec-tools ... dpkg: error processing /var/cache/apt/archives/ipsec-tools_1%3a0.5-2_i386.deb (--unpack): trying to overwrite `/etc/ipsec.conf', which is also in package openswan

Bug#303057: slapd goes into endless sched_yield() loop

Um 23:56 Uhr am 11.04.05 schrieb Sven Hartge: [Sorry for spamming this bug report, but I _really_ need to get this going *fast*.] My last change is set_lk_max_lockers 10 which was still default and seems to be to _real_ culprit, as per ITS#2030: http://www.openldap.org

Bug#303057: slapd goes into endless sched_yield() loop

, at least my experience show this. But: I still consider it a grave bug for db4.2, if running out of lockers corrupts the database. And I consider it a bug in slapd, if it runs into a busy-waiting loop, if something inside the database went wrong. Grüße, Sven. -- Sven Hartge -- professioneller Unix

Bug#397691: librrd2 memory leak in 1.2.15

Um 00:36 Uhr am 27.11.06 schrieb Josip Rodin: On Thu, Nov 16, 2006 at 03:48:40PM +0100, Sven Hartge wrote: Can you perhaps provide a configuration (and by that I mean the RRD::graph invocation) and a .rrd data file that makes librrd2 explode? If you want, I can privately provide a tar

Bug#362049: libxfixes3: XFixesSetCursorName (no such operation)

it to something else, like shown above. If you still use the split XML tree, the entry is inside ~/.gconf/desktop/gnome/peripherals/mouse/%gconf.xml This change reverts your cursor style to the plain old X11 one, but stops the constant errors. At least for me, so far. Grüße, Sven. -- Sven Hartge

Bug#362049: libxfixes3: XFixesSetCursorName (no such operation)

Um 02:23 Uhr am 12.04.06 schrieb Sven Hartge: Open your ~/.gconf/%gconf-tree.xml and locate the following entry: entry name=cursor_theme mtime=1144799098 type=string stringvalueX/stringvalue /entry Most users will have Industrial in there. Just change it to something else

Bug#362049: libxfixes3: XFixesSetCursorName (no such operation)

to the gconf-tree: Gnome falls back to the default builtin cursor theme, which works without problems. So to me this indeed looks like a bug somewhere inside X. Grüße, S° -- Sven Hartge -- professioneller Unix-Geek Meine Gedanken im Netz: http://www.svenhartge.de/ Achtung, neue Mail-Adresse

Bug#366896: Uninstallable in Unstable due to broken versioned dependency on librrds-perl

Package: couriergraph Version: 0.24-2 Severity: grave The recent upload to unstable declares a versioned dependency on librrds-perl (= 1.1) which cannot be satisfied in Sid (or Etch=. The changelog for this version lists * Incompatibility with rrdtool1.2 has to wait until next version but

Bug#366896: closed by José Luis Tallón [EMAIL PROTECTED] (Couriergraph 0.25 solves this bug)

Um 05:48 Uhr am 18.05.06 schrieb Debian Bug Tracking System: The versioned depends was on purpose. Why? To break the package? The version in question should have _never_ been uploaded to unstable. Why did you intentionally upload a *broken* version to unstable? What purpose does such a

Bug#354771: avahi-daemon: missing dependency on libavahi-core3

Package: avahi-daemon Version: 0.6.8-1 Severity: grave Justification: renders package unusable avahi-daemon links to libavahi-core.so.4 from libavahi-core3, but does not depend on it, thus causing the daemon to fail. [EMAIL PROTECTED]:~$ ldd /usr/sbin/avahi-daemon linux-gate.so.1 =

Bug#385012: init-script does not work if /usr is on a different filesystem

realized my error. Sorry for the noise and trouble. S° -- Sven Hartge -- professioneller Unix-Geek Meine Gedanken im Netz: http://www.svenhartge.de/

Bug#379859: rxvt-unicode: depends on libgcc1 (= 1:4.2-20060707) from experimental, uninstallable in Sid

Package: rxvt-unicode Version: 7.8-1 Severity: grave Justification: renders package unusable The package is build with gcc4.2 from experimental and thus depends on libgcc1 from experimental which causes it to be uninstallable in Sid: rxvt-unicode: Depends: libgcc1 (= 1:4.2-20060707) but

Bug#385012: init-script does not work if /usr is on a different filesystem

Package: procps Version: 1:3.2.7-1 Severity: serious /etc/init.d/procps is using which (located at /usr/bin/which) at a time where /usr is not mounted. This causes the init-script to fail and leaves /etc/sysctl.conf unprocessed. The severity is justified by the fact that /etc/sysctl.conf is the

Bug#385012: init-script does not work if /usr is on a different filesystem

a backported package to Sarge (where which is only in /usr/bin). I am very sorry for the noise I made, I will take my business with this problem back to the backports.org mailinglist. Grüße, Sven. -- Sven Hartge -- professioneller Unix-Geek Meine Gedanken im Netz: http://www.svenhartge.de/ Achtung, neue

Bug#397691: causes munin-graph to consume all memory

Package: librrds-perl Version: 1.2.15-0.1 Severity: critical Since the upgrade from 1.2.11-0.6 to 1.2.15-0.1 munin-graph consumes all memory and swap on my system, causing the system to be unusable until the OOM killer fires and hopefully kills the offending processes. Since munin-graph is run

Bug#373676: python-imaging: Error in configure: __main__.PyCentralError: package has no field Python-Version

Package: python-imaging Version: 1.1.5-8 Severity: grave Justification: renders package unusable During setup of python-imaging the following happens: Setting up python-imaging (1.1.5-8) ... Traceback (most recent call last): File /usr/bin/pycentral, line 1314, in ? main() File

Bug#373856: python2.4-minimal: Install/Upgrade fails: TypeError: unindexable object

Package: python2.4-minimal Version: 2.4.3-7 Severity: grave Justification: renders package unusable During configuration the following happens: Setting up python2.4-minimal (2.4.3-7) ... Traceback (most recent call last): File /usr/bin/pycentral, line 1365, in ? main() File

Bug#487761: postinst overwrites /etc/imapproxy.conf with empty file

Package: imapproxy Version: 1.2.6-3 Severity: critical The postinst overwrote my working /etc/imapproxy.conf with an empty file and thus causes the daemon to fail to start and consequentially all applications using the proxy. ds9:/etc # ls -al imapproxy.conf -rw-r--r-- 1 root root 4121 Jun 24

Bug#487761: Re postinst overwrites /etc/imapproxy.conf with empty file

Here is a -x version of the postinst. Setting up imapproxy (1.2.6-3) ... + '[' -e /usr/share/debconf/confmodule ']' + . /usr/share/debconf/confmodule ++ '[' '!' '' ']' ++ PERL_DL_NONLAZY=1 ++ export PERL_DL_NONLAZY ++ '[' '' ']' ++ exec /usr/share/debconf/frontend

Bug#487761: postinst overwrites /etc/imapproxy.conf with empty file

Um 10:59 Uhr am 24.06.08 schrieb José Luis Tallón: Which PERL version are you using? (i.e. what does perl -version say) This is perl, v5.10.0 built for i486-linux-gnu-thread-multi perl: Installed: 5.10.0-11 Candidate: 5.10.0-11 Version table: Grüße, Sven. -- Sven Hartge

Bug#487761: Re postinst overwrites /etc/imapproxy.conf with empty file

processing: imapproxy And again imapproxy.conf is empty: [EMAIL PROTECTED]:/etc# ls -al imapproxy.conf -rw-r--r-- 1 root root 0 24. Jun 11:41 imapproxy.conf During installation I get only asked on debconf question about the ip to listen on (with localhost being the default). Grüße, Sven -- Sven

Bug#487761: Re postinst overwrites /etc/imapproxy.conf with empty file

José Luis Tallón wrote: I have produced a fixed version. Please test it so that we can double-check before having this uploaded. Looks fine to me. Grüße, Sven. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#470485: fuse-utils fail to configure

node creation. else # Call makedev and fix perms cd /dev; MAKEDEV fuse chgrp fuse /dev/fuse fi As far as I know, /dev/.udev is guaranteed to be present while udev is active. No need to grep /proc/mounts or anything else. Grüße, Sven. -- Sven Hartge -- professioneller Unix

Bug#448253: azureus: uninstallable in Sid, missing libswt-gtk-3.3-java

Package: azureus Version: 3.0.3.4-1 Severity: grave Justification: renders package unusable Azureus is uninstallable in Sid: azureus: Depends: libswt-gtk-3.3-java which is a virtual package. This also causes an additional FTBFS bug. -- System Information: Debian Release: lenny/sid APT

Bug#554537: postinst failes with exit status 30

Christian Perrier wrote: At first glance, it seems that replacing all db_input foo/bar by db_input foo/bar || true (in isdnutils-base.config, for instance) could be what makes things work *without* set +e. Untested, though Some other packages have been bitten by this recently (but I can't

Bug#563427: fails since installation of bash-4.1

Package: localepurge Version: 0.6.1 Severity: grave Hi. Since the installation of bash-4.1 on my system, localepurge does not work any more: , | :/root # bash --version | GNU bash, version 4.1.0(1)-release (i486-pc-linux-gnu) | Copyright (C) 2009 Free Software Foundation, Inc. |

Bug#520499: lsb-base upgrade breaks init scripts at least of gdm

Pablo López Martín wrote: Its a bug in /lib/lsb/init-functions start_daemon function in /lib/lsb/init-functions has a bug in 3.2-21. I changed: args=--start --chdir '$PWD' --nicelevel $nice --quiet --oknodo to: args=--start --chdir $PWD --nicelevel $nice --quiet --oknodo and it works.

Bug#542810: update from sqlite2 will fail because of AUTOINCREMENT in table definition

Package: bacula-director-sqlite3 Version: 3.0.2-1 Severity: serious Hello. During the update from a previous sqlite2-base director, the postinst runs the following command: sqlite $DB .dump | sqlite3 $DB.sqlite3 This will fail on older installations of bacula-director-sqlite, because the

Bug#542810: update from sqlite2 will fail because of AUTOINCREMENT in table definition

Addendum: After further experimentation I discovered the following facts. Given a schema like this, 'x' _will_ autoincrement on insert: CREATE TABLE t1 ( x INTEGER, name TEXT DEFAULT , PRIMARY KEY(x) ); Give a schema like this, with added UNSIGNED after INTEGER, 'x' *will not*

Bug#542810: update from sqlite2 will fail because of AUTOINCREMENT in table definition

John Goerzen wrote: Thanks for the report. I am initially unsure what to do about it either, and have opened an upstream report at the above URL. http://bugs.bacula.org/view.php?id=1351 Quote from Kern Sibbald: | Converting from SQLite2 to SQLite3 is easy. You simply export or | dump the

Bug#542810: [Fwd: [bacula 0001351]: SQLite tables lack autoincrement -- also implications for upgrades from SQLite 2]

John Goerzen wrote: I am curious, then, where the AUTOINCREMENT came from, and which specific older Bacula version you think it may have been in? I really don't know. But I never manually altered the database. But, look here: o...@hild:~/apt/bacula-2.4.4/updatedb$ grep AUTOINCREMENT *

Bug#542810: [Bacula-devel] Sqlite3 and autoincrement

Kern Sibbald wrote: Based on the information you provided below, I have reopened the bug report and posted my suggested fix. Sorry that I missed the fact that the Bacula developers added the offending AUTOINCREMENT. I would appreciate a confirmation to the bug report whether or not my

Bug#542810: [Bacula-devel] Sqlite3 and autoincrement

Kern Sibbald wrote: On Monday 24 August 2009 02:17:29 Sven Hartge wrote: Kern Sibbald wrote: Based on the information you provided below, I have reopened the bug report and posted my suggested fix. Sorry that I missed the fact that the Bacula developers added the offending AUTOINCREMENT. I

Bug#542810: [Bacula-devel] Sqlite3 and autoincrement

Sven Hartge wrote: Kern Sibbald wrote: Based on the information you provided below, I have reopened the bug report and posted my suggested fix. Sorry that I missed the fact that the Bacula developers added the offending AUTOINCREMENT. I would appreciate a confirmation to the bug report

Bug#594379: haveged: FTBFS: Architecture mismatch on rd. Requires v9|v9a|v9b; requested architecture is sparclite.

Steve Kostecke said: Jakub Wilk said: haveged failed to build from source on sparc[0]: haveged only supports x86 and amd64. This is not completely true. The code should still support SPARC (and ia64 and ppc), but the Debian SPARC port has a 32bit (aka sparclite) userland (with a 64bit kernel)

Bug#594379: haveged: FTBFS: Architecture mismatch on rd. Requires v9|v9a|v9b; requested architecture is sparclite.

On 17.10.2010 00:20, intrigeri wrote: Sven Hartge wrote (13 Sep 2010 23:21:35 GMT) : Steve Kostecke said: Jakub Wilk said: haveged failed to build from source on sparc[0]: haveged only supports x86 and amd64. This is not completely true. The code should still support SPARC (and ia64

Bug#601768: does not configure during upgrade

Package: isdnutils-base Version: 1:3.9.20060704+dfsg.2-5 Severity: grave Hi. During upgrade and configure, the following happens: Setting up isdnutils-base (1:3.9.20060704+dfsg.2-5) ... dpkg: error processing isdnutils-base (--configure): subprocess installed post-installation script returned

Bug#617763: possible fix... regarding #629207, #629310, #631284, #617763

Michael Schmitt tcwardr...@gmail.com wrote: I had a brief conversation about that issue with a develeoper of compiz on IRC (#compiz@freenode): 14:54:12 maniac103 you can cite: 'A simple recompile of the compiz(-gnome) package should be sufficient to get things in order again' He could

Bug#674832: FTBFS: xattr test fails if /tmp on tmpfs

Package: obnam Version: 0.29-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi Lars, during a rebuild of obnam I stumbled upon the following error: FAIL: xattr-change-only: stderr diff: --- /dev/null 2012-05-27

Bug#674834: FTBFS: test convert5to6 fails on FS w/o nanosecond resolution

Package: obnam Version: 0.26-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi Lars, during a rebuild of obnam I discovered the following error: on a filesystem without nanosecond resolution the convert5to6 test fails:

Bug#676432: wine-bin: fails to upgrade: update-alternatives: error: alternative link /usr/share/man/de.UTF-8/man1/wine.1.gz is already managed by wine.1.de.UTF-8.gz (slave of wine).

Package: wine-bin Version: 1.4-3 Severity: serious Justification: fails to upgrade Hi Wine Maintainers, during upgrade to 1.4-3 on Sid the following happens: Setting up wine-bin (1.4-3) ... update-alternatives: error: alternative link /usr/share/man/de.UTF-8/man1/wine.1.gz is already managed

Bug#676598: libwine-bin: trying to overwrite '/usr/share/man/man1/regedit.1.gz', which is also in package wine-bin 1.4-3

Package: libwine-bin Version: 1.4-4 Severity: serious Justification: does not upgrade Hi Wine Maintainers, during the upgrade from 1.4-3 to 1.4-4 the following happens: Preparing to replace libwine-bin:i386 1.4-3 (using .../libwine-bin_1.4-4_i386.deb) ... Unpacking replacement libwine-bin:i386

Bug#728529: libselinux1: causes ld.so error in smartctl/smartd

Package: libselinux1 Version: 2.2-1 Severity: critical Justification: breaks unrelated software Hi! The recent upgrade auf libselinux1 to version 2.2-1 in unstable causes smartctl and smartd to fail with the following message: system:~# smartctl Inconsistency detected by ld.so: dl-version.c:

Bug#757605: libfreerdp1: changes to soname cause remmina RDP plugin to fail

On 05.09.2014 16:00, Julien Cristau wrote: On Mon, Aug 11, 2014 at 22:14:06 +, Mike Gabriel wrote: I guess, the approach needs to be: (a) provide proper shared libs packages for each libfreerdp-* and libwinpr-* shared lib (b) make remmina et al. use generic .so files

Bug#757605: fixed in freerdp 1.1.0~git20140921.1.440916e+dfsg1-1

On Tue, 23 Sep 2014 12:00:12 + Mike Gabriel sunwea...@debian.org wrote: Source: freerdp Source-Version: 1.1.0~git20140921.1.440916e+dfsg1-1 We believe that the bug you reported is fixed in the latest version of freerdp, which is due to be installed in the Debian FTP archive. Umm, how

Bug#757605: fixed in freerdp 1.1.0~git20140921.1.440916e+dfsg1-1

On 24.09.2014 10:20, Mike Gabriel wrote: In a private post you mentioned that current remmina-master is completely broken and the remmina-gtk3 branch still uses the old freerdp-1.0 cmake rules (this seems easy to fix, actually). Yes, see here:

Bug#745794: chromium FTBFS on i386 leaves users w/o security support

The reporter of bug #745794[1] suggested that it's enough to add the proper build-dependency on libkrb5-dev. Is this correct, or are there other problems that make finding a fix difficult? (FYI: I am no DD, just a normal user.) I tried to rebuild chromium in a pristine Sid chroot with

Bug#748673: chromium-browser: FTBFS, missing protobuf-compiler Build-Depends

James McCoy write: The latest experimental upload didn't include protobuf-compiler in Build-Depends, so the buildd build failed[0]. [0]: https://buildd.debian.org/status/fetch.php?pkg=chromium-browserarch=i386ver=35.0.1916.99-1stamp=1400365223 Also missing: gperf bison ninja-build And

Bug#747135: chromium: FTBFS on i386 due to 32bit linker

Hi! I just tested this by adding gcc (= 4:4.9.0-2exp2), g++ (= 4:4.9.0-2exp2), to the build-deps and rebuilding inside cowbuilder. With gcc-4.9 chromium is finally able to be linked: LINK(target) out/Release/chrome: Finished touch out/Release/obj.target/chrome/chrome.stamp make[1]:

Bug#765871: does not start with new openssl version

Package: freeradius Version: 2.2.5+dfsg-0.1 Severity: grave Hi! After the recent upgrade of openssl, freeradius does not start anymore. freeradius -X results in the following message: libssl version mismatch. Built with: 1000109f Linked: 100010af After recompiling the package everything is

Bug#772703: postinst fails because of wrong path to 90-sieve-extprograms.conf

Package: dovecot-sieve Version: 1:2.2.13-9 Severity: grave Hi! The postinst of the dovecot-sieve package searches for 90-sieve-extprograms.conf in the wrong place: Setting up dovecot-sieve (1:2.2.13-9) ... Error: The new file /usr/share/dovecot/90-sieve-extprograms.conf does not exist! dpkg:

Bug#799734: missing dependency on libfile-slurp-perl

Package: needrestart Version: 2.3-1 Severity: grave Hi! Subject says it all: needrestart needs libfile-slurp-perl but does not depend on it, resulting in an error: Can't locate File/Slurp.pm in @INC (you may need to install the File::Slurp module) (@INC contains: /etc/perl

Bug#805738: wrong dependency on python-acme

On Sat, 21 Nov 2015 21:56:50 +0100 Sven Hartge <s...@svenhartge.de> wrote: > The following packages have unmet dependencies: > python-letsencrypt : Depends: python-acme (= 0.0.0.dev20151114) but > 0.0.0.dev20151114-1 is to be installed > E: Unable to correct problems, yo

Bug#805738: wrong dependency on python-acme

On Sat, 21 Nov 2015 21:56:50 +0100 Sven Hartge <s...@svenhartge.de> wrote: > In trying to fix #805185 you added a dependency on This is of course bug #805186 Grüße, Sven.

Bug#805738: wrong dependency on python-acme

Package: python-letsencrypt Version: 0.0.0.dev20151114-3 Severity: serious Hi! In trying to fix #805185 you added a dependency on python-acme (= ${source:Upstream-Version}) to the python-letsencrypt package, but this prohibits the installation of that package: The following packages have

Bug#813339: isc-dhcp-server: Update to 4.3.3-7 today makes isc-dhcp-server unable to work

On Tue, 16 Feb 2016 23:10:33 +0100 Pierre Ynard wrote: > Thank you for your efforts to fix most of the issues with the > initscript. There is one other issue with the init-script: The config option points to the same config file:

Bug#818036: "kpartx does not ship multipathd.service but tries to start/stop that service" not fixed in 0.5.0+git1.656f8865-7

On 16.03.2016 09:33, Ritesh Raj Sarraf wrote: > On Tue, 2016-03-15 at 23:35 +0530, Ritesh Raj Sarraf wrote: >> Okay! I'd agree on the last statement. :-) >> I'll fix it soon. >> >> For others who get hit, Sven has mentioned the workaround in this bug >> report. > > Can you test the attached .deb

Bug#818551: golang-golang-x-tools: provides same file '/usr/bin/bundle' as ruby-bundler

Package: golang-golang-x-tools Version: 1:0.0~git20160315.0.f42ec61-1 Severity: serious Justification: Policy 10.1 Hi! The subject says it all: The following packages will be upgraded: golang-golang-x-tools 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get

Bug#818036: "kpartx does not ship multipathd.service but tries to start/stop that service" not fixed in 0.5.0+git1.656f8865-7

On Tue, 15 Mar 2016 22:28:49 +0530 Ritesh Raj Sarraf wrote: > If you upgrade from -5 to -7, you shouldn't be hitting this problem. I > thought about handling the breakage, but that would touch files outside > , which I'm not keen on. > > And Unstable is supposed to have

Bug#818036: "kpartx does not ship multipathd.service but tries to start/stop that service" not fixed in 0.5.0+git1.656f8865-7

On 15.03.2016 18:16, Ritesh Raj Sarraf wrote: > I am not walking away. The failure is 2 folds. If you got hit by -6, on > your machine the (broken) maintainer script gets installed, which you'll > have to manually remove. No, I do not. It is your job as package maintainer to clean this up. You

Bug#832357: [pkg-bacula-devel] Bug#832357: bacula-director-*: fails to upgrade from 'sid' - trying to overwrite /etc/init.d/bacula-director

On 24.07.2016 16:44, Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'sid' to 'experimental'. > It installed fine in 'sid', then the upgrade to 'experimental' fails > because it tries to overwrite other packages files without declaring a >

Bug#843838: [pkg-bacula-devel] Bug#843838: Bug#843838: Fail to access config file

On 10.11.2016 16:41, Jörg Frings-Fürst wrote: > Am Donnerstag, den 10.11.2016, 09:25 +0100 schrieb Sven Hartge: >> Was the system in question at some time in the past cloned/copied via >> rsync (without using --numeric-ids) or any other method while having >> been bootet from

Bug#843838: [pkg-bacula-devel] Bug#843838: Bug#843838: Bug#843838: Fail to access config file

On 10.11.2016 18:51, Jörg Frings-Fürst wrote: > I guess that the error is the wrong group. Of course, this is obvious. > But the error comes not from use rsync without --numeric-ids. > I don't use rsync, I have moved the hard disk with dd. > > But also I have no idea from where the dirmngr

Bug#843838: [pkg-bacula-devel] Bug#843838: Fail to access config file

On 10.11.2016 08:05, Jörg Frings-Fürst wrote: > # ls -l /etc/bacula/ > insgesamt 104 > -rw-r- 1 root dirmngr 9343 Feb 20 2016 bacula-dir.conf > -rw-r- 1 root bacula 9156 Aug 18 14:12 bacula-dir.conf.dist > -rw-r- 1 root dirmngr 1024 Sep 29 2013 bacula-fd.conf This looks

Bug#849382: [apt] Every package on the system gets silently upgraded to backports. The result is severe system breakage, malfunctioning and data loss.

On Mon, 26 Dec 2016 14:40:05 +0100 (CET) <34tg...@tutanota.com> wrote: > I use Debian 8 64bit with GNOME installed with standard install > procedure from netinstall and using tasksel. This occured to me the > second time. First time was a year ago, I reinstalled Debian then and > a year after

Bug#849382: [apt] Every package on the system gets silently upgraded to backports. The result is severe system breakage, malfunctioning and data loss.

On 07.01.2017 21:24, Julian Andres Klode wrote: > On Sat, Jan 07, 2017 at 09:15:15PM +0100, Sven Hartge wrote: >> On Mon, 26 Dec 2016 14:40:05 +0100 (CET) <34tg...@tutanota.com> wrote: >> >>> I use Debian 8 64bit with GNOME installed with standard install >>&

Bug#873921: python3.5_3.5.4-3 breaks borgbackup: undefined symbol: PyFPE_jbuf

Package: borgbackup Version: 1.0.11-3 Severity: grave Hi! I am reporting this bug against borgbackup, because I am not sure if the bug is in python3.5 or borgbackup just needs to be binNMUd. Please reassign as you see fit. The upload of python3.5 (3.5.4-3) disables the fpectl extension and

Bug#889144: stricter PIDfile handling breaks several daemons

Um 03:02 Uhr am 03.02.18 schrieb Michael Biebl: > Am 02.02.2018 um 20:07 schrieb Sven Hartge: >> ulogd2 drops its priviliges on its own. It needs to start as root to >> connect to the netlink sockets. > So, ulogd2 creates a directory /run/ulog which is owned by ulog:ulog

Bug#889073: Permission denied on /run/munin/munin-node.pid

Hello! Just for your information: This is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889144 and https://github.com/systemd/systemd/issues/8085 Grüße, Sven. signature.asc Description: OpenPGP digital signature

Bug#889144: stricter PIDfile handling breaks several daemons

On 04.02.2018 17:25, Michael Biebl wrote: > Am 03.02.2018 um 14:35 schrieb Sven Hartge: >> Um 14:00 Uhr am 03.02.18 schrieb Michael Biebl: >>> The alternative afaics would be, that the daemon writes the pid file as >>> munin:munin then (or ulog:ulog for the above case)

Bug#889144: stricter PIDfile handling breaks several daemons

On Sun, 4 Feb 2018 15:41:37 + Simon Kelley wrote: > With my dnsmasq maintainer hat on, the current arrangement looks like this. > > 1) /run/dnsmasq is a directory owned by dnsmasq:nogroup > 2) /run/dnsmasq/dnsmasq.pid gets written by dnsmasq before it drops > root,

Bug#889144: stricter PIDfile handling breaks several daemons

Um 14:00 Uhr am 03.02.18 schrieb Michael Biebl: > Am 03.02.2018 um 13:27 schrieb Sven Hartge: >> Um 03:02 Uhr am 03.02.18 schrieb Michael Biebl: >>> Does munin-node have the same mismatch? >> It has: >> But, as you can see, the directory is also used by the

Bug#871229: /usr/sbin/update-grub: running update-grub segment faults

On Wed, 28 Feb 2018 22:37:41 +0100 Martin Zobel-Helas wrote: > I get segfaults when running update-grub on my Lenovo Thinkpad x270 > running Debian unstable from today. I see the same on my Dell Precision 7520. > Using host libthread_db library

Bug#893844: borgbackup: upgrade of python3-msgpack creates version conflict

On 23.03.2018 11:03, Gianfranco Costamagna wrote: > I don't know what broke it, but seems not a borgbackup issue? This was https://github.com/borgbackup/borg/issues/3515 "DistributionNotFound error with msgpack-python 0.5.0 installed" and also

Bug#919922: Does not start anymore, existing file /var/log/atop/atop_20190120 has incompatible header

Package: atop Version: 2.4.0-1 Severity: grave Hello! After the update tpo 2.4.0-1 atop does not start anymore for me. TL;DR: existing file /var/log/atop/atop_20190120 has incompatible header (created by version 2.3 - current version 2.4) Here the whole debugging session: server:~# systemctl

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

On Mon, 15 Apr 2019 18:10:18 +0200 Vincent Lefevre wrote: > E: Sub-process /usr/bin/dpkg returned an error code (1) > Setting up initramfs-tools (0.133) ... > update-initramfs: deferring update (trigger activated) > Processing triggers for initramfs-tools (0.133) ... > update-initramfs:

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

Um 01:35 Uhr am 16.04.19 schrieb Vincent Lefevre: > On 2019-04-15 23:07:02 +0200, Sven Hartge wrote: >> Could you add "set -x" to the top of >> /usr/share/initramfs-tools/hooks/plymouth to get a clear picture where >> exactly the hook fails? > It is also fc-ca

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

On 16.04.19 14:32, Vincent Lefevre wrote: > On 2019-04-16 01:53:03 +0200, Sven Hartge wrote: >> Try running the following commands as root: >> >> mkdir -p /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d >> cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_0BRFs9/etc/fonts

Bug#927153: plymouth: upgrade fails: /usr/share/initramfs-tools/hooks/plymouth failed with return 134

On 16.04.19 15:12, Vincent Lefevre wrote: > access("/var/tmp/mkinitramfs_0BRFs9//etc/fonts/conf.d/60-latin.conf", R_OK) = > 0 > stat("/var/tmp/mkinitramfs_0BRFs9//var/tmp/mkinitramfs_0BRFs9//etc/fonts/conf.d/60-latin.conf", > 0x7ffc35e33b50) = -1 ENOENT (No such file or directory) >

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

Package: bind9 Version: 1:9.16.1-2 Severity: critical Justification: breaks unrelated packages Hi! The recent upgrade from 1:9.11.16+dfsg-2 to 1:9.16.1-1 causes isc-dhcp-server to die upon start with SIGABRT, creating the following backtrace: 8<

Bug#954736: Upgrade to 9.16.1-1 causes dhcpd to die with SIGABRT

On 22.03.20 19:07, Sven Hartge wrote: > Interestingly, isc-dhcp-server 4.4.1 does not even compile against the > current 9.16 libs from Sid right now. Something is very broken here. I have to correct that part. It seems my checkout from Salsa was wrong, as recompiling the source package

Bug#972455: Does not compile for Linux 5.9

Package: iptables-netflow-dkms Version: 2.5.1-1 Severity: grave Hi! It seems adfc6318 was not enough to be compatible with Linux 5.9, as compilation breaks for me with the following log: ---8<-- DKMS make.log for ipt-netflow-2.5.1 for kernel 5.9.0-1-amd64 (x86_64) Sun 18

Bug#972454: Does not build with Linux 5.9, but new compatible release available upstream

Package: xtables-addons-dkms Version: 3.9-1 Severity: grave Tags: patch Hello! As the subject says: The current version 3.9 does not build with Linux 5.9, but a new upstream release is available. I created a MR in Salsa correcting this:

Bug#972455: Does not compile for Linux 5.9

On 18.10.20 22:50, Axel Beckert wrote: That's strange. Works fine for me. Tested on sid amd64 as well: I tested this on a different system with 5.9 and got the same result and identical make.log. But, and here it becomes strange: It does work on a third system of mine. Question now is:

Bug#979853: fp-compiler-3.2.0: does not install: postinst: line 68: --slave: command not found

Package: fp-compiler-3.2.0 Version: 3.2.0+dfsg-9 Severity: grave Justification: renders package unusable Hi! During postinst the following happens: Setting up fp-compiler-3.2.0:amd64 (3.2.0+dfsg-9) ... Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak"

Bug#979984: breaks on check with "NameError: name 'get_binary_stdin' is not defined"

Package: pyzor Version: 1:1.0.0-5 Severity: grave Hi! The fix for https://bugs.debian.org/923077 seems to have introduced a serious regressing, causing pyzor to stop working on check: ~$ pyzor check < testmail Traceback (most recent call last): File "/usr/bin/pyzor", line 411, in main()

Bug#975376: Fails to build with Linux 5.9.9 because of change in ip_route_me_harder()

Package: xtables-addons-dkms Version: 3.11-1 Severity: grave Hi! Kernel 5.9.9 changes ip_route_me_harder() with commit 46d6c5ae953cc0be38efd0e469284df7c4328cf8 causing a build failure for xtables-addons-dkms: , | In file included from

Bug#1000229: binary package is missing /usr/sbin/memlockd

Package: memlockd Version: 1.3-2 Severity: grave Hello! The subject says it all: The package is missing the binary: , | oweh@ds9:~$ dpkg -L memlockd | /. | /etc | /etc/default | /etc/init.d | /etc/init.d/memlockd | /etc/memlockd.d | /lib | /lib/systemd | /lib/systemd/system |

Bug#997139: bacula: FTBFS: configure: error: cannot find required auxiliary files: config.rpath mkinstalldirs config.guess config.sub ltmain.sh install-sh

Um 21:04 Uhr am 23.10.21 schrieb Lucas Nussbaum: > Relevant part (hopefully): > > touch src/qt-console/tray-monitor/.libs/bacula-tray-monitor > > chmod 755 src/qt-console/tray-monitor/.libs/bacula-tray-monitor > > dh_auto_configure -- --enable-smartalloc --with-tcp-wrappers --with-openssl > >

Bug#1054654: Tries to use LWP::Debug::trace which is long gone from libwww-perl

Package: liblwp-protocol-http-socketunix-perl Version: 0.02-4 Severity: grave Tags: upstream Hi! The module has been broken for a long long time, it tries to unconditionally use LWP::Debug::trace which has been remove from LWP. The attached reproducer shows the problem. There is a forked and

Bug#1054654: Acknowledgement (Tries to use LWP::Debug::trace which is long gone from libwww-perl)

Hello, I misinterpreted the error. LWP::Debug::trace() still exists, but one needs to explicitly add use LWP::Debug; to the code to be able to use it. Either way, the code is still very old, broken in the default state, LWP::Debug only exists for legacy code and should not be used anymore