Bug 403673 - Yast Package Manager(Software Management) - automatically skip/retry failed packages
Summary: Yast Package Manager(Software Management) - automatically skip/retry failed p...
Status: RESOLVED DUPLICATE of bug 396159
: 409467 430207 (view as bug list)
Alias: None
Product: openSUSE 11.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: i686 Other
: P4 - Low : Enhancement (vote)
Target Milestone: ---
Assignee: Ladislav Slezák
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-25 11:24 UTC by Parameshwara Bhat
Modified: 2008-10-02 17:20 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Parameshwara Bhat 2008-06-25 11:24:00 UTC
1.If during package download,internet connection breaks,then returns,PM is hung up.It cannot reconnect and continue by itself.After long time,it comes up with an error message.(This contnues from 10.1 - or since I started using)
2.If PM cannot download a package for network related reasons,it doesn't continue till user intervenes.This makes it incapable of unattended update/installation.Compare this with Synaptic behaviuor where if network connection is ON,it continues to download and install other packages and displays error on un-downloaded and dependent packages only in the end.(This contnues from 10.1 - or since I started using)
3.I read somewhere that from OS 11.0 onwards,PM can automatically detect and connect to mirrors to download.But,there is no evidence of that in my observation.I have a broadband connection of 2 Mbps and higher.But,in my use of OS 11.0 RC1 and Final,PM nowhere is able to make good use of my bandwideth.It's speed often is a few Bytes/sec and finally it throws up in error.I have tested my connection exact at the time of this occurrence to come to this conclusion.
4.There is still no good amount of proper integration and segregation among 'security update','upgrade','dist-upgrade'.What amount of this is visible in zypper is not visible/apparent in Yast PM.
5.Though Repository management is included in 'software management' in yast,there are too many overlapping choices in yast-software group.Compare this with Synaptic or fedora package management.

At this time,OS package management is riddled with irritants though it's backend is claimed much superior to it's above mentioned competitors.
Comment 1 Parameshwara Bhat 2008-06-25 12:29:52 UTC
Must Yast refresh cache everytime?You install packages,close package
manager,re-open it to install a few more.It refreshes cache again!Does it
expect newer packages every minute?can't there be a time based algorithm for
refreshment? Or like Synaptic,user initiated refreshment?I know OS 11.0 allows
you to turn-off auto-refreshing,but that exactly(auto-refreshing) is setup by
the OS.Even if it is on,why every minute refreshment?That's insane.
Comment 2 Ladislav Slezák 2008-07-22 11:10:07 UTC
Please, open a separate report for each problem next time, it's (almost) impossible to track more problems in one report.

1) Depending on error type yast (libzypp) in some cases retries downloading.

2) Sounds like a good feature request...

3) AFAIK the mirrors must be supported on the server side, it should be supported by software.opensuse.org. Parallel download in one of the future features.

4) I don't see a problem there: "security update" = use 'yast2 online_update' or the opensuse-updater applet.
   "upgrade" = select the packages to upgrade in the package manager
   "dist-upgrade" = boot from the upgrade medium and select "upgrade" instead of fresh install or install "yast2-update-FACTORY" package for updating the system

5) The problem has already been reported, I just cannot find the bug number right now.

To comment #1: Yes, there is a timeout between the refreshes. See Refresh section in 'man zypper'.
Comment 3 Ladislav Slezák 2008-09-29 14:44:44 UTC
*** Bug 409467 has been marked as a duplicate of this bug. ***
Comment 4 Ladislav Slezák 2008-09-29 14:45:47 UTC
*** Bug 430207 has been marked as a duplicate of this bug. ***
Comment 5 Ladislav Slezák 2008-09-29 15:50:50 UTC

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