[CentOS-devel] CR repo messes ctdb package deps badly

Tue Jul 2 18:04:49 UTC 2019
lejeczek <peljasz at yahoo.co.uk>


On 02/07/2019 15:13, Trevor Hemsley wrote:
> On 02/07/2019 15:09, lejeczek via CentOS-devel wrote:
>> true, but still, it being messy to such an extent (when with CR) that
>> different archs being chained together, must be something in involved
>> rpms deps, no?
> CR has nothing whatsoever to do with this. You enabled fasttrack and
> installed packages from there. Now you've disabled it and it trying to
> install things from base/updates that require matching package versions
> from there that do not exist. They're in fasttrack.
>
> CR has been empty since 7.6 was released in early December. If you're
> seeing any mentions of it then it will be as @cr which means that that
> was where the packages came from when you installed them. The 7.5 CR
> content was then merged into the 7.6 base repo so that's where those
> versions are now. CR has nothing in it.
>
> Trevor
cr or no cr if this was purely a different versions issue
then package would/should downgrade/upgrade to whichever
version is best available.
Thus, cr aside and question of why deps want to pull
different arch, on a system which is purely x86_64 and ctdb
is x86_64 too, remains.
Even with fasttrack disabled, package & deps should get
upgraded or disabled and which one should be determined by
the logic of yum+spec, no?
Maybe it still is an issue, though not related to
CR/fasttrack but worth investigating?