Bug in port name handling
Sbranzo
sbranzo at gmail.com
Wed Jan 3 11:20:14 PST 2007
I thinks there's a bug in the way port names are handled.
I'm trying to compile a cvs snapshot of slrn, the same present in debian
experimental. The debian maintainer assigned 0.9.8.1pl2~cvs20061116 as
version number, and I wish to keep this convention.
If I manually change some links before the ./configure phase (refer to
my previous email) I can build and install my port using macports, but
it blocks here:
$ sudo port -vc install slrn-dev +ssl +pull
[...]
./opt/local/share/slrn/macros/xcomment.sl
---> Archive slrn-dev-0.9.8.1pl2~cvs20061116_0+pull+ssl.powerpc.tgz
packaged
---> Archive for slrn-dev 0.9.8.1pl2~cvs20061116_0+pull+ssl packaged
---> Installing slrn-dev 0.9.8.1pl2~cvs20061116_0+pull+ssl
---> Activating slrn-dev 0.9.8.1pl2~cvs20061116_0+pull+ssl
Error: Target com.apple.activate returned: Registry error: slrn-dev
cvs20061116_0+pull+ssl not registered as installed.
Warning: the following items did not execute (for slrn-dev):
com.apple.activate
Error: Status 1 encountered during processing.
If you notice the version should be 0.9.8.1pl2~cvs20061116_0+pull+ssl
but com.apple.activate sees only cvs20061116_0+pull+ssl.
Now I officially have a screwed installations of macports :-D
$ port installed
Error: port installed failed: Registry error: slrn-dev
cvs20061116_0+pull+ssl not registered as installed.
No ports are installed.
How can I repair it?
Thanks,
Gufo
More information about the macports-users
mailing list