Date: Sun, 21 Feb 2010 23:55:10 -0600 From: Programmer In Training <pit@joseph-a-nagy-jr.us> To: freebsd-questions@freebsd.org Subject: Re: Problems With K3b Message-ID: <4B821C3E.4060509@joseph-a-nagy-jr.us> In-Reply-To: <20100221105819.0cc86d17.freebsd@edvax.de> References: <4B80AFCA.50404@joseph-a-nagy-jr.us> <20100221105819.0cc86d17.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1E16FAF573A31063345AEF8F Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 02/21/10 03:58, Polytropon wrote: <snip> > I've often been told that portmaster would be a good choice. > I've used portinstall / portupgrade in the past, but have to > say that I honestly prefer pkg_add -r for simplicity. :-) I'm running portmaster right now to check for new packages and (recursively) dependencies and to upgrade anything that needs upgrading (if I'm reading the man page right I believe I issued the right command). I'm hoping this will take care of my k3b issue as well. Either way, I've decided to not worry about k3b, though I do want to resolve this if for no other reason than for if someone else runs into this problem, the archive will have the solution. I'd give you the output of pkg_add -rvn k3b but it'd be pointless because at some point I think I might have forced its install. pkgdb -f (to handle the stale dependency for mDNSResponder-108) flakes out on mDNSResponder, I think. I have more important issues right now than k3b (such as searching out docs for accessing my internal IOmega ZIP100 drive, seeing as the handbook only deals with USB, Optical (CD and DVD) and Floppy drives). I'll keep the list updated with my progress in getting k3b working (right now I get the following: [user1@hostname]k3b /libexec/ld-elf.so.1: Shared object "libkparts.so.3" not found, required by "k3b" which I'm hoping portmaster will fix). --=20 Yours In Christ, PIT Emails are not formal business letters, whatever businesses may want. --------------enig1E16FAF573A31063345AEF8F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJLghxLAAoJEENZQ8DH7rW0z1AIAJvg1uVWjOBEnmsCV+UHWHtE mj6XIeweWEim+Us4JVhcgsHFbuBKbi2c3mZKynB3DB9pJqpnY1MaIq1i5gaod5dS P3+1wh94oLtYDqeqPLlcYbkNbTSGYIfVMGfZ83gySmKiBuU2DUx5mvbmKAEPxCMT enHIkpwYMvQcNDIERdxAGyJ/U2tEVs9S5kw/6b69mqAZifiQBWAHE8S95d+5/7E1 a4ThmsSbvl9HWCGF3y7X+4kr09BOOXvXqMMKZ9CPSvQ/7FxCAP6vQKghXfPfK3En vTLwr0jhom11ph4fq05N+YdgJE3f3cZAHKD/0dBx9+47I78hNCf2vqJacnHF9NU= =pMsy -----END PGP SIGNATURE----- --------------enig1E16FAF573A31063345AEF8F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B821C3E.4060509>