#17625 closed update (fixed)
unixODBC: update to 2.2.14
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | alakazam@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.7.0 |
| Keywords: | Cc: | simon@… | |
| Port: | unixODBC |
Description
It looks like the unixODBC port is at version 2.2.12 but version 2.2.14 is available.
Change History (6)
comment:1 Changed 15 years ago by alakazam@…
comment:3 Changed 15 years ago by alakazam@…
| Cc: | simon@… added |
|---|---|
| Milestone: | Port Bugs → Port Updates |
| Owner: | changed from simon@… to alakazam@… |
| Status: | new → assigned |
| Version: | 1.6.0 → 1.7.0 |
I am now building the latest UnixODBC.
comment:4 Changed 15 years ago by alakazam@…
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
UnixODBC has been updated in r45622 (Maintainer timeout). I've also added a livecheck and linted the Portfile.
comment:5 Changed 15 years ago by jmroot (Joshua Root)
| Type: | defect → update |
|---|
Note: See
TracTickets for help on using
tickets.
No progress has been made on this issue ; octave-database doesn't compile with the current UnixODBC, and might compile with UnixODBC 2.2.14. As there has been no maintainer answer in more than a month, should I update the port ?