Bug 327490

Summary:	Editing Properties of a Repository Fails to Invalidate the Cache
Product:	[openSUSE] openSUSE 11.0	Reporter:	Crispin Cowan <crispin>
Component:	YaST2	Assignee:	Ladislav Slezák <lslezak>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P3 - Medium
Version:	Alpha 2
Target Milestone:	---
Hardware:	x86
OS:	openSUSE 10.3
Whiteboard:
Found By:	DeveloperNet	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Crispin Cowan 2007-09-22 16:58:35 UTC

I removed my initial physical DVD from my repositories, and then added the .iso file. However, I screwed it up and entered a bogus file (an incomplete copy of the full openSUSE-10.3-RC1-DVD-i386.iso file). So, I go back and edit the path name of my local ISO repository, and continue to get the same error:

There was an error in the repository initialization.
'10.3_RC1_ISO_1': /var/cache/zypp/raw/10.3_RC1_ISO_1: Required file is missing: ./content

And of course you can't load any software from the .iso file.

However, when I deleted this repository and then added it again, it worked fine.

Conjecture: YaST has built a cache of the repository, and is failing to invalidate that cache when you change the path name to the repository.

I have not tested this, but it probably fails to invalidate the cache when you change the path name, server name, URL, etc. for any kind of repository.

A fairly difficult to trip bug, because you have to point it at a repository that is good enough to build a cache in the first place, and then change the path name.

Comment 1 Ladislav Slezák 2007-09-26 08:11:52 UTC

The old cache is removed when you change URL to the repository (I just have tested this). So this is not a general problem.

I think this problem was caused by the incomplete ISO image, better error handling should solve this problem.

Comment 2 Stephan Kulow 2008-06-25 09:10:46 UTC

mass reopening of later+remind bugs of 11.0

Comment 3 Ladislav Slezák 2008-11-28 09:07:46 UTC

The cache should be removed when registering a repo fails.

Comment 4 Ladislav Slezák 2009-07-10 11:38:24 UTC

Fixed in yast2-pkg-bindings-2.18.9 - the cache is removed when creating a new repository and Yast should use really unique alias for new repositories (duplicated alias can lead to this problem).