Bug#489445: 'azureus' renamed to 'vuze'.
merge 487512 489445 kthxbye On 7/5/08, Shaun Jackman [EMAIL PROTECTED] wrote: 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. Hi Shaun, I recommend to upload vuze_3.1.1.0 in NEW and request removal on azureus from unstable for the following reasons: * azureus has 3 RC bugs and sooner or latter will be removed from lenny [1]; * vuze_3.0.5.0-1 depends on two packages which are no longer available [2]; Considering that the big blocked for azureus is the upload of 'openjdk' I recommend to not waste time fixing azureus (probably package 3.0.5.2 along with some bug fixes) and go for vuze_3.1.1.0 in lenny (azureus being a dummy package depending on vuze). Thanks for your response. [1] http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=azureusarchive=nopend-exc=pending-fixedpend-exc=fixedpend-exc=donesev-inc=criticalsev-inc=gravesev-inc=seriousrepeatmerged=no [2] http://packages.debian.org/sid/vuze -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489445: 'azureus' renamed to 'vuze'.
Hi Teodor, On Sun, Jul 6, 2008 at 2:30 AM, Teodor [EMAIL PROTECTED] wrote: I recommend to upload vuze_3.1.1.0 in NEW and request removal on azureus from unstable for the following reasons: * azureus has 3 RC bugs and sooner or latter will be removed from lenny [1]; * vuze_3.0.5.0-1 depends on two packages which are no longer available [2]; Considering that the big blocked for azureus is the upload of 'openjdk' I recommend to not waste time fixing azureus (probably package 3.0.5.2 along with some bug fixes) and go for vuze_3.1.1.0 in lenny (azureus being a dummy package depending on vuze). Thanks for your response. [1] http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=azureusarchive=nopend-exc=pending-fixedpend-exc=fixedpend-exc=donesev-inc=criticalsev-inc=gravesev-inc=seriousrepeatmerged=no [2] http://packages.debian.org/sid/vuze Vuze 3.1.1.0 built and run with surprising ease. The source zip finally includes a build script! I'm considering uploading it as azureus 3.1.1.0 rather than changing the package name at this point. Not much has changed in the source code. The jar file, for example, is still named Azureus2.jar. I don't feel that there's much to be gained by renaming the source package to vuze. Cheers, Shaun -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#489445: 'azureus' renamed to 'vuze'.
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]
