[04:36] <zequence> cub: if you investigate the contents of the desktop file, you will see the line which executes the application
[04:36] <zequence> /usr/bin/<something>, usually
[04:38] <zequence> Or, let me show an example
[04:38] <zequence> the desktop file ardour3.desktop
[04:38] <zequence> Name=Ardour3 (the name that appears in the menu)
[04:39] <zequence> Exec=/usr/bin/ardour3 (the actual binary)
[04:40] <zequence> Or, just the name is enough, cause that will make sure that what you see in the menu is for the right desktop file
[04:40] <zequence> Probably not a problem. I just put it in there in case
[04:41] <zequence> Right, I forgot to put in the rules
[04:41] <zequence> I was a little busy at the time. Still am. Also, a bit under the weather
[04:42] <zequence> Let me do some changes to the instructions during the coming weekend
[04:42] <DalekSec> zequence: he's long gone, mate.
[05:11] <zequence> DalekSec: He usually read the backlogs
[05:11] <zequence> It
[05:11] <DalekSec> Ah, pardon me then.
[05:11] <zequence> :)
[05:11]  * DalekSec ducks and hides.
[13:51] <ttoine> hello
[17:49] <cub> How about the blueprints, fdc-graphics contains kdenlive which is AudioVideo, is there something we should do to move it to fdc-video? Or does that not matter?
[17:51] <cub> Also, is the Categories order important? As for kdenlive it's: Qt;KDE;AudioVideo;AudioVideoEditing;
[17:58] <zequence> cub: kdenlive is for some reason put in the graphics section in Debian, so that should probably be changed upstream as well
[17:58] <zequence> I can't think of any other reason for the order being important than pure pedantism :).
[17:59] <cub> Aha
[17:59] <cub> I we find packages that might be dropped? Like Kino which hasn't been updated since 2009 and their webpage claims the project is dead. :D
[18:04] <zequence> Well, this is really a full go through of all multimedia packages, just the ones with desktop files. Other subjects than categorization is not a part of the plan.
[18:04] <zequence> this is not a full go-through, is what I meant
[18:05] <zequence> If Kino still works, I see no problem with keeping it in the repo, as long as the package maintainer is active
[18:05] <zequence> It's really a job for the maintainer to keep track of that, in Debian
[18:05] <zequence> But, if there are problems, one should report a bug and make sure the maintainer is aware of it
[18:09] <cub> Kino package is taken care of, and started just fine in my 14.04
[18:09] <cub> Kino has 44 open bugs
[18:31] <zequence> atom has gone stable - http://atom.io
[18:36] <cub> Looks good. Still hooked on vim though.
[18:40] <zequence> I never started using anything beyond nano on terminal. Haven't had the patience to learn
[18:41] <zequence> There are some editing features that I'm not sure you can do in a terminal
[18:42] <zequence> Like cut and paste a section into a specific tab depth
[18:42] <zequence> Also, moving a selection left, right, 4 spaces with TAB, or SHIFT+TAB
[18:48] <cub> I have quite basic needs as long as I get 4 spaces tab, colour coding and Solarized theme


[03:51]  * arosales finishing up review time
[04:15] <fuzzy> Hi there I just build a juju deployment using the quick start and manual provisioning.  I'm using 12.04 and have the precise juju-gui installed, but when I do a juju status it says pending.  The machine is at 100% idle and it's been like 5 minutes.  Is there anyway to figure out what is holding it up?
[09:43] <stub> Interesting... my agent died while in debug-hooks
[09:43] <stub> lxc
[09:43] <jam2> stub: seems surprising, anything interesting in the log file?
[09:45] <stub> jam2: yeah, I seem to have a big arsed go panic in there
[09:47] <stub> jam2: here we go. http://pastebin.ubuntu.com/8231693/
[13:30] <aisrael> Which project contains the text of this page? Doesn't look like it's juju-docs. https://juju.ubuntu.com/
[13:31] <tvansteenburgh> how does one test an upgrade-charm hook?
[13:33] <tvansteenburgh> nevermind, `juju upgrade-charm -h` look helpful
[13:36] <lazyPower> hey  marcoceppi, hazmat, jcastro, mbruzek did you see we had a community member working with linode contribue a quick start stack script for creating a juju jump-host on linode? https://www.linode.com/stackscripts/view/10193
[13:36] <hazmat> lazyPower, i did
[13:37] <jcastro> that is awesome
[13:37] <jcastro> I'll send him a shirt
[13:37] <hazmat> lazyPower, ideally it would be wrapped up into a plugin like the digitalocean provider using the api.. its pretty manual to use something like that
[13:37] <hazmat> basically its restricted to a one node env without some work
[13:38] <lazyPower> hazmat: well, I was working with fuzzy to achieve their goal of having a jump station for their trusted dev-staff to control deployments.
[13:38] <hazmat> not sure if it really needs the host name set, or if could bootstrap localhost and be auto for the one node case
[13:38] <jcastro> oh you're talking to them already?
[13:38] <lazyPower> they didn't like the idea of porting ~/.juju - so they threw it up as a stack script, and thats effectively their manual jump host.
[13:39] <lazyPower> jcastro: yeah - i've known fuzzy a little over a year. Fuz is working with our Meteor.js charm
[13:39] <jcastro> oh ok
[13:39] <jcastro> # Stephanie Sunshine<EMAIL_ADDRESS>[13:39] <lazyPower> it started as "how can i gate deployments a-la capistrano style?" - to which I showed them Juju-strano
[13:39] <lazyPower> Thats the one.
[13:39] <jcastro> what about her? should I send her a  shirt or are there multiple ones?
[13:39] <lazyPower> Stephanie Sunshine = Fuz
[13:40] <jcastro> ack
[13:40] <jcastro> I'll send along a link to the DO provider as well
[13:41] <lazyPower> hazmat: I pinged the list with that stack script, any feedback for them on that thread would be awesome. I'll point fuz at it when she shows up later today.
[13:41] <lazyPower> I was talking about a phaux provider like your DO plugin - but for PoC work that was overkill. I can see that being on the roadmap as a community contribution though - baby steps :)
[13:42] <jcastro> yeah
[13:44] <aisrael> jcastro: any idea where that page lives, project wise (see previous question)?
[13:45] <jcastro> the website, it's a wordpress setup
[13:45] <jcastro> there should be a l ink on where to report bugs at the bottom
[13:45] <jcastro> ... or not
[13:45] <jcastro> https://launchpad.net/juju-website
[13:46] <aisrael> ack, thanks
[13:50] <aisrael> jcastro: I assume content changes just need to have a bug filed against it?
[13:51] <jcastro> yeah
[13:51] <jcastro> if you want irc ping luca
[13:51] <jcastro> he's just taken over the site and is doing a massive clean up/reorg
[13:54] <aisrael> kk
[14:23] <natefinch> marcoceppi, jcastro, anyone else:  do I have to do open_port 80 in my install hook if I declare my app to be http, or will juju expose do that for me?
[14:23] <marcoceppi> natefinch: all port openings need to be explicit
[14:23] <natefinch> marcoceppi: ok, that makes sense
[14:23] <marcoceppi> port 80 isn't the only port an http server could run on
[14:23]  * marcoceppi wanders off pondering tomcat
[14:41] <jcastro> natefinch, the other half of that bug, which is annoying
[14:41] <jcastro> is the whole directory structure for local charms
[14:41] <jcastro> so like, juju expects:

[14:42] <jcastro> -> <charmname>
[14:42] <jcastro> and if you do `juju deploy --repository=foo local:blah`
[14:42] <jcastro> if foo doesn't have a series/charm structure, it just bails
[14:43] <natefinch> jcastro: you should read my latest email about writing a charm, I mentioned that specifically
[14:43] <jcastro> yeah
[14:43] <natefinch> jcastro: my suggestion is to make juju deploy --local=<path>  work if <path> points to a charm directory
[14:43] <jcastro> yeah!
[14:43] <jcastro> natefinch, is there a specific bug for that or is it just on your radar somewhere?
[14:43] <natefinch> jcastro: on my radar, but we should make a bug
[14:44] <natefinch> jcastro: my radar is notoriously unreliable ;)
[14:44] <jcastro> ok I'll copy and paste your text and toss it in there
[14:44] <natefinch> jcastro: awesome, thanks
[14:46] <jcastro> https://bugs.launchpad.net/juju-core/+bug/1365542
[14:46] <mup> Bug #1365542: Doesn't deploy a charm unless the repository directory has a specific directory structure <ui> <juju-core:New> <https://launchpad.net/bugs/1365542>
[14:49] <natefinch> jcastro: great
[15:38] <JoshStrobl> Hey arosales_ where do you think the Code Review section in the Charms Review Doc should be? Prior to the charmers team part so it doesn't break apart the absolutely essential parts of the review?
[15:40] <JoshStrobl> Also, I was thinking about moving up the community review ending part to prior to the charmers team, that way the process of the charmers team can take up more room if necessary and not push down the community content.
[15:41] <arosales_> JoshStrobl: hmm, it would live in the workflow your defined, perhaps before deploy/test.
[15:41] <arosales_> JoshStrobl: or we could leave that specifically for the ~charmer section
[15:41] <arosales_> your thoughts?
[15:42] <JoshStrobl> hmm
[15:42] <arosales_> I guess it comes back to if we think everyone will want/be able to do a code review.
[15:42] <JoshStrobl> exactly
[15:43] <JoshStrobl> I don't want to make it seem like it is only meant for the charmers team.
[15:43] <arosales_> ya +1 to that
[15:43] <JoshStrobl> but it is your call
[15:43] <arosales_> I think this should be _the_ review process
[15:43] <arosales_> we could put it out to the list for input too
[15:44] <arosales_> ideally, the review process is transparent and anyone wanting to can do a full reivew.
[15:44] <arosales_> but
[15:44] <arosales_> perhaps folks just want a workflow that is straight forward and does not include code review
[15:45] <JoshStrobl> marcoceppi, do you know if the "expanded sections" header thing (the Juju specific Markdown) works?
[15:45] <JoshStrobl> arosales_, if the expanded sections part works, we could have it prior to the deployment section.
[15:46] <JoshStrobl> arosales_, it could be unexpanded by default, marked optional, those that want or are required to dive into the code review can expand the section
[15:47] <JoshStrobl> marcoceppi, what I am referring to -> https://github.com/juju/docs/wiki/Markdown#foldouts
[15:48] <marcoceppi> JoshStrobl: yes, those all work
[15:48] <marcoceppi> JoshStrobl: you can see it in action on this page:
[15:48] <marcoceppi> https://juju.ubuntu.com/docs/reference-release-notes.html
[15:48] <JoshStrobl> ah sweet, thanks
[15:49] <JoshStrobl> arosales_, would that work?
[15:49] <marcoceppi> JoshStrobl: if you need additional HTML elements that don't exist yet, Im happy to make more markdown plugins
[15:50] <allomov> Hey, all.
[15:50] <allomov> I will have short question about deploying to openstack.
[15:50] <marcoceppi> allomov: feel free to ask your question
[15:50] <allomov> I get following error trying to bootstrap openstack environment: https://gist.githubusercontent.com/allomov/188131c84fdbcbab5ea8/raw/b7192994bbab0f0c70d8e1a19f7dcb09cab3cb70/fail-juju.log
[15:51] <allomov> here is a piece from my environment.yml file https://gist.githubusercontent.com/allomov/188131c84fdbcbab5ea8/raw/799c20a50083e82bf832cadb3e72ad7d2159c5a4/juju-env.yml
[15:51] <marcoceppi> allomov: you need to create cloud image metadata for your openstack provider
[15:51] <marcoceppi> allomov: https://juju.ubuntu.com/docs/howto-privatecloud.html
[15:52] <arosales_> JoshStrobl: I am thinking if we just put out code review section in the ~charmer section but welcome anyone to also do that as part of their reivew . ..
[15:52] <allomov> marcoceppi: cool, thank you for the source
[15:52] <arosales_> JoshStrobl: but also try to keep this readable so folks don't think this is just for ~charmers
[15:52] <marcoceppi> allomov: the first half of that doc is pretty heavy with details that might confuse at first. Make sure you read through once :)
[15:53] <allomov> marcoceppi: that's the strange thing, because I didn't need to use my region name before. fog gem for instance doesn't need it
[15:53] <marcoceppi> allomov: Juju does a bit more and things slightly differently than fog gem
[15:55] <arosales_> JoshStrobl: my 2 cents, fwiw, lets put the code review section in the "general/community" review process. Cavet the code review is optional pending review comfort level.
[15:55] <arosales_> inlucde some common things to look for that we can grow out so folks can grow their skill there if they want
[15:55]  * arosales_ thinking out loud
[15:55] <arosales_> JoshStrobl: as you mentioned this could also be folded in too
[15:55] <JoshStrobl> arosales_, sounds good to me.
[15:56] <JoshStrobl> arosales_, I'll make note of the existing code review contents you pointed out in the comments and it can be expanded up later if others come up with more stuff, sound good?
[16:01] <arosales_> JoshStrobl: sounds good
[16:02] <JoshStrobl> Fantastic. I'll get started on it now then!
[16:02]  * arosales_ really liking this doc.
[16:03] <arosales_> I will also be creating a complimentary charm author guidliens doc specifically to call out design consideration and common gotchas in reviews that we can take care of before review.
[16:03] <arosales_> JoshStrobl: be good to get your input there if you have time given your a charm author
[16:04] <JoshStrobl> arosales_, sounds good. do you want us to figure it out after your guys' sprint?
[16:08] <arosales_> JoshStrobl: ya I have this slated to creat at the sprint next week.
[16:08] <JoshStrobl> \o/
[16:12] <arosales_> JoshStrobl: to conrim I read that correctly, re "figure it out after your guy's sprint" was that in regards to your charm review doc, or my charm author guidlines doc.
[16:12] <JoshStrobl> arosales_, your charm author guidelines doc
[16:13] <JoshStrobl> arosales_, we understand each other correctly?
[16:16] <arosales_> JoshStrobl: we do :-)
[16:16] <JoshStrobl> great :)
[16:44] <JoshStrobl> arosales_, sorry to nag you again, was thinking about another thing to watch out for in the code review, you approve of the following? "Not using set -ex in bash scripts, which allows the bash script to more easily catch failed execution, thereby allowing Juju to more accurately detect a failed hook."
[16:47] <arosales_> JoshStrobl: not nagging at all
[16:52] <marcoceppi> JoshStrobl: yes, that should def be in there
[16:52] <marcoceppi> JoshStrobl: well, only -e is needed
[16:52] <marcoceppi> -x is xtrace
[16:52] <JoshStrobl> marcoceppi, ah
[16:53] <JoshStrobl> I'll remove the x part then :P
[16:53] <marcoceppi> -eux should be in best practices though, (-u being that if a varaible is accessed before set it's an error)
[16:54] <JoshStrobl> marcoceppi, so you think I should have it as -eux or something like "Not using set -e or set -eux[...]"
[16:54] <marcoceppi> -e is the minimum for a review, -eux should be in the best practice section of the docs imo
[16:54]  * marcoceppi may make a merge for that
[16:59] <arosales_> JoshStrobl: +1 to marcoceppi comments on just making sure -e is there
[17:00] <arosales_> +1 on recommending -eux though per marcoceppi's suggestions
[17:02] <JoshStrobl> marcoceppi, request for the script that converts the GFM / Juju Markdown into HTML (you know, the make stuff), have a sha1sum of each file. Do an on-the-fly comparison between the sha1sum of the files in src/en/ and the existing sha1sums. If the file changed, THEN convert it. Otherwise don't bother. I think it'd speed up the converting time when using "make" since it'd only convert files that have changed.
[17:03] <JoshStrobl> (does this with some of his custom "compilers")
[17:03] <marcoceppi> JoshStrobl: sure, that's a great idea. Can you open an issue on GH
[17:03] <marcoceppi> I'm collecting a list of things I can do "offline" the next time I'm flying
[17:03] <JoshStrobl> yep, is the converter in juju/docs?
[17:04] <marcoceppi> JoshStrobl: yup
[17:04] <JoshStrobl> cool, I'll file an issue there then
[17:04] <marcoceppi> you're talking about a hashsum of the compiled file, right?
[17:04] <marcoceppi> rather
[17:04] <JoshStrobl> no, a sha1sum of the src/en markdown files
[17:04] <marcoceppi> if compiled file exists, and hashsum of the source hasn't changed, then skip
[17:05] <marcoceppi> otherwise, you'd never get an initial copy of the compiled file
[17:05] <JoshStrobl> if src/en/*.md sha1sum !== existing sha1sum of the file (stored in a .sha1sum file), compile, else skip
[17:06] <JoshStrobl> right, if the sha1sum simply doesn't, go ahead and compile it anyways, since the file probably doesnt exist in htmldocs
[17:06] <marcoceppi> JoshStrobl: yeah, i get teh concept. def open an issue, it's a great idea esp as the docs increase size
[17:06] <marcoceppi> I was going to implement a file watcher
[17:06] <marcoceppi> so as src/* files changed it would just recompile them
[17:07] <JoshStrobl> that'd be great too, but I'd prefer to not have to compile every single markdown file into HTML whenever I make a change I want to test :P
[17:07] <JoshStrobl> but yea, I'll file an issue in a bit
[17:08] <marcoceppi> it would only compile the markdown file that changed, not all the files
[17:08] <marcoceppi> but yeah
[17:10] <JoshStrobl> You can sorta get an idea of how I do it by looking at the recursiveCompiling function at https://github.com/StroblIndustries/Metis/blob/master/build/compiler/metisCompiler and the fileChanged function at https://github.com/StroblIndustries/Metis/blob/master/build/compiler/compilerFunctions
[17:11] <JoshStrobl> it is bash, I'm going to assume yours is in python, but the logic is essentially the same
[17:13] <avoine> anyone got that error on a bootstrap?
[17:13] <avoine> ERROR juju.cmd supercommand.go:323 cannot initiate replica set: cannot get replica set configuration: cannot get replset config: not authorized for query on local.system.replset
[17:13] <JoshStrobl> arosales_, doc is now updated: https://github.com/JoshStrobl/docs/commit/bf62c234572b94ff61cec6709db3190654639433?diff=split
[17:14] <marcoceppi> avoine: what version of juju are you using? `juju version`?
[17:14] <avoine> 1.20.6-trusty-amd64 and juju-mongodb 2.4.9-0ubuntu3
[17:15] <avoine> from http://ppa.launchpad.net/juju/stable/ubuntu
[17:16] <avoine> and with an lxc local bootstrap
[17:17]  * arosales_ loving the split in github
[17:17] <arosales_> JoshStrobl: thanks taking a look
[17:21] <JoshStrobl> marcoceppi, issue filed - https://github.com/juju/docs/issues/157
[17:49] <marcoceppi> kirkland: using "run-one-constantly" in the new review queue, love these little helper scripts
[17:49] <kirkland> marcoceppi: woot :-)
[17:50] <kirkland> marcoceppi: btw, I just found, per dpb2, the timeout command, which is nice in conjunction with run-one*
[17:50] <marcoceppi> nice
[17:50] <dpb2> :)
[18:55] <arosales_> marcoceppi: got a question for you
[18:55] <arosales> any any yaml experts out there
[18:55] <arosales> I am looking at the cassandra charm
[18:55] <marcoceppi> arosales: what's the problem?
[18:56] <arosales> and it is currently failing proff as it is missing defatult value for some of the keys
[18:56] <arosales> I am looking for a recomendaton on what to put for a default
[18:56] <arosales> is it simply, "default:"
[18:56] <marcoceppi> arosales: just put the default key, but leave it blank
[18:56] <arosales> or
[18:56] <marcoceppi> yes, that one
[18:56] <arosales> default: ""
[18:56] <arosales> marcoceppi: ack on just the default key, but blank, ie "default:"
[18:57] <arosales> marcoceppi: thanks.
[18:57] <marcoceppi> to keep current behavior, you should use the former, if blank string is needed (intead of unset) then the latter
[18:57] <arosales> marcoceppi: ack.
[18:57] <marcoceppi> it's the difference between "" and NULL which most charms wont' care about, but some do
[18:57] <arosales> I'll check that doesn't cause any issues on the charm deploy
[18:57] <arosales> ya I was wondering if some charms check for any value to be set
[18:58] <arosales> and take action on that even if it is blank
[18:58] <arosales> or specifically look for a Null, and then key off that
[18:58] <arosales> that was my main concern
[20:27] <lazyPower> hatch: no. The mismatch in versions between deployed and what you have installed locally wouldn't cause that. (moving convo here)
[20:28] <hatch> ahh ok, just noticed it, thought I'd point it out
[20:28] <hatch> :)
[20:28] <hatch> I'm really hoping you can reproduce this
[20:28] <hatch> heh
[20:28] <lazyPower> hatch: i found the issue though
[20:28] <lazyPower> your source option is coming back as undefined. and it should be defaulting to true.
[20:29] <hatch> so is this a GUI bug?
[20:29] <lazyPower> i'm pointing a finger at the devel branch of the gui,  I'm testing with -stable now and pending a deployment.
[20:29] <lazyPower> it appears so
[20:30] <hatch> interesting....
[20:30] <hatch> wow if it is, it's good we caught it now and not next week lol
[20:32] <hatch> lazyPower:  I'll also try on stable
[20:54] <lazyPower> tvansteenburgh: http://paste.ubuntu.com/8253401/
[20:54] <lazyPower> i ran into a promulgate bug - any idea what i've snagged?
[20:55] <lazyPower> wait, i found it. when i cloned it it was missing the push branch it was sniffing for. I overrode the lp resource to use the ~charmers route and it worked.
[21:00] <wesleymason> So...I have a theory that in a certain situation the containerName passed to OpenstackStorage.Remove() can be blank (perhaps if a destroy-environment is called after a failed destroy due to an API timeout, not sure), which will result in a DELETE being sent to the swift account URL (and in v1.7.x of swift marks the account on swift as deleted, which is a total PITA to then fix as it involves either a) waiting for a cron'd script to really delete the DB, or
[21:00] <wesleymason> b) manually removing the sqlite3 DB file for the user on the swift replicas - both of which then results in the account being recreated based on the keystone perns for the user on next access. Now I have an easy fix for that (check for the error condition specifically in func Remove(...)), but not a clue how to replicate the issue, other than the fact that this is the only explanation I have for how my swift account got screwed after a failed destroy-enviro
[21:00] <wesleymason> nment followed by a successful one.
[21:00] <wesleymason> Any thoughts?
[21:01] <wesleymason> probably better off asked in #juju-dev, but more after ideas or reactions like "that sounds ridiculs, naaah"
[21:02] <wesleymason> *ridiculous
[21:17] <hatch> lazyPower: so I was able to deploy it just fine in an old version of the GUI
[21:17] <hatch> you the same?
[21:18] <hatch> source isn't even set when running the juju-run command
[21:18] <hatch> er, it's not in the list
[21:24] <dpb2> If I give an http:// url to image-metadata-url, it still downloads with 'https://' is that expected?
[21:30] <dpb2> and by downloads, I mean, downloads the images
[21:33] <lazyPower> dpb2:are  you referring to simple streams?
[21:33] <lazyPower> hatch: correct, it worked fine using a -stable revision of the gui.
[21:34] <lazyPower> er, whatever is provided by default.
[21:34] <lazyPower> hatch: i'd re-target the bug against the GUI and point to this LP resource for all the aggregated details.
[21:34] <dpb2> lazyPower: maybe, I'm referring to the images for lxc creation that get downloaded form cloud-images.ubuntu.com
[21:34] <lazyPower> dpb2: ah, yeah it defaults to secure comms to avoid MITM attacks.
[21:35] <dpb2> lazyPower: but I changed it to http?
[21:35] <dpb2> no good?
[21:35] <lazyPower> natefinch: are there any schenanigans with fetching of the cloud image url structure?
[21:36] <lazyPower> dpb2: so, offtopic - i've noticed you've incremented by 1, level up?
[21:36] <dpb2> lazyPower: perhaps... you never know with me
[21:36] <hatch> lazyPower: definitely
[21:36] <hatch> thanks so much for the help
[21:36] <dpb2> lazyPower: I think freenode didn't like my identity. :)
[21:37] <lazyPower> hatch: np :) I smelled some schenanigans once I saw the deploy configuration in the bug.
[21:37] <lazyPower> dpb2:  Freenode, like camelot - is a silly place.
[21:39] <hatch> lazyPower: I've also got help on getting apache2 going for ghost and which options I need so very close to finally piecing together a bundle :)
[21:40] <lazyPower> hatch: awesome! I look forward to seeing your bundle submission
[21:41] <dpb1> lazyPower: I'm back!
[21:41] <lazyPower> dpb1: decrement
[22:27] <mbruzek> arosales, Github will not let me merge your change as-is.
[22:27] <JoshStrobl> mbruzek, what is the issue?
[22:27] <arosales> mbruzek:ok let me get this conflict resolved
[22:28] <arosales> https://github.com/juju/docs/pull/154 is in question
[22:28] <mbruzek> I have no problem with the *change* I need you to run the commands to get your branch current (is my guess).
[22:28] <mbruzek> JoshStrobl, I see the following message:   We can’t automatically merge this pull request.
[22:28] <mbruzek> to resolve conflicts before continuing.
[22:29] <JoshStrobl> arosales, maybe your master branch of your fork isn't updated?
[22:29]  * JoshStrobl checks
[22:29] <JoshStrobl> yea it is 186 commits behind juju master
[22:30] <fuzzy> Hi there, I got a new Juju installation going, but on the command and control node, my logs are being spammed pretty bad.  Could someone tell me what is going on and possibly how to fix it? https://clbin.com/XZ63i
[22:30] <arosales> ya it appears so
[22:30] <mbruzek> hi fuzzy I have not seen that before.
[22:30]  * arosales working to update
[22:31] <mbruzek> fuzzy, what version of Juju are you using?
[22:34] <arosales> mbruzek: I think if I push to master it will hit master
[22:34] <arosales> mbruzek: to confirm your review was a +1?
[22:34] <mbruzek> arosales, Confirmed.  It looks great
[22:35] <arosales> mbruzek: ok thanks
[22:35] <fuzzy> Sorry my wifi card likes to forget it exists
[22:35] <mbruzek> fuzzy, have not seen that error before what version of Juju are you using?
[22:35] <fuzzy> the latest one for 12.04 as of last night
[22:36] <fuzzy> I followed the quickstart for manual provisioning
[22:37] <fuzzy> is there an easy way to get juju to spit out version info?
[22:38] <mbruzek> fuzzy, juju version
[22:38] <fuzzy> 1.20.7-precise-amd64
[22:39] <mbruzek> hrmm... That *is* the latest.
[22:39] <mbruzek> What command are you running that it gives you this log output?
[22:39] <fuzzy> cat /var/log/syslog
[22:39] <fuzzy> well tail -n 100 /var/log/syslog
[22:40]  * JoshStrobl is going reset his fork of juju/docs. git sometimes doesn't like to fast-forward so I magically end up with extra commits that are then ahead of juju/docs.
[22:40] <mbruzek> fuzzy, I have several messages like that in my syslog
[22:41] <mbruzek> fuzzy, so I guess that is normal.
[22:41] <mbruzek> fuzzy, You can go to #juju-dev and ask the developers about those logs, but I see them all over my syslog too.
[22:42] <sarnold> wow that's noisy..
[22:44] <mbruzek> fuzzy, I am about to end my day I have to get to dinner.
[22:59] <lazyPower> fuzzy: that looks like the migrations weren't run against the collection setting roles
[22:59] <lazyPower> and yes, thats very noisy.
[23:00] <fuzzy> ty :)
[23:00] <fuzzy> about 10mb in 24 hours of logs


[00:11] <Unit193> bluesabre: lp 1368557, lp 1357217.  I suppose we/I/someone should prep that.
[00:24] <Unit193> bluesabre: https://sigma.unit193.net/source/apt-offline_1.3.1ubuntu0.1.dsc
[00:36] <Unit193> https://wiki.ubuntu.com/StableReleaseUpdates
[01:18] <bluesabre> Unit193: cool, suppose I should try to work on that nowish
[01:19] <Unit193> bluesabre: That's the upload prepped, just needs the paperwork. :P
[01:32] <Unit193> bluesabre: And, you should have packageset.  Do you need anything else from me/
[01:42] <bluesabre> Unit193: I think that's it, thanks for doing the hard work :)
[01:53] <Unit193> Hah. :P
[01:57] <bluesabre> Unit193: want to add any ideas to http://pad.ubuntu.com/xubuntu-v-dev ?
[02:02] <Unit193> "Get ready for systemd which will land in the first half of the cycle" Pardon?  New stuff in staging, so it's not staging as much as daily.  I'm sure I'll continue to dump stuff in extras. :P
[02:04] <Noskcaj> bluesabre, Could you review the xfce sync requests on http://reqorts.qa.ubuntu.com/reports/sponsoring/ please?
[02:05] <bluesabre> Unit193: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2014-October/001116.html
[02:06] <bluesabre> Noskcaj too, "Autosyncs will be running shortly, so give a little patience to the buildd network as they work through the queue, and no need to rush to sync your favourite package, it'll get there."
[02:06] <Noskcaj> these aren't autosyncs
[02:06] <bluesabre> ah, gotcha
[02:06] <bluesabre> then yeah, will review those shortly
[02:07] <Noskcaj> ty
[02:08] <Unit193> bluesabre: That's a SRU, for trusty. ;)
[02:09] <bluesabre> Unit193: apt-offline, right? or talking about something else now?
[02:10] <Unit193> Naaah, though I can give you more! :P
[02:15] <Unit193> bluesabre: So, which systemd stuff are you talking about?
[02:18] <bluesabre> Unit193: Adam's comment: " - Steady progress on the systemd transition, with a goal to switch over in the first half of the cycle."
[02:18] <Unit193> Aha, missed that bit. >_<
[02:18] <Unit193> :P
[02:18] <Unit193> 215 already landed.
[02:23] <bluesabre> Unit193: signed and uploaded your package
[02:23] <Unit193> \o/
[02:26] <Unit193> queuebot:#ubuntu-release: Unapproved: apt-offline (trusty-proposed/universe) [1.3.1 => 1.3.1ubuntu0.1] (xubuntu)
[02:30] <bluesabre> gettin' things done!
[02:35] <Unit193> bluesabre: Can you think of anything I should be thinking of then?  We're supposed to be "considering" extras for inclusion, right?  Nothing we want to include?
[02:36] <bluesabre> I'm just looking for ideas now, and you usually have a good idea of whats happening in various development channels
[02:37] <Unit193> 0_o
[02:37] <bluesabre> I have crazy suggestions like considering viewnoir and geary as possible new apps
[02:38] <Unit193> Ewww, -1 -1 -1! :P
[02:38] <bluesabre> haha, not a fan of either?
[02:38] <Unit193> Less so of the second.
[02:39] <bluesabre> it works well now, if not for missing contacts management or pgp support
[02:40] <bluesabre> but its super-new and likely to change at any time, and thunderbird is always pretty reliable
[02:41] <Unit193> There's those, it seems to be pretty tied to Gnome, seemed pretty basic, etc, etc.  And, look at my QA page, and guess which one I use. :P
[02:43] <bluesabre> :)
[02:43] <bluesabre> viewnior opens pretty darn quickly
[02:44] <bluesabre> "Set as wallpaper" doesn't seem to support xfce though, maybe I'll submit a patch for that
[02:48] <Unit193> ristretto isn't so bad, gpicview isn't bad except the bugs, thus the first is better. :P
[02:48] <Unit193> And it's Xfce! :P
[02:49] <bluesabre> woo!
[02:52] <Unit193> http://paste.openstack.org/show/DfSCXL0KSdgsuQMb0iuE/ FWIW.  Not very good as those stats could be off, and a few of those were recently uploaded.
[02:53] <bluesabre> hello thunar-dropbox-plugin
[02:53] <Unit193> bluesabre: Got the dalies started for Varmint?
[02:53] <Unit193> !info thunar-dropbox-plugin utopic
[02:53] <Unit193> Already covered. :P
[02:53] <bluesabre> :)
[02:53] <Unit193> Hopefully it's in your packageset.
[02:54] <bluesabre> going to update daily ppas now... wonder if I can tell things to rebuild for vivid without a re-upload
[02:55] <bluesabre> maybe a copy to the same ppa with different release
[03:00] <bluesabre> sweet, that does work
[03:05] <Noskcaj> Anything i should be working on?
[03:15] <bluesabre> I have nothing planned yet.  Updating PPAs and daily builds as needed
[03:18] <Unit193> !info systemd vervet
[03:18] <bluesabre> !info systemd vivid
[03:21] <Unit193> !info systemd vivid-proposed
[03:21] <Unit193> :P
[03:21] <Unit193> Oh yes it does.
[03:23] <bluesabre> ok, most of our PPAs should be updated as needed for vivid tomorrow
[03:23] <bluesabre> or even in a few minutes
[03:25] <Unit193> Not rebuilding the packages yet, nothing much has changed and when it does that'd require a new upload.
[04:55] <Pwnna> is there a way to reload xfwm4 so it picks up changes to .config/xfce4/xfconf/xfce.../xfwm4.conf?
[04:56] <Unit193> killall xfwm4 ?
[04:57] <ali1234> xfwm4 --replace
[04:58] <Unit193> Because of user sessions, xfwm4 will respawn.
[05:00] <Pwnna> doesn't work
[05:00] <Pwnna> i'm moving the close maximize minimize button
[05:00] <Pwnna> xfwm4 --replace doesn't pick up those settings
[05:00] <Pwnna> lightdm restart does
[05:02] <Pwnna> actually that's not even guarenteed
[05:10] <Pwnna> basically i'm trying to change     <property name="button_layout" type="string" value="CHM|O"/>, except automatically
[05:13] <Pwnna> and if i changed in the xml, it won't take effect
[07:21] <ochosi> morning folks
[07:21] <elfy> hi ochosi - bit more relaxed today?
[07:22] <ochosi> sure
[07:22] <ochosi> had a busy week, slowly fading into weekend mode
[07:22] <elfy> \o/
[07:23] <ochosi> bringing that over from -ot, since it's more -dev.. geary was intended as tb replacement
[07:24] <elfy> ok - pop3 support?
[07:24] <ochosi> i've used it for a while, it's quite good in some aspects
[07:24] <ochosi> pop3? ofc not :)
[07:24] <ochosi> or at least i think not
[07:24] <elfy> well lots of people still use pop3
[07:24] <elfy> unfortunately
[07:25] <ochosi> weird, i don't know anybody
[07:25] <ochosi> giving them a reason to switch might be good ;)
[07:25] <ochosi> anyway, on a more serious note, it has some advantages
[07:25] <elfy> British Telecom unless they do now
[07:26] <ochosi> (speed, low on depends etc), but it also has some backdraws
[07:26] <ochosi> for me, the lack of an addressbook and pgp are the two biggest ones
[07:26] <ochosi> not sure i could recommend it based on those two things not being there
[07:26] <elfy> oh - well no need for me to hear anymore then :)
[07:26] <ochosi> i mean i personally use it, but i'm not sure it's best for default
[07:27] <ochosi> well i encourage you to give it a try though, it might develop into something we might wanna ship a bit later
[07:27] <elfy> apparently BT does do imap
[07:30] <ochosi> there you go, BT transitioned into the 2000s
[07:31] <elfy> don't blame me - my cynicism is well founded re them :D
[07:31] <elfy> currently ALL my *buntu mail is pop3
[07:32] <ochosi> wowza
[07:35] <elfy> I'll look at that later on today
[07:35] <elfy> but anyway I digress - no addressbook nor pgp would mean a massive -1 from me
[07:36] <Unit193> Strong -1 indeed.
[07:44] <elfy> not changing to imap "you need to be aware that any local folder structure you might have set up within POP will be lost when you make the change"
[09:00] <elfy> well for better or worse - I added the staging ppa now
[09:00] <elfy> seems to be the only one with vivid :)
[09:27] <ochosi> hmm, i gotta check what version of gnutls is in vivid
[09:27] <ochosi> but i guess same as utopic
[09:27] <ochosi> might have to move forward soon, claws-mail isn't working anymore due to SSL3 POODLE bug
[09:28] <elfy> no version in vivid currently seemingly
[09:58] <ochosi> bluesabre: have you seen that recent docs view of evince yet? i never noticed that... could be fun to add something like that for parole
[11:03] <bluesabre> ochosi: haven't seen it
[11:03] <bluesabre> you guys make my job easy, geary is not ready for xubuntu :)
[11:04] <elfy> hi bluesabre :)
[11:06] <elfy> bluesabre: thanks for getting the staging ppa vivid ready :)
[11:07] <bluesabre> elfy: np... there might be a few packages I'll need to rebuild so they are vivid-ready... I'll take care of those tonight
[11:07] <elfy> okey doke
[11:08] <bluesabre> I'll also update branches to get ready for vivid, unless ochosi wants to do it
[11:08] <bluesabre> clone trunk to make a utopic branch, etc
[11:08] <elfy> am I going to need any other ppas's - shimmer etc?
[11:08] <elfy> really don't want to have to use more than 1 tbh - but will if I have to
[11:09] <bluesabre> depends on what we decide, we can easily add shimmer/artwork/settings daily builds to -staging as well
[11:09] <bluesabre> I just need the go/nogo
[11:09] <elfy> perhaps include this while chatting tomorrow
[11:09] <bluesabre> yup
[11:10] <elfy> and I opened synaptic to do something and now I can't remember what ...
[11:10] <bluesabre> :)
[11:10] <elfy> it wouldn't be so bad if it was longer than 2 minutes ago lol
[11:10] <bluesabre> :D
[11:11] <bluesabre> anyway, gotta run, heading out to Ohio LinuxFest today, so got a bit of a drive ahead of me
[11:11] <bluesabre> seeya
[11:11] <elfy> safe driving :)
[11:11] <elfy> cya
[11:13] <elfy> ahah I remember now
[11:31]  * ochosi is playing with thunar to get a better free-space indicator in the props dialog... http://www.zimagez.com/zimage/screenshot-2014-10-25-133057.php
[11:32] <elfy> ooh - shiny :)
[11:36] <elfy> hi brainwash
[11:37] <brainwash> hey elfy
[11:39] <brainwash> I'm still curious.. was apport disabled during the utopic beta phase?
[11:39] <brainwash> usually we get quite few apport reports
[11:40] <brainwash> thunar, tumbler, and so on are known to crash a lot :)
[11:43] <elfy> apport does get turned off
[11:43] <elfy> can't remember when
[11:44] <elfy> though I did think it's at release
[11:57] <Unit193> bluesabre: Oh right, the s/evince/evince-gtk/ thing.
[11:58] <knome> should be at release, maybe somebody forgot to turn it off. poke -release maybe?
[13:43] <elfy> brainwash: :)
[14:53] <ali1234> ochosi: someone is reporting black background on messages in evolution again, wasn't that fixed?
[14:53] <ochosi> ali1234: that happens time and time again, they use lotsa custom widgetry
[14:54] <ali1234> http://postimg.org/image/jkgss9l0f/
[14:54] <ochosi> yeah, those things have happened previously
[14:54] <ochosi> frankly, i've never found a real solution
[14:55] <ochosi> one could look into evolution's source-code and try to find out what's the offending part
[14:55] <ali1234> this is with 14.04
[14:55] <ochosi> and stock evolution?
[14:55] <ochosi> or newer version
[14:55] <ali1234> afaik yes
[14:55] <ali1234> just things from repos
[14:57] <ochosi> supposedly that issue was fixed (brainwash just pasted the link over there)
[14:57] <brainwash> fixed in greybird
[14:57] <ali1234> over there?
[14:58] <brainwash> #xubuntu
[14:58] <ali1234> oh, well, it was reported in #ubuntu-uk :)
[14:59] <brainwash> this link https://github.com/shimmerproject/Greybird/issues/40
[14:59] <brainwash> maybe the same guy :)
[14:59] <ali1234> and i'm not currently on #xubuntu, unless the same person is reporting it there?
[14:59] <brainwash> is it safiyyah?
[14:59] <ali1234> yeah
[15:01] <ali1234> so is this just an issue of not being fully up to date, or did this fix never land in 14.04?
[15:04] <brainwash> I have no clue
[15:05] <brainwash> was the fix every applied to bluebird, that is the question
[15:21] <ochosi> i haven't maintained bluebird as actively in this respect
[15:21] <ochosi> simply because it's not our default theme and time is limited
[20:17] <elfy> knome: started and even had a go with the voodoo :p http://pad.ubuntu.com/upgrading
[20:29] <ochosi> elfy: looks great!
[20:29] <ochosi> hope you don't mind that i messed a bit with some of the formulations
[20:31] <elfy> ochosi: not in the slightest - it was all *stuff* to me :D
[20:32] <elfy> oic
[20:32] <elfy> I thought you meant all the <para> stuff :D
[20:32] <ochosi> :)
[20:32] <ochosi> looks good though, i read through the non-markup part now
[20:33] <ochosi> i think that'll be quite useful for people
[20:33] <ochosi> maybe we even get more testers with that info out there
[20:33] <elfy> which I've not really got any idea it it's right - though I *think* it's nearly right at least :D
[20:34] <elfy> synced the marked up bit
[20:38] <elfy> ochosi: as far as testing is concerned - every little helps :)
[20:56] <elfy> another jpg opens in gimp bug ;)
[21:08] <brainwash> how is it different?
[21:08] <brainwash> oh, do you mean another bug report (dupe)?
[21:08] <elfy> yea lol - marked it dupe
[21:09] <brainwash> ok
[21:10] <brainwash> it can be fixed, not sure if bluesabre has added it to his todo list
[21:11] <elfy> no idea - once we've got blueprints up we can start listing bugs we can deal with again
[21:11] <brainwash> sru team should stop slacking and release the updates for xfce4-weather-plugin and xfdesktop4 (trusty)
[21:11] <brainwash> =S
[21:14] <brainwash> I am not worried about the open with bug in utopic, but the quality of the lts release should be increased, delaying package updates does not help
[21:16] <elfy> probably not, but unless you've got a magic wand - they get done when they do ;)
[21:24] <elfy> done for Saturday - night all :)


[16:01] <smoser> o./
[16:01] <hallyn_> arosales is up today?
[16:01] <gnuoy> o/
[16:01] <arosales> o/
[16:02] <arosales> ah sorry I didn't update the rotate order, but I am happy to host today
[16:02] <arosales> I guess that should be my penance since I didn't udpate the rotate order
[16:02] <coreycb> o/
[16:02] <jamespage> o/
[16:03]  * arosales gets instructions
[16:03] <arosales> alright, lets rock
[16:03] <arosales> #startmeeting ubuntu-server-team
[16:03] <meetingology> Meeting started Tue Mar  3 16:03:31 2015 UTC.  The chair is arosales. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:03] <meetingology> Available commands: action commands idea info link nick
[16:03] <arosales> #topic Review ACTION points from previous meeting
[16:03] <matsubara> o/
[16:03] <gaughen> \o   o/     \o
[16:04] <kickinz1> o/
[16:04] <arosales> non that I see from last week
[16:04] <arosales> #topic Vivid Development
[16:04] <arosales> #link https://wiki.ubuntu.com/VividVervet/ReleaseSchedule
[16:05] <strikov> o/
[16:06] <arosales> #info Final Beta Freeze, Warning /!\ Final Beta Mar
[16:06] <smoser> Mar ...
[16:06] <smoser> insert day of month here.
[16:06] <arosales> #info Final Beta Freeze, Warning /!\ Final Beta Mar 25
[16:06] <arosales> #info UserInterFaceFreeze on March 12
[16:06] <jamespage> that's not far off
[16:07] <arosales> right around the corner
[16:07] <jamespage> indeed
[16:07] <arosales> #subtopic Release Bugs
[16:07] <arosales> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-v-tracking-bug-tasks.html#ubuntu-server
[16:08] <arosales> hmm that isn't loading for me atm, is it working for others?
[16:08] <arosales> smoser: ^ that link work for you?
[16:09] <gnuoy> not working for me
[16:09] <arosales> #action smoser follow up on #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-v-tracking-bug-tasks.html#ubuntu-server not working
[16:09] <meetingology> ACTION: smoser follow up on #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-v-tracking-bug-tasks.html#ubuntu-server not working
[16:09] <smoser> arosales, thanks
[16:09] <arosales> we'll cover some bugs later, but any release tracking bugs we should discuss now?
[16:10] <arosales> ok, moving on
[16:10] <arosales> #subtopic Blueprints
[16:10] <arosales> #link http://status.ubuntu.com/ubuntu-v/group/topic-v-server.html
[16:11] <arosales> #link https://blueprints.launchpad.net/ubuntu/+spec/servercloud-v-server-core
[16:11] <arosales> 3 blueprints, all red atm
[16:12] <arosales> hmm don't see rbask here atm
[16:12] <arosales> smoser: work in this BP look to be updated and in progress?
[16:12] <smoser> i'll take a look at that.
[16:12] <arosales> smoser: thanks
[16:12] <smoser> and get it into orde.r
[16:13] <arosales> smoser: thank you sir
[16:13] <arosales> zul: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-v-openstack-kilo
[16:13] <arosales> up to date and on track?
[16:13] <arosales> #link https://blueprints.launchpad.net/ubuntu/+spec/servercloud-v-openstack-kilo
[16:13] <zul> on track not up to date
[16:13] <arosales> good to hear on track, if you have a spare moment could you update?
[16:14] <arosales> #link https://blueprints.launchpad.net/ubuntu/+spec/servercloud-v-openstack-charms
[16:14] <arosales> gnuoy: up to date and on track ^
[16:14] <gnuoy> up to date, yes. on track ...hmmmm
[16:14] <arosales> A few todos there, that I think you were prioritizing
[16:14] <gnuoy> absolutely
[16:14] <arosales> gnuoy: thanks
[16:14] <arosales> those are the three BPs out there
[16:16] <arosales> hmm, there are a couple more out at the spec, but not in status
[16:16] <arosales> #link https://blueprints.launchpad.net/ubuntu/+spec/servercloud-v-cloud-init
[16:16] <arosales> smoser: no work items there
[16:17] <smoser> updating
[16:17] <arosales> smoser: thanks
[16:17] <arosales> #link https://blueprints.launchpad.net/ubuntu/+spec/servercloud-v-osci
[16:17] <arosales> was the other
[16:17] <arosales> beisner: ^ no work items there either
[16:18] <arosales> that looks like the 5 BPs for the vivid cycle
[16:18] <arosales> #topic Server & Cloud Bugs (caribou)
[16:18] <caribou> arosales: nothing from the CTS side this week
[16:18] <arosales> caribou: ok, thanks
[16:18] <arosales> #topic Weekly Updates & Questions for the QA Team (psivaa)
[16:19] <hallyn_> thought there was an action to update that
[16:20] <arosales> hallyn_  that was my action I missed. I'll update.
[16:20] <arosales> hallyn_: to confirm who was the correct qa rep?
[16:20] <arosales> #action arosales update QA Team rep
[16:20] <meetingology> ACTION: arosales update QA Team rep
[16:20] <arosales> #topic Ubuntu Server Team Events
[16:21] <arosales> Any events (meetups, conferences) folks would liketo call out here?
[16:21] <hallyn_> arosales: was it beisner wh owas going to take over?
[16:21] <arosales> hallyn_: I think you may be riht
[16:21] <arosales> *right
[16:21] <smb> arosales, I have nothing this week, just in case. :)
[16:21] <arosales> smb: apologies, sorry skipped over that link :-/
[16:21] <arosales> #topic Weekly Updates & Questions for the Kernel Team (smb, sforshee, arges)
[16:22] <beisner> hi hallyn_, matsubara will be the contact
[16:22] <smb> arosales, I have nothing this week anyway :)
[16:22] <arosales> #info no updates from Kernel team (smb)
[16:22] <arosales> smb thanks
[16:22] <hallyn_> beisner: thx :)
[16:22] <arosales> #action arosales update QA Team rep to matsubara
[16:22] <meetingology> ACTION: arosales update QA Team rep to matsubara
[16:23] <arosales> re: Events
[16:23] <beisner> arosales, re: blueprint - will move workitems from a diff bp asap.
[16:23] <arosales> MWC is this week
[16:23] <arosales> beisner: thank you
[16:23] <arosales> Ubuntu booth @ MWC https://lh3.googleusercontent.com/-ATkXumIdXKw/VPQGak11pwI/AAAAAAAAJhI/6Kg-F5sxch8/w1598-h614-no/IMG_0943.JPG
[16:24] <arosales> if folks are in Spain be sure to check it out
[16:25] <arosales> OpenPower summit coming up on the 16th of March if folks are in the San Jose area
[16:25] <arosales> http://openpowerfoundation.org/2015-summit/
[16:25] <arosales> #link http://openpowerfoundation.org/2015-summit/
[16:25] <arosales> thats the ones I know of that are coming up.
[16:25] <arosales> #topic Open Discussion
[16:25] <arosales> Any other topics?
[16:26] <arosales> I'll take it we covered the relevant bits
[16:26] <arosales> smb:  apologies agains for skipping over kernel team's update, thanks for the renider
[16:26] <arosales> *reminder
[16:26] <arosales> #topic Announce next meeting date and time
[16:26] <smb> arosales, No worries :)
[16:27] <arosales> smb: thanks
[16:27] <arosales> #info Tuesday 2015-03-10 at 1600 UTC
[16:27] <arosales> thanks for joining
[16:28] <arosales> #endmeeting
[16:28] <hallyn_> thx arosales \o
[16:28] <meetingology> Meeting ended Tue Mar  3 16:28:04 2015 UTC.
[16:28] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-03-03-16.03.moin.txt
[16:28] <gnuoy> thanks arosales
[16:28] <kickinz1> Thanks
[16:28] <caribou> thanks arosales
[16:28] <arosales> np, /me will be sure to udpate the wiki this time :-)
[16:29] <matsubara> thanks arosales
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ##
[17:00] <meetingology> Meeting started Tue Mar  3 17:00:30 2015 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available commands: action commands idea info link nick
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Vivid
[17:00] <ppisati> o/
[17:00] <ogasawara> o/
[17:00] <henrix> o/
[17:00] <sforshee> o/
[17:00] <bjf> o/
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Status: Vivid Development Kernel (ogasawara)
[17:01] <ogasawara> We have officially uploaded our v3.19 kernel for Vivid to the archive,
[17:01] <ogasawara> ie. 3.19.0-7.7.  Please test and let us know your results.
[17:01] <ogasawara> This is also an early reminder that kernel freeze for Vivid is on Thurs
[17:01] <ogasawara> Apr 9.  If you have any patches which need to land for 15.04's release,
[17:01] <ogasawara> please make sure to submit those sooner rather than later.
[17:01] <ogasawara> -----
[17:01] <ogasawara> Important upcoming dates:
[17:01] <ogasawara> [LINK] https://wiki.ubuntu.com/VividVervet/ReleaseSchedule
[17:01] <ogasawara> Thurs Mar 26 - Final Beta (~3 weeks away)
[17:01] <ogasawara> Thurs Apr 09 - Kernel Freeze (~5 weeks away)
[17:01] <ogasawara> Thurs Apr 23 - 15.04 Release (~7 weeks away)
[17:01] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: CVE's
[17:02] <jsalisbury> The current CVE status can be reviewed at the following link:
[17:02] <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:02] <jsalisbury> ..
[17:02] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Utopic/Trusty/Precise/Lucid (bjf/henrix/kamal/arges)
[17:02] <bjf> Status for the main kernels, until today:
[17:02] <bjf>   *   Lucid - Kernel Prep
[17:02] <bjf>   * Precise - Kernel Prep
[17:02] <bjf>   *  Trusty - Kernel Prep
[17:02] <bjf>   *  Utopic - Kernel Prep
[17:02] <bjf>
[17:02] <bjf> Current opened tracking bugs details:
[17:02] <bjf>   * http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
[17:02] <bjf> For SRUs, SRU report is a good source of information:
[17:02] <bjf>   * http://kernel.ubuntu.com/sru/sru-report.html
[17:02] <bjf>
[17:02] <bjf>
[17:02] <bjf> Schedule:
[17:02] <bjf>
[17:02] <bjf> cycle: 27-Feb through 21-Mar
[17:02] <bjf> [17:02] <bjf>          27-Feb   Last day for kernel commits for this cycle
[17:02] <bjf> 01-Mar - 07-Mar   Kernel prep week.
[17:02] <bjf> 08-Mar - 21-Mar   Bug verification; Regression testing; Release
[17:02] <bjf>
[17:02] <bjf> ..
[17:03] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:03] <jsalisbury> Thanks everyone
[17:03] <jsalisbury> #endmeeting
[17:03] <meetingology> Meeting ended Tue Mar  3 17:03:24 2015 UTC.
[17:03] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2015/ubuntu-meeting.2015-03-03-17.00.moin.txt
[17:03] <cking> thanks jsalisbury


[07:48] <studio-user279> im curious about what kind of issues people aer having after they have completed the 17.04 update
[18:16] <studio-user697> hello
[18:17] <studio-user697> I be havin some trouble with upgrade from 16.04 to 17
[18:18] <studio-user697> this is what I got in my dmesg
[18:18] <studio-user697> [    0.000000] Linux version 4.4.0-92-lowlatency (buildd@lcy01-17) (gcc version  5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #115-Ubuntu SMP PREEMPT Thu Aug  10 09:53:57 UTC 2017 (Ubuntu 4.4.0-92.115-lowlatency 4.4.76)
[18:19] <studio-user697> today i went into software and did a complete update on everything which also listed OS update
[18:19] <studio-user697> after rebooting, my DMESG is still the same
[18:19] <studio-user697> what did I miss?
[18:22] <studio-user697> software updater says:   The Software on this computer is UP TO DATE
[18:23] <krytarik> !upgradeofflts | studio-user697
[18:24] <studio-user697> ok thanks that was informative
[18:24] <krytarik> You are welcome.
[18:25] <studio-user697> i was jsut looking at Long Term vs non-LTS
[18:25] <studio-user697> and I dont knwo that I NEED to upgrade but I have been getting some repeat system errors
[18:25] <studio-user697> I am concerned that the upgrade to 17 might Break something
[18:27] <studio-user697> having annoyances with VLC crashing and far too aftern the delayed response after a mouse click to open a menu or soemthing has become rather annoying aswell
[18:28] <studio-user697> I would like to know if any hardware support was dropped from 16 to 17
[18:28] <krytarik> Just try with a Live image if everything works still.
[18:29] <studio-user697> and is there any significant changes to software being used like the file manager or Window Manger or Desktop Manage
[18:30] <studio-user697> thats a good idea to run a live dvd for a bit.
[18:30] <studio-user697> but it is very time consuming
[18:41] <studio-user697> having reviewed the change log I see that file manger repalced with THUNAR is having some annoyances and so is Parole
[18:42] <studio-user697> SO I think I will try and wait till january for LTS upgrade
[18:48] <OvenWerks> studio-user697: it is unlikely that the file manager or media player will change for the next LTS
[18:49] <OvenWerks> Thunar has been a part of Studio for a few years now since nautilus has been reduced in functionality.
[18:50] <OvenWerks> The gnome media player seems to break every other release.
[18:51] <OvenWerks> However, the idea of having a choice is that the user can install whatever filemanager/media player(s) <add list here> they enjoy using.
[19:11] <studio-user697> thank you OvenWerks
[19:13] <studio-user697> I wonder is it viable to run two different file manager? like I have 3 media palyers that I run simultaneously, parole, VLC and SMPlayer
[20:35] <OvenWerks> of course, you can run more than one file manager. The desktop will continue to be thunar... maybe ask on #xubuntu how to change that part.