no matching port found for: name=p5.12-sgmlspm, version=1.3.{}, revision=0, variants=, epoch=0

[ballapete (Peter "Pete" Dyballa)]

This is the error:

/opt/local/libexec/macports/bin/tclsh8.5 ./src/upgrade_sources_conf_default.tcl "/opt/local"
/opt/local/libexec/macports/bin/tclsh8.5 ./src/images_to_archives.tcl
This could take a while...
no matching port found for: name=p5.12-sgmlspm, version=1.3.{}, revision=0, variants=, epoch=0
    while executing
"registry::entry open $name $version $revision $variants $epoch"
    (procedure "receipt_sqlite::open_entry" line 2)
    invoked from within
"${macports::registry.format}::open_entry $name $version $revision $variants $epoch"
    (procedure "registry::open_entry" line 4)
    invoked from within
"registry::open_entry $iname $iversion $irevision $ivariants $iepoch"
    ("foreach" body line 8)
    invoked from within
"foreach installed $ilist {
    incr counter
    set iname [lindex $installed 0]
    set iversion [lindex $installed 1]
    set irevision [lindex $inst..."
    (file "./src/images_to_archives.tcl" line 38)
make: *** [install] Error 1
Command failed: cd /opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base && CC=/usr/bin/cc OBJC=/usr/bin/cc ./configure --prefix=/opt/local --with-tclpackage=/Library/Tcl --with-install-user=root --with-install-group=admin --with-directory-mode=0755 --enable-readline && make SELFUPDATING=1 && make install SELFUPDATING=1
Exit code: 2
DEBUG: Error installing new MacPorts base: command execution failed
    while executing
"macports::selfupdate [array get global_options] base_updated"
Error: Error installing new MacPorts base: command execution failed

Presumingly this refers to installed ports

  p5.12-sgmlspm @1.3.{}_0
  p5.12-sgmlspm @1.03ii.0_0 (active)

And presumingly I need now to remove this incorrectly named port "p5.12-sgmlspm @1.3.{}_0" somehow…

[ryandesign (Ryan Carsten Schmidt)]

See #43727. It was an error for the developers of SGMLSpm to have used the version number "1.03ii" because perl module version numbers are required to be floating point numbers. However, that was done 19 years ago. Perhaps that requirement was not in effect at the time, and in any case, the software appears to have been abandoned, or else they would have released a new version by now.

Perhaps we should assign a different (floating point) version number to this port to avoid this problem.

Still, it would be nice if MacPorts would not explode, even if a perl module uses an incorrect version number.

Have you tried the obvious, that is to say:

sudo port uninstall p5.12-sgmlspm '@1.3.{}_0'

[neverpanic (Clemens Lang)]

The sqlite database that contains this version number treats consecutive non-alphanumerics as separator only when comparing version numbers. Try sudo port uninstall p5.12-sgmlspm @1.3.0 if the former command doesn't work. Don't worry about the apparently missing underscore there, @1_3_0 should yield the same result.

[ballapete (Peter "Pete" Dyballa)]

Replying to ryandesign@…:

Have you tried the obvious, that is to say:

sudo port uninstall p5.12-sgmlspm '@1.3.{}_0'

When I tried it the first time, it did not work. I also tried the other variations. Then I decided to uninstall p5.12-sgmlspm @1.03ii.0_0, which also needed me to uninstall docbook-utils first. Then your command worked. Port could successfully selfudate.

I wonder what will happen when I decide to reinstall docbook-utils…

[ryandesign (Ryan Carsten Schmidt)]

Replying to Peter_Dyballa@…:

I wonder what will happen when I decide to reinstall docbook-utils…

Nothing out of the ordinary should occur, since this problem, which is specific to the p5-sgmlspm port because of the project's illegal version number, was worked around in r120107 but you presumably installed the port before that.

[cooljeanius (Eric Gallager)]

Cc Me!

[cooljeanius (Eric Gallager)]

Does docbook-utils really have to use the perl5.12 version of this module? I thought perl5.16 was the new default in MacPorts...

Edit: or use a bin:-style dependency, so any of the versions can fulfill it (they all install an executable with the same name and should really be marked as conflicting)

[dbevans (David B. Evans)]

Replying to egall@…:

Does docbook-utils really have to use the perl5.12 version of this module? I thought perl5.16 was the new default in MacPorts...

docbook-utils uses perl5.16 as of r122724 (maintainer update).

[dbevans (David B. Evans)]

As mentioned above version number issue dealt with in r120107.