On Thu, Jan 16, 2014 at 06:48:55PM +0100, Michael Biebl wrote:
> As you probably noticed, systemd ships a generator for cryptdisks which
> dynamically creates units and hooks them up in cryptsetup.target.
I know. I also found out that cryptsetup.target makes it impossible to
port the current cryptsetup/lvm2 setup to systemd, which relies on
cryptdisks-early -> lvm2 -> cryptdisks.
What I have problems with is _your_ handling of the whole thing. If
something can not work, it have to fail loud. You however decided to
make it fail silent, you did not document it and didn't inform
the maintainers of affected packages.
> I still hope we can convince you to ship a systemd service file for
> lvm2.
Well. There is no other solution available anyway.
> Since this only affects lvm2, this looks like the cleanest solution overall.
If only lvm2 is affected, why was this override added in the first
place?
Bastian
--
It would be illogical to kill without reason.
-- Spock, "Journey to Babel", stardate 3842.4
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
