This package:
Name : spamassassin Version : 3.4.0 Release : 8.fc21 Architecture: ppc64 Install Date: (not installed) Group : Applications/Internet Size : 3892884 License : ASL 2.0 Signature : (none) Source RPM : spamassassin-3.4.0-8.fc21.src.rpm Build Date : Sun 31 Aug 2014 05:49:22 AM UTC Build Host : ppc-builder6.qa.fedoraproject.org Relocations : (not relocatable) Packager : Fedora Project Vendor : Fedora Project URL : http://spamassassin.apache.org/ Summary : Spam filter for email which can be invoked from mail delivery agents
was built with an RPM version which suffers from bug 1131960. This is not an immediate problem because primary is at release 9, so there will be yet another rebuild.
However, I was under the assumption that koji-shadow had an exception for certain packages like RPM, so that those would use the most recent version, and not the version required to reproduce the primary build. Is this not the case, or is something else going on here?
On Mon, 01 Sep 2014 21:02:20 +0200 Florian Weimer fweimer@redhat.com wrote:
This package:
Name : spamassassin Version : 3.4.0 Release : 8.fc21 Architecture: ppc64 Install Date: (not installed) Group : Applications/Internet Size : 3892884 License : ASL 2.0 Signature : (none) Source RPM : spamassassin-3.4.0-8.fc21.src.rpm Build Date : Sun 31 Aug 2014 05:49:22 AM UTC Build Host : ppc-builder6.qa.fedoraproject.org Relocations : (not relocatable) Packager : Fedora Project Vendor : Fedora Project URL : http://spamassassin.apache.org/ Summary : Spam filter for email which can be invoked from mail delivery agents
was built with an RPM version which suffers from bug 1131960. This is not an immediate problem because primary is at release 9, so there will be yet another rebuild.
However, I was under the assumption that koji-shadow had an exception for certain packages like RPM, so that those would use the most recent version, and not the version required to reproduce the primary build. Is this not the case, or is something else going on here?
unfortunately koji-shadow can do exact match, closest match (when a build is missing the closest newer is used) or manual substitutions for buildroot members. The substitutions could be used in this case, but right now it seems we are replicating primary including all errors. AFAIK all builds affected by the rpm bug were rebuild in primary, which means they will be later rebuild also on ppc (and others unless they manually replace the bad rpm builds), so we should be safe. Allowing to use the latest builds for selected packages in buildroots is already on our wish list for the next koji-shadow [1]
[1] https://fedoraproject.org/wiki/Architectures/KojiShadowNG
Dan
On 09/01/2014 09:41 PM, Dan Horák wrote:
unfortunately koji-shadow can do exact match, closest match (when a build is missing the closest newer is used) or manual substitutions for buildroot members. The substitutions could be used in this case, but right now it seems we are replicating primary including all errors. AFAIK all builds affected by the rpm bug were rebuild in primary, which means they will be later rebuild also on ppc (and others unless they manually replace the bad rpm builds), so we should be safe.
Thanks for the explanation. I agree that with more waiting, this should fix itself on its own.
secondary@lists.fedoraproject.org