Processing commands for cont...@bugs.debian.org:
> forwarded 941758 https://github.com/systemd/systemd/pull/11373
Bug #941758 {Done: Michael Biebl } [systemd] systemd:
StopWhenUnneeded has stopped working for a mount unit
Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/11
user pkg-systemd-maintain...@lists.alioth.debian.org
usertag 941758 + buster-backport
done
Am 07.10.19 um 12:52 schrieb Jonathan Dowland:
> Fair enough, thanks. Realistically I doubt I'll work on one and I'll
> wait instead for buster-backports. But I'll probably have a look to see
> if I can fin
On 03/10/2019 14:06, Michael Biebl wrote:
Am 03.10.19 um 12:43 schrieb Alexandra N. Kossovsky:
My point is, it is a major change in behaviour, and users should be
notified via NEWS.Debian. The notification should include the
instructions how to get the old behaviour.
Ok, it was not clear to m
On Mon, Oct 07, 2019 at 12:49:01PM +0200, Michael Biebl wrote:
A buster-backport, sure, that is defintely going to happen.
The current version of systemd in bullseye is imho in a pretty good
shape, so I might just do a backport of 242-7.
Great.
Alternatively, assuming a reasonable patch can b
Am 07.10.19 um 10:29 schrieb Jonathan Dowland:
> On Sat, Oct 05, 2019 at 02:20:48AM +0200, Michael Biebl wrote:
>> Do you know about automount units?
>> They would be the perfect fit for your use case.
>
> From what I understand they behave like pre-systemd automounting, that
> is, any process tha
On Sat, Oct 05, 2019 at 02:20:48AM +0200, Michael Biebl wrote:
Do you know about automount units?
They would be the perfect fit for your use case.
From what I understand they behave like pre-systemd automounting, that
is, any process that attempted to read/open /backup would cause it to be
moun
