Bug 72120
Summary: | view advisory => traceback | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michael Schwendt <bugs.michael> |
Component: | up2date | Assignee: | Adrian Likins <alikins> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jay Turner <jturner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | gafton, mihai.ibanescu, srevivo |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-08-27 00:24:24 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michael Schwendt
2002-08-21 08:50:53 UTC
taking a look... fixed in 2.9.53 *** Bug 72425 has been marked as a duplicate of this bug. *** On redhat-list someone reported this bug to be still present in Psyche: https://listman.redhat.com/pipermail/redhat-list/2002-December/162634.html Should be fixed in 3.1.50 or so. Or at least, every way/time/place I can possibly think of hitting "view advisory" seems to work up2date 3.1.46-2 in Severn gives: No package selected. Select a package first. Is that a work-around for empty advisories or unexpected behaviour? work around? Not really. You have to select a package before it can get the advisory info for it. Funny that you think I'm *that* stupid. Of course did I select a package beforehand. But this is Severn -- a beta -- so, what should I get instead of "No package selected. Select a package first."? An empty advisory maybe? Not assuming anyone is stupid (aside from myself, and thats no assumption...). But there is a distinction between selecting package to be updated (check the check mark) and selecting it for seeing advisory info (click the row so that it's highlighted in blue) that is fairly non obvious. (to be fixed, but low on the priority list...). I should probabaly add a comment about that in the error text, if I can come up with wording that doesnt confuse the matter more. Well, that's a bad wording indeed, especially due to the "Select all packages" checkbox at the top. At least the error message could say to "highlight" a package. That would have helped [me]. Or you could highlight the top entry by default. ;) |