[01:19] <Ubulette> seems i'm almost done with seamonkey-2.0
[01:25] <Ubulette> http://www.sofaraway.org/ubuntu/tmp/SeaMonkey2.png
[01:25] <Ubulette> asac, gnomefreak : ^^
[01:25] <Ubulette> :)
[05:03] <Zylogue> I have a question about mozilla applicaitons and the use of rsync as a backup/restore tool...basically to test for DR purposes, I rsynced my /home to my server.  I re-installed gutsy, and rsynced back.  installed tbird and then tbird would not run.  is there a better way of doing this?  is there an option in tbird to 'import' that older information?
[05:04] <Zylogue> do I need to have installed and run tbird once, before rsyncing back?
[05:09] <tonyyarusso> Zylogue: Thunderbird should just take your old profile dir - I just backup my .mozilla-thunderbird and paste it into new installations before the first run of TB
[05:09] <tonyyarusso> so, should work
[05:09] <tonyyarusso> you might want to try the -P option
[05:11] <Zylogue> tonyyarusso, Thanks.  I will give the -p a try.  I'm just testing.  I want to get fully away from MS, and need to have a good backup soluiton in place.  I like hte difference between rsync for backup versus tarballs, as only the changes get moved.
[08:14] <gnomefreak> Ubulette: how is the new addon "installer" or download manager whatever its called
[08:15] <gnomefreak> morning asac
[08:25] <gnomefreak> well bad news is disabling the reply-to-list-support patch doesnt fix this. I would love to know how icedove was fixed since they dont have the patch
[08:28] <gnomefreak> might have the reason
[08:33] <gnomefreak> asac: it looks like the patch you applied in icedove per debian bug 381273 is not the same as our patch, here is both patches from top to line 277 is our patch and lines 281 to the end is debians (they look different to me but it might just be me
[08:33] <ubotu> Debian bug 381273 in thunderbird "thunderbird: Please apply patch to allow list replies" [Wishlist,Fixed] http://bugs.debian.org/381273
[08:48] <gnomefreak> wth is the quilt command to use a patch added to debian/patches and debian/patches/series
[08:49] <gnomefreak> none of the commands im using are adding that patch
[09:21] <gnomefreak> asac: if you do tbird today please take patch from debian bug 381273 and try it. it looks differnet than ours
[09:21] <ubotu> Debian bug 381273 in thunderbird "thunderbird: Please apply patch to allow list replies" [Wishlist,Fixed] http://bugs.debian.org/381273
[09:58] <gnomefreak> oops forgot to give you the patches
[10:00] <gnomefreak> here are the 2 patches on pastebin
[10:00] <gnomefreak> http://pastebin.mozilla.org/229125
[10:14] <tonyyarusso> Oh thank god - TB is finally going to be able to handle mailing lists?
[10:14] <gnomefreak> tonyyarusso: it used to but we will see
[10:14] <tonyyarusso> gnomefreak: it did?  When?
[10:15] <gnomefreak> tonyyarusso: pre 2.0 final with our patch
[10:15] <tonyyarusso> ah
[10:15] <gnomefreak> some reason the patches failed to work after final release
[14:07] <asac> gnomefreak: you can reuse the remove binonly script
[14:07] <asac> Ubulette: so what would be needed to make seamonkey work with xul-1.9?
[14:07] <asac> is there an upstream bug tracking this?
[14:29] <asac> reply to list extension 0.3 is out btw
[14:35] <asac> (maybe old news though)
[16:05] <gnomefreak> asac: i know its out im waiting on email to test with new profile. asac the issue with the script is where do i run it from how do i rename package version to right version ect.
[16:12] <gnomefreak> !aptfix
[16:12] <ubotu> If an APT front-end crashed and your database is locked, try this in a !terminal: « sudo fuser -vki /var/lib/dpkg/lock;sudo dpkg --configure -a »
[16:14] <gnomefreak> reply to list 3.0 seems to work here (i dont know why its crashing for the user
[16:23] <gnomefreak> just replied to kubuntu-users post using it so if it worked than i guess closing that bug is a good idea but im not sure why it fails for all but me, i removed icedove and i moved ~/.mozilla-thunderbird and started clean to test it
[16:29] <bluekuja> gnomefreak, heya
[16:30] <bluekuja> gnomefreak, any news?
[16:30] <bluekuja> for iceape?
[16:30] <gnomefreak> bluekuja: 64 has been built but there was another flood of packages
[16:30] <gnomefreak> i havent checked since yesterday morning
[16:30] <bluekuja> gnomefreak, just ping me when everything is ready
[16:30] <gnomefreak> once done with email ill look
[16:32] <gnomefreak> bluekuja: its done https://edge.launchpad.net/~gnomefreak/+archive
[16:32] <bluekuja> gnomefreak, is it a new upstream release?
[16:32] <bluekuja> bug fix?
[16:32] <gnomefreak> its security release from upstream
[16:33] <bluekuja> gnomefreak, ok, can you point me again to REVU link?
[16:33] <gnomefreak> yeah
[16:34] <gnomefreak> http://revu.tauware.de/details.py?upid=438
[16:34] <bluekuja> thanks
[16:34] <bluekuja> gnomefreak, added to TODO
[16:34] <gnomefreak> thank you :)
[16:34] <bluekuja> will be done today or tomorrow
[16:34] <bluekuja> :)
[16:34] <gnomefreak> thanks fine thank you for doing it
[16:35] <bluekuja> np, thanks to you for it
[16:35] <bluekuja> :)
[16:35] <bluekuja> gnomefreak, any news from ML side?
[16:35] <bluekuja> got any response?
[16:35] <gnomefreak> as soon as i figure out this nobinonly crap i will have sunbird up and ready i think
[16:35] <gnomefreak> bluekuja: i thought i added you already but i might have forgot, let me look and add you
[16:36] <bluekuja> gnomefreak, great :)
[16:36] <gnomefreak> bluekuja: i need an email address that you want to use
[16:36] <bluekuja> gnomefreak, bluekuja@ubuntu.com
[16:36] <bluekuja> is fine
[16:37] <gnomefreak> added
[16:37] <bluekuja> you rock thanks
[16:37] <bluekuja> :)
[16:37] <bluekuja> gnomefreak, will ping you when uploaded
[16:38] <gnomefreak> ok ty
[16:38] <gnomefreak> im sending you an email i hope :)
[16:38] <bluekuja> lol
[16:45] <gnomefreak> sent it let me know if you get it and can open it tbird is giving me issues today
[16:45] <bluekuja> gnomefreak, what's that?
[16:45] <gnomefreak> the email i sent you, you need it to access admin for ML
[16:45] <bluekuja> oh^^
[16:46] <bluekuja> gnomefreak, done, uncrypted
[16:46] <gnomefreak> :)
[16:47] <bluekuja> gnomefreak, was encrypted using which key?
[16:47] <bluekuja> mine?
[16:49] <bluekuja> ah no, your key
[16:49] <bluekuja> :)
[16:51] <gnomefreak> yeah i added your key but i will resend
[16:51] <gnomefreak> if needed
[16:52] <bluekuja> no, it's ok
[16:52] <bluekuja> :)
[16:52] <bluekuja> worked out
[16:52] <gnomefreak> ok cool
[17:52] <bluekuja> gnomefreak, iceace packaging side
[17:52] <bluekuja> is the as the last gutsy version?
[17:52] <bluekuja> I mean you took the gutsy debian's dir
[17:52] <gnomefreak> bluekuja: what do you mean?
[17:53] <bluekuja> and pushed it inside new u-r
[17:53] <gnomefreak> bluekuja: yes
[17:54] <gnomefreak> the only thng that differs is the changelog its not really gutsys deb dir.
[17:54] <gnomefreak> bluekuja: i used my bzr branch as always
[17:54] <bluekuja> gnomefreak, yes, but everything should be the same as gutsy version
[17:54] <bluekuja> you cannot change stuff without documenting it
[17:54] <gnomefreak> right
[17:54] <gnomefreak> changelog was only thing that needed change
[17:55] <gnomefreak> bluekuja: i did document everything
[17:55] <gnomefreak> bluekuja: the changelog should say upstream security release and the autoconf update
[17:55] <bluekuja> I see
[17:55] <bluekuja> new upstream release
[17:55] <bluekuja> and a patch update
[17:56] <gnomefreak> yes that should have been it
[17:56] <bluekuja> debian/patches/99_configure.dpatch: Updated for new release
[17:56] <gnomefreak> yep
[17:56] <bluekuja> so those are the only changes
[17:56] <bluekuja> you did
[17:56] <gnomefreak> yes and the changelog
[17:56] <bluekuja> yes
[17:56] <gnomefreak> thats all
[17:56] <bluekuja> asac: small question
[17:56] <bluekuja> asac: does a gutsy-security changelog entry
[17:57] <gnomefreak> its been pushed already
[17:57] <bluekuja> should be in hardy too?
[17:57] <bluekuja> gnomefreak, yes, seen
[17:57] <gnomefreak> i dont see an issue with it, since they were both rom same branch
[17:57] <gnomefreak> bluekuja: you mix debian and ubuntu changes why not gutsy and hardy
[17:57] <bluekuja> gnomefreak, yes
[17:58] <bluekuja> gnomefreak, but gutsy-security
[17:58] <bluekuja> is another repo
[17:58] <bluekuja> not hardy
[17:58] <bluekuja> or gutsy
[17:58] <gnomefreak> its gutsy no?
[17:58] <bluekuja>  Published in gutsy-updates on 2007-10-25
[17:58] <bluekuja> Published in gutsy-security on 2007-10-25
[17:58] <bluekuja>  Published in hardy-release on 2007-10-18
[17:58] <bluekuja> Published in gutsy-release on 2007-09-13
[17:59] <gnomefreak> how was it published on 2007-10-18?
[18:00] <bluekuja> gnomefreak, nope
[18:00] <gnomefreak> if needed i can remove the gutsy-securoty changelog entry but it shouldnt cause an issue afaik
[18:01] <bluekuja> https://launchpad.net/ubuntu/hardy/+source/iceape
[18:02] <bluekuja> iceape 1.1.4-1ubuntu2 is in hardy
[18:02] <gnomefreak> yes
[18:02] <gnomefreak> since it hasnt been pushed yet that is expected im just reading your published comments above
[18:02] <bluekuja> iceape (1.1.4-1ubuntu3) gutsy; urgency=low
[18:02] <bluekuja> can you merge it in one entry?
[18:03] <gnomefreak> bluekuja: not really
[18:03] <gnomefreak> ubuntu3 was never pushed
[18:03] <gnomefreak> remember i wanted to get it in but it was too late (after waiting of asac to push
[18:03] <bluekuja> so this should be a two-revisions upload
[18:03] <gnomefreak> i guess i should have combined the changes in ubuntu3 to 1.1.5 build
[18:04] <bluekuja> atm, we cannot upload it to gutsy
[18:04] <gnomefreak> its not going to gutsy
[18:04] <bluekuja> -1ubuntu3
[18:04] <bluekuja> so, you should merge it
[18:04] <gnomefreak> the changes for ubuntu3 were never pushed
[18:04] <bluekuja> with the hardy entry
[18:04] <bluekuja> yes
[18:04] <bluekuja> I know
[18:04] <gnomefreak> bluekuja: thats what i said i should do :)
[18:04] <bluekuja> but now we cannot upload
[18:05] <bluekuja> as gutsy
[18:05] <gnomefreak> ill fix it and revu it again
[18:05] <bluekuja> great
[18:05] <gnomefreak> bluekuja: those changes will never make it in gutsy
[18:05] <bluekuja> yea
[18:05] <gnomefreak> bluekuja: you want gutsys changelog entry taken out? the -security one
[18:05] <bluekuja> gnomefreak, I don't see it on REVU
[18:05] <bluekuja> but only on lp
[18:05] <bluekuja> which is correct
[18:06] <bluekuja> http://revu.tauware.de/revu1-incoming/iceape-0710270320/iceape-1.1.5/debian/changelog
[18:07] <bluekuja> gnomefreak, when it was uploaded to security
[18:07] <bluekuja> a new entry has been created
[18:07] <bluekuja> in LP
[18:07] <bluekuja> so it wont appear in our changelog
[18:07] <gnomefreak> thats fine
[18:07] <bluekuja> gnomefreak, plus
[18:07] <bluekuja> as I said
[18:07] <bluekuja> we should have *one* changelog's entry
[18:08] <bluekuja> with every change you made
[18:08] <bluekuja> plus 1ubuntu3 (never pushed)
[18:08] <bluekuja> merged in it
[18:08] <gnomefreak> see i did but forgot ubuntu3 wasnt pushed
[18:08] <bluekuja> np :)
[18:09] <bluekuja> gnomefreak, let me know when done
[18:09] <gnomefreak> ok shouldnt be long
[18:10] <bluekuja> oki
[18:10] <gnomefreak> going for smoke while it buildsa
[18:10] <bluekuja> fine
[18:21] <asac> i have the feeling i won't get anything done while here
[18:21] <asac> :(
[18:23] <bluekuja> asac: :9
[18:23] <bluekuja> *:)
[18:23] <bluekuja> asac: did you read my small question before?
[18:25] <asac> probably not :)
[18:25] <bluekuja> hehe
[18:25] <bluekuja> asac: should I include a gutsy-security changelog's entry
[18:25] <bluekuja> inside the whole changelog?
[18:26] <bluekuja> or not?
[18:27] <asac> for which package/update?
[18:27] <asac> iceape for hardy or what?
[18:28] <bluekuja> yep
[18:28] <bluekuja> iceape for hardy
[18:29] <asac> look how i did it for firefox
[18:30] <asac> since i merged the changes done for guts security update the changelog entry is there as well
[18:30] <bluekuja> yep
[18:30] <bluekuja> https://launchpad.net/ubuntu/hardy/+source/firefox/+changelog
[18:30] <asac> and yes ... in that case you should include the gutsy-security changelog entries in .changes as well
[18:30] <bluekuja> gnomefreak, include gutsy-security as well
[18:30] <bluekuja> in the changelog
[18:30]  * asac hoping that i really did that 
[18:30] <asac> :)
[18:30] <gnomefreak> i saw
[18:30] <gnomefreak> not the best of timing
[18:31] <asac> he?
[18:31] <bluekuja> gnomefreak, lol
[18:31] <bluekuja> gnomefreak, sorry, told it too late
[18:31] <bluekuja> but I wanted to ask to alex
[18:31] <bluekuja> to be sure of it
[18:31] <Ubulette> hi
 Ubulette: so what would be needed to make seamonkey work with xul-1.9?
 is there an upstream bug tracking this?
[18:33] <Ubulette> asac, 1st: fix the ftbfs in mailnews/addrbook, then see what's next :P
[18:33] <bluekuja> asac: bittorrent mail sent
[18:33] <bluekuja> asac: package built today
[18:34] <bluekuja> off for dinner
[18:34] <gnomefreak> bluekuja: ill ping you when uploaded
[18:34] <gnomefreak> i have to run out this afternoon sometime
[18:34] <gnomefreak> asac: having fun in boston?
[18:41]  * gnomefreak makes mental note to not build in debian dir
[18:41] <gnomefreak> although it does grab tarball from ftp.mozilla
[18:42] <Ubulette> :)
[18:48] <gnomefreak> bluekuja: uploading to revu im assuming it should be same link you already have.) im heading out for a while
[18:49] <gnomefreak> bluekuja: http://revu.tauware.de/details.py?upid=438 just in case. bbl
[19:08] <asac> Ubulette: ok i will try to talk to some seamonkey devs about seamonkey with xulrunner and whats the idea
[19:08] <asac> maybe there are blog entries about that?
[19:09] <asac> Ubulette: http://wiki.mozilla.org/SeaMonkey:suiterunner
[19:12] <Ubulette> yep, i've read that page. my understanding is that it's still in progress but maybe i'm wrong
[19:16] <Ubulette> asac, it seems there's no more -dev in seamonkey 2
[19:18] <Ubulette> nor any need for it
[19:20] <Ubulette> i guess that expected as it's a task for xul
[19:37] <Ubulette> mozilla bug 399233
[19:37] <ubotu> Mozilla bug 399233 in Phishing Protection "Phishing UI hidden by content, inconsistent with malware" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=399233
[19:38] <asac> Ubulette: wheneverf there are application specific components - read .idl files - there is a need for -dev
[19:39] <Ubulette> there's no such thing in dist
[19:39] <Ubulette> just usr/bin and usr/lib
[19:39] <Ubulette> no include/idl anywhere in dist
[19:40] <asac> hmmm ... are there no .idl files in mailnews/ hierarcdhy?
[19:40] <asac> otherwise you cannot write any mailnews specific extensions
[19:40] <Ubulette> hmm, i mean, in debian/tmp
[19:40] <Ubulette> dist has them
[19:40] <asac> same for thunderbird ... without the mail/ specific idls you won't be able to build engigmail for instance
[19:41] <asac> yeah ... but thats a bug in the build system then
[19:41] <Ubulette> why not use xulrunner-1.9-dev ?
[19:42] <asac> why? because those are no toolkit componentes?
[19:42] <asac> just think about thunderbird as an independent application ... the fact that it resides in the same CVS doesn't make a difference
[19:43] <asac> so xulrunner doesn't know anything about mail/
[19:43] <Ubulette> seamonkey 2 is just a xul app according to suiterunner specs
[19:43] <asac> nor about browser/ ... and all other application specific things
[19:44] <asac> Ubulette: yes ...but that doesn't make a difference ... a xul app can stil have interfaces to extend the application itself
[19:44] <asac> evenmike understood this at some point :)
[19:45] <asac> so being a xul app doesn't conflictwith being extensible through native components ... and those might even want to provide -dev package as well ... and so on and on
[19:48] <Ubulette> he said: "It is recommended that you use libxul-dev instead, if possible."
[19:51] <bluekuja> gnomefreak, I'm going to read then I move to sleep, I'll take care of it tomorrow
[19:51] <bluekuja> gnomefreak, gonna ping you when I start doing it
[19:52] <Ubulette> bluekuja, you're in italy right ?
[19:52] <bluekuja> Ubulette, yes
[19:52] <Ubulette> it's early to go to bed :)
[19:52] <bluekuja> Ubulette, lol, as I said I'm going to read my new python book
[19:52] <bluekuja> before sleeping
[19:53] <Ubulette> i usually fall asleep after half of page of such books ;)
[19:53] <bluekuja> lol
[19:53] <bluekuja> I read something like 20-30 pages
[19:53] <bluekuja> per night
[19:54] <bluekuja> it's a huge book
[19:54] <bluekuja> ^^
[19:54] <Ubulette> what's your goal ? be a python guru and work for canonical ? :)
[19:55] <bluekuja> lol
[19:55] <bluekuja> I love python language and would start to develop my own application
[19:55] <bluekuja> plus tons of packages are not python-related
[19:55] <bluekuja> so having a good base of python will help me
[19:56] <Ubulette> oh, ok. good luck then :)
[19:56] <bluekuja> *are
[19:56] <bluekuja> (why I added that "the"?)
[19:56] <Ubulette> (so far, i haven't been convinced by python at all)
[19:57] <bluekuja> why?
[19:58] <bluekuja> Ubulette, also on evening I get pretty tired, usually with headaches
[19:58] <bluekuja> cause crash with motorbike
[19:58] <bluekuja> it keeps stressing my mind
[19:58] <bluekuja> but that's normal
[19:59] <Ubulette> oh, take some rest then
[19:59] <bluekuja> yes, I hope to get a clear mind again
[19:59] <bluekuja> but It will take time
[20:00] <bluekuja> ok, fine, cu tomorrow
[20:00] <bluekuja> take care
[20:19] <gnomefreak> bluekuja: ty im gone for the day as well
[20:19] <gnomefreak> have a good night
[20:20] <Ubulette> gnomefreak, what was your question this morning for sm2 ?
[20:20] <gnomefreak> i dont remember
[20:20] <gnomefreak> sorry
 Ubulette: how is the new addon "installer" or download manager whatever its called
[20:21] <gnomefreak> ah yes
[20:21] <gnomefreak> the tools>addons> install
[20:21] <gnomefreak> Ubulette: it should be totally differnet than 1.1.x series
[20:21] <gnomefreak> and should work :)
[20:22] <Ubulette> same as ff3
[20:22] <gnomefreak> good its fixed than
[20:23] <gnomefreak> Ubulette: when is 2.0 ready to build for personal use?
[20:23] <Ubulette> http://www.sofaraway.org/ubuntu/tmp/SeaMonkey2-Add-ons.png
[20:24] <Ubulette> soon
[21:44] <Ubulette> gnomefreak, it's usable now
[22:50] <Ubulette> gnomefreak, ppa is on sync, sm2 is building on both arch
[23:25]  * gnomefreak building it atm
[23:26] <gnomefreak> or not
[23:27] <gnomefreak> not sure why fails but i will
[23:27] <gnomefreak> bzr: ERROR: Unprintable exception DebianError: dict={'_preformatted_string': None}, fmt='A Debian packaging error occurred: %(message)s', error=KeyError('message',)
[23:29] <Ubulette> bad dir
[23:29] <Ubulette> what are you building ?
[23:29] <gnomefreak> todays seamonkey build
[23:29] <gnomefreak> maybe renaming dir?
[23:29] <Ubulette> you mean, from my branch ?
[23:30] <gnomefreak> your branch todays tarball
[23:30] <Ubulette> stop
[23:30] <Ubulette> it's not uptodate
[23:30] <gnomefreak> that shouldnt give me that error
[23:30] <gnomefreak> that error is mainly when in wrong dir trying to build
[23:31] <gnomefreak> that much i remember i didnt think renaming dir would cause this though
[23:31] <gnomefreak> and i didnt rename it it seems
[23:32] <Ubulette> pushed
[23:32] <gnomefreak> its MT branch
[23:33] <gnomefreak> is it MT branch you pushed to?
[23:37] <Ubulette> no, mine
[23:37] <Ubulette> well, it's the same
[23:37] <Ubulette> i've subscribed mt to my branch
[23:37] <Ubulette> #119
[23:38] <Ubulette> hm, no, i'm author but i pushed in mt tree
[23:38] <Ubulette> doesn't matter
[23:38] <Ubulette> ppa is done for hardy
[23:38] <gnomefreak> k
[23:40] <Ubulette> building for gutsy now
[23:53] <Ubulette> gnomefreak, does it work for you ?
[23:57] <gnomefreak> Ubulette: i guess todays tarball cant be used
[23:57] <gnomefreak> configure: error: system NSPR does not support PR_STATIC_ASSERT
[23:59] <Ubulette> you just need a better nspr
[23:59] <Ubulette> ie a 4.7.*, not 4.6