Re: the art of pkgdb -F
Michael P. Soulier writes: Might as well paint PLEASE KICK ME! and an arrow pointing down on your back I'm used to binary-package distributions that seem to try a lot harder to not break. I suppose that ports is evolving, and it used to be worse, so I shouldn't complain. Still, if the handbook says to use portupgrade -R to upgrade a port, that's what BSD newbies like me are going to use. Don't mistake me - I use portupgrade, and recommend it to others. But I know from bitter experience it is /not/ bullet-proof. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On 28/03/07 Robert Huff said: But I bet I'm not the only one who, once upon a time, happened to try portupgrade -arR or equivalent after forgetting to read UPDATING and ended up with more to do than I originally thought. Might as well paint PLEASE KICK ME! and an arrow pointing down on your back I'm used to binary-package distributions that seem to try a lot harder to not break. I suppose that ports is evolving, and it used to be worse, so I shouldn't complain. Still, if the handbook says to use portupgrade -R to upgrade a port, that's what BSD newbies like me are going to use. I'm just glad that portupgrade has a -n switch. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgphORTxDiaJu.pgp Description: PGP signature
Re: the art of pkgdb -F
On Wed, 28 Mar 2007 00:19:47 -0500
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
but with training my computer is teaching me what
is right and what is not. I think.
... and I thought that's why I had stopped using Windows...hmmm ;)
_
{Beto|Norberto|Numard} Meijome
An invasion of armies can be resisted,
but not an idea whose time has come.
Victor Hugo
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On Wed, 28 Mar 2007 20:36:59 -0400 Michael P. Soulier [EMAIL PROTECTED] wrote: On 28/03/07 RW said: The gettext upgrade is actually a good example of what portupgrade offers. With portupgrade the -rf option is advisable, but not essential, with portmaster, it's essential that the -r option is used, If it's not, or the upgrade fails to complete, you can end-up with not much more than the base-system working. Wow. You would think that such tools would prevent you from getting into that situation. That is the beauty of portmanager. Just using the -p flag will guarantee that all dependencies are updated, no matter how far down the dependency's tree. Using the -u -p combination will get everything working correctly, although in the case of the 'gettext' update, it can involve a large number of applications being updated. -- Gerard This must be morning. I never could get the hang of mornings. signature.asc Description: PGP signature
Re: the art of pkgdb -F
On Thu, 29 Mar 2007 12:15:53 -0400 Gerard Seibert [EMAIL PROTECTED] wrote: On Wed, 28 Mar 2007 20:36:59 -0400 Michael P. Soulier [EMAIL PROTECTED] wrote: On 28/03/07 RW said: The gettext upgrade is actually a good example of what portupgrade offers. With portupgrade the -rf option is advisable, but not essential, with portmaster, it's essential that the -r option is used, If it's not, or the upgrade fails to complete, you can end-up with not much more than the base-system working. Wow. You would think that such tools would prevent you from getting into that situation. That is the beauty of portmanager. Just using the -p flag will guarantee that all dependencies are updated, no matter how far down the dependency's tree. Using the -u -p combination will get everything working correctly, although in the case of the 'gettext' update, it can involve a large number of applications being updated. Portmanager is really no better, the dependencies recorded in the package database are also recursive. The big problem with gettext was that a lot of port failed to build afterwards, leaving them with a missing library. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On Thu, 29 Mar 2007 20:40:05 +0100 RW [EMAIL PROTECTED] wrote: Portmanager is really no better, the dependencies recorded in the package database are also recursive. The big problem with gettext was that a lot of port failed to build afterwards, leaving them with a missing library. I have had problems in the past getting 'portupgrade' to properly update all of the dependencies required when doing a major update; i.e., 'gettext'. On the other hand, I have never had a problem using 'portmanager' provided I used the '-p -f' flags. Portmanager can update its list of ports that need updating on the fly. I do not believe that either portupdate or portmaster have that ability. I noticed that when doing the 'gettext' update, it twice recalculated the number of ports that needed to have their dependencies updated. It would probably behoove anyone prior to doing a massive update to clean out the '/usr/ports/distfiles' directory and possibly running 'portsclean -C -D -l -PP' to insure that any old crud was not laying around. It certainly couldn't hurt. Just my 2 cents. -- Gerard Be careful how you get yourself involved with persons or situations that can't bear inspection. signature.asc Description: PGP signature
Re: the art of pkgdb -F
On Thu, 29 Mar 2007 16:41:06 -0400 Gerard Seibert [EMAIL PROTECTED] wrote: On the other hand, I have never had a problem using 'portmanager' provided I used the '-p -f' flags. OPPS, should have been '-p -u' flags. -- Gerard signature.asc Description: PGP signature
Re: the art of pkgdb -F
On Thu, 29 Mar 2007 16:41:06 -0400 Gerard Seibert [EMAIL PROTECTED] wrote: On Thu, 29 Mar 2007 20:40:05 +0100 RW [EMAIL PROTECTED] wrote: Portmanager is really no better, the dependencies recorded in the package database are also recursive. The big problem with gettext was that a lot of port failed to build afterwards, leaving them with a missing library. I have had problems in the past getting 'portupgrade' to properly update all of the dependencies required when doing a major update; i.e., 'gettext'. On the other hand, I have never had a problem using 'portmanager' provided I used the '-p -f' flags. Your missing the point that when portupgrade fails to upgrade the dependent ports, it doesn't really matter because it has preserved copies of the old libraries. That allows software built against the old and new versions to co-exist until the underlying problem is fixed. I use portmanager myself, but no upgrade utility can guarantee that any port will build. I got into this problem myself - I couldn't start KDE. I got out of it by deleting gettext, reinstalling the old version with pkg_add -r, and re-upgrading gettext with portupgrade. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On Tue, 27 Mar 2007 21:17:13 -0400 Michael P. Soulier [EMAIL PROTECTED] wrote: I'm looking at http://www.freebsddiary.org/pkgdb.php while I run it myself. I'm finding wonderful questions like Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24 (security/p5-GSSAPI): p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no] I must ask. How the hell am I supposed to know?? I build that as a dependency of something that I built months ago. There's a good chance that I'll be simply guessing at all of the answers. Is it really useful to run this if you can't remember? And why am I remembering anyway? That's what a packaging system is for, isn't it? You can run: portmanager -u -p -l That will rebuild all broken and or missing dependencies for all of your ports. If you just want to correct a single port, try this: portmanager /port/name-of-port -p -l HTH -- Gerard Horner's Five Thumb Postulate: Experience varies directly with equipment ruined. signature.asc Description: PGP signature
Re: the art of pkgdb -F
Jeffrey Goldberg wrote:
On Mar 27, 2007, at 8:34 PM, Josh Carroll wrote:
Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24
(security/p5-GSSAPI):
p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no]
Well this one is pretty obvious. Look at what the stale dependency is,
and what it's suggesting? :)
To me it is entirely unclear. First of all, I don't know what stale
dependency is supposed to mean. Second, I don't know what score
means, and finally, I don't know what the question is that I'm to answer
yes, no or all to.
I could attempt, but it's easier to type See below.
So I've just taken to running with -Fa and hope for the best (and so far
everything has worked).
This makes you pretty normal, I expect.
If the answers to these questions are in the man page for pkgdb, I
apologize, but I haven't found them there.
Here is a time-honored and rather canonical diatribe on The Art of
Pkgdb -F (a great thread title, BTW). Note also that it is nearly
six years old, and that additional package-management tools have been
proposed, created, and released to the public, and some may have already
been EOL'ed and buried, but the rest of them aren't considered standard
by any means, and currently the FreeBSD world is in a pseudo-Biblical
every man did as he saw fit state these days[1].
http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html
Of course, (and here's a rather large can of worms), there weren't {m?}any
alternatives back in the day, the the tools that are 'officially' documented
became standard more or less by default. (and, come to think of it, are
they at all, if so, where, etc., etc.)
HTH, `cat flames /dev/null 21`,
Kevin Kinsey
[1] Since the punishment for these transgressions is basically just
a temporal make deinstall under /usr/ports followed by 2-4 days of
rebuilding, (more if KDE/GNOME is installed, but not much as opposed
to eternal flame/torment), I suppose it's OK to let everybody fend
for themselves with whatever tool they like best. One thing you'll
notice about the BSDs is that since they are traditional Unix-like
systems, a lot of folks stick to traditions pretty closely.
--
You need no longer worry about the future.
This time tomorrow you'll be dead.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On Wed, 28 Mar 2007 00:19:47 -0500 [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Obviously, as I am not about to batter you about the neck and head with the beam projecting from my eye (hold still, you've got a . . .), I can only suggest a decent cringepray manouver (as I execute from time to time), and a stout attempt to wean oneself off, albeit % portupgrade -fr blorf* is quite seductive, nearly doubly so when blorf* is actually gettext.arg.bah. ports-mgmt/portmaster disposes with the hairy databases and leering dependancies at the cost of being slightly less . . . err, come to think of it, after a bit of man page perusal I cannot think of anything that I use portupgrade for that portmaster seems to be missing. YMMV as usual. The gettext upgrade is actually a good example of what portupgrade offers. With portupgrade the -rf option is advisable, but not essential, with portmaster, it's essential that the -r option is used, If it's not, or the upgrade fails to complete, you can end-up with not much more than the base-system working. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On 28/03/07 Kevin Kinsey said: Here is a time-honored and rather canonical diatribe on The Art of Pkgdb -F (a great thread title, BTW). Note also that it is nearly six years old, and that additional package-management tools have been proposed, created, and released to the public, and some may have already been EOL'ed and buried, but the rest of them aren't considered standard by any means, and currently the FreeBSD world is in a pseudo-Biblical every man did as he saw fit state these days[1]. http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html I suppose I'm curious as to how my ports got into this state in the first place, since I would have expected a package managements system to have prevented it. Now, I've been upgrading ports via portupgrade -R port as suggested in the handbook. As -R upgrades only those packages that require those supplied, and not those that it requires, would that cause it? I'm wondering how my port dependencies became broken in the first place. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpEjniW1tlh0.pgp Description: PGP signature
Re: the art of pkgdb -F
On 28/03/07 RW said: The gettext upgrade is actually a good example of what portupgrade offers. With portupgrade the -rf option is advisable, but not essential, with portmaster, it's essential that the -r option is used, If it's not, or the upgrade fails to complete, you can end-up with not much more than the base-system working. Wow. You would think that such tools would prevent you from getting into that situation. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpGNniQrLuol.pgp Description: PGP signature
Re: the art of pkgdb -F
On 28/03/07 Gerard Seibert said: You can run: portmanager -u -p -l That will rebuild all broken and or missing dependencies for all of your ports. How does it know what ports are installed? Originally, I thought that the pkgdb was that source of information, so if it was gone, how could it be rebuilt? Obviously there is installed package metadata elsewhere. Just not sure where. If you just want to correct a single port, try this: portmanager /port/name-of-port -p -l Thanks. Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgpNiY0kiBlC7.pgp Description: PGP signature
Re: the art of pkgdb -F
Hi, On Wed, 28 Mar 2007 20:34:00 -0400, Michael P. Soulier wrote: Now, I've been upgrading ports via portupgrade -R port as suggested in the handbook. As -R upgrades only those packages that require those supplied, and not those that it requires, would that cause it? Be careful with your syntax: '-R' isn't consistent between pkg_info and portupgrade: Running 'pkg_info -R' will downward recurse, or show dependencies of the port in question, but 'portupgrade -R' will upward recurse and upgrade every port on which it depends - which often causes a _lot_ of ports to be rebuilt and is, in fact, the opposite of your description above. I've been caught by this before... regards -- Joel Hatton -- Infrastructure Manager | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On 28/03/07, Joel Hatton [EMAIL PROTECTED] wrote: Hi, On Wed, 28 Mar 2007 20:34:00 -0400, Michael P. Soulier wrote: Now, I've been upgrading ports via portupgrade -R port as suggested in the handbook. As -R upgrades only those packages that require those supplied, and not those that it requires, would that cause it? Be careful with your syntax: '-R' isn't consistent between pkg_info and portupgrade: Running 'pkg_info -R' will downward recurse, or show dependencies of the port in question, but 'portupgrade -R' will upward recurse and upgrade every port on which it depends - which often causes a _lot_ of ports to be rebuilt and is, in fact, the opposite of your description above. I've been caught by this before... In fact, as frequently the build looks for a binary, and portupgrade checks /var/db/pkg there can be some quite exciting results from a portupgrade -R if you have alternate dependancies. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
Michael P. Soulier wrote:
On 28/03/07 Kevin Kinsey said:
Here is a time-honored and rather canonical diatribe on The Art of
Pkgdb -F (a great thread title, BTW). Note also that it is nearly
six years old, and that additional package-management tools have been
proposed, created, and released to the public, and some may have already
been EOL'ed and buried, but the rest of them aren't considered standard
by any means, and currently the FreeBSD world is in a pseudo-Biblical
every man did as he saw fit state these days[1].
http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html
I suppose I'm curious as to how my ports got into this state in the first
place, since I would have expected a package managements system to have
prevented it.
Good point, perhaps --- if I understand the problem (and there is no
guarantee that I do), it would seem, upon a first, furtive, tentative
and cursory examination that the fact you might need to run pkgdb -F
violates the POLA. Maybe you should qualify and say I would have
expected a *perfect* package management system to
However, ports get moved, dropped, re-named, re-categorized and so on
(somewhat) frequently --- perhaps no *one* port, but taken as a whole
(what, +15K ports now?) the tree is rather a moving target. In the
case of a moved or deleted port, I see no particular way that you
would miss out on at least a missing origin warning from the pkgtools
after obtaining an updated tree.
Otherwise, I suppose that, canonically, if one does the right thing
every time, you might come close. But I bet I'm not the only one who,
once upon a time, happened to try portupgrade -arR or equivalent
after forgetting to read UPDATING and ended up with more to do than I
originally thought.
And, of course, this is the point where the various disciples/proponents
(and possibly even the maintainers/authors) of the increasing variety of
package management tools come forth to sing the praises of their
favorite software.
So far we've heard from portupgrade, portmanager, and portmaster.
Any portscout, managepkg, or porteasy advocates wanna speak up?
[What did I miss, and, no, sorry, I didn't read every pkg-descr]
As I mentioned earlier, it's no secret that:
1. The Ports Collection is large, dynamic, and somewhat complex.
2. Different tools exist for ports management (in fact, there are now
so many that a new ports category was recently created to store all of them).
3. One set of tools existed for a long time before the others pretty much
by itself, and became the accepted (or at least the documented) way to
upgrade 3rd-party software. It wasn't perfect, but it continues to be
improved, as do the newer management programs.
4. The future of package management remains to be seen, but the various
and occasional pitfalls of the system have given rise to varied paths
to package nirvana (I, for one, haven't yet decided which to take).
This is actually a Good Thing for BSD, insofar as it continues to
exemplify another UNIX principle, tools, not policy.
I might expect, given this philosophy, that development on several
programs for the management of installed 3rd-party software will
continue, and that, unless one shows itself to be very superior to
the others, a variety of programs will continue in general use, much
to the chagrin of the FDP people, who will have to decide if the
current approach should be changed, and, if so, how. Doesn't sound
like as much fun as, say, beachcombing on Fiji or strolling through
downtown {$nice_city} in spring, though.
Full circle, Kinda back to every man for himself ---
Kevin Kinsey
--
The things that interest people most are usually none of their business.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
Kevin Kinsey writes: But I bet I'm not the only one who, once upon a time, happened to try portupgrade -arR or equivalent after forgetting to read UPDATING and ended up with more to do than I originally thought. Might as well paint PLEASE KICK ME! and an arrow pointing down on your back Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
the art of pkgdb -F
I'm looking at http://www.freebsddiary.org/pkgdb.php while I run it myself. I'm finding wonderful questions like Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24 (security/p5-GSSAPI): p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no] I must ask. How the hell am I supposed to know?? I build that as a dependency of something that I built months ago. There's a good chance that I'll be simply guessing at all of the answers. Is it really useful to run this if you can't remember? And why am I remembering anyway? That's what a packaging system is for, isn't it? Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein pgp8MyUeIp4ep.pgp Description: PGP signature
Re: the art of pkgdb -F
On Tue, 27 Mar 2007 21:17:13 -0400 Michael P. Soulier [EMAIL PROTECTED] wrote: I'm looking at http://www.freebsddiary.org/pkgdb.php while I run it myself. I'm finding wonderful questions like Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24 (security/p5-GSSAPI): p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no] I must ask. How the hell am I supposed to know?? I build that as a dependency of something that I built months ago. There's a good chance that I'll be simply guessing at all of the answers. Is it really useful to run this if you can't remember? And why am I remembering anyway? That's what a packaging system is for, isn't it? Mike -- Michael P. Soulier [EMAIL PROTECTED] Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. --Albert Einstein when i come across those, i always just take the defaults. one time i tried to tell it what i thought, and i built myself into an endless loop of 'run pkgdb -F's. eventually i had to just delete a few things, reinstall a few things to correct it. ever since then, i just do what it says and hope for the best. 9 out of 10, it guesses right for me. hth, jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24 (security/p5-GSSAPI): p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no] Well this one is pretty obvious. Look at what the stale dependency is, and what it's suggesting? :) Sometimes it can be less clear, though. You just have to take a best guess, or look at the dependencies for the installed package with pkg_info. Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On Mar 27, 2007, at 8:34 PM, Josh Carroll wrote: Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24 (security/ p5-GSSAPI): p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no] Well this one is pretty obvious. Look at what the stale dependency is, and what it's suggesting? :) To me it is entirely unclear. First of all, I don't know what stale dependency is supposed to mean. Second, I don't know what score means, and finally, I don't know what the question is that I'm to answer yes, no or all to. So I've just taken to running with -Fa and hope for the best (and so far everything has worked). If the answers to these questions are in the man page for pkgdb, I apologize, but I haven't found them there. Cheers, -j ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On Tuesday 27 March 2007, Jeffrey Goldberg said: On Mar 27, 2007, at 8:34 PM, Josh Carroll wrote: Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24 (security/ p5-GSSAPI): p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no] In this case the port p5-Authen-SASL-2.09 is linked to p5-GSSAPI-0.24, but security/ p5-GSSAPI-0.24 doesn't exist. thus it's a stale dependency. It then searches what ports you do have installed and picks what it thinks is closest. In this case p5-Geography-Countries-1.4. the score is how close a match to the original dependency this choice is. In this case 26% which isn't a very good match. ([y]es/[n]o/[a]ll) [no] means Do I want to change the link to what's suggested? Yes No or All. All means every time a stale link to p5-GSSAPI-0.24 is found answer yes. And finally the last [no] is the default. Hitting enter will use this answer unless you change it. Unless you're sure of the replacement choice (it's just a version update etc...), don't blindly just choose yes. You can really shoot yourself in the foot and cause all kinds of build failures. If you're not sure, choose no and hit enter. It will then ask you if you want to reinstall the dependency it's looking for. Which would be a good choice in this case. Hope this helps, Beech Well this one is pretty obvious. Look at what the stale dependency is, and what it's suggesting? :) To me it is entirely unclear. First of all, I don't know what stale dependency is supposed to mean. Second, I don't know what score means, and finally, I don't know what the question is that I'm to answer yes, no or all to. So I've just taken to running with -Fa and hope for the best (and so far everything has worked). If the answers to these questions are in the man page for pkgdb, I apologize, but I haven't found them there. Cheers, -j ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
Beech Rintoul wrote: On Tuesday 27 March 2007, Jeffrey Goldberg said: On Mar 27, 2007, at 8:34 PM, Josh Carroll wrote: Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24 (security/ p5-GSSAPI): p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no] In this case the port p5-Authen-SASL-2.09 is linked to p5-GSSAPI-0.24, but security/ p5-GSSAPI-0.24 doesn't exist. thus it's a stale dependency. It then searches what ports you do have installed and picks what it thinks is closest. In this case p5-Geography-Countries-1.4. the score is how close a match to the original dependency this choice is. In this case 26% which isn't a very good match. ([y]es/[n]o/[a]ll) [no] means Do I want to change the link to what's suggested? Yes No or All. All means every time a stale link to p5-GSSAPI-0.24 is found answer yes. And finally the last [no] is the default. Hitting enter will use this answer unless you change it. Unless you're sure of the replacement choice (it's just a version update etc...), don't blindly just choose yes. You can really shoot yourself in the foot and cause all kinds of build failures. If you're not sure, choose no and hit enter. It will then ask you if you want to reinstall the dependency it's looking for. Which would be a good choice in this case. Hope this helps, Beech Well this one is pretty obvious. Look at what the stale dependency is, and what it's suggesting? :) To me it is entirely unclear. First of all, I don't know what stale dependency is supposed to mean. Second, I don't know what score means, and finally, I don't know what the question is that I'm to answer yes, no or all to. So I've just taken to running with -Fa and hope for the best (and so far everything has worked). If the answers to these questions are in the man page for pkgdb, I apologize, but I haven't found them there. Cheers, -j Stale's like lost, but IIRC the entry is still there or the current entry was properly updated to reflect the move. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: the art of pkgdb -F
On 27/03/07, Jonathan Horne [EMAIL PROTECTED] wrote: On Tue, 27 Mar 2007 21:17:13 -0400 Michael P. Soulier [EMAIL PROTECTED] wrote: I'm looking at http://www.freebsddiary.org/pkgdb.php while I run it myself. I'm finding wonderful questions like Stale dependency: p5-Authen-SASL-2.09 - p5-GSSAPI-0.24 (security/p5-GSSAPI): p5-Geography-Countries-1.4 (score:26%) ? ([y]es/[n]o/[a]ll) [no] I must ask. How the hell am I supposed to know?? I build that as a dependency of something that I built months ago. There's a good chance that I'll be simply guessing at all of the answers. Is it really useful to run this if you can't remember? And why am I remembering anyway? That's what a packaging system is for, isn't it? when i come across those, i always just take the defaults. one time i tried to tell it what i thought, and i built myself into an endless loop of 'run pkgdb -F's. eventually i had to just delete a few things, reinstall a few things to correct it. ever since then, i just do what it says and hope for the best. 9 out of 10, it guesses right for me. Not to put too fine a point on it, but pkgdb(1) et al are part of an occasionally tempermental third party package management system. Built on ruby. Obviously, as I am not about to batter you about the neck and head with the beam projecting from my eye (hold still, you've got a . . .), I can only suggest a decent cringepray manouver (as I execute from time to time), and a stout attempt to wean oneself off, albeit % portupgrade -fr blorf* is quite seductive, nearly doubly so when blorf* is actually gettext.arg.bah. ports-mgmt/portmaster disposes with the hairy databases and leering dependancies at the cost of being slightly less . . . err, come to think of it, after a bit of man page perusal I cannot think of anything that I use portupgrade for that portmaster seems to be missing. YMMV as usual. Well, portmaster seems to have rather different notions of how flags apply than do I (it seems to enjoy recusring through dependancies when I was nearly certain I did not set that flag, several times) but with training my computer is teaching me what is right and what is not. I think. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
