[12:10] <Nafallo> hi there. before I start digging... did anything change with pristine-tar or tar on the receipe builders the last couple of months? it's not able to reproduce my tarball, for example: https://launchpadlibrarian.net/494424699/buildlog.txt.gz
[12:12] <Nafallo> actually, never mind for now. I'll keep digging for a bit.
[12:26] <sigv> is changing Bug Importance behind some rights assignment? Sponsorship requests should explicitly tag bugs as Wishlist based on the docs, but I do not have the option to do that for my created bug at https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110
[12:29] <sigv> further, I would like to explicitly mark it as affecting 'Ubuntu Groovy' instead of 'Ubuntu' similar to how for example https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112 affects 'linux (Groovy)' but that's also something that I do not appear to have an option to do
[12:29] <Nafallo> actually, my question still stands. if I do gbp import-orig on bionic it seems focal can't checkout the tarball successfully.
[13:05] <cjwatson> Nafallo: We upgraded it a little while ago to be able to reproduce newer tarballs ...
[13:05] <cjwatson> Nafallo: Feel free to file a bug
[13:06] <cjwatson> sigv: See https://wiki.ubuntu.com/Bugs/Importance
[13:06] <sigv> cjwatson: thank you! will head to #ubuntu-bugs then
[13:32] <Nafallo> cjwatson: alright. I remember reading they had some workaround in one of the applications with an environment variable you could set to try the old behaviour. want me to dig that up first? :-)
[13:34] <Nafallo> ah. it was for both tar and pristine-tar. had it in my browser history :-)
[13:40] <Nafallo> https://code.launchpad.net/~vcc-caeit/+archive/ubuntu/vcclc-testing/+recipebuild/2631382/+files/buildlog.txt.gz
[13:40] <Nafallo> no
[13:40] <Nafallo> https://bugs.launchpad.net/launchpad/+bug/1892503
[13:45] <Nafallo> haha, running pristine-tar gendelta manually on focal obviously gets some other error :-D. that one I'll dig into myself though :-)
[13:57] <rbasak> "git clone" has been very slow for a few days that I've noticed. Known issue?
[13:57] <rbasak> It gets there in the end but it seems to be taking ~10 minutes for a clone of a relatively simple source tree :-/
[14:31] <sigv> https://code.launchpad.net/debmirror seems to be misconfigured -- historically set up to import lp:debmirror Bazaar branch in trunk series from outdated git://git.debian.org/collab-maint/debmirror.git when the upstream is actually at https://salsa.debian.org/debian/debmirror.git as can be verified from https://tracker.debian.org/pkg/debmirror VCS info
[14:31] <sigv> as I am not a signed Canonical contributor and unable to provide a "Canonical Project Manager or contact", I am not sure if I can request a code import
[14:38] <cjwatson> sigv: contributor licence agreements have nothing to do with requesting a code import
[14:38] <cjwatson> sigv: but let me fix that up
[14:40] <sigv> cjwatson: I was thinking that might of concern due to the name of the 'owner' field when requesting a code import
[14:41] <cjwatson> It is not
[14:41] <cjwatson> sigv: However, I can't easily fix this since it's owned by somebody else rather than ~registry or whatever.  I've sent Max a message asking if I can have access
[14:44] <cjwatson> We can override that with superpowers if need be but I prefer to avoid that if possible
[14:45] <sigv> cjwatson: Understandable -- Thank you!
[15:39] <sigv> Is my conclusion correct that debmirror 1:2.27ubuntu1 source is really just a source package without the patches being in version control? https://launchpad.net/ubuntu/+source/debmirror/1:2.27ubuntu1
[15:41] <sigv> Just trying to make sense of the structure of the project. Maybe that's more suited for #ubuntu-devel
[15:45] <cjwatson> Almost certainly yes
[15:45] <cjwatson> And indeed, not really for here
[16:24] <cjwatson> sigv: I've deleted the old git-to-bzr import and replaced it with a git-to-git import from the right place
[16:24] <sigv> cjwatson: awesome! Thank you very much!
[22:12] <LocutusOfBorg> bos2 looks again so saaaaaad
[22:13] <LocutusOfBorg> interestingly, the sadness starts with the weekend...
[22:15] <cjwatson> Not interesting :)
[22:15] <cjwatson> That just means we're less likely to do manual babysitting at the weekend
[22:15] <LocutusOfBorg> I was wondering about machines feeling lonely and start crying :p
[22:16] <cjwatson> I've done a bulk reset
[22:16] <cjwatson> That's users ;-)
[22:18] <cjwatson> Resets should generally be a lot more stable after some fixing last night, but there still seem to be some serious networking issues with bos02 that may cause builds to be interrupted, fail without logs, etc.  I was supposed to grab a sysadmin to dig into it today but I ended up spending half the day going back and forward between the vet hospital and the pharmacy for a sick cat
[22:18] <cjwatson> So that didn't happen
[22:20] <LocutusOfBorg> oh... I hope the cat is feeling better now
[22:20] <LocutusOfBorg> bos can wait
[22:22] <cjwatson> Well, it's potentially a long-term thing unfortunately, but I think I've done most of the tedious driving about bits
[22:33] <LocutusOfBorg> thanks for the hard work :)