 I wanted to ask something , please help me
[18:03] <UbuPhillup> arrun: just ask
[18:04] <arrun> UbuPhillup:  I had a po and mo file of a language which is a local language, I wanted to apply that file to the software, how can I do that?
[18:05] <UbuPhillup> arrun: you can upload the file into lauchpad
[18:05] <arrun> UbuPhillup: no, I have already downloaded it
[18:06] <arrun> UbuPhillup: Already got the po and mo
[18:06] <arrun> UbuPhillup: but can't figure out how to apply
[18:06] <UbuPhillup> arrun: you would like to run the software with the new po file right?
[18:07] <arrun> UbuPhillup: YUP
[18:08] <UbuPhillup> arrun: you must change the mo file on your system the then restart
[18:08] <arrun> UbuPhillup: bro, can't we add a new one?
[18:11] <UbuPhillup> arrun: just copy the old one put the new one in the folder
[18:12] <arrun> UbuPhillup: bro, but I wanted to add a new language
[18:13] <UbuPhillup> hmm
[18:17] <UbuPhillup> dont know


[00:26] <cjwatson> '"~canonical-kernel-team/ubuntu/ppa" or "ppa:canonical-kernel-team/ubuntu/ppa" for a PPA'
[00:26] <cjwatson> The canonical-kernel-team and ppa bits are examples
[00:26] <cjwatson> The pattern is ppa:OWNER/DISTRO/NAME
[17:20] <kisak> g'day, I got an automated email that there was an internal error while copying a package id OOPS-2d4b588ecc8af4e1cc5ffbc74d841bca (llvm 13 being copied to https://launchpad.net/~kisak/+archive/ubuntu/steamvr ). If it's easy to do, can someone check if I need to take action like removing the recently copied package and asking launchpad to copy it again?
[17:22] <cjwatson> kisak: That's a known bug (https://bugs.launchpad.net/launchpad/+bug/1314569) that you can safely ignore; the copy happened successfully.
[17:26] <kisak> thanks for checking


[07:23] <bazhang> forkbomb and the rm etc command from deadbit
[07:33] <deadbit> hell!
[07:33] <deadbit> o
[07:33] <deadbit> hello!
[07:33] <deadbit> So I was offering a new guy some help in avoiding random people telling him to run random commands.
[07:34] <deadbit> I don't think it's correct - even if it is bazhang and he's an op to tell a member of a community for the official ubuntu support channel to run a random command.
[07:34] <deadbit> Also - as a user of Ubuntu - I don't see why you have banned me from the official support channel.
[07:35] <bazhang> you were the one to post the forkbomb deadbit
[07:35] <bazhang> and the rm etc command deadbit
[07:35] <deadbit> is this something i can talk to canonical about? seeing as i do have support through them?
[07:35] <bazhang> no
[07:35] <deadbit> yes I said DO NOT RUN commands.
[07:36] <deadbit> Do you say no as an official representative of them?
[07:36] <bazhang> never post them
[07:36] <bazhang> canonical has no say over irc #ubuntu deadbit
[07:36] <deadbit> Again are you telling me, that No i cannot ask canonical/ubuntu about the issue i am having from the official support channel?
[07:37] <deadbit> from what i understand - channel with # are official channel linked to the projects themselves
[07:37] <bazhang> deadbit, let's be very clear, you posted it, you created the issue
[07:37] <deadbit> and the channel even states that this is the official support channel for ubuntu
[07:37] <deadbit> lets be very clear..... are you denying me access to the official support i'm entitle too?
[07:38] <bazhang> deadbit, thats a privilege not a right
[07:38] <deadbit> no it's a right but the terms of agreement in the ubuntu TOS
[07:39] <bazhang> deadbit, this is not the place to argue about such things; you posted some very bad things in the #ubuntu channel and were banned as a result
[07:39] <deadbit> This is exactly the place to talk about it.
[07:39] <bazhang> deadbit, did you wish to resolve that issue or not
[07:39] <deadbit> Are you acting as a representative of Ubuntu in this matter?
[07:40] <deadbit> Sure I do. I stated I was helping a fellow community member to avoid detrimental commands that could disrupt his OS.
[07:40] <bazhang> deadbit, this entire channel is the ops channel for the various ubuntu channels
[07:41] <deadbit> I gave examples to avoid. I did not state to run them, in fact I stated to not run them.
[07:41] <deadbit> But I can see you're trying to obfuscate the issue.
[07:43] <deadbit> I will consider you an official representative of Ubuntu; You are also violating my rights as a member and user of Ubuntu products since you have effectively rendered a support channel null to me.
[07:45] <deadbit> I have asked you clearly if you are acting as a representative of Ubuntu and you do not state yes or no. Yes you have to power to deny my access to an official support channel. I take this to be a violation of my rights to service under the TOS of Ubuntu as the channel has clearly made the distinction of it being a proper and recognized support channel for Ubuntu.
[07:46] <bazhang> deadbit, did you wish to discuss resolution of the ban, or continue as you are presently
[07:47] <deadbit> bazhang: Again, are you acting as a representative for Ubuntu? Will you deny me service for Ubuntu Official Channels? I have clearly stated that my comments were meant and intended under good faith to assist a fellow community member under an officially recognized support channel.
[07:48] <bazhang> forkbombs are not an assist, ever deadbit
[07:49] <deadbit> The information presented was for assistance - it was clear to the user; from the remark I made to avoid random commands given to members of the community from random individuals.
[07:50] <deadbit> It was so he could recognize a malicious command; and avoid it. This will prevent him from running a command in the future that could and would be harmful to his system.
[07:51] <bazhang> deadbit, if you did not wish to discuss the resolution of your ban, there is no reason to continue this discussion
[07:51] <deadbit> I'm sure you have the log - so I will ask a final time. Are you acting as an official representative of Ubuntu - and do you have the authority to deny me access to services which are rights to a user under the Ubuntu TOS on an officially recognized support channel?
[07:52] <deadbit> I have discussed it with you.
[07:52] <bazhang> deadbit, irc channels have operators, that moderate
[07:52] <deadbit> I will make sure to find the appropriate party and inform them of your actions in violation of the TOS.
[07:52] <bazhang> !appeals | deadbit
[07:53] <bazhang> feel free to appeal your ban deadbit
[07:54] <deadbit> I will seek assistance for this official support channel from Ubuntu and contact my VAR representative... thank you.
[07:55] <deadbit> I am currently documenting our discussion - If you remove me from the channel I will consider this an additional violation of the TOS.
[07:55] <deadbit> It is my intention to leave once I have documented my grievance and contacted the appropriate parties.
[07:55] <bazhang> deadbit, there are channel logs
[07:55] <bazhang> !1984 | deadbit
[07:56] <deadbit> Thank you for your time. Have a wonderful night!
[09:34] <bazhang> is kegsay threatening something on #ubuntu ?
[09:34] <ikonia> no, I don't think so
[09:35] <ikonia> I'm wondering if this is the matrix clean up
[09:35] <ikonia> or if another service is having a similar problem
[09:35] <ikonia> there goes a matrix user
[09:35] <ikonia> it must be matrix
[09:36] <ikonia> won't that be the same problem as the gateway timing out idle users
[09:36] <ikonia> is this the matrix solution it kicks idle users ?
[09:36] <ikonia> mass leave ?
[09:36] <ikonia> or is this just a one off thing ?
[15:41] <elky> ikonia: https://github.com/matrix-org/matrix-appservice-irc/issues/304#issuecomment-271939428 suggests periodic. it's the first time ever this time, they're still figuring out what exactly they'll be doing.
[17:34] <dax> ^ says Dinner is a PM bot, looks like an android IRC clint to me, and am unable to reproduce the issue
[17:34] <dax> client*


 Hell yes
[05:23] <valkyrie> at the time.
[05:23] <valkyrie> Learned my lesson
[05:23] <valkyrie> And was a stupid idea
[05:23] <mneptok> !enter
[05:23] <valkyrie> Bots are a privalige, not a right
[05:23] <Amaranth> valkyrie: And I see you're in a channel known for trolling
[05:23] <valkyrie> O.o
[05:23] <valkyrie> Which?
[05:24] <valkyrie> Lemme guess
[05:24] <valkyrie> Arch linux?
[05:24] <Amaranth> Yes, that's the one
[05:24] <valkyrie> I run arch man
[05:24]  * valkyrie Runs Arch and Slackware atm
[05:24] <Amaranth> I think you'll have to talk to the person who banned on about this one, I do not think it should be removed
[05:25]  * mneptok agrees
[05:25]  * valkyrie Nods slowly
[05:25] <bazhang> dont see how the trolling part has changed tbh
[05:25] <Amaranth> But it was a little over a month ago, not 3 months ago
[05:25] <valkyrie> Can i know who banned me?
[05:25] <valkyrie> i dont even know
[05:25] <mneptok> jussi01
[05:25]  * valkyrie Shoulda been smarter at the time and routed his IP
[05:25] <valkyrie> But again
[05:25] <valkyrie> i shouldent have done it period
[05:25] <Amaranth> Uh...
[05:25] <bazhang> what..
[05:26] <valkyrie> Thanks
[05:26] <valkyrie> Running through a proxy
[05:26] <valkyrie> Or multiple.
[05:26] <Amaranth> Right, people from that channel seem to love doing that
[05:26] <valkyrie> From Arch linux?
[05:26] <valkyrie> God man, you make us seem like bad people, Arch linux is just a distro, not horrible human beings =P
[05:27] <mneptok> garbage in, garbage out.
[05:27] <Amaranth> That channel seems to have almost no relation to the distro
[05:27] <valkyrie> #archlinux has nothing but the distro
[05:27] <Amaranth> Not that one, the other one
[05:27] <valkyrie> #Archlinux-offtopic
[05:27] <valkyrie> diff story
[05:27] <valkyrie> xD
[05:27] <mneptok> !enter
[05:27] <valkyrie> Ya i know, its a bad habit
[05:28] <valkyrie> Is the person who banned me on at this time? i would like a word
[05:29] <Amaranth> Doesn't look like it
[05:29] <mneptok> no.
[05:30] <valkyrie> Darn, ok, i'll be back later i guess, can you inform him\her i wanted to talk to him\her?
[05:30] <valkyrie> xD
[05:30] <bazhang> he'll know
[05:30]  * valkyrie Nods
[05:30] <valkyrie> Thanks
[05:30] <valkyrie>  /wc
[05:40] <bazhang> NoorulIslaam, how may we assist you
[05:41] <NoorulIslaam> oh uh
[05:42] <NoorulIslaam> essy came to #defocus and told everyone to join this channel
[05:42] <NoorulIslaam> and i responded
[05:42] <NoorulIslaam> :P
[05:42] <bazhang> ?
[05:42]  * NoorulIslaam looks at essy
[05:42] <essy> bazhang, that's not correct. I missed a / when joining the channel
[05:42] <NoorulIslaam> ah
[05:42] <NoorulIslaam> that explains a lot
[05:42] <NoorulIslaam> :P
[05:42] <NoorulIslaam> k bye
[05:42] <bazhang> essy, of course I knew that :)
[05:43] <essy> I'm prepping for my normal server to be offline for a bit - sorry for the confusion
[05:43] <bazhang> hehe
[05:43] <bazhang> my ? was for noorulislam's *extremely* unlikely explanation :)
[05:44] <SportChick> well he is a bit of a troll ;)
[05:44] <SportChick> anyway, sorry for the disruption
[06:12] <leo_rockway> I don't know if this is the right place, but I'd like to leave a complain on m4v, op in #ubuntu-es
[06:12] <leo_rockway> he's banning people without reasons
[06:13] <leo_rockway> it's not the first time he does it either
[06:27] <mneptok> leo_rockway: AFAIK, #ubuntu-es is not a channel the ops team monitors
[06:27] <leo_rockway> ok mneptok, thank you
[06:27] <leo_rockway> I also talked about this in #ubuntu-irc is that the right place?
[06:27] <mneptok> perfecto
[06:27] <leo_rockway> thanks :)
[06:28] <mneptok> de nada
[08:03] <Madpilot> @login
[08:04] <Madpilot> ubottu, raptors is <reply>Not as big as you thought they were. But just as dangerous. "... clever girl..."
[09:07] <Amaranth> obviously trolling
[09:07] <Madpilot> ya
[09:07] <Madpilot> enough rope, I think
[09:07] <Madpilot> want to ban forward him to #debian, or would that be cruel to #debian?
[09:07] <Amaranth> cruel to debian
[09:08] <Gary> very cruel :p
[09:08] <Amaranth> special.ubuntu.3.wget?
[09:08] <Amaranth> wtf
[09:09] <Gary> I want whatever he has been smoking
[09:09] <Madpilot> he probably smoked all of it, none left to share
[09:09] <Amaranth> Gary: Ask the guy in Ubuntu who bought his mic from a crack dealer
[09:09] <Amaranth> err, #ubuntu
[09:09] <Gary> hehe
[09:17] <Gary> pm'ing runge
[09:18] <Myrtti> looks like the pattern is ident ircd
[09:18] <Myrtti> or something
[09:19] <Gary> allah was just a
[09:20] <Myrtti> ok, here is another one
[09:21] <Madpilot> StapleAttack has been borderline-trolling for a while
[09:21] <Madpilot> the new nick is not an improvement
[09:21] <Myrtti> I've got him on my aim
[09:22] <Myrtti> then again, I should go eat breakfast so I can take my antibiotics and go shower my wounds
[09:22] <Gary> they seem to be playing in #debian
[09:23] <bazhang> 'google clownsex' ? did he really say that?
[09:23] <Myrtti> does someone have him on pm or something to tell him to change nick
[09:24] <Madpilot> dare I say that #debian is welcome to them?
[09:24] <Myrtti> what on earth are they talking on #ubuntu now
[09:24] <Myrtti> making /dev 20gig?
[09:24] <Myrtti> WTF
[09:25] <Madpilot> no idea
[09:25] <Madpilot> someone really likes their enter key, tho
[09:25] <Myrtti> E_MAKENOSENSE
[09:26] <Myrtti> ok, I see a rapid decline
[09:27] <bazhang> heh
[09:27] <bazhang> 'thought I was in club'
[09:27] <Myrtti> *cringe*
[09:27] <Madpilot> many bong-smoking trolls this morning. fun.
[09:28] <bazhang> haha
[09:30] <bazhang> nice real name on yocrap
[09:31] <Myrtti> SpacePigeon<EMAIL_ADDRESS>has quit ["he  went to bang your mom"]
[09:32] <Myrtti> thank you for that  k-line
[09:33] <Gary> np
[09:34] <Myrtti> anyone have objections if I kick yocrap out
[09:34] <bazhang> none
[09:34] <Myrtti> or even ban/banforward him here?
[09:34] <bazhang> better yet
[09:35] <Myrtti> last attempt
 yocrap is now buLl
[09:43] <Myrtti> ok, brekkie and showertime
[09:44] <Mamarok> right, he just starts trolling in #kde now
[09:46] <Madpilot> we're running an export trade in bong-smoking trolls from #ubuntu...
[09:46] <bazhang> hehe
[09:46] <Mamarok> looks like
[09:47] <Madpilot> you're welcome to them :)
[09:47] <Mamarok> not for very long
[10:21] <DrDerek> was I banned forever?
[10:32] <elky> what were you banned for?
[10:35] <elky> 16 days is hardly forever and certainly logical when you consider that we ban on an incremental duration basis.
[10:35] <elky> topyli, got comments?
[10:36] <DrDerek> aight
[10:45] <Myrtti> humdidum
[10:45] <Myrtti> hold on
[10:46] <Myrtti> he was banned 16 days ago?
[10:46] <Myrtti> I remember him discussing CPS "abducting" kids just few days ago
[10:46] <elky> i'm going by what the bantracker tells me, but it's entirely possible that coincides with some of the downtime
[10:48] <elky> ok, he's been ban-evading with a different nick?
[10:48] <Myrtti> I think so
[10:49] <elky> on, say the 17th. and tonyyarusso booted him.
[10:49] <Myrtti> yeah, sounds about right
[10:49] <Myrtti> snuxoll might remember the discussion too
[10:49] <Myrtti> my backlog doesn't go that far
[10:50] <elky> he knows the rules on ban evasion more than anyone.
[10:55] <elky> ah, no, the nick wasn't the ban-evasion bit. it was the obnoxious bit, though.
[10:56] <Myrtti> !away > happyaron|afk
[11:00] <Myrtti> *DINGDONGDINGDONG* sugar rush warning
[12:59] <elky> topyli, are you meaning to discuss derek here, rather than -ot?
[12:59] <topyli> oh darn
[13:00] <topyli> of course :+
[13:00] <elky> topyli, i dunno if it's your ban. i didn't feel like going through the ban list right now. I suspect not, but the bantracker doesn't seem to be listing removes any more.
[13:01] <topyli> hrm
[13:07] <topyli> well according to my backlog he was not eager to discuss it. maybe he wanted to just check if he's banned forever because his conduct will not change
[13:11] <Myrtti> hrm
[13:11] <Myrtti> the !hi factoid should be revised for -ot
[13:18] <Myrtti> *sigh*
[13:45] <elky> !hi
[14:30]  * Myrtti waits
[14:38] <elky> for?
[14:58] <Myrtti> for zilleplus to join and tell his opinion that having a bot in #ubuntu is stupid
[14:58] <Myrtti> because people with simple common questions can just google it
[14:58] <elky> heh
[17:05]  * elky blinks
[17:06] <elky> you kid.
[17:06] <elky> surely, you kid.
[17:09] <Seeker`> O.o
[17:11] <Seeker`> 'parently not
[17:12] <elky> i am very much resisting the temptation to say something.
[17:14] <elky> but i'll refrain, and mope that it was not lucky llama
[17:16] <Seeker`> here's a llama, theres a llama and another little llama
[17:17] <elky> exactly! now wouldn't that have made a great release day song!
[17:17] <elky> but now we don't get to :(
[17:17] <elky> my plans are ruined. RUINED!
[17:18] <Seeker`> :(
[17:32] <Myrtti> !awn
[17:33] <Myrtti> !awn =~ /in Hardy/from Hardy on/
[17:33] <Myrtti> someone with better grammar please fix
[17:50] <Myrtti> I must be sick with something, I keep thinking the factoid sounds ... inappropriate
[17:52] <elky> !awn =~ /on/onwards/
[17:52] <elky> !awn
[17:52] <elky> that failed...
[17:52] <Myrtti> uhoh
[17:52] <elky> !awn =~ /hardy on/hardy onwards/
[17:52] <elky> !awn =~ /Hardy on/Hardy onwards/
[17:53] <Myrtti> !awn =~ /navigationwards/navigation/
[17:53] <Myrtti> !awn
[17:53] <elky> Myrtti, better? :)
[17:53] <Myrtti> yeah
[17:53] <Myrtti> *shudder*
[17:55] <elky> !hardy
[17:55] <elky> !awn =~ /Hardy/Hardy (8.04)/
[17:55] <Myrtti> I thought it still *is* the eighth release, or has that changed?
[17:55] <Myrtti> ;-)

[17:58] <elky> i'm just putting more stuff between hard and on :-/
[17:58] <Myrtti> now you said it!
[17:58]  * Myrtti hides
[17:58] <Myrtti> !awn
[17:59] <Myrtti> but yeah, it's perfect now
[18:24] <Myrtti> I don't see an email about lucid lynx on the devel-announce ml
[18:49] <Pici> ...
[19:15] <Myrtti> for christs sake
[19:15] <Myrtti> what was the irssi option to make the channel sync better
[19:17] <Myrtti> help?
[19:17] <Myrtti> !staff
[19:17] <tomaw> Myrtti: why don't you just ban the host?
[19:17] <tomaw> he'll only keep reconnecting with a different ident
[19:18] <Myrtti> tomaw: because my irssi is flaking seriously out
[19:18] <nalioth> pity
[19:18] <tomaw> ah
[19:19] <tomaw> /set ban_type is probably where it's tripping up :)
[19:20] <Myrtti> no, it's tripping on the setting about the channel sync or something
[19:20] <Myrtti> "you need to be an operator to do that"
[19:21] <Myrtti> or then chanserv is lagging
[19:21] <mneptok> Myrtti: irssi has problems with /kickban when the channel has a large number of members. i have never used it successfully. so i craft all bans by hand.
[19:21] <Myrtti> channel_max_who_sync = 2000
[19:21] <Myrtti> hm
[19:21] <Myrtti> should be enough
[19:23] <tomaw> lowering it might be better to disable sync for large channels
[19:23] <Myrtti> hrm
[19:23] <Myrtti> historically it has worked though
[19:24] <Myrtti> tomaw: suggestions on a good value
[19:24] <tomaw> I have mine set to 1000 but that's probably default
[19:24] <tomaw> I haven't had a problem with it though
[19:24] <tomaw> what exactly was your irssi doing?
[19:25] <Myrtti> it's running on aliases
[19:25] <tomaw> ah, an op, ban, deop alias?
[19:25] <Myrtti> yup
[19:25] <tomaw> does it have a wait in between the op and ban commands?
[19:26] <nalioth> is it allowing you to even op up?
[19:26] <Myrtti> wait 50
[19:27] <tomaw> that's not enough
[19:27] <tomaw> make it 2000 and it will be much more reliable
[19:27] <Myrtti> ok
[19:29] <Myrtti> what was I doing again
[19:29] <Myrtti> oh yes
[19:29] <tomaw> :)
[19:30] <Myrtti> !pm > dhillon-v10
[19:32]  * Myrtti does the unorthodox and sed replaces the config file
[19:32] <mneptok> Myrtti: that will be overwritten when you /quit irssi
[19:33] <gord> unless you /reload and /save
[19:33] <mneptok> *nod*
[19:33] <Myrtti> mneptok: I've used irssi quite a long time and do know my way around it ;-)
[19:34] <Myrtti> in fact, irssi was the first linux app I remember using
[19:34] <Myrtti> s/was/is/
[19:35] <Myrtti> (apart from perhaps pine)
[19:40] <Tm_T> irssi+screen as first linux apps
[19:41] <Tm_T> but I'm still bit "fresh", first own pc with net connection in early 2004 (:
[19:41] <Tm_T> or so
[19:43] <Tm_T> that reminds me... /save
[19:43] <topyli> pine was my first app altogether, on the university terminals
[19:43] <topyli> not linux there then though
[19:43] <Tm_T> heh
[20:11]  * jpds goes to have pizza with MenZa.
[20:20] <jussi01_> All quiet on the western front?
[20:21] <Myrtti> apart from a bot attempt
[20:22] <jussi01_> Great:)


[00:02] <geser> shadeslayer: don't forget to close your bug in your changelog entry the next time
[00:02] <shadeslayer> geser: i have to close my own bug in the changelog? 0_o
[00:02] <shadeslayer> i didnt know that
[00:02] <geser> yes please, else they stay open
[00:03] <shadeslayer> yeah, but i would have closed it manually :D
[00:03] <shadeslayer> but either way, ill remember this
[00:03] <shadeslayer> geser: thanks :D
[00:03] <geser> of course you can close them after your debdiff got sponsored through the web ui but it's easier to do through the changelog and one doesn't forget it
[00:06] <Laney> and better, because then the bug tells you in which version it was fixed
[00:06] <shadeslayer> right
[00:08] <geser> and one also has a reference to a previous merge bug (if a need arises in the future to understand some changes and why they kept merged)
[00:08] <Laney> haha
[00:08] <Laney> see, many reasons!
[00:08] <geser> as the merge bug might have some additional info
[00:10] <shadeslayer> any idea where cowbuilder stores generated debs? :P
[00:11] <geser> and from a DMB point-of-view: when looking at the sponsored packages from an applicant, the linking to the sponsoring bug makes it easy to check how it got handled
[00:16] <geser> shadeslayer: try /var/cache/pbuilder/result/ (if you don't use a script that sets a different directory)
[00:16] <shadeslayer> geser: its not there, thats why im asking
[00:16] <shadeslayer> which i find very odd
[00:19] <geser> does your ~/.pbuilderrc specify BUILDRESULT?
[00:19] <shadeslayer> nope
[00:19] <geser> I've never used cowbuilder, so I'm mere guessing
[00:19] <geser> :(
[00:19] <Laney> are you using pbuilder-dist?
[00:20] <shadeslayer> nope, just simple cowbuilder
[00:21] <geser> almost last idea: check the value of BUILDRESULT in /etc/pbuilderrc
[00:21] <geser> and if that doesn't help: check the source
[00:22] <shadeslayer> BUILDRESULT=/var/cache/pbuilder/result/
[00:22] <shadeslayer> well.. thats ok, it built fine
[00:23] <geser> and the build succeeded?
[00:23] <Laney> is there a cowbuilderrc?
[00:23] <shadeslayer> geser: yes
[00:23] <shadeslayer> Laney: no
[00:24] <Laney> i suggest you check the manpage
[00:24] <Laney> and if that fails then the source
[00:24] <shadeslayer> i did... nothing there :p
[00:24] <geser> Laney: http://manpages.ubuntu.com/manpages/maverick/en/man8/cowbuilder.8.html
[00:25] <shadeslayer> i wonder if its because i run sudo -E pdebuild
[00:25] <geser> mentions only the pbuilder configuration files, nothing cowbuilder specific
[00:25] <geser> shadeslayer: yep, pdebuild != pbuilder
[00:25] <geser> slight difference
[00:25] <geser> check .. for the debs
[00:25] <shadeslayer> geser: not there as well
[00:26] <geser> damn
[00:27] <geser> ok, the pdebuild manpages mentions /var/cache/pbuilder/result
[00:27] <geser> then you have to dig through the source where your debs got put
[05:52] <micahg> SpamapS: what Ubuntu version are you on?
[05:55] <micahg> anyone here that understands scons?
[07:32] <AnAnt> Hello
[07:38] <shadeslayer> ho
[07:39] <shadeslayer> err... hi
[11:25] <ari-tczew> please open task on maverick and lucid in bug 617614
[11:29] <Laney> ok
[11:29] <Laney> there yo ugo
[11:35] <ari-tczew> thanks Laney
[13:44] <nthykier> Hi, I got a package (libsysactivity) that FTBFS on Ubuntu due the Autobuilders using a 2.6.24 kernel and one of the tests needs a 2.6.25 (or newer) - is there a way to get it built on a machine with a newer kernel or should I patch the package to skip the particular test?
[13:54] <tumbleweed> nthykier: I think the best solution is to patch out the test
[13:58] <bilalakhtar> hi tumbleweed
[13:59] <bilalakhtar> tumbleweed: looking at the nginx issue, Why is the lintian error being discussed now? Why wasn't it discussed when it was added?
[13:59] <bilalakhtar> tumbleweed: BTW, adding the HTML files is not important
[13:59] <bilalakhtar> tumbleweed: Its just an added convenience
[14:00] <bilalakhtar> tumbleweed: and, there's no need to run checks, because nginx has /var/www as its root by default
[14:00] <bilalakhtar> unlike apache ^^
[14:00] <tumbleweed> bilalakhtar: people make mistakes
[14:00] <tumbleweed> (and are lazy)
[14:00] <tumbleweed> but it's easier to get sponsorees to do the right thing :)
[14:01] <bilalakhtar> tumbleweed: yup, it appears the previous uploader has taken up the issue
[14:01] <bilalakhtar> tumbleweed: and he is ready to get it fixed
[14:01] <tumbleweed> bilalakhtar: I disagree re the checks. /var/www is an area that belongs to the sysadmin, we shouldn't be messing with their things in there
[14:02] <bilalakhtar> tumbleweed: but see, nginx is a server of its own and not an add-on
[14:02] <bilalakhtar> tumbleweed: it conflicts with apache and lighttpd
[14:02] <tumbleweed> bilalakhtar: so, as a sysadmin, you installed nginx when you deployed your machine
[14:02] <tumbleweed> now you upgrade to a new version of ubuntu
[14:02] <tumbleweed> and suddenly files appear in your /var/www
[14:03] <tumbleweed> (new files, that you didn't expect)
[14:03] <bilalakhtar> tumbleweed: should we do what debian is doing?
[14:03] <tumbleweed> you mean not installing them?
[14:03] <bilalakhtar> yes ^^
[14:03] <bilalakhtar> they are an added convenience
[14:03] <bilalakhtar> and
[14:03] <tumbleweed> yes, that's the easy solution
[14:03] <bilalakhtar> it appears that no bug was filed to have them in there
[14:03] <bilalakhtar> in lp ^^
[14:04] <tumbleweed> yeah, fair enough to remove them then
[14:04] <bilalakhtar> then the only change from debian would be the ufw profile
[14:04] <bilalakhtar> its always better to clean up packages when merging
[14:05] <tumbleweed> agreed, we often end up with cruft
[14:05] <tumbleweed> bonus points if you look at any bugs in lp with patches :)
[14:06] <bilalakhtar> BTW, the html file addition was done way back in karmic
[14:06] <bilalakhtar> it skipped lucid
[14:06] <bilalakhtar> and
[14:06] <bilalakhtar> was detected in maverick
[14:06] <bilalakhtar> RoAkSoAx was the one who uploaded
[14:06] <bilalakhtar> RoAkSoAx: ping
[14:07] <tumbleweed> the curse/advantage of group maintainance - every time we touch a package, a different person works on it.
[14:07] <bilalakhtar> Its somewhat better
[14:07] <bilalakhtar> In debian, NMUs take a long time to get sponsored
[14:07] <bilalakhtar> here, almost every upload is an NMU
[14:07] <tumbleweed> helps if you are a DD :)
[14:08] <bilalakhtar> tumbleweed: are you a DD ?
[14:08] <tumbleweed> bilalakhtar: no, I need someone to want to advocate me
[14:08] <bilalakhtar> tumbleweed: I have 6 uploads in debian pending sponsorship, of which 5 are new packages and 1 NMU
[14:09] <bilalakhtar> I am hunting down debian IRC channels and asking people to sponsor that NMU which is 2 months old now. But, most of them tell me to contact maintainer, who has been unresponsive
[14:10] <tumbleweed> yup, unresponsive maintainers are a pain
[14:14] <bilalakhtar> tumbleweed: dammit, a confusing, two-way bug #547267
[14:16] <tumbleweed> there you go, you weren't th efirst to run into this
[14:16] <bilalakhtar> yup
[14:16] <bilalakhtar> and, RoAkSoAx has said that he forgot to add the reference to the bug
[14:16] <bilalakhtar> earlier, I mentioned that there was no bug
[14:16] <bilalakhtar> there is this one
[14:18] <vish> ScottK: tumbleweed: hey, [i think]found out why the lp janitor switches the name and email fields..  it seems to do that when the name has a . [dot], for some reason it doesnt like dots ;)
[14:19] <vish> tumbleweed: similar happened in Bug #532056
[14:19] <tumbleweed> vish: aha, file a bug :)
[14:20]  * tumbleweed has acutally just uploaded a (papercut) sponsorship with a .
[14:20] <vish> tumbleweed: yeah, should do that , bug in which...?  :)
[14:20] <bilalakhtar> vish: file a bug in malone
[14:20] <vish> bilalakhtar: malone!
[14:20] <vish> hrm..
[14:21] <bilalakhtar> vish: yes, the janitor is a part of malone
[14:21] <bilalakhtar> vish: https://edge.launchpad.net/malone
[14:21] <tumbleweed> vish: indeed: https://edge.launchpad.net/ubuntu/+source/acm/5.0-27ubuntu2
[14:21] <tumbleweed> bilalakhtar: I don't think this is malone, the problem is in th echanges file processing. soyuz?
[14:22] <bilalakhtar> tumbleweed: vish: Is the problem here as well? Aha
[14:22] <bilalakhtar> Go file in soyuz, vish
[14:23] <vish> tumbleweed: yeah, always wondered why it kept doing that.. finally found someone who suffers the same fate! ;p
[14:24] <bilalakhtar> vish: Yes, While looking at your uploads I thought why don't you follow the debian changelog policy!
[14:24] <vish> bilalakhtar: pff, policies ;p
[14:24] <bilalakhtar> vish: for adding changelog entries, I suppose you use dch
[14:25] <tumbleweed> bilalakhtar: the changelogs are correct, it's lp which has th ewrong data
[14:26] <bilalakhtar> tumbleweed: I know that
[14:27] <bilalakhtar> so soyuz grabs the latest changelog entry and tries to validate its e-mail address. Due to a dot in the name, it thinks the opposite and interprets the changelog in the wrong manner. malone just copies the data provided by soyuz
[15:02] <nthykier> tumbleweed: okay - TY
[15:49] <vish> DktrKranz: hi , does zipper work on Ubuntu or is it meant for use only after installing GNUstep?
[15:49]  * vish noticed DktrKranz made the last upload and might have some info.. :)
[15:59] <vish> DktrKranz: Bug #613301 was filed as its description seemed confusing for the user...  could you comment on it? thanks.
[16:05] <DktrKranz> vish: well, it's an app designed for GNUstep, so it requires at least base packages (e.g. gnustep-base). Perhaps description can be improved, but it should be done Debian side first (and there's currently an ongoing transition there)
[16:09] <vish> DktrKranz: ah yeah, maybe for that info could be included .  could you comment on the bug?
[16:10] <vish> DktrKranz: maybe we can ask the reporter to forward the bug to debian :)
[16:34] <DktrKranz> vish: done
[16:48] <ScottK> Rhonda: I did, but to provide an endorsement.  it seems odd to me people doing random edits on people's wiki pages, but maybe that's just me.
[17:21] <xelister> I fixed a 1 year old damn bug in krusader
[17:22] <xelister> how to build it now? I got sources via apt-get source + apt-get build-dep
[17:23] <geser> debuild
[17:53] <xelister> geser: ok.. now what?
[17:53] <xelister> Successfully signed dsc and changes files
[17:54] <xelister> but I dont see any .deb file
[17:56] <xelister> the modified by me sources seem to build, debuild seem to execute,  now how to install the builded package to test if program works correctly?
[18:01] <shadeslayer> xelister: cd ..
[18:02] <shadeslayer> and then : sudo dpkg -i foo.deb
[18:11] <xelister> shadeslayer: how to make a diff to be attached as .patch to LP bug report for the bug I fixed?
[18:11] <shadeslayer> !debdiff | xelister
[19:21] <vish> tumbleweed: hmm , i think there is a white space in the changelog. :s the second entry, probably why it was failing?
[20:29] <micahg> jdong_: ping?
[20:32] <Rhonda> ScottK: Yes, it's strange to some degree. Though, I don't see the big deal when turning channel names into links. :)
[20:37] <micahg> Rhonda: are you familiar with scons?
[20:38] <Rhonda> Not really. I gave it once a try wether switching from autotools to it for wesnoth would make a sense, but I sticked with autotools. Why do you ask?
[20:38] <micahg> Rhonda: having trouble getting mongodb to make a source upload
[22:08] <yofel> does anyone know if there's a reason why there are no -dbgsym packages for -backports?
[22:09] <micahg> yofel: maybe because they're not officially supported
[22:09] <yofel> was looking through old bugs and found bug 316227
[22:10] <micahg> yofel: also intrepid is EOL
[22:11] <yofel> yep, but NO release has dbgsyms for -backports so..
[22:12] <yofel> you can reproduce that failure with any package from lucid-backports
[22:12] <ebroder> yofel: My understanding is that extracting the dbgsym packages is a giant hack, and it's probably "just" that nobody has implemented that hack for anything but the main archive
[22:12] <ebroder> (I have no idea how much resistance there would be on the archive admin/buildd admin/etc admin side to adding functionality for extracting backports dbgsym packages)
[22:13] <yofel> erm, debug symbol extraction is on for lucid lucid-updates lucid-proposed and lucid-security, only -backports doesn't have them
[22:13] <ebroder> yofel: Exactly. Someone with the right powers cared enough to set it up for -updates, -proposed, and -security. Nobody with the right powers has cared enough to set it up for -backports
[22:19] <yofel> any idea where I should send that bug to then? soyuz?
[22:21]  * micahg thought -backports weren't officially supported
[22:21] <Rhonda> yofel: There is wesnoth-1.8-dbg in karmic-backports. Or is that something completely different?
[22:22] <micahg> Rhonda: different -dbgsym
[22:22] <yofel> Rhonda: that is a packaged -dbg package, we are talking about -dbgsym on ddebs.ubuntu.com
[22:22] <yofel> those are automatically generated for every package
[22:22] <yofel> (by the buildds)
[22:23] <Rhonda> ah
[22:25] <yofel> micahg: well, I think too that -backports is unsupported so I'll close the bug
[22:26] <ebroder> yofel: backports is supported, just not through the same mechanisms as the normal archive. It's on a volunteer basis, like universe
[22:29] <yofel> well, I'll just leave the bug as it is until tomorrow, if anyone knows who I should talk to about or where I should move that bug ping me
[22:30] <ebroder> yofel: Sorry - I wasn't clear. Backports are supported, but anything related to intrepid is unsupported. So that bug can be closed. It's a separate bug that backports aren't generating dbgsym packages
[22:31] <yofel> ok, that makes sense, closing


[00:15] <ActionParsnip> bethebunny: did you md5 test the iso?
[00:16] <bethebunny> I'm having trouble booting the install CD. The framebuffer window (with keyboard == human) appears fine, then the ubuntu loading screen is fragmented as though it is attempting to render the image to a different resolution than my monitor
[00:16] <ActionParsnip> bethebunny: did you md5 test the iso?
[00:16] <bethebunny> I'll go do that, but I'm having the same problem with an old 10.04 build on the same machine.
[00:16] <ActionParsnip> bethebunny: why did you not test it before?
[00:17] <bethebunny> ActionParsnip: It might be good practice, but I'm generally not in the habit of md5 testing my downloads >.>
[00:17] <ActionParsnip> bethebunny: you should, the data needs to be perfect
[00:26] <bethebunny> ActionParsnip: Yes, the hash matches.
[00:28] <ActionParsnip> bethebunny: what video chip do you use?
[00:28] <bethebunny> nVidia GT550TI
[00:28] <ActionParsnip> bethebunny: tried the boot option: nouveau.blacklist=1
[00:38] <bethebunny> ActionParsnip: It said something along the lines of "`1' is an invalid value for nouveau option `blacklist'", but then successfully booted without further graphical errors (well, it's not exactly full-featured, but I suspect the remaining problems are due to using a fallback graphics driver)
[00:39] <ActionParsnip> bethebunny: some chips don't like the nouveau driver.
[00:39] <ActionParsnip> bethebunny: you should know basic stuff like that if you want to use pre-release, its not ready for the lay-user
[00:40] <bethebunny> ActionParsnip: I'm sorry I tried dabbling in your deep and dark realm. I'll try growing out my neckbeard. Or maybe I should just switch back to gentoo.
[00:53] <ActionParsnip> did the boot option help?
[00:59] <vivid> bethebunny: nouveau is totally broken for me on that same GPU
[00:59] <ActionParsnip> in updated version its not shabby
[01:00] <vivid> i managed to install using the mini.iso and then manually installing nvidia-current and kubuntu-desktop via a base system
[01:00] <vivid> its still broken as of yesterday, when i cleaned up this system
[01:01] <vivid> so, dont be surprised when you get into a broken gui, be prepared to ctrl+alt+f1 and shut down lightdm
[01:01] <vivid> and quickly, the perpetual loop of lightdm restarts is a pain
[01:03] <vivid> bethebunny: and....i have a totally pimp neckbeard right now.  definitely helps getting through nouveau
[01:29] <ActionParsnip> vivid: have you tried kdm instead?
[01:30] <vivid> no need, default desktop installs lightdm and the aim is to get default working for the majority
[01:30] <vivid> and lightdm works wonderfully
[01:30] <ActionParsnip> vivid: from what you say, apparently not
[01:30] <vivid> the problem is nouveau
[01:30] <vivid> on GF114
[01:30] <ActionParsnip> i see
[01:37] <vivid> ActionParsnip: alternatively, we could argue that no vesa fallback is an issue as well
[05:16] <lapion> is it possible to install quantal to a btrfs-oonly system ?
[05:18] <ActionParsnip> sure
[05:19] <lapion> cannot get it to install grub
[05:20] <ActionParsnip> lapion: can you install it from liveCD?
[05:20] <lapion> yes
[05:20] <lapion> failt to install grub
[05:20] <lapion> *fails
[05:21] <ActionParsnip> isit a known bug?
[05:23] <lapion> do not know am trying to install it again, this time will try to manually install grub before exiting install environment
[05:30] <lapion> it gives me core.img unusually large error
[05:32] <ActionParsnip> http://forums.funtoo.org/viewtopic.php?id=828
[05:36] <lapion> I already found that one and was reading it.
[05:36] <ActionParsnip> ha
[05:37] <lapion> this only happens to systems whose hdd partition table is erased and recreated.
[05:37] <lapion> maybe the default chs should be something like n n 96 or something..
[05:44] <lapion> hmm no xz support in grub-mkimage
[06:23] <lapion> hmm installing synaptics in the live environment seems to make the system totally useless
[07:05] <lapion> has anyone tried to install synaptic in the live version ?
[07:05] <smartboyhw> lapion: You mean live CD?
[07:06] <lapion> yes
[07:58] <lapion> the grub error is a partition related problem solved by "creating" a new partition table, or recrating the mbr
[08:10] <lapion> hmm at least the not enough space error did nit repeat, but still no booting
[09:51] <vega-> seems most of new stuff on 12.10 will be "under the hood" type of things?
[11:00] <lapion> booting with a btrfs is not working it cannot find the files because when you mount the btrfs all files and folder of the fs reside in the folder "@" in stead of "."
[11:41] <BluesKaj> Hey all
[12:07] <pfarrell> hi, there seems to be a bug in the slepc package in quantal. Where should I report it?
[12:18] <smartboyhw> pfarell: Open a terminal and type ubuntu-bug slepc
[12:55] <lapion> ubuntu cannot handle btrfs
[12:57] <KM0201> i thought it was still pretty experimental
[13:42] <thoong> you guys suffer from nouveau booting problems from kernel 3.4 - 3.5? is it confined to kernel  or distro specific? currently running ubuntu 12.04 and fedora 17.  new kernel updates in f17 is giving me grief. was wondering will future ubuntu suffer same fate?
[15:12] <sandyd_away> bobweaver, http://i45.tinypic.com/14nub5.png
[15:12] <sandyd_away> that is what it looks like
[15:13] <bobweaver> loOking
[15:14] <bobweaver> Oh ccsm unity arch nemesis . Not sure that I can help with that sorry sandyd_away  maybe others can
[15:15] <sandyd_away> its alright, thanks for looking bobweaver
[15:15] <bobweaver> sandyd_away,  what happens when you go to font settings and play with them
[15:16] <sandyd_away> where?
[15:17] <bobweaver> not sure that is a great question
[15:18] <bobweaver> I thought that it was under gnome-control-panel but I can not seem to find
[15:18] <sandyd_away> nvm - fixed the problem
[15:18] <bobweaver> And font viewer is not seeeming to do anything but hang
[15:18] <sandyd_away> ccsm doing funky stuff
[15:19] <bobweaver> how did you fix it ? ccsm ?>
[15:19] <sandyd_away> yup
[15:19] <bobweaver> cool
[15:46] <em> hi
[17:14] <Bluefoxicy> Is 12.10 going to use 3.4 instead of 3.5.3 or 3.6?
[17:15] <trism> Bluefoxicy: depends on what you are talking about, for nautilus, yes, for kernels, I think we are sticking with 3.5
[17:17] <Bluefoxicy> kernel
[17:17] <Bluefoxicy> heh that was ambiguous.
[17:25] <trism> yeah too many similar version numbers this release
[19:44] <hd1> hmph
[19:44] <hd1> what happened to /usr/bin/X in quantal?
[19:46] <trism> hd1: -rwsr-sr-x 1 root root 10192 Aug 23 13:37 /usr/bin/X (seems to be there, what's the issue?)
[19:47] <hd1> what package is it to be found in?
[19:48] <trism> hd1: xserver-xorg
[19:49] <hd1> thanks trism, for some reason that package wasn't installed :p
[19:52] <cjohnston_> Is anyone else having a problem with ubuntu-panel-search using huge amounts of CPU? 99+%?
[19:56] <trism> cjohnston: maybe bug 1041354 (though a recent libreoffice update should fix that)
[19:59] <hd1> trism: ok, thanks
[19:59] <cjohnston> trism: that sounds about right
[19:59] <cjohnston> I'm updating right now, maybe ill get it
[20:00] <cjohnston> thanks trism


I ahve a server or sale.  Dell Poweredge 2900, with 2 73GB 15K RPM SAS drives, 8GB ram, and dual Quad core Xeon 2.5Ghz CPUs