[10:32] <laney> has anyone tried a bzr -> git conversion on update-manager?
[10:32] <laney> was just fiddling with it but couldn't get it to work for various tedious reasons
[11:45] <Unit193> laney: I had some warnings about some tags for commits that didn't exist, but https://git.unit193.net/cgit/users/unit193/update-manager.git/ looks OK-ish.
[11:52] <Unit193> bzr has no idea where a lot of these tags go, eg 'upstream-0.41.1.dfsg+CVS20051105 ?'
[13:14] <laney> Unit193: yeah I saw that, don't understand the model very well to know how that happen
[13:14] <laney> merci for the conversion!
[13:18] <laney> bdmurray: any thoughts on doing a migration to git for update-manager?
[14:04] <bdmurray> laney: none other than that sounds great
[15:22] <dbungert> bdmurray: did you get the info you were looking yesterday?  If not I can try to figure out what's going on.
[15:24] <bdmurray> dbungert: No, I haven't done more with that yet.
[16:28] <schopin> (copied straight from -release) Hi :) Looking for sponsor(s) for LP #1931994 (openssl), with several SRUs. Note that there's already an openssl package in hirsute-proposed, I pinged the uploader, but I'm guessing they're on w-e.
[16:51] <bdmurray> schopin: the openssl in hirsute-proposed is just a test fix correct?
[16:53]  * bdmurray answers own question with yes
[16:54] <bdmurray> schopin: Were you pinging the uploader for sponsorship or something else?