pkgsrc-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: pkg/59417: Multiple Security Issues in Screen



The following reply was made to PR pkg/59417; it has been noted by GNATS.

From: Jonathan Perkin <jperkin%pkgsrc.org@localhost>
To: Taylor R Campbell <riastradh%NetBSD.org@localhost>
Cc: Ricardo Branco <rbranco%suse.de@localhost>, gnats-bugs%NetBSD.org@localhost,
	pkgsrc-bugs%NetBSD.org@localhost
Subject: Re: pkg/59417: Multiple Security Issues in Screen
Date: Fri, 16 May 2025 16:24:18 +0100

 * On 2025-05-16 at 16:05 BST, Taylor R Campbell wrote:
 
 >screen5 seems to be a total disaster and I don't think it should be
 >inflicted on users at all under the package name `screen' or the path
 >`misc/screen'.
 
 FWIW I fully agree, it drops support for illumos, causes regressions, 
 and has no discernible improvements over screen 4.  I don't understand 
 why it was "upgraded".
 
 >I suggest we delete misc/screen altogether (add misc/screen5 if anyone
 >really wants it, which I doubt), and have misc/screen4 install a
 >package named screen4 with
 >
 >SUPERSEDES+=	screen-[0-9]*
 >
 >so that users who had gotten screen-5.* under the misapprehension it
 >is a normal update over screen-4.* will have a chance to restore
 >sanity (except for the part where pkgin SUPERSEDES processing is
 >broken, sigh, but once it is fixed...).
 
 I'd rather misc/screen was restored to 4.x, 5.x moved to misc/screen5, 
 and then perhaps in the future when 5.x is actually an improvement over 
 4.x it can just be updated normally.  All this PKGPATH messing around 
 just breaks binary package upgrades.
 
 That said, I have some incoming fixes for pkgin SUPERSEDES support that 
 are able to handle the php renames, and would likely handle this too.
 
 -- 
 Jonathan Perkin                    pkgsrc.smartos.org
 Open Source Complete Cloud   www.tritondatacenter.com
 


Home | Main Index | Thread Index | Old Index