[12:21] <bddebian> crimsun: You aboot?
[12:21] <LaserJock> more content, more content *whip*
[12:22] <bddebian> ??
[12:22] <LaserJock> contentless ping
[12:23] <bddebian> Yeah, so? :-)
[12:23] <geser> bddebian: about bug #76544: are you sure the Ubuntu changes aren't needed anymore?
[12:23] <Ubugtu> Malone bug 76544 in fnfx "[Sync Request]  fnfx 0.3-12" [Undecided,Needs info]  https://launchpad.net/bugs/76544
[12:23] <bddebian> crimsun: <content> What's up with beep-media-player? </content>
[12:24] <bddebian> geser: No, that should probably be rejected but I think a lot of the changes could/should go away
[12:29] <bddebian> Gah, I hate these where we have strayed from Debian and now it's like what makes sense and what doesn't...
[12:33] <crimsun> bddebian: yes?
[12:34] <bddebian> Heya ScottK
[12:35] <ScottK> heya
[12:35] <bddebian> crimsun: I was just curious what was up with beep-media-player
[12:36] <crimsun> bddebian: if you'd like to merge it, feel free (I'm short on time). Note the changes to the image files (default skin).
[12:36] <bddebian> yeah, I saw that :)
[12:36] <bddebian> Hmm, should we sync/merge a package with 3 RC bugs in Debian? :)
[12:36] <geser> persia already did a merge. it only needs review and sponsoring
[12:36] <bddebian> geser: Well what are you waiting for? :-)
[12:38] <crimsun> well, persia has noted it blocking on maintainer mangling, though I think that's a superfluous blocker.
[12:38] <Toadstool> bddebian: fix the bugs :)
[12:38] <crimsun> (bug 79065)
[12:38] <Ubugtu> Malone bug 79065 in beep-media-player "merge beep-media-player <IP_ADDRESS>+cvs20050803-2 from debian unstable" [Undecided,Unconfirmed]  https://launchpad.net/bugs/79065
[12:38] <Toadstool> heya everybody
[12:39] <bddebian> Heya Toadstool
[12:42] <TheMuso> Whats the best way of putting a homepage URL in a package description?
[12:43] <TheMuso> As in, at the end, with the homepage keyword?
[12:43] <Toadstool> " .\n  Homepage: <URL>"?
[12:43] <geser> "  Homepage: <URL>" (note the two spaces at the begin)
[12:44] <TheMuso> ok thanks guys.
[12:44] <TheMuso> I thought the long description only needed one space at the end.
[12:44] <TheMuso> beginning sorry
[12:45] <geser> TheMuso: the second space has a special meaning: no word-wrap
[12:45] <TheMuso> ah ok.
[12:45] <geser> crimsun: are you going to upload the bmp merge?
[12:46] <crimsun> geser: no, I'm not near my keys.
[12:46] <geser> ok, I will do it if you don't mind
[12:46] <crimsun> that's fine.
[12:48] <geser> bddebian: you could merge fnfx :)
[12:49] <bddebian> No thanks
[12:50] <bddebian> I've looked at it twice and somerville32 has tried a couple I think
[12:54] <StevenK> Heh, I can try, if you want.
[12:55] <bddebian> Go for it
[12:56] <coNP> Can someone help me how to fix packaging bugs?
[12:56] <bddebian> We can try
[12:56] <coNP> Upload an usual debdiff?
[12:56] <bddebian> heh
[12:57] <coNP> okay, not sent
[12:59] <Toadstool> coNP: prepare a debdiff fixing the bug, attach it to the bug report and subscribe ubuntu-universe-sponsor (or whatever the name is) or poke a MOTU here :)
[01:00] <coNP> Toadstool: as is the usual process, isn't it?
[01:00] <Tonio_> bddebian ping ?
[01:01] <Toadstool> coNP: yep
[01:01] <Tonio_> bddebian should I really add any copyright of any file of a project in debian/copyright ?
[01:02] <Tonio_> bddebian that's really ridiculous, unreadable, and unmaintainable
[01:02] <azeem> Tonio_: how many of them are different?
[01:02] <bddebian> Tonio_: Well I've had to but I'm now where near an expert on the licensing stuff.  I tend to agree with you. :-)
[01:02] <Tonio_> azeem dozens........
[01:03] <azeem> yummy
[01:03] <Tonio_> bddebian and the typo IS FIXED for at least two uploads :)
[01:03] <Tonio_> bddebian s/from/of not the oposite :)
[01:03] <bddebian> Yeah, I noticed
[01:03] <Tonio_> bddebian I which that guy to revu the kdebase package and have fun in that case
[01:03] <Tonio_> about 3000 different copyrights there
[01:03] <Tonio_> I agree for the lgpl to be mentionned
[01:04] <Tonio_> but that's all
[01:04] <Tonio_> I'm not going to mention all copyrights, that's a pure bullshit !
[01:04] <bddebian> Works for me :)
[01:04] <Tonio_> or !!! or I'm doing this :
[01:05] <Tonio_> grep -d recurse '(C)' ./ >> debian/copyright
[01:05] <Tonio_> and have fun to revu
[01:05] <Tonio_> I was about to post a flamming reply on revu, but I prefer to flame here, it'll have disapear on tomorrow :)
[01:05] <Tonio_> revu stays online, that's dangerous :)
[01:06] <bddebian> heh
[01:07] <Toadstool> Tonio_: this channel is logged too :)
[01:08] <bddebian> Hmm, what about all those libcommons-* merges...
[01:10] <Tonio_> Toadstool: true, but well I had to empty my brain on that point :)
[01:10] <Toadstool> heh
[01:10] <Tonio_> some expectations on revu are sometimes ridiculous...
[01:10] <Tonio_> how to maintain a package if every copyright on any file has to be mentionned, including headers ? that impossible
[01:10] <Toadstool> you're talking about jabbin?
[01:11] <Tonio_> yup
[01:11] <Tonio_> I agree concerning the lplg, I missed it and will mention it, but for the copyrights......
[01:11] <Tonio_> imagin the same requirement for kdelibs.....
[01:12] <Toadstool> well, technically you're supposed to list them all although I agree it can be a real pita
[01:12] <Tonio_> Toadstool that's theory, imagin the same for linux sources for example...
[01:13] <Toadstool> I know :)
[01:13] <geser> Tonio_: are you talking about my comment on jabbin?
[01:13] <Tonio_> geser, probably :)
[01:13] <Tonio_> I agree for everything but the copirights, that drives me nuts, really !
[01:13] <Tonio_> ;)
[01:13] <Tonio_> that's not against you, just that's simply impossible to maintain
[01:14] <Toadstool> Tonio_: imho, list the main ones, upload and wait for any comments from an archive admin ;)
[01:14] <Tonio_> Toadstoolthat's what I did
[01:14] <Toadstool> oh
[01:14] <Toadstool> and it got rejected?
[01:15] <Tonio_> when 99% of the files of a tree are the ame and just one little file has a different copyright, I don't mention it
[01:15] <geser> I don't meant you have to list each appearance of Copyright
[01:15] <Toadstool> well, I guess so, otherwise you wouldn't be pissed off ...
[01:15] <Tonio_> Toadstool yes, hehe :)
[01:15] <Tonio_> geser well you even added isolated header files on a full tree
[01:16] <Tonio_> for the licence, I'm okay I'll add the lgpl
[01:17] <Tonio_> geser the redistribution of iLBC is to be checked too, you are right on that point
[01:17] <Tonio_> geser just the copyright thing pissed me off especially since I've been asked in the past to stop proviing them all :)
[01:17] <Tonio_> on revu too :)
[01:19] <geser> the other I mentioned have a license that looks like it's free enough (I haven't checked thoroughly) but it's not the GPL
[01:20] <Tonio_> hum, if that's licence, I'm with you
[01:21] <Tonio_> I must say the all tarball is released under the gpl so I didn't checked all files in it, I should have done it though
[01:21] <Tonio_> geser okay I'll revu the all sources concerning the licence, since I perfectly agree with you on that point
[01:21] <Tonio_> geser maybe I just missunderstood you on that point, sorry for this
[01:22] <Tonio_> but the copyrights expectations has already been a long debate so once again drive me nuts :)
[01:22] <Tonio_> geser I'll ping you for revu once I made ot clear concerning the licence
[01:22] <geser> see for example http://revu.tauware.de/revu1-incoming/jabbin-0701261035/jabbin-2.0~beta/src/tools/crash/crash_sigsegv.h
[01:23] <bddebian> ademan: Any luck yet?
[01:24] <ademan> actually i haven't tried anything
[01:24] <Tonio_> yeah that's not explicitly gpl, but looks like compatible
[01:24] <ademan> but the build was successful
[01:24] <ademan> only problem is the deb wants to install all of the shared objects into /usr/share/codeblocks/blah blah blah
[01:24] <Tonio_> geser I think I missunderstood your point, you were talking about the licence more than the coyrights
[01:24] <ademan> and iirc shared objects shouldn't be in /usr/share
[01:24] <Tonio_> geser, and you were right, I admit
[01:25] <geser> Tonio_: http://revu.tauware.de/revu1-incoming/jabbin-0701261035/jabbin-2.0~beta/voip/stun.h has a license at the end of the file
[01:25] <ademan> is that right?  (i picked up a little pdf on the unix file structure, and iirc only platform independant stuff should go in /usr/share)
[01:25] <bddebian> ademan: Is there a lib package?
[01:26] <ademan> naw, it's all one package, it DEFINITELY needs to get broken up into multiple packages though
[01:26] <ademan> like, there's an sdk included
[01:26] <ademan> just a bunch of stuff that should be in separate packages
[01:26] <bddebian> SO break it up :-)
[01:27] <ademan> but most of the libs are essential to the base program, still put them in a codeblocks-lib package?
[01:27] <ademan> i will, but as you could tell by me floundering around, i'm not so great at packaging just yet :-)
[01:27] <Tonio_> geser, that's clear now, and I must say you are right, I'll have to check those files for their licence
[01:27] <bddebian> ademan: Welcome to the club :-)
[01:28] <ademan> hehe
[01:29] <bddebian> I suppose ideally you would have codeblocks, libcodeblocks, libcodeblocks-dev, and codeblocks-sdk or something but since I haven't seen the package I'm just talking out of my arse
[01:30] <ademan> bddebian: even if the libcodeblocks is essential to the codeblocks package?
[01:31] <Tonio_> geser, thanks for beeing patient :) I'm tired, I wouldn't have reacted like this 3 or 4 hours ago
[01:31] <Tonio_> bddebian, he was right hehe :)
[01:31] <bddebian> Sure.  You can have the codeblocks binary depend on the libcodeblocks binary
[01:31] <ademan> yeah, i just didn't know if that was preffered or what
[01:32] <Tonio_> okay I'll check the full licence.... why  ALL those voip software like this ? same licence issue in wengophone.....
[01:32] <ademan> now i just gotta figure out HOW to divide it up into multiple packages :-)
[01:33] <ademan> the maintainer wrote the debian dir to generate these packages: codeblocks codeblocks-contrib libcodeblocks libcodeblocks-devel libcodeblocks-dbg but of course he hasn't committed the new debian dir... so i don't get them :-(   plus isn't libcodeblocks-dev preffered to devel?
[01:35] <coNP> Toadstool: can you have a look at bug 81757 if it is okay?
[01:35] <Ubugtu> Malone bug 81757 in xchat-systray "Duplicate entry in tasklist" [Undecided,Confirmed]  https://launchpad.net/bugs/81757
[01:35] <ademan> course, i may just ask him for the new debian dir, i dunno
[01:36] <ademan> i'd have to fix things up AGAIN, since what he claims builds, doesnt...
[01:37] <ademan> i think the problem is he builds with ./configure && make FIRST, so things that AREN't taken care of in debian/rules are actually present on his system
[01:41] <Toadstool> coNP: sure
[01:47] <geser> coNP: you should probably use conflict instead of replaces
[01:47] <coNP> geser: why? It does not actually conflict.
[01:48] <geser> coNP: http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces
[01:48] <coNP> geser: ty
[01:49] <geser> Replaces allows dpkg to move files owned by one package to another
[01:49] <geser> you are more interested in xchat-systray getting deinstalled
[01:50] <geser> http://www.debian.org/doc/debian-policy/ch-relationships.html#s-conflicts
[01:50] <Toadstool> coNP: what geser said (sorry, I am at work, kinda busy :)
[01:52] <coNP> sorry, my DSL is broken :(
[01:52] <coNP> geser: did you get my last message?
[01:53] <geser> last I've seen from you: <coNP> geser: ty
[01:53] <coNP> geser: so I think replaced is better
[01:53] <coNP> because the documentation says "Packages can declare in their control file that they should overwrite files in certain other packages, or completely replace other packages."
[01:54] <coNP> Now xchat completly replaces xchat-systray.
[01:54] <coNP> But I might be bad
[01:55] <geser> that would be 7.5.2 Replacing whole packages, forcing their removal
[01:56] <coNP> Actually then both replaces and conflicts should be added
[01:56] <geser> so you would probably need replaces and conflicts
[01:56] <coNP> And I think only to xchat, but not to xchat-common
[01:57] <geser> yes
[01:57] <coNP> but that was okay, I checked
[01:58] <coNP> now I should add this new debdiff to the bug?
[01:58] <geser> yes
[01:59] <Toadstool> ok sick of working, I call it a day, let's go get drunk in LA \o/
[01:59] <Toadstool> have a good weekend everybody
[01:59] <coNP> by Toadstool
[01:59] <coNP> +e
[02:03] <bddebian> Later Toadstool
[02:09] <coNP> geser: can you have a look at it again? I think it is quite easy to check, if you want to. However, it is not (very) important at all.
[02:11] <geser> looks ok. have you verified that it works as intended?
[02:13] <ScottK> geser: No problem if you don't, but I was curious if you thought you might have time yet for the new package review I mentioned this afternoon?
[02:15] <geser> ScottK: ah, forgot. I will look at it in the morning (it's past 2 am here)
[02:15] <ScottK> No problem.  Thanks.
[02:17] <coNP> geser: I think so, now it does not allow me to install xchat-systray again, and try again.
[02:17] <coNP> I wanted to test it again
[02:17] <coNP> maybe someone running feisty should do that
[02:19] <geser> I could test it in the morning and upload it afterwards (if nobody is faster)
[02:19] <bddebian> geser: No one is faster than you :-)
[02:19] <coNP> geser: thanks
[02:21] <coNP> good night everyone (in timezones, where it is night :))
[02:21] <bddebian> Gnight coNP
[02:23] <bddebian> welshbyte: Fix all the bugs :-)
[02:24] <welshbyte> ok, i'll start from bug #1 and work my way up ;)
[02:24] <Ubugtu> Malone bug 1 in ichthux "Microsoft has a majority market share" [Critical,Confirmed]  https://launchpad.net/bugs/1
[02:25] <jdong> aah ichthux has taken over bug 1!!!!!!
[02:25] <Liberax> hi any developer here?
[02:26] <bddebian> Nope, no developers here.
[02:26] <Liberax> anybody with amd 64 and pptp could try this fix: https://bugs.launchpad.net/ubuntu/+source/network-manager-pptp/+bug/67881 ?
[02:26] <Ubugtu> Malone bug 67881 in network-manager-pptp "Crash while trying to connect to PPTP server" [Undecided,In progress]
[02:31] <LaserJock> jdong: it's always somebody. I wish we could kill that bug
[02:31] <jdong> lol
[02:32] <Liberax> LaserJock: what bug?
[02:32] <LaserJock> I should ask raphink about that
[02:32] <LaserJock> Liberax: bug #1 of course ;-)
[02:32] <Ubugtu> Malone bug 1 in ichthux "Microsoft has a majority market share" [Critical,Confirmed]  https://launchpad.net/bugs/1
[02:33] <Liberax> :)
[02:33] <LaserJock> I'm just annoyed at getting bugmail from it
[02:34] <ScottK> Speaking of fixing bug and that other operating system...  I recently fix a python-dns bug, Bug #80360, here and then decided to report it upstream.  There I found a few open bugs that have been there for more than two years.  At least one of them is Windows only.  I am considering doing a patch here to resolve the upstream bugs too.  Would it be considered poor form to fix the Windows unique stuff in the same package?
[02:34] <Ubugtu> Malone bug 80360 in python-dns "Crash - Fails to trap socket.error when network is not available" [Undecided,Fix released]  https://launchpad.net/bugs/80360
[02:35] <crimsun> ScottK: no.
[02:35] <LaserJock> ScottK: uneccesarly maybe, but not bad form surely ;-)
[02:36] <bddebian> Shirley?  I thought his name was Scott? :-)
[02:36] <LaserJock> darn, I'd sound so much more intelligent if I could spell better
[02:36] <crimsun> we should be concerned about code quality, not what OS is affected.
[02:36] <LaserJock> bddebian: bah
[02:40] <ScottK> OK.  Thanks.  I thought I'd check before I went to the trouble.  Back when I was exclusively using Windows, the fact that Python was cross platform was one of the things that attracted me to it in the first place.
[02:41] <LaserJock> I liked it because you didn't have to buy a compiler for it
[02:58] <ScottK> I will also confess that the ESR piece on how all the cool geeks used Python influenced me too.
[03:00] <bddebian> pfft :-)
[03:05] <bddebian> I thought XbuildX revisions were synced automagically?
[03:08] <LaserJock> should be
[03:20] <bddebian> LaserJock: Care to review libticables2 for me? :-)
[03:30] <bddebian> Ho hum
[03:40] <crimsun> keescook: regarding #78339, a debdiff cannot represent the upstream changes in binary form.
[03:40] <crimsun> keescook: my practice has always been to provide a debdiff otherwise.
[04:16] <ScottK> Good (I'm guessing it's afternoon for you) afternoon Hobbsee
[04:17] <Hobbsee> hey ScottK :)
[04:17] <Hobbsee> yeah, it's afternoon
[04:19] <Hobbsee> :)
[04:26] <Hobbsee> https://wiki.ubuntu.com/UpToDateAtiNvidiaDrivers
[04:27] <jdong> Hobbsee: if you defer it to backports... *shakes fist* :D
[04:28] <Hobbsee> jdong: which?
[04:28] <jdong> that spec you listed ;-)
[04:28] <somerville32> Mez: Are there plans to backport Exaile?
[04:29] <Hobbsee> jdong: i dont know where it's come from - it's just gone to ubuntu-universe-sponsors list
[04:39] <crimsun> eek, pitti's an ftp admin now (or at least doing syncs)?
[04:39] <bddebian> Yeah apparently :-)
[04:40] <crimsun> looks like a script, actually.
[04:52] <StevenK> Hobbsee: It requires u-u-s to have a wiki page and more importantly, a profile.
[04:52] <Hobbsee> StevenK: true...
[05:33] <LaserJock> bddebian: hmm, what did I have a problem with last time
[05:35] <bddebian> For what libticables2?
[05:35] <LaserJock> yeah
[05:35] <LaserJock> sorry
[05:36] <LaserJock> was afk and read away message
[05:36] <bddebian> The missing pkgconfig file :)
[05:37] <LaserJock> oh yeah
[05:42] <ScottK> Any else (bddebian excluded) up for reviewing a simple Python package?  http://revu.tauware.de/details.py?upid=4194
[05:48] <ScottK> OK.  Well if anyone turns up, I'll be here for a bit seeing if I can find a package I'm up to merging.
[05:48] <bddebian> Thought you were gonna try fnfx? :-)
[05:50] <StevenK> That was me
[05:51] <somerville32> lol
[05:52] <ScottK> bddebian: Do you mind if I do endeavour?  You did it last time.
[05:52] <bddebian> Go for it
[05:52] <StevenK> How 'cott' can be confused with 'teven', I have *no* idea.
[05:52] <bddebian> Damnit, did I do it again??
[05:53] <ScottK> me neither, but 90% pluss of the time when is name is gotten wrong it's Steve or some variation of it...
[05:53] <nixternal> BOO
[05:53] <nixternal> wth
[05:53] <TheMuso> There is something called tab completion. :)
[05:53] <bddebian> Heh, heya nixternal
[05:53] <LaserJock> what?
[05:53] <Hobbsee> LaserJock: [15:42]  <ScottK> Any else (bddebian excluded) up for reviewing a simple Python package?  http://revu.tauware.de/details.py?upid=4194
[05:53] <nixternal> no, the boo was BOO
[05:53] <Hobbsee> tabcompletion on irssi kinda sucks
[05:54] <StevenK> It does not, you tell lies
[05:54] <LaserJock> oh, yeah, I'm firing up my pbuilders now
[05:54] <nixternal> not if you get the silly script to fix the case issue
[05:54] <LaserJock> I *love* irssi tabcompletion
[05:54] <LaserJock> it's the only one that works well for me
[05:54] <nixternal> LaserJock: I find myself trying to tab complete everything I type now
[05:54] <StevenK> Hobbsee: What do you prefer?
[05:55] <nixternal> Hobbsee: spoiled by the dropdown?
[05:55] <Hobbsee> nixternal: yse
[05:55] <Hobbsee> nixternal: yes
[05:55] <nixternal> hehe, that was nice
[05:55] <TheMuso> You just make sure you type the first four or so characters.
[05:55] <StevenK> Hah, I don't think irssi can do that.
[05:55] <LaserJock> I hate dropdowns
[05:55] <LaserJock> so annoying
[05:55] <LaserJock> I don't want to have to arrow or click
[05:55] <LaserJock> I just want to hit tab darnit
[05:55] <nixternal> irssi can't do the drop down, but after a couple of tabs you will eventually make it, unless of course you get bitten by someone with funky case
[05:56] <TheMuso> I dislike the mouse.
[05:56] <TheMuso> Stupidest computer invention ever.
[05:56] <ScottK> Well to get ScottK and StevenK correct one only needs to type two characters...  That appears to be difficult for some.
[05:56] <TheMuso> Irssi usually fixes up the case.
[05:57] <Hobbsee> StevenK: the other sane option would just be to complete to wherever the next character is, and wait for you to type hte next one
[05:57] <Hobbsee> TheMuso: uploaded espeak
[05:57] <StevenK> Hobbsee: Why? The shell does what irssi does.
[05:57] <Hobbsee> StevenK: does it?
[05:57] <LaserJock> yeah
[05:58] <TheMuso> Hobbsee: Thanks.
[05:58] <LaserJock> well, kinda
[05:58] <TheMuso> Gotta love that list of changes I had to do to the damn thing.
[05:58] <StevenK> pb <tab> -> pbuilder <tab again> lists pbuilder pbuilder-upgrade
[05:59] <TheMuso> Hobbsee: You did review the package I hope.
[05:59] <ScottK> If it turns out that no Ubuntu specific changes are required any more, do I just go file a bug that requests a synch vice a merge?
[05:59] <Hobbsee> TheMuso: yeah.  appears to build, cant see anything crazy.
[06:00] <TheMuso> Hobbsee: Righto.
[06:00] <Hobbsee> TheMuso: and you'll into trouble yourself if you broke it :P
[06:00] <StevenK> Heh, "appears to build"
[06:00] <StevenK> The debian/rules just cats a build log, but doesn't do anything
[06:00] <Hobbsee> heh
[06:00] <StevenK> That'd be cool. :-P
[06:01] <Hobbsee> StevenK: no, it runs a build log, but rm -rf's /
[06:01] <Hobbsee> StevenK: package name is beryl :P
[06:01] <StevenK> And if you build packages as real root, you deserve what you get.
[06:01] <Hobbsee> indeed
[06:01] <TheMuso> The only thing I was slightly worried about, is that upstream moved the location of a header file in libespeak-dev. I just want to make sure I covered all my bases. I am pretty sure I did.
[06:02] <TheMuso> Gotta love upstream moving things around, and you have to find out for yourself.
[06:02] <StevenK> TheMuso: Try ALSA some time.
[06:03] <TheMuso> StevenK: lol
[06:03] <StevenK> TheMuso: They moved entire drivers around, and release at least once without updating the Makefiles
[06:03] <TheMuso> eeeew
[06:03] <StevenK> released, even
[06:04] <StevenK> "No wonder it doesn't build, the whole directory doesn't exist. .... Oh wait a moment..."
[06:05] <LaserJock> darn bddebian already acked it
[06:05] <LaserJock> I hate being number 2 ;-)
[06:05] <TheMuso> StevenK: Well as I may have told you, I am trying to get the espeak author to separate voice data compilation routines out of a graphical app, and include them in the espeak source package, so the voice data can actually be built on the fly when the package gets built.
[06:06] <TheMuso> Trouble is, they are tied to damn wx data types.
[06:06] <StevenK> Ewwww
[06:06] <bddebian> LaserJock: Bah, you're #1 baby :-)
[06:06] <ScottK> Anyone?  If Ubuntu specific changes are no longer required for a package on the merge list do I file a bug requesting a synch instead?
[06:06] <bddebian> ScottK: yes
[06:06] <StevenK> Sync, and yes
[06:06] <ScottK> Thanks.
[06:07] <LaserJock> ScottK: just be sure that it builds
[06:07] <TheMuso> StevenK: Yep.
[06:07] <TheMuso> I literally had to ship two copies of the voice data files in the orig tarball, for little and big endian architectures.
[06:07] <TheMuso> I'd rather not have to do that.
[06:07] <StevenK> At least it doesn't hook to perl datatypes
[06:07] <TheMuso> Well, for ppc anyway
[06:07] <ScottK> LaserJock: Thanks.
[06:08] <StevenK> TheMuso: In Perl, any variable translates to one of two structs, where one of the members is "magic" that is a function pointer
[06:09] <StevenK> And people wonder why I'm insane. It's all Perl's fault.
[06:10] <TheMuso> StevenK: riiight
[06:11] <StevenK> TheMuso: Is that in reference to all what I just said? :-)
[06:11] <TheMuso> StevenK: yeah
[06:14] <TheMuso> You know,not having a maintainer for any particular universe package is a good idea, but someone who is dedicated to maintaining a package is a good thing, as they get to know the package source, and can work with upstream to fix bugs.
[06:14] <TheMuso> case in point, me and espeak.
[06:15] <Hobbsee> TheMuso: definetly true
[06:19] <Hobbsee> uh, yeah
[06:19] <ScottK> Endeavour builds then.  Here's the bug #81795:
[06:19] <Ubugtu> Malone bug 81795 in endeavour "endeavour: sync new Debian version (2.7.5-1)" [Undecided,Unconfirmed]  https://launchpad.net/bugs/81795
[06:19] <TheMuso> Is the motu council happening yet/
[06:20] <LaserJock> just waiting on TB
[06:20] <TheMuso> Right.
[06:21] <StevenK> LaserJock: Really? The MOTU Council need to be diagnosed with it?
[06:21] <TheMuso> StevenK: rofl
[06:21] <LaserJock> :p
[06:23] <ScottK> LaserJock: Have you finished (either completed or as much, if any as you have time for) looking at http://revu.tauware.de/details.py?upid=4194? If you have, I'm going to go to bed (it's getting late here).
[06:24] <LaserJock> I just left my comment
[06:24] <ScottK> Thanks.
[06:25] <ScottK> LaserJock: I gather you think it should be optional (vice extra)?  I debated that when I did it.
[06:26] <LaserJock> optional is normal
[06:26] <ScottK> OK.
[06:26] <ScottK> Fixing now...
[06:26] <LaserJock> extra is for something the conflicts with the packages in the other Priorities
[06:27] <LaserJock> *that
[06:27] <ScottK> OK.
[06:28] <ScottK> It depends on a package that's in extra.
[06:28] <LaserJock> I don't think that should matter
[06:28] <ScottK> OK.
[06:29] <LaserJock> oh
[06:29] <LaserJock> "Packages must not depend on packages with lower priority values "
[06:29] <ScottK> I did that one too.
[06:29] <ScottK> That one exists in Debian.  I'll go double check what the last Debian package did and match that.
[06:30] <ScottK> The package from Debian is in extra, so I think I'm stuck with that.
[06:31] <LaserJock> yeah
[06:37] <ScottK> LaserJock: http://revu.tauware.de/details.py?upid=4201 is ready for another look if you would...
[06:52] <ScottK> bddebian: How about I take a shot at merging Courier?
[06:53] <bddebian> Didn't I already do that?
[06:53] <bddebian> Or is it an updated one?
[06:54] <ScottK> It's an updated one.  You did it last.
[06:54] <ScottK> Looks like all of the changes have to stay.
[06:55] <bddebian> Sure
[06:57] <bddebian> If someone wants to look at tamil-gtk2im.. If you know shell/POSIX stuff it should be pretty easy.  For some reason in debian/rules it does sh compile-gtk2im.sh.  Inside compile-gtk2im.sh it does sh libtool ....  For some reason dash doesn't like it.
[07:08] <ScottK> bddebian: Just about done with courier.  If you wouldn't mind relooking at http://revu.tauware.de/details.py?upid=4201?, I'd appreciate it.
[07:08] <bddebian> I'll take a look tomorrow.  I have GOT to get to bed.
[07:08] <ScottK> OK.
[07:08] <ScottK> Thanks
[07:09] <bddebian> NP
[07:09] <bddebian> Gnight folks
[07:11] <LaserJock> arggg
[07:11] <LaserJock> I was just going to tell him to upload his package
[07:14] <somerville32> crimsun, can you upload https://launchpad.net/ubuntu/+source/mousepad/+bug/56161 ? Please :)
[07:14] <Ubugtu> Malone bug 56161 in mousepad "Segfault when saving files on AMD64" [Medium,In progress]
[07:18] <ScottK> LaserJock: Thanks for taking another look and advocating.
[07:18] <LaserJock> ScottK: np
[07:19] <crimsun> somerville32: uploaded.
[07:20] <somerville32> ty :)
[07:20] <ScottK> courier is going to take a while to build.  I think I'm going to bed...
[07:21] <ScottK> Good night everyone.
[08:46] <ademan> ah, i'm back
[08:50] <ademan> does http://www.codeblocks.org work for you guys?
[09:08] <ademan> course as soon as i get back LaserJock is gone :-p
[09:08] <Simon80> http://revu.tauware.de/details.py?upid=4203
[09:08] <Simon80> review me :)
[09:08] <Simon80> I'm going to bed
[09:11] <Simon80> please and thank you
[09:13] <ademan> Simon80: wish i could but i suck haha
[09:32] <ademan> can anyone tell me why my package wants to install it's libs to /usr/share/codeblocks/*  ?
[09:32] <ademan> and more importantly, where should it go (/usr/lib/codeblocks/* ?)  and what file controls this?
[09:45] <afflux> ademan: if I'm not wrong, libs should go to /usr/lib. You can control this by "make install"ing them to debian/<packagename>/usr/lib
[09:46] <ademan> yeah but i don't see anything like that in debian/rules or makefile.am
[09:52] <lucas> Adri2000: on alioth, project name is pkg-multidistrotools
[10:08] <ademan> how might i change wherre it installs to?
[10:13] <imbrandon> hrm
[10:22] <imbrandon> crimsun / ajmitch , do you know how a menu like this would be created ( it launches automaticly on ssh login ) http://www.imbrandon.com/misc/ssh-menu.png
[10:23] <imbrandon> i have looked in the ~/.bash* and seen nothing that starts it , or even what it is ( e.g. bash script or a actual program etc )
[10:23] <imbrandon> but i wanna make something like it myself
[10:23] <imbrandon> any clues?
[10:23] <imbrandon> ( or anyone ^^ )
[10:24] <coNP> imbrandon: maybe it is the login shell?
[10:24] <imbrandon> zomg, your right
[10:24] <imbrandon> thanks
[10:24] <imbrandon> haha
[10:25] <imbrandon> i should have thought of that
[10:25] <coNP> yw :)
[10:29] <Amaranth> ooh, shiny
[10:35] <coNP> hey, MOTUs, bug 2415 seems to be fixed
[10:35] <Ubugtu> Malone bug 2415 in openbox "windows do not appear in gnome-panel workspace switcher" [Medium,Confirmed]  https://launchpad.net/bugs/2415
[10:35] <coNP> however it is assigned to MOTU, may I switch it to fix released?
[10:36] <imbrandon> where did you test it coNP
[10:37] <imbrandon> e.g. on feisty or edgy ?
[10:37] <imbrandon> and if on edgy i would say yes, fix released
[10:37] <coNP> imbrandon: I guess on dapper, edgy, feisty
[10:37] <coNP> I use openbox
[10:37] <coNP> on all of these
[10:38] <coNP> and no problems with gnome-panel
[10:39] <coNP> okay, imbrandon I will make it fixed, if you don't mind
[10:39] <coNP> should I assign it to nobody?
[10:39] <imbrandon> no
[10:39] <imbrandon> never assign a bug to anyone
[10:40] <imbrandon> but yes mark it fixed if you wish or ask the reporter to confirm it was fixed now
[10:42] <coNP> imbrandon: so leave it assigned to MOTU?
[10:43] <imbrandon> yes, you should never change the assignment of a bug if you are not the person thats doing it, e.g. unless you are assigning a bug to your self you never never never change that fienld
[10:43] <imbrandon> field*
[10:43] <coNP> okay, imbrandon
[10:43] <coNP> I understand
[10:43] <coNP> now, finally :)
[10:43] <imbrandon> heh
[11:10] <afflux> review me please :) http://revu.tauware.de/details.py?upid=4200 -- thank you
[11:12] <Amaranth> coNP: The problem was on amd64
[11:12] <Amaranth> coNP: you say it's fixed on x86, that's not the bug :)
[11:15] <coNP> Amaranth: oh. My mistake.
[11:18] <coNP> Amaranth: isn there a way to assign this bug to amd64 build (and not to the source package)?
[11:19] <Amaranth> no
[11:19] <Amaranth> it's a bug in the source package
[12:06] <neutrinomas1> can somebody please take a look at bug 57875 ? It seems to affect a lot of people ... (it's not an issue for me and I'd fix it myself if I could )
[12:06] <Ubugtu> Malone bug 57875 in azureus "Azureus does not start" [High,Confirmed]  https://launchpad.net/bugs/57875
[12:48] <AnAnt> hello
[12:48] <AnAnt> may someone remove the softbeep package that I just uploaded
[12:48] <AnAnt> I uploaded it by mistake to REVU
[12:48] <Hobbsee> AnAnt: to revu?
[12:48] <AnAnt> Hobbsee: thanks
[12:51] <Hobbsee> AnAnt: hasnt hit revu yet - how many min ago did you upload?
[12:51] <AnAnt> Hobbsee: few secs
[12:52] <Hobbsee> ah, that's why
[12:55] <Hobbsee> cypher1: are you cypherbios too?
[02:03] <geser> coNP: I just wanted to your replaces/conflicts for xchat-systray
[02:03] <geser> but I can't get it installed as xchat-systray is gone in feisty
[02:05] <coNP> geser: okay
[02:06] <coNP> geser: however, I am not sure, that this will clean old xchat-systray packages making a dist-upgrade
[02:06] <geser> we still need it for the upgrade
[02:06] <geser> I'm considering to upload it but I can't test it
[02:07] <coNP> geser: okay I see, I guess noone can
[02:07] <coNP> geser: except someone using e.g. herd2
[02:07] <coNP> with no updates since
[02:08] <geser> fortunately LP has still the old debs
[02:08] <coNP> nice :)
[02:11] <geser> coNP: here are my test results:
[02:11] <geser> dpkg: considering removing xchat-systray in favour of xchat ...
[02:11] <geser> dpkg: yes, will remove xchat-systray in favour of xchat.
[02:11] <geser> ic  xchat-systray          2.4.5-6ubuntu1         xchat systray notification icon
[02:11] <geser> only the config-files are left
[02:11] <coNP> geser: what do you think? Is it right?
[02:12] <coNP> Did you --purge-d them? Or is it supposed to to do?
[02:12] <geser> I don't know but I'd say it's ok
[02:26] <coNP> thanks geser
[02:27] <geser> np
[02:37] <co-NP> geser: can you take a look at bug 45171? It is not urgent, of course.
[02:37] <Ubugtu> Malone bug 45171 in openbox "openbox cannot catch gnome-screenshot shortcut" [Low,Confirmed]  https://launchpad.net/bugs/45171
[02:45] <siretart> when changing the source of an yet unmodified debian package in ubuntu, are we supposed to change the maintainer field now?
[03:04] <ScottK> Good morning.
[03:19] <ScottK> Last night I started working on merging courier.  I'm afraid I may have bitten off more than I can chew at this point.  I'd appreciate it is someone experienced in doing merges would look at the list of errors lintian threw when I built the binary: http://pastecode.com/12715 - I'm guessing that I need to fix the missing build dependency, but I have no idea which, if any of the warnings would need to be fixed as part of the
[03:19] <ScottK> Note that with the missing build-dep installed the package appears to have built successfully.
[03:51] <Liberax> anybody with pptp network manager on an ubuntu 64bit?
[03:57] <ScottK> Adri2000: Thanks for the kick in the head about Bug #81795 - I think I stayed up to late last night trying to do merges.  It's fixed now.
[03:57] <Ubugtu> Malone bug 81795 in endeavour "endeavour: merge (2.7.5-1ubuntu1)" [Undecided,Unconfirmed]  https://launchpad.net/bugs/81795
[03:58] <Adri2000> :)
[04:48] <pochu> hi guys!
[04:48] <pochu> I've a problem while building a package
[04:48] <pochu> the package builds fine, but it says this:
[04:49] <pochu>
[04:49] <pochu> dh_gencontrol -ptracker
[04:49] <pochu> dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
[04:49] <pochu> dh_md5sums -ptracker
[04:49] <pochu> dh_builddeb -ptracker
[04:49] <pochu> dpkg-deb: construyendo el paquete `tracker' en `../tracker_0.5.4-0ubuntu1_i386.deb'.
[04:49] <pochu>
[04:49] <pochu> what do you think about that?
[04:49] <pochu> unknow substitution variable...
[04:50] <coNP> hi phanatic
[04:50] <phanatic> hey coNP
[05:16] <coNP> Hey! Any sponsors up to fix bug 45171?
[05:16] <Ubugtu> Malone bug 45171 in openbox "openbox cannot catch gnome-screenshot shortcut" [Low,Confirmed]  https://launchpad.net/bugs/45171
[05:16] <crimsun> I see you're volunteering.
[05:16] <ScottK> Heh
[05:16] <coNP> crimsun: I did what I could do. Cannot go any further without the blessing of a MOTU
[05:17] <coNP> I need the MOTU power now :)
[05:18] <ScottK> CoNP: Until I looked at the bug, I didn't realize you'd already done a patch and wanted someone to apply it.  I thought you were looking for someone else to develop the fix.
[05:19] <coNP> ScottK: Sorry, I was not clear enough, for sure.
[05:21] <ScottK> At this point I'd just sit back and wait.  IME they usually get around to applying such patches reasonably quickly.
[05:21] <ScottK> Maybe find a MOTU to bug if it's not applied tomorrow.
[05:23] <coNP> Okay, thanks.
[05:28] <givre> Hello all
[05:28] <ScottK> Hello
[05:29] <givre> how can i get a new version of a package in main. Should i use the Sponsorship Process or should i go to REVU ?
[05:29] <givre> the package in question is fuse
[05:29] <givre> version in debian is 2.5.3 but latest version is 2.6.1
[05:29] <crimsun> this question has arisen before, and I asked the person to check the dependencies.
[05:30] <crimsun> there was no response.
[05:31] <givre> crimsun: dependencies of 2.6.1 are the same of 2.5.3
[05:31] <crimsun> does it integrate with fuse's rdeps?
[05:32] <givre> of course
[05:32] <givre> i didn't fully test, but i don't see why there should be a problem
[05:32] <crimsun> it's a main package; regression testing is ... encouraged.
[05:33] <jdong> is it backwards-compatible with existing fuse stuff?
[05:33] <jdong> and you mean fuse-utils?
[05:33] <jdong> and libfuse2...
[05:33] <jdong> the userspace stuff....
[05:33] <givre> right
[05:35] <givre> 2.6 is backwards-compatible with 2.5
[05:37] <givre> i can ask Miklos to be sure, but all virtual fs i use works with 2.5 & 2.6
[05:37] <crimsun> givre: although a few of us have the ability to update it, none of us are going to update it without seeing positive testimony and the most recent uploader's blessing
[05:38] <crimsun> givre: in this case, ask fabbione if he considers an update to 2.6.1 a priority
[05:39] <givre> crimsun: right
[05:41] <givre> crimsun: ok, so i guess what i have to do is :
[05:41] <givre> - put my package in revu
[05:41] <givre> - explain why it should be update
[05:41] <givre> - ask fabbione to have a look at it
[05:42] <givre> thanks crimsun
[05:58] <ScottK> crimsun: Have you got a moment to help me with a merge problem?
[06:07] <ScottK> OK.  I guess he's really away...  Anyone?  How much packaging fixing is one expected to do when merging?  My merge of courier builds, but lintian is extremely whiny: http://pastecode.com/12719 Should I just leave this package for someone more experienced?
[06:08] <pirast> crimsun, moved
[06:10] <gnomefreak> guys crimsun is away atm please see /whois crimsun for more details
[06:10] <pirast>  /whois crimsun
[06:10] <pirast> ugh
[06:10] <pirast> gnomefreak. thanks
[06:10] <gnomefreak> yw
[06:18] <geser> ScottK: the more you differ from Debian the more has to be merged the next time, so only fix real problems
[06:19] <ScottK> geser: Any thoughts on if any of those problems - http://pastecode.com/12719 - qualify as real?
[06:35] <geser> ScottK: I don't know any details about this warnings
[06:36] <ScottK> OK.  Thanks for looking.
[07:01] <crimsun> pirast: which?
[07:02] <pirast> crimsun, dos one for vlc 0.8.6a..
[07:02] <pirast> works against my patched vlc
[07:08] <crimsun> we need to get http://sam.zoy.org/zzuf/ into universe.
[07:17] <LaserJock> crimsun: I'm a little sketchy on what exactly it does
[07:17] <LaserJock> crimsun: how does adding random bits to user input help find bugs/security holes?
[07:19] <crimsun> LaserJock: it helps identify which functions need to have input validation fixed.
[07:21] <ScottK> LaserJock: I'm try to merge courier and am getting a huge number of lintian warnings when I build the binary.  I'd appreciate it if you would take a look and give me some advice of which of those issues are significant enough that I should add an Ubuntu change for it - http://pastecode.com/12719
[07:27] <siretart> crimsun: zzuf is on its way to debian. we can sync it from there then
[07:31] <LaserJock> ScottK: holy cow
[07:31] <LaserJock> that is a lot
[07:31] <ScottK> Yeah.
[07:31] <LaserJock> they are all Warnings though
[07:31] <ScottK> Yes.  I fixed the errors.
[07:32] <ScottK> So do I say builds with no errors and call it good enough or do I need to fix some of that stuff?
[07:32] <LaserJock> well, we try to minimize divergence
[07:33] <LaserJock> you should look for Debian bugs for those
[07:33] <LaserJock> a compat of 2 and standards version of 3.5 sounds like it's not even being maintained
[07:34] <LaserJock> but that hardly seems possible, courier is a very common app
[07:34] <ScottK> Yes.  And the Debian update is a Debian only change, so someone is maintaining it.
[07:35] <LaserJock> well, I personally leave Debian stuff alone unless I really know what I'm doing
[07:35] <LaserJock> perhaps couriers build system doesn't behave nicely or something
[07:36] <ScottK> A couple of the issues have bugs, including one filed by siretart over a year ago...
[07:37] <LaserJock> geeze, the BTS page looks aweful
[07:37] <enyc> hrrm debian always seem to have phun getting rid of RC bugs...
[07:37] <enyc> people keep adding more rc bugs as fast as they are going away lol
[07:37] <LaserJock> 143 bugs, 1 Fixed or Pending
[07:38] <LaserJock> 15 patches in BTS
[07:39] <LaserJock> he hd 12 uploads in 2006 and still all that?
[07:39] <LaserJock> *had
[07:41] <ScottK> Any suggestions?
[07:43] <LaserJock> ScottK: minimize divergence, try to poke upstream
[07:44] <LaserJock> that's about all I've got
[07:45] <ScottK> OK.  I think I'll go with "builds with no errors and call it good enough" and provide a patch for the merge.  Then see about bugs for upstream.  Hopefully enough courier users will try it out before Feisty gets released to uncover any serious excitement...
[07:58] <ademan> my package wants to install libraries to /usr/share/codeblocks/*, it should be /usr/lib/codeblocks/*    where might i change this?
[08:13] <ScottK> ademan: I think you want to look at man dh_install.
[08:21] <geser> ademan: check the Makefile
[08:26] <tsmithe> could someone do a quick revu for me?
[08:31] <ademan> geser: i'll paste Makefile.am?
[08:31] <ademan> or do i want Makefile.in?
[08:32] <ademan> hrm, there is no Makefile.in
[08:32] <ScottK> Howdy bddebian
[08:33] <ademan> http://rafb.net/p/mMjkEm70.html   i don't see anything that would affect that do you?
[08:33] <bddebian> Heya gang
[08:33] <bddebian> Hi ScottK
[08:33] <LaserJock> hi bddebian
[08:33] <ScottK> bddebian: Congrats on your package...
[08:33] <bddebian> Heya LaserJock
[08:34] <bddebian> ScottK: What package is that?
[08:34] <LaserJock> bddebian: did you read your REVU emails yet?
[08:34] <ScottK> bddebian: The lib whatever it was you've been messing with.
[08:34] <geser> ademan: me neither
[08:34] <ScottK> Apparently not.
[08:35] <ademan> wanna see debian/rules?
[08:35] <ScottK> bddebian: After you read your REVU e-mail, would you please relook at http://revu.tauware.de/details.py?upid=4201?  It's now looking for you to be 2nd advocate.
[08:35] <bddebian> The only one I saw was aptoncd
[08:35] <ademan> http://rafb.net/p/4Bw55Y47.html  i don't see where it might happen here either
[08:35] <LaserJock> bddebian: I acked libticables and told you to upload it ;-)
[08:36] <ademan> man dh_install seemed to suggest there should be a debian/package.install  but i didn't see one
[08:36] <LaserJock> bddebian: about 2 minutes after you left last night
[08:36] <bddebian> LaserJock: Ah cool thanks.  Now I can do tilp2 :)
[08:36] <LaserJock> ademan: do you have an install?
[08:37] <LaserJock> debian/install I mean
[08:37] <ScottK> bddebian: After you catch up on my stuff, OK?
[08:37] <bddebian> ScottK: Sure :-)
[08:37] <ademan> LaserJock: nope
[08:38] <LaserJock> ademan: well, it get's the dir for somewhere, grep for "share"
[08:38] <ademan> in rules? or what?
[08:38] <LaserJock> I'm guessing that it's setting the lib dir the same as data dir
[08:38] <LaserJock> no, the source
[08:38] <geser> ademan: check the defaults where it wants to install
[08:39] <LaserJock> as long as debian/rules isn't actually moving those files it's determined by the Makefile
[08:39] <ademan> i posted the makefile above though, or are there more makefiles in src?
[08:39] <geser> a good start would be the Makefile (the install target)
[08:40] <LaserJock> ademan: grep it though, trying to find anything in the whole Makefile is difficult
[08:40] <geser> ademan: you need the one created by automake
[08:40] <ademan> LaserJock: how would i grep file contents? (sorry)
[08:40] <ademan> geser: oh, so no Makefile.am?
[08:41] <LaserJock> grep src *
[08:41] <LaserJock> ademan: no
[08:41] <LaserJock> look at configure, etc.
[08:41] <tsmithe> anyone? anyone at all? (revu'age, please)
[08:41] <LaserJock> just grep the whole darn thing
[08:41] <coNP> tsmithe: you need a MOTU, don't you?
[08:41] <LaserJock> ademan: grep share * , my bad
[08:42] <ademan> hrm, well it seems to clean up Makefile(s) during clean in rules
[08:42] <tsmithe> coNP, yup
[08:42] <tsmithe> :)
[08:42] <ademan> don't you think?  because there definitely aren't any Makefile(s) laying around
[08:43] <LaserJock> ademan: you're looking for things like PREFIX or DESTDIR or LIBDIR
[08:43] <LaserJock> ademan: I said grep *
[08:43] <ademan> k
[08:43] <bddebian> tsmithe: Which package?
[08:43] <tsmithe> bddebian, thanks; you've done it already ;)
[08:44] <ademan> i got a bunch of cbp and bat files, aren't those windows specific?
[08:45] <bddebian> ademan: Did you say that there are configure.am files?
[08:46] <ScottK> bddebian: Did you upload it?
[08:46] <ademan> none, did you mean Makefile.am?  definitely no configure.am
[08:47] <bddebian> ScottK: Not yet
[08:47] <ademan> no configure.in either
[08:47] <bddebian> ademan: There is a Makefile.am?
[08:47] <ScottK> bddebian: OK.  I like the yet.  I'll be patient.
[08:48] <ademan> there's a lot of them, but none contain "share" apparently
[08:48] <ademan> "grep share * | grep -i Makefile.am" would get me that no?
[08:50] <bddebian> ademan: Have you run autoreconf -f -i?
[08:50] <ademan> in rules or just straight up? i've done neither though
[08:50] <ademan> unless its in rules and i missed it
[08:50] <ademan> it's not in rules for sure
[08:53] <bddebian> No I mean from the source dir.  Do you have your files posted somewhere?
[08:55] <ademan> bddebian: no, how could/should i?
[08:55] <ademan> i could upload the dir to my webserver, would that work?
[08:56] <bddebian> Have you gotten it to create the .dsc and .diff.gz?
[08:57] <ademan> yep
[08:57] <ademan> i've build the entire package
[08:57] <ademan> i've got a deb sitting around
[08:58] <ademan> but lintian errored all over my face
[08:58] <ademan> thats how i found out about the /usr/share libraries
[09:10] <ScottK> bddebian: Thanks.
[09:11] <ScottK> Laserjock: Are you up for another review while I'm wrestling with the courier merge patch? http://revu.tauware.de/details.py?upid=4179
[09:13] <bddebian> ademan: Just post the .orig.tar.gz, .diff.gz and .dsc somewhere
[09:31] <ScottK> hey bddebian: Thanks again.
[09:31] <bddebian> NP
[09:47] <Simon80> hey, bddebian, sorry, but can you rereview my package? I added some modifications from Gentoo to add support to the MX300 and MX518, and I changed the description slightly
[09:49] <bddebian> From Gentoo?  Why? :-)
[09:49] <Simon80> lol
[09:49] <Simon80> yes? no?
[09:49] <Simon80> :)
[09:50] <bddebian> Which package?
[09:52] <ScottK> bddebian: It's http://revu.tauware.de/details.py?upid=4203
[09:52] <ScottK> Simon80: Don't advocate your own packages.  MOTUs are the one that are supposed to do that.
[09:53] <Simon80> hehe, I can delete that
[09:53] <Simon80> my logic was that if it were wrong, the system wouldn't let it happen :)
[09:54] <ScottK> In the system it doesn't matter, it just makes it harder for a MOTU to decide if the package is ready for upload, AFAICT.
[09:54] <Simon80> oh
[09:55] <ScottK> OTOH, maybe it annoys them and they review my package instead, so wait, go ahead and do that ;-)
[09:56] <ademan> bddebian: alright will do
[09:58] <bddebian> ScottK: hehe
[10:00] <pirast> Nafallo, ping
[10:05] <ScottK> I've taken merging courier as far as I can go.  bddebian: Since you merged it last time, you might want to have a look.  Bug #81799.
[10:05] <Ubugtu> Malone bug 81799 in courier "Courier version courier_0.53.3-3ubuntu1 requires merge" [Undecided,Unconfirmed]  https://launchpad.net/bugs/81799
[10:05] <Simon80> anyone else available for review?
[10:06] <Simon80> bddebian: thanks, btw
[10:06] <bddebian> Simon80: NP
[10:07] <luckyone> hello Masters of the universe
[10:07] <bddebian> Hello luckyone
[10:08] <luckyone> does anyone know of any problems with sane or libsane in 32-bit edgy?
[10:08] <luckyone> I am having this problem - http://ubuntuforums.org/showthread.php?t=299347&page=2
[10:08] <luckyone> and, I have no clue how to debug it
[10:10] <Adri2000> Simon80: why do you use this hack in debian/rules to install the man page?
[10:13] <bddebian> luckyone: libsane is a main package
[10:13] <ademan> bddebian: i can't get into my web host for some reason, any reccomendations?
[10:13] <Simon80> Adri2000: I don't know a better way to do it
[10:14] <luckyone> so, ubuntu main channel would be where I need to get help
[10:14] <luckyone> ok, thank you MOTU
[10:14] <luckyone> keep up the great work
[10:14] <Adri2000> Simon80: DEB_INSTALL_MANPAGES_logitech-applet := debian/logitech_applet.1
[10:18] <Simon80> I'll try that now
[10:25] <Adri2000> Simon80: also, 0.4test1 means there will be 0.4test2 ... and finally the final stable 0.4?
[10:26] <Simon80> Adri2000:no maintainer
[10:26] <Adri2000> :-/
[10:26] <Simon80> so, yes, but no
[10:26] <Simon80> it's ok, there's another package that has maintainers, but I'll package it for feisty+1
[10:26] <Adri2000> if yes, version should be 0.4~test1
[10:27] <Simon80> ah
[10:27] <Simon80> I can do that
[10:28] <Simon80> see, the manpage hack, I totally blame lack of docs
[10:29] <Simon80> it's frustrating, really
[10:29] <Adri2000> grep /usr/share/cdbs/, all the doc is there
[10:29] <Simon80> $ grep manpage /usr/share/cdbs/ -ri
[10:29] <Simon80> /usr/share/cdbs/1/rules/debhelper.mk:   dh_installman -p$(cdbs_curpkg) $(DEB_INSTALL_MANPAGES_$(cdbs_curpkg))
[10:30] <Simon80> that's surprisingly the fastest documentation ever, if you happen to grep for the right thing
[10:32] <Simon80> lintian's complaining about my version
[10:32] <Simon80> bad-version-number 0.4~test1-0ubuntu1
[10:33] <Simon80> I don't think that's the first time though
[10:33] <bddebian> ademan: Upload it to REVU, we can look at it there if you want
[10:33] <Simon80> done
[10:33] <Adri2000> Simon80: you are using edgy?
[10:33] <Simon80> yeah
[10:34] <Adri2000> that's why
[10:34] <Simon80> oh, you weren't talking to me, bddebian, lol
[10:34] <Adri2000> your lintian is too old
[10:34] <Simon80> yep
[10:34] <Simon80> I figured
[10:34] <Simon80> k, I just have to wait for revu to update
[10:35] <ScottK> Simon80: You might want to make a Feisty chroot to work in - https://wiki.ubuntu.com/DebootstrapChroot
[10:35] <Simon80> maybe
[10:35] <Simon80> I'll look into it for feisty+1
[10:36] <Simon80> cause I'm only packaging new apps
[10:36] <Simon80> and the deadline is whenever it is, like, right now :)
[10:36] <Simon80> for upstream freeze
[11:05] <Simon80> ok, bddebian, Adri2000: http://revu.tauware.de/details.py?upid=4207
[11:05] <Simon80> thanks
[11:05] <Simon80> errr, I should delete the hack instead of commenting it out :(
[11:09] <Simon80> http://revu.tauware.de/details.py?upid=4208
[11:09] <Simon80> last one!
[11:09] <Simon80> lol
[11:22] <pirast> could anyone who is in ubuntu-qa approve the nominations in bug 76094?
[11:22] <Ubugtu> Malone bug 76094 in tor "Tor <IP_ADDRESS> fixes HttpProxyAuthenticator privacy flaw" [Undecided,Fix released]  https://launchpad.net/bugs/76094
[11:22] <pirast> ,please ;-)
[11:24] <LaserJock> pirast: I'm not sure who can approve nominations
[11:25] <Adri2000> core-devs
[11:25] <pirast> mhm
[11:25] <Adri2000> ubuntu{qa,dev} can't
[11:25] <pirast> i though that all people who are in ubuntu-qa can
[11:25] <Adri2000> motu-sru neither
[11:25] <pirast> :-(
[11:25] <LaserJock> I can't
[11:26] <LaserJock> and I'm ubuntu-dev
[11:26] <pirast> because the security bug should be nominated for edgy, dapper and breezy..
[11:26] <pirast> thanks anyway.. ill ask in ubuntu-devel
[11:26] <somerville32> pirast: For security issues, see pitti
[11:26] <LaserJock> it shouldn't have a Feisty nomination though I shouldn't think
[11:26] <keescook> pirast: got it, one sec
[11:27] <pirast> keescook, thanks..
[11:28] <keescook> no problem!  thanks for tracking the problem.  :)
[11:28] <pirast> keescook, new mail at security-review ;-)
[11:28] <keescook> pirast: hehe okay, I'll check it out
[11:28] <pirast> it somehow does not really makes sense to fix universe security bugs in breezy, does it?
[11:29] <LaserJock> pirast: btw, I think in the future more people will be able to accept nominations (they might allow anybody to nominate in the future)
[11:29] <LaserJock> pirast: why not?
[11:29] <pirast> LaserJock, they already had I think..
[11:30] <LaserJock> sorry, I mean you wouldn't have to get them accepted
[11:30] <LaserJock> people could just set a target release
[11:30] <pirast> LaserJock, that was possible some time ago
[11:30] <LaserJock> yes
[11:30] <LaserJock> and they are thinking of bringing it back
[11:31] <pirast> ah okay..
[11:31] <keescook> pirast: if it's easy, go for it, but I tend to recommend focusing on LTS and current stable.
[11:31] <LaserJock> not sure quite yet
[11:31] <pirast> sorry, somewhat tired
[11:31] <pirast> LaserJock, http://fridge.ubuntu.com/node/721/results.. It would be nice if LTS + Edgy universe had less bugs first.. And we should concentrate on that first,  I think
[11:32] <LaserJock> well sure, but there's no inherent reason to not fix something in Breezy
[11:32] <LaserJock> pirast: well, that vote is also very inaccurate
[11:33] <pirast> yeah.. there are probably lots of ubuntu fans which want to have the latest and greatest..
[11:33] <pirast> see how many feisty users there are ;-)
[11:36] <LaserJock> pirast: that poll only shows 154 Feisty users ;-)
[11:37] <pirast> LaserJock, but that are 14% of all voters :-P
[11:37] <LaserJock> ah, but that's where it get's sticky
[11:38] <pirast> yeah..
[11:38] <pirast> you're right
[11:38] <LaserJock> lies, damn lies, and statistics ;-)
[11:44] <gouki> I'm having trouble deciding which 'section' I should enter. Any links to help me out?
[11:45] <gouki> Sorry, I'm creating a package from scratch.
[11:45] <Adri2000> http://packages.debian.org/unstable/
[11:45] <gouki> Adri2000: Thank you.
[11:49] <Simon80> so, can any two MOTUs review my package again?
[11:49] <Simon80> http://revu.tauware.de/details.py?upid=4208
[11:50] <Adri2000> Simon80: are you sure that DEB_INSTALL_CHANGELOGS_ALL      := ChangeLog is needed?
[11:51] <Simon80> uh
[11:51] <Simon80> not sure actually
[11:51] <Simon80> thanks, dh_make :)
[11:52] <Simon80> well, without it, the changelog probably wouldn't get into the docs
[11:52] <Simon80> so I'm going to say yes
[11:52] <Adri2000> have you actually tried without it?
[11:53] <Simon80> I'll try now
[11:54] <Simon80> seems to work without it
[11:55] <Simon80> new upload?
[11:56] <Adri2000> wait, I'm checking if I have not missed anything
[12:00] <Adri2000> looks fine
[12:10] <pirast> if now a package gets updated in debian, will it arrive in feisty?
[12:11] <Adri2000> not automatically
[12:11] <Adri2000> !seen Fujitsu
[12:11] <ubotu> I last saw Fujitsu (n=root@ubuntu/member/fujitsu) 1d 18h 41m 50s ago, quiting: "leaving"
[12:12] <Adri2000> uhuh, "root", that's bad :)


[01:31] <Salt> just stumbled upon U+1, was wondering if things are on track for the 26th?
[02:46] <cprofitt> is the iso.qa.ubuntu.com server down for others?
[02:48] <kanliot> yes
[02:49] <cprofitt> I was just about to submit three test results... grr
[03:03] <cprofitt> kanliot: its back up
[11:40] <astraljava> Hey, any ETA for the RC opening on iso.qa.ubuntu.com?
[12:04] <jibel> astraljava, tomorrow https://lists.ubuntu.com/archives/ubuntu-release/2012-April/001083.html
[12:06] <astraljava> jibel: Thanks, I believe I have accidentally deleted that mail.
[12:10] <jibel> np
[12:33] <stgraber> jibel: any interesting installation bug that's not already on rls-p-tracking? (checking before I start looking at lower priority bugs)
[12:35] <jibel> stgraber, nope, only boring bugs. I'm confirming the missing oem-config-slideshow ATM. you'll have a new one to work on soonish :)
[12:36] <stgraber> jibel: are you testing that on a media that has matching oem-config and ubiquity versions?
[12:37] <stgraber> jibel: we tracked down your failed OEM install to /pool being out of sync with the livefs, expecting a respin to it soon
[12:37] <stgraber> oh, it already did apparently, /me syncs
[12:38] <stgraber> ah, but ubiquity's version is still wrong...
[12:38] <stgraber> so no point testing 20120418.1 then
[12:39] <jibel> stgraber, I tried alternate
[12:40] <jibel> stgraber, it's only wrong on i386, 64bit is ok
[12:41] <jibel> stgraber, alternate is not affected by the non-matching version of ubiquity
[12:42] <stgraber> jibel: right
[12:43] <stgraber> jibel: and you reproduced the missing slideshow using alternate?
[12:45] <stgraber> jibel: ah, I see, bug 984829. That's fixed in ubiquity trunk though
[12:46] <jibel> stgraber, is it something allowed to have different version of the same package on the same buildnumber of an image but on different arch ?
[12:46] <jibel> eg ubiqtuiy 2.10.12 on 20120418.1 i386 and 2.10.13 on 20120418.1 amd64
[12:47] <stgraber> it happens when the livefs fails to build, the cd build then takes an older livefs
[12:47] <stgraber> so 20120418.1 i386 has 20120418's livefs
[12:48] <stgraber> 20120418.2 is building now which should build fine and be consistent on all architectures
[12:48] <jibel> ah ok. maybe that's something we could check automatically and raise an 'inconsistent image' failure
[12:48] <stgraber> we get e-mail notifications for livefs build failures
[12:49] <stgraber> but yeah, might be worth exporting that flag to cdimage.u.c
[13:22] <alourie> balloons: hey Nick
[13:22] <balloons> alourie, good to see you!
[13:22] <balloons> how's everything?
[14:39] <stgraber> jibel: Steve asked me to help doko with bug 983981 but he's apparently waiting for some answers from you :)
[14:45] <astraljava> balloons: Weren't we supposed to have a meeting already?
[14:47] <jibel> stgraber, yes, sorry, -ENOTENOUGHARMS
[14:56] <balloons> astraljava, i didn't get anything on my popup
[14:56] <balloons> sigh..
[14:56] <balloons> I agree, we were
[15:00] <phillw> balloons: I'd have started it, but was feeding time for me :/
[15:01] <balloons> no worries.. I feel silly.. everyone is really busy this week
[15:01] <balloons> lots of testing going on.. and me too.. time is just flying by this morning
[15:01] <balloons> #startmeeting ubuntu qa community meeting
[15:01] <meetingology> Meeting started Wed Apr 18 15:01:50 2012 UTC.  The chair is balloons. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[15:01] <phillw> indeed it is
[15:02] <balloons> ok, so I'll try and go quick, but there's stuff to chat about
[15:03] <balloons> [TOPIC] Previous Actions
[15:04] <balloons> we don't have any :-) awesome
[15:04] <balloons> [TOPIC] Ubuntu Updates
[15:04] <balloons> jibel, hggdh care to enlight us a bit?
[15:06] <balloons> guess there not around.
[15:06] <balloons> well, lots of testing is going on this week
[15:06] <balloons> and if anyone hasn't yet seen, we've put out a call to the greater community to help strengthen the iso testing
[15:06] <balloons> http://www.theorangenotebook.com/2012/04/would-you-adopt-iso.html
[15:07] <balloons> so far the feedback has been large, lots of first timers experiencing iso testing. We have good coverage on the ubuntu iso's now, and for the flavor teams, I have directed people at testing several of those images as well
[15:07] <balloons> be forewarned if you meet or find some new folks testing your images :-)
[15:08] <phillw> balloons: we've already got a new one :)
[15:08] <balloons> Questions/comments?
[15:08] <roignac> balloons: I suppose, we should concentrate to find people who would test lubuntu and other less popular distros
[15:08] <roignac> on less popular configurations such as arm or powerpc
[15:09] <phillw> roignac: the lubuntu ppc testers have been trying to help out on other flavours.
[15:09] <balloons> roignac, we actually had someone volunteer to help who had a omap 3430 chip.. I was pleasantly surprised
[15:09] <phillw> we have no arm
[15:09] <roignac> whoa, that is great
[15:09] <balloons> yea.. pretty sweet I thought
[15:09] <balloons> he had quite a setup, so I had him go at it
[15:10] <roignac> that is a pity, that ubuntu can't run on raspberry pi, as it gained a lot of attention recently =(
[15:11] <balloons> yea.. the older versions can.. for instance natty
[15:11] <balloons> arm is changing fast
[15:11] <balloons> it's coming of age if you will
[15:11] <roignac> anyway, that post is great, attention to iso tests is important
[15:11] <balloons> [TOPIC] Ubuntu Flavor Updates
[15:11] <balloons> phillw, wanna speak to lubuntu real quick?
[15:12] <phillw> yeah, I've tried pinging kanliot
[15:12] <phillw> There is one possible bug that applies to very few set-ups for equipment, that will not be fixed for 12.04
[15:12] <phillw> the -release tema mentioned it 'may' affect all flavours as it is kernel bug.
[15:13] <phillw> bug 966403
[15:13] <phillw> There is a work-around
[15:14] <phillw> other than that, we're looking good-to-go.
[15:14] <balloons> awesome :-)
[15:14] <balloons> interesting bug
[15:15] <balloons> anyone from xubuntu want to weigh in?
[15:15] <astraljava> o/
[15:16] <astraljava> but not much to say. I have been very busy lately with real-life issues (I actually kinda hate that expression, but meh...), but I haven't heard of/seen any issues.
[15:16] <astraljava> Xubuntu does have an alternate install image, though, so it's likely to hit the same bug.
[15:17] <astraljava> But I guess we'll hear more as the RC ISO testing begins.
[15:17] <astraljava> ..
[15:17] <balloons> I'm surprised it's limited to lubuntu, but I haven't heard of it happening
[15:17] <balloons> astraljava, i've had 4 people signup to test xubuntu iso's, fyi
[15:17] <phillw> it appears to be very narrow set of kit.
[15:17] <balloons> so hopefully we see some good results from them
[15:18] <astraljava> balloons: What does that mean, where did they sign up?
[15:18] <balloons> how about ubuntu studio astraljava ?
[15:18] <balloons> astraljava, they answered the call to 'adopt' an iso...
[15:18] <balloons> :-)
[15:18] <balloons> and I sent them to task on some xubuntu isos
[15:18] <astraljava> Ahh... gotcha, yeah didn't get a chance to look into that at all, yet.
[15:18] <balloons> basically the desktop and alt images for 386 and amd64
[15:18] <astraljava> I have some pending members for the Testers team.
[15:19] <astraljava> I'll go through those tonight.
[15:19] <balloons> when this is all done, I will followup with the flavors teams on who tested and direct them your way
[15:19] <balloons> but you will also see the results if they do contribute
[15:19] <astraljava> But anyway, for Studio, we just recently got the mixer changes through, so testing those initially proved successful.
[15:19] <astraljava> Otherwise the same as Xubuntu, except no alternate image, so won't hit that bug.
[15:19] <astraljava> ..
[15:19] <balloons> thanks astraljava
[15:20] <balloons> anyone about for kubuntu?
[15:20] <balloons> Riddell?
[15:21] <balloons> mmkkk.. edubuntu?
[15:21] <balloons> we had some volunteers adopt those edubuntu and kubuntu iso's as well.. hopefully they follow thru and they get extra attention from outside there core QA teams
[15:22] <balloons> [TOPIC] Other topics
[15:22] <balloons> finally, anything else anyone has to discuss? The RC will be dropping this thursday, release next week and in 3 weeks we'll be at UDS again.. Time is a tickin' past!
[15:23] <Effenberg0x0> o/ Can I make a request?
[15:23] <balloons> Effenberg0x0, floor is yours
[15:23] <Effenberg0x0> Thanks balloons
[15:23] <Effenberg0x0> Ok, on Apr. 14, 15, 16, 17 and today we started seeing an unusual number of reports of Compiz/Unity/Name it VGA (GL-relted) problems. People affected by it simply can't use Unity (or anything GL) after upgrades. Suddenly we had 100 posts about it and even had to join threads to avoid mess. Yesterday, NVidia admited that it's latest driver (295.40) was broken can cause problems. For some, however, this is not the only reason. So
[15:23] <Effenberg0x0> me people have downgraded to previous NVidia versions and it hasn't solved the problem for them. Looking at the relevant / related updates, we had Nux, Mesa, Unity, other updates in the mentioned period. Bug reports and triaging are focusing on blaiming NVidia and waiting for an update from them. But some are asking: What if it's *not* just NVidia driver? So, this is something I am particularly concerned right now. See #982485
[15:23] <Effenberg0x0> and dups (#981737, #982762, #983080, #983171, #984353, probably more).
[15:24] <Effenberg0x0> So, the only way to test it is to use NVidia hardware on a fresh / upgraded install and test: Current NVidia drivers and Previous NVidia drivers. And see if GL stuff works on your hardware.
[15:24] <Effenberg0x0> If you could ask your teams to test this, I think it's relevant at this point.
[15:25] <balloons> Effenberg0x0, grabbing the bug
[15:26] <balloons> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/982485
[15:26] <balloons> ok, so I have the old nvidia driver, and haven't upgraded it all cycle Effenberg0x0
[15:26] <balloons> and my system doesn't have any issues
[15:26] <balloons> i have a 7300
[15:27] <Effenberg0x0> NVidia hasn't released much info and the list of affected hardware. This is a problem for us
[15:27] <balloons> I'm on 295.33
[15:27] <Effenberg0x0> They just mention (some models in the 7 and 8 series)
[15:28] <balloons> How did the bug reporter get the newer driver?
[15:28] <Effenberg0x0> If more people could test and post results to these bug reports, it could really help us understand whats going on, affected models, etc
[15:28] <Effenberg0x0> And also if it's only NVidia or seomthing else
[15:28] <Effenberg0x0> (That's it, sorry for the long text)
[15:28] <balloons> anyways.. I'll keep it in mind and contribute my result :-)
[15:28] <balloons> thanks Effenberg0x0
[15:29] <balloons> hopefully it is just a driver thing, but you are right.. it's easy to blame
[15:29] <balloons> anyone else?
[15:29] <Effenberg0x0> balloons, new driver 295.40 is on repos since 14th
[15:29] <phillw> hmmm... 3 weeks... my final exams :/ - have fun!
[15:30]  * balloons wonders why his system hasn't updated
[15:30] <phillw> I'd like to ask for a peer review of https://wiki.ubuntu.com/Lubuntu/Testing/TheStages
[15:31] <balloons> phillw, I spot some grammar mistakes -- shall I simply edit?
[15:31] <phillw> It was 'thrown' together in a hurry as part of https://wiki.ubuntu.com/Lubuntu/Testing for the late newcommers.
[15:31] <phillw> balloons: by all means! It has not got as far as grammar checking yet :)
[15:31] <balloons> haha
[15:31] <balloons> ok, I will try and give 5 mins to it
[15:31] <phillw> now I know where they came from :D
[15:32] <balloons> anything else phillw?
[15:32] <phillw> nope, thansk
[15:32] <balloons> k, anyone else?
[15:32] <phillw> *thanks
[15:32] <balloons> if not, good luck and happy testing to everyone.. This is going to be quite a week..
[15:32] <balloons> quickly, do we feel like we want to meet next weds?
[15:33] <balloons> I'll post to the ml, but I'm thinking we'll likely want to skip, being so hammered by getting the release out
[15:33] <phillw> I think it would be good, to cover any zero day bugs
[15:33] <astraljava> Yeah, I think so too. Good to keep track of how testing goes with other flavors etc.
[15:34] <balloons> yes, the downside of not meeting it potentially not being able to help each other
[15:34] <roignac> balloons: yes, in case of any major bugs
[15:34] <balloons> lol.. ok ;-) Idea squashed
[15:34] <astraljava> Thanks. :)
[15:34] <balloons> so that's it then.. I do apologize -- feel free to beat me up with a ping if you arrive @ the meeting on time and I'm seemingly absent
[15:34] <balloons> I don't mind
[15:35] <balloons> I need it beat into my head the new time
[15:35] <balloons> when your working and get into the zone it's easy to miss..
[15:35] <phillw> balloons: this time suits me better :D
[15:35] <balloons> I'm around, there's no reason for me to miss and not start
[15:35] <balloons> that's all folks!
[15:35] <balloons> #endmeeting
[15:35] <meetingology> Meeting ended Wed Apr 18 15:35:40 2012 UTC.
[15:35] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-testing/2012/ubuntu-testing.2012-04-18-15.01.moin.txt
[15:35] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-testing/2012/ubuntu-testing.2012-04-18-15.01.html
[15:35] <Effenberg0x0> Thank you everyone
[15:36] <phillw> balloons: I'll ping you before I go for my evening meal next week :D
[15:36] <balloons> phillw, that would be awesome :-)
[15:37] <astraljava> Thanks Nick, all!
[15:37] <phillw> np
[15:38] <raju> Effenberg0x0:  woowo
[15:38] <raju> Effenberg0x0:  its long time
[15:38] <Effenberg0x0> hey Raju, indeed. All fine?
[15:39] <raju> Effenberg0x0:  yeah , after two changing two SMPS
[15:39] <raju> Effenberg0x0:  how are you ?
[15:40] <Effenberg0x0> Everything fine, work's a little harder than usual latety, but it's just a phase
[15:40] <raju> Effenberg0x0:  you usually work with out sleep  , now more than that means how i have to predict i am not getting :
[15:41] <raju> Effenberg0x0:  :p
[15:41] <raju> Effenberg0x0:  few days to go for release
[15:41] <Effenberg0x0> Gotta pay the bills lol. and t his Ubuntu thing takes too much time
[15:42] <Effenberg0x0> Yeah... Forums will be hell
[15:42] <raju> Effenberg0x0:  i am getting back my laptop in a few weeks
[15:42] <raju> Effenberg0x0:  yeah already started man
[15:42] <raju> but more we can expect after release
[15:43] <phillw> raju: were you there when grub2 launched?
[15:43] <Effenberg0x0> I know. Is it OK to answer threads while drunk? I'm thinking of it as a good strategy
[15:43] <raju> phillw:   i think no
[15:44] <phillw> raju: oh, you missed out on so much *fun* :P
[15:44] <raju> Effenberg0x0:  i dont know,  because i dont drink :p
[15:44] <raju> phillw:  in forums ?
[15:44] <phillw> was just like trying to herd cats.... everyone reporting the same problems....
[15:45] <raju> phillw:  lol that could make us some better , if we solve one then we can give it others as reference
[15:46] <Effenberg0x0> raju, most users think their problems is always unique
[15:46] <phillw> raju: yeah, that's where the count for http://ubuntuforums.org/member.php?u=824544 camer from :)
[15:47] <phillw> raju: the answer was there, they just needed pointing to it :)
[15:47] <phillw> the more difficult ones, were when they had decided to hack the code!
[15:48] <phillw> oh, and it didn't work with RAID arrays :)
[15:48] <raju> phillw:  lol yeah more counts
[15:48] <raju> Effenberg0x0:  but small thing can echo big difference
[15:48] <phillw> I think it was over 500 in my two 18 hour stints I did on the forum.
[15:49] <phillw> (each stint)
[15:49] <Effenberg0x0> wow, that's huge Philw :)
[15:49] <raju> Effenberg0x0:  what  you got today ? ?
[15:49] <raju> Effenberg0x0:  lightDm issue over  ?
[15:50] <phillw> lightDM is behaving.
[15:50] <Effenberg0x0> Raju, I think so. I'm concerned about this NVidia thing. :\
[15:50] <raju> Effenberg0x0:  aaha!
[15:50] <phillw> we at lubuntu are grateful of xubuntu taking it last release.
[15:50] <Effenberg0x0> 100 posts in a couple hours ... it can go bananas in release
[15:51] <raju> Effenberg0x0:  100 HUGE
[15:51] <phillw> Effenberg0x0: I've nothing on lubuntu, sorry I cannot give you any help from our team.
[15:51] <Effenberg0x0> I understand Philw, it's very Unity/COmpiz related as it seems
[15:52] <raju> Effenberg0x0: phillw  VGA stuff ?
[15:53] <phillw> raju: out testers range from 128MB RAM system to quad-core 4MB+ kit, in all sorts of variants.
[15:53] <Effenberg0x0> Yep... people say they update normally, mainly since the 14th to today. And they loose the desktop. NVidia admited latest driver is broken, but only for some hardware models. Reports mention other models.
[15:54] <phillw> Effenberg0x0: is that update 11.10, or upgrade 11.10 --> 12.04?
[15:55] <raju> Effenberg0x0:  what about the old drivers which are not broken , we could use them as alternatives up to they get fixed ,hope its possible . is it ?
[15:55] <Effenberg0x0> phillw, 11.0->12.04, 12.04->12,04 and even some fresh installs were reported.
[15:56] <Effenberg0x0> Raju: Yes, considering 295.40 is the only cause, Ibelieve they will remove it from repos.
[15:56] <raju> Effenberg0x0:  yeah !
[15:57] <phillw> there was some insanity in apt when dealing with computers that have both 64bit & 32bit software installed. The release for that is going out as we speak. Are you sure it is not related to that as well?
[15:58] <phillw> https://bugs.launchpad.net/ubuntu/+source/apt/+bug/850264
[15:58] <phillw> such a thing can cause complete and utter chaos!
[15:58] <Effenberg0x0> philw, not sure of anything. Most reporters are ordinary users. Like "Ubuntu is broken" reports. It takes a while to get information and diagnosis from each.
[15:59] <phillw> possibly not all the bugs are 100% Nvid?
[15:59] <phillw> Effenberg0x0: tell me about it!
[15:59] <Effenberg0x0> phillw, I want to be wrong about it. People are betting on nvidia as the single cause and I think they're wrong.
[15:59] <raju> phillw:  Effenberg0x0  cya people , marathon in the stomach
[16:00] <Effenberg0x0> BYe Raju, cya later
[16:00] <phillw> the new bug-reporter for 12.04 will hopefully reduce dupes as it will check itself. cyas raju
[16:01] <Effenberg0x0> philw, true, counting on it too
[16:01] <Effenberg0x0> philw, gotta go, eat something :) Talk to you later
[16:01] <phillw> tc... nearly bed time here!
[16:02] <Effenberg0x0> lunch here lol
[16:05] <jibel> stgraber, I confirm the slideshow was missing in oneiric in oem mode on alternate.
[16:06] <stgraber> jibel: cool, so no weird magic going on, just a specific path not many use apparently ;)
[16:06] <jibel> stgraber, I do, that is what worries me :)
[17:16] <PaoloRotolo> Salve
[18:58] <stgraber> jibel: can you reliably reproduce bug 984932?
[18:58] <stgraber> jibel: I just tried with OEM with the latest Ubuntu daily and couldn't reproduce
[20:28] <jibel> stgraber, not reliably. set it to incomplete and let it expire unless I find a reliable way to reproduce.
[20:30] <stgraber> jibel: good to know, still wondering what happened exactly in your case... my guess is that the panel started before X finished intializing, causing only the indicators to get rendered
[20:31] <stgraber> jibel: if you reproduce this at some point, can you run "xwininfo" on the panel and get me its dimensions?


[00:03] -queuebot:#ubuntu-release- New binary: sword [riscv64] (hirsute-proposed/universe) [1.9.0+dfsg-3] (no packageset)
[11:25] -queuebot:#ubuntu-release- New binary: gemma [s390x] (hirsute-proposed/none) [0.98.3+dfsg-1] (no packageset)
[11:26] -queuebot:#ubuntu-release- New binary: gemma [amd64] (hirsute-proposed/none) [0.98.3+dfsg-1] (no packageset)
[11:26] -queuebot:#ubuntu-release- New binary: gemma [ppc64el] (hirsute-proposed/none) [0.98.3+dfsg-1] (no packageset)
[11:36] -queuebot:#ubuntu-release- New binary: gemma [arm64] (hirsute-proposed/universe) [0.98.3+dfsg-1] (no packageset)
[17:03] -queuebot:#ubuntu-release- New: accepted gemma [amd64] (hirsute-proposed) [0.98.3+dfsg-1]
[17:03] -queuebot:#ubuntu-release- New: accepted gemma [ppc64el] (hirsute-proposed) [0.98.3+dfsg-1]
[17:03] -queuebot:#ubuntu-release- New: accepted gemma [arm64] (hirsute-proposed) [0.98.3+dfsg-1]
[17:03] -queuebot:#ubuntu-release- New: accepted gemma [s390x] (hirsute-proposed) [0.98.3+dfsg-1]
[17:03] -queuebot:#ubuntu-release- New: accepted meep [amd64] (hirsute-proposed) [1.16.1-1]
[17:03] -queuebot:#ubuntu-release- New: accepted meep [armhf] (hirsute-proposed) [1.16.1-1]
[17:03] -queuebot:#ubuntu-release- New: accepted meep [s390x] (hirsute-proposed) [1.16.1-1]
[17:03] -queuebot:#ubuntu-release- New: accepted rust-derive-builder [armhf] (hirsute-proposed) [0.9.0-3]
[17:03] -queuebot:#ubuntu-release- New: accepted rust-derive-builder [s390x] (hirsute-proposed) [0.9.0-3]
[17:04] -queuebot:#ubuntu-release- New: accepted meep [arm64] (hirsute-proposed) [1.16.1-1]
[17:04] -queuebot:#ubuntu-release- New: accepted rust-derive-builder [arm64] (hirsute-proposed) [0.9.0-3]
[17:04] -queuebot:#ubuntu-release- New: accepted meep [ppc64el] (hirsute-proposed) [1.16.1-1]
[17:04] -queuebot:#ubuntu-release- New: accepted rust-derive-builder [ppc64el] (hirsute-proposed) [0.9.0-3]
[17:04] -queuebot:#ubuntu-release- New: accepted rust-derive-builder [amd64] (hirsute-proposed) [0.9.0-3]
[17:04] -queuebot:#ubuntu-release- New: accepted sword [arm64] (hirsute-proposed) [1.9.0+dfsg-3]
[17:04] -queuebot:#ubuntu-release- New: accepted sword [ppc64el] (hirsute-proposed) [1.9.0+dfsg-3]
[17:04] -queuebot:#ubuntu-release- New: accepted sword [s390x] (hirsute-proposed) [1.9.0+dfsg-3]
[17:04] -queuebot:#ubuntu-release- New: accepted sword [amd64] (hirsute-proposed) [1.9.0+dfsg-3]
[17:04] -queuebot:#ubuntu-release- New: accepted sword [riscv64] (hirsute-proposed) [1.9.0+dfsg-3]
[17:04] -queuebot:#ubuntu-release- New: accepted sword [armhf] (hirsute-proposed) [1.9.0+dfsg-3]


[08:48] <blahdeblah> jose: Sorry I didn't get back to you the other day; other work preempted the charm I was working on.  I ended up basing mine on a newer python-based charm.
[09:49] <Odd_Bloke> Could a charmer have a look at https://code.launchpad.net/~daniel-thewatkins/charms/trusty/ubuntu-repository-cache/hotfix-leader-election/+merge/270838, please?
[09:50] <Odd_Bloke> marcoceppi: lazypower: $others: ^
[10:10] <gnuoy> jamespage, would you mind taking a look at https://code.launchpad.net/~gnuoy/charm-helpers/1496746/+merge/271443 when you have a moment?
[10:12] <jamespage> gnuoy, For pagesize, size, min_size and nr_inodes options, you
[10:12] <jamespage> can use [G|g]/[M|m]/[K|k] to represent giga/mega/kilo.
[10:13] <gnuoy> jamespage, ok, but that leaves me with some horrible code converting that to bytes.
[10:15] <jamespage> gnuoy, hmm
[10:16] <jamespage> gnuoy, well we need to support human usable config somewhere in the stack
[10:16] <jamespage> gnuoy, but I don't think that's exposed just yet right?
[10:16] <jamespage> gnuoy, some sort of general K M G functions would be good I think
[10:17] <gnuoy> ok
[11:05] <gnuoy> jamespage, would you mind taking another look pls?
[11:08] <jamespage> gnuoy, +1
[11:12] <gnuoy> jamespage, thanks
[12:22] <gnuoy> jamespage, got a sec for https://code.launchpad.net/~gnuoy/charms/trusty/nova-compute/1496746/+merge/271451 ? Mainly just a charmhelper sync plus setting the new set_shmmax
[13:03] <bloodearnest> anyone know of a charm with amulet tests that test the upgrade step from previous version of the charm?
[13:06] <bloodearnest> I can just install from the charmstore, right? Like cs:trusty/gunicorn-0 ?
[14:45] <Odd_Bloke> jose: marcoceppi: lazypower: Any chance you could have a look at the merge I linked about?
[14:45] <Odd_Bloke> There's also https://code.launchpad.net/~cjwatson/charms/trusty/ubuntu-repository-cache/inline-release/+merge/271107
[14:54] <rick_h_> Odd_Bloke: I think they're sprinting today so might be slow to respond
[14:56] <Odd_Bloke> rick_h_: Ah, thanks for the heads up.
[14:56] <Odd_Bloke> I'll try in all caps in a bit, I'm sure that'll help. ;)
[14:57] <rick_h_> Odd_Bloke: wfm :)
[14:59] <jose> Odd_Bloke: lazypower says that he'll take a look later today and merge, we're in a summit right now
[15:00] <Odd_Bloke> jose: lazypower: <3 thanks.
[15:00] <jose> thanks to you!
[15:08] <jamespage> thedac, can you tip the video down a bit
[15:08] <gnuoy> thehi
[15:08] <gnuoy> thedac, hi (is what I meant
[15:08] <thedac> hi
[15:08] <wolverineav> hey, this is aditya
[15:10] <jamespage> thedac, question sounds like its about branching strategy?
[15:10] <thedac> yes
[15:11] <thedac> You also have options when you branch a charm. bzr branch lp:charms/trusty/$CHARM
[15:13] <jamespage> thedac, this https://github.com/openstack-charmers is probably waht the charms will look like once migrated to git
[15:14] <wolverineav> I have a question very specific to openstack neutron - the subordinate charm for DHCP and L3 agent is deployed on the controller node (the neutron-api / gateway).
[15:14] <wolverineav> now, is there a way to deploy this on the compute node instead? (at scale, the controller node becomes a bottleneck when VMs are brought up and it requests DHCP and L3). so i would like to disable DHCP and L3 on controller and enable it only on compute. (or enable it on all nodes)
[15:14] <jamespage> 15.10
[15:14] <thedac> thanks
[15:15] <jamespage> thedac, we'll switchover once we release from bzr
[15:15] <gnuoy> wolverineav, not at the moment. You can have dhcp and metadata on the compute nodes but only if the gateway is not deployed
[15:15] <jamespage> probably
[15:16] <wolverineav> neutron-gateway would always have to be deployed, right?
[15:16] <gnuoy> wolverineav, right
[15:16] <thedac> jamespage: is the hangout public?
[15:16] <jamespage> probably not
[15:16] <gnuoy> wolverineav, you can use DVR t oreduce traffic through the gateway
[15:16] <jamespage> wolverineav, erm not sure that's accurate
[15:18] <gnuoy> fwiw the link quality isn't good enough to follow everything that's being said
[15:19] <ddellav> we've got some people here that want to screen share so can we switch to a public hangout so they can be invited?
[15:19] <ddellav> or how else should we accomplish this?
[15:19] <gnuoy> I'm happy to switch
[15:19] <bdx><EMAIL_ADDRESS>[15:20] <wolverineav> ah, so the bottleneck I'm talking about is pre-DVR
[15:20] <wolverineav> I haven't tried it with DVR enabled.
[15:28] <coreycb> wolverineav, https://git.launchpad.net/~sdn-charmers/charms/+source/openvswitch-odl/tree/
[15:30] <coreycb> wolverineav, http://bazaar.launchpad.net/~ost-maintainers/openstack-charm-testing/trunk/view/head:/bundles/ovs-odl/ovs-odl.yaml
[15:33] <ddellav> are you guys seeing the juju-gui jamespage gnuoy ? He's got a full openstack deployment but juju-gui is not displaying any charms
[15:33] <ddellav> we've got mbruzek helping him but it's pretty bazaar
[15:34] <gnuoy> I see the gui, not sure whats causing the issue though
[15:35] <rick_h_> ddellav: gui issue? hatch can help if you need a hand with something.
[15:36] <hatch> hello
[15:36] <ddellav> hey hatch we have a charm partner that's having issues with the gui
[15:37] <ddellav> he has the gui deployed to an lxc container alongside a full openstack deployment but the gui is showing no charms or machines
[15:37] <ddellav> it previously worked but in the last few weeks it started doing this
[15:38] <hatch> ddellav: can you get them to open the browser console to see if there are any errors?
[15:38] <hatch> also, do they still have to log into the gui? (it didn't get switched to sandbox mode by accident?)
[15:39] <thedac> hatch: he does log in
[15:39] <ddellav> hatch, no errors in the browser console
[15:40] <hatch> hmm
[15:40] <hatch> and the `juju status` in the cli shows the gui?
[15:40] <thedac> Yes as well as the rest of the openstack deploy
[15:41] <hatch> ok give me a moment to think about this one :)
[15:41] <thedac> sure. One other point is this is a MAAS deploy
[15:42] <hatch> thedac: which browser are they using?
[15:42] <ddellav> chrome
[15:42] <cory_fu> Merlijn_S: Welcome.  https://jujucharms.com/docs/devel/authors-charm-composing
[15:42] <hatch> ddellav: thedac ok I'm going to investigate locally here and will get back to you
[15:42] <Merlijn_S> cory_fu: Thanks
[15:43] <thedac> hatch: thanks
[15:45] <stub> tvansteenburgh1: http://juju-ci.vapour.ws:8080/view/Juju%20Ecosystem/job/charm-bundle-test-aws/735/console is looking promising. Formatting a little off with the update, but close enough.
[15:45] <jamespage> thedac, coreycb: for those interested - https://review.openstack.org/#/c/224797/
[15:45] <jamespage> gnuoy, ^^
[15:46] <jamespage> pulled my finger out
[15:46] <gnuoy> jamespage, tip top. thanks
[15:47] <tvansteenburgh1> stub: \o/
[15:47] <coreycb> jamespage, when do you think we'll have base charms available for SDN charm composing?
[15:48] <coreycb> wolverineav, https://jujucharms.com/docs/devel/authors-charm-composing
[15:48] <jamespage> coreycb, context?
[15:48] <jamespage> coreycb, probably this month
[15:48] <jamespage> need to make some time
[15:48] <ddellav> thanks hatch
[15:48] <tvansteenburgh> stub: i have some follow-up questions/comments to your latest remarks, but will get to those later today. thanks for taking the time
[15:48] <coreycb> jamespage, I'm chatting with wolverineav from big switch and showing him the odl charm
[15:48] <jamespage> coreycb, right
[15:50] <ddellav> hatch, not sure if this helps but here's a screenshot: http://cl.ly/image/2z1F3Y100I12
[15:51] <hatch> ddellav: very odd, thanks - I'm just spinning up a local env here to see if I can reproduce
[15:54] <hatch> ddellav: can you check `juju get juju-gui` and look for the 'sandbox' property value
[15:58] <jamespage> wolsen, dosaboy, Tribaal: https://review.openstack.org/#/c/224797/2
[15:58] <bdx> hatch: http://paste.ubuntu.com/12438918/
[15:59] <ddellav> hatch, bdx is the user with the gui issue, he's pasted that output you wanted
[15:59] <hatch> ahh alright
[15:59] <hatch> yeah so this is very weird
[16:01] <ddellav> hatch, can you let us know the best place to submit a bug report for this issue?
[16:01] <hatch> bdx: ddellav https://bugs.launchpad.net/juju-gui
[16:01] <hatch> but this shouldn't be possible :)
[16:03] <ddellav> love those impossible bugs haha
[16:03] <hatch> bdx: can you run `app.env.getAttrs()`
[16:04] <hatch> it shouldn't contain any sensitive information, just take a look before pasting
[16:05] <hatch> bdx: does the machine view show your other maas machines? have you tried to deploy something? If you deploy a simple charm via the gui, like say Ghost, does it deploy as expected?
[16:05] <hatch> ddellav: yeah I could see this happening if there was some exception raised, but with no errors in the browser console it's quite odd
[16:05] <bdx> hatch: no, the juju-gui shows no sign of anything from my juju env.
[16:06] <bdx> omp
[16:09] <bdx> hatch: I don't know how you want this formatted: http://paste.ubuntu.com/12438981/
[16:10] <bdx> or I don't know how to get it into a better format
[16:10] <hatch> :) no that's fine
[16:10] <hatch> thanks
[16:11] <hatch> bdx: and the ip of your bootstrap node is <IP_ADDRESS>?
[16:11] <bdx> hatch: .73 is my juju-gui
[16:12] <hatch> ahh alright, so bdx what I would recommend trying is destroying this instance and deploying a new one
[16:12] <hatch> it appears that the connection between the GUI and your bootstrap node has somehow become broken
[16:15] <hatch> bdx: are you able to destroy/deploy the GUI to see if it resolves?
[16:24] <thedac> hatch: he has destroyed and redeployed several times. Same result.
[16:24] <thedac> he is at lunch at the moment
[16:24] <hatch> understood
[16:24] <hatch> ok
[16:26] <hatch> maybe the best case would be to file a bug...the issue is that the gui server is not able to communicate with the bootstrap node to get the environment details
[16:26] <hatch> so we need to surface that error
[16:26] <hatch> as there isn't anything the GUI can do to resolve it
[16:41] <mbruzek> hatch: I am working with bdx on this problem.
[16:41] <mbruzek> We will file a bug on this when he returns from lunch.
[16:42] <mbruzek> hatch: I had him destroy the service and redeploy with the same result.  The juju status shows all the deployed units, but the gui does not.
[16:42] <hatch> mbruzek: great thanks - The only way I was able to reproduce was to block the gui server from accessing the bootstrap node
[16:43] <hatch> so I'm assuming that there is something from the guiserver > bootstrap node which is blocking that communication
[16:44] <mbruzek> We did find an error in the web browser console a connection problem.
[16:44] <hatch> ahh there we go
[16:44] <mbruzek> Is there anything else that I can check.
[16:44] <hatch> did you happen to copy it somewhere I could see the error?
[16:44] <mbruzek> He is still at lunch
[16:44] <hatch> mbruzek: well the GUI thinks that it's connected
[16:45] <mbruzek> So ssh to the gui and see if I can ping the bootstrap node?
[16:45] <hatch> mbruzek: yeah that would be a good place to start
[16:45] <hatch> also, if there is an error in the console that might explain it
[17:01] <wolsen> jamespage: woot! on it
[17:15] <lazypower> Odd_Bloke, o/
[17:15] <lazypower> having a look now
[17:18] <Odd_Bloke> lazypower: Yo!  Thanks!
[17:19] <lazypower> Odd_Bloke, this merge makes me a little sad but I understand why its necessary
[17:19] <lazypower> Odd_Bloke, did you run into instances where this code was not being run on >= 1.23.2
[17:19] <Odd_Bloke> lazypower: The problem is that other parts of the code assume that 'lowest numbered == leader'.
[17:20] <lazypower> ah
[17:20] <lazypower> was this the only merge? or was there another one?
[17:21] <Odd_Bloke> lazypower: So, for example, unit 0 would go "I'm not the leader, I don't need to sync stuff down" and other units would still try to sync from unit 0.
[17:21] <Odd_Bloke> Proofs to tier 1 reset currency:	806.52 Qa / 1.18 Qt (+3.89 Qa Proofs/tick)
[17:21] <Odd_Bloke> Proofs to tier 1 reset currency:	806.52 Qa / 1.18 Qt (+3.89 Qa Proofs/tick)
[17:21] <Odd_Bloke> NICE
[17:21] <Odd_Bloke> https://code.launchpad.net/~cjwatson/charms/trusty/ubuntu-repository-cache/inline-release/+merge/271107
[17:21] <Odd_Bloke> lazypower: ^
[17:21] <lazypower> Odd_Bloke, yeah, that makes sense that the rest of the charm would need to be updated to us leader-set receivers on where they should sync from
[17:22] <Odd_Bloke> lazypower: Yeah, precisely.
[17:22] <lazypower> Odd_Bloke, as the leader may change in flight over the course of the lifetime
[17:22] <lazypower> *service lifecycle
[17:22] <Odd_Bloke> Yeah.
[17:22] <Odd_Bloke> So we do have a way of coping with the leader changing, but it isn't plumbed in to the leader election stuff yet.
[17:23] <lazypower> yeah this works for me as a conceptual fix until proper leader election bits can be landed
[17:23] <Odd_Bloke> (And, actually, given the response on that hook bug earlier, it might actually never get called.)
[17:23] <Odd_Bloke> OK, great!
[17:29] <lazypower> Odd_Bloke, not suree what should be done to the bug triage here if anything. https://bugs.launchpad.net/launchpad/+bug/804252
[17:29] <mup> Bug #804252: Please support InRelease files <Launchpad itself:In Progress by cjwatson> <ubuntu-archive-publishing:In Progress by cjwatson> <https://launchpad.net/bugs/804252>
[17:29] <lazypower> i'm going to head back into the charmer summit. Ping if you need anything else
[17:29] <lazypower> o/
[17:30] <Odd_Bloke> lazypower: I'll just let cjwatson know. :)
[18:48] <hatch> mbruzek: hey, any luck?
[19:03] <bdx> hatch: whats up
[19:06] <bdx> hatch: so what I was able to ascertain about the juju-gui not showing env issue is that.... it doesn't look like it is requesting to the bootstrap node....it seems to be requesting to itself....http://cl.ly/image/2q001V0F3v1o
[19:07] <bdx> <IP_ADDRESS> is the address of the juju-gui
[19:07] <bdx> <IP_ADDRESS> is the ip of the bootstrap node
[19:09] <hatch> bdx: ok thanks, I'll look into that code to see if I can figure out why it might be doing that
[19:09] <bdx> awesome, thanks
[19:20] <hatch> bdx: what version of juju are you using?
[19:20] <hatch> the gui used to work then just stopped? Can you remember any changes to the env made around that time?
[19:20] <hatch> the issue appears to be with the gui's websocket connection to the gui's server


[01:40] <forces> does lubuntu have alternative cd image ?
[04:23]  * mali\aweeeh autoawehs: feeding rocks
[09:14] <malina> https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
[09:15] <malina> hey... look, when I download that via git
[09:15] <malina> I don't get the debian/scripts directory so it fails
[09:15] <malina> make-pkg that is (or fakeroot)
[09:15] <malina> but downloading the maverick source via git, it does have those so
[09:15] <malina> wtf :/
[09:15] <malina> there is NO mentioning of it in that or other guides :/
[11:21] <stlsaint> Hey folks
[11:21] <bioterror> hi saint
[11:21] <bioterror> havent seen you for a while
[11:21] <bioterror> should I say, I almost missed you :D
[11:21] <stlsaint> Ah shucks your too kind
[11:22] <bioterror> are you now oil millionare?
[11:22] <stlsaint> Lol far from it
[11:22] <stlsaint> I'm almost ashamed to be in this channel
[11:22] <bioterror> how so
[11:22] <bioterror> I am here, you have nothing to be ashamed
[11:22] <bioterror> hahaha
[11:23] <stlsaint> Since buying my tablet I have yet to touch my main computer
[11:23] <bioterror> oh tablet, yes yes
[11:23] <stlsaint> My lubuntu is so out of date it might be at eol
[11:24] <bioterror> only if it's 9.10
[11:24] <stlsaint> Lol I wouldn't know
[11:24] <bioterror> you remember that the lubuntu dev's promised to keep 10.04 as a LTS
[11:24] <stlsaint> Aye
[11:24] <bioterror> well, I have only one ubuntu computer at my home atm.
[11:24] <bioterror> and that's my wifes
[11:25] <stlsaint> Irc clients are lacking on tablet though
[11:26] <stlsaint> bioterror so what new with everything
[11:26] <bioterror> :o
[11:27] <stlsaint> Damn curious about buttons
[11:27] <bioterror> :D
[11:27] <bioterror> I dont know about new
[11:27] <bioterror> I've been a little non-active, to be honest
[11:27] <stlsaint> Tsk tsk
[11:28] <stlsaint> Shame on u
[11:28] <bioterror> yeah
[11:28] <bioterror> I'm still wondering where phillw vanished
[11:28] <bioterror> and people asks from me about it
[11:28] <stlsaint> Where Phill go?
[11:28] <bioterror> yeah, where did he go
[11:28] <ericy> stlsaint:  I have XChat 2.8.6 on my Nokia N900.
[11:28] <stlsaint> How long has he been gone?
[11:29] <bioterror> stlsaint, from the beginning of this month
[11:29] <stlsaint> ericy autotab features and such?
[11:30] <stlsaint> bioterror interesting
[11:30] <ericy> stlsaint:  By autotab do you mean automatically startup all my server and channel tabs? Yes!
[11:31] <stlsaint> More along the lines of tab completion
[11:31] <stlsaint> That and auto channel join is killing me right now
[11:32] <stlsaint> And I just checked there is no xchat in andriod market for me
[11:32] <ericy> stlsaint:  I haven't used that yet on my Nokia900, (but of course I use it all the time here on my Lubuntu notebook).
[11:34] <ericy> stlsaint:  (I hear you.)
[11:35] <stlsaint> Lol on my lubuntu I use irssi
[11:35] <stlsaint> Love it but its not out for android
[11:36] <stlsaint> Really what I am using is best app it seems
[11:36] <stlsaint> Though this client can't seem to handle auto join
[11:38] <ericy> stlsaint:  That's not so great..
[11:38] <stlsaint> Nope and I chat in lot of channels. Too many to add each manually
[11:39] <ericy> Wow.
[11:43] <bioterror> ahhh, maybe moar work
[11:53] <stlsaint> Strange
[11:54] <stlsaint> Bt seems awfully quite lately
[12:06] <stlsaint> bioterror I need you to figure out how to port lubuntu to my tablet
[12:07] <bioterror> sudo apt-get install lxde
[12:07] <bioterror> :D
[12:30] <stlsaint> Not quite it
[12:30] <stlsaint> Trying to make me brick my tab lol
[13:20] <kjr63> testing
[13:25] <kjr63> hello
[13:25] <kjr63> how do i burn lubuntu .iso file to CD?
[18:26] <lcb> is  latest torrent's image from 11.04 Beta 2 already?
[18:29] <lcb> is this channel for /topic (s),  /join & /part messages and parking spots only?
[19:38] <bonny> do you know of any distros like lubuntu something that is fast and lightweight and is under 200 MB
[19:38] <basso> hmmm
[19:38] <basso> well you have chrunchbang
[19:39] <bonny> ok
[19:39] <basso> debian based
[19:39] <basso> we run it on a surf computer at our radio
[19:39] <basso> i think it uses around 60-70mb ram
[19:39] <bonny> ok
[19:40] <bonny> it looks good
[19:40] <basso> will you get public canonical release by 11.04?
[19:42] <bonny> i dont know what you mean by that i am reading about it now
[19:43] <basso> im asking if lubuntu will be canonicalized soon :P
[19:43] <bonny> what does canonicalized me
[19:43] <bonny> mean*
[19:44] <bonny> you mean when a new version will come out?
[19:53] <emce_PL> hello - he means when it gains Canonical official support
[19:54] <emce_PL> I think that only Julien can answer this
[20:16] <uofm49426> how to get widows added to grub in lubuntu
[20:16] <uofm49426> how to get windows added to grub in lubuntu
[20:16] <emce_PL> try os-prober
[20:18] <uofm49426> thanyou
[20:19] <emce_PL> yoo're welcome
[20:21] <uofm49426> is there any real demaning game i should try to see what my geforce 330 gtx can do
[20:22] <uofm49426> in lubuntu of cource
[20:22] <Unit193> Nexuiz is kinda demanding
[20:25] <emce_PL> yeah - you should try it
[20:25] <uofm49426> just went back to nvidia last card nvidia was a 6200 tc
[20:29] <uofm49426> i have a onboard hd 3000 its ok for a onboard i got a ati 4350 512 wasnt to much a difference between the 2 in proformance took it back next day
[20:30] <uofm49426> order this 330glx on ebay and so far blowes them away
[21:16] <uofm49426> how to edit screen size of the bootsplash
[21:16] <bonny> what is a widows prober
[21:16] <bonny> nvm
[21:16] <bonny> what is an os prober
[21:17] <bonny> i heard you guys mention it earluer
[21:17] <uofm49426> you have same problem i had
[21:17] <bonny> earlier*
[21:17] <uofm49426> os_prober
[21:17] <bonny> what does it do
[21:18] <bonny> it turns your lubuntu into windows?
[21:18] <uofm49426>  its what edits grub in a dual boat
[21:19] <uofm49426>  its what edits grub in a dual boot
[21:20] <uofm49426> if you have both window and ubuntu when you boot grub you will see
[21:20] <uofm49426> ubuntu 10.10 kernel number
[21:20] <uofm49426> at the bottem you will have windows
[21:21] <uofm49426> kubuntu and ubuntu has it buy befault so you never see it
[21:22] <uofm49426> lubuntu forgot it
[21:24] <MrChrisDruif> uofm49426: Lubuntu doesn't come with os_prober? But it's necessary for grub/dual-boot?
[22:09] <emce_PL> os-prober its a service, that discovers other systems installed on your harddrive
[22:09] <emce_PL> and adds them to grub.list
[22:14] <MrChrisDruif> But grub doesn't do that? So os-prober is needed for that?
[22:16] <MrChrisDruif> emce_PL: ^
[22:16] <emce_PL> it depends
[22:16] <MrChrisDruif> I'm no dual-booter, nor would I know how it all works if I did :)
[22:17] <emce_PL> sometimes it does, sometimes I had to install os-prober to add other os (windows of course)
[22:18] <MrChrisDruif> So grub only has problems detecting Windows? But other Linuxes are done correctly?
[22:27] <emce_PL> rather
[22:28] <emce_PL> there was always a problem when grub was reinstalled after windows installation
[22:28] <emce_PL> normally with lubuntu install windows was always on OS list in GRUB
[22:30] <MrChrisDruif> I'll put it in the mailing-list for consideration; so os-prober to eliminate problems when reinstalling grub after Windows installation?
[22:31] <emce_PL> with it there was no problem to add any Windows to OS list
[22:31] <emce_PL> os-prober && update-grub2
[22:33] <MrChrisDruif> I see it's installed by default in Ubuntu
[22:41] <gnewb> Hello, how do I upgrade to FFox 4?
[22:43] <emce_PL> which version do you have?
[22:43] <gnewb> emce_PL: 3.2?
[22:44] <emce_PL> not FF - Lubuntu
[22:44] <gnewb> srry, 3.6
[22:44] <gnewb> Oh, Lubuntu 10,04
[22:45] <emce_PL> sudo add-apt-repository ppa:mozillateam/firefox-stable
[22:45] <emce_PL> sudo apt-get update
[22:45] <emce_PL> sudo apt-get install firefox ubufox
[22:45] <gnewb> Thank You!
[22:49] <gnewb> emce_PL: I was missing the ppa: part, Thank you kindly.