Closed #199.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/199#event-1078065808___
Rpm-maint mailing list
Also, the only reason they can't be mixed is because on most RPM systems, they
share `/usr/lib`. If they were in a sysroot-style FHS or Debian-style FHS, that
would not be the case.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on
It wouldn't necessarily matter one way or the other, as the system rpm is
installing into the chroot, so it would be outside of the personality scope,
wouldn't it?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hmm. Seems like rpm doesn't use the --root argument when it searches for the
platform file. I wonder if this is a bug or not.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@mlschroe Unlike obs-build, mock uses the host's `rpm` and `dnf` to actually
build packages, so the host needs to allow it.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
That's more in @xsuchy's domain. But as far as I know, mock uses
`personality(2)` syscall to set target arch, and without the commit to declare
compat, rpm bombs out saying that the packages are for a different architecture.
--
You are receiving this because you are subscribed to this thread.
But if you can't mix them then they should not be marked as "compat". Wouldn't
it be better to declare the system as "armv7l" via /etc/rpm/platform or
something like that? Dunno if 'mock' supports that, though.
--
You are receiving this because you are subscribed to this thread.
Reply to this
Note that technically you cannot mix armsfp with armhfp packages as they have
different libc ABIs. I'm not sure if there is a better way to do this in RPM,
though.
As it is, though, at least the first commit in this PR is needed regardless,
since it fixes the arch compatibility tree changes
