[01:34] <lifeless> sssss
[01:52] <litwol> Hello. Is there a way in bzr to find out what will be updated if i execue 'bzr update' command ? similar to 'svn status -u'
[02:34] <spiv> litwol: hmm, not that I know of.  It probably ought to have a --dry-run or --preview option (like 'bzr commit' and 'bzr merge' do, respectively).
[02:34] <spiv> litwol: file a bug?
[02:49] <lifeless> hi poolie
[03:14] <twisted_steel> what is the option to package all files from a repository into a tar.gz? I did it 6 months ago, but can't find it any more
[03:14] <lifeless> bzr export foo.tar.gz
[03:14] <twisted_steel> ahh, export.  thank you
[05:23] <pattern> i interrupted bzr in the middle of a commit... is there a chance of its database getting corrupted?
[05:31] <Peng> pattern: Perhaps if you're using an extremely old disk format. But otherwise no.
[05:33] <pattern> cool
[05:33] <pattern> thanks
[07:36] <vila> spiv: ping
[07:36] <vila> hi all ! :)
[08:47] <Anteru> Hi
[09:25] <gerard_> sooooooo
[09:25] <gerard_> when is this bug going to be fixed? https://bugs.launchpad.net/bzr/+bug/113809
[09:25] <gerard_> the attached patch looks good to me (though I have only little experience with the internal workings of bzr)
[09:26] <gerard_> gogo bazaar devs
[09:26] <gerard_> I love the rest of bazaar but this just plain sucks
[09:28] <gerard_> that bug is a duplicate of a lot of other bugs btw
[09:28] <gerard_> those really should be marked that way
[09:29] <spiv> gerard_: huh, there's a patch that was partially approved that disappeared.
[09:33] <spiv> gerard_: I just poked vila, the patch pilot this week, by email to suggest he take a look.
[09:33] <gerard_> thx
[09:34] <gerard_> my boss already finds bazaar a little scary, no need to keep bugs like this around
[09:36] <vila> spiv, gerard_ : I'll have a look at it but it seems to require more work, it was reviewed 'Needs_fixing' not 'Approved'
[09:36] <vila> spiv: are you around or not really ?
[09:54] <gerard_> vila: is there any reason noted why it needs fixing?
[09:55] <vila> https://code.edge.launchpad.net/~craighewetson/bzr/update_with_local_commit/+merge/10320
[09:55] <spiv> vila: not really, but I may glance at IRC from time to time...
[09:56] <vila> spiv: ok, how about a few questions of the per-file merge hook ? There are two points that compromise the landing: 1) repeated access to the config, 2) license for the cachedproperty
[09:57] <vila> spiv: you're away until thursfay (at least) right ?
[09:57] <vila> surfday, yes, *Thursday* damn it
[10:01] <gerard_> vila: ah, so it needs some minor changes?
[10:01] <gerard_> I could make those later this week
[10:01] <gerard_> I've already written a testcase for it anyway
[10:02] <gerard_> I think I also have a better error message
[10:03] <vila> gerard_: good, I'll look into it then, the weird thing is that the merge proposal is marked as 'Merged'...
[10:03] <spiv> vila: for 1, make the plugin store it on the hook params, e.g. "val = getattr(params, 'news_merge_files, None); if val is None: ..."
[10:03] <spiv> vila: for 2, someone needs to ask an LP person about it
[10:04] <spiv> vila: it's not "crown jewels" code so I doubt there will be any issue, but it might take time to find the right person and get them to say "ok".
[10:04] <vila> spiv: 1) ! of course, I thought about caching it but didn't think about letting the plugin do it
[10:04] <vila> 2) But why do you think your first version was bogus ? I didn't *test* it properly but..
[10:05] <spiv> vila: probably flacoste or maybe even ask jml
[10:05] <spiv> vila: the cache was global, not per instance
[10:05] <vila> global ? A local variable ? What makes you think so ?
[10:06] <spiv> (Two different definitions that used @cachedproperty would have their own cache, but not two instances of a class)
[10:06] <vila> ha, yes
[10:06] <vila> hmm, still, I preferred your lighter version :-/
[10:06] <spiv> vila: try "class C(object): def __init__(self, x): self.x = x; @cachedproperty; def y(self): return x**2", then "print C(1).y, C(2).y"
[10:07] <spiv> vila: so, FWIW, I read through the LP version and I think it's good and correct
[10:07] <spiv> vila: and as short as it can reasonably be while being as featureful and clear as it is.
[10:08] <vila> spiv: ok, I'll look into it and try to get an approval for the additional diff (time to use that pre-requisite parameter again :)
[10:16] <vila> gerard_: weirder, it seems that the original branch has been replaced with bzr.dev, lp shows an *empty* diff so I don't even know where the code is right now, I'll ping craig in the mp about it
[10:18] <gerard_> vila: :o
[10:19] <vila> gerard_: That's the first time I see such a weird thing...
[11:48] <cjwatson> so, the new 'bzr rebase-foreign' command sounds like exactly what I've been after for a while.  However, when I run it (in a checkout of lp:~ubuntu-cdimage/debian-cd/ubuntu, with NEW_BASE pointing to a checkout of lp:debian-cd) it just says "Nothing to do."  Am I doing something wrong?
[11:48] <cjwatson> is it possible that bzr-rewrite can only deal with branches imported using things like bzr-svn, not cscvs?
[11:49] <cjwatson> I wouldn't mind (all that much) having to generate a map for it matching up old and new revision ids, if I knew how ...
[12:36] <swathanthran> can i some how know how much data i would be downloading, before doing a bzr update?
[12:36]  * swathanthran wanted to update his emacs trunk.
[12:56] <maxb> swathanthran: I don't think such support exists.
[13:08] <vila> cjwatson: I don't think there are constraints on the branches except for some common ancestry and the fact that the revisions you want to rebase are not already part of the branch you're targetting, but I confess no experience with rebase-foreign
[13:12] <maxb> cjwatson: I think the problem is that your branches don't match one of the preexisting matcher algorithms written into the plugin. Some custom hackery is probably needed. Especially as there seems to be an off-by-one relationship in revision numbers and arch patch-X numbers between the two branches.
[13:20] <cjwatson> maxb: indeed, base-0 would translate to r1 in bzr-speak, patch-1 to r2, etc.
[13:20] <maxb> Not quite what I meant - both of your branches have arch-derived revids, but base-0 in one is patch-1 in the other
[13:32] <Morbus> g'day, i'm trying to tweak the bzr emailer.py to get the branch nick into the subject line.
[13:32] <Morbus> so, since branch is added to self in the init, i was hoping to add self.branch to the subject() function.
[13:32] <Morbus> but, i'm not sure how to get the branch *nick* - i'm not a python coder.
[13:33] <Morbus> is it just magically branch.nick? ;)
[13:33] <Morbus> self.branch.nick, rather.
[13:33] <maxb> try it and see? (I think it is)
[13:34] <Morbus> yeah, i had just tried it, but intro'd a syntax error somewhere else and panicked ;)
[13:34]  * Morbus is trying again.
[13:34] <vila> it is, but where did you find an emailer.py ?
[13:34] <Morbus> bzr: ERROR: Server sent an unexpected error: ('error', 'not all arguments converted during string formatting')
[13:34] <Morbus> https://launchpad.net/bzr-email/trunk
[13:35] <Morbus> also linked from the bzr plugin handbook guide thingy.
[13:35] <vila> yeah the plugin, found it fater asking ;)
[13:35] <vila> err, after
[13:35] <Morbus>    def subject(self):
[13:35] <Morbus>         return ("[bzr] [%s] r%d - %s" %
[13:35] <Morbus>                 (self.branch.nick,
[13:35] <Morbus>                  self.revno,
[13:35] <Morbus> is the start of my revised subject line.
[13:35] <Morbus> and is giving the above error.
[13:35] <Morbus> on commit.
[13:36] <vila> the error means that you have more arguments than mentioned in the format,
[13:36] <Morbus> ah, tht's true.
[13:36] <vila> Use paste.ubuntu.com instead of pasting here
[13:36] <Morbus> i left the url in cos i didn't want to delete it.
[13:36] <Morbus> thought extra args would just be ignored.
[13:37] <vila> Morbus: ha, coming from C ? ;-)
[13:37] <Morbus> nah, php/perl.
[13:37] <Morbus> i don't even know if it works over there, honestly ;)
[13:38] <Morbus> welp, no errors that time.
[13:38] <Morbus> now just have to wait for the email.
[13:38] <Morbus> :D
[13:38] <vila> Morbus: congratulations !
[13:38] <Morbus> i'm surprised emailer isn't being regularly updated.
[13:39] <vila> Morbus: bzr core is, I'm pretty sure almost all of emailer.py should be deprecated and use the core version instead but nobody found the time to do that so far
[13:39] <Morbus> vila: wait, there's a core version?
[13:39] <Morbus> since when?
[13:39] <Morbus> i just set this up a few months ago.
[13:40] <vila> Morbus: well, smtp_connection is part of core, I'm sure about that. There are certainly features of bzr-email that are not, I just don't know exactly which
[13:40] <maxb> cjwatson: I hacked it to guess the relationship between your revids, and it rebased 395 revisions, but then it exploded with an AssertionError when it first hit a merge in the ubuntu branch. I'm afraid I'm out of time to look at it today. :-/
[13:41] <Morbus> vila: ah.
[13:47] <Morbus> email came through. self.branch.nick works fine. thanks much.
[13:48] <cjwatson> maxb: *nod*, thanks for looking
[13:53] <swathanthran> ok.. i used http://bzr.savannah.gnu.org/r/emacs/trunk/ to do the initial checkout last week.. now it looks like that trunk is blank but latest revision is seen on lp how can i change the url of bzr update?
[13:59] <cjwatson> swathanthran: you mean blank as seen in a web browser?
[14:02] <vila> swathanthran: what does 'bzr  log -l5 http://bzr.savannah.gnu.org/r/emacs/trunk' says ?
[14:05] <swathanthran> when i do bzr update it says uptodate upto revision 99318. but launchpad has it up to 99375
[14:05] <swathanthran> bzr log -l5 shows only upto 2010-01-13
[14:05] <vila> swathanthran: so the trunk is not blank, good.
[14:06] <vila> Now you have to decide which branch you want to track. Is the lp one supposed to be a mirror of the savannah one ?
[14:06] <swathanthran> oh sorry i forgot to add the link:)
[14:07] <rubbs> swathanthran: do you have a branch or checkout?
[14:07] <swathanthran> ok.. i have a checkout of trunk and i want to update trunk..
[14:07] <swathanthran> bzr log -l5 http://bzr.savannah.gnu.org/r/emacs/trunk shows it upto 19 itself.. so the branch don't have a problem..
[14:08] <swathanthran> terribly sorry i have to go out now..
[14:08] <rubbs> oh. ok. I'll keep thinking
[14:09] <lornajane> apparently my branches have diverged.  That doesn't sound good to me
[14:10] <vila> lornajane: 'bzr missing' should display the differences
[14:10] <rubbs> diverged branches mean that you have a branch and someone else has a branch and that you both want to push to the tree. The other person(s) have already pushed
[14:10] <rubbs> you have to do a merge to make yours work
[14:10] <lornajane> yes, I've been offline for a few days
[14:11] <lornajane> I have a lot of local commits and the rest of the team have been working too
[14:11] <lornajane> this is exactly why I use bzr-svn :)
[14:11] <lornajane> its just that I've only just started and I'm confused.  Your explanation doesn't sound like its broken though, so I'll try the missing thing and see what happens
[14:11] <lornajane> The bzr error message about the diverged branches was very friendly and helpful
[14:12] <rubbs> good to hear.
[14:14] <rubbs> lornajane: http://doc.bazaar.canonical.com/bzr.2.0/en/tutorials/tutorial.html?#merging-from-related-branches that might help a little too
[14:14] <lornajane> rubbs: thanks!  I'll look
[14:14] <rubbs> np
[14:15] <lornajane> I expected it to just update and either merge it or conflict
[14:17] <rubbs> bzr tries to do the safest thing when possible. It wants you to merge it explicitly because a merge in the background could throw some things off.
[14:17] <rubbs> it's safer to just tell you that the branches are now diverged and let you know that you have to merge them.
[14:18] <toytoy> guys, anyone have successfully installed bazaar in eclipse?
[14:19] <toytoy> rubbs, are you talking to me?
[14:19] <lornajane> rubbs: makes sense once you know that's what's happening
[14:19] <toytoy> ah no, sorry
[14:20] <rubbs> toytoy: heh. no problem.
[14:20] <rubbs> lornajane: good. We try to make it less complicated
[14:20] <rubbs> toytoy: I haven't played with eclipse in a long while.
[14:20] <rubbs> toytoy: are you looking for full integration?
[14:21] <rubbs> or just looking for bzr to be separate?
[14:30] <toytoy> rubbs: yeah, somewhat like cvs feature in eclipse. that is cool! I want something like that for bazaar. is there any?
[14:31] <rubbs> as far as I know, there is, but it takes some setting up. I'll see if I can find the docs again.
[14:32] <lornajane> I don't think I understand the workflow of this :(  So normally I just pull changes
[14:33] <lornajane> my branches had diverged, which is fine
[14:33] <lornajane> so I merged, I got a conflict, I resolved that and marked it as resolved
[14:33] <lornajane> now I'm confused by two things
[14:33] <lornajane> one: stuff that is coming in is showing as local changes in my working directory
[14:34] <lornajane> two: I have a pending merge tip, no idea what that is or what I should do about it
[14:34] <lornajane> should I be RTFMing? I can't quite see how this process is going to work
[14:35] <rubbs> toytoy: http://wiki.bazaar.canonical.com/BzrEclipse/Installation
[14:35] <toytoy> okay rubbs, I found one but yeah it doesn't work perhaps i need to do more. I got this error bzr: Error: no such option: --short
[14:35] <toytoy> do you know that one? yeah that's the one i'm installing, indeed
[14:36] <rubbs> toytoy: I'm not sure if bzreclipse is still in active development. I'm not sure if anyone else knows more. I know it has been done before, I just can't find out where.
[14:37] <rubbs> lornajane: problem one: My guess is you have one branch, and you merged in your changes from the trunk correct?
[14:38] <lornajane> rubbs: correct
[14:39] <rubbs> lornajane: if that is the case, then that is the reason your trunk looks like the "local" branch. When doing a merge, the place you are merging is on the left side. The place you are getting the merge from (i.e. the trunk) is always on the right. There is a way to get around this...
[14:40] <rubbs> lornajane: you actually need two branches in this case (if you always want to make the trunk on the left). One branch will be your branch you have now. and the other branch will be a Mirror of the trunk.
[14:40] <rubbs> so you would have to create a branch from the trunk. cd into that mirrored branch, and then merge in the changes from your original branch.
[14:41] <rubbs> then you can push your mirrored branch back to the trunk.
[14:41] <rubbs> does this make sense so far?
[14:42] <rubbs> it's a little complicated, but once you get it, it kind of make sense
[14:43] <rubbs> you want a "mirror" of your trunk, and a "working branch." Once you are done with your working branch, you merge them into your "mirror" and then push from the mirror. Your working branch can then be updated.
[14:44] <lornajane> I *think* I understand :)
[14:44] <rubbs> for problem two it's a little more simple
[14:45] <rubbs> bzr doesn't automatically commit after all the conflicts are marked resolve (or for any merge for that matter). To finish your merge you have to do a commit. I usually just say "merging in xxx branch" in the message.
[14:46] <lornajane> right
[14:48] <rubbs> the pending merge tip is just telling you that in this commit the merge will take the two "tips" or "heads" and merge them to one.
[14:49] <rubbs> I might raise a bug about how best to set up a workflow for people in your situation. We've had a few people with similar problems before.
[14:53] <lornajane> rubbs: even a picture I think would help.  I am confident with SVN and I can't be the only person moving over
[14:54] <rubbs> I think I'm gonna work on that now. I'm working on a "google doc" that will be really basic, but at least it's something.
[14:54] <rubbs> I'll show it to you in a few minutes.
[14:54] <rubbs> after I show you I'll work on polishing it up.
[14:55] <lornajane> rubbs: sounds great :)  I hope I'm not making work for you!
[14:56] <rubbs> lornajane: not at all! your distracting me from work I really don't want to do (I've been searching for a reason to procrastinate all morning ;) ) and I have plenty of time to get it done
[15:01] <lornajane> so, I'm definitely making progress, but I'm sort of confused on what to do next
[15:03] <lornajane> I have updated and put my branch changes into my trunk.  Now I want to push the commits I made back to subversion (I used bzr-svn to check out).  Can I send the commits as they were done locally or can it only be a monster commit?
[15:06] <rubbs> lornajane: you know, I'm not entirely sure (I've done very little bzr-svn work myself)
[15:07] <lornajane> rubbs: hehe, maybe I'll improvise and then blog about it.  I can clean up in SVN if I have to
[15:07] <rubbs> I'm sorry.
[15:07] <vish> hi.. how to do a merge in lp? ken Accepted the merge , but he isnt sure how to do it...  ;)  https://code.launchpad.net/~vish.../ubuntu/lucid/human-theme/bug507632+bug495644/+merge/17538
[15:07] <vish>  do i set the status to "merged" or... does  he have to do it?
[15:09] <rubbs> vish: whoever has write access to that particular branch can do it. They do it by pulling from the trunk (mirror whats on lp) and then merge in the changes from your trunk (off of lp) and then push the result to the lp trunk.  At least I'm pretty sure that's what will work. It's been a while for me to be honest.
[15:10] <vish> ah , i thought so too.. :(
[15:11] <vish> but it seems a waste of bandwidth ;p  if the user has changed only one line of a huge branch , the author has to fully download the merge branch too :s
[15:11] <rubbs> no... they don't actaully
[15:11] <rubbs> if they just use the lp: shortcuts, it only will download the changes
[15:11] <rubbs> so you only need a mirror of the trunk.
[15:12] <rubbs> using ssh+bzr will keep the bandwidth down to a minimum
[15:12] <rubbs> so in the trunk the command would be "bzr merge lp:branch-to-merge-from" and then once that's all done "bzr push lp:trunk"
[15:12] <rubbs> er by in the trunk I meant in the mirror of the trunk
[15:13] <vish> rubbs: ah.. ok thanks :)
[15:13] <rubbs> np
[15:17]  * cjwatson typos 'bzr blog'.  Hmm.
[15:19] <Kinnison> hmmmmm indeed
[15:19]  * Kinnison ruffles cjwatson
[15:19] <cjwatson> LTNS!
[15:20] <cjwatson> jam: thanks so much for the fix for bug 494269.  I find the notion of being able to change the tree root rather magical ...
[15:21] <maxb> ooh
[15:21] <jam> cjwatson: yeah, I think there are still some paths that don't get it right, but at least more of them are working now
[15:21] <vila> cjwatson: try lp:bzr-guess :-D
[15:21]  * maxb should retest
[15:21] <vila> morning jam !
[15:21] <jam> morning vila
[15:22] <maxb> I managed to get some WTs into an entertaining state by pull --overwrite-ing and unrelated branch
[15:22] <cjwatson> vila: hah
[15:22] <Kinnison> vila: ooh handy
[15:22]  * Kinnison installs
[15:22] <vila> jam: just a quick check from patch pilot to patch pilot :) Do you still take care of the ignore-exception mp and the 392428 one ?
[15:23] <vila> bialix: any news about gary ? I don't remember seeing him here these days...
[15:24] <bialix> hi vila, jam, et al
[15:24] <bialix> vila: I've chatted with him last night
[15:24] <cjwatson> jam: merge-package (lp:ubuntu/vim <- lp:debian/vim) is mostly working now, but I'm getting a load of "Conflict adding files to Contents.  Moved to root."  What do those mean?
[15:24] <bialix> Gary made qbzr 0.14.6 release last night
[15:24] <cjwatson> Contents being an actual file in the vim tree
[15:24] <vila> bialix: ok, I'll ping him from lp about his unicode-bom-detect mp then
[15:25] <bialix> unicode? do you have a link?
[15:26] <vila> https://code.edge.launchpad.net/~garyvdm/bzr/unicode_bom_detect/+merge/17076
[15:27] <bialix> thx
[15:28] <bialix> interesting
[15:29] <vila> bialix: Yeah, what did you expect from Gary ? :-D
[15:29] <bialix> me? anything!
[15:31] <vila> hehe
[15:38] <lornajane> I'm reading some instructions here http://www.szakmeister.net/blog/2009/oct/12/bazaar-subversion-super-client/ which suggest I want to merge to the repository rather than pushing.  Does anyone have any thoughts on that?  I'm using bzr-svn and I want to push changes on my trunk back to subversion
[15:41] <rubbs> lornajane: not sure about what you just posted, I'd have to read it. but I finished my very rough slide presentation.
[15:41] <rubbs> here it is: http://docs.google.com/present/view?id=dhc4j5xm_90gr8227ch
[15:42] <rubbs> if the current directory marker is in open space that means the directory just above the branch directories.
[15:44] <rubbs> opps just realized that my permissions on that file were a little too tight. if you had trouble you should be able to view it now
[15:45] <lornajane> I can see it
[15:45] <lornajane> that's a good description of what I was doing with the simple changes
[15:46] <rubbs> ok, cool. I'm also reading the article you posted above.
[15:51] <rubbs> lornajane: the article correct, you want to merge into the mainline, but they mean the mirror of the mainline (I think). That means that your mirror on your computer should *always* be treated as if it were the subersion server. That way you always get your history right. Once you have checked that it's correct, you can then push up to the server.
[15:51] <lornajane> rubbs: but will my many commits to there be many commits to SVN or just one?
[15:52] <rubbs> just one. if you want to do many commits you need to look at rebasing.
[15:52] <lornajane> meh, I thought this was going to be much easier :)
[15:52] <rubbs> that article seems to have a section on it
[15:53] <rubbs> rebasing "rewrites history" so that all your commits look like they came from the latest revision instead of an old one (which is what is happeing with yours)
[15:53] <rubbs> that way you can then push up to the main branch and it will all look like your commits came from the tip. and you will get all your commits as little ones rather than as one big one
[15:53] <lornajane> that sounds promising
[15:53] <rubbs> it's a flaw with svn in that it doesn't keep merged history
[15:54] <lornajane> I'm hoping this will get easier/quicker as I get used to it
[15:54] <rubbs> that's why a merge in svn will look like one big commit.
[15:54] <lornajane> I've spent half my afternoon wondering how to update and commit :)
[15:54] <rubbs> lornajane: I don't use svn that much anymore but this will get easier with a little practice. most of it isn't that time consuming, just a little bit of work in the begining
[15:54] <rubbs> once you get a workflow that works, it's pretty easy
[15:55] <rubbs>  < lornajane> I've spent half my afternoon wondering how to update and commit :)
[15:55] <rubbs> ^^ been there before
[15:57] <jam> cjwatson: my best guess is that the same file exists in both branches but with a different file-id, so we get a conflict and have to put the files side-by-side
[15:58] <lornajane> rubbs: yes I'm sure I've been here before too :)  I'll always be using central SVN repos but I love having bzr functionality on my working copy, if I can figure this out its going to be excellent
[16:02] <rubbs> lornajane: I think it will work out for you. If you have more questions, just let us know. We'll try to help you out.
[16:05] <lornajane> rubbs: this channel has been great so far - and the community is the main reason I'm persevering with this rather than following the crowd in my sector to git
[16:06] <cjwatson> jam: that was my first guess, but there are no .moved files or similar in the working tree
[16:06] <jam> cjwatson: the other possibility is the root id issue. In that in one tree it looks like Contents should be in '' with root id X, and in the other tree it looks like it should be in '' with root id Y. And root id Y isn't present in the first tree, so it seems like a conflict
[16:07] <jam> (root ids are mostly allowed so that you can do stuff like join by reference or join by value, and have things show up in the appropriate subdir)
[16:07] <rubbs> lornajane: I use git a little too (for work) it's not bad. Their community has worked well for me. For me though... bzr-svn had a few less problems than git-svn and a whole lot less problems than hg-svn. That and bzr makes it easy to contribute back to them ;)
[16:07] <jam> it wasn't really intended that the *same* project should get 2 root ids
[16:07] <jam> however, people did 'bzr init' 2x, rather than 'bzr init + bzr branch'
[16:07] <jam> etc
[16:07] <jam> especially with the udd stuff
[16:08] <cjwatson> jam: right.  It's a bit of an incomprehensible message though - what am I meant to do with a conflict when I have no alternatives to choose between? :-)
[16:09] <lornajane> rubbs: I just can't bear ruby fanboys telling me that if I don't think git is the best thing ever, then I know nothing.  These are just tools and I just want to use them, not argue about it
[16:09] <lornajane> git is pretty good, sure, but if I'm going to get flamed in their channels then I'd rather use something else :)
[16:11] <rubbs> haha good points
[17:19] <starenka_> hi, i just want to checkout/branch source from a lp project (bzr :D), is there a way how to checkout "lightweight"? I mean i dont need any history, just need the lastest source to compile it
[17:20] <starenka_> (bzr n00b, sorry)
[17:21] <jderose> starenka_: bzr checkout --lightweight YOUR_BRANCH
[17:22] <starenka_> ty
[18:37] <eydaimon> I'm wanting to merge to specific files from one branch to another.  bzr merge ../trunk/file1 ../trunk/file2 gives errors complaining about extra arguments, and merging one file at a time gives error during merging of second file saying there are uncommitted changes. How can I merge more than one file at a time?
[18:38] <Kinnison> Erm, bzr operates by revision for merging IIRC
[18:38] <Kinnison> so you can't really merge by file
[18:38] <Kinnison> (unless this is a new feature I didn't know about)
[18:38] <eydaimon> but it appears to be very possible to merge just one file
[18:39] <eydaimon> seems to me I would have to merge and commit one file at a time otherwise
[18:39] <eydaimon> and if I can do that, it should support multiple
[18:39] <Kinnison> Why do you want to only merge specific files; rather than revisions?
[18:39] <eydaimon> what if the files are spread out over multiple revisions?
[18:40] <eydaimon> and there are other changes in those revisions I don't want merged
[18:42] <Kinnison> Sounds like a very unfortunate situation
[18:43] <Kinnison> I honestly don't know; sorry
[18:43] <Kinnison> you could try:
[18:43] <Kinnison> for F in file1 file2 file3; do bzr merge -force ../trunk/$F; done
[18:43] <Kinnison> since the --force option makes merge ignore uncommmitted changes and continue anyway
[18:43] <eydaimon> well, luckily it's not happening. I can actually use the change
[18:44] <Kinnison> I'd prefer using the revisions
[18:44] <Kinnison> since then history is nice and neat
[18:44] <eydaimon> but to me it's easier to keep track of what files I need rather than the revision
[18:44] <eydaimon> and since the above case is possible... just seems like something that would be supported
[18:46] <eydaimon> what's the bzr file needed to specify username?
[18:46] <Kinnison> username?
[18:47] <maxb> eydaimon: Try using bzr help whoami
[18:47] <Kinnison> If you want to tell bzr what author/committer name to use, then do: bzr whoami "My Name<EMAIL_ADDRESS>[18:47] <eydaimon> found
[18:47] <eydaimon> ~/.bazaar/bazaar.conf
[18:47] <eydaimon> well, one guy is checking in as root...
[18:47] <Kinnison> that guy needs to be spanked
[18:47] <Kinnison> (unless you're doing some kind of etckeeper thing)
[18:50] <eydaimon> he didn't want to touch his mac by installing stuff on it, so he is running virtualbox with redhat and doing his dev on there....
[18:50] <eydaimon> don't ask ...
[19:00]  * Kinnison won't :)
[19:00] <lifeless> Kinnison: he might like it
[19:02] <Kinnison> In that case, even if I were tempted to ask; I wouldn't want to know :-)
[19:15] <eydaimon> heh
[20:46] <Chocobo> Hi all.  How well does bzr handle large files?  I know this is an issue with hg and git.
[20:48] <luks> not much better, I guess
[20:48] <luks> what specifically are you interested in?
[20:50] <Chocobo> Oh I have a project with a lot of large binary data files.
[21:01] <lifeless> Chocobo: how large is large
[21:01] <Chocobo> 100 MB or so.
[21:02] <Chocobo> I would like to keep it in revision control because it is part of the project.
[21:03] <lifeless> as long as you have 300MB ram it should be fine.
[21:03] <lifeless> [and you are using 2.x]
[21:04] <NfNitLoop> Hrmm.  'bzr log' on this svn branch doesn't show 'svn revno:' for something I pushed from my local branch.
[21:05] <NfNitLoop> Not sure what's causing that...  doesn't seem to generate an error or anything.
[21:06] <NfNitLoop> Oh, come to think of it, it doesn't show svn revno for anything that was a result of a merge, it seems.
[21:06] <NfNitLoop> I guess so it can continue to show the bzr mergeinfo?
[21:16] <maxb> Hmm, the bzr-beta-ppa is not in very good shape :-/
[22:16] <maxb> Is there any convenient trick to running bzr from a working tree, but with C extensions?
[22:16] <maxb> Or should I find somewhere in my homedir to install it to, and use PATH and PYTHONPATH?
[22:16] <fullermd_> `gmake`
[22:17] <maxb> oh, neat, I didn't even look for a Makefile once I'd seen the setup.py
[22:27] <igc> morning
[22:46] <lamont> given a CVS repo with N branches, and possibly some violations of nature (hi lifeless), is that trivial to import into bzr yet?  even at one directory tree per branch?
[22:49] <lifeless> lamont: cvs2svn can output fast-import streams
[22:50] <lifeless> lamont: if it can handle your repo, then yes.
[22:50] <lamont> ah, cool
[22:50] <lifeless> lamont: as we can import fast import streams
[22:50] <lamont> and FWIW, it's not _my_ repo (this time)
[22:51]  * lamont cries a little as 'rcs' and 'subversion' both wind up on his machine
[22:53] <maxb> cvs2svn(bzr) does a decent job these days. Give me a prod if you find a problem, I've been hacking on it lately
[22:54] <lamont> will do
[23:02] <rockstar> jam, you're not at LCA are you?
[23:03] <mwhudson> rockstar: he is not
[23:03] <jam> rockstar: nope, I believe lifeless is
[23:04] <rockstar> jam, I wonder if I might schedule a call with you tomorrow as I land the last of the branch upgrade work.
[23:04] <rockstar> Er, the launchpad branch upgrade work.
[23:06] <jam> rockstar: sure, what time is good for you?
[23:06] <jam> I need to be going soon, though
[23:06] <rockstar> jam, how 'bout 10 AM your time tomorrow?
[23:07] <jam> rockstar: sounds good right now
[23:08] <rockstar> jam, okay.  If something comes up, feel free to send me an email with a new time.
[23:19] <maxb> bzr-rewrite is eating my brain
[23:28] <cjwatson> lamont: I did actually manage to use cscvs to import multiple branches; since there was already a cvs->bzr import on Launchpad using cscvs, I figured I was best off sticking with the same tool
[23:29] <lamont> cjwatson: coolness.
[23:29] <cjwatson> lamont: https://code.launchpad.net/~cjwatson/launchpad-cscvs/openssh-branch-imports for the gross hacks involved
[23:29] <lamont> nice
[23:29] <lamont> this is an NDA'ed CVS repo that 'git cvsimport' has a history of sometimes not liking
[23:29] <cjwatson> lamont: and http://bzr.debian.org/loggerhead/pkg-ssh/openssh/trunk/annotate/head:/debian/README.source? documents how to drive it.
[23:30] <cjwatson> lamont: oh, if cscvs hasn't already been involved, you might keep your sanity better by not involving it
[23:30] <lamont> it doesn't help that someone (and not me this time) has felt sufficiently of-clue to do manual surgery on the ,v files from time to time
[23:30] <cjwatson> that never helps
[23:30] <lamont> cvsps
[23:31] <cjwatson> my normal preference is to use something that spits out fast-import streams (like cvs2svn/cvs2git/whateveryoucallit), since they're hackable
[23:31] <lamont> one question that I might get an answer to (assuming it finishes): does cvs2git create consistent commit hashes?  or will two imports of the same tree not give the same git tree?  (ditto for cvs2bzr...)
[23:32] <cjwatson> there's no "cvs2bzr" AFAIK, it's more like cvs2git | bzr fast-import
[23:32] <lamont> cvs2svn: /usr/bin/cvs2bzr
[23:33] <lamont> beg differ
[23:33] <cjwatson> huh, so there is
[23:33] <cjwatson> wasn't last I looked. :)
[23:33] <lamont> gotta love these works in progress.
[23:33] <lamont> 375MB cvs tree -> 2.5GB and counting blob file
[23:34] <lamont> meanwhile, git cvsimport: WARNING: Invalid PatchSet 7114, Tag v9_0_base:
[23:36] <cjwatson> anyway, cvs2bzr is just slightly tweaked output versus cvs2git, it still requires use of bzr fast-import
[23:36] <lamont> and given that upstream is cvs, and I have my git tree for debian/ubuntu, and the whole tree is totally NDA, I'm inclined to leave it in git for the moment, and then play with it in bzr and make sure cvs2bzr is doing the right thing.
[23:36] <cjwatson> and bzr fast-import doesn't guarantee consistent revision-ids
[23:36] <lamont> maxb: cvs2bzr would be far more useful to me if it could do a delta addon to an existing previous result from cvs2bzr
[23:36] <cjwatson> I don't know about cvs2git | git fast-import
[23:37] <maxb> lamont: So say many people, but converting from CVS doesn't lend itself to that
[23:37] <lamont> well, running 2 copies of cvs2git now, just to see what it does.
[23:37] <cjwatson> however, to amend my previous comment
[23:37] <cjwatson> bzr fast-import permits storage of "fastimport-id-map" in the .bzr/repository
[23:37] <maxb> cjwatson: Well I've worked out what the bug in bzr rebase-foreign is, but I don't know how to fix is :-/
[23:37] <cjwatson> if you do that, then successive imports into the same repository will be idempotent
[23:37] <lamont> maxb: so I've told upstream.  in the end, I got rsync access to the ,v files, and "CVS has worked for us so far, no reason to change" by way of an answer about joining the current VCS world
[23:37] <cjwatson> so it *is* possible to do delta imports, that way
[23:38] <cjwatson> in fact I do that myself with debian-policy
[23:38] <lamont> cjwatson: awesome
[23:38] <cjwatson> rebasing will break it
[23:39] <lamont> that's because rebase always breaks things
[23:39] <cjwatson> http://paste.ubuntu.com/359284/ is the script I use to update my debian-policy bzr import
[23:39] <cjwatson> should switch to bzr-git one of these days
[23:39] <maxb> I don't think fastimport storing a map file will work to allow delta imports from cvs2bzr
[23:39] <maxb> Perturbation in the cvs repository could cause cvs2bzr to resolve changesets differently
[23:40] <cjwatson> depends on level of branch complexity
[23:40] <cjwatson> if there's weirdness regarding default branches, then possibly
[23:40] <lamont> "This is a necessary workaround for the fact that CVS tags are fundamentally different than git tags.)" <-- no, it's because CVS tags are fundamentally b0rked
[23:41] <cjwatson> you could also manually chop off the dump file before a certain timestamp, and hack it to start from a given revision
[23:41] <cjwatson> fast-import lends itself to that kind of hackery if you're sufficiently desperate
[23:42] <cjwatson> though generally once I fast-import from CVS I throw away the original as fast as humanly possible, admittedly
[23:42] <lamont> but for me, for whatever reason, the commit IDs turn out different every time I import. <-- sigh
[23:43] <lamont> I think it might be time to reopen the discussion with upstream...
[23:46] <maxb> Hmm, I wish jelmer was around.
[23:56] <lamont> WARNING: in '....' branch '...' already has name 'foo', cannot also have name 'bar', ignoring the latter
[23:57] <lamont> I wonder if that means they assigned a branch 2 names
[23:57] <lamont> cjwatson: I
[23:58] <lamont> d pay cash money to get the original CVS thrown away in this case.... just not enough money to convince upstream, yet.
[23:58] <lamont> of course, there'd be more negotiability if the repo weren't so private


[01:29] <StevenHarperUK> Hi - are translation downloads very slow again/still
[02:16] <StevenHarperUK> Hobbsee: are the translation exports still slow?
[02:17] <Hobbsee> StevenHarperUK: no idea.  i don't do translations
[02:18] <StevenHarperUK> Hobbsee: Ok It appears they are still v slow on the exports
[02:18] <StevenHarperUK> ccya
[15:00] <mpt> Goooooooooooooooooooood afternoon Launchpadders!
[15:15]  * mpt drops a pin
[15:17]  * TFKyle catches it
[15:24] <TomJaeger> Hi.  Is there anybody here with a fast internet connection who could do me a favor and upload two files to launchpad?  I'm getting timeouts...
[15:25] <mpt> TomJaeger, that's usually not a problem with the Internet connection itself, but I can try if you like
[15:25] <TomJaeger> okay, thanks
[15:29] <TomJaeger> I should have mentioned large files...
[15:35] <TomJaeger> sorry, I didn't immediately realize this: Private messages from unregistered users are currently blocked due to spam problems
[19:16] <ubotu> New bug: #179426 in launchpad "Can't approve someone's membership from their "Recently applied" link" [Undecided,New] https://launchpad.net/bugs/179426
[19:35] <ubotu> New bug: #179428 in launchpad "Page for editing applicant's membership and page linked by e-mail notification are different" [Undecided,New] https://launchpad.net/bugs/179428
[19:55] <ubotu> New bug: #179433 in launchpad ""Users can spoil their votes?" checkbox is wonky" [Undecided,New] https://launchpad.net/bugs/179433
[20:10] <ubotu> New bug: #179437 in launchpad "Validity of new poll's dates isn't checked before form submission" [Undecided,New] https://launchpad.net/bugs/179437
[20:25] <ubotu> New bug: #179441 in launchpad "Asking for poll option "Name" and "Title" is nonsense" [Undecided,New] https://launchpad.net/bugs/179441
[20:30] <ubotu> New bug: #179442 in launchpad "Adding another poll option requires navigating to another page" [Undecided,New] https://launchpad.net/bugs/179442
[20:40] <ubotu> New bug: #179443 in launchpad "Asking for poll's "unique name" and "title" is unnecessary" [Undecided,New] https://launchpad.net/bugs/179443
[20:50] <ubotu> New bug: #179445 in launchpad "Not obvious whether/why a team admin can't change the team's owner" [Undecided,New] https://launchpad.net/bugs/179445
[23:10] <ubotu> New bug: #179466 in soyuz "race between build retry and purge of old build tree" [Undecided,New] https://launchpad.net/bugs/179466


[05:04] <harry_> hey any one with the knowledge of language selector in Ubuntu 11.04???
[10:32] <harry_> ey any one with the knowledge of language selector in Ubuntu 11.04???


[00:20] <bluesabre> knome: why you sleeping people silly?
[00:23] <knome> nooo
[00:23] <knome> i'm not sleeping!
[00:25] <bluesabre> :o
[02:34] <bluesabre> Trying to figure out what is broken for clutter is a pain
[02:42] <bluesabre> Well, parole starts now, but the video pops out into its own window
[02:45] <knome> plop
[02:45] <knome> ;)
[03:18] <bluesabre> Apparently, cluttersink is now clutterautovideosink
[03:18] <bluesabre> and has different properties
[04:21] <bluesabre> after playing with that code for a few hours, no progress
[04:21] <bluesabre> yay
[04:21] <bluesabre> night all
[04:28] <Unit193> G'nighty, bluesabre.
[07:40] <flocculant> oh good lord - another rebuild
[08:02] <Nairwolf> flocculant: I've haven't time to test new version of xubuntu, but how is the next xubuntu 15.04 ? Will it be a good version ?
[08:03] <flocculant> 16.04 is looking good :)
[08:04] <Nairwolf> oh, yes, we are in 2016 ;)
[08:04] <flocculant> Nairwolf: I'll be wanting as many people as possible to test the beta 1 milestone next week - so you can have a go with that :)
[08:04] <Nairwolf> oh, good !
[08:04] <Nairwolf> okay, will you send a new mail ?
[08:04] <Unit193> flocculant: I've got 3 systems on it!
[08:05] <Nairwolf> great ;)
[08:05] <flocculant> Nairwolf: yep - to the -devel list and directly to people in https://launchpad.net/~xubuntu-testers
[08:05] <flocculant> Unit193: I knew I could count on you quietly :p
[08:05] <Nairwolf> where I can find what will be new in this version ?
[08:05] <flocculant> and I see where you report things as well
[08:05] <Nairwolf> a release notee
[08:05] <flocculant> Nairwolf: for 16.04?
[08:05] <Nairwolf> yes
[08:06] <Nairwolf> is it already writen, or not ?
[08:06] <flocculant> there will be a release note and a website page
[08:06] <Unit193> Figured you might see reports.
[08:06] <flocculant> ha ha ha - no not even started - I'll do that next week
[08:06] <flocculant> Unit193: :)
[08:06] <Nairwolf> ok, ok ;)
[08:07] <flocculant> Unit193: I dropped by -dekstop yesterday and dropped the gst issue in there - that'll get sorted now I think
[08:07] <flocculant> with bugs being marked critical etc
[08:08] <flocculant> seb got it to fail in rhythmbox
[08:10] <Unit193> Nice!
[08:10] <flocculant> possibly would have been easier to find it fails in rhythmbox I guess :)
[08:41] <dkessel> flocculant: do you als have "parole displays all videos as green window in xenial"?
[08:41] <dkessel> also
[08:42] <dkessel> vlc also only plays half the videos anymore
[13:09] <flocculant> dkessel: that's a clutter issue afair bug 1513277
[13:09] <flocculant> change to xv to use it
[13:09] <flocculant> no idea about vlc never use it :)
[13:28] <flocculant> just so people are aware if they were intending to test trusty - another rebuild happening 'tomorrow'
[13:37] <Akxwi-dave> thx flocculant ..  date noted.. :-)
[14:41] <dkessel> oh good to know!
[14:59] <knome> Unit193, krytarik: decided which media manager you are going to confess using?
[16:28] <knome> i'm so happy we have our own wiki now
[16:28] <knome> the old one is pain to work with (and i just want to make simple edits)
[16:28] <knome> it's the slowest in ages again...
[16:48] <knome> flocculant, do we want to keep maintaining https://wiki.ubuntu.com/Xubuntu/Testing/HardwareProfile somewhere?
[16:49] <knome> flocculant, same for https://wiki.ubuntu.com/Xubuntu/Testing/TeamHardware
[17:37] <flocculant> knome: spooky ... I was looking at them earlier - was going to ask you how to kill profile - not sure about other one yet
[17:40] <knome> so hwprofile is just obsolete?
[17:40] <knome> or do we want a redirect?
[17:42] <flocculant> knome: hwprofile is pretty much obsolete - the only real reason was a copy of the thing that was on the tracker - which is now gone
[17:43] <knome> yeah
[17:45] <knome> oh bah
[17:46] <flocculant> alternatively - replace it with 'really ... '
[19:16] <knome> pleia2, just that you don't get a heart attack the next time you access a marketing page in the wiki - i have copied most of them to the new wiki with 5 sec redirects on the old pages
[19:16] <pleia2> lol
[19:16] <pleia2> noted
[19:16] <knome> pleia2, but obviously if you looked at your email, you'd know this already..
[19:17] <pleia2> updates from the wiki? the wiki can't email me at the moment, I need to switch off my @ubuntu.com address
[19:18] <knome> oh
[19:18] <knome> nvm then
[19:24] <knome> pleia2, how do you feel about https://wiki.ubuntu.com/Xubuntu/Marketing/Projects/Flyers ? i would probably just point that to the repository (this page has no information that is useful)
[19:26] <pleia2> knome: as long as we retain the information that lived on wiki (main details, formats) I think that's fine
[19:26] <pleia2> could add it to a readme file in the repo or something
[19:27] <knome> the intro is kept in x.org, the text ideas too, the formats is just for planning (and we don't plan to provide the flyer in *all* of those), and the design *is* in the repository
[19:27] <pleia2> yep
[19:27] <pleia2> so I think we're ok then
[19:27] <knome> yeah, i'll point it to the repository
[19:41] <flocculant> knome: re announcement - website currently points to the .2 announcement/release note
[19:41] <knome> i don't think we have .3 announcement/notes
[19:41] <knome> that's why it's doing that
[19:41] <flocculant> nope
[19:41] <flocculant> yea
[22:02] <krytarik> knome: Remember my reasoning for not jumping in on the vote earlier?  That's valid for real now! :P  (Not using anything regularly myself currently.)
[22:03] <knome> i don't... :P
[22:07] <flocculant> vote?
[22:07] <knome> depends on the election i guess :P
[22:14] <krytarik> → https://lists.ubuntu.com/archives/xubuntu-devel/2015-November/010948.html
[22:14] <flocculant> oh that
[22:14] <knome> aha.
[22:21] <ochosi> hey bluesabre, if you wanna get that patch into xfpm you better submit it soonish ;)
[22:45] <ochosi> bluesabre: also, it might be a good idea to postpone some workitems from development so the focus can be laid on the ones that really should be fixed this cycle (fonts-droid, default LO theme, shimmer-themes packageset, x-core, and a few more)
[23:13] <knome> if people want to try something new out, there's now a more integrated looking tracker at http://tracker.xubuntu.org/index2.php
[23:14] <knome> or not really tracker any more - developer area


[01:48] <DanaG> hmm, anyone know why the kernel-ppa stuff hasn't been updated in a while?  the only 34-rc2 kernel there says "karmic" specifically, and the same is true of the latest drm-next kernel there.
[01:49] <DanaG> Does it matter that it says "karmic", if I want to use it on Lucid?  I've seen it matter before, on ARM, at least.... try a karmic kernel with lucid userspace, it doesn't boot.
[02:03] <JanC> I guess "karmic" means it was compiled with karmic's configuration file?
[02:06] <DanaG> beats me.  I'm about to try the drm-next "karmic" kernel.
[02:06] <DanaG> I've also noticed that the kernel-ppa kernels all have the STAGING dir entirely disabled... as well as MMC_RICOH_MMC
[02:07] <DanaG> Something about "symbol 'm' not valid for ... "
[12:55] <nosse1> How do I build a (fresh git) kernel when I dont have the debian/ dirs installed and get it installed on the system (preferrably via a deb-file)
[12:55] <nosse1> Will make-kpkg handle that?
[13:09] <smb> preferably (if you don't want to use git) by apt-get source linux-image-2.6.x-y-generic which gives you the kernel source including the debian dirs
[13:11] <nosse1> smb: I can't use the ubuntu source, as there are none for my target, so I need to go with a 3rd part kernel branch.
[13:11] <nosse1> So I have the kernel source and a working config, but I need to wrap this into ubuntu-world
[13:13] <smb> You could clone the git tree and copy the debian* dirs into your tree
[13:13] <nosse1> smb: Thats all that's needed? What happens to my local kernel config?
[13:14] <smb> nosse1, You would need to see how you get it integrated with debian.master/configs/...
[13:17] <smb> nosse1, Maybe it does work with make-kpkg but I never use that
[13:17] <nosse1> smb, I'm trying to integrate debian* right now.
[13:18] <nosse1> smb, What do you do to compile kernels then?
[13:19] <smb> nosse1, I only do the Ubuntu kernels. No need for me to do anything special. :-P
[13:19] <nosse1> But you use make-kpkg to build them, right?
[13:20] <smb> nosse1, No. Either debuild, or dpkg-buildpackage or fakeroot debian-rules ... when I am in a hurry
[13:21] <nosse1> OK, thanks
[13:46] <mozmck> smb: did you see my post here about the kernelconfig script not working because DROOT is not defined?
[13:47] <smb> mozmck, I cannot recall it. Where did you post it?
[13:47] <mozmck> here on IRC a couple days ago.
[13:47] <mozmck> To fix it here I just added DROOT=debian to debian/debian.env
[13:48] <mozmck> this is in the lucid git tree
[13:48] <smb> IRC is quite prone to loose things. But on Lucid debian.env should be always set
[13:48] <smb> Are you using a special tree?
[13:49] <smb> Actually it should be debian.master which it points to
[13:49] <mozmck> no
[13:50] <smb> ~/src/ubuntu-lucid/kernel$ cat debian/debian.env
[13:50] <smb> DEBIAN=debian.master
[13:50] <mozmck> I'm using kernel.ubuntu.com/ubuntu/ubuntu-lucid.git
[13:51] <mozmck> yes, but DROOT is used in the kernelconfig script and is not defined anywhere.
[13:51] <mozmck> this is both on karmic and in 10.04 beta1
[13:53] <mozmck> and looking at the kernelconfig script, line 29 is bindir="`pwd`/${DROOT}/scripts/misc"
[13:53] <smb> which script are you talking about?
[13:53] <mozmck> so I figured DROOT had to be 'debian'
[13:53] <smb> ok found it
[13:54] <smb> apw, Is that meant to be called directly
[13:55] <apw> mozmck, smb, nope thats not menat to be run directly
[13:55] <mozmck> all the instructions I found have you call "kernelconfig editconfig" to edit the configs.  this worked on karmic fine but not in lucid
[13:55] <apw> its used from debian/rules updateconfigs and the like
[13:55] <mozmck> so how are you supposed to edit the configs now?
[13:55] <apw> where are those instructions?  they are wrong
[13:55] <smb> Right, where does it say to call it directly?
[13:55] <apw> debian/rules editconfigs would make sense
[13:55] <smb> yep
[13:56] <apw> and should work for all releases too
[13:56] <smb> mozmck, To call "debian/rules editconfig" was always the intended way
[13:57] <mozmck> http://blog.avirtualhome.com/2009/11/03/how-to-compile-a-kernel-for-ubuntu-karmic/
[13:57] <mozmck> That's linked to from here: https://help.ubuntu.com/community/Kernel/Compile
[13:57] <apw> yay ... random community randomness
[13:57] <Keybuk> https://wiki.ubuntu.com/KernelTeam/KernelForIdiots ;-)
[13:58] <apw> Keybuk, heh yeah i like that one better :)
[13:59] <mozmck> I see.  It seems quite hard to find good information on this subject!
[13:59] <apw> i wonder if we should rename that dummies :)
[13:59] <apw> mozmck, mostly because there is such a lot of bad information out there
[13:59] <mozmck> I've seen that link, but it doesn't mention editconfig, and I am a dummy so I need menuconfig :)
[14:00] <apw> do feel free to help us make the ForIdiots page better ... Keybuk only did the bits he needed :)
[14:01] <mozmck> oh, ok! I forget I can change those pages.
[14:01]  * apw adds a comment to the random blog telling them they are wrong :)
[14:01] <mozmck> thanks for the help.
[14:01] <Keybuk> it's basically where I put notes so I don't have to keep rediscovering them each time
[14:03] <mozmck> is there a way to tell it to just edit the config for one flavour or do you just have to step through them all?
[14:03] <Keybuk> I just tend to edit the config file itself
[14:03] <Keybuk> then use updateconfigs to fill in the bits I missed
[14:03] <apw> mozmck, no you have to step through them all with that interface
[14:04] <mozmck> ok
[14:04] <apw> yeah mostly i am in bulk update mode and want to do them all at once, so i tend to do the update by adding things to the toplevel common files and doing an updateconfigs
[14:06] <mozmck> I'm working on a custom flavour with rtai patches for running CNC machines with EMC2, so I just add and change settings for that one flavour.
[14:10] <mozmck> 'debian/rules editconfig' -> make: *** No rule to make target `editconfig'.  Stop.
[14:11] <mozmck> 'debian/rules editconfigs' -> dh_testdir: cannot read debian/control: No such file or directory
[14:11] <Keybuk> mozmck: fakeroot debian/rules clean first
[14:11] <mozmck> ah, that works
[14:11] <mozmck> thanks
[16:02] <bjf> ##
[16:02] <bjf> ## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[16:02] <bjf> ##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting
[16:02] <bjf> ##
[16:57] <IdleOne> ogasawara: Congrats!!! awesome,incredible,great news :D
[16:57] <ogasawara> IdleOne: thanks!
[17:27] <cnd> apw: I'm interested in cleaning up the linux-firmware-nonfree package, partially to learn more about packaging
[17:27] <cnd> rtg is gone for a bit, and I'd like my changes to get into lucid
[17:27] <cnd> would you be able to review them?
[17:53] <apw> cnd sure thing
[18:00] <ogasawara> apw: https://launchpad.net/~leannogasawara/+archive/ppa/+build/1590208/+files/buildlog_ubuntu-lucid-i386.linux_2.6.34-1.1~oga2_FAILEDTOBUILD.txt.gz
[18:12] <JFo> bug 507416
[18:12] <ubot3> Malone bug 507416 in linux-fsl-imx51 "CONFIG_NEON=y causes platform lockups with certain application/platform combinations" [Medium,Fix committed] https://launchpad.net/bugs/507416
[18:14] <smb> JFo, That should be ok as far as I know, they just don't bother update their bug status. :/
[18:14] <JFo> ok :)
[18:33] <crimsun> pgraner: JFo: could you ping Jane S and ask her permission to put a Reported-by in the git changelog for LP 551606, 548661?
[18:34] <crimsun> (ideally an e-mail address, too, but I understand if she doesn't want it in the kernel changelog)
[18:35] <JFo> crimsun, will see what I can do about that. :)
[18:35] <bjf> crimsun, you're doing an upstream fix for 551606?
[18:37] <crimsun> bjf: yes, I'm about to push the button on git commit -e -a -s
[18:38] <bjf> crimsun, ok, you are doing a quirk for her SSID?
[18:38] <crimsun> bjf: no, for all models using that quirk; I'll attach the diff
[18:39] <bjf> crimsun, ack
[18:39] <crimsun> bjf: also, I believe I have a fix for her hp mute issue, but there are at least two further debugging steps necessary, one of which requires rolling a new alsa-driver snap (I'll attach a diff to 548661 if the first option is insufficient)
[18:41] <bjf> crimsun, when does takashi "release" new alsa-driver versions? is there a schedule or just when he feels things are "right"
[18:42] <crimsun> bjf: he doesn't generally roll those; Jaroslav tends to push the buttons
[18:42] <bjf> crimsun, ah, ok
[18:43] <cnd> apw: while I work with #launchpad to figure out the merge request, feel free to review the last four commits at https://code.launchpad.net/~chasedouglas/lucid/linux-firmware-nonfree
[18:51] <crimsun> smb: do you know when the window for <IP_ADDRESS> closes? I have possibly two more patches to push to stable (both Jane S's bugs), and I'd like to get them in if feasible.
[18:52] <JFo> I think it is tomorrow morning iirc
[18:52] <JFo> but I defer to smb
[18:52] <smb> crimsun, Not for sure. Normally this amount of activity I would say he might close on Friday
[18:52] <JFo> ah, see I was wrong ;-)
[18:52] <smb> crimsun, But sometimes he is quicker.
[18:52] <crimsun> smb: JFo: ok, thanks
[18:53] <smb> JFo, ITs hard to say. I have not really found a regular schedule in Greg.
[18:53] <JFo> true, I was thinking of something else entirely I am sure
[18:58] <cnd> apw: ignore my previous bzr branch, I figured out the merge process, so use it instead please
[19:02] <bjf> apw, can you comment on crimsun question ^^
[19:06] <crimsun> (actually I'm awaiting on her ack to submit the first patch :-)
[19:06] <crimsun> awaiting her *
[19:38] <rackerhacker> jjohansen: have you had reports of a microtime issue in linux-ec2?
[19:38] <rackerhacker> i couldn't find a relevant bug
[19:39] <jjohansen> hrmm, not any that I have heard of
[19:39] <jjohansen> what are you seeing?
[19:39] <rackerhacker> lemme slip it into pastie right quick
[19:39] <rackerhacker> http://pastie.org/895689
[19:41] <rackerhacker> jjohansen: here's a normal karmic server (bare metal, not in a VM): http://pastie.org/895692
[19:41] <rackerhacker> which is more of what i'd expect
[19:42] <rackerhacker> if i pop in an old hardy 2.6.24 kernel, all is well
[19:43] <rackerhacker> domU w/2.6.24-23 -> http://pastie.org/895696
[19:44] <rackerhacker> it's not perfect in 2.6.24, but it's worse in linux-ec2 from lucid
[19:44] <rackerhacker> but it could be a silly kernel config on my part
[19:45] <jjohansen> hrmm, well that does look odd, I'll have a look and run a few tests
[19:46] <rackerhacker> i can set you up on one of our environments if that'd help
[19:48] <jjohansen> rackerhacker: sure, that would be worth snooping at
[19:49] <rackerhacker> gimme a second to get one rolling
[20:43] <rackerhacker> jjohansen: want me to pile the details into a launchpad bug?
[20:59] <soren> rackerhacker: Just for giggles, could you try booting a machine with clocksource=acpi_pm and run the same test?
[20:59] <soren> rackerhacker: (A physical machine, that is)
[21:00] <rackerhacker> a physical machine running linux-ec2?
[21:00] <soren> rackerhacker: Running the same as the machine in http://pastie.org/895689 was running.
[21:01] <rackerhacker> soren: that particular example was within a domU
[21:01] <soren> rackerhacker: Sorry, wrong pastie.
[21:01] <soren> rackerhacker: http://pastie.org/895692 this one.
[21:02] <rackerhacker> let me see if i can spare that machine for a moment ;-)
[21:26] <jjohansen> rackerhacker: hrmm, not yet.  I haven't been able to replicate on EC2, I have run through 10 different instance size/kernel combinations and every one was good.  I haven't tried your config on EC2 yet though
[21:32] <rackerhacker> jjohansen: you might be right, soren walked over and gave me a run down
[21:35] <JFo> crimsun, thumbs up from Jane
[21:35] <JFo> crimsun,
[21:35] <JFo> That's fine - I have no problem with my name and/or email going in there.
[21:35] <JFo> thanks,
[21:35] <JFo> Jane
[21:44] <rackerhacker> jjohansen: call off the search, soren just beat me up with some knowledge
[21:44] <rackerhacker> it turns out i was using clocksource=jiffies
[21:44] <rackerhacker> soren's suggestion of clocksource=acpi_pm fixed it immediately
[21:44] <jjohansen> ah, yeah that can cause so problems
[21:45] <rackerhacker> soren also says hello
[21:45] <jjohansen> yeah, say hi to soren for me too
[21:46] <rackerhacker> can do
[21:46] <rackerhacker> jjohansen: i owe you three cases of beer at this point
[21:46] <rackerhacker> my tab is increasing :/
[21:46] <jjohansen> hehe, not at all
[21:47] <jjohansen> after all soren fixed this problem :D
[21:47] <rackerhacker> other than acpi_pm being a little more expensive than jiffies, should i be worried about anything?
[21:51] <jjohansen> rackerhacker: not really it is consider the best practice to use acpi_pm on more modern kernels
[21:52] <soren> rackerhacker: Just make sure you keep proper time on the host.
[21:55] <rackerhacker> soren: can do
[21:55] <rackerhacker> jjohansen: thanks ;)
[21:56] <jjohansen> np
[21:56] <jjohansen> :-)


[01:19] <RedSingularity> Excuse me gentleman, what can I do with a bug that is more of an opinion rather than a bug?  Besides mark it as opinion.....do i do anything else to it?
[01:21] <hggdh> RedSingularity: bug #, please
[01:21] <RedSingularity> bug 656493
[01:21] <ubot2> Launchpad bug 656493 in update-manager (Ubuntu) "ask for reboot only if the system changes are critical and heuristics tell us the machine wont get a reboot sooner or later (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/656493
[01:23] <hggdh> RedSingularity: well... we only ask for a reboot if a critical component has been replaced...
[01:23] <hggdh> So, as far as I can understand, we are already doing this.
[01:23] <hggdh> let me comment there
[01:24] <RedSingularity> hggdh:  alright :)
[01:25] <RedSingularity> hggdh:  in the future if I see opinions is it correct to mark it as an opinion and give it a "opinion" response?
[01:26] <hggdh> no, opinion should be restricted to those bugs that -- after being closed -- still get a lot of comments
[01:26] <RedSingularity> ah ok
[01:29] <hggdh> RedSingularity: I added my comment and request for info there
[01:30] <RedSingularity> hggdh:  Ok i see it.  Thanks :)
[01:32] <RedSingularity> hggdh:  Is the closed option for a bug under the importance?
[01:33] <hggdh> RedSingularity: I am not sure I understand your question
[01:33] <hggdh> oh -- how to close a bug?
[01:33] <RedSingularity> yes sir
[01:34] <hggdh> this is done by changing the Importance field
[01:34] <RedSingularity> Oh ok thats what i thought because i didnt see it anywhere
[01:34] <hggdh> A value of opinion, invalid, fix released is considered a final status
[01:34] <hggdh> sorry, not importance, status
[01:35] <RedSingularity> final status is closed?
[01:35] <RedSingularity> or considered "closed" i mean?
[01:37] <micahg> and Won't Fix :)
[01:37] <RedSingularity> i see
[01:38] <RedSingularity> sorry for all these questions guys :)
[01:40] <RedSingularity> i do appreciate all the help i get in here though :)
[01:40] <micahg> RedSingularity: questions are how we learn
[01:40] <hggdh> micahg: thank you, I had forgotten wontfix
[01:41]  * hggdh is tired, been on that since 0600
[01:42] <RedSingularity> With some bugs I see that i cannot reproduce it so i suggest a fix.....am I right doing that?  For example bug 655024
[01:42] <ubot2> Launchpad bug 655024 in transmission (Ubuntu) "Using higher cpu usage (affects: 2) (dups: 1) (heat: 18)" [Undecided,Incomplete] https://launchpad.net/bugs/655024
[01:45] <hggdh> that's OK. But I noticed you asked about a 10.04, while in the decription it said 10.10...
[01:46] <hggdh> RedSingularity: I am not sure it is a fix you suggested, though
[01:46] <RedSingularity> I usually ask if they have upgraded from a previous version so i may do the same.
[01:47] <hggdh> yes, that's OK, but you asked if the OP hgad upgraded *to* 10.04. The description clearly states the issue is on 10.10
[01:47] <hggdh> this just shows we need to really _read_ the description (and yes, I have done that also)
[01:48] <hggdh> so you are not alone ;-)
[01:48] <RedSingularity> hggdh:  oh that is a typo on my part....i meant 10.10
[01:48] <hggdh> oh, OK
[01:49] <RedSingularity> And i read the comments before I post them for typos.......didnt do too good a job there.
[01:49] <hggdh> heh
[01:50] <RedSingularity> time for a contact lens prescription update ;)
[01:52] <RedSingularity> hggdh:  If a fix does not work for a person and they still have a problem that *cannot* be reproduced on another machine what would be the next step?
[01:53] <hggdh> gather more information from the OP
[01:54] <RedSingularity> you mean any info I can think of that may help me reproduce it?
[01:56] <hggdh> it may be you cannot reproduce at all
[01:56] <RedSingularity> thats what i though.....so what would I do with any other info I collect?
[01:56] <hggdh> so you would have to start considering what could be causing transmission to use CPU
[01:56] <RedSingularity> hmmmmm
[01:57] <hggdh> for example -- the OP is not downloading, but is transmission uploading?
[01:57] <hggdh> the real important point is that the bug *may* exist, even if you cannot reproduce it
[01:58] <RedSingularity> could it really be considered a bug if the problem is on their machine alone?
[01:59] <hggdh> how do you know it is on their machine alone? Just because *you* (and some others) cannot reproduce?
[01:59] <RedSingularity> true
[01:59] <hggdh> this is particular important when dealing with hardware-related issues, BTW
[02:00] <hggdh> personally, I think the OP's transmission is uploading... so it is not a bug. But this has to be proved
[02:02] <RedSingularity> Well.....in the rare case that the problem is on their machine......how would we even know?  We would need LOTS of people to test it and prove it wrong would we not?
[02:02] <hggdh> well
[02:03] <hggdh> let's say it is hardware-related (sound, or video). The only way to _really_ be able to reproduce is by having the exact same hardware
[02:03] <RedSingularity> i agree
[02:04] <RedSingularity> I personally stay away from hardware related problems though because I am using virtualbox
[02:04] <hggdh> which, amazingly enough, is not that easy to get -- vendors sell a machine, with the same product code, even when they replace pieces of harware
[02:05] <RedSingularity> yea i have seen that many time
[02:05] <RedSingularity> *times*
[02:05] <hggdh> but, in this case, there is a chance transmission is uploading to some, perhaps many, remotes
[02:06] <hggdh> so the OP is not _downloading_ but transmission is still doing what it does -- sending up chunks of a file
[02:07] <hggdh> now... how you check this... IDK, I do not use transmission, or any other torrent client
[02:07] <RedSingularity> I guess this is why they suggest to stay with packages you know well yourself.  It is easier to diagnose.
[02:08] <hggdh> yes
[02:08] <RedSingularity> do you specialize in a section of bugs?
[02:09] <RedSingularity> or packages?
[02:09] <hggdh> I used to do a lot of evolution, but I am sort of out nowaday, quite busy with the Ubuntu server flavour
[02:09] <hggdh> coreutils
[02:09] <hggdh> and the miscelaneous odds and ends
[02:10] <hggdh> (which is to say, answering questions like yours, etc)
[02:10] <RedSingularity> interesting.....
[02:11] <hggdh> but... I am going AFK, been on the computer for the last 14 hours
[02:11] <RedSingularity> no problem.....talk later :)
[02:11] <RedSingularity> thanks
[02:11] <hggdh> later
[02:13] <rusivi> RedSingularity: From my experience, the best way to go is specialize in bugs of the packages you find interest in. I like VirtualBox & WINE and have regulated those.
[02:14] <RedSingularity> Yeah....or i though about maybe packages that I use on a daily basis......
[02:15] <rusivi> RedSingularity: That is a good way to go.
[02:16] <RedSingularity> Is there a way to "sort" bugs you want to see on launchpad?  I have done it in the past but maybe i am not doing it the *correct* way.  IDK.
[02:17] <RedSingularity> I have been using the default page......https://bugs.launchpad.net/
[02:18] <RedSingularity> And selecting a project
[02:18] <RedSingularity> Is there a more efficient way?
[02:24] <rusivi> RedSingularity: Sure, if you go to the bug list of the package your interested in bugging, you could use the advanced search and have at it.
[02:25] <rusivi> For myself, virtualbox-ose I would start at: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ose
[02:25] <rusivi> then advanced search accordingly.
[02:29] <rusivi> Others in this chat use site search via google.
[02:36] <RedSingularity> Yeah, i like using the google site search for duplicates.  That works great!
[02:46]  * RedSingularity is away: Away at the moment, be back soon.
[03:31]  * RedSingularity is back (gone 00:44:59)
[03:33] <RedSingularity> Is there a command I can use to gather system information from a user?  Operating system information to be exact.
[03:38] <charlie-tca__> as in?
[03:38] <charlie-tca__> if you want the release version, you ask them to run "lsb_release -a"
[03:38] <charlie-tca__> If you want the kernel/linux version you ask for "uname -a"
[03:39] <RedSingularity> lsb_release was what i was looking for!
[03:39] <RedSingularity> great
[10:34] <algnod> Hi all, could someone please set the following to triaged Bug #656763 thanks!
[10:34] <ubot2> Launchpad bug 656763 in gnome-games (Ubuntu) "The 'Pause' button in Mahjongg doesn't have an icon (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/656763
[10:35] <vish> algnod¦ could you forward that bug upstream?
[10:35] <algnod> vish, how do i do that?
[10:36] <vish> !forwarding
[10:36] <ubot2> Factoid 'forwarding' not found
[10:36] <vish> hmm.. ;p
[10:36]  * vish grabs linky
[10:36] <algnod> ok, I will look it up :-)
[10:37] <vish> algnod¦ https://wiki.ubuntu.com/Bugs/Upstream/GNOME
[10:38] <vish> algnod¦ do you know what is causing that bug?
[10:41] <vish> algnod¦ not a requirement to know, but it would just be a bonus if you knew! ;)
[10:42] <vish> i should stop talking to ghosts ;p
[11:37] <mortal> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/656255 I posted this bug some time ago
[11:37] <ubot2> Launchpad bug 656255 in xserver-xorg-input-synaptics (Ubuntu) "package can not be installed on maverick, limited synaptics functionality (affects: 1) (heat: 6)" [Undecided,New]
[11:37] <mortal> it is very annoying
[11:37] <mortal> I can not install maverick on my gf's laptop because of it
[11:53] <AbhiJit> hi
[11:54] <persia> mortal, Please try again.  It installed for me.
[11:54] <AbhiJit> what can be done here?
[11:54] <AbhiJit> https://bugs.launchpad.net/ubuntu/+source/yarssr/+bug/656817
[11:54] <ubot2> Launchpad bug 656817 in yarssr (Ubuntu) "yarssr dont support Devanagari (affects: 1) (heat: 6)" [Undecided,New]
[11:54] <AbhiJit> anyone free to do?
[11:54] <mortal> persia: how
[11:56] <mortal> persia: it complains on my system about dependencies
[11:56] <mortal> persia: I am running i386, are you?
[11:56] <persia> mortal, Does `apt-get update` help?
[11:56] <mortal> running
[11:57] <mortal> persia: did you have the same problem
[11:57] <persia> AbhiJit, I suspect someone has to investigate the string handler for the yarssr configuration settings: it probably isn't UTF-8 safe
[11:57] <persia> mortal, Nope.  Installed fine for me
[11:57] <AbhiJit> persia, hmm annything there i can do? or can you suggest me a good rss reader?
[11:58] <mortal> persia: weird
[11:58] <mortal>  xserver-xorg-input-synaptics : Riippuvuudet: xorg-input-abi-11.0
[11:58] <persia> mortal, Unfortunately common, as mirrors pulse and sync.
[11:58] <mortal>                                 Riippuvuudet: xserver-xorg-core (>= 2:<IP_ADDRESS>5-1ubuntu3) mutta 2:1.7.6-2ubuntu7.3 o
[11:58] <mortal> persia: I have had that problem for a long time
[12:00] <persia> mortal, very odd.  I really can't reproduce.  No installation issues, and I get xserver-xorg-core 2:1.9.0-0ubuntu7 (which is definitely bigger).
[12:01] <mortal> maybe I need to reinstall xorg
[12:01] <persia> Maybe you need to `apt-get update; apt-get dist-upgrade`.  I'd recommend asking in #ubuntu+1 for help, as I'm 85% convinced it's a transitional issue that only affects your install.
[12:01] <mortal> persia: did that
[12:01] <mortal> now removing xorg
[12:02] <AbhiJit> persia, thats my bug. anything i can do with it?
[12:02] <persia> AbhiJit, There's heaps of RSS readers: you'd want to try them all.  If you're up for investigating, the key bit is to get the source and look for how it saves and loads the configuration.  You may find lots of useful information by just opening the configuration in a text editor or similar.
[12:02] <mortal> persia: now it works
[12:02] <AbhiJit> persia, ok
[12:02] <persia> mortal, Happens often running prereleases.  Please mark your bug "Invalid".
[12:03] <mortal> how?
[12:03] <AbhiJit> persia, what is OPML?
[12:04] <persia> AbhiJit, My guess would be some sort of XML: http://en.wikipedia.org/wiki/OPML may or may not be a useful resource.
[12:04] <AbhiJit> ok
[12:04] <penguin42> Does anyone know how to get amixer values in the same format as apport includes them in sound bugs?
[12:06] <penguin42> ah - no options!
[12:06] <persia> penguin42, heh, also /usr/share/apport/package-hooks/source_alsa-driver.py
[12:06]  * penguin42 spent 5 mins trying to find the right option; answer - no options
[13:18] <layn> Greetings to all
[13:38] <kklimonda> hey, when package craches with apport enabled it stores all the data in /var/crash even if the package isn't "genuine"?
[13:39] <ashams> Hello,
[13:40] <ashams> can any one help me to read the xev output, please :)
[14:33] <badp> Hello, I need help with attaching this bug to the right packages/projects:
[14:33] <badp> https://bugs.launchpad.net/ubuntu/+bug/656855
[14:33] <ubot2> Launchpad bug 656855 in ubuntu "Desktop icons and the mouse may reside in areas that are covered by no monitor. (affects: 1) (heat: 6)" [Undecided,New]
[14:36] <bp_> (I'm badp, rebooting other computer to test if kubuntu also has that bug)
[14:58] <penguin42> bp_ I'd say xserver-xorg
[14:59] <bp_> fair enough (I'm currently struggling to use ubuntu-bug under kubuntu to report the different set of problems Kubuntu has)
[15:00] <penguin42> ah, which ones?
[15:01] <bp_> for example, you can drag widgets off screen; the second monitor doesn't run a desktop at all; clicking in the "virtual" area above the main screen brings artifacts
[15:02] <bp_> and you can also have the mouse off screen
[15:02] <bp_> it'd be easier if OpenDNS didn't claim bugs.launchpad.com isn't working
[15:02] <bp_> it'd be easier if ubuntu-bug didn't fail if a rekonq window is already open too.
[15:03] <bp_> *www.bugs.launchpad.com
[15:06] <Pici> bp_: Thats because it doesn't exist. Its launchpad.NET
[15:07] <penguin42> bp_: What's your graphics setup ?
[15:08] <bp_> Pici: sure, that was just a problem with writing the URL from memory.
[15:08] <bp_> penguin42: what would you like to know about it?
[15:08] <bp_> I'm not running any propietary drivers.
[15:09] <bp_> Both Ubuntu and Kubuntu should be using the noveau drivers.
[15:09] <penguin42> ah ok, nouveau, I just wondered if it was a commonish multi display Intel problem
[15:13] <bp_> what's the package behind ubuntu-bug, so I can report the rekonq bug against it?
[15:13] <bp_> apt-cache search ubuntu-bug gives nothing.
[15:14] <penguin42> bp_: dpkg -S says apport
[15:14] <bp_> thanks
[15:52] <flipefr> hello
[15:53] <flipefr> did someboby try to watch videos with firefox in maverick after the upgrade?
[15:55] <charlie-tca> flipefr: I am sure some have tried that. There have been over 200 people running Maverick for some months already in #ubuntu+1
[15:57] <flipefr> charlie-tca: sure, i ask it because is a bug telling that cant play video in firefox 3.6.10 with maverick
[15:57] <charlie-tca> Can you reproduce it?
[15:58] <flipefr> no, becuase i am still using lucyd
[15:58] <flipefr> that's the other reason why i am asking
[15:58] <charlie-tca> If you don't have the ability to reproduce it, leave that bug alone and go to another one. It is better to allow someone else to work those maverick only bugs than to ask about each one here.
[15:59] <flipefr> ok
[15:59] <penguin42> which bug out of interest?
[15:59] <flipefr> but there lots of bug that i dont feel capable of reproduce
[15:59] <flipefr> anyway
[15:59] <flipefr> i leave it
[16:00] <charlie-tca> There are thousands of new bugs, surely you can reproduce some of them?
[16:00] <flipefr> maybe
[16:10] <flipefr> charlie-tca: true, i got another bug very easy to reproduce
[16:10] <flipefr> i marked it as confirmed
[16:12] <flipefr> charlie-tca: could you look at it and assign the importance you beleive it has
[16:12] <flipefr> ?
[16:23] <dyfet> I have a bug that can be marked at least triaged, #656926
[16:24] <hggdh> bug 656926
[16:24] <ubot2> Launchpad bug 656926 in openocd (Ubuntu) "ftbfs - on maverick fails on armel - sync openocd from debian unstable to universe (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/656926
[16:25] <hggdh> dyfet: what Importance you would like there?
[16:25] <dyfet> For armel users medium, everyone else would be low :)
[16:26] <dyfet> That is I feel it should be an update candidate
[16:26] <hggdh> done
[16:26] <hggdh> dyfet: you mean SRU to Maverick?
[16:26] <dyfet> Yes
[16:27] <hggdh> You can set it, by selecting Nominate to Release
[16:27] <flipefr> I have a bug that can be marked at least triaged, #656852
[16:27] <dyfet> ahh...I will do that then...if others disagree they can change it back :)
[16:27] <hggdh> dyfet: sorry, "Target to release"
[16:28] <dyfet> You mean Nominate for??
[16:28] <hggdh> flipefr: if you preceed the bug # by "bug ", this will print here data baout it -- like bug 656852
[16:28] <ubot2> Launchpad bug 656852 in nautilus (Ubuntu) "Nautilus does not copy/cut when using keyboard to find a file (affects: 1) (heat: 6)" [Undecided,Confirmed] https://launchpad.net/bugs/656852
[16:29] <hggdh> dyfet: on my view it is 'Target to release"....
[16:29] <flipefr> bug 656852
[16:29] <dyfet> Hmm...I see Nominate for release :)
[16:38] <flipefr> bug 656696 should be mark as wishlist, can anybody take a look over it?
[16:38] <ubot2> Launchpad bug 656696 in gcalctool (Ubuntu) "Horizontal scrolling is a poor solution (affects: 1) (heat: 6)" [Undecided,Opinion] https://launchpad.net/bugs/656696
[16:39] <flipefr> bug 656852 should be mark as triaged, can anybody take a look?
[16:39] <ubot2> Launchpad bug 656852 in nautilus (Ubuntu) "Nautilus does not copy/cut when using keyboard to find a file (affects: 1) (heat: 6)" [Undecided,Confirmed] https://launchpad.net/bugs/656852
[16:43] <hggdh> dyfet: for a release change (I did not look in detail) it is too late for Maverick. We might get it as a backport
[16:44] <penguin42> flipefr: You could upstream that calculator one
[16:44] <hggdh> flipefr:#656696 <- I cannot see it as an opinion
[16:45] <flipefr> hggdh: which status should it has?
[16:46] <penguin42> hggdh: I can kind of, he says their new design is broken which they may not agree with; but I agree with him as well - I think the prominent marker makes sense
[16:46] <hggdh> it should be New, until you can confirm it, then confirmed
[16:46] <hggdh> and -- I agree -- wishlist
[16:46] <flipefr> hggdh:confirmed then
[16:47] <hggdh> flipefr: then please go there and mark it so (just marked it New)
[16:48] <hggdh> penguin42: I agree, also in part. But I do not want to see 'Opinion' abused
[16:49] <penguin42> hggdh: Yeh
[16:49] <penguin42> flipefr: So upstream it
[16:49] <hggdh> yes indeed, upstreaming it would be very good, flipefr
[16:49] <drizzle> does apport work on kde?
[16:49] <hggdh> yes
[16:50] <flipefr> hggdh: i arked it as new, but i dont know hhow to upstream it
[16:52] <hggdh> flipefr: gcalctool is on bugzilla.gnome.org -- so you have to get there, and open a new bug on it (and, pretty much, copy the OP's description
[16:53] <hggdh> flipefr: once you have done that, ping me, and I will look at the b.g.o bug, and tell you what to do next
[16:57] <dyfet> hggdh: backport also could be appropriate.  Actually it effects the most technical users only (which happens to be a majority of the armel users presently ;), and with them knowing they simply can rebuild the package from sid successfully if needed, they probably will simply do that.  I thought it was a good update candidate in part because it's also a more trivial one only requiring a sync...
[16:57] <flipefr> hggdh: I created an account but dont know where to put the bug
[16:58] <hggdh> flipefr: you want to File a Bug;
[16:58] <flipefr> ok
[16:59] <flipefr> and now?
[16:59] <hggdh> you will be now asked on what; click on the "all" link, and search for gcalctool; click on it
[17:00] <penguin42> dyfet: It's just the build on armel? I guess most openocd users are driving the openocd on a PC driving an ARM on the other end
[17:00] <flipefr> hggdh:done
[17:01] <flipefr> hggdh: i paste the op's text in description
[17:02] <flipefr> hggdh: put severitu as normal, os as linux
[17:02] <hggdh> now -- as the FIRST line in the b.g.o description, add: "original Ubuntu bug: <the link for the UBuntu bug"
[17:02] <hggdh> flipefr: correct. Now, what version of gcalctool?
[17:03] <charlie-tca> This helps with those upstream reports - https://wiki.ubuntu.com/Bugs/Upstream
[17:04] <flipefr> hggdh: done, the version is 5.32
[17:04] <flipefr> hggdh: i marked it
[17:04] <hggdh> what is the bug #?
[17:05] <flipefr> 656696
[17:06] <hggdh> gnome bug 656696
[17:06] <hggdh> flipefr: I meant the Gnome bug #...
[17:07] <flipefr> hggdh: i didn't make commit
[17:07] <flipefr> yet
[17:08] <dyfet> penguin42: yes, arm specific only
[17:08] <penguin42> dyfet: Yeh I guess it's pretty rare to be running it that way
[17:08] <dyfet> (host)
[17:09] <dyfet> penguin42: hmm....that may well be true...then yes, it should actually be low priority
[17:09] <dyfet> and could keep until 11.04 :)
[17:09] <penguin42> Can anyone suggest what should be done with bug 636329 ?
[17:09] <ubot2> Launchpad bug 636329 in gimp (Ubuntu) (and 1 other project) "Gimp won't print preview (affects: 11) (heat: 62)" [Medium,Confirmed] https://launchpad.net/bugs/636329
[17:10] <penguin42> It's actually gimp won't print at all; that seems worthy of at least a mention in a Known Issues, and maybe an early update - any suggestions as to what to do?
[17:11] <charlie-tca> gimp prints here
[17:11] <penguin42> charlie-tca: Really?!
[17:11] <flipefr> hggdh: gnome number 620643
[17:11] <charlie-tca> printed several things out of it directly on maverick
[17:11] <penguin42> charlie-tca: can you pastebin a dpkg -l \*gimp\* ?
[17:12] <flipefr> hggdh: i committed it but i dont know if this the right number
[17:12] <flipefr> how can i find the bugs i opened
[17:13] <hggdh> I am on https://bugzilla.gnome.org/show_bug.cgi?id=620643
[17:13] <ubot2> Gnome bug 620643 in Touchpad "Horizontal Scrolling Broken" [Normal,Unconfirmed]
[17:13] <hggdh> flipefr: but I see no description at all, and no link to the Ubuntu bug
[17:13] <flipefr> hggdh: because that is not my bug
[17:13] <penguin42> charlie-tca: Think is I've got multiple people on there who've all had the problem and a confirmed fix that fixes it
[17:13] <flipefr> i mistake the number
[17:14] <flipefr> hggdh: how can i find the bug number now?
[17:14] <hggdh> flipefr: well, did you commit your bug, or not?
[17:14] <charlie-tca> penguin42: okay
[17:14] <flipefr> i commit it
[17:14] <flipefr> comitted
[17:14] <flipefr> hggdh: the sumary is horizontal scrolling
[17:15] <flipefr> hggdh: to make a search
[17:15] <charlie-tca> penguin42: http://paste.ubuntu.com/508892/
[17:15] <penguin42> charlie-tca: Hmm you're running with gutenprint - I'm not and I don't think the others were either
[17:16] <charlie-tca> gutenprint is what makes gimp print, isn't it?
[17:16] <penguin42> charlie-tca: Well, it seems more complex than that
[17:16] <penguin42> charlie-tca: Without gutenprint it just prints through the normal gnome print stuff
[17:17] <flipefr> hggdh: is there any way to see my own bugs?
[17:17] <penguin42> charlie-tca: With gutenprint I think it will produce the bitstream for the printer itself
[17:17] <charlie-tca> I didn't think it prints without gutenprint. With it, it just works
[17:17] <flipefr> hggdh:that's frustrating
[17:17] <penguin42> charlie-tca: Yeh well in Lucid it did print without gutenprint and with the 2 line fix in there it also does
[17:18] <flipefr> hggdh: the sumary is "horizontal scrolling in gcalctool"
[17:19] <flipefr> hggdh: i found it 631688
[17:20] <hggdh> flipefr: thank you. Just a sec
[17:20] <flipefr> hggdh: gnome bug 631688
[17:20] <ubot2> Gnome bug 631688 in general "horizontal scrolling in gcalctool" [Normal,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=631688
[17:20] <hggdh> flipefr: perfect! Now
[17:21] <flipefr> hggdh: thank you
[17:21] <penguin42> charlie-tca: OK, this is curious, so I've installed gimp-gutenprint and on my File menu on gimp I now have 2 options, Print and Print with gutenprint; selecting Print still produces a blank preview for me, gutenprint is separate
[17:21] <hggdh> flipefr: on the Ubuntu bug, click on "Also affects project", and add the link for the b.g.o bug
[17:21] <flipefr> hggdh: what about the other bug 656852
[17:21] <ubot2> Launchpad bug 656852 in nautilus (Ubuntu) "Nautilus does not copy/cut when using keyboard to find a file (affects: 2) (heat: 10)" [Undecided,Confirmed] https://launchpad.net/bugs/656852
[17:21] <flipefr> bug 656852
[17:22] <hggdh> flipefr: we are not yet done with the first bug
[17:22] <flipefr> hggdh: i thought it was, what's next?
[17:23] <charlie-tca> lets release note it, then, at least anybody reading them would know to try gutenprint, right/A
[17:23] <charlie-tca> ?
[17:23] <hggdh>  hggdh | flipefr: on the Ubuntu bug, click on "Also affects project", and add the link for the b.g.o bug
[17:24] <penguin42> charlie-tca: Yeh it makes sense - is there a way to suggest it gets into an update? It's a 2 line fix that the upstream guys have done and are getting into the next point release
[17:24] <flipefr> hggdh: done
[17:25] <charlie-tca> It should update for natty then, shouldn't it?
[17:25] <charlie-tca> With gimp not in Ubuntu by default, it takes a SRU or backport to update it in maverick
[17:26] <hggdh> flipefr: Cool. Now we can (and I have just done it) mark this Ubuntu bug as Triaged
[17:26] <hggdh> flipefr: congratulations, you have just upstreamed a bug!
[17:26] <penguin42> charlie-tca: Yeh I guess so, it's still a 'main' package
[17:26] <flipefr> hggdh: thanks again
[17:28] <flipefr> hggdh: and now, can you see the other bug #656852
[17:28] <ubot2> Launchpad bug 656852 in nautilus (Ubuntu) "Nautilus does not copy/cut when using keyboard to find a file (affects: 2) (heat: 10)" [Undecided,Confirmed] https://launchpad.net/bugs/656852
[17:30] <pedro_> that looks like a duplicate
[17:31] <charlie-tca> !info gimp
[17:31] <ubot2> charlie-tca: gimp (source: gimp): The GNU Image Manipulation Program. In component main, is optional. Version 2.6.8-2ubuntu1.1 (lucid), package size 4309 kB, installed size 12552 kB
[17:31]  * charlie-tca thought it was universe now
[17:34] <pedro_> flipefr, that works fine in Maverick for me, can you confirm it on Maverick as well?
[17:34] <hggdh> flipefr: oh, BTW, the OP's language seems to be Portuguese, not Spanish ;-)
[17:34] <hggdh> pedro_: thank you for taking over, I am not sure I understand what it is about...
[17:35] <micahg> charlie-tca: no, it's still seeded as well apparently
[17:35] <pedro_> hggdh, looks like it's about using ctrl+c on the nautilus find dialog, works fine here though, it indeed copy/paste the file
[17:36] <hggdh> oh OK
[17:36]  * pedro_ back to iso testing
[17:36] <flipefr> pedro_: i can't confirm it in maverick, but i confirm it in lycyd, and the bug is described in lucyd
[17:36] <pedro_> flipefr, then the bug is fixed on Maverick
[17:36] <pedro_> flipefr, it's a small issue and not likely to be a candidate to SRU
[17:37] <flipefr> hggdh: i thought with the name luis eduardo he would be spanish, it is a novel name, like a romantic hero xd
[17:37] <pedro_> flipefr, please comment on the report saying that you can't reproduce it on Maverick and ask for testing on that release to the reporter or just mark it as fix released
[17:37] <pedro_> either is fine
[17:40] <dyfet> bug 640572 can be triaged.  It involves a security vulnerability.
[17:40] <ubot2> Launchpad bug 640572 in moodle (Ubuntu) "Please Merge Moodle 1.9.4 in Maverick with Debian Unstable 1.9.9 - active security vulnerability (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/640572
[17:40] <flipefr> pedro_: done, i post a comment telling it dont happen in maverick and asking him for a test
[17:40] <pedro_> flipefr, thank you
[17:41] <nigelb> hi flipefr
[17:41] <nigelb> sorry, had a long week.
[17:42] <nigelb> I'm glad you're asking in the channel for help :)
[17:42] <pedro_> flipefr, btw when you ask something to the reporter like test in another release you should mark the bug as Incomplete
[17:42] <flipefr> pedro_: done
[17:43] <pedro_> thanks again ;-)
[17:43] <flipefr> nigelb: i always do
[17:43] <flipefr> pedro_: nothing
[17:43] <nigelb> flipefr: :)
[17:46] <hggdh> dyfet: since this is a security vulnerability, I would feel better if we wait for the sec folks to look at it first
[17:46] <hggdh> (although I think this would be triaged as well)
[17:46] <dyfet> hggdh: ok :)
[17:54] <enav> my volume control is not working  in a linear way...  this mean [123456]   instead of this is working like this [24655]   this could be defined as bug?...  btw im using 10.04 and i did't have this problem on 9.10
[17:54] <penguin42> enav: If it doesn't work right it's a bug!
[17:56] <enav> i reach the maximum volume at 1/4 longitud of the volume control and those 3/4 does nothing
[17:58] <penguin42> enav: I'm sure I've seen something similar
[18:00] <penguin42> enav: I could swear I reported a bug very similar to it but I can't find it
[18:00] <penguin42> ah
[18:00] <penguin42> enav: Bug 508733
[18:00] <ubot2> Launchpad bug 508733 in gnome-media (Ubuntu) "volume control app operates over ~25% of range (affects: 2) (heat: 17)" [Low,New] https://launchpad.net/bugs/508733
[18:00] <enav> i do some test in another computer and the volume control works fine... the problem must be driver related
[18:02] <enav> what i need to do  submit my machine specifications?
[18:03] <penguin42> enav: Probably follow the stuff in here: https://wiki.ubuntu.com/DebuggingSoundProblems
[18:05] <enav> no i mean co collaborate on the solution is a good idea submit my machine specifications?
[18:07] <penguin42> yeh, probably stuff from /proc/asound/cards and /proc/asound/card*/codec*
[18:17] <hggdh> given this is about the sound stack, it is better to open a new bug (unless you have verified, and your hardware exactly matches the OP's)
[18:17] <hggdh> BTW, chances are it does not match ;-)
[18:20] <JFo> in the vast majority of cases it won't
[18:22] <penguin42> can someone look at bug 615077
[18:22] <ubot2> Launchpad bug 615077 in virtinst (Ubuntu Maverick) (and 8 other projects) "[Maverick] SDL local window broken in last update (affects: 7) (dups: 2) (heat: 50)" [Medium,Confirmed] https://launchpad.net/bugs/615077
[18:22] <penguin42> I merged bug 656531 as a dupe, but he seems to be triggering it without the higher levels, yet Jamie StrandBoge has just closed the task against qemu-kvm as invalid saying it's only the upper layers - I'm not sure that's true or not
[18:22] <ubot2> Launchpad bug 656531 in libvirt (Ubuntu) "libvirt unable to start VM with SDL display (dup-of: 615077)" [Undecided,New] https://launchpad.net/bugs/656531
[19:08] <jelabarre> wanted to check if anyone had seen this particular bug in the RC install for 10.10 (couldn't find it on launchpad).
[19:08] <jelabarre> I did a fresh install from DVD (but preserved my home partition), and was reading some news articles while the install was running. When the install finished I was still reading, so I dismissed the "reboot" dialog (electing to continue working).  Now that I'm ready to reboot into the newly installed system, I don't see an option in the menus to reboot, only to lock screen, suspend or hibernate.
[19:10] <penguin42> jelabarre: I could swear I've seen someone else say they've seen that
[19:10]  * penguin42 hasn't though
[19:10]  * penguin42 disappears for a few mins
[19:20] <jelabarre> I haven't run a reboot on it yet, if there's a way to grab the install log (unless it's already been copied to the HDD already)
[19:29] <mrand> jelabarre: no option to logout?
[19:30] <jelabarre> nope
[19:33] <jelabarre> should be something under either the "System" menu, or the "Power" menu.  Nothing on either
[19:34] <jelabarre> granted, *I* know how to do a reboot, but I'm concerned about "newbie" users
[19:36] <AbhiJit> bye
[19:40] <mrand> jelabarre: I remember seeing a bug on that a long while back.  Unfortunate it hasn't been addressed.
[19:41] <mrand> Bug 515139 is one, but I think it was a different one.
[19:41] <ubot2> Launchpad bug 515139 in gnome-panel (Ubuntu) "Icons from gnome panel are missing at random on startup (affects: 4) (heat: 22)" [Low,Incomplete] https://launchpad.net/bugs/515139
[19:46] <jelabarre> random failure, just love those.  I suppose this would have to be tried on a system that doesn't have a pre-existing /home partition.  Probably should finish this setup and do another test install in a VM and see if I can duplicate it.
[19:47] <mrand> jelabarre: I found a forum thread discussing it, but no bug yet.
[19:51] <penguin42> jelabarre: Someone just asked on +1 about a similar failure with misisng shutdown etc
[19:51] <penguin42> ah, they have them they just don't work
[19:55] <micahg> jelabarre: have you checked in #ubuntu-testing?
[19:57] <jelabarre> could ask there.
[20:04] <mrand> It's been a random problem for some time now - certainly nothing unique to 10.10
[20:04] <micahg> oh, hmm
[20:15] <Darxus> Get:1 http://archive.ubuntu.com/ubuntu/ lucid/universe libplot2c2 2.6-0ubuntu1 [936kB]
[20:16] <Darxus> ^ That wasn't on mit.edu's mirror.
[20:16] <Darxus> E: Failed to fetch http://ubuntu.media.mit.edu/ubuntu/pool/universe/p/plotutils/libplot2c2_2.6-0ubuntu1_amd64.deb: 404  Not Found
[20:26] <hggdh> Darxus: and?
[20:26] <hggdh> we do not control MIT's mirror...
[20:27] <Darxus> I just emailed the people who do.
[20:29] <hggdh> Darxus: meanwhile, this may help: https://edge.launchpad.net/ubuntu/+archivemirrors
[20:29] <micahg> ubuntu3 is the current version, that's why you get the 404
[20:30] <micahg> Darxus: ^^
[20:30] <micahg> hggdh: ^^
[20:31] <hggdh> micahg: yes, this would be a good enough reason ;-)
[20:40] <Darxus> Except that I did an aptitude update right before that.
[20:42] <Darxus> I suppose hugin could have a broken dependancy.
[20:43] <Darxus> libplot2c2 2.6-0ubuntu1 is the one that ended up getting installed when I switched to the main archives.
[20:44] <Darxus> micahg: Ah, ubuntu3 is the latest for maverick, but I'm running lucid, which is ubuntu1.
[20:46] <hggdh> Darxus: indeed
[20:51] <dyfet> Bug 607896 can be triaged
[20:51] <ubot2> Launchpad bug 607896 in griffith (Ubuntu) (and 1 other project) "Please sync Griffith 0.12-1 from Debian (unstable) to Maverick - updated dependency (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/607896
[20:54] <micahg> Darxus: ah, yeah, that would be a mirror issue then :)
[20:55] <BUGabundo> evening
[21:02] <Darxus> Yeah.  I mostly mentioned it here because I wanted to mention it somewhere before I forgot about it.
[21:12] <hggdh> BUGabundo: boas
[21:12] <BUGabundo> ola hggdh
[21:16] <charlie-tca> Hello, BUGabundo
[21:18] <BUGabundo> hey charlie-tca
[21:31] <devildante> hey guys :)
[21:34] <charlie-tca> hello, devildante
[21:34] <devildante> hi charlie-tca :)
[21:37]  * devildante brb rebooting
[22:36] <dyfet> I think bug 657024 can be marked as triaged
[22:36] <ubot2> Launchpad bug 657024 in ziproxy (Ubuntu) "please sync/merge 3.1.3-1 from debian (unstable) to Maverick (universe) - security vulnerability (affects: 1) (heat: 262)" [Undecided,New] https://launchpad.net/bugs/657024
[22:36] <dyfet> already reviewed by security team
[22:38] <dyfet> same for bug 657035
[22:38] <ubot2> Launchpad bug 657035 in babiloo (Ubuntu) "please sync from debian (unstable) 2.0.11-1 - security vulnerability (affects: 1) (heat: 260)" [Undecided,New] https://launchpad.net/bugs/657035
[23:48] <Tetsuo55> huh? where did all my bugs go?
[23:50] <Tetsuo55> did something change on launchpad
[23:50] <Tetsuo55> ?
[23:50] <Tetsuo55> nevermind, i seem to be logged out for some reason
[23:50] <penguin42> mine are still there - any particular ones?
[23:53] <wgrant> Tetsuo55: Some DB maintenance yesterday caused most people to be logged out.
[23:54] <Tetsuo55> that maintenance thing must be it
[23:54] <Tetsuo55> another question
[23:55] <Tetsuo55> why doesnt this bug show up in my list? 612816
[23:55] <Tetsuo55> im affected and subscribed, but i dont see it when i look at my related bugs list
[23:55] <Tetsuo55> bug 612816
[23:55] <ubot2> Launchpad bug 612816 in xserver-xorg-video-intel (Ubuntu) "[MASTER] [gm45] GPU lockup 493062ea (EIR: 0x00000010 PGTBL_ER: 0x00000001) (affects: 8) (dups: 5) (heat: 114)" [Medium,Confirmed] https://launchpad.net/bugs/612816
[23:56] <penguin42> Tetsuo55: Does it show up in your subscribed list?
[23:56] <Tetsuo55> no it doesnt
[23:57] <penguin42> interesting since you appear to be subscribed by a dupe
[23:57] <penguin42> maybe ask in #launchpad
[23:59] <Tetsuo55> ok
[23:59] <penguin42> ask and stick around, it's not normally very lively in there


[04:13] <nhaines> pleia2: pretty - http://2.bp.blogspot.com/-dHLjjxdYEmY/UHCUers09BI/AAAAAAAAJpk/nwXWr94Mi4s/s1600/wallet1210.png
[04:13] <darthrobot`> Content type: [image/png] Size: [170141]
[05:41] <pleia2> nhaines: nice, are they having cds printed, or just a mockup for fun?
[05:43] <nhaines> pleia2: I don't know.  :)
[05:43] <bkerensa> Evening
[05:59] <nhaines> pleia2: Ah, I think it's just for DIYMarketing or whatever they call the wiki page with all the art on it these days.
[06:00] <pleia2> ah
[06:07] <nhaines> I think I'm just recommending people stick with 12.04 LTS and not install 12.10.  :(
[16:12] <pleia2> meeting tonight at 7