[03:14] <vpa1977> Hi, looking for sponsorship for https://bugs.launchpad.net/ubuntu/+source/maven/+bug/1930541 - guice and maven upload to focal queue. It is currently broken when running with Java 17 :( Thank you!!!!
[03:14] -ubottu:#ubuntu-devel- Launchpad bug 1930541 in maven (Ubuntu) "[SRU] Maven 3.6.3-1 fails to run with OpenJDK 17" [Undecided, Confirmed]
[03:18] <vpa1977> Also looking for sponsorship to upload OpenJDK 21.0.1+12 to Jammy and Focal (https://bugs.launchpad.net/ubuntu/+source/openjdk-21/+bug/2036873/comments/58) Thank you!!!
[03:18] -ubottu:#ubuntu-devel- Launchpad bug 2036873 in openjdk-21 (Ubuntu Lunar) "[SRU] Please provide openjdk-21 for focal, jammy and lunar" [Undecided, Confirmed]
[03:24] <Eickmeyer> vpa1977: RE bug 1930541: I'm not part of the SRU team, but since OpenJDK 17 isn't in the repos for Focal, and since we only guarantee operability for packages within the repos to work with each other, I'd expect a hard NACK for that one.
[03:24] -ubottu:#ubuntu-devel- Bug 1930541 in maven (Ubuntu) "[SRU] Maven 3.6.3-1 fails to run with OpenJDK 17" [Undecided, Confirmed] https://launchpad.net/bugs/1930541
[03:24] <vpa1977> Eickmeyer
[03:25] <vpa1977> Eickmeyer: this bug is about introducing a new package - openjdk-21, and it does not impact OpenJDK 17
[03:25] <vpa1977> openjdk-17 is present in bionic and up
[03:25] <Eickmeyer> !info openjdk-17 focal
[03:26] <Eickmeyer> I may have butchered the package name, I'll admit.
[03:26] <vpa1977> It is present in -updates
[03:26] <Eickmeyer> The bot would pick it up.
[03:26] <vpa1977> The bot only picks up release pocket
[03:27] <Eickmeyer> That's a bug in the bot then, I'll bring it to the owner's attention. I see it in https://launchpad.net/ubuntu/+source/openjdk-17
[03:28] <vpa1977> And apologises, I thought you are talking about openjdk-21 bug ;(
[03:29] <vpa1977> Maven one is rather interesting - original packaging introduced a bug by using aop version of guice. Upstream used non-aop version in this release (3.6.3). So the fix only brings things to where they should be.
[03:30] <Eickmeyer> Yeah, understood. I just don't know how SRUs apply to updating items that weren't in the release pocket.
[03:31] <Eickmeyer> Like I said, I'm not on the SRU team. :)
[03:31] <vpa1977> maven was =)
[03:31] <vpa1977> But openjdk-17 was introduced later and people discovered that they can not use maven with it
[03:31] <Eickmeyer> Right, which is an SRU grey area.
[03:31] <vpa1977> !info maven focal
[03:32] <vpa1977> thank you bot =)
[03:32] <Eickmeyer> I knew maven was there before. :)
[03:32] <Eickmeyer> I wonder...
[03:32] <Eickmeyer> !info openjdk-17 focal-updates
[03:32] <Eickmeyer> bot hates me
[03:32] <vpa1977> !info openjdk-17 focal-security
[03:32] <Eickmeyer> heh
[03:33] <Eickmeyer> Unit193: Fun times with ubottu ^
[05:10] <Unit193> !info openjdk-17 focal
[05:15] <Unit193> Eickmeyer: Mate, there's no binary with that name. :P
[05:15] <Unit193> !info openjdk-17-jre focal
[05:16] <Eickmeyer> Unit193: Ah, I was looking at the source package. :P
[10:01] <mirespace> Hi, working in a FTBFS #lp2036255 for clamav on Mantic ... but I built it without changes in ppa https://launchpad.net/~mirespace/+archive/ubuntu/clamav-ftbfs-lp2036255/+build/27008110
[10:03] <mirespace> Should the next step be to ask for a package rebuild on Mantic?
[10:35] <mkukri> https://code.launchpad.net/~mkukri/ubuntu/+source/cryptsetup/+git/cryptsetup/+merge/455868
[11:28] <ginggs> mirespace: I can retry that test rebuild, do you want/have a copy of the log before I do so?
[11:37] <mirespace> ginggs: Nice, thanks! I have the log of the mantic testrebuild attached to the FTBFS bug, and extracted in the description the error, so I think we're fine
[11:39] <ginggs> ok, retrying...
[12:01] <ginggs> mirespace: success \o/
[12:01] <waveform> @pilot in
[12:01] <mirespace> ginggs: \o/ Thankyou!
[15:32] <arraybolt3> Soooo... lintian.debian.org got taken down in favor of UDD, and now the awesome database of "this is why Lintian is yelling at you" is now gone. Does anyone have an alternative they're using?
[15:32] <arraybolt3> (Alternatively, can someone tell me what on earth prefer-uscan-symlink means?)
[15:33] <arraybolt3> oh, nvm, I just found lintian-explain-tags (a command I can run in my shell).
[16:00] <waveform> @pilot out
[16:00] <waveform> (well mostly, I'm still finishing off a few bits of -s32 review)
[16:03] <ginggs> arraybolt3: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042428#30
[16:03] -ubottu:#ubuntu-devel- Debian bug 1042428 in qa.debian.org "qa.debian.org: Missing description for lintian warning tags (https://udd.debian.org/lintian/?packages=)" [Wishlist, Open]
[16:04] <Eickmeyer> waveform: Lovely flight on Pi Air today. :)
[16:04] <ginggs> arraybolt3: so https://udd.debian.org/lintian-tag.cgi?tag=prefer-uscan-symlink
[16:05] <arraybolt3> ginggs: Ah, cool. The command I found is more convenient anyway though.
[16:06] <waveform> Eickmeyer, heh -- I've managed to calm the small jet-turbine of the fan down a bit (see LP: #2041741 :)
[16:06] -ubottu:#ubuntu-devel- Launchpad bug 2041741 in linux-raspi (Ubuntu Mantic) "Fan speed control not working on Pi 5 under Ubuntu 23.10" [High, Fix Committed] https://launchpad.net/bugs/2041741
[16:08] <Eickmeyer> waveform: Ha! I don't mind cool temps, but I get the noise factor! (tends to drown-out noisy toddlers in the cabin :))
[18:06] <ravikant_> quid
[18:06] <ravikant_> quit
[18:29] <teward> arraybolt3: so, is there a reason that we need two packaging bugs for redshift-qt?  Because it would be easier to simply wait for Debian to process the package and then sync it then upload to Ubuntu then sync again to keep in line with Debian.  Just sayin.
[18:30] <arraybolt3> teward: See the #lubuntu-devel backlog.
[18:31] <arraybolt3> #SimonsFault
[19:49] <tsimonq2> (tl;dr it's a feature goal for Lubuntu, so rather than let it go through the normal process, we came to a general consensus to let it go through the Ubuntu NEW queue as well, once I fully review it.)
[21:03] <tsimonq2> @pilot in
[21:03] <tsimonq2> Hey hey!
[21:04] <tsimonq2> I'm going to start with arraybolt3's redshift-qt upload, in bug 2044008 (which I'll also do in Debian.)
[21:04] -ubottu:#ubuntu-devel- Bug 2044008 in Ubuntu "[needs-packaging] redshift-qt" [Wishlist, In Progress] https://launchpad.net/bugs/2044008
[21:05] <tsimonq2> After that, I'll probably tackle bug 2041800 and bug 2041836.
[21:05] -ubottu:#ubuntu-devel- Bug 2041800 in Ubuntu "[needs-packaging] usbio-drivers" [Wishlist, Confirmed] https://launchpad.net/bugs/2041800
[21:05] -ubottu:#ubuntu-devel- Bug 2041836 in Ubuntu "[needs-packaging] intel-lpmd" [Wishlist, Confirmed] https://launchpad.net/bugs/2041836
[21:06] <tsimonq2> If I get to it, I'll also take https://code.launchpad.net/~mkukri/ubuntu/+source/cryptsetup/+git/cryptsetup/+merge/455868 since it looks like xnox did a preliminary review.
[21:06] <tsimonq2> Probably it for today.
[21:09] <vpa1977> Hi, sorry for spam. I am looking for sponsorship to upload OpenJDK 21.0.1+12 to Jammy and Focal (https://bugs.launchpad.net/ubuntu/+source/openjdk-21/+bug/2036873/comments/58) Thank you!!!
[21:09] -ubottu:#ubuntu-devel- Launchpad bug 2036873 in openjdk-21 (Ubuntu Lunar) "[SRU] Please provide openjdk-21 for focal, jammy and lunar" [Undecided, Confirmed]
[21:13] <tsimonq2> vpa1977: I'll look at that first for you.
[21:13] <vpa1977> tsimonq2: Thank you!!!!
[21:14] <tsimonq2> vpa1977: Just give me a bit to fully read over the bug report, logs, and diff, but I'll ping you if I have any questions. You have some sort of bouncer, right? :)
[21:15] <vpa1977> tsimonq2: I need to set up one properly ;( I've been just checking irc logs ;(
[21:16] <bdmurray> vpa1977 is in NZ so will be around for a while
[21:16] <tsimonq2> vpa1977: My best suggestion for pure IRC would be to use tmux/byobu + irssi on a $5 VPS.
[21:16] <tsimonq2> Ah, cool. Thanks Brian. :)
[21:25] <tsimonq2> vpa1977: Could you help me understand this line in your focal diff, and what precisely the reversal is for?
[21:25] <tsimonq2> +  openjdk-20-jdk-headless:native | openjdk-21-jdk-headless:native,
[21:25] <tsimonq2> (It's the same in your Jammy diff, too.)
[21:25] <vpa1977> one second
[21:27] <vpa1977> tsimonq2: that's a generated control file, doko reversed order to prefer 21 in debian sid, but i think it was not changed for older releases.
[21:28] <vpa1977> the manual change in the debdiff is uncommented "with_check = disabled for this upload"
[21:29] <tsimonq2> vpa1977: I'm just trying to understand how openjdk-20-jdk-headless can be used to build openjdk-21, but then again, I'm not intimately familiar with the Java stack.
[21:29] <tsimonq2> Could you just give a *little* more details on their compatibility?
[21:30] <tsimonq2> Unless I'm not seeing build depends...
[21:30] <vpa1977> tsimonq2: I apologise, this is the bootstrap step. An older JDK is used to build compilation tools for the newer one.
[21:30] <tsimonq2> vpa1977: Got it, makes a lot of sense. We used to do this with Qt 5 transitions, so I get it. Thanks. :)
[21:31] <vpa1977> The upload that we currently have in proposed bootstraps from openjdk-17, but I had to add a rather ugly patch to do that, which we do not want to see in the release.
[21:31] <tsimonq2> vpa1977: Also, could you consider, perhaps in a future upload, depending on g++ instead of a specific version? Not sure how doko would feel about doing that in Debian Sid (seems dangerous if compatibility is strictly enforced), but for stable releases that seems fine.
[21:31] <tsimonq2> Makes sense.
[21:33] <vpa1977> tsimonq2: so that g++ version is resolved automatically, rather than hardcoded in control? I probably need to check with doko, if there are issues there
[21:34] <tsimonq2> vpa1977: It's mostly out of idle curiosity, since it'd allow you to not have to worry about looking it up every time. Then again, yeah, please check with him, there's likely a lot of context I'm missing.
[21:34] <tsimonq2> Anyway, running it through my usual automated gauntlet.
[21:34] <tsimonq2> https://nthykier.wordpress.com/2012/02/23/some-sponsors-are-evil-and-pedantic/
[21:39] <tsimonq2> vpa1977: Looks like the Jammy dependencies need to be updated:
[21:39] <tsimonq2> unsat-dependency: openjdk-20-jdk-headless:amd64 | openjdk-21-jdk-headless:amd64
[21:39] <tsimonq2> https://packages.ubuntu.com/search?keywords=openjdk-20-jdk-headless
[21:39] <tsimonq2> Well, and Focal too.
[21:40] <vpa1977> is it in a local build environment ?
[21:40] <tsimonq2> It's with a fresh Jammy chroot against the archive, with -proposed enabled.
[21:41] <tsimonq2> Could it be 17 instead of 20, like you mentioned earlier?
[21:41] <vpa1977> Probably best for me just drop openjdk-20 from the debdiff
[21:41] <vpa1977> Not with this version - it will only build against 20 or 21
[21:42] <tsimonq2> Is it in too early of a stage for 21 to be a viable build dependency?
[21:43] <vpa1977> We have already uploaded openjdk-21~35 to act as a bootstrap
[21:43] <vpa1977> it is in -proposed
[21:45] <tsimonq2> Ah cool, I'll try a build with "openjdk-21-jdk-headless" instead of "openjdk-20-jdk-headless | openjdk-21-jdk-headless"
[21:46] <vpa1977> I will attach debdiffs with openjdk-20 removed, one second I will apply/start build to make sure they are ok
[21:46] <tsimonq2> Sounds good, looking forward to it. In the meantime, I'll take care of redshift-qt and come back.
[21:53] <tsimonq2> arraybolt3: Always remember to look at your build logs ;) systemtray.cpp:177:50: warning: ‘Q_PID QProcess::pid() const’ is deprecated: Use processId() instead [-Wdeprecated-declarations]
[21:53] <tsimonq2> arraybolt3: Not a blocker persay, but definitely something to bug upstream about.
[21:53] <arraybolt3> I saw that and figured we'd patch it once it was a real problem.
[21:53] <arraybolt3> Upstream hasn't worked on it for three years.
[21:54] <arraybolt3> Might be worth asking them about though.
[21:54] <arraybolt3> Good idea.
[21:55] <tsimonq2> Thanks! We could always patch that in the Debian package, too.
[21:55] <arraybolt3> I guess a long hiatus doesn't necessarily mean it's been abandoned.
[21:56] <arraybolt3>  Yeah that's what I was thinking. I guess better to do it now before it's a big mess later.
[21:57] <tsimonq2> arraybolt3: I just uploaded your package to Debian, with an amd64 deb. It should show up here shortly: https://ftp-master.debian.org/new.html
[21:57] <tsimonq2> arraybolt3: Looking at Ubuntu now.
[21:57] <arraybolt3> Nice, thanks!
[21:57] <vpa1977> tsimonq2: I have updated debdiffs - https://bugs.launchpad.net/ubuntu/+source/openjdk-21/+bug/2036873/comments/66 and https://bugs.launchpad.net/ubuntu/+source/openjdk-21/+bug/2036873/comments/67
[21:57] -ubottu:#ubuntu-devel- Launchpad bug 2036873 in openjdk-21 (Ubuntu Lunar) "[SRU] Please provide openjdk-21 for focal, jammy and lunar" [Undecided, Confirmed]
[22:00] <tsimonq2> vpa1977: Sweet, I'll look in just a second. As long as they're Lintian-clean and build, I have no further questions from the packaging side of things.
[22:01] <tsimonq2> arraybolt3: Uploaded to Ubuntu as well.
[22:01] <arraybolt3> 🎉
[22:02] <vpa1977> tsimonq2: Thank you!!!
[22:03] <tsimonq2> vpa1977: No, thank *you*. :)
[22:07] <tsimonq2> vpa1977: Oh nice, looks like a four hour build each. Thankfully you're around for a little while longer. ;P
[22:11] <tsimonq2> Taking a quick break, then I'll review cryptsetup.
[22:11] <tsimonq2> After that, mowing through a bunch of old source NEW packages in the queue.
[22:37] <tsimonq2> Uploaded the cryptsetup merge.
[22:40] <tsimonq2> WOAH. I can select RISC-V now when creating a new PPA. That is *HUGE* progress!
[22:42]  * arraybolt3 goes and sees if I can do that
[22:43] <xnox> yeah, seems like all the changes are deployed, likely this is because other pieces of infra got upgraded
[22:43] <arraybolt3> WOOHOO it's available for me too!
[22:43]  * arraybolt3 throws a small party
[22:44] <mkukri> aw cryptsetup merge im a bit scared by, it builds fine, but i did remove a patch, and didnt run autopkgtest locally yet
[22:44] <tsimonq2> mkukri: Let's see how it goes. I'll help you keep an eye on it, to fix things.
[22:45] <arraybolt3> No more wishing we had a RISC-V porterbox for Lubuntu :D
[22:45] <mkukri> ta
[22:45] <vpa1977> mkukri: cryptsetup autopkgtest take quite a bit of time =)
[22:46] <mkukri> shall see tomorrow, not at working rn, just happened to glance on IRC
[22:46] <tsimonq2> vpa1977, mkukri: I can also trigger autopkgtests against PPAs, if you need it for testing something.
[22:47] <tsimonq2> mkukri: No worries, have fun :D
[22:51] <mkukri> yeah i also can, probably should have done that earlier now that we talk about it...
[22:51] <mkukri> i already have the same package in a ppa
[22:52] <mkukri> (i am a fairly new canonical foundations team member for the external peeps here)
[22:52] <tsimonq2> mkukri: Welcome, glad to have you here. :)
[22:52]  * tsimonq2 is a member of ~not-canonical
[23:21] <mitchdz> @sarnold: I  addressed your nits in https://bugs.launchpad.net/ubuntu/+source/hibagent/+bug/2044029 thanks for taking a look!
[23:24] <tsimonq2> @pilot out
[23:24] <tsimonq2> I think I'm good for the night.
[23:26] <tsimonq2> For the next sponsor, bug 1930541 by vpa1977 may be a good starter package for you.
[23:26] -ubottu:#ubuntu-devel- Bug 1930541 in maven (Ubuntu) "[SRU] Maven 3.6.3-1 fails to run with OpenJDK 17" [Undecided, Confirmed] https://launchpad.net/bugs/1930541
[23:26] <tsimonq2> vpa1977: I'm continuing to wait for your openjdk builds, but I have $other_stuff to do and I'll follow up tomorrow at the latest. (TZ is US/Central)
[23:27] <vpa1977> tsimonq2: thank you!!!!
[23:27] <tsimonq2> Vim merge also incoming. I'm guessing the autopkgtest runners will be pretty occupied in the near future. :P
[23:27] <tsimonq2> vpa1977: Of course, I'm happy to help. :)
[23:28] <bdmurray> poor autopkgtest
[23:28] <tsimonq2> vpa1977: Also, I'm looking at https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsor=&sponsor_search=name&sponsoree=Vladimir+Petko&sponsoree_search=name (OOC) and I'm surprised you haven't applied for (at least) PPU yet. ;)
[23:29] <tsimonq2> bdmurray: poor src:kitty, it'll probably fail on something...
[23:31] <tsimonq2> mdeslaur, sarnold: Would you happen to know who I could get in touch with about red security items in the sponsorship queue? Generally speaking, it would be nice to do some housekeeping, and the three oldest items on the queue are things that the security team needs to sponsor. Thanks in advance for your attention. :)
[23:31] <tsimonq2> Quick link: http://reqorts.qa.ubuntu.com/reports/sponsoring/
[23:31] <tsimonq2> (Why hasn't that been moved to a different domain yet? :P)
[23:35] <tsimonq2> ogayot: I stole your sysvinit merge, feel free to steal it back in the future.
[23:38] <tsimonq2> bdrung: Ooooh, I just noticed your lp:ubuntu-sponsoring work. Thank you *so* much for that!
[23:45] <amurray> leosilva: I see you are on the community role this week - can you please take a look at the security sponsors queue? re tsimonq2's request above?