On Monday 03 March 2003 02.19, Cliff Sarginson wrote: > Hello, > Ok so portupgrde did not work in installing the latest KDE. > I cannot get KDE to run at all. > I get errors about libintl being missing. > Plus a mysterious and new requirement to tell make I have a Matrox 450 > card.
That's not a requirement, it's an option, if you want special support for that card from something that offers it. Probably X itself, certainly nothing related to KDE. *What* says libintl is missing? which binary? there is no binary called "KDE", something specifically must be giving these problems. Does upgrading gettext help. You *need* to keep your dependencies up to date as well as the port you're trying to upgrade, these things are not developed in a vacuum. > Plus the fact I cannot even re-intall KDE from the 4.7 ISO CD's. > I get the highly useful message "Error -1". From what? The CD-Rom drive? KDE? What KDE binary? From pkg_add? from Portupgrade? from tcsh? From Raelian clones? Who knows. > Now, correct me if I am wrong. > The tag for ports should always be ".", since the do not follow any kind > of upgrade system like the release does. > Why does portupgrade try to find 4.8-PRELEASE ports ? > This is nonsense. > From where is it getting this idea ? uname -a Because you are trying to make it install packages, for a branch that doesn't exist yet. I honestly could explain this, but it would take more time than I have this precise minute, and wouldn't help you fix anything anyway. So here's my "Lauri's rules to upgrading ports and stuff" 1: Don't mix pkg_add -r and portupgrade, you *will* have problems. You can mix "make install" and portupgrade, in most cases. 2: Run pkgdb -F before you try to do anything. Follow it's instructions to the letter. *Fix* your pkgdb before you continue. If you don't understand what it's asking you, cut and paste what it says into an email and ask. Don't give anecdotes or paraphrase the errors, if you do we *cannot* help you. 3: Have an up to date portsdb -u. Run it after every cvsup. Most everyone will advise you do "portsdb -Uu" and it won't hurt if you do, but it will take exponentially longer. You'll have a shiny up to date index out of it though. portsdb -u is the one that portupgrade needs to be up to date to work effectively. Ignore the complaints it makes about anything, you only have an actual problem if it fails to complete it's run. If it actually fails, cut and paste what it says into an email and ask. Don't give anecdotes or paraphrase the errors, if you do we *cannot* help you. 4: Don't try to upgrade piecemeal if other ports are out of date. The problem you describe above probably relate to a out of date dependency ports, but I can't be totally sure without the info from "pkg_info -Ia". Don't paraphrase that output, cut and paste it into an email, or I can't help you (are you seeing a pattern here?) *ALL* dependencies must be up to date, before you try to upgrade something like KDE. It probably won't build with an old version of anything that it depends on, and if it does, it might not work. If you really have your system in such a mess as I suspect, it's amazing anything is working. You can get in a situation where a particular binary finds it is missing a particular library dependency (your libintl problem) if you install a binary package that was built with a different *version* of the library than the one you now have installed. pkgdb -F will show you these as "stale dependencies", but it can't necessarily fix them, because this is something that can only be fixed by recompiling. You have two choices: 4a: Recompile the affected binary package against the currently installed version of the library, 4b: Reinstall packages of *both* the binary and the library, that were built against each other. Taking that second option, will likely cause the problem to reappear in anything else you've built locally. This is precisely why I say don't mix pkg_add and portupgrade/make install - use one way, or use the other, or be prepared to spend endless hours fixing things by hand. 5: Report build problems with ports *to the maintainer* with the output of "pkg_info -Ia", the output of "uname -a", the output of configure from the affected port (run it again with script, if you must) and config.log from the wrkdir. With these things, we stand a really good chance of diagnosing your problems. Don't paraphrase any of the error logs, cut and paste them. We really can't help you without them. 6: If you've done "make build" in a port and it fails, do this: make clean cvsup your ports try it again *BEFORE* you report a problem. If you've done portupgrade in a port, do the above anyway. If you really want your system fixed, and to understand how to safely upgrade things in place, you need to learn how to complain and report problems effectively. I highly suggest the following pages as reading, right now, before you go any further: How to Ask Questions the Smart Way: http://catb.org/~esr/faqs/smart-questions.html How to Report Bugs Effectively: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html Writing FreeBSD Problem Reports: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html Regards, -- Lauri Watts KDE Documentation: http://i18n.kde.org/doc/ KDE on FreeBSD: http://freebsd.kde.org/
pgp00000.pgp
Description: signature
