On Tue, 09 Apr 2013, George Kadianakis wrote:
> weasel, would you do the honors?
>
> I guess what must be done is:
> - Move /obfsproxy.git to /pluggable-transports/obfsproxy-legacy.git .
> - Move /pluggable-transports/pyobfsproxy.git to
> /pluggable-transports/obfsproxy.git .
> - Add redirects o
"George Kadianakis" writes:
>> George Kadianakis:
>>> we have decided to keep the Obfsproxy name and simply replace the old C
>>> codebase with the new Python codebase. It seems that 'obfsproxy' is an
>>> extremely powerful brand name and changing it will result in user
>>> confusion.
>>>
>>> Tha
Another issue that Lunar raised in IRC is whether bridge operators
will have to change their torrc after they upgrade to the new
obfsproxy package.
The answer (unfortunately) is yes; the obfsproxy torrc line will have
to change in two ways after an upgrade:
a) Bridge operators will have to change
> George Kadianakis:
>> we have decided to keep the Obfsproxy name and simply replace the old C
>> codebase with the new Python codebase. It seems that 'obfsproxy' is an
>> extremely powerful brand name and changing it will result in user
>> confusion.
>>
>> That said, what is the best way to updat
> George Kadianakis:
>> we have decided to keep the Obfsproxy name and simply replace the old C
>> codebase with the new Python codebase. It seems that 'obfsproxy' is an
>> extremely powerful brand name and changing it will result in user
>> confusion.
>>
>> That said, what is the best way to updat
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 probabl
George Kadianakis:
> we have decided to keep the Obfsproxy name and simply replace the old C
> codebase with the new Python codebase. It seems that 'obfsproxy' is an
> extremely powerful brand name and changing it will result in user
> confusion.
>
> That said, what is the best way to update the De
Greetings (Debian) people,
we have decided to keep the Obfsproxy name and simply replace the old C
codebase with the new Python codebase. It seems that 'obfsproxy' is an
extremely powerful brand name and changing it will result in user
confusion.
That said, what is the best way to update the Debi
