Opened 12 years ago
Closed 12 years ago
#36679 closed update (fixed)
whizard: update to 2.1.1
Reported by: | Romendakil | Owned by: | whizard@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | haspatch | Cc: | neverpanic (Clemens Lang) |
Port: | whizard |
Description
The software WHIZARD in the scientific part of MacPOrts has a new version (2.1.1 instead of 2.1.0). How do I update MacPorts in order to let the MacPorts user know this?
Attachments (1)
Change History (6)
comment:1 follow-up: 2 Changed 12 years ago by neverpanic (Clemens Lang)
Cc: | cal@… added |
---|---|
Keywords: | Version update removed |
Owner: | changed from macports-tickets@… to whizard@… |
Summary: | Version Update → whizard: update to 2.1.1 |
Changed 12 years ago by Romendakil
Attachment: | patch.whizard.portfile added |
---|
Patch for WHIZARD Portfile for version upgrading 2.1.0 -> 2.1.1
comment:2 Changed 12 years ago by Romendakil
Replying to cal@…:
The proper way to do this is to open a ticket (like you did) and assign it to the maintainer (which I just have done for you). The maintainer (or somebody else, so if you want to give it a try, go ahead) then creates a patch against the Portfile to update the version and checksum statements.
Given the patch, we need the maintainer stating that the patch is fine and a commiter (e.g., me) will commit it. If the port was marked openmaintainer (see the guide for the definition), this update could be done without explicit permission of the maintainer.
Ok, I tried to supply the patch file, updating the version number, the checksums, and the configure parameters.
comment:3 follow-up: 4 Changed 12 years ago by jmroot (Joshua Root)
Keywords: | haspatch added |
---|---|
Version: | 2.1.2 |
The revision should reset to 0 with a new version. For future reference, unified diff format is preferred.
comment:4 follow-up: 5 Changed 12 years ago by Romendakil
Replying to jmr@…:
The revision should reset to 0 with a new version. For future reference, unified diff format is preferred.
Ok, will do that the next time. When will the new version be available in the ports database?
comment:5 Changed 12 years ago by neverpanic (Clemens Lang)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Replying to juergen.reuter@…:
When will the new version be available in the ports database?
In 30 minutes tops, since I just committed the update in r99533. Normally, we would wait for approval of the maintainer (whizard@…), but I'm doing this without approval according to our policy for non-maintainer updates as described in the guide, section 7.3.1: http://guide.macports.org/#project.update-policies.nonmaintainer.
The proper way to do this is to open a ticket (like you did) and assign it to the maintainer (which I have now done for you). The maintainer (or somebody else, so if you want to give it a try, go ahead) then creates a patch against the Portfile to update the version and checksum statements.
Given the patch, we need the maintainer stating that the patch is fine and a commiter (e.g., me) will commit it. If the port was marked openmaintainer (see the guide for the definition), this update could be done without explicit permission of the maintainer.