Is using "updates-testing-" repository for at single package possible?

[Max Andersen]

Hi everyone,

I installed a package from "updates-testing" repository, but I noticed that it doesn't get updated from "updates-testing" repository, moving forward, when the system is configured to only use stable repository in general. Even if I used the parameter/option "enablerepo" it is only for the command and not for the lifetime of the package install. That kinda breaks it for me.

I am curious if it is possible to have 1 package that is using the "updates-testing" repository and the rest using the stable one?

Thanks for any feedback.
Sincerely
Max

[Samuel Sieb]

On 6/22/19 10:39 PM, Max Andersen via users wrote:
> I am curious if it is possible to have 1 package that is using the "updates-testing" repository and the rest using the stable one?

According to the docs, it looks like you can do that.  Edit the 
/etc/yum.repos.d/fedora-updates-testing.repo file.  In the 
[updates-testing] section, change enabled to 1 and add a line 
"includepkgs=packagename".  That means that you can't update any other 
package from there unless you add the --disableexcludes option to the 
dnf command line.

[Max Andersen]

Hi Samuel,

Thank you for your answer. That might be exactly what I'm looking for. You describe the catch 22 nicely. I believe that if I install a package from testing I need it to be updated, of course. I won't get that unless I also put it in the name of the package in the repository.

Shouldn't the default be, that if I install a package from any repository, it should automatically be updated from that repository, regardless of which was used?

Thank you very much for your help. Whare are thos docs, by the way? I haven't been able to find them

Sincerely
Max

[Joe Zeff]

On 06/23/2019 11:33 AM, Max Andersen via users wrote:
> Shouldn't the default be, that if I install a package from any repository, it should automatically be updated from that repository, regardless of which was used?

No.  Once packages have received enough karma, they're moved from 
updates-testing to updates.

[Samuel Sieb]

On 6/23/19 10:33 AM, Max Andersen via users wrote:
> Thank you for your answer. That might be exactly what I'm looking for. You describe the catch 22 nicely. I believe that if I install a package from testing I need it to be updated, of course. I won't get that unless I also put it in the name of the package in the repository.

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.
> Shouldn't the default be, that if I install a package from any repository, it should automatically be updated from that repository, regardless of which was used?

That's not how dnf (and yum before it) works.  A package will be updated 
from whichever repository has the latest version.  Or a specific version 
if you are specifying which one to install.
> Thank you very much for your help. Whare are thos docs, by the way? I haven't been able to find them

man dnf.conf

[Max Andersen]

> 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)
> 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.

Only thing regarding includepkgs was something about repoid.option for the option and setopt=.
 --setopt=<option>=<value>
              Override a configuration option from the configuration file. To override configuration options for repositories, use repoid.option for the <option>. Values for  configuration
              options  like  excludepkgs,  includepkgs,  installonlypkgs  and  tsflags are appended to the original value, they do not override it. However, specifying an empty value (e.g.
              --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.
Sincerely
Max
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.

[Samuel Sieb]

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.

[Ed Greshko]

On 6/24/19 1:06 PM, Samuel Sieb wrote:
> What's an "advisory update"?  dnf will get updates from any available repository
> regardless of which repository a package was initially installed from.

I'm guessing the meaning is updates which address a Common Vulnerabilities and Exposures
(CVE) such as the recent firefox update.  Or any other "security advisory".

I could understand why one would want an update ASAP and get it from updates-testing. 
But, there seems no value to tying a package to that repo unless you're going to always
want to test add karma as new versions become available.