#13545 closed defect (fixed)
port version doesn't distinguish trunk
| Reported by: | yaseppochi (Stephen J. Turnbull) | Owned by: | mww@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 1.5.2 |
| Keywords: | update | Cc: | mww@…, jmpalacios (Juan Manuel Palacios) |
| Port: |
Description
In regard to the 'invalid command name "cd"' issue that is slowly being fixed throughout the Portfiles it seems, I reported one such bug and was told
Comment: If you're encountering this error, you must have built MacPorts from trunk. MacPorts 1.6.0 will still include the `cd` command.
But "port version" tells me "Version: 1.600".
Change History (4)
comment:1 Changed 17 years ago by mww@…
| Cc: | mww@… jmpp@… added |
|---|---|
| Keywords: | update added |
| Owner: | changed from macports-dev@… to mww@… |
| Priority: | Normal → High |
| Status: | new → assigned |
| Version: | → 1.5.2 |
comment:2 Changed 17 years ago by jmpalacios (Juan Manuel Palacios)
| Milestone: | Port Bugs → MacPorts base bugs |
|---|---|
| Priority: | High → Normal |
| Resolution: | → fixed |
| Status: | assigned → closed |
This might be due to the fact that both trunk and the current release branch, release_1_6, carry the same version number due to an oversight on my part, so it's probably impossible to distinguish between trunk and release_1_6 if you don't dig deeper than port version; I really doubt that any leak through selfupdate occurred. I corrected the problem in r31907.
-jmpp
comment:3 Changed 16 years ago by tobypeterson
| Milestone: | MacPorts base bugs → MacPorts Future |
|---|
Milestone MacPorts base bugs deleted
comment:4 Changed 15 years ago by jmroot (Joshua Root)
| Milestone: | MacPorts Future |
|---|
Note: See
TracTickets for help on using
tickets.
So you got version 1.6 via port selfupdate???