[00:04] <vorlon> teward: FFe is to file a bug and subscribe ~ubuntu-release
[00:04] <vorlon> Eickmeyer: removals are not handled by the auto-sync
[00:05] <Eickmeyer> vorlon: Yeah, I realized that after I posted that, and realized it requires a removal bug.
[00:05] <teward> vorlon: ack i'll file the bug (looks like requestsync has the -e flag for that) - and see if we can't get this in.
[00:05] <vorlon> Eickmeyer: ok. and no, you don't have to file a removal bug for a package removed from Debian unstable
[00:06] <teward> that will fix a critical level bug in the package (E:UNUSABLE) and from there I can poke the TB and Release teams for a one time exception to copy the package to the older releases since thte latest breakage was nasty.  (I'm looking into whether this is snappable)
[00:06] <teward> (for the long term future)
[00:06] <Eickmeyer> vorlon: I think Ukikie's worry is that they don't want it removed for this release.
[00:07] <vorlon> teward: if the package is currently broken then it doesn't need an FFe.  FFe is for features not bugfixes
[00:07] <teward> vorlon: therein lies the chaos
[00:07] <teward> it's *not* just a bugfix release
[00:07] <teward> it includes other changes in the system for translations, additional feature changes, etc. because of a full v bump
[00:07] <teward> (and upstream doesn't have separate feature branches)
[00:08] <vorlon> teward: ok but if the current package is *unusable* then there's no risk of regression and no need for an FFe
[00:08] <teward> vorlon: ack, so, JFDI then with the sync with my coredev?
[00:09] <vorlon> Eickmeyer: well anyway, that one was blocked from removal because it was seeded.  Now that it's no longer seeded, I'll remove it right now (<-- Ukikie)
[00:09] <Eickmeyer> vorlon: I see. ack
[00:12]  * Eickmeyer is learning details
[00:15] <teward> vorlon: given that the package is broken (#2000077 indicates download URLs are broken and this also breaks the launcher functioning on upload and can't be used to spawn *new* torbrowser sessions in userspace as designed) I just did the syncpackage call and that looks like it's accepted for Lunar
[00:16] <teward> the only Ubuntu specific deltas I noticed were the pull from upstream of a python float strict check but that's fixed now in upstream so heh.
[00:16] <teward> (in case anyone asks)
[00:17] <teward> guiverc: see above RE your poke on that bug on the 13th.
[00:17] <Ukikie> vorlon: Thanks!
[00:18]  * guiverc smiles; thanks all !
[05:12] <vorlon> Eickmeyer: speaking of, Debian removed muon as 'abandoned upstream' but several flavors still seed it including ubuntustudio; can that be dropped?
[15:36] <Eickmeyer> vorlon: There's a case where I'd rather wait until next cycle as it works rather well. I'll be sad to see that one go as it is superior to Synaptic in many ways.
[18:07] <vorlon> Eickmeyer: ok (this is exactly why we don't automatically remove seeded packages that are dropped in Debian)
[18:08] <Eickmeyer> vorlon: And I knew that, which is why I second-guessed myself yesterday. 😅
[18:08] <Eickmeyer> I do understand, however, that it will have to be dropped as there's a new package called muon that needs to be introduced.
[19:44] <Bashing-om> UWN: Issue779 up for review and final edits: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue779 :D
[19:57] <vorlon> bdmurray: hmm do you know what consumes /proposed-migration/$series/autopkgtest-results.cache ?  currently inaccessible because it's a symlink to outside the ~/public_html tree and therefore not being synced
[20:30] <mwhudson> good morning
[21:19] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Focal 20.04.6] has been marked as ready