On 6/29/20 12:14 AM, Daniel Mach wrote: > I think it's related to modularity as suggested by James. > If a module stream is active (enabled or default), it hides all non-module > packages with the same name or Provides. > See: > https://dnf.readthedocs.io/en/latest/modularity.html#package-filtering > > > Following config change should make your packages visible again: > [nginx-mainline-local] > ... > module_hotfixes=1
i -- destroyed/recreated the repo -- rebuilt rpm db -- added the > [nginx-mainline-local] > module_hotfixes=1 and -- increased the priority of my local repo from default/99 -> 90 some combination of the above did the trick. i can now see/install-from my packages. i don't know yet specifically what 'modularity' conflict might have been causing a problem. i did see that if i do _not_ raise the local repo priority, even though 'my' nginx pkg is versioned "1.19.0", the system finds, and displays only the system available "1.18.0". i _thought_ that higher-version would automatically get selected, even in the case of same (=default) repo priorities. i'll poke around some more, to figure out the specific gotchas. in any case, it WORKSFORNOW. thx, all! now, to wait for needed COPR fixes and push this all there ... _______________________________________________ buildsys mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]
