adam.mclaurin at gmx.net
Wed May 19 23:55:39 PDT 2004
Just had a very weird happening with portupgrade .. I can't explain it's
-# pkg_version -v |grep "needs"
ImageMagick-126.96.36.199_1 < needs updating (port has 188.8.131.52)
apache-1.3.29_5 < needs updating (port has 1.3.31)
kdebase-3.2.2 < needs updating (port has 3.2.2_1)
mod_php4-4.3.6,1 < needs updating (port has 4.3.6_1,1)
mozilla-1.7.r1,2 < needs updating (port has 1.7.r2,2)
p5-sdl-1.20.3_2 < needs updating (port has 1.20.3_3)
rhythmbox-0.8.3 < needs updating (port has 0.8.4)
sdl_gfx-2.0.10_2 < needs updating (port has 2.0.11)
-# portupgrade -a -x "kdebase*" -x "apache*" -x "mod_php4*" -f galeon2
---> Reinstalling 'zsh-4.2.0' (shells/zsh)
---> Building '/usr/ports/shells/zsh'
===> Cleaning for zsh-4.2.0
===> Vulnerability check disabled
===> Extracting for zsh-4.2.0
>> Checksum OK for zsh-4.2.0.tar.bz2.
>> Checksum OK for zsh-4.2.0-doc.tar.bz2.
===> Patching for zsh-4.2.0
===> Applying FreeBSD patches for zsh-4.2.0
===> Configuring for zsh-4.2.0
configuring for zsh 4.2.0
-# pkg_version -v |grep -i zsh
zsh-4.2.0 = up-to-date with port
-# pkgdb -F
---> Checking the package registry database
(back to command prompt here; ie, no errors)
-# uname -a
FreeBSD jake 5.2.1-RELEASE-p4 FreeBSD 5.2.1-RELEASE-p4 #0: Tue Mar 30
01:07:47 EST 2004 root at jake:/usr/obj/usr/src/sys/ESKI i386
Why the h*ll did portupgrade try to recompile zsh? I can't think of any
logical explanation for this behavior. Perhaps I am missing something
simple here; or perhaps I stumbled across a bug in portupgrade (or even
"satyam, shivam, sundaram"
More information about the freebsd-ports