[Bug 1090505] New: An older version of openSUSE Tumbleweed did not show any updates because zypper repos of type "yast2" are not found (needs to be rpm-md)
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505 Bug ID: 1090505 Summary: An older version of openSUSE Tumbleweed did not show any updates because zypper repos of type "yast2" are not found (needs to be rpm-md) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening@forge.provo.novell.com Reporter: okurz@suse.com QA Contact: jsrain@suse.com CC: dimstar@opensuse.org, ma@suse.com Found By: --- Blocker: --- Created attachment 767940 --> http://bugzilla.opensuse.org/attachment.cgi?id=767940&action=edit y2logs including zypper.log showing errors and workarounds ## Observation On an older openSUSE Tumbleweed installation, originally from 2016, no available updates are shown since some time, I guess since the repo format of openSUSE Tumbleweed was changed to "rpm-md" by default?. Calling `zypper ref` reveals: ``` File '/content' not found on medium 'http://download.opensuse.org/tumbleweed/repo/oss/' ``` ## Problem The repo configuration file /etc/zypp/repos.d/repo-oss.repo is configured with "type=yast2". Changing that to "type=rpm-md" fixes this. Shouldn't that transformation have happened automatically? If not possible then I am not sure if announcements project-wide were enough. ## Further details See attached y2log files including the zypper.log which shows the errors on trying to refresh the repos as well as the fixed updated calls. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505#c1
Stephan Kulow
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505#c2
--- Comment #2 from Michael Andres
------------------------------------------------------------------- Wed Jul 12 17:06:14 CEST 2017 - ma@suse.de - repo refresh: Re-probe if the repository type changes (bsc#1048315) - version 16.14.0 (0)
Duplicate? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505#c3
Oliver Kurz
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505#c4
Michael Andres
So is it a duplicate of bug 1048315 ? Kinda, because I have libzypp 16.12.0-1.2 currently installed which is the old version before the fix
Yes. 16.14. will re-probe and detect that it's now rpm-md. *** This bug has been marked as a duplicate of bug 1048315 *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505#c5
Oliver Kurz
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505#c6
--- Comment #6 from Dominique Leuenberger
I think I made myself not clear. I reopen the bug and update the subject line. Can someone understand from the attached log files why the automatic update of packages did not work?
Was that machine EVER updated in the time since libzypp was updated until the product published as an rpm-md repo? We had a > 6 month gap to get users going. At one point we just had to 'move'. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505#c7
--- Comment #7 from Oliver Kurz
Was that machine EVER updated in the time since libzypp was updated until the product published as an rpm-md repo?
Apparently not and I think you did nothing wrong with the big enough time gap. I just wonder why the yast automatic online update did not do what I expected it to do. And I am even assuming I did something wrong configuring it but I do not understand what hence my kinq request for someone with better understanding of the yast+zypper logs can help me understand what went wrong. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505#c8
--- Comment #8 from Michael Andres
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505#c9
Oliver Kurz
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505
http://bugzilla.opensuse.org/show_bug.cgi?id=1090505#c10
J. Daniel Schmidt
Shouldn't that transformation have happened automatically?
No, why? YaST should not automatically modify the repos on a system. This is the task of the admin. YaST2 automatic_online_update is only made to run "zypper patch" (with some other parameters) via cron. It even skips interactive patches and the ones that require reboot of the system. The admin needs to make sure that an update repo is present. (at least that was the original aim when the YaST module was created - it might have changed over time). -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com