Thank you for the explanation. Indeed, my problem was that the Portindex was
out of date and not being updated, because the Portfiles had time stamps older
than the Portindex itself.
Cheers
Artur
________________________________________
From: Clemens Lang [c...@macports.org]
Sent: 09 November 2016 22:34
To: Artur Szostak
Cc: macports-...@lists.macosforge.org
Subject: Re: Issues with upgrading with private repositories
Hi,
On Wed, Nov 09, 2016 at 10:17:36AM +0000, Artur Szostak wrote:
> During my testing when developing Portfiles I have a few different
> private repositories configured under
> /opt/local/etc/macports/sources.conf. I have gotten into a situation
> where after a "sudo port sync" I am seeing a version number that is
> not expected for my package when listing it with "sudo port list
> mypackage".
That version number comes from the portindex. Check the PortIndex files
for your local repositories. Also, check the order of those sources in
sources.conf to make sure the newer version you'd expect is first.
> When I look at all the cached Portfiles found under
> /opt/local/var/macports/sources/, I cannot find any existing Portfile
> with the version number seen in the "sudo port list mypackage"
> listing.
That suggests that your PortIndex might somehow be outdated. Usually the
'portindex' command uses file modification times to figure out which
ports to re-index, so touching the Portfile in question and running
portindex might fix this.
> Is there a way to clean any such caches if they exist? ("sudo port
> clean --all installed" did not help)
You can also just delete PortIndex and PortIndex.quick entirely, but it
might take a while to re-generate if you have a lot of ports.
--
Clemens
