[12:12] <coz_> i like it as so far very nice simple colorgul look easy to maneuver in
[12:12] <coz_> colorful
[12:14] <coz_> vdepizzol, I like it all I wold just clen up the ubuntu logo symbol the edges seem choppy
[12:14] <coz_> just my opinion
[12:14] <vdepizzol> coz_: thank's :)
[12:14] <coz_> vdepizzol, what about the font? you didn't want to use the official ubuntu ttf?
[12:16] <vdepizzol> coz_: I didn't try. I'll :)
[12:16] <coz_> vdepizzol, well I like the design very much :)
[12:36] <darkmatter> vdepizzol, lovely work mein freund.. it looks very nice thus far
[12:38] <coz_> darkmatter, agreed
[12:38] <coz_> darkmatter, but you and I are perverts so what do we know:0
[12:39] <darkmatter> :P
[12:39] <coz_> darkmatter, so tell be about saskatcuan not spelled ritht of course
[12:40] <darkmatter> coz_ you'll like the top secret work being done on Glory... wasn't by intent, but the widget layout is picking upa few traits that I know will bring back memories
[12:40] <coz_> oooo darkmatter i think i understand:)
[12:41] <coz_> darkmatter, even if it is not yellow I will like  it :)
[12:41] <darkmatter> well... saskatchewan is cold... has cows, wheat, potash, oil, uranium, and hotties
[12:41] <darkmatter> lol
[12:41] <darkmatter> coiz_ yup... like that
[12:41] <darkmatter> I just noticed the "neo <that>" traits last night
[12:42] <coz_> darkmatter, I like cold, I don't eat cows I like wheat don't use postash I don'tthink . oil is ok uranium you can keep and hotties cool
[12:42] <darkmatter> its not the same thing obviously... but it has a really interesting feel
[12:42] <darkmatter> lol
[12:43] <coz_> darkmatter, well I know you will do it well, so whatever  you have is fine with me... I am interested in your concepts and how you carry them out so i will like it icomes from one like mind
[12:44] <coz_> darkmatter, what about work up there
[12:44] <coz_> jobs
[12:45] <darkmatter> work?? theres enough... more opportunities arising et... would be nice if I wasnt on disability... could get a half decent one
[12:46] <darkmatter> not saying its exeedingly diverse employ (as in choice of career)... but its there
[12:47] <coz_> darkmatter, thinking of making a run from all I have here don't be surprised if you see me up there :)
[12:47] <darkmatter> lol
[12:47] <vdepizzol> darkmatter: :)
[12:48] <darkmatter> coz, was thinking of the thing you mentioned about my theme "how ya though it might have had yellow" thing before ya saw it
[12:48] <darkmatter> dude.. that was inspiration
[12:49] <darkmatter> the "morningglory" scheme is actually shifted to a base of very pale honey...
[12:49] <darkmatter> kinda golden but not a yellow
[12:49] <darkmatter> almost a creamy color
[12:49] <coz_> darkmatter, well doesn't need to be yellow ..actually it wold be nice to see tha tin different colors come to think of it, although the yellow looked fine for be  more pastel shades would look nice also
[12:49] <coz_> darkmatter, ok ifinished typing that before I read what you just typed :)
[12:49] <darkmatter> glry will be the gray
[12:50] <darkmatter> *glory
[12:50] <coz_> oooo creamy colors are nice
[12:50] <coz_> i am freezing here 7F
[12:50] <darkmatter> I'm freezing too... its -22c
[12:50] <darkmatter> :O
[12:50] <coz_> ok now I have to do my math or google the difference beween f and c
[12:51] <coz_> brb nephew dropped in
[12:51] <vdepizzol> coz_: Brazilian summer here: 23C
[12:51] <darkmatter> just google "f toc:
[12:51] <darkmatter> bah
[12:51] <darkmatter> missed em
[03:27] <MayaAntz> hello
[05:21] <La_PaRCa> hey guys. Quick question: What is the font used for the ubuntu strapline?
[06:15] <La_PaRCa> Hey guys, does anyone know the name of the font on the ubuntu logos?
[06:18] <troy_s> La_PaRCa: yes
[06:18] <troy_s> ubuntu-title ttf
[06:18] <troy_s> apt-cache search ubuntu title
[06:19] <troy_s> sudo apt-get install ttf-ubuntu-title
[06:19] <La_PaRCa> troy_s, awesome!
[06:19] <La_PaRCa> thanks
[06:19] <troy_s> erm
[06:19] <troy_s> if you mean the font underneath
[06:19] <troy_s> i believe the other one, with the tails, is modata
[06:19] <troy_s> and if all else vails
[06:19] <troy_s> fails
[06:19] <troy_s> http://www.myfonts.com/WhatTheFont/
[06:19] <troy_s> good luck :)
[06:20] <La_PaRCa> ok, thanks
[06:34] <La_PaRCa> doesnt seem like I can find the font for the text underneath
[06:54] <BHSPitLappy> ugh
[06:54] <BHSPitLappy> the Show Desktop button is so badly implemented
[06:54] <BHSPitLappy> it's like the whole button itself is bitmapped in
[06:55] <BHSPitLappy> when you have a transparent panel, it's the only button that doesn't go transparent with it
[11:17] <darkmatter> ping
[02:26] <kwwii> anyone know where the original files are for the usplash?
[02:27] <kwwii> I wanted to try and improve on the progress bar backgrounds
[03:11] <kwwii> Seveas: I am working on improving the usplash, could you explain a few things to me?
[03:16] <Seveas> kwwii, sure
[03:16] <Seveas> kwwii, btw, I'm making patches to mak using everything easier. I assume you only want to change the artwork and not the code?
[03:16] <kwwii> Seveas: what do the *-16.png files do?
[03:16] <Seveas> 16-color files
[03:16] <kwwii> Seveas: yepp, only small artwork changes this time
[03:16] <Seveas> used on amd64
[03:17] <kwwii> Seveas: but they have a 256 colormap...funny
[03:17] <Seveas> that indeed is funny
[03:17] <Seveas> someone should be slapped
[03:17] <kwwii> ;-)
[03:19] <kwwii> I hope to have something done by tomorrow...I'll ping you so you can have a look at what I have made
[03:20] <kwwii> Seveas: one of the problems is that people seem to think that the progress bar is smaller than on the desktop. sabdfl would like to have the progress bar look exactly like the one on the desktop
[03:20] <kwwii> although the pixel size is the exact same :-)
[04:14] <alefteris> hi everyone! could someone point me to the upstream for the edgy/feisty gdm themes?
[04:17] <kwwii> alefteris: I doubt that the gdm from ubuntu went upstream since it is distro specific
[04:19] <kwwii> but if you want the sources for it, run "apt-get source ubuntu-artwork"
[04:21] <alefteris> kwwii, ok that is what i did.. so the sources for the theme are kept ionly n bazzar?
[04:27] <kwwii> alefteris: guess so, not sure where else they should be kept ;-)
[04:28] <kwwii> bbl
[04:28] <alefteris> can someone take look at this https://launchpad.net/ubuntu/+source/feisty-gdm-themes/+bug/70829
[04:28] <Ubugtu> Malone bug 70829 in edgy-gdm-themes "gdm theme should use dejavu fonts" [Low,Needs info] 
[04:52] <TheSheep> troy_s: you here?
[04:52] <troy_s> there you are!
[04:52] <troy_s> thesheep where the hell you been?
[04:52] <troy_s> tsk tsk
[04:52] <troy_s> great to see you here.
[04:53] <troy_s> TheSheep: ?
[04:53] <TheSheep> troy_s: I don't think I will be able to help the project on regular basis :(
[04:54] <TheSheep> troy_s: several other of my projects started to be alive, and I was a little busy lately
[04:54] <TheSheep> troy_s: I'm sorry
[05:02] <alefteris> troy_s, could you please take a look at this bug https://launchpad.net/ubuntu/+source/feisty-gdm-themes/+bug/70829. What I need to do next to push this forward?
[05:02] <Ubugtu> Malone bug 70829 in edgy-gdm-themes "gdm theme should use font aliases" [Low,Needs info] 
[05:03] <alefteris> you can see the differerces here http://librarian.launchpad.net/5809389/screenshot2.png and http://librarian.launchpad.net/6298458/Screenshot-FeistyVM.png
[05:35] <troy_s> alefteris: Ideally
[05:35] <troy_s> alefteris: "Branch" a bzr repository of the issue in question
[05:36] <troy_s> as in
[05:36] <troy_s> 'sudo apt-get install bzr' (if you don't already have it)
[05:37] <troy_s> go to www.launchpad.net/products and find the 'product' in question
[05:37] <troy_s> in this case, feisty-gdm-themes
[05:37] <troy_s> click on 'code' in the left panel to get the list of branches that are available from bzr
[05:38] <troy_s> click on the branch in question
[05:38] <troy_s> and copy the link for use with bzr
[05:38] <troy_s> in this case, it is:
[05:38] <troy_s> bzr branch http://bazaar.launchpad.net/~ubuntu-art-pkg/feisty-gdm-themes/ubuntu
[05:38] <troy_s> oops
[05:38] <troy_s> bzr branch http://bazaar.launchpad.net/~ubuntu-art-pkg/feisty-gdm-themes/ubuntu my-local-feisty-gdm-themes
[05:38] <troy_s> which will create a subdirectory called 'my-local-feisty-gdm-themes'
[05:38] <troy_s> go into that directory, and make the changes.
[05:39] <troy_s> test it (either using symlinks or trying the make which may not work if you have added files)
[05:39] <troy_s> once you are certain you have fixed the issue
[05:39] <troy_s> push your 'new' branch as per wiki.ubuntu.com/Bzr and register it against the bug report by selecting 'add a branch' and notify the bug listing.
[05:39] <troy_s> phew.
[05:39] <troy_s> basically two steps:
[05:40] <troy_s>  1) branch the bzr and make your fixes
[05:40] <troy_s>  2) push and update bug listing with a comment and a branch
[05:40] <troy_s> that makes it easiest for daniel to merge your changes.
[05:40] <troy_s> alefteris: Ok?
[05:40] <troy_s> if you need further help or tutoring, just ping me.
[05:41] <alefteris> troy_s, ok this seems a lot easier than the way I made a patch from the sources :)
[05:41] <troy_s> it is very easy
[05:41] <troy_s> the problem is, if you haven't setup bzr yet, you will need to take an additional step to set it up at launchpad
[05:41] <troy_s> once you have done that, it is _very_ easy to push changes
[05:41] <alefteris> when i finish, who should i contact? daniel?
[05:42] <troy_s> note -- they won't take effect until one of the artwork packagers takes notice...
[05:42] <troy_s> no.
[05:42] <troy_s> although he is an artwork packager
[05:42] <troy_s> the best bet
[05:42] <troy_s> is to simply subscribe or make sure that an artwork packager is subscribed.
[05:42] <alefteris> i should assign the bug to ubuntu-artwork-packagers?
[05:43] <alefteris> ok thanks
[05:43] <troy_s> https://launchpad.net/~ubuntu-art-pkg
[05:43] <troy_s> you could subscribe the team yes
[05:43] <troy_s> that SHOULD notify them
[05:43] <troy_s> but again, the formalized process is missing key players to take on the duties.
[05:43] <troy_s> those folks have team access to the bzr so they can push formal changes to the main 'trunk' branch
[05:44] <troy_s> kwwii has access too
[05:44] <troy_s> and he is probably a good pointman now as canonical is paying his rent
[05:44] <kwwii> :-)
[05:44] <troy_s> there he is :)
[05:44] <alefteris> hehe#
[05:44] <troy_s> the bottom line though
[05:44] <kwwii> just got back from my walk
[05:44] <troy_s> is that you want to make it as PAINLESS for the packagers as possible
[05:44] <kwwii> alefteris: are you talking about the font change in gdm?
[05:44] <troy_s> which means using bzr
[05:44] <alefteris> kwwii, yes
[05:44] <lizardking> hi
[05:44] <troy_s> then they can simply do a bzr merge
[05:44] <troy_s> without farting around with pain
[05:44] <lizardking> what do you are talking about?
[05:45] <troy_s> bzr merge, bzr push
[05:45] <troy_s> lizardking: fixing reported bugs
[05:45] <kwwii> alefteris: I agree completely with you, so once it is pushed we'll use it
[05:45] <alefteris> ok I do it right away
[05:45] <troy_s> alefteris:  oh yes... i forgot to mention
[05:46] <kwwii> if we do it before thursdasy it will be in the next herd
[05:46] <lizardking> troy_s: is there new feisty artwork or is the same than edgy?
[05:46] <troy_s> make sure that the 'powers that be' agree before you bother to work on something.  they will be a little more responsive now that we have kwwii handling ubuntu details.
[05:46] <troy_s> lizardking: kwwii is handling that.
[05:46] <troy_s> lizardking: if you are wise, you would not try to get involved as it directly involves the master of aesthetic nightmares himself -- sabdfl.
[05:47] <troy_s> lizardking: but that is just my 2c.
[05:47] <troy_s> lizardking: pretty sure that who_, jmak, fschoep, and others anyone else who survived his edgy endgame would agree.
[05:49] <lizardking> troy_s: Last week I wrote at sabdfl asking the question of trademark
[05:50] <troy_s> trademark regarding?
[05:50] <kwwii> from what I understand the decision making for the default theme will stay in canonical hands at least for a little while (as he is paying for this). This doesn't mean that people cannot work on it, it just means that the direction it takes will be directly controlled by someone
[05:51] <lizardking> troy_s: yes, he does not answer me yet
[05:51] <kwwii> in the meantime, the plan is to make the automated theme building stuff as good/simple as possible
[05:51] <troy_s> kwwii:  Practically, it means that working on it is nightmarish without design concepts and such.  Unless you value the 'throw sh*t at the wall and hope it sticks' approach.
[05:51] <kwwii> so that everyone can create a theme however they like
[05:51] <troy_s> lizardking: he probably wont... you have to appreciate that sabby is _damn_ busy
[05:51] <kwwii> troy_s: yeah, that is part of what I am trying to work out
[05:51] <troy_s> and he gets about sixteen thousand emails a day.
[05:52] <kwwii> lizardking: perhaps I could answer your question
[05:52] <lizardking> troy_s:  yes I suppos that
[05:52] <troy_s> kwwii: Problem is you can't work it out if the guy who is calling the aesthetic judgements has zero sense on the matter nor ideas on implementation strategies.
[05:52] <lizardking> kwwii: I'm hearing you
[05:53] <troy_s> alefteris: https://wiki.ubuntu.com/BzrContributorHowto
[05:53] <kwwii> troy_s: hopefully once I "prove" myself things will change in that regards
[05:53] <troy_s> there is a summary of what i just described, but with different teams involved.
[05:53] <troy_s> kwwii:  I don't know.  I suspect he wants a patsy, which might earn his faith, but possibly doesn't help the larger issues.
[05:54] <kwwii> well, that is my fear as well ;-)
[05:54] <troy_s> kwwii:  The main problem is that
[05:54] <troy_s> kwwii: "art" is actually a many pronged element in an operating system -- there is implementation artwork (like icons/walls/etc) but then there is the artistry of design.
[05:54] <troy_s> which is an entire other can of worms.
[05:55] <troy_s> kwwii:  The true unfortunate portion of this entire puzzle is that there are some _very_ knowledgeable folks already in our midst who would at least be able to engage the concepts on a semantic level and attempt to address them in terms of future design patterns.
[05:55] <troy_s> (read people like Darkmatter, TheSheep, etc.)
[05:56] <lizardking> kwwii: : please Can you tell me what is the answer to my question?
[05:56] <troy_s> knowledgable _and_ researched.
[05:56] <troy_s> lizardking: Your question needs clarification.  What form of licensing for what?
[05:56] <kwwii> lizardking: I didn't quite understand the question
[05:57] <lizardking> kwwii: :ok, I mean the truoble of oransoda trademark. Kwwii tells me that he has the answer
[05:57] <kwwii> troy_s: I think that until now the biggest problems have been that of simple artwork and continuity, not the bigger, more long term design issues
[05:58] <kwwii> lizardking: well, you cannot use anything that is trademarked by anyone
[05:58] <kwwii> lizardking: that is a major no-no, unless you have permission from those who hold the trademark
[05:58] <troy_s> kwwii:  I think most people who try to get involved with ubuntu artwork seek to break off from the continuity that has been established.
[05:58] <troy_s> kwwii:  Arguably, making _any_ change is a departure from continuity.
[05:59] <kwwii> troy_s: yepp, we tend to get 8 differing opinions from 5 people
[05:59] <troy_s> kwwii:  Currently, the continuity is nothing more than an accident that happens to meet sabdfl's liking.
[05:59] <lizardking> kwwii: : ok
[05:59] <troy_s> kwwii:  lol.  To say the least.
[05:59] <kwwii> that is also true, probably because he doesn't have the time to lead this correctly
[05:59] <troy_s> kwwii:  But the bottom line is that if the end result of all of this is to simply make the Ubuntu current look operate more effectively, I don't know how much support there is going to be in the end.
[05:59] <cryingfreeman> Hi everyone, can you tell me if there are any Ubuntu slideshows, logos etc that is available for download? I need some for a presentation that I'm about to do..
[05:59] <kwwii> but I think that by hiring me there is a long term plan to fix things
[05:59] <kwwii> troy_s: right
[06:00] <kwwii> troy_s: basically I get to start at the very bottom and build everything up again
[06:00] <troy_s> kwwii:  And with a distribution such as Ubuntu, we can possibly really 'shape' interface considerations in much the same way that Novell was trying to do with little bits like SLAB etc.
[06:00] <kwwii> cryingfreeman: check the wiki
[06:00] <lizardking> cryingfreeman: : Do you view the Impress OpenOffice ubuntu template or examples?
[06:00] <troy_s> kwwii:  Problem with 'building up' is that we are still stuck with sabdfl's fundamental direction, which is haphazard to say the least.
[06:01] <troy_s> cryingfreeman do a search for DIY marketing on the wiki
[06:01] <kwwii> troy_s: as I have some experience with Novell I must say that all that work is done in a closed room by 3 people
[06:01] <troy_s> kwwii:  Which reminds me
[06:01] <lizardking> kwwii: : It's not true open development the Novell's one, in my opinion
[06:01] <troy_s> kwwii:  Can you (as a rather higher priority because I have responded to at least 20 irc and 30 email requests) attempt to get the source svg files into the bzr repos for who's ubuntu logo?
[06:02] <kwwii> troy_s: oh, I can see lots of places where things can go wrong, and I know that it will be very tricky to work this out right
[06:02] <cryingfreeman> lizardking: Didn't know there were any. :)
[06:02] <kwwii> as even sabdfl doesn't completely understand the subject
[06:02] <troy_s> kwwii:  That's fine too... my issue isn't with the process that Novell implements -- it is the fact that SOMEWHERE in the line, they are ATTEMPTING to innovate.
[06:02] <cryingfreeman> Troy_s: Thanks a bundle. :) keep up the good work.
[06:02] <kwwii> troy_s: is that the one that is used in edgy? I found them on the wiki
[06:02] <lizardking> cryingfreeman: Yes they are there! and are quite cool. Btw I advice you to make slides with LateX Beamer ;)
[06:03] <kwwii> troy_s: and then redrew them myself
[06:03] <kwwii> simplifying things, etc
[06:03] <troy_s> kwwii:  Obviously the 'Novell paradigm' leaves at least as much to desire as our own regarding process ;)
[06:03] <troy_s> kwwii:  The source files SHOULD be in the source repository on bzr
[06:03] <troy_s> as it is the 'sources'
[06:03] <troy_s> with me"/
[06:03] <troy_s> ?
[06:03] <kwwii> ahhh, yeah, true
[06:03] <troy_s> (yet another baby step to 'art and design' getting its shit together.  ;) )
[06:03] <kwwii> hehe, yeah
[06:03] <troy_s> we shouldn't need to crawl the wiki to get instant sources
[06:04] <troy_s> hell -- that is what bzr is for :)
[06:04] <kwwii> yepp, very true
[06:04] <lizardking> folks I have to go studying...see U soon ok?
[06:04] <kwwii> lizardking: see you soon
[06:04] <kwwii> troy_s: yeah, it took we quite a while to find the stuff I need
[06:04] <troy_s> further, keeping up to date is far easier... (and dare I say with SVGs diff might provide detailed changes in the actual filestructure which is rather interesting)
[06:04] <kwwii> and I still haven't found everything
[06:04] <troy_s> kwwii:  So when you push your package, put the sources in there and simply exclude them from the build package
[06:04] <troy_s> follow me?
[06:04] <lizardking> Information Retrieval wants me :(.. havea nice day! bye
[06:05] <kwwii> troy_s: yepp, I will do that
[06:05] <troy_s> It also allows us to utilize powerful applications like imagemagick or other cmd line tools to 'break' images apart from their sources -- saving
[06:05] <kwwii> Information Retrieval sounds like a part of the CIA
[06:05] <troy_s> painful graphical resolution changes etc.
[06:05] <troy_s> LOL
[06:05] <troy_s> lizardking: bye friend.
[06:05] <kwwii> ok, my wife and kid are waiting on me to go to dinner
[06:05] <kwwii> bbl
[06:05] <troy_s> see ya kwwii
[06:45] <alefteris> troy_s, is there any way to remove my branch? netowork connection faild and the push was not finished.. :(
[06:45] <troy_s> alefteris: just re-push
[06:46] <troy_s> alefteris: To push
[06:46] <troy_s> you will need to follow the instructions in wiki.ubuntu.com/Bzr
[06:46] <troy_s> it will step you through publishing your ssh key
[06:46] <troy_s> (not difficult)
[06:46] <alefteris> its gives me an error..
[06:46] <alefteris> bzr: ERROR: File exists: u'/~alefteris/feisty-gdm-themes/ubuntu.bug70829': mkdir failed: unable to mkdir
[06:47] <troy_s> eek
[06:47] <troy_s> yes...
[06:47] <troy_s> you aren't choosing a good branch to push to
[06:47] <troy_s> A) Have you published your SSH key?
[06:47] <alefteris> yes
[06:47] <troy_s> B) If you have, you should include the product and push to your local spot on the Bazaar server.
[06:47] <troy_s> for example:
[06:49] <troy_s> bzr push sftp://alefteris@bazaar.launchpad.net/~alefteris/feisty-gdm-themes/fontfix
[06:50] <troy_s> or something like that
[06:50] <troy_s> note
[06:50] <troy_s> alefteris: the 'alefteris' is your Launchpad identity string.
[06:50] <troy_s> i just used alefteris as an example
[06:50] <troy_s> alefteris: Ok?
[06:51] <alefteris> ok i show the .bug00 naming in one of the documents you told me to look, thats why i used it
[06:51] <troy_s> sure...
[06:51] <troy_s> that's fine too
[06:51] <troy_s> but note the syntax
[06:51] <troy_s> what is your lp identity?
[06:51] <alefteris> alefteris
[06:52] <troy_s> ok so
[06:52] <troy_s> bzr push sftp://alefteris@bazaar.launchpad.net/~alefteris/feisty-gdm-themes/fix.bug70829
[06:52] <troy_s> better?
[06:52] <troy_s> ;)
[06:52] <troy_s> note that you could push to ~alefteris/whateveryouwant
[06:53] <troy_s> but if you include the feisty-gdm-themes in there, i think it will automatically be crosslinked from the feisty 'other branches' page.
[06:53] <troy_s> follow me?
[06:53] <alefteris> yes
[06:54] <alefteris> ok but what happens with the .bug branch that failed? it apears in https://code.launchpad.net/feisty-gdm-themes/+branches. Can i remove it?
[06:56] <troy_s> erm let me look
[06:57] <troy_s> alefteris: on a side note, what did you generate your edgy vm vmplayer vmx file with?
[06:57] <troy_s> https://code.launchpad.net/~alefteris/+branch/feisty-gdm-themes/ubuntu.bug70829
[06:57] <alefteris> from here: http://www.easyvmx.com/
[06:57] <troy_s> try heading there
[06:57] <troy_s> and
[06:57] <troy_s> marking the branch as abandoned
[06:57] <troy_s> see if that works.
[06:57] <troy_s> let me see if there is another option
[06:58] <troy_s> (delete functionality is missing from bzr as of now -- it will be added soon hopefully -- until then abandoned is all you can do)
[06:58] <troy_s> try marking it as abandoned and it SHOULD be removed from branch listings.
[07:02] <alefteris> troy_s, what's this warning in the brarch webpage about? Launchpad could not mirror this branch at 2007-02-06 20:00:09 EET.  The error was: Not a branch: /srv/sm-ng/push-branches/00/00/0b/00/.bzr/branch/
[07:27] <troy_s> yeah it means you didn't finish the push
[07:27] <troy_s> as in it doesn't exist
[07:27] <troy_s> so simply push something empty to it for a success
[07:27] <troy_s> if you can
[08:12] <troy_s> alefteris: did you get it to work ok?
[08:14] <alefteris> troy_s, yeah, the warning message is gone now :)
[08:15] <alefteris> very easy way to fix bugs :)
[08:17] <troy_s> woo!
[08:17] <troy_s> bzr is great, but still has some 'features' :)
[08:17] <troy_s> the folks in #bzr are MORE than helpful.
[08:19] <alefteris> but still im not sure how can someone can test the changes that he makes in his bzr branch
[08:19] <alefteris> you cant build a package this way..
[08:19] <alefteris> i think..
[08:20] <troy_s> alefteris: The build functions
[08:20] <troy_s> are written by Daniel
[08:21] <troy_s> kwwii and dholbach have been reworking the artwork build process to make it better
[08:21] <troy_s> that said, for now, it will build if you don't add any files -- changing existing files should still build properly.
[08:21] <troy_s> standard build procedures are cd DIRECTORY
[08:21] <troy_s> ./configure
[08:21] <troy_s> ./make
[08:22] <troy_s> erm
[08:22] <troy_s> for debian it is checkinstall or whatever the hell command.
[08:22] <troy_s> anyways, that will build a package and install it via dpkg
[08:22] <troy_s> then you can test it.
[08:22] <troy_s> if you know how to test gdms without packages, just test the code and you can skip 'building' the damn thing
[08:24] <alefteris> troy_s, it would help on this was added to the wiki page..
[08:24] <alefteris> i mean a section about testing before pushing the changes
[08:25] <troy_s> alefteris: I would add something, but it is still up in the air.
[08:25] <troy_s> Hell I had to fight like a bugger to try and get the artwork team to start using bzr...
[08:26] <troy_s> at least now, it is progressing.
[08:26] <troy_s> alefteris: the more you use it, the more you can help others.
[08:26] <troy_s> alefteris: Build instructions are pretty simple... let me see if I can find an archived email.
[08:28] <troy_s> debuild -us -uc && sudo debi
[08:28] <troy_s> alefteris: That is for CURRENT build system mechanics (automake hell)
[08:28] <troy_s> the new system will use python setup I believe
[08:30] <alefteris> oh its the same way that i used to build from the package sources
[08:30] <troy_s> alefteris: But yes... you should test them before you push them.
[08:30] <troy_s> yes.
[08:30] <troy_s> the difference with that command
[08:30] <troy_s> is that you get a package that gets installed so you can remove it.
[08:30] <troy_s> as opposed to dealing with the nightmare of tracing files