[01:48] <gnomefreak> asac: you still around?
[01:52] <gnomefreak> asac: well when you det here be it tomorrow i should be here in morning the rules file to iceape doesnt list config options like firefoxs anymore. it seems mike changed alot of things and it looks like they are calling other parts to run instead of simple config options. but i will get with you in morning and see what we can figure out.
[02:10] <gnomefreak> ok read email found things i dont like (not what anyone from team did) and i think it needs to stop :( he has been warned many times before (i know nothing we can do about it but bitch) so im bitching!
[02:16] <AlexLatchford> heh heh
[09:36] <asac> hi
[09:37] <DarkMageZ> sup?
[09:38] <asac> sup?
[09:39] <DarkMageZ> it's like what's up
[09:39] <DarkMageZ> nfi where it came from tho :s
[09:41] <asac> ah ... all fine .... have to get some coffee though
[09:53] <DarkMageZ> yeah, everytime you mention coffee... i all the sudden need a coffee
[09:53] <DarkMageZ> normally i can manage the addiction :(
[09:55] <asac> i have given up on addictions :)
[09:55] <asac> one has to accept those weaknesses
[09:56] <asac>  :) better be strong elsewhere :)
[09:59] <asac> damn ... lp is really down :(
[10:22] <DarkMageZ> asac, launchpad being down the night before launch
[10:23] <asac> :)
[10:27] <DarkMageZ> hey wait. you dislike opera cause it's closed source right? then why use launchpad?
[10:27] <DarkMageZ> :P
[10:42] <asac> same as for google :)
[10:43] <asac> its a web application and luckily doesn't run on my system :)
[10:49] <DarkMageZ> interesting arguement
[11:01] <asac> actually i used opera a bunch of times ... and i hated their UI approach ... so its not the "not-free" which makes me dislike it
[11:02] <asac> BTW, isn't opera based on Qt?
[11:11] <asac> yes it is
[11:11] <asac> but well :) ...  at least they support linux ;)
[11:24] <DarkMageZ> could you imagine if internet explorer was ported to linux
[11:24] <DarkMageZ> that would be interesting
[11:25] <asac> yes i could :) ... it probably would use Xt :)
[11:27] <DarkMageZ> Xt?
[11:30] <asac> http://www.visi.com/~grante/Xtut/
[11:33] <DarkMageZ> that would be interesting
[12:34] <gnomefreak> asac: when you get time http://gnomefreak.pastebin.ca/444352   in that rules file can i just add the config options to line 45 or 65. and looking at the depends in control file some depend on iceape-browser iceape-mail others ${shlibs:Depends} and i find that good but i need to find what defines ${shlibs:Depends}
[12:35] <asac> ?
[12:36] <asac> let me reread :)
[12:37] <asac> gnomefreak: which config options do you want to add?
[12:37] <gnomefreak> to be honest it doesnt look like he changed anything for nss and nspr
[12:37] <asac> does he mention in changelog?
[12:37] <asac> ah you want system nss /nspr
[12:37] <gnomefreak> looking up logs
[12:37] <asac> add those options to debian/mozconfig
[12:38] <gnomefreak> oh
[12:38] <asac> see line 63
[12:38] <asac> he sets MOZCONFIG env
[12:38] <asac> for configure
[12:38] <asac> which apparently honors that
[12:38] <asac> only things that need variable substitution during build stay in debian/rules (e.g. for his way of doing this)
[12:39] <gnomefreak> oh ok so hes just making rules us the config options in mozconfig instead of listing each one?
[12:39] <asac> you need --with-system-nspr
[12:39] <asac> and --with-system-nss
[12:40] <asac> yes ... all that have no variable substituted during build time (see --enable-optimize in debian/rules) go to mozconfig
[12:40] <gnomefreak> yeah i saw thats what confused me he kept listing dirs. and got confused
[12:42] <gnomefreak> ah the depends was the other thing. everything depends on iceape-browser and iceape-browser depends on ${shlibs:Depends} so that should be fine now?
[12:50] <asac> depends are fine as they are
[12:51] <gnomefreak> cool that should be it lets test build than :)
[12:51] <asac> yes
[12:52] <asac> i have ffox 2+3 and tbird 2 already building against nspr/nss ... so if iceape builds fine against those we can go ahead with the "next-generation" packaging
[12:53] <asac> wtf ... firefox and gecko status meeting have apparently been joined again ... not tuesdays but wednesdays
[12:53] <gnomefreak> can i lower the verison of libhunspell without any issues?
[12:54] <gnomefreak> libhunspell-dev even
[12:54] <asac> why?
[12:54] <gnomefreak> libhunspell-dev (>= 1.1.5-2)
[12:54] <gnomefreak> libhunspell-dev: Installed: 1.1.4-7
[12:54] <asac> ah ... it might build ... but we definitly want 1.1.5
[12:54] <gnomefreak> thats the latest in feisty
[12:55] <asac> yeah ... try to drop it ... but remember that we add it again once we have it
[12:55] <asac> you can just remove the version for now
[12:55] <gnomefreak> i would think we would have it for gutsy
[12:55] <asac> OR you could build libhunspell from debian unstable
[12:55] <asac> and add to our repo
[12:56] <gnomefreak> how bad is it?
[12:56] <gnomefreak> lol
[12:56] <asac> as our repo has lots of new stuff that will land on the first breath of gutsy
[12:56] <asac> not bad
[12:56] <asac> apt-get source + building
[12:56] <asac> should do the trick
[12:56] <asac> no version change needed in changelog as its already released in sid
[12:57] <gnomefreak> so no changes? just build and upload?
[12:57] <asac> yep
[12:58] <asac> you can try at least :) ... should build rather quickly
[12:58] <gnomefreak> ok lets find out :)
[12:59] <gnomefreak> what is the package name hunspell or libhunspell
[12:59] <gnomefreak> hunspell should build -dev
[01:00] <gnomefreak> sob
[01:00] <gnomefreak> Get:1 ftp://ftp.uk.debian.org sid/main hunspell 1.1.4-5
[01:01] <gnomefreak> updating my chrrot
[01:01] <gnomefreak> chroot
[01:09] <gnomefreak> ok it needed an update
[01:19] <hjmf> good afternoon
[01:20] <gnomefreak> good morning ;)
[01:21] <hjmf> :)
[01:22] <gnomefreak> seems huspell is the OO.o team
[01:39] <gnomefreak> btw asac and hjmf that wallace person has been told a bunch of times in past to read the docs before triaging mozilla bugs. im not sure what kind of karma you get for marking as upstream but it would be nice if there was a bug upstream beofore marking as such
[01:40] <asac> gnomefreak: he?
[01:41] <gnomefreak> cant think of full LP name atm let me see if i still have bugs with him
[01:41] <asac> me ... i remember that i marked upstream to test launchpad things before we used tags
[01:41] <gnomefreak> asac: he does it on bugs that havent even been triaged
[01:41] <asac> so some have an upstream without a bug ... you can find them in advanced search
[01:41] <asac> gnomefreak: really?
[01:41] <gnomefreak> yes
[01:42] <asac> show me one
[01:42] <gnomefreak> looking
[01:42] <gnomefreak> it was one i looked at this am
[01:43] <gnomefreak> lp is down
[01:44] <gnomefreak> sortof
[01:44] <gnomefreak> looking on server
[01:47] <asac> slow
[01:47] <asac> i just used it a few minutes ago
[01:49] <gnomefreak> cant find it now. if you havent checked your email yet you will see a post from me on a few. ill still look
[01:50] <gnomefreak> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/107096
[01:50] <ubotu> Malone bug 107096 in firefox "firefox freeze when close tab" [Medium,Needs info] 
[01:50] <gnomefreak> there has been activity since he did it
[01:51] <gnomefreak> said 11 hours ago thats not right as it was around 5-6 am
[01:51] <gnomefreak> its now 7:51
[01:51] <gnomefreak> https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/107096/+activity is the activity log
[01:51] <ubotu> Malone bug 107096 in firefox "firefox freeze when close tab" [Medium,Needs info] 
[01:54] <asac> i will go through bugmail this afternoon
[01:54] <asac> will to go lunch soon
[01:54] <asac> after that probably
[01:54] <asac> or maybe a bit later
[01:54] <asac> hope i can do mt-confirm/summary processing as well
[01:54] <gnomefreak> well i got hunspell built and uploaded now building iceape
[01:55] <asac> great
[01:55] <asac> any news on how i can upload packages?
[01:55] <gnomefreak> i go through  unconfirmed bugs 1 time a week or so :)
[01:55] <asac> for amd64?
[01:55] <gnomefreak> i cant build amd63
[01:55] <gnomefreak> 64
[01:55] <asac> yes ... great ... i often forget to go through unconfirmed
[01:56] <asac> gnomefreak: i build them ... you told me i could upload through ftp
[01:56] <gnomefreak> im happy doing them there isnt ever all that much
[01:56] <asac> i can upload them to somehwere else and you can setup a sync
[01:56] <asac> if you can get outgoing connections from ssh account
[01:56] <gnomefreak> asac: how hard is it to set up sync?
[01:56] <asac> dunno :)
[01:56] <asac> guess just cronjob
[01:56] <gnomefreak> no i cant we tried that before :(
[01:56] <asac> with one rsync line
[01:57] <gnomefreak> noone has ever been able to ssh into me
[01:57] <asac> really ? ... you cannot do wget on that box?
[01:57] <gnomefreak> i can wget all i want ;)
[01:57] <asac> thats what i meant "if you can get outgoing connections from ssh account"
[01:57] <gnomefreak> ah ok
[01:58] <asac> look man rsync
[01:58] <hjmf> gnomefreak: yea woallance3!!! today I've fixed some of his *triages* :(
[01:58] <gnomefreak> nalioth and a bunch of others have tried sshing into me but something with these internet over power adapters are stopping it
[01:58] <gnomefreak> hjmf: i saw i did about 3 or 4
[01:58] <gnomefreak> hjmf: you did a few also :)
[01:58] <hjmf> :)
[01:59] <hjmf> I remember him being told to not to do that some weeks ago
[01:59] <asac> can we unmark upstream hints?
[01:59] <hjmf> I just rejected them
[01:59] <gnomefreak> reject them
[01:59] <asac> good
[01:59] <gnomefreak> hjmf: some months ago as well
[01:59] <asac> can we still ad upstream if we find?
[01:59] <gnomefreak> yes
[02:00] <gnomefreak> unless we mark as upstream without a bug i would rather have a bug beofre marking upstream
[02:00] <gnomefreak> we confuse eachother enough ;)
[02:00] <asac> has anyone explained that he is doing wrong? or will he go on?
[02:00] <hjmf> gnomefreak: told him
[02:01] <asac> k
[02:01] <gnomefreak> hell i think we all have
[02:01] <gnomefreak> you can find him in -bugs alot of time. hes nick is on his LP page iirc
[02:01] <gnomefreak> ^^^ from months back
[02:01] <asac> he has high karma?
[02:01] <asac> or just a beginner?
[02:02] <gnomefreak> dont remember i think beginner
[02:02] <asac> then its fine
[02:02] <hjmf> karma=422
[02:02] <asac> fine
[02:02] <gnomefreak> was that because of the drop though?
[02:03] <hjmf> could be, I don't know what karma means
[02:03] <hjmf> or how is it calculated.
[02:03] <gnomefreak> he doesnt do alot of bug work but when he does i notice it
[02:03] <asac> actually marking upstream without bug is a launchpad feature ... so we cannot hold this against it
[02:03] <asac> maybe her really thought this should be dealt upstream :)
[02:04] <hjmf> but he was advised to not doing that
[02:04] <hjmf> short memory maybe :)
[02:04] <gnomefreak> he marks them as batix also
[02:05] <gnomefreak> people see thier bug was marked upstream (with or without a bug) they think mozilla is dealing with it. why give false hope
[02:05] <asac> https://help.launchpad.net/KarmaCalculation
[02:05] <asac> hjmf: ^^^
[02:07] <hjmf>  asac ty
[02:08] <asac> yes thats true
[02:08] <asac> we have to fix bughelper for that
[02:08] <asac> i guess waiting for launchpad would take much longer
[02:09] <gnomefreak> my Lp home page is giving me 503 still
[02:09] <gnomefreak> but bugs work :(
[02:09] <asac> 503 ?
[02:09] <asac> assigned?
[02:09] <gnomefreak> can you please check your homepage
[02:09] <asac> ah http error
[02:09] <asac> :)
[02:09] <gnomefreak> Launchpad is offline at the moment for maintenance. It should be back, better than ever, soon. Thanks for your patience.
[02:09] <asac> works
[02:09] <asac> pretty fast
[02:10] <asac> guess just a restart and you had bad luck
[02:10] <asac> press reload
[02:10] <gnomefreak> i just did
[02:10] <gnomefreak> tried restarting browser
[02:11] <gnomefreak> lets see if trunk gets in
[02:11] <asac> trunk?
[02:11] <gnomefreak> fx 3
[02:11] <gnomefreak> nope
[02:12] <asac> hmm
[02:12] <asac> maybe launchpad is clustered and you get a different server?
[02:12] <hjmf> * gnomefreak would like a way to search bugs that dont have tags so i can spend a few days tagging ;)
[02:12] <hjmf> if you don't mind to leave your pc working for a while
[02:12] <hjmf> you can script it
[02:13] <asac> hjmf: have you looked at bughelper?
[02:13] <asac> better script it in there :)
[02:13] <asac> e.g. improve bughelper code
[02:13] <hjmf> no I haven't
[02:13] <asac> if you need hints let me know
[02:13] <hjmf> I'll look
[02:13] <asac> its python ... pretty easy to read
[02:14] <hjmf> but the script can be something like
[02:14] <asac> https://code.launchpad.net/~bugsquad/
[02:14] <asac> use bughelper.main ... if you code something
[02:14] <hjmf> get_metadata.__dict__['tags']  == ""
[02:14] <hjmf> I will look at it
[02:15] <asac> if you have questions let me know
[02:15] <hjmf> k
[02:15] <asac> there are places where Bug are parsed
[02:15] <gnomefreak> seems beta isnt beta?
[02:15] <asac> beta is public :)
[02:16] <gnomefreak> yeah thats what the issue was. my homepage was beta URL
[02:16] <gnomefreak> so everyone sees the same thing now?
[02:16] <asac> hjmf: https://wiki.ubuntu.com/MozillaTeam/Bugs/Bughelper/ClueFile
[02:16] <asac> that should work as well and without coding
[02:17] <asac> maybe makes sense to start with that
[02:17] <hjmf> hmm have to figure out what and how works bughelper
[02:17] <asac> its simple ... just run bughelper -pfirefox ... it will branch clue files for all packages
[02:17] <asac> out of bzr
[02:17] <asac> there you can add your own clues and check in
[02:17] <asac> bughelper is run centrally
[02:18] <asac> so we have an updated list daily
[02:18] <hjmf>  No WorkingTree exists for file:///home/pituko/.bughelper/packages/.bzr/checkout/
[02:18] <asac> ah
[02:18] <asac> ok
[02:18] <asac> wait
[02:18] <asac> thought it would do automatcically
[02:18] <asac> are you on feisty?
[02:18] <hjmf> yes
[02:19] <asac> http://pastebin.ubuntu-nl.org/16112/
[02:19] <asac> that is .bughelper/config
[02:19] <asac> then i did
[02:20] <asac> bzr branch sftp://asac@bazaar.launchpad.net/%7Ebugsquad/bughelper-data/main/ bughelper-data.main
[02:20] <asac> in directory ubuntu_bzr
[02:20] <asac> adapt path as you with
[02:20] <asac> running bughelper -pfirefox should work then
[02:21] <asac> you can also use bug-search url ... to refine bug list to process
[02:21] <asac> you need to add ssh key to launchpad to checkout and checkin to bugsquad through sftp
[02:21] <hjmf> ok I'm going to try that
[02:22] <gnomefreak> bughelper-data.main is default location?
[02:23] <asac> in launchpad? yes
[02:24] <asac> in bzr command above its how the directory is called locally after cloning/branching
[02:24] <hjmf> Ofcourse I assume that the command is "bzr branch sftp://bazaar.launchpad.net/"
[02:24] <hjmf> w/o asac@
[02:24] <asac> no
[02:24] <asac> your username
[02:24] <asac> instead of asac :)
[02:25] <hjmf> k
[02:25] <asac> you are in bugsquad?
[02:25] <hjmf> yes
[02:25] <asac> good ... then you can use sftp with your SSH key
[02:26] <asac> hjmf: you should see your personal url at
[02:26] <asac> https://code.launchpad.net/~bugsquad/bughelper/bughelper.main
[02:26] <asac> i have  You can upload to this branch at: sftp://asac@bazaar.launchpad.net/~bugsquad/bughelper/bughelper.main
[02:27] <hjmf> yea, now its working
[02:27] <asac> oops
[02:27] <asac> its i posted bughelper code ... not -data ?
[02:27] <asac> i guess you can figure out :)
[02:27] <asac> fine
[02:27] <asac> at them moments we are branching what is currently in bugsquad repo
[02:27] <hjmf> Branched 98 revision(s).
[02:28] <gnomefreak> k
[02:28] <asac> if you have modifications you commit them locally
[02:28] <asac> and eventually push changes up to bugsquad repo .... e.g. if they proved to work well
[02:28] <asac> those clues will be processed daily (e.g. you don't need to run this lenghty process on your own)
[02:29] <asac> there is already a firefox.info file
[02:29] <asac> which shows a duplicate example
[02:29] <asac> and MASTER bug?
[02:29] <gnomefreak> there is?
[02:29] <asac> yes
[02:29] <asac> we already have clues
[02:29] <asac> but just example
[02:29] <gnomefreak> running bughelper -pfirefox with default bughelper
[02:30] <gnomefreak> i havent used bughelper since it was first introduced
[02:30] <gnomefreak> Branched 98 revision(s).
[02:30] <asac> the processs is pretty fine now ... whats needed next is an improved more easily extensible codebase imo
[02:30] <asac> i am working on that (e.g. currently thinking how to improve)
[02:31] <gnomefreak> bughelper -pfirefox should do something right? it gave the revisions and now just sitting there
[02:31] <asac> yeah ... takes ages
[02:31] <asac> just wait
[02:31] <gnomefreak> k
[02:31] <asac> please look in firefox.info
[02:31] <asac> and tell me if there is MASTER clue
[02:31] <asac> otherwise you will wait really long :)
[02:32] <gnomefreak> hmmmmmm
[02:33] <asac> isn't there?
[02:33] <gnomefreak> in ~/.bughelper i dont have a firefox.info
[02:33] <asac> please read above
[02:33] <asac> use my config file
[02:33] <asac> and branch bzr
[02:33] <asac> -> read above 40-100 lines :)
[02:33] <asac> i am going to lunch now
[02:34] <asac> gnomefreak: maybe ~/.bughelper has subdirectories?
[02:34] <gnomefreak> yeah but not in them either
[02:34] <asac> what is in config ?
[02:34] <asac> Packages-Dir
[02:34] <gnomefreak> yes
[02:35] <gnomefreak> in bughelper you have packages and a config
[02:35] <asac> in packages?
[02:36] <gnomefreak> a .bzr dir and a list of packages none of them are firefox
[02:36] <asac> simple clues can be added with bugxml
[02:36] <gnomefreak> should i bzr checkout http://bazaar.launchpad.net/~bugsquad/bughelper/bughelper.main
[02:36] <asac> bugxml -pfirefox "Your Search String" "Your Description"
[02:36] <asac> e.g.
[02:36] <asac> bugxml -pfirefox "MASTER" "This is a master bug"
[02:37] <asac> read above ... you can branch http or sftp
[02:37] <asac> whatever you like more
[02:37] <asac> no
[02:37] <asac> not that
[02:37] <gnomefreak> to branch you need revisions
[02:37] <asac> that url was wrong
[02:37] <asac> search for bughelper-data
[02:40] <hjmf> firefox takes ages, trying with bughelper -pvino shows results :-P
[02:40] <asac> hjmf: is there a master hint already?
[02:40] <hjmf> no
[02:40] <hjmf> :(
[02:40] <asac> otherwise run the bugxml above
[02:40] <hjmf> k
[02:40] <asac> and maybe play around with searchurl instead of -p to test clues
[02:40] <asac> on a refined set of bugs
[02:41] <asac> ok ... now lunch for real :)
[02:41] <hjmf> bon profit!
[02:42] <hjmf> it should be  bugxml -afirefox "MASTER" "This is a master bug"
[02:42] <hjmf> instead of -p
[02:42] <asac> yeah
[02:42] <hjmf> not tested yet (from the error output)
[02:42] <hjmf> k
[02:46] <gnomefreak> hmmmm looks like only one clue file
[02:46] <gnomefreak> file:///home/gnomefreak/.bughelper/packages/firefox.info
[02:46] <hjmf> yes, you have to provide new ones as in bugxml -afirefox "MASTER" "This is a master bug"
[02:46] <hjmf> it works now, its showing all masters
[02:47] <gnomefreak> doe that line work ro do i need to add bugnumbers and such?
[02:47] <hjmf> with bughelper -pfirefox "MASTER"
[02:47] <hjmf> no, it just search for MASTER
[02:47] <hjmf> and returns the urls as is:
[02:47] <hjmf> http://launchpad.net/bugs/45008 [firefox upstream: Fix Released/Unknown] [firefox Ubuntu: Confirmed/High]  - This is a master bug
[02:47] <ubotu> Malone bug 45008 in firefox "MASTER firefox theme crash" [High,Confirmed] 
[02:48] <gnomefreak> hmmmmm maybe i should be cd;ed somewhere?
[02:48] <gnomefreak> i get error when running bugxml
[02:48] <hjmf> watch the config file that asac posted:
[02:48] <hjmf> http://pastebin.ubuntu-nl.org/16112/
[02:49] <hjmf> be sure that the line is: Local-Packages-Dir: ~/ubuntu_bzr/bughelper-data.main
[02:49] <gnomefreak> what do i do with that? it just gives his dir. and interval times
[02:50] <gnomefreak> ah
[02:50] <hjmf> read ^^ :)
[02:50] <hjmf> I downloaded the bzr stuff to ubuntu_bzr, just use your own path
[02:52] <gnomefreak> my config file is same as his
[02:52] <gnomefreak> its in ~/.bughelper/config
[02:52] <hjmf> it's the path to  your local bughelper-data.main
[02:52] <hjmf> directory
[02:53] <hjmf> that one with the .info files
[02:53] <gnomefreak> ~/.bughelper/packages/firefox.info
[02:54] <hjmf> well In my case is where I downloaded the bzr repo
[02:54] <hjmf> i did
[02:54] <hjmf> mkdir -p bughelper-data.main ; cd bughelper-data.main
[02:54] <hjmf> bzr branch sftp://hmontoliu@bazaar.launchpad.net/%7Ebugsquad/bughelper-data/main/ bughelper-data.main
[02:55] <hjmf> so the path in my case is
[02:55] <gnomefreak> so on the line Local-Packages-Dir: i should have a dir
[02:55] <hjmf> ~/ubuntu_bzr/bughelper-data.main
[02:55] <hjmf> yes
[02:56] <gnomefreak> no error that time
[02:56] <gnomefreak> jsut gave me back prompt so lets try
[02:56] <hjmf> I'll try to use bughelper, though I'm actually using this stuff to quickly find dups
[02:56] <hjmf>  sed -n '/^#\(.[0-9] *\)/ {s/0x.[^ ] * in //;p}' retraced_stacktrace.txt
[02:57] <hjmf> | sed -n '/#4 / {s/#4 \(.[^ ] *\) .*/STACK_SIGNATURE="\1"/p;}; /#5 / {s/#5 \(.[^ ] *\) .*/STACK_SIGNATURE_1="\1"/p;q}'
[02:57] <hjmf> and hence
[02:57] <hjmf> firefox -remote "openurl(https://bugs.launchpad.net/ubuntu/+source/${PACKAGE}/+bugs?field.searchtext=${STACK_SIGNATURE}&orderby=-datecreated,new-window)
[02:58] <hjmf> that opens firefox seaching for the stacksignature in the summary of firefox / mozilla-thunderbird... etc bug reports
[02:58] <hjmf> it is called just after the retrace is finish
[02:59] <hjmf> is faster than bughelper (but ofcouse only searchs in bug summary)
[02:59] <hjmf> hopefully bughelper may search on attachments too
[02:59] <hjmf> dont know
[03:06] <gnomefreak> bughelper only searches summarys?
[03:06] <hjmf> dont know
[03:06] <hjmf> I'm looking
[03:06] <gnomefreak> search status would be a good idea and search importantce
[03:07] <gnomefreak> filtering would be needed at that point though
[03:08] <hjmf> Admiral_Chicago: hi
[03:09] <Admiral_Chicago> hey there hjmf
[03:09] <Admiral_Chicago> wow, just woke up
[03:09] <hjmf> Admiral_Chicago: does bugheper search in attachments?
[03:09] <hjmf> if you know
[03:09] <hjmf> 'morning
[03:09] <hjmf> :)
[03:09] <Admiral_Chicago> hjmf: yes
[03:09] <Admiral_Chicago> you use the -A flag
[03:09] <hjmf> thanks :)
[03:10] <hjmf> oops ofcourse, just RTFM :-P
[03:11] <gnomefreak> Admiral_Chicago: status search?
[03:11] <hjmf> --status=STRING
[03:11] <hjmf>               filter on given bug status
[03:12] <Admiral_Chicago> gnomefreak: hjmf has it
[03:12] <hjmf> --importance=STRING
[03:12] <hjmf>               filter on given bug importance
[03:12] <hjmf> but no tags AFAIK
[03:13] <Admiral_Chicago> nope, tags support needs to be added
[03:13] <gnomefreak> hjmf: how did you do that bugxml -Afirefox?
[03:13] <hjmf> bugxml -afirefox "MASTER" "This is a master bug"
[03:13] <hjmf> it was just the first attempt
[03:14] <Admiral_Chicago> gnomefreak: bughelper -p -a firefox "Searchterm" "This bug is X,Y,Z"
[03:14] <Admiral_Chicago> actually give me a sec
[03:14] <Admiral_Chicago> iirc...
[03:16] <hjmf> afk for a while
[03:17] <Admiral_Chicago> bugxml is for clue files
[03:17] <Admiral_Chicago> bughelper runs clue files and custom search terms
[03:17] <Admiral_Chicago> i lied above about the command to use gnomefreak
[03:17] <gnomefreak> oh
[03:18] <Admiral_Chicago> let me see which one to actually use
[03:18] <gnomefreak> good thing i waited
[03:18] <Admiral_Chicago> I ran 'freddy@omg-gnus:~$ bughelper -A -p firefox MASTER this is a master report' but i'm waiting on output
[03:19] <asac> the buxml i mentioned above is known to work
[03:19] <asac> where is the problem?
[03:20] <Admiral_Chicago> asac: give me a moment to read...
[03:20] <Admiral_Chicago> ah okay
[03:20] <Admiral_Chicago> you may not want to search attachments, let me see
[03:21] <asac> actually i would like to have that rule in bugsquad firefox.info
[03:21] <asac> and add the clues from david (updated to latest tags)
[03:21] <Admiral_Chicago> to automatically search attachment
[03:21] <asac> https://wiki.ubuntu.com/MozillaTeam/Bugs/Bughelper/ClueFile
[03:21] <gnomefreak> nsGenericElement::HandleDOMEvent
[03:22] <asac> Admiral_Chicago: ?
[03:22] <asac> i guess the MASTER clue does not want to search attachments right? can we specify this in clue file?
[03:22] <asac> or just command line?
[03:22] <Admiral_Chicago> reading...
[03:23] <gnomefreak> can i just add that to bottom of the clue file?
[03:23] <gnomefreak> @nsXULElement::HandleDOMEvent
[03:23] <asac> gnomefreak: it has to be valid xml
[03:23] <Admiral_Chicago> asac: that clue file isn't commited anywhere in bughelper
[03:23] <asac> gnomefreak: if you just want to search for strings
[03:23] <gnomefreak> ignore my random pastes
[03:23] <asac> just use the bugxml -afirefox ... command
[03:24] <asac> its committed
[03:24] <gnomefreak> asac: i want to search status
[03:24] <asac> read above :) (~140 lines) :)
[03:24] <gnomefreak> i have master set up already
[03:24] <gnomefreak> whats teh chances of those being the same :(
[03:24] <asac> Admiral_Chicago: search for bzr branch
[03:24] <asac> in irc log
[03:24] <asac> ... or did you just join?
[03:25] <gnomefreak> brb let me re read thsi stack
[03:26] <Admiral_Chicago> asac: i have the bzr branch pulle
[03:27] <asac> yes
[03:27] <gnomefreak> whats the chances this summary should be nsGenericElement::HandleDOMEvent instead of what it is? bug 87776
[03:27] <ubotu> Malone bug 87776 in firefox "MASTER Firefox Crashed [@~nsCOMPtr_base]  [@nsXULElement::HandleDOMEvent]  " [High,Confirmed]  https://launchpad.net/bugs/87776
[03:27] <asac> you have to add the directory in your .bughelper/config file
[03:27] <asac> as Local-Packages-Dir
[03:29] <gnomefreak> #10 of stack says nsGenericElement::HandleDOMEvent
[03:29] <Admiral_Chicago> I have one in ~/bzr/bughelper-data
[03:30] <Admiral_Chicago> which contains teh original .info file I commited, plus revisions by daniel
[03:31] <asac> yes
[03:31] <asac> if that is pulled then everything is fine
[03:31] <asac> :)
[03:32] <asac> pulled==used for bughelper runs
[03:32] <Admiral_Chicago> okay, so the next course of action should be....getting a list of master reports and adding the appropriate terms in the .info correct?
[03:32] <asac> ook ... daily bughelper results are http://daniel.holba.ch/bugs/
[03:33] <asac> Admiral_Chicago: right
[03:33] <asac> for each cras master bug use the signatures in title
[03:33] <gnomefreak> no revisions to pull
[03:33] <Admiral_Chicago> asac: neat. okay I'll get on that as soon as I can
[03:34] <Admiral_Chicago> i should have it by the next meeting
[03:34] <asac> Admiral_Chicago: sure ... hope you don't mind if we fill in some already
[03:34] <asac> :)
[03:34] <Admiral_Chicago> asac: go for it, let me know if help is needed
[03:35] <asac> yes ... for now its just branch stuff ... and if you see anything that is not yet clued, add it and push asap (so we don't accidentially duplicate efforts)
[03:35] <asac> mainly master crashes for now
[03:38] <hjmf> back again
[03:38] <hjmf> to push back to bzr ...
[03:38] <hjmf>  bzr push sftp://hmontoliu@bazaar.launchpad.net/%7Ebugsquad/bughelper-code/main/ bughelper-code.main
[03:39] <hjmf> right?
[03:39] <hjmf> <<noob here :)
[03:39] <asac> hjmf: you committed locally?
[03:39] <hjmf> no
[03:39] <hjmf> no idea
[03:39] <asac> you have to do that ... at best for each change one commit
[03:39] <asac> e.g. bzr commit -m "add MASTER clue" firefox.info
[03:39] <hjmf> k
[03:40] <asac> then add no tags matching (e.g. wiki)
[03:40] <asac> bzr commit -m "added no tag recognition clue for state 'Needs Info'" firefox.info
[03:40] <asac> if you have done that
[03:40] <asac> you can push like above
[03:40] <asac> of course test before pushing if everything still works
[03:40] <asac> then go :)
[03:40] <hjmf> ok, recording commands :)

[03:41] <asac> in the morning it do:
[03:41] <asac>   bzr merge
[03:41] <asac> when i changed things i look what i have done by:
[03:42] <asac>   bzr status # which gives me an overview what files are actually touched
[03:42] <asac> then i verify if changes are minimal and only contain one feature by
[03:42] <asac>   bzr diff
[03:42] <asac> if that is ok, i commit changes by
[03:42] <asac>   bzr commit <optional filenames>
[03:42] <asac> and insert a good comment :)
[03:43] <asac> if i am sure changes are fine, i push things by
[03:43] <asac>   bzr push
[03:43] <asac> if i push for first time i specify url :)
[03:43] <asac> bzr should remember ... otherwise use --remember option with bzr push

[03:44] <hjmf> OK, good howto (however I will read bzr man page before start messing things ) :)
[03:44] <asac> yeah :)
[03:44] <asac> you can test stuff on your selve
[03:44] <asac> e.g. cp -r yourcurrentbzrdir /to/somewhere/else/
[03:44] <asac> then
[03:44] <asac> bzr clone /to/somewhere/else /to/somewhere/different
[03:45] <asac> cd /to/somewhere/different/
[03:45] <asac> change stuff
[03:45] <asac> commit stuff
[03:45] <asac> push stuff to /to/somwehere/else
[03:45] <asac> :)
[03:45] <hjmf> :)
[03:45] <hjmf> lets play :)
[03:45] <asac> bzr is pretty simple and consitant about branching and merging et al
[03:46] <asac> yu can clone two times above ... make changes to one, push them, then merge them to the second location and so forht
[03:46] <asac> have fun
[03:46] <hjmf> I used to have a local cvs repo for playing, seems easier :)
[03:46] <hjmf> ty
[03:47] <asac> yeah ... for just local stuff its definitly best to use distributed system
[03:47] <asac> actually i don't see the benefit of any centralized system anymore
[03:47] <asac> as its just a subset of what we have with bzr and git
[03:48] <hjmf> have to learn what is git
[03:48] <hjmf> Git - Fast Version Control System
[03:48] <hjmf> things to look at :)
[03:55] <hjmf> wow! I have to halt the system, seems that the lights are failing somewhat
[03:55] <hjmf> lets close
[04:15] <gnomefreak> dh_install -a --sourcedir=debian/tmp
[04:15] <gnomefreak> cp: cannot stat `debian/tmp//usr/lib/iceape/libnspr4.so': No such file or directory
[04:15] <gnomefreak> dh_install: command returned error code 256
[04:15] <gnomefreak> :(
[04:15] <gnomefreak> make: *** [binary-arch]  Error 1
[04:17] <gnomefreak> could that be because im missing libnspr4
[04:23] <asac> yeah
[04:23] <asac> gnomefreak: look in iceape.install
[04:23] <asac> is there libnspr4.so?
[04:23] <asac> remove that line
[04:23] <asac> same for all libnss related
[04:23] <asac> you can see so files by
[04:23] <asac> dpkg -L libnss3-dev
[04:23] <asac> those don't belong to iceape.install anymore
[04:23] <asac> because they are not build anymore now that we use --with-system-
[04:23] <gnomefreak> ok looking for it
[04:25] <gnomefreak> in debian i have seperate iceape-*.install
[04:25] <gnomefreak> browser, calendar, mailnews, so on and so forth. ther eis a iceapedev.install
[04:27] <asac> gnomefreak: you will find it :)
[04:27] <asac> probably in browser
[04:29] <gnomefreak> .usr/lib/iceape/libnspr4.so
[04:29] <gnomefreak> that what im looking for :)
[04:32] <gnomefreak> ok running clean now than try again
[04:33] <asac> no
[04:33] <gnomefreak> no?
[04:33] <asac> you need to remove all libnss3 stuff as well
[04:33] <asac> as i said above
[04:33] <asac> otherwise you will run into it as well
[04:33] <asac> you can list files that you need remove by libnss3-dev
[04:33] <asac> path is defeinitly different but filenames should be the same
[04:34] <asac>  dpkg -L libnss3-dev
[04:34] <asac> and you don't need to clean to test
[04:34] <asac> just try
[04:34] <asac> fakeroot ./debian/rules binary
[04:34] <asac> after you did your changes
[04:34] <asac> will safe you lots of time
[04:34] <asac> testing stuff
[04:34] <asac> or dpkg-buildpackage -rfakeroot -nc
[04:35] <asac> which is the clean way to retry without clean
[04:35] <gnomefreak> gnomefreak@FeistyFawn:~/iceape-feisty/iceape-1.1.1/debian$ dpkg -L libnss3-devPackage `libnss3-dev' is not installed.
[04:36] <gnomefreak> i shouldnt have to remove it from my system and dpkg searches system
[04:36] <asac> why isn't it installed?
[04:36] <asac> you should
[04:36] <asac> same as libnspr4-dev
[04:37] <asac> or haven't you build it yet?
[04:37] <gnomefreak> libnspr4-dev is
[04:37] <gnomefreak> yes
[04:37] <asac> yes ... libnss3-dev is the other
[04:37] <asac> you need to add it to Build-Depends:
[04:37] <asac> as well
[04:37] <gnomefreak> ah its not installed
[04:37] <asac> right
[04:37] <asac> install it :)
[04:38] <gnomefreak> ok add both to build -deps?
[04:39] <asac> yes
[04:39] <asac> its just a formality ... but should be done
[04:39] <asac> actually its necessary ... to get to releasable state
[04:39] <gnomefreak> k fixed
[04:40] <asac> good
[04:40] <asac> maybe commit that change to control
[04:40] <asac> then fix debian/iceape-browser.install
[04:40] <asac> e.g. remove all files that are not in libnss3-dev as well from file list
[04:43] <gnomefreak> ok
[05:01] <AlexLatchford> no new firefox-trunk builds?
[05:02] <AlexLatchford> or are you following alpha releases?
[05:43] <asac> AlexLatchford: its when gnomefreak likes to update
[05:43] <asac> maybe push him to roll an update
[05:44] <asac> i guess we will follow beta releases for what goes into gutsy development release
[05:44] <asac> but for mt archive we can do weekly imo
[05:46] <asac> anyway, i think gnomefreak is still working on building apps on top of nss and nspr
[05:46] <asac> so probably thats why we haven't seen an update
[05:49] <AlexLatchford> ah okay
[05:49] <AlexLatchford> no, i was just wondering
[06:34] <gnomefreak> asac: nothing new on branch
[06:34] <gnomefreak> thats why i havent updated
[06:34] <gnomefreak> :)
[06:35] <gnomefreak> and yes been tied up with iceape
[06:35] <gnomefreak> ill tell ya fakeroot ./debian/rules binary doesnt cut off any time in build
[06:36] <gnomefreak> AlexLatchford: is there something broke in trunk build?
[06:46] <asac> gnomefreak: branch does not change ... you have to just change changelog url to get new upstream sources
[06:46] <asac> makes no sense that i check in changelog date changes for that :)
[06:47] <gnomefreak> looking at changelog
[06:48] <gnomefreak> firefox-trunk (2.99+2cvs20070328-0ubuntu0)??
[06:48] <gnomefreak> changing the date on that wont update the release will it? i was thinking it would just build with new date
[06:50] <gnomefreak> 2.99+2cvs20070404-0ubuntu0 is the latest update on mt repo
[06:53] <gnomefreak> MOZ_CVS_ROOT := :pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot << this will grab latest?
[06:53] <asac> now
[06:53] <asac> neworig gives you updated tarball
[06:53] <asac> if you change date
[06:53] <asac> e.g. neworig will always update to date you have in changelog version
[06:53] <gnomefreak> ah ok
[06:53] <asac> just change date
[06:53] <asac> run neworig
[06:53] <asac> spin
[06:53] <asac> done
[06:54] <gnomefreak> ok cool. this is built off nightlys?
[06:54] <asac> no right from cvs
[06:54] <asac> so: out own nightlies
[06:55] <asac> but since you won't update daily its more like weekly :)
[06:55] <asac> or "out randomlies" :)
[06:55] <gnomefreak> if i put todays date will it grab newest or do i need exact date
[06:55] <asac> you should put today-1 in
[06:55] <asac> to be safe
[06:55] <gnomefreak> ok thats what i was thinking
[06:55] <asac> e.g. 20070416
[06:59] <gnomefreak> ok updating atm. will build sometime tonight and have it uploaded by tomorrow afternoon.
[06:59] <gnomefreak> AlexLatchford: ^^^
[07:00] <gnomefreak> libplds4.so <<< thats not libnss nor libnspr :(
[07:01] <gnomefreak> asac: thats the new one same error as before but that package :(
[07:04] <asac> its in libnss
[07:04] <asac> you should look whats in there
[07:04] <asac> by dpkg -L libnss3-dev
[07:06] <gnomefreak> omg
[07:07] <gnomefreak> you would think libnssckbi.so would be in libnss3-dev
[07:08] <gnomefreak> nssckbi.h but no .so
[07:09] <asac> ?
[07:09] <asac> i think most simple is to run dpkg-buildpackage -rfakeroot -nc
[07:09] <gnomefreak> usr/lib/iceape/libnssckbi.so
[07:09] <asac> until it builds successfully
[07:09] <asac> and remove line by line
[07:09] <gnomefreak> k
[07:10] <asac> /usr/lib/libssl3.so
[07:10] <asac> /usr/lib/libsoftokn3.so
[07:10] <asac> /usr/lib/libsmime3.so
[07:10] <asac> /usr/lib/libnss3.so
[07:10] <asac> those are definitly in libnss
[07:11] <gnomefreak> yes i got all them
[07:11] <asac> good
[07:11] <gnomefreak> and same with libnspr4-dev .so's
[07:11] <asac> exactly
[07:11] <gnomefreak> but the name as a headerfile is what made me think to get rid of it but i ket it
[07:11] <gnomefreak> kept*
[07:11] <asac> yeah might be confusing
[07:12] <gnomefreak> only one way to find out :)
[07:16] <gnomefreak> -fakeroot -nc builds each package in order?
[07:16] <gnomefreak> -rfakeroot even
[07:17] <gnomefreak> ok finished no errors :)
[07:27] <gnomefreak> more sever weather :(
[07:28] <gnomefreak> severe*
[07:29] <gnomefreak> a fire warning :( wtf is this
[07:30] <gnomefreak> ill be back a little later
[07:44] <asac> crazy
[07:45] <asac> -nc does rebuild without clean
[07:45] <asac> its good to test in case something fails in the packaging stage
[07:45] <asac> that you want to verify that its now fixed
[07:45] <asac> if everything build fine with -nc do a full respin before upload
[07:45] <asac> gnomefreak: ^^^
[08:10] <asac> https://code.launchpad.net/~asac/firefox/ubuntu-2.0.0.x
[08:10] <asac> there we have new firefox 2.x
[08:10] <asac> for system nspr/nss ... based on cdbs + tarball + quilt packaging
[08:10] <asac> have fun
[08:10] <AlexLatchford> gnomefreak: ta
[09:54] <gnomefreak> asac: you here?
[09:55] <gnomefreak> trunk failed
[09:57] <gnomefreak> asac: is it safe to remove patches from firefox-trunk?
[09:59] <gnomefreak> bz364093-thebes-system-cairo-fix failed to apply
[10:05] <gnomefreak> 1 out of 1 hunk FAILED -- rejects in file gfx/thebes/src/gfxMatrix.cpp
[10:12] <gnomefreak> i think i disabled it lets see how it goes
[10:23] <gnomefreak> seems to be building. ill look into that patch once it finishes good or bad
[10:54] <asac> gnomefreak: yes
[10:54] <asac> you can disable that patch
[10:55] <asac> it has been landed in trunk cvs
[11:04] <asac> hmmm i missed trademark discussions
[11:04] <asac> in meeting
[11:06] <asac> gnomefreak: there is one more that needs to be build :)
[11:06] <asac> tomorrow another one will come ;)
[11:07] <asac> https://code.launchpad.net/~asac/firefox/ubuntu-2.0.0.x
[11:07] <asac> this is next package generation for firefox 2.0
[11:07] <asac> e.g. with quilt patches and embedded tarball  ... as well as already using system nspr/nss
[11:07] <asac> tomorrow i will push tbird 2.0 bzr branch as well
[11:08] <asac> if we have all this in the archive, we are well prepared for gutsy i guess
[11:08] <asac> and we can start to think about things like sunbird/lightning (e.g calendar extension)
[11:12] <gnomefreak> ok that is a bunch of building ;)
[11:12] <gnomefreak> the 2.0.0.x build is bzr?
[11:13] <gnomefreak> like the fx trunk?
[11:29] <asac> yes
[11:29] <asac> there is no new orig
[11:29] <asac> you have to tar up by your selve
[11:29] <asac> just drop the tarball in the top level
[11:29] <asac> and tar it up with top-level as prefix into orig.tar.gz
[11:30] <asac> let me see
[11:30] <asac> maybe i should add that target
[11:30] <asac> to ease your pain :)
[11:30] <asac> and tbird exactly the same as well
[11:30] <asac> at least when its out :)
[11:38] <asac> was it real hard?
[11:39] <asac> have you been struck besides some dirt?
[11:39] <gnomefreak> 4 inches of rain with 50+ mph winds
[11:40] <gnomefreak> i have 3 ~80 foot trees down and a crap load of debrie
[11:40] <gnomefreak> maybe ~60ish
[11:44] <gnomefreak> good thing is they fell in the woods so the 5 of us should beable to cut them up and leave them back there
[11:59] <asac> crazy
[11:59] <asac> that trees fall at that windspeeds
[12:00] <gnomefreak> wet ground + high winds + middle of woods
[12:00] <gnomefreak> 4 inches in 26hours
[12:00] <gnomefreak> 36hours
[12:07] <gnomefreak> asac: im wondering if we are gonna do the libnss3 and libnspr4 thing with firefox-trunk :(
[12:07] <asac> hmm 4 inches is a good bunch :) ... me wonders how much liters per square meter that is ... as volume gets me a etter feeling
[12:07] <asac> gnomefreak: sure ... i will update -trunk bzr soon
[12:07] <gnomefreak> k
[12:08] <asac> its basically the same
[12:08] <asac> just replace --without-system-nspr with
[12:08] <gnomefreak> oh hell i can do that next week on my side
[12:08] <asac> --with-system-nspr --with-system-nss :)
[12:08] <asac> sure
[12:08] <asac> i will just checkin stuff
[12:08] <asac> if you see you have  a merge feel free to respin (no need to hurry)
[12:08] <gnomefreak> as long as i dont need to rebuild nss and friends
[12:09] <asac> no you don't need to
[12:09] <asac> they should be stable
[12:09] <gnomefreak> cool
[12:09] <asac> and in case we have an update we won't need to rebuild all other apps
[12:09] <asac> e.g. thats the reason why we split those
[12:09] <asac> conflicts?
[12:09] <asac> ah
[12:09] <asac> you mean the -dev package
[12:09] <gnomefreak> yeah
[12:09] <asac> yes ... thats nothing to bother much
[12:09] <asac> developers have to suffer ;)
[12:09] <gnomefreak> yeah and the -0d
[12:09] <asac> for users its all somooth
[12:10] <gnomefreak> -dev will bring in -0d
[12:10] <asac> the -0d is so you can have old libnspr installed in parallel
[12:10] <asac> to new one
[12:10] <asac> so we get smooth transition
[12:10] <gnomefreak> oh ok
[12:10] <asac> ii  libnspr4            1.firefox2.0.0.3+1- Netscape Portable Runtime Library
[12:10] <gnomefreak> -0d is new for gutsy?
[12:10] <asac> ii  libnspr4-0d         1.8.0.10-3ubuntu1   NetScape Portable Runtime Library
[12:10] <asac> e.g. -> no problem
[12:10] <asac> yes
[12:11] <gnomefreak> ok is this on us?
[12:11] <asac> what?
[12:11] <asac> actually everything should be fine
[12:11] <gnomefreak> are we building the new nss and friends for gutsy repos?
[12:11] <asac> yes ... epiphany will just pull in new libnspr4 if it gets eventually respun
[12:12] <asac> otherwise it will use libnspr4 ... read: smooth transition
[12:12] <gnomefreak> true
[12:12] <asac> gnomefreak: its one aspect of the repo to test this in advance ... yes.
[12:12] <gnomefreak> true
[12:13] <asac> e.g. you could try if just respinning works
[12:13] <asac> epiphany
[12:13] <gnomefreak> yay -trunk built fine
[12:13] <asac> i will do that eventually
[12:13] <asac> i guess you don't need to
[12:13] <asac> have enough things to do for the moment i guess :)
[12:13] <gnomefreak> i thought epiphany was the -desktop teams package
[12:14] <asac> sure ... but since we lead the transition we should figure out for them
[12:14] <gnomefreak> true
[12:14] <asac> at least test how it works and if they need to do something ... then drop instructions
[12:14] <asac> like: respin
[12:14] <gnomefreak> as long as you let them know im sure they wont mind
[12:14] <asac> or ... do this + that, then respin
[12:14] <gnomefreak> true
[12:15] <asac> ah ... because we provide testing repo?
[12:15] <asac> na thats not a problem. We are in free software here
[12:15] <gnomefreak> no for gutsy.
[12:15] <asac> we just have to take care for proper versioning
[12:15] <asac> for other people packages i mean
[12:15] <asac> we can just release them as we like
[12:15] <gnomefreak> ah ok
[12:15] <asac> but i don't think we want to :)
[12:15] <asac> we just want to test locally if rebuilding works fine
[12:16] <asac> then pass that info to desktop team
[12:16] <asac> and if they ask for help, then help
[12:16] <gnomefreak> yeah
[12:16] <gnomefreak> that sounds better
[12:16] <gnomefreak> @schedule new_york
[12:16] <ubotu> Schedule for America/New_York: Current meeting: Community Council | 18 Apr 08:00: Edubuntu | 19 Apr 11:00: Development Team | 24 Apr 16:00: Technical Board | 25 Apr 16:00: Edubuntu | 26 Apr 16:00: MOTU
[12:16] <asac> still running CC ?
[12:17] <gnomefreak> yep
[12:17] <gnomefreak> they last forever
[12:17] <asac> gnomefreak: can you explain me the difference of ubuntu-dev vs. motu ?
[12:18] <gnomefreak> motu == universe and multiverse packages
[12:18] <asac> yeah ... and ubuntu-dev is universe as well, right?
[12:18] <gnomefreak> ubuntu-devel does all packages
[12:18] <asac> hmm?
[12:18] <gnomefreak> yes
[12:18] <asac> no core-devel can upload to main
[12:19] <asac> and restricted which ubuntu-dev cannot
[12:19] <gnomefreak> or core == canonical
[12:19] <gnomefreak> oh
[12:19] <asac> no core-devel is just core-team ... for main and restricted
[12:19] <gnomefreak> than im not sure
[12:19] <asac> core-devel is automatically ubuntu-dev (which according to lp upload packages to universe)
[12:19] <asac> however core-devs are not automatically motu ... which made me wonder in the first place :)
[12:20] <gnomefreak> core-devel is over everyone i would think
[12:20] <gnomefreak> anyone with main upload rights should beablet o upload to uni and multi
[12:20] <gnomefreak> afaik
[12:20] <asac> not sure ... looking at launchpad team pages ... core-devs cannot upload to multiverse without being motu
[12:20] <asac> which they are not
[12:21] <gnomefreak> thats kind of eh
[12:21] <asac> but i am not sure ... maybe core-devs can upload everywhere ... but team dependencies are not properly setup
[12:21] <gnomefreak> maybe because multi is all nonfree packages?
[12:21] <asac> hmm
[12:21] <asac> core-dev can upload to restricted
[12:21] <asac> might be not as nonfree however :)
[12:21] <gnomefreak> hmmmmm
[12:22] <asac> but probably a good thing not to be associated with multiverse :)
[12:22] <asac> in case someone sues ;)
[12:22] <gnomefreak> that makes me wonder about the diff between restrictedd and multi
[12:22] <asac> restricted is shipped on CD
[12:22] <gnomefreak> asac: you should have main and uni at the very least
[12:22] <gnomefreak> ah
[12:22] <asac> so essential things to make ubuntu work out of box where otherwise users woudlbe disappointed
[12:23] <asac> e.g. drivers
[12:23] <asac> for video
[12:23] <gnomefreak> good point
[12:23] <asac> wireless
[12:23] <asac> etc
[12:23] <gnomefreak> multi is packages not really needed for anything but make people happy
[12:23] <asac> yes
[12:24] <gnomefreak> lol we are talking about cloaks in -ops :(
[12:24] <gnomefreak> you will be uploading iceape right?
[12:24] <gnomefreak> or do i need to use revu?
[12:24] <asac> unless someone comes up with major complains ... i will yes
[12:25] <gnomefreak> ok cool
[12:25] <asac> no ... though i don't understand revu exactly, i will happily take sponsorship ... for mozilla packages
[12:25] <asac> that go to universe
[12:25] <gnomefreak> ok
[12:26] <asac> i guess if you request on revu they will ask me anyways :)
[12:26] <gnomefreak> true