[Bug 1761997] Re: /var/run needs mode 777 in bionic

[Brian Murray]

Ah I think it (the tmpfile isn't created) because /usr/bin/screen is
2755 in Ubuntu 16.04 but 755 in Ubuntu 18.04. Here's the change between
the two releases.

 override_dh_auto_install:
-       # can't call the normal install target b/c it installs the info files
-       # and other crud
-       $(MAKE) prefix=$(ROOT)/usr SCREENENCODINGS='$$(prefix)/share/screen/utf8encodings' installdirs install_bin
-       # hack around the fact that the install target makes screen a symlink to screen-$$(VERSION)
-       rm -f $(ROOT)/usr/bin/screen
-       mv -f $(ROOT)/usr/bin/screen* $(ROOT)/usr/bin/screen
-       # make it setgid utmp
-       chown root:utmp $(ROOT)/usr/bin/screen
-       chmod 2755 $(ROOT)/usr/bin/screen
+       # can't call the normal install target b/c it installs the
+       # info files and other crud
+       cd build;      $(MAKE) prefix=$(ROOT)/usr      SCREENENCODINGS='$$(prefix)/share/screen/utf8encodings' installdirs install_bin
+       cd build-udeb; $(MAKE) prefix=$(ROOT_UDEB)/usr SCREENENCODINGS='$$(prefix)/share/screen/utf8encodings' installdirs install_bin
+       # hack around the fact that the install target makes screen a
+       # symlink to screen-$$(VERSION)
+       rm -f      $(ROOT)/usr/bin/screen  $(ROOT_UDEB)/usr/bin/screen
+       mv -f      $(ROOT)/usr/bin/screen*      $(ROOT)/usr/bin/screen
+       mv -f $(ROOT_UDEB)/usr/bin/screen* $(ROOT_UDEB)/usr/bin/screen
+       # make it setgid utmp only in udeb
+       chown root:utmp $(ROOT_UDEB)/usr/bin/screen
+       chmod 2755      $(ROOT_UDEB)/usr/bin/screen
+       chmod  755      $(ROOT)/usr/bin/screen

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1761997

Title:
  /var/run needs mode 777 in bionic

Status in screen package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  [Test Case]
  1) have an Ubuntu 16.04
  2) rm /etc/cron.daily/mlocate (this'll ensure you get a conffile prompt)
  3) ssh to Ubuntu 16.04 system so the release upgrade is run in screen
  4) run do-release-upgrade -d
  5) wait for the conffile prompt from mlocate
  6) ssh to the Ubuntu 16.04 system being upgraded
  7) sudo -i
  8) run screen -rd

  With the version of screen in the release pocket you'll receive the
  following error:

  root at clean-xenial-amd64:~# screen -rd
  Directory '/run/screen' must have mode 777.

  [Original Description]
  I saw some odd behaviour of screen during the upgrade from Xenial to Bionic using do-release-upgrade. I was trying to use screen to reattach to an upgrade process that had gone sideways during a router daemon upgrade (duh). But I was told that the permissions on /run/screen needed to be 777. Does the bionic version of screen have that as a requirement? And if so, perhaps do-release-upgrade should set those permissions in anticipation of the upgrade process so that screen works with both old and new versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1761997/+subscriptions