/srv/irclogs.ubuntu.com/2022/05/24/#ubuntu-devel.txt

quidnuncrbasak: https://docs.huihoo.com/debian/manuals/maint-guide/ch-update.en.html this says "simply copy the debian/ directory if it was packaged with quilt". I think that package uses quilt (?). Can I do that?00:22
quidnuncDoes gbp work with Fossil too?00:23
=== didrocks999 is now known as didrocks
cpaelzergit-build-recipe --allow-fallback-to-native makes the content contiain a .git dir07:40
cpaelzersome packages build behavior changes in presence of one07:40
cpaelzerI should be able to remove the .git in d/rules as part of the recipe delta, but wanted to know if there is a more declarative/systematic way to avoid getting that .git in the final result?07:41
cpaelzeroh and local git-build-recipe behaves different than the one running on LP, I'm assuming one finds the tarball and makes it native and the others does not?07:45
=== alan_g_ is now known as alan_g
=== sem2peie- is now known as sem2peie
jawn-smithbdmurray, enr0n: my u-r-u MP has been approved15:50
bdmurrayjawn-smith: great15:54
enr0njawn-smith: thanks for the heads up15:55
jawn-smithNow that we have the code in good shape I'll make another MP to ubuntu/devel15:57
jawn-smithbut first, a sandwich15:58
jawn-smithactually after discussing with waveform I don't think this needs a kinetic PR. Rather, the remove_uboot should be removed from kinetic17:02
bdmurrayjawn-smith: is remove_uboot a quirk?17:05
jawn-smithbdmurray: yes, it is17:05
bdmurrayjawn-smith: if its not relevant for an upgrade from J to K then it can be removed. Additionally, if your new quirk isn't relevant for J to K then it doesn't need to be in K even though its being SRU'ed to J17:07
jawn-smithbdmurray: that is correct, neither of these quirks are relevant for J to K upgrades17:07
bdmurrayjawn-smith: Although given that the quirk is late you should think about people who have already upgraded to J17:08
waveformboth the netplan and remove-uboot quirks are relevant for upgraders *to* jammy, but correct me if I'm wrong, as you can't skip an LTS when upgrading, that means all upgraders to kinetic (or ++) would *have* to pass thru jammy and so neither is necessary beyond that. The only reason I can think to leave either in beyond jammy is in case there's some future SRU back to jammy (so it *might* be worth gating both quirks on version <= 22.04?)17:12
jawn-smithbdmurray: since this breaks networking I don't think it's something that could be ignored for a long period of time. It therefore seems unlikely that someone would make it all the way to a kk upgrade without fixing this manually17:15
bdmurrayjawn-smith: ack17:22
dbungertMay I get assistance with a retest? https://autopkgtest.ubuntu.com/request.cgi?release=kinetic&arch=arm64&package=chkrootkit&trigger=binutils/2.38-4ubuntu121:15
kanashirodbungert, done21:17
dbungertkanashiro: thanks!21:20
bdmurrayWhile there isn't much in the queues right now I think it'd be better to provide a `retry-autopkgtest-regressions` command to run as taht will check for any existing queued tests.21:28
dbungertbdmurray: I actually asked that before, but it wasn't run yet, so I thought I might have better luck with the URL22:03

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