Opened 10 years ago
Closed 10 years ago
#44746 closed update (fixed)
libctl @3.2.2 update to new version
| Reported by: | Yogesh.Sharma@… | Owned by: | higginja@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | haspatch | Cc: | ryandesign (Ryan Carsten Schmidt) |
| Port: | libctl |
Description
Currently the libctl that is include in macports is 3.1.1 and the current version is 3.2.2
This Portfile updates libctl to version 3.2.2 and updates the guile dependency to the newest version of guile.
Attachments (2)
Change History (15)
Changed 10 years ago by Yogesh.Sharma@…
comment:1 Changed 10 years ago by Yogesh.Sharma@…
| Cc: | Yogesh.Sharma@… added |
|---|
comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added; Yogesh.Sharma@… removed |
|---|---|
| Keywords: | haspatch added |
| Owner: | changed from macports-tickets@… to higginja@… |
| Type: | enhancement → update |
Please attach a unified diff of your changes.
comment:3 Changed 10 years ago by Yogesh.Sharma@…
I attached the unified diff of the changes to the libctl port. Is there any other changes that need to be applied to the port for it to be accepted?
comment:4 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Thanks for letting us know. Merely attaching a file to a ticket does not generate an email notification; adding a comment does.
The line "distname libctl-${version}" should not be added because that is the default. Also the "revision" line should be removed when the version is increased. Other than that it looks reasonable.
comment:5 Changed 10 years ago by Yogesh.Sharma@…
I updated the patch to remove the revision and distname lines.
comment:7 Changed 10 years ago by Yogesh.Sharma@…
Sorry I accidentally diff-ed the wrong directories ...... I updated the patch with the correct information.
comment:8 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
higginja, do you approve of this patch? Note that Yogesh.Sharma is requesting to be added as co-maintainer.
comment:9 Changed 10 years ago by Yogesh.Sharma@…
How long do we want to wait for approval before moving forward with this update?
comment:10 Changed 10 years ago by neverpanic (Clemens Lang)
See https://guide.macports.org/#project.update-policies.nonmaintainer and https://guide.macports.org/#project.update-policies.abandonment.
I can commit the functional change right away under the regulations of maintainer timeout. For the maintainer change, I'd normally wait for maintainer approval, but since it's been three weeks without acknowledgement from the maintainer, we'd might just want to do the port abandonment procedure now. Let me know which one it's going to be.
comment:11 Changed 10 years ago by Yogesh.Sharma@…
I would like to start the port abandonment procedure. I tried to contact the port maintainer in the past and received no response.
comment:12 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Alex sent the following response by email:
Whatever update you need to make os fine with me. Sorry, but I haven't had time to check this update myself, nor can I try to maintain this port right now. Thanks,
comment:13 Changed 10 years ago by mf2k (Frank Schima)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
| Version: | 2.3.1 |
r125381. I removed Alex as maintainer and added openmaintainer.
Cc Me!