The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 356 (new: 15)
Total number of packages offered up for adoption: 88 (new: 1)
Total number of packages request
Package: wnpp
Severity: wishlist
Owner: Chris Lawrence <[EMAIL PROTECTED]>
* Package name: r-cran-gmaps
Version : 0.1
Upstream Author : Andrew Redd <[EMAIL PROTECTED]>
* URL : http://cran.r-project.org/web/packages/gmaps/index.html
* License : GPL
Description
On 2008-03-06, Hamish Moffatt <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 07, 2008 at 12:15:09AM +0200, Riku Voipio wrote:
>> Hello dear developers,
>>
>> As you may have noticed, a new architecture, armel, has been added to
>> Debian. Here are some highlights and a bit of information in a nutshell.
On Fri, Mar 07, 2008 at 12:15:09AM +0200, Riku Voipio wrote:
> Hello dear developers,
>
> As you may have noticed, a new architecture, armel, has been added to
> Debian. Here are some highlights and a bit of information in a nutshell.
> For more details, refer to the wiki pages[0].
Can someone gi
On Thursday 06 March 2008, Riku Voipio wrote:
> As you may have noticed, a new architecture, armel, has been added to
> Debian. Here are some highlights and a bit of information in a nutshell.
> For more details, refer to the wiki pages[0].
Now that armel is becoming official, could someone involv
Package: wnpp
Severity: wishlist
* Package name: jscoverage
Version : 0.3.1
Upstream Author : Copyright © 2007 siliconforks.com
* URL or Web page : http://siliconforks.com/jscoverage/download.html
* License : GPLv2+
Description : JSCoverage is a tool that measures cod
Hi fellow Debian people,
noticing all the recent discussions about sourcev2/v3, git.tar.gz,
and other VCS-related stuff, I thought I could get away with
dropping a quick pointer to http://vcs-pkg.org, which I hope can
become a central resource for the topics we're discussing.
Also, if you would c
On Wed, Mar 05, 2008 at 08:12:55PM +, Julien Cristau wrote:
> 'Conflicts' is not an appropriate way to resolve a conflict for a
> program name. See policy 10.1:
> Two different packages must not install programs with different
> functionality but with the same filenames. (The case o
8 matches
Mail list logo