#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #898530 (http://bugs.debian.org/898530)
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package systemd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
On Sat 13 Feb 2021 at 15:43:12 +0200, Jari Aalto wrote:
> It's Debian mainter's job to forward bugs to upstream.
If there are jobs to apportion out, yours is to assist a
maintainer, especially one as assiduous in their *volunteer*
work as Michael Biebl, in every possible way.
So - get on with it
Am 02.02.21 um 10:11 schrieb Francesco P. Lovergine:
Well, the truly annoying thing is that it warns even for init scripts
disabled, but never removed (sometimes on purpose, sometimes due to
package errors). I discovered a few of them still around since years,
and reduced
a bit the noisei by p
Since Bullseye already entered the freeze but upstream only got around
reacting to the bug report now, my possibilities for getting crashes
by upgrading something that comes with an init script are slim.
I've compiled systemd packages using this command:
$ DEB_BUILD_OPTIONS="nostrip noopt noudeb"
