Bug#800388: PathChanged triggers too early, not just when file is closed

[Luca Boccassi]

Control: unblock 799782 by -1
Control: tags -1 upstream
Control: close -1

On Mon, 28 Sep 2015 20:27:17 +0200 Joachim Breitner
<nomeata at debian.org> wrote:
> Package: systemd
> Version: 226-3
> Severity: normal
> Control: block 799782 by -1
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> local-apt-repository ships with the following file:
> 
> $ cat /lib/systemd/system/local-apt-repository.path
> [Path]
> PathChanged=/srv/local-apt-repository
> 
> [Install]
> WantedBy=paths.target
> 
> If a process opens a not-yet-existing file in /srv/local-apt-
repository,
> starts writing and eventually closes it that systemd would activate
the
> corresponding service only after the close – at least that is my
reading
> of systemd.path(5).
> 
> This can be reproduced by installing local-apt-repository, and
running
> 
> $ pv -L 100 < .../some.deb > /srv/local-apt-repository/some.deb
> 
> and observing in the journal that dpkg-deb complains about an invalid
> file.
> 
> Is the documentation misleading me here, or is there a bug?
> 
> If it is not a bug: Would it be possible to provide the behaviour
that
> was hoping for here?
> 
> Thanks,
> Joachim

It looks like this was worked around a long time ago, and no updates
since. We do not patch nor reconfigure path units behaviour downstream,
so any issue with them needs to be tested in unstable on the latest
version and then reported upstream.

-- 
Kind regards,
Luca Boccassi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20240526/5cb92bc1/attachment-0001.sig>