Bug 49992 - an entire package tree for one package?
an entire package tree for one package?
Product: Red Hat Linux
Classification: Retired
Component: distribution (Show other bugs)
i386 Linux
low Severity low
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-07-25 16:10 EDT by Panic
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-25 18:50:29 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 Panic 2001-07-25 16:10:42 EDT
Description of Problem:

Installing from re0725.0.  There is an entire tree branch in the individual
package selection for *one package* -- wl, the lisp imap/pop client for
Emacs.  The tree is Utilities/Text.  This seems a little odd -- either wl
should have some company (aren't there any other text utilities?) or we
should eliminate that branch of the tree.

Or is this just a transition to a new structure?

How Reproducible:


Steps to Reproduce:
1. run the installation from the re0725.0 tree, select individual packages
2. Check out the Utilities/Text tree

Actual Results:

Utilities/Text has only one entry -- the wl package

Expected Results:

wl shouldn't be so lonely.

Additional Information:
Comment 1 Michael Fulbright 2001-07-25 16:50:47 EDT
This is probably a packaging error for the package.
Comment 2 Glen Foster 2001-07-25 18:46:15 EDT
Which package is it?  Name the one and we'll make sure it's fixed.
Comment 3 Trond Eivind Glomsrxd 2001-07-25 18:50:25 EDT
It's "wl" (wanderlust). It's fixed in the package (but not built yet , due to
buildsystem) and in specspo (which overrides the former value anyway) in CVS.
Comment 4 Trond Eivind Glomsrxd 2001-07-25 18:55:26 EDT
The package is now built.
Comment 5 Glen Foster 2001-07-25 19:03:37 EDT
This defect is considered MUST-FIX for Fairfax.

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