Bug#965088: Re: [Pkg-privacy-maintainers] Bug#965088: Waiting for release 2.3
> 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:35 AM] > 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] intrigeri: Thanks > for caring!
Bug#965088: Re: [Pkg-privacy-maintainers] Bug#965088: Waiting for release 2.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] intrigeri: Thanks for caring! Thanks for the information. On a sociological sidenote: In FLOSS communities, silence (as in: absence of communication) is a means of communication which might have many different meanings and which exist on very different ends of a spectrum; on the one end there could be ignorance, forgetfulness, unavailability (even harder if one of the communicating parties is our single contact point, or SPOF), or even disagreement, while on the other end we can find agreement, implicit consent, the absence of (particular) needs, questions, or concerns. Specifically on Debian mailing lists silence often means agreement. I do find this hard to navigate sometimes! :) Ulrike
Bug#965088: [Pkg-privacy-maintainers] Bug#965088: Waiting for release 2.3
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 Onionshare, see https://github.com/micahflee/onionshare/pull/1208. Version 2.3 has been released (and tag added yesterday). Is it too late for Bullseye? Probably. Indeed. I have no idea how much work is needed to update the Debian package with regard to the huge refactoring of the code in 2.3. (And if that version number should have been a 3.0 instead…) 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. Ulrike
Bug#965088: Waiting for release 2.3
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/micahflee/onionshare/pull/1208. > > Version 2.3 has been released (and tag added yesterday). > Is it too late for Bullseye? Probably. -- Everyone is a terrorist. You're just not pissed enough.
Bug#965088: Waiting for release 2.3
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 released (and tag added yesterday). Is it too late for Bullseye? signature.asc Description: This is a digitally signed message part.
Bug#965088: Waiting for release 2.3
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 onionshare-cli and onionshare-gui (former GUI) to just onionshare * Rearranged the directory structure -- now the CLI project is in cli and the GUI project is in desktop * Ported from PyQt5 to PySide2 -- these are two competing python bindings for Qt5, but PySide2 makes setting up a dev environment much simpler and works with Briefcase greetings, ulrike
