On Tue, Aug 02, 2005, Bill Campbell wrote:
> I just ran into what seems to be to be a wierd problem. I built our normal
> selection of packages on one SuSE Linux Enterprise 9 (SLES9) system which
> created the tag suse9. I then installed the binary packages on another
> SLES9 system where the OS is identical.
>
> I had a problem with clamav giving an invalid instruction on the second
> machine so did an ``openpkg build -z binutils gcc'' to rebuild since the
> second machine has is a VIA EPIA while the first has an Intel Celeron
> processor, figuring that the difference in CPU might make a difference.
> The build process included a rebuild of openpkg itself to the latest
> CURRENT version (the rest is primarily Release 2.3).
>
> After rebuilding openpkg, the tag had changed from suse9 to linux2.6 which
> naturally broke the generated update script.
>
> Why would the tag change since I didn't specify any when originally
> bootstrapping OpenPKG?
Are you really speaking about the --tag stuff or do you mean the
platform identifier. I guess you mean that the platform identifier
changed from x86-suse9 to x86-linux2.6, right? This can happen if the
underlying SLES9 perhaps has to /etc/SuSE-release or /etc/SuSE_version
file AFAIK. Can you check this, Bill?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List openpkg-dev@openpkg.org
