Bug 153098 - rhnpush --new_cache should be --new-cache
rhnpush --new_cache should be --new-cache
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Backend (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: John Wregglesworth
Max Spevack
Depends On:
Blocks: 147875
  Show dependency treegraph
Reported: 2005-04-01 10:34 EST by John Wregglesworth
Modified: 2007-04-18 13:22 EDT (History)
2 users (show)

See Also:
Fixed In Version: RHN 4.0.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-31 22:22:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description John Wregglesworth 2005-04-01 10:34:53 EST
Description of problem: One of the options for rhnpush is --new_cache, but it
should be named --new-cache because _'s in options are annoying. This should be
an easy, one line change.
Comment 1 John Wregglesworth 2005-05-09 16:50:06 EDT
Test Plan:

o Use rhnpush to upload a package into a channel while without using the
--new-cache option. This will cause rhnpush to prompt you for your username and
password whick will be cached so you won't have to enter them the next time you
run rhnpush.

o Use rhnpush to upload a package into a channel again, still without
--new-cache.  As long as the cache hasn't expired (which takes 5 minutes by
default) you shouldn't be prompted for your username and password.

o Run rhnpush a third time, this time WITH --new-cache. This time you should be
prompted for your username and password because you included --new-cache.

Comment 2 Max Spevack 2005-08-03 16:57:03 EDT

Note You need to log in before you can comment on or make changes to this bug.