[00:22] <cjwatson> juergh,bdrung: FWIW I tracked this down as far as https://bugs.launchpad.net/launchpad/+bug/2029879 (i.e. the kernel team broke Launchpad ;-) )
[00:22] -ubottu:#ubuntu-devel- Launchpad bug 2029879 in Launchpad itself "send-bug-notifications hangs on a large number of notifications related to a single bug" [Undecided, New]
[00:28] <mwhudson> oh not how i was expecting them to break it!
[00:36] <tsimonq2> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: mwhudson
[00:43] <mwhudson> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A
[01:40] <vpa1977> Hi, would it be possible to restart https://launchpad.net/ubuntu/+source/rstcheck/6.1.2+~1.0.3-1/+build/26299872 . The package just built successfully in PPA: https://launchpad.net/~vpa1977/+archive/ubuntu/pastebinit/+sourcepub/15055289/+listing-archive-extra. Thank you !!!!
[02:12] <tsimonq2> vpa1977: .
[02:12] <vpa1977> Thank you !!!!
[02:13] <tsimonq2> No worries. :)
[02:13] <tsimonq2> vpa1977: Looking at bug 2029877 as well for you.
[02:13] -ubottu:#ubuntu-devel- Bug 2029877 in network-manager-strongswan (Ubuntu) "failure to build due to deprecated declarations" [Undecided, New] https://launchpad.net/bugs/2029877
[02:13] <tsimonq2> *ahem*
[02:13] <tsimonq2> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: tsimonq2
[02:13] <tsimonq2> ;)
[02:13] <vpa1977> Thank you =) tried to fix it properly but there are too many changes =)
[02:14]  * tsimonq2 thinks < GTK 4 && < Qt 6 should start going by the wayside. :P
[02:15] <tsimonq2> vpa1977: Let me just say, for the record, that the patch makes me *kinda* uncomfy.
[02:16] <tsimonq2> That being said, you filed both a Debian bug and an upstream one. It's a reasonable enough solution if it's truly going to fix the FTBFS and won't cause end-user issues.
[02:16] <vpa1977> hmmm, https://launchpadlibrarian.net/680308142/buildlog_ubuntu-mantic-amd64.rstcheck_6.1.2+~1.0.3-1_BUILDING.txt.gz - rstcheck still failed to build in archive, but builds in ppa
[02:17] <vpa1977> I have installed ppa version and checked that dialog works fine - I was able to configure vpn connection with strongwan
[02:17] <tsimonq2> Do yourself a favor and learn about piuparts :)
[02:17] <tsimonq2> Sponsoring
[02:18] <vpa1977> piuparts. yes this will help ;)
[02:20] <tsimonq2> Glad I could help ;) you should get an email soon, I'll also mark as such on the MP and the bug report. Pretty please, follow up once you get a patch ;)
[02:21] <vpa1977> tsimonq2: +1
[02:32] <tsimonq2> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A
[03:01] <tjaalton> LocutusOfBorg: nice, thanks
=== JanC_ is now known as JanC
[07:35] <bdrung> cjwatson, Thanks. Could I subsribe to this bug to follow the progress on it? ;-)
[08:36] <cjwatson> bdrung: maybe? :-)
[14:55] <tsimonq2> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: tsimonq2
[15:11] <tsimonq2> Bug 2029523 just needs an SRU template, otherwise it should be good.
[15:11] -ubottu:#ubuntu-devel- Bug 2029523 in docker.io-app (Ubuntu Jammy) "docker export is missing ownership information" [Undecided, New] https://launchpad.net/bugs/2029523
[15:12] <tsimonq2> Other sponsorship requests have been cleared out; I'm leaving that one on the queue.
[15:12] <tsimonq2> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A
[15:12] <tsimonq2> Still lurking if anyone needs sponsorship ;)
[15:12] <kanashiro[m]> tsimonq2: the docker.io-app bug is probably affecting other release as well, I am planning to take a look at that
[15:14] <tsimonq2> kanashiro[m]: Looks like it's pretty exclusively stable releases.
[15:14] <tsimonq2> In fact, seems like an SRU regression.
[15:14] <tsimonq2> In any case, all yours kanashiro[m] :)
[15:14] <kanashiro[m]> yes, it is a regression
[15:15] <kanashiro[m]> thanks :)
[15:21] <tsimonq2> No worries :)
[16:19] <ahasenack> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: ahasenack
[16:25] <utkarsh2102> vorlon: hey, so looking at https://ubuntu-archive-team.ubuntu.com/germinate-output/ubuntu.mantic/cloud-minimal, I just noticed it doesn't populate with the contents of the seed which the cloud-minimal "inherited" from, that is, contents of server-cloud-minimal. Is that expected? am I missing something?
[16:25] <utkarsh2102> similarly for https://ubuntu-archive-team.ubuntu.com/germinate-output/ubuntu.mantic/server-minimal. Should it not have the contents from server-cloud-minimal?
[16:32] <vorlon> utkarsh2102: expected
[16:32] <utkarsh2102> vorlon: oh, wait a second, germinate-output of cloud-minimal does mention ubuntu-cloud-minimal, is there where things are happening behind the scenes?
[16:32] <utkarsh2102> could you explain the BTS a bit, please? ^.^
[16:33] <vorlon> utkarsh2102: the seed contents aren't duplicated, the relationship is documented in https://ubuntu-archive-team.ubuntu.com/germinate-output/ubuntu.mantic/structure
[16:33] <vorlon> e.g. pretty much everything depends on 'standard', but we don't pull the contents of the standard seed into all the other seeds
[16:33] <vorlon> that would end up with an excess of task headers, for one thing
[16:33] <vorlon> (and probably duplicate dependencies in metapackages)
[16:36] <ahasenack> xypron: around?
[16:36] <xypron> ahasenack: Hi
[16:36] <ahasenack> xypron: sorry, I know it's late. I'm looking at the rsyslog merge
[16:36] <ahasenack> did you see the ping to push the logical tag? Do you have it locally?
[16:37] <xypron> No I don't have it. I need to get back to that but was busy with other stuff.
[16:37] <utkarsh2102> vorlon: aha, I was missing that, thank you! I could see that the installation of ubuntu-cloud-minimal on a fresh container is pulling in all the packages from server-cloud-minimal but couldn't comprehend what those files are showing, many thanks.
[16:38] <xypron> ahasenack: I really need to get more experience with git-ubuntu.
[16:38] <ahasenack> xypron: that's fine
[16:38] <ahasenack> xypron: you have split, going to logical with that is much simpler, a) remove changelog and update-maintainer commits
[16:39] <ahasenack> b) if you want, you can squash multiple commits changing the same thing into one. FOr example, one upload added a dep8 test, and the next upload changing something in that test. This could be one commit
[16:39] <ahasenack> this last bit (b) is optional
[16:39] <ahasenack> it just helps to keep our delta with debian more consice
[16:39] <ahasenack> er
[16:39] <ahasenack> concise
[16:40] <ahasenack> but I can continue without it, if there are no surprises in the commits and rebasing
[16:40] <ahasenack> (and I'm familiar with the rsyslog package, which I changed a bit in the past)
[16:40] <xypron> The only merge conflicts where on the test config file because Debian added some tests and our old Ubuntu created the same file.
[16:41] <ahasenack> right, they added a dep8 test
[16:41] <xypron> 3 of them
[16:42] <xypron> ahasenack: I am off now.
[16:42] <ahasenack> xypron: cool, enjoy the weekend!
[16:42] <utkarsh2102> vorlon: (probably not the last but) lastly, we do see "Recommened" packages being installed, too. For instance when I try to install ubuntu-cloud-minimal, it's pulling in software-properties-common.
[16:42] <utkarsh2102> root@mtemp:~# aptitude why software-properties-common
[16:42] <utkarsh2102> i   ubuntu-cloud-minimal Depends    cloud-init
[16:42] <utkarsh2102> i A cloud-init           Recommends software-properties-common
[16:43] <utkarsh2102> but we do have feature: no-follow-recommends in the seed definition.
[16:43] <utkarsh2102> would it still pull in the Recommends? I was under the assumption that it won't, unless explicitly told.
[16:44] <vorlon> utkarsh2102: no-follow-recommends affects the behavior of the *construction of the metapackage*; it has no effect on whether apt follows recommends at install time
[16:44] <vorlon> the cloud-init package in the archive still Recommends: software-properties-common, no matter what you write in the seed file.  So when you install ubuntu-cloud-minimal package, unless you override the apt option, you get default apt behavior to follow recommends
[16:46] <utkarsh2102> aha! so when we use that in livecd-rootfs, how should we use the seed in a way that's not going to be installing Recommends?
[16:47] <vorlon> I don't know that there is an interface for this in livecd-rootfs
[16:48] <utkarsh2102>    if [ "${SUBPROJECT:-}" = minimized ]; then
[16:48] <utkarsh2102>       add_package install ubuntu-cloud-minimal --no-install-recommends
[16:49] <utkarsh2102> because this won't look right^
[16:49] <utkarsh2102> :P
[16:49] <utkarsh2102> or would it?
[17:22] <vorlon> utkarsh2102: if that works, it's entirely an accident
[17:23] <utkarsh2102> hah!
[17:24] <utkarsh2102> mwhudson: any idea if we can leverage the --no-install-recommends feature in livecd-rootfs?
[18:45] <philroche> utkarsh2102:  We'd need to see if the `add_package ` function accepts arguments like that
[18:47] <utkarsh2102> philroche: of course, that's a given.
[18:47] <utkarsh2102> philroche: I'm just asking if they happen to know if we can actually leverage it.
[18:47] <utkarsh2102> a workaround or whatever.
[18:48] <utkarsh2102> it wouldn't be directly possible I imagine.
[19:28] <vorlon> you should not do that given the current architecture of the code
[19:29] <vorlon> because "add_package" explicitly takes its list of arguments and spits them out into a file under config/package-lists/
[19:29] <vorlon> can we be asking instead of cloud-init should not Recommend software-properties-common?
[19:45] <tsimonq2> For patch pilots, a fix for bug 1756748 is coming down the pipe. Should allow you to sync multiple packages at once.
[19:45] -ubottu:#ubuntu-devel- Bug 1756748 in ubuntu-dev-tools (Ubuntu) "[syncpackage] Allow me to sync multiple packages at one time" [Wishlist, In Progress] https://launchpad.net/bugs/1756748
[20:18] <cjwatson> BTW, LP bug notifications are working normally again - we basically just excised the several tens of thousands of notifications about a single bug being rapidly flipped back and forward between New and Incomplete by a rogue script.
[20:35] <cjwatson> (also I just pushed an MP to sort out alerting for it)
[20:53] <Unit193> Hmm, who do I ping about MATE things these days?
[21:05] <Unit193> tsimonq2: Speaking of ubuntu-dev-tools, does `pull-debian-source` work for you?
[22:08] <fossfreedom_> Anyone around with memories about ubiquity? I want to test making changes to ubiquity-dm to see what happens on the initial try install screen you see on booting a legacy iso. Any ideas how to restart into that screen?
[22:48] <RikMills> fossfreedom_: you can stop the display manager
[22:48] <RikMills> then sudo systemctrl start ubiquity.service
[22:49] <RikMills> I think....
[22:53] <ahasenack> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: Mantic Open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Bionic-Lunar | Patch Pilots: N/A
[22:59] <fossfreedom_> RikMills: yay! Cheers. That works nicely
[23:01] <RikMills> :)