Description of problem: When you choose a differend location to store the update rpm's and the directory doesn't exists; you'll get the error that /var/spool/up2date could not be found. Version-Release number of selected component (if applicable): up2date-4.1.16-1 How reproducible: always Steps to Reproduce: 1. run up2date-config 2. choose another directory to store the rpm's. Ie: /tmp/up2date (just choose a dir that doesn't exists) + save the config. 3. run up2date Actual results: You'll get the error message: The storage directory /var/spool/up2date could not be found, or was nog accessable. Expected results: It should say that the dir /tmp/up2date (or another directory that you've chosen) could not be found. Additional info:
hmm, indeed. fixed in cvs
The error message is still hardcoded in up2date-4.3.47-5 from FC3.
Fedora Core 1 is maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thanks! NOTE: Fedora Core 1 is reaching the final end of support even by the Legacy project. After Fedora Core 6 Test 2 is released (currently scheduled for July 26th), there will be no more security updates for FC1. Please use these next two weeks to upgrade any remaining FC1 systems to a current release.
Still hardcoded in up2date-4.4.69-25 in RHEL4
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.