Guido let me know if you need any help or prod me on IRC if I'm needed.
Will certainly test the result, but if you get stuck would be happy to
spend time on this.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
Sorry, I forgot to add the dmesg output.
In it, you can see the wrong device name "SAVITECH Bravo-X USB Audio" affected
at startup and at the end, when I tried to replicate the issue when
unplugging/plugging it back, the proper name being affected "HiFimeDIY Audio
SA9023 USB Audio".
Sorry
Hi,
On Mon, Apr 15, 2019 at 10:18:18PM +0200, Michael Biebl wrote:
> Hi Sam
>
> Am 15.04.2019 um 20:38 schrieb Sam Hartman:
> > control: severity -1 serious
> >
> > justification: libvirtd upgrades from stretch to buster break causing
> > apt to fail and requiring the admin to get the systemd
Am 15.04.19 um 22:18 schrieb Michael Biebl:
> Using debhelper compat level 12, you are able to completely decouple
> dh_installinit and dh_installsystemd which would give you the ability to
> implement what you want afaics.
From debhelper's changelog:
debhelper (12.1) unstable; urgency=medium
#
# 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 #904913 (http://bugs.debian.org/904913)
control: severity -1 serious
justification: libvirtd upgrades from stretch to buster break causing
apt to fail and requiring the admin to get the systemd units into a
consistent state before things can continue
Unfortunately based on discussion so far this is a complex bug to fix.
Ubuntu's
OUR CORPORATE PHILOSOPHY is to support Investors, Business Men / woman and
enable each individual to maximize future opportunities through effective
use of credit.
As a reflection of this philosophy, OUR MISSION is to provide a wide range
of consumer financial services that best meet customer
Hello Ryan,
Ryan Goodfellow [2019-04-13 23:22 -0400]:
> It seems the systemd package should depend on udev, or at least
> recommend it. The systemd-networkd service requires udev for some
> functionality. See the following as an example of what can happen when
> udev is not present.
systemd