[13:22] <seb128> libzip migrate \o/ thanks cpaelzer !
[13:43] <cpaelzer> yw seb128
[13:44] <cpaelzer> let us hope it really does migrate and not hit any last minute issues
[13:44] <cpaelzer> or did it complete by now
[13:44] <cpaelzer> oh yeah it did \o/
[13:46] <cpaelzer> seb128: maybe I can trade that fro some AA need I have?
[13:46] <cpaelzer> seb128: I was pinging doko this morning, but he seems busy
[13:46] <cpaelzer> seb128: another +1 think I found was spyder https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#spyder
[13:46] <cpaelzer> it had a bunch of issues, with all but one resolved by now
[13:46] <cpaelzer> the one that is left is that spyder-reports is incompatible
[13:47] <cpaelzer> I'd like to ask that we go the same way as Debian did on that which is remov spyder-reports and let the rest migrate
[13:47] <cpaelzer> https://tracker.debian.org/news/1235339/spyder-reports-removed-from-testing/
[13:48] <cpaelzer> seb128: if you'd agreee could you do that removal for me so this can migrate as well?
[13:56] <seb128> cpaelzer, k, let me check that one
[14:31] <seb128> cpaelzer, removed
[14:31] <cpaelzer> thank you seb128
[14:31] <seb128> np!
[17:43] <JawnSmith> Is any core dev available to restart the failed python3-pynvim autopkgtests that are blocking python3-defaults? I believe the new version of python-msgpack resolves the issue.
[17:50] <ginggs> JawnSmith: .
[17:50] <JawnSmith> Thanks again ginggs!
[17:51] <ginggs> yw!
[21:38] <teward> doko: you TIL for `rar`, is that synced to Multiverse from debian, or is that handled by Ubuntu?  Asking because it looks odd that `rar` only is on i386 and amd64, and not the ports (RPi, etc.) while `unrar` is fully available on the arm archs.
[21:38] <teward> was wondering if you knew anything about that
[21:38] <teward> (was digging into an Lubuntu issue when I discovered this)
[21:46] <cjwatson> teward: easy to check, compare with https://tracker.debian.org/pkg/rar
[21:46] <cjwatson> teward: https://tracker.debian.org/media/packages/r/rar/control-2%3A5.5.0-1 has the arch limitation too
[21:46] <cjwatson> looks just not super well-maintained
[21:47] <teward> hmm makes sense.  seems like there's something going awry there though, with it not being maintained.  I'm assuming it's closed source proprietary if it's in Multiverse.)
[21:47] <cjwatson> teward: however from the "source code" it's clear enough why it's only available on a couple of arches: https://sources.debian.org/src/rar/2:5.5.0-1/
[21:47] <teward> pfft
[21:48] <teward> figures it ships the prebuilts
[21:48] <teward> this explains a lot
[21:48] <teward> *makes notes on this limitation for things*
[21:48] <teward> if i had any knowledge of the internals on creating RAR files I'd consider creating some other `rar` tool but I don't have the knowledge, and ERR:TOOBUSY
[21:49] <cjwatson> there's no sign that source exists publicly here.
[21:50] <teward> yeah the license files explain it too
[21:50] <teward> TL;DR it's WinRAR's rar but built for linux.
[21:50] <cjwatson> and I don't know how much to believe https://peazip.github.io/free-rar-create.html (which was just the first hit on some search terms) but it suggests that no free reimplementation can legally exist
[21:50] <teward> at least, if i'm understanding the license on there right.
[21:51] <cjwatson> which I think means nobody should morally support this format.
[21:51] <teward> *rolls eyes* I don't disagree
[21:52] <teward> ... there's no way we can `rm -rf` the `rar` non-free utility from Ubuntu without everyone being supremely mad at us is there?  (since 'unrar' is made under a similar license on the 'no reverse engineering')
[21:52] <teward> (i can see keeping unrar, but i'd love to take the proverbial nuke to the `rar` binaries themselves.
[21:53] <cjwatson> I don't know.  it's probably no worse than a bunch of other stuff in multiverse.
[21:54] <teward> well when amd64 eventually dies in a decade or more, RAR will die anyways :P
[21:54] <teward> *shrugs*