Hi Martin,<br><br><div class="gmail_quote">On Mon, Jul 25, 2011 at 9:02 PM, Martin Langhoff <span dir="ltr"><<a href="mailto:martin.langhoff@gmail.com" target="_blank">martin.langhoff@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Peter, Fedorans,<br>
<br>
I'm playing with test builds using F14 for arm. And I get strange<br>
errors of f14 python packages that depend on python 2.6. And yet, when<br>
I look at koji, it clearly has newer RPMs...<br>
<br>
So for example, see python-decorator:<br>
<a href="http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=7698" target="_blank">http://arm.koji.fedoraproject.org/koji/packageinfo?packageID=7698</a><br>
<br>
Right now, it lists<br>
python-decorator-3.2.0-2.fc14 pbrobinson 2011-07-23 10:55:56<br>
python-decorator-3.2.0-3.fc14 pbrobinson 2011-05-25 19:47:30<br>
<br>
The -3 package is newer, but was build earlier than the -2 package.<br>
Looking at the changelog, the -3 rev is where the Python 2.7 rebuild<br>
happened.<br>
<br>
Now if I grab the pkg list, it offers python-decorator-3.2.0-2.fc14<br>
<a href="http://arm.koji.fedoraproject.org/repos/dist-f14-build/latest/arm/pkglist" target="_blank">http://arm.koji.fedoraproject.org/repos/dist-f14-build/latest/arm/pkglist</a><br>
<br>
I've had similar problems with other Python packages. Anybody can help<br>
me understand why? Any fixes? Workarounds?<br>
<br></blockquote><div><br>Its a known problem. Mash (or what ever it is that generates the koji build repo) uses some very random criteria for tagging packages into the build repo. This is causing problems for noarch packages that are just imported by build-previous as opposed to rebuilt esp for python. The problem is that some of the packages, like the one you mention, were rebuilt/imported explicitly to get the build root for koji up to a F-14 level. It should hopefully just disappear once we have build-previous go to completion. The real fix it to add a check for the script to check if a later release is already in the tree.<br>
<br>Peter<br></div></div>