[00:18] <poolie> hi all
[00:31]  * slangasek waves to poolie
[00:32] <poolie> hey
[00:32] <slangasek> does anyone here know why the openldap import is failing? the error message looks pretty wrong, openldap didn't exist in Debian woody. http://package-import.ubuntu.com/status/openldap.html#2011-06-15%2000:44:51.442540
[00:32] <slangasek> (and that version number never existed for the openldap package)
[00:32] <poolie> !
[00:32] <slangasek> well, actually, I guess openldap *might* have existed in woody... but it was a completely different package back then, *before* it was renamed to openldap2 :)
[00:33] <poolie> perhaps that's connected to the '2' epoch
[00:33] <poolie> i need to reboot and perhaps debug something weird here, biab
[00:33] <poolie> let's file a bug first
[00:34]  * slangasek files
[00:34]  * fullermd questions the meaningfulness of the microseconds term   :p
[00:35] <poolie> patches welcome :)
[00:36] <fullermd> I've been looking for the proper place to submit patches to physics for _years_!
[00:38] <slangasek> poolie: bug #877827 filed
[06:34] <vila> hi all :)
[06:35] <vila> poolie: ping
[06:35] <poolie> hi vila
[06:35] <vila> poolie: I pushed the importer too much ? :)
[06:36] <poolie> how's it going?
[06:36] <poolie> i think that trying to catch up with Precise opening made it too excited
[06:36] <vila> hehe
[06:37] <vila> that was me, I progressively raised max_threads to 24 and it was going well for several hours
[06:37] <vila> looks like it's at 2 right now
[06:37] <poolie> yes
[06:37] <vila> I'll have to look at the logs
[06:37] <vila> I'll put it back to its regular 8 now
[06:37] <poolie> mm. if you want to
[06:37] <poolie> please don't
[06:38] <vila> why ?
[06:38] <vila> (just reverted it to 2)
[06:38] <poolie> why did you think you should?
[06:39] <vila> to catch up the ~18.000 pending imports faster
[06:39] <poolie> it's an operational issue for lp so we shouldn't put it back up until we can do so without slamming them
[06:39] <vila> oh, we did ?
[06:39] <poolie> yes, i replied in gz's mail thread
[06:40] <vila> oh, I should read that then
[06:40] <poolie> oh i thought you had
[06:41] <psycose> Hi I got the following error while using bzr https+urllib://......    bzr: ERROR: wanted 1433 bytes but next hunk only contains 848: 'gcb1z\n1417\n2632\nx\x9c\xcdV'    I did bzr check and bzr pack on all side, any tips ? thanks       Repository tree (format: 2a)
[06:41] <poolie> psycose: my guess would be there is a proxy interfering with traffic
[06:42] <poolie> though that seems a bit unlikely for https
[06:42] <AuroraBorealis> oh god that error sounds terrible
[06:44] <vila> poolie: I replied to the thread
[06:45] <psycose> As it seems to be an application level error, it does not seems to come from the HTTP server, if ever you have any tips for me to investigate, the server and the client are on the same computer.
[06:51] <poolie> !
[06:51] <poolie> what's the server software?
[07:51] <mgz> morning all.
[07:59] <poolie> hi mgz
[08:02] <vila> mgz: hey !
[08:24] <marcamilly> trying to install bazaar on os x lion
[08:24] <marcamilly> got the dog from the canonical site
[08:24] <marcamilly> *dmg i mean
[08:24] <marcamilly> installed it
[08:25] <marcamilly> but when I go to terminal, bzr returns 'command not found'
[08:25] <AuroraBorealis> are you on lion
[08:25] <marcamilly> yep
[08:25] <marcamilly> i did set Python to 2.6
[08:25] <AuroraBorealis> have to do something
[08:25] <AuroraBorealis> that worked for me
[08:25] <marcamilly> what else do I have to do?
[08:25] <marcamilly> do I do that after the install?
[08:25] <AuroraBorealis> yeah
[08:25] <AuroraBorealis> thats what i did and then it worked
[08:25] <marcamilly> nope
[08:25] <marcamilly> just did it again
[08:25] <marcamilly> still doesn't work
[08:26] <AuroraBorealis> is it bash saying that the command isn't found?
[08:26] <marcamilly> yes
[08:26] <AuroraBorealis> did you open a new terminal?
[08:26] <marcamilly> -bash: bzr: command not found
[08:26] <marcamilly> yep
[08:26] <marcamilly> closed terminal altogether
[08:26] <marcamilly> and re-opened it
[08:26] <AuroraBorealis> not sure why its not working then since it worked for me
[08:26] <marcamilly> maybe restart machine?
[08:26] <marcamilly> but that's sooooo windows
[08:27] <vila> mgz: did you see http://www.themacaque.com/?p=954 ?
[08:28] <AuroraBorealis> you can try, but it should of installed it to your path...
[08:28] <AuroraBorealis> not sure why its not working for you
[08:28] <AuroraBorealis> or you did the python 2.6 thing wrong
[08:29] <marcamilly> k, lemme try restarting
[08:29] <marcamilly> before doing anything more drastic
[08:29] <marcamilly> like installing the 'Test' version
[08:30] <AuroraBorealis> that dmg really needs to be updated =/
[08:40] <mgz> vila: they don't actually say what the problem is in that post
[08:41] <vila> mgz: wrong encoding ?
[08:42] <mgz> but not having access to the environment block in unicode does break people who want to languages other than their system install
[08:42] <mgz> their test would work on my box downstairs, because it would return CP932 that could then be correctly decoded
[08:46] <vila> mgz: I didn't look to closely, but we rely on expanduser here and there and I thought you will be interested
[08:46] <mgz> so, his question about whether it's fixed in Python 3 is funny
[08:46] <mgz> the environment is unicode already in Python 3.
[08:47] <mgz> vila: it's interesting.
[08:48] <marcamilly> still no dice
[08:48] <marcamilly> even after reset!
[08:48] <mgz> but an edge case, most spanish users don't give themselves japanese user names
[08:50] <vila> mgz: yup, let's handle the rare case befor the hairy one ;)
[08:51] <mgz> vila, do you know anything about installing on osx for marcamilly?
[08:51] <vila> hmm, not for a long time and never on lion, but let see
[08:51] <vila> marcamilly: what's your PATH ?
[08:52] <AuroraBorealis> there is an issue on lion
[08:52] <marcamilly> how do I see that at the command line?
[08:52] <AuroraBorealis> because it doesn't adapt for the fact that python2.7 is default
[08:52] <vila> env | grep PATH
[08:53] <vila> that's because noone with a lion setup has stepped up to build the installer :)
[08:54] <marcamilly> my PATH: https://gist.github.com/1297769
[08:54] <vila> it's pretty easy once you installed the dev dependencies
[08:55] <vila> marcamilly: can you check that bzr is in /usr/local/bin ?
[08:57] <marcamilly> how do I do that?
[08:58] <marcamilly> just tried cd-ing to that folder, but it wouldn't allow me
[08:58] <vila> ls -l /usr/local/bin/bzr
[08:58] <marcamilly> permission denied
[08:58] <vila> o.0
[08:58] <marcamilly> ls: /usr/local/bin/bzr: Permission denied
[08:58] <vila> ls -l /usr/local/
[09:00] <marcamilly> k got that, sec
[09:00] <marcamilly> https://gist.github.com/1297769
[09:01] <AuroraBorealis> seems bzr didn't install or something o.o
[09:02] <vila> marcamilly: ugly, '502' seems to be an unknown user and you miss 'x' there anyway
[09:02] <vila> marcamilly: which means you cannot read the directory content
[09:02] <marcamilly> yeh
[09:02] <marcamilly> so how do I change it?
[09:02] <vila> marcamilly: are you an admin on this machine ?
[09:03] <marcamilly> yep
[09:03] <vila> then 'sudo bash' and 'cd /usr/local/bin/
[09:03] <vila> '
[09:04] <vila> marcamilly: be aware that you get root powers once you 'sudo bash' and that you can destroy stuff (just mentioning in case)
[09:06] <marcamilly> lol
[09:06] <marcamilly> k
[09:07] <marcamilly> ok i see bzr
[09:07] <marcamilly> in /usr/local/bin
[09:07] <vila> marcamilly: any idea about who '502' is ?
[09:07] <marcamilly> nope
[09:07] <marcamilly> how do I find out?
[09:07] <marcamilly> and how do I replace it, if it's not 'legit'?
[09:07] <marcamilly> could it be a Lion role/user?
[09:08] <vila> well, that's the issue, a number is used because it's not known :)
[09:08] <vila> did you upgrade from a previous osx release ?
[09:09] <AuroraBorealis> would the lion upgrade really screw things up that badly?
[09:09] <marcamilly> yeh i did
[09:09] <marcamilly> from Snowleopard
[09:09] <vila> well, if a user of a previous release did the install and wasn't migrated to lion...
[09:09] <vila> then its id is hanging around
[09:09] <marcamilly> but i didn't have 'many' users
[09:10] <marcamilly> actually, just had one
[09:10] <marcamilly> the main one
[09:10] <marcamilly> and MAYBE guest
[09:10] <vila> iirc, osx starts at 500 and increment so we're talking about the third created user but that also takes deleted users into account
[09:10] <vila> anyway, is there something else than bzr in /uzr/loca/bin ?
[09:11] <marcamilly> yah, lots of other stuff
[09:11] <marcamilly> coda, compare, Magick++-config
[09:11] <marcamilly> dot display djpeg diggimg
[09:11] <marcamilly> and lots of others
[09:12] <marcamilly> how should I proceed?
[09:12] <vila> meh, given the path you pasted, I was expecting to find those in /opt/local/bin instead
[09:12] <vila> so, that rules out deleting bin and reinstalling, let
[09:12] <vila> 's try a more delicate fix then
[09:13] <vila> in /usr/local do:
[09:13] <vila> chown -R root:wheel bin
[09:14] <marcamilly> LOL
[09:14] <marcamilly> come out of sudo bash?
[09:14] <vila> nope
[09:14] <marcamilly> k
[09:14] <vila> you need to be root to CHange OWNer
[09:15] <marcamilly> done
[09:15] <marcamilly> drwxr--r--  61 root       wheel  2074 Oct 19 03:11 bin
[09:15] <vila> chmod -R go+x bin
[09:15] <marcamilly> what's 'wheel' though?
[09:15] <marcamilly> which folder should I be in?
[09:16] <marcamilly> or can I run that command from anywhere?
[09:16] <vila> /usr/local
[09:16] <marcamilly> done
[09:16] <vila> let's backtrack then
[09:17] <vila> in a new terminal (keep the sudo's one around): ls -l /usr/local/bin/bzr
[09:17] <marcamilly> -rwxr-xr-x  1 root  wheel  5439 Sep 13 17:45 /usr/local/bin/bzr
[09:17] <marcamilly> great
[09:17] <marcamilly> seems to work
[09:17] <marcamilly> great
[09:17] <marcamilly> bzr version works
[09:17] <marcamilly> finally!
[09:17] <marcamilly> thnx
[09:17] <marcamilly> do I need to do anything else?
[09:18] <vila> probably add /usr/local/bin to your path, how did you run 'bzr version' ? With the full path ?
[09:18] <marcamilly> no
[09:18] <marcamilly> just bar version
[09:18] <marcamilly> *bzr
[09:18] <marcamilly> 'bzr version'
[09:19] <marcamilly> so it seems to have been added to my path
[09:19] <vila> oh ! Missed /usr/loca/bin in your paste, you already have it
[09:19] <vila> should be fine then
[09:19] <marcamilly> hrmm
[09:19] <marcamilly> kk
[09:19] <marcamilly> thanks much
[09:19] <marcamilly> btw, what's 'wheel'?
[09:19] <marcamilly> admin user
[09:19] <AuroraBorealis> he probably just saved you from some serious headaches
[09:19] <marcamilly> ?
[09:19] <AuroraBorealis> its the group for "sudo"
[09:19] <marcamilly> nah I am pretty sure he did
[09:19] <marcamilly> thnx much meng
[09:19] <marcamilly> you were pleasant too
[09:19] <marcamilly> :)
[09:20] <marcamilly> rare combo in these here relay chatts
[09:20] <vila> wheel is some king of group for admining, I never bother searching the details ;)
[09:20] <marcamilly> hehehe
[09:20] <marcamilly> kk
[09:20] <marcamilly> well this is fine
[09:20] <marcamilly> i really appreciate it
[09:20] <vila> err kind not king (it's an interesting freudian lisp though ;)
[09:20] <vila> lips
[09:20] <vila> lol
[09:20] <AuroraBorealis> The wheel group is a group which limits the number of people who are able to su to root. This usually consists of a group named “wheel” and a set of users that are permitted to use the utility ‘su’ in order to change to root.
[09:21] <marcamilly> *slip you mean ;)
[09:21] <marcamilly> not lips
[09:22] <marcamilly> ok thnx again gents
[09:22] <marcamilly> i'm off
[09:23] <vila> AuroraBorealis: weird, sudo is preferred over su these days iiuc but who knows
[09:23] <vila> it may be a BSD heritage ? fullermd ?
[09:23] <AuroraBorealis> just got that off some unix website
[09:24] <vila> oh, ok
[09:24] <AuroraBorealis> basic idea is the same
[09:25] <AuroraBorealis> but i doubt that the osx installer would ruin the permissions on /usr/local/bin o.o
[09:26] <mgz> yeah, I never use su
[09:26] <AuroraBorealis> apple's mantra is usually to try and not cause a terrible failure of the computer haha
[09:27] <AuroraBorealis> and how easy is it to build the mac os x bzr dmg?
[09:27] <AuroraBorealis> or installer
[09:27] <mgz> likely a pre-borked system, lucky we have vila.
[09:27] <mgz> the good thing about windows is restarting *would* have worked :)
[09:28] <mgz> where as with unix you need someone who understands it to tell you what commands to type :)
[09:28] <vila> AuroraBorealis: pretty easy, see https://launchpad.net/bzr-mac-installers
[09:28] <millun> hello
[09:28] <millun> bzr-explorer stopped working for me. i am looking for a good alternative
[09:28] <vila> mgz: :)
[09:29] <AuroraBorealis> bzr explorer is pretty good, define stopped working
[09:29] <mgz> millun, can you be more specific than "stopped working", ideally with a traceback or screenshot?
[09:30] <AuroraBorealis> vila, would i have to do anything because lion has python2.7 as the default?
[09:30] <millun> /usr/lib/pymodules/python2.6/pygments/plugin.py:39: UserWarning: Module pygments was already imported from /usr/lib/pymodules/python2.6/pygments/__init__.py, but /usr/lib/pymodules/python2.6 is being added to sys.path
[09:31] <AuroraBorealis> i think thats the main problem with it at the moment
[09:31] <vila> AuroraBorealis: not sure but if you have it should be pretty straight forward, doxxx really did a good job there
[09:31] <millun> import pkg_resources --> bzr: ERROR: exceptions.EOFError:
[09:31] <jelmer> poolie: ^\
[09:31] <vila> AuroraBorealis: the main issue is to setup the initial dev requirements (TeX is pretty big to download iirc)
[09:31] <millun> oic. i did run out of space some weeks ago. that could be it? i will try to reinstall bzr
[09:31] <jelmer> poolie: it was that sort of error that we were seeing for lazr.restfulclient as well
[09:32] <AuroraBorealis> i'll look into it when i have time, hopefully this weekend
[09:32] <vila> jelmer: wasn't it related to eggs or something ?
[09:32] <vila> AuroraBorealis: that would be awesome
[09:32] <jelmer> vila: nope, this is on Debian/Ubuntu which don't install eggs
[09:32] <mgz> millun, if you have truncated pyc files, that could help
[09:33] <mgz> but I need to see a full traceback to have an idea what's wrong.
[09:33] <mgz> !pastebin
[09:34] <mgz> if you do `bzr explorer` on the command line, and put the full output up, that would help.
[09:34] <poolie> yeah for the channel that was https://bugs.launchpad.net/ubuntu/+source/lazr.restfulclient/+bug/796992
[09:34] <poolie> insane
[09:34] <vila> oh, I thought .pth were related to eggs 0.O
[09:35] <millun> http://www.sexshopik.cz/we-vibe-2-7249/
[09:36] <poolie> i don't think so
[09:36] <millun> sorry
[09:36] <millun> my bad :-)
[09:36] <millun> http://dpaste.com/637252/
[09:36] <poolie> should i even click that?
[09:36] <millun> not really, unless you want to
[09:37] <poolie> i'm glad you're mistaken not a spambot :)
[09:37] <millun> looking for an xmas present :-)
[09:37] <poolie> or at least a clever one
[09:37] <poolie> night all
[09:37] <millun> night
[09:37] <vila> poolie: night
[09:37] <jelmer> g'night poolie
[09:37] <mgz> variation on bug 814151
[09:38] <vila> mgz: from JS Bach ?
[09:38] <mgz> delete ~/.bazaar/explorer/history.dat
[09:38] <mgz> and explorer will magically start working for you again millun
[09:38] <millun> awesome
[09:39] <millun> sweet!!
[09:39] <millun> thanks
[09:39] <millun> a lot
[09:43] <mgz> guess I better fix that bug
[11:03] <mgz> Riddell: when you mark bugs you've fixed, set yourself as the assignee and put in the milestone so you get blame on the release page
[11:06] <Riddell> mgz: release page?
[11:10] <mgz> Riddell: eg https://launchpad.net/bzr/+milestone/2.5b3
[11:10] <Riddell> cor, I've never seen that before
[11:10] <Riddell> do we use that, don't we just use the release-notes ?
[11:11] <mgz> I've found having the info in launchpad can be useful for seeing just from a bug entry what version has the change
[11:22] <mgz> vila: GlobalConfig.get_editor is telling bzr-explorer it's deprecated, what's the replacement?
[11:23] <mgz> searching release notes for 2.4 and my mail archive isn't telling me.
[12:16] <jelmer> mgz: would you perhaps be able to review a branch for me?
[12:23] <mgz> jelmer: yes, that's on my list of stuff to do today
[12:23] <mgz> is there a a paticular one you want me to look at before I go and have lunch?
[12:24] <vila> mgz: that should be config.GlobalStack().get('editor')
[12:24] <mgz> vila: and how far back does that work?
[12:25] <mgz> ...current explorer wants to support bzr 2.3+ as far as I can see
[12:25] <vila> 2.5 probably, let me check
[12:26] <vila> nope, valid in 2.4 already
[12:28] <jelmer> mgz: Cool, thanks :) https://code.launchpad.net/~jelmer/bzr/build-commit-parent-ids/+merge/79707 should be fairly simply and would unblock one of my other branches
[12:28] <mgz> vila: but not 2.3 then so I'll need to do a dance of some kind I guess
[12:29] <vila> mgz: what's the context ?
[12:29] <mgz> jelmer: what confused me a little with that mp is you also add a allow_leftmost_as_ghost param
[12:29] <vila> bzr-explorer ?
[12:29] <mgz> vila: yup
[12:30] <vila> no targeted branches for it ?
[12:30] <mgz> jelmer: is that just being pulled out of the **kwargs or is it also new?
[12:30] <jelmer> mgz: it's new
[12:30] <mgz> vila: it's a little less strict than qbzr about having one series per bzr series
[12:30] <jelmer> commit() doesn't take a parent_ids argument
[12:31] <vila> mgz: well, the sooner the better then ;) Or more trouble is expected
[12:34] <mgz> right, lunch lunch.
[12:54] <jelmer> mgz: thanks!
[13:04] <vila> jelmer: could you give feedback on https://code.launchpad.net/~bzr/bzr-svn/stacks/+merge/78259 ? Or should we just discuss it ?
[13:07] <jelmer> vila: I'll have another look at it this afternoon
[13:07] <vila> cool
[13:07] <jelmer> sorry for letting it slip
[13:08] <vila> np
[13:29] <mgz> bug 878132 looks like a config interface change too
[13:50] <jelmer> wow, we should really ahve another look at pypy
[13:50] <jelmer> http://speed.pypy.org/
[14:08] <jam> jelmer: I agree, with the main caveat that our actual performance sensitive code is written in Cython/C
[14:08] <jam> which is often not compatible with pypy
[14:08] <jam> it also depends a lot on JIT performance, and bzr is a process that starts and stops a lot
[14:08] <jam> so may never 'warm up' enough to get the JIT effect.
[14:35] <Lo-lan-do> Hi all :-)
[14:36] <Lo-lan-do> jelmer: You say "bzr-git plugin is quite stable" — does that mean what I hope it means, and did I miss something important?
[14:37] <jelmer> Lo-lan-do: it doesn't mean roundtripping works, but dpush/pull work pretty well
[14:37] <Lo-lan-do> Ah.  How about multiple branches?
[14:42] <jelmer> Lo-lan-do: there is basic support for those in bzr 2.5
[14:42] <Lo-lan-do> Aha.  Good news :-)
[14:44] <briandealwis> Hi all.  I'm currently using branch.revision_id_to_dotted_revno in tiplog to map a number of revision-ids for a branch.  It's quite slow if I go across the network.  Is there anything I can do to speed it up?
[14:50] <briandealwis> Will obtaining a read lock on the branch help?
[14:59] <briandealwis> never mind — I didn't read the report correctly
[15:08] <jelmer> hi briandealwis
[15:08] <briandealwis> hi jelmer
[15:09] <jelmer> Lo-lan-do: basically, you can do something like "bzr dpush git+ssh://git.debian.org/git/collab-maint/heimdal,branch=experimental"
[15:09] <jelmer> Lo-lan-do: local support for colocated branches still needs some more improvements (having to use "bzr switch file://`pwd`,branch=bar" rather than "bzr switch bar" is annoying)
[15:11] <Lo-lan-do> That's just a matter of a shell alias :-)
[16:08] <fullermd> vila: hmmwhut?
[16:08] <vila> fullermd: what is the wheel group origin and use ?
[16:09] <fullermd> Controls access to su (and repurposes for other similar uses by everyone of course).  I think it came out of Berkeley early on, like 2BSD era.  I'd have to dig around.
[16:10] <fullermd> There's no wheel group in the SysIII dist at least.
[16:11] <vila> I thought su was close to being deprecated by sudo (at least to become root) but it seems to be all over the place in osx
[16:11] <vila> rhaa, s/it/wheel/
[16:12] <fullermd> I can't imagine it will ever be _deprected_ in existence.
[16:12] <fullermd> I hardly ever use it interactively of course.  But still, it's there in base, and gets used all over the place programmatically.
[16:12] <fullermd> Anyway, I use the wheel group to control who can sudo   8-}
[16:12] <vila> hehe
[16:13] <vila> right, so it will never disappear because no one will even try to delete it ;)
[16:14] <fullermd> Oh, people will try.  I hope not too many more, though.  The hole in my back yard is getting full.
[16:14] <vila> hehe, time for BBQ instead
[16:15]  * Lo-lan-do uses "su" daily
[16:16] <fullermd> Probably more likely that 'operator' will get retired.  And I'm sure that won't happen anytime soon...
[16:16] <vila> Lo-lan-do: really ? To get root access or to other users ?
[16:17] <Lo-lan-do> Mostly for root, but often to other users too.
[16:17] <Lo-lan-do> "su - postgres -c 'psql gforge'" is one command I use quite often.
[16:19] <mgz> see, I didn't even know the syntax for switching user with su
[16:20] <mgz> just use dumb basic option of act-as-root sudo
[16:20] <vila> Lo-lan-do, fullermd : what I still don't get is why files and dirs get group wheel...
[16:21] <fullermd> Which files?
[16:21] <Lo-lan-do> Ah, I have no idea.  Never had anything to do with wheel myself.
[16:21] <fullermd> I use the group to let just wheel people see stuff...
[16:21] <fullermd> Considering that 'su' means 'switch user', it isn't hard to guess the syntax   :p
[16:21] <vila> grr
[16:21] <vila>  /usr hierarchy for example
[16:22]  * fullermd shrugs.
[16:22] <vila> (never ever type an absolute path at the beginning of a chat msg)
[16:22] <fullermd> By default I s'pose.  The group doesn't mean much through there really.
[16:23] <vila> ok
[16:23] <fullermd> Rarely has differnt perms than 'other'.
[16:23] <vila> yup
[16:23] <fullermd> And usually when there are, it's a different group anyway.
[16:24] <fullermd> e.g. -r-sr-x---  1 root  network  412392 Jul 30 21:53 /usr/sbin/ppp*
[16:24] <vila> so yeah, used as a default as *one* group is needed
[16:24] <vila> yup
[16:24] <fullermd> And being gid 0, it's a good excuse for default  ;)
[16:24] <vila> hmpf, silly me !
[16:26] <vila> makes sense, uid(root) == 0 because he's here first, then gid(wheel) == 0 because root *may* have friends
[16:26] <vila> the rest is optional ;)
[16:26] <fullermd> If root gets friends, why don't I?  :(
[16:27] <vila> fullermd: they are in your backyard :)
[16:27] <fullermd> Hm, yeah.  Always present.  But they suck at bowling.
[17:44] <mgz> I've hung vim, with cpu pegged at 100%, how the hell did I manage that
[17:45] <fullermd> Maybe it's trying to start emacs.
[17:45] <mgz> it died politely at least and...
[17:46] <mgz> with an interestingly giant number in the output
[17:46] <mgz> I think I may have accidentally told it to do something thousands of times, by not being in insert mode when pasting a bug number
[17:47] <mgz> 814151 is pretty big.
[17:47] <fullermd> It takes it a while to do brace matching on meg+ JSON files too.
[17:47] <fullermd> Seems like that should be faster.
[17:48] <mgz> yup, I seem to have a file with that number, probably repeated that number of times
[17:48] <mgz> I'll get used to modality in the end...
[20:33] <wonza> Hi, I have a little bzr problem in that I can't seem to create a new branch while logged into my work computer over ssh from home. http://pastebin.com/DCWj0LCF has the error listed. If anyone could help, that'd be really great :) (commits, and updates seem to work just fine btw)
[20:41] <wgz> wonza: looks like bug 796873
[20:44] <wgz> so +affectsmeto that at least, and you can likely catch the error in the 'custom' plugin as suggested in the discussion there
[20:46] <wgz> the change for this issue in bzr-gtk was basically just that: <http://bazaar.launchpad.net/~bzr-gtk/bzr-gtk/trunk/revision/685>
[20:48] <wonza> thanks for the suggestion, I'll take a look
[21:20] <thumper> hey
[21:20] <thumper> is there a "stock" presentation for bazaar internals?
[21:20] <thumper> I'm wanting to describe how revisions work, branching and merging, and why mainline is special
[21:20] <thumper> also pipelines if one is around
[21:50] <fullermd> I've got some of that piled up in my SpotDocs...


[01:41] <MTecknology> edge went away? :(
[01:46] <lifeless> MTecknology: iz going
[01:46] <lifeless> MTecknology: why so sad?
[01:47] <MTecknology> lifeless: I just noticed I can't do recipes - I was going to try again
[01:48] <lifeless> you should be able to on edge
[01:48] <MTecknology> oh.. I just don't have the automatic redirect anymore?
[01:48] <lifeless> right
[01:48] <lifeless> edge is going
[01:48] <MTecknology> oh
[01:48] <lifeless> its not gone yet
[01:49] <MTecknology> will recipes be available when it does go?
[01:49] <lifeless> recipes will be available to recipe beta testers on production before edge goes
[01:49] <MTecknology> yay
[01:50] <MTecknology> lifeless: what's the team name?
[01:52] <lifeless> dunno yet :)
[01:52] <MTecknology> alrighty
[02:06] <MTecknology> lifeless: dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found
[02:06] <MTecknology> lifeless: Any idea what's up with that?
[02:07] <lifeless> there was a thread on the bzr list about this
[02:07] <lifeless> is a bug (obviously)
[02:07] <wgrant> I don't think it's a bug.
[02:07] <wgrant> dpkg in maverick just doesn't fall back any more.
[02:08] <wgrant> Launchpad's daily builds feature doesn't support orig tarballs yet.
[02:08] <lifeless> wgrant: its a usability issue for recipes
[02:08] <wgrant> It is.
[02:08] <MTecknology> Natty-> Could not build because of chroot problem
[02:08] <wgrant> MTecknology: That's because IS needs to set up natty bzr-builder packages.
[02:08] <MTecknology> so for now I still need to build each series by itself if I need to use quilt?
[02:09] <wgrant> You can't use quilt. You can only build a native package.
[02:09] <wgrant> <= lucid automatically fall back to native.
[02:09] <wgrant> maverick doesn't.
[02:09] <wgrant> So you need to specify 3.0 (native) or 1.0 to get the same behaviour.
[02:10] <MTecknology> ok
[02:10] <MTecknology> what are the changes of that breaking something else?
[02:11] <wgrant> It should have been building native packages anyway.
[02:11] <wgrant> So just about zero.
[02:11] <MTecknology> alrighty
[02:11] <MTecknology> so 3.0 (quilt) and 3.0 (native); those both use the same patch system or??
[02:11] <wgrant> 3.0 (native) doesn't have a patch system. Everything ends up in the tarball.
[02:12] <MTecknology> what about debian/patches/* ?
[02:12] <wgrant> Which recipe is this?
[02:12] <MTecknology> or am I utterly lost in the patching system?
[02:12] <MTecknology> https://code.edge.launchpad.net/~nginx/+recipe/nginx-development/
[02:13] <StevenK> The idea with recipes is the patches are directly applied, since you have version control
[02:13] <wgrant> dpkg-source: info: source format `3.0 (quilt)' discarded: no orig.tar file found
[02:13] <wgrant> dpkg-source: info: using source format `1.0'
[02:13] <wgrant> MTecknology: That's from the Lucid log.
[02:13] <wgrant> So it's using 1.0.
[02:13] <wgrant> And therefore probably not applying patches.
[02:14] <MTecknology> If I change source/format from 3.0 (quilt) to 3.0 (native) - would it apply patches the same way?
[02:14] <wgrant> The same way as 1.0, which is "not at all".
[02:14] <MTecknology> oh...
[02:15] <wgrant> 3.0 (quilt) applies patches.
[02:15] <wgrant> That's why 'quilt' is in the name.
[02:15] <MTecknology> so if I want to use the patching system.. I have to build nd upload myself?
[02:15] <wgrant> Why do you want to use a patch system?
[02:15] <wgrant> Why not have the changes directly in the branch that you merge in?
[02:15] <wgrant> s/branch/branches/
[02:16] <wgrant> I hear that bzr is good at this merging thing.
[02:16] <MTecknology> because the source is an exact copy of the upstream source; anything done to the package is inside debian/
[02:16] <wgrant> You could alternatively include a patch system in debian/rules.
[02:16] <wgrant> But I would be making the changes directly in another branch which is then merged on top of trunk.
[02:17] <MTecknology> how do you include the patching system in debian/rules?
[02:17] <StevenK> I would check, but I purged quilt from this machine for being crap
[02:18] <wgrant> Hah.
[02:18] <MTecknology> I'm not the biggest fan of quilt either..
[02:18] <wgrant> Woah, old-style debhelper rules file.
[02:18] <StevenK> Haha
[02:18] <MTecknology> but the debian maintainer uses quilt so if I send them a patch; it's easiest to keep it quilt
[02:19] <StevenK> quilt has a way to import a patch file into a quilt patch file, so meh
[02:22] <exarkun> If this release, <https://launchpad.net/pyopenssl/main/0.11>, was only registered 3 hours ago, how can some of its files have been downloaded 24 hours ago?
[02:22] <MTecknology> Is it going to be possible to use a patching system in a recipe someday?
[02:22] <wgrant> MTecknology: Yes.
[02:22] <wgrant> MTecknology: We just need to work out a nice way to handle orig.tar.*
[02:23] <MTecknology> wgrant: oh... I suppose since you can't just upload them as you do with the dput method..
[02:24] <wgrant> Right. We need to either extract them from bzr (using pristine-tar, probably), or find some other way to get them in there.
[02:24] <lifeless> MTecknology: in the bzr thread folk suggesting forcing them to native
[02:25] <MTecknology> lifeless: which means no patch system so any patches are dropped?
[02:30] <MTecknology> I can handle building them individually for now. I was just hoping
[02:30] <MTecknology> I'm excited for recipes to be ready for the big time
[02:30] <MTecknology> lifeless: so where's the mailing list?
[02:31] <MTecknology> alrighty - 8 builds waiting - 2 will die right away
[02:32] <MTecknology> I feel I annoying to many people that actually understand what's going on
[02:33] <lifeless> MTecknology<EMAIL_ADDRESS>[02:33] <lifeless> erm
[02:33] <lifeless><EMAIL_ADDRESS>[02:33] <MTecknology> thanks
[02:41] <MTecknology> If you upload a lot of packages to be built - can you be 'punished' and have to wait longer for it to build?
[02:42] <StevenK> #define a lot ?
[02:43] <MTecknology> attempting a recipe build for lucid/maverick/natty in two ppa's then after failing; trying the same thing again by building them myself
[02:43] <MTecknology> really.. I should only have built for one ppa and just copied
[02:43] <lifeless> MTecknology: at the moment queue scheduling is very static. This will change.
[03:03] <MTecknology> Would any of you kill be if I decided to upload all of python to be built?
[03:03] <wgrant> All of Python?
[03:04] <MTecknology> every single python package that's in main
[03:04] <MTecknology> or wait..
[03:04] <MTecknology> what was it that was really killing builds a while back that got uploaded a couple times?
[03:05] <MTecknology> sorry for the dumb attitude - I think I'm lacking on sleep pretty bad
[03:12] <wgrant> MTecknology: That was Python, yes.
[03:12] <wgrant> Not just main, though.
[03:12] <wgrant> 'twas the whole archive.
[03:13] <MTecknology> wgrant: that wasn't exactly a fun time for packaging :P
[04:55] <micahg> lamont: when you get a chance can you kill the build on iridium and prevent it from starting again? It's going to hang until bug 663294 is fixed
[04:56] <micahg> lamont: if you can't do that easily, let me know and I"ll delete the xulrunner build in the PPA
[08:35] <eagles0513875|2> hey guys i have a question is it possible to import a public key that i generated outside of linux such as with putty or xshell etc how can i upload my key?
[08:37] <persia> eagles0513875|2, You should be able to upload a key generated with any tool, although you may need to check the documentation for that tool to find the public key in local storage.  Once you identify the public key, the remainder of the procedure should be unchanged.
[08:38] <eagles0513875|2> persia: i have my keys on my pendrive for portability
[08:38] <eagles0513875|2> hummo k
[08:38] <eagles0513875|2> humm ok
[08:38] <eagles0513875|2> thanks persia
[08:47] <eagles0513875|2> hey guys for bugs in a bzr project i created where do i file bugs against the project
[08:47] <eagles0513875|2> of mine
[08:53] <odony> Hi, anyone familiar with the launchpadlib API here? I'm trying to get the number of bugs in a given status for a projects, but get this interesting error "TypeError('collection size is not available')" ... Am I supposed to iterate over the (huge) collection of matching bugs just to know how many there are?
[08:54] <odony> the API seems to indicate that you can query the length of collections: https://help.launchpad.net/API/launchpadlib#line-428
[09:01] <fta2> henninge, dpm: hi, did you get email wrt my chromium translations issue?
[09:01] <fta2> +my
[09:02] <henninge> fta2: yes, looking at it atm
[09:03] <henninge> at the issue, I mean
[09:03] <henninge> will get back to you
[09:03] <fta2> ok, excellent, thanks
[09:03] <dpm> morning fta2, I'm just reading all post-UDS e-mail right now, I haven't come to it yet, but I will in a few mins
[09:04] <fta2> henninge, btw, i mentioned only one change, but there are a few more (mostly encoding of \n and some xml entities i had to do to ensure the full bijection between grit and gettext)
[09:12] <odony> about my issue with sizing launchpadlib collections, seems to be an upstream bug from lazr, found a workaround here: https://bugs.launchpad.net/wadllib/+bug/274074 ... long outstanding issue apparently
[09:13] <odony> seems fixed in wadllib 1.5.5, gonna try that, otherwise monkeypatching lazr.restfulclient.resource.Collection.__len__ works for me
[09:33] <henninge> fta2: So, it must be an error in the export-to-branch script, AFAICT
[09:33] <henninge> fta2: A manual export of a po file produces correct data (i.e. without "<ph" in it)
[09:34] <fta2> henninge, without &ph too?
[09:34] <henninge> Also, I notice that the exported files still reference the old POT-Creation-Date, whereas the manual export has the new date
[09:34]  * henninge looks
[09:34] <fta2> henninge, search for "ph path=" instead
[09:35] <henninge> fta2: you can do a manual download of a single file here https://translations.launchpad.net/chromium-browser/translations/+pots/chromium-strings/de/+export
[09:35] <fta2> henninge, i meant "ph name="
[09:35]  * henninge looks
[09:35] <henninge> fta2: nothing
[09:36] <henninge> in fact, "ph" only occurs twice in the whole file, but in only as part of other words.
[09:36] <fta2> ok. so the script populating the branch is broken
[09:36] <henninge> yup
[09:36] <henninge> fta2: can you please file a but about that?
[09:36] <fta2> ok
[09:37] <henninge> https://bugs.launchpad.net/rosetta/+filebug
[09:38] <henninge> fta: as a work-around you can download all the translations in a tarball from here: https://translations.launchpad.net/chromium-browser/translations/+export
[09:38] <henninge> fta2: ^
[09:39] <fta2> henninge, i guess the content on my email is good enough, right?
[09:39] <henninge> fta2: yes, but add that a manual export works as expected.
[09:39] <fta2> ok
[09:40] <henninge> fta2: with the tarball download, I am not sure if the file naming suites your branch ... :(
[09:40] <henninge> sorry about the inconvenience
[09:40] <fta2> as for the tarball, we already discussed that a few weeks ago, it won't work for me, due to different file names policy
[09:40] <henninge> what I feared ... :(
[09:41] <henninge> fta2: I will see that we find the reason and a fix for it asap.
[09:42] <fta2> bug 669831
[09:44] <fta2> henninge, thanks. would be nice. I just have a knob to flip in the chromium package to re-enable the translations merges
[13:51] <berco> hi
[13:51] <berco> anyone knows what to do if want a 3PA to build for natty as well as maverick?
[14:18] <persia> berco, Did you already try just uploading with "natty" in the changelog?  Did that not work?
[14:53] <Laney> berco: You can upload to M and then use the Launchpad PPA interface to copy the package to N.
[14:53] <Laney> Or upload to M and then N with a higher version.
[15:27] <micahg> deryck: convert to question is a no go: OOPS-1767E1152
[15:27] <berco> persia: I tried it but my package has been rejected
[15:28] <deryck> micahg, will it work on a reload?
[15:28] <berco> Laney: I thought I could specify both "maverick natty" in my changelog
[15:28] <persia> berco, Aha!  Then it is something awkward.  If nobody gets back to you here, file a question (answers.launchpad.net/soyuz)
[15:28] <persia> berco, No, you can only specify one.
[15:28] <micahg> deryck: no
[15:29] <deryck> micahg, ok.  Will take it up a notch.
[15:29] <berco> persia: pk. According to the debian policy I understood I could list both distri
[15:29] <deryck> lifeless, can you do feature flags, or do you need an admin like the rest of us?
[15:29] <berco> I'll try with just natty
[15:29] <micahg> deryck: thanks
[15:29] <persia> berco, Dunno if that's a bug in policy or a bug in Soyuz :)
[15:30] <lamalex> Is there any way to direct what bugmail goes to what email address?
[15:31] <lamalex> I'd like to send my Unity bugmail to my Canonical email address, but for the projects I do in my free time I'd prefer my gmail
[15:31] <deryck> lamalex, no, there's no way to do that.  We use the preferred email address for all bug mail.
[15:34] <Laney> You can filter by the X-Launchpad headers though
[15:35] <lifeless> deryck: the form requires Launchpad.ADMIN to make changes.
[15:35] <lifeless> deryck: e.g. ~admin only. Rubber ducky, you're the one.
[15:35] <deryck> k, thanks.
[15:36] <deryck> lifeless, micahg reports the 15 seconds doesn't help.  Perhaps he's on lp.net now.  Do you mind 20 secs on that page now?
[15:36] <lifeless> deryck: cross check the PPR
[15:36] <deryck> lifeless, PPR?
[15:36] <lifeless> deryck: page performance report
[15:36] <lifeless> that will show you the spread
[15:36] <deryck> ah
[15:36] <lifeless> then check a representative OOPS
[15:36] <lifeless> that will give you /some/ idea.
[15:37] <lifeless> if there is a big uptick at the right edge of the graph, it means incompleted requests are hitting the timeout in significant numbers
[15:37] <lifeless> that means that raising the timeout will spread the uptick out, but you may find it needs to be higher.
[15:40] <maxb> berco: Debian policy says you can list multiple distributions there. It does *not* however define what it means to do so, AFAIK, so it's up to each individual implementation of an upload processor to determine what to do
[15:40] <deryck> ok, thanks, lifeless.  We may need higher then.  I read it as, generally ok for everyone but Ubuntu. :-)  Waiting on OOPS to sample.
[15:43] <micahg> deryck: do you need me to try again or is the oops above ok?
[15:43] <deryck> micahg, it should be fine.  There's some delay between the OOPS generated and the web interface to review it.
[17:22] <nekohayo> hey there, I just got added to https://launchpad.net/~ubuntu-answer but I still can't create FAQs for https://answers.launchpad.net/ubuntu/+source/pitivi/+question/132140/+createfaq (for example); I get the same "Not allowed here" error. What's up?
[19:00] <MTecknology> Is there any chance somebody could look at why this is broken? https://code.launchpad.net/~nginx/nginx/echo-module
[19:13] <cjohnston> jamesh: ping
[19:16] <lifeless> MTecknology: file a question on answers.launchpad.net/launchpad-code ?
[19:24] <deryck> micahg, the page is in too bad a shape for me to raise the timeout.  Nothing will help until we fix the root cause of the timeout.
[19:24] <micahg> deryck: :(
[19:25] <deryck> micahg, sorry, man.
[19:25] <micahg> deryck: I understand, is it still at the top of the list?
[19:26] <deryck> micahg, yes.  next on my list for the bugs team, but that's still a few days off from being started.  Just no capacity yet.
[19:26] <lifeless> micahg: its in the timeout bucket, which is prioritised to the top of the 'current work backlog' for all LP teams.
[19:26] <micahg> deryck: ok, thanks, let me know if you need testing
[19:26] <deryck> micahg, definitely will.
[19:26] <deryck> thanks!


[05:36] <soee> good morning
[07:06] <smartboyhw> kubotu: newversion calligra 2.6.90
[07:06] <kubotu> https://bugs.launchpad.net/bugs/1178125
[07:06] <smartboyhw> Meh, is 4.10.3 done?
[07:09] <soee> dont think so :)
[07:09] <soee> yofel said yesterday he might work on it today if find time
[08:33] <Riddell> smartboyhw_: only if you've done it :)
[08:36] <Mamarok> btw, people, there apparently is a kdelibs/plasma regression in KDE 4.10.3, not something I would release as is: https://bugs.kde.org/show_bug.cgi?id=319475
[08:41] <soee> can't confirm - have no 4.10.3 yet :0
[08:42] <soee> hope yofel find time to do packaging
[08:42] <soee> or in summer i try to find out how to do it and do it myself next time :)
[09:32] <yofel> good morning
[09:33] <shadeslayer> morning :)
[09:54] <afiestas_> ScottK: thanks
[10:38] <yofel> shadeslayer: ping
[10:38] <yofel> do I need some special setup for bug 1177333?
[10:38] <yofel> because "just" nvidia + kscreen doesn't crash for me
[10:42] <kubotu> ::qt-bugs:: [1177823] qdbus needs dependency ubuntu-sdk to work @ https://bugs.launchpad.net/bugs/1177823 (by Patola)
[10:44] <kubotu> ::runtime-bugs:: [1178192] My laptop occasionally doesn't shutdown @ https://bugs.launchpad.net/bugs/1178192 (by Tomas Brandysky)
[10:48] <shadeslayer> uhh no
[10:48] <shadeslayer> just nvidia drivers
[10:49] <yofel> it only happens when you don't use nouveau on first login maybe?
[10:49]  * yofel tries that
[10:49] <Riddell> you need a second screen
[10:49] <Riddell> you do anything in kscreen
[10:49] <yofel> I have that
[10:49] <Riddell> then next login it crashes
[10:49] <yofel> ah, ok
[10:54] <yofel> err... nope
[10:55] <yofel> maybe that only happens when you have 2GPU's ?
[10:58] <afiestas_> yofel: kscreen-console output
[10:59] <yofel> afiestas_: is that supposed to finish or should I CTRL-C it at the end?
[11:00] <afiestas_> yofel: ctrl+c should be ok
[11:01] <yofel> afiestas_: http://paste.kde.org/740534/
[11:02] <afiestas_> yofel: are you using nvidia blob?
[11:04] <yofel> that's using nvidia-313-updates (313.30), Xorg.log if you need the details: http://paste.kde.org/740540/
[11:04] <yofel> that's pretty much a fresh install, so maybe I'm missing something... but I don't see what
[11:08] <afiestas_> yofel: nope, your ystem has a LVDS,it crashes with other kind of displays
[11:08] <yofel> ah, so you would need a desktop with 2 monitors...
[11:12] <yofel> afiestas_: 2 identical displays or would a DVI/VGA mix do?
[11:12] <afiestas_> yofel: you need an embedded display called DP
[11:13] <yofel> er, that's nvidia's naming for DisplayPort, that's not embedded
[11:13] <yofel> but let me try that actually
[11:13]  * yofel goes digging around for his DP-HDMI adapter
[11:16] <yofel> :/
[11:17] <yofel> first I pull my VGA cable out of the notebook and nothing changes until I run 'xrandr' in konsole... and now I plug my DP cable in,  screen is configured right but now plasma is frozen solid -.-
[11:21] <yofel> well, didn't crash either, so it probably needs to be embedded after all
[11:21]  * yofel gives up
[11:29] <BluesKaj> Hiyas all
[11:53] <Quintasan> hello
[11:54] <Quintasan> yofel: I can't reproduce it on my desktop, two DVI ports and nothing happens
[11:54] <Quintasan> I'll try it on my laptop later when I get the dvi connector
[11:57] <BluesKaj> hey , getting this error and I think I know what the offending app/patch is , "
[11:57] <BluesKaj> Error!  The dkms.conf for this module includes a BUILD_EXCLUSIVE directive which
[11:57] <BluesKaj> does not match this kernel/arch.  This indicates that it should not be built.
[11:58] <yofel> BluesKaj: can you pastebin the surrounding parts please?
[11:59] <BluesKaj> https://launchpad.net/~ubuntu-audio-dev/+archive/alsa-daily
[12:02] <BluesKaj> yofel, here's the paste, http://pastebin.com/ZfbpMidR
[12:04] <BluesKaj> yofe I'm thinking that hdmi patch is seen as the problem since it's 32 bit
[12:10] <BluesKaj> bbiab
[12:21] <yofel> BluesKaj: sounds like it... what does 'dkms status' say?
[12:25] <BluesKaj> oddly the kernel seemed to build ok , dkms status : http://pastebin.com/EE8nbUhE
[12:25] <BluesKaj> yofel,^
[12:27] <BluesKaj> and uname -a shows : 3.9.0-1-generic x86_64 x86_64 x86_64
[12:30] <BluesKaj> yofel , doesn't seem to be an issue , all seems fine , think I was concerened for no reason
[12:31] <yofel> hm, reading the dkms logs would probably tell more, but I forgot where those were... either somwhere under /var/log or /lib/modules/ iirc...
[12:41] <BluesKaj> yofel, turns out the suspect patch is 64 bit after all , so it's something else ..I did install lsb-core and ia32-libs for google-earth previous to new kernel buld
[12:57] <yofel> BluesKaj: found the log location: /var/lib/dkms/<module>/<version>/<kernel>/<arch>/log
[12:57] <yofel> maybe that can tell you more
[12:58] <yofel> Can someone please try to explain to me how this can happen? http://paste.kde.org/740570
[12:58] <yofel> that code hasn't changed since 2009...
[12:58] <yofel> raring didn't suddenly switch compilers either
[12:58] <smartboyhw> Dunno…
[12:59] <yofel> the method is
[12:59] <yofel> bool init(const QString &configfile);
[12:59] <yofel> so the symbol is correct
[12:59] <yofel> I just don't get why it would change NOW
[12:59] <yofel> that's private so not much of an issue... I just don't get it
[13:03] <yofel> saucy debhelper is fun
[13:03] <yofel> lintian I mean
[13:03] <smartboyhw> yofel: How fun?
[13:03] <yofel> E: kde4libs source: license-problem-gfdl-invariants kdoctools/customization/el/entities/gpl-notice.docbook
[13:03] <yofel> like... 50 times
[13:04] <smartboyhw> What the hell?:P
[13:04] <yofel> correction: 113 times
[13:04] <smartboyhw> yofel: :O
[13:05] <Riddell> one for each language
[13:05] <Riddell> dudes: mgraesslin says there's abug in plasma in 4.10.3 and we probablydon't wantto release it until that's fixed
[13:05] <yofel> the one Mamarok pointed to?
[13:06] <yofel> kde 319475
[13:06] <Riddell> quite possibly
[13:06] <smartboyhw> Riddell: Good, we haven't done anything on 4.10.3:P
[13:06] <yofel> well, I'm not done with it anyway. Will try to get it in a usable state so we can try it
[13:11] <yofel> ...
[13:12] <smartboyhw> yofel: … :P
[13:13] <yofel> Phonon5: kde-workspace-4.10.2/debian/libkwinglutils1abi1.symbols of your kde-workspace SRU in raring-proposed looks rather odd
[13:13] <yofel> libkwinglutils.so.1abi2 libkwinglutils1abi1 #MINVER#
[13:13] <yofel> is that 1abi1 or 1abi2 now...?
[13:15] <yofel> it won't matter for .3 as the patch is dropped again, but...
[13:17] <smartboyhw> kde 319428
[13:17] <yofel> @_@
[13:18] <smartboyhw> We need to SRU every kdepim 4.x with this, as in the mailing lists…
[13:18] <shadeslayer> yep
[13:18] <shadeslayer> I was just looking at that
[13:18] <yofel> ah good
[13:18] <smartboyhw> shadeslayer: \o/
[13:19] <yofel> shadeslayer: lucky you that 2 releases just went EOL :P
[13:19] <shadeslayer> hurray :P
[13:19] <smartboyhw> yofel: shadeslayer: :P
[13:29] <yofel> libnepomukextractor.so
[13:31] <yofel> shadeslayer: that had no headers, right?
[13:32] <yofel> brrrrr
[13:32] <yofel> +    class NEPOMUK_EXTRACTOR_EXPORT ExtractorPlugin : public QObject
[13:32] <yofel> -    class NEPOMUK_EXPORT ExtractorPlugin : public QObject
[13:36] <shadeslayer> nope, vHanda says it's a private header
[13:37] <shadeslayer> yofel: why?
[13:38] <yofel> shadeslayer: nah, should work, it just seemed fishy from the kdeadmin and kdepim build logs, but I guess those were old
[13:38] <shadeslayer> ah yes
[13:38] <shadeslayer> vHanda also mentioned something about that :P
[13:38] <yofel> shadeslayer: are you sure that file should be in nepomuk-core-dev though?
[13:39] <shadeslayer> yofel: nope, it should be in the standard normal package
[13:39]  * vHanda waves
[13:39] <shadeslayer> so I made a mistake if it's not there
[13:39] <yofel> yeah, that's what I was wondering about and went looking if something of it is public
[13:39] <yofel> I'll move it
[13:40] <shadeslayer> yeah, thanks :)
[13:53] <shadeslayer> hmm
[13:53] <shadeslayer> yofel: did you apply https://projects.kde.org/projects/kde/kdelibs/repository/revisions/65d736dab592bced4410ccfa4699de89f78c96ca to the 4.10.3 packages??
[13:54] <yofel> shadeslayer: not yet, needs to be done
[13:54] <yofel> er wait
[13:54] <yofel> that bug is marked at "Fixed-in: 4.10.3", no?
[13:54] <yofel> *as
[13:55] <shadeslayer> mmm commit message doesn't say
[13:55] <shadeslayer> no "Version fixed in"
[13:55] <shadeslayer> plus it was commited 17 hours ago
[13:55] <shadeslayer> Added by Grégory Oestreicher about 17 hours ago
[13:55] <yofel> ok
[13:55] <yofel> checked git, it's not part of v4.10.3
[13:56] <shadeslayer> okay, I'll leave the 4.10.3 patching to you, and I'll upload to saucy first
[13:56] <yofel> good
[14:09] <Riddell> kde is not alone in its dislike of the SRU system http://paste.kde.org/740594/
[14:11] <smartboyhw_> Riddell: heh. Ubuntu should really reform it's SRU system.
[14:11] <smartboyhw_> Propose it to the TB
[14:13] <yofel> well, we already have several bugfix updates only in the PPAs because SRU-ing point releases is too much work
[14:13] <yofel> e.g. calligra or networkmangement
[14:14] <Riddell> smartboyhw_: I did
[14:14] <Riddell> there's not much that can be reformed without making it unsafe
[14:15] <smartboyhw_> Riddell: Meh
[14:16] <yofel> the procedure isn't bad, really. It just requires a large amount of manpower with the current design
[14:17] <smartboyhw_> yofel, Riddell: If they can reduce needed manpower for application uploads, they can reduce needed manpower in SRUs too.
[14:17] <Riddell> aparently suse don't do updates at all, atleast so someone said in our discussion, I'm not convinced this is true
[14:17] <smartboyhw_> Riddell: How can a distribution work properly without updates?
[14:17] <smartboyhw_> SRUs…
[14:19] <Riddell> that's why I'm not convinced it's true
[14:19] <yofel> Phonon5: is there something in kubuntu-settings that you don't want to have uploaded to saucy right now?
[14:20] <yofel> I would like to get bug 1174689 fixed
[14:20] <yofel> though the changes I see in the changelog look sane to upload
[14:22] <smartboyhw_> Meh, I just realized Phonon5 is apachelogger…
[14:22] <yofel> he likes to confuse people :P
[14:22] <smartboyhw_> yofel: ;P
[14:34] <shadeslayer> Riddell: https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/1178286
[14:38] <smartboyhw_> shadeslayer: Awesome, but aren't Lucid (desktop) supposed to EOL?
[14:38] <shadeslayer> smartboyhw_: yeah, but Lucid isn't approved
[14:38] <shadeslayer> so doesn't matter
[14:38] <smartboyhw_> shadeslayer: Good Riddell denied it:)
[14:38] <shadeslayer> yeah
[14:40]  * yofel usually approves and deletes the task after that
[14:40] <yofel> I hate how launchpad does release nominations
[14:40] <smartboyhw_> yofel: Oh
[14:41] <yofel> I mean there's not even a purpose for a declined nomination, setting the release status to Won't Fix gives the same message and is more flexible
[15:32] <smartboyhw_> Riddell: Nice blog post.
[15:41] <Phonon5> yofel: can all go up
[15:42] <yofel> perfect
[17:14] <Peace--> Riddell:
[17:15] <Riddell> hi Peace--
[17:15] <yofel> hm...
[17:15] <yofel> ~karma Peace
[17:15] <kubotu> Peace has neutral karma
[17:15] <Peace--> Riddell:  mmm maybe you can give me some advice about a voip software
[17:16] <yofel> ah, he turned that off, right
[17:16] <yofel> laggy...
[17:16] <Peace--> Riddell: we did a shell program  to create audio conference
[17:17] <Peace--> Riddell: but now we would like create a gui
[17:17] <Peace--> Riddell: qml is good for that ?
[17:17] <Peace--> Riddell: btw it is written in c ...
[17:17] <Peace--> Riddell: btw it's here http://nowardev.wordpress.com/2013/05/08/kubuntu-kde-voip-opensource-free-for-all-done/
[17:19] <Riddell> golly
[17:21] <shadeslayer> flipping patches
[17:21] <Riddell> well aye you can use QML,but QML needs you to pick a widget toolkit and even then bits can be missing
[17:21] <Riddell> it's great if you want swipey swooshy UIs
[17:21] <Riddell> but it might be easier to use just Qt in c++ or PyQt
[17:21] <Riddell> with QWidgets
[17:23] <Peace--> ok
[17:23] <Peace--> Riddell: tx
[17:23] <Peace--> Riddell: btw if you want test this software it will be great
[17:26] <Riddell> can do but not todya I'm afraid
[17:26] <Riddell> alreayd got a million things on my task list
[17:35] <shadeslayer> alright, bug 1178286 has everything now
[17:35] <shadeslayer> do I just upload stuff now?
[17:35] <shadeslayer> Riddell: ^
[17:36] <shadeslayer> or if anyone wants to review it
[17:40] <Riddell> shadeslayer: looks good, upload and subscribe ubuntu-security I'd say
[17:50] <debfx> shadeslayer: only the security team can do security uploads so all you have to do is subscribe them to the bug
[17:51] <Riddell> ah, shows how long it's been since kde had a security issue
[18:05] <debfx> shadeslayer: a description of the vulnerability would be nice in the changelog
[18:25] <shadeslayer> debfx: uhhh ... I get to upload everything again ? :S
[19:10] <ahoneybun> valorie: hey
[19:13] <debfx> shadeslayer: maybe just add another comment suggesting a new changelog
[19:13] <shadeslayer> ack
[19:17] <jussi01> hrm, do we still have anything like netbook edition? Ive an atom based machine I need to get something installed on...
[19:18] <jussi01> mind, it also has a touch screen, so Im hoping that also works...
[19:21] <shadeslayer> jussi01: plasma-netbook
[19:21] <shadeslayer> oh and if you boot the ISO, and the screen is small, it'll start plasma-netbook
[19:22] <jussi01> shadeslayer: the tech preview of active.... is it een worth considering for something that is actually usuable? or is it really just that, a tech preview?
[19:23] <shadeslayer> I wouldn't recommend it really
[19:23] <shadeslayer> just install kubuntu normally and then install active
[20:07] <ahoneybun> hey shadeslayer
[20:12] <soee> hey guys so are you leaving for now 4.10.3 because of some bug ?
[20:22] <ahoneybun> I think it is just taking time for it to compile
[20:22] <ahoneybun> but I'm not sure, I'll just let the Package Team take their time :)
[20:35] <yofel> well, soee's point is partly true
[20:35] <yofel> other than that people are busy with other things
[20:44] <ahoneybun> yofel: I would think so with the just released 13.04 and work for 13.10
[21:01] <ahoneybun> shadeslayer:
[23:27] <ahoneybun> should I keep a list of things left to do for the wiki?


[01:16] <tictacaddict> Hi, I want to write some code for unity, if I can just get as far as buiding it. :)
[01:16] <tictacaddict> I'm running Natty right now but a bug in bzr is keeping me from branching unity so far
[01:18] <spikeb> not sure if anyone but me is around, might want to check back during the day
[01:19] <tictacaddict> hmm, day in what timezone approximately?
[01:22] <spikeb> that i'm not sure..CST is mine.
[01:22] <spikeb> and one or two of the devs show up during the day,then the rest very late night (the london team, i assume)
[01:22] <spikeb> I think people are on holiday at the moment.
[01:23] <tictacaddict> ah, I suppose they would be. personally I'm trying to spend a little time on this because I have some extra holiday free time
[01:24] <spikeb> all I can do is tell you to keep checking in here every so often, somebody is bound to show up sooner or later
[01:24] <spikeb> or perhaps try the mailing list
[01:26] <tictacaddict> okay, I'll probably be back again. maybe I'll have more luck in a few days.
[01:26] <spikeb> I hope so, new contributors are always a good thing :)
[01:27] <tictacaddict> there is a fix out for the bug I'm seeing, so I might be able to just wait until it's packaged/
[01:27] <spikeb> cool
[01:27] <tictacaddict> @spikeb How are you involved with unity?
[01:27] <tictacaddict> or ubuntu etc
[01:28] <spikeb> tictacaddict, i'm a wannabe desginer. i help mostly by participating in design discussions on the mailing list. also, file bugs and whatnot for releases
[01:28]  * spikeb is pretty new at this whole game himself
[01:28] <tictacaddict> heh
[01:29] <tictacaddict> I've been using Ubuntu for a few years and have always been interested in helping somehow, just never dived in
[01:30] <spikeb> that was the case with me up until a few months ago, then i joined the ayatana mailing list and started learning a bunch of design related things. fast forward a bit and we are here.
[01:30] <tictacaddict> It seems like there is a big push to get new people involved with this project though, so it seemed like a good place to start
[01:30] <spikeb> yeah there is a huge push to get the community involved in Unity.
[01:31] <tictacaddict> seems like they can use all the help they can get, with the switch to unity for this cycle
[01:32] <tictacaddict> Seems like not everybody is happy about it at this point. :P
[01:32] <spikeb> they sure can
[01:32] <spikeb> who can blame them, after the disaster that is unity in 10.10? heh
[01:35] <tictacaddict> I never used it. I'm pretty much trying it out for the first time
[01:35] <tictacaddict> but from what I heard, yeah. there is some reason for concern
[01:36] <spikeb> however, the new Unity is already much better than the released version in 10.10. so I'm not overly concerned on that point.
[01:42] <tictacaddict> I guess it will be easy to switch back, but I hope that it's good enough by then that I won't want to. :)
[01:42] <tictacaddict> To a standard gnome desktop, I mean
[01:43] <spikeb> it will be easy to switch back (it'll be a login option). hopefully it will be good enough you wont want to :)
[01:44] <spikeb> if the progress already made this cycle is any indication, Unity will be in fine shape come release time.
[02:16] <tictacaddict> well I shall be back some other day. nice talking to you, spikeb
[02:17] <spikeb> tictacaddict, best of luck! :)
[02:18] <tictacaddict> thanks. :)
[06:08] <jderose> what is the proper way to update the text in an indicator MenuItem? (from Python)
[06:10] <jderose> MenuItem.get_child().set_text('foo') followed by Indicator.set_menu(menu) works, but causes a weird flashing when menu is visible
[09:36] <Devil505> hi
[12:54] <coz_> good day all
[14:21] <Devil505> http://www.techradar.com/news/software/operating-systems/the-evolution-of-the-linux-desktop-914736
[14:21] <Devil505> they're talking about ayatana :)
[14:23] <spikeb> cool
[15:23] <evilvish> Devil505: i guess you did not notice who wrote that article.. ;)
[15:32] <Devil505> evilvish, i don't know him
[15:36] <Amaranth> Devil505: That's jono, the head community guy with canonical and the awesome rock star
[15:36] <Devil505> oh
[18:12] <tictacaddict> any devs in the house?
[18:25] <coz_> tictacaddict,   I believe most are still on vacation
[18:30] <tictacaddict> coz_, know when they will be back?
[20:13] <nmarques> I've left a small bug-report for indicator-sound on: https://bugs.launchpad.net/indicator-sound/+bug/694828. Not sure if it helps upstream, but might be cool for downstreamers