Hi Teodor, In just four weeks, I'm leaving on vacation for ten weeks. That being the case, I'm not sure I want to push vuze 3.1.1.0 into the archive in time for etch, since I won't be around to help with bugs. On the plus side, azureus 3.0.5.0 already includes a dummy package named vuze that depends on azureus as well as the necessary packages for the web browser that vuze embeds. So, if someone running etch installs the package 'vuze', they should get what they expect. On the downside, this means I can't just package vuze 3.1.1.0 as a new package with a new name and upload it, because it would conflict with the vuze package in azureus 3.0.5.0. I just downloaded vuze 3.1.1.0 and I'll see if it builds and runs without too much trouble.
Cheers, Shaun On Mon, Jun 23, 2008 at 6:08 AM, Teodor <[EMAIL PROTECTED]> wrote: > Hi, > > One week ago a new major release (minor version number) of azureus was > announced [1]. From this release the upstream has decided to change > the name from 'azureus' to 'vuze'. > > What can be done to have this change in time for lenny? Probably a new > source package name 'vuze' and an binary dummy package for azureus -> > vuze transition. > In fact this is not the problem, but what do you now about the > packaging of openjdk? From what I've read on the BTS, depending on > openjdk being in lenny or not the implication will be for azureus/vuze > too. Do you have any ideea why is taking so long to have openjdk in > Debian? > > Thanks > > [1] http://azureus.sourceforge.net/ > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
