[02:26] <jsgotangco> hi
[02:44] <jjesse> did the edubuntu docs get uploaded into our svn yet?? i though someone mentioned it at the last doc team mtg?
[03:01] <jsgotangco> i am not aware..i haven't been in the loop lately
[03:09] <LaserJock> jjesse: well, we are supposed to get Edubuntu Handbook material sometime
[03:10] <LaserJock> jjesse: and I think they wanted to put an Edubuntu pamphlet that was done for Dapper on help.ubuntu.com as well
[03:19] <jsgotangco> hey LaserJock
[03:34] <LaserJock> hi jsgotangco
[05:00] <nixternal> let me guess. problems around here ;)
[05:00] <LaserJock> hm?
[05:01] <nixternal> whats up LaserJock
[05:01] <jsgotangco> hey
[05:01] <nixternal> whats up jsgotangco
[05:01] <jsgotangco> nothing much
[05:02] <jsgotangco> just looking for changes at the gnome wiki
[05:02] <LaserJock> not a whole lot here
[05:02] <LaserJock> I'm going to try to work on some stuff
[05:02] <nixternal> seems it has been pretty quiet..thats good..i bet it gets noisey come friday afternoon when the vacation is over with ;)
[05:02] <LaserJock> jsgotangco: I got an email back from the debian refernce maintainer, did I tell you that?
[05:03] <jsgotangco> yeah me too, its been a while since ive slacked ever since i discovered online fragging on the DS
[05:03] <jsgotangco> LaserJock: hmm i think so
[05:03] <jsgotangco> i can't seem to recall
[05:03] <jsgotangco> are we forking?
[05:03] <LaserJock> I'll need to take a deep look into that, and it's not yet clear when I
[05:03] <LaserJock> have time for that. But that's on my todo-list.
[05:03] <LaserJock> ^^ is all he sent me
[05:04] <LaserJock> soooo
[05:04] <jsgotangco> lol
[05:04] <LaserJock> I have no idea if that means a couple weeks, or a couple years
[05:04] <jsgotangco> forking sounds good
[05:09] <LaserJock> jsgotangco: well, I still don't know what to do, I should test how easy it is to convert debiandoc to docbook
[07:21] <Laser_away> jsgotangco: you still around?
[07:21] <jsgotangco> of course its only 1:20PM
[07:21] <jsgotangco> :)
[07:24] <jsgotangco> Laser_away: what's up?
[07:24] <Laser_away> jsgotangco: oh
[07:25] <Laser_away> jsgotangco: well, I was looking at debiandoc2xml
[07:25] <jsgotangco> i have judas priest on my track list i definitely won't sleep ;)
[07:25] <jsgotangco> okay
[07:25] <Laser_away> basically I just gave it the developers-reference.sgml
[07:25] <Laser_away> and it spat out nice docbook chapters
[07:25] <jsgotangco> wow
[07:25] <Laser_away> that rendered pretty well in yelp
[07:26] <jsgotangco> no tag hacks done?
[07:26] <Laser_away> it looked ok to me
[07:27] <jsgotangco> that's nice but i wonder how much work still needs to be done to adapt to it
[07:27] <Laser_away> I just had to change some non-unicode characters for some accented letters in somebodies name
[07:27] <jsgotangco> the d-i manual basically grep'ed some words then changed it with some modifications as well
[07:27] <jsgotangco> so i guess we'll have to do the same approach
[07:28] <Laser_away> I wonder if we can just keep modifing the debian doc and if they move to docbook before edgy is released I think we can pretty easily merge
[07:28] <Laser_away> and if not we are ok
[07:28] <jsgotangco> yeah
[07:28] <Laser_away> anyway, I gotta go
[07:28] <Laser_away> bed time here
[07:28] <jsgotangco> Laser_away: when do you want to start?
[07:28] <Laser_away> soon
[07:28] <jsgotangco> this month is pretty free for me
[07:29] <Laser_away> I'll talk to you tommorow about it
[07:29] <jsgotangco> okay
[07:29] <Laser_away> goodnight
[07:29] <jsgotangco> thanks
[08:32] <Burgundavia> finally, a story about gai! http://www.wiredwriter.net/index.html?page=Tutorials#add
[08:36] <jsgotangco> oohhh
[08:37] <Madpilot> cool, doesn't look like the author got too much wrong
[08:37] <Burgundavia> nope
[08:40] <jsgotangco> hmm not much really
[09:00] <mdke> morning
[09:02] <Burgundavia> morning mdke
[09:07] <jsgotangco> hi
[09:33] <neilc_> hello
[09:39] <jsgotangco> hey
[10:03] <Burgundavia> night
[10:26] <mdke> mvirkkil: another bug for you on moin->docbook
[10:27] <mdke> mvirkkil: when generating this page (http://docbook.wikiwikiweb.de/MatthewEast/Participate) the resulting docbook was missing a space after the <ulink> tags (see https://lists.ubuntu.com/archives/ubuntu-doc-commits/2006-August/002708.html for the corrections)
[10:29] <mdke> mvirkkil: oh hang on, it seems to be ok in the docbook generated by the wiki, it's tidy that has caused the damage I think
[12:01] <bhuvan> mdke: ping
[12:01] <mdke> bhuvan: yep
[12:02] <bhuvan> do you have access to ubuntu-doc repo ?
[12:02] <bhuvan> i meant direct access
[12:02] <mdke> no
[12:02] <mdke> why?
[12:03] <bhuvan> ok; i've a suggestion. i'm unsure how useful it'll be.
[12:03] <bhuvan> will it be useful if we enable a bot to send commit messages to this channel as soon as it was committed
[12:03] <mdke> would be nice, sure
[12:05] <bhuvan> visit http://cia.navi.cx for details. by default the commit messages are forwarded to #commits channel and we can also redirect it to any channel we wish. to implement, all we need is to install (copy) a script to hooks dir in our repo
[12:06] <mdke> I could arrange that
[12:06] <bhuvan> oh excellent, thank you!
[12:07] <mdke> bhuvan: can you send me the script?
[12:07] <bhuvan> btw, i dont see this setup for any of ubuntu projects (motu, artwork, doc, etc). would be useful if we do that as well (or atleast inform the lead)
[12:07] <bhuvan> sure.http://cia.navi.cx/clients/svn/ciabot_svn.py
[12:08] <mdke> and I need to amend the script to specify the channel?
[12:09] <bhuvan> nope; by default it'll send it to #commits channel. we need to contact someone<EMAIL_ADDRESS>to forward it to this channel.
[12:10] <mdke> fine
[12:11] <bhuvan> mdke: we can edit the script and change the project name, repositoryURI, revisionURI (as we have viewVC)
[12:11] <mdke> and it drops into the hooks directory?
[12:12] <mvirkkil> mdke: Ok.
[12:12] <mdke> how are the commit messages forwarded? the bot joins this channel and uses a normal message
[12:12] <mdke> how are the commit messages forwarded? the bot joins this channel and uses a normal messag/win 13
[12:12] <mdke> argh
[12:14] <bhuvan> mdke: yes. in addition, edit post-commit.tmpl to run this script (ciabot_svn.py)
[12:14] <mdke> bhuvan: alright, the instructions in the script look sufficient, I'll send it off
[12:15] <bhuvan> mdke: ok. yes, the bot (CIA-XX will join this channel and post the commit messages automatically). you can join #commits channel to view the snippet though it looks bit ugly as it prints the commit messages of *many* open source projects
[12:16] <mdke> yeah, nice suggestion, thanks
[03:10] <jjesse> ubuntu book comes out on the 4th :)
[03:11] <mdke> at last!
[03:11] <jjesse> ranked 10,943 or something like that
[03:11] <jjesse> all i know is prentince hall has some google mojo
[03:11] <jjesse> do a search for jonathan jesse :)
[03:12] <jsgotangco> braggart!
[03:12] <jsgotangco> :)
[03:12] <mdke> says something about a porn star
[03:12] <jsgotangco> wooooo
[03:12] <jjesse> well i didn't want anyone to know that about me....
[03:19] <jjesse> mdke: i had Laser_away upload my patch to the release notes, should i see changes on doc.ubuntu.com?
[03:20] <jjesse> i'm trying to fix bug 48525
[03:20] <Ubugtu> Malone bug 48525 in kubuntu-docs "Problems with Dapper Release Notes for Kubuntu" [Medium,Confirmed]  http://launchpad.net/bugs/48525
[03:20] <mdke> jjesse: doc.ubuntu.com deals with what is in trunk, if you made the changes in branch you won't see them
[03:20] <jjesse> mdke: i would assume that Laser_away uploaded to trunk yesterday
[03:21] <mdke> jjesse: what was your patch on?
[03:21] <jjesse> release notes
[03:21] <mdke> in trunk or branches/dapper?
[03:21] <jjesse> in trunk
[03:21] <mdke> I see
[03:21] <mdke> you should use branches/dapper if you want to make changes for dapper
[03:21] <jjesse> trunk/kubuntu/releasenotes/C/releasenotes.xml
[03:22] <mdke> but yes, it should appear on doc.ubuntu.com since the changes were done to trunk
[03:22] <jjesse> well i would like some feedback on them which is why i uploaded to trunk instaed of brnaches
[03:23] <mdke> trunk and branches were the same?
[03:23] <jjesse> yes
[03:23] <mdke> alright then, I forgive you
[03:23] <jjesse> thanks
[03:23] <mdke> lemme check if it is building right
[03:24] <jjesse> i validated it and Laser_away did before he committed
[03:24] <mdke> no, it isn't included in the build
[03:24] <mdke> I'll fix that
[03:24] <jjesse> i just don't have my svn password here at work
[03:26] <mdke> jjesse: ok, let me know if it is working now
[03:27] <mdke> jjesse: ok, let me know if it is working now
[03:27] <jjesse_> will do thanks
[05:20] <mdke> jjesse_: any luck?
[05:55] <locutus_> Could anyone help me with a sound problem?
[05:56] <mdke> locutus_: #ubuntu
[05:56] <mdke> they can help
[05:56] <locutus_> mdke: Same server?
[05:56] <mdke> yep
[05:56] <locutus_> TX.
[06:54] <jjesse_> why do so many people post support requests either here or on the mailing list?
[09:11] <jjesse> mdke: still haven't seen doc.ubuntu.com update how long does it take?
[09:37] <mdke> jjesse: I did it manually while we were speaking earlier
[09:40] <jjesse> still show the old text under release notes for kubuntu
[09:40] <jjesse> it shouldn't have the "Whaoo a sweet installer" stuff
[09:42] <mdke> I'll try a rebuild
[09:42] <mdke> now?
[09:43] <jjesse> hmm this is what is supposed to be in trunk/kubuntu/releasenotes?
[09:45] <jjesse> on what i've built on my workstation there is a section titled "Changes to the Kubuntu Installer"
[09:45] <jjesse> and on doc.ubuntu.com it shows "Installing Kubuntu"
[09:47] <mdke> jjesse: so when you do "make release-notes" in trunk/kubuntu on your local system, it is different to what you see there?
[09:47] <jjesse> double checking
[09:49] <LaserJock> mdke: are you going to start doing doc.ubuntu.com builds via cron again?
[09:49] <mdke> (ensure you haven't got any changes to your local system that haven't yet been committed)
[09:49] <mdke> LaserJock: they are still done by cron
[09:49] <jjesse> mdke: correct i'm looking at ubuntu-doc/trunk/build/kubuntu/release-notes/C/documen.html
[09:49] <jjesse> and it is different then what is at doc.ubuntu.com
[09:49] <LaserJock> mdke: hmm, well it looked like the status reports weren't getting build
[09:49] <mdke> LaserJock: possibly, check in the makefile if it is working
[09:49] <jjesse> the patch i had sent yesterday that LaserJock committed should match what is on my system
[09:50] <LaserJock> mdke: ah, k
[09:50] <mdke> http://doc.ubuntu.com/kubuntu/release-notes/C/document.html
[09:50] <mdke> jjesse: looks right to me
[09:50] <mdke> "Changes to the Kubuntu Installer"
[09:51] <jjesse> does it have "Wahoo a sweet instalelr"
[09:51] <jjesse> ah wait just changed
[09:51] <jjesse> maybe i had a cached version in my browser?
[09:51] <jjesse> hmmm sorry bout tthat
[09:51] <mdke> possibly
[09:51] <mdke> np!
[09:51] <mdke> i'm off for a bit, cya later
[09:51] <jjesse> bye
[10:01] <LaserJock> jjesse: need me to apply your ent patch?
[10:01] <jjesse> yes please :)
[10:01] <jjesse> just starting to work on edgy release notes and wanted to get some things chagned :)
[10:04] <LaserJock> done
[10:05] <jjesse> thanks
[10:08] <LaserJock> mdke: hmm, I can't find anything in the makefiles for doing the status reports, did we remove that?


 @teward001 Any chance you can trigger a rebuild of Agordejo? The issue with Nuitka is fixed.
 Nvm, it's fixed.
 👍
 less work for me i guess ;P
 *goes back to futzing with the Lubuntu infra*
[20:31] <RikMills> Eickmeyer[m]: fyi, if you need something in universe rebuilding, you can also ping me
[20:32] <Eickmeyer[m]> RikMills: Ok, good to know!
[20:32] <RikMills> but if you apply for MOTU, then no need ;)
[20:32] <Eickmeyer[m]> I need to get on that.
[20:32] <RikMills> it is not as scary as it seems
[20:33] <RikMills> Q. Are you reasonably competent at packaging?
[20:33] <RikMills> A. yes
[20:34] <RikMills> Q.  HEHE
[20:36] <RikMills> @teward001 that is basically it right, apart from being able to answer a few procedural things
[20:37] <RikMills> Eickmeyer[m]: I would think so :)
 the question is does Eickmeyer pass my tests >:D
 @RikMills it's certainly not the same standards as coredev would be
 which is a lot more restrictive because you can do WAY more evil with that but :P
[20:48] <Eickmeyer[m]> I don't contribute to main, so no reason to have coredev.
 i don't see why Eickmeyer isn't applying for MOTU already
 other than $LAZY being a factor :P
[20:48] <Eickmeyer[m]> s/$LAZY/$BUSY
 they're synonyms of each other 😔
[20:49] <Eickmeyer[m]> :
[20:49] <Eickmeyer[m]> :P
 'course the next DMB meeting is like the 11th or whatever it is thanks to the holidya soooooooooooo
 get your damn application in xD
[20:50] <Eickmeyer[m]> Yeah.
[20:50] <Eickmeyer[m]> I might be able to work on that over the next couple of days.
 well if you don't you'll never get it done xD
[21:07] <RikMills> DOIT
[21:36] <Eickmeyer[m]> Now my work has tasked me with it.
[21:36] <Eickmeyer[m]> I guess I'm doing it, boys!  HAHA
[22:01] <OvenWerks> Eickmeyer[m]: ok
[22:01] <OvenWerks> Eickmeyer[m]:  I am thinking to release studio-controls 2.1 on monday.
[22:02] <Eickmeyer[m]> OvenWerks: Cool, sounds great!


[03:19] <holmanb> minimal: I'd lean towards (a) until we have a known reason to diverge, +1 to the idea
[03:42] <holmanb> I've contributed to the Gentoo packaging in the past, I can help if switching to sysvinit/openrc breaks anything downstream
[03:43] <holmanb> They are probably due for an update anyway, I haven't checked lately what version they are at
[09:13] <caribou> holmanb: Hi, I finally ironed out the responses intricacies for the python 3.6 unittest on https://github.com/canonical/cloud-init/pull/2033.
[09:13] <caribou> Hope that everything is fine with you
[09:13] -ubottu:#cloud-init- Pull 2033 in canonical/cloud-init "Adapt DataSourceScaleway to IPv6" [Open]
[09:14] <caribou> let me know if you have an idea of when this can be merged so I can do some planning on my side
[14:01] <holmanb> caribou: Thanks for ironing that out! I'll try to get in a review today, and if no objections I'll merge if you're okay with that.
[14:04] <caribou> I'm fine with that or anytime this week, as long as there is no more mods to the DS to be expected
[14:05] <caribou> very nice of you, I appreciate
[20:33] <holmanb> thanks for the review meena - is "warn" prefered on netbsd as well?
[20:34] <meeena> holmanb: do we have NetBSD rc scripts yet??
[20:35] <holmanb> in the PR, yeah
[20:36] <meeena> https://man.netbsd.org/rc.subr.8 yes
[20:37] <meeena> but, i have no idea how NetBSD sets kernel / boot options
[20:47] <meeena> somebody with a @ hat in #netbsd, and a cloak that says NetBSD developer says that they don't think NetBSD has such a mechanism to begin with