Since SWarp upstream seems to move to Github:
https://github.com/astromatic
(psfex is already there) there is some hope that they will be a bit more
transparent then now [1]. Therefore it may be useful to have them ready
for that day.
And since you are already using some RCS internally, it would
I agree that the patches should be more easily extractable, this was
originally planned but time constrains did not allow this for the last
two releases, hopefully next time the changes will be included as
separate patch files.
The patches are for the most part incomplete and not upstreamable
Hi Julian,
you are right; it is probably the best to include the patched swarp in
the package as long as the packaged version does not do the job jere.
Although I know that SWarp's upstream is not very responsive: could you
please document the bugs you found with Swarp somewhere publicely,
togeth
Package: cpl-plugin-visir
Version: 4.3.0+dfsg-1
Severity: serious
I have already told you in the past that visir does not work with the
packaged swarp. The swarp included in visir is patched to behave as the
pipeline needs it. There are also feature patches which go beyond the
bugfix patches I
4 matches
Mail list logo
