-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Jammy Final] has been updated (20220418.2) | 00:59 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Jammy Final] has been updated (20220418.2) | 00:59 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Jammy Final] has been updated (20220418.2) | 01:00 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Jammy Final] has been updated (20220418.2) | 01:00 | |
=== plars_ is now known as plars | ||
-queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Jammy Final] has been updated (20220418.4) | 02:33 | |
=== cpaelzer_ is now known as cpaelzer | ||
bdmurray | sil2100: I'd like to have a speedy release of ubuntu-release-upgrader fixing bug 1968607. Agreed? | 08:20 |
---|---|---|
ubottu | Bug 1968607 in ubuntu-release-upgrader (Ubuntu Impish) "screen became locked during release upgrade" [Critical, Fix Committed] https://launchpad.net/bugs/1968607 | 08:20 |
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Jammy Final] (20220418.2) has been added | 08:31 | |
bdmurray | For the record sil2100 and I discussed this in person and he agreed with an early release of it | 08:41 |
sil2100 | +1 | 08:51 |
sil2100 | Ok everyone, we will be respinning 22.04 images shortly | 08:53 |
sil2100 | No real changes, but it seems the previous RCs were spun a bit too early and now they're out-of-sync with the jammy archive (re: vim and u-r-u) | 08:53 |
-queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Jammy Final] has been updated (20220419) | 10:18 | |
-queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Jammy Final] has been updated (20220419) | 10:19 | |
cjwatson | vorlon: perhaps laney's removal raced with a proposed-migration run already in progress. That would be consistent with the LP UI, since it *does* show the -proposed source being deleted, it just only shows the deletion message resulting from the copy-and-delete step (which I hypothesize was effectively a second deletion) | 10:19 |
cjwatson | I haven't checked the DB, but that would make a certain amount of sense | 10:19 |
-queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Jammy Final] has been updated (20220419) | 10:23 | |
-queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Jammy Final] has been updated (20220419) | 10:24 | |
laney | that would make sense to me | 10:26 |
laney | except I think the block-proposed tags are read before the britney run starts | 10:26 |
-queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Jammy Final] has been updated (20220419) | 10:27 | |
laney | so I'm not sure why it would have seen that I had closed it | 10:27 |
laney | would need to double check the code :-) | 10:27 |
-queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Jammy Final] has been updated (20220419) | 10:28 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Jammy Final] has been updated (20220419) | 10:29 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Jammy Final] has been updated (20220419) | 10:29 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Jammy Final] has been updated (20220419) | 10:36 | |
cjwatson | laney: they are, but doesn't it work off published Packages/Sources files rather than directly from LP publication records? | 10:53 |
cjwatson | laney: so the bug might be seen as closed even though Sources files are still from prior to the deletion | 10:53 |
cjwatson | distributed systems are hard | 10:53 |
laney | yeah we ask the API for the tags but the published archive for what packages exist, so there's a window of inconsistency there | 11:12 |
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Jammy Final] has been updated (20220419) | 11:14 | |
jbicha | I need to remember to file 2 bugs next time 😢 | 11:14 |
coreycb | jamespage: thoughts on removing vmware-nsx from the archive? see vorlon's msg above. | 12:44 |
jamespage | coreycb: no objections from me | 12:46 |
jamespage | coreycb: although I see we have been pushing snapshots... | 12:47 |
jamespage | oh I see its a r-dep | 12:47 |
coreycb | jamespage: yes it depends on neutron-fwaas which is really out of date and abandoned at this point | 12:54 |
-queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Jammy Final] has been updated (20220419) | 12:57 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Jammy Final] has been updated (20220419) | 12:57 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Jammy Final] has been updated (20220419) | 12:57 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Jammy Final] has been updated (20220419) | 12:57 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Jammy Final] has been updated (20220419) | 12:57 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Jammy Final] has been updated (20220419) | 12:57 | |
-queuebot:#ubuntu-release- New source: ignition-gazebo (jammy-proposed/primary) [6.4.0+ds-0ubuntu1] | 13:00 | |
coreycb | vorlon: I've updated the bug to ask for removal of vmware-nsx as well | 13:13 |
-queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Jammy Final] has been updated (20220419) | 13:19 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Jammy Final] has been updated (20220419) | 13:19 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Jammy Final] has been updated (20220419) | 13:19 | |
-queuebot:#ubuntu-release- Builds: Ubuntu WSL [Jammy Final] (2189939148) has been added | 14:11 | |
-queuebot:#ubuntu-release- New: accepted ignition-gazebo [source] (jammy-proposed) [6.4.0+ds-0ubuntu1] | 14:49 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Jammy Final] has been updated (20220419.1) | 15:03 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Jammy Final] has been updated (20220419.1) | 15:03 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Jammy Final] has been updated (20220419.1) | 15:03 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Jammy Final] has been updated (20220419.1) | 15:03 | |
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Jammy Final] has been updated (20220419.1) | 15:03 | |
vorlon | seb128: desktop images are still oversized vs the stated limit for both focal and jammy; do you have a different limit you want to set? | 15:13 |
vorlon | Wimpy: size limit hasn't been updated yet for ubuntu-mate - do you want to just tell me what size you want and I can land the change? | 15:13 |
-queuebot:#ubuntu-release- New binary: ignition-gazebo [amd64] (jammy-proposed/universe) [6.4.0+ds-0ubuntu1] (no packageset) | 15:15 | |
seb128 | vorlon, when Brian asked about it a few weeks ago we replied that bumping to 3.6G seemed reasonable, could you edit it to that value if that wasn't done yet? | 15:17 |
vorlon | seb128: ok. same for both focal and jammy? | 15:17 |
seb128 | yes | 15:17 |
rbasak | vorlon: lucasmoura asked me to do a 0-day SRU review for ubuntu-advantage-tools. How does this work for an SRU team member? I have no queue control for Jammy I don't think, and won't expect to have that on day 0. And presumably we're skipping the paperwork and verification process anyway? Or are you expecting normal SRU paperwork? | 15:18 |
vorlon | rbasak: normal SRU paperwork | 15:19 |
bdmurray | normal SRU paperwork | 15:19 |
bdmurray | ubuntu-sru may have permission on day 0 but you could let a release team member know if its critical to get out on day zero | 15:19 |
rbasak | OK thanks | 15:20 |
-queuebot:#ubuntu-release- New: accepted ignition-gazebo [amd64] (jammy-proposed) [6.4.0+ds-0ubuntu1] | 15:26 | |
-queuebot:#ubuntu-release- New binary: ignition-gazebo [ppc64el] (jammy-proposed/universe) [6.4.0+ds-0ubuntu1] (no packageset) | 15:28 | |
-queuebot:#ubuntu-release- New source: rshell (jammy-proposed/primary) [0.0.31-0ubuntu1] | 15:32 | |
-queuebot:#ubuntu-release- New: accepted ignition-gazebo [ppc64el] (jammy-proposed) [6.4.0+ds-0ubuntu1] | 15:34 | |
vorlon | waveform, jawn-smith: I'm not happy with taking 'rshell' as a package name for an Ubuntu-specific package; this is a dangerous bit of namespace homesteading | 15:38 |
jawn-smith | I was actually wondering about the name tbh | 15:38 |
jawn-smith | Though I don't think this is Ubuntu-specific. waveform has proposed the package to Debian as well | 15:39 |
vorlon | yes but if we accept it in NEW here that's an Ubuntu-specific accept | 15:41 |
vorlon | if it were accepted in Debian first, then no problem | 15:41 |
vorlon | but if Debian rejects the name and we accept it, we get a migration problem | 15:41 |
waveform | yes, it's horribly reminiscent of good ol' rsh -- unfortunately, that is what the upstream's been called for some years now | 15:41 |
vorlon | yes, but the binary package could have a longer, clarifying name | 15:42 |
vorlon | (and source package) | 15:43 |
vorlon | the python module name is fine | 15:43 |
waveform | pyboard-rshell? (it was originally intended for use with the "pyboard", a microcontroller specifically built around running micropython, although it now works with many more, including the pico) | 15:44 |
vorlon | that would work for me | 15:45 |
waveform | would you want just the source package name changed, or the /usr/bin binary too? | 15:45 |
waveform | erm, I mean source+bin packages in addition to the /usr/bin binary | 15:46 |
vorlon | waveform: just the package name, because that's Debian namespace; shipping the program under the name that all the documentation on the wider Internet references is reasonable | 15:46 |
waveform | okay, sounds good | 15:46 |
-queuebot:#ubuntu-release- New: rejected rshell [source] (jammy-proposed) [0.0.31-0ubuntu1] | 15:47 | |
sil2100 | jchittum: heeeey, how's the 22.04 release looking from the CPC POV? Any blockers? | 15:48 |
jchittum | we're looking green | 15:48 |
jchittum | sil2100: do you believe it to be safe to run preparatory builds tomorrow? we lack the staging ability of ISOs, but we can prep a daily "download" (the stuff on cloud-images.ubuntu.com) and be ready to build release images for all the other clouds | 15:58 |
sil2100 | jchittum: yeah, so far I think yes | 15:59 |
sil2100 | But I still want to wait for more testing feedback | 16:00 |
-queuebot:#ubuntu-release- New source: ignition-launch (jammy-proposed/primary) [5.0.0+ds-0ubuntu1] | 16:03 | |
-queuebot:#ubuntu-release- New source: text-engine (jammy-proposed/primary) [0.1.1-0ubuntu1] | 16:10 | |
-queuebot:#ubuntu-release- New: accepted ignition-launch [source] (jammy-proposed) [5.0.0+ds-0ubuntu1] | 16:28 | |
-queuebot:#ubuntu-release- New binary: ignition-launch [amd64] (jammy-proposed/none) [5.0.0+ds-0ubuntu1] (no packageset) | 16:32 | |
-queuebot:#ubuntu-release- New binary: ignition-launch [ppc64el] (jammy-proposed/none) [5.0.0+ds-0ubuntu1] (no packageset) | 16:33 | |
-queuebot:#ubuntu-release- New binary: ignition-launch [armhf] (jammy-proposed/none) [5.0.0+ds-0ubuntu1] (no packageset) | 16:35 | |
-queuebot:#ubuntu-release- New: accepted ignition-launch [amd64] (jammy-proposed) [5.0.0+ds-0ubuntu1] | 16:40 | |
-queuebot:#ubuntu-release- New: accepted ignition-launch [ppc64el] (jammy-proposed) [5.0.0+ds-0ubuntu1] | 16:40 | |
-queuebot:#ubuntu-release- New: accepted ignition-launch [armhf] (jammy-proposed) [5.0.0+ds-0ubuntu1] | 16:40 | |
Wimpy | vorlon: 3.5GB should be suitable. Thanks for the offer. | 16:42 |
vorlon | Wimpy: ah, that's quite a jump from 2.8? can do though | 16:44 |
Wimpy | Just trying to pick something that won't flap. | 16:45 |
vorlon | ack | 16:45 |
vorlon | Wimpy: now, ubuntu-mate on focal is actually at 3.8GB today... | 16:46 |
Wimpy | Ahhh, because it has the NVIDIA drivers and Jammy does not. | 16:46 |
Wimpy | So, perhaps 4.0GB then? | 16:46 |
vorlon | Wimpy: do you want it at 4GB for both series? | 16:46 |
Wimpy | Yeah, seems reasonable. | 16:46 |
vorlon | ok | 16:46 |
vorlon | Wimpy: pushed | 16:50 |
Wimpy | Thanks! | 16:52 |
jawn-smith | vorlon: pyboard-rshell uploaded | 17:52 |
-queuebot:#ubuntu-release- New source: pyboard-rshell (jammy-proposed/primary) [0.0.31-0ubuntu1] | 17:52 | |
ahasenack | has anybody tried the minimal install, without updates? I just did it in a vm and can't get the graphical login to work, I just get a blank screen | 18:34 |
ahasenack | I wasn't looking for this type of test when I started, so I'm about to retry, more carefully with my selections | 18:34 |
dbungert | ahasenack: given the mention of graphical login, is this the desktop iso? | 18:35 |
jbicha | ahasenack: what vm are you using? | 18:36 |
ahasenack | dbungert: yes | 18:37 |
ahasenack | jbicha: kvm on jammy itself, via libvirt | 18:37 |
ahasenack | I just switched to xorg, and there the login worked | 18:37 |
jbicha | that's what I was about to suggest :( | 18:37 |
ahasenack | the display is spice | 18:37 |
ahasenack | I logged in on the console while the graphical display was dark, and wayland was running, as were a bunch of desktopy things | 18:38 |
ahasenack | where is the wayland log? | 18:39 |
-queuebot:#ubuntu-release- New source: network-manager-sstp (jammy-proposed/primary) [1.3.0-0ubuntu1] | 18:43 | |
rbasak | ^ this essentiall the same as what is in Debian NEW, but unfortunately therefore needs a full review. | 18:45 |
jbicha | ahasenack: I see that issue too. It works for me if enable 3D Acceleration (not enabled by default) | 19:21 |
jbicha | but then there's also this really annoying issue (you have to toggle 3d accel): https://gitlab.gnome.org/GNOME/gnome-boxes/-/issues/759#note_1386057 | 19:21 |
ahasenack | huh | 19:21 |
ubottu | Issue 759 in GNOME/gnome-boxes "virtual machines won't work with 3d acceleration enabled" [Opened] | 19:21 |
ahasenack | so wayland needs 3d accel? | 19:22 |
jbicha | ahasenack: on your jammy host computer, edit /usr/share/osinfo/os/ubuntu.com/ubuntu-18.04.xml to remove the devices section. maybe reboot? then recreate your jammy guest | 19:33 |
ahasenack | why 18.04? | 19:34 |
jbicha | that worked for me with Boxes (I just needed to close Boxes, not reboot). That disables the 3D Acceleration feature (uses virgl) | 19:34 |
ahasenack | are those the templates for virt-manager? | 19:34 |
jbicha | it's osinfo-db and I think virt-manager uses it. GNOME Boxes definitely does | 19:35 |
jbicha | it's 18.04 because I tested and thought things worked starting from 18.04 but clearly there are still bugs. Later releases derive from 18.04. | 19:36 |
-queuebot:#ubuntu-release- Unapproved: gnome-control-center (focal-proposed/main) [1:3.36.5-0ubuntu3 => 1:3.36.5-0ubuntu4] (ubuntu-desktop) | 19:41 | |
vorlon | LocutusOfBorg: you've seen that jansson got stuck? | 20:29 |
ahasenack | jbicha: ok, I removed devices from that file, will reinstall in a few, I have to run an errand | 20:31 |
ahasenack | back | 21:08 |
ahasenack | jbicha: the suggestion worked, I just added a comment to the bug | 21:26 |
ahasenack | tcp scan, all ports (1-65535) finished, nothing was open in the live env | 21:42 |
ahasenack | maybe if "try ubuntu" is selected instead of "install ubuntu"? | 21:43 |
* ahasenack tries that | 21:43 | |
ahasenack | I see nothing in the live env either, when selecting "try ubuntu" | 21:48 |
ahasenack | not sure if there is a build id somewhere in /etc | 21:49 |
-queuebot:#ubuntu-release- Unapproved: osinfo-db (jammy-proposed/universe) [0.20220214-1ubuntu1 => 0.20220214-1ubuntu2] (no packageset) | 21:50 | |
ahasenack | I do see "remote desktop" set to "on" in the "sharing" tab of settings... | 21:51 |
ahasenack | in the live env | 21:51 |
-queuebot:#ubuntu-release- Unapproved: accepted osinfo-db [source] (jammy-proposed) [0.20220214-1ubuntu2] | 21:51 | |
-queuebot:#ubuntu-release- Unapproved: freeipmi (focal-backports/main) [1.6.4-3ubuntu1.1 => 1.6.9-2~bpo20.04.1] (ubuntu-desktop, ubuntu-server) | 21:58 | |
jbicha | please unblock osinfo-db to fix the black screen bug mentioned earlier | 23:19 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!