=== mfo_ is now known as mfo [05:25] -queuebot:#ubuntu-release- New binary: libkiwix [amd64] (kinetic-proposed/universe) [11.0.0-2] (no packageset) [05:26] -queuebot:#ubuntu-release- New binary: libkiwix [ppc64el] (kinetic-proposed/universe) [11.0.0-2] (no packageset) [05:31] -queuebot:#ubuntu-release- New binary: libkiwix [s390x] (kinetic-proposed/universe) [11.0.0-2] (no packageset) [06:05] -queuebot:#ubuntu-release- New binary: libkiwix [arm64] (kinetic-proposed/universe) [11.0.0-2] (no packageset) [06:05] -queuebot:#ubuntu-release- New binary: libkiwix [armhf] (kinetic-proposed/universe) [11.0.0-2] (no packageset) [06:27] -queuebot:#ubuntu-release- New binary: libkiwix [riscv64] (kinetic-proposed/universe) [11.0.0-2] (no packageset) [07:16] paride: which is the 'full jammy arm64 iso' test? I recall doing the ubuntu base image smoke test, which I ran locally on a RPi4 [07:20] ginggs, hi! I meant an install from the ISO image, and not from a preinstalled image like the rpi ones, so if you if you only tested on rpi that's not what I was looking for [07:21] ginggs, however I think I sorted it out, I apparently I was hitting https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1921664 [07:21] Launchpad bug 1921664 in qemu (Ubuntu) "Coroutines are racy for risc64 emu on arm64 - crash on Assertion" [Low, Incomplete] [07:22] I recompiled qemu without lto and it's not crashing anymore (despite a comment there saying that a version reported working was already compiled with lto) [07:48] lto1: fatal error: bytecode stream in file ‘/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/libSPIRV.a’ generated with LTO version 11.3 instead of the expected 12.0 [07:48] mmmmm [07:48] something is making ffmpeg ftbfs [07:49] doko, maybe you need to add this rebuild on your "new default gcc uploaded" list? [08:09] -queuebot:#ubuntu-release- New sync: oem-sutton.newell-cagatay-meta (focal-proposed/primary) [20.04~ubuntu1] [08:09] -queuebot:#ubuntu-release- New sync: oem-sutton.newell-cagney-meta (focal-proposed/primary) [20.04~ubuntu1] [08:10] -queuebot:#ubuntu-release- New sync: oem-sutton.newell-cai-meta (focal-proposed/primary) [20.04~ubuntu1] [08:10] -queuebot:#ubuntu-release- New sync: oem-sutton.simon-cais-meta (focal-proposed/primary) [20.04~ubuntu1] [08:10] -queuebot:#ubuntu-release- New sync: oem-sutton.newell-caia-meta (focal-proposed/primary) [20.04~ubuntu1] [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-cagatay-meta to canonical-oem-metapackages in bionic [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-cagney-meta to canonical-oem-metapackages in bionic [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-cai-meta to canonical-oem-metapackages in bionic [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-caia-meta to canonical-oem-metapackages in bionic [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.simon-cais-meta to canonical-oem-metapackages in bionic [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-cagatay-meta to canonical-oem-metapackages in focal [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-cagney-meta to canonical-oem-metapackages in focal [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-cai-meta to canonical-oem-metapackages in focal [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-caia-meta to canonical-oem-metapackages in focal [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.simon-cais-meta to canonical-oem-metapackages in focal [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-cagatay-meta to canonical-oem-metapackages in jammy [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-cagney-meta to canonical-oem-metapackages in jammy [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-cai-meta to canonical-oem-metapackages in jammy [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.newell-caia-meta to canonical-oem-metapackages in jammy [08:28] -queuebot:#ubuntu-release- Packageset: Added oem-sutton.simon-cais-meta to canonical-oem-metapackages in jammy [11:28] ubuntu-archive po4a, a build-depends of apt, now needs libsyntax-keyword-try-perl, please add it to the i386 allowlist and copy-package -b --force-same-destination -e 0.27-1 libsyntax-keyword-try-perl [14:32] hello SRU team, I would like to see if we can get bug 1852610 reviewed in the bionic unapproved queue and also have bug 1965297 reviewed (verification-done) in focal-proposed. [14:32] Bug 1852610 in nova (Ubuntu Bionic) "[SRU] API allows source compute service/node deletion while instances are pending a resize confirm/revert" [Undecided, In Progress] https://launchpad.net/bugs/1852610 [14:32] Bug 1965297 in neutron (Ubuntu Focal) "l3ha don't set backup qg ports down" [High, Fix Committed] https://launchpad.net/bugs/1965297 [14:38] Hello everyone! I will be spinning the *real* RC images for .1 in less than an hour [14:39] Reason for that is that linux-lowlatency was missed in the set of packages that had to be released, and it's used by studio. Normally we'd just rebuild studio, but we also had a few security updates (like samba) landing today, which means we have to respin all or nothing [14:40] That being said, the plan was anyway to spin the real RCs today, so I think it's still fine. I published mesa and libreoffice, will wait for them to migrate and will spin the images once they're all published [14:41] sil2100: Reminder about SRU bug 1983136 with the secure boot issue for Studio [14:41] Bug 1983136 in ubuntustudio-meta (Ubuntu Jammy) "[SRU] v4l2loopback-dkms breaks secure boot installation in seed" [Critical, In Progress] https://launchpad.net/bugs/1983136 [14:42] Eickmeyer[m]: reviewing o/ [14:44] Eickmeyer[m]: hm, since studio was the only one to seed v4l2loopback, can you remind me why was it seeded in the first place? [14:44] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-meta [source] (jammy-proposed) [0.266.2] [14:44] I just need to assess how feasible would it be to fast-track that [14:45] It goes hand-in-hand with OBS Studio to give a means for it to make an output as a webcam device selectable in a videoconferencing application such as Skype, Zoom, Google Meet, etc. Not exactly essential, completely optional. [14:45] Was seeded as a matter of convenience. [15:20] Please review the SRU in bug 1969734. The package in question is a VPN support package in the universe component that fails to work with network-manager-openconnect (a plugin for NetworkManager to work with this package). [15:20] Bug 1969734 in openconnect (Ubuntu) "[Jammy] NetworkManager-openconnect 1.2.6 not compatible with openconnect 8.20" [Undecided, In Progress] https://launchpad.net/bugs/1969734 [15:20] sil2100: ^ [15:21] juliank: done [15:21] vorlon: thanks [15:23] sil2100: From the [Impact] section, "Users with a common GlobalProtect serverside configuration will not be able to connect." [15:32] So this is a fatal bug for users of certain VPNs. [15:37] sil2100: Are you reviewing this SRU? [15:37] I only reformatted the patch and uploaded the patched source package to my test builds PPA. [15:43] vorlon: Can you review this SRU? This is a fatal bug for users of some VPNs. [15:43] -queuebot:#ubuntu-release- Packageset: Removed hesiod from i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added cachy to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added clikit to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added crashtest to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added libsyntax-keyword-try-perl to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added pastel to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added pep517 to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added pexpect to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added poetry to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added poetry-core to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added ptyprocess to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added pylev to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added python-build to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added python-cleo to i386-whitelist in kinetic [15:43] -queuebot:#ubuntu-release- Packageset: Added python-installer to i386-whitelist in kinetic [15:44] -queuebot:#ubuntu-release- Packageset: Added python-lockfile to i386-whitelist in kinetic [15:44] -queuebot:#ubuntu-release- Packageset: Added python-pkginfo to i386-whitelist in kinetic [15:44] -queuebot:#ubuntu-release- Packageset: Added python-requests-toolbelt to i386-whitelist in kinetic [15:44] -queuebot:#ubuntu-release- Packageset: Added python-tomlkit to i386-whitelist in kinetic [15:44] -queuebot:#ubuntu-release- Packageset: Added shellingham to i386-whitelist in kinetic [15:44] luis220413: not my SRU day, I'm working on other things; this doesn't look to me like a critical bug that requires queue jumping [15:46] vorlon: But can you just set the importance of the bug tasks: network-manager-openconnect to Wishlist and openconnect to High? [15:47] luis220413: I can but the SRU team doesn't care about the importance field as set [15:47] vorlon: I have made multiple requests on #ubuntu-bugs and did not receive replies. Where should I do those requests? [15:50] luis220413: I don't think you should worry about requesting changes to bug priorities, those really aren't relevant to developers unless it's an actively-maintained package where the developers are trying to manage a backlog of bugs and this is not that [15:51] I also requested on #ubuntu-bugs in the last few days that several bugs be closed as Won't Fix [15:51] luis220413: also as far as SRU review, I release after checking that there is no package in the jammy-proposed queue currently for this, it looks like what you need is an upload sponsor - I see they're subscribed but there hasn't been activity there yet. #ubuntu-devel is a better venue for getting a sponsor as it's a wider audience [15:51] vorlon: OK [15:51] having an Ubuntu SRU team member as your sponsor reduces the number of SRU Team members who can review! [15:59] vorlon: OK [16:00] luis220413: I'm sadly a bit busy with point-release things today, but I might do a quick queue review sweep a bit later [16:01] sil2100: I already asked for a sponsor for this SRU in #ubuntu-devel. [16:01] Eickmeyer[m]: ok, that sounds like something we should try maybe getting for .1. You feel comfortable releasing ubuntustudio-meta today? [16:03] sil2100: Is this package preinstalled (or going to be preinstalled for 22.04.1) in any Ubuntu 22.04 flavor (including Desktop and Server)? [16:04] I am referring to the binary packages built from the openconnect source package. [16:04] If so, I believe this must be fixed in the point release. [16:05] sil2100: Yes, that sounds great. [16:05] Eickmeyer[m]: can you try install-testing the ubuntustudio-meta from -proposed just to make sure nothing blew up [16:05] luis220413: hm, let me take a look [16:07] luis220413: looks like it's seeded in studio and kubuntu - but this would be something we'd release post-.1 [16:08] sil2100: What does "seeded" mean? [16:08] sil2100: I can. Hang on... [16:09] luis220413: ah, it means it's preinstalled by default either on given images or on the target systems that are being installed with it [16:10] So yeah, Kubuntu and Ubuntu Studio essentially use it, but I need to close the gates today for SRUs for .1 since Thursday is release day [16:14] sil2100: Do a substantial number of users require a VPN of this kind to access web services accessed during installation (for updates and statistics)? If so, this must be released today. [16:17] luis220413: I don't think our installers support configuring VPN access during installation [16:18] sil2100: Can a SRU be accepted into the proposed pocket for 22.04 tomorrow? [16:19] sil2100: OK. So this SRU will not be released into Ubuntu 22.04.1. [16:19] luis220413: I think we can look into getting this into -proposed. Did you find someone that could manage to sponsor this for you? I could do a quick SRU review on it in the next hours then [16:20] sil2100: No. [16:24] sil2100: If the VPNs supported by OpenConnect are used by a substantial number of users, I would like to get these 2 source packages into the main component and enabled in all flavors (including Desktop and Server). [16:34] luis220413: for a package to be included in main, there is a set of requirements that need to be fullfilled and someone in Canonical needs to be willing to own the package in question. See https://github.com/canonical/ubuntu-mir for details [16:35] Eickmeyer[m]: how's the package looking? I doubt that anything will explode because of it ;p [16:35] sil2100: Nothing exploded, looks good. [16:35] Metapackages are easy. [16:39] Eickmeyer[m]: thanks, published. Will start spinning images now anyway, will add studio to the set once the metapackage migrates [16:39] s/migraets/publishes/ [16:39] Sounds good. [16:39] sil2100: What is the exact date of Feature Freeze for Ubuntu 22.10? I would like to get these packages in main for Ubuntu 22.10. [16:40] luis220413: August 25 [16:41] luis220413: you are welcome to try, but there usually needs to be a sound reason for a new package being included in main, and it's up to the Ubuntu MIR team decision then [16:42] sil2100: My reason is that the package already has a substantial number of users in Ubuntu X and subsequent releases, and should be promoted to main for that and subsequent releases under standard support (including Kinetic). [16:42] Where X is under standard support (i.e. X >= 18.04) [16:43] I have already seen a few main inclusion reports. [16:58] luis220413: fill in an MIR with all the details and start the discussion with the ubuntu-mir team o/ [16:58] Okay everyone, 22.04.1 RCs will be spinning in a moment [17:03] sil2100: Can I file a single MIR bug for 2 source packages? [17:05] sil2100: OK. I will do so enough time before Feature Freeze. [17:06] And as soon as possible because I want this feature to be supported by Canonical, even if not installed by default on Ubuntu Desktop or some flavors. [17:14] Or Ubuntu Server [17:24] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Jammy 22.04.1] has been updated (20220801) [17:25] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220801) [17:26] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220801) [17:30] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220801) [17:31] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Jammy 22.04.1] has been updated (20220801) [17:32] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Jammy 22.04.1] has been updated (20220801) [17:33] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Jammy 22.04.1] has been updated (20220801) [17:51] luis220413: I think 2 packages on one MIR seem fine [17:51] Eickmeyer[m]: ok, studio building now as well [17:51] sil2100: Thanks! [17:53] sil2100: OK! But I will check with the ubuntu-mir team. [17:53] sil2100: When will the Ubuntu Server image build? [17:54] luis220413: for .1? hm, sadly those might take a while, since it builds all the arches and only publishes once all are done. And the RISC-V builds usually take a long time [17:54] So they might only appear later, during the night [18:18] bdmurray, sil2100: was LP: #1977493 on the list to fix before turning on 22.04 upgrades? [18:18] it has a duplicate bug now [18:24] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Jammy 22.04.1] has been updated (20220801) [18:25] We, or I at least, was looking at bugs with a milestone of 22.04.1 so no that wasn't. [18:29] -queuebot:#ubuntu-release- Unapproved: accepted yt-dlp [source] (jammy-backports) [2022.07.18-1~bpo22.04.1] [18:29] -queuebot:#ubuntu-release- Unapproved: accepted gallery-dl [source] (focal-backports) [1.22.4-1~bpo20.04.1] [18:35] sil2100: Why did the Ubuntu Server builds for the other architectures finish? And why do the RISC-V builds take so long? [18:35] All RISC-V builds take longer than other arches right now, generally. [18:39] tsimonq2: And riscv64 is restricted in PPAs: https://answers.launchpad.net/launchpad/+question/702628 [18:40] It's a new architecture. It will take some degree of patience for those builds. [18:41] tsimonq2: That does not explain the slowness unless you are bootstrapping the archive for riscv64, that was already done before Ubuntu 20.04 (focal) was released. [18:42] tsimonq2: Restricted means that only site administrators can enable or disable the architecture in PPAs [18:42] sil2100: s/Why/When/ [18:42] I know, I've been a Core Developer for several years now. It's not because it's new in Ubuntu, it's because the architecture is new. [18:43] bdmurray: alas; it got a jira card targeted to 22.04.1 but the tag didn't land on the bug [18:44] bdmurray: do you think we should try to slot this in? [18:46] luis220413: riscv64 is a new architecture, there is no server-grade hardware available at scale, the current Launchpad implementation uses qemu, and every possible build farm implementation is slow [18:47] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Jammy 22.04.1] has been updated (20220801) [18:59] vorlon: I have just set that bug to Invalid because the reporter has fixed their issue after fixing the configuration, that was the cause for the upgrade failure. [18:59] sil2100: Same [19:00] bdmurray: Same [19:00] luis220413: Please avoid mass-pinging unless you need to. [19:01] tsimonq2: I wanted to notify vorlon and bdmurray but not sil2100 [19:02] facepalm [19:03] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Jammy 22.04.1] (20220801) has been added [19:03] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Jammy 22.04.1] has been updated (20220801) [19:03] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Jammy 22.04.1] has been updated (20220801) [19:03] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Jammy 22.04.1] has been updated (20220801) [19:03] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Jammy 22.04.1] has been updated (20220801) [19:03] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Jammy 22.04.1] has been updated (20220801) [19:13] -queuebot:#ubuntu-release- New: accepted libfile-dirlist-perl [source] (focal-backports) [0.05-2~bpo20.04.1] [19:15] -queuebot:#ubuntu-release- New binary: libfile-dirlist-perl [amd64] (focal-backports/universe) [0.05-2~bpo20.04.1] (no packageset) [19:19] rbasak: could you take a look at this bug? It seems they are waiting for a SRU upload rejection and you commented there: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1977870 [19:19] Launchpad bug 1977870 in lxcfs (Ubuntu Bionic) "SRU fix for LP#1807628" [Undecided, In Progress] [19:23] -queuebot:#ubuntu-release- New: accepted libfile-dirlist-perl [amd64] (focal-backports) [0.05-2~bpo20.04.1] [20:35] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Jammy 22.04.1] has been updated (20220801) [20:35] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Jammy 22.04.1] has been updated (20220801) [20:35] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+nezha [Jammy 22.04.1] has been updated (20220801) [20:35] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Jammy 22.04.1] has been updated (20220801) [20:35] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+visionfive [Jammy 22.04.1] has been updated (20220801) === mpontillo_ is now known as mpontillo === Kamilion|ZNC is now known as Kamilion === patviafore_ is now known as patviafore [21:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Jammy 22.04.1] (20220801.3) has been added [21:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Jammy 22.04.1] (20220801.3) has been added [21:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Jammy 22.04.1] (20220801.3) has been added [21:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Jammy 22.04.1] (20220801.3) has been added [21:52] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Jammy 22.04.1] (20220801.3) has been added [22:10] -queuebot:#ubuntu-release- Unapproved: openconnect (jammy-proposed/universe) [8.20-1 => 8.20-1ubuntu0.1] (kubuntu) [23:20] -queuebot:#ubuntu-release- New binary: golang-github-pion-turn.v2 [amd64] (kinetic-proposed/universe) [2.0.8-3] (no packageset) [23:44] what's the best way for me to reach Ubuntu Kylin developers? bug 1934661 needs to be resolved to complete the gnome-desktop transition [23:44] Bug 1934661 in kylin-greeter (Ubuntu) "kylin-greeter build-depends on missing ukui-settings-daemon-dev:amd64" [Critical, New] https://launchpad.net/bugs/1934661 [23:44] it would be good if they could look into bug 1964774 too. There are no Launchpad bug subscribers for those source packages [23:44] Bug 1964774 in ubuntu-kylin-wizard (Ubuntu) "ubuntu-kylin-wizard fails to build" [High, New] https://launchpad.net/bugs/1964774 [23:48] jbicha: A web page do ya any good - https://www.ubuntukylin.com/news/ ? [23:49] I get a 403 Forbidden when I try to access that domain [23:51] I guess I should just try to email handsome_feng [23:54] jbicha: Yesterday at one point I got a 503 on that server - now I gfet a 504 timeout - let me see if I do not have a different contact. International politics at play here ?