[15:59] <jgrimm> o/
[15:59] <rharper> o/
[16:00] <jgrimm> arosales, around to chair today?
[16:01] <caribou> o/
[16:01] <powersj> o/
[16:01] <rbasak> o/
[16:01] <nacc> o/
[16:02] <jgrimm> howdy, we may need an alternate chair today
[16:02] <jgrimm> rharper,  you are next in line.. wanna take?
[16:02] <rharper> yeah
[16:02] <jgrimm> https://wiki.ubuntu.com/ServerTeam/Meeting
[16:02] <rharper> #startmeeting ubuntu-server-team
[16:02] <meetingology> Meeting started Tue Oct  4 16:02:27 2016 UTC.  The chair is rharper. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:02] <meetingology> Available commands: action commands idea info link nick
[16:02] <rharper> #topic Review ACTION points from previous meeting
[16:02] <jgrimm> thanks rhaper
[16:02] <jgrimm> rharper even!
[16:03] <rharper> jgrimm: sure
[16:03] <rharper> jgrimm: Add a url for server release bugs to irc commands for meetings ?
[16:03] <smoser> o/
[16:04] <jgrimm> rharper, bah.. i just need to add the rls-x url in again
[16:04] <jgrimm> rharper, leave it, i'll do right after meeting
[16:04] <rharper> ok, we'll keep that
[16:04] <rharper> jamespage checking with old iscsitarget users on relevancy with new kernels
[16:04] <jamespage> oh boy
[16:05] <jamespage> better carry that - I need to figure out who to ask
[16:05] <rharper> sure
[16:05] <rharper> powersj to put together iso testing signup sheet
[16:05] <jgrimm> hmm.. that's old
[16:05] <jgrimm> rharper, where are you looking at agenda from
[16:05] <powersj> rharper, yeah - done a while ago ;)
[16:05] <rharper> https://wiki.ubuntu.com/MeetingLogs/Server/20160927
[16:06] <jgrimm> ok, should have been marked done last time. not on wiki at least
[16:06] <rharper> #done powersj to put together iso testing signup sheet
[16:07] <jgrimm> rharper, you are looking at the agenda of last week
[16:07] <jgrimm> by looking at the minutes. :)
[16:07] <rharper> but I was successful, 2/3 still need doing =)
[16:07] <jgrimm> heheheh. indeed!
[16:08] <rharper> ok, I don't see any other actions to review
[16:08] <rharper> #topic Yakkety Development
[16:08] <rharper> #link https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule
[16:08] <rharper> just up to Final Freeze
[16:08] <jgrimm> rush to the finish line
[16:08] <rharper> very much
[16:08] <rharper> #subtopic Release Bugs
[16:09] <jgrimm> anything to discuss wrt urgent/critical for freeze?
[16:09] <rharper> maybe, smoser re: the nss/cloud-init/dbus.socket stuff
[16:09] <nacc> down to 4 ftbfs in the test rebuild
[16:09] <jgrimm> cpaelzer got a new upload in today (already in archive) for dpdk, he has some cleanups to do with respect to latest ovs
[16:10] <smoser> bug 1629868
[16:10] <smoser> and bug 1629797
[16:10] <smoser> are the fun
[16:10] <smoser> they're a result of 2 changes... a.) cloud-init.service now running 'Before=basic.target'
[16:10] <smoser> b.) adding of 'resolv' to /etc/nsswitch.conf in yakkety
[16:11] <smoser> sorry, spelling. resolve
[16:11] <jgrimm> smoser, fix in hand? need help?
[16:11] <rharper> smoser: and (a) was required to ensure cloud-init can mount/unmount devices
[16:11] <rharper> before systemd.mount does
[16:11] <smoser> i'd say *a* fix is possible, but everyone agrees that while being least-intrusive of the options, it seems yucky
[16:12] <smoser> (that fix is to put 'Before=dbus.service' in cloud-init.service, which seems quite counter obvious at first glance)
[16:12] <rharper> indeed
[16:12] <smoser> so, continuing to work that. the good news is it is fairly easily recreatable.
[16:13] <rharper> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-y-tracking-bug-tasks.html#ubuntu-server
[16:13] <jgrimm> ok, i just read the dbus one.
[16:14] <rharper> any other release items/issues ?
[16:14] <jgrimm> rls-y looks fine
[16:14] <rharper> k
[16:14] <rharper> #topic Server & Cloud Bugs (caribou)
[16:14] <caribou> Hi,
[16:14] <caribou> sosreport up for review, removed the clamav tomsfastmath Universe dependancy
[16:14] <smoser> i'm hoping to fix bug 1630274 shortly
[16:14] <caribou> that's about it
[16:14] <smoser> i need odd_bloke to verify that it works for him, but i expect it to
[16:15] <rharper> any questions for caribou
[16:16] <rharper> thanks caribou
[16:16] <jgrimm> nope, but on the topic, i'm currently working through bugs that have xenial, trusty tasks still in some sort of in-progress state to nudge them along
[16:16] <jgrimm> get owners as needed, etc
[16:16] <jgrimm> that's all
[16:16] <rharper> thanks
[16:17] <rharper> #topic Weekly Updates & Questions for the QA Team (powersj)
[16:17] <powersj> Spent last week at QA sprint with folks from other areas, learned lots. Focusing this week on triage, gathering cloud-init integration test cases, qemu/kvm live migration tests running.
[16:17] <powersj> Server ISO kernel issues got resolved last week (yea!) and size is decreasing nicely. Only waiting on GCC 6 reductions to hopefully get us down below 703 MB (amd64 is at 743 MB today). Post-release will continue analysis of ISO size and contents. /qa_update
[16:17] <rharper> #link https://jenkins.ubuntu.com/server/
[16:17] <rharper> powersj: thanks for the summary from the sprint, that was super helpful
[16:18] <nacc> +1
[16:18] <powersj> good to hear :)
[16:18] <rharper> should be an interesting discussion with the team later this week
[16:19] <rharper> any questions for powersj ?
[16:19] <jgrimm> :) heh. josh already had to hear a few rants from me.
[16:19] <rharper> haha
[16:19] <rharper> yeah, I was resisting the urge to poke the messenger
[16:19] <jgrimm> :)
[16:20] <rharper> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
[16:22] <rharper> nothing from kernel team
[16:22] <rharper> #topic Upcoming Call For Papers
[16:22] <rharper> any new CfPs to think about ?
[16:23] <jgrimm> fosdem 2017 has end of Oct CFP deadline
[16:23] <jgrimm> otherwise october looking pretty empty for CFPs (according to LWN)
[16:23] <rharper> y
[16:24] <rharper> #topic Ubuntu Server Team Events
[16:25] <jgrimm> LinuxCon Europe / ContainerCon Europe: stgraber & brauner are there for LXD/LXC
[16:25] <jgrimm> this week
[16:25] <rharper> ODS is in a few too
[16:25] <jgrimm> indeed that time o year
[16:25] <rharper> #topic Open Discussion
[16:25] <rharper> floor's open
[16:26] <jgrimm> i'll bring up the z blueprint again just for awareness
[16:26] <jgrimm> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-z-server-core
[16:26] <rharper> #link https://blueprints.launchpad.net/ubuntu/+spec/servercloud-z-server-core
[16:26] <jgrimm> open for business
[16:26] <jgrimm> thanks!
[16:26] <jgrimm> that's all from me
[16:26] <rharper> ok
[16:27] <rharper> #topic Assigned merges/bugwork (rbasak)
[16:27] <rbasak> Nothing from me this week. Carry on as normal I think! Any questions or issues to raise?
[16:27] <rharper> ok
[16:28] <rharper> #topic Announce next meeting date, time and chair
[16:28] <rharper> Next meeting will be same time a week from now, chair will be rharper (I shall taunt you a second time!)
[16:29] <jgrimm> :)
[16:29] <rharper> #action jgrimm Add a url for server release bugs to irc commands for meetings
[16:29] <meetingology> ACTION: jgrimm Add a url for server release bugs to irc commands for meetings
[16:29] <rharper> #action jamespage checking with old iscsitarget users on relevancy with new kernels
[16:29] <meetingology> ACTION: jamespage checking with old iscsitarget users on relevancy with new kernels
[16:29] <rharper> adding those for next time since we carry them
[16:29] <rharper> and that's it folks
[16:29] <jgrimm> thanks rharper
[16:29] <rharper> #endmeeting
[16:29] <meetingology> Meeting ended Tue Oct  4 16:29:40 2016 UTC.
[16:29] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2016/ubuntu-meeting.2016-10-04-16.02.moin.txt
[16:29] <caribou> thanks
[16:30] <nacc> rharper: thanks!
[16:30] <rharper> np
[17:29] <arosales> jgrimm: thanks for chairing today, to confirm am I am deck for next week?
[17:29] <jgrimm> arosales, rharper took next week too, unless you'd like a makeup?
[17:32] <arosales> I should be in the office the next 3 weeks, so any of those work for me. Next week is fine and it looks like the wiki currently shows that
[17:33] <arosales> jgrimm: rharper: I can chair next week
[17:33] <jgrimm> arosales, thanks!!
[17:33] <arosales> jgrimm: thanks for chairing this week
[17:35] <jgrimm> heh rharper gets the thanks ^


[01:22] <attunix> Hi. Earlier I came in to ask about writing GUI apps for Ubuntu, and I didn't like pyGTK. Anything C[++]-like?
[01:23] <calc> gtk is C
[01:25] <attunix> calc: but I didn't like pyGTK... that's Python
[01:25] <persia> gtkmm is c++ :)
[01:25] <attunix> anything else
[01:26] <calc> attunix: you wanted to know if there was anything C[++]-like which regular gtk is C so it is very much C like :)
[01:26] <attunix> calc: oh. ok :P
[01:26] <calc> pyGTK is the python bindings so if you want to write in python for gtk/gnome that is what you use...
[01:27] <attunix> Glade pre-setups the interface for you, right?
[01:27] <calc> i believe so
[01:27] <attunix> Thanks.
[01:28] <attunix> How do I set up my own package repositories?
[01:28] <calc> with apt-ftparchive
[01:28] <attunix> calc: thanks :)
[01:31] <ion_> calc, attunix: falcon ftw.
[01:32] <attunix> ion_: what's falcon ftw?
[01:32] <ion_> https://edge.launchpad.net/falcon
[01:33] <ion_> https://launchpad.net/falcon without the edge.
[01:33] <attunix> thx
[01:33] <sladen> attunix: also Qt, which is /very/ C++
[01:33] <attunix> ooh! thanks :)
[01:33] <sladen> attunix: or WxWindows
[01:33] <attunix> ok
[01:34] <persia> Umm..  wxWindows has vast issues.  If you must use WX, please use wxWidgets.
[01:35] <sladen> persia: thanks for the tip; I never realised there /was/ a difference
[01:35] <attunix> I'll look into QT and GTK
[01:35] <persia> sladen: wxWindows is the old, non-unicode version
[01:35] <sladen> "wxWidgets (formerly wxWindows)" ah, nod
[02:22]  * lamont looks around for the big red "RESET" switch for gnome-preferences
[02:23] <ion_> lamont: gconftool --recursive-unset / or something like that.
[02:25] <lamont> ion_:  how do I dump the entire config first?
[02:25]  * lamont rtfc
[02:25] <lamont> rtfm even
[02:26] <ion_> gconftool --dump / :-)
[02:27] <attunix> In Gambas, when I try to create a project it says I can't because access is forbidden. Please help.
[02:27] <ion_> Please read the topic.
[02:28] <attunix> Ok.
[02:28] <attunix> Anyone have any ideas?
[02:28] <attunix> ion_: it's an IDE, by the way.
[02:57] <jdong> grr what do I have to do to make tracker actually useful?
[02:57] <jdong> it doesn't seem to be indexing contents of textfiles (such as irclogs) in a way that actually serves any purpose to me
[02:57] <Burgundavia> jdong: use deskbar with tracker live search
[02:57] <Burgundavia> likely it is not going into . files
[02:57] <Burgundavia> this why Beagle is better, as it supports more files
[02:58] <jdong> Burgundavia: oh no, it's recusing into the dirs, but only recognizes a few keywords
[02:58] <jdong> Burgundavia:  it odesn't seem to default to text for textfiles *.log
[02:58] <jdong> Burgundavia: like I can search for "gutsy" and not find a thing in ~/irclog... which is hard to believe that 2 months of #ubuntu has no mention of gutsy :)
[02:59] <jdong> Do I have to do something to get it to think .log = text?
[03:00] <jdong> I have it set to index 10240kb into each file and 100000 unique words
[03:00] <jdong> is that not enough? :(
[03:01]  * jdong strongly considers reverting back to beagle if this doesn't work out
[03:01] <Burgundavia> personally, I think we should have gone with Beagle
[03:02] <jdong> beagle actually worked for me
[03:02] <jdong> I'd be more than happy to give the daemon 100MB RAM if it does for me what grep couldn't
[03:03] <jdong> aha, it finds it with a .txt extension
[03:07] <jdong> *sigh* I'll just comply and move all my logs to a .txt extension
[03:07]  * jdong files bug, too
[03:13] <attunix> How do I get GTK installed? I keep getting an "error: gtk/gtk.h: no such file or directory".
[03:38] <attunix> anyone familiar with GTK?
[03:39] <sbalneav> A bit.
[03:39] <attunix> This is my first GTK program
[03:39] <attunix> i'm trying to use gcc to compile it,
[03:40] <attunix> but i keep getting an error that gtk/gtk.h doesn't exist
[03:40] <attunix> my first line in the program is #include <gtk/gtk.h>
[03:40] <ion_> Please read the topic.
[03:40] <attunix> i already installed build-ess
[03:40] <attunix> *essential
[03:40] <attunix> ion_: oh.
[03:48] <sbalneav> Cripes, so, he messages me, I start to explain to him, switch to another terminal to figure out a simple command line for him to compile with `pkg-config ... `, and he buggers off.
[03:48] <sbalneav> What do people want, answers in 10 seconds?
[03:48]  * sbalneav sighs
[03:49] <ajmitch> yes
[03:49] <persia> sbalneav: 10 seconds is far too long.  Faster! :)
[03:49] <ajmitch> 10 seconds is an eternity on the internet :)
[03:49] <sbalneav> I guess it must be.
[03:50] <sbalneav> Fortunately, my first modem was an acoustic coupled 300 baud, so I learned patience early :)
[03:50] <ajmitch> a what? ;)
[03:50] <persia> ajmitch: One of those newfangled contraptions one attaches to the phone to let the computer have a conversation.
[03:51] <ajmitch> that doesn't sound safe!
[03:51] <sbalneav> If you were really good, you could whistle at the right frequency, and make the other guy's carrier light come on :)
[03:52] <ajmitch> try doing that with adsl now.. :)
[03:52] <ion_> :-)
[03:52] <Keybuk> ah
[03:52] <Keybuk> the old /ctcp ping looser +++ATH trick
[03:52] <sbalneav> All my truly great hacker skills are now obsolete :)
[03:55] <sbalneav> I used to have the entire stty() option set in my head.  I could wire RS232 breakout boxes with nothing but paperclips.  All these memories will be lost in time, like tears in rain.
[03:57] <Keybuk> Oranges and Lemons...
[04:07] <erosa> bye all
[04:21] <wisu> I modified the flash-plugin.deb  post install to download the flash...tar.gz from a local cd... Q: how does the revision of the deb supposed to look like?
[04:34] <b4sic> hey, i was hoping someone in here with experience developing (freelance or otherwise)
[04:34] <b4sic> would be available for me to run an idea by.
[04:49] <b4sic> welcome, lure.
[04:49] <Lure> hi b4sic
[04:50] <b4sic> you script any?
[04:50] <b4sic> hey j_ack.
[05:16] <OpenSorce> If it's okay to ask this here: If you were evaluating Linux distros for new user suitability, would you consider whether or not it offered Live CD mode and install from Live CD as a "must" or just a plus?
[05:17] <rob> a plus I think
[05:17] <OpenSorce> rob, thank you....but not a must per se, right?
[05:17] <rob> no, they tend to be slow and its "hard" for a user to save their work
[05:18] <OpenSorce> rob, yeah the speed bothers me too....I'd hate for a new person to perceive Live CD speed as the speed the installed system will run
[05:18] <rob> yeah
[05:19] <jdong> rob: I disagree, I'd say it's almost a must
[05:20] <jdong> I, and any potential user, does NOT want to spend time installing a new operating system, making room for it on their system, just to learn that some piece of hwradware is unsupported, or the OS is otherwise dissatisfactory
[05:20] <jdong> as long as the LiveCD boots in a reasonable amount of time, it is essential for evaluating a new operating system
[05:20] <OpenSorce> jdong, thanks.....good point as well
[05:20] <rob> I think live cd environments have their uses, but there are also various negatives to them too. Another issue I have seen is people think it is the installed Linux, and get all confused when you tell them it isn't. Ubuntu even adds a pop up to explain this iirc.
[05:20] <jdong> I find myself almost unwilling nowadays to test new operating systems that do not have an evaluation CD
[05:20] <rob> jdong, I guess you haven't tested Vista then ;)
[05:21] <jdong> rob: unfortunately curiousity lead me to do it
[05:21] <jdong> rob: fortunately their installer is lightning fast, otherwise I would've had more non-CoC things to say about it
[05:21] <OpenSorce> jdong, my boss agrees with you....he won't even let me evaluate openSuse until they release a Live CD version
[05:21] <jdong> OpenSorce: they DO have a livecd/livedvd, no?
[05:21] <jdong> just not installable
[05:21] <jdong> the live-eval thing is totally separate
[05:21] <OpenSorce> jdong, not for the latest release, no
[05:21] <jdong> OpenSorce: ah, ok
[05:22] <jdong> OpenSorce: the thing is, I don't just want a LiveCD evaluator, I want a livecd that boots as closely to the final system as possible
[05:22] <jdong> OpenSorce: IMO the Ubuntu livecd is almost 100% accurate diagnosis of how well Ubuntu works with a particular machine
[05:22] <rob> ever tried to use the live environment on a low spec pc? I almost would consider a Live CD to be a bad thing for those users.
[05:22] <jdong> because the bootup process and hardware detection routines are basically the same as an installed system.
[05:22] <OpenSorce> jdong, good point.....I also think it's essential to see if the hardware is going to work on that distro
[05:22] <jdong> rob: low-spec systems are a weakness, good point.
[05:23] <OpenSorce> maybe a big pop-up that says "This is just Live CD mode, once installed your system will run much faster than this" is a good idea
[05:24] <OpenSorce> rob, did you say ubuntu has that?
[05:24] <rob> I tried using a low spec pc once, this very laptop actually. 256 Mb ram and an old AMD sempron processor, I would click next then wait several hours before the next screen of the live installer appeared.
[05:24] <OpenSorce> rob, ouch!!
[05:24]  * ScottK is reading the scrollback and having trouble finding anything about Ubuntu development.
[05:25] <rob> I'd consider this laptop to be a perfect candidate for Linux too since Windows XP went to heck on it and I inherited it.
[05:25] <OpenSorce> ScottK, so good to see you again....it was quiet and I wanted opinions....so sorry to clutter the channel with off-topic discussion :-)
[05:26] <ScottK> We have #ubuntu-offtopic for that.
[05:26] <OpenSorce> ScottK, of course.....again...my apologies :-)
[05:26] <jdong> apart from low-RAM or slow-CD machines, I'd say a live evaluation CD is a very important feature for a distribution that would like to get people to switch from some other operating system
[05:27] <OpenSorce> rob, jdong, I'm going to move to #ubuntu-offtopic you are welcome to join me.....thanks again ScottK.....please continue your Ubuntu Devel discussions...
[05:31] <OpenSorce> Hobbsee, so nice to see you again, how are you?
[05:31] <Hobbsee> hiya
[05:31] <Hobbsee> pondering doing a talk in india, among other things
[05:32] <OpenSorce> Hobbsee, ah....I detest public speaking :-)
[05:32] <ScottK> Good afternoon (I think I did the TZ math right) Hobbsee.
[05:32] <Hobbsee> ScottK: indeed!  good morning to you!
[05:32] <Hobbsee> OpenSorce: so do i, somewhat, depending on what it's on :)
[05:32]  * Hobbsee managed not to have to get up and speak at all for UDS.
[05:32]  * lamont yawns, waves
[05:33] <Hobbsee> hiya lamont
[05:33] <ScottK> Hello there lamont.
[05:34] <ScottK> Any noise yet on when we'll be able to start uploading to Hardy?
[05:34] <lamont> ScottK: I haven't been paying attention
[05:34] <Hobbsee> ScottK: toolchain is going
[05:35] <lamont> OTOH, I'd expect that we want to let release/archive/etc have until monday or so to recover from the release.  (several back-to-back 20+ hour days do take a toll)
[05:35] <ScottK> That's good.  So far I've not gotten any FTBFS mails I didn't expect.
[05:35] <lamont> and I'm not sure where they're at in the checklist
[05:35] <Hobbsee> meh.  sleep is overrated.
[05:35] <ScottK> Sleep is for the weak.
[05:37] <OpenSorce> Seeya later guys
[05:37] <OpenSorce> ScottK, my apologies again :-)
[05:37] <ScottK> I've got a narrow window I need to catch for a bugfix.  It's not SRU worthy, but important.  There's already a newer version in Debian.  So I need to upload the bugfix and get it backported between when the repo opens and the first autosync.
[05:37] <Hobbsee> however, i did get pinentry-gtk-2 working.
[05:37] <Hobbsee> unsure why it's not standard in gnome.
[05:38] <ScottK> Hobbsee: They didn't do the same encryption by default stuff we did in Kubuntu AFAIK.
[05:38] <ScottK> pinentry was in Universe until I got that in.
[05:38] <Hobbsee> ScottK: seahorse is just weird!
[05:38] <Hobbsee> yeah, well.  i might have to fix that
[05:38]  * calc got rid of about 50 ooo bugs today
[05:38] <Hobbsee> calc: yay!
[05:38] <Hobbsee> now 100 more!
[05:38] <calc> heh the next 100 will be a bit more work ;)
[05:38] <Hobbsee> hmm, gnome is much smaller than kde.
[05:39]  * Hobbsee restarts X
[05:39] <calc> but uses more memory
[05:39]  * ScottK missed the transition from "0" to "o" there for a second and was really stunned.
[05:39] <calc> ScottK: lol
[05:39] <calc> ScottK: i know a way to get rid of that many... nuke LP ;)
[05:40] <persia> Regarding pinentry: in GNOME (not XFCE), seahorse-agent takes care of the GPG stuff.
[05:40] <ScottK> calc: Well given how the implemented the auto expiration stuff you ought to just file a bug and ask for it.  They may just close them all for you </bitter>
[05:41] <ScottK> persia: But isnt' that in Universe too?
[05:41] <calc> what auto expiration stuff?
[05:41] <persia> ScottK: Ah.  I missed the sense of things.  Apologies.
[05:41] <ScottK> They added a "feature" to auto expire bugs left incomplete to long.
[05:41] <Hobbsee> persia: yes, but seahorse *sucks*
[05:41] <Hobbsee> or at least, it doesnt do what i want
[05:41] <Hobbsee> persia: i cant seem to set it so that it asks for my passphrase the first time, and then keep it cached fro a set time, for ssh
[05:41] <calc> ScottK: ah cool
[05:41] <Hobbsee> whereas you can set pinentry to do exactly that, and it works for *ssh* and gpg
[05:42] <ScottK> Their initial implementation got just a "little" more than they planned to get.
[05:42] <Hobbsee> er, *and*, not *ssh*
[05:42]  * persia ceases to defend seahorse
[05:42] <ScottK> calc: Actually I think not.  For one the one size fits all timer works better for some things than others.
[05:42] <ScottK> I cuts down on LP useability for some projects.
[05:42] <ScottK> I/It
[05:43] <calc> ScottK: how long was the timer?
[05:43] <Hobbsee> persia: it's quite possible that i got the settings wrong, and it's really nice that it caches...but my user p/w is far less secure than my gpg and ssh passphrases (obviously), and so dropping down to that particular level of security is kinda unnerving.
[05:43] <calc> true if it just closes bugs regardless of their status that could be very bad
[05:43] <Hobbsee> whereas pinentry you do have to persuade to work, somewhat.
[05:44] <ScottK> calc: I may have managed to erase that fact from my brain, but I think 4 months.
[05:44] <calc> ok
[05:45] <ScottK> So far every bug I've seen it expire that I got bugmail for was a valid issue that ought not be lost, but that's just me.
[05:48] <persia> Hobbsee: I'm not sure you got your settings wrong.  I don't use seahorse for SSH, just GPG.
[05:49] <Hobbsee> persia: ahh.  then you're missing out.
[05:49]  * persia doesn't ssh much
[05:50] <superm1> hey Hobbsee you got a few for ~ubuntu-archive'y stuff?
[05:50] <Hobbsee> superm1: yes, but i'm limited in what i can do
[05:50] <superm1> Hobbsee, oh didn't sort out the part about announcing to $release-changes yet?
[05:51] <Hobbsee> superm1: no.  they wont fix that until late november.
[05:51] <Hobbsee> what were you after?
[05:51] <superm1> well accepting an SRU: bug 154985
[05:51] <ubotu> Launchpad bug 154985 in mythbuntu-control-centre "MCC fails on amd64 if medibuntu hasn't been used in the past" [High,Fix committed] https://launchpad.net/bugs/154985
[05:51] <superm1> into -proposed
[05:52] <ScottK> Good night all.
[05:53] <calc> is there a way to search bugs for any assignee other than nobody?
[05:53] <Hobbsee> superm1: ahh.  dont thik so, sorry
[05:53] <superm1> Hobbsee, no biggie, for now i'm just pointing amd64 users to a ppa until its in :)
[06:22] <Hobbsee> superm1: come to think of it - does -proposed actually mail anywhere?
[06:22] <Hobbsee> slangasek: might be able to do it, too
[06:23] <superm1> Hobbsee, well i think it still announces to gutsy-changes.  because when it goes into gutsy-updates, its just cross pocket copied, and not announced then
[06:24] <Hobbsee> superm1: ahh, kay.  then i'd better not touch it
[06:24] <Hobbsee> (sigh)
[09:01] <DShepherd> does anyone else thing it would be helpful to add a factoid to ubotu about the new appearance menu and whats located there? There seems to be a number of questions just related to find that appearance option much less the stuff under it
[09:02]  * Hobbsee suspects that's more of a question for #ubuntu-ops
[09:03]  * DShepherd takes Hobbsee suspected advice
[15:31] <frimjon> Hi guys.  I want to report something that could fall somewhere between policy and bug, it's my first report, I'm just not sure how to report it.
[15:31] <frimjon> It's about improving the error message in the Save dialog, whenever you save something with a forward slash it will give you a "file not found", I'd like to suggest that it be fixed to tell the user what the actual problem is (that they're using a slash) instead.
[15:32] <frimjon> Should I be unafraid to report that as a bug?
[15:33] <dsas> frimjon, be unafraid, be very unafraid
[15:33] <frimjon> Hee hee, alright, I'll go straight into the wilderness of Launchpadland.
[15:50] <frimjon> dsas: Actually, after some thought I found out that it really wasn't a bug, but rather the feature to allow paths in the file name (to save at that path instead of browsing) that's inevitably making shaky messages for those unfamiliar with the Linux file structure.  I can't see a proper way to remove that newcomer unfriendliness without changing something that veterans probably like.
[15:51] <Keybuk> mail ubuntu-devel-discuss, describe the perceived problem and why you think it should behave differently
[15:51] <Keybuk> (and also why you think it should behave like that)
[15:51] <Keybuk> other people might have ideas
[15:51] <Keybuk> a problem shared is a problem solved
[15:52] <frimjon> Keybuk: That's a great idea, Keybuk, thank you.
[15:52] <Keybuk> ubuntu-desktop might be a good alternative to ubuntu-devel-discuss
[15:52] <Keybuk> though it has fewer subscribers, they're probably able to give a better help
[15:53] <frimjon> Okay, I'll check that out.  Thanks again.
[16:13] <popey> is there a way to determine why a package that was in dapper through feisty, isn't in gutsy? jpilot-syncmal is the one in question
[16:15] <Hobbsee> popey: check the blacklist for why it got removed.  check if the source is there, but hasnt built.  check if the binary has a new name.
[16:16] <lamego> where is that blacklist ?
[16:16] <popey> glad you asked that
[16:17] <Hobbsee> hmmm...off people.ubuntu.com/~ubuntu-archive/
[16:17] <popey> i see no pages mentioning the package on the wiki
[16:17] <Hobbsee> no, the wiki isnt used to track such things
[16:17] <Hobbsee> popey: is it a package from debian, or only in ubuntu?
[16:17] <lamego> http://people.ubuntu.com/~ubuntu-archive/sync-blacklist.txt this one ?
[16:17] <Hobbsee> lamego: looks good
[16:17] <popey> it's not listed
[16:17] <Hobbsee> lamego: of course, it will only show up on there if it's in debian too
[16:18] <lamego> right, sync blacklist
[16:18] <popey> it is in sid
[16:18] <Hobbsee> popey: do the launchpad bugs show anything interesting?
[16:19] <geser> http://people.ubuntu.com/~ubuntu-archive/removals.txt mentions it: "(From Debian) RoM; FTBFS since libmal-dev is no more available"
[16:20] <popey> that's helpful, thanks
[16:20] <Hobbsee> oh, that's the one i wanted.
[16:20] <lamego> what is the removals.txt purpose ?
[16:20] <Hobbsee> ....
[16:20] <Hobbsee> to document what's been removed, and why?
[16:20] <geser> Debian has it only on oldstable
[16:20] <popey> yeah
[16:20] <geser> s/on/in/
[16:21] <lamego> I am lost, that means, it will be synched for the next release ?
[16:21] <popey> (the reason I ask is the question has been asked in a lp answers post)
[16:21] <Hobbsee> popey: FYI, RoM is "request of maintainer"
[16:21] <Hobbsee> popey: ie, because it doesnt build anymore.
[16:21] <popey> also helpful, thanks Hobbsee
[16:21] <geser> lamego: no, as it got removed in Debian too
[16:21] <lamego> ah ok
[16:21] <Hobbsee> lamego: no, it means it didnt build in debian, so the maintainer asked for it to be removed.
[16:22] <popey> thanks everyone
[16:23] <lamego> geser, Hobbsee for how long are you working with debian/ubuntu packaging ?
[16:23] <Hobbsee> lamego: hmm.  a year and 3/4?
[16:24] <lamego> ok, just profiling :)
[16:24]  * popey hands Hobbsee ¾
[16:24] <Hobbsee> lamego: it helps to learn the acronyms, and i've got an interest in archive admin stuff
[16:24] <Hobbsee> so might tend to know more than most
[16:24] <geser> lamego: my first sponsored upload is around 14 months ago
[16:25] <Hobbsee> popey: thanks. i dont have those funky keys on my keyboard.
[16:25] <Hobbsee> (and so ignore symbols too)
[16:25] <StevenK> Hobbsee: That would have been using a compose key
[16:25] <popey> Alt+Gr + 6 = ¾
[16:25]  * Hobbsee wonders what Gr is
[16:25] <popey> Graphics ?
[16:25] <StevenK> It's a growly Alt, duh
[16:25] <StevenK> Hum.
[16:25] <lamego> I am trying to estimate how long I will take to have an average know-how :P
[16:25]  * StevenK can't find his Compose key
[16:26] <Hobbsee> okay, maybe i should have asked *where* it is
[16:26] <StevenK> (Which is what AltGr is usally mapped as)
[16:26] <Hobbsee> lamego: depends.  people have their specialties
[16:26] <StevenK> Hobbsee: AltGr is right Alt
[16:26]  * popey specialises in ☻
[16:27] <lamego> Hobbsee, sure, but regardless of that, you need a certain time to get a broader knowledge
[16:27] <Hobbsee> interesting.  it tehn takes me to window 6
[16:27] <Hobbsee> lamego: true.  in which case, a couple of release cycles.  more than one.
[16:29]  * geser has Compose on the menu-key
[16:30] <StevenK> I've never understood how to bind keys in X.
[16:30] <pitti> soren: FYI, I'll do the mutt merge; it's a tradition :)
[16:30]  * Hobbsee closes a couple of bugs
[16:31]  * pitti hugs Hobbsee
[16:31] <StevenK> Hey pitti
[16:31] <pitti> moin StevenK
[16:31] <Hobbsee> right, no more bugs for that source package
[16:31] <luk_> StevenK: xbindkeys might help
[16:32] <pitti> soren: oh, nevermind, it can be synced
[16:33] <geser> StevenK: either do it through gnome-keyboard-properties or through the right option in xorg.conf (for Compose)
[16:34] <StevenK> I suppose I have to restart X for that option to work
[16:36] <StevenK> steven@liquified:~% tracker-status
[16:36] <StevenK> zsh: segmentation fault (core dumped)  tracker-status
[16:36] <StevenK> Tracker, please jump off a cliff. kthxbye
[16:37] <luk_> System->Preferences->Keyboard Shortcuts works fine in Gnome
[16:37] <StevenK> luk_: Oh, absolutely, but the key doesn't work, I suspect I have to restart X.
[16:40] <StevenK> pitti: What's that -Wl,--as-needed love page you were telling me about?
[16:42] <norsetto> stevenk: this http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html under 9.1 ?
[16:48] <leleobhz> someone can explain me how the package restricred drivers are generated?
[16:48] <leleobhz> because i want to make a updated kernel package but im getting trouble with restrited modules
[17:18] <soren> pitti: Oh, sorry about that. I didn't know :) I already filed a sync request.
[17:19] <soren> pitti: I was actually referring to mutt when I asked on Friday if it was ok to file sync requests now.
[17:19] <pitti> soren: NP, I checked
[17:19] <phillips321> hi guys, any1 here?
[17:20] <soren> phillips321: Er.. Yes? 226 of us, actually :)
[17:20] <phillips321> what options are available for someone who wishes to use full hdd encryption but also be able to remotely reboot a box?
[17:20] <soren> None that I know of.
[17:20] <phillips321> i would like to try the 7.10 encryption but i'm riddled with needing physical access to reboot a box
[17:21] <phillips321> it's a pain, im thrying to think of other options like partition encryption and then mouting once booted
[17:21] <soren> You can hack something together with a tiny partition only used to boot and ask for the password, mount the real root and chroot your way into that, but it's not something we support. I'm just making it up right now.
[17:22] <phillips321> ive thort about that, /boot and / not encrypted and only encrpting the /home partition
[17:22] <phillips321> but i might not be able to boot correctly if my /home partition cant be found...
[17:23] <soren> Why not?
[17:23] <superm1> pitti, would you be able to release something into gutsy-proposed for me?
[17:25] <phillips321> guess it's something i shud try....
[17:52] <soren> Is there any way to see packages that have been uploaded to hardy, but not accepted yet?
[17:59] <Mithrandir> soren: http://people.ubuntu.com/~ubuntu-archive/queue/hardy/unapproved/
[18:00] <soren> Mithrandir: That wasn't there 10 minutes ago, was it?
[18:00] <soren> Or am I going loony?
[18:00] <Mithrandir> soren: no, it wasn't. :-)
[18:01] <soren> phew..
[18:01] <soren> Thanks!
[18:01] <Mithrandir> publish-queue isn't smart enough to DTRT when we start publishing new distroreleases.
[18:01] <Mithrandir> so it requires a little bit of handholding, aka mkdir

[18:03] <alex-weej> asac: spare a couple of mins to talk about NM?
[18:03] <Mithrandir> I should rewrite p-q to be a) faster and b) smarter, but just haven't had the time yet.
[18:03] <Mithrandir> that'd make queuebot more useful too
[18:05] <soren> Mithrandir: I actually really have no idea what either of those do, to be honest. :)
[18:06] <Mithrandir> soren: publish-queue is the script that pushes the queue from the ftp-master to p.u.c/~u-a/queue, queuebot looks at a status file and tells us on IRC when there's a new queue item there.
[18:07] <soren> Mithrandir: Hm? Which channel?
[18:44] <soren> Mithrandir: Does it perhaps /msg the archive team?
[18:47] <Mithrandir> soren: #ubuntu-release
[18:47] <soren> Mithrandir: Shiny.
[18:47] <Mithrandir> not that there's much going on there outside of release times.
[18:51] <Dekans> what's the matter with nvidia drivers ?
[18:51] <Dekans> several people just can't have 3D acceleretion on gutsy
[18:52] <Dekans> are nvidia-glx and nvidia-glx-new broken ?
[18:52] <Dekans> is it l-r-m ?
[18:53] <soren> linux-restricted-modules
[18:55] <Dekans> ok, so they have to wait for an update of it
[18:55] <Dekans> :/
[19:17] <lamego> Dekans, I have no problem with the nvidia driver
[19:22] <Dekans> when i upgraded to gutsy, i installed succesfully nvidia-glx
[19:22] <Dekans> but no X server at reboot
[19:22] <Dekans> I instelled the .run binary from nvidia.com
[19:23] <Dekans> a fe days later, no X server again
[19:23] <Dekans> I removed this driver and reinstalled nvifia-glx
[19:23] <Dekans> and it works...
[19:23] <Dekans> but several people cannot use it on gutsy
[19:23] <Dekans> at all
[19:30] <lamego> I am using nvidia-glx-new, without any issues
[19:30] <asac> alex-weej: sure
[19:31] <alex-weej> oops sorry, bad timing
[19:31] <alex-weej> need to cook
[19:31] <alex-weej> ttyl
[19:31] <asac> alex-weej: hehe ... ok
[19:33] <Dekans> but some people cannot ahve 3D
[19:33] <Dekans> have*
[19:41] <Dekans> so no fix planned :(
[19:44] <Karnaugh> Dekans: blame the manufacturers
[19:45] <Dekans> it seems to be a issue related to l-r-m
[20:20] <lamego> hello, anyone will an nvidia card and 3d enabled that could help me with a test ?
[21:02] <blueyed> lamego: yes
[21:02] <lamego> bluekuja, sudo apt-get install snowballz
[21:02] <lamego> snowballz
[21:03] <lamego> I am getting: Major opcode of failed request:  135 (XFree86-VidModeExtension)
[21:05] <blueyed> lamego: works for me (nvidia-glx-new, Club3D 6600GT)
[21:06] <lamego> hum
[21:06] <lamego> I am using nvidia-glx
[21:07] <lamego> no, i have the new
[21:08] <lamego> a google for the error gave me the idea it was related to the nvidia driver, but it could be also with the display setup, for the video mode switching
[21:18] <bluekuja> lamego, huh?
[21:19] <lamego> the X Error of failed request:  BadValue (integer parameter out of range for operation), on the set video mode function
[21:19] <lamego> which is what I am getting when launching the game
[21:22] <attunix> What libraries are needed to develop in QT?
[21:26] <lamego> libqt4-dev ?
[21:26] <attunix> thanks
[21:53] <mekius> bryce: Hey, was wondering if you had any estimate on the inclusion of Xorg 7.3?
[21:53] <Kmos> mekius: try to ask that tomorrow
[21:54] <mekius> ok :)
[21:55] <mekius> Kmos: didn't really need an answer right away, just throwing it out there
[22:36] <ec158148> hi all, i don't seem to have the manpage for scanf
[22:36] <ec158148> could somebody guess as to why?
[22:36] <azeem> ec158148: please ask in #ubuntu
[22:36] <ec158148> ok
[22:37] <ec158148> thanks
[23:53] <bryce> mekius: I do
[23:53] <bryce> mekius: in fact timo has just done the xorg merge and is getting ready to upload it; xserver is either done or to be done soon
[23:54] <bryce> mekius: also if you're interested, I've prepared a Ubuntu-X project list at http://wiki.ubuntu.com/X/Projects
[23:55] <bryce> essentially, the plan is to get all the Xorg 7.3 bits incorporated as soon as Hardy is open for business
[23:57] <bryce> mekius: I personally am probably going to stay focused on bugs a bit, as there's several I'd like to -sru for Gutsy (esp. -ati and -intel)


[13:26] <gary_poster> ok, in addition to having my opinion of System 76 machines reinforced, now my opinion of Dell machines is reinfirced. :-/
[13:32] <rick_h_> gary_poster: +1 all the way around
[13:32] <gary_poster> :-/
[13:33] <rick_h_> at least in laptop land
[13:33] <gary_poster> That was what I was thinking--if I got a desktop I'd be fine
[13:33] <gary_poster> No such luck this time around, anyway
[13:33] <rick_h_> yea, I did go with system76 for a desktop and ok. Laptops though I'm still not a fan yet. Seen too many issues and build isn't as solid as I'd like
[13:34] <gary_poster> I don't know who to use for desktops now.  Laptops I'm Apple, and Lenovo otherwise, from here on out until convincing evidence is given. :-)
[13:35] <rick_h_> that's what I've got written down (reverse order)
[13:36] <gary_poster> heh
[14:01] <gary_poster> frankban, hey.  replied to Wm's email about the GUI authentication issues.  Curious about your thoughts, including whether you'd like to set up a meeting with him to explore more.
[14:01] <frankban> gary_poster: looking
[14:02] <gary_poster> ty
[14:04] <hatch> morning
[14:04] <rick_h_> party
[14:05] <gary_poster> hiya
[14:19] <hatch> is there a way to get askUbuntu to email me every time something happens on a thread I've interacted with?
[14:24] <hatch> This weekend I found myself wanting 'to' functionality in the GUI
[14:25] <hatch> because quickstart is in juju-stable will it be in universe in 14.04?
[14:26] <rick_h_> it was a goal I thought so that it helps you get juju installed
[14:26] <hatch> I was thinking that it NEEDS to be in there haha, the quickstart story i just too awesome not too
[14:27] <rick_h_> yea, jcastro showed it off and had some <3 for it end of last week
[14:27] <hatch> `apt-get install juju-quickstart && juju-quickstart ghost-bundle-simple` is an awesome story
[14:28] <rick_h_> yep
[14:58] <frankban> hatch: I just sent an email about oddities I've found while working on the server side basic HTTP auth for the putCharm functionality. Could you please take a look?
[14:59] <hatch> yup reading it now
[15:06] <hatch> frankban just to clarify - does option 1 work in firefox 100% of the time?
[15:06] <hatch> or does it also fail the first time
[15:07] <gary_poster> also fails first time, according to email
[15:08] <frankban> gary_poster, hatch: right, also first time
[15:08] <hatch> hmm
[15:08] <hatch> looking into this
[15:09] <frankban> hatch: thank you, it would be nice if you are able to reproduce that
[15:09] <hatch> I'd need the charm, have you uploaded the version where this is happening?
[15:10] <gary_poster> frankban: looking for bugs.  so far only found http://stackoverflow.com/questions/9459017/xmlhttprequest-authentication-not-working-in-firefox : 2012, so old, and no resolution.
[15:12] <gary_poster> frankban: OPTIONS call? http://stackoverflow.com/questions/19234892/xmlhttprequest-based-cors-call-with-basic-auth-fails-in-firefox-and-chrome
[15:13] <gary_poster> worth investigating charm log at least
[15:13] <hatch> that should only be required cross domain
[15:14] <frankban> hatch: lp:~frankban/charms/precise/juju-gui/http-proxy is what I have now. It would be nice if we can dupe that excluding the proxy, to ensure this is not a problem on the gui server side. e.g. pointing the GUI directly to the core API server
[15:14] <hatch> frankban I'm pulling down the charm now and will give it a go
[15:14] <gary_poster> true
[15:14] <gary_poster> hatch, frankban, but charm log coudl be informative
[15:22] <hatch> frankban the env is spinning up, I'll keep you posted
[15:24] <bac> hey rick_h_ can you review https://pastebin.canonical.com/103628/plain/ before i submit the RT to see if i forgot anything?
[15:24] <rick_h_> bac: looking
[15:25] <bac> rick_h_: i've verified there is no impact on CI so the window where qa and staging point to the same machine is unnecessary
[15:25] <rick_h_> bac: so we verified we can keep that IP if we have to rebuld staging/qa?
[15:25] <rick_h_> bac: that's the only part I have questions on in that. Looks good otherwise.
[15:26] <rick_h_> bac: I don't know how staging. is currently handled with a rebuilt/keeping the IP in canonistack
[15:26] <bac> rick_h_: we currently control the IP used by staging.j.c.  it is assigned in the deploy script to the apache instance.  the revno is subsequently updated by using juju, so the FQDN is never used again.
[15:26] <rick_h_> bac: ah ok then
[15:27] <bac> so the name can change and no one notices or cares, except those of us who want to hit it
[15:27] <rick_h_> right
[15:27] <bac> ok, i'll submit pretty much as is.  i just didn't want to file an RT with obvious holes.
[15:28] <rick_h_> bac: yea, looks like what we talked about here
[15:28] <bac> simplified
[15:28] <rick_h_> right, because we control the IP address it makes things easier?
[15:29] <bac> rick_h_: well because the name 'staging' is not used in any of the CI machinery
[15:30] <rick_h_> bac: right cool
[15:36] <bac> gary_poster: do we have a departmental meeting with IS?
[15:37] <gary_poster> bac, every other thursday.  cancelled this week because they are out.  Do you have somethng to raise?
[15:38] <hatch> vim's recording 'feature' has to be the under the worst key possible lol
[15:38] <bac> gary_poster: yeah, i filed an RT for getting staging on prodstack.  asked spads what else to do to get it scheduled and he said to raise it in that meeting.
[15:38] <gary_poster> heh, it has bitten me more than anything else in vi as well, yes, hatch
[15:38] <bac> gary_poster: i don't think we want to wait 2.5 weeks to get it on the radar
[15:39] <gary_poster> bac ack. I can ask mramm to escalate to robbiew, who can set priority.  gimme rt?
[15:39] <bac> gary_poster: RT 67257
[15:39] <gary_poster> bac, ok. will cc you.
[15:40] <bac> thanks
[15:41] <gary_poster> bac, staging.jujucharms.com is confusing naming IMO and FWIW.  staging.manage.jujucharms.com?  managestaging.jujucharms.com?  ugh, I know, but we will probably want staging for GUI jujucharms also, unless it is wiped out in favor of other sites soon.
[15:42] <gary_poster> that's not important for me escalating--just a comment/thought
[15:42] <bac> gary_poster: good point
[15:45] <frankban> gary_poster: I am still debugging. re: GUI/quickstart auth, I like your idea, a command like that can be used also by quickstart. curious to see if they come up with other ideas
[15:45] <gary_poster> cool frankban thx
[15:45] <bac> gary_poster: ok, i'll modify to request staging.manage.jujucharms.com and qa.manage.jujucharms.com.  what a mouthful.
[15:45] <hatch> frankban ok I finally got this thing up and running and am getting a 400 when trying to upload the charm
[15:46] <gary_poster> :-) k thanks
[15:47] <rick_h_> gary_poster: bac in the prioritizing, can we keep the 'move jujucharms to juju-core' above this?
[15:47] <gary_poster> rick_h_: ack, +1.  rt please?
[15:47] <bac> rick_h_: +1
[15:47] <frankban> hatch: 400? how did you create the zip?
[15:47] <rick_h_> gary_poster: 67167
[15:47] <rick_h_> thanks
[15:48] <frankban> hatch: FWIW, the charm files must be at the root of the zip, e.g. it does not work if you compress the charm dir
[15:48] <gary_poster> thanks rick_h_.  bac, rick_h_, I suggest making RT links on the kanban cards if you have not already
[15:48] <rick_h_> gary_poster: yep, full link is there
[15:48] <gary_poster> ack thanks, soory I missed it
[15:48] <hatch> frankban I downloaded the zip from github for my ghost charm
[15:48] <hatch> frankban I pinged you the url
[15:50] <frankban> hatch: what are the zip contents? does it create a root dir when you decompress it?
[15:50] <hatch> frankban well would that give me a 400 if they weren't?
[15:51] <hatch> what should I look for in the charm to make sure I have the proper one deployed?
[15:51] <frankban> hatch: what's the content of the response body?
[15:51] <hatch> {"Error":"invalid charm archive: bundle file not found: metadata.yaml"}
[15:52] <gary_poster> well there ya go ;-)
[15:52] <frankban> hatch: exactly, metdata.yaml must be at the zip root level.
[15:52] <rick_h_> hah
[15:52] <hatch> ok that's not going to work
[15:52] <frankban> hatch: so you need to create another zip to test it
[15:52] <hatch> will do
[15:52] <hatch> buut we will need to allow it to be nested one folder deep
[15:53] <gary_poster> methinks that dragging a folder (and having us figure out what to zip) will be much less fiddly for users
[15:53] <rick_h_> +1
[15:53] <frankban> +1
[15:54] <rick_h_> though I think the idea of wget xxx.zip and deploy it will be more adminy-useful.
[15:54] <rick_h_> kind of like bundles where they're getting sent around via email you can more easily link/share a local/dev charm as a single file
[15:55] <rick_h_> jujugui call in 5?
[15:55] <gary_poster> bah thank you
[15:56] <hatch> frankban works with a single request in chrome
[15:57] <frankban> hatch: how do you see that it's a single request?
[15:57] <hatch> just looking in the network tab
[15:57] <hatch> looking in the charm logs now
[15:58] <frankban> hatch: ok
[15:58] <frankban> hatch: /var/log/upstart/guiserver.log
[15:58] <gary_poster> jujugui call in 2
[16:01] <gary_poster> Makyo pingy
[16:01] <hatch> frankban ok I see the two requests in the guiserver logs
[16:01] <hatch> after the call I'll try firefox
[16:01] <frankban> hatch: cool
[16:12] <hatch> frankban unfortunately I can reproduce your issue with Firefox but Chrome works 100% of the time
[16:13] <frankban> hatch: Firefox version?
[16:14] <hatch> frankban OSX 26.0
[16:15] <hatch> it has the issue, open firebug, works no problem :/
[16:15] <frankban> hatch: re python gcc errors: try installing libpython-dev, if that fixes the issue please add it o sysdeps
[16:15] <hatch> uable to find package
[16:16] <frankban> hatch: libpython2.7-dev
[16:17] <frankban> ?
[16:19] <hatch> frankban https://gist.github.com/hatched/8651673 these are all the packages I have available
[16:20] <frankban> hatch: just python-dev?
[16:21] <hatch> installing
[16:21] <hatch> hah
[16:21] <frankban> hatch: so, were you able to dupe the problem in FF?
[16:21] <hatch> frankban yes, now trying to track down the issue because clearly this is unacceptable
[16:22] <frankban> hatch: cool thanks, weird the firebug thing
[16:22] <hatch> yeah....and you were saying that the same issue happens with option 2?
[16:23] <frankban> hatch: yes, with option 2 FF just refuses to include the auth header in the first request
[16:23] <frankban> hatch: but you can dupe that too switching to juju-gui-debug=true and applying that diff
[16:24] <hatch> yeah, I'll take your word for it for now, just doing some research
[16:24] <frankban> hatch: I'd be curious to see what's the IE behavior
[16:24] <hatch> I can spin IE up after my next call
[16:25] <hatch> unfortunately I feel like I'm coming down with a cold so brain is moving a little slow haha
[16:27] <frankban> heh
[16:28] <hatch> frankban ok I'm going to apply the diff and see option 2 - firefox strips the auth headers unless the server responds with a 401, it then should make another request with the headers
[16:29] <frankban> hatch: so firefox don't trust us
[16:29] <hatch> it doesn't :) but it SHOULD be making the second response after the guiserver responds with the 401
[16:29] <hatch> but it doesn't appear to be doing so unless firebug is open
[16:31] <gary_poster> luca_: https://plus.google.com/hangouts/_/canonical.com/discuss-local ?
[16:32] <gary_poster> rick_h_: Makyois sick
[16:32] <luca_> gary_poster: thank you :)
[16:32] <gary_poster> welcome :-)
[16:32] <hatch> frankban I guess a hacky workaround is to have it try twice :/
[16:33] <rick_h_> gary_poster: ok, thanks for the heads up
[16:43] <frankban> hatch: I think we are hitting https://bugzilla.mozilla.org/show_bug.cgi?id=901342
[16:45] <frankban> hatch: if you send a string in place of the zip file, the second request is correctly executed. Also note that the firebug network tab is mentioned in the bug comments too :-/
[16:46] <hatch> frankban hah, in call, will read in a bit
[17:08] <hatch> frankban ok off call, reading now
[17:09] <hatch> frankban I would agree that's the same bug
[17:09] <frankban> hatch: yeah, tried changing the GUI to send a random string and the second POST request is corretcly sent by firefox
[17:09] <hatch> ok, so....workaround is to try multiple times?
[17:10] <hatch> I'll also add the most recent version of firefox to that bug
[17:10] <hatch> yuck I hate writing hack code to workaround bugs
[17:10] <hatch> bleh
[17:11] <hatch> frankban I'm spinning up a windows 8 vm to test there
[17:12] <frankban> hatch: sending the file contents?
[17:12] <hatch> frankban well we try once, if it doesn't resolve to 200 in x seconds then try again
[17:13] <hatch> that 'should' workaround the firefox issue
[17:13] <frankban> hatch: 200 or 400 or 500...
[17:15] <frankban> hatch: and now IE... at least it seems the proxy works well
[17:16] <hatch> yes we'll need to check those other responses as well.
[17:16] <hatch> yep testing Ie now
[17:16] <hatch> yeah the proxy seems to work just fine :)
[17:17] <jcsackett> hey juju-gui, is bac likely to be back online today? have some questions about some ingest code of his.
[17:18] <rick_h_> jcsackett: should be
[17:18] <rick_h_> jcsackett: his interwebs hate him
[17:18] <hatch> frankban it looks like Windows can only (natively) turn a folder into an archive so if the charm has to be the root in the zip then that's not a very good story in Windows. This was a limitation of the juju-core implementation?
[17:18] <jcsackett> rick_h_: awesome. i'll shoot him an email then so he and i can link up whenever he's back.
[17:18] <jcsackett> thanks.
[17:21] <frankban> hatch: yes, we can propose core devs to change the API like the following: if the zip root includes only a directory, assume the charm is included in that directory. the directory name should not be relevant
[17:21] <hatch> right ok good I'll file a bug to that effect
[17:21] <frankban> hatch: cool thnaks
[17:22] <hatch> at the moment I'm having issues with my ie vm connecting to my juju instance
[17:22] <hatch> sorry for the delay
[17:22] <frankban> hatch: np
[17:22]  * rick_h_ goes to have a lunch shoveling snow while he waits for his snow blower to arrive
[17:22] <hatch> lol
[17:24] <frankban> hatch: FYI I noticed that if an error occurs core returns a 400 code and the details can be found in the response body. we need to handle that case, maybe just adding an error notification
[17:24] <hatch> ok sounds good, I wasn't entirely sure the structure of the response but now that we have it it's easy to check for.
[17:24] <frankban> sure
[17:38] <hatch> ugh I hate Windows
[17:38] <hatch> I can't seem to get this tunnel to work
[17:56] <hatch> yay finally got the tunnel to work
[17:56] <hatch> should have known to just done it in the host
[18:06] <hatch> frankban  just FYI it looks like there is an issue with the .zip upload in IE but the inspector is....well it's the IE inspector lol
[18:31] <hatch> frankban  here is the error from IE when I try to upload a zip https://gist.github.com/hatched/b80599004f52d3464458 does this look like an error from juju-core/guiserver? The IE inspector is being pretty useless so I'm having a hard time tracking it down
[18:34] <hatch> gary_poster https://bugs.launchpad.net/juju-gui/+bug/1273363 IE11 show non-supported browser window....I'll let you decide if this is an issue or not :)
[18:34] <_mup_> Bug #1273363: Non-supported browser warning on IE11 <juju-gui:New> <https://launchpad.net/bugs/1273363>
[18:34] <gary_poster> hatch: does everything else work?
[18:35] <gary_poster> hatch, nm: I will add IE 11 support to huw's list, and see if he's willing :-)
[18:35] <hatch> gary_poster nope there are some d3 issues
[18:35] <hatch> at least that's all I've found
[18:35] <gary_poster> hatch, darn.  ok thanks
[18:36] <hatch> so it IS broken so that's a good thing the warning is there
[18:36] <gary_poster> yup
[18:36] <gary_poster> though we should maybe suggest IE 10 also :-)
[18:38] <hatch> yeah that's probably a good idea
[18:41] <hatch> frankban ok I've figured out why IE doesn't work for dropping the zip.... IE calls zips "application/x-zip-compressed" not "application/zip"
[18:42] <Makyo> Ugh.  Alright.  Half-here.  Will be all-here once meds kick in.
[18:43] <rick_h_> Makyo: hey, good meds I hope. If you get a sec would appreciate a pointer to the location of the code you reference in the reafctor card for "Finding the real position from canvas coordinates"
[18:43] <rick_h_> Makyo: my git-fu is failing to find something promising
[18:43] <Makyo> rick_h_, sure thing!  One sec.
[18:44] <frankban> hatch: uhm, thanks for investigating
[18:44] <hatch> frankban I'll take over getting the fix landed for that
[18:45] <hatch> frankban after adding python-dev I was also able to get make check to run on quickstart thanks
[18:45] <hatch> so-much-multitasking
[18:45] <frankban> hatch: cool, :-)
[18:46] <hatch> frankban maybe 2h before our daily tomorrow you can give me a walk through of the execution order of quickstart?
[18:49] <hatch> 3 vm's running and this thing is still humming along
[18:49] <hatch> vroom vroom
[18:49] <Makyo> Oh for pete's sake.
[18:58] <jcsackett> bac: can you look at https://code.launchpad.net/~jcsackett/charmworld/fix-trigger-test-criteria/+merge/203401
[18:58] <bac> jcsackett: sure
[18:58] <jcsackett> thanks.
[19:04] <bac> jcsackett: done and thanks.
[19:26] <hatch> rick_h_ it looks like your neighbours across the street are lazy at snow removal :)
[19:27] <rick_h_> hatch: heh, he's got a giant john deere two stage thrower. I think he waits for it to get high enough to be able to use his beast and then just does 3 passes and calls it a day
[19:27] <hatch> lol
[19:28] <rick_h_> and when I see him out I beg him to run his giant machine in front of the mailbox
[19:28] <hatch> community mail there?
[19:29] <rick_h_> ?
[19:29] <rick_h_> we all have a mailbox and mail person that delivers each day
[19:29] <rick_h_> not sure what makes community mail or what other options there are
[19:30] <hatch> ohh now I See, sorry I didn't look close enough
[19:33] <hatch> rick_h_ the new areas here have a single mailbox which you have to walk to instead of curbside or at the door mailbox
[19:33] <hatch> is what I meant about a community mail
[19:33] <rick_h_> ah, yea that would stink
[19:33] <bac> benji, rick_h_: i've added a note regarding the deployment issue to our google doc with the rollout instructions. please be aware of it if you request a deploy in the near future.
[19:34] <rick_h_> bac rgr
[19:34] <benji> k
[19:34] <bac> rick_h_: sadly deej is not going to be around to work on it this week.  :(
[19:34] <hatch> rick_h_ haha I agree it would
[19:35] <rick_h_> bac: bummer, hate this stuff hanging over our heads
[19:36] <bac> yep
[20:20] <hatch> I wonder if juju will run in a vagrant instance
[20:21] <rick_h_> hatch: they've got images for that
[20:21] <rick_h_> hatch: http://blog.utlemming.org/2013/12/beta-cross-platform-juju-development.html
[20:22] <hatch> cool I'll have to check those out. Until I can get an on-metal version of Ubuntu working vagrant images seem like the most efficient way of working on various juju bits
[20:22] <hatch> actually, even after I do it would probably still be the best
[20:24] <hatch> mdn.microsoft.com now requires you to log in to read the docs.... FAIL
[20:24] <hatch> msdn that is
[20:31] <rick_h_> jujugui review please https://github.com/juju/juju-gui/pull/87 I think I found the code Makyo was referring to. Makyo if you're up for a review would appreciate your eyes to make 100% sure it's the right things.
[20:31] <Makyo> Yep, on it rick_h_
[20:32] <bac> man, ignore your trusty vm for a few days and there is hell to pay.  so much updating.
[20:32] <rick_h_> bac: hah, tis true
[20:32] <bac> it's like one of those damned japanese toys you have to feed
[20:32] <rick_h_> just hope it didn't die from neglect and now it can't come back to life
[20:33]  * rick_h_ updated the laptop to trusty this weekend so out of stable machines.  Just got lxc juju working today with the 'manually create /etc/lxc/auto' trick and latest golxc
[20:37] <rick_h_> hazmat: other than that been fine
[20:38] <bac> hatch: hah, i use the squirt bottle i bought from sunglasses hut for $5 b/c they promised free refills and a microfiber.  luckily there is SG Hut 1/4 mile from here so i will make them refill that sucker until i get my money's worth.
[20:38] <hazmat> rick_h_, cool, good to hear. i'll probably wait few weeks, but planning on diving early
[20:39] <bac> that said,i think windex and a rag works really well
[20:39] <hatch> haha ok, so some diluted rubbing alcohol it is then! I was going to try the same but I wasn't sure....apple and all haha
[20:39] <rick_h_> hazmat: yea, laptop was kind of on rarind and ran into some issues with old python so jumped
[20:39] <rick_h_> raring
[20:40] <bac> hatch: it's just glass.
[20:40] <bac> well, sort of
[20:40] <hatch> bac no it's squishy
[20:40] <hatch> I thought it was glass too
[20:40] <hatch> haha
[20:40] <rick_h_> hatch: it's magic apple glass. You have to take it to an apple store for cleaning or void your warranty :P
[20:40] <hatch> rofl
[20:40] <hatch> I wouldn't put it past them
[20:49] <bac> rick_h_: is this the problem with lxc/trusty that was supposedly solved: ERROR Get http://<IP_ADDRESS>:8040/provider-state: dial tcp <IP_ADDRESS>:8040: connection refused
[20:50] <rick_h_> bac: no, that's a failed old environment. rm your .juju/environments/local.jenv I think
[20:51] <bac> i don't have one of those
[20:51] <rick_h_> bac: also make sure `sudo lxc-ls` is clear of any lingering units
[20:51] <bac> it is
[20:51] <bac> :)
[20:51] <rick_h_> bac: is anything in .juju/environments?
[20:51] <bac> wait it was local.jenv
[20:51] <bac> thanks
[20:52] <rick_h_> cool
[20:52] <rick_h_> bac: and then sudo mkdir /etc/lxc/auto
[20:52] <rick_h_> will fix the last issue I had today
[20:52] <bac> already did that
[20:52] <rick_h_> k
[21:59] <huwshimi> Morning
[21:59] <gary_poster> morning
[21:59] <hatch> ahoy huwshimi
[22:13] <hatch> sweet charm upload now works in IE11
[22:14] <hatch> that was kind of a pita to debug, but the new IE11 debugger is leagues ahead of it's predecessor
[22:14] <hatch> jujugui looking for a review https://github.com/juju/juju-gui/pull/88 no qa necessary
[22:15] <gary_poster> cool hatch.  any result on the FF issue?  I didn't see a resolution
[22:15] <gary_poster> I will review
[22:17] <hatch> gary_poster we ran into what we think is this bug https://bugzilla.mozilla.org/show_bug.cgi?id=901342 but with the changes to fix IE appear to have fixed FF, I'm going to have to spin up my other ubuntu vm to check there too
[22:18] <gary_poster> hatch, so you mean the auth headers sem to have fixed FF?
[22:18] <hatch> I find when I open certain vm's together it kernel panics so gota do all this in order haha
[22:18] <gary_poster> heh\
[22:18] <gary_poster> I saw the bug from frankban's email, yeah
[22:18] <hatch> gary_poster yeah, they are now working first time every time in OSX
[22:18] <hatch> OSX FF that is
[22:18] <gary_poster> awesome
[22:18] <hatch> Chrome always worked
[22:19] <hatch> IE11 required them....even though there is absolutely nothing wrong with how we were doing it before
[22:19] <hatch> :/ IE
[22:19] <gary_poster> hatch +1 with ultra trivials.  Only downside to new setup is that making small changes feels so expensive now. :-(
[22:19] <hatch> but hey....if it works better...yay
[22:19] <gary_poster> definitely yay
[22:21] <hatch> lots of moving parts for sure - not to mention the required setup to build custom juju, custom charm, custom branch lol
[22:21] <hatch> I wish I had a vm with IE10 still....but it looks like Win 8 just auto updated me to 11
[22:21] <hatch> maybe that's a good thing, everyone else with IE10 will be running 11
[22:22] <gary_poster> heh ok
[22:24] <hatch> so the gui charm is using the tornado web server?
[22:24] <gary_poster> yes
[22:25] <hatch> well the good news is that it works properly according to the basic auth spec....unfortunately browsers don't haha
[22:49] <hatch> gary_poster the auth headers appear to have fixed it in Ubuntu FF which is odd because Francesco said that wasn't the case....but I'm sure he will test it again while working on the charm


[02:59] <barry_> #startmeeting
[02:59] <MootBot> Meeting started at 20:59. The chair is barry_.
[02:59] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[02:59] <barry_> mootbot!
[02:59] <barry_> hello everybody and welcome to this week's asiapac reviewers meeting
[02:59] <barry_> who's here today?
[03:00] <barry_> anybody?
[03:01] <barry_> jml, mwhudson, thumper ping?
[03:01] <jml> hi
[03:01] <thumper> barry_: hi
[03:01] <jml> I forgot it was Tuesday :)
[03:01]  * thumper is somewhat busy with beuno
[03:02] <barry_> jml: it's not, it's still monday :)
[03:02] <mwhudson> hi
[03:02] <jml> my mistake
[03:02] <barry_> thumper: i can wait a little bit if you want
[03:02] <thumper> barry_: yeah, but you can't wait for a week :)
[03:02] <thumper> I'll just pop in and out
[03:02] <barry_> :)
[03:03] <barry_> cool.  btw, i will not be here next week.  do you want to skip the meeting or can one of you run it?
[03:03] <barry_> [TOPIC] agenda
[03:03] <MootBot> New Topic:  agenda
[03:03] <barry_>  * Roll call
[03:03] <barry_>  * Using ReST instead Moin for documentation -- flacoste  [<<Date(2008-09-22T10:17:00-0500)>>]
[03:03] <barry_>  * Naming conventions for unit test methods. `testFooBar`, `test_fooBar` and `test_foo_bar` all exist. Recommend settling on `testFooBar` and only changing existing ones as encountered in normal work. -- jml [<<Date(2008-09-10T13:48:09+1000)>>]
[03:03] <barry_>  * Reviewers remove requests from Pending Reviews when you start a review.  If you forget the next on-call reviewer may duplicate your work.  -- bac [<<Date(2008-09-16T10:07:09-0500)>>]
[03:03] <barry_>  * If there's time, the old boring script
[03:03] <barry_>    * Next meeting
[03:03] <barry_>    * Action items
[03:03] <barry_>    * Queue status
[03:03] <barry_>    * Mentoring update
[03:04]  * jml waits
[03:05] <barry_> i'll let you guys sort it out for next week then :)
[03:05] <barry_> [TOPIC]  * Using ReST instead Moin for documentation -- flacoste  [<<Date(2008-09-22T10:17:00-0500)>>]
[03:05] <MootBot> New Topic:   * Using ReST instead Moin for documentation -- flacoste  [<<Date(2008-09-22T10:17:00-0500)>>]
[03:05] <thumper> I really don't care about this one
[03:05] <barry_> i haven't talked to flacoste about this yet, but i think this was brought up by gary
[03:06] <barry_> gary wants to write doctests in reST
[03:06]  * barry_ likes reST
[03:06] <jml> barry_: given that we aren't actually publishing the documentation, I don't see that it matters too much.
[03:06] <mwhudson> unless we're actually going to render the documentation and do something with it, i heartily don't care
[03:07] <barry_> cool.  i just wanted to get your sense so i can communicate it accurately at the ameu meeting
[03:07] <mwhudson> (rendering the documentation would probably be a good idea though)
[03:07] <barry_> sounds like a resounding -0/+0
[03:07] <jml> barry_: can we change the doc standard so it's 78 cols all the way through?
[03:07] <mwhudson> barry_: well, it's a bit more negative than that, as it would be a lot of work
[03:07]  * jml is half kidding
[03:07] <barry_> jml: i've been wanting to do that since i started
[03:08] <mwhudson> .oO(not that i edit doctests much...)
[03:08] <jml> barry_: 72 for text and 78 for Python seems like make-work to me.
[03:08] <barry_> mwhudson: i wouldn't propose to rewrite existing docs just to reformat them.  do it as general cleanup
[03:08] <jml> barry_: but that's probably a separate agendum :)
[03:08] <barry_> jml: why do you think i avoid friday reviews?  sinzui is the only one who cares about that :)
[03:09] <barry_> jml: but now sinzui is team leader and not doing reviews, so there ya go :)
[03:09] <jml> heh heh
[03:09] <mwhudson> barry_: still more work than seems worth it unless there are other benefits
[03:09] <barry_> jml: i will put it on the agenda for wednesday
[03:09] <barry_> [ACTION] barry put 78 column consistency in doctests on agenda for ameu
[03:09] <MootBot> ACTION received:  barry put 78 column consistency in doctests on agenda for ameu
[03:10] <barry_> mwhudson: ok, thanks.  gotcha
[03:10] <jml> cool.
[03:10]  * jml agrees with mwhudson
[03:10] <barry_> [TOPIC]  * Naming conventions for unit test methods. `testFooBar`, `test_fooBar` and `test_foo_bar` all exist. Recommend settling on `testFooBar` and only changing existing ones as encountered in normal work. -- jml [<<Date(2008-09-10T13:48:09+1000)>>]
[03:10] <MootBot> New Topic:   * Naming conventions for unit test methods. `testFooBar`, `test_fooBar` and `test_foo_bar` all exist. Recommend settling on `testFooBar` and only changing existing ones as encountered in normal work. -- jml [<<Date(2008-09-10T13:48:09+1000)>>]
[03:10] <jml> I had a look at the AMEU minutes.
[03:10] <barry_> jml: we talked about this in ameu, but you hadn't had time to state your position yet
[03:10] <jml> it seems they settled on test_<identifier>_qualifying_comments
[03:11] <barry_> jml: right, are you okay with that? or disagree?
[03:11] <jml> I assume that tests without identifiers just get pep8'd?
[03:11] <barry_> yep
[03:12] <jml> barry_: I'm cool with it.
[03:12] <barry_> jml: cool
[03:12] <jml> barry_: I basically just wanted a standard -- every module I use is different.
[03:12] <barry_> jml: right, agreed!
[03:13] <mwhudson> hooray
[03:13] <barry_> [TOPIC]  * Reviewers remove requests from Pending Reviews when you start a review.  If you forget the next on-call reviewer may duplicate your work.  -- bac [<<Date(2008-09-16T10:07:09-0500)>>]
[03:13] <MootBot> New Topic:   * Reviewers remove requests from Pending Reviews when you start a review.  If you forget the next on-call reviewer may duplicate your work.  -- bac [<<Date(2008-09-16T10:07:09-0500)>>]
[03:14] <barry_> i think this one's just a heads up.  several people did multiple reviews
[03:14] <jml> oh that's right, we still have a wiki page :)
[03:14] <mwhudson> "what is this Pending Reviews you speak of" ?
[03:14] <barry_> :)
[03:14] <mwhudson> i guess it's worth making the point
[03:14]  * barry_ looks to thumper and beuno
[03:14] <jml> barry_: incidentally... https://code.edge.launchpad.net/~launchpad/launchpad/trunk
[03:15] <thumper> sure
[03:15] <thumper> jml: shhh
[03:15] <thumper> ;-)
[03:15]  * jml needs to read over that "actually using Launchpad for reviews doesn't work" email
[03:16]  * thumper too
[03:16] <barry_> jml: whoa
[03:17] <thumper> barry_: FYI, beuno and I are making reviews rock in LP
[03:17] <barry_> i can has branches on lp?
[03:17] <barry_> thumper, beuno i am very excited to see the results
[03:17] <jml> on the sly, yes.
[03:17] <beuno> barry_, it's very promising  :)
[03:17] <jml> barry_: although make sure you upgrade everything (branches and repos) to 1.6
[03:18] <beuno> it should make the workflow almost natural
[03:18] <barry_> jml: cool.  eta for switching to?
[03:18] <thumper> barry_: also use bzr 1.7 or later
[03:18] <barry_> beuno: eta?
[03:18] <thumper> barry_: and the scanner will choke somewhat until mwhudson's branch is cherrypicked
[03:18] <mwhudson> i guess we could switch in maybe a week?
[03:18] <jml> barry_: there are a few patches we need to land.
[03:19] <jml> depending on how the cherry blossoms fall
[03:19] <beuno> barry_, it depends on thumper's speed and availability, but we should ahve something submitable after this week
[03:19] <barry_> after mwhudson branch is cherrypicked?  if we could do it on or before epic, that would be fantastic
[03:19] <mwhudson> that should be possible for sure
[03:19] <thumper> barry_: within a day or two for production is my guess
[03:20] <barry_> wow. it would be fantastic if we can dogfood all this, kill off devpad branches and PR at epic
[03:21]  * thumper hopes too
[03:21]  * beuno hopes three
[03:21] <thumper> I do have two weeks leave between now and the epic
[03:23] <barry_> cool.  that's about it from me.  queue update, mentor update, action items, blah blah blah
[03:23] <barry_> anything from you guys?  anything you want me to bring up at ameu?
[03:24] <mwhudson> nothing springs to mind
[03:24] <jml> nope
[03:24] <thumper> nada
[03:24] <barry_> cool.  thanks guys.  see you all in 2 weeks.
[03:24] <barry_> #endmeeting
[03:24] <thumper> ok
[03:24] <MootBot> Meeting finished at 21:24.
[03:24] <thumper> later dude
[03:25] <jml> barry_: see ya


[02:06] <ahoneybun> busy in here today
[02:07] <tsimonq2> ahoneybun: yup XD
[02:33] <ahoneybun> nice


[13:37] <kanashiro> is autopkgtest infra working? I just got this error while requesting a test run
[13:37] <kanashiro> A server error has occured, please contact a member of the Ubuntu QA team. You can contact them via the ubuntu-quality mailing list, or via the #ubuntu-quality IRC channel on irc.libera.chat (highlight 'qa-help' for more reactivity). Traceback: local variable 'msg' referenced before assignment
[13:52] <ginggs> kanashiro: from scrollback:
[13:53] <ginggs> that's a known temporary issue, you'll encounter that when rabbitmq is mid-restart. Once it's all back up and running, you will no longer experience the traceback.
[13:57] <Skia> usually solved in about 5 minutes
[13:57] <kanashiro> awesome, it worked now :)
[13:57] <kanashiro> thanks
[14:34] <bluca> andersson123: given it's clogged due to 23.10 I have temporarily disable the systemd job submission, please feel free to kill all currently queued/running jobs to shorten the queue


[15:54] <CarlFK> why does $(debconf-get... get expanded on "d-i preseed/late_command string" but not "d-i apt-setup/local0/repository string" ?
[15:54] <CarlFK> d-i preseed/late_command string cd /target/tmp && wget http://$url/lc/late.sh && chmod u+x late.sh && chroot /target /tmp/late.sh $(debconf-get mirror/suite) $(debconf-get passwd/username)
[15:54] <CarlFK> d-i apt-setup/local0/repository string http://ppa.launchpad.net/timvideos/ppa/fpga-support $(debconf-get mirror/suite) main
[15:55] <xnox> it's all static
[15:55] <CarlFK> er... thinking more, I think I can imagine why, and that's good enough
[15:55] <xnox> it just happens that late_command spawns a shell to process the string that comes after it
[15:56] <CarlFK> yeah. that' what I started to realize
[15:56] <CarlFK> boo.
[15:56] <xnox> hence command =)
[15:56] <xnox> it's not a turing complete templating language =)
[15:57] <CarlFK> for years I have just created a new dir for each release, copied the files, update the release names...
[15:57] <CarlFK> anything better?


[05:50] <slangasek> bkerensa: where's the beer
[05:50] <bkerensa> slangasek: in the stomach
[05:50] <slangasek> bkerensa: I mean tomorrow's Debian beering :)
[05:51] <bkerensa> oh
[05:51] <slangasek> Lucky Lab?  Or somewhere closer to OSCON?
[05:51] <slangasek> I suppose Lucky Lab isn't too bad; .5h walk, or <10min bus
[05:52] <bkerensa> slangasek: so ideally we could meetup at one of the oscon parties?
[05:52] <bkerensa> :)
[05:52] <bkerensa> http://www.oscon.com/oscon2013/public/schedule/detail/31419
[05:52] <slangasek> if that's what folks prefer
[05:53] <slangasek> I have no preference, I just want to make sure the locals know where to meet up :)
[05:53] <bkerensa> slangasek: so pleia2 is leaving early tomorrow but there are still a lot of Canoni folks in town
[05:53] <slangasek> Canonical Debian folks?  I thought this was supposed to be a Debian meet-up :)
[05:54] <bkerensa> slangasek: yeah so pleia2 would be the only debian person in town and she has to fly out early
[05:54] <bkerensa> :(
[05:54] <slangasek> pff
[05:54] <slangasek> ok, well, feel free to call the beering wherever you'd like then :)
[05:54] <bkerensa> slangasek: unless you consider shuttleworth a debian folk
[05:54] <bkerensa> ;p
[05:55] <bkerensa> I asked him about Honey Bee Colony Collapse
[05:55] <bkerensa> and he said he bees are not suffering
[05:55] <slangasek> I will sidestep that question by pointing out we're unlikely to get him to come to a beering tomorrow on such short notice
[05:55] <bkerensa> he thinks our use of pesticides is the cause
[05:55] <bkerensa> :)
[05:55] <bkerensa> oh
[05:55] <bkerensa> he was at all the parties this week
[05:55] <bkerensa> :)
[05:55] <slangasek> it's probably a factor; colony collapse seems to be a primarily US phenomenon. :P
[05:56] <slangasek> but that doesn't rule out it being a natural disease that's geographically limited
[05:57] <slangasek> anyway, if you want Debian folks to come out to OSCON or wherever for beering, please send mail :)
[05:57] <slangasek> if I don't see mail, I will probably find other ways to occupy my time tomorrow evening
[05:57] <bkerensa> slangasek: sent
[05:58] <bkerensa> I am not opposed to Lucky Labs either way and would gladly meet there if oscon party sees opposition
[05:59] <slangasek> I don't foresee any opposition to OSCON.  We already had the regularly scheduled Debian beering this month, so tomorrow is a bonus beering specifically for OSCON
[06:01] <bkerensa> slangasek: DD's in Town: Thierry Carrez, Gustavo Franco, Frédéric Lepied, Taku Yasui
[06:03] <slangasek> Thierry's not a DD, though the other three are and apparently some keysigning is warranted :)
[06:04] <bkerensa> slangasek: have you seen this key signing tool http://www.phildev.net/pius/
[06:05] <slangasek> nope.  Looks redundant with the signing-party package and the caff tool.
[16:59] <bkerensa> slangasek: do you have any suggestions for me ever getting this patch landed? http://permalink.gmane.org/gmane.linux.network/255227
[17:00] <bkerensa> Its like upstream is ignoring it
[17:00] <slangasek> bkerensa: no, I'm not a kernel dev and have no insights there
[17:00] <bkerensa> kees: ^ do you :/
[17:00] <bkerensa> the only person I know is maybe kees he sends patches to lkml land
[17:01] <kees> bkerensa: /me looks
[17:05] <kees> bkerensa: oh, that was in Jan?
[17:05] <kees> bkerensa: so, I have a number of suggestions:
[17:05] <bkerensa> kees: yeah man and I sent once before and then kindly e-mailed the maintained who ripped me a new one about off mailing list mail and such
[17:05] <bkerensa> :d
[17:05] <kees> 1) use the "scripts/checkpatch.pl" tool in the kernel to validate the contents of the patch
[17:05] <bkerensa> ok
[17:06] <kees> 2) CC lkml and netdev (I use scripts/get_maintainer.pl to get a list of people that might want to be CC)
[17:06] <kees> from 1, you'll likely have to split that line, since it looks to be >80 char
[17:07] <kees> 3) read Documentation/SubmittingPatches since it looks like your patch isn't from git, and lacks the right ordering and subjects
[17:08] <kees> from 3, you'd likely want to use "git log path/to/ping_common.c" to see how other people have done patches, but I bet the subject will look like "[PATCH] ping: remove excessive punctuation in flood warning"
[17:08] <kees> and then the body would be more descriptive, followed with your Signed-off-by
[17:08] <kees> "git format-patch" can be used to help with that, too.
[17:08] <bkerensa> ok
[17:09] <kees> and, I think I'm out of ideas :)
[17:09] <kees> but I'd suggest pull a git tree and using it to generate the patches.
[17:09] <bkerensa> kk
[17:09] <bkerensa> I will do this tonight
[17:09] <bkerensa> thx
[17:09] <kees> e.g.:
[17:10] <kees> git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
[17:10] <kees> vi path/to/ping_common.c
[17:10] <kees> git commit -aes
[17:10] <kees> git format-patch HEAD~1
[17:10] <kees> ./scripts/checkpatch.pl 0001-ping_remove_excessive...patch
[17:10] <kees> ./scripts/get_maintainer.pl 0001-....patch
[17:11] <kees> (oh, you'll need a "cd linux" after that git clone)
[17:11] <bkerensa> kees: where do you store all this data? :) do you answer questions like this often?
[17:11] <bkerensa> :)
[17:11] <kees> bkerensa: heh, nah, this is just off the top of my head. I do it so much.
[17:12] <kees> only thing I looked up with the full git clone path to linus's tree :)
[17:12] <bkerensa> kees: you coming to the beering at Jupiter Hotel tonight?
[17:13] <bkerensa> slangasek: I invited all the DD's and DM's that are in town for OSCON to come
[17:13] <kees> bkerensa: unclear, I'm still trying to understand the shape of my day today. :)
[17:14] <kees> bkerensa: when you've got it prepared again, feel free to email it to me first and I can re-check what you've got.
[17:15] <bkerensa> kees: kk