Speculation: the key was renewed locally, but those things have not
been uploaded to the keyservers.
Hi Eike: The explanation was similar to your above speculation but not quite. :-) I had not refreshed my local keyring from the keyservers recently. When I did that refresh (inspired by your speculation), the expired key "problem" was solved. So sorry for the noise, but nevertheless there is a useful gpg lesson to be learned here. After keys expire they can be renewed (which I didn't realize before) rather than having to generate a whole new key. So that means I (or anybody else) should always execute "gpg --refresh-keys" before complaining about expired keys! Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
