software-o-o
software-o-o copied to clipboard
do not addrepo system repos
Manual download: do not tell the operator to addrepo system repos (Factory, Tumbleweed or Leap)!
Fixes bsc#1185917.
- [ ] I've included before / after screenshots or did not change the UI
I'm curious why not all of SLE, but SLE 15 specifically, though that's mostly a question to @lkocman, since it was his suggestion
I'm curious why not all of SLE, but SLE 15 specifically, though that's mostly a question to @lkocman, since it was his suggestion
SLE doesn't rebuild packages each release, for example the last time dbus-1 was branched was in an update to SLE-15-SP1 so currently SLE-15-SP2 / SP3 / SP4 will all get the dbus-1 package from that repo. This means that if I do a security update and fix it in SUSE:SLE-15SP1:Update (or whatever it is) that fix will automatically be pulled into all currently supported products including Leap 15.3, SLE, SLE LTSS and any other products SUSE is building.
Possibly another question here is does software.o.o know that the latest official version of dbus-1 actually comes from SUSE:SLE-15SP1:Update, if it doesn't know that then it wont find it and its not an issue.
Keep in mind, all this PR does is remove a zypper addrepo
line, which isn't really related to how software-o-o does anything, but how it instructs people to add repositories. Let me word this differently, we already figured out that a Tumbleweed user will not want to add a SLE 15 repo, will a Tumbleweed user want to add a SLE repo instead?
This will just remove it from the official repos? If it's also the community and experimental ones then i don't agree.
This will just remove it from the official repos? If it's also the community and experimental ones then i don't agree.
This is not even that part of code. This relates to the download pages. It will remove reference to files that don't actually exist, official .repo files.