Bug#952470:

2020-04-12 Thread Chris Putnam
I was hit again by this today. In the current state, Netdata is completely broken when it tries to send an email. I have to manually edit the systemd file, which is clobbered by any apt upgrades. I had unattended-upgrades on a bit aggressively and today Netdata broke again, as 1.19.0-3 was pulled

Bug#957088: ledmon: libsgutils2-2 1.45 update breaks ledmon

2020-04-17 Thread Chris Putnam
Package: ledmon Version: 0.94-1 Severity: grave Justification: renders package unusable Dear Maintainer, After updating libsgutils2-2 to 1.45-1, ledmon no longer runs as the library it was linked to is no longer present on the system: ledmon: error while loading shared libraries:

Bug#994521: ledmon: libsgutils2-2 1.46 update breaks ledmon

2021-09-16 Thread Chris Putnam
Package: ledmon Version: 0.95-1 Severity: grave Justification: renders package unusable Dear Maintainer, After updating libsgutils2-2 to 1.46-1, ledmon no longer runs as the library it is linked to (1.45) is no longer present on the system. This happened also when libsgutils2-2 was updated to

Bug#994521: Acknowledgement (ledmon: libsgutils2-2 1.46 update breaks ledmon)

2021-12-25 Thread Chris Putnam
It has now been 3 months since this package has been broken in testing. Is it safe to assume this package is abandoned? On Fri, Sep 17, 2021 at 12:48 AM Debian Bug Tracking System < ow...@bugs.debian.org> wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on

Bug#986634: 7zr ignores umask for output directory

2022-03-28 Thread Chris Putnam
This bug was reported *13 years ago* on Sourceforge and ignored: https://sourceforge.net/p/p7zip/bugs/87/ I reported it again today but I am not holding my breath for the developer to fix it. It would be great to see this simple patch added by the maintainer.

Bug#1012600:

2022-06-19 Thread Chris Putnam
Apologies if this question is well-answered, but why isn't this package holding back the kernel to 5.17? In my mind an "apt upgrade" should not have pulled 5.18, especially when the net result may well be an unbootable system. Surely there's some way to mark this package as broken in tandem with

Bug#1019425:

2022-09-14 Thread Chris Putnam
I would argue the severity of this bug should be raised to grave. This is system-breaking for those that must keep secure boot enabled and are using necessary 3rd party drivers such as NVIDIA or out-of-tree modules like ZFS. As a side note I discovered that despite secure boot being enabled,

Bug#939392:

2022-10-05 Thread Chris Putnam
Is kmodsign necessary? I have been using the `sign-file` tool included in the linux-headers package. It is located at /usr/src/linux-headers-xxx/scripts/sign-file. It is also referenced by the script /etc/dkms/sign_helper.sh, included with the dkms package. Regardless, something happened recently