[13:20] <Kangarooo> hello in #xubunut bot doesnt respond to bug 611869
[13:20] <Kangarooo> like it does it here
[13:20] <charlie-tca> You are correct. You have reported this already here, too.
[13:22] <Kangarooo> and it still not fixed. no one from irc team has replied to bug and hasnt fixed. its just an irc script..
[13:23] <Kangarooo> script works as we see here so bot has some limitation in script for executing response in #xubuntu .. maybe by accident. thats all i can think of what could be wrong to that bot
[13:23] <Pici> Kangarooo: The bot doesn't reply in #ubuntu or #kubuntu either.  Is there a reason why it should reply in #xubuntu?
[13:23] <Pici> rather, it doesn't reply to bugs in #k or #u
[13:24] <Kangarooo> yes its easyr to post short version just bug and nr not whole link in irc text line. so it will be removed? bot isnt needed?
[13:25] <Kangarooo> Pici: so it should reply in all ubuntu channels as it was in past
[13:25] <Pici> How often are bug #s posted there?
[13:25] <Pici> Kangarooo: When was the last time that it replied in #xubuntu to bugs? I don't recall us doing that in any of the main support channels
[13:25] <Kangarooo> why u ask? if giving some exact nr will change something?
[13:26] <jpds> Yes.
[13:26] <Kangarooo> is a reason if only 20 bug # are there a day a reason to remove it from channel? its written that that bug needs to be in that channel and work there
[13:27] <charlie-tca> I don't think we ever had 20 bug numbers a day in #xubuntu
[13:29] <Kangarooo> yes now i cheched it looks like 0-2 but sometimes max 5 (only one day as now checking only few irc logs) Pici
[13:31] <Kangarooo> why then isnt bug respone working in xubuntu and as now i get info also in ubuntu and kubuntu ?
[13:31] <Pici> Kangarooo: The bug parsing isn't enabled in #ubuntu or #kubuntu either.
[13:31] <jpds> Kangarooo: The bot doesn't reply to bug commands in #ubuntu or #kubuntu
[13:32] <Kangarooo> but why? is irc script crashed or it specially removed?
[13:32] <jpds> Kangarooo: It's removed as they are user channels.
[13:36] <Kangarooo> ok problem is that there should be 2 bots ubottu for bug responses and ubuntulog for logging. log bot isnt there ubottu doesnt work
[13:36] <Kangarooo> *log bot is there..
[13:37] <nhandler> Kangarooo: ubottu does more than just display links to bugs
[13:38] <Kangarooo> facts its giving. and bug responses.. something more also?
[13:40] <Pici> Kangarooo: ban tracking.
[13:42] <Kangarooo> all exept responses to LP bug nr work. why then bug responses doesnt work? why it was working in past?
[13:42] <Kangarooo> what has changed?
[13:44] <jpds> Kangarooo: Because they were turned off in the support channels
[13:44] <Kangarooo> yes cool. but why?
[13:45] <Kangarooo> what has changed to be turned them off?
[13:45] <Kangarooo> is it bad that it helps giving bug description?
[13:46] <Kangarooo> its taking too much LP traffic?
[13:57] <Pici> Kangarooo: It takes more bot processing power.
[14:00] <Kangarooo> so 0-2 bugs a day in #xubuntu takes some processing power but not a lot. also ubottu is already sitting in xubuntu and kubuntu and ubuntu . if ubuntu consumes a lot then kick bot out and put new bot to log. but for xubuntu i cant image how can be taken processing power of comp on witch bot is running.
[14:02] <Pici> Kangarooo: It needs to inspect every line of traffic for a bug# or url.  None of the other bot plugins need to do that.
[14:02] <Kangarooo> bot already sits in thouse channels and reads and logs all. that should take a lot but making 2 less bug nr responses is not big help to cool script comp
[14:02] <Pici> Kangarooo: ubottu doesn't log.
[14:02] <bazhang> it works with /msg ubottu here
[14:03] <k1l> Kangarooo: maybe it logs already, but it needs processing power to read and handle the logs for the bug ids. that is the problem
[14:03] <Kangarooo> im sure theres channel witch posts more bug nr then in xubuntu
[14:03] <Kangarooo> example #ubuntu-bugs
[14:03] <Kangarooo> :)
[14:04] <bazhang> Kangarooo, /msg ubottu it works fine
[14:05] <Pici> Kangarooo: We actually have a different bot in #ubuntu-bugs to deal with bug parsing.
[14:06] <Kangarooo> how much removing bug nr responses from xubuntu helped save processing power?
[14:07] <Kangarooo> bazhang: /msg ubottu bug 1 ? doesnt save time as just bug 1 did
[14:07] <k1l> Kangarooo: its removed for all channels. why are you taking this so personally?
[14:07] <bazhang> Kangarooo, I always keep a /msg open with ubottu
[14:10] <Kangarooo> btw bazhang i got different response from /msg ubottu bug 1 then in this chan. and opening /msg with ubottu isnt replacing as it was in past - posting in channel gives response in channel. msg ubottu gives back private. still processing power is used and since only private is procesed power result given then return of investment is very low on saving time
[14:10] <bazhang> Kangarooo, I doubt it will be activated in support channels. too much noise for one.
[14:12] <Kangarooo> why u doubt? all info is already writen. takes procesing but in private ubbotu can process and takes same processing power but less ppl get time saved.. they need to still open link to see if they know about bug reported programm or not..
[14:13] <bazhang> Kangarooo, it wont happen.
[14:13] <Kangarooo> if everyone who is in channel get bug nr then if all now will write /msg ubottu bug nr then really more processing power will be taken.
[14:14] <Kangarooo> also removing from ubuntu bug nr respones already a lot processing power is saved. is needed a new server for bot?
[14:21] <Kangarooo> btw ubottu doesnt replies in prive for bug bugnr
[14:23] <Pici> It does for me.
[14:24] <bazhang> same
[14:24] <Pici> Kangarooo: I'll bring it up during the next IRCC meeting, but I doubt that any action will be taken.
[14:27] <Kangarooo> no in private it doesnt work is its bad replacement. try bug 611869   or bug 2 ion private. bug 1 is like factoin maybe set couse it gives wrong info
[14:27] <Pici> bug 1 is a factoid.
[14:27] <Kangarooo> so its bad replacement
[14:28] <Pici> Kangarooo: Its possible that its working for us because we're operators.
[14:29] <Kangarooo> so even replacement doesnt work.
[14:29] <Kangarooo> and also replacemnt will still take processing power.
[14:30] <charlie-tca> Of course, there is always the idea that we don't actually need this in #xubuntu, too
[14:31] <Kangarooo> yes but now is bigger problems- processing power consumption.
[14:31] <charlie-tca> That is not our problem. It just is not needed
[14:31] <Kangarooo> since that is saved by removing bug nr help in ubuntu still it should be working in xubuntu
[14:33] <Pici> Kangarooo: I've added it to the IRCC meeting agenda, if you can attend that would be great, otherwise I'll just bring it up for discussion: https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda
[15:48] <Kangarooo> in witch channel will be meeting in that wiki isnt writen. in #ubuntu-meeting ?
[15:50] <Pici> Kangarooo: Yes.
[15:52] <vish> Kangarooo: salem :D
[15:52]  * vish hides
[16:00] <Kangarooo> vish: whats salem?
[16:01] <vish> Kangarooo: "witch channel" ;)
[16:01] <Kangarooo> 8/ ?in witch language?
[16:02] <Kangarooo> about what channel u ask? where meeting will be or where bot doesnt work?
[16:02] <vish> Kangarooo: hmm, nevermind,  i thought that was a typo in your previous question :)
[16:02] <Kangarooo> bot doesnt work in #xubuntu and #kubuntu and #ubuntu and meeting will be in #ubuntu-meeting
[16:03] <vish> Kangarooo: yes the meeting will be held in #ubuntu-meeting
[16:03] <Kangarooo> yes thats correct
[16:26] <Zic> hi, I am one of #ubuntu-fr* channel administrator contact and we want to drop #ubuntu-fr-geeks (our old #ubuntu-fr-ops) but I cannot get a contact with the actual +F
[16:26] <Zic> (who was in the past also a contact-admin of our team)
[16:38] <nhandler> jussi, tsimpson, Pici, topyli:  ^^^ (racoon97, the founder was last seen 24 weeks ago)
[16:42] <Pici> Zic: You just want the channel dropped, or would you like control?
[16:45] <Zic> Pici: just drop it, we were not planning to use it in the futur
[16:45] <Pici> nhandler: Could you please drop that channel?
[16:46] <nhandler> Pici: Yep, one second
[16:46] <Zic> s/futur/future/
[16:47] <nhandler> Zic: It has been dropped
[16:48] <Zic> nhandler: thank you ;)