Re: KDE issues after recent portupgrade
On Sun, 23 Jan 2005 11:59, Trey Sizemore wrote: From the /usr/ports/UPDATING entry: 20040313: AFFECTS: users of textproc/expat2 AUTHOR: [EMAIL PROTECTED] Users of expat2 (and its many dependencies) should do the following to properly update expat2 and all of its dependencies: portupgrade -rf textproc/expat2 I did the mentioned portupgrade above and a *lot* of packages were reinstalled, among those KDE. I'm not sure in retrospect that I needed to do this as I only installed FreeBSD on this box a couple of months ago. Anyway, since the upgrade Konqueror crashes when started in a directory (core dumps) as a file browser, KDE notifications no longer work (although sound from Gnome apps *do* work - I have gnome-session-daemon start when I log into KDE) and k3b won't start any longer for starters. What would be the best way to try an rectify this? Reinstall kde from scratch with a 'portupgrade -rf /usr/ports/X11/kde3' or something else entirely? All the aforementioned apps were working prior to the portupgrade command mentioned in UPDATING. You could try removing the kde packages install packages instead - the FreeBSD-KDE people seem to suggest that's the prefered method for KDE. See http://rabarber.fruitsalad.org/index.html for the correct PACKAGESITE setting to use with portupgrade. Having said that, the latest ports have some more recent updates, so kdenetwork one or two others will still need to be compliled from ports to get you fully up to date. I've found that method to work well for me it saves a hell of a lot of compilation time! Cheers, -- Ian GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc pgpZA9bKbVHUe.pgp Description: PGP signature
Re: KDE issues after recent portupgrade
On Sun, 2005-01-23 at 20:52 +1030, Ian Moore wrote: You could try removing the kde packages install packages instead - the FreeBSD-KDE people seem to suggest that's the prefered method for KDE. snip What is the 'best'/'easiest' way to uninstall kde ports and then do a fresh reinstall? -- Cheers, Trey --- Men do not differ much about what things they will call evils; they differ enormously about what evils they will call excusable. -- GK Chesterton 11:22AM up 2:51, 0 users, load averages: 0.01, 0.03, 0.02 FreeBSD salamander.thesizemores.net 5.3-STABLE i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Sunday 23 January 2005 08:23 am, Trey Sizemore wrote: On Sun, 2005-01-23 at 20:52 +1030, Ian Moore wrote: You could try removing the kde packages install packages instead - the FreeBSD-KDE people seem to suggest that's the prefered method for KDE. snip What is the 'best'/'easiest' way to uninstall kde ports and then do a fresh reinstall? To not uninstall them, but to properly upgrade your installed ports with sysutils/portmanager. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Sun, 2005-01-23 at 08:30 -0800, Michael C. Shultz wrote: To not uninstall them, but to properly upgrade your installed ports with sysutils/portmanager. I'd tried with portupgrade, but it seems that is what caused the most recent issues. I've not used portmanager before. Would that be a better alternative to portupgrade? -- Cheers, Trey --- It is easier to forgive an enemy than to forgive a friend. William Blake 11:38AM up 3:06, 0 users, load averages: 0.40, 0.16, 0.07 FreeBSD salamander.thesizemores.net 5.3-STABLE i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Sunday 23 January 2005 08:40 am, you wrote:
On Sun, 2005-01-23 at 08:30 -0800, Michael C. Shultz wrote:
To not uninstall them, but to properly upgrade your installed ports
with
sysutils/portmanager.
I'd tried with portupgrade, but it seems that is what caused the most
recent issues. I've not used portmanager before. Would that be a
better alternative to portupgrade?
Yes. portupgrade screws up the port registration files when you run
pkgdb -F. These are the files in /var/db/pkg/{portname}/+CONTENTS
Portmanager does not mess with the registration files and can usually
straighten out the damage caused by pkgdb -F. As portmanager runs it
gives you good feedback on what it is doing and why, and if you
disagree or just question something it is perfectly safe to ctrl-C out
of it. When start again and it will just pick up from when you left
off.
-Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Sun, 2005-01-23 at 08:41 -0800, Michael C. Shultz wrote:
Yes. portupgrade screws up the port registration files when you run
pkgdb -F. These are the files in /var/db/pkg/{portname}/+CONTENTS
Portmanager does not mess with the registration files and can usually
straighten out the damage caused by pkgdb -F. As portmanager runs it
gives you good feedback on what it is doing and why, and if you
disagree or just question something it is perfectly safe to ctrl-C
out
of it. When start again and it will just pick up from when you left
off.
So as a general rule, it appears I would just cvsup my ports as usual
and then use 'portmanager -u' rather than 'portupgrade -arR'. No more
need for portsdb -u and pkgdb -F then?
--
Cheers,
Trey
---
Humor is the only test of gravity, and gravity of humor; for a subject
which will not bear raillery is suspicious, and a jest which will not
bear serious examination is false wit.
-- Aristotle
11:50AM up 3:18, 0 users, load averages: 0.05, 0.07, 0.07
FreeBSD salamander.thesizemores.net 5.3-STABLE i386
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Sunday 23 January 2005 08:53 am, Trey Sizemore wrote:
On Sun, 2005-01-23 at 08:41 -0800, Michael C. Shultz wrote:
Yes. portupgrade screws up the port registration files when you run
pkgdb -F. These are the files in /var/db/pkg/{portname}/+CONTENTS
Portmanager does not mess with the registration files and can
usually straighten out the damage caused by pkgdb -F. As
portmanager runs it gives you good feedback on what it is doing and
why, and if you disagree or just question something it is perfectly
safe to ctrl-C out
of it. When start again and it will just pick up from when you
left off.
So as a general rule, it appears I would just cvsup my ports as usual
and then use 'portmanager -u' rather than 'portupgrade -arR'. No
more need for portsdb -u and pkgdb -F then?
Correct.
-Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Sun, 2005-01-23 at 08:30 -0800, Michael C. Shultz wrote: To not uninstall them, but to properly upgrade your installed ports with sysutils/portmanager. -Mike Did a 'portmanager -u' and still having the same issues with k3b and konq. -- Cheers, Trey --- The world is full of obvious things which nobody by any chance ever observes. -- Sir Arthur Conan Doyle 3:42PM up 9 mins, 0 users, load averages: 0.17, 0.18, 0.11 FreeBSD salamander.thesizemores.net 5.3-STABLE i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Sunday 23 January 2005 12:43 pm, Trey Sizemore wrote: On Sun, 2005-01-23 at 08:30 -0800, Michael C. Shultz wrote: To not uninstall them, but to properly upgrade your installed ports with sysutils/portmanager. -Mike Did a 'portmanager -u' and still having the same issues with k3b and konq. Try setting up a different user account on your machine then see how kde works with it. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Sun, 2005-01-23 at 13:04 -0800, Michael C. Shultz wrote: Try setting up a different user account on your machine then see how kde works with it. The new user had an artsd.core and kdeint.core file in their home directory when I logged in using their account. Starting up k3b from their account created a k3b.core file and k3b was not started. :-( -- Cheers, Trey --- When you have robbed a man of everything, he is no longer in your power. He is free again. -- Alexander Solzhenitsyn 5:01PM up 28 mins, 0 users, load averages: 0.36, 0.26, 0.21 FreeBSD salamander.thesizemores.net 5.3-STABLE i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Sunday 23 January 2005 02:03 pm, Trey Sizemore wrote: On Sun, 2005-01-23 at 13:04 -0800, Michael C. Shultz wrote: Try setting up a different user account on your machine then see how kde works with it. The new user had an artsd.core and kdeint.core file in their home directory when I logged in using their account. Starting up k3b from their account created a k3b.core file and k3b was not started. :-( I guess you should try to install kde from packages and see if that works, else you've little choice but to start over by deleting and reinstalling all its dependencies which means you might as well remove everthing and start over. Sorry I don't have anything better to offer. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Mon, 24 Jan 2005 02:53, Trey Sizemore wrote: On Sun, 2005-01-23 at 20:52 +1030, Ian Moore wrote: You could try removing the kde packages install packages instead - the FreeBSD-KDE people seem to suggest that's the prefered method for KDE. snip What is the 'best'/'easiest' way to uninstall kde ports and then do a fresh reinstall? Looking at what's been happening in this thread since I last checked my mail, I gather you are now faced with doing this. I'm no expert, but I'd say cd to each of the ports directories and do a make deinstall. Do all the kde ports, leaving the kde3 metaport till last. Then make deinstall quanta, arts qt. Now set your PACKAGESITE env. variable as per the instructions on fruitsalad. Then pkg_add qt, arts, kdelibs, kdebase, kdenetwork, then the other kde ports, quanta finally the kde metaport. Hope that helps. Cheers, -- Ian Moore GPG Key: http://homepages.picknowl.com.au/imoore/imoore.asc pgppFbzLaYG1X.pgp Description: PGP signature
Re: KDE issues after recent portupgrade
Well, you could either try to debug the applications that dont work, or take a look in the UPDATING file again, maybe they have descriptions concerning your applications... you could also try to do a cvsup and then a portupgrade -af and look if it goes through and things work afterwards again... hope that helps you any further... Greetings Oliver Leitner Technical Staff http://www.shells.at On Sunday 23 January 2005 02:29, you wrote: From the /usr/ports/UPDATING entry: 20040313: AFFECTS: users of textproc/expat2 AUTHOR: [EMAIL PROTECTED] Users of expat2 (and its many dependencies) should do the following to properly update expat2 and all of its dependencies: portupgrade -rf textproc/expat2 I did the mentioned portupgrade above and a *lot* of packages were reinstalled, among those KDE. I'm not sure in retrospect that I needed to do this as I only installed FreeBSD on this box a couple of months ago. Anyway, since the upgrade Konqueror crashes when started in a directory (core dumps) as a file browser, KDE notifications no longer work (although sound from Gnome apps *do* work - I have gnome-session-daemon start when I log into KDE) and k3b won't start any longer for starters. What would be the best way to try an rectify this? Reinstall kde from scratch with a 'portupgrade -rf /usr/ports/X11/kde3' or something else entirely? All the aforementioned apps were working prior to the portupgrade command mentioned in UPDATING. -- By reading this mail you agree to the following: using or giving out the email address and any other info of the author of this email is strictly forbidden. By acting against this agreement the author of this mail will take possible legal actions against the abuse. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Sun, 2005-01-23 at 02:30 +0100, Oliver Leitner wrote: Well, you could either try to debug the applications that dont work, or take a look in the UPDATING file again, maybe they have descriptions concerning your applications... Didn't see anything in the UPDATING file when I looked... you could also try to do a cvsup and then a portupgrade -af and look if it goes through and things work afterwards again... Well, portupgrade -af would force an upgrade of everything, right? I thought I'd try just KDE first, but that's something to fall back on. hope that helps you any further... -- Cheers, Trey --- This wasn't just plain terrible, this was fancy terrible. This was terrible with raisins in it. -- Dorothy Parker 9:01PM up 53 mins, 0 users, load averages: 0.03, 0.01, 0.00 FreeBSD salamander.thesizemores.net 5.3-STABLE i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: KDE issues after recent portupgrade
On Saturday 22 January 2005 05:29 pm, Trey Sizemore [EMAIL PROTECTED] wrote: From the /usr/ports/UPDATING entry: 20040313: AFFECTS: users of textproc/expat2 AUTHOR: [EMAIL PROTECTED] Users of expat2 (and its many dependencies) should do the following to properly update expat2 and all of its dependencies: portupgrade -rf textproc/expat2 I did the mentioned portupgrade above and a *lot* of packages were reinstalled, among those KDE. I'm not sure in retrospect that I needed to do this as I only installed FreeBSD on this box a couple of months ago. Anyway, since the upgrade Konqueror crashes when started in a directory (core dumps) as a file browser, KDE notifications no longer work (although sound from Gnome apps *do* work - I have gnome-session-daemon start when I log into KDE) and k3b won't start any longer for starters. What would be the best way to try an rectify this? Reinstall kde from scratch with a 'portupgrade -rf /usr/ports/X11/kde3' or something else entirely? All the aforementioned apps were working prior to the portupgrade command mentioned in UPDATING. I would uninstall all the KDE ports and then reinstall them, starting with kdelibs3, then kdebase3, then the rest. If KDE's installed in the right order it does alright, but even installing the kde3 metaport misses some dependencies, and when doing an upgrade like this it's often not done in the right order. This could cause some breakage. After installing kdelibs3, kdebase3 and QT, you might be able to install the metaport from there to get the rest, but I personally avoid it until after installing everything, as it's always given me problems. - jt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
