[08:35] <utkarsh21021> enr0n: thanks. I’ll take a look later today.
[08:35] <utkarsh21021> \o/
[11:32] <bluca> bdmurray: any update on the autopkgtest infra?
[14:11] <sergiodj> jbicha: hi there.  unless you have an objection I intend to merge wpewebkit from unstable in order to unblock cog
[14:14] <mdeslaur> sergiodj: what? we blocked wpewebkit and cog, why do you want to merge them again?
[14:14] <sergiodj> ah, wait, it's been removed from the archive
[14:14] <sergiodj> mdeslaur: sorry, my bad, too many tabs opened
[14:14] <mdeslaur> hrm, though it appears cog is still there by mistake
[14:14] <sergiodj> yes, it is
[14:15] <mdeslaur> that was bug 1981592
[14:15] -ubottu:#ubuntu-devel- Bug 1981592 in wpewebkit (Ubuntu) "Please remove wpewebkit and block syncs from Debian" [Undecided, Fix Released] https://launchpad.net/bugs/1981592
[14:15] <mdeslaur> vorlon: looks like cog never got blacklisted? ^
[15:07] <sergiodj> I'll reintroduce nim-{unicodeplus,regex} because (a) nim successfully builds with openssl3 now, and (b) bcbio depends on mosdepth which depends on nim-regex
[18:14] <bdmurray> bluca: we are having wider problems with the autopkgtest infrastructure (it wasn't systemd-upstream specific) and we are trying to work out a solution
[18:25] <tsimonq2> jbicha: Please, do not sync over Lubuntu packages
[18:25] <bluca> ok, thanks for checking - glad I didn't bork anything :D
[18:25] <tsimonq2> jbicha: We (as the Lubuntu team) specifically made the decision to manually review all changes coming from Debian LXQt.
[18:26] <tsimonq2> jbicha: Syncing over those packages conflicts with the Lubuntu and will now manually require work to get VCSes up to date.
[18:27] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: ^^^^ congrats, surprise manual review of the LXQt stack, yet again.
[18:28] <jbicha> tsimonq2: why don't you work together with Debian to maintain LXQt? It seems extra work for there to be 2 groups of people doing the same tasks
[18:28] <arraybolt3> tsimonq2: Meh, it was only one component right?
[18:28] <arraybolt3> jbicha: We attempted to do so. They reacted aggressively.
[18:28] <jbicha> arraybolt3: how long ago was that?
[18:28] <arraybolt3> Despite our best attempts to collaborate with them on their terms, they pretty much refused to let us help hardly at all.
[18:28] <tsimonq2> They actively revert and drop changes we consider to be important.
[18:29] <arraybolt3> jbicha: Very recently.
[18:29] <arraybolt3> I could look up emails to get an exact date.
[18:29] <tsimonq2> jbicha: There's a lot of nuance here.
[18:29] <arraybolt3> We're still working out how to work with the Debian Community Team and the Debian LXQt Team to get things repaired, but for now, Debian LXQt and Lubuntu LXQt have split and are maintained entirely separately.
[18:30] <tsimonq2> As a general rule, it's inappropriate to sync over packages only seeded in one flavor (especially as our primary DE) without even asking, especially when I explicitly put as such on MoM.
[18:30] <jbicha> this seems a pretty easy case: http://launchpadlibrarian.net/650570927/lxqt-about_1.2.0-0ubuntu1_1.2.0-1.diff.gz
[18:30] <arraybolt3> Notice that they changed our d/watch file.
[18:30] <arraybolt3> Also appears to have messed up a package version number a tiny bit, though not enough to really matter.
[18:31] <arraybolt3> And we lost Lubuntu-specific customizations to some fields in d/control.
[18:31] <jbicha> the ~ isn't wrong
[18:31] <jbicha> or at least inconsequential
[18:32] <tsimonq2> Doesn't negate the general point, which is, why would you sync the entire LXQt stack without asking?
[18:32] <tsimonq2> Why are we having this conversation after the fact?
[18:32] <jbicha> I did not use merges.ubuntu.com so I didn't see the note there
[18:32] <arraybolt3> The problem here isn't technical difficulties per se, but communication issues and general hostility.
[18:33] <arraybolt3> They change things in ways that don't work for Lubuntu (i.e., dropping symbols files, having libfm-qt and libfm-qt-common as one package), and refuse to accept changes that make things work for both. Why, I don't know.
[18:34] <jbicha> I met Andrew Lee last year & he seemed willing to want to work with Lubuntu
[18:35] <arraybolt3> That's certainly not the impression we got.
[18:36] <jbicha> I apologize for causing y'all extra work. A lot of the LXQt packages are in sync & it looked to me like others had useful improvements on the Debian side
[18:36] <arraybolt3> Meh, we'll live. :)
[18:37] <tsimonq2> ^^^ / apology accepted :)
[18:39] <jbicha> I met Andrew at DebConf. If either of you are able to get the time off work to attend https://debconf23.debconf.org/ it might help improve relations
[18:39] <jbicha> Debian does have bursary sponsorship you could apply for. Debian is interested in having more people from derivatives attend.
[18:40] <tsimonq2> I would certainly love to, if I can get the time off etc.
[18:40] <jbicha> India requires visas for people from almost all countries so you'll want to be thinking about it early
[18:41] <arraybolt3> I currently am unable to travel abroad so :-/ Perhaps there's some way to get Andrew and his team to actively be on IRC somewhere so that we can discuss what needs done to fix things. Emails and MRs that go ignored for weeks naturally make things sloooooow. :P
[18:57] <Eickmeyer[m]> jbicha: You also have to think about it this way: almost no packages from KDE are synced from Debian for Kubuntu, and such a thing would have to be cleared through the Kubuntu team anyhow.
[18:57] <Eickmeyer[m]> Different teams for different package sets.
[18:58] <arraybolt3> On the bright side, at least LXQt is relatively small and manageable. KDE would be huuuuuuge.
[18:58] <jbicha> I don't understand the Kubuntu divergence either
[19:01] <Eickmeyer[m]> Doesn't matter, it's there for a reason. Best to consult the appropriate team for the reason.
[19:03] <Eickmeyer[m]> Ubuntu != Debian. We must remind ourselves of this.
[22:20] <vpa1977> Hi, would it be possible to retry regressions for vim migraion:
[22:20] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=amd64&package=vim-ultisnips&trigger=vim%2F2%3A9.0.1000-4ubuntu2 (passes locally)
[22:20] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=armhf&package=vim-ultisnips&trigger=vim%2F2%3A9.0.1000-4ubuntu2 (timeout, might be infrastructure issue)
[22:20] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=arm64&package=entr&trigger=vim%2F2%3A9.0.1000-4ubuntu2 (infrastructure, connection failure)
[22:20] <vpa1977> https://autopkgtest.ubuntu.com/request.cgi?release=lunar&arch=s390x&package=vim-youcompleteme&trigger=vim%2F2%3A9.0.1000-4ubuntu2 (passed with ubuntu1 version of vim package, and ubuntu2 is a no-change upload http://launchpadlibrarian.net/649686327/vim_2%3A9.0.1000-4ubuntu1_2%3A9.0.1000-4ubuntu2.diff.gz)
[22:52] <Eickmeyer[m]> vpa1977: Done
[22:52] <vpa1977> Thank you!!!