portupgrade troubles
Hello
I post the questions several months a go but I find until now no solutions. If
I use portupgrade -fa I get the folowing error:
/usr/local/lib/ruby/site_ruby/1.8/pkgversion.rb:41:in `initialize': ,2: Not in
due form: '[_][,]'. (ArgumentError)
from /usr/local/sbin/portupgrade:638:in `new'
from /usr/local/sbin/portupgrade:638:in `main'
from /usr/local/sbin/portupgrade:613:in `each'
from /usr/local/sbin/portupgrade:613:in `main'
from /usr/local/sbin/portupgrade:588:in `catch'
from /usr/local/sbin/portupgrade:588:in `main'
from /usr/local/lib/ruby/1.8/optparse.rb:1303:in `call'
from /usr/local/lib/ruby/1.8/optparse.rb:1303:in `parse_in_order'
... 7 levels...
from /usr/local/lib/ruby/1.8/optparse.rb:785:in `initialize'
from /usr/local/sbin/portupgrade:229:in `new'
from /usr/local/sbin/portupgrade:229:in `main'
from /usr/local/sbin/portupgrade:2173
But get no answer and find no solution for my problem. Any ideas
Regards,
In the past I did a lot:
- /usr/ports/UPDATING: checked all the ruby hints
- Find and read the following posts:
[snip]
Re: portupgrade error - `deorigin': cannot convert nil into String
(PkgDB::DBError)
From: Kent Stewart (kstewart_at_owt.com)
Date: 06/25/04
To: [EMAIL PROTECTED]
Date: Fri, 25 Jun 2004 13:10:44 -0700
On Friday 25 June 2004 12:25 pm, Andy Smith wrote:
> Ever since a recent cvsup of ports and a portsdb -Uu, portupgrade
> has been giving the following error:
>
> ---> Session started at: Fri, 25 Jun 2004 18:58:25 +
> ---> Session ended at: Fri, 25 Jun 2004 18:58:28 + (consumed
> 00:00:03) /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in
> `deorigin': cannot convert nil into String (PkgDB::DBError) from
> /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from
> /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from
> /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from
> /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from
> /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from
> /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from
> /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933: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:1845
>
> I have tried:
>
> - Waiting a day and doing another cvsup
>
> - Doing make index / portsdb -Uu
>
> - Removing ruby and portupgrade and reinstalling
>
> but I still get the same error.
>
> I also searched the mailing list archives and found someone with a
> very similar error:
>
> http://lists.freebsd.org/pipermail/freebsd-stable/2003-May/001255.htm
>l
>
> however, I've already learnt my lesson about refusing ports, and so
> my sup/refuse contains only:
>
> ports/INDEX
> ports/INDEX-5
>
> Anyone have any other ideas?
Someone on ports said to run portsdb -fu to fix this one. The cooment
was
> Probably a ruby bug. Rebuilding {pkg|ports}.db from scratch will do,
I
think.
But I thought that was a pkgdb -fu.
Kent
--
Kent Stewart
Richland, WA
http://users.owt.com/kstewart/index.html
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
__
[snip]
Newsgroups: mailing.freebsd.ports
Von: [EMAIL PROTECTED] (Sergey Matveychuk)
Datum: Sun, 27 Jan 2008 04:20:30 +0800 (CST)
Lokal: Sa 26 Jan. 2008 22:20
Betreff: ports-mgmt/portupgrade-devel
Antwort an Autor | Weiterleiten | Drucken | Einzelne Nachricht |
Hi!
After a long time, I've got a little free time and spent it working for
portupgrade.
A new version (2.4.0) was released.
* Many bugs fixed (thanks to reporters).
* At last I've finished rewriting code and portupgrade now controls all
tasks (before some port installed without a portupgrade note). As a
result portupgrade gathers all depends for a port. It spends a time for
preparing in the beginning of a upgrade process.
* I've change unused -c and -C options to allow run 'make
config-conditional' and 'make config' (force options change) before all
processing.
Test the release please. To move from portupgrade to portupgrade-devel
port, use the command:
portupgrade -fo ports-mgmt/portupgrade-devel portupgrade
If you'll want to back to stable porupgrade, use the command:
portupgrade -o ports-mgmt/portupgrade portupgrade-devel
--
Dixi.
Sem.
___
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: 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 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)
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 attribute, which... um... quotes blocks of text. When f=f mailers that also can handle HTML encounter text, it’s usually marked up with the same excerpt bars we’re familiar with from f=f. Format=flowed isn’t actually at work there, but since 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 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]"
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: 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
Portupgrade troubles, interactive ports
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. I am currently running 5.2 release. I am sorry if this has been answered before but I didn't see mention of it in the archives or in other reference sources. Thanks, Simon ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
