After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 58175 - RFE: remove install button
RFE: remove install button
Status: RESOLVED WONTFIX
Product: gnorpm
Classification: Deprecated
Component: general
0.96
Other Linux
: Normal enhancement
: ---
Assigned To: Malcolm Tredinnick
Malcolm Tredinnick
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2001-07-27 15:44 UTC by Alexander Larsson
Modified: 2012-02-19 16:32 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexander Larsson 2001-07-27 15:44:42 UTC
Note: This bug was moved here from the redhat bugtracker at
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=20058

Start gnorpm, select Install.

The page that is displayed should *not* have an Install button, as Upgrade
is almost always what is needed.

FWIW, here are several other nit-nots

1) If "Expand Tree" is hit immediately, a downrev version of gnorpm is
displayed. That means, when running gnrorpm-0.95.1-5, gnorpm-0.95.1-3
is displayed for reasons beyond my ken.

2) "Select All" after "Add" should not select multiple occurences of
identically
named packages. While filtering multiple identically named packages should
have been implemented in rpmlib many moons ago, rpmlib has *never* behaved
gracefuully when presented with mutiple identical packages as part of the
same
transaction, and support for legacy versions of rpm demands the filtering
in
gnorpm rather than rpmlib.



------- Additional comments from alan@redhat.com 2000-12-12 16:13:43 -------

The install button maybe should prompt with an are you sure to do a '--force' 
type thing but it is needed in some cases so needs to stay

The rpmlib stuff is a mess. I am very tempted to stop using rpmlib and use rpm
down pipes in order to escape the disgusting mess it causes. Possibly rpm-at or
the redcarpet libs will help. I plan to drop support for rpmlib 2.x before
gnorpm 1.0, does 3.x have this problem too ?



------- Additional comments from jbj@redhat.com 2001-03-05 16:13:42 -------

No --force is not the answer. Presenting a single choice "Upgrade" (which is
identical to
"Install" if package is not already imstalled) was the suggestion, as otherwise
you
will have to entries in the database for the same package.

FWIW, proper bug reports against rpm will start to resolve the "mess", as I
can't change
nothing without a request
Comment 1 Malcolm Tredinnick 2002-04-28 01:27:24 UTC
The "Select All" problem has been fixed in CVS now (you can still
select everything, but the upgrade or install process will now only
attempt to operate on the latest version or release).

I can't reproduce (or understand) problem (1), so ignoring that for
now. The enhancement requests about "Upgrade" versus "Install" I'll
leave for when I've reduced the bug list a bit further.
Comment 2 André Klapper 2012-02-19 16:32:58 UTC
According to http://www.jamesh.id.au/software/gnorpm/ this application is unmaintained since 1999. Please feel free to reopen the bugs in future if anyone takes the responsibility for active development.