[01:38] <vibhav> Good Morning
[01:59] <vibhav> can https://bugs.launchpad.net/ubuntu/+source/calamaris/+bug/569514 be nominated for oneiric, natty and luicd?
[02:22] <micahg> vibhav: if you plan on fixing it for all those releases, sure
[02:24] <micahg> actually, I shouldn't say that until I look at the fix
[02:25] <micahg> yeah, that would be fine for an SRU
[02:25] <micahg> IMHO
[02:30] <vibhav> micahg: Yes, I am planning it to fix it for all these releases
[02:31] <micahg> vibhav: done
[04:23] <vibhav> micahg: ping
[04:25] <vibhav> micahg: I created an SRU for natty https://bugs.launchpad.net/ubuntu/+source/calamaris/+bug/569514/comments/4
[04:29] <micahg> vibhav: yes?
[04:29] <micahg> vibhav: there's no changelog entry
[04:34] <vibhav> micahg: wait
[04:35] <vibhav> micahg: done
[04:45] <micahg> vibhav: still not sure why you pinged me though
[06:35] <vibhav> micahg: I wanted you to look at my debdiff
[06:49] <dholbach> good morning
[06:56] <geser> good morning
[07:17] <Laney> greetings
[07:17] <Laney> how was the meeting? :-)
[07:17] <micahg> Laney: we made you king of the MOTUs
[07:18] <vibhav> yeah
[07:19] <dholbach> King Laney, first of his name, sole ruler of bugs, sponsorship requests, bug fixing initiatives, packaging guide updates and lintian warnings
[07:19] <Laney> that means I don't have to do any of the work myself, right?
[07:19] <vibhav> NO
[07:19] <Laney> \o/
[07:19] <micahg> Laney: right, it all got assigned to broder
[07:19] <dholbach> I'm not sure that's how it works - you have a kingdom to take care of
[07:20] <vibhav> hehe
[07:21] <dholbach> the meeting was great - I'll write the minutes in a bit
[07:22] <vibhav> yeah, I was the only non-MOTU among all MOTUs
[07:41] <ajmitch> Laney: I showed up, why didn't you? :)
[07:56] <alkisg> Any good tools for writing man pages? Is docbook + po4a a good choice, in order to have them translatable in launchpad etc?
[08:01] <Rhonda> vim :)
[08:01]  * Rhonda prefers to write manpages directly in roff.
[08:01] <Rhonda> But po4a is always a good choice
[08:02] <alkisg> Rhonda: can sections be extracted and translated if one writes manpages directly in roff?
[08:05] <Rhonda> I would assume so.
[08:18] <Daviey> dholbach: Hey, i understand you reviewed two packages for yolanda?
[08:18] <Daviey> dholbach: do you fancy uploading, and i'll review it in-queue?
[08:19] <dholbach> Daviey, sure, why not - particularly the maintainer scripts would be good to have reviewed by a server person, for example
[08:20] <dholbach> and license/copyright obviously
[08:20] <Daviey> right.. thanks dholbach
[08:20] <dholbach> thanks
[08:21] <yolanda> hi
[08:25] <Daviey> hey yolanda :)
[08:26] <MrChrisDruif> dholbach; nice way to appraise Laney (about an hour ago)
[08:30] <dholbach> :)
[08:31] <MrChrisDruif> (I love scrollback ^_^)
[08:32] <dholbach> Daviey, done
[15:51] <l3on> dholbach, thanks for sponsor :)
[18:10] <tumbleweed> dupondje: going to sync/merge snort?
[18:32] <dupondje> tumbleweed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650060 needs fixed first in debian, then we can sync
[18:32] <dupondje> wanted to wait a bit :)
[20:17] <tumbleweed> dupondje: aah
[20:29] <jtaylor> wtf https://launchpad.net/ubuntu/+source/pyzmq/2.2.0-1/+build/3518451
[20:29] <jtaylor> why is that building, all other arches are in dep-wait
[20:29] <jtaylor> oh
[20:29] <jtaylor> it was just installing to fail
[20:30] <jtaylor> should ahve waited 5 more sec
[20:30] <tumbleweed> aha, the workitem tracker doesn't like Informational blueprints and this is heron<EMAIL_ADDRESS>has joined #ubun
[20:31] <tumbleweed> err *this is: https://blueprints.launchpad.net/ubuntu/+spec/other-q-backports-bof
[20:31]  * tumbleweed changes it to Unknown
[20:45] <dupondje> tumbleweed: had time for my MOTU application yet ? :)
[20:58] <bregma> hey folks, I uploaded a package to precise-proposed for an SRU and discovered a bug at the last minute, but I can't use dcut on Ubuntu archives -- how do I replace the erroneous package in the queue?
[21:04] <bregma> ah, never mind, I can just upload over top, evidently
[21:07] <jtaylor> or ask an admin in ubuntu-release to reject it
[21:12] <ScottK> bregma: What package?
[21:13] <ScottK> (both uploads will stay in the queue, so one ought to be rejected)
[21:36] <micahg> Jump to: main (35) restricted (0) universe (666) multiverse (11)
[21:37] <ajmitch> bit of a jump in ftbfs numbers?
[21:38] <LordOfTime> zomg, universe is 666 o.O
[21:38] <jtaylor> there was a sync yesterday
[21:41]  * LordOfTime was reffering to the number being 666 :P
[21:42] <LordOfTime> yeah, the sync got in quite a few things i was hoping were going to be included in Quantal :P
[21:47] <micahg> ajmitch: yeah, I was hoping the sync would reduce the number :(
[22:27] <jtaylor> wow the libpgm NMU was neat ..., new upstream version, weird version number, dropped patch which should not have been dropped, dropped autoreconf without reason
[22:28] <jtaylor> and all that not even required to fix the rc bug
[23:44] <tumbleweed> dupondje: yup
[23:55] <dupondje> thanks ! :)


[17:10] <Eickmeyer[m]> sigh I'll get it.
[17:10] <Eickmeyer> !no ubuntustudio-installer is <reply> Ubuntu Studio Installer is an app that can be used to add Ubuntu Studio's benefits to an existing Ubuntu (or official flavor) installation, and/or add the !ubuntustudio-backports PPA. For more info, see https://ubuntustudio.org/ubuntu-studio-installer/
[17:11] <teward> *finger-wags at Eickmeyer*
[17:12] <Eickmeyer> That's what happens when I try to use my Matrix client instead of direct IRC.


[09:07] <Saviq> G'day
[09:08] <Saviq> OM$D, what is it with the CVEs…
[09:09] <Saviq> alan_g I'll take these on today
[09:29] <alan_g[m]> We do need to automate more
[09:29] <Saviq> Yup, it's in our backlog
[09:30] <Saviq> Also, we may want to think about only rebuilding once a week or so, to collect more CVEs together
[09:31] <alan_g[m]> I'd prefer it to be automated and immediate
[09:31] <Saviq> Sure, same, but until we can get there…
[09:32] <alan_g[m]> Let's get there next iteration
[09:47] <Saviq> Not sure that we can, at least for the more prominent snaps we want somewhat comprehensive testing. We also should deprecate some of them - that, we can certainly do next iteration.
[09:54] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [issue #2733](https://github.com/MirServer/mir/issues/2733): Mir fatal error: surface observer should have been deleted, but was not (use count 2) when running Audacity in egmde... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/2883d179e02142b0b7eb0f314c090abf7c6a2ccd>)
[09:59] <alan_g[m]> OK, so you first want to automate "somewhat comprehensive testing" beyond what we currently have in the lab?
[09:59] <alan_g[m]> Seen my PoC? https://github.com/AlanGriffiths/ubuntu_frame_test
[09:59] <alan_g[m]> That could be fleshed out
[10:24] <Saviq> Well, yes, that's the kind of high level tests I have in mind, but probably using one of the existing tools out there that help with UI testing (probably fuzzy screenshot comparison). But yeah, spawn Frame, OSK, VNC,
[10:25] <Saviq> Plus some basic interaction - changing OSK layouts, typing on the OSK - what Sophie had in mind
[10:28] <alan_g[m]> Yeah, it was definitely the simpest thing. But could replace a lot of what we do manually and do it reliably on multiple targets that we may not have to hand
[10:42] <Saviq> alan_g got access to confined-shell now, just needed to accept
[15:32] <alan_g[m]> Saviq seeing your comment about Kodi plugins makes me wonder if this is another place where a content interface might be part of the solution. (Not that we want to spend time ourselves)
[15:53] <Saviq> alan_g yeah, it _could_ be, but then it's 200 plugins ;)
[15:53] <Saviq> I'm thinking maybe a kind of importer script… `mir-kiosk-kodi.get-addon <url>`
[15:54] <Saviq> Though that wouldn't get updated
[15:54] <Saviq> But yes, for real it should be a greedy content slot
[15:55] <alan_g[m]> I was thinking more along the lines a "snap your plugin" industry
[15:56] <alan_g[m]> Saviq: It *could* poll in post-refresh
[16:28] <Saviq> Assuming the URL would be static, or we'd actually use a PPA, but yeah, something for a December afternoon ;)
[16:42] <alan_g[m]> I was assuming the normal case would be ppa:team-xbmc/ppa
[17:36] <Saviq> Good weekend all o/
[18:02] <alan_g[m]> Have a good weekend everyone!


[00:33] <Noskcaj> darkxst, Would it be worth me trying to get clutter 1.16.4 into ubuntu this late in the cycle? we're at 1.16.0 now
[01:20] <darkxst> Noskcaj, yes, that won't be affected by the freeze
[02:14] <darkxst> Noskcaj, although obviously too late to enable the wayland backend in clutter
[04:22] <darkxst> mitya57, you still going to switch flashback to XDG_CURRENT_DESKTOP=Unity?
[05:06] <mitya57> darkxst: Yes, I am.
[05:08] <mitya57> I don't understand why nautilus xdg autostart file doesn't work in Flashback when XDG_C_D is Unity
[05:09] <mitya57> Anyway, upstream approved my patch so I can just find someone who commits it for me.
[05:10] <darkxst> mitya57, it may need --forcedesktop?
[05:16] <mitya57> In gnome-session args?
[05:16] <darkxst> also I am not seeing a 'show-desktop-icons' key anymore, however I don't quite have vanilla installation
[05:16] <mitya57> Ah, no, that has Unity in OnlyShowIn
[05:18] <darkxst> mitya57, anything listed in a required component of gnome-session session will get launched based on *ShowIn values
[05:18] <darkxst> upstart user launching only works for things in /etc/xdg/autostart (I think)
[05:19] <mitya57> Ok, let's use my patch then
[05:21] <darkxst> ok
[05:22] <darkxst> I am hoping to push through gnome-desktop 3.10 as a FFe, however right now it breaks on flashback due to the whole GNOME not Unity thing..
[05:49] <darkxst> mitya57, wierd, seems to me like dbus activation is not working under flashback sessions ;(
[05:58] <Noskcaj> darkxst, done, plus the bugfix releases of vinagre and libdmapsharing
[06:00] <Noskcaj> crap, i didn't test build clutter, and just deleted the files
[06:00] <Noskcaj> Could someone branch lp:~noskcaj/ubuntu/trusty/clutter-1.0/1.16.4 and test build it? My internet will take too long to get it, plus my brother's won't let me download stuff right now
[06:01] <Noskcaj> too long ~= 1 hour
[06:01] <darkxst> oh Noskcaj !!!!
[06:17] <mitya57> darkxst: So many things are broken there :(
[06:19] <mitya57> I expect to switch identifying to Unity once I fix the indicators, and then look if other bugs still persist.
[06:24] <darkxst> mitya57, yeh, I predicted this mess over a year ago, before edubuntu picked up flashback
[06:24] <darkxst> Noskcaj, well it builds
[06:25] <Noskcaj> darkxst, thank you
[06:25] <Noskcaj> I'll try and get the bugfix release of aisleriot done, but it's taking it's time to download
[06:26] <darkxst> I couldn't care less about games ;)
[06:27] <darkxst> but go ahead, someone has to look after them ;)
[06:31] <Noskcaj> neither do i, but as stable a release a possible helps
[21:30] <GuSec> Hi! Having trouble nvidia drivers and this bug: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1268134
[21:30] <GuSec> What's a safe solution to install them? Tried installing jockey-kde, but that doesn't seem to work.
[21:35] <darkxst> GuSec, you can install them directly with apt-get
[21:35] <GuSec> I now checked the jockey log, and something has been done. Albeit not completely. How to clean this mess first?
[21:49] <GuSec> Hello again. Jockey seemed to be able to fix it, rebooted after a green light when trying the nvidia-304. Works like a charm. Anything else I should think about? As far as I knew, using jockey is strongly discouraged...


[00:12] <mhall119> I hope yours teaches more practical things than mine
[00:13] <nigelb> heh
[00:14] <mhall119> I had a professor question whether I wrote an assignment myself, I pointed him to my bzr repo for history, and he told me that using version control was more complicated than I should be doing
[00:14] <nigelb> wtf
[00:15] <mhall119> me and that prof....didn't get along
[01:11] <locodir-user> hello guyz ....
[01:44] <paultag> mhall119: haha, my professors rule
[01:44] <paultag> mhall119: he let me set up a server to use to turn in assignments via vcs on campus
[01:55] <paultag> BBL, one love
[01:57] <mhall119> turning in assignments by pushing to a school's repo would be awesome
[01:57] <mhall119> might get me into the habit of signing my commits too
[06:35] <YoBoY> good morning
[07:15] <jasonjang> G'morning, ALL~ &
[07:15] <jasonjang> Thx for the rapid reply, czajkowski
[07:20] <czajkowski> jasonjang: np
[07:20] <czajkowski> right off to work
[07:20] <jasonjang> THX again, I'll wait 4...
[07:21] <czajkowski> I dint know could be a few daysb
[07:21] <czajkowski> days
[07:21] <czajkowski> we all work and there are timezones as well
[07:21] <czajkowski> but we will reply
[07:21] <jasonjang> OK. never mind. ok.
[07:26] <dholbach> good morning
[07:27] <jasonjang> G'morning,
[08:48] <cjohnston> mornin
[11:37] <aakshay> where can i find the documentation of the LocoDirectory development?
[11:38] <Ronnie> aakshay: what documentation do you need?
[11:39] <Ronnie> i think there is not much developer documentation, except the raw code itself
[11:39] <aakshay> Ronnie: hi Ronnie .. i am gonna present working with Loco Dorectory in seminar
[11:39] <aakshay> so was planning to get some documentation to show there
[11:40] <aakshay> Ronnie: ok.. no probs then i will design something myself
[11:40] <Ronnie> great, share it with the rest of the community when your done, all documentation is welcome
[11:41] <aakshay> Ronnie: thanks.. but is there not even any documentation of LD?
[11:44] <Ronnie> cjohnston, mhall119, dholbach: do you know if there is any documentation ^
[11:45] <dholbach> https://wiki.ubuntu.com/LoCoDirectory/Development is the only one I know of
[11:45] <dholbach> Ronnie, ^
[11:45] <dholbach> it's not much
[11:45] <dholbach> but a few tips we collected
[11:46] <aakshay> dholbach: thanks.. i will use these tips.. :)
[11:53] <nigelb> aakshay: most of it is well commented python code, so I guess no one actually wrote too much docs :(
[11:53] <aakshay> nigelb: may be.. :)..
[12:16] <mhall119> morning
[12:18] <aakshay> mhall119: good morning
[12:28] <nigelb> morning mhall119
[12:39] <daker> hello
[12:39] <daker> mhall119, Ronnie do you know any __working__ django openid provider app ?
[12:40] <nigelb> heh, like the emphasis
[12:41] <mhall119> daker: hmmm, nope
[12:41] <daker> :s
[12:43] <mhall119> daker: you might try https://launchpad.net/canonical-identity-provider
[12:44] <daker> ok
[12:45] <mhall119> I think that's what LD is calling to
[14:50] <cdbs> czajkowski: You mailed me?
[14:51] <czajkowski> cdbs: I did
[14:51] <cdbs> czajkowski: Okay, my spam filter caught it. Weird.
[14:51] <cdbs> Fine, then, that's all
[14:52] <czajkowski> I am not spam :(
[14:54] <cdbs> czajkowski: Jams are impossible when you have just 10 active members spread across 8 far-away cities. :(
[14:54] <czajkowski> cdbs: do them online
[14:54] <czajkowski> you dont actually need to be in person
[14:54] <cdbs> oh? really?
[14:54] <czajkowski> can be online and in your loco irc channel
[14:54] <cdbs> will raise up this in the mailing list
[14:55] <cdbs> Thanks!
[14:56] <BigWhale> fsck!
[14:56] <czajkowski> cdbs: np
[15:03] <mhall119> cdbs: if you can get 2 of them together, that's a jam
[15:04] <cdbs> mhall119: a rather small jam, and I'm too young to go anywhere myself :(
[15:05] <mhall119> cdbs: my jam is going to have 2, maybe 3 people in person, plus others participating remotely
[15:05] <cdbs> mhall119: oh
[15:05]  * cdbs isn't good at arabic and the others aren't goot at english
[15:06] <cdbs> *good
[15:06] <mhall119> so do it all in French
[15:06] <mhall119> ;)
[15:19] <RawChid> Do you have suggestions what non-tech people can do on a Jam?
[15:20] <RawChid> We already've covered translating and documentation..
[15:21] <czajkowski> RawChid: they can reveie and delete wiki pages :D
[15:21] <czajkowski> *review
[15:21] <czajkowski> RawChid: they can report bugs, you don't have to be technical to do that
[15:22] <czajkowski> bad people can help one another
[15:22] <RawChid> Yeah, I also thought of bug hunting
[15:23] <czajkowski> RawChid: yes, if folks cna install unity and do some testing that would be great
[15:23] <RawChid> But I don't have experience with it.
[15:23] <RawChid> Oke, that is a good idea
[15:23] <czajkowski> RawChid: well , you can learn, if things aren't running as you think they should report the bug, try and have someone verify it
[15:23] <czajkowski> and then you'll learn more
[15:26] <RawChid> One more thing. Two weeks ago we've decided to organise a Jam. 2 april was too early, so we'll do it on April 16th
[15:27] <RawChid> Is it then still useful to do natty testing ?
[15:28] <RawChid> Ronnie, ping
[15:28] <Ronnie> pong
[15:29] <RawChid> Well, I was brainstorming on what we could do on the Jam
[15:29] <Ronnie> ic
[15:29] <czajkowski> RawChid: yes testing is always good
[15:30] <RawChid> Oke
[15:33] <Ronnie> RawChid: it seems we have enough ideas to work with all the participants for one day
[15:35] <czajkowski> RawChid: dont be put off if the date doesn't fully suit
[15:36] <czajkowski> the idea of the UGJ is to get one weekend where as many as possible take part, but if the weekend doesn't suit just try and do one at another time and let us know how you get on
[15:36] <RawChid> In the Netherlands we have 2 Jams on April the 16th ;)
[15:43] <czajkowski> RawChid: great stuff
[15:43] <czajkowski> be sure to let people know how you get on
[15:44] <RawChid> What do you mean with: "how you get on" ?
[15:45] <RawChid> How people can participate?
[15:48] <czajkowski> RawChid: a report of it
[15:48] <czajkowski> how it went
[15:49] <RawChid> Yes, we'll do that :)
[16:40] <BigWhale> I wonder if a talk about evolution of Narwhals and marine mammals in general is appropriate talk for upcoming release party...
[16:41] <mhall119> I think anything is okay for a release party, as long as people are enjoying themselves
[16:43] <dholbach> BigWhale, talk to jcastro about it - he once gave a lightning talk on dinosaurs :)
[16:44] <mhall119> that's a big topic for a lighting talk
[16:45] <mhall119> 100 million years, condensed into 5 minutes?
[16:45] <BigWhale> Well, I already had a talk at Karmic release party that started at the very beginning. Big bang.
[16:46] <BigWhale> but talking about marine mammals could sound like shameless self-promotion, for myself. :>
[16:48] <BigWhale> mhall119, any talk about dinosaurs is a big topic :>
[20:07] <mhall119> cjohnston: one set of approvals on my django-openid-auth fixes, hopefully will have them totally approved and landed in trunk tomorrow
[20:07] <mhall119> then we can test it out on LD, and then on summit
[20:08] <mhall119> no more openiduser###!
[20:08] <mhall119> no more old usernames after a rename in LP!
[20:43] <daker_> wow :)
[22:32] <nigelb> morning
[22:34] <mhall119> evening
[22:39] <nigelb> mhall119: did we decide to add support for that mobile thingy?
[23:42] <mhall119> nigelb: yes, they're doing some work on their end, there might be some minor things on our end
[23:42] <mhall119> mostly in the ical feed
[23:44] <nigelb> mhall119: oh ok :)
[23:45] <nigelb> mhall119: I'm trying to put as many summit bugs into the review queue as possible before the hackathon :D
[23:48] <nigelb> mhall119: when we hit lp for authentication, it gives a name for the app, where is that set at?
[23:48] <nigelb> at launchpad itself?
[23:55] <mhall119> in the summit code it tells it, you can also associate it within LP itself, but that takes approval
[23:55] <mhall119> but we don't use LP for authentication, we use SSO


[02:05] <Ubugtu> New bug: #66093 in blueprint "Meeting specifications page omits whether they have been accepted" [Undecided,Unconfirmed]  http://launchpad.net/bugs/66093
[02:20] <Ubugtu> New bug: #66096 in blueprint "Any list of specifications should show your relationship to each" [Undecided,Unconfirmed]  http://launchpad.net/bugs/66096
[02:46] <mhb> hello launchpad masters ... I need to contact a LP user because he wants to join the team I'm managing but I can't seem to find the email address (example: https://launchpad.net/people/petr-simek) ...
[02:46] <mhb> his email address
[03:14] <mpt> mhb, hmm, that's probably a bug
[03:15] <mpt> People can choose to keep their e-mail addresses hidden, but if they apply for your team Launchpad should provide some way for you to contact them
[03:21] <mhb> mpt: ok, should I report it then?
[03:22] <mhb> mpt: I agree with that
[03:22] <mpt> mhb, I'll do it if you like
[03:23] <mhb> thanks
[03:24] <mhb> mpt: point me to it later so I can subscribe it, thank you
[03:26] <mpt> mhb, bug 66105
[03:26] <Ubugtu> Malone bug 66105 in launchpad "Team admin can't contact prospective member who hides e-mail addresses" [Undecided,Unconfirmed]  http://launchpad.net/bugs/66105
[03:35] <mhb> thanks
[03:35] <Ubugtu> New bug: #66105 in launchpad "Team admin can't contact prospective member who hides e-mail addresses" [Undecided,Unconfirmed]  http://launchpad.net/bugs/66105
[06:10] <Little^^Shamrock> hello
[06:17] <Little^^Shamrock> sery
[06:17] <Little^^Shamrock> fxh
[06:17] <Little^^Shamrock> aut5u
[06:17] <Little^^Shamrock> ry
[06:17] <Little^^Shamrock> arey
[06:17] <Little^^Shamrock> resy
[06:17] <Little^^Shamrock> sre
[06:17] <Little^^Shamrock> yser
[06:17] <Little^^Shamrock> ser
[06:17] <Little^^Shamrock> yrey
[06:17] <Little^^Shamrock> esry
[06:17] <Little^^Shamrock> ery
[06:17] <Little^^Shamrock> ser
[06:17] <Little^^Shamrock> ser
[06:17] <Little^^Shamrock> yj
[06:17] <Little^^Shamrock> ytj
[06:17] <Little^^Shamrock> htjd
[06:17] <Little^^Shamrock> hjry
[06:17] <Little^^Shamrock> i
[06:17] <Little^^Shamrock> 57i
[06:18] <Little^^Shamrock> 65i
[06:18] <Little^^Shamrock> e65
[06:18] <Little^^Shamrock> u
[06:18] <Little^^Shamrock> tustrhs
[06:18] <Little^^Shamrock> xgfs
[06:18] <Little^^Shamrock> xyf
[06:18] <Little^^Shamrock> setr
[06:18] <Little^^Shamrock> ys
[06:18] <Little^^Shamrock> ryus
[06:18] <Little^^Shamrock> e5ryu7
[06:18] <Little^^Shamrock> tru
[06:18] <Little^^Shamrock> drtyu
[06:18] <Little^^Shamrock> dtr
[06:18] <Little^^Shamrock> ujsdrtu
[06:18] <Little^^Shamrock> as435
[06:18] <Little^^Shamrock> uts
[06:18] <Little^^Shamrock> 534u
[06:18] <Little^^Shamrock> ths
[06:18] <Little^^Shamrock> rfhg
[06:18] <Little^^Shamrock> srf
[06:18] <Little^^Shamrock> yh
[06:18] <Little^^Shamrock> trey
[06:18] <Little^^Shamrock> a
[06:18] <Little^^Shamrock> 53u
[06:18] <Little^^Shamrock> 53u
[06:18] <genuine_Part> hello
[06:21] <genuine_Part> hello
[06:21] <genuine_Part> any some wnat to help me?
[11:26] <arromeo> Hello.
[11:27] <arromeo> Anyone around?


[12:15] <uniq> riddell: http://siretart.tauware.de/revu/details.py?upid=117 if you want to advocate the upload.
[02:11] <Riddell> \sh_away: could you review kio-apt and datakiosk please
[09:05] <pef> hi
[09:37] <karthik085> Riddell: Hey
[09:44] <karthik085> Riddell: I tested KCall. There are problems such as the stability and the UI. Connecting to the servers is another problem. A new release(0.5.2) came out 3- 4 days back. I tried that too. For some reasons, when I dialed a phone number, it did not ring. This app is still in his early stages. I tried on breezy. But, I had lot ofproblems with qt. I guess qt is not working in Breezy, I have contacted the author regarding the pr
[09:44] <karthik085> oblems currently I am facing, furutre plans, etc. I will keep in touch with you and let you know my progress.
[09:55] <karthik085> Riddell: I tested KCall. There are problems such as the stability and the UI. Connecting to the servers is another problem. A new release(0.5.2) came out 3- 4 days back. I tried that too. For some reasons, when I dialed a phone number, it did not ring. This app is still in his early stages. I tried on breezy. But, I had lot ofproblems with qt. I guess qt is not working in Breezy, I have contacted the author regarding the pr
[09:55] <karthik085> oblems currently I am facing, furutre plans, etc. I will keep in touch with you and let you know my progress.
[10:44] <paines> hi
[10:45] <paines> when setting up a printer via kcontrol you cannot print at all
[10:45] <paines> browsing localhost:631 shows the configured drivers but you cannot change anything at all
[10:46] <paines> there is a message, but which is still related to gnome / ubuntu
[10:46] <paines> the message says to configure printer via system -> etc .... gnome way
[10:47] <OculusAquilae> hi
[01:10] <sebas> Is there a good reason why gcc can't find certain X headers in breezy?
[01:10] <sebas> error: X11/extensions/Xrandr.h: No such file or director
[01:11] <sebas> If I add it with -I/usr/X11R6/include, then it compiles
[01:11] <sebas> The same in hoary doesn't have that problem, though.
[01:51] <paines> could be that in hoary the Xrandr.h is in /usr/include which is default include
[02:00] <sebas> paines: Nope, the location of Xrandr.h hasn't changed since then
[02:06] <OculusAquilae> hi
[02:07] <paines> hmm
[02:08] <OculusAquilae> ?
[02:08] <sebas> I've sent a more detailed description of my weirdness to the devel list
[02:34] <JRe> Riddell: for kat 0.6.0 we will need better inotify support
[02:34] <JRe> than the one of hoary
[02:49] <sebas> Would be cool if it got merged, finally.
[03:13] <Riddell> JRe: hoary's inotify is broken completely :)
[03:13] <Riddell> JRe: but I believe breezy's is better
[03:13] <JRe> Riddell: okay good ;)
[03:14] <Riddell> JRe: so kat is getting updates on file changes?
[03:14] <JRe> Riddell: i'm wainting (and helping) for the 0.6.0 version to fix the package
[03:15] <JRe> Riddell: 0.6.0 has a KDED module, KCM, client and slave
[03:15] <JRe> Riddell: and a lib which cab be used by Krusader for instance
[03:15] <Riddell> krusader?
[03:16] <JRe> Riddell: yeah Krusader devs want to add a "search file with this word" features
[03:16] <JRe> Riddell: and they likely use katlib to do that
[03:17] <Riddell> ooh
[03:18] <sebas>   +
[03:18] <sebas> ~4~
[03:18] <Riddell> JRe: how about the user interface, my main problem with it currently is that firstly by default you have to create and save catalogues which I think should be done automatically
[03:18] <JRe> Riddell: this version is very different from the last one! it even has a wizard to configure it ;)
[03:19] <Riddell> and secondly it defaults to a file management interface not a search interface
[03:19] <Riddell> hmm.  startup wizard.  oh joy.
[03:19] <JRe> Riddell: now there is a katslave!
[03:20] <JRe> Riddell: and a kdedmodule which index files on idle time
[03:21] <Riddell> all sounding rather good
[03:21] <Riddell> tvo: you getting this?
[03:21] <tvo> Riddell: reading it now...
[03:23] <tvo> k got it
[04:03] <Riddell> sebas: the X include issue will be a removed symlink
[04:03] <Riddell> new X packages have removed various symlinks for some (presumably perfectly sensible) reason
[05:33] <sebas> Riddell: Ah, but am I right that I should expect to have Xrandr.h in some standard include path?
[05:33] <sebas> Or will I have to specify the include path in my gcc command in the long run? (Hope not)
[05:42] <Riddell> sebas: don't you normally have to give a -I line for X11 includes?
[05:47] <OculusAquilae> hi
[05:47] <Riddell> hello OculusAquilae
[05:48] <Riddell> OculusAquilae: going to become a crack kubuntu hacker?
[05:48] <OculusAquilae> Riddell: hm, hope so
[05:49] <Riddell> OculusAquilae: any thoughts on what to work on?
[05:50] <sebas> Riddell: Hm, not sure. It works in hoary without that
[05:51] <OculusAquilae> Riddell: Hm, I've thought about that, but I don't really know where people are needed. OK kynaptic must be better and so on.
[05:51] <Riddell> OculusAquilae: the trouble with kynaptic is that we're wanting to use kapture instread which should one day be a better program for the job.  but it's in the middle of heavy refactoring and doesn't all work
[05:52] <OculusAquilae> Riddell: I've heard about kapture, but I couldn't find anything about it
[06:04] <OculusAquilae> i'll be back soon
[06:04] <OculusAquilae> cu
[06:05] <Riddell> anyone want to take a look at ksystemlog?  pef?
[06:06] <pef> Riddell: for packaging ?
[06:07] <Riddell> pef: it already comes with packaging, so making sure it works, making sure the packaging is good and upload to revu
[06:08] <pef> Riddell: ok, let's go :)
[06:08] <Riddell> http://www.kde-apps.org/content/show.php?content=23761
[06:09] <Riddell> pef: also there's a post on the mailing list about it which mentions a couple of issues
[06:10] <Riddell> froud: any sign of the NEW e-mail for kubuntu-docs?
[06:10] <froud> no:-)
[06:24] <pef> Riddell: 4 lintian warnings
[06:34] <pef> Riddell: I don't find the source package, I have to start a new one from the sources I think ?
[06:35] <Riddell> pef: don't do that, poke the author instead
[06:36] <pef> ok
[06:38] <Riddell> pef: have you checked if the sources contain a debian/ directory?
[06:39] <pef> Riddell: that's what i'm doing
[06:50] <pef> Riddell: i've sent the mail to the author
[06:50] <Riddell> cool
[06:53] <pef> Riddell: is it difficult to build packages for jam or ant based sources ?
[06:54] <Riddell> pef: never heard of jam, don't know about ant
[06:54] <Riddell> i'd imagine gcj fun is the difficult bit
[07:06] <pef> Riddell: where is the mail about ksystemlog ? I can't find find in my archives and on the online ml archive
[07:35] <froud> Anyone tested the last nightly build?
[07:35] <froud> Does the installer work :-)
[11:19] <pef> bye !


[00:56] <michi> robru: What does “diff missing” mean
[00:56] <michi> ?
[00:57] <robru> michi: it means the diffs are missing :-P
[00:57] <michi> No kidding! :)
[00:58] <michi> What diffs? For what?
[00:58] <michi> I mean, all I did was hit “Build” after pushing a change.
[00:58] <robru> michi: it's the diffs between what's in the silo and whats in distro.
[00:58] <michi> I didn’t see this previously, which is why I’m asking.
[00:58] <michi> So, how does this happen?
[00:58] <michi> Sorry, this is a bit of a black box to me.
[00:59] <michi> Just wondering whether I should worry.
[00:59] <robru> michi: what's happening here is that there's a race condition in the script that updates the silo status. the build job deletes the diffs first then regenerates them at the end. the status update shouldn't be running when the build job is
[00:59] <michi> Aha.
[00:59] <michi> OK, fair enough. I guess it means I can safely ignore that message then.
[00:59] <robru> but the status updater started just before the build did, so it ran and was like "hey the diffs are gone'
[00:59] <robru> but it's ok because the buld job will regenerate them later
[00:59] <michi> Cool, thanks!
[00:59] <robru> michi: you can ignore it for now. if you hadn't just started a build you'd have to worry about it
[01:00] <michi> OK, no prob, thanks!
[01:00] <robru> michi: fixing that race condition is on my to-do list.
[01:00] <robru> yw
[01:00] <michi> Because you have hardly anything to do at the moment… :(
[01:00] <michi> Thanks again for your herculean effort yesterday!
[01:14] <robru> oh man, yeah, yesterday was nuts. every possible thing that could go wrong, did.
[01:14] <michi> Yes, I got that impression.
[01:14] <michi> Well, all is well again. The train is ticking over very nicely, and it’s really easy to use.
[01:15] <michi> Thanks for making a great tool. And one that was actually built with the needs of poor sods like myself in mind!
[01:15] <robru> michi: oh, you like it? thanks. some days I'm like "man this is crap"
[01:15] <robru> I guess it beats the spreadsheet ;-)
[01:15] <michi> No. I think this is a great example of how to get it right.
[01:15] <michi> I can throw a silo together in two minutes flat and it just works.
[01:16] <michi> that’s really nice.
[01:16] <robru> wow, cool
[01:16] <michi> And it’s easy to see what’s going on with the build, and upgrade the phone once things are done.
[01:16] <michi> I really like it.
[01:16] <robru> thanks dude, that's awesome
[01:16] <michi> My pleasure!
[01:17] <robru> just wait until we get rid of jenkins. then it'll be really streamlined! no more "assigning", you just click build and a PPA will be created automatically. I can't wait for that!
[01:17] <robru> that's a few months out yet though, lots of prerequisites to clean up first
[01:17] <michi> Would love to have that.
[01:17] <michi> I’m a little concerned about the proposal for us to create our own Jenkins builds.
[01:17] <michi> the instructions are awfully complicated.
[01:18] <michi> And copying and pasting a large script around hundreds of times is probably not a good thing.
[01:18] <robru> oh yeah, I was really surprised by that
[01:18] <michi> I think if we need to look after our own Jenkins jobs, we’ll need something more like citrain.
[01:18] <robru> I was thinking s-jenkins would be around forever.
[01:18] <michi> Where I can fill in a handful of fields and just press “Go".
[01:18] <robru> michi: yeah I'm hoping to make the train faster & easier so you don't need s-jenkins at all
[01:19] <michi> What we would need is essentially what s-jenkins does for us now though.
[01:19] <michi> Automatic build/test whenever I push a branch.
[01:19] <robru> hmmm, yeah auto build when a branch is pushed could be a bit trickier.
[01:19] <michi> If there is a manual step involved (however small) after a push to get the testing happening, the testing won’t happen most of the time.
[01:20] <michi> This is one strength of Jenkins.
[01:20] <michi> I just do an MP, and it gets built and tested automatically.
[01:20] <michi> I actually don’t mind Jenkins all that much.
[01:20] <michi> Sure, the UI sucks.
[01:20] <michi> And when something goes wrong with one of the builders, it’s hell for us.
[01:20] <michi> But, when Jenkins is working, it’s really nice to have.
[01:21] <michi> From where you sit, it’s an entirely different story, I’m sure.
[01:21] <robru> michi: yeah, I didn't used to mind jenkins, but the longer I am stuck maintaining one the more flaws I find in it and the more powerless I am to do anything about those flaws. train can't continue being a wrapper around jenkins for much longer
[01:21] <michi> I believe you.
[01:21] <michi> But, whatever the replacement, it has to be at least as automatic as Jenkins is now.
[01:21] <michi> Otherwise we’ll lose.
[01:22] <robru> michi: I think we're talking about two different jenkinses ;-)
[01:22] <michi> ?
[01:22] <robru> you're talking about s-jenkins which does the auto-testing of your merges
[01:22] <michi> Yes.
[01:22] <michi> OK, so you are using a different instance underneath the train?
[01:22] <robru> I'm talking about ci-train.ubuntu.com which is itself a jenkins, which I plan to get rid of and incorporate into bileto
[01:22] <michi> Ah
[01:23] <michi> Well, I don’t really care how the train does its thing, as long as it keeps moving :)
[01:23] <robru> yeah, having the train do auto-rebuilds would be a new feature that we could look into doing, but that's separate from what I'm talking about with "replacing jenkins"
[01:23] <michi> Right
[01:24] <robru> michi: but yeah, jenkins is holding us back in a lot of ways. for one it's preventing us from having unlimited silos. the main goal of getting rid of jenkins is to have unlimited silos. but it will also clean up a huge amount of smaller bugs that the train has hobbled through for years
[01:25] <michi> I didn’t know that it was Jenkins that limited the number of silos.
[01:25] <robru> michi: well, indirectly so
[01:26] <robru> michi: what happened was that the lp people made it possible for us to create ppas dynamically, which is amazing.
[01:26] <robru> michi: but in jenkins we have 4 jobs per ppa("silo") and we don't have a great way of generating those dynamically. basically jenkins needs to be restarted in order to see when new jobs are made. there's kind of a way around that but it's not great and blah blah blah so we're kind of stuck with this.
[01:27] <michi> urgh
[01:27] <robru> so if we get rid of jenkins, we don't need to "create jenkins jobs" for every new silo, and we gain a ton of flexibility
[01:27] <michi> Well, from what I’ve heard, you wouldn’t be the only one to see it go.
[01:28] <michi> only one to be happy to see it go.
[01:28] <robru> heh, yeah
[01:47] <michi> trainguards: Sorry for this...
[01:47] <michi> Would it be possible to delete the s390x packages in silo 26 to stop them from getting published?
[01:47] <michi> After some deliberation, we decided to not try and make the builds/tests succeed for s390x.
[01:49] <robru> michi: uh I'm not able to delete binaries, only sources
[01:49] <michi> Aargh.
[01:49] <robru> michi: if you're going to change something that prevents s390x from building you'll need to rebuild anyway.
[01:50] <robru> michi: because if you just delete s390x, then all that happens is it'll be rebuilt in proposed
[01:50] <michi> robru: After talking with jamesh, he pointed out this: https://lists.launchpad.net/ubuntu-phone/msg17189.html
[01:50] <michi> the problem is that we can’t really test with s390x, except in a silo.
[01:50] <jamesh> robru: the package has never been built in proposed
[01:50] <michi> If something breaks on us all of a sudden on that arch, we are toast.
[01:51] <jamesh> robru: michi had disabled some tests to get s390x to build in the silo, but we think it is better to leave things broken since it won't hide the problems should someone want to get this working on that platform
[01:52] <robru> jamesh: michi: right so just re-enable those tests, rebuild, make sure s390x is broken, then you're good to go
[01:52] <michi> robru: Cool, about to do that.
[01:52] <jamesh> robru: my fear was that there would still be an s390x binary package in the silo from the previous build with the tests disabled
[01:53] <jamesh> robru: or does that get ignored during publishing?
[01:53] <robru> jamesh: publishing only looks at the most recent silo contents
[01:53] <jamesh> robru: great.  That makes things easy
[01:54] <robru> jamesh: michi: thumbnailer does not have a s390x binary in xenial so publication will not block on that being failed.
[02:24] <robru> ok, off to the gym, back in ~2 hours
[04:18] <bzoltan_> robru:  is thre a way to just merge the branch and not to release to Xenial? Or how big problem is if the package stucks in the proposed pocket if the next release comes in a day a or two?
[04:20] <robru> bzoltan_: yeah having stuff in proposed isn't horrible. you can't just include your s390x fix in the same silo?
[04:33] <bzoltan_> robru:  QA does not like rebuilds after QA validation
[04:33] <bzoltan_> robru:  but let me try that... maybe QA will not be badly pissed
[04:36] <bzoltan_> robru:  I pushed a single line change to the landing branch ... It will take some time to build all arches, but it will be fine after that.
[04:43] <robru> bzoltan_: oh I didn't realize it had qa already. ok well if it builds you can publish it after that
[04:44] <bzoltan_> robru:  All right then :)
[04:44] <bzoltan_> robru:  I will still need a jedi's ack on the debian/ changes I guess
[04:45] <robru> right
[05:42] <bzoltan_> robru:  all good, but I am not authorized to publish the ubuntu-themes package from that silo60
[05:42] <bzoltan_> ERROR Publish failed: bzoltan not authorized to upload ubuntu-themes
[06:04] <Mirv> bzoltan_: there's uitk packaging change too so needs coredev
[06:16] <bzoltan_> Mirv: Do we have any of the coredevs active in this time?
[06:33] <Mirv> bzoltan_: not really, sometimes I've pinged RAOF but sil2100 should be here in 2h or so
[06:34] <Mirv> and I'd have the uitk rights if the last meeting had been held, but alas it was not
[09:06] <bzoltan_> Mirv:  have you seen sil2100 aready?
[09:18] <sil2100> bzoltan_, Mirv: what's up?
[09:18] <bzoltan_> sil2100:  I would like to publish the silo60 UITK
[09:18] <bzoltan_> sil2100:  and it has debian/ space changes
[09:19] <sil2100> Let me look at it between promotion preparations
[09:20] <Mirv> bzoltan_: yep, soon there. and btw great that the s390x issue was solved (weird that the same trick that fixed other archs didn't work there)
[09:21] <bzoltan_> Mirv:  This fix is a permanent one at least It is a nice and clean landing... I see the chance to spin off one more UITK before the weekend
[09:22] <sil2100> Mirv, bzoltan_: looking at the packaging diff now, but we'll need to get an ubuntu archive member reviewing it as well
[09:22] <bzoltan_> sil2100:  for me the Overlay PPA and the merge are the most critical
[09:23] <sil2100> hmmm
[09:24] <sil2100> Mirv: do you remember if anyone of us got 1.3.1742+16.04.20151209-0ubuntu1 reviewed by an archive admin when we landed it overlay-only?
[09:26] <sil2100> seb128: hey! Sorry to bother you once again with binNEW reviews - we have 2 packages (the base and its -gles equivalent) adding two new binary packages each
[09:26] <sil2100> seb128: diffs here https://ci-train.ubuntu.com/job/ubuntu-landing-060-2-publish/3/artifact/ubuntu-ui-toolkit_xenial_packaging_changes.diff and https://ci-train.ubuntu.com/job/ubuntu-landing-060-2-publish/3/artifact/ubuntu-ui-toolkit-gles_xenial_packaging_changes.diff
[09:27] <sil2100> seb128: could you take a look and give us a sign if it's good to publish with the new binary packages?
[09:30] <seb128> just had a look, the descriptions could be better "Ubuntu gestures library with SwipeArea" doesn't really explain well what that library is, what is "SwipeArea"?
[09:30] <seb128> that's not a blocker
[09:30] <seb128> also "libubuntugestures" should include the soname and be "libubuntugestures5"
[09:30] <seb128> that's a blocker
[09:30] <seb128> so please fix that before archive upload
[09:30] <seb128> bonus if you improve the description
[09:30] <seb128> otherwise looks fine
[09:31] <sil2100> seb128: ACK!
[09:31] <sil2100> bzoltan_: ^
[09:31] <bzoltan_> seb128: sil2100:  fantastic! Thank you gents.
[09:32] <Mirv> sil2100: I don't really remember that. I think maybe, but then again I may mistake it with another earlier landing. but all done now anyhow :)
[09:32] <bzoltan_> seb128:  the next landing will fix those issues
[09:32] <seb128> thanks
[09:32] <sil2100> bzoltan_, Mirv: if you could change and fix that, rebuilt and I guess no re-testing will be needed
[09:33] <sil2100> Since it's generally just a library package name change
[09:34] <bzoltan_> sil2100:  Let me look after it
[09:34]  * sil2100 goes back to his OTA-8.5 promotion hole
[09:34] <bzoltan_> zsombi:  the archive core devs require a better package description for the libubuntugestures package
[09:35] <bzoltan_> zsombi:  not here
[09:37] <sil2100> The biggest blocker is the library package name if anything ;)
[09:37] <sil2100> Description can be changed later
[09:37] <bzoltan_> sil2100:  so simple s/libubuntugestures/libubuntugestures5/ will do it?
[09:44] <bzoltan_> seb128: do you mean to simple change the package name to libubuntugestures5
[09:44] <bzoltan_> ?
[09:45] <seb128> bzoltan_, http://ubuntu-packaging-guide.readthedocs.org/en/latest/ubuntu-packaging-guide/libraries.html
[09:46] <seb128> bzoltan_, but yes, best practice is to use "libname<soname>" so when the abi/soname change the packages are co-installable which makes transitions easier
[09:48] <bzoltan_> seb128:  makes sense
[10:22] <Saviq> hmm hmm, where are the packages from https://requests.ci-train.ubuntu.com/#/ticket/725 ??
[10:24] <Saviq> trainguards ↑↑ did that get published at all? there are per-silo excuses now, but those are not visible in xenial excuses... are autopkgtests ran on silos now or something?
[10:25]  * Saviq happy if that's the case, but who can retrigger the failed test? :)
[10:26] <robru> Saviq: yes autopkgtests for silos were rolled out on Monday, i forgot to make a big announcement because there was a huge outage at the same time, and also it's a bug experimental as well
[10:26] <Saviq> robru, nice one, /me planned to do that in our Jenkaas, much happier if that's global
[10:26] <robru> Saviq: i know pitti can retry autopkgtests, I'm not sure who else though. New uploads will trigger new tests ;-)
[10:27] <Saviq> right, new uploads will also require manual re-tests and QA ;P
[10:27] <Saviq> robru, thing is, https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-021/excuses.html shows qtmir-gles regression, but http://autopkgtest.ubuntu.com/packages/q/qtmir-gles/xenial/amd64/ does not
[10:27] <sil2100> Not if it's a no-change rebuild! But seriously speaking, just poke pitti on -devel, maybe he can retry it for you for now
[10:28] <Saviq> jibel, can't you restart autopkgtests, too? /me hopes pitti's not our single point of failure ;)
[10:28] <robru> Saviq: oh yeah no, the autopkgtest.u.c site doesn't show the silo results at all. Click the "regression" link to see the full test run log
[10:29] <Saviq> robru, ok, the invalid links should be stripped, then, if possible :)
[10:29] <Saviq> same with version links pointing to void
[10:29] <robru> Saviq: what?
[10:29] <Saviq> robru, https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-021/excuses.html
[10:30] <robru> What broken links?
[10:30] <Saviq> robru, "amd64", "0.4.7+16.04.20151214.1-0ubuntu1"
[10:30] <Saviq> for qtmir-gles in this case
[10:31] <robru> Saviq: links work for me, not sure what you're seeing
[10:31] <Saviq> robru, v
[10:31] <Saviq> https://launchpad.net/ubuntu/+source/qtmir-gles/0.4.7+16.04.20151214.1-0ubuntu1
[10:32] <Saviq> that version is nowhere in ubuntu yet
[10:32] <Saviq> robru, and as you said, http://autopkgtest.ubuntu.com/packages/q/qtmir-gles/xenial/amd64/ does not show results for silo tests
[10:32] <Saviq> both are links out of silo excuses
[10:33] <robru> Saviq: hmm, you'll have to raise that with pitti, he maintains the code that generates that page.
[10:33] <Saviq> ok, not important enough :)
[10:35] <Saviq> robru, can you tell when are they ran? only before publishing or for all builds in silo?
[10:36] <Saviq> (/me only found first in mir QA-Granted silo)
[10:37] <robru> Saviq: currently they are only run if the qa state is "ready for qa" buy that will change soon, we're working out how to streamline the process a bit
[10:37] <robru> Saviq: oh hmmm if qa granted that means the excuses will stop updating ;-)
[10:38] <Saviq> robru, sneaky
[10:39]  * Saviq thought silo 21 was waiting for a +1 from autopkgtests, but will it ever get it, then?
[10:39] <robru> Saviq: yeah if it's in granted state the page will never update
[10:40] <robru> Saviq: ideally qa shouldn't grant before the tests are passing, this is what i mean by the process needing streamlining ;-)
[10:40] <Saviq> robru, agreed, ideally we shouldn't put "ready for QA" unless it's passing, chicken'n'egg! :)
[10:41] <Saviq> robru, all in all, best xmas gift ever! :)
[10:41] <robru> Saviq: yeah i need to invent a new state that means "lander approved, go for autopkgtests" and then it only promotes to ready if the tests pass
[10:41] <robru> Saviq: thanks! That was a huge project!
[10:42] <Saviq> and a surprise, too ;)
[10:54] <Mirv> I wonder what's up with my silo publishing to xenial
[10:54] <Mirv> https://ci-train.ubuntu.com/job/ubuntu-landing-025-2-publish/lastSuccessfulBuild/artifact/packagelist_rsync_ubuntu-landing-025/*view*/
[10:55] <Mirv> sil2100: did you have any visibility to what happens after ^ or would we need eg cj_watson?
[10:56] <sil2100> Mirv: hmm, sadly not, I don't think our copy2distro scripts have user-visible logs (I think)
[10:57] <sil2100> Strange that it would get rejected
[10:58] <Mirv> cjwatson: could you check the above ^ rsync, not found in any queue
[10:58] <Mirv> sil2100: well it's not rejected either, more like these /dev/null:s for some reason
[10:58] <sil2100> By rejected I mean rejected by the script too, but hmmm
[11:00] <cjwatson> it should have mailed whatever the address of the requesting bot is
[11:01] <Mirv> sil2100: did we still have anyone with access to the bot emails..
[11:05] <cjwatson> Odd, I'm not seeing any cicopy logs from today
[11:05] <cjwatson> Oh, I bet it's locked
[11:05]  * cjwatson clears the lock
[11:06] <cjwatson> Mirv: may work in a few minutes
[11:08] <Mirv> ok
[11:14] <cjwatson> Mirv: that seems to have sorted it out; the train should catch up in a bit
[11:14] <cjwatson> I removed /tmp/.cu2d.lock on snakefruit, which was stuck after the train incident last night
[11:22] <bzoltan_> sil2100:  The issues pointed out by seb128 are fixed in the silo60 UITK and the new build is all fine. Would you please publish the packages. I have no right to publish the ubuntu-theme
[11:24] <sil2100> bzoltan_: let me just grab my food and publish, since I'm done with OTA-8.5 now :)
[11:24] <bzoltan_> sil2100: are you? Congratulations for that!
[11:25] <seb128>  bzoltan_, small issue (not need to respin for that), usually the -dev depends on the lib (= ${binary:Version})
[11:26] <bzoltan_> seb128:  I will fix that for the next release (eta tomorrow). Thank you.
[11:26] <Saviq> trainguards, can we publish https://requests.ci-train.ubuntu.com/#/ticket/725 please? or is it waiting on something?
[11:29] <seb128> bzoltan_, thanks
[11:32] <Mirv> cjwatson: looks good, thanks! there were indeed another landing stuck  there too but they're now all in
[11:33] <Mirv> Saviq: a core-dev, so sil2100 could publish it
[11:33] <Mirv> I pinged RAOF earlier but he was probably already gone
[11:33] <cjwatson> Mirv: right, ubuntu-push too
[11:34] <Saviq> Mirv, ah, tx
[11:37] <seb128> xavigarcia, charles, could you look at bug #1502094 for indicator-sound? it's probably just changing gee-1.0 to gee-0.8  in the Makefile and debian/control, would be nice to have that done in one of the next landings if we can
[11:37] <sil2100> Saviq: on it in a minute, was a bit busy in the morning ;)
[11:37] <seb128> xavigarcia, charles, and yeah, the versionning is backward, 1.0 is old and 0.8 newer
[11:41] <xavigarcia> seb128: sure, I will take a look
[11:42] <seb128> xavigarcia, thanks
[11:42] <seb128> xavigarcia, it's probably trivial, https://code.launchpad.net/~seb128/unity-lens-files/use-gee-0.8/+merge/280696 is one example
[11:43] <xavigarcia> seb128: I see... I need to check the state of the repository, though, as we had a rolled back landing last month
[11:43] <xavigarcia> seb128: and it seems we are delaying some fixes in the sound indicator until a pulseaudio issue is fixed
[11:44] <seb128> k
[11:44] <seb128> well no hurry
[11:44] <seb128> that needs to be done for the LTS
[11:46] <xavigarcia> seb128: okay
[11:54] <sil2100> seb128: hey! Have time for another binNEW ;) ? This time quite trivial as it's a standard mir soversion bump: https://ci-train.ubuntu.com/job/ubuntu-landing-021-2-publish/1/artifact/mir_xenial_packaging_changes.diff
[11:54] <seb128> +1
[11:55] <seb128> (are we sure the .pc removed is not used?)
[11:56] <seb128> lunch now, bbiab
[12:16] <kdub> trainguards, silo 21 is still undergoing testing, found an 11th hour bug... please don't publish just yet
[12:17] <sil2100> Saviq, Mirv: ^
[12:17] <sil2100> I wanted to publish but wanted one of the merges approved, and good thing it was unapproved as it wasn't ready for release ;)
[12:17] <sil2100> seb128: thanks! :)
[12:18] <Mirv> thanks kdub
[12:18] <kdub> I'm not sure how it went to QA granted yet, it was toggled to "QA needed" briefly, and then back to "QA required" a few minutes later when the bug was found
[12:23] <sil2100> We had a train derailment, maybe it got switched back then
[13:45] <Saviq> sil2100, kdub, ack :(
[14:13] <Saviq> "jenkins is preparing to shut down", should I not start jobs?
[14:14] <Saviq> or will they just get picked up when it's back up again?
[14:17] <jhodapp> sil2100, the release notes for OTA 8.5 don't mention background playlists in media-hub
[14:18] <sil2100> jhodapp: ah, right, we had to pull that in with the fixes, right?
[14:18] <jhodapp> sil2100, yes indeed
[14:36] <jhodapp> sil2100, can you please dput the qtmultimedia source pkg from ppa:jhodapp/ubuntu/ppa to silo 34 please?
[14:37] <sil2100> jhodapp: sure
[14:37] <jhodapp> ooh, double please :)
[14:37] <jhodapp> thanks
[14:38] <fginther> nerochiaro, the lp:camera-app/staging and lp:qtubuntu-camera/staging branches are now setup. Please let us know if there are any changes necessary
[14:40] <jhodapp> sil2100, let me know when I can do a watch only build on that silo
[14:41] <nerochiaro> fginther: where do i get the packages ?
[14:41] <sil2100> jhodapp: 5.4.1-1ubuntu19, right?
[14:42] <jhodapp> yes
[14:42] <sil2100> jhodapp: ah, we'll need the ~overlay1 appended, right? Can I do it, or do you keep normal versioning for the overlay?
[14:42] <Mirv> charles: you've held to this silo for two months, do you still need it or can it be abandoned to free up silos? https://requests.ci-train.ubuntu.com/#/ticket/507
[14:42] <jhodapp> sil2100, hmm, robru has never had to do that before
[14:43] <sil2100> Not sure what's the notation for qt packages
[14:43] <jhodapp> sil2100, pretty sure he just uploaded it as is
[14:43] <sil2100> Mirv: hey! You append ~overlay to qt packages released to the overlay? I don't think so, right?
[14:44] <Mirv> sil2100: usually nowadays yes, like the today's qtdeclarative was ~overlay2
[14:44] <sil2100> hm hmmm
[14:44] <Mirv> and same for qtbase + qtpim
[14:44] <sil2100> Ok, so let's do it here too
[14:44] <sil2100> jhodapp: no worries, taking care of it :)
[14:44] <Mirv> sil2100: here as in where?
[14:45] <jhodapp> sil2100, thanks!
[14:45] <jhodapp> Mirv, a new qtmultimedia upload from me
[14:45] <sil2100> Mirv: qtmultimedia-opensource-src
[14:45] <Mirv> sil2100: jhodapp: ah ok, yes, better there too
[14:45] <jhodapp> Mirv, and all of these changes are already upstreamed :)
[14:45] <sil2100> \o/ ;)
[14:46] <jhodapp> Mirv, would you be able to push the -gles package after sil2100 is done?
[14:46] <jhodapp> silo 34
[14:47] <Mirv> jhodapp: great! I hope all of them would be soon merged too in upstream so that we know they're happy with them
[14:47] <sil2100> jhodapp: ok, package pushed
[14:47] <Mirv> jhodapp: ok
[14:47] <jhodapp> Mirv, they already are happy with them, they just literally need to merge it
[14:47] <jhodapp> thanks sil2100
[14:51] <Mirv> jhodapp: I've bookmarked the following three at least: https://codereview.qt-project.org/#/c/138927/ + https://codereview.qt-project.org/#/c/142109/ + https://codereview.qt-project.org/#/c/142334/ all need formal code-review approval, after which you can also yourself click a button to try merging them to staging
[14:52] <Mirv> anyway, let's hope they're getting there soonish
[14:53] <jhodapp> Mirv, yes they're in Yoann's hands
[14:54] <Mirv> jhodapp: btw I'm not sure if you noticed but tsdgeos filed bug #1523407 - since Unity 8 is doing dual landings (=same code for vivid + xenial), they will need the code to be exactly as it is in upstream also for xenial before they can start utilizing features. so there's some work for January there, to make vivid even more identical upstream and then of course syncing up everything to xenial
[14:55] <Mirv> and I think it was the comment #1 that they then agreed is the correct way, unlike what Albert wrote in the description :)
[14:55] <Mirv> otherwise xenial would need to lie about its version
[14:55] <jhodapp> Mirv, yes that's a story currently in progress for my team's current sprint
[14:55] <sil2100> jhodapp: yw!
[14:56] <Mirv> jhodapp: ok! anyway, uploading the gles now to the same silo
[14:56] <jhodapp> Mirv, thanks!
[14:56] <jhodapp> Mirv, we did the first steps already of syncing media-hub and gstreamer versions across vivid and xenial, next comes the higher level stuff like qtmultimedia and qtubuntu-media
[14:58] <fginther> nerochiaro, oh, let me fix that
[15:00] <Mirv> jhodapp: ok, I noticed the gstreamer ones. I think with time you could even move to dual landings (or even the next one could be such potentially).
[15:00] <Mirv> the teams that are doing those generally seem pretty happy with the less complexity
[15:01] <jhodapp> Mirv, yes indeed
[15:01] <jhodapp> Mirv, oh I really want to get there, it is a little annoying because we used to be told to just ignore wily landings
[15:01] <jhodapp> now it's the opposite
[15:36] <fginther> nerochiaro, I fixed the missing debs. I've retriggered the build for https://code.launchpad.net/~uriboni/camera-app/no-permissions-dialog/+merge/279260
[15:36] <nerochiaro> fginther: ok, so every MR that is submitted against these two branches will have packages rebuilt automatically and jenkins will post a note on the MR ?
[15:37] <fginther> nerochiaro, yes, that should all be working now
[15:37] <nerochiaro> fginther: thanks
[15:39] <jhodapp> jibel, does this bug only happen on arale or have you seen it on krillin as well? https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1479036
[16:19] <jibel> Mirv, why do we need silo 5 at all on the overlay? it has nothing to do with the phone, does it?
[16:29] <tvoss> trainguards, I would need a silo for https://requests.ci-train.ubuntu.com/#/ticket/793
[16:29] <tvoss> sil2100, Mirv ^
[16:29] <sil2100> On it!
[16:29]  * tvoss making sure the request is seen
[16:30] <Saviq> trainguards, what does "Diff missing" mean when in silo status for a set of packages?
[16:33] <seb128> can we get the ubuntu-ui-toolkit/ubuntu-themes silo force merged?
[16:33] <sil2100> Saviq: not sure what causes that to happen, but usually a DIFF_ONLY build should help in that case
[16:33] <seb128> I want to do another ubuntu-themes landing today before holidays and it's getting tight ... that one already migrated but I guess no way to force merge one component only?
[16:34] <seb128> uitk is still doing autopkgtests
[16:34] <Mirv> jibel: it's for people like kenvandine who run overlay on their desktop for development purposes.
[16:34] <sil2100> seb128: yeah, no standard way of doing that, safest bet is to merge everything
[16:34] <seb128> sil2100, can you do it?
[16:35] <sil2100> seb128: let me look into that
[16:35] <Saviq> sil2100, I think it might be a failed build job causing it
[16:36] <sil2100> seb128: hmm, I see it's landed, the changes should be merged?
[16:36] <sil2100> https://requests.ci-train.ubuntu.com/#/ticket/778 ?
[16:36] <Mirv> Saviq: train's diffs are not there. either run build job normally or with DIFF_ONLY for a no-op
[16:36] <Saviq> I just had a build with that bombed because of conflicts
[16:36] <Saviq> Mirv, ack
[16:38] <sil2100> seb128: hmm, interesting! The landing didn't have an ubuntu-theme merge in it
[16:38] <seb128> hum?
[16:38] <sil2100> seb128: or maybe it did but during the train outage it got nuked...
[16:38] <sil2100> seb128: it did have the ubuntu-theme package tho
[16:38] <seb128> so we need to manually merge?
[16:39] <seb128> https://code.launchpad.net/~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-xenial-landing-060
[16:39] <seb128> sil2100, ^
[16:39] <sil2100> I suppose we need to manually merge as the train obviously forgot about this merge completely
[16:39] <sil2100> A bzr push --overwrite is what the train usually does
[16:40] <seb128> k, I can do that that
[16:41] <sil2100> seb128: thanks! And sorry for this, I suspect the derailment to be the cause of this situation
[16:42] <renatu> trainguards, could you assign this silo for me? https://requests.ci-train.ubuntu.com/#/ticket/794
[16:42] <sil2100> renatu: assigning!
[16:45] <renatu> sil2100, thanks
[17:33] <jibel> bfiller, renatu silo 55 approved
[17:35] <bfiller> jibel: thanks
[17:37] <bfiller> jibel: looks like 45 landing as well, hope we don't have to rebuild 55 as 45 has address book as well?
[17:52] <bzoltan_> trainguards: I would like to ask for a silo  - https://requests.ci-train.ubuntu.com/#/ticket/796
[17:54] <bzoltan_> Mirv: sil2100: ^
[18:14] <bzoltan_> Is here a trainguard at this hour?
[18:44] <Mirv> bzoltan_: all 60 are assigned right at the moment
[18:44] <Mirv> bzoltan_: I'll clean my qtdeclarative one since I follow up it anyway
[18:46] <Mirv> bzoltan_: ok you have silo
[18:47] <Mirv> bzoltan_: kicked a build too
[18:53] <bzoltan_> Mirv:  thank you!
[20:40] <dobey> trainguards: can i get a retry on https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-041/+build/8448901 please?
[20:47] <robru> dobey: on it
[20:50] <dobey> robru: thanks
[20:50] <robru> dobey: yw


[05:37] <Logan_> ScottK: I'm looking at the build log for armhf, and I'm not seeing the issue...
[05:42] <Logan_> Responded on LP.
[08:15] <dholbach> good morning
[12:20] <yuckfou> I have a noob question: If I package a new software will it only be included in the universe of raring? Or is there a way to include it to older versions too, like precise ?
[12:21] <Zhenech> you could offer backports via a ppa
[12:21] <Laney> hmm?
[12:21] <Zhenech> or even real backports, if its really worth it
[12:21] <Laney> you could offer backports via -backports, indeed
[12:23] <yuckfou> no i think it will not be so much in use. on sourceforge there are 100 downloads per months. so i think i will put that into my ppa. thanks.
[12:41] <yuckfou> if a [need-packaging] bug in LP is assigned to MOTU, can I assign it to myself, or does that mean that a MOTU guy will will do that?
[12:46] <geser> yuckfou: have you a bug number to check?
[12:47] <yuckfou> there are many. for example this one: https://bugs.launchpad.net/ubuntu/+bug/99299
[12:50] <geser> yuckfou: Assign it to you if you want to work in it. Having such a bug assigned to MOTU doesn't make much sense (IMHO).
[12:51] <yuckfou> Yes it also appeared strange to me. ok thanks for the info
[13:27] <yuckfou> in Testdrive: I want to have a daily update of the raring ISO. So when I launch it in the virtual machine, should I click "Try Ubuntu" or "Install Ubuntu" ?
[17:48] <ESphynx> 'afternoon :)
[17:58] <jtaylor> wtf why is there a scilab upload in proposed ...
[17:59] <jtaylor> untested before upload of course ._.
[18:00] <jtaylor> oh well that at least saves me from filing an ffe
[18:00] <jtaylor> as now it counts as bugfix right?
[19:27] <jtaylor> hm my mail to the pyqt list has still not appeared :(
[19:34] <Logan_> ScottK: I'm turning that FFe into a merge per what you said about the armv7l target - testing it out in my PPA now.
[19:35] <ScottK> Logan_: I don't know for sure either way, all I'm saying is you need to check the build logs "It built" is not sufficient.
[19:36] <Logan_> I just figured that the only reason they added the target was because it wasn't building on armel, and, since it now builds on armhf, I figured it was unnecessary. But let's see if it builds in the PPA with the armv7l target.
[19:36] <Logan_> I might contact the person who added the target to see if he thinks it's necessary, but he hasn't been active on LP recently.
[19:38] <ScottK> I think you'll be able to tell from comparing the build logs.
[19:39] <Logan_> Okay, cool.
[19:40] <ESphynx> ScottK: So my 64 bit support Ecere version is in raring-proposed. But it broke ppc builds... (but fixes amd64)
[19:40] <ScottK> Fix it then ...
[19:40] <ESphynx> ScottK: I'm guessing there are more amd64 users than ppc users though? :)
[19:40] <ESphynx> ScottK: I have a SunSPARC here (also big endian) that I plan to set up today...
[19:40] <ScottK> Right, but you should be able to make it work fr both ...
[19:41] <ESphynx> ScottK: I should and I will, just not sure when :P but I'm gonna try to get it running on the SPARC this weekend and then we can retry the build on the ppc buildbot...
[19:41] <ESphynx> ScottK: but if I do get it running within a week, it can still make it?
[19:46] <ScottK> For a bug fix like that, certainly
[19:50] <ESphynx> cool. I'll try on the SPARC, and otherwise I'll try to get my hands on a PPC
[19:51] <ESphynx> thanks
[21:24] <sharms> if my screen brightness lowers fine via echo to /sys/class/backlight/acpi_video/brightness, but my hot keys do not, which package should I look to fix it in?
[21:42] <chilicuil> sharms: it may be gnome-settings-daemon.., but it could also be other package.., I'd suggest to look at: https://wiki.ubuntu.com/Hotkeys/Troubleshooting
[22:13] <arand> How likely is it for an updated leaf game package to get into Raring at the moment, 10% or just zilch? (I'm looking for sponsors for experimental atm)
[22:26] <ScottK> arand: For a game, probably pretty decent.
[22:27] <arand> Ok, then I'll scale the nagging of sponsors accordingly :)


[14:56] <airurando> afternoon
[14:56] <airurando> wishing you all an enjoyable festive season!
[14:59] <zmoylan-len> hi
[14:59] <zmoylan-len> all crimbo shopping sorted?
[15:01] <airurando> just about
[15:02] <airurando> what about yourself zmoylan-len
[15:02] <zmoylan-len> being athiest means i save a fortune on crimbo pressies :-)
[15:03] <airurando> forgot about that
[15:03] <airurando> lucky you
[15:03] <zmoylan-len> though i am checking to see if my nephew would be interested in a rasp pi
[15:04] <airurando> Santa is bringing one to oisin. Orla gets a laptop
[15:04] <airurando> oisin is getting a nexus 7 also
[15:05] <zmoylan-len> odd, my nephew is also called oisin
[15:05] <airurando> ha ha
[15:05] <airurando> popular name
[15:05] <zmoylan-len> oisin and owen.  pretty sure it's oisin that's the geeky one
[15:06] <airurando> you better get that right
[15:06] <airurando> ;-)
[15:06] <zmoylan-len> ah, i'll just tell my brother to hand it to the geeky one. :-)
[15:07] <airurando> :-)
[15:08] <airurando> tell me how easy/hard will it be to dual boot a new dell laptop with win8 on it?
[15:08] <airurando> I never understood that secure boot stuff.
[15:09]  * zmoylan-len is currently rebuilding my main media drive after accidently erasing it making dual boot work 'properly'
[15:09] <airurando> oh dear
[15:10] <airurando> :-(
[15:10] <zmoylan-len> i finally got linux installed on lenovo win 8 afflicted computer.  but it was awkward
[15:11] <zmoylan-len> when i used bios it booted linux and when i used uefi it booted windows.  i followed instructions to make uefi, win8 and linux to all get along and it never booted again and erased media drive
[15:11] <airurando> hmmmm
[15:12] <zmoylan-len> i saw it as natures way of saying stop using windows.  which i only used for itunes anyway.  so have ditched windows and am now 100% linux
[15:12] <zmoylan-len> even my mac has been cleared off to keep me away from itunes
[15:12] <airurando> :-)
[15:12] <airurando> itunes has a hold on me also
[15:13] <zmoylan-len> linux has no substitute, nor android.  writing a partial replacement for own use in perl at mo.
[15:13] <zmoylan-len> the file shuffling part that allows you to watch a tv show on an idevice
[15:14] <airurando> I probably won't be messing with my daughters laptop for a while so as all you have said demonstrates that dual booting is way above my skill level on newer hardware
[15:14] <airurando> http://www.dell.com/ie/p/inspiron-15-3521/pd
[15:15] <airurando> that one with the core i3 processor
[15:15] <zmoylan-len> i intend to get an oxfam laptop with win7 to dual boot.   http://www.oxfamireland.org/computers/laptop-plus
[15:16] <zmoylan-len> win8 is deliberatly knobbled to make dual boot with linux horrible.
[15:16] <tdr112> hey airurando
[15:16] <airurando> nice zmoylan-len
[15:17] <tdr112> zmoylan-len: that happen to me
[15:17] <airurando> hi tdr112
[15:17] <zmoylan-len> cheap, high end business laptops in decent nick.  i've seen 2 so far. very nice
[15:17] <tdr112> wasted a day on it trying to get it to work , just got rid of win 8 and runing stuff in a vm
[15:18] <zmoylan-len> can't create a vm without an install disk though
[15:18] <tdr112> hey airurando, kids going mad yet
[15:18] <zmoylan-len> on a laptop
[15:18] <tdr112> zmoylan-len: i have a vm of vista
[15:18] <airurando> tdr112:  yip
[15:18]  * zmoylan-len is not sure if that's better or worse than win8 :-D
[15:20] <tdr112> zmoylan-len: have not used it for 20 days, just using wine more and more
[15:20] <zmoylan-len> itunes doesn't work in wine
[15:20] <tdr112> airurando: how goes the dojo
[15:20] <zmoylan-len> or rather it loads, but it doesn't actually work
[15:21] <airurando> tdr112: great. on Christmas break at the moment.  Orla has taken to scratch really well.  Oisin still a bit young.
[15:22] <tdr112> airurando: Do you help out, when your off ?
[15:27] <airurando> tdr112:  as much as i can.  They are getting to a point beyond my current abilities
[15:28] <airurando> Orla is on her own.
[15:28] <airurando> I can help the newer folks a bit
[15:33] <tdr112> airurando: but its not chlid care, parents do hang around ?
[15:34] <airurando> yes they do
[15:34] <airurando> it is real good here in athy but it is early days yet
[15:35] <airurando> from the parents I get the impression that they are very greatful to the mentors for providing their kids with the opportunity
[15:36] <airurando> it clashes with alot of things on a sat morning but kids and parents are picking the coder dojo over those other activities
[15:36] <airurando> again though it is early days
[15:37] <airurando> as long as my kids want to go I'll support and encourage them but I won't force them
[15:44] <airurando> crikey it is pouring rain here.
[15:45] <zmoylan-len> train station down south closed https://twitter.com/cybernoelie/statuses/413325728038805504
[16:04] <airurando> aye the mother in law is trapped on the train from cobh
[16:55] <zmoylan-len> pics of the train from cobh with debris on roof.  https://pbs.twimg.com/media/Bbx9oSnIMAE3WEL.jpg