[wplug-bsd] cvsup and portupgrade

[Daryl Clevenger]

Hello,

% uname -v
FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003     root at freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/GENERIC 

After the hints and advice from 1.5 months ago, I decided to
try and upgrade /usr/ports and some of the packages.  I appreciate
everyones feedback.  All of it was very helpful.

For various reasons, I would rather not compile anything.

The results have been less than I expected.  I have not poked around the
ftp site(s) to see what is really there.

Here are the steps and results

1. cvsup -g -L 1 /root/sup/ports/supfile

No problems here.  The only differences from the example (ports-supfile)

51c51
< *default host=CHANGE_THIS.FreeBSD.org
---
> *default host=cvsup2.us.FreeBSD.org
58c58
< *default compress
---
> #*default compress

2. portsdb -Uu

This action was recommended in portsdb(1).  There were many errors
(warnings?).  I deleted INDEX.db and ran it a second time.  Still
many errors of the form:

gnopernicus-0.8.4:"" non-existent -- dependency list incomplete
gnopernicus-0.8.4:"/usr/ports/devgok-0.10.2" non-existent -- dependency list incomplete
<snip>
/ports/devel/pkgconfig               : malformed entry: /ports/devel/pkgconfig               |
<snip>
make_index: py23-gstreamer-0.7.91: no entry for /usr/X11R6
make_index: py23-gstreamer-0.7.91: no entry for /usr/X11R6
<snip>
make_index: gnupod-0.94_1: no entry for /usr/ports/audio/gogo
make_index: gnupod-0.94_1: no entry for /usr/ports/audio/gogo
<snip>
Warning: Duplicate INDEX entry: freeciv-gtk-1.14.1
<snip>

I have included samples of the types of messages.  There were

25 - dependency list incomplete
10 - malformed entry
29 - make_index: ... no entry for
1  - Duplicate INDEX entry:

I next decided to see what would happen if I tried to upgrade my packages

3. portupgrade -PP -R -b -a

--->  Checking the availability of the latest package of 'converters/libiconv'
--->  Fetching the package(s) for 'libiconv-1.9.1_3' (converters/libiconv)
--->  Fetching libiconv-1.9.1_3
fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/libiconv-1.9.1_3.tgz: File unavailable (e.g., file not found, no access)
** The command returned a non-zero exit status: 1
** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/libiconv-1.9.1_3.tgz
fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/libiconv-1.9.1_3.tbz: File unavailable (e.g., file not found, no access)
** The command returned a non-zero exit status: 1
** Failed to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4.9-release/All/libiconv-1.9.1_3.tbz
** Failed to fetch libiconv-1.9.1_3
** The following packages were not downloaded (*:skipped / !:failed)
        ! libiconv-1.9.1_3      (fetch error)
** No latest link for '' (converters/libiconv) -- giving up
** Could not fetch the latest version '1.9.1_3'
** The package of 'converters/libiconv' is not found.
<snip>
** The following packages were not installed or upgraded (*:skipped / !:failed)
--->  Skipping 'devel/ORBit' (ORBit-0.5.17_1) because 'devel/gettext' (gettext-0.12.1) failed
<snip>
--->  Skipping 'editors/emacs' (emacs-21.3) because 'graphics/tiff' (tiff-3.5.7_1) failed
<snip>

These are example messages.  If I included one for a package known to
cause problems, there are others.

Some of the messages probably make sense; some packages appear to have
been skipped because there is no newer messages.

Questions:

1. Are these messages normal?  I dislike ignoring error messages.

2. Should I abandon my folly of trying to do 'portupgrade -PP' and
   build package upgrades?

3. Is it simply the case that packages are provided for FreeBSD 5.X, but
   the 4.X releases lag?

4. Similarly, I am having problems since I am not tracking -STABLE or
   -CURRENT.  Slow changing "RELENG" releases are fine with me.

5. What am I missing?  Should this procedure be less chatty?

I will probably try doing "portupgrade -PR" to see how that goes.

None of this is a gripe.  I'm just trying to get a clearer understanding
of how FreeBSD provides upgrade services.  For my apart, I'm trying
to determine which techniques for using the upgrade services work
(without requiring too much time).

--
Daryl Clevenger
dlc at cs.cmu.edu