[Bug 191029] New: [patch] systuils/screen: 4.2.1_2 breaks access to sessions to previous portrevsisions

[bz-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191029

            Bug ID: 191029
           Summary: [patch] systuils/screen: 4.2.1_2 breaks access to
                    sessions to previous portrevsisions
           Product: Ports Tree
           Version: Latest
          Hardware: Any
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: beastie at tardisi.com

Created attachment 143771
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=143771&action=edit
Make being backward compatible to 4.0 an option

screen-4.2.1_2 can't find my screen sessions any more.

# pkg info -E screen
screen-4.2.1_1
# screen -ls
There are screens on:
        18332.prts2     (Attached)
        72554.ports     (Attached)
2 Sockets in /tmp/screens/S-root.
# pkg upgrade
...
# pkg info E screen
screen-4.2.1_2
# screen -ls
No Sockets found in /tmp/screens/S-root.
# ls -al /tmp/screens/S-root
total 8
drwx------  2 root  wheel  512  9 Jun 11:28 .
drwxr-xr-x  3 root  wheel  512  5 Jun 21:14 ..
srwx------  1 root  wheel    0  5 Jun 21:14 2508.prts2
srwx------  1 root  wheel    0  9 Jun 11:28 86107.ports

Yes, it was annoying when 4.2.1 came out on April 30th that my existing screen
sessions were lost.  But, there has been plenty of time to get over the loss,
especially since there have been (at least for me, two reboots due to kernel
updates from freebsd-update.  I did 9.2-RELEASE-p6 on May 18th, and
9.2-RELEASE-p7 on June 5th for my two core servers.)

If being able to find pre-existing 4.0 sessions is so important, at this point
it should be an option to not break things for the rest of us.

Since the application is mutual exclusive on whether its doing sockets or fifos
for functions in its file named 'sockets.c'.

-- 
You are receiving this mail because:
You are the assignee for the bug.