[03:10] <Darxus> I haven't made a ppa in years.  nest-part is failing because the directory exists in the base repo.  How do I fix that?  https://code.launchpad.net/~darxus/+archive/ubuntu/linux-firmware-amdgpu-daily/+recipebuild/2665693
[03:16] <Darxus> Do I have to merge in a repo that's just deleting that directory?
[04:30] <Darxus>  git push git+ssh://darxus@git.launchpad.net/~darxus/+git/linux-firmware-rmamdgpu
[04:30] <Darxus> works
[04:30] <Darxus> In a recipe, this doesn't?  merge lp:~darxus/+git/linux-firmware-rmamdgpu
[04:36] <Darxus> Sorry, I forgot the short name.  And it really has been about four years.
[06:07] <Darxus> This is driving me nuts.  It's supposed to be cloning from the focal, but it's getting firmware versions that are in master, not focal:  https://code.launchpad.net/~darxus/+recipe/linux-firmware-amdgpu-daily
[06:08] <Darxus> For example, it should have cxgb4/t5fw-1.24.11.0.bin, from focal, but it has cxgb4/t5fw-1.24.17.0.bin, which is in master.
[06:09] <Darxus> That's... probably because of the repo I used to delete the amdgpu directory.  Ugh.
[07:18] <Darxus> Woo, it works!
[15:00] <Darxus> I realized I also need to merge in WHENCE from the upstream repo.  So I also deleted that in my build fixing repo, pushed it, added the nest-part, and now I'm getting: fatal: failed to unpack tree object 58d41d0facca2478d3e45f6321224361519aee96:WHENCE
[15:00] <Darxus> https://code.launchpad.net/~darxus/+recipe/linux-firmware-amdgpu-daily-focal
[15:05] <Darxus> It looks like it's saying it failed to import the file WHENCE from From https://git.launchpad.net/~darxus/linux-firmware/+git/trunk.  Which doesn't make sense to me.  It's there.
[15:07] <Darxus> nest-part does work on files, not just directories, right?
[15:16] <Darxus> subprocess.CalledProcessError: Command '['git', '-C', '/home/buildd/build-RECIPEBRANCHBUILD-2665970/chroot-autobuild/home/buildd/work/tree/recipe', 'read-tree', '--prefix', 'WHENCE', '-u', '58d41d0facca2478d3e45f6321224361519aee96:WHENCE']' returned non-zero exit status 128.
[15:46] <arunpyasi> Hi everyone, I was having groovy (binaries conflicting with the existing ones) error while trying to copy/rebuild from one ppa to another within same series. But I don't see the package in the destination PPA. Is there anything that can be done without re-uploading a new version?
[15:52] <arunpyasi> cjwatson, are you around please?
[16:01] <tomwardill> arunpyasi: sorry, cjwatson is off today and I forgot to change the header
=== tomwardill changed the topic of #launchpad to: Help contact: twom (09:00-17:00 UTC Mon-Fri) | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support and spam reporting: https://answers.launchpad.net/launchpad
[16:02] <tomwardill> arunpyasi: I _think_ a reupload is the only way out of that, but publishing isn't a strong point for me :)
[16:07] <arunpyasi> tomwardill, Oh ok.
[17:04] <Darxus> My linux-firmware package finished building 19 minutes ago.  Still publishing :/
[17:06] <Darxus> Done after 23 minutes.
[17:07] <Darxus> 51 minutes since I cliked build.
=== WrathOfAchilles is now known as IchabodCrane
[23:23] <caraka> Greetings. There appears to be a great deal of idle hardware at the build farm, but whenever I request builds, I get:
[23:23] <caraka> The following errors occurred:
[23:23] <caraka>     Timeout error, please try again in a few minutes.
[23:28] <sarnold> wow, and a lot of builders cleaning for hours
[23:44] <caraka> The cleaning stuff is not so unusual, from my limited time(s) checking the build farm status. The amount of idle builders is pretty unusual.
[23:45] <pappacena> Hey, caraka. Where exactly are you getting this "Timeout error, please try again in a few minutes"?
[23:45] <pappacena> The build farm seems to be ok. There is no queue, that's why there are so many idle builders.
[23:50] <caraka> Cheers pappacena. I'm getting the message when I click "Request Builds" on my recipe page
[23:53] <pappacena> It doesn't seem to be related to the build farm. I could only find this message on javascript code, so it's probably some HTTP request timing out. Do you have any OOPS?