On Thu, Sep 18, 2003, Christoph Schug wrote:
> > i get this error when trying to rebuild last pkg from mysql-4
> >
> > + exit 0
> > Executing(%build): env -i /users/www/local/lib/openpkg/bash --norc
> > --noprofile --posix -e /users/www/local/RPM/TMP/rpm-tmp.7700
> > + cd /users/www/local/RPM/TMP
> > + cd mysql-4.0.14
> > + /users/www/local/lib/openpkg/shtool subst '%{l_value' -s '-a}'
> > mysys/default.c
> > shtool:subst:Error: either -e option(s) or -f option required
> > error: Bad exit status from /users/www/local/RPM/TMP/rpm-tmp.7700 (%build)
> >
> > host is a sparc solaris 2.7 and openpkg is a snapshot so this could be
> > the pb (correspond to 1.3)
> > >rpm -qa|grep openpkg
> > openpkg-20030715-20030715
> > openpkg-tool-20030528-20030528
>
> yep, your openpkg package is just one day to old, openpkg >= 20030716 is
> required.
And the "mysql" package actually expressed "openpkg >= 20030718" because
%{l_value} was introduced over multiple days. Lesson to learn here,
guys: "never ever use --nodeps on a CURRENT package", except you're
closely monitoring our CURRENT changes and know _EXACTLY_ what you're
doing. We never bump up dependencies just for fun, especially not those
to the "openpkg" bootstrap package.
So, if a package says it requires "openpkg >= 20030718" and you have
openpkg-20030715, you first _have_ to upgrade. Sorry, that's the price
of running bleeding edge OpenPKG-CURRENT and not OpenPKG-RELEASE. If
someone is tired of such regular updating (or his Internet link is
already driving hot ;-), he has to stick with OpenPKG-RELEASE, i.e.,
currently OpenPKG 1.3. Else one have to fulfill the dependencies on
every upgrade. Sorry.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
