Re: fitsverify now included in cfitsio: which version to use?
Hi,
On 2024-10-16 11:33, Ole Streicher wrote:
> Aurelien Jarno <aurel32@debian.org> writes:
> > Starting with version 4.5.0, cfitsio now includes the fitsverify binary.
> > I have added it to the libcfitsio-bin package along with the other
> > tools. When receiving bug #1085050, I realized that it was already
> > packaged as a standalone tool.
>
> I am the maintainer of the standalone tool. It comes from the same
> upstream (HEASARC) as cfitsio, and it seems that they are somehow the
> same.
>
> > Now there are two options:
> > - stop shipping it from libcfitsio-bin
> > - add a Conflicts + Provides: fitsverify to libcfitsio-bin and ask for
> > removal of the fitsverify package from the archive. We might
> > optionally add a transitional package to smooth the upgrade.
> >
> > Any opinions?
>
> Clearly option 2, with a transitional package (or maybe just a
> "breaks+provides fitsverify" would be enough?)
Thanks for the feedback, and also to Sergio. I therefore went to the
transitional package way as opposed to breaks+replaces+provides, to
ensure that systems with fitsverify but not libcfitsio-bin installed
will keep the fitsverify binary. This added some more complexity because
the version of fitsverify is higher than the one of cfitsio, but we can
get rid of that package after the release of Trixie.
> I could just happily create an RM bug for fitsverify to clean the path
> for you if you like.
IIRC source packages without binaries get removed automatically. If it
doesn't happen automatically in the next days, I'll fill a RM bug.
Cheers,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://aurel32.net
Reply to: