[00:05] <jelmer> 'evening poolie, Noldorin
[00:06] <Noldorin> hi :-)
[00:06] <Noldorin> how's collocated branch project, i was going to ask?
[00:17] <jelmer> Noldorin: which bit in particular?
[00:18] <Noldorin> jelmer, all bits. lp, bzr, bzr-git :-)
[00:23] <poolie> hi jelmer
[00:23] <poolie> so my half-baked idea was that we should just merge the metadir colo stuff
[00:24] <poolie> putting it in a side branch has never seemed to work well, because people don't in practice test it much either as users or developers
[00:25] <poolie> also, once you ask users to test it at all, they will basically count on it
[00:25] <poolie> it's hard to do more than a smoke test without putting real data in
[00:25] <poolie> i think the most you can expect of that kind of tester is that they be willing to have a rougher ride than they normally did
[00:25] <poolie> which i suppose is kind of what dev formats went towards
[00:27] <jelmer> poolie: I'm a bit wary about using a side branch too, as it just means having to do lots of merge work (and probably bug fixing) later rather than continuously
[00:27] <poolie> that too
[00:27] <jelmer> poolie: John makes a good point about not being able to change it once it's landed though, especially as we're changing an existing format rather than introducing a new one
[00:27] <poolie> also, with the best of intentions, i don't things get the same level of review until they're actually going to come in
[00:28] <poolie> and also eventually landing them as one big bump makes things harder
[00:28] <poolie> that is true
[00:28] <poolie> i wonder if we can do something about saying "it will be stable by 2.5.0"
[00:28] <poolie> (and less stable during the betas)
[00:28] <poolie> generally speaking i don't like to make plans that rely on predictions like that but it's a tool we can use
[00:29] <jelmer> poolie: I think that might be a reasonable compromise
[00:30] <Noldorin> jelmer, hmm....?
[00:30] <Noldorin> poolie isn't hte only one here ;-)
[00:31] <jelmer> poolie: especially as I don't really expect us to make changes to the format, but it's nice if we can crawl back through the trap door if we really have to
[00:31] <jelmer> Noldorin: sorry
[00:31] <jelmer> Noldorin: we're talking about colocated branches though :)
[00:31] <Noldorin> it's ok
[00:31] <Noldorin> oh right
[00:31] <Noldorin> didn't notice
[00:31] <Noldorin> hehe
[00:32] <jelmer> Noldorin: so, the support for importing colocated branches on launchpad hasn't landed yet. No further changes are necessary to bzr-git
[00:32] <Noldorin> ok cool
[00:32] <Noldorin> and 2.5b1 coming soon?
[00:37] <jelmer> Noldorin: yes, the 15th - https://launchpad.net/bzr/+milestone/2.5b1
[00:37] <Noldorin> not soon enough ;-)
[00:37] <Noldorin> but okay
[00:37] <Noldorin> that's good
[00:37] <Noldorin> jelmer, when is LP support coming?/
[00:43] <jelmer> Noldorin: there's an approved branch that adds it, which still needs to land and then be deployed. So, hopefully a couple of days, perhaps more.
[00:43] <Noldorin> jelmer, probably by time of 2.5b1 release though right?
[01:10] <jelmer> Noldorin: probably, but they're unrelated
[01:13] <Noldorin> jelmer, in terms of release, yeah i'd presume so...ok godo to know :0
[06:04] <pippijn> hi
[06:05] <pippijn> how can I show the diff between my own repository and upstream?
[06:05] <bob2> diff or commits?
[06:05] <pippijn> diff
[06:06] <pippijn> I just need a complete patch against upstream
[06:07] <poolie> pippijn: probably 'bzr diff -rsubmit' or 'bzr diff -rancestor:UPSTREAM_URL'
[06:07] <poolie> inserting the right relative path there
[06:08] <pippijn> upstream is lp:inkscape, I think
[06:09] <pippijn> ah, I think it works
[06:11] <pippijn> yep
[06:11] <pippijn> thanks
[06:12] <pippijn> but it has to connect to upstream for this.. isn't this information also in my repo?
[06:25] <vila> hey guys !
[06:27] <lifeless> pippijn: the data is, but the information about what is current isn't.
[06:34] <pippijn> ok
[06:35] <lifeless> pippijn: you can have an explicit local mirror of lp:inkscape if you like
[06:36] <pippijn> it's ok for now
[06:36] <lifeless> it would then be up to you to pull in changes into that mirror, but you could diff when offline
[06:36] <pippijn> I'm not doing many diffs
[06:37] <pippijn> and I'm certainly not doing diffs when offline
[06:37] <pippijn> I'm only doing a diff when updating the patch in our (*puke*) svn repo
[06:40] <lifeless> heh :)
[06:55] <vila> vila_: Wrong machine ;)
[06:57] <vila> Land ! bzr committers, land ! With our new shiny pqm, running 'make check' is down to 23 mins ! \o/
[06:58] <vila> And that's without /tmp mounted as tmpfs AFAICS (S == say ;)
[07:03] <lifeless> vila: do you have --parallel=fork in place ?
[07:03] <vila> lifeless: not even :) But we don't need a losa for that, so I'm waiting for all losas tweakable stuff to be done before looking into it :)
[07:32] <poolie> hi lifeless, vila
[07:32] <vila> poolie: hello !
[07:38] <poolie> hi there
[07:47] <vila> I just did a 'bzr pull' on my bzr trunk and things look alarming !
[07:47] <vila> can anybody running from source try a 'bzr missing' ?
[07:47] <vila> I' afraid something may have gone wrong when switching on pqm maybe ??
[07:48] <poolie> hm
[07:50] <poolie> worked for me
[07:53] <lifeless> vila: alarming in what way?
[07:53] <poolie> what actually goes wrong?
[07:54] <vila> http://paste.ubuntu.com/685803/
[07:54] <vila> Note the 'Removed revisions'
[07:54] <vila> where are they gone ?
[07:55] <poolie>  ah, you should have said
[07:55] <poolie> good question
[07:55] <poolie> that does sound like something like the pqm branch being out of date
[07:56] <vila> ha, ok, they are still there
[07:56] <vila> look at revno 6124
[07:56] <poolie> they're still merged?
[07:57] <poolie> ok, so it was out of date, but jelmer's branch was based on the tip
[07:57] <poolie> that's probably why it didn't fail to push to lp
[07:57] <vila> yup
[07:57] <poolie> well, that's a bit unfortunate but i think not worth doing anything about now
[07:57] <vila> yup
[07:58] <vila> sorry for the false alarm but well, that was unexpected
[07:58] <lifeless> append_revision_only=False :P
[07:59] <vila> my thoughts exactly
[08:00] <poolie> could you get one of the losas to set that on our branches?
[08:00] <poolie> i don't see why not
[08:00] <vila> on the other hand pqm guarantees that under normal circumstances
[08:00] <poolie> obviously there is a bit of horse-has-bolted
[08:02] <vila> poolie: I kind of fear that it would make it harder to recover (we can ask for a push --overwrite if we want to fix such issues today)
[08:02] <poolie> that's true
[08:02] <poolie> so, we could ask them to push over it now and then remerge the later revisions
[08:03] <poolie> that's not really clearly objectively better
[08:03] <poolie> since none of the revisions that got pushed to the side were tagged for a release i think we should just live with it
[08:06] <vila> poolie: oh yes, let's just live with it
[08:07] <poolie> i'm glad you noticed though
[08:07] <poolie> you did have me a bit worried there was some horrible corruption :/
[08:10] <fullermd> I worry about corruption from vila all the time...
[08:10] <vila> fullermd: thanks for recognizing my hard work !
[08:10] <vila> I mean, I put a lot of effort into *not* fixing my tyops and such...
[08:11] <vila> Because it provides such an endless source of tests...
[08:11] <vila> stress tests even :)
[08:11] <fullermd> Oh, totally.  I mean, if you didn't, people might start thinking your were a chatbot!
[08:12] <vila> That's how you recognize aproject with a true TDD mentality: search for the most awkward member and nominate him as RM :-D
[09:09] <poolie> i hope eliz's mail doesn't turn into a futile thread about what's reasonable or not
[09:09] <poolie> there are a lot of things about windows that aren't reasonable
[09:11] <vila> one key point here is that it's hard to setup a windows dev machine
[09:12] <vila> as in: not documented enough or even automated
[09:22] <vila> 573 spurious import failures
[09:22] <vila> requeued
[09:25] <vila> interestingly 8 other ones were qualified as spurious and retried automatically
[09:25] <vila> i.e. the importer can already do that but not all cases are recognized
[09:30] <vila> jelmer (huh, where are you ?), Riddell : investigating http://package-import.ubuntu.com/status/73aaec3da59a46ab68e18ea8c195a6e7.html aka PristineTarError, it looks like pristine-tar can't recognize the bzip2 produced here
[09:32] <Riddell> I can't imagine what would be unusual about KDE's tars
[09:36] <Riddell> although I can recreate it locally
[09:36] <Riddell> "pristine-bz2 failed to reproduce build of kde-l10n-is_4.7.1.orig.tar.bz2"
[09:50] <poolie> o/ riddell
[09:50] <poolie> Riddell, vila, if either of you get a chance could you look into https://bugs.launchpad.net/udd/+bug/820671
[09:51] <vila> Riddell: yup, me neither
[09:54] <vila> Riddell: I digged a bit into pristine-tar itself, and well, once you found the code involved, it's basically try with this executable with this params and if you get a different result, barf
[09:55] <vila> Riddell: so while I can't imagine *what* is different in kde, it's still surprising that *only* kde packages have triggered that so far
[09:55] <Riddell> it works fine with older versions, just this version it doesn't like
[09:55] <vila> Riddell: did they jump on bzip2 wagon ahead of time ?
[09:56] <vila> which version of what ?
[09:56] <vila> Riddell: wag: 32bits/64bits ?
[09:56] <Riddell> pristine-tar from 4.6.90 to 4.7.0 works fine
[09:57] <vila> Riddell: hmm, thanks for the detail
[09:58] <Riddell> vila: I have an upstream asking for more information if he might be of use
[10:00] <vila> Riddell: you mean kde upstream or pristine-tar upstream ?
[10:00] <Riddell> vila: kde upstream
[10:01] <vila> Riddell: ha
[10:01] <poolie> i'm going to sign off soon
[10:01] <vila> my understandin gso far is that it's a pristine-tar bug, but they will indeed need more information
[10:01] <vila> poolie: enjoy your week-end !
[10:01] <poolie> thanks, i hope to
[10:05] <vila> Riddell: may be some change in bzip2 itself...
[10:05] <vila> Riddell: if this is the case, people producing the bz2 should not be able to reproduce the issue with pristine-tar ?
[10:06] <Riddell> that'll be a suse guy, I wonder if I can install pristine-tar on suse and try
[10:09] <vila> may be unrelated but the bz2 I'm looking at has root/root as user/group for all files
[10:10] <vila> nah, irrelevant, that's part of tar which bz2 don't read
[10:15] <Riddell> "<bcooksley> suse 11.4+ use bzip2 1.0.6, debian stable has 1.0.5"
[10:15] <Riddell> pristine-bz2 runs fine on suse with that tar
[10:15] <Riddell> next step would be to try upgrading bzip2 on debian and try it
[10:15]  * Riddell tries
[10:16] <Riddell> "The current version is 1.0.6, released 20 Sept 2010"  hmm, we're slacking
[10:21] <vila> Riddell: I tried running pristine-tar from sources and reproduced the issue...
[10:21] <vila> Riddell: that was yesterday though and maybe I missed some point or used the wrong sources... let me double-check
[10:21] <Riddell> vila: how do you mean pristine-tar from sources?
[10:22] <Riddell> hmm, installing bzip2 1.0.6 doesn't seem to help pristine-tar
[10:22] <Riddell> well that leaves one solution, move the UDD importer to a suse machine
[10:23] <Riddell> :)
[10:24] <vila> Riddell: bah, misread, that's bzip2 that needs to be updated ? But won't that break other tars ?
[10:24] <Riddell> I presume bzip2 is backwards compatible
[10:24] <Riddell> and mostly forwards compatible since these tars can be read by normals tools
[10:25] <Riddell> however it doesn't seem to help
[10:25] <vila> what I mean is that if we use a new bzip2 to recognize old ones, it may fails the way it fails today by using an old bzip2 to recognize new ones
[10:26] <vila> Riddell: that's confusing... do you see what I mean ?
[10:26] <vila> Guest27145: don't try to hide
[10:27] <Guest27145> :)
[10:27] <Riddell> vila: it might but surely it's going to be backwards compatible?
[10:27] <Riddell> I wonder if libbzip2 is to blame rather than bzip2
[10:28] <vila> Riddell: well, in this case, I'm afraid it means: so compatible you can't see a single difference :)
[10:30] <vila> Riddell: but it's up to pristine-tar devs to speak on that matter, I'm not sure I understand all the cases here nor the way to address them
[10:33] <jelmer_> vila, Riddell: have you seen bug 576119
[10:33] <jelmer_> ?
[10:33] <jelmer_> Debian bug 576119
[10:34] <vila> jelmer_: Yeah ! Of course not :)
[10:35] <jelmer_> The changelog entry mentions -t to try harder, which I don't think bzr-builddeb uses yet
[10:35] <jelmer_>        -t  Try harder to determine how to generate deltas of difficult bz2
[10:35] <jelmer_>            files.
[10:35] <jelmer_> worth a shot :)
[10:36] <Riddell> all programmes should have a -t Try harder option
[10:38] <jelmer_> heh
[10:38] <Riddell> "pristine-bz2 will have to try especially hard to reproduce kde-l10n-is_4.7.1.orig.tar.bz2 (This could take a long time.)" I can see it breaking sweat
[10:39] <jam> Riddell: I'm curious what it actually does. It sounds like it randomly samples time-stamps, whatever then bz2's it, then checks to see if the sha hash matches.
[10:39] <jam> Which IMO certainly does fall into the "try especially hard"
[10:39] <jam> having to indirect through *both* bz2 and sha would be terrible
[10:42] <vila> -t takes indeed far longer and... doesn't work here :-/
[10:42] <jelmer_> jam: it looks like it's indeed doing brute-forcing, but of the block size
[10:43] <jam> jelmer_: who uses bz2 that doesn't just use -9?
[10:43] <jam> (the default, and the highest level)
[10:43] <jelmer_> jam: pbzip2, which is used by the KDE folks
[10:44] <jelmer_> (p for parallel)
[11:17] <Riddell> if I install SUSE's bz2 RPM onto my ubuntu system then pristine tar works fine
[11:18] <Riddell> they do have some patches to it
[11:27] <jelmer_> Riddell: interesting
[11:31] <Riddell> this seems to be the offending patch  https://build.opensuse.org/package/view_file?file=bzip2-maxlen20.patch&package=bzip2&project=openSUSE%3AFactory&srcmd5=3ee4cf959e98e3ca50a881d1cdc13570
[11:35] <vila> Riddell: so, in effect, they *reverted* to generate the old (< 1.0.3) .bz2 files
[11:36] <Riddell> I guess so
[11:37] <vila> so if this patch is not there, bzip cannot produce such files and pristine-tar is doomed
[11:37] <vila> bzip2
[11:41] <vila> the weird thing is that it seems that pristine-tar includes zgz just for this purpose (and use 20 there not 17)
[11:43]  * vila lunch time
[11:55] <jelmer_> vila: Do you know how the merge tool code works?
[12:02] <Riddell> vila: shall I report a bug on pristine-tar or is there more we can look into?
[12:15] <vila> Riddell: I think you've found enough evidence for the pristine-tar maintainers to see (especially the url above and the failing .bz2 from the package importer)
[12:16] <vila> jelmer_: superficially yes
[12:16] <vila> . o O (It's a bit surprising that bzip2 website doesn't mention any VCS archive)
[12:18] <vila> Riddell: let me know how it goes, it would be nice to link that bug to a udd one too
[12:21] <jelmer_> vila: I'm pretty sure it's in git
[12:21] <jelmer_> vila: either way, lp:pristine-tar :)
[12:22] <vila> jelmer_: bzip2 :)
[12:22] <jelmer_> ah, sorry
[12:22] <vila> jelmer_: hehe np, I made exactly the same mistake while talking to Riddell :)
[12:23] <mthaddon> jelmer_: did you get an error email from PQM?
[12:24] <jelmer_> mthaddon: I don't think I did - I got a confirmation email to say one of my branches had landed
[12:24] <mthaddon> hmm, maybe it was just that the web UI was stale
[12:24] <mthaddon> ok, thx
[12:25] <mthaddon> vila: I think the web UI was just stale - carry on with your tests pls (one submission to any branch is fine - just want to make sure it goes through with tmpfs in place
[12:25]  * vila prepares
[12:25] <vila> mthaddon: I'll ping you first
[12:26] <jelmer_> I've just submitted another one
[12:27] <vila> jelmer_: against bzr.dev ? I'm preparing for older branches, 2.2 needs to be merged into 2.3 and up
[12:30] <jelmer_> vila: yep
[12:32] <vila> jelmer_: 1 failure (by the way, mthaddon is testing mounting /tmp as tmpfs so watch for related failures)
[12:33] <jelmer_> vila: Yeah, just noticed. Not sure what that's about
[12:33] <vila> mthaddon: I'm ready, waiting for your green light
[12:33] <jelmer_> vila: btw, did I mention I got the number of failures from running bzr.dev tests against bzr-svn down to less than 100 yesterday evening?
[12:33] <mthaddon> vila: go for it
[12:33] <vila> jelmer_: the messages about tags updated is... yummy :)
[12:33] <vila> jelmer_: no you didn't ! \o/
[12:34] <jelmer_> vila: yeah, I noticed. I'll have a look at it later today
[12:34] <vila> jelmer_: I didn't mean the bug I filed, I mean all other cases where it's great to have the feedbaclk ! :)
[12:35] <vila> back
[12:35] <vila> what with non-sense tyops !!1!!
[12:36] <jelmer_> vila: :)
[12:36] <vila> jelmer_: but now that I have a '1 tag(s) updated.' message, I wonder which tag it is :D
[12:36] <jelmer_> vila: yeah, that might be useful to mention too, indeed.
[12:37] <vila> jelmer_: I'll cowardly settle for a mutter() call :)
[12:37] <vila> hmm, looking at .bzr.log is... interesting, I didn't realize there was that much noise there ;)
[12:39] <jelmer_> vila: I think it makes sense to mention the updated tags in the output
[12:39] <jelmer_> I guess the only odd case is if somebody actually updates 200 tags
[12:39] <vila> well, I'd put it under -v with the revisions no ?
[12:41] <vila> and in this case, well, 200 or 1000, you get what you asked for ;)
[12:46] <vila> ha ha, xz incoming on jubany: http://package-import.ubuntu.com/status/pleiades.html#2011-09-09%2003:33:07.686923
[12:47] <vila> jelmer_: what did you sat about xz ?
[12:47] <vila> say
[12:56] <vila> mthaddon: no noticeable difference with tmpfs, that's.. unexpected
[12:57] <vila> mthaddon: you did the change *in* the chroot ?
[12:57] <mthaddon> vila: yep, in the chroot
[13:03] <jelmer_> vila: basically, xz is supported by bzr-builddeb; it happily calls pristine-tar
[13:03] <jelmer_> vila: however, pristine-tar doesn't support xz properly yet, so it will just generate a delta that consists of the entire file
[13:04] <vila> jelmer_: so we need a more recebt bzr-builddeb on jubany ?
[13:06] <jelmer_> vila: well, didn't you update it recently? that version should have included xz support already
[13:06] <jelmer_> however, even when we do have that it will be painful for big packages
[13:07] <vila> jelmer_: I did, revno 607
[13:07] <vila> jelmer_: well, jubany doesn't complain about pain ;) But here it fails
[13:09] <jelmer_> ah, the support is there but it assumes lzma rather than xz
[13:10] <vila> for the suffix ?
[13:12] <vila> jelmer_: nm, I can see the source... but the source suggests it handles .tar.xz fine, and with tests >-//
[13:13] <jelmer_> vila: that's just the upstream tarballs, not the stuff that's in debian
[13:13] <vila> ha ok
[13:16] <vila> mthaddon: my submission against 2.3 succeeded, I noticed the email is <pqm@cupussao> instead of<EMAIL_ADDRESS>though
[13:17] <vila> mthaddon: Patch Queue Manager instead of Canonical.com Patch Queue Manager while I mention nits...
[13:17] <fullermd> Onoes, it's a free agent!
[13:18] <mthaddon> vila: should we remove the tmpfs since it doesn't speed things up?
[13:18] <jelmer_> vila: I'll upload a patch
[13:19] <mthaddon> vila: have fixed (I think) the pqm@cupuasso part
[13:19] <vila> mthaddon: yes, but that's the first time I see tmpfs *not* providing a huge boost
[13:20] <vila> mthaddon: may be I'm confused because it makes a real difference when running with --parallel=fork ...
[13:21] <jelmer_> vila:  lp:~jelmer/bzr-builddeb/tar-xz
[13:23] <vila> jelmer_: what do you want me to do with that ? Review ? Test on jubany ? Deploy on jubany ?
[13:26] <vila> jelmer_: oh, that's *instead of* not *in addition* ?!?!
[13:29] <vila> jelmer_: I'm confused, part of this patch seem to implement 'rather than' while other so 'in addition' >-}
[13:31] <jelmer_> vila: yeah - debian doesn't actually support .tar.lzma
[13:31] <jelmer_> (xz is the second version of lzma)
[13:33] <vila> jelmer_: ha, ok.
[14:00] <Noldorin__> wha'ts the difference between bzr pull and merge?
[14:01] <LeoNerd> pull is for when you are just behind on history, and just adding extra revisions
[14:01] <LeoNerd> merge is for when you have diverged history, in a branch, and need to reconcile changes changes from both sides
[14:21] <henninge> HI! Is there a PPA for bzr builder? I need to install bzr-bulider >=0.5 on lucid.
[14:22] <AuroraBorealis> what is bzr builder?
[14:25] <henninge> https://launchpad.net/bzr-builder
[14:25] <henninge> I don't know exactly, I just need it to satisfy a dependency ...
[14:25] <AuroraBorealis> what error is it giving?
[14:28] <henninge> I am installing a package on lucid that has bzr-builder >= 0.5 as a dependency
[14:28] <henninge> but only 0.2 is packaged
[14:29] <henninge> This not really a bzr question, I guess.
[14:29] <AuroraBorealis> hmm
[14:29] <AuroraBorealis> build it using checkinstall?
[14:30] <henninge> build what?
[14:30] <AuroraBorealis> checkinstall will prodce a deb
[14:30] <AuroraBorealis> i dunno if it will work with that though
[14:31] <henninge> dpkg-buildpackage -b
[14:31] <AuroraBorealis> building debs is like black magic. i have no idea how to do it otther then checkinstall =)
[14:31] <henninge> that's ok ;)
[14:41] <Noldorin> LeoNerd, so in certain cases merge and pull will do the same thing?
[14:42] <Noldorin> i.e. when branches haven't diverged
[14:42] <LeoNerd> Er.. pass. Not sure offhand. If there's no diversion I just pull
[14:42] <Noldorin> heh ok
[14:42] <AuroraBorealis> if the branch hasn't diverged then why are you merging :o
[14:42] <Noldorin> that's not my question
[14:42] <Noldorin> LeoNerd, there's also bzr merge --pull to confuse things more ;-)
[14:43] <Noldorin> hrmm
[14:44] <henninge> Noldorin: merge and pull are different.
[14:44] <Noldorin> how so?
[14:44] <Noldorin> in the case branches haven't diverged
[14:44] <Noldorin> seems identical to me
[14:44] <AuroraBorealis> doesn't pull/push make it a mirror?
[14:45] <henninge> Noldorin: pull will pull in multiple revisions and put them in your branch.
[14:45] <henninge> Nephyrin: merge will merge the revisions which you then need to commit.
[14:45] <henninge> Noldorin: ^
[14:45] <henninge> Noldorin: that creates only *one* revision  on your branch.
[14:45] <Noldorin> henninge, ohh, got it!
[14:46] <henninge> Noldorin: and merge --pull will use pull instead of merge if the branches have not diverged.
[14:47] <Noldorin> henninge, and just normal merge if they have diverged, right?
[14:48] <henninge> right
[14:48] <Noldorin> henninge, and bzr update is like bzr merge, except it replies to the working tree rather than the branch itself?
[14:49] <Noldorin> it applies*
[14:49] <Noldorin> oops
[14:49] <henninge> ah
[14:49] <henninge> It updates your working tree from your branch.
[14:50] <henninge> if you are wokring on a full branch and working tree, merge and pull will do that for you.
[14:50] <Noldorin> henninge, bzr update merges changes from the branch into the working tree, whereas bzr pull merges from another branch into the branch?
[14:50] <fullermd> Wow, that sounds like a wildly confusing way to explain it...
[14:50] <henninge> fullermd: possibly ;)
[14:50] <Noldorin> how would you explain it?
[14:51] <Noldorin> also, merge and pull don't change the working tree afaik...
[14:51] <henninge> also, I am not sure on all aspects of update tbh
[14:51] <fullermd> I dunno, but I'm pretty sure I wouldn't try drawing parallels between merge and update   :)
[14:51] <fullermd> Er.  Both change the working tree...
[14:51] <Noldorin> fullermd, they both do merging of a sorts :-P
[14:52] <fullermd> Well, so does 'pack'   :P
[14:52] <Noldorin> i don't use pack
[14:52] <Noldorin> that's out of the question
[14:53] <Noldorin> fullermd, so if you do a pull, then an update is not necessary after right?
[14:53] <Noldorin> to get to the latest rev.
[14:53] <fullermd> Correct.
[14:54] <Noldorin> fullermd, and bzr update automatically does a pull in 'bound' branches i suppose?
[14:54] <fullermd> Oh, you don't want to get me started there...
[14:55] <Noldorin> hah
[14:55] <Noldorin> is that right though?
[14:55] <Noldorin> more or less
[14:55] <fullermd> Sorta, sometimes.
[14:56] <Noldorin> hah
[14:56] <Noldorin> well bound branches make it like centralised VCS afaik
[14:56] <fullermd> And then sometimes it does a sort of horrific pivot double-merge and completely ruins your life.
[14:56] <Noldorin> that's how i think of them
[14:56] <Noldorin> fullermd, hah i think i'll ignore that for now :-)
[15:00] <Noldorin> thanks for clearing it up anyway
[15:42] <jelmer_> vila: still there ?
[15:42] <vila> jelmer_: yup
[15:43] <vila> jelmer_: I've tried setting up a bot to do reviews but once debugged he said: nah, I don't want to do that
[15:43] <jelmer_> vila: I think we should be good to update to the latest version of bzr-builddeb
[15:43] <jelmer_> the worst thing that can happen is that xz tarballs still don't work
[15:44] <vila> jelmer_: ok, my concerns were about things like 'Cope with move of features in bzr 2.5' and other 'compat with bzr-svn' stuff
[15:44] <jelmer_> vila: those should both be backwards compatible
[15:45] <vila> thanks for confirming
[15:45] <vila> jelmer_: also, if I can deploy from bzr-builddeb trunk, I know I don't leave a weird setup someone else will be confused by
[15:46] <vila> (carrying an uncommitted change to disable the merge hook is bad enough)
[15:46] <vila> jelmer.... come back !
[15:47] <jelmer> vila: sorry
[15:47] <vila> ha, good :)
[15:47] <jelmer> vila: what I was trying to say before the kernel on my other machine oopsed..
[15:47] <jelmer> vila: those two changes should only affect the test suite of bzr-builddeb anyway
[15:47] <vila> hehe, oops, sorry not funny :-/
[15:47] <vila> ok,
[15:47] <vila> did you get:
[15:48] <vila> jelmer_: also, if I can deploy from bzr-builddeb trunk, I know I don't leave a weird setup someone else will be confused by
[15:48] <vila> (carrying an uncommitted change to disable the merge hook is bad enough)
[15:48] <jelmer> I'm still not sure why that change is necessary
[15:48] <jelmer> where do we actually merge?
[15:48] <vila> jelmer: we need a newer dpkg-dev
[15:49] <jelmer> vila: yeah, but why is that relevant if that merge hook never gets called
[15:49] <jelmer> (also, could we perhaps automatically disable the merge hook in bzr-builddeb if a new enough dpkg-dev is not available)
[15:49] <vila> it got called
[15:50] <vila> that will work yeah
[15:52] <vila> jelmer: rt #47638 by the way
[16:01] <jelmer> vila: thanks
[16:01] <vila> jelmer: ?? what for ?
[16:02] <jelmer> vila, for that rt
[16:02] <vila> jelmer: it's a week old :-/
[16:02] <jelmer> vila: for mentioning the RT # :)
[16:02] <jelmer> ... the music
[16:02] <jelmer> .. the joy it's bringing
[16:02] <vila> oh :)
[16:02] <vila> really ? Funny you mention that while a police car was under my windows :)
[16:03] <vila> That's not me !


[00:48] <GridCube> i still have this constant delay on vlc
[00:48] <Sysi> what kind on delay?
[00:50] <GridCube> a 0.4 seconds delay on the audio
[00:50] <GridCube> i have to manually set -0.4 to the audio sinc
[00:50] <GridCube> every single time
[00:51] <Sysi> ahem.. could be pulseaudio (or just alsa)
[00:51] <orngjce223> Yeah, pulseaudio causes such delays often
[00:52] <GridCube> why do i even have it?
[00:53] <Sysi> it's there by default for being needed for some stuff
[00:53] <GridCube> tried alsa, still has it
[00:54] <Sysi> you should try removing pulseaudio completely and possibly reboot
[00:54] <orngjce223> Wait no
[00:54] <orngjce223> You just need to logout/login
[00:54] <orngjce223> pulseaudio is userspace
[00:54] <Sysi> though I'm not sure how vlc/linux sounsystem actually works
[00:54] <GridCube> mmm let me try another player
[00:54] <orngjce223> aplay perhaps?
[00:55] <orngjce223> Or if you're talking video
[00:55] <orngjce223> I think mplayer offers a choice of which sound server it sends to (pulse or alsa or whatever)
[00:56] <GridCube> totem, works, sadly if i watch for over 10 minutes it thinks im doing nothing and shuts down my monitor, even if i have already dislabled that a gazillion times
[00:57] <orngjce223> Ugh
[00:58] <orngjce223> That's probably in your power settings though, not your screensaver settings
[00:58] <GridCube> you... where right
[00:58] <GridCube> XD
[00:59] <GridCube> fixed that
[01:00] <GridCube> but still vlc has a superior sound configurartion, there is no way to boost sound over 399% in totem
[02:32] <ball> hello preecher
[02:32] <preecher> ball hello
[02:47] <GridCube> hello preecher and ball
[02:47] <ball> hello GridCube
[02:47] <GridCube> :D
[05:42] <preecher> late reply but hello GridCube
[05:42] <GridCube> ;)
[05:42] <preecher> i fell asleep
[10:18] <wizpig64> installing xubuntu as i chat, neato.
[11:04] <xubuntu491> hello
[20:09] <beanluc> Where is the channel log? I just saw the welcome message
[20:10] <beanluc> says there'
[20:10] <beanluc> there's a log
[20:10] <beanluc> ids it on the web somewhere?
[20:10] <beanluc> TYVM
[20:10] <Sysi> !log
[20:10] <beanluc> TYVM
[20:17] <beanluc> Regarding installation: Is there ANYTHING different about xubuntu vs. vanilla ubuntu? ubuntu documentation doesn't have anything to help with a problem i'm having with xubuntu
[20:17] <beanluc> So is this  a good place for me or should i go to #ubuntu?
[20:23] <Sysi> xubuntu has different GUI and some apps
[20:23] <Sysi> !xubuntu
[20:23] <beanluc> thanks Sysi but that's true only after installation is complete, eh? heh, just kiddin
[20:23] <beanluc> in short, i used the 10.04 CD to install, but first boot yields only a grub prompt
[20:24] <beanluc> no xubuntu
[20:24] <beanluc> IDK what to do
[20:24] <beanluc> single boot system
[20:24] <beanluc> nothing fancy
[20:24] <Sysi> failed burn maybe
[20:25] <beanluc> the whole installer ran fine... wasnt until re-boot that any prob showed up
[20:25] <Sysi> oh
[20:25] <beanluc> bad burn would have had failed installer, right/
[20:25] <beanluc> ?
[20:25] <Sysi> yes
[20:26] <beanluc> OK well I'm looking for 2 bits of help: How to boot from grub prompt, and, how to fix grub
[20:26] <beanluc> thanks for any help
[20:26] <charlie-tca> !grub
[20:41] <richez> very quiet
[21:02] <beanluc> It was bad HDD sectors... nothing wrong with installation
[21:02] <beanluc> all better now
[22:31] <beanluc> Hello, vanilla ubuntu has a menu, System -> Administration -> Services... I can't find this on my brand new xubuntu desktop
[22:31] <beanluc> Any help? Thanks
[22:33] <Sysi> find out what app it is and install it
[22:35] <beanluc> "find out what app it is"... ok shall i ask that over in #ubuntu
[22:42] <charlie-tca> beanluc: usually that' s either menu -> System or menu -> Settings Manager.
[22:44] <beanluc> charlie-tca I have an Applications menu, it does have Settings (this only contains xfce settings) it also contains System
[22:44] <beanluc> charlie-tca my Applications -> System menu has lots of useful things but not Services
[22:44] <beanluc> do you know what the application is, á la Sysi's advice?
[22:45] <beanluc> charlie-tca my Applications -> System menu has lots of useful things but not Services - not Administration sub-menu  or app either
[22:45] <charlie-tca> because Services is part of Gnome instead of Xfce. Even after you install that, it won't be the same as gnome, because this is not gnome
[22:46] <beanluc> oh
[22:48] <beanluc> charlie-tca "won't be the same as Gnome" well will it be useful at all under xfce?
[22:48] <beanluc> Does anyone know of a *similar* app for xfce?
[22:49] <charlie-tca> Services is a gnome menu for gnome items, I don't think much of xfce settings will be there.
[22:49] <Sysi> apps work but desktop itself stays different
[22:49] <Sysi> I guess "services" to be some upstart config gui
[22:50] <charlie-tca> no, sysi
[22:50] <beanluc> "Services is a gnome menu for gnome items" well it appears to be used for httpd, mysqld, ftpd, and services like that... those sure don't have to do with Gnome
[22:50] <charlie-tca> it is a system menu in gnome,
[22:50] <beanluc> I'm taking this from the LAMP Howto on ubuntu.org
[22:51] <charlie-tca> okay, which tells you to install lamp in Ubuntu?
[22:51] <Sysi> ugh, really hard to say about gnome stuff when you've never used it
[22:52] <charlie-tca> If you are using Xubuntu, you can look in the menus there are to find those same entries, but they will not be in the same place because this is not gnome
[22:52] <beanluc> Does anyone know of a *similar* app for xfce? I really don't appear to have a GUI services manager at all.
[22:52] <charlie-tca> Ubuntu has always made things much easier/simpler for the user.
[22:54] <beanluc> Huh?
[22:54] <charlie-tca> my gftp shows up in Internet in the menu
[22:55] <well_laid_lawn> beanluc: is it a daemon controller that's needed?
[22:55] <beanluc> Lawn, could be
[22:55] <beanluc> Just a lil controlpanel showing services with start/stop/pause
[22:56] <beanluc> naturally i can just do it from CLI but I'm running xubuntu vs. totally headless for a reason
[22:56] <charlie-tca> sessions and startup?
[22:56] <beanluc> be nice to take advantage, en?
[22:57] <charlie-tca> I use task manager to stop/kill apps, session and startup in settings manager has some of that, too.
[22:57] <beanluc> very interesting... I don't have "startup" either
[22:58] <charlie-tca> You have a menu -> Settings -> Session and Startup?
[22:58] <charlie-tca> not session
[22:58] <charlie-tca> not startup
[22:58] <charlie-tca> Sessions and Startup
[22:58] <beanluc> I sure don't
[22:58] <beanluc> The only menus I have are Applications and Places
[22:59] <charlie-tca> Click on Applications
[22:59] <charlie-tca> click on settings
[22:59] <beanluc> Under Applications, there is Settings (for xfce settings)
[22:59] <beanluc> and there is System
[22:59] <charlie-tca> do you have a settings manager?
[22:59] <beanluc> with none of the useful things we're talking about
[22:59] <charlie-tca> click on Settings
[23:00] <beanluc> mmhm
[23:00] <beanluc> XFCE 4 Settings Manager
[23:00] <charlie-tca> click that
[23:00] <charlie-tca> now go to Sessions and Startup
[23:00] <beanluc> it's totally desktop oriented
[23:01] <beanluc> I don't see how to use it for daemons
[23:01] <charlie-tca> yes, it is
[23:01] <beanluc> I don't want httpd to stop when I log out of desktop so... this doesn't look like the thing to sue
[23:01] <beanluc> \"use"
[23:02] <well_laid_lawn> it just looks different
[23:03] <beanluc> It sure does: here's what we've got
[23:04] <beanluc> "Below is the applications that will be started when you *log into Xfce Desktop*, in addition to apps that were saved when you logged out last time
[23:04] <beanluc> thats under application autostart
[23:04] <beanluc> Then under the Sessions tab we've got
[23:04] <beanluc> "These apps are part of the currently running session"
[23:04] <beanluc> as in" DESKTOP saession
[23:05] <beanluc> and no9ne of these things have like start/pause/stop/restart buttons
[23:05] <beanluc> which you'd want for daemons, amirite
[23:05] <well_laid_lawn> is httpd listed?
[23:05] <beanluc> heh, well */I/* do anyway
[23:06] <beanluc> No, httpd isn't there but it is there under ps
[23:06] <beanluc> see what i mean? it's completely irrelevant to the desktop, and this Sessions and Startup thingy knows it
[23:21] <JeZ-l-Lee> does anyone know how to change the space between icons on the desktop on Xubuntu 11.04 ?
[23:23] <charlie-tca> JeZ-l-Lee: menu -> Settings -> Desktop, icons tab, the size of the icon is preset to 36
[23:23] <charlie-tca> changing that changes the length of the name and positions
[23:25] <JeZ-l-Lee> charlie-tca - is it possible to modify the space between desktop icons?
[23:25] <JeZ-l-Lee> new to Xubuntu - just installed it today
[23:25] <charlie-tca> NOt without a lot of extra editing of files
[23:26] <charlie-tca> space is preset by the developers, and not easy at all to modify
[23:27] <JeZ-l-Lee> Was using regular Ubuntu for few years, but Unity made me switch to Xubuntu and XFCE
[23:28] <JeZ-l-Lee> Gnome 3 and/or Unity is just awful
[23:28] <charlie-tca> Xubuntu/Xfce welcomes all new users. However, it will not be the same as gnome was.
[23:29] <charlie-tca> Xfce does allow more configuration, but also requires the user work a bit more at doing that
[23:29] <beanluc> "Xfce does allow more configuration" hehe, not desktop icon spacing tho eh?
[23:30] <beanluc> Actually charlie-tca and Sysi, I'm gonna go with webmin
[23:31] <beanluc> for my services thingy
[23:31] <beanluc> that will work
[23:32] <charlie-tca> It can be done, you just have to dig into the code to do it. Have fun while digging
[23:32] <JeZ-l-Lee> got my XFCE desktop set my way - have a look: http://16bitsoft.com/images/Desktop_07-2-2011a.png
[23:34] <JeZ-l-Lee> I was a fan of Gnome 2.x - but that is gone now
[23:34] <well_laid_lawn> there's a port of it a bloke is maintaining in archlinux
[23:35] <charlie-tca> Has he ported it to gtk3 yet?
[23:35] <charlie-tca> That seems to be the biggest issue with maintaining it. GTK2 is on the way out
[23:37] <orngjce223> Sorry, hit the wrong button
[23:37] <orngjce223> But we've gotten two complaints about desktop icon snap in three days, :v
[23:55] <JeZ-l-Lee> .


[00:53] <phunyguy> @btlogin
[07:08] <Jordan_U> We really are going to need to write a policy on support for Ubuntu on Windows in #ubuntu at some point.
[07:08] <dax> e.g. when it comes out
[07:08] <dax> until then, #ubuntu-{offtopic,discuss}
[07:10] <dax> !ubuwin is <reply> Canonical and Microsoft have announced that Windows 10 will be able to run Ubuntu programs without needing porting/recompilation. This functionality has not yet been released. For general discussion, see #ubuntu-offtopic and/or #ubuntu-discuss.
[07:10] <dax> !ubuwin =~ s/general //
[07:10] <dax> !win10 is <alias> ubuwin
[07:12] <Unit193> Might actually want to talk with ##windows people, find out what's going on with them.
[07:13] <dax> i'm just glad the idea of forwarding people talking about it over there didn't catch on
[07:13] <dax> i don't imagine they'd appreciate that
[07:13] <dax> but yeah, that's a good idea
[09:02] <Myrtti> why do I even bother
[09:56] <k1l> Voyage: hi
[10:00] <Voyage> k1l,  HI
[10:00] <k1l> Voyage: what brings you here?
[10:02] <Voyage> auto join.. maybe
[10:03] <Voyage> parting
[10:04] <k1l> ok, so i guess he doesnt want to resolve the bans
[10:05] <k1l> @mark Voyage seems to have no interest in ban resolving.
[10:35] <ikonia> for the record it's not auto join
[10:35] <ikonia> he often tries to join ubuntu channels unclocked to get around the ban,
[10:35] <ikonia> hello mcphail
[10:35] <mcphail> Hi - would anyone be kind enough to pop in to #ubuntu and have a look at hary_potter?


[12:24] <saiarcot895> There's a package in a PPA called my-weather-indicator that was built as a native package; shouldn't it be non-native?
[12:36] <tsimpson> probably, but that's up to the packager
[15:09] <pmjdebru1jn> hi folks
[15:10] <pmjdebru1jn> I have an issue where upstream changed a release tarball (because of a release error)
[15:10] <pmjdebru1jn> except that I already pushed the initial faulty tarball to my ppa
[15:10] <pmjdebru1jn> now I can't upload the "correct" one
[15:10] <pmjdebru1jn> would I need to do a repack reversioned tarball?
[15:10] <pmjdebru1jn> deleted the "wrong" packages doesn't seem to allow the new tarball
[15:10] <pmjdebru1jn> deleting*
[15:15] <mapreri> pmjdebru1jn: afaik you have to upload the new one with a different version, since lp doesn't accept two source package with the same version (even if you delete one first, lp remember everything ;P)
[15:18] <pmjdebru1jn> mapreri: sure, typically that makes sense
[15:18] <pmjdebru1jn> I'm dealing with a misbehaving upstream :(
[15:18] <pmjdebru1jn> so 0.19 is the current version, so I'd have do so 0.19repack1 or something like that
[15:19] <pmjdebru1jn> do so/to do
[15:19]  * pmjdebru1jn wonders if there's an official procedure for this
[15:19] <pmjdebru1jn> +repack seems common
[15:20] <mapreri> pmjdebru1jn: eheh, not all upstream are developer-friendly ;) I suggest you to upload an 0.19-1 or something like your idea
[15:20] <mapreri> yeah. even +repack is ok, but I don't like to see it (personally opinion, of course). You are dealing with a ppa, so you can call your software version as you prefer
[15:21] <pmjdebru1jn> I don't like it either :)
[15:21] <pmjdebru1jn> this isn't about liking anything :)
[15:21] <pmjdebru1jn> but
[15:21] <pmjdebru1jn> my debian version is already higher
[15:21] <pmjdebru1jn> and it won't accept
[15:21] <pmjdebru1jn> so I guess the upstream tarball needs renaming
[15:21] <pmjdebru1jn> well reversioning
[15:21] <pmjdebru1jn> at least +repack0 seems common-ish
[15:22] <pmjdebru1jn> so would be something like 0.19repack0-0ubuntu1pmjdebruijn1~precise :D
[15:23] <mapreri> omg -.- the lp versiong is horrible sometimes
[15:23] <mapreri> versioning*
[15:23] <pmjdebru1jn> well partially it's forced
[15:24] <pmjdebru1jn> so... :(
[15:24] <mapreri> you right...
[15:24] <pmjdebru1jn> I always add teh pmjdebruijn tag to make it easy to identify my packages
[15:24] <pmjdebru1jn> so that's just a practical thing too
[15:25] <pmjdebru1jn> and ~precise is required to have the same package for several dists
[15:25] <pmjdebru1jn> anyhow, it's workable nontheless
[15:25] <pmjdebru1jn> it's least there's some logic to it
[15:26] <pmjdebru1jn> anyhow, thanks
[15:27] <mapreri> there is some logic, but the logic is for machines, not for humans ;)
[21:46] <cjwatson> mapreri: eh, this isn't lp versioning, it's self-inflicted :P


[20:21] <OvenWerks> Eickmeyer: dist-upgrade just put in a new menu file... perhaps icons as well (not sure). Anyway, assuming 1804 iso, I do have backports enabled as well.
[20:21] <Eickmeyer> Yep, fixes the zynaddsubfx bug.
[20:22] <Eickmeyer> dist-upgrade == full-upgrade
[20:22] <OvenWerks> Eickmeyer: anyway, whisker looks ok, but applications menu does not. and also right click on the backdrop does not look right
[20:22] <Eickmeyer> Right click on the backdrop should've been unaffected. Sounds like a different bug.
[20:22] <OvenWerks> The icon for ubuntu studio info is way too big
[20:22] <Eickmeyer> *shouldnt've
[20:23] <Eickmeyer> Strange, it should conform.
[20:23] <Eickmeyer> I'll take a look, but I didn't notice that.
[20:23] <Eickmeyer> I could revert the backport, if necessary.
[20:23] <OvenWerks> it may be that the icon in the directory file points at the wrong one
[20:24] <Eickmeyer> Very possible.
[20:24] <Eickmeyer> Might be that there aren't enough sizes available.
[20:25] <OvenWerks> Right, maybe whisker uses a slightly different size? or resizes on the fly to fit
[20:28] <Eickmeyer> I'll make more sizes and add them. Should probably be a size for every size available in HiColor
[20:29] <OvenWerks> It is interesting to me that none of the other icons in the rest of the menu have this problem... maybe we fixed the rest
[20:40] <Eickmeyer> Yeah. I'll work on that in a few.
[20:41] <OvenWerks> no rush, we install whisker anyway and I am probably the only person who uses the app menu or thinks to right click on backdrop
[20:43] <OvenWerks> I do not know if the app menu is even still maintained...
[20:44] <OvenWerks> Possibly for 2004 I will switch to kde anyway (which also gives an appmenu choice)
[22:33] <Eickmeyer> OvenWerks: The difference there is that Plasma's menus scale nicely. iirc they use the svg icons.
[22:37] <Eickmeyer> OvenWerks: And, yes, the old appmenu doesn't use svg, and we only provide 16x16,, 32x32, 48x48, and scalable sizes of the problematic icon, so that's the problem. This will definitely take a while.
[22:40] <Eickmeyer> Probably only going to go up to 64x64. Bigger than that is rediculous.
[22:40] <Eickmeyer> *ridiculous
[22:40] <OvenWerks> Ya
[22:42] <OvenWerks> It may be enough to change ubuntustudio-logo to ubuntustudio-logo-menu
[22:42] <OvenWerks> but I don't know where each is :)
[22:43] <Eickmeyer> ubuntustudio-logo-menu is in -default-settings, iirc.
[22:43] <Eickmeyer> And, iirc, it has size limitations as well.
[22:43] <OvenWerks> Sorry, I meant where in the disk tree, one may be in "pixmaps" for example
[22:44] <Eickmeyer> Yeah, one is in pixmaps.
[22:45] <Eickmeyer> Honestly, This is going pretty smoothly so far. I've got a workflow going.
[22:47] <Eickmeyer> Was only the info category icon the issue?
[22:48] <OvenWerks> also website and contribute
[22:48] <OvenWerks> probably the same icon.
[22:48] <Eickmeyer> Confirmed, those are the same icon.
[22:52] <OvenWerks> I thought we had a Hexter icon, seems not.
[22:54] <Eickmeyer> I see an icon for it. I think the Hexter people finally made an icon. I see it in 19.10. I remember something in the Debian Multimedia mailing list about this.
[22:54] <OvenWerks> I'm in 1804 so that could be
[23:00] <Eickmeyer> Ok, about to trigger a new build for backports. Also going to push that to eoan.
[23:27] <Eickmeyer> OvenWerks: New -menu just dropped in Backports.


[02:06] <bregma> robert_ancell, your unity-session-compositor LightDM branch is working really well for me, but is there any way to configure environment variables to pass to unity-system-compositor before starting it?
[02:07] <robert_ancell> bregma, not that I can think of, what sort of variables?
[02:07] <bregma> ANDROID_ROOT in particular, used to find device configuration files (instead of /system)
[02:08] <robert_ancell> bregma, you can make a shell script for the compositor and set the name of that in lightdm.conf
[02:08] <robert_ancell> if that's something more permanent, we could look into options
[02:08] <bregma> yeah, that was my next plan, assuming even using device files will solve my problem
[02:09] <robert_ancell> I'm not sure off hand if the global env variables make it through to the compositor or we have a clean environment
[02:10] <bregma> well, it's probably a sort of last-resort solution anyway, since going that route woukld require shipping device configuration for pretty much every known device
[02:10] <bregma> but if that's what it takes....
[02:12] <robert_ancell> yeah, shell script time for you :)
[03:26] <robru> cyphermox, hey i installed urfkill... how will i know it's working? what steps should I take o test it?
[05:49] <pitti> Good morning
[06:16] <TheMuso> pitti: Thanks for chacing down that espeak issue. That really was a weird one.
[06:17] <TheMuso> Well... Working around the dpkg issue that is.
[06:25] <pitti> TheMuso: well, it's not dpkg, it's overlayfs/aufs
[06:25] <pitti> TheMuso: and I'm far from proud about that workaround, but I didn't find a better one
[08:02] <pitti> Laney: do you know what holds glib 2.38 back from unstable?
[09:02] <Laney> morning
[09:02] <Laney> pitti: the ftbfs
[09:02] <seb128> hey laney
[09:02] <seb128> good morning desktopers
[09:03] <Laney> hey seb128
[09:03] <Laney> how's it going?
[09:04] <pitti> bonjour seb128
[09:04] <pitti> hey Laney
[09:04] <Laney> hola
[09:04] <seb128> pitti, guten tag! wie gehts?
[09:04] <seb128> Laney, good! you?
[09:04] <pitti> Laney: ah, of course
[09:04] <Laney> bigon was looking at the build failures a bit but I don't think he got anywhere
[09:04] <pitti> seb128: gut, danke!
[09:05] <Laney> good thanks seb128!
[09:05] <Laney> pub quiz last night ;-)
[09:07] <Laney> seb128: seen https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1260473 ?
[09:07] <ubot2`> Launchpad bug 1260473 in Ubuntu Kylin "The slide bar that allow to rezise the partition does not appear" [Medium,Triaged]
[09:11] <seb128> Laney, now I did ... that seems similar to https://code.launchpad.net/~larsu/ubiquity/lp1260396
[09:11] <seb128> that fix landed right? (I didn't follow up, that was during my holidays, just saw it mentioned when looking to what happened while I was not there)
[09:12] <seb128> Laney, the mp got approved only on monday and we didn't have an ubiquity upload since
[09:12] <Laney> not sure that's the same
[09:13] <seb128> yeah, me neither
[09:14] <seb128> it would be good to land an update with the fix from Lars though
[09:15] <seb128> would it only be to avoid debugging something that's already fixed (if that turns out to be the same issue)
[09:15] <seb128> xnox, hey, do you plan to do an ubiquity update in trusty?
[09:22] <seb128> didrocks, hey, do you have any opinion on what integration tests we should have before merging https://code.launchpad.net/~diegosarmentero/ubuntu-system-settings/click-updates/+merge/195729 in?
[09:23] <seb128> didrocks, there is some pushback in recent comment saying it makes the review longer and should be in another merge later on, I'm just unsure that they are going to care once that one land so I'm tempted to ask for the branch with tests to be ready before we merge that one
[09:23] <didrocks> seb128: for system image update, it would be nice to use barry's mock and that the mock so that we ensure we receive the right signals
[09:23] <didrocks> seb128: well, if I were you, I would really bind the 2 merges (tests and code) together, otherwise, you know how it goes
[09:24] <seb128> didrocks, I guess they are going to argue that the system image is your code and that they didn't change/don't own it :p
[09:24] <seb128> right
[09:24] <didrocks> seb128: they did change it, right?
[09:24] <seb128> they changed the UI and refactored
[09:24] <didrocks> yeah, both the UI and backend
[09:25] <seb128> didrocks, well, it looks like they kept most of your updates.cpp, just did s/updates/systemupdate
[09:26] <seb128> in any case, let's me try to get them to add some more testing there
[09:26] <didrocks> seb128: there are some new objects retaining all states, not sure the signaling is still working
[09:26] <seb128> ok
[09:26] <didrocks> seb128: and yeah, you know how QML can be, when changing it :p
[09:36] <seb128> didrocks, so, can I try to land the u-s-s update we put in CI train yesterday or is the system down due to the canonistack issues?
[09:36] <didrocks> seb128: you can try, there are a lot of network issues
[09:37] <didrocks> so be prepare to run and rerun
[09:37] <seb128> didrocks, is #is looking at those?
[09:37] <didrocks> seb128: not sure, asked twice yesteday
[09:37] <didrocks> nothing happened
[09:37] <seb128> did you get anyone responding?
[09:37] <didrocks> in meeting…
[09:37] <didrocks> well, everyone using canonistack
[09:37] <didrocks> so yeah
[10:08] <xnox> seb128: after bug #1260473 is fixed, ubiquity will be uploaded.
[10:08] <ubot2`> Launchpad bug 1260473 in Ubuntu Kylin "The slide bar that allow to rezise the partition does not appear" [Medium,Triaged] https://launchpad.net/bugs/1260473
[10:08] <seb128> xnox, so it's a different issue than the one larsu fixed?
[10:08] <xnox> which also appears to be a gtk+ / themeing bug.
[10:08] <seb128> xnox, do you need help debugging it? is it easy to reproduce?
[10:09] <xnox> seb128: yeah, larsu's fixed is good. the installer is no 3X width the monitor screen.
[10:09] <xnox> seb128: well... we have a custom widget that is using deprecated gtkwidget themeing.... what could go wrong?! =)
[10:10]  * xnox needs to do a minimal example. As going from start to "dual-boot install" takes some time.
[10:13] <seb128> xnox, yeah, having a small example code would be nice
[10:23] <didrocks> seb128: ok, seems we are going to redeploy another instance in lcy01
[10:23] <didrocks> seb128: as I can't get any instance up on lcy02, it means I can't rsync the filesystem :/
[10:23] <didrocks> so, I'll have to rerun your build job with the same parameters
[10:24] <didrocks> (and reconfigure the silos)
[10:24] <didrocks> mind if I do that? So that you are unblocked ASAP
[10:25] <czajkowski> Laney: which train are you on to FOSDEM ?
[10:25] <Laney> 1532 or so
[10:25] <czajkowski> :(
[10:25] <seb128> didrocks, whatever unblocks the upload wfm
[10:25] <didrocks> seb128: ok ;)
[10:25] <Laney> y u sad
[10:25] <didrocks> asac: FYI, applying the band-aid version (I'll rerun the stuff for seb128 to not have to redo it himself) ^
[10:25] <seb128> didrocks, I've other changes to land today btw, not sure if we want to batch those or just redo a landing
[10:26] <czajkowski> Laney: I'm on the 12
[10:26] <ochosi> seb128: thanks for checking my merge-request on indicator-power and spotting the obvious whoopsie. anyway, i was also wondering whether this patch doesn't introduce problems for ubuntu-gnome, or are they not using indicators at all?
[10:26] <didrocks> seb128: as you prefer, we can do that, sure
[10:26] <Laney> czajkowski: the other uk-ers too?
[10:26] <czajkowski> yp about 10 going from our LUG
[10:26] <czajkowski> :D
[10:27] <czajkowski> Laney: stop by the NoSQL room on sunday will be there all day for a cupcake!
[10:27] <Laney> ^_^
[10:27] <mlankhorst> ;D
[10:29] <seb128> ochosi, yw, larsu said he's going to tweak it and land it I think
[10:29] <asac> didrocks: what is the bandaid version?
[10:30] <asac> is that the bandaid of the bandaid :P
[10:30] <seb128> ochosi, well, Ubuntu GNOME doesn't use indicators so they shouldn't be impacted by whatever the indicator code is doing
[10:30] <didrocks> asac: redeploying somewhere else and rerunning myself the job so that seb128 is in the same state
[10:30] <ochosi> seb128: ah, nice!
[10:30] <ochosi> seb128: ok, that's good to hear, cause i was afraid that the gnome-control-center call was for them...
[10:30] <asac> didrocks: yeah. unfortunate, but this exercise of redeploying etc. is probably worth it
[10:31] <asac> didrocks: how would the system behave if we just deploy it 2-3 times (e.g. on different regions)
[10:31] <asac> and the switch to whereever we get what we want?
[10:31] <seb128> ochosi, I think the g-c-c call was more "we didn't think much about the different usecase and let the old command as default"
[10:31] <didrocks> asac: not possible accross regions
[10:31] <didrocks> asac: the rules for having something quick were clear: one instance, one filesystem
[10:32] <asac> didrocks: sure, but we could have one spare?
[10:32] <didrocks> asac: well, you have to rsync the filesystem between the 2
[10:32]  * asac guesses that causs races etc.
[10:32] <didrocks> which isn't possible here
[10:32] <didrocks> as we even can't brought up an instance on lcy02 to attach to filesystem
[10:32] <ochosi> seb128: i see. well i'm sure ubuntu-studio will also be greatful for this getting in, as it'll make it very easy for them to also use -power if they want to, so thanks for the quick review!
[10:32] <seb128> ochosi, yw ;-)
[10:36] <ochosi> larsu: let me know if you want me to update the MR or if you're just going to throw the "gchar *path;" and "g_free (path);" into the Unity-if yourself
[10:37] <asac> didrocks: that is only if you dont want to risk loosing progress on active landings/silos?
[10:37] <asac> e.g. what will we loose if we redo the filesystem?
[10:37] <didrocks> asac: right
[10:37] <asac> ok thats fine
[10:37] <didrocks> all progress
[10:37] <didrocks> all silo attributions
[10:37] <asac> for a moment i was scared that we need to backup filesystem
[10:37] <larsu> ochosi: I'm doing it right now. Thanks!
[10:38] <didrocks> asac: and changing instance means changing some metadata on the spreadsheet, meaning if people keep IP directly, they won't work
[10:38] <asac> didrocks: the IP is recorded in the spreadsheet for the silo? what else?
[10:38] <didrocks> well, here, we need to have new public IP
[10:38] <asac> e.g. what else is instance specific
[10:39] <didrocks> and new firewall rules
[10:39] <didrocks> but that's only one time, we'll keep both opened then
[10:39] <asac> ok. we cant reassign the IP:)
[10:39] <asac> like elastic ips?
[10:39] <asac> maybe we have something like that?
[10:39] <asac> note: this is just theory talk so i understand better
[10:39] <didrocks> I don't think they have this notion accross instances
[10:42] <ochosi> larsu: ok, thank *you* in fact :)
[11:13] <Laney> bah
[11:13] <Laney> webkit ooming on the porterbox
[11:16] <seb128> Laney, well, does it mean that it went far enough that it should build?
[11:16] <Laney> not quite ...
[11:16] <seb128> :-(
[11:18] <Laney> -Wl,--reduce-memory-overheads HEAR MY CALL
[11:18] <mitya57> Didn't Debian fix the FTBFS on i386 recently?
[11:20] <Laney> I'm not looking at that
[11:21] <Laney> (ppc)
[11:21] <mitya57> Ah, yes, ppc
[11:22] <mitya57> Then I am waiting for your fix to apply it to qtwebkit :)
[11:22] <Laney> does that track webkit 2.3.x?
[11:23] <mitya57> 2.3 is webkitgtk numeration, not upstream one
[11:23] <Laney> you know what I mean
[11:24] <Laney> I'm trying something quite similar to http://pkgs.fedoraproject.org/cgit/webkitgtk3.git/tree/webkitgtk-1.11.5-libatomic.patch?id=2d4347bc2e76a07a8a0d6e8260730dfc91b0410e
[11:24] <mitya57> qtwebkit 5.2.0 is webkit 538.1, don't know about the gtk one
[11:25] <Laney> trying one more time with --reduce-memory-overheads
[11:25] <Laney> otherwise I'll just take the chance probably
[11:29] <didrocks> seb128: sil2100: can you check that you can login in and have enough rights on http://<IP_ADDRESS>/ ? (to run some jobs)
[11:31] <seb128> didrocks, what job can I try on?
[11:32] <didrocks> seb128: just check if you have the "build" button
[11:32] <seb128> didrocks, I don't
[11:32] <seb128> didrocks, on what job should I have one?
[11:32] <didrocks> hum
[11:32] <didrocks> everyone but deploy
[11:32] <seb128> I tried http://<IP_ADDRESS>/job/landing-001-1-build/
[11:32] <didrocks> and configure silo
[11:32] <didrocks> ok, let me check
[11:33] <didrocks> seb128: when you logged in, you have tick the teams you are in, right?
[11:33] <sil2100> hmm, I have some problems logging in
[11:33] <seb128> didrocks, yes, u-c-d
[11:33] <seb128> didrocks, but even without that, before I had a build button even when not logged in
[11:33] <seb128> clicking on the button would send me to the auth page
[11:33] <seb128> didrocks, http://ubuntuone.com/3X3SNx74hOelkX9J5kuZDE
[11:34] <didrocks> seb128: I don't see a build button here, you meant, you had one when not logged in?
[11:34] <sil2100> didrocks: do I have to create a new ubuntu one account here? Since it seems I cannot get my existing credentials to work
[11:35] <seb128> didrocks, yes, remember the discussion the other time? I had the "build" button even when not logged in before
[11:35] <didrocks> sil2100: yeah, it's using staging sso
[11:35] <seb128> didrocks, I first though it was a bug, but clicking on it was sending to a login page
[11:35] <didrocks> seb128: it's when you go to the build page directly
[11:35] <didrocks> (this isn't the build page)
[11:35] <seb128> oh
[11:35] <seb128> I got confused by jenkins UI again
[11:36] <seb128> well, anyway, I'm logged in and checked the u-c-d team (which was the only listed)
[11:36] <didrocks> ok
[11:36] <didrocks> let me check why
[11:36] <seb128> didrocks, is the canonical team supposed to be in the list?
[11:36] <didrocks> seb128: no, is it?
[11:36] <seb128> (it's not)
[11:36] <didrocks> ok ;)
[11:36] <didrocks> we can't
[11:36] <seb128> no, but I though it was before
[11:36] <didrocks> as we are not whitelisted
[11:36] <seb128> ok
[11:37] <didrocks> there was a canonica-ci
[11:37] <didrocks> canonical-ci*
[11:37]  * didrocks finished to resetup the rsync
[11:37] <didrocks> ok, now let's see those creds
[11:43] <didrocks> seb128: better now?
[11:44] <seb128> didrocks, yes
[11:44] <seb128> didrocks, http://ubuntuone.com/3X3SNx74hOelkX9J5kuZDE
[11:44] <seb128> ups
[11:44] <seb128> didrocks, http://<IP_ADDRESS>/job/landing-001-1-build/1/
[11:44] <seb128> "/tmp/hudson1182320129477473757.sh: line 5: cd: /var/lib/jenkins/silos/landing-001: No such file or directory"
[11:44] <seb128> didrocks, :-(
[11:44] <didrocks> seb128: yeah, I didn't assign you the silo yet
[11:45] <didrocks> and the firewall for rsync isn't opened by IS
[11:45] <didrocks> (as the IP changed)
[11:45] <didrocks> seb128: want me to attribute the silo so that you can build?
[11:45] <didrocks> or you want to add more components first?
[11:53] <didrocks> sil2100: in addition to seb128's right, you should be able to see the build button for deploy-jenkins
[11:54] <seb128> didrocks, let's attribute the silo, we can do another landing later
[11:56] <didrocks> ok :)
[11:56] <didrocks> launchpad authorization done
[11:56] <didrocks> let's attribute
[11:57] <didrocks> seb128: ok, you can try to run a build
[11:58] <didrocks> seb128: sil2100: I'm reverting to login.ubuntu instead of staging
[11:59] <sil2100> \o/
[12:00] <didrocks> sil2100: mind testing and so answering if the creds are fine?
[12:00]  * didrocks pushed his changes to prod
[12:00] <sil2100> didrocks: ok, so I'm logged in now and I had ubuntu-unity team in it
[12:00] <didrocks> sil2100: so, do you see the build button to the deploy-jenkibs job?
[12:01] <sil2100> didrocks: and I see build with parameters on landing-001-1-build
[12:01] <sil2100> didrocks: yes
[12:01] <didrocks> great!
[12:01] <sil2100> :)
[12:03] <didrocks> sil2100: can you try to reassign the second silo? would be a good exercise :)
[12:04] <didrocks> sil2100: only the jenkins job is needed, not the spreadsheet part
[12:04] <didrocks> asac: so, we're back on shape, I just rebuilt an instance and improved the install rules
[12:05] <didrocks> asac: just the status isn't synced back to the spreadsheet and we can't copy packages to distro until rsync from the new IP address is allowed
[12:05] <didrocks> asac: ev will work on that once he's back
[12:05] <seb128> didrocks, build running (sorry, was have lunch, I'm back now)
[12:05] <didrocks> seb128: let's look if it's starting fine
[12:05] <sil2100> didrocks: how can I do a reassign by using only jenkins? Which job to use?
[12:05] <seb128> didrocks, it is, it's installing packages
[12:06] <didrocks> seb128: sweet!
[12:06] <didrocks> sil2100: you have the link in the assign silo menu
[12:07]  * didrocks now praises that there is just one call to change to update all links :p
[12:07] <didrocks> seb128: great, uploaded to the ppa it seems
[12:08] <seb128> nice
[12:08] <didrocks> let's hope the gpg is rightly setup
[12:08] <didrocks> we'll see it soon :)
[12:08] <didrocks> seems it signed successfully at least
[12:08] <sil2100> didrocks: destination is Ubuntu archive, yes? ;)
[12:08] <didrocks> launchpadlib creds matches
[12:08] <didrocks> sil2100: yeah, so keep it empty
[12:09] <didrocks> seb128: https://launchpad.net/~ci-train-ppa-service/+archive/landing-001/+builds?build_state=building
[12:09] <sil2100> didrocks: reconfigure_silo set to landing-002 (just confirming if doing it irght)
[12:09] <didrocks> ok, now, I can work on what I planned at 10am :p
[12:09] <seb128> didrocks, great
[12:09] <didrocks> sil2100: you can try this ;) (it's a special case, as we don't really have a config file)
[12:09] <didrocks> sil2100: let's see ;)
[12:10] <didrocks> sil2100: if you don't set anything, it will take next available silo anyway
[12:10] <didrocks> which is landing-002 :p
[12:10] <sil2100> didrocks: oh noes... sil2100 is missing the Job/Build permission
[12:10] <sil2100> ;_;
[12:10] <didrocks> sil2100: hum… you checked ubuntu-unity, right?
[12:10] <didrocks> oh
[12:10] <didrocks> I redeployed all jobs
[12:10] <sil2100> Yes
[12:10] <didrocks> not that one
[12:10] <didrocks> uno momento
[12:11] <didrocks> sil2100: retry
[12:12] <sil2100> didrocks: yay, seems to work!
[12:12] <didrocks> great!
[12:12] <sil2100> Finished: SUCCESS
[12:12] <didrocks> sweet, all good then :)
[12:12] <asac> didrocks: ok thanks. i hope it takes not too long
[12:12] <sil2100> Assigned to landing-002
[12:12] <didrocks> asac: let's see…
[12:12] <sil2100> SO all is cool
[12:12] <didrocks> sil2100: thanks :)
[12:12] <didrocks> sil2100: back to landing -> did yu publish the keyboard?
[12:12] <sil2100> didrocks: thank *you* ;)
[12:13] <didrocks> (I don't see it in -changes)
[12:13] <sil2100> didrocks: yes, I pressed the button at least
[12:13] <didrocks> as I'll need that to update the seeds
[12:13] <didrocks> hum, and the artefacts were created?
[12:13] <sil2100> Let me check
[12:14] <didrocks> I have an idea what can happen
[12:14] <sil2100> http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Services/job/cu2d-services-head-3.0publish/127/console <- hum
[12:14] <sil2100> So not good...
[12:14] <didrocks> ok
[12:14] <didrocks> I guess the rsync on snakefruit doesn't happen
[12:14] <didrocks> as the script is set -e
[12:14] <didrocks> and now that the jenkins other node isn't reachable…
[12:16] <didrocks> sil2100: yeah, that was it, unblocked
[12:16] <didrocks> and added || true to first request
[12:16] <sil2100> didrocks: thanks ;)
[12:16] <didrocks> sil2100: yw! think about looking at -changes please :)
[12:16] <sil2100> didrocks: there is this as well -> https://code.launchpad.net/~sil2100/ubuntu-keyboard/some_packaging_changes/+merge/202654 (not top priority)
[12:17] <sil2100> didrocks: it's still not lintian-free, but well...
[12:17] <sil2100> didrocks: will do :)!
[12:17] <didrocks> sil2100: approved
[12:22] <didrocks> sil2100: I don't see hub and libcolumbus though
[12:48] <didrocks> seb128: hum, do you see deja-dup, wasn't it in g-c-c? (or visible in the dash)
[12:48] <didrocks> I may have remove the g-c-c plugin part, just checking
[12:49] <seb128> shrug
[12:49] <didrocks> hum, deja-dup binary package has the plugin normally
[12:49] <seb128> 3 person to ask the question this week :p
[12:49] <didrocks> ahah :)
[12:49] <seb128> didrocks, it's showing in unity-control-center and not gnome-control-center
[12:49] <seb128> mterry knows about it
[12:50] <seb128> (it's supposed to show in both)
[12:50] <seb128> we didn't switch defaults yet because everything didn't get transitionned for u-c-c
[12:50] <seb128> but that's ongoing work
[12:50] <didrocks> seb128: ok, as we are still shipping g-c-c by default… :p
[12:50] <didrocks> yeah
[12:50] <seb128> well, the intend was to have it in both
[12:50] <seb128> there is a bug, we discussed with mterry on monday
[12:50] <didrocks> I can see that as /usr/lib/x86_64-linux-gnu/control-center-1/panels/libdeja-dup.so
[12:50] <seb128> I guess he's going to fix it
[12:50] <didrocks> ok ;)
[12:51]  * didrocks install u-c-c
[12:51] <seb128> that's likely a key in the .desktop issue
[12:51] <seb128> you can run the standalone deja-dup UI otherwise
[12:51] <didrocks> probably, yeah
[12:51] <didrocks> I never know how to get the main panel
[12:51] <seb128> would give you an idea of how client side decoration don't work on Unity ;-)
[12:51] <didrocks> it's only restore or save
[12:52] <seb128> didrocks, run "deja-dup-preferences"?
[12:52] <didrocks> ah -preferences
[12:52] <didrocks> seb128: come on, there is a beautiful decoration there!
[12:53] <didrocks> invisible, but I'm sure, beautiful :)
[12:54] <seb128> ;-)
[13:33] <Laney> happyaron: are kylin doing some alpha 2 testing?
[14:04] <happyaron> Laney: I think they are mainly busy working on those third party cooperation projects
[14:21] <xnox> seb128: thanks for the new glade! so much better.
[14:22] <xnox> seb128: i'm however, loading ubiquity custom python widgets catalog, and it appears to be marking one of my widgets as "deprecated" (but no other), not sure why
[14:26] <seb128> xnox, yw!
[14:27] <seb128> I don't know about the deprecation either
[14:29] <Laney> happyaron: would be good to have some if there's to be a release
[14:45] <seb128> Laney, hum, would it make sense to override the fileselector setting in ubuntu-settings rather than in the gtk source?
[14:46] <Laney> hmm
[14:47] <seb128> Laney, that's where we moved the Ubuntu overrides for other sources, it makes easier for other flavors to make different decisions than us
[14:48] <seb128> to take*
[14:48] <seb128> on that note, I'm away for some exercice, be back in ~1h
[14:48] <Laney> I was thinking of it as a "gtk" choice rather than an "ubuntu desktop" one
[14:48] <Laney> don't really mind
[14:50] <seb128> Laney, that works for me, especially if we patch gtk2 we sort of enforce that as a gtk choice
[14:50] <seb128> or we would just give others the flexibility to make gtk2/3 softwares inconsistant
[15:02] <tedg> seb128, Looking at your comment: https://code.launchpad.net/~robert-ancell/indicator-power/ucc-only-in-unity/+merge/202559/comments/472287
[15:03] <tedg> seb128, What do you think we should be checking?  I thought we only wanted u-c-c for Unity so that GNOME could be "vanilla"?
[15:03] <mdeslaur> seb128: for some reason, I'm getting a race at boot with trusty where gnome-keyring doesn't end up as the ssh agent...have you seen that?
[15:03] <mdeslaur> about half the time
[15:10] <happyaron> Laney: I see, will check with our PM how to talk about it with them.
[15:10] <Laney> mdeslaur: I think it races with the upstart job
[15:10] <Laney> happyaron: cool, thanks
[15:11] <happyaron> :)
[15:14] <mdeslaur> Laney: hrm, ok, I'll file a bug. thanks
[15:35] <seb128> mdeslaur, what Laney said, and yes sometime the agent is not working for me either (wrong env, because if I run gnome-keyring-daemon and export the env it prints things works)
[15:36] <mdeslaur> seb128: I filed 1271591
[15:36] <seb128> tedg, right, GNOME doesn't use indicators (there is no way to use them under gnome-shell and the UI wouldn't fit the shell anyway)
[15:37] <tedg> seb128, So what's the issue of checking for the Unity desktop?
[15:37] <seb128> tedg, GNOME is going to be vanilla by not using indicator and using g-c-c
[15:37] <seb128> tedg, xfce use indicators, gnome-panel session use indicators
[15:37] <tedg> I'm more worried about folks like Xubuntu
[15:38] <tedg> Don't they want g-c-c ?
[15:38] <seb128> tedg, did you see https://code.launchpad.net/~larsu/indicator-power/xfce-control-center/+merge/202641
[15:38] <seb128> tedg, I think those desktops want, in priority order, their-own-tool, u-c-c, g-c-c
[15:39] <tedg> seb128, Oh, okay, I thought they'd want g-c-c before u-c-c.
[15:39] <seb128> tedg, g-c-c is not going to include indicator settings, so better to call u-c-c which does
[15:39] <seb128> tedg, I'm also unsure that stuff like CSD is going to work well on those desktops
[15:39] <tedg> Seems weird that the behavior could change based on what is installed though.
[15:39] <seb128> tedg, I think they are closer from Unity than from shell
[15:40] <tedg> i.e. if you had Xubuntu and Ubuntu Desktop you'd get one, but not if you didn't.
[15:40] <seb128> you mean?
[15:40] <seb128> xfce would always have their own tool called
[15:40] <seb128> Ubuntu Desktop installed or not
[15:40] <tedg> I guess Xubuntu is a bad example as they have their own.  But just saying because we're checking for the existence of the utility, we could behave differently.
[15:41] <tedg> Seems we should decide and error.
[15:41] <seb128> I would be fine with that
[15:41] <seb128> I don't care enough to spend time on it though
[15:41] <seb128> if somebody files a bug or some other desktops have concerns they can file a bug/send a patch
[15:41] <tedg> Is there any reason an indicator would want to call g-c-c?
[15:42] <seb128> better than erroring out I guess?
[15:42] <seb128> but yeah, at this point g-c-c seems a random choice
[15:42] <seb128> we could as well call kdeconfig
[15:42] <tedg> Yeah
[15:42] <seb128> we should maybe just hide the entry if u-c-c is not installed
[15:43] <seb128> though having the g-c-c case makes it easier for e.g Debian to keep packaging indicators
[15:43] <seb128> or at least having them working as designed
[15:44] <tedg> It also makes the migration story easier.
[15:44] <seb128> tedg, I think we should claim the current code as good enough and not spend more effort on it until somebody comes with a valid concern/bug/reason to change
[15:44] <tedg> So my thought is: keep the patches like they are today.  But when we get to a stable point we can start dropping g-c-c.
[15:44] <seb128> +1
[15:45] <tedg> K, will review as such.
[15:45] <seb128> thanks
[15:47] <xnox> seb128: my custom do_draw() is borked. All it does is request the current split between pack1 & pack2 of a Gtk.Paned widget and updates labels appropriately with the split.
[15:47] <xnox> seb128: upon resizing, does Gtk.Paned emit any singnal that I can key on?
[15:48] <seb128> xnox, do you have code to share/a small testcase showing what you do/the issue?
[15:48] <xnox> seb128: yeah, one sec.
[16:04] <xnox> seb128: awwwwww!
[16:04] <seb128> xnox, works now or what?
[16:04] <xnox> seb128: so my do_draw() method ( a derived / subclassed Gtk.Paned)
[16:05] <xnox> seb128: did not have "Gtk.Paned.do_draw(self, cr)" as first thing
[16:05] <xnox> seb128: so nothing was drawn!
[16:05] <xnox> seb128: now it all works!
[16:05] <seb128> great!
[16:15] <xnox> seb128: do you know if I can increase the corner radius of the ShadowType.ETCHED_IN ?
[16:15] <xnox> of a Gtk.Frame
[16:16] <xnox> seb128: \o/ OMG, migrating away from HPaned to Paned, made that custom widget render in the new glade! #firstinhistory
[16:20] <seb128> haha
[16:20] <seb128> dunno for the corner
[16:20] <seb128> but larsu might
[16:20] <seb128> or Cimi
[16:21] <Cimi> xnox, it's static IIRC
[16:21] <xnox> Cimi: fair enough =) it looks miles better now, so it's all good.
[16:21] <Cimi> xnox, because at that time there were child windows and we couldn't play much with those
[16:21] <Laney> pix
[16:22] <xnox> Laney: we are not past UIF yet, are we?! =)
[16:23] <Laney> depends on whether you're going to give me chocolate / beer as a bribe :-)
[16:23] <seb128> what do I need to do to get chocolate / beer as well? ;-)
[16:26] <Laney> I'm after ui-toolkit in trusty with the listview emulator
[16:26] <Laney> will share my chocolate with you if you do that :P
[16:26] <seb128> hum
[16:26] <seb128> not sure I'm that hungry in fact :p
[16:26] <seb128> but it reminds me I wanted to test your autopilot fixes branch
[16:26]  * seb128 goes to do that
[16:26] <Laney> om nom nom
[16:26] <seb128> ;-)
[16:33] <xnox> Laney: sbuild-build-depends-ubiquity-dummy : Depends: gir1.2-webkit-3.0 but it is not going to be installed
[16:34] <xnox> Laney: how can I build a ubiquity update?! =)
[16:34] <Laney> there's skew atm
[16:34] <seb128> you might want to delete the proposed version
[16:34] <seb128> to unblock ubiquity
[16:34] <Laney> do it
[16:34] <seb128> where is my chocolate? ;-)
[16:35] <Laney> xnox has it
[16:35] <Laney> it's posh belgian stuff
[16:36] <ogra_> i thought she is english
[16:36] <xnox> Laney: i'm still pondering about going to Fosdem to replenish my backup stores.
[16:36] <xnox> ogra_: posh - adj, not Posh - name.
[16:36] <Laney> neat, see you there
[16:36] <ogra_> :)
[16:36] <Laney> everyone's going
[16:37] <xnox> Laney: hm. I have a volleyball match on sunday =/
[16:37] <xnox> Laney: yeah, FTBFS on i386 is not good =)
[16:37] <Laney> heh
[16:37] <Laney> trying to get a ppc fix before uploading
[16:38] <Laney> speaking of which
[16:38] <Laney> collect2: error: ld terminated with signal 9 [Killed]
[16:41] <seb128> Laney, xnox: deleted from proposed, that should unblock other things until Laney uploads a version that builds
[16:41] <Laney> ta
[16:41] <xnox> seb128: thanks!
[16:41] <seb128> yw!
[17:17] <Laney> aha, I think it got past the failing stage
[17:23] <Laney> yup
[18:26] <seb128> sil2100, hey, can you give me a landing slot for ubuntu-system-settings? (l10 on the CI train list)
[18:29] <sil2100> seb128: sure! (I think ;p) Let me take a look, will be my first real time
[18:32] <sil2100> seb128: hmmm
[18:33] <sil2100> seb128: there seems to be a problem, as the previous request still didn't get cleaned up
[18:33] <sil2100> seb128: landing from l7 is still in state 'Cleaning silo', and it's blocking further ubuntu-system-settings landings
[18:33] <sil2100> didrocks: ^
[18:34] <seb128> sil2100, try again, it just finished cleaning it ;-)
[18:34] <sil2100> didrocks: how long does it usually take to clean up a silo ?
[18:34] <sil2100> Ah!
[18:34] <sil2100> Ok ;)
[18:34] <sil2100> didrocks: nevermind!
[18:34] <seb128> didrocks, sil2100: btw I saw it was still running, but that was making a good test of that scenario
[18:34] <seb128> sil2100, http://<IP_ADDRESS>/job/landing-001-3-merge-clean/1/console
[18:34] <sil2100> \o/
[18:34] <seb128> sil2100,  seems like the ppa took ~10 min from the delete request to be empty
[18:36] <sil2100> seb128: indeed - ok, assigning silo now
[18:36] <seb128> sil2100, thanks
[18:37] <sil2100> hmmm
[18:38] <sil2100> didrocks, seb128: I'm trying to press the 'Submit' button to assign a silo, but it does not work sadly?
[18:38] <didrocks> sil2100: hum
[18:38] <didrocks> sil2100: the job or the spreadsheet?
[18:39] <sil2100> didrocks: on the spreadsheet
[18:39] <didrocks> have you set the silo naming?
[18:39] <sil2100> didrocks: the jenkins job was ok, but now when I selected the silo it doesn't work
[18:39] <sil2100> I set landing-001 there
[18:39] <didrocks> which silo was assigned?
[18:39] <didrocks> ok
[18:40] <didrocks> sil2100: worked here
[18:40] <sil2100> didrocks: does it have some permissions on submit, or would the script not start even if I wouldn't have the permissions?
[18:41] <didrocks> sil2100: not sure, we need to look together, you should have all needed permissions
[18:42] <sil2100> didrocks: let's look at it tomorrow, not to waste your time anymore for today :)
[18:43] <didrocks> yeah, finishing a hangout and done
[18:43] <jasoncwarner> hey seb128 or laney (or anyone). I seem to have a broken package on upgrade. gyp? anyone know anything about that? seems to be broken for a few days now.
[18:43] <seb128> not know no, which one?
[18:43] <seb128> "gyp" is that the name?
[18:44] <jasoncwarner> seb128: yeah.
[18:44] <seb128> https://bugs.launchpad.net/ubuntu/+source/gyp/+bug/1246730 ?
[18:44] <ubot2`> Launchpad bug 1246730 in gyp (Ubuntu) "dependency_links.txt.dpkg-new': No such file or directory" [Undecided,Confirmed]
[18:45] <jasoncwarner> seb128: that's teh one
[18:45] <seb128> hum
[18:45] <seb128> that's a build tool from the chromium stack it seems, first time I read about it
[18:46] <seb128> qengho, ^ do you know about that source or bug?
[18:46] <qengho> Generate your Project.  Yes, I know of it.
[18:46] <seb128> jasoncwarner, you are building your own chromium packages then? ;-)
[18:46] <jasoncwarner> seb128: didn't think I was ;)
[18:46] <jasoncwarner> seb128: though, I might have installed something along the way. perhaps I have a ppa (checking)
[18:47] <seb128> jasoncwarner, you can probably safely uninstall that package then, still a bug that should be fixed though ... but an universe one
[18:47] <qengho> jasoncwarner, seb128, I don't think we got it from chromium, though.  Even an old one.
[18:47] <seb128> qengho, I'm just saying that because it has "maintainer: Debian Chromium Maintainers"
[18:48] <jasoncwarner> ah, it seems it is probably nodejs
[18:48] <jasoncwarner> when I go to uninstall it, all my node modules get uninstalled
[18:48] <seb128> oh, ok
[18:48] <qengho> seb128: I think GYP is one of those projects that was split off to be standalone, but few other projects took it up.
[18:48] <seb128> seems so
[18:48] <qengho> Nodejs isn't small, though.  That's nice.
[18:52] <jasoncwarner> I removed nodejs for now. not like I have time to work on that project anyway atm ;)
[20:07] <robert_ancell> tedg, are you OK with https://code.launchpad.net/~robert-ancell/indicator-power/ucc-only-in-unity/+merge/202559 being rejected? It means indicator-power runs u-c-c if it is installed, where the other indicators only do that if in Unity. I don't think it's a problem in practise but just inconsistent with the changes you requested
[20:08] <robert_ancell> seb128, ^ if still online
[20:08] <tedg> robert_ancell, Yeah, so seb128 and I had a conversation about it.  Long term we're just not going to call g-c-c at all.
[20:08] <robert_ancell> yep
[20:08] <tedg> robert_ancell, But for the migration and everything else, we're being simple.
[20:08] <tedg> i.e. not worth another round of back-and-forth
[20:08] <seb128> robert_ancell, hey
[20:08] <robert_ancell> ack
[20:09] <seb128> robert_ancell, do you look at the commit I pointed?
[20:09] <robert_ancell> yes
[20:12] <seb128> what's wrong with it?
[20:13] <seb128> robert_ancell, what do you want changed compared to the code that got commited?
[20:14] <robert_ancell> seb128, all the indicators have a g_strcmp0 (g_getenv ("XDG_CURRENT_DESKTOP"), "Unity") == 0 (on tedgs request) except for indicator-power
[20:14] <robert_ancell> but it's not that important
[20:14] <robert_ancell> so running the indicators say from lxde will bring up g-c-c for everything except indicator-power which will bring up u-c-c
[20:14] <seb128> robert_ancell, right, that's from the time where GNOME was gnome-panel and using indicators, I don't think that makes sense anymore with GNOME = gnome-shell and not using indicators
[20:15] <robert_ancell> yeah, it all goes away if we don't support g-c-c anymore
[20:15] <seb128> robert_ancell, I would argue that other indicators should favor u-c-c over g-c-c as well (that's basically what I did today for -power and why we landed that code)
[20:15] <seb128> g-c-c doesn't have indicator options to start with
[20:15] <robert_ancell> that was my original branches :)
[20:16] <seb128> you were right then ;-)
[20:16] <seb128> we just didn't have discussions about the topic before
[20:16] <seb128> and reviews are probably not the best venue to decide on such changes
[20:17] <robert_ancell> anyways, when do these new versions hit the archive?
[20:18] <robert_ancell> tedg, you can treat utf-8 as ASCII. Since all multibyte characters have the first bit set to 1 you will never get a valid ascii character in a multibyte sequence
[20:18] <robert_ancell> utf-8 is surprisingly clever
[20:18] <seb128> robert_ancell, I'm going to do a landing ask tomorrow, I already talked to didrocks about it todauy
[20:18] <tedg> Ha, I didn't realize.
[20:21] <seb128> robert_ancell, btw, for some reason the unity/compiz keybinding are not showing in the keyboard section of u-c-c, do we need to make compiz install its .xml in a new location?
[20:21] <seb128> e.g the hud key is not there
[20:21] <seb128> but other sections are missing as well
[20:21] <robert_ancell> seb128, oh, I hadn't noticed that
[20:21] <robert_ancell> is there a bug open?
[20:22] <seb128> robert_ancell, no, I just noticed today, I can open one if you want
[20:22] <robert_ancell> please do
[20:22] <robert_ancell> yeah, looks like it needs to
[20:22] <robert_ancell> /usr/share/gnome-control-center/keybindings - move/copy to /usr/share/unity-control-center/keybindings
[20:23] <seb128> shrug
[20:24] <seb128> robert_ancell, I don't know why you insist on migrating those locations ;-)
[20:24] <seb128> robert_ancell, https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1271710
[20:24] <ubot2`> Launchpad bug 1271710 in unity-control-center (Ubuntu) "doesn't list compiz/unity keybindings" [Undecided,New]
[20:24] <robert_ancell> seb128, because we're not g-c-c anymore and who knows what changes will come in new versions of g-c-c
[20:25] <seb128> robert_ancell, we are going to need landing of compiz and unity to complete that migration then, let's see how many weeks that takes
[20:25] <seb128> :/
[20:25] <robert_ancell> we need to sort that out
[20:25] <robert_ancell> our velocity has got even slower
[20:26] <seb128> indeed
[20:26] <seb128> well, the landing team is really focussed on touch
[20:26] <robert_ancell> seb128, did you see I uploaded that nautilus patch
[20:26] <seb128> yes
[20:26] <seb128> thanks for that
[20:26] <seb128> did you code review it or just went "oh, it builds, it seems to work, let's upload"?
[20:27] <robert_ancell> I reviewed it, but not in depth. It seems independent enough that we can maintain it into newer versions
[20:27] <seb128> I was sort of going to do that and figured out I would try to ping you in case you had the motivation to do a proper review ;-)
[20:27] <seb128> we already received a bug report about it btw
[20:27] <robert_ancell> it does logical stuff
[20:27] <seb128> the guy who wrote the patch is going to look at it
[20:27] <robert_ancell> yeah, he seems onto it
[20:28] <seb128> Sweetshark, https://launchpadlibrarian.net/163120675/buildlog_ubuntu-trusty-powerpc.libreoffice_1%3A4.2.0~rc2-0ubuntu1_FAILEDTOBUILD.txt.gzhttps://launchpadlibrarian.net/163120675/buildlog_ubuntu-trusty-powerpc.libreoffice_1%3A4.2.0~rc2-0ubuntu1_FAILEDTOBUILD.txt.gz :-(
[20:29] <seb128> shrug, sorry for the double copy, firefox was hanging while loading the page and I though it didn't get the copy
[20:29] <seb128> https://launchpadlibrarian.net/163120675/buildlog_ubuntu-trusty-powerpc.libreoffice_1%3A4.2.0~rc2-0ubuntu1_FAILEDTOBUILD.txt.gzhttps://launchpadlibrarian.net/163120675/buildlog_ubuntu-trusty-powerpc.libreoffice_1%3A4.2.0~rc2-0ubuntu1_FAILEDTOBUILD.txt.gz
[20:29] <seb128> https://launchpadlibrarian.net/163120675/buildlog_ubuntu-trusty-powerpc.libreoffice_1%3A4.2.0~rc2-0ubuntu1_FAILEDTOBUILD.txt.gz
[20:29] <seb128> (grrrr)
[20:29] <seb128> robert_ancell, you are going to be in London, right?
[20:29] <robert_ancell> seb128, yep
[20:29] <seb128> great
[20:30] <seb128> I hope we can finish those transitions there
[20:30] <seb128> robert_ancell, do you need help from me before that?
[20:30] <robert_ancell> seb128, just help to keep things moving
[20:30] <robert_ancell> i.e. annoying people until they take the changes / get them into the archive :)
[20:31] <robert_ancell> and finding any bugs
[20:31] <seb128> right, I'm on that already
[20:31] <seb128> how is u-s-s going?
[20:31] <seb128> btw, are you bored/looking for things to do? ;-)
[20:33] <robert_ancell> ha, I wish
[20:33] <seb128> :-(
[20:33] <robert_ancell> I'm leaving u-s-s until u-c-c is out of the way
[20:33] <robert_ancell> Don't want to land both at once
[20:33] <seb128> you are still fulltime on u-c-c?
[20:33]  * seb128 has work for you :p
[20:34]  * robert_ancell hides
[20:34] <robert_ancell> doing lightdm stuff and general fixing
[20:34] <robert_ancell> sure, propose it to me
[20:34] <robert_ancell> I want to hear a great sell
[20:34] <seb128> robert_ancell, joke aside I think most of our changes for the LTS are going to be done after u-c-c/u-s-d
[20:35] <seb128> robert_ancell, it's an old sell, but I think you did some work on gnome-screensaver some cycles ago to give it an unity-greeter like UI (or at least a less-win-95-like-UI)
[20:35] <seb128> do you still have that somewhere?
[20:35] <robert_ancell> yeah, somewhere
[20:35] <robert_ancell> I can do some work there
[20:36] <robert_ancell> it will be hacky, but I guess it's better than nothing
[20:37] <seb128> how much work would it be to bring it back? ;-)
[20:37] <seb128> that would be nice
[20:37] <seb128> thanks
[20:38] <seb128> yeah
[20:38] <seb128> in fact I don't even care much if it's the same as the login screen (that would be nice though)
[20:38] <robert_ancell> seb128, do you know if it needs to be conditional on running in Unity, i.e. is anyone else still using gnome-screensaver?
[20:38] <seb128> but at least something which is not that grey rectangle
[20:38] <seb128> I wouldn't bother
[20:39] <robert_ancell> we'll see if anyone shouts
[20:39] <seb128> gnome-shell doesn't use gnome-screensaver
[20:39] <seb128> and xfce went for light-locker
[20:39] <seb128> yeah
[20:39] <seb128> if anyone complains we can rename "fork" gnome-screensaver as well :p
[20:39] <seb128> that one would be an easy rename
[21:17] <TheMuso> pitti: Fair enough, thanks again.
[21:58] <seb128> shrug, why is dch setting my distro serie to "the"?!
[21:58] <kenvandine> seb128, cool... "the"
[21:58] <kenvandine> it starts with a T
[21:58] <kenvandine> :-D
[21:58] <Laney> The next release
[21:59] <seb128> kenvandine, did you hack into my computer? ;-)
[21:59] <kenvandine> yup :)
[21:59] <seb128> damnit!
[21:59] <Laney> panel still uses gnome-screensaver
[21:59] <Laney> fallback
[21:59] <seb128> Laney, what greeter do they use?
[21:59] <Laney> and random people might, of course
[21:59] <seb128> well
[22:00] <seb128> the question is "would they be annoyed if the lock screen was looking unity-greeter like, rather than win95 like"
[22:00] <seb128> ?
[22:00] <Laney> I think it'd be good for it to look better
[22:00] <Laney> but "nobody other than us uses this" isn't a good metric to make decisions on
[22:00] <kenvandine> you know someone will complain
[22:00]  * Laney wouldn't mind
[22:00] <kenvandine> the only thing worse is xscreensave
[22:00] <kenvandine> +r
[22:01] <seb128> well, it's rather "is anyone attached to the current look"?
[22:01] <seb128> I would think not
[22:01] <seb128> but you never know
[22:01] <kenvandine> fork it!
[22:01]  * kenvandine ducks
[22:01] <seb128> lol
[22:01] <Laney> heh
[22:01] <seb128> kenvandine, read the backlog, I suggested it ;o
[22:01] <Laney> I'd change it and then see who complains
[22:01] <seb128> right
[22:01] <kenvandine> feeling a little punchy after a couple hours debugging the keyboard
[22:01] <kenvandine> ha... you did :)
[22:01] <seb128> that's what are going to do I think
[22:01] <Laney> I doubt a fork is required as it'd probably be easy to have both looks if necessary
[22:02] <seb128> well, fork might be better than a stack of if statements in the code
[22:02] <Laney> shrug
[22:02] <seb128> but let's see if anyone complains first
[22:02] <seb128> well, first let's refresh the UI
[22:02] <seb128> then let's see if anyone complains
[22:03] <seb128> if they do, then let's decide on what to do ;-)
[22:03] <seb128> soooo
[22:03] <seb128> where is dch getting the current distro serie from?
[22:03] <seb128> is anyone else getting "the" on "dch -r"?
[22:03] <seb128> kenvandine, WHAT DID YOU DO
[22:04]  * kenvandine tries
[22:04] <Laney> there's a mode where it copies the previous one
[22:04] <kenvandine> nope... i'm getting trusty
[22:04] <seb128> I'm not using any mode
[22:04] <seb128> or said differently, I've no custom config
[22:04] <seb128> shrug
[22:05] <Laney> well... is it getting it from the previous entry?
[22:05] <seb128> I doubt it, just got that on 6 different sources
[22:06] <Laney> otherwise I think it gets it from distro-info
[22:06] <Laney> ubuntu-distro-info --devel --codename
[22:07] <seb128> $ distro-info --devel --codename
[22:07] <seb128> trusty
[22:07] <Laney> outta ideas
[22:08] <seb128> shrug
[22:08] <Laney> now you get to use the source :P
[22:08] <seb128> so in fact my issue is
[22:08] <seb128> $ dch -i "Rebuild for the new poppler soname"
[22:08] <seb128> $ dch -r
[22:08] <seb128> it has to do with the dch -i message
[22:08] <seb128> wth?
[22:09] <seb128> if I "dch -i "Rebuild"" it works
[22:09] <Laney> oh yeah, I see that
[22:09] <Laney> that's funny
[22:09] <Laney> I always do dch -D trusty -r "" so I'd never see that
[22:10] <seb128> I usually do it in those steps for the vcs commits
[22:10] <seb128> you get the commit with the change
[22:10] <seb128> then the release one
[22:11] <seb128> but wth is wrong with that changelog entry?
[22:12] <Laney> bug
[22:12] <Laney> debug it!
[22:13] <seb128> :-(
[22:13] <seb128> that doesn't seem like the sort of bug I'm wanting to debug
[22:13] <seb128> that seems like a bug infinity would enjoy :p
[22:13] <seb128> or slangasek
[22:15] <seb128> ok, let me open a bug and assign it to kenvandine
[22:16] <seb128> he mentioned earlier that he has something to do with that issue
[22:16] <seb128> ;-)
[22:16] <seb128> kenvandine, debugging dch should be good for you, that's going to be a change of all the touch work
[22:17] <seb128> of->from
[22:38] <Sweetshark> seb128: *urgh*
[22:38] <seb128> Sweetshark, indeed... :/
[22:39] <seb128> cyphermox, hey, did you see https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197854 ?
[22:39] <ubot2`> Launchpad bug 1197854 in network-manager (Ubuntu) "NetworkManager crashed with SIGABRT in g_assertion_message()" [High,Confirmed]
[22:39] <cyphermox> I did
[22:39] <seb128> ok, you never commented/acted on it, so I'm checking
[22:39] <cyphermox> yeah
[22:39] <cyphermox> I think it's already been applied though
[22:39] <seb128> it seems a simple commit, can we get it in trusty?
[22:39] <cyphermox> yeah
[22:40] <seb128> thanks
[22:40] <cyphermox> we'll get it via <IP_ADDRESS> on friday though
[22:40] <cyphermox> I'm updating NM and MM
[22:40] <seb128> ok, good
[22:41] <seb128> (you are right, looking to the current source it seems the source has it)
[22:43] <Sweetshark> seb128: so the good thing is that it is a casting error in a function called 'convertLittleEndian', so a/ it will likely only fail on PPC and b/ its at least a decent hint of what is going wrong (unlike e.g. stumbling over itself somehow) ...
[22:52] <seb128> Sweetshark, "good" I guess, still not debugging/work/another upload :/
[22:54] <Sweetshark> seb128: yup
[22:54] <seb128> not->need
[22:55] <Sweetshark> seb128: git blame suggests I might was just out at a bar with the guy who broke it ;)
[22:55] <seb128> Sweetshark, well, the good news is that the l10n package built :-)
[22:55] <seb128> haha
[22:56] <seb128> you just missed an opportunity to bribe him in fixing it then!
[22:59] <seb128> on that note, enough for today, night everyone


 I need to go to the local Comcast office to play it back for the manager on duty. I listened to the recording and there was a lengthy discussion where I brought up that point and she even put me on hold to confirm.
 I record all calls on my mobile phone unless I specifically have a phone number tagged as "Friend", "Family", "Work" and "Personal"


 farbod: use the magic word
[05:54] <bazhang> sudo ?
[05:55] <rww> http://www.roguescast.com/wp-content/uploads/2014/02/youmadethisImadethis.jpg
[05:56] <bazhang> bwahahaha
[05:59] <rww> lol, ValicekB has been cycling in and out of ##fix_your_connection for a week or more now i think
 Do parentheses work in grep
[07:14] <bazhang> cross compiler for ubuntu and android on arm?
[07:14] <bazhang> isnt that just gcc?
 how to create a botnet <TeamKorea> this is a hacking zone for anonymous
[07:43] <bazhang> lordie
[08:31] <Pricey> rww: Looks like a kettle.
[12:16] <DJones> I wonder whether its worth adding something along the lines of "Ubuntu 14.04 is due to be offered as an upgrade from 12.04 once 14.04.1 is released (which is due on 24th July 2014)" to the end of !12.04
[12:17] <philinux> hello,  #ubuntu+1 seems to be invite only. i get Cannot join #ubuntu+1 (Channel is invite only).
[12:17] <philinux> is it offline until uu is annouced?
[12:18] <IdleOne> yes
[12:18] <DJones> philinux: The channel gets closed down once a new release is issued and then reopened when the next release starts being worked on
[12:18] <philinux> DJones;~ cant remember that as i auto connect from xchat. never seen that message before
[12:19] <IdleOne> We had left it open last release which is probably why you didn't remember
[12:19] <IdleOne> anyway should be any day now
[12:20] <philinux> IdleOne;~ thanks , though i was going bonkers for a minute
[12:20] <IdleOne> oh, you probably are, but not about this :)
[12:20] <jussi> :D
[12:21] <philinux> indeed, cheers
[12:21] <philinux> bye for now
[12:21] <IdleOne> have a good day
[12:23] <DJones> Wonder when unified unicorn is due to be announced anyway
[12:23] <IdleOne> usually is by now
[12:23] <IdleOne> sabdfl must be on vacation.
[12:24] <IdleOne> maybe he'll decide to skip U and go to Warty Warthog 2
[12:26] <IdleOne> I assume he he going to completely ignore Ubuntu Varicose Veins
[12:26] <IdleOne> s/he he/he is/
[12:27] <DJones> I quite like uppity ubuntu
[13:29] <phunyguy> Baahahaa @ Varicose Veins
[13:29] <phunyguy> that's hilarious
[19:41] <Jordan_U> Why was !anyone removed again?
[23:37] <elky> Jordan_U: because people were using it based on if the word "anyone" was ever mentioned in any context ever
[23:38] <Jordan_U> :(
[23:39] <Jordan_U> I made a lot of (I believe good) use of that factoid while it existed. Interestingly, most of the comments I used it in reply to didn't actually contain the word "anyone".
[23:40] <knome> !details | Jordan_U?
[23:43] <rww> DJones: I agree that we need such a factoid, people keep asking about it. phunyguy was thinking the same iirc
[23:43] <rww> DJones: was gonna make a new one for it tho
[23:43] <Jordan_U> knome: The real problem is that they haven't actually asked any support question, though I guess telling them that their question isn't detailed enough for us to help them somewhat makes that point.
[23:44] <knome> what about just asking "what's up?"
[23:44] <rww> ^
[23:46] <rww> k1l: AP--'s a repeat problem, in case you didn't notice already.
[23:46] <rww> best keep that one set a while
[23:46] <k1l> yeah, i was just going through the bantracker and logs to make sure
[23:47] <IdleOne> set @duration 10000d and forget