#48753 closed update (fixed)
sumo @0.24.0: Update to new release and fix current dependency breakage
Reported by: | lockhart (Thomas Lockhart) | Owned by: | Ionic (Mihai Moldovan) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.3.3 |
Keywords: | haspatch | Cc: | |
Port: | sumo |
Description
SUMO-0.24.0 was released earlier this week. Also, GDAL-2.0 recently replaced the GDAL-1.11.2 port which broke the SUMO-0.23.0 build (and probably other packages also). The new version of SUMO can build against either release of GDAL.
Attachments (1)
Change History (7)
Changed 9 years ago by lockhart (Thomas Lockhart)
Attachment: | Portfile.diff added |
---|
comment:1 Changed 9 years ago by Ionic (Mihai Moldovan)
Owner: | changed from macports-tickets@… to ionic@… |
---|---|
Status: | new → assigned |
Summary: | sumo @ 0.24.0 Update to new release and fix current dependency breakage → sumo @0.24.0: Update to new release and fix current dependency breakage |
comment:2 Changed 9 years ago by Ionic (Mihai Moldovan)
Keywords: | maintainer removed |
---|
Please don't add the maintainer
keyword, if the port actually has no maintainer...
Unless you want to take maintainership?
comment:3 Changed 9 years ago by Ionic (Mihai Moldovan)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Committed as r139980. Thanks!
comment:5 follow-up: 6 Changed 9 years ago by Ionic (Mihai Moldovan)
Any comment on the maintainer bit?
comment:6 Changed 9 years ago by lockhart (Thomas Lockhart)
Replying to ionic@…:
Any comment on the maintainer bit?
Oh! Didn't realize I was not listed. I'm the only one contributing to this port during the last year and a half, and I'm still actively using the software. Please list me unless you would prefer not to. I won't be offended either way. While you are at it, sumo-devel is so obsolete it is painful. I had asked about bumping it to be based on the head of the svn tree but was told that the build needs to be based on a specific tag (or svn version number). The SUMO developers do not do this regularly (or at all), so this port should just go away since its presence is misleading and unhelpful.
Update from 0.23.0 to 0.24.0