Hi,

Am Wed, Mar 25, 2026 at 12:43:19PM -0500 schrieb Theodore Tso:
> On Wed, Mar 25, 2026 at 11:11:41AM -0400, Frédéric Brière wrote:
> > On Fri, Feb 20, 2026 at 10:29:16AM +0100, Andreas Tille wrote:
> > > As far as I can tell, there is no active upstream anymore, and I am not
> > > aware of ongoing efforts to port xzgv to GTK3 or GTK4.
> > 
> >   https://github.com/fbriere/xzgv/tree/gtk-3
> > 
> > Very little testing and code review has been done yet; my goal in making
> > this pre-pre-pre-alpha version public right now is to show that there's
> > still hope for this little package, and prevent any premature action
> > such as a massive bug-closing if it can be avoided.
> 
> Very cool!

Yes, yes, yes.  I really applause this.

> At the risk of scaring you off, would you at all be
> interested in becoming the new upstream for xzgv?

This was my first thought as well.

> Upstream is at:
> 
>       https://sourceforge.net/projects/xzgv/
> 
> And as you can see, it hasn't been updated in 3 years, and I got added
> as one of the SourceForge project owners so I could get some of the
> bug fixes that got introduced via Debian upstream.  So if we want to
> keep it around, in order to be sustainable, we probably do need to
> find a new official upstream.

... which moves most favourably to a recent Git forge.
 
> I'm willing to help, but (a) I have very little time, and (b) I have
> almost no experience with GtK2 or GtK3 programming.  (What I have was
> trying to fix obvious xzgv bugs.  :-)

Same here.  I have no capacity to do some upstream work.

Usually I can provide patches for bugs like this
   https://bugs.debian.org/1098181
(havn't looked into it yet since I assumed that GTK2 dependency would be
a killer anyway) but no real upstream work from my side.
 
> > Also be warned that proper testing might take a while; although I use
> > xzgv every day, that version includes several patches that would require
> > porting/merging before I would consider switching over.  (I'm hesitating
> > between submitting these well-tested patches upstream *before*
> > finalizing the port, or porting first and submitting these now-rebased
> > no-longer-well-tested patches afterward.  We'll see.)
> 
> We can reach out to Reuben Thomas and see he might be interested in
> waking up and looking at your port, but I suspect it's not all that
> likely.

+1

Thank you in any case for looking into xzgv.

Kind regards
   Andreas.

-- 
https://fam-tille.de

Reply via email to