On Fri, 22 Mar 2013, Jérémy Bobbio wrote:
George Kadianakis:
That said, what is the best way to update the Debian packages so that they contain the Python codebase?
obfsproxy will be in Wheezy. So in any cases, if the binary package name is going to stay the same, it would probably be better to have a version number for the Python codebase higher than the previous implementation.
Or we just use an epoch. That's what they are for.
Lunar, how did the Debian package creation go? Do you need any help? We should name the new packages 'obfsproxy'.
The package is waiting in the NEW queue: http://ftp-master.debian.org/new/pyobfsproxy_0.0.2-1.html
Do you plan to rename the Git repository, project page and all for the Python codebase? If not, we can have the source package "pyobfsproxy" create a "obfsproxy" binary package that would superseed the package currently in Debian. It could only be done after the actual "obfsproxy" is removed, though.
Should I ask the ftpmasters to remove pyobfsproxy from the NEW queue until we sort this out?
Probably.
If we want to re-use the source package name obfsproxy that's fine with me too.