On 6/23/19 9:56 PM, Max Andersen via users wrote:
> 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
> eventually.
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
configuration file)
Well, it will also update that package from any other repo if possible,
but that's the only package it will update from updates-testing.
> man dnf.conf
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.
That's not the right one. I pointed to the "dnf.conf" man page.
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.
What's an "advisory update"? dnf will get updates from any available
repository regardless of which repository a package was initially
installed from.