[MacPorts] #36679: Version Update
#36679: Version Update ------------------------------+-------------------------------- Reporter: juergen.reuter@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: Version update | Port: whizard ------------------------------+-------------------------------- 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? -- Ticket URL: <https://trac.macports.org/ticket/36679> MacPorts <http://www.macports.org/> Ports system for Mac OS
#36679: whizard: update to 2.1.1 -------------------------------+----------------------- Reporter: juergen.reuter@… | Owner: whizard@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: whizard | -------------------------------+----------------------- Changes (by cal@…): * cc: cal@… (added) * owner: macports-tickets@… => whizard@… * keywords: Version update => Comment: 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. -- Ticket URL: <https://trac.macports.org/ticket/36679#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#36679: whizard: update to 2.1.1 -------------------------------+----------------------- Reporter: juergen.reuter@… | Owner: whizard@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: whizard | -------------------------------+----------------------- Comment (by juergen.reuter@…): Replying to [comment:1 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. -- Ticket URL: <https://trac.macports.org/ticket/36679#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#36679: whizard: update to 2.1.1 -------------------------------+----------------------- Reporter: juergen.reuter@… | Owner: whizard@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: whizard | -------------------------------+----------------------- Changes (by jmr@…): * keywords: => haspatch * version: 2.1.2 => Comment: The revision should reset to 0 with a new version. For future reference, unified diff format is preferred. -- Ticket URL: <https://trac.macports.org/ticket/36679#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#36679: whizard: update to 2.1.1 -------------------------------+----------------------- Reporter: juergen.reuter@… | Owner: whizard@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: whizard | -------------------------------+----------------------- Comment (by juergen.reuter@…): Replying to [comment:3 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? -- Ticket URL: <https://trac.macports.org/ticket/36679#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#36679: whizard: update to 2.1.1 -------------------------------+----------------------- Reporter: juergen.reuter@… | Owner: whizard@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch Port: whizard | -------------------------------+----------------------- Changes (by cal@…): * status: new => closed * resolution: => fixed Comment: Replying to [comment:4 juergen.reuter@…]:
When will the new version be available in the ports database?
In 30 minutes tops, since I just committed the updated in r99533. Normally, we would wait for approval of the maintainer (whizard@mail.desy.de), 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. -- Ticket URL: <https://trac.macports.org/ticket/36679#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts