#15397 closed defect (fixed)
libuninum distfile changed
| Reported by: | simon@… | Owned by: | mww@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.6.0 |
| Keywords: | Cc: | ||
| Port: |
Description
Hi,
the checksums for the libuninum distfile have changed:
Portfile: sha1 3886b511b9f7e8a84efc16bc8e03bb676ce7104e Now: sha1 03e0390da91a0c3242da7d36cb21285906663066
The new distfile compiles fine for me, but please look into it.
Thanks, Simon
Change History (3)
comment:1 Changed 16 years ago by simon@…
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
When changing portfile checksums because an upstream distfile changed without the filename changing, you must also change the dist_subdir so that the new distfile goes to a different place than the old file. Otherwise users who had the existing distfile downloaded already will get a checksum error. Now that we have a distfiles mirror, it's even more important to ensure each unique distfile gets a unique location in the distfiles directory. Otherwise the distfiles mirror doesn't get updated either.
If the new distfile is not just a repackaging, but actually causes different files to be installed, then you must also Increase the port revision. I can confirm by comparing the old and new distfiles that there are hundreds of lines of diffs.
I increased the port revision and changed the dist_subdir in r37443.
I committed this in r37432. If you don't like this change just revert it.