[15.6] openSUSE-release-15.6-lp156.408.1.x86_64 policy change???
openSUSE-release-15.6-lp156.408.1.x86_64: # rpm -ql openSUSE-release | grep repo /etc/zypp/repos.d/repo-backports-debug-update.repo /etc/zypp/repos.d/repo-backports-update.repo /etc/zypp/repos.d/repo-sle-debug-update.repo /etc/zypp/repos.d/repo-sle-update.repo # Two of these replicate existing repos. Two are unneeded/undesired (as all repos that are named "repo*.repo" are undesired here[1]). # ls -Ggl /etc/zypp/repos.d/*.repo -rw-rw-r-- 1 185 Jan 1 00:00 /etc/zypp/repos.d/FCL-leap.repo -rw-r--r-- 1 219 Jul 15 2023 /etc/zypp/repos.d/KDE3.repo -rw-r--r-- 1 153 Jul 15 2023 /etc/zypp/repos.d/NonOSS.repo -rw-r--r-- 1 143 Jul 15 2023 /etc/zypp/repos.d/OSS.repo -rw-r--r-- 1 129 Jul 15 2023 /etc/zypp/repos.d/Update.repo -rw-r--r-- 1 239 Jul 15 2023 /etc/zypp/repos.d/UpdateBP.repo -rw-r--r-- 1 145 Jul 15 2023 /etc/zypp/repos.d/UpdateNonOSS.repo -rw-r--r-- 1 135 Jul 15 2023 /etc/zypp/repos.d/UpdateSLE.repo -rw-r--r-- 1 192 Feb 8 2023 /etc/zypp/repos.d/openh264.repo # zypper lr Repository priorities are without effect. All enabled repositories share the same priority. # | Alias | Enabled | GPG Check | URI --+--------------+---------+-----------+------------------------------------------------------------------ 1 | FCL-leap | Yes | ( p) Yes | http://silk.apana.org.au/rpm-opensuse15-unstable-dev 2 | KDE3 | Yes | (r ) Yes | http://download.opensuse.org/repositories/KDE:/KDE3/15.6/ 3 | NonOSS | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.6/repo/non-oss/ 4 | OSS | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.6/repo/oss/ 5 | Update | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/oss/ 6 | UpdateBP | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/backports/ 7 | UpdateNonOSS | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/non-oss/ 8 | UpdateSLE | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/sle/ 9 | openh264 | Yes | (r ) Yes | http://codecs.opensuse.org/openh264/openSUSE_Leap/ # This seems may be a significant policy change for a "minor" release version, especially since this didn't first appear in TW. What's up that an admin can no longer choose what repos to include, or what to call them? [1] My normal routine is to run the following script as prequel to zypper up and to zypper dup: #!/bin/bash # /usr/local/zypstart [ -e /etc/zypp/repo*.repo ] && rm /etc/zypp/repos.d/repo*.repo 2> /dev/null zypper -v in --download-in-advance rpm zypper libzypp libsolv-tools openSUSE-release coreutils filesystem [ -e /etc/zypp/repo*.repo ] && rm /etc/zypp/repos.d/repo*.repo 2> /dev/null # -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Hello Felix, did you consider using *openSUSE-repos(-Leap), you'd have
a better changelog and repository change awareness?
Aside from that I'm unaware of any repository priority related changes
in 000package-groups/000release-packages.
All of the repos on my system have prio 99 (openSUSE-repos).
[0] https://github.com/openSUSE/openSUSE-repos
Lubos
On Fri, May 24, 2024 at 7:21 AM Felix Miata
openSUSE-release-15.6-lp156.408.1.x86_64: # rpm -ql openSUSE-release | grep repo /etc/zypp/repos.d/repo-backports-debug-update.repo /etc/zypp/repos.d/repo-backports-update.repo /etc/zypp/repos.d/repo-sle-debug-update.repo /etc/zypp/repos.d/repo-sle-update.repo # Two of these replicate existing repos. Two are unneeded/undesired (as all repos that are named "repo*.repo" are undesired here[1]). # ls -Ggl /etc/zypp/repos.d/*.repo -rw-rw-r-- 1 185 Jan 1 00:00 /etc/zypp/repos.d/FCL-leap.repo -rw-r--r-- 1 219 Jul 15 2023 /etc/zypp/repos.d/KDE3.repo -rw-r--r-- 1 153 Jul 15 2023 /etc/zypp/repos.d/NonOSS.repo -rw-r--r-- 1 143 Jul 15 2023 /etc/zypp/repos.d/OSS.repo -rw-r--r-- 1 129 Jul 15 2023 /etc/zypp/repos.d/Update.repo -rw-r--r-- 1 239 Jul 15 2023 /etc/zypp/repos.d/UpdateBP.repo -rw-r--r-- 1 145 Jul 15 2023 /etc/zypp/repos.d/UpdateNonOSS.repo -rw-r--r-- 1 135 Jul 15 2023 /etc/zypp/repos.d/UpdateSLE.repo -rw-r--r-- 1 192 Feb 8 2023 /etc/zypp/repos.d/openh264.repo # zypper lr Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Enabled | GPG Check | URI --+--------------+---------+-----------+------------------------------------------------------------------ 1 | FCL-leap | Yes | ( p) Yes | http://silk.apana.org.au/rpm-opensuse15-unstable-dev 2 | KDE3 | Yes | (r ) Yes | http://download.opensuse.org/repositories/KDE:/KDE3/15.6/ 3 | NonOSS | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.6/repo/non-oss/ 4 | OSS | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.6/repo/oss/ 5 | Update | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/oss/ 6 | UpdateBP | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/backports/ 7 | UpdateNonOSS | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/non-oss/ 8 | UpdateSLE | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/sle/ 9 | openh264 | Yes | (r ) Yes | http://codecs.opensuse.org/openh264/openSUSE_Leap/ #
This seems may be a significant policy change for a "minor" release version, especially since this didn't first appear in TW. What's up that an admin can no longer choose what repos to include, or what to call them?
[1] My normal routine is to run the following script as prequel to zypper up and to zypper dup: #!/bin/bash # /usr/local/zypstart [ -e /etc/zypp/repo*.repo ] && rm /etc/zypp/repos.d/repo*.repo 2> /dev/null zypper -v in --download-in-advance rpm zypper libzypp libsolv-tools openSUSE-release coreutils filesystem [ -e /etc/zypp/repo*.repo ] && rm /etc/zypp/repos.d/repo*.repo 2> /dev/null # -- Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
-- Best regards Luboš Kocman openSUSE Leap Release Manager
Lubos Kocman composed on 2024-05-24 11:38 (UTC+0200):
Felix Miata wrote:
openSUSE-release-15.6-lp156.408.1.x86_64: # rpm -ql openSUSE-release | grep repo /etc/zypp/repos.d/repo-backports-debug-update.repo /etc/zypp/repos.d/repo-backports-update.repo /etc/zypp/repos.d/repo-sle-debug-update.repo /etc/zypp/repos.d/repo-sle-update.repo
Why does the release file contain those four, and only those four?
# Two of these replicate existing repos. Two are unneeded/undesired (as all repos that are named "repo*.repo" are undesired here[1]). # ls -Ggl /etc/zypp/repos.d/*.repo -rw-rw-r-- 1 185 Jan 1 00:00 /etc/zypp/repos.d/FCL-leap.repo -rw-r--r-- 1 219 Jul 15 2023 /etc/zypp/repos.d/KDE3.repo -rw-r--r-- 1 153 Jul 15 2023 /etc/zypp/repos.d/NonOSS.repo -rw-r--r-- 1 143 Jul 15 2023 /etc/zypp/repos.d/OSS.repo -rw-r--r-- 1 129 Jul 15 2023 /etc/zypp/repos.d/Update.repo -rw-r--r-- 1 239 Jul 15 2023 /etc/zypp/repos.d/UpdateBP.repo -rw-r--r-- 1 145 Jul 15 2023 /etc/zypp/repos.d/UpdateNonOSS.repo -rw-r--r-- 1 135 Jul 15 2023 /etc/zypp/repos.d/UpdateSLE.repo -rw-r--r-- 1 192 Feb 8 2023 /etc/zypp/repos.d/openh264.repo # zypper lr Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Enabled | GPG Check | URI --+--------------+---------+-----------+------------------------------------------------------------------ 1 | FCL-leap | Yes | ( p) Yes | http://silk.apana.org.au/rpm-opensuse15-unstable-dev 2 | KDE3 | Yes | (r ) Yes | http://download.opensuse.org/repositories/KDE:/KDE3/15.6/ 3 | NonOSS | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.6/repo/non-oss/ 4 | OSS | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.6/repo/oss/ 5 | Update | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/oss/ 6 | UpdateBP | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/backports/ 7 | UpdateNonOSS | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/non-oss/ 8 | UpdateSLE | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/sle/ 9 | openh264 | Yes | (r ) Yes | http://codecs.opensuse.org/openh264/openSUSE_Leap/ #
This seems may be a significant policy change for a "minor" release version, especially since this didn't first appear in TW. What's up that an admin can no longer choose what repos to include, or what to call them?
[1] My normal routine is to run the following script as prequel to zypper up and to zypper dup: #!/bin/bash # /usr/local/zypstart [ -e /etc/zypp/repo*.repo ] && rm /etc/zypp/repos.d/repo*.repo 2> /dev/null zypper -v in --download-in-advance rpm zypper libzypp libsolv-tools openSUSE-release coreutils filesystem [ -e /etc/zypp/repo*.repo ] && rm /etc/zypp/repos.d/repo*.repo 2> /dev/null #
Hello Felix, did you consider using *openSUSE-repos(-Leap),
Ill fit here: # zypper ll | grep repo 43 | openSUSE-repo* | package | (any) | # grep \$releasever /etc/zypp/repos.d/*repo # ls -1 /etc/zypp/repos.d/*rep* | wc -l 58 # ls -1 /etc/zypp/repos.d/*repo | wc -l 9 # ls -1 /etc/zypp/repos.d/[a-z]*repo /etc/zypp/repos.d/openh264.repo #
you'd have a better changelog and repository change awareness?
How can you know yours would be better than mine? Installations I currently have are 16 15.6, 30 15.5, 31 64 bit TW and 15 32bit TW, all on hardware, about 45 working multiboot PCs. I developed my own repo strategy shortly after implementing a LAN server nearly two decades ago, before "openSUSE" was born. A master set of repos lives on the server. If and when the content of a repo file needs a change, or a new repo is desired, it happens first on the server. My awareness is maximized by the matching of each individual installation's repo files matching the name *&* timestamp on the server. Repo names and aliases are kept relatively short, in part in order for repo lists to have minimal need to line wrap. On my 100 or so openSUSE installations, desired repo files are copied from the server. What follows is a subset of some of these files:
ls -gGl /etc/zypp/repos.d/OSS* -rw-r--r-- 1 147 Jun 7 2023 OSS.repo-gwdg -rw-r--r-- 1 138 Oct 11 2023 OSS.repoC -rw-r--r-- 1 143 Jun 7 2023 OSS.repoD -rw-r--r-- 1 159 Jun 7 2023 OSS.repoLmia
Whichever OSS repo I wish to use is copied to end in .repo. To disable a repo, the copy ending in .repo is removed. When I wish a different URL used for any particular repo, it happens quickly via filename. If a repo with a deviant name appears, I know it wasn't me that put it there. Various scripts here look for repo*.repo and if found deletes them. If any installation's repo's timestamp differs from the server, it's cause for concern. One or more visits to /etc/zypp/repos.d/ are part of most boots here that include a zypper up or zypper dup.
Aside from that I'm unaware of any repository priority related changes in 000package-groups/000release-packages.
All of the repos on my system have prio 99 (openSUSE-repos).
Few of my repo files have any priority line.
Fine for typical users, of which I am not. :-D -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On Fri, May 24, 2024 at 2:31 PM Felix Miata
Lubos Kocman composed on 2024-05-24 11:38 (UTC+0200):
Felix Miata wrote:
openSUSE-release-15.6-lp156.408.1.x86_64: # rpm -ql openSUSE-release | grep repo /etc/zypp/repos.d/repo-backports-debug-update.repo /etc/zypp/repos.d/repo-backports-update.repo /etc/zypp/repos.d/repo-sle-debug-update.repo /etc/zypp/repos.d/repo-sle-update.repo
Why does the release file contain those four, and only those four?
https://build.opensuse.org/projects/openSUSE:Leap:15.6/packages/000release-p... # Install missing repositories to user's system, bsc#1186593 bsc#1186795 It was a quick fix and we've carried definitions since then. I'd prefer not to drop these only with the GMC build which we can expect very soon :-)
# Two of these replicate existing repos. Two are unneeded/undesired (as all repos that are named "repo*.repo" are undesired here[1]). # ls -Ggl /etc/zypp/repos.d/*.repo -rw-rw-r-- 1 185 Jan 1 00:00 /etc/zypp/repos.d/FCL-leap.repo -rw-r--r-- 1 219 Jul 15 2023 /etc/zypp/repos.d/KDE3.repo -rw-r--r-- 1 153 Jul 15 2023 /etc/zypp/repos.d/NonOSS.repo -rw-r--r-- 1 143 Jul 15 2023 /etc/zypp/repos.d/OSS.repo -rw-r--r-- 1 129 Jul 15 2023 /etc/zypp/repos.d/Update.repo -rw-r--r-- 1 239 Jul 15 2023 /etc/zypp/repos.d/UpdateBP.repo -rw-r--r-- 1 145 Jul 15 2023 /etc/zypp/repos.d/UpdateNonOSS.repo -rw-r--r-- 1 135 Jul 15 2023 /etc/zypp/repos.d/UpdateSLE.repo -rw-r--r-- 1 192 Feb 8 2023 /etc/zypp/repos.d/openh264.repo # zypper lr Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Enabled | GPG Check | URI --+--------------+---------+-----------+------------------------------------------------------------------ 1 | FCL-leap | Yes | ( p) Yes | http://silk.apana.org.au/rpm-opensuse15-unstable-dev 2 | KDE3 | Yes | (r ) Yes | http://download.opensuse.org/repositories/KDE:/KDE3/15.6/ 3 | NonOSS | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.6/repo/non-oss/ 4 | OSS | Yes | (r ) Yes | http://download.opensuse.org/distribution/leap/15.6/repo/oss/ 5 | Update | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/oss/ 6 | UpdateBP | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/backports/ 7 | UpdateNonOSS | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/non-oss/ 8 | UpdateSLE | Yes | (r ) Yes | http://download.opensuse.org/update/leap/15.6/sle/ 9 | openh264 | Yes | (r ) Yes | http://codecs.opensuse.org/openh264/openSUSE_Leap/ #
This seems may be a significant policy change for a "minor" release version, especially since this didn't first appear in TW. What's up that an admin can no longer choose what repos to include, or what to call them?
[1] My normal routine is to run the following script as prequel to zypper up and to zypper dup: #!/bin/bash # /usr/local/zypstart [ -e /etc/zypp/repo*.repo ] && rm /etc/zypp/repos.d/repo*.repo 2> /dev/null zypper -v in --download-in-advance rpm zypper libzypp libsolv-tools openSUSE-release coreutils filesystem [ -e /etc/zypp/repo*.repo ] && rm /etc/zypp/repos.d/repo*.repo 2> /dev/null #
Hello Felix, did you consider using *openSUSE-repos(-Leap),
Ill fit here: # zypper ll | grep repo 43 | openSUSE-repo* | package | (any) | # grep \$releasever /etc/zypp/repos.d/*repo # ls -1 /etc/zypp/repos.d/*rep* | wc -l 58 # ls -1 /etc/zypp/repos.d/*repo | wc -l 9 # ls -1 /etc/zypp/repos.d/[a-z]*repo /etc/zypp/repos.d/openh264.repo #
you'd have a better changelog and repository change awareness?
How can you know yours would be better than mine? Installations I currently have are 16 15.6, 30 15.5, 31 64 bit TW and 15 32bit TW, all on hardware, about 45 working multiboot PCs.
I meant compared to the changelog for definitions in 000release-packages or skelcd.
I developed my own repo strategy shortly after implementing a LAN server nearly two decades ago, before "openSUSE" was born. A master set of repos lives on the server. If and when the content of a repo file needs a change, or a new repo is desired, it happens first on the server. My awareness is maximized by the matching of each individual installation's repo files matching the name *&* timestamp on the server.
Repo names and aliases are kept relatively short, in part in order for repo lists to have minimal need to line wrap.
On my 100 or so openSUSE installations, desired repo files are copied from the server. What follows is a subset of some of these files:
ls -gGl /etc/zypp/repos.d/OSS* -rw-r--r-- 1 147 Jun 7 2023 OSS.repo-gwdg -rw-r--r-- 1 138 Oct 11 2023 OSS.repoC -rw-r--r-- 1 143 Jun 7 2023 OSS.repoD -rw-r--r-- 1 159 Jun 7 2023 OSS.repoLmia
Whichever OSS repo I wish to use is copied to end in .repo. To disable a repo, the copy ending in .repo is removed. When I wish a different URL used for any particular repo, it happens quickly via filename. If a repo with a deviant name appears, I know it wasn't me that put it there. Various scripts here look for repo*.repo and if found deletes them. If any installation's repo's timestamp differs from the server, it's cause for concern. One or more visits to /etc/zypp/repos.d/ are part of most boots here that include a zypper up or zypper dup.
Aside from that I'm unaware of any repository priority related changes in 000package-groups/000release-packages.
All of the repos on my system have prio 99 (openSUSE-repos).
Few of my repo files have any priority line.
Fine for typical users, of which I am not. :-D -- Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
-- Best regards Luboš Kocman openSUSE Leap Release Manager
Mr K: Having similar issues with my Leap 15.6 repos . . . as posted on this forum thread. https://forums.opensuse.org/t/leap-15-6-dup-brings-29-problem-questions-blac...
Hello Fritz,
I do see that the forum touches multiple topics, that's never a good
thing as it is super difficult to resolve such threads / issues.
These different issues from what Felix was describing. Felix was not
happy about (default) priority being the same for all openSUSE-repos.
@Fritz please open a bug for your dependency issues as long as the
dependency issues are from official repos and not OBS dev
projects/Packman.
And do not mix it with openSUSE-repos
https://en.opensuse.org/openSUSE:Submitting_bug_reports
The nvidia repo url path which was fixed as part of
https://bugzilla.suse.com/show_bug.cgi?id=1224185
Please make sure that you have the latest openSUSE-repos installed
(described in the bug).
Note at the end.
Just keep in mind that if you have openSUSE-repos and RIS managed you
should use zypper modifyrepo etc. instead of editing generated files
in /etc/zypp
Example here https://github.com/openSUSE/openSUSE-repos/blob/main/README.md#how-to-enable...
I summarized the situation about openSUSE-repos in
https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/D...
Hope it helps
On Sat, May 25, 2024 at 7:12 PM Fritz Hudnut
Mr K:
Having similar issues with my Leap 15.6 repos . . . as posted on this forum thread.
https://forums.opensuse.org/t/leap-15-6-dup-brings-29-problem-questions-blac...
-- Best regards Luboš Kocman openSUSE Leap Release Manager
Lubos Kocman via openSUSE Factory composed on 2024-05-27 12:57 (UTC+0200):
Felix was not happy about (default) priority being the same for all openSUSE-repos.
The thread's OP has nothing to do with repo priorities. The topic is a combination of repo duplication, and package management unconditionally adding new repos in a post-installation transaction. The only mention of priorities in my follow-up to your reply was my relative lack of use of repo priorities. Also, if you revisit my OP, you'll note total absence of repo files whose name includes more than one instance of string "repo". IOW, all repo names on my installations differ from defaults. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Lubos Kocman wrote:
Hello Fritz,
@Fritz please open a bug for your dependency issues as long as the dependency issues are from official repos and not OBS dev projects/Packman. And do not mix it with openSUSE-repos https://en.opensuse.org/openSUSE:Submitting_bug_reports
@Lubos: Thanks for the post back on it. The dependency issues were solved, once I got the repos straightened out thanks to @hui and @mrmazda . . . . My issue is I believe the same issue that Mrmazda is reporting, that my repos were somehow changed by the system, as I had a working Leap system for months and then suddenly repo errors were showing up causing dependency problems. I didn't try to edit my repos and then have it blow up on me and wonder why, etc. Then, compounding the problem, I couldn't get YaSt to make the suggested edits to my repos in the GUI and needed high level help to get the repos added back into my system. And now it seems to be "OK," . . . . Doing autopsy on it, it seems like a similar situation with repos happened to my Slow Roll install . . . running fine for some weeks and then suddenly . . . ER shell and "/" "not found," as it seemed like the repos were changing every couple of days??? I have been kicking around in linux for a fair amount of time and haven't seen this, "Your repos have been changed for your own protection" kind of a deal. I have edited my repos in ubuntu/debian to upgrade a system, but I know when that is happening and am aware that it has been done. And, I don't have to be checking wiki's to see what the latest repos for my installation should be. I set them up and that is that, done.
The nvidia repo url path which was fixed as part of https://bugzilla.suse.com/show_bug.cgi?id=1224185 Please make sure that you have the latest openSUSE-repos installed (described in the bug).
Yes, the nvidia/nouveau issue is "another problem" and one that keeps recurring, not sure if I have it "fixed" or waiting again for the next visit. I believe I did post to that bug report . . . .
Best regards
Luboš Kocman openSUSE Leap Release Manager
participants (3)
-
Felix Miata -
Fritz Hudnut -
Lubos Kocman