[01:15] <asac> s/dues/due/
[01:16] <Ubulette> i don't have a single issue tied to system nspr/nss
[01:16] <asac> Ubulette: actually you don't have to deal with that release-fiddling if you want
[01:16] <asac> Ubulette: have you tested with in source nss/nspr?
[01:17] <asac> Ubulette: that doesn't matter ... we cannot overlay nss/nspr from main with more or less cvs snapshot in universe
[01:17] <asac> i have a bad feeling about pushing something like it
[01:17] <asac> not talking about release manager ;)
[01:17] <Ubulette> as you want.
[01:19] <Ubulette> I'm gonna retry my form. if i disappear, it's xgl
[01:19] <asac> Ubulette: i can test that ;)
[01:19] <asac> i mean i can test the system-nss/nspr thing
[01:19] <asac> if you prefer to do that let me know
[01:20] <asac> Ubulette: so do we want to rename the xulrunner package?
[01:20] <asac> i would prefer to name it xulrunner-1.9 ... not trunk
[01:21] <Ubulette> it's already the name
[01:21] <asac> the source package?
[01:21] <Ubulette> yep
[01:22] <asac> ah cool ... so you fixed that?
[01:22] <Ubulette> Source: xulrunner-1.9
[01:22] <Ubulette> no, since day 1
[01:23] <asac> ok ... then lets just adapt the branch names to reflect that .... and firefox-trunk => firefox-granparadiso or firefox-3.0 ?
[01:28] <asac> anything about branchnames/packagename you see not being consolidated/streamlined enough?
[01:37] <Ubulette> i don't like the -trunk in source package of nss/nspr (but we've discussed that in august)
[01:37] <Ubulette> trunk as branch name for ff is ugly
[01:38] <Ubulette> grandparadiso too
[01:38] <Ubulette> those two should be mergeable to make our life easier
[01:39] <Ubulette> so appname is an issue
[01:39] <Ubulette> and I like minefield.. clearly says what it is
[01:42] <asac> yes ... read what i wrote above
[01:42] <asac> firefox-3.0 is an option imo
[01:43] <asac> it would require one transition for gutsy users _now_ ... but better now than at some point ;)
[01:44] <Ubulette> i agree, better now than later
[01:44] <asac> so what can we still do for beta?
[01:45] <Ubulette> so either we drop the minefields branding and switch to default (gp) for our dev
[01:45] <Ubulette> or we keep two branches in parallel forever
[01:45] <asac> i think we could say: UNRELEASED uploads are minefield and gutsy uploads to ppa are at least a bit QAed so we can call it gp
[01:46] <asac> we could then add a check in rules for the distribution in changelog
[01:46] <asac> (just an idea)
[01:46] <asac> the package name would still be the same though
[01:46] <asac> all firefox-3.0
[01:47] <Ubulette> why not just do post beta cvs ? like 3.0~a7+cvs
[01:47] <asac> you mean to check if its minefield?
[01:47] <Ubulette> instead of 3.0~a8~cvs
[01:47] <asac> how did you get to that point in this conversation
[01:48] <asac> i mean is that still the same topic or am i just confused;)
[01:48] <Ubulette> let's start with plain a8. we release it, then continue with a8+cvs
[01:48] <Ubulette> instead of with a9~cvs
[01:48] <Ubulette> so it could still use appname gp
[01:48] <asac> i have no hard opinion on that ... except that selecting + in the version in gnome-terminal is a pain by double-clicking ;)
[01:48] <Ubulette> then all our patches are good and easy to merge
[01:49] <Ubulette> but it's still trunk between released
[01:49] <Ubulette> but it's still trunk between releases
[01:49] <asac> Ubulette: i don't understand how this version shift contributes to fix "so it could still use appname gp"
[01:49] <Ubulette> just add + to the selection
[01:49] <Ubulette> it's in prefs
[01:49] <asac> i see no difference
[01:49] <asac> either we decide to ship any build as gp
[01:50] <Ubulette> yes
[01:50] <asac> (branding)
[01:50] <asac> or we try to detect changelog what is gp and what is minefield ;)
[01:50] <asac> somehow i like the latter more
[01:50] <asac> in any case, please explain to me how changing the version scheme we use contributes to this
[01:51] <Ubulette> today it's easy. mozilla/browser/config/version.txt tells us
[01:51] <asac> what is easy?
[01:51] <Ubulette> gp vs minefield
[01:51] <asac> how?
[01:51] <asac> pre?
[01:51] <Ubulette> m/pre/
[01:53] <asac> i don't like introspecting the upstream source from debian packaging better look at changelog with dpkg-parsechangelog
[01:53] <asac> why can't we just see if there is cvs in it? then use minefield
[01:53] <asac> otherwise gp?
[01:53] <asac> is there a difference?
[01:56] <Ubulette> i have to think about that. I'm tired and i have to get up very early :P
[01:56] <asac> anyway ... i am fine with both ... just consider dpkg-parsechangelog a bit cleaner as it would be more universal
[01:57] <Ubulette> mozclient will need something from upstream files
[01:57] <asac> Ubulette: ok let me know in the morning... if i find a few minutes i would do abit and don't want to do something I don't know all ideas for ;)
[01:58] <asac> for now its just firefox
[02:05] <Ubulette> sure. 'night
[02:06] <mertiki> asac : wow.. do you sleep sometimes?
[02:13] <asac> no ;)
[02:13] <asac> just work + sport :)
[02:14] <asac> but will be off now ;)
[02:20] <mertiki> hehe
[06:01] <therealnanotube> hello everyone. i notice that the firefox 2.0.0.7 signature was made using a different key than the one used for previous releases. is that as it should be? did mozilla start using a different key?
[12:55] <bluekuja> asac: talked with mertiki?
[01:01] <asac> bluekuja: yes. thanks.
[01:01] <bluekuja> asac: if you want me to upload that too, just ping ;)
[01:02] <asac> yes ... its not completely ready. mertiki wanted to improve it today based on my comments
[01:03] <bluekuja> asac: ok cool, let me know when we'll have a good package
[01:03] <bluekuja> :)
[01:33] <janimo> Ubulette_: hi, you mentioned having added libnspr4-dev as a dep of xulrunner-1.9-dev (it is needed) but it does not seem to be there in the package
[02:32] <bluekuja> asac: you there?
[02:33] <bluekuja> asac: is ok to modify a makefile.am/in without a patch system?
[03:09] <asac> how?
[03:10] <asac> bluekuja: ?
[03:19] <bluekuja> asac: directly
[03:19] <bluekuja> asac: http://launchpadlibrarian.net/9376568/rkward_0.4.7a-1ubuntu2.debidff
[03:19] <bluekuja> I told him to provide a patch
[03:19] <bluekuja> for it
[03:22] <bluekuja> asac; ?
[03:26] <asac> bluekuja: the makefile.in looks strange
[03:26] <asac> +#>- 	$(INSTALL_DATA) $(srcdir)/rkward.desktop /usr/share/applications/rkward.desktop #>+ 1
[03:26] <asac> ??
[03:26] <asac> where is that from?
[03:26] <bluekuja> destdir missing
[03:26] <asac> no
[03:26] <asac> thats just crazy
[03:26] <asac> i mean it looks like it was once a patch
[03:27] <asac> now its a makefile
[03:27] <asac> ?
[03:27] <bluekuja> mmm...
[03:27] <asac> bluekuja: please apply the makefile.am ...and see how makefile.in looks like afterwards
[03:27] <asac> rerun automake for that
[03:27] <bluekuja> lets see
[03:31] <bluekuja> asac: what should I check now'
[03:32] <bluekuja> asac: the final package with that debdiff was ok
[03:32] <bluekuja> e.g it fixes the issues
[03:39] <bluekuja> asac: write me back when you get here again, I leave because I'm not feeling really good these days
[03:41] <asac> bluekuja: the diff of the Makefile.in
[06:00] <cwong1> asac: hi
[06:01] <asac> hey
[06:01] <cwong1> asac: can u tell me how to have a static page as the start page again, please?
[06:04] <cwong1> I put the startpage in midbrowser/locales/en-us, right?    Do I access it using chrome://content/midbrowser/startpage.html?
[06:12] <asac> cwong1: hmm ... you can try it in location bar
[06:15] <asac> sorry ... i am completely busted atm, because of the freeze that will be lifted tomorrow morning
[06:16] <cwong1> atm?
[06:17] <asac> at the moment
[06:17] <cwong1> k
[07:56] <janimo> asac, thanks for applying the nm autostart patch.
[07:56] <janimo> did you get a chance to look at the libgnome deps one?
[08:04] <Ubulette_> hi
[08:17] <gnomefreak> how would i find the ip of my router?
[08:19] <gnomefreak> this one looks kind of weird but i guess ill try it
[08:20] <Ubulette> gnomefreak, http://www.findmyip.com/
[08:20] <ubuntu-laptop> ty
[08:20] <ubuntu-laptop> looking
[08:20] <ubuntu-laptop> thats not what im looking for :( but ty
[08:21] <ubuntu-laptop> i need ip of router not my pc ip
[08:21] <ubuntu-laptop> trying to set up printing from laptop to pc with printer
[08:21] <Ubulette> internally or the ip you've got from your isp ?
[08:22] <ubuntu-laptop> it should be a 192.168 iirc
[08:23] <ubuntu-laptop> i cant remember the last xx.x numbers
[08:23] <Ubulette> plenty of methods
[08:24] <Ubulette> route
[08:24] <Ubulette> ifconfig and look for the gateway
[08:24] <Ubulette> traceroute something
[08:24] <ubuntu-laptop> got it ty
[08:24] <Ubulette> ping -b your broadcast addr
[08:25] <ubuntu-laptop> lets see if it works :)
[08:26] <Ubulette> depends on the router
[08:27] <ubuntu-laptop> i had it working years ago for 3 desktops in breezy but never for a laptop and its been 2 years since i had that set up
[08:28] <ubuntu-laptop> than again maybe its not right
[08:28] <ubuntu-laptop> shit
[08:29] <ubuntu-laptop> it says it is here but nothing working in printer
[08:29] <ubuntu-laptop> should i have restarted cups here
[08:33] <ubuntu-laptop> looks as if that isnt right ip
[08:34] <ubuntu-laptop> 192.168.0.x
[08:34] <ubuntu-laptop> not sure what x is yet
[08:37] <ubuntu-laptop> im looking for the ip that you type in ff and it brings up router config
[08:40] <janimo> Ubulette: xulrunner-1.9-dev still does not seem to depend on libnspr4-dev
[08:41] <janimo> although it includes headers form it
[08:42] <Ubulette> hmm. you're right. same for nss-dev I guess
[08:45] <Ubulette> gnomefreak, could you ask admin to drop everything in universe from our ppa?
[08:45] <Ubulette> well, maybe not everything (iceape and co)
[08:48] <ubuntu-laptop> asac: asked the other day and i havent heard of an answer
[08:49] <ubuntu-laptop> Ubulette: just bump the version and we will tell people to use main for the time being. feistys PPA i havent gotten to yet to move it to main
[08:50] <ubuntu-laptop> ill ask again though see if i get answer
[08:50] <Ubulette> i dont want to add an epoch. we'll have to keep it forever. it's not worth it
[08:51] <ubuntu-laptop> i didnt want to either thats why i havent
[08:51] <ubuntu-laptop> but atm there is no way for us to do it i asked kiko if admins can
[08:52] <ubuntu-laptop> god i need a new frigging laptop
[08:52] <ubuntu-laptop> no noone including admins can remove anything from PPA
[08:53] <ubuntu-laptop> brb checking on printer
[08:56] <gnomefreak> grrrrrrrrrrr
[08:56] <Ubulette> lol,bug #137767
[08:56] <ubotu> Launchpad bug 137767 in soyuz "Launchpad-Bugs-Fixed in PPA uploads closes Ubuntu bugs" [High,Fix committed]  https://launchpad.net/bugs/137767
[08:57] <ubuntu-laptop> its a nice day so i wanted to do court paperwork outside and print inside butr noooooooo
[08:58] <ubuntu-laptop> s/butr/but
[08:59] <Ubulette> Bug #128127
[08:59] <ubotu> Launchpad bug 128127 in soyuz "remove-package should work for PPAs" [Medium,Confirmed]  https://launchpad.net/bugs/128127
[08:59] <ubuntu-laptop> Ubulette: they were hinking with 1.9 release
[08:59] <ubuntu-laptop> or 1.1.9 whatever version it was
[08:59] <ubuntu-laptop> that i heard weeks ago though
[09:01] <ubuntu-laptop> but i think  1.1.9 was released this week already but i could be wrong
[09:04] <tonyyarusso> nope
[09:04] <ubuntu-laptop> wasnt releeased?
[09:04] <ubuntu-laptop> released
[09:04] <ubuntu-laptop> or wasnt added to that milestone?
[09:06] <tonyyarusso> wasn't released
[09:06] <ubuntu-laptop> anyone want to go into my office and see if the page printed? im tired of getting up and down
[09:07] <ubuntu-laptop> they need to find a was of checking from remote spot
[09:07] <ubuntu-laptop> s/was/way
[09:10] <ubuntu-laptop> ill be back on other pc in a bit
[09:21] <asac> Ubulette: gnomefreak: instead of bumping versions et al .... we want to rename the package
[09:22] <gnomefreak> asac: really rather name it something rather than adding a epoche to it
[09:22] <gnomefreak> makes more sense to me that way
[09:22] <gnomefreak> wtf isnt firefox auto logging me into LP anymore
[09:22] <asac> well epoch is not a problem either, but we wnat to rename anyway ... so
[09:23] <Ubulette> asac, sorry, didn't have time this morning
[09:23] <asac> yeah ... i was busted anyway
[09:23] <asac> have to wait until after beta nwo
[09:23] <gnomefreak> is it possible to wait until release for 1.1.9
[09:23] <gnomefreak> i would like to see if the remove is added than to make life simplier
[09:24] <gnomefreak> than the rename isnt needed ;)
[09:24] <gnomefreak> hmmm ok good its fixed
[09:27] <Ubulette> well, we can rename now anyway
[09:27] <asac> sure
[09:27] <asac> but please choose the version wisely ;)
[09:27] <asac> xulrunner-1.9 ... firefox-3.0 ... is the way to go i guess
[09:28] <gnomefreak> i agree
[09:41] <Ubulette> should we use ".ubuntu" inside branch names ?
[09:42] <Ubulette> or are we completely out of the debian philosophy ?
[09:47] <Ubulette> asac, gnomefreak: what about this http://pastebin.mozilla.org/202680 ?
[09:48] <gnomefreak> we cant have same name
[09:48] <gnomefreak> you have trunk and gp as same name
[09:48] <gnomefreak> we really need to fix dpi settings
[09:49] <gnomefreak> name them same as branch?
[09:50] <gnomefreak> having -trunk and -gp the same name is only gonna get confusing after a while
[09:50] <Ubulette> except ff, why can't we use the same name for source names ?
[09:50] <gnomefreak> Ubulette: are they the same?
[09:51] <Ubulette> ff is special because of the minefield branding
[09:51] <gnomefreak> is nss and nss-devel the same package?
[09:51] <gnomefreak> sorry nss and nss-trunk
[09:51] <Ubulette> nss.dev is just fresher than the released nss
[09:51] <gnomefreak> if nto same way would you name it the same
[09:51] <gnomefreak> s/nto/not
[09:52] <Ubulette> I mean, we work in *.dev, when it's ready, we push to non-dev and release
[09:52] <gnomefreak> once its built how would determine what one is what?
[09:52] <gnomefreak> they would have same source name-versiondates
[09:52] <Ubulette> just looking at version and changelog
[09:53] <gnomefreak> Ubulette: and once named the same would it have to be changed again at a later date or is it perm.
[09:53] <Ubulette> what do you mean ?
[09:54] <gnomefreak> Ubulette: you and asac changed names of all sources alot in the past 2 weeks this is why we are changing them now. name them so they dont need to be changed again is what i suggest atm
[09:54] <gnomefreak> atelast trunk
[09:54] <gnomefreak> and gp
[09:54] <Ubulette> gnomefreak, today, source names are the same for the two nss branches, it's not a problem
[09:55] <Ubulette> forget about firefox for now, think nss/nspr/xul
[09:56] <gnomefreak> firefox-3.0_trunk and firefox-3.0
[09:56] <gnomefreak> what is wrong with keeping -trunk  or _trunk
[09:57] <gnomefreak> its always gonna be trunk until release than we dont need to worry about keeping it
[09:57] <gnomefreak> gp is gonna be gp/minefield until release
[09:57] <gnomefreak> than with firefox-4.0 no versioning issues
[09:57] <gnomefreak> or 3.0.0.1
[09:58] <gnomefreak> or whatever
[09:58] <gnomefreak> this way you know what you are getting if its weekly updated or release only update
[09:59] <gnomefreak> or instead of using the ~ use a -
[09:59] <gnomefreak> that will fix that issue as well
[10:00] <Ubulette> asac, what's your view on all that ?
[10:00] <gnomefreak> brb
[10:00] <gnomefreak> think smart not hard or you will burn yourself out IMHO
[10:03] <Jazzva> Evening... :)
[10:03] <Ubulette> hi
[10:03] <Jazzva> How's it going? :)
[10:03] <Jazzva> asac: You around?
[10:04] <bluekuja> mertiki, heya
[10:04] <mertiki> bluekuja : Hi!
[10:05] <bluekuja> mertiki, news from your package?
[10:07] <gnomefreak> my only point being is that me Ubulette and asac can tell the difference easy but end user isnt gonna see source so they need to beable to tell what one they have installed thats why i say leave -trunk or _trunk or something like that that will identify it for end users
[10:08] <gnomefreak> if they install trunk and gp they will see the same firefox-3.0.deb
[10:08] <mertiki> bluekuja : Not yet, I uploaded the last lightning-extension-locales package to REVU and emailed Alex
[10:08] <gnomefreak> or nss.dsb for either package
[10:08] <bluekuja> mertiki, cool
[10:08] <bluekuja> :)
[10:08] <mertiki> bluekuja : I'm very proud of the work I did in that package :) The script is all automatic :D
[10:08] <gnomefreak> anyone have the dpi bug handy for gutsy?
[10:08] <gnomefreak> i cant remember what dir the change is needed in
[10:09] <mertiki> gnomefreak : the dpi bug handy effects are? Because I've two programs ( virtualBox and Hplip ) that have huge fonts
[10:09] <bluekuja> mertiki, you rock
[10:09] <bluekuja> :)
[10:09] <gnomefreak> mertiki: mine are way too damn small
[10:10] <Jazzva> gnomefreak: That's in FF 2, right?
[10:10] <mertiki> gnomefreak : In my case, everything is OK except the two programs I spoke about
[10:10] <mertiki> bluekuja : :D
[10:10] <gnomefreak> Jazzva: my whole desktop
[10:10] <gnomefreak> its a xorg bug iirc
[10:11] <Jazzva> gnomefreak: Ouch... I've been having it in FF... the fonts are too small, even though everything is set to 10px... But the rest is fine...
[10:11] <Jazzva> Granparadiso has ok font size...
[10:11] <mertiki> bluekuja : I'm working to do the same for the enigmail-locales, but I found a lot of problems. Asac really helped me around lightning-extension-locales script
[10:11] <gnomefreak> Jazzva: im having the gutsy bug and i cant find the damn bug :(
[10:12] <Jazzva> gnomefreak: And does setting fonts to be bigger change anything?
[10:12] <gnomefreak> Jazzva: what dir?
[10:12] <Jazzva> gnomefreak: dunno...
[10:13] <bluekuja> mertiki, asac is a pro so you can learn everything you need from him :)
[10:13] <gnomefreak> i need the dpi corecct settings and the dir/file its in
[10:13] <gnomefreak> clean feisty install upgrade to gutsy
[10:14] <gnomefreak> i had upgraded before the dpi bug surfaced so it didnt effect me
[10:14] <mertiki> bluekuja : When he gave me his vision of what my lightning-extension-locale could be. Everything I though was " Yes, that's the ultimate all good solution " :P
[10:14] <bluekuja> lol
[10:14] <bluekuja> :d
[10:14] <bluekuja> :D
[10:14] <mertiki> bluekuja : So I learn a lot from him :)
[10:14] <Jazzva> gnomefreak: But shouldn't it effect everyone? We all get the same updates :).
[10:15] <gnomefreak> Jazzva: i dont know why it didnt effect upgrade <maybe because it was a --dont-overwrite? unless you go from version x to version z?
[10:15] <gnomefreak> i dont know why it never got to me before
[10:15] <gnomefreak> fff2 always had smaller fonts for me but this is first desktop has done it
[10:15] <gnomefreak> ff2 even
[10:15] <Jazzva> gnomefreak: Yeah, that sounds reasonable...
[10:16] <Jazzva> So, you need the config file for that setting?
[10:16] <mertiki> bluekuja : I think that it's pretty late to add packages to Gutsy, when does new Gutsy updates are Freezes? At the BetaFreeze?
[10:16] <gnomefreak> yes
[10:16] <gnomefreak> im fairly sure its should be around 96-98dpi but cant remember
[10:16] <gnomefreak> the file and the settins are on the bug iirc
[10:17] <gnomefreak> bug 139700
[10:17] <ubotu> Launchpad bug 139700 in xorg "dpi setting incorrect" [Undecided,New]  https://launchpad.net/bugs/139700
[10:17] <bluekuja> mertiki, https://wiki.ubuntu.com/GutsyReleaseSchedule
[10:20] <Jazzva> gnomefreak: Hmm, my xorg.conf doesn't containt the mentioned settings...
[10:20] <gnomefreak> mine either
[10:23] <Ubulette_> damn, lost synchro 12min :(
[10:23] <mertiki> bluekuja : thanks ( I should need to read sometimes :) )
[10:24] <bluekuja> mertiki, np
[10:24] <mertiki> bluekuja : did you see asac today?
[10:24] <bluekuja> mertiki, this morning yes
[10:25] <Jazzva> gnomefreak: Have you tried setting the DisplaySize?
[10:25] <Ubulette_> 1h ago too
[10:25] <gnomefreak> bug 140540
[10:25] <ubotu> Launchpad bug 140540 in libgnome "[Gutsy update]  Gnome application font sizes too small to read" [High,Fix released]  https://launchpad.net/bugs/140540
[10:25] <gnomefreak> jano brb
[10:25] <mertiki> it would be great if I can have is comments on the last package I uploaded, it's maybe the "real" one :)
[10:25] <gnomefreak> Jazzva: no brb
[10:26] <asac> mertiki: hi
[10:26] <mertiki> hi asac!
[10:26] <mertiki> how are you :)
[10:26] <asac> hard day ;)
[10:27] <mertiki> asac : yeah for me too
[10:27] <Jazzva> Evening, asac :)
[10:27] <asac> oh Jazzva is back :)
[10:27] <Jazzva> Pretty much... *jumps_around*
[10:28] <mertiki> asac : if you have time, I uploaded my latest update to the lightning-extension-locales to REVU
[10:28] <Jazzva> asac, is it too late/too hard to start implementing that isUserAdmin check in ubugox?
[10:28] <asac> Jazzva: no ... its just too late for beta
[10:28] <asac> Jazzva: but we can add that afterwards
[10:28] <gnomefreak> ok now fonts are bigger in terminal looks almost goos
[10:28] <gnomefreak> good
[10:29] <asac> Jazzva: the trick is to sell this change as a bug-fix  ... not a new feature ;)
[10:29] <Jazzva> asac: We can :)? I thought it's not possible to implement new features in current version after beta freeze...
[10:29] <Jazzva> *lol* Oh, that...
[10:29] <asac> its a bug
[10:29] <asac> users that cannot install packagse, shouldn't
[10:29] <Jazzva> I get it...
[10:29] <mertiki> asac : I'm here for a while, you can speak to me at anytime, if I don't answer, I'll see your message once I come back
[10:29] <gnomefreak> now ff fonts are woo damn big just a little too big but fixable
[10:30] <Jazzva> gnomefreak: See if this is useful... http://gentoo-wiki.com/HOWTO_Xorg_and_Fonts#.2Fetc.2FX11.2Fxorg.conf
[10:30] <asac> mertiki: you have a direct link?
[10:30] <asac> to your revu upload?
[10:30] <mertiki> asac: http://revu.tauware.de/details.py?upid=265
[10:30] <Jazzva> Ok, dinner time... BBL...
[10:30] <gnomefreak> sorry Jazzva seee if what is usefull
[10:31] <Jazzva> gnomefreak: Well, there's a part about setting dpi...
[10:31] <Jazzva> Oh... you left the channel :)
[10:31] <gnomefreak> where?
[10:31] <Jazzva> gnomefreak: This http://gentoo-wiki.com/HOWTO_Xorg_and_Fonts#.2Fetc.2FX11.2Fxorg.conf
[10:31] <gnomefreak> ty
[10:32] <Jazzva> no problem :)...
[10:38] <asac> mertiki: are the res-files shipped? or are those just temporary files?
[10:39] <mertiki> asac : what do you mean by shipped? When you run the regen-package.sh, they all are overwrited by autogenerated ones
[10:39] <asac> what would happen when you remove the res-files folder at the end of regen- ?
[10:40] <mertiki> which line ?
[10:40] <asac> last line :)
[10:41] <asac> those are created during regen-package.sh, right?
[10:41] <mertiki> Ok, what would happen if I remove the res-files? The package won't build. these files are the files used to build the package
[10:41] <asac> so you probably can remove them
[10:41] <asac> let me look again ;)
[10:41] <mertiki> asac : of course :)
[10:42] <mertiki> asac : actually, regen-package.sh creates all these so the package can be built. It's just one step away from the all-automatic-rules-file
[10:42] <mertiki> asac : but I wanted to speak to you before that step
[10:42] <asac> mertiki: so what is your idea?
[10:44] <mertiki> asac : I almost don't know anything about rules file and I can't get to clearly know if including the content of the regen-package.sh into the rules file can be done and if it's a real good idea, I think that's what you talked about yeaterday right?
[10:45] <asac> yeah i think so
[10:45] <gnomefreak> resolution:    126x121 dots per inch is whats wrong
[10:45] <mertiki> asac : actually, it's still very simple, people just needs to upgrade the lightning XPI file and the Langlist.text to upgrade the whole package in one step
[10:45] <Ubulette> gnomefreak, ati ?
[10:45] <gnomefreak> nvidia
[10:45] <Ubulette> which driver ?
[10:45] <gnomefreak> have to figure out how to change that value
[10:46] <gnomefreak> -glx-new
[10:46] <mertiki> asac : Now, does including the regen-package.sh into the rules file will causes problems? What if we want to modify something by hand after?
[10:47] <asac> mertiki: i will come back to you ;)
[10:47] <asac> in a few minutes
[10:47] <mertiki> asac : np
[10:47] <asac> have to do something right now :)
[10:47] <mertiki> ok :)
[10:53] <asac> mertiki: you don't know anything about makefiles?
[10:54] <mertiki> asac : so basic things, I learn very quickly, but I think that I'm better in c++ and PHP that I'm in simple makefiles yet
[10:54] <Ubulette> asac, did you comment on my branch exchange with gnomefreak ? (got disconnected for +10min)
[10:55] <mertiki> asac : by reading doc and exploring existing makefiles, I would learn a lot very quickly
[10:55] <gnomefreak> Ubulette: i didnt see you change anything
[10:55] <asac> Ubulette: no ... sorry
[10:55] <gnomefreak> Ubulette: i wouldnt get it in email since its not set up atm
[10:55] <asac> Ubulette: when was that?
[10:55] <gnomefreak> oh that topic
[10:56] <gnomefreak> asac: not naming trunk and gp the same
[10:56] <gnomefreak> keep trunk in name for trunk
[10:56] <Ubulette> gnomefreak, I didn't. just wanted to see what everyone has to say 1st
[10:56] <gnomefreak> ff-3.0-trunk or something
[10:56] <gnomefreak> Ubulette: i thought that was for me but it was for asac
[10:57] <mertiki> asac : Since now, do you think it would be a good idea to add regen-package.sh into the rules file?
[10:57] <Ubulette> asac, between 21:47 and 22:00
[11:00] <asac> mertiki: let me do something
[11:01] <mertiki> asac : ok
[11:01] <asac> Ubulette: ok what will happen to your current .dev branches?
[11:01] <asac> for nss/nspr
[11:03] <Ubulette> I can pull that back to my own space as you never seemed interested by those 2 too edgy
[11:11] <asac> Ubulette: ok ... whatever you want
[11:14] <Ubulette> no comment about http://pastebin.mozilla.org/202680 ?
[11:14] <Ubulette> asac ^^
[11:14] <Ubulette> i'm surprised...
[11:18] <asac> Ubulette: is there an easter-egg hidden?
[11:19] <mertiki> asac : according to the changes that I did into that package in the last days, to you like what I made?
[11:20] <Ubulette> asac, so you like it that way ? no opposition ?
[11:21] <Ubulette> the ff branding is still unclear
[11:22] <asac> Ubulette: ist mostly what we discussed yesterady
[11:22] <asac> Ubulette: unless nss/nspr implies that we ship those in official gutsy ... i am fine with it
[11:22] <Ubulette> should we drop minefield branding and use a unique appname instead of our current two (meaning we'll no longer be able to install/run both at the same time)
[11:23] <asac> Ubulette: when i look at that paste its obvious imo ... there won't be two different binary packages installable at the same time of firefox-3.0 series
[11:23] <asac> either you use gutsy ... or you use ppa ... or you use your archive
[11:23] <Ubulette> for nss/nspr, I assume that by ff 3.0 (in 1 or 2 months) they will be released upstream
[11:23] <asac> yes, but not in time for gutsy
[11:24] <asac> ffox is january i guess
[11:26] <Ubulette> i bet on november
[11:26] <asac> that would be a astonishing ...
[11:28] <mertiki> asac : in few minutes, I'll be gone for 1 or 2 hours
[11:28] <asac> mertiki: ok
[11:29] <asac> mertiki: we probably have to wait till after betwa freeze anyway
[11:29] <Ubulette> asac, in update manager, ff 2.0.0.6+2-0u4 reads "This is a build of a random development version (aka trunk). It is ment for preview and not for production use. "
[11:29] <mertiki> asac : to upload the language packs?
[11:30] <Jazzva> asac: what's the changes I need to do if I want to submit a package to debian? Do I need to make a debian chroot? unstable?
[11:31] <Jazzva> *what're
[11:33] <Ubulette> asac, http://www.sofaraway.org/ubuntu/tmp/Update-manager.png
[11:38] <mertiki> asac : I'm gone, but I'll read every message you'll write me when I'll come back
[11:40] <asac> Ubulette: thanks
[11:41] <asac> Ubulette: apparently nobody reads that ;)
[11:41] <asac> it has been in there since gutsy ;)
[11:42] <asac> nobody complained
[11:42] <asac> interesting
[11:46] <gnomefreak> i thought we got rid of that or did i just remove it from iceape
[11:47] <gnomefreak> hmm it is still there
[12:10] <Ubulette> well well well, rename or not rename. asac seems ok, gnomefreak disagreed. not a strong consensus..
[12:11] <gnomefreak> im worried about end-users i can care less for us
[12:11] <gnomefreak> trying to keep end-users from being confused. same name == same package to them
[12:12] <gnomefreak> they will only see the packages being installed
[12:12] <asac> gnomefreak: which end-users?
[12:12] <gnomefreak> the ones that use PPA
[12:12] <asac> gnomefreak: and whats the problem for them?
[12:12] <gnomefreak> or if you rename for gutsy as well
[12:13] <asac> gnomefreak: PPA users sometimes have to accept sufferage
[12:13] <asac> if everything was perfect we wouldn't upload to PPA ;)
[12:13] <gnomefreak> asac: if we are using trunk in gutsy repo and you also rename gutsys gp its gomma confuse the hell out of people
[12:13] <gnomefreak> or is gutsy name for gp staying different?
[12:13] <asac> better confuse them now, than after a full release cycle
[12:14] <asac> gnomefreak: at some point we have to rename firefox-granparadiso
[12:14] <asac> better now than after a full release, where all the universe users that run latest stable get confused by a rename
[12:14] <gnomefreak> if you have PPA version named firefox-3.0 and the one in gutsy repo being firefox-3.0 we are gonna have issues im sure with nss nspr depends if the user is just looking not thinking
[12:15] <asac> gnomefreak: ?
[12:15] <gnomefreak> only difference would be the -mt
[12:15] <asac> gnomefreak: thats not a problem xulrunner in gutsy universe will not use system-nspr/nss for various reasons
[12:15] <gnomefreak> what do you plan on naming firefox-gp in gutsy repo?
[12:15] <asac> transition to firefox-3.0
[12:15] <gnomefreak> ok xulrunner than
[12:16] <gnomefreak> asac: keep ppa and official repos with differnet names
[12:16] <asac> why?
[12:16] <asac> thats not reasonable imo
[12:16] <gnomefreak> you really dont want to name them the same asac think about what kind of idiots use ubuntu
[12:16] <gnomefreak> if you forget join #ubuntu
[12:16] <gnomefreak> ;)(
[12:16] <asac> the cleanest approach is to project the development of upstream in a single release line
[12:16] <asac> this means *all* packages have the same name
[12:17] <asac> its just that the version in changelog differs
[12:17] <gnomefreak> use trunk for feistya nd gutsy
[12:17] <asac> gnomefreak: see ... the point is: we need just one package
[12:17] <asac> ppa has more fine grained releases
[12:18] <gnomefreak> but i dont think the names should be simular because they report bug on PPA with wroing xulrunner cuase all kindds of wasted time for usa
[12:18] <asac> so people that want that can use just that
[12:18] <gnomefreak> us
[12:18] <asac> if they don't want to use that anymore, they just drop ppa line and on next gutsy update they will be back in safe-place
[12:18] <gnomefreak> if we had xulrunner 1.9 in repos i could care less TBH since than it would work
[12:18] <asac> gnomefreak: i don't think its a problem
[12:18] <asac> we want bug reports on our preview packages as well
[12:19] <asac> at least for ppa releases
[12:19] <gnomefreak> not on LP we dont
[12:19] <asac> not atm, but in future
[12:19] <asac> would make sense
[12:19] <gnomefreak> asac: than the packages for sure would need differnet names
[12:19] <asac> its the same package ... we do these preview releases to get feedback ... why fear that they file bugs in LP ?
[12:19] <asac> gnomefreak: why?
[12:19] <asac> there is no reason
[12:20] <asac> just use same bug db
[12:20] <asac> as we use same package name
[12:20] <gnomefreak> asac: how many people triage our bugs and dont know wtf they are doing
[12:20] <gnomefreak> they close bugs that we need open why the hell do we want to go behind people checking
[12:21] <asac> but i don't think that this is an argument on the current topic
[12:21] <asac> what does that have to do with using same name in ppa/gutsy
[12:21] <gnomefreak> its gonna cause un needed bullshit IMHO but please name it as you wish, im only trying to advoid future issues since i deal with the morons on a daily basis
[12:22] <asac> as always there will be a bit confusion in the beginning
[12:22] <gnomefreak> when someone asks how to install packages on gutsy it makes me think of how smart people really are not
[12:22] <asac> after some time, things will just work as usual ... thats usually the case
[12:22] <asac> and remember that we make things simpler by unifying the package name
[12:22] <gnomefreak> after the 1st part of confusion than we do something else to add to it
[12:22] <gnomefreak> and so on
[12:22] <asac> but that will always be the case
[12:23] <gnomefreak> avoid*
[12:23] <gnomefreak> ok picture your on gutsy
[12:23] <asac> i mean ... things go on ... while the first problem gets solve a new arrives et al
[12:23] <gnomefreak> you install firefox3.0.deb from official repos
[12:23] <gnomefreak> than you see PPA and install xulrunner and firefox-3.0.deb
[12:23] <gnomefreak> what is gonna happen?
[12:24] <asac> why?
[12:24] <gnomefreak> asac: people will do it
[12:24] <asac> if i am on final gutsy, i just run
[12:24] <gnomefreak> i can promise that
[12:24] <asac> apt-get install firefox-3.0
[12:24] <asac> that will come from universe
[12:24] <asac> if people as on forums for more bleeding edge builds
[12:24] <gnomefreak> asac: you are now using xulrunner 1.8
[12:24] <asac> they might be pointed to PPA
[12:24] <asac> otherwise those are people that we ask to verify a fix, et al
[12:24] <asac> gnomefreak: well xulrunner-1.9 will be installed
[12:25] <gnomefreak> now you install from PPA what is gonna happen? will firefox-3.0 be removed or will it complain it cant install it its already installed
[12:25] <gnomefreak> asac: when was this? i thought that was for heron?
[12:25] <asac> gnomefreak: if a user decides to use our PPA ... he will just upgrade to the latest we have
[12:26] <asac> around the official release date this should be pretty much the same that will be in official ... in between there might be changes like new development, etc
[12:26] <gnomefreak> if using the same name there is no upgrade unless we leave the dates attached and forget dates for official packages?
[12:26] <asac> gnomefreak: yes ... but thats the way it works ... versioning must provide a nice upgrade path
[12:26] <gnomefreak> asac: IMHO if we want it in lets get it in so we can gt bugs worked out of it
[12:26] <gnomefreak> since we have to deal with a shit load of packages depending on it
[12:27] <asac> thats what we are doing
[12:27] <gnomefreak> asac: we dont have anything that depends on xulrunner atm
[12:27] <asac> yes, thats the plan
[12:27] <gnomefreak> everything depending on firefox atm should be depending on xulrunner instead (whole point of adding it as i recall)
[12:27] <asac> bring firefox-3.0 with xulrunner-1.9 to gutsy
[12:28] <asac> PPA will receive regular updates in between, with a version that allows them to upgrade to next official as well
[12:28] <gnomefreak> epiphany -desktop packages and so on will depend on xulrunner instead of firefox
[12:28] <asac> in gutsy+1
[12:28] <gnomefreak> what happened for gutsy?
[12:28] <asac> but bring it in gutsy now, so people can develop against it
[12:28] <gnomefreak> was it pushed off?
[12:28] <asac> and bring their packages in shape
[12:28] <gnomefreak> thought the point was for gutsy
[12:29] <gnomefreak> thats why it was talked about during feisty devel
[12:29] <asac> right from the beginning of heron dev cycle
[12:29] <asac> gnomefreak: no epiphany et al will stay on firefox for guty
[12:29] <gnomefreak> than i missed the meeting that it was deffered at
[12:29] <asac> he?
[12:30] <asac> what was planned?
[12:30] <asac> i dont understand
[12:30] <gnomefreak> it was supposed to be in gutsy that i had heard as plannd during one of the meetings in feisty devel cycle
[12:30] <asac> well ... talk is cheap
[12:30] <asac> probably they assumed that it would be ready by now
[12:30] <asac> but its not
[12:30] <gnomefreak> for gutsy packages to depend on xulrunner so they are not installing 2 browsers to get one
[12:31] <asac> thats not done
[12:31] <gnomefreak> whats wrong with it for xulrunner 1.8?
[12:31] <asac> but that was clear right from the beginning
[12:31] <asac> firefox cannot be build against it
[12:31] <gnomefreak> ?
[12:31] <asac> 1.8 is not yet ready
[12:31] <gnomefreak> 2.0 cant be?
[12:31] <gnomefreak> ah ok
[12:32] <asac> 1.9 is the first that is good enough to build firefox against it
[12:32] <gnomefreak> but ff2.0 cant build against it can it?
[12:32] <asac> you can look from both directions, right
[12:32] <gnomefreak> im assuming xulrunner 1.9 has something to do with gecko1.9
[12:33] <gnomefreak> and 1.8 gecko 1.8
[12:33] <gnomefreak> i would think if xulrunner is using gecko 1.9 ff 2.0 cant build on it since ff2.0 is gecko 1.8
[12:36] <Ubulette> correct
[12:37] <gnomefreak> anyway i have more important things to take care of (court papaers) please name it as you wish
[12:37] <asac> me shivers in fear
[12:38] <asac> i just uploaded the network-manager bomb ;)
[12:38] <Ubulette> gasp
[12:38] <Ubulette> :)
[12:38] <Ubulette> so, should I keep .ubuntu. in branch names too ?
[12:40] <Ubulette> hmm. how are feisty/gutsy nss/nspr managed today (I see no branch)
[12:40] <Ubulette> asac ?
[12:41] <Ubulette> behind that, the question is, should nspr branch be called nspr-4.7 like ff and xul ?
[12:42] <Ubulette> in opposition to the current (released) 4.6 (4.6.6-3)
[12:43] <Ubulette> no strong feeling here as 1/ no existing branch of 4.6 and 2/ nspr is not installed with a version
[12:43] <Ubulette> all the same for nss
[12:51] <asac> Ubulette: today nss/nspr are synched from debian
[12:51] <asac> Ubulette: and no ... nspr should aim to be a lib, so we want a sonamed binary package name
[12:52] <asac> ok if your network is down tomorrow, then i am the one to blame :)
[12:52] <asac> ifupdown uploaded
[12:53] <asac> good thing is that people without net have no voice ;)
[12:55] <mertiki> asac : I'm currently working on enigmail-locales too so I would need to know if you want me to build something very similar for enigmail-locales than what I made for lightning-extension-locales ( regen-package.sh )
[12:57] <asac> mertiki: no ... not before gutsy final
[12:57] <asac> mertiki: we shouldn't stress things too much at this point of cycle
[12:58] <mertiki> asac : So I just change the XPIRegFiles to something like langpack-ca-CA@enigmail and that's all?
[01:00] <asac> mertiki: you want to migrate directories? or just add new .xpis?
[01:02] <gnomefreak> are we planing on fixing bugs in tbird 1.5.0.13?
[01:02] <gnomefreak> stupid little annoying bugs
[01:02] <asac> unless they are regressions ... i don't think so
[01:02] <mertiki> asac : I already added some XPI and removed some to keep the ones that works under Thunderbird 2, but I don't know if you remember but two language pack currently have the same ThunderbirdRegKey name so they are overwriting each other. You proposed me to fix that using langpack-ca-CA@enigmail and not {847b3a00-7b61-11d4-8f02-006008948af5}
[01:03] <gnomefreak> no its the link issue for extensions
[01:03] <gnomefreak> it was there in 2.0 and we fix it but not for 1.5
[01:03] <asac> mertiki: ok, but please do that just for one locale
[01:03] <asac> mertiki: at best fix the locale that is new
[01:04] <asac> gnomefreak: link issue for extensions?
[01:04] <mertiki> asac : no problem, I'll do it like you tell me to
[01:04] <gnomefreak> asac: bug 140980
[01:04] <ubotu> Launchpad bug 140980 in mozilla-thunderbird "thunderbird extensions directs you to firefox addons" [Undecided,New]  https://launchpad.net/bugs/140980
[01:04] <gnomefreak> its fixed in 2.0
[01:05] <asac> gnomefreak: anything else?
[01:05] <gnomefreak> so far thats all ive seen
[01:05] <gnomefreak> im going through email atm
[01:05] <Ubulette> asac, they've patched cairo sources for some glyphs. definitely not good to bring with-system-cairo back
[01:06] <asac> i am willing to do a sru at some poing, but we should find more nasty bugs that are easy to fix if possible
[01:06] <asac> Ubulette: wow
[01:06] <Ubulette> mozilla bug 362682
[01:06] <ubotu> Mozilla bug 362682 in GFX: Thebes "Some Unicode characters are no longer displayed with certain fonts (e.g. Arial)" [Normal,Resolved: fixed]  http://bugzilla.mozilla.org/show_bug.cgi?id=362682
[01:06] <gnomefreak> ok ill explain for now and see what else we have
[01:07] <Ubulette> asac, it's not even protected by a moz ifdef :(
[01:07] <asac> Ubulette: that looks bad ... is this a defintiency in cairo api or just lazy moz devs?
[01:08] <asac> Ubulette: well ... actually thats better for us, because they look more like they might be suitable for upstream inclusion
[01:08] <asac> upstream==cairo
[01:09] <gnomefreak> what is the needtester tag?
[01:09] <gnomefreak> i thought mt-needtesters
[01:10] <Ubulette> asac, comment 13: "his patch makes an assumptiont that we don't use our own font prefs and that
[01:10] <Ubulette> we use fontconfig instead which i think we're going to go with.
[01:10] <Ubulette> "
[01:10] <gnomefreak> ah i had 2 s' that i shouldnt have
[01:11] <Ubulette> god, I have 9999 emails in my mailbox
[01:12] <gnomefreak> asac: another easy fix is bug 119291
[01:12] <ubotu> Launchpad bug 119291 in thunderbird "thunderbird 2.0 should use a local startpage" [Wishlist,Confirmed]  https://launchpad.net/bugs/119291
[01:12] <gnomefreak> for 1.5.0.13 atleast fixed for gutsy so im assuming feistys has issue as well
[01:12] <gnomefreak> i dont have a way to test atm
[01:15] <mertiki> asac : do you want me to modify the addNewXPI.sh from enigmail-locales to work inside the debian/script folder?