[03:11] <j1mc> anyone around?
[03:11] <sommer> j1mc: yo
[03:11] <j1mc> hi sommer
[03:11] <j1mc> i'm putting the finishing touches on xubuntu docs.  cody somerville was going to help me build them, but i think he's a little busy lately.
[03:12] <j1mc> i was hoping someone could help me.
[03:12] <sommer> uh, I *may* be able to
[03:12] <sommer> have you built a package before?
[03:13] <j1mc> nope.  not one.
[03:13] <j1mc> :)
[03:13] <sommer> that's cool, it's really not that hard
[03:14] <sommer> best place to start is the packaging guide: https://wiki.ubuntu.com/PackagingGuide
[03:14] <j1mc> i think i can ping mrpouit for help.  cody said that he'd be willing to help me out (i just remembered)
[03:15] <sommer> cool, the getting started link will point you to which packages to install
[03:16] <sommer> I've never actually built the doc package, but if you have any specific questions just let me know
[03:19] <j1mc> thanks, sommer
[03:19] <j1mc> the server docs have really improved a lot for this release.  i think it's great.
[03:20] <sommer> thanks, they were in need of a few updates :-)
[03:21] <j1mc> :)
[03:22] <sommer> also mdke can probably answer any package related questions, but he's probably not on at the moment
[03:26] <j1mc> sommer: do you have access to updating the ubuntu global.net file?  the kernel version listed isn't correct.
[03:26] <j1mc> it says 2.6.22, and hardy uses 2.6.24
[03:26] <sommer> I think you should be able to update it
[03:27] <j1mc> ok
[03:27] <sommer> I did ask mdke about it and he recommended to update all branches
[03:27] <sommer> and since I don't have them all checked out, he said he'd update it
[03:27] <sommer> if you have them checked out I'd say go ahead and update it
[03:28] <j1mc> i don't know about glibc, but i've checked the other ones.
[03:29] <sommer> heh, I'd imagine that glibc has been updated as well
[03:31] <j1mc> would it be under package libc6  (do an apt-cache show libc6)  i show version 2.7 for glibc, based on that
[03:33] <sommer> ummm... I think so, but you might want to double check
[03:35] <j1mc> /lib/libc.so.6  (entering that command gave me the info)
[03:36] <sommer> ah, I guess I'm not 100% sure, is libc the same as glibc?  isn't glib a gnome library?
[03:37] <sommer> I'd imagine it is
[03:37] <sommer> cause there isn't a glibc in dpkg -l | grep glib
[03:37] <j1mc> but wouldn't the "g" stand for gnu?
[03:37] <j1mc> gnu c library?
[03:38] <sommer> heheheh... yep, your right
[03:38] <sommer> I think I was thinking of gtk or something
[03:38] <j1mc> :)
[03:55] <j1mc> sommer: what did i just do??
[03:56] <j1mc> all of the updates are there, but the history isn't correct now.
[03:56] <j1mc> crap
[03:56] <j1mc> mdke is going to kill me.
[03:58] <sommer> the history isn't correct?
[04:00] <sommer> which commit do you mean?
[04:02] <j1mc> check your email
[04:02] <sommer> how about 3656
[04:02] <sommer> did you do a bzr push after a bzr merge?
[04:03] <nixternal> j1mc: my battery died
[04:03] <j1mc> ah, ok
[04:03] <j1mc> sommer: yes
[04:04] <j1mc> sommer: all of the docs are ok in terms of content, but the history is screwed up
[04:04] <sommer> it's not a big deal (I don't think) what happens is that a merge affects your local copy
[04:04] <nixternal> j1mc: it is right on LP and my local history
[04:04] <nixternal> the history matches just fine here
[04:05] <j1mc> https://code.launchpad.net/~ubuntu-core-doc/ubuntu-doc/ubuntu-hardy
[04:05] <sommer> so when you then push it the repo the history goes along as well
[04:05] <sommer> I'm pretty sure it's just a bzr thing
[04:05] <sommer> heh... sort of a pun ;)
[04:06] <j1mc> sommer: yeah, but it still sucks.  and why doesn't it happen to other people?
[04:06] <sommer> I've done a bzr bind on my check out, which makes it act pretty much the same as svn
[04:06] <sommer> when I do bzr commit it automatically goes to the repo
[04:07] <sommer> you can find the command to bind the repo at the bottom of the repository wiki page
[04:07] <sommer> I think it's just bzr bind bzr+ssh://path/to/repo, but you'll probably want to confirm that
[04:10] <j1mc> i found it...
[04:10] <j1mc> thanks.
[04:10] <j1mc> is there any way to fix this, though?
[04:10] <j1mc> i'm embarrassed.
[04:10] <sommer> don't be, others have done the same thing, and the content is the important thing anyway
[04:11] <j1mc> i guess this way it will make it look like i wrote all of the documentation for ubuntu, though.
[04:11] <j1mc> which is great.
[04:12] <j1mc> um... but i wish there were a way to fix it.  obvs...  you all have accurate local histories at this point.
[04:12] <j1mc> CRAP!  i was trying to be helpful.
[04:12] <sommer> there probably is, but I'm far from a bzr expert
[04:13] <j1mc> i'll ask in bzr
[04:13] <j1mc> #bzr
[04:21] <nixternal> damn, the firefox start pages are a mess
[04:22] <kgoetz> :(
[04:22] <j1mc> kgoetz: :(
[04:23] <kgoetz> j1mc: i was watching your bzr question - i did the same thing to myself a while ago
[04:25] <j1mc> mdke: sommer nixternal http://pastebin.ca/948485
[04:27] <sommer> j1mc: wow... we should turn on that options, heh
[04:28] <j1mc> yeah
[04:28] <sommer> I really wouldn't sweat it, ping mdke tomorrow and see what he wants to do
[04:29] <sommer> maybe send an email to the doc ml to expect a few messages, then do the proposed fix?
[04:29]  * kgoetz suspects now is a bad time to run bzr up
[04:29] <kgoetz> s/up/merge
[04:29] <sommer> I updated, but then I'm also working in an update :-)
[04:30] <j1mc> yeah, a day before string freeze i screw up the history.
[04:31] <j1mc> trying to be helpful
[04:31]  * kgoetz passes j1mc the lamp of shame
[04:31] <kgoetz> :P
[04:31]  * j1mc puts on lampshade
[04:32] <sommer> no worries, the history shouldn't be affected by the freeze
[04:32] <sommer> at least I don't think it gets translated, heh
[04:35] <j1mc> entering the command "bzr log --show-ids > ~/Desktop/ids" does show everything correctly.
[04:36] <j1mc> (i sent the output to a file cos there's a lot of it)
[04:36] <j1mc> i sent matthew a note about it
[04:37] <j1mc> he probably won't be available for a while now cos he's flying over from england to kick my ass.
[04:37] <kgoetz> hehe
[04:37] <sommer> lol, just get in some good quick shots while he's jet lagged
[04:49] <nixternal> bzr commit --fixes lp:bug_num
[04:49] <nixternal> great flag right there...never knew about it until just now
[04:49] <nixternal> it will add a link in the description showing the new fix
[04:49] <j1mc> bzr bind... how about that one?
[04:49] <j1mc> that's the best one ever
[04:49] <nixternal> hell no
[04:49] <nixternal> bzr co
[04:49] <nixternal> that's all I do
[04:50] <j1mc> but you can't commit locally if you do a co
[04:50] <nixternal> don't need to
[04:50] <nixternal> all of my fixes go right into the repo for everyone
[04:51] <nixternal> when it comes to funky setups, I am not a bzr fan
[04:51] <nixternal> Mercurial and git are good for funky stuff like that ;p
[04:51] <kgoetz> hehe. when it comes to funky setups i still think patches are cool :P
[04:51] <nixternal> very true, I am with you there
[04:52] <nixternal> I like the bundles feature of mercurial
[04:52] <j1mc> i would be much happier right now if i had just done bzr diff > patch and emailed someone.
[04:52] <nixternal> lol
[04:52] <j1mc> F*CK
[04:52] <kgoetz> hehe
[04:52] <nixternal> and with bzr co, I don't have to worry about mucking up the history :p
[04:53] <j1mc> with bzr bind you don't have to worry about mucking up history either
[04:53] <nixternal> j1mc: did those fixes in pastebin work?
[04:53] <j1mc> i haven't tried.
[04:53] <j1mc> i don't want to send out 108 emails to the entire doc team from launchpad.
[04:53] <j1mc> not w/o people being aware of it
[04:54] <nixternal> j1mc: oh well, mdke and I did it from dapper -> feisty with translations
[04:54] <nixternal> we have like 6mb emails too :)
[04:54] <nixternal> s/have/had
[04:55] <nixternal> to bad there isn't such a thing like 'svn commit -m "SVN_SILENT: foo foo foo foo"'
[04:55] <nixternal> as long as the triggers are added
[04:55] <j1mc> right...
[04:55] <kgoetz> hehe
[04:56] <j1mc> do you think i should try the comment from lifeless?  he's an old hand at bzr development, so i trust him.
[04:56] <nixternal> I would
[04:56] <nixternal> if it messes up, blame him :p
[04:57] <j1mc> kgoetz: what do you think?
[04:58] <kgoetz> j1mc: i rec'n you should try it out.
[04:58] <sommer> +1 from me, what's the worste that could happen :-)
[04:59] <kgoetz> j1mc: we all support your actions, until you send the emails :P
[04:59] <nixternal> haha
[05:01]  * j1mc goes to join #bzr again to ask another question
[05:01]  * kgoetz watches
[05:01]  * nixternal laughs
[05:02] <j1mc> haha
[05:05] <sommer> hrmm... doc.u.c doesn't seem to be updated
[05:08] <j1mc> you need to make sure you refresh the page
[05:08] <j1mc> i've encountered that quite a bit
[05:09] <j1mc> we could all set our email notifications to "no emails" and then turn it back on.
[05:10] <j1mc> https://code.launchpad.net/~ubuntu-core-doc/ubuntu-doc/ubuntu-hardy  > edit subscription
[05:14] <j1mc> kgoetz: are you following in #bzr?  any thoughts?
[05:16] <kgoetz> j1mc: let me read up (being tought perl by my boss atm...
[05:18] <kgoetz> i think you branch from the last commit befor yours. try it out, just stop following lifeless' steps where you commit back to LP :)
[05:42] <j1mc> kgoetz: or sommer ... could one of you do "bzr log --show-ids > ~/Desktop/ids" and pastebin the top of the output from that log?
[05:44] <kgoetz> sommer: is probably your best bet
[05:44] <kgoetz> as my repo is about a week old (when i last hacked on the docs)
[05:44] <j1mc> right... and he committed the last valid commit.
[05:52] <sommer> j1mc: the file is pretty big
[05:52] <j1mc> sommer: right...
[05:52] <j1mc> bzr log --show-ids > ~/Desktop/ids
[05:52] <sommer> want me to email it to you
[05:53] <j1mc> sure
[05:53] <j1mc> jwcampbell ate gmail.com
[05:54] <sommer> on the way
[05:55] <j1mc> thanks...
[05:56] <kgoetz> *grin* @ ate
[05:56] <j1mc> :)
[05:56] <sommer> np, bed time for me
[05:56] <sommer> later all
[05:56] <j1mc> ok...
[05:56] <j1mc> thanks!!
[05:56] <kgoetz> later mate
[05:57]  * kgoetz nurses his could-happen-but-just-on-edge-currently rsi
[05:58] <j1mc> rsi?
[05:58] <kgoetz> repeditive strain injury
[05:58] <j1mc> :(
[05:58] <kgoetz> eg, typing
[05:59]  * kgoetz reads doco to try and avoid pain
[06:03] <j1mc> i have the command ready, but i'm just apprehensive
[06:03] <j1mc> bzr branch -r revid:asommer70@gmail.com-20080318135647-hbbpj5bl819nu1oa trunk local; cd local; bzr merge -r revid:jwcampbell@gmail.com-20080315024243-bzrus01hxn3r6v9y ../trunk; bzr commit; bzr push --overwrite ../trunk
[06:07] <kgoetz> i understand your nervousness
[06:07] <kgoetz> want my advice?
[06:07] <j1mc> sure
[06:07] <kgoetz> run ` bzr commit; bzr push --overwrite ../trunk` as a second command
[06:07] <kgoetz> and check what has changed after the first bit runs
[06:08] <j1mc> my gut is to send the chat info to mdke and let him decide
[06:08] <j1mc> what do you think?
[06:08] <kgoetz> i think run the first bit, and if your not positive it'll do what you want, wait for mdke
[06:09] <j1mc> "the first bit" being...
[06:09] <kgoetz> 16:33 < j1mc> bzr branch -r revid:asommer70@gmail.com-20080318135647-hbbpj5bl819nu1oa trunk local; cd local; bzr merge -r revid:jwcampbell@gmail.com-20080315024243-bzrus01hxn3r6v9y ../trunk;
[06:09] <kgoetz> s/;$/$/
[06:10] <kgoetz> eg. stopping before you commit back
[06:10] <j1mc> and then checking the log...
[06:10] <j1mc> good idea
[06:11] <kgoetz> :)
[06:14] <j1mc> hm, this may take a while
[06:15] <j1mc> it's going though
[06:16] <kgoetz> it may take a while yeah :)
[06:16]  * kgoetz wonders if theres been any updates to the [ed,k]ubuntu docs (if there hasnt, no need for me to pull again)
[06:26] <nixternal> just firefox startpage updates
[06:27] <nixternal> probably make a few changes tomorrow if I have time
[06:27] <kgoetz> cutting it fine :)
[06:31] <nixternal> as fine as possible...tend to do that every release
[06:46] <j1mc> woot
[06:46] <j1mc> http://bazaar.launchpad.net/~ubuntu-core-doc/ubuntu-doc/ubuntu-hardy/changes
[06:46] <j1mc> i fixed it
[06:48] <kgoetz> :D
[06:49] <j1mc> kgoetz: are you getting a flood of emails?
[06:49] <kgoetz> j1mc: i'm not part of docteam
[06:49] <j1mc> ah, ok
[06:50] <kgoetz> i'm heading to dinner+ home
[06:50] <kgoetz> catch you later all
[06:52] <j1mc> later!
[06:52]  * j1mc goes to bed
[07:00] <George> New bug: #203827 in ubuntu-doc "serverguide error" [Undecided,New] https://launchpad.net/bugs/203827
[07:05] <George> New bug: #203829 in ubuntu-doc "server guide error" [Undecided,New] https://launchpad.net/bugs/203829
[07:49] <cge> I'm not sure if this is the right place to ask, but I'm rather confused by the MacBookPro page on the wiki (https://wiki.ubuntu.com/MacBookPro). Why does it have a bizarre warning at the beginning, before a bunch of random information about things like proprietary programs for theming vista? Is the warning at all valid, or is it just the result of some misinformed editor?
[07:52] <mdke> cge: that is seriously weird
[07:52] <cge> mdke: There seems to be a group of one or two editors very strongly responding to any attempts to remove some of the stuff.
[07:53] <cge> I can't figure out how to get information on the launchpad users behind the usernames, so I have no idea who they are.
[07:54] <mdke> yeah
[07:54] <mdke> there are clearly parts of the page that are inappropriate
[07:54] <mdke> also, the whole page should be moved to help.ubuntu.com
[07:54] <cge> I was wondering why it was on wiki.ubuntu, yes.
[07:55] <mdke> I'll move it now, it will provide an opportunity to remove the vista stuff
[07:55] <cge> thank you
[08:04] <mdke> cge: moved. I've deleted the sections dealing with Windows and OSX - I will try and contact the author to discuss
[08:05] <cge> Very good - thank you. I'll also try to update it if I have time in the next few days.
[13:15] <sommer> mdke: I don't think doc.u.c has been updated for a while... at least the latest serverguide changes aren't showing up :-)
[20:05] <ubotu> New bug: #204030 in ubuntu-docs (main) "package ubuntu-docs 7.10.5 failed to install/upgrade: fork falhou" [Undecided,New] https://launchpad.net/bugs/204030
[20:12] <l3on> Hi... I'm walking into wiki and find this page: https://wiki.ubuntu.com/KennethBaafour
[20:13] <l3on> Nothing strange by a quick look... but look at attachfiles ;)
[20:13] <l3on> Here is the right place to comunicate it?
[20:17] <l3on> mdke: are you there?
[21:34] <cge> Now we're going to have a revert war on https://help.ubuntu.com/community/MacBookPro it seems. I had hoped that sort of thing was limited to Wikipedia...
[21:37] <seisen> somebody delete before?
[21:38] <cge> A user keeps adding a bunch of stuff about Vista themes, games, and whatnot, and keeps adding it back in whenever anyone removes it, even if it's mdke doing the removal...
[22:18] <mdke> l3on: what's up?
[22:21] <l3on> mdke: files attached to https://wiki.ubuntu.com/KennethBaafour were full of spam...
[22:21] <l3on> linked to porn site & co...
[22:21] <l3on> I deleted them...
[22:22] <mdke> l3on: thanks for doing that. You can also report the username responsible in #launchpad and ask for the account to be deactivated
[22:22] <l3on> mdke: controll before ;)
[22:23] <mdke> l3on: sorry?
[22:25] <l3on> nothing mdke, I've read that you'll contact them... I've read wrong :P
[22:25] <mdke> :)
[22:26] <l3on> ;)