Tagging, let us know when you're done.

I have untagged this as it broke the buildroots

Given that this build chain will break any users of nss for the time that it's in the buildroot, and requires a synchronized update:

1) why are they separate packages to begin with?

2) is it better to do this in a separate tag?

Sorry about that. We have them as separate packages because of RHEL where we often need to keep softokn at the last FIPS-validated version while letting the the rest of nss move along with the latest security fixes. Then nss-util because it is a dependency of both nss-softokn and nss ended up as a separate package as well. The new scheme works better than the old system but it still leaves to be desired.

One way to prevent problems is by changing the BuildRequires on nss and nss-softokn from BuildRequires >= %{nss_util_version} to be BuildRequires >= %{nss_util_build_version} where nss_util_build_version would be the last version already available on the buildroot. That would be 3.12.6 right now. Unfortunately, in this update (a rebase) nss-softokn and nss do need the latest nss-util to compile. In rawhide we have a chain build but that is not the case on the stable branches. Is there a way to emulate that? Let me experiment with scratch build and mockbuilds on a virtual machine on f14. I will questions as I make progress or fail to.

By relaxing the build requires I now have built all three packages: nss-util-3.12.7-2.fc14, nss-softokn-3.12.7-3.fc14, and nss-3.12.7-3.fc14. I would like to have them added to build override for fc14 next. Is it possible to add them all at once, perhaps postponing other request for a short while until all tree at in?

This seems superseded by other tickets.