[08:40] <pstolowski> trainguards hello, may i ask for publishing of silo 65? i'm not authorized
[08:40] <sil2100> pstolowski: hey! Let me take a look
[08:41] <sil2100> pstolowski: so this one's autopkgtest failure is known and unrelated, yes? Just confirming
[08:43] <pstolowski> sil2100, yes, known, unstable unity8 tests, there is a fix coming separately https://code.launchpad.net/~aacid/unity8/fix_unstable_phone_stage_tests/+merge/297294
[08:46] <sil2100> pstolowski: ok, on it, reviewing
[08:48] <sil2100> pstolowski: just one thing - is there a bug filled for the flaky tests on arm64?
[08:49] <pstolowski> sil2100, for unity8?
[08:50] <sil2100> pstolowski: no, for ubuntu-system-settings-online-accounts
[08:50] <sil2100> pstolowski: the ubuntu-system-settings-online-accounts there is disabling arm64 unit-testin
[08:52] <pstolowski> sil2100, ah. dunno
[08:52] <pstolowski> mardy, ^ ?
[08:52] <sil2100> mardy: ping
[08:53]  * mardy reads
[08:53] <sil2100> Since now that arm64 is gaining on importance (for xenial), we need to have this tracked at least so that the test don't stay disabled for too long
[08:53] <sil2100> We need an assigned bug for that
[08:53] <mardy> sil2100: yes, there is, let me find it
[08:54] <mardy> sil2100: bug 1585942
[08:54] <sil2100> mardy: excellent, ok, thanks!
[08:54] <sil2100> Let me publish then
[08:56] <pstolowski> sil2100, uh ^
[08:56] <sil2100> pff
[08:58] <sil2100> Oh
[08:58] <sil2100> hm, funny thing
[08:59] <sil2100> WTH
[08:59] <sil2100> pstolowski: ok, so there was an unity-scopes-shell release happening in the meantime
[08:59] <sil2100> pstolowski: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+sourcepub/6544174/+listing-archive-extra
[09:00] <sil2100> pstolowski: which means... you'll have to no-change rebuild unity-scopes-shell now :<
[09:00] <sil2100> pstolowski: but I don't think a re-test will be needed
[09:00] <pstolowski> sil2100, ah, ok..
[09:00] <pstolowski> sil2100, yes, it was a no change rebuild for abi break in location service
[09:06] <pstolowski> sil2100, thanks for investigating! btw, when this lands you may want to mention it in your landing emails, as this is a significant change. plus there are a few known bugs surrounding it; you can find more details in the last section of the updates scopes test plan
[09:07] <sil2100> I know, I was already thinking about that when seeing the silo in testing ;)
[09:07] <pstolowski> sil2100, such as mx4 rebooting.. :/
[09:51] <oSoMoN> trainguards: could you please retry https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-068/+build/10022334 and https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-068/+build/10022337 for me? they depend on a UITK version that hadn’t migrated to -release yet, rebuilding now should make them succeed
[10:09] <robru> oSoMoN: done. you should bump your Build-Depends to point at the new version so that a) they would depwait instead of fail and b) they would auto-retry periodically
[10:09] <oSoMoN> robru, good point
[10:09] <oSoMoN> and thanks for retrying the failed jobs!
[10:09] <robru> oSoMoN: you're welcome!
[10:11] <oSoMoN> robru, ah, the armhf build would need to be retried too, it suffered from the same problem (but it took longer to fail): https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-068/+build/10022336
[10:11] <robru> oSoMoN: done
[10:11] <oSoMoN> cheers
[10:11] <robru> you're welcome
[11:01] <oSoMoN> robru, would you mind retrying the 3 failed builds at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-068/+sourcepub/6544262/+listing-archive-extra again? it seems the builds still didn’t pick up the updated UITK, hopefully now they will
[11:02] <robru> oSoMoN: done. which UITK are you hoping for?
[11:02] <oSoMoN> robru, https://launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/1.3.1995+16.10.20160607.1
[11:02] <oSoMoN> it’s been in the release pocket for > 1 hour, I wonder why it wasn’t picked up previously
[11:03] <robru> oSoMoN: well according to LP it was in release just 1 hour ago and I retried those builds 1hr ago so maybe just a bit racy. we'll see this time
[11:04] <oSoMoN> thanks
[12:06] <rvr> mardy: ping
[12:07] <mardy> rvr: pong
[12:07] <rvr> mardy: Silo 39
[12:07] <mardy> rvr: yes?
[12:08] <rvr> mardy: Without an active U1, I tapped on Cut the Rope price button
[12:08] <rvr> mardy: No prompt is displayed, see the logs here https://trello.com/c/dgYXSQVM/3305-1448-ubuntu-landing-039-ubuntu-system-settings-online-accounts-dbarth
[12:09] <rvr> By "active" I mean, there is no U1 account added
[12:10] <mardy> rvr: how did you get that log?
[12:11] <rvr> mardy: dbus.log
[12:11] <mardy> rvr: ah, ok
[12:11] <mardy> rvr: do you have other applications open?
[12:11] <rvr> mardy: Nope
[12:12] <mardy> rvr: looks like a mir issue, can you try killing unity8?
[12:13] <rvr> mardy: Done, let me see
[12:17] <rvr> mardy: Same result
[12:18] <dbarth> rvr: hmm
[12:18] <mardy> rvr: with about the same logs ("Couldn't setup prompt session")?
[12:19] <rvr> mardy: Yes, same logs
[12:19] <mardy> rvr: last thing, can you please try without the silo?
[12:19] <dbarth> i will re-flash my phone in parallel
[12:19] <rvr> Flashing
[12:19] <dbarth> rvr: you're on latest proposed?
[12:21] <rvr> dbarth: Yes
[12:23] <rvr> dbarth: mardy: 65 didn't land when I installed the silo, could be that?
[12:24] <dbarth> rvr: shouldn't be, it's only for the soundcloud fix
[12:24] <dbarth> rvr: you mean the silo with oxide?
[12:25] <rvr> dbarth: Confinement
[12:25] <mardy> rvr: but it still hasn't landed, has it?
[12:25] <rvr> mardy: Yeah, so I ask whether that is needed/related
[12:26] <mardy> rvr: it's not needed, but it could have an impact indeed
[12:26] <mardy> rvr: better test silo 39 without silo 65
[12:30] <rvr> mardy: Same problem with the silo
[12:30] <rvr> Err
[12:30] <rvr> Without
[12:30] <mardy> rvr: that's "good" ;-)
[12:31] <mardy> rvr: looks like some other landing caused that regression
[12:32] <mardy> rvr: I wonder if it's related to bug 1586219
[12:37] <mardy> rvr: how do you want to proceed? Are you trusting that the silo work, or do you want me to remove that branch from the silo, since you cannot effectively test it?
[12:38] <mardy> rvr: or would it be acceptable to test the silo using an older revision of rc-proposed, where you can test this fix?
[12:45] <rvr> mardy: Meeting, will ping you later
[13:16] <rvr> mardy: I have checked OA prompt, and it is displayed in other scopes, so seems the only thing failing is paid apps
[13:16] <rvr> mardy: I think the best way to proceed is to remove the branch, as it cannot be tested properly
[13:24] <mardy> rvr: OK
[13:29] <mardy> dbarth: I need to take https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/unconfined-req-1582824/+merge/295196 out of the silo; could you please ask another silo for it?
[13:31] <mardy> dbarth: or maybe not, I just saw your discussion with rvr in the other channel :-)
[13:31] <mardy> rvr: you decide :-)
[13:41] <dbarth> mardy: quick chat with rvr; we agreed to proceed with the rest of the validation of this silo
[13:41] <rvr> mardy: Just had a quick hangout with dbarth and clarified the test case for the prompt
[13:41] <rvr> Yup
[13:41] <dobey> hmm
[13:45] <rvr> mardy: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1592829
[13:47] <dobey> rvr: that is a regression. definitely shouldn't land a silo that is causing that
[13:48] <rvr> dobey: The silo is not causing that
[13:48] <rvr> Another silo introduced the regression
[13:48] <dobey> you're saying this happens in current rc-proposed?
[13:48] <rvr> Yes
[13:50] <dobey> rvr: it's opening the login UI here just fine
[13:50] <dobey> well "fine"
[13:50] <dobey> it's opening it _behind_ the pay-ui window
[13:51] <dobey> which is https://bugs.launchpad.net/canonical-devices-system-image/+bug/1586219
[13:51] <dobey> at least, on my mako that i literally just updated less than an hour ago
[13:52] <dobey> so this does indeed seem like the branch mardy mentioned is likely causing this issue
[13:52] <mardy> dobey: nope, because rvr said that the logs where the same without the silo: the trust session couldn't be created
[13:53] <dobey> mardy: but that doesn't make any sense, because it works fine here; so it seems like perhaps something got left around for the "without the silo" case
[13:54] <dobey> and i can't imagine what else would have already landed and caused this
[13:54] <mardy> dobey: given that it works fine there, could you please install the silo and try if it breaks?
[13:54] <dobey> what silo # is it?
[13:54] <mardy> dobey: silo 39
[13:54]  * rvr flashes again his device
[13:55] <dobey> granted, i have been hitting a very weird issue lately on my mako, when installing silos
[13:55] <dobey> but lets see what happens
[14:01] <dobey> mardy, rvr: hrmm, so after installing the silo it's still the same. login ui opens behind pay-ui "just fine"
[14:01] <dobey> really do wish that bug would be fixed though
[14:04] <mardy> dobey: I'm sure that if unity8 were to be reverted to the last working version, the bug would get fixed in no time :-)
[14:05] <dobey> assuming unity8 is the problem
[14:06] <mardy> dobey: sure, but it looks like the reason for the bug has already being identified
[14:08] <dobey> well anyway, that bug is certainly not introduced in this silo
[14:09] <rvr> mardy: Is it unity8?
[14:10] <dobey> the pop-under issue apparently is
[14:11] <dobey> but that's not what you claim to be hitting here
[14:12] <rvr> 2016-06-15 15:11:24,003 - WARNING - RequestAccess failed: QDBusError("com.ubuntu.OnlineAccountsUi.NoPromptSession", "Could not create a prompt session")
[14:12] <rvr> That is without any silo
[14:12] <dobey> weird
[14:12] <rvr> current build number: 104 device name: turbo channel: ubuntu-touch/rc-proposed/meizu.en
[14:12] <dobey> no idea what is causing that then. definitely not happening on my mako :)
[14:16] <sil2100_> pstolowski: did you rebuild silo 65 in the end?
[14:17] <pstolowski> sil2100_, i'm still waiting for that other change to land
[14:17] <sil2100_> Ah, it didn't migrate yet?
[14:17] <sil2100_> Damn
[14:18] <sil2100_> Tests in progress I see
[14:18] <sil2100_> eh
[14:50] <mardy> dbarth: do you need to push some button for https://requests.ci-train.ubuntu.com/#/ticket/1532 to land? QA approved it this morning
[14:58] <dbarth> mardy: generally not, it all goes automatically after that step
[15:00] <mardy> robru: can you please confirm? I just wonder why it's taking so long ^
[15:28] <dobey> mardy: someone with uplooad privs, like a coredev, has to approve the packaging changes and publish the ticket
[15:43] <rvr> oSoMoN: Silo 68 merge proposals need review and approval.
[15:44] <oSoMoN> rvr, darn, forgot about that, I’ll fix that
[15:45] <oSoMoN> rvr, done
[15:46] <pstolowski> sil2100, hey, can you check again if the migration that's blocking silo 65 isn't stuck or someting?
[16:20] <sil2100> pstolowski: I need to go now for dinner
[16:20] <sil2100> Will try to look later
[16:21] <sil2100> o/
[16:30] <rvr> bschaefer: ping
[16:31] <kenvandine> robru, any magic to get a silo built for a new package that has never been in the archive?
[16:35] <kenvandine> robru, does bileto handle native packages?  maybe it's unhappy by the native package version
[16:38] <bschaefer> rvr, pong
[16:38] <rvr> bschaefer: Hi
[16:38] <bschaefer> hello!
[16:38] <rvr> bschaefer: I'm checking silo 70
[16:38] <rvr> bschaefer: but I don't see any OSK appearing
[16:39] <rvr> bschaefer: Can you give me some info about how to test it?
[16:39] <bschaefer> rvr, you'll need a libertine branch as well
[16:39] <bschaefer> yup
[16:39] <bschaefer> rvr, https://code.launchpad.net/~brandontschaefer/libertine/seed-packages-workaround/+merge/297393
[16:39] <bschaefer> rvr, you've libertine + say gedit open?
[16:40] <bschaefer> rvr, you dont need need that branch since you can install whats needed
[16:40] <rvr> bschaefer: What is needed?
[16:40] <bschaefer> libertine-container-manager install-package -p maliit-inputcontext-gtk3
[16:40] <bschaefer> (for gedit)
[16:40] <bschaefer> if you're doing qt youll need
[16:40] <bschaefer> maliit-framework
[16:40] <rvr> Hmm
[16:41] <bschaefer> annnd maliit-inputcontext-gtk2 (on the container)
[16:41] <bschaefer> rvr, soo i should have been more descriptive, where are you testing this?
[16:41] <rvr> bschaefer: On the tablet
[16:41] <rvr> bschaefer: Using latest rc-proposed
[16:41] <rvr> with the silo installed
[16:42] <bschaefer> o ok, yeah that libertine branch was just approved to auto install those packages on your container
[16:42] <bschaefer> but right now they dont get installed by default
[16:42] <rvr> Hmm
[16:42] <bschaefer> rvr, and you cant use puritine since you cant edit the container
[16:42] <bschaefer> for testing you'll have to make your own container, install gedit
[16:42] <bschaefer> and then install the inputcontext
[16:43] <rvr> bschaefer: as phablet user:  Not using locking for read only lock file /var/lib/dpkg/lock
[16:44] <rvr> bschaefer: As root: Please do not run libertine-container-manager using sudo
[16:44] <bschaefer> rvr, yup thats puritine, its read only
[16:44] <bschaefer> (onces those packages get seeded you'll be OK)
[16:44] <bschaefer> for now to test on a R/W container do:
[16:44]  * bschaefer has to find command :)
[16:45] <bschaefer> ChrisTownsend, if you know off the top of your head ^
[16:46] <bschaefer> libertine_container_manager create -t chroot -s cont
[16:46] <bschaefer> (cont is the name of the container)
[16:46] <bschaefer> rvr, ^
[16:46] <ChrisTownsend> rvr: bschaefer: We need to land libertine first that will add the maliit packages automatically upon container creation.
[16:46] <bschaefer> ChrisTownsend, yeah... but for testing he could create his own container right?
[16:46] <ChrisTownsend> rvr: bschaefer: I'm working on a branch for that landing right this very moment.
[16:46] <bschaefer> o ok that makes things easier
[16:46] <bschaefer> rvr, we can just wait then :)
[16:47] <ChrisTownsend> bschaefer: He could and then manually install the maliit packages.
[16:47] <ChrisTownsend> bschaefer: And then he still needs the title bar workaround.
[16:47] <rvr> ChrisTownsend: Are you using the same silo?
[16:47] <ChrisTownsend> rvr: No, it won't be since libertine is a triple landing.
[16:47] <bschaefer> ChrisTownsend, that seed packages MP
[16:47] <bschaefer> has the toolbar workaround
[16:47] <ChrisTownsend> bschaefer: Right, I meant if he manually did it.
[16:47] <bschaefer> ooo right
[16:47] <bschaefer> yeah
[16:48] <rvr> Ok, then I will block this silo and test both at the same time
[16:48] <rvr> ChrisTownsend: ping me when ready
[16:48] <bschaefer> ChrisTownsend, thanks!
[16:48] <ChrisTownsend> rvr: Ok, sounds like a plan:)
[16:48] <bschaefer> rvr, thanks as well!
[16:48] <kenvandine> robru, i think you can disregard my ping now
[17:13] <ChrisTownsend> robru: Hey, I thought I would point out that https://requests.ci-train.ubuntu.com/#/ticket/1542 says "Ready to build" even though packages are building in the silo.  Not sure if that's a bug or something.
[17:42] <ChrisTownsend> robru: nm
[18:37] <bschaefer> wgrant, hello, im fixing the mir FTBFS issue but not hitting it in my pbuilder
[18:37] <bschaefer> would you be able to test this branch fixes it? https://code.launchpad.net/~brandontschaefer/mir/include-missing-header-0.21/+merge/297485
[19:11] <robru> kenvandine: it should handle native packages as long as it's source format 3
[19:31] <dobey> robru, kenvandine: yeah, native packages work, but you need source/format "3.0 (native)"
[19:33] <kenvandine> thx
[19:37] <bzoltan> robru: how can i build only the gles package of my silo?
[19:37] <bzoltan> robru:  I mean rebuild.
[19:38] <bzoltan> robru: I would need to rebuild only this - https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-008/+build/10024176
[19:39] <dobey> bzoltan: you have to ping robru or someone with access to upload directly to the PPA, to retry the build.
[19:39] <robru> bzoltan: by asking Ken nicely (I'm EOD in Athens)
[19:40] <bzoltan> kenvandine:  would you be able to help me with this?
[19:41] <kenvandine> sure
[19:41] <bzoltan> kenvandine:  thank you!
[19:42] <kenvandine> hmmm...
[19:42] <kenvandine> oh... nm
[19:42] <bzoltan> I have no idea why, but the unit tests are much more flakier in the silo builds than with the jenkins. I am landing MRs what were tested about 14-16 times before they were siloed. Strange.
[19:42] <kenvandine> bzoltan, rebuild kicked
[19:43] <bzoltan> kenvandine: thanks a lot... I was rebuilding this silo like 4th time and always a different package (out of 12) fails for different magical reason.
[20:25] <ChrisTownsend> rvr: I'm sure you're not around, but https://requests.ci-train.ubuntu.com/#/ticket/1542 is ready to go along with silo 70.  I have instructions in that request including a link to the new Puritine click.
[20:41] <tvoss_> robru, am I good to hit merge on https://requests.ci-train.ubuntu.com/#/ticket/1451
[20:42] <robru> tvoss_: no? It's already landed
[20:44] <tvoss_> robru, ah okay, I'm probably confused by the buttons :)
[20:45] <robru> tvoss_: merging is automatic, only forced in special cases


[01:47] <stgraber> @schedule
[01:47] <Ubugtu> Schedule for Etc/UTC: 08 Nov 20:00: Edubuntu | 15 Nov 12:00: Edubuntu | 22 Nov 20:00: Edubuntu | 28 Nov 16:00: LoCo Team | 29 Nov 12:00: Edubuntu
[09:17] <Mez> @schedule
[09:17] <Ubugtu> Schedule for Etc/UTC: 08 Nov 20:00: Edubuntu | 15 Nov 12:00: Edubuntu | 22 Nov 20:00: Edubuntu | 28 Nov 16:00: LoCo Team | 29 Nov 12:00: Edubuntu
[09:17] <Mez> @schedule birmingham
[09:20] <Ng>  l/win 71
[09:20] <Ng>  /win 71
[09:20] <Ng> gah
[09:20] <Ng> I suck at irc ;)
[09:29] <ian_brasil> @schedule manaus
[09:29] <Ubugtu> Schedule for America/Manaus: 08 Nov 16:00: Edubuntu | 15 Nov 08:00: Edubuntu | 22 Nov 16:00: Edubuntu | 28 Nov 12:00: LoCo Team | 29 Nov 08:00: Edubuntu
[09:49] <sivang> Ng: 71 ??
[09:49] <sivang> Ng: you need some cleanup obviously
[09:49] <Ng> yeah
[09:49] <Ng> lots of windows from regisering people


[06:49] <ara> good morning all!
[11:07] <ara> jibel, can you remind me where mvo hosts the code for automated upgrade tests?
[11:07] <jibel> ara, it's part of update-manager
[11:09] <ara> jibel, but the launchpad code for it?
[11:11] <jibel> ara, lp:ubuntu/update-manager in AutoUpgradeTester
[11:12] <jibel> ara, it doesn't work in maverick and needs to be updated with the latest vmbuilder.
[11:12] <ara> jibel, OK, thanks
[11:14] <mvo> jibel: there is no fix for the "outputs a random filename yet"?
[11:14] <mvo> jibel: in vmbuilder?
[11:19] <jibel> mvo, I haven't checked upstream, but in maverick the last update was in July and I haven't been able to specify an output file name with this version only an output directory.
[11:19] <jibel> mvo, but maybe I missed something.
[11:20] <mvo> jibel: ok, I will poke soren and/or add code in the auto-upgrader-tester to just use glob to find the file


[12:41] <BluesKaj> Hiyas all
[13:37] <penguin42> BluesKaj: Is the firefox pdf reader still working for you?
[13:37] <BluesKaj> penguin42, let me check
[13:38] <penguin42> I'm seeing it hang before displaying the 1st page
[13:39] <BluesKaj> got a url i can check , have no pdf files on my pc
[13:41] <yofel> BluesKaj: http://www.scala-lang.org/docu/files/ScalaTutorial.pdf
[13:41] <yofel> works for me
[13:41] <yofel> penguin42: got the relevant url?
[13:41] <penguin42> hmph
[13:41] <penguin42> yofel: http://www.montblanc-project.eu/sites/default/files/publications/Are%20mobile%20processors%20ready%20for%20HPC.pdf
[13:41]  * penguin42 wgot it and it's fine - so the site is ok
[13:42] <penguin42> but I had a different one last night that did the same thing
[13:42] <BluesKaj> sorry about the disconn , ..trying to set up kvpnc , but it keeps kicking konversation
[13:44] <yofel> It didn't finish loading it on first attempt. I then loaded the url again, now it displays the PDF and I have a "This PDF document might not be displayed correctly" warning at the top
[13:44] <BluesKaj> penguin42, that url/pdf file loads and works fine here on FF , but I'n still on FF 20
[13:44]  * penguin42 is on 21.0
[13:44]  * yofel is on 22
[13:44] <penguin42> interesting
[13:45] <BluesKaj> ahh
[13:45] <yofel> I got it from -proposed which I enabled yesterday to pull some other fixes
[13:53] <BluesKaj> i don't have the proposed repos enabled , but I guess I should
[13:54]  * penguin42 doesn't run proposed but is on 21 - I guess that is in main?
[13:54] <yofel> not really, at least it's not recommended. I only enable it sometimes when I need something from there
[13:55] <yofel> 21 is in release, yes
[13:55] <yofel> uh wait
[13:55] <yofel> ok, saucy has 20, raring-updates has 21, saucy-proposed has 22
[13:56] <BluesKaj> penguin42, yofel , i've dist-upgraded several times and FF hasn'y upgraded , but now that proposed is enable I see the FF upgrade iin the terminal
[13:57]  * penguin42 doesn't understand the output of apt-cache policy - it's listing 21.0... from 100 /var/lib/dpkg/status   and 20.0.... from saucy/main
[13:58] <penguin42> http://paste.ubuntu.com/5703597/
[13:59] <BluesKaj> penguin42, I see FF 20 in saucy main , FF 22 in proposed
[13:59] <yofel> you have 21 from raring http://paste.kde.org/751058
[14:01] <penguin42> that's very confusing http://packages.ubuntu.com/search?keywords=firefox&searchon=names&suite=all&section=all   doesn't show the 21's
[14:01] <penguin42> and it's bizarre that there's a security update in raring that's not in saucy
[14:02] <yofel> not really, after all 22 is pending for saucy
[14:13] <BluesKaj> ok , just upgraded FF to 22 ,and the montblanc pdf files loaded just fine and viewable without any warnings
[14:14] <BluesKaj> looks sgood to me
[14:14] <yofel> maybe because I loaded it twice...
[14:14]  * yofel restarts ff
[14:15] <penguin42> hmm
[14:17] <yofel> hm, now it loaded fine for me too
[14:21] <BluesKaj> http://pastebin.com/gcEqNGvv
[14:28] <penguin42> hmm, ok for me as well in 22 - hmm
[14:44] <BluesKaj> damn kvpnc ..looks buggy
[17:02] <jaba_> hi
[17:02] <jaba_> i have problem setup ubuntu 13.04 with newest cinnamon
[17:03] <jaba_> fonts in cinnamon menu ar messy, half not showing
[17:06] <Daekdroom> !13.04 | jaba_
[17:06] <Daekdroom> Oops
[17:07] <Daekdroom> Thought that would tell you to go to #ubuntu
[17:07] <Daekdroom> Well, anyway. Now that Ubuntu 13.04 is released, this is no longer the channel to talk about it.
[17:30] <bjsnider> i don't think cinnamon is supported here anyway
[17:30] <penguin42> why? cinnamon is in the repos
[17:30] <k1l_> cinnamon is in the repos since 13.04
[17:31] <k1l_> but in what way we can give support for that is another question, imho
[17:31] <bjsnider> in the repos is not the issue
[17:31] <bjsnider> lots of stuff is in the repos
[17:49] <penguin42> well yeh but generally if someone came here and said something was broken we'd try and help, I mean it's not like it's the paid support
[19:58] <lordievader> Good evening.
[20:01] <penguin42> hey
[20:04] <lordievader> Hey penguin42, how are you?
[20:04] <penguin42> not too bad


[14:02] <stgraber> NCommander, stokachu, arges, jibel, skaet, smoser, jamespage: ping
[14:02] <arges> o/
[14:02] <jamespage> o/
[14:02] <stgraber> #startmeeting 12.04.1 team meeting
[14:02] <meetingology> Meeting started Thu Aug  9 14:02:28 2012 UTC.  The chair is stgraber. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:02] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[14:02] <seb128> hey
[14:02] <stgraber> hey seb128
[14:02] <jibel> hi
[14:02] <stgraber> #topic Action items review
[14:02] <skaet> hi
[14:02] <stgraber> xnox to liase with ballons, gema and jibel w.r.t. fs/storage testing
[14:02] <stgraber> xnox: there by any chance?
[14:03] <jibel> no news from xnox
[14:03] <xnox> nope
[14:03] <xnox> but there is progress in utah development, such that this testing can be now feasible
[14:03] <xnox> will do this next week.
[14:03] <xnox> ..
[14:03] <stgraber> ok, cool
[14:03] <stgraber> Flavor leads participating, please verify that the images are as you
[14:03] <stgraber> expect, and start smoke testing tomorrow to make sure all the right
[14:03] <stgraber> 12.04.1 bits are in place.
[14:04] <stgraber> skaet: did you get any feedback on that?
[14:04] <skaet> yup,  flavors started testing last Friday,  results coming in
[14:04] <skaet> not heard of any nasty surprises from them.
[14:05] <skaet> ..
[14:05] <stgraber> good to hear
[14:05] <stgraber> #topic Review of upcoming deadlines
[14:05] <stgraber>   - today 21:00 UTC: KernelFreeze, LanguageTranslationDeadline, SRU Fix Validation Testing
[14:05] <stgraber>   - 2012/08/16: FinalFreeze, ReleaseNoteFreeze
[14:05] <stgraber>   - 2012/08/23: Ubuntu 12.04.1
[14:06] <stgraber> The plan is to switch images to building from -updates today, though we'll need quite a few more tricks to have them really usable, so it might have to wait till tomorrow or we'll be building an oversized batch with broken upgrade path
[14:06] <stgraber> #topic Quick look through the current bug lists, checking for progress.
[14:07] <stgraber> Not going to paste stats this time as it's not as relevant at this stage.
[14:07] <stgraber> Verification and fixes of any detected regression should be the main focus at this point.
[14:07] <stgraber> We're at least still waiting on maas and eglibc at this point, these need to be in -proposed by 21:00 UTC today at the latest and might still be getting their exception declined if it's considered too dangerous at this point.
[14:08] <stgraber> I'm currently trying to get our alternate image to allow for internet-less upgrades from 10.04 to 12.04, this might require some extra shuffling and uploading later today
[14:08] <stgraber> as a general rule, if you want something in 12.04.1, upload it to the queue. It's easier for us to then review it here and grant or decline the exception. Poking #ubuntu-release might also make things go a bit faster (if we missed an upload)
[14:09] <stgraber> any critical bugs that need some hilighting?
[14:10] <stgraber> taking that as a no
[14:11] <stgraber> #topic Media oversizedness
[14:11] <stgraber> The recent live-build fixes have made both amd64 and amd64+mac fit again
[14:11] <smartboyhw> Yeah!
[14:11] <stgraber> i386 will need some fixing as it's including an extra langpack making it oversized at the moment
[14:12] <stgraber> a simple seed change didn't do the trick, so we'll likely need to hack it around in live-build
[14:12] <stgraber> I'll be looking into that once I'm done fixing the upgrade bug
[14:12] <skaet> :)
[14:12] <stgraber> As far as I know, all the other images currently fit, so unless some packages in -proposed got a big size increase, we should be fine
[14:13] <stgraber> #topic Round table
[14:13] <stgraber> stgraber@castiana:~$ echo $(shuf -e NCommander seb128 stgraber stokachu arges jibel skaet smoser jamespage)
[14:13] <stgraber> stokachu NCommander seb128 skaet stgraber arges jamespage smoser jibel
[14:13] <stgraber> stokachu:
[14:14] <stgraber> NCommander: then
[14:14] <smoser> o/
[14:15] <stgraber> seb128:
[14:15] <seb128> hey
[14:15] <seb128> nothing special, we are hard frozen
[14:15] <seb128> a compiz SRU was uploaded to fix the arm* build issue from the one currently in proposed
[14:16] <seb128> discussion is ongoing on the release list about whoopsie on or off
[14:16] <seb128> otherwise we pushing some fixes to .2
[14:16] <seb128> we are mostly good at this point I think
[14:16] <seb128> ..
[14:17] <stgraber> ok. I guess you'll want to do some poking in #ubuntu-release to get that compiz upload in
[14:17] <stgraber> skaet:
[14:17] <skaet> Daily images will be switching from being built based on  -proposed to being built based on -updates after 2100 today.
[14:17] <skaet> Release Note framework and initial edit for 12.04.1 set up was done.
[14:17] <skaet> Release Notes are available for updates now.      Plan this time around is to make the release notes reflective of the 12.04.1 image, and include changelogs.   To make edits (adding bugs, documenting new features added since 12.04),  please edit the appropriate wiki linked to from: https://wiki.ubuntu.com/PrecisePangolin/ReleaseN
[14:17] <skaet> otes
[14:17] <skaet> For example: if there is a new server feature for 12.04.1,  a note should go into: https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuServer  (the original version for 12.04 is at: https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuServer/UbuntuServer-12.04)
[14:17] <skaet> ..
[14:18] <stgraber> stokachu:
[14:18] <stgraber> oops
[14:18] <stgraber> stgraber:
[14:18] <skaet> :)
[14:19] <stgraber> right, so I've been working on that upgrade bug with slangasek yesterday. I managed to get it working locally but now we need to achieve the same miracle with the alternate media.
[14:19] <stgraber> Will continue on that today, then look at fixing the langpack list on the i386 daily-live
[14:20] <stgraber> I also have a bunch more verification to do as the list is kind of long at this point
[14:20] <stgraber> then maybe I'll even find the time to look at the usb-creator verification failure, though I don't consider this 12.04.1 critical at this point, so if it's easy to fix, good, otherwise, will just postpone
[14:20] <stgraber> arges:
[14:21] <arges> I setup the cronjob to upload the point release page
[14:21] <arges> http://people.canonical.com/~arges/point-release/milestone-12.04.1.html
[14:21] <arges> Submitted code to arsenal, hope to get things on cranberry and also start putting up pages for 12.04.2
[14:21] <arges> ..
[14:21] <arges> oh
[14:22] <arges> still waiting on http://launchpad.net/bugs/979003
[14:22] <arges> ..
[14:22] <stgraber> yeah... infinity said we'd get it uploaded today...
[14:22] <stgraber> jamespage:
[14:23] <jamespage> so most server stuff is looking ok; the only straggler being walinuxagent which is currently stuck in the precise-propsed NEW queue
[14:23] <jamespage> this is required for enablement of the azure IaaS platform
[14:23] <jamespage> other than that I've been repointing stuff that won't make it to -updates
[14:23] <jamespage> I'll let smoser cover maas
[14:23] <jamespage> ..
[14:24] <smoser> there are not going to be any updates to maas for 12.04.1
[14:25] <stgraber> good to hear ;)
[14:25] <stgraber> smoser:
[14:26] <smoser> i have nothing else really.
[14:26] <smoser> i woudl say ther eis an outside chance at having a cloud-init change in today
[14:26] <smoser> but that is low likelyhood.
[14:27] <stgraber> ok
[14:27] <stgraber> jibel:
[14:27] <jibel> Focus on upgrade testing:
[14:27] <jibel> * defects found with automated tests are mostly obsolete configuration files. I don't know if they are all harmless so I reported a few for desktop and server:
[14:27] <jibel> bug 1034824 bug 1034829 bug 1034830 bug 1034832
[14:27] <jibel> You can have a look to the artefact obsolete_conffiles.log attached to the jobs at https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/ and if you want more, tell me and I'll file more
[14:28] <jibel> * bug 1034889
[14:28] <jibel> * I've been hit by bug 979661 during an upgrade from Oneiric (debconf failed to load GTK). It seems to occur rather frequently. but need latest update-manager to verify the workaround really works
[14:29] <jibel> * Community bugs:
[14:29] <jibel>     bug 1034794: if someone from foundations could have a look
[14:29] <jibel>     bug 1034668: for the desktop team
[14:29] <jibel> todo:
[14:29] <jibel> * verification of bug 1029531 in progress but failing at the moment, waiting for openoffice to be accepted and seeded.
[14:29] <jibel> furthermore the CD contains update-manager 0.156.14 instead of <IP_ADDRESS> (-proposed) or .6 (-updates)
[14:29] <jibel> One request:
[14:29] <jibel> Would it be possible to update UpgraderTool in http://changelogs.ubuntu.com/meta-release-development to point to the version in precise-updates (or better precise-proposed) if that makes sense ?
[14:29] <jibel> It currently points to the version from the release pocket and makes testing versions from proposed and updates a bit harder, and people who are currently upgrading to precise with -d doesn't use the latest version.
[14:30] <jibel> Installation smoke testing;
[14:30] <jibel> Nothing found for the moment.
[14:30] <jibel> ..
[14:30] <skaet> jibel,  we'll be switching the builds to be from -updates later today,  so probably not make sense to switch now.
[14:30] <skaet> however,  something to note for 12.04.2
[14:31] <stgraber> mvo: ^
[14:32] <skaet> ..
[14:32] <jibel> skaet, will that pull the release-upgrader from -updates too ? because currently for example alternate is built with packages from -proposed but the upgrader is from -release
[14:32] <slangasek> switching to -updates today?  I thought the switch wasn't meant to be until we're farther along with the SRU promotion?
[14:33] <skaet> slangasek,  schedule discussed was we'd be switching the dailies to be built from -updates today,  rather than -proposed,  to ready for final freeze.
[14:33] <slangasek> hmm
[14:33] <slangasek> except that means no more image-based testing of the stuff that's currently in -proposed and not ready for promotion
[14:34] <slangasek> and since we're iterating CD upgrade fixes, that's rather significant
[14:34] <skaet> hmm..
[14:34] <slangasek> perhaps we should push back the switch?
[14:34] <stgraber> yeah, that's why I said earlier that I'm not going to do the switch until we have a test image that upgrades fine and isn't oversized
[14:35] <slangasek> ok
[14:35] <skaet> lets discuss further in #ubuntu-release then after the meeting.
[14:35] <stgraber> I don't necessarily mind regressing with the switch to -updates as long as I know that the fixes in -proposed are correct and will indeed fix the image when they land (or the SRU team can decide to let them through to -updates before the 7 days)
[14:36] <stgraber> #topic AOB
[14:38] <stgraber> ok, let's get back to work :)
[14:38] <stgraber> #endmeeting
[14:38] <meetingology> Meeting ended Thu Aug  9 14:38:21 2012 UTC.
[14:38] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-08-09-14.02.moin.txt
[14:38] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-08-09-14.02.html
[14:40] <mvo> jibel: sure I can update meta-release-development
[14:40] <seb128> thanks
[14:41] <skaet> thanks stgraber
[14:41] <jibel> thanks stgraber
[14:41] <mvo> jibel: meta-release-development and/or meta-release-lts-development?
[14:41] <jibel> mvo, well, skaet wants to wait until builds are from -updates
[14:42] <mvo> jibel: ok, just shout and I update it immediately
[14:42] <jibel> mvo, ok, thank you
[16:00] <micahg> anyone here for the MOTU meeting?
[16:01]  * dholbach is here, but will have to run for 3-4 minutes
[16:01]  * iulian waves.
[16:01]  * iulian is here on and off.
[16:02] <micahg> let's wait a couple minutes to see if anyone else shows up
[16:02] <jtaylor> <
[16:03] <dholbach> micahg: shall we just start and see who joins in? :)
[16:03] <dholbach> #startmeeting
[16:03] <meetingology> Meeting started Thu Aug  9 16:03:34 2012 UTC.  The chair is dholbach. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:03] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:03] <dholbach> welcome everybody to the MOTU meeting
[16:03] <dholbach> we have our agenda over here: https://wiki.ubuntu.com/MOTU/Meetings
[16:04] <dholbach> #topic Killing off sqlite 2 (src:sqlite)
[16:04] <dholbach> anyone here to discuss the topic? :)
[16:04] <micahg> o/
[16:04] <dholbach> awesome
[16:05] <jtaylor> I can probably help out to but I'm not familiar with the situation
[16:05] <dholbach> micahg: can you enlighten us about what's planned?
[16:05] <micahg> So, this is something I wanted to do for precise, but ran out of time, I've repeatedly requested for the removal from Debian without success, so I figure we can push things forward by JFDI in Ubuntu and pushing up patches
[16:05] <micahg> we have to fix up the remaining reverse dependencies to drop sqlite 2 support as was done for applications in main for precise
[16:06] <dholbach> micahg: does this involve major porting work or is it something we could make part of our bug fixing initiatives?
[16:07] <micahg> sometimes it's a flag, there might be a little porting work, I'd be fine with dropping anything that requires porting until it's done upstream (I would venture that most upstreams probably have already done this, it might not be packaged yet though)
[16:08] <jtaylor> how many packages are affected?
[16:08] <Laney> can we get a tracker?
[16:08] <micahg> http://paste.ubuntu.com/1138024/
[16:08] <micahg> Laney: sure, sounds like a good idea
[16:08] <Laney> nice
[16:09] <micahg> the list is much smaller than it was in precise FWIR
[16:09] <dholbach> the python-sqlite rdeps would likely need to go too?
[16:09] <dholbach> or rather be updated
[16:10]  * xnox is testing ben tracker file locally
[16:10] <Laney> good old xnox
[16:10] <micahg> yeah, updated to use python-pysqlite2
[16:10] <dholbach> old?
[16:10] <dholbach> :-P
[16:10] <Laney> who still doesn't love motu enough to hang around in our channel :(
[16:10] <dholbach> good old public shaming
[16:10] <micahg> only about 10 rdepends on python-sqlite
[16:10] <Laney> now that /is/ old
[16:11] <dholbach> micahg: I'm happy to advertise the initiative as part of the bug fixing initiatives - maybe not for new contributors, but still it'd be good to get some eyeballs on it - maybe we should talk after the meeting about what we need to do for this
[16:12] <micahg> ok
[16:12] <dholbach> it doesn't look like anybody has major objections to getting this done :)
[16:13]  * xnox rumbles something about DD and motu
[16:13] <dholbach> micahg: do you feel we have a good enough way forward to getting sqlite out of the archive?
[16:14] <micahg> dholbach: I think so
[16:14] <dholbach> fantastic
[16:14] <dholbach> moving on then
[16:14] <dholbach> #topic update from Developer Advisory Team
[16:14] <dholbach> I don't have much to report, as I was on holidays
[16:15] <dholbach> but I'm happy to report that we have a bunch of new contributors in quantal already who we're reaching out to
[16:15] <dholbach> we are still looking for new contributors to the DAT, so if you're interested in the social aspects of Ubuntu Development just ping me
[16:15] <dholbach> any questions about the DAT?
[16:16] <dholbach> ok, moving on :)
[16:16] <dholbach> #topic review https://wiki.ubuntu.com/UbuntuDevelopment/BugFixingInitiative
[16:17] <dholbach> it looks like it hasn't been updated in a while, so it'd be good to review it and see what we might want to add or replace on there
[16:17] <dholbach> micahg and I will add something about the sqlite situation - anyone else who would like to advertise some necessary work in the archive?
[16:17] <micahg> well, I've got something else, but not for the list
[16:18]  * xnox boost1.50 transition quantal or R-series?
[16:18] <dholbach> now is a probably a good time to get new or reemerging contributors involved as quantal is likely less daunting to run on a regular basis :)
[16:18] <dholbach> micahg: an initiative you'd like to propose or a new/separate topic?
[16:18] <micahg> dholbach: initiative, but only for existing MOTUs
[16:19] <micahg> not to be exclusive
[16:19] <dholbach> which one is that?
[16:19] <micahg> ghc rebuilds :)
[16:20] <dholbach> xnox, I can't give you a proper answer on this, but I could imagine that ScottK might know more - wasn't this discussed at some stage on the ubuntu-devel@ list already?
[16:20] <dholbach> micahg: I'll do the minutes later on and am happy to mention it in there if that suits you
[16:20] <ScottK> xnox: R.
[16:20] <micahg> xnox: I think we have enough cleanup for quantal without starting another boost transition
[16:20] <xnox> ScottK: micahg: agreed.
[16:20] <dholbach> ok, that's settled then :)
[16:21] <ScottK> Pick your boost at release open and don't change without a very good reason.
[16:21] <micahg> dholbach: yeah, if anyone wants to help, just link to the tracker: http://people.canonical.com/~ubuntu-archive/transitions/ghc.html , I think we're coordinating in -motu for it
[16:21] <xnox> ScottK: micahg: where/how do we add tasks for R archive opening? it would help to have boost-defaults uploaded at archive opening, same as it was done for Q
[16:21] <dholbach> thanks a lot micahg
[16:21] <ScottK> In fact, I'd be inclined to stick with 1.49 until after Wheezy releases and Debian changes.
[16:21] <ScottK> xnox: You have to remember to do it and talk to doko/cjwatson to coordinate.
[16:22] <ScottK> We should discuss it though.
[16:22] <micahg> there's a wiki page for archive opening tasks
[16:22] <xnox> ok. I'll take it to mailing list closer to R opening.
[16:22] <dholbach> ok - anything else we should be pointing new (or other work-seeking) contributors towards?
[16:22] <ScottK> Sounds good.
[16:22] <micahg> fix Debian RC bugs so wheezy can release :)
[16:24] <dholbach> alright, I guess we can move on then - I'll have a look over it tomorrow again and blog about it
[16:24] <dholbach> #topic Any other business?
[16:25] <dholbach> I'm not sure why "Update MOTU/FAQ" is still on the agenda
[16:25] <dholbach> I'll remove it - it seems like Bhavani already updated it
[16:25] <micahg> o/
[16:26] <dholbach> micahg: go
[16:26] <cjwatson> xnox: Feel free to add stuff to https://wiki.ubuntu.com/NewReleaseCycleProcess if it's been discussed.
[16:26] <cjwatson> (Or is obviously sensible.)
[16:27] <micahg> just a reminder that backports is a great way to get newer software into old releases without having to fiddle with PPAs, get the version you want into the dev release and run the requestbackport script from ubuntu-dev-tools (12.04+), the script will let you know what testing needs to be done
[16:28] <micahg> oh, also, did we get anywhere with -backports open at feature freeze yet?
[16:28] <dholbach> maybe a blog post about this would be good to have too?
[16:28] <micahg> dholbach: yeah, I've been meaning to set up a blog
[16:28] <dholbach> fantastic
[16:28] <micahg> cjwatson: can we do backports open at feature freeze yet?
[16:29] <cjwatson> I don't recall.  Wasn't there a work item or a bug or something?
[16:30] <Laney> there was some launchpad change but I always forget what it is
[16:30] <Laney> pretty sure ajmitch got the work item though :-)
[16:31] <micahg> sleeptold, I think that's a new one...
[16:31] <dholbach> ok, any other other business? :)
[16:32] <dholbach> perfect - I'll get out the minutes tomorrow
[16:32] <dholbach> thanks a lot everyone! :)
[16:32] <dholbach> #endmeeting
[16:32] <meetingology> Meeting ended Thu Aug  9 16:32:41 2012 UTC.
[16:32] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-08-09-16.03.moin.txt
[16:32] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-08-09-16.03.html
[16:32] <Laney> hang on
[16:32] <Laney> oh, nm
[16:32] <micahg> thanks dholbach
[16:32] <Laney> I felt a thought formulating
[16:33] <dholbach> Laney, sorry - what did you want to talk about?
[16:33] <Laney> I was thinking the other day about the plusonemaint team
[16:33] <Laney> and how the people there tend to come up with little projects to get done
[16:34] <Laney> it just occurs to me that there could be some sharing to be done there
[16:34] <Laney> that is all, it's quite a nebulous thought
[16:34] <dholbach> Laney, do you think it could help to bring up the idea in a mailing list conversion so we could all expand on it?
[16:35] <Laney> i'm not even sure what to suggest :P
[16:35] <dholbach> ok, I'll try to mention it accurately in the minutes ;-)
[16:36] <Laney> anyway, carry on
[16:36] <dholbach> and hope you'll have some free time to find out how we could do something about it
[16:36] <dholbach> maybe it'd already help to mention a few of those little projects to give everyone some ideas
[16:36] <Laney> just, we could encourage them to send out "this is what we're going to work on this week" updates or something
[16:37] <dholbach> yes, that'd very likely help
[16:38] <Laney> not sure how organised it all is though really
[16:39] <dholbach> maybe bring it up on the ML to remind everyone to mention their projects, if suitable? *shrugs*
[16:40]  * Laney goes to #ubuntu+1-maint
[16:40] <dholbach> sweet
[16:40] <dholbach> adjourned :)
[18:00] <jono> alrighty!
[18:00]  * cielak waves
[18:00] <jono> #startmeeting
[18:00] <meetingology> Meeting started Thu Aug  9 18:00:30 2012 UTC.  The chair is jono. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[18:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[18:00] <mfisch> hi
[18:00] <jono> welcome everyone to the Ubuntu Accomplishments meeting!
[18:00] <jono> who is here for the meeting today?
[18:00] <cielak> o/
[18:01] <mfisch> me!
[18:01] <jono> alrighty :-)
[18:01]  * janos too
[18:01] <jono> woo!
[18:01] <jono> so before we start, a quick update on the Canonical IS RT ticket
[18:02] <jono> I had a response from Canonical IS about us deploying our service there and they are currently evaluating hardware and resource needs
[18:02] <jono> one thing they made clear is that it is unlikely to be deployed before late Aug due to a data center move]
[18:02] <cielak> I have a question in this matter
[18:02] <jono> the good news is that this looks this is going to go ahead
[18:02] <jono> sure cielak
[18:03] <janos> nice nice
[18:03] <cielak> are they going to migrate the server including the U1 setup?
[18:03] <jono> cielak, yeah
[18:03] <cielak> I mean - after they deploy the validation server on their machines, will shares keep being active?
[18:03] <jono> cielak, yes, they should be
[18:04] <cielak> alright! I was worried if we'll need to somehow recreate them all...
[18:04] <jono> we are just deploying the same U1 user on a different machine
[18:04] <cielak> hm, that makes sense
[18:04] <jono> the sharecheck script int he validation server should reload them all and resubscribe them
[18:04] <cielak> yeah :)
[18:04] <cielak> thanks :)
[18:04] <jono> and the good news is that while we set this up our existing server can still be serving requests
[18:05] <cielak> won't they collide?
[18:06] <jono> cielak, they wont collide so long as only one server is processing the jobs
[18:06] <jono> having the multiple shares set up should be fine
[18:06] <jono> so we can get the shares working on the IS server while the current server processes jobs
[18:06] <cielak> aah, so only one signs the trophies, but all can browse then?
[18:06] <cielak> them*
[18:06] <jono> right
[18:06] <cielak> that's cool!
[18:06] <jono> and then we switch over the signing to the new server
[18:07] <jono> any more questions about the move?
[18:07] <cielak> not from me
[18:07] <jono> cool
[18:07] <jono> alrighty, so onto 0.3 planning
[18:07] <jono> so we have a few outstanding MPs to review
[18:07] <jono> cielak, did you get a chance to look at the big rename branch?
[18:08] <cielak> not yet, I gave only a brief look ;)
[18:08] <jono> I know mfisch took a look
[18:08] <jono> cool, I think should an invasive change will want a look from each of us
[18:08] <mfisch> yeah I did a couple looks
[18:08] <jono> and then we will need to port the viewer and lens, which shouldnt be much work
[18:08] <cielak> although it seems to me that ideally we would merge it together with a similar branch for the viewer
[18:08] <mfisch> it is invasive but using grep and vi it's easy to follow
[18:08] <mfisch> yeah the viewer merge should be ready to go
[18:09] <jono> mfisch, oh did you work on the change to the viewer?
[18:09] <mfisch> no
[18:09] <mfisch> sorry I mean should be ready to go before we merge the daemon
[18:09] <jono> oh I see
[18:09] <jono> yeah, I agree
[18:10] <jono> one other point
[18:10] <jono> we should also fix https://bugs.launchpad.net/bugs/1026749 while we are doing this
[18:10] <jono> mfisch, would you be happy to work on this?
[18:11] <jono> actually that bug is not critical
[18:11] <jono> I forgot it is about vars as opposed to functions
[18:12] <mfisch> hold on 1 sec
[18:12] <jono> sure
[18:12] <mfisch> yeah I can do that, but it will not affect the API
[18:13] <jono> yeah, no worrieds
[18:13] <jono> if you can assign it to yourself that would be cool
[18:13] <jono> ooh
[18:13] <jono> we should also fix https://bugs.launchpad.net/bugs/1024085
[18:13] <jono> I am just trying to ensure we focus on API related changes
[18:14] <jono> anyone want to take this one?
[18:15] <jono> cielak, which bugs would you like to focus on in 0.3 as we move forward?
[18:15] <jono> I am wondering if it is possible for us to get some assignments on these bugs
[18:16] <jono> I would like to open up further testing in a few weeks if poss
[18:16] <cielak> well, the point is that in 2 days I'll be offline for 2 weeks, so I would rather not assign myself to anything greater to avoid blocking anything
[18:16] <mfisch> I thought that one was fixed with the big API change?
[18:17] <jono> cielak, ahhh of course
[18:17] <jono> good point
[18:17] <jono> mfisch, oh it is?
[18:17] <cielak> by the way, I am delighted to see Brian working extensively on some bugs out there :)
[18:17] <mfisch> jono: looking
[18:18] <jono> cielak, totally!
[18:18] <jono> so maybe while cielak is away, mfisch would you be happy to look at the daemon bugs and I will look at viewer bugs?
[18:18] <cielak> hm, I can take #1033773, this shouldn't take time ;)
[18:18] <mfisch> jono: unfortately I'm also off and on next week
[18:18] <mfisch> week after is fine
[18:19] <jono> mfisch, no worries, so I will try and nail some viewer bugs next week
[18:19] <jono> and then we can reconvene around the daemon bugs the week after
[18:19] <jono> and obviously other folks are welcome to contribute fixes too!
[18:19] <mfisch> ok
[18:19] <mfisch> are we holding this API change until then?
[18:19] <jono> cielak, that would be awesome
[18:19] <mfisch> if it gets stale due to other commits the merge will suck
[18:20] <jono> mfisch, I would like to get the API change done before cielak leaves if possible
[18:20] <jono> cielak, any chance you can review the API change today?
[18:20] <mfisch> agreed
[18:20] <jono> and then I will take a look and we can commit
[18:20] <cielak> jono: I'll do my best to
[18:20] <jono> thanks cie
[18:20] <jono> thanks cielak
[18:20] <cielak> I agree this MP has to be merged soon to avoid conflicts
[18:21] <jono> yeah, so if we all focus on this first I think this makes sense
[18:21] <mfisch> I'm flying out on Saturday and have a lot of stuff to do here, so I'll be limited availability this week too :(
[18:21] <jono> I want to dive deep on the viewer over the next week
[18:21] <jono> mfisch, np
[18:21] <mfisch> jono: the date-completed stuff is not in this merge
[18:21] <jono> if we can get these API changes finalized before you guys leave, I can focus on the viewer fine
[18:21] <jono> mfisch, ok
[18:21] <jono> we can change that later
[18:22] <jono> ok so I have one topic to discuss
[18:22] <jono> I would like to add some debugging tools in the daemon/client
[18:23] <jono> so when someone experiences a problem (e.g. the trophy not getting validated) we can ask them to run a command and it gives us all the data we need
[18:23] <mfisch> like an apport script?
[18:23] <jono> that kind of thing
[18:23] <jono> right now we often ask people to run through various steps
[18:23] <cielak> apport integration sounds quite cool
[18:24] <jono> I would just like to make the debugging experience easier for everyone involved
[18:24] <jono> any thoughts on how we do this?
[18:24] <jono> I have never written an apport script before
[18:25] <jono> would that mean someone can use: ubuntu-bug accomplishments-viewer ?
[18:25] <cielak> examining apport docs might be helpful to recognise what possibilities do we have
[18:25] <cielak> but   ubuntu-bug   would probably work
[18:25] <cielak> although
[18:26] <jono> that would be cool
[18:26] <cielak> I expect it would report bug in Ubuntu package, instead of our project :)
[18:26] <cielak> maybe this can be tuned up
[18:26] <jono> particularly someone can select the issue in the debug window
[18:26] <jono> e.g. my trophies were not validated
[18:27] <cielak> yay, that would provide an awesome experience
[18:27] <jono> indeed :-)
[18:27] <jono> what would be cool is if the following happens:
[18:28] <jono>  * someone files a bug that their trophies were not validated
[18:28] <jono>  * a script checks if they have an account on LP, checks the remove share, and posts the report to the bug
[18:28] <jono> so the entire debugging process is automated
[18:29] <cielak> hang on a second
[18:29] <cielak> why would it check for a LP account?
[18:29] <cielak> to see if the trophy should be awarded?
[18:29] <jono> I was presuming if the trophy that did not validate was an LP one
[18:29] <jono> yeah, so imagine this:
[18:30] <jono>  * the user expects his ubuntu-member trophy to be valdiated
[18:30] <cielak> oh, then this is very wrong
[18:30] <cielak> that means we include trophy scripts logic in our apport script
[18:30] <jono>  * it isnt, so he files a bug, and the apport script would check the remove share to see if the trophies are there, and check LP to see if he has an account
[18:30] <jono> cielak, no no
[18:30] <jono> I am just suggesting we explore methods of automating the debugging
[18:31] <jono> this is just an idea off the top of my head :-)
[18:31] <cielak> alright ;)
[18:31] <jono> I am just trying to think of areas in which we can avoid the IRC debugging sessions we sometimes need to have
[18:31] <jono> I dont think we should include trophy scripts in our debugging support :-)
[18:31] <cielak> yet the script could simply   ls   the trophies directory to give us an idea of what the user expects and what's not signed ;)
[18:31] <cielak> yeah ;)
[18:31] <jono> indeed
[18:32] <jono> cielak, I just wanted to present the mindset here of what we can do to make things easier for debugging
[18:32] <jono> we can maybe discuss this more when you guys return from your trips
[18:32] <cielak> okay ;)
[18:32] <jono> ok, so this is the plan so far:
[18:33] <jono>  * cielak is going to work on https://bugs.launchpad.net/bugs/1033773 and try and review the API change MP before he heads out
[18:33] <jono>  * I will focus on viewer-related bugs while you guys are away and keep on top of MPs
[18:33] <jono>  * we will discuss the debugging approach when you guys get back
[18:33] <jono> sounds like a good plan :-)
[18:33] <cielak> yeah :)
[18:34] <jono> cool
[18:34] <jono> any other topics?
[18:34]  * cielak has one more
[18:34] <jono> \sure
[18:34] <cielak> something about the daemon again, but this time more like the UI design
[18:34] <cielak> one of the things we postponed for 0.3
[18:34] <cielak> what I mean is the main notification bubble
[18:35] <cielak> which says 'You have accomplished something!'
[18:35] <jono> right
[18:35] <cielak> I guess we may need to reword it
[18:35] <jono> oh yes
[18:35] <jono> what did we discuss last time?
[18:36] <cielak> not only it looks inconsistent with Ubuntu desktop, but it appears we're dealing with the syndrome of 'talking computer'
[18:36] <jono> yes
[18:36] <jono> any thoughts on a better string to use?
[18:36] <cielak> we discussed that since there is quite a lot of options available, we'll do it for 0.3 so that translators will have time to update their work
[18:36] <cielak> yeah, quite a lot
[18:37] <cielak> obviously this has to be an affirmative statement, with a feel of 'notification'
[18:37] <jono> maybe we can collate ideas on a wiki page
[18:37] <jono> to choose the best one
[18:38] <cielak> alright, I can put my thoughts together on a wiki page
[18:38] <jono> cool
[18:38] <jono> and maybe mail the list and we can review the options
[18:38]  * janos don't really see what's so wrong with 'You have accomplished something!' ...
[18:38] <cielak> alright!
[18:39] <jono> cielak, did you want to explain to janos your concerns here?
[18:39] <janos> jono cielak you can do later, that was just me wondering out loud
[18:40] <cielak> well, since I'll do it in the e-mail anyway, maybe you'll read them there ;)
[18:40] <jono> ok cool
[18:40] <janos> yup, no prob
[18:40] <jono> alrighty
[18:40] <jono> btw, janos, the web viewer seems to be working great for me
[18:41] <jono> has imbrandon contributed the new CSS yet?
[18:41] <janos> btw i noticed meetingology has a command # - action, maybe we could tag some actionable stuff from the above?
[18:41] <janos> good question, wondering if imbrandon is around...
[18:41] <jono> he might not be online now
[18:41] <jono> yeah, I need to learn meetingology more :-)
[18:41] <jono> ok cool, I guess we will wrap it
[18:42] <jono> thanks for joining the meeting folks!
[18:42] <jono> the road to 0.3 continues!
[18:42] <jono> thanks for all of your wonderful efforts!
[18:42] <cielak> thanks everyone :)
[18:42] <jono> #endmeeting
[18:42] <meetingology> Meeting ended Thu Aug  9 18:42:35 2012 UTC.
[18:42] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-08-09-18.00.moin.txt
[18:42] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-08-09-18.00.html
[18:43] <janos> see ya, i'll be on the other chan
[18:55] <imbrandon> jono: i am


[09:09] <KrisJace> can anyone tell me how on Ubuntu Touch with Mir do I find screen DPI from command line?
[09:19] <anpok_> KrisJace: there is a tool called mirout that prints the outputs and the current active resolution on each of them
[09:21] <anpok_> the tool must be allowed to connect to a server.. so you can have it connect to u-s-c or unity8.. in the case of unity8 it may report the wrong orientation and swapped WxH on some devices..
[09:24] <anpok_> KrisJace: if you are a client with a window you would get that information in a nicer form as soon as you get displayed.. since there is a mir_surface_output_event sent.. containing the output and its dpi form factor refresh rate..
[09:38] <KrisJace> @anpok THank you!
[09:38] <KrisJace> I actually got same answer from Michael Zanetti ad Ubuntu App Dev group on Telegram
[09:38] <KrisJace> it works
[09:39] <KrisJace> also I cannot use mir_surface_output_event I'm affraid
[09:39] <KrisJace> as my apps are Gtk apps
[09:39] <KrisJace> and run in XMir
[12:23] <brunch875> Hello! My computer broke and now I'm left with a painfully slow raspberry pi (python interpreter takes 4 seconds to load) with a broken APT which can't install anything...
[12:23] <brunch875> Do you know where I could get some guides to set up the ubuntu phone to replace this?
[12:26] <brunch875> Mostly interested about setting up a container and logging into it where I can use apt. If I could redirect the display over SSH that'd be amazing as well, since this PI is choking with the kiwi
[12:27] <brunch875> I would also try the whole miracast thing but the e4.5 can't do it... right?
[14:26] <dobey> brunch875: http://askubuntu.com/a/623311/50737
[14:26] <dobey> brunch875: note that the e4.5 only has 1GB RAM and not a lot of storage space or CPU power, so probably won't actually be faster than running stuff on a rpi
[14:27] <brunch875> this rpi has 700MHz + 400MB RAM!
[14:28] <brunch875> I just managed to set up a libertine container, where I'm running finch to IRC via SSH :)
[14:32] <brunch875> What I'm trying to do right now is forward the libertine container display through SSH -Y
[14:34] <brunch875> libertine-launch -i containername has matchbox complain that DISPLAY isn't set, so it sounds like it is capable to do this
[14:35] <dobey> the problem is that launching apps through libertine starts their own X server
[14:36] <brunch875> :/ So this means I should give up doing via libertine then
[14:36] <dobey> well you can use libertine to manage the chroot
[14:37] <brunch875> if I set a chroot environment like in the askubuntu post... would it be possible to connect to it via SSH and rediret the display?
[14:37] <dobey> but you're going to have to ssh in and manually chroot into the libertine container and run whatever app with the appropriate DISPLAY=:0 set
[14:37] <brunch875> right now if I DISPLAY=:0 ssh -Y phablet@ip it will state that it wasn't possible to forward through :0
[14:37] <dobey> well DISPLAY=:0 is probably wrong
[14:38] <dobey> also see the man page about -Y and default options
[14:39] <brunch875> does it sound plausible to make this work without making the phone writable?
[14:40] <dobey> yes
[14:40] <dobey> been there done that :)
[14:42] <dobey> though ssh over wifi to phone is a bit annoying because it gets really laggy when the phone tries to go to sleep
[14:43] <brunch875> no problem, I just made it stay awake :p
[16:03] <elopio> Elleo: ping. I've sent the Esperanto layout for the keyboard. Can you please review the MP to see if I'm missing something?
[16:11] <brunch875> dobey: It seems I'm having problems forwarding X since the phone doesn't have xauth installed... do you remember having this issue at all?
[16:12] <Elleo> elopio: sure thing
[16:12] <brunch875> this is regardless of using -X or -Y. If I understood it correctly, the default settings *should* work out of the box
[16:12] <dobey> brunch875: no, but it's been a long time
[16:48] <brunch875> bingo! someone filed a bug complaining that the xauth program is missing and how he worked it around by generating an .Xauthority himself
[16:48] <brunch875> this was last friday, so I take it xauth hasn't been missing for too long
[16:51] <brunch875> https://bugs.launchpad.net/bugs/1648914
[16:51] <ubot5`> Ubuntu bug 1648914 in Canonical System Image "Add xauth for helping X forwarding scenarios" [Undecided,Opinion]
[16:59] <aca021191> im trying to install ubuntu in my tablet
[16:59] <aca021191> does  somebody know the correct channel for a monster tablet
[17:30] <elopio> Elleo: thanks!
[17:45] <taiebot> Hi, I believe focus of development is on Xenial now, so what is the status of devel-proposed is it stable enough to switch to this channel? BTW i am on mako
[17:45] <dobey> devel-proposed is not xenial and no you shouldn't run it
[17:55] <taiebot> dobey: just realised no images are build anymore on devel-proposed
[17:56] <taiebot> they all stopped on the 25th of October
[19:36] <brunch875> jesus this is more complicated than I thought. I coldn't get installation candidates of xauth so I had to apt-get download on the rpi to then get in the chroot to dpkg -i xauth and the library dependency
[19:36] <brunch875> and it works!
[19:36] <brunch875> Now the real question is how I install these things at $HOME so that the ssh daemon can use them
[19:37] <dobey> brunch875: why not just run ssh server inside the chroot instead of in the host? :)
[19:37] <brunch875> is it good enough to put $PATH and $LPATH (or however it is) in .bashrc
[19:37] <brunch875> ?
[19:38] <brunch875> yes, dobey, that's definitely what I want
[19:38] <brunch875> thanks for snapping me out
[19:38] <brunch875> how could I do this, though?
[19:38] <dobey> or just run it on a different port
[19:39] <dobey> chroot into the chroot, and install openssh-server and configure the port, and run it?
[19:39] <brunch875> :) I'm glad you know all of this and are willing to share
[19:39] <brunch875> you've helped me mountains already
[19:40] <dobey> then just ssh -p 2222 -Y or whatever and it should put you inside the chroot
[19:41] <dobey> might need to create a different user inside the chroot or bind-mount home dir or something
[19:41] <dobey> but then you can just apt away things in the chroot straight through ssh without really worrying about the host system
[19:42] <brunch875> are these binds going to go away once the base ssh shuts down?
[19:43] <dobey> mount --bind? no it has nothing to do with ssh itself
[19:43] <dobey> but it will be unmounted when you reboot or such, and the chroot ssh of course would get killed then too, and not automatically started on reboot
[19:44] <brunch875> so the chroot ssh is going to stay alive too?
[19:44] <brunch875> that's a great thing
[19:45] <brunch875> I really may want to create a non-root user inside the chroot though, since running firefox as root could be a very crazy idea
[19:45] <brunch875> knowing that the base system can be accessed from the mounted folders
[19:51] <dobey> well if you created it with libertine, i think it should already have stuff setup to run as "phablet" user, at least when run with libertine stuff; not really poked deeper into it myself
[19:55] <brunch875> Wouldn't libertine sandbox the openssh-server so it wasn't reachable from outside?
[19:55] <brunch875> I'm not too familiar with the confinement of those things
[19:59] <dobey> it depends on how it's started i guess. but in the end a chroot is just a chroot
[20:00] <dobey> it's certainly possible to run services inside the container which are accessible from the outside
[20:12] <brunch875> managed to create a user but I can't seem to give him a password so no idea how to log in as him
[20:12] <brunch875> "passwd: Authentication token manipulation error"
[20:16] <dobey> not sure, can't really help debug, sorry


[00:08] <johnc4510> The new issue of the Ubuntu Weekly Newsletter is now available:
[00:08] <johnc4510> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue150
[14:38] <nhandler> Was the "NOTE: Please let<EMAIL_ADDRESS>know too about the new meeting!" comment on the CommunityCouncilAgenda wiki page added at our request? If so, is there a reason for it?
[14:47] <tyche> nhandler: I don't see the comment you are referring to.
[14:49] <nhandler> tyche: It is a MoinMoin comment. Here is the diff https://wiki.ubuntu.com/CommunityCouncilAgenda?action=diff&rev2=1397&rev1=1396 or you can use ?action=raw
[14:50] <tyche> That was added back a while, before they regularized the CC meetings.
[14:51] <nhandler> tyche: 2009-07-13 05:23:44
[14:51] <nhandler> That is the date of that change
[14:51] <tyche> The reason it was added was because they were complaining that we weren't adding it to the Fridge calendar, and the Upcoming Meetings and Events.  And the reason we weren't adding it was because we were not mind readers.
[14:52] <nhandler> tyche: Well, it was just added (or re-added). Instead of that, (I'll talk to Daniel first) I think a reminder to update the Fridge and a link to the howto wiki page would be more beneficial
[14:52] <nhandler> Any objections?
[14:53] <tyche> Check with Daniel or someone on the CC before you add/change it.  It's their page.
[14:54] <nhandler> I will, but would the News Team be fine without an email to the mailing list about the meetings if they are added to the Fridge?
[14:54] <tyche> They're already on automatic in the Fridge/Google calendar.
[14:55] <tyche> They're set for every 2 weeks.  So the only notification we would need is if they change the schedule  or time, or something.
[14:55] <nhandler> tyche: I think the whole reason for this comment being added was that they rescheduled the meeting due to vacations. In cases like this, I think updating the fridge would be best
[14:56] <tyche> Or if they specifically want us to show that a particular meeting has been deleted for some reason.


[04:16] <mapps> hi all
[04:17] <daftykins> mornin'
[04:19] <mapps> sup!
[04:21] <daftykins> mmm not much, kicked back on the sofa
[04:27] <mapps> 2what to watch
[04:43] <mapps> did some more spanish using the app today
[04:43] <mapps> its funny..its like when you learn english 'the cat sat on the mat'
[04:43] <mapps> stuff like 'the elephants drink water'
[04:43] <mapps> lol
[04:44] <daftykins> :D
[05:05] <mapps> hm cool dwight from the office is in this new series
[05:29] <mapps> daftykins
[05:35] <mapps> still around??
[10:47] <brobostigon> morning boys and girls,
[15:38] <bujji> openmotif-2.2.3-x86_64 Notffound.failed
[15:41] <bujji> hey any one
[15:41] <bujji> openmotif22-2.2.3-x86_64 Notffound.failed
[15:42] <bujji> :popey hi
[15:57] <m0nkey_> wut?
[15:59] <penguin42> indeed
[16:47] <ali1234> penguin42: bug 1409015
[16:47] <ali1234> something weird happened on that bug
[16:47] <ali1234> some random person came along and marked it fix released, private security
[16:48] <ali1234> as far as i can tell it is neither
[16:48] <ali1234> and now the person appears to have been deleted from launchpad
[16:48]  * penguin42 can't see it either
[16:48] <ali1234> i can see it cos it's my bug
[16:48] <penguin42> can you untick the security tag?
[16:48] <ali1234> done
[16:49] <ali1234> any idea what happened here?
[16:49] <penguin42> ali1234: It sounds like a random person being random
[16:50] <ali1234> and then got deleted for being too random?
[16:51] <penguin42> maybe, or deleted themselves?  I wonder what otherstuff they broke
[16:52] <ali1234> https://dogfood.paddev.net/~ijdisabest
[16:55] <ali1234> weird :S
[16:57] <penguin42> yeh I found that as well
[16:58] <penguin42> ali1234: Can you set that back to new?
[16:58] <ali1234> done
[16:59] <ali1234> i need to check if it still happens actually
[16:59] <penguin42> hehe
[16:59] <ali1234> none of the installers have been working for like the past week but i think they are fixed now
[17:00] <penguin42> ah, I've got kubuntu 15.04 downloading at the moment
[17:00] <ali1234> zsyncing the xubuntu daily...
[17:24] <penguin42> ali1234: hmm
[17:25] <penguin42> ali1234: The install apparently worked fine, but it's failed to boot off the disc after install in a VM
[17:26] <penguin42> hmm, ok after a reset, hmm
[17:37] <ali1234> xubuntu booted okay
[17:37] <ali1234> start page is in right language
[17:38] <zmoylan-pi> can't you just change that in a setting?
[17:42] <ali1234> yes but that's not really the point?
[17:43] <penguin42> ali1234: You mean it's not remembering it from the installer?
[17:43] <ali1234> no
[17:43] <ali1234> when i reported the bug, i just went through the installer and didn't change any of the defaults (it detected UK correctly)
[17:45] <ali1234> and then in the install the start page was in arabic or something
[17:45] <ali1234> this time i did the same thing but it worked as you'd expect
[17:48] <penguin42> wacky
[17:49] <ali1234> i suspect related to the bug that was making the installer not work at all
[17:49] <ali1234> that was something to do with character maps and the ISO
[18:39] <daftykins> diddledan: i too, have creme eggs! \o/
[18:39] <daftykins> *creme egg clink*
[18:40] <zmoylan-pi> the new icky creme eggs?
[18:40] <daftykins> how do you mean? have they changed 0o
[18:41] <penguin42> they changed the chocolate to standard CDM rather than a better one they used to use
[18:41] <zmoylan-pi> they changed the recipie. there's uproar over it in uk and ireland
[18:41] <penguin42> however, I never liked them since they were always too sweet for me anyway
[18:41] <daftykins> WAT
[18:41] <daftykins> i haven't opened my box yet so i shall have to conduct research
[18:41] <zmoylan-pi> i liked them in early 80s but haven't had one for years
[18:42] <daftykins> so you practically haven't had one for as long as i've been alive :>
[18:42] <daftykins> (i'm 30 this month ;_; )
[18:42] <penguin42> daftykins: http://www.chocolatemission.net/2015/01/january-30th-cadbury-creme-egg-in-2015.html
[18:42] <zmoylan-pi> i think i had one around 2000 or so
[18:44] <daftykins> penguin42: ty sir!
[21:42] <daftykins> don't worry, i've done the necessary science... sample #1 went down just fine
[21:42] <daftykins> creme eggs are still safe
[21:44] <mecanik> hi