It's getting late here, and currently I'm at a loss.
Today's Rawhide build of xulrunner does:
%global nss_version 3.12.9
BuildRequires: nss-devel >= %{nss_version}
http://koji.fedoraproject.org/koji/buildinfo?buildID=250684 http://kojipkgs.fedoraproject.org/packages/xulrunner/5.0/4.fc16/data/logs/x8...
The root.log says:
DEBUG util.py:250: nss x86_64 3.12.9-11.fc16 build 748 k
However, that is an old build of nss from 2011-02-16. There have been half a dozen newer builds of nss for dist-f16, including a version upgrade to 3.12.10 and several builds since then: http://koji.fedoraproject.org/koji/packageinfo?packageID=248
$ rpmdev-vercmp 3.12.9-11.fc16 3.12.10-5.fc16 3.12.9-11.fc16 < 3.12.10-5.fc16
I've also searched for an Epoch change. What am I missing?
On Tue, Jun 28, 2011 at 11:09:02PM +0200, Michael Schwendt wrote:
It's getting late here, and currently I'm at a loss.
Today's Rawhide build of xulrunner does:
%global nss_version 3.12.9
BuildRequires: nss-devel >= %{nss_version}
http://koji.fedoraproject.org/koji/buildinfo?buildID=250684 http://kojipkgs.fedoraproject.org/packages/xulrunner/5.0/4.fc16/data/logs/x8...
The root.log says:
DEBUG util.py:250: nss x86_64 3.12.9-11.fc16 build 748 k
However, that is an old build of nss from 2011-02-16. There have been half a dozen newer builds of nss for dist-f16, including a version upgrade to 3.12.10 and several builds since then: http://koji.fedoraproject.org/koji/packageinfo?packageID=248
$ rpmdev-vercmp 3.12.9-11.fc16 3.12.10-5.fc16 3.12.9-11.fc16 < 3.12.10-5.fc16
I've also searched for an Epoch change. What am I missing?
Builds for a given target don't always use packages from the tag with the same name:
koji list-targets --name=dist-f16
will show that builds for dist-f16 use a buildroot populated with packages from the dist-f16-build tag, and sure enough, 3.12.9-11.fc16 is tagged for dist-f16-build. I don't know why that's there, though.
HTH,
Nalin
On Tue, 28 Jun 2011 17:23:33 -0400, ND (Nalin) wrote:
Builds for a given target don't always use packages from the tag with the same name:
koji list-targets --name=dist-f16
will show that builds for dist-f16 use a buildroot populated with packages from the dist-f16-build tag, and sure enough, 3.12.9-11.fc16 is tagged for dist-f16-build. I don't know why that's there, though.
HTH,
Strange. Dunno what that implies. koji tag history pasted at the bottom. Something's broken here.
http://koji.fedoraproject.org/static-repos/dist-rawhide-current/x86_64/pkgli...
nss/3.12.10/5.fc16/x86_64/nss-pkcs11-devel-3.12.10-5.fc16.x86_64.rpm nss/3.12.10/5.fc16/x86_64/nss-3.12.10-5.fc16.x86_64.rpm nss/3.12.10/5.fc16/x86_64/nss-devel-3.12.10-5.fc16.x86_64.rpm nss/3.12.10/5.fc16/x86_64/nss-tools-3.12.10-5.fc16.x86_64.rpm nss/3.12.10/5.fc16/x86_64/nss-sysinit-3.12.10-5.fc16.x86_64.rpm
And:
http://download.fedora.redhat.com/pub/fedora/linux/development/rawhide/x86_6...
Could it be that some package maintainers build against a different target than what gets mashed into Rawhide?
Also affected by having being built against with ancient "nss":
seamonkey thunderbird thunderbird-lightning
[...]
$ koji list-history --tag=dist-f16-build --package=nss Wed Feb 16 16:27:44 2011 nss-3.12.9-11.fc16 tagged into dist-f16-build by emaldonado [still active]
$ koji list-history --tag=dist-f16 --package=nss Fri Feb 11 18:06:06 2011 nss-3.12.9-10.fc16 tagged into dist-f16 by emaldonado Wed Feb 16 05:56:47 2011 nss-3.12.9-11.fc16 tagged into dist-f16 by emaldonado Wed Feb 16 06:49:30 2011 nss-3.12.9-11.fc16 untagged from dist-f16 by emaldonado Fri Feb 18 22:55:32 2011 nss-3.12.9-12.fc16 tagged into dist-f16 by emaldonado Fri Feb 25 00:33:19 2011 nss-3.12.9-13.fc16 tagged into dist-f16 by emaldonado Fri Mar 25 22:46:44 2011 nss-3.12.9-14.fc16 tagged into dist-f16 by emaldonado Sun Mar 27 07:01:05 2011 nss-3.12.9-10.fc16 untagged from dist-f16 by oscar Tue Apr 12 21:51:33 2011 nss-3.12.9-15.fc16 tagged into dist-f16 by emaldonado Thu Apr 14 06:07:12 2011 nss-3.12.9-12.fc16 untagged from dist-f16 by oscar Thu Apr 28 07:25:54 2011 nss-3.12.10-0.1.fc16.beta1 tagged into dist-f16 by emaldonado Sat Apr 30 04:53:04 2011 nss-3.12.9-13.fc16 untagged from dist-f16 by oscar Sat May 7 17:54:36 2011 nss-3.12.10-1.fc16 tagged into dist-f16 by emaldonado Mon May 9 05:05:04 2011 nss-3.12.9-14.fc16 untagged from dist-f16 by oscar Tue May 17 18:33:53 2011 nss-3.12.10-2.fc16 tagged into dist-f16 by emaldonado [still active] Thu May 19 05:47:00 2011 nss-3.12.9-15.fc16 untagged from dist-f16 by oscar Fri May 20 16:33:01 2011 nss-3.12.10-3.fc16 tagged into dist-f16 by ausil [still active] Sun May 22 05:24:32 2011 nss-3.12.10-0.1.fc16.beta1 untagged from dist-f16 by oscar Sun Jun 12 04:12:25 2011 nss-3.12.10-4.fc16 tagged into dist-f16 by emaldonado [still active] Mon Jun 13 05:10:51 2011 nss-3.12.10-1.fc16 untagged from dist-f16 by oscar Mon Jun 27 20:41:43 2011 nss-3.12.10-5.fc16 tagged into dist-f16 by mschwendt [still active]
On 6/28/11 2:31 PM, Michael Schwendt wrote:
Mon Jun 13 05:10:51 2011 nss-3.12.10-1.fc16 untagged from dist-f16 by oscar
Who is oscar and why is (s)he repeatedly untagging nss builds from dist-f16?
On 6/28/11 2:40 PM, Jesse Keating wrote:
Who is oscar and why is (s)he repeatedly untagging nss builds from dist-f16?
I'm a dork. oscar (the grouch) is the garbage collection bot that untags old builds.
On 6/28/11 2:31 PM, Michael Schwendt wrote:
$ koji list-history --tag=dist-f16-build --package=nss Wed Feb 16 16:27:44 2011 nss-3.12.9-11.fc16 tagged into dist-f16-build by emaldonado [still active]
Also suspect. Nobody should be tagging things into dist-f16-build directly, especially people who aren't in the releng team. I've untagged this build, so that dist-f16-build will once again inherit the latest build from dist-f16.
$ koji latest-pkg dist-f16-build nss Build Tag Built by ---------------------------------------- -------------------- ---------------- nss-3.12.10-5.fc16 dist-f16 mschwendt
On 06/28/2011 03:44 PM, Jesse Keating wrote:
On 6/28/11 2:31 PM, Michael Schwendt wrote:
$ koji list-history --tag=dist-f16-build --package=nss Wed Feb 16 16:27:44 2011 nss-3.12.9-11.fc16 tagged into dist-f16-build by emaldonado [still active]
Also suspect. Nobody should be tagging things into dist-f16-build directly, especially people who aren't in the releng team. I've untagged this build, so that dist-f16-build will once again inherit the latest build from dist-f16.
$ koji latest-pkg dist-f16-build nss Build Tag Built by
nss-3.12.10-5.fc16 dist-f16 mschwendt
perhaps bodhi build override feature go amok?
On 6/28/11 2:49 PM, Nathanael D. Noblet wrote:
perhaps bodhi build override feature go amok?
Would have been pretty far amok, since overrides aren't needed for f16 work, let alone the override feature would be using dist-f16-override not dist-f16-build.