RFS: starvoyager - package already in main repository
Hello. I'm the maintainer of the package "starvoyager", which, under recently, was generously sponsored by Leo Antunes, however, due to his lack of free time, he has proposed that I will look for another DD who will be willing to review and upload an update i've made to the package. I'm including the original message to my sponsor, describing the enhancements to the package, as well as reference url's for the package description file and diffs: --- I have prepared a new revision of the starvoyager package, with some minor changes: Changes: ~ starvoyager (0.4.4-5) unstable; urgency=low ~ . ~ * Bumb policy number ~ * Stricter menu format as proposed by lintian ~ * Add menu icon - based on patch by Mark Purcell <[EMAIL PROTECTED]> (closes: #319196) The new package changes/diff is available from both the self-hosted location: http://idanso.dyndns.org/maps/sv/ And the repository at mentors.debian.net: http://mentors.debian.net/debian/pool/main/s/starvoyager/ --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Sponsership for libjabber-ruby
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm currently in process of packaging jabber4r, or libjabber-ruby in it's debianized form(ITP #207636), and I'm looking for a sponser to review my work:-) I've followed closely after the current ruby sub-policy, although it seems to be in a draft state - packages are produced for both Ruby 1.6 and 1.8, with 1.8 being the default. Although I'm not sure if that's a correct approach, the package has build-depends on RDoc - upstream do not include pre-generated docs, however, RDoc can be used to produce a usefull reference for the library internals. in anycase those docs are contained in a seperate package as their compressed size is twice larger then the modules themselves, and given the fact we produce 1 "binary" package per Ruby major release, it seemed wise to seperate this piece of bloat:-) the diff/orig/dsc combo(Did I forget anything?) Is available from here: http://idanso.dyndns.org/maps/deb/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/jjNeHT1NNTuNW1YRArMaAKCYw9EYsblc89xMj1iJYNLUIOeAYgCfaVdq fAipZnGcVcwOK/VR502BFS0= =p9Ji -END PGP SIGNATURE-
RFS[2] libjabber-ruby
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm currently in process of packaging jabber4r, or libjabber-ruby in it's debianized form(ITP #207636), and I'm looking for a sponser to review my work:-) libjabber-ruby provides a pure ruby, client-side implemetation of the jabber protocol: http://www.jabber.org I've followed closely after the current ruby sub-policy, although it seems to be in a draft state - packages are produced for both Ruby 1.6 and 1.8, with 1.8 being the default. Although I'm not sure if that's a correct approach, the package has build-depends on RDoc - upstream do not include pre-generated docs, however, RDoc can be used to produce a usefull reference for the library internals. in anycase those docs are contained in a seperate package as their compressed size is twice larger then the modules themselves, and given the fact we produce 1 "binary" package per Ruby major release, it seemed wise to seperate this piece of bloat:-) the diff/orig/dsc combo(Did I forget anything?) Is available from here: http://idanso.dyndns.org/maps/deb/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/oiEeHT1NNTuNW1YRAnD/AJ4qTPVQ68crcp/7/l/b0L9JVT6FJACeLw4P aP5veXXfu5vonXpR/4nOVy0= =5+uU -END PGP SIGNATURE-
RFS[3] libjabber-ruby
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm currently in process of packaging jabber4r, or libjabber-ruby in it's debianized form(ITP #207636), and I'm looking for a sponser to review my work:-) libjabber-ruby provides a pure ruby, client-side implemetation of the jabber protocol: http://www.jabber.org I've followed closely after the current ruby sub-policy, although it seems to be in a draft state - packages are produced for both Ruby 1.6 and 1.8, with 1.8 being the default. Although I'm not sure if that's a correct approach, the package has build-depends on RDoc - upstream do not include pre-generated docs, however, RDoc can be used to produce a usefull reference for the library internals. in anycase those docs are contained in a seperate package as their compressed size is twice larger then the modules themselves, and given the fact we produce 1 "binary" package per Ruby major release, it seemed wise to seperate this piece of bloat:-) the diff/orig/dsc combo(Did I forget anything?) Is available from here: http://idanso.dyndns.org/maps/deb/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/ronlHT1NNTuNW1YRAh/YAJ9ipJwaa60z1/0J/zKxtWs9iT/jUgCeIw0q JSOkGzmbwMGZusV+R0E0nyQ= =vE7J -END PGP SIGNATURE-
RFS[4] libjabber-ruby
I'm currently in process of packaging jabber4r, or libjabber-ruby in it's debianized form(ITP #207636), and I'm looking for a sponser to review my work:-) libjabber-ruby provides a pure ruby, client-side implemetation of the jabber protocol: http://www.jabber.org I've followed closely after the current ruby sub-policy, although it seems to be in a draft state - packages are produced for both Ruby 1.6 and 1.8, with 1.8 being the default. Although I'm not sure if that's a correct approach, the package has build-depends on RDoc - upstream do not include pre-generated docs, however, RDoc can be used to produce a usefull reference for the library internals. in anycase those docs are contained in a seperate package as their compressed size is twice larger then the modules themselves, and given the fact we produce 1 "binary" package per Ruby major release, it seemed wise to seperate this piece of bloat:-) the diff/orig/dsc combo(Did I forget anything?) Is available from here: http://idanso.dyndns.org/maps/deb/
RFS: gcjlib-anttasks
I'm looking a sponser for gcjlib-anttask ITP: http://bugs.debian.org/310962 Repository: http://mentors.debian.net/debian/pool/main/g/gcjlib-anttasks/ gcjlib-anttask is the (proposed?) debianized name for gcjlib by Anthony Green: http://spindazzle.org/gcjlib/ gcjlib-anttask is an extension for the Apache ant build system. it eases and automates the process of building a fully native .so file from java code using the facilities provided by GCC Java frontend. The package is lintian clean, and according to my understanding, follows the debian java policy: http://www.debian.org/doc/packaging-manuals/java-policy/ It should also be noted the package can fully build and run on a free VM(kaffe), although under custom heap size settings: http://lists.debian.org/debian-java/2005/05/msg00104.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: libjabber-ruby
ITP: http://bugs.debian.org/207636 Repository: http://mentors.debian.net/debian/pool/main/l/libjabber-ruby/ libjabber-ruby provides a client-side implemetation of the jabber protocol for the Ruby programming language. It is the debianized name for jabber4r package: http://rubyforge.org/projects/jabber4r/ The packages are lintian clean, and conforms to the Debian sub-policy for Ruby drafts: http://pkg-ruby.alioth.debian.org/ruby-policy.html/index.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Looking for a sponsership
I've taken some time during this weekend to learn a bit of debian packaging system, and i've debianized starvoyager, a star-trek themed game licenced under BSD/LGPL: http://www.srcf.ucam.org/~ret28/ The result is available here: http://idanso.dyndns.org/maps/sv/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Sponsership for libjabber-ruby
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm currently in process of packaging jabber4r, or libjabber-ruby in it's debianized form(ITP #207636), and I'm looking for a sponser to review my work:-) I've followed closely after the current ruby sub-policy, although it seems to be in a draft state - packages are produced for both Ruby 1.6 and 1.8, with 1.8 being the default. Although I'm not sure if that's a correct approach, the package has build-depends on RDoc - upstream do not include pre-generated docs, however, RDoc can be used to produce a usefull reference for the library internals. in anycase those docs are contained in a seperate package as their compressed size is twice larger then the modules themselves, and given the fact we produce 1 "binary" package per Ruby major release, it seemed wise to seperate this piece of bloat:-) the diff/orig/dsc combo(Did I forget anything?) Is available from here: http://idanso.dyndns.org/maps/deb/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/jjNeHT1NNTuNW1YRArMaAKCYw9EYsblc89xMj1iJYNLUIOeAYgCfaVdq fAipZnGcVcwOK/VR502BFS0= =p9Ji -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS[2] libjabber-ruby
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm currently in process of packaging jabber4r, or libjabber-ruby in it's debianized form(ITP #207636), and I'm looking for a sponser to review my work:-) libjabber-ruby provides a pure ruby, client-side implemetation of the jabber protocol: http://www.jabber.org I've followed closely after the current ruby sub-policy, although it seems to be in a draft state - packages are produced for both Ruby 1.6 and 1.8, with 1.8 being the default. Although I'm not sure if that's a correct approach, the package has build-depends on RDoc - upstream do not include pre-generated docs, however, RDoc can be used to produce a usefull reference for the library internals. in anycase those docs are contained in a seperate package as their compressed size is twice larger then the modules themselves, and given the fact we produce 1 "binary" package per Ruby major release, it seemed wise to seperate this piece of bloat:-) the diff/orig/dsc combo(Did I forget anything?) Is available from here: http://idanso.dyndns.org/maps/deb/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/oiEeHT1NNTuNW1YRAnD/AJ4qTPVQ68crcp/7/l/b0L9JVT6FJACeLw4P aP5veXXfu5vonXpR/4nOVy0= =5+uU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS[3] libjabber-ruby
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm currently in process of packaging jabber4r, or libjabber-ruby in it's debianized form(ITP #207636), and I'm looking for a sponser to review my work:-) libjabber-ruby provides a pure ruby, client-side implemetation of the jabber protocol: http://www.jabber.org I've followed closely after the current ruby sub-policy, although it seems to be in a draft state - packages are produced for both Ruby 1.6 and 1.8, with 1.8 being the default. Although I'm not sure if that's a correct approach, the package has build-depends on RDoc - upstream do not include pre-generated docs, however, RDoc can be used to produce a usefull reference for the library internals. in anycase those docs are contained in a seperate package as their compressed size is twice larger then the modules themselves, and given the fact we produce 1 "binary" package per Ruby major release, it seemed wise to seperate this piece of bloat:-) the diff/orig/dsc combo(Did I forget anything?) Is available from here: http://idanso.dyndns.org/maps/deb/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/ronlHT1NNTuNW1YRAh/YAJ9ipJwaa60z1/0J/zKxtWs9iT/jUgCeIw0q JSOkGzmbwMGZusV+R0E0nyQ= =vE7J -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS[4] libjabber-ruby
I'm currently in process of packaging jabber4r, or libjabber-ruby in it's debianized form(ITP #207636), and I'm looking for a sponser to review my work:-) libjabber-ruby provides a pure ruby, client-side implemetation of the jabber protocol: http://www.jabber.org I've followed closely after the current ruby sub-policy, although it seems to be in a draft state - packages are produced for both Ruby 1.6 and 1.8, with 1.8 being the default. Although I'm not sure if that's a correct approach, the package has build-depends on RDoc - upstream do not include pre-generated docs, however, RDoc can be used to produce a usefull reference for the library internals. in anycase those docs are contained in a seperate package as their compressed size is twice larger then the modules themselves, and given the fact we produce 1 "binary" package per Ruby major release, it seemed wise to seperate this piece of bloat:-) the diff/orig/dsc combo(Did I forget anything?) Is available from here: http://idanso.dyndns.org/maps/deb/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Looking for a sponsership
I've taken some time during this weekend to learn a bit of debian packaging system, and i've debianized starvoyager, a star-trek themed game licenced under BSD/LGPL: http://www.srcf.ucam.org/~ret28/ The result is available here: http://idanso.dyndns.org/maps/sv/
Looking for a sponsership for starvoyager
I have published the request two weeks ago, having no repies, I am reposting with a few more details. I have invested some time making sure the package conforms to debian's guidelines, and it passes lintian tests. The package itself is splitted to two, starvoyager, containing the binary, and noarch package starvoyager-data containing images/sounds. > I've taken some time during this weekend to learn a bit of debian > packaging system, and i've debianized starvoyager, a star-trek themed > game licenced under BSD/LGPL: > > http://www.srcf.ucam.org/~ret28/ > > The result is available here: > > > http://idanso.dyndns.org/maps/sv/
