On 6/23/19 10:33 AM, Max Andersen via users wrote:
Not sure what you're saying here. Which repository? If you install a
package, it will get updated if it's available in a repository.
Packages from updates-testing end up in the regular updates repository
I want to lock a specific package to use the updates-testing repository. Not only for one
release, but all coming releases for that package. I believe your first post did that,
with some caveats(manually need to allow other packages to be installed using a
Using man dnf or man 8 dnf I couldn't find what I was looking for, regarding
includepkgs, but I'm thankful for your initial answer that probably solves it.
Only thing regarding includepkgs was something about repoid.option for the option and
Override a configuration option from the configuration file. To override
configuration options for repositories, use repoid.option for the <option>. Values
options like excludepkgs, includepkgs, installonlypkgs and tsflags are
appended to the original value, they do not override it. However, specifying an empty
--setopt=tsflags=) will clear the option.
I hope I now always will get the mentioned package from the updates-testing, whenever
there is a release of that package, while the rest is getting updates from stable.
Thank you very much for your time.
p.s. basic understanding. My thoughts was that if I install package from updates-testing,
I should always get package updates for that package through update-testing, but if I
install an "advisory" thorugh update-testting, It's only that single
advisory update and it should not break the normal stable upgrading of that package.