Rencently,I changed the IP of my koji and regen-repo,but it shows missing dependency.The root.log as follows, redhat-rpm-config-8.0.45-29.el5.noarch from build has depsolving problems --> Missing Dependency: perl(Getopt::Long) is needed by package redhat-rpm-config-8.0.45-29.el5.noarch (build) redhat-rpm-config-8.0.45-29.el5.noarch from build has depsolving problems --> Missing Dependency: /bin/bash is needed by package redhat-rpm-config-8.0.45-29.el5.noarch (build) redhat-rpm-config-8.0.45-29.el5.noarch from build has depsolving problems --> Missing Dependency: /bin/sh is needed by package redhat-rpm-config-8.0.45-29.el5.noarch (build) redhat-rpm-config-8.0.45-29.el5.noarch from build has depsolving problems --> Missing Dependency: /usr/bin/perl is needed by package redhat-rpm-config-8.0.45-29.el5.noarch (build) Error: Missing Dependency: /bin/bash is needed by package redhat-rpm-config-8.0.45-29.el5.noarch (build) Error: Missing Dependency: /usr/bin/perl is needed by package redhat-rpm-config-8.0.45-29.el5.noarch (build) Error: Missing Dependency: perl(Getopt::Long) is needed by package redhat-rpm-config-8.0.45-29.el5.noarch (build) Error: Missing Dependency: /bin/sh is needed by package redhat-rpm-config-8.0.45-29.el5.noarch (build)
On 10/14/2009 03:57 AM, 李晓 wrote:
Rencently,I changed the IP of my koji and regen-repo,but it shows missing dependency.The root.log as follows,
By default, repo regens use the --update option against the last active repo. Because of this, old entries will persist. This is normally a helpful optimization, but when those old entries reference a now-changed url, it can be a problem.
The fix is to expire the active repo. This will force a full rebuild of the repo (no --update).
If you only have a few active repos, you can expire them on the command line like: % koji call repoExpire <repo-id> (the koji taginfo command will report the repo id of the active repo for the tag)
If you have a lot of active repos (i.e. lots of different build targets), then the easiest way to expire them all is in the db. For example: => update repo set state = 2 where state in (0, 1);
Once you've expired the repos, kojira should trigger the regenerations.
Hi, li xiao
Maybe this reason, chinese help can get from http://jianlee.ylinux.org/Computer/Server/koji.html#sec27
在 2009-10-14三的 12:23 -0400，Mike McLean写道：
On 10/14/2009 03:57 AM, 李晓 wrote:
Rencently,I changed the IP of my koji and regen-repo,but it shows missing dependency.The root.log as follows,
By default, repo regens use the --update option against the last active repo. Because of this, old entries will persist. This is normally a helpful optimization, but when those old entries reference a now-changed url, it can be a problem.
The fix is to expire the active repo. This will force a full rebuild of the repo (no --update).
If you only have a few active repos, you can expire them on the command line like: % koji call repoExpire <repo-id> (the koji taginfo command will report the repo id of the active repo for the tag)
If you have a lot of active repos (i.e. lots of different build targets), then the easiest way to expire them all is in the db. For example: => update repo set state = 2 where state in (0, 1);
Once you've expired the repos, kojira should trigger the regenerations.
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
buildsys@lists.fedoraproject.org
-
Jian Lee -
lixiao＠nudt.edu.cn -
Mike McLean