Comment 2 for bug 1761997

Steve Langasek wrote:
> I believe this is a bug in screen. The postinst script has code to
> handle the changed requirements for /run/screen permissions, but then
> immediately afterwards a debhelper code snippet runs which clobbers them
> again.

I currently don't see that clobbering, at least not in Debian:

The maintainer-written code creates
/etc/tmpfiles.d/screen-cleanup.conf in most cases.

It also links /lib/systemd/system/screen-cleanup.service to /dev/null.

debhelper-generated code seems to create
/usr/lib/tmpfiles.d/screen-cleanup.conf — which is overridden by
/etc/tmpfiles.d/screen-cleanup.conf if it exists.

If it is not created because neither of the two conditions in the
maintainer code is given, I don't see how something which is not
created can be clobbered.

So please elaborate where you see the bug in screen's postinst.
Setting to "invalid" until then. Feel free to reassign or -- if you
can explain where the bug is -- reopen.

(Note: To me this rather looks like a not yet run postinst or similar
during a dist-upgrade.)

  Regards, Axel
--
 ,''`. | Axel Beckert <email address hidden>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
  `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE