On Sat, Jul 24, 2004 at 08:59:01AM +0200, Ralf S. Engelschall wrote:
That's a known bug in the openpkg build command (see
http://cvs.openpkg.org/getfile/openpkg-tools/TODO for a
list of known issues). It works fine for CURRENT, but when
updating a RELEASE it always thinks that the openpkg
Hello,
I'm having trouble using openpkg build on FreeBSD and am consistently
getting an I/O error. I am not sure how to identify the problem further.
I installed the following openpkg packages by hand (built locally):
bash-2.05a# pwd
/openpkg/RPM/PKG
bash-2.05a# /openpkg/bin/openpkg rpm -qa
On Sat, Jul 24, 2004, Michael van Elst wrote:
On Sat, Jul 24, 2004 at 08:59:01AM +0200, Ralf S. Engelschall wrote:
That's a known bug in the openpkg build command (see
http://cvs.openpkg.org/getfile/openpkg-tools/TODO for a
list of known issues). It works fine for CURRENT, but when
On Sat, Jul 24, 2004, Michael van Elst wrote:
[..]
One could special case the openpkg package, but I'd like to avoid this
if possible.
The following patch therefore will simply select the database entry with
the smallest version number, i.e. OpenPKG-2.1.0-2.1.0 when deciding on
wether it
After several attempts to recover the situation using suggested methonds (I
am not afraid of hard work) it became clear that the first suggestion -
reinstall - was the smarter, easier, and ultimately the best way to resolve
it. Done. Thank you - it was very educational.
Regards.
Thomas Lotterer
On Sun, Jul 25, 2004 at 12:03:09AM +0200, Ralf S. Engelschall wrote:
On Sat, Jul 24, 2004, Michael van Elst wrote:
[..]
One could special case the openpkg package, but I'd like to avoid this
if possible.
The following patch therefore will simply select the database entry with
the
