Luke Shumaker wrote:
On Tue, 20 Mar 2018 16:51:49 -0400,
Andreas Grapentin wrote:
archlinux32 is building their own arch=(any) packages, which means
they
can't share the same cachedir as the x86_64 built -any packages.
This
patch adds a separate cachedir for each CARCH in librechroot, which
should solve the signature issues we have seen in libremakepkg.
But we don't import arch=(any) packages from archlinux32 anymore, do
we?
Actually, I don't think we import arch=(any) packages from ALARM
anymore either.
right, unless it's an original package.
more precisely, Arch's arch=(any) packages may override
existing ALARM or Arch32 pkgnames -- they are given priority
and all architectures are meant to use archlinux-keyring.
i don't expect this scenario to surface often in practice,
since both ALARM and Arch32 follow Arch, not the other way
around.
on the other hand, ALARM and Arch32's arch=(any) packages aren't
allowed to override Arch's arch=(any) stuff, nor each other's.
this is the relevant code:
https://git.parabola.nu/packages/dbscripts.git/tree/db-import-pkg?id=78fd5a0ca15cedc369ffd6c8035fd573ca253d76#n124
https://git.parabola.nu/packages/dbscripts.git/tree/db-import-pkg?id=78fd5a0ca15cedc369ffd6c8035fd573ca253d76#n304
--
Isaac David
GPG: 38D33EF29A7691134357648733466E12EC7BA943
Ring: c8ba5620e080bef9470efb314c257304ff9480f5
Tox:
0C730E0156E96E6193A1445D413557FF5F277BA969A4EA20AC9352889D3B390E77651E816F0C
_______________________________________________
Dev mailing list
Dev@lists.parabola.nu
https://lists.parabola.nu/mailman/listinfo/dev