[01:41] teward: Did you clean up https://github.com/lubuntu-team/pastebinit, or is something force pushing there? [02:45] i think something's force pushing [02:45] Unit193: that repo is not going to be the primary repo as soon as Simon gives me comaintainer on the package in Salsa [02:45] Well if you didn't, then obviously yeah. I do appreciate that one, but... [02:45] we're gonna move it out of whatever is force-pushing [02:45] but i've also been spending the past ~12hours getting my new laptop set up with stuff [02:46] like right now only NOW I'm getting to the irccloud and stuff setups xD [02:46] Having it on GH makes more sense as upstream than on salsa, fwiw. You can have the opensuse person make patches. [02:46] Unit193: oh definitely, but I mean, not in lubuntu-team/pastebinit [02:46] Yeah not the best. :P [02:46] i've already got SImon's OK to do so [02:46] and also got his ack to add myself to uploaders if he goes and does his dcut commands [02:47] but right now i'm staring the "you're screwed" problem of needing my key signed again for a new key in debian-keyring. Because new smartcard. [02:47] (and because there's no USB-A ports in the computer and my USB-A yubikey is replaced by a usb-c one) [02:47] https://github.com/Unit193/pastebinit/commits/master has a couple more now too. [03:06] .. well that took an hour to shrink the filesystem geez. === pizzaiolo is now known as pizza [08:30] jbicha: hey! your upload for glib-networking is failing autopkgtest. D'you have time to look at it, please? [08:31] let me know otherwise. [08:42] bah, armhf builders have died at this point. (: [08:45] Hi everyone, can someone with enough rights trigger the rebuild of psycopg2 package? It failed 2 weeks ago because it lacked dependencies that landed a few days back so that should be enough: https://launchpad.net/ubuntu/+source/psycopg2/2.9.3-1 [08:45] Thanks! [08:48] alexghiti: on it === schopin_ is now known as schopin [08:50] schopin: Thanks! [12:26] utkarsh2102: feel free to take a look. There was only one commit that apparently triggered the test failures https://gitlab.gnome.org/GNOME/glib-networking/-/commits/glib-2-72/ === ginggs_ is now known as ginggs [14:08] is there a way to NOT install the ubuntu-server package with the new automatic installer? I cannot find anything related in the autoinstall reference documentation [15:25] I am looking for a core dev to sponsor bug 1987850 [15:25] Bug 1987850 in pcre2 (Ubuntu) "pcre2 10.40-1 causes siridb-server FTBFS on ppc64el" [Undecided, New] https://launchpad.net/bugs/1987850 [15:27] enr0n: I'll take a look :) [15:28] I found another component mismatch, this time in Ubuntu 20.04: ubuntu-standard (main) depends on dnsutils (universe). However, bind9-dnsutils provides dnsutils. [15:30] One of my queestions remains unanswered: What is the best way to propose that a package be seeded in an Ubuntu flavor (including Desktop and Server but not Core)? [15:31] *questions [15:33] Can anyone from the MIR team tell the correct owning team for bug 1986592 and the subordinate MIRs? [15:33] Bug 1986592 in network-manager-openconnect (Ubuntu) "[MIR] network-manager-openconnect" [Low, Incomplete] https://launchpad.net/bugs/1986592 [15:33] I mean the MIR approval team [15:34] schopin: thanks! [15:37] luis220413: The `Provides: dnsutils` in main means there isn't a component mismatch: I can install `ubuntu-standard` with only `main` enabled. === justDeez is now known as justache [19:13] Can a core dev please retry autopkgtest from `retry-autopkgtest-regressions --log-regex "Removing sudo" --blocks systemd -s kinetic`? These needed a glibc trigger (for 2.36-0ubuntu2), and should be OK now that glibc 2.36-0ubuntu2 is in the release pocket. [19:18] And, can a MOTU or core dev please retry this build https://launchpad.net/ubuntu/+source/siridb-server/2.0.48-1/+build/24315647 ? It should be able to build now with pcre2 10.40-1ubuntu1 in -proposed. [19:40] enr0n: re-triggered the tests for you [19:40] kanashiro[m]: thanks! [19:40] and the package you mentioned built fine already [19:51] Not sure if you're saying that it was you who re-tried it, but thanks if you did (I see it was re-tried ~20 minutes ago). [20:02] no, I did not :) maybe someone else [20:22] doko: how do you suggest we handle Debian bug 1015556 in Ubuntu? [20:22] Debian bug 1015556 in src:network-manager "network-manager: ftbfs with LTO (link time optimization) enabled" [Minor, Open] https://bugs.debian.org/1015556 [20:23] doko: I guess we should just keep doing what we've been doing in Ubuntuu's NM, just add --enable-lto [21:05] I maintain gnome-shell-extension-autohidetopbar in Debian and upstream got a bug reported that the package is no longer available in 22.04 ... Is there a way to find out the reason for the removal? [21:06] "remove the extensions that need updating for the new gnome shell series" is why it was removed from jammy. [21:06] https://launchpad.net/ubuntu/+source/gnome-shell-extension-autohidetopbar/+publishinghistory [21:10] ok, thanks. however its compatible with gnome 42 :) [21:10] (as its d/control correctly declares) [21:11] At the time of the removal, I imagine it didn't? How is it with 43? [21:11] one thing that catches my eye: there was recently a epoch introduced in the package... I only see versions with the old version scheme in that list… Could the epoch be an issue? [21:12] https://sources.debian.org/src/gnome-shell-extension-autohidetopbar/1%3A108-1/debian/control/#L14 seems to say that 43 should work? If so, I can sync it now so it'll at least be in kinetic. [21:15] 42 for sure. IIRC 1:107-1 was already ok with 42. For 43, It is very *likely* that 1:108-1 will work with Gnome 43, but it is not tested yet. I think 43 lands in Debian sid these days, afterwards I can confirm it will work with 43. [21:16] !info gnome-shell kinetic [21:16] gnome-shell (43~beta-1ubuntu1, kinetic): graphical shell for the GNOME desktop. In component main, is optional. Built by gnome-shell. Size 847 kB / 3,924 kB. (Only available for linux-any.) [21:16] I'm hesitent to sync it if you're not sure, sooo... [21:17] (If I had GNOME or a clue about it, I'd simply have tested for you.) [21:18] tobi: most GNOME Shell extensions have been removed from Ubuntu. See https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from-universe-and-stop-auto-syncs/18437/9 [21:19] this was a compromise to allow us to provide new point releases (like 42.2 to 42.3) of gnome-shell while meeting expectations that things in Ubuntu wouldn't break because of updates [21:19] and allowing us a manageable amount of extensions to test [21:21] Unit193: it's been blacklisted so you would have gotten an error if you tried to syncpackage it [21:21] Yeah thought about checking that list since it didn't make it back in yet, didn't know if there'd have been a hangup from the last removal and forgotten though. [21:21] jbicha: :-| Actually this extension has a lots of users, they will not like this. [21:22] tobi: A lot of feedback from users is a good way to let devs know they did the wrong thing. [21:22] But thanks for the link, I'll post it in the upstream bug report. [21:23] tobi: I added it to the 22.04 LTS Release Notes and I haven't really heard much complaining đŸ¤· [21:23] it's a nice extension. I used it to give my GNOME 43 demo talk at debconf to get rid of all the Ubuntu chrome to focus on the full screen GNOME Boxes VMs of Debian [21:24] but I was able to easily install it with gnome-shell-extension-manager. I didn't need a Debian package for the extension [21:25] jbicha: this is actually a constant source of frustation upstream, and upstream was very happy that /me suggested to document to use the packaged version. People constantly installed non-compatible versions and complained about not working... [21:27] being stuck on say gnome-shell 42.1 when 42.6 is available with lots of bugfixes is a real problem too [21:29] GNOME Shell has gone back to enforcing the extension metadata versions by default; maybe that helps with earlier breakage that annoyed upstream? [21:38] one will see, I guess. I'll just report the news to upstream and consider this topic closed for me.