| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
The package is hardly needing any specific version, but
bumping it once in a while to keep us away from ancient
versions seems like a good idea.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Silly me wrote the URI in the control file before having actually
created the repository… lets not think too deeply about what a
"tranport" might be. Sounds 'fishy' at least…
|
| | |
|
| |
|
|
|
|
|
|
| |
The default configuration will make use of a local tor instance, but
there is nothing technically stopping a user from configuring the use
of a remote tor instance via the Acquire::tor::Proxy option.
Closes: #812490
|
| |
|
|
|
|
| |
The package itself builts no binaries anymore and just symlinks to
binaries in an architecture-independent directory with an
architecture-independent interface.
|
| |
|
|
|
|
|
| |
The technical side of tor support is handled mostly by the apt package
itself, so it makes sense to have the team as maintainer to have
potential bugreports end up there as well as having one of its current
members (me) in the uploader list.
|
| |
|
|
|
|
|
|
|
| |
APT 1.3 supports socks5h proxies out of the box now, so instead of using
a copy of the -https transport as a proof of concept, we can now
deligate all of the technical implementation details to APT via a few
simple symlinks.
Closes: #835128
|
| | |
|
| |
|
