Hello,
I've just discovered a rather strange glitch with koji, used for
internal builds.
I've set it up by following the wiki instructions, and it seems to work
pretty well, but I've found out a strange behaviour.
I've set up a build tag (something like myproject-build) for arch x86_64
only, and I've added some externals repo to it (notably
centos-x86_64-updates and centos-x86_64-os).
Centos/RHEL (not sure about Fedora) does something tricky BTW: on 64 bit
systems, some packages (notably glibc and other low-level system
packages) are installed for both supported archs (x86_64 and i386). But
the koji "merged" repository xml only includes x86_64 packages; this is
a problem when trying to build some packages explicitly relying on the
presence of such i386 version.
Also, I sometimes use the koji repo on testing machines to fetch the
latest version of my development packages along with os deps. Even tough
mash is probably the best tool for such job, it was quite useful, but
this is impossible when glibc updates happen -> trying to upgrade the 64
bit glibc version but retaining the old version for 32 bit generates a
rpm conflict.
Any clue? Is such behaviour intentional?
Thanks in advance.
--
Alan Franzoni
contact me at public(a)[mysurname].eu