Date: Wed, 28 Sep 2005 13:18:09 -0500 From: Mark Kane <mark@mkproductions.org> To: Mark Linimon <linimon@lonesome.com> Cc: freebsd-ports@freebsd.org Subject: Re: Portupgrade Error Message-ID: <433ADE61.7030208@mkproductions.org> In-Reply-To: <20050928172829.GB5451@soaustin.net> References: <433855C1.4060803@mkproductions.org> <433AC90D.80608@mkproductions.org> <20050928172829.GB5451@soaustin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark Linimon wrote: > What shell are you using? If it's csh or derivative, try again with > /bin/sh and see if that changes your results. I was using csh, the normal root shell that ships with FreeBSD. I tried with /bin/sh and it just finished with: # portsdb -Uu Updating the ports index ... Generating INDEX.tmp - please wait.."/usr/ports/Mk/bsd.port.mk", line 2890: warning: duplicate script for target "checksum" ignored Warning: Duplicate INDEX entry: freeciv-gtk2-2.0.2 Warning: Duplicate INDEX entry: cvsup-without-gui-16.1h_2 Done. done [Updating the portsdb <format:bdb1_btree> in /usr/ports ... - 13524 port entries found .........1000.........2000.........3000.........4000.........5000.........6000.........7000.........8000.........9000.........10000.........11000.........12000.........13000..... ..... done] ---------------------- It worked with csh before...any reason it should not now? Stupid question, but does this mean I'm good to continue with portupgrade now? I see the warnings but it didn't say to run pkgdb -F or anything. I just don't want to screw anything up. > You should realize that there are many hundreds of people who are not > seeing these problems. The automated build cluster, in particular, > would have spotted them within a few hours. I figured it was not a widespread problem because I didn't see much about it, but I am fairly new to portupgrade and it said to report it, so I did. Thanks again. -Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?433ADE61.7030208>