#28084: Registry error for ports with underscore ('_') in version ---------------------------------+------------------------------------------ Reporter: ken@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.2 Keywords: registry version | Port: ---------------------------------+------------------------------------------ Comment(by ryandesign@…): Are you using the flat registry or the sql registry? (See portdbformat in macports.conf) -- Ticket URL: <https://trac.macports.org/ticket/28084#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#28084: Registry error for ports with underscore ('_') in version ---------------------------------+------------------------------------------ Reporter: ken@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.2 Keywords: registry version | Port: ---------------------------------+------------------------------------------ Comment(by jmr@…): Works for me (I maintain iozone, for example). This sounds a lot like #23966. Are you sure you're using the 1.9.2 release and not some old pre-1.9 trunk version? -- Ticket URL: <https://trac.macports.org/ticket/28084#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS

#28084: Registry error for ports with underscore ('_') in version ---------------------------------+------------------------------------------ Reporter: ken@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.2 Keywords: registry version | Port: ---------------------------------+------------------------------------------ Comment(by jmr@…): Actually I do see this for the ports you mention, but not for all ports with an underscore in the version. -- Ticket URL: <https://trac.macports.org/ticket/28084#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS

#28084: Registry error for ports with underscore ('_') in version ---------------------------------+------------------------------------------ Reporter: ken@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.2 Keywords: registry version | Port: ---------------------------------+------------------------------------------ Comment(by ken@…): Replying to [comment:6 jmr@…]:

Actually I do see this for the ports you mention, but not for all ports with an underscore in the version. I believe I have identified the issue. It's the underscore '''and the dash''' in "2.2_20050523-0". iozone's version is 3_373, which has no dash.

Now, look at proc decode_spec (/opt/local/share/macports/Tcl/registry2.0/registry_util.tcl:55): {{{ proc decode_spec {specifier version revision variants} { upvar 1 $version ver $revision rev $variants var return [regexp {^([^+]+?)(_(\d+)(([-+][^-+]+)*))?$} $specifier - ver - rev v ar] } }}} Experimenting interactively with that regexp: {{{ $ tclsh % echo [regexp {^([^+]+?)(_(\d+)(([-+][^-+]+)*))?$} "2.2_20050523-0_0" - ver - rev var] 1 % echo $ver 2.2 % echo $rev 20050523 % echo $var -0_0 % echo [regexp {^([^+]+?)(_(\d+)(([-+][^-+]+)*))?$} "3_373_0" - ver - rev var] 1 % echo $ver 3_373 % echo $rev 0 % echo $var % }}} -- Ticket URL: <https://trac.macports.org/ticket/28084#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS

#28084: Use of composite version specs should be avoided ---------------------------------+------------------------------------------ Reporter: ken@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: base | Version: 1.9.2 Keywords: registry version | Port: ---------------------------------+------------------------------------------ Comment(by jmr@…): So basically we want to be passing around separate version,revision,variants values whenever possible. The use of composite versions is a holdover from the flat registry, which ironically avoided this problem by actually storing the values this way. (So it would only run into trouble if there actually were two versions of a port installed at the same time where a different possible interpretation was correct for each.) -- Ticket URL: <https://trac.macports.org/ticket/28084#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS

#28084: Use of composite version specs should be avoided ----------------------------------+----------------------------------------- Reporter: ken@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: MacPorts 2.0.0 Component: base | Version: 1.9.2 Resolution: fixed | Keywords: registry version Port: | ----------------------------------+----------------------------------------- Changes (by jmr@…): * status: new => closed * resolution: => fixed * milestone: => MacPorts 2.0.0 Comment: This should be taken care of on the registry side by r79167. The front end could potentially need some more work, since it accepts composite version specs as user input, but we'll see how this goes. -- Ticket URL: <https://trac.macports.org/ticket/28084#comment:12> MacPorts <http://www.macports.org/> Ports system for Mac OS