Re: packaging C interpreter

2012-07-20 Thread Gergely Nagy
Rustom Mody writes: > I use and am interested in packaging the C interpreter > http://www.linuxbox.com/tiki/node/149 > 1. Its not under GPL but a 'creative licence' >From the homepage, and the source, this 'creative license' appears to be the Artistic License, used by, for example, Perl. I do n

packaging C interpreter

2012-07-20 Thread Rustom Mody
I use and am interested in packaging the C interpreter http://www.linuxbox.com/tiki/node/149 Before spending significant time on it, I thought I would ask if this would be acceptable as a debian package Some possible issues: 1. Its not under GPL but a 'creative licence' 2. It build does not use a

Bug#682276: RFS: jampal/02.01.06+dfsg1-1 -- mp3 song library

2012-07-20 Thread pgbennett
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for a new version of Jampal. The previous sponsor of Jampal was Kilian Krause  * Package name    : jampal    Version : 02.01.06+dfsg1-1    Upstream Author : Peter Bennett < pgbenn...@co

Bug#681444: marked as done (RFS: grive/0.2.0-1 [ITP #675310])

2012-07-20 Thread Debian Bug Tracking System
Your message dated Fri, 20 Jul 2012 21:14:18 + with message-id <20120720211418.gh16...@master.debian.org> and subject line RFS: grive/0.2.0-1 [ITP #675310] has caused the Debian Bug report #681444, regarding RFS: grive/0.2.0-1 [ITP #675310] to be marked as done. This means that you claim that

Bug#679344: RFS: bzr-email/0.0.1~bzr58-1 [ITA] is not-fit-for-wheezy

2012-07-20 Thread Thibaut Paumard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 20/07/12 17:14, Satoru KURASHIKI a écrit : > hi, > > On Fri, Jul 20, 2012 at 9:42 PM, Thibaut Paumard > wrote: >> package sponsorship-requests user >> sponsorship-reque...@packages.debian.org usertags 679344 >> not-fit-for-wheezy > >> Now that

Processed: RFS: viennacl/1.3.0-1 (for experimental)

2012-07-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 665354 RFS: viennacl/1.3.0-1 (for experimental) Bug #665354 [sponsorship-requests] viennacl/1.3.0-1 (for experimental) Changed Bug title to 'RFS: viennacl/1.3.0-1 (for experimental)' from 'viennacl/1.3.0-1 (for experimental)' > stop Stopp

Bug#679344: RFS: bzr-email/0.0.1~bzr58-1 [ITA] is not-fit-for-wheezy

2012-07-20 Thread Satoru KURASHIKI
hi, On Fri, Jul 20, 2012 at 9:42 PM, Thibaut Paumard wrote: > package sponsorship-requests > user sponsorship-reque...@packages.debian.org > usertags 679344 not-fit-for-wheezy > Now that the freeze has started, this package is not fit for wheezy. > During freeze, it is generally better to upload

Processed: viennacl/1.3.0-1 (for experimental)

2012-07-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > user sponsorship-reque...@packages.debian.org Setting user to sponsorship-reque...@packages.debian.org (was them...@users.sourceforge.net). > usertags 665354 not-for-wheezy Usertags were: not-fit-for-wheezy. Usertags are now: not-for-wheezy not-f

Bug#679344: RFS: bzr-email/0.0.1~bzr58-1 [ITA] is not-fit-for-wheezy

2012-07-20 Thread Thibaut Paumard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 package sponsorship-requests user sponsorship-reque...@packages.debian.org usertags 679344 not-fit-for-wheezy thanks Hi, Now that the freeze has started, this package is not fit for wheezy. During freeze, it is generally better to upload new upstre

Re: freeze policy - open requests for sponsorship

2012-07-20 Thread Thibaut Paumard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 19/07/12 21:30, Paul Tagliamonte a écrit : > On Thu, Jul 19, 2012 at 07:27:01PM +, Bart Martens wrote: >> On Thu, Jul 19, 2012 at 04:57:44PM +0200, Thibaut Paumard wrote: >>> http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sponsorship-request

Bug#679335: marked as done (RFS: glipper/2.3-3)

2012-07-20 Thread Debian Bug Tracking System
Your message dated Fri, 20 Jul 2012 19:29:27 +0800 with message-id and subject line Re: RFS: glipper/2.3-3 has caused the Debian Bug report #679335, regarding RFS: glipper/2.3-3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is no