[02:24] <joebob777as7_> ogra, you on?
[02:41] <gotama> Hi! Where can I get some information on how to configure ltsp 5. It seems that lts.conf is no longer the main configuration file.
[02:42] <joebob777as7_> what do you need gotama ?
[02:42] <gotama> configure for sound and the vesa drivers.
[02:43] <gotama> I have tried two days without any results.
[02:43] <joebob777as7_> oh i did it in lts.conf... with the mac address of each unit
[02:44] <gotama> exactly. This is what I need to read. information on configuration.
[02:44] <gotama> seems the ltsp 5 is a little different that ltsp 4.
[02:47] <gotama> Please tell me how can I use the mac address to use the vesa driver.
[02:49] <joebob777as7_> [mac address]  section in lts.conf like this [00:00:00:00:00]
[02:51] <gotama> Then, what is next XSERVER=vesa ?
[02:52] <joebob777as7_> not sure on that one... just do a search for lts.conf vesa you'll find it
[02:52] <gotama> Ok. Thanks a lot.
[02:54] <joebob777as7_> lol not a big help but np
[03:24] <Meshezabeel> /cls
[04:21] <gotam1> Hi! I'm working with edubuntu 7.04, ltsp 5. The xserver crashes a lot on the thin client. Is there any solution? How can I use the vesa driver? XSERVER  = vesa in the lts.conf file doesn't work.
[04:22] <joebob777as7_> you should be using gutsy... works much better with ltsp 5 gotam1
[04:23] <gotam1> Thanks, I am moving now.
[04:24] <joebob777as7_> ok are you upgrading or starting from the beta from scratch
[04:25] <joebob777as7_> ?
[04:25] <joebob777as7_> gotam1, ?
[04:25] <gotam1> I've have installed edubuntu dapper and one of the oldes thin clients is a pentium I, works fine.
[04:26] <gotam1> But with feisty I got a lot of troubles.
[04:26] <joebob777as7_> yeah but ltsp 5 is leaps and bounds above old ltsp's
[04:26] <joebob777as7_> i had issues with feisty as well
[04:26] <joebob777as7_> go with gutsy. i would start from scratch if possible from the beta download and then run updates
[04:27] <joebob777as7_> you will have an issue with cups for today but should be fixed tomorrow. final release will be in two weeks or so
[04:27] <joebob777as7_> brb in 10
[04:27] <gotam1> AS you say gutsy may be a better solution.
[04:28] <gotam1> I'm going to download it right now, thanks again.
[10:48] <infos> hi
[10:48] <infos> I need help with ltsp
[10:50] <infos> anybody?
[10:56] <infos> wake up people
[12:56] <RichEd> ogra: ping ?
[01:10] <ogra> RichEd, ?
[03:39] <tsurc> I've had an idea about load balancing edubuntu servers. I just don't know if it'll work or if my theory is flawed?
[03:44] <bddebian> Heya
[03:44] <Kamping_Kaiser> hey
[03:44] <Kamping_Kaiser> tsurc, neither do i
[03:44] <bddebian> Hi Kamping_Kaiser
[03:45] <Kamping_Kaiser> bddebian, hows it going?
[03:46] <tsurc> Kamping_Kaiser thanks for that. apparently though loadbalancing is in Gutsy already. So I'll be checking that out.
[03:47] <Kamping_Kaiser> tsurc, cool. let me know what its like
[03:47] <bddebian> Kamping_Kaiser: OK thanks, you?
[03:47] <Kamping_Kaiser> not to bad, thanks
[03:49] <tsurc> Kamping_Kaiser: will do, current;t 57% through a download of edubuntu-7.10-beta-server-i386.iso
[03:49] <tsurc> *currently
[03:50] <Kamping_Kaiser> :)
[04:34] <tsurc> Kamping_Kaiser: 100% burning as we speak.... wish me luck!
[04:36] <Kamping_Kaiser> tsurc, good luck!
[04:36] <Kamping_Kaiser> i'm going to bed in a few min, so i'll have to see the result tomorrow am
[04:53] <tsurc> 351pm here got lots of things to do yet. some of which involve giving the wife the heave ho ;) Fireworks anyone?
[04:53] <Kamping_Kaiser> night mate
[04:53] <Kamping_Kaiser> 00:23 here
[05:11] <LaserJock> ogra: is today supposed to be a fix-it-friday?
[05:13] <ogra> LaserJock, given that we onl yhave hours to final rc freeze i wont have time for more than RC bugs
[05:13] <LaserJock> oh, are we that far already?
[05:15] <LaserJock> ogra: how's disc space for RC?
[05:15] <ogra> thats fine
[05:15] <ogra> the udeb isnt
[05:15] <ogra> i'm very busy atm
[05:16] <LaserJock> sorry to bother
[05:16] <LaserJock> I was just thinking I better get the edubuntu-docs translations and upload
[05:18] <ogra> yeah
[05:18] <ogra> they want to freeze today
[05:18] <ogra> my efforts o fix the ltsp progressbar led nowhere its simply not possible to so want i want i think
[05:19] <ogra> so now i try to get it at least back to the feisty state
[05:19] <ogra> and try to get that in before they freeze completely
[05:20] <LaserJock> :/
[05:23] <ogra> hmm, at least the progress for compressing seems to work
[08:45] <joebob777as7_> sbalneav, you on?
[08:45] <joebob777as7_> down here at my other server...
[08:47] <joebob777as7_> ogra, you here?
[09:07] <joebob777as7_> when are times i have to rebuild client images? when i install server updates? when i install client updates?
[09:41] <sbalneav> joebob777as7_: yeah, here
[09:41] <sbalneav> When you touch anything in /opt/ltsp/i386/
[09:42] <joebob777as7_> so not when i install server updates... do i need to when i chroot in to install flash plugin and x11vnc?
[09:42] <joebob777as7_> sbalneav, also looks like my log out issue has gone away... :)
[09:43] <sbalneav> If you chroot in and add something, then you're touching /opt/ltsp/i386/
[09:43] <sbalneav> so yes.
[09:44] <joebob777as7_> ok good to know
[09:44] <joebob777as7_> do any updates on the server ever touch /opt/ltsp/i386/ ?
[09:45] <sbalneav> no
[09:45] <sbalneav> Server updates are fine, but anything you touch in /opt/ltsp, either by direct editing, or via the chroot command, requires a rebuild.
[09:47] <joebob777as7_> if i want to install a bunch of fonts should i just do it in the client chroot or are they different?
[09:48] <sbalneav> AFAIK fonts you can just install on the server, and the RENDER extention to X handles them.
[09:49] <joebob777as7_> ok
[09:50] <cbx33> hey all
[09:50] <sbalneav> Hey cbx33!
[09:51] <cbx33> hey sbalneav
[10:07] <lns> Can anyone share what typing tutor programs they're using under Edubuntu? I am looking for a good solution for elementary school students, something with things like nice graphics and games, but more importantly, progress tracking / reporting for the teachers.
[10:08] <lns> And I don't mean tuxtype or ktouch...those just aren't mature enough for real educational use by many students yet (sorry to say)
[10:09] <sbalneav> Seeing as how I've never actually learned to touch-type, and use a modified 4 finger system of my own design, I'd be the wrong guy to advise you on that :)
[10:10] <joebob777as7_> sbalneav, another question on my client i have chrooted in and was wondering why i'm seeing this:
[10:10] <lns> sbalneav, hahaha
[10:10] <joebob777as7_> http://pastebot.ltsp.org/331
[10:10] <lns> It would be *so* nice to have mavis beacon for linux. I learned on that in jr. high and I can type ~70-80wpm now.
[10:12] <sbalneav> That only gives me a list of what didn't install.  I'm sure there were probably errors for those packages during the install phase.  What were they?
[10:12] <sbalneav> And, do you have /proc mounted in the choot when you're updating?  Some packages look at /proc during install/upgrade.
[10:13] <sbalneav> dbus I know for sure does.
[10:16] <joebob777as7_> i just did sudo chroot /opt/ltsp/i386/ and then did apt-get update followed by apt-get install (java-package-name)
[10:17] <joebob777as7_> how do i mount proc when updating? never heard of it...
[10:18] <sbalneav> It's on the ubuntu wiki
[10:18] <sbalneav> Also in the handbook
[10:18] <sbalneav> mount -t proc proc /proc
[10:18] <sbalneav> while in the chroot
[10:18] <sbalneav> make sure to umount before you exit the chroot.
[10:19] <joebob777as7_> http://www.pastebin.ca/727164
[10:19] <joebob777as7_> to unmount just umount /proc?
[10:20] <sbalneav> yeah, line 81
[10:20] <sbalneav> Can not write log, openpty() failed (/dev/pts not mounted?)
[10:20] <sbalneav> That's the dbus
[10:20] <sbalneav> while in the chroot, yes.
[10:21] <joebob777as7_> ok thanks again!
[10:28] <joebob777as7_> sbalneav, one other issue we are having when we try to switch users: we get a permissions error
[10:29] <LaserJock> hi cbx33 and sbalneav
[10:29] <joebob777as7_> your user does not have permissions to create additional logins. Check your ~/.Xauthority setup.
[10:29] <joebob777as7_> ~/.Xauthority file badly configured or missing 100 Not authenticated
[10:31] <sbalneav> Quite possible.  Sounds like a bug
[10:31] <sbalneav> File a bug for it, and we can have a look at it.
[10:31] <joebob777as7_> ok does it have anything to me chmoding my user dirs to 701?
[10:31] <joebob777as7_> do i file it under ltsp-server?
[10:33] <sbalneav> joebob777as7_: Entirely possible, include that info in your bug report.
[10:33] <sbalneav> ltsp-server's fine.
[10:34] <sbalneav> Dunno if we'll get to it for gutsy or not, but it'll be fixed for hardy anyway.
[10:34] <joebob777as7_> bug fixes don't happen for updates?
[10:35] <sbalneav> Depends on if it's considered critical or not.
[10:35] <sbalneav> And/or we can find enough people to test it :)
[10:35] <sbalneav> And/or figure out how to fix it :)
[10:41] <joebob777as7_> some users are also not able to print. what log should i be looking at to see why?
[10:41] <joebob777as7_> i don't know if it's this or not: http://www.pastebin.ca/727191
[10:42] <sbalneav> Yeah, printing's not here.
[10:42] <sbalneav> #ubuntu+1
[10:43] <joebob777as7_> even if the server prints fine always?
[10:44] <sbalneav> You're running the printing on the server, right?
[10:44] <sbalneav> i.e., the programs are running on the server.
[10:45] <joebob777as7_> yes
[10:45] <sbalneav> So if the program's running on the server, and the print queue's on the server, you're problems on the server.
[10:45] <joebob777as7_> ok


[22:43] <gen0cide_> Anyone tried to install oracle java 7 using the upd8 ppa on ubuntu 12.04 SERVER? It wants to install all these graphics dependencies - google-chrome, firefox, etc. - anyone have any direction on how to get a headless oracle-java-7 going without all the graphics libs?


[08:00] <ApfH> Hello
[12:11] <pjotter> Hi people. I just tried installing Xubuntu 16.04 from a live CD and the installer seems stuck on a lot of "WARNING:root:can't add [packetname]..." Does anyone know what is going wrong here?
[14:06] <xubuntu90w> One question, I'm using Xubuntu (whatever version) trough VirtualBox and I always have the same problem: when I want to add Guess additions to put 1024x768 pix, appears an ISO to mount and there are some .exe's when I open, the result is an error that cannot open that file
[14:07] <xubuntu90w> I tried to input some code I saw on forums, but always with the same results
[14:09] <flocculant> let the cd run - in the filemanager which should open up, right click >open terminal here and then run the linux .run file - you will want sudo
[14:10] <flocculant> you can tab complete to make sure you get the filename correct
[14:14] <xubuntu90w> thanks for response. I opened the terminal and run the .run file, but appears another window with this message: This program must be run with administrator privileges. Aborting
[14:18] <xubuntu90w> thanks for response. I opened the terminal and run the .run file, but appears another window with this message: This program must be run with administrator privileges. Aborting
[14:22] <flocculant> as I said - you will want sudo
[14:24] <xubuntu90w> I don't know the code to be sudo :(
[14:25] <flocculant> it is sudo
[14:25] <Pici> xubuntu90w: its your password
[14:25] <flocculant> just sudo nameoffile.run
[14:31] <xubuntu90w> Appears "Command not found"
[14:31] <xubuntu90w> I put in my case: sudo VBoxLinuxAdditions.run
[14:33] <flocculant> xubuntu90w: please check you are in the correct folder to run it - the command looks right
[14:34] <flocculant> hence mention tab complete - it won't tab complete if you're not in the right place in the terminal
[14:36] <xubuntu90w> I'm in the disk directory mounted "VBOXADDITIONS v5.0.24_108355"
[14:37] <akxwi-dave> xubuntu90w, are in the terminal or in thunar file manager?
[14:38] <xubuntu90w> I'm on that directory that appeared once I click on guest additions and the disk mounted
[14:38] <akxwi-dave> ok
[14:38] <flocculant> you need to be in a terminal to run the command
[14:38] <flocculant> right click in there and 'open terminal here'
[14:38] <akxwi-dave> right click on any plain area of the file manager and select run treminal here
[14:39] <akxwi-dave> open terminal here that is
[14:39] <xubuntu90w> yeah, that was I did
[14:40] <akxwi-dave> in the terminal type in
[14:40] <akxwi-dave> sudo VBoxLinuxAdditions.run
[14:40] <xubuntu90w> and then I put my passwrd
[14:40] <akxwi-dave> yes
[14:40] <xubuntu90w> and finally appears the message I told: Command not found
[14:40] <xubuntu90w> (in spanish, orden no encontrada)
[14:41] <Unit193> akxwi-dave: Forgot ./
[14:41] <akxwi-dave> opppp   try      sudo ./VBoxLinuxAdditions.run
[14:41] <xubuntu90w> ok
[14:42] <akxwi-dave> Unit193, doh
[14:42] <flocculant> hah
[14:42] <xubuntu90w> hahaha yeah! This works
[14:42] <flocculant> same forgetting here too ...
[14:42] <flocculant> sorry xubuntu90w :)
[14:43] <xubuntu90w> haha no prob friend
[14:43] <xubuntu90w> :D
[14:50] <akxwi-dave> hides face in shame...
[14:51] <flocculant> nah - just change your nick or pretend I stole yours :)
[14:52] <akxwi-dave> that will do me
[16:03] <ranu> flocculant, not sure if you remember but I was having a problem with VLC and the screen lock, I found the solution: http://askubuntu.com/questions/668834/vlc-player-is-not-displaying-video-but-audio-works
[16:07] <flocculant> ranu: right the first time - no I don't remember :)
[16:08] <ranu> flocculant, no problem though :)
[16:08] <flocculant> looks a bit like the xubuntu clutter in parole (and other apps) issue
[16:09] <flocculant> hence us changing default from clutter there
[16:09] <flocculant> anyway - thanks for coming back and updating people :D
[16:10] <ranu> I still think that it has something to do with the problem in intel drivers (xorg), it never happened in older xubuntu versions (at least with me).
[16:11] <flocculant> ranu: possibly - an intel update recently fixed something else - rather unexpectedly
[20:26] <craigbass76> I've got a remote guy running a 14.04 livecd. Had him run apt-get install openssh-server, and after a sudo -i ran passwd xubuntu. I still can't ssh in.
[20:40] <genii> Should just be: passwd      ..as the default user which is named xubuntu. Then ssh in as user xubuntu and whatever password got set for that. After that use sudo to do admin things
[20:41] <genii> What you've done there is put a password on the root user, which normally is not allowed to ssh in
[20:41] <genii> ( or even have a valid login)
[20:44] <craigbass76> genii, well, as xubuntu I first just tried passwd. After we did the sudo -i, then passwd xubuntu (thought I was setting xubuntu's pass with that), then just passwd (thought I was setting root's with that)
[20:46] <craigbass76> We also got, both times, updated successfully, and I can't log in as either xubuntu or root
[21:01] <genii> craigbass76: If you're trying from some location on the other side of their internet, make sure the modem/router is forwarding port 22 to that machines LAN IP. If from inside LAN, make sure sshd is actually running by having him ssh localhost or his current IP
[21:05] <craigbass76> genii, He actually gets denied when running it. It's asking for a pass, so I'm assuming ssh is running. S'pose that's accurate?
[21:06] <Elec_A> Hi, I want to install KDE on my xubuntu, Is it ok if I add ppa:kubuntu-ppa/backports repository ?
[21:07] <genii> Elec_A: Just sudo apt-get install kubuntu-desktop ...after that you can start adding PPAs
[21:08] <Elec_A> genii: so should I add that PPA for Plasma 5.7 ? or not ?
[21:08] <knome> tbh, you should ask #kubuntu on kde specific issues
[21:08] <Elec_A> knome: but my OS is Xubuntu
[21:09] <knome> Elec_A, believe me, they know much more about installing plasma this and that than anybody here. and the core system is still ubuntu on both, so it doesn't really matter.
[21:10] <Elec_A> knome: nice, I just wanted to make sure the above PPA does not conflict with other packages.
[21:10] <Elec_A> I mean in Xubuntu
[21:11] <knome> xubuntu and kubuntu are very different; anything related to plasma will not conflict anything in xubuntu
[21:12] <genii> The main difference is it will replace the login with sddm, or if 14.04 then lightdm-kde-greeter


[02:49] -SwissBot:#ubuntu-news- ::Fridge:: Ubuntu Weekly Newsletter Issue 725 @ https://fridge.ubuntu.com/2022/03/07/ubuntu-weekly-newsletter-issue-725/ (by guiverc)
[16:26] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: The Best New Features in GNOME 42 @ https://www.omgubuntu.co.uk/2022/03/gnome-42-best-new-features (by Joey Sneddon)
[23:58] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: GNOME 42’s New Terminal and Text Editor are Available to Install on Ubuntu 22.04 @ https://www.omgubuntu.co.uk/2022/03/install-gnome-console-text-editor-on-ubuntu-22-04 (by Joey Sneddon)


[01:26] <mup> Bug #1590121 changed: [xenial][maas beta5] [arm64] system tries to enlist when I commission.  <MAAS:Invalid by newell-jensen> <https://launchpad.net/bugs/1590121>
[01:26] <mup> Bug #1617044 changed: [2.1] View Full History on Events doesn't show anything <MAAS:Invalid by newell-jensen> <https://launchpad.net/bugs/1617044>
[04:33] <mup> Bug #1662111 changed: when deploying 'virsh' type of machine(KVM), it repeats deploying constantly <MAAS:Expired> <https://launchpad.net/bugs/1662111>
[04:33] <mup> Bug #1673854 changed: Commissioning selects wrong boot drive on 3-disk KVM <MAAS:Expired> <https://launchpad.net/bugs/1673854>
[10:18] <mup> Bug #1691434 opened: Can not apply stage final, no datasource found! Likely bad things to come! <MAAS:New> <https://launchpad.net/bugs/1691434>
[10:27] <mup> Bug #1691434 changed: Can not apply stage final, no datasource found! Likely bad things to come! <MAAS:New> <https://launchpad.net/bugs/1691434>
[10:36] <mup> Bug #1691434 opened: Can not apply stage final, no datasource found! Likely bad things to come! <MAAS:New> <https://launchpad.net/bugs/1691434>
[12:07] <int-0x21> Hi, quick question
[12:07] <int-0x21> How do i connect to a deployed machine with ssh ?
[12:08] <int-0x21> I get permission denied publickey
[12:13] <BjornT> int-0x21: if you have added your public key to your account in maas, it should be possible to ssh to ubuntu@<ip>
[12:15] <int-0x21> Ah i might have confused it with the api key
[12:18] <int-0x21> Hmm adding the key i however get invalid key.
[15:56] <alanmac> Hello everyone - running MaaS on Ubuntu 16.04 - 2.2.0~rc3 (upgrading right now). Running into an issues that I'm unable to find the answer to - we are having an issue with our network and DHCP helpers currently. As a result of this, we have discovered that with this DHCP Helpers issue, when we reboot a node that has been provisioned by MaaS, the node will not boot from the drives. Console says that no UEFI devices found.
[15:57] <alanmac> Why would this cause an issue? Does MaaS indeed have to be online and fully accessible at all times for a server, already provisioned, to be successfully rebooted?
[16:04] <roaksoax> alanmac: no. That's a known bug
[16:05] <roaksoax> alanmac: https://bugs.launchpad.net/curtin/+bug/1680917
[16:08] <alanmac> roaksoax: Thanks! Is there a work around? Not seeing it in the ticket.
[16:09] <roaksoax> alanmac: the fix is here: https://code.launchpad.net/~blake-rouse/curtin/uefi-clear-reorder/+merge/323875 requires redeployment
[16:09] <roaksoax> alanmac: for work around, would be  to fix the boot order
[16:09] <roaksoax> or get maas back up, get machines to boot, fix the bootorder to boot from PXE/IPv4 first
[16:13] <alanmac> we will probably just do a re-deploy once our network is up and running properly again (new environment with new SDN vendor). PXE/IPv4 is set as first boot.
[16:16] <xygnal> roaksoax: its worked well, as did the fix code pre rc4
[16:17] <xygnal> there will be a new bug soon about image upload via MAAS
[16:17] <xygnal> we did not submit any info yet
[16:25] <alanmac> roaksoax: Could we just update grub on the existing working systems? adding --no-nvram to "GRUB_CMDLINE_LINUX_DEFAULT="?
[17:30] <roaksoax> alanmac: sorry, was on the phone. I dont think that would work. --no-nvram would keep whatever is set on the bios which i think it will try to pxe boot, and not fallback to boot from the disk
[17:31] <alanmac> ok. reason i ask about modifying grub is we have a few nodes that are set for OpenStack (openstack ansible - have a few vital components on these servers).
[19:45] <Budgie^Smore> oddball question for the day has anyone created a preseed file to do a core os and maas install?
[19:52] <setuid> Yes
[20:14] <roaksoax> alanmac: right, so I had to change my efibootmgr parameters manually to get them to work around the issue really
[20:15] <alanmac> ok... hmmm, probably just easier to install the signed kernel then?
[20:17] <roaksoax> alanmac: the kernel is installed
[20:17] <roaksoax> alanmac: but you just need the right boot order to fallback to disk after attempting to pxe boot


[00:37] <camrdale> bluekuja: I updated LP 155491 with a new debdiff
[00:37] <ubotu> Launchpad bug 155491 in torrentflux "Multiple security vulnerabilities in Edgy" [Medium,Confirmed] https://launchpad.net/bugs/155491
[15:04] <bluekuja> asac, hardy opened
[15:04] <bluekuja> asac, let me know when you have time for bittorrent
[16:02] <asac> bluekuja: ok .... where is the debdiff?
[16:02] <bluekuja> asac: https://bugs.edge.launchpad.net/ubuntu/+source/bittorrent/+bug/66795?
[16:02] <ubotu> Launchpad bug 66795 in bittorrent "Missing package dependencies in bittorrent-gui" [Undecided,Triaged]
[16:20] <asac> hmm i do not yet have setup a hardy dev env :)
[16:22] <bluekuja> asac: ^^
[16:24] <asac> bluekuja: isn't that ment for hardy?
[16:24] <bluekuja> asac: yup
[16:24] <asac> bluekuja: the debdiff still claims gutsy ... so its for hardy?
[16:24] <asac> or SRU?
[16:24] <bluekuja> he missed the release
[16:24] <bluekuja> :)
[16:25] <asac> ok
[16:25] <bluekuja> when he gets online, I'll ask for confirmation
[16:25] <bluekuja> asac: motu-p2p is up too
[16:25] <bluekuja> :)
[16:25] <asac> i saw that
[16:25] <asac> i think i will do that tomorrow ... together with your NM advocacy
[16:26] <bluekuja> great :)
[16:26] <bluekuja> gonna remind/ping you tomorrow
[16:26] <bluekuja> so you can have bug number
[16:26] <bluekuja> and every info
[16:26] <bluekuja> needed
[16:27] <bluekuja> asac: I would like to give admin status to you as well, if you agree
[16:32] <asac> sure
[16:32] <asac> thanks
[16:34] <bluekuja> asac: done :)
[16:35] <asac>  \o/
[16:37] <bluekuja> :)
[18:18] <bluekuja> heya camrdale
[18:19] <bluekuja> camrdale, https://bugs.edge.launchpad.net/ubuntu/+source/torrentflux/+bug/156163
[18:19] <ubotu> Launchpad bug 156163 in torrentflux "Please merge torrentflux from Debian-unstable" [Wishlist,Confirmed]
[18:19] <bluekuja> camrdale, #66795 will be done tomorrow with some other things by alexander
[18:19] <camrdale> bluekuja: hey, thanks for all your help
[18:19] <bluekuja> bug #66795
[18:19] <ubotu> Launchpad bug 66795 in bittorrent "Missing package dependencies in bittorrent-gui" [Undecided,Triaged] https://launchpad.net/bugs/66795
[18:19] <bluekuja> camrdale, np, happy to have you in
[18:20] <bluekuja> :)
[18:20] <bluekuja> camrdale, can you check bug #156163?
[18:20] <ubotu> Launchpad bug 156163 in torrentflux "Please merge torrentflux from Debian-unstable" [Wishlist,Confirmed] https://launchpad.net/bugs/156163
[18:20]  * camrdale checking ...
[18:20] <bluekuja> adding a comment there
[18:20] <bluekuja> as well
[18:20] <bluekuja> :)
[18:22] <camrdale> bluekuja: I'm not sure about the dependency on zip (I'll have to look into it), but the dependency on tar is definitely not needed
[18:22] <bluekuja> I dont know why it got added
[18:23] <bluekuja> camrdale, add your comment there then
[18:23] <bluekuja> and let me know about zip
[18:23] <bluekuja> so we can merge it
[18:23] <camrdale> I will
[18:24] <bluekuja> camrdale, just add what you said me know, saying you'll check zip
[18:24] <camrdale> ok
[18:24] <bluekuja> so he knows he have to be patient a bit more
[18:24] <bluekuja> :)
[18:25] <bluekuja> camrdale, one more thing, bug #66795 is meant for hardy right?
[18:25] <ubotu> Launchpad bug 66795 in bittorrent "Missing package dependencies in bittorrent-gui" [Undecided,Triaged] https://launchpad.net/bugs/66795
[18:26] <bluekuja> is not a gutsy SRU?
[18:26] <camrdale> well, I don't think it's working in gutsy
[18:26] <bluekuja> camrdale, k, then your debdiff should be updated
[18:26] <bluekuja> for gutsy
[18:26] <camrdale> so the bittorrent-gui package is unsusable
[18:26] <bluekuja> *hardy
[18:26] <bluekuja> you set gutsy
[18:26] <bluekuja> in the release
[18:27] <bluekuja> +bittorrent (3.4.2-11ubuntu3) gutsy; urgency=low
[18:27] <camrdale> I see what you mean, so I should just try and fix it for hardy, and ignore gutsy?
[18:27] <bluekuja> camrdale, it depends on which priority we have on it?
[18:27] <camrdale> main
[18:27] <bluekuja> is it worth to be fixed in gutsy?
[18:27] <camrdale> I'm not sure, I don't use it :)
[18:28] <bluekuja> does it match SRU policy requirements?
[18:28] <bluekuja> I mean if it's not really important
[18:28] <bluekuja> or if the package on gutsy works
[18:29] <bluekuja> we can put them for hardy
[18:29] <bluekuja> but if the package in gutsy
[18:29] <bluekuja> doesnt work
[18:29] <bluekuja> or causes loss of data
[18:29] <bluekuja> or whatever
[18:29] <bluekuja> we move to SRU
[18:29] <camrdale> the package in gutsy doesn't work (no data loss though)
[18:29] <bluekuja> what do you mean with doesnt work?
[18:29] <bluekuja> doesnt startup?
[18:30] <camrdale> when you start it you get instant error
[18:30] <bluekuja> so i'ts unusable
[18:30] <camrdale> see also LP 155583
[18:30] <ubotu> Launchpad bug 155583 in bittorrent "/usr/bin/btdownloadgui.bittorrent complains about missing wxPython" [Undecided,New] https://launchpad.net/bugs/155583
[18:31] <camrdale> brb
[18:32] <bluekuja> I'm testing it
[18:32] <bluekuja> at
[18:32] <bluekuja> m
[18:33] <bluekuja> ok
[18:33] <bluekuja> bug is there
[18:33] <bluekuja> now testing the one with your debdiff
[19:05] <camrdale> I think my Internet died
[19:07] <bluekuja> camrdale, I've built the fixed package
[19:07] <bluekuja> now testing
[19:07] <bluekuja> (was having dinner)
[19:07] <camrdale> my internet was out for a little bit, but seems to be back now
[19:07] <camrdale> I updated LP 156163
[19:07] <ubotu> Launchpad bug 156163 in torrentflux "Please merge torrentflux from Debian-unstable" [Wishlist,Confirmed] https://launchpad.net/bugs/156163
[19:08] <camrdale> summary: zip needed, tar not needed
[19:08] <bluekuja> great :)
[19:08] <camrdale> new Debian version is coming
[19:08] <bluekuja> great
[19:08] <bluekuja> now checking bitttorrent
[19:10] <bluekuja> camrdale, works fine now
[19:10] <bluekuja> but is the download error normal?
[19:10] <bluekuja> when launching it?
[19:10] <bluekuja> (btdownloadgui.bittorrent)
[19:10] <camrdale> if you don't specify a torrent, yes
[19:10] <bluekuja> true, fine then
[19:10] <bluekuja> I add a comment for you in the bug
[19:10] <camrdale> thanks
[19:16] <bluekuja> camrdale, done ;)
[19:16] <bluekuja> check it
[19:16] <bluekuja> otu
[19:16] <bluekuja> *out
[19:21] <camrdale> argggh, I'm still having problems with the web, I'll have to check it later
[19:22] <bluekuja> ok, fine
[19:22] <bluekuja> important is to have it done
[19:22] <bluekuja> for tomorrow
[19:37] <camrdale> bluekuja: so for the bittorrent fix I should create a debdiff for gutsy-proposed, but what about hardy? will it get the new package from gutsy-proposed?
[19:37] <bluekuja> camrdale, I guess no
[19:38] <bluekuja> camrdale, if it will be accepted for gutsy
[19:38] <bluekuja> I'll ask for inclusio
[19:38] <bluekuja> in hardy as well
[19:38] <bluekuja> dont worry
[19:38] <camrdale> thanks, I should be able to upload the new debdiff tonight
[19:38] <bluekuja> camrdale, great, tomorrow we can have it fixed, so I can mail motu mailing list
[19:39] <bluekuja> for testing it out
[19:39] <bluekuja> and acking for gutsy
[19:39] <bluekuja> and later hardy
[19:39] <bluekuja> ;)
[19:54] <bluekuja> hi ember
[19:54] <bluekuja> I would like you to start contributing a bit
[19:55] <bluekuja> before gaining membership
[19:55] <ember> ok
[19:55] <bluekuja> as you can see existing members
[19:55] <bluekuja> are all developers
[19:55] <bluekuja> or maintainers
[19:55] <bluekuja> so If you can start up bug reporting testing
[19:55] <bluekuja> would be great
[19:55] <bluekuja> ember, tomorrow we will upload anew bittorrent version
[19:55] <bluekuja> to -proposed
[19:55] <bluekuja> and we need some feedback
[19:56] <bluekuja> that's a good starting point
[19:56] <bluekuja> to get involved
[19:56] <bluekuja> :)
[19:56] <ember> okidoki
[19:56] <ember> heh
[19:56] <bluekuja> :)
[19:56] <bluekuja> just hang around
[19:56] <bluekuja> the channel
[19:56] <bluekuja> so I can reach you easily
[19:56] <ember> np
[19:56] <ember> just ping me if u need something
[19:57] <bluekuja> I will tomorrow for sure
[19:57] <bluekuja> with some links


[07:45] <nlsthzn> Goeie môre Suid Afrika :)
[07:46] <nlsthzn> ah yes a lazy Sunday in ZA land
[09:02] <paddatrapper> Hi nlsthzn
[09:58] <nlsthzn> hey paddatrapper ... sorry had popped out to the shops :)
[09:59] <paddatrapper> nlsthzn: no worries.  Nope sitting in Brussels airport. Hope to be back 10am tomorrow
[10:01] <nlsthzn> uncle Kilos , allo
[10:01] <paddatrapper> Been a nightmare of a flight...
[10:01] <Kilos> did you enjoy it
[10:01] <paddatrapper> nlsthzn: tired.  The problem wasn't long flights, but I apparently needed a Schengen visa to be allowed on my Brussels -> Frankfurt plane. Thankfully immigration was able to reroute me through London
[10:03] <Kilos> wow
[10:03] <paddatrapper> But the stress around it has been exhausting
[10:03] <Kilos> yes
[10:03] <Kilos> come home and rest
[10:03] <paddatrapper> I don't plan on leaving home any time soon!
[10:03] <Kilos> lol
[10:05] <Kilos> now you have had the experience, was a shocker for me as well first time away from za
[10:05] <Kilos> not fun at all
[10:08] <nlsthzn> it is a culture shock for sure
[10:33] <nlsthzn> \o/ spelling working again... thanks hunspell <3
[11:23] <Kilos> lol
[11:45] <nlsthzn> it is important :p
[13:12] <nlsthzn> hmmm... currently running archlabs with i3wm, and it is a bit of a frog in a blender situation but it works for the most part :p


[11:19] <faa> meena: and FreeBSd congratulation
[12:07] <meena> faa: thank you!
[12:46] <meena> So, I'm trying to implement an ifconfig parser for net/*bsd; and I'm trying to figure out where best to put it, because the equivalent of that thing would be all the `/sys` reading methods / functions in Linux land. in BSD, an ifconfig -a would give us all that info; and I'd like to put it into a structured form… a structured form already exists:
[12:46] <meena> NetworkState but doesn't seem to be used for any such thing
[14:42] <holman> cjp256: Morning! Thanks for the follup in #1725.
[14:42] <holman> Do you think the potential work items there are release blockers, or is that work that could go into 22.4?
[14:42] <holman> If not required in 22.3 I'll move forward with release, but I wanted to double check with you first :)
[16:31] <cjp256> holman: i'd be more comfortable with the error handling addressed for the update_metadata_is_supported path + the instance id fix.  I have the latter one in queue I'm less sure about the former.  If we raise an exception instead of returning False, I assume cloud-init will exit/fail early and what state would we be in?  I'll talk to Anh
[19:11] <holman> cjp256: No problem, sounds good. I reviewed and merged the instance id fix. I'll let blackbox speak to the exception / false bit, seems like he had thoughts on that (blackbox isn't around today, so it will probably be tomorrow).
[19:21] <faa> meena: yes parsing ifconfig is hard, some utils updated and now parsing friendly example netstat -A --libxo json
[19:23] <meena> faa: I would like to add --libxo to ifconfig… but that will take a while to trickle down
[19:24] <meena> faa, but it's not about how tricky it is, it's about where it structurally best fits these days
[19:25] <meena> a lot has changed since i last worked on cloud-init
[19:30] <faa> yes is old dream https://reviews.freebsd.org/D25447 but now early developed netlink https://reviews.freebsd.org/D33975
[20:07] <meena> faa: libifconfig via ffi was another idea suggested
[20:07] <meena> i just feel for most admins, libxo is a lot more useful


[00:06] <SlidingHorn> studio-user493: 18.10 is a development version that just opened.  It is not recommended for regular use at this time
[00:08] <studio-user493> i see


[16:11] <cvb> hello...
[16:13] <cvb> hello...
[17:59] <AlanBell> hi all
[17:59] <AlanBell> #start meeting IRCC
[17:59] <AlanBell> #startmeeting IRCC
[17:59] <meetingology> Meeting started Sun Jun 24 17:59:59 2012 UTC.  The chair is AlanBell. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:59] <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
[18:00] <Unit193> Howdy.
[18:00] <AlanBell> hi all
[18:00] <AlanBell> who is here for the meeting?
[18:00] <topyli> hey
[18:01] <DJones>  /
[18:01] <Pici> ♫
[18:01] <Pici> er, \o
[18:01] <IdleOne> o/
[18:01] <m4v> hi
[18:02] <jussi> o/ vaguely, crying baby
[18:03] <AlanBell> #topic Review last meetings action items
[18:03] <AlanBell> so actions from last time, lets see
[18:04] <AlanBell> alanbell to sort out removal of eir
[18:04] <AlanBell> #fail
[18:04] <AlanBell> so I was going to do this because uBOTu-fr was going to take over, but it was missing
[18:04] <AlanBell> lets come back to that whole question a bit later when we have a topic dedicated to it
[18:05] <AlanBell> #topic Welcome to the new IRCC member
[18:05] <AlanBell> welcome Tm_T \o/
[18:05] <IdleOne> Welcome and congrats Tm_T !
[18:05] <topyli> yay Tm_T !
[18:05] <Pici> Woo, Tm_T!
[18:05] <DJones> Congrats Tm_T
[18:05] <IdleOne> No new taxes!
[18:06] <topyli> finns love taxes, beware
[18:06] <AlanBell> the results of the election were announced by the Community Council the other day and Tm_T is now our 5th IRCC member
[18:06] <AlanBell> launchpad groups and channel access and suchlike has been set up
[18:07] <Pici> launch codes, etc.
[18:07] <AlanBell> if only
[18:07] <IdleOne> Pici: not the abort codes right?
[18:07] <AlanBell> #topic Open items in the IRCC tracker
[18:07] <pleia2> just a quick note, I added his expire time as the same as the rest of you, but that's just because it's not something we've discussed
[18:08] <pleia2> we (CC and IRCC) should probably pick that up at some point
[18:08] <AlanBell> pleia2: yeah, I saw that, thanks
[18:08] <Pici> Yep
[18:08] <AlanBell> pleia2: setting the expire time the same was something we had planned and stated a few times
[18:08] <topyli> hm, wasn't that in the initial announcement that we're looking for the missing member?
[18:08] <pleia2> even better
[18:09] <Pici> ooh, problem solved already? I like this.
[18:09] <pleia2> me too :)
[18:09] <TheLordOfTime> heh
[18:09] <IdleOne> item closed.
[18:09] <jussi> too good to be true, watch it...
[18:09] <AlanBell> ok, so the tracker, we do have an open item in it relating to the user mcloy
[18:09] <AlanBell> I closed it once and it reopened :(
[18:10] <AlanBell> and we have another email today relating to some kind of appeal
[18:10] <IdleOne> what is the issue exactly with mcloy?
[18:10] <IdleOne> or can we not discuss that here?
[18:10] <Pici> Which was sent to both lists, but we'll be taking it
[18:10] <AlanBell> so it was
[18:11] <topyli> i rejected the message to the irc-team list and accepted the one to the council
[18:11] <topyli> public vs private and all that
[18:11] <AlanBell> good stuff
[18:11] <Pici> topyli: oh, good, good.
[18:12] <AlanBell> Shano56 is the user involved in that appeal
[18:12] <topyli> personally i think it's being handled just fine by ops
[18:12] <AlanBell> IdleOne: I would rather not discuss individual stuff here as a general rule, just being open about what appeals are going on
[18:12] <Pici> I think we should just talk about it 'offline' (so to speak).
[18:13] <Pici> AlanBell: which is what I was trying to get at.
[18:13] <IdleOne> sounds good. the Shano56 thing I think was handled properly.
[18:13] <AlanBell> ok, so that is the tracker
[18:13] <AlanBell> #topic Review Bugs related to the Ubuntu IRC Council
[18:14] <AlanBell> no new bugs
[18:14] <AlanBell> #subtopic bug 892500 eir is still not fit for purpose in #ubuntu -ikonia
[18:14] <AlanBell> lets come back to that one in a sec
[18:14] <AlanBell> #subtopic bug 913541 there are a number of people with Ubuntu IRC cloaks who have expired from the ubuntumembers group
[18:14] <AlanBell> Pici: have you had a poke at this one?
[18:15] <Pici> AlanBell: I did, and then I got terribly busy with work stuff.  Keep it on my docket, I'll make some time to deal with it.
[18:15] <AlanBell> ok
[18:15] <AlanBell> #topic alignment of launchpad teams and channel access lists
[18:15] <AlanBell> I did some of this and sent a few mails to the lists about it
[18:15] <AlanBell> I ticked off the big channels
[18:16] <IdleOne> ticked off as in upset?
[18:16] <AlanBell> heh, hope not
[18:16] <Pici> as in marked the checkboxx.
[18:16] <IdleOne> ah, k.
[18:16] <AlanBell> then there was the IRCC election stuff and other things which distracted me
[18:17] <AlanBell> but I will continue with that and get it to a point where we can automate it
[18:17] <AlanBell> there was also a kubuntu council election which changed some kubuntu stuff
[18:17] <IdleOne> Congrats to jussi for being elected to Kubuntu Council
[18:17] <IdleOne> :)
[18:17] <Pici> Grats Jussi!
[18:17] <AlanBell> yes indeed!
[18:18]  * jussi blushes and hides
[18:18] <topyli> :)
[18:18] <AlanBell> any comments on the access list processing so far?
[18:19] <Pici> No issues from over here.
[18:19] <AlanBell> #topic Review #ubuntu-ops-team (Quarterly)
[18:20] <AlanBell> this is a standing item we insert quarterly
[18:20] <topyli> we've done this a couple of quarters now, and been generally happy. i think we could stop reviewing it
[18:20] <AlanBell> the #ubuntu-ops-team channel is an invitation only channel for operators and a few others who are invited
[18:20] <jussi> Pici mentioned about offtopic in there - do we want to talk about that?
[18:20] <topyli> that doesn't mean we shouldn't address any specific issues
[18:21] <Pici> knome, Unit193 and I had a good discussion the other day about offtopicness in -ops-team
[18:21] <AlanBell> jussi: sure
[18:21] <topyli> jussi: well, there are a couple of valid but somewhat contradicting views, so it deserves discussion
[18:22] <topyli> 1) offtopic stuff isn't coordination. 2) not all ops are in the same offtopic channels and thus will miss each other lolcats if they're not allowed in -ops-team
[18:22] <Pici> I had originally suggested to move the offtopicness into #ubuntu-offtopic, but there were problems with that suggestion, mainly that its very #ubuntu centric (Rather than #x/#k#/l etc).  So the comprimise that we agreed on was to try to seed some of the good conversations that we have been having there into the various offtopic channels.
[18:23] <AlanBell> I am quite comfortable with the concept of #ubuntu-ops-team, I think it is really useful to separate that from the #ubuntu-ops channel
[18:23] <guntbert> seeding good conversations into ot channels sounds *very* good
[18:24] <topyli> AlanBell: absolutely. that's why i'm suggesting we stop reviewing its existance
[18:25] <Pici> But publicly reviewing anything that we may have brought up in there (that should be made public) isn't probably good.
[18:25] <Pici> er, s/isn't/is/
[18:26] <Tm_T> sorry for my late arrival
[18:26] <AlanBell> hi Tm_T
[18:26] <IdleOne> o/ Tm_T
[18:26] <topyli> hi Tm_T. welcome to the meeting and to the council :)
[18:26] <Pici> Anyway, the point was to be conscious of the offtopicness, and try to bring it into our offtopic channels if the parties involved are there as well.
[18:26] <AlanBell> does anyone think we should review the #ubuntu-ops-team channel in a further three months, or not bother as per topyli's proposal?
[18:26] <jussi> the point of the review is to make sure it isnt becoming clique and being abused
[18:26] <Pici> And again, this isn't a blanket ban on being able to socialize in there, just something to keep in the back of your head.
[18:27] <topyli> i think jussi and Pici are saying the same thing
[18:27] <IdleOne> AlanBell: I think keeping the review process is a good thing and won't hurt.
[18:27] <AlanBell> topyli: I am thinking that 5 minutes per quarter isn't a big deal, but we should focus on how we are using it rather than whether it should exist
[18:28] <topyli> yes
[18:28] <IdleOne> Will serve as a reminder to us to try and keep the channel on topic as much as possible.
[18:28] <Tm_T> that
[18:28] <AlanBell> ok lets move on, and I will swap the next two agenda items
[18:28] <jussi> AlanBell: ++
[18:28] <AlanBell> #topic Make #ubuntu-offtopic +r (discussion on the merits of this)
[18:29] <AlanBell> this was something ikonia asked us to think about
[18:29] <TheLordOfTime> i'm not on the ircc, but would ikonia care to explain the background of this?
[18:29] <Pici> We breifly weighed the pros and cons, but we suggested that he add it to the meeting agenda anyway.
[18:29] <AlanBell> as one possible way to improve conversations in -offtopic and stop a little bit of random abuse
[18:30] <IdleOne> making the channel +r will make it more difficult for the #ubuntu ops to direct new users to the channel when needed
[18:30] <TheLordOfTime> i agree with IdleOne on this one
[18:30] <TheLordOfTime> a majority of #ubuntu is unregistered
[18:30] <jussi> whatever happened to #ubuntu-discuss? wasnt it part of the master plan?
[18:30] <AlanBell> I asked ikonia to figure out how much of #ubuntu-offtopic was unregistered
[18:30] <Pici> jussi: still up in the air.
[18:30] <topyli> there is some obvious merit. less random noise, and also easier bans :)
[18:31] <IdleOne> meaning, not only do we have to explain that they are off topic and to change channel but then explain how to register. if the channel is open then we can take the registration "support" and help the user in -ot
[18:31] <TheLordOfTime> ^ that
[18:31] <Tm_T> I don't like restricting -ot nor necessarily the idea of extra -discuss
[18:31] <Pici> IdleOne: I think we already have enough pain when trying to direct folks to ##java, and simiular channels.
[18:31] <topyli> IdleOne: good point
[18:31] <DJones> There's a lot of occasions when new users are directed to -ot rather than #u when they want just general info, they're unlikely to be registered (new to IRC etc), which will cause confusion & potentially push them away from ubuntu
[18:32] <IdleOne> Pici: in #u you mean? yes, why add to it by restricting -ot?
[18:32] <Pici> IdleOne: Exactly.
[18:32] <IdleOne> ok :)
[18:32] <guntbert> to my eyes "abuse" has diminished significantly - there have even been some quality discussions
[18:33] <Pici> Well yeah, but only when we're not scaring off our -offtopic operators ;)
[18:33] <Pici> guntbert: but seriously, I agree.
[18:33] <Tm_T> I have my hope on leading by example (not by me necessarily)
[18:33] <IdleOne> -1 to setting -ot +r
[18:34] <Pici> And the folks who are determined to troll aren't going to be deterred by it being set +r, just the folks who want to casually chat.
[18:34] <IdleOne> also, sometimes a two hour chat about kittens is quality
[18:34] <AlanBell> ok, it sounded quite an appealing suggestion to me, but those are good points about directing new people to it
[18:35] <topyli> i'll say -1 too. -ot is an old channel and hasn't really become any *worse* over the years. this whispers to me not to rock the boat
[18:35] <AlanBell> but I do think that new people should be directed to somewhere to discuss Ubuntu rather than kittens
[18:35] <Tm_T> it would just make -ot even more of a place for limited circle instead of whole community
[18:35] <AlanBell> (or other small fluffy/feathery creatures)
[18:36] <topyli> AlanBell: i think the lolcat discussions most often pause when real ubuntu discussion is starting to take place
[18:36]  * TheLordOfTime agrees with Tm_T's view
[18:36] <IdleOne> AlanBell: We discuss Ubuntu a lot in -ot, just that some people take great offense to Ubuntu being put down. e.g. UNITY SUCKS!
[18:36] <guntbert> AlanBell: as long as one discussion doesn't drown the other, I see no problem with discussing pets
[18:36] <Pici> A UNITY SUCKS discussion is neither a) constructive nor b) something that 99% of the folks there want to discuss.
[18:36]  * AlanBell is all in favour of chicken related discussions
[18:37] <IdleOne> many of the people who start out with that sort of comment about Ubuntu end up having excellent points
[18:37] <DJones> Possibly a different thought process needs to be gone through from #u etc when directing people to -ot, at times it possibly gets used to redirect non-coc comliant conversations to to -ot rather than just asking them to stop the conversation all-together, not by ops, but by general #u users
[18:37] <topyli> there's very good unity criticism there as well, worthy of being directed to #ubuntu-desktop or similar really :)
[18:37] <Pici> IdleOne: true, but then again we've heard most of the arguments for/against it already. but lets not get too sidetracked.
[18:38] <IdleOne> Pici: I hear you
[18:38] <AlanBell> yeah, this item was about setting it +r, and it seems on balance that isn't going to be a good idea, so lets not do that then
[18:38] <Pici> DJones: I've been pretty quick to point that out to folks who mash !ot instead of telling people to stop.
[18:38] <IdleOne> Anyway, I want to be able to send new Ubuntu/IRC users to -ot without having to send them to #freenode first to get help registering
[18:38] <guntbert> DJones: so we should decide if !ot is to be used or some other factoid (in #u)
[18:39] <Pici> AlanBell: agreed.
[18:39] <AlanBell> ok, so moving on once more
[18:39] <AlanBell> )
[18:39] <AlanBell> #topic ubottu, uBOTu-fr and eir
[18:39] <Pici> Lets try to get through the rest of the agenda, and then we can move back to the State of Offtopic afterwards if we have time.
[18:39] <AlanBell> so, bots
[18:39] <Pici> yep
[18:40] <Pici> can't live with'em, oh... wait, thats somethinjg else...
[18:40] <topyli> eir database is growing by the minute, as ikonia reminded us today in -irc-council
[18:40] <AlanBell> I was going to get eir removed so we could focus on uBOTu-fr
[18:40] <AlanBell> but uBOTu-fr was missing in action, and m4v raised some points about the test suite not passing
[18:41] <IdleOne> AlanBell: do we have a working ubotu-fr to use in #ubuntu yet?
[18:41] <Pici> Sounds like we might not.
[18:41] <AlanBell> I grabbed a copy of the source today to have a look at what it does
[18:41] <IdleOne> then I say we hold off until there is a known working replacement for eir
[18:41] <Tm_T> I'd say first u-fr up to shape and then drop eir
[18:42] <IdleOne> eir is not perfect but it is better than nothing for now
[18:42] <m4v> I don't want to maintain a supybot fork for stuff that should be in a plugin.
[18:42] <Pici> I think it might be good to trial u-fr (once it gets back up to spec) in some of our other high traffic channels
[18:43] <oCean> We should not start with trials with any bot, until we have a agreed on set of requirements
[18:43] <AlanBell> https://docs.google.com/spreadsheet/ccc?key=0ApW_s9q9E0zEdE9naVF4c0xjTUhpelZnZTFoYzZWNVE#gid=0
[18:43] <Pici> oCean: I thought we already had a list somewhere
[18:43] <AlanBell> requirements ^^
[18:43] <Unit193> May see if you can get some of that into a plugin, and general stuff into an existing fork.
[18:44] <oCean> Pici: we had a list of bugs for eir, the link AlanBell posted is where I started a little while ago
[18:44] <oCean> This could be where to start from. Decide which are the Must/Could/Should haves etc
[18:44] <AlanBell> yeah, I like the list oCean
[18:45] <m4v> well, there's the stuff we wrote for the next bt http://ubottu.com/devel/wiki/Spec/Bantracker
[18:46] <oCean> m4v: yeah, that is another point. The BT
[18:46] <oCean> we should not see those to apart from each other, is what I think
[18:46] <IdleOne> the requirements look good to me
[18:46] <oCean> those two*
[18:46] <m4v> oCean: another? isn't the BT the point we're discussing?
[18:47] <oCean> m4v: we have focussed on bot functionality a lot
[18:47] <m4v> there's the idea of using ubotu-fr because our bt doesn't have automatic removal of bans
[18:47] <oCean> for example, we started with eir, while we knew there was no integration with the BT
[18:48] <AlanBell> yeah, I am not sure why we don't just write ban expiry into the existing ubottu channel plugin
[18:48] <AlanBell> or a separate plugin
[18:48] <oCean> Yes, I'm all for that, AlanBell
[18:49] <oCean> however, I don't have the knowledge/skill to do that
[18:49] <m4v> AlanBell: ubottu bantracker plugin, ubotu-fr channel plugin is a rewrite of a supybot core plugin.
[18:50] <AlanBell> yeah, I saw that
[18:50] <Pici> I think we have enough python/supybot skill here to make that happen, but the issue was that we sort of felt that the current Bantracker system needed a lot of love in various places to bring it up to spec.
[18:50] <IdleOne> which m4v gave it did he not?
[18:50] <oCean> Pici: Indeed, it still does
[18:50] <m4v> well, I have been looking how to add automatic removal in ubottu, I think it can be done, but are we going to have ubottu +o all the time?
[18:51] <oCean> m4v: eir isn't +o all the time
[18:51] <Pici> I personally don't have a problem with that, as long as she doesn't go haywire.
[18:51] <AlanBell> m4v: maybe, or can it just talk to chanserv?
[18:51] <IdleOne> m4v: ubottu only needs +o when setting the modes
[18:51] <Pici> AlanBell: chanserv can't unban people.
[18:51] <Pici> Well, other than yourself.
[18:51] <AlanBell> orly
[18:52] <m4v> ok, so needs to request op when needed.
[18:52] <TheLordOfTime> yep
[18:52] <IdleOne> AlanBell: something about accountability and not abusing chanserv to do nasty things
[18:52] <Pici> Being opped all the time is less noise that opping up, unbanning, and deopping.
[18:53] <AlanBell> ah, ok, unban is only for self
[18:53] <m4v> Pici: is also easier to implement, that's why I asked
[18:53] <Pici> m4v: right.
[18:53] <IdleOne> I would be fine with ubottu holding @
[18:53] <AlanBell> any downside to always being @
[18:53] <Pici> oblivious people ask it questions.
[18:53] <Tm_T> more private messages
[18:53] <Unit193> Questions may be directed directly more.
[18:53] <Pici> like we get with the floodbots.
[18:53] <TheLordOfTime> AlanBell:  not unless the bot starts spitting out random errors
[18:53] <TheLordOfTime> ;P
[18:54] <AlanBell> ubottu: do people talk to you already?
[18:54] <oCean> I don't think eir opping and deopping is too much noise for anyone
[18:54] <Tm_T> have to be afk now, sorry
[18:54] <m4v> AlanBell: well, maybe the channel's "temperature"?
[18:54] <IdleOne> wouldn't be any more noisy then eir
[18:54] <guntbert> m4v: she cannot get into an argument, so will not raise the temperature, I guess
[18:55] <DJones> I can't see a problem with ubottu being +o other than spam from users, most regulars know that ubottu is a bot and will normally advise users of that when they see somebody speaking directly to her
[18:55] <m4v> guntbert: I guess so :P
[18:56] <AlanBell> it seems fine to me, I can't imagine any security concerns about it, if someone can impersonate ubottu then they can cause a similar amount of nusiance either way
[18:56] <oCean> Getting into the details already :(
[18:56] <Pici> Why don't we see how feasible it is to make ubottu's current bantracker handling unbanning (and all that jazz), and then we can see how we want to handle the opping status.
[18:56] <AlanBell> yup
[18:56] <m4v> oh right, I'll get ops in #ubuntu through ubottu >D j/k
[18:57] <AlanBell> :O
[18:57] <IdleOne> I still don't know why you don't have ops in #u
[18:57] <AlanBell> so m4v, want to have a crack at implementing that? I am happy to help a bit and I am sure others will too
[18:57] <Pici> As am I.
[18:59] <m4v> AlanBell: I already started looking at it, it will be a hack, but meh.
[18:59] <Pici> Isn't everything ;)
[18:59] <DJones> If ubottu fell off freenode and somebody was alert enough to spot it, could they /nick to ubottu and gain ops in the 30 seconds before nick enforce took priority
[18:59] <Pici> no
[18:59] <m4v> DJones: nope, it would need to identify
[18:59] <IdleOne> not without knowing the nickserv pass
[18:59] <IdleOne> which is not HUNTER2
[18:59] <IdleOne> I tried.
[19:00] <topyli> yeah i changed it the other day
[19:00] <Pici> The enteries in the access list are account names, not nicks.
[19:00] <TheLordOfTime> lol
[19:00] <jussi> its not 123456789 either :P
[19:00] <Pici> jussi: thats the same password I have on my luggage :o
[19:00] <DJones> That sounds like it would restrict any 3rd party potential for abuse anyway
[19:01] <AlanBell> lets do some actions
[19:01] <topyli> ok, so eir stays and a mega ubottu hackfest is commensing. we can then retire eir tuesday by lunchtime? :)
[19:01] <oCean> (:
[19:02] <AlanBell> #action m4v Pici AlanBell to look into adding ban removal to ubottu cababilities
[19:02] <meetingology> ACTION: m4v Pici AlanBell to look into adding ban removal to ubottu cababilities
[19:02] <AlanBell> by tuesday lunchtime
[19:02] <topyli> :)
[19:02] <AlanBell> #agreed ubottu can hold +o in channels where ban expiry will be used
[19:03] <m4v> ok, you guys never took a look at bantracker code? welcome to the madhouse.
[19:03] <Pici> m4v: no, I've already lost my mind looking at it a few times before.
[19:03] <jussi> bantracker is a huge mess
[19:03] <topyli> by lunch is not realistic?
[19:03] <IdleOne> Why can't something new be used in its place?
[19:03] <Pici> It always has been, lets blame Seveas, hes not really heere.
[19:04] <Pici> IdleOne: because we can't seem to do that fast enough for anyone's liking.
[19:04] <jussi> topyli: give them till dinner :P
[19:04] <AlanBell> this is just adding ban removal, how hard can it be?
[19:04] <AlanBell> #topic Linking IRCC 'contact this team' in launchpad with osticket
[19:04] <TheLordOfTime> AlanBell:  on a timer, HARD
[19:04] <IdleOne> Pici: sucks to be them.
[19:04] <topyli> ok fine, volunteers and all
[19:04] <m4v> IdleOne: something new would take a lot of more time.
[19:04] <AlanBell> so who added this suggestion?
[19:04] <topyli> i did
[19:04] <oCean> What is the progress with the BT, can both bot and bt developments combined?
[19:05] <IdleOne> m4v: I understand that but it would be better than hacking stuff together and hope it doesn't explode
[19:05] <oCean> oh
[19:05] <oCean> nvm
[19:05] <Pici> I though the 'contact this team' thing just sent all the team members an email.
[19:05] <AlanBell> it does, but it seems we can direct it to a specific email address
[19:05] <TheLordOfTime> |^ that
[19:05] <topyli> this item is about avoiding mail via launchpad in our inboxen and into the ticket system
[19:05] <Pici> topyli: that sounds like a much better idea to me.
[19:05] <Pici> can I send all my own mail there too? ;)
[19:05] <jussi> I like this idea
[19:06] <jussi> Pici: no :P
[19:06] <Pici> darn.
[19:06] <AlanBell> A confirmation message has been sent to<EMAIL_ADDRESS>Follow the instructions in that message to confirm the new contact address for this team.
[19:06] <topyli> heh
[19:06] <AlanBell> hmm
[19:06] <AlanBell> ok, we have a new appeal to deal with ;)
[19:06] <topyli> denied!
[19:07] <Pici> topyli: you need to actually read the appeal message first ;)
[19:07] <jussi> Noooo!!! :(
[19:07] <AlanBell> ok, so we can finish that off later, but it seems like a good idea
[19:07] <AlanBell> #topic Any Other Business
[19:07] <Pici> cool cool fcool
[19:07] <topyli> yeah we can handle it ourselves
[19:08] <AlanBell> does anyone else have any other topics they would like to raise?
[19:09] <jussi> argh, I had somethign, but Ive forgotten
[19:09] <IdleOne> AlanBell: We have been having issues with certain persistent people trolling our less active channels that have hardly any access for the ops team. Would it be possible to create a spec ops team account and add this account to those smaller channels?
[19:09] <jussi> no doubt it will come to me after the meeting
[19:09] <Pici> IdleOne: Isn't that what the ircc account is for?
[19:10] <IdleOne> Pici: there are only 5 of you and they seem to know your schedules
[19:10] <topyli> jussi: it always does doesn't it :)
[19:10] <AlanBell> some don't have the ubuntuirccouncil account in the access list (-beginners is the example that springs to mind)
[19:10] <Pici> IdleOne: Is freenode-staff on those access lists?
[19:10] <IdleOne> AlanBell: which brings me to my next suggestion make it mandatory that IRCC be in all channel access list in the namespace
[19:11] <IdleOne> Pici: some but staff is not always available either
[19:11] <jussi> IdleOne: can you name specific time when this has happened?
[19:11] <Tm_T> back
[19:11] <AlanBell> right now it is suggested that we are in the access lists, and we can get staff assistance if we are not and need to be
[19:11] <TheLordOfTime> oh, i have one other thing of business to bring up, when you're done with this issue you're discussing.
[19:11] <TheLordOfTime> regarding access lists.
[19:12] <TheLordOfTime> (you just reminded me AlanBell)
[19:12] <IdleOne> jussi:19:00 to 21:00 my time
[19:12] <IdleOne> UTC-5
[19:12] <topyli> i would enjoy being sure without checking that ubuntuirccouncil is on the access list of any channel with an emergency
[19:13] <IdleOne> jussi: the times vary
[19:13] <TheLordOfTime> there are a few channels which have Ubuntu Members in their access lists.  Given that freenode has been starting a policy of secondary-cloaks being project.accountname rather than project.role.accountname, Ubuntu Members with newer secondary cloaks are not able to have access to channels which use the primary-cloak, and old-secondary-cloak access formats
[19:13] <TheLordOfTime> i.e. if we see the -irc access list, you see ubuntu/member/* and ubuntu.member.*
[19:14] <IdleOne> point is that channels are being harassed for far longer then should be allowed IMO
[19:14] <jussi> TheLordOfTime: ahh yes, those need fixing
[19:14] <Pici> I thought we updated those somewhere...
[19:14] <TheLordOfTime> jussi:  indeed, and preferably globally, there's a few other channels still having that
[19:14] <AlanBell> so what would be the correct mask?
[19:14] <TheLordOfTime> AlanBell:  for newer secondary cloak formats (as an example, mine),
[19:14] <Pici> ubuntu/* and ubuntu.* should cover everything
[19:14] <TheLordOfTime> ^ that
[19:15] <TheLordOfTime> or rather for the secondary format...
[19:15] <TheLordOfTime> */ubuntu.*
[19:15] <Pici> er, right
[19:16] <AlanBell> Pici: can you take that one, needs fixing in -meeting and -irc for starters
[19:16] <Pici> sure
[19:16] <AlanBell> I will only get the mask wrong
[19:16] <AlanBell> #action pici to review masks for Ubuntu Member access to channels
[19:16] <meetingology> ACTION: pici to review masks for Ubuntu Member access to channels
[19:17] <jussi> Id also like to have the discussion/decision about #ubuntu-discus
[19:17] <jussi> err
[19:17] <jussi> #ubuntu-discuss
[19:17] <jussi> #ubuntu-discus could be fun though :D
[19:17] <AlanBell> IdleOne: can we start by finding channels that lack ubuntuirccouncil and see if we can just fix them one by one?
[19:18] <AlanBell> maybe search with alis for #ubuntu-* having more than 10 people in the channel and check the access lists
[19:18] <IdleOne> AlanBell: sure but it won't help solve the problem. What i am suggesting is lightning the load for the IRCC
[19:19] <topyli> i'm still a bit sceptical about -discuss. we have topical channels and -ot
[19:19] <AlanBell> having a second account for op access across other channels is a bit of a big topic for the any other business section IdleOne :)
[19:19] <Tm_T> is
[19:20] <jussi> topyli: I think it is a very topical channel - its for discussion of specifically ubuntu related things that dont fit into #ubuntu's supportarea
[19:20] <Tm_T> agree with AlanBell, needs some preparation that discussion
[19:20] <IdleOne> AlanBell: indeed. I brought it up, you folks can shoot the idea around and make a decision. let us know at some point before December :)
[19:20] <AlanBell> I like the idea of #ubuntu-discuss as a place for on-topic non support discussions
[19:20] <IdleOne> isn't that what -ot is for?
[19:20] <AlanBell> and somewhere that Ubuntu marketing materials from LoCos and Canonical can direct people to
[19:20] <jussi> ubuntu in the news, improvements to ubuntu, etc etc
[19:20] <Tm_T> I like the idea of #ubuntu-offtopic as aplace for all non-support discussion that is suitable to our community spirit
[19:20] <IdleOne> on topic non support
[19:21] <topyli> jussi: that's -ot IMO
[19:21] <jussi> IdleOne: no, -ot is a break room type area, for just relaxing
[19:21] <AlanBell> so why is it called "off topic"?
[19:21] <IdleOne> jussi: but it can also be for cool ubuntu news and stuff
[19:21] <topyli> jussi: i disagree :)
[19:21] <Pici> I'd like to see some folks willing to staff -discuss that will actually be able to answer questions before we set it up
[19:21] <jussi> topyli: topic says so :P
[19:21] <Tm_T> AlanBell: good question, similar channels on other communities are called cafes etc
[19:21] <jussi> Pici: hrm?
[19:21] <topyli> AlanBell: historical reasons. it was created to move non-support away from #ubuntu back in 2005
[19:22] <Pici> i.e. not all us ops are knee deep in Ubuntu to know enough to respond to everything .
[19:22] <AlanBell> Tm_T: yes, a community cafe or something sounds about right
[19:22] <topyli> forums have a community cafe
[19:22] <topyli> so that would fit
[19:22] <Tm_T> that's pretty much what our -ot is
[19:22] <IdleOne> it sounds like another off topic channel
[19:22] <Pici> Isn't that what community-team is for?
[19:22]  * topyli is defensive of -ot :)
[19:23] <Tm_T> Pici: good point
[19:23] <jussi> Pici: nah, community team is for jono to organise calls :P
[19:23] <AlanBell> ok, so maybe community cafe is more what offtopic is
[19:23] <Pici> No.. thats what he uses it for, but its also where the community teams coordinate things
[19:23] <AlanBell> Canonical sent out a bunch of emails a while back relating to ubuntu phones or Ubuntu for Android asking people to "join the conversation in #ubuntu"
[19:23] <topyli> my sauna is getting cold :(
[19:24] <AlanBell> which I had to point out to them was not really what #ubuntu was all about
[19:24] <jussi> AlanBell: exactly the type of discussion we want in -discuss.
[19:24] <Tm_T> I wish -ot would be in shape for that kind of use
[19:25] <Pici> A lot of people use -ot as a place to relax, they don't want to have to deal with that sort of stuff in there.
[19:25] <topyli> ubuntu phones an ubuntu for android have nothing to do with the community afaik, and nobody knows nothing about them...
[19:25] <AlanBell> and no, I don't think #ubuntu-offtopic is an appropriate place to direct people to, partly because the name is weird for that kind of thing, and partly because the conversations are a bit random at times
[19:25] <jussi> I really think that -ot isnt for that, its not somewhere we send people for that type of discussion. its not that it cant happen in -ot, but that its nice to have a dedicates area
[19:25] <AlanBell> topyli: not entirely true, but anyhow, this is a general point about marketing Ubuntu
[19:25] <Tm_T> topyli: ...so best option is no channel in that case
[19:26] <Pici> So, instead of going around in circles.... do we want to trial this?
[19:26] <topyli> well, canonical can set one up
[19:26] <Pici> or?
[19:26] <AlanBell> sabdfl's response was that perhaps they should direct people to askubuntu.com and not IRC at all
[19:26] <topyli> Tm_T: iirc #ubuntuone is working fine
[19:26] <jussi> Pici: I would like to trial it
[19:26] <AlanBell> I would like to trial it
[19:26] <jussi> AlanBell: you guys want to have a vote? ;)
[19:26] <Pici> AlanBell: unfortunately, sabdfl has a bit of a history of not exactly getting what we do.
[19:26] <Tm_T> topyli: yup, because there's canonical folks answering
[19:27] <topyli> we can trial it, see if people will join when encouraged, and what becomes of it
[19:27] <topyli> (-discuss i mean)
[19:27] <Pici> Worst thing that happens is that its a bust and we end up forwarding it to somewhere else.
[19:27] <topyli> yep
[19:27] <AlanBell> ok, lets have a little vote on this
[19:28] <Tm_T> true, but I'm bit worried of the idea that Canonical points people to us and we have to clean up the mess, to put it bluntly
[19:28] <jussi> ops should also direct people who have that kind of discussion in #ubuntu to there as well
[19:28] <AlanBell> #vote set up a #ubuntu-discuss channel for high quality on-topic non-support discussions of Ubuntu as a trial to be reviewed at a later date
[19:28] <meetingology> Please vote on: set up a #ubuntu-discuss channel for high quality on-topic non-support discussions of Ubuntu as a trial to be reviewed at a later date
[19:28] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[19:28] <DJones> What area's of the community would you staff it from? core ops, members, canonical employee's, community-team etc?
[19:28] <topyli> +1
[19:28] <meetingology> +1 received from topyli
[19:28] <AlanBell> #voters AlanBell Pici topyli Tm_T
[19:28] <meetingology> Current voters: AlanBell Pici Tm_T topyli
[19:28] <jussi> DJones: all of the above ?:D
[19:28] <AlanBell> +1
[19:28] <Pici> +1
[19:28] <meetingology> +1 received from AlanBell
[19:28] <meetingology> +1 received from Pici
[19:29] <DJones> jussi: Agreed, it would have to be a mixture
[19:29] <Tm_T> +0
[19:29] <meetingology> +0 received from Tm_T
[19:29] <topyli> i suspect jussi would like to set it up :)
[19:29] <AlanBell> #endvote
[19:29] <meetingology> Voting ended on: set up a #ubuntu-discuss channel for high quality on-topic non-support discussions of Ubuntu as a trial to be reviewed at a later date
[19:29] <meetingology> Votes for:3 Votes against:0 Abstentions:1
[19:29] <meetingology> Motion carried
[19:29] <Pici> I can think of a few folks that would at least be willing to idle there and answer questions
[19:30] <IdleOne> I'm still not sure about the idea but I'll be idle in there and happy o help out
[19:30] <AlanBell> great
[19:30] <topyli> would be nice to lure some canonical staff there
[19:30] <AlanBell> ok, any more stuff?
[19:30] <AlanBell> five
[19:30] <AlanBell> four
[19:30] <AlanBell> three
[19:30] <AlanBell> two
[19:30] <Pici> Is someone willing to send out a mail to the list so that the rest of the folks not present today will know about it?
[19:30] <Pici> or... will the meeting notes be enoughj
[19:30] <AlanBell> yeah, I will do that
[19:30] <AlanBell> one
[19:30] <Pici> AlanBell: great, thaks.
[19:30] <AlanBell> #endmeeting
[19:30] <meetingology> Meeting ended Sun Jun 24 19:30:38 2012 UTC.
[19:30] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-06-24-17.59.moin.txt
[19:30] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-06-24-17.59.html
[19:30] <Pici> I need new fingers today.
[19:30] <AlanBell> thanks everyone
[19:30] <topyli> i suppose the meeting minutes will take care of it
[19:30] <IdleOne> Thank you.
[19:30] <topyli> thanks all, i'm off to sauna :)
[19:31] <Tm_T> yay, I voted on IRCC meeting, did I win something?
[19:31] <IdleOne> yes, responsibility
[19:31] <topyli> Tm_T: a trophy in the ubuntu accomplishments game!
[19:31] <Tm_T> topyli: ooooooo shiny!
[19:31] <AlanBell> IdleOne: does that come with great power?
[19:31] <IdleOne> it does peter
[19:31] <IdleOne> it does.
[19:31] <Pici> heh
[19:31] <topyli> haha
[19:32] <Tm_T> IdleOne: I would have expected that even without IRCC position
[19:32]  * AlanBell wonders off to get cake
[20:07] <Seveas> Pici, ?
[20:09] <IdleOne> Seveas: you have been blamed during a meeting and were given ample time to respond. meeting is now over and your opinion no longer matters. Thank you for playing.
[20:09]  * IdleOne hugs Seveas :)
[20:15]  * Seveas slaps IdleOne
[20:16] <Seveas> what did I get the blame for this time?
[20:16] <IdleOne> BT
[20:17] <Seveas> British Telecom?
[20:17] <IdleOne> bad taste
[20:17] <IdleOne> lol
[20:17] <IdleOne> the ban Tracker
[20:17] <Seveas> is that still in use?
[20:17] <IdleOne> heh, yeah
[20:17] <Seveas> it was falling over years ago already
[20:17] <Seveas> surprised it hasn't yet
[20:17] <IdleOne> it has been given a cane but is limping badly now
[20:17] <Seveas> you've had years to replace it, blame the lazy buggers who didn't
[20:18] <Seveas> or the muppets who made me quit :-)
[20:18] <IdleOne> name calling is not going to help us get a better ban tracker
[20:19] <Seveas> nope, someone will need to write one
[20:19] <Seveas> and it ain't gonna be Seveas
[20:19] <IdleOne> if interested and have the spare time talk to AlanBell and Pici about helping them out with this, also m4v
[20:19] <Seveas> nope, not even a little bit
[20:19] <IdleOne> :(
[20:20] <IdleOne> Just so you know I do appreciate that you did write it in the first place.