[07:01] -queuebot:#ubuntu-release- Unapproved: tty-clock (lunar-proposed/universe) [2.3-1build1 => 2.3-3] (no packageset) (sync)
[07:02] -queuebot:#ubuntu-release- Unapproved: accepted tty-clock [sync] (lunar-proposed) [2.3-3]
[07:12] -queuebot:#ubuntu-release- Unapproved: qemu (focal-proposed/main) [1:4.2-3ubuntu6.25 => 1:4.2-3ubuntu6.26] (ubuntu-server, virt)
[07:12] -queuebot:#ubuntu-release- Unapproved: qemu (jammy-proposed/main) [1:6.2+dfsg-2ubuntu6.7 => 1:6.2+dfsg-2ubuntu6.8] (ubuntu-server, virt)
[07:12] -queuebot:#ubuntu-release- Unapproved: qemu (kinetic-proposed/main) [1:7.0+dfsg-7ubuntu2.2 => 1:7.0+dfsg-7ubuntu2.3] (ubuntu-server, virt)
[08:01] -queuebot:#ubuntu-release- Unapproved: guestfs-tools (lunar-proposed/universe) [1.48.3-3ubuntu1 => 1.48.3-4ubuntu1] (no packageset)
[08:02] <LocutusOfBorg> fixing CVE-2022-2211 ^^
[08:02] -ubottu:#ubuntu-release- A vulnerability was found in libguestfs. This issue occurs while calculating the greatest possible number of matching keys in the get_keys() function. This flaw leads to a denial of service, either by mistake or malicious actor. <https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2211>
[08:02] -queuebot:#ubuntu-release- Unapproved: accepted guestfs-tools [source] (lunar-proposed) [1.48.3-4ubuntu1]
[09:07] -queuebot:#ubuntu-release- Unapproved: thunderbird (lunar-proposed/main) [1:102.10.0+build1-0ubuntu1 => 1:102.10.0+build2-0ubuntu1] (mozilla, ubuntu-desktop)
[10:28] -queuebot:#ubuntu-release- Unapproved: xlnx-firmware (lunar-proposed/multiverse) [2022.1-4-0ubuntu1 => 2022.1-4-0ubuntu2] (no packageset)
[10:29] -queuebot:#ubuntu-release- Unapproved: accepted xlnx-firmware [source] (lunar-proposed) [2022.1-4-0ubuntu2]
[11:04] -queuebot:#ubuntu-release- Unapproved: accepted shotwell [source] (lunar-proposed) [0.30.18-0ubuntu1]
[11:05] -queuebot:#ubuntu-release- Unapproved: accepted ubuntucinnamon-environment [source] (lunar-proposed) [23.04.4]
[11:05] -queuebot:#ubuntu-release- Unapproved: accepted tar [sync] (lunar-proposed) [1.34+dfsg-1.2]
[11:06] -queuebot:#ubuntu-release- Unapproved: accepted containerd [source] (lunar-proposed) [1.6.12-0ubuntu3]
[11:38] -queuebot:#ubuntu-release- Unapproved: accepted geocode-glib [sync] (lunar-proposed) [3.26.3-6]
[11:40] -queuebot:#ubuntu-release- Unapproved: accepted cheese [sync] (lunar-proposed) [44.0-1]
[11:41] -queuebot:#ubuntu-release- New: rejected nvme-stas [source] (lunar-proposed) [2.2.1-0ubuntu1]
[11:41] -queuebot:#ubuntu-release- New: accepted yosys-plugin-ghdl [arm64] (lunar-proposed) [0.0~git20211127.09a32cd-1]
[11:41] -queuebot:#ubuntu-release- New: accepted yosys-plugin-ghdl [amd64] (lunar-proposed) [0.0~git20211127.09a32cd-1]
[11:41] -queuebot:#ubuntu-release- New: accepted yosys-plugin-ghdl [ppc64el] (lunar-proposed) [0.0~git20211127.09a32cd-1]
[11:54] -queuebot:#ubuntu-release- Unapproved: openstack-trove (lunar-proposed/universe) [2:19.0.0-0ubuntu2 => 2:19.0.0-0ubuntu3] (openstack)
[12:46] <xypron> Hi release team, would you be willing to grant a feature freeze exception for the correction in LP #2006130?
[12:46] -ubottu:#ubuntu-release- Launchpad bug 2006130 in licheerv-rtl8723ds-dkms (Ubuntu) "FFE: Add build support for Linux >= 6.1" [Undecided, New] https://launchpad.net/bugs/2006130
[12:48] <seb128> xypron, the change doesn't seem a feature but rather a bugfix, unsure that requires an exception?
[12:57] <LocutusOfBorg> Hello Release Team, I would like to have an opinion about syncing llvm-toolchain-16 from experimental again. 16 is not the current default, doesn't build on riscv64 (and maybe after the sync it might build), its a new minor release, and I personally fixed Debian RC bug: #1033933, prevending spirv from being packaged, as well as fixing the testsuite of the package
[12:57] -ubottu:#ubuntu-release- Bug 1033933 in OpenStack Compute (nova) "product_version is missing from software_version on xcp-xapi" [Medium, Fix Released] https://launchpad.net/bugs/1033933
[12:58] <LocutusOfBorg> in my opinion, the current llvm-16 in lunar is not "good for release and usage" since the cmake script is basically not working unless you hack it or install full omp libraries (not available everywhere)
[12:58] <LocutusOfBorg> after the sync, it might be really better for "release"
[12:59] <LocutusOfBorg> (I'm speaking of Debian version 1:16.0.1-1~exp2)
[12:59] <LocutusOfBorg> Debian bug: #1033933
[12:59] -ubottu:#ubuntu-release- Debian bug 1033933 in llvm-16-dev "llvm-16-dev: cmake findpackage(LLVM) fails due to missing /usr/lib/llvm-16/lib/libomptarget.so.16" [Serious, Open] https://bugs.debian.org/1033933
[12:59] <LocutusOfBorg> yay, this time ubottu made it right :D
[13:03] -queuebot:#ubuntu-release- Unapproved: fonts-ubuntu (lunar-proposed/main) [0.863-0ubuntu2 => 0.863-0ubuntu3] (desktop-core, ubuntu-server)
[13:37] -queuebot:#ubuntu-release- Unapproved: licheerv-rtl8723ds-dkms (lunar-proposed/universe) [1.0-0ubuntu3 => 1.0-0ubuntu4] (no packageset)
[13:38] -queuebot:#ubuntu-release- Unapproved: accepted licheerv-rtl8723ds-dkms [source] (lunar-proposed) [1.0-0ubuntu4]
[13:38] -queuebot:#ubuntu-release- Unapproved: json-smart (lunar-proposed/universe) [2.2-2 => 2.2-2ubuntu1] (no packageset)
[13:39] -queuebot:#ubuntu-release- Unapproved: accepted json-smart [source] (lunar-proposed) [2.2-2ubuntu1]
[13:44] -queuebot:#ubuntu-release- Unapproved: cmake (lunar-proposed/main) [3.25.1-1 => 3.25.1-1ubuntu1] (core, i386-whitelist)
[13:54] -queuebot:#ubuntu-release- Unapproved: screen-resolution-extra (lunar-proposed/main) [0.18.2 => 0.18.3] (ubuntu-desktop)
[14:00] <LocutusOfBorg> at the end, I uploaded the current llvm-toolchain-16 with just fixes of cmake and testsuite, so we don't risk with the new upstream release (even if bugfix only)
[14:02] -queuebot:#ubuntu-release- Unapproved: llvm-toolchain-16 (lunar-proposed/universe) [1:16.0.0-1~exp5ubuntu1 => 1:16.0.0-1~exp5ubuntu2] (i386-whitelist)
[14:03] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-16 [source] (lunar-proposed) [1:16.0.0-1~exp5ubuntu2]
[14:07] -queuebot:#ubuntu-release- Unapproved: accepted cmake [source] (lunar-proposed) [3.25.1-1ubuntu1]
[14:08] -queuebot:#ubuntu-release- Unapproved: accepted openstack-trove [source] (lunar-proposed) [2:19.0.0-0ubuntu3]
[14:13] -queuebot:#ubuntu-release- Unapproved: accepted fonts-ubuntu [source] (lunar-proposed) [0.863-0ubuntu3]
[14:21] <LocutusOfBorg> interesting behaviour queuebot! You say "accepted" llvm-toolchain-16, but on lunar/+queue page its shown in "done" page, not in the "accepted" one :)
[14:48] -queuebot:#ubuntu-release- Unapproved: sl-modem (lunar-proposed/restricted) [2.9.11~20110321-16ubuntu3 => 2.9.11~20110321-16ubuntu4] (i386-whitelist, kernel-dkms)
[14:56] <vorlon> cpaelzer: so a rerun of identify-removals-from-rebuilds is now reporting candidates that it wasn't reporting yesterday, by almost double... hmm.  (example: chibi-scheme)
[14:57] <vorlon> cpaelzer: and chibi-scheme shouldn't be a candidate, the only build failure is an arch for which it's not built in lunar...  dunno what's failed there when this check worked previously
[15:09] <cpaelzer> I didn't change any code yet
[15:09] <cpaelzer> since it checks various conditions, like versions in Debian/Ubuntu and such maybe any of that changed and makes it a candidate now
[15:10] <cpaelzer> I could download the ftbfs report, reduce it to just chibi-scheme and thne via cmdline we can bump up the loglevel to understand more in detail why it is shown now
[15:20] <ginggs> vorlon cpaelzer: i changed the reference series from kinetic to lunar in the last ftbfs report run
[15:21] <ginggs> wanted to see if it handled removals differently
[15:22] <ginggs> next run (underway) will use kinetic as the reference again
[15:23] <ginggs> if you are interested in the differences, see the copies named *-ref-lunar and *-ref-kinetic
[15:33] <vorlon> ginggs: ah and it looks like this is a recent change, and chibi-scheme/armhf is now unhelpfully labelled as a regression on https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230324-lunar-lunar.html
[15:37] <vorlon> ginggs: I can't see that there was ever a successful chibi-scheme build on armhf
[15:37] <vorlon> so the report is buggy, not the tool
[15:58] <vorlon> wow, how did mac-fdisk get into the i386-whitelist
[16:03] -queuebot:#ubuntu-release- Unapproved: wordpress (lunar-proposed/universe) [6.1.1+dfsg1-1ubuntu1 => 6.2+dfsg1-1ubuntu1] (no packageset)
[16:03] -queuebot:#ubuntu-release- Unapproved: accepted wordpress [source] (lunar-proposed) [6.2+dfsg1-1ubuntu1]
[16:21] <vorlon> ginggs: knitpy is another one that has newly shown up in the report; I'm not sure why that changed, there is a -3 upload that fixed the build failure but the report is only showing the -2
[16:23] <ginggs> vorlon: knitpy is in the superseded section
[16:23] <vorlon> ginggs: yes - I'm trying to suss out why it newly shows up in the report
[16:24] <vorlon> it does correctly show up in the superseded section, but *something* has changed to make paelzer's script pick it up now
[16:28] -queuebot:#ubuntu-release- Packageset: Removed duktape from i386-whitelist in lunar
[16:28] -queuebot:#ubuntu-release- Packageset: Removed google-perftools from i386-whitelist in lunar
[16:28] -queuebot:#ubuntu-release- Packageset: Removed mac-fdisk from i386-whitelist in lunar
[16:28] -queuebot:#ubuntu-release- Packageset: Added asmtools to i386-whitelist in lunar
[16:28] -queuebot:#ubuntu-release- Packageset: Added testng7 to i386-whitelist in lunar
[16:48] <enr0n> ubuntu-sru / bdmurray: Can you please look into releasing the systemd SRUs during your shift today?
[17:09] <jbicha> vorlon: we'll need duktape on i386 for 23.10 policykit-1. Do you prefer that we just enable it when we need it?
[17:19] -queuebot:#ubuntu-release- New source: fonts-irannastaliq (jammy-proposed/primary) [1.5-0ubuntu1]
[17:20] <vorlon> jbicha: yes
[17:20] <vorlon> jbicha: it should not be enabled in a series where it's not used (and cleaning up manually-enabled i386 builds is part of the checklist for release)
[17:50] -queuebot:#ubuntu-release- New: rejected fonts-irannastaliq [source] (jammy-proposed) [1.5-0ubuntu1]
[17:52] -queuebot:#ubuntu-release- New source: fonts-irannastaliq (lunar-proposed/primary) [1.5-0ubuntu1]
[17:54] -queuebot:#ubuntu-release- New: accepted fonts-irannastaliq [source] (lunar-proposed) [1.5-0ubuntu1]
[17:56] -queuebot:#ubuntu-release- New binary: fonts-irannastaliq [amd64] (lunar-proposed/none) [1.5-0ubuntu1] (no packageset)
[18:04] -queuebot:#ubuntu-release- New: accepted fonts-irannastaliq [amd64] (lunar-proposed) [1.5-0ubuntu1]
[18:48] <seb128> could the thunderbird update in the queue be considered? it's another candidate for the new stable with a one line timezone related fix
[19:01] <bdmurray> I'll look at thunderbird
[19:02] <seb128> bdmurray, thanks!
[19:06] -queuebot:#ubuntu-release- Unapproved: accepted thunderbird [source] (lunar-proposed) [1:102.10.0+build2-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- Unapproved: accepted sl-modem [source] (lunar-proposed) [2.9.11~20110321-16ubuntu4]
[19:58] -queuebot:#ubuntu-release- Unapproved: icingaweb2-module-x509 (lunar-proposed/universe) [20190125-3 => 1:1.1.2-1] (no packageset) (sync)
[19:58] <vorlon> uh ok weird, colord-sensor-argyll is built on i386, depends on argyll, but argyll/i386 was reported as a candidate for removal :/
[19:59] -queuebot:#ubuntu-release- Unapproved: accepted icingaweb2-module-x509 [sync] (lunar-proposed) [1:1.1.2-1]
[20:00] <vorlon> copying that back over, and I'll follow up to see what's going on
[20:14] <seb128> vorlon, I was going to ask what you did, those copies show weirdly on the changes list :-/
[20:17] <vorlon> yeah can't help that, sorry
[20:25] <vorlon> ok the issue is that colord is pulled into the whitelist as a dependency, but the colord-sensor-argyll binary package is not.  Known issue with dep traversal for i386 stuff, I'll hand-enable it
[20:30] <seb128> vorlon, could you explain the issue and how you resolve it so I can document it if needed on https://wiki.ubuntu.com/ArchiveAdministration ?
[20:38] <vorlon> seb128: just under 'i386 whitelist updates'?
[20:38] <vorlon> apw, xnox: what's this garbage https://ubuntu-archive-team.ubuntu.com/nbs.html
[20:41] <vorlon> how are these packages NBS, but the per-ABI binaries that depend on them are not
[20:41] <apw> vorlon, without using too much brain actually reading it, i am going to say i think it is an LRM respin
[20:41] <apw> vorlon, so the metas have moved on to a +1
[20:41] <vorlon> but how did 6.2.0-20 migrate without the matching lrm
[20:42] <apw> that should be impossible as far as i recall.
[20:42] <vorlon> answer: it didn't but somehow the packages from lrm are not being reported as NBS
[20:42] <vorlon> https://ubuntu-archive-team.ubuntu.com/proposed-migration/lunar_outdate.txt catches that they're out of date
[20:42] <vorlon> ugly
[20:43] <vorlon> k I'll hack those out by hand-
[20:45] <apw> those are -18 arn't they on lunar_outdate.txt ?
[20:46] <vorlon> yeah there's multiple layers of oddness
[20:47] <apw> oh but (unusually) there would have been a -19.N and then a -19.N+1 for LRM which both were replaced in place.
[20:47] <vorlon> hmmmMMmmmM at least some of these packages listed here are ones I've already removed (34 minutes ago https://launchpad.net/ubuntu/lunar/amd64/linux-modules-nvidia-390-6.2.0-18-generic).  Guess I need to let things settle out first
[20:47] <apw> when -20 migrated.
[20:48] <apw> (so perhaps this is things becoming unmasked when you removed the newer one.)
[20:52] <vorlon> apw: aren't these cloud kernels all arriving post-kernel freeze?
[20:53] <vorlon> jbicha: are you fixing gst-plugins-base1.0/amd64?
[20:53] <vorlon> and gst-plugins-good1.0/arm64....
[20:53] <apw> vorlon, hrm, i think they have been in the signing pipeline, so approved before the deadline; and coming into sync with master as a result.
[20:54] <vorlon> mmk
[20:54] <apw> (better than the alternative most likely, but not ideal.)
[20:55] <vorlon> the kernel freeze is intended to be the deadline by which the packages are in the archive, so that we have adequate time for the bits downstream of it
[20:55] <vorlon> we'll manage, but
[20:56] <apw> yeah, and i am sure i approved them early last week to entirely avoid this... so will investigate where they have been.
[20:57] -queuebot:#ubuntu-release- Unapproved: libcupsfilters (lunar-proposed/main) [2.0~b4-0ubuntu6 => 2.0~rc1-0ubuntu1] (no packageset)
[20:58] -queuebot:#ubuntu-release- Packageset: Added argyll to i386-whitelist in lunar
[20:58] -queuebot:#ubuntu-release- Unapproved: postfix (jammy-proposed/main) [3.6.4-1ubuntu1 => 3.6.4-1ubuntu1.1] (core)
[20:58] -queuebot:#ubuntu-release- Unapproved: postfix (kinetic-proposed/main) [3.6.4-1ubuntu2 => 3.6.4-1ubuntu2.1] (core)
[20:59] <tillkamppeter> @vorlon, hi
[21:00] <tillkamppeter> @vorlon, could you accept libcupsfilters 2.0rc1 for Lunar? Contains lots of bug fixes, most for correct printing, but also a crasher.
[21:04] <vorlon> tillkamppeter: looking
[21:05] <tillkamppeter> @vorlon, it is the release candidate, I went through the recent bug reports, fixed them, did a lot of testing and fixed a lot of bugs ...
[21:08] <vorlon> tillkamppeter: I don't think the debian/NEWS file is appropriate; this is not information that should be shown to users with priority, which is the purpose of debian/NEWS.  Not a blocker though
[21:09] <vorlon> tillkamppeter: cfippfindBasedURIConverter was previously exposed in the ABI of this library and exported in the headers, now you've marked it 'missing'.  What checks have you done to ensure nothing uses this symbol?
[21:09] <tillkamppeter> @vorlon, what is the place then where I could put such info? Only to know for later releases or similar situations ...
[21:10] <vorlon> tillkamppeter: I wouldn't worry about putting it anywhere other than the changelog, personally
[21:11] <tillkamppeter> @vorlon, I have checked all the packages with which I use this library, CPDB, pappl-retrofit, c2esp, libppd, and they all do not use it. the library is new and its predecessor did not have the function, so it should not be used by someone else ..
[21:12] <vorlon> yes, and this package only exists in the devel series, so the fact that the ABI wasn't yet stable doesn't bother me - I only care that we're not breaking any of our own packages
[21:13] <vorlon> I also did a quick check and don't find any references to the dropped symbol
[21:13] <vorlon> ok
[21:13] <vorlon> accepting
[21:13] -queuebot:#ubuntu-release- Unapproved: accepted libcupsfilters [source] (lunar-proposed) [2.0~rc1-0ubuntu1]
[21:17] <tillkamppeter> @vorlon, thanks. Generally, as upstream developer, I consider the API at least slightly changeable before one does a release candidate, so with the RC as the latest ...  This API is even not completely documented yet ...
[21:19] <vorlon> tillkamppeter: that's a fine position for an upstream to take, but when the pre-RC has already been uploaded in Ubuntu's devel series and has reverse-dependencies and the ABI changes 2 weeks before release, there's some due diligence required
[21:30] -queuebot:#ubuntu-release- Unapproved: rejected screen-resolution-extra [source] (lunar-proposed) [0.18.3]
[21:33] <bdmurray> coreycb: I'm confused by the test results in https://bugs.launchpad.net/cloud-archive/+bug/2011709/comments/6 Were you doing verification for kinetic-proposed or for zed-proposed?
[21:33] -ubottu:#ubuntu-release- Launchpad bug 2011709 in neutron (Ubuntu Kinetic) "[SRU] zed stable releases" [High, Fix Committed]
[21:50] <vorlon> bdmurray: propozed
[21:53] -queuebot:#ubuntu-release- Unapproved: gnome-control-center (lunar-proposed/main) [1:44.0-1ubuntu4 => 1:44.0-1ubuntu5] (ubuntu-desktop)
[21:53]  * bdmurray groans
[21:53] <vorlon> jamespage: python-inflect doesn't look like it's getting resolved before lunar release, so I'm re-demoting python-autocommand
[22:14] <vorlon> kanashiro_: would you happen to want to take a look at ruby-omniauth-oauth2-generic?  It's a candidate for removal from lunar because it FTBFS and has been removed from Debian testing; but I noticed there was a newer version in unstable that fixed the build failure and is only blocked from Debian testing due to release freeze
[22:14] <vorlon> kanashiro_: however, it has failing autopkgtests in both Debian and Ubuntu - in Debian they are not considered a regression because the package isn't in testing, in Ubuntu they are a regression vs the ftbfs version in the release pocket
[22:15] <vorlon> I might just ignore the test failures, since there's a TOCTOU race here (if I had removed the package from lunar and ignored the package in unstable, then in MM we would've gotten the new version, and then it clearly would not have been a test regression)
[22:17] <jbicha> vorlon: -good built on retry (the "flvmux" build test is unreliable). I filed bug 2015928 & bug 2015931 . I don't think I can fix them but I reported them upstream
[22:17] -ubottu:#ubuntu-release- Bug 2015928 in gst-plugins-base1.0 (Ubuntu) "gst-plugins-base1.0 fails to build on Ubuntu 23.04 with glib 2.76.1" [High, Triaged] https://launchpad.net/bugs/2015928
[22:17] -ubottu:#ubuntu-release- Bug 2015931 in gstreamer-editing-services1.0 (Ubuntu) "gstreamer-editing-services1.0 build test failure on Ubuntu 23.04" [High, New] https://launchpad.net/bugs/2015931
[22:18] <jbicha> the gstreamer build test issues also affect the versions already in lunar
[22:38] -queuebot:#ubuntu-release- Unapproved: mozjs102 (lunar-proposed/main) [102.9.0-1 => 102.10.0-1] (i386-whitelist) (sync)
[22:41] -queuebot:#ubuntu-release- Unapproved: ibus (lunar-proposed/main) [1.5.28-3 => 1.5.28-4] (i386-whitelist, input-methods, ubuntu-desktop) (sync)
[22:47] <tillkamppeter> Hi, any core-dev around here? I would like to have the upload of libppd 2.0~rc1-0ubuntu1 sponsored: bug 2015938
[22:48] -ubottu:#ubuntu-release- Bug 2015938 in libppd (Ubuntu) "Sponsor upload for libppd 2.0~rc1-0ubuntu1" [High, New] https://launchpad.net/bugs/2015938
[23:00] <tsimonq2> I'll take care of you Till :) give me less than an hour
[23:31] <tillkamppeter> Thanks in advance, @tsimonq2
[23:57] -queuebot:#ubuntu-release- Unapproved: cups-filters (lunar-proposed/main) [2.0~b3-0ubuntu2 => 2.0~rc1-0ubuntu1] (desktop-core, ubuntu-server)
[23:58] <tillkamppeter> @vorlon, could you also approve cups-filters for me? It contains lots of Coverity scan fixes, so would be great in Lunar ...


[09:01] <ppisati> brb
[10:23]  * apw realises he isn't on irc :) [sic]
[11:58] <smb> apw, nor on mumble fwiw
[11:59] <apw> no indeed ... up in the office
[13:08] <psivaa> jdstrand: with apparmor disabled, bug #1202203 does not occur
[13:08] <ubot2`> Launchpad bug 1202203 in isc-dhcp (Ubuntu) "Connection requests to saucy server VMs from a hosts fail after fresh preseeded VM installs" [Undecided,New] https://launchpad.net/bugs/1202203
[13:08] <psivaa> updated the bug with this info
[13:29] <jdstrand> psivaa: how many times did you try? iirc, it didn't always happen with apparmor enabled
[13:31] <psivaa> jdstrand: i've run at least 10 times with apparmor disabled. i was also running in parallel with apparmor enabled and i saw the bug in a couple of attempts in that
[13:31] <psivaa> out of 10 runs where apparmor disabled i did not see any
[14:38] <rtg> cking, 3.11-rc1 is booting OK on a non-UEFI Lenovo x120e
[14:39] <cking> guess it's a UEFI specific issue then
[14:39] <rtg> no doubt
[15:27] <arges> i see that CONFIG_BLK_DEV_RBD is in the precise common config, but it seems that 'modprobe rbd' doesn't work in the virtual flavor (tested on 3.2.0-49)
[15:28] <rtg> arges, extras ?
[15:28] <arges> rtg: ah
[15:29] <arges> rtg: bingo. thanks
[16:31] <ppisati> ubuntu@c16:~$ uname -a
[16:31] <ppisati> Linux c16 3.8.0-27-generic #40~precise2-Ubuntu SMP Thu Jul 18 08:12:12 UTC 2013 armv7l armv7l armv7l GNU/Linux
[16:31] <ppisati> ubuntu@c16:~$ lsb_release -a
[16:31] <ppisati> No LSB modules are available.
[16:31] <ppisati> Distributor ID: Ubuntu
[16:31] <ppisati> Description:    Ubuntu 12.04.2 LTS
[16:31] <ppisati> Release:        12.04
[16:31] <ppisati> Codename:       precise
[16:31] <ppisati> ubuntu@c16:~$
[16:31] <ppisati> rtg-afk: ^
[17:36] <rtg> ppisati, cool. I'll have a Saucy LTS 3.10 based kernel for you to try by about tomorrow.
[17:37] <ppisati> rtg: ok
[18:27] <rtg> ogasawara, apw: any objections to me uploading saucy ? there is an Azure fix that needs to get into the wild.
[18:28] <ogasawara> rtg: no objections here
[18:40] <infinity> rtg: apw and I have some saucy bits queued locally, but no harm in two back-to-back uploads.
[18:41] <infinity> rtg: I imagine our bits won't go out until tomorrow.
[18:44] <bjf> yum, saucy bits
[18:45] <rtg> infinity, np
[18:48] <infinity> rtg: Is yours an API bump?  (curious if I need to do a d-i upload tonight to match)
[18:48] <infinity> s/API/ABI/
[18:48] <infinity> I may have had some alcohol today.
[18:48] <rtg> infinity, it is an ABI bumper
[18:48] <infinity> rtg: Kay, I'll watch out for that then.  If ARM finishes before I sleep, I'll get a d-i in tonight.
[18:48] <rtg> infinity, and I would think tomorrow morning is soon enough
[18:48] <bjf> infinity, you don't remember if you have?
[18:49] <infinity> bjf: I'm fairly certain.
[18:50] <bjf> infinity, your not letting apw lead you astray are you?
[18:50] <infinity> bjf: I could think of worse examples to follow.
[21:08]  * rtg -> EOD