Date: Sat, 18 Mar 2006 17:50:04 -0400 From: Duane Whitty <duane@greenmeadow.ca> To: Jez Hancock <jez.hancock@gmail.com> Cc: freebsd-questions@freebsd.org, "Donald J. O'Neill" <duncan.fbsd@gmail.com> Subject: Re: Portupgrade fails to upgrade after using portsnap Message-ID: <441C808C.60808@greenmeadow.ca> In-Reply-To: <200603181220.59384.duncan.fbsd@gmail.com> References: <7b3c7f0b0603180606g54ffe6e6k3152b6f00555cab0@mail.gmail.com> <200603181129.59168.donaldjoneill@gmail.com> <7b3c7f0b0603181006n26e33e60uc198e6c86f777f2e@mail.gmail.com> <200603181220.59384.duncan.fbsd@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Donald J. O'Neill wrote: > On Saturday 18 March 2006 12:06, Jez Hancock wrote: > >> Hi Donald, >> >> Thanks for the replies. >> >> On 3/18/06, Donald J. O'Neill <donaldjoneill@gmail.com> wrote: >> >>> On Saturday 18 March 2006 08:06, Jez Hancock wrote: >>> >>>> Hi all, >>>> >>>> For a long time I've been using cvsup and portupgrade to update >>>> the ports tree once a week; this has worked well for years now. >>>> Recently though I changed to using portsnap to update the ports >>>> tree, still using portupgrade once a week to update the ports. I >>>> followed the method outlined in the handbook more or less for >>>> upgrading using portsnap, essentially running a cronjob: >>>> >>>> portsnap cron && portsnap update && portupgrade -arRF && >>>> pkg_version -v -I -l "<" >>>> >>>> to grab and extract the latest port snapshot, fetch any newer >>>> port distfiles/tarballs and then report by mail what ports are >>>> out of date. >>>> >>>> This worked well for a few weeks up until Feb 25th - since then >>>> not a single out of date port has been reported and 'portupgrade >>>> -arR' fails to upgrade anything. I thought this might have been >>>> to do with the recent ports freeze, though checking now I see >>>> that only went on from the start of March... >>>> >>>> I've changed back to use cvsup and the old method - basically >>>> 'cvsup -g -L2 supfile && cd /usr/ports && make fetchindex && >>>> portsdb -u' - but still no joy. I was convinced it was the ports >>>> db files that were out of synch and thought this might do the >>>> trick to fix the problem, but unfortunately no - if I view the >>>> resulting INDEX file from this procedure I can see there are >>>> ports out of date as well, it's just 'portupgrade -arR' etc >>>> refuses to find any updates. >>>> >>>> Questions then: >>>> >>>> What could the problem be? >>>> For future reference what is the best way to purge the ports >>>> system of out of date db files and regenerate them all so >>>> 'portupgrade -arRi' will work? >>>> >>>> Cheers. >>>> -- >>>> Jez Hancock >>>> _______________________________________________ >>>> >>> Jez, >>> >>> I think my first response was a little unkind and I apologize for >>> that. >>> >>> The way I see it, your cronjob succeeded in doing what you set it >>> to do. It just didn't do what you wanted. >>> >>> First, portsnap requires fetch to get the files it needs, 'portsnap >>> upgrade' doesn't do that. You need to run 'portsnap fetch upgrade' >>> or 'portsnap fetch' && ' portsnap upgrade'. Had you done that, it >>> probably would have worked and you would have gotten something from >>> the portupgrade portion of your cronjob. As it was, there was >>> nothing new for portupgrade to work with and report. >>> >> Ok, I think you posted that before I clarified things in my last post >> :) >> >> By the by anyway... the issue I have is that when I run pkg_version >> or portversion I'm told there are a dozen or so ports need upgrading. >> However when I run portupgrade, portupgrade finds no ports to >> upgrade. Very frustrating. >> >> The general gist is in the following typescript/commandline output: >> >> [14:43:05] root@users /usr/ports# portversion -vl "<" >> bash-3.1.10 < needs updating (port has 3.1.10_1) >> mtr-nox11-0.69_2 < needs updating (port has 0.69_3) >> mutt-devel-1.5.11_1 < needs updating (port has 1.5.11_2) >> mysql-server-4.0.26_1 < needs updating (port has 4.0.26_2) >> netpbm-10.26.25 < needs updating (port has 10.26.26) >> nmap-4.01 < needs updating (port has 4.01_1) >> p5-Archive-Tar-1.28 < needs updating (port has 1.29) >> p5-Mail-Tools-1.73 < needs updating (port has 1.74) >> p5-XML-RSS-1.05_1 < needs updating (port has 1.10) >> tiff-3.8.0_1 < needs updating (port has 3.8.1) >> vim-6.4.6 < needs updating (port has 6.4.6_1) >> w3m-0.5.1_4 < needs updating (port has 0.5.1_5) >> >> [14:43:10] root@users /usr/ports# portupgrade -arRi >> ---> Session started at: Sat, 18 Mar 2006 14:43:16 +0000 >> -snip- >> ** No need to upgrade 'bash-3.1.10' (>= bash-3.1.10). (specify -f to >> force) -snip- >> ** No need to upgrade 'mtr-nox11-0.69_2' (>= mtr-nox11-0.69_2). >> (specify -f to force) >> -snip- >> ** No need to upgrade 'mutt-devel-1.5.11_1' (>= mutt-devel-1.5.11_1). >> (specify -f to force) >> >> etc etc >> >> This is all the result after running 'cd /usr/ports && make >> fetchindex' to get the latest ports INDEX db then running 'portsdb >> -u' to update /var/db/pkg/pkgdb.db. >> >> Any ideas why portversion says various ports are out of date but >> portupgrade doesn't want to update them? Is there any db that >> portupgrade would use to determine out of date ports other than >> /var/db/pkg/pkgdb.db? >> >> Thanks again. >> >> -- >> Jez Hancock >> - System Administrator / PHP Developer >> >> http://munk.nu/ >> http://freebsd.munk.nu/ - A FreeBSD Diary >> http://ipfwstats.sf.net/ - ipfw peruser traffic logging >> _______________________________________________ >> > Jez, > > I have no clue. If portversion is saying there is a port in need of > upgrade, 'portupgrade -arRi' should find it. That's a portupgrade > problem, not a portsnap problem. I would suggest trying portmanager and > see if that works. Both portmanager and portupgrade work for me. There > are times where I prefer to use one over the other. > > What happens if instead of using 'portupgrade -arRi', you used, say: > 'portupgrade -vrR bash', have you tried something like that to see if > it would upgrade? > > Don > _______________________________________________ > > Hi, I seem to remember needing to run portsnap fetch extract update the first time I ran portsnap. Afterwards portsnap fetch update worked as I expected. Perhaps you have already tried this? If so, my apologies for the useless noise. HTH, Duane --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?441C808C.60808>