[00:07] <Bashing-om> jbicha: Maybe not so good, but -- Susie from Ubuntu Kylin community >><EMAIL_ADDRESS>.
[00:42] <bdmurray> jbicha: there is an ubuntu-flavors irc channel where flavor leads hang out
[00:59] <arraybolt3[m]> Ubuntu Kylin's page loads for me here in the US.
[01:00] <arraybolt3[m]> If someone needs in there but can't load the page, I can probably download whatever you need and beam it over Google Drive, GitHub, or Matrix.
[01:04] <Bashing-om> arraybolt3[m]: Loads here now for me too :) I see what I can find for a developer link.
[01:13] <Bashing-om> jbicha: links from the [age still 504s - best I can see is: Email<EMAIL_ADDRESS>.
[01:13] <Bashing-om> page*
[01:21] <arraybolt3[m]> I also see this entire page full of email addresses: https://mailweb.ubuntukylin.com/postorius/lists/?page=1
[01:22] <arraybolt3[m]><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>look the most hopeful to me.
[04:44] -queuebot:#ubuntu-release- Unapproved: apparmor (bionic-proposed/main) [2.12-4ubuntu5.1 => 2.12-4ubuntu5.2] (core)
[05:21] -queuebot:#ubuntu-release- New binary: ismobilejs [amd64] (kinetic-proposed/none) [0.5.0-3] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: rubberband [i386] (kinetic-proposed/universe) [3.0.0+dfsg0-1] (i386-whitelist, kubuntu)
[05:21] -queuebot:#ubuntu-release- New binary: redland-bindings [amd64] (kinetic-proposed/universe) [<IP_ADDRESS>+dfsg-2] (i386-whitelist)
[05:22] -queuebot:#ubuntu-release- New binary: redland-bindings [i386] (kinetic-proposed/universe) [<IP_ADDRESS>+dfsg-2] (i386-whitelist)
[05:22] -queuebot:#ubuntu-release- New binary: rubberband [amd64] (kinetic-proposed/universe) [3.0.0+dfsg0-1] (i386-whitelist, kubuntu)
[05:23] -queuebot:#ubuntu-release- New binary: highway [s390x] (kinetic-proposed/universe) [1.0.0-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: rubberband [ppc64el] (kinetic-proposed/universe) [3.0.0+dfsg0-1] (i386-whitelist, kubuntu)
[05:24] -queuebot:#ubuntu-release- New binary: highway [ppc64el] (kinetic-proposed/universe) [1.0.0-1] (no packageset)
[05:24] -queuebot:#ubuntu-release- New binary: redland-bindings [s390x] (kinetic-proposed/universe) [<IP_ADDRESS>+dfsg-2] (i386-whitelist)
[05:24] -queuebot:#ubuntu-release- New binary: redland-bindings [ppc64el] (kinetic-proposed/universe) [<IP_ADDRESS>+dfsg-2] (i386-whitelist)
[05:24] -queuebot:#ubuntu-release- New binary: rubberband [s390x] (kinetic-proposed/universe) [3.0.0+dfsg0-1] (i386-whitelist, kubuntu)
[05:27] -queuebot:#ubuntu-release- New binary: highway [amd64] (kinetic-proposed/universe) [1.0.0-1] (no packageset)
[05:33] -queuebot:#ubuntu-release- New binary: redland-bindings [arm64] (kinetic-proposed/universe) [<IP_ADDRESS>+dfsg-2] (i386-whitelist)
[05:36] -queuebot:#ubuntu-release- New binary: rubberband [armhf] (kinetic-proposed/universe) [3.0.0+dfsg0-1] (i386-whitelist, kubuntu)
[05:38] -queuebot:#ubuntu-release- New binary: redland-bindings [armhf] (kinetic-proposed/universe) [<IP_ADDRESS>+dfsg-2] (i386-whitelist)
[05:38] -queuebot:#ubuntu-release- New binary: rubberband [arm64] (kinetic-proposed/universe) [3.0.0+dfsg0-1] (i386-whitelist, kubuntu)
[05:39] -queuebot:#ubuntu-release- New binary: rubberband [riscv64] (kinetic-proposed/universe) [3.0.0+dfsg0-1] (i386-whitelist, kubuntu)
[05:42] -queuebot:#ubuntu-release- New binary: redland-bindings [riscv64] (kinetic-proposed/universe) [<IP_ADDRESS>+dfsg-2] (i386-whitelist)
[08:09] -queuebot:#ubuntu-release- New binary: budgie-desktop [amd64] (kinetic-proposed/universe) [10.6.2+git20220728-1] (personal-fossfreedom, ubuntu-budgie)
[08:09] -queuebot:#ubuntu-release- Unapproved: openconnect (jammy-proposed/universe) [8.20-1 => 8.20-1ubuntu0.1] (kubuntu)
[08:10] <sil2100> Hello everyone! Please test our 22.04.1 release candidate images!
[08:10] <sil2100> http://iso.qa.ubuntu.com/qatracker/milestones/437/builds
[08:12] -queuebot:#ubuntu-release- New binary: budgie-desktop [s390x] (kinetic-proposed/universe) [10.6.2+git20220728-1] (personal-fossfreedom, ubuntu-budgie)
[08:13] -queuebot:#ubuntu-release- New binary: budgie-desktop [ppc64el] (kinetic-proposed/universe) [10.6.2+git20220728-1] (personal-fossfreedom, ubuntu-budgie)
[08:16] -queuebot:#ubuntu-release- New binary: budgie-desktop [arm64] (kinetic-proposed/universe) [10.6.2+git20220728-1] (personal-fossfreedom, ubuntu-budgie)
[08:18] -queuebot:#ubuntu-release- New binary: budgie-desktop [armhf] (kinetic-proposed/universe) [10.6.2+git20220728-1] (personal-fossfreedom, ubuntu-budgie)
[08:48] -queuebot:#ubuntu-release- New binary: budgie-desktop [riscv64] (kinetic-proposed/universe) [10.6.2+git20220728-1] (personal-fossfreedom, ubuntu-budgie)
[08:49] <arraybolt3[m]> sil2100: I just discovered an error on the Kubuntu 22.04.1 ISO - the release notes link pops open a text editor with the HTML code of the release notes, rather than opening a web browser.
[08:49] <arraybolt3[m]> I know this is to be reported on the QA tracker, but since this is a bug at a pretty critical time I'd better raise an alarm ASAP.
[08:50] <sil2100> arraybolt3[m]: huh? Wonder what happened, was that all good on 22.04 release images?
[08:50] <arraybolt3[m]> Checking...
[08:52] <arraybolt3[m]> Nope. The original 22.04 ISO has the exact same problem.
[08:52] <sil2100> Okay, so even though this is annoying, as it is not a regression compared to the GA images, let's make sure we have a bug filled in and prioritized
[08:53] <arraybolt3[m]> 👍
[08:54] <arraybolt3[m]> Do you know off the top of your head what package contains the Ubiquity config for each flavor? I'm about to file it against ubiquity-frontend-kde, but I'm not quite sure that's the right way to go.
[08:58] <RikMills> arraybolt3[m], known issue
[08:59] <arraybolt3[m]> RikMills: ack, no longer making bug report
[08:59] <RikMills> LP: #1967015
[09:20] -queuebot:#ubuntu-release- Unapproved: apt (bionic-proposed/main) [1.6.15 => 1.6.16] (core)
[09:44] -queuebot:#ubuntu-release- New: accepted budgie-desktop [arm64] (kinetic-proposed) [10.6.2+git20220728-1]
[09:44] -queuebot:#ubuntu-release- New: accepted budgie-desktop [riscv64] (kinetic-proposed) [10.6.2+git20220728-1]
[09:44] -queuebot:#ubuntu-release- New: accepted budgie-desktop [armhf] (kinetic-proposed) [10.6.2+git20220728-1]
[09:45] -queuebot:#ubuntu-release- New: accepted budgie-desktop [amd64] (kinetic-proposed) [10.6.2+git20220728-1]
[09:45] -queuebot:#ubuntu-release- New: accepted budgie-desktop [s390x] (kinetic-proposed) [10.6.2+git20220728-1]
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-ap-normalize [arm64] (kinetic-proposed) [<IP_ADDRESS>-1]
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-bitwise [ppc64el] (kinetic-proposed) [<IP_ADDRESS>-2]
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-kvitable [s390x] (kinetic-proposed) [<IP_ADDRESS>-2]
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-language-c99 [s390x] (kinetic-proposed) [0.1.3-1]
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-libbf [s390x] (kinetic-proposed) [0.6.3-1]
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-witch [ppc64el] (kinetic-proposed) [<IP_ADDRESS>-1]
[09:45] -queuebot:#ubuntu-release- New: accepted highway [amd64] (kinetic-proposed) [1.0.0-1]
[09:45] -queuebot:#ubuntu-release- New: accepted highway [s390x] (kinetic-proposed) [1.0.0-1]
[09:45] -queuebot:#ubuntu-release- New: accepted budgie-desktop [ppc64el] (kinetic-proposed) [10.6.2+git20220728-1]
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-bitwise [riscv64] (kinetic-proposed) [<IP_ADDRESS>-1]
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-language-c99 [ppc64el] (kinetic-proposed) [0.1.3-1]
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-lift-type [ppc64el] (kinetic-proposed) [<IP_ADDRESS>-1]
[09:45] -queuebot:#ubuntu-release- New: accepted highway [ppc64el] (kinetic-proposed) [1.0.0-1]
[09:45] -queuebot:#ubuntu-release- New: accepted lsb-release-minimal [amd64] (kinetic-proposed) [0.4-1]
[09:45] -queuebot:#ubuntu-release- New: accepted r-cran-fontawesome [amd64] (kinetic-proposed) [0.2.2-1]
[09:45] -queuebot:#ubuntu-release- New: accepted rust-concat-string [amd64] (kinetic-proposed) [1.0.1-1]
[09:45] -queuebot:#ubuntu-release- New binary: rust-protoc [ppc64el] (kinetic-proposed/universe) [2.27.1-1] (no packageset)
[09:45] -queuebot:#ubuntu-release- New binary: rust-scale-info-derive [ppc64el] (kinetic-proposed/universe) [2.1.2-1] (no packageset)
[09:45] -queuebot:#ubuntu-release- New: accepted golang-github-pion-turn.v2 [amd64] (kinetic-proposed) [2.0.8-3]
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-libbf [ppc64el] (kinetic-proposed) [0.6.3-1]
[09:45] -queuebot:#ubuntu-release- New: accepted ismobilejs [amd64] (kinetic-proposed) [0.5.0-3]
[09:45] -queuebot:#ubuntu-release- New: accepted rust-clap-lex [amd64] (kinetic-proposed) [0.2.4-1]
[09:45] -queuebot:#ubuntu-release- New binary: rust-retry [ppc64el] (kinetic-proposed/universe) [1.3.1-1] (no packageset)
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-bitwise [s390x] (kinetic-proposed) [<IP_ADDRESS>-2]
[09:45] -queuebot:#ubuntu-release- New: accepted lua-resty-core [amd64] (kinetic-proposed) [0.1.23-1]
[09:45] -queuebot:#ubuntu-release- New binary: rust-wrapcenum-derive [ppc64el] (kinetic-proposed/universe) [0.4.0-1] (no packageset)
[09:45] -queuebot:#ubuntu-release- New: accepted haskell-witch [s390x] (kinetic-proposed) [<IP_ADDRESS>-1]
[09:45] -queuebot:#ubuntu-release- New: accepted rust-dialoguer [amd64] (kinetic-proposed) [0.10.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted libkiwix [amd64] (kinetic-proposed) [11.0.0-2]
[09:46] -queuebot:#ubuntu-release- New: accepted libkiwix [armhf] (kinetic-proposed) [11.0.0-2]
[09:46] -queuebot:#ubuntu-release- New: accepted libkiwix [riscv64] (kinetic-proposed) [11.0.0-2]
[09:46] -queuebot:#ubuntu-release- New: accepted lua-resty-lrucache [amd64] (kinetic-proposed) [0.13-2]
[09:46] -queuebot:#ubuntu-release- New: accepted r-cran-fontawesome [amd64] (kinetic-proposed) [0.3.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted redland-bindings [arm64] (kinetic-proposed) [<IP_ADDRESS>+dfsg-2]
[09:46] -queuebot:#ubuntu-release- New: accepted redland-bindings [i386] (kinetic-proposed) [<IP_ADDRESS>+dfsg-2]
[09:46] -queuebot:#ubuntu-release- New: accepted redland-bindings [riscv64] (kinetic-proposed) [<IP_ADDRESS>+dfsg-2]
[09:46] -queuebot:#ubuntu-release- New: accepted rubberband [amd64] (kinetic-proposed) [3.0.0+dfsg0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rubberband [armhf] (kinetic-proposed) [3.0.0+dfsg0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted libkiwix [arm64] (kinetic-proposed) [11.0.0-2]
[09:46] -queuebot:#ubuntu-release- New: accepted libkiwix [s390x] (kinetic-proposed) [11.0.0-2]
[09:46] -queuebot:#ubuntu-release- New: accepted redland-bindings [amd64] (kinetic-proposed) [<IP_ADDRESS>+dfsg-2]
[09:46] -queuebot:#ubuntu-release- New: accepted redland-bindings [ppc64el] (kinetic-proposed) [<IP_ADDRESS>+dfsg-2]
[09:46] -queuebot:#ubuntu-release- New: accepted rubberband [arm64] (kinetic-proposed) [3.0.0+dfsg0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rubberband [ppc64el] (kinetic-proposed) [3.0.0+dfsg0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rubberband [s390x] (kinetic-proposed) [3.0.0+dfsg0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-clap-lex [armhf] (kinetic-proposed) [0.2.4-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-clap-lex [s390x] (kinetic-proposed) [0.2.4-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-concat-string [armhf] (kinetic-proposed) [1.0.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted libkiwix [ppc64el] (kinetic-proposed) [11.0.0-2]
[09:46] -queuebot:#ubuntu-release- New: accepted redland-bindings [armhf] (kinetic-proposed) [<IP_ADDRESS>+dfsg-2]
[09:46] -queuebot:#ubuntu-release- New: accepted rubberband [i386] (kinetic-proposed) [3.0.0+dfsg0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-clap-lex [arm64] (kinetic-proposed) [0.2.4-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-concat-string [arm64] (kinetic-proposed) [1.0.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-concat-string [riscv64] (kinetic-proposed) [1.0.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-dialoguer [arm64] (kinetic-proposed) [0.10.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-dialoguer [ppc64el] (kinetic-proposed) [0.10.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-dialoguer [s390x] (kinetic-proposed) [0.10.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-nvml-wrapper-sys [armhf] (kinetic-proposed) [0.6.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted lua-resty-lrucache [amd64] (kinetic-proposed) [0.13-3]
[09:46] -queuebot:#ubuntu-release- New: accepted rubberband [riscv64] (kinetic-proposed) [3.0.0+dfsg0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-concat-string [ppc64el] (kinetic-proposed) [1.0.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-dialoguer [armhf] (kinetic-proposed) [0.10.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-nvml-wrapper-sys [arm64] (kinetic-proposed) [0.6.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-nvml-wrapper-sys [s390x] (kinetic-proposed) [0.6.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-pcsc [arm64] (kinetic-proposed) [2.7.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-pcsc [ppc64el] (kinetic-proposed) [2.7.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-pcsc [s390x] (kinetic-proposed) [2.7.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-predicates [armhf] (kinetic-proposed) [2.1.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted redland-bindings [s390x] (kinetic-proposed) [<IP_ADDRESS>+dfsg-2]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-concat-string [s390x] (kinetic-proposed) [1.0.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-nvml-wrapper-sys [ppc64el] (kinetic-proposed) [0.6.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-pcsc [armhf] (kinetic-proposed) [2.7.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-predicates [arm64] (kinetic-proposed) [2.1.1-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-predicates [s390x] (kinetic-proposed) [2.1.1-1]
[09:46] -queuebot:#ubuntu-release- New source: ipu6-drivers (kinetic-proposed/primary) [0~git202204270226.8357dee9-0ubuntu1]
[09:46] -queuebot:#ubuntu-release- New source: lubuntu-installer-prompt (kinetic-proposed/primary) [0.2.0-0ubuntu1]
[09:46] -queuebot:#ubuntu-release- New binary: rust-retry [amd64] (kinetic-proposed/universe) [1.3.1-1] (no packageset)
[09:46] -queuebot:#ubuntu-release- New binary: rust-wrapcenum-derive [amd64] (kinetic-proposed/universe) [0.4.0-1] (no packageset)
[09:46] -queuebot:#ubuntu-release- New: accepted rust-clap-lex [ppc64el] (kinetic-proposed) [0.2.4-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-pcsc [amd64] (kinetic-proposed) [2.7.0-1]
[09:46] -queuebot:#ubuntu-release- New: accepted rust-predicates [ppc64el] (kinetic-proposed) [2.1.1-1]
[09:46] -queuebot:#ubuntu-release- New source: ivsc-driver (kinetic-proposed/primary) [0~git202205110052.b8c22f42-0ubuntu1]
[09:46] -queuebot:#ubuntu-release- New binary: rust-scale-info-derive [amd64] (kinetic-proposed/universe) [2.1.2-1] (no packageset)
[09:47] -queuebot:#ubuntu-release- New: accepted rust-protoc [ppc64el] (kinetic-proposed) [2.27.1-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-retry [amd64] (kinetic-proposed) [1.3.1-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-retry [armhf] (kinetic-proposed) [1.3.1-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-retry [s390x] (kinetic-proposed) [1.3.1-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-pcsc [riscv64] (kinetic-proposed) [2.7.0-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-protoc [s390x] (kinetic-proposed) [2.27.1-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-rust-embed-impl [ppc64el] (kinetic-proposed) [6.2.0-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-scale-info-derive [s390x] (kinetic-proposed) [2.1.2-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-tesseract-sys [riscv64] (kinetic-proposed) [0.5.12-3]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-typed-builder [ppc64el] (kinetic-proposed) [0.10.0-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-wrapcenum-derive [amd64] (kinetic-proposed) [0.4.0-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-wrapcenum-derive [s390x] (kinetic-proposed) [0.4.0-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-scale-info-derive [amd64] (kinetic-proposed) [2.1.2-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-typed-builder [amd64] (kinetic-proposed) [0.10.0-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-wrapcenum-derive [ppc64el] (kinetic-proposed) [0.4.0-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-retry [ppc64el] (kinetic-proposed) [1.3.1-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-typed-builder [s390x] (kinetic-proposed) [0.10.0-1]
[09:47] -queuebot:#ubuntu-release- New: accepted rust-tesseract-sys [armhf] (kinetic-proposed) [0.5.12-3]
[10:20] <arraybolt3> sil2100: I hate to bring up more stuff here, but for some reason, v4l2loopback is still in the latest Ubuntu Studio 22.04.1 ISO. Yes, I'm sure I downloaded the right one, and yes, I'm sure it's up to date. Secure Boot is blowing up as a result.
[10:21] <arraybolt3> LP #1983136
[11:06] <fossfreedom> sil2100: the jammy raspi image does not want to install for me - downloaded twice ... can you or any one else confirm? Stuck on the plymouth screen. Pressing esc shows lots of systemd start failures.
[11:07] <waveform> fossfreedom, I'll take a look in a mo -- I take it we're talking about the desktop image?
[11:09] <fossfreedom> The preinstalled image http://cdimage.ubuntu.com/jammy/daily-preinstalled/current/
[11:09] <sil2100> arraybolt3[m]: hm hm, might need to respin those. I made sure that rmadison was giving me the right ubuntustudio-meta
[11:12] <sil2100> arraybolt3[m]: ok, weird, since I see the right meta package pulled in
[11:12] <sil2100> Eickmeyer: ^
[11:12] <sil2100> Eickmeyer: is it pulled in via some dependency perhaps?
[11:17] <waveform> fossfreedom, yup that's the desktop image -- I'll spin one up in a bit (just downloading now)
[11:18] <waveform> fossfreedom, out of curiosity what medium are you booting from? SD card or something over USB (like an SSD)?
[11:20] <fossfreedom> SD card. Checked the 22.04 image and that's OK. Just the 22.04.1 that I am having an issue with
[11:21] <fossfreedom> 22.10 yesterdays daily is OK as  well.
[11:27] -queuebot:#ubuntu-release- Unapproved: rejected lxcfs [source] (bionic-proposed) [3.0.3-0ubuntu1~18.04.3]
[11:28] <rbasak> lucaskanashiro[m: rejected, but please note that rejection isn't required for an upload to happen over the top.
[11:31] <waveform> fossfreedom, okay -- flashing an SD card with the jammy daily now
[11:40] <sil2100> waveform, fossfreedom: thanks for taking a look
[11:41] <sil2100> I'll be a bit angry if this is a reproducible issue
[11:41] <waveform> fossfreedom, hmm -- seems to be booting happily to the oem setup for me. This is on a Pi 400 with board rev 1.1. What model of Pi are you using? (and, if possible, the board rev)
[11:41] <sil2100> Since basically this will put the whole point-release in jeopardy
[11:43] <arraybolt3[m]> I have an RPi I could probably rope into the mess real quick. Raspberry Pi 4 Model B 8 GB RAM. I'm pulling the image now and will flash it in a bit.
[11:46] <waveform> okay, I've got thru oem-setup now, just waiting on it to finish setup and I'll run thru one of the ISO tests (because that was on my list to do today anyway) but it's looking okay on the 400 so far ... will wait to see if fossfreedom can let us know what Pi they're using and will stick that next on my list to test (if it's different to the 400)
[11:51] <fossfreedom> waveform: it's a 8gb pi 4b
[11:52] <fossfreedom> Yeah. The oem setup didn't appear for me.
[11:52] <sil2100> Eickmeyer: give me a sign when you're up o/
[11:52] <arraybolt3> If anyone can reproduce it a second time, it'll be me then, since I have that exact same Pi.
[11:53] <arraybolt3> (I mean, I'm in a good spot to help reproduce it, sorry if that sounded wrong or weird...)
[12:14] <slyon> hey ubuntu-release! It looks like the download links for jammy-base images in the ISO tracker are broken for arm64/armhf/ppc64el, i.e.: http://cdimage.ubuntu.com/ubuntu-base/daily/20220801/jammy-base-arm64.tar.gz -> http://cdimage.ubuntu.com/ubuntu-base/jammy/daily/20220801/jammy-base-arm64.tar.gz
[12:18] <arraybolt3> fossfreedom: Just got the OEM setup screen on my Pi 4B 8GB. Everything seems to be going fine.
[12:20] <fossfreedom> arraybolt3: hmm.  Oh well. Just me. Thx for confirming.
[12:21] <arraybolt3> fossfreedom: Thanks for reporting so we could get it tested!
[13:25] <sil2100> slyon: argh, of course. I'll take a look, it's always such a manual process :|
[13:26] <sil2100> Actually, many of the isos will probably have the same problem
[13:26] <slyon> I tested most of the base images already, using the fixed URL (I think).
[13:27] <slyon> but if other isos might have the same issue it still makes sense to fix it
[13:28] <sil2100> It's a very manual process always, I think we need to think of ways of making this better. I have a few ideas, like finally fixing the daily tree structure for cdimage to be reliable
[13:28] <sil2100> But no time!
[13:28] <sil2100> Anyway, thanks for reporting, and thanks for testing!
[13:28] <slyon> yw
[13:58] <Eickmeyer> sil2100: I'm up, investigating the v4l2loopback issue. Might be pulled by a recommends?
[14:01] <Eickmeyer> sil2100: Can't find it in the rdepends, and it's dropped from the seed and the meta, so I'm very confused here.
[14:01] <sil2100> hm hm hm
[14:01] <sil2100> I'm in a meeting now, but let me dive into that as well
[14:02] <Eickmeyer> Just did a germinate and according to that it's gone.
[14:02] <Eickmeyer> ok
[14:02] -queuebot:#ubuntu-release- Unapproved: autofs (jammy-proposed/main) [5.1.8-1ubuntu1.1 => 5.1.8-1ubuntu1.2] (core)
[14:26] <paride> sil2100, hey, I submitted (good!) results for the subiquity candidate image
[14:26] -queuebot:#ubuntu-release- New source: dotnet6 (jammy-proposed/primary) [6.0.107-0ubuntu2~22.04.1]
[14:27] <paride> sil2100, I've got bitten again by the partial respin (the static validation expects 20220702 images), but I worked around that
[14:27] <sil2100> paride: ouch, sorry! hahah, yeah, was spinning some test images for intel-iot, forgot that this actually messes up automation for you!
[14:28] <paride> sil2100, no worries, no big deal, but maybe let's figure out a way to fix it at some point
[14:30] -queuebot:#ubuntu-release- Unapproved: accepted devscripts [source] (focal-backports) [2.22.1ubuntu1~bpo20.04.1]
[14:34] <jbicha> could we build libavif and its dependency libgav1 on i386? it's wanted by libgd2
[14:39] <LocutusOfBorg> vorlon, or somebody else. hddemux/s390x passed from neutral to fail basically because in release, b-d were not installable
[14:40] <LocutusOfBorg> can it be hinted please?
[14:40] <LocutusOfBorg>  knot-resolver | 5.4.4-1        | kinetic/universe          | source, amd64, arm64, armhf, ppc64el
[14:40] <LocutusOfBorg>  knot-resolver | 5.5.1-3        | kinetic-proposed/universe | source, amd64, arm64, armhf, ppc64el, s390x
[14:40] <LocutusOfBorg> this is the reason
[14:46] <sil2100> Eickmeyer: ok, no idea what's going on, per https://launchpadlibrarian.net/615984321/buildlog_ubuntu_jammy_amd64_ubuntustudio_BUILDING.txt.gz I see it's simply being installed but the ubuntustudio-meta package seems of the right version
[14:47] <Eickmeyer> sil2100: Same, and it's missing from the rdepends in germinate, so I don't know what's going on.
[14:48] <sil2100> reverse-depends still mentions that ubuntustudio-video recommends it, but it might be out-of-date
[14:48] <Eickmeyer> In the seed it's simply commented-out.
[14:48] <Eickmeyer> Yeah, that should be out-of-date as I just pulled germinate and it's not there.
[14:49] <arraybolt3[m]> Maybe it's a different DKMS module?
[14:49] <arraybolt3[m]> I wonder if the low latency kernel has anything to do with it.
[14:50] <arraybolt3[m]> (Probably not, actually, but if v4l2loopback isn't the problem, then searching for other modules might help.)
[14:50] <Eickmeyer> The other dkms modules showing are the nvidia-dkms, but they're showing as skipped, so it's not those.
[14:51] <sil2100> As said, it seems that v4l2loopback is pre-installed, but we don't know why
[14:51] <Eickmeyer> arraybolt3[m]: The lowlatency kernel is merely a kernel "flavor" of the generic kernel, generated at the same time, with *slightly* different build flags, so never read too much into it.  Maybe try just deleting the lines from the seeds entirely and see if that does the trick?
[15:13] <Eickmeyer> For now, I'm just waiting to see sil2100's "something stupid", so I'm being patient.
[15:20] <vorlon> LocutusOfBorg: why is knot-resolver being pulled from -proposed in the gnutls28 test but not in the baseline test?
[15:22] <vorlon> (apt bug? autopkgtest-cloud bug?)
[15:25] <arraybolt3[m]> Eickmeyer: According to this page https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntustudio.jammy/all ubuntustudio-video has the offending package as a Recommends. I'm not seeing that to be true using apt -s install, but that's apparently the idea Germinate is getting.
[15:30] <Eickmeyer> arraybolt3[m]: Yeah, we're thinking that's outdated. My manual build of germinate's rdepends tree is here: https://nextcloud.ericheickmeyer.com/index.php/s/9JgP7P35HCjZAPj
[15:30] <sil2100> Eickmeyer: ok, so I did a test in my chroot and I think it needs to be pulled in via the germinate runs somehow, because I tried installing the set of packages that livecd-rootfs installs minus the v4l2loopback* packages and it's not installed
[15:30] <sil2100> So nothing pulls it in via deps/recommends for sure
[15:31] <Eickmeyer> Right, I had the same result.
[15:31] <Eickmeyer> Minus the livecd-rootfs.
[15:33] <Eickmeyer> sil2100: Are we looking at something slow on the image building side where it pulled before it was ready? Like, perhaps, if we do a rebuild it will be fine?
[15:34] <LocutusOfBorg> vorlon, maybe apt when in doubt from non-existing package in release, and existing package in proposed, choose the latter?
[15:34] <arraybolt3[m]> I wonder if maybe phased updates are striking the Ubuntu build servers and so our last-minute change will now take a while before it actually works?
[15:34]  * arraybolt3[m] grasping at straws here
[15:35] <Eickmeyer> arraybolt3[m]: Nah, I think you're onto something, but I think we're all grasping at straws and banging our heads against the walls right now.
[15:36] <bdmurray> Looking in the directory https://people.canonical.com/~ubuntu-archive/germinate-output/ubuntustudio.jammy/ it was updated today
[15:38] <sil2100> eh
[15:38] <Eickmeyer> Yeah, that makes no sense.
[15:39] <sil2100> I think we know what's up, just have a sync with vorlon and bdmurray and uh, let me get back to you in a moment
[15:39] <Eickmeyer> Ok
[15:58] <sil2100> Eickmeyer, arraybolt3[m]: okay, so I think this is all caused by a 'known bug' that was never really fixed: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1921862 - certainly feels like what might be the case here
[15:59] <sil2100> The seeds are correct, but germinate runs without jammy-updates so it considers ubuntustudio-video from release which pulls in the v4l2loopback packages
[15:59] <Eickmeyer> Oh fun.
[15:59] <sil2100> Not 100% sure it's the case, but certainly seems like what's happening. And we're screwed...
[15:59] <sil2100> We only worked-around it last time
[16:00] <Eickmeyer> Yeah. That's a huge bummer. Obviously it won't work this time as we just simply don't have time to fix it now. But definitely something that *should* be fixed for .2.
[16:00] <Eickmeyer> I guess I'll release note it.
[16:07] <tsimonq2> There has to be a way to make it pull from updates...
[16:11] <arraybolt3[m]> I think at this point, we'd probably be better off writing a workaround guide for how to make Secure Boot work. Maybe even make a script that the user can download at install time and run, and it will make everything work (possibly by doing the mokutil dance if needed).
[16:12] <tsimonq2> Nah, into the rabbit hole I go, not my first rodeo with germinate ;) will throw patches shortly
[16:13] <Eickmeyer> tsimonq2: Good luck. sil2100, bdmurray: If tsimonq2 can get this resolved and it looks sane, do you think we could respin in time?
[16:14] <arraybolt3[m]> Simon Quigley: Good luck :) meanwhile, I'll work on the part I know (guides and scripts) so that we have a fallback hopefully.
[16:14] <tsimonq2> It's Tuesday. We release on Thursday. Imo we still have time
[16:15]  * Eickmeyer release noted it *just in case*
[16:18] <tsimonq2> oh lol I shouldn't even need a code modification
[16:23] <arraybolt3[m]> And we have successfully brought #lubuntu-devel culture into #ubuntu-release while fixing an #ubuntustudio-devel problem. Task failed successfully?
[16:24] <Eickmeyer> arraybolt3[m]: Yeah, let's be careful with that. In this context we're working with the release team on figuring out a fundamental problem.
[16:24] <arraybolt3[m]> 👍
[16:28] <laney> The problem is you get the union of the Task fields for all pockets, so you can't ever drop something from a seed post release really :/
[16:29] <laney> We should stop using tasks and only install the metapackages
[16:29] <laney> but that's clearly not something that can be done with <2 days to go
[16:30] <tsimonq2> laney: I think you're right. For now, do you know of a sane workaround used in the past?
[16:30] <laney> perhaps a hack in livecd-rootfs
[16:30] <tsimonq2> (You can always add a `dists:` line below the `dist:` line listing all three pockets you want to include (jammy, jammy-updates, and jammy-security) but that's probably only useful for *adding* packages.)
[16:31] <tsimonq2> Thanks laney, I will take a look.
[16:32] <laney> It's this bit: https://git.launchpad.net/livecd-rootfs/tree/live-build/auto/config#n132
[16:32] <laney> (aside: still one of my favourite lines of code ever, particularly the backslashes)
[16:32] <tsimonq2> (Very much appreciated, probably would have taken me an extra 10 minutes to find. :) )
[16:32] <laney> but you can see that it picks up packages with the Task you ask for in all pockets
[16:33] <laney> so you probably want to hack the result of calling that I guess
[16:33] <tsimonq2> That is just... amazing. I love it.
[16:34] <laney> perhaps the subtract_package_lists() function? not sure, do check
[16:34] <laney> also maybe get a sanity review from sil2100, I could be talking rubbish
[16:34] <laney> or proposing something which will never be accepted
[16:34] <tsimonq2> No worries, thank you again for at least pointing me in the right direction laney :)
[16:36] <tsimonq2> sil2100, vorlon, Eickmeyer: Hi, technical advice on the above workaround would be appreciated. I can save everyone else the work by filing the paperwork and writing the patch if we can at least agree on steps forward. Thanks.
[16:36] <tsimonq2> Also, let me know if the mailing list would be more appropriate for this topic.
[16:37] <arraybolt3[m]> If all else fails, I just discovered the glorious "sudo mokutil --disable-verification". Keeps Secure Boot on in BIOS, but essentially turns it off in Linux.
[16:40] <arraybolt3[m]> (Er, --disable-validation, I mean.)
[16:50] -queuebot:#ubuntu-release- Unapproved: net-snmp (focal-proposed/main) [5.8+dfsg-2ubuntu2.4 => 5.8+dfsg-2ubuntu2.5] (desktop-core, i386-whitelist, ubuntu-server)
[17:03] <arraybolt3[m]> I also have discovered a Calamares config hack that allows the install to work without disabling Secure Boot at all (it just uninstalls v4l2loopback immediately before installing shim-signed).
[17:04] <Eickmeyer> arraybolt3[m]: I'd rather not hack Calamares, and I'm sure tsimonq2 agrees.
[17:04] <tsimonq2> Yes, I agree.
[17:05] <arraybolt3[m]> Eickmeyer: Right, but it's only one config change, and if something happens where we can't get the root of the problem fixed, we can just say, "Secure Boot systems require a workaround - simply run this script on the live ISO prior to installation and everything will work." So we now have a fully functional fallback as our worst-case scenario.
[17:08] <Eickmeyer> arraybolt3[m]: Unfortunately, running a script prior to that won't work because calamares will still unpack whatever is in the .squashfs, which includes v4l2loopback, even if it's been uninstalled from the live system.
[17:09] <arraybolt3[m]> Eickmeyer: I just tried it and it worked. I hacked the contextual process file that installs shim-signed so that it basically says "apt remove -y v4l2loopback-dkms && sudo apt install shim-signed" (that's not the line verbatim but you get the idea).
[17:09] <arraybolt3[m]> And it installed and booted properly on a Secure Boot VM just fine.
[17:09] <Eickmeyer> Huh, interesting.
[17:09] <Eickmeyer> I could release note that.
[17:10] <arraybolt3[m]> My last step is going to be to make a patch script so that rather than having a user hack the config themselves, they can just do "sudo fixStudioSecureBoot.sh" and then run the installer or something like that.
[17:11] <Eickmeyer> arraybolt3[m]: Ok, take that discussion to #ubuntustudio-devel, lets keep this to the fix for livecd-rootfs that tsimonq2 is working on.
[17:11] <arraybolt3[m]> 👍
[17:17] <tsimonq2> Ah, I used my personal email. Please approve my post to ubuntu-release. :P
[17:18] -queuebot:#ubuntu-release- New binary: rust-event-listener [amd64] (kinetic-proposed/universe) [2.5.3-1] (no packageset)
[17:18] <bdmurray> Oh, that's one I don't have moderation powers for.
[17:19] <Eickmeyer> tsimonq2: To be fair (in the context of your email), it was v4l2loopback was removed from the seed and the meta sru is fix-released and it was released to updates, so it's no longer that I intend to, it's that it's done.
[17:22] <bdmurray> vorlon, sil2100: Can you look at my comment on the ubuntu-release-upgrader MP from schopin? https://code.launchpad.net/~schopin/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/427718
[17:23] <tsimonq2> Eickmeyer: I did clarify later on in that paragraph that it was past tense, I was re-reading it and thought it should have been more clear but sent it anyway. My apologies.
[17:24] <Eickmeyer> tsimonq2: No worries, just wanted to make sure you were on the same page as myself and sil2100.
[17:30] <tsimonq2> Eickmeyer: Idea. Blacklist it.
[17:31] <tsimonq2> Blacklist may override the inclusion. Consult with s_il2100 or laney on that though.
[17:31] <Eickmeyer> tsimonq2: Might be the only way and won't require a metapackage rebuild since it's already absent.
[17:31] <Eickmeyer> sil2100: thoughts? ^
[17:32] -queuebot:#ubuntu-release- New binary: rust-event-listener [ppc64el] (kinetic-proposed/universe) [2.5.3-1] (no packageset)
[17:33] -queuebot:#ubuntu-release- New binary: rust-event-listener [riscv64] (kinetic-proposed/universe) [2.5.3-1] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: zabbix [amd64] (kinetic-proposed/universe) [1:6.0.7+dfsg-2] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: zabbix [ppc64el] (kinetic-proposed/universe) [1:6.0.7+dfsg-2] (no packageset)
[17:36] -queuebot:#ubuntu-release- New binary: rust-event-listener [s390x] (kinetic-proposed/universe) [2.5.3-1] (no packageset)
[17:41] <laney> what blacklist?
[17:42] <tsimonq2> The seed blacklist
[17:43] <tsimonq2> Does germinate prioritize blacklisting packages over including them? That's probably a more precise question
[17:43] -queuebot:#ubuntu-release- New binary: rust-event-listener [arm64] (kinetic-proposed/universe) [2.5.3-1] (no packageset)
[17:43] -queuebot:#ubuntu-release- New binary: rust-event-listener [armhf] (kinetic-proposed/universe) [2.5.3-1] (no packageset)
[17:48] <vorlon> tsimonq2: agreed, a livecd-rootfs patch is most sensible here
[17:48] <laney> you can't germinate this away i'm afraid. livecd-rootfs is seeing the task fields in the release pocket and those can't be changed.
[17:48] <vorlon> tsimonq2: blacklisting only causes image build failures, it does not remove packages from images
[17:49] <laney> (blacklisting won't help anyway but in general no germinate based solution can)
[17:49] <laney> hey vorlon
[17:49]  * vorlon waves
[17:49] <tsimonq2> Ah, got it. Thank you to you both. Don't hesitate to let me know if you think of something else :)
[17:49] -queuebot:#ubuntu-release- New: accepted rust-event-listener [arm64] (kinetic-proposed) [2.5.3-1]
[17:49] -queuebot:#ubuntu-release- New: accepted rust-event-listener [armhf] (kinetic-proposed) [2.5.3-1]
[17:49] <vorlon> I hate having to patch livecd-rootfs but it is your escape hatch
[17:50] <vorlon> also it's an SRU that won't require respins of any other images
[17:50] -queuebot:#ubuntu-release- New: accepted rust-event-listener [amd64] (kinetic-proposed) [2.5.3-1]
[17:50] -queuebot:#ubuntu-release- New: accepted rust-event-listener [riscv64] (kinetic-proposed) [2.5.3-1]
[17:50] -queuebot:#ubuntu-release- New: accepted zabbix [amd64] (kinetic-proposed) [1:6.0.7+dfsg-2]
[17:50] -queuebot:#ubuntu-release- New binary: zabbix [s390x] (kinetic-proposed/universe) [1:6.0.7+dfsg-2] (no packageset)
[17:50] -queuebot:#ubuntu-release- New: accepted rust-event-listener [ppc64el] (kinetic-proposed) [2.5.3-1]
[17:50] -queuebot:#ubuntu-release- New: accepted zabbix [ppc64el] (kinetic-proposed) [1:6.0.7+dfsg-2]
[17:50] -queuebot:#ubuntu-release- New: accepted rust-event-listener [s390x] (kinetic-proposed) [2.5.3-1]
[17:51] <tsimonq2> vorlon: Did laney link the correct spot in the code or should I also investigate elsewhere? I'd imagine a conditional for Ubuntu Studio would be appropriate
[17:51] <laney> I just linked you to the function that's causing your problem
[17:51] <laney> you need to find the add_task call for ubuntustudio and fiddle around there somewhere
[17:51] <tsimonq2> gracias :)
[17:51]  * laney off, ttyl
[17:51] <tsimonq2> Have fun!
[17:52] <vorlon> bdmurray: commented
[17:54] <bdmurray> vorlon: ack, thanks that is what I was thinking too
[18:05] -queuebot:#ubuntu-release- New binary: zabbix [armhf] (kinetic-proposed/universe) [1:6.0.7+dfsg-2] (no packageset)
[19:00] -queuebot:#ubuntu-release- New: accepted zabbix [armhf] (kinetic-proposed) [1:6.0.7+dfsg-2]
[19:01] -queuebot:#ubuntu-release- New: accepted zabbix [s390x] (kinetic-proposed) [1:6.0.7+dfsg-2]
[20:08] <bdmurray> vorlon: I added words to the nvidia upgrade issue in a new MP https://code.launchpad.net/~ubuntu-core-dev/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/427736 and would appreciate a review
[20:11] <vorlon> bdmurray: ok looking
[20:11] <vorlon> fwiw I have code here for the pam upgrade issue, need to add tests and merge the translations from the pam package
[20:13] <vorlon> bdmurray: reviewed
[20:58] <vorlon> bdmurray: currently having a sad that dh_auto_test does nothing for u-r-u and Build-Deps do not encompass the test deps
[21:10] <vorlon> bdmurray: how do you update the .pot file in u-r-u?
[21:13] <vorlon> cd po && make, ok
[21:13] <bdmurray> It's part of pre-build.sh
[21:14] <vorlon> aha
[21:22] <vorlon> bdmurray: I have code, I have a test case, I have a strategy for importing translations from pam, but I'm going afk for the next 1.5h; will you be around to review after that?
[21:23] <bdmurray> vorlon: Yes, I also have an appointment this afternoon but will turn up after it.
[21:23] <vorlon> ok thanks
[21:33] <vorlon> bdmurray: I lied and finished up before leaving the keyboard, please review: https://code.launchpad.net/~ubuntu-core-dev/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/427743
[23:20] -queuebot:#ubuntu-release- New binary: dh-nss [amd64] (kinetic-proposed/none) [1] (no packageset)
[23:21] -queuebot:#ubuntu-release- New binary: junit5-system-exit [amd64] (kinetic-proposed/none) [1.1.2-1] (no packageset)
[23:43] <bdmurray> vorlon: reviewed
[23:43] <vorlon> thankee kindly
[23:44] <vorlon> bdmurray: fwiw the capitalization here is because that's how the string is in the Debian package.  Do you think I should upper-case the English only, or attempt to upper-case the translations?
[23:47] <sarnold> uhoh, is that the entire nation of turkey I hear? :)
[23:47] <bdmurray> vorlon: I saw that's how it is in the debian pacakge. Thinking about it more maybe it isn't worth the effort - not that many people will encounter it.
[23:48] <vorlon> sarnold: lol string not translated to Turkish
[23:48] <vorlon> bdmurray: ok. I could do it but I would have to do it manually and it would take me maybe a half hour?
[23:49] <bdmurray> I think its fine the way it is then
[23:50] <vorlon> bdmurray: not that long - turns out there are only 10 translations and the only trick is two of them use cyrillic. 10 minutes and I'll have it done
[23:52] -queuebot:#ubuntu-release- New binary: opencascade [amd64] (kinetic-proposed/universe) [7.6.3+dfsg1-2] (no packageset)
[23:53] <bdmurray> sil2100: There isn't a documented test case for bug 1955047. Do you want me to make a best guess or wait for schopin?
[23:54] <sil2100> bdmurray: I would say let's get this into -proposed and work on a test-case tomorrow
[23:54] <sil2100> (if the fix passed the review phase)
[23:55] <bdmurray> sil2100: Looks like it did pass review.


[08:50] <kikr> i'm looking at the wiki and I see that the Toshiba Satellite Pro L10 is supported, but I have a Toshiba Satellite R25. Would ubuntu work on it? what about the touchscreen?
[10:56] <GortiZ> hi to all
[10:59] <GortiZ> i've a problem with the suspension of a sony vgn-fe31h
[10:59] <GortiZ> some one could help me?
[10:59] <GortiZ> when I came back from suspend mode the laptop show a black screen with the mouse pointer and nothing else


[08:24] <lordievader> Good morning
[09:10] <rgvon> hello! unable to connect my YU Yuphoria YU5010A to Kubuntu 18.04. This error comes - The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/ does not exist.
[10:35] <BluesKaj> Hey folks
 (Photo, 1134x548) https://irc-attachments.kde.org/J8gVC0h1/file_15644.jpg hi
[14:18] <Aristide> Hello ! I have a small problem with Packagekit ... (I have same problem with Apper / Discover / pkcon command → Waiting in ...  ).  I don't know how explain that but .... Process is blocked on « Refreshing » (in KDE Notification). I kill packagekitd, notification disappear but comme back when I launch again pkcon/apper/discover (Kubuntu 19.04°
[14:19] <Aristide> Waiting in queue*
[14:19] <Aristide> I have packagekit 1.1.12-5
[17:05] <azx> how can i get plasma 5.13?
[17:05] <azx> i have 5.12.7 right now
[17:05] <azx> installed from sudo apt-get install kde-desktop
[17:05] <azx> someone told me i need to enable backports
[17:19] <Aristide> Hello
[17:19] <Aristide> I have a big problem with Discover :'(
[17:20] <Aristide> I have already explain, but I repeat :  (I have same problem with Apper / Discover / pkcon command → Waiting in queue...  ).  I don't know how explain that but .... Process is blocked on « Refreshing » (in KDE Notification). I kill packagekitd, notification disappear but comme back when I launch again pkcon/apper/discover (Kubuntu 19.04)
[17:20] <Aristide> And if I quit Discover/apper, notification tray continue to display « Getting repo list »
[17:20] <Aristide> (I don't have problems when I use apt-get update)
[17:21] <Aristide> And install, updates, upgrade, all functions are disabled in Discover
[17:22] <Aristide> https://i.imgur.com/rnUA6NR.png And if I click on stop : Do nothing : I must kill packagekitd process
[18:00] <friendlyGoat> anyone have experience with KDE Connect? it works and all but whenever i get a text the notifications FLOOD my whole screen and i have no idea how to get it to stop.
[18:00] <friendlyGoat> along with that my other situation is this and i'll take help from anybody https://askubuntu.com/questions/1147801/bios-contains-wgds-but-no-wrds
 Hey guys! Are there any plans to make a ppa for Plasma 5.16 and Kubuntu 18.04?
 @Linuxophil, Not at the moment.
 (Document) https://irc-attachments.kde.org/vskzU4nA/file_15651.mp4
 it would require an entire Qt stack backport, plus rebuilds of all the things in the Ubuntu archive that have a Qt ABI hard dependency, and then commit to maintianing that over time. It is not a simple thing to do or support.
 @acheronuk, Understandable.
 @acheronuk, But from a users standpoint, please know that it would change the world!
 That is why Neon exists
 @acheronuk, I look forward to Kubuntu 20.04 when I will be able to honestly recommend Plasma to non techy Windows converts.
 @acheronuk, I use Kubuntu 18.04 and am perfectly capable of working around the quirks of Plasma 5.12. But the older Generation of my family cannot be asked to do the same. So they are on Mint Cinnamon. Neon is not an adequate distro for the generation 60+ that is stuck on Win7 and will have to make a decision where to go before Jan 2020 when Win7 support ends.
 @acheronuk, ...and once they start with cinnamon, they will not change againg when  Kubuntu LTS with Plasma 5.16 comes around. At least that's my fear.
 What do you think, Rik?
 I think that I can't commit to maintaining a plasma 5.16 ppa for 18.04, no matter what
 @acheronuk, Understandable. But do you think that maybe someone else can?
 Maybe as an request to the developer community?
 To give a home to Win7 refugees?
 It might be a once in a lifetime opportunity!
 anytone can sign up to launchpad and create a ppa. the 2GB standard space would not be enough for this, so you would have to make a case for extra space
 @acheronuk, Hm... I wish I could help. Unfortunately I have no background in IT so cannot do it.
 Linuxophil - you could to what I do with my parents and keep them on the latest releases with backports and update them to the latest relase wehn I visit.
 I am just a fan of Kubuntu since I came to Linux 2 years ago to prepare my flight from Win10. 😉
 @DarinMiller, I thought about that, but you don't kow my father... 😉
 @DarinMiller, But actually I think in much broader terms. Not just my family. I think about the adoption of Plasma in general. And using opportunities.
 Does not like change or thinks everything that is wrong with the PC is your fault? Or both...
 :)
 @DarinMiller, A bit of both. But mostly does not like change. One change to Linux is all I can get him to do. But only because he has to change from Win7 to Win10 anyway.
[20:48] <valorie> @Linuxophil wouldn't it be easier to just update those aging people once every six months?
[20:48] <valorie> we generally get the latest or close to it in backports
[20:48]  * valorie is running 19.04 quite happily
[20:49] <valorie> I have plasma 5.15.4
[20:49] <valorie> and could be running the beta if I wanted....
[21:31] <mparillo> ... in both the stable 19.04 or the new shiny EE
[21:47] <valorie> right, not running EE yet
[21:48] <valorie> although I guess that's an option


[00:15] <doctormo> Heyo czajkowski, hows life?
[01:08] <cjohnston> doctormo: still around?
[01:22] <doctormo> cjohnston: yes
[01:25] <cjohnston> doctormo: are you going to continue development with https://code.launchpad.net/~doctormo/loco-directory/team-calendar  ?
[01:26] <doctormo> cjohnston: No, it was an experimental branch. Want me to delete it?
[01:26] <cjohnston> if you wouldnt mind
[01:26] <cjohnston> im going to try to clean up the list
[01:27] <doctormo> cjohnston: gone
[01:27] <cjohnston> ty sir
[01:29] <doctormo> np
[09:58] <duanedesign> morning all
[12:51] <nigelb> Today is phenomenal.  Weasley is trending on twitter.
[12:52] <nigelb> and quote of the day "rather be a Weasley than a Cullen" HAHA
[12:53] <duanedesign> hey there nigelb
[12:57] <duanedesign> nigelb: what is git2web?
[13:00] <nigelb> duanedesign: Hey there
[13:00] <nigelb> duanedesign: I'm writing it, a web interface to gitosis
[13:01] <nigelb> duanedesign: I got till listing everything so far.  Going to work on editing stuff and commiting it :D http://imagebin.ca/view/lIGHeHz.html
[13:14] <duanedesign> nigelb: cool. You using PHP, Python?
[13:15] <nigelb> duanedesign: python
[13:15] <nigelb> no way I can use php for this
[13:16] <nigelb> duanedesign: picked up Flask today, it was interesting
[13:19] <duanedesign> nigelb: ahh, cool
[13:19] <duanedesign> I really want to do more Python stuff for the web
[13:19] <nigelb> Same here
[13:19] <nigelb> I just get lost with LD, most of the time
[13:20] <nigelb> This turned up after a fun conversation in the cakephp channel
[13:20] <cjohnston> nigelb: i do to... maybe we can collaberate
[13:20] <cjohnston> lol
[13:20] <nigelb> cjohnston: sure, feel free to fork from here https://github.com/nigelbabu/git2web;)
[13:20] <nigelb> (err, ignore the smiley at the end)
[13:21] <cjohnston> no.. collaberate on LD
[13:22] <nigelb> cjohnston: ah, that
[13:24] <duanedesign> hello cjohnston
[13:25] <cjohnston> hey duanedesign
[13:25] <duanedesign> cjohnston: hope you had a good thanksgiving. I think i saw you were working.  I was going to ask if you get many 'holiday' related calls. like people burning themselves while deep frying a turkey
[13:27] <duanedesign> cjohnston: It was really good. Everyone was in a particularly good mood so it was nice
[13:27] <cjohnston> not this year
[13:28] <cjohnston> thats good
[13:28] <nigelb> duanedesign: cjohnston has too much Hope ;-P
[13:28] <cjohnston> the fire was someone left the toaster oven on when they went to work
[13:29] <duanedesign> ugh
[13:29] <cjohnston> other than that, just normal every day stuff
[13:29] <nigelb> heh
[13:29] <duanedesign> I am starting the redesign of screencasts.ubuntu.com
[13:30] <cjohnston> cool
[13:30] <nigelb> duanedesign: Nice :-)
[13:30] <duanedesign> first I have to upgrade to Drupal 6
[13:31] <nigelb> drupal! all the best
[13:31] <duanedesign> i want to solicit any ideas you all may have about improving the site
[13:31] <cjohnston> drupal ftl
[13:31] <nigelb> first suggestion => move to wordpress
[13:32] <duanedesign> I have little experience with Drupal. I thought about using Wordpress because that is what i am used too
[13:32] <nigelb> a lot more easier to maintain
[13:32] <cjohnston> WP ftw
[13:32] <nigelb> Drupal is, well, complicated
[13:32] <cjohnston> I'd like to, for learning reasons make a blog in django, but thats beyond my skill level
[13:32] <duanedesign> it just needs to be a platform that is compatible with the new theme
[13:32] <nigelb> cjohnston: you must be kidding me
[13:33] <cjohnston> what
[13:33] <nigelb> cjohnston: making a blog in django should be very easy, you just need to get the tables right and everything should be ready out of the box without much trouble
[13:33] <cjohnston> ya.. beyond my skill level
[13:33]  * nigelb kicks cjohnston
[13:33] <nigelb> you work on LD! It is within your skill level!
[13:34] <cjohnston> dude.. most of the fixes I come up with is pure dumb luck... and hanging out in #django
[13:34] <nigelb> lol
[13:34] <cjohnston> I was gettin help in there last night to fix a bug
[13:34] <cjohnston> then mhall kindly said I did it wrong and did it his way
[13:34] <cjohnston> lol
[13:34] <nigelb> haha
[13:35] <duanedesign> I want to have screencasts in multiple languages. The Nicaraguan Team is making some Spanish screencasts
[13:35] <cjohnston> and by kindly I mean he made a merge proposal against my merge propsal removing what I put in
[13:35] <cjohnston> lol
[13:36] <duanedesign> what is LD?
[13:36] <nigelb> haha
[13:36] <cjohnston> loco directory
[13:36] <cjohnston> duanedesign: you should work on it :-P
[13:36] <duanedesign> d'oh, of course
[13:36] <duanedesign> <.<  >.>
[13:38] <duanedesign> have you all seen the tuxtorial site?
[13:39] <duanedesign> http://tuxtorial.com
[13:41] <nigelb> duanedesign: wow
[13:43] <duanedesign> nigelb: neat idea. Have not had a chance to try it


[02:48] <grantbow> q: random friend gave me an HP Pavilion dv6 aka qg291ua laptop that fails to boot windows 7. My usb 12.04 grub boot medium boots to a black screen with a blinking cursor. I think I need a magic kernel parameter to make it boot. any suggestions?
[02:55] <akk> Do you know if it's actually booting from the USB (and then failing), or not even seeing the grub boot at all?
[02:55] <akk> I'm wondering if it might be a bios boot setting issue rather than a problem booting grub.
[02:55] <grantbow> it's booting grub2 and when I loopback mount the iso it seems to load the kernel and sit there
[02:55] <akk> So much for that idea.
[02:56] <grantbow> http://rww.name/articles/grub2iso/
[02:56] <darthrobot> Title: [Booting ISOs from GRUB 2]
[02:56] <grantbow> it works on many machines but not all
[02:56] <nhaines> grantbow: my laptop is a dv6 and boots with no modifications.
[02:56] <grantbow> I was caught without my other machine and other medium to try booting from
[02:56] <akk> Ah, this isn't a normal single live usb, it's a grub-with-isos thing?
[02:57] <grantbow> nhaines: interesting
[02:57] <grantbow> akk: yes
[02:57] <akk> I have one of those too, but I've sometimes seen it fail on machines where a normal live usb will work.
[02:57] <nhaines> I would try a DVD.  It's the computer or it's the install media.
[02:57] <akk> I don't understand why (I confess I don't totally grok how the grub-to-iso transition happens).
[02:58] <akk> (I don't think anyone else groks it either -- at least, if anyone does they're not writing public explanations :)
[02:58] <grantbow> it doesn't like the 12.10 dvd
[03:01] <grantbow> I hate the bios dance. booting a machine shouldn't be so hard.
[03:02] <akk> We'll all come to love bios after we have to "up"grade to secureboot UEFI machines. :(
[03:02] <nhaines> UEFI without secureboot is awfully nice though.
[03:03] <grantbow> aha! It doesn't auto-detect cd and dvd well. Manually telling it to go to disc is working!
[03:03] <nhaines> Last client machine I built had a pretty mouse-driven GUI.  I had to keep shoeing her 6yo away from it.
[03:03] <akk> The older EFI on macs was a major pain with ubuntu.
[03:03] <grantbow> or, tries to work, darn it, same black screen and blinking cursor
[03:04] <grantbow> nothing on ctrl-alt-F1 vt
[03:12] <grantbow> I think this is a qvc model
[03:29] <grantbow> after long timeouts it finally booted. Not sure if there is a hardware problem involved or not yet.
[03:29] <grantbow> at least I can copy files off now! hurray!
[03:29] <akk> It's a start! Yay.
[03:29] <akk> Wonder what the timeout was doing/waiting for?
[03:31] <grantbow> udevd [*]: timeout: killing '/sbin/blkid -o udev -p /dev/sda?' [*]
[03:31] <grantbow> with numbers for the *'s and ?
[03:34] <grantbow> the trouble will now be talking my friend through booting from CD with the right timing on the esc key and choosing the CD.
[03:35] <grantbow> I can rest easier knowing at least it can be done
[03:36] <grantbow> toggling wifi made it scan to connect, that's a good sign
[03:36] <akk> Yes, that's often the hardest part getting laptops to work.
[03:37] <akk> Hope it's not broadcom.
[03:40] <grantbow> bcm4313 but it worked out of the box
[03:41] <grantbow> though it is throwing qos stuff to the console vt
[04:18] <nhaines> PLOT TWIST: installing the proprietary driver kills wireless support.
[09:12] <nhaines> Just finished work on my new Ubuntu business cards.  If I get good feedback I'll print them in time for SCALE.  :)


[12:45] <BluesKaj> Howdy folks
[16:16] <kfunk_> heya guys, I'm on Kubuntu 20.04 and I'm wondering if you're planning to upgrade the kdepim stack to sth more recent? right now it's stuck at 19.04. asking b/c I'm experiencing some issue wrt .ics event entries rendering in kmail.
[16:16] <kfunk_> (which is fixed in later kmail versions)
[16:19] <RikMills> kfunk_: yeah, I intend to do it under a feature freeze exeption as soon as I can


[03:27] <Omnifrog> http://i.imgur.com/G9H6M97.jpg
[03:29] <wrst> howdy Omnifrog
[03:30] <Omnifrog> hi wrst
[03:30] <wrst> all going well?
[03:33] <Omnifrog> it is indeed!
[03:34] <Omnifrog> life is great
[03:43] <wrst> great to hear
[03:43] <wrst> :)
[06:11] <Unit193> wrst: So an update, I'm not just the one to get snakes out of the basement, I also get racoons out of the house. 0_o
[11:07] <cyberanger> ouch
[11:08] <Unit193> Yeah, twice in one day too, same one.
[14:06] <tenc> Good morning TN; wrst, twayneprice, Unit193.
[14:06] <wrst> howdy tenc
[14:09] <tenc> I can't decide if syslinux is a pain or if I'm just a noob with boot loaders.
[14:09] <tenc> Probably the latter.
[14:20] <wrst> tenc: curious why syslinux?
[14:22] <twayneprice> morning tenc
[14:22] <tenc> Following the ArchWiki for creating a bootable USB that doesn't just dd the ISO so I can put other things on it and the guide seems to prefer syslinux.
[14:24] <wrst> ahh yes tenc, also arch on virtual box I have always had to use syslinux
[14:25] <wrst> morning twayneprice
[14:28] <twayneprice> morning wrst
[14:29] <wrst> twayneprice: I looked at att's map last night, big white no service spot over brotherton :)
[14:29] <twayneprice> I can confirm that is true.  :)
[14:30] <wrst> ha ha it really does look pretty good most other places, but they don't do a strength map
[14:31] <twayneprice> It is not very good in Lebanon either.  When anyone here at work gets a call they have to run outside to answer.  :)  I drop calls 4 or 5 times on my way home.
[14:31] <wrst> ok that's pretty sorry
[14:31] <wrst> I keep finding things cheaper but with all of them seem to be making a sacrifice of some sort
[14:31] <wrst> and right now my sacrifices are minimal vs verizon
[14:32] <wrst> tenc: sorry got distracted from a conversation from yesterday, I've used some tool to do what you are doing
[14:33] <wrst> maybe from pendrive linux or something similar
[14:33] <twayneprice> I just looked at the map.  It actually show moderate at my house and at church.  The church is right at the intersection of Buck Mountain Rd and Mountain Top Ln.  I live on Decatur about an inch away.  :)
[14:34] <wrst> so moderate means zero now evidently
[14:35] <twayneprice> in moderation.  :)
[14:36] <wrst> so my hope is that my wife gets over her iphone addiction
[14:50] <twayneprice> Good luck with that.  :)
[14:56] <wrst> yes exactly not likely to happen :)


[15:59] <len-dt> smartboyhw, You might notice that there are some "ubuntustudio" that are not included in an install.
[16:00] <len-dt> Normally we don't recommend adding all of them to another install, just the needed work flows.
[16:02] <len-dt> Just so you know Ubuntu or Xubuntu plus all the ubuntustudio metas does not = Ubuntustudio the way a fresh install would do.
[16:06] <smartboyhw> len-dt, well then..... we never recommended installing it on a Mac anyway did we? Thx for the info though.
[16:07] <len-dt> smartboyhw, Even then, I would start with the desktop of choice and add workflows.
[16:08] <len-dt> I don't know that there is a lowlatency kernel for the mac.
[16:10] <persia> Which mac?  Recent macs running Ubuntu use the same x86_64 lowlatency as any other recent intel chip.  Most of the same patches probably also apply for powerpc, but there may not be enough users to be worth the maintenance.  OS X kernels are just one flavour, which is reported to be sufficiently low latency when running Logic.
[16:11] <len-dt> persia, Ya, I was just reviewing a converstion on #ubuntustudio
[16:11] <persia> Ah, no worries then :)
[16:12] <len-dt> even with a pc mapping all our metas over something else mostly doesn't do the same as an install
[16:12] <persia> I think we ought consider that a bug, personally.  It used to work that way.
[16:14] <len-dt> I think zequence is working on that actually as part of the controls package.
[16:15] <len-dt> There are some things though that with xfce panels and such where once the user has logged in, the way they are is set and changing the system default won't change them.
[16:16] <len-dt> Eye candy stuff, backgrounds and themes mostly
[16:16] <zequence> I think the mac version is not very different from the regular version. Mac has some HW oddities, but CPU is the same
[16:16] <persia> That probably needs lots of low-level work: I know that for the GNOME stuff, there was a lot of work done to cause the user session to be generated from a mix of system and user data.
[16:17] <persia> Having just gotten a new mac, I tell you that it's not any different, aside from the hardware selection.
[16:17] <zequence> I've only tried using mac with linux. Puredyne ran pretty well on a macbook
[16:17] <persia> The reason for the different downloadable images is because Apple EFI and other folks UEFI are rather incredibly different.
[16:18] <persia> Someone might get around to writing code that works well by default on both and lets you boot a CD/DVD/USB, but perhaps not very soon.
[16:18] <len-dt> persia, nice to know. So it is the grub part of things then so a kernel should work?
[16:18] <persia> Yeah, kernels are the same.  grub is even the same.
[16:19] <persia> For both mac and non-mac, one can run either grub-pc (BIOS) or grub-efi (EFI/UEFI): the issues all surround the grub-install script.
[16:19] <zequence> I think the main practical difference in adding all our metas, compared to a fresh studio install, is that the user will not end up in audio group after adding metas, which should not happen anyway. And, many user settings are already done, especially if you use another UI, so the experience using the desktop is not going to be identical
[16:20] <persia> Needing to be in the audio group is a bug.
[16:21] <persia> Certainly the desktop experience would be different, but we should be able to provide standards-compliant stuff to give a broadly similar experience.
[16:21] <len-dt> it keeps the server people happy...
[16:21] <persia> Mind you, environments like unity that fail to comply with XDG menu spec are probably harder to support.
[16:21] <persia> Hrm?  How?
[16:22] <len-dt> There are some people who do not want the user to have rt access by default so if not audio group something else to do the same thing.
[16:23] <persia> But aren't we supposed to use rtkit for that?
[16:23] <zequence> Not according to Paul Davis
[16:24] <zequence> I'm happy with whatever works well, and is the easiest to implement
[16:24] <zequence> Fromt he user point of view, I mean
[16:24] <zequence> On Debian, the user is a member of audio group by default
[16:24] <zequence> Probably not a good thing, but that is how it is
[16:25] <zequence> pulseaudio is also a member of audio group
[16:25] <persia> Used to be that way in Ubuntu as well.  Most of the things that required that stopped.
[16:25] <zequence> I think different people are using the same group for different things
[16:25] <len-dt> I think slackware is set up that way too
[16:25] <persia> The last remaining item is limits.conf, which rtkit *should* solve.
[16:25]  * len-dt remebers it used to be
[16:25] <persia> but perhaps rtkit isn'T rich enough, or something.  I haven't been following the debate.
[16:26] <zequence> jackd now installs /etc/security/limits.d/audio.conf, which contains the two important lines
[16:26] <zequence> So, on Debian, that is enough to get realtime privilege. However, there's another problem too
[16:26] <zequence> firewire devices cannot be accessed without being in audio group
[16:26] <zequence> udev rules
[16:27] <persia> That's easy to fix.
[16:27] <persia> I think pitti is part of udev upstream now, and I know he was one of the folk interested in dropping the audio group requirement.
[16:28] <zequence> /lib/udev/rules.d/60-ffado.rules
[16:29] <len-dt> it has to work with all the variants not just debian derivatives. As jack is developed for linux and the author is not likely to be happy doing it more than one way.
[16:30] <persia> Heh, of course :)  No reason we can't ask for changes upstream.
[16:31] <zequence> I don't know why one way is better than the other. I don't care. From our point of view, it's a matter of getting Debian/Ubuntu system infrastructure working to our benefit, no matter which solution, as long as it works
[16:32] <len-dt> I agree, the admin should be able to chose if the user has rt or not. so long as that happens, what does it matter?
[16:33] <zequence> It's too much for me personally to find out, and work on, so I'm not touching it, at least for now. But, it would be nice if a user could just install jackd, and get realtime privilege
[16:33] <zequence> Without further setting up
[16:34] <len-dt> yup
[16:34] <persia> Hrm.  The ffado udev rules specifying the audio group don't seem to have been uploaded with a bug reference.  I wonder why they are that way.
[16:35] <len-dt> That doesn't work without jack anyway.
[16:36] <zequence> jack works without realtime privilege, but the firewire driver won't work without the user being a member of audio group
[16:36] <persia> zequence: Because of the udev rules, or also because of something else?
[16:39] <zequence> persia: I guess the udev rules are what makes it possible for users to access the firewire devices, through the group membership.
[16:40] <zequence> So, if one is member of audio group, that is enough to run jackd with firewire. To get realtime privilege, you add the two lines to /etc/security/*
[16:40] <persia> Ah, OK.  I'm guessing leftovers from the every-firewire-device-is-a-hard-drive-and-must-be-restricted-to-root-access philosophy then.
[16:40] <persia> Now that we have juju, we can probably relax that (but I should go verify the state of juju in our kernels before I say that)
[16:42] <persia> Ah, found it: https://blueprints.launchpad.net/ubuntu/+spec/multimedia-platform-n-pro-audio-secured
[16:43] <zequence> We should probably talk with David about that then
[16:44] <persia> Yep :)
[16:45] <persia> From the last note at the end, I get the impression that adding the memlock support is feasible (although I don't think it's done, based on my search results).
[16:45] <persia> If so, that drops the limits.d/audio.conf requirement.
[16:47] <persia> Indeed, the audio group requirement for the firewire udev rules is about protecting raw1394 access to the underlying device (which could be used to compromise filesystems)
[16:51] <len-dt> It looks to me like not much has moved. FW development in general seems to be quite slow. Reading about FW to ALSA it seems the idea is dead right now.
[16:53] <persia> OK, 60-ffado.rules can be changed to not use the audio group: it ought use the ACL mechanism: see 70-acl.rules.
[16:53] <persia> Mind you, this would only let the currently-logged-in user access the firewire devices.  Does this seem like it might be an issue?
[16:54] <len-dt> We set up pulse to be user centric so it should be ok.
[16:54] <persia> Cool.
[16:55] <zequence> For low latency audio, I don't see much point in multiuser access to the same device
[16:55] <len-dt> It should be session centric. There are some problems for people who run audio from terminal... IE sight impared.
[16:56] <len-dt> Setting up a session than the same user can use from more than one VT at the saem time is "interesting"
[16:56] <persia> heh. indeed :)
[16:57] <len-dt> The answer that google shows ends up with a pile og dbus tasks running when really only two are needed (maybe one)
[16:58] <zequence> One audio server at a time though
[16:58] <len-dt> I did manage to get it to work with just the two though.
[16:58] <persia> If someone else wants to investigate ffado's need for the audio group before I get to it: apparently Fedora has it working without: presumably one could install in a VM and check the file layout.
[16:58] <len-dt> Yup one audio server. but a lot of the jack CLI utils use dbus.
[17:01] <persia> Right: finished confirming: we are entirely using the new firewire stack, so the permissions concerns with the old one are no longer relevant.
[17:03] <zequence> persia: Are you talking about the change from the old stack to the new stack in the kernel, that happened around 2010?
[17:03] <zequence> I think Ubuntu moved to the new stack with 10.10
[17:03] <persia> Um, it's not done yet.
[17:03] <persia> it's still possible to generate raw1394 drivers (or was last I knew)
[17:04] <zequence> I'm not that good with terms, but I think raw1394 is the old one, and firewire_something, is the new one
[17:04] <persia> And the reports I see are that the v4l2 driver is still missing, as well as fixes to libavformat and pwlib (pwlib will likely never happen)
[17:05] <persia> Right.  *1394 are the old interfaces, and firewire-* are the new ones.
[17:05] <persia> (well, sbp2 was also one of the old interfaces, but that's just a detail)
[17:05] <zequence> persia: Yea, so from what I understand, we've been using the new stack since 10.10. The udev rules appeared at that time too
[17:05] <persia> That said, in Ubuntu, it appears our kernels don't build the old interfaces.
[17:06] <persia> (which means that we just handle video cameras badly)
[17:06] <zequence> The udev rules are what makes the current setup work, while for the old one, Ubuntu Studio used to grant access to all firewire devices through video
[17:06] <zequence> through the video group
[17:07] <zequence> There were no udev rules preinstalled in the past, as they are now, on all Debian systems (I think)
[17:07] <persia> Well, a mix of the "audio" and "video" groups, but yeah.
[17:07] <persia> No, it was more hardcoded, and what wasn't often used hal.
[17:09] <zequence> So, I don't think Fedora is doing it differently. In fact, i think they are doing it the same way, but one would need to confirm that
[17:10] <persia> According to the upstream firewire wiki, Fedora is using ACLs for some firewire device types, but I think that's just using 70-acl.rules, from what I see.
[17:10] <persia> But I'd need to test to find out what is different, and whether the GROUP= entry could be dropped from 60-ffado.rules with that before being confident.
[17:12] <zequence> Ah, this line: SUBSYSTEM=="firewire", ENV{ID_FFADO}=="1", TAG+="udev-acl"
[17:12] <zequence> And there are a few others, concerning firewire
[17:14] <persia> Right.  I believe that is supposed to interact with session management and grant the currently active user access to the device.
[17:15] <persia> What I don't know is whether we have polkit configured in such a way that it just works.
[17:19] <persia> Indeed, we do *not* have the necessary polkit rules to automagically do the right thing.
[17:19] <persia> So, two bugs:
[17:20] <persia> 1) rtkit needs to grow memlock support
[17:20] <persia> 2) we need polkit rules to grant access to ffado devices
[17:20] <persia> Unless someone knows another reason we need an "audio" group?
[17:23] <zequence> And rtprio?
[17:23] <zequence> Or, does rtkit handle that differently?
[17:26] <persia> Seems it's configued in rtkit: http://git.0pointer.de/?p=rtkit.git;a=blob;f=README
[18:03] <zequence> ever felt like if you didn't have so many problems to solve, you'd have more time to solve problems?
[18:12] <astraljava> zequence: I can't hear you over the problems I'm trying to solve.
[18:16] <zequence> astraljava: I'm sorry. Busy strangling my mouse. Get back to you when I have audio
[21:25] <zequence> It's great when you google for help and find a very helpful wiki page you forgot you wrote only a week ago
[21:45] <Len-nb> :)
[22:12] <zequence> Interesting, though 4 years old talk about linux kernel development. Some facts about speed of changes, and who contributes https://www.youtube.com/watch?feature=player_detailpage&v=L2SED6sewRw#t=51s
[22:15] <zequence> I wasn't aware of the fact that amateurs, at least then, where the biggest group of contributors, if you didn't count companies as one single group, but separate per company
[22:16] <zequence> And, also back then, Canonical were not contributing much at all
[22:20] <zequence> I think probably it might be worthwhile looking at maintaining a linux-rt
[22:21] <zequence> Or.. I don't know. I need to think more about that
[22:32] <len-dt> zequence, it may be more worthwhile figuring out why new kernels have poor low latency performance.
[22:32] <len-dt> Maybe there are new additions/settings that could be changed/bypassed in the low latency/rt kernel
[22:36] <zequence> len-dt: I was looking at the kernel versioning, and realized the odd versions are not maintained for any long periods of time. They reach EOL pretty quickly. Yet, Ubuntu always uses whatever kernel is the latest
[22:36] <zequence> the rt patch is added to all the even numbers
[22:36] <zequence> Those which are maintained for a longer time
[22:37] <zequence> Somehow, I would have thought it would make sense for Ubuntu to only use the even numbers, and that would also have made it practical when maintaining a -rt kernel
[22:37] <zequence> Of course, one could always keep one, which was not the same version as the stock kernel
[22:37] <zequence> So, if Ubuntu would go with say, 3.5, the -rt kernel could be 2.4
[22:37] <zequence> 3.4*
[22:38] <zequence> I haven't yet tried patching the Ubuntu kernel with the rt patch. I actually only built an rt for the first time today
[22:39] <zequence> As the -rt patch is meant for the vanilla kernel, there could be problems
[22:39] <len-dt> zequence, I think there is good reason for using only even numbered kernels
[22:40] <len-dt> Would it be possible to set US to look at only even numbers in case generic was installed too?
[22:40] <len-dt> What versions does -server use?
[22:42]  * len-dt thinks he would prefer even kernels in a server for sure
[22:42] <zequence> len-dt: There's no server flavor anymore
[22:43] <len-dt> I thought ubuntu was trying to have a server market... something that pays.
[22:43] <zequence> ..wait
[22:44] <zequence> I must have misunderstood something
[22:44] <zequence> It's the same versioning anyway
[22:45] <len-dt> Even in LTS?
[22:45] <zequence> No server flavor since 12.04
[22:45] <len-dt> Or are the LTS ones always even?
[22:45] <zequence> https://wiki.ubuntu.com/Kernel/Dev/Flavours
[22:48] <zequence> lucid had a preempt flavor. Didn't know that. Only mad64
[22:48] <zequence> amd64*
[22:49] <len-dt> what has happened with the LMMS thing? (swept under the carpet?)
[22:50] <zequence> len-dt: Perhaps just that no one has taken a decision for adding it
[22:50] <len-dt> But no talk either
[22:50] <len-dt> I could add it to the seeds and see what happens...
[22:50] <zequence> I think we covered just about everything on the mail list
[22:51] <zequence> I'm for adding it
[22:51] <len-dt> If I add it to the seeds now it should show tomorrow either in or broken build.
[22:51]  * len-dt is willing to take the blame
[22:52] <len-dt> I'll comment the commit as "trial only"
[22:52] <zequence> Nah, just add it
[22:53] <len-dt> will do.
[22:53] <zequence> I think it fills a workflow that other applications don't really do
[22:53] <zequence> It's not like there are 5 other apps like LMMS out there
[22:54] <zequence> And to those who say it's buggy. Well, so are most of the other apps as well
[22:55] <Len-nb> gmorgan tries to do much the same.
[22:55] <zequence> If we all had magic wands, maybe we could solve those problems pretty quick
[22:55] <Len-nb> or got paid... just for this
[22:56] <zequence> gmorgan was new to me, but that looks more like a tracker than a sequencer
[22:57] <zequence> Ah, musical patterns
[22:57]  * Len-nb is going to eat
[22:58] <zequence> Never seen an interface like that one before
[23:23] <zequence> the mail accounts request seems to have been accepted
[23:47] <zequence> I must be doing something wrong. I can't get an rt kernel built with decent performance
[23:48] <zequence> There's a new config for the rt patch though, called CONFIG_PREEMPT_LAZY
[23:51] <zequence> But, disabling it doesn't help much
[23:52] <zequence> I'm getting worse performance than from -lowlatency


[13:20] <snapy> hi there, I am starting to learn about PPA in Launchpad
[13:20] <snapy> I have recently "activated" my ppa repository and it seems that I only have a jaunty branch
[13:21] <snapy> Is there a way to have multiple branches (hardy, intrepid, etc)?
[13:22] <noodles> Hi snapy, yes you can publish to multiple distribution series... for example:
[13:22] <noodles> http://launchpad.net/~cprov/+archive
[13:23] <snapy> interesting...
[13:24] <snapy> how did you manage to do it?
[13:24] <noodles> That's not my archive... but
[13:26]  * noodles is just looking a relevant help page...
[13:32] <snapy> (I am also investigating on help pages...)
[13:32] <noodles> snapy, great! I found the following which mentions that when you copy packages from an archive into your own PPA, that you select the distroseries for the packages:
[13:32] <noodles> https://help.launchpad.net/Packaging/PPA#Copying%20packages
[13:33] <snapy> uhmmm
[13:33] <noodles> just trying to find related docs for when you upload your own source package...
[13:35] <snapy> meanwhile I am going to finish retouching my package (a personal version of network-manager)
[13:38] <noodles> snapy, cool. From what I can see, when you setup your pbuild environment you specify the the build environment distribution... there's tips here for setting up for multiple ubuntu series:
[13:38] <noodles> https://wiki.ubuntu.com/PbuilderHowto#Change%20base.tgz%20Location
[13:51] <asabil> hi all
[13:51] <asabil> this import seems to fail: http://launchpadlibrarian.net/20302313/gst-plugins-base-trunk-log.txt
[13:51] <asabil> could someone take a look at it please ?
[14:01] <snapy> hello again, it seems I have now a problem signing the source package with debuild
[14:02] <snapy> I type debuild -S -sa
[14:03] <snapy> and I get the error:  gpg: skipped "Miguel Telleria<EMAIL_ADDRESS>secret key not available
[14:03] <noodles> Hi again snapy, first check if this helps:
[14:03] <noodles> https://help.launchpad.net/Packaging/UploadErrors
[14:04] <snapy> I suspect it is a problem with my gpg configuration, but I am going to check
[14:05] <snapy> oh I see, thanks noodles it seems I need to specify the key explicitly
[14:12] <snapy> I think I have uploaded it !! (the source package of course)
[14:12] <noodles> whohoo!
[14:13] <snapy> but I don't see the package yet
[14:13] <snapy> https://launchpad.net/~miguel-mtelleria/+archive
[14:14] <noodles> Yeah, I had to wait a while before mine showed up... (maybe 10 or 15mins, I can't remember...)
[14:14] <oojah> snapy: You'll get emails with success/failure in a bit.
[14:14] <snapy> ok, I wait then :)
[14:16] <snapy> uuhmm it was rejected :(
[14:16] <snapy> Could not find person 'miguel-telleria'
[14:17] <snapy> anyway I am getting close
[14:17] <snapy> uhhm I see
[14:17] <snapy> it is miguel-mtelleria
[14:18] <snapy> changing .dput.cf and retrying
[14:21] <oojah> snapy: You can change your username if you've made a typo.
[14:21] <snapy> yes I have done it and the package has been accepted :)!!
[14:22] <oojah> snapy: I mean if you want the username to be miguel-telleria on launchpad then you can change it.
[14:22] <oojah> (and well done :)
[14:22] <snapy> oh yeah I see now
[14:22] <snapy> and also I see only the source package
[14:22] <snapy> http://ppa.launchpad.net/miguel-mtelleria/ubuntu/pool/main/n/network-manager/
[14:23] <oojah> It's still building.
[14:23] <oojah> Click on any of the architectures to see the status.
[14:24] <snapy> to change the username I should go to my launchpad profile I guess (I won't do it yet until the package has been built)
[14:24] <oojah> snapy: Correct.
[14:25] <snapy> what do you mean by "clicking in the architectures"?
[14:25] <snapy> I just don't see the link
[14:26] <snapy> ok I see
[14:27] <snapy> things like http://ppa.launchpad.net/miguel-mtelleria/ubuntu/dists/intrepid/universe/binary-i386/ I guess
[14:27] <noodles> From here:
[14:27] <noodles> https://edge.launchpad.net/~miguel-mtelleria/+archive
[14:28] <noodles> You'll see there a list of architectures currently being (or waiting to be) built...
[14:28] <snapy> cool :)
[14:33] <snapy> well it seems the build is over but I still don't see the .deb packages in the ftp repository
[14:34] <snapy> and I haven't received any emails neither
[14:34] <snapy> (just getting impatient)
[14:34] <snapy> :)
[14:35] <snapy> well, I have to leave to go to eat (Spanish time)
[14:35] <snapy> I'll get back in the evening
[14:36] <snapy> thanks noodles and oojah for your help.  I am sure I will make it very soon
[14:36] <snapy> (if not already :) )
[14:36] <noodles> No problem :). Yeah, I think you're there, just give it a few mins...
[16:00] <johannes> I experimented a bit with releases on launchpad. I have a milestone with a few ssigned bugs and blueprints. Now I'm making a release. How can I link from the milestone to the release to say "all of these milestone targets are implemented there"? Or how should that work in the end?
[17:31] <darius12> hi, I 've got a strange problem trying to build vim from my ppa, same package builds fine locally
[17:32] <darius12> configure: error: C compiler cannot create executables
[17:32] <darius12> See `config.log' for more details.
[17:32] <darius12> the logs are in https://launchpad.net/~pktoss/+archive/+build/808279
[17:54] <bigjools> darius12: check your build dependencies
[18:17] <Rinchen> nand, ping
[18:35]  * mnft is away: Gone away for now.
[21:04] <der|kunstler> how do I remove a project from my +junk ?
[21:04] <der|kunstler> and how do I edit a branch's information ? :)
[21:05] <mwhudson> der|kunstler: little icons next to the heading
[21:05] <der|kunstler> mwhudson, uhm, the ones that look like some soft of sign ?
[21:05] <der|kunstler> mwhudson, I mean, yellow sign
[21:06] <mwhudson> yeah, it's meant to be a minus sign and a pencil
[21:06] <der|kunstler> got it, thanks
[21:06] <der|kunstler> :/ how come I didn't see it, heh!
[21:08] <mwhudson> der|kunstler: you're not the only one, we need to make this more discoverable somehow
[21:08] <der|kunstler> mwhudson, yeah, the first place I look for is on the right side
[21:09] <der|kunstler> mwhudson, when deleting a branch, here's what I've got: (Error ID: OOPS-1073H2400)
[21:09] <mwhudson> der|kunstler: are you on edge?
[21:10] <der|kunstler> mwhudson, pardon my ignorance, what is edge ?
[21:10] <mwhudson> der|kunstler: ah, ok
[21:10] <thumper> mwhudson: that'll be a no
[21:10] <der|kunstler> heh :P
[21:10] <thumper> der|kunstler: known issue, and fixed in code (and edge)
[21:10] <der|kunstler> I guess that's a no
[21:10] <mwhudson> der|kunstler: edge stands for "bleeding edge"
[21:10] <der|kunstler> aaah, got it
[21:10] <thumper> der|kunstler: if you add a ".edge" between "code" and ".launchpad.net"
[21:10] <mwhudson> it's a server that gets its code updated dairly
[21:10] <der|kunstler> it hasn't been merged into the actual launchpad code
[21:10] <thumper> der|kunstler: for you branch
[21:11] <thumper> der|kunstler: you should be able to delete your branch
[21:11] <der|kunstler> thumper, got it
[21:11] <der|kunstler> thumper, so edge.code.blah right ?
[21:11] <thumper> der|kunstler: code.edge.launchpad.net
[21:11] <der|kunstler> thumper, muchas gracias amigo :D
[21:11] <der|kunstler> mwhudson, thanks to you too
[21:11] <thumper> der|kunstler: you'll need to log in again as it is a different server
[21:11] <mwhudson> p
[21:11] <der|kunstler> thumper, understood
[21:11] <mwhudson> np
[21:12] <der|kunstler> when does the main launchpad server gets its code updated, how regular ?
[21:12] <mwhudson> roughly monthly
[21:13] <der|kunstler> ok
[21:13] <mwhudson> next rollout will be in a week and a bit
[21:13] <der|kunstler> great
[21:14] <der|kunstler> the project delete worked like a charm on that one. I assume the edge server is faster right ?
[21:18] <mwhudson> ah, he left
[21:19] <thumper> that he did
[21:19] <thumper> I didn't feel like answering no one


[15:00] <barry> #startmeeting
[15:00] <MootBot> Meeting started at 09:01. The chair is barry.
[15:01] <intellectronica> me
[15:01] <barry> hello everybody and welcome to this week's meeting.  who's here today
[15:01] <rockstar> me
[15:01] <sinzui> me
[15:01] <bac> me
[15:01] <gmb> me
[15:01] <mars> me
[15:01] <bigjools> me
[15:01] <flacoste> me
[15:01] <salgado> me
[15:02] <allenap> me
[15:02] <abentley> me
[15:03] <cprov> me
[15:03] <EdwinGrubbs> me
[15:04] <barry> [TOPIC] agenda
[15:04] <MootBot> New Topic:  agenda
[15:04] <intellectronica> barry: Bjorn mentioned that he'll be away this afternoon, maybe he's not back yet
[15:04] <barry> == Agenda ==
[15:04] <barry>  * Roll call
[15:04] <barry>  * Cross-referencing monkey patches in code (intellectronica, bigjools)
[15:04] <barry>  * If there's time, the old boring script
[15:04] <barry>    * Next meeting
[15:04] <barry>    * Action items
[15:04] <barry>    * Queue status
[15:04] <barry>    * Mentoring update
[15:05] <barry> [TOPIC]  * Cross-referencing monkey patches in code (intellectronica, bigjools)
[15:05] <MootBot> New Topic:   * Cross-referencing monkey patches in code (intellectronica, bigjools)
[15:05] <barry> intellectronica, bigjools the floor is yours
[15:05] <intellectronica> ok, i'll go
[15:05]  * bigjools looks at intellectronica since he added the topic :)
[15:06] <intellectronica> sometimes we need to monkey patch code
[15:06] <intellectronica> this became quite frequent since we started exporting stuff to the API
[15:07] <flacoste> ?
[15:07] <bigjools> circular imports
[15:07] <intellectronica> since in order to avoid circular imports we often need to amend classes after they're first declared
[15:07] <barry> intellectronica: can we define "monkey patch" :)
[15:07] <flacoste> that,s not monkey patching!
[15:07] <flacoste> that's working around circular imports!
[15:07] <intellectronica> flacoste: ok, since you oobviosly understand what i'm talking about, how about you propose a better definition?
[15:07] <sinzui> barry is the master of monkeypatching
[15:08] <sinzui> see launchpad/mailman/monkeypaches
[15:08] <flacoste> intellectronica: well, you are talking about the working around of circular imports, right?
[15:08] <intellectronica> flacoste:
[15:08] <intellectronica> flacoste: yup
[15:08]  * barry is a patched monkey
[15:09] <flacoste> intellectronica: ok, so what is the issue you wanted to raise about this?
[15:09] <intellectronica> see l/c/l/interfaces/bugtask.py:634 for a representative example of the problem i'm referring to
[15:09] <intellectronica> so, while working through a problem bigjools and i realised that it's often quite difficult, when you look at the class definition, to know where it's being amended
[15:10] <intellectronica> and wanted to suggest that we make it a requirement to cross reference the places using comments
[15:10] <intellectronica> so that next to the general definition, you'll have to add a comment saying where it's being patched
[15:11] <barry> intellectronica: that seems like good practice to me
[15:11] <flacoste> so where we have schema=Interface, # ITeamMembership
[15:11] <flacoste> we would have
[15:11] <flacoste> schema=Interface, # ITeamMembership, in teammembership.py?
[15:12] <bigjools> see interfaces/archive.py for an example of how bac recommended I do this yesterday
[15:12] <intellectronica> flacoste: yes, maybe even something more specific, as long as it's maintainable
[15:12] <abentley> I think that this fixup requirement is a framework bug.  We should allow schema='ITeamMembership'
[15:12] <mars> flacoste, wild speculation, can Zope 3.4 deferred imports take care of this?
[15:12] <barry> abentley: you beat me to it.  +1
[15:12] <intellectronica> abentley: that's a _really_ nice idea
[15:12] <flacoste> yes, now that we have zope 3.4, we can look into deferredimport
[15:13] <barry> eliminating the patch up is definitely the right way to go
[15:13] <flacoste> gary reports that it's not necessarily nice
[15:13] <flacoste> so if that turns out to be true
[15:13] <abentley> I'm happy with requiring an xreference until that's fixed.
[15:13] <flacoste> we should look into supporting schema='canonical.launchpad.interfaces.ITeamMembership'
[15:14] <barry> agreed.  so who can i give an action item to for that?
[15:14] <flacoste> foundations
[15:14] <flacoste> we can look into deferredimport
[15:14] <flacoste> and fix all of them
[15:14] <flacoste> otherwise, we'll file a bug
[15:15] <barry> [ACTION] flacoste & foundations to look into techniques for eliminating back-patching of schema types to avoid circular imports
[15:15] <MootBot> ACTION received:  flacoste & foundations to look into techniques for eliminating back-patching of schema types to avoid circular imports
[15:15] <flacoste> actually, iirc, there is already a bug reported about using deferredimport
[15:15] <barry> anything else on this topic?
[15:16] <abentley> flacoste: We also have the option of using bzrlib's lazy_import.
[15:16] <flacoste> interesting!
[15:16] <flacoste> i diN,t know about that one
[15:17]  * barry wishes python had a standard way of doing it
[15:17] <abentley> barry: What about the one in the email module :-) ?
[15:17] <barry> abentley: yech :)
[15:17]  * rockstar notes that barry can make a standard way of doing it with his commit access.
[15:17]  * bigjools coughs and mentions that even C has a way of doing this
[15:18]  * barry emits an evil chortle
[15:18] <barry> that's all the fun stuff on the agenda, so it's boring script time
[15:18] <barry> [TOPIC] action items
[15:18] <MootBot> New Topic:  action items
[15:18] <barry>  * barry will move the preimp discussion to the ml
[15:19] <barry> fail.  but i did pull my half written email out of my drafts folder so i'll do that today <wink>
[15:19] <barry>  * flacoste to take discussion of rest v. moin to ml
[15:19] <flacoste> that will happen once gary finishes his example
[15:19] <flacoste> should be soon
[15:19] <barry> flacoste: excellent, thanks
[15:20] <barry>  * rockstar to take discussion of adding launchpadlib tests for exposed api to ml
[15:21] <rockstar> Oh noes!  This has been an my TODO list for a week!  I will start the discussion now.
[15:21] <barry> rockstar: thanks!
[15:21] <barry>  * abentley to investigate current code coverage tools for lp tests
[15:21] <abentley> barry: I haven't done this yet.
[15:22] <barry> abentley: np, we'll just carry it over
[15:22] <gmb> abentley: ISTR allenap did something related to this a way back.
[15:22] <gmb> Unless I remember incorrectly.
[15:22] <gmb> abentley: So it might be worth tapping his newly-returned cranium for information.
[15:22] <sinzui> abentley: gmb: allenap did!
[15:23] <gmb> Thank you, Launchpad team historian.
[15:23] <barry> :)
[15:24] <barry> [TOPIC]    * Queue status
[15:24] <MootBot> New Topic:     * Queue status
[15:24] <barry> any comments on the queue?  either the review queue, pqm, etc.
[15:25] <gmb> Apart from the occasional overnight buildup
[15:25] <gmb> (AMEU time)
[15:25] <gmb> The queue is very manageable at the moment.
[15:26] <gmb> (At least ona Thursday)
[15:26] <intellectronica> we've got more reviewers, that really helps
[15:26] <barry> btw, i'm hoping that by epic we can try merge proposals again.  the redesigned u/i really looks great
[15:26] <barry> intellectronica: indeed.
[15:27] <rockstar> barry, that should land soon
[15:27] <barry> rockstar, abentley: correct me if i'm wrong, but diffs are still a ways away
[15:27]  * rockstar looks at abentley
[15:27] <abentley> barry: Hard to say.
[15:28] <rockstar> Database patches...  :)
[15:28] <barry> ah :)
[15:28] <abentley> I'll be implementing diffs this week or next, I think.
[15:28] <barry> abentley: will that include diffstats?
[15:29] <abentley> barry: Not initially.
[15:30]  * bigjools has to duck out now
[15:30] <barry> cool, thanks
[15:30] <barry> [TOPIC]    * Mentoring update
[15:30] <MootBot> New Topic:     * Mentoring update
[15:30] <barry> any feedback here?
[15:31] <gmb> barry: mars is doing an exceelent job.
[15:31] <bac> rockstar continues doing a great job
[15:31] <gmb> Not all that many reviews to do, sadly.
[15:31]  * rockstar feels warm inside
[15:31]  * gmb hands rockstar an antacid
[15:31]  * barry feels bad that he's missed abentley's last few sessions
[15:32] <barry> abentley: we'll get back on track after epic
[15:32] <abentley> barry: We managed alright.
[15:32] <barry> abentley: yep, appreciated!
[15:32] <abentley> The big problem was getting attention from Rinchen and kiko the first time, when I didn't know what to do.
[15:33] <barry> yep, they're busy guys :)
[15:33] <barry> anyway, that's all i have today.  do you have any topics not on the agenda?
[15:33] <rockstar> Negative
[15:33] <abentley> barry: No.
[15:34] <barry> okie dokie!  have a great week everybody and thanks for coming
[15:34] <barry> #endmeeting
[15:34] <MootBot> Meeting finished at 09:34.
[15:34] <gmb> Thanks barry.