Ports not listed as outdated
Mojca Miklavec
mojca at macports.org
Wed Apr 22 04:40:59 PDT 2015
On Wed, Apr 22, 2015 at 12:14 PM, Mihai Moldovan wrote:
> On 22.04.2015 12:00 PM, Mojca Miklavec wrote:
>> Thanks again and sorry for the noise,
>
> No, not noise. Let me explain why.
>
>
>> Hm. Interesting.
>>
>> Thank you, it seems that running portindex solved the problem indeed.
>> I now got a long list of outdated ports.
>
> That's interesting indeed.
>
>> I didn't know that portindex had to be run on regular basis. I knew
>> one had to run it when adding a new port or subport, but usually
>> everything worked out of the box once the port was in the portindex.
>> But maybe I'm just biased. Usually I'm the one changing the ports in
>> my local repository and running "sudo port upgrade foo" just works. (I
>> never use "sudo port upgrade outdated" to try to install the latest
>> version of the port I modify myself, so I probably just never noticed
>> the problem so far.)
>
> portindex must be executed every time you change a port to update the version numbers therein.
> The reason is that the outdated set is calculated by looking at PortIndex.
>
> Now, if that problem wasn't caused by YOU directly editing the Portfiles, there's something else going on.
>
> The portindex is generated on the rsync machine, which is running Linux. If doing funky stuff that happens to abort Portfile parsing ungracefully (like not wrapping sysctl stuff in "catch"), the index will be stale for these ports.
Maybe I need to explain a bit more.
I have a sparse SVN checkout configured as:
file:///Users/me/app/macports/trunk/dports [nosync]
I used [nosync] because I'm often bitten by failures during svn
updates when my local changes conflict with upstream changes in the
repository and I prefer to solve those manually, not during "port
selfupdate".
I ran "svn up" in "~/app/macports/trunk", but I didn't run portindex.
The texlive-bin port was one of those ports in my sparse checkout
(maybe I initially even forgot to run "svn up"). From my understanding
that fully explains the situation. Apparently I run portindex often
enough that I have never been bitten by this particular type of the
problem in years.
Mojca
More information about the macports-dev
mailing list