[06:11] <rbasak> Eickmeyer: FWIW, you're not supposed to be able to push directly to git-ubuntu repositories. They're read-only.
[06:11] <rbasak> The staging branches are supposed to be the exception but they're not live yet (waiting on a Launchpad feature request).
[06:12] <rbasak> Eickmeyer: https://canonical-git-ubuntu.readthedocs-hosted.com/en/latest/howto/upload.html for how to "push" rich history with git-ubuntu
[14:14] <Eickmeyer> rbasak: Ah. Makes sense. Still came in handy as I did a `pull-lp-source` and `git ubuntu` for the merge and then built the package as normal and uploaded that way. Worked like a charm.
[14:32] <arif-ali> athos, thanks for your comments on the sosreport LP, I've got to the point of using debdiff-apply, and get the issue on "don't know how to rebase version-change", is that normal
[14:40] <Eickmeyer> arif-ali: debdiff-apply isn't really for you to use, but for the sponsor to use. :)
[14:41] <arif-ali> Eickmeyer: sure, wanted to make sure it would apply cleanly as per the issues with symbolic links yesterday. So wanted to see if that was something I need to worry about
[14:43] <LocutusOfBorg> ahasenack, LP: #2063841 has a new comment
[14:43] -ubottu:#ubuntu-devel- Launchpad bug 2063841 in virtualbox-hwe (Ubuntu) "[SRU] virtualbox crash on network traffic" [Critical, Confirmed] https://launchpad.net/bugs/2063841
[14:43] <LocutusOfBorg> please tell me if something is still missing, or you want something changed
[14:43] <ahasenack_> k
[14:43] <LocutusOfBorg> I'm a little bit afk but will answer eventually :D
[14:44] <athos> arif-ali: if that is the only issue you are  facing, it is fine. I will deal with it before uploading :) Thanks for addressing it.
[14:45] <arif-ali> ack, thanks
[15:25] <john-cabaj> Not sure anyone is around, but I'm hoping to get sponsorship on some new packages for LTS releases pre-Noble (Jammy, Focal, Bionic) - https://bugs.launchpad.net/bugs/2063362
[15:26] -ubottu:#ubuntu-devel- Launchpad bug 2063362 in involflt (Ubuntu Jammy) "Backport for 22.04, 20.04, and 18.04" [Undecided, In Progress]
[15:45] <tsimonq2> @pilot in
[15:45] <tsimonq2> o/
[16:00] <tsimonq2> liushuyu needs a bouncer ;P
[16:05] <john-cabaj> tsimonq2: Are you able to have a look at the LP bug above?
[16:06] <tsimonq2> john-cabaj: Sure :)
[16:09] <john-cabaj> tsimonq2: Thanks!
[16:11] <tsimonq2> john-cabaj: I'm a community member, so I don't have as much insight on this package's purpose as you probably do... that being said, if you need this in Bionic, that has passed the standard 5 year support cycle. I'd talk to the ESM team.
[16:11] <tsimonq2> john-cabaj: For Focal and Jammy, I'll do a full source NEW review (the works), but from an SRU team perspective my gut tells me they'll want more information.
[16:12] <john-cabaj> tsimonq2: Noted. Priority is Jammy and Focal
[16:16] <tsimonq2> john-cabaj: `lintian -EvIL +pedantic` throws me these two, I would be mindful of them for future uploads but I won't block on them: executable-not-elf-or-script (probably comes from upstream?), wrong-section-according-to-package-name (can be done via an Archive Admin override)
[16:19] <tsimonq2> Oh, on the source build itself I'm getting missing-build-dependency-for-dh-addon and missing-build-dependency-for-dh_-command ... should be a fairly simple fix
[16:19] <john-cabaj> tsimonq2: Interesting. The packages did build fine in my PPA
[16:21] <tsimonq2> Yeah, that is somewhat confusing, hm
[16:23]  * tsimonq2 sees if it builds any different with dh-dkms as a build dep
[16:27] <tsimonq2> john-cabaj: Is this intended to ship the *built* kernel module or just the source files under /usr/src/involflt-0.1.0/ ?
[16:30] <john-cabaj> tsimonq2: It's intended to ultimately build the module with the kernel. The kernel build pulls in DKMS, builds it, and packages the module
[16:31] <john-cabaj> So the former, I believe
[16:31] <tsimonq2> I ask because as-is, it only ships the source under /usr/src/involflt-0.1.0/
[16:32] <tsimonq2> I'm also not very familiar with DKMS packages :)
[16:32] <john-cabaj> tsimonq2: Right, I think if you were to install the DKMS package standalone, it would go there.
[16:33] <john-cabaj> But this should be part of the kernel build eventually (similar to zfs-linux, v4l2loopback, etc...)
[16:37] <tsimonq2> john-cabaj: Okay, I'm mostly satisfied here - the only thing that caught my eye besides the aforementioned Lintian flags is that src/md5.c is public domain. I'll add the debian/copyright entry and get these in the queue for you; that being said, I'd still suggest making the SRU bug report more detailed :)
[16:38] <tsimonq2> ( licensecheck --copyright -r . )
[16:38] <john-cabaj> tsimonq2: Thanks for giving it a look!
[16:39] <tsimonq2> No problem :)
[17:45] <tsimonq2> @pilot out
[18:11] <arraybolt3> tsimonq2: ok so what am I doing wrong here
[18:11] <arraybolt3> first I downloaded the build logs of all the failed qcoro builds and stuck them in a directory.
[18:11] <arraybolt3> Made sure they were unzipped and named differently, so they're all there.
[18:12] <arraybolt3> Then I went into the root of the qcoro source package tree, and did pkgkde-symbolshelper batchpatch -v 0.10.0 ../qcoro-symbols/*
[18:12] <arraybolt3> this spits out a ton of output and it does indeed change the symbols, but then when I build qcoro again locally, it has a bunch more added and removed symbols that almost seem to have been "missed".
[18:12] <arraybolt3> Any clue what happened there?
[18:13] <arraybolt3> (part of me is tempted to just surgically convert each build log into a diff file and then `patch` it manually)
[18:43] <RikMills> arraybolt3: pkgkde-symbolshelper batchpatch -v 0.10.0 -c amd64,arm64,armhf,ppc64el,riscv64,s390x../qcoro-symbols/* is what I would have done at 1st
[18:45] <tsimonq2> arraybolt3: try piping it into the command?
[18:46] <tsimonq2> I'd have to clone it myself, but if you're stuck I can do that
[18:47] <arraybolt3> I'll give it a shot later on, thanks!
[18:48] <tsimonq2> yw :)
[19:06] <liushuyu> tsimonq2: Thanks for looking through all the merge proposals!
[19:07] <liushuyu> tsimonq2: liushuyu needs a bouncer ;P > I did not use a bouncer because I know where to find the scroll back
[19:37] <RikMills> arraybolt3: do you mean your local qcoro build failed again on symbols, or it succeeded but with messy symbols output?
[19:38] <tsimonq2> liushuyu: hahahaha fair enough ;)
[19:38] <tsimonq2> liushuyu: Also, I didn't look through *all* of them, I left a few of the complicated ones ;P
[19:39] <arraybolt3> RikMills: It succeeded but with messy symbols output.
[19:39] <arraybolt3> And I'm unsure if it would have succeeded had I pushed to the archive.
[19:39] <RikMills> arraybolt3: arraybolt3 the current symbols file have a lot of MISSING entries commented out with a #
[19:40] <RikMills> is that perhaps what you are seeing?
[19:40] <arraybolt3> maybe, but it wasn't just that, there were symbols that were shown as needing to be added too
[19:41] <arraybolt3> so both new symbols and MISSING symbols together in the build log of the "working" build.
[19:41] <RikMills> arraybolt3: so I just did this: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3997/+sourcepub/16128654/+listing-archive-extra
[19:41] <RikMills> which might be more helpful than a local build
[19:42] <arraybolt3> hmm, yours looks substantially nicer than mine
[19:43] <RikMills> yeah, I don't seem to have any added. just missing optional, which is to be expected and allowed
[19:43] <arraybolt3> mine was this mess: https://termbin.com/wa1c
[19:44] <arraybolt3> and this is *after* pkgkde-symbolshelper
[19:44] <arraybolt3> what was the exact command you used to do it?
[19:44] <RikMills> the one I posted earlier
[19:45] <RikMills> arraybolt3: your above paste seems truncated
[19:45] <liushuyu> Hi there, can someone with permissions to retry https://launchpad.net/ubuntu/+source/gammaray/2.11.3-4ubuntu1/+build/28434638? It should succeed according to my PPA build https://launchpad.net/~liushuyu-011/+archive/ubuntu/misc/+build/28425081
[19:46] <liushuyu> (This is an universe package, so I suppose any MOTU or CoreDev should be able to do it)
[19:46] <RikMills>  pkgkde-symbolshelper batchpatch -v 0.10.0 -c amd64,arm64,armhf,ppc64el,riscv64,s390x ../buildlog_ubuntu-oracular-*
[19:47] <tsimonq2> liushuyu: .
[19:47] <RikMills> liushuyu: just did it. or collided with tsimonq2
[19:47] <RikMills> :P
[19:48] <arraybolt3> so yeah, the only thing I missed was the "-c" in there. OK, noted.
[19:49] <arraybolt3> I vaguely remember needing to do something like that now.
[19:50] <liushuyu> RikMills, tsimonq2: Thanks! (Although I am bit nervous because the build job got assigned to the slower ARM worker)
[20:12] <sudip> I need to request no-change rebuild of two packages for oracular. Is there any special process to request rebuild or do I just do the usual process of opening new bug, add debdiff and assign to sponsors?
[20:17] <arraybolt3> sudip: Easier yet still, say something here and someone who has access can do it.
[20:17] <arraybolt3> What two packages, and what are they being rebuilt for so I know what to put in the changelog?
[20:17]  * sudip knows arraybolt3 has access ;-)
[20:18] <sudip> diagnostics and ivtools please. "no-change rebuild for libace-7.1.3"
[20:19] <arraybolt3> on it
[20:19] <sudip> thanks arraybolt3
[20:24] <arraybolt3> sudip: done
[20:25] <arraybolt3> marked them both as being from you and sponsored them
[20:25] <sudip> thanks arraybolt3 :)
[20:26] <sudip> now I know whom to ping next time I upload a new version of libace in Debian  :D
[20:29] <arraybolt3> hmm, I have some time to burn, might not do a whole lot but why not...
[20:29] <arraybolt3> @pilot in
[20:34] <arraybolt3> Currently looking at fstransform.
[20:35] <arraybolt3> Patch looks great, building.
[20:35] <RikMills> arraybolt3: do you want me to upload qcoro or leave you another try?
[20:36] <arraybolt3> RikMills: If you could, that would be great, it takes a while to build here and if you have the magic words figured out, I'd not introduce another point of potential failure by passing it back to me.
[20:36] <arraybolt3> I'm sure I'll get a chance to patch the symbols right again :)
[20:36] <RikMills> ack, will do
[20:37] <RikMills> arraybolt3: done
[20:38] <arraybolt3> sudip: fstransform patch for Oracular sponsored (bug https://bugs.launchpad.net/ubuntu/+source/fstransform/+bug/2060740).
[20:38] -ubottu:#ubuntu-devel- Launchpad bug 2060740 in fstransform (Ubuntu Oracular) "fsattr fails to run" [Undecided, Confirmed]
[20:39] <sudip> arraybolt3: can you please add release targets for fstransform, Focal, Jammy and Mantic please
[20:39] <arraybolt3> sure
[20:39] <sudip> thanks :)
[20:40] <arraybolt3> done
[20:40] <arraybolt3> for https://bugs.launchpad.net/ubuntu/+source/bcftools/+bug/2062071, the fix looks like it should be applicable to Oracular too. Do you want to update the patch for that, or would you like me to do it so it can be uploaded and thus become SRU-ready for Noble?
[20:40] -ubottu:#ubuntu-devel- Launchpad bug 2062071 in bcftools (Ubuntu) "gff2gff.py crashed with ModuleNotFoundError in Noble" [Medium, Confirmed]
[20:42] <sudip> arraybolt3: will be great, if you can do it please. I think I missed it when I was updating all the others to Oracular
[20:42] <arraybolt3> kk, doing
[20:43] <sudip> thanks a lot
[20:45] <arraybolt3> oh, actually, it looks like Debian already has the fix and it's been pulled into Oracular.
[20:45] <arraybolt3> So in that instance, the Noble patch is SRU-ready.
[20:47] <sudip> I will need to add the SRU information first. removing sponsors for now, will add the info tomorrow and put it to sponsors list again
[20:47] <arraybolt3> sounds good
[21:05] <sudip> arraybolt3: I can see the no-change upload in diagnostics, but cant see it for ivtools.
[21:12] <sudip> dont worry, I can see it now. thanks again :)
[21:14] <arraybolt3> Wrote some guidance for the libfilezilla SRU patch here: https://bugs.launchpad.net/ubuntu/+source/libfilezilla/+bug/2061954
[21:14] -ubottu:#ubuntu-devel- Launchpad bug 2061954 in libfilezilla (Ubuntu) "filezilla crashed with SIGABRT in start_thread()" [Undecided, In Progress]
[21:14] <arraybolt3> and with that, my patch piloting time is out.
[21:14] <arraybolt3> @pilot off
[21:14] <arraybolt3> @pilot disable
[21:14] <arraybolt3> @pilot out
[22:05] <ahasenack_> LocutusOfBorg: I couldn't get to virtualbox, the containerstack sru was huge and was ahead
[22:05] <ahasenack_> blackboxsw: ^likewise for cloud-init
[22:06] <blackboxsw> thanks ahasenack_ for the note. we appreciate the effort