Re: nom-tam-fits in debian
Hi Richard and Ole,
I apologise for my very delayed response. I'm definitely willing to help
updating the package. Due a deadline in my ESO project given by the 17th
of March, unfortunately I can offer my help only after this date.
On 03/11/2016 10:15 AM, van Nieuwenhoven, Richard wrote:
question when I try to register/verify I get a
"Could Not Get User"
Am 2016-03-11 um 09:42 schrieb Ole Streicher:
I will try to reach Florian today as well, so that we can find a good
way to proceed here. Probably a shared team maintenance is the best.
For the other questions, I would ask you to follow-up to the Debian
Astronomy mailing list https://lists.debian.org/debian-astro
Altough the fits packags is still in debian-science, I think that by
topic it belongs to debian-astro (and I would ask Florian to move it).
As a documentation for start, I would recommend the New Maintainers
I also write a tutorial which may be helpful, but it is a bit python
centric (for astropy affiliated packages):
Since you are going to help us in team maintenance, you should apply for
team membership on debian-astro and debian-science; for this first
create an account on https://alioth.debian.org and then look to the
according project pages.
Does this help for the start? If you have any other questions, please
don't hesitate to ask.
On 11.03.2016 08:23, van Nieuwenhoven, Richard wrote:
As Florian seems to be unavailable, I redirect my question to the
We would be willing to update the package ourself, but we need some
hints how to do it. And where to register and so on.
As I learned in the mean time, the debain standard enforces the local
build. That is ok with me, the build is a completely standard maven
build, so the packaging should be easy. The release tar's are available
Thanks for any help, pointing us to the right starting place.
Am 2016-02-28 um 09:52 schrieb Richard van Nieuwenhoven:
I see you are the maintainer of the debian package of nom-tam-fits. The
package is rather outdated by now.
As we are on GidHub now and available in the maven central repository,
we want to try to update the debian package. Best method would be to use
the artefacts deployed to central:
they are signed and readonly and available forever (central repo policy)
we created an issue for this task:
if you want to discuss this more openly.