I'm having a new issue with OpenPKG itself. When I use the openpkg build tools against a local source repository to rebuild packages into binary rpms there seems to be some sort of loop. I setup the local source repository so that it has PLUS and UPD under the top level SRC directory. Then I rebuild the index for SRC, which includes all subdirectories. After this, I use openpkg build to generate the upgrade script which seems to go through fine and do all the rebuilds. However, after doing this the first time, if I do it again to verify that nothing more needs to be rebuilt/upgraded I get the following list of things that it wants to upgrade:
ghostscript-8.14-2.1.0 UPDATE ghostscript-8.14-2.1.2 gimp-2.0.2-2.1.0 DEPEND gimp-2.0.2-2.1.0 gv-3.5.8-2.1.0 DEPEND gv-3.5.8-2.1.0 kerberos-1.3.4-2.1.0 UPDATE kerberos-1.3.4-2.1.1 libwmf-0.2.8.3-2.1.0 DEPEND libwmf-0.2.8.3-2.1.0 mgv-3.1.5-2.1.0 DEPEND mgv-3.1.5-2.1.0 mysql-4.0.20-2.1.0 UPDATE mysql-4.0.20-2.1.1 openpkg-2.1.2-2.1.2,openpkg-20040825-20040825 UPDATE openpkg-2.1.0-2.1.0 perl-dbi-5.8.4-2.1.0 UPDATE perl-dbi-5.8.4-2.1.1 perl-dbix-5.8.4-2.1.0 DEPEND perl-dbix-5.8.4-2.1.0 pgautodoc-1.23-2.1.0 DEPEND pgautodoc-1.23-2.1.0 postgresql-7.4.3-2.1.1 UPDATE postgresql-7.4.3-2.1.0 pstoedit-3.33-2.1.0 DEPEND pstoedit-3.33-2.1.0 rsync-2.6.2-2.1.0 UPDATE rsync-2.6.2-2.1.1 sasl-2.1.18-2.1.0 UPDATE sasl-2.1.18-2.1.1 sudo-1.6.7p5-2.1.0 UPDATE sudo-1.6.7p5-2.1.2 vim-6.3.11-2.1.0 UPDATE vim-6.3.11-2.1.1 Note that it seems to want to "update" openpkg-2.1.2 to openpkg-2.1.0, which of course is a downgrade. It also has some extra provides that includes a date, like it is from current, but it isn't. If I go ahead with this "upgrade" then check what it wants to do again, it returns the following list: ghostscript-8.14-2.1.2 UPDATE ghostscript-8.14-2.1.0 gimp-2.0.2-2.1.0 DEPEND gimp-2.0.2-2.1.0 gv-3.5.8-2.1.0 DEPEND gv-3.5.8-2.1.0 kerberos-1.3.4-2.1.1 UPDATE kerberos-1.3.4-2.1.0 libwmf-0.2.8.3-2.1.0 DEPEND libwmf-0.2.8.3-2.1.0 mgv-3.1.5-2.1.0 DEPEND mgv-3.1.5-2.1.0 mysql-4.0.20-2.1.1 UPDATE mysql-4.0.20-2.1.0 openpkg-2.1.0-2.1.0,openpkg-20040712-20040712 UPDATE openpkg-2.1.2-2.1.2 perl-dbi-5.8.4-2.1.1 DEPEND perl-dbi-5.8.4-2.1.0 perl-dbix-5.8.4-2.1.0 DEPEND perl-dbix-5.8.4-2.1.0 pgautodoc-1.23-2.1.0 DEPEND pgautodoc-1.23-2.1.0 postgresql-7.4.3-2.1.0 UPDATE postgresql-7.4.3-2.1.1 pstoedit-3.33-2.1.0 DEPEND pstoedit-3.33-2.1.0 rsync-2.6.2-2.1.1 UPDATE rsync-2.6.2-2.1.0 sasl-2.1.18-2.1.1 UPDATE sasl-2.1.18-2.1.0 sudo-1.6.7p5-2.1.2 UPDATE sudo-1.6.7p5-2.1.0 vim-6.3.11-2.1.1 UPDATE vim-6.3.11-2.1.0 Why would it be doing this? It seems that I'm stuck in an infinite loop. This doesn't seem to be a problem if I don't include the UPD directory, but we need to include it so that we have the security updates and other bug fixes that are applied to the source rpms under UPD. Can anybody assist me with this dilemma or point me in the right direction please? Thanks. -- David M. Fetter - UNIX Systems Administrator Portland State University - www.oit.pdx.edu
signature.asc
Description: This is a digitally signed message part