Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.java > #9154 > unrolled thread

Seeking a sponsor

Started byGeorge Bateman <georgebateman16@gmail.com>
First post2016-06-05 11:50 +0200
Last post2016-06-07 11:40 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.debian.maint.java


Contents

  Seeking a sponsor George Bateman <georgebateman16@gmail.com> - 2016-06-05 11:50 +0200
    Re: Seeking a sponsor Markus Koschany <apo@debian.org> - 2016-06-07 10:40 +0200
      Re: Seeking a sponsor George Bateman <georgebateman16@gmail.com> - 2016-06-07 11:40 +0200

#9154 — Seeking a sponsor

FromGeorge Bateman <georgebateman16@gmail.com>
Date2016-06-05 11:50 +0200
SubjectSeeking a sponsor
Message-ID<rGCQV-528-11@gated-at.bofh.it>
Hi,

I'm trying to package Processing <https://processing.org> and its
dependencies for Debian; I'm a contributor to it upstream. I've
packaged one dependency, Classpath Explorer, filed an ITP, and
submitted it to mentors.debian.net:
<https://mentors.debian.net/package/classpath-explorer>.
Please could I have a sponsor to help me transfer it to Debian, and to
help me with uploading Processing to Debian?

Thanks,

George Bateman.

[toc] | [next] | [standalone]


#9155

FromMarkus Koschany <apo@debian.org>
Date2016-06-07 10:40 +0200
Message-ID<rHkIi-nf-39@gated-at.bofh.it>
In reply to#9154

[Multipart message — attachments visible in raw view] — view raw

On 05.06.2016 11:26, George Bateman wrote:
> Hi,
> 
> I'm trying to package Processing <https://processing.org> and its
> dependencies for Debian; I'm a contributor to it upstream. I've
> packaged one dependency, Classpath Explorer, filed an ITP, and
> submitted it to mentors.debian.net:
> <https://mentors.debian.net/package/classpath-explorer>.
> Please could I have a sponsor to help me transfer it to Debian, and to
> help me with uploading Processing to Debian?

Hello George,

thanks for your interest in packaging software for Debian. Your basic
packaging of classpath-explorer looks quite good. As usual some parts
could be improved. For instance at first glance you don't need to
mention in your package description that

" This package installs itself in the Maven repository as well as
 /usr/share/java."

I'd rather add one or two sentences about what classpath-explorer is
actually useful for.

I would also remove the orig-tar.sh script and use the Files-Excluded
mechanism in debian/copyright for removing *.class and *.jar files.

The orig-tar.sh script is rather strange because you try to perform an
svn export on an old googlecode repository. The watch file points to
github.com though. Moreover the last project release was in 2009 which
makes me think that better alternatives might exist.

I think in your case it makes sense to package Processing on your local
system first before you start to upload single dependencies to Debian. I
speak for myself but I would like to see the whole software in action
first before I start uploading build-dependencies.

It also appears that packaging Processing is non-trivial. The original
ITP dates back to 2007.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433270

Several attempts failed so far. Please note that also someone packaged
processing-core already.

https://tracker.debian.org/pkg/processing-core

To summarize my concerns, you should be willing to prepare the package
completely and demonstrate that you are able to maintain it for the
foreseeable future. If you want to do that, feel free to ask for more
reviews.

Regards,

Markus




[toc] | [prev] | [next] | [standalone]


#9156

FromGeorge Bateman <georgebateman16@gmail.com>
Date2016-06-07 11:40 +0200
Message-ID<rHlEm-Wz-23@gated-at.bofh.it>
In reply to#9155
The debian directory was autogenerated; I can go through and
delete/correct stuff where needed as you say. I wasn't really sure
what to do regarding giving an upstream URL; the googlecode URL gives
Lintian warnings and is obsolete, but I'm not sure if the Github
repository is actually "official" in any way.

You might notice that 3 tests fail; as far as I can tell, they're
supposed to, since the version distributed with Processing also fails
on the same three tests. Regarding better alternatives, it seems a bit
unreasonable to make modifications to Processing just to use a newer
library. Classpath Explorer is a very small library, so while it might
be unmaintained, it probably doesn't need much maintenance.

As I mentioned in my first post, I contribute a bit to Processing
upstream, so I would of course be happy to maintain the Debian package
in the long term; I've discussed this with the upstream project owner.

On 7 June 2016 at 09:34, Markus Koschany <apo@debian.org> wrote:
> On 05.06.2016 11:26, George Bateman wrote:
>> Hi,
>>
>> I'm trying to package Processing <https://processing.org> and its
>> dependencies for Debian; I'm a contributor to it upstream. I've
>> packaged one dependency, Classpath Explorer, filed an ITP, and
>> submitted it to mentors.debian.net:
>> <https://mentors.debian.net/package/classpath-explorer>.
>> Please could I have a sponsor to help me transfer it to Debian, and to
>> help me with uploading Processing to Debian?
>
> Hello George,
>
> thanks for your interest in packaging software for Debian. Your basic
> packaging of classpath-explorer looks quite good. As usual some parts
> could be improved. For instance at first glance you don't need to
> mention in your package description that
>
> " This package installs itself in the Maven repository as well as
>  /usr/share/java."
>
> I'd rather add one or two sentences about what classpath-explorer is
> actually useful for.
>
> I would also remove the orig-tar.sh script and use the Files-Excluded
> mechanism in debian/copyright for removing *.class and *.jar files.
>
> The orig-tar.sh script is rather strange because you try to perform an
> svn export on an old googlecode repository. The watch file points to
> github.com though. Moreover the last project release was in 2009 which
> makes me think that better alternatives might exist.
>
> I think in your case it makes sense to package Processing on your local
> system first before you start to upload single dependencies to Debian. I
> speak for myself but I would like to see the whole software in action
> first before I start uploading build-dependencies.
>
> It also appears that packaging Processing is non-trivial. The original
> ITP dates back to 2007.
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433270
>
> Several attempts failed so far. Please note that also someone packaged
> processing-core already.
>
> https://tracker.debian.org/pkg/processing-core
>
> To summarize my concerns, you should be willing to prepare the package
> completely and demonstrate that you are able to maintain it for the
> foreseeable future. If you want to do that, feel free to ask for more
> reviews.
>
> Regards,
>
> Markus
>
>
>
>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.maint.java


csiph-web