Bug#858034: [Pkg-privacy-maintainers] Bug#858034: Deleting patches

[Ulrike Uhlig]

Hi,

Right, it would not work out of the box without the dependency.

I agree with you that there should be a long term solution such as
creating a vendor specific file. However, right now I have not enough
time to test that in detail and I want to bring out the new upstream
version nevertheless.

So I'll do that for now, leave this bug open and will get back to it later.

Cheers!
u.

Bug#858034: [Pkg-privacy-maintainers] Bug#858034: Deleting patches

[intrigeri]

Hi,

Ulrike Uhlig:
> Indeed, these (old) patches are actually
> not even needed. I've decided to delete them from the packaging. This
> will result in
> * new users will use the default TorBirdy configuration, which uses port
> 9150, or TorBrowser's tor.

Does it imply that xul-ext-torbirdy will need "Depends:
torbrowser-launcher" to work out of the box, and thus shall be moved
to contrib just like e.g. onionshare?

I mean, there are (somewhat) good reasons why OnionShare needs to use
an instance of Tor on which it has full control, hence the dependency
on torbrowser-launcher (until that's fixed thanks to onion-grater :)

But AFAIK it's not the case for TorBirdy, that can very well work out
of the box with the current "Depends: tor" as long as the SOCKS port
is correctly set, so requiring enabling contrib + having a running Tor
Browser feels like a sad outcome wrt. UX; I _personally_ prefer to
live with #858034 being unfixed (until someone tries to fix it in
a nicer way) than to add these requirements to all users of TorBirdy
in Debian. YMMV :)

Sorry if I missed something!

Cheers!
-- 
intrigeri