[Pkg-privacy-maintainers] Bug#1063423: Bug#1063423: obfs4proxy: please package a new version

[meskio]

Quoting John Scott (2025-12-27 17:58:24)
> Ahoy there!
> 
> Matija Nalis wrote:
> > Debian contains old version 0.0.14 of obfs4proxy, new upstream is at 0.8.0
> > https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird
> 
> It's my understanding that the rename was mainly done out of respect for the original author and to acknowledge the new maintainership under the Tor Project folks. So I think the roadmap for inclusion in Debian is like this:
>  • rename the source package and the principal binary package to Lyrebird but retain the contents generally (preserving the old changelog should be possible)
>  • have that source package build an transitional package named 'obfs4proxy', with a version matching the source package version, and which Depends on Lyrebird
>  • have Lyrebird set Replaces appropriately, but after this I'm lost:
>         ◦ If the binaries are renamed too and the packages are, in principle, co-installable, I'm not sure what should happen after that, especially if Tor needs to change its invocation in tandem anyway. If we ship a compatibility symbolic link so Lyrebird can be invoked as 'obfs4proxy' then Breaks + Replaces should be good (to help remove the old obfs4proxy binary package). Since they work alike, though, we probably would want a 'Provides: obfs4proxy' then too?
> 
> I've not actually used this package before but I guess it comes down to whether an automatic transition should, in principle, be possible.
> (These rambling notes are for the benefit of Debian folks who want to know what's going on with respect to the details. Don't concern yourself with these technicalities now.)

I think this plan makes sense, it will make sense to deprecate obfs4proxy as a 
name. AFAIK obfs4proxy doesn't appear configured in the current tor package, 
maybe it is in other packages. But it might make sense to make a symlink from 
/bin/obfs4proxy to /bin/lyrebird for backward compatibility.

There is already an ITP:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111471

And I'm not sure how much Yifei has already advanced on this package, but maybe 
something to check with Yifei (in CC).

-- 
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/attachments/20260101/77421d68/attachment.sig>