Re: Stale Dependencies ??????
On Saturday 24 June 2006 12:27, Robert Davison wrote: I've recently had a few problems with KDE 3.5.1, so recently upgraded to 3.5.3 via the ports. I have a port upgrade script which is producing the following output when executed. Stale dependency: gconf2-2.14.0_2 -- openldap-client-2.2.30 -- manually run 'pkgdb -F' to fix, or specify -O to force. now upgrading the required ports Stale dependency: gconf2-2.14.0_2 -- openldap-client-2.2.30 -- manually run 'pkgdb -F' to fix, or specify -O to force. Could someone please explain what is happening here. If I run pkgdb -F I get the following output (pressing enter to accept the default) luey# pkgdb -F --- Checking the package registry database Stale origin: 'devel/gnu-libtool': perhaps moved or obsoleted. - The port 'devel/gnu-libtool' was removed on 2006-06-05 because: Has expired: devel/libtool15 is now stock and should be used instead - Hint: gnu-libtool-1.5.20 is required by the following package(s): kdevelop-3.3.1_1 - Hint: checking for overwritten files... - No files installed by gnu-libtool-1.5.20 have been overwritten by other packages. Deinstall gnu-libtool-1.5.20 ? [no] You should be able to answer YES to this question. Stale dependency: gconf2-2.14.0_2 - openldap-client-2.2.30 (net/openldap22-client): openldap-client-2.3.24 (score:76%) ? ([y]es/[n]o/[a]ll) [no] New dependency? (? to help): Skip this? ([y]es/[n]o/[a]ll) [yes] Skipped. Stale dependency: kde-3.5.3 - libexif-0.6.13 (graphics/libexif): libxslt-1.1.17 (score:17%) ? ([y]es/[n]o/[a]ll) [no] New dependency? (? to help): Skip this? ([y]es/[n]o/[a]ll) [yes] Skipped. Stale dependency: kde-3.5.3 - poppler-0.5.3 (graphics/poppler): popt-1.7_1 (score:18%) ? ([y]es/[n]o/[a]ll) [no] New dependency? (? to help): Skip this? ([y]es/[n]o/[a]ll) [yes] Skipped. Stale dependency: kde-3.5.3 - poppler-qt-0.5.3 (graphics/poppler-qt): popt-1.7_1 (score:18%) ? ([y]es/[n]o/[a]ll) [no] New dependency? (? to help): Skip this? ([y]es/[n]o/[a]ll) [yes] Skipped. Stale dependency: kdeartwork-3.5.1_1 - openldap-client-2.2.30 (net/openldap22-client): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdesdk-3.5.1_1 - openldap-client-2.2.30 (net/openldap22-client): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdeutils-3.5.1_1 - openldap-client-2.2.30 (net/openldap22-client): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: kdevelop-3.3.1_1 - openldap-client-2.2.30 (net/openldap22-client): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: libgsf-1.14.1 - openldap-client-2.2.30 (net/openldap22-client): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: samba-libsmbclient-3.0.22 - openldap-client-2.2.30 (net/openldap22-client): Skip this? ([y]es/[n]o/[a]ll) [yes] Stale dependency: wv2-0.2.2_3 - openldap-client-2.2.30 (net/openldap22-client): Skip this? ([y]es/[n]o/[a]ll) [yes] Try running: pkgdb --autofix That should take care of the easily fixed dependency problems. -- Gerard Seibert [EMAIL PROTECTED] Encyclopedia for sale by father. Son knows everything. pgpBwzGhREP2k.pgp Description: PGP signature
Re: Stale Dependencies ??????
On Jun 24, 2006, at 9:41 AM, Gerard Seibert wrote: On Saturday 24 June 2006 12:27, Robert Davison wrote: I've recently had a few problems with KDE 3.5.1, so recently upgraded to 3.5.3 via the ports. I have a port upgrade script which is producing the following output when executed. Stale dependency: gconf2-2.14.0_2 -- openldap-client-2.2.30 -- manually run 'pkgdb -F' to fix, or specify -O to force. now upgrading the required ports Stale dependency: gconf2-2.14.0_2 -- openldap-client-2.2.30 -- manually run 'pkgdb -F' to fix, or specify -O to force. Could someone please explain what is happening here. If I run pkgdb -F I get the following output (pressing enter to accept the default) I've had the hardest time understanding what pkgdb asks. This is the only article I've found which makes some sense to me: http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html?page=1 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stale Dependencies ??????
On Saturday 24 June 2006 13:11, vayu wrote: On Jun 24, 2006, at 9:41 AM, Gerard Seibert wrote: //snip// I've had the hardest time understanding what pkgdb asks. This is the only article I've found which makes some sense to me: http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html?page=1 I once had a problem on FSBD 5.4 that was so bad that I finally used portmanager to clean it up. portmanager -u -f -y -l That corrected everything. However, it did take a couple of days to rebuild the entire system. Ciao! -- Gerard Seibert [EMAIL PROTECTED] Reporter, n.: A writer who guesses his way to the truth and dispels it with a tempest of words. Ambrose Bierce, The Devil's Dictionary ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stale dependencies in pkgdb
Andrew wrote:
On Fri, 2006-02-10 at 11:42 -0500, Robert Huff wrote:
Andrew writes:
I've run pkgdb -F as portupgrade suggests, deleting stale
dependencies, but they seem to keep reappearing.
I'm not an expert on pkgdb, but I'm pretty sure that's the way
it works.
You need to fix, not delete, the stale dependencies. This may
take some effort the first time around.
Beyond that, I question the wisdom of any automatic
solution. There are definitely times when I do _not_ want to accept
the fixes proposed by pkgdb -F.
My apologies; I re-read the man pages for portupgrade and pkgdb and I
think I understand what's going on now. Thanks anyway...
-Andrew
A good solution in the long term, rather than fixing dependencies every
time you do an upgrade, is to look at the ALT_PKGDEP section of
pkgtools.conf. Here is how i addressed the cdrtools dependency you
mentioned.
ALT_PKGDEP = {
'cdr-tools*' = 'cjk-cdrtools*',
'pcre-*' = 'pcre-utf8',
}
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [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: stale dependencies in pkgdb
On Friday 10 February 2006 20:35, Andrew wrote: think I've got it now. I believe I was correct in thinking that portupgrade usually takes care of dependencies; the portion that I was missing was that pkgdb catches what discrepancies do appear between what is installed and what is required. Try portmanager instead. Portupgrade, and the other package-tools installed by the portupgrade port, are highly dependent on the package database and need it to self-consistent. Portmanger uses the information in the port makefiles instead, which makes it much more robust. This also means it's working from information about how thing should be, rather than how they are/were. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stale dependencies in pkgdb
On Fri, 2006-02-10 at 11:42 -0500, Robert Huff wrote: Andrew writes: I've run pkgdb -F as portupgrade suggests, deleting stale dependencies, but they seem to keep reappearing. I'm not an expert on pkgdb, but I'm pretty sure that's the way it works. You need to fix, not delete, the stale dependencies. This may take some effort the first time around. Beyond that, I question the wisdom of any automatic solution. There are definitely times when I do _not_ want to accept the fixes proposed by pkgdb -F. I guess what is unclear to me is how I go about fixing the stale dependencies. I was under the impression that portupgrade would take care of the dependencies for a particular port, and the stale dependency was just an error in the package database (pkgdb). Is this not the case? Thank-you, Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stale dependencies in pkgdb
On Friday 10 February 2006 12:41, Andrew wrote: On Fri, 2006-02-10 at 11:42 -0500, Robert Huff wrote: Andrew writes: I've run pkgdb -F as portupgrade suggests, deleting stale dependencies, but they seem to keep reappearing. I'm not an expert on pkgdb, but I'm pretty sure that's the way it works. You need to fix, not delete, the stale dependencies. This may take some effort the first time around. Beyond that, I question the wisdom of any automatic solution. There are definitely times when I do _not_ want to accept the fixes proposed by pkgdb -F. I guess what is unclear to me is how I go about fixing the stale dependencies. I was under the impression that portupgrade would take care of the dependencies for a particular port, and the stale dependency was just an error in the package database (pkgdb). Is this not the case? Thank-you, Andrew ___ A stale dependency can be a required program that's old, or it can be that there are two versions of the required program listed as installed in pkgdb, or it can be the required program was removed by another program and something else installed in its place and the dependcies not upgraded in pkgdb. 'pkgdb -F' will fix the problems it can safely fix. What it won't fix is a dependcency on a program that's been removed. You need to look at that message and figure out what's going on and correct the problem. Skipping or deleting the dependency is not taking care of the problem, it's just getting out of 'pkgdb -F'. Portupgrade - depending on how you used it - takes care of dependcies. A stale dependency is not an error in pkgdb. Something is wrong and you have to fix it. By the way, portaudit is a fine tool, but sometimes it gets in the way of what you want to do. It can prevent you from installing or upgrading some program that you want to. I can't say you would be better off without it, but I very seldom use it. Don ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stale dependencies in pkgdb
On Fri, 2006-02-10 at 11:42 -0500, Robert Huff wrote: Andrew writes: I've run pkgdb -F as portupgrade suggests, deleting stale dependencies, but they seem to keep reappearing. I'm not an expert on pkgdb, but I'm pretty sure that's the way it works. You need to fix, not delete, the stale dependencies. This may take some effort the first time around. Beyond that, I question the wisdom of any automatic solution. There are definitely times when I do _not_ want to accept the fixes proposed by pkgdb -F. My apologies; I re-read the man pages for portupgrade and pkgdb and I think I understand what's going on now. Thanks anyway... -Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stale dependencies in pkgdb
On Fri, 2006-02-10 at 15:11 -0500, Robert Huff wrote: Andrew writes: I guess what is unclear to me is how I go about fixing the stale dependencies. I was under the impression that portupgrade would take care of the dependencies for a particular port, and the stale dependency was just an error in the package database (pkgdb). Is this not the case? My understanding of how things work: Consider two ports a and b, such that a-4.6 is a dependency for b-2.2. If a updates to 4.7, and I run portupgrade -r a, b will also be updated. But if I run portupgrade a (or there's a bug in the programs/ scripts) b will not update ... and pkgdb will complain about about a stale (i.e. unsatisified) dependency. This also happens when you replace one port with another that provides the same functionality. For example: many gnome ports depend on openldap. But I use openldap-sasl - and every time I update one of those ports I have to manually correct the dependency. (There's probably a way to do that automatically, but I haven't figured out how.) And now there's a stale dependency. This can be expecially frustrating if the dependant port hasn't been updated for years; the required port may have been upgraded beyond recognition, no longer available, absorbed into another port, etc.. As to how, try this as a first approximation. Run [kgdb -f, and reply no to all changes. Write down the port:dependency pairs, and then anaylze the dependencies. Has it been installed. but not registered? Replaced by a newer version? Two useful files are /usr/ports/UPDATING and /usr/ports/MOVED. My response here is mostly guesswork, educated by several years of doing this and sometimes asking for help. In the case above, fixing a-4.6 with a-4.7 is usually a no-brainer. Fixing a-4.6 with a-5.0, however, would require reseaech (and warrant keeping a backup of the pkgdb). Sorry; just fired off a message to the list before I got this one... Anyway, I think I've got it now. I believe I was correct in thinking that portupgrade usually takes care of dependencies; the portion that I was missing was that pkgdb catches what discrepancies do appear between what is installed and what is required. One of the ports that was giving me troubles was gamin; which I've just noticed seems to be similar to your situation with openldap-sasl (gamin/fam). Another was cdrtools (cdrtools/cjk-cdrtools). I've corrected both manually using pkgdb -F, which I think solves my problem (for now, at least :-) ). Thank you for your help! -Andrew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stale dependencies in pkgdb
--- Andrew [EMAIL PROTECTED] wrote: On Fri, 2006-02-10 at 11:42 -0500, Robert Huff wrote: Andrew writes: I've run pkgdb -F as portupgrade suggests, deleting stale dependencies, but they seem to keep reappearing. I'm not an expert on pkgdb, but I'm pretty sure that's the way it works. You need to fix, not delete, the stale dependencies. This may take some effort the first time around. Beyond that, I question the wisdom of any automatic solution. There are definitely times when I do _not_ want to accept the fixes proposed by pkgdb -F. My apologies; I re-read the man pages for portupgrade and pkgdb and I think I understand what's going on now. Ok, but be more careful next time. __ Find your next car at http://autos.yahoo.ca ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stale dependencies
Mark Withers wrote: Hello everyone! I've been using FBSD for a few years now, but am not sure as to what a 'stale dependency' is... I am receiving an error message with ymessenger pkg that it has stale dependencies and to use 'pkgdb -F' to fix or -O to force. I'm a bit inexperienced when it comes to repairing the package db and would appreciate any pointers you can give. http://www.onlamp.com/pub/a/bsd/2001/11/29/Big_Scary_Daemons.html Pretty good explanation by Michael Lucas of Absolute BSD fame KDK ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: stale dependencies
On Saturday 21 August 2004 2:22 am, Mark Withers wrote: Hello everyone! I've been using FBSD for a few years now, but am not sure as to what a 'stale dependency' is... I am receiving an error message with ymessenger pkg that it has stale dependencies and to use 'pkgdb -F' to fix or -O to force. I'm a bit inexperienced when it comes to repairing the package db and would appreciate any pointers you can give. Thanks for listening... Mark Stale dependency means portupgrade doesn't recognize the dependency port used to build the listed port. It wants you to use pkgdb -F so it can force the dependency to be something portupgrade recognizes. Though your listed port was built with a stale (out of date) dependency port, portupgrade wants to change so that it looks like the listed port was built with a current up to date dependency. A better approach is to rebuild the port with newer, up to date dependency ports that are not stale. I suggest you get a current cvsup then update your port collection with sysutils/portmanager, it will rebuild your ports with only up to date dependencies. -Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
