=== JanC_ is now known as JanC | ||
=== JanC_ is now known as JanC | ||
=== esembee_ is now known as esembee | ||
=== JanC_ is now known as JanC | ||
wouter | vorlon: thanks -- sorry, I had a minor emergency shortly after that message yesterday, and had to leave. "Where things could go wrong": if the bug is patched, I don't see where it could? if it doesn't apply, then yes, I guess that could go wrong. I couldn't think of anything else though? | 06:42 |
---|---|---|
wouter | vorlon: the bug is fairly simple (you've seen the patch) and at the same time the impact is "complete and utter failure to make anything work", so it's a fairly binary "either it works or it doesn't". If you apply the patch, it should be patched and that should be that. If you don't, it won't work. | 06:44 |
wouter | vorlon: I guess I could add a "Where things could go wrong" section that says that, essentially, but I thought that was a bit silly so skipped it. Happy to add if you think it necessary though. Other than that, do I need to do anything more to make the lunar update happen, or will you take care of it? | 06:47 |
ahasenack | hm, anybody familiar with launchpad build recipes, building debs from a git repository? I'm getting a weird result, and I think it has to do with the build recipe tool "converting" the package to a native format | 12:48 |
ahasenack | specifically, I have missing patches in debian/patches, and the build fails when it tries to apply them | 12:48 |
ahasenack | log of the source package build: https://code.launchpad.net/~ahasenack/+archive/ubuntu/openssh-ccache-testing/+recipebuild/3544354/+files/buildlog.txt.gz | 12:48 |
ahasenack | (which succeeds) | 12:48 |
ahasenack | but the binary build fails: https://code.launchpad.net/~ahasenack/+archive/ubuntu/openssh-ccache-testing/+build/26173883/+files/buildlog_ubuntu-jammy-amd64.openssh_1%3A8.9p1-3ubuntu0.1+ccache1~202305222004~ubuntu22.04.1_BUILDING.txt.gz | 12:48 |
ahasenack | recipe: https://code.launchpad.net/~ahasenack/+recipe/openssh-ccache-testing | 12:49 |
ahasenack | I have to apply a patch manually in d/rules, so the patch exists in debian/patches, but is commented in debian/patches/series | 12:49 |
ahasenack | maybe that is throwing it off? | 12:49 |
ahasenack | there is no orig tarball uploaded to the ppa either, and if I download the dsc and the debian tar gz, and unpack them, the whole debian/patches is missing | 12:50 |
ahasenack | so, "weird" | 12:50 |
ahasenack | hm, looks like the conversion to native format means applying all patches and then packing the whole thing as is | 13:23 |
ahasenack | since my patches are commented in d/p/series, they don't get applied | 13:23 |
ahasenack | bummer | 13:23 |
ahasenack | all because it couldn't get a orig tarball (https://bugs.launchpad.net/ubuntu/+source/git-build-recipe/+bug/2020386) | 13:24 |
-ubottu:#ubuntu-devel- Launchpad bug 2020386 in git-build-recipe (Ubuntu) "pristine-tar handling not compatible with git-ubuntu repositories" [Undecided, New] | 13:24 | |
wouter | ahasenack: so store the patch in a different location? | 13:25 |
wouter | or, alternatively, just reformat the patch so you don't need to apply it manually from d/rules? | 13:26 |
ahasenack | storing the patch in the root of the source package would mean doing that via a debian patch :) | 13:26 |
ahasenack | so that when it's converted to native format, all declared patches are applied, and that would create the actual patch files I need at the root of the source code | 13:27 |
wouter | I was thinking more of "debian/my-own-patches/foo.patch", or some such | 13:27 |
ahasenack | so ugly | 13:27 |
ahasenack | right, but the correct packaging is not native. This is just a shortcoming of the git-build-recipe tool | 13:27 |
ahasenack | I need two builds: one with the patch, one without it. That's why I need this control of where and when the patch is applied | 13:27 |
ahasenack | normal ppa build works just fine, if I upload the correct source package to it | 13:28 |
ahasenack | it's the launchpad recipe that breaks it | 13:28 |
wouter | oh, right, now it makes sense | 13:28 |
ahasenack | because of this conversion to a native source package, because it can't find the orig tarball | 13:29 |
teward | does anyone here have any way to reach Martin Pitt (pitti)? | 13:55 |
teward | emails seem to be being ignored | 13:56 |
teward | its devel / permissions related hence a poke here | 13:56 |
ogra | teward, https://www.piware.de/ ... there is an email icon on his blog | 13:58 |
teward | ogra: thanks I'll poke there but if we get no reply the issue will have to be escalated to far higher in the governance chain... | 13:59 |
teward | ddstreet: ping drop me a DM please | 14:17 |
teward | mapreri: ping drop me a DM if you're alivr | 14:25 |
=== cpaelzer_ is now known as cpaelzer | ||
danilogondolfo | Anyone available to review and sponsor a merge request? https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460 | 15:21 |
-ubottu:#ubuntu-devel- Launchpad bug 2020460 in libcap2 (Ubuntu) "Please merge 1:2.66-4 into mantic" [Undecided, New] | 15:21 | |
schopin | danilogondolfo: not volunteering, but you might wanna subscribe ubuntu-sponsors to the bug to clearly mark it as needing a sponsor (it'll show up on a list somewhere) | 15:43 |
danilogondolfo | schopin, done ^.^ | 15:47 |
danilogondolfo | I'm also looking for a reviewer/sponsor for a sudo MR btw :) https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470 | 16:02 |
-ubottu:#ubuntu-devel- Launchpad bug 2020470 in sudo (Ubuntu) "Please merge 1.9.13p3-1 into mantic" [Undecided, New] | 16:02 | |
=== juliank_ is now known as juliank | ||
mapreri | teward: hey, I'm alive yes. Kind of surprised that doing a "small" (1w) journey destroyed my effectively fragile life balance. -.- And indeed, sorry but I totally forgot we had our meeting last week, I manage to schedule two overlapping events.. /cc ddstreet | 17:52 |
teward | owies. | 17:53 |
teward | mapreri: no worries but not what i wanted to poke you about | 17:53 |
mapreri | oh | 17:53 |
mapreri | right, there is text before the ping lol | 17:53 |
ahasenack | wouter: your suggestion to store the patch in another location was correct in the end. I missed that "other location" could still be inside debian/, and didn't have to be in the source root. It just needs to be outside debian/patches | 19:32 |
vpa1977 | Hi, I am looking for review and sponsorship for a new upstream release of jtreg7 package (bug 2020402). Thanks in advance !!!! | 22:19 |
-ubottu:#ubuntu-devel- Bug 2020402 in jtreg7 (Ubuntu) "Please update to 7.2+1" [Undecided, In Progress] https://launchpad.net/bugs/2020402 | 22:19 | |
vpa1977 | I am looking for review and sponsorship for an interim bugfix patch of jsurf-alggeo package (bug 2013132) that often blocks openjdk migration. Thanks in advance !!!! | 22:38 |
-ubottu:#ubuntu-devel- Bug 2013132 in jsurf-alggeo (Ubuntu) "autopkgtest failure for jsurf-allgeo" [Undecided, In Progress] https://launchpad.net/bugs/2013132 | 22:38 | |
vorlon | wouter: it's fine to say that the current behavior is completely unusable | 22:38 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!