https://bugzilla.suse.com/show_bug.cgi?id=1200446 https://bugzilla.suse.com/show_bug.cgi?id=1200446#c22 --- Comment #22 from Jens Mozdzen <jens.mozdzen@suse.com> --- Could you introduce an installation-time flag that could be set by the admin (or rather the AutoYaST file, in the reported case) with a "do not add repositories" semantics? If someone sets this flag, it's that one's responsibility to make sure all required repositories are available. If that flag were introduced via some wrapper that you ask everyone to use, then this wrapper could also record all blocked "add repository" attempts and report these in the installation logs. This would help in debugging issues if the "admin" (the one setting the "don't add repositories" flag) messed up the extra repository setup. Potentionally the "wrapper" could be "zypper", if that's what every RPM script is using to add repositories. Yes, indeed, the wrapper would need to be able to distinguish between repositories added by the installation environment, vs. those added by RPM scripts - if the installation environment does use the same mechanism to update the repository list. But even then, it could be handled in a manner that the installation env sets the flag *after* having set up all "manual" repositories, blocking only further updates. -- You are receiving this mail because: You are on the CC list for the bug.