[opensuse-factory] zypper: does not recover from network hiccup.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I was doing a "zypper shell" / "dup" of factory when my adsl got a hiccup, after 8 hours: network went down for some seconds, and the provider gave me a new IP. This interruption lasts something like 20..30 seconds, in the middle of a package download, causing it to abort the update: ... ... Downloading package xmoto-0.4.1-7.i586, 16.0 M (23.6 M unpacked) * Downloading: xmoto-0.4.1-7.i586.rpm [done (43.9 K/s)] * Installing: xmoto-0.4.1-7 Downloading package xgl-git_071026-48.i586, 1.6 M (4.5 M unpacked) * Downloading: xgl-git_071026-48.i586.rpm [done (89 B/s)] Problem downloading the package file from the repository: Can't provide ./suse/i586/xgl-git_071026-48.i586.rpm : Timeout exceed Please see the above error message for a hint. zypper> Shouldn't zypper offer a retry of the package before aborting? I start again "dup", and it says its going to download 1.6 GB, as if nothing were done previously. And it asks again that I accept the license I already accepted. I can not make sure that the network will not go down while downloading that amount of data! Its impossible! ... In order to install this package, you must agree to terms of the above license. Continue? [yes/NO]: yes * Removing libxine1-arts-1.1.8-0.pm.0 Error * Removing libxine1-dvb-1.1.8-0.pm.0 Error * Removing libxine1-dxr3-1.1.8-0.pm.0 Error * Removing libxine1-gnome-vfs-1.1.8-0.pm.0 Error * Removing libxine1-jack-1.1.8-0.pm.0 Error * Removing libxine1-sdl-1.1.8-0.pm.0 Error * Removing xine-browser-plugin-1.0-0.pm.0 Error * Removing TnL-tools-20070827-0.pm.2 Error * Removing TnL-20070827-0.pm.2 Error * Removing codeine-1.0.1-0.pm.0 Error * Removing libxine1-1.1.8-0.pm.0 Error Downloading package AdobeICCProfiles-2.0-100.noarch, 3.9 M (5.4 M unpacked) * Downloading: AdobeICCProfiles-2.0-100.noarch.rpm [done (75.6 K/s)] * Installing: AdobeICCProfiles-2.0-100 I had to abort the zypper shell session, restart and retry: ] nimrodel:/ # rpm -q zypper ] zypper-0.10.4-9 ] nimrodel:/ # zypper shell ] zypper> dup ... Now it says: ] Overall download size: 918.0 M. After the operation, additional 149.1 M ] will be used. So, after the restart, it does know that "some" 700 MB were already updated. Shouldn't it be cleverer than that? It should have asked me if I wanted to retry or abort, not abort without question. I'm sure that all users can not ensure a fully reliable network for the many hours of the download! - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH7XCBtTMYHG2NR9URAog8AKCMvN1aPNYyKotF1WiZe42T78g+EQCeIsfl bdFIZIzpuqXe4o/QBIGE2xQ= =ldGF -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Fri, 2008-03-28 at 23:25 +0100, Carlos E. R. wrote:
Shouldn't zypper offer a retry of the package before aborting?
See https://bugzilla.novell.com/show_bug.cgi?id=340345 Hub --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-03-28 at 18:32 -0400, Hubert Figuiere wrote:
Yes, it matches what I saw. I did find another problem with some packaga failing to unpackage, cpio something, file is directory or something - and it did ask "retry ignore abort". But not for the network problem. About comment #4 in that bugzilla: "It certainly does not make sense to continue without solving, as it makes breaking your system possible." IMO, it breaks more things by aborting the upgrade for a single failed package, as everything else will not be upgraded. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH7ZtdtTMYHG2NR9URAgnPAJ0Utai7+9vD3UEwxl5a+kJcGczA9QCeJ7Xo mKqB3moQnkgGcIBIBepBjjg= =liyQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Fri, 2008-03-28 at 23:25 +0100, Carlos E. R. wrote:
And I forgot. Quit zypper and start again. It will realise that some stuff has been installed. This is another annoyance, I'm not sure it has been reported/fixed. Hub --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-03-28 at 18:33 -0400, Hubert Figuiere wrote:
Yes, this I tried already and worked... I still have some of the not so old school of "exit and retry".
This is another annoyance, I'm not sure it has been reported/fixed.
Dunno. I'm not used to this method of upgrading, it is the first time I use it. Even more... I'm running a factory upgrade via zypper on a partition mounted under a functional 10.3 - the partition is chrooted. Zypper runs fine, yast failed (even text mode). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH7Z1atTMYHG2NR9URAoS1AJ9PwiMkD7IXKb/03X5lp0+SDzvSnACfbBGN scsMwk2RXa+/KiGzWBBtdIo= =31j4 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Dňa Saturday 29 March 2008 02:37:27 Carlos E. R. ste napísal:
In general, zypper shell is not very reliable at this point. And given the speed of the new libzypp in Factory, it's probably not even worth using it in day-to-day work. Although, any bug report is welcome and we are working on resolving the issues. Stano --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-03-31 at 11:26 +0200, Stanislav Visnovsky wrote:
Subject: Re: ***SPAM*** Re: [opensuse-factory] zypper: does not recover from network hiccup.
Hey! Are you people testing a new ***SPAM*** pollicy? :-p
What do you recomend? "zypper dup" directly, not "zypper shell"? Or Yast? Yast is out of the question for this situation. I'll explain: I'm running 10.3 standard. On it, I mount the factory partition: mount /otros/test_d/ mount /otros/test_d/boot/ mount --bind /proc /otros/test_d/proc mount --bind /sys /otros/test_d/sys mount --bind /dev /otros/test_d/dev cp -f /etc/resolv.conf /otros/test_d/etc/resolv.conf chroot /otros/test_d/ And then, I run zypper to update/upgrade factory. I did that to upgrade one of my _test_ partitions, previously 10.3 stable, previously 10.3 beta, to 11 alfa, and it worked fine. Yast GUI refuses to work in this situation, something about X display permissions. Yast ncurses works, but not all sections. The software module failed. Thus I resorted to zypper: first upgrade zypper itself, then the entire thing. It worked fine, I must say, although it took 12 hours downloading. Certainly, I can not stop my machine, boot factory, and wait for a 12 hours download while I sit looking! So, the procedure for upgrading a factory partition from inside another "stable" partition worked quite well, and the resulting factory booted fine later. Although a procedure to use zypper or yast to upgrade another partition would be nicer ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH8Mw7tTMYHG2NR9URApzxAJsGxx/KAxVDgythJyHKyZidAS6GGwCghBWO lgvf4sjmUlyMTr3No0yV5zw= =mA3K -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Carlos E. R. wrote:
yes, see bug #328822 (fix to be released in zypper 0.10.5) Cheers, jano --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Fri, 2008-03-28 at 23:25 +0100, Carlos E. R. wrote:
Shouldn't zypper offer a retry of the package before aborting?
See https://bugzilla.novell.com/show_bug.cgi?id=340345 Hub --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-03-28 at 18:32 -0400, Hubert Figuiere wrote:
Yes, it matches what I saw. I did find another problem with some packaga failing to unpackage, cpio something, file is directory or something - and it did ask "retry ignore abort". But not for the network problem. About comment #4 in that bugzilla: "It certainly does not make sense to continue without solving, as it makes breaking your system possible." IMO, it breaks more things by aborting the upgrade for a single failed package, as everything else will not be upgraded. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH7ZtdtTMYHG2NR9URAgnPAJ0Utai7+9vD3UEwxl5a+kJcGczA9QCeJ7Xo mKqB3moQnkgGcIBIBepBjjg= =liyQ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Fri, 2008-03-28 at 23:25 +0100, Carlos E. R. wrote:
And I forgot. Quit zypper and start again. It will realise that some stuff has been installed. This is another annoyance, I'm not sure it has been reported/fixed. Hub --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-03-28 at 18:33 -0400, Hubert Figuiere wrote:
Yes, this I tried already and worked... I still have some of the not so old school of "exit and retry".
This is another annoyance, I'm not sure it has been reported/fixed.
Dunno. I'm not used to this method of upgrading, it is the first time I use it. Even more... I'm running a factory upgrade via zypper on a partition mounted under a functional 10.3 - the partition is chrooted. Zypper runs fine, yast failed (even text mode). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH7Z1atTMYHG2NR9URAoS1AJ9PwiMkD7IXKb/03X5lp0+SDzvSnACfbBGN scsMwk2RXa+/KiGzWBBtdIo= =31j4 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

Dňa Saturday 29 March 2008 02:37:27 Carlos E. R. ste napísal:
In general, zypper shell is not very reliable at this point. And given the speed of the new libzypp in Factory, it's probably not even worth using it in day-to-day work. Although, any bug report is welcome and we are working on resolving the issues. Stano --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-03-31 at 11:26 +0200, Stanislav Visnovsky wrote:
Subject: Re: ***SPAM*** Re: [opensuse-factory] zypper: does not recover from network hiccup.
Hey! Are you people testing a new ***SPAM*** pollicy? :-p
What do you recomend? "zypper dup" directly, not "zypper shell"? Or Yast? Yast is out of the question for this situation. I'll explain: I'm running 10.3 standard. On it, I mount the factory partition: mount /otros/test_d/ mount /otros/test_d/boot/ mount --bind /proc /otros/test_d/proc mount --bind /sys /otros/test_d/sys mount --bind /dev /otros/test_d/dev cp -f /etc/resolv.conf /otros/test_d/etc/resolv.conf chroot /otros/test_d/ And then, I run zypper to update/upgrade factory. I did that to upgrade one of my _test_ partitions, previously 10.3 stable, previously 10.3 beta, to 11 alfa, and it worked fine. Yast GUI refuses to work in this situation, something about X display permissions. Yast ncurses works, but not all sections. The software module failed. Thus I resorted to zypper: first upgrade zypper itself, then the entire thing. It worked fine, I must say, although it took 12 hours downloading. Certainly, I can not stop my machine, boot factory, and wait for a 12 hours download while I sit looking! So, the procedure for upgrading a factory partition from inside another "stable" partition worked quite well, and the resulting factory booted fine later. Although a procedure to use zypper or yast to upgrade another partition would be nicer ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFH8Mw7tTMYHG2NR9URApzxAJsGxx/KAxVDgythJyHKyZidAS6GGwCghBWO lgvf4sjmUlyMTr3No0yV5zw= =mA3K -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (5)
-
Carlos E. R.
-
Carlos E. R.
-
Hubert Figuiere
-
Jan Kupec
-
Stanislav Visnovsky