Opened 13 years ago
Closed 13 years ago
#34320 closed defect (duplicate)
netCDF developer made stealth upgrade, need new checksum
Reported by: | russ@… | Owned by: | tenomoto (Takeshi Enomoto) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.4 |
Keywords: | Cc: | ||
Port: | netcdf |
Description (last modified by mf2k (Frank Schima))
Hi,
I unwisely made a "stealth upgrade" in the netCDF-4.2 release at
ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf-4.2.tar.gz
and
ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf-4.2.zip
I changed the IP number of our test server in some remote access test code. I see the error in my ways. I would like to fix the problem without reverting to the use of the old test server, which results in failed tests and support questions for us.
How can I best do this? I'm not the Macports committer for netCDF, so maybe I should be corresponding with him/her. How do I find out who that person is?
--Russ
Russ Rew UCAR Unidata Program
russ@… http://www.unidata.ucar.edu/staff/russ
Change History (3)
comment:1 Changed 13 years ago by mf2k (Frank Schima)
Description: | modified (diff) |
---|---|
Owner: | changed from macports-tickets@… to takeshi@… |
Port: | netcdf added |
comment:2 Changed 13 years ago by russ@…
Replying to russ@…:
I unwisely made a "stealth upgrade" in the netCDF-4.2 release at
ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf-4.2.tar.gzand
ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf-4.2.zipI changed the IP number of our test server in some remote access test code. I see the error in my ways. I would like to fix the problem without reverting to the use of the old test server, which results in failed tests and support questions for us.
I restored the netcdf-4.2.zip and netcdf-4.2.tar.gz files on our FTP server to the Mar 20 19:33 versions, which should have the original checksums.
In that FTP directory, there are symbolic links netcdf.zip and netcdf.tar.gz to the "stealth release" files netcdf-4.2.0.zip and netcdf-4.2.0.tar.gz, which updated a port number for tests.
The test server is now running on both old and new ports, so both releases should build identically. this problem will be eliminated in the next release by removing port numbers from the URLs in the source and letting Apache pick the right ports for testing.
--Russ Russ Rew, UCAR Unidata Program russ@… http://www.unidata.ucar.edu/staff/russ
comment:3 Changed 13 years ago by tenomoto (Takeshi Enomoto)
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Duplicate of #34315.
To find the maintainer of this port type:
I have assigned this ticket to the maintainer. In the future, please also fill in the Port field.