Re: portupgrade questions
Warren Block wrote: On Mon, 5 Nov 2007, Donovan R. Palmer wrote: A total noob here with FreeBSD, but am liking it so far. I went to run portupgrade for the first time and encountered quite a few problems. I have googled around and found some of my answers, but it's been slow going. For example: cairo# portupgrade -aF The thing you should be doing first is checking /usr/ports/UPDATING. Major things can change, and portupgrade may not be able to handle them without help. You could try portmanager, it seems to handle most things so it's great for lazy people (like me :) Port: portmanager-0.4.1_9 Path: /usr/ports/ports-mgmt/portmanager Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
Jerry McAllister wrote: > On Tue, Nov 06, 2007 at 10:15:54AM -0500, Aryeh M. Friedman wrote: > > >>> I really should rephrase what I said, because you're both right and I knew >>> you were right. >>> >>> *I* can't mix packages and ports, because *I* can't be bothered keeping >>> track of things. >>> >>> >> Like everything in UNIX there are several ways: >> >> 1. The default (simplest way) >> 2. The simple but manual way >> 3. And the "right" but insanely complex way >> > > It may seem like that sometimes. But, most often, the right way > is also the simplest way. > > >> Has anyone heard of KISS??!?!?!?!? >> > > Yes. The problem is that so many people put all their emphasis > on the last 'S' which doesn't help anybody. > The last S implies the lowest maintance method which just so happens to always be the first one listed above... for example out of the godizillon kernel settings that might marginally improve performence the only one I set in 8-current is IPI_PREEMPTION (as well as removing the debug options) surely this is simpler then fiddling with indivual settings and/or sysctl's -- Aryeh M. Friedman Developer, not business, friendly http://www.flosoft-systems.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
On Tue, Nov 06, 2007 at 10:15:54AM -0500, Aryeh M. Friedman wrote: > > > > > > > I really should rephrase what I said, because you're both right and I knew > > you were right. > > > > *I* can't mix packages and ports, because *I* can't be bothered keeping > > track of things. > > > > Like everything in UNIX there are several ways: > > 1. The default (simplest way) > 2. The simple but manual way > 3. And the "right" but insanely complex way It may seem like that sometimes. But, most often, the right way is also the simplest way. > > Has anyone heard of KISS??!?!?!?!? Yes. The problem is that so many people put all their emphasis on the last 'S' which doesn't help anybody. jerry > > -- > Aryeh M. Friedman > Developer, not business, friendly > http://www.flosoft-systems.com > > ___ > 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: portupgrade questions
> > > I really should rephrase what I said, because you're both right and I knew > you were right. > > *I* can't mix packages and ports, because *I* can't be bothered keeping > track of things. > Like everything in UNIX there are several ways: 1. The default (simplest way) 2. The simple but manual way 3. And the "right" but insanely complex way Has anyone heard of KISS??!?!?!?!? -- Aryeh M. Friedman Developer, not business, friendly http://www.flosoft-systems.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
On Nov 6, 2007 8:16 AM, Jonathan Chen <[EMAIL PROTECTED]> wrote: > On Tue, Nov 06, 2007 at 12:18:01AM +, James wrote: > > [...] > > So you don't need to uninstall pkgs before starting to use ports, but > you > > can't go back once you've started using them. > > That's not true. Packages are just precompiled ports, and you can mix > and match if you know what you're doing. If you keep to one particular > update interface that can support using packages, eg: portupgrade, you > should be fine. > -- > Jonathan Chen <[EMAIL PROTECTED]> > -- > "The reason why worry kills more people than work is that more people > worry than work." - Robert Frost > I really should rephrase what I said, because you're both right and I knew you were right. *I* can't mix packages and ports, because *I* can't be bothered keeping track of things. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
On Tue, Nov 06, 2007 at 12:18:01AM +, James wrote: [...] > So you don't need to uninstall pkgs before starting to use ports, but you > can't go back once you've started using them. That's not true. Packages are just precompiled ports, and you can mix and match if you know what you're doing. If you keep to one particular update interface that can support using packages, eg: portupgrade, you should be fine. -- Jonathan Chen <[EMAIL PROTECTED]> -- "The reason why worry kills more people than work is that more people worry than work." - Robert Frost ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
Aryeh M. Friedman wrote: *cd patchs # optional ./apply # optional * patchs are some local patchs and yet to be committed patchs I use ok, thanks :) I was wondering why I couldn't find them on my system :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
>> *cd patchs # optional >> ./apply # optional >> * patchs are some local patchs and yet to be committed patchs I use -- Aryeh M. Friedman Developer, not business, friendly http://www.flosoft-systems.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
On Nov 5, 2007 7:11 PM, Jack Barnett <[EMAIL PROTECTED]> wrote: > > Aryeh M. Friedman wrote: > > Here is a script I use to automate the procedure I posted in the > previous reply: > > #!/bin/sh > > cd /usr/src > csup ports-supfile > csup standard-supfile > cd patchs # optional > ./apply # optional > portupgrade -a > > > > ?? > I was wondering about that, too. My understanding, Aryeh, of the ports vs pkg issue is that part of your method is uneccesary. You can use pkg_add fine, but as soon as you start using ports you have to stick with ports. portupgrade -a with a recently updated ports tree will update everything that has an update, and reverting to pkg_add after that could start creating dependency issues. So you don't need to uninstall pkgs before starting to use ports, but you can't go back once you've started using them. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
Aryeh M. Friedman wrote: Here is a script I use to automate the procedure I posted in the previous reply: #!/bin/sh cd /usr/src csup ports-supfile csup standard-supfile cd patchs # optional ./apply # optional portupgrade -a ?? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
The thing you should be doing first is checking /usr/ports/UPDATING. Major things can change, and portupgrade may not be able to handle them without help. Ah, i c. I am starting to make sense out of some of this from my fighting around on this. The "-f" option to pkg_delete/pkg_deinstall will force it to do the action, even if there are dependencies. Sometimes it's the only way. There's also the -o option to portupgrade. As for a tutorial: first, check UPDATING. Then the command man page. If necessary, a web search. I have done some web searching, but haven't found anything that has everything in one place (including the Handbook). Once I emerge from all of this, I might take a stab at writing up something for N00bs to help them learn some of the things that I have figured out the hard way I can't remember what I did for this particular upgrade, but do remember deleting some of the older autoconf ports manually. I suspect you could delete all of them (and maybe some or all of the automake ports) and then just deinstall and install autotools. (Like pkg_delete -f, "make deinstall" in a port will ignore dependencies and just go ahead.) After you do all that, you'll probably need to run pkgdb -F to fix or at least check dependencies. Very helpful! Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
On Mon, 5 Nov 2007, Donovan R. Palmer wrote: A total noob here with FreeBSD, but am liking it so far. I went to run portupgrade for the first time and encountered quite a few problems. I have googled around and found some of my answers, but it's been slow going. For example: cairo# portupgrade -aF The thing you should be doing first is checking /usr/ports/UPDATING. Major things can change, and portupgrade may not be able to handle them without help. cd: can't cd to /usr/ports/devel/gnu-autoconf ** Package 'gnu-autoconf' has been removed from ports tree. Old versions of autoconf were replaced with 2.61. So one possibility I read to fix something like this is to uninstall and resintall it. This yields the following result: But you can't reinstall it, since it's gone from the ports tree. cairo# pkg_info | grep gnu-autoconf gnu-autoconf-2.59 Automatically configure source code on many Un*x platforms cairo# pkg_deinstall gnu-autoconf-2.59 ---> Deinstalling 'gnu-autoconf-2.59' pkg_delete: package 'gnu-autoconf-2.59' is required by these other packages and may not be deinstalled: gnu-automake-1.9.6 kde-3.5.4 kdevelop-3.3.4 ** Listing the failed packages (*:skipped / !:failed) ! gnu-autoconf-2.59 (pkg_delete failed) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed So how do I fix this? Is there a HOW-TO or tutorial on a webpage out there that will help me learn how to fix these things? The handbook makes no mention of how to resolve these issues... unless I missed something? The "-f" option to pkg_delete/pkg_deinstall will force it to do the action, even if there are dependencies. Sometimes it's the only way. There's also the -o option to portupgrade. As for a tutorial: first, check UPDATING. Then the command man page. If necessary, a web search. I can't remember what I did for this particular upgrade, but do remember deleting some of the older autoconf ports manually. I suspect you could delete all of them (and maybe some or all of the automake ports) and then just deinstall and install autotools. (Like pkg_delete -f, "make deinstall" in a port will ignore dependencies and just go ahead.) After you do all that, you'll probably need to run pkgdb -F to fix or at least check dependencies. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
While portsupgrade does work on packages it is usually better to do stuff from ports... even though this may be time consuming you may want to deinstall every last package you have installed then select a few "high level" ports to install (i.e. enough to drag in almost everything you need)... in general the install cycle I use is: 1. Install a top-level port (making any build changes needed if build fails [*PLEASE* submit a pr for any of these]) 2. Do a csup (or cvsup on older releases) to make sure there is nothing newer for the installed ports 3. Do a portupgrade -a 4. If there are more top-level ports goto to step 1 Very interesting. Without sounding too daft, how do I determine what a "high level" port is? Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
> > Very interesting. Without sounding too daft, how do I determine what > a "high level" port is? Thanks! > oops forgot to include on that list: 1. lyx tex editor 2. linux-flashplayer7 3. acrobat reader 7 4. The latest firefox a. Install both native and linux verions b. Use linux to install extensions -- Aryeh M. Friedman Developer, not business friendly http://www.flosoft-systems.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
Donovan R. Palmer wrote: >> While portsupgrade does work on packages it is usually better to do >> stuff from ports... even though this may be time consuming you may want >> to deinstall every last package you have installed then select a few >> "high level" ports to install (i.e. enough to drag in almost everything >> you need)... in general the install cycle I use is: >> >> 1. Install a top-level port (making any build changes needed if build >> fails [*PLEASE* submit a pr for any of these]) >> 2. Do a csup (or cvsup on older releases) to make sure there is nothing >> newer for the installed ports >> 3. Do a portupgrade -a >> 4. If there are more top-level ports goto to step 1 > > Very interesting. Without sounding too daft, how do I determine what > a "high level" port is? Thanks! Depends on what you use the machine for... for example for the most part mine are: 1. gnome-office (normally do xorg and gnome2 as seperate builds though) 2. vlc video player 3. rythmbox mp3 player 4. Java 1.6 5. gimp-shop 6. apache 2+mysql+php5 7. electricsheep 8. Deluge torrent client and as soon the port team adds them: 1. thistest 2. filebuilder (sorry for the self promotion, but I wrote both of these ;-)) -- Aryeh M. Friedman Developer, not business friendly http://www.flosoft-systems.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
Here is a script I use to automate the procedure I posted in the previous reply: #!/bin/sh cd /usr/src csup ports-supfile csup standard-supfile cd patchs # optional ./apply # optional portupgrade -a -- Aryeh M. Friedman Developer, not business friendly http://www.flosoft-systems.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
> > So how do I fix this? Is there a HOW-TO or tutorial on a webpage out > there that will help me learn how to fix these things? The handbook > makes no mention of how to resolve these issues... unless I missed > something? While portsupgrade does work on packages it is usually better to do stuff from ports... even though this may be time consuming you may want to deinstall every last package you have installed then select a few "high level" ports to install (i.e. enough to drag in almost everything you need)... in general the install cycle I use is: 1. Install a top-level port (making any build changes needed if build fails [*PLEASE* submit a pr for any of these]) 2. Do a csup (or cvsup on older releases) to make sure there is nothing newer for the installed ports 3. Do a portupgrade -a 4. If there are more top-level ports goto to step 1 -- Aryeh M. Friedman Developer, no business friendly http://www.flosoft-systems.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade questions
Hi Gang, A total noob here with FreeBSD, but am liking it so far. I went to run portupgrade for the first time and encountered quite a few problems. I have googled around and found some of my answers, but it's been slow going. For example: cairo# portupgrade -aF cd: can't cd to /usr/ports/devel/gnu-autoconf ** Package 'gnu-autoconf' has been removed from ports tree. So one possibility I read to fix something like this is to uninstall and resintall it. This yields the following result: cairo# pkg_info | grep gnu-autoconf gnu-autoconf-2.59 Automatically configure source code on many Un*x platforms cairo# pkg_deinstall gnu-autoconf-2.59 ---> Deinstalling 'gnu-autoconf-2.59' pkg_delete: package 'gnu-autoconf-2.59' is required by these other packages and may not be deinstalled: gnu-automake-1.9.6 kde-3.5.4 kdevelop-3.3.4 ** Listing the failed packages (*:skipped / !:failed) ! gnu-autoconf-2.59 (pkg_delete failed) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed So how do I fix this? Is there a HOW-TO or tutorial on a webpage out there that will help me learn how to fix these things? The handbook makes no mention of how to resolve these issues... unless I missed something? TIA Donovan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
Thanks all for the help, it is working perfectly now! Rich RW wrote: On Wednesday 30 March 2005 10:55, Darksidex wrote: Richard Danter wrote: 1. If I do "portupgrade -rR port" it will recompile the new version of "port" and related ports as expected but it will also try to compile up any packages that are dependent. Is there a way to tell it not to upgrade packages, or to upgrade them using a new package? portupgrade -rRPP port => this will force portupgrade to use only ports Also look at the HOLD_PKGS array in pkgtools.conf ___ 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: portupgrade questions
On Wednesday 30 March 2005 10:55, Darksidex wrote: > Richard Danter wrote: > > 1. If I do "portupgrade -rR port" it will recompile the new version of > > "port" and related ports as expected but it will also try to compile up > > any packages that are dependent. Is there a way to tell it not to > > upgrade packages, or to upgrade them using a new package? > > portupgrade -rRPP port => this will force portupgrade to use only ports Also look at the HOLD_PKGS array in pkgtools.conf ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Danter wrote: > Hi all, > > I have a mixture of ports and packages on my system. Mostly ports, but > since my machine is not all that fast I decided not to compile things > like OpenOffice.org for obvious reasons. > > I have two questions about portupgrade: man portupgrade > > 1. If I do "portupgrade -rR port" it will recompile the new version of > "port" and related ports as expected but it will also try to compile up > any packages that are dependent. Is there a way to tell it not to > upgrade packages, or to upgrade them using a new package? portupgrade -rRPP port => this will force portupgrade to use only ports > > 2. If, when initially compiling a port, I specified options to make (eg > "make USE_MOZILLA=firefox install clean") how do I ensure that > portupgrade will use the same options? /usr/local/etc/pkgtools.conf => Check MAKE_ARGS section -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCSnePLWSOuibjjvIRAqekAJ4ga7032y1swfvkuLBn+xTql1kxYACfbE6/ deCEpn0INxgLi9yBYKAEU/M= =oJe3 -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade questions
Hi all, I have a mixture of ports and packages on my system. Mostly ports, but since my machine is not all that fast I decided not to compile things like OpenOffice.org for obvious reasons. I have two questions about portupgrade: 1. If I do "portupgrade -rR port" it will recompile the new version of "port" and related ports as expected but it will also try to compile up any packages that are dependent. Is there a way to tell it not to upgrade packages, or to upgrade them using a new package? 2. If, when initially compiling a port, I specified options to make (eg "make USE_MOZILLA=firefox install clean") how do I ensure that portupgrade will use the same options? Many thanks Rich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
portupgrade questions
Hello, I've got a machine i want to run portupgrade on. I want to do this as automatically as possible. In the default portinstall pkgtools.conf file in the BEFOREDEINSTALL array i've uncommented the automatically stop each service that has an rc script, and the stop postfix line. I'm now getting a cintax error, does anyone have a working array? Secondly, one of the packages i know is going to be upgraded is postfix, i don't want to have to enter the configuration dialog box and enter the options, i'd just rather have it select cyrus-sasl2, and tls is this doable? Finally, for the make args do i have to list dependencies of ports in that list or just the primary packages i want? Thanks. Dave. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade questions
"Charles Howse" <[EMAIL PROTECTED]> writes:
> Now that I am ready to start installing applications, I have read *some*
> of the documentation in man portupgrade and some articles on the web.
>
> First, I did:
> # tar -czvf dbpkg.tgz /var/db/pkg
> Then:
> #pkgdb -F
> It found cvsupit was broken with no fix for 3 months, I deleted it and
> all it's dependencies.
> Then:
> # portversion
> And upgraded all those that needed it.
> Then I installed mc, popa3d, and lynx.
> # Portinstall mc
> # Portinstall popa3d
> # Portinstall lynx
> When I went to install bash2, it couldn't find it, so I installed it the
> old way from the port.
> Then:
> # portinstall samba
> (not smaba-devel)
> It went interactive and prompted me for options, I selected with syslog
> support. I don't really know what I'm doing here, I've never had to
> configure options in samba before: rpm -ivh samba*.rpm
>
>
> Good so far?
>
>
> Now when I reboot, I see messages about not being able to connect to the
> cups server.
> What's goin' on there?
cups is now pulled in by samba by default.
There's a variable ("WITHOUT_CUPS") for disabling this. You could set
it in pkgtools.conf for convenience.
> Now on to staying up2date...
> I've put a file in /usr/local/etc/periodic/daily to cvsup -g -L 2
> /etc/cvsupfile
> I've created the file /usr/local/etc/cvsup/sup/ports-all/refuse and put
> ports/INDEX in it.
> That should give me a fresh update every night with the exception of the
> INDEX.
>
> I'm going to subscribe to freebsd-announce,
>
> I'm going to keep running cvsup at intervals, and look for modifications
> to the ports I've
> installed.
>
> When something needs updating I can do it individually or:
>
> # cd /usr/ports
> # make index ( -or- portsdb -uU)
> # portupgrade -Nia
>
> Whew! Is there anything else I should do or be aware of?
You could always build the index automatically, as part of the cvsup
job, and then portversion will be all you need to know whether
anything has an update available. Of course, just because an update
is available doesn't necessarily mean that you need to get it.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Portupgrade questions
Hi, Now that I am ready to start installing applications, I have read *some* of the documentation in man portupgrade and some articles on the web. First, I did: # tar -czvf dbpkg.tgz /var/db/pkg Then: #pkgdb -F It found cvsupit was broken with no fix for 3 months, I deleted it and all it's dependencies. Then: # portversion And upgraded all those that needed it. Then I installed mc, popa3d, and lynx. # Portinstall mc # Portinstall popa3d # Portinstall lynx When I went to install bash2, it couldn't find it, so I installed it the old way from the port. Then: # portinstall samba (not smaba-devel) It went interactive and prompted me for options, I selected with syslog support. I don't really know what I'm doing here, I've never had to configure options in samba before: rpm -ivh samba*.rpm Good so far? Now when I reboot, I see messages about not being able to connect to the cups server. What's goin' on there? Now on to staying up2date... I've put a file in /usr/local/etc/periodic/daily to cvsup -g -L 2 /etc/cvsupfile I've created the file /usr/local/etc/cvsup/sup/ports-all/refuse and put ports/INDEX in it. That should give me a fresh update every night with the exception of the INDEX. I'm going to subscribe to freebsd-announce, I'm going to keep running cvsup at intervals, and look for modifications to the ports I've installed. When something needs updating I can do it individually or: # cd /usr/ports # make index ( -or- portsdb -uU) # portupgrade -Nia Whew! Is there anything else I should do or be aware of? Thanks, Charles ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: More Portupgrade questions
On 26 Dec 2002 at 14:31, Kent Stewart boldly uttered:
> On Thursday 26 December 2002 02:21 pm, Philip J. Koenig wrote:
> > Running "make index" fills the screen with lots more error messages
> > than "portsdb -Uu".. :-)
> >
> > Mostly "..no entry for.." messages, some "..Duplicate INDEX entry:.."
> > messages.
>
> That was when "make index" was broken. If you do it today, you don't see
> that. You get a message about generating the index and that is it.
Actually that was when I ran it just before writing that email.
Just before writing this message, I re-cvsup'd ports-all. As I am
writing this, I did "make index" again. No more "no entry for"
errors, but I did get 4 "Duplicate INDEX entry" errors.
Progress. :-)
Continued below.
> > [other error msgs snipped]
> >
> > > > make_index: no entry for: /usr/ports/x11-toolkits/itk
> > > > make_index: no entry for: /usr/local
> > > > Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f
> > >
> > > Re-cvsup your ports tree and see if this still happens.
> >
> > I just cvsup'd it yesterday, this was the prerequisite to trying to
> > update portupgrade and the rest of the ports.
> >
> > FYI - if I'm not mistaken, "cvsup-without-gui-16.1f" shares the same
> > code as the "with gui" cvsup port, but with a different build option.
>
> I have without-gui installed. I log everything and there isn't any point
> to building the gui and then running it from a shell script that tees
> the output.
The only reason I mentioned that port is because it showed up in the
list of port errors.
It looks like all these duplicate errors are for ports which
reference another port but just change the build options slightly.
IE the Makefile for cvsup-without-gui has just the following 2 lines:
MASTERDIR= ${.CURDIR}/..cvsup
WITHOUT_X11=yes
This is starting to make sense now.
As a matter of fact, after removing some orphaned ports and fixing up
some dependencies, everything is looking copacetic. Now for some
actual port upgrading. Thanks for all the help folks.
--
Philip J. Koenig [EMAIL PROTECTED]
Electric Kahuna Systems -- Computers & Communications for the New Millenium
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Re: More Portupgrade questions
On Thursday 26 December 2002 02:21 pm, Philip J. Koenig wrote: > On 26 Dec 2002 at 13:39, Kent Stewart boldly uttered: > > On Thursday 26 December 2002 01:32 pm, Philip J. Koenig wrote: > > > When running "portsdb -uU" as recommended in the Portupgrade > > > documentation I'm currently getting some errors, and not sure if > > > I have to do something about them or what I should do. Couldn't > > > find any suggestions in the Portsdb manpage. > > > > Until just recently "make index" was broken and the only choice was > > using -uU. There was a ~2 day band where "make index" was really > > broken. > > > > For some time now, the only way to get a full list of ports is to > > do a "make index" from /usr/ports. You make get a duplicate port > > message but it works. The -U options fills screens with messages as > > it encounters ports that it can't deal with. > > Running "make index" fills the screen with lots more error messages > than "portsdb -Uu".. :-) > > Mostly "..no entry for.." messages, some "..Duplicate INDEX entry:.." > messages. That was when "make index" was broken. If you do it today, you don't see that. You get a message about generating the index and that is it. > > Continued below. > > On 26 Dec 2002 at 21:37, Stacey Roberts boldly uttered: > > portsdb -U is broken / has been broken for ages. Use the following > > sequence instead: > > make index > > pkgdb -Fv > > portsdb -u > > When running "pkgdb -Fv" after "make index", I now get: > > /usr/ports/INDEX:1:Port info line must consist of 10 fields. > > [repeats 3 times]s > > > Skip this for now? [yes] > > Not sure what I should do here. "Make Index" has created a mis- > formatted INDEX file? Sigh. > > > [other error msgs snipped] > > > > make_index: no entry for: /usr/ports/x11-toolkits/itk > > > make_index: no entry for: /usr/local > > > Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f > > > > Re-cvsup your ports tree and see if this still happens. > > I just cvsup'd it yesterday, this was the prerequisite to trying to > update portupgrade and the rest of the ports. > > FYI - if I'm not mistaken, "cvsup-without-gui-16.1f" shares the same > code as the "with gui" cvsup port, but with a different build option. I have without-gui installed. I log everything and there isn't any point to building the gui and then running it from a shell script that tees the output. FWIW, I just cvsuped ports-all and I didn't get any messages using "make index". I would redo your port cvsup. Kent -- 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: More Portupgrade questions
On Thu, 2002-12-26 at 22:21, Philip J. Koenig wrote: > On 26 Dec 2002 at 13:39, Kent Stewart boldly uttered: > > > On Thursday 26 December 2002 01:32 pm, Philip J. Koenig wrote: > > > When running "portsdb -uU" as recommended in the Portupgrade > > > documentation I'm currently getting some errors, and not sure if I > > > have to do something about them or what I should do. Couldn't find > > > any suggestions in the Portsdb manpage. > > > > Until just recently "make index" was broken and the only choice was > > using -uU. There was a ~2 day band where "make index" was really > > broken. > > > > For some time now, the only way to get a full list of ports is to do a > > "make index" from /usr/ports. You make get a duplicate port message but > > it works. The -U options fills screens with messages as it encounters > > ports that it can't deal with. > > > Running "make index" fills the screen with lots more error messages > than "portsdb -Uu".. :-) > > Mostly "..no entry for.." messages, some "..Duplicate INDEX entry:.." > messages. > > Continued below. > > > > On 26 Dec 2002 at 21:37, Stacey Roberts boldly uttered: > > > portsdb -U is broken / has been broken for ages. Use the following > > sequence instead: > > make index > > pkgdb -Fv > > portsdb -u > > > When running "pkgdb -Fv" after "make index", I now get: > > > /usr/ports/INDEX:1:Port info line must consist of 10 fields. > [repeats 3 times] > > > > Skip this for now? [yes] > > > Not sure what I should do here. "Make Index" has created a mis- > formatted INDEX file? Sigh. > > > [other error msgs snipped] > > > make_index: no entry for: /usr/ports/x11-toolkits/itk > > > make_index: no entry for: /usr/local > > > Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f > > > > > > > Re-cvsup your ports tree and see if this still happens. > > > I just cvsup'd it yesterday, this was the prerequisite to trying to > update portupgrade and the rest of the ports. I'd cvsup the ports tree now, actually. Things get broken, someone complains, if its simple enough, a fix is uploaded, if you're really lucky, two hours later your mirror is updated. Regards, Stacey > > FYI - if I'm not mistaken, "cvsup-without-gui-16.1f" shares the same > code as the "with gui" cvsup port, but with a different build option. > > > -- > Philip J. Koenig > [EMAIL PROTECTED] > Electric Kahuna Systems -- Computers & Communications for the New > Millenium -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: More Portupgrade questions
On 26 Dec 2002 at 13:39, Kent Stewart boldly uttered: > On Thursday 26 December 2002 01:32 pm, Philip J. Koenig wrote: > > When running "portsdb -uU" as recommended in the Portupgrade > > documentation I'm currently getting some errors, and not sure if I > > have to do something about them or what I should do. Couldn't find > > any suggestions in the Portsdb manpage. > > Until just recently "make index" was broken and the only choice was > using -uU. There was a ~2 day band where "make index" was really > broken. > > For some time now, the only way to get a full list of ports is to do a > "make index" from /usr/ports. You make get a duplicate port message but > it works. The -U options fills screens with messages as it encounters > ports that it can't deal with. Running "make index" fills the screen with lots more error messages than "portsdb -Uu".. :-) Mostly "..no entry for.." messages, some "..Duplicate INDEX entry:.." messages. Continued below. On 26 Dec 2002 at 21:37, Stacey Roberts boldly uttered: > portsdb -U is broken / has been broken for ages. Use the following > sequence instead: > make index > pkgdb -Fv > portsdb -u When running "pkgdb -Fv" after "make index", I now get: > /usr/ports/INDEX:1:Port info line must consist of 10 fields. [repeats 3 times] > > Skip this for now? [yes] Not sure what I should do here. "Make Index" has created a mis- formatted INDEX file? Sigh. [other error msgs snipped] > > make_index: no entry for: /usr/ports/x11-toolkits/itk > > make_index: no entry for: /usr/local > > Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f > > > > Re-cvsup your ports tree and see if this still happens. I just cvsup'd it yesterday, this was the prerequisite to trying to update portupgrade and the rest of the ports. FYI - if I'm not mistaken, "cvsup-without-gui-16.1f" shares the same code as the "with gui" cvsup port, but with a different build option. -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: More Portupgrade questions
On Thursday 26 December 2002 01:32 pm, Philip J. Koenig wrote: > When running "portsdb -uU" as recommended in the Portupgrade > documentation I'm currently getting some errors, and not sure if I > have to do something about them or what I should do. Couldn't find > any suggestions in the Portsdb manpage. Until just recently "make index" was broken and the only choice was using -uU. There was a ~2 day band where "make index" was really broken. For some time now, the only way to get a full list of ports is to do a "make index" from /usr/ports. You make get a duplicate port message but it works. The -U options fills screens with messages as it encounters ports that it can't deal with. Since I rebuild INDEX and INDEX.db everytime I cvsup ports-all, I added ports/INDEX to my ports-all refuse file. This saves several minutes using my local cvs-mirror. If you retransfer INDEX from an external mirror, it has to be much longer. Kent > > I recently removed all the Ruby stuff and portupgrade and upgraded to > the latest version, but I got about the same errors with a version > from July 02. > > Examples: > > "/usr/ports/Mk/bsd.ruby.mk", line 135: "Ruby 1.7 is obsolete; set > RUBY_VER to 1.8 instead." > *** Error code 1: malformed entry: *** Error code 1 > 'all' not remade because of errors.: > > guile-gnome-0.20_5:"" non-existent -- dependency list incomplete > > l-1.1.3:/usr/ports/www/gtkhtml: malformed entry: l- > 1.1.3:/usr/ports/www/gtkhtml: /usr/X11R6/share/gnome/ > .keep_me:/usr/ports/misc/gnomehier > > make_index: no entry for: /usr/ports/x11-toolkits/itk > make_index: no entry for: /usr/local > > Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f -- 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: More Portupgrade questions
On Thu, 2002-12-26 at 21:32, Philip J. Koenig wrote: > When running "portsdb -uU" as recommended in the Portupgrade > documentation I'm currently getting some errors, and not sure if I > have to do something about them or what I should do. Couldn't find > any suggestions in the Portsdb manpage. portsdb -U is broken / has been broken for ages. Use the following sequence instead: make index pkgdb -Fv portsdb -u > > I recently removed all the Ruby stuff and portupgrade and upgraded to > the latest version, but I got about the same errors with a version > from July 02. > > Examples: > > "/usr/ports/Mk/bsd.ruby.mk", line 135: "Ruby 1.7 is obsolete; set > RUBY_VER to 1.8 instead." > *** Error code 1: malformed entry: *** Error code 1 > 'all' not remade because of errors.: > > guile-gnome-0.20_5:"" non-existent -- dependency list incomplete > > l-1.1.3:/usr/ports/www/gtkhtml: malformed entry: l- > 1.1.3:/usr/ports/www/gtkhtml: /usr/X11R6/share/gnome/ > .keep_me:/usr/ports/misc/gnomehier > > make_index: no entry for: /usr/ports/x11-toolkits/itk > make_index: no entry for: /usr/local > Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f > Re-cvsup your ports tree and see if this still happens. Regards, Stacey > > -- > Philip J. Koenig > [EMAIL PROTECTED] > Electric Kahuna Systems -- Computers & Communications for the New > Millenium > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-questions" in the body of the message -- Stacey Roberts B.Sc (HONS) Computer Science Web: www.vickiandstacey.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
More Portupgrade questions
When running "portsdb -uU" as recommended in the Portupgrade documentation I'm currently getting some errors, and not sure if I have to do something about them or what I should do. Couldn't find any suggestions in the Portsdb manpage. I recently removed all the Ruby stuff and portupgrade and upgraded to the latest version, but I got about the same errors with a version from July 02. Examples: "/usr/ports/Mk/bsd.ruby.mk", line 135: "Ruby 1.7 is obsolete; set RUBY_VER to 1.8 instead." *** Error code 1: malformed entry: *** Error code 1 'all' not remade because of errors.: guile-gnome-0.20_5:"" non-existent -- dependency list incomplete l-1.1.3:/usr/ports/www/gtkhtml: malformed entry: l- 1.1.3:/usr/ports/www/gtkhtml: /usr/X11R6/share/gnome/ .keep_me:/usr/ports/misc/gnomehier make_index: no entry for: /usr/ports/x11-toolkits/itk make_index: no entry for: /usr/local Warning: Duplicate INDEX entry: cvsup-without-gui-16.1f -- Philip J. Koenig [EMAIL PROTECTED] Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
