In <[EMAIL PROTECTED]>, [EMAIL PROTECTED] typed:
> I just upgrade XFree86 from 4.2 to 4.3 using portupgrade on 2 different
> machines.
That statement doesn't make sense. Portupgrade upgrades pors, not the
system. So you can't upgrade from 4.2 to 4.3 with portupgrade. If you
actually upgraded the
In <[EMAIL PROTECTED]>, Cliff Sarginson <[EMAIL PROTECTED]> typed:
> Portupgrade has too many ways it can go wrong for mere mortals.
> I have offered to re-write it.
> It will be a mega-project, but my offer is serious.
> And ruby (don't take our love to town) will place a less than significant
> r
On Tue, Mar 04, 2003 at 05:06:44PM +0100, Cliff Sarginson wrote:
> On Tue, Mar 04, 2003 at 10:00:08AM +0100, Stijn Hoop wrote:
> >
> > Hope this helps to clear up some of the confusion.
> >
> > --Stijn
>
> Oh Mr Stijn. Listen, I am not tellimg you off, or making fun of you..Ok ?
> I promise. But
On Tue, Mar 04, 2003 at 10:00:08AM +0100, Stijn Hoop wrote:
>
> Hope this helps to clear up some of the confusion.
>
> --Stijn
Oh Mr Stijn. Listen, I am not tellimg you off, or making fun of you..Ok ?
I promise. But my eyes crossed, went sidewyas, took a holiday, crawled
across the floor looking
On Tue, Mar 04, 2003 at 12:45:19AM -0800, Kent Stewart wrote:
> On Tuesday 04 March 2003 12:16 am, Stijn Hoop wrote:
> > On Mon, Mar 03, 2003 at 07:42:02PM -0800, Kent Stewart wrote:
> > > I learned something out of this too. Fontconfig was modified and so
> > > I tried -Rup fontconfig. Portupgrade
On Tuesday 04 March 2003 12:16 am, Stijn Hoop wrote:
> On Mon, Mar 03, 2003 at 07:42:02PM -0800, Kent Stewart wrote:
> > I learned something out of this too. Fontconfig was modified and so
> > I tried -Rup fontconfig. Portupgrade just built fontconfig. Next I
> > tried -pur fontconfig. It rebuild X
On Mon, Mar 03, 2003 at 07:42:02PM -0800, Kent Stewart wrote:
> I learned something out of this too. Fontconfig was modified and so I
> tried -Rup fontconfig. Portupgrade just built fontconfig. Next I tried
> -pur fontconfig. It rebuild Xft, which had also been upgraded, and just
> repackaged ev
On Monday 03 March 2003 06:30 pm, Roger Merritt wrote:
> At 01:15 PM 3/3/03, Kent Stewart wrote:
> >On Sunday 02 March 2003 08:55 pm, Roger Merritt wrote:
> > > At 05:15 AM 3/3/03, Kent Stewart wrote:
> > > >
>
> On Marcus' advice I took a look at my version of Python. Somehow I
> had version 1.6,
At 01:15 PM 3/3/03, Kent Stewart wrote:
On Sunday 02 March 2003 08:55 pm, Roger Merritt wrote:
> At 05:15 AM 3/3/03, Kent Stewart wrote:
> >
> >What portupgrade options are you using? When you do "-r", you have
> > to force "-f".
>
> Very interesting. Where is that documented? I just did a quick re
On Mon, Mar 03, 2003 at 08:24:48AM +0100, Lauri Watts wrote:
Content-Description: signed data
> On Monday 03 March 2003 00.23, Cliff Sarginson wrote:
>
> > Well I am trying to be constructive. Not just a compainer...although it
> > sounds that way (having spent 2 unsuccessful days trying to get th
On Monday 03 March 2003 00.23, Cliff Sarginson wrote:
> Well I am trying to be constructive. Not just a compainer...although it
> sounds that way (having spent 2 unsuccessful days trying to get the
> latest KDE ports installed).
We obviously test the ports on a wide variety of systems, but we ca
On Sunday 02 March 2003 08:55 pm, Roger Merritt wrote:
> At 05:15 AM 3/3/03, Kent Stewart wrote:
> >
> >What portupgrade options are you using? When you do "-r", you have
> > to force "-f".
>
> Very interesting. Where is that documented? I just did a quick read
> through the portupgrade man page an
At 05:15 AM 3/3/03, Kent Stewart wrote:
What portupgrade options are you using? When you do "-r", you have to
force "-f".
Very interesting. Where is that documented? I just did a quick read through
the portupgrade man page and don't see anything about it. I believe you,
and I'm going to try it o
On Sunday 02 March 2003 07:20 pm, Kirk Strauser wrote:
> At 2003-03-03T02:19:38Z, Kent Stewart <[EMAIL PROTECTED]> writes:
> > We are basically doing the same thing. A portversion -c would have
> > shown x, y, and z. When I check the versions, I would have seen
> > that y depended on x and z. I wo
* Kirk Strauser ([EMAIL PROTECTED]) wrote:
> At 2003-03-03T02:19:38Z, Kent Stewart <[EMAIL PROTECTED]> writes:
>
> > We are basically doing the same thing. A portversion -c would have shown
> > x, y, and z. When I check the versions, I would have seen that y depended
> > on x and z. I would speci
At 2003-03-03T02:19:38Z, Kent Stewart <[EMAIL PROTECTED]> writes:
> We are basically doing the same thing. A portversion -c would have shown
> x, y, and z. When I check the versions, I would have seen that y depended
> on x and z. I would specify x and z on the -ruf. This is what I called
> an i
On Sunday 02 March 2003 05:25 pm, Kirk Strauser wrote:
> At 2003-03-03T00:28:21Z, Kent Stewart <[EMAIL PROTECTED]> writes:
> > The -rR bothers me because it is making a lot of ports that don't
> > need to be updated.
>
> It was my understand that if `-rR' would upgrade a port, then that
> port need
At 2003-03-02T23:36:45Z, Stijn Hoop <[EMAIL PROTECTED]> writes:
> Anyway, I've succesfully survived XFree, gnumeric, and mozilla upgrades
> this way.
Good to know!
> I do religiously add any port build options to pkgtools.conf though, so
> that I never have to do any 'interactive' portbuild.
I'
At 2003-03-03T00:28:21Z, Kent Stewart <[EMAIL PROTECTED]> writes:
> The -rR bothers me because it is making a lot of ports that don't need to
> be updated.
It was my understand that if `-rR' would upgrade a port, then that port
needs to be upgraded. For a non-FreeBSD perspective, look at Debian:
On Sunday 02 March 2003 03:24 pm, Kirk Strauser wrote:
> At 2003-03-02T22:15:59Z, Kent Stewart <[EMAIL PROTECTED]> writes:
> > portupgrade -puf portupgrade
> > portupgrade -pufr png
> > portupgrade -pufr fontconfig
> > portupgrade -pufr libxml2
> > portupgrade -pufr ghostscript-gnu
>
> Interesting.
On Sun, Mar 02, 2003 at 05:24:21PM -0600, Kirk Strauser wrote:
> At 2003-03-02T22:15:59Z, Kent Stewart <[EMAIL PROTECTED]> writes:
> > portupgrade -puf portupgrade
> > portupgrade -pufr png
> > portupgrade -pufr fontconfig
> > portupgrade -pufr libxml2
> > portupgrade -pufr ghostscript-gnu
>
> Int
At 2003-03-02T22:15:59Z, Kent Stewart <[EMAIL PROTECTED]> writes:
> portupgrade -puf portupgrade
> portupgrade -pufr png
> portupgrade -pufr fontconfig
> portupgrade -pufr libxml2
> portupgrade -pufr ghostscript-gnu
Interesting. I almost always user `portupgrade -rR foo' without other
options.
On Sun, Mar 02, 2003 at 02:47:51PM -0800, Kent Stewart wrote:
> On Sunday 02 March 2003 02:37 pm, Cliff Sarginson wrote:
> > On Sun, Mar 02, 2003 at 03:33:49PM -0500, taxman wrote:
> > > On Sunday 02 March 2003 02:22 pm, Cliff Sarginson wrote:
> > > > At the risk of being accused of a complainer.
>
On Sunday 02 March 2003 02:37 pm, Cliff Sarginson wrote:
> On Sun, Mar 02, 2003 at 03:33:49PM -0500, taxman wrote:
> > On Sunday 02 March 2003 02:22 pm, Cliff Sarginson wrote:
> > > At the risk of being accused of a complainer.
> > > I will state here that my experiments in the use of portupgrade,
On Sun, Mar 02, 2003 at 03:33:49PM -0500, taxman wrote:
> On Sunday 02 March 2003 02:22 pm, Cliff Sarginson wrote:
> > At the risk of being accused of a complainer.
> > I will state here that my experiments in the use of portupgrade, have
> > left me without a useable X system.
> > Guess it is back
On Sunday 02 March 2003 03:01 pm, Cliff Sarginson wrote:
| On Sun, Mar 02, 2003 at 01:49:21PM -0600, Mike Meyer wrote:
| > In <[EMAIL PROTECTED]>, Cliff Sarginson
<[EMAIL PROTECTED]> typed:
| > > Will the ports maintainers *please* make sure they release
| > > compilable ports..especially for t
On Sunday 02 March 2003 12:01 pm, Cliff Sarginson wrote:
> On Sun, Mar 02, 2003 at 01:49:21PM -0600, Mike Meyer wrote:
> > In <[EMAIL PROTECTED]>, Cliff Sarginson
<[EMAIL PROTECTED]> typed:
> > > Will the ports maintainers *please* make sure they release
> > > compilable ports..especially for the
On Sunday 02 March 2003 02:22 pm, Cliff Sarginson wrote:
> At the risk of being accused of a complainer.
> I will state here that my experiments in the use of portupgrade, have
> left me without a useable X system.
> Guess it is back to the CD's.
> Will the ports maintainers *please* make sure they
On Sun, Mar 02, 2003 at 01:49:21PM -0600, Mike Meyer wrote:
> In <[EMAIL PROTECTED]>, Cliff Sarginson <[EMAIL PROTECTED]> typed:
> > Will the ports maintainers *please* make sure they release compilable
> > ports..especially for the big mothers like X/KDE.
>
> I'm sure they do. However, they can't
On Sunday 02 March 2003 02:22 pm, Cliff Sarginson wrote:
| At the risk of being accused of a complainer..
| I will state here that my experiments in the use of portupgrade, have
| left me without a useable X system.
| Guess it is back to the CD's.
| Will the ports maintainers *please* make sure t
In <[EMAIL PROTECTED]>, Cliff Sarginson <[EMAIL PROTECTED]> typed:
> Will the ports maintainers *please* make sure they release compilable
> ports..especially for the big mothers like X/KDE.
I'm sure they do. However, they can't test in your environment. The X
ports built fine for me. I don't use
On Sun, Mar 02, 2003 at 08:22:33PM +0100, Cliff Sarginson wrote:
> At the risk of being accused of a complainer..
> I will state here that my experiments in the use of portupgrade, have
> left me without a useable X system.
> Guess it is back to the CD's.
> Will the ports maintainers *please* make
On Saturday 01 March 2003 06:53 pm, Cliff Sarginson wrote:
> Ok,
> I give in.
>
> /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:310:in `deorigin': failed to
> convert nil into String (Pkg DB::DBError)
>
> After most of two days trying to understand portupgrade, RTFM, and advice
> given on this list, I
On Thu, Jan 30, 2003 at 10:35:39AM -0800, Kris Kennaway wrote:
> On Thu, Jan 30, 2003 at 04:12:14PM +, Daniel Bye wrote:
> > Hi all,
> >
> > I am having problems with portupgrade and related tools on 5.0-RELEASE
> > on Sparc64. I can't find anything relevant in the archives, nor on
> > Googl
On Thu, Jan 30, 2003 at 04:12:14PM +, Daniel Bye wrote:
> Hi all,
>
> I am having problems with portupgrade and related tools on 5.0-RELEASE
> on Sparc64. I can't find anything relevant in the archives, nor on
> Google, so I turn to you ;-)
This question has been asked a couple of times on
On Tue, Jan 28, 2003 at 09:06:33PM -0600, Mike Dean wrote:
> I would like to know if there is a way to have portupgrade update all
> ports, except a select few that I want to remain "frozen"
> (OpenOffice.org, simply because I no longer have the free space to
> rebuild it). It looks like I may be
On Tuesday 28 January 2003 07:06 pm, Mike Dean wrote:
> I would like to know if there is a way to have portupgrade update all
> ports, except a select few that I want to remain "frozen"
> (OpenOffice.org, simply because I no longer have the free space to
> rebuild it). It looks like I may be able
I've fixed it 10 hours ago. Thanks for pointing out, BTW.
-Maxim
On Mon, Jan 20, 2003 at 01:46:26PM -0700, BSD wrote:
> There is actually a typo in the patch file for the jasper port. I've
> already email the maintainer about it (Don't know if he's emailed me
> back, as I've been having email iss
There is actually a typo in the patch file for the jasper port. I've
already email the maintainer about it (Don't know if he's emailed me
back, as I've been having email issues since).
Edit
ports/graphics/jasper/files/patch-src-libjasper-include-jasper-jas_types.h
and change:
+typedef log long in
In <1043094762.13652.9.camel@localhost>, Stacey Roberts <[EMAIL PROTECTED]>
typed:
> Hello,
>
> On Mon, 2003-01-20 at 14:59, Mike Meyer wrote:
> > In <1043015655.51041.505.camel@localhost>, Stacey Roberts
><[EMAIL PROTECTED]> typed:
> > > Hello,
> > > After a fresh cvsup of my ports tree, I
Hello,
On Mon, 2003-01-20 at 14:59, Mike Meyer wrote:
> In <1043015655.51041.505.camel@localhost>, Stacey Roberts
><[EMAIL PROTECTED]> typed:
> > Hello,
> > After a fresh cvsup of my ports tree, I tried to update
> > jasper-1.500.4 using portupgrade, but it fails with errors below.
>
> The
In <1043015655.51041.505.camel@localhost>, Stacey Roberts <[EMAIL PROTECTED]>
typed:
> Hello,
> After a fresh cvsup of my ports tree, I tried to update
> jasper-1.500.4 using portupgrade, but it fails with errors below.
The proper way to deal with port build failures is to first make sure
yo
On Mon, 2003-01-06 at 17:15, Stacey Roberts wrote:
> Hello,
> I've just cvsup'd ports tree and attempted to update
> pilot-link-0.11.4 via portupgrade, which fails.
>
> Here's what I've managed to capture off the screen at the end.
>
> Any pointers as to where I could look to fix?
I sent Jo
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 qt
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 a
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 upg
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
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 (unsurprisin
From the man page:
-P
--use-packages Use packages instead of ports whenever
available.
portupgrade searches the local directories
listed
in PKG_PATH for each package to install or
upgrade
the curre
On Fri, Dec 20, 2002 at 08:28:17PM +0100, Pierrick Brossin wrote:
>
> Hi !
>
> I 'portupgrade -a' my system and figured out that it is
> recompiling every new port.
> It's taking a vry long time to do so.
>
> Is there a way to specify to portupgrade to get the
> compiled package instead of c
On Tue, Dec 10, 2002 at 11:32:05AM -0800,
paul beard <[EMAIL PROTECTED]> writes:
| I have some perl modules I installed with cpan and portupgrade
| always kicks back these errors: I'm not clear on how to fix the
| "missing origin" stuff. Anyone got the clue-by-four for me?
|
| ! (bs
isnt pkgdb -F the answer to this..
these types of things led me to occasionally backup my database of whats
installed.
Bri
On Tue, 10 Dec 2002, paul beard wrote:
> I have some perl modules I installed with cpan and portupgrade
> always kicks back these errors: I'm not clear on how to fi
in message <[EMAIL PROTECTED]>,
wrote Dick Hoogendijk thusly...
>
> I've read somewhere that after a cvsup of my /usr/ports is is wise to
> run "portsdb -Uu", maybe even followed by a "pkgdb -F"
>
> Is this really true? Especially portsdb takes quit some time to run, so
> if it's ok not to run.. ;
Dick Hoogendijk wrote:
I've read somewhere that after a cvsup of my /usr/ports is is wise to
run "portsdb -Uu", maybe even followed by a "pkgdb -F"
Is this really true? Especially portsdb takes quit some time to run, so
if it's ok not to run.. ;-))
There isn't any reason to run pkgdb -F but
In an older episode (Friday 18 October 2002 01:32), Andy Knapp wrote:
> Seems that your error is that you just don't have the second tarball of
> X source. Try going to ftp://ftp.xfree86.org/pub/XFree86/4.2.0/source/
> and downloading the second tarball (think it's X420src-2.tgz) and
> putting it m
Seems that your error is that you just don't have the second tarball of
X source. Try going to ftp://ftp.xfree86.org/pub/XFree86/4.2.0/source/
and downloading the second tarball (think it's X420src-2.tgz) and
putting it manually in /usr/ports/distfiles. From what i see, it should
solve the problem.
> From: Tom Carrick <[EMAIL PROTECTED]>
> Date: 08 Oct 2002 12:56:36 +0100
> Sender: [EMAIL PROTECTED]
>
> That worked great, thanks. Can you give me some explanation on why (and
> how) this happens, and in what way it messes up?
When portupgrade is editing/modifying the ports database (not the
That worked great, thanks. Can you give me some explanation on why (and
how) this happens, and in what way it messes up?
On Tue, 2002-10-08 at 07:35, Adam Weinberger wrote:
> try portsdb -fu. the switches are easy enough to remember ::P.
> portupgrade dies from time to time, and that command can
try portsdb -fu. the switches are easy enough to remember ::P.
portupgrade dies from time to time, and that command can often get you
back in business.
-Adam
>> (10.07.2002 @ 2115 PST): Tom Carrick said, in 2.0K: <<
> I was using portupgrade happily upgrading my ports, when it barfed in
> the m
> From: Chip Wiegand <[EMAIL PROTECTED]>
> Date: 07 Oct 2002 16:01:35 -0700
> Sender: [EMAIL PROTECTED]
>
> I am trying to use portupgrade to upgrade freetype2 but am getting this
> error:
>
> chip# portupgrade freetype2
> [Updating the pkgdb in /var/db/pkg ... - 214
> packages found (-0 +1) .
Hello Yann Golanski,
Monday, September 23, 2002, 12:39:17 PM, you wrote:
YG> I'm running portupgrade to keep all my ports up to date but have come to
YG> the following issue.
YG> I want to run the latest cvs version of XFree86 -- need it to get the
YG> Vaio to have X11 -- but this is not a por
From: "Rahim Anderson" <[EMAIL PROTECTED]>
> On a whim I used portupgrade today, just to see how it worked and
everything
> (this is on a box used mostly for testing) and got the following
errors...
>
> dhcp-849-11# portupgrade -a
> cd: can't cd to /usr/ports/devel/ruby-fnmatch
> cd: can't cd to
On Sep 20 at 17:21, Hanspeter Roth spoke:
> Then there's a claim
> ===> XFree86-libraries-4.2.0_3 depends on shared library: freetype.9 - not found
> ===>Verifying install for freetype.9 in /usr/ports/print/freetype2
I had commented out ports-print from the ports-supfile. Thus the new
v
Rahim Anderson wrote:
> On a whim I used portupgrade today, just to see how it worked and everything
> (this is on a box used mostly for testing) and got the following errors...
>
> dhcp-849-11# portupgrade -a
> cd: can't cd to /usr/ports/devel/ruby-fnmatch
> cd: can't cd to /usr/ports/devel/r
At Fri, 20 Sep 2002 14:47:19 -0700,
Adam Weinberger wrote:
> pkg_tarup was removed from the ports tree.
Correct.
> pkg_deinstall -f pkg_tarup-1.2_3 && portupgrade -f portupgrade-20020920
But this could be wrong since that version of portupgrade still relies
on pkg_tarup. Simply upgrade portupg
acey
> > > --
> > > Stacey Roberts
> > > B.Sc (HONS) Computer Science
> > >
> > > Web: www.vickiandstacey.com
> >
> >
> > >> end of "portupgrade of portupgrade fails with "The port directory for
>'sysutils/pk
Thanks for the reply, Adam.
I'll give the procedure a try in a bit, but there's one thing that
perhaps you might be able to explain..,
I'm just curious as to how I was able to "portupgrade -R
portupgrade-x.x.x just last night without hitting this issue..,
Thanks again Adam (and to Kevin Oberma
erman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> E-mail: [EMAIL PROTECTED]Phone: +1 510 486-8634
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-qu
pkg_tarup is gone as a port. The easiest way to fix this is to:
1. pkg_delete -f pkg_tarup-\*
2. pkg_delete portupgrade -\*
3. cd /usr/ports/sysutils/portupgrade
4. make install clean
5. pkgdb -F
That should do the trick. portupgrade does not really handle the
removal of dependencies when the dep
S -
pkg_tarup was removed from the ports tree.
pkg_deinstall -f pkg_tarup-1.2_3 && portupgrade -f portupgrade-20020920
if you're worried about the functionality of it, note the commit message
given when the port got removed:
Retire pkg_tarup. pkg_create(1) has the feature (-b pkgname)
On Sep 20 at 12:18, Jud spoke:
> Try just "make deinstall" or "make deinstall clean" in
> /usr/ports/print/freetype2, then portupgrade
> XFree86-libraries - see if portupgrade will then build
> freetype for you as part of the upgrade.
I had tried that but it still failed. (Can't remember ho
-Original Message-
From: Hanspeter Roth <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Fri, 20 Sep 2002 17:21:26 +0200
Subject: portupgrade, freetype2 and freetype.9
Hello,
pkg_version -vs freetype2 tells me
freetype2-2.0.6 = up-to-date with port
As of XFree86-lib
On Tue, 2002-09-17 at 14:26, Stacey Roberts wrote:
> Hello,
> Portupgrade of gnomepilot-0.1.65 fails after cvsup'ing a few
> minutes ago. I've included last of the failed upgrade below.
This is fixed now. Please cvsup and try again.
Joe
>
> Here's the uname info:
> # uname -a
> FreeBSD
901 - 973 of 973 matches
Mail list logo
