On 2020-11-17 20:23, Ryan Schmidt wrote:
On Nov 17, 2020, at 20:04, Jim DeLaHunt wrote:
Hi, folks:
In doing my daily `sudo port selfupdate` on 16 November UTC, I encountered a
warning which is new to me:
"Warning: No port […portname…] found in index"
In redoing `sudo port selfupdate`,
On Nov 17, 2020, at 20:04, Jim DeLaHunt wrote:
> Hi, folks:
>
> In doing my daily `sudo port selfupdate` on 16 November UTC, I encountered a
> warning which is new to me:
>
> "Warning: No port […portname…] found in index"
>
> In redoing `sudo port selfupdate`, this warning did not reoccur.
> On 2020-11-17, at 21:04, Jim DeLaHunt wrote:
>
> Hi, folks:
>
> In doing my daily `sudo port selfupdate` on 16 November UTC, I encountered a
> warning which is new to me:
>
> "Warning: No port […portname…] found in index"
Seems like a race condition where your index was blank at the time
Hi, folks:
In doing my daily `sudo port selfupdate` on 16 November UTC, I
encountered a warning which is new to me:
"Warning: No port […portname…] found in index"
In redoing `sudo port selfupdate`, this warning did not reoccur.
What is the significance of this warning? What, if anything,
On Nov 14, 2020, at 06:05, Joshua Root wrote:
> The MacPorts Project is pleased to announce the release of version
> 2.6.4. This is a bugfix release with small changes only. See the
> ChangeLog [1] for the list of changes.
Thank you, Josh, for doing this release. I know it takes time to
> MacPorts compiler to break is a pain on systems which have an older
> toolchain. Probably this goes unnoticed on newer macs where the system
> clang/gcc is "new enough".
> Here were are in the situation that if, for some upstream reason,
> libxml2 stops compiling with gcc 4.2, the user has no
