Re: Portupgrade vs. multiple versions of packages
On Wed, Jan 01, 2003 at 03:01:43PM +1030, Brian Astill wrote: That upgrade is a doozie. Been there, done that! rm -fr qt2 is (I think) the correct thing to do (someone else on the list will correct me). Then port kde3. qt2 and qt3 will NOT live comfortably together. So delete qt2 and all the apps dependent on it (that includes kde2 and its apps). The kde3 port will look for the version of qt it needs, fail to find it, and fetch it for you. Ain't that nice? Do get confirmation of that rm command I listed, though. Brian, I think my problem was believing that portupgrade was smarter than it actually is... it's certainly way smarter than me though :-) Looks like my mistake was not completely purging the old qt2/kde2 before I started upgrading things. I'll blow away the Frankenstein's Monster install I have now and try again from a clean start. I'd still love to know if that extra +CONTENTS file is good for anything though... Thanks, Scott -- === Scott Mitchell | PGP Key ID | Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines [EMAIL PROTECTED] | 0xAA775B8B | -- Anon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Portupgrade vs. multiple versions of packages
On Wed, Jan 01, 2003 at 03:01:43PM +1030, Brian Astill wrote: Scott Mitchell wrote: Hi all, I've just spent a fun day upgrading ~180 ports that were about a year out of date, which will teach me not to be so lazy in future :-( Anyway, portupgrade coped with most of this mess admirably, except for (unsurprisingly) the KDE2 -- KDE3 upgrade. That upgrade is a doozie. Been there, done that! rm -fr qt2 is (I think) the correct thing to do (someone else on the list will correct me). Then port kde3. qt2 and qt3 will NOT live comfortably together. So delete qt2 and all the apps dependent on it (that includes kde2 and its apps). The kde3 port will look for the version of qt it needs, fail to find it, and fetch it for you. Ain't that nice? Do get confirmation of that rm command I listed, though. # cd / # rm -rf * No problems anymore. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Portupgrade vs. multiple versions of packages
Hi all,
I've just spent a fun day upgrading ~180 ports that were about a year out
of date, which will teach me not to be so lazy in future :-( Anyway,
portupgrade coped with most of this mess admirably, except for
(unsurprisingly) the KDE2 -- KDE3 upgrade.
Portupgrade simply refused to upgrade kdelibs-2.2.2 to the latest 3.0.5_1,
I suspect because the install required some file that portupgrade was
deinstalling along with the rest of 2.2.2, before it installed 3.0.5. So
in the end I just installed 3.0.5 on top of the old version, presumably
leaving various rubbish from the old installation on my system. This
allowed the rest of the upgrades to proceed happily.
Pkgdb moticed later that I had two kdelibs installed, and helpfully offered
to deregister one for me. I took it up on this, and ended up with a new
file +CONTENTS.kdelibs-2.2.2 under /var/db/pkg/kdelibs-3.0.5_1, alongside
the usual +CONTENTS for the new version.
First question: Will any of the pkg* tools make use of this file so that I
can, for example, deinstall the new version plus the leftover bits of the
old version, next time I upgrade?
Second question: If not, is there a nice automated way to find (and remove)
stray files left behind by old packages that weren't properly removed? I
could put together a script to find anything in /usr/{local,X11R6} that
doesn't belong to any installed package, but maybe this wheel has already
been invented?
Thanks in advance happy new year,
Scott
--
===
Scott Mitchell | PGP Key ID | Eagles may soar, but weasels
Cambridge, England | 0x54B171B9 | don't get sucked into jet engines
[EMAIL PROTECTED] | 0xAA775B8B | -- Anon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Portupgrade vs. multiple versions of packages
On Tuesday 31 December 2002 07:41 am, Scott Mitchell wrote:
Hi all,
I've just spent a fun day upgrading ~180 ports that were about a year
out of date, which will teach me not to be so lazy in future :-(
Anyway, portupgrade coped with most of this mess admirably, except
for (unsurprisingly) the KDE2 -- KDE3 upgrade.
Portupgrade simply refused to upgrade kdelibs-2.2.2 to the latest
3.0.5_1, I suspect because the install required some file that
portupgrade was deinstalling along with the rest of 2.2.2, before it
installed 3.0.5. So in the end I just installed 3.0.5 on top of the
old version, presumably leaving various rubbish from the old
installation on my system. This allowed the rest of the upgrades to
proceed happily.
Most of us upgraded to XFree86-4.x at the same time. The HEADSUP
instruction at the time were to completely delete both of them and then
upgrade install the new versions.
Kent
Pkgdb moticed later that I had two kdelibs installed, and helpfully
offered to deregister one for me. I took it up on this, and ended up
with a new file +CONTENTS.kdelibs-2.2.2 under
/var/db/pkg/kdelibs-3.0.5_1, alongside the usual +CONTENTS for the
new version.
First question: Will any of the pkg* tools make use of this file so
that I can, for example, deinstall the new version plus the leftover
bits of the old version, next time I upgrade?
Second question: If not, is there a nice automated way to find (and
remove) stray files left behind by old packages that weren't properly
removed? I could put together a script to find anything in
/usr/{local,X11R6} that doesn't belong to any installed package, but
maybe this wheel has already been invented?
Thanks in advance happy new year,
Scott
--
Kent Stewart
Richland, WA
http://users.owt.com/kstewart/index.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
Re: Portupgrade vs. multiple versions of packages
Brian Astill wrote: Scott Mitchell wrote: Hi all, I've just spent a fun day upgrading ~180 ports that were about a year out of date, which will teach me not to be so lazy in future :-( Anyway, portupgrade coped with most of this mess admirably, except for (unsurprisingly) the KDE2 -- KDE3 upgrade. That upgrade is a doozie. Been there, done that! rm -fr qt2 is (I think) the correct thing to do (someone else on the list will correct me). Then port kde3. qt2 and qt3 will NOT live comfortably together. So delete qt2 and all the apps dependent on it (that includes kde2 and its apps). The kde3 port will look for the version of qt it needs, fail to find it, and fetch it for you. Ain't that nice? it would probably make sense to subscribe to the kde-freebsd list. I have learned a lot from just lurking and they work hard to make sure KDE stays up to date. http://lists.csociety.org/listinfo/kde-freebsd -- Paul Beard: seeking UNIX/internet engineering work http://paulbeard.no-ip.org/paulbeard.html 8040 27th Ave NE Seattle WA 98115 / 206 529 8400 Although golf was originally restricted to wealthy, overweight Protestants, today it's open to anybody who owns hideous clothing. -- Dave Barry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
