Kenneth,

As you only had octave itself update, it seems likely that you don’t have any 
octave packages installed. As Ryan said, is the directory placeholder where 
packages are normally installed. However, that directory is empty until you 
install an octave package,

Marius
--
Marius Schamschula




> On Mar 30, 2025, at 1:42 PM, Kenneth Wolcott <[email protected]> wrote:
> 
> Hi Ryan;
> 
>   Since it wasn't a fatal error, the octave port work area was automatically 
> cleaned, so I only have the details that I provided in the initial email.
> 
>   I did a self update.
> 
>   I did a port outdated.
> 
>   The octave port was the only port that needed updating.
> 
>   I then did a port upgrade outdated.
> 
> That's it.
> 
> Hope that helps.
> 
> Ken Wolcott
> 
> On Sun, Mar 30, 2025 at 8:43 AM Ryan Carsten Schmidt <[email protected] 
> <mailto:[email protected]>> wrote:
>> On Mar 29, 2025, at 21:03, Kenneth Wolcott wrote:
>>> 
>>> What is a 'turd_octave'? this occurred during the most recent update to the 
>>> octave package...
>>> 
>>> recreating package description from .turd_octave
>>> warning: directory .turd_octave is not a valid package
>>> warning: called from
>>>     rebuild at line 71 column 7
>>>     pkg at line 707 column 9
>> 
>> When a Portfile uses the directive destroot.keepdirs to tell MacPorts to 
>> keep a directory as part of the port's contents even though it is empty, 
>> this is accomplished by MacPorts creating an invisible "turd" file in the 
>> directory so that it is not empty. The octave Portfile does this here:
>> 
>> https://github.com/macports/macports-ports/blob/595780010dd23eef0efe9602355c0de096008425/math/octave/Portfile#L728
>> 
>> In your warning message it is being referred to as a directory rather than a 
>> file. I assume that is simply a mistake in the warning message.
>> 
>> Something about octave is unexpectedly trying to process the turd file as if 
>> it were an octave package. Since it isn't one it complains. 
>> 
>> You could file a bug report. Be sure to mention what commands you ran that 
>> resulted in these messages. 



Marius
--
Marius Schamschula




Reply via email to