[Bug 1181734] New: "1 Click install" adding _a_lot_ of repositories
http://bugzilla.opensuse.org/show_bug.cgi?id=1181734 Bug ID: 1181734 Summary: "1 Click install" adding _a_lot_ of repositories Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: dfaggioli@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- So, maybe there is a good reason for this (in which case, sorry for the noise), but I do not understand why, when using "1 click install" from software.opensuse.org a lot of repositories are added, much more than the one(s?) needed for installing the package that one is trying to install. As an example, if I look for the "megasync" package and then follow the "1 click install" procedure, I end up with the following repos: https://download.opensuse.org/repositories/devel:/languages:/go/openSUSE_Fac... (devel:languages:go) https://download.opensuse.org/repositories/home:/Dead_Mozay/openSUSE_Tumblew... (home:Dead_Mozay) https://download.opensuse.org/repositories/openSUSE:/Factory/snapshot/ (openSUSE:Factory) https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/dod/ (openSUSE:Tumbleweed) https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/dod_debug/ (openSUSE:Tumbleweed) https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ (openSUSE:Tumbleweed) https://download.opensuse.org/repositories/utilities/openSUSE_Factory/ (utilities) They show up like this, in `zypper lr`: 5 | home_dfaggioli_branches_home_megamaced | Branch project for package rtl8821ce (openSUSE_Tumbleweed) | Yes | (r ) Yes | No 6 | https-download.opensuse.org-054a68d6 | openSUSE:Factory | Yes | (r ) Yes | Yes 7 | https-download.opensuse.org-27713afa | utilities | Yes | (r ) Yes | Yes 8 | https-download.opensuse.org-5f66b0a9 | devel:languages:go | Yes | (r ) Yes | Yes 9 | https-download.opensuse.org-7cfbaf44 | openSUSE:Tumbleweed | Yes | ( p) Yes | Yes 10 | https-download.opensuse.org-941670e8 | openSUSE:Tumbleweed | Yes | (r ) Yes | Yes 11 | https-download.opensuse.org-966896f6 | openSUSE:Tumbleweed | Yes | ( p) Yes | Yes 12 | https-download.opensuse.org-cb85059b | home:Dead_Mozay | Yes | (r ) Yes | Yes If, on the other hand, go to "Expert download" and click on "Add repository and install manually", these are the instructions: zypper addrepo https://download.opensuse.org/repositories/home:Dead_Mozay/openSUSE_Tumblewe... zypper refresh zypper install megasync And, following them, the package installs and work. So, why is it that the "1 click" procedure gives me a bunch of Factory repos, that may potentially update (and even break) a lot of other packages? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1181734 http://bugzilla.opensuse.org/show_bug.cgi?id=1181734#c1 --- Comment #1 from Dario Faggioli <dfaggioli@suse.com> --- (In reply to Dario Faggioli from comment #0)
So, why is it that the "1 click" procedure gives me a bunch of Factory repos, that may potentially update (and even break) a lot of other packages?
In fact, if I start a `zypper dup`, here's what I get: bolt openSUSE -> obs://build.opensuse.org/devel:languages:go calcurse openSUSE -> obs://build.opensuse.org/utilities calcurse-lang openSUSE -> obs://build.opensuse.org/utilities cdda2wav openSUSE -> obs://build.opensuse.org/utilities cdrecord openSUSE -> obs://build.opensuse.org/utilities cpuid openSUSE -> obs://build.opensuse.org/utilities fdupes openSUSE -> obs://build.opensuse.org/utilities And more. That is only if I enable and allow vendor changes... which I want to, because I have legitimate (like, added by myself, voluntarily) external repos. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1181734 http://bugzilla.opensuse.org/show_bug.cgi?id=1181734#c3 --- Comment #3 from Dario Faggioli <dfaggioli@suse.com> --- Ok, thanks for all these logs and info. From what I can tell after having a look at them, I am now even more convinced that this is another instance of the same underlying problem that was reported here: https://lists.xenproject.org/archives/html/xen-devel/2020-10/msg01561.html In particular, the fact that there are all those vCPUs with the minimum possible amount of credits (visible in `xl debug-keys r` output) is something that really puzzles me since a while, and that I am trying to figure out. So, "procedural" question: if I produce debug patchs, will you be able to build a version of Xen with them applied and give them a test? Alternatively, I can try to produce test RPM Xen packages for your distro. Would that be fine, and which one do you prefer? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1181734 http://bugzilla.opensuse.org/show_bug.cgi?id=1181734#c4 --- Comment #4 from Dario Faggioli <dfaggioli@suse.com> --- Err... sorry! Wrong window when commenting :-( (In reply to Dario Faggioli from comment #3)
Ok, thanks for all these logs and info.
From what I can tell after having a look at them, I am now even more convinced that this is another instance of the same underlying problem that was reported here:
https://lists.xenproject.org/archives/html/xen-devel/2020-10/msg01561.html
In particular, the fact that there are all those vCPUs with the minimum possible amount of credits (visible in `xl debug-keys r` output) is something that really puzzles me since a while, and that I am trying to figure out.
So, "procedural" question: if I produce debug patchs, will you be able to build a version of Xen with them applied and give them a test?
Alternatively, I can try to produce test RPM Xen packages for your distro.
Would that be fine, and which one do you prefer?
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1181734 http://bugzilla.opensuse.org/show_bug.cgi?id=1181734#c5 --- Comment #5 from Dario Faggioli <dfaggioli@suse.com> --- (In reply to Fabian Vogt from comment #2)
The .ymp file is generated by OBS and contains all repos in the build path leading up to the distribution. So home:Dead_Mozay, devel:languages_go and utilities are definitely necessary. The "Expert instructions" only work if the other two repos are added as well, otherwise it leads to inconsistencies.
Well... In this very case at least, just adding home:Dead_Mozay is enough for the package to install and work fine, but maybe it's just a coincidence.
The four repos for TW are a bug, they're part of the distro in OBS and need to be filtered out.
Reassigning to the build service.
Ok, cool. Thanks -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1181734 http://bugzilla.opensuse.org/show_bug.cgi?id=1181734#c8 --- Comment #8 from Adrian Schr�ter <adrian.schroeter@suse.com> --- these three openSUSE:Factory/snapshot openSUSE:Tumbleweed/standard openSUSE:Tumbleweed/dod are mapped to the same URL meanwhile, so the list should be shorter. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com