 Fwd from nggraham: It would be really really great to get this in for Bionic: https://bugs.launchpad.net/ubuntu-rtm/+source/qtdeclarative-opensource-src/+bug/1761016
 Fwd from IrcsomeBot: <ubottu> Launchpad bug 1761016 in qtdeclarative-opensource-src (Ubuntu RTM) "cherry-pick https://codereview.qt-project.org/#/c/224684/ to fix image slideshows in KDE Plasma" [High,Confirmed]
 Fwd from nggraham: The Qt patch just landed in 5.11
 I can take care of it.
[18:31] <lisandro> tsimonq2: if you can also commit it in Debian. This is definitely bugging us all
[18:31] <lisandro> acheronuk: thanks for the update!
 @lisandro, Sure, should I prepare an upload for Sid?
[18:34] <lisandro> Yes please
 Will do in a few hours.
[18:34] <lisandro> Sure!
[20:06] <valorie> weeeeeeeee
[20:06] <valorie> it was biting me you-know-where


[18:41] <elbrus> rbasak: my proposal with respect to LP 1578144 would be to have cacti move to xenial-updates before we fix the next issue that popped up...
[18:42] <elbrus> with the current package in proposed, at least the package does reasonable things (albeit not everything)
[18:43] <elbrus> upstream didn't respond at all so far... slightly disappointing...
[22:28] <rbasak> elbrus: that sounds fine. I'm in regular touch with MySQL upstream if that'll help you?
[23:03] <worralph_> is it possible to have per subpackage conffiles?
[23:16] <rbasak> What's a subpackage?
[23:18] <worralph_> when you have one source package that is split into several other packages
[23:52] <rbasak> Oh, I see. One source package makes multiple binary packages. You're asking whether each binary can have its own conffiles? Yes. conffiles are defined in binary packages so that's the only way they actually happen anyway.


[14:22] <ikonia> guys what is the policy on using image (not icons) in wiki pages ? I can't find any wiki page that gives terms of use or how to use them ouside of icons
[21:51] <grndslm> Heya....
[21:51] <grndslm> anybody here know how I can get my Remastersys guide accepted to the Tutorials & Tips section of the forums??
[21:52] <grndslm> Here it is:  http://loscompanion.com/forums/index.php?topic=6456.0
[21:52] <grndslm> I've submitted it many times, but the forum never accepts it
[21:52] <grndslm> =-(


[02:33] <llol> hello folks what causes a WHITE BOX terminal after login
[02:33] <llol> ?
[02:33] <llol> just stays there like its crashed at one time it went thru
[02:37] <crimsun> well, I suppose it'd be helpful if you stuck around...
[06:13] <nomasteryoda> http://www.hemmy.net/2007/05/05/truth-happens-linux-ad/
[06:13] <nomasteryoda> check it out...
[06:15] <nomasteryoda> http://www.redhat.com/v/ogg/TruthHappens.ogg
[06:15] <nomasteryoda> the original
[10:07] <Cassano> so what new features is Gutsy gonna have?
[10:08] <ajmorris_> ooooh.... this new default font size looks awesome
[12:13] <borschty> what is the current conflict between scim and gtk packages, i can't find the dependency problem?


[02:51] <dutchie> Pendulum/AlanBell: i am around now
[02:51] <dutchie> (ish)
[02:51] <Pendulum> dutchie: I will poke you tomorrow
[02:52] <dutchie> that would probably be a good idea
[02:52] <dutchie> seeing as it is nearly 3 am now
[06:59] <AlanBell> student ^^
[07:57] <dutchie> AlanBell: :P
[07:57] <dutchie> student that is up at 8 nevertheless
[07:58] <nigelb> dutchie: I suspect he's in France.
[07:58] <dutchie> eh?
[07:59] <nigelb> aah
[07:59] <nigelb> dutchie: ah, sorry.  Confused :D
[08:00] <nigelb> dutchie: you slept at 3 and got up at 8? o.O
[08:01] <dutchie> i think that is due to the large amount of caffeine i consumed last night
[08:06] <nigelb> lol
[15:18] <Pendulum> oh, I said I'd blather about this here this morning since I ran out of time at the meeting last night
[15:19] <Pendulum> I've been beta testing an online cross-platform GUI mobile phone app development program
[15:19] <JackyAlcine> o.O
[15:19] <Pendulum> first app I decided to work on was for this team
[15:19] <Pendulum> I'm not sure if i'll publish it, but I wanted to let people know!
[15:20] <Pendulum> I realise it's a bit ironic to be doing an app about accessibility for a non-accessible platform using (currently) non-accessible software
[15:20] <Pendulum> but it was an easy thing for me to start with in terms of information and just doing something
[15:21] <JackyAlcine> hm. okay
[15:21] <Pendulum> anyway, http://community.spotspecific.com/boards/3/topics/5 is a little about I'm doing with a screenshot of the index for the app
[15:22] <Pendulum> if people are interested, I'll think about publishing once I have things perfect in it
[15:22] <Pendulum> for the record, using this software I can publish for both iPhone and Android
[15:24] <maco> Pendulum: iPhone isn't non-accessible
[15:24] <Pendulum> maco: no, but it's not wonderfully non-accessible
[15:24] <maco> or rather, it has some attempts at accessibility
[15:24] <maco> i am told it's pretty good if you're blind, much better than Android
[15:24] <maco> a kid at school was very excitedly showing me how well it worked for him
[15:25] <Pendulum> err... I mean not wonderfully accessible
[15:26] <Pendulum> I think TheMuso has been considering an iPhone
[15:26] <Pendulum> (I just vaguely remember a conversation about it at a UDS)
[15:27] <maco> i could imagine problems with multitouch for arthritis
[15:38] <Pendulum> I have to admit that for me, my iPhone is fabulous
[15:38] <Pendulum> and substantially more accessible for a lot of things compared to a regular phone
[15:38] <Pendulum> (big buttons, etc.)
[15:38] <Pendulum> but I also use a stylus part of the time (I'd really love a bulked up iPhone stylus that works)
[15:47] <maco> Pendulum: like the one that's pen-size with a brush tip instead of a little super-thin stick? thinkgeek has that...
[15:49] <Pendulum> I relaly need one thicker than that
[15:50] <Pendulum> *really
[15:50] <Pendulum> but I should try that one
[15:57] <Pendulum> Anyway, notice is now there that I'm working on this app (well, was working on it, now sitting on it) and if people want, I'll look into releasing it once I've gotten a chance to clean it up :)
[15:57] <Pendulum> also, Spot Specific is cool, but not accessible yet as far as I know (it's accessible if you can use a mouse, but I haven't really tested with a screen reader yet and it's all webkit, IIRC)
[16:16] <Pendulum> maco: do you have any tips about taking photos of signs? (this afternoon I'm going to be doing photos for a really simple ASL app which will be my next app after the Ubuntu Classroom one I'm working on now)
[16:17]  * AlanBell is doing a BSL app
[16:18] <maco> Pendulum: have a helper. running around to the other side of the camera or trying to aim it on a stand is not easy
[16:18] <maco> the best i can do without a helper is put a mirror behind the camera to check its aim
[16:22] <Pendulum> yeah, my mother's willing to help :)
[16:22] <Pendulum> any suggestions for background colour? I figure I'll be doing the signs infront of my so it's a "what colour t-shirt" question really
[16:23] <Pendulum> AlanBell: I suspect yours will be fancier than mine. I'm just doing an alphabet app with photos and no video
[16:23] <Pendulum> (so lots of screens, but nothing really fancy)
[16:24] <maco> one that contrasts with your skin :P
[16:24] <Pendulum> heh
[16:24] <maco> i dont think you're pale enough for white to be a problem
[16:24] <Pendulum> yeah
[16:24] <Pendulum> I might use blue
[16:24] <AlanBell> smile :)
[16:24] <Pendulum> since that's the colour of the current shirt I'm wearing :)
[16:24] <maco> but i guess one with not a lot of writing would be good
[16:24] <Pendulum> yeah
[16:25] <maco> AlanBell: heh. just dont smile when teaching the sign for "kill" or "murder" or "die" :P
[16:25] <Pendulum> current tshirt is plain blue
[16:25] <maco> huh. should maybe have a "crimes" lesson in gally?
[16:25] <maco> i just know kill & steal
[16:25] <AlanBell> you don't have a #dd4814 tshirt yet then?
[16:27] <AlanBell> I just know rude signs from that Cee Lo Green song
[16:31] <Pendulum> AlanBell: I will never by choice have a #dd4814 shirt
[16:31] <Pendulum> in fact, I might chance the a11y background colour to #d05630 just because it gives me less of a headache
[16:32] <maco> AlanBell: the funny thing about the cee lo green song in ASL video everybody's all "zomg" about is that ITS NOT EVEN THE RIGHT SIGN
[16:32] <Pendulum> er... a11y app
[16:32] <Pendulum> maco: okay, I wondered about that because it's a different sign from the one I was taught
[16:32] <maco> the sign she's doing is "so what?"
[16:32] <Pendulum> I assumed it was regional variance
[16:32] <Pendulum> but the video is awesome for othe reasons :)
[16:33] <maco> i saw a theory that she had picked it up from a BSL video
[16:33] <maco> either that, or she watches too many mafia movies (that was my theory)
[16:33] <Pendulum> haha
[16:34] <Pendulum> maco: actually looking at wikipedia, she got it from there: http://en.wikipedia.org/wiki/Profanity_in_American_Sign_Language
[16:34] <maco> such a page exists? O_o
[16:35] <maco> Pendulum: did didnt read the third sentence
[16:35] <maco> s/did/and/
[16:35] <Pendulum> right
[16:36] <maco> interesting.... i learned what i assume is regional variation on BS
[16:36] <maco> i learned thumb & pinkie
[16:37] <maco> im having trouble differentiating their explanation of "slut" from the sign for girl :-/
[16:38] <AlanBell> I saw a little bit of Glee the other day (by accident, the TV was on and I walked past) and they were doing that song but with "forget you" as the line
[16:38] <Pendulum> AlanBell: that's the radio edit version
[16:39] <maco> if i was signing that song, id sign those two words individually
[16:39] <maco> itd go better with the rhythm anyway
[16:39] <AlanBell> go for it :)
[16:39] <Pendulum> maco: I think it's a matter if distance. I was taught girl came from up near the ear, where slut seems to be just the chin
[16:39] <maco> heh i dont know the rest of the signs, and songs are the hardest thing to interpret
[16:40] <maco> Pendulum: ah ok
[16:40] <maco> for a while i had menstruate and girl mixed up. oops
[17:19] <charlie-tca> Wonderful, they want to make launchpad match the guidelines used for www.ubuntu.com.
[17:19] <charlie-tca> let's get something else half of us can not use
[17:20] <AlanBell> charlie-tca: link?
[17:21] <charlie-tca> http://blog.launchpad.net/general/launchpads-ui-is-evolving
[17:22] <Pendulum> charlie-tca: I have a contact person about launchpad issues so I'll start poking now if someone gives me a good explanation I can give to him
[17:23] <Pendulum> (or just a list of issues for me to explain to him)
[17:23] <Pendulum> interested that they mentioned accessibility in the post, though
[17:23] <charlie-tca> orange banner and links, footer that is unreadable if the text size is changed by the user,
[17:23] <Pendulum> charlie-tca: can you e-mail it to me?
[17:23] <Pendulum> (sorry in the middle of something else)
[17:23] <charlie-tca> Yeah, you do know they changed the main website so it is more accessibile, right?
[17:23] <Pendulum> yes
[17:24] <Pendulum> this is why I want to know what the issues are *now* rather than what they used to be :)
[17:24] <charlie-tca> I just looked at the website, I still am missing most links in the footer if I grow the text to a size I can read
[17:25] <charlie-tca> To make them all visible requires a 8pt or smaller font
[18:02] <maco> O_o
[18:02] <maco> charlie-tca: why do they go invisible if made big?  overflow=none ?
[18:03] <charlie-tca> When the page is made with big text, using Ctrl+, the links disappear, they seem to be hiding behind each other or something
[18:04] <charlie-tca> If you make the page tiny, using Ctl - , you see many more than when the text is made big. Unfortunately, the entire page grows and shrinks with the text, making it pretty hard to see
[18:05] <charlie-tca> It is a fixed width, fully shrinkable page
[18:06] <maco> charlie-tca: on what browser?
[18:06] <maco> i just zoomed in as far as firefox would let me. i have to scroll left and right to see them all, but nothing seems to be *gone*
[18:08] <charlie-tca> maco: screenshot at http://imagebin.org/138439
[18:08] <charlie-tca> What is under Trademark policy?
[18:09] <charlie-tca> How about the line under Get Ubuntu ????
[18:09] <charlie-tca> there are at least two lines of links missing
[18:10] <maco> i see this http://imagebin.org/138440
[18:11] <maco> and so i suspect browser rendering bug
[18:11] <charlie-tca> I can reproduce it on both firefox 4.0 in natty and 3.6.13 in lucid
[18:11] <charlie-tca> on two different computers
[18:12] <maco> im on 3.6.13 in maverick
[18:12]  * AlanBell tries in natty
[18:12] <maco> it ools like on yours it's zooming *just* the text, not the page
[18:12] <maco> which is rather weir
[18:12] <maco> *weird
[18:12] <maco> so the boxes the text is in are running out of space to hold the now-bigger text
[18:13] <maco> s/ools/looks/
[18:13] <AlanBell> works for me
[18:13] <maco> but i have no idea why only your text zooms without the rest of the page
[18:13] <AlanBell> if you go view-zoom-zoom text only then it zooms text only
[18:13] <AlanBell> untick that and it zooms the page
[18:13] <maco> oh. its optional?
[18:14] <AlanBell> default is unticked
[18:14] <maco> well the way to fix this so that making just text bigger doesnt break shit would be to make the divs sizes be set in ex's and em's
[18:14] <maco> erm
[18:14] <maco> i mean doesnt break stuff!
[18:14] <charlie-tca> Ctrl -  shrinks it like http://imagebin.org/138441
[18:15] <maco> and i have to *pout* at the fact that changing base font size in ff doesnt change the fonts in ubuntu.com....because theyre using px instead of em's grrrr
[18:15] <charlie-tca> zoom text only is not checked
[18:15] <charlie-tca> Looking at the two images, I conclude the page is growing and shrinking
[18:17] <AlanBell> maco: thanks to 960.gs designer types have fallen in love with pixels all over again
[18:17] <charlie-tca> I avoid the website as much as possible, since I can't see all of it
[18:18] <charlie-tca> When they do that to launchpad, I guess my contributions are going to be much less
[18:18] <AlanBell> there is a new style guide on photography and beard maintenance http://design.canonical.com/brand/10.%20Photography%20treatments.pdf
[18:19] <Cheri703> heh, I'm guessing that was supposed to say brand, but I'm chuckling about a style guide on beard maintenance :D
[18:19] <AlanBell> I meant beards :)
[18:21] <Cheri703> :)
[18:21] <AlanBell> see what I mean!
[19:01] <Pendulum> UDS Diversity meeting (aimed at women) taking place right now in #ubuntu-women-project
[21:37] <JackyAlcine> If this interests anyone, we're working to add speech synthesis to Chromium.
[21:37] <JackyAlcine> https://www.launchpad.net/browserspeak
[21:37] <JackyAlcine> A work in progress.
[22:44] <TheMuso> Pendulum: YES I IN FACT GOT AN IPHONE, TRUMPS EVERYTHING ELSE SMART PHONE WISE WITH DEACENT ACCESSIBILITY AT THE MOMENT.
[22:45] <maco> TheMuso: your caps lock is on
[22:45] <maco> TheMuso: woah hey....does your screen reader shout when it encounters caps?
[22:46] <TheMuso> Heh yeah it does, and thanks for the heads up, there is a bug with Orca's capslock stuff atm, I am on a notebook atm.
[22:46]  * TheMuso should really dig through git to see if there is a fix upstream for that already, and apply it.
[22:46] <maco> well i figured it's not like you can tell from looking at the screen when it's on
[23:06] <AlanBell> maco: http://people.ubuntu.com/~alanbell/spotapp.png
[23:12] <maco> AlanBell: nice
[23:12] <maco> AlanBell: pretty please could you make some photos for BSL for gally?
[23:12] <maco> i need to write in support for more langs, but i also need langs with which to test!
[23:20] <AlanBell> I have a friend I can ask
[23:21] <AlanBell> I don't know it at all so I would be copying the diagrams, no idea if I was doing it wrong
[23:30] <maco> ok


[02:09] <ahoneybun> pleia2: ping
[02:17] <pleia2> ahoneybun: hey
[02:26] <ahoneybun> pleia2: I'll be rockin my ubuntu 14.04 tshirt the first day!
[02:26] <pleia2> \o/
[02:26] <pleia2> I never got one
[02:27] <ahoneybun> its my first tshirt
[02:27] <pleia2> :)
[02:27] <ahoneybun> when though I'm rocking manjaro kde right now lol
[02:27] <ahoneybun> https://plus.google.com/photos?pid=6009238434492873602&oid=110525358571541799848
[02:28] <pleia2> no worky
[02:29] <ahoneybun> the link
[02:29] <ahoneybun> ?
[02:29] <pleia2> yeah
[02:30] <ahoneybun> darn well you'll hopefully see me in it thursday
[02:30] <pleia2> yeah :)
[02:30] <ahoneybun> darn well you'll hopefully see me in it thursday 18 hours up
[02:31] <pleia2> haha
[02:31] <ahoneybun> well off to netflix
[02:31] <pleia2> enjoy
[02:31]  * pleia2 heads off for the evening as well


[01:05] <sandy|lurk> what happened to the ubuntuone-servers package?
[01:05] <sandy|lurk> how do I file a bug against the U1 server?
[01:05] <beuno> sandy|lurk, still there, same place
[01:05] <sandy|lurk> hmm, I am not sure what I'm doing wrong then
[01:06] <sandy|lurk> trying to change this bug to ubuntuone-servers https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/670478
[01:06] <ubot4> Launchpad bug 670478 in tomboy (Ubuntu) "tomboy fails to sync notes to ubuntuone (500 internal server error) (affects: 1) (heat: 6)" [Undecided,New]
[01:06] <beuno> sandy|lurk, https://launchpad.net/ubuntuone-servers
[01:06] <beuno> sandy|lurk, right
[01:06] <beuno> it's not a package
[01:06] <sandy|lurk> beuno, so how do I transfer the bug?
[01:06] <beuno> sandy|lurk, "Also affects project"
[01:09] <sandy|lurk> beuno, thanks
[01:09] <sandy|lurk> took a few too many steps to remove Tomboy from there
[01:09] <sandy|lurk> but makes sense in a Launchpad sort of way :-P
[01:09] <beuno> sandy|lurk, yeah, the interaction there is a bit awkward
[15:40] <duanedesign> afternoon all
[16:20] <SpamapS> o/
[16:20] <joshuahoover> SpamapS: hello
[16:21] <SpamapS> so, the scenario is simple really.
[16:21] <SpamapS> I marked one folder in my home dir for sync to ubuntuone
[16:21] <joshuahoover> SpamapS: so we have 2 problems here...one is the annoying pop-up that i think we have a bug for...but i don't have handy
[16:21] <SpamapS> it has 4.3GB of pictures in it
[16:22] <SpamapS> Every so often (maybe every 12 hours?) it pops up and tells me that I'm Out of space
[16:23] <SpamapS> when it does that, it does it in a really weird annoying way that tends to pop windows up and close them at an alarming rate, which makes X basically completely non responsive.
[16:23] <joshuahoover> SpamapS: the 2nd problem is you need more space on your account, that problem should now be fixed
[16:23] <mattgriffin> SpamapS: so the folder you are trying to sync already has more than 2 GB in it
[16:24] <SpamapS> joshuahoover: haha but I don't want more space, I want U1 to be t3h awesome... this is not t3h awesome. This is not web scale. ;)
[16:24] <SpamapS> mattgriffin: yes. the folder has always had too much data in it.
[16:24] <joshuahoover> SpamapS: heh, right...the bug needs fixed
[16:24] <SpamapS> (btw, that would be a cool feature.. "You are trying to sync 4.3GB into your 2GB account, are you sure you want to do this?"
[16:26] <mattgriffin> SpamapS: for 11.04, we will have a way to notify you on your desktop with info about what's happening with sync. this sounds like a scenario that we should re-evaluate our current functionality and consider integrating with the new notification ability
[16:26] <joshuahoover> SpamapS: so the bug needs fixed and, if you really want to sync more than 2 GB you need more space, which you now have
[16:27] <SpamapS> joshuahoover: Cool thanks for that...
[16:27] <SpamapS> do you guys get that its not just that its nagging me.. its that it makes my system unusable for 30+ seconds?
[16:29] <SpamapS> Yeah U1 should totally just use the panel. Pop ups are like, 1998 tech. ;)
[16:29] <joshuahoover> SpamapS: yep, i understand...i'm checking for the bug now and making sure we have it on the list to get in for an sru
[16:31] <SpamapS> I'll drop my "this affects me too" $0.02 in there as well.
[16:32] <SpamapS> its also weird that whenever I type 'apport-bug ubuntuone-client' it takes me to some old bug that is claimed to have been fixed.
[16:37] <joshuahoover> SpamapS: bug #650671
[16:37] <ubot4> Launchpad bug 650671 in ubuntuone-client (Ubuntu) "UbuntuOne "out of space" dialog is broken (affects: 2) (heat: 10)" [High,Confirmed] https://launchpad.net/bugs/650671
[16:44] <SpamapS> alright, threw my "this affects me" hat into the ring
[16:51] <joshuahoover> SpamapS: think you can reproduce this bug for me? if so, i'd like to have you turn debug mode on for u1 and try again, then attach the log files to the bug
[16:55] <SpamapS> joshuahoover: well now I have 50GB of space.. so I'm not sure if I can. ;)
[16:55] <joshuahoover> SpamapS: right, i can try to reproduce here on a test vm
[16:55] <joshuahoover> SpamapS: you were connected to u1 when you did this?
[16:56] <SpamapS> joshuahoover: if by connected you mean I had my account details entered in the preferences, yes.
[16:56] <SpamapS> Everything worked awesome until it ran out of space. :)
[16:56] <joshuahoover> SpamapS: sorry, i meant, were you connected to the server in ubuntuone-preferences, in the devices tab?
[16:57] <SpamapS> joshuahoover: I don't think I ever looked in the devices tab.
[16:57] <SpamapS> Right at this moment though, it shows the current machine and one other that I connected a while back.
[16:58] <joshuahoover> SpamapS: ok, i should be able to reproduce this fairly easily...updating my vm and then will see what i can do :)
[16:58] <SpamapS> joshuahoover: One sticky detail may be that I originally installed using Xubuntu 10.10, and then switched it to regular Ubuntu by apt-get installing ubuntu-desktop. It might be that there is something seeded in Ubuntu that doesn't get pulled in by ubuntu-desktop.
[16:59] <joshuahoover> SpamapS: that shouldn't matter
[20:33] <iheartubuntu> hi all! Are there any U1 updates coming soon? U1 does not work for me still. I have the U1 indicator and Magicicada and nothing wants to connect. I cannot use my Tomboy notes anymore now either. Any help would be so greatly appreciated.
[20:34] <duanedesign> iheartubuntu: are you runnning Maverick
[20:34] <iheartubuntu> Yes. Hi Duane, you have helped me before :)
[20:35] <duanedesign> iheartubuntu: can you open a Terminal and run:  u1sdtool -s
[20:35] <duanedesign> and post what it says?
[20:36] <iheartubuntu> http://paste.ubuntu.com/525949/
[20:36] <duanedesign> ok
[20:37] <duanedesign> iheartubuntu: can you run: u1sdtool -q
[20:37] <iheartubuntu> my computer is smoking now
[20:37] <iheartubuntu> just kidding :)
[20:37] <duanedesign> :)
[20:37] <duanedesign> did it say ubuntuone-syncdaemon stopped.
[20:38] <iheartubuntu> ubuntuone-syncdaemon still running
[20:38] <iheartubuntu> i think syncdaemon is always running
[20:39] <iheartubuntu> not sure on that though
[20:39] <iheartubuntu> i have been trying to get magicicada working
[20:39] <duanedesign> can you try -  killall ubuntuone-syncdaemon; killall ubuntu-sso-login
[20:39] <iheartubuntu> and the U1 indicator too. they both just sit there.
[20:39] <iheartubuntu> gladly :)
[20:40] <iheartubuntu> i now have "dbus-daemon" maxing out my cpu
[20:40] <iheartubuntu> now ubuntuone-indiactor is coming back on
[20:41] <iheartubuntu> now cpu is normal
[20:42] <duanedesign> iheartubuntu:  can you run u1sdtool -s
[20:43] <iheartubuntu> a couple of weeks ago i was here talking to rye and it appeared i had a bug on bootup with U1 loading. not sure what happened to that bug. i would be happy to manually turn on U1 every morning if it would work
[20:44] <iheartubuntu> same error as before
[20:44] <iheartubuntu> Oops, an error ocurred:
[20:44] <iheartubuntu> Traceback (most recent call last):
[20:44] <duanedesign> ok can you quit the indicator
[20:44] <iheartubuntu> Failure: dbus.exceptions.DBusException:
[20:44] <duanedesign> i think it would be killall ubuntuone-indicator
[20:45] <iheartubuntu> ok. got it
[20:45] <iheartubuntu> now i retried "u1sdtool -s"
[20:45] <iheartubuntu> State: LOCAL_RESCAN
[20:45] <iheartubuntu>     connection: Not User With Network
[20:45] <iheartubuntu>     description: doing local rescan
[20:45] <iheartubuntu>     is_connected: False
[20:45] <iheartubuntu>     is_error: False
[20:45] <iheartubuntu>     is_online: False
[20:45] <iheartubuntu>     queues: WORKING_ON_BOTH
[20:45] <duanedesign> ok
[20:46] <duanedesign> can you try -  u1sdtool -c
[20:47] <iheartubuntu> ok, it brought me back to terminal prompt
[20:49] <iheartubuntu> i notice "ubuntuone-syncdaemon" is listed as uninterruptible
[20:50] <duanedesign> iheartubuntu: ok, can you try u1sdtool -s
[20:51] <iheartubuntu> i just went into my me menu and to the U1 preferences
[20:51] <iheartubuntu> now it says sync in progress
[20:51] <iheartubuntu> State: QUEUE_MANAGER
[20:51] <iheartubuntu>     connection: With User With Network
[20:51] <iheartubuntu>     description: processing queues
[20:51] <iheartubuntu>     is_connected: True
[20:51] <iheartubuntu>     is_error: False
[20:51] <iheartubuntu>     is_online: True
[20:51] <iheartubuntu>     queues: WORKING_ON_BOTH
[20:57] <iheartubuntu> So I should do the killall commands? then do the u1sdtool commands, then go into the U1 preferences to hopefulyl kickstart it?
[20:57] <duanedesign> no
[20:57] <duanedesign> iheartubuntu: it is working
[20:57] <iheartubuntu> I mean to get it going each day
[20:58] <duanedesign> oh sorry
[20:58] <duanedesign> :P
[20:58] <duanedesign> ththere might be a bug in the indicator..
[20:59] <iheartubuntu> for sure dont use that one
[20:59] <duanedesign> if you open the Preferences, Connect, then after it is connected try the indicator.
[21:00] <iheartubuntu> what does "u1sdtool -c" do? and also the -s?
[21:00] <duanedesign> u1sdtool -c is connect
[21:00] <iheartubuntu> ahh! ok
[21:01] <duanedesign> the same as pushing connect in the Preferences
[21:01] <duanedesign> u1sdtool -q is quit
[21:01] <duanedesign> u1sdtool -s is status
[21:01] <iheartubuntu> I think they work better from the command line :)
[21:01] <duanedesign> if yo look at u1sdtool -s a lot you will start to get used to what the different status means
[21:01] <iheartubuntu> errr... terminal
[21:01] <duanedesign> if you notice in the two you posted
[21:02] <duanedesign> the first one said Not user With Network
[21:02] <iheartubuntu> it looks like everything is working :)
[21:02] <duanedesign> and thesecond said With User With Network
[21:03] <iheartubuntu> my tomboy doesnt sync. should i wait for all files to download first?
[21:03] <rye> could somebody please test "/me something" line ?
[21:03] <duanedesign> have you authorized tomboy seperately from Ubuntu One
[21:03] <duanedesign> rye: hello
[21:03]  * iheartubuntu is testing it
[21:04] <iheartubuntu> i authorized tomboy in tomboy to use U1
[21:04] <rye> duanedesign, hi! Finally, I fixed xchat-gnome translation... woo-hoo!
[21:04] <duanedesign> iheartubuntu:/8
[21:04] <duanedesign> oops
[21:10] <iheartubuntu> thanks so much for the help duane!
[21:10] <iheartubuntu> im going to reboot and watch how my computer behaves
[21:10] <duanedesign> i am glad i could help
[21:30] <iheartubuntu> :|
[21:30] <iheartubuntu> hello duane :)
[21:31] <iheartubuntu> after reboot nothing happens. i proceed to killall, then quit, then connect and still nothing
[21:32] <iheartubuntu> should i wait a period of time for things to happen?
[21:32] <iheartubuntu> i notice i get a dbus error if i try to connect to quickly.
[21:33] <iheartubuntu> i have just waited a few minutes and now it connected
[21:33] <iheartubuntu> it is working once again, but im not sure how it dos it
[21:33] <iheartubuntu> *does
[21:34] <iheartubuntu> the tomboy notes synced up perfectly. upon connection to U1
[21:34] <iheartubuntu> :)
[21:54] <rye> iheartubuntu, ubuntoune connects after 30 seconds from the login time
[22:02] <iheartubuntu> what about after i killall it will come back in 30 seconds?


[12:46] <maks_piechota> Hi guys, do you know if Ubiquity project has its own irc channel? I have few question regarding building it


[00:01] <Quintasan> shadeslayer: http://wstaw.org/m/2012/12/22/plasma-desktoprD2665.png
[00:01] <Quintasan> sup
[00:01] <shadeslayer> :D
[00:02] <ScottK> shadeslayer: re kraft: Don't update standards version in Ubuntu relative to what Debian has.  It's pointless diff in Ubuntu and Ubuntu policy says not to.
[00:02] <Quintasan> woah
[00:02] <shadeslayer> oh
[00:02] <Quintasan> 12.10 has LVM in options?
[00:02] <shadeslayer> ScottK: we have a policy for that?
[00:02] <shadeslayer> Quintasan: heh yeah
[00:02] <shadeslayer> Riddell got it in :P
[00:02] <ScottK> Yes.
[00:03] <shadeslayer> okay, I'll keep that in mind, want me to re-upload? ( just needs fixing of control and changelog though )
[00:03]  * ScottK fixed locally already.
[00:03] <ScottK> No need
[00:03] <shadeslayer> oh thx :)
[00:04] <shadeslayer> there wasn't anything involved in updating the policy from what I could tell, so I bumped it
[00:04] <Quintasan> I'm surprised I can read this shadeslayer
[00:05] <Quintasan> but this
[00:05] <Quintasan> http://wstaw.org/m/2012/12/22/plasma-desktopMk2665.png
[00:05] <Quintasan> gotta loved mixed translations
[00:05] <ScottK> shadeslayer: Right, but there's a general policy of not updating because it just makes more diff that we don't care about.
[00:05] <shadeslayer> ScottK: Understood.
[00:05] <ScottK> shadeslayer: BTW, ask about such packages in #ubuntu-motu so we can get you more visibility there. (in the future)
[00:05] <shadeslayer> Quintasan: hehe
[00:06] <shadeslayer> ScottK: okie
[00:06]  * shadeslayer sucks at making himself visible
[00:06] <shadeslayer> even stopped blogging :P
[00:07] <Quintasan> shadeslayer: oh yea
[00:07] <Quintasan> dude
[00:07] <Quintasan> check query
[00:08] <Riddell> Quintasan: awooga
[00:08] <Riddell> shadeslayer: got what in?
[00:09] <shadeslayer> Riddell: kde-workspace 4.9.95/raring
[00:09] <Quintasan> Riddell: awooga about what?
[00:09] <ScottK> shadeslayer: Uploaded.  Thank you for your contribution to Ubuntu.
[00:11] <Riddell> Quintasan: awooga for wanting to look into input methods
[00:11] <Quintasan> mmkay
[00:12] <shadeslayer> ScottK: thx :)
[00:15] <yofel> uh...
[00:16]  * yofel wanted to check if software-properties-kde works right with py3 and got this instead:
[00:16] <yofel>   File "/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py", line 38, in <module>
[00:16] <yofel>     from PyKDE4.kdecore import ki18n, i18n, KUrl
[00:16] <yofel> RuntimeError: the sip module implements API v9.0 but the PyKDE4.kdecore module requires API v9.1
[00:16] <yofel> I need sip from proposed?
[00:18] <Riddell> ScottK: uploaded
[00:18] <ScottK> yofel: Probably.
[00:19] <ScottK> I'll unblock it.
[00:19] <ScottK> PyQt is taking longer than i expected.
[00:20] <yofel> yep, that worked
[00:20] <ScottK> Done.
[00:27] <ScottK> Riddell: "For details see the accompanying COPYING-CMAKE-SCRIPTS file."  cmake-modules/* in kajongg is BSD license.
[00:27] <ScottK> And said license is missing ...
[00:39] <Quintasan> apachelogger: ping
[00:40] <Quintasan> ScottK: You know C well?
[00:40] <ScottK> Quintasan: Not at all.
[00:40] <Quintasan> hmm
[00:40] <Quintasan> Riddell: You?
[00:48] <yofel> Quintasan: what's the question anyway?
[00:49] <Quintasan> yofel: http://sequoia.ict.pwr.wroc.pl/~mucha/PProg/wyklad07_prezentacja.pdf
[00:49] <Quintasan> go to page 63
[00:49] <Quintasan> what the hell
[00:49] <Quintasan> int (*piksele)[obraz->wym_x];
[00:49] <Quintasan> piksele=(int(*)[obraz->wym_x]) obraz->piksele; /*inicjujemy go jak trzeba*/
[00:49] <Quintasan> do?
[00:49] <Quintasan> ignore the comments since they are in polish
[00:50] <Quintasan> yofel: The whole thing apparently creates a dynamicall two dimensional array
[00:53] <Quintasan> it seems I killed yofel with that
[00:53] <Quintasan> :P
[00:54] <yofel> not really, I'm just getting confused by all the polish
[00:54] <Quintasan> ignore the comments
[00:54] <Quintasan> they really don't say anything
[00:54] <yofel> int (*piksele)[obraz->wym_x]; should be -> piksele defined as pointer to int array with obraz->wym_x elements
[00:55] <yofel> the next line is a "simple" type cast
[00:55] <yofel> defining the data type for the malloc a few lines above
[00:56] <Quintasan> shadeslayer: see this?
[00:56] <Quintasan> he knows his stuff
[00:56] <yofel> but I'm still wondering about the 2-dimensionality
[00:57] <shadeslayer> yofel: inorite
[00:57] <Quintasan> oh
[00:57] <Quintasan> that's the thing
[00:57] <shadeslayer> as for int (*piksele)[obraz->wym_x] I've never written such code :P
[00:57] <shadeslayer> silly C
[00:57] <Quintasan> yofel: Basically he is importing an pbm image
[00:57] <Quintasan> wymX would be resolutionX
[00:57] <Quintasan> and wymY -> resolutionY
[00:57] <Quintasan> obraz -> picture
[00:58] <shadeslayer> and what yofel said makes sense now :P
[00:58] <Quintasan> if you scroll up
[00:58] <Quintasan> you can see it done ez mode i.e static array
[00:58] <shadeslayer> ohhh
[00:58] <shadeslayer> ohhhh okay
[00:59] <Quintasan> and the next excerices ask you to rewrite the previous app you were supposed to do
[00:59] <Quintasan> using dynamical array
[00:59] <Quintasan> dynamical 2d array ofc
[00:59] <Quintasan> and I was like
[00:59] <Quintasan> how the hell does this even work
[01:00] <Quintasan> how is this stuff creating twodimensional array?
[01:00] <Quintasan> I can see one dimension there
[01:00] <yofel> nah, it's using one malloc to allocate the space for the whole 2-dim array and later defines the types to slice it into pieces
[01:01] <Quintasan> for all I see he iterates through piksele like a 2d array
[01:02] <shadeslayer> *nod*
[01:02] <yofel> well, yeah
[01:03] <shadeslayer> yofel: though isn't piksele a 1d array?
[01:03] <Quintasan> I think the array doesn't know it yet :P
[01:03] <shadeslayer> hah
[01:03] <yofel> not really, it's an array of 1d arrays
[01:04] <shadeslayer> uhhhh
[01:04] <yofel> int (*piksele)[obraz->wym_x];
[01:04] <shadeslayer> does not compute
[01:04] <Quintasan> yeah
[01:05] <yofel> hm wait, how do I explain this correct
[01:05] <Quintasan> don't ask US that :P
[01:05] <shadeslayer> afaictl that defines an array of pointers
[01:05] <shadeslayer> of length obraz->wym_x
[01:05] <Quintasan> apachelogger: halp
[01:06] <yofel> I read that as a pointer to an array of int
[01:06] <Quintasan> I read that as a mindfuck (excuse the poor wording) for new students
[01:06] <yofel> which defines that 2nd dimension
[01:06] <shadeslayer> :D
[01:07] <Quintasan> yofel: Note this is apparently from my friends "introduction to programming" course :D
[01:07] <Quintasan> 7th lecture I think
[01:07] <shadeslayer> I really do fail to see the 2nd dimension there :P
[01:07] <yofel> Quintasan: this *IS* introductory material for C
[01:07]  * yofel wished he had C at uni -.-
[01:08] <yofel> shadeslayer: the next line does that I believe - it tells it that the allocated space is of 'arrays of int with size obraz->wym_x size' type
[01:08] <Quintasan> I don't think this is something to do at 7th lecture whne you spend two lectures introducing X window system
[01:08] <yofel> that will make the for loop skip exact the amount of bytes for one int array on i++
[01:09] <yofel> Quintasan: welcome to uni ;P
[01:09] <Quintasan> I wish I had this stuff instead of JAva
[01:09] <Quintasan> People who go to IT course have Java
[01:09] <Quintasan> and people who went for automation and robotics have C
[01:09] <Quintasan> the hell
[01:10] <yofel> well, that's what I saw in the company introductions here too, the electronics folk use C, the IT companies Java
[01:11] <yofel> so that's pretty close to reality
[01:11] <shadeslayer> that's normal actually :P
[01:11] <shadeslayer> Quintasan: thank god you're not learning verilog/VHDL
[01:11] <shadeslayer> I cannot parse that stuff no matter how hard I tried
[01:11]  * yofel dropped out before he got to VHDL...
[01:12] <shadeslayer> I did basic VHDL
[01:12] <shadeslayer> designed Flip Flops and switches
[01:12] <shadeslayer> mux's
[01:12] <Quintasan> WTF
[01:12] <yofel> Quintasan: do you know how C handles looping through malloc'd arrays?
[01:12] <Quintasan> is this
[01:12] <yofel> or how that loop works?
[01:12] <yofel> because it cares about the data type there
[01:12] <Quintasan> yofel: I think this would be called pointer arithmetic?
[01:13] <yofel> yes, but the pointer arithmetic does an automatic multiplication of the index with sizeof(datatype)
[01:13] <Quintasan> i.e by +1 it jumps X bytes where X is the number of bytes that certain data type uses?
[01:13] <shadeslayer> piksele=(int(*)[obraz->wym_x]) obraz->piksele < that to me reads as : the pointer to the first element in an array of length wym_x sliced off from obraz->piksele
[01:13] <yofel> that's why the typecast is in there
[01:14] <Quintasan> oh christ
[01:14] <yofel> shadeslayer: no
[01:15] <Quintasan> what is this I don't even
[01:15] <yofel> the pointer to the first element of data that is of type "int array of size wym_x"
[01:15] <Quintasan> WHAT IS THIS VHDL
[01:15] <Quintasan> TAKE IT AWAY
[01:15] <yofel> shadeslayer: so piksele[0] would indeed be the first int array
[01:15] <yofel> piksele[1] will be the next
[01:15] <shadeslayer> I see
[01:16] <shadeslayer> but then can you resolve piksele[0][1]
[01:16] <yofel> that would be bytes 4-7
[01:16] <shadeslayer> and shouldn't it be : ( piksele[0])[1]
[01:16] <shadeslayer> oh, so that does resolve? I didn't think it could
[01:17] <Quintasan> Riddell: I'll be perfectly honest
[01:17] <Quintasan> Fresh quantal install has nothing
[01:17] <Quintasan> nothing
[01:17] <shadeslayer> which is why I was confused
[01:17] <Quintasan> that looks like japanese input
[01:17] <yofel> it knows that piksele[0] is the first element, and since it knows the data type of that element it knows that [1] is the 2nd int in there
[01:17] <shadeslayer> smart ass compiler
[01:18] <shadeslayer> the code makes sense now I think :P
[01:18] <yofel> since it knows the data type, it knows that piksele[1] is *piksele + sizeof(that data type)
[01:18] <shadeslayer> right
[01:18] <shadeslayer> and we told it that data type when we added this : piksele=(int(*)[obraz->wym_x]) obraz->piksele
[01:19] <yofel> that code is nice, but that's really not the way I'm used to doing it
[01:19] <yofel> as usually you would replace one of that lines by simply using calloc()
[01:20] <Quintasan> how the hell does piksele[0][1] resolve then?
[01:20] <shadeslayer> Quintasan: yofel just explained that
[01:21] <Quintasan> so wait
[01:21] <yofel> hm...
[01:21] <Quintasan> If I understood it correctly
[01:22] <Quintasan> piksele[0] is not an int but an array of ints?
[01:22] <shadeslayer> yofel: C is more convoluted than I thought it was
[01:22] <shadeslayer> Quintasan: piksele is an array of pointer to arrays
[01:22] <Quintasan> array of pointers
[01:22] <Quintasan> okay
[01:22] <Quintasan> that computes
[01:22] <Quintasan> to arrays
[01:22] <Quintasan> okay
[01:22] <shadeslayer> right
[01:22] <Quintasan> that computes as well
[01:22] <yofel> not really
[01:23] <shadeslayer> whut? 0.o
[01:23] <yofel> you never allocated space for the pointers
[01:23] <Quintasan> XD
[01:23] <shadeslayer> heh
[01:23] <yofel> it's a pointer to an array of arrays
[01:23]  * Quintasan 's brain explodes
[01:23] <shadeslayer> oic
[01:23] <yofel> it can't be anything else as you only have one variable and one slice of memory
[01:23] <shadeslayer> yofel: also, that's just shitty :P
[01:23] <Quintasan> yofel: SO piksele[0] (the first element) is a array of ints?
[01:24] <Quintasan> and piksele[1] would be another array of its?
[01:24] <yofel> shadeslayer: well, that's a pretty sane way to implement a 2-dim dynamic array in C IMHO ^^
[01:24] <Quintasan> ints*
[01:24] <yofel> Quintasan: right
[01:24] <Quintasan> holy shit
[01:24] <Quintasan> is it any different from
[01:24] <Quintasan> tab[100][100]?
[01:25] <shadeslayer> yofel: what if the resolution is more? :P
[01:25] <yofel> not really, but what memory address that resolves to is a matter of types
[01:25] <shadeslayer> erm
[01:25] <shadeslayer> Quintasan: ^
[01:25] <Quintasan> shadeslayer: I don't care
[01:25] <Quintasan> I wanted to know if it's different memory wise
[01:26] <shadeslayer> Quintasan: welcome to the world where people have images of different resolutions :P
[01:26] <shadeslayer> Quintasan: sure it is
[01:26] <Quintasan> that magic with wymX and wymY = 100 vs. int tab[100][100]
[01:26] <shadeslayer> then it's not
[01:26] <shadeslayer> but what if wymX and wymY are 50
[01:26] <yofel> well, I'm not sure, but wouldn't tab[100][100] be on the stack and not on the heap?
[01:26] <shadeslayer> then you're wasting half the space with a static array
[01:26] <Quintasan> they will be different duh
[01:26] <shadeslayer> yofel: that too
[01:26] <Quintasan> because they have different dimensions?
[01:27] <shadeslayer> Quintasan: huh?
[01:27] <Quintasan> yofel: but they will take the same amount of memory, won't they?
[01:27] <Quintasan> provided the size matches of course
[01:27] <shadeslayer> Quintasan: you can't do tab[wymX][wymY] where the two vars are not known
[01:27] <Quintasan> I KNOW
[01:27] <Quintasan> derp
[01:28] <shadeslayer> okay
[01:28] <shadeslayer> in terms of mem consumption, it shouldn't be different :P
[01:28] <yofel> it won't be different in simply amount of bytes
[01:28] <Quintasan> dude, I want to know if they will occupy exactly the same amount of memory when wymX and wymY are defined during runtime and they equal 50
[01:28] <yofel> as C has no metadata in arrays
[01:28] <shadeslayer> yes
[01:29] <shadeslayer> they will be equal
[01:29] <Quintasan> in other words
[01:30] <Quintasan> SUP BRO I HEARD YOU LIKE DYNAMICAL ARRAYS SO WE PUT 1D DYNAMICAL ARRAY IN YOU 1D DYNAMICAL ARRAY SO YOU CAN INTERATE WHILE YOU MALLOC WHILE YOU ITERATE
[01:30] <shadeslayer> just to make it clear, if wymX/Y are 50, and if you allocate a array of 50x50 , it should be the same
[01:31] <Quintasan> side note
[01:31] <Quintasan> asian input is non existent with clean installs
[01:33] <Quintasan> yofel, shadeslayer: Thanks, my brain is almost no working :P
[01:33]  * Quintasan goes to bed
[01:33] <shadeslayer> heh
[01:33]  * yofel is still thinking about the type difinitions
[01:34] <shadeslayer> lol
[01:34] <shadeslayer> hah
[01:34] <shadeslayer> etc/dbus-1/system.d/org.kde.active.clockconfig.conf
[01:34] <shadeslayer> xD
[01:35] <shadeslayer> I don't think we want that
[01:35] <shadeslayer> hm
[01:35] <shadeslayer> nvm, we do what that
[01:35] <shadeslayer> I read that incorrectly
[01:41] <shadeslayer> anywho
[01:41] <shadeslayer> morning everyone
[01:41] <yofel> hm
[01:41] <yofel> just learned something about C too
[01:41] <shadeslayer> ?
[01:42] <yofel> I wasn't sure why piksele was defined as one array pointer just to have its type changed in the next line
[01:42] <yofel> but to be used as an array pointer it has to be defined like that
[01:43] <shadeslayer> heh
[01:43] <yofel> i.e. it has to be the type of the first element it's later pointing to
[01:43] <shadeslayer> I see
[01:43] <yofel> otherwise the compiler barfs
[01:46] <yofel> or actually more correct: piksele=(int(*)[obraz->wym_x]) obraz->piksele; says that obraz->piksele has elements of the type of the pointer.
[01:46] <yofel> defining the type of the memory, not the pointer
[01:47]  * yofel looks at kde again to let his brain rest
[01:47] <shadeslayer> :P
[01:47] <shadeslayer> I'm just about done with plasma-mobile
[01:47] <shadeslayer> so yay :)
[01:47] <yofel> \o/
[01:51] <shadeslayer> http://paste.kde.org/629672/
[01:51] <shadeslayer> just need to make a -dev package now :D
[01:57] <shadeslayer> yofel: does plasma-active-dev sound fine?
[01:57] <yofel> sure
[02:08] <shadeslayer> plasma-mobile uploaded to ppa:kubuntu-active/ppa
[02:08] <shadeslayer> I'll do the rest later on :)
[07:22] <ScottK> Sigh.
[07:22] <ScottK> Workspace not uploaded.
[07:29] <ScottK> Riddell: workspace is a bit confused between ninjas and bzr what's supposed to be uploaded.
[11:17] <apachelogger> oh children
[11:18]  * apachelogger needs coffee
[11:18] <apachelogger> Quintasan_, yofel_, shadeslayer: that line you pasted should be obvious :P
[11:19] <apachelogger> it's an array of size wym_x, named tablica, containing pointers to ints
[11:21] <apachelogger> also the program technically leaks
[11:22] <apachelogger> so that declaration you pasted is so weird because the code is weird... first of all int* and int[] are treated as if they are the same which of course they are not
[11:23] <apachelogger> secondly a bad compiler would allocate >=5*4bytes on that line
[11:23] <apachelogger> as the code litterally says "there now shall be an array of int pointers 5 cells long"
[11:24] <apachelogger> all nice and fancy
[11:24] <apachelogger> now in the next line however comes what makes it bad code
[11:26] <apachelogger> an allocation on the heap assuming that the two dimensional array created before will be treated linear
[11:27] <apachelogger> it's allocating a memory segment >= x*y*4bytes and telling the compiler it should use that memory segment as the actual variable tablica
[11:29] <apachelogger> this program now contains the knowledge that an array in C is linear memory
[11:31] <apachelogger> it all had of course been more obvious if the variable had been int** or int[][], but oh well
[11:31]  * apachelogger thinks we should all program arm asm anyway
[11:31] <apachelogger> now coffee
[11:40] <yofel> thanks for the enlightment
[11:44] <yofel> apachelogger: wait, on which page were you? page 63 has no variable called tablica - that's a few pages before
[11:48] <yofel> and even there I don't see an array of pointers to int.
[11:48] <yofel> int* tablica[wym_x]; is an array of pointers to int
[11:49] <yofel> int (* tablica)[wym_x] is a pointer to an array of ints
[11:49] <yofel> apachelogger: or am I reading that the other way around?
[12:27] <Tm_T> packages on ninjas are good to go for installation on 12.10 ?
[12:28] <yofel> Tm_T: kate isn't done yet, otherwise yes
[12:34] <Tm_T> ok thanks
[12:51] <Riddell> yofel: awesome job on quantal there
[12:51] <yofel> uh... except kate all packages built by themselves, so it was an easy job really
[12:52] <Riddell> ssh, just take all the credit :)
[12:52] <yofel> :D
[13:05] <Tm_T> yofel: could you prod me when kate is ready to roll too and I go and install them for testing? (:
[13:07] <yofel> Tm_T: it's done now
[13:08] <Tm_T> ooh jolly good thanks
[15:24] <vibhav> Riddell: SOrry for pinging at the wrong channel, are you available?
[15:29] <Riddell> vibhav: mm?
[15:30]  * yofel finished kubuntu-batch-backport - comments welcome
[15:30] <yofel> and I'm off for the rest of the evening
[15:30] <Riddell> thanks yofel
[15:31] <vibhav> Riddell: pm?
[16:48] <oy> is a kubuntu alpha LiveCD available?
[16:56] <ScottK> yofel: Everything built by itself, except for the stuff I retried ....
[16:56] <tsimpson> oy: https://wiki.kubuntu.org/RaringRingtail/Alpha1/Kubuntu
[16:56] <ScottK> yofel, Riddell, apachelogger: workspace is still missing.
[17:00] <oy> tsimpson, thanks :-)
[17:59] <apachelogger> yofel: oh, must have looked on the wrong page ^^
[18:00] <apachelogger> yofel: but yeah, while drinking my coffee I realized that I was wrong
[18:00] <apachelogger> it's a pointer to an array
[18:00] <apachelogger> so that won't cause a pointless stack allocation
[18:00] <apachelogger> it's pretty much cheating the compiler though
[18:01] <kubotu> ::workspace-bugs:: [1093149] [kubuntu] default background not showed @ https://bugs.launchpad.net/bugs/1093149 (by Fabio Marconi)
[18:02] <apachelogger> ah 63 is the same thing tho
[18:02] <apachelogger> still cheating the compiler
[18:04] <apachelogger> i.e. it's not an array it's a memory segment, so accessing it via a pointer to an array and then using the pointer as first dimension is not only not obvious it defeats the purpose of declaring it as an array to begin with
[18:07] <apachelogger> so the way to do it right is either ** (which IMHO would be best seeing as there really is no array as actual data type involved in the allocation) or (*)[][] (to have the compiler help you with not abusing the memory and making it apparent to the reader that this is in fact fixed size)
[18:29] <Riddell> vibhav: you had a question?
[18:31] <Riddell> ScottK: you rejected kdiamond?
[18:57] <Riddell> oh it's a soyuz issue
[18:57] <Riddell> ScottK: kde-workspace uploaded
[18:57] <Riddell> kajongg too
[18:57] <Riddell> I don't see anything wrong with kshisen, all copyright holders in debian/copyright and FDL


[19:28] <rick_h_> closing in on 2k views over the weekend! https://www.youtube.com/user/celebrateubuntu
[23:00] <huwshimi> Morning


[01:17] <wrst> minasota: I'm a braves fan, so no!
[01:18] <Unit193> Indians.
[01:19] <minasota> wrst: Maybe the braves will get back to the glory days of the 90's... ;)
[01:19] <wrst> the lake caught on fire once didn't it in cleveland?
[01:19] <wrst> minasota: I just want them to not be a laughing stock :)
[01:20] <minasota> Unit193: Not a cleveland fan, I'm not a boston fan even more :)
[01:22] <minasota> As much as I'd like to see the Indians knock the the red socks out of it, doubtful that will happen
[01:23] <Unit193> \o/
[01:29] <minasota> Porcello not having a good night. But Boston doesn't haven't any depth in pitching rotation. Cleveland might pull it out... Wild Thing would be proud...
[01:29] <Unit193> Boston, where nobody can talk right.
[01:30] <Unit193> http://i.imgur.com/Gx9FX78.jpg
[01:32] <minasota> lol, that was pretty good. I'm sure there are some of those floating around about us down here in the south, too
[01:35] <minasota> https://www.youtube.com/watch?v=Hs2KiBiPU6w  I guess you were right, Unit193
[01:35] <Unit193> Nice one: http://poster.keepcalmandposters.com/2291628.png  Not so nice: http://i.imgur.com/db0Ru7h.jpg
[01:36]  * Unit193 runs before wrst gives him the booot.
[02:23] <wrst> Unit193: that west Virginia one was funny ;)
[02:23] <Unit193> :D


[01:03] <TheMuso> ScottL: I see nobody has sponsored the studio meta upload, so I'll make sure to take a look today some times.
[01:04] <TheMuso> time
[01:04] <ScottL> TheMuso, thank you!  that would be fantastic, please let me know if there is anything i can assist you with
[01:04] <TheMuso> Sure.
[01:15] <paultag> yo there ScottL
[01:31] <ScottL> hi paultag :)
[01:46] <paultag> :)
[03:05] <TheMuso> ScottL: THis diff for the studio has a few things. I'll update it, show you the corrected diff, and explain what the problems were.
[03:40] <ScottL> TheMuso, thank you, i look forward to understanding better
[03:40] <TheMuso> No problem.
[04:28] <TheMuso> ScottL: http://paste.ubuntu.com/537735/ is the diff, with some corrections.
[04:29] <TheMuso> I am going to upload now so we can get it in by Alpha 1.
[04:56] <ScottL> TheMuso, holy smokes, that is one big diff!  i'll try to explore it tomorrow and during the week
[04:56] <TheMuso> ScottL: Right, you can ignore all the *-amd64/i386/armel/powerpc stuff
[04:57] <TheMuso> I should have filtered that actually. Let me do that now.
[04:58] <holstein> paultag: im around now
[04:59] <holstein> ScottL: youll be able to facilitate the meeting right?
[04:59] <holstein> tuesday?
[05:01] <paultag> holstein, what's up
[05:01] <paultag> :)
[05:02] <holstein> not much
[05:02] <holstein> you mind if a /q you for a sec?
[05:02] <paultag> holstein, go for it
[05:02] <TheMuso> ScottL: http://paste.ubuntu.com/537749/ is the filtered diff.
[11:55] <ScottL> holstein, i thought the meeting was on wednesday for us, at 7:00 am?
[11:56] <ScottL> but i'll check the time again later this morning
[11:56] <ScottL> this week will be very busy for me during the morning
[11:57] <ScottL> on wednesday i can make 7:00 am but i will _only_ have thirty minutes though
[11:57] <ScottL> TheMuso, thank you
[13:14] <scott-work> ack, holstein, i think i'm an idiot
[13:15] <scott-work> it looks like i was wrong earlier (a few days ago) when i said your schedule for the website meeting was off
[13:15] <scott-work> http://www.timeanddate.com/worldclock/fixedtime.html?month=12&day=1&year=2010&hour=1&min=0&sec=0&p1=0
[13:15] <scott-work> this puts my local time a 7:00pm :)
[13:15] <scott-work> TheMuso: it didn't look like too much change between my version and yours
[13:15] <scott-work> +  * Remove lpia and ubuntustudio-audio package list files
[13:15] <scott-work> this was the only major thing i saw
[13:16] <scott-work> granted i quickly scan through it all
[13:51] <holstein> scott-work: morning :)
[13:51] <holstein> i just wanted to make sure you were either going to be there
[13:52] <holstein> OR if you could get me links and whatever needs to be covered
[13:55] <scott-work> holstein: since i know now that it is tomorrow night it shouldn't be a problem to attend :)
[13:59] <holstein> scott-work: COOL
[14:37] <scott-work> persia: yay!  + [apw] write a skeleton document for outside consumers to reference for migrating from older versions/flavours:DONE
[14:45] <scott-work> persia: doh, sorry, that wasn't what i thought it was :(
[14:45]  * scott-work is trying to do WAY too much concurrently this morning
[21:26] <TheMuso> scott-work: No there weren't, but there were a few important bits that need fixing. I also suggest you take a look at the bzr branch for the seeds.
[21:27] <scott-work> TheMuso:  to be clear, you also made changes to the seeds?
[21:27] <TheMuso> Yes.
[21:28] <scott-work> ah, i see the revision
[21:28] <scott-work> i'll dig into that tonight or tomorrow
[21:28] <TheMuso> Ok cool.
[21:29] <scott-work> okay, i looked right now :P
[21:29] <scott-work> i see that adding the task-seeds line takes care of something per.sia had mentioned before
[21:30] <scott-work> i thought that was taking care of during the STRUCTURE file
[21:30] <scott-work> where it mentioned "generation: audio-common"
[21:31] <scott-work> TheMuso: i also see the changes for boot and desktop-common...wow
[21:32] <TheMuso> No its not. The structure file lays out how things are built on each other, it doesn't say that the contents of one seed should be included in another.
[21:32] <scott-work> TheMuso: when we offer the -lowlatency kernel will we need to reimplement these
[21:32] <scott-work> ?
[21:32] <TheMuso> scott-work: Yeah, until we ship our own different kernel again, we don't need those hanging around.
[21:32] <TheMuso> Yes for low latency, we will need those again.
[21:32] <scott-work> haha, i think that answers myq uestion
[21:33] <scott-work> okay, i don't feel too bad about those changes then  :)
[21:33] <TheMuso> Ok cool.
[21:33] <scott-work> of course i'm going to go through other seeds and see if i can find other instances of the task-seeds line
[21:34] <TheMuso> Ok.
[21:36] <scott-work> i'm excited about having the changes made, we should see all these implemented in tomorrows build, yes?
[22:02] <TheMuso> Yes, but there is one more change that needs to be made, I just need to send Colin a patch for the build scripts to know about the new tasks.
[22:02] <TheMuso> The patch in question is against the version of debian-cd used to build all Ubuntu disks.
[22:34] <TheMuso> Ok, patch made and a merge proposal sent to Colin.
[22:34] <scott-work> TheMuso: i talked to colin almost a week ago and he said he had a script that updates the tasks and even told me when it was compelte
[22:34] <TheMuso> scott-work: This is different.
[22:34] <scott-work> TheMuso: ah, okay :)
[22:36] <scott-work> apparently unity is now turned on in the natty daily builds
[22:36] <scott-work> i wonder how this will affect ubuntustudio
[22:36] <holstein> cool
[22:36] <holstein> i was wondering about that
[22:36] <holstein> scott-work: the ubuntustudio-desktop shouldnt be effected right?
[22:36] <scott-work> and i am looking forward to downloading a vanilla ubuntu daily build and seeing it from a live cd
[22:37] <scott-work> holstein: i haven't a clue to be honest
[22:37] <holstein> gnome is about to get some cool stuff i hear
[22:37] <holstein> some funding
[22:37] <holstein> im sure there will be gubuntu
[22:37] <scott-work> holstein: i would defer to TheMuso or persia about how unity being turned on by default will effect ubuntu studio, or i'll just download a new ubuntu studio daily tomorrow :)
[22:38] <TheMuso> Studio won't get unity, as its not in the seeds.
[22:38] <holstein> i was worried about it
[22:38] <holstein> but i think we should just roll on with gnome
[22:38]  * scott-work is going home, ciao
[23:03] <quadrispro> ScottL, mda-lv2 has joined Debian unstable
[23:19] <ScottL> quadrispro, super sweet!  i've been researching mda a bit
[23:20] <ScottL> it looks like we are beginning to have quite a stable of plugins
[23:20] <ScottL> i wonder if we (i.e. ubuntustudio-devs) parse through them at some point and be more selective about which ones we ship
[23:20] <ScottL> quadrispro, also:  https://wiki.ubuntu.com/UbuntuStudio/Backports
[23:21] <ScottL> it's not done, but it's got a lot to it
[23:23] <ScottL> quadrispro, how did you get mda into unstable?  shouldn't it reside in debian-new until release?
[23:23] <quadrispro> no, ftp-masters (slowly) process packages in NEW
[23:24] <quadrispro> BTW, they will not enter squeeze


[00:25] <james_w> lifeless: looms look pretty cool to me, thanks again.
[00:25] <james_w> lifeless: any direction you want to point me in to do a bit of hacking to start to understand the mechanics?
[00:27] <james_w> I think the only difference with what I was looking at was the order of the parents in the merge commits that result from up-thread.
[00:27] <james_w> and obviously that you have a working implementation :)
[04:24] <cjb> Hi!  Is there a way for a repository to specify its submit_to address, such that `bzr send` could send mail to a default address for a pulled repository?
[04:31] <Verterok>
[04:47] <baijum> The "HistoryOfBazaar" wiki page says: "In early 2008, Bazaar became GNU Bazaar when release 1.2 was accepted as part of the GNU project." is there any news or more details available ?
[05:05] <abentley> baijum: Not yet.  I was expecting some kind of announcement, but it's just kind of leaked out gradually.
[05:06] <abentley> cjb: Not yet.
[05:33] <Peng> Wait, so that's true?
[05:33]  * bob2 watches bzr climb up to 1gb of ram to check out ikarus.dev
[05:34] <bob2> with a healthy 3MB of data in the branch so far
[05:39] <Peng> So, what's the point of being a GNU project? Canonical can provide all of the hardware bzr needs, and I doubt they'd want to give up any control over the project...
[05:39] <Basic> marketing
[05:39] <Peng> Advertising?
[05:39] <Peng> Heh.
[05:39] <NichardRixon> homestarrunner.com cool website
[05:39] <Basic> heh
[05:40] <Peng> So, the big thing for shareware in the 1990s was to be get a Download.com badge, and now FOSS projects are going to go after GNU badges?
[05:40] <Basic> my local repo is messed up, is there a way, other then do do a bzr pull of upstream to just suck down all of upstream and overwrite and conflicts in my local repo?
[05:41] <Peng> Basic: Conflicts? Like, you've committed things in the branch, or your repo is corrupt?
[05:41] <Basic> like I forgot to commit stuff in local (desktop), hacked code in my laptop, pushed the changes from laptop to upstream, now want local/desktop to be in-sync
[05:42] <Basic> bzr merge gives me 138 conflicts and I know upstream and laptop are the changes I want to keep
[05:42] <bob2> now hit 1.5GB, nice
[05:43] <Peng> Basic: Why can't you bzr pull from upstream?
[05:43] <Basic> trying
[05:44] <Peng> Basic: "bzr help pull" says "If you want to forget your local changes and just update your branch to  match the remote one, use pull --overwrite."
[05:44] <Peng> s/  / /
[05:44] <Basic> excellent, exactly what I want thanks
[05:44] <bob2> with giant red flashing lights "you may lose data"
[05:45] <Peng> Heh, right.
[05:45] <Peng> Basic: You can use "bzr missing" to see if you have anything important in your version of the branch.
[05:46] <Peng> Oogh, why do I feel sick?
[06:18] <Peng> jelmer: I'm being lazy and not doing research here, but the BzrPlugins page lists bzr-svn as beta. Is it still?
[06:41] <lifeless> bob2: 'bzr heads' can recover commits, at leat until a gc.
[06:41] <lifeless> 16:33  * bob2 watches bzr climb up to 1gb of ram to check out ikarus.dev
[06:41] <lifeless> woops, didn't mean to paste :|
[06:42] <Peng> lifeless: By gc you mean the revisions being removed from the repo? Does that ever happen automatically?
[06:42] <lifeless> Peng: not presently
[06:42] <Peng> Right.
[06:43] <Peng> Ok, I'm going to go take that nap I meant to take an hour ago. Bye. :)
[06:53] <jeremyb> Peng: it's at 0.4.x iirc
[06:53] <jeremyb> Peng: i need to try it...
[06:54] <jeremyb> Peng: recently saw a bug fixed where it made a remote svn repo unusable by *anyone* on commit fwiw
[06:54] <jeremyb> (not all commits)
[06:55]  * jeremyb needs to sleep as well
[07:39] <bob2> lifeless: ah, neato
[09:59] <Odd_Bloke> jelmer: I'm in the Debian room ATM.
[11:16] <jelmer> Odd_Bloke: ping
[11:17] <Odd_Bloke> jelmer: Pong.
[11:18] <jelmer> Odd_Bloke: still wandering around on FOSDEM?
[11:18] <Odd_Bloke> jelmer: Yeah, in the Debian room ATM.
[11:19] <jelmer> Odd_Bloke: ah, cool
[11:19] <jelmer> me too
[11:19] <jelmer> LarstiQ is the guy behind the big camera btw
[11:20] <Odd_Bloke> Yeah, I ran in to him last night.
[11:20] <Odd_Bloke> His hair was less blue at that juncture.
[11:21] <Odd_Bloke> jelmer: I'm kinda opposite the door, wearing a red T-shirt using a Thinkpad.
[11:21] <Odd_Bloke> A T60, if that helps narrow it down. :p
[11:24] <johnf> is there anyone about that understands the smart server code? I'm trying to fix a bug in it
[11:25] <Odd_Bloke> johnf: Asking your question makes it more likely that people will respond. :)
[11:25] <johnf> Odd_Bloke: ok let me go paste some stuff somewhere
[11:25] <jelmer> Odd_Bloke: ah, I think I know who you are then :-)
[11:26]  * jelmer is sitting close to the door with a Thinkpad X60 and wearing a black debian sweater
[11:27] <johnf> http://pastie.caboo.se/156526. Basically a change was made which meant bzr+https stopped working. I've fixed that but now it looks like _remote_is_at_least_1_2 needs to be set somewhere.
[11:28] <johnf> I think just setting it to true like is done in bzrlib/smart/client.py is correct but I'm not sure of the right place to do it
[11:28] <johnf> the transport/http/_urllib doesn't feel like it would be the right place to do it
[11:31] <jelmer> johnf: you may want to bring this up on the list
[11:31] <jelmer> I don't think there are any smart server ackers about
[11:31] <johnf> that was my next move :)
[11:32] <jelmer> *hackers
[11:42] <james_w> johnf: one moment
[11:44] <james_w> johnf: I thought this came up on the list the other day, but I can't find it now.
[11:44] <james_w> johnf: are you using latest bzr.dev?
[11:45] <johnf> james_w: opps too late. Just emailed the list with some potential fixes. Stupidly didn't check archives. I'm testing with latest bzr.dev
[11:45] <james_w> johnf: no loss, I just thought there was a tentative patch you could apply, but as I can't find it a mail to the list is best.
[11:47] <johnf> james_w: The patch I just email works. First part I know is right. Second part does the job but I'm not sure that its appropriate. As I learned while debugging it today there is a lot of codebase involved in getting the smart server to do stuff!
[11:50] <james_w> johnf: I can't confirm I'm afraid, but you should get a response either way tomorrow.
[16:39] <hsn_> someone with sf.net shell acount with installed bzr here? I need bzr path
[18:01] <ubotu> New bug: #195133 in bzr-loom "Please notify when a thread becomes empty" [Undecided,New] https://launchpad.net/bugs/195133
[18:05] <ubotu> New bug: #195134 in bzr-loom "Lots of up-threads are tiring" [Undecided,New] https://launchpad.net/bugs/195134
[20:18] <Janzert> does "bzr tag blah" tag the most recent revision committed or get applied to the next commit?
[20:19] <dato> Janzert: the most recent committed revision
[20:19] <Janzert> thanks
[20:30] <shagbag> Can anyone help me with bazaar.launchpad.net?    I'm trying to checkout some code but it's taking AGES to connect and then it gives me the error: bzr: ERROR: Connection error: Couldn't resolve host 'bazaar.launchpad.net' (-2, 'Name or service not known')
[20:34] <awmcclain> Hey all... can someone enlighten me why, when I try to push my changes back to my mainline, I get bzr: ERROR: No push location known or specified.
[20:34] <jdong> awmcclain: it doesn't know where to push?
[20:35] <awmcclain> jdong: How does that get set? I can pull fine
[20:35] <jdong> awmcclain: the first push has to have an explicit destination. Afterwards bzr will remember that destination. Also see push --remember
[20:35] <awmcclain> jdong: I see. So, the first time you have to specify.
[20:35] <jdong> awmcclain: right.
[20:35] <jdong> awmcclain: hte last paragraph in bzr help push explains it better than I can :)
[20:36] <awmcclain> jdong: Got it.
[20:36] <jdong> awmcclain: also, bzr info can show you the various remembered locations, if you forgot or need something to copy-paste from
[20:38] <awmcclain> jdong: Is there an easy way to convert a branch into a checkout w/o overwriting the files I've changed?
[20:38] <jdong> awmcclain: bzr bind
[20:38] <awmcclain> Done.
[20:39] <awmcclain> greart
[20:39] <jdong> awmcclain: any differences you've made will show up as a merge when you first bzr up
[20:42] <awmcclain> hrm
[21:28] <lifeless> shagbag: sounds like a dns error at your location
[21:28] <lifeless> shagbag: what does 'host bazaar.launchpad.net' say ?
[21:42] <lifeless> hi poolie
[21:57] <poolie> good morning lifeless
[21:58] <james_w> morning lifeless
[21:58] <james_w> morning poolie
[22:28] <james_w> lifeless: I might be being silly, but can you confirm that setting tree.branch.nick doesn't change the thread you are on?
[22:28] <james_w> I'm looking at test_up_thread_preserves_changes in blackbox.py
[22:30] <lifeless> james_w: it changes the pointer at the current thread
[22:30] <lifeless> james_w: in the TODO there is a note that this should be replaced by it renaming the current thread.
[22:47] <james_w> lifeless: thanks.
[22:48] <lifeless> james_w: most of TODO can be made bugs now
[22:48] <lifeless> james_w: for hopefully obvious reasons, using malone was a little tricky before the release.
[22:53] <james_w> lifeless: of course.
[22:53] <james_w> lifeless: you abandoned the rename to warps?
[22:56] <igc> morning all
[22:58] <lifeless> james_w: mixed minds
[22:58] <lifeless> I think the accuracy of warp and weft reference will be beyond most folk;
[22:58] <lifeless> that is not actually helpful
[22:59] <lifeless> but most everyone knows what a thread is in fabric terms
[23:00] <lifeless> OTOH warp and weft are a more detailed analogy with richer (and useful) implications
[23:00] <lifeless> poolie: today I am doing ui for shallow branches
[23:01] <igc> poolie: call now?
[23:07] <james_w> lifeless: I might spend some time sorting out the TODO and moving some stuff to Malone then.
[23:07] <james_w> patch sent anyway, that's all for tonight.
[23:07] <lifeless> that would be good
[23:07] <lifeless> thanks!
[23:08] <james_w> the code looks very clean from what I have seen, and the documentation is great as well, so thank you.
[23:09] <james_w> The only thing I am not that clear on is "record", but it seems that is a temporary solution according to the TODO.
[23:16] <lamont> I wonder if there's already a bug in the system about bzr not tracking file permissions
[23:16] <lamont> (git does)
[23:16] <james_w> lamont: git doesn't
[23:16] <james_w> lamont: which permissions would you like tracking?
[23:17] <lamont> git diff 8e16fa6ff4f1bd3e42febd166f3e1074c6f87bdb..7fca3ff2f2ab0774d4a92c2bd40bfc7c4d596e4c
[23:17] <lamont> diff --git a/cron.d/cache-git-status b/cron.d/cache-git-status
[23:17] <lamont> old mode 100755
[23:17] <lamont> new mode 100644
[23:17] <lamont> james_w: I beg to differ.
[23:18] <lamont> although just tracking the last 12 bits would be plenty.
[23:18] <lifeless> lamont: git doesn't track full modes; it just cheats for what it appears to record
[23:18] <lifeless> lamont: see git-fastexport's stream format for instance
[23:18] <lamont> while bzr just plain ignores mode
[23:18] <lifeless> bzr tracks exec
[23:18] <james_w> lamont: that just means executable, which bzr tracks as well.
[23:18] <lamont> ah, just not rw?
[23:18] <lifeless> anyhow, for sysadmins see the discussion I'm having with elmo & co about a plugin
[23:19] <james_w> lamont: make it 750 and try again.
[23:20] <lamont> james_w: hrm.. thanks
[23:21] <lifeless> lamont: score one for git...not :>
[23:21] <james_w> lamont: no problem. You can see etckeeper for some wrappers and stuff around git(?, maybe others) that tracks full (?) permissions for versioning /etc
[23:21] <fullermd> It's easy to make it 750; you just have to change your umask   ;)
[23:22] <james_w> lamont: but in general it is a headache to track them, so most systems don't.
[23:22] <lamont> right
[23:22] <lifeless> james_w: the canonical sysadmins would love a etckeeper for bzr; I have a spec
[23:24] <james_w> lifeless: you mean a plugin, rather than using etckeeper?
[23:24] <lifeless> yes
[23:24] <james_w> I doubt etckeeper is VCS specific, but a plugin may make for a better experience.
[23:25] <jelmer> lifeless: I have the implementation
[23:25] <jelmer> lifeless: see http://gitweb.samba.org/
[23:25] <james_w> right, that really is all from me. Thanks all, and good night.
[23:25] <jelmer> however, it hsn't been merged yet because bzr doesn't have a start-commit hook
[23:26] <jelmer> so it's not totally functional, which is why it hasn't been merged yet
[23:26] <lifeless> jelmer: could you be more specific; thats just a web page list
[23:26] <lifeless> jelmer: also, I'm talking about not using etckeeper but doing a plugin
[23:26] <jelmer> there's only one etckeeper repo there :-)
[23:26] <jelmer> http://gitweb.samba.org/?p=jelmer/etckeeper.git;a=summary
[23:27] <jelmer> it basically boils down to being a plugin since it requires a plugin that calls out to etckeeper
[23:27] <lifeless> is it just me or that web ui ugly?
[23:27] <jelmer> of git web?
[23:27] <jelmer> I like it better than loggerhead
[23:28] <lifeless> loggerhead is ugly too
[23:28] <lifeless> in differnet ways
[23:29] <lifeless> none of the web uis I've seen for vcs introspection feel nice
[23:29] <jelmer> yeah, there aren't any really good ones yet
[23:30] <mwhudson> if anyone can come up with a nice design for loggerhead, i'm permanently volunteered to do the coding to make it happen, btw
[23:31] <ubotu> New bug: #195245 in bzr-loom "'record' is too generic a name, and is possibly a conflict with another plugin" [Medium,In progress] https://launchpad.net/bugs/195245
[23:34] <lifeless> mwhudson: I think its basically too static and too slow
[23:34] <lifeless> mwhudson: the visuals aren't the issue, the coarseness of the interface is.
[23:34] <mwhudson> lifeless: 'too static' ?
[23:34] <lifeless> mwhudson: I'd like fast drill-downs, pivots between files/history/annotations
[23:35] <lifeless> google maps for the vcs data
[23:35] <mwhudson> oh right yes
[23:35] <lifeless> now theres an idea; if we built maps tiles from a  branch we could literally point maps at it
[23:35] <mwhudson> well, i see the point but don't really have a clue how this would work well
[23:36] <mwhudson> (even out of a browser, truth be told: 'bzr viz' is pretty nice, but not completely there)
[23:36] <awilkins> Is there a plugin which will allow you to commit selectively by deleting lines from your commit log "line below" section?
[23:37] <lifeless> I believe so
[23:37] <lifeless> selective commit I think its called
[23:38] <awilkins> Could also use gcommit I suppose, but not as vimtastic :-)
[23:58] <lifeless> jelmer: so when should I expect a patc to review for a commit start python hook ?
[23:59] <jelmer> lifeless: when I find the time :-(
[23:59] <jelmer> lifeless: My time for bzr is somewhat limited at the moment and the time I do have I spend on the plugins I'm maintainer for
[23:59] <lifeless> you're coming next week ?


[19:30] <markbaas> Hi, can anyone tell me where to find the code that shows the window title in the panel and replaces itself for the menu
[19:31] <markbaas> I looked at the appmenu indicator, but could not find anything