<html><head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body> I'm following up on this today, because Debian finally got off their lazy butt and uploaded 0.3.6-2 to Debian that addresses the core problems in Debian. However, that does not solve the problems for everything in Ubuntu. With the blessing of the Release team, I did a sync last night (forced) of 0.3.6-2 from Debian Unstable to Ubuntu Lunar, which addresses <a class="moz-txt-link-freetext" href="https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2000077">https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2000077</a> in Lunar. Unfortunately the fix that is applied for this in 0.3.6-2 is interwoven with all the changes from 0.3.3 to 0.3.6 upstream which includes new features. I have not heard back from the Release team on this, or the SRU team, so I'm re-asking this. Is the SRU / Release team willing to let us do a one-time backport from Lunar of 0.3.6-2 to the older releases currently supported (to Bionic but no further backwards)? Thomas <div class="moz-cite-prefix">On 2/1/23 14:26, Thomas Ward wrote: </div> <blockquote type="cite" cite="mid:MN0PR19MB59480B834DC52887CFDED0AE9BD19@MN0PR19MB5948.namprd19.prod.outlook.com"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style>@font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink {mso-style-priority:99; color:#0563C1; text-decoration:underline;}span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri",sans-serif; color:windowtext;}.MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",sans-serif;}div.WordSection1 {page:WordSection1;}</style> <div class="WordSection1"> Hello, release team.<o:p></o:p> Pursuant to a recent change for torbrowser-launcher and Tor Browser, we have a little bit of a conundrum that is leading to a one time request for SRUing the latest `torbrowser-launcher` to all currently supported releases.<o:p></o:p> <o:p> </o:p> With Tor Browser 12 (TB12 for short here), upstream tor browser no longer uses locales, requiring folder cleanup from TB12 and download URL changes in order for things to properly function. Unfortunately, the code changes necessary to implement the changes to torbrowser-launcher are not easily nitpicked and include more than just these fixes, as it has new changes and such to make it work properly. Refer to <a href="https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2000077" moz-do-not-send="true" class="moz-txt-link-freetext"> https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/2000077</a> as the current bug on this.<o:p></o:p> <o:p> </o:p> Debian is behind on updating upstream, so later today I will be preparing a package for Lunar that will have a -0ubuntu1 prefix for the latest upstream version. That works fine in Lunar. It also works fine in Kinetic and in initial tests in Jammy. I’m installing test environments for Focal and Bionic.<o:p></o:p> <o:p> </o:p> The problem here is, though, we have a mix of “new features” and “bug fixes” together – there is no ‘major version bump’ for feature branches vs. ‘bugfix’ branches, making it a comingled problem of “new features” and “bug fixes”. Therefore, I’d like to request a one-time exception for SRU processes to accept the same version packaged for each release using Lunar as a base, and adjusting the packaging as needed accordingly for older releases. That is, this will be an SRU, but it will accept the ‘new features’ that’re part of torbrowser-launcher that were not present in Bionic or Focal but are present in later releases.<o:p></o:p> <o:p> </o:p> Most of the ‘feature’ changes allow choosing additional options, etc. but nothing that as far as I can tell changes the core functionality of the package.<o:p></o:p> <o:p> </o:p> I’m happy to discuss this further with the SRU and Release teams (IRC is always a way to reach me heh), but given the complexities of including the fixes and changes just to make tor browser 12 work with the older launchers, it’d make more sense and ease of fixing this “breaks the launcher tool entirely” issue by simply taking the current version and making it match in the entire packaging structure.<o:p></o:p> <o:p> </o:p> I’m happy to spearhead this, but I wanted to put this to the Release Team and the SRU team for consideration before I go through the process of building all this for the SRU/MRE/Version Bump processes as well.<o:p></o:p> <o:p> </o:p> A full changelog upstream is available on their GitHub - <a href="https://github.com/micahflee/torbrowser-launcher" moz-do-not-send="true" class="moz-txt-link-freetext"> https://github.com/micahflee/torbrowser-launcher</a><o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> Thomas<o:p></o:p> LP: <a class="moz-txt-link-freetext" href="https://launchpad.net/~teward">https://launchpad.net/~teward</a><o:p></o:p> Ubuntu Core Developer<o:p></o:p> </div> <fieldset class="moz-mime-attachment-header"></fieldset> </blockquote> </body> </html>