Date: Thu, 12 Sep 2002 16:22:57 -0700 From: Andy Sparrow <spadger@best.com> To: FreeBSD Ports List <ports@FreeBSD.ORG> Cc: pippo@videotron.ca Subject: Re: Can somebody help this guy please? [pippo@videotron.ca: Re: [CUPS] frustrated to no end] Message-ID: <20020912232257.13A0447@CRWdog.demon.co.uk> In-Reply-To: Message from Alan E <alane@geeksrus.net> of "Thu, 12 Sep 2002 18:07:18 EDT." <20020912220718.GE87447@wwweasel.geeksrus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_-548992140P Content-Type: text/plain; charset=us-ascii > Can someone help this guy? I'll try. Remember, free advice is sometimes worth what you pay for it :-) > At 11:24 PM 9/12/2002 +0400, you wrote: > >Try to cvsup the latest port tree. > > Done. > > >Check the versions of installed ports with pkg_version -v. Check the > >package db integrity with > >pkgdb -F. This utility's quite useful and comes with portupgrade port. > > Yeah, but it's quite confusing. For instance, I upgraded portupgrade and > then did portversion: portversion would not run since there was a stale > dependency for ruby. Well, what do I do? Do I change the dependency to the > oder installed version of ruby and then upgrade ruby? Will that fix the > dependency after an upgrade? Or do I portupgrade ruby first and then rerun > portversion? - I did the second and then portversion did work. But what If > I had done the former? After updating the ports tree, I generally fix the INDEX file and check the integrity of the package db as suggested, and then run 'portupgrade -r \*', or 'portupgrade -Rr \*', (or even 'portupgrade -Rrf \*'), depending on how long I've got, how long it's been since I re-built all my ports, how far out of sync my installed world and the majority of my ports are, and how I'm feeling today :-) Come back a some time later. Note that some packages will stop building and wait for operator input unless/until you make special arrangements (e.g. in '/usr/local/etc/pkg_tools.conf'). If you have problems with any ports (unfetchable, compile errors etc), you may need to look back over the list archives or through the PR database and find out what the appropriate fix is. You may need to update your world, or simply apply some local patch that hasn't yet made it into CVS. Submit it with a PR (ideally, with patches! ;-) if you think you find a real bug that no-one else has discovered/reported yet. Generally, however, it'll run through and update the vast bulk of the ports necessary the first time - maybe leaving you with a few that need special attention. In the specific question you ask above, I'd probably do a: portupgrade -r portversion\* then portupgrade should upgrade portversion and any dependancies recursively. Sometimes, you might need to force some packages to be rebuilt. > >Get a list of files under /usr/local and /usr/X11R6 that do not > >belong to any package: > >find /usr/local /usr/X11R6 -type f | xargs pkg_which -v|fgrep '?' > > Ouch - there's alist of at least 1.5mb just for .../local. What can I do > with them? How do I know that they are not in use by a program? If you've been compiling and installing packages from source code without the benefit of the Ports system, then there's not much it can do to help you here, you just need to know what/where they are. You could always create a port for these packages, if there isn't one already ;-) Basically, you'll need to sift through and decide which you need and which you don't. > Can I delete them? Or what? Look at them. If they're generated or manually-modified files (e.g. Glimpse indexes, catman pages, Samba or other port configuration/startup files), then they're fine, just leave 'em alone, as it'll only break things if you remove them. If they're turds left behind by an older version of a package (e.g. I just noted a whole bunch of versioned plugins from older versions of Ethereal), then they're safe to remove, if you've already updated to the later versions via 'portupgrade'. If they're locally-installed applications, icons, libraries etc., see answer to previous para.. ;-) Otherwise, you're probably still using at least the most recent versions of these... Note that 'portupgrade' stores previous versions of shared libraries in /usr/local/lib/compat - these might be safe to remove, might not, depending on how everything went in your previous portupgrade runs... > >Check if the installed files have been altered somehow: pkg_info -ga > > Yeah, tons of MD%c checksum failures.... Does that mean they have been > overwritten by more recent installations? Well, the checksum stored in the package DB when the package was installed doesn't match the checksum of the file on the disk. I see some of these (mostly for missing files) for ports where the file(s) are mis-specified or there appear to be namespace collisions with other ports, for example. I don't know how else this could happen. Doesn't keep me awake nights... :) > Are they still good? YMMV. I have some reports of these, but everything works on my system, AFAIK... > Can I delete them? Uh, probably not wise if you want them to work. Update your ports via portupgrade if you haven't done so already, then re-run the check. > I don't really understand what would cause this overload of garbage, if > that is what it is... :)) > > I am happy to learn how to use the pkg_* tools. I never thought about using > them as whatever results I would get, would (and are) pretty meaningless > for me as I have no idea of what to do about them. > > Thanks for any help. You're welcome. HTH. Cheers, AS --==_Exmh_-548992140P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) Comment: Exmh version 2.5 07/13/2001 iD8DBQE9gSHQPHh895bDXeQRAmuYAKCtx4wxgE+HvPNgeTOb+KfCGG01SACfRMs/ 7vQR6qcqQER+TlFf+6L/6fg= =JA8+ -----END PGP SIGNATURE----- --==_Exmh_-548992140P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020912232257.13A0447>