aMule Bug Tracker - aMule | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0001618 | aMule | Preferences | public | 2010-07-30 17:01 | 2010-08-07 21:49 |
Reporter | morph | ||||
Assigned To | |||||
Priority | normal | Severity | feature | Reproducibility | always |
Status | closed | Resolution | won't fix | ||
Platform | OS | OS Version | |||
Product Version | 2.2.6 | ||||
Target Version | Fixed in Version | ||||
Fixed in Revision | |||||
Operating System | Any | ||||
Summary | 0001618: Disable NewVersionCheck by Default | ||||
Description | Hello, we receive this bug on the Debian bug tracker: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554623 [^] Indeed it would be nice to ship an amule.conf (actually the one automatically created by amule if it doesn't find one) with NewVersionCheck set to 0. This because in Debian we have other thing to alert people of new packages, and also a new release doesn't always translate in an immediate new Debian package (for several reasons, lack of time, integration issues to fix & so), the way a user expect to install it. F.e. a ./configure option might be interesting to disable this setup, or any other viable way for you to allow us to disable that option by default: users can still reactivate it if they like. Regards, Sandro | ||||
Steps To Reproduce | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2010-07-30 17:01 | morph | New Issue | |||
2010-07-30 17:01 | morph | Operating System | => Any | ||
2010-08-07 21:49 | sturedman | Note Added: 0003470 | |||
2010-08-07 21:49 | sturedman | Status | new => closed | ||
2010-08-07 21:49 | sturedman | Resolution | open => won't fix |
Notes | |||||
|
|||||
|
|