Learn more about these different git repos.
Other Git URLs
tomcat-native is used by Java appservers such as Tomcat and JBoss, and the arch of the Java runtime and tomcat-native need to match. There's no ix86 Java runtime in the x86_64 repo so there's no need to have ix86 tomcat-native there either.
What's pulling it in?
Nothing AFAIK. It's a library only package, perhaps a tool somewhere made a decision based on that.
{{{ $ repoquery --repoid=rawhide --whatrequires --alldeps tomcat-native tomcat-native-0:1.1.16-3.fc11.x86_64 tomcat-native-0:1.1.16-3.fc11.i586
$ repoquery --repoid=rawhide --list tomcat-native.x86_64 /usr/lib64/libtcnative-1.so /usr/lib64/libtcnative-1.so.0 /usr/lib64/libtcnative-1.so.0.1.16 /usr/share/doc/tomcat-native-1.1.16 /usr/share/doc/tomcat-native-1.1.16/CHANGELOG.txt /usr/share/doc/tomcat-native-1.1.16/LICENSE /usr/share/doc/tomcat-native-1.1.16/NOTICE.txt }}}
The libraries in a standard path is what makes our tools think this is suitable for multilib. What are those libraries used for?
Native HTTP etc connectors by Tomcat, JBoss etc. They are in the standard lib path because that's where those appservers expect to find them.
Added in git; the assumption is that this isn't causing any actual issues, so it's unlikely to be pushed back to older releases any time soon.
tomcat-native-1.1.16-3.fc11.i586.rpm is still in the x86_64 repo, shouldn't it be gone already?
It was changed upstream in mash, it'll take effect next time we bump mash, which will likely be shortly after beta.
Login to comment on this ticket.