Bug 20052 - default vendor field is weird in preferences
default vendor field is weird in preferences
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: gnorpm (Show other bugs)
7.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
Dale Lovelace
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-10-30 14:28 EST by Jeff Johnson
Modified: 2007-04-18 12:29 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-06-05 14:59:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeff Johnson 2000-10-30 14:28:17 EST
Start gnorpm, select preferences -> rpmfind.

Vendor is displayed as "Olivier Fourdan <fourdan@csi.com>" rather than
something sensible.

FWIW, same screen, has the following nit-nots:

1) Download dir should probably be per-system, not per-user. Rationale is
that
only root can install rpm's anyways, so there's little reason to download 
to per-user
directory for future root-only install.

2) no upgrade list should include (at least) kernel, dunno what shlibs is
either.
Comment 1 Alan Cox 2000-12-12 15:43:57 EST
I am unable to duplicate this problem with any official gnorpm release, or
gnorpm cvs. It sounds like a double memory free however so could be yet another
rpmlib bug or something triggered by an obscure cause.
Comment 2 Jeff Johnson 2001-03-05 16:21:41 EST
Again, properly formed bug reports against rpm will get issues resolved.

From gnorpm-0.96-1:

The vendor is now displayed correctly, may have been a problem with
data returned from the URL.

Default for Download dir is still "/root/rpms"

No upgrade list still does not include kernel.
Comment 3 Alexander Larsson 2001-07-25 11:11:12 EDT
I am unable to reproduce this in any version. Marking WORKSFORME.

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