Re: portupgrade error?
On Sun, Mar 21, 2004 at 12:57:34AM -0500, Ralph M. Los wrote: Has anyone ever had this problem: [EMAIL PROTECTED]portupgrade mozilla-devel /usr/local/sbin/portupgrade:35:in `require': No such file to load -- pkgtools (LoadError) from /usr/local/sbin/portupgrade:35 I can't seem to figure it out. Any pointers would be great! Did you update portupgrade following /usr/ports/UPDATING? Kris pgp0.pgp Description: PGP signature
Re: portupgrade strangeness
On Thu, 18 Mar 2004, stan wrote: I suddenly have a bunch of machines where I'mgetting portupgrade failures on various ports wiht uninstall error. I've found thta if I manually do a make deintall ; make resiantll sequence on these, that I cna fix the proble, Please mind: I am not sure about the reasons of this behaviour, but I had the same problem. If you have a look at /usr/ports/UPDATING you will find some changes that might affect your system: - ruby/portupgrade - expat2 Regards, Uli. However this seesm to be a new behavior. I normally run portupgrarde with teh -arR -l report) options, so is there a new option or somethinng that has changed this tools behavior? -- They that would give up essential liberty for temporary safety deserve neither liberty nor safety. -- Benjamin Franklin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] +---+ |Peter Ulrich Kruppa| | Wuppertal | | Germany | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Mail readers (was: Re: Portupgrade troubles, interactive ports)
On Mar 17, 2004, at 5:45 PM, Kris Kennaway wrote: 1) Please wrap your lines at 70 characters so your emails may be easily read. I'm using Mail.app on OS X 10.3.3, and someone offering some advice from this list also asked me to fix line wrapping. I checked and checked, but found nothing in Mail that allows a wrapping unless it's done manually. I went to the MacOSX admin mailing list and asked there. They said that the problem is that when Mail.app sends as text (I avoid whenever possible sending html or rich text stuff through email...if it's good enough for telnet, it's good enough for me! :-) the format is flow (format = flowed), and pointed me to http://www.joeclark.org/ffaq.html for some information. From what I understood the problem isn't Mail.app, it was a MUA that isn't correctly reading format=flowed Out of curiosity, what email program are you using that it's not showing up? I thought the FAQ said that many term emailers support the flowed format...essentially my hitting enter at the end of each line is making it more difficult for the format=flowed-speaking- mailers to correctly format my email for quoting, etc... Suggestions? I'm not trying to start any kind of religious MUA war or anything like that, just asking for honest opinion on best practices... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mail readers (was: Re: Portupgrade troubles, interactive ports)
On Mar 17, 2004, at 5:45 PM, Kris Kennaway wrote: 1) Please wrap your lines at 70 characters so your emails may be easily read. I'm using Mail.app on OS X 10.3.3, and someone offering some advice from this list also asked me to fix line wrapping. I checked and checked, but found nothing in Mail that allows a wrapping unless it's done manually. Yup. I do it manually - just hit that nice big Enter/Return key between a couple of word when I get out around that far. Some Mail clients allow you to set a line length and then try to break between word near there. Most editors such as vi allow something like this too. I am using vi, but have a long habit of hitting return from way back in the days of typewriters (I'm old) so I never even bother to set anything in vi.I just miss the bell 'ding' and sound of the platen or type ball moving back each time. Maybe that could be simulated. I went to the MacOSX admin mailing list and asked there. They said that the problem is that when Mail.app sends as text (I avoid whenever possible sending html or rich text stuff through email...if it's good enough for telnet, it's good enough for me! :-) the format is flow (format = flowed), and pointed me to http://www.joeclark.org/ffaq.html for some information. From what I understood the problem isn't Mail.app, it was a MUA that isn't correctly reading format=flowed That's all too complicated. It is really because many people read their mail on text only readers - such as on a console without much gui stuff or whatever. So, the stuff either just wraps at lousy places and runs stuff together or it ignores all the html or other markup junk that clutters up the message file and splats it all out on the screen just as it gets it which is hard to read. Out of curiosity, what email program are you using that it's not showing up? I thought the FAQ said that many term emailers support the flowed format...essentially my hitting enter at the end of each line is making it more difficult for the format=flowed-speaking- mailers to correctly format my email for quoting, etc... A return in there usuall doesn't mess up the gui Email readers. They tend to ignore it. But it sure helps text based Email readers. jerry Suggestions? I'm not trying to start any kind of religious MUA war or anything like that, just asking for honest opinion on best practices... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mail readers (was: Re: Portupgrade troubles, interactive ports)
On Mar 18, 2004, at 3:42 PM, Jerry McAllister wrote: Yup. I do it manually - just hit that nice big Enter/Return key between a couple of word when I get out around that far. Which is why, on my mailer, quoting you gives a full line then one word then a line...it kind of reminds me of a person I knew in college who typed his first multipage essay with the hard linefeeds at the end of each line instead of the end of each paragraph, then made a change near the beginning and foobar'd his formatting for the whole document... :-) That's all too complicated. It is really because many people read their mail on text only readers - such as on a console without much gui stuff or whatever. So, the stuff either just wraps at lousy places and runs stuff together or it ignores all the html or other markup junk that clutters up the message file and splats it all out on the screen just as it gets it which is hard to read. In the FAQ (and the conversation I had with the person on the OS X lists), it isn't HTML, and it isn't a GUI thing. Format=flowed works in several console programs, from what the FAQ said. Re: HTML, the FAQ said: No. Nothing. Format=flowed applies solely to plain-text messages. HTML messages already have something functionally equivalent to f=f: the BLOCKQUOTE attribute, which... um... quotes blocks of text. When f=f mailers that also can handle HTML encounter BLOCKQUOTE text, its usually marked up with the same excerpt bars were familiar with from f=f. Format=flowed isnt actually at work there, but since BLOCKQUOTE text flows nicely when you resize a window, the effect is the same. A return in there usuall doesn't mess up the gui Email readers. They tend to ignore it. But it sure helps text based Email readers. Actually, it is displaying oddly in my MUA...because of the hard returns mixed with the f=f. Incidentally, can others on the list verify where my mail is wrapping? I was working with someone offlist to see if, in Mail.app, my wrapping is affected by the size of the composition window when I send the message. I noticed that quirk in a few other OS X apps when working with printing documents...WYSIWYG taken to an extreme :-) -Bart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mail readers (was: Re: Portupgrade troubles, interactive ports)
On Thu, Mar 18, 2004 at 03:52:30PM -0500, Bart Silverstrim wrote: Incidentally, can others on the list verify where my mail is wrapping? I was working with someone offlist to see if, in Mail.app, my wrapping is affected by the size of the composition window when I send the message. I noticed that quirk in a few other OS X apps when working with printing documents...WYSIWYG taken to an extreme :-) -Bart Look good to me. I use vim for my mutt editor. The command set editor=vim -c 'set tw=70 expandtab' in my .muttrc file makes vim wrap at 70 characters only while it is run from mutt. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mail readers (was: Re: Portupgrade troubles, interactive ports)
in message [EMAIL PROTECTED], wrote Bart Silverstrim thusly... Incidentally, can others on the list verify where my mail is wrapping? Love to! Your first reply did not wrap around ~72 characters; it went until the width of my terminal (mutt 1.5.5.1_1 in xterm) for all practical purposes. This message of yours was around ~72 characters, and i like you for that. Now. - Parv -- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mail readers (was: Re: Portupgrade troubles, interactive ports)
On Mar 18, 2004, at 5:22 PM, Parv wrote: in message [EMAIL PROTECTED], wrote Bart Silverstrim thusly... Incidentally, can others on the list verify where my mail is wrapping? Love to! Your first reply did not wrap around ~72 characters; it went until the width of my terminal (mutt 1.5.5.1_1 in xterm) for all practical purposes. This message of yours was around ~72 characters, and i like you for that. Now. I'm still conversing with someone else from the list about this...I really think it depends on the width of Mail.app's composition window as to where it inserts the formatting codes! Probably will know more shortly...I just sent him two messages, each with differently width-ed windows for the composition windows. -Bart ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade troubles, interactive ports
On Wed, Mar 17, 2004 at 02:50:54PM -0700, SIMON TIMMS wrote: Hi there, I use to run portupgrade and when it ran into an interactive port (like php) it would sit and wait for my input before continuing. This worked fine and I didn't mind having to keep a bit of an eye on portupgrade. However now when I run portupgrade (portupgrade -ra) it stalls when it runs into an interactive port. I can't enter any input and ctrl-C/ctrl-z do nothing. I end up killing the process from another terminal. I have tried this over ssh and also from the console. 1) Please wrap your lines at 70 characters so your emails may be easily read. 2) Set the BATCH environment variable before running portupgrade to skip interactive ports. You can then go and build the interactive ports all at once by setting the INTERACTIVE variable. This and other control settings are documented in the /usr/ports/Mk/bsd.port.mk file. Kris pgp0.pgp Description: PGP signature
Re: Portupgrade - Piping Output to file
On Fri, Mar 12, 2004 at 01:32:17PM +1100, Ron Joordens wrote: Hi Everyone, I'm currently using portupgrade to upgrade my ports (obviously). I'm getting errors on some of my ports. Eg config error on gedit2, and KDE fails for unknown reason. How do I direct my output to a file so I can review it to find the reason or at least post it to this forum? I want the output dumped to a file and display on the monitor at the same time. Last time I tried using the monitor was blank but there was nothing in the file. Use script(1) or tee(1). Kris pgp0.pgp Description: PGP signature
Re: Portupgrade - Piping Output to file
Ron Joordens wrote: Hi Everyone, I'm currently using portupgrade to upgrade my ports (obviously). I'm getting errors on some of my ports. Eg config error on gedit2, and KDE fails for unknown reason. How do I direct my output to a file so I can review it to find the reason or at least post it to this forum? I want the output dumped to a file and display on the monitor at the same time. Last time I tried using the monitor was blank but there was nothing in the file. Thanks Ron You might look at script(1). HTH, Kevin Kinsey DaleCo, S.P. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade: uninstall error ???
I am seeing many uninstall errors lately when I do a portupgrade (particularily with Gnome). Of course one can manually # make deinstall make reinstall but this is becoming a bit tiresome. So I would like to know what is the reason of these errors: One should think either a port is out of date and will be updated by portupgrade or it isn't, shouldn't one? Have you done the UPDATING process on portupgrade? If not, you should read and follow the advice in /usr/ports/UPDATING to upgarde portupgrade (and ruby). -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Daemon Dancing in the Dark, a FreeBSD weblog: http://freebsd.amazingdev.com/blog/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade: uninstall error ???
On Mon, 8 Mar 2004, Kris Kennaway wrote: That still doesn't tell us anything. Look further back in the portupgrade output and post the actual errors it encounters (e.g. record the output to a file with script(1) or tee(1) and then extract the relevant parts). Great idea to use script for this! But I will have a look at the ruby/portupgrade upgrade, mentioned by Jonathan Arnold, first. Uli. Kris +---+ |Peter Ulrich Kruppa| | Wuppertal | | Germany | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade: uninstall error ???
On Tue, 9 Mar 2004, Jonathan Arnold wrote: Have you done the UPDATING process on portupgrade? No. I will look after this first. Thanks, Uli. +---+ |Peter Ulrich Kruppa| | Wuppertal | | Germany | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade and binary packages
On Mon, Mar 08, 2004 at 02:39:18PM +0100, Michael Sig Birkmose wrote: Hi everyone, I recently tried to switch from compiling everything myself from ports, to use portupgrade -PP package_name. However, after having run CVSUP on my ports tree, I run into the problem, that the binary packages from ftp.something.freebsd.org are far behind the version in the portstree. After a little bit of digging, I found out that ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/ has much newer binary packages. However it stills is a bit behind? What is the solution to this problem, or is there none? I would really like to avoid compiling things... Since computers and mirror site bandwidth are still not infinitely fast, there will always be a time lag between the packages on the ftp site and the ports in the ports collection [1]. Unfortunately this means that you can't have it both ways: either you can compile the latest versions of all the ports yourself, or you can install packages that are a bit older. Kris [1] Of course, if you want to reduce this lag we'd be happy to accept donations of a dozen or so fast build machines :-) pgp0.pgp Description: PGP signature
Re: portupgrade and binary packages
On Monday 08 March 2004 01:51 pm, Kris Kennaway wrote: On Mon, Mar 08, 2004 at 02:39:18PM +0100, Michael Sig Birkmose wrote: Hi everyone, I recently tried to switch from compiling everything myself from ports, to use portupgrade -PP package_name. However, after having run CVSUP on my ports tree, I run into the problem, that the binary packages from ftp.something.freebsd.org are far behind the version in the portstree. After a little bit of digging, I found out that ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/ has much newer binary packages. However it stills is a bit behind? What is the solution to this problem, or is there none? I would really like to avoid compiling things... Since computers and mirror site bandwidth are still not infinitely fast, there will always be a time lag between the packages on the ftp site and the ports in the ports collection [1]. Unfortunately this means that you can't have it both ways: either you can compile the latest versions of all the ports yourself, or you can install packages that are a bit older. The other side is that ports follows -current and -stable. It hasn't been that long since make on something like 4.8-release wouldn't build some ports. Would such a package install on the older systems? People have had ways of building just make but that won't always work. Bison was also an example but I don't show any installed ports on my system that depend on bison-1.75_2. Of course, my pkg_info -R $1 lookup command fails frequently. Kent Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade: uninstall error ???
On Tue, Mar 09, 2004 at 06:16:12AM +0100, Peter Ulrich Kruppa wrote: Hi! I am seeing many uninstall errors lately when I do a portupgrade (particularily with Gnome). Of course one can manually # make deinstall make reinstall but this is becoming a bit tiresome. So I would like to know what is the reason of these errors: It's hard to say since my psychic error message guessing powers aren't working well today. Can you give us a hint? :-) Kris pgp0.pgp Description: PGP signature
Re: portupgrade: uninstall error ???
On Mon, 8 Mar 2004, Kris Kennaway wrote: On Tue, Mar 09, 2004 at 06:16:12AM +0100, Peter Ulrich Kruppa wrote: Hi! I am seeing many uninstall errors lately when I do a portupgrade (particularily with Gnome). Of course one can manually # make deinstall make reinstall but this is becoming a bit tiresome. So I would like to know what is the reason of these errors: It's hard to say since my psychic error message guessing powers aren't working well today. Can you give us a hint? :-) I understand what you mean, but it is a bit difficult to describe, since I don't have an idea myself. What I see is something like this: After a # portupgrade -r pkgconfig I receive -- ** The following packages were not installed or upgraded (*:skipped / !:failed) ! accessibility/gnopernicus (gnopernicus-0.7.5) (uninstall error) ! x11-toolkits/gal2 (gal2-2.1.5)(uninstall error) ! www/gtkhtml3 (gtkhtml3-3.1.8) (uninstall error) ! net/gnomemeeting (gnomemeeting-0.98.5_1) (compiler error) ! accessibility/gok (gok-0.9.8) (uninstall error) ! databases/evolution-data-server (evolution-data-server-0.0.7) (unknown build error) ! print/ggv2 (ggv2-2.5.4) (uninstall error) ! x11/gdm2 (gdm2-2.5.90.1) (uninstall error) * x11/gnomepanel (gnomepanel-2.5.90) ! deskutils/gucharmap (gucharmap-gnome-1.3.0) (uninstall error) ! www/epiphany (epiphany-1.1.10)(uninstall error) * graphics/gimp-devel (gimp-gnome-2.0.pre3_1,1) * net/gnomeicu2 (gnomeicu2-0.99_1) * x11/gnomeapplets2 (gnomeapplets2-2.5.6) and so on ... --- the uninstall errors can mostly be fixed manually by # make deinstall make reinstall since a complete ../work directory has been built but hasn't been installed because of an existing version. After this manual procedure most skipped ports will build and install well. I also tried a # pkgdb -fu in case something is wrong with my package database, but that doesn't help either. Uli. +---+ |Peter Ulrich Kruppa| | Wuppertal | | Germany | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade: uninstall error ???
On Tue, Mar 09, 2004 at 08:30:48AM +0100, Peter Ulrich Kruppa wrote: On Mon, 8 Mar 2004, Kris Kennaway wrote: On Tue, Mar 09, 2004 at 06:16:12AM +0100, Peter Ulrich Kruppa wrote: Hi! I am seeing many uninstall errors lately when I do a portupgrade (particularily with Gnome). Of course one can manually # make deinstall make reinstall but this is becoming a bit tiresome. So I would like to know what is the reason of these errors: It's hard to say since my psychic error message guessing powers aren't working well today. Can you give us a hint? :-) I understand what you mean, but it is a bit difficult to describe, since I don't have an idea myself. What I see is something like this: After a # portupgrade -r pkgconfig I receive That still doesn't tell us anything. Look further back in the portupgrade output and post the actual errors it encounters (e.g. record the output to a file with script(1) or tee(1) and then extract the relevant parts). Kris pgp0.pgp Description: PGP signature
Re: Portupgrade and db/db2
On Saturday 06 March 2004 09:20 am, Chris wrote: What would be the best way to handle this in portupgrade? [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 321 packages found (-0 +1) . done] ** Package name changed from 'db' (databases/db2) to 'db2' (databases/db2). ** No need to upgrade 'db-2.7.7_1' (= db2-2.7.7_1). (specify -f to force) I don't think you can. It has been my experience that portupgrade won't run until you have fixed it. Everything that uses it will also have to be fixed but portsdb will often present you with the choices y/n/[a]ll and all will fix the rest. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade and db/db2
On Saturday 06 March 2004 11:12 am, Kent Stewart wrote: On Saturday 06 March 2004 09:20 am, Chris wrote: What would be the best way to handle this in portupgrade? [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 321 packages found (-0 +1) . done] ** Package name changed from 'db' (databases/db2) to 'db2' (databases/db2). ** No need to upgrade 'db-2.7.7_1' (= db2-2.7.7_1). (specify -f to force) I don't think you can. It has been my experience that portupgrade won't run until you have fixed it. Everything that uses it will also have to be fixed but portsdb will often present you with the choices y/n/[a]ll and all will fix the rest. I did it again. Portsdb should read pkgdb. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade and db/db2
On Sat, Mar 06, 2004 at 11:20:53AM -0600, Chris wrote: What would be the best way to handle this in portupgrade? [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 321 packages found (-0 +1) . done] ** Package name changed from 'db' (databases/db2) to 'db2' (databases/db2). ** No need to upgrade 'db-2.7.7_1' (= db2-2.7.7_1). (specify -f to force) That's not an error, so there's nothing to handle :-) If you want to remove the warning then rebuild the db port with the -f flag to force the rebuild. Kris pgp0.pgp Description: PGP signature
Re: Portupgrade and db/db2
On Sat, Mar 06, 2004 at 02:30:49PM -0800, Kris Kennaway wrote: That's not an error, so there's nothing to handle :-) If you want to remove the warning then rebuild the db port with the -f flag to force the rebuild. Kris Hi! I have the same messages, but pkgdb -f or pkgdb -fu don't remove those warnings. portsdb -fuU doesn't work too. I have installed FreeBSD 4.9-RELEASE-p2 (this night I'll upgrade to last security patch). Thanks for your help! Regards. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade and db/db2
On Sun, Mar 07, 2004 at 01:10:41AM +0100, Manuel Hernandez wrote: On Sat, Mar 06, 2004 at 02:30:49PM -0800, Kris Kennaway wrote: That's not an error, so there's nothing to handle :-) If you want to remove the warning then rebuild the db port with the -f flag to force the rebuild. Kris Hi! I have the same messages, but pkgdb -f or pkgdb -fu don't remove those warnings. portsdb -fuU doesn't work too. pkgdb and portsb don't rebuild the ports. portupgrade is the utility that does. Kris pgp0.pgp Description: PGP signature
Re: portupgrade/pkgdb problem
Roman Bogorodskiy wrote: Hi, As described in http://www.freshports.org/[EMAIL PROTECTED], I've reinstalled portupgrade-\*. And now when I try to run portupgrade I have such error: novel /usr/local/bin $ portupgrade -sfr lang/ruby16 --- [Executing a command as root: sudo /usr/local/sbin/pkgdb -u] --- Updating the pkgdb [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 266 packages found (-41 +135) (...)ruby in malloc(): error: allocation failed --- [Executing a command as root: sudo /usr/local/sbin/pkgdb -u] --- Updating the pkgdb [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 266 packages found (-41 +135) (...)ruby in malloc(): error: allocation failed The pkgdb must be updated. Please run 'pkgdb -u' as root. novel /usr/local/bin $ What's wrong? FreeBSD 5.2.1-RELEASE i386 portupgrade 1.8.1 ruby 1.8.1 (2003-12-25) [i386-freebsd5] I think this is because ruby-1.6 used to install /usr/local/bin/ruby, but by the recent upgrade this becomes /usr/local/bin/ruby16 and ruby is not there anymore. Since portupgrade needs ruby, portupgrade gets stuck as soon as upgrading ruby-1.6 removes the /usr/local/bin/ruby file. I have removed portupgrade and all related ruby stuff and then reinstalled portupgrade, which then installs ruby-1.8. All works well then. Rob. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade/pkgdb problem
Rob wrote: I think this is because ruby-1.6 used to install /usr/local/bin/ruby, but by the recent upgrade this becomes /usr/local/bin/ruby16 and ruby is not there anymore. Since portupgrade needs ruby, portupgrade gets stuck as soon as upgrading ruby-1.6 removes the /usr/local/bin/ruby file. I have removed portupgrade and all related ruby stuff and then reinstalled portupgrade, which then installs ruby-1.8. All works well then. I said that I've reinstalled portupgrade already. And I have no ruby16 installed now, my /usr/local/bin/ruby is a ruby-1.8 novel ~ $ ruby --version ruby 1.8.1 (2003-12-25) [i386-freebsd5] novel ~ $ -Roman Bogorodskiy pgp0.pgp Description: PGP signature
Re: portupgrade portupgrade ...
leafy writes: Deinstall ruby 1.6 stuff (if you are paranoi[d]) pkg_deinstall -ri lang/ruby16 root@ pkg_deinstall -ri lang/ruby16 --- Deinstalling 'ruby16-shim-ruby18-1.8.1.p3' delete ruby16-shim-ruby18-1.8.1.p3? n --- Deinstalling 'ruby-1.6.8.2003.10.15_1' delete ruby-1.6.8.2003.10.15_1? y pkg_delete: package 'ruby-1.6.8.2003.10.15_1' is required by these other packages and may not be deinstalled: ruby16-shim-ruby18-1.8.1.p3 --- Reporting the results (+:done / -:ignored / *:skipped / !:failed) + ruby16-shim-ruby18-1.8.1.p3 ! ruby-1.6.8.2003.10.15_1 (pkg_delete failed) Robert Huff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade portupgrade ...
On Monday 01 March 2004 07:48 am, Robert Huff wrote: leafy writes: Deinstall ruby 1.6 stuff (if you are paranoi[d]) pkg_deinstall -ri lang/ruby16 root@ pkg_deinstall -ri lang/ruby16 --- Deinstalling 'ruby16-shim-ruby18-1.8.1.p3' delete ruby16-shim-ruby18-1.8.1.p3? n --- Deinstalling 'ruby-1.6.8.2003.10.15_1' delete ruby-1.6.8.2003.10.15_1? y pkg_delete: package 'ruby-1.6.8.2003.10.15_1' is required by these other packages and may not be deinstalled: ruby16-shim-ruby18-1.8.1.p3 --- Reporting the results (+:done / -:ignored / *:skipped / !:failed) + ruby16-shim-ruby18-1.8.1.p3 ! ruby-1.6.8.2003.10.15_1 (pkg_delete failed) You have to upgrade it by hand. You can't portupgrade the tool portupgrades uses to do the upgrade. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade crash
On Fri, Feb 06, 2004 at 10:23:58PM -0500, Jeff Elkins wrote: My machine just suffered a power-failure 6 hrs into a portupgrade -a I restarted it after a pkgdb -F Did I do the right thing? Yep, that should be pretty safe (assuming e.g. fsck didn't discover that the power failure caused filesystem corruption and lost files). If the database appears to be corrupted you can try a `pkgdb -fu` in order to rebuild it. -- -jg. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade of KDE-3.1.4 to KDE-3.2.0 (5.2.1-RC)
On Fri, Feb 06, 2004 at 08:29:29PM -0600, Chris wrote: Ok - I have been away for a spell - perhaps someone can led insight. Granted, I have 5.2.1-RC installed, and granted I do a weekly cvsup of the ports then a portupgrade. But what the hell-o is up with the replacement of KDE-3.1.4 with KDE-3.2.0??? Well, that's what happens when new versions of software get released. This just totally whacked my system. Provide some details, please. Kris pgp0.pgp Description: PGP signature
Re: Portupgrade crash
On Fri, Feb 06, 2004 at 10:23:58PM -0500, Jeff Elkins wrote: My machine just suffered a power-failure 6 hrs into a portupgrade -a I restarted it after a pkgdb -F Did I do the right thing? Yep, that should be pretty safe (assuming e.g. fsck didn't discover that the power failure caused filesystem corruption and lost files). Kris pgp0.pgp Description: PGP signature
Re: portupgrade
On Fri, 23 Jan 2004, Jeff Elkins wrote: Ouch! I'm located somewhere deep within a portupgrade cycle. I misunderstood the command (portupgrade -a), and assumed that it would only upgrade ports that I had installed, not pkgs installed with pkg_add -r. How can I avoid portupgrade touching big packages such as KDE, Mozilla and OpenOffice which were installed from binary? Look for HOLD_PKGS in /usr/local/etc/pkgtools.conf -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ Axioms speak louder than words. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade
On Friday 23 January 2004 6:21 pm, Jan Grant wrote: On Fri, 23 Jan 2004, Jeff Elkins wrote: Ouch! I'm located somewhere deep within a portupgrade cycle. I misunderstood the command (portupgrade -a), and assumed that it would only upgrade ports that I had installed, not pkgs installed with pkg_add -r. How can I avoid portupgrade touching big packages such as KDE, Mozilla and OpenOffice which were installed from binary? Look for HOLD_PKGS in /usr/local/etc/pkgtools.conf Thanks, Jan. Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade overkill?
From: Herculano de Lima Einloft Neto [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: portupgrade overkill? Date: Sat, 29 Nov 2003 05:16:43 -0200 Hello people, Check this out, if you will: ]# portinstall -RPv urwfonts Have you checked # man portinstall with a /-R you will find -R --upward-recursive Act on all those packages required by the given packages as well. (When specified with -F, fetch recursively, including the brand new, uninstalled ports that an upgraded port requires) and just for fun because it could be confusing later /-r -r --recursiveAct on all those packages depending on the given packages as well. I tend to like -u -P -p -a -i on different occasions also. provecho - enjoy, (...) --- Reporting the results (+:done / -:ignored / *:skipped / !:failed) + urwfonts-1.0 - pkgconfig-0.15.0 + perl-5.6.1_13 + imake-4.3.0 + freetype2-2.1.4_1 - expat-1.95.6_1 + fontconfig-2.2.0 + XFree86-libraries-4.3.0_5 #why were these 5 pkgs _fetched_? (...) pkg_add: warning: package 'urwfonts-1.0' requires 'perl-5.6.1_13', but 'perl-5.6.1_14' is installed pkg_add: warning: package 'urwfonts-1.0' requires 'imake-4.3.0', but 'imake-4.3.0_1' is installed pkg_add: warning: package 'urwfonts-1.0' requires 'freetype2-2.1.4_1', but 'freetype2-2.1.5_1' is installed pkg_add: warning: package 'urwfonts-1.0' requires 'fontconfig-2.2.0', but 'fontconfig-2.2.90_3' is installed pkg_add: warning: package 'urwfonts-1.0' requires 'XFree86-libraries-4.3.0_5', but 'XFree86-libraries-4.3.0_6' is installed --- Installation of urwfonts-1.0 ended at: Sat, 29 Nov 2003 04:24:25 -0200 (consumed 00:00:02) --- Fresh installation of x11-fonts/urwfonts ended at: Sat, 29 Nov 2003 04:24:25 -0200 (consumed 00:15:45) [Updating the pkgdb format:bdb1_btree in /var/db/pkg ... - 205 packages found (-0 +1) . done] --- Reporting the results (+:done / -:ignored / *:skipped / !:failed) - devel/libtool13 (libtool-1.3.5_1) - lang/perl5 (perl-5.6.1_14) - textproc/expat2 (expat-1.95.6_1) - devel/imake-4 (imake-4.3.0_1) - converters/libiconv (libiconv-1.9.1_3) - devel/gettext (gettext-0.12.1) - devel/gmake (gmake-3.80_1) - print/freetype2 (freetype2-2.1.5_1) - devel/pkgconfig (pkgconfig-0.15.0) - x11-fonts/fontconfig (fontconfig-2.2.90_3) - x11/XFree86-4-libraries (XFree86-libraries-4.3.0_6) + x11-fonts/urwfonts portupgrade sometimes gives me the impression of taking a lot of time turning simple updates to recursive crusades, but I have always trusted it's sanity. This could be a local problem, but thought I'd let you know. Best, -- Herculano de Lima Einloft Neto ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] _ Set yourself up for fun at home! Get tips on home entertainment equipment, video game reviews, and more here. http://special.msn.com/home/homeent.armx ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -Fa
Sorry, Your mail was cougth in my junk box. On Mon, Oct 13, 2003 at 11:43:47AM +0200, [EMAIL PROTECTED] wrote: Alex de Kruijff writes: On Fri, Oct 10, 2003 at 01:29:40PM +0200, Patrick O'Reilly wrote: The strange part is that on some of the servers the script works just fine, and on others it runs, and emails me what looks like a job well done, but the distfile has NOT been fetched. When I then go to do the actual upgrade, the distfile must first be fetched by portupgrade before it proceeds to build. There could be any number of problems that may be the cause of this. I realy can't see that from here. What you need to do is to do a check on every machine that doesn't work. I find it best to go from where the process begins and go all the way down to portupgrade. Try to find where it goes wrong. It could be that the crontab is wrong or that portupgrade isn't installed. Alex, thanks for your response. I've tried what you say before I sent the email. What confuses me is that the script runs fine if I log in and run it at the CLI. And it definitely runs from cron, because I get the email I am expecting, which is the output that would normally go to the terminal. You will have to add lines that print output to see where it goes wrong. So, the crontab is evidently active, and portupgrade is correctly installed and configured. The problem lies in beneith. But the actual fetch of the file simply does not happen if it is run from cron... Yet, on other servers it all works fine... ?!?!?!? Still confused. Patrick. Its posible that you didn't write all calls to there full path. On the shell you can type portrupgrade to start it. But from cron you have to write /usr/local/sbin/portupgrade. -- Alex My homepage (dutch) - http://www.kruijff.org/alex/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -arR
On Tue, 11 Nov 2003, William O'Higgins wrote: Quite foolishly, I ran this command without thinking it through: portupgrade -arR It's been running for 15 hours or so now, and I'm wondering how much longer it is likely to take? I realize that that depends grin / Well, that depends; many ports can be upgraded quickly. However compilation of C++ is markedly slower than compilation of C, so whenever you see things like KDE or Qt meeding an upgrade, expect it to take a while. If you use portversion -v | grep -v = then you'll see the list of ports which remain that need updating. (You need to run portsdb after a cvsup for the output of this, and portupgrade's operation, to be accurate.) Any suggestions? Thanks. If you've got packages installed that you don't want, portupgrade _can_ be safely interrupted and will pick up pretty much from where it left off when you kick it off again. It's often worthwhile checking the Makefiles for the ports you install for tunable variables. Many ports offer interactive menus to select features to build; Murphy's law would suggest that one of these might well pop up just after you leave portupgrade to do its thing and go to bed. You can normally select batch operation and choose the appropriate options by putting them into /usr/local/etc/pkgtools.conf; the exact mechanism used to indicate non-interactive mode isn't uniform across all ports, however. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ printf 'cat\nhello world' | `sh -c 'read c; echo $c'` ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -arR
- Original Message - From: Jan Grant [EMAIL PROTECTED] Sent: Wednesday, November 12, 2003 2:37 AM On Tue, 11 Nov 2003, William O'Higgins wrote: Quite foolishly, I ran this command without thinking it through: portupgrade -arR It's been running for 15 hours or so now, and I'm wondering how much longer it is likely to take? I realize that that depends grin / Well, that depends; many ports can be upgraded quickly. However compilation of C++ is markedly slower than compilation of C, so whenever you see things like KDE or Qt meeding an upgrade, expect it to take a while. If you use portversion -v | grep -v = then you'll see the list of ports which remain that need updating. (You need to run portsdb after a cvsup for the output of this, and portupgrade's operation, to be accurate.) Or you can use the (IMHO) simpler 'portversion -vL=' to get the same information. Cheers, Drew ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -arR
William O'Higgins wrote: Quite foolishly, I ran this command without thinking it through: portupgrade -arR It's been running for 15 hours or so now, and I'm wondering how much longer it is likely to take? I realize that that depends grin /, but I've love some anecdotal hints if anyone's got some. I installed 4.8 from a CD, and didn't upgrade much of anything, and I have since CVSup'd a new ports tree, built the pkgdb and now portupgrade is just running and running. It's not looping, it's just working away, and I have no idea where it is in the process (it compiling kdeutils as we speak - I wish I'd remembered to uninstall *that* before I started). Any suggestions? Thanks. Don't know that it's foolish, though it's best to have done this via X, I guess... you could just watch it work in an xterm or something. I guess if you're in CLI, you could ALT-F2 to another virtual terminal and still work a bit? -arR generally takes a day and a half for my desktop machine. Most of the time spent, though, in retrospect, is grabbing new tarballs over a modem connection... Kevin Kinsey DaleCo, S.P. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -arR
On Tuesday 11 November 2003 18:33, William O'Higgins wrote: Quite foolishly, I ran this command without thinking it through: portupgrade -arR Try the -n switch (ie. portupgrade -narR), this will show which ports will be upgraded without doing so. Bjarne ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -arR
On Tuesday 11 November 2003 01:39 pm, Bjarne Wichmann Petersen wrote: On Tuesday 11 November 2003 18:33, William O'Higgins wrote: Quite foolishly, I ran this command without thinking it through: portupgrade -arR Try the -n switch (ie. portupgrade -narR), this will show which ports will be upgraded without doing so. The great thing about this, is once you have done this for the 1st time (as you have) and if you continue to update your ports tree (perhaps on a nightly basis) you can run portupgrade daily, and the time needed is sooo much shorter. On a personal note - I do update my ports nightly, then run portgrade -arR daily. I don't think it runs more then 10 mins on any day. Welcome to the world of maintaining your ports! Bjarne ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Best regards, Chris __ PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363 PGP Mail encouraged / preferred - keys available on common key servers __ 01010010011101100011011001010111001001011000 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -arR
On Tue, Nov 11, 2003 at 06:24:31PM -0600, Chris wrote: On Tuesday 11 November 2003 01:39 pm, Bjarne Wichmann Petersen wrote: On Tuesday 11 November 2003 18:33, William O'Higgins wrote: Quite foolishly, I ran this command without thinking it through: portupgrade -arR Try the -n switch (ie. portupgrade -narR), this will show which ports will be upgraded without doing so. The great thing about this, is once you have done this for the 1st time (as you have) and if you continue to update your ports tree (perhaps on a nightly basis) you can run portupgrade daily, and the time needed is sooo much shorter. On a personal note - I do update my ports nightly, then run portgrade -arR daily. I don't think it runs more then 10 mins on any day. Welcome to the world of maintaining your ports! Do you happen to run apache and php4? I had trouble with these two. One didn't need to be updated and the other did. The result was that apache didn't wan't to load php4. I had to fore the compilation of the other port. -- Alex ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade auto deinstall+reinstall?
On Friday 24 October 2003 10:41 am, Jesse Guardiani wrote: Howdy list, Sorry if this is an obvious question, but I didn't find anything in the portupgrade manpage. I'm in the process of upgrading the ports on my 5.1-RELEASE laptop, and I just executed the following command: portupgrade -R 'grip*' And it's giving me the following message: -- === Checking if x11/libgnome already installed === An older version of x11/libgnome is already installed (libgnome-2.2.0.1) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of x11/libgnome without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/x11/libgnome. *** Error code 1 Now, I know how to get around this manually: pkg_delete -f 'libgnome-*' And then rerun `portupgrade -R 'grip*'`. However, is there a way to automate this process? It's happened three times already on this one port, and I'm getting a bit annoyed. I was hoping it would be done the first time I came back from lunch. :) Thanks! You can use -Rf but that will update everything that is a dependancy for grip. What you did is probably much faster than that :). That includes the time you spent eating lunch. I come from the programming world and to update a library and not update the codes that use it really bothers me. I do what you did but I keep thinking about all of the problems that I could be causing. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade auto deinstall+reinstall?
Kent Stewart wrote: On Friday 24 October 2003 10:41 am, Jesse Guardiani wrote: Howdy list, Sorry if this is an obvious question, but I didn't find anything in the portupgrade manpage. I'm in the process of upgrading the ports on my 5.1-RELEASE laptop, and I just executed the following command: portupgrade -R 'grip*' And it's giving me the following message: -- === Checking if x11/libgnome already installed === An older version of x11/libgnome is already installed (libgnome-2.2.0.1) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of x11/libgnome without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/x11/libgnome. *** Error code 1 Now, I know how to get around this manually: pkg_delete -f 'libgnome-*' And then rerun `portupgrade -R 'grip*'`. However, is there a way to automate this process? It's happened three times already on this one port, and I'm getting a bit annoyed. I was hoping it would be done the first time I came back from lunch. :) Thanks! You can use -Rf but that will update everything that is a dependancy for grip. What you did is probably much faster than that :). That includes the time you spent eating lunch. I come from the programming world and to update a library and not update the codes that use it really bothers me. I do what you did but I keep thinking about all of the problems that I could be causing. Ah. I see. It's binary compatibility thing. Portupgrade has no way of knowing if the new package is binary compatible with the old package, so it builds the new package, uninstalls the old package, and installs the new one. Grrr... OK. I guess I'll just have to rebuild my entire ports tree if I want it done right. Thanks. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade auto deinstall+reinstall?
On Friday 24 October 2003 01:38 pm, Jesse Guardiani wrote: Kent Stewart wrote: On Friday 24 October 2003 10:41 am, Jesse Guardiani wrote: Howdy list, Sorry if this is an obvious question, but I didn't find anything in the portupgrade manpage. I'm in the process of upgrading the ports on my 5.1-RELEASE laptop, and I just executed the following command: portupgrade -R 'grip*' And it's giving me the following message: -- === Checking if x11/libgnome already installed === An older version of x11/libgnome is already installed (libgnome-2.2.0.1) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of x11/libgnome without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/x11/libgnome. *** Error code 1 Now, I know how to get around this manually: pkg_delete -f 'libgnome-*' And then rerun `portupgrade -R 'grip*'`. However, is there a way to automate this process? It's happened three times already on this one port, and I'm getting a bit annoyed. I was hoping it would be done the first time I came back from lunch. :) Thanks! You can use -Rf but that will update everything that is a dependancy for grip. What you did is probably much faster than that :). That includes the time you spent eating lunch. I come from the programming world and to update a library and not update the codes that use it really bothers me. I do what you did but I keep thinking about all of the problems that I could be causing. Ah. I see. It's binary compatibility thing. Portupgrade has no way of knowing if the new package is binary compatible with the old package, so it builds the new package, uninstalls the old package, and installs the new one. Grrr... OK. I guess I'll just have to rebuild my entire ports tree if I want it done right. Not all of the time. For example, the only one in recent time was the gettext library problem. The other thing is why are you telling portupgrade to recursively build all of grip's dependancies when you may not need to. I look at what portversion tells me is out of date first. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade auto deinstall+reinstall?
Kent Stewart wrote: On Friday 24 October 2003 01:38 pm, Jesse Guardiani wrote: Kent Stewart wrote: On Friday 24 October 2003 10:41 am, Jesse Guardiani wrote: [...] I come from the programming world and to update a library and not update the codes that use it really bothers me. I do what you did but I keep thinking about all of the problems that I could be causing. Ah. I see. It's binary compatibility thing. Portupgrade has no way of knowing if the new package is binary compatible with the old package, so it builds the new package, uninstalls the old package, and installs the new one. Grrr... OK. I guess I'll just have to rebuild my entire ports tree if I want it done right. Not all of the time. For example, the only one in recent time was the gettext library problem. The other thing is why are you telling portupgrade to recursively build all of grip's dependancies when you may not need to. I look at what portversion tells me is out of date first. You mean portupgrade won't recursively upgrade my ports that are out of date? It rebuilds ALL of them? Hmmm... I never noticed that before. That stinks! I'm looking for an automated upgrade proceedure here. portupgrade doesn't seem to be giving it to me. -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade auto deinstall+reinstall?
On Friday 24 October 2003 02:41 pm, Jesse Guardiani wrote: Kent Stewart wrote: On Friday 24 October 2003 01:38 pm, Jesse Guardiani wrote: Kent Stewart wrote: On Friday 24 October 2003 10:41 am, Jesse Guardiani wrote: [...] I come from the programming world and to update a library and not update the codes that use it really bothers me. I do what you did but I keep thinking about all of the problems that I could be causing. Ah. I see. It's binary compatibility thing. Portupgrade has no way of knowing if the new package is binary compatible with the old package, so it builds the new package, uninstalls the old package, and installs the new one. Grrr... OK. I guess I'll just have to rebuild my entire ports tree if I want it done right. Not all of the time. For example, the only one in recent time was the gettext library problem. The other thing is why are you telling portupgrade to recursively build all of grip's dependancies when you may not need to. I look at what portversion tells me is out of date first. You mean portupgrade won't recursively upgrade my ports that are out of date? It rebuilds ALL of them? It didn't in the past. You only had to create packages and you would see them with 1-2 minute differences in creation times. That is only long enough to re-package the large tarball, which is what I see it doing. Hmmm... I never noticed that before. That stinks! I could be also wrong. When it comes to computers, truth is a sliding window. I'm looking for an automated upgrade proceedure here. portupgrade doesn't seem to be giving it to me. You are also looking for a quick solution and that is what portupgrade doesn't always provide. It can't make the decision of rebuilding what has been updated versus rebuilding everything is needed. There isn't any magic flag in the port tree to tell portupgrade that all of the dependant ports need to be updated. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problems, please help
What versions of ruby do you have installed? I can remember back a few versions, that uninstalling portupgrade and ruby and then making and installing portupgrade was faster than fighting the problems with ruby. Kent -su-2.05b# ruby -v ruby 1.6.8 (2003-03-26) [i386-freebsd5] Ivan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade
Ralph wrote: I'm running 5.1 and I'm having the same problem as the other person with portupgrade ... so how do I uninstall Ruby? and portupgrade? # pkg_delete -rx ruby # cd /usr/ports/sysutils/portupgrade # make install clean Regards, Jens ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problems, please help
On Wednesday 22 October 2003 05:37 am, ivan georgiev wrote: What versions of ruby do you have installed? I can remember back a few versions, that uninstalling portupgrade and ruby and then making and installing portupgrade was faster than fighting the problems with ruby. Kent -su-2.05b# ruby -v ruby 1.6.8 (2003-03-26) [i386-freebsd5] I don't have any idea. It looks like a source/configuration/make error of some type. My version is the also the following ruby 1.6.8 (2003-03-26) [i386-freebsd5] I didn't have any problem re-building portupgrade and the ruby tools using portupgrade -pufr ruby. My last cvsup was on 15 Oct, which is a little bit old. So, I recvsuped ports-all and, as always, re-built INDEX and INDEX.db. I use make index to update INDEX and the only refuse I have is ports/INDEX-5. Since I rebuild the INDEXs everytime I cvsup ports-all, there isn't any point in having cvsup grab a current copy of INDEX-5, which is always out of date. After INDEX.db was rebuilt, I reran the -pufr update of ruby and didn't have any problems. My setup is KISS simple. I use the stock gcc that comes with 5-current. I don't use options for the build flags in /etc/make.conf. My port tree is also located in /usr/ports. The only thing different on my FreeBSD-5-current machine is the packages produced by portupgrade are stored on a different fs called /usr3/All. That shouldn't make any difference to the build process. The iso images for version 5.1-Release were built on 5 Jun, which is several months after the last changes to ruby-1.6.8. A uname -a of my system shows FreeBSD opal 5.1-CURRENT FreeBSD 5.1-CURRENT #41: Wed Oct 15 You aren't the only one with problems and it may be something simple like a trashed ruby patch file. I haven't seen them re-roll the tarballs for ruby, which is only seen when the checksums don't agree. Since I don't have a 5.1-release system, there isn't much else that I can try. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problems, please help
Kent Stewart wrote: On Wednesday 22 October 2003 05:37 am, ivan georgiev wrote: What versions of ruby do you have installed? I can remember back a few versions, that uninstalling portupgrade and ruby and then making and installing portupgrade was faster than fighting the problems with ruby. Kent -su-2.05b# ruby -v ruby 1.6.8 (2003-03-26) [i386-freebsd5] I don't have any idea. It looks like a source/configuration/make error of some type. My version is the also the following ruby 1.6.8 (2003-03-26) [i386-freebsd5] Maybe complete remove of ruby and dependend packages followed by a reinstall of all of them may help. If you only have portupgrade installed, you can simply # pkg_delete -rx ruby # cd /usr/ports/sysutils/portupgrade # make install clean If you have other ruby-dependend ports, please write them down, eg. by $ cd $ ls -l /var/db/pkg/ installed-packages $ su - # [above procedure] $ ls -l /var/db/pkg/ after-reinstall-ruby-packages $ diff installed-packages after-reinstall-ruby-packages And then reinstall all packages missing (and you need). Regards, Jens ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problems, please help
Kent Stewart wrote: On Wednesday 22 October 2003 05:37 am, ivan georgiev wrote: What versions of ruby do you have installed? I can remember back a few versions, that uninstalling portupgrade and ruby and then making and installing portupgrade was faster than fighting the problems with ruby. Kent -su-2.05b# ruby -v ruby 1.6.8 (2003-03-26) [i386-freebsd5] I don't have any idea. It looks like a source/configuration/make error of some type. My version is the also the following ruby 1.6.8 (2003-03-26) [i386-freebsd5] Maybe complete remove of ruby and dependend packages followed by a reinstall of all of them may help. If you only have portupgrade installed, you can simply # pkg_delete -rx ruby # cd /usr/ports/sysutils/portupgrade # make install clean If you have other ruby-dependend ports, please write them down, eg. by $ cd $ ls -l /var/db/pkg/ installed-packages $ su - # [above procedure] $ ls -l /var/db/pkg/ after-reinstall-ruby-packages $ diff installed-packages after-reinstall-ruby-packages And then reinstall all packages missing (and you need). Thanks for all of the suggestions! Finaly portupgrade -arR works again. Here is what I did (chronologically) 1) ls -l /var/db/pkg/ ~/old 2) pkg_delete -rx ruby 3) cd /usr/ports/sysutils/portupgrade; make install; make clean 4) ls -l /var/db/pkg/ ~/new 5) diff ~/old ~/new which showed no other difference but for the new installed ruby; 6)/usr/local/sbin/pkgdb -fuF 7)/usr/local/sbin/portupgrade -arR the result was :( Then I tried the other suggestion: 8)cd /usr/ports 9) make index which produced zillion of outputs like: make_index: xcdplayer-2.2_1: no entry for /usr/ports/x11/ XFree86-4-libraries 10) /usr/local/sbin/pkgdb -fuF 11) /usr/local/sbin/portupgrade -arR which took much longer than usual to say something the result is :) Ivan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problems, please help
On Wednesday 22 October 2003 05:02 pm, ivan georgiev wrote: Kent Stewart wrote: On Wednesday 22 October 2003 05:37 am, ivan georgiev wrote: What versions of ruby do you have installed? I can remember back a few versions, that uninstalling portupgrade and ruby and then making and installing portupgrade was faster than fighting the problems with ruby. Kent -su-2.05b# ruby -v ruby 1.6.8 (2003-03-26) [i386-freebsd5] I don't have any idea. It looks like a source/configuration/make error of some type. My version is the also the following ruby 1.6.8 (2003-03-26) [i386-freebsd5] Maybe complete remove of ruby and dependend packages followed by a reinstall of all of them may help. If you only have portupgrade installed, you can simply # pkg_delete -rx ruby # cd /usr/ports/sysutils/portupgrade # make install clean If you have other ruby-dependend ports, please write them down, eg. by $ cd $ ls -l /var/db/pkg/ installed-packages $ su - # [above procedure] $ ls -l /var/db/pkg/ after-reinstall-ruby-packages $ diff installed-packages after-reinstall-ruby-packages And then reinstall all packages missing (and you need). Thanks for all of the suggestions! Finaly portupgrade -arR works again. Here is what I did (chronologically) 1) ls -l /var/db/pkg/ ~/old 2) pkg_delete -rx ruby 3) cd /usr/ports/sysutils/portupgrade; make install; make clean 4) ls -l /var/db/pkg/ ~/new 5) diff ~/old ~/new which showed no other difference but for the new installed ruby; 6)/usr/local/sbin/pkgdb -fuF 7)/usr/local/sbin/portupgrade -arR the result was :( Then I tried the other suggestion: 8)cd /usr/ports 9) make index which produced zillion of outputs like: make_index: xcdplayer-2.2_1: no entry for /usr/ports/x11/ XFree86-4-libraries You must have been lucky because a condensed version of a recent cvsup of ports-all on my 5-current machine looks like Edit ports/www/epiphany/pkg-plist Add delta 1.16 2003.10.22.17.20.29 marcus Shutting down connection to server Finished successfully Generating INDEX-5 - please wait.. Done. [Updating the portsdb format:bdb1_btree in /usr/ports ... - 9533 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000. . done] All of your messages would have appeared between wait.. and done. I use a script to do all of my cvsups because I use a thing called cvsuplog, that was written by Ben Smithurst, to convert my redirected cvsup.log into HTML links to cvsweb.cgi. I use make index to update INDEX-5 and portsdb -u to update INDEX.db. I have been told that portupgrade will build INDEX.db if it is out of date but I want to see it on the monitor. Since all I did is type uports, running an extra process is a not a big deal. 10) /usr/local/sbin/pkgdb -fuF 11) /usr/local/sbin/portupgrade -arR which took much longer than usual to say something the result is :) Great!! Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problems, please help
On Tuesday 21 October 2003 05:48 pm, ivan georgiev wrote: I use 5_1_RELEASE. I do not know what happened but now I get: -su-2.05b# portupgrade -arR /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:325:in `deorigin': failed to convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:918:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:917:in `each' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:917:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:909:in `each' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:909:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:931:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:935:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1846 Can someone tell how to fix it. I tried pkgdb -uf but it doesn't help. You may try to remove /var/db/pkg/pkgdb.db and pkgdb -u again. Thanks, but it didn't cure it :( I would force upgrade portupgrade before you do anything using portupgrade -Rf portupgrade. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problems, please help
On Tuesday 21 October 2003 09:02 pm, Kent Stewart wrote: On Tuesday 21 October 2003 05:48 pm, ivan georgiev wrote: I use 5_1_RELEASE. I do not know what happened but now I get: -su-2.05b# portupgrade -arR /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:325:in `deorigin': failed to convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:918:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:917:in `each' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:917:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:909:in `each' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:909:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:931:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:935:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1846 Can someone tell how to fix it. I tried pkgdb -uf but it doesn't help. You may try to remove /var/db/pkg/pkgdb.db and pkgdb -u again. Thanks, but it didn't cure it :( I would force upgrade portupgrade before you do anything using portupgrade -Rf portupgrade. /usr/local/sbin/pkgdb -fuF /usr/local/sbin/portupgrade -arR -- Best regards, Chris __ PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363 PGP Mail encouraged / preferred - keys available on common key servers __ 01010010011101100011011001010111001001011000 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problems, please help
I use 5_1_RELEASE. I do not know what happened but now I get: -su-2.05b# portupgrade -arR /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:325:in `deorigin': failed to convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:918:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:917:in `each' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:917:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:909:in `each' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:909:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:931:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:935:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1846 Can someone tell how to fix it. I tried pkgdb -uf but it doesn't help. You may try to remove /var/db/pkg/pkgdb.db and pkgdb -u again. Thanks, but it didn't cure it :( I would force upgrade portupgrade before you do anything using portupgrade -Rf portupgrade. /usr/local/sbin/pkgdb -fuF /usr/local/sbin/portupgrade -arR Thanks for the input, portupgrade -Rf portupgrade. did not help. As well as /usr/local/sbin/pkgdb -fuF Still :( ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problems, please help
On Tuesday 21 October 2003 07:50 pm, ivan georgiev wrote: I use 5_1_RELEASE. I do not know what happened but now I get: -su-2.05b# portupgrade -arR /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:325:in `deorigin': failed to convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:918:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:917:in `each' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:917:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:909:in `each' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:909:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:931:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:935:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1846 Can someone tell how to fix it. I tried pkgdb -uf but it doesn't help. You may try to remove /var/db/pkg/pkgdb.db and pkgdb -u again. Thanks, but it didn't cure it :( I would force upgrade portupgrade before you do anything using portupgrade -Rf portupgrade. /usr/local/sbin/pkgdb -fuF /usr/local/sbin/portupgrade -arR Thanks for the input, portupgrade -Rf portupgrade. did not help. As well as /usr/local/sbin/pkgdb -fuF Still :( What versions of ruby do you have installed? I can remember back a few versions, that uninstalling portupgrade and ruby and then making and installing portupgrade was faster than fighting the problems with ruby. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -Fa
Alex de Kruijff writes: On Fri, Oct 10, 2003 at 01:29:40PM +0200, Patrick O'Reilly wrote: The strange part is that on some of the servers the script works just fine, and on others it runs, and emails me what looks like a job well done, but the distfile has NOT been fetched. When I then go to do the actual upgrade, the distfile must first be fetched by portupgrade before it proceeds to build. There could be any number of problems that may be the cause of this. I realy can't see that from here. What you need to do is to do a check on every machine that doesn't work. I find it best to go from where the process begins and go all the way down to portupgrade. Try to find where it goes wrong. It could be that the crontab is wrong or that portupgrade isn't installed. Alex, thanks for your response. I've tried what you say before I sent the email. What confuses me is that the script runs fine if I log in and run it at the CLI. And it definitely runs from cron, because I get the email I am expecting, which is the output that would normally go to the terminal. So, the crontab is evidently active, and portupgrade is correctly installed and configured. But the actual fetch of the file simply does not happen if it is run from cron... Yet, on other servers it all works fine... ?!?!?!? Still confused. Patrick. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -Fa
On Fri, Oct 10, 2003 at 01:29:40PM +0200, Patrick O'Reilly wrote: Here's a strange thing: I have a number of servers which all run a portupgrade script every night to fetch the latest distfiles automatically. I then complete the upgrade when I decide I'm in the mood :) The strange part is that on some of the servers the script works just fine, and on others it runs, and emails me what looks like a job well done, but the distfile has NOT been fetched. When I then go to do the actual upgrade, the distfile must first be fetched by portupgrade before it proceeds to build. Does anyone know what might cause this? There could be any number of problems that may be the cause of this. I realy can't see that from here. What you need to do is to do a check on every machine that doesn't work. I find it best to go from where the process begins and go all the way down to portupgrade. Try to find where it goes wrong. It could be that the crontab is wrong or that portupgrade isn't installed. -- Alex Articles based on solutions that I use: http://www.kruijff.org/alex/index.php?dir=docs/FreeBSD/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade and USE_GCC=3.3
On Thu, Oct 09, 2003 at 11:18:49AM +0200, Herbert wrote: Am I doing something wrong or is this a bug? This is a FAQ - you're doing something wrong. USE_GCC is a makefile-internal variable. Kris pgp0.pgp Description: PGP signature
Re: Portupgrade
On Thu, Sep 04, 2003 at 01:56:58AM +0200, Stefan Malte Schumacher wrote: Hi I have just run portupgrade -a for the first time. About 2 hours later I realized that portupgrade is not only building the port I built myself from /usr/ports but also the packages which I did install from the CD. I do not want to build Mozilla or XFree myself, is there a way I can exclude such large programs from being updated ? Are installed ports and packages stored in the same database ? portupgrade has a config file (/usr/local/etc/pkgtools.conf), which offers many config options for you to tweak - including the ability to specify ports to ignore - look for the section about HOLD_PKGS. Ports and packages keep their install data in the same place, yes - /var/db/pkg. For the next question I just need a pointer to the right documentation ; I would like to read more about using sysinstall to upgrade my system instead of make world. Have you read man sysinstall? But bear in mind that make buildworld was carefully designed to upgrade the system properly. Is there some kind of packageupgrade which downloads and installs new packages for stuff I do not want to build myself ? The -P or -PP options to portupgrade should work, but read the manpage for caveats. HTH Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgp0.pgp Description: PGP signature
Re: Portupgrade
On Wednesday 03 September 2003 05:15 pm, Daniel Bye wrote: On Thu, Sep 04, 2003 at 01:56:58AM +0200, Stefan Malte Schumacher wrote: Hi I have just run portupgrade -a for the first time. About 2 hours later I realized that portupgrade is not only building the port I built myself from /usr/ports but also the packages which I did install from the CD. I do not want to build Mozilla or XFree myself, is there a way I can exclude such large programs from being updated ? Are installed ports and packages stored in the same database ? portupgrade has a config file (/usr/local/etc/pkgtools.conf), which offers many config options for you to tweak - including the ability to specify ports to ignore - look for the section about HOLD_PKGS. Ports and packages keep their install data in the same place, yes - /var/db/pkg. For the next question I just need a pointer to the right documentation ; I would like to read more about using sysinstall to upgrade my system instead of make world. Have you read man sysinstall? But bear in mind that make buildworld was carefully designed to upgrade the system properly. Is there some kind of packageupgrade which downloads and installs new packages for stuff I do not want to build myself ? The -P or -PP options to portupgrade should work, but read the manpage for caveats. There is also the -x option. You have to understand that if you are upgrading a library, you may need to upgrade everything that uses that library as a dependancy. For example, lets assume that XFree86-libraries is updated because they find an error in one of the header files. Every program that uses that header file should be rebuilt. I rarely update my entire system when a library is updated. You just have to be aware of the consequences that may occur if you don't do the update. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problem (was Re: orphaned port?)
On Sat, Aug 23, 2003 at 04:05:05PM -0700 or thereabouts, paul beard wrote: I am having this problem as well on any port I try to install. I have rebuilt pkgdb from scratch. === Installing for p5-SNMP_Session-0.95 === Generating temporary packing list === Checking if net/p5-SNMP_Session already installed *** Error code 1 Stop in /usr/ports/net/p5-SNMP_Session. *** Error code 1 Stop in /usr/ports/net/mrtg. [ ... ] Then breaking it down to run just the first command makes me wonder what's wrong with pkg_info. [/usr/ports/net/mrtg]:: /usr/sbin/pkg_info -q -O net/p5-SNMP_Session pkg_info: illegal option -- O usage: pkg_info [-cdDfGiIkLmopqrRsvVx] [-e package] [-l prefix] [-t template] [-W filename] [pkg-name ...] pkg_info -a [flags] the O option doesn't seem to be in the man page, so I'm not sure what's up. This is a VFAQ lately. You need FBSD 4.7 or better. -- Josh -- Paul Beard http://paulbeard.no-ip.org/movabletype/ whois -h whois.networksolutions.com ha=pb202 E Pluribus Unix ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problem (was Re: orphaned port?)
Joshua Oreman wrote: This is a VFAQ lately. You need FBSD 4.7 or better. No, you just need to install sysutils/pkg_install. I would suspect it's a POLA violation to require an upgrade to get around a new version of a utility program. -- Paul Beard http://paulbeard.no-ip.org/movabletype/ whois -h whois.networksolutions.com ha=pb202 Do not read this fortune under penalty of law. Violators will be prosecuted. (Penal Code sec. 2.3.2 (II.a.)) ___ [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]
Re: Portupgrade Broke?
Khairil Yusof wrote: On Sat, 2003-08-09 at 22:07, Bob Perry wrote: I run FreeBSD 4.7 RELEASE. Just ran the portversion command for the first time since last Saturday and the ouptut indicated that my installed packages were up-to-date. Thought it odd so I ran pkg_version command and picked up 9 packages in need up upgrade and several orphaned packages listed. Is there a known problem with the portupgrade system or was there some warning I missed previously? If I'm not wrong, portversion/pkg_version relies on ports index (man 8 portupgrade) which needs to be up to date in order for portversion to be accurate. This is not done on a daily basis for the ports tree (as it takes some time). What you should try to do is check that your pkgdb is ok and fix any problems: #pkgdb -F then update the ports index (which takes a while) #portsdb -Uu Then run your portversion/pkg_version which should give more accurate results. Hope this helps. First, thanks for taking the time to respond. Yesterday, I brought all of my packages up-to-date, ran pkgdb -F, followed by portsdb -Uu and rhe output from both portversion and pkg_version matched. I slept well. This morning, portversion indicated that all packages were current but pkg_version showed p5-Date-Manip-5.40 needed to be upgraded to 5.42. I ran portupgrade expecting to receive a message indicating that the package was current, but instead, it fetched, built, installed, p5-Date-Manip-5.42 and I thought, removed p5-Date-Manip-5.40. I ran portversion again and it indicates that p5-Date-Manip-5.42 succeeds port (port has 5.40). Pkg_version shows p5-Date-Manip-5.42 is up-to-date with port. Looks as though the portversion program may not be reading the port tree accurately (?). I'll have to do more investigation. Maybe I broke something. Thanks again. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade Broke?
It doesn't read the tree. It uses INDEX.db, which you are supposed to build after each cvsup of ports-all. To build INDEX.db, you need a current version of INDEX. I get too many messages from portsdb -U and use the sequence make index and then portsdb -u. I run these everytime I cvsup ports-all. The only time you can save is adding ports/INDEX to your refuse file. There isn't any point in downloading INDEX and rebuilding it immediately after cvsup finishes. If you have more ports in your refuse file, running portsdb -U is probably your only choice. Make is known to stop when it hits a port that is missing in your /usr/port fs. I think I have a better understanding now of this process. It's also clear that I have to spend more time with the available documentation. Thanks to you both for taking the time to help. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade Broke?
On Sunday 10 August 2003 07:55 am, Bob Perry wrote: Khairil Yusof wrote: On Sat, 2003-08-09 at 22:07, Bob Perry wrote: I run FreeBSD 4.7 RELEASE. Just ran the portversion command for the first time since last Saturday and the ouptut indicated that my installed packages were up-to-date. Thought it odd so I ran pkg_version command and picked up 9 packages in need up upgrade and several orphaned packages listed. Is there a known problem with the portupgrade system or was there some warning I missed previously? If I'm not wrong, portversion/pkg_version relies on ports index (man 8 portupgrade) which needs to be up to date in order for portversion to be accurate. This is not done on a daily basis for the ports tree (as it takes some time). What you should try to do is check that your pkgdb is ok and fix any problems: #pkgdb -F then update the ports index (which takes a while) #portsdb -Uu Then run your portversion/pkg_version which should give more accurate results. Hope this helps. First, thanks for taking the time to respond. Yesterday, I brought all of my packages up-to-date, ran pkgdb -F, followed by portsdb -Uu and rhe output from both portversion and pkg_version matched. I slept well. This morning, portversion indicated that all packages were current but pkg_version showed p5-Date-Manip-5.40 needed to be upgraded to 5.42. I ran portupgrade expecting to receive a message indicating that the package was current, but instead, it fetched, built, installed, p5-Date-Manip-5.42 and I thought, removed p5-Date-Manip-5.40. I ran portversion again and it indicates that p5-Date-Manip-5.42 succeeds port (port has 5.40). Pkg_version shows p5-Date-Manip-5.42 is up-to-date with port. Looks as though the portversion program may not be reading the port tree accurately (?). It doesn't read the tree. It uses INDEX.db, which you are supposed to build after each cvsup of ports-all. To build INDEX.db, you need a current version of INDEX. I get too many messages from portsdb -U and use the sequence make index and then portsdb -u. I run these everytime I cvsup ports-all. The only time you can save is adding ports/INDEX to your refuse file. There isn't any point in downloading INDEX and rebuilding it immediately after cvsup finishes. If you have more ports in your refuse file, running portsdb -U is probably your only choice. Make is known to stop when it hits a port that is missing in your /usr/port fs. Kent I'll have to do more investigation. Maybe I broke something. Thanks again. Bob ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade Broke?
On Sat, 2003-08-09 at 22:07, Bob Perry wrote: I run FreeBSD 4.7 RELEASE. Just ran the portversion command for the first time since last Saturday and the ouptut indicated that my installed packages were up-to-date. Thought it odd so I ran pkg_version command and picked up 9 packages in need up upgrade and several orphaned packages listed. Is there a known problem with the portupgrade system or was there some warning I missed previously? If I'm not wrong, portversion/pkg_version relies on ports index (man 8 portupgrade) which needs to be up to date in order for portversion to be accurate. This is not done on a daily basis for the ports tree (as it takes some time). What you should try to do is check that your pkgdb is ok and fix any problems: #pkgdb -F then update the ports index (which takes a while) #portsdb -Uu Then run your portversion/pkg_version which should give more accurate results. Hope this helps. -- Optimized, readable, on time; Pick any two. FreeBSD 5.1-CURRENT i386 2:42PM up 7 days, 16:15, 4 users, load averages: 1.05, 0.60, 0.63 signature.asc Description: This is a digitally signed message part
Re: Portupgrade errors
In the last episode (Jul 21), Per olof Ljungmark said: 4.6.2-RELEASE-p13 cvsup very recent I get the following error on all ports I try to upgrade. Have seen similar posts but unable to deduce how the problem was solved. Have run pkgdb -F/portsdb -uU but no change. === Checking if devel/pcre already installed *** Error code 1 Upgrade to FreeBSD 4.8, or manually compile and install the 4.8 /usr/src/usr.sbin/pkg_install programs. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade problems
On Thursday 29 May 2003 11:59 am, Andrea Venturoli wrote: Hello, I have a strange problem on a couple of FreeBSD 4.7 machines which share the same port tree (via NFS). Whenever I try to upgrade a port I get: /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:310:in `deorigin': failed to convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:903:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:902:in `each' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:902:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:894:in `each' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:894:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:916:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:920:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1834 Any hint? There was a similar problem recently and it was caused by adding important items to their refuse file. The refuse was causing poor versions of INDEX and INDEX.db to be created. For make index to work, it needs a full cvsup of ports-all. If you aren't willing to do this, then installing packages will probably be your only problem free method. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade issue
At 08:04 AM 5/29/03, you wrote: On Wed, May 28, 2003 at 05:51:33PM -0700, Joe Kelsey wrote: : follow the suggestion and actually *use* the suggested refuse file you : will then be unable to follow the other suggestion and ever use : portupgrade, or else fix portupgrade so that it does not dump it guts : out if a language dependency is missing. : : Very frustrating and totally unnecessary. Especially since I now have : to waste disk space on language ports. Can't you specify the languages in the IGNORE_CATEGORIES portion of pkgtools.conf? Then you should be able to safely skip it. Doesn't work. I tried it. It doesn't prevent 'portsdb -U' from complaining about the missing dependencies. I don't know what it does* do, but I, too, had to discard my refuse file to cut down on the number of error messages. Roger ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade mess
On Thursday 13 March 2003 11:54 am, [EMAIL PROTECTED] wrote: At 11:22 AM 3/13/2003 -0800, you wrote: I forced the portugrade of imake. That also rebuilt kde-3. I have found that if you don't force, it only updates the ports that have changed. It doesn't take care of the full b-dep dependancy list. Hmmm... now, that's interesting. I did portupgrade of imake (without any special options) before upgrading XFree86 as I needed to use the computer (WinXP) and had to wait until off hours to upgrade the rest. So, I'm wondering if that did not mess up something. I did notice that KDE3 was up-to-date and did not need upgrading, but I caught something about KDE3 upgrade on one of the computers. Does that mean that imake is reponsible somehow for upgrading KDE3? What is the switch to force the upgrade? How did the upgrade of imake lead to the rebuild of kde-3? I see that I only replied to you and not the list. You have to use something like portupgrade -pufr imake. For example, on my system a required by dependancy list for imake shows Information for imake-4.3.0: Required by: ImageMagick-5.5.5 Mesa-3.4.2_2 WordNet-1.7.1 XFree86-4.3.0,1 XFree86-FontServer-4.3.0 XFree86-Server-4.3.0 XFree86-clients-4.3.0 XFree86-documents-4.3.0 XFree86-font100dpi-4.3.0 XFree86-font75dpi-4.3.0 XFree86-fontCyrillic-4.3.0 XFree86-fontDefaultBitmaps-4.3.0 XFree86-fontEncodings-4.3.0 XFree86-fontScalable-4.3.0 XFree86-libraries-4.3.0 XFree86-manuals-4.3.0 Xft-2.1_3 apsfilter-7.2.5_1 arts-1.1,1 cups-1.1.18.0_4 cups-pstoraster-7.05.6 docproj-jadetex-1.10 ghostscript-gnu-7.05_4 gtk-1.2.10_9 html2ps-letter-1.0_1 imlib-1.9.14_1 imwheel-0.9.9 jadetex-3.12_1 kdbg-1.2.5 kde-3.1 kdeartwork-3.1 kdebase-3.1_1 kdegames-3.1 kdegraphics-3.1 kdelibs-3.1 kdemultimedia-3.1 kdenetwork-3.1 kdepim-3.1 kdetoys-3.1_1 kdeutils-3.1 kdevelop-2.1.5 koffice-1.2.1,1 libmpeg2-0.3.1_1 libungif-4.1.0b1 libwmf-0.2.8 links-2.1.p9,1 open-motif-2.2.2_1 peps-1.0 pilot-link-0.11.7_1 qt-3.1.1_4 teTeX-2.0.2 tk-8.3.5 transfig-3.2.4 wrapper-1.0_2 xanim-2.92.0 xfree86_xkb_xml-0.2 xmbmon-201 xmcd-3.2 xmms-esound-1.2.7_3 xmms-kde-3.0.0 If you just use -r imake, you will only update imake and the XFree86-4.3 ports. This leaves a lot of ports linked to old XFree86 libraries. The libraries are probably used dynamicaly but the header files that went along with them have been updated. I believe in a KISS simple, clean setup and will always rebuild anything that has an updated port as an b-dep. The only thing I ignore are utilities such as imake. An upgrade of imake doesn't justify rebuilding everything in my mind; however, a major update of XFree86-libraries is a different matter. If you use -rf, you will update everything in the required by list. It will also take a long time :). Kent BTW, any idea how I could reduce the size of the /usr/ports slice - it's max is about 2Gb and there is about 1.7 in use. It seems a bit bloated and I certainly don't need all the stuff that is in there... Thanks, Phil To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message -- 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 mess
On Thu, Mar 13, 2003 at 07:50:11PM -0800, Daxbert wrote: This will get your distfile downloads out of /usr/ports as well. However, there's probably a cleaner way to do this via a make.conf setting. DISTDIR=/usr/obj/usr/ports/distfiles should do it. Cheers, Scott -- === Scott Mitchell | PGP Key ID | Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines scott at fishballoon.org | 0xAA775B8B | -- Anon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: portupgrade mess
What I did was move my distfiles directory elsewhere and made a symbolic link to it. That means that the pointers are still valid in every compile, but they exist elsewhere... You could just empty distfiles with a rm -rf /usr/ports/distfiles/* (don't forget the *) Anthony On Fri, 2003-03-14 at 14:16, Scott Mitchell wrote: On Thu, Mar 13, 2003 at 07:50:11PM -0800, Daxbert wrote: This will get your distfile downloads out of /usr/ports as well. However, there's probably a cleaner way to do this via a make.conf setting. DISTDIR=/usr/obj/usr/ports/distfiles should do it. Cheers, Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: portupgrade mess
In [EMAIL PROTECTED], Daxbert [EMAIL PROTECTED] typed: Quoting Cliff Sarginson [EMAIL PROTECTED]: BTW, any idea how I could reduce the size of the /usr/ports slice - it's max is about 2Gb and there is about 1.7 in use. It seems a bit bloated and I certainly don't need all the stuff that is in there... Delete everything in /usr/ports/distfiles. And before you go to bed one night do a make clean from /usr/ports. It takes some time... Another option is to add the following to your make.conf ( 5.x: /etc/make.conf 4.x: /etc/defaults/make.conf ) No! 4.x is /etc/make.conf as well. It just doesn't have one by default, whereas 5.x does. You should *never* edit anything in /etc/defaults. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: portupgrade mess
Quoting Mike Meyer [EMAIL PROTECTED]: In [EMAIL PROTECTED], Daxbert [EMAIL PROTECTED] typed: Quoting Cliff Sarginson [EMAIL PROTECTED]: BTW, any idea how I could reduce the size of the /usr/ports slice - it's max is about 2Gb and there is about 1.7 in use. It seems a bit bloated and I certainly don't need all the stuff that is in there... Delete everything in /usr/ports/distfiles. And before you go to bed one night do a make clean from /usr/ports. It takes some time... Another option is to add the following to your make.conf ( 5.x: /etc/make.conf 4.x: /etc/defaults/make.conf ) No! 4.x is /etc/make.conf as well. It just doesn't have one by default, whereas 5.x does. You should *never* edit anything in /etc/defaults. mike -- Ok... so why in 5.x does make.conf no longer live in /etc/defaults as well? --daxbert To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: portupgrade mess
In [EMAIL PROTECTED], Daxbert [EMAIL PROTECTED] typed: Quoting Mike Meyer [EMAIL PROTECTED]: In [EMAIL PROTECTED], Daxbert [EMAIL PROTECTED] typed: Quoting Cliff Sarginson [EMAIL PROTECTED]: BTW, any idea how I could reduce the size of the /usr/ports slice - it's max is about 2Gb and there is about 1.7 in use. It seems a bit bloated and I certainly don't need all the stuff that is in there... Delete everything in /usr/ports/distfiles. And before you go to bed one night do a make clean from /usr/ports. It takes some time... Another option is to add the following to your make.conf ( 5.x: /etc/make.conf 4.x: /etc/defaults/make.conf ) No! 4.x is /etc/make.conf as well. It just doesn't have one by default, whereas 5.x does. You should *never* edit anything in /etc/defaults. Ok... so why in 5.x does make.conf no longer live in /etc/defaults as well? The copy in /etc/defaults was never anything more than documentation on what could go there. It's been moved to /usr/share/examples/make.conf. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: portupgrade mess
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 system, how did you do it? Did you then use portupgrade to upgrade all the ports you had installed? If not, that may be part of the problem. Generally, when upgrading across a release, you want to deinstall the ports in large chunks - all of them is best - and then reinstall the ports from the new ports in the system. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: portupgrade mess
On Thursday 13 March 2003 08:15 am, [EMAIL PROTECTED] wrote: I just upgrade XFree86 from 4.2 to 4.3 using portupgrade on 2 different machines. On one portupgrade seems to have worked ok, except that XFree86 does not function quite correctly - I shall assume it is an XFree86 problem. The second machine is totally screwed up - even though the upgrade did not work, the previous installation is now shot. Startx does not bring up kde3. I really don't know what to do - should I deinstall XFree86 or what? portversion does not work since dependencies are no longer valid. I have never fully understood how the dependencies function in portsdb -F. I don't know how this can be correctly fixed? I don't understand why the upgrade did not work. Does anyone understand any of this? Thanks for any suggestions... I just hit the same thing. It doesn't like the names of my video cards. It is more specific now and I ended up running xf86cfg again. Everything works fine now. 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: portupgrade mess
At 11:22 AM 3/13/2003 -0800, you wrote: I forced the portugrade of imake. That also rebuilt kde-3. I have found that if you don't force, it only updates the ports that have changed. It doesn't take care of the full b-dep dependancy list. Hmmm... now, that's interesting. I did portupgrade of imake (without any special options) before upgrading XFree86 as I needed to use the computer (WinXP) and had to wait until off hours to upgrade the rest. So, I'm wondering if that did not mess up something. I did notice that KDE3 was up-to-date and did not need upgrading, but I caught something about KDE3 upgrade on one of the computers. Does that mean that imake is reponsible somehow for upgrading KDE3? What is the switch to force the upgrade? How did the upgrade of imake lead to the rebuild of kde-3? BTW, any idea how I could reduce the size of the /usr/ports slice - it's max is about 2Gb and there is about 1.7 in use. It seems a bit bloated and I certainly don't need all the stuff that is in there... Thanks, Phil To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: portupgrade mess
On Thu, Mar 13, 2003 at 02:54:03PM -0500, [EMAIL PROTECTED] wrote: At 11:22 AM 3/13/2003 -0800, you wrote: I forced the portugrade of imake. That also rebuilt kde-3. I have found that if you don't force, it only updates the ports that have changed. It doesn't take care of the full b-dep dependancy list. Hmmm... now, that's interesting. It is more than interesting, it is something I have vaguely moaned about already. Portupgrade does not handle the so called meta-ports at all well. Anything like KDE and Gnome as well I suppose, forget it. I did portupgrade of imake (without any special options) before upgrading XFree86 as I needed to use the computer (WinXP) and had to wait until off hours to upgrade the rest. So, I'm wondering if that did not mess up something. I did notice that KDE3 was up-to-date and did not need upgrading, but I caught something about KDE3 upgrade on one of the computers. Does that mean that imake is reponsible somehow for upgrading KDE3? What is the switch to force the upgrade? How did the upgrade of imake lead to the rebuild of kde-3? I asked myself this very same question several months ago. No answers came forth. BTW, any idea how I could reduce the size of the /usr/ports slice - it's max is about 2Gb and there is about 1.7 in use. It seems a bit bloated and I certainly don't need all the stuff that is in there... Delete everything in /usr/ports/distfiles. And before you go to bed one night do a make clean from /usr/ports. It takes some time... -- Regards Cliff [ 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
Re: portupgrade mess
Quoting Cliff Sarginson [EMAIL PROTECTED]: BTW, any idea how I could reduce the size of the /usr/ports slice - it's max is about 2Gb and there is about 1.7 in use. It seems a bit bloated and I certainly don't need all the stuff that is in there... Delete everything in /usr/ports/distfiles. And before you go to bed one night do a make clean from /usr/ports. It takes some time... Another option is to add the following to your make.conf ( 5.x: /etc/make.conf 4.x: /etc/defaults/make.conf ) WRKDIRPREFIX= /usr/obj This will cause all of your port builds to be directed to /usr/obj. You can then nuke /usr/obj/usr/ports and only remove the work, not the ports tree. To take care of the distfiles problem... # mkdir -o /usr/obj/usr/ports/distfiles # mv /usr/ports/distfiles/* /usr/obj/usr/ports/distfiles # --(optional) # rm -rf /usr/ports/distfiles # ln -s /usr/obj/usr/ports/distfiles /usr/ports/distfiles This will get your distfile downloads out of /usr/ports as well. However, there's probably a cleaner way to do this via a make.conf setting. I do all of this because my ports tree is NFS mounted read-only as needed. --daxbert To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: portupgrade mess
At 2003-03-14T03:06:33Z, Cliff Sarginson [EMAIL PROTECTED] writes: Delete everything in /usr/ports/distfiles. And before you go to bed one night do a make clean from /usr/ports. It takes some time... `portsclean -CD' does pretty much the same thing in about 1% as much time. -- Kirk Strauser In Googlis non est, ergo non est. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: portupgrade mess
On Thu, 2003-03-13 at 09:31, Mike Meyer wrote: 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 system, how did you do it? Did you then use portupgrade to upgrade all the ports you had installed? If not, that may be part of the problem. He's talking about XFree86 4.2 not BSD 4.2. Portupgrade is definitely the way to go. Also, XFree86 4.3 installs a new xinitrc which loads twm by default. If you want gnome-session or KDE you have to edit xinitrc to launch that session. Generally, when upgrading across a release, you want to deinstall the ports in large chunks - all of them is best - and then reinstall the ports from the new ports in the system. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Portupgrade -- revisited
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 everything that used them below that. Now, the kicker is that qt-3.x uses Xft.2 in the build but it was not rebuilt. I had to run -pufr fontconfig for that to happend. Please send this as a problem report to the portupgrade maintainer, Akinori MUSHA [EMAIL PROTECTED]. Qt31 has Xft.2 listed as a direct dependency so it should be rebuilt if that port is rebuilt, just as you said. --Stijn -- Remember, kids: Q is always followed by U. You can learn more on the Internet in the Spelling FAQU. -- James Kibo Parry pgp0.pgp Description: PGP signature
Re: Portupgrade -- revisited
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 Xft, which had also been upgraded, and just repackaged everything that used them below that. Now, the kicker is that qt-3.x uses Xft.2 in the build but it was not rebuilt. I had to run -pufr fontconfig for that to happend. Please send this as a problem report to the portupgrade maintainer, Akinori MUSHA [EMAIL PROTECTED]. I will try that tomorrow. It is too late to try it to night. I have never used send-pr before. Qt31 has Xft.2 listed as a direct dependency so it should be rebuilt if that port is rebuilt, just as you said.portupgrade-20030228 It wasn't the only one. The complete list looks like # pkgreq Xft Information for Xft-2.1_2: Required by: XFree86-4.2.0_1,1 XFree86-clients-4.2.1_3 arts-1.1,1 kdbg-1.2.5 kde-3.1 kdeartwork-3.1 kdebase-3.1_1 kdegames-3.1 kdegraphics-3.1 kdelibs-3.1 kdemultimedia-3.1 kdenetwork-3.1 kdepim-3.1 kdetoys-3.1_1 kdeutils-3.1 kdevelop-2.1.5 koffice-1.2.1,1 qt-3.1.1_4 None of them were rebuilt with out specifying -f on the portupgrade command. The version used was portupgrade-20030228. It was on a recent cvsup of ports-all and new INDEXs. Portupgrade was upgraded before trying to build fontconfig. The port's in the list all have Xft-2 as a b/r-dep. The command I used was portupgrade -pur fontconfig What it typically did was build anything showing up as modified (fontconfig and Xft-2) and then just repackage the rest like the following. --- Packaging 'XFree86-clients-4.2.1_3' as dependency Creating package /usr/ports/packages/All/XFree86-clients-4.2.1_3.tgz Creating gzip'd tar ball in '/usr/ports/packages/All/XFree86-clients-4.2.1_3.tgz' --- Packaging 'XFree86-4.2.0_1,1' as dependency Creating package /usr/ports/packages/All/XFree86-4.2.0_1,1.tgz Creating gzip'd tar ball in '/usr/ports/packages/All/XFree86-4.2.0_1,1.tgz' --- Packaging 'qt-3.1.1_4' as dependency . . etc 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: Portupgrade -- revisited
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 just built fontconfig. Next I tried -pur fontconfig. It rebuild Xft, which had also been upgraded, and just repackaged everything that used them below that. Now, the kicker is that qt-3.x uses Xft.2 in the build but it was not rebuilt. I had to run -pufr fontconfig for that to happend. Please send this as a problem report to the portupgrade maintainer, Akinori MUSHA [EMAIL PROTECTED]. I will try that tomorrow. It is too late to try it to night. I have never used send-pr before. If you can send mail, you can use send-pr. However, after careful reading this might not be a bug but intended behaviour. You see, the manpage says this on the -r switch (and paraphrases it for the -R switch): -r --recursiveAct on all those packages depending on the given packages as well. The problem is that 'act' is not defined very well -- if you think about it, you've asked portupgrade, by using -pur, to check if fontconfig is out of date and *if so* rebuilt it, and do *the same thing* for all packages dependent on fontconfig. Now, because qt hadn't changed, portupgrade didn't rebuilt it. It probably did consider it though. You can use -v with portupgrade to check this. If you use -f, it will *unconditionally* rebuild all dependent ports. Is this a problem? Yes and no. Most of the time (and I suspect it is so with qt) the dependant ports use the shared library. This means that they will have the new functionality of the Xft port right away. There are at least two cases where this breaks: - Xft was upgraded to use a new major version. The old library is saved by portupgrade in a compatibility path, so qt and all other dependant packages will still function correctly, but it might pay to rebuild them to use the new library. Most of the time this requires source patches to the dependant ports though, because a library version bump should indicate an API breakage. - Dependant ports used the *static* library. Now they need to be rebuild after every upgrade of Xft. There's no way to avoid this except to bug the authors of the port to consider using the shared library instead. So, in retrospect, portupgrade was only doing what you told it to do. I would suggest that next time you try and let portupgrade decide what to upgrade, and check if dependant ports still work as expected. I'd estimate that in 95% of the cases, they still work. Hope this helps to clear up some of the confusion. --Stijn -- An Orb is for life, not just for Christmas. pgp0.pgp Description: PGP signature
Re: Portupgrade -- revisited
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 for somewhere else to be. Years and years ago I wrote a caculator program for DOS, using a recursive state-machine model and allowing infinite precision, kind of like bc..or is it dc ? Quite necessary at the time to deal with the Dutch Tax System. 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 role. -- Regards Cliff [ 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
Re: Portupgrade -- revisited
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 my eyes crossed, went sidewyas, took a holiday, crawled across the floor looking for somewhere else to be. What part did you not understand? I'll try and reword it for you. Hopefully things can become clear then. Years and years ago I wrote a caculator program for DOS, using a recursive state-machine model and allowing infinite precision, kind of like bc..or is it dc ? Quite necessary at the time to deal with the Dutch Tax System. What does that have to do with portupgrade? If you're trying to convey the height of your programming skills, you've succeeded -- I've never done the above, and probably never will. My interests lie elsewhere. To each his own. I am not making fun of you either -- portupgrades *can* go wrong in many subtle ways. However I enjoy finding out what exactly went wrong, and try to fix things in the process. Even better if I can find where portupgrade got things wrong, so that I can report them to the author. Note that I'm still a convinced portupgrade user. Kent's story led me to find out why portupgrade did what it did, and it cautioned me to again look more closely at what exactly happened after my portupgrade runs. And like I said, I succesfully used portupgrade to survive X, mozilla and gnumeric upgrades. That's why I'm still convinced that there's something on your system that prevents you from portupgrading KDE. However you don't seem interested in fixing this anymore; not my loss. 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. That would be great. More alternatives is always better. Maybe you will also encounter a lot of the difficulties of automatic dependencies and the like. Maybe you can even make it part of the base system, or at least of the ports system. Regards, --Stijn -- Remember, kids: Q is always followed by U. You can learn more on the Internet in the Spelling FAQU. -- James Kibo Parry pgp0.pgp Description: PGP signature
Re: Portupgrade -- revisited
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 role. So what are you going to write it in? C? BTW, did you know your email to freebsd-questions has an invalid From: field in it? I keep getting bounces with host not found for [EMAIL PROTECTED]. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Portupgrade -- revisited
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 the latest KDE ports installed). We obviously test the ports on a wide variety of systems, but we can't catch everything. For example, there were recent changes on -CURRENT that completely broke in kdebase, and we've been asking for people affected to test a patch that very likely fixes it. As a further example, a recent upgrade to libxine changed it's API so much that kdemultimedia stopped building. Of course, updating the ports again with cvsup would fix that one, since we fixed it rather quickly, and posting the build error to kde@, we would have immediately recognised the problem as the one we just fixed, and advised you accordingly. I guess I don't see your posts to [EMAIL PROTECTED] (clearly listed as the maintainer for all KDE ports) with your build/runtime problems, symptoms, and logs that would help us diagnose the problem. They must have slipped under one of my filters. Perhaps, since I can obviously see your posts here, you could repost them and I can forward them to kde@ for you. Ok, mea culpa. I should use the right list when I have a problem. I will do so from now on. I do realise that KDE is one complex beast. I apologise. I still don't have KDE, but my next message about it will be to the right list. I do appreciate everyone's efforts... -- Regards Cliff [ 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
Re: Portupgrade -- revisited
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: snip 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 on my libxml2, which has refused to build for about six weeks now, but this is one of the things that has made me disenchanted with portupgrade. That, and things like 'portsdb -Uu'. You have to live with the -uU. INDEX isn't updated very often and if you don't cvsup right after it is, it won't have the current requirements. If you use portupgrade and the other tools, you have to update INDEX.db. If you refuse or don't cvsup ports-all, the make index probably won't work properly to begin with. Some days, portsdb -U won't work and you have to use make index. Regardless of which method you use, you always have to run portsdb -u after you have updated INDEX. Since I always recreate INDEX and INDEX.db, I have refused ports/INDEX. There isn't any point in downloading a new copy and then destroying it with the new version. I looked at your other email. Libxml2 has requirements and I think your are out of date. The latest portupgrade does wonderful things. I would start by upgrading it to portupgrade-20030228 first. It has fixed the requirement for the pkgdb -F being run unless they tell you to. If you want to see if it will work, run portupgrade -Ruf libxml2. That won't take very long. You have to build everything that uses it if it works and that is the -r option. If you do both at the same time, it will be hours until they finish. I don't know which is the best list. I start out with the maintainer but I really don't believe there is anything wrong with libxml2. I found a problem making libxslt package and marcus@ fixed it right away. Since then, it has been upgraded on my 4 main machines. Now that you mention it, libxslt is another problem I've been having. Haven't been able to upgrade it for a long time for reasons similar to libxml2. On Marcus' advice I took a look at my version of Python. Somehow I had version 1.6, while the port is 1.5.2_2! So I have run 'pkg_deinstall python 1.6' and am now running 'portupgrade -NR lang/python15' (it reported there was no package or port named python15). When that's done I'll try again with libxml2 and libxslt. And pango. But thank goodness for this mailing list. Otherwise I'd never find out about some of these gotchas. -- Roger To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Portupgrade -- revisited
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: snip snip On Marcus' advice I took a look at my version of Python. Somehow I had version 1.6, while the port is 1.5.2_2! So I have run 'pkg_deinstall python 1.6' and am now running 'portupgrade -NR lang/python15' (it reported there was no package or port named python15). When that's done I'll try again with libxml2 and libxslt. And pango. The port system is really simple and straight forward. If you change anything, then you have to be able to deal with it on your own. Change anything includes refusing ports, not rebuilding INDEX*, and etc. Some how you changed things by adding 1.6 and we all saw what happened. Now, we just have to remember it until the next person does it :). I am reasonably sure you will but many of the rest of us might not. But thank goodness for this mailing list. Otherwise I'd never find out about some of these gotchas. 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 everything that used them below that. Now, the kicker is that qt-3.x uses Xft.2 in the build but it was not rebuilt. I had to run -pufr fontconfig for that to happend. 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: Portupgrade -- revisited
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 sure they release compilable ports..especially for the big mothers like X/KDE. -- Regards Cliff What specifically is wrong with X? Does X not launch at all, or does X launch but KDE fails? If KDE is botched then you could always fall back on twm until you can get your wm of choice back up and running. Nathan -- GPG Public Key ID: 0x4250A04C gpg --keyserver pgp.mit.edu --recv-keys 4250A04C http://63.105.21.156/gpg_nkinkade_4250A04C.asc pgp0.pgp Description: PGP signature
Re: Portupgrade -- revisited
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 KDE, so haven't tried to build that. If you send the maintainer a note with the error messages when you tried to build the port, they might be able to fix it. A generic it didn't build on -questions almost certainly means that nothing will happen. mike -- Mike Meyer [EMAIL PROTECTED] http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Portupgrade -- revisited
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 release compilable | ports..especially for the big mothers like X/KDE. This was just much-discussed in STABLE. I've had a similar experience to yours, though many people gave ways to make it work. What *I* do is is just mass upgrade OR none-- I do the kernel/world thing for my base system, save my current ports with pkg_info -aI, pkg_delete '*', wipe out /usr/local, then go over the packages I saved and remove the version numbers, and do (on a copy of hte file where I saved them, delete any that i must build from ports (eg, local patches) 1,$s/^/pkg_add -r/ 1,$s/[0-9].*$// Check for sanity, and then script source the file . . . then check the script file and build from ports any that failed, take any special actions, and install my local mods (and build from ports those that I need to). YMMV; lots of people swear by portupgrade. But I've had better luck with it. -- Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Portupgrade -- revisited
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 test in your environment. The X ports built fine for me. I don't use KDE, so haven't tried to build that. If you send the maintainer a note with the error messages when you tried to build the port, they might be able to fix it. A generic it didn't build on -questions almost certainly means that nothing will happen. Ok Mike, I really do always respect your advice. I want as much as anyone else that things *work*. I do not mind geting my hand dirty, if it improves things. But I think, after reflecting on it, that the ports system is in a mess. I will see if I can be more positive about improving it. But I am dmned if I am going to learn Ruby :) -- Regards Cliff [ 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
Re: Portupgrade -- revisited
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 release compilable ports..especially for the big mothers like X/KDE. Cliff, it's worked fine for me. I installed all of KDE3 from ports. Got virtually no errors, but I did do it by uninstalling almost all of my installed ports. So yes portupgrade for something that large did not work. Try making packages out of what ports you have installed. Then uninstalling and reinstalling them shouldn't be too bad. And you've got to understand the complexity problems involved here. There are 8200 or so ports right now. Each has as many as 60 dependencies (like kde). This creates an incredible web that is very difficult to keep working. The ports maintainers do a great job of this in fact. What is nearly impossible is to have it work perfectly for every given individual installation that may have many thousands of individual configuration changes, versions, old binary, source cruft lying around. So as mentioned before, problems could easily be due to stuff only you have on your system. Try building in a clean environment. If you get the same error in a clean environment then a clear message to the port maintainer with how to repeat the problem is the only way for them to get it working. It doesn't involve knowing how to code in the given language, just useful error messages. An it doesn't work is useless and does fall into the complainer side, even if you're not trying to. Try that and then ask questions if you can't get something working. Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: Portupgrade -- revisited
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 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 KDE, so haven't tried to build that. If you send the maintainer a note with the error messages when you tried to build the port, they might be able to fix it. A generic it didn't build on -questions almost certainly means that nothing will happen. Ok Mike, I really do always respect your advice. I want as much as anyone else that things *work*. I do not mind geting my hand dirty, if it improves things. But I think, after reflecting on it, that the ports system is in a mess. I will see if I can be more positive about improving it. But I am dmned if I am going to learn Ruby :) I just finished building kde and X. In the last 2 weeks I have portupgrade -puf portupgrade portupgrade -pufr png portupgrade -pufr fontconfig portupgrade -pufr libxml2 portupgrade -pufr ghostscript-gnu I have also done a portupgrade -pufR XFree86 on a box with problems. It wasn't X with the problem it turns out. I just wanted a clean X. There was a minor problem with ghostscript-gnu's font directory during the deinstall phase. I removed and did a make package to reinstall it. What portupgrade options are you using? When you do -r, you have to force -f. 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: Portupgrade -- revisited
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 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 KDE, so haven't tried to | build that. If you send the maintainer a note with the error | messages when you tried to build the port, they might be able to | fix it. A generic it didn't build on -questions almost certainly | means that nothing will happen. | | Ok Mike, I really do always respect your advice. | I want as much as anyone else that things *work*. | I do not mind geting my hand dirty, if it improves things. | But I think, after reflecting on it, that the ports system is in a | mess. I will see if I can be more positive about improving it. | But I am dmned if I am going to learn Ruby :) I would disgree that the ports system in general is a mess; indeed, I think it's about the best single thing about FreeBSD. It *is* true that upgrading is a problem but I dont' believe that this is the fault of the ports system; indeed, the real problem is that versioning on shared libraries is inadequate. And there is only so much that the ports system can do about it. As long as that problem remains, then ANY attempt to do partial upgrades can only aspire to succeed most of the time; it can never be reliable no matter HOW smart the ports system or portupgrade becomes. -- Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
