Hi,

On Thu, Aug 25, 2016 at 09:17:19AM +0100, Tim Retout wrote:
> On 21 August 2016 at 22:36, David Kalnischkies <da...@kalnischkies.de> wrote:
> >> So, assuming we can agree on that this is in general a good idea, this
> >> would leave apt-transport-tor relatively empty (expect three symlinks,
> >> a depends on apt and a recommends on -https & tor) but perhaps this
> >> frees resources for a-t-t to gain an option to turn all sources into
> >> tor+http(s) [with debconf] or even .onion addresses, additional
> >> documentation… instead of diverting energy into maintaining an -https
> >> fork.
[…]
> I'm entirely supportive of merging a-t-t back somehow - I'd be happy
> for the apt team to take over the package.

As mentioned already, my main motivation is getting the codecopy
situation resolved for stretch (as every security problem is basically
magnified by the inbuilt MITM aka exit-node in tor), so any way
achieving it works for me, that said:
The APT team is too small/busy to take care of the existing set of
packages, so while I suggested deity@ as maintainer I just did that as
in my proposed scheme they would be responsible for the technical side
of things – I would very much prefer (a bunch of) people != deity@ to be
the 'real' package maintainers in terms of packaging & documentation as
as mentioned in the quote I think there could be various things done to
improve a-t-t further, but I don't think deity@ will have the time… but
if you and/or perhaps others, who shied away so far fearing they would
need to touch C++ ……… (I have a wild imagination sometimes)

Anyway, as I proposed this mergeback I will see if I can come up with
the relevant packaging changes now instead of just imagining things.


> hope it played some small part in making it easier to use apt through
> tor, and in getting official Debian onion mirrors set up.  But I'm not

The package has a popcon >=250 and I would actually assume most of its
users to not report popcon… not to mention the various references to
a-t-t on the web, so you absolutely had an impact – and I hope you
continue to have! :)


Best regards

David Kalnischkies

Attachment: signature.asc
Description: PGP signature

Reply via email to