Date: Sun, 3 Mar 2002 10:56:15 +0000 From: Kevin Golding <kevin@caomhin.demon.co.uk> To: S Roberts <sroberts84@hotmail.com> Cc: freebsd-questions@FreeBSD.org, knu@freebsd.org Subject: Re: Portupgrade Problem? Message-ID: <MMDnQpBPFgg8Ewp0@caomhin.demon.co.uk> In-Reply-To: <F259lYLJPnLDRZIjoUK00004484@hotmail.com> References: <F259lYLJPnLDRZIjoUK00004484@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <F259lYLJPnLDRZIjoUK00004484@hotmail.com>, S Roberts <sroberts84@hotmail.com> writes >Hello, > I did the following tonight: > >1] Cvsup's ports manually >2] Ran pkg_verison -v (to see if any installed ports are out of date) >3] Noted those ports listed that needed upgrading >4] Attempted to use portupgrade [-R] to upgrade said ports > >The port concerned is: >ruby-1.6.6.2002.01.29 < needs updating (port has 1.6.7) > >I ran portupgrade (more than once) and got this: >portupgrade -R ruby-1.6.6.2002.01.29 >Stale dependency: ruby-1.6.6.2002.01.29 <-- ruby-uri-0.9,1 -- manually >run 'pkgdb -F' to fix, or specify -O to force. This is somewhat covered by: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/34388 Although that is talking about portupgrade instead of Ruby. I think your next concern should help fix it though. >I note that there is another ruby port listed as "up to date": >ruby-1.6.7 = up-to-date with port > >Do I have some sort of conflict here? # pkgdb -F it should show any concerns and advise you on methods to resolve them, but sort out portupgrade like below first. Once this is run you should only have one copy of Ruby installed and no dependency worries >Also, since I installed portupgrade some time ago, I have never been able to >upgrade it using portupgrade either. Do I have some underlying problem >that's going to bite me later on? See latest attempt tonight; > >portupgrade -R portupgrade >cd: can't cd to /usr/ports/misc/pkg_tarup >** The port directory for 'misc/pkg_tarup' does not exist. >---> Skipping 'sysutils/portupgrade' (portupgrade-20020220.1_2) because >'misc/pkg_tarup' (pkg_tarup-1.2_3) failed >** The following packages were not installed or upgraded (*:skipped / >!:failed) > ! misc/pkg_tarup (pkg_tarup-1.2_3) (port directory error) > * sysutils/portupgrade (portupgrade-20020220.1_2) > >Please help with the above "problems?" or, kindly let me know if I've missed >some step along the way somewhere. If you require some more information on >the system, do let me know. The problem is that pkg_tarup is now in sysutils rather than misc, try running 'pkg_deinstall -f pkg_tarup' then go to /usr/ports/sysutils/pkg_tarup and install it from there. It's confusing because when I get errors the first thing I do is check with the web interface to see how it corresponds to my ports collection, and pkg_tarup is still listed in misc on there and returning errors. I only send a mail to the folk this morning so hopefully when they get round to it the information will make more sense. Looking at portupgrade gives mixed results, portversion says it's out of date, pkg_version -v says it's up to date. I appear to have a working version of portupgrade installed right now so I'm not going to play too much. Maybe I tried a few too many things to get it upgraded in the first place but /var/db/pkg says it's version portupgrade-20020227 As a trial I ran make in sysutils/portupgrade and it failed as follows: /usr/local/bin/ruby -wc tsort.rb Syntax OK /usr/local/bin/ruby -p -e 'sub %r:/usr/local:, "/usr/local"' tsort.rb > .build /tsort.rb ===> misc ===> misc/bash Warning: Object directory not changed from original /usr/ports/sysutils/portupgr ade/work/pkgtools-20020204/misc/bash ===> misc/tcsh Warning: Object directory not changed from original /usr/ports/sysutils/portupgr ade/work/pkgtools-20020204/misc/tcsh ===> misc/zsh Warning: Object directory not changed from original /usr/ports/sysutils/portupgr ade/work/pkgtools-20020204/misc/zsh Maybe that's of some use to someone. Kevin -- kevin@caomhin.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MMDnQpBPFgg8Ewp0>