[01:24] Hi [01:24] Any idea about the comment #5 in https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/784604 when is it going to be available in the repos ? [01:24] Ubuntu bug 784604 in sun-java6 "a new java version is available for download" [Undecided,Confirmed] [01:25] Looks like it mostly needs someone to do the work. I'm not sure that many people are interested in sun-java these days. [01:26] ok [01:26] Comment #4 implies there's some messiness involving fonts that needs investigation. [01:26] persia: does it mean people are more interested towards openjdk ? [01:27] Whats the exact difference b/n openjdk and sunjdk [01:27] It seems that way from what I've seen, but last I knew there were some things not yet implemented in openjdk [01:27] The difference is large. It can't easily be expressed on IRC. [01:28] persia: Do you have a writeup ? [01:28] No. [01:28] I don't have access to the dun-java6 source, so I can't run the diff. [01:28] You would need someone at Oracle to do that. [01:28] persia: so whom do i contact for this bug ? [01:29] I suppose one could compare the method lists for all classes made available for each, but that would miss any differences in implementation behaviour. [01:29] Needs someone to volunteer to fix it. I'm not sure contacting folk would help especially. Do you want to fix it? [01:29] sure [01:29] How do i go about ? [01:30] !sru [01:30] Hrm. [01:30] Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates [01:30] OK. So look at that page. [01:30] Because of that procedure, it needs to be fixed first in oneiric, then in natty, then in maverick, then in lucid, and finally in hardy. [01:31] In each case the procedure is the same, so you can likely reuse a lot of the work you do for oneiric when you do the rest. [01:31] First get the source package for the target suite. [01:31] Then download the new update of the binary distribution. [01:32] Compare the licensing, to make sure that it's compatible. [01:32] Insert the new release from Oracle into the source package. [01:32] Build the source package, and test to make sure it works. [01:32] Upload (or if you can't upload, ask for sponsorship). [01:32] persia: sure [01:32] When doing natty, maverick, lucid, and hardy you'll need to additionally work with the sru-verification team. [01:33] Comment #1 implies it's fixed in Debian, so it may be worth looking also there to see precisely what was done. [01:33] persia: you said Build the source package [01:33] If you have questions, ask here. If nobody answers, try #ubuntu-motu (because it's in multiverse) or #ubuntu-devel [01:33] Yep. [01:34] Any documentation [01:34] I generally prefer sbuild. [01:34] `apt-get --no-install-recommends install sbuild ubuntu-dev-tools` [01:34] Then `mk-sbuild oneiric` (or whichever) [01:35] ok [01:35] Then `sbuild -A -d oneiric-${ARCH} ${DSC_FILE}` [01:35] When you change a package, you can generate a new .dsc file with `debuild -S -us -uc` [01:36] Be sure to update the changelog (easiest way to do this is with `dch -i`) after modifying the source, but before generating a new .dsc [01:36] persia: Do you have any wiki page for it [01:36] I would love to do it [01:37] https://wiki.kubuntu.org/PackagingGuide/Recipes/PackageUpdate may be a bit out of date [01:37] persia: Thanks [01:37] Also it recommends pbuilder rather than sbuild (either works: they serve the same function) [01:37] I would start working on it [01:38] persia: you motivated me [01:38] You were already motivated. I'm just providing instructions. Thanks for helping with Ubuntu. [01:38] persia: I would revisit you [01:38] agaib [01:39] again* [01:39] is it ok ? [01:39] My recommendation is just to ask questions generally in channels. Folks who have time will respond. [01:39] If you try to get me, and I'm not around, you may wait for a while, but someone else may be able to help you instantly. [01:39] You can ask for me, I'm just not sure you'll get the fastest or best response that way. [01:40] persia: Thanks a Lot === hannesw_ is now known as hannesw === doko_ is now known as doko