I've created a PR for the makefile change I've made:

https://github.com/dstndstn/astrometry.net/pull/90

astrometry.net updated to 0.67 + Tim Jenness and my changes. Only builds the C portions (doesn't run make python or make extras), so outside code that depends on the python interface/scripts will almost certainly fail on python 3. But it's enough to make our meas_astrom tests pass.

I checked and those patch files were indeed not relevant any longer.

I find it strange that I get told there are no clang patches to apply but that seems to have been saying that for ages.

I have one main comment and that is I have no idea what version of astrometry.net this really contains. I would prefer it if we took the ngmix approach of including an upstream SHA1 in the version number of the file (and later tag). Also, since your Makefile patches have not (yet) been accepted by upstream we should include them explicitly in a patches directory. Otherwise, in a few months we will have no way of understanding which astrometry.net we are really using.

The clang message is coming from eupspkg.cfg.sh. That line can probably be deleted, but I don't know what it's about.

I've renamed the tarball and made it based on upstream master, and added a patchfile based on the Makefile changes against that. Rebuilding on Jenkins to be sure stuff is still happy.

Merged! Multiple Jenkins runs passed.