Bug#1042384: Modifications made for logcheck.logfiles.d break usage of -L option

2023-07-27 Thread phep
Hi, Le 27/07/2023 à 18:12, Richard Lewis a écrit : i think there is a better solution already available you can use the -D option to avoid the standard the logfiles.d directory - set it to -L new.file -D /dev/null or to any empty directory. we do this with /dev/null in the debian tests so i

Bug#1042384: Modifications made for logcheck.logfiles.d break usage of -L option

2023-07-27 Thread phep
Hi, To be more precise, the problem showed up here when logcheck configuration started to use the logcheck.logfiles.d files by default, i.e. when we upgraded some hosts to bookworm. Before that, since there was no files in this directory, concatenating its files contents to the LOGFILES

Bug#1042384: Modifications made for logcheck.logfiles.d break usage of -L option

2023-07-27 Thread phep
As you might have guessed, this implies the lines in logcheck.logfiles.d/journal.logfiles are all commented out in our configurations, we only use syslog.logfiles. Would you mind modifying the logcheck script so that the -L option keeps working as a complete alternative to logcheck.logfiles, as it used to? Thanks in advance, -- phep

Bug#921824: terminator: Impossible to load a layout on startup after upgrading to 1.91-3

2019-02-09 Thread phep
tk.Notebook): num = 0 keys = list(children.keys()) -keys.sort(child_compare) +keys = sorted(keys, key=cmp_to_key(child_compare)) for child_key in keys: child = children[child_key] Cheers, phep

Bug#811116: lxc-ls raises error messages

2016-01-26 Thread phep
Hi, Le 25/01/2016 15:32, Sven Haardiek a écrit : installing cgmanager solved it for me. As you may see in my report, I do have cgmanager installed. Regards, phep

Bug#801749: gdm3: Does not start anymore

2015-11-09 Thread phep
/Xfce_Panel_Plugins for example). HTH, phep

Bug#801749: gdm3: Does not start anymore

2015-11-08 Thread phep
his did not change anything on my box, I really had to downgrade gdm3, which is quite annoying... Tia for any solution that would permit upgrading to the standard version of gdm3. phep

Bug#739190: Add conflict with systemd-sysv

2014-06-26 Thread phep
be to add a conflict with systemd-sysv to avoid the package removal and keeping this bug around as a reminder. Arnaud, what do you think about it? phep -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas

Bug#745169: lxc: Container fails to start 'no ns_cgroup option specified'

2014-04-18 Thread phep
Hi, Le 18/04/2014 18:04, Patrice Pillot a écrit : I wonder if this could come from some conflicts between cgroups handling from lxc vs. libvirt Co... Actually, as soon as I purged libvirt-bin, the problem disappeared and the container could be started. It seems there's a conflict somehow

Bug#732666: [Pkg-libvirt-maintainers] Bug#732666: severity:serious, since it breaks the upgrade

2014-01-01 Thread phep
for this). Yet, as already acknowledged before, I'm anything but a kernel wizard so that I may miss something obvious or be utterly in the blue. Cheers, phep -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#732666: about libvirt commit 96f9aae6a

2013-12-30 Thread phep
to add cgroup_enable=memory on the linux cmd line if one does not want to be left with an half-configured libvirt-bin (on jessie, at last). phep -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#732666: about libvirt commit 96f9aae6a

2013-12-30 Thread phep
Hi, Le 30/12/2013 13:19, Guido Günther a écrit : On Mon, Dec 30, 2013 at 11:23:57AM +0100, phep wrote: Hi, Thank you for packaging libvirt, Since I just hit the problem this morning while upgrading my laptop, I tried applying the changes referenced in the subject line. Alas, as I feared

Bug#732666: about libvirt commit 96f9aae6a

2013-12-30 Thread phep
the kernel cmdline should not be necessary with you patch. On the other hand, this new behaviour might deserve some notice in NEWS.Debian or changelog.Debian at least, yet. Regards, phep -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe