Bug 896057 - UI improvements
Summary: UI improvements
Keywords:
Status: CLOSED DUPLICATE of bug 980543
Alias: None
Product: Fedora
Classification: Fedora
Component: fedup
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-16 14:48 UTC by Neal Becker
Modified: 2013-10-09 22:22 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-09 22:22:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Neal Becker 2013-01-16 14:48:22 UTC
Description of problem:

Needs better UI.

1. Because I had used some testing repos (kde-testing, kde-unstable), which were not enabled by default, fedup went ahead and did the installs it could, leaving some problems after.

It would be great to have a ui that told me of the problems BEFORE the install, so I could have corrected them before finding an unusable kde.

2. When the install is actually running (plymouth), need better feedback as to what it's doing.  On 1 system which had a lousy monitor, I didn't even notice the progress bar, and thought it was hung.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Will Woods 2013-10-09 22:22:31 UTC
1. The next release of fedup is a lot more straightforward about warning you of dependency errors or packages that aren't going to be upgraded. This is the same as (e.g.) bug 981442 and it's already fixed in git. See the following commits:

  https://github.com/wgwoods/fedup/compare/29d97f45...866319d2

2. You can hit Esc to see detailed package installation progress; this is covered by bug 980543.

Since both these problems are duplicates of other bugs, I'm closing this as a duplicate. Gotta pick one, so I'll pick the one that's still open.

*** This bug has been marked as a duplicate of bug 980543 ***


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