[00:08] <liushuyu> tsimonq2: I am not sure how it happened, but the upload https://launchpad.net/ubuntu/+source/rustc-1.68/1.68.2+dfsg0ubuntu1-0ubuntu6 is missing one of the patches. To avoid this being a Git repository de-sync issue, I have prepared https://launchpad.net/~liushuyu-011/+archive/ubuntu/rust-vvv-1.68/+sourcepub/15699493/+listing-archive-extra ...
[00:09] <liushuyu> ... so that you may do a source copy
[00:09] <liushuyu> (If you download https://launchpad.net/~liushuyu-011/+archive/ubuntu/rust-vvv-1.68/+sourcefiles/rustc-1.68/1.68.2+dfsg0ubuntu1-0ubuntu5/rustc-1.68_1.68.2+dfsg0ubuntu1-0ubuntu5.debian.tar.xz, you will find there is a patch fixing libgit 1.7 inside)
[02:09] <vorlon> jbicha: libnss-myhostname is in components-mismatches because gnome-control-center has grown a recommends on it.  We've intentionally kept this package out of the install.  Can this be dropped?
[03:57] <tsimonq2> liushuyu: ack, will look/sponsor in less than 12 hours unless someone else gets to it
[03:58] <tsimonq2> liushuyu: would recommend a bug with ubuntu-sponsors regardless :)
=== JanC_ is now known as JanC
[07:02] <liushuyu> I have opened a sponsorship bug for the current situation with rustc-1.68: https://bugs.launchpad.net/ubuntu/noble/+source/rustc-1.68/+bug/2049577
[07:02] -ubottu:#ubuntu-devel- Launchpad bug 2049577 in rustc-1.68 (Ubuntu Noble) "Backport libgit2 1.7 fix for rustc-1.68 on Noble" [High, New]
[08:04] <LocutusOfBorg> liushuyu, tsimonq2 I didn't fix it up, because somebody told me rust-1.68 was scheduled for removal
[08:04] <LocutusOfBorg> and I'm pretty sure you need to disable a patch to make it build
=== sem2peie- is now known as sem2peie
=== sem2peie- is now known as sem2peie
=== sem2peie- is now known as sem2peie
[09:49] <schopin> tsimonq2: fwiw it's doubtful that things will ever get to a syncable state for Rust (unless we actually take over in Debian, I guess?), for the simple reason that we're moving way faster than they are :)
[09:50] <schopin> And I'm aware that for the people that keep asking us for ETAs on various versions that statement might sound a bit odd :-P
[10:42] <LocutusOfBorg> schopin, kernel folks are blinking :D
[12:02] <ginggs> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: ginggs
[12:45] <seb128> ginggs, hey, did you get any luck/reply about those python build issues I mentioned in response to the noble archive rebuild email?
[12:52] <ginggs> seb128: no answers :( i guess not a common failure then
[12:52] <ginggs> LocutusOfBorg: diaspora-installer hinted
[12:54] <LocutusOfBorg> ta
[13:00] <seb128> ginggs, ack, thanks
[14:11] <schopin> vorlon: do you know whether we'll see a new pam upstream release before feature freeze in Noble? Wondering whether I should upload the patch for LP: #2045250 now or just wait for upstream.
[14:11] -ubottu:#ubuntu-devel- Launchpad bug 2045250 in Ubuntu on IBM z Systems "pam_lastlog doesn't handle localtime_r related errors properly" [High, New] https://launchpad.net/bugs/2045250
[15:34] <jamespage> mfo: hey - thanks for the py3.12 fixes into eventlet - I uploaded a new upstream release today which includes those and has full 3.12 support :)
[15:47] <vorlon> schopin: sorry, I have no idea
[15:47] <vorlon> schopin: it's nothing I'm working on right now in Debian
[15:48] <schopin> vorlon: I actually just had a look. The release I was looking for is actually 1.5.3 which has been out for a while and has hit experimental a couple of days ago.
[15:48] <schopin> meanwhile upstream has released 1.6.0 less than an hour ago.
[16:00] <vorlon> schopin: haha
[16:02] <ginggs> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: N/A
[16:02] <ginggs> thank you for flying Ubuntu Air!
[16:15] <jbicha> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: jbicha
[17:25] <mdeslaur> schopin, vorlon: pam 1.6.0 fixes a security issue, I will be publishing updates to the stable releases this pm, should I upload the security fix only to noble, or should we consider 1.6.0?
[17:26] <vorlon> mdeslaur: off the cuff I think you should just upload to noble; release happening today doesn't mean we're getting it uploaded as maintenance to devel in the near future
[17:27] <mdeslaur> vorlon: ack
[17:27] <mdeslaur> schopin: do you want to include my fix in your upload, or just upload after me?
[17:28] <schopin> mdeslaur: please go ahead without me, I need to look into all the various versions anyway :)
[17:28] <mdeslaur> schopin: ack, thanks!
[17:28] <mdeslaur> vorlon: thanks!
[17:57] <liushuyu> Hi ubuntu-devel, can someone help me check why https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#gdb (SRU) has not migrated? The tests are all green now
[17:59] <liushuyu> The corresponding SRU bug is https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2041396
[17:59] -ubottu:#ubuntu-devel- Launchpad bug 2041396 in gdb (Ubuntu Jammy) "gdb 12.1 generates SIGILL on armhf" [Undecided, Fix Committed]
[18:00] <sudip> liushuyu: its still in verification-needed stage
[18:00] <sudip> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification
[18:02] <liushuyu> Okay, so I need to wait for the verification
[18:03] <sudip> liushuyu: you should test the package from poposed according to the test plan and add the verification report
[18:03] <sudip> and then update the tags
[18:06] <liushuyu> I see. According to the wiki, it sounds like someone other than the uploader should do the verification test. Is it enough that I (who proposed the fix) performed test and determined the updated package to be fixed?
[18:12] <sudip> liushuyu: I think its ok for you to test
[18:17] <bdmurray> liushuyu: In an ideal world other people would perform the verification but that doesn't always happen.
[18:17] <bdmurray> liushuyu: The important thing is to "show your work" when verifying the bug.
[18:18] <tsimonq2> liushuyu: Looks like LocutusOfBorg took care of your request :) although it falls onto me as the person that signed the upload, the constructive criticism I would have for you in the future is, ensure the changelog describes all changes made. I had no idea that patch existed or needed to be included, because there was no changelog entry. Instead of simply grabbing your package, I pulled the current
[18:18] <tsimonq2> copy from proposed, changed the deps myself, and added your changelog entry. Partly my mistake for not sitting through the 2 hour local build, partly your mistake for the changelog. I'm glad it's sorted now. :)
[18:30] <tsimonq2> seb128 (cc mkukri): I disagree with you on bug 2049188. More often than not, Debian maintainers are not inclined to accept this class of patches, if the issue is not present on Debian. In fact, vendor patches are specifically forbidden per Debian Policy. This definitely needs to be a delta, until Debian upstreams this part of our dpkg delta.
[18:30] -ubottu:#ubuntu-devel- Bug 2049188 in hiredis (Ubuntu) "hiredis FTBFS on ppc64el" [Undecided, New] https://launchpad.net/bugs/2049188
[18:30] <tsimonq2> seb128: The *vast* majority of the time I would agree with you on this point, in this case I do think a delta would be acceptable.
[18:31] <liushuyu> tsimonq2: Yes. The changelog issue is my fault. That is also why I corrected the issue in the newer revision of the package
[18:31] <tsimonq2> liushuyu: Live and learn :D
[18:32] <tsimonq2> liushuyu: Anyway, thanks for your work and persistence on that. Thanks again for following up on your upload :D
[18:33] <vininim> I'm getting the following error while trying to run git-ubuntu: fatal: could not read Username for 'https://git.launchpad.net': terminal prompts disabled
[18:34] <tsimonq2> vininim: IME that can be ignored. The repo should still be cloned and usable, yeah?
[18:34]  * tsimonq2 tries to find some git-ubuntu docs on actually "signing in" in some capacity...
[18:34] <liushuyu> tsimonq2: Thank you for uploading and helping me understand the issue. We always learn something new everyday
[18:35] <vininim> That's the second error: Unable to find imported repository. I thought it was related to the first one.
[18:36] <tsimonq2> liushuyu: of course :)
[18:36] <tsimonq2> vininim: hmmmmmm which package are we talking about here?
[18:36] <vininim> tsimonq2: pipewire-jack
[18:37] <tsimonq2> vininim: Ah, okay! I know what the problem is :)
[18:37] <tsimonq2> vininim: `git ubuntu clone` only supports source packages, not binary packages, to my understanding.
[18:37] <tsimonq2> vininim: So instead of running `git ubuntu clone pipewire-jack`, try `git ubuntu clone pipewire` - that should do the trick.
[18:38] <tsimonq2> For future reference: https://packages.ubuntu.com/noble/pipewire-jack shows the source package name on the right side.
[18:38] <vininim> Oh, it worked. Thanks.
[18:38] <tsimonq2> (Otherwise, you can run `$ apt-cache showsrc pipewire-jack` in a terminal. :) )
[18:38] <tsimonq2> No worries!
[18:40] <tsimonq2> ginggs, jbicha: You guys are great, the queue looks awesome :)
[18:51] <tsimonq2> https://launchpad.net/ubuntu/+source/rustc-1.68/1.68.2+dfsg0ubuntu1-0ubuntu7/+build/27651974 ah yes started 10 hours ago
[18:56] <liushuyu> 10 hours is actually quite fast for building rustc on an emulated RISC-V system
[18:57] <liushuyu> (Is there a way to fast-forward though time so that I don't have to wait?)
[19:03] <tsimonq2> When you figure that out, let me know. :D
[19:04] <arraybolt3> liushuyu: Yes, there is, it's called sleep :)
[19:25] <liushuyu> arraybolt3: But that is somewhat uncontrollable, you can't fast-forward a specific amount of time. The alarm-clock method isn't always reliable, the time-travel may overshoot into unspecified future
[19:26] <liushuyu> I have added a verification report: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2041396/comments/15
[19:26] -ubottu:#ubuntu-devel- Launchpad bug 2041396 in gdb (Ubuntu Jammy) "gdb 12.1 generates SIGILL on armhf" [Undecided, Fix Committed]
[19:30] <cpete> liushuyu: an additional bug is that experienced time is not guaranteed to be less than the traveled time
[19:30] <liushuyu> cpete: Exactly
[19:38] <rbasak> vininim: explanation here: https://bugs.launchpad.net/git-ubuntu/+bug/1761821
[19:38] -ubottu:#ubuntu-devel- Launchpad bug 1761821 in git-ubuntu "Spurious error message: fatal: could not read Username for 'https://git.launchpad.net': terminal prompts disabled" [Medium, Triaged]
[19:38] <mfo> jamespage, hey o/ re: py3.12/eventlet
[19:38] <mfo> jamespage, sure, happy to help
[19:39] <mfo> jamespage, glad there's a new upstream version with those, that's good news
[19:41] <mfo> jamespage, btw, you probably noticed that too, but mentioning just in case you also look at py3.12 for nose -- there's still a hunk in python-eventlet's d/rules to ignore nose.config SyntaxWarnings on py3.12, that can go away too if that is fixed in nose
[19:41] <mfo> :)
[19:42] <mfo> reference: (PYTHONWARNINGS="$$([ $$i != 3.12 ] ...
[20:05] <liushuyu> Ah, the struggle has finally coming to an end https://launchpad.net/ubuntu/+source/rustc-1.68/1.68.2+dfsg0ubuntu1-0ubuntu7/+build/27651974
[20:21] <jbicha> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Mantic | Patch Pilots: N/A
=== blahdeblah_ is now known as blahdeblah