Bug 708019

Some other repros are affected.

Created attachment 442067 [details]
zypp history

Created attachment 442069 [details]
y2log

It seems that the repository definitions are messed somehow:

2011-07-25 13:09:43 <1> linux-9aw6(11076) [Progress++] ProgressData.cc(report):86 {#1454|/etc/zypp/repos.d/Virtualization_openSUSE_11.4_.repo}END
2011-07-25 13:09:43 <1> linux-9aw6(11076) [zypp] RepoFileReader.cc(repositories_in_stream):100 - alias       : Virtualization/openSUSE_11.4/
2011-07-25 13:09:43 <1> linux-9aw6(11076) [zypp] ProductFileReader.cc(parse):242 - name        : openSUSE BuildService - Banshee
2011-07-25 13:09:43 <1> linux-9aw6(11076) [zypp] ProductFileReader.cc(parse):242 - enabled     : 1
2011-07-25 13:09:43 <1> linux-9aw6(11076) [zypp] ProductFileReader.cc(parse):242 - autorefresh : 1
2011-07-25 13:09:43 <1> linux-9aw6(11076) [zypp] ProductFileReader.cc(parse):242 - url         : http://download.opensuse.org/repositories/Virtualization/openSUSE_11.4/

The Virtuallization repository has Banshee name. Check the content of /etc/zypp/repos.d/Virtualization_openSUSE_11.4_.repo file.

Did you manually edit the repo files? The zypp history file does not contain any change of the repository.

No, I did not manually edit the repro file.

In the past I had to do a downgrade of my system to the openSUSE11.4 installation dvd(not starting system), which brought some nasty figuring around with it to bring the things up again, also the repros, so the cause of this might be there.

Interesting! I´ve looked at the file:

[Virtualization/openSUSE_11.4/]
name=openSUSE BuildService - Banshee
enabled=1
autorefresh=1
baseurl=http://download.opensuse.org/repositories/Virtualization/openSUSE_11.4/
path=/
type=rpm-md
keeppackages=0


Yes somehow it has chanched. But be sure I do not edit this manually:)Ha!

o.K, I can´t see how to get bugfix for this directly.
Have you an idea/suggestion that is beside setting it back manually.
------------------------------------------------------------------------
May be it could be usefull to try a reproducing like:

installing a openSUSE11.4
bring it to the newest repros(you can get a list of my repros).
downgrade it with the original version(dvd:actualisation option)
upgrade it again and see how affect this zypper

But it would be a time consuming thing.

Yes, that would take too much time.

Do you have some older yast logs? /var/log/YaST2/y2log file is rotated, maybe some older /var/log/YaST2/y2log-*.gz contains log from the update. Please, attach all YaST logs (use 'save_y2logs' command).

Maybe the repositories were messed during repository update - there is a dialog where you enable/remove the old repositories. Maybe this step caused the problem...

"Maybe the repositories were messed during repository update - there is a dialog
where you enable/remove the old repositories. Maybe this step caused the
problem..."

A:Yes, I have thought of this.

Q:Do you have some older yast logs?

A: Yes, I have compressed the yast2 logfolder with dolphin and not with the script.Hope that do it also.

Created attachment 442664 [details]
the yast2 logfolder

Unfortunately the logs were rotated, the oldest (installation) logs were deleted to save disk space :-(

Do you remember what exactly you did during the upgrade? Esp. related to the old repositories so we could potentially reproduce the problem.

Sorry, but that is to long ago.

I got here two older zypper files. I upload it.

Created attachment 444580 [details]
old zypper

Unfortunately zypper logs do not help as the change was done by YaST.

Anyway, I'll try reproducing the problem next time I do an upgrade...

I haven't seen any issue similar to this. Moreover the installer has been modified in Factory/13.2 to apply the repository changes immediately (so if something messed up the repos later it should not happen anymore).

So I suppose it was fixed (indirectly).