Hi,
I was testing updating an openpkg 1.2 instance on Solaris 9. The RPMs were
built on Solaris 8. I created a binary repository with:
openpkg index -o 00INDEX.rdf -i -p sparc64-solaris8 .
I was using a repository that is NFS-mounted. I noticed that:
openpkg build /mnt/openpkg/sparc-SunOS-5.8/1.2/bin.rpm -p
sparc64-solaris2.8 XXX
results in code like this:
-----------------
echo ::::
/mnt/nfsadm1/openpkg/sparc-SunOS-5.8/1.2/bin.rpm/binutils-2.13.2.1-1.2.
0.sparc64-solaris2.8-oo1.rpm ::::
/opt/opkg/1.2/lib/openpkg/curl -q -s -o
/opt/opkg/1.2/RPM/PKG/binutils-2.13.2.1-1 .2.0.sparc64-solaris2.9-oo1.rpm
/mnt/nfsadm1/openpkg/sparc-SunOS-5.8/1.2/bin.rpm/
binutils-2.13.2.1-1.2.0.sparc64-solaris2.8-oo1.rpm || exit $?
/opt/opkg/1.2/bin/rpm -Uvh
/opt/opkg/1.2/RPM/PKG/binutils-2.13.2.1-1.2.0.sparc64- solaris2.9-oo1.rpm
|| exit $?
echo ::::
/mnt/nfsadm1/openpkg/sparc-SunOS-5.8/1.2/bin.rpm/binutils-2.13.2.1-1.2.
0.sparc64-solaris2.8-oo1.rpm = $? ::::
-----------------
1. Notice that the echo statements use "solaris2.8" but the curl renames
the output using the string 'solaris2.9'. It shouldn't break anything in
this case, but is that intentional?
2. The curl fails. Removing "-s" reveals a "malformed <url>" error, which
I resolved by prepending "file://" to the pathname in the saved output
from openpkg build. The openpkg man page says "-r" can take a directory
path for the repository, so I'm assuming this is a bug. Is this fixed in a
newer release ?
Thanks,
--
Vinod
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
