on Sat, 24 May 2008 12:18:49 -0700, Shaun Jackman <[EMAIL PROTECTED]> wrote: > In bug #455351 and before that #405997, I was asked to remove > auto-update because it conflicts in purpose with Debian's package > management system. This change had the side effect of creating bugs > #452326, #452321, and now #481011. I'm unsure how to fix these bugs > without once again enabling azupdater.
in this case, the cure is much worse than the problem that it's solving. personally, i don't care that much about updating the core (running 'sid', azureus is reasonably up-to-date...and i don't run it very often anyway). but it is a serious bug that i can't install any of the plugins, like Speed Scheduler or the web interface. I used to use these and other plugins in the previous version of azureus, and they are a huge improvement to azureus. i just assumed that it was a bug that would eventually get fixed until i checked the bug archives again just now (i must have missed the bug reports when i checked earlier this year) (BTW, Speed Scheduler is a particularly useful plugin - it lets me specify how much bandwidth azureus will use at various times of particular days. e.g. minimal bandwidth during the day, a lot late at night or on weekends. Sp.Sch. has very flexible scheduling) having read through 405997, i completely agree with manoj's and your comments. it's the user's choice whether to upgrade or not, and the package should not paternalistically cripple that functionality. at most it should disable updating by default if it is feasible to do that, but it should not remove it entirely. other people complained about there being no indication that it wasn't a debian-approved upgrade. that's a reasonable concern.....but the correct solution there is obvious - change the java code so that it clearly warns the user that: a) the update they are about to install is not the debian packaged version, and has not been through debian's package and review process. also mention that debian's ability to resolve bugs is necessarily limited if the user runs non-packaged azureus updates. b) that it will install in the users ~/.azureus/ directory. the warning should also refer the user to a "README.Debian.Azureus-Update" file in /usr/share/doc/azureus/ that documents this issue, with links to the relevant bug reports, AND provides instructions for removing/disabling an updated azureus binary in ~/.azureus/ it would also be worthwhile modifying the plugin installer dialog to remove the option "Install the plugin for all users" (better yet, disable the option and put in a reminder note that plugins can only be installed for individual users, not for all users). craig -- craig sanders <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
