[02:55] <bobby> Why isn't there a Public Key for the Maverick 3.7a6pre daily PPA? It won't let me update my system, because there isn't a Public Key, and it isn't authenticated on Maverick
[02:56] <ddecator> there isn't a key?
[02:56] <bobby> Nope
[02:56] <ddecator> should be this: http://keyserver.ubuntu.com:11371/pks/lookup?search=0xB34505EA326FEAEA07E3618DEF4186FE247510BE&op=index
[02:56] <bobby> Nope
[02:56] <bobby> I used a terminal to update
[02:57] <bobby> Here, this is what I get in Update Manager
[02:57] <bobby> W:GPG error: http://ppa.launchpad.net maverick Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY EF4186FE247510BE, W:Failed to fetch http://linux.dropbox.com/ubuntu/dists/maverick/main/binary-amd64/Packages.gz  404  Not Found
[02:57] <bobby> , E:Some index files failed to download, they have been ignored, or old ones used instead.
[02:57] <ddecator> did you use a terminal to add the ppa, or did you do it manually?
[02:57] <bobby> manually
[02:57] <bobby> Upgraded from Lucid, worked in Lucid
[02:57] <bobby> Removed and then re added the PPA, still nothing
[02:58] <ddecator> is the key still shown by the software sources?
[02:58] <bobby> Nothing comes up, it is just the PPA, so I'm not really sure
[02:58] <ddecator> it should be under "Authentication"
[02:59] <bobby> Nope, it isn't there...
[02:59] <ddecator> ok, then go here: http://keyserver.ubuntu.com:11371/pks/lookup?op=get&search=0xEF4186FE247510BE
[02:59] <bobby> And just add that key?
[02:59] <ddecator> select the text, create a new text document somewhere on your comp, paste the text into the file, save, then import it in the Software Sources :)
[03:00] <ddecator> then it should work
[03:00] <bobby> The selected file may not be a GPG key file or it might be corrupt.
[03:00] <bobby> That is the error importing selected file
[03:01] <ddecator> alright, since you're on lucid, this will be easier. remove the PPA, then go to a terminal and run 'sudo add-apt-repository ppa:ubuntu-mozilla-daily/ppa'
[03:02] <bobby> I'm on Maverick
[03:02] <ddecator> well as long as you're on something on karmic or more recent
[03:02] <ddecator> that'll add the ppa and automatically get the key
[03:02] <bobby> Okay
[03:03] <bobby> Wait, after removing it, I get this:
[03:03] <bobby> Failed to fetch http://linux.dropbox.com/ubuntu/dists/maverick/main/binary-amd64/Packages.gz  404  Not Found
[03:03] <bobby> Some index files failed to download, they have been ignored, or old ones used instead.
[03:03] <ddecator> why is it trying to pull something from dropbox..
[03:03] <bobby> I have the Dropbox PPA installed too
[03:03] <bobby> Something messed up with the Sources manager?
[03:04] <ddecator> do you have the key added for the dropbox ppa?
[03:04] <bobby> No, now it isn't there... WTF?
[03:04] <ddecator> strange...
[03:04] <bobby> Wait, I opened it back up, now it is there again...
[03:05] <ddecator> the key is?
[03:05] <bobby> For Dropbox yeah
[03:05] <bobby> Weird...
[03:05] <ddecator> haha, weird. you can try importing the key for the mozilla daily ppa if you want, but running the command is usually easier
[03:06] <bobby> Yeah, I just did the command, lets see
[03:06] <bobby> Okay, it is there, lets update
[03:06] <bobby> Update manager gives me this now:
[03:06] <bobby> W:Failed to fetch http://linux.dropbox.com/ubuntu/dists/maverick/main/binary-amd64/Packages.gz  404  Not Found
[03:06] <bobby> , E:Some index files failed to download, they have been ignored, or old ones used instead.
[03:07] <bobby> Is it the dropbox repos?
[03:07] <ddecator> might be..
[03:07] <bobby> Not supporting Maverick?
[03:07] <bobby> Let me remove the dropbox PPA and key
[03:07] <ddecator> or they might be down atm
[03:07] <bobby> No, because I got the Lucid PPA and Key from the dropbox site
[03:07] <bobby> WAit...
[03:07] <bobby> It is the dropbox MAVERICK PPA
[03:07] <bobby> I don't think dropbox officially supports Maverick yet
[03:08] <bobby> I think I have to use the Lucid PPA, because when a source is added, it automatically changes to a Maverick key
[03:08] <bobby> What happened when I upgraded
[03:08] <ddecator> seems like they'd have it working in maverick..
[03:09] <bobby> Well, I thought that too
[03:09] <ddecator> it could still be their server being down, i've run into that before with other PPAs
[03:09] <bobby> But there IS NO MAVERICK PPA for Dropbox, and when added to the sources, it automatically changes to a Dropbox repository
[03:09] <ddecator> strange..
[03:09] <bobby> No, because I could get the Lucid repository
[03:10] <bobby> How can I remove dropbox?
[03:10] <bobby> The actual program?
[03:10] <bobby> I installed it using the .deb package from the Dropbox website
[03:10] <ddecator> you can find it in synaptic, or it may show up in the software center under installed software
[03:10] <bobby> No, it wasn't in Synaptic
[03:10] <bobby> I'll check the SC
[03:11] <bobby> Okay, got rid of dropbox, lets try and re-install it
[03:12] <bobby> Actually, let me reboot first, so it doesn't startup, brb
[03:14] <bobby> Okay, lets install dropbox again
[03:15] <ddecator> if there's a ppa, then can't you install from the ppa instead of the deb?
[03:16] <bobby> I r a genius
[03:16] <bobby> And, I couldn't find the PPA btw
[03:16] <bobby> All I did, was changide the dropbox PPA from Maverick to Luc
[03:17] <bobby> Lucid
[03:17] <ddecator> well, if it works
[03:17] <bobby> Well, I can't tell
[03:18] <bobby> The update manager is downloading 0 out of 0 bits, which means, I don't know if it is actually checking any repos for updates
[03:18] <bobby> Okay, because there isn't anything to update
[03:18] <bobby> sudo apt-get update
[03:18] <bobby> doesn't bring up any updates
[03:18] <bobby> BEAST
[03:18] <bobby> I love FOSS :)
[03:19] <bobby> Thanks for your help :)
[03:20] <bobby> Oh yeah, anyone know how the new JS engine is coming along?
[03:21] <ddecator> for FF?
[03:21] <bobby> Yeah
[03:22] <bobby> I haven't noticed a difference in the 3.7a6pre's engine over any previous ones
[03:23] <bobby> Takes a little while to load, but it runs pretty well, I'm still looking forward to the updated engine
[03:24] <ddecator> it probably won't be available for a while yet. the version should switch to 4.0 fairly soon, i'd expect them to allow testing of the engine in probably a month or so? that's just my guess
[03:25] <bobby> Yeah, hopefully in a few weeks, I think I read that they are changing to 4.0 when the updated JS engine is ready for beta
[03:25] <bobby> GTG, thanks for your help, see ya
[03:47] <ddecator> hey micahg
[03:48] <micahg> hi ddecator
[03:48] <ddecator> micahg: any chance you'll have time tonight to help me figure out how to fix the FF 3.7 patch?
[04:00] <micahg> ddecator: sorry, pidgin memory leak
[04:01] <micahg> actually, it's a kernel issue that'll be fixed in Maverick
[04:03] <ddecator> micahg: np
[04:05] <micahg> ddecator: ff37 should be similar to what you do w/songbird except you can use the .tar.gz from the daily PPA
[04:07] <micahg> ddecator: just saw your mail
[04:07] <ddecator> micahg: i was doing the same thing i had to do with sb, but for whatever reason whenever i tried to force the ubuntu_bookmarks patch to apply, it kept trying to force a different patch to apply, and i couldn't figure out why (although it was really late, so i might have been doing something wrong :p)
[04:07] <micahg> ddecator: so, quilt push -f, tries to push another patch even when it stops before on ubuntu_bookmarks?
[04:07] <ddecator> micahg: yup, firefox-profile patch or something
[04:08]  * micahg looks
[04:08] <micahg> ddecator: which tarball are you using?
[04:08] <ddecator> micahg: i used get-orig-source
[04:08] <micahg> ddecator: k, then you might have a new patch to fix as well as the old issue
[04:09] <ddecator> micahg: the patch it was trying to apply worked when i tried to build, but then it would fail when quilt tried to force it (i'm guessing because it was already applied)
[04:10] <micahg> ddecator: k, do you have a patches dir in build-tree/mozilla?
[04:10] <ddecator> micahg: let me check..
[04:10] <ddecator> micahg: no
[04:11] <micahg> ddecator: ln -s ../../debian/patches .
[04:11] <micahg> then try quilt pop -a
[04:11] <micahg> then quilt push -a
[04:11] <micahg> and see where it stops
[04:13] <ddecator> File series fully applied, ends at patch ubuntu_codes_amazon.patch
[04:13] <micahg> so maybe it's not broke anymore?
[04:13] <micahg> ddecator: try with a fresh build
[04:13] <ddecator> (from build-tree/mozilla)
[04:13] <ddecator> micahg: k
[04:14] <ddecator> should i be doing this from the firefox-<blah> dir or the mozilla dir?
[04:14] <micahg> ddecator: start from the firefox-3.7 dir with debuild -b
[04:14] <ddecator> micahg: k
[04:14] <micahg> ddecator: then when it fails, make the symlink in build-tree/mozilla and fix
[04:15] <ddecator> micahg: ok, i'll give it a try
[04:15] <micahg> ddecator: k, if you get it fixed in the next 10 minutes, I'll try to merge it quickly :)
[04:15] <ddecator> micahg: sounds good :)
[04:15] <micahg> ddecator: don't worry, we'll get it fixed for tomorrow
[04:15] <ddecator> micahg: haha, ok
[04:16] <ddecator> micahg: ok, ubuntu_bookmarks.patch failed, so create the symlink then use quilt push -f in the mozilla dir?
[04:18] <micahg> ddecator: right
[04:18] <ddecator> micahg: so doing that causes the series to fully apply..
[04:18] <micahg> ddecator: that's weird
[04:19]  * micahg pulls down last nights tarball
[04:19] <ddecator> sorry i know it's getting late, but i want to figure this out so i can start helping with the dailies :p
[04:20] <micahg> ddecator: that's ok, I'd like to get you helping too :)
[04:20]  * micahg can then work on other stuff :)
[04:20] <ddecator> very true, haha
[04:24] <micahg> ddecator: wfm
[04:24] <ddecator> micahg: odd...let me try one more time
[04:31] <ddecator> micahg: didn't work again, i wonder if it's how i have quilt setup...here's what i'm doing: http://paste.ubuntu.com/452297/
[04:32] <micahg> ddecator: idk
[04:33] <ddecator> micahg: this is what's in my .quiltrc file (doesn't seem like it should cause any issues) http://paste.ubuntu.com/452298/
[04:33] <ddecator> micahg: the branch is firefox-3.7.head.daily right?
[04:33] <micahg> ddecator: ah, you might already have QUILT_PATCHES then...
[04:34] <micahg> ddecator: no, maybe that's your issue
[04:34] <micahg> firefox-3.7.head
[04:35] <ddecator> micahg: ah, thanks, i didn't see that on lp, i'll pull that and try it
[04:36] <micahg> ddecator: lp:firefox
[04:36] <ddecator> micahg: that's what i need to branch?
[04:37] <micahg> ddecator: it's firefox-3.7.head :)
[04:37] <ddecator> oh :)
[04:37] <ddecator> alright, i'm getting it now, i'll go through everything again afterward
[04:41] <micahg> ddecator: I try to keep lp:firefox as trunk
[04:41] <ddecator> micahg: good to know :)
[04:41]  * ddecator hopes this works
[04:41] <ddecator> i was getting frustrated last night, haha
[04:59] <ddecator> micahg: i'm starting to hate my computer
[05:01] <ddecator> QUILT_PATCHES does point to the debian/patches dir..
[05:01] <micahg> ddecator: k, so you should just be able to quilt push -f in build-tree-mozilla
[05:02] <ddecator> micahg: alright, let me try a sec
[05:06] <ddecator> micahg: still says it fully applied...
[05:07] <ddecator> but that patch definitely didn't apply...
[05:11] <micahg> ddecator: where's your .pc dir?
[05:13] <ddecator> micahg: where should it be?
[05:14] <micahg> ddecator: in build-tree/mozilla for FF/TB
[05:14] <ddecator> micahg: yup, it's there
[05:15] <ddecator> the ubuntu_bookmarks patch isn't in there..
[05:15] <micahg> ddecator: that means it didn't apply
[05:15] <micahg> ddecator: is it in patches?
[05:15] <ddecator> micahg: yup
[05:20] <ddecator> i'm confused..
[05:20]  * micahg is too
[05:23] <ddecator> lets try...
[05:25] <ddecator> "No patches in series" wtf..
[05:25] <micahg> ddecator: ah, so you do need the link
[05:25] <micahg> ddecator: so make the symlink and try quilt pop -a
[05:26] <ddecator> micahg: doesn't make a difference. i made the link and it still doesn't see the series file..
[05:26] <micahg> ddecator: weird
[05:27] <micahg> ddecator: try moving your .quiltrc file out of the way
[05:27] <ddecator> micahg: k
[05:27] <micahg> ddecator: never worked right for me, so I gave up on it
[05:28] <ddecator> micahg: ok, so i'll have to make the symlink then for sure, right?
[05:28] <micahg> ddecator: yep
[05:28] <ddecator> micahg: k
[05:32] <ddecator> micahg: ...that was it
[05:32] <micahg> ddecator: :) I had the same problem
[05:33] <ddecator> micahg: so did you already fix the patch, or should i fix it for practice and push to lp and request a merge? :)
[05:34] <micahg> ddecator: go for it
[05:34] <micahg> ddecator: BTW, I find it easier with the bookmarks patch to see if something around the code changed that's easily editable and edit the patch manually and try to reapply
[05:34] <micahg> ddecator: only because some of the lines are >500 char
[05:35] <ddecator> micahg: yah i saw that, wasn't really sure the best way to approach it. i'll take a look, thanks
[05:52] <ddecator> micahg: AHA! after a bit of trial and error, i got it fixed. i'll make sure it fully builds before i push to lp :)
[05:54] <micahg> ddecator: k, that one only takes a few minutes
[05:54] <ddecator> micahg: yup, just finished :)
[06:01] <ddecator> micahg: ok, i'm pushing now, i'll request the merge in a few minutes. let me know if the formatting is wrong at all
[06:02] <micahg> ddecator: k, thanks
[06:04] <ddecator> heh, i changed the format of the "new upstream snapshot" a bit from what i do with sb, not sure if that really matters
[06:05] <ddecator> micahg: merge requested :)
[06:09] <micahg> ddecator: k, so here's the thing, we don't add a new changelog entry for each daily fix, so, just modify the current version in the changelog for the first commit, take a look at some previous commits for the commit entry, then, the second commit, you add your name to the existing entry with what you did, see other commits for formatting
[06:10] <ddecator> micahg: ah, ok, i kind of wondered about that. i'll do that now
[06:11] <micahg> ddecator: thanks
[06:13] <ddecator> micahg: should i still do one commit for the new snapshot and then a second commit for the fix, or should i just change the version of the package in the changelog, then add my fix and just commit the fix?
[06:13] <ddecator> micahg: looks like you do a commit with each update to the package version
[06:13] <ddecator> or revision*
[06:14] <ddecator> (i definitely didn't do this with songbird...)
[06:14] <micahg> ddecator: one commit to show the new version ,then one commit for each change
[06:14] <ddecator> micahg: k
[06:14] <micahg> ddecator: with songbird, we just need one new version commit, then one for each change (not file)
[06:15] <ddecator> micahg: so you want me to re-do the changelog for songbird so all of the changes are under the one entry?
[06:17] <micahg> ddecator: yes, so with songbird, you just need a changelog entry if you're adding a feature to the build, since it's not released yet, when there's a version in archive, then you need and entry for each packaging change
[06:17] <ddecator> micahg: so i don't need to add changelog entries for the build fixes?
[06:19] <micahg> ddecator: no, but you do need bzr commit entries
[06:20] <micahg> ddecator: it took me a while to get this down as well
[06:20] <ddecator> micahg: right. so should i just change the changelog or should i start over and re-commit the changes i made? (btw, i just re-pushed the firefox fix)
[06:23] <ddecator> except it didn't push...
[06:23] <micahg> ddecator: well, you can mv that dir and rebranch, then pull the changes in 1 by 1 and commit them with the proper messages
[06:23] <ddecator> micahg: ok, i'll work on that after i get firefox figured out
[06:24] <micahg> ddecator: thanks
[06:25] <ddecator> it's giving me trouble because the branches diverged..
[06:25] <micahg> ddecator: if it's yours, just push --overwrite
[06:26] <ddecator> i thought there was a way to do that, but i couldn't remember the flag. thanks :)
[06:26] <micahg> ddecator: bzr help push :)
[06:28] <ddecator> micahg: ok, it updated. how does it look?
[06:30] <micahg> ddecator: almost got it :) 2 things...1.  commit message should be 3.7 a6 not 3.7~a6, 2.  for the first commit, make sure to pass debian/changelog to bzr commit so that it only commits the changelog file
[06:31] <ddecator> micahg: ok. how do i have it just commit that?
[06:31] <micahg> ddecator: bzr commit debian/changelog
[06:31] <ddecator> micahg: simple enough. here goes try #3 :)
[06:31] <micahg> ddecator: I don't remember how many times I had to redo the TB3 import
[06:33] <ddecator> micahg: is it ok for me to have "snapshot:" or should i remove the colon?
[06:34] <micahg> ddecator: I don't think you need the colon
[06:34] <ddecator> micahg: k
[06:38] <ddecator> alright, let's try this again
[06:41] <ddecator> micahg: ok, it updated
[06:42] <micahg> ddecator: looks great
[06:42] <ddecator> micahg: i missed a space in the commit :p
[06:43] <micahg> ddecator: in the New upstream snapshot?
[06:43] <ddecator> micahg: yup. does that matter?
[06:43] <micahg> ddecator: I think it's ok this time
[06:44] <ddecator> micahg: ok, i'll make sure to watch that next time, haha, i swear i hit space...
[06:44] <ddecator> micahg: ok, so for songbird. just make one addition to the changelog for the new snapshot, then just do commits for all of the changes?
[06:45] <micahg> ddecator: although I wonder why the space is showing up different
[06:45] <ddecator> micahg: hm?
[06:45] <micahg> ddecator: nno, just modify the version in teh changelog
[06:45] <ddecator> micahg: ok, and then just commits for the changes...i'll work on that next
[06:45] <micahg> ddecator: yep
[06:46]  * ddecator is learning :)
[06:48] <micahg> ddecator: ah, they removed a space from that file, that's the diff
[06:49] <ddecator> micahg: oh, gotcha. i couldn't see a difference so i copy pasted the part before and after then respaced everything. a space might have gotten left out or added from that..
[06:50] <ddecator> micahg: should i pass debian/changelog again, or was that just because i had updated the patch and that shouldn't have been in the commit?
[06:50] <micahg> ddecator: no, in the patch file
[06:51] <ddecator> micahg: i can fix the space if you want :p
[06:51]  * micahg goes to check upstream file
[06:51] <ddecator> i think i changed it on accident..
[06:52] <micahg> ddecator: no, it's correct
[06:52] <ddecator> :)
[06:53] <ddecator> micahg: so do i need to pass debian/changelog again? (i'm guessing not)
[06:53] <micahg> ddecator: no
[06:54] <ddecator> micahg: ok, thanks
[06:55] <micahg> ddecator: k, I pushed it up
[06:55] <ddecator> micahg: and final question (for now). should i do the commit in the style you use for firefox, or the style fabien was using?
[06:55] <ddecator> micahg: thanks :)
[06:55] <micahg> ddecator: they should be the same
[06:55] <ddecator> micahg: k
[06:55] <micahg> ddecator: please tell me if I'm diverging
[06:56] <ddecator> micahg: well for songbird fabien was doing "* New upstream snapshot: 2.0.0~a SVN <blah>" which is how i was doing it
[06:56]  * micahg goes to check other commits
[06:57] <ddecator> well it was 1.4.0 for him, but that format
[06:57] <micahg> ddecator: I think he's changed styles since then :-/
[06:57] <micahg> ddecator: it's merged :)
[06:57] <ddecator> micahg: haha, so should i go with that, or the one you are using now?
[06:57] <ddecator> micahg: thanks :D
[06:58] <micahg> ddecator: thanks you
[06:58] <micahg> ddecator: use the current one
[06:58] <ddecator> micahg: ok
[06:59] <ddecator> micahg: the tarball doesn't say what alpha it is, it just says '2.0.0~a~svn<blah>' so should i do "2.0.0 a" or "2.0.0 a1"?
[06:59] <ddecator> it's nit-picky, but apparently i need to be :p
[07:00] <micahg> ddecator: 1st one
[07:00] <ddecator> micahg: alright, thanks. now i'll get started :p
[07:14] <nikolam> hi micahg, what could we/I do about debugging that seamonkey-closing bug, etc. Could it be upstream problem but not related to packaging?
[07:14] <micahg> nikolam: most likely due to the cairo changes in lucid, I'm supposed to prepare a patch for upstream, I just haven't gotten around to ityet
[07:16] <nikolam> so you think is distribution-related and that non-packaged variont of SM downloaded from Mozilla directly, most likely would not have such behavior?
[07:16] <micahg> nikolam: yes, it's because I used system cairo
[07:17] <nikolam> Aha. so it would require upstream changes to fix local behaviour..
[07:18] <micahg> nikolam: well, it's patched in xulrunner-1.9.2, but not in xulrunner-1.9.1 which Seamonkey 2 is based on
[07:19] <nikolam> hm. I have xulrunner 1.9.2 on this lucid now
[07:20] <micahg> nikolam: yes, but Seamonkey 2.0 has its own copy of xulrunner
[07:20] <nikolam> so as i understand, it would have to wait 2.0.5 etc, or not?
[07:21] <nikolam> aha. or patching .1 with needed changes, I see.
[07:22] <micahg> nikolam: yeah, 2.0.5 is in the security PPA, but I don't have the fix yet, if I get it done before 2.0.5/FF3.5.10 is released, I'll have it reuploaded, otherwise, I'll need to SRU or wait until 2.0.6 (I'd be more inclined to SRU)
[07:23] <ddecator> micahg: ok, the songbird merge updated. i'm sure i need to fix a few things, just let me know what when you get a chance. (i'm not sure what's going on with the diff for the one patch, it has the contents and applies when i try to build, i think the diff shows everything being removed and then re-added but it gets cut-off?)
[07:23] <micahg> ddecator: I'll take a quick look, but I won't merge until morning as I'm afraid to do it when this tired
[07:24] <ddecator> micahg: no problem
[07:35] <ddecator> wait..
[07:36] <ddecator> what the heck, with that patch i just made sure xulrunner was replaced with xulrunner-1.9.2, why is that huge block missing..
[07:36] <micahg> ddecator: was it not committed originally?
[07:37] <ddecator> micahg: i'm not sure, i'm checking the patch that's in the untouched branch to see if a block is really missing
[07:38] <ddecator> yah, a huge chunk is missing, what the heck..
[07:38] <ddecator> let me see if i can redo the change
[07:41] <ddecator> micahg: i'll fix that, make sure it still applies, then re-push so you can check tomorrow
[07:41] <micahg> ddecator: k
[08:34] <ddecator> micahg: should be good now
[08:35] <micahg> ddecator: k, thanks
[08:41] <ddecator> dang it, there's still one file it doesn't take care of. it'll be ready in a little bit...
[08:50] <ddecator> there...
[17:45] <gnomefreak> ddecator: are you around?
[17:45] <gnomefreak> im just guessing here but Songbird FTBFS again?
[17:56] <micahg> gnomefreak: he's working on it :)
[17:57] <gnomefreak> micahg: thanks just checking. i really really wan tto play with it
[17:57] <micahg> gnomefreak: he fixed FF37 last night
[17:58] <gnomefreak> oh yeah i forgot that was old/broken
[17:59] <gnomefreak> i took a quick look at gtkpod but it didnt look like it was a easy learning app. but when i get more time i will play with that as well
[18:11] <gnomefreak> i need a link
[18:11] <micahg> gnomefreak: to?
[18:12] <gnomefreak> micahg: any flash video. testing chromium as default browser and flash
[18:12] <fta> micahg, fixed the dh7 thingy in my dashboard: http://people.ubuntu.com/~fta/ppa-dashboard/ubuntu-mozilla-daily--ppa.html
[18:13] <micahg> gnomefreak: http://www.youtube.com/watch?v=g4kT-K9eJ2k&feature=fvhl
[18:13] <gnomefreak> thanks
[18:13] <fta> micahg, dh7 is indeed in hardy, but in backports, so it's not really usable
[18:13] <gnomefreak> youtube wasnt being helpful but im trying your link now
[18:13] <micahg> fta: yep, I was saying that we probably don't need it in the PPA
[18:13] <micahg> gnomefreak: with Chromium, you can use HTML5 w/Youtube
[18:14] <gnomefreak> ah
[18:14] <gnomefreak> well this video works now test java on thier site :)
[18:16] <fta> micahg, just deleted ff3.5 from umd
[18:16] <gnomefreak> http://java.com/en/download/help/testvm.xml  fails in Chromium
[18:17] <gnomefreak> so i have to guess either java needs to be enabled or the versions i have dont work
[18:17] <micahg> fta: cool, can you delete thunderbird-3.0 please?
[18:17] <fta> micahg, done
[18:18] <micahg> fta: thanks
[18:21] <gnomefreak> fta: micahg ok what am i missing with java+chromium?
[18:22] <micahg> gnomefreak: I'm guessing the Java part ;)
[18:22] <micahg> gnomefreak: which java?
[18:22] <gnomefreak> yeah i was thinking that but i dont see anyway to enable it or even if it works with the versions im using
[18:22] <micahg> gnomefreak: which java?
[18:23] <fta> gnomefreak, i use sun-java6-plugin and it's fine. but iirc, there's a problem with openjdk-6
[18:23] <gnomefreak> IIRC i am using free version but i do believe i have both installed. im going to play in update-alternatives to see what i have
[18:23] <micahg> bug 529242
[18:23] <ubot2> Launchpad bug 529242 in chromium-browser (Mandriva) (and 3 other projects) "chromium doesn't recognize icedtea6-plugin (affects: 13) (dups: 1) (heat: 99)" [Unknown,Won't fix] https://launchpad.net/bugs/529242
[18:24] <gnomefreak> policy sun-java6-plugin
[18:24] <gnomefreak> W: Unable to locate package sun-java6-plugin
[18:24] <micahg> gnomefreak: partner?
[18:24] <gnomefreak> its wont fix
[18:24] <micahg> gnomefreak: for mandriva :)
[18:24] <gnomefreak> micahg: i thought i had it enabled but cheaking
[18:24] <fta> lucid/partner
[18:24] <gnomefreak> micahg: ah
[18:25] <fta> !info sun-java6-plugin
[18:25] <fta> zzZZzz..
[18:25]  * gnomefreak doesnt like mandriva. im on 10.10
[18:25] <ubot2> fta: Package sun-java6-plugin does not exist in lucid
[18:25] <fta> !info sun-java6-plugin partner
[18:25] <ubot2> fta: 'partner' is not a valid distribution: hardy, jaunty, karmic, lucid
[18:25] <fta> pfff
[18:25] <gnomefreak> yep its enabled
[18:26] <micahg> http://pastebin.com/ngXwz51G
[18:28] <fta> remember it's partner/lucid, not maverick
[18:29] <gnomefreak> http://paste.ubuntu.com/452567/
[18:29] <gnomefreak> i am enabling it for lucid
[18:30] <gnomefreak> once updates and my smoke is done
[18:31] <fta> smoking is bad for you
[18:31] <gnomefreak> sometimes :)
[18:31] <fta> and for anyone fwiw
[18:49] <fta> micahg, will hardy get ff3.6?
[18:53] <micahg> fta: yes, it's staged in the mozilla-security PPA
[18:54] <fta> micahg, why is it red in umd then?
[18:55] <micahg> fta: .head won't build, chrisccoulson or I need to modify the patch so that the dailies work, it's the kde patches
[18:55] <fta> oh
[19:21] <gnomefreak> ok set my alias' finally
[19:33] <gnomefreak> i need to find a song that i heard a week or 2 ago and other than "i hate$SOMETHING" in the song i have nothing :(
[19:37] <gnomefreak> i love i dont have to restart Chromium after installing extensions and stuff :)
[19:39] <micahg> gnomefreak: FF4 will have the same capabilities
[19:40] <gnomefreak> micahg: cool
[19:42] <JanC> the new extension famework can be installed in current FF too
[19:43] <JanC> search for the JetPack extension
[19:43] <micahg> JanC: I think the idea is even for non jetpack extensions to not require a restart in 4.0
[19:44] <gnomefreak> what is smtp port other than 25 i was thinking its 465 or something like that?
[19:44] <micahg> gnomefreak: 465 or 587
[19:44] <gnomefreak> micahg: thanks
[19:45] <micahg> gnomefreak: 465 is smtps and 587 is smtps or alternative smtp
[19:45] <JanC> I thought that wasn't possible with all current extensions, but one never knows...  ;)
[19:45] <JanC> 587 is "submission"
[19:46] <gnomefreak> and that was the problem :)
[19:47] <JanC> intended to be used for an smtp-server to "submit" mail to from a mail client (and is using TLS in most cases because of that--you only want authenticated users to use your mailserver to send mail)
[19:49] <gnomefreak> Chromium is broken i think. i set it as default in the system>pref. menu i set as default in update-alternatives and it poped up saying its not default so i clicked the button on the prower that said "set as default" and yet it is still poping up when i open a new session
[19:52] <micahg> gnomefreak: alternative system isn't the main way to set defaults anymore
[19:52] <JanC> there are many ways to set a "default" browser in linux  ;)
[19:53] <gnomefreak> i know but even still it is set everywhere and opens as default but says it isnt default
[19:53] <micahg> gnomefreak: what does xdg-open open?
[19:54] <gnomefreak> nothing
[19:54] <micahg> gnomefreak: xdg-open http://google.com opens nothing?
[19:54] <gnomefreak> i tried just "xdg-open" and i tried with a url but failed to open
[19:55] <JanC> use '' around the URL
[19:55] <gnomefreak> i didnt use the HTTP
[19:56] <gnomefreak> it opened chromium and still has the yellow bar at top saying it is not my default browser and gives me 2 buttons "set as default" and "dont ask me again"
[19:57] <micahg> gnomefreak: that's probably a bug
[19:57] <micahg> fta: ^^^
[19:57] <gnomefreak> it is a bug :)
[19:58] <gnomefreak> il try the dont ask again and see what happens
[19:58] <fta> http://code.google.com/p/chromium/issues/detail?id=45208
[19:59] <ddecator> gnomefreak: i am now
[19:59] <micahg> bug 513133?
[19:59] <ubot2> Launchpad bug 513133 in chromium-browser (Ubuntu) (and 1 other project) "When chromium is the only browser installed, i'm still asked to make it the default (affects: 2) (dups: 1) (heat: 38)" [Undecided,New] https://launchpad.net/bugs/513133
[19:59] <ddecator> gnomefreak: i have it building, now it's just a matter of getting the commits and everything right so it can be merged :)
[19:59] <fta> yep, it's xdg something
[19:59] <gnomefreak> ddecator: :) micahg answered
[19:59] <ddecator> gnomefreak: waiting on him to review :p
[20:00] <gnomefreak> ddecator: i was looking for your commits thinking that you did more than 1 and i was going to see what i could do but now the weekend is hectic for me
[20:03] <gnomefreak> fta: how do i get the updates? i click on the star but how does it know my email?
[20:03] <gnomefreak> i am signed in for google
[20:14] <gnomefreak> they havent finished tb3 tb31 and they are already talking about tb32
[20:15] <micahg> gnomefreak: what do you mean?
[20:16] <gnomefreak> mozilla is talking about code name (not sure what else i havent finished reading) still have alot of updates for 3.0 that should be comming. tb31 has yet been released it might be beta i dont recall and now 32 is starting
[20:16] <micahg> gnomefreak: codenames are chosen early on
[20:17] <gnomefreak> i know but still 32 is a long ways away atm what maybe 1 year or so
[20:17] <micahg> gnomefreak: they're trying to get comm-central in shape for an alpha 1 release and they need the codename before
[20:18] <gnomefreak> oh
[20:19] <gnomefreak> ff37 is hitting beta1 soon or has already?
[20:20] <micahg> gnomefreak: soon
[20:21] <ddecator> and will hopefully labeled 4.0 :)
[20:21] <gnomefreak> well there are some blockers atm. i know of one for Windows atm
[20:21]  * gnomefreak wonders
[20:21] <gnomefreak> mozilla 513162
[20:21]  * gnomefreak waits
[20:21] <gnomefreak> and waits
[20:21] <ubot2> Mozilla bug 513162 in Widget: Win32 "[Windows] Drawing in the Title Bar for the New Firefox Theme" [Normal,New] http://bugzilla.mozilla.org/show_bug.cgi?id=513162
[20:22] <gnomefreak> about time you shit
[20:22] <ddecator> ubot2 is hungover
[20:22] <ubot2> Factoid 'is hungover' not found
[20:22] <gnomefreak> ok they fixed server
[20:22] <gnomefreak> i miss the real bot, i am sick of these clones
[20:22] <micahg> gnomefreak: too much load for 1 bot
[20:22] <gnomefreak> cant use any admin commands
[20:22] <ddecator> gnomefreak: it was hit and miss last night when i tried it, didn't catch some of the bugs mentioned (in a diff channel)
[20:23] <gnomefreak> micahg: there are ~6 bots we are using to save ubottu from working in every channel
[20:24] <gnomefreak> if i get time i will beet with the IRCC and talk about this
[20:24] <gnomefreak> @whoami
[20:24] <ubot2> gnomefreak: I don't recognize you.
[20:24] <gnomefreak> see
[20:24] <micahg> @whoami
[20:24] <ubot2> micahg: I don't recognize you.
[20:24] <micahg> gnomefreak: file a bug or complain to the IRC admins
[20:25] <micahg> s/IRC admins/ubuntu-irc
[20:25] <gnomefreak> i am, bug isnt worth it since i have direct access to the council
[20:25] <gnomefreak> ill be back in a few
[20:34] <gnomefreak> ill be gone for a bit i need to get dinner started.