#2876 closed defect (fixed)
BUG: 'epoch' does not affect port updating
| Reported by: | danchr@… | Owned by: | olegb@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | base | Version: | 1.0 |
| Keywords: | Cc: | olegb@… | |
| Port: |
Description
Description: Setting 'epoch' to ensure that a port is considered updated despite a possible 'downgrading' in it's version, does not affect 'port upgrade'.
I tried to take a peak at the source but I couldn't make much sense of the upgrade function :) Cc'ing Ole by Landon's suggestion.
Steps to reproduce:
- Update dports/ to get newest cdparanoia.
- port upgrade cdparanoia
Expected results:
- cdparanoia is updated from version 5 to the newer 0.9.8.
Actual Results:
- cdparanoia is not updated; version 5 remains installed.
Change History (6)
comment:1 Changed 19 years ago by olegb@…
| Owner: | changed from darwinports-bugs@… to olegb@… |
|---|
comment:2 Changed 19 years ago by olegb@…
As far as i can tell, there is no way to retrieve the epoch of a port allready installed - so epoch cannot be uses in an upgrade comparison, until there is a way to get the epock key from an installed port (from registry).
comment:3 Changed 19 years ago by olegb@…
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
fixed in release1, will merge with later (today?)
the fix will require that you have installed the "epoch-using" port with the new register-format also commited.
comment:4 Changed 19 years ago by danchr@…
(In reply to comment #3)
the fix will require that you have installed the "epoch-using" port with the new register-format also commited.
Just wondering, would this handle the case in which an old port, not using epoch, suddenly uses epoch?
comment:5 Changed 19 years ago by olegb@…
every port uses epoch, the value defaults to zero.
so, if a port suddenly uses a non-zero epoch it is upgraded.
Right, the upgrade procedure doesn't use epoch.
I'll look into this as soon as i have the time.