rpa weird message

[Guillaume Marcais]

[gus@gusmac rpa-base-0.2.3]$ rpa -v info xmlresume2x
rpa (rpa-base 0.2.3-1) RPA 0.0
Matching installed ports:
xmlresume2x 0.1.0-3 Converts an XML resume to various output formats.

[gus@gusmac rpa-base-0.2.3]$ rpa -v check xmlresume2x
rpa (rpa-base 0.2.3-1) RPA 0.0
Port xmlresume2x is not installed.
All requested installed ports are in the same state as when unpacked.

[gus@gusmac rpa-base-0.2.3]$ uname -a
Darwin gusmac.local 7.6.0 Darwin Kernel Version 7.6.0: Sun Oct 10
12:05:27 PDT 2004; root:xnu/xnu-517.9.4.obj~1/RELEASE_PPC Power
Macintosh powerpc

Why does 'info' tells me it is installed and 'check' it is not? (And I
did install the port).

Guillaume.

 

[Mauricio Fernández]

[gus@gusmac rpa-base-0.2.3]$ rpa -v info xmlresume2x
rpa (rpa-base 0.2.3-1) RPA 0.0
Matching installed ports:
xmlresume2x 0.1.0-3 Converts an XML resume to various output formats.

[gus@gusmac rpa-base-0.2.3]$ rpa -v check xmlresume2x
rpa (rpa-base 0.2.3-1) RPA 0.0
Port xmlresume2x is not installed.
All requested installed ports are in the same state as when unpacked.

This is believed to be fixed in rpa-base 0.2.3-3.
Please run
rpa update
(will perform a self-update) and try to reproduce.

FYI, this could happen if you ran rpa check with a different user
than the one who installed rpa-base, because rpa check tried to get an
exclusive lock on the package registry. The corresponding exception was
rescued unconditionally and the 'xxx not installed' message displayed,
even though that was not correct.

Does that correspond to your case?

 

[Guillaume Marcais]

Le 25 nov. 04, à 05:59, Mauricio Fernández a écrit :

[gus@gusmac rpa-base-0.2.3]$ rpa -v info xmlresume2x
rpa (rpa-base 0.2.3-1) RPA 0.0
Matching installed ports:
xmlresume2x 0.1.0-3 Converts an XML resume to various output
formats.

[gus@gusmac rpa-base-0.2.3]$ rpa -v check xmlresume2x
rpa (rpa-base 0.2.3-1) RPA 0.0
Port xmlresume2x is not installed.
All requested installed ports are in the same state as when unpacked.

This is believed to be fixed in rpa-base 0.2.3-3.
Please run
rpa update
(will perform a self-update) and try to reproduce.

FYI, this could happen if you ran rpa check with a different user
than the one who installed rpa-base, because rpa check tried to get
an
exclusive lock on the package registry. The corresponding exception was
rescued unconditionally and the 'xxx not installed' message displayed,
even though that was not correct.

Does that correspond to your case?

It definitely does! Thanks for the explanation.
Guillaume.