Opened 6 years ago
Closed 6 years ago
#56649 closed update (fixed)
Update Mercurial from 4.5.3 -> 4.6.1
| Reported by: | josephsacco | Owned by: | seanfarley (Sean Farley) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | mercurial |
Description
The current version of Mercurial is 4.6.1. I built the current version by updating the checksums and removing the patch file [see attached Portfile.diff]. The build completed without incident.
I ran the extensive test suite, which runs forever. Most of the tests passed.
-Joseph
Attachments (1)
Change History (9)
comment:1 Changed 6 years ago by josephsacco
comment:2 Changed 6 years ago by mf2k (Frank Schima)
| Cc: | sean@… removed |
|---|---|
| Keywords: | mercurial update removed |
| Owner: | set to seanfarley |
| Status: | new → assigned |
| Version: | 2.5.2 |
Please use the obsolete port guidance instead of removing the -devel port so that anyone who has it installed will be updated too.
comment:3 Changed 6 years ago by seanfarley (Sean Farley)
That should be eliminated from the port tree.
What? I guess the repo hasn't been updated since the bot is down (which I'll update here in a minute) but why should it be removed?
comment:4 Changed 6 years ago by josephsacco
Frank: Point taken. I should (re)read the documentation and follow protocol.
Sean: See above.
-Joseph
comment:5 Changed 6 years ago by raimue (Rainer Müller)
See what above? You provided no reasons to remove mercurial-devel...
comment:6 Changed 6 years ago by seanfarley (Sean Farley)
I see the comments above but no reason explaining why you want to remove mercurial-devel.
comment:7 Changed 6 years ago by josephsacco
Sorry for the confusion. I was suggesting that I should (re)read the manual and follow protocol if I wish to continue making submissions to MacPorts.
As for the development version of mercurial...
If a development version of mercurial exists, MacPorts could certainly support it. I took a quick look and could not find one. You may be more successful in searching for it.
-Joseph
comment:8 Changed 6 years ago by seanfarley (Sean Farley)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Ready, Fire, Aim...
Reviewing the Portfile, I see there was a sub-port,
subport mercurial-devel { bitbucket.setup seanfarley mercurial f1a0933ce59e name mercurial-devel version 4.5.99 revision 0 conflicts mercurial master_sites ${bitbucket.master_sites} checksums rmd160 6035b11e2e037b824b61231a49e8a53f1a69d3a9 \ sha256 0812e74014fdc15b4f0b61e1528c30461bd6efc2f64e40059d047139faffe838 }That should be eliminated from the port tree.
I will update the Portfile diff.
-Joseph