ncview

[Magnus Hagdorn-2]

Hi there,
I would like to package ncview - a simple netCDF file viewer
http://meteora.ucsd.edu/~pierce/ncview_home_page.html

In fact I have already done so and wonder how I can get the package into
Debian. So I figured this is probably the best place to ask.

I have created an account on alioth. I have also asked to become a
member of the Alioth Grass Project. What next?

As a brief introduction of myself... I have been a Linux user for ages
(since 1994). I am a scientific software developer and as such into
scientific data formats such as netCDF, data visualisation and fortran
and HPC programming. So far I haven't been involved with any
distributions so I figured it is about time.

Cheers
magnus


_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[Francesco P. Lovergine]

On Fri, Jul 10, 2009 at 03:21:25PM +0100, Magnus Hagdorn wrote:

> Hi there,
> I would like to package ncview - a simple netCDF file viewer
> http://meteora.ucsd.edu/~pierce/ncview_home_page.html
>
> In fact I have already done so and wonder how I can get the package into
> Debian. So I figured this is probably the best place to ask.
>
> I have created an account on alioth. I have also asked to become a
> member of the Alioth Grass Project. What next?
>

You got it, you just need to ask for sponsoring and reviewing
when a package will be ready. Of course usual recommendations
applies, i.e. be familiar with current Debian Policy document
for packaging, read the New Maintainer Guide and so on. In
the meantime feel free to cooperate on other packages too
which can be of your interest.

> As a brief introduction of myself... I have been a Linux user for ages
> (since 1994). I am a scientific software developer and as such into
> scientific data formats such as netCDF, data visualisation and fortran
> and HPC programming. So far I haven't been involved with any
> distributions so I figured it is about time.
>

Welcome aboard. Better later than never :)

--
Francesco P. Lovergine

_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[Magnus Hagdorn-2]

On Fri, 2009-07-10 at 17:37 +0200, Francesco P. Lovergine wrote:

> > I have created an account on alioth. I have also asked to become a
> > member of the Alioth Grass Project. What next?
> >
>
> You got it, you just need to ask for sponsoring and reviewing
> when a package will be ready. Of course usual recommendations
> applies, i.e. be familiar with current Debian Policy document
> for packaging, read the New Maintainer Guide and so on. In
> the meantime feel free to cooperate on other packages too
> which can be of your interest.

OK, I have finished building the package using the new maintainer guide.
Where can I post it for review? How do I go about finding a sponsor?

As an aside are there any packages that need particular help at the
moment?

Cheers
magi



_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[hamish-2]

Magnus Hagdorn wrote:
> As an aside are there any packages that need particular
> help at the moment?


Quantum GIS is a glaring omission from our repertoire. this needs to be
coordinated with the QGIS devs*, reviewed, etc. see

https://trac.osgeo.org/qgis/ticket/1028


[*] Paolo, you reading this? any comments as to status?


regards,
Hamish



     


_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[Francesco P. Lovergine]

On Sun, Jul 12, 2009 at 09:16:40PM +0100, Magnus Hagdorn wrote:
>
> OK, I have finished building the package using the new maintainer guide.
> Where can I post it for review? How do I go about finding a sponsor?
>

You need to refine the packaging stuff. Please check and update for a recent
policy (3.8.2), remove unused .ex files and all unused debhelper stuff.
Avoid including not useful templates in general. Also build against an
up-to-date sid chroot to verify you are using the complete and up-to-date
build-deps. This is my first comments based on a few seconds check, other
could come with a more deep analysis...

--
Francesco P. Lovergine

_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[Francesco P. Lovergine]

On Sun, Jul 12, 2009 at 09:16:40PM +0100, Magnus Hagdorn wrote:
> OK, I have finished building the package using the new maintainer guide.
> Where can I post it for review? How do I go about finding a sponsor?
>

You need to complete the debian/copyright file with all required information
about authors and copyright. See for instance SciPlot.c which is BSD licensed
by another author. DO NOT trust authors about licenses, verify each files at
every releases. Missing in doing that would result easily in a ftpmasters drop
of the contributed package.

Please, submit an ITP for the new package with appropriate description,
and check against a sid lintian, because it presents a series of issues.

--
Francesco P. Lovergine

_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[Francesco P. Lovergine]

> OK, I have finished building the package using the new maintainer guide.
> Where can I post it for review? How do I go about finding a sponsor?
>

Some README documents are superfluous: Solaris and Sgi platform related ones.
You also should add a menu and a watch file for ncview. A menu is due because
it is an X11 program, so have a look to the current menu policy with new
sections.

--
Francesco P. Lovergine

_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[Paolo Cavallini]

Hamish ha scritto:

> Magnus Hagdorn wrote:
>> As an aside are there any packages that need particular
>> help at the moment?
>
>
> Quantum GIS is a glaring omission from our repertoire. this needs to be
> coordinated with the QGIS devs*, reviewed, etc. see
>
> https://trac.osgeo.org/qgis/ticket/1028
>
>
> [*] Paolo, you reading this? any comments as to status?

Agreed fully. I use debian/rules from trunk to make my packages, without
any obvious problem, but I do not know how much work is involved to
bring qgis back to debian. This would be a much needed major achievement
IMHO.
All the best.
--
Paolo Cavallini: http://www.faunalia.it/pc

_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[Francesco P. Lovergine]

On Tue, Jul 14, 2009 at 10:21:09AM +0200, Paolo Cavallini wrote:

> Hamish ha scritto:
> > Magnus Hagdorn wrote:
> >> As an aside are there any packages that need particular
> >> help at the moment?
> >
> >
> > Quantum GIS is a glaring omission from our repertoire. this needs to be
> > coordinated with the QGIS devs*, reviewed, etc. see
> >
> > https://trac.osgeo.org/qgis/ticket/1028
> >
> >
> > [*] Paolo, you reading this? any comments as to status?
>
> Agreed fully. I use debian/rules from trunk to make my packages, without
> any obvious problem, but I do not know how much work is involved to
> bring qgis back to debian. This would be a much needed major achievement
> IMHO.
> All the best.

Mainly policy compliance and setting up the required framework to manage
smooth plugins updates. I already sent a message about that on the qgis-dev
list. No answers at my knowledge...

--
Francesco P. Lovergine

_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[Magnus Hagdorn-2]

On Tue, 2009-07-14 at 10:41 +0200, Francesco P. Lovergine wrote:
> On Sun, Jul 12, 2009 at 09:16:40PM +0100, Magnus Hagdorn wrote:
> > OK, I have finished building the package using the new maintainer guide.
> > Where can I post it for review? How do I go about finding a sponsor?
> >
>
> Magnus if you agree, I would complete the missing parts and upload,
> you will see the complete changes in a single diff.
>
yes, that would be great. Thanks for the review.

I don't think the package needs a menu entry since you cannot run the
program without at least one argument (the file to display).

I also submitted an ITP but never heard back from it :-(

Cheers
magnus



_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[hamish-2]

frankie@debian wrote:
> Mainly policy compliance and setting up the required framework to manage
> smooth plugins updates. I already sent a message about that on the
> qgis-dev list. No answers at my knowledge...


Then I would suggest to send .deb version a.b.c-0 to sid/experimental with
plugins (or plugin updates) disabled. This could get the bulk of the non-
plugin packaging issues dealt to and perhaps motivate others to help
with plugin needs.

Do the qgis plugins have a firefox-like addon update structure?? (eek)
If so, can we ship a static snapshot of them? I'd prefer to keep things
in main and just deal with some things being out of date, but perhaps
the volatile repo is another option. Moving targets and external downloads
will not help to get it packaged quickly..


Hamish



     


_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[Francesco P. Lovergine]

On Tue, Jul 14, 2009 at 01:47:59AM -0700, Hamish wrote:

>
> frankie@debian wrote:
> > Mainly policy compliance and setting up the required framework to manage
> > smooth plugins updates. I already sent a message about that on the
> > qgis-dev list. No answers at my knowledge...
>
>
> Then I would suggest to send .deb version a.b.c-0 to sid/experimental with
> plugins (or plugin updates) disabled. This could get the bulk of the non-
> plugin packaging issues dealt to and perhaps motivate others to help
> with plugin needs.
>
> Do the qgis plugins have a firefox-like addon update structure?? (eek)
> If so, can we ship a static snapshot of them? I'd prefer to keep things
> in main and just deal with some things being out of date, but perhaps
> the volatile repo is another option. Moving targets and external downloads
> will not help to get it packaged quickly..
>

I'm mainly worried by the currently volatile interface for plugins (python or what else),
so that a per package interface in Provides: should be included with Qgis. It at least
would avoid recurrent breakages due to misversioning. Better doing that soon that later.
I'm not sure if third-parties plugins will be available any time soon, but I would
prefer a defensive approach on that regards.

--
Francesco P. Lovergine

_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general

[Moritz Lennert]

On 14/07/09 10:47, Hamish wrote:

> frankie@debian wrote:
>> Mainly policy compliance and setting up the required framework to manage
>> smooth plugins updates. I already sent a message about that on the
>> qgis-dev list. No answers at my knowledge...
>
>
> Then I would suggest to send .deb version a.b.c-0 to sid/experimental with
> plugins (or plugin updates) disabled. This could get the bulk of the non-
> plugin packaging issues dealt to and perhaps motivate others to help
> with plugin needs.
>
> Do the qgis plugins have a firefox-like addon update structure?? (eek)
> If so, can we ship a static snapshot of them? I'd prefer to keep things
> in main and just deal with some things being out of date, but perhaps
> the volatile repo is another option. Moving targets and external downloads
> will not help to get it packaged quickly..

There are four types of plugins:

- The "core" plugins which ship with QGIS (e.g. delimited-text, georef,
etc) and which, in the current definitions of the debian directory in
the QGIS tree, are in the qgis package.

- The grass plugin which is in the qgis-plugin-grass and
qgis-plugin-grass-common package.

- The 'plugin installer' plugin which is in the python-qgis-common
package, and which, once activated allows to then download the

- Other plugins which you can download and update from within the plugin
installer in QGIS.

I guess "only" the first three need to be worried about...

Moritz

_______________________________________________
Pkg-grass-general mailing list
[hidden email]
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general