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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> 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. 
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux