|
Bugzilla – Full Text Bug Listing |
| Summary: | Packages from a Yum repository type installs with little visual feedback | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Joe Morris <joe_morris> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | freek, james, mistinie, opensuse, suse-beta, uli.2001, wstephenson |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
yast install screen installing from xorg7 repository
My Yast Sources Yast install screen from the Factory repo Mixed install type sources. |
||
|
Description
Joe Morris
2006-11-12 00:41:30 UTC
Created attachment 104814 [details]
yast install screen installing from xorg7 repository
screenshot of Yast installing from the build repository xorg7 Factory source, which is a YUM type source according to Installation Sources.
Ladislav? Stefan? Any idea. I don't see how this can depend on the repository type. May it be YaST is not propperly connected to the zypp callbacks? I have no clue. Those callbacks are handled outside the C++ package selector. *** Bug 221253 has been marked as a duplicate of this bug. *** JFYI: Bug #221253 has logs attached. 2006-11-15 10:32:20 <3> linux(4264) [YCP] SlideShow.ycp:636 SlideShow::SanityCheck(): Slide show not correctly initialized: SlideShow::InitPkgData() I'll try to reproduce that... Created attachment 105629 [details]
My Yast Sources
Here is a snapshot of my sources, clearly showing only the Factory repo and the DVD as a Yast type source.
Created attachment 105630 [details]
Yast install screen from the Factory repo
Here is the snapshot installing from a Yast repo (Factory), which has the proper feedback.
BTW, It is the same feedback no matter which of the other YUM type repositories I try to download from, thus my conclusion it is a YUM repo type handling problem. Yes, it a general problem with YUM sources, increasing the severity. *** Bug 220901 has been marked as a duplicate of this bug. *** Fixed in yast2-pkg-bindings-2.14.4 and yast2-packager-2.14.10 *** Bug 223802 has been marked as a duplicate of this bug. *** *** Bug 223851 has been marked as a duplicate of this bug. *** *** Bug 223366 has been marked as a duplicate of this bug. *** I finally was able to install the updated packages, i.e. joe@jmorris:~> rpm -qa | grep yast2-p yast2-perl-bindings-2.14.0-7 yast2-packager-2.14.10-3 yast2-profile-manager-2.14.1-12 yast2-pam-2.14.0-31 yast2-power-management-2.14.3-7 yast2-pkg-bindings-2.14.4-3 yast2-phone-services-2.14.0-5 yast2-printer-2.14.14-3 yast2-powertweak-2.14.0-8 Much better thanks. I did notice a couple of small errors still. For Yum repositories, there is no number under Packages heading for the packages to install. I will provide a screenshot. Also, I don't know if it is possible, but when they are mixed Yum and Yast type sources, none display anything under Time until the Yum repository type has finished, after which they (or it if only one) disappears, and then the Time shows up for the Yast type repository. Still much better and thanks for your efforts. Created attachment 107190 [details]
Mixed install type sources.
Screenshot of problem still there, no Package number, and while the Yum type repository is present in the download list, there is no Time listed.
Thank you for testing. BTW, I was wrong about the Time problem, it must have been caused by the number of packages installed. I noticed it seems to time the first 2 packages it installs to arrive at a time left for the install, and that appears to be working OK, even with YUM type repositories, so it is just the fact the number of packages do not show. Yes, the number of packages was wrong, fixed in yast2-pkg-bindings-2.15.1 *** Bug 231199 has been marked as a duplicate of this bug. *** Will this fixed package ever make it to a 10.2 update, or will I need to install the yast2 from Factory to get the final fix to this bug? *** Bug 255619 has been marked as a duplicate of this bug. *** |