[00:02] <BarkingFish> DarkriftX: I'm not sure if this is the only thing it does, but system connection prioritizes the connections you have set up.  If you have more than one connection set up to connect automatically, marking your preferred one as "system connection" will cause that one to always be selected as the primary connection.
[00:03] <DarkriftX> Ok
[00:03] <BarkingFish> I do it with Wifi here - I have 8 wifi connections out of here, all marked "connect automatically" - but I have one preferred one marked system connection - which always gets picked and connected to when I start KDE
[00:04] <DarkriftX> Ok. My router has a 2.4 and a 5ghz setting so it has 2 network id's
[00:04] <DarkriftX> I set the 5ghz one to system and the other just to auto
[00:04] <DarkriftX> either should work at any time, so it prob wont matter
[00:06] <DarkriftX> I do think its odd that the 5Ghz shows lower signal str than the 2.4 considering there are 2.4 networks all over my neighborhood
[00:49] <skierpage> Printing to PDF using CUPS recently broke for me, I'm not sure why.
[00:50] <skierpage> Status "Backend /usr/lib/cups/backend/cups-pdf does not exist".  Indeed, no such file. It's worked for so long I'm not sure what I did to set it up.
[01:07]  * rar is back
[01:53] <DarkriftX> does anyone know what the value for KDE4_KDEUI_LIBS should be?
[01:53] <DarkriftX> also KDE4_INCLUDES
[02:03] <skierpage> Hmm, `aptitude show cups-pdf` says it's not installed, though there's no record of its removal in /var/logs/dpkg.log*
[02:04] <DarkriftX> is there record of its install?
[02:08] <skierpage> I take it back, 2011-10-14 has "status installed cups-pdf 2.5.1-7", immediately followed by "remove cups-pdf 2.5.1-7 <none>", maybe it was recommended but not any more. Anyway, a reinstall fixed it.
[02:11] <skierpage> A lot of apps can now directly save/export/print to file as PDF, so cups-pdf is less useful.
[02:11] <skierpage> cheerio
[02:52] <saravana> hi guys
[02:52] <badboyyyyyy> hi
[02:56] <saravana> i downloaded hunting unlimited 2010 game and then mounted it with furius iso then i installed it but when i open the game it shows an error message like "there is no program configured to open tis kind of file "
[02:57] <saravana> what to do now
[03:07] <Xploitatious> hey im currently on kubuntu 10.04 and was wondering how can i upgrade from KDE 4.5.3 to 4.7
[03:10] <DarkriftX> does anyone know what the value for KDE4_KDEUI_LIBS should be?
[03:24] <Xploitatious> fine
[04:35] <Ahmed_> i want to install the official nvidia driver but i cannot unload the nouveu driver
[04:36] <Ahmed_> i want to log in runlevel 3
[04:56] <Tech936> hi can some one help me
[04:58] <SunTsu> Tpain: yes, of course, my first help would be pointing out that changing your nick right after asking a question is a bad idea
[04:59] <Tpain> woops sorry didnt notice it gave me that user by accident
[05:00] <SunTsu> and for the rest: state your business, whithout nobody is able to help
[05:06] <OerHeks> oh ..
[07:13] <caesar_> nube question but how do i cd in terminal
[07:15] <caesar_> i need to cd to root/media/HP TOUCHPAD/cminstall
[07:19] <qbit> depends on permissions and who you arr and where you're trying to cd to
[07:19] <qbit> but I bet you're trying to cd /media/HP TOUCHPAD/cminstall
[07:21] <qbit> if you are a user trying to cd into /root you'll more than likely be denied permission
[07:22] <caesar_> just got a wrong bash error
[07:22] <caesar_> something or another.. sorry i'm new to term and cli all together
[07:23] <qbit> cd / changes to the beginning of your file system
[07:23] <qbit> cd /root changes into the home directory for the root user, which will be denied if you are not the root user
[07:24] <qbit> if you're trying to find something mounted under /media you need the slash in front like /media
[07:24] <caesar_> bash: cd: media/HP: No such file or directory
[07:24] <caesar_> linux doesn't like the space
[07:24] <qbit> cd /media
[07:25] <qbit> try to escape the space with cd /media/HP\ Touchpad
[07:25] <caesar_> i'm already in media
[07:25] <qbit> then see if cd HP\ TOUCHPAD works
[07:26] <caesar_> bash: cd: /media/HP Touchpad/cminstall: No such file or directory
[07:27] <qbit> cd: /media/HP\ Touchpad/cminstall    <- look/see the "\" character after HP
[07:28] <qbit> ohm and drop the ":" after cd while you're at it
[07:29] <qbit> as in cd /media/HP\ Touchpad/cminstall
[07:29] <qbit> used to be how you wouyld escape a space in regular Unix, not sure if it stil applies to Linux
[07:31] <qbit> bummer, just tried it out and it don't work
[07:31] <qbit> pwd
[07:31] <qbit> oops, wrong windows...
[07:32] <qbit> oh it does work after all, I tried the wrong thing  :-)
[07:33] <qbit> cd My\ Music put me in the My Music directory
[07:35] <SunTsu> caesar_: command line arguments are delimited by whitespace, so you need to tell the shell that that space is part of the name, which is called "escaping". You can add a Backslash ("\") before that space or put double or single quotes around that name
[07:36] <SunTsu> else the shell is not aware that you are trying to supply a single command line argument with a space in it but takes that as two separate arguments
[07:42] <caesar_> i think the issue is bigger than the code.. i'm just trying to install cm7 on my HP TOUCHPAD but the touchpad isn't showing in the explorer
[07:42] <caesar_> and it's in usb mode
[07:42] <caesar_> so i dunno what the issue is
[07:43] <qbit> if it's supposed to be under /media I suspect it is supposed to be mounted as a file system? then the mount command would list it
[07:44] <qbit> if it is supposed to show up as a device that is different
[07:48] <caesar_> which mount command?
[07:48] <qbit> just mount all by itself will display a list of all mounted file systems
[07:50] <qbit> for example, I just stuck a flash drive in my box and mount returns this: /dev/sdc1 on /media/usb0 type vfat  (options removed from cut/paste)
[07:51] <qbit> if your touchpad isn't showing as a mounted file system you should look under /dev to see if it is being recognized there as a device
[07:51] <caesar_> /dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)
[07:51] <caesar_> proc on /proc type proc (rw,noexec,nosuid,nodev)
[07:51] <caesar_> sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
[07:51] <caesar_> fusectl on /sys/fs/fuse/connections type fusectl (rw)
[07:51] <caesar_> none on /sys/kernel/debug type debugfs (rw)
[07:51] <caesar_> none on /sys/kernel/security type securityfs (rw)
[07:51] <caesar_> udev on /dev type devtmpfs (rw,mode=0755)
[07:51] <caesar_> devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
[07:51] <caesar_> tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
[07:51] <caesar_> none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
[07:51] <caesar_> none on /run/shm type tmpfs (rw,nosuid,nodev)
[07:52] <GoTh> äîáðûé äåíü âñåì
[07:53] <caesar_> lol
[07:53] <GoTh> Êòî ìîæåò ïîäñêàçàòü ïóòè ðåøåíèÿ ïðîáëåì ñ óñòàíîâêîé, êîòîðûå âîçíèêàþò èç-çà íåâîçìîæíîñòè óñòàíîâêè grub?
[07:53] <caesar_> that's what i get when i type mount
[07:54] <qbit> so no mounted file system to be seen, and with no mounted file system you cannot cd to some place that does not exist
[07:55] <qbit> I'm running short on ideas, but my guess here is it may not have a device node under /dev either
[07:55] <qbit> if kernel support exists, or a module can autoload at boot you might get a device node created at boot
[07:56] <qbit> you could also do lsmod and look to see if a module is loading to support the touchpad
[07:57] <qbit> but I do not know enough about the subject either  :-)  just a few guesses on my part
[08:00] <qbit> I also thought that the Touchpad drivers were part of Xorg
[08:00] <qbit> maybe you're missing those
[08:04] <caesar_> qbit: maybe yea
[08:04] <caesar_> let me show you what i'm looking at
[08:04] <caesar_> http://www.youtube.com/watch?v=q2zWiftfwIk
[08:19] <caesar_> qbit: the program i use to communicate with the HP Touchpad is novacom.. when i type novacom in terminal this is what i come up with
[08:19] <caesar_> caesar@cerebro:~$ novacom
[08:19] <caesar_> version: novacom-17
[08:19] <caesar_> usage: novacom [-a address] [-p port] [-t] [-l] [-d device] [-c cmd] [-r password] [-w] <command>
[08:19] <caesar_> novacom [-V]
[08:19] <caesar_> novacom [-a address] [-p port] -P[ [-f <localport:remoteport,...>] ]
[08:19] <caesar_> options:
[08:19] <caesar_>         -a address: ip address of the novacomd server, default is 'localhost'
[08:19] <caesar_>         -p port: port of the novacomd server's device list port, default is 6968
[08:19] <caesar_>         -t: go into terminal mode, for interactive use
[08:19] <caesar_>         -s: pass signals to remote process
[08:19] <caesar_>         -l: list devices and then exit
[08:19] <caesar_>         -r: device password
[08:19] <caesar_>         -c: service command [login, add, remove, logout]
[08:19] <caesar_>                   login:  opens new session
[08:19] <caesar_>                   add:    adds device token to host
[08:19] <caesar_>                   remove: remove device token from host
[08:19] <caesar_>                   logout: closes active session
[08:19] <caesar_>         -d device: connect to specific device instead of first.
[08:19] <caesar_>                  might be <nduid>, <connection type>, <device type>
[08:20] <caesar_>         -w: wait for device to show up before running command
[08:20] <caesar_>         -V: version information
[08:20] <caesar_>         -P: Port Forwarding Enabled
[08:20] <caesar_>         -f: ports to forward
[08:20] <caesar_> maybe that will make some sense of it
[08:20] <caesar_> err hopefully
[08:29] <DaemonFC> so kdebase is now a transitional package in KDE 4.7.4 in Kubuntu because it has been split up finally to use the names from upstream
[08:29] <DaemonFC> but consequently the i386 version is dropped because you don't multiarch empty packages
[08:30] <DaemonFC> but something from Wine claims it needs the i386 version
[08:30] <DaemonFC> and the empty package is a "dependency" of a bunch of Kubuntu specific stuff
[08:30] <DaemonFC> *sigh*
[08:30] <DaemonFC> so my choices appear to be 1. Back out KDE 4.7.4 so I can install wine1.3:i386
[08:31] <DaemonFC> or go without Wine, because the x86-64 version which does install, likes to crash X
[08:31] <DaemonFC> what a mess
[08:31] <DaemonFC> I've never seen dependency hell as bad as on Ubuntu before
[09:07] <szal> caesar_: next time use a pastebin please
[09:08] <caesar_> szal: sure thing
[09:09] <szal> DaemonFC: instead of complaining at this un-Christian hour (;)), file a bug
[09:10] <szal> DaemonFC: or wait for yofel to appear (likely when it's evening in Europe, i.e. in 10 hours or later) and poke him directly
[09:19] <cedar> Nobody's here to speak.
[09:19] <Peace-> ?
[09:20] <cedar> I don't know what is IRC.
[09:20] <Peace-> a chat
[09:20] <Peace-> where people help people
[09:20] <cedar> What's the different between this and others?
[09:21] <szal> define 'others'
[09:21] <Peace-> here you can speak only of kubuntu
[09:21] <Graf_Westerholt> cedar?
[09:21] <cedar> ?
[09:21] <Graf_Westerholt> IRC is the best chat. :)
[09:22] <szal> this is Kubuntu support; if you want non-specific chatrooms, you might want to visit #kubuntu-offtopic or #ubuntu-offtopic or #defocus
[09:22] <szal> or all of them; you can connect to multiple chatrooms at once
[09:23] <Graf_Westerholt> cedar http://en.wikipedia.org/wiki/Internet_Relay_Chat
[10:07] <DaemonFC> Does anyone else get a bunch of dependency problems when installing Wine in 11.10?
[10:07] <DaemonFC> the more I look, the more I think they've declared that it depends on packages that don't exist
[10:08] <DaemonFC> apt error messages aren't real helpful
[10:08] <DaemonFC> if a package exists it just says it won't be installed, not why
[10:08] <DaemonFC> earlier versions of WINE just depended on ia32-libs, but now the wine packages try to install Wine64 which crashes the X server when I go to play any games
[10:09] <DaemonFC> and the i386 version is not installable due to depending on packages that don't exist
[10:09] <DaemonFC> ok, this sucks *sigh*
[10:30] <rodstvenik> ygghjhj
[12:55] <srinivasan> hi
[13:20] <tonymc> hi all
[13:20] <tonymc> suddenly all my ntfs partitions has become read only
[13:21] <tonymc> i checked them with chkdsk on windows and they're clean
[13:21] <tonymc> i didn't edit fstab and it was working yesterday perfectly
[13:21] <tonymc> what could have possibly caused this?
[13:21] <tonymc> moreover, i can't mount read-write even ntfs partitions on external HDD
[13:22] <tonymc> the only recent update i remember that could have caused this is the 3.0.15 kernel
[13:29] <tonymc> ah, sorry, never mind, somehow ntfsprogs was installed triggering mtfs-3g removal
[14:16] <BluesKaj> Hey all
[14:17] <prince> hi
[14:56] <MatusT> I made a fresh install of Kubuntu 11.10, everything went fine except Kubuntu won't boot, i installed it from LiveUSB and liveUSB runs with no problems in live mode
[15:00] <pr_> hi
[15:00] <pr_> I need some help...
[15:01] <pr_> my volume control, network manager and notification widget were gone from my bar, without i change anything, any idea of how to recover it?
[15:03] <Peace-> MatusT: try to boot in recovery kernel
[15:03] <Peace-> pr_: right button on panel add default panel
[15:08] <Zippa> hi
[15:08] <Zippa> I am from Poland
[15:09] <MatusT> Peace-: well, booting to recovery mode doesn't help
[15:09] <Peace-> MatusT: well what  did you do ?
[15:10] <Peace-> have you tried to login via shell?
[15:10] <Zippa> Kubuntu is great
[15:10] <Peace-> MatusT: and then startx?
[15:10] <MatusT> Peace: nothing, i am unable to do anything
[15:10] <MatusT> it just shows some errors
[15:10] <Peace-> mm
[15:10] <MatusT> that i dont have nforce2 chip and EISA cannot allocate resource for mainboard
[15:10] <Peace-> mm
[15:11] <Peace-> MatusT: ave you a shot?
[15:11] <Peace-> something i can read?
[15:11] <MatusT> the last thing it wrote is setting time
[15:11] <Peace-> are yo on linux now?
[15:11] <Peace-> in the live cd?
[15:11] <MatusT> nope, using Windows 7
[15:11] <MatusT> i am always dual booting
[15:12] <MatusT> and Kubuntu 11.04 worked just fine
[15:12] <Peace-> MatusT: ok so ... reboot in live cd , then go  with the browser on webirc and join the kubuntu channel  http://webchat.freenode.net/
[15:12] <MatusT> ok and then?
[15:13] <Peace-> MatusT: do you know lcpci ?
[15:13] <Peace-> you should make some shot of the error
[15:13] <Peace-> then live cd
[15:13] <MatusT> i have a shot of error
[15:13] <Peace-> post me
[15:13] <Peace-> it
[15:13] <MatusT> but actually its not the error, it just writes some things and stops at the setting time
[15:13] <Peace-> wihtout any information i can't help
[15:13] <Peace-> i guess is a kernel bug
[15:13] <MatusT> ok, wait a sec
[15:14] <Peace-> but after that i have no idea
[15:15] <MatusT> Peace-: http://ge.tt/8as3NLB/v/0
[15:18] <Peace-> MatusT: reading
[15:20] <MatusT> that's all i have
[15:21] <Peace-> MatusT: mm  have you tried to press CRTL C
[15:21] <Peace-> ?
[15:21] <Peace-> or S
[15:21] <MatusT> i could't press anything
[15:21] <Peace-> i know it seems
[15:21] <Peace-> you can't press anything
[15:22] <Peace-> MatusT: btw try it or S
[15:22] <Peace-> or crtl c
[15:22] <MatusT> ok...
[15:26] <MatusT> Peace-: no, i really can't press anything on keyboard
[15:26] <Peace-> ok
[15:27] <Peace-> so it's blocked
[15:27] <MatusT> yep and now i am on LiveUSB
[15:27] <Peace-> perfect
[15:27] <Peace-> MatusT: terminal
[15:27] <MatusT> interesting thing is when LiveUSB boots it writes same things to console as recovery kernel
[15:27] <Peace-> lspci | grep -i Vga
[15:27] <MatusT> but it continues after time, while recovery just stops and do nothing
[15:28] <Peace-> MatusT: maybe could be an acpi settings
[15:28] <Peace-> MatusT: sometimes acpi stuff just breaks balls
[15:28] <MatusT> http://paste.kde.org/175346/
[15:30] <Peace-> MatusT: wait i am reading searchin
[15:33] <Peace-> MatusT: damn i guess i kernel bug
[15:33] <MatusT> yep it probably is
[15:33] <MatusT> because previous Kubuntu versions worked just fine
[15:33] <MatusT> i guess i will have to wait for a new kernel
[15:33] <Peace-> MatusT: you can choose another kenel ?
[15:33] <Peace-> i mean another version
[15:34] <Peace-> it's seem it's the  3.0 that has this problem
[15:34] <MatusT> ah
[15:34] <MatusT> i thought its some problem only in the minor and when new version is released i will just install kubuntu with checked option for updates...
[15:35] <Peace-> MatusT: http://ubuntuforums.org/showthread.php?t=1863143
[15:35] <Peace-> MatusT: maybe tere is a solution
[15:36] <Peace-> MatusT: you have to read that topic
[15:36] <MatusT> *reading*
[16:58] <aanti> can someone help me with ext4 and a ssd (mount-optiions in fstab, performance related)...?
[18:40] <johan_> http://pastebin.com/5gH6E3hb i have an akonadiserver but i do not know how to solve this :|
[18:40] <johan_> email is not accesible
[18:41] <johan_> i hav ean mysql and working
[18:53] <caesar_> will the virtualbox in the software center support usb devices?
[18:54] <caesar_> does*
[18:57] <civerdoris2> hola"" que tal
[18:57] <civerdoris2> mmm necesito ayuda con mi sistema  talvez me puedan ayudar
[18:58] <BluesKaj> caesar_, run lsusb with your device plugged in.
[18:59] <caesar_> BluesKaj: while the vbox is running?
[18:59] <BluesKaj> yes
[18:59] <caesar_> k
[18:59] <BluesKaj> !es |civerdoris2
 gracias
[19:01] <BluesKaj> civerdoris2, de nada
[20:15] <horseatingweeds> Is there a guide for KDE desktop? I've been messing around with Kubuntu, but I'd rather read something about how to properly use this desktop.
[20:15] <DarkriftX> I dont think so
[20:15] <DarkriftX> there are tons of tutorials for little things all over
[20:16] <BluesKaj> horseatingweeds, best to install kubuntu-desktop
[20:16] <DarkriftX> but ive never really seen a guide to general use. I would ask your questions here and explore a little to get an idea of what is where
[20:16] <horseatingweeds> Yeah, I've seen some sparce little things.
[20:16] <DarkriftX> except for finding config pages, most things in kde are pretty easy to figure out
[20:18] <horseatingweeds> BluesKaj: What is kubuntu-desktop?
[20:18] <horseatingweeds> Is that different from kde?
[20:19] <BluesKaj> horseatingweeds, yes , it's the metapckage that brings in the default apps they woulkd be on the official kubuntu install
[20:19] <BluesKaj> !kubuntu-desktop
[20:20] <BluesKaj> kubuntu isn't just ubuntu with kde , horseatingweeds
[20:21] <Resistance> its got a lot of KDE-based applications too
[20:21] <horseatingweeds> I think I have the oficial Kubuntu installed.
[20:21] <BluesKaj> http://www.kubuntu.org/feature-tour
[20:21] <BluesKaj> horseatingweeds, ^
[20:22] <horseatingweeds> It certainly has a different pack of software. Dolphin instead of Nautilus, gksudo not installed.
[20:22] <Resistance> its kdesudo
[20:22] <Resistance> or kdesu
[20:22] <Resistance> (KDE sudo, instead of GNOME sudo)
[20:22] <horseatingweeds> ok
[20:22] <BluesKaj> gtk is replaced by kde apps
[20:23] <Resistance> yep
[20:23] <mateusz> Hi all, have a question : how to set different wallpapers on each desktop in kubuntu 11.10, I use compiz and cube
[20:24] <DarkriftX> lol, that was a pain in the ass to do a year ago.
[20:25] <horseatingweeds> I decided to try out kubuntu because I find Ubuntu's Unity a pain.
[20:27] <mateusz> can anyone help me?
[20:27] <Resistance> !ask | mateusz
[20:27] <Resistance> :P
[20:27] <DarkriftX> mateusz: id ask in #compiz (I think thats it)
[20:27] <DarkriftX> Resistance: he already asked his question
[20:28] <Resistance> ah there's the question
[20:28] <Resistance> DarkriftX:  i'm getting packet loss
[20:28] <DarkriftX> just has not received an answer
[20:28] <Resistance> LOTS of it
[20:28] <Resistance> DarkriftX:  since internet out here just came back online today :P
[20:28] <Resistance> DarkriftX:  there's laggy hubs or something, so everyone is getting hit with some packet loss
[20:28] <Resistance> (therefore i'm missing entire chunks of IRC text :/)
[20:29] <DarkriftX> odd, never seen irc behave like that unless you disconnected
[20:29] <BluesKaj> mateusz, not sure but you can check in your compiz , and system settings>workspace behaviour , and how they interact
[20:30] <BluesKaj> bbl..
[20:30] <mateusz> oh man
[20:30] <mateusz> you are great
[20:30] <mateusz> thank you
[20:33] <Resistance> DarkriftX:  well i'm in via a boucner
[20:33] <Resistance> so the data isnt getting from the bouncer to me completely
[20:33] <Resistance> ;P
[20:33] <Resistance> but is more than likely getting from irc to bouncer
[20:34] <DarkriftX> ahh, I see
[20:40] <dbc254> dunno how to word this, so can't exactly do a "search" myself. When I get a email from a list I'm on, I used to be able to click on the title of a msg and goto that specific one in the list. Now I can't . How do I regain that function?
[20:41] <horseatingweeds> When you first start Kubuntu, what is this translucent box that appears?
[20:43] <Snowhog> horseatingweeds: If you are refering to the 'folder' you see on the desktop, that's the Folder View widget.
[20:45] <horseatingweeds> Snowhog: So you stick often used folders in there or somehting?
[20:47] <Snowhog> horseatingweeds: You can configure it to show what you want. If widgets are 'unlocked' then if you mouse over this folder, you will see a pop-out 'tool bar' that has a wrench icon. Click on the wrench to get to the configuration settings.
[20:57] <randomatix> Hi, just upgraded to 11.10.   Many apps are now using high CPU, and causing /usr/bin/X to also consume close to 100% of a core.  The common factor seems to be GTK.  Any ideas?
[20:58] <rafa_28> I don't know,but maybe
[21:00] <rafa_28> have you upgraded from 11.04?
[21:01] <randomatix> Yes.  Just did the dist-upgrade.
[21:06] <randomatix> strace shows that they tend to be obsessed with reads/writes on a socket, returning EAGAIN
[21:06] <rafa_28> I don't like upgrade from older version because the OS run slowly or there are options that don't work
[21:08] <BluesKaj> randomatix, are you sure you upgraded , dist-upgrade just upgrades kernel packages , not the OS
[21:08] <rafa_28> are you sure??
[21:09] <rafa_28> I don't know. How I can do full-upgrade??
[21:10] <randomatix> BluesKaj: yes, it was a dist-upgrade through the GTK update-manager.  Plenty of non-kernel things included, Then I manually addressed the PPAs that got disabled.  Was using xorg-edgers, backed off to the more stable one.
[21:10] <BluesKaj> to upgrade from 11.04 to 11.10 , sudo do-release-upgrade
[21:11] <randomatix> I used the option in the gtk update-manager
[21:11] <randomatix> it did the whole system
[21:11] <BluesKaj> why gtk update manager this is kubuntu/kde
[21:12] <randomatix> I have some experience with dist-upgrades.  This install started out as Gnome back around Breezy or Dapper.
[21:13] <BluesKaj> rafa_28, sudo apt-get update && sudo apt-get upgrade , then sudo do-release-upgrade
[21:13] <randomatix> it's not a pure Kubuntu system.   finally got fed up with the Gnome instability and ditched it.
[21:15] <BluesKaj> randomatix, wow no clean installs since breezy , that's very unusual
[21:15] <randomatix> it was probably 2006, maybe early 2007
[21:16] <BluesKaj> randomatix, the do-release-upgrade command auto-disables any ppas in /etc/apt/sources.list.d
[21:17] <rafa_28> BluesKaj, Make a new install, is it the best ?
[21:17] <randomatix> BluesKaj: yes, as did the tool I used.  I suspect the methods are comparable.
[21:18] <BluesKaj> rafa_28, not necessarily , I've been doing upgrades for the last 3 new releases . without much trouble
[21:18] <randomatix> rafa_28: New install is not an option here.  Eventually that will happen, but not now.
[21:19] <randomatix> (and one can learn a lot more fixing upgrade problems than just reinstalling like geek squad would :)
[21:22] <randomatix> I should mention that I'm using the Intel video drivers, and those have had some problems.
[21:47] <randomatix> Some progress: seems like the problem might be with oxygen-molecule.  Changing to another widget style works a lot better.
[21:57] <randomatix> anyone else noticing high CPU loads with oxygen-molecule?
[22:02] <vit> hola
[22:05] <vit_> homosexuales x aki
[23:12] <divyaraj> logic
[23:18] <znt>  hello, how can i disable the settings bar of "folder view widget" ? i dont want to see it when i m on the widget.
[23:45] <DoctorPepper> hi guys !!!
[23:46] <Tech-1> ǝʞoɹq ʇsnɾ pɹɐɔ sɔıɥdɐɹƃ ʎɯ ʞuıɥʇ ı
[23:50] <DoctorPepper> can anyone help me please ,  i have a issue with sound not work for only one user  when using the gstreammer backend for phonon
[23:59] <EvilResistance> Tech-1 mind using normal characters :P


[07:49] <rogpeppe> davecheney: ping
[07:49] <rogpeppe> mornin' all!
[08:19] <rogpeppe> wallyworld_: you around?
[10:18] <aram> hello.
[10:31] <rogpeppe> aram, dimitern: hiya
[10:32] <dimitern> rogpeppe, aram: morning :)
[10:32] <rogpeppe> dimitern: openstack tests are broken in trunk BTW, if you don't have OS_TENANT_NAME set
[10:32] <dimitern> rogpeppe: hmm
[10:32] <dimitern> rogpeppe: that's now or the branch I proposed yesterday?
[10:33] <rogpeppe> dimitern: currently
[10:34] <rogpeppe> dimitern: it would also be nice if the goose "required environment variable" error message printed the name of the required environment variable rather than the struct field name...
[10:34] <rogpeppe> "required environment variable not set for credentials attribute: TenantName" makes it look as if the required env var is $TenantName
[10:35] <dimitern> rogpeppe: tell me about it :) I did it like that originally, but.. anyway I'll take a look
[10:51] <dimitern> rogpeppe: fixed https://codereview.appspot.com/7196043 - this is trivial, if you think it's ok, I'll land it now
[10:51] <jam> mgz: poke
[10:52] <rogpeppe> dimitern: LGTM. agreed trivial.
[10:52] <dimitern> rogpeppe: 10x, submitting then
[10:55] <dimitern> rogpeppe: how about looking at my bootstrap branch - https://codereview.appspot.com/7181046/
[10:55] <rogpeppe> dimitern: will do
[10:56] <mgz> jam: hey
[10:56] <jam> mgz: I had some questions about how to setup tarmac, and thought you might be good to bounce off for feedback.
[10:56] <jam> I think I have it up and running, and a small patch to handle some stuff I didn't realize.
[10:56] <jam> However, what branch do we want it to actually manage?
[10:57] <jam> (do we want to add it to ~gophers, and give it write access there, do we want a different team, a branch only accessble by goose-bot, ... ?)
[10:59] <jam> (I guess the next direct step is to add support for running juju-core tests before landing trunk code, but I'd like to answer the above first)
[10:59] <mgz> hm, the bzr-pqm way is to have the branch owned by the bot
[10:59] <jam> mgz: right
[10:59] <jam> the major downside is the "manual escape hatch"
[10:59] <mgz> but being able to get around it and commit anyway will probably be useful for now
[10:59] <jam> especially because of wanting to be able to land goose code and juju-core code concurrently
[11:00] <mgz> yup.
[11:01] <mgz> so, maybe we want a new team that the bot can be a member of to own the goose code
[11:04] <jam> I tend to be cautious, so giving it full '~gophers' access seemed a bit much, but it is also a fair amount of bookkeeping just to do goose.
[11:04] <mgz> yeah.
[11:05] <dimitern> jam: but isn't that like the other go projects? all owned by ~gophers?
[11:07] <jam> dimitern: sure, and all of us have the ability to push whatever we want to them. I'm hesitant to allow a bot the same access.
[11:08] <mgz> it's easy enough to make ~gophers a member of the group that owns goose trunk, we just don't want the bot to have too much power :)
[11:08] <jam> dimitern: it also stems from a group that doesn't have a habit of using a bot to control their trunks, vs the launchpad group using that method for a long time.
[11:08] <dimitern> jam: wouldn't it need to merge and push changes?
[11:08] <jam> dimitern: goose bot needs to be able to write to goose's trunk
[11:08] <jam> I'm not sure that it needs rights to everything else owned by ~gophers
[11:08] <jam> (juju-core, goamz, etc, etc.)
[11:09] <dimitern> you don't trust the bot? c'mon :D
[11:09] <dimitern> it's a nice guy
[11:09] <jam> dimitern: the inverse is actually just as important (to me). I would rather the equivalent of having to run 'sudo' to be able to alter trunk.
[11:10] <jam> so that: yes anyone on our team can fix trunk if we need to, but we have to do so very explicitly instead of accidentally
[11:10] <dimitern> jam, makes sense - preventing accidental mistakes, provided it doesn't impede normal workflow
[11:12] <rogpeppe> dimitern: reviewed
[11:12] <jam> so mostly I'm trying to find the tasteful point in balancing these desires, adding goose-bot to ~gophers is the most expedient solution, though not one I personally control.
[11:12] <jam> as is having the branch owned explicitly by goose-bot
[11:13] <jam> I suppose goose-bot the launchpad account could just have us all know the password, and all have our ssh-keys attached to the account.
[11:13] <jam> mgz: ^^?
[11:13] <jam> that would give us "do X to become the goose-bot superuser"
[11:13] <dimitern> rogpeppe: tyvm
[11:14] <jam> mgz: ah, but the problem ends up that only goose-bot can approve changes to ~goose-bot/ branches. I'll have to look into the review side of things to figure out how to fix that
[11:14] <mgz> that would probably be okay
[11:15] <jam> mgz: looks like you can set a "reviewers" on a branch
[11:15] <jam> which I can just make ~gophers
[11:15] <mgz> yeah
[11:15] <jam> so they can approve branches even though they can't commit directly to it.
[11:35] <mgz> jam: poke?
[11:35] <wallyworld_> rogpeppe: i am around now, am in a stand up
[11:35] <rogpeppe> wallyworld_: np, the issue's been fixed now.
[11:36] <wallyworld_> ok, sorry i was at soccer training
[11:58] <rogpeppe> wallyworld_: i only pinged you 'cos you were the only one that showed up on the IRC user list :-)
[11:58] <wallyworld_> ah ok
[11:58] <wallyworld_> i didn't log out at my EOD
[11:59] <rogpeppe> a couple of CLs if anyone wants. the first one is pretty trivial, the second a bit bigger: https://codereview.appspot.com/7197043/ https://codereview.appspot.com/7133063/
[11:59] <dimitern> rogpeppe: I'm on the first one
[11:59] <rogpeppe> dimitern: thanks
[12:04] <dimitern> rogpeppe: reviewed
[12:04] <rogpeppe> dimitern: thanks
[12:04] <rogpeppe> anyone else wanna take it to the magic two LGTMs? :-) https://codereview.appspot.com/7197043/
[12:05] <dimitern> rogpeppe: it's weird though, unlike the usual case the first comment wasn't "Please take a look" from you
[12:06] <rogpeppe> dimitern: ha, i'd forgotten to lbox propose it without -wip
[12:07] <rogpeppe> dimitern: it's got that message now :-)
[12:07] <dimitern> rogpeppe: ok :)
[12:24] <rogpeppe> niemeyer: yo!
[12:25] <niemeyer> rogpeppe: Heya!
[12:28] <dimitern> niemeyer: hey!
[12:28] <niemeyer> dimitern: Hey there
[12:28] <dimitern> niemeyer: would you like to take a look at this - https://codereview.appspot.com/7181046/
[12:34] <jam> mgz, wallyworld_, dimitern: I just sent you guys an email with the security keys, etc you'll need. I used your public GPG keys, but if you need help figuring out how to decode them, just ask.
[12:34] <dimitern> jam: cheers
[12:37] <dimitern> jam: yep, I have to replace that PGP key for which I forgot the passphrase a long time ago
[12:38] <dimitern> jam: I'll do it today and you can resend it with my new key perhaps?
[12:42] <rogpeppe> niemeyer: small CL to make add multiple addrs to the API: https://codereview.appspot.com/7197043/
[12:43] <niemeyer> dimitern: CHecking
[12:43] <dimitern> thanks
[12:43] <niemeyer> rogpeppe: Super, thanks
[12:45] <niemeyer> rogpeppe: Btw, have you had a chance to check that bug Dave filed?
[12:45] <rogpeppe> niemeyer: which one?
[12:45] <niemeyer> rogpeppe: The one saying bootstrap is broken
[12:46] <rogpeppe> niemeyer: i couldn't reproduce it. i suspect he was running without --upload-tools.
[12:47] <niemeyer> rogpeppe: Have you tried in the regions he suggested?
[12:47] <niemeyer> rogpeppe: Or at least one of them?
[12:48] <rogpeppe> niemeyer: i'll do that. the error in the bug report "error: API entity name not found in configuration" should not be possible to happen in the branch he was talking about.
[12:48] <rogpeppe> niemeyer: but there may well be another bug
[12:48] <niemeyer> rogpeppe: I'm poking because he asked there, so it'd be good to at least interact to clarify the bug
[12:49] <niemeyer> Since Dave isn't on the same timezone, if we don't get back to him on async locations, we won't talk
[12:51] <niemeyer> dimitern: Any significant change to the ec2 logic on that bootstrap function?
[12:52] <dimitern> niemeyer: how do you mean?
[12:52] <dimitern> niemeyer: no, it's essentially the same
[12:52] <dimitern> niemeyer: the Bootstrap() code, that is
[12:54] <rogpeppe> niemeyer: i'm trying it now
[12:55] <niemeyer> rogpeppe: Thanks a lot
[12:55] <niemeyer> dimitern: Cool, I was really just curious if there was anything that had to be done differently there
[12:55] <niemeyer> dimitern: It's great that there isn't (except for Roger's point in the CL, which I agree with)
[12:56] <niemeyer> dimitern: Have you seen rogpeppe's comment?
[12:56] <niemeyer> dimitern: Are there consistency issues there too?
[12:56] <dimitern> niemeyer: well, it's seems not - both tests (svc doubles and live) pass - although on canonistack the lack of floating IPs fails the test, but everything else works
[12:57] <dimitern> niemeyer: about consistency - not sure how to test that, but I've run into other consistency issues with OS on some API calls
[12:57] <niemeyer> dimitern: Oh, consistency issues and "seems" don't go well together :-)
[12:58] <niemeyer> dimitern: The idea, in S3, is that the answer is totally arbitrary for an undefined period of time
[12:58] <rogpeppe> dimitern: i suggest starting without any of the eventual-consistency loops, and seeing if things still work.
[12:58] <niemeyer> dimitern: You create, and it's not there.. you delete, and it's still there
[12:58] <niemeyer> rogpeppe: Please no
[12:58] <dimitern> niemeyer: I've had the same issues with swift while doing live tests
[12:58] <niemeyer> rogpeppe: We already have the logic for that.. let's not introduce the bug to see if we can hit it
[12:59] <dimitern> niemeyer: creating/deleting/modifying containers in quick succession
[12:59] <niemeyer> rogpeppe: I agree with you cleaner would be better, but let's ask someone that actually knows that stuff if OpenStack is consistent or not
[12:59] <rogpeppe> niemeyer: i suppose so. but if there are no such issues in openstack, then that code is more complex for no good reason
[12:59] <rogpeppe> niemeyer: yes, that's a good plan
[13:00] <niemeyer> rogpeppe: Sure, that's the part I agree.. I just don't think rolling back something we know works well to wait for the bug is great
[13:00] <niemeyer> dimitern: Oh, then it has the same issues
[13:00] <dimitern> rogpeppe: well, we can ask yes, but how can it be consistent, when the arch is the same - distributed, multi-tier, API disconnected from the actual service, etc.
[13:00] <niemeyer> dimitern, rogpeppe: I suggest just leaving the same logic there then
[13:01] <dimitern> niemeyer: yeah, I agree
[13:01] <niemeyer> dimitern, rogpeppe: If we start to have a few other backends with the exact same logic of Bootstrap, we should factor it out..
[13:01] <rogpeppe> niemeyer: agreed
[13:01] <niemeyer> dimitern, rogpeppe: That said, I think OpenStack is perhaps too similar to EC2.. I suggest seeing how the others look like before going over the trouble of generalizing
[13:02] <rogpeppe> niemeyer: +1
[13:02] <dimitern> niemeyer: +1 as well - let's not refactor/optimize prematurely :)
[13:06] <niemeyer> dimitern: LGTM
[13:07] <niemeyer> dimitern: Does it work for real already?
[13:07] <dimitern> niemeyer: great, 10x
[13:07] <dimitern> niemeyer: yes it does on canonistack, partially
[13:08] <dimitern> niemeyer: starting the instance works, putting the tools, all ok, except for the floating iP shortage, which fails to add an address to the machine after building
[13:14] <dimitern> rogpeppe: can I consider your review as LGTM as well, with the points mentioned addressed?
[13:15] <rogpeppe> dimitern: i'll have a quick once-over, if that's ok
[13:16] <rogpeppe> niemeyer: i have a suspicion that eventual-consistency issues are fouling upload-tools.
[13:16] <dimitern> rogpeppe: you mean repropose it after changes before submitting?
[13:16] <rogpeppe> dimitern: yeah
[13:16] <dimitern> rogpeppe: sure
[13:18] <rogpeppe> niemeyer: ah, no that's not it.
[13:20] <dimitern> rogpeppe: reproposed - https://codereview.appspot.com/7181046/
[13:21] <rogpeppe> dimitern: looking
[13:22] <rogpeppe> dimitern: LGTM
[13:22] <dimitern> rogpeppe: cheers
[13:23] <rogpeppe> niemeyer: bootstrap against sa-east-1 works fine for me, although it failed for me first time because i used a different juju to the one it was uploading
[13:24] <rogpeppe> niemeyer: i suspect that was dfc's issue too
[13:24] <niemeyer> rogpeppe: Curious.. was the symptom the same?
[13:24] <rogpeppe> niemeyer: similar
[13:25] <rogpeppe> niemeyer: the problem (for me) was that it was making the cloudinit script with an old version of the agent config data structure.
[13:27] <niemeyer> rogpeppe: How did that change again?
[13:27] <niemeyer> rogpeppe: This kind of thing is interesting to observe and keep in mind
[13:27] <niemeyer> rogpeppe: THis is a major breakage
[13:27] <rogpeppe> niemeyer: in my case, i was using a version that produced JSON, not YAML
[13:27] <niemeyer> rogpeppe: Ah, that
[13:27] <rogpeppe> niemeyer: the problem is that we're not incrementing the version numbers when we make incompatible changes
[13:28] <rogpeppe> niemeyer: which is of course convenient when we're breaking things all the time, but will lead to these kinds of issue
[13:30] <rogpeppe> niemeyer: actually... i don't think we check that the tools we're uploading are compatible with the version that's running. that should be fixed, if true.
[13:31] <rogpeppe> niemeyer: (not that that would've helped here though
[13:31] <niemeyer> rogpeppe: What I mean is that breaking isn't okay.. the problem is breaking
[13:32] <niemeyer> rogpeppe: and breaking without even being aware that you're breaking
[13:32] <rogpeppe> niemeyer: i was very aware that i was making breaking changes
[13:32] <niemeyer> rogpeppe: You should mention that, and coordinate with Dave an update to the tools
[13:33] <niemeyer> rogpeppe: Since whatever is up there doesn't work anymore
[13:33] <niemeyer> rogpeppe: Just being aware isn't quite enough :)
[13:33] <rogpeppe> niemeyer: i was presuming dave was updating the tools on every release, given that every release is breaking backward compatibility, pretty much
[13:34] <niemeyer> rogpeppe: Sorry, I'm talking past you
[13:34] <rogpeppe> niemeyer: the next one is going to too - how big a priority for us is preserving backward compatibility currently?
[13:34] <niemeyer> rogpeppe: Please coordinate with Dave when you introduce breaking changes.
[13:35] <niemeyer> rogpeppe: Thanks.
[13:35] <rogpeppe> niemeyer: will do
[13:43] <rogpeppe> lunch
[14:20] <niemeyer> rogpeppe: Please ping once you're back
[14:20] <rogpeppe> niemeyer: ping
[14:20] <niemeyer> rogpeppe: Yo :)
[14:20] <niemeyer> rogpeppe: Do you have some time for a call in.. 10 mins?
[14:20] <rogpeppe> niemeyer: sure
[14:20] <niemeyer> rogpeppe: COol thanks
[14:32] <niemeyer> rogpeppe: Will send the invite
[14:48] <aram> I won't be able to join today's kanban meeting, have to run to some place. mramm, I think this applies to our 1:1 as well (though not 100% yet, I might be back soon enough).
[14:48] <mramm> I may not be able to make the 1 on 1 either
[14:49] <mramm> there are sabdfl meetings all day here in Austin
[15:02] <rogpeppe> is anyone gonna make the kanban meeting?
[15:02] <rogpeppe> i'll be there if anyone else will
[15:08] <rogpeppe> fwereade, mramm: hiya
[15:08] <rogpeppe> fwereade: how's tricks?
[15:09] <fwereade> rogpeppe, heyhey, not bad thanks
[15:09] <fwereade> rogpeppe, and yourself?
[15:09] <rogpeppe> fwereade: not bad at all thanks, pushing on.
[15:10] <rogpeppe> fwereade: missing your reviews :-)
[15:10] <fwereade> rogpeppe, awesome
[15:10] <fwereade> rogpeppe, I came here with the best of intentions but it's been hard to find the energy ;)
[15:10] <rogpeppe> fwereade: no, i wouldn't expect you to while you're there tbh
[15:11] <fwereade> rogpeppe, jolly good :)
[15:32] <dimitern> fwereade: hey :) how's texas?
[15:52] <niemeyer> Lunch.. biab
[15:55] <fwereade> dimitern, heyhey
[15:55] <fwereade> dimitern, texas is... texan :)
[15:56] <fwereade> dimitern, although that's an unfair thing to say really, this is austin after all
[15:56] <fwereade> dimitern, and I've barely left the hotel actually
[15:56] <fwereade> dimitern, when not working, sleeping has been high priority
[15:56] <fwereade> dimitern, I *am* very happy that my bag was delivered last night
[15:56] <fwereade> dimitern, that's 3 timesin a row now
[15:56] <fwereade> dimitern, tyvm for reviews btw
[15:57] <dimitern> fwereade: wow, lost again?
[15:57] <fwereade> dimitern, yep :/
[15:57] <fwereade> dimitern, I'm getting used to it now though
[15:57] <dimitern> fwereade: np, my pleasure
[15:57] <dimitern> fwereade: hehe, all in there?
[15:57] <fwereade> dimitern, yeah, nothing lost
[15:58] <fwereade> dimitern, all I really suffered was a brief blood-pressure spike at houston
[15:58] <dimitern> fwereade: hmm, that doesn't sound good
[15:58] <dimitern> fwereade: how was the flight?
[15:59] <fwereade> dimitern, only metaphorical -- a brief internal GAAAAAAAAAAAAAAAAH
[15:59] <fwereade> dimitern, flight was way smoother than I expected given the weather at heathrow
[16:00] <fwereade> dimitern, greenland was covered in clouds, which was a shame, that place is *beautiful* if you have a nice view from 40000ft
[16:00] <dimitern> fwereade: yeah, the cancelled like 250 flights that day
[16:00] <fwereade> dimitern, oof, luckier than I thought then :)
[16:00] <dimitern> luckily you managed to sneak through
[16:01] <fwereade> dimitern, was able to be pretty relaxed about the prospect though, I could always have stayed the night with my sister, she's pretty close
[16:01] <dimitern> fwereade: she always seems around when you're somewhere on a trip :)
[16:01] <fwereade> dimitern, heh, maybe :)
[16:03] <fwereade> hazmat, ping
[16:04] <dimitern> fwereade: we have bootstrap working with openstack now, landed today
[16:04] <fwereade> dimitern, w00t!
[16:04] <dimitern> :)
[16:04] <dimitern> yeah, it's taking shape faster now I think
[16:05] <dimitern> the provider
[16:05] <hazmat> fwereade, pong
[16:05] <fwereade> hazmat, I think we have enough people to discuss identities if you can tear yourelf away
[16:05] <fwereade> hazmat, mramm has been collecting interested parties
[16:08] <rogpeppe> i'd love a review of this branch, if anyone can spare a mo. i'm stacking up stuff on top of it. it shouldn't be too bad, despite the number of files changed: https://codereview.appspot.com/7133063/
[16:55] <rogpeppe> dimitern: unfortunately the branch you reviewed earlier was WIP for a good reason - i hadn't got tests to pass yet!
[16:55] <mgz> minor details :)
[16:56] <rogpeppe> dimitern: i've now updated it so they do, but somehow it was necessary to add some more stuff along the way, and it's acquired a dependency. if you could have another look (and at the dependency too), that'd be great. https://codereview.appspot.com/7197049/
[17:19] <dimitern> rogpeppe: sorry, just saw this
[17:19] <rogpeppe> dimitern: np
[17:19] <dimitern> rogpeppe: I'll take a look now
[17:19] <rogpeppe> dimitern: thanks
[17:20] <dimitern> rogpeppe: while I'm on it, would like to look at https://codereview.appspot.com/7195046
[17:21] <rogpeppe> dimitern: looking
[17:23] <niemeyer> rogpeppe: Would be interesting to have your opinion on https://codereview.appspot.com/7149043/
[17:23] <niemeyer> rogpeppe: as you're working right around it
[17:24] <rogpeppe> niemeyer: i've pinged dfc for a conversation about this
[17:24] <rogpeppe> niemeyer: hopefully we'll have one tonight
[17:24] <rogpeppe> niemeyer: i think it's the wrong thing to do, but he might have better plans than me, so i want a chat before commenting too much
[17:25] <niemeyer> rogpeppe: What seems wrong, specifically?
[17:25] <niemeyer> rogpeppe: Looks quite straightforward to me
[17:25] <rogpeppe> niemeyer: i think it should be a machiner job, not a new subcommand
[17:26] <niemeyer> rogpeppe: Ah, indeed
[17:26] <rogpeppe> niemeyer: then it works at the same level as the API server, and in the future we'll be able to dynamically adjust servers etc
[17:26] <niemeyer> rogpeppe: Agreed
[17:26] <dimitern> rogpeppe: you've got a review
[17:26] <rogpeppe> dimitern: thanks a lot
[17:26] <niemeyer> rogpeppe: Would you mind to point that out in the CL?
[17:26] <niemeyer> rogpeppe: Even if you include "Let's talk live about it."?
[17:26] <rogpeppe> niemeyer: ok, i will do
[17:27] <niemeyer> rogpeppe: Thanks!
[17:27] <niemeyer> rogpeppe: The stater itself looked nice.. I've skimmed over too quickly thinking it was a job as well
[17:28] <rogpeppe> niemeyer: yes, the stater itself is ok, but i'm not sure it works very well as a task
[17:28] <rogpeppe> niemeyer: most of the logic is fine though
[17:29] <niemeyer> rogpeppe: Maybe it needs additional stuff, but what's there seems well structured, and necessary
[17:30] <rogpeppe> niemeyer: yes. i'm not entirely sure that worker/stater is the right place, but all the unpacking and running logic is good, which makes up the bulk.
[17:30] <niemeyer> rogpeppe: Seems right as a worker too
[17:30] <dimitern> mgz: ping
[17:31] <rogpeppe> niemeyer: i was wondering if the tar unpacking code might live nicely in a standalone package, but it's probably ok where it is until we need it elsewhere.
[17:31] <niemeyer> rogpeppe: Indeed
[17:33] <rogpeppe> niemeyer: i'm going to try to catch dave tonight - about when he starts work.
[17:33] <niemeyer> rogpeppe: Super, cheers
[17:44] <dimitern> niemeyer: if you have time, take a look at https://codereview.appspot.com/7195046/
[17:52]  * rogpeppe just started running first live test that connects to the API server... i wonder if it'll work.
[18:00] <mgz> rogpeppe: did it? :)
[18:00] <rogpeppe> mgz: still running...
[18:01] <rogpeppe> mgz: oh, darn
[18:01] <rogpeppe> mgz: failed
[18:01] <mgz> ;_;
[18:01] <dimitern> mgz: ah, you're here :) can you look at this https://codereview.appspot.com/7195046/ - especially the way private and public addresses are discovered (ported the logic from py-juju)
[18:01] <mgz> dimitern: sure
[18:02] <dimitern> mgz: thanks
[18:02] <mgz> you ported the tests too, right? :)
[18:03] <dimitern> mgz: well, not really, but I test for all paths I think
[18:03] <mgz> the tests are the bit with value, because they cover the sort of json I actually saw in the wild
[18:04] <dimitern> mgz: I see, then I could port their essence as well
[18:07] <mgz> hm... and GetServerAddresses really shouldn't be needed, it's included in servers/{}/detail which juju is likely using in all cases
[18:08] <dimitern> mgz: unfortunately, it's not the same always
[18:09] <mgz> that's an ongoing issue though, the ip/name bindings aren't static
[18:09] <mgz> unless you mean something else?
[18:09] <dimitern> mgz: sometimes (at startup, but it happened to me multiple times after some uptime) the address fields are empty there, while the /ips returns them correctly
[18:09] <mgz> right
[18:10] <mgz> well, ips will only work once a binding exists
[18:10] <mgz> but that's pretty much the same thing
[18:10] <dimitern> what binding?
[18:10] <dimitern> i'm not talking about floating ips
[18:11] <mgz> when you first start a machine, you get details back before the networking setup is done
[18:11] <dimitern> the automatic ones nova assigns at boot
[18:11] <mgz> there's a hack you might notice in the python code that polls for contents of addresses in launch in one case (where you need to assign a floating ip)
[18:11] <dimitern> mgz: yes, but even after that /servers/detail won't get me the addresses - they're always empty
[18:12] <mgz> they're not always empty, they're just initially empty
[18:12] <dimitern> mgz: well, /ips works even at BUILD, while /servers/detail doesn't
[18:12] <mgz> I think because it reflects current reality rather than intent or something
[18:12] <mgz> it works at BUILD, just not straight away, only when it's actually bound
[18:13] <mgz> anyway, this might be a neat trick for the moment
[18:14] <dimitern> anyway, it's not reliable to use /servers/detail for addresses in my experience
[18:14] <dimitern> and having it this way simplifies the tests / doubles a bit
[18:15] <mgz> really juju needs to learn that addresses aren't reliable
[18:15] <dimitern> :)
[18:15] <dimitern> especially if they float
[18:15] <mgz> but if this hacks around that broken assumption for now, it's not the end of the world
[18:17] <dimitern> yeah
[18:21] <rogpeppe> mgz: i was listening on localhost!
[18:24] <rogpeppe> time to stop
[18:24] <rogpeppe> g'night all
[18:25] <dimitern> rogpeppe: c u
[18:30] <mgz> dimitern: commented, fine overall, but I think much of that code should live in juju-core
[18:30] <dimitern> mgz: thanks, I'll think about it some more tomorrow
[20:14] <fwereade> davecheney, ping
[20:38] <fwereade> davecheney, I need to head to meetings in a few minutes but I should be on again in a couple of hours, let me know if I can clarify anything...
[22:01] <rogpeppe> davecheney: ping
[22:18] <davecheney> rogpeppe: ack
[22:18] <rogpeppe> davecheney: yo!
[22:18] <rogpeppe> davecheney: G+?
[22:19] <davecheney> sure
[22:23] <davecheney> ringing ...
[22:23] <davecheney> this is fucking annoying
[22:23] <davecheney> can we use Skype like grownups ?


[01:01] <slangasek> bdmurray: that process is still in the same state an hour later, including no further cpu time used, so it's blocked on something I can't see (because /someone/ we know needed to make strace not work against already running processes).  I think it got stuck due to a network outage to launchpad, given the file list.  Killing it and running again
[01:35] -queuebot:#ubuntu-release- New binary: cu2qu [amd64] (bionic-proposed/universe) [1.3.0-1] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: dh-dlang [ppc64el] (bionic-proposed/none) [0.1] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: dh-dlang [amd64] (bionic-proposed/none) [0.1] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: dh-dlang [i386] (bionic-proposed/none) [0.1] (no packageset)
[05:17] -queuebot:#ubuntu-release- New binary: dh-dlang [arm64] (bionic-proposed/none) [0.1] (no packageset)
[05:18] -queuebot:#ubuntu-release- New binary: dh-dlang [armhf] (bionic-proposed/none) [0.1] (no packageset)
[08:42] -queuebot:#ubuntu-release- New: accepted dh-dlang [amd64] (bionic-proposed) [0.1]
[08:42] -queuebot:#ubuntu-release- New: accepted dh-dlang [armhf] (bionic-proposed) [0.1]
[08:42] -queuebot:#ubuntu-release- New: accepted dh-dlang [ppc64el] (bionic-proposed) [0.1]
[08:42] -queuebot:#ubuntu-release- New: accepted dh-dlang [arm64] (bionic-proposed) [0.1]
[08:42] -queuebot:#ubuntu-release- New: accepted dh-dlang [i386] (bionic-proposed) [0.1]
[08:43] -queuebot:#ubuntu-release- New: accepted cu2qu [amd64] (bionic-proposed) [1.3.0-1]
[08:43] -queuebot:#ubuntu-release- New: accepted libzc [arm64] (bionic-proposed) [0.3.6-1]
[08:43] -queuebot:#ubuntu-release- New: accepted libzc [i386] (bionic-proposed) [0.3.6-1]
[08:43] -queuebot:#ubuntu-release- New: accepted libzc [amd64] (bionic-proposed) [0.3.6-1]
[08:43] -queuebot:#ubuntu-release- New: accepted libzc [ppc64el] (bionic-proposed) [0.3.6-1]
[08:43] -queuebot:#ubuntu-release- New: accepted libzc [armhf] (bionic-proposed) [0.3.6-1]
[10:30] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-105.128] (core, kernel)
[10:46] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-105.128]
[12:28] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-138.187] (core, kernel)
[12:30] -queuebot:#ubuntu-release- New binary: ufo2ft [amd64] (bionic-proposed/universe) [0.6.2-1] (no packageset)
[12:34] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-105.128~14.04.1] (kernel)
[12:47] -queuebot:#ubuntu-release- Unapproved: file-roller (xenial-proposed/main) [3.16.5-0ubuntu1.2 => 3.26.2-0ubuntu1] (ubuntu-desktop)
[12:54] -queuebot:#ubuntu-release- Unapproved: rejected file-roller [source] (xenial-proposed) [3.26.2-0ubuntu1]
[12:55] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-105.128~14.04.1]
[12:55] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-138.187]
[13:07] -queuebot:#ubuntu-release- New: rejected opengcs [source] (bionic-proposed) [0.3.4+dfsg1-0ubuntu1]
[13:08] -queuebot:#ubuntu-release- New binary: budgie-wallpapers [amd64] (bionic-proposed/universe) [18.04] (personal-fossfreedom)
[13:46] -queuebot:#ubuntu-release- New source: opengcs (bionic-proposed/primary) [0.3.4+dfsg1-0ubuntu1]
[15:07] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (artful-proposed) [1.169.2]
[15:10] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (xenial-proposed) [1.157.15]
[15:17] -queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (zesty-proposed) [1.164.3]
[15:26] <slashd> slangasek, I have found a potential issue with the openjdk-8 depend for ca-certificates-java pkg. Can you please review my comment when you have a chance, I'd like to have your opinion on this --> LP: #1723198 (comment #16) to choose the best approach.
[15:26] <ubot5`> Launchpad bug 1723198 in ca-certificates-java (Ubuntu Zesty) "[SRU] upgrade from 14.04 to 16.04 fails with: ca-certificates 20170717~16.04.1 failed to install/upgrade: triggers looping, abandoned" [Medium,In progress] https://launchpad.net/bugs/1723198
[15:30] <slashd> slashd, sorry wrong channel
[16:15] <balloons> bdmurray, thanks for reviewing the juju sru last night. I did the validation this morning and all the autopkgtests are passing now with 2.3 :-). Might we be able to push these into updates today?
[16:22] <bdmurray> balloons: Not on a friday
[16:22] <balloons> bdmurray, no worries, I figured as much :-)
[16:23] <balloons> Just glad the adt tests are sorted
[16:24] <bdmurray> balloons: also I don't see that other bug as having been verified yet
[16:29] <wgrant> Which Juju version is to be SRUed?
[16:35] <bdmurray> bug 1718213
[16:35] <ubot5`> bug 1718213 in juju-core (Ubuntu Zesty) "[SRU] Juju 2.3.1" [Undecided,Fix committed] https://launchpad.net/bugs/1718213
[16:47] <wgrant> Hm does that include Juju releases with catastrophic upgrade bugs?
[16:47] <wgrant> IMO SRUing anything before 2.3.2 is wrong
[16:48] <wgrant> eg. https://bugs.launchpad.net/juju/+bug/1737058
[16:48] <ubot5`> Launchpad bug 1737058 in juju "network-get fails to find configs on 2.3.0 that worked on 2.2.6" [Critical,Triaged]
[16:49] <wgrant> Juju 2.3 may be in simplestreams, but it's not production-ready until 2.3.2 at the earliest.
[17:09] -queuebot:#ubuntu-release- New binary: caja [s390x] (bionic-proposed/universe) [1.18.5-2] (ubuntu-mate, ubuntukylin)
[17:12] -queuebot:#ubuntu-release- New binary: caja [ppc64el] (bionic-proposed/universe) [1.18.5-2] (ubuntu-mate, ubuntukylin)
[17:14] -queuebot:#ubuntu-release- New binary: caja [arm64] (bionic-proposed/universe) [1.18.5-2] (ubuntu-mate, ubuntukylin)
[17:14] -queuebot:#ubuntu-release- New binary: caja [armhf] (bionic-proposed/universe) [1.18.5-2] (ubuntu-mate, ubuntukylin)
[17:17] -queuebot:#ubuntu-release- New binary: caja [amd64] (bionic-proposed/universe) [1.18.5-2] (ubuntu-mate, ubuntukylin)
[17:17] -queuebot:#ubuntu-release- New binary: ruby-guard-compat [amd64] (bionic-proposed/none) [1.2.1-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: caja [i386] (bionic-proposed/universe) [1.18.5-2] (ubuntu-mate, ubuntukylin)
[17:17] -queuebot:#ubuntu-release- New binary: ruby-guard [amd64] (bionic-proposed/none) [2.14.1-1] (no packageset)
[17:32] <balloons> wgrant, yea, it still has the bug, but it is the last stable version of juju. Nothing about the client changes that
[17:33] <balloons> bdmurray, sorry, which bug is missing validation?
[17:33] -queuebot:#ubuntu-release- Unapproved: ca-certificates-java (xenial-proposed/main) [20160321 => 20160321ubuntu1] (core)
[17:34] -queuebot:#ubuntu-release- New: accepted budgie-wallpapers [amd64] (bionic-proposed) [18.04]
[17:34] -queuebot:#ubuntu-release- New: accepted ruby-guard [amd64] (bionic-proposed) [2.14.1-1]
[17:34] -queuebot:#ubuntu-release- New: accepted ruby-guard-compat [amd64] (bionic-proposed) [1.2.1-1]
[17:34] -queuebot:#ubuntu-release- New: accepted ufo2ft [amd64] (bionic-proposed) [0.6.2-1]
[17:34] <bdmurray> balloons: bug 1727355
[17:34] <ubot5`> bug 1727355 in distro-info-data (Ubuntu Zesty) "Juju attempts to bootstrap bionic by default" [High,Fix committed] https://launchpad.net/bugs/1727355
[17:34] -queuebot:#ubuntu-release- New: accepted caja [amd64] (bionic-proposed) [1.18.5-2]
[17:34] -queuebot:#ubuntu-release- New: accepted caja [armhf] (bionic-proposed) [1.18.5-2]
[17:34] -queuebot:#ubuntu-release- New: accepted caja [ppc64el] (bionic-proposed) [1.18.5-2]
[17:34] -queuebot:#ubuntu-release- New: accepted caja [arm64] (bionic-proposed) [1.18.5-2]
[17:34] -queuebot:#ubuntu-release- New: accepted caja [s390x] (bionic-proposed) [1.18.5-2]
[17:34] -queuebot:#ubuntu-release- New: accepted caja [i386] (bionic-proposed) [1.18.5-2]
[17:35] <balloons> bdmurray, ahh, right, ty
[17:35] -queuebot:#ubuntu-release- Unapproved: ca-certificates-java (zesty-proposed/main) [20161107 => 20161107ubuntu1] (core)
[17:35] <slashd> davecore ^
[17:37] <balloons> wgrant, btw, trying to put out a 2.2.7 today
[17:37] <davecore> slashd: ack
[17:54] <doko><EMAIL_ADDRESS>[17:54] <doko> a python3.5 (yes .5) traceback showing up?
[18:00] <doko> tjaalton: fyi, there are some freeipa autopkg test failures
[18:14] <tjaalton> doko: likely the same reason as dogtag-pki, libjaxrs-api update
[18:14] <tjaalton> I need to package jboss-jaxrs-api..
[18:35] <tjaalton> doko: hm no, looks like it fails to resolve the ip address of the vm
[18:35] <tjaalton> this used to work: IP=`ip route get <IP_ADDRESS> | awk '{print $NF; exit}'`
[18:37] <slangasek> tjaalton: it fails because you are getting multiple default routes
[18:38] <tjaalton> ah :)
[18:38] <slangasek> which I think is a bug, but you should still filter down to 1
[18:38] <slangasek> er, although, you have the 'exit' in there
[18:38]  * slangasek ponders
[18:39] <slangasek> yeah, it's not that, because the 'exit' is there precisely so you only get one result
[18:40] <tjaalton> I must've copied that from somewhere, can't remember where.. but anyway
[18:41] <slangasek> just spot-checked, and I get reasonable results for that command in an autopkgtest instance
[18:50] <tjaalton> hrm
[19:16] <doko> fyi, demoted graphviz in -proposed. need to see what pulls it back again ... will look at it tomorrow
[19:16] <doko> Laney: still seeing the installation issues with python3-distlib, so let's try to get the migration done soonish
[19:21] <tjaalton> slangasek: was that with updated iproute2? I see that it got updated after the last working freeipa autopkgtest run
[19:27] <slangasek> tjaalton: hmm, it should've been, but let me check
[19:27] <slangasek> tjaalton: aha, yes, the output of iproute2 has changed
[19:27] <slangasek> <IP_ADDRESS> via <IP_ADDRESS> dev wlan2 src <IP_ADDRESS> uid 1000
[19:27] <slangasek>     cache
[19:27] <tjaalton> grreat
[19:28] <slangasek> tjaalton: so I'll mark that badtest in the meantime
[19:30] <tjaalton> yes, it would fail later anyway because the dogtag instance would be broken..
[19:30] <tjaalton> might fix that over the holidays
[19:30] <slangasek> tjaalton: ok.  meanwhile, I'm going to upload the fix for the iproute2 issue because I'm already here
[19:33] <tjaalton> oh, I can fix freeipa if you meant that?
[19:33] <slangasek> tjaalton: too late, I uploaded
[19:33] <slangasek> ;)
[19:33] <tjaalton> heh, okay
[19:33] <tjaalton> no worries
[19:42] <slangasek> tjaalton: and it ftbfs on all archs
[19:56] <tjaalton> bah
[19:57] <tjaalton> ah yes
[19:57] <tjaalton> 4.4.x is too old for new samba
[19:58] <tjaalton> I have 4.6 almost done in git, but it needs bind 9.11 which is fairly new in debian
[20:04] <slangasek> tjaalton: ok, bind9 merge is due and I discussed it already w/ the server team, since it's required for openssl 1.1.1
[20:16] <tjaalton> cool
[20:45] <tjaalton> hmm actually upstream provided a backport for 4.4 to build against new samba, so I'll push that (and the autopkgtest update) to debian, then sync
[23:10] -queuebot:#ubuntu-release- New binary: mate-polkit [ppc64el] (bionic-proposed/universe) [1.18.2-2] (ubuntu-mate, ubuntukylin)
[23:10] -queuebot:#ubuntu-release- New binary: mate-polkit [s390x] (bionic-proposed/universe) [1.18.2-2] (ubuntu-mate, ubuntukylin)
[23:16] -queuebot:#ubuntu-release- New binary: mate-polkit [i386] (bionic-proposed/universe) [1.18.2-2] (ubuntu-mate, ubuntukylin)
[23:16] -queuebot:#ubuntu-release- New binary: mate-polkit [amd64] (bionic-proposed/universe) [1.18.2-2] (ubuntu-mate, ubuntukylin)
[23:18] -queuebot:#ubuntu-release- New binary: mate-polkit [arm64] (bionic-proposed/universe) [1.18.2-2] (ubuntu-mate, ubuntukylin)
[23:19] -queuebot:#ubuntu-release- New binary: terminado [amd64] (bionic-proposed/universe) [0.7-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: mate-polkit [armhf] (bionic-proposed/universe) [1.18.2-2] (ubuntu-mate, ubuntukylin)
[23:33] <slangasek> slashd: your xenial upload has wrong changelog syntax to link the bug; I'm rejecting/reuploading
[23:34] -queuebot:#ubuntu-release- Unapproved: rejected ca-certificates-java [source] (xenial-proposed) [20160321ubuntu1]
[23:35] -queuebot:#ubuntu-release- Unapproved: ca-certificates-java (xenial-proposed/main) [20160321 => 20160321ubuntu1] (core)
[23:36] -queuebot:#ubuntu-release- Unapproved: rejected ca-certificates-java [source] (zesty-proposed) [20161107ubuntu1]
[23:38] -queuebot:#ubuntu-release- Unapproved: ca-certificates-java (zesty-proposed/main) [20161107 => 20161107ubuntu1] (core)