On Thursday November 13 2014 21:33:00 Clemens Lang wrote:
Hi,
> That's exactly what I would have expected, because this archive has just been
> created from your ${prefix}.
Yeah, I figured that :)
>
> Yes. If you had had this file, images_to_archives.tcl wouldn't have attempted
> to create it. You must have had gsed installed, though, because
> images_to_archives.tcl uses the metadata MacPorts keeps about its installed
> ports in the registry database in $prefix/var/macports/registry/registry.db.
I see I didn't write down my full thought :-/ What I meant to say was that I
suspected that the gsed I had installed was part of another port, recently
split up. It'd be a feat to handle that kind of thing automatically (I guess
:)).
Question is, if I did install gsed at some point (which would be very likely),
how come I can't find a trace of its Portfile?
Unless...
I keep getting that error that I've already signalled but that I cannot
reproduce nor predict nor even "debug" because it "self heals": some kind of
transient failure uninstalling a port with alerts about missing files from
MacPort's infrastructure. Usually the port does get uninstalled though, without
collateral damage as far as I can tell. I wonder if this is related and if so,
what on earth is going on.
AFAIT I can rule out issues with my harddrive...
R.
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users
