[01:03] <Coringao> kiko-zzz, ola colega ..blz?
[01:09] <Coringao> kiko-zzz, cprov  ola colegas..blz.. estou precisando de uma ajuda sua no Launchpad, pode me ajudar?
[01:15] <Coringao> cprov, ola
[01:17] <cprov> Coringao: sure, what's your doubt ?
[01:17] <Coringao> cprov, fiz uma besteira no launchpad .. tava fazendo um modo de colocar o programa IUG (Instalador Ubuntu Games) no Launchpad
[01:18] <Coringao> cprov, e acabei adicionando outro launchpad do Ubuntu Games
[01:18] <Coringao> cprov, agora esta mostrando dois
[01:18] <Coringao> cprov, tem como excluir um
[01:18] <Coringao> ?
[01:19] <cprov> Coringao: sorry, but conversation in this channel has to be in English. I don't mind to help you in pt_BR in pvt.
[01:19] <Coringao> cprov, ops!! sorry
[01:25] <ubotu> New bug: #153107 in launchpad "hwdb interface does not provide a means to retrieve hardware submissions" [Undecided,New]  https://launchpad.net/bugs/153107
[01:50] <ubotu> New bug: #153112 in malone "Subscribed bug does not show in personal bug listing" [Undecided,New]  https://launchpad.net/bugs/153112
[05:32] <KeithWeisshar> i'm getting an error message when i try to reset my password
[05:32] <KeithWeisshar> on launchpad.net
[05:32] <mpt> KeithWeisshar, what does the error say?
[05:34] <KeithWeisshar> Sorry, something just went wrong in Launchpad. Weve recorded what happened, and well fix it as soon as possible. Apologies for the inconvenience.
[05:34] <KeithWeisshar> Trying again in a couple of minutes might work. If it doesnt, and this is blocking your work, let us know on the launchpad-users mailing list (requires subscription). Include the error ID OOPS-654E182 in your message.
[05:34] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/654E182
[05:34] <KeithWeisshar> i'm unable to log in with the new password that i just set to
[05:35] <KeithWeisshar> it's a timeout error
[05:35] <lifeless> win 20
[05:37] <KeithWeisshar> is there any launchpad.net admin online?
[05:38] <Hobbsee> unlikely, they're in the UK for the most part, or brazil
[05:39] <KeithWeisshar> why is the shipping to usa from shop.canonical.com so high
[05:39] <KeithWeisshar> even for regular mail
[05:39] <KeithWeisshar> the shipping is almost $10 for a $1.38 pen
[05:41] <KeithWeisshar> i forgot my launchpad.net passwore
[05:41] <KeithWeisshar> when i try to reset the password i get a timeout error that says Sorry, something just went wrong in Launchpad. Weve recorded what happened, and well fix it as soon as possible. Apologies for the inconvenience.
[05:41] <KeithWeisshar> Trying again in a couple of minutes might work. If it doesnt, and this is blocking your work, let us know on the launchpad-users mailing list (requires subscription). Include the error ID OOPS-654E182 in your message.
[05:41] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/654E182
[05:42] <KeithWeisshar> ID OOPS-654E182
[05:42] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/654E182
[05:42] <KeithWeisshar> ID OOPS-654E182
[05:42] <ubotu> https://devpad.canonical.com/~jamesh/oops.cgi/654E182
[05:44] <KeithWeisshar> can you fix the launchpad password
[05:46] <KeithWeisshar> is there a lp admin on irc
[05:46] <Hobbsee> you asked that 8 minutes ago.  i dobut the answer has changed.
[05:48] <KeithWeisshar> does freenode accept connections from uk
[05:49] <jml> yes
[05:49] <KeithWeisshar> ubuntu is located in uk too
[05:50] <Hobbsee> not quite sure that's accurate
[05:50] <Hobbsee> but the data centre is in the UK, yes
[05:54] <lifeless> KeithWeisshar: hi. A developer, not admin, needs to look at the error report.
[05:55] <lifeless> KeithWeisshar: if its still not working, as you say its not, please follow the instructions in the error report (contact the launchpad-users mailing list)
[07:58] <lifeless> any volunteers to run the review meeting ?
[07:58] <lifeless> thumper-office: ^ spiv ^ BjornT ^
[08:04] <jml> I'll do it. where's the agenda?
[08:05] <jamesh> hi
[08:05] <jml> = Meeting begins =
[08:05] <jml> == Roll call ==
[08:05] <thumper> here
[08:05] <jml> here
[08:05] <spiv> here
[08:05] <jamesh> here
[08:06] <lifeless> poolie is ringing me
[08:06] <lifeless> if you need me sms
[08:06] <jml> BjornT: ?
[08:06] <BjornT> me
[08:06] <jml> == Next meeting ==
[08:07] <jml> DST is sweeping its way across the southern hemisphere.
[08:07] <jml> But I don't think we need to change the time for next week
[08:07] <thumper> +1
[08:07] <thumper> perhaps after all hands...
[08:07] <jml> Excellent. It is decided.
[08:07] <spiv> Yeah.
[08:08] <jml> == Action items ==
[08:08] <jml> Nothing listed in previous minutes
[08:08] <jml> I wasn't at the meeting though.
[08:08] <jml> Anything worth mentioning?
[08:08] <thumper> wasn't there an email from SteveA somewhere?
[08:08] <jml> Oh right.
[08:09] <jml> that was a view / tal thing.
[08:09] <thumper> properties for no-arg funcs
[08:09] <jml> I'll look after the meeting to confirm that it was added to the relevant wiki checklist
[08:09] <thumper> +1
[08:09] <spiv> About using properties rather than no-arg functions on view classes, iirc.
[08:09] <jml> ACTION: jml confirm above.
[08:09] <thumper> I'm for adding it to the checklist
[08:09] <jml> Moving along!
[08:09] <jml> Queue status
[08:09] <spiv> Me too.
[08:09] <jml> *ahem*
[08:10] <jml> == Queue status ==
[08:10] <thumper> the script seems somewhat behind
[08:10] <thumper> the two oldest are mine and were both finished a number of hours ago
[08:10] <jml> The needs review queue is big, red and out of date
[08:10] <thumper> I have one other still in progress
[08:11] <thumper> :)
[08:11] <jml> I count 30+ on the wiki page.
[08:11] <jml> Anyone here have any overdue branches?
[08:11] <spiv> I do.
[08:11] <jml> spiv: oh really? ;)
[08:11] <spiv> But you'd know that, as one of them is for you ;)
[08:12] <thumper> I have only one red and I'm working on it
[08:12] <spiv> And the other is a branch that's returned from needs-reply.  They should both be done today.
[08:12] <jml> jamesh, BjornT: how are your reviews going?
[08:12] <jml> I've just bounced the last one of mine.
[08:13] <BjornT> jml: quite good, non are overdue (almost cleared my queue yesterday)
[08:13] <jml> sweet
[08:13] <jamesh> jml: okay.  I've also got to mentor-review a few of jtv's ones
[08:14] <jml> that segues neatly into the next item
[08:14] <jml> == Proposal: needs-mentoring ==
[08:14] <jml> I get the feeling that this agenda wasn't updated last week.
[08:14] <jml> Has this been resolved at all? The thread seemed long, inconclusive and slightly bike-sheddy.
[08:15] <BjornT> that's right, and no progress has been made since the last meeting.
[08:16] <jml> ok. Probably the thing to do is to get Barry to make a decision and we can go with that.
[08:17] <jml> (Barry is review team lead, right?)
[08:17] <spiv> I agree.  Pretty much all the interesting points I can think of have already been discussed, so it just needs someone to make a decision.
[08:17] <jml> excellent.
[08:18] <jml> == Mentoring update ==
[08:18] <jml> everyone here except me is a mentor -- how's it going?
[08:18] <BjornT> i'm not a mentor
[08:19] <jml> oops.
[08:19] <spiv> Busy all of a sudden :)
[08:19] <jml> spiv: haha
[08:20] <jml> I have nothing else to say.
[08:20] <spiv> Nothing much for me to remark on though, it seems to be going smoothly enough.
[08:21] <jml> Oh, I see there were actions from the last meeting, but none of them concern anyone present.
[08:21] <jml> spiv: good to hear :)
[08:21] <jml> Please take a look at them now so you know how to deal with our next segment.
[08:21] <jml> == Any other business? ==
[08:21] <thumper> nope
[08:22] <jml> excellent
[08:22] <jml> 5
[08:22] <jml> 4
[08:22] <jml> 3
[08:22] <jml> 2
[08:22] <jml> 1
[08:22] <jml> = Meeting ends =
[08:22] <thumper> jml: thanks, and don't forget the minutes :)
[08:22] <jml> Thank you all for coming
[08:22] <jml> thumper: I shan't
[08:24] <lifeless> thanks jml
[08:30] <ubotu> New bug: #153189 in launchpad "Visiting +retry-url does not retry build" [Undecided,New]  https://launchpad.net/bugs/153189
[08:32] <carlos> morning
[09:35] <ubotu> New bug: #153199 in malone "No indication of quality of service for addressing/closing a project's bug reports" [Undecided,New]  https://launchpad.net/bugs/153199
[10:09] <baijum> Hi
[10:10] <baijum> Is it possible to disable Launchpad Janitor ?
[10:10] <mwhudson> baijum: it is disabled
[10:10] <mwhudson> the recent run was a mistake
[10:10] <baijum> mwhudson, ok, thanks !
[10:22] <soren> Did the details portlet get removed from edge.lp.net/~whoever/+participation get removed today or have I just not noticed it before?
[10:23] <soren> er...
[10:23] <soren> Bah, you know what I mean :)
[10:23] <Fujitsu> soren: You mean the person details?
[10:23] <soren> Yup
[10:24] <Fujitsu> I'm sure it was there a few days ago. It looks empty now, I guess 'cause it's all green.
[10:24] <mpt> soren, it was removed in the past day
[10:24] <soren> mpt: Mkay..
[10:29] <soren> I've heard rumors that there is a way to fetch the contents of a portlet on launchpad without having to fetch the entire page.. Could someone fill me in on this?
[11:31] <ubotu> New bug: #153230 in soyuz "/~person/+packages times out even for people without any uploads" [Undecided,New]  https://launchpad.net/bugs/153230
[12:55] <ubotu> New bug: #153250 in malone "Disable bug expirations for a project" [High,Confirmed]  https://launchpad.net/bugs/153250
[12:55] <ubotu> New bug: #153251 in launchpad "Please add foaf:nick to team RDF" [Undecided,New]  https://launchpad.net/bugs/153251
[01:08] <stu2> intellectronica: How did structural subscription discussions go with Mark?
[01:09] <intellectronica> stub: why here?
[01:35] <ubotu> New bug: #153258 in launchpad "Delete Google search results concerning your name" [Undecided,New]  https://launchpad.net/bugs/153258
[01:43] <mwhudson> now _that's_ a wtf type bug
[01:44] <mwhudson> report
[01:44] <Ng> hehe, yeah
[01:44] <Ng> I put my name on a website and now the web can see it!
[01:44] <Ng> I recommend having a name that's absurdly popular :)
[01:46] <mwhudson> heh
[01:47] <mwhudson> the suggested solution is also quality
[01:47] <mwhudson> oh, hm
[01:47] <mwhudson> i misread that bit
[01:54] <ddaa> well
[01:55] <ddaa> it's true that launchpad is a very effective googlebomb
[01:55] <ddaa> I believe the real problem is the multiple hosts
[01:56] <ddaa> people get one google hit for launchpad.net, one for bugs.launcphad.net, one for answers.launchpad.net, one for code.launchpad.net, one for translations.launchpad.net, and one for blueprints.launchpad.net
[01:56] <ddaa> if they only got one hit, they probably would not mind that much
[01:56] <ddaa> See: http://www.google.com/search?ie=UTF-8&oe=UTF-8&sourceid=navclient&gfns=1&q=Felix+Heinonen
[01:57] <ddaa> The whole first page of google results is the person's page in various facets
[01:58] <ddaa> it was discussed at length before, and no real conclusion came out
[01:58] <ddaa> in my personal opinion (that does not represent the official position of canonical, launchpad, or any affiliate ;)
[01:58] <ddaa> we should just back out from the "multiple hostnames" scheme
[01:59] <kiko> !
[02:08] <gnomefreak> is there a way to get LP admin to change owner of a team if the owner had removed himself from team (also been gone for months) change owner to me(as im the only admin for the team atm) so i can make a few other admins
[02:09] <kiko> gnomefreak, which team is it?
[02:09] <gnomefreak> https://edge.launchpad.net/~mozillateam
[02:09] <gnomefreak> kiko: also https://edge.launchpad.net/~mozilla-bugs
[02:10] <gnomefreak> same situation
[02:14] <kiko> gnomefreak, done.
[02:16] <gnomefreak> ty
[02:44] <kiko> LaserJock, siretart: ping
[02:53] <Hobbsee> hiya kiko
[02:53] <kiko> I'm back :)
[02:53] <Hobbsee> what, already?
[02:54] <kiko> yeah, it was only 2 days
[03:00] <siretart> kiko: pong
[03:36] <ubotu> New bug: #153299 in launchpad "please provide printable view or PDF export for Answers" [Undecided,New]  https://launchpad.net/bugs/153299
[03:36] <kiko> wow, PDF export!
[03:38] <intellectronica> we could just export as latex and let the users process it :)
[03:54] <evarlast> 0nice
[03:54] <evarlast> LaTeX <3
[04:06] <ddaa> LaTeX is sooo last-century
[04:07] <ddaa> Maybe export to ReST, or some ML that can be converted to LaTeX.
 What should rt do with HTML mail?
 Send a reply in DVI
[04:09] <mwhudson> hm, that wasn't quite as appropriate as i remembered :)
[04:09] <mwhudson> still a good quote...
[04:09] <Spads> ddaa: reST needs a way to generate PDFs without going via LaTeX
[04:09] <Spads> ddaa: it'd be nice if it could generate scribus files or something
[04:10] <ddaa> Spads: I can only concur with that. The beauty of using an intermediate code such as ReST is that we can make it Someone Else's Problem.
[04:13] <siretart> ddaa: sssh, it is still popular in academics ;)
[04:13] <ddaa> siretart: I used to be a core dev of http://www.texmacs.org
[04:15] <siretart> uh, impressive :)
[04:16] <ddaa> I mean, I know a lot about LaTeX prevalence in academia, since this project is (among other thing) a competitor of LaTeX.
[04:20] <ddaa> In some fields, journals and book editors will require articles to be LaTeX documents using some custom stylesheet.
[04:20] <ddaa> Other fields are married to MS/Word.
[04:23] <ddaa> Also, scientists find a (pervert IMO) pleasure mastering TeX/LaTeX arcana. So I do not expect those niches are going to migrate away from LaTeX, ever.
[04:23] <siretart> indeed
[04:24] <ddaa> By the time people get into decision-making positions they have a thorough Stockholm syndrom with LaTeX.
[04:26] <Spads> it's basically sendmail all over again
[04:34] <ddaa> Do not get me wrong. LaTeX was revolutionary, 30 years ago.
[04:36] <ddaa> But even Leslie Lamport said that the future should be LaTeX-like structured documents with TeX-grade rendering in a WYSIWYG fashion.
[04:37] <ddaa> The current situation is largely a consequence of MS/Word dominance, causing stagnation in word-processing technology.
[05:09] <evarlast> You all are crazy. LaTeX is just wonderful.
[05:10] <evarlast> As an end user, I'd rather write LaTeX markup than wrestle with MS Word or Open Office Writer. I tend to loose those wrestling matches and win with LaTeX
[05:10] <ddaa> Agreed.
[05:10] <ddaa> The MS/Word-like editing paradigm sucks big time.
[05:11] <ddaa> The LaTeX-like structured document paradigm is vastly superior.
[05:11] <ddaa> They just both suck in different ways.
[05:11] <mwhudson> nevertheless latex still sucks
[05:11] <mwhudson> maybe just not as much :)
[05:11] <intellectronica> latex is great. anything else i know is a compromise on quality
[05:12] <ddaa> TeX's design dates from a time where computers were a lot smaller and a lot more expensive than they are today.
[05:12] <ddaa> intellectronica: give TeXmacs a shot.
[05:12] <ddaa> Today, we can do structured AND beautiful AND WYSIWYG.
[05:13] <intellectronica> ah yes, i remember giving it a try a few years ago and it was pretty good. these days i don't tend to produce many printable documents anyway
[05:19] <Hobbsee> hmmm.  i'm going to love the day when launchpad gives me automatic debdiffs between releases, wiki-style.
[05:21] <evarlast> I just don't see how LaTeX "sucks". It is what it is. It is an SGML for document publication. Its NOT a WYSIWYG editor and it isn't supposed to me.
[05:22] <ddaa> evarlast: the only think that can RELIABLY parse LaTeX documents is TeX.
[05:22] <ddaa> it's not a markup language
[05:22] <mwhudson> evarlast: have you looked at the source to xypic?
[05:22] <ddaa> it's not structured, it just gives the _illusion_ of structure, and people who know TeX love to break the abstraction.
[05:23] <ddaa> I know that first-hand from working on a project which critically needs good latex import and export filters. And that's a horrible problem.
[05:24] <ddaa> It allows, even invite, people to mix logical and physical markup.
[05:24] <ddaa> oops, I ranted again.
[05:25] <evarlast> ddaa: I like rants. It is cool. I'd argue that it IS a markup language. It may not be deterministic.
[05:25] <ddaa> In short, LaTeX is NOT a document format. It's a programming language.
[05:25] <evarlast> ah!   LaTeX sucks as a markup language because it cannot be reliably parsed, and it's tied to TeX which, by design, cannot be made WYSIWYG.
[05:27] <ddaa> The notion that it's not possible to be both WYSIWYG and structured is incorrect.  Document writing needs to move into the 21st century.
[05:29] <jtv> Forsooth, thou art on crack!
[05:29] <ddaa> There's nobody named Forsooth in this channel.
[05:29] <jtv> Sigh.  Trust me to get the guy who doesn't know his classical English.  :-)
[06:05] <ubotu> New bug: #153333 in launchpad "Clean up owner and registrant attributes" [Undecided,New]  https://launchpad.net/bugs/153333
[06:19] <Odd_Bloke> Although this is _so_ one hour ago, I use LyX for the majority of my LaTeX needs. :)
[06:25] <LaserJock> kiko: pong
[08:19] <bigjools> lamont: hi
[08:53] <lamont> bigjools: howdy
[08:53] <bigjools> hey lamont - your chroot fix suggestion worked like a charm, thanks!
[08:54] <bigjools> lamont: would you be able to make me new chroots with that change for all our active distroarchseries?
[08:56] <lamont> all as in _ALL_?
[08:56] <lamont> and yes, i can do that
[08:57] <bigjools> yes - we're ditching the pocketchroot concept in favour of one chroot per d-a-s
[08:57] <bigjools> and the slave scanner will tell it which pockets it can use, as we talked about yesterday
[08:57] <lamont> ah, and LP will just force sources.list to what it should be>?
[08:58] <bigjools> yup
[08:58] <lamont> cool.  because, for instance, -security probably shouldn't be using -updates
[08:58] <bigjools> yeah, it doesn't in the new code :)
[08:58] <lamont> woot!
[08:59] <lamont> so... give me one collection of tarballs on chinstrap, and I'll give you a replacement set.
[08:59] <lamont> oh...
[08:59] <lamont> hrm.
[08:59] <lamont> does the overrides append to sources.list, or force it completely?
[08:59] <bigjools> see here for the deps we're using:
[08:59] <bigjools> https://lists.ubuntu.com/archives/launchpad-users/2007-October/002486.html
[09:00] <bigjools> it forces it completely
[09:01] <lamont> ok.  needed feature: there must be a way to add a non-LP archive to sources.list for bootstrapping purposes.  for bonus points, it should be painfully obvious that such a thing has happened.
[09:01] <lamont> maybe a -bootstrap pocket, which then gets the results, and can be forced for the actual build... anyway, we'll need to hammer that bit of things out.
[09:01] <bigjools> that could be arranged
[09:01] <bigjools> yeah
[09:02] <bigjools> cprov: can you grab all the active release pocketchroots for lamont and put them on chinstrap please?
[09:03] <cprov> bigjools: gutsy or all supported atm ?
[09:03] <lamont> for example, if you look in sources.list.{mult,un}iverse on several of the gutsy chroots right now, you'll find that they also look at sanae/~lamont/bootstrap (which is how we got mlton and icedtea-java7 into gutsy *verse), and that the hppa chroot fully looks at sanae/~lamont/gutsy-stage0 (bootstrapping hppa into LP)
[09:03] <bigjools> cprov: we'll need all active d-a-s when this code goes live
[09:05] <bigjools> this is going to be a lot of chroots, but look on the bright side, it's a lot LESS in the end :)
[09:05] <bigjools> or fewer, I should say
[09:25] <ubotu> New bug: #153395 in malone "E-mail interface refuses tags with "-" in their name" [Undecided,New]  https://launchpad.net/bugs/153395
[09:40] <bigjools> lamont: cprov has put the chroots on chinstrap for you
[09:40] <bigjools> chinstrap:~cprov/current_chroots/*
[09:40] <bigjools> thanks very much for helping
[09:53] <thumper> morning
[10:13] <evarlast> can I get lauchpad cloak?
[10:14] <Odd_Bloke> "ircname  : fuk" .
[10:14] <kiko> !
[10:14] <evarlast> I can change that if need be.
[10:30] <mpt> Goooooooooooood morning Launchpadders!
[10:31] <ubotu> New bug: #153406 in launchpad "feeds template doctype is incorrect" [Low,Confirmed]  https://launchpad.net/bugs/153406
[10:31] <jtv> mpt: I guess that's my cue to go to bed.  Have a good one!
[10:34] <ScottK> Would someone please explain to me what this information is supposed to mean? https://edge.launchpad.net/ubuntu/gutsy/+source/pyspf/+packaging
[10:36] <kiko> ScottK, that Ubuntu pyspf is packaged from upstream PySPF?
[10:36] <ubotu> New bug: #153407 in launchpad "feeds template needs info about date a bug was made private" [Low,Confirmed]  https://launchpad.net/bugs/153407
[10:36] <ScottK> kiko: We get it in Ubuntu from Debian.
[10:36] <ScottK> There is an uptsream eventually, but not directly.
[10:36] <kiko> ScottK, which in turn gets its code from upstream pyspf
[10:36] <ScottK> Right.
[10:37] <kiko> it doesn't matter if it's direct or not
[10:37] <ScottK> But that doesn't actually point to anything.
[10:37] <ScottK> And it can't be removed.
[10:37] <kiko> why would you remove it?
[10:37] <ScottK> Because it doesn't point to anything meaninful.
[10:37] <kiko> ScottK, it actually does. it includes the homepage to the upstream project
[10:38] <kiko> and if the upstream project had a code repo or a bug tracker
[10:38] <ScottK> Where?  I don't see any links on that page?
[10:38] <kiko> it would also allow further functionality
[10:38] <kiko> do you mean https://edge.launchpad.net/pyspf?
[10:38] <kiko> I think you're just confused by the poor UI in +packaging
[10:38] <ScottK> No.  That's not the upstream.
[10:39] <kiko> ScottK, really?
[10:39] <ScottK> I'm one of the upstream maintainers (in addition to an Ubuntu dev) and I"ve never seen that before.
[10:39] <kiko> how interesting
[10:39] <ScottK> Upstream is on Sourceforge
[10:39] <kiko> so that may be an honest mistake then.
[10:39] <kiko> what's the URL?
[10:39] <ajmitch> registered by Registry Administrators
[10:39] <kiko> (to the project)?
[10:40] <ScottK> kiko: It's part of this project: http://sourceforge.net/projects/pymilter/
[10:41] <kiko> ScottK, okay, I'll fix it up.
[10:42] <ScottK> kiko: How is it that random incorrect data like this gets filled in?
[10:43] <ScottK> An "Assume all projects use Launchpad" model doesn't seem likely to have a very high accuracy.
[10:45] <kiko> ScottK, it gets filled in when people notice unlinked packages, and it gets fixed when people complain. that's actually a pretty effective process.
[10:45] <kiko> for most packages the information is correct
[10:46] <kiko> and given that you've complained for this instance, we're improving accuracy as we speak :)
[10:46] <ScottK> I'd have preferred just to be able to remove the wrong information.
[10:46] <ScottK> That would have sucked up a lot less of my time and still been an improvement.
[10:46] <kiko> ScottK, that's a known bug. blame salgado for not fixing it for 1.1.10! :)
[10:46] <kiko> (I had scheduled it)
[10:46] <ScottK> OK.  Is it in 1.1.11?
[10:47] <kiko> seriously 1.1.10 was tricky because of ubuntu and shipit
[10:47] <salgado> what's the bug/spec?
[10:47] <ScottK> In other news, I'm still seeing launchpad janitor closing bugs.  I thought it was stopped?
[10:48] <kiko> salgado, deleting packaging?
[10:48] <kiko> ScottK, it was a crontab typo, fixed again, will be reverted.
[10:48] <ScottK> OK.  When is the reversion planned to happen?
[10:50] <ScottK> kiko: I also just noticed that the description/home page on https://edge.launchpad.net/pyspf come from an old (Dapper/Edgy) package description.  That's probably part of the error source.
[10:52] <kiko> ScottK, hmmm. but the ubuntu package has always come from pymilter?
[10:53] <ScottK> No.  The homepage for the project used to be the one listed, but since Feisty it's been pymilter
[10:53] <ScottK> The package has always come from Debian or Pymilter though.
[10:53] <kiko> okay
[10:54] <kiko> so for dapper and edgy it used to be pyspf (standalone) and from Feisty onwards it's packaged from pymilter. is that correct?
[10:55] <ScottK> Yes.
[10:55] <ScottK> Sort of
[10:56] <ScottK> It's a separate package within the pymilter project on sourceforge
[10:57] <kiko> ScottK, all in a single upstream SVN (or CVS) repository?
[10:58] <ScottK> Yes (cvs).  Pymilter itself is also in Gutsy, FYI.
[10:58] <kiko> gotcha.
[10:59] <kiko> this is interesting and useful; I have a discussion to raise with mark now.
[11:02] <ScottK> OK.  Well good luck.
[11:14] <lamont> cprov-afk: I wonder if we could populate all the unbuilt gutsy packages into gutsy-proposed. :-)
[11:15] <cprov-afk> lamont: it's not possible, it will require new uploads.
[11:15] <lamont> ah, ok.
[11:16] <lamont> spoilsport
[11:16] <lamont> :-)
[11:16] <lamont> it wasn't a completely serious idea, of course.
[11:16] <lamont> anyway, afk
[11:30] <ubotu> New bug: #153417 in soyuz "PoolFileOverwriteError on publishing vlc and pkgsel" [Undecided,New]  https://launchpad.net/bugs/153417


[09:35] <dgadomski> hi guys, can anybody from the desktop team confirm whether this is the expected behavior or in fact a bug? https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1125442
[09:35] <ubot2> Ubuntu bug 1125442 in unity "Always Visible and On Top Windows Steal Focus on Workspace Switch" [Medium,Confirmed]
[11:42] <dgadomski> hi seb128, do you have a minute to take a look at the bug I mentioned ^^?
[11:42] <seb128> dgadomski, hey, that would be a better question for bregma or Trevinho, I saw it earlier but I'm not working on compiz
[11:43] <dgadomski> seb128: I see, thank you
[11:43]  * Trevinho checking
[11:43] <seb128> dgadomski, the current behaviour doesn't feel buggy to me
[11:44] <dgadomski> seb128: looks pretty consistent to me as well, when we switch to another workspace there is only 1 window there (the one on all workspaces) to it gets the focus, then we go back and the same window remains focused - this is how I see this
[11:45] <seb128> the fact that entering a workspace with 1 dialog gives it focus sort of make sense, even if I can see how it can be annoying to some
[11:45] <bregma> seems to be something that was fixed with alll the Switcher changes that went in since 12.04
[11:46] <seb128> bregma, that's still happening in utopic, not sure it's a bug though
[11:46] <seb128> pitti, hey, do you know if datetimed is having known issue on the device on current images?
[11:46] <seb128> pitti, bug  #1360554
[11:46] <ubot2> Launchpad bug 1360554 in ubuntu-system-settings "cannot change time zone" [High,Confirmed] https://launchpad.net/bugs/1360554
[11:47] <seb128> pitti, settings didn't change, and looking a bit a it seems the helper is correctly called but hit permissions issues
[11:54] <dgadomski> bregma: do you think this could be a regression?
[12:23] <Sweetshark> Laney: You wanted me to save Munich. Well it seems to be save for now: http://linux.slashdot.org/story/14/08/24/194208/munich-council-say-talk-of-limux-demise-is-greatly-exaggerated ;)
[12:35] <pitti> seb128: not known to me yet, but certainly sounds like some regression, yes
[12:39] <seb128> pitti, do you have a phone? does it work for you?
[12:40] <ogra_> seb128, when selecting moscow on my non-mako device i properly get 16:40 in the indicator and lock screen ... pretty instantly after changing
[12:41] <ogra_> switching back works fine too here
[12:41] <seb128> ogra_, k, on mine it doesn't work, the tz is not changed and it doesn't return from the panel
[12:41] <ogra_> (image 207)
[12:43] <pitti> seb128: yes, I do (dual-boot), and the emulator too; still busy with other stuff, but will look at it
[12:47] <pitti> seb128: works fine in the emulator at least; but that's r/w by defualt, so perhaps that's why
[12:48] <pitti> but works after remounting r/o, too
[12:49] <pitti> seb128: WFM on mako too (r/o)
[12:50] <pitti> I'll think about some debugging instrucutions and follow up on the bug
[12:50] <seb128> pitti, thanks
[13:25] <ricotz> seb128, hi :), would be great if this can be revisited https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1223401
[13:25] <ubot2> Ubuntu bug 1223401 in libnotify "[0.7.6] the add_action api changed creating issues for clients" [High,Confirmed]
[13:25] <seb128> ricotz, we already discussed it, I'm still unsure what would be an appropriate solution, renaming the binary to indicate the abi change?
[13:27] <ricotz> seb128, the actual binary/library didnt change anything but gir/typelib
[13:28] <seb128> right
[13:28] <seb128> so the gir binary should be renamed?
[13:28] <seb128> otherwise you bug half the clients that rely on the old annotations
[13:31] <ricotz> seb128, adding a suffix to the fixed gir1.2 package would be an option to force a proper transition
[13:31] <seb128> right
[13:32] <seb128> do you know why Debian didn't do that?
[13:32] <ricotz> no, i guess they just gone through it
[13:33] <ricotz> if might effect not that much users
[13:46] <ricotz> seb128, so not changing any package name and rather adding some Breaks to an unpatched libnotify seems cleaner
[13:46] <ricotz> this way things like gnome-music and gnome-tweak-tool would be instantly fixed
[13:50] <seb128> ricotz, while things like unity8 would stop working...
[13:51] <ricotz> seb128, therefore the Breaks!
[13:52] <ricotz> not sure how unity8 works around the broken api now
[13:52] <seb128> the api is not broken right now
[13:53] <seb128> it's just "stable"
[13:53] <seb128> e.g we didn't change it to be incompatible
[13:53] <ricotz> it is! since this crashes clients using it that way
[13:53] <seb128> like upstream did
[13:53] <seb128> well
[13:53] <seb128> that's what happens when you change an api
[13:53] <seb128> or a public api rather
[13:53] <seb128> clients stop working
[13:53] <seb128> GNOME did a stupid thing there
[13:53] <ricotz> seb128, just stop and be constructive
[13:54] <ricotz> it isn't useful to keep it in this current state
[13:54] <ricotz> which unity8 package is actually using the notify-gir?
[13:56] <seb128> ricotz, how is that not being constructive? Debian usually handle those things better, I'm a bit disappointed they didn't rename the gir/do a proper transition
[13:56] <seb128> ricotz, the issue is that you don't know what packages are using the old api and are going to start bugging if you change the annotation
[13:56] <seb128> we can grep the archive, but what about third party, admin scripts, etc?
[13:57] <seb128> the minimum we should do is a proper transition, but even that is going to make working code stop working
[13:57] <ricotz> seb128, if packages using the gir then they should have it set as dependency otherwise i would call the packaging broken
[13:57] <seb128> ricotz, what about local scripts?
[13:57] <seb128> or stuff people write
[13:57] <seb128> changing public api is just not nice
[13:58] <seb128> that should have been handled by adding a new function and deprecating the old one
[13:58] <ricotz> seb128, those g-i api changes happen all the time, to actually fix things
[13:58] <seb128> you don't just change the number of a parameter of a function in a stable api
[13:58] <seb128> "fix"
[13:58] <seb128> sure we can wave hand and say we don't care, it doesn't make the reality different
[13:58] <ricotz> this is just a special case where ubuntu got hit
[13:58] <seb128> no it's not
[13:59] <seb128> if it's not us, it would be admin, users who write custom scripts, etc
[14:00] <ricotz> seb128, using scope=async in this case was wrong and actually changes the "virtual" api not matching the actual c-api
[14:01] <seb128> I didn't say the fix was not correct
[14:01] <seb128> but it doesn't make my point invalid
[14:01] <seb128> several libs live with wrong/suboptimal apis because "fixing" those would be an incompatible change and they avoid doing that because it has a cost
[14:02] <ricotz> (having this problem sit there without doing nothing is nothing better then "breaking" it again)
[14:02] <seb128> but I appreciate that g-i has no compatibility story whatsoever
[14:02] <seb128> it still doesn't make it right
[14:02] <ricotz> alright this is pretty valid, but yeah g-i is a bit special here
[14:03] <seb128> well, my suggestion by then was to rename the binary to have a proper transition
[14:03] <seb128> it's just that nobody picked that up to do it
[14:03] <ricotz> i see
[14:04] <ricotz> again which unity8 package is using this add_action part?
[14:04] <seb128> I don't know, they might not be using it anymore
[14:05] <seb128> tests/autopilot/unity8/shell/emulators/create_interactive_notification.py:        notification.add_action(
[14:05] <seb128> seems they still do
[14:05] <ricotz> as i said it cant be properly used since it crashes the second time you use the action
[14:06] <ricotz> ok, so "only" in the tests
[14:06] <seb128> yes
[15:40] <Ursinha> pitti: hey :) I have a question about autopkgtest, more specifically adt-run, that you might have the answer: when a package has no tests adt-run return code is 8, is that only to create a distinction between tests that actually ran and passed and no tests found? Or is there the intention to consider lack of tests a failure? (I'd assume no, but better ask :))
[15:43] <pitti> Ursinha: yes, we usually consider 8 a failure as way more often than not it's an unintended packaging bug
[15:45] <Ursinha> pitti: got it
[15:45] <Ursinha> pitti: thanks!
[15:46]  * pitti waves good night
[15:48] <seb128> night pitti
[16:23] <Sweetshark> dpkg versioning question: a version 1.2.3 is lower than a version <IP_ADDRESS>, right? This appears to be the case from reading the debian policy manual, but the footnote makes me nervous.
[16:27] <seb128> Sweetshark, yes, you can use dpkg --compare-versions 1.2.3 lt <IP_ADDRESS>; echo $?
[16:27] <lullis> Hey guys... So, I wrote a tiny python gtk application with an indicator that can interact with it. So far, so good. Now I am trying to figure out what is needed to do in order to have this indicator available on my login greeter (unity or lightdm-gtk should do).
[16:28] <lullis> I am guessing I need to write some kind of .desktop file, but that is just a guess.
[16:30] <Sweetshark> seb128: thx
[16:33] <seb128> Sweetshark, yw!
[17:13] <Laney> hey ;-)
[17:14] <larsu> hi Laney! What's going on?
[17:15] <Laney> currently meeting the tech-ctte
[17:15] <Laney> portland is quite pleasant
[17:15] <larsu> so I hear :)
[17:16] <Laney> how are you?
[17:17] <larsu> I have a cold
[17:17] <larsu> but am fine otherwise :)
[17:17]  * larsu just finished beating unitythemeiconprovider into shape
[17:53] <Laney> :( / :)
[17:54] <larsu> heh
[17:56] <seb128> hey laney, had a good trip? how is debconf?
[18:02] <Laney> hey seb128, trip was fine if a bit long
[18:02] <Laney> mostly over the jet lag now
[18:03] <seb128> Laney: no promotion this time?
[18:03] <Laney> no :(
[18:03] <Laney> debconf is good though, nice to meet people again
[18:03] <seb128> great!
[18:03] <seb128> weather is better than in the u.k as well I guess ;-)
[18:04] <Laney> http://www.bbc.com/weather/2641170 looks like it!
[18:05] <seb128> kenvandine, do we need those rtm merge requests to keep the rtm in sync with trunk?
[18:05] <Laney> you still in nl?
[18:05] <kenvandine> seb128, yes
[18:05] <seb128> Laney: guess? :p
[18:05] <Laney> I guess you have shipped your things already
[18:05] <seb128> kenvandine, that sucks, why do we need to branch if we don't add features to trunk/keep it for rtm only
[18:05] <seb128> Laney: lol
[18:06] <seb128> no
[18:06] <seb128> but still visiting people here yes ;-)
[18:06] <Laney> excellent
[18:06] <Laney> how was the poezenboot?
[18:06] <Laney> (trolling monday?)
[18:06] <kenvandine> seb128, i'm not the one to ask :)
[18:07] <seb128> Laney: didn't go there (yet)
[18:07] <kenvandine> we had to make rtm branches for everything
[18:07] <seb128> kenvandine, that's suboptimal
[18:09] <kenvandine> seb128, i think they are still working the kinks out
[18:19] <seb128> kenvandine, k
[18:20] <seb128> kenvandine, "working the kinks out" ... learnt a new expression today ;-)
[18:20] <kenvandine> ha, sorry :)
[18:20] <seb128> no worry, it's good to learn ;-)
[18:21] <seb128> is that commonly used one (the number of hints on google suggest maybe not)
[18:21] <seb128> is that like "working the details out"
[18:21] <seb128> or is there a nuance?
[18:22] <kenvandine> pretty common
[18:22] <kenvandine> more like working the bugs out
[18:22] <seb128> k
[18:22] <seb128> thanks ;-)
[22:53] <DalekSec> Hello.  So it seems you guys are the maintainers for xchat-indicator.  Hexchat seems to be "the new hip xchat", and has since had https://bugs.launchpad.net/ubuntu/+source/hexchat/+bug/1360785 reported.  Would you, since you maintain xchat-indicator, perhaps maintain hexchat-indicator?  https://code.launchpad.net/~unit193/hexchat-indicator/packaging may be a starting point...
[22:53] <ubot2> Ubuntu bug 1360785 in hexchat "HexChat does not integrate with the Ubuntu me-menu" [Undecided,New]


[00:32] <dyson_vacuum_exp> good evening!!!!
[00:37] <amundsen> hi
[00:37] <amundsen> i'm trying to install NitruxOS icon theme in Kubuntu
[00:38] <amundsen> i've followed the instructions
[00:38] <amundsen> try to find some help in Google
[00:38] <amundsen> but no success yet ...
[00:38] <amundsen> anybody got it ?
[00:55] <guest__> ls
[00:55] <guest__> nick #olll
[00:55] <guest__> l
[00:55] <olll> ls
[01:06] <firenetcorp> hola
[01:06] <firenetcorp> buenas tardes
[01:06] <firenetcorp> alguien me puede ayudar por favor
[01:13] <firenetcorp> me pueden ayudar con mi ubuntu 13.04
[01:13] <SonikkuAmerica> firenetcorp: Sí ... pero no puedo aquí, ve a #ubuntu-es
[01:21] <firenetcorp> y como accedo
[02:54] <mr44> hi! Is it normal when the apps like Firefox, dolphin, some wine stuff have several processes of the same names running even if i close the apps?
[04:24] <littlegirl> Hey there, I'm having a brain bubble. Can I do sudo apt-get purge pkg1 pkg2 pkg3 all on one line?
[04:25] <littlegirl> I'm finding all sorts of examples of apt-get purge with one package, but none with multiple. (:
[04:25] <Unit193> Yes.
[04:25] <littlegirl> Thanks!
[04:25]  * littlegirl hugs Unit193
[04:25] <Unit193> Sure.
[04:39] <ProjektGopher> do backwards smileys bother anyone else, or is it just me?
[08:28] <zipper> ..
[08:38] <geomyidae> hi, if I build kde-workspace, how can i install or run it's bits without installing it over my existing bits?
[08:43] <PsyKoTic> Hey guys, anyone willing to help me with a GRUB2 problem I'm having?
[09:01] <PsyKoTic> Why?
[09:01] <PsyKoTic> That's for Grub not Grub2, right?
[09:17] <Beetoo> having network problems with kubuntu
[09:18] <macwolf74> liiikkeee
[09:19] <Beetoo> i installed kubuntu 12.04.2 but after reboot, the network is not working
[09:19] <Beetoo> i can  configure network and all the devices are available in "lspci", but ping is not working for any server
[09:21] <macwolf74> hm
[10:18] <chiefw0tj> I'm having an issue with green screens on Dragon Player and Kamoso...has anyone else seen this? My system is a System76 Gazelle Pro, pure Intel
[10:37] <BluesKaj> HI all
[12:07] <papret>  in calc, how to count nonempty cells? how to count cells with a particular color background? or how to count noncolored cells?
[12:09] <SonikkuAmerica> papret: Head for #libreoffice with that question.
[12:12] <papret> SonikkuAmerica: yes i know.... but for some reason i always get lucky in the kubuntu channel so i gave it a shot.... :)
[12:12] <SonikkuAmerica> XD
[12:13] <SonikkuAmerica> papret: I would've thought, however, it was the =COUNT function, but I don't use spreadsheets.
[12:14] <papret> SonikkuAmerica: yes but dont understand how to do it with the colors....
[12:15] <SonikkuAmerica> papret: Now that one's out of my reach.
[12:17] <papret> i dont use kde... in fact i am a big fan of lxde.... but i always get the feeling kde people are nice.... :)
[12:18] <SonikkuAmerica> papret: Have you tried Lubuntu?
[12:19] <papret> yes that's what i have here....
[12:25] <papret> bye :)
[13:10] <vladino> hi which bittorrent client is best under KDE?
[13:10] <BluesKaj> there is no best , ktorrent is the default I think
[13:11] <vladino> thanks
[14:25] <lordievader> Good afternoon.
[14:32] <SonikkuAmerica> Good morning from America lordievader
[14:46] <lordievader> Hey SonikkuAmerica, how are you?
[14:47] <SonikkuAmerica> Fine
[14:47] <SonikkuAmerica> I *am* in -offtopic you know :)
[14:48] <lordievader> SonikkuAmerica: But you replied here ;)
[14:48] <SonikkuAmerica> :P
[15:09] <gianni__> ciao
[15:09] <gianni__> list
[15:30] <Daskreech> !best
[16:19] <ss_haze> hello kde
[16:20] <chachan> bye unity
[16:24] <ss_haze> I use both, periodicly
[16:24] <ss_haze> sometimes even openbox is fun
[16:25] <ss_haze> but it's no holly war right :)
[16:26] <ss_haze> I tried windows 8 start screen, and screen is so boring, I even missed what they implemented
[16:26] <BluesKaj> I tried unity and even gave it a fighting chance , but after a few weeks I'd had enough and dumped it
[16:28] <BluesKaj> some ppl love it ...to each his own. Being an old windows guy , kde is more familiar and makes more sense to me .
[16:29] <BluesKaj> sidebar panels never appealed to me
[16:42] <ss_haze> thats the problem with people who don't evolve, even if it is all a cycle somehow..
[16:43] <ss_haze> but I really like kde panel
[16:43] <ss_haze> it is really beuty, if you don't like to mess configuring it
[16:44] <ss_haze> or you DO want to do it
[16:44] <BlaXpirit> i'm doing experiments with my panels
[16:44] <BlaXpirit> I think they recently added a new task manager
[16:44] <BlaXpirit> that kinda mimicks Unity's panel
[16:45] <BlaXpirit> i moved the panel to the left side of the screen
[16:45] <BlaXpirit> vertical space is much more precious with those crazy widescreen monitors
[16:46] <ss_haze> every user bow down to LCD, LED industry
[16:46] <BlaXpirit> and then the idea stuck in my head
[16:47] <BlaXpirit> so i even moved the tab bar to the side in my webbrowser
[16:47] <ss_haze> buying stocks of LED industry?
[16:47] <BlaXpirit> huh
[16:47] <ss_haze> no
[16:49] <ss_haze> next semester in "computer sciences" or some IT will be great, if I will get in university, which I think I can do
[16:49] <ss_haze> last year electronics course made me think of physics, random shit how it's all one big bubble
[16:52] <ikonia> ss_haze: that language is uncalled for an uncacceptable
[17:15] <Daskreech> BlaXpirit: I just browse in full screen mode :)
[17:17] <victor__> quiet room :)
[17:25] <Daskreech> Well it's a support room so that's good I guess?
[18:42] <jjeronimo> hi kubuntu fans
[18:43] <jjeronimo> I recently enabled the desktop widget "Remember the milk", now my plasma desktop process freezes on startup
[18:43] <jjeronimo> any idea how to disable the widget?
[19:40] <jjeronimo> fixed it
[22:28] <daniel29> hi
[22:28] <daniel29> how do i report a bug in the mouse driver?
[22:29] <daniel29> at least the mouse driver for my machine
[22:30] <daniel29> anyone?
[22:30] <daniel29> bueller?
[22:31] <SonikkuAmerica> daniel29: You'll file it against the X server.
[22:33] <daniel29> DUH!!
[22:33] <daniel29> lol
[22:51] <jpontes> #portugal
[22:54] <OerHeks> !pt
[23:38] <doctorpepper> hi guys !!


[05:04] <slangasek> pitti: morning! looks like autopkgtest runners are stalled on amd64,i386,ppc64el; the juju node seems to show some sort of image mastering job running for the past couple of hours; is this expected maintenance?
[05:30] <cpaelzer> good morning
[06:02]  * Son_Goku sighs
[06:02] <Son_Goku> I was really hoping that my patches to ondrej for php7.0 would have been merged in by now
[07:10] <Mirv> @pilot in
[07:32] <pitti> Good morning
[07:34] <pitti> slangasek: php-* migrated, so I suppose this got sorted out with my infra cleanups yesterday evening
[07:34] <pitti> slangasek: runners stalled> yeah, I got tons of worker failures over the weekend, apparently some neworking cloud trouble again
[07:34] <pitti> slangasek: but all good now
[08:03] <cpaelzer> pitti: I didn't realise that was the difference between autopkgtest and auto-package-testing - thanks for fixing the tagging in the bug
[08:04] <pitti> cpaelzer: no worries, that's a bit subtle indeed :)
[08:19] <dholbach> good morning
[08:36] <slangasek> pitti: right, lots of things being rebooted for the security update, wonder if these systems should recover more automatically
[08:36] <pitti> slangasek: well, apparently they did
[08:36] <slangasek> ah, ok
[08:36] <pitti> slangasek: I didn't do anything this morning
[08:36] <slangasek> :)
[08:37] <pitti> well, I'm reviewing failures on excuses.html, but no manual infra work
[08:37] <pitti> slangasek: every six hours there is a cronjob which deletes orphaned instances and restarts all workers
[08:38] <pitti> slangasek: that usually cleans up after networking or other scalingstack issues which happen and get fixed within a few hours
[08:40] <slangasek> pitti: as far as php-* migrating, it still looks buggy to me that britney triggered tests against the -proposed version and then this didn't get dispatched... I think I wound up manually retriggering those tests I mentioned
[08:40] <pitti> slangasek: ah, that's only a display bug -- britney does not trigger a particular version of a test
[08:40] <slangasek> hmm, ok
[08:40] <pitti> slangasek: it just says "run tests for package foo against the proposed version of bar"
[08:41] <pitti> i. e. the trigger is versioned, but not the test
[08:41] <pitti> and once the test actually ran, britney shows the "real" version
[08:41] <pitti> but for the "in progress" it apparently currently shows the -proposed version, which is wrong more often than not
[08:41] <pitti> I guess I should just not show it at all
[08:41]  * pitti adds a WI
[08:42] <pitti> ah well, that's not actually that easy UI wise, as all arches are grouped on one line as long as the version matches
[08:42] <pitti> so maybe -- if there is a line with *only* "in progress", don't show a version
[08:55] <doko> pitti, slangasek: dns problems on Sunday
[09:36] <Mirv> @pilot out
[09:36]  * dholbach hugs Mirv
[09:36] <Mirv> pitti: hmm I guess you're not pilotting anymore since you did on Friday?
[09:36] <pitti> @pilot out
[09:37]  * Mirv hugs dholbach
[09:37] <pitti> Mirv: indeed, thanks
[09:50] <doko> LocutusOfBorg, is the powerpc ftbfs in insighttoolkit4 fixed in your last upload?
[09:52] <LocutusOfBorg> doko, I don't think so
[09:52] <LocutusOfBorg> specially because seems more a compiler ICE
[09:52] <doko> and the i386 test failures?
[09:53] <LocutusOfBorg> should be
[09:56] <infinity> That's not an ICE.
[09:57] <infinity> But it probably means some large function needs splitting.
[09:58] <LocutusOfBorg> I don't remember the reason, I'm trying to get the package migrate, and i386 is the blocker AFAICS
[09:58] <doko> LocutusOfBorg, any reason why you build with 8 cpu's in parallel on amd64?
[09:59] <LocutusOfBorg> you disabled the parallel build on amd64, and the build was taking something like a week. I did a parallel=2 and it worked, I did a parallel=4 and it worked, today I did a parallel=8. I'm not sure why you disabled it
[10:00] <infinity> LocutusOfBorg: Don't set an explicit parallel= unless you're trying to set it *lower* than the buildds do.
[10:00] <LocutusOfBorg> infinity, do the amd64 builds defaults to 8?
[10:00] <infinity> (pretty please)
[10:00] <doko> the build now takes 16h, the machine swapping ...
[10:00] <infinity> LocutusOfBorg: They default to 4 these days, probably.
[10:00] <LocutusOfBorg> ough, sorry, I thought it was 16
[10:00] <infinity> LocutusOfBorg: (They default to $(nproc))
[10:01] <LocutusOfBorg> for some reasons I had 16 in my mind, probably because DebOMatic is defaulting to that
[10:01] <infinity> "Initiating build PACKAGEBUILD-9048365 with 4 jobs across 4 processor cores."
[10:01] <LocutusOfBorg> bad monday
[10:01] <LocutusOfBorg> I can cancel it if needed and reupload
[10:03] <infinity> +  * Drop intrinsics patch: upstream.
[10:03] <infinity> LocutusOfBorg: You also don't need to mention that in every upload. ;)
[10:05] <LocutusOfBorg> that was a copy-paste error, I thought about removing, but probably forgot that :)
[10:13] <pitti> cjwatson, infinity: did we disable autosyncs? (we should as we are in FF, but last Friday during my sponsoring shift it appeared as if they were still on)
[10:15] <pitti> cyphermox: can you please have a look at bug 1548252? I'm fairly sure that this used to work at some point, as I often do that to investigate handling of cryptsetup devices during boot
[10:16] <doko> pitti, they are disabled
[10:16] <pitti> doko: thanks
[10:20] <doko> The following packages have unmet dependencies:
[10:20] <doko>  php-symfony-proxy-manager-bridge : Depends: php-proxy-manager (< 2~~) but 2.0.0-1ubuntu1 is to be installed
[10:21] <doko> slangasek: according to the changelog you fixed the tests to work with php-proxy-manager 2
[10:38] <cjwatson> pitti: I disabled them last thing Thu / early Fri morning, so it would've depended on your criteria :-)
[10:39] <pitti> cjwatson: ack, thanks for confirming
[11:08] <Kryczek> Hi! I do not know much about the Ubuntu project apart from being a very happy user of it since 5.04, and I apologize if this has been mentioned to you already several times, but as far as I understand the Ubuntu live media are made using live-build which is now sadly orphaned: https://packages.qa.debian.org/l/live-build.html . I offered my help of course but I have neither the knowledge nor the time
[11:08] <Kryczek> to contribute much so I am wondering if by any chance the Ubuntu community with all its might could perhaps save this crucial software?
[11:17] <LocutusOfBorg> fixed and reuploaded itk4
[11:21] <doko> cjwatson, https://launchpadlibrarian.net/241356698/buildlog_ubuntu-xenial-amd64.haskell-bindings-sane_0.0.1-7build1_BUILDING.txt.gz (showed up in the ghc transition tracker). any idea about the ftbfs?
[11:57] <doko> apw, any idea when the linux block-proposed issue gets removed?
[11:59] <cjwatson> doko: yes, I know about that, it's because of IIRC libsane's pkg-config version having a ~ in it or some such, need to figure out how to work around that in cabal
[12:35] <doko> LocutusOfBorg, please could you use the -v<last ubuntu version> option when merging packages?
[12:41] <LocutusOfBorg> ok, I wasn't aware of this
[12:41] <LocutusOfBorg> ok
[12:59] <xnox> bdmurray, could you please subscribe foundations bugs to libica package for the MIR 1546987 ? it's an s390x specific thing.
[13:08] <rbasak> doko: btw, I don't think we have any process of telling new uploaders how to do such things. People get upload rights but no instructions on dput, etc, and of course before direct uploading, sponsorees don't need to know.
[13:08]  * rbasak bets that caribou doesn't know either
[13:09] <rbasak> The wiki could do with a "Congratulations, so you're a new uploader!" page with instructions on dput, -v<last ubuntu version> for merges, etc, and get the DMB to point to that.
[13:11] <Laney> Like https://wiki.ubuntu.com/MOTU/New ?
[13:11] <ginggs> it is mentioned here: https://wiki.ubuntu.com/UbuntuDevelopment/Merging#Get_your_work_uploaded
[13:12] <doko> xnox, bdmurray: done
[13:12] <doko> rbasak, like Laney said
[13:13] <rbasak> Ah, great!
[13:13] <rbasak> Nobody pointed me to that page when I became an uploader/MOTU though. Maybe that's the only missing link then.
[13:13] <xnox> doko, thanks.
[13:13] <doko> rbasak, please could you address https://launchpad.net/bugs/1546957 ? now blocking another transition (or you might want to fight with Laney about the bug subscription ;)
[13:13] <caribou> rbasak: doko: I found out by reading your merge doc; I used it for clamav
[13:14] <Laney> boring troll
[13:14] <caribou> rbasak: oh, I didn't know about dput, I thought you meant dpkg-buildpackage
[13:18] <rbasak> doko: tons of !server stuff depends on lua. So why should this be a server bug subscription? I accept the nmap rdep, but this seems pretty generic. I'll defer to jgrimm I think.
[13:18] <rbasak> (why uses nmap with lua anyway?)
[13:18] <rbasak> who
[13:18] <doko> rbasak, fix it to rmove the dependency
[13:22] <rbasak> doko: I'll add it to our queue to look at.
[13:46] <flexiondotorg_> I have a package update I'd like beg gets sponsored.
[13:46] <flexiondotorg_> Anyone able to help? - https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-welcome/+bug/1548133
[13:50] <pitti> doko: I'm looking at the tomcat7 → tomcat8 change on component-mismatches, unless you already did
[13:51] <pitti> it seems some packages need to be updated for libservlet3.0-java → libservlet3.1-java
[13:51] <doko> pitti, sure, please make sure to revert seb128's change for hsqld1.8
[13:51] <pitti> doko: right, that's another step
[13:52] <seb128> it's not "my changes", I only merged that package because nobody else was doing it
[13:52] <pitti> seb128: yeah, it was entirely right at the time, that wasn't a blame
[13:52] <seb128> good :-)
[13:53]  * doko never blames
[13:54] <pitti> Debian's dependency is also wrong
[13:54] <pitti> Depends: libservlet2.5-java, ${misc:Depends}
[13:54] <pitti> <pathelement location="/usr/share/java/servlet-api-3.1.jar"/>
[13:54]  * pitti will file a b gu
[13:54] <pitti> bug too
[13:54] <pitti> l
[14:03] <jamespage> please could an archive admin promote python-openvswitch to main; its source is already in main and its needed for neutron
[14:04] <jamespage> looks like it popped into main for a bit and then when back to universe?
[14:06] <pitti> jamespage: done
[14:07] <jamespage> pitti, ta
[14:20] <pitti> jamespage: just FYI, I'm tracking the tomcat7 → 8 changes on bug 1539903
[14:21] <pitti> there might be some temporary hiccups, but I'm tracking component-mismatches etc.
[14:23] <abeato_> pitti, hi, I have a patch for ntp (bug #1526264), who should be best to take a look?
[14:23] <pitti> abeato_: please subscribe ubuntu-sponsors
[14:24] <abeato_> pitti, ok, and then should I send an e-mail to the list?
[14:26] <doko> I'm planning to start an archive test-rebuild this week, maybe tomorrow, once the current linux/bind9/gcc-5 migrate. Is there anything which should be included? If yes, what?
[14:27] <doko> pitti, jamespage, rbasak, Laney, seb128, smoser, apw: ^^^
[14:27] <xnox> infinity, glibc 2.23? ^
[14:27] <seb128> doko, nothing special on the desktop side
[14:28] <Md> I am testing the 16.04 installer, but I have noticed that my custom partman recipe now creates an extended partition instead of a primary one. has something changed?
[14:29] <xnox> Md, better ask on #ubuntu-installer. and/or highlight cyphermox. Loads of things have changed in 16.04 installer, as a lot of d-i components got upgraded.
[14:30] <Md> I have not tested debian/unstable, but the same recipe works as expected with the debian/stable installer
[14:32] <ben__> hi, could someone from the archive team please have a look at the binary removal request (bug #1542398)? the old armhf binary is blocking the new version from migrating to release for two weeks now
[15:03] <doko> rbasak, please subscribe to tomcat8 bug reports (like for tomcat7), so that pitti's uploads can build
[15:06] <pitti> doko: nothing that needs squeezing in from my side
[15:08] <seb128> doko, we might have a poppler soname change, better before or after?
[15:09] <doko> seb128, well, upload today and start the transition today
[15:09] <rbasak> doko: tomcat8> done. I'm not sure I understand why it would be a problem for pitti, but it needs doing anyway.
[15:09] <seb128> doko, ok
[15:09] <pitti> rbasak: it's just for completing the demotion of tomcat7 and promotion of tomcat8
[15:09] <doko> rbasak, he already promoted; or else he would only see dep-waits
[15:10] <pitti> stuff is building now
[15:25] <rharper> I've a bug that's now fixed in xenial, but not fixed in trusty;  how do I add task entry for say Trusty ?  I see the Also affects project, distro/package and nominate; not sure which one of those (or something else) I'd use to indicate it's also broken in trusty (so I can propose an SRU)
[15:29] <rbasak> rharper: nominate Trusty
[15:35] <rharper> rbasak: thanks!
[16:01] <doko> rbasak, fyi, https://launchpad.net/ubuntu/+source/nmap/7.01-2ubuntu1  but some features are disabled
[16:04] <doko> pitti, does virtualbox need testing against proposed (kernel)?
[16:10] <pitti> doko: you mean -7 regresses virtualbox and that holds back the proposed virtualbox?
[16:11] <pitti> doko: that's a special case for the kernel team indeed, they want to test DKMS stuff against the proposed kernel always
[16:11] <pitti> so we don't do apt pinning for the kernel
[16:12] <pitti> doko: but it's clearly not a regression of that rebuild itself, so I'm fine with allowing that rebuild to unblock the transition
[16:13] <pitti> it's a glaring red regression on http://people.canonical.com/~kernel/status/adt-matrix/xenial-linux-meta.html, so it should be on apw's radar
[16:14] <apw> pitti, regressions on virtualbox and spl-linux are almost always not regressions, as we have the same version in the kernel and that errors, but i hint them on manual review
[16:42] <marlinc> cking, you around?
[16:43] <marlinc> Anyway, the default ZFS compression algorithm is lz4 not gzip-6
[16:47] <cking> marlinc, ok, i'll correct that in the wiki
[16:47] <sarnold> I thought the default was lzjb? and that folks -should- change it to lz4?
[16:51] <cking> bah, I can't recall now, I need to double check that
[16:55] <Son_Goku> wasn’t it lzo for speed?
[17:01] <pepee> sarnold, did I talk with you about this bug a few days ago?  https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1545401
[17:03] <sarnold> pepee: I think before you filed it, yes; I hadn't seen the report thuogh. nice.
[17:05] <sarnold> pepee: jeeze, good thing your reproducer is a thuosand times easier than "just install mosix and migrate a process". sheesh.
[17:07] <sarnold> pepee: interesting, looks like the rhat bug was filed via a vmware guest.. yours has vbox modules linked in; can you reproduce it with a kernel that doesn't have vbox loaded? (best if it -never- had vbox modules loaded..)
[17:07] <marlinc> sarnold, The  current default compression algorthm is either lzjb or, if the lz4_compress feature is enabled, lz4.
[17:07] <marlinc> lz4_compress is enabled by default :)
[17:07] <marlinc> Thanks cking!
[17:08] <cking> lz4 is by default, had to check that for sure
[17:08] <marlinc> cking, is it possible for others to work on that document?
[17:08] <pepee> sarnold, mine isn't a VM, though
[17:08] <marlinc> sudo zpool create example raidz /dev/sdb /dev/sdc /dev/sdd /dev/sde /dev/sdf /dev/sdg
[17:08] <cking> marlinc, it should be editable by anyone with wiki acess
[17:08] <marlinc> That should be raidz3 :)
[17:08] <sarnold> pepee: yeah; still, those modules are .. iffy.
[17:09] <marlinc> '3 parity bits, allowing for 3 disk failures before losing data with performance like RAIDZ2 and RAIDZ. Example, create a 3 parity 6 VDEV pool:'
[17:09] <doko> barry, did you omit the python-pip merge by intent?
[17:09] <pepee> sarnold, I linked to the sources, I guess (wild guess...) that there is a problem with some API
[17:09]  * cking fixes that too, thanks for spotting that marlinc
[17:09] <sarnold> marlinc: ah! good. lz4 is a much better default. is that something speicific to zfsonlinux implementatio or is that common to all openzfs now?
[17:09] <marlinc> I don't think I have that cking
[17:09] <pepee> sarnold, true... I'd have to test later, I'm not using 4.2 anymore, too risky :(
[17:09] <sarnold> pepee: heh, the source is what made me wonder -- why was your memory allocation going through a numa-aware code-path. seemed funny on a laptop. ;)
[17:10] <marlinc> Not sure sarnold, I looked it up in the ZFS man pages on my Ubuntu install
[17:10] <sarnold> marlinc: woo :)
[17:10] <cking> bah, wiki timeouts
[17:10] <pepee> sarnold, my laptop is loading numa stuff, not sure why... I think I installed some packages and that came as dependency
[17:11] <marlinc> :)
[17:11] <pepee> in fact, my laptop doesn't even support iommu and other things being loaded, heh
[17:12] <barry> doko: yes, i think we can drop the ubuntu deltas.  i merged --user by default to the debian version and i believe the shebang should be correct now too.  i'll double check the proposed version and look at excuses
[17:12] <marlinc> What should I do if I find something else cking?
[17:12] <pepee> anyway, thanks sarnold, I'll do some testing later
[17:12] <cking> marlinc, if you can't edit it, ping me, or email me<EMAIL_ADDRESS>[17:13] <sarnold> pepee: ha! click around on that a bit -- the _one_ caller checks to _ensure_ that the page is PROT_NONE before calling do_numa_page
[17:13] <sarnold> pepee: .. but do_numa_page BUGs on that specific condition
[17:16] <marlinc> Okay cking :p
[17:19] <pepee> sarnold, the caller is follow_page_pte()?
[17:20] <sarnold> pepee: handle_pte_fault()
[17:21] <sarnold> apw: the kernel team's demotativation bug bot hasn't commented on 1545401 yet -- is it hooked up to look for bugs in the linux-lts-* packages too?
[17:25] <pepee> sarnold, oh, I see... I think, you mean   3265  if (pte_protnone(entry))      3266  return do_numa_page(mm, vma, address, entry, pte, pmd);  ?
[17:26] <pepee> shouldn't the dev that made the patch have also change the other functions/files?
[17:26] <apw> sarnold, quite possibly not ... bjf ^
[17:27] <apw> sarnold, i would hope they would get retargeted to linux as things need to be fixed in the primaries first in the main
[17:28] <sarnold> apw: yeah, that'd make sense, but e.g. linux-lts-utopic is a bit strange, as linux in utopic is eol ..
[17:29] <bjf> sarnold, apw, i haven't looked but no the bot most likely isn't looking at those
[17:29] <sarnold> pepee: yeah, some time with git blame to figure out what happened to the code might help figure out if that's just missing a ! before the call or if this is going to be a huge change..
[17:30] <pepee> sarnold, https://lists.ozlabs.org/pipermail/linuxppc-dev/2014-December/123285.html
[17:30] <apw> sarnold, yep, that one is a strange one for sure, and that one filing direct does make sense, so that isn't confusing at all
[17:32] <sarnold> pepee: heh, he's one of the few who I might have expected to understand this code :) haha
[17:34] <pepee> sarnold, the earliest one I could find:  http://lkml.iu.edu/hypermail/linux/kernel/1411.1/05082.html   ,  patchset is  http://lkml.iu.edu/hypermail/linux/kernel/1411.1/05086.html
[18:00] <pepee> sarnold, apw: what does invalid means?
[18:01] <apw> pepee, invalid where?  in a bug it normally means that the bug is not applicable to a specific task (series/package combination)
[18:02] <pepee> apw, ah, ok. I submitted bug # 1545401
[18:03] <apw> bug: #154401
[18:04] <apw> bug: #1545401
[18:04] <apw> pepee, right in that one the bug is reported against linux-lts-wily in xenial, which makes no sense
[18:04] <apw> pepee, so you are seeing me targetting it to trusty where that kernel exists and adding linux tasks as we
[18:05] <pepee> ah, heh
[18:05] <apw> pepee, have to fix it there first, the invalid ones are mostly non-existant combinations
[18:05] <pepee> I hadn't noticed, sorry
[18:07] <pepee> I had no idea this was a security bug
[18:14] <ginggs> doko: dpkg: error processing archive /var/cache/apt/archives/libtesseract4_3.04.01-2_amd64.deb (--unpack):
[18:14] <ginggs>  trying to overwrite '/usr/lib/libtesseract.so.3.0.4', which is also in package libtesseract3v5 3.04.00-5ubuntu1
[18:16] <doko> Laney, ^^^
[18:16] <Laney> Someone synced it
[18:17] <Laney> and that person was doko
[18:17] <doko> ahh, crap, we need the Breaks/Replaces ... will fix
[18:20] <doko> ginggs, hmm, can you file a Debian issue? that should show up for unstable as well, it has the conflict, but misses the replaces?
[18:21] <ginggs> doko: ok
[18:24] <doko> and the somebody not merging was Laney
[18:25] <ginggs> doko: looks like it is already filed, debian #815056
[18:26] <doko> argh
[18:27] <infinity> Uhh, why does a package named libtesseract4 contain libtesseract.so.3?
[18:28] <infinity> Someone doesn't know how SONAMEs work.
[18:29] <sarnold> pepee: I hit the 'security' flag because a series of user-space operations appeared to put the kernel in a state that it certainly didn't expect
[18:30] <pepee> sarnold, ah
[18:30] <pepee> you are right... I'm a bit slow
[18:32] <pepee> sarnold, wondering if it's exploitable :P
[18:34] <sarnold> pepee: my first guess is that it's not exploitable for privilege escalation but it may have other surprising effects
[18:38] <pepee> I just noticed, http://lxr.free-electrons.com/ident?v=4.2;i=do_numa_page says do_numa_page() is referenced in its own definition and in the bugged line... what's the point of that function, then?
[18:39] <pepee> bah, I wish I knew more about kernel dev'ing
[18:42] <sarnold> the function is defined on the first (3133) and called on the second (3266)
[18:43] <sarnold> because it's only called from one place it -could- have been written inline in the handle_pte_fault() function and avoid the function call, but that kind of programming leads to thousand-line functions that are impossible to think about :)
[18:49] <pepee> ah, ok
[20:07] <doko> barry, did you omit the python-pip merge by intent?
[20:07] <barry> doko: did you see my previous response?
 doko: yes, i think we can drop the ubuntu deltas.  i merged --user by
[20:07] <barry>         default to the debian version and i believe the shebang should be
[20:07] <barry>         correct now too.  i'll double check the proposed version and look at
[20:07] <barry>         excuses  [12:12]
[20:07] <barry>
[20:08] <barry> doko: the pkg looks good.  i don't know why python-virtualenv is holding it back.  a local adt-run passes and the a.u.c artifact is mysterious
[20:09] <doko> hmm, didn't see the reply.
[20:09] <barry> doko: anyway ^^
[20:09] <doko> barry, it's because python-pip-whl is not installable
[20:10] <barry> doko: seems to be here<EMAIL_ADDRESS>[20:13] <doko> barry, python-virtualenv is not considered for migration, because the tox autopkg tests fail
[20:14] <barry> doko: right, but i cannot reproduce that locally in adt-run with -proposed enabled
[20:15] <doko> barry, well, ask pitti to hint it
[20:15] <barry> pitti: ^^ any thoughts?
[20:16] <doko> python-setuptools shows some regressions too, and afail python-pip has a breaks to the version in the release pocket
[20:16] <pitti> barry: local adt-run> did you enable -proposed?
[20:16] <pitti> ah, you did
[20:16] <barry> pitti: i used a xenial-amd64 chroot w/-proposed enabled and verified the python-virtualenv and python-tox versions that got installed there.  passes beautifully for me
[20:17] <pitti> barry: let me first re-run the test against all of -proposed, maybe there's some hidden dependencies there
[20:17] <doko> barry, and setuptools triggers virtualenv failures
[20:17] <barry> pitti: thanks
[20:18] <mdeslaur> cyphermox: any plans on merging sudo?
[20:18] <barry> doko: that looks like it's using the old virtualenv pkg, but that has no tests
[20:18] <doko> plus pbgenomicconsensus and python-pex
[20:19] <doko> barry, pitti: can you retry with -proposed enabled?
[20:19] <pitti> doko: just did
[20:19] <barry> as did i
[20:19] <Noskcaj> Could someone please upload the newest youtube-dl to xenial? I've test built it, but this package needs to be treated almost like a rolling release for it to function properly (A number of it's releases are compatibility fixes)
[20:19] <pitti> retry-autopkgtest-regressions | sed 's/run-autopkgtest/& --all-proposed/' | sh
[20:19] <pitti> err, and a | grep python
[20:19] <barry> pex may be intermittent.  /me retries
[20:20] <pitti> doko, cjwatson, infinity, slangasek: FYI: I added a --all-proposed option to run-autopkgtest the other day that disables apt pinning
[20:20] <cyphermox> mdeslaur: if it's rush, feel free to do it.
[20:20] <cyphermox> I'm assuming you ask because of sudoedit?
[20:20] <doko> pitti, am I allowed to use this as well?
[20:20] <pitti> doko, cjwatson, infinity, slangasek: FYI: easier than cobbling together tons of --trigger options
[20:20] <mdeslaur> cyphermox: yeah, and I'd like to backport the version we're going to ship in xenial into the stable releases after
[20:20] <pitti> doko: sure; I thought you used run-autopkgtest/retry-autopkgtest-regressions yourself before we had the web-clicky stuff?
[20:21] <mdeslaur> cyphermox: and I'd rather do it with 1.8.15
[20:21] <cyphermox> mdeslaur: yeah, I understand
[20:21] <barry> pitti, doko pex failures are reproducible locally
[20:22] <doko> probably a missing build/test dependency,
[20:22] <doko> pitti, is there consensus to ignore pbgenomicconsensus? ;)
[20:22] <pitti> but it has *such* a funny package name!
[20:22] <barry> doko: that's probable, since it shuts off pypi and it's a connection refused.  i need to update pex anyway
[20:23] <pitti> doko: yep, the history is fairly red-heavy, I'll hint it
[20:23] <cyphermox> pitti: up in the top 10 with datefudge and all.
[20:23] <doko> barry, it would be nice to modify pip to print out what it wants to fetch for such cases ...
[20:23] <barry> doko: at least desktop is down to just samba keeping py27
[20:24] <barry> doko: indeed, i've wanted that for a long time.  next time it bugs me too much i'll give it a look
[20:24] <pitti> cyphermox: libcatalyst-authentication-credential-authen-simple-perl absolutely belongs in that list too
[20:25] <pitti> Package: how-to-trigger-buffer-overflows-in-dpkg-parser-codes
[20:25] <pitti> doko: ah, it already has a hint, just needs a version bump
[20:26] <barry> doko: server has nothing keeping python python2.7 on it so i guess it just needs to be deseeded
[20:27] <barry> and i think smoser has a todo for that
[20:27] <smoser> i'm open to someone else doing that.  i dont think it is seeded anywhere is it
[20:28] <smoser> i have a TODO to blacklist it from the images
[20:28] <smoser> https://blueprints.launchpad.net/ubuntu/+spec/foundations-x-python3-only
[20:28] <pitti> doko: hinted aplpy/s390x too while I'm at it
[20:28] <barry> smoser: i grabbed today's daily and `apt-get purge python2.7 libpython2.7`.  it only purges those, nothing else
[20:29] <barry> smoser: yes.  time to add that blacklist?
[20:29] <pitti> barry: http://autopkgtest.ubuntu.com/running.shtml#pkg-tox doesn't look good, several Fs
[20:29] <infinity> It shouldn't need blacklisting.
[20:29] <smoser> so how'd they get there?
[20:29] <smoser> we wanted blacklist to fail build
[20:29] <infinity> If it's ending up on the images, we should figure out why, not hack around it.
[20:29] <smoser> i agree with infinity, but i thought the intent was to make things fail
[20:30] <barry> pitti: huh.
[20:30] <barry> smoser, infinity that's what i thought too
[20:30] <doko> barry, ahh, should be @builddeps@, not @
[20:30] <infinity> smoser: There are lots of packages we don't want on images, we shouldn't force a failure every time one pops up.  python's not really special here. :P
[20:31] <infinity> But definitely, if there's no clear reason it's showing up in all those tasks still, we might want to investigate.
[20:31] <barry> doko: hmm, maybe so since it's running its own self tests
[20:32] <doko> barry, fixing this, while you prepare a new upstream
[20:32] <barry> doko: in tox, right?
[20:32] <barry> not pex
[20:32] <barry> or did you mean pex?
[20:32] <doko> I thought pex
[20:32] <barry> doko: oh, i was looking in the wrong place, just a sec
[20:33] <barry> doko: hmm, i don't think pex should use builddeps
[20:33] <barry> doko: textwrap comes from stdlib
[20:33] <doko> barry, not even the execute.sh test?
[20:34] <barry> doko: right, not even that.  it's entirely possible something's changed tho
[20:34] <barry> doko: but i'll verify as i prep the new version
[20:34] <infinity> smoser: FWIW, python2.7 isn't in the server livefs manifest anymore.
[20:34] <infinity> barry: How did you install server?
[20:35] <barry> infinity: grabbed xenial-server-amd64.iso from here: http://cdimage.ubuntu.com/ubuntu-server/daily/current/
[20:35] <smoser> that is old.
[20:35] <smoser> due to some failing tests.
[20:35] <barry> infinity: installed in fresh vm, no downloads during install
[20:35] <smoser> :-(
[20:35] <smoser> fudge.
[20:35] <smoser> the change that would have released it went into postfix today
[20:36] <smoser>  https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1538198
[20:36] <doko> smoser, why not installing an image, then trying to remove python2.7-minimal and libpython2.7-minimal?
[20:36] <barry> smoser: ah, okay!  so maybe it'll be gone in the next successful image
[20:36] <smoser> er... it says 20th, but lamont made it sound like today i thought.
[20:36] <smoser> doko, ? i didnt come up with the idea to blacklist.
[20:37] <smoser> i think it is fine to test other ways for sure.
[20:37] <barry> smoser: it came up in the last uos session, but i don't remember who suggested it
[20:37] <barry> smoser: just that you didn't have your finger on your nose :)
[20:37] <infinity> smoser: Anyhow, please don't blacklist.  I'm on VAC today (see how well I'm doing), but if a plain install still pulls in python2, let's fix it tomorrow.
[20:37] <smoser> deal
[20:37] <barry> wfm
[20:37] <infinity> python2.7 is still in the "server" task, so something likely needs a nudge, but let's do it rightish.
[20:38]  * infinity goes back to ignoring IRC for a bit.
[20:41] <doko> coreycb, python-ironicclient wants some MIRs
[20:41] <coreycb> doko, thanks I'll take a look
[20:42] <doko> coreycb, python-restructuredtext-lint and python-doc8
[20:43] <coreycb> doko, ok I think we can drop those
[20:43] <coreycb> I'll work on it
[20:47] <pitti> ah, forgot one last tomcat7 dep apparently
[20:48] <pitti> https://launchpad.net/ubuntu/+source/libcommons-dbcp-java/1.4-5ubuntu2, thanks doko
[20:51] <smoser> i'm sure this is obvious to many of you
[20:51] <smoser> what am i doing wrong here ; http://paste.ubuntu.com/15174005/
[20:52] <smoser> or what am i suppsoed to do to have autoconf re-run
[20:53] <doko> smoser, never use 'configure' as a target
[20:54] <doko> you probably want a cdbs hook
[20:54] <smoser> i read that from https://wiki.debian.org/Autoreconf
[20:55] <doko> hmm, but that's in the autotools-dev section ...
[20:55] <doko> cdbs should die
[20:56] <sarnold> doko: also here https://wiki.debian.org/Autoreconf#debhelper_packages
[20:57] <doko> sarnold, and above that is the cdbs section
[20:58] <sarnold> doko: is your advice to not use 'configure' as a target specific to cdbs? or for all package types?
[20:58] <smoser> ok. so used
[20:58] <smoser>  +include /usr/share/cdbs/1/rules/autoreconf.mk
[20:59] <doko> sarnold, it's used as a dependency on a file, and when it get's regenerated, the time stamp changes, and it's run again during the build or the install
[20:59] <smoser> instead, and it got me back to why i went down that rathole.
[20:59] <smoser> http://paste.ubuntu.com/15174062/
[20:59] <sarnold> doko: it seems like a dangerous thing to do in general :) but there it is, in the wiki, twice :) hehe
[20:59] <smoser> what is pulling CPPFLAGS of -Werror=date-time
[21:01] <doko> sarnold, if you want to read a scary rules file, see ucommon
[21:02] <sarnold> doko: wow, that looks like highly unstable spaghetti.. i'd certainly be afraid of making any changes to that package
[21:03] <doko> smoser, export DEB_CFLAGS_MAINT_STRIP = -Wdate-time before including the dpkg-buildflags.mk
[21:03] <doko> sarnold, yep, took me some time to find something to fix the build :-/
[21:04] <doko> smoser, but the better option would be to use the system libltdl. but that maybe for another time ...
[21:05] <slangasek> LocutusOfBorg: looking for the wrong name, I guess ;)
[21:05] <smoser> doko, yeah, this is really just to test a  newer squid on trusty.  merge with debian is being done by rbasak.
[21:27] <barry> doko, pitti new pex uploaded.  now we just have to wait for sync to xenial
[21:50] <lamont> smoser: it got hung up in autopkgtest
[21:50] <lamont> sadly
[21:50]  * lamont is fighting with that still, 3.0.4-1 is the current "I think it works, adt doesn't" version
[21:52] <infinity> Man, poor NoneType is always being called out for its lack of attributes.
[21:53] <lamont> infinity: we should get it some attributes, yes?
[21:53] <lamont> :*(
[21:53] <lamont> mostly I'm just being sick today
[21:53] <infinity> lamont: testlib and test-postfix just seem to be entirely full of sad.
[21:53] <cjwatson> NoneType totally has attributes.  __class__, __repr__, ...
[21:53] <sarnold> infinity: *cough* vacation *cough* :)
[21:53] <lamont> tbf, I had nothing to do with them
[21:54] <lamont> cjwatson: hah
[21:54] <infinity> cjwatson: But never the attributes people want. ;)
[21:54] <cjwatson> Picky
[21:54] <infinity> sarnold: Oh, right.  That.
[21:58] <infinity> lamont: FWIW, the quick hack (if this is the fault of the py2->py3 porting of tests) could be to just revert all changes to debian/tests/* and then add python to debian/tests/control deps.
[21:59] <infinity> lamont: adt tests don't need dep closure with package deps.
[21:59] <infinity> (Fixing the bugs would be nicer though...)
[22:12] <cyphermox> pitti: have you seen https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1548524 ?
[23:15] <juliank> cyphermox: Sounds similar to http://bugs.debian.org/815590
[23:16] <cyphermox> indeed, I hadn't seen that one
[23:17] <cyphermox> lemme add links
[23:17] <juliank> It looks like something in the dbus-glib -> gdbus transition is messed up
[23:17] <cyphermox> yup
[23:17] <cyphermox> I'm familiar enough with dbus-glib, but not so much gdbus to tell what's wrong there
[23:18] <cyphermox> I looked a bit, seems like maybe device is NULL, but I haven't dug in more to find out why
[23:19] <juliank> It should be easily reproducible though, I just had to run upower -d about 2 to 3 times in a terminal.
[23:20] <juliank> On my Debian side, systemd-coredump lost the coredump ...
[23:24] <tjaalton> so how exactly does one create a git 'project' on the lp user account? simply pushing a branch fails with "project foo does not exist"
[23:25] <cyphermox> juliank: yeah, I got it from running upower -d too
[23:28] <tjaalton> ok, had to rename the project it seems.. 'linux' works, 'ubuntu-xenial' didn't
[23:36] <tjaalton> and still wrong, think I got it now :)


[12:05]  * penguin42 yawns to the sound of 'One step beyong'
[12:05] <penguin42> d
[12:19]  * zxmpi waves to sound of microwave boiling egg
[12:21] <penguin42> zxmpi: Hmm, I've scrambled an egg in a microwave but never boiled one
[12:23] <zxmpi> got one of these in lidl https://i.pinimg.com/originals/a0/07/5f/a0075fd5f8bdd70d5dadcb938e8aa2c3.jpg
[12:25] <penguin42> do you put water in there?
[12:29] <zxmpi> fill with water to the top. poke egg with pin to burst the yoke. put lid on. zap in microwave for a few mins. 1 boiled egg
[12:30] <penguin42> is that a metal ring on it where the two parts touch?
[12:32] <zxmpi> looks like metal, feels like metal. top and bottom. but microwave seems ok with it
[12:33] <penguin42> I wonder if it's on purpose for it to get hot
[12:36] <zxmpi> well microwave cooks from within. water is only half way up egg and would boil and have steam all around it. inside the metal egg inside the plastic egg
[12:37] <zxmpi> once in a blue moon a yolk will explode because you missed it with the pin. the plastic egg sometimes pops open but contains most of the egg when that happens
[12:40]  * penguin42 had not realised the yolk exploding would have been an issue
[12:41] <zxmpi> put an average egg in microwave and it will explode. messy
[12:42] <zxmpi> yolk is a little capsule inside egg that boils first and pops
[12:45] <penguin42> yeh, I'd assumed the explosion due to the shell blowing rather than the yolk specifically


[01:55] <LLKCKfan> I have to have it the way it is set up
[20:11] <LLKCKfan> Is there a way to hook up a tv to a cable box and get a clear picture? I have it hooked from a cable bx then to a vcr/dvd that is not plugged into power and then to the tv. And it has been up this way since it was installed
[20:24] <Steve_Goodey> LLKCKfan: Might be missing something here but does turning the power on on the vcr/dvd improve the picture?
[20:27] <LLKCKfan> No
[20:29] <Steve_Goodey> LLKCKfan: What's wrong with the picture you're getting? Does it have some sort of interference?
[20:29] <LLKCKfan> Itlooks and sound like bad antennt channel
[20:30] <Steve_Goodey> LLKCKfan: I take it you can't connect the box to the TV direct?
[20:33] <LLKCKfan> I still use the vcr/dvd player so no
[20:36] <Steve_Goodey> LLKCKfan: If you remove if temporarily does the cable box picture improve? I'm wondering if the VCR/DVD could be causing RF interference.
[20:37] <LLKCKfan> It has always been hooked up loike this
[20:38] <Steve_Goodey> LLKCKfan: So the problem has only recently happened?
[20:38] <LLKCKfan> yes
[20:40] <Steve_Goodey> LLKCKfan: Ah sorry. All out of ideas then. Cable fault-VCR/DVD fault?
[20:43] <LLKCKfan> No


[04:57] <hikiko> Hi
[05:57] <pitti> Good morning
[07:18] <seb128> good morning desktopers
[07:51] <pitti> bonjour seb128, ça va ?
[07:54] <willcooke> morning all
[07:54] <willcooke> hey seb128, thanks for following up on those emails late last night.  Much appreciated.
[08:02] <Laney> moin
[08:02] <willcooke> hey Laney
[08:02] <willcooke> Wow!  I got a report from HR about the amount of holiday that people have to use up.  It's accurate to 4 decimal places
[08:03] <willcooke> TheMuso, you have 6.9992 days to use before the EOY :)
[08:03] <willcooke> Please allocate in chunks of 0.0001
[08:03] <pitti> so don't you *dare* slacking off those missing 69 seconds!
[08:04] <willcooke> :DDD
[08:06] <Laney> that's squirrel watching time
[08:08] <seb128> hey pitti willcooke Laney
[08:09] <seb128> willcooke, yw! sounds like it's a known issue with the new qt and Mirv is looking at it, unsure about timing of landing a fix though
[08:09] <willcooke> seb128, yeah, reading about that now
[08:09] <seb128> it looks like it's being discussed for a while which doesn't give confidence on a fix landing today
[08:09] <willcooke> wondering if we are allowed to declare arm64 not supported
[08:10] <willcooke> at least short term
[08:10] <willcooke> seb128, did you get an "ok" from Steve about starting the seedings?
[08:11] <seb128> yeah, recommends are fine if unhandled they shouldn't block the iso build
[08:11] <willcooke> cool
[08:11] <seb128> but it also mean the session isn't going to end up on the iso until all the depends are sorted out
[08:12] <willcooke> We're not far away from having that all sorted I think
[08:12] <seb128> right
[08:12] <seb128> we are not far away from 16.10 either though...
[08:13] <seb128> but yeah things are moving correctly
[08:14] <Mirv> seb128: willcooke: actually we're now potentially finding out it's not a Qt issue, althouh some more recompilations to make sure. it seems to happen only on yakkety, not xenial(overlay) despite identical Qt versions -> GCC6, glibc 2.24 related potentially
[08:14] <Mirv> or maybe a Qt issue but not with GCC5
[08:14] <willcooke> O_o
[08:15] <willcooke> it's a deep rabbit hole
[08:15] <willcooke> thanks Mirv
[08:15] <seb128> Mirv, which means we are not any closer from having it resolved?
[08:15] <seb128> just moving the blame to the next component
[08:15] <seb128> if it's a toolchain issue it's going to take a while...
[08:16] <seb128> do we have a fallback option/workaround for 16.10?
[08:16] <Mirv> seb128: no, just more information
[08:18] <TheMuso> willcooke: Urm, is that with all accrued by the end of year, or is that based on current data?
[08:18] <TheMuso> Hey folks bTW.
[08:19] <seb128> hey TheMuso
[08:22] <TheMuso> willcooke: Having said that, it sounds about right.
[08:23] <willcooke> TheMuso, not really sure.  I think it's accrued until the EOY, but they've already taken off the Christmas close down.  Anyway, doesn't matter - was just a good example of the ridiculousness
[08:23] <TheMuso> Oh sure.
[08:24] <seb128> willcooke, speaking of vac, I'm in discussion with Hannah about french counts, they added some extra 10 days it seems unsure why
[08:26] <willcooke> seb128, :) It did look kinda "WTF"!
[08:26] <seb128> willcooke, by law we have ~10 days/year to get back because legal work time is 35h/week and we do 40h/week so we get some compensation days, but companies have the choice to give them as vac days or to pay them and until now Canonical always took the option to pay those
[08:26] <seb128> so waiting for a reply on that
[08:26] <willcooke> erk, yes, getting paid sounds better
[08:26] <willcooke> let me know if I can help
[08:26] <seb128> should be fine, Hannah is on it
[08:27] <seb128> but thanks
[08:27] <willcooke> np
[08:28] <Laney> france is the best
[08:28] <davmor2> seb128: just move to a decent Country that doesn't complicate things and you just get paid already ;)
[08:28] <didrocks> well, in the past, we just got them paid
[08:28] <didrocks> just afraid that this year, they changed without noticing the count
[08:28] <chrisccoulson> seb128, surely you do about 70h/week? ;)
[08:28] <didrocks> and meaning that if we don't take them, they aren't paid, the count will just go to 0
[08:29] <didrocks> seb128: if you don't get an answer before your holidays, maybe willcooke should take it back on his pile of things to enjoy with HR? :)
[08:29] <Laney> hi didrocks!
[08:29] <didrocks> hey hey Laney ;)
[08:30] <Laney> how's it going?
[08:30] <Laney> saw a sexy picture of you giving a talk
[08:30] <Laney> ...although it looked like it was in the office
[08:31] <didrocks> it was in the office :)
[08:31] <TheMuso> willcooke: Since I have you here, do you have bug numbers for those tasks you added to trello on my 16.10 board for your dock issue and that other bluetooth bug? I tried to search for an appropriate bug for the latter today but without any luck so far.
[08:31] <didrocks> unsure where the picture was, didn't see it :p
[08:31] <Laney> i forgot
[08:31] <didrocks> but yeah, was in London last week
[08:31] <pitti> bonjour didrocks, comment vas-tu ?
[08:31] <Laney> sprint?
[08:31] <willcooke> TheMuso, I haven't, sorry, but I will do
[08:31] <didrocks> pitti: bien, et toi ?
[08:31] <davmor2> didrocks: London last week
[08:31] <TheMuso> willcooke: Ok thanks.
[08:31] <pitti> didrocks: je vais bien aussi, merci !
[08:31] <didrocks> Laney: no, ThingMonk (conference), then 2 days off :)
[08:32] <didrocks> and some people in my team decided that I should do a meetup in the evening
[08:32] <Laney> haha
[08:32] <willcooke> TheMuso, what should I log them against for now?  Pulse?
[08:33] <seb128> didrocks, I should have a reply this week but it's fine either way for me, it's only 10 days, worth case I take december off
[08:33] <Laney> that sounds TERRIBLE!
[08:33] <Laney> (jealous)
[08:33] <seb128> chrisccoulson, hey, you are saying I should get way more days? ;-)
[08:33] <didrocks> seb128: well, it's a big change… I have 20 days now and it's quite some cut in the pay (without notice)
[08:34] <didrocks> so they could at least have warned
[08:34] <seb128> right
[08:45] <TheMuso> willcooke: Pulse for bluetooth, alsa-driver for the dock one, because info from alsa-info is needed.
[08:46] <TheMuso> willcooke: Well it maybe needed, given that it could very well be a kernel bug.
[08:46] <willcooke> Just tried reproducing the BT one, and of course I cant
[08:46] <willcooke> I'll focus on the dock one
[08:46] <willcooke> thanks TheMuso
[08:46] <TheMuso> Ok cool.
[08:46] <TheMuso> np
[08:57] <Laney> bah bah de bah
[08:57] <Laney> can't valgrind the asgen
[08:58] <seb128> why not?
[08:58] <Laney> it's mmapping too much
[09:02] <seb128> :-/
[10:41] <Laney> http://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[10:41] <Laney> looks fun now
[10:45] <seb128> yeah, was about to mention it
[10:45] <Laney> imagine the noises doko is making :D
[10:45] <seb128> lol
[10:45] <seb128> well it's mostly looking good
[10:45] <seb128> there is little non yellow which isn't a R
[10:57] <seb128> willcooke, ^ that looks good, I send another email but it looks like the ones that need fixing are
[10:57] <seb128> * ubuntu-keyboard still depending on fonts-android
[10:58] <seb128> * u-s-s depending on dbus-property-service (I think that was not on our list, we noted down that it should be made optional but then didn't work on i)
[10:58] <seb128> * address-book-service depending on the buteo stack
[10:58] <seb128> then the ones waiting on security team
[10:59] <willcooke> ubuntu-keyboard - elleo was supposed to look at that.  Will chase.
[11:02] <seb128> hum, seems like he landed a change in http://launchpadlibrarian.net/280894470/ubuntu-keyboard_0.100+16.10.20160808.1-0ubuntu1_0.100+16.10.20160818-0ubuntu1.diff.gz
[11:02] <seb128> -Depends: fonts-droid-fallback | fonts-droid,
[11:02] <seb128> +Depends: fonts-droid-fallback | fonts-droid | fonts-noto,
[11:08] <seb128> but -noto is in universe as well...
[11:11] <willcooke> if they can move to fonts-noto-cjk we win :)
[11:11] <willcooke> (as in, no MIR needed)
[11:11] <seb128> indeed!
[12:47] <jbicha> hmm, I misunderstood the release schedule too
[12:49] <desrt> survey day!
[12:49] <desrt> good morning everyone
[12:50] <Laney> hi!
[12:52] <jbicha> seb128: Laney: what do you think of bug 1625897 ?
[12:52] <ubot5`> bug 1625897 in webkit2gtk (Ubuntu) "Update webkitgtk to 2.14.0 in yakkety" [Wishlist,New] https://launchpad.net/bugs/1625897
[12:52] <desrt> "My organisation genuinely cares about the environment"
[12:52] <desrt> some of these questions...
[12:54] <Laney> laney@nightingale> env | wc -l                                                                                ~
[12:54] <Laney> 89
[12:54] <Laney> STRONGLY DISAGREE
[12:55] <desrt> pollution
[12:55] <desrt> desrt@humber:~$ env | wc -l
[12:55] <desrt> 30
[12:55] <desrt> try debian
[12:55] <desrt> ......and a ream of "unset .." lines in your bash_profile
[12:56] <Laney> probably most of these were set by me ...
[12:56] <Laney> jbicha: I think it's a fine idea to do after beta 2
[13:09] <seb128> jbicha, I'm not in the release team, I think we have quite some bugs/issues in yakkety and we should have focussed on fixing those rather than doing version updates recently but that's only my view
[13:10] <seb128> jbicha, also all those packages migrating from cdbs to dh seems late for such changes...
[13:14] <jbicha> ok
[13:15] <andyrock> good afternoon
[13:15] <desrt> andyrock: hihi
[13:15] <seb128> hey andyrock, how are you?
[13:15] <seb128> oh and hey desrt ;-)
[13:15] <desrt> good morning seb
[13:15] <jbicha> cdbs was kinda unstable recently which motivated the pkg-gnome team to finally switch to dh
[13:15] <andyrock> my toe is getting better
[13:15] <andyrock> :D
[13:16] <desrt> i thought it was a finger?
[13:16]  * desrt feels like she just learnt something about latin
[13:16] <andyrock> and I thought that you could refer to a toe as a finger
[13:16] <andyrock> :P
[13:16] <desrt> er.  italian.
[13:16] <andyrock> at least in Italian you can do it
[13:16] <andyrock> :D
[13:17] <desrt> it's same(ish) in esperanto
[13:17] <desrt> a toe is a foot-finger
[13:19] <seb128> jbicha, weird, didn't notice any issue with cdbs and it didn't change much ... anyway rewritting the packaging has potential for bugs and has 0 benefit to users, such changes should get done early in the cycle or at least before ff, not now
[13:19] <jbicha> seb128: do you have a list of good candidate bugs for yakkety?
[13:19] <seb128> jbicha, https://bugs.launchpad.net/ubuntu/+bugs?field.tag=rls-y-incoming
[13:19] <willcooke> jhodapp, hey!  Do you know if mediaplayer-app "just works" on classic Ubuntu deskop under u8?
[13:19] <jhodapp> willcooke, it does
[13:19] <willcooke> jhodapp, sweet!
[13:19] <jhodapp> willcooke, and also as a snap now too :)
[13:19] <seb128> thanks for filing that MIR jhodapp!
[13:20]  * seb128 hides
[13:20] <willcooke> jhodapp, would you mind filing an MIR for it
[13:20] <seb128> lol
[13:20] <willcooke> :))
[13:20]  * willcooke hugs jhodapp
[13:20] <jhodapp> lol
[13:20] <jhodapp> seb128, for what change?
[13:20] <willcooke> jhodapp, I'll send you an email with the details
[13:21] <davmor2> willcooke, seb128: lightdm is still triggering a whole load of upstart jobs is that still expected?
[13:21] <seb128> jhodapp, I was mostly joking, see what willcooke said, we are about to get the unity8 session as optional on the desktop iso and we would like to include the mediaplayer so we need it promoted to main
[13:21] <seb128> davmor2, pitti knows better but yes
[13:21] <seb128> I don't think we ever ported it to systemd
[13:21] <seb128> that was blocked on indicators to land or something
[13:21] <seb128> it's late now I guess
[13:22] <jhodapp> seb128, ah, lol...I was so confused...
[13:22] <davmor2> seb128: thanks
[13:22] <pitti> seb128, davmor2: yes, I'm waiting for the indicator silo to land, then I can port the lightdm greeter
[13:22] <jhodapp> willcooke, thanks, I'd be happy to fill that out
[13:22] <seb128> jhodapp, sorry :-)
[13:22] <davmor2> pitti: thanks
[13:22] <seb128> pitti, that still didn't land?
[13:22] <seb128> crazyness
[13:22] <jhodapp> seb128, no worries :)
[13:23]  * seb128 thinks we are about to beat edgy
[13:23] <pitti> seb128: no -- I asked tedg a couple of times about the status, but no response yet; I don't know what's blocking it
[13:23] <seb128> ted is busy on doing a snap from the unity8 session
[13:23] <seb128> which is the new thing of the day
[13:23] <seb128> I think
[13:24] <willcooke> jhodapp, you got mail
[13:24] <jhodapp> willcooke, hehe, thanks
[13:24] <willcooke> jhodapp, could you send me a link when you've done it
[13:24] <jhodapp> willcooke, sure
[13:24] <willcooke> jhodapp, bear in mind it's not a final decision if we will push for it yet - depends on other work getting done, but would like to get things lined up ready
[13:25] <jhodapp> willcooke, makes sense
[13:32] <renatu> hi willcooke, I am talking with mterry about the same problem.
[13:33] <renatu> I just want to understand is the "recommend" a problem for buteo packages?
[13:33] <willcooke> hey renatu
[13:33] <willcooke> seb128, could you speak to renatu, I'm in ameeting and would like this sorting quickly
[13:33] <seb128> willcooke, sure
[13:33] <willcooke> thank you
[13:34] <renatu> seb128, hi
[13:34] <seb128> renatu, hey
[14:51] <seb128> wooot, Laney tackling yakkety bugs ;-)
[14:53] <seb128> Trevinho, andyrock, is there any reason https://code.launchpad.net/~azzar1/unity/properly-handle-copy-dialog/+merge/299301 isn't getting reviewed?
[14:53] <seb128> tedg, hey, did you see the ping about indicators/systemd landing?
[14:54] <tedg> Yeah, I was looking at the silo now. There's a bunch of build errors that need to be chased down.
[14:54] <tedg> Though, I should be able to do that some today.
[14:54] <tedg> Planning to spending a fun day with bileto
[14:59] <seb128> tedg, do you need help on those build issues?
[15:01] <andyrock> seb128: nope
[15:01] <tedg> seb128: I don't think so, I think it's JFDI type things.
[15:01] <andyrock> it should still work
[15:01] <seb128> tedg, k
[15:01] <seb128> andyrock, so just need to wake up Trevinho? ;-)
[15:01]  * seb128 sends some pizza to Trevinho
[15:01] <andyrock> i'll schedule some time tomorrow to reviews  a couple of Trevinho's MP
[15:15] <seb128> andyrock, thanks
[15:25] <willcooke> Laney, looking at:  https://code.launchpad.net/~willcooke/ubuntu-themes/hidpiicons/+merge/305219
[15:26] <willcooke> I've fixed gtk-widgets-assets-radiance.css in both places
[15:26] <willcooke> But I don't get what's wrong with ln 2218 & 2231 in Ambiance/gtk-3.20/gtk-widgets.css
[15:26] <seb128> oh, that didn't land?
[15:27] <willcooke> not yet, need to fix some bugs
[15:27] <seb128> it's getting late, maybe going to be for next time
[15:27] <seb128> time->cycle
[15:27] <willcooke> fine by me, but it's very very nearly ready
[15:27] <willcooke> if that counts for anything
[15:27] <willcooke> probably not
[15:28] <seb128> Laney, bug #1571729 on what arch did you try? it seems 32 bits specific
[15:28] <ubot5`> bug 1571729 in gnome-software (Ubuntu) "/usr/bin/gnome-software:11:look_at_pkg:load_apt_db:gs_plugin_refine:gs_plugin_loader_run_refine:gs_plugin_loader_run_results" [High,Incomplete] https://launchpad.net/bugs/1571729
[15:28] <willcooke> I also don't get what needs doing for "I also found a find and replace error that I made on a previous commit - could you look for "assets/scale.vertical-vertical-fill.png" and "assets/scale.vertical-vertical-fill-disabled.png" and fix those too please?"
[15:28] <Laney> seb128: definitely not 32 bit
[15:29] <Laney> willcooke: look for button-toolbar.png
[15:29] <Laney> willcooke: Look for those strings and fix the filenames
[15:29] <seb128> Laney, k, dunno if it's 32 bits but reports are only from armhf and i386 and it does it every time on i386
[15:30] <seb128> I should get a valgrind
[15:30] <seb128> let me does that once my daily is downloaded, which is another 10 minutes
[15:31] <willcooke> ah, line 2228
[15:32] <Laney> maybe they moved if I merged it into trunk
[15:34] <jhodapp> willcooke, https://bugs.launchpad.net/mediaplayer-app/+bug/1626164
[15:34] <ubot5`> Ubuntu bug 1626164 in mediaplayer-app "[MIR] mediaplayer-app" [Undecided,New]
[15:34] <willcooke> thanks jhodapp
[15:34] <jhodapp> willcooke, np...one change was needed so far that I completed and documented in that MIR
[15:37] <seb128> willcooke, I would not ask them to hold on it, it just doesn't need to prioritized but if they have some extra review cycles...
[15:37] <willcooke> undo
[15:37] <willcooke> undo
[15:37] <seb128> lol
[15:37] <willcooke> guess I can't delete that can I?
[15:38] <seb128> no
[15:38] <Laney> you can sometimes hide comments ;-)
[15:55] <Laney> ximion: I got a new machine with 32G of RAM ;-)
[16:02] <ximion> Laney: ...and that is another way to solve this problem :D
[16:02] <ximion> one I kind of like ^^
[16:02] <Laney> did you ever try valgrinding the asgen?
[16:02] <ximion> now you could probably even extract the localization into memory :P
[16:02] <Laney> it dies for me
[16:03] <willcooke> Laney,  https://code.launchpad.net/~willcooke/ubuntu-themes/hidpiicons/+merge/306356
[16:03] <ximion> yes, I did - but the GC makes valgrinding harder
[16:03] <Laney> lmdb cries
[16:03] <Laney> as far as I could see it tries to mmap with a huge size and valgrind needs to put that in ram, but can't
[16:04] <Laney> willcooke: merci
[16:05] <Laney> willcooke: you could have just pushed (with or without --overwrite), no need to make a new proposal
[16:06] <Laney> saves a bit of clicking anyway
[16:07] <Laney> although you need to comment in order to generate mail for the reviewer
[16:08] <Laney> urgh this locale synchronisation sucks
[16:08] <Laney> come on Jussi, fix your build system!
[16:34] <willcooke> Laney, ah, oki.  I just clicked the "resubmit proposal" button after I pushed the new stuff
[16:35] <Laney> you need that to change settings (e.g. add a prerequisite branch), but not to just add more commits
[16:35] <Laney> TYL :P
[16:35] <willcooke> :))
[16:59] <seb128> have a nice evening desktopers!
[17:07] <willcooke> cya seb128
[18:34] <willcooke> going EOD - night all
[22:07] <ximion> Laney: I valgrinded that ages ago, but I think I simply went with a very small archive there and reduced the amount of stuff that gets mmapped