Re: openpkg 1.9 rpm install error
Thomas Lotterer wrote: On Mon, Jun 21, 2004, F. Even wrote: [...] what I'm asking is, can I do the following: Take openpkg-20040609-20040609.src.rpm, modify the spec file as described earlier to make this a 1.9 bootstrap. Then after converting the database, I should install the openpkg-20040609- 20040609.src.rpm again, unmodified, to bring myself from 1.3 to CURRENT. Is that correct? ... to bring myself from 1.9 to CURRENT, exactly. I don't remember all the issues why we introduced the intermediate step. But I do remeber: - OpenPKG 1.3 does not understand the %track section, it will become part of the previous %description. This is a cosmetic issue only. - OpenPKG 1.3 does not understand the Class: header and bails out on rebuilding. This is a showstopper. - The database needs conversion and it's a good idea to do the acutal install with a already converted database but database conversion requires the new rpm. - The new --tagfmt feature requires OpenPKG 2.0 but the upgrade is done using the existing (old) software. This might be a cosmetic issue if you do not use that feature but will be nasty if you use it and the bootstrap package itself receives a wrong filename. The intermediate OpenPKG 1.9 bootstrap resolves all those issues in a very elegant (although CPU time consuming ;-) way and provides a safe and compatible upgrade path. ...but that is where it crapped out on me (not very elegantly), trying to simply rpm --rebuild the source 1.9 bootstrap. So that is why I intend on trying some of these other things steps you suggested. Too late now though...bed time. Thanks for your assistance. I'll probably have a few more questions and errors to post. I've put a list of my installed pkgs, I've removed all of the perl stuff in anticipation of this upgrade (it seems like it was somewhat recommended in the upgrade docs). I'll have another go at it sometime tomorrow. Thanks. [EMAIL PROTECTED] rpm -qa | grep openpkg openpkg-1.3.1-1.3.1 [EMAIL PROTECTED] rpm -qa | sort binutils-2.14-1.3.0 bzip2-1.0.2-1.3.0 cdk-4.9.10.20030418-1.3.0 coreutils-5.0.1-1.3.2 curl-7.10.6-1.3.0 db-4.1.25.1-1.3.0 expat-1.95.6-1.3.0 freetype-2.1.4-1.3.0 fsl-1.3.0-1.3.2 gcc-3.3-1.3.0 jpeg-6b-1.3.0 lzo-1.08-1.3.0 make-3.80-1.3.0 ncurses-5.3.20030726-1.3.0 ntp-4.1.2-1.3.1 openpkg-1.3.1-1.3.1 openssh-3.6.1p2-1.3.2 openssl-0.9.7b-1.3.2 png-1.2.5-1.3.0 procmail-3.22-1.3.0 readline-4.3-1.3.0 sudo-1.6.7p5-1.3.1 zlib-1.1.4-1.3.0 __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
updated 1.9 intermediate package for upgrade procedure 1.3 - 2.0 available (Was: Re: openpkg 1.9 rpm install error)
On Mon, Jun 21, 2004, F. Even wrote: [...] seem then that the 1.9 bootstrap would need an upgrade I created the upgrade companion packages and added them to the ftp download area ftp://ftp.openpkg.org/release/2.0/UPD/ openpkg-1.9.3-2.0.3.src.rpm openpkg-1.9.2-2.0.2.src.rpm [*] openpkg-1.9.1-2.0.1.src.rpm [*] [*] belated and just for completeness See also http://cvs.openpkg.org/chngview?cn=17591 and http://cvs.openpkg.org/openpkg-re/upgrade.txt = 1.44 Thanks for pointing out. -- [EMAIL PROTECTED], Cable Wireless __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: updated 1.9 intermediate package for upgrade procedure 1.3 - 2.0 available (Was: Re: openpkg 1.9 rpm install error)
On Mon, Jun 21, 2004, F. Even wrote: [...] seem then that the 1.9 bootstrap would need an upgrade I created the upgrade companion packages and added them to the ftp download area ftp://ftp.openpkg.org/release/2.0/UPD/ openpkg-1.9.3-2.0.3.src.rpm openpkg-1.9.2-2.0.2.src.rpm [*] openpkg-1.9.1-2.0.1.src.rpm [*] [*] belated and just for completeness See also http://cvs.openpkg.org/chngview?cn=17591 and http://cvs.openpkg.org/openpkg-re/upgrade.txt = 1.44 Thanks for pointing out. You're welcome. But, not to be bothersome, but I think I'm a little bit more confused now. What exactly needs to be done to get from OpenPKG 1.3.1 to anywhere? I think this is a little confusing: - use openpkg-1.3.1 to rebuild and install the openpkg-1.9.0-2.0.0.src.rpm provided with the 2.0 release (intentionally no src.sh available). This intermediate package is a modified openpkg-2.0.0-2.0.0.src.rpm that has the offending Class: header removed. This is the recommended variant. For updated = openpkg-2.0.1-2.0.1 corresponding companion = openpkg-1.9.1-2.0.1 are available. Can or should openpkg-1.9.0-2.0.0.src.rpm be used at all? Under what circumstances would openpkg-1.9.1-2.0.1, openpkg-1.9.2-2.0.2.src.rpm, or openpkg-1.9.3-2.0.3.src.rpm be used? Is there any particular path in the bootstrapping I should use if I want to end up @ CURRENT? Meaning, if I manage to get to openpkg-2.0.0-2.0.0 somehow, someway, can I just short-circuit the rest and install openpkg-20040609-20040609.src.rpm? Thanks for your assistance. Frank __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
1.3 to 2.0/CURRENT upgrade on FreeBSD 4.0 (Was: Re: openpkg 1.9 rpm install error)
On Tue, Jun 22, 2004, F. Even wrote: It dies in pretty much the same place trying to go from 1.9.1-2.0.1. OK, I assume you give 1.9.3 or a very recent CURRENT a try, too. [EMAIL PROTECTED] rpm --rebuild openpkg-1.9.1-2.0.1.src.rpm snip main.c:1014:2: #error lack of strtoll() needs fixing If the error persists the first actions digging down are a man strtoll and a look in libc having that function defined using $ nm /usr/lib/libc.a | egrep 'T strtoll' T strtoll -- [EMAIL PROTECTED], Cable Wireless __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]
Re: updated 1.9 intermediate package for upgrade procedure 1.3 - 2.0 available (Was: Re: openpkg 1.9 rpm install error)
On Mon, Jun 21, 2004, F. Even wrote: [...] seem then that the 1.9 bootstrap would need an upgrade I created the upgrade companion packages and added them to the ftp download area ftp://ftp.openpkg.org/release/2.0/UPD/ openpkg-1.9.3-2.0.3.src.rpm openpkg-1.9.2-2.0.2.src.rpm [*] openpkg-1.9.1-2.0.1.src.rpm [*] [*] belated and just for completeness See also http://cvs.openpkg.org/chngview?cn=17591 and http://cvs.openpkg.org/openpkg-re/upgrade.txt = 1.44 Thanks for pointing out. You're welcome. But, not to be bothersome, but I think I'm a little bit more confused now. What exactly needs to be done to get from OpenPKG 1.3.1 to anywhere? I think this is a little confusing: - use openpkg-1.3.1 to rebuild and install the openpkg-1.9.0-2.0.0.src.rpm provided with the 2.0 release (intentionally no src.sh available). This intermediate package is a modified openpkg-2.0.0-2.0.0.src.rpm that has the offending Class: header removed. This is the recommended variant. For updated = openpkg-2.0.1-2.0.1 corresponding companion = openpkg-1.9.1-2.0.1 are available. Well, after clearing out all of the cruft in SRC and TMP, I decided to give 1.9.0-2.0.0 another whirl. Same error still. On to 1.9.1-2.0.1 I guess It dies in pretty much the same place trying to go from 1.9.1-2.0.1. I can really only think of one other thing that might be a little odd in my config, but has never caused a problem before, and that is that I have /cw symlinked: [EMAIL PROTECTED] ls -lrt | grep cw lrwxr-xr-x 1 root wheel 13 Nov 10 2003 cw - /home/openpkg ...it is most definitely bedtime now. I couldn't sleep is the only reason I didn't leave this for tomorrow. ;-) [EMAIL PROTECTED] rpm --rebuild openpkg-1.9.1-2.0.1.src.rpm snip using piecewise archive linking... /cw/bin/ar cru .libs/libcurl.a file.o timeval.o base64.o hostip.o progress.o formdata.o : .libs/libcurl.a /cw/bin/ar cru .libs/libcurl.a cookie.o http.o sendf.o ftp.o url.o dict.o if2ip.o speedcheck.o : .libs/libcurl.a /cw/bin/ar cru .libs/libcurl.a getdate.o ldap.o ssluse.o version.o getenv.o escape.o : .libs/libcurl.a /cw/bin/ar cru .libs/libcurl.a mprintf.o telnet.o netrc.o getinfo.o transfer.o strequal.o : .libs/libcurl.a /cw/bin/ar cru .libs/libcurl.a easy.o security.o krb4.o memdebug.o http_chunks.o strtok.o : .libs/libcurl.a /cw/bin/ar cru .libs/libcurl.a connect.o llist.o hash.o multi.o content_encoding.o : .libs/libcurl.a /cw/bin/ar cru .libs/libcurl.a share.o http_digest.o md5.o http_negotiate.o http_ntlm.o : .libs/libcurl.a /cw/bin/ar cru .libs/libcurl.a inet_pton.o strtoofft.o ranlib .libs/libcurl.a creating libcurl.la (cd .libs rm -f libcurl.la ln -s ../libcurl.la libcurl.la) make[2]: Leaving directory `/usr/home/openpkg/RPM/TMP/openpkg-1.9.1/curl-7.11.0/lib' make[1]: Leaving directory `/usr/home/openpkg/RPM/TMP/openpkg-1.9.1/curl-7.11.0/lib' Making all in src make[1]: Entering directory `/usr/home/openpkg/RPM/TMP/openpkg-1.9.1/curl-7.11.0/src' /cw/RPM/TMP/openpkg-1.9.1/make-3.80/make all-am make[2]: Entering directory `/usr/home/openpkg/RPM/TMP/openpkg-1.9.1/curl-7.11.0/src' if /cw/bin/cc -DHAVE_CONFIG_H -I../include -I../src -I../src -I/cw/RPM/TMP/openpkg-1.9.1/curl-7.11.0/../zlib-1.2.1 -I/cw/RPM/TMP/openpkg-1.9.1/curl-7.11.0/../zlib-1.2.1 -MT main.o -MD -MP -MF .deps/main.Tpo -c -o main.o main.c; \ then mv -f .deps/main.Tpo .deps/main.Po; else rm -f .deps/main.Tpo; exit 1; fi main.c:1014:2: #error lack of strtoll() needs fixing make[2]: *** [main.o] Error 1 make[2]: Leaving directory `/usr/home/openpkg/RPM/TMP/openpkg-1.9.1/curl-7.11.0/src' make[1]: *** [all] Error 2 make[1]: Leaving directory `/usr/home/openpkg/RPM/TMP/openpkg-1.9.1/curl-7.11.0/src' make: *** [all-recursive] Error 1 + exit 2 + exit 2 error: Bad exit status from /cw/RPM/TMP/rpm-tmp.15631 (%build) RPM build errors: Bad exit status from /cw/RPM/TMP/rpm-tmp.15631 (%build) __ The OpenPKG Projectwww.openpkg.org User Communication List [EMAIL PROTECTED]