DarxusI 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/266569303:10
DarxusDo I have to merge in a repo that's just deleting that directory?03:16
Darxus git push git+ssh://darxus@git.launchpad.net/~darxus/+git/linux-firmware-rmamdgpu04:30
DarxusIn a recipe, this doesn't?  merge lp:~darxus/+git/linux-firmware-rmamdgpu04:30
DarxusSorry, I forgot the short name.  And it really has been about four years.04:36
DarxusThis 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-daily06:07
DarxusFor example, it should have cxgb4/t5fw-, from focal, but it has cxgb4/t5fw-, which is in master.06:08
DarxusThat's... probably because of the repo I used to delete the amdgpu directory.  Ugh.06:09
DarxusWoo, it works!07:18
DarxusI 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:WHENCE15:00
DarxusIt 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:05
Darxusnest-part does work on files, not just directories, right?15:07
Darxussubprocess.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:16
arunpyasiHi 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:46
arunpyasicjwatson, are you around please?15:52
tomwardillarunpyasi: sorry, cjwatson is off today and I forgot to change the header16:01
=== 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
tomwardillarunpyasi: I _think_ a reupload is the only way out of that, but publishing isn't a strong point for me :)16:02
arunpyasitomwardill, Oh ok.16:07
DarxusMy linux-firmware package finished building 19 minutes ago.  Still publishing :/17:04
DarxusDone after 23 minutes.17:06
Darxus51 minutes since I cliked build.17:07
=== WrathOfAchilles is now known as IchabodCrane
carakaGreetings. There appears to be a great deal of idle hardware at the build farm, but whenever I request builds, I get:23:23
carakaThe following errors occurred:23:23
caraka    Timeout error, please try again in a few minutes.23:23
sarnoldwow, and a lot of builders cleaning for hours23:28
carakaThe 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:44
pappacenaHey, caraka. Where exactly are you getting this "Timeout error, please try again in a few minutes"?23:45
pappacenaThe build farm seems to be ok. There is no queue, that's why there are so many idle builders.23:45
carakaCheers pappacena. I'm getting the message when I click "Request Builds" on my recipe page23:50
pappacenaIt 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?23:53

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!