[05:15] <juergh> @johang Debian just ships the upstream kernel and you'll get whatever support for Pi there is. Ubuntu adds a couple hundred additional patches from the pi foundation on top that give you support for additional HATs, bug fixes, enhancements, what not. We don't want all of that in the generic kernel hence the raspi flavor.
[08:14] <LocutusOfBorg> hello xnox and ubuntu kernel developers!
[08:14] <LocutusOfBorg> do you have any plan for LP: #1215411 ?
[08:14] -ubottu:#ubuntu-kernel- Launchpad bug 1215411 in linux (Ubuntu) "libcpupower.so is not installed from linux-tools" [Medium, In Progress] https://launchpad.net/bugs/1215411
[09:34] <johang> juergh: thanks for the explanation


[00:21] <nosmelc> I was wondering if many people use Lubuntu on non-low-end machines?
[00:22] <ianorlin> yes there is a 64 bit version for that if you want it
[00:22] <ianorlin> I run it sometimes on a laptop with 4 gb of ram and a core 2 duo
[00:23] <nosmelc> ianorlin: I installed it on a Core 2 Duo with 6GB of memory and it worked great
[09:37]  * one sighs
[09:49] <one> Baby I'm your man...
[09:50] <one> don't fear the reaper
[11:59] <Little-Chip> hello?
[12:02] <Little-Chip> some problem with my computer when I power on... I have to force turn off my wlan...  if not I will get shutdown...
[13:59] <dovah> hello can someone help me with my graphics drivers
[13:59] <dovah> im having trouble. i need to switch back to the fallback graphics drivers like the ones that the installer disk uses
[14:00] <dovah> the screen looks fine with the installation but after install and after restart i can only get 640 x 480 and the screen has artifacts
[14:17] <vn151502510> dovah: Start menu -> Preferences -> Monitor Settings could have any luck?
[14:18] <dovah> vn151502510, i tried alls i get is 640
[14:19] <dovah> by 480
[14:19] <dovah> but with live cd i get full resolution
[14:19] <dovah> i wanted to maybe use the drivers the live cd uses
[14:20] <vn151502510> so u have only one option of Resolution? 640x480
[14:20] <dovah> yes
[14:21] <vn151502510> could you try command `xrandr`
[14:21] <vn151502510> and get the output
[14:21] <dovah> i dont know that command
[14:21] <dovah> k hold on
[14:21] <dovah> its on another pc
[14:27] <dovah> hey vn151502510 im going to try this other thing thanks for help
[21:07] <llogiq> Hi folks.
[21:09] <llogiq> I have a problem with a Lubuntu 13.10 (recently upgraded from 12.10). The lxpanel does not show up after logging in. When I manually start it (lxpanel --profile Lubuntu &), it appears to work.  Also the xfce4-power-manager is not started with the session. Does anyone know where to look?
[21:50] <holstein> llogiq: i would try using a different user to rule out issue with the user configuration files
[21:50] <holstein> llogiq: you can purge those in that user, if you find them to be the issue
[21:51] <llogiq> holstein, I already checked with two users. Then I purged .config/lxpanel. lxpanelctl restart and the (manually started) panel vanishes.
[21:52] <llogiq> So perhaps it has something to do with the session?
[21:52] <llogiq> By the way, my terminal tells me that lxpanel segfaulted.
[21:55] <llogiq> If I strace lxpanelctl I get a lot of EAGAINs.
[21:55] <llogiq> So it could have something to do with a lower level component...does lxpanel use DBus?
[21:56] <llogiq> dbus service is running.
[22:15] <phillw> llogiq: accept the invitation :)


[00:23] <Unit193> Wonder why Google is getting into screenlockers.
[01:04] <bluesabre> Might be related to their adding Linux applications to Chrome OS
[01:24] -SwissBot:#xubuntu-devel- ::xfce4-announce:: ANNOUNCE: exo 0.12.6 released @ http://xfce.10915.n7.nabble.com/ANNOUNCE-exo-0-12-6-released-tp54115.html (by Sean Davis-6)
[06:14] <ochosi> Unit193: indeed, quite interesting
[09:08] <bluesabre> !team | Reminder, Xubuntu Community Meeting tonight at 22:00 UTC, hope to see at least a few of you there
[09:10] <knome> i will *try* :)
[09:23] <Unit193> I'll be here unless I'm not.
[09:24] <bluesabre> :)
[09:25] <bluesabre> Improving snap appearance in Xubuntu, https://twitter.com/m_wimpress/status/1139376489445486594 (something I'll be looking at this weekend)
[21:29] <bluesabre> evening all
[21:31] <bluesabre> !team | Xubuntu Community Meeting in 30 minutes :)
[21:58] <knome> bluesabre, i'm kind of here..
[21:59] <bluesabre> knome: yay!
[21:59] <bluesabre> Anybody else nearby?
[22:00] <bluesabre> #startmeeting Xubuntu Community Meeting
[22:00] <meetingology> Meeting started Fri Jun 14 22:00:27 2019 UTC.  The chair is bluesabre. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[22:00] <meetingology> Available commands: action commands idea info link nick
[22:00] <bluesabre> Here we go
[22:00] <bluesabre> #chair knome
[22:00] <meetingology> Current chairs: bluesabre knome
[22:00]  * bluesabre hopes other people are around
[22:02] <Unit193> I'll be a bit, sorry.
[22:02] <bluesabre> Unit193: np, long bit, short bit?
[22:02] <bluesabre> Eickmeyer: don't suppose you're around?
[22:03] <pleia2> oh, hello
[22:03] <bluesabre> Might be a quick meeting :D
[22:03] <bluesabre> woohoo!
[22:04] <bluesabre> I'll wait just a bit longer (putting notes together anyway)
[22:04] <Eickmeyer> I'm around.
[22:04] <bluesabre> Nice
[22:04]  * Eickmeyer totally didn't mark his calendar
[22:05] <knome> calendar? what's that? ;)
[22:05] <bluesabre> :)
[22:05] <bluesabre> Guess we'll go ahead
[22:06] <bluesabre> #topic Open action items
[22:06] <bluesabre> The last meeting was quite a while ago, and all the action items were done.
[22:06] <pleia2> that's one way to do it
[22:06] <bluesabre> Oh,  agenda is at https://wiki.ubuntu.com/Xubuntu/Meetings
[22:07] <bluesabre> #topic Updates and announcements
[22:07] <bluesabre> #info Xfce 4.14 to be released August 11, 2019 (in time for Eoan)
[22:08] <bluesabre> #info flocculant (Kev) has left the position of QA lead / Xubuntu Council (thanks for all the years of help)
[22:08] <knome> that's fantastic news.
[22:08] <knome> ...the xfce release, that is
[22:08] <bluesabre> #info ochosi (Simon) has filled the remaining Xubuntu Council position following a team vote
[22:08] <bluesabre> knome: indeed
[22:08] <bluesabre> Everybody should be pumped for Xfce 4.14 :)
[22:09]  * Eickmeyer gives a woot woot
[22:09] <bluesabre> #info jjfrv8 (Jack) has officially left the Xubuntu Team (thanks for all the help, take care!)
[22:09] <bluesabre> Any other announcements?
[22:12] <bluesabre> Moving on... :-)
[22:12] <bluesabre> #topic Discussion
[22:12] <bluesabre> #subtopic Replacing Light Locker with Xfce Screensaver
[22:12] <bluesabre> This is something that we discussed for Disco, but we didn't quite make it to.
[22:13] <bluesabre> I think the screensaver is now in a position to replace light-locker... so unless there are any objections, I think we can move forward with this.
[22:13] <bluesabre> Should we send this to a vote, or move it along?
[22:13] <Eickmeyer> This is something I'm all for doing for Studio. Light Locker and xscreensaver have been virtually unusable.
[22:14] <pleia2> sounds fine to me
[22:15] <knome> if it's indeed in a stable enough state, then sure, let's go for it
[22:15] <knome> maybe it gets more love because it's now named like a serious xfce component ;)
[22:16] <bluesabre> :)
[22:16] <bluesabre> Then we'll do just that.
[22:16] <bluesabre> #action bluesabre to replace light-locker with xfce4-screensaver in eoan
[22:16] <meetingology> ACTION: bluesabre to replace light-locker with xfce4-screensaver in eoan
[22:17] <bluesabre> #subtopic Including additional keyboard shortcuts common to other desktops / OSes
[22:17] <bluesabre> This is something I'm interested in doing to ease new users or cross-desktop users into Xubuntu
[22:17] <bluesabre> A couple examples that seem pretty ubiquitous
[22:18] <bluesabre> - Super+L to lock the screen
[22:18] <knome> what kind of scope are we talking about?
[22:18] <bluesabre> - Super+D to show the desktop
[22:18] <bluesabre> desktop environment scope, largely
[22:18] <bluesabre> We improved the per-application scope in disco
[22:18] <Eickmeyer> That's a tricky one, especially when it comes to invoking whisker with Super alone, which I realize isn't the default.
[22:18] <knome> sure, that makes sense and isn't completely different what we do now
[22:19] <Eickmeyer> But people expect it.
[22:19] <bluesabre> Yeah, and we can't currently do since we have other Super+ shortcuts
[22:19] <Eickmeyer> Exactly.
[22:19] <bluesabre> (due to Xfce limitations)
[22:19] <Eickmeyer> It's too bad it's not evoked on keyup.
[22:19] <Eickmeyer> er, invoked. :P
[22:20] <Spass> Super+Space would be pretty good too IMHO, like in elementary OS
[22:20] <Eickmeyer> That's not a bad idea.
[22:20] <Spass> And Super+L and Super+D would be great additions, also IMHO :)
[22:21] <bluesabre> :)
[22:22] <bluesabre> I'm guessing this is one that would likely warrant a team vote, but it's also pretty painless to at least swap in the D and L shortcuts
[22:22] <bluesabre> Spass: what's Super+Space do in elementary? App launcher?
[22:23] <knome> super+D/L are probably something we can just drop in, the menu shortcut thing is probably a bit too "core" for that
[22:23] <Spass> Yes, iirc, so it would be good for a Whisker Menu
[22:23] <pleia2> if it doesn't clobber any existing defaults, I don't see this as disruptive
[22:24] <bluesabre> Yeah, pretty sure it does not
[22:24] <pleia2> makes sense to me then :)
[22:24] <knome> i'd personally avoid super+space because it just feels too frustrating/wrong (compared to just super) and i don't want to frustrate our users
[22:24] <bluesabre> And Super+Space is easily more reachable than Super+Esc
[22:25] <bluesabre> knome: good point
[22:25] <Eickmeyer> Another one I've heard suggested is Super+Z
[22:25] <Spass> bluesabre, you mean Ctrl+Esc?
[22:25] <bluesabre> Spass: yeah, that's what I meant
[22:25] <pleia2> maybe put together a list of proposals from everyone and finalize at future meeting?
[22:25] <bluesabre> pleia2: yeah, I think that's a good idea
[22:26] <bluesabre> I'll send this off to the ML
[22:26] <knome> yep, mailing list thread sounds fair.
[22:26] <bluesabre> #action bluesabre to mail the mailing list to discuss additional keyboard shortcuts
[22:26] <meetingology> ACTION: bluesabre to mail the mailing list to discuss additional keyboard shortcuts
[22:26] <Spass> Are you thinking about replacing current ones or just adding another working shortcuts?
[22:27] <bluesabre> Spass: just adding
[22:27] <bluesabre> Spass: but also, always open to proposals
[22:27] <Spass> Cool
[22:27] <bluesabre> Moving on to the next subtopic :)
[22:27] <bluesabre> #subtopic Configuring GIMP to use the GTK theme (instead of dark)
[22:28] <bluesabre> (theming things always bring plenty of opinions, but)
[22:28] <bluesabre> We added GIMP back to Xubuntu during the last development cycle.
[22:28] <bluesabre> The new GIMP appearance default is a dark background and monochrome icons.
[22:28] <bluesabre> I propose we set this to use the GTK theme and color icon theme (in the name of desktop consistency)
[22:29] <knome> doesn't all image editing software do that now
[22:29] <Eickmeyer> Studio will probably pass on this as more pro artists tend to prefer a medium- to dark-gray.
[22:29] <bluesabre> knome: probably
[22:29] <knome> but yes, i agree with keeping the GTK theme especially if it's "supported" - meaning we don't end up with broken-looking software
[22:31] <bluesabre> Eickmeyer: yeah, and that makes sense for Studio. Since Xubuntu doesn't really target a pro/creative audience, I think the GTK theme option might be a better fit for us.
[22:33] <bluesabre> My question is, should we roll with that distinction, or send it to a M/L vote?
[22:34] <Spass> As a user, I also agree that GTK+Color would look better overall in Xubuntu (so +1 for that), but yeah, I know that some people will not like that.
[22:34] <bluesabre> (Sorry my meetings are always, hey team, can I do this?) :D
[22:34] <Spass> (I know that I don;t really have a vote here, but it's just a small feedback, hope you don't mind that)
[22:35] <bluesabre> Spass: don't mind that at all, it is a community meeting after all :)
[22:36] <bluesabre> Suppose I'll send this along to the team for a vote to be fair
[22:37] <knome> well, the other side is that gimp used to be GTK
[22:37] <knome> so wouldn't the change to the medium gray need the approval :P
[22:37] <bluesabre> Yeah, GTK theme used to be "default"
[22:37] <bluesabre> :D
[22:38] <Spass> Good point :)
[22:38] <bluesabre> #action bluesabre to mail the team regarding the GTK styles in GIMP (noting GTK used to be default)
[22:38] <meetingology> ACTION: bluesabre to mail the team regarding the GTK styles in GIMP (noting GTK used to be default)
[22:38] <bluesabre> :)
[22:38] <knome> good good
[22:38] <bluesabre> And now onto something more divisive
[22:38] <bluesabre> #subtopic Color emoji in Xubuntu
[22:39] <bluesabre> We visited the idea of color emoji in the past and determined that we should continue to use non-color emoji at the time, citing the GTK2 Xfce desktop and other toolkits.
[22:39] <bluesabre> Since Xfce 4.14 is imminent and ships with GTK3 (and the non-color emoji is difficult to see, at least for me), I'd like to propose shipping with color emoji by default.
[22:39] <knome> do you have any evidence of hard-to-see monochrome emojis in context?
[22:40] <bluesabre> I'll need to put together some screenshots
[22:40] <bluesabre> I've personally switched after not being able to decipher my barrage of email notifications containing emoji
[22:40] <bluesabre> (why are they everywhere now?)
[22:41] <knome> you are emailing with the wrong people?
[22:41] <Spass> I remember that I've sent some before here, but can't find it now.
[22:41] <bluesabre> In any case, this is something that would require a team vote, so this is more of a heads up :D
[22:41] <knome> yes
[22:41] <Spass> iirc I've proposed that for Disco
[22:42] <bluesabre> Spass: yes, I think I recall that
[22:42] <knome> yep.
[22:42] <pleia2> it's time for them
[22:43] <Unit193> Heh, I guess I'm the only one that reamins -1.
[22:43] <bluesabre> :)
[22:43] <Unit193> Remains, rather.
[22:43] <knome> Unit193, not really. but then again, i don't really use any emoji at all.
[22:43] <bluesabre> Anyway, I'll be sending this to a vote in the M/L, so be sure to reply there so can we collectively +1/-1 :D
[22:43] <knome> i can be persuaded to +1'ing :P
[22:43] <pleia2> imma vote with emojis
[22:44] <bluesabre> #action bluesabre to email a team vote for color emoji support in Xubuntu
[22:44] <meetingology> ACTION: bluesabre to email a team vote for color emoji support in Xubuntu
[22:44] <knome> i'll vote -1 and then hack the mailing list so nobody else gets their votes through
[22:44] <knome> (:
[22:44] <bluesabre> pleia2: lol
[22:45] <bluesabre> knome: how very 😏 of you
[22:45] <Eickmeyer> It's just the state the world is in now. You either move with it or break from it.
[22:45] <bluesabre> Yeah
[22:45] <knome> bluesabre, that just looks like a circle to me in my IRC client. it could be a watermelon or... something completely different.
[22:46] <bluesabre> knome, hence bringing it up ;)
[22:46] <bluesabre> Next subtopic...
[22:46] <bluesabre> #subtopic Expanding membership
[22:46] <Eickmeyer> knome: He could be flipping you off and you'd never know it. ;)
[22:47] <bluesabre> lol
[22:47] <bluesabre> So, our team has been getting a bit smaller/quiter as of late, so Unit193 and I reached to out check on some folks...
[22:47] <knome> Eickmeyer, i'm happy i've decided to stop caring what other people think over half of my lifetime ago :P
[22:47] <Eickmeyer> hehe
[22:47] <bluesabre> slickymaster (David) isn't going to be very available in the near future, but we may see him pop in here and there.
[22:47] <bluesabre> akxwi-dave (Dave) says he'll be back to help soon.
[22:48] <bluesabre> And also the news about Kev and Jack stepping away.
[22:48] <bluesabre> So, we're down a few more folks than usual. Anybody interested in joining the Xubuntu team, or have ideas on how to expand membership? :D
[22:48] <knome> yeah... to be fair, this doesn't come by surprise; it's now a bit more official/visible than it was before
[22:49] <knome> i mean, those people haven't really been around in the day-to-day stuff even if they might have taken part in the team votes etc.
[22:49] <bluesabre> Indeed
[22:49] <Eickmeyer> Due to our shared DE, do you kinda see the Studio team as a quasi-extension?
[22:50] <bluesabre> So, smaller team, varying workload, not the healthiest of positions right now
[22:50] <bluesabre> Eickmeyer: yeah, definitely. I was hoping to start working with your team more (in general, and because we all need help)
[22:51] <Eickmeyer> Right. I would suggest a partnership on this, especially with matters that are DE-specific, including configuration, but not necessarily theming because we use a different default theme.
[22:52] <knome> Eickmeyer, i think bluesabre is specifically talking about getting new xubuntu team members
[22:52] <bluesabre> Yeah, and we're the last non-GNOME GTK desktops, so there's even less outside help than before
[22:52] <knome> but i'm also happy to get back to xubuntu and ubuntu studio collaboration
[22:53] <bluesabre> Eickmeyer: knome's right, I actually have a separate subtopic for the collaboration :)
[22:53] <knome> bluesabre, otoh, xfce itself is so much healthier than it's been for a long time
[22:53] <Eickmeyer> Ok, then I'll stop jumping ahead.
[22:53] <bluesabre> knome: that's also true
[22:53] <knome> (and a big part of the xubuntu development resources have gone there too)
[22:54] <knome> so potentially after 4.14 and some bugfix releases we might see more manpower available for the xubuntu-specific stuff
[22:54] <knome> given that you and simon are still interested in such things ;)
[22:55] <bluesabre> But as far as Xubuntu goes, we're a bit lacking in QA and documentation these days, which will probably become more of a problem over time
[22:55] <knome> but to get back to the subject and something more concrete...
[22:55] <bluesabre> It definitely helps that Xfce is more alive
[22:55] <knome> lower barrier to entry, somehow
[22:55] <knome> fortunately our documentation is relatively up-to-date
[22:56] <knome> if xfce gets more love in that area, we could try to lean more on that upstream documentation
[22:56] <knome> i don't think we currently interlink the documentation very well there
[22:57] <bluesabre> I think you're right about that
[22:58] <knome> in a sense i feel like with the gtk3 migration and with more xfce components being "what we need" OOTB, xubuntu has become "just another xfce distro" (mostly in a good way)
[22:58] <bluesabre> Fair point
[22:59] <knome> we've always been upstream-friendly, trying to push all of our improvements upstream
[22:59] <Eickmeyer> I would say Xubuntu is the distro people think of when they hear "Xfce".
[22:59] <knome> which pays off in the long run since we do not have a huge pile of code to maintain
[22:59] <knome> but of course there is the QA side, which must be done for xubuntu specifically
[23:00] <bluesabre> So, we're in pretty OK shape in areas other than QA :D
[23:00] <knome> we're... just about ok :P
[23:01] <bluesabre> :)
[23:01] <bluesabre> We live another day/release :)
[23:01] <knome> of course it isn't ideal that most of our teams are just one guy (team lead) and probably one or two of the other core members hanging around and kind of helping with yet another thing
[23:02] <bluesabre> Don't suppose there's any magic pill to get people to join?
[23:02] <pleia2> nope
[23:02] <knome> nah
[23:03] <bluesabre> dang
[23:03] <Eickmeyer> Sadly, no.
[23:03] <knome> this is the same situation xubuntu has been in since i joined in 2008.
[23:03] <bluesabre> In any case, it's good to review and discuss
[23:04] <pleia2> defining discrete tasks and offering mentorship is one method (and has worked some with testing), but it's pretty hands on
[23:04] <knome> it takes time to convince people to start contributing, and when they do, it takes more time to keep them involved enough until they keep maintaining their own motivation up
[23:04] <knome> mentorship indeed
[23:05] <knome> but the issue with that is that it takes a lot of time and there is no guarantee of the outcome
[23:05]  * pleia2 nods
[23:05] <pleia2> we have spent a lot of time on people in the realm of testing who disappeared, and it can get pretty discouraging
[23:05] <Eickmeyer> From the Studio side, I'm having to learn from other teams how to do stuff because nobody is around to mentor me. Which means nobody is around to mentor new people.
[23:05] <pleia2> Eickmeyer: there are only so many people like us :)
[23:07] <Eickmeyer> pleia2: Exactly. I hope to get to the point where I can mentor new people.
[23:08] <knome> i feel like a lot of the mentoring is/can be just being "there" for the other person.
[23:08] <knome> ...once you have somebody that is motivated to do something
[23:09] <knome> we've had a few people telling how they want to help with xubuntu, but they expect us to be something we're not -- and working with open source software to be something it's not
[23:10] <knome> eg. "i really like xubuntu and want to help... please give me a title and send me all of your assets and plans so i can start working"
[23:10] <Eickmeyer> knome: Same for Studio, but on a different scale.
[23:10] <pleia2> that's why discrete tasks help
[23:11] <pleia2> but it takes time and effort to put that sort of thing together, and it's not easy to come up with things that don't require lots of background knowledge
[23:11] <bluesabre> Definitely seems like the place to start investigating though
[23:12] <knome> sure... but then the starting point is already wrong if people expect to get some kind of "value" in return
[23:13] <knome> i can only speak for the areas i work with, but.. if i had the time to put up a very specific plan to so something, i could likely use the time i used to create the documentation to implement the "feature" myself
[23:13] <knome> doing the latter means i know it will get done
[23:13] <pleia2> yeah, that's the thing
[23:13] <pleia2> but it does help long term if someone signs up for it and can do it on their own next time :)
[23:14] <knome> doing the former means there is a very small chance somebody will pick up the pieces and finish it off before the documentation is so rotten that it needs to be rewritten
[23:14] <knome> of course... but where should we draw the line?
[23:14] <pleia2> this is probably a bigger discussion than we can have here right now
[23:14] <Eickmeyer> knome: I'm still cleaning up Studio's documentaton after years of rot/neglect.
[23:14] <bluesabre> I'll work on documenting some starting points for dev/QA so we have better places/resources. I'll also ping the other flavors to see if we can do this with a larger group
[23:15] <knome> take the flyer for example... there will definitely be low hanging fruit in updating it
[23:15] <pleia2> bluesabre: good place to start :)
[23:15] <knome> but if we need to teach the contributor to use the tools to do the changes... meh
[23:15] <Eickmeyer> bluesabre: I like that idea, count me in.
[23:15] <bluesabre> Eickmeyer: will do
[23:16] <Eickmeyer> knome: The Ubuntu wiki's formatting is hard to learn/teach, so I'm right there with you.
[23:16] <bluesabre> #action bluesabre to work on improving "starting point" documentation for dev/QA
[23:16] <meetingology> ACTION: bluesabre to work on improving "starting point" documentation for dev/QA
[23:16] <knome> Eickmeyer, now you lost me with ubuntu wiki ;)
[23:16] <Eickmeyer> knome: XD
[23:16] <knome> but sure, all tools require learning
[23:16] <bluesabre> #action bluesabre to reach out to other flavors to improve shared documentation
[23:16] <meetingology> ACTION: bluesabre to reach out to other flavors to improve shared documentation
[23:17] <bluesabre> knome: and in the case of ubuntu wiki, patience! :D
[23:17] <pleia2> hehe
[23:17]  * Eickmeyer starts throwing stuff at the Ubuntu wiki out of rage
[23:17] <knome> but if you're not motivated to learn the tools yourself, then i don't personally see much "future" for you in the open source world, because mostly it is learning something to be able to do something
[23:18]  * bluesabre nods
[23:18] <knome> i can deal with the ubuntu wiki (it's always been nicer to me than everybody else) ;)
[23:19] <bluesabre> Moving on to the next subtopic
[23:19] <bluesabre> #subtopic QA
[23:19] <bluesabre> We mentioned this before, but with flocculant (Kev) stepping down, we no longer have a QA lead.
[23:20] <knome> i vote for Unit193.
[23:20] <knome> wait, what?
[23:20] <knome> we aren't voting yet?
[23:20] <knome> (:
[23:20] <bluesabre> +1
[23:20] <bluesabre> Oh
[23:20] <Eickmeyer> +1 (Even though my vote doesn't count)
[23:20] <knome> he's the only one around with no team lead hat.
[23:21] <pleia2> hehe
[23:21]  * knome hands Unit193 the clown costume and silly hat
[23:21] <Eickmeyer> hehehe
[23:21] <bluesabre> Obviously we'll want to fill this position soon, but I don't think anybody's currently stepping in to it. So, we might need to drum up some consistent QA contributors first.
[23:21] <bluesabre> All related to the membership discussion above :)
[23:22] <Unit193> knome: I've had a team lead hat for quite some time.
[23:22] <bluesabre> Anything else that needs to be said here meanwhile?
[23:22] <bluesabre> Unit193 is the Debian Liaison :D
[23:22] <knome> liaison, no lead
[23:22] <knome> :P
[23:22] <Unit193> (Still not sure what that is, btw.)
[23:22] <knome> before we have a QA lead, will the council take the role of "leading" the QA efforts?
[23:22] <Eickmeyer> My QA lead is also my Debian liason, so  ¯\_(ツ)_/¯
[23:23] <Eickmeyer> albiet, smaller workload
[23:23] <knome> Unit193, we can switch it to the QA lead hat, i'm pretty sure you know what QA is :P
[23:23] <bluesabre> knome: yeah, council or tech lead... I'm basically going to try to drum up testing interest (and test where possible)
[23:24] <bluesabre> And flocculant has been here and there reporting bugs, thankfully :)
[23:24] <Unit193> knome: Yeah, but TBH I haven't been testing ISOs much for some time, I tend to do some devel testing of course, but just not repeated installs.
[23:25] <knome> fortunately kev left pretty good documentation after him
[23:25] <Unit193> Eickmeyer: I don't know who you have, but what that so far means is that I try and keep Debian Xfce as close to syncable as possible, and maintain Xfce components there.
[23:26] <bluesabre> knome: definitely
[23:26] <bluesabre> Unit193: and you do a great job managing that, so thanks there
[23:26] <Eickmeyer> Unit193: I have Ross (rosco2) and he's one of the Debian Multimeda Team leads. He does the same with the multimedia software.
[23:27] <bluesabre> But yeah, for now I'll at least be keeping an eye on QA and attempting to field testing questions
[23:27] <knome> thanks bluesabre
[23:28] <knome> i'd love to, but unfortunately i don't think i can provide much help with my time and hardware
[23:28] <bluesabre> :)
[23:28] <Unit193> Eickmeyer: I think you mean 'team members' :)
[23:28] <bluesabre> I'm stretching my laptop thin with VMs while I save up for some new hardware :)
[23:28] <Eickmeyer> Unit193: Yeah, must be. I'm still learning that structute. :)
[23:29] <Eickmeyer> *structure
[23:29] <bluesabre> Anyway, we'll continue on to the next subtopic
[23:29] <bluesabre> (thanks for sticking around!)
[23:29] <bluesabre> #subtopic Collaboration with Ubuntu Studio
[23:30]  * Eickmeyer is in bed on his back, so can do nothing BUT stick around
[23:30] <Eickmeyer> And, seeing me talk in here, I bet you're all like, "Who but THIS guy in charge of Ubuntu Studio?!?"
[23:30] <Eickmeyer> *put
[23:31] <bluesabre> Eickmeyer: team vote, mutiny, inheritance? :D
[23:31] <pleia2> we're familiar with leaders becoming leaders by default (or being voluntold, see above)
[23:32] <Eickmeyer> bluesabre: Probably inheritance. I joined the team with intention to contribute, but nobody was leading anything, so I jumped-in and got things organized. That's the Cliff's Notes version of the Reader's Digest version.
[23:32] <knome> Eickmeyer, i bet you were the only one too crazy or clueless of what awaits you to step up for the spot :P
[23:32] <Eickmeyer> knome: Crazy or clueless? Yes.
[23:32] <Eickmeyer> (Inclusive Or)
[23:32] <knome> welcome to the team
[23:32] <pleia2> :D
[23:32] <Eickmeyer> Haha, thanks. :)
[23:32] <knome> err, i mean club
[23:33] <knome> but
[23:33] <knome> eh
[23:33] <knome> whatever
[23:33] <Eickmeyer> hehe
[23:33] <bluesabre> Eickmeyer: I reported some bugs and ochosi pushed me into Xfce and Xubuntu
[23:33] <knome> (2.30am here...)
[23:33] <Unit193> Seems we're getting a little off track.
[23:33] <Eickmeyer> Anyhow...
[23:33] <bluesabre> Unit193: it's all related-ish
[23:33] <knome> bluesabre, ochosi reported some bugs and i pushed him into xfce and xubuntu :P
[23:33] <Eickmeyer> I guess this is something I brought-up in the ML.
[23:34] <bluesabre> Anyway, with Xubuntu and Ubuntu Studio sharing a similar Xfce base (don't ever leave us), we have an opportunity for some collaboration (and better communication)
[23:34] <bluesabre> https://lists.ubuntu.com/archives/xubuntu-devel/2019-May/011793.html
[23:35] <bluesabre> ^ Eickmeyer reaching out with the proposal
[23:35] <knome> this only makes sense; it's been done before and i can't see any negatives on it
[23:35] <Eickmeyer> The example I used was our panel was way-off and still using indicator-* stuff, which I was informed is no longer maintained.
[23:36] <bluesabre> We're definitely open to keeping things more in sync between the 2, since that expands testing on our shared base
[23:36] <Eickmeyer> The team hadn't been informed of using xfce4-pulseaudio-plugin as opposed to xfce4-volumed for volume control.
[23:36] <Eickmeyer> That got me to reach-out to all of you.
[23:37] <Eickmeyer> And, I know we could use the shared resources of knowledge.
[23:37] <bluesabre> Yeah, that one was probably my lack of communication, sorry about that.
[23:37] <Unit193> Pretty sure the indicator stuff is still maintained in the Ubuntuverse.
[23:37] <Eickmeyer> Unit193: I've been informed it is not.
[23:37] <knome> "maintained"
[23:37] <knome> as in, it's still in the repository
[23:37] <Unit193> Eickmeyer: Subscribe to the RSS feeds for xubuntu.seed and xubuntu-default-settings and you're pretty much set, fwiw.
[23:37] <knome> until somebody notices there hasn't been any updates in the last 10 years and drops it.
[23:38] <Eickmeyer> Yes, but as with all things, the indicator stuff will be subject to bitrot.
[23:38] <Eickmeyer> Unit193: Will do.
[23:38] <Unit193> knome: There's push back against the Ayatana stuff because some Ubuntu people think they're still maintaining the indicator stuff properly.
[23:38] <knome> lol
[23:38] <Unit193> That's why we can't sync xfce4-indicator-plugin from Debian, like I'd really really really want to.
[23:38] <knome> sounds fun.
[23:39] <Unit193> Because ayatana is a fork that makes it distro-agnostic, and of course someone in Ubuntu doesn't like that. \o/
[23:39] <Eickmeyer> I was specifically informed that Canonical wants to drop the indicator stuff from Ubuntu entirely, but that means making sure all flavors are onboard with that.
[23:39] <bluesabre> :(
[23:40] <Unit193> Eickmeyer: What's your source?
[23:40] <bluesabre> If dropping means that the Ayatana stuff replaces it, I don't think there's a negative from the Xubuntu team perspective.
[23:40] <Eickmeyer> Unit193: I'd have to look back at my logs, but it was in either -release or -desktop.
[23:40] <Eickmeyer> Perhaps even -devel.
[23:40] <Unit193> Eickmeyer: Last I saw their response was "We're maintaining Ubuntu indicator stuff and don't want to work with some hostile upstream" :/
[23:41] <Eickmeyer> Unit193: My source was a couple weeks ago.
[23:41] <Unit193> bluesabre: Yeah, we're more than ready as we *could* just use the ayatana stuff, but we don't ship any of that anyway.
[23:41] <Unit193> Eickmeyer: This would be very good, we want to get rid of the Ubuntu versions.
[23:41] <Unit193> ...But this isn't exactly related to the topic at hand. :P
[23:42] <Eickmeyer> Either way, we've dropped indicator-* from our seed and updated our panel to match Xubuntu.
[23:42] <knome> it is, you're just doing the real collaboration instead of the meta talk :P
[23:42] <bluesabre> :D
[23:42] <Eickmeyer> In the meantime, we get a lot of people with issues related to using xfce4-volumed.
[23:42] <knome> but yes, let's try to wrap up the meeting
[23:42] <Eickmeyer> For instance, it doesn't survive a pulseaudio restart.
[23:43] <Unit193> xfce4-pulseaudio-plugin replaces xfce4-volumed/indicator-sound, sooo...
[23:43] <Eickmeyer> Exactly.
[23:43] <Eickmeyer> Unfortunately, we didn't know that until a month ago.
[23:43] <Unit193> (My version survives a PA restart.)
[23:43] <Unit193> knome: Yes, lets.
[23:43] <Eickmeyer> That drove this collaboration talk.
[23:44] <knome> bluesabre, wake up!
[23:44]  * Eickmeyer steps off of soapbox
[23:44] <bluesabre> Eickmeyer: so yeah, going forward we'll keep your team up-to-date on the latest Xubuntu updates (and hopefully you'll often follow suit so the base remains similar)
[23:44] <Eickmeyer> bluesabre: That's the plan. :)
[23:44] <bluesabre> Right-o!
[23:44] <bluesabre> I think that wraps everything up then.
[23:45] <bluesabre> Anybody else got anything else before we close it out?
[23:45] <bluesabre> #topic AOB
[23:45] <bluesabre> Because I'm out of things to say, I think :)
[23:45] <knome> i'm good. i think i'm next in the line for scheduling a meeting, but i'm not sure when i'll have the time... so if you don't hear from me in a sensible time, please skip me.
[23:46] <bluesabre> knome: will do
[23:46] <Eickmeyer> Doodle is a good place to collaborate on scheduling.
[23:46] <knome> i can do my chairing duties at another time
[23:46] <knome> we usually just ask the irc channel and then go for it
[23:46] <bluesabre> knome: sounds fair
[23:46] <bluesabre> In that case
[23:46] <bluesabre> #topic Schedule next meeting
[23:46] <knome> or just schedule and hope somebody pops up :D
[23:47] <bluesabre> #action knome to schedule next meeting, but skip him if he doesn't in a sensible amount of time
[23:47] <meetingology> ACTION: knome to schedule next meeting, but skip him if he doesn't in a sensible amount of time
[23:47] <bluesabre> :D
[23:47] <knome> thanks
[23:47] <bluesabre> #endmeeting
[23:47] <meetingology> Meeting ended Fri Jun 14 23:47:24 2019 UTC.
[23:47] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/xubuntu-devel/2019/xubuntu-devel.2019-06-14-22.00.moin.txt
[23:47] <Unit193> Wait, I thought we were supposed to schedule and hope nobody did....I've been doing this all wrong.
[23:47] <bluesabre> Thanks everybody!
[23:47] <Unit193> bluesabre: Thanks.
[23:47] <knome> and thanks bluesabre for chairing
[23:47] <bluesabre> That was a good discussion
[23:47] <Eickmeyer> Thanks! Looking forward to a bright future of collaboration!
[23:48] <knome> yep, and i didn't fall asleep before the meeting irrecoverably :D
[23:48] <bluesabre> 👍
[23:48] <knome> again some kind of poo poo on my screen
[23:48] <knome> :D
[23:48] <Eickmeyer> knome: I'm going to tell you what I have told tsimonq2: Go. To. Bed.
[23:48] <knome> nighty!
[23:48] <knome> yep.
[23:48] <bluesabre> Seeya!
[23:48] <knome> o/
[23:52] <bluesabre> Minutes are up, https://wiki.ubuntu.com/Xubuntu/Meetings


[13:01] <lool> heya
[13:01] <lool> stgraber, barry, ogra_, plars: heyo
[13:01] <plars> hi lool
[13:01] <barry> howdy
[13:02]  * stgraber waves
[13:02] <lool> so let's try to keep this short  :-)
[13:02] <lool> barry: want to start?  you have all the download manager action  :-)
[13:02] <barry> sure :)
[13:03] <barry> so, i've been working with mandel on the downloader dbus service.  all the major bugs there have been fixed and are in various stages of ci/landing-on-trunk/landing-in-archive.  my system-image integration branch is getting closer to full-test passing and with a couple more dl bugs fixed i expect we'll have that done this week
[13:04] <barry> (we have a couple of weird issues still with the d/l service, ongoing to debug and fix)
[13:04] <barry> hopefully schedule is:
[13:04] <barry> dl service lands by tomorrow.  new system-image by friday
[13:04] <lool> barry: I'm not sure I've done that, but I wanted to ask you to add autopkgtests to systme-image client so that download-helper updates cause it to run and can be blocked from testing migration if they would regress system-image
[13:04] <barry> that's the high order bit.  i can dig into details if you want
[13:05] <lool> barry: list of bugs we're blocked on for d/l service would be good
[13:05] <lool> barry: especially if you want to land the fixes
[13:05] <barry> lool: yeah, slangasek mentioned the same thing last night.  i will file a bug and get that once we have the basic stuff done
[13:05] <ogra_> whoops, i'm late
[13:05] <barry> lp: #1229413
[13:05] <lool> ok, this one isn't fixed in trunk yet
[13:05] <barry> (that has a branch i will review today)
[13:06] <barry> https://bugs.launchpad.net/ubuntu-download-manager
[13:06] <barry> lp: #1229463
[13:06] <lool> ok
[13:06] <barry> that one mostly affects the s-i test suite, so we're not going to block d/l update for that
[13:06] <barry> i think that's it
[13:07] <lool> barry: I've just invited mandel here, but could you make sure he requests landing with adequate priority to not block you for too long?
[13:07] <lool> currently we have an updated staged in the proposed image, and another one in PPA
[13:07] <lool> (trunnk)
[13:07] <lool> but we're still missing at list this bug
[13:07] <lool> barry: ok; thanks for the update
[13:07] <barry> np
[13:07] <lool> stgraber: so you've deployed all the server side pieces in the last couple of weeks for channel aliases, pooled diffs etc.?
[13:08] <lool> stgraber:( awesome!)
[13:08] <lool> stgraber: are there things you're looking after?
[13:08] <lool> there is this fs corruption bug I raised which affected Jamie as well
[13:08] <stgraber> yep, I landed the server changes a week ago, so far everything's just working, haven't had to touch anything since
[13:08] <lool> barry, stgraber: Did either of you receive Jamie's bug report?  I told him to attach details of the image he was upgrading from/to, how he upgraded etc.
[13:08] <stgraber> there are some tools improvement though I want to get done (make the copy script wait for the lock to be released and make a batch copy script)
[13:09] <stgraber> besides that my first priority for system-image stuff now is to look at boot time hooks
[13:09] <lool> ok
[13:09] <barry> lool: i haven't seen it
[13:09] <barry> (or if i did, it was below the radar)
[13:09] <lool> barry: did you turn logging to verbose in trunk?
[13:10] <lool> would be good to debug future issues
[13:10] <barry> lool: it's in my integration branch, so logging will be 'info' level with s-i 1.6
[13:10] <lool> ok
[13:10] <lool> didrocks: I invited you because you had the UI side
[13:10] <lool> didrocks: so that you know the updates are coming up :-)
[13:10] <lool> didrocks, barry: I just filed https://bugs.launchpad.net/ubuntu-system-settings/+bug/1229707 which has been bugging me for a while
[13:11] <lool> might be dbus client side, or system-settings not sure
[13:11] <didrocks> lool: I looked at the it (some other people reported it)
[13:11] <didrocks> lool: the method is sent
[13:11] <didrocks> so I think service-side
[13:11] <lool> didrocks: if you're touching this piece of code, it would be nice if you could start the spinner before the dbus autospawn kicks in as the spinner takes a little while to show up when one first enters the OS updates menu  :-)
[13:11] <barry> didrocks: i'm still planning on plumbing through progress from d/l thru s-i to ui, but you should keep an eye on the progress meter usability.  i'm seeing fairly coarse progress from d/l, but apparently we're stuck with what the qt network stack gives us
[13:12] <didrocks> lool: in fact, it's more a state machine, that can work, but mpt didn't design a spinner
[13:12] <barry> lool: tagged
[13:12] <didrocks> lool: he just wanted to see the progress(0)
[13:12] <lool> barry, stgraber: Oh and one more thing </Steve Jobs>
[13:12] <didrocks> what I'm waiting barry on :)
[13:12] <lool> barry, stgraber: we want to generate server-side changelogs in some way and show them in the UI
[13:12] <didrocks> barry: can't you send progress(0)?
[13:12] <didrocks> barry: I think that will make people happy at least to be able to cancel and so on
[13:13] <didrocks> (remember that bug?)
[13:13] <barry> didrocks: yes, there's a bug on that.  i'll get that done when i plumb thru the new progress signals.  still planning on s-i 1.6 for that
[13:13] <barry> and yeah, dbus activation is pretty laggy across the board :/
[13:13] <lool> stgraber: would you think we could use ogra's .manifest diffing stuff as a start to generate the changelogs?
[13:14] <stgraber> lool: right, that'll take some thinking about, not so much on the system-image side (it's just a text field) but on first landing what we need on the server side
[13:14] <lool> stgraber: I'm guessing we want to stuff them in the json
[13:14] <stgraber> lool: Ursinha wrote a tool to do that properly in cdimage but it's pending review from cjwatson and I
[13:14] <didrocks> barry: I fixed another bug FYI, (barry is assigned as well to that one), but I think that UpdateFailed() shouldn't be sent on CancelUpdate() which has nothing to cancel.
[13:14] <stgraber> lool: once we have that one landed in the tree, we can look into getting system-image to import those and use them
[13:14] <cjwatson> yeah, needed to fix some more things in changelogs.u.c first unfortunately and I got stalled on that
[13:14] <lool> stgraber: Ok; I think this is a 13.10 thing; if it ends up being delayed too much, we should secure some time to remove the dummy messages
[13:14] <lool> stgraber: ah right remember the Ursinha mp now
[13:15] <barry> lool, didrocks there's still the u/i bug that it can't handle the array-of-dicts that i18n descriptions passes back.  not sure what the status is on that, but i just need to uncomment a bunch of code to re-enable that
[13:15] <ogra_> lool, we have a cdimage branch that nobody reviews
[13:15] <ogra_> lool, for doing proper changelog generation during build
[13:15] <didrocks> barry: yeah, it's still blocked, I'm distracted with other things unfortunately
[13:15] <cjwatson> ogra_: Like I say, it's blocked on some server-side fixes on changelogs
[13:15] <barry> didrocks: k, no worries
[13:15] <cjwatson> ogra_: I do still consider it on my plate ...
[13:15] <ogra_> cjwatson, ah, i didnt know it had reached your plate at all yet
[13:16] <cjwatson> ogra_: I worked with Ursinha and stgraber on it at the saucy releng sprint in July
[13:16] <cjwatson> (but there's this totally unimportant package called click that people keep wanting me to work on)
[13:16] <ogra_> we wanted to take a look at it during the sprint, but somehow that didnt happen
[13:16] <lool> barry: i18n will be incomplete in this relesae I'm afraid; can't translate changelogs either; we'll have to think of something better in next iteration
[13:16] <lool> but can't design new features at this point
[13:16]  * barry nods
[13:16] <lool> 3 weeks left til release!
[13:16]  * barry freaks out
[13:16] <ogra_> cjwatson, awesome, i'll leave that to you then, though tell me if it landed so i can stop the cron scripts on my desktop :)
[13:17] <lool> Ok
[13:17] <lool> plars: on to you
[13:17] <lool> plars: couple of topics: QA against R/O images and testing of upgrades
[13:17] <lool> plars: do you have updates on these?
[13:17] <plars> lool: on the ro testing side, we're making some additional progress toward that this week
[13:18] <plars> sergio figured out how to get some additional things in as click packages
[13:18] <plars> namely notes for now
[13:18] <plars> but it could grow to other apps too
[13:18] <plars> but for the time being, we're going to take some of the existing apps that are in as click, and get the tests working on them
[13:18] <lool> yeah; sadly he's been a bit blocked on clickification due to other reasons
[13:18] <lool> but cool
[13:18] <plars> things like dropping letters, stockticker, etc
[13:18] <plars> yeah, I know
[13:18] <plars> but as a proof of concept that evertything works as it should
[13:18] <plars> then as the other apps get clickified, we can transition their testing properly
[13:19] <cjwatson> that's a good approach, proves the concept without disturbing the image
[13:19] <lool> plars: I saw that there was a meeting on click testing in images and click infrstructure
[13:19] <plars> lool: that's exactly what it's about
[13:19] <plars> lool: we're having regular status meetings about it
[13:19] <lool> https://docs.google.com/a/canonical.com/document/d/1Ou5HTXaeqiGyDvPlvwJb02vazmNBhQy0S7sw12sJ084/edit?usp=drive_web
[13:19] <lool> click testing task force  :-)
[13:19] <plars> unfortunately this week is fairly well tied up with saucy beta for me, on top of all the image stuff
[13:19] <lool> plars: awesome
[13:20] <lool> plars: what about upgrade testing?
[13:20] <plars> but doanac is doing a lot of the work on the ci side for this
[13:20] <lool> plars: it's critical we have this in place to support production post 13.10
[13:20] <barry> click and clack, the tappet brothers: http://en.wikipedia.org/wiki/Car_talk
[13:20] <plars> for upgrade, we noticed that system-image-cli -i gives us a lot better info about what we've been upgraded to now
[13:20] <lool> was it Javier on this?
[13:20] <plars> lool: javier is qa, I have no idea what he's on
[13:20] <barry> plars: yay!
[13:21] <lool> hmm right, I guess I should have updated guests after the team split
[13:21] <plars> there's the beginnings of a upgrade test in our branch, but it doesn't do much past upgrade
[13:21] <lool> plars: who's on the hook for completing the upgrade test?
[13:21] <lool> plars: basically we want to make sure that folks running latest public stable will be able to upgrade to next one
[13:21] <plars> if I manage to get some spare time this week, we might see about fixing it to use -i, and really check the upgrade worked, but it's not running and would have to be set up as a completely separate job
[13:21] <plars> since it has to do a (-#) install firswt
[13:21] <lool> yes, it's a separate job
[13:21] <plars> lool: no idea, you'd have to talk to jfunk about that
[13:22] <lool> we even have a dedicated channel almost only for this job  :-)   well not anymore
[13:22] <plars> lool: they maintain the tests still
[13:22] <lool> plars: so you're getting the test from jfunk?
[13:22] <plars> lool: a dedicated channel?
[13:22] <plars> lool: jfunk is manager of the qa team
[13:22] <lool> plars: originally the proposed channel was just for upgrade testing
[13:23] <lool> plars: Ok; will grab jfunk on this, can I direct him at you for the CI infrastructure side?
[13:23] <lool> or is that not adequate?
[13:23] <plars> lool: really? I thought that was so that we could ci the image before marking it current
[13:23] <plars> but ok
[13:23] <plars> yep
[13:23] <plars> me or andy
[13:23] <lool> ok
[13:23] <lool> I think I'm out of topics
[13:23] <lool> did others have topics to bring up?
[13:24] <lool> do we want a meeting only in 2 weeks, or next week?
[13:24] <stgraber> nothing here
[13:24] <barry> lool: given 3 weeks left, maybe weekly until release?
[13:24] <lool> barry: +1
[13:24] <lool> ok, will adjust invite
[13:25] <lool> Thanks a lot folks for a quick and productive meeting!  I wish a good rocking end of week to all of you  :-)
[13:25]  * lool waves
[13:25] <barry> cheers
[15:59] <hallyn> \o
[15:59] <roaksoax> o/
[16:00] <roaksoax> let's wait a few more minutes
[16:03] <roaksoax> couple more minutes and we get started
[16:03] <arosales> roaksoax, ack and thanks
[16:04] <smoser> o/
[16:04] <roaksoax> alright, let's get the party started!
[16:04] <roaksoax> #startmeeting ubuntu-server-team
[16:04] <meetingology> Meeting started Tue Sep 24 16:04:39 2013 UTC.  The chair is roaksoax. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:04] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:04] <roaksoax> #topic Review ACTION points from previous meeting
[16:04] <roaksoax> smoser look at / assign bug 1206872 and bug 1156932
[16:04] <roaksoax> any updates?
[16:05] <smoser> no updates. :-(
[16:05] <smoser> please re-action
[16:05] <roaksoax> ack!
[16:05] <roaksoax> ACTION: smoser look at / assign bug 1206872 and bug 1156932
[16:06] <roaksoax> [ACTION] smoser look at / assign bug 1206872 and bug 1156932
[16:06] <meetingology> ACTION: smoser look at / assign bug 1206872 and bug 1156932
[16:06] <roaksoax> #topic Saucy Development
[16:06] <roaksoax> #link https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[16:06] <roaksoax> so there's our release schedule
[16:07] <roaksoax> #subtopic Release Bugs
[16:07] <roaksoax> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server
[16:07] <roaksoax> bug #1208455
[16:07] <roaksoax> smoser: any updates?
[16:07] <roaksoax> err
[16:07] <roaksoax> smb:
[16:07] <hallyn> (smb is not in today, and he didn't mention his one)
[16:08] <roaksoax> ah seems that smb is not here today
[16:08] <hallyn> (not in right now that is)
[16:08] <roaksoax> alright moving on
[16:08] <roaksoax> bug #1213915
[16:08] <roaksoax> i guess we wll see progress as soon as an archive admin can make it happen
[16:09] <roaksoax> bug #1206872
[16:09] <roaksoax> anyone from the server team willing to take on that one
[16:09] <roaksoax> zul: ? maybe you since you've previously touched samba
[16:09] <roaksoax> (or used to)
[16:09] <zul> i can look i guess
[16:10] <roaksoax> thank you
[16:10] <roaksoax> bug #1156932
[16:10] <zul> no progress
[16:10] <roaksoax> ack! thanks
[16:10] <roaksoax> bug #1199791
[16:10] <roaksoax> zul: what about this oen?
[16:10] <zul> no progress
[16:11] <roaksoax> bug #1210054
[16:11] <roaksoax> jamespage: any updates?
[16:11] <jamespage> not yet
[16:11] <roaksoax> or maybe arosales knows of someone who should take care of this one instead
[16:11] <roaksoax> alrighty
[16:11] <roaksoax> bug #1223010
[16:11] <roaksoax> zul: ?>
[16:11] <arosales> roaksoax, I can investigate bug 1210054 for an owner
[16:11] <zul> looked at it i dont think thats going to make it in for saucy
[16:12] <roaksoax> arosales: awesom,e thank you
[16:12] <roaksoax> zul: uhmm is it too big of a change?
[16:12] <zul> roaksoax:  yeah
[16:12] <arosales> hallyn, if you have an opportunity could you also throw in a comment in bug 1210054 ?
[16:13] <hallyn> uh, sure
[16:13] <arosales> hallyn, thanks
[16:13] <roaksoax> zul: ok boomer
[16:14] <roaksoax> bug 1226871
[16:14] <roaksoax> adam_g: any updates?
[16:14] <adam_g> roaksoax, in progress. have a branch up for review to lp:~ubuntu-server-dev/python-troveclient/havana
[16:15] <roaksoax> perfect! thank you!
[16:15] <adam_g> https://code.launchpad.net/~gandelman-a/ubuntu/saucy/python-troveclient/1226871/+merge/187113
[16:15] <roaksoax> volunteers to review are welcome :)
[16:15] <roaksoax> bug 1227153
[16:15] <roaksoax> this one should be an easy one
[16:15] <roaksoax> zul: ^^
[16:15] <roaksoax> same as bug #1227167
[16:16] <roaksoax> bug #1227353
[16:16] <zul> roaksoax:  fixed, fixed
[16:16] <roaksoax> waiting for archive admin
[16:16] <roaksoax> zul: thanks! please update appropriately
[16:16] <roaksoax> #subtopic Blueprints
[16:16] <roaksoax> #link http://status.ubuntu.com/ubuntu-s/group/topic-s-servercloud-overview.html
[16:17] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmhelper2
[16:17] <roaksoax> arosales: any updates you would like to share?
[16:18] <arosales> roaksoax, hm . .  .
[16:18] <roaksoax> since marco doens't seem to be around
[16:18] <arosales> roaksoax, I think mathew wedgwood has been working on an api for charm helpers
[16:19] <arosales> roaksoax, but for charm-tools marcoceppi is working on a 1.0 release and juju/stable currently has that and he is working on getting that into saucy, if possible
[16:19] <roaksoax> awesome! thanks for the update
[16:19] <arosales> roaksoax, that should cover charm tools and helper updates
[16:19] <roaksoax> perfect!
[16:19] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-2-delivery
[16:20] <roaksoax> jamespage: any updates?
[16:20] <arosales> roaksoax, I'll follow up on [marcoceppi] Update charm tools to promote best practices wrt stubbing/libraries WITH TESTS: TODO with marco on the charmhelper2 bp
[16:20] <jamespage> roaksoax, all going OK - FFe for 1.16 applied for
[16:20] <roaksoax> arosales: thank you!
[16:20] <roaksoax> jamespage: awesome!
[16:20] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms-ha-v2
[16:21] <roaksoax> no new progress
[16:21] <roaksoax> james is taking care of percona charm
[16:21] <roaksoax> i still have to work on the haproxy stuff (but past 3 weeks in training so couldn't move forward)
[16:21] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-ceph
[16:21] <roaksoax> jamespage: ^^
[16:21] <jamespage> roaksoax, all good - apart from the radosgw agents for geo-replication
[16:22] <jamespage> I've not had time to look in detail but they look a bit early days for 13.10 inclusion
[16:23] <roaksoax> i guess we just have to keep an eye on it
[16:23] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-simplestreams
[16:23] <roaksoax> smoser: updates?
[16:23] <smoser> i'll update now.
[16:23] <roaksoax> smoser: thank you!
[16:24] <roaksoax> but there seems to be good progress and things looking great
[16:24] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-qa
[16:24] <roaksoax> zul: ^^ any updates?
[16:24] <zul> ill update it
[16:24] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-havana
[16:24] <roaksoax> same as ^^ if there's updates please
[16:25] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-mongodb
[16:25] <zul> ditto
[16:25] <roaksoax> jamespage: so we still blocked with mongodb?
[16:25] <jamespage> roaksoax, yeah - it won't make main this cycle
[16:25] <roaksoax> alrighty
[16:25] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-charms
[16:25] <roaksoax> adam_g: any updates?
[16:26] <roaksoax> in me meantime:
[16:26] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-virtstack
[16:26] <roaksoax> hallyn: any updateS?
[16:27] <hallyn> not really, all going well
[16:27] <roaksoax> perfect!
[16:27] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-archive
[16:27] <roaksoax> jamespage: how's the CA looking?
[16:28] <jamespage> roaksoax, OK
[16:28] <jamespage> I've been testing today with whats in staging
[16:28] <roaksoax> the cloud-tools pocket is WIP, and things are lookging good too
[16:28] <roaksoax> awesome!
[16:28] <jamespage> mainly hitting charm compat issues due to name changes quantum-> neutron
[16:28] <jamespage> but niggles
[16:29] <roaksoax> alriught, so that's easy to fix i guess then
[16:29] <roaksoax> https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-openstack-hypervisor
[16:29] <roaksoax> finalle
[16:29] <roaksoax> zul: ^^
[16:29] <zul> needs updating
[16:29] <roaksoax> tjamls!
[16:29] <roaksoax> thanks
[16:30] <roaksoax> #topic Weekly Updates & Questions for the QA Team (psivaa)
[16:30] <roaksoax> psivaa: any updates for us?
[16:30] <psivaa> no update from us
[16:30] <psivaa> hallyn fixed the lxc bug already :)
[16:30] <roaksoax> awesome!
[16:30] <roaksoax> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:30]  * hallyn raises his hand
[16:30] <roaksoax> smb is not around
[16:30] <hallyn> smb says,
[16:30] <hallyn> he's working on the raring xen mre,
[16:31] <hallyn> and he is looking at bug 1185756 but needs to set up an environment to reproduce in
[16:31] <hallyn> (that's all)
[16:31] <roaksoax> awesome thank you!
[16:31] <roaksoax> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:31] <roaksoax> rbasak in holidays.. anyone might have something?
[16:32] <roaksoax> i guess not
[16:32] <roaksoax> #topic Ubuntu Server Team Events
[16:33] <roaksoax> any event's coming up other than ODS in november?
[16:33] <zul> openstack in action in montreal on the oct 8
[16:33] <roaksoax> zul: yaay you representing us then?
[16:33] <zul> roaksoax:  im not giving any presenation but ill be there
[16:34] <roaksoax> cool
[16:34] <arosales> roaksoax, we had jcastro and maroceppi at  Ohio Texas Linux Fest and LinuxCon, respectively these past weekends
[16:34] <arosales> roaksoax, charm school this Friday
[16:34] <arosales> Charm School: How to submit your bundle for the charm championship :-)
[16:34] <arosales> more details @ https://juju.ubuntu.com/events/
[16:34] <roaksoax> that's great!
[16:35] <roaksoax> hurray for jcastro and marcoceppi
[16:35] <roaksoax> so let;'s mover on
[16:35] <roaksoax> move on*
[16:35] <roaksoax> #topic Open Discussion
[16:35] <roaksoax> anyone hjas anything to add?
[16:35] <arosales> roaksoax, I also updated the agenda before the meeting to have a new item.
[16:35] <arosales> roaksoax, if you referesh https://wiki.ubuntu.com/ServerTeam/Meeting
[16:35] <arosales> do you see "Server & Cloud Bugs (caribou)"
[16:36] <roaksoax> arosales: now i SEE
[16:36] <roaksoax> see*
[16:36] <roaksoax> #topic Server & Cloud Bugs (caribou)
[16:36] <arosales> I need to add that to the copy/paste commands now that I think of it
[16:36] <roaksoax> caribou: any updates?
[16:36]  * arosales updates copy/paste now . . .
[16:36] <roaksoax> arosales: :)
[16:36] <caribou> well, this is mostly an introduction for this week
[16:37] <caribou> just some specific cloud & server bugs which would need some attention from CTS engineering team
[16:37] <caribou> but I don't have anything specific for this week, thanks
[16:37] <roaksoax> caribou: please go for it if you have any
[16:37] <roaksoax> ok
[16:37] <roaksoax> perfect then!
[16:37] <roaksoax> #topic Announce next meeting date and time
[16:37] <roaksoax> same day time
[16:37] <arosales> thanks caribou
[16:37] <roaksoax> thanks all for coming
[16:38] <arosales> roaksoax, thanks for chairing
[16:38] <roaksoax> #endmeeting
[16:38] <meetingology> Meeting ended Tue Sep 24 16:38:18 2013 UTC.
[16:38] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-24-16.04.moin.txt
[16:38] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-24-16.04.html
[16:38] <roaksoax> arosales: my pleasure
[16:38] <caribou> arosales: :-)
[16:39] <arosales> Server IRC commands updated
[16:39] <roaksoax> arosales: thank you!
[16:40] <arosales> roaksoax, np.
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ##
[17:00] <meetingology> Meeting started Tue Sep 24 17:00:17 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy
[17:00] <ogasawara> o/
[17:00] <cking> \o
[17:00] <ppisati> \o/
[17:00] <arges> o/
[17:00] <sconklin_> o/
[17:01] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> The flash-kernel dtb concatenation patch finally landed in the archive, while
[17:01] <ppisati> support for TI AM35XX and bug fixing for the rest of the socs
[17:01] <ppisati> (omap3/4, imx, etc) continues.
[17:01] <ppisati> ..
[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:02] <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html
[17:02] <ogasawara> || apw       || foundations-1305-arm64-bringup     || 2 work items ||
[17:02] <ogasawara> || cking     || foundations-1308-power-measurement || 1 work item  ||
[17:02] <ogasawara> || smb       || servercloud-s-virtstack            || 1 work item  ||
[17:02] <ogasawara> ||           || servercloud-s-openstack-hypervisor || 1 work item  ||
[17:02] <ogasawara> ..
[17:02] <jsalisbury> [TOPIC] Status: Saucy Development Kernel (ogasawara)
[17:02] <ogasawara> We've remained rebased on a v3.11.1 kernel for Saucy and the archive is
[17:02] <ogasawara> currently frozen for Final Beta this Thurs Sept 26.  Any uploads will
[17:02] <ogasawara> need to be cleared with the Ubuntu Release Team.  Additionally, Ubuntu Kernel Freeze is ~1 week away, Thurs Oct 03.  Any patches submitted
[17:02] <ogasawara> after Kernel Freeze will be subject to our SRU policy.
[17:02] <ogasawara> -----
[17:02] <ogasawara> Important upcoming dates:
[17:02] <ogasawara> [LINK] https://wiki.ubuntu.com/SaucySalamander/ReleaseSchedule
[17:02] <ogasawara> Thurs Sep 26 - Final Beta (~2 days away)
[17:02] <ogasawara> Thurs Oct 03 - Kernel Freeze (~1 week away)
[17:02] <ogasawara> Thurs Oct 10 - Final Freeze (~2 weeks away)
[17:02] <ogasawara> Thurs Oct 17 - 13.10 Release (~3 weeks away)
[17:02] <ogasawara> ..
[17:03] <jsalisbury> [TOPIC] Status: CVE's
[17:03] <jsalisbury> == 2013-09-24 ==
[17:03] <jsalisbury> The current CVE status can be reviewed at the following link:
[17:03] <jsalisbury> http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:03] <jsalisbury> ..
[17:03] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid (bjf/henrix/sconklin)
[17:03] <bjf> Status for the main kernels, until today (Sept. 24):
[17:03] <bjf>   *   Lucid - Verification & Testing
[17:03] <bjf>   * Precise - Verification & Testing
[17:03] <bjf>   * Quantal - Verification & Testing
[17:03] <bjf>   * Raring  - Verification & Testing
[17:03] <bjf> Current opened tracking bugs details:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:03] <bjf> For SRUs, SRU report is a good source of information:
[17:03] <bjf>   * http://people.canonical.com/~kernel/reports/sru-report.html
[17:03] <bjf> ..
[17:03] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:04] <jsalisbury> Thanks everyone
[17:04] <jsalisbury> #endmeeting
[17:04] <meetingology> Meeting ended Tue Sep 24 17:04:28 2013 UTC.
[17:04] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-24-17.00.moin.txt
[17:04] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-09-24-17.00.html
[19:24] <kkg2005> hello there
[19:25] <kkg2005> please help me where i can found help about ubuntu,
[19:25] <kkg2005> ,
[19:25] <kkg2005> ?
[19:25] <mapreri> !support | kkg2005
[19:25] <kkg2005> senku


[00:17] <mgw> Is there a way for a kvm instance to access its uuid or id?
[00:19] <thinknow> how to setup shell acounts(are putting together an botnet) on my ubuntu 12.10 server ? (-just installed it, regular installation with lvm encryption though)
[00:34] <adam_g> zul, no, thats just the src package
[00:34] <zul> adam_g:  k
[01:01] <twb> debsecan "works" on Ubuntu, but it gives false positives for fixes in the M of -NubuntuM.
[01:01] <twb> Is there something like debsecan, that talks to launchpad?
[01:02] <twb> Plan B is to get my PFY to check, \forall CVEs debsecan reports, does /usr/share/doc/foo mention it (and if so, take no action).
[01:45] <gartral> hey all, I hosed grub on my server and need to recover, I've managed to boot the system, but I need a perma-fix
[01:51] <twb> http://cyber.com.au/~twb/snarf/extlinux.txt
[02:13] <codepython777> Is there a faster way than this : ping -n 1 -w 100 IP4v  : For knowing if my server is up?
[02:17] <twb> ITYM -c1
[02:18] <twb> But not really.  You might want nagios or nmap or something.
[02:24] <codepython777> twb: -c is not there on my ping for some reason
[02:24] <codepython777> also, ping seems to be unreliable for detecting a machine is up or not...sometimes -c 1 does not work?
[02:24] <twb> Shrug.
[02:30] <Patrickdk> define, faster
[02:30] <Patrickdk> cause what your specified I would not consider fast at all
[02:30] <Pici> I vaugely remember there being a netcat argument that could quickly tell if a target was up or not.
[02:30] <Patrickdk> and if your ping doesn't have -c, your not using ubuntu
[02:31] <twb> Pici: well if you're testing e.g. for ssh, you can nc example.net ssh, with a timeout
[02:50] <roasted_> hello friends
[02:50] <roasted> is there a way to cron rsync to run every 5 minutes without having 6,000 entries in crontab?
[02:54] <Patrickdk> yep
[02:54] <Patrickdk> you did read the cron manual right?
[02:55] <Patrickdk> second thing, you won't want to put rsync in cron anyways, cause then you could startup two copies of rsync, and well, rsync doesn't like that
[02:55] <mardraum> man 5 crontab is all you need
[02:55] <roasted> a few times. evidently I missed something.
[02:55] <Patrickdk> */5 * * * *
[02:55] <roasted> Patrickdk: have you ever used lsyncd? I might look into that instead.
[02:55] <Patrickdk> personally, I use bash
[02:56] <roasted> bash, as an alternative to lsyncd?
[02:56] <Patrickdk> to wrap rsync
[02:56] <roasted> ah
[02:56] <Patrickdk> or perl
[02:56] <roasted> I understand lsyncd watches for file system changes and rsyncs the data accordingly.
[02:56] <roasted> I thought that would be kind of neato, but I'm not sure what kind of cons that setup would come with.
[03:00] <Patrickdk> why would it use cron?
[03:01] <roasted> lsyncd wouldn't use cron
[03:02] <roasted> I was looking into a continual rsync and came across lsyncd just a minute ago
[03:19] <twb> Patrickdk: you could wrap rsync with lockfile-progs, though running it every five minutes is a bit excessive
[03:28] <Patrickdk> excessive?
[03:28] <Patrickdk> I used to run it every 20seconds :)
[03:29] <Patrickdk> over a 8gig maildir
[03:29] <twb> I guess you had enough RAM to cache all the dirents
[03:29] <Patrickdk> yep
[03:29] <Patrickdk> that first rsync would take a good 3min or so
[03:30] <twb> But at that point I would instead just use a while :; do rsync ...; done loop or something, rather than cron jobs
[03:30] <twb> Or for maildir specifically, something maildiry like offlineimap
[03:30] <Patrickdk> well, this was just a loop like that yes, with a 20sec sleep
[03:30] <twb> Righto
[03:30] <Patrickdk> well, offlineimap wouldn't work
[03:30] <Patrickdk> it wasn't clean enough
[03:30] <twb> k
[03:30] <Patrickdk> this was my first attempt, and it worked well for several years
[03:31] <Patrickdk> multi-master mailservers in multible datacenters
[03:31] <twb> What do you do now, drbd?
[03:31] <twb> Or some magic in dovecot
[03:32] <Patrickdk> well, I would use dsync if I cared
[03:32] <Patrickdk> but the internet has been much better than it was back then
[03:32] <Patrickdk> back them, I would constantly randomly loose routing paths to one or another dc
[03:32] <Patrickdk> local isp's fault
[03:32] <twb> swap in a new ISP
[03:33] <twb> ...with prejudice
[03:33] <Patrickdk> wasn't an option
[03:33] <Patrickdk> when you can only pick from 2
[03:33] <Patrickdk> and the other was 30x the price, much more than they where willing to pay
[03:33] <twb> We still had a quarter of our /24 reserved for staff dial-in pstn modems, until like 2008
[03:33] <Patrickdk> servers in two other dc's where not even 1/3 that price
[03:34] <twb> maybe 2010 even... whenever I took over
[03:34] <twb> That is, staff connecting directly to us because ISPs didn't exist yet
[03:39] <roasted> lsyncd is proving to be a headache.
[03:39] <roasted> I somehow made it work from laptop to server, but the goal is to go from server 1 to server 2. It keeps failing saying the host verification key failed, yet regular rsync works without keys since SSH keys are set up.
[04:10] <twb> roasted: running it as different users?
[04:10] <roasted> tried my regular user and root
[04:10] <twb> host verification failure is usually a result of known_hosts having different data in it, or running in -oBatchMode=yes and not having the existing entry
[04:10] <roasted> if I run rsync manually it works fine
[04:10] <roasted> if I let lsyncd do it, it tanks
[04:11] <twb> I dunno about lsyncd, sorry.
[04:11] <roasted> I'm looking at the log file pulling my ahir out because it looks perfect
[04:11] <twb> But maybe lsyncd can't access your ssh agent?
[04:11] <roasted> I suppose. I'm not sure.
[04:12] <twb> Is it using passphraseless SSH keys for auth?
[04:12] <twb> Also run it with LC_ALL=C and tell me the exact error message
[04:16] <roasted> I have ssh keys set up. I have no idea if it's seeing it properly.
[04:16] <roasted> for now I just set up rsync to run.
[04:16] <twb> Are the passphraseless?
[04:16] <roasted> probably not a good idea for me to troubleshoot half lit up and tired as can be. :P
[04:16] <roasted> well, when I ssh to the server I get no PW prompt, so yea.
[04:26] <codepython777> curl -k -X HEAD -i https://website -- hangs after printing the head- any ideas why?
[04:28] <twb> WFM.
[04:33] <codepython777> how do i measure the total number of bytes sent/received by a particular command?
[08:00] <jamespage> smb: looking at iscsitarget right now
[08:12] <jamespage> Daviey, everything is built in havana-proposed now
[08:12] <jamespage> shall I promote to updates?
[08:26] <sanderj_> What do I do when fsck /dev/sdb1 returns only the version number. and when I go into the dir I get: ls: reading directory .: Input/output error
[08:28] <apw> sanderj_, i would look in dmesg and see if the drive is even present, also fsck on a mounted filesystem is a no-no unless it is r/o and even then not recommended
[08:29] <sanderj_> apw, scsi0: ERROR on channel 0, id 1, lun 0, CDB: Read (10) 00 12 c1 ad 4f 00 00 08 00, Info fld=0x12c1cd8f, Current sdb: sense key Medium Error
[08:29] <apw> medium error, this means physical issues
[08:30] <sanderj_> apw, ok, thanks.
[08:56] <jamespage> adam_g, what do you think about a feature for the nova-compute charm that allows you to suckup disks and mount them on /var/lib/nova/instances
[08:57] <jamespage> right now they always sit on the OS disk by default
[08:57] <jamespage> this would allow extra disks in servers to provide ephemeral storage
[08:57] <jamespage> smb, just uploaded a new version of iscsitarget - should be OK now
[08:58] <jamespage> when the patches landed upstream the whitespace/tabbing in the compat patches got fixed up
[08:58] <smb> jamespage, Ok, I will get it downloaded as soon as it shows up and make the machine that failed verify it
[09:00] <jamespage> smb, I tested it on a 3.5 12.04 machine and it looks OK
[09:01] <smb> jamespage, ok, well the machine that exploded was a saucy one but just happened to get upgraded from 3.9 to 3.10 kernel at the same upgrade run
[09:01] <smb> (not that I can repeat that exactly)
[10:06] <phretor> hi, does this kernel build http://packages.ubuntu.com/precise/linux-image-server has the CONFIG_ROOT_NFS=y?
[10:27] <zatricky> Hi, all. I updated my personal server at home last night from 12.10 to 13.04 - the upgrade went smoothly except that the new kernel (3.8) doesn't finish booting. There are no clues given except for an error saying "Timed out", and "Dropping to a shell".
[10:28] <zatricky> The server runs off a 60GB Intel SSD with btrfs - which works without any issue with the previous kernel (3.5)
[10:29] <zatricky> I've done a lot of googling but I'm not seeing much info relevant either to btrfs or simply "Timed out" in relation to the a boot process failure :-/
[11:39] <foo357> Hello. I've had some trouble with cron-anacron recently, I'm fairly new to it.
[11:40] <foo357> However I think I've found the answer: http://askubuntu.com/questions/92322/time-of-execution-of-daily-anacron-job
[11:42] <foo357> the solution is to make cron start anacron every hour. But the suggested edits to the crontab file seems a bit flawed.
[11:43] <foo357> 01 0    * * *   root start -q anacron || :
[11:43] <foo357> @hourly root start -q anacron || :
[11:43] <foo357> If I'm reading this correctly these two lines are equivalent and just uses a bit different syntax.
[11:44] <foo357> so only one of them would be needed really.
[11:44] <foo357> can anyone confirm if I'm right or wrong?
[11:45] <zatricky> foo357 - correct, seems a bit strange to have two entries that do the same thing at the same time
[11:51] <foo357> thanks for the response zatricky.
[13:28] <Teduardo> okay i've figured out that if i interrupt the boot process by holding shift and then select ubuntu advanced and then tell it to boot normally the console works
[13:40] <sebrock> I'm having trouble gettin L2TP tunnel to work with xl2tpd. It just sits there. No error messages, nothing. Can someone please help me?
[15:24] <hallyn_> stgraber: I'm going to have to have lxc-start check whether it is already in a subdir of /sys/fs/cgroup/$d/lxc/$container and do nothing if so
[15:25] <hallyn_> stgraber: it gets a bit hacky, but with new kernel restrictions it seems the only way to keep the mountcgroups hook usable
[15:25] <hallyn_> just fyi
[15:28] <stgraber> hallyn_: ok, does that mean that a nested container will essentially end up in the same cgroup as its parent (instead of its own sub-entry)?
[15:29] <hallyn_> no
[15:29] <hallyn_> it may be that doubly nested containers won't work any more - i haven't thought thruogh whether that's fixable yet
[15:40] <resno> i have 2 vms behind a pfsense firewall, both configured the same. one can ping an ip the other cant... any suggestions?
[15:40] <resno> both ubuntu 10.04
[15:41] <sindri> Ok, I'm still having problem running vsftpd on my server; getting "530 Non-anonymous sessions must use encryption." My config looks like this: http://paste.ubuntu.com/5846998/ and my user config like this: http://paste.ubuntu.com/5847003/ any help would be welcome. Thanks!
[17:08] <Free99> hey everyone. Trying to figure out how to use the "remember" option in PAM for the pam_unix.so module
[17:08] <Free99> there apparently used to be a package called "pam_pwhistory" but it doesn't exist any longer for 12.04
[17:15] <Free99> (shrug) ok then
[17:18] <Vec_> Hi. <- learning newbie. Just about to install LAMP-stack on my server. Should i also install a webbased adminpanel like cPanel or ISPConfig3, or simply take my time and config it through a ssh? - what are you guys' reccomendations?
[17:19] <Vec_> Basically at first i just want my box to serve webpages securly, then my goal is to host various java applets im programming for school.
[17:19] <jpds> Vec_: You're going to learn a lot more via SSH.
[17:19] <Pici> Vec_: The only web-based front end that I personally find useful is phpmyadmin (or phppgadmin), anything else is probably overkill.
[17:19] <sarnold> Vec_: strongly recommend against web-based configuration panels. (a) they are very often used by hackers to gain access to systems, since their code quality is usually very poor (b) they get in the way of doing the configuration yourself -- it's like wearing boxing gloves with everything you do. I dislike them. Intensely. :)
[17:19] <Vec_> hehe
[17:20] <jpds> sarnold: Including boxing?
[17:20] <Vec_> Ok, well im settled then. SSH it is.
[17:20] <Pici> Also, I usually leave them disabled unless I'm actively working with them.
[17:20] <Vec_> jpds: lol
[17:20] <sarnold> jpds: lol :)
[17:21] <Vec_> Tbh i've gotten really far in 1 week. From 0% knowledge of linux to now having a server sharing files, running automated backup, sharing a printer -- all configured as restrictive as my brain find logical and whatnot HOWTOs and ubuntu docs tell me
[17:21] <Vec_> Its really really fun ^^
[17:21] <maxb> The other *massively* useful thing about doing configuration in textual configuration files is that you can put them under version control, and have an audit trail, notes about why you changed things, and a way to roll back when things go wrong
[17:22] <sarnold> Vec_: cool :) I'm glad it's fun :)
[17:22] <Vec_> maxb: That sounds like something i should google.. not sure if i can handle the added complexity of learning version control (however that works) together with configing the LAMP stuff
[17:22] <jpds> Vec_: sudo apt-get install etckeeper
[17:23] <jpds> Vec_: https://help.ubuntu.com/12.04/serverguide/etckeeper.html
[17:24] <enraged> maxb: I just joined in the middle of this conversation, but if I launch a GUI program that makes modifications to a config file, doesn't the user who launched the GUI program be recorded as the person who edited the text file, just as if they'd done it with a standard text editor?
[17:24] <Vec_> jpds: "By default, etckeeper will commit uncommitted changes made to /etc daily" what exactly does this mean?
[17:24] <maxb> The context of the conversation involved ssh vs. web admin tools
[17:25] <enraged> Ah ok
[17:25] <enraged> I apologize
[17:25] <maxb> np
[17:25] <jpds> Vec_: It'll do a daily commit of changes on its own.
[17:25] <enraged> If we're discussing SSH atm in here, is there anyone using Ubuntu 10.04 that has managed to get multi factor authentication working with OpenSSH?
[17:25] <Vec_> Please define commit. Also, if i make changes to a config file in /etc then i save it staight away (pretty sure im missing the target at this point? :p)
[17:26] <enraged> I'm specifically involving ssh keys here
[17:26] <enraged> An important detail missed out.
[17:26] <jpds> enraged: I always use SSH keys, everywhere.
[17:26] <jpds> Vec_: Commited into the version control.
[17:26] <Vec_> jpds: As in logged? (will continiue to read now..)
[17:26] <thinknow> easiest app to make an shell account on my server?
[17:26] <jpds> Vec_: If you just save the file, the change isn't yet in the version control system until you commit it into it.
[17:26] <enraged> jpds: Do you use mfa aswell?
[17:26] <jpds> enraged: No.
[17:27] <enraged> jpds: Aw damn.
[17:27] <sarnold> thinknow: adduser(8)
[17:27] <Vec_> jpds: Ah ok, so if i change stuff, notice i fubar'd it, then i can roll it back before its committed?
[17:27] <jpds> Vec_: Yes, and even after it's commited.
[17:27] <Vec_> well that sounds very nice
[17:27] <thinknow> sarnold, but i mean shell account so i can add process like irc
[17:28] <thinknow> dont remember the name
[17:28] <enraged> jpds: I've been trying to get totp codes to be required as a secondary authentication method to an ssh key, but as far as I can tell PAM is required to do that and when you use an SSH key it bypasses PAM
[17:28] <jpds> enraged: If they steal your private SSH key, you have other issues.
[17:29] <enraged> jpds: Yeah, my concern is the laptop I use to remotely admin being hacked, the private key file being stolen and the laptop being keylogged so they know the passphrase to decrypt the file.
[17:29] <enraged> jpds: So yeah, totp codes generated by a phone or something else as secondary authentication, because they'd then need to hack the phone aswell
[17:30] <jpds> enraged: Welcome to the world of paranoia. Encrypt your /home directory on the laptop.
[17:30] <enraged> jpds: Oh man! I wish I could, but the circumstances I'm in, the laptop is Windows 7.
[17:30] <sarnold> enraged: see if this helps: https://www.duosecurity.com/docs/duounix
[17:30] <enraged> jpds: So yeah, now you understand why I'm so nervous XD
[17:30] <Free99> anyone know how I can enable the "remember" option in PAM?
[17:30] <enraged> sarnold: Thanks. I remember annoying you about this a while back.
[17:30] <Free99> I'm not clear on how to do it
[17:31] <sarnold> enraged: yes, and I remember being very annoyed that I didn't completely understand opeenshd at the time :)
[17:31] <enraged> sarnold: No problem man; It's what, a month later, and I still haven't figured this one out.
[17:32] <jpds> enraged: You can still encrypt things on Windows (truecrypt and co.).
[17:32] <enraged> jpds: Oh yes, but the private key file is stored on a usb stick anyways seperate from the laptop.
[17:32] <sarnold> Free99: pam_cracklib's "similar" might do it?
[17:32] <enraged> jpds: So the win7 laptop itself isn't the concern, just a keylogger and filestealer being installed.
[17:32] <sarnold> enraged: man :/ you think this would be easier..
[17:33] <Free99> enraged: what about using libpam-oath?
[17:33] <enraged> sarnold: I talked to the guy who wrote the sirc protocol yesterday and mentioned this to him. Didn't believe me so he logged onto his test server, spent 10 minutes playing arond and came back giving me a puzzled look.
[17:33] <Free99> sarnold, i'll take a look thanks
[17:34] <sarnold> enraged: hahah :)
[17:34] <sarnold> enraged: well, at least I'm not the only one then
[17:34] <mgw> I have a firstboot script in rc.local (I used vm-builder). How can that script cause a reboot?
[17:34] <sarnold> that makes me feel a touch better :)
[17:34] <enraged> free99: Whole problem here is you can't use PAM
[17:34] <sarnold> mgw: by calling /sbin/reboot ?
[17:34] <mgw> Simply rebooting aborts rc and the firstboot flag never gets set
[17:34] <mgw> so it repeats the reboot after every boot
[17:34] <jpds> mgw: Nice.
[17:35] <Free99> but enraged, sshd authenticates against pam
[17:35] <sarnold> ah :) good luck ;)
[17:35] <sarnold> Free99: only for passwords..
[17:35] <mgw> sarnold, jpds: I guess I can set the firstboot flag manually
[17:35] <jpds> mgw: Store that you've firsted boot in a file and check if that file exists before you reboot?
[17:35] <sarnold> Free99: if you use keys, it bypasses pam entirely :/
[17:35] <enraged> free99: Only when you use passwords. When you use SSH keys, it bypasses PAM for auth, so you can't use any pam modules.
[17:36] <Free99> hum.
[17:36] <enraged> hum indeed
[17:37] <mgw> jpds: thanks, that's what the rc.local script does, but the firstboot.sh was exiting before it got there. SHould have it fixed now
[17:37] <Free99> enraged, would this help? think about the possibilities: http://jpmens.net/2006/03/02/ssh-public-keys-from-ldap/
[17:38] <jpds> enraged: You could just set up a firewall so that the server only allows access to sshd from your IP address.
[17:39] <Free99> enraged, the idea isn't the LDAP part, its more the fact that the patch allows you to connect via ssh through seeing you have a user account via PAM, then checking the key against...well, whatever you want
[17:40] <Free99> could potentially be a file or a stupid script or w/e you want
[17:40] <enraged> I'll have to read more into this; it's the first time I've seen this post.
[17:41] <jpds> enraged: LDAP doesn't slove your problem.
[17:41] <enraged> It's close to a suggestion I recieved by the sounds of it, where we would have a key server that I logged into with a password and otp code, then from that key server, log onto the other servers
[17:42] <enraged> Yeah, I'll have to read it more.
[17:42] <enraged> I've never heard of LDAP before.
[17:42] <enraged> How bad is that?
[17:42] <jpds> "bad" ?
[17:42] <enraged> Well, OpenSSH is something every sysadmin show know about...
[17:42] <Free99> enraged: it's got a steep learning curve. it's the tech that microsoft borrowed to make active directory
[17:42] <enraged> By comparison, LDAP is....?
[17:42] <Free99> basically a database of user accounts and stuff
[17:43] <enraged> hrm, ok
[17:43] <Free99> update in one place, updated everywhere
[17:43] <enraged> Just to be clear, purely focused on user management or is this just a general file syncing service?
[17:44] <jpds> enraged: User management.
[17:44] <enraged> Ok
[17:44] <jpds> enraged: But you can store other things in it.
[17:44] <Free99> enraged, what service provider do you have?
[17:44] <Free99> for your cell
[17:45] <enraged> British Telecom
[17:48] <Free99> enraged, do you know what BT's sms gateway is?
[17:48] <enraged> No...
[17:48] <enraged> Sorry, you've gone off on a tangent here; what are we/you trying to do?
[17:50] <Free99> enraged, if you want to replicate Google's OTP thing, I was thinking you'd have that pam plugin make the OTP and you can essentially "email it to your phone" via sms
[17:51] <Free99> in the US, if you want to send a text to your phone, depending on your service provider (mine is AT&T) you email "<phone<EMAIL_ADDRESS>and it shows up as a regular text
[17:52] <sarnold> Free99: but PAM isn't available if you're doing ssh authorized_keys :/
[17:52] <Free99> sarnold, unless he uses that patch I just linked him
[17:52] <sarnold> Free99: jpmen's ldap-thingy?
[17:52] <Free99> yeah. the LDAP is totally PAM-based
[17:52] <sarnold> aha :)
[17:52] <enraged> Free99: Oh, I understand!
[17:53] <enraged> Free99: One second.
[17:53] <Free99> oh dang. the link to the patch is dead
[17:54] <Free99> oh wait! github to the rescue!
[17:54] <Free99> https://github.com/rfay/OpenSSH-LPK
[17:55] <enraged> Free99: Ok, so at the moment, I have an app on my phone (Android) that produces the TOTP codes without contacting the server I'm connecting to. The problem is, how do I get the SSHd server to request the second authentication method, of the totp code, and then compare it against the PAM module which will confirm or declare false the code entered.
[17:55] <jpds> Free99: You do realize using a hacked up version of OpenSSH like that is going to be a security nightmare in the long term?
[17:55] <enraged> Free99: The PAM module is supposed to initiate after a succesful password login that then waits for the user to enter the TOTP code before giving Shell
[17:56] <enraged> jpds: At the moment, this is more technical curiosity.
[17:56] <enraged> jpds: If it can just be done I'll be happy.
[17:56] <Free99> jpds, yeah.. I know. But how can I trust anyone tbh? Just because the repos are canonical maintained, doesn't mean they're always trustworthy. Even kernel.org... http://www.theregister.co.uk/2011/08/31/linux_kernel_security_breach/
[17:57] <jpds> Free99: No, I meant more like having to compile and update OpenSSH by hand every time an update comes out in precise-updates.
[17:58] <Free99> jpds, perhaps enraged will become a repo contributor... that's how it starts right?
[17:58] <enraged> BWA HA HA
[17:58] <Free99> openssh-server-lpk? lol
[17:58] <enraged> Free99: I think you're overestimating my capabilities
[17:59] <Free99> enraged, that's on you bro haha
[17:59] <Free99> anyhow I'm enjoying my 5th of july off. Gonna hit the pool. see you guys! and good luck
[17:59] <enraged> See ya man
[18:00] <sarnold> enraged: the duo-security thing looks like an unfortunate hack the way it's implemented, but a pal who I trust uses it, so perhaps the caveats are worth it :)
[18:00] <mgw> Free99: upstream has AuthorizedKeysCommand directive for ssh
[18:01] <enraged> Sarnold: Yeah I'll have to give it a proper look later.
[18:02] <enraged> I don't think Free99's ldap proporsal really solves the problem; it looks very similair to a certificate authority
[18:04] <sarnold> enraged: he is only suggesting it because it patches sshd to use the PAM stack before doing ssh keys
[18:04] <sarnold> enraged: the ldap is just a side effect
[18:04] <sarnold> .. and probably one you can ignore
[18:05] <enraged> ok
[18:05] <enraged> I think I'm starting to get a bit closer to fully understanding why he wanted to do this now then :p
[18:06] <enraged> I'll be reading through the duo security manual though before I decide which to try first
[18:07] <sarnold> enraged: I'd also like to suggest against running a patched sshd :)
[18:07] <sarnold> it's fragile code.
[18:08] <sarnold> or, it has a long history of being fragile..
[18:08] <enraged> Yeah, probably the main reason I am going to put my hope in your duo security suggestion...
[18:09] <enraged> If this doesn't work, I'll come back and annoy you some more with the forcecommand issue...
[18:09] <sarnold> :)
[18:09] <enraged> Sarnold: You have so much fun to look forward to!
[18:09] <sarnold> hehe
[18:20] <thinknow> someone have an idea how to connect my server trough tor/vidalia ?
[18:21] <thinknow> i have tried some tutorials, but cant find any apps that make this job easy or stable
[18:22] <sarnold> thinknow: I think what you're looking for is tor onion addresses. maybe ask in #tor on irc.oftc.net.
[18:23] <thinknow> ok i will look it up:)
[18:23] <thinknow> thank you
[18:41] <sandprickle> I've been trying for hours to get Nginx+php fpm working to no avail. Precise. Nginx 1.4.1 from the Nginx repo. All other packages from ubuntu repos. What might I be missing?
[18:42] <sarnold> sandprickle: anything in hte logs?
[18:43] <sandprickle> yeah: 2013/07/05 14:34:22 [crit] 25963#0: *1 connect() to unix:/var/run/php5-fpm.sock failed (13: Permission denied) while connecting to upstream, client: <IP_ADDRESS>, server: localhost, request: "GET /test.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost"
[18:43] <sandprickle> file permissions?
[18:47] <rOYk> smells like PEBKAC
[18:52] <sarnold> sandprickle: could be; what ar ethe permissions on /var/run/php5-fpm.sock? does the nginx process owner have privileges to talk with thatsocket?
[18:58] <sandprickle> www-data owned /var/run/php5-fpm.sock; did chown nginx:www-data /var/run/php5-fpm.sock; now I get a different error..
[18:59] <sarnold> yeah don't change the ownership of the socket... the fpm runner should own it, it provides the socket after all :)
[19:02] <sandprickle> Yeah, that didn't work. added nginx to the www-data group. now getting this: 2013/07/05 15:01:15 [error] 26598#0: *1 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: <IP_ADDRESS>, server: localhost, request: "GET /test.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "localhost"
[19:02] <sarnold> TheLordOfTime: ^^^  :)
[19:03]  * TheLordOfTime looks
[19:03] <TheLordOfTime> sarnold:  you did poke me at a bad time though
[19:03]  * TheLordOfTime was beating an nginx FTBFS
[19:03] <sarnold> TheLordOfTime: d'oh :)
[19:04] <TheLordOfTime> sandprickle:  pastebin your conf
[19:04] <sandprickle> sure thing
[19:06] <sandprickle> it's in multiple files... multiple pastes or just one (pastebin n00b)
[19:10] <sandprickle> nginx.conf: http://pastebin.com/9WCkccyt conf.d/dev.conf: http://pastebin.com/9SmR5Y9X fastcgi_params: http://pastebin.com/sTprY17D
[19:10] <sandprickle> TheLordOfTime: ^^
[19:14] <sandprickle> /etc/php5/fpm/pool.d/www.conf: http://pastebin.com/PxVz0JUy /etc/php5/fpm/php.ini: http://pastebin.com/D3AjBb4L
[19:24] <TheLordOfTime> sanderj_:  sorry i'm like jugging a billion things
[19:24]  * TheLordOfTime looks now
[19:25] <TheLordOfTime> erm
[19:25] <TheLordOfTime> sandprickle:  ^
[19:26] <sandprickle> no worries. #nginx woke up now anyway.
[19:26] <TheLordOfTime> sandprickle:  yes they did
[19:26] <TheLordOfTime> having said that i see a few pitfalls
[19:48] <Vec_brb> On my apache server, i have java.html with 004 permissions. If the file is owned by root user and root group, i can view the file in my browser. If www-data group owns the file, i get permission denied. How come? o.O
[19:48] <sarnold> Vec_brb: permissions are checked in the order of user, group, world
[19:49] <sarnold> Vec_brb: when the web server owns the file, the first check finds '0', and returns forbidden
[19:50] <Vec_brb> Oh, derp..
[19:50] <Vec_brb> In other words, im denying the owner of content in displaying it to my browser?
[19:53] <Vec_> Yeah, i could make www-data the owner group and give that group read permissions with everyone else at 0 and it works. I assume this is because its the www-data group that is because my user which is in www-data is responsible for serving the site
[19:53] <sarnold> Vec_: yes, and worse, if your web server is compromised, it'd be easy for the file permissions to be set back to allowing the server to write the file, and then changes be made ot your website content in a persistent fashion
[19:54] <sarnold> Vec_: web servers shouldn't own any of the content they serve -- their only write privileges should be their log files, database and fast-cgi-like sockets
[19:55] <Vec_> sarnold: Ok. So best practice is having no owners on the files with 004 permissions ?
[19:56] <sarnold> Vec_: well, make sure www-data doesn't own any more files than necessary; 004 is another matter (it's overkill, and perhaps counter-productive..)
[19:59] <Vec_> There is only one user in www-data, me (the server superuser?), i don't see why it would be bad for effectivly me to own the files in my webdirectory.. I'm 100% new at this linux stuff, and i just installed LAMP so im kinda fumbeling atm >..<
[20:00] <Vec_> I mean, does it matter when i can control the permissions anyway. And if my user is compromised then im fubared anyway
[20:00] <sarnold> Vec_: on the one hand, you're right, if the servre gets compromised you're better off re-building from backups
[20:01] <sarnold> Vec_: but business demands sometimes means fixing the iimmediate problem and getting back to business while you rebuild a new machine
[20:03] <Vec_> sarnold: Thanks for making me understand what happened on my original question. Other than that i feel like you are replying with knowledge way outside my league at this point in time. Im just a random student who installed linux a week ago and now i have this awsome server up and running with some basic services like printersharing/filesharing/automated backup and now this LAMP server.
[20:03] <Vec_> I should probably just read a whole lot more HOWTOs and documentation instead of conversing in this channel on a level i dont yet fully comprehend ^^
[20:04] <Vec_> I was kinda apprehensive about installing LAMP tho as it exposes me so much (i assume) to the net.. Therefore i think i should read more to limit my exposure and get the permissions and fileownership right (and understand it too)
[20:06] <sarnold> Vec_: heh, fair enough, just mark down that you'll want to ask me about it again in another six months or osmething :)
[20:06] <sarnold> I've got a nice rant written about it somewhere..
[20:07] <Vec_> ^-^
[20:08] <Vec_> Hm, i should probably only installed apache, considering i really just want to serve static pages with java applets i program for school
[22:53] <hallyn_> stgraber: are you by any chance around with a few minutes to look at an ugly lxc patch?
[22:55] <hallyn_> (if so, http://people.canonical.com/~serge/0011-cgroup-hook-handle-stricter-kernel - else, i'll test some more and push to saucy and post to list)
[23:03] <stgraber> hallyn_: +INFO("XXX checking subsystem %s against string devices len %d", cg->subsystem, len);
[23:03] <stgraber> hallyn_: did you mean for those three INFO to stay there? the XXX looks like a temporary thing
[23:05] <stgraber> hallyn_: besides that, as ugly as it's, it looks fine
[23:08] <hallyn_> i kind of wonder if we went ahead and setup all the cgroups first, then ran hooks, then entered cgroup at very end, if that would be better overall
[23:08] <hallyn_> meanwhile upstream git has diverged there from saucy's pkg...  already split up the devices setup a bit
[23:09] <hallyn_> still, this is passing tests
[23:10] <hallyn_> stgraber: you've told me before, but can't find it in my irc logs -  were you planning on merging upstream git in july?
[23:13] <hallyn_> well really the clean solution will be "if you want nesting, use user namespaces and the cgroup management agent."  <shudder>
[23:24] <stgraber> hallyn_: I've been pretty busy with other things but I think we should try and get an alpha release done upstream in early August, then use that for saucy
[23:25] <stgraber> hallyn_: what we end up shipping with in saucy I don't really care much about, it's a non-LTS release with a 9 months support period, so as long as it's fairly recent and it works...
[23:32] <hallyn_> stgraber: sounds good.
[23:32] <thinknow> lol question, but command in ubuntu server for starting ftp host ?
[23:35] <sarnold> thinknow: apt-get install vsftpd, edit the configuration as necessary, then 'service vsftpd start'   ought to do it
[23:36] <thinknow> ok thnx