[00:12] <meoblast001> hi
[00:12] <meoblast001> i have 4 files that use 4 space indents and i want them to be 2 space indents.. would that be worth it in terms of VC efficiency?
[00:42] <lifeless> meoblast001: do you mean 'will the vc same much space if you use 2 space indents'?
[00:42] <lifeless> meoblast001: or 'how inefficient is the vc at storing a change from 4 space to 2 space indents
[00:42] <meoblast001> i mean, is it worth it to make this consistent on these 4 files and lose the efficiency
[00:43] <meoblast001> the sum of the 2 files is about 400 lines
[00:43] <meoblast001> or, 4 files
[00:43] <lifeless> worth it is up to you :)
[00:43] <lifeless> its c=going to cost about 400 bytes
[00:44] <meoblast001> 400 bytes? try 400 lines
[00:44] <meoblast001> right?
[00:44] <lifeless> 400 bytes, in 2a
[00:44] <meoblast001> 2a?
[00:44] <lifeless> the 2.0 default format
[00:44] <lifeless> if you're not using it yet, thats fine, when you upgrade it will compress it then
[00:44] <meoblast001> oh, so it only actually records changes byte for byte?
[00:44] <lifeless> yes
[00:44] <meoblast001> i use Ubuntu 9.04, which version do i use then?
[00:45] <lifeless> bzr --version
[00:45] <ScottK> 1.13
[00:45] <meoblast001> Bazaar (bzr) 1.13.1
[00:45] <meoblast001> does that mean i have to update now?
[00:45] <meoblast001> if i want to get the new optimization
[00:46] <SamB_XP> yeah ;-P
[00:46] <meoblast001> so if i previously did something like this, it will still remain in it's unoptimized form?
[00:48] <meoblast001> although my previous change was a rewrite of most of the source so it wouldn't really change
[00:48] <meoblast001> this time it's mainly just removal of those spaces
[00:50] <lifeless> when you do upgrade your repository, it will gain the benefits
[00:50] <SamB_XP> meoblast001: well, if/when you convert your repository to 2a, which maybe you'll want to do after you upgrade to 2.x, you'll get the goods
[00:50] <lifeless> there is no rush
[00:50] <meoblast001> ah, how does that work technically?
[00:50] <meoblast001> i sometimes don't believe things that sound too good to be true
[00:50] <lifeless> 'bzr upgrade' converts your data from one disk format to another
[00:51] <lifeless> we typically see repositories drop to 30% of their older size (once our gc kicks in and removes the rollback stuff we store in obsolete packs)
[00:52] <meoblast001> "disk format"?
[00:52] <SamB_XP> bzr supports a dizzying array of disk formats for repositories
[00:52] <ScottK> lifeless: Is there a significant speed difference between the 1.19 format and 2.0?
[00:52] <lifeless> ScottK: huge
[00:52] <lifeless> ScottK: there isn't a 1.19 format though, perhaps you mean 1.9?
[00:53] <ScottK> I mean the one immediately previous.
[00:53] <ScottK> Let me check
[00:53] <lifeless> in repo terms thats 1.9
[00:53] <SamB_XP> lifeless: you didn't up the default in 1.19 ?
[00:53] <lifeless> 1.14 as a label was actually a working tree change
[00:53] <ScottK> 1.14 actually
[00:53] <meoblast001> so how does it convert it from a format of detecting changes by lines to a format of changes by bytes?
[00:53] <lifeless> SamB_XP: we haven't done a 1.19 release :P
[00:54] <ScottK> Right, I mis-remembered.
[00:54] <lifeless> meoblast001: reads ins, writes out :P
[00:54] <lifeless> meoblast001: I'm not really sure what you're asking.
[00:54] <ScottK> lifeless: OK, so from 1.14, how huge?
[00:55] <meoblast001> well, if revisions 1 - 90 were made with 1.x, how would you convert those to 2.x
[00:55] <lifeless> ScottK: depends on what you're doing. Small trees and short histories the difference is swamped by startup time
[00:55] <meoblast001> they aren't the same format of revision logs
[00:55] <lifeless> meoblast001: 'bzr upgrade'
[00:55] <lifeless> ScottK: large trees, 'bzr commit' is something like 1/5 the duration; log -v is even more significantly improved.
[00:56] <meoblast001> so it magically figures out "oh, this whole line didn't need changed, only these 3 bytes needed to be"
[00:56] <ScottK> lifeless: bzr stat on the project I'm thinking of is currently taking 8 seconds with bzr.
[00:56] <lifeless> meoblast001: nothing magic about it, it converts the data
[00:57] <lifeless> ScottK: bzr st is entirely working tree; so its not going to change. However 8 seconds is about 8 times longer than stat on openoffice for me.
[00:57] <ScottK> Not sure if that qualifies as large, medium, or small.
[00:57] <ScottK> Hmmm.
[00:57] <ScottK> Interesting.
[00:57] <lifeless> ScottK: so there's a good chance something is wrong like:
[00:57] <ScottK> Thanks.
[00:57] <lifeless>  - missing C extensions
[00:57] <ScottK> OK.
[00:57] <lifeless>  - uncompiled/stale .pyc files causing just-in-time compilation
[00:57] <ScottK> Could the fact that it was imported from Git matter?
[00:57] <meoblast001> lifeless: but it still does exactly what i said in that quote, except in Python code?
[00:58] <lifeless> meoblast001: not really, it doesn't look at the old /changes/ at all.
[00:58] <ScottK> lifeless: We're operating from Ubuntu packages, so is there more was can do to make it faster?
[00:58] <lifeless> meoblast001: bzr doesn't model things by deltas, rather by the full content.
[00:58] <meoblast001> uh oh
[00:58] <meoblast001> bzr: WARNING: bzrlib version doesn't match the bzr program.
[00:58] <ScottK> Our resident git fanatic is still all over speed.
[00:58] <meoblast001> lifeless: what do you mean by deltas?
[00:58] <lifeless> ScottK: the packages should have the C extensions; I have seen python-* helpers blow up.
[00:59] <lifeless> meoblast001: don't worry about it, we're clearly not connecting :)
[00:59] <ScottK> OK.  Is there any docs on how to check into this?
[00:59] <lifeless> meoblast001: if you're interested in the exact details of the storage delta algorithm, have a look at group_compress in the bzr source for 2.0
[00:59] <meoblast001> but basically old revisions will be updated perfectly up to the new format?
[00:59] <lifeless> meoblast001: yes
[00:59] <meoblast001> ok :)
[00:59] <ScottK> Oops.  Noticed the time.  Need to run.
[00:59] <lifeless> ScottK: strace 'bzr st' on a empty tree
[00:59] <ScottK> OK
[01:00] <lifeless> bzr init; bzr st
[01:00] <ScottK> Thanks
[01:00] <lifeless> that will tell you the system minimum time to st
[01:00] <lifeless> ask a question on LP's answers thing, or on the list
[01:00] <lifeless> or back here, when you aren't running
[01:00] <meoblast001> anyways, i broke my bzr install
[01:00] <meoblast001> bzr: WARNING: bzrlib version doesn't match the bzr program. < that's the warning i get, followed by a crash
[01:01] <lifeless> meoblast001: what did you do?
[01:01] <meoblast001> make (did that on accident)
[01:01] <meoblast001> then i did sudo python setup.py install
[01:02] <lifeless> so, you've probably got two copies of 'bzr' on your path
[01:02] <SamB_XP> meoblast001: did you wait for it to *finish*?
[01:02] <meoblast001> yup
[01:02] <lifeless> and the first one on your path doesn't match the first bzrlib on your PYTHONPATH
[01:03] <meoblast001> PYTHONPATH is an environment variable?
[01:03] <SamB_XP> yeah
[01:03] <lifeless> its like PATH
[01:03] <lifeless> when PYTHONPATH is empty it has a default
[01:03] <meoblast001> i echo'd it, aparently i don't have one
[01:03] <meoblast001> ok
[01:03] <lifeless> you can see the effectice PYTHONPATH by doing
[01:03] <lifeless> python -c 'import sys; print sys.path'
[01:04] <lifeless> meoblast001: you should read the upgrade guide though
[01:06] <meoblast001> lifeless: what should that say?
[01:06] <SamB_XP> meoblast001: if he knew what it should say, he could have told you what to set PYTHONPATH to ;-P
[01:06] <meoblast001> ['', '/usr/lib/python2.6', '/usr/lib/python2.6/plat-linux2', '/usr/lib/python2.6/lib-tk', '/usr/lib/python2.6/lib-old', '/usr/lib/python2.6/lib-dynload', '/usr/lib/python2.6/dist-packages', '/usr/lib/python2.6/dist-packages/Numeric', '/usr/lib/python2.6/dist-packages/PIL', '/usr/lib/python2.6/dist-packages/gst-0.10', '/var/lib/python-support/python2.6', '/usr/lib/python2.6/dist-packages/gtk-2.0', '/var/lib/python-support/p
[01:06] <meoblast001> ython2.6/gtk-2.0', '/usr/local/lib/python2.6/dist-packages']
[01:07] <meoblast001> oops
[01:07] <meoblast001> i expected that to be 1 line
[01:07] <meoblast001> and not so, well, long
[01:07] <meoblast001> everything looks shorter in the terminal
[01:32] <meoblast001> lifeless: i just reinstalled again
[01:35] <zsquareplusc> i have a remote repository with several branches and "bzr branches" lists all of them. can i also pull all of them at once? "pull" does not seem to support that
[01:36] <meoblast001> am i supposed to install bzrlib seperately?
[01:36] <bob2> meoblast001: no
[01:36] <bob2> zsquareplusc: multi-pull plugin, not sure if it is maintained anymore
[01:37] <meoblast001> is the release candidate known to be broken?
[01:37] <bob2> oh, sorry, ignore me
[01:38] <meoblast001> ?
[01:53] <meoblast001> i honestly don't think it's installing bzrlib
[01:54] <lifeless> meoblast001: python -c 'import bzrlib; print bzrlib.__path__'
[01:54] <meoblast001> ['bzrlib']
[01:58] <meoblast001> lifeless: is that supposed to be an absolute directory?
[01:59] <meoblast001> lifeless: should i just install the debs?
[01:59] <meoblast001> although i'll never really get an understanding of what installing this from source is like if i do that
[02:00] <lifeless> meoblast001: that means its in your local directory
[02:00] <lifeless> cd somewhere else
[02:01] <meoblast001> lifeless: ['/usr/lib/python2.6/dist-packages/bzrlib']
[02:02] <lifeless> thats the packaged bzr
[02:03] <lifeless> which is your 1.13 or whatever version
[02:03] <lifeless> you might prefer the PPA rather than installing from source
[02:03] <meoblast001> should i remove the bzr package?
[02:03] <lifeless> anyhow, must go, back later
[02:03] <meoblast001> ok, ttyl
[02:08] <zsquareplusc> bob2: hm ok. its multi-pull contained in bzrtools, when i run it, it just lists *local* file URLs and tells me that these are no branches, even though i specified a remote repo
[02:09] <meoblast001> got it working
[02:13] <zsquareplusc> i wonder from where it takes that local paths, i want to do a fresh download and i'm in an empty directory
[02:22] <meoblast001> oh no
[02:22] <meoblast001> http://codepad.org/MIoiOxGQ
[02:22] <meoblast001> if i would have known upgrading to 2.0 would cause tons of problems, i wouldn't have done it
[02:23] <meoblast001> nvm, i'm an idiot
[02:35] <Colonel-Rosa> morning
[02:35] <meoblast001> good norning
[02:35] <meoblast001> morning*
[02:38] <Colonel-Rosa> does bazaar have a feature where it can work with multiple push locations, eg push production, push staging
[02:38] <meoblast001> you can push to 2 different locations if that's what you mean
[02:39] <Colonel-Rosa> right, but bazaar would only remember 1 at a time?
[02:39] <Colonel-Rosa> So I would have to keep typing in the other location
[02:39] <meoblast001> i'm not sure
[02:40] <Colonel-Rosa> alright, thanks
[03:22] <lifeless> Colonel-Rosa: you can create location bookmarks I believe, with the bookmark plugin
[03:48] <Colonel-Rosa> lifeless, I will check it out
[03:48] <Colonel-Rosa> Can not find any documentation for it though
[09:29] <vila> lifeless: lots of attempts to escape test isolation on OSX failures=84, errors=167 for tiger, failures=73, errors=167 for leopard, probably a single cause having to do with /tmp access rights though
[09:31] <vila> vila: pff, not even, it's the infamous /tmp is really /private/tmp on OSX...
[12:10] <aboSamoor> I am searching any resource to understand bzr split, any idea
[12:29] <dsuch> not exactly bzr-specific question but what have you guys used to be able to tab-complete the commands?
[12:29] <dsuch> I'd like to use something like that in my own Python application.
[12:30] <dsuch> Or is it something specific to Bash?
[12:31] <Kamping_Kaiser> if i understand you correctly, its a bash thing.
[12:31] <Kamping_Kaiser> look in /etc/bash_completion.d/ , you'll probably see a bzr script
[12:35] <dsuch> oh right, thanks Kamping_Kaiser
[12:35] <aboSamoor> is there anything wrong with this check http://paste.ubuntu.com/274091/ ?
[12:41] <dsuch> aboSamoor: sorry, can't help you, you'll need to wait a bit more
[12:43] <aboSamoor> dsuch: I am trying to learn how to use bzr split which I don't know how it can help me to answer my Q https://answers.launchpad.net/bzr/+question/83031
[12:43] <dsuch> aboSamoor: not really
[12:44] <aboSamoor> dsuch: no problem :)
[12:44] <dsuch> you'll just need to wait for someone more knowledgeable to join in
[13:19] <aboSamoor> ok, any idea which is the latest format ? is it 2a ?
[13:30] <dsuch> I think it is.
[14:15] <aboSamoor> does upgrading branch locally upgrade the format on the launchpad repository ?
[14:17] <dsuch> aboSamoor: I don't know but I would've created a test repo in a sandbox to test it out
[14:17] <dsuch> in fact, I'm interested in knowing it too :)
[14:18] <dsuch> aboSamoor: so I would appreciate it if you could tell me if it did
[14:18] <aboSamoor> dsuch: it is giving me errors
[14:18] <aboSamoor> so I will rollback then I will try to make a new branch and push it
[14:19] <dsuch> pastebin it somewhere and perhaps someone will know why it's giving you errors
[14:23] <aboSamoor> the error while trying to push the new format to launchpad
[14:23] <aboSamoor> http://paste.ubuntu.com/274143/
[14:24] <davidstrauss> aboSamoor: Upgrade the remote repo first
[14:25] <davidstrauss> aboSamoor: bzr upgrade --default-rich-root<EMAIL_ADDRESS>[14:25] <aboSamoor> davidstrauss: I am usign 1.18 because 2.0rc1 gave me errors and I am using 2a format
[14:26] <davidstrauss> aboSamoor: You shouldn't be using 2a for production use yet.
[14:27] <aboSamoor> davidstrauss: I asked this question https://answers.launchpad.net/bzr/+question/83031. and the answer was to use split.
[14:27] <aboSamoor> split needs rich root format, so I thought the best to upgrade to the future format so I won't do it again
[14:27] <davidstrauss> aboSamoor: A split branch has a rich root
[14:28] <davidstrauss> aboSamoor: you shouldn't upgrade to unstable formats
[14:28] <aboSamoor> davidstrauss: I see. can you please take a look at the question, so I am sure that I am in the correct path
[14:29] <davidstrauss> aboSamoor: I already said you should be using split.
[14:30] <aboSamoor> davidstrauss: I searched for explanation how split is working and how to use. My first VCS is bzr and I am not sure of the technical terms used
[14:30] <aboSamoor> but I did not find anything other than bzr help split
[14:30] <davidstrauss> aboSamoor: Split takes the current directory in the current branch and converts it into its own branch
[14:31] <aboSamoor> inside the same directory ? should I move outside the directory and push as new branch ?
[14:32] <davidstrauss> aboSamoor: right after running split in a directory, you can stay in that directory and push it as a new branch
[14:32] <fullermd> You should note though that split doesn't rewrite any history, so you're still carrying around the whole thing.
[14:33] <davidstrauss> fullermd: from before the split, yes
[14:35] <aboSamoor> davidstrauss: ok, I will do the following. 1-bzr check , 2-bzr reconcile 3-bze upgrade [not sure now what to use !], 4-bzr split dir1 5- cd dir1 6- bzr push
[14:35] <davidstrauss> aboSamoor: bzr upgrade --default-rich-root
[14:36] <davidstrauss> aboSamoor: Otherwise looks good
[14:36] <davidstrauss> aboSamoor: You can skip the reconcile if check doesn't find anything
[14:36] <aboSamoor> davidstrauss: I forgot to mention to use bzr upgrade --default-rich-root remote-repo before everything
[14:36] <davidstrauss> aboSamoor: Indeed
[14:37] <davidstrauss> aboSamoor: You could also pick --1.14-rich-root if you'd like the latest stable rich-root format.
[14:39] <davidstrauss> aboSamoor: make sense?
[14:40] <aboSamoor> now, I understand the big picture. I applied the default-rich root for the remote repo .  Waiting, it takes long time.
[14:41] <davidstrauss> aboSamoor: Yes, it takes quite a while
[14:43] <aboSamoor> davidstrauss: I reported bug 433039 while trying to use bzr 2.0rc1
[14:44] <davidstrauss> aboSamoor: Don't file those against the Ubuntu package. File them against the bzr project.
[14:47] <aboSamoor> davidstrauss: done, but don't know how to remove the ubuntu package from the "Affects" column
[14:47] <davidstrauss> aboSamoor: They'll have to
[14:47] <aboSamoor> davidstrauss: :-D, making mess all  the time
[14:48] <davidstrauss> aboSamoor: This was probably the bug you ran into: https://bugs.launchpad.net/bzr/+bug/422849
[14:49] <davidstrauss> aboSamoor: And I've marked yours as a duplicate
[14:49] <aboSamoor> davidstrauss: it was hard for me to figure that out, but the fix was released and I still have it !
[14:50] <davidstrauss> aboSamoor: but you were running rc1
[14:50] <aboSamoor> davidstrauss: yeah, it is released in RC2
[14:50] <aboSamoor> davidstrauss:  which I could not grab because of the build errors
[14:52] <aboSamoor> davidstrauss: by the way, this upgrade process is not friendly, no sign what is going on ! still blinking cursor :(
[14:52] <davidstrauss> aboSamoor: there should be a progress bar
[14:53] <aboSamoor> davidstrauss: http://paste.ubuntu.com/274159/
[14:54] <davidstrauss> aboSamoor: It doesn't give progress for making the backup
[14:54] <aboSamoor> davidstrauss: it was giving when I make the upgrade locally, but with the remote one no progress bar
[14:55] <davidstrauss> aboSamoor: that's because it's still copying the backup
[14:57] <fullermd> LP really needs an upgrade widget.  Doing it remotely is pure pain.
[14:57] <fullermd> It's probably much faster to dump the current branch there and push a new one fresh in the new format.
[15:00] <aboSamoor> fullermd: I don't think it is a good idea to cancel the process
[15:07] <aboSamoor> I got this message before the progress bar
[15:07] <aboSamoor> !!! [Hook] hook(): title not found
[15:09] <davidstrauss> aboSamoor: What's the full output?
[15:10] <aboSamoor> davidstrauss: http://paste.ubuntu.com/274169/
[15:10] <davidstrauss> aboSamoor: I'd ignore that. It didn't cause a backtrace, so it was handled.
[15:38] <aboSamoor> davidstrauss: after updating the remote repo. bzr check operation gave me this output http://paste.ubuntu.com/274179/
[15:41] <davidstrauss> aboSamoor: try running reconcile on it
[15:41] <davidstrauss> aboSamoor: wait
[15:41] <davidstrauss> Standalone tree (format: pack-0.92)
[15:41] <davidstrauss> aboSamoor: That looks un-upgraded
[15:41] <aboSamoor> davidstrauss: seems ok
[15:42] <aboSamoor> I upgraded only the remote repo only
[15:42] <davidstrauss> aboSamoor: did that succeed?
[15:42] <aboSamoor> I did not upgrade the local one
[15:43] <aboSamoor> davidstrauss: http://paste.ubuntu.com/274184/
[15:43] <davidstrauss> aboSamoor: OK. Does check succeed now?
[15:44] <aboSamoor> davidstrauss: nothing changed after the reconcile
[15:45] <aboSamoor> the check operation still gives the same output
[15:47] <davidstrauss> aboSamoor: can you just get a fresh branch from the remote (upgraded) branch?
[15:48] <aboSamoor> yeah, if I understand that I should branch the current repo
[15:49] <davidstrauss> aboSamoor: yeah
[15:49] <davidstrauss> aboSamoor: easier to do that than upgrade both
[15:51] <aboSamoor> davidstrauss: I did the branching, bzr info gives me Standalone tree (format: rich-root-pack)
[15:52] <davidstrauss> aboSamoor: sounds right
[15:52] <aboSamoor> davidstrauss: I will delete the old branch from my desktop, and I will start to split the folders
[15:52] <davidstrauss> k
[16:04] <flvr8> hello all... what's the "bzr way" to move a directory between two (unrelated) branches but maintain revision control of that folder? [the branches are projects; the folder is a module; the module is "graduating" to a more general project]\
[16:17] <davidstrauss> flvr8: split, mv (not bzr mv), and then join
[16:17] <davidstrauss> flvr8: But upgrade your branch first: bzr upgrade --default-rich-root
[16:19] <flvr8> so...    cd Project1 && bzr split mymodule   //    bzr mv mymodule bzr+ssh://somewhere/Project2/trunk     //     cd ../Project2 && bzr update    //    bzr join mymodule    ?
[16:20] <davidstrauss> flvr8: do not bzr mv. just mv
[16:20] <flvr8> oh
[16:20] <flvr8> ok
[16:20] <flvr8> thanks
[16:21] <davidstrauss> flvr8: and you need to do the mv and join locally
[16:21] <flvr8> is there an parallel operation for individual files?
[16:21] <davidstrauss> flvr8: other than moving a file into a directory of its own and doing a split+join, i don't know of a way to take a file's history from one branch to another
[16:21] <flvr8> k
[16:22] <davidstrauss> flvr8: make sure you read all the split+join docs first. what you're doing is quite advanced
[16:23] <flvr8> will do, thanks
[16:46] <aboSamoor> davidstrauss: everything works fine, thanks very much :)
[16:47] <davidstrauss> aboSamoor: :-D
[17:11] <flvr8> davidstrauss: it seems to be getting stuck doing "inserting stream" after doing the above and then add/commit... it's uploaded 300MBs (of something) to the server so far (the module is fairly small); i do not see a similar growth in disk space on the server
[17:12] <davidstrauss> flvr8: Commits are streamed to memory before being committed to disk, AFAIK.
[17:12] <davidstrauss> flvr8: But I have to go. I'll be back online later this weekend. Not sure when. Consider posting your question to http://answers.launchpad.net/bzr
[17:12] <flvr8> ok, thanks
[17:25] <vila> flvr8: just passing around, no time to double check, but keep in mind that join/split still keep the while history (or you wouldn't be able to merge from before split otherwise) so that may explain the volumes you see
[17:26] <flvr8> ah ok
[17:35] <SamB_XP_> hmm, I really like the repoalias plugin ...
[17:56] <blueyed> Are there things planned to make conflict resolving better? BeyondCompare can resolve a lot more conflicts then bzr. Maybe just because of content inspection? (it handles files in different charsets, which bzr does not, ie a file gets converted to another charset in the deriving branch).
[18:05] <james_w> blueyed: that would be good
[18:05] <james_w> blueyed: but check the extmerge plugin
[18:05] <james_w> you can use an external tool, e.g. BeyondCompare to resolve conflicts
[18:06] <blueyed> oh well.. I have a bc-resolve-conflict(s) shell script already. I'll check it out.
[18:08] <blueyed> james_w: should I file a wishlist bug about encoding ambivalence in comparisons? Might you want to just file it (you now more of the inners)? (Link: https://bugs.launchpad.net/bzr/+filebug ;))
[18:09] <blueyed> extmerge is nice, should get added to the core.. :)
[18:10] <blueyed> btw: my script asks about resolving the conflict, when coming back.. I'll forward that as an idea
[18:14] <james_w> please file bugs for anything you think could be improved
[18:14] <james_w> you're in a better place to file than me as you know what you want to happen
[19:37] <Colonel-Rosa> lifeless, thank you for the bzr-bookmarks recommendation yesterday, was what I needed.
[19:37] <Colonel-Rosa> ta
[20:17] <RenatoSilva> Is it possible to directly push a merge directive to launchpad?
[20:18] <RenatoSilva> I mean, instead of pulling from it, then pushing the branch, you'd push the patch, and then pull the changes
[23:32] <lifeless> vila: if they need protecting, they aren't innocent ;)
[23:32] <vila> lifeless: ok, that was you and me :-D
[23:34] <lifeless> vila: and jam and poolie that reviewed ;P
[23:35] <vila> lifeless: ow, that's rude :)
[23:39] <vila> lifeless: by the way, even if t was for a wrong reason, you trapped ~130 tests that were trying to escape isolation, not so bad...
[23:40] <lifeless> vila: they were?
[23:40] <vila> that's what make them failed yes
[23:40] <lifeless> cool
[23:40] <lifeless> uhm
[23:40] <lifeless> I excluded /tmp because ETOOHARD
[23:41] <vila> but you caught TESTROOT, based on tmp
[23:41] <vila> or was it test_dir ?
[23:41] <vila> babune has the logs if you're interested anyway
[23:45] <lifeless> vila: maybe tomorrow; can you link the build in the bug?
[23:45] <lifeless> vila: oh maybe I misremember stuff
[23:45] <vila> lifeless: yup, I wanted to add some info there if only for historical value, I'll do that right now
[23:45] <lifeless> vila: anyhow, its good that the things that have failed are legitimate escape attempts.
[23:46] <lifeless> vila: I thought by the way you described it that it was an isolation-checking bug
[23:46] <vila> lifeless: yes, they *look* like legitimate attempts but it's just an aliasing problem (/private/tmp is not inside /tmp, but in fact they are the same)
[23:47] <lifeless> urgle
[23:47] <lifeless> so we have to permit /private/tmp when we see /tmp ?
[23:47] <lifeless> because realpath is /private/tmp ?
[23:54] <wgrant> bzr-beta-ppa just tried to give me 2.0rc1 (karmic i386). That seems like a really bad idea.
[23:55] <vila> lifeless: no, by using realpath early, we just have to permit /private/tmp and be done with the problem
[23:57] <lifeless> wgrant: its a terrible idea
[23:58] <vila> lifeless, wgrant : bug #432390
[23:58] <wgrant> vila, lifeless: Somebody might want to delete 2.0rc1 from it?
[23:58] <wgrant> I think nothing is better than 2.0rc1.


[00:26] <harushimo> i'm running MAAS. I'm trying to get the images.  It doesn't show up
[00:26] <sarnold> heya harushimo; what do you mean by "it doesn't show up"?
[00:27] <sarnold> harushimo: note that downloading images can take a long time..
[00:27] <harushimo> its starts loading the images and then it goes away
[00:27] <harushimo> it says nodes deployed: 0
[00:27] <harushimo> I'm trying to setting up on my master node
[00:27] <sarnold> you won't be able to deploy nodes until the image imports finish, I don't think
[00:28] <harushimo> how do I know when its finished? Is there an button?
[00:28] <harushimo> I see a button to apply changes
[00:28] <sarnold> dunno, I only ever saw the image importing at the command line..
[00:29] <harushimo> can you teach me how to do it in the command line or refer to me a good document on it
[00:30] <harushimo> No Ubuntu images have been imported. Ubuntu images are required to allow nodes to enlist, commission, and install.
[00:31] <harushimo> I get this message every time
[00:31] <sarnold> harushimo: it's been a few months since I tested, but I used "sudo maas-import-pxe-files" to import the images
[00:31] <harushimo> its been awhile since I've seen that command
[01:30] <harushimo> does anyone how to setup maas-region-controller
[01:30] <harushimo> ?
[01:30] <harushimo> The images aren't still importing
[08:51] <lordievader> Good morning.
[09:32] <Craig4who> Hi Guys
[09:32] <Craig4who> does anyone know when Ubuntu will be supporting 32BIT EFI? really need to use ubuntu on some Atom Tablets, but finding it tricky
[09:42] <Walex> Craig4who: "really need" usually means that you would be willing to pay Canonical to do custom work for you, or else it is not "really need".
[09:44] <Craig4who> ok so currently its not supported but i would need to contact Canonical for support
[09:44] <Craig4who> would they cover me under a paid subription, or would it be classed as a project, with a one off payment?
[09:44] <Walex> I am not related to Canonical.
[09:45] <Walex> note that "really need" could mean also that you or a contractor you hire would roll your own.
[09:45] <Craig4who> ok. Can you recommend anyone contractor?
[09:45] <Walex> anyhow I think that Canonical have a consulting arm
[09:46] <Walex> can't recommend contractors...
[09:46] <Craig4who> ok mate. Thanks for your response appreicate it
[09:46] <Walex> but also note that Caonical have a definite interest in tablets as well as (mainly) phones.
[09:46] <Craig4who> ok thats good to know
[09:46] <Walex> see this typical photo: http://www.canonical.com/products
[09:47] <Craig4who> yea..
[09:47] <Craig4who> makes sense
[09:48] <Craig4who> ill have to contact them to see if they can help
[09:48] <Walex> Craig4who: also note that a tablet is a bit of in-between: Ubuntu for phones is somewhat different from Ubuntu desktop, as to app delivery, and GUI, and a tablet could plausibly run either.
[09:49] <Walex> Craig4who: probably Canonical are more interested nowadays in Ubuntu for phones running on a tablet.
[09:49] <Craig4who> yea
[09:51] <OpenTokix> What prevents you fro msending an email to them?
[09:51] <Craig4who> nothing at all. Thought i would ask experts in here first see if anyone has experience
[09:55] <Walex> http://partners.ubuntu.com/programmes/phone
[09:59] <Craig4who> cheers
[14:58] <samba35> i want to boot ubuntu pxe boot from another ubuntu pxe server
[14:58] <samba35> i want to boot laptop from ubuntu server ,laptop has no harddisk/cdrom
[14:59] <samba35> i have dhcp/dns server and laptop can boot with pxe
[15:10] <genii> samba35: In your dhcp server config, use the next-server option to specify what machine it should boot from if it's not the one handing out the IPs
[15:10] <samba35> yes but what other changes i have to make
[15:10] <genii> samba35: You might find https://help.ubuntu.com/community/PXEInstallServer informative
[15:11] <samba35> ok ,thanks
[15:14] <Vexena> Anyone got some knowledge about upstart? I've got this script so far: http://pastebin.com/uDwFdVdz but would like to make that the jar runs under a unprivileged user instead of root
[15:14] <Vexena> how could I implement that?
[15:16] <jrwren> Vexena: http://upstart.ubuntu.com/cookbook/#setuid
[15:16] <jpds> Vexena: https://superuser.com/questions/213416/running-upstart-jobs-as-unprivileged-users
[15:16] <Vexena> will check that out, thanks
[19:09] <kully3xf> how to change dns settings on startup on aws ec2
[19:20] <jrwren> kully3xf: I called resolvconf from cloud-config cloudinit userdata script.
[19:21] <jrwren> kully3xf: http://pastebin.ubuntu.com/10999046/
[19:22] <kully3xf> righteous. Thanks!
[21:20] <pedahzur> Well, this is frustrating. I just tried to upgrade my border router box from Ubuntu 10.04 to 12.04, and got this message from do-release-upgrade: "Your system uses an i586 CPU or a CPU that does not have the 'cmov' extension. All packages were built with optimizations requiring i686 as the minimal architecture. It is not possible to upgrade your system to a new Ubuntu release with this hardware."  Any recommendations for a Linux distro that
[21:20] <pedahzur> doesn't require 'cmov' or other i686 specific instructions?  Really don't want to throw out the hardware, and 10.04 is no longer supported, so...
[22:00] <dasjoe> pedahzur: you might have more luck with some BSD, maybe take a look at pfsense for a router?
[23:36] <pedahzur> dasjoe: Possibly. Just wanted to remain with something familiar.


[22:40] <dagarwal82> Hi all, I am having a hard time to work on designing a small problem, is it the right place to ask for help ?


[00:02] <cqfd93> Hi All!
[00:03] <cqfd93> GodbyK, are you listening?
[00:03] <godbyk> cqfd93: Yep!
[00:03] <cqfd93> great news!
[00:04] <cqfd93> we're ready to finalize precise and quantal
[00:04] <godbyk> cqfd93: Ah, excellent!
[00:04] <cqfd93> yes, finally
[00:05] <godbyk> Are both branches ready?
[00:05] <cqfd93> yes, sir!
[00:06] <godbyk> cqfd93: Okay. I should use the fr.po files from Launchpad?
[00:08] <cqfd93> yes, here are the links:
[00:08] <cqfd93> precise : http://launchpadlibrarian.net/125649179/ubuntu-manual_ubuntu-manual-fr.poquantal : http://launchpadlibrarian.net/125649191/ubuntu-manual_ubuntu-manual-fr.po
[00:08] <cqfd93> quantal : http://launchpadlibrarian.net/125649191/ubuntu-manual_ubuntu-manual-fr.po
[00:08] <godbyk> cqfd93: Thanks!
[00:08] <godbyk> cqfd93: I'll start working on it soon and email you if I find any problems or have more tidbits for you to translate.
[00:09] <godbyk> cqfd93: Could you take a look at the text on the back cover and translate those paragraphs for me?  Just email me the translations and I'll have thorwil generate the covers.
[00:09] <godbyk> cqfd93: You can find the English cover in titlepage/lulu-en_US.pdf (or .svg).
[00:10] <cqfd93> Ok!
[00:10] <cqfd93> Can you wait untill tomorrow?
[00:10] <cqfd93> It's late here (1:10am...)
[00:11] <godbyk> cqfd93: Oh, yeah. It's not rush. I won't be able to do too much work on it myself 'til this weekend.
[00:11] <godbyk> You should get some sleep. :)
[00:11] <cqfd93> Yes!
[00:11] <godbyk> cqfd93: G'night!
[00:11] <cqfd93> Thank you!  See you tomorrow.
[00:11] <cqfd93> Bye everybody!
[16:00] <hannie> cqfd93, hi
[16:01] <hannie> I have just added wubi to the glossary, but I have removed the pageref from it (in Dutch version precise-e2)
[16:01] <hannie> I do not think that IN the glossary we should refer to a chapter/section
[16:02] <hannie> It is the other way around. In the section we refer to the explanation of the term in the glossary
[16:15] <cqfd93> Hi Hannie!
[16:15] <hannie> hey cq
[16:16] <hannie> I just changed the sudo line (added \prompt \userinput as you suggested (in Dutch version)
[16:16] <cqfd93> Yes, removing the pageref is probably a good idea, as the wubi section points to the glossary :-)
[16:17] <hannie> I will add the sudo change to my notes for Raring (English). Thanks for reporting it.
[16:18] <hannie> I will upload my nl.po to LP in a minute
[16:18] <cqfd93> for the sudo line and at least another one, I added a line break (\n) between the command and the output
[16:20] <hannie> sudo updategrub is on a line of its own
[16:21] <hannie> ah, yes, just found it. Good catch again ;)
[16:22] <cqfd93> https://translations.launchpad.net/ubuntu-manual/precise-e2/+pots/ubuntu-manual/fr/1653/+translate
[16:22] <cqfd93> and
[16:22] <cqfd93> https://translations.launchpad.net/ubuntu-manual/precise-e2/+pots/ubuntu-manual/fr/1655/+translate
[16:30] <cqfd93> hannie, can you look at the bottom of page 117 in the French precise-e2 pdf?  There's a problem with the size of the titles "Comptes utilisateurs"
[16:30] <cqfd93> and "Utilisateurs et groupes"
[16:32] <cqfd93> page #111 in the Dutch manual
[16:33] <hannie> I'll have a look right now
[16:35] <hannie> cqfd93, let me finish those \promt \userinput strings first and then I will download fr.po (precise-e2)
[16:37] <cqfd93> hannie, no need to compile it, here is the link to the pdf: http://ubuntuone.com/1fD6ZGk4WYFDcoCMGn6HN2
[16:38] <hannie> cqfd93, ok, in a minute I'll have a look
[16:41] <cqfd93> ok!
[16:44] <cqfd93> Just found something in the Dutch manual: the first paragraph of each section is missing the indentation, the French manual doesn't show this problem
[16:44] <hannie> I think in the English version the 1st par has no indentation either
[16:45] <hannie> I talked to Kevin about this a long time ago
[16:46] <cqfd93> It looks like it has been fixed in the French version
[16:49] <hannie> ah, I know what happened to Comptes utilisateurs
[16:50] <hannie> Let me find the link on the bug report I sent to LP a while ago
[16:51] <cqfd93> ok
[16:52] <hannie> cqfd93, https://bugs.launchpad.net/ubuntu-manual/+bug/1082852
[16:52] <manualbot> Launchpad bug 1082852 in ubuntu-manual "chapter6 section user accounts" [Medium,Confirmed]
[16:52] <cqfd93> Even the English version has this title problem
[16:52] <hannie> hence my bug report :)
[16:53] <cqfd93> :-)
[16:53] <hannie> we should switch subsection and section here
[16:53] <hannie> We will change this in Raring
[16:55] <cqfd93> But the font sizes will still be wrong?
[16:56] <hannie> font of section is bigger than subsection, yes
[16:57] <hannie> So, if User account = section and Users and groups = subsection, it should be ok
[16:59] <hannie> On second thought, it should be reshuffled
[17:00] <cqfd93> In your bug description, you said:
[17:00] <cqfd93> I think it should be
[17:00] <cqfd93>  \section{Users and groups}
[17:00] <cqfd93> \subsection{user accounts}.
[17:01] <hannie> Well. user accounts is just one line. It would look odd after paragraph "User and groups"
[17:01] <hannie> I would make User account a section and the others subsections
[17:02] <cqfd93> No, user accounts is the title of a subsection that hat 3 paragraphs
[17:02] <hannie> So therefore it should be Section (User accounts :) )
[17:03] <cqfd93> I'm confused...
[17:03] <cqfd93> Let me try to understand:
[17:03] <cqfd93> section Users and groups has several subsections
[17:03] <cqfd93> user accounts
[17:04] <hannie> If User accounts would have 3 paragraphs, then those paragraphs would not be subsections
[17:04] <cqfd93> users management
[17:05] <hannie> So: the section User accounts has 4 subsections namely:
[17:05] <hannie> users and groups/managing users/managing groups/applying groups to files and folders
[17:07] <cqfd93> To me, it should be:
[17:07] <cqfd93> section users and groups
[17:07] <cqfd93> 4 subsections User accounts/managing users/managing groups/applying groups to files and folders
[17:08] <cqfd93> and this is what you imply in your bug report
[17:08] <hannie> Shouln't this be: section user accounts, subsection Users and groups
[17:10] <cqfd93> no, because users is just part of users and groups
[17:10] <hannie> If you do this:
[17:11] <hannie> Section Users and groups (not followed by any text) and then
[17:11] <cqfd93> Hi CarstenG
[17:12] <CarstenG> Hi Sylvie
[17:12] <hannie> subsection User accounts (with text following), then it is not logical
[17:12] <hannie> hi CarstenG
[17:12] <CarstenG> Hi Hannie
[17:13] <hannie> CarstenG, we were just discussing this bug:
[17:13] <hannie> https://bugs.launchpad.net/ubuntu-manual/+bug/1082852
[17:13] <manualbot> Launchpad bug 1082852 in ubuntu-manual "chapter6 section user accounts" [Medium,Confirmed]
[17:13] <cqfd93> funny that manualbot just repeats the bug number you posted :-)
[17:13] <hannie> ah those bots
[17:15]  * cqfd93 is thinking about this: Section Users and groups (not followed by any text) and then subsection User accounts (with text following), then it is not logical
[17:16] <hannie> cqfd93, let me read what it says in paragraph Users and groups to see if we can just exchange these two headings
[17:19] <cqfd93> hannie, I think I understand that you think there should be at least one paragraph between these two titles
[17:19] <hannie> ok, in the first paragraph they talk about users and groups, so the title is right
[17:21] <hannie> cqfd93, I am thinking of a title for the subject/section, followed by the different (sub)sections like: Managing users, Managing groups etc.
[17:22] <cqfd93> to make sure we're talking about the same paragraphs, we should look at the same pdf: the English pdf?
[17:23] <hannie> What you suggest is: the title is "Users and groups" and the subsections are: Users and groups, Managing users etc.
[17:24] <hannie> sorry, Title = Users and groups, subsections are: user accounts, managing users etc.
[17:25] <cqfd93> Yes: Title = Users and groups, subsections are: user accounts, managing users etc.
[17:25] <cqfd93> that sounds more logical to me
[17:26] <cqfd93> But now, after reading what would be the user accounts section, I see they are talking about groups... grrrrrrrrrrr!!!
[17:27] <hannie> Now you see what I mean. Life is difficult :(
[17:27] <cqfd93> ;-)
[17:28] <hannie> Hence my proposal to make the title (=section) User accounts and one of its subsections = Users and groups
[17:30] <hannie> I need a break........I am going to finish nl.po and upload it. Otherwise kevin may start publishing without these changes
[17:30] <hannie> cqfd93, we still have lots of time before Raring is released. So, no worries about sections and subsections :)
[17:31] <cqfd93> OK!
[17:31] <hannie> see you all
[17:31] <cqfd93> see you!
[17:31] <CarstenG> see you
[17:44] <godbyk> Hey, CarstenG. it looks like lulu.com is still having trouble printing the 12.10 manual.
[17:44] <CarstenG> Hi Kevin
[17:44] <CarstenG> grml.
[17:44] <CarstenG> Still with you new PDF with Adobe?
[17:45] <godbyk> CarstenG: And we have a new support guy to boot. So far he's just sent me the same link of recommended PDF creation software but with no other useful help.
[17:45] <godbyk> As far as I can tell, the current 12.10 manual should be using the PDF that Lulu generated for us.
[17:45] <godbyk> So one would assume that PDF would be okay.
[17:45] <godbyk> Seems not.
[17:46] <godbyk> I think we should start exploring other printers in case lulu.com can't sort this out.
[17:46] <cqfd93> hi godbyk!
[17:46] <godbyk> Hey, cqfd93!
[17:47] <godbyk> cqfd93: I'm trying to get this lulu.com problem sorted out before I start trying to publish a bunch more manuals with them.
[17:47] <godbyk> cqfd93: Seems some of their printers don't like our PDFs. But it's difficult to get any details from them.
[17:47] <godbyk> They just keep saying, 'You shouldn't use LaTeX.'
[17:47] <CarstenG> Yes, we should find a new partner for printing, if lulu can not fix this issue.
[17:48] <cqfd93> do you know what the problem is?
[17:48] <CarstenG> GRML
[17:48] <CarstenG> LaTeX is the best. :-)
[17:48] <CarstenG> They should use good printers ...
[17:49] <godbyk> CarstenG: Agreed.
[17:49] <godbyk> CarstenG: And it seems that *some* of their printers are fine.. because it printed my copy of the manual without any complaints. And that was back when we still had transparent images and the like.
[17:49] <godbyk> cqfd93: I don't know what the problem is. I keep asking and they keep guessing. Then I fix the thing they think is the problem and there are still problems.
[17:50] <CarstenG> Yes, so they _can_ print our LaTeX files, if they want. It is not a problem with our files...
[17:50] <cqfd93> do they print the 12.04 manual OK?
[17:51] <godbyk> cqfd93: Sometimes.
[17:51] <cqfd93> :-(
[17:51] <godbyk> cqfd93: They printed it okay for me. But then they had problems printing it for Carsten.
[17:51] <godbyk> cqfd93: Then I think we got it printed okay for Carsten (right, CarstenG?) but now someone else is having problems getting it printed.
[17:52] <cqfd93> Frustrating and time consuming :-(
[17:54] <godbyk> I'm starting a list of possible printers here: http://pad.ubuntu.com/PrintOnDemand
[17:54] <godbyk> Right now I'm just pulling up lists of competitors to lulu.com and competitors of the competitors.
[17:54] <godbyk> I haven't looked at any of their websites yet.
[17:54] <godbyk> We can start looking at their websites and making notes of which ones would work for us, pricing info, etc.
[19:23] <CarstenG> Kevin, i have no access to your pad
[19:23] <CarstenG> OpenID Authentication Required
[19:23] <CarstenG> Authorization is required to access http://pad.ubuntu.com/PrintOnDemand
[19:23] <CarstenG> Either you have not been granted access to this resource or your entitlement has timed out. Please try again.
[19:23] <CarstenG> You are currently logged in as https://login.ubuntu.com/+id/w48WtfY. (logout)
[19:24] <CarstenG> Why do I need a login for that pad?
[20:23] <CarstenG> Sylvie
[20:23] <cqfd93> Yes CarstenG
[20:24] <CarstenG> I have just thought about the "users and groups" topic
[20:24] <CarstenG> I stay at my opinion, as I wrote in the bug report
[20:24] <cqfd93> so, we both agree
[20:25] <CarstenG> We should make
[20:25] <CarstenG> \section{Users and groups}
[20:25] <CarstenG> \subsection{user accounts}
[20:25] <CarstenG> \subsection{Managing users}
[20:25] <CarstenG> \subsection{Managing groups}
[20:25] <CarstenG> \subsection{Applying groups to files and folders}
[20:25] <cqfd93> that's exactly what I think
[20:26] <cqfd93> but the first paragraphs are a bit confusing
[20:26] <cqfd93> as they talk about groups
[20:27] <CarstenG> as well as users. :-)
[20:28] <cqfd93> yes!
[20:30] <CarstenG> So maybe we could move the third paragraph "Every user in Ubuntu is ..." to the \subsection{managing groups}
[20:34] <CarstenG> Ok, I would upload the changed section heading to raring and cose the bug.
[20:36] <cqfd93> Yes, that would be good.
[20:36] <CarstenG> ok
[20:37] <CarstenG> and online in rev 25 :-)
[20:37] <manualbot> http://bazaar.launchpad.net/ubuntu-manual/revision/25 | http://bazaar.launchpad.net/ubuntu-manual -r 25
[20:39] <cqfd93> Good!  thanks to the bot for the link ;-)
[20:39] <cqfd93> oops, dead link :-(
[20:42] <CarstenG> yeah. Be quiet, Bot!
[20:42] <CarstenG> :-)
[20:43] <cqfd93> ;-)


[00:02] <b-yeezi> kantlivelong, with what?
[02:52] <goddard> i have a problem where my wordpress site isn't able to connect to the mysql server
[02:52] <goddard> i can login to the server from phpmyadmin
[03:33] <codepython777> where can i download all the current .deb files for 14.04.4?
[03:40] <patdk-lap> ubuntu package servers
[03:40] <patdk-lap> archive.ubuntu.com and security.ubuntu.com
[03:44] <codepython777> patdk-lap: which directory do i clone for getting to 14.04.4 packages?
[03:44] <codepython777> patdk-lap: http://archive.ubuntu.com/ubuntu/pool/main/ - are these files shared between multiple versions of ubuntu?
[03:46] <patdk-lap> yes
[03:46] <patdk-lap> use something like apt-mirror
[03:47] <codepython777> patdk-lap: looks like one needs apache + apt-mirror?
[03:47] <codepython777> patdk-lap: is there a script somewhere that will mirror all .deb files for a given version (like 14.04.4)?
[03:48] <patdk-lap> ya, apt-mirror
[03:48] <codepython777> patdk-lap: is there a one line command using apt-mirror to do what i need?
[03:49] <patdk-lap> sure, service apt-mirror start
[03:49] <patdk-lap> though, I think it normally goes into cron
[03:50] <codepython777> patdk-lap: where does it write the .deb files?
[03:50] <patdk-lap> http://manpages.ubuntu.com/manpages/trusty/man1/apt-mirror.1.html
[08:14] <jamespage> ddellav, coreycb: lots of experimental uploads from zigo over the last 24hr - which way do we need to catchup?
[10:28] <Yanick> Any one have any good guides/books for high performance network tuning for ubuntu?
[10:40] <Xin> yanick; er, what in particular were you trying to tune..
[10:40] <Xin> It comes in a fairly '
[10:41] <Xin> 'best for everyone' configuration
[10:41] <Yanick> IDS, so IRQ cpu stuff etc.
[10:41] <Yanick> and kernel stuff to boost its performance
[10:43] <Xin> see, none of that really means anything
[10:43] <Xin> lol
[10:44] <Yanick> ?
[10:45] <Xin> for most network adapters the driver already comes compiled into the core, irq's are utterly meaningless to do with anything 'optimization', 'cpu stuff' = ???
[10:48] <Yanick> my plan was to split the traffic with 4 rss queues, and then have 4 suricata workers pinned to each CPU, not done or tested this before so thats why I asking, pretty much looking for a best practice guide / tutorial for high performance networking stuff
[10:51] <cpaelzer> Yanick: in my personal experience in like 99.9% eventually it turns out that the tuning made it worse
[10:52] <cpaelzer> Yanick: the reason is that you have to know a lot of your workload (sizes, timings, ...) to make good tunings
[10:52] <cpaelzer> Yanick: especially since most really critical things are auto-tuning these days
[10:53] <cpaelzer> Yanick: IRQs are local to the card you can set up rps (if your card can HW assist even more effectively) and the workers will migrate to the IRQ arriving cpu anyway
[10:53] <Yanick> cpaelzer: what about C and P states? should i just set it to max all the time or let the auto tuning do that too?
[10:54] <cpaelzer> Yanick: as I said "in my experience" tuning rarely helps in the long term - people do it on a POC state and nobody realizes the workload changes later on
[10:54] <cpaelzer> Yanick: you surely can do it, but it is not a one shot task - IMHO it has to be rechecked and reevaluated continuously
[10:56] <cpaelzer> Yanick: that means you can do all of https://www.kernel.org/doc/Documentation/networking/scaling.txt but then it is "you" who have to take care it still applies over time
[10:56] <cpaelzer> and that is why I mean, I too often have seen environments where years ago someone tuned something and it is making it worse today
[10:57] <Yanick> cpaelzer: Tnx alot! :)
[10:58] <Yanick> cpaelzer: Got any experience with dpdk or any other kernel bypass methods? good? bad? hard?
[11:02] <cpaelzer> Yanick: I'm the Ubuntu dpdk maintainer :-)
[11:03] <cpaelzer> Yanick: it works, but it is a) not generally  helping but for special purposes and b) only maturing the last 12 months
[11:03] <cpaelzer> Yanick: with b) I mean you see it getting more stable day by day which is great, but up until recently it was all too easy to hit severe bugs
[11:04] <cpaelzer> Yanick: https://insights.ubuntu.com/2016/05/05/the-new-simplicity-to-consume-dpdk/ https://help.ubuntu.com/16.04/serverguide/DPDK.html
[11:05] <cpaelzer> Yanick: so if you are using Openvswitch you have a good chance to gain some benefit, and I hope that with upcoming OVS 2.6 and DPDK 16.07 things are more stable
[11:05] <cpaelzer> Yanick: but if you are just runnign some arbitrary service on your server they won't help you until they actually exploit DPDK
[11:05] <cpaelzer> Yanick: I've seen work on nginx for that and there might be more I haven't seen
[11:06] <cpaelzer> Yanick: the performance answer always was and probably always will be "it depends"
[11:12] <Yanick> cpaelzer: haha nice!
[11:14] <Yanick> cpaelzer: Done any performance test with lxd containers? much overhead/latency? would it be possible to run a 1gbps sensor(suricata) in lxd?
[11:15] <cpaelzer> TL;DR container (almost) always is as fast as without virtualization
[11:31] <Yanick> Think I will give that a try :D need to set up a sniffing interface in promisc mode and map it into the container then?
[11:43] <cpaelzer> Yanick: yeah you should just try and check if the bridge would eat up too much bandwidth
[11:43] <cpaelzer> Yanick: I only found older LXC howtos, once he is online later on stgraber can point you to something recent for lxd
[12:00] <Yanick> cpaelzer: Thank you so much for your time :) appreciated!
[12:15] <coreycb> jamespage, we should be good for oslos and clients but most anything else could possibly need an update
[13:53] <jamespage> frickler, finally moving on the 10.2.2 update for ceph
[13:53] <jamespage> apols for the lag
[13:53] <jamespage> dropped under a carpet somewhere
[14:03] <frickler> jamespage: np, thx for the update, most of the openstack stuff seems to have gotten into proposed yesterday already, so that should be fine for now
[14:03] <jamespage> frickler, ceph accepted - takes some hours to build...
[14:06] <frickler> jamespage: did you ever look at generating a set of packages with jemalloc enabled instead of tcmalloc? it seems that this is a compile-time-only decision due to the way some libraries are included, the variant using LD_PRELOAD doesn't seem to work anymore
[16:06] <CrashTestDummy> Hello. I configured my lxd on ubuntu 16.04 according to this tutorial on the interwebz : https://insights.ubuntu.com/2015/11/10/converting-eth0-to-br0-and-getting-all-your-lxc-or-lxd-onto-your-lan/
[16:07] <CrashTestDummy> The problem is that i do noet get any DHCP address from my opnsense machine to the containers. The opnsense machine also does not seem to get a DHCP request from the containers
[16:08] <roaksoax> CrashTestDummy: that's probably an issue with the bridge you are using
[16:08] <CrashTestDummy> log : https://codeshare.io/Ndexm
[16:09] <CrashTestDummy> I think so too, can you please help me by having a look at the codeshare to see if you find something strange ?
[16:10] <compdoc> I removed lxd just so I dont have to see boot messages from it anymore
[16:11] <CrashTestDummy> But i am actually using lxd
[16:20] <compdoc> CrashTestDummy, how is you networking setup? pastebin.com your /etc/network/interfaces
[16:20] <stoker> Hi, does anyone have a document which describes how to deploy maas, juju and openstack on xenial?
[16:21] <stoker> I have 8 HP SLG7 computes where I wish to do a deployment.
[16:21] <CrashTestDummy> my interfaces file is the last section of the codeshare
[16:22] <CrashTestDummy> https://codeshare.io/Ndexm
[16:41] <stoker> Is there a way to deploy xenial from an ISO, providing a configuration file and skip all the questions it asks during install?
[16:42] <nacc> stoker: you are referring to a preseed file
[16:42] <nacc> stoker: and i think you can put a preseed file on the iso that will get loaded at install time
[16:43] <stoker> ok, thanks
[16:43] <stoker> I'll google it
[16:43] <nacc> stoker: https://help.ubuntu.com/community/Cobbler/Preseed is roughly a no-questions-asked install preseed
[16:43] <nacc> stoker: https://wiki.debian.org/DebianInstaller/Preseed/EditIso
[16:45] <stoker> nice
[16:45] <nacc> stoker: i *think* (not sure, never tried it), but you might be able to pass the preseed as an install-time parameter to the installer kernel and it might also be able to d/l it, not sure if that requires specifically the netinstall kernel/initrd combo, though
[16:45] <stoker> I can remaster the ISO if necessary but DL would be real easy
[16:46] <nacc> stoker: yeah, should be easy to test, at least
[16:46] <nacc> stoker: note that depending on how you install, you might also need to pass things like the network configuration to the installer so that it can download the preseed
[16:46] <nacc> stoker: at that point, you might as well pxe install :)
[16:48] <stoker> inception
[17:33] <cpaelzer> rbasak: when you consider merge review priorities you might have a look at the last two comments in bug 1567540
[17:33] <cpaelzer> rbasak: it seems it starts to get uncomfortable :-)
[17:55] <teward> is there a known issue where landscape-client will eat up all the RAM and swap on small-sized servers?
[17:55] <teward> and then not clean up after itself thereby nomming all the data?
[17:55] <teward> Xenial, by the way
[17:57] <deadnull> so I created a custom bind9 package from the deb-src, and I want to host on my mirror (using aptly) is there a way to fix the duplicate package (Writing more data than expected) error?
[18:19] <sarnold> deadnull: what error is that? I don't think I've ever seen it..
[18:19] <sarnold> deadnull: can you pastebin the error  and surrounding context?
[18:20] <sarnold> teward: news to me, it might be news to them too :) maybe grab some ps output on the process every hour for a few days and paste the log to a bug?
[18:24] <deadnull> sarnold so the deal is I am running an aptly server. I am mirroring xenial, xenial-updates, and xenial-security. The issue is i build bind9 from source with mysql-dlz, which has different content then the distribution package in the xenial repo, so when I do an install, there is a conflict because the packages are different.
[18:25] <deadnull> I think I have found a way to remove the upstream bind9 package from my mirror so there is no conflict. the reason I am doing this is because I dont want to have deb-src enabled on my servers and compiling custom packages on servers.
[18:28] <sarnold> deadnull: hmm, if you give your bind package a unique-to-you version number I think that ought to just work
[18:32] <deadnull> sarnold yea, looking into that as an option now, forgive my ignorance with dpkgs, how would I set a custom version/name - my google-fu is apparently failing me
[18:32] <sarnold> deadnull: in the debian/changelog change the top-most version number -- adding -deadnull to the end would probably be sufficient
[18:33] <sarnold> (better yet, make your own new entry in the file, so you can see what you did to it the next time you have to rebuild :)
[18:33] <deadnull> woot, thanks man, I really appreciate it!
[18:33] <deadnull> i was in the rules file
[18:33] <sarnold> yeah, you can look and look and look and never spot it :)
[18:50] <teward> sarnold: going to spin up a dns3 on my net and try and replicate
[18:50] <teward> can't have the only two DNS resolvers for my net having zero space for bind9 to use ;P
[18:51] <sarnold> teward: are those auths or recursors?
[18:52] <teward> sarnold: half-and-half.  internal recursors for my network, with authoritative on some of the domains (overriding public IP for private IP ranges and such necessary for proper internal network routing)
[18:53] <sarnold> aha
[18:54] <teward> sarnold: since the entire network runs DNS through there, I have to make sure those are 'up'
[18:54] <teward> 100% swap and 98% RAM means it can't operate
[18:54] <teward> was able to get in and stop landscape-client and subprocesses with a kill -9
[18:55] <teward> freed up all the swap and all but 100MB of RAM (in use by the rest of the system)
[18:55] <teward> unclean approach, I know, but...
[18:55] <teward> with both DNS servers having 512MB RAM, and 512MB swap...
[18:56] <teward> and landscape-client trying to nom almost a full gig...
[18:56] <teward> sounds to me there's a memleak somewhere
[18:56] <sarnold> it's quite possible :) hehe
[18:56] <sarnold> I suspect most of the machines running landscape client have a bit more headroom
[18:57] <teward> true
[18:57] <teward> but i noticed it eating 512 RAM and 48 MB on a 1024MB VPS so...
[18:57] <teward> and fun fact: this doesn't happen with 14.04
[18:57] <teward> it uses about half that.
[18:58] <coreycb> ddellav, I synced saharaclient 0.15.0
[19:04] <Xin> hey guys and girls I want to set up a proxy ring of sorts, and have it so that at a random given node, I siphon data out at random, but only my static ip is allowed.. any other traffic is put into an endless loop lol
[19:04] <Sling> what
[19:06] <Xin> so like 4 nodes of routing, mainly http but other stuff too, a full vpn
[19:06] <Xin> I connect to one of these at random and make requests
[19:07] <Xin> Only that node should have the request, and should only perform it for my ip address
[19:07] <Xin> for all other addresses, it should just infinitely loop 1,2,3,4,1,2,3,4 etc, or similar
[19:08] <sarnold> and why should it do that?
[19:08] <Xin> Well mainly for lols
[19:08] <sarnold> do the owners of those machines pay you for bandwidth used? :)
[19:09] <Xin> they're all my vps's
[19:09] <Xin> geologically sparse
[19:10] <Xin> I also need to set up the full vpn thingy lol :/
[19:10] <Xin> never done that before
[19:10] <Xin> I was supposed to have a partner in all this but they bailed because they are a flake
[19:10] <Xin> my mistake.
[19:12] <Xin> what id love is some kind of time sensitive token for everything over the vpn
[19:12] <Xin> so even if it were logged, at a later date, it would be irrecoverable essentially
[19:14] <Xin> im not doing anything dodgy, I just want to be as secure as possible
[19:14] <Xin> security isnt really my thing though
[19:14] <sarnold> I think the DHE ciphersuites will provide that
[19:14] <Xin> oh yeah?
[19:14] <Xin> what vpn server would you recommend?
[19:15] <Xin> or how do I configure such a thing haha
[19:15] <sarnold> the best VPN i've ever used was an IPSec configuration; but that doesn't always work through e.g. terrible hotels.
[19:16] <sarnold> openvpn seems to have a lot of fans, it seems to be able to work through a lot of terrible misconfigured networks
[19:18] <Xin> yeah that seems to be the go
[19:24] <Xin> so I basically just want to steal its network stack
[19:24] <Xin> um
[19:24] <Xin> is that what a vpn inherently does?
[19:24] <Xin> or do I need other software for each specific protocol
[19:26] <sarnold> depends on the VPN software, most can provide generic IP support so they can route any IP-based protocol, usually icmp, udp, and tcp
[19:26] <sarnold> but e.g. tor is limited to just tcp, drastically reducing what it can be used for
[19:28] <Xin> yeah, I was thinking about using an anonymous vpn that then routes through tor
[19:28] <Xin> is that overkill lol
[19:28] <skylite> btw any working ideas to block tor traffic?
[19:29] <Xin> cut your network cables
[19:29] <sarnold> skylite: the list of exit nodes is published, just drop packets from them
[19:29] <Xin> works 100%
[19:29] <skylite> sarnold wow. all of them?
[19:30] <sarnold> skylite: yeah
[19:31] <skylite> cool
[19:32] <Xin> so is it overkill? is it even a good idea at all?
[19:32] <Xin> itd be nice to have a tor address too
[19:32] <Xin> im not sure how all that works
[19:55] <Xin> I also need to be able to coordinate one task between all the nodes if I so choose
[19:55] <Xin> eg I might install a new package
[19:55] <Xin> I dont want to do that on every vps
[19:55] <Xin> nor do I want an apt-get specific solution. I want to essentially batch bash lol
[20:44] <Xin> ok so I have openvpn
[21:54] <kzaitsev_ws> I have a possible very dumb question, but can't really find the answer anywhere =)
[21:55] <kzaitsev_ws> do SRU bugs go to https://launchpad.net/ubuntu/ ?
[21:56] <kzaitsev_ws> I'm in the process of understanding how to propose an update to my openstack project's package to cloud-archive
[22:04] <rbasak> SRU bugs go to the usual place for the package - https://bugs.launchpad.net/ubuntu/+source/<source package name>
[22:04] <rbasak> Then they need to have a series added for the SRU target.
[22:05] <rbasak> I don't remember what we do to track bugfixes in the cloud archive specifically. coreycb may be able to help you with that.
[22:13] <Xin> if I told you my name was Todd Aspen
[22:13] <Xin> would that seem legit to you
[22:24] <kzaitsev_ws> rbasak: yep, I've been pinging him for a day or two =) I think he's somewhere in Europe and is asleep now =)
[22:25] <kzaitsev_ws> Xin: now that's a really weird thing to stumble into =)
[22:28] <terje> when enrolling machines in maas, is it possible to specify a naming schema?


[17:30] <Robathome> greetings all! Linux newbie here... I have question about loading the OS into RAM on startup. If I understand correctly, if you boot the entire OS into RAM, then any changes that you make do not persist after the next shutdown. Is it possible to load everything into RAM on startup, and then back /root, /home, /var, etc into a writeback bcache?


[05:14] <frederick> hello, how could i modify the default alt+right click behavior?
[05:15] <frederick> i use blender but the shortcut does not work
[09:55] <antto> how do i install kde?
[14:38] <OvenWerk1> antto: I would think sudo apt-get install kde-standard
[14:38] <OvenWerk1> That installs the desktop plus standard kde apps
[14:39] <OvenWerk1> just the desktop might be plasma-desktop
[14:40] <OvenWerk1> hmm, there is also kde-plasma-desktop which installs the desktop plus a "minimal set of apps"
[14:40] <OvenWerk1> there is kde-plasma-netbook for something that works well with a small screen.
[14:41] <OvenWerk1> antto: you would probably get better info from #kubuntu though.
[14:44] <OvenWerk1> kde-full probably gets more stuff yet
[14:46] <OvenWerk1> antto: you could go by steps: install plasma-desktop, try it... is it enough? if not try kde-minimal (might be a better place to start) then you could add kde-standard if minimal is not enough and then kde-full if standard is not enough.
[15:31] <antto> i did installed kde-plasma-desktop, and now kde-standard, but things still look the same
[15:32] <antto> ubuntustudio uses gnome, right?
[15:40] <antto> ah, it's selectable from the login screen.. from the arrow button


[02:51] <slangasek> infinity: should casper and livecd-rootfs be using xz-utils instead of lzma?
[02:55] <infinity> slangasek: And dell-recovery probably, yeah.
[06:33] <doko> pitti, unable to give back autopkg tests, timing out
[07:02] <pitti> doko: yes, autopkgtests.u.c. seems to be down, looking
[07:02] <pitti> i. e. just the debci frontend, the machinery works
[07:02] <pitti> doko: as soon as the queue settles, I'm going to mass-retry all the failures, though
[07:08] <pitti> oh, OOM killer
[09:25] <Odd_Bloke> Why is Vivid still listed as Supported (https://launchpad.net/ubuntu/vivid/)?  (Snappy?)
[09:28] <apw> Odd_Bloke, yes, that is snappy related, not sure if that status can change or not and keep that side working
[09:29] <xnox> Odd_Bloke, and because Ubuntu Touch is on vivid too
[09:29] <xnox> Odd_Bloke, note how vivid is not gone from the mirrors.
[09:29] <Laney> vivid was a vintage release
[09:30] <Laney> top quality packages
[09:30] <Laney> good sun that year
[09:30] <xnox> Odd_Bloke, use distro-info / distro-info-data, don't trust launchpad. it's supported to keep PPAs working for phone landings.
[09:30] <xnox> Laney, approved by all hipsters in Hoxton
[10:43] <pitti> I'm sure to the kernel team it feels more like venomous viper by now ;)
[10:43] <apw> pitti, :)
[10:44]  * ogra_ thought lag moved to linaro ...
[10:45] <ogra_> (oh, wait, he colletc cobras, not vipers)
[10:45] <ogra_> *collects
[12:15] <flexiondotorg> Laney or infinity Now I have PPU for some Ubuntu MATE packages, what does the SRU process look like?
[12:15] <flexiondotorg> Do I file an SRU and get a release team ack and then upload? Or can upload directly?
[12:17] <pitti> flexiondotorg: file an SRU bug and upload
[12:17] <flexiondotorg> pitti, So file SRU and then upload without ack?
[12:17] <pitti> flexiondotorg: yes, it'll be held in the unapproved queue anyway, where the sru team will review it
[12:18] <flexiondotorg> pitti, Thanks.
[13:42] <flexiondotorg> infinity, I tried upload ubuntu-mate-welcome to xenial for an SRU and I was rejected.
[13:45] <rbasak> flexiondotorg: when I first got upload rights, I discovered that packagesets are per-release. Which I agree is a pain :-/
[13:46] <rbasak> Unless there's some reason not to, it would make sense to add you to those packages for Xenial as well, since that's what we agreed. I don't know how though.
[13:46]  * rbasak should probably learn that.
[13:47] <flexiondotorg> rbasak, I was informed during the DMB meeting that the PPU would be applied to Xenial and Yakkety.
[13:47] <flexiondotorg> SO I can maintain Xenial.
[13:48] <rbasak> flexiondotorg: agreed, that's what I mean.
[14:50] <infinity> flexiondotorg: My bad, I haven't set up the packageset yet.  I'll get to that right after my morning meeting.
[14:51] <infinity> flexiondotorg: I'll ping you when it's done so you can try again.
[15:20] <bzoltan_> infinity: would you pleas re-trigget the autopkg test for this https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-047/excuses.html
[15:22] <flexiondotorg> infinity, Cheers.
[15:25] <infinity> pitti: Remind me of the syntax for nudging the non-archive autopkgtests? ^^
[15:27] <pitti> infinity: retry-autopkgtest-regressions --ci-train landing-047 -s vivid
[15:27] <pitti> infinity: that'll generate the commands to stdout
[15:29] <infinity> pitti: Shiny.
[15:29] <infinity> bzoltan_: Done.
[15:30] <bzoltan_> infinity:  thank you
[15:33] <slangasek> grah.  what is pulling ocl-icd into main?  seeded-in-ubuntu claims it's 'supported' and grep of the seeds disagrees
[15:38] <slangasek> oh. not in main, but in restricted, right
[15:39] <infinity> nvidia-opencl-icd-304 might belong in multiverse.
[15:39] <infinity> Oh, but nvidia-XXX recommends nvidia-opencl-icd-XXX
[15:40] <infinity> So that would need fixing if we wanted to demote.
[15:41] <ginggs> infinity, slangasek: we need the icd from nvidia, but the icd loader from ocl-icd
[15:41] <slangasek> infinity: I don't have a specific reason to demote, I was just being confused when analyzing unowned packages in "main" because restricted != main
[15:41] <infinity> ginggs: No one's questioning the package selection, just the supported status. :)
[15:42] <slangasek> though I see it's pulling more dependencies now
[15:42] <infinity> slangasek: Ahh, fair enough.
[15:42] <slangasek> (c-m, this morning)
[15:42] <infinity> slangasek: c-m could try to be a bit more clear about the non-free components, I suspect.
[15:42] <slangasek> infinity: and my local why-in-main script could be smarter ;)
[15:42] <infinity> (As could other tools)
[15:43] <slangasek> 'reverse-depends -c main src:ocl-icd' <nothing> Whhhhyyyyyyy
[15:43] <ginggs> infinity: sure, i just know that the naming of these packages is terrible and I've worked with them a bit, so i might be able to clarify what goes with what
[15:44] <infinity> slangasek: Maybe we should simplify your script by proposing a GR to drop non-free.
[15:44] <slangasek> infinity: I am submitting an amendment to this GR to replace the word "non-free" with "acid"
[15:45] <infinity> Duuuuuuuuuude.
[16:34] <infinity> flexiondotorg: Try that SRU upload again.
[16:51] <infinity> flexiondotorg: http://paste.ubuntu.com/16102589/ <-- Double-check that for me?  If it looks sane, I'll copy it forward to yakkety.
[16:53] <infinity> flexiondotorg: Looks like it matches your list, I just re-checked myself.  So, copying.
[16:54] <infinity> flexiondotorg: And done.
[18:14] <bzoltan_> folks, I got a little problem :) Vivid is removed from the http://cdimage.ubuntu.com/ubuntu-core/releases/
[18:15] <bzoltan_> but I still need a core image of Vivid
[18:15] <nacc> bzoltan_: why? vivid is EOL?
[18:16] <bzoltan_> nacc: I know, but the Ubuntu Phone is still based on Vivid
[18:16] <bzoltan_> nacc: and I need to create an SDK image for it, what is based on a core image
[18:17] <bzoltan_> is this any good? http://cdimage.ubuntu.com/ubuntu-core/vivid/daily-preinstalled/current/vivid-preinstalled-core-amd64.tar.gz
[18:19] <infinity> bzoltan_: Lemme slap vivid core on old-releases, that should sort you out.
[18:19] <nacc> bzoltan_: or maybe it's at: http://cdimage.ubuntu.com/ubuntu-touch/vivid/daily-preinstalled/ ?
[18:19] <bzoltan_> infinity: that would be great
[18:19] <nacc> (-touch rather -core)
[18:20] <bzoltan_> nacc:  good hint, I will try the touch too
[18:20] <infinity> bzoltan_: If you use the ubuntu-core tarball, the touch images won't be much use.
[18:21] <bzoltan_> infinity: I used to use the core image to patch it with all the SDK API and toolchain pckages.
[18:22] <infinity> bzoltan_: Yeah, sec.  Resurrecting.
[18:22] <infinity> http://old-releases.ubuntu.com/releases/vivid/
[18:22] <infinity> bzoltan_: ^
[18:22] <bzoltan_> infinity:  thank you!
[18:23]  * infinity notes upon seeing them in the same directory for the first time that his core naming is inconsistent with other products... Oops.
[19:14] <bzoltan_> infinity:  sorry to bug you with my problems today :) You might now apt better then me... How is it possible that a package fails to install due to a  strange dependency problem, but the dependency can indeed be installed ->http://pastebin.ubuntu.com/16118469/
[19:14] <bzoltan_> That happens when a developer tries to bootstrap a click chroot for the phone
[19:15] <bzoltan_> cjwatson: you might have some idea ^
[19:17] <nacc> bzoltan_: maybe try `apt-get install ubuntu-sdk-libs:armhf ubuntu-html5-container:armhf` as it might be further down the chain
[19:17] <nacc> that is the conflict is if it installed the latter, the former becomes uninstallable or something
[19:17] <nacc> bzoltan_: as you haven't yet installed the original package in that pastebin :)
[19:43] <infinity> bzoltan_: Indeed, as nacc suggests, try installing both together.
[20:03] <bzoltan_> infinity: nacc: no problem when I install both
[20:05] <nacc> bzoltan_: ok, it's hard to say what apt thought, can you get back to the original state (with the second package not installed)? and see if apt will let you specify both? not sure why it's happening otherwise
[21:46] <lamont> infinity: since you are my favoritest one.... can you help me understand how xenial has not come to live in http://changelogs.ubuntu.com/meta-release-lts
[21:48] <nacc> lamont: i assume it won't until 16.04.1
[21:48] <nacc> so as to avoid suggesting LTS -> LTS upgrades before then?
[21:48] <lamont> oh, right.
[21:49] <lamont> now all is clear... I'll just go crawl back into my corner and pretend I didn't forget that feature of LTS
[21:50] <lamont> and it's so sad that dapper never got a .1 :D
[21:50] <nacc> heh
[21:50] <ogra_> it had a .6 !
[21:50] <ogra_> (well, .06 technically)
[21:57] <pitti> see, not bigger than .1 :)


[02:14] <ahoneybun> lordievader: I've heard that all those GUI USB makers are broken
[06:03] <lordievader> Good morning.
[06:04] <lordievader> ahoneybun: Unetbootin works fine here for both efi and bios systems.
[10:05] <clivejo> anyone interested in this on ubuntu - https://lkubuntu.wordpress.com/2015/08/23/using-openlux-to-help-your-sleep-andor-relax-your-eyes-2/ ?
[13:04] <BluesKaj> Hiyas all
[14:06] <clivejo> anyone know what dep Im misisng to correct this error - CMake Error at /usr/share/cmake-3.2/Modules/FindX11.cmake:439 (message):
[14:06] <clivejo>   Could not find X11
[14:31] <lordievader> libx11-dev?
[14:40] <clivejo> yeah, found it thanks lordievader
[17:38] <soee> what way to reinstall kubuntu do you suggest ? USB images are not working
[18:18] <clivejo> soee: can you write a DVD with the iso?
[18:19] <clivejo> soee: have you check the ISO check sum, maybe the download got damaged?
[18:19] <soee> uh i have no any CD/DVD :D
[18:19] <soee> i do not remember when i used them last time
[18:19] <clivejo> is it an old system?
[18:19] <soee> nah, broken Wily
[18:20] <soee> anyway i will try install Vivid and jump from it to Wily
[18:20] <clivejo> what way is it broken?
[18:23] <ScottK> soee: I've not tried this with an Ubuntu image, but it definitely works with Debian ones (but be careful): https://www.debian.org/releases/jessie/amd64/ch04s03.html.en
[18:34] <ahoneybun> yofel: ping
[18:38] <clivejo> ovidiu-florin: do you program QT frontends?
[19:17] <soee> ok updating fresh Vivid to WIly :)
[19:18] <soee> had to create bootable usb from Windows using Universal USB installer
[19:19] <ScottK> soee: Did you try the Debian instructions I linked to?
[19:19] <soee> ScottK: ah didn't look at it
[19:20] <ScottK> K.  I'd be interested to know if that works for Ubuntu images or not.
[19:23] <soee> i will try it next time
[19:25] <valorie> clivejo: have you tried out redshift?
[19:25] <clivejo> nope
[19:25] <valorie> not starting properly in wily, but beyond that, works well
[19:26] <valorie> and is not high CPU intensive
[19:26] <valorie> !info redshift
[19:26] <clivejo> has wily a different arch?
[19:26] <valorie> we have a widget too, but unfortunately the widget doesn't depend on redshift itself, evidently
[19:26] <clivejo> openlux seems to not function in wily
[19:26]  * valorie filed a bug about it
[19:27] <valorie> !info redshift vivid
[19:27] <valorie> it's tiny, and Just Works
[19:27] <valorie> reminds me to put it back onto this box
[19:28] <valorie> woah, wants to restart once installed
[19:28] <valorie> that's a bit odd
[19:30] <clivejo> x is odd!
[19:35] <clivejo> cant get either to work in wily
[19:43] <valorie> yeah, I'm not sure why it doesn't want to start in wily
[19:49] <clivejo> I wonder is it the change to Wayland
[19:55] <valorie> we're not in wayland-land *yet*
[19:55] <valorie> afaik
[19:55] <valorie> that's still in testing
[19:56] <yofel> ahoneybun: pong
[19:56] <yofel> right, unless you're running kwin_wayland, you're not using wayland
[20:14] <soee> ok i have now fully working Wily :)
[20:14] <soee> is this new kmix widget already in archive?
[20:27] <ahoneybun> OMG my work from Akademy is in Plasma 5.4!
[20:27] <ahoneybun> this is awesome
[20:28] <clivejo> ahoneybun: what work?
[20:28] <ahoneybun> yofel: I just wanted some help to start on kdenlive :)
[20:28] <ahoneybun> clivejo: a high contrast color scheme for breeze
[20:34] <clivejo> congrats
[20:36] <ahoneybun> thanks
[20:36] <valorie> excellent, ahoneybun
[20:36] <valorie> wasn't it worth the worry and work to come to akademy?
[20:37] <valorie> :-)
[20:37] <ahoneybun> there was no worry valorie
[20:37] <ahoneybun> not tooooo much
[20:38] <valorie> ah, then you are braver than me
[20:39] <valorie> I always have a small pit of fear in my stomach going to a new place
[20:39] <valorie> I try to overcome it and go anyway
[20:40] <ahoneybun> just worry about my lagguage
[20:40] <ahoneybun> new places are great
[20:40] <valorie> eh, I just make sure that my absolute essentials are with me, and not checked
[20:40] <valorie> everything in my checked bags can be bought
[20:40] <valorie> yes, they are
[20:40] <ahoneybun> of course but we need clothes
[20:41] <ahoneybun> XD
[20:41] <valorie> but that doesn't stop the fear
[20:41] <valorie> it disappears once I have a homebase
[20:41] <yofel> well, at least you guys didn't fly with iberia, martin and matthias had fun.. stories to tell
[20:41] <ahoneybun> yea hostel and such
[20:42] <ahoneybun> yea
[20:42] <ahoneybun> nightmares
[20:42] <valorie> our plane to and from A Coruna were Iberia
[20:43] <valorie> I've learned you just take it one step at a time
[20:44] <valorie> slightly off-topic perhaps, but: has anyone else lost bash history in wily?
[20:44] <valorie> up-arrow has always been my best friend in the cli
[20:44] <valorie> and now it seems to simply not work
[20:44] <valorie> every session starts clean
[20:44] <yofel> is ~/.bash_history empty?
[20:45] <valorie> is this part of the "sessions not being saved" problem?
[20:45] <yofel> nah, bash manages its history itself.. maybe you just have keyboard input issues
[20:45] <yofel> and it's never recieving the up-arrow event
[20:46] <valorie> hmmm, cat ~/.bash_history gets "Permission denied"
[20:46] <yofel> you can also run 'history'
[20:46] <valorie> that sounds wrong
[20:46] <yofel> uh yeah, that's not right...
[20:47] <valorie> I can't recall running sudo when I shouldn't
[20:47] <yofel> should be owned by you and 600 for permissions
[20:48] <valorie> !chown
[20:49]  * clivejo waves at yofel
[20:50] <yofel> o/
[20:50] <clivejo> how are you today?
[20:53] <yofel> tried to take a break today and spend some time outside just to end up with a headache the whole evening.. not quite sure how I managed that
[20:56] <clivejo> is the weather very heavy?
[20:57] <valorie> I ran chown -R valorie:valorie ~/*
[20:57] <valorie> without result, which is good -- still can't access the bash_history though
[20:58] <valorie> on this computer, no problem
[20:58] <yofel> valorie: run it on ~/
[20:59] <yofel> otherwise it'll skip the hidden files
[21:00] <yofel> clivejo: not really, if anything it cooled down a bit lately. Which is great after weeks with almost up to 40°C
[21:00] <valorie> ok
[21:00] <clivejo> wow
[21:01] <clivejo> why cant we have some sun!
[21:01] <valorie> so, I guess I need to run that from sudo, because two files can't be changed: ~/.bash_history and ~/.dropbox-dist
[21:01] <clivejo> 14°C and raining here
[21:01] <valorie> probably why dropbox isn't running well on that computer
[21:01] <clivejo> huge floods this morning
[21:01] <yofel> where're you at?
[21:02] <clivejo> Ireland
[21:02] <valorie> jealous of rain!
[21:02] <yofel> ah, that's cold for summer o.O
[21:02] <yofel> but yeah, we have far too little rain here lately..
[21:02] <valorie> just more heat here, and smoke from the fires on the other side of the mountains
[21:02] <clivejo> its too cold, wet and windy for this time of the year
[21:02] <valorie> east of our state is burning up
[21:03] <clivejo> had a lovely BBQ in the rain on Friday evening
[21:03] <valorie> my husband just walked ahead of all those fires
[21:03] <yofel> heh, I did that once, it was fun anyway. If anything I had to wash my clothes twice to get the smoke smell out of them ^^
[21:03] <valorie> :(
[21:04] <clivejo> yofel: where are you?
[21:04] <yofel> usually from Stuttgart, currently in Berlin for work
[21:04] <yofel> (Germany)
[21:04] <clivejo> oh nice
[21:04] <clivejo> are you german born?
[21:04] <yofel> yeah, though my parents are from croatia
[21:05] <valorie> yay, now history works!
[21:05] <valorie> thanks, yofel
[21:05] <yofel> yw
[21:05] <valorie> I wonder how that got messed up though
[21:06] <clivejo> gremlins
[21:06] <yofel> maybe if you ran kdesudo konsole or so, I think that doesn't reset $HOME. Or something similiar
[21:08] <valorie> I can't imagine doing that, but I didn't do the initial install either
[21:09] <clivejo> yofel: did you look at any more of the 15.08.0 apps?
[21:10] <clivejo> hi soee
[21:10] <yofel> nope
[21:10] <clivejo> back on wily?
[21:10] <soee> clivejo: yes, almost all works fine :)
[21:10] <soee> haha :D to get plasma-pa widget working, plasmashell had to crash and restart -.-
[21:11] <clivejo> yofel: I cant figure out what is wrong with those cmake version problem ones
[21:11] <soee> self-repair in plasma is cool
[21:12] <soee> lamp-server^ install fails die to dependencies
[21:12] <yofel> I'm not quite sure either... I took a quick look at the findpkgconfig file, but I'm not expert at debugging cmake marcos so I didn't see anything
[21:13] <clivejo> did you do a diff on CMake 15.07.90 and 15.08.00 ?
[21:13] <clivejo> I wonder what changed
[21:13] <clivejo> cause 15.07.90 builds fine
[21:14] <yofel> built fine or still builds fine?
[21:14] <clivejo> it builds locally for me
[21:15] <yofel> hm, let me check git
[21:15] <clivejo> I was playing with okteta
[21:18] <yofel> there are no relevant changes in either okteta or kde-baseapps that I can see...
[21:23] <valorie> yay, got dropbox working on that lil box too
[21:25] <yofel> clivejo: meh, I should actually pay attention when reading the kde release team ML
[21:25] <yofel> https://git.reviewboard.kde.org/r/124801/
[21:26] <clivejo> how do we fix that?
[21:26] <clivejo> quilt patch?
[21:26] <yofel> http://www.cmake.org/gitweb?p=cmake.git;a=commitdiff;h=b9ec9392da21a3421e48c6961976060d872faffb
[21:26] <yofel> seems like the correct fix
[21:27] <clivejo> but how do we apply that?
[21:29] <yofel> hm, I have no upload rights for cmake, bummer
[21:30] <yofel> so, either ask jr tomorrow, or do it the classic way: file a bug against cmake on launchpad, apply patch to package, make a debdiff, attach that to bug, subscribe ~ubuntu-sponsors
[21:31] <clivejo> could we make a debian/patches/CMakeFix patch?
[21:33] <yofel> you can also cherry-pick the fixes in kde git, e.g. 8eb8cfcf1a37e96694e30294e0265f6bf0133323 would fix okular
[21:33] <yofel> maybe the less cumbersome way to fix this
[21:34] <clivejo> why did they do that?
[21:35] <yofel> do what?
[21:35] <clivejo> remove the CMake version?
[21:36] <yofel> uhm, dunno. it was a change in kdelibs, too lazy to dig the commit up now
[21:47]  * yofel off for the night, nini
[21:47] <clivejo> good night
[21:47] <valorie> sweet dreams, yofel


[05:38] <juancarlospaco> hi
[08:21] <mugshot> hello everybody
[08:22] <Myrtti> hi
[08:23] <mugshot> i have hard time trying to properly install matrox driver on ubuntu meerkat
[08:23] <rww> I suspect you want #ubuntu. This isn't a support channel :)
[08:25] <mugshot> searching the forum was like a vacuum vicious circle, i couldn't get anywhere
[08:26] <mugshot>  thanks for informing me
[13:29] <azad> hi to all
[13:29] <azad> i have problem with network manager
[13:29] <azad> any one can help me?
[13:33] <Myrtti> you're looking for #ubuntu, this isn't a support channel
[14:48] <azad> hi
[14:49] <Myrtti> hi
[14:50] <azad> any one here?????????????????????????????????
[14:50] <Myrtti> no, just you and the echo. Yes. there is.
[14:50] <charlie-tca> apparently, yes, since you were answered with a reponding "hi"
[14:51] <azad> :d
[14:51] <azad> i am very very bigginer
[14:51] <azad> sorry
[14:52] <azad> my network manager  disabled and disabled any connection
[14:52] <Myrtti> as I said earlier, this isn't the channel for support issues or for problem solving your Ubuntu installation. If you want that, you need to join #ubuntu, with writing "/join #ubuntu" without the quotes.
[14:52] <azad> wat can i doo?
[14:52] <k1l> azad: #ubuntu is the right channel. not this here: #ubuntu-irc
[14:52] <azad> ok very tnx
[14:55] <Myrtti> wohey
[14:56] <k1l> groundhog day :)
[14:57] <DJones> He's going to get eaten alive in #u
[14:59] <Myrtti> more likely to be ignored as he misuses the enter key


[07:27] <Noskcaj> If someone has the time to run me through some of iconview in glade that would be great
[10:19] <ochosi> Noskcaj: what info/hints are you looking for exactly?
[11:06] <bluesabre> hey all
[11:06] <bluesabre> I'll return to my regularly scheduled usefulness tonight
[11:06] <bluesabre> :D
[11:07] <knome> hey sean
[11:08] <knome> you ought to look at the new features of the tracker
[11:20] <ochosi> hey bluesabre
[11:20] <ochosi> hope you enjoyed your holidays
[12:03] <ochosi> knome, pleia2 (or anyone else in -team with proofreading skills): i just finished a brief artwork update on our LO integration work for 15.10 on x.org, would be great if you could review before i publish! thanks in advance
[12:03] <ochosi> http://xubuntu.org/?p=3269&preview=true
[12:05] <astraljava> I've been told I'm one of the nastiest nitpickers people have ever met, and they run their texts by me because of it. I could have a look in a few hours when I get home.
[12:09] <knome> ochosi, Xubuntu’s default “elementary-xfce”. -> Xubuntu's default icon theme elementary-xfce
[12:09] <ochosi> knome: sure, feel free to change that
[12:09] <knome> ochosi, and i guess generally try to be consistent with quotes or no quotes on theme names
[12:10] <knome> ochosi, then release the lock
[12:10] <ochosi> oh
[12:10] <ochosi> oops :)
[12:10] <astraljava> Ahh... knome is on it, so then I don't need to. :D
[12:10]  * ochosi releases lock
[12:15]  * knome did edits, feel free to double-check
[12:15] <knome> i changed the whole LO upstream sentence
[12:16] <knome> ochosi, what about something on how people can help?
[12:16] <knome> or who to contact
[12:16] <ochosi> yeah, could do
[12:16] <knome> not that i expect wonders, but still
[12:16] <knome> who knows
[12:17] <knome> also ping ping pleia2: we would likely prefer to have this on the news :)
[12:17] <knome> ochosi, we haven't used tags for projects before, do you want to start doing that now?
[12:17] <knome> ochosi, see the sidebar for the tags we have now
[12:18] <ochosi> yeah, dunno, i just felt i could add some, haven't put too much thought into the tags yet tbh
[12:18] <knome> ok
[12:18] <ochosi> i guess 15.10 is an ok tag
[12:18] <ochosi> not sure about the others
[12:18] <knome> i left Artwork
[12:18] <ochosi> alright
[12:18] <knome> we have tags like Marketing and QA
[12:18] <knome> so it might be ok to tag posts with "interest groups"
[12:19] <ochosi> right
[12:19] <knome> or in other words, subteams
[12:20] <knome> another option (that requires code change) is to create new taxonomies
[12:20] <knome> "release" and "team"
[12:20] <knome> then start tagging like mad men
[12:20] <knome> (pun intended)
[12:22] <knome> but to make it clear, the code change is pretty trivial
[12:22] <knome> but *shrug*
[12:22] <ochosi> yeah
[12:23]  * ochosi shrugs too
[12:23] <ochosi> ok, added a brief contribute-section
[12:23] <knome> i'm somwhat dissatisfied with this now
[12:23] <ochosi> with what?
[12:23] <knome> the tag issue
[12:23] <ochosi> oh
[12:23] <knome> maybe i'll add at least the releases taxonomy
[12:24] <knome> with some extra features
[12:24] <knome> like release and EOL date fields
[12:24]  * ochosi poked the bear
[12:24] <knome> could then even use that to create the list for supported releases on "Help & Support"
[12:24] <knome> nah, i've been thinking this for a long time
[12:24] <knome> +about
[12:28] <ochosi> right
[12:28] <ochosi> in that case i guess it's a good thing i tagged without thinking :D
[12:29] <knome> bah
[12:29] <knome> :P
[12:54] <knome> ok, got to pick up some groceries, bbl
[12:58] <ochosi> ttyl
[20:46] <knome> ochosi, poke?
[20:47] <pleia2> today is trying to kill me, but I can probably find time tomorrow or tonight to look if still needed
[20:47] <knome> look at what?
[20:47] <knome> the article?
[20:47] <knome> i did that already, don't worry too much about that
[20:47] <pleia2> ok
[20:48] <knome> pleia2, more goodness incoming: http://xstaging.lallinaho.fi/release/12-04/
[20:48] <pleia2> reminds me, should remove utopic from docs.x.o
[20:48] <knome> basically moving releases from tags to a "release" taxonomy
[20:48] <knome> with custom fields
[20:48] <knome> we can even build the "supported releases" list with this information
[20:48] <pleia2> tagging confounds me, good work
[20:49] <knome> so now we can use the tags for something else
[20:49] <knome> like
[20:49] <knome> this is what i do on my blog:
[20:49] <knome> all application names that are mentioned in the article -> tag
[20:49] <knome> all themes that are covered in the article -> tag
[20:50] <knome> also app names "Capitalized", themes "uncapitalized"
[20:50] <knome> http://open.knome.fi/?s=
[20:50] <knome> ^ makes most sense to me
[20:51] <pleia2> ok :)
[20:51] <knome> but we can do whatever we want
[20:51] <knome> mixing in releases there was the bad idea
[20:52] <knome> but since we didn't have this custom taxonomy...
[20:57] <ochosi> evening all
[20:58]  * ochosi pokes knome back
[20:58] <knome> ochosi, basically the url i posted to pleia
[20:58] <knome> +2
[20:58] <ochosi> pleia2: yeah, dont worry, just wanted another set of eyes
[20:58] <ochosi> knome: nice! i like it
[20:59] <knome> also see sidebar
[20:59] <knome> widget just arrived
[20:59] <ochosi> you mean the "object(stdClass)#296 (9) { ["term_id"]=> string(2) "25" ["name"]=> ..."
[20:59] <ochosi> ?
[20:59] <ochosi> :)
[20:59] <knome> refrehs :P
[20:59] <knome> refresh too
[20:59] <ochosi> nice
[20:59] <knome> so we can dump in the release codename, release and eol dates, and of course, a description
[21:00] <ochosi> sometimes i'm wondering whether we should use the per-release animal logos more
[21:00] <knome> so we can do a quick overview of the release if we want
[21:00] <ochosi> sounds lovely
[21:00] <knome> ..and then have a list of all articles linked to that release
[21:01] <ochosi> yeah
[21:01] <ochosi> so basically collecting all info of a single release in one (dynamic) place would be great
[21:01] <ochosi> incl links to docs for that release etc
[21:01] <knome> that's pretty much what i'm doing
[21:01] <knome> right...
[21:01] <knome> that's a different question, but yeah, it's doable
[21:02] <ochosi> yeah, i know, that could be the next step
[21:02] <ochosi> but let's go with the tagging mechanism you're working on there
[21:02] <knome> heh
[21:02] <ochosi> ;))
[21:03] <knome> well, as long as we name the release slugs in a standard way, we can resolve the docs link from there
[21:03] <knome> automatically, that is
[21:04] <knome> eg. the slug '15-04' can be easily converted to 'http://docs.xubuntu.org/1504/'
[21:04] <knome> do i need to tell you how to do that? (:
[21:04] <ochosi> what me? do i need to resolve the links now?
[21:04] <knome> hah.
[21:05]  * knome slaps ochosi
[21:06] <ochosi> ouch
[21:06]  * ochosi bleeds when people stab him
[21:06]  * ochosi feels pain when knome slaps him
[21:06] <knome> well good, that's the goal :P
[21:06] <knome> better example for archives http://xstaging.lallinaho.fi/release/14-04/
[21:07] <ochosi> nice
[21:07] <ochosi> yeah, that really makes sense to group our articles by release
[21:07] <knome> definitely
[21:07] <knome> we're doing that already
[21:07] <knome> just with tags
[21:07] <ochosi> (i mean the release-tagged ones at least)
[21:07] <knome> http://xubuntu.org/news/tag/14-04/
[21:08] <knome> but that isn't even close
[21:09] <knome> http://xstaging.lallinaho.fi/release/14-04/
[21:09] <knome> updated that with a description from wikipedia
[21:09] <knome> >:)
[21:10] <ochosi> :D
[21:10] <knome> i wonder if it would be better if the description was first
[21:10] <knome> opinion?
[21:11] <knome> maybe it was better the other way
[21:12] <ochosi> yeah
[21:12] <ochosi> well
[21:12] <ochosi> hmm
[21:12] <knome> heh
[21:12] <ochosi> to some extent both make sense
[21:12] <knome> now this feels too top-heavy
[21:13] <knome> or bottom
[21:13] <ochosi> but the EOL is really important for releases
[21:13] <knome> depending how you look at it
[21:13] <ochosi> yeah
[21:13] <knome> one thing i've been pondering is how to show the eol status
[21:13] <knome> eg. if it's EOL, should the date be in red?
[21:13] <knome> or appended with some notice?
[21:13] <knome> or both?
[21:16] <ochosi> yeah
[21:16] <knome> yeah to what?
[21:16] <ochosi> definitely should be highlighted
[21:16] <knome> stupid
[21:16] <knome> :P
[21:16] <ochosi> :)
[21:16] <ochosi> btw, any more comments on the LO article or can i pubish as is?
[21:16] <knome> pubish?
[21:16] <knome> HUH.
[21:16] <knome> PLEASE
[21:16] <ochosi> or publish
[21:16] <knome> no pubes on the website
[21:16] <ochosi> you decide
[21:16]  * knome checks quickly
[21:17] <ochosi> after all, you're the fancy web lead
[21:17] <knome> oh, i'm now fancy?
[21:17] <ochosi> the web lead position is
[21:17] <ochosi> so you holding that position makes you fancy too, i guess
[21:18] <knome> i'm so flattered now, simon.
[21:18] <knome> anyway, i fixed a few pubish errors
[21:18] <ochosi> why am i not surprised?
[21:18] <knome> you're good to go now
[21:19] <ochosi> good good, i'm a go-er, ya know ;)
[21:19] <knome> yeah i do
[21:19] <knome> there's no doubt about it - your partner is pregnant
[21:20] <knome> heh @ wikipedia:
[21:20] <knome> There will also be a new version of Xubuntu "Core" starting from Xubuntu 15.10. Developers have speculated that it will fit in regular CDs.[citation needed]
[21:20] <knome> yeah...
[21:20] <knome> who has "speculated" with that?
[21:20] <knome> CONFESS!
[21:20] <ochosi> haha
[21:20] <ochosi> gotta love wikipedia
[21:21] <knome> now somebody will surely make a mention there that the developers do not care for their users because they only joke about their wikipedia edits
[21:22] <knome> especially that fancy web lead
[21:22] <ochosi> definitely
[21:22] <ochosi> and it's teh truth!
[21:22] <knome> citation: Pasi Lallinaho, Xubuntu Web Lead
[21:22] <knome> ^ obviously fake, we have no "Web Lead"
[21:23] <ochosi> who's that pasi guy?
[21:23] <knome> don't know
[21:23] <knome> but i've heard he's damn fancy
[21:24] <knome> and a go-er
[21:24] <knome> fwiw
[21:24] <ochosi> indeed, wears strange clothes, talks "the fancy talk" he himself invented and constantly references the pythons and m.a.numminen
[21:25] <knome> and sports a minimalist designer wallet, i've heard
[21:26] <knome> ochosi, i just checked our status tracker and saw you haven't scheduled our next meeting
[21:26] <knome> <:
[21:26] <ochosi> haha, yeah, had to publish that article first ;)
[21:26] <ochosi> but will do that now
[21:26] <knome> hard work, that
[21:26]  * ochosi schedules time for scheduling the next meeting
[21:26] <knome> pubishing :P
[21:27] <ochosi> yeah, i hear they build houses just for that!
[21:27] <knome> hah
[21:27] <knome> anyway
[21:27] <knome> something else i need to figure out
[21:27] <knome> is how to separate articles on the blog better
[21:27] <knome> it looks clunky now
[21:27] <knome> the problem is
[21:27] <knome> i've never really sorted that problem
[21:27] <knome> except by only showing one article at a time
[21:28] <knome> maybe it just needs more space in between
[21:28] <ochosi> humm
[21:28] <ochosi> right now there's so little space in between
[21:28] <knome> yeah
[21:28] <ochosi> i mean basically almost no visible separation at all
[21:28] <knome> i have a mixed group of updates for the theme incoming
[21:28] <knome> some from way back
[21:28] <knome> so, meh
[21:28] <knome> need to pull the strings together
[21:29] <knome> maybe i need to do the other things first
[21:29] <knome> then the release stuff
[21:29] <knome> that's fortunately still relatively easily kept separate
[21:29] <ochosi> right, take your time
[21:29] <ochosi> i'll meanwhile figure out a good meeting time
[21:29] <knome> i will, i just hate this process
[21:29] <ochosi> brb
[21:29] <knome> lol
[21:29] <knome> have fun scheduling
[22:00] <knome> huh, ok, worst bunch of work done and stuff in the repository
[22:30] <bluesabre> good evening al
[22:30] <bluesabre> l
[22:30] <bluesabre> and al and all
[22:30] <ochosi> hey al!
[22:30] <bluesabre> :D
[22:30] <ochosi> nice of you to stop by
[22:30] <bluesabre> heya ochosi
[22:30] <ochosi> looking forward to the burndown looking more optimistic after tonight ;D
[22:31] <bluesabre> or tomorrow night
[22:31] <bluesabre> going to work on it tonight though
[22:31] <bluesabre> but not feeling too great
[22:31] <ochosi> oh
[22:32] <ochosi> sorry to hear
[22:32] <ochosi> first day at work after holidays is rarely fun though
[22:32] <bluesabre> a few days out, and plenty to do when I get back :)
[22:33] <ochosi> yeah
[22:33] <knome> hey bluesabre
[22:33] <bluesabre> hey knome
[22:34] <knome> ochosi, i think the burndown chart looks much better than a few days ago
[22:34] <knome> (pun intended and obvious)
[22:34] <bluesabre> xstatus is looking quite good
[22:35] <bluesabre> so does the burndown burn itself down as you complete tasks improving the actual burndown chart? :D
[22:36] <ochosi> knome: hehe, indeed
[23:27] <pleia2> looks like only G+ updated so far with new article?
[23:27] <pleia2> I'll do fb and twitter
[23:27] <knome> oh, ok
[23:27] <knome> :)
[23:28] <pleia2> knome: or you can do twitter if you want
[23:28]  * pleia2 writes words for fb
[23:28] <knome> can do that
[23:29] <knome> tweeted
[23:29] <pleia2> ty
[23:45] <krytarik> slickymaster, knome: This fixes all the current targets of the docs: http://paste.openstack.org/show/tMcOyxWCYEhyXy5oULhz/
[23:47] <knome> krytarik, erm, you sure that's done against the latest docs branch?
[23:48] <krytarik> Yep.
[23:48] <knome> oh pop
[23:48] <knome> *poop
[23:49] <knome> krytarik, please rediff
[23:50] <knome> krytarik, i just pushed your changes from last time
[23:50] <krytarik> Meh.
[23:52] <knome> well, you aren't willing to do MP's, so you'd better give us the diff in some other way we fancy it.
[23:53] <krytarik> knome: Thought you hadn't decided on that one yet though, and since it was all in a bunch...
[23:54] <knome> no, i just forgot to push it basically
[23:54] <krytarik> Alright then.
[23:55] <krytarik> Give me a min.
[23:55] <knome> MPs are nice because there's history and real commit log
[23:55] <knome> sure, i'm watching a dvd...
[23:55] <krytarik> lol


[14:52] <ceed^> I see that 17.04 comes with Unity 8. If I update from 16.10 will I just have Unity 8? How compatible is Unity 8 with themes, icon packs and indicators?
[14:53] <k1l> ceed^: not as default desktop
[14:54] <k1l> 16.10 did already included a preview that can be used
[15:02] <ceed^> k1l, That preveiw was pretty awful. I hope it is better in 17.04 :)
[15:03] <k1l> ceed^: "preview" :)
[15:19] <ceed^> k1l, bad as preveiw even :)
[15:21] <hanshenrik> will it be an LTS?
[15:23] <hanshenrik> hmm, nope doesnt seem so ^^
[15:23] <k1l> hanshenrik: no
[15:23] <k1l> 14.04,16.04,18.04,.. every second year there is a LTS
[15:24] <ceed^> I always get the releases early. Kinda enjoy the breakage since Ubuntu is so stable most of the time. Can't decide when to jump on 17.04 though.
[18:07] <Volkodav> I have this issue with lowriter javaldx: Could not find a Java Runtime Environment!
[18:08] <Volkodav> then the warning and it crashes Warning: failed to read path from javaldx
[18:11] <Volkodav> and this one with thunderbird http://paste.ubuntu.com/24002229/


[14:35] <yano> https://encrypted.google.com/search?hl=en&q=twitter.com%20columbus%2C%20ohio
[14:35] <jenni> [ twitter.comcolumbus,ohio - Google Search ] - https://j.mp/1SAzX0l
[17:49] <yano> http://www.13abc.com/home/headlines/Multiple-shootings-reported-in-Southern-Ohio--376752961.html
[17:49] <jenni> [ Multiple shootings reported in Southern Ohio ] - https://j.mp/1SzecuP
[19:08] <yano> https://u.osu.edu/w8lt/
[19:08] <jenni> [ W8LT - Amateur Radio Club at Ohio State University | Student Organization for Amateur Radio Operators ] - https://u.osu.edu