Welcome to iraf.net Thursday, April 18 2024 @ 01:33 AM GMT
ncaon |
09/06/2013 12:01PM (Read 1592 times)
|
|
|
Status: offline
Registered: 10/30/2005
Posts: 29
|
Hi,I've been trying to upgrade TABLES/STSDAS from v3.15, currently installed, to the latest version, 3.16, using the update tools:
make self_update
make check
make update
but the output says that packages tables and stsdas are current.After some investigation, it seems to me that the problem may be related to the fact that the above packages have not been updated in ftp://iraf.noao.edu/iraf/v216/REPO/ (which I understand is the default repository where IRAF looks for external packages), though I see that ftp://iraf.noao.edu/iraf/extern-v216/ contains indeed the latest release.So my question is: Should I just define the variable IRAF_REPO to point to the latter repository, or perhaps I should wait for you to update iraf/v216/REPO/ too?Thanks a lotNicolaP.S. If it matters, I'm running IRAF v2.16 in a Fedora 17 x86_64 Linux desktop.
|
|
|
|
fitz |
09/06/2013 12:01PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
Hi Nicola,I'm not sure what happened, the v3.16 version is what's in our build repository but somehow it never made it to the release repo. In any case, it should be there now, try updating again and sorry for the inconvenience.-Mike
|
|
|
|
ncaon |
09/06/2013 12:01PM
|
|
|
Status: offline
Registered: 10/30/2005
Posts: 29
|
Thanks Mike for the quick reply.However, I'm still unable to update TABLES and STSDAS, since ftp://iraf.noao.edu/iraf/v216/REPO/ apparently still has the old release; the files for STSDAS and TABLES have a timestamp of 08/13/2012.I also tried to redefine IRAF_REPO to ftp://iraf.noao.edu/iraf/extern-v216/, but it does not work:
> make self_update Updating repository data ....
Cannot download repository manifest file, quittingThanks againNicola
|
|
|
|
fitz |
09/06/2013 12:01PM
|
|
|
Status: offline
Registered: 09/30/2005
Posts: 4040
|
Ahh, I see the problem.... The REPO being updated was for v2.15 not v2.16. In any case, it is fixed now, please try updating one more time.
|
|
|
|
| |
|
Content generated in: 0.17 seconds |
|