[opensuse-factory] In middle of update mirror not accessible?
Hi, 454.53 MB to go: 166pkgs, the Yast section: packages not found. every pkg fails, refreshing does nor help. ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss File'./suse/x86_64/yast2-vm-2.16.7-1.11.x86_64.rpm' not found on medium 'ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss' -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Hi,
454.53 MB to go: 166pkgs, the Yast section: packages not found. every pkg fails, refreshing does nor help. ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss
File'./suse/x86_64/yast2-vm-2.16.7-1.11.x86_64.rpm' not found on medium 'ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss'
-- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Oddball napsal(a):
Oddball schreef:
Hi,
454.53 MB to go: 166pkgs, the Yast section: packages not found. every pkg fails, refreshing does nor help. ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss
File'./suse/x86_64/yast2-vm-2.16.7-1.11.x86_64.rpm' not found on medium 'ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss'
Well, yes, that's known problem we face all the time. Factory can change while you're updating to the snapshot. YaST/Zypper will offer to download all packages first before installing them but this doesn't work yet. Bye Lukas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkkYCeQACgkQVSqMdRCqTiyc1wCfW0o1EJ+MjoPlVz8nhH/63dTY +GwAn35QGan/hL75TzqkTUaNj5gDv5Ia =eOoq -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Lukas Ocilka wrote:
Oddball napsal(a):
Oddball schreef:
Hi,
454.53 MB to go: 166pkgs, the Yast section: packages not found. every pkg fails, refreshing does nor help. ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss
File'./suse/x86_64/yast2-vm-2.16.7-1.11.x86_64.rpm' not found on medium 'ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss'
Well, yes, that's known problem we face all the time. Factory can change while you're updating to the snapshot. YaST/Zypper will offer to download all packages first before installing them but this doesn't work yet.
Bye Lukas
Workaround by zypper can be found in this blog post (little advertise :) - http://lizards.opensuse.org/2008/10/30/how-survive-zypper-dup-on-system-with... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Josef Reidinger schreef:
Lukas Ocilka wrote:
Oddball napsal(a):
Oddball schreef:
Hi,
454.53 MB to go: 166pkgs, the Yast section: packages not found. every pkg fails, refreshing does nor help. ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss
File'./suse/x86_64/yast2-vm-2.16.7-1.11.x86_64.rpm' not found on medium 'ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss'
Well, yes, that's known problem we face all the time. Factory can change while you're updating to the snapshot. YaST/Zypper will offer to download all packages first before installing them but this doesn't work yet.
Bye Lukas
Yep, i know, but that doesn't make it less painfull....
Workaround by zypper can be found in this blog post (little advertise :) - http://lizards.opensuse.org/2008/10/30/how-survive-zypper-dup-on-system-with...
zypper mr –keep-packages –remote , does this mean that the repo-'state' itself is cached on the repo? because this would save a lot of trouble.. -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball wrote:
Josef Reidinger schreef:
Lukas Ocilka wrote:
Oddball napsal(a):
Oddball schreef:
Hi,
454.53 MB to go: 166pkgs, the Yast section: packages not found. every pkg fails, refreshing does nor help. ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss
File'./suse/x86_64/yast2-vm-2.16.7-1.11.x86_64.rpm' not found on medium 'ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss'
Well, yes, that's known problem we face all the time. Factory can change while you're updating to the snapshot. YaST/Zypper will offer to download all packages first before installing them but this doesn't work yet.
Bye Lukas
Yep, i know, but that doesn't make it less painfull....
Workaround by zypper can be found in this blog post (little advertise :) - http://lizards.opensuse.org/2008/10/30/how-survive-zypper-dup-on-system-with...
zypper mr –keep-packages –remote , does this mean that the repo-'state' itself is cached on the repo?
because this would save a lot of trouble..
Storing repo state is useless if that file is not on server, so you can't download it. But if you download it and doesn't refresh it (also no autorefresh) install in same state as it saves it packages. JR -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Josef Reidinger schreef:
Oddball wrote:
Josef Reidinger schreef:
Lukas Ocilka wrote:
Oddball napsal(a):
Oddball schreef:
Hi,
454.53 MB to go: 166pkgs, the Yast section: packages not found. every pkg fails, refreshing does nor help. ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss
File'./suse/x86_64/yast2-vm-2.16.7-1.11.x86_64.rpm' not found on medium 'ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss'
Well, yes, that's known problem we face all the time. Factory can change while you're updating to the snapshot. YaST/Zypper will offer to download all packages first before installing them but this doesn't work yet.
Bye Lukas
Yep, i know, but that doesn't make it less painfull....
Workaround by zypper can be found in this blog post (little advertise :) - http://lizards.opensuse.org/2008/10/30/how-survive-zypper-dup-on-system-with...
zypper mr –keep-packages –remote , does this mean that the repo-'state' itself is cached on the repo?
because this would save a lot of trouble..
Storing repo state is useless if that file is not on server, so you can't download it. But if you download it and doesn't refresh it (also no autorefresh) install in same state as it saves it packages. JR
Than you still have the chance not to complete the download, and use bandwith for nothing..? -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball wrote:
Josef Reidinger schreef:
Oddball wrote:
Josef Reidinger schreef:
Lukas Ocilka wrote:
Oddball napsal(a):
Oddball schreef:
> Hi, > > 454.53 MB to go: 166pkgs, the Yast section: packages not found. > every pkg fails, refreshing does nor help. > ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss > > File'./suse/x86_64/yast2-vm-2.16.7-1.11.x86_64.rpm' not found on medium > 'ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss' > > Well, yes, that's known problem we face all the time. Factory can change while you're updating to the snapshot. YaST/Zypper will offer to download all packages first before installing them but this doesn't work yet.
Bye Lukas
Yep, i know, but that doesn't make it less painfull....
Workaround by zypper can be found in this blog post (little advertise :) - http://lizards.opensuse.org/2008/10/30/how-survive-zypper-dup-on-system-with...
zypper mr –keep-packages –remote , does this mean that the repo-'state' itself is cached on the repo?
because this would save a lot of trouble..
Storing repo state is useless if that file is not on server, so you can't download it. But if you download it and doesn't refresh it (also no autorefresh) install in same state as it saves it packages. JR
Than you still have the chance not to complete the download, and use bandwith for nothing..?
I don't say nothing...only files which is updated immediately need redownload, so this need be much package. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
zypper mr –keep-packages –remote , does this mean that the repo-'state' itself is cached on the repo?
because this would save a lot of trouble..
What i understand is that pkgs have to get from one place to another first? My speed is high enough, somewhere around 250K/s, installing doesn't take much time either. Total dl + installing 1150+ or so pkgs, 2,5 GB+ done in less than 2 hours. Problem is to recognise when exactly the repo changes.. and how much time that takes.. At few occasions i ran into this, and offcourse many off us have, and when i logged out and in again, refreshed the repos, and than factory update again, the changes were taken into account, and the update could be finished.. This time not yet. If i reboot completely, chance is big, that i have to reinstall, and start over.... I rather would not want this, because it takes much valuable time... everybody knows this... Will there be no way to solve this problem to everybodies satisfactory? Like paralell serving? That means that factory can change, but not for the servers that are occupied, (with uploading the updates to the custumers,) they change as soon as the updates are completed. As soon as the exhanged image is available, all new connections get the new image to update from, while those who are busy updating from the older one, can complete their downloads. Is this construction possible somehow? I can imagine that some script would be able to redirect new connections to the location of the new image, while existing connections remain to download from the earlier image? -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Nov 10, 2008 at 11:16:04AM +0100, Lukas Ocilka wrote:
Oddball napsal(a):
Oddball schreef:
Hi,
454.53 MB to go: 166pkgs, the Yast section: packages not found. every pkg fails, refreshing does nor help. ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss
File'./suse/x86_64/yast2-vm-2.16.7-1.11.x86_64.rpm' not found on medium 'ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss'
Well, yes, that's known problem we face all the time. Factory can change while you're updating to the snapshot. YaST/Zypper will offer to download all packages first before installing them but this doesn't work yet.
Confirmed - factory was replaced upstream, and it was in the course of disappearing on ftp.gwdg.de just during your update. According to the URL, you are using ftp.gwdg.de directly as entry point? YMMV. Btw, what does zypper do in such a case? Does it restart the update in such a case? It should do the same as Yum, IMO: download metadata + packages, and when that fails at any point, you'd refresh the local metadata and start over, and once you have a consistent state on your system (including packages) _then_ start the actual update. Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development
On 2008/11/10 11:55 (GMT+0100) Peter Poeml composed:
It should do the same as Yum, IMO: download metadata + packages, and when that fails at any point, you'd refresh the local metadata and start over, and once you have a consistent state on your system (including packages) _then_ start the actual update.
That can't work consistently on systems with limited / space. Most of my installs use a small / partition, so downloading all packages first can easily fill up / before installation of any packages starts. It happens to me frequently on systems using apt-get. Smart defaults to downloading everything first, so I have to work around that with small scripts that divide the task into manageable chunks. It has a stepped option, but the first time it runs into an unavailable package, it halts instead of trying to do any other packages. URPMI defaults to downloading small bunches, installing them, then repeating. I like that about it, and that zypper is more like it than smart or apt-get. -- "Love is not easily angered. Love does not demand its own way." 1 Corinthians 13:5 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Nov 10, 2008 at 06:10:48AM -0500, Felix Miata wrote:
On 2008/11/10 11:55 (GMT+0100) Peter Poeml composed:
It should do the same as Yum, IMO: download metadata + packages, and when that fails at any point, you'd refresh the local metadata and start over, and once you have a consistent state on your system (including packages) _then_ start the actual update.
That can't work consistently on systems with limited / space. Most of my installs use a small / partition, so downloading all packages first can easily fill up / before installation of any packages starts. It happens to me frequently on systems using apt-get.
Yes - I actually didn't mean to imply that this should be the *only* way of doing it. An optional "download on the fly" strategy makes sense in some cases.
Smart defaults to downloading everything first, so I have to work around that with small scripts that divide the task into manageable chunks. It has a stepped option, but the first time it runs into an unavailable package, it halts instead of trying to do any other packages.
It is much easier to work around in this way than in the other.
URPMI defaults to downloading small bunches, installing them, then repeating. I like that about it, and that zypper is more like it than smart or apt-get.
I actually find myself doing that frequently because in real life there are always some issues when doing a large update that one needs to work through. But I think it is a hard to systematically separate an update in reasonable chunks, without ending up having at least one pretty large chunk. A useful distinction I often make is C and C++ programs. C++ programs are rarely vital, and I don't care if they are updated later or if the update doesn't complete. Peter -- Contact: admin@opensuse.org (a.k.a. ftpadmin@suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development
Peter Poeml schreef:
On Mon, Nov 10, 2008 at 11:16:04AM +0100, Lukas Ocilka wrote:
Oddball napsal(a):
Oddball schreef:
Hi,
454.53 MB to go: 166pkgs, the Yast section: packages not found. every pkg fails, refreshing does nor help. ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss
File'./suse/x86_64/yast2-vm-2.16.7-1.11.x86_64.rpm' not found on medium 'ftp://ftp.gwdg.de/pub/opensuse/factory/repo/oss'
Well, yes, that's known problem we face all the time. Factory can change while you're updating to the snapshot. YaST/Zypper will offer to download all packages first before installing them but this doesn't work yet.
Confirmed - factory was replaced upstream, and it was in the course of disappearing on ftp.gwdg.de just during your update.
According to the URL, you are using ftp.gwdg.de directly as entry point? YMMV.
Yes i switched this morning because the other mirrors at: http://download.opensuse.org/distribution/11.1/repo/'etc' where acting unstable..
Btw, what does zypper do in such a case? Does it restart the update in such a case?
It should do the same as Yum, IMO: download metadata + packages, and when that fails at any point, you'd refresh the local metadata and start over, and once you have a consistent state on your system (including packages) _then_ start the actual update.
Peter
That indeed has and did happen on earlier occasions, just not this time... But i will try lateron to see if will find the new data and adapt... -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Peter Poeml schreef:
Confirmed - factory was replaced upstream, and it was in the course of disappearing on ftp.gwdg.de just during your update.
According to the URL, you are using ftp.gwdg.de directly as entry point? YMMV.
Yes i switched this morning because the other mirrors at: http://download.opensuse.org/distribution/11.1/repo/'etc' where acting
sorry meanth these http://download.opensuse.org/factory/repo/oss/
unstable..
Btw, what does zypper do in such a case? Does it restart the update in such a case?
It should do the same as Yum, IMO: download metadata + packages, and when that fails at any point, you'd refresh the local metadata and start over, and once you have a consistent state on your system (including packages) _then_ start the actual update.
Peter
That indeed has and did happen on earlier occasions, just not this time... But i will try lateron to see if will find the new data and adapt...
Yast does not adapt to the new situation (have not rebooted yet, only logged out and in few times.) I cannot access media... -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Oddball schreef:
Peter Poeml schreef:
Confirmed - factory was replaced upstream, and it was in the course of disappearing on ftp.gwdg.de just during your update.
According to the URL, you are using ftp.gwdg.de directly as entry point? YMMV.
Yes i switched this morning because the other mirrors at: http://download.opensuse.org/distribution/11.1/repo/'etc' where acting
sorry meanth these http://download.opensuse.org/factory/repo/oss/
unstable..
Btw, what does zypper do in such a case? Does it restart the update in such a case?
It should do the same as Yum, IMO: download metadata + packages, and when that fails at any point, you'd refresh the local metadata and start over, and once you have a consistent state on your system (including packages) _then_ start the actual update.
Peter
That indeed has and did happen on earlier occasions, just not this time... But i will try lateron to see if will find the new data and adapt...
Yast does not adapt to the new situation (have not rebooted yet, only logged out and in few times.) I cannot access media...
Zypper noticed the key as in the message from Carlos this morning, but after few adjustments, it is running dup. -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
Oddball schreef:
Oddball schreef:
Peter Poeml schreef:
Confirmed - factory was replaced upstream, and it was in the course of disappearing on ftp.gwdg.de just during your update.
According to the URL, you are using ftp.gwdg.de directly as entry point? YMMV.
Yes i switched this morning because the other mirrors at: http://download.opensuse.org/distribution/11.1/repo/'etc' where acting
sorry meanth these http://download.opensuse.org/factory/repo/oss/
unstable..
Btw, what does zypper do in such a case? Does it restart the update in such a case?
It should do the same as Yum, IMO: download metadata + packages, and when that fails at any point, you'd refresh the local metadata and start over, and once you have a consistent state on your system (including packages) _then_ start the actual update.
Peter
That indeed has and did happen on earlier occasions, just not this time... But i will try lateron to see if will find the new data and adapt...
Yast does not adapt to the new situation (have not rebooted yet, only logged out and in few times.) I cannot access media...
Zypper noticed the key as in the message from Carlos this morning, but after few adjustments, it is running dup.
What was nice was that i accidentaly touched the outlet power-switch when i took the adapter of my laptop out: Power gone at that very instant. Held my haert while rebooting: was in the middle of zypper dup...after the broken yast update.. Black grub screen, returning at entries...grub confused, had some trouble to find the right partition, cleaned it and booted... <sigh of relief> NP wse... pfff -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
What was nice was that i accidentaly touched the outlet power-switch when i took the adapter of my laptop out: Power gone at that very instant. Held my haert while rebooting: was in the middle of zypper dup...after the broken yast update..
Black grub screen, returning at entries...grub confused, had some trouble to find the right partition, cleaned it and booted... <sigh of relief>
NP wse... pfff
fyi My pc crashed, not the laptop, they were in the same switchable poweroutlet. Zypper runs at constant speed of 318K/s, very nice! -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Oddball schreef:
fyi My pc crashed, not the laptop, they were in the same switchable poweroutlet. Zypper runs at constant speed of 318K/s, very nice!
Just one time out, but finished now.. -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- 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 On Monday, 2008-11-10 at 11:55 +0100, Peter Poeml wrote:
Confirmed - factory was replaced upstream, and it was in the course of disappearing on ftp.gwdg.de just during your update.
According to the URL, you are using ftp.gwdg.de directly as entry point? YMMV.
Btw, what does zypper do in such a case? Does it restart the update in such a case?
Nope, it fails, with weird errors, like package not found on repo. That's one of the reasons I said that factory should keep versions numbers, a timestamp. If while downloading zypper sees a different stamp than at the beginning, it should abort with informative error. The timestamp could perhaps also be used to keep snapshots of the repo, so that we users are guaranteed the repo doesn't change for some days.
It should do the same as Yum, IMO: download metadata + packages, and when that fails at any point, you'd refresh the local metadata and start over, and once you have a consistent state on your system (including packages) _then_ start the actual update.
That requires double disk space. And there is no guarantee that we won't have to restart the download many times. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkkYLhoACgkQtTMYHG2NR9WVUACePemGO8sUG9r5Lz1N4sERY4Qc Ho4Ani6j9Rn0EjZGqHVcF0KlvXTHrJeI =w5Z6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Mon, Nov 10, 2008 at 01:50:32 +0100, Carlos E. R. wrote:
It should do the same as Yum, IMO: download metadata + packages, and when that fails at any point, you'd refresh the local metadata and start over, and once you have a consistent state on your system (including packages) _then_ start the actual update.
That requires double disk space.
With some intelligence it could actually be possible to delete cached packages that are known to be obsolete already, before their new versions are downloaded, no?
And there is no guarantee that we won't have to restart the download many times.
No guarantuee, but this is function of the frequency of factory replacement, and your download speed. Obviously, when factory is replaced every 5 minutes, this is never going to work, unless a lot of snapshots are kept around. So there needs to be some piece and time for updates. The same happens for the buildservice - it's always possible that some repository is being updated while you access it. By the time you press 'y' it could be have been replaced, so you need to start again. The difference to the Factory is that the second attempt is very likely successfull. While with Factory the second attemt is very likely unsuccessful ;) Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. wrote:
Btw, what does zypper do in such a case? Does it restart the update in such a case?
Nope, it fails, with weird errors, like package not found on repo.
That's one of the reasons I said that factory should keep versions numbers, a timestamp. If while downloading zypper sees a different stamp than at the beginning, it should abort with informative error. The timestamp could perhaps also be used to keep snapshots of the repo, so that we users are guaranteed the repo doesn't change for some days.
Actualy the timestamp of the index file (repo/repomd.xml, content) is the timestamp of the repostiory. So we have this, and use this, but not for media problems when downloading rpms. We could improve this, indeed. The type of error should be accessible to applications from MediaException (i was about to suggest this on zypp-devel), so that they can act on them (zypper could check whether metadata are up to date in case of FileNotFound error when downloading rpm file and report that to user, or this can be done in libzypp's commit code and a specific exception can be thrown to the apps). - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ----------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkkZlwAACgkQgEhGpmN+6QGiOwCfRYNV4r9ifAcI/sZp/5YARo6c o/kAn1Z8MdOj0vVY9JRyR/GoHkr81hwA =oTCV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (7)
-
Carlos E. R. -
Felix Miata -
Jan Kupec -
Josef Reidinger -
Lukas Ocilka -
Oddball -
Peter Poeml