Package: sextractor Version: 2.19.5+dfsg-6
Hi Paul, Aurelien, I maintain both packages (sextractor and iraf-fitsutil). 1st, quick answer for sextractor: You don't need to care; this is my fault/problem: The test is home-made and directly compares string-wise the result with a reference catalog, which fails due to minimal changes in the numbers -- from a quick view, that should be neglilible. That also happened in the past, and I solved it by updating the reference (which is ofcourse not the smartest solution). If you have a good general way to handle this, I am happy to apply this; otherwise I will just read+compare the numbers with python3-numpy in future. For iraf-fitsutil, I still have no glue what happens there. That is also a bit painful to debug, since the package is mainly written in a domain specific language (IRAF SPP; Aurelien may know it from work). So I am afraid it may take a bit of time to analyze. Best regards Ole On 04.09.19 22:47, Paul Gevers wrote: > Hi maintainers of sextractor and iraf-fitsutil, > > In bug 939048 we are discussing a transition slot for glibc 2.29. As > part of the preparation we are checking autopkgtest results in unstable, > when glibc 2.29 from experimental is installed. This e-mail is a heads > up of failures in your packages. Can you please check that these are > genuine? If so, please either let us know in this bug, or by filing a > bug against your own package that blocks this bug. > > On 04-09-2019 22:06, Aurelien Jarno wrote: > > [...] > >> Thanks for the info. >> >>> I'll check why there are so many "Test in progress" items. Most of them >>> should be neutral I see. >> >> Ok. I have checked the one marked as regression, and there are only two >> if them that are real regressions in addition to postgresql-hll: >> - iraf-fitsutil: this is a strange issue, I am able to reproduce it, but >> I haven't investigated more yet. > > Log: > https://ci.debian.net/data/autopkgtest/unstable/amd64/i/iraf-fitsutil/2885704/log.gz > >> - sextractor: I am able to reproduce the issue, it seems to be related >> to a math precision change, but I haven't investigated more yet. > > Log: > https://ci.debian.net/data/autopkgtest/unstable/amd64/s/sextractor/2841528/log.gz > > @aurelien, so, let's have the maintainers on board. > > Paul >
