> That said, we might be able to provide a backport, as this has been >
> requested multiple times. Nodens could check with Tails if they would > want
> a backport - which would make it more of a priority for us to > maintain a
> backport. Quoting a reply by intrigeri from tails-dev MUC: 11:41:3
Hello!
intrigeri: IMO, there's no rush and it's OK for us to delay the upgrade (and
dealing with any Tails-specific integration work) until we upgrade to Bullseye.
[11:42:15 AM] intrigeri: If we had any other need/requirement on this front, we
would have let nodens know 🙂 [11:42:46 AM] intrig
Hello,
On 22.02.21 21:34, Antoine Beaupré wrote:
On 2021-02-22 21:13:40, Diederik de Haas wrote:
On Sat, 14 Nov 2020 23:14:12 +0100 Ulrike Uhlig wrote:
I did not forget about this, but I'm waiting for 2.3 to be released, as
there has been some huge refactoring which concerns the packaging of
On 2021-02-22 21:13:40, Diederik de Haas wrote:
> On Sat, 14 Nov 2020 23:14:12 +0100 Ulrike Uhlig wrote:
>> I did not forget about this, but I'm waiting for 2.3 to be released, as
>> there has been some huge refactoring which concerns the packaging of
>> Onionshare, see https://github.com/micahfle
On Sat, 14 Nov 2020 23:14:12 +0100 Ulrike Uhlig wrote:
> I did not forget about this, but I'm waiting for 2.3 to be released, as
> there has been some huge refactoring which concerns the packaging of
> Onionshare, see https://github.com/micahflee/onionshare/pull/1208.
Version 2.3 has been release
Hi!
I did not forget about this, but I'm waiting for 2.3 to be released, as
there has been some huge refactoring which concerns the packaging of
Onionshare, see https://github.com/micahflee/onionshare/pull/1208.
Among other things, what was done there is:
* Renamed onionshare (former CLI) to oni
6 matches
Mail list logo
