Date: Wed, 11 Aug 2004 18:04:21 -0700 From: "Michael C. Shultz" <ringworm@inbox.lv> To: freebsd-questions@freebsd.org Subject: Re: what's wrong with my ports??? Message-ID: <200408111804.29125.ringworm@inbox.lv> In-Reply-To: <411ABD41.6050705@att.net> References: <411AACD4.10405@att.net> <411AB61E.5010000@crime.ctf.edu> <411ABD41.6050705@att.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 11 August 2004 05:43 pm, Duane Winner wrote: > Will wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Duane Winner wrote: > > | Hello all, > > | > > | This problem has been recurring on my laptop (5.2.1-RELEASE-p9) for the > > | past few weeks and I'm scratching my head. > > | > > | Very frequently, I'll go to portinstall something, and I'll get several > > | stop errors, and the build will fail. > > | > > | But if I do a "rm -rf /usr/ports", then re-cvsup my ports collection, I > > | can successfully build whatever port I was trying at the time. However, > > | a few days later (or whatever), I'll try to build another port, and it > > | will start all over. I delete /usr/ports, cvsup again, then I'm fine. > > | This has happened several times over the past few weeks and the whole > > | manual cvsup'ing to refresh my entire /usr/ports every time is getting > > | old. (Although I've noticed I can sometimes get away with just deleting > > | the /usr/ports/... directory of the port I'm trying to build and > > | cvsup'ing again.) > > | > > | I'm keeping my ports current the same way on a workstation in at work, > > | and I've had no problems there, so I know it has to be something that's > > | wrong on my laptop. > > | > > | Here is the output of the latest port failure (fwbuilder): > > | > > | ===> Applying FreeBSD patches for net-snmp-5.1.2 > > | 2 out of 4 hunks failed--saving rejects to > > | agent/mibgroup/ucd-snmp/diskio.c.rej > > | > > | >> Patch patch-diskio.c failed to apply cleanly. > > | >> Patch(es) patch-Makefile.in patch-aa patch-auto_nlist.c > > | > > | patch-configure.in applied cleanly. > > | *** Error code 1 > > | > > | Stop in /usr/ports/net-mgmt/net-snmp. > > | *** Error code 1 > > | > > | Stop in /usr/ports/security/libfwbuilder. > > | *** Error code 1 > > | > > | Stop in /usr/ports/security/fwbuilder. > > | ** Command failed [exit code 1]: /usr/bin/script -qa > > | /tmp/portinstall79078.0 make > > | ** Fix the problem and try again. > > | ** Listing the failed packages (*:skipped / !:failed) > > | ! security/fwbuilder (patch error) > > | ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed > > | > > | > > | Thank for any feedback! > > | > > | -Duane > > | > > | _______________________________________________ > > | 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" > > > > I'm abit confused, just syncing your port tree via cvsup does'nt work? > > ie. things wont build after that, but after removing your entire ports > > tree they will? Are you sure it couldn'nt be a disc problem with the > > ports files being corrupted? > > Yeah, I'm confused too :), but that's what's going on. I have a cronjob > that syncs my ports tree every day at noon. It does: > > /usr/local/bin/cvsup -L 2 /usr/sup/supfile > /usr/local/sbin/portsdb -Uu > /usr/sbin/pkg_version -v | grep "needs" > > My supfile is: > > *default host=cvsup11.us.freebsd.org > *default base=/usr > *default prefix=/usr > *default release=cvs tag=RELENG_5_2 > *default use-rel-suffix compress > > src-all > ports-all tag=. > doc-all tag=. > > Additionally, I should mention that the problem isn't consistent. > > For instance, yesterday, the cronjob ran and I was notified (pkg_version > -v) that there were updates to XFree86 et.al. > > I got home last night, and did a portupgrade -a. No problem. > > Today at noon, cvsup (via cronjob) ran again. > > I got home tonight and finally decided to install xmms. So I did a > "portinstall xmms" and it installed fine. > > Later on, I decided I wanted to install fwbuilder. "portinstall > fwbuilder" started, then eventually bombed with the patch errors. > > So I "rm -rf /usr/ports", did cvsup again which sucked in a virgin ports > tree again, then tried "portinstall fwbuilder" again. I'ts humming along > nicely now. > > I'll entertain the possiblity of disk errors, but I am not having any > other noticeable issues, and I have just one big filesystem (/). > > Is it possible portsdb -Uu is hosing things? > > -Duane > Duane, I wrote sysutils/portmanager because portupgrade doesn't always do a good job at updateting ports, try it if you like it may just solve your problem.... -Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408111804.29125.ringworm>