#2480 closed defect (fixed)
Port upgrade should not deactivate port until new version is known good
| Reported by: | jberry@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 1.0 |
| Keywords: | Cc: | ||
| Port: |
Description
Port upgrade deactivates the current port before it knows whether it can even fetch, checksum, or build a new version. If any of those steps fail, the port will be left deactive.
Port upgrade should defer deactivation of the current port until it has successfully built (destrooted?) the current port.
(Actually it would be nice if it could actually install the new version (inactivated) first. Then it would be just a matter deactivate old/activate new -- a nice symmetry).
Another issue with the current method is if the curl installed by dp was found by configure for dp. In attempting to upgrade such a curl installation, the curl desired by dp to fetch the new version is deactivated before it can be used, so the fetch fails.
Change History (3)
comment:1 Changed 20 years ago by jberry@…
comment:2 Changed 20 years ago by olegb@…
no, if it fails it re-activates the "old version" - so, maybe we should close here ?
comment:3 Changed 20 years ago by jberry@…
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Closing bug, as it's been fixed.
Hmm. I think this all got fixed up. I know the issue with curl got cleaned up.
Ole: does port upgrade still leave the port inactive if fetch or build fails?