[02:45] <mdeonte> Is there a way that I could set 2 owners for a group?
[02:45] <mwhudson> you can make the owner be a team
[02:45] <mdeonte> mwhudson; then members of that team can have control?
[02:46] <mwhudson> mdeonte: right
[02:46] <mdeonte> shweet
[10:30] <KabEe> hello
[10:30] <KabEe> website builder for launchpad.net around?
[10:31] <KabEe> i found some spam on it
[10:43] <KabEe> nevermind, i spoke with intellectronica
[11:07] <dholbach> hiya
[11:08] <dholbach> can somebody help me with hitchhiker and getting me to push lp:~loco-directory-dev/loco-directory/0.2?
[11:08] <dholbach> I thought I had deleted the branch from LP
[11:08] <dholbach> but there seems to be something still lingering around
[11:08] <dholbach> and I get:
[11:08] <dholbach> bzr: ERROR: KnitPackRepository('lp-64802192:///~loco-directory-dev/loco-directory/trunk/.bzr/repository')
[11:08] <dholbach> is not compatible with
[11:08] <dholbach> CHKInventoryRepository('lp-64802192:///~loco-directory-dev/loco-directory/0.2/.bzr/repository')
[11:08] <dholbach> different rich-root support
[11:09] <wgrant> dholbach: You're pushing a 2a branch, and it's trying to stack on the pack-0.92 development focus.
[11:10] <dholbach> wgrant: how can I get it not to stack? :)
[11:10] <wgrant> dholbach: Just push again, without deleting.
[11:11] <dholbach> we have LOTS megabytes of cruft in the old branch and wanted to start 0.2 branch from rev1
[11:11] <dholbach> (yeah, I know)
[11:11] <wgrant> Ah.
[11:11] <dholbach> somebody committed megabytes of map data which makes it painful to push a new branch for every review and stuff
[11:12] <wgrant> Ew.
[11:12] <wgrant> But stacking should have minimised that problem.
[11:12] <dholbach> it still takes a long time
[11:12] <dholbach> wgrant: anything I should do about: "This transport does not update the working tree of: bzr+ssh://bazaar.launchpad.net/~loco-directory-dev/loco-directory/0.2/."
[11:12] <dholbach> ?
[11:12] <dholbach> wgrant: will that make loggerhead not work?
[11:13] <dholbach> ah no, it works
[11:13] <dholbach> thanks wgrant
[11:13]  * dholbach asks a lot of stupid questions today :)
[14:16] <cjwatson> hi, can I prod a LOSA about https://answers.launchpad.net/launchpad-code/+question/94536 ? I've got the rest of my openssh imports in place now, so this is really the last piece I need
[14:16]  * mthaddon looks
[14:34] <jdaly> Hi, Ive noticed that my branch revisions no longer show up in my karma. I checked some other folks karma and it appears theres are still functioning. Any ideas?
[14:39] <mthaddon> cjwatson: done
[14:43] <cjwatson> mthaddon: ta
[14:44] <cjwatson> mthaddon: hmm, should I not expect to see something other than "Packs containing knits without subtree support" on https://code.launchpad.net/~vcs-imports/openssh/main? That sounds like an old branch format to me ...
[14:45] <mthaddon> cjwatson: hmm, not sure if there needs to be some kind of import somewhere - I'm in mwhudson's hands on this one I'm afraid
[14:45] <jamalta> actually, we should make an rsvp page for ubuntu hour
[14:46] <jamalta> eh,, sorry.. that was supposed to go to another channel
[14:46] <cjwatson> mthaddon: I'll wait until a bit later today and follow up on the ticket if it doesn't fix itself
[14:46] <mthaddon> cjwatson: sounds good
[14:47] <cjwatson> is it possible to register a mirrored branch in the source package namespace? (I'd like to ask Launchpad to import a branch from bzr.debian.org, and it ought to live in ~cjwatson/debian/sid/lucid/debian or something like that)
[14:48] <cjwatson> I can do it with https://code.launchpad.net/openssh/+addbranch, but https://code.launchpad.net/debian/+source/openssh/+addbranch doesn't exist
[14:52] <cjwatson> ah, bug 347755
[14:58] <leoquant> security updates to FireFox 3.0.x in Ubuntu 8.04 have
[14:58] <leoquant> been based on security updates from upstream (Mozilla project)
[14:58] <leoquant>  But as I
[14:58] <leoquant> understand it, the stream of security updates from upstream is about to
[14:58] <leoquant> stop.
[14:58] <cjwatson> leoquant: #ubuntu-mozillateam would be a better place to ask
[14:59] <leoquant> ok
[15:00] <akgraner> deryck, ping
[15:01] <akgraner> if you have a couple mins I need to pick you brain about some bug stats
[15:01] <akgraner> s/you/your
[15:02] <deryck> akgraner, hi.  Sure.  I have a couple minutes.
[15:03] <akgraner> deryck, do you look and the bug stats section in UWN at all?
[15:03] <akgraner> deryck, https://launchpad.net/ubuntu/+bugs  this is the link we used to use to get those stats
[15:03] <akgraner> but now the information we used to report on isn't there any more
[15:04] <akgraner> so I need help in getting that information again
[15:04] <akgraner> specifically unassigned and total bugs reported
[15:04] <akgraner> I tried the advanced search and the numbers weren't even close
[15:04] <deryck> akgraner, looking at the +bugs page for a second...
[15:05] <akgraner> deryck, thanks
[15:05] <akgraner> :-)
[15:05] <deryck> akgraner, what info was there but isn't now?
[15:05] <akgraner> total number of bugs every reported
[15:05] <akgraner> and unassigned
[15:07] <akgraner> unassigned we used the advanced search and got close enough
[15:07] <akgraner> but I can't figure out how to get total number of bugs reported to date
[15:08] <deryck> hmm, I see that's gone now.  Had noticed.  Wonder why we dropped that.
[15:08] <akgraner> this was the last number we reported  All bugs ever reported (356337)
[15:08] <deryck> intellectronica, was this ^^ (total bugs and unassigned bugs being dropped from +bugs home) part of the 3.0 redesign?
[15:08] <akgraner> so if we could get unassigned and totals back that would sure make the UWN staff happy campers  :-)
[15:10] <intellectronica> deryck: yes
[15:10] <intellectronica> akgraner: you can still get these numbers with a search
[15:11] <deryck> intellectronica, I don't recall talking about these specific bits of info (which is fine, of course) but did we drop them feeling they weren't as useful to general users?
[15:11] <akgraner> intellectronica, I tried and got the unassigned
[15:11] <akgraner> but I must have been doing something wrong with trying to get totals
[15:11] <akgraner> intellectronica, this was what we last reported All bugs ever reported (356337)
[15:12] <akgraner> and I could not even get close to that number...
[15:12] <intellectronica> deryck: yes for total number of bugs. i don't remember why unassigned got left out, and i think it might be useful
[15:13] <akgraner> intellectronica, willing to learn how.. could someone just email me or walk me through the correct boxes to tick?  I ticked all the status boxes
[15:13] <deryck> intellectronica, yeah, total feels a bit like it go in some leading paragraph.  i.e. 356337 bugs reported here.  And I think unassigned would make a nice filter still.
[15:13] <deryck> akgraner, I think you want to check all statuses and uncheck hide duplicates.
[15:14] <intellectronica> deryck: sure, i'll file a bug. might even do it later, it's very little work
[15:14] <akgraner> deryck, ok do I have to do 2 searches or will it include the nobody ones as well
[15:14] <deryck> intellectronica, excellent.  thanks!  It could actually fall in CHR since akgraner asked about it. ;)
[15:15] <intellectronica> akgraner: b.t.w if this is something you want to do regularly (to track the number or something) you could also easily set up a script to read it using the api.
[15:15] <intellectronica> we can help you write it, of course
[15:16] <akgraner> intellectronica, always willing to learn
[15:16] <deryck> akgraner, by "nobody ones" if you mean the unassigned bugs, that would be a subset of the all bugs query I gave you.  So I would two two searches -- one for all bugs and one for unassigned.
[15:16] <akgraner> then add them together and I should have the total in theory right..
[15:17] <akgraner> intellectronica, it's 5 lines on UWN we report on... # Open (76454) +61 over last week
[15:17] <akgraner> # Critical (41) +8 over last week
[15:17] <akgraner> # Unconfirmed (39611) +121 over last week
[15:17] <akgraner> # Unassigned (67029) +73 over last week
[15:17] <akgraner> # All bugs ever reported (356337) +1821 over last week
[15:17] <akgraner> and the difs from week to week
[15:17] <intellectronica> wow, the new post-dupe-search anim looks like a compiz effect
[15:18] <akgraner> those were from 2 weeks ago just so you can see what we use them for
[15:18] <deryck> akgraner, I believe the query I gave you will include unassigned bugs.  intellectronica, or am I understanding this wrong, that assignee "doesn't matter" is only if there is an assignee?
[15:19] <intellectronica> deryck: you are correct. "doesn't matter" means any assignee or none. it doesn't filter by assignee
[15:19] <deryck> right.
[15:19] <deryck> akgraner, see ^^
[15:19] <akgraner> deryck, intellectronica thanks..:-)
[15:19] <deryck> akgraner, no problem.
[15:20] <akgraner> just wanted you all to see why we needed the stats...
[15:21] <akgraner> and since you all are the bug people... is there something else you would perhaps like to include with those numbers  while I am hear and asking
[15:21] <akgraner> here even
[15:22] <intellectronica> akgraner: looks like a perfect use case for a script. if you tell me a bit more about it i can help you write it so that you can run it regularly
[15:23] <akgraner> intellectronica, awesome  can I email you?
[15:23] <intellectronica> akgraner: sure thing
[15:24] <akgraner> intellectronica, thank you so much!!
[15:24] <akgraner> will get that out to you in just a few then
[15:55] <genete> Hi, I'm currently the most visible header of Synfig Studio project. We are looking for a new host service to migrate to. Current host of Synfig is giving some troubles to make the community grow. We need some info about launchpad and its features, anyone?
[15:56] <akgraner> intellectronica, email sent to gmail account is that ok?
[15:56] <cody-somerville> genete, https://launchpad.net/+tour
[15:56] <akgraner> intellectronica, also Thank you again!  much appreciated,  :-)
[15:56] <intellectronica> akgraner: that's fine
[15:56] <intellectronica> akgraner: no problem, my pleasure
[15:58] <genete> cody-somerville: yes, the tour is great but I need more info. For example, Synfig has already a forum (phpBB) and a wiki (mediawiki) database  with its own users. Can we migrate them to launchpad without problems?
[15:58] <cody-somerville> genete, No. Launchpad does not provide those types of services.
[15:59] <genete> current host service we have has problems with sendmail so it doesn't allow us to make the community grow
[16:00] <genete> so wiki and forum has to be hosted externally launchpad, right?
[16:00] <cody-somerville> genete, Thats correct, yes.
[16:00] <genete> Hmmm what a pita
[16:35] <thomas> going crazy trying to dput my package into launchpad.  Can't seem to get the changes file right. I get the error "no valid opengpg date"
[16:35] <geser> thomas: what did you try?
[16:35] <al-maisan> thomas: the date should be in `date -R` format
[16:36] <geser> usually signing during build (dpkg-buildpackage or debuild) or using debsign later on the .changes files works
[16:37] <thomas> first I created my debian/files and then did dpkg-genchanges and then gpg to create the asc file
[16:37]  * al-maisan reconsiders
[16:37] <cjwatson> you should not create debian/files by hand
[16:37] <cjwatson> dpkg-buildpackage should create that; it should also take care of running dpkg-genchanges for you
[16:38] <thomas> When I ran dpkg-buildpackage some error showed up and then it stopped just before createing the files
[16:38] <cjwatson> debug that, then :)
[16:38] <thomas> ok. Thanks for pointing me in the right direction.  Actually If I just run dpkg-buildpackage it should work...
[16:38] <cjwatson> 'dpkg-buildpackage -S' (or 'debuild -S') is the proper way to create a source package for upload to Launchpad
[16:44] <joaopinto> hello
[16:44] <joaopinto> is there an example how to get the bug list for a specific project ? I coudn't figure from the launchpad api doc
[16:51] <joaopinto> assuming it's possible
[16:52] <thekorn> joaopinto, that's easy, let me try to find get an example
[16:53] <joaopinto> I have looked at the bugs collection, there is no reference to bug queries excep by using bug nrs
[16:53] <thekorn> joaopinto, http://paste.ubuntu.com/344175/
[16:54] <thekorn> this gets a list of all bugs in the bughelper project
[16:56] <joaopinto> thekorn, just what I was needing, thanks :)
[16:56] <thomas> now I did the dpkg-buildpackage and it says "dpkg-genchanges error; cannot open file list"
[17:07] <cjwatson> thomas: it would be easier to analyse your problem given a full build log on paste.ubuntu.com
[17:09] <thomas> thanks.  It seems to be working somewhat now. With the S flag it seems to have worked except that I needed to run gpg manually. As we speak dput is putting the files up on my ppa
[17:12] <thomas> hmm... Strange.  It said "successfully uploaded packages but I don't see the packages in my ppa.  Does it take some time to get there?
[17:12] <bigjools> it takes up to 5 minutes
[17:13] <noodles775> ...and you should get an email within 5mins too.
[17:13] <bigjools> if it takes longer then see https://answers.launchpad.net/soyuz/+faq/227
[17:14] <thomas> ok .. thanks...
[17:26] <zekopeko___> hi
[17:26] <zekopeko___> could somebody tell me how to manually merge translations in trunk?
[17:36] <joaopinto> TypeError: can't subtract offset-naive and offset-aware datetimes <- any hints how to determine the bug age using python ?
[17:36] <jamalta> Any launchpad admins willing to show this question some love? https://answers.edge.launchpad.net/launchpad/+question/94519
[17:36] <jamalta> :)
[17:39] <intellectronica> jamalta: sure, i'll assign it to the admins team
[17:40] <chmac> I gots me a question about imports. I'm looking at wordpress on launchpad, I think it makes sense to import both trunk and branches/2.9 from svn. Any idea how to progress that?
[17:40] <jamalta> intellectronica: thank you!
[17:41] <chmac> The code in trunk and branches/2.9 will diverge. The useful code is really in branches/2.9, but the vcs import page says it will only import trunk.
[17:43] <chmac> intellectronica: Are you the help person?
[17:44] <intellectronica> chmac: at your service :)
[17:45] <chmac> intellectronica: :-)
[17:45] <intellectronica> chmac: how can i help?
[17:45] <chmac> intellectronica: Is it possible to get http://svn.automattic.com/wordpress/branches/2.9/ imported into launchpad as well as the trunk branch?
[17:46] <intellectronica> chmac: no, we usually only import trunk from cvs/svn
[17:46] <chmac> intellectronica: The word "usually" is my focus here... :-)
[17:46] <intellectronica> i don't know if it's a technical limitation or just a policy. why do you want to import it?
[17:46] <chmac> intellectronica: Let me rephrase another way, what steps would I need to go through to convince somebody to import branches/2.9? :-)
[17:47] <intellectronica> abentley: do you know if it's possible (technically) to import a non-trunk branch from svn?
[17:47] <chmac> intellectronica: The code in branches/2.9 is production quality, trunk isn't really. I want to start remixing versions of WordPress. The useful code for that is in branches/2.9
[17:47] <chmac> It's the way WP uses code, branches/2.9 starts to diverge from trunk almost immediately
[17:48] <intellectronica> chmac: i think that's a legitimate use case. why don't you try setting up an import. if it's successful i'll approve it
[17:49] <chmac> :-)
[17:49] <abentley> intellectronica: Yes, it's technically possible, but it's a bad idea because it won't be compatible with trunk.  This will be fixed for new imports when we switch from cscvs to bzr-svn.
[17:49] <chmac> abentley: What does "not compatible with trunk" mean?
[17:49] <intellectronica> abentley: right, so that's why we don't do it. the same revisions will be different in trunk and in the other branch?
[17:50] <chmac> The same revision numbers (r3, r4, etc) would exist in both branches but be related to different actual changesets, is that the issue?
[17:50] <abentley> chmac: The import will assign different ids to the revisions and files, so merging them will be impossible.
[17:51] <chmac> abentley: Merging from trunk to branches/2.9 for example?
[17:51] <abentley> chmac: yes.
[17:51] <chmac> Hmm, let me ponder that for a few minutes. I wonder if that will be an issue in this case...
[17:52] <chmac> In this case, I don't think that will be a problem.
[17:53] <chmac> Most developers will still use svn, so anything that needs to go from trunk to branches/2.9 would be done by somebody in svn.
[17:53] <chmac> I see the use on launchpad as creating "custom spins" of WordPress, to use Fedora's terminology
[17:54] <chmac> intellectronica: I'll request the import now... :-)
[17:54] <intellectronica> chmac: cool
[17:57] <chmac> intellectronica: Ok, sent the request, hopefully I got the urls correct, I double checked them... :-)
[18:12] <chmac> intellectronica: Any idea on a timescale for the 2.9 branch to be imported (or not as the case may be... :-) ?
[18:13] <chmac> I'm refreshing the page every few minutes, but that might be overly optimistic, I did read from a few hours to a few days on the wiki
[18:14] <intellectronica> chmac: it really should run soon
[18:14] <chmac> Cancel that, message from Tom Beger "The import has been approved and an import will start shortly." :-)
[18:14] <chmac> Just got the email...
[18:42] <AnAnt> Hello, does LP support 3.0 source format now ?
[18:47] <chmac> AnAnt: What's 3.0 source format?
[18:48] <sinzui> AnAnt: Yes it does, but I am not certain it is fully operational to all users.
[18:49] <thekorn> intellectronica, hey, is there any action from me needed to get https://code.edge.launchpad.net/~thekorn/launchpad/affects_in_interleaved_activitylog/+merge/16261 merged, or is it just patience ;)
[18:49] <AnAnt> chmac: erm,  a new source format
[18:49] <intellectronica> thekorn: actually, thanks for reminding me. i need to merge it and will do it now
[18:51] <RoAkSoAx> hey guys any idea of why i'm getting this error when using launchpadlib??: 'IOError: [Errno 36] File name too long:...[]'
[18:51] <thekorn> intellectronica, super cool, thanks
[18:52] <rCX> How do I make a hyperlink when commenting at bugs.launchpad.net?
[18:53] <chmac> AnAnt: A new source format for what? For bazaar?
[18:54] <AnAnt> chmac: source package format
[18:55] <intellectronica> rCX: you can't make a hyperlink, but urls are linkified, as are mentiones of other bugs or of branches
[18:55] <chmac> AnAnt: Ok, sounds like packaging talk, way over my head :-)
[18:56] <rCX> intellectronica: so if I put "#12345" it will be linked automatically?
[18:56] <AnAnt> chmac: yup, packaging talk indeed
[18:58] <thomas> I sent my package to ppa an hour ago.  Seems launchpad does not know my key.  But everything seems completely right.  Nice key in launchpad and same key in gpg...
[18:58] <thomas> I have not received any mail either
[18:58] <intellectronica> rCX: 'bug #12345' will be
[18:59] <rCX> intellectronica: ok thx
[19:00] <thomas> any ideas what could be wrong???
[19:01] <intellectronica> thomas: https://answers.edge.launchpad.net/soyuz/+faq/227 perhaps?
[19:02] <thomas> Well, I signed the package changes file with the same key I have in launchpad and sent it and dput worked for a while sending the file
[19:02] <thomas> so I tried everything in that link
[19:03] <thomas> Is there any way to test my key???
[19:03] <thomas> it should be ok
[19:04] <ScottK> intellectronica: Is something stuckon soyuz so that package builds aren't getting initiated for Ubuntu?
[19:05] <intellectronica> ScottK: i wonder if that's the case. it seems code imports aren't running either
[19:05] <ScottK> OK, you're listed as help contact, so Help!
[19:07] <intellectronica> ScottK: spray some UBIK on the clouds? ;) i'm trying to get an admin to look at it for us. will update you as soon as i know anything
[19:07] <ScottK> Thanks.
[19:10] <intellectronica> thomas: did you try to do something else which requires signing with that key, like signing an email to the launchpad bug email interface?
[19:15] <thomas> intellectronica: I signed the Ubuntu code of conduct.  That should test the key....
[19:16] <intellectronica> thomas: right, yes, that's an adequate test
[19:16] <zekopeko___> hey could somebody show me how to do some merge translations foo?
[19:17] <zekopeko___> as stated before i need to sync a translation to trunk
[19:17] <thomas> when I do gpg --list-keys I see I have a "pub" key with same name that is in my launchpad and then a "sub" key.  It it perhaps the sub key I should be using???
[19:17] <zekopeko___> transl. is already on lp just needs sync to trunk
[19:18] <zekopeko___> so can somebody help. the guy that knows this lp black magic isn't online
[19:24] <intellectronica> ScottK: would you mind filing a question with all the information you have, so that we care share it with the soyuz folks later, and with an admin?
[19:25] <ScottK> intellectronica: I'm not sure what to say other than package builds aren't starting and there are a bunch in queue.
[19:26] <intellectronica> ScottK: that's a good start :)
[19:28] <ScottK> intellectronica: https://answers.launchpad.net/soyuz/+question/94802
[19:30] <cjwatson> abentley: compatible> I spent the entire weekend constructing very very careful manual imports of a bunch of openssh branches using cscvs :)
[19:32] <cjwatson> openssh is in CVS upstream, so bzr-svn wasn't an option
[19:34] <abentley> cjwatson: Sorry, I don't follow you.
[19:35] <cjwatson> oh, just noting that it is just about possible to make file-id-compatible branch imports using cscvs, although quite possibly far more trouble than it's worth
[19:58] <chmac> intellectronica: I got an email saying the branch would imported a couple of hours ago, no visible progress on launchpad.net yet. Is patience the order of the day?
[19:58] <chmac> intellectronica: I'm wondering if something has gone wrong with the import or I just need to wait... :-)
[20:00] <ScottK> intellectronica: It's fixed.  Thanks for the help.
[20:03] <geser> thomas: and you have only one gpg key? (just asking to be sure that dpkg-buildpackage doesn't pick the wrong one)
[20:15] <joaopinto> hi
[20:16] <joaopinto> using launchpad lib, I can't use any of the fields listed for bugs on the searchTasks( orderby parameter
[20:17] <joaopinto> is there a specific list of fields for the orderby ? They don't seem to match bug fields
[20:21] <maxb> joaopinto: I'm not sure, does https://launchpad.net/+apidoc help?
[20:21] <joaopinto> maxb, I have been reading it already
[20:22] <joaopinto> I think I am getting it, searchTasks returns bug_tasks, not bugs
[20:26] <micahg> less than 1k bugs from 500k
[20:26] <joaopinto> erm, it's a bit messy, you search using a criteria field, then the field is not available on your results :\
[21:14] <zekopeko_> can you upload .po file to translations?
[22:06] <chmac> intellectronica: Code has arrived, 2.9 is a go... :-)
[22:07] <intellectronica> chmac: excellent!
[22:08] <chmac> intellectronica: The branch is lp:~chmac/wordpress/2.9, might make more sense as lp:~vcs-imports/wordpress/2.9 I reckon
[22:08] <chmac> Any idea if / how I can change that without breaking the import?
[22:08] <intellectronica> chmac: your wish is my command
[22:09] <chmac> intellectronica: :-)
[22:09] <chmac> I was just saying on #bzr by mistake, I love the responsiveness of people on this channel, launchpad has a very human feel to it... :-)
[22:09] <intellectronica> chmac: https://code.edge.launchpad.net/~vcs-imports/wordpress/2.9
[22:10] <chmac> intellectronica: Beautiful, now it looks like an independent copy rather than my own personal branch :-)
[22:10] <intellectronica> chmac: i'm glad to hear you've had a good experience. we really do put an effort to make launchpad a true community project
[22:10] <chmac> intellectronica: I was just debating between google code & hg, git & github and launchpad / bzr, looks like I made a good decision
[22:11] <chmac> I particularly like the teams feature, gives us an easy way to let anyone contribute to our code (different project)
[22:19] <mwhudson> heh yes
[22:19] <mwhudson> occasionally i deal with services that don't have teams and then get annoyed
[22:19] <mwhudson> (amazon ec2, for example)
[23:16] <MTecknology> NO! This is NOT cool.
[23:16] <MTecknology> I can't call you rubber duckies anymore...
[23:17] <MTecknology> :'(
[23:18] <wgrant> MTecknology: The LOSA icon has changed; the admins one has not.
[23:20] <MTecknology> wgrant: what is it now?
[23:20] <MTecknology> a glass and what beside it?
[23:39] <chmac> I'm struggling to figure out how to produce a tar.gz from my new wordpress branch lp:~wpflavours/wordpress/wpflavour-no-visual-editor
[23:40] <chmac> I'm not familiar with packaging at all. I'd like to produce a tar.gz of the whole branch so it can be downloaded as a single file rather than via bzr
[23:40] <chmac> Can anyone point me to the right section in help or explain how I go about it?
[23:41] <spiv> chmac: 'bzr export foo.tar.gz' in your local branch
[23:41] <spiv> chmac: and/or are you unsure how to upload that to Launchpad?
[23:41] <chmac> spiv: Yeah, uploading to launchpad is the part I'm not sure about
[23:42] <chmac> spiv: I thought there might be a way to produce the tar on launchpad, but I can do that locally, so thanks for answering that part :-)
[23:42] <spiv> chmac: IIRC it's something like you go to the series and upload it there
[23:42] <chmac> spiv: Ok, I'll look into that, thanks
[23:42] <wgrant> You need to add a release within a series, then add the file to that release.
[23:43] <chmac> wgrant: Ok, thanks
[23:44] <chmac> wgrant: I'm starting a project called WP Flavours to produce multiple remixed versions of WordPress. Would you recommend creating a new project WP Flavours with WordPress as the parent project?
[23:44] <chmac> I'm not an admin on the WordPress project so I don't think I can create new a series there
[23:45] <chmac> I'll ask the admin if he can give me access or do it for me...
[23:45] <wgrant> chmac: What is a flavour?
[23:46] <wgrant> I wonder if perhaps a separate project for each makes sense.
[23:46] <chmac> wgrant: For example, wp-no-visual-editor, exact replica of WordPress 2.9 minus the visual editor
[23:46] <chmac> wgrant: That's a simple example. Flavours might include custom plugins, or edits to core code to achieve a specific purpose.
[23:47] <chmac> We could create a different project for each flavour, set the parent project to WordPress
[23:47] <wgrant> Wouldn't everybody be a whole lot better off if the code changes were turned into config options in Wordpress itself, and everything else just distributed as plugins?
[23:47] <chmac> wgrant: lol, that's a hot topic of debate, there are many who feel that way :-)
[23:48] <chmac> wgrant: One of the key issues that started this for me was the "phone home for updates" feature WP introduced.
[23:48] <chmac> There's no way to turn it off except with a plugin, but by the time WP is installed and you go the plugin management page, it phoned home already
[23:48] <chmac> Only way I can see to install wp without it phoning home is to hack core before installing
[23:49] <chmac> A flavour might simply be a wp core plus a few selected plugins, but packaged as a single tar.gz to make it easier to download / install


[00:43] <slangasek> do not meddle in the affairs of dpkg-maintscript-helper; for its bugs are subtle, and life's too short.
[00:51] <mwhudson> infinity: oops, i forgot to update Maintainer when i added ubuntu delta to dh-golang
[00:52] <infinity> mwhudson: Naughty.
[00:52] <infinity> mwhudson: You can go sit on the bench of shame with doko -- he never updates the maintainer. :/
[00:52] <mwhudson> heh
[00:52] <slangasek> mwhudson: set DEBEMAIL to something appropriately Ubuntuish and dpkg-buildpackage will remind you of this
[00:53] <slangasek> and yeah, I hate doing an ubuntu2 upload behind doko ;)
[00:53] <mwhudson> oh right i guess i should use ubuntu.com for packaging now
[00:58] <stgraber> can someone review lxc and lxd in the queue? lxd is trivial, lxc is a bit bigger what with being an upstream rc release and all
[00:58] <stgraber> I have some hope of tagging final lxc 2.0 tomorrow but that kind of depends on users being exposed to that last rc first :)
[01:04] <infinity> stgraber: Looking.
[01:05] <infinity> stgraber: Oh look, ports support!
[01:06] <stgraber> it was there already as a cherry-picked fix in the previous upload :)
[01:07] <stgraber> but yeah, the Debian maintainer didn't know that archive and ports are separate in Ubuntu so when fixing the ubuntu template on Debian he kinda broke it for everything but amd64 and i386 :)
[01:08] <stgraber> yay, now to tag another lxd rc, hoping that's the last one but as can be seen by the absurd number of rcs we've gone through already, I'm not gonna bet on it :)
[01:09] <stgraber> at least we're done with lxcfs, that's one less thing to worry about
[01:09] <infinity> stgraber: Meh, keep on RCing until release week, as long as the bugfixes are tiny and auditable.
[01:10] <infinity> stgraber: Just gimme a shiny round number before we close the archive. :P
[01:10]  * infinity isn't sure if he'd have more confidence in 2.0rc1 or 2.0rc30, but 2.0 is always prettier)
[01:10] <stgraber> well, our plan was to land the first upstream bugfix release of all 3 before 16.04 releases but for that to work we need to release the actual thing first and for that to happen people should stop reporting rc bugs :)
[01:11] <infinity> rc30 is either a sign of an anal-retentive perfectionist upstream release manager, or people who Really Can't Get It Right, Ever.
[01:13] <infinity> stgraber: Knowing you, I'm sure it's the former, but if it was just some random, I might start thinking it was the latter. :P
[01:13] <infinity> Tag, "crap, it's broken", tag, "crap, it's broken", ad infinitum.
[01:14] <stgraber> :)
[01:14] <stgraber> I thing we had one lxc tag where I had to tag again 10min later because someone landed a change which introduced a new file but which wasn't included in the dist tarball... turns out things don't build when files are missing.
[01:15] <infinity> Picky, picky.
[01:15] <infinity> Also, never push a tag until you've tested.
[01:15] <stgraber> but that was at at the time where the kernel was busted so jenkins was lying to us, otherwise we'd have caught it way earlier (as our jenkins job does a make dist + build + package on all arches we care about and even on Android)
[01:15] <infinity> They're super easy to delete locally.  Super hard to delete from everyone else's computer. :P
[01:16] <slangasek> infinity: you're going to love reviewing this one.  A taste of things to come: http://paste.ubuntu.com/15572738/
[01:16] <stgraber> "./configure && make && make install" worked great locally :)
[01:16] <infinity> slangasek: Dude.
[01:17] <infinity> slangasek: How's the ganja over there?
[01:17] <slangasek> infinity: 100% legal
[01:17] <stgraber> slangasek: you forgot to throw some messing with IFS in there
[01:18] <slangasek> stgraber: haha
[01:18] <stgraber> assuming your goal was to give a headache to whoever reviews it
[01:19] <infinity> I'm already a bit headachey trying to figure out *which* maintscript he feels needs that abuse.
[01:19] <slangasek> stgraber: this is a very parsimonious implementation ;)
[01:19] <infinity> But I'll wait for the glorious finished product before I string the rope.
[01:20] <slangasek> infinity: the preinst and postinst of squid.  The existing Debian package calls dpkg-maintscript-helper in both the squid and squid3 packages, for conffiles previously owned by squid3.  The 'squid' copy of these DTRT *if* you previously had the squid dummy package installed, otherwise it's a complete no-op.  The squid3 copy does the right thing *only if you haven't modified any of the conffiles*;
[01:20] <slangasek>  otherwise it overwrites the squid package's ...
[01:20] <slangasek> ... conffiles with your modified squid3 version with no conffile prompt
[01:21] <slangasek> because dpkg-maintscript-helper looks at the args and says "oh, you have no previous version? jollygood, I'll just noop all this code"
[01:21] <slangasek> so the only way to dtrt is to trick it, in the squid maintscripts, to not no-op
[01:21] <infinity> Gross.
[01:25] <infinity> slangasek: Oh well, to be fair, I pointed someone to the pkgbinarymangler preinst as a "useful example" today, so we all have blood on our hands.
[01:27] <infinity> Speak of the devil.
[01:27] <cyphermox> haha, yeah
[01:27] <cyphermox> now I have bloody hands too, good job
[01:28] <cyphermox> oh wait, there once was usb-modeswitch too.
[01:31] <infinity> cyphermox: Oh, hrm.  I might make you reupload that, even after I pre-reviewed it. :/
[01:32] <infinity> cyphermox: The postinst bit could concievably break if an upgrade breaks for other reasons and then someone does "dpkg -i dbus.deb" over the half-installed dbus.
[01:32] <infinity> cyphermox: ie: instead of the version check in postinst, it should be a check for the diversion, probably.
[01:52] <slangasek> infinity: wow. ok, no, when all is said and done, mv_conffile does entirely the wrong thing for a modified conffile, no matter what... it just moves the new conffile aside and drops the old one in its place, in the postinst, when it's too late to get any conffile prompts.
[01:52] <slangasek> why did we ever stop using Keybuk's cargo culted code snippets again?
[01:54] <infinity> slangasek: Because a single, central copy is better.  If anyone bothers to improve it. :P
[01:54] <slangasek> it wasn't supposed to need improving :P
[01:54] <slangasek> it was supposed to have gotten all this stuff right on the first go!
[02:05] <slangasek> infinity: alright, so it's possible some of the work I did here didn't make a darn bit of difference anyway.  Except that it does simplify the maintscript code quite a bit overall, so probably still worth doing; and it's as good as it's going to get.  So I'll upload and if you balk at the diff I can trim things down
[02:06] <infinity> slangasek: Heh.  Does it upgrade from old versions?  That's sort of the bit that matters.
[02:06] <slangasek> infinity: it does, and it does as well a job of handling modified conffiles as dpkg-maintscript-helper allows it to
[02:07]  * infinity is filing github pull requests in anger over his upstream not understand what an ABI is.
[02:07] <infinity> Or, rather, what an SOVER is for.
[02:07] <infinity> I suppose both.
[02:08] <infinity> (No, not *that* upstream, we don't have libc7 on the horizon)
[02:08] <infinity> Though, man, if we were collectively prepared to go through the pain of another libc transition, we could clean up SO MUCH CRUFT.
[02:08] <infinity> There's a metric whackton of stuff we've removed from the API, but not the ABI.
[02:10] <slangasek> infinity: 2038 man, just drop all entry points that predate 64-bit time_t
[02:10] <rharper> slangasek: \o/
[02:11] <infinity> slangasek: That date is way less scary-far-off-futuristic than it used to be...
[02:12] <slangasek> infinity: we could avoid the transition pain by moving all the computers to within 10 feet of sealevel?
[02:13] <infinity> slangasek: To be fair, that's where an awful lot of them are already.
[02:13] <slangasek> rharper: yeah, squid3 uploaded, it should upgrade everywhere, I'm looking for whiskey now
[02:14] <infinity> slangasek: And it occurs to me that the reason Republicans outwardly appear to be climate change deniers is simply because if they continue to do nothing about it, a large portion of the Democrat voting base will be floating.
[02:14] <infinity> (Along with their fancy datacenters)
[02:21] <slangasek> infinity: PJ O'Rourke: "well sure, we *say* it's not happening, meanwhile we're buying a lot of inland real estate"
[02:26] <infinity> Man, when did 8 o'clock happen?
[02:26]  * infinity goes to find a pizza and take a TV break.
[02:28] <infinity> slangasek: If you had an upstream that bundles multiple libs in the same source, versions them based on source version, and one of them broke ABI, would you be more inclined to recommend decoupling the versioning, or just bump them both in lockstep, even though it's a lie for the unchanged one?
[02:29] <infinity> Guessing the latter is easier to explain.  And it's definitely a simpler patch.
[02:29] <slangasek> infinity: generally, decoupling
[02:29] <slangasek> but yeah
[02:31] <infinity> slangasek: Ain't no autotools or other magic in play, they literally parse the RPM specfile (lolz) for the version, and slap that on the library.  Which works well enough, but isn't amazingly flexible.
[02:32] <slangasek> infinity: software is horrible, where's that bottle of whiskey
[02:32]  * infinity will see if he can catch up with Nate and converse realtime.
[02:49] <bluesabre> Please accept the above mugshot package. Resolves several issues and has been tested by Xubuntu QA
[03:00] <bluesabre> yay!
[03:43] <bluesabre> Please accept the above catfish package. Fixes an issue with displayed timestamps and brings more complete translations.
[03:44] <bluesabre> (sorry for the redundant looking messages, but the first few seem to have worked well, and somebody seems to be seeing them :))
[13:38] <knome> hello release team! the xubuntu team will be doing an upload to our community wallpapers package; this upload doesn't change the default wallpaper, only the some of the wallpapers available by default. would you like some kind of freeze exception paperwork done whatsoever, or can we just upload that once we have picked our winners?
[13:41] <infinity> knome: No exception needed, if the defaults are all the same, IMO.
[13:42] <knome> infinity, ok, cheerio
[13:42] <knome> we'll make sure it lands before the final freeze then :)
[13:43] <infinity> Ta.
[14:31] <teward> can I get the nginx 1.9.13 upload at bug 1563393 reviewed for an FFe?  I'd like to get this reviewed now, and included, and then the next version (to also need review, it'll be before FinalFreeze) will have additional changes - but for that next upload to go in, I'd like 1.9.13 to land first.
[14:31] <ubot5`> bug 1563393 in nginx (Ubuntu) "[FreezeException Needed] Update nginx to 1.9.13." [Wishlist,Confirmed] https://launchpad.net/bugs/1563393
[14:31] <teward> it's not in the upload queue yet, i was waiting for the review before i pushed it up
[15:00] <ogra_> can someone let livecd-rootfs in (i'd like to build a test image before EOD)
[17:30] <infinity> superm1: Unless those symbols really were added with an Ubuntu patch (man, I hope not), you should s/0.7.0-0ubuntu1/0.7.0/ in the symbols file to get sane deps against the upstream version rather than the package version.
[17:32] <infinity> superm1: Also, is there an FFe for this?  It's pretty clearly not just bugfixes.
[17:39] <infinity> xnox: What's the point of differing from upstream on the location of cpuplugd's config file?
[17:40] <infinity> xnox: Seems like a pretty large delta for no good reason.
[17:42] <infinity> xnox: Oh, I see, it's IBM that fed you that patch.  Weird.  Does that mean they intend to move it in the upstream packaging too?
[17:43] <infinity> xnox: Also, shipping a service disabled by default is both un-Ubuntu and un-Debian.
[17:46] <teward> infinity: given the final stretch before Final Freeze, any chance you can look at the nginx FFe for 1.9.13?  I haven't uploaded yet, was waiting on the 'all clear' - bug 1563393.  Tuesday's my deadline on getting 1.9.13 uploaded...
[17:46] <ubot5`> bug 1563393 in nginx (Ubuntu) "[FreezeException Needed] Update nginx to 1.9.13." [Wishlist,Confirmed] https://launchpad.net/bugs/1563393
[17:47] <infinity> teward: Looking.
[17:47] <teward> infinity: thank you kindly, sorry to be a nag :)
[17:49] <infinity> teward: Make it happen.
[17:49] <teward> infinity: thank you kindly!
[17:50] <xnox> infinity, i will not ship a brand new config file in /etc/sysconfig/cpuplugd that it too much redhadish
[17:50] <xnox> infinity, the daemon is weird, i believe default config will make one not use 100% of available resources and scale one back.
[17:50] <xnox> which imho is wrong to be enabled by default, and hence needs user to provide/update config before enabling.
[17:51] <superm1> infinity: ack, reject it and I'll make sure the features are documented in ffe
[17:51] <xnox> infinity, and hence whilst that is undebian and unubuntu, it's least surprise.
[17:51] <xnox> and hence does not warrant to be in a standalone package
[17:51] <superm1> They're used only with new software not in archive but yes technically new features included
[17:51] <teward> infinity: it's waiting approval, can you ACK it?
[17:51] <infinity> xnox: I was with you right up until the last sentence. :P
[17:51] <xnox> infinity, however the osnmp thing adds dependency on three more shared libraries, maybe that should be split into stand alone package
[17:51] <infinity> teward: I did.
[17:51] <teward> ah, email is slow :)
[17:52] <xnox> infinity, so would you rather see cpuplug thing into standalone package, and enabled service by default instead?
[17:52] <xnox> i'm happy to upload that.
[17:52] <xnox> infinity, also what's your opinion on growing three more shared libraries deps for osnmp thing?
[17:52] <infinity> xnox: It's generally more the Debian Way to have services start when installed.  It's the element of least surprise.
[17:53] <xnox> ok.
[17:53] <infinity> xnox: As for the conffile, I'm not fundamentally opposed to it moving, I'd just like to see the movement mirrored upstream.  It's a silly delta to carry forever.
[17:53] <xnox> i think i would want to split the osnmpd into separate package too
[17:53] <xnox> because of the deps, and not eveyone carrying about snmp
[17:54] <xnox> (and for snmp to be worthwhile one needs an extra furtune, to have more than one mainframe....)
[17:54] <infinity> xnox: Yeah, no huge opinion there from me, but not dragging more deps into the base install is nice.
[17:54] <infinity> xnox: Can you name the extra packages "s390-tools-$binary", so they're obviously parts of s390-tools split out (and not pulluting namespace with the super generic names)?
[17:55] <infinity> xnox: And probably add both to s390-tools' Suggests, so they're vaguely discoverable.
[17:56] <xnox> yes and yes
[17:57] <infinity> xnox: Oh, and if that current conffile move is a copy or symlink (sadly, debdiff presents both the same), a debian/rules hack to mv tmp/etc/sysconfig/foo to tmp/etc/foo.conf would be a much less ugly delta until upstream moves it for realz.
[17:57] <xnox> infinity, i did mv in debian/rules
[17:57] <xnox> then went with a patch
[17:57] <xnox> it is identical / rename
[17:57] <infinity> Yeah, I'd go for the rules mv then.
[17:57] <xnox> i might go fancy and use dh-exec to rename it in debian/*.install file =)
[17:57] <infinity> 1 line instead of hundreds. :P
[17:58] <infinity> Or dh-exec, sure.
[17:58] <xnox> ok.
[17:58] <xnox> so i take it you have rejected this upload by now, right?
[17:58] <xnox> =)
[17:58] <infinity> Yeah, I did.
[17:59] <infinity> You didn't respond on IRC in time, so I rejected it to prevent someone else accepting before we talked. :P
[18:01] <infinity> superm1: And fix your symbols too, if you missed that nag. ;)
[18:09] <infinity> teward: OOI, where do your nginx orig tarballs come from?  Are they guaranteed to be the same ones Debian will pick/use?
[18:10] <teward> infinity: upstream directly
[18:10] <infinity> teward: (Having weird deltas due to mismatched tarballs makes future maintenance suck)
[18:10] <teward> Debian grabs the pristine tarballs and uses them as their base
[18:10] <teward> most of their changes are done internal to debian/*
[18:10] <teward> including third party modules
[18:10] <infinity> teward: So, same tarballs as Debian is what I'm hearing?
[18:10] <teward> correct
[18:10] <infinity> Kay, good.
[18:10] <infinity> Thanks.
[18:10] <teward> I personally pull them right from nginx's site
[18:10] <teward> I think Debian grabs them then adds them to alioth/git
[18:11] <infinity> But with pristine-tar, I'd assume, so they reconstruct same as uptream.
[18:11] <teward> right
[18:11] <teward> the biggest hurdle going into Y-series is that Debian is, IIRC, planning on releasing their experimental module support "soon"
[18:11] <teward> as in before FinalFreeze
[18:12] <teward> Xenial FinalFreeze*
[18:12] <teward> rbasak and I discussed, so from here until Xenial release there's not going to be a merge
[18:12]  * infinity nods.
[18:12] <teward> then comes Y-series, which will be the hellish time - many more things to determine - what goes in what pocket, Security review, etc.
[18:12]  * teward shivers
[18:12] <infinity> teward: No merge with Debian (cherrypicks for bugfixes, though, please) is fine, but having the same tarball still makes it much simpler to check what the delta is.
[18:12] <teward> infinity: indeed.
[18:13] <teward> though, consider Debian's, what, at least 3 revisions behind now
[18:13] <teward> so a merge will need some finesse to make sure it works right
[18:13] <teward> last I saw, Debian's on 1.9.10
[18:13] <teward> and 'cause they never moved i've been doing direct-upload
[18:13] <teward> (Debian's aware we're gunning for 1.10.0)
[18:14] <teward> s/gunning/going/
[18:14] <teward> i hate IRC over phone >.>
[18:14] <infinity> gunning works in that context too....
[18:14] <teward> true, though i didn't type it
[18:15] <infinity> I would never have known it was a typo if you hadn't mentioned it.
[18:15] <teward> infinity: so far, though, there's not been any real bugfixes in Debian, just some feature changes to what gets HTTP/2, some third party modules that got updated to work around 1.9.11 FTBFS (we nitpicked the fix, the update to an RC version was a "yeah, no" moment)...
[18:15] <teward> i think maybe some core config changes given dynamic modules, but they're not landing in Xenial
[18:15] <teward> (Not Released, yet, in Debian, for the feature changes parts)
[18:16] <teward> infinity: I also track upstream, so when an issue happens here, and upstream has fixes, I nitpick there :)
[18:17] <infinity> superm1: Remind me to un-reject gnome-software after your new fwupd is a thing.
[18:18] <infinity> slangasek: Running out of things in the queue to use as a delay tactic.  Looks like squid3's up.  Can I trade you appstream-glib as penance?
[18:19] <teward> infinity: also, for the record, perfect example of this happened in 1.9.10 - https://launchpad.net/ubuntu/+source/nginx/1.9.10-0ubuntu1 was direct-uploaded ahead of a Debian merge for the CVE, to make sure it lands in Xenial; https://launchpad.net/ubuntu/+source/nginx/1.9.10-1ubuntu1 uploaded the next day with the Debian merge
[18:19] <teward> with no merge/tarball oddities, that almost reinforces the tarballs are both pristine
[18:19] <infinity> ogra_: [ -d /etc/cloud/cloud.cfg.d ] || mkdir -p /etc/cloud/cloud.cfg.d
[18:20] <infinity> ogra_: That test is pointless, mkdir -p is idempotent.
[18:20] <infinity> ogra_: (Not worth a reject, just pointing it out so you can make a mental note for future shell abuse)
[18:28] <infinity> slangasek: Sweet mother of holy changelogs.  I guess I can't fault you for your documentation.
[18:30] <infinity> slangasek: Why the choice to mv squid3 squid instead of moving the contents?  Concern that if it's a mountpoint you'll ENOSPC their root partition?
[18:30] <slangasek> infinity: that, plus not having to deal with dotfiles
[18:31] <mgz> slangasek: can I bug you about the suggestion to not do update-alternatives and just make a juju-1.25 binary
[18:31] <slangasek> infinity: and yeah, I'll look at appstream-glib
[18:31] <slangasek> mgz: sure
[18:32] <mgz> slangasek: the reason that I didn't do that is the way juju plugins work is they select sibiling or path binaries named juju-$PLUGIN
[18:33] <mgz> so, if we just have a juju-1.25, that breaks all juju 1.X plugins, because it will find and try to use the juju 2 plugins
[18:33] <slangasek> mgz: where do these plugins come from?
[18:33] <infinity> slangasek: The dotfile argument could surely be sorted with "for i in `ls -A1`", but the mountpoint argument is probably still valid.
[18:33] <mgz> whereas when you run `/usr/lib/juju-1.25/juju` it works, and is also unambiguous
[18:33] <mgz> slangasek: they're built from the same source
[18:34] <slangasek> mgz: /usr/bin/juju-1.25 doesn't have to be a binary, just an executable; it could be a wrapper that just calls 'exec /usr/lib/juju-1.25/juju "$@"'?
[18:34] <mgz> but the logic for doing that stuff is in go, not in the packaging
[18:34] <mgz> let me see
[18:38] <infinity> slangasek: We don't install anything by default that shows NEWS.Debian, I'm wondering if a debconf note at migration failure (before the daemon is restarted) prompting the admin to shell out, fix the situation, and continue, might not be the worst idea.
[18:38] <mgz> slangasek: plugins only work when they're on the path, and named 'juju-$NAME'
[18:39] <slangasek> infinity: I've already burned way more time on this package than it deserves; that seems like a further enhancement above and beyond, rather than a bug I've introduced with my changes?
[18:40] <superm1> infinity: ^ with the symbols fix and FFe documentation
[18:40] <infinity> slangasek: Oh, sure, it's not a bug in your bits, which are clearly an improvement over not attempting the migration at all. :P
[18:40] <infinity> superm1: Ta.
[18:40] <slangasek> mgz: isn't that a problem with the update-alternatives approach too?
[18:40] <slangasek> mgz: or, should your /usr/bin/juju-1.25 wrapper just prepend /usr/lib/juju-1.25 to the path (also trivial)?
[18:42] <mgz> slangasek: that's an idea. it's not a problem with update-alternatives when we do switching, because the plugins get symlinked into /usr/bin
[18:43] <slangasek> mgz: ok. but then that means the update-alternatives approach really doesn't support the user running the non-default alternative at all, despite it being installed
[18:43] <slangasek> I think a wrapper script makes more sense there
[18:43] <infinity> Indeed, the wrapper with a PATH modification seems much cleaner.
[18:43] <mgz> slangasek: `PATH=/usr/lib/juju-1.25/bin:$PATH juju "$@"` works
[18:44]  * slangasek nods
[18:44] <infinity> export PATH=...\nexec juju "$@" gets a prettier ps output (and lack of useless long-running shell)
[18:45] <slangasek> +#define AS_TEST_WILDCARD_MD5   "\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?\?"
[18:45] <slangasek> hahahahaha
[18:45] <infinity> Wat.
[18:46] <infinity> slangasek: "It's an MD5 if it's a string of the right length" is the test here?
[18:46] <slangasek> infinity: this complements AS_TEST_WILDCARD_SHA1 on the preceding line
[18:46] <slangasek> infinity: yes!
[18:46] <infinity> Oh dear.  Same thing for SHA1?
[18:46] <infinity> But, well, longer?
[18:46] <slangasek> yes! :)
[18:46] <infinity> Brilliant.
[18:47] <mgz> slangasek, infinity: so, I propose leaving the update-alternatives machinery in place (I want it for a safe way of putting alphas in the next dev release), and adding a /usr/bin/juju1 that's a script wrapper
[18:48] <infinity> mgz: Given the plugins argument, I don't see much use for the update-alteratives at all.  The safe way to do alphas would be to have a similar /usr/bin/juju3 wrapper, and then drop it when the default flips.
[18:48] <infinity> Or /usr/bin/juju-alpha, so it's not ever-changing.
[18:49] <slangasek> mgz: I am unconvinced that update-alternatives is the right tool for any of this.  The only legitimate way to change which alternative is the "default" on a system is by juggling priorities; I don't think you want to have to upload old versions of juju multiple times in a release cycle for this
[18:49] <slangasek> I also don't see that alphas warrant co-installability
[18:50] <mgz> I have had conflicting feedback on putting alphas into the distro
[18:50] <slangasek> in a dev release, standard procedure is that you upload to the archive the package that's on track to be released, and it just owns that name, and you deal with bugs
[18:50] <infinity> YOu could make all versions co-installable if they *all* used a /usr/bin/juju-$ver path wrapper and introduced a juju-defaults that ships the /usr/bin/juju symlink to the right default (Cause, hey, if it's good enough for compilers, why not replicate it everywhere!)
[18:50] <mgz> distro says go do that... everyone else doesn't want it
[18:50] <mgz> I can do the path wrapper thing in replacement
[18:50] <slangasek> who is this "everyone else" that has opinions on what should be in the dev release that AFAIK they aren't using?
[18:51] <slangasek> anyway, from a ux pov, you don't want to have to 'sudo update-alternatives fwibble' every time you switch between coinstalled versions
[18:52] <slangasek> you want to be able to run any of the installed versions of juju as a user without doing that; in which case the alternative is of marginal value but high overhead
[18:52] <mgz> it seemed like a nice way of having people who need to remain on 1.X have all their scripts still work
[18:53] <mgz> but I'm fine with doing what's suggested now
[18:53] <slangasek> sure; but the fact that juju-1.25 /won't/ be the default means the user has to do $something to keep their script working, and that something might as well be editing the script (or adding /usr/lib/juju-1.25 to their system path?) rather than managing an alternative
[18:54] <infinity> slangasek: The plan was for juju-1 to be the default, actually, to avoid breaking upgrades.
[18:54] <infinity> (But maybe that plan changed again)
[18:54] <slangasek> infinity: that plan was nacked by sabdfl
[18:54] <infinity> Ah.
[18:54] <slangasek> and I signed off on this
[18:54] <infinity> Yeah, then alternatives are pointless in this context.
[18:54] <slangasek> things don't always work without interruption on LTS upgrade
[18:54]  * slangasek nods
[18:55] <mgz> okay, so I'll switch to wrapping scripts named juju-$VERSION that add /usr/lib/juju-$VERSION/bin to the path
[18:55] <slangasek> by which I mean: the distro should work without interruption on LTS upgrade, but things external to our packages that make assumptions are not guaranteed to work without modification
[18:55] <slangasek> mgz: +1, thanks
[18:55] <infinity> There's no real difference between saying "you must run update-alternatives" or "you must sed s/juju/juju-1.25/ in all your scripts", except that the latter is a much saner explicit choice that works everywhere and isn't dependent on some obscure system config.
[18:55] <mgz> thanks for the explanations guys
[18:56] <infinity> And, indeed, if the version wrappers persist forever, people can keep that explicit choice motif going forward and be less surprised on the next upgrade.
[18:57] <infinity> (ie: they can move to 2, and then when 3 happens, their 2 scripts won't be broken and they can test and move)
[19:02] <mgz> I have some fiddly bits with man pages and bash completion to work out, but am just removing scripts for now
[19:18] <mgz> slangasek: can the FFE bug be accepted as it stands? I'm doing the changes for name-version linking, were there other concerns to address?
[19:27] <infinity> doko: Why does --with-milestone differ between EFAULT_CONFIGURE_ARGS and COMMON_CONFIGURE_ARGS?
[19:27] <infinity> s/EFAULT/DEFAULT/
[19:27] <slangasek> mgz: the packages to be accepted will need to meet the outlined conditions; are you asking for the bug to be marked 'Confirmed'?
[19:28] <infinity> doko: re: openjdk-8, if that wasn't clear.
[19:32] <slangasek> infinity: ok so I've reviewed appstream-glib and this looks to me like a featureful upload with no FFe bug, no upstream changelog, and no assurance of upstream QA (git snapshot); unless you had some other context, this looks like a nack to me
[19:32] <mgz> slangasek: do you/release team need to review the debian/rules once I've uploaded to unblock this process? or are we good to propose with these changes?
[19:32] <infinity> slangasek: I had zero context outside the diff being something I didn't want to read.  All you.
[19:33] <slangasek> mgz: there will be a post-upload review
[19:33] <mgz> slangasek: so, do I have the sign-off to upload? that's not reflected in the bug at present.
[19:33] <slangasek> mgz: you unblock the process by getting something uploaded
[19:34] <infinity> slangasek: "rm -f || true"?  You don't trust the effiness of -f?
[19:34] <slangasek> infinity: hum.  Did I write that? or did I copy it from somewhere
[19:35] <slangasek> (what did I rm -f and why?)
[19:35] <infinity> slangasek: I dunno.  If you copied it, it's not from anywhere in context. :P
[19:35] <slangasek> infinity: ah, I copied it from dh_apparmor's maintscript snippet :-)
[19:40] <infinity> slangasek: Oh, also, that squid3->Pre-Dep: squid, squid->Conflicts: squid3 combo kinda buggers the world a tiny bit.  That Conflict should surely be a Breaks.
[19:41] <slangasek> infinity: it was like that when I got there.  I at one point iterated and dropped it to Breaks, then reverted because of the horror of dpkg-maintscript-helper being called in both packages. Let me think
[19:41] <infinity> The conflict forces a total removal before we even start, which messes up any attempts to stop the old daemon, and also busts your mv_conffile attempts, if we're doing the upgrade with --purge.
[19:42] <slangasek> the old daemon is stopped by the old package's prerm
[19:42] <slangasek> ... who does an upgrade with --purge?
[19:42] <infinity> I do. :P
[19:42] <infinity> Pretty much always.
[19:43] <slangasek> right, well
[19:43] <slangasek> yes, I think the Conflicts can and should be dropped to Breaks now that the maintscripts are confined to a single package
[19:43] <slangasek> but I'll need to re-test that
[19:45] <infinity> slangasek: The rest looks vaguely reasonable in that "I'd really have to build it and test to be sure" sort of way.
[19:47] <infinity> tjaalton: Where's the FFe for this major version bump to wayland?
[19:47]  * infinity said, while clicking reject.
[19:49]  * mdeslaur chuckles at commentary
[19:55] <slangasek> infinity: ok, so I'll downgrade Conflicts to Breaks, retest the upgrades, and reupload.  Do you want the current one accepted or rejected in the meantime?  Note that while I versioned the Conflicts in this upload, it's there in the one currently in -proposed already
[19:56] <infinity> slangasek: Yeah, I'd rather we just leave this in the queue while we test.  Then we can accept whichever turns out to be more correct.
[19:57] <slangasek> infinity: but block the server team from doing any more Real Testing in the meantime.  My turnaround on this is probably going to be about 2 hours
[19:57] <infinity> slangasek: And +1 from me on this, other than that one sticking point, so if you either come to the conclusion that the Conflict is necessary or reupload with Breaks and that's the only diff, feel free to self-accept.
[19:57] <infinity> slangasek: To be fair, it's EOD for most people by now anyway.
[19:57] <infinity> (or close to it)
[19:57] <infinity> EOW, even.
[19:58] <infinity> slangasek: But I suppose you're right that it does no harm to upload twice.  I can accept this one, and you can self-accept the 1-liner if it's gooder.
[19:59]  * infinity won't be testing upgrades on his production kit until the second upload happens. :P
[20:14] <infinity> superm1: You appear to have an endian bug in fwupd which, based on the build logs, might actually be a singed-comparison bug that is exacerbated by your ints being backwards.  :P
[20:15] <superm1> infinity: sigh, and it looks like it's only encountered from actually running the test suite on all the other archs now :)
[20:16] <infinity> superm1: Well, good.  That's what testsuites are for.
[20:16] <tjaalton> it's a build dep for mesa & xserver, only reaaon why it's in main
[20:16] <tjaalton> iirc
[20:16] <infinity> tjaalton: And gtk, and a few others.  But it still has the ability to destabilise the world.
[20:16] <infinity> (it's a runtime dep too, obviously)
[20:17] <superm1> infinity: can you let it through proposed for now and this can be investigated more closely at a lower priority?  the more interesting part today really is x86
[20:17] <infinity> superm1: No.
[20:18] <infinity> superm1: It's regressed on two arches.
[20:18] <superm1> okay.
[20:18] <infinity> superm1: If what you're saying is "this was always broken on BE, apparently", you can reupload with the tests disabled on BE, so it can build everywhere, and thus things can link to it.
[20:19] <infinity> superm1: But I'd want a pretty firm commitment to actually fix the bug.  Since endian and singed-compare bugs are often lurking evil on other arches too that your testsuite just happens not to notice (or that other code could perturb into a bug)
[20:21] <superm1> infinity: yeah i'll need to get some BE emulation set up to investigate further, but yes likely this was broken everywhere BE most likely all along
[20:21] <infinity> superm1: Without looking at the code, I'm betting it's a signed-char versus unsigned-int comparison, where you just happen to not be comparing the top bit, so it works by accident on some arches, but explodes on big-endian because the ints also happen to be flippity whee.
[20:23] <infinity> superm1: Based on that, and a build log, you might be able to fix it blind (happy to test).  But I can hook you up with BE hardware if blind is a no-go.
[20:28] <infinity> superm1: Oh, or actually, it's the length mismatch that's probably the endian bug.  I missed that one.
[20:28] <infinity> superm1: (You'd end up comparing the wrong half of your long)
[20:28] <infinity> superm1: But you should fix the singed-compare bug too. :P
[20:28] <infinity> superm1: Anyhow, both are staring at you angrily in the build log.
[20:34] <infinity> superm1: FWIW, both those compiler warnings were there in the previous version, so I'd be okay with an upload to disable the testsuite on big-endian and a commitment to fix and reenable "soon".
[20:37] <superm1> infinity: OK well i'll take a stab at a fix and make the test suite failing non-critical on those archs in case it's not adequate
[20:37] <infinity> superm1: ifeq($(shell dpkg-architecture -qDEB_HOST_ARCH_ENDIAN),big) for the workaround
[20:39] <superm1> infinity: can i have my PPA turned on for one of those archs?
[20:39] <infinity> Sadly not yet. :(
[20:39] <superm1> that way i don't need to waste more of your time trying to fix it
[20:39] <superm1> oh
[20:39] <superm1> okay
[20:39] <infinity> We're almost there for powerpc.
[20:41]  * infinity notes that he failed to lunch again, and goes to find a snack.
[21:39] <slangasek> infinity: yeah, I'm good with the Breaks/Replaces behavior; uploaded
[21:43] <infinity> slangasek: Ta.
[21:47] <infinity> Okay, now lunch for realz.  I mean it.
[21:47] <infinity> Back later.
[21:48] <superm1> infinity: it looked like an easy rabbit hole, but alas it's deeper than it appears , test suite off for now on those archs but i'll work with upstream to get this fixed
[21:49] <slangasek> infinity: "failure to lunch", a common problem for the younger generation
[22:01] <superm1> blah, s390x is failing harder than powerpc was
[22:04] <superm1> xnox: although the s390x failure was with launching valgrind, is that itself working on s390x?
[22:05] <superm1> i see the build used 1:3.11.0-1ubuntu2, but 1:3.11.0-1ubuntu3 was just uploaded to proposed.  probably should retry with that
[22:08] <slangasek> superm1: "illegal instruction"?
[22:09] <slangasek> (cf https://launchpadlibrarian.net/249873837/buildlog_ubuntu-xenial-s390x.colorhug-client_0.2.8-1_BUILDING.txt.gz which I knew was another package using valgrind at build-time)
[22:10] <superm1> looks pretty similar  failure
[22:12] <superm1> looks like trying with new valgrind did resolve it
[22:12] <slangasek> and it looks like -1ubuntu3 is a fix specifically for s390x issues, so \o/
[22:13] <slangasek> superm1: ah, you did a rebuild and already picked up -1ubuntu3? I was waiting for it to show up in rmadison before retriggering things
[22:13] <superm1> yeah
[22:13] <slangasek> spiff
[22:13] <superm1> talk about convenient timing
[22:14] <slangasek> clearly dannf was sent back in time from the future to fix all our s390x bugs
[22:16] <dannf> but not in a nude terminatory way, i promise
[22:20] <slangasek> "come with me if you want to virtualize"
[23:06] <flocculant> cyphermox: you might like to know that I have now got an upgraded xubuntu 16.04 from 14.04.4
[23:06] <flocculant> I know I did ;)
[23:12] <flocculant> restart appeared to not - but in the context I still think it's a win :)
[23:20] <infinity> flocculant: Restart should work, so still some bugs to squish, but yay progress.
[23:21] <flocculant> yea - I realise it *should* but given I was wiki warning last week - definitely progress :)
[23:22] <flocculant> infinity: also, your throw away comment last week re flavours and release notes - made me stop and think a bit - so if I save time next cycle- thanks :D
[23:39] <superm1> infinity: I recall you told me to remind you to unreject gnome software earlier
[23:40] <infinity> superm1: Yup, already have the tab open.  Was just waiting for those binaries to publish in the release pocket, for reasons unexplained.
[23:40] <superm1> Kk


[02:06] <sommer> mdke: just to double check... is the archive open?
[02:10] <nhandler> sommer: Based on his email, it looks like it is safe to push to the bzr branches now
[02:10] <nhandler> Be sure to use the new locations when you push
[02:15] <sommer> bonus :-)
[07:41] <mdke> sommer: what nhandler said, although the ubuntu-doc branches will be renamed to ubuntu-docs in the future (I can't do that myself, and need a LP admin)
[19:07] <binarymutant> How can I create an anchor on a page in the Ubuntu wiki?
[19:07] <binarymutant> is the anchor just a heading? syntax ie: [19:31] <binarymutant> nevermind the above question


[01:12] <gorgut> lo folks. I'm trying to adjust some X settings via an SSH session. can someone tell me the correct syntax to declare a display (or maybe i need a screen declaration?) in the following command line: 'xrandr --output LVDS --off"
[01:13] <gorgut> I assume it's something similar to "xrandr -d 0 --output LVDS --off" but I can't seem to get it nailed down
[01:25] <TheSheep> gorgut: just export DISPLAY=:0
[01:26] <gorgut> TheSheep, then what is the correct syntax for the command line?
[01:28] <gorgut> TheSheep, also, should I run "export DISPLAY=:0" locally on the machine I'm adjusting, or through my remote session?
[01:32] <TheSheep> gorgut: you should run it in the same environment that the xrandr command
[01:37] <gorgut> TheSheep, sweet. Thanks, man
[02:27] <Raggs> hi all
[02:49] <focus> hows it going everyone, I was wondering what the difference between ubuntu and xubuntu as far as configuration, should I clean install xubuntu, or can install it from apt?
[02:53] <Raggs> focus as i understand it you can apt-get it
[02:54] <focus> awesome, thanks.
[02:54] <Raggs> apt-get install xubuntu-desktop i believe
[02:55] <knome> Raggs is right.
[02:55] <knome> !info xubuntu-desktop
[02:55] <Raggs> knome, it happens
[02:56] <knome> it will install all the necessary packages
[02:56] <knome> ;)
[02:56] <focus> cool, thanks.
[02:56] <knome> focus, if you want to erase all gnome packages at some point...
[02:56] <knome> !purexfce
[03:00] <Raggs> knome how long have you been running xubuntu?
[03:01] <knome> exactly two years the day after tomorrow.
[03:01] <Raggs> sweet
[03:01] <knome> but been running ubuntu for ages and xfce under it also earlier than 2 years ago
[03:01] <Raggs> you are an old hand then
[03:02] <sirtoast> Hi folks, this the appropriate channel for some xubuntu assistance?
[03:02] <knome> sirtoast, absolutely the best irc channel in the world.
[03:02] <knome> Raggs, quite ;)
[03:02] <sirtoast> awesome, bear with me, i haven't used ircII since approx 1993
[03:02] <knome> no problem
[03:03] <sirtoast> I just did a system update on my xubuntu install, and when I log onto the Xfce desktop, i'm just getting a light blue background, it's not loading the desktop
[03:03] <knome> right...
[03:04] <knome> try moving ~/.cache to ~/.cache_backup
[03:06] <sirtoast> testing now
[03:06] <sirtoast> this truly is the best irc channel in the world:)
[03:06] <Raggs> sirtoast, one of ;)
[03:07] <knome> in the best three ;)
[03:07] <Raggs> yes i am
[03:07] <sirtoast> is there something I missed in the system upgrade that caused this, or is it just one of those things that I should keep in mind when upgrading the system files?
[03:08] <knome> it's something that can happen when upgrading - or even without an upgrade sometimes.
[03:08] <knome> did it work?
[03:08] <sirtoast> it sure did
[03:08] <knome> okay. good to hear.
[03:14] <sirtoast> thanks again for the help knome!  I'll keep pimping xubuntu at work
[03:14] <knome> right :)
[03:14] <knome> sounds good
[03:14] <sirtoast> may pop back in for more social stuff rather than just pop in for free support:)
[03:15] <Raggs> knome, of the buntus X is my favorite
[03:16] <knome> Raggs, that's good to hear as well :)
[03:16] <knome> we have done quite a work to set it up
[03:17] <knome> (a secret: karmic will be even better)
[03:19] <Raggs> i am not using Xubuntu atm
[03:20] <knome> what really matters is that people are using a non-propietary os ;)
[03:21] <Raggs> Debian here
[03:21] <knome> debian is a really good distribution for servers
[03:21] <Raggs> its a really good desktop as well
[03:22] <knome> never used it as a desktop since... 2000 i think
[03:22] <knome> eh, i think that was red hat and not debian
[03:22] <Raggs> its a little better now
[03:22] <knome> well, anyway ;)
[03:22] <knome> the desktops sucked back then anyway
[03:22] <Raggs> i run testing anyhow
[03:25] <knome> testing is not bad either.
[03:26] <Raggs> i like it
[03:27] <knome> i don't mind risking some operability of my production machine, but karmic alpha is a bit too experimental :)
[03:28] <Raggs> well i hope it goes well
[03:28] <knome> it will go well, but it's still a long time to release
[03:30] <Raggs> i should go to bed, but i am not yet
[03:31] <Raggs> have to get up early
[03:31] <knome> hah, if i'd had to get up early, i would be in problems. it's already 5:30 am. ;)
[03:33] <Raggs> lol, 10:33 PM here
[06:19] <tuv0k> Is there a xubuntu pulseaudio guide. Fresh install on a 754 chipset with onboard sound. I have no sound.
[06:50] <knome> tuv0k, try uninstalling pulseaudio? ;>
[09:18] <immo> REGISTER <pustefix13><EMAIL_ADDRESS>[09:18] <SiDi> hm :)
[09:19] <SiDi>  /msg chanserv register pustefix13 (or another password now :p<EMAIL_ADDRESS>[09:19] <immo> wrong?
[09:19] <SiDi> i hope for you its not your gmail account password
[09:19] <immo> checking...
[09:23] <immo> its not
[10:38] <premorphos> hey is there somebody pro on bluetooth solutions online?
[10:38] <marcPV> hi there
[10:40] <marcPV> anyone please, i deleted an user but i dont know how to delete his directories
[10:42] <premorphos> i need a good working solution on how to brows file system on cell phones... ex bacing up contacts, other files and so on...
[10:42] <premorphos> any one have a clue..
[10:43] <premorphos> have tried gammu wammu and xgnokii and they arent working
[10:44] <premorphos> marcPV: have you tried as Root
[10:45] <marcPV> sorry im little rookie here, tell me how pls
[10:50] <premorphos> open terminal... go to the location of the subfolder and type sudo and give the delete comand and enter and root passwrd
[10:51] <marcPV> thanks, let me try
[10:53] <marcPV> sorry, whats the delete command for a folder?
[10:54] <premorphos> rm -r  but be cereful
[10:55] <premorphos> ex rm -r foldername
[10:56] <marcPV> "sudo rm r yag-kosha" is ok? i want to delete a folder inside "home" from an user that i deleted
[10:56] <premorphos> no: sudo rm -r yag-kosha
[10:57] <premorphos> but you need to move to home
[10:57] <premorphos> home is not same as root
[10:58] <SiDi> marcPV: sudo rm -rf /home/username (be careful this will delete everything forever)
[10:59] <marcPV> ok, i go to folder home, open terminal there (/home) and type that?
[10:59] <SiDi> premorphos: for your bluetooth problem
[10:59] <marcPV> rm f or rm -rf?
[10:59] <SiDi> marcPV: you can type it from anywhere
[10:59] <SiDi> rm -rf
[10:59] <marcPV> ok, thanks, let me try
[11:00] <SiDi> which stands for "remove recursively and force deletion"
[11:01] <marcPV> (hey, it works, thanks SiDi and premorphos for the support)
[11:01] <premorphos> no prob... "my first help case".... im so proud...
[11:01] <premorphos> im all ears sidi
[11:02] <SiDi> premorphos: i dont know in xfce but with gnome-bluez i used to can mount my bluetooth phone's folders and then browse them
[11:02] <SiDi> as far as i recall
[11:02] <SiDi> premorphos: at worse you can google translate this page : http://doc.ubuntu-fr.org/bluetooth
[11:02] <SiDi> it explains some methods for sending and receiving data
[11:02] <SiDi> https://wiki.ubuntu.com/Bluetooth/Docs
[11:03] <SiDi> marcPV: you're welcome
[11:11] <premorphos> il look at it... tnx
[13:26] <pandi2456> hi
[13:27] <gabkdlly> hi
[13:30] <pandi2456> so quite in here :D
[13:30] <pandi2456> ello gab
[13:43] <pandi2456> very confuse what is the basic different between ubuntu and xubuntu beside the layout ?
[13:52] <SiDi> its not exactly the layout. it's a different desktop environment.
[13:52] <SiDi> Ours is lighter and faster, but it has less features
[13:55] <pandi2456> uhmm... features like open office ? or other apps?
[13:56] <SiDi> you can get any ubuntu app in xubuntu
[13:57] <tuv0k> pandi2456, pulseaudio is broken in xubuntu, but that is all
[13:58] <tuv0k> I should have just installed ubuntu from alt cd THEN installed xbuntu-desktop
[14:03] <slow-motion> hi
[14:08] <SiDi> tuv0k: or install xubuntu from xubuntu's alt cd
[14:10] <Ben_Cs> is there offtopic xubuntu chan?
[14:14] <SiDi>  #xubuntu-offtopic
[14:14] <SiDi> but its empty
[14:14] <pandi2456> yeah
[14:21] <Ben_Cs> so i'll ask a short question here
[14:22] <Ben_Cs> do you use simultaneously python and perl? or only one of them. which one?
[14:30] <Ben_Cs> ?
[14:44] <premorphos> what can be wrong if i cant find my blue dongle with lsusb
[14:45] <premorphos> i wuled kill to be able to brows my phones on my system
[14:46] <premorphos> way is this so tricky
[15:03] <pandi2456> where is xubuntu place the temporary files ?
[15:24] <tuv0k> so there is NO xubuntu pulseaudio wiki? or Fix?
[15:25] <charlie-tca> xubuntu does not use pulseaudio by default
[15:25] <tuv0k> hence my question
[15:25] <charlie-tca> no, there is not, since it does not use it
[15:26] <tuv0k> and does not provide an option for those that do. WHY is there even a xubuntu when ubuntu  with xubuntu-desktop is not broken or depreciated?
[15:26] <charlie-tca> It is a Ubuntu component, so you could use any Ubuntu pulseaudio help
[15:27] <charlie-tca> If there was no Xubuntu, there would be no xubuntu-desktop
[15:27] <tuv0k> lol, riiiight
[15:35] <erik__> hi all
[15:35] <erik__> i have a quick question
[15:37] <charlie-tca> !question | erik__
[15:37] <premorphos> ok what is your q?
[15:48] <Kangarooo> Hello from Latvia.. I Found one maybe big problem.. at leas for me.. :) I have Xubuntu and I allways liked save session on shutdown (yes Im shutting down computer) and I also like dropbox but its as I found only available if also installed nautilus but it won't take over.. ok but I some times started nautilus also and now my session is dirty- allways starting with nautilus as desktop manager.. how can I reset session or delete it? Applications -> Sett
[15:49] <cody-somerville> You can delete .cache/session directory from your home directory to reset your session
[15:51] <Kangarooo> whole folder or files in it? /home/kangarooo/.cache/sessions
[15:54] <charlie-tca> whole folder, Kangarooo
[15:54] <Kangarooo> in windows if I would delete folder then programm would ask in witch then save..
[15:54] <Kangarooo> ah ok :)
[15:54] <Kangarooo> thanks :)
[15:54] <charlie-tca> You are welcome
[16:07] <premorphos> if i cant see a usb dongle in lsusb.... is there any way to fix this or shall i go shopping
[16:15] <TheSheep> premorphos: check the cable, also look at dmesg
[16:40] <premorphos> thesheep: tnx 4 your reply
[16:43] <premorphos> sweet there it was... but what is dmesg?...
[16:50] <premorphos> if i se my bluetooth dongle in dmesg... can i mount it so that i see it in my file system every time i pair a device?
[16:58] <TheSheep> premorphos: bluetooth is not a disk
[16:58] <TheSheep> premorphos: you can't see it in your filesystem
[16:59] <TheSheep> premorphos: you see it as a network device
[17:08] <lvr> how do i get transmission, rhytmbox and such icons back to the toolbar in xubuntu? i removed them by accident and don't know how to reverse it
[17:11] <SiDi> do you mean the menu ?
[17:11] <SiDi> or launchers in your panel ?
[17:11] <slow-motion> right click on the bar "add new items" > "starter"
[17:12] <TheSheep> I think he means system tray
[17:12] <SiDi> oh
[17:12] <TheSheep> it's called 'Notification area'
[17:12] <SiDi> you removed the notification area off your panel, lvr ?
[17:13] <lvr> SiDi is that what its called? i guess, then
[17:13] <lvr> okay thanks got it back
[17:16] <SiDi> np
[17:38] <Araneidae> Is there any way I can stop xfce from saving my workspace?
[17:39] <Araneidae> I know I can turn it off ... but it keeps turning itself back on again!  Grrr
[17:39] <SiDi> remove .cache/sessions
[17:39] <Araneidae> In fact: "Automatically save session on logout" isn't set!  Yet it just restored something...
[17:40] <Araneidae> Thanks SiDi
[17:40] <SiDi> it stops saving sessions
[17:40] <SiDi> but it still restores the last saved one
[17:40] <Araneidae> Hmm
[17:40] <SiDi> badly designed feature, imo :p
[17:40] <Araneidae> Where is the saved session saved?
[17:40] <SiDi> its in ~/.cache/sessions normally
[17:41] <Araneidae> Well, duly deleted ... we'll see what happens
[17:41] <Araneidae> I dug a little deeper into my missing RAM
[17:41] <Araneidae> I think I might need to try a PAE kernel!
[17:43] <spaztik1> hey guys, anyone know why the 3 finger salute wouldn't work to restart GDM?
[17:43] <Araneidae> Hasn't that been turned off in recent *buntu updates?
[17:43] <charlie-tca> Turned off in 9.04
[17:43] <Araneidae> Think you need to add Option "DontZap" "false" to xorg.conf
[17:43] <spaztik1> seriously?
[17:43] <Araneidae> afraid so!
[17:44] <Araneidae> Designed to protect the ... uh ... less able
[17:44] <spaztik1> bah, so i guess i should find a thread that is already bitching about this
[17:44] <spaztik1> well, how would one re-enable it
[17:44] <spaztik1> i'm assuming in the /etc/X11 files somewhere
[17:44] <Araneidae> Just add the line 'Option "DontZap" "false"' to Section "ServerFlags"
[17:44] <sml12261> Can I run a 64 bit VM in a 32 bit OS? I do have a 64 bit CPU
[17:45] <Araneidae> Can't imagine why not.
[17:45] <charlie-tca> sml12261: don't believe it will work
[17:45] <charlie-tca> It depends on the actual kernel you are using. If you installed a 32 bit kernel, it won't run 64bit kernel
[17:46] <spaztik1> sml12261, not sure, but one would presume if the vm cpu was 64 bit it might emu the arch? not sure if that falls back on the host cpu or not
[17:46] <spaztik1> Araneidae, is that to me? the DontZap?
[17:46] <Araneidae> Sure
[17:46] <Araneidae> The DontZap refers to C-A-Backspace
[17:46] <spaztik1> lol that's a funny config param
[17:47] <Araneidae> sure, it's pretty odd.
[17:47] <charlie-tca> spaztik1: see the release notes here: http://www.ubuntu.com/getubuntu/releasenotes/904#Ctrl-Alt-Backspace%20disabled%20by%20default%20in%20Xorg
[17:47] <Araneidae> It's in xorg.conf(5)
[17:47] <sml12261> I was planning on putting Virtual box on my 64bit Ubuntu and my 32 bit Vista so wanted to be able to move between the two. Think it would work?
[17:48] <spaztik1> so it's not an ubuntu thing, but rather an xorg preference?
[17:48] <spaztik1> or did the ubuntu guys change some xorg things?
[17:48] <Araneidae> Suspect it might be an Ubuntu build preference, don't know though
[17:49] <spaztik1> well actually it makes sense that it's been in xorg for a while actually... i guess most distros just have it compiled with it enabled
[17:55] <sml12261> Why can't I get my normal nick?? It's annoying
[17:56] <charlie-tca> did you register it?
[17:56] <sml12261> Nope
[17:57] <charlie-tca> That is probably why then. Anyone else can use it
[17:57] <sml12261> nobody else is using it though so unless somebody registered it I don't get it
[17:58] <charlie-tca> If someone else registered it, it is no longer available to you
[17:58] <sml12261> Well I doubt its registeredbecause this has happened before and the next time I get on I have my old one back
[17:59] <sml12261> Need to try to register to be sure
[18:10] <sml12261> I looked and found my regular nick and it says its me??? I'm only on 1 pc so not sure why this is happening.
[18:11] <firecrotch> How can I stop xfwm4 without it restarting itself?  I need to do this as a regular user, without using sudo.  If I just kill xfwm4 it restarts itself
[18:12] <sml12261> Why do you need to do that?
[18:13] <TheSheep> firecrotch: you can start a different window manager with --replace option
[18:13] <firecrotch> TheSheep: I need there to be no window manager
[18:13] <TheSheep> that's precisely what xubuntu avoids
[18:14] <TheSheep> you can probably uninstall xfwm4
[18:14] <sml12261> Go to services (i think thats where it is) xfwm4 is in there I think. Tell it to end it and that may work. Not in Xubuntu now so forget exactly how
[18:17] <firecrotch> Thanks guys for pointing me in the right direction - I found a setting that allows me to tell it to not restart when it's killed
[18:17] <sml12261> Where I can't remember if what Isaid was even close to right
[18:17] <sml12261> ?
[18:20] <firecrotch> Applications -> Settings -> Sessions and Startup -> Session tab
[18:21] <sml12261> That is what I was thinking of just not remembering what it was. Thanks for letting me know.
[18:32] <forces> saluton
[19:07] <spaztik1> firecrotch, you need to have a different startup script
[19:07] <spaztik1> like in your .xinitrc you can just start whatever you want
[20:55] <davebot> Hello
[20:56] <davebot> Can anyone help me? I am having an issue with my GUI.
[20:57] <davebot> Basically, my tool bars that are normally at the top and bottom of my screen have disappeared and I was wondering how I could get them back.
[20:58] <TheSheep> davebot: press alt+f2 and type 'xfce4-panel'
[20:58] <davebot> ah, thanks
[21:45] <gsa1> Hi
[21:46] <gsa1> A little question, after some reboot I lost the automatic starting of panels and so, each time I reboot I need to execute Alt+2 and xfce4-panel
[21:46] <gsa1> This is a know problem? Have some solution?
[21:52] <TheSheep> gsa1: press alt+f2 and type 'xfce4-panel'
[21:54] <SiDi> gsa1, what GPU do you have ?
[21:54] <SiDi> did the reboot include the latest kernel upgrade ? Do you know if you have proprietary drivers for this kernel ,
[21:54] <SiDi> Also, you can just add "xfce4-panel" in a file named .initrc, that'll do for now
[22:33] <TheSheep> SiDi: I think it stays when you run it
[22:34] <SiDi> not with a bug linked to mesa drivers
[22:34] <SiDi> which breaks xfce4-session's launch
[22:38] <TheSheep> uh


[05:38] <Dinan> Hi, this is my first time here :). Any suggestion on good instructor led Linux beginner training courses that's Ubuntu focused?


[02:42] <pleia2> akgraner: not getting review done tonight, I need some rest
[10:47] <akgraner> pleia2, working on the the last parts of UWN now...I'll ping when I am finished
[10:52] <nlsthzn> ... ah man... wish I knew how to help with the post production side... have been slacking of the whole day while you guys are gearing up for UDS :/
[11:12] <akgraner> nlsthzn, no worries - we'll  figure out how you can learn this part :-)
[11:12] <nlsthzn> akgraner, :-) when the time comes then... enjoy UDS btw!
[11:12] <akgraner> pleia2 - I'm done tweaking if you or someone could do a once through for me  - I'll publish :-)
[11:13] <akgraner> nlsthzn, thanks!  Hope to see you in some seasons via remote participation :-)  (which reminds me I need to add that to UWN) - sigh - I just thought I was done :-)
[11:14] <nlsthzn> For sure... I am going to try and catch the keynote video (if streamed) and will catch some sessions as work allows :)
[11:20] <akgraner> should be :-)  well I gotta run will add the "In this Issue" shortly... Thanks everyone!
[11:20] <nlsthzn> So it is just past 7 in the morning... monday morning and still the news team is hard @ work to get the newsletter out... +1 to awesomeness
[18:42] <akgraner> The new edition of the Ubuntu Weekly Newsletter is now available here:
[18:42] <akgraner> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue239
[18:42] <akgraner> Thanks y'all :-) and now we start another week :-)  woot woot! \o/
[18:44] <pleia2> yay, thanks akgraner!
[18:45] <akgraner> pleia2,  you're welcome setting up the new template now  :-)
[18:49] <akgraner> pleia2,  how does "Community Acknowledgements and Success Stories" sound for the "Thank You" section?
[18:49] <akgraner> this way it's not just about "Thank You's"
[18:49] <pleia2> akgraner: perfect :)
[18:50] <akgraner> and I'll add it after General Community News - so you can go ahead and tell Jono the first BP action items from the session is now complete :-)
[18:50] <akgraner> pleia2, ^^  :-D
[18:50] <pleia2> added it to the template?
[18:51] <pleia2> (I can do it, it's my action item :))
[18:56] <akgraner> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/IssueTemplate
[18:57] <akgraner> pleia2, oops already did it since I was in the wiki - but I can delete it - I added a ## description :-) can you review and see if the description needs changing
[18:57] <pleia2> haha, no problem, thanks :)
[18:57] <akgraner> Thank you!


[01:33] <wrst> Unit193: you causing all the noise. :p
[01:33] <Unit193> wrst: Well, I did make a netsplit
[01:34] <wrst> OK just thought we blamed you for everything
[01:35] <Unit193> I always blame you
[01:35] <wrst> oh yeah
[01:36] <Unit193> I got someone this morning!
[01:37] <wrst> how?
[01:38] <Unit193> I'me halfop on #saver2 (Different network), and the game is to kick ops/halfops before they half/op up
[01:38] <Unit193> A halfop can't kick other ops or halfops
[01:44] <cyberanger> Unit193: so does chanserv allow anyone to halfop then, or how's that bit work
[01:45] <Unit193> cyberanger: Nope, it's like atheme only with levels
[01:45] <Unit193> You get set at that leve
[01:45] <Unit193> l
[01:48] <cyberanger> ah
[01:49] <Unit193> It's fun
[01:58] <Unit193> G = Filters out all Bad words in your messages with <censored>
[02:33] <cyberanger> love filter games
[02:33] <cyberanger> take innocent setences, filter it out to where it sounds like it's just evil
[02:34] <cyberanger> then show somebody the censored version, and the original, watch the shock
[14:45] <wrst> wb... again binarymutant :P
[14:46] <cyberanger> wrst: he has connection issues, yes
[14:47] <wrst> yes cyberanger I'm thinking so :)
[14:47] <wrst> cyberanger: how are you doing today?
[14:47] <cyberanger> better
[14:47] <cyberanger> the car isn't moving
[14:48] <wrst> ha ha
[14:50]  * cyberanger doesn't mind the travel, it's too many drivers for one steering column, too many navigatiors for one route
[14:54] <wrst> ha ha family trip?
[15:33] <cyberanger> yeah, Mom, Dad & the Annoy-a-Tron (aka naginabox, GPS Navigation, other names too)
[15:34] <cyberanger> keeps it intresting
[15:37] <cyberanger> it's not really family though, it's just the added input is more distracting than helpful
[15:38] <cyberanger> it could have been friends, or coworkers, or just me and a naginabox, same frustration (except, I guess all those I can say shutup to without any adverse affects)
[15:48] <cyberanger> wrst: just finished burning all the debian stable cd's
[15:49] <cyberanger> err, dvds
[16:07] <wrst> nice cyberanger, how did you download all that on the road?
[16:07] <wrst> greetings chris4585
[16:11] <cyberanger> wrst: I didn't, some was before the trip, some on the hotel wifi, some when I got back (and all the testing was when I got back, gotta run that through rsync each week)
[16:12] <cyberanger> Chicago isn't too far from the Argonne National Labortory (in a literal & networking sense) plus closer (in a networking sense) to RIT and other mirrors
[16:13] <cyberanger> and that card really ran there anyhow (claiming 15MBPS, but it was going up and down like crazy, it avg.d out to 9MBPS, over 1.50 here (on a 3 down 1 up connection here)
[16:15] <wrst> cyberanger: i'm super digging all this ssh tunneling can't wait to use it on public wifi
[16:15] <cyberanger> I'd run an iptables command to force it to only use that
[16:16] <wrst> before I venture out may have to get a lesson :)
[16:16] <cyberanger> that's not a problem, however that may have to wait a few hours
[16:16] <cyberanger> I know that can happen today
[16:19] <wrst> oh i mean like in months cyberanger :)
[16:19] <wrst> i'm going no where
[16:51] <cyberanger> wrst: I'm going nowhere at 70MPH
[16:51] <cyberanger> ;-)
[16:51] <chris4585> hey wrst
[16:52] <cyberanger> wb chris4585 been awhile
[16:53] <wrst> chris4585: how you doing
[17:15] <chris4585> I'm alright, if I'm not here its usually because freenode doesn't like me to auto connect, sometimes it'll go and sometimes it wont
[17:16] <wrst> what have you done to freenode chris4585? :)
[17:17] <chris4585> nothing, just doesn't connect sometimes, my other network works fine
[17:21] <cyberanger> bbl, finish packing and heading back to cleveland today
[18:30] <wrst> http://www.omgubuntu.co.uk/2011/10/native-netflix-client-coming-linux-in-12-months/
[18:49] <Unit193> Oh no! wrst reads OMGUbuntu!
[18:50] <wrst> ha ha Unit193 i'm well read :)
[18:51] <Unit193> That's the one I don't like :P
[20:32] <cyberanger> well, that didn't go as planned
[20:37] <binarymutant> wow I completely forgot how addictive video games are :D
[20:39] <cyberanger> binarymutant: how true, how true
[20:41] <binarymutant> ...must resist playing again
[20:41] <binarymutant> I don't get the netflix linux client thing, aren't they using flash?
[20:41]  * cyberanger hands binarymutant a controller >:-)
[20:41] <binarymutant> if not html5?
[20:42] <cyberanger> binarymutant: silverlight with drm
[20:42] <Unit193> Silverlight last I knew]
[20:42] <binarymutant> Ooh
[20:42] <cyberanger> Unit193: yep, with DRM
[20:42] <cyberanger> moonlight won't work due to that
[20:42] <binarymutant> I thought MS even abandoned silverlight
[20:43] <cyberanger> binarymutant: special clients for special devices
[20:43] <cyberanger> and I think they're moving away with microsoft slowly
[20:43] <binarymutant> how could a huge company like that make such a big error :D
[20:44] <cyberanger> binarymutant: netflix or microsoft/
[20:44] <binarymutant> netflix
[20:44] <binarymutant> they should just do html5 and auth the page for paying clients
[20:44] <binarymutant> easy, cross platform, etc
[20:45] <binarymutant> oo big trouble in little china :D
[20:45] <cyberanger> binarymutant: simple, at the time, html5 didn't exist (or too draft, lacked media)
[20:46] <binarymutant> yeah but in order to stay alive, internet companies have to keep up with the times. Look at AOL
[20:46] <cyberanger> also, they walked in knowing flash's pains, needing drm (due to royalities, license holders)
[20:47] <cyberanger> and aware that their market was mail rentals
[20:47] <binarymutant> they shouldn't need drm... wait do you download netflix? I thought it was stream
[20:48] <pleia2> they are even required to drm the streams
[20:48] <binarymutant> that's so weird!
[20:48] <pleia2> (this all comes from the content providers they license content from)
[20:48] <cyberanger> binarymutant: it's not netflix choice
[20:49] <cyberanger> the dvd's are a different market
[20:49] <pleia2> the ChromeOS version of Netflix uses HTML5
[20:49] <cyberanger> crossing over to streaming, bad waters
[20:50] <binarymutant> they should the chrome version for everyone then :D
[20:50] <cyberanger> pleia2: you have a cr48?
[20:50] <pleia2> but there are challenges to keeping it protected, so if you want to use Netflix with ChromeOS you can't run it in Dev mode, essentially meaning you can't poke around and see what's going on
[20:50] <pleia2> cyberanger: yep
[20:50] <cyberanger> lucky
[20:50] <cyberanger> I applied, too late I guess
[20:50] <pleia2> this is why they  don't have a generic chrome plugin yet
[20:51] <binarymutant> idk what dev mode is :(
[20:51] <pleia2> binarymutant: on chromebooks you can switch into developer mode to poke around the filesystem, get extra commands and do development
[20:51] <pleia2> regular mode is very locked down
[20:52] <binarymutant> that's weird too :/
[20:52] <binarymutant> dev mode should be regular mode lol :D
[20:52] <pleia2> not really, it's a consumer-level device that's essentially a web browser
[20:53] <cyberanger> binarymutant: think android phone prior to rooting it
[20:53] <pleia2> you don't want normal people messing around with it, it's very simple and Just Works
[20:53] <binarymutant> but most people wouldn't even if they were given the opportunity I think
[20:53] <cyberanger> binarymutant: the cr48 was targetting those that would
[20:54] <binarymutant> oh well, some companies are weird :P
[20:54] <pleia2> the opportunity isn't needed, best to not give it to them
[20:54] <pleia2> it's not like you're installing software on the thing, upgrades just come with magic when you reboot
[20:54] <cyberanger> pretty much the only cromeos device out there
[20:54] <pleia2> there are several now: amazon.com/chromeos
[20:54] <binarymutant> <-- sticks with debian/ubuntu
[20:55] <pleia2> best buy sells them online too
[20:55] <pleia2> (not in stores, boo)
[20:55] <pleia2> I like the idea, they include an ssh client (yay!) and the battery life is amazing (about 8 hours on the cr-48) but they are too expensive for what they are
[20:56] <binarymutant> expensive and no access? doesn't sound like a good time :P
[20:57] <pleia2> I have plenty of computers that I can tinker with ;)
[21:09] <binarymutant> aren't companies pretty good with streaming and not caching nowadays
[21:10] <binarymutant> it used to to cache in /tmp but now - I have nooo clue where they do it
[21:10]  * binarymutant thinks the netflix problems are the reason piracy will never go away
[21:13] <binarymutant> it's easier to copy than to appease IP hoarding companies :P
[21:14] <cyberanger> binarymutant: flash caches to tmp, deletes it in an instant
[21:15] <cyberanger> it's linked to /proc till it's no longer needed (and one can copy it knowing that)
[21:15] <cyberanger> presume that's the same concern for html5 and moonlight
[21:15] <binarymutant> that's useful info ^^
[21:16]  * binarymutant sticks with debian AND piracy lol
[21:17] <Unit193> He says in the logged channel ;)
[21:18] <binarymutant> rofl, oh noes
[21:19] <cyberanger> It's the end of the world as I know it...
[21:19] <cyberanger> I feel fine
[21:20]  * Unit193 chuckles
[21:20] <binarymutant> I doubt they search google with "ubuntu piracy" as the terms
[21:21] <binarymutant> they = ip police
[21:22] <binarymutant> anywho be back in a few (more urban terror! yay :D)
[21:22] <Unit193> Eh, they do more worse things
[21:22] <binarymutant> Unit193: like...?
[21:23] <binarymutant> I heard they download torrents lol
[21:23] <binarymutant> let me find that article, it was hilarious
[21:23] <Unit193> I've seen examples and read a few things, but I don't remember (Watch cyberanger tell it ;P )
[21:24] <binarymutant> http://boingboing.net/2011/09/22/movie-industry-self-piracy-proves-that-ip-addresses-arent-people-invalidates-copyright-enforcement-schemes.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+boingboing%2FiBag+%28Boing+Boing%29
[21:26] <binarymutant> techdirt.com is a good link too :D brb (this time for real)
[21:39] <cyberanger> Unit193: binarymutant got the best one
[22:05] <vychune> hey guys
[22:06] <vychune> Could you guys critique my website for me?
[22:08] <vychune> as usual nobody home lol
[22:08] <binarymutant> I can :D
[22:08] <binarymutant> :D :D :D
[22:09] <binarymutant> url me
[22:09]  * binarymutant apologizes, lots of energy drinks
[22:09] <Unit193> Link 'em
[22:09] <Unit193> dano
[22:09] <vychune> http://www.chestpaint.com/
[22:09] <binarymutant> uh
[22:10] <vychune> what?
[22:10] <vychune> give me your honest opinion
[22:10] <vychune> don't think of my feeling lol
[22:10] <binarymutant> vychune: do you know how to do gradients in css?
[22:11] <vychune> yes the background uses them
[22:12] <vychune> as well as the three top divs
[22:12] <binarymutant> hng on
[22:13] <vychune> k
[22:13] <binarymutant> http://i54.tinypic.com/10gbj14.jpg  is what it looks like for webkit
[22:14] <vychune> doesnt Chrome use webkit?
[22:14] <binarymutant> yes
[22:14] <vychune> im using that
[22:14] <binarymutant> http://binarymutant.byethost8.com/ I like these types of gradients :D
[22:15] <vychune> your site wont come up :/
[22:16] <binarymutant> :(
[22:16] <vychune> dude on your screenshot zoom out lol
[22:16] <binarymutant> comes up for me.... owell
[22:17] <binarymutant> I can't lol
[22:17] <vychune> oh lol
[22:17] <vychune> check the spelling?
[22:17] <binarymutant> I say your top* divs should be on bottom
[22:17] <binarymutant> and your content in the middle
[22:18] <vychune> hmm
[22:18] <vychune> i like that idea hold on
[22:18] <binarymutant> nav-content-top* divs
[22:21] <vychune> I LIKES THAT
[22:21] <vychune> view the homepages
[22:21] <vychune> view the homepage
[22:21] <binarymutant> I like masthead, donate/cc is blurry, maybe add a little 3d?
[22:22] <binarymutant> and a 2 color scheme, 3 at most. you have 5 colors
[22:23] <binarymutant> my site doesn't come up?
[22:23] <binarymutant> that aint cool
[22:24] <binarymutant> I have 6 color scheme on my site lol
[22:24] <binarymutant> thats bad
[22:24] <binarymutant> 7! :(
[22:27] <vychune> yeah seven color is a little much lol
[22:28] <binarymutant> the rounded corners are so rounded that they hide stuff, like "violation"
[22:29] <vychune> ok
[22:29] <vychune> dang i gtg
[22:29] <vychune> babysitting
[22:29] <vychune> -_-
[22:30] <vychune> THANKS FOR ALL YOUR HELP!!!!!!!!!!!!!!!!!
[22:30] <binarymutant> :(
[22:30] <vychune> o/
[22:30] <vychune> ttyl?
[22:30] <binarymutant> sure :D
[22:30] <vychune> o/
[22:30] <vychune> later
[22:31] <binarymutant> why doesn't my site come up, I pay good money for that ( $0 )
[23:54] <Unit193> I get some nice from my shell :D


[07:15] <cjohnston> Greetings.. We are getting ready to push a new update to the LoCo Team Directory. It would be much apprecieated if the translators could help us with completing the translations prior to our next release. Thanks! https://translations.launchpad.net/loco-directory
[07:36] <dpm> good morning all
[15:24] <dpm> hi translators, the new translations videocast will start in ~40 min, feel free to join!
[15:24] <dpm> http://is.gd/MgV88B
[16:40] <gtriderxc> can't write a word on a chat