We are working on building a beta release of our ia64 F9 bits. I have been digging through the wiki for general release engineering processes and found this:
http://fedoraproject.org/wiki/ReleaseEngineering/SOP/FreezingRawhide?highlig...
which shows using the command:
koji clone-tag dist-f8 f8-final
however, I find that the clone-tag command does not actually exist. Was it replaced by something else? We are looking for a way to take the latest version of all packages and tag them with a tag which will be used to build the beta release.
- Doug
On Mon, 2008-04-21 at 20:54 -0400, Doug Chapman wrote:
We are working on building a beta release of our ia64 F9 bits. I have been digging through the wiki for general release engineering processes and found this:
http://fedoraproject.org/wiki/ReleaseEngineering/SOP/FreezingRawhide?highlig...
which shows using the command:
koji clone-tag dist-f8 f8-final
however, I find that the clone-tag command does not actually exist. Was it replaced by something else? We are looking for a way to take the latest version of all packages and tag them with a tag which will be used to build the beta release.
It does exist, what version of Koji are you using? It requires admin permissions, so it'll only show up in "koji help --admin". For usage, use "koji clone-tag --help".
On Mon, 2008-04-21 at 22:06 -0400, Mike Bonnet wrote:
On Mon, 2008-04-21 at 20:54 -0400, Doug Chapman wrote:
We are working on building a beta release of our ia64 F9 bits. I have been digging through the wiki for general release engineering processes and found this:
http://fedoraproject.org/wiki/ReleaseEngineering/SOP/FreezingRawhide?highlig...
which shows using the command:
koji clone-tag dist-f8 f8-final
however, I find that the clone-tag command does not actually exist. Was it replaced by something else? We are looking for a way to take the latest version of all packages and tag them with a tag which will be used to build the beta release.
It does exist, what version of Koji are you using? It requires admin permissions, so it'll only show up in "koji help --admin". For usage, use "koji clone-tag --help".
Ok, appears I have an old version of koji which is odd because I did do a "yum update koji" but evidently we don't have this version in the f8 repos right now. I will grab the latest rawhide koji and try that.
thanks,
- Doug
Doug Chapman wrote:
Ok, appears I have an old version of koji which is odd because I did do a "yum update koji" but evidently we don't have this version in the f8 repos right now. I will grab the latest rawhide koji and try that.
Odd. the clone-tag command was added on 2007-07-23. Git has several fc8 tags, but I don't see matching builds on koji.fp.o.
On Tue, 2008-04-22 at 11:18 -0400, Mike McLean wrote:
Doug Chapman wrote:
Ok, appears I have an old version of koji which is odd because I did do a "yum update koji" but evidently we don't have this version in the f8 repos right now. I will grab the latest rawhide koji and try that.
Odd. the clone-tag command was added on 2007-07-23. Git has several fc8 tags, but I don't see matching builds on koji.fp.o.
I don't know if I've pushed any koji updates for F-8 since the server side of things changed a lot and may not work with current F-8 toolings. Given that the client is tied to the server it makes it rather hard to do client updates.
Jesse Keating wrote:
I don't know if I've pushed any koji updates for F-8 since the server side of things changed a lot and may not work with current F-8 toolings. Given that the client is tied to the server it makes it rather hard to do client updates.
I'm pretty sure the F8 updates are sufficient to run koji. I've had an F8 system running koji development code (hub, client, builder, and kojira) for a while now.
$ koji latest-pkg --quiet dist-f8-updates mock yum createrepo python-krbV mock-0.9.7-2.fc8 dist-f8-updates jcwillia yum-3.2.8-2.fc8 dist-f8-updates skvidal createrepo-0.4.11-2.fc8 dist-f8-updates lmacken python-krbV-1.0.13-6.fc8 dist-f8 mikeb
Well, ok, I'm cheating a little bit. I previously had to make skip-stat optional in kojid (change committed on the shadow branch), but that appears to no longer be necessary since createrepo-0.4.11-2.fc8 has the skip-stat patch.
On Tue, 2008-04-22 at 16:30 -0400, Mike McLean wrote:
I'm pretty sure the F8 updates are sufficient to run koji. I've had an F8 system running koji development code (hub, client, builder, and kojira) for a while now.
$ koji latest-pkg --quiet dist-f8-updates mock yum createrepo python-krbV mock-0.9.7-2.fc8 dist-f8-updates jcwillia yum-3.2.8-2.fc8 dist-f8-updates skvidal createrepo-0.4.11-2.fc8 dist-f8-updates lmacken python-krbV-1.0.13-6.fc8 dist-f8 mikeb
Well, ok, I'm cheating a little bit. I previously had to make skip-stat optional in kojid (change committed on the shadow branch), but that appears to no longer be necessary since createrepo-0.4.11-2.fc8 has the skip-stat patch.
Gotcha, now that everything is almost in sync, it would be a good time to do another upstream release and push it to F8 as well.
buildsys@lists.fedoraproject.org
-
Doug Chapman -
Jesse Keating -
Mike Bonnet -
Mike McLean