[13:35] <mgariepy> good morning everyone
[14:16] <highvoltage> good morning
[15:32] <vmlintu> good afternoon
[19:59] <JasonO> hello everyone


[00:00] <teward> vorlon: that be in Groovy yes
[00:00] <teward> vorlon: do we need to wait for the apt maintainer first?
[00:00] <teward> cjwatson: well it's failing multiple studio builds so it's on the radar for "this is broken hard"
[00:01] <teward> as virtually all studio packages Eickmeyer's trying to get out of proposed and NEW dep on it
[00:01] <teward> so it kind of is breaking Studio stuff :P
[00:01] <teward> haven't noticed if there's any OTHER packages of mine affected (triggering PPA builds in Groovy of xca, vmfs6-tools, nginx "soon")
[00:02] <teward> but......
[00:02] <teward> not sure if you should rollback until someone fixes it or not
[00:04] <teward> ODDLY ENOUGH the fails are only in amd64 and risc, somehow the builds for mcpdist in other archs succeeded
[00:18] <vorlon> teward: is this happening with the -proposed version of apt?
[00:19] <vorlon> since apt hasn't updated in the release pocket since July 9
[00:19] <vorlon> if so, I think we should just bounce 2.1.9 out of -proposed
[00:19] <vorlon> and let juliank look it over at his leisure
[00:24] <vorlon> teward: amd64 and riscv64 have commonality in terms of which network the builders run on, vs the other architectures
[00:27] <wgrant> teward, vorlon: Specifically, amd64 and riscv64 are talking to Apache, while the others are usually talking to Squid.
[00:27] <cjwatson> vorlon: The reports I've seen have been with apt from groovy-proposed.  I haven't done any kind of exhaustive analysis
[00:27] <cjwatson> But I think rolling back is probably appropriate here
[00:27] <wgrant> The changes in groovy-proposed look very very suspicious, and it's clearly only that version that is showing trouble.
[00:27] <wgrant> So yeah, backing 2.1.9 out of groovy-proposed seems the right path.
[00:27] <vorlon> ok, removing
[00:27] <vorlon> juliank: ^^ apt 2.1.9 removed from proposed due to the regressions it causes for package builds
[00:28] <cjwatson> Thanks.  I can do some kind of bulk retry tomorrow if nobody beats me to it before then
[00:29] -queuebot:#ubuntu-release- New: accepted bslizr [amd64] (groovy-proposed) [1.2.8-0ubuntu1]
[00:29] -queuebot:#ubuntu-release- New: accepted bslizr [armhf] (groovy-proposed) [1.2.8-0ubuntu1]
[00:29] -queuebot:#ubuntu-release- New: accepted bslizr [s390x] (groovy-proposed) [1.2.8-0ubuntu1]
[00:29] -queuebot:#ubuntu-release- New: accepted bslizr [arm64] (groovy-proposed) [1.2.8-0ubuntu1]
[00:29] -queuebot:#ubuntu-release- New: accepted bslizr [ppc64el] (groovy-proposed) [1.2.8-0ubuntu1]
[00:31] <wgrant> I'm doing it.
[00:31] <wgrant> Well, for the primary archive.
[00:31] <cjwatson> Thanks
[00:58] <teward> vorlon: all these packages are in proposed
[00:59] <teward> so if groovy-proposed builds with -proposed enabled and available I'd say "yes" to it being apt in proposed
[00:59] <teward> let me check
[00:59] <teward> 'cause i just got spammed
[01:00] <teward> apt 2.1.9
[01:01] <teward> ah good so you just yanked it
[01:01] <teward> i'm slow :)
[01:04] <teward> wgrant: so can i retrigger the mspdisp errors in Studio's builds then or is that on your radar too
[01:08] <vorlon> teward: you wouldn't have to wait on him to do it, in any case; but I've just retriggered those fwiw
[01:11] -queuebot:#ubuntu-release- New binary: mcpdisp [amd64] (groovy-proposed/universe) [0.1.2-0ubuntu1] (no packageset)
[01:24] -queuebot:#ubuntu-release- New binary: mcpdisp [riscv64] (groovy-proposed/universe) [0.1.2-0ubuntu1] (no packageset)
[01:29] <teward> vorlon: tyvm
[01:30] <teward> is apt source tracked somewhere curious what changes were made that broke this so hard
[01:30] <teward> esp. between 2.1.7 and 2.1.9 (where'd 2.1.8 go xD)
[01:30] <teward> not a pro but i want to know heh
[06:04] <juliank> vorlon: ooh failures. I need to reproduce
[06:04] <juliank> Because I removed the code masking them, as it caused other bugs
[06:04] <juliank> And now need to fix the bugs
[06:09] <juliank> cjwatson: wgrant I might actually need shell access to an instance that can trigger the data left in buffer bug. Also am I hiding actual error message? I think I am! Because data left in buffer is a server side connection closure that was not handled properly
[06:09] <juliank>  I can't reproduce any bugs locally really, these are all very connection specific.
[06:10] <juliank> Arguably they might depend on MTU, package size, and transfer speeds
[07:10] <juliank> frustrating!
[09:44] -queuebot:#ubuntu-release- Unapproved: muffin (focal-proposed/universe) [4.4.3-1 => 4.4.3-1ubuntu0.1] (no packageset)
[09:48] <cjwatson> juliank: I don't have a way to give you shell access to any of our builders
[09:48] <juliank> ack
[09:48] <cjwatson> juliank: Hopefully it can be reproduced from something else in the Canonical DC that has direct access to ftpmaster.internal:80 (may not be required, but it's possible)
[09:56] <juliank> cjwatson: The funny thing is I have another reproducer on debian, it fails like 10%
[09:56] <juliank> cjwatson: The bug only happens if headers and content are in the same packet :/
[09:56] <juliank> At least the one I see
[09:56] <juliank> I've made good progress
[10:01] <Laney> juliank: Use autopkgtest's access to scalingstack if you want, that might be close enough
[10:02] <juliank> That makes sense
[10:02] <juliank> I also need a failing build
[10:02] <cjwatson> That sounds promising.  So effectively only if your internet connection is too fast? :)
[10:02] <cjwatson> nautilus/groovy-proposed was failing I think
[10:03] <cjwatson> It's been retried now, but you could try rebuilding the same thing
[10:03] <juliank> yeah
[10:03] <juliank> I bet there's a ton more bugs
[10:03] <juliank> this fixed some https://salsa.debian.org/apt-team/apt/-/merge_requests/130/diffs?commit_id=d3ce6323d450c80bbcc8daee944271f1c0af9691
[10:03] <juliank> also this one https://salsa.debian.org/apt-team/apt/-/merge_requests/130/diffs?commit_id=4b910d12a51f812b802951cf011f5abeaf410299
[10:04] <juliank> I think I broke pipelining
[10:04] <juliank> because I stopped exiting successfully on In.IsLimit() == true
[10:04] <juliank> And this was all papered over before because apt silently retried
[10:04] <juliank> with a brand new connection
[10:05] <juliank> Still need to improve error handling a bit
[10:05] <juliank> or rather, reporting
[10:07] <seb128> cjwatson, juliank , that was not source specific, random packages were failing to get some of the debs and different ones at each retry
[10:07] <juliank> seb128: it is
[10:07] <seb128> so I think just apt build-dep for some non trivial package should be enough to trigger
[10:07] <juliank> seb128: always specific
[10:08] <juliank> it just does not appear so
[10:08] <juliank> but it depends on the pipeline and response order, and length of packets and such
[10:08] <seb128> k, well it happened like on half the packages I uploaded/synced yesterday
[10:09] <seb128> I would say it's just random and if you download enough debs from the archive you would end up hitting it
[10:09] <seb128> I'm unsure how it could be specific to a source, the source code isn't involved at this point
[10:28] <juliank> I think you currently don't see Error reading from server. Remote end closed connection, but I can't test it really, my connection is too fast
[10:37] <LocutusOfBorg> vorlon, would it be possible to hint gfs2-utils on ppc64el that has regressed in release? https://autopkgtest.ubuntu.com/packages/g/gfs2-utils/groovy/ppc64el
[11:51] <juliank> I'm fairly optimistic that this works now, I messed up the success recovery paths in the connection closure path
[11:51] <juliank> I've also rewritten the entire thing to do the same in readable
[11:52] <juliank> which meant doing code path analysis
[11:52]  * juliank wonders if there's a tool for that
[11:52] <juliank> (like, tell it which boolean variables it is allowed to toggle and give me the outputs in a table)
[11:59] <juliank> I can reproduce
[11:59] <juliank> on autopkgtest
[12:01] <Laney> ✅
[12:07] <juliank> I installed apt build-deps and I can no longer reproduce with my test, so I now download all of plasma-desktop
[12:07] <juliank> because I need to download enough files for the server to close the connection on me
[12:11] <juliank> All I can say is do not maintain 22 year old http clients
[12:13] <juliank> Fix seems to work
[12:40] <juliank> new apt landing, please stay attentive and ping me immediately if you see download errors https://launchpad.net/ubuntu/+source/apt/2.1.10
[14:17] <teward> juliank: so you fixed the 2.1.9 regression issue?  they rolled back because it broke every build on select archs :P
[14:18] <juliank> teward: yup
[14:39] <teward> juliank: cool as long as it stops erroring heh
[15:27] -queuebot:#ubuntu-release- Unapproved: accepted apport [source] (focal-proposed) [2.20.11-0ubuntu27.8]
[15:32] -queuebot:#ubuntu-release- Unapproved: rejected rpcbind [source] (xenial-proposed) [0.2.3-0.2ubuntu<IP_ADDRESS>]
[15:39] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (bionic-proposed/partner) [1:20200609.1-0ubuntu<IP_ADDRESS> => 1:20200811.1-0ubuntu<IP_ADDRESS>] (no packageset)
[15:39] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (xenial-proposed/partner) [1:20200609.1-0ubuntu<IP_ADDRESS> => 1:20200811.1-0ubuntu<IP_ADDRESS>] (no packageset)
[15:39] -queuebot:#ubuntu-release- Unapproved: adobe-flashplugin (focal-proposed/partner) [1:20200609.1-0ubuntu<IP_ADDRESS> => 1:20200811.1-0ubuntu<IP_ADDRESS>] (no packageset)
[16:04] <xnox> argh
[16:04] <xnox> isn't it dead?! =)
[16:05] <xnox> i thought 20202 was the year it will die
[16:05] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (bionic-proposed) [1:20200811.1-0ubuntu<IP_ADDRESS>]
[16:05] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (focal-proposed) [1:20200811.1-0ubuntu<IP_ADDRESS>]
[16:06] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (xenial-proposed) [1:20200811.1-0ubuntu<IP_ADDRESS>]
[16:15] <Odd_Bloke> xnox: End of the year, I think?
[16:18] <cjwatson> 20202> perhaps that typo is more true than you think
[16:21] <xnox> hahahhahahahhahahhahahhahahahhaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaahahhhhhhhhhhhhhhhhhhhhhhahahahhahahahahahhahahhahaha
[16:36] <patriciadomin> hello. I see 16.04.7rc ISO ready for testing on arm64 and amd64. Are you planning to build it for ppc64le and s390x?
[16:38] -queuebot:#ubuntu-release- New: accepted mcpdisp [amd64] (groovy-proposed) [0.1.2-0ubuntu1]
[16:38] -queuebot:#ubuntu-release- New: accepted mcpdisp [armhf] (groovy-proposed) [0.1.2-0ubuntu1]
[16:38] -queuebot:#ubuntu-release- New: accepted mcpdisp [riscv64] (groovy-proposed) [0.1.2-0ubuntu1]
[16:38] -queuebot:#ubuntu-release- New: accepted mcpdisp [arm64] (groovy-proposed) [0.1.2-0ubuntu1]
[16:38] -queuebot:#ubuntu-release- New: accepted mcpdisp [s390x] (groovy-proposed) [0.1.2-0ubuntu1]
[16:38] -queuebot:#ubuntu-release- New: accepted mcpdisp [ppc64el] (groovy-proposed) [0.1.2-0ubuntu1]
[16:40] <vorlon> LocutusOfBorg: gfs2-utils/ppc64el hinted, thanks
[16:41] <xnox> patriciadomin:  no, we do not.
[16:41] <xnox> patriciadomin:  the BootHole does not affect ppc64le nor s390x. It only affect UEFI platforms.
[16:53] <vorlon> cpaelzer: fyi after yesterday's conversation (and britney nagging me about a number of packages that I "uploaded" being stuck in -proposed too long ;), I am going ahead and rolling forward the various haskell packages that had been rolled back, after confirming they're not entangled with any current transitions.  (e.g. the haskell-gi-* stuff can't be since it was all removed from release pocket)
[16:55] <vorlon> WHY DOES REVERSE-DEPENDS OUTPUT TO STDERR
[17:07] <patriciadomin> ok thanks xnox
[17:24] -queuebot:#ubuntu-release- New binary: libnfc [s390x] (groovy-proposed/universe) [1.8.0-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: aflplusplus [amd64] (groovy-proposed/universe) [2.66c-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: libzorpll [s390x] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: libnfc [amd64] (groovy-proposed/universe) [1.8.0-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: libnfc [ppc64el] (groovy-proposed/universe) [1.8.0-1] (no packageset)
[17:27] -queuebot:#ubuntu-release- New binary: libzorpll [amd64] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:28] -queuebot:#ubuntu-release- New binary: libzorpll [ppc64el] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: wtdbg2 [amd64] (groovy-proposed/universe) [2.5-4] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: libnfc [armhf] (groovy-proposed/universe) [1.8.0-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: libnfc [arm64] (groovy-proposed/universe) [1.8.0-1] (no packageset)
[17:31] -queuebot:#ubuntu-release- New binary: libzorpll [armhf] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:31] <vorlon> not rolling forward haskell-ansi-terminal because pandoc.  not rolling forward haskell-tasty / haskell-tasty-hunit, haskell-hledger-lib, haskell-hledger, because intertwined with haskell-ansi-terminal.  not rolling forward haskell-quickcheck, because pandoc.
[17:31] <vorlon> all the rest of my rollbacks have been rolled forward again
[17:32] -queuebot:#ubuntu-release- New binary: libzorpll [arm64] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[17:44] -queuebot:#ubuntu-release- New binary: libnfc [riscv64] (groovy-proposed/universe) [1.8.0-1] (no packageset)
[17:59] -queuebot:#ubuntu-release- New binary: libzorpll [riscv64] (groovy-proposed/universe) [<IP_ADDRESS>-1] (no packageset)
[18:17] -queuebot:#ubuntu-release- New: accepted libnfc [amd64] (groovy-proposed) [1.8.0-1]
[18:17] -queuebot:#ubuntu-release- New: accepted libnfc [armhf] (groovy-proposed) [1.8.0-1]
[18:17] -queuebot:#ubuntu-release- New: accepted libnfc [riscv64] (groovy-proposed) [1.8.0-1]
[18:17] -queuebot:#ubuntu-release- New: accepted libzorpll [amd64] (groovy-proposed) [<IP_ADDRESS>-1]
[18:17] -queuebot:#ubuntu-release- New: accepted libzorpll [armhf] (groovy-proposed) [<IP_ADDRESS>-1]
[18:17] -queuebot:#ubuntu-release- New: accepted libzorpll [riscv64] (groovy-proposed) [<IP_ADDRESS>-1]
[18:17] -queuebot:#ubuntu-release- New: accepted wtdbg2 [amd64] (groovy-proposed) [2.5-4]
[18:17] -queuebot:#ubuntu-release- New: accepted libnfc [arm64] (groovy-proposed) [1.8.0-1]
[18:17] -queuebot:#ubuntu-release- New: accepted libnfc [s390x] (groovy-proposed) [1.8.0-1]
[18:17] -queuebot:#ubuntu-release- New: accepted libzorpll [ppc64el] (groovy-proposed) [<IP_ADDRESS>-1]
[18:17] -queuebot:#ubuntu-release- New: accepted libnfc [ppc64el] (groovy-proposed) [1.8.0-1]
[18:17] -queuebot:#ubuntu-release- New: accepted libzorpll [s390x] (groovy-proposed) [<IP_ADDRESS>-1]
[18:17] -queuebot:#ubuntu-release- New: accepted libzorpll [arm64] (groovy-proposed) [<IP_ADDRESS>-1]
[18:29] -queuebot:#ubuntu-release- New: accepted aflplusplus [amd64] (groovy-proposed) [2.66c-1]
[18:31] -queuebot:#ubuntu-release- Unapproved: accepted umockdev [source] (focal-proposed) [0.14.1-1ubuntu0.1]
[18:34] -queuebot:#ubuntu-release- Unapproved: accepted umockdev [source] (bionic-proposed) [0.11.1-1ubuntu0.1]
[18:38] -queuebot:#ubuntu-release- Unapproved: accepted gnome-boxes [source] (focal-proposed) [3.36.5-0ubuntu2]
[19:22] <sergiodj> hello again, archive-admin :-).  just a friendly ping to see if anyone can review telegraf, which is currently sitting at the NEW queue.  TIA
[20:39] <vorlon> node-sha.js - what incredibly terrible testsuite output
[20:40] <vorlon> I'll just look for the "should be equal" test, shall I
[21:04] <LocutusOfBorg> vorlon, ocaml-ctypes needs lwt on i386... can you please restore it?
[21:08] <vorlon> why is anything ocaml part of the i386 set?
[21:08] <vorlon> llvm-toolchain-10 build-depends on it? :P
[21:09] <vorlon> ok I'll get it in
[21:19] <LocutusOfBorg> :)
[21:33] <seb128> vorlon, did you see https://irclogs.ubuntu.com/2020/08/07/%23ubuntu-devel.html#t12:21 ? (just mentioning because you said you were looking at the package earlier)
[21:47] <vorlon> seb128: had not seen it, thanks for the link
[21:53] <seb128> vorlon, np!
[21:56] <seb128> I see that bryce also replied on the list with pointers to the upstream bug and that they commit a fix today
[21:56] <seb128> (Olivier is off this week also so don't wait on him)
[22:35] <xnox> vorlon:  cleaned up more udebs, from unused seeds, which components-missmatches looks at. Hopefully next run of components missmatches will allow more things to be demoted or removed.
[23:38] <RikMills> vorlon: hi, would you consider skiptesting kio and kconfig in proposed to get most of the KDE things through? the libreoffice armhf mess/fails are not their fault
[23:57] -queuebot:#ubuntu-release- Packageset: 55 entries have been added or removed


[03:16] <troy_s> woodwizzle
[03:16] <troy_s> probably try the text[colour]  stanza
[12:04] <coz_> evening all :)
[12:04] <BHSPitLappy> yo


[00:49] <pdtpatrick> Question - would someone please explain/help me with .deb packaging. I'm using deb helper and i've gone through the PackagingGuide.pdf -- and i still cannot understand how you move files around. For instance, if i want the .deb file when installed to have files in /etc/ and then /home/user/.filename  .. where/how do i do that ?  would this be the dh_installdeb helper script ?
[00:52] <mirabilos> you can't write files into users' homes
[02:08] <cjwatson> ScottK: I'd appreciate your thoughts on the kdelibs5-dev and pykde4 bugs I just filed in Debian for Python 3 support (#672552 and #672553, mainly the latter).  I'd love to get that into Ubuntu soon so that I can upload a Python 3 version of ubiquity.
[02:09] <cjwatson> When you get a chance, obviously.
[03:05] <nixternal> infinity: hey, one last problem with live-build. it builds the binary for me (binary/casper), however when i use that to create an ISO, and boot, i get that 'unable to open '/dev/zram0''...any pointers will be great
[03:05] <nixternal> also tried out lp.net/offspring, but that is a mess & a half, and the ubuntu-cdimage stuff seems to be private to ~canonical only :/
[03:09] <cody-somerville> nixternal, What version of live-build are you using and is your config/image available anywhere?
[03:09] <cody-somerville> nixternal, And what problems did you have with Offspring?
[03:09] <nixternal> 3.0~a24-1ubuntu32
[03:10] <nixternal> i can't get offspring to build. i have been getting a crash with offspring-master
[03:10] <nixternal> if i am correct, i need master, web, & slave. i have those 3 on the same machine
[03:11] <cody-somerville> nixternal, There's an API incompatibility with python2.7 in trunk at the moment.
[03:11] <nixternal> start slave first, then master, followed by web. at first i wasn't getting errors with master, then after a restart I was getting an IOError in regards to xml-rpc
[03:11] <nixternal> cody-somerville: right, i have installed 2.6 on my server
[03:12] <nixternal> though, damn, i didn't check if virtualenv was using 2.6
[03:13] <nixternal> for my slave/lexbuilder the status was always UNKNOWN
[03:13] <nixternal> if i could get offspring working, that would be the most perfect thing for my client. that would remove me from the equation once it is setup
[03:14] <cody-somerville> That means the master probably hasn't been successful in running.
[03:14] <cody-somerville> nixternal, Neat. I'd be happy to help you. If you could file a bug with the traceback/log, I'd be happy to look into/fix issue for you.
[03:15] <nixternal> rock on bro, I will do that. i will reinstall everything and start from scratch on my server and make sure virtualenv is using 2.6
[03:15] <nixternal> it is fine for slave & master to be the same machine right?
[03:15] <nixternal> if so, what the proper start up sequence.... slave, master, then web? or master, slave, then web? or....
[03:16] <cody-somerville> nixternal, That's fine, yes. I wouldn't necessarily recommend it though since a rogue build could cause both services to be affected (say due to doing fork bomb or something) which is especially problematic if you have a farm of builders.
[03:16] <cody-somerville> nixternal, You can start them in any sequence.
[03:16] <nixternal> ok
[03:16] <nixternal> thanks!
[03:17] <nixternal> i was going to attack you anyways for offspring as I saw your name all over it :p
[03:17] <nixternal> thanks to Daviey though for linking me to it last night
[03:17] <cody-somerville> nixternal, the load induced by a build will most certainly affect apache2 + postgresql so hosting web on same machine might be problematic fyi
[03:18] <nixternal> so you are saying it is best to have slave running on other systems? so if for starters I have i386 & amd64, they should each be on a separate machine. web & master ok to be together on the same machine though?
[03:19] <cody-somerville> nixternal, Cool. There is a mailing list FYI. It's very low traffic currently but it'll be good for keeping up to date if there are major changes we plan to introduce / place to discuss dev + support issues.
[03:19] <nixternal> ok, i will join that so i can follow along. if this works out for me, i am building my own farm and selling access to clients then :)
[03:21] <cody-somerville> nixternal, web + master should be fine to be on same machine yes load wise. However, in our setup we have master on it's own machine where we also host the NFS server for storing the results - this is because master obviously requires access to slaves and we don't want our assets or slaves to be compromised so we keep them tightly firewalled and thus if web host gets compromised in some fashion it isn't as big of a deal.
[03:22] <cody-somerville> as for i386 & amd64, you can just have single amd64 host and it can build both those arches
[03:22] <nixternal> yeah, but for load i thought about separating them
[03:23] <nixternal> oh, my live-build config, let me paste that if you are still interested in looking at it
[03:23] <cody-somerville> sure thing. if you can put image somewhere too that would be even better and I'll try it out myself to see whats wrong.
[03:24] <cody-somerville> nixternal, re: load, in that case I would just have two machines both amd64 - unless you specifically want to have i386 only machine for cost or queueing priority purposes.
[03:24]  * nixternal did 'sudo lb clean' :)
[03:24] <nixternal> right
[03:24] <cody-somerville> if you run into problems, I recommend 'sudo lb clean --purge'
[03:24] <nixternal> what does purge do?
[03:24] <nixternal> i always remove cache just to be safe
[03:25] <cody-somerville> purge removes everything, including all caches. The config directory is kept.
[03:25] <nixternal> ahh
[03:27] <nixternal> cody-somerville: http://paste.ubuntu.com/982823/  my config
[03:27] <nixternal> foobar is my fake project name, so i don't give my client info away in public :)
[03:29] <cody-somerville> ah. you use auto/config (I'm not a personal fan of the feature, lol)
[03:29] <nixternal> should my config have 'noauto' added to the lb config?
[03:29] <nixternal> or, is there a config out there i can use as an example
[03:30] <nixternal> i think i snooped all of linaro & oem services for one, as well as cjwatson's 3 million bzr repos :)
[03:31] <cody-somerville> I don't have one for lb 3.x. This is fine. I'll do a build with this and see what pops out.
[03:31] <nixternal> well, it won't work with foobar, so i will message you
[04:59] <ScottK> cjwatson: I saw the Debian bugs.  I think its great you got it sorted.  yofel_ is ~close to uploading KDE SC 4.8.3 to precise, so I think he should include your changes.
[04:59] <ScottK> I'd discuss it with him.
[06:36] <vibhav> Pornview looks dead upstream, and is very crash prone, should I file a request to get it removed?
[06:49] <vibhav> Also, can https://bugs.launchpad.net/ubuntu/+source/meep/+bug/990137 be nominated for oneiric?
[08:52] <larsdues1ng>  /j #perl
[08:52] <larsdues1ng> ups :) sorry
[11:24] <larsduesing> Is ubuntu having any problems with the line "Architecture: linux-any kfreebsd-any" in debian/control ?
[11:25] <larsduesing> (upstream debian change from "Archtitecture: any")
[11:25] <larsduesing> arghs Architecture I meant :)
[11:26] <larsduesing> and this line "Depends: iputils-ping [!kfreebsd-i386 !kfreebsd-amd64]
[11:55] <chrysn> are there any ways to debug what's happening on ubuntu build servers?
[11:56] <chrysn> i'm getting errors in its build logs, but not on my own precise building vm
[14:45] <JonEdney> o/
[15:55] <melodie> hi
[15:55] <JonEdney> o/ melodie
[15:55] <melodie> hi JonEdney !
[15:59] <melodie> I would like to get feedback for a package having for name openbox-menu. It is useful when using Openbox as only environment and can also be used while having Openbox in a DM environment
[16:00] <melodie> anyone interested ?
[16:10] <Bluefoxicy> things to be aware of:  mount NOTHING anywhere except under /home
[16:11]  * Bluefoxicy mounted a drive with disk images on it under /var/vm/ and it was summarily erased even though there's no such folder and he didn't instruct it to format...
[16:11] <Bluefoxicy> The installer warns you that if there are system files in that path it'll erase them
[16:11] <Bluefoxicy> and of course just erases the whole thing >:|
[16:14] <PaoloRotolo> Hi all!
[23:15] <Bluefoxicy> Why not make locales for every application in every language, but store them in different repos?
[23:16] <Bluefoxicy> main security universe multiverse locale-en locale-de locale-es locale-jp ...
[23:16] <Bluefoxicy> and teach dpkg to depend conditionally
[23:17] <Bluefoxicy> DEPENDS: debian-locale-de ? gnome-terminal-locale-de
[23:17] <Bluefoxicy> DEPENDS: debian-locale-ja ? gnome-terminal-locale-ja
[23:17] <Bluefoxicy> etc
[23:21]  * Bluefoxicy watches the language pack installer bring in firefox-locale-ja when he doesn't have firefox anything installed
[23:28] <melodie> gn


[02:27] <nhandler> akgraner, pleia2: Did one of you touch the permissions on the fridge (see Matthias's email)
[02:28] <pleia2> not I
[02:33] <akgraner> nhandler, I haven't
[02:34]  * akgraner goes to read his email
[02:34] <nhandler> Hmm...Strange. Maybe another sysadmin did
[02:36] <akgraner> dunno - I'll email nick on his other question...
[02:36] <akgraner> as I am not sure what those settings were
[12:40] <nhandler> I also checked on the interview script, it sounds like there won't be any issues with it on the new fridge
[20:02] <akgraner> nhandler, great thank you for looking into that


[00:07] <acheronuk> mamarley: plasma 5.8.5 is in zesty staging :)
[00:10] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #763: SUCCESS in 10 min: http://kci.pangea.pub/job/mgmt_merger/763/
[00:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #84: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_discover/84/
[00:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kreport build #17: STILL FAILING in 10 min: http://kci.pangea.pub/job/yakkety_unstable_kreport/17/
[00:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #17: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/xenial_unstable_kdb/17/
[00:30] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #15: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/15/
[00:30] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #11: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kdb/11/
[00:31] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdesdk-kioslaves build #74: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/yakkety_unstable_kdesdk-kioslaves/74/
[00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #88: STILL FAILING in 20 min: http://kci.pangea.pub/job/zesty_unstable_discover/88/
[00:31] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #17: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/17/
 plasma-discover all green
 green!!
 bouncer still down?
 still refusing connections here
 or my pathetic excuse for broadband
 may look at the plasma-sdk orange tommorow, but that is mostly it for plasma I think?
 test it
 It's running on this box as I type
 I pinged mamarly on IRC
[00:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_oxygen-icons5 build #62: FAILURE in 25 min: http://kci.pangea.pub/job/zesty_unstable_oxygen-icons5/62/
 Oh, well. No IRC till morning the. Night all
[00:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #45: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/45/
[00:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #101: STILL FAILING in 30 min: http://kci.pangea.pub/job/xenial_unstable_discover/101/
[00:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-auth-handler build #46: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/zesty_unstable_ktp-auth-handler/46/
[00:43] <mamarley> acheronuk:  Thanks!  Sorry, I wasn't around earlier because I was installing an Ethernet drop in my parents' house (my Christmas present to them).
[00:47] <mamarley> At first glance, it seems to work fine, thanks!  I will let you know if I have any issues.
[00:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #241: STILL FAILING in 40 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/241/
[00:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #44: STILL UNSTABLE in 40 min: http://kci.pangea.pub/job/zesty_unstable_kopete/44/
[00:52] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #143: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_kopete/143/
[00:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktp-auth-handler build #192: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_ktp-auth-handler/192/
[00:52] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #40: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/40/
[00:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khtml build #150: STILL FAILING in 40 min: http://kci.pangea.pub/job/yakkety_unstable_khtml/150/
[00:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #47: FAILURE in 7 min 25 sec: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/47/
 Hehehehehehe I still have IRC
[01:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #89: STILL FAILING in 50 min: http://kci.pangea.pub/job/yakkety_unstable_marble/89/
[01:03] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #192: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/192/
[01:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #180: STILL UNSTABLE in 22 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/180/
[01:05] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen-icons5 build #132: FAILURE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen-icons5/132/
 what day is it?
[01:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_cantor build #145: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_cantor/145/
[01:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_blogilo build #28: FAILURE in 1 min 48 sec: http://kci.pangea.pub/job/xenial_unstable_blogilo/28/
 @CliffordTheBigRedDoggie, TUESDAY
 really?
 Yessss
 but its 1:17am
 Noooo it's 7:17 PM
 Im in the future
 Bah
[01:18] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen-icons5 build #181: FAILURE in 15 min: http://kci.pangea.pub/job/xenial_unstable_oxygen-icons5/181/
[01:24] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_cantor build #49: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/zesty_unstable_cantor/49/
[01:25] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #287: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/287/
[01:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #37: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/xenial_unstable_peruse/37/
[01:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kreport build #17: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kreport/17/
[01:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #53: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/zesty_unstable_kstars/53/
[01:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #326: STILL UNSTABLE in 29 min: http://kci.pangea.pub/job/xenial_unstable_kstars/326/
[01:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kreport build #18: STILL FAILING in 20 min: http://kci.pangea.pub/job/yakkety_unstable_kreport/18/
[01:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #60: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/60/
[01:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #56: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/56/
[01:35] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_blogilo build #29: STILL FAILING in 2 min 2 sec: http://kci.pangea.pub/job/xenial_unstable_blogilo/29/
[01:35] <marco-parillo> acheronuk: Did I see that Plasma 5.8.5 is available for testing in ZZ?
[01:36] <marco-parillo> sudo add-apt-repository ppa:kubuntu-ppa/staging-plasma ?
[01:36] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_pim-sieve-editor build #48: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_pim-sieve-editor/48/
[01:36] <marco-parillo> Sorry, but the kde bnc bouncer seems to not work for me. Webchat at home.
[01:43] <marco-parillo> 116 updates running/
[01:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kreport build #19: STILL UNSTABLE in 30 min: http://kci.pangea.pub/job/xenial_unstable_kreport/19/
[01:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #61: STILL UNSTABLE in 50 min: http://kci.pangea.pub/job/zesty_unstable_marble/61/
[01:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libkipi build #119: STILL UNSTABLE in 28 min: http://kci.pangea.pub/job/yakkety_unstable_libkipi/119/
[01:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #33: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_peruse/33/
[01:45] <marco-parillo> Re-booting
[01:46] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_oxygen-icons5 build #63: STILL FAILING in 21 min: http://kci.pangea.pub/job/zesty_unstable_oxygen-icons5/63/
[01:53] <marco-parillo> ZZ with Plasma 5.8.5 seems ok to me on real HW. Re-booted. Ran kinfocenter, dolphin, rekonq, firefox, muon discover, with nothing immediatly obvious.
[01:54] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_cantor build #251: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/xenial_unstable_cantor/251/
[01:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #166: STILL UNSTABLE in 51 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/166/
[01:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_marble build #77: STILL UNSTABLE in 51 min: http://kci.pangea.pub/job/xenial_unstable_marble/77/
[01:55] <marco-parillo> Well, other than spellchecking in firefox with IRC webchat anyway.
[01:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_oxygen-icons5 build #182: STILL FAILING in 23 min: http://kci.pangea.pub/job/xenial_unstable_oxygen-icons5/182/
[01:58] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_oxygen-icons5 build #133: STILL FAILING in 25 min: http://kci.pangea.pub/job/yakkety_unstable_oxygen-icons5/133/
[02:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_marble build #90: STILL FAILING in 42 min: http://kci.pangea.pub/job/yakkety_unstable_marble/90/
[02:07] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #240: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/240/
[02:07] <marco-parillo> FF spell-checking had nothing to do with the upgrade. I just forgot to do the about:config thing in ZZ.
[02:07] <marco-parillo> All is good for whenever you want to call for testers.
[02:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_khtml build #151: STILL FAILING in 42 min: http://kci.pangea.pub/job/yakkety_unstable_khtml/151/
[02:11] <mparillo> konversation works fine with Plasma 5.8.5, now that the kde bnc bouncer is back.
[02:12] <mparillo> !testers
[02:13] <mparillo> If anybody has a throw-away VM, spare partition, or otherwise unused computer around, you can test Plasma 5.8.5 on ZZ. sudo add-apt-repository ppa:kubuntu-ppa/staging-plasma
[02:15] <mparillo> Topic is already current.
[02:25] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:25] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_discover build #85: FIXED in 51 min: http://kci.pangea.pub/job/yakkety_unstable_discover/85/
[02:25] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_discover build #89: FIXED in 41 min: http://kci.pangea.pub/job/zesty_unstable_discover/89/
[02:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #45: STILL UNSTABLE in 1 hr 9 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/45/
[02:42] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #26: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/26/
[02:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #242: STILL FAILING in 1 hr 18 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/242/
[02:43] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_discover build #102: FIXED in 35 min: http://kci.pangea.pub/job/xenial_unstable_discover/102/
[03:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-common-internals build #253: STILL UNSTABLE in 35 min: http://kci.pangea.pub/job/xenial_unstable_ktp-common-internals/253/
[03:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #27: STILL UNSTABLE in 1 hr 58 min: http://kci.pangea.pub/job/xenial_unstable_krita/27/
[03:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #48: STILL UNSTABLE in 2 hr 49 min: http://kci.pangea.pub/job/zesty_unstable_krita/48/
[03:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #25: STILL UNSTABLE in 2 hr 49 min: http://kci.pangea.pub/job/yakkety_unstable_krita/25/
[03:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #153: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/153/
[03:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemmodels build #60: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/zesty_unstable_kitemmodels/60/
[04:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #61: FAILURE in 5 min 20 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/61/
[04:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #45: FAILURE in 6 min 17 sec: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/45/
[04:26] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #63: FAILURE in 6 min 17 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/63/
[04:27] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #43: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/43/
[04:27]  * DarinMiller reporting in - ZZ + plasmas-taging working fine here.
[04:30] <DarinMiller> I never saw any of the issues reported in the plasma 5.8.5 bug fix list so all I can report is everything is working very well. Nice to see everything stabilizing!
[04:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_korganizer build #45: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_korganizer/45/
[04:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #64: STILL FAILING in 4 min 39 sec: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/64/
[04:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #62: STILL FAILING in 5 min 42 sec: http://kci.pangea.pub/job/zesty_unstable_kmail/62/
[04:37] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #46: STILL FAILING in 5 min 37 sec: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/46/
[04:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_mailcommon build #44: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_mailcommon/44/
[05:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #29: STILL FAILING in 13 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/29/
[05:24] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_pimcommon build #30: STILL FAILING in 14 min: http://kci.pangea.pub/job/yakkety_unstable_pimcommon/30/
[05:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #49: FAILURE in 6 min 43 sec: http://kci.pangea.pub/job/xenial_unstable_kmail/49/
[05:35] <tsimonq2> https://trello.com/c/lOiMIMAJ
[05:35] <tsimonq2> PACKAGING TASK ^^^^
[05:40] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmail build #50: STILL FAILING in 4 min 36 sec: http://kci.pangea.pub/job/xenial_unstable_kmail/50/
[07:01] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-sdk build #707: FAILURE in 7.7 sec: http://kci.pangea.pub/job/merger_plasma-sdk/707/
[07:04] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:04] -kubuntu-ci:#kubuntu-devel- Project merger_plasma-sdk build #708: FIXED in 12 sec: http://kci.pangea.pub/job/merger_plasma-sdk/708/
[07:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #288: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/288/
[07:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kbookmarks build #183: FAILURE in 45 min: http://kci.pangea.pub/job/yakkety_unstable_kbookmarks/183/
[07:29]  * acheronuk yawns
[07:32] <valorie> morning, rik
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kbookmarks build #184: FIXED in 8 min 41 sec: http://kci.pangea.pub/job/yakkety_unstable_kbookmarks/184/
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-integration build #57: FIXED in 10 min: http://kci.pangea.pub/job/zesty_unstable_plasma-integration/57/
[07:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ksysguard build #56: FIXED in 10 min: http://kci.pangea.pub/job/zesty_unstable_ksysguard/56/
[07:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-sdk build #57: STILL UNSTABLE in 11 min: http://kci.pangea.pub/job/zesty_unstable_plasma-sdk/57/
[07:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_oxygen build #46: FIXED in 16 min: http://kci.pangea.pub/job/zesty_unstable_oxygen/46/
[07:44] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-workspace build #85: FIXED in 21 min: http://kci.pangea.pub/job/zesty_unstable_plasma-workspace/85/
[07:45] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-sdk build #181: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-sdk/181/
[07:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[07:56] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_breeze build #54: FIXED in 11 min: http://kci.pangea.pub/job/zesty_unstable_breeze/54/
[08:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:02] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #47: FIXED in 11 min: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/47/
[08:08] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdepim-addons build #65: FIXED in 17 min: http://kci.pangea.pub/job/zesty_unstable_kdepim-addons/65/
[08:08] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:08] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmail build #63: FIXED in 17 min: http://kci.pangea.pub/job/zesty_unstable_kmail/63/
[08:09] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-sdk build #289: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/xenial_unstable_plasma-sdk/289/
[08:13] <lordievader> Good morning
[08:25] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:25] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwin build #69: FIXED in 28 min: http://kci.pangea.pub/job/zesty_unstable_kwin/69/
[08:26] <acheronuk> morning all :)
[08:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_khotkeys build #58: FIXED in 9 min 48 sec: http://kci.pangea.pub/job/zesty_unstable_khotkeys/58/
[08:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_powerdevil build #27: FIXED in 9 min 48 sec: http://kci.pangea.pub/job/zesty_unstable_powerdevil/27/
[08:39] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #68: FIXED in 14 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/68/
[08:44] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmenuedit build #42: FIXED in 9 min 53 sec: http://kci.pangea.pub/job/zesty_unstable_kmenuedit/42/
[09:11] <soee_> o/
[09:22] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #103: STILL FAILING in 18 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/103/
[09:39] <acheronuk> yofel: what is this doing? what test? http://kci.pangea.pub/job/zesty_unstable_plasma-desktop/62/console
[09:40] <acheronuk> BBL
[09:43] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-desktop build #62: NOW UNSTABLE in 1 hr 18 min: http://kci.pangea.pub/job/zesty_unstable_plasma-desktop/62/
[09:43] <acheronuk> oh, qml deps
[09:43] <acheronuk> NM
[09:46] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_messagelib build #104: STILL FAILING in 19 min: http://kci.pangea.pub/job/yakkety_unstable_messagelib/104/
[13:29] <BluesKaj> Hi all
[14:05] <mparillo> Hi BluesKaj. Plasma 5.8.5 in ZZ with -staging is solid for me.
[14:10] <BluesKaj> Hi mparillo, ok thanks for the heads up
[14:18] <BluesKaj> mparillo, just ran staging-plasma. any other ppas relevant?
[14:20] <acheronuk> staging-frameworks if you are not running with zesty proposed enabled
[14:23] <BluesKaj> no proposed
[14:43] <mparillo> I must have already upgraded frameworks from -staging. When I re-enabled framework-staging, I had no updates. kinfocenter reports I am on 5.28
[14:44] <acheronuk> that is the correct version, yes
[14:44] <mparillo> TY acheronuk.
[14:51] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #34: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_peruse/34/
[14:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_peruse build #16: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_peruse/16/
[14:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #38: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/xenial_unstable_peruse/38/
[15:37] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_peruse build #17: FAILURE in 4 min 12 sec: http://kci.pangea.pub/job/yakkety_unstable_peruse/17/
[15:37] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #39: FAILURE in 4 min 41 sec: http://kci.pangea.pub/job/xenial_unstable_peruse/39/
[15:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #35: FAILURE in 5 min 11 sec: http://kci.pangea.pub/job/zesty_unstable_peruse/35/
[15:39] <clivejo> acheronuk: ^
[15:44] <acheronuk> clivejo: I know. result of a merge that typically chose not to conflict
[15:45] <clivejo> merge with what?
[15:45] <clivejo> Debian dont have it?
[15:46] <acheronuk> KCI merging our unreleased WIP zesty_archive branch
[15:47] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_peruse build #18: STILL FAILING in 4 min 49 sec: http://kci.pangea.pub/job/yakkety_unstable_peruse/18/
[15:47] <clivejo> peruse conflict?
[15:47] <clivejo> or newstuff?
[15:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #40: STILL FAILING in 5 min 5 sec: http://kci.pangea.pub/job/xenial_unstable_peruse/40/
[15:48] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #36: STILL FAILING in 5 min 16 sec: http://kci.pangea.pub/job/zesty_unstable_peruse/36/
[15:52] <acheronuk> clivejo: peruse on the 'optional' newstuff qml module
[15:53] <acheronuk> there is a fix for unstable building, restoring it for that
[15:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_peruse build #19: NOW UNSTABLE in 9 min 46 sec: http://kci.pangea.pub/job/yakkety_unstable_peruse/19/
[15:57] <acheronuk> just KCI being REALLY helpful today by merging the change not wanted in unstable cleanly, and then auto-retrying the resultant failure
[16:01] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_peruse build #37: NOW UNSTABLE in 13 min: http://kci.pangea.pub/job/zesty_unstable_peruse/37/
[16:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_peruse build #41: NOW UNSTABLE in 14 min: http://kci.pangea.pub/job/xenial_unstable_peruse/41/
[19:03] <mparillo> wxl: The *package* konversation - 1.6.2-0ubuntu1 is in ZZ https://bugs.launchpad.net/ubuntu/+source/konversation/+bug/1635911/comments/6 but help about konversation says Version 1.6-branch #4910 in ZZ. I assume that is equivalent to 1.6.2, but (broader question, maybe) especially for KDE Apps, can the version numbers in the packages match the announced version numbers, or, as I suspect, is there a subtlety I am missing.
[19:03] <wxl> mparillo: yep. said that in the email :)
[19:04] <wxl> you're asking how the .2-0ubuntu1 version differs from the .2 version?
[19:05] <mparillo> I thought your e-mail was primarily about SRUing it to YY. I was wondering how the package number matches the upstream number in ZZ, but help about has its own way of versioning.
[19:05] <wxl> help about says what?
[19:05] <wxl> and you're referring to yakkety or zesty?
[19:07] <clivejo> well that source is from here - http://download.kde.org/stable/konversation/1.6.2/src/
[19:07] <tsimonq2> AFTERNOON CLIVE :DDDD
[19:08] <clivejo> maybe the developer forgot to set the version from the help menu
[19:08] <clivejo> Hi Simey
[19:08] <tsimonq2> clivejo: How are you?
[19:08] <clivejo> narfed off
[19:08] <clivejo> you?
[19:08] <tsimonq2> Narf?
[19:08] <tsimonq2> Pretty good. :)
[19:09]  * sick_rimmit Narfed here too
[19:09] <tsimonq2> What's narf mean?
[19:09] <tsimonq2> o/ o/ o / o  oo/ / // / / sick_rimmit
[19:09] <sick_rimmit> \o/ Yo!!
[19:10] <clivejo> narfed is family friendly alternative to the strong language which conveys my true mood
[19:10] <sick_rimmit> For me it means, I have been wrangling with kdev-xdebug for 2 days, and further away a fix than when I started
[19:11] <sick_rimmit> I finally find myself in a forest of deprecated KDE4 CMake Macros, with no leads on what their replacements might be under KF5
[19:11] <mparillo> In ZZ, Help > About Konversation > Version says: Version 1.6-branch #4910
[19:11] <sick_rimmit> Frankly!!!
[19:12] <sick_rimmit> I am Narfed!!
[19:12] <sick_rimmit> Pah!
[19:12] <clivejo> mparillo: same here
[19:12] <clivejo> but that's using the official source code
[19:13] <wxl> what does 1.6.1 say? or any of the point release versions for that matter?
[19:20] <mparillo> I never noticed what 1.6.1. said, and if clivejo separately compiled from upstream source, I guess all I was doing was idly complaining in the wrong place.
[19:20] <acheronuk> xdebug?
[19:20] <sick_rimmit> Yes
[19:20]  * acheronuk has a look
[19:21] <clivejo> sick_rimmit: https://xdebug.org/
[19:21] <sick_rimmit> But, I'm about to jump out the window
[19:21] <wxl> seems version.h is set right https://cgit.kde.org/konversation.git/tree/src/version.h?h=v1.6.2&id=bd0add0e9f59eb3fc750d745364f65a06abdbb67
[19:22] <sick_rimmit> I got this far
[19:22] <sick_rimmit> https://techbase.kde.org/KDevelop5/KDevPlatformPluginExample
[19:22] <sick_rimmit> Which I just a few minutes ago found, but it won't build either!
[19:23] <sick_rimmit> I was hoping to steel it's CMakeLists.txt file to get my build working, but I've got something misconfigured with my QT Env
[19:23] <acheronuk> sick_rimmit: so the kdev-xdebug plugin in kde git doesn't work for latest kdevelop?
[19:24] <sick_rimmit> It doesn't appear to be available under Kubuntu
[19:24] <sick_rimmit> and the Kdevelop5 PPA doesn't have a build of it
[19:24] <sick_rimmit> Which is what I was trying to solve
[19:24] <acheronuk> so this needs building? https://cgit.kde.org/kdev-xdebug.git/
[19:25]  * sick_rimmit checks
[19:25] <sick_rimmit> Yes that's correct
[19:25] <wxl> and strangely version.h is what main.cpp uses to set the application version
[19:25] <wxl> that said, it seems like something might not be working right
[19:25] <wxl> since you found the bug, you have to report it upstream, mparillo
[19:25] <acheronuk> or porting maybe
[19:26] <clivejo> acheronuk: I kinda made a start - https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdev-xdebug
[19:26] <clivejo> but got railroaded by krita and kdevelop
[19:26] <sick_rimmit> If I can get this up and running, I have a Full C, C++, Python, PHP tool chain, with Virtual Box running LAMP Server, with Xdebug enabled.
[19:26] <sick_rimmit> This would be a fabulous Web Dev environment
[19:27]  * sick_rimmit Thanks clivejo for making a start
[19:28] <sick_rimmit> Maybe I should not work locally, and try to fix it on the KCI... or perhaps in a Pbuilder env
[19:28] <clivejo> sick_rimmit: I dont think it can be fixed!
[19:28] <clivejo> its designed for Kdevelop 4
[19:28] <clivejo> needs to be ported to work with Kdevelop5
[19:28] <acheronuk> yes, was just looking and the cmakelists is KDE4
[19:28] <clivejo> well thats my understanding anyways
[19:28] <sick_rimmit> I made quite a few porting changes,
[19:29] <acheronuk> which is why I said "porting"
[19:29] <sick_rimmit> follwing the KDE guides
[19:29] <acheronuk> well, that's kde development rather than packaging
[19:29] <sick_rimmit> All the work looks like it would happen in CMakeLists.txt
[19:29] <sick_rimmit> The rest of the code looks good.
[19:30] <sick_rimmit> I scanned the headers for the requesite QT stuff, and there was nothing there
[19:30] <sick_rimmit> I have no answer for the KDE4 macro's however
[19:31] <acheronuk> maybe have a word with the regular committers to that repo? see if they have done any prelim porting work that hasn't gone in a branch yet?
[19:31] <mparillo> https://bugs.kde.org/show_bug.cgi?id=374264
[19:33] <sick_rimmit> acheronuk: I think I'll take that advice, this is too hard for me :-(
[19:34] <acheronuk> sick_rimmit: I can usually package what others have ported, but from ground up porting of the base code is probably too much for me right now as well
[19:36] <sick_rimmit> acheronuk: Alright, I will drop Kevin Funk a line, see if he can help.
[19:36] <mparillo> Just upgrading ZZ and I got this: dpkg: error processing archive /tmp/apt-dpkg-install-3SfKGM/0-libkpmcore4_3.0.0-1_amd64.deb (--unpack):  trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/plugins/libpmdummybackendplugin.so', which is also in package partitionmanager 1.2.1-0ubuntu1
[19:43] <acheronuk> kfunk: do you know if anyone has done prelim work for getting kdev-xdebug working with kdevelop 5?
[19:45] <clivejo> another Debian sync - https://launchpad.net/ubuntu/+source/partitionmanager/3.0.0-1
[19:46] <tsimonq2> clivejo: I know, that bugged me when I saw it
[19:47] <acheronuk> not even got a git repo for that? just an ancient bzr branch?
[20:15] <clivejo> the xdebug plugin does take some working around to install. you need a few other plugins before it will compile. you need kdev-php, kdev-executebrowser, kevelop-pg-qt before kdev-xdebug will have all the necessary components.
[20:17] <acheronuk> fun!
[21:06] <acheronuk> wxl: any idea how we might debug the tests running in python here? https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204
[21:08] <acheronuk> In LP builds, they hang indefinitely when calling a particular c++ function/extension or however you phrase it
[21:08] <acheronuk> whereas building in local sbuild etc, all is fine
[21:41] <acheronuk> we can't do any new frameworks until that gpgme builds in the archive. blocks new kde applications as well
[22:50] <wxl> acheronuk: isn't there an option to build with eht ubuntu system? like buildd or something??
[22:54] <acheronuk> wxl: maybe, but I would still need to debug in some way those hanging tests
[22:54] <wxl> acheronuk: well that may be helpful to some degree
[22:55] <wxl> --debootstrapopts --variant=buildd
[22:55] <wxl> if you can't reproduce the failure on your own machine, that might be interesting
[23:11] <acheronuk> wxl: using the LP chroot from sbuild-launchpad-chroot, builds are successful. no hangs
[23:12] <wxl> yeah that might be something to mention on the bug report. that doesn't sound right. something wrong with the build machinery? maybe get the lp team involved???
[23:14] <acheronuk> I think Colin at least is away until after new year. I'll so some more poking around


 Can it run Android?
 @AdamOutler, I am sure it could if someone put the effort to Port it over
 It might
 @KMyers blast you I'm looking at pixelbooks now
 Worst email request auto response ever.
 @RazPi, Want to try a Chromebook to see if it works for you?
 @KMyers I know I like the form factor of the pixelbook, it's the thinnest next to the MacBook with a good keynoard, the only other concern is my ability to wipe it and put Linux on it natively
 @RazPi, You could but ouch... The matebook may be better suited for that. Of course the keyboard on the Pixel book is by far the best I have ever used
 Oh wow it supports external gpu
 I didn't even know this existed
 Would need to test the keyboard
 See if any of the Microsoft stores carry them online. May be a fun day trip
 Yeah!
 It ticks the right boxes though, i5/i7, nvme, eGPU, and supposedly a good keyboard
 It is also on the thin side as well
 Yes, I wish there was an ultra small model though, I'll need a different backpack
 @RazPi, It is hard to find something that will tick all boxes
 The build quality and thinness of the pixelbook is what was drawing me in
 I'm happy with the form factor of the Mac. I'm just not happy it's a Mac 😭
 Upsetting that they broke Linux installation on it
 I’m happy with my Mac
 And happy with osx
 I spent an 2-3hours on someone’s laptop in the office that was running Ubuntu and needed to use virtual box to test and verify some networking stuff across multiple vms and the host on bridge mode
 Without going to the complexity of it all... it was a nightmare
 I wonder if Google's Alt-OS implementation will allow booting of Linux officially as well as Windows on the Pixelbook. It would in theory allow you to use the eGPU via thunderbolt
 I was extremely surprised as well as I am surely an Ubuntu fan
 Just this was one frustrating occasion
 @ghbd0wn, That should not be too hard to setup but I do understand. We had a policy at work that if I wanted to use anything but Windows, I would need to support myself as I could not go to the desktop support team if something did not work correctly. Fortunately I am pretty good with figuring out things
 This was a mess
 @KMyers, i'm extremely tempted to switch it to dev... but i'm using it as my work machine lately, so don't want to mess it up
 Your it support team is our clients.... we are the it for the it guys
 Joel. Are you at work?
 yes
 Please report to HR
 😂
 fool me once...
 Lol
 @ghbd0wn, I have actually been using ChromeOS as my daily driver. It is pretty much able to run anything I thorw at it
 except kdnlive :-P
 though that might be changing soon
 @Ivoriesablaze, In my defense, it did run and it is not something I use too often.
 haha
 @ghbd0wn, Well that was the first problem. Virtual box is nobody's friend.
 Oh my bad I read that wrong
 I thought it was testing a network from inside virtual box
 @ghbd0wn, Use pfSense in Bridge mode and set up a virtual network.   The rest of the machines should be connected to the virtual network.   I've done something similar before
 I have a virtual network set up now.  pfSense is set to forward port 22, 443, and 80 to a machine in the virtual network.  That machine then distributes Apache vhost requests to the other machines.
 @RazPi - I may go over to Ungergrounds later tonight to get some work done. I think I need a change of venue to focus
 Might join, let me know when you head over
 It will likely be after 6
 @KMyers, What! A fun day trip.... Microsoft store.... Where is Keith!?
 @govatent, Is it a crime to remove Windows and liberate machines?
 I remember when people were jail breaking ios devices when the pdf exploit was around
 In the stores
 Plug in some usb sticks and turn them on.
 @RazPi - I think I am going to head to Undergrounds in a few minutes to try to beat rush hour traffic
 Ok, I'll come after rush hour I think
 Ok
 Does it end after 6 or 7?
 Around 6
 I have arrived


[16:52] <aikidouke> is there a community qa meeting today?
[16:53] <wxl> aikidouke: yep, in about 5 min
[16:53] <aikidouke> hey wxl! :) thanks
[16:53] <wxl> np aikidouke :)
[16:58] <voxoph> how does this work
[16:58] <voxoph> the comunity qna
[17:00] <balloons> you ask us questions and we answer them :-)
[17:00] <voxoph> cool :)
[17:01] <voxoph> I was wondering, does ubuntu plan on updating UI/ UX in the future?
[17:01] <elfy> balloons: normal protocol QUESTION: foo ?
[17:01] <mhall119> elfy: yup
[17:01] <mhall119> waiting for everyone to get on the hangout, then we'll start
[17:01] <voxoph> okay
[17:01] <elfy> QUESTION : Up to early December last year I often went to https://jenkins.qa.ubuntu.com/view/Ubiquity/view/Xubuntu/ to check how my images were faring - it gave some indication of whether an image at least got through basic testing - that is now still showing fails from over 5 months ago- what gives - any plans to get visible reports back
[17:02] <elfy> QUESTION : A while back Canonical made the decision to not take part during milestones until the Final Beta, while that's great for Ubuntu I'm sure - it makes things less certain for flavours who do take part. Often during the last cycle or two things have failed which do so for Ubuntu too - but it's left to people like me (more interested in Xubuntu) to flag Ubuntu issues affecting flavours. That said - I have had nothing but help from the
[17:02] <elfy> likes of infinity, cyphermox, pitti, Laney and others when I have shouted. Is the Final Beta only going to continue?
[17:02] <elfy> QUESTION : When you all get really excited about Snappy - is that going to mean that flavours not going that way get sidelined, what's going to happen if we're worrying about something *Ubuntu* isn't?
[17:02] <elfy> :)
[17:02] <mhall119> elfy has been saving these up
[17:02]  * elfy got asked :p
[17:03] <aikidouke> QUESTION: How long do we expect Unity 7 to be maintained?
[17:03] <elepants> is it on? i can't see teh videoh
[17:03] <ChloeWolfieGirl> I cnat see either
[17:03] <elepants> maybe we blind  :(
[17:03] <elepants> OMG WE BLIND X-(
[17:04] <mhall119> it hasn't started yet
[17:04] <elepants> so we no blind?
[17:04] <elepants> pheww
[17:04] <balloons> starting up now :-)
[17:04] <mhall119> going live now
[17:05] <aikidouke> QUESTION: How will packaging things like non-free video drivers work with snappy?
[17:05] <Gralak> QUESTION: Please tell, will MX4 be available in June in Europe? When will be another flash sale in China?
[17:06] <elepants> QUESTION: how to install mir on ubuntu snappy core?
[17:07] <DS-McGuire> QUESTION: What happened to the new design for the headers on Ubuntu Touch. One day they were and the next they were gone.
[17:08] <elepants> QUESTION: is Snappy Ubuntu Core Fun Pack available for sale?
[17:09] <wxl> QUESTION: is there going to be any more organized, official community testing for Touch/Phone beyond exploratory testing like there is for every other image? :)
[17:09] <Gralak> QUESTION: Please tell, will MX4 be available in June in Europe? When will be another flash sale in China?
[17:09] <wxl> Gralak: please, ask only once.
[17:10] <DS-McGuire> Loving the banter! :L
[17:10] <aikidouke> QUESTION:If he colors the hair and the beard, is that convergance? :)
[17:10] <wxl> aikidouke: HAHAHAH
[17:11] <wxl> argh brb
[17:13] <DS-McGuire> QUESTION: WHEN CAN I IN THE UK GET AN UBUNTU MX4?
[17:13] <DS-McGuire> Opps, sorry about the caps
[17:14] <DS-McGuire> QUESTION: How long after applying for an Ubuntu membership should I expect to hear something back from it?
[17:14] <Gralak> QUESTION: Please tell, will MX4 be available in June in Europe? When will be another flash sale in China?
[17:15] <mhall119> any QA/CI/Testing questions, please get them in now before it's too late
[17:15] <elfy> DS-McGuire: are you on https://wiki.ubuntu.com/Membership/Boards
[17:16] <DS-McGuire> elfy, No not yet, I need more testimonials for my wiki: https://wiki.ubuntu.com/daniel-mcguire351
[17:16] <elfy> DS-McGuire: right - so once you have those, the board meets twice a month :)
[17:17] <DS-McGuire> elfy, Thanks a lot! I am suppose to have at least two, yes?
[17:19] <elfy> mhall119: so where's Daniel and Nick reading these questions from?
[17:19] <mhall119> elfy: the questions we're answering here?
[17:20] <elfy> I guess - can't see the questions they're answering :p
[17:20] <mhall119> elfy: I'm skipping around from what was asked in here
[17:20] <mhall119> trying to hit the QA related ones first
[17:20] <elfy> mmm
[17:20] <balloons> elfy, :-) i have a feed straight into my brain from irc
[17:20] <mhall119> elfy: did I miss one?
[17:20] <balloons> always running ;p
[17:21] <mhall119> cat /dev/random > balloons
[17:21] <elfy> mhall119: well I don'tknow how many where in here before mine
[17:21] <mhall119> none before you
[17:21] <elfy> mmm
[17:21] <elfy> well I missed mine then I guess somehow
[17:22] <mhall119> elfy: your first 2 were answered first
[17:22] <wxl> stupid customers interrupting my uoa session
[17:22] <wxl> what did i miss?
[17:22] <elfy> mhall119: is this recorded?
[17:22] <mhall119> elfy: yes, it'll be on ubuntuonair.com for a while
[17:22] <elfy> I'll see if I can hear the answers then :)
[17:22] <mhall119> elfy: or http://www.youtube.com/watch?v=fBeRaSjqrmg anytime
[17:23] <mhall119> elfy: I summarized the questions, rather than reading them out fully
[17:23] <elfy> mhall119: I had --verbose ...
[17:24] <wxl> QUESTION: same question about Touch above for Snappy. tl;dr how can average joes and janes contribute to testing much in the way that testing for desktop images has a low point of entry?
[17:24] <wxl> mhall119: FIELD TRIP :)
[17:26] <wxl> …raspberry pi TWO
[17:28] <balloons> any last minute questions for us QA folks?
[17:30] <ChloeWolfieGirl> QUESTION: will snappy snap at us? ;-;
[17:30]  * wxl facepalms
[17:30] <Kamilion> Negative; it will snapshot at you.
[17:31] <mhall119> in soviet Ubuntu, snappy packages you :)
[17:31]  * wxl groans
[17:31] <mhall119> I'm here all week :)
[17:31]  * Kamilion throws some change in the hat
[17:31]  * wxl takes mhall119's wife
[17:32] <ChloeWolfieGirl> beautiful mhall119
[17:32] <wxl> QUESTION: what about tests in Common Lisp? XD
[17:32] <Kamilion> QUESTION: What about tests for Xen?
[17:32] <Kamilion> Aw. Too late.
[17:33] <wxl> well, thanks everyone
[17:34] <Kamilion> QUESTION: when will we see something like the casper livecd ISO for snappy?
[17:35] <wxl> QUESTION: how exactly do flavors start integrating Snappy? taking all their particular packages and making Snaps out of them?
[17:38] <Knightmare> QUESTION: Is there any development that can be done for the phone in python?
[17:39] <balloons> thanks for all the questions guys! As we said, #ubuntu-quality is the place if you ever want to chat with myself or anyone from the QA team :-)
[17:39] <Gralak> QUESTION: Please tell, will MX4 be available in June in Europe? When will be another flash sale in China?
[17:39] <wxl> Gralak: he just answered.
[17:39] <elepants> mhall119: fun pack https://twitter.com/adzankich/status/599298402644439041
[17:40] <ChloeWolfieGirl> QUESTION: How will canonical advertise Ubuntu Touch and Ubuntu desktop to the public to make them more aware of ubuntu?
[17:40] <wxl> Kamilion: he's answering your question btw
[17:41] <Kamilion> I'm watchin'.
[17:41] <wxl> ko
[17:41] <DS-McGuire> QUESTION: Do you know weather the minimum price of an app in the store drop to something lower? I want to charge a small fee for apps I am creating but 1.99 is too much to ask.
[17:42] <Kamilion> Aye -- appliance images, I currently use casper's TORAM to load the squashfs on boot from the ISO for my xen project.
[17:42] <ChloeWolfieGirl> QUESTION: Do you know if/when we'll get bitcoin support in the store and could you intergrate the payment with a bitcoin app?
[17:43] <wxl> oh man i am so making a lubuntu snappy image
[17:43] <wxl> wanna help, Kamilion ?
[17:43] <Kamilion> Sure.
[17:43] <wxl> i got a pi 2 that i'd love to put it on
[17:43] <DS-McGuire> Stream down?
[17:43] <Kamilion> froze for me too.
[17:43] <Kamilion> and it's back.
[17:43] <wxl> DS-McGuire: buffering
[17:44] <DS-McGuire> back!
[17:44] <ChloeWolfieGirl> QUESTION: What will happen to apps I paid for in the current ubuntu store with unity8 and the new store?
[17:45] <wxl> QUESTION: is there any documentation anywhere about making a flavor Snappy image?
[17:45] <wxl> shoot work calls brb
[17:47] <Gralak> QUESTION: Please tell, will MX4 be available in June in Europe? When will be another flash sale in China?
[17:48] <elepants> mhall119: it was given away for free at ubuntu booth IoTWorld
[17:49] <Kamilion> QUESTION: Has anything been looked at re Stripe or Coinbase for micropayments?
[17:49] <Knightmare> QUESTION: Will 16.04 have support for high resolution displays i.e. 4k
[17:51] <Geek500> Is anything happening with Ubuntu for TV?
[17:55] <ChloeWolfieGirl> QUESTION: Will Ubuntu on the Phone be a bit neglected when making unity8 desktop exclusive features that you'd only beable to use on desktop or coverged devices?
[17:57] <Knightmare> QUESTION: Do you feel that maybe Canonical/Ubuntu might be getting spread a bit thin due to the work load?
[17:58] <aikidouke> QUESTION: Does the QA team have a weekly meeting?
[17:59] <Kamilion> QUESTION: What is the air-speed velocity of an unladen swallow?
[17:59] <aikidouke> An African or European Swallow?
[17:59] <Kamilion> It's irresponsible to answer a question with a question, aikidouke ;)
[17:59] <aikidouke> :)
[18:00] <Kamilion> python3 can answer it.
[18:00] <Kamilion> just import antigravity.
[18:00] <mhall119> thanks eveyrone
[18:01] <Knightmare> bye
[18:01] <Kamilion> cheers.
[18:02] <Kamilion> psst, the answer is 10 meters per second.
[18:04] <wxl> aikidouke: btw there is no regular QA team meeeting
[18:05] <aikidouke> wxl: I thought I saw one on the wiki a while ago, but havent been able to find it. TY
[18:05] <balloons> aikidouke, if you can't use IRC there's also the mailing list
[18:05] <balloons> aikidouke, https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
[18:06] <aikidouke> balloons: ;) well i did ask first in IRC, i've been in and out thought, so i might have missed it
[18:06] <aikidouke> balloons: I am on the mailing list and have done a tiny bit of testing
[18:06] <aikidouke> balloons: i just need to give myself some more time to do more I guess
[18:08] <balloons> aikidouke, feel free to contact me directly anytime if you get stuck. But in general the IRC channel and mailing list gets you in touch with the rest of the community and they are happy and more than capable of pointing you in the proper direction
[18:09] <aikidouke> balloons: thank you, I will, soon!
[18:11] <elfy> balloons: thanks -must have missed the beginning on -on-air - caught it all now


[13:55] <AskUbuntu> Example Wordpress content from github missing for juju charm | http://askubuntu.com/q/505018
[15:04] <asanjar> hi GKing
[15:36] <jamespage> gnuoy, console support merged - thanks1
[15:36] <jamespage> it helped flush out a bug in websockify as well
[15:36] <gnuoy> jamespage, brilliant, thanks for the review
[15:36] <jamespage> gnuoy: https://bugs.launchpad.net/ubuntu/+source/websockify/+bug/1350352
[15:36] <_mup_> Bug #1350352: nova-novncproxy and nova-spiceproxy need patched websockify <websockify (Ubuntu):Fix Released> <nova (Ubuntu Trusty):Invalid> <websockify (Ubuntu Trusty):In Progress by james-page> <nova (Ubuntu Utopic):Invalid> <websockify (Ubuntu Utopic):Fix Released> <https://launchpad.net/bugs/1350352>
[15:38] <jamespage> gnuoy, how do you feel about enabling the l2pop driver by default in the neutron charms
[15:38] <jamespage> ?
[15:41] <gnuoy> jamespage, I like the sound of what it does. Have you used it much in anger ?
[15:45] <jamespage> gnuoy, no
[15:45] <jamespage> but it should help with scalability again
[15:45] <jamespage> is my understanding
[15:46] <jamespage> as management of ovs is more targetted and less broadcast
[15:46] <gnuoy> sure, but on-by-default seems a little extreme
[15:47] <jamespage> gnuoy, agreed
[15:47] <gnuoy> well, maybe we stick it on by default and in next and see what happens
[15:47] <gnuoy> s/and in/in/
[16:09] <dpb1> bcsaller, cory_fu: Quick one to update an out of date readme: https://code.launchpad.net/~davidpbritton/charms/precise/block-storage-broker/fix-readme/+merge/229074
[16:09] <dpb1> if you have a sec
[16:16] <cory_fu> dpb1: Any idea why those extra-packages were included in the first place?
[16:17] <dpb1> cory_fu: extra packages?
[16:17] <dpb1> cory_fu: oh, on the postgres charm options
[16:17] <cory_fu> - extra-packages: python-apt postgresql-contrib postgresql-9.1-debversion
[16:17] <dpb1> ?
[16:18] <cory_fu> Yeah
[16:18] <dpb1> ok
[16:18] <cory_fu> Seems fine to remove them, just wondering why they were there if not needed
[16:18] <dpb1> cory_fu: cut and paste I suspect.  It's what we use for our deployment, they are not needed in a general case
[16:18] <dpb1> like the max_connections
[16:18] <cory_fu> Makes sense
[16:32] <dpb1> cory_fu: btw, here is another one that has kind of stagnated: https://code.launchpad.net/~davidpbritton/charms/trusty/apache2/avoid-regen-cert/+merge/223990  -- it's just to merge up from the precise charm.
[16:32] <dpb1> (i.e., it's already been reviewed/accepted in precise)
[17:59] <jcastro> can someone review these two fixes to the ES charm?
[17:59] <jcastro> https://code.launchpad.net/~michael.nelson/charms/trusty/elasticsearch/add-ufw/+merge/225934
[17:59] <jcastro> https://code.launchpad.net/~michael.nelson/charms/trusty/elasticsearch/ufw-for-peers-too/+merge/225968
[18:42] <sebas5384> jcastro: ping
[18:43] <jcastro> yo!
[18:43] <sebas5384> hey jcastro o/
[18:43] <sebas5384> jcastro: we have like 5 devs using juju as a local dev environment
[18:43] <jcastro> ooh! Any feedback!
[18:44] <sebas5384> yeah! exactly
[18:44] <sebas5384> so we have a lot of feedback :P
[18:44] <jcastro> sebas5384, I am having an argument, I mean discussion on local dev things we should fix with the devs next week
[18:44] <jcastro> so the more the merrier, but I need it soon!
[18:44] <sebas5384> how can we schedule some talk about our experiences
[18:44] <jcastro> maybe we can have you dial in?
[18:45] <sebas5384> yeah sure!
[18:45] <sebas5384> i remember you talked about some team working in that
[18:45] <sebas5384> or some guys
[18:45] <sebas5384> i would really like to share our experiences and stuff we had done
[18:47] <sebas5384> for example, we make juju-local working in the elementaryOS hehe
[18:47] <sebas5384> *work
[18:48] <sebas5384> wasn't a perfect solution, but at least we know what's the problem hehe
[18:49] <sebas5384> and we have 3 people using juju-local using the vagrant workflow
[18:49] <sebas5384> a lot of things to resolve there hehe
[18:57] <jcastro> which time zone are you guys in?
[19:00] <arosales> sebas5384 +1 on feedback :-)
[19:00] <sebas5384> arosales: :)
[19:00] <jcastro> sebas5384, we're going to be in Germany, so if you can find an hour next week that works for you guys, I can schedule us to all be in a room to listen in
[19:00] <sebas5384> i'm in GMT-3
[19:01] <sebas5384> jcastro: sounds good to me :)
[19:02] <sebas5384> wednesday 8/6 ?
[19:14] <jcastro> sebas5384, hey
[19:14] <jcastro> how about tomorrow?
[19:14] <jcastro> you guys able to do google plus?
[19:14] <sebas5384> yeah sure
[19:14] <arosales> jcastro: +1 for tomorrow if you are available sebas5384 ?
[19:15] <sebas5384> yes! just have to know the time
[19:15] <sebas5384> to see my agenda
[19:18] <arosales> sebas5384: looking at jcastro and my cal
[19:18] <sebas5384> great!
[19:23] <arosales> sebas5384: does 14:00 utc work for you?
[19:23] <sebas5384> arosales: let me see
[19:27] <sebas5384> arosales: can be 13:00 utc ?
[19:28] <sebas5384> if not it's okay :)
[19:29] <arosales> sebas5384: for sure, that works for me. I"ll just get my coffee breweing earlier :-)
[19:29] <sebas5384> arosales: thanks!!! :)
[19:30] <arosales> sebas5384: thanks for the feeback, thats solid gold :-)
[19:30] <sebas5384> who's going to send the invite :)
[19:30] <sebas5384> ?
[19:30] <sebas5384> arosales: thanks for the awesome work ;)
[19:31] <arosales> sebas5384: I'll send. sent you a pm for your email.
[19:31] <sebas5384> arosales: great
[19:31] <arosales> if anyone else is interested in joining let me know
[19:31] <sebas5384> if you can
[19:31] <sebas5384><EMAIL_ADDRESS>send it here
[19:32] <sebas5384> ooh arosales sorry, didn't see about the pm xD
[19:32] <jcastro> sebas5384, start thinking about what you're going to tell us
[19:32] <jcastro> because we're going to write it down
[19:32] <sebas5384> jcastro: yeah! we are going to organize here to get a list
[19:37] <arosales> sebas5384: here is a google doc to add your ideas to https://docs.google.com/a/canonical.com/document/d/1t_55N1il3XoL8z-jfa1CBoSxzOQjC90cgSpCqx5wkH0/edit
[19:37] <arosales> any one else please feel free to add in your ideas.  or ping me to join the meeting.
[19:37] <arosales> we'll be sureto the mail the list with our findings too.
[19:38] <jcastro> arosales, it wouldn't hurt to just post the document to the list for everyone
[19:38] <sebas5384> arosales: great!
[19:39] <arosales> jcastro: will do
[19:40] <arosales> sebas5384: I think we'll just make tomorrow's session on air if you don't mind.
[19:40] <arosales> so we can sure learning with others who are unable to join, does that sound ok with you?
[19:40] <sebas5384> yeah that would be awesome!
[19:51] <jose> arosales: ping
[19:51] <jose> arosales: mind a quick PM?
[19:53] <arosales> jose: sure
[19:53] <arosales> jose: I mean I don't mind at all :-)
[19:53] <jose> :P
[20:48] <noodles785> Hi hazmat. When you've time, I've updated the elasticsearch charm MP after your feedback: https://code.launchpad.net/~michael.nelson/charms/trusty/elasticsearch/add-ufw/+merge/225934
[20:56] <hazmat> noodles775, nice
[20:59] <noodles775> It would have been nice if ufw could be configured via a config file in /etc - I don't like that it's reseting the firewall on each hook run.


[04:03] <paultag> hey gilbert
[04:03] <paultag> gilbert: came accross http://lists.debian.org/debian-mentors/2011/09/msg00522.html
[04:04] <paultag> gilbert: the if/if/if conditionals can be condensed into cc_dict = { "java"<EMAIL_ADDRESS>"python"<EMAIL_ADDRESS>... }
[04:04] <paultag> and use that, and on key error, fall through
[04:04] <paultag> also haskel is marked as python
[04:04] <paultag> +    if section == 'python':
[04:04] <paultag> +        headers.append('X-Debbugs-CC<EMAIL_ADDRESS>[04:04] <paultag> +    if section == 'python':
[04:04] <paultag> +        headers.append('X-Debbugs-CC<EMAIL_ADDRESS>[04:05] <paultag> you can also += """ \n\n\n\ """
[04:05] <paultag> minor crap, but totally cool
[04:07] <dzho> whee, <60min to blackout
[04:09]  * Unit193 is so scared </sarcasm_for_now>
[04:25]  * Cheri703 is trying to decide if it is a good idea to send an angry/frustrated email when suffering from sleep deprivation
[04:26] <dzho> might be ok to compose it, to get it out of your system, but postpone it.
[04:26] <dzho> use all that energy to drive the writing, sure.
[04:26] <Cheri703> well, I *do* need a response on part of it as soon as possible, and I'll be asleep when he is likely to get it / respond
[04:26] <dzho> doesn't sound like there's much choice, then, really.
[04:28] <Cheri703> short version: purchased something, in setting it up, running into ALL SORTS of quality control issues, have had to make multiple trips to purchase parts that should have come with it, will have to make more trips to fix a spot that has stripped threads, just all around ridiculous...and I'm pissed. also bought x specifically to mount y, explicitly mentioned I was planning to use y, guy recommended y, and there is NO POSSIBLE way that y will
[04:28] <Cheri703> fit securely onto x...
[04:28] <Cheri703> so I'm super annoyed
[04:29] <Cheri703> the mounting issue is the part I need a reply on, we've discussed some of the rest of it, but he's all "oh, no big deal, just go get replacement thingy, I'll pay for the part" but it requires driving across town, waiting til a car is available, and coming home from the store to realize I will have to go RIGHT BACK for another part is ridiculous
[22:18] <jrgifford> paultag, i didn't know opencongress.org was your guys thing.
[22:18] <jrgifford> nice work!
[22:21] <paultag> jrgifford: thanks! :)
[22:21] <paultag> yeppers, sunlight as hell
[22:21] <paultag> feel free to contribute, it's all f/oss!
[22:21] <jrgifford> i noticed, i'm like, watcher #50 on github. :P
[22:22] <paultag> :D
[22:22] <jrgifford> i really need to get my act together and stop writing docs and helping people and start writing code. :P
[22:22] <paultag> jrgifford: dude
[22:22] <Unit193> Looks like they have a SOPA thing up too
[22:22] <paultag> jrgifford: docs are tragic with sunlight, i've come to notice
[22:22] <paultag> Unit193: :)
[22:22] <jrgifford> yeah they do Unit193. :)
[22:22] <paultag> jrgifford: if you wanted to get into doing developer stuff, I'd be bloody impressed
[22:22] <paultag> jrgifford: shame you're not in BOS, we're looking for an intern
[22:23] <Unit193> jrgifford: Was looking for a few earlier :P But now I :x
[22:23] <jrgifford> paultag, sad story of all f/oss unfortunately, have a small project that needs docs?
[22:24] <paultag> jrgifford: yeah, actually. They all do - a few HOWTOs on how to help with openstates would be super ultra kickass
[22:24] <jrgifford> also, if you're interested in informally formal relationship with a remote intern-ish type idiot, just tell me and i'll do my best to convince my parents. :P
[22:24] <paultag> jrgifford: we're looking for someone to work here in BOS :(
[22:24] <paultag> some of it sucks to do remote
[22:24] <paultag> and we already have one remote intern :(
[22:24]  * canthus13 wonders how crappy of a company GXS is...
[22:25] <jrgifford> :( oh well. i'll look into openstates after I finish calling portman and brown about PIPA. :)
[22:25] <paultag> Cheri703: http://influenceexplorer.com/organization/gxs/f01803a0885147faac4e49f137e44a34
[22:25] <paultag> jrgifford: :)
[22:25] <paultag> erm crap
[22:25] <paultag> sorry Cheri703
[22:25] <paultag> canthus13: http://influenceexplorer.com/organization/gxs/f01803a0885147faac4e49f137e44a34
[22:26] <canthus13> paultag: I'm more interested in what it's like to work there.
[22:26] <paultag> canthus13: ahhh. Right.
[22:26]  * canthus13 is looking at a TSS position in Brook Park.
[22:26] <jrgifford> LOLOLOLOLOLOLOL
[22:27] <jrgifford> portmans voicemail box is full. :D
[22:27] <jrgifford> and all the lines are busy.
[22:28] <jrgifford> that says something about the power of the internet right there guys.
[22:28] <paultag> jrgifford: you know that zipcode thinger on wikipedia?
[22:28] <paultag> jrgifford: sunlight data ;)
[22:28] <jrgifford> i haven't visited wikipedia all day.
[22:28] <jrgifford> well, everyone uses sunlight now that i look at it.
[22:29] <jrgifford> also, govtrack.us is evil. :P
[22:29] <paultag> :)
[22:29] <paultag> jrgifford: yeah, sunlight is everywhere
[22:29] <paultag> and it's awesome
[22:30] <paultag> all up on the news too
[22:30] <paultag> which is cool
[22:30] <jrgifford> :D
[22:34] <jrgifford> thank the lord for free domestic US Google Voice calls. If I didn't have that, I wouldn't be calling DC. :(
[22:34] <canthus13> jrgifford: You must have a crappy cell carrier?
[22:34] <jrgifford> canthus13, i'm 15 and without a cell phone. :P
[22:34] <canthus13> jrgifford: Ah. Makes sense. :)
[22:35] <jrgifford> paultag! opencongress is 502'ing on me! where do I send money for another server?! :D
[22:51] <Unit193> jrgifford: I don't think I remembered/knew you were 15
[22:52] <jrgifford> Unit193, i seem to remember putting it on my wiki page.
[22:52] <jrgifford> but i might have edited it out after someone said something
[22:53] <Unit193> Hmmm... Not that it really matters though
[23:05] <jrgifford> It does if you're trying to get any sort of job type thing. :P
[23:10] <Unit193> There it would
[23:10] <Unit193> Better chances at 16 w/ permission from school
[23:10] <jrgifford> I have permission from school. In fact, school is forcing me to do this. ("yay" for homeschooling. :P)
[23:11] <Unit193> *Permission from local school super
[23:11] <Unit193> I was homeschooled (Did better for my sisters), my sister went through this years ago
[23:12] <jrgifford> oh, thats easy to get, particularly if job start date is after May 20th or something like that. But I can't get that until I get a offer.
[23:12] <Unit193> Language warning: Lookup Cyanide and Happiness and view the source for today
[23:13] <jrgifford> lol?
[23:13] <Unit193> Would volunteer also work? I had that for a while (not required) and I loved it
[23:14] <Unit193> jrgifford: Source is funny, but like paultag
[23:14] <jrgifford> Unit193, volunteer could work, its just not where I want to be.
[23:16] <Unit193> jrgifford: Was in a hospital IS dept for a while, was awesome (They trusted me so I got to do all sorts of fun stuff wtih the little crappy parts)
[23:16] <jrgifford> oh? That could be fun.
[23:18]  * Unit193 got the domain admin pass, and his own account with cool privs :D
[23:40] <gilbert> paultag: thx 4 the suggestions
[23:41] <gilbert> paultag: btw how did u come accross that?
[23:41] <gilbert> paultag: i didn't seem to get much interest after i put it together...felt a bit discouraged