https://bugzilla.suse.com/show_bug.cgi?id=1214135 https://bugzilla.suse.com/show_bug.cgi?id=1214135#c12 --- Comment #12 from Bill Wayson <bill_wayson@yahoo.com> --- (In reply to Michael Andres from comment #11) @Michael, so that you understand my abilities better, while my career was in IT, I am more of a user now than I am a developer/programmer. I can respond to requests well, but I don't want to provide what might be random noise to those troubleshooting this.
@Bill, I'll try to figure out what "yast2 repositories" does. Using https can not cause the issue here, but maybe the way "yast2 repositories" modifies the repo files. After reading this, I copied all of the /etc/zypp/repos.d/openSUSE\:*.repo files to a location outside of /etc, and then used "yast2 repositories" to modify one (and only one) of the openSUSE service repos (repo-oss). I simply changed "http" in the URI to "https". Interestingly (to me):
1. That repo file had these lines added to it: path=/ type=rpm-md keeppackages=0 and this line deleted: service=openSUSE 2. All of the other five openSUSE:*.repo files were touched. If the repo was enabled, these lines were added: type=rpm-md keeppackages=0 and no lines were deleted. IF the repo was disabled, this line was added: keeppackages=0 and, again, no lines were deleted. Finally, now, running zipper dist-upgrade gives me the error again: Adding repository 'repo-oss' ..........................................................................[error] Unexpected exception. [openSUSE:repo-oss|http://cdn.opensuse.org/tumbleweed//repo/oss] Repository already exists. Please file a bug report about this. See http://en.opensuse.org/Zypper/Troubleshooting for instructions. I will run the commands at the end of your comment 4 to fix this error. Also, this explains to me why, after my original report, the openh264 repo was the only repo tagged as belonging in the openSUSE service. I had not modified that repo because the original, non-service repo would not work with the https protocol, so I figured the service-tagged repo wouldn't work either with https.
In case the yast logs of running "yast2 repositories" are still available on your system, please attach them.
If https is a must-have for you, you'd need to edit the service definition (/usr/share/zypp/local/service/openSUSE/repo/repoindex.xml) and lock the openSUSE-repos-Tumbleweed package, so it does not update the repoindex.xml. Or create your own service using the repoindex.xml as a template. Thanks for this. https is not a must-have for me. It is more of a "best
I will attach both the old log file (y2log-2.gz) -- I am pretty sure it is the one with the original issue -- and the current log (y2log-0.gz). I will also cogitate the middle part of your comment 11 to understand it better. practice" thing. Hope this helps -- let me know if you'd like something else. -- You are receiving this mail because: You are on the CC list for the bug.