Date: Fri, 28 Oct 2005 20:20:29 -0700 From: "Michael C. Shultz" <ringworm01@gmail.com> To: John DeStefano <john.destefano@gmail.com> Cc: Eric F Crist <ecrist@secure-computing.net>, freebsd-questions@freebsd.org Subject: Re: portupgrade stale dependencies Message-ID: <200510282020.32005.ringworm01@gmail.com> In-Reply-To: <f2160e0d0510281951s541d3d9ft808d36b023fa9661@mail.gmail.com> References: <f2160e0d0510151746n28cdbb25s2150337c0c6f7cfc@mail.gmail.com> <200510281922.16495.ringworm01@gmail.com> <f2160e0d0510281951s541d3d9ft808d36b023fa9661@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 28 October 2005 19:51, John DeStefano wrote: > On 10/28/05, Michael C. Shultz <ringworm01@gmail.com> wrote: > > On Friday 28 October 2005 17:31, John DeStefano wrote: > > > On 10/28/05, Eric F Crist <ecrist@secure-computing.net> wrote: > > > > > status report finished > > > > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > > >=3D=3D=3D =3D=3D > > > > > percentDone-=3D>0 =3D 100 - ( 100 * ( QTY_outOfDatePortsDb-=3D>1 / > > > > > TOTAL_outOfDatePortsDb-=3D>1 ) ) > > > > > upgrade 0.3.0_0 info: ignoring apache-2.0.48, reason: failed duri= ng > > > > > (2) make > > > > > -----------------------------------------------------------------= =2D- > > > > >--- -- > > > > > update of ports collection complete with either some errors, > > > > > ignored ports or both > > > > > > > > > > > > > > > Unfortunately, this is the most crucial of all, and ironically the > > > > > one about which I've been asking since the beginning. As I > > > > > mentioned earlier, upgrading this port bails consistently with a C > > > > > callout to PEM_F_DEF_CALLBACK. I'd really like to get this port > > > > > updated, not only to finally complete this insane goose chase of > > > > > updating, but because I know that apache-2.0.48 is chock full of > > > > > vulerabilities. > > > > > > > > cd /usr/ports/www/apache20 && make deinstall && make clean && make > > > > reinstall > > > > > > > > See what happens. > > > > > > Talk about strange: > > > > > > # cd /usr/ports/www/apache20/ > > > # make deinstall > > > =3D=3D=3D> Deinstalling for www/apache20 > > > =3D=3D=3D> apache not installed, skipping > > > > > > # make -V PKGNAME > > > apache-2.0.55 > > > > > > # pkg_info | grep apache > > > apache-2.0.48 Version 2 of the extremely popular Apache http > > > server > > > > > > # apachectl -v > > > Server version: Apache/2.0.48 > > > Server built: Nov 19 2003 22:44:21 > > > _______________________________________________ > > > freebsd-questions@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to > > > "freebsd-questions-unsubscribe@freebsd.org" > > > > Try > > ls /var/db/pkg/a* > > any apache versions in there? > > > > -Mike > > Yep: it was 2.0.48 > > I ended up deinstalling that apache installation (which I was not keen > on doing), and installing the apache20 port (which was the same > version (2.0.55) as the apache2 port <?>), and, thankfully, it's > working fine. I'm also now able to run both 'pkgdb -F'and 'portsdb > -Uu' without ANY errors (except for a few 'Duplicate INDEX entry' > warnings). > > Needless to say, this process wasn't much fun. What can I do to keep > this from happening again? What can/can't I safely include in cron to > automate database and index maintenance? > > Thanks to all. Pardon my bias agan ;) but I'd recommend only updating with portmanager. =46rom cron I'd just run a cvsupdate and portmanager -s > /root/portmanager= =2Elog. Review the log from time toi time and when you see something that should be= =20 updated run portmanager -u manually. Some ports do not do well being built= =20 from cron so will save you much trouble to do the updates manually. As far= =20 as the INDEX goes, portmanager doesn't require it, but other utilies do so= =20 maybe add a make fetch index to cron as well. Congradulations on getting everything fixed BTW. =2DMike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510282020.32005.ringworm01>