Bug#440551: patch

Ciao, with this patch start-stop-daemon will wait for mldonkey to shutdown correctly. The timeout was simply got from the apache init script. I hope that this time the Debian bug tracking system don't stop this patch. Trek --- debian/mldonkey-server.init 2007-09-14 04:50:03.0 +0200

Bug#307019: odd counters in log files after reboot

(search the numbers on google groups) and persist in the unstable release. c-ya! 3 http://www.trek.eu.org/ k PGPKey: 7016731A57D4A69B 1A8EE5E90EF2608E (since 1995) #!/bin/sh # # MRTG Debian boot file by Trek [EMAIL PROTECTED] # case $1 in start) if [ -e /etc

Bug#640123: wheezy fresh install

Hi, I have recently installed a new wheezy i386 system and claws-mail fails when checking mail on a POP3 SSL connection with this error message: claws-mail: /build/buildd-cairo_1.12.2-2-i386-1cmzkR/cairo-1.12.2/src/cairo-surface.c:1591: cairo_surface_set_device_offset: Assertion status ==

Bug#697905: persistent naming in crypttab

Package: partman-crypto Version: 56 Hi, I think that using udev persistent device naming in /etc/crypttab would be useful to prevent some dangerous situation, like the following one. I have a 3 disks setup with the first two in raid mode and the third as archive. The swap partitions are

Bug#697913: wine crash with nouveau vieux driver

Package: libwine-gl Version: 1.4.1-4 Hi, there is a bug that prevents to run 3D applications under wine with the nouveau vieux driver. It fails with this error message: err:d3d:wined3d_adapter_init_gl_caps GL_INVALID_ENUM (0x500) from extension detection @ ../../../dlls/wined3d/directx.c /

Bug#697913: wine crash with nouveau vieux driver

On Sat, 12 Jan 2013 16:12:28 +0100 Hilko Bengen ben...@debian.org wrote: A binary package of patched libwine-gl would be really appreciated Please use the packages at http://people.debian.org/~bengen/wine/ Many thanks for the package built with the patch, but unlucky the issue is not resolved.

Bug#698026: libsoup should recommends vs. depends on glib-networking

Package: libsoup2.4-1 Version: 2.38.1-2 Severity: wishlist libsoup actually depends on glib-networking for the SSL/TLS support and, probably, the automatic proxy configuration. The installed size of libsoup is 522KB, where glib-networking depends on 8 other packages with a total installed size of

Bug#681860: xscreensaver-data should recommends vs. depends on libwww-perl

xscreensaver-data actually depends on libwww-perl to download images from the web, disabled by default. The installed size of xscreensaver-data is 1209KB, where libwww-perl depends on 18 others packages totaling 5167KB. I wrote a patch to dynamically load the LWP module at runtime and print an

Bug#681860: xscreensaver-data should recommends vs. depends on libwww-perl

On Sat, 12 Jan 2013 20:54:41 -0800 Jamie Zawinski j...@jwz.org wrote: Actually xscreensaver-text already does something very similar with LWP. Do you mean without? That was my first guess, but xscreensaver-text (in the version included by Debian) uses the Socket module instead of LWP. So I

Bug#658896: please try to downgrade libgcrypt11 to 1.4.6

Hi, can you try to downgrade libgcrypt11 to the version 1.4.6-9? You can download it from: http://snapshot.debian.org/archive/debian/20110807T212024Z/pool/main/libg/libgcrypt11/ this resolved a bug using claws-mail and midori with libgcrypt 1.5, that seems to have problems with its memory

Bug#658739: please try to downgrade libgcrypt11 to 1.4.6

Hi, can you try to downgrade libgcrypt11 to the version 1.4.6-9? You can download it from: http://snapshot.debian.org/archive/debian/20110807T212024Z/pool/main/libg/libgcrypt11/ this resolved a bug using claws-mail and midori with libgcrypt 1.5, that seems to have problems with its memory

Bug#699034: similar bug report

you may find interesting this bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640501 that was fixed downgrading libgcrypt11 to the 1.4.6-9 version from: http://snapshot.debian.org/archive/debian/20110807T212024Z/pool/main/libg/libgcrypt11/ may be it is the same bug? Ciao -- To

Bug#699034: libwebkitgtk-1.0-0: midori and GtkLauncher crash after typing a url (cairo-surface.c assertion)

On Tue, 5 Feb 2013 16:39:37 -0500 (EST) alber...@aol.it wrote: Did you trydowngrading libcrypt11 as mentioned in: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699034#35 Apparently with the downgraded version of libgcrypt11 the bug doesn't show up anymore. If the bug is no more affecting

Bug#699034: libwebkitgtk-1.0-0: midori and GtkLauncher crash after typing a url (cairo-surface.c assertion)

On Thu, 21 Feb 2013 18:33:03 +0100 Alberto alber...@aol.it wrote: I've checked again today after updating the distribution with the latest packages (including also libc6 and nouveau). With libgcrypt11 1.5 the bug is present (with https sites). With libgcrypt11 1.4.6 the bug doesn't show up. I

Bug#699034: libwebkitgtk-1.0-0: midori and GtkLauncher crash after typing a url (cairo-surface.c assertion)

Control: reassign -1 libgcrypt11 Control: affects -1 + libwebkitgtk-1.0-0 Control: severity -1 grave Control: merge -1 640501 On Fri, 22 Feb 2013 22:57:09 +0100 Alberto alber...@aol.it wrote: Since claws-mail doesn't use webkit (except with the Fancy plugin), it think this bug should not be

Bug#699034: Is this fixed in upstream upstream LIBGCRYPT-1-5-BRANCH?

On Sun, 24 Feb 2013 11:44:05 +0100 Andreas Metzler ametz...@downhill.at.eu.org wrote: upstream has a couple of patches in in their LIBGCRYPT-1-5-BRANCH, would you mind checking whether the issue is fixed there? I have built binary packages for i386, and have temporarily uploaded them to

Bug#699034: Is this fixed in upstream LIBGCRYPT-1-5-BRANCH?

On Sun, 24 Feb 2013 16:34:32 +0100 Andreas Metzler ametz...@downhill.at.eu.org wrote: relevant patches. Could you please test whether http://people.debian.org/~ametzler/libgcrypt11_1.5.0-3+test+2_i386.deb also does the trick? It just adds three patches

Bug#550891: It is a libfarstream packaging bug

In the effort to reduce the pidgin dependencies, I wrote a patch to dynamically load libfarstream only if it is installed. I never coded with GObjects and so only during the testing to finish the patch I realized that there is no need to modify the code. Only the package dependencies should be

Bug#550891: It is a libfarstream packaging bug

On Sat, 07 Dec 2013 10:28:55 -0500 Ari Pollak a...@debian.org wrote: Thanks for the patch. For the patch to the libpurple source, can you try to get it merged with pidgin upstream? I don't really trust myself to maintain a far-reaching patch that I didn't write, since I am not an expert on the

Bug#711082: black boxes around widgets without composition

Package: libwebkitgtk-1.0-0 Version: 1.8.1-3.4 Tags: upstream I have two rendering bugs with Midori and GtkLauncher on wheezy. The first, black rectangles around gtk widgets are rendered in pages. I have found similar bug reports and screenshots as reference: http://i.imgur.com/b1gOZ.png

Bug#711097: radeon rv100 XVideo diagonal tearing

Package: xserver-xorg-video-radeon Version: 1:6.14.4-8 Tags: upstream playing videos with mplayer causes diagonal tearing on fullscreen with the xv driver, that uses Radeon Textured Video, even if it is played step by step the definition is not an issue as it appears always, as this example:

Bug#668001: please help test proposed patch for bug#668001

the patch works perfectly, I hope it will be included in jessie+1 you can roughly apply the patch on debootstrap 1.0.66 with: patch -r- /usr/sbin/debootstrap 668001.patch patch -r- /usr/share/debootstrap/functions 668001.patch and press enter to any question after patching I can install a new

Bug#21941: dpkg usage of /var

here the example hooks for readonly /usr and noexec /var that should be added to /etc/apt/apt.conf to works with apt-get/aptitude: DPkg { // Auto re-mounting of a readonly /usr and noexec /var Pre-Invoke { mount -o remount,rw /usr mount -o remount,exec /var; }; Post-Invoke { test

Bug#763399: Hardening dpkg/apt

I never submitted a bugreport for that, as I thought it was too paranoid for debian, but while the new version of apt uses a similar method, I want to share the one I used since wheezy to drop privileges: adduser --system --home /var/lib/apt --no-create-home --group apt dpkg-statoverride

Bug#778499: purging does not remove all configuration files

Package: systemd Version: 215-11 purging the systemd package leaves the system dirty, as it does not remove /etc/sytemd/system/*remote-fs* (or something similar) and possibly other files and directories created on postinst one cannot simply remove the /etc/systemd directory as it may contains

Bug#778500: iputils-ping: reconfiguring with setcap leaves the binary suid

Package: iputils-ping Version: 3:20121221-5 Tags: patch I have installed iputils-ping without having setcap, so the /bin/ping* binaries where suid root thanks to the warning message, I have installed libcap2-bin and then ran dpkg-reconfigure on iputils-ping, but even if the setcap was done

Bug#697905: persistent naming in crypttab

as I have installed jessie with debootstrap, I cannot verify if the swap config lines in /etc/crypttab are safe now, but reading the source they are not the patch I proposed 2 years ago sadly run only on linux but not on kfreebsd nor hurd may be that in the meanwhile we can add a warning in the

Bug#779824: claws-mail depends on plugins libraries

Package: claws-mail Version: 3.10.1-2~bpo70+1 installing claws-mail 3.10+ on Debian (jessie and wheezy-backports) results to the installation of libgpgme and thus all the gnupg2 stuff, nearly doubling the required disk space (20.2MB vs 11.9MB on a minimal setup with openbox and iceweasel) the

Bug#823908: bad dependencies

On Tue, 10 May 2016 10:34:37 + (UTC) Gianfranco Costamagna wrote: > Hi, can you please double-check this commit? > > http://anonscm.debian.org/cgit/pkg-gambas/gambas3.git/commit/?id=adacb811579d0bf80fe805829ed707f96d2f6789 > > otherwise feel free to propose a

Bug#823913: remove gconf

Package: pidgin Version: 2.10.12-1 the gconf2 dependency must be removed, as it pollutes desktop environments other than gnome gconf is useful only with gnome, where it is already installed ciao!

Bug#823909: bad dependencies

Package: libfarstream-0.2-5 Version: 0.2.7-1 libfarstream must not depends on gstreamer1.0-plugins-* instead, the application packages should depend on these plugins like any other GIO interface, they are dynamically loaded only if found, so it's up to the user to decide what features want to

Bug#823908: bad dependencies

Package: gambas3 Version: 3.5.4-2 I'm reviving this thread as it was confirmed by upstream developer and has a patch to fix. Basically: - gb.gui technically depends on no components, as it searches for GUI components (gb.gtk, gb.gtk3 and gb.qt4) at runtime. Concretely, it should

Bug#827395: firefox hidden connections

the connections you found can be blocked by changing these configuration directives: browser.newtabpage.enabled security.OCSP.enabled browser.safebrowsing.enabled browser.safebrowsing.malware.enabled privacy.trackingprotection.pbmode.enabled browser.search.suggest.enabled browser.search.update

Bug#868453: xorg flooded by dbus messages

Package: xserver-xorg-core Version: 2:1.16.4-1+deb8u1 Dear maintainer, after the security upgrade from 2:1.16.4-1 to 2:1.16.4-1+deb8u1, I got flooded by dbus messages (which is not installed) every 10 seconds (EE) dbus-core: error connecting to system bus:

Bug#528058: patch

Control: tags -1 patch xfonts-75dpi or 100dpi are required by the X client, but not for the server alone c-ya!--- control.orig 2017-05-15 17:21:30.0 +0200 +++ control 2017-05-15 17:23:22.716441323 +0200 @@ -9,6 +9,7 @@ Package: xfrisk Architecture: any Depends: ${shlibs:Depends},

Bug#791944: /etc/init.d/sendsigs kills systemd-udevd upon shutdown, causing dmsetup to hang

Hi, I can confirm the version 239-7 is affected by this bug and it's fixed by the patch written by Pali Rohár I've added a fix in the maintainer scripts to actually create rc.d symlinks on upgrade and some little lifting to the init.d script thanks to all the people involved! also I would like

Bug#791944: /etc/init.d/sendsigs kills systemd-udevd upon shutdown, causing dmsetup to hang

Hi, I write directly to you, as in the past you pointed out some additional fixes to do is there any remaining work that I can do to get this patch merged? it a really annoying bug, that prevents a clean shutdown/unmount of the system many thanks in advance ciao!

Bug#791944: /etc/init.d/sendsigs kills systemd-udevd upon shutdown, causing dmsetup to hang

On Fri, 7 Sep 2018 19:41:52 +0200 Michael Biebl wrote: > I made an upload today which incorporates that patch (with a small fix > as udev needs a aproper ordering on shutdown against umountroot). I see, thank you, you was faster than me :)

Bug#908796: udev (with sysvinit) fails to find devices at boot

with swaps and filesystems encrypted in plain mode (no luks, no cryptroot) ciao!>From b8f8bcfa1c447bc0839a84c4f64a551278a33dec Mon Sep 17 00:00:00 2001 From: Trek Date: Sun, 7 Oct 2018 17:59:25 +0200 Subject: [PATCH] Stop udev before sendsigs to fix a regression of #791944 The start-stop-daem

Bug#908796: udev (with sysvinit) fails to find devices at boot

r can you check this patch? ciao!>From 67d080cc7c195f1a34cb6a0dc7ac7a5d9dbad28d Mon Sep 17 00:00:00 2001 From: Trek Date: Tue, 16 Oct 2018 21:45:42 +0200 Subject: [PATCH] Set the proper permissions to s-s-d notify socket and directory If the --chuid parameter is specified, the notify socket

Bug#908796: udev (with sysvinit) fails to find devices at boot

good job! with cryptsetup the new patches are running fine thank you to every one! to Guilhem Moulin: I made a little patch because the socket permissions seems to be wrong when --chuid is specified ciao :)>From 67d080cc7c195f1a34cb6a0dc7ac7a5d9dbad28d Mon Sep 17 00:00:00 2001 From: Trek D

Bug#911916: x11-apps: xcacl won't divide correctly on buster

> I was trying to calculate how much carfentanil I needed, and when I > tried 0.2/5000 I got the result 4e-05 it correct, the result is in the e-notation format, where MeN means M*10^N check with bc: $ echo "4*10^-5" | bc -l results in 0.4 exactly like: $ echo ".2/5000" | bc -l can this

Bug#908796: udev (with sysvinit) fails to find devices at boot

break if there are more than one process of udevd) what do you think about? thanks for your time Trek

Bug#908796: udev (with sysvinit) fails to find devices at boot

On Thu, 4 Oct 2018 21:58:38 +0200 Michael Biebl wrote: > > 1) revert the 791944 patch, create a new init.d/udev-clear script to > > remove the control file and run it just after sendsigs (this will > > restore the old well tested behavior) > > The removal of the control file should be bound to

Bug#908796: udev (with sysvinit) fails to find devices at boot

p 17 00:00:00 2001 From: Trek Date: Mon, 1 Oct 2018 06:38:35 +0200 Subject: [PATCH] Wait for udev to be ready before trigger under sysvinit The start-stop-daemon command with the --background argument returns immediately, too soon to trigger events on some systems. Update the SysV init script

Bug#908796: udev (with sysvinit) fails to find devices at boot

On Sat, 29 Sep 2018 18:41:45 +0200 Michael Biebl wrote: > > +# wait for udev to be ready (see #908796) > > +timeout=15 > > +until udevadm control -S || [ $timeout -le 0 ]; do > > +timeout=$((timeout-1)) > > +sleep 1 > > +done > > +

Bug#791944: /etc/init.d/sendsigs kills systemd-udevd upon shutdown, causing dmsetup to hang

On Mon, 3 Sep 2018 16:41:58 +0200 Michael Biebl wrote: > The patch looks fine to me from a cursory glance. I haven't tested it > though. Trek, I assume you built a test package and did a test-upgrade > checking it works as expected? I haven't built a test package, but instead I hav

Bug#908796: udev (with sysvinit) fails to find devices at boot

On Mon, 21 Jan 2019 08:36:51 +0100 Trek wrote: > and the one in the attach missed, sorry attached to this message--- udev.init.orig 2019-01-12 21:49:44.0 +0100 +++ udev.init 2019-01-21 01:54:51.047997585 +0100 @@ -178,7 +178,7 @@ fi log_action_begin_msg "Synt

Bug#908796: udev 240-2: failed to connect to udev daemon (on boot)

On Mon, 21 Jan 2019 16:34:56 + js jb wrote: > I'm surprised at the change between udev_240-2 and udev_240-4, since > I thought the -4 refers only to the debian revision but it resultedin > a significant change in the package's usability. some patches were gracefully backported from the

Bug#908796: udev (with sysvinit) fails to find devices at boot

On Sun, 13 Jan 2019 20:11:04 +0100 Michael Biebl wrote: > Can you test https://github.com/systemd/systemd/pull/11349 I have built and tested udev 240-4 with these patches: https://github.com/systemd/systemd/commit/3797776e11d2a242517c3a20a953b5d0e80384f8.patch

Bug#908796: udev (with sysvinit) fails to find devices at boot

On Sun, 13 Jan 2019 20:11:04 +0100 Michael Biebl wrote: > Can you test https://github.com/systemd/systemd/pull/11349 I've just figured out how to download the patch from github I assume that you would apply this patch

Bug#888106: initramfs-tools: mkinitramfs should fail when ldd fails in copy_exec

On 23 Jan 2018 13:49:30 +0100 Andrew Shadura wrote: > The return code of ldd is not handled at all. Should ldd fail for any > reason, this failure will be ignored. with this code, failures of ldd should be handled ldd_output=$(ldd "${src}" 2>/dev/null) || return $? for x in $(echo

Bug#916696: initramfs-tools: search for nonexistent resume device

Package: initramfs-tools Version: 0.132 at boot, initramfs blocks searching for a resume device Begin: Waiting for suspend/resume device ... Begin: Running /scripts/local-block ... done. I'm using sysvinit and two encrypted swap partitions the file /etc/initramfs-tools/conf.d/resume does not

Bug#908796: udev (with sysvinit) fails to find devices at boot

Hi, is there any blocking to fix this bug? can I help in some way? this is nearly a release critical bug, as it "makes unrelated software on the system break" (cryptsetup) and "the whole system" (some system don't boot) if dpkg can't be upgraded before the freeze, can we add a workaround to the

Bug#610719: dpkg: [S-S-B] make start-stop-daemon find out the pid of forked processes

this patch would be really useful for daemons like udev that does not create the pidfile (bugs #791944 and #908796) ciao!

Bug#918009: firmware-amd-graphics: please add amdgpu firmware for kaveri

Version: 20180825+dfsg-1 I confirm the problem, it leads to a crash of the amdgpu module if the 4.19 kernel is booted with amdgpu.cik_support=1 radeon.cik_support=0 for further informations see https://bugs.freedesktop.org/show_bug.cgi?id=107855 comment 2 for the kernel messages and comment 4

Bug#908796: udev (with sysvinit) fails to find devices at boot

Version: 240-2 after upgrading from 239-13 to 240-2, the VGA card is no more recognized on my system, but adding a small sleep fixes the problem if dpkg will not be updated with the new sd-notify interface, I think it would be better to rollback the #791944 patch: the system will not shutdown

Bug#908796: udev (with sysvinit) fails to find devices at boot

dev is just started, but at least it checks if the control socket is listening ciao >From 1c9dd060a25d904aa200c9fdc33e34dc003dd1d8 Mon Sep 17 00:00:00 2001 From: Trek Date: Sat, 15 Sep 2018 05:50:03 +0200 Subject: [PATCH] Wait for udev to be ready before trigger under sysvinit The sta

Bug#908796: udev (with sysvinit) fails to find devices at boot

On Tue, 22 Jan 2019 18:21:43 -0800 Bill Brelsford wrote: > I'm still using version 1.19.2+test2 of dpkg, but without udev's > --wait-daemon argument. The next dpkg (1.19.3) will handle > --wait-daemon; I assume including it in udev will fix the problem..? these are two independent ways to fix

Bug#908796: udev (with sysvinit) fails to find devices at boot

On Fri, 25 Jan 2019 19:14:54 -0800 Bill Brelsford wrote: > It works with a 2-second sleep inserted before the udevadm call. > Sounds familiar.. too much familiar.. :) well, at least we found this patch is absolutely useless regarding this issue hopefully it seems dpkg version 1.19.3 will

Bug#908796: udev (with sysvinit) fails to find devices at boot

On Tue, 5 Mar 2019 09:46:53 +0100 Andreas Henriksson wrote: > You likely also want to include in your patch a debian/control > change that makes udev depend on a new enough dpkg which has the > new flags you're making use of. right, a new patch is attached thank you!diff --git a/debian/control

Bug#908796: udev (with sysvinit) fails to find devices at boot

On Tue, 5 Mar 2019 23:39:00 +0100 Michael Biebl wrote: > Strictly speaking, we should only need either --notify-await when > starting the daemon via s-s-d, or --wait-daemon when calling udevadm > trigger. Using both probably doesn't hurt, but isn't really necessary. correct, actually only the

Bug#908796: udev (with sysvinit) fails to find devices at boot

Control: tag -1 patch hello, the new dpkg version finally landed to testing, so I send you a little patch to enable both --notify-await and --wait-daemon options this patch was tested against dpkg 1.19.5 and udev 241-1 (unstable) all is running fine! (boot and shutdown) I would say a big

Bug#916696: initramfs-tools: search for nonexistent resume device

On Wed, 06 Feb 2019 21:21:57 + Ben Hutchings wrote: > The RESUME variable doesn't have to be set in any particular file. > Please check with: > > grep -rw RESUME /etc/initramfs-tools/initramfs.conf \ > /etc/initramfs-tools/conf.d \ > /usr/share/initramfs-tools/conf.d/

Bug#916696: initramfs-tools: search for nonexistent resume device

On Sun, 10 Feb 2019 17:32:08 + Ben Hutchings wrote: > > I include a patch, tested with and without an ephemeral swap: > > - the second block (-79,9 +83,10) is the actual fix > If you would actually send me the log messages I might understand this > fix, but as it is I don't. I do need to

Bug#908796: udev (with sysvinit) fails to find devices at boot

On Thu, 24 Jan 2019 19:02:54 -0800 Bill Brelsford wrote: > Thanks for the build instructions, Trek. However, dpkg-buildpackage > fails (at test-condition, line 4259 in attached trace file). to workaround these @#!%^&* tests, you should go in the systemd-240 directory and type as us

Bug#878953: libpurple0: please stop linking to libfarstream

I think this bug should be merged with #823909 that was fixed this year while the submitter requested removing libfarstream dependency from libpurple, he was concerned about gstreamer-plugins-bad, that was removed form the dependencies of libfarstream ciao!

Bug#928040: lprng: fails to install

Control: tag -1 patch this patch should fix the issue ciao! diff -urN a/debian/lprng.init.in b/debian/lprng.init.in --- a/debian/lprng.init.in 2012-06-11 09:47:19.0 +0200 +++ b/debian/lprng.init.in 2019-05-17 16:54:10.750983282 +0200 @@ -106,7 +106,8 @@ ;; stop) [ "$VERBOSE" != no

Bug#924640: tt-rss: initscript tt-rss action "stop" failed

Control: tag -1 patch this (untested) patch should fix the issue ciao! diff -urN a/debian/tt-rss.init b/debian/tt-rss.init --- a/debian/tt-rss.init 2019-05-17 17:47:08.174896466 +0200 +++ b/debian/tt-rss.init 2019-05-17 17:52:21.938887893 +0200 @@ -79,7 +79,7 @@ # 1 if daemon was already

Bug#930473: bsdgames: New wtf acronym makes no sense

On Thu, 13 Jun 2019 13:30:51 +0200 Fabian Greffrath wrote: > It's understandable that this was introduced to avoid using the > f-word. How about replacing it with "frick" or "fsck" instead? frick seems to me to be the most appropriate fsck can cause confusion, it is not a filesystem check

Bug#930473: bsdgames: New wtf acronym makes no sense

On Thu, 13 Jun 2019 17:27:33 +0200 Trek wrote: > where is the food: what the heck? no fantasy here? what it means? how > changing the meaning of an utility can be considered acceptable? if we > really want to be boringly polite, then why not "what term for"? sorry, I

Bug#930428: debootstrap should ensure matching _apt uid

On Thu, 20 Jun 2019 09:32:17 +0200 Ansgar Burchardt wrote: > I don't think it is a good idea to require debootstrap to know about > such details. _apt user is standard to debian, but not its uid the _apt user is created by the apt postinst, that cannot know anything about the host system from

Bug#930428: debootstrap should ensure matching _apt uid

On Thu, 20 Jun 2019 22:31:15 +0200 Ansgar Burchardt wrote: > If _apt deserves a special solution, I would suggest assigning the > _apt user a static uid instead of patching debootstrap. it seems to me the simplest approach, from a technical point of view, and it's the one I'm using since _apt

Bug#831828: libgtk2.0-0: GTK+ 2 is not GNOME and should not depend on GNOME icons

On Thu, 13 Apr 2017 16:12:50 +0200 Laurent Bigonville wrote: > And in a lot of cases, not having these icons might IMVHO result in a > degraded user experience. I think this definition perfectly fits the one of the Recommends dependency: The Recommends field should list packages that would

Bug#927904: claws-mail: filtering option does not work as excepted

On Wed, 24 Apr 2019 22:23:55 +0200 Pierre wrote: > The Debian computer is ignoring these rules, and the OpenIndiana > machine is running fine. > For example, if I send a mail from this address to another mail > address, the Debian machine will ignore the filtering action and the > mail will stay

Bug#930019: default-jre wants to uninstall sysvinit-core to install systemd

On Wed, 17 Jul 2019 10:41:39 +0200 Emmanuel Bourg wrote: > I suspect openjdk-11 ends up pulling libpam-systemd in its dependency > graph, which triggers #926316. going up the reverse dependency tree it happens: libpam-systemd (is needed by) dbus-user-session dconf-service

Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

On Tue, 24 Sep 2019 07:28:29 +0800 Ian Campbell wrote: > Has anyone investigated late dynamic binding using a stub library > which merely determines which init is running and then dlopens the > appropriate libsystemd0 of libelogind0 library and forwards the calls > to it? it could be in the

Bug#931867: /lib/init/init-d-script is sourcing /etc/default/* too late

On Thu, 11 Jul 2019 12:05:10 -0500 Justin Pasher wrote: > Moving it above the following block would ensure it's sourced first: this is a chicken-egg problem: init-d-script sources /etc/default/$NAME but $NAME is defined inside /etc/init.d/snmpd (that is $SCRIPTNAME) init-d-script could be

Bug#962350: /etc/init.d/checkfs.sh is not very robust, and fails on missing filesystems.

On Sat, 06 Jun 2020 07:27:18 -0700 Brad Lanam wrote: > /etc/init.d/checkfs.sh fails when trying to check a non-existent > filesystem. Apparently it is trying to run a fsck on a filesystem > that was removed. it seems to be working as expected, but you could disable that behavior adding the

Bug#968038: sysvinit-utils: do_restart fails when not ran from a terminal

you spotted a bug fixed in my patch 7 of 12 a month ago :) http://www.chiark.greenend.org.uk/pipermail/debian-init-diversity/2020-July/003306.html may be someone will apply them, but who knows? ciao!

Bug#962649: init-d-script: fix PIDFILE argument to status_of_proc

Package: sysvinit-utils Version: 2.88dsf-59.3 Control: tags -1 patch the fix for #822674 had a caveat, because status_of_proc cannot parse options after the first non-option argument, as it uses getopts a simple test, where /run/crond.pid contains a running pid: $ . /lib/lsb/init-functions

Bug#971713: sysstat: init or systemd file has overlapping runlevels

lications of removing those overwrites, so I just moved the code before this part the second patch is for the manpage about empty fields, that are allowed by insserv, but probably it could be explained better please to tell me if you need some more info or work to be done :) ciao! >From d6704148edd51

Bug#971713: sysstat: init or systemd file has overlapping runlevels

vels are never undefined, so this additional patch should fix the regression make check now passes all 240 tests thanks for the review and happy hacking! :) >From 4a3b1e90f23792b6f640e8d9bc28c334cafce843 Mon Sep 17 00:00:00 2001 From: Trek Date: Tue, 15 Dec 2020 20:00:18 +0100 Subject: [PATCH 3/3]

Bug#971713: sysstat: init or systemd file has overlapping runlevels

On Mon, 14 Dec 2020 03:54:28 +0100 Lorenzo wrote: > if you are searching in the source under /debian directory, the code > that you are looking for will be written by dh-installinit in place of > the #DEBHEPLER# placeholder, during the build of the package. @Lorenzo oh yeah, many thanks :) so

Bug#971713: sysstat: init or systemd file has overlapping runlevels

On Sun, 13 Dec 2020 11:03:57 +0100 Robert Luberda wrote: > sysstat's init.d has the following lines in /etc/init.d/sysstat > # Default-Start: 2 3 4 5 > # Default-Stop: > I'm not sure how empty Default-Stop is interpreted, so I've just tried it seems to me that on empty Default-Stop the

Bug#971644: [elogind/elogind] System crashed on suspend/hibernate failure (#177)

searching for info, I found this assertion, that made me think the issue could be outside of elogind: This appears to be that Debian in user space tries to trigger the resume when the system is falling to hibernation. https://bugzilla.kernel.org/show_bug.cgi?id=201855#c10 I really don't