Package: wnpp
Owner: tak...@debian.org
Severity: wishlist
* Package name: techne
Version : 0.2
Upstream Author : Dimitris Papavasileiou
* URL or Web page : http://www.nongnu.org/techne/
* License : GPL-3
Description : programmable physical simulator and renderer
Tec
Package: wnpp
Severity: wishlist
Owner: "Roberto C. Sanchez"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: luamongo
Version : 0.0.0+svn20110118
Upstream Author : Neil Richardson
* URL : http://code.google.com/p/luamongo/
* License : MIT
Pr
Package: wnpp
Severity: wishlist
Owner: Oxan van Leeuwen
I want to package the python-gearman library, as it's a lot easier to use
then python-gearman.libgearman and it has better documentation.
* Package name: python-gearman
Version : 2.0.2
Upstream Author : Matthew Tai
* URL
Package: wnpp
Severity: wishlist
Owner: ka...@ccs.neu.edu
* Package name: dmtcp
Version : 1.2.0
Upstream Author : Kapil Arya
* URL : http://dmtcp.sourceforge.net/
* License : LGPL
Programming Lang: C, C++
Description : Checkpoint/Restart functionality
Stefan Fritsch writes ("Re: security updates introducing breakage"):
> Ack. There is no automatic way the security team is notified of such bugs.
> Please CC us in such cases.
Would it be worth defining a [user]tag of some kind that would allow
this kind of thing to be dealt automatically ?
An a
On Thu, 20 Jan 2011, Ian Jackson wrote:
Stefan Fritsch writes ("Re: security updates introducing breakage"):
Ack. There is no automatic way the security team is notified of such bugs.
Please CC us in such cases.
Would it be worth defining a [user]tag of some kind that would allow
this kind of
On Thu, 20 Jan 2011, Adam D. Barratt wrote:
On Thu, January 20, 2011 03:18, Paul Wise wrote:
On Thu, Jan 20, 2011 at 10:59 AM, Brian May
wrote:
What is policy when security updates for stable introduce new
regressions in software that weren't there before? Can these get fixed
in stable?
If
On Thursday 20 January 2011 15:33:17 Adam Borowski wrote:
> On Thu, Jan 20, 2011 at 02:27:55PM +0100, Dominique Dumont wrote:
> > On Thursday 13 January 2011 16:35:06 Picca Frédéric-Emmanuel wrote:
> > > 16:30:47 Invalid line: Copyright : � 1997-1999 AT&T Laboratories
> > > Cambridge
>
>
Package: wnpp
Severity: wishlist
Owner: Christophe Trophime
* Package name: nlopt
Version : 2.2.1
Upstream Author : Steven G. Johnson
* URL : http://ab-initio.mit.edu/wiki/index.php/NLopt
* License : LGPL
Programming Lang: C, C++, Python, octave
Descripti
On Thu, Jan 20, 2011 at 02:27:55PM +0100, Dominique Dumont wrote:
> On Thursday 13 January 2011 16:35:06 Picca Frédéric-Emmanuel wrote:
> > 16:30:47 Invalid line: Copyright : � 1997-1999 AT&T Laboratories Cambridge
^
Aren't those supposed to be UTF-8 encoded?
On Saturday 15 January 2011 17:04:30 Joey Hess wrote:
> One more thing, "License: GPL-2+ | Expat" was an old syntax on the wiki,
> and it seems the parser only looks for an expansion of the GPL-2+
> license in this case, ignoring the Expat part.
That was a bug in the Parse::RecDescent grammar snip
On Thursday 13 January 2011 23:54:04 Charles Plessy wrote:
> By the way, Dominique, some licence version numbers can contain
> alphanumeric characters. For instance the LaTeX project public license,
> version 1.3c.
Given that License keywords are fuzzy, moving targets. I've dropped any
attempt at
Hello Frédéric
On Thursday 13 January 2011 16:35:06 Picca Frédéric-Emmanuel wrote:
> hello, another try :)
>
> picca@grisette:~/Debian/tango/tango$ config-edit -application
> dpkg-copyright -ui none You should install Config::Model::TkUI or
> Config::Model::CursesUI for a more friendly user inter
Package: wnpp
Severity: wishlist
Owner: Charles Plessy
Package name: sra-sdk
Version : 2.0.0rc1
Upstream Author : National Center for Biotechnology Information (U. S. A.)
URL :
http://trace.ncbi.nlm.nih.gov/Traces/sra/sra.cgi?cmd=show&f=software&m=software&s=softw
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org,debian-p...@lists.debian.org
* Package name: libanyevent-dbi-perl
Version : 2.1
Upstream Author : Marc Lehmann , Adam Rosenstein
* URL : http://search.cpan.org/dist/AnyEvent-DBI/
* License
Hi, Olaf:
On Thursday 20 January 2011 09:51:27 Olaf van der Spek wrote:
> On Wed, Jan 19, 2011 at 9:27 AM, Nikita V. Youshchenko
wrote:
> > Then, maybe explicitly request upstream - at appropriate forums and in
> > appropriate polite wording - to help debian team(s) to handle the bug
> > report
Izmet no sava kompja, neinteresanto un neinteresanto porno filmu kolekciju un
piedalies ziemas porno izpardoshanaa!!
Nevar buut :- 8560 filmas tikai par nieka 75 santimiem..
Panem un pielade pilnu cieto disku ar superigu porno!
http://www.allforfree.radinet.de saac sheit!
--
To UNSUBSCRIB
On Wed, Jan 19, 2011 at 9:27 AM, Nikita V. Youshchenko wrote:
> Then, maybe explicitly request upstream - at appropriate forums and in
> appropriate polite wording - to help debian team(s) to handle the bug
> report stream?
I think upstream has the same problem in some cases: too many bug reports
On Thu, January 20, 2011 03:18, Paul Wise wrote:
> On Thu, Jan 20, 2011 at 10:59 AM, Brian May
> wrote:
>
>> What is policy when security updates for stable introduce new
>> regressions in software that weren't there before? Can these get fixed
>> in stable?
>
> If a stable security update contain
19 matches
Mail list logo
