On Mon, Oct 27, 2025 at 08:23:16PM -0700, Tianon Gravi wrote:
> On Mon, 27 Oct 2025 at 20:20, Tianon Gravi <[email protected]> wrote:
> > We should probably be careful with this one, as the upstream
> > repository is already explicitly deprecated/unmaintained
> > (https://github.com/creack/goselect):
> >
> > > This repository was archived by the owner on Apr 10, 2025. It is now 
> > > read-only.
> > > ...
> > > Keeping the repository for reference, but please, consider moving to 
> > > something more modern and portable than select(2).
> >
> > ♥,
> > - Tianon
> >   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
> 
> Not sure exactly where my brain is tonight, sorry -- I thought this
> was an ITP, not just looking for a sponsor for an update.  Carry on!
> 🤦
> 
> (Although the point still stands - we should probably think about
> patching out this library from the other upstream and/or deprecating
> both if upstream isn't willing to find something else or take over the
> library.)
> 

Thank you Tianon for the feedback -- 

Agreed that the archived library golang-github-creack-goselect requires future
attention and should be deprecated/removed in time.

I just learned about about the archived status this week while updating the
package, and had tried to note it in the package debian/changelog.  I'm
currently working to update the package dependencies for `pat' and have yet to
explore how that upstream project is planning to handle this archived
dependency.  Given `pat' is in active development, I expect they will also
desire a long term stable solution.

May this 0.1.3-1 golang-github-creack-goselect package be processed for now,
and revisit removal after I learn more how `pat' is evolving?  Alternately, I
can pause this update and research other avenues.


    https://github.com/creack/goselect

    https://github.com/la5nta/pat/wiki

    https://getpat.io/
    
    https://qa.debian.org/developer.php?login=donfede%40casagrau.org


Regards,

donfede




Attachment: signature.asc
Description: PGP signature

Reply via email to