[07:18] <dholbach> good morning
[08:44] <slytherin> persia: FYI ... I have setup debian pbuilder. I will try to forward the jftp patch tonight. I will also join pkg-java mailing list.
[08:45] <persia> slytherin: Excellent.  Some of what we do is Ubuntu-specific, but where are deriving from Debian, it's always best to try to get the change made there.
[08:46] <slytherin> persia: yes. By the way, Vincent Fourmond is already working on getting batik and it's dependency in Debian. xml-commons-external has entered Debian.
[08:46] <persia> Excellent news indeed.
[08:51] <slytherin> persia: if you are administrator of Java Team, can you please auto-subscribe to bugs related to some important packages?
[08:55] <persia> slytherin: I'm not an admin: I just lead the weekly meetings.
[08:55] <slytherin> :-)
[09:33] <persia> Koon: Are you sure Debian bug #413906 matches LP bug #256052?  I'd recommend creating a separate bug, against the tomcat6 source itself.
[09:34] <Koon> hmm
[09:35] <Koon> "ITP: tomcat6 -- servlet container"
[09:35] <persia> My reasoning is that although I agree that the tomcat6 packaging may not have been "complete", that your work is done against the current package, rather than being a complaint about how it was packaged in the first place.
[09:36] <persia> Not an ITP: that specifically means a new source package, but rather as an update to the existing package.
[09:36] <Koon> ah.
[09:38]  * Koon struggles withe the bug history
[09:38] <persia> Heh.  Yeah.
[09:38] <Koon> ah ok, it was filed as tomcat5.5 then reassigned as wnpp
[09:38] <persia> Also, are you still working on that individually?  I notice you remain assigned, and it's not gone to any sponsor queues.
[09:38] <Koon> then closed
[09:39] <persia> Yes, which is the right path for the "Gimme tomcat6" bug.  Your work is something else.
[09:39] <Koon> persia: ok, will file a new bug against tomcat6
[09:40] <persia> Koon: Thanks.  That will probably get the attention of the right people.
[09:40] <persia> Remember that unless we work with Debian to accept changes, we're bound to maintain every byte of variation until the end of days...
[09:41] <Koon> persia: about subscribing universe-sponsors: I was waiting on mathiaz to confirm that every problem he found on the package has been fixed to his likings before pushing it to a sponsor queue (or let him sponsor it) -- and given the size of the update that's why I asked a couple others to have a look as well
[09:42] <Koon> I can push it to the queue now, I just didn't want to rush him
[09:43] <persia> Koon: Personally, I think it's best practice to put everything to the queue as soon as it's ready.  If someone has time to get to it, great.  If not, someone else might have the time.
[09:43] <persia> Anyway, no point subscribing the queue now: if you're done with it, I'll push it.
[09:44] <Koon> persia: so you had time to look at it ?
[09:44] <persia> Koon: Yep.  Looks fairly reasonable.  My main issue is how the bug is triaged, rather than the work itself.
[09:44] <Koon> (do you sleep sometimes ?)
[09:45] <persia> Mind you, I'd probably be more careful if we were in freeze.
[09:45] <persia> Yes, I sleep :p
[11:34] <kaaloo> Koon: hi, slytherin told me yesteday that you are working on a way of working with maven for building packages ?  Also, I just saw your work on tomcat6 on intrepid-changes the webapps are installed as packages with links to their jar dependencies ?
[12:33] <Koon> kaaloo: about maven -- yes, see https://wiki.ubuntu.com/JavaTeam/Specs/MavenSupportSpec for details
[12:34] <Koon> kaaloo: about tomcat6 -- webapps are installed as packages but didn't require any link, the tomcat6 webapps have no specific library depends
[13:45] <acuster> Hey all, is there any status page maintained on where we are with java/eclipse/... ?
[13:50] <slytherin> acuster: There is no specific work going on in regards to eclipse in Ubuntu. You may want to keep watch on debian-java mailing list. As for the other work in Ubuntu, check https://wiki.ubuntu.com/JavaTeam/Roadmap
[13:54] <kaaloo> Koon: thanks for the information !  I'll take a look, see if I can help.
[13:54] <Koon> kaaloo: you're welcome :)
[13:55] <acuster> thanks
[13:59] <slytherin> persia: any idea why there are so many failures on ppc in regards to java related to packages. I think I have found the problem. Need your comment.
[13:59]  * persia wants something to comment upon
[14:01] <slytherin> persia: if you check rules file in java-common, the jvmdir is being set to cacao-6-openjdk. As found from checking the cacao-oj6-jre-headless package file it looks like correct name would be java-6-cacao.
[14:03] <persia> slytherin: If you make that as a local change in the build chroot, can you build them on powerpc?
[14:04] <slytherin> persia: I don't have powerpc machine as of now. I am still waiting for my ibook's power adapter to be repaired. :-(
[14:06] <slytherin> persia: I will log a bug and wait for doko to stumble upon it.
[14:09] <persia> slytherin: That's probably best.  You might also try checking with the powerpc team (and no, I don't know if they have a channel)
[14:15] <slytherin> persia: they have a channel but don't think anyone is interested in java there.
[14:15] <persia> slytherin: But given a test case, they may be willing to try something for you.
[14:16] <slytherin> let me try.
[14:16] <slytherin> persia: in any case the build failures are clearly evident on FTBFS page.
[14:17] <persia> slytherin: Right, but the powerpc FTBFS folk may not understand Java well enough to understand how to address it :)
[14:18] <slytherin> persia: I guess doko will handle it. And he is smart enough. :-D
[14:20] <persia> Oh, certainly that :)
[14:26] <slytherin> persia: filed a bug, should I subscribe only doko or entire java team?
[14:28] <persia> slytherin: i'd subscribe only the Java team.  doko is a member, and will see it.  I suspect he's fairly busy with Debian right now though: you might also add it to the meeting agenda to see if anyone else has thoughts or can test.
[14:28] <slytherin> ok
[14:39] <slytherin> persia: that reminds me, do I need to log a bug for moving jftp to universe?
[14:41] <persia> slytherin: Indeed you do.
[14:41] <slytherin> ok
[14:42] <persia> Well, technically you don't, but as the alternative is finding an archive admin who feels like doing it just then, filing a bug might be easier :)
[14:43] <slytherin> I will see if I can find an archive admin, if not then file a bug.
[14:52] <persia> Archive Admins can be tricky to find :)
[15:16] <LucidFox> slytherin, have you seen that xml-commons-external has been accepted into Debian?
[15:16] <LucidFox> by Fourmond, and it's based on your package
[15:25] <slytherin> LucidFox: yes, saw that yesterday. :-)
[15:26] <slytherin> LucidFox: I had added comments to debian bug for batik update that the version was available in Ubuntu.
[15:26] <LucidFox> ah
[15:27] <slytherin> LucidFox: I didn't expect him to retain the Ubuntu changelog entry. :-D
[15:28] <LucidFox> heh
[15:33] <persia> Vincent tends to be careful about attribution, but can be very helpful.
[15:42] <slytherin> persia: 'careful' as in?
[15:43] <cody-somerville> http://packages.debian.org/changelogs/pool/main/c/catfish/catfish_0.3-2/changelog
[15:44] <persia> slytherin: Tries never to exclude credit where things are borrowed from others.  It's a habit we could all adopt, although I sometimes think he's over-careful.  Were I updating based on your package, I'd have modified the same changelog entry, rather than adding a new onw.
[15:44] <slytherin> :-)
[15:45] <persia> cody-somerville: Good example, although uploaded by a different person.
[15:46] <persia> (although it looks like someone forgot how to use -k in 0.3-0ubuntu2)
[15:47]  * cody-somerville nods.
[15:48] <slytherin> persia: do you have idea how pkg-java SVN works? Upload once you have commited changes to SVN or commit to SVN after updated package has been uploaded?
[15:49] <persia> slytherin: I don't know, but suspect that debian-java@lists.debian.org is the place to ask.
[15:49] <persia> For most teams, it seems that work gets committed to SVN first.
[15:49] <slytherin> hmm, will do.
[15:51] <slytherin> I will send some patches first. So I don't have to justify why I need SVN access.
[15:52] <persia> Heh.  *lots* of patches to the BTS are often a good argument all on their own :)
[15:52] <slytherin> Is patches to BTS good idea? I was planning to send them to pkg-java list.
[15:59] <slytherin> ﻿/me heads home
[16:00] <slytherin> damn pidgin
[16:00]  * slytherin heads home
[16:05]  * persia hopes slythering reads backscroll
[16:05] <persia> The BTS is typically the preferred means by which patches are submitted, reviewed, and discussed.  While this is also email, it allows the set of subscribers to change over time, and keeps a single URL for the entire thread.