https://bugzilla.novell.com/show_bug.cgi?id=352719 User meissner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=352719#c1 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com Status|NEW |NEEDINFO Info Provider| |deanjo@sasktel.net --- Comment #1 from Marcus Meissner 2008-01-10 00:15:25 MST --- can you run "zypper refresh" once? it should actually go away automatically... The meta files look correctly signed here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 User kcoombs@gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=352719#c3 Kirk Coombs changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kcoombs@gmail.com Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #3 from Kirk Coombs 2008-01-21 13:00:00 MST --- I just did a fresh install today (Jan 21) and the problem still exists. I was able to work around it by doing the following instructions from http://suseforums.net/lofiversion/index.php/t44342.html ### Begin Quoted Text ### If you get his error message try the suggestion below i helped my after I tried every possible solution i read on variouse forums. "Error Adding repository Main Update Repository Failed http://download.opensuse.org/update/10.3/: Valid metadata not found at specified URL(s) History: - Wrong checksum for patch-fetchmsttfonts.sh-4347.xml" 1) Start Yast2 and run the online update configuration if not already run. 2) Open 'Community Repositorys and add 'main update repository' 3) Open 'Software Repositorys' and tick enable at the 'main update repository'. 4) Open a console with root rights 5) rm /var/cache/zypp/zypp.db 6) zypper refresh 7) The build repository should start now and halt were you get the font error. Now you get and option to answer yes and now and you should accept to continue (you will only get this question when running in console mode). The update window should appear now and tell you that you can perform 1 update that fix an endless loop for yast2. If you don't get this update window run an online update. After this run the online update again and you should be able to get all the updates. ### End Quoted Text ### -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 User cihlarov@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=352719#c5 Klara Cihlarova changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cihlarov@novell.com Status|REOPENED |NEEDINFO Info Provider| |deanjo@sasktel.net --- Comment #5 from Klara Cihlarova 2008-01-29 08:34:47 MST --- Can you please attach YaST logs, see http://en.opensuse.org/Bugs/YaST ? Thanks! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 Kirk Coombs changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|deanjo@sasktel.net | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 Klara Cihlarova changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |yast2-maintainers@suse.de Status|ASSIGNED |NEW -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 User juhliarik@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=352719#c8 Jozef Uhliarik changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |jkupec@novell.com --- Comment #8 from Jozef Uhliarik 2008-02-01 01:38:34 MST --- It seems to be problem of zipper -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=352719#c10 Peter Poeml changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |poeml@novell.com Status|NEEDINFO |NEW Info Provider|poeml@novell.com | --- Comment #10 from Peter Poeml 2008-02-06 09:30:14 MST --- A file patch-fetchmsttfonts.sh-4347.xml doesn't exist on the download server. What I do find is patch-fetchmsttfonts.sh-4825.xml. (Never mind.) We indeed refrain from redirects for .xml files -- but only in the /distribution tree. In the /update tree however, we obey a different regime; there we refrain from redirects for files whose names do not contain numbers. ZrkadloExcludeFileMask "/[^0-9]*$" </Directory> The file in question has numerals though, so we were treating it like "if a mirror has a file named like this, we trust its freshness" which works fine for RPM packages, because their name is altered which each change (rebuild). The patch-FOO-nnn.xml files do not fit the bill however, as it seems. As a consequence, I will exclude them from redirecting from now on. This is going to fix the issue, as far as I can see. If however the filenames are supposed to changes as in rpm rebuilds, then the seen behaviour might show a bug in the update process, which ought to be fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 User meissner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=352719#c12 --- Comment #12 from Marcus Meissner 2008-02-10 03:36:38 MST --- Jan, Rudi changed the file in-place. We occasionaly do this, but not often. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=352719#c14 Peter Poeml changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian@novell.com, deckel@novell.com Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #14 from Peter Poeml 2008-02-14 07:47:47 MST --- Lars, what exactly do you mean with "should be fixed meanwhile"? Do you mean "the manual editing won't happen again"? That would be good. Because, the new situation is: since we don't redirect client requests on patch-*.xml files anymore, these requests adds a LOT to traffic on our download server. Precisely, I see it serving at least 6-8 MB per second of patch-*xml files alone. (thats with the current load of > 300 req/s). Can we afford this? I don't think so. Rudi, Lars - can you guarantee to not edit files again in-place in the future? It would be really better if we can redirect for those files again. What do you think? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 User ro@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=352719#c15 Ruediger Oertel changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ro@novell.com --- Comment #15 from Ruediger Oertel 2008-02-14 09:54:23 MST --- if the mirrors can't update patch-foo.xml in time, how can we expect them to update the master-metadata in time (primary.xml.gz), where the files never change the filename ? for example on the 10.3 repo there are: # du -sch patch-*xml | tail -n 1 6.4M total # du -sch *.gz | tail -n 1 62M total -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 User lrupp@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=352719#c17 Lars Rupp changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|ro@novell.com | Resolution| |WONTFIX --- Comment #17 from Lars Rupp 2008-03-11 06:32:12 MST --- So for you it would be the best if we never ever release any new patch, don't rebuild the repo files (which is normally the case if we add a new patch, ne?) and even don't try to fix things? With this information, I close this bug as WONTFIX: * every new updated package would change the meta files * even if we fix something in the update channels manually, this is just to avoid our internal machines to rebuild the whole metadata - but the result will be the same (just visible earlier outside) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 Peter Poeml changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |ro@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=352719 User poeml@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=352719#c20 Peter Poeml changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #20 from Peter Poeml 2008-03-13 12:50:06 MST --- If anything goes wrong, we can resort to - removing a file from the redirector database (so it is sent only from download.opensuse.org), or - reconfigure download.opensuse.org to the same effect, so it doesn't redirect for certain content We can do that on short notice, and it will be preferable to fixing it on the server only and having to wait for mirrors to pick up, and having clients get broken files until all mirrors have resynced. It would be easy to give you guys access to the database, and I think we should think about an easy way to "invalidate" files (or file patterns) from redirection, temporarily. I could provide a script for that. The test repository is no longer mirrored, indeed. So it doesn't matter what goes on there, from the perspective of mirroring. So I'll remove the redirect exception for the patches-FOO-NNN.xml files now, which I added to work around this bug - and we'll send users to mirrors again for those files. Thanks for clarifying and for your committment! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.