Bug#672300: O: dumpasn1
Package: wnpp Severity: normal I don't use the package anymore, and don't have the will to maintain it, hence orphan it. It's a very low-maintainance package (a single .c file), though it requires a little knowledge about ASN.1 for some bugs. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120509202525.12349.25252.report...@apollon.madism.org
Bug#661881: O: xinetd
Package: wnpp Severity: normal Orphaning xinetd as I don't use it anymore nowadays -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120302082433.3543.4763.report...@apollon.madism.org
Bug#661880: O: proxsmtp
Package: wnpp Severity: normal -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120302082342.3437.60203.report...@apollon.madism.org
Bug#650830: O: tokyocabinet
Package: wnpp Severity: normal I don't use it anymore, and don't maintain it for a long time. It's in collab-maint (git). -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111203175229.14213.80246.report...@apollon.madism.org
Bug#596302: O: pdnsd
Package: wnpp Severity: normal Hi, I'm not using pdnsd anymore, but unbound, on my local machines, hence have lost interest in maintaining it for Debian. The current state of the packaging can be found on git://git.madism.org/packages/pdnsd.git -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100910073228.27008.21448.report...@apollon.madism.org
Bug#590527: ITP: mussh -- MUltihost SSH Wrapper
On Tue, Jul 27, 2010 at 12:46:16AM -0400, Holger Levsen wrote: > Hi Jacob, > > On Montag, 26. Juli 2010, Jacob Luna Lundberg wrote: > > * Package name: mussh > > > > Mussh is a shell script that allows you to execute a command > > or script over ssh on multiple hosts with one command. When > > possible mussh will use ssh-agent and RSA/DSA keys to minimize > > the need to enter your password more than once. > > how is that different to dsh, already present in Debian? Or clusterssh ? -- ·O· Pierre Habouzit ··Omadco...@debian.org OOOhttp://www.madism.org -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100728131459.gh6...@madism.org
Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems
On Thu, Jun 25, 2009 at 12:54:35AM +0200, Guus Sliepen wrote: > On Wed, Jun 24, 2009 at 06:33:44PM -0400, Bryan Donlan wrote: > > > >> Why would they use less memory? > > > > > > Since they don't link against a large library. Granted, that is only a > > > benefit > > > if all running programs link against libposix instead of glibc. > > > > What makes you think libposix will be smaller? It is currently very > > incomplete; by the time it reaches a full implementation of POSIX, it > > may well be the same size as libc. > > Glibc implements much more than just POSIX, and it is not known for its > leanness, hence the existence of dietlibc, uClibc, etc. Most of its fat comes from stuff like Sun RPC, or gconv, that thanks to eglibc you can switch off. I'm not saying libposix is a stupid idea, just that it's meaningless to package it in Debian (especially in its current state, but that's _really_ orthogonal). -- Intersec <http://www.intersec.com> Pierre Habouzit Tél : +33 (0)1 5570 3346 Mob : +33 (0)6 1636 8131 Fax : +33 (0)1 5570 3332 37 Rue Pierre Lhomme 92400 Courbevoie signature.asc Description: Digital signature
Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems
On Thu, Jun 25, 2009 at 12:41:43AM +0200, Pierre Habouzit wrote: > On Thu, Jun 25, 2009 at 12:24:40AM +0200, Guus Sliepen wrote: > > On Wed, Jun 24, 2009 at 05:47:16PM -0400, Steve Langasek wrote: > > > > > > Once libposix reaches maturity, I will certainly consider linking > > > > applications I wrote myself against libposix. Applications linked > > > > against > > > > it will probably use less memory > > > > > > Why would they use less memory? > > > > Since they don't link against a large library. > > Which is a ridiculous argument given what the S in .so means. As soon as > at least one always running program on your system uses glibc, you want > to only use glibc if you want to save memory. It's simple as that. PS: I read the full mail, and the postulate that all Debian can link against libposix is wrong to begin with, because too many GNU stuff heavily relies on GNU extensions to the libc. That's exactly why kFreeBSD uses a GNU libc instead of the BSD one -- Intersec <http://www.intersec.com> Pierre Habouzit Tél : +33 (0)1 5570 3346 Mob : +33 (0)6 1636 8131 Fax : +33 (0)1 5570 3332 37 Rue Pierre Lhomme 92400 Courbevoie signature.asc Description: Digital signature
Bug#534398: ITP: libposix -- unifed implementation of core functionality of all Unix systems
On Thu, Jun 25, 2009 at 12:24:40AM +0200, Guus Sliepen wrote: > On Wed, Jun 24, 2009 at 05:47:16PM -0400, Steve Langasek wrote: > > > > Once libposix reaches maturity, I will certainly consider linking > > > applications I wrote myself against libposix. Applications linked against > > > it will probably use less memory > > > > Why would they use less memory? > > Since they don't link against a large library. Which is a ridiculous argument given what the S in .so means. As soon as at least one always running program on your system uses glibc, you want to only use glibc if you want to save memory. It's simple as that. -- Intersec <http://www.intersec.com> Pierre Habouzit Tél : +33 (0)1 5570 3346 Mob : +33 (0)6 1636 8131 Fax : +33 (0)1 5570 3332 37 Rue Pierre Lhomme 92400 Courbevoie signature.asc Description: Digital signature
Bug#452186: O: dumpasn1 -- ASN.1 object dump program
On Sat, Jan 10, 2009 at 05:00:12PM +, Manfred Lichtenstern wrote: > retitle 452186 ITA: dumpasn1 -- ASN.1 object dump program > owner 452186 ! > thanks I've just hijacked that bug from you because I really need an up to date package, and that i saw nowhere a request from you for a sponsor. Feel free to hijack it from me again if you want to, I will gladly sponsor it. -- ·O· Pierre Habouzit ··Omadco...@debian.org OOOhttp://www.madism.org pgpMBIbpSEWA4.pgp Description: PGP signature
Bug#513305: ITP: unscd -- Micro Name Server Caching Daemon
On Fri, Jan 30, 2009 at 09:37:43PM +, Don Armstrong wrote: > On Fri, 30 Jan 2009, Pierre Habouzit wrote: > > I know it's a separate upstream, but it's a drop-in replacement, to > > the point where it can read /etc/nsdcd.conf, so my goal was to just > > drop nscd from the libc package at once and replace it with unscd. > > (replacing nscd with a transition package and all that). > > It's fine to have that transition plan, but unscd will still be a > separate source package; Sure > I'm planning on having it Replaces/Conflicts nscd. Fine then, the goal is that it can also Provide: nscd so that we're done with it for good. -- ·O· Pierre Habouzit ··Omadco...@debian.org OOOhttp://www.madism.org pgpnOq1LmmIQl.pgp Description: PGP signature
Bug#513305: ITP: unscd -- Micro Name Server Caching Daemon
On Fri, Jan 30, 2009 at 07:27:58PM +, Don Armstrong wrote: > On Fri, 30 Jan 2009, Pierre Habouzit wrote: > > On mer, jan 28, 2009 at 01:30:23 +, Don Armstrong wrote: > > > It should mostly be a drop-in replacement for existing installs > > > using nscd. > > > > For what it's worth, I'm thinking packaging it in place of the > > current nscd that is a real PoS with too many issues to list. We may > > decide to just drop nscd in favor of unscd at once, hence it would > > be easier if maintained from within the glibc team. > > It's fine with me if it ends up being maintained by the glibc team > eventually; I just need unscd now becauser nscd being so hideous is > causing me no end of grief. > > It is a separate upstream, though, so it should be separate from glibc > source-wise. I do plan on making it so that it can easily be installed > in place of nscd. I know it's a separate upstream, but it's a drop-in replacement, to the point where it can read /etc/nsdcd.conf, so my goal was to just drop nscd from the libc package at once and replace it with unscd. (replacing nscd with a transition package and all that). -- ·O· Pierre Habouzit ··Omadco...@debian.org OOOhttp://www.madism.org pgpOgABUdlMmp.pgp Description: PGP signature
Bug#513305: ITP: unscd -- Micro Name Server Caching Daemon
On mer, jan 28, 2009 at 01:30:23 +, Don Armstrong wrote: > Package: wnpp > Severity: wishlist > Owner: d...@debian.org > > * Package Name: unscd > * Version : 0.36 > * Upstream: Denys Vlasenko > * URL : http://busybox.net/~vda/unscd/ > * License : GPL-2 > > Description: Micro Name Service Caching Daemon > A daemon which handles passwd, group and host lookups for running > programs and caches the results for the next query. You only need > this package if you are using slow Name Services like LDAP, NIS or > NIS+. > . > This particular NSCD is a complete rewrite of the GNU glibc nscd > which is a single threaded server process which offloads all NSS > lookups to worker children; cache hits are handled by pthe parent, > and only cache misses start worker children, making the parent immune > to resource leaks, hangs, and crashes in NSS libraries. > . > It should mostly be a drop-in replacement for existing installs using > nscd. For what it's worth, I'm thinking packaging it in place of the current nscd that is a real PoS with too many issues to list. We may decide to just drop nscd in favor of unscd at once, hence it would be easier if maintained from within the glibc team. I was just waiting for lenny to be out first. -- ·O· Pierre Habouzit ··Omadco...@debian.org OOOhttp://www.madism.org pgpyal0MGMd2P.pgp Description: PGP signature
Bug#495221: O: ldapscripts -- Add and remove user and groups (stored in a ldap directory)
Package: wnpp On Sun, Aug 10, 2008 at 07:21:23PM +, Adam Sommer wrote: > Hello, > > I noticed from the package that you are the Debian ldapscripts maintainer, > and Ganaël mentioned that he's worked with you in the past. Anyway, I just > wanted to let you know that there's a new release [1]. This release has > quite a few changes, but I think that packaging shouldn't be too bad. > > Thanks for packaging ldapscritps. > > http://sourceforge.net/projects/ldapscripts/?abmode=1 I'm not really interested in ldapscripts anymore actually as I don't use it nowadays anymore. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpIITZ5PMYBx.pgp Description: PGP signature
Bug#482277: ITP: unbound -- validating, recursive, caching DNS resolver
On Thu, May 22, 2008 at 04:03:14PM +, Robert Edmonds wrote:
> hi,
>
> Pierre Habouzit wrote:
> > On Wed, May 21, 2008 at 02:58:04PM +, Robert Edmonds wrote:
> > > Package: wnpp
> > > Owner: "Robert S. Edmonds" <[EMAIL PROTECTED]>
> > > Severity: wishlist
> > >
> > > * Package name: unbound
> > > Version : 1.0.0
> > > Upstream Author : NLnet Labs
> > > * URL : http://libev.schmorp.de/
>
> whoops, looks like I fat fingered the URL when copying from a previous
> ITP. that should be http://unbound.net/ of course.
>
> > > * License : BSD
> > > Programming Lang: C
> > > Description : validating, recursive, caching DNS resolver
> > >
> > > Unbound is a validating, recursive, and caching DNS resolver.
> > > .
> > > The C implementation of Unbound is developed and maintained by NLnet
> > > Labs. It is based on ideas and algorithms taken from a java prototype
> > > developed by Verisign labs, Nominet, Kirei and ep.net.
> > > .
> > > Unbound is designed as a set of modular components, so that also DNSSEC
> > > (secure DNS) validation and stub-resolvers (that do not run as a
> > > server, but are linked into an application) are easily possible.
> >
> > Err I missed that and I happened to just file the same ITP. I'm
> > already packaging nsd3 from the same authors FWIW, and am really
> > interested into {co-,}maintaining unbound.
>
> well, I've written a bit of research-quality DNS code (including some
> that uses ldns, very nice library) and run a few production recursive /
> authoritative DNS servers; I don't think a package team is necessary for
> unbound.
okay then.
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgplSfT23GLPI.pgp
Description: PGP signature
Bug#482277: ITP: unbound -- validating, recursive, caching DNS resolver
On Wed, May 21, 2008 at 02:58:04PM +, Robert Edmonds wrote:
> Package: wnpp
> Owner: "Robert S. Edmonds" <[EMAIL PROTECTED]>
> Severity: wishlist
>
> * Package name: unbound
> Version : 1.0.0
> Upstream Author : NLnet Labs
> * URL : http://libev.schmorp.de/
> * License : BSD
> Programming Lang: C
> Description : validating, recursive, caching DNS resolver
>
> Unbound is a validating, recursive, and caching DNS resolver.
> .
> The C implementation of Unbound is developed and maintained by NLnet
> Labs. It is based on ideas and algorithms taken from a java prototype
> developed by Verisign labs, Nominet, Kirei and ep.net.
> .
> Unbound is designed as a set of modular components, so that also DNSSEC
> (secure DNS) validation and stub-resolvers (that do not run as a
> server, but are linked into an application) are easily possible.
>
> --
> Robert Edmonds
> [EMAIL PROTECTED]
Err I missed that and I happened to just file the same ITP. I'm
already packaging nsd3 from the same authors FWIW, and am really
interested into {co-,}maintaining unbound.
Cheers,
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpDG5gxKRAQ6.pgp
Description: PGP signature
Bug#482390: ITP: unbound -- Validating, recursive, and caching DNS resolver.
Package: wnpp Severity: wishlist Owner: Pierre Habouzit <[EMAIL PROTECTED]> * Package name: unbound Version : 1.0.0 Upstream Author : NLnet Labs <http://www.nlnetlabs.nl/> * URL : http://unbound.net/ * License : BSD Programming Lang: (C, C++, C#, Perl, Python, etc.) Description : Validating, recursive, and caching DNS resolver. Unbound is designed as a set of modular components, so that also DNSSEC (secure DNS) validation and stub-resolvers (that do not run as a server, but are linked into an application) are easily possible. Note: this is _NOT_ the final description that will be used in the packaging, no need to answer to tell me it sucks, I'm aware of it :) I merely cut&pasted one § of the upstream homepage. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#459325: ITP: clang -- A C language family frontend for LLVM
On Sat, Jan 05, 2008 at 03:21:43PM +, Y Giridhar Appaji Nag wrote: > Package: wnpp > Severity: wishlist > Owner: Y Giridhar Appaji Nag <[EMAIL PROTECTED]> > > * Package name: clang > Version : 2.2svn > Upstream Author : Chris Lattner <[EMAIL PROTECTED]> > * URL : http://clang.llvm.org/ > * License : University of Illinois/NCSA Open Source License > Programming Lang: C/C++ > Description : A C language family frontend for LLVM > > The Clang project is a new C, C++, Objective C and Objective C++ > front-end for the LLVM compiler. The end-user features of clang are > fast compiles and low memory use, expressive diagnostics, and GCC > compatibility. It has a modular library based architecture, supports > diverse clients (refactoring, static analysis, code generation, etc.) > and allows tight integration with IDEs. Internally, clang has a single > unified parser for C, Objective C, C++, and Objective C++. > .. > Clang is still in early development stages and good for source analysis > or source-to-source transformation tools. It is not yet ready for use > as a drop in C compiler. It currently has pretty good parsing and > semantic analysis support for C and Objective-C. C++ support is still > very early. And while we're at it, it'd be great to have a pkg-llvm group on alioth where we could package llvm(-gcc), clang, and other llvm derivatives, especially given how llvm is built for now (with almost only static libraries, making it quite a nightmare for upgrades) -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpqnfQIsZ2i9.pgp Description: PGP signature
Bug#459325: ITP: clang -- A C language family frontend for LLVM
On Sat, Jan 05, 2008 at 03:21:43PM +, Y Giridhar Appaji Nag wrote: > Package: wnpp > Severity: wishlist > Owner: Y Giridhar Appaji Nag <[EMAIL PROTECTED]> > > * Package name: clang > Version : 2.2svn > Upstream Author : Chris Lattner <[EMAIL PROTECTED]> > * URL : http://clang.llvm.org/ > * License : University of Illinois/NCSA Open Source License > Programming Lang: C/C++ > Description : A C language family frontend for LLVM > > The Clang project is a new C, C++, Objective C and Objective C++ > front-end for the LLVM compiler. The end-user features of clang are > fast compiles and low memory use, expressive diagnostics, and GCC > compatibility. It has a modular library based architecture, supports > diverse clients (refactoring, static analysis, code generation, etc.) > and allows tight integration with IDEs. Internally, clang has a single > unified parser for C, Objective C, C++, and Objective C++. > .. > Clang is still in early development stages and good for source analysis > or source-to-source transformation tools. It is not yet ready for use > as a drop in C compiler. It currently has pretty good parsing and > semantic analysis support for C and Objective-C. C++ support is still > very early. Note that clang requires llvm 2.1 to build, which isn't in Debian yet. I've Cc-ed the owner of the ITA of the current package (that is only from 1.8 right now). -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpb2HLRv0OJO.pgp Description: PGP signature
Bug#456599: ITP: dvtm -- Tiling window management for the console
On Tue, Dec 18, 2007 at 10:24:39AM +, Marc Andre Tanner wrote: > Pierre Habouzit wrote: > >On dim, déc 16, 2007 at 09:19:54 +, Albin Tonnerre wrote: > >>Package: wnpp > >>Severity: wishlist > >>Owner: Albin Tonnerre <[EMAIL PROTECTED]> > >> > >> > >>* Package name: dvtm > >> Version : 0.01 > >> Upstream Author : Anselm R. Garbe, Marc Andre Tanner > >>* URL : http://www.brain-dump.org/projects/dvtm/ > >>* License : MIT/X > >> Programming Lang: C > >> Description : Tiling window management for the console > >> > >> dvtm brings the concept of tiling window management, popularized by > >> X11-window managers like dwm to the console. As a console window > >> manager it tries to make it easy to work with multiple console based > >> programs like vim mutt, cmus or irssi. > > Note that librote doesn't support utf-8 at all, which is kind of > >backwards nowadays. librote isn't very fixeable in that regard btw. Note > >that this breakage is _obvious_ on the upstream's screenshots. > > Hi, > > I am the upstream author of dvtm. I have recently merged a patch which > adds utf8 support to librote. My current development tree can be found > at: > > http://repo.or.cz/w/librote.git > > > Though they could base their work on > >http://git.madism.org/?p=madtty.git that is a rework of librote I did, > >and that does support utf-8 [though it misses some uncommited changes to > >work great]. This is the base of code that I used to do that: > >http://blog.madism.org/index.php/2007/11/10/141 > > What would be the advantage i get by switching to your code? Well if recent rote support multi byte encodings and have fixed their handling of colors for rote launched inside rote, probably not a lot. I think I understand a different set of escape sequences though, as I chose 'rxvt' as a terminal to emulate, which has a nice _short_ list of capabilities, so that it's even less likely that applications that I host would send me escape sequences I don't get. I think rote uses 'screen' by default, and this is a bad choice (like xterm would be) because applications assert a _lot_ of things when $TERM has this value. Oh and I support terminal resizing, which last time I checked rote didn't. And for a tiling WM, that helps a lot ;) -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpzcB0ktcntT.pgp Description: PGP signature
Bug#456599: ITP: dvtm -- Tiling window management for the console
On dim, déc 16, 2007 at 09:19:54 +, Albin Tonnerre wrote: > Package: wnpp > Severity: wishlist > Owner: Albin Tonnerre <[EMAIL PROTECTED]> > > > * Package name: dvtm > Version : 0.01 > Upstream Author : Anselm R. Garbe, Marc Andre Tanner > * URL : http://www.brain-dump.org/projects/dvtm/ > * License : MIT/X > Programming Lang: C > Description : Tiling window management for the console > > dvtm brings the concept of tiling window management, popularized by > X11-window managers like dwm to the console. As a console window > manager it tries to make it easy to work with multiple console based > programs like vim mutt, cmus or irssi. Note that librote doesn't support utf-8 at all, which is kind of backwards nowadays. librote isn't very fixeable in that regard btw. Note that this breakage is _obvious_ on the upstream's screenshots. Though they could base their work on http://git.madism.org/?p=madtty.git that is a rework of librote I did, and that does support utf-8 [though it misses some uncommited changes to work great]. This is the base of code that I used to do that: http://blog.madism.org/index.php/2007/11/10/141 It supports utf-8, gets colors right[0] (you cannot launch rote applications in rote applications, colors are wrong). Though the API is quite unlike rote, and not documented. And given the triviality of the reworked code, I'm unsure this warants being a shared library btw. [0] though there are some ongoing patches to fix this properly, it works well on dark backgrounds only for now. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgp2VqXkzB0Ud.pgp Description: PGP signature
Bug#452903: ITP: gamine -- an interactive game for young children
On Mon, Nov 26, 2007 at 10:22:33AM +, Gonéri Le Bouder wrote: > On Mon, Nov 26, 2007 at 01:07:21AM +0100, Pierre Habouzit wrote: > > On Sun, Nov 25, 2007 at 11:53:57PM +, Gonéri Le Bouder wrote: > > > Package: wnpp > > > Severity: wishlist > > > Owner: "Gonéri Le Bouder" <[EMAIL PROTECTED]> > > > > > * License : DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE > > > [...] game designed for 2 years old children [...] > > > > hah, some upstreams have a marvellous sense of humor it seems :) > Yes, like a famous DPL. heh, I absolutely don't mind, 2yo children won't read the license anyways, but still, this is kind of fun :) -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpDqBCQWrmmt.pgp Description: PGP signature
Bug#452903: ITP: gamine -- an interactive game for young children
On Sun, Nov 25, 2007 at 11:53:57PM +, Gonéri Le Bouder wrote: > Package: wnpp > Severity: wishlist > Owner: "Gonéri Le Bouder" <[EMAIL PROTECTED]> > * License : DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE > [...] game designed for 2 years old children [...] hah, some upstreams have a marvellous sense of humor it seems :) -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgprgBXiWvaop.pgp Description: PGP signature
Bug#452699: O: dcc
Package: wnpp Severity: normal I clearly lack the motivation for a proper maintenance of this package since I don't use it anywhere anymore. So let's orphan it so that this fact isn't hidden. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#452073: ITP: tokyo-cabinet -- Tokyo Cabinet Database format [successor of QDBM]
On Tue, Nov 20, 2007 at 03:17:41PM +, Ron Johnson wrote: > On 11/20/07 03:00, Pierre Habouzit wrote: > > Package: wnpp > > Severity: wishlist > > Owner: Pierre Habouzit <[EMAIL PROTECTED]> > > > > * Package name: tokyo-cabinet > > Version : 1.0.6 > > Upstream Author : Mikio Hirabayashi <[EMAIL PROTECTED]> > > * URL : http://tokyocabinet.sourceforge.net/ > > * License : LGPL > > Programming Lang: C (with perl, ruby and java bindings) > > Description : Tokyo Cabinet Database format [successor of QDBM] > >Tokyo Cabinet is a library of routines for managing a database. The > >database is a simple data file containing records, each is a pair of > >a key and a value. Every key and value is serial bytes with variable > >length. Both binary data and character string can be used as a key > >and a value. There is neither concept of data tables nor data types. > >Records are organized in hash table or B+ tree. > >. > >This library is presented as the successor of QDBM from the same > >author. > > Should the source package create separate bindings packages for each > language? That's standard, isn't it? 1) It's an ITP so it describes the _source_ package, not the split I'll obviously perform. 2) it happens that unlike qdbm the bindings are separated upstream, and as I've absolutely no interest in the bindings but only in the C library I won't package them after all. FWIW it's already in new, and there is 5 binary packages: * the lib, * the -dev package, * the -dbg package, * the -doc package, * the -bin package with the tools to load/dump/... tokyocabinet databases. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpAXyqPlJVBy.pgp Description: PGP signature
Bug#452073: ITP: tokyo-cabinet -- Tokyo Cabinet Database format [successor of QDBM]
Package: wnpp Severity: wishlist Owner: Pierre Habouzit <[EMAIL PROTECTED]> * Package name: tokyo-cabinet Version : 1.0.6 Upstream Author : Mikio Hirabayashi <[EMAIL PROTECTED]> * URL : http://tokyocabinet.sourceforge.net/ * License : LGPL Programming Lang: C (with perl, ruby and java bindings) Description : Tokyo Cabinet Database format [successor of QDBM] Tokyo Cabinet is a library of routines for managing a database. The database is a simple data file containing records, each is a pair of a key and a value. Every key and value is serial bytes with variable length. Both binary data and character string can be used as a key and a value. There is neither concept of data tables nor data types. Records are organized in hash table or B+ tree. . This library is presented as the successor of QDBM from the same author. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#451106: ITP: llvm2 -- Low-Level Virtual Machine (LLVM) compiler for C/C++
On Wed, Nov 14, 2007 at 02:56:00PM +, Al Stone wrote: > Arthur, > > It seems sort of overkill to do a whole new ITP for LLVM. If you're > interested, you could take over the maintenance of the existing > LLVM packages, perhaps even put them into team maintenance. I haven't > had the time need to maintain the packages, and haven't put it up for > adoption yet, mostly because no one else has come forward as willing > to do the work... OTOH llvm 2.x is not backward compatible with the 1.x series, and comes some brand new tools, meaning that such a package will go through NEW and stuff like that anyways. It _is_ a brand new package on many aspects. It's unclear to me if llvm should continue to exist in the archive or not, but I disagree with the fact that an ITP is an overkill. Cheers, -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpkWBWNJAT8b.pgp Description: PGP signature
Bug#445866: ITP: perforce -- closed source revision control system
On Mon, Oct 08, 2007 at 09:32:23PM +, Florian Weimer wrote: > * Pierre Habouzit: > >> I think making it easier to use Debian with them is > >> within the mandate for non-free. > > > > There is ways to interact with perforce in debian, in a free way: > > git-p4 being one of them. > | * The import does not require anything from the Perforce client view as > | it just uses > | "p4 print //depot/path/file#revision" to get the actual file contents. > > Seems to me that this depends on Perforce. D'oh. heh okay :) > (I don't know anything about Perforce. Perhaps it's really dangerous > software. But perhaps it's just non-free.) OTOH I'm always reluctant to see new things enter non-free when there is perfectly suitable alternatives. I mean git, hg, bzr, or even the horrible svn can do what p4 does, or even way better. But I understand that you don't always chose the tools you have to use at work. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpzQ4mVAf1k5.pgp Description: PGP signature
Bug#445866: ITP: perforce -- closed source revision control system
On Mon, Oct 08, 2007 at 07:52:55PM +, Daniel Jacobowitz wrote: > On Mon, Oct 08, 2007 at 03:41:21PM -0400, Roberto C. S?nchez wrote: > > Given the great abundance of revision control systems already packaged > > for Debian, what is the point of adding another? Especially when it is > > non-free. > > How about "people use it"? There's plenty of installations of > perforce; s/perforce/windows/ and the sentence is still true ;) > I think making it easier to use Debian with them is > within the mandate for non-free. There is ways to interact with perforce in debian, in a free way: git-p4 being one of them. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgp3gEjUKOuoU.pgp Description: PGP signature
Bug#445843: O: php-memcache
Package: wnpp Severity: normal I don't use php-memcache anymore, hence I'm orphaning it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#438753: ITP: md5deep -- Recursing file hash calculator
On Sun, Aug 19, 2007 at 03:18:24PM +, Giovanni Mascellani wrote:
>Package name: md5deep
> Version: 1.13
> Upstream Author: Jesse Kornblum
> URL: http://md5deep.sourceforge.net/
> License: Public domain and others
> Description: Recursing file hash calculator
> This utility is similar to the famous md5sum, but has the ability to
> recurse into subdirectories when calculating hashes for many files. It
> is not limited to the MD5 algorithm, but can also calculate SHA1,
> SHA256, Tiger and Whirpool hashes.
You mean like find . [options] -exec md5sum \{} \; > sums ?
Or like md5sums **/* (if using zsh) ?
Is there a point in packaging such trivial things ?
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpfBYyq6jypp.pgp
Description: PGP signature
Bug#401575: [pkg-lighttpd] lighttpd RFH
On Sat, Jul 21, 2007 at 12:15:55AM +0200, Pierre Habouzit wrote: > FWIW I'd like to step up as a lighttpd co-maintainer. I've requested > membership on alioth already. Hello someone ? -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgp5B0b4ASkca.pgp Description: PGP signature
Bug#434206: ITP: moe -- powerful text editor for ISO-8859 and ASCII character encodings
On Sun, Jul 22, 2007 at 04:22:41PM +0530, Kumar Appaiah wrote: > Description : powerful text editor for ISO-8859 and ASCII character > encodings What is the point of packaging new editors that do not support current Debian default's encoding (namely utf-8) ? -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpA8LC7Rf8kg.pgp Description: PGP signature
Bug#401575: lighttpd RFH
FWIW I'd like to step up as a lighttpd co-maintainer. I've requested membership on alioth already. Cheers, -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpccTYwjPT3B.pgp Description: PGP signature
Bug#430335: ITP: nsd3 -- authoritative name domain server
On Sun, Jun 24, 2007 at 12:35:25PM +0200, Thijs Kinkhorst wrote: > Hi Pierre, > > On Saturday 23 June 2007 15:57, Pierre Habouzit wrote: > > * Package name: nsd3 > > >NSD3 is an fast, authoritative only, high performance, simple > >and open source name server. > > Good that you want to work on this. Did you coordinate this with the > maintainer of the current nsd package, Ondřej Surý? He told me in #406978 > that he plans to package it. Yes, I contacted him, he promised me an answer in the week, ... 3 weeks ago. He is welcomed to be a co-maintainer if he wants this. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpnbvAVUp78x.pgp Description: PGP signature
Bug#430335: ITP: nsd3 -- authoritative name domain server
On Sat, Jun 23, 2007 at 04:43:22PM +0200, Andreas Barth wrote: > * Pierre Habouzit ([EMAIL PROTECTED]) [070623 16:33]: > > * Package name: nsd3 > > Version : x.y.z > > Upstream Author : NLnet Labs > > * URL : http://www.nlnetlabs.nl/nsd/ > > * License : Mostly BSD with some bits in GPLv2 > > Programming Lang: C > > Description : authoritative name domain server > >NSD3 is an fast, authoritative only, high performance, simple > >and open source name server. > >. > >NSD was primarily developed by NLnet Labs on request from and close > >cooperation with RIPE NCC, as an alternative name server software to be > >run on the root name server RIPE NCC operates. > > Why not upgrade the nsd-package? because the configuration is not backward compatible, and that nsd 2.x branch is still supported upstream. There is no upgrade path between nsd2 and nsd3. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpTGJ3APLlsx.pgp Description: PGP signature
Bug#430335: ITP: nsd3 -- authoritative name domain server
Package: wnpp Severity: wishlist Owner: Pierre Habouzit <[EMAIL PROTECTED]> * Package name: nsd3 Version : x.y.z Upstream Author : NLnet Labs * URL : http://www.nlnetlabs.nl/nsd/ * License : Mostly BSD with some bits in GPLv2 Programming Lang: C Description : authoritative name domain server NSD3 is an fast, authoritative only, high performance, simple and open source name server. . NSD was primarily developed by NLnet Labs on request from and close cooperation with RIPE NCC, as an alternative name server software to be run on the root name server RIPE NCC operates. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403770: ITP: context -- A powerful TeX format
On Tue, Dec 19, 2006 at 07:08:45PM +0100, Norbert Preining wrote: > Hi Frank! > > On Die, 19 Dez 2006, Frank Küster wrote: > > > * Package name: context > > > > Fine :-) > > It is time to get it into Debian I think. It was clear that it wont go > into etch, but I want to see proper context support in lenny, and > neither texlive upstream nor tetex has this. > > Not that I care for ConTeXt, I am not a context user, but I want to have > everything TeX related more or less up2date. > > > > Use ConTeXt to create simple documents and complex layouts. > > > > To me this long description sounds too much like marketing blurb and has > > little information content. The most important question that it should > > answer is "what's the difference to the more known LaTeX?" > > You are heartly invited to write something better, it is all in our svn > repository. I am quite bad in writing stupid texts (better in writing > math) and I just copied the text from the website/description/doc. technically that's hard to do when you don't know it yet ;) the fact that the upstream's website is poorly worded is not a very good excuse. I've read the .pdf manual, and to me it's still unclear why context should be better than the good old latex distro ;) PS: you made a mistake the web site is .nl and not .com -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpIUHkMTwcV7.pgp Description: PGP signature
Bug#387926: ITP: eaccelerator -- PHP opcode cacher and compilation optimizer
Le dim 17 septembre 2006 19:57, Pierre Habouzit a écrit : > Le dim 17 septembre 2006 19:35, Roberto C. Sanchez a écrit : > > On Sun, Sep 17, 2006 at 06:07:57PM +0200, Pierre Habouzit wrote: > > > Le dim 17 septembre 2006 16:11, Pierre Habouzit a écrit : > > > > Upstream Author : Name <[EMAIL PROTECTED]> > > > > > > bah stupid template... > > > > > > reportbug should barf when such things are forgotten :| > > > > > > anyway the package is in NEW, and debian/copyright is ok > > > > Have you checked out these threads? > > > > http://lists.debian.org/debian-devel/2005/05/msg00681.html > > http://lists.debian.org/debian-mentors/2005/05/msg00148.html > > http://lists.debian.org/debian-mentors/2005/09/msg00440.html > > http://lists.debian.org/debian-legal/2004/11/msg00078.html > > http://lists.debian.org/debian-legal/2005/01/msg00130.html > > > > Basically, I tried to package this more than a year ago and was > > basically not able to finish. So, unless the legal issues have > > been resolved, this package will likely not be possible. The root > > of the problem is that the GPL is not compatible with the PHP > > license. There is no way around it, other than a clean rewrite of > > eacclerator by people who have not seen the mmchache-derived code. > > hmm, right. the thing is, the code has been rewriten for the most > part of it, so they are not tied with the turck-mmcache copyright > holders anymore (afaict). so maybe it's possible to discuss it with > upstream. here is the link that explains that: http://archive.eaccelerator.net/OldNews and that has been achieved since, if I'm correct. so if this is just a matter of exception to be done to the GPL, I'm really sure we can work on it nicely. > so basically, what has to be done? they must just explain that they > allow anyone to build their GPL software against php, is that it ? > > the situations changed in the sense that we are not tied because of > the past anymore. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpql1HMyAgAP.pgp Description: PGP signature
Bug#387926: ITP: eaccelerator -- PHP opcode cacher and compilation optimizer
Le dim 17 septembre 2006 19:35, Roberto C. Sanchez a écrit : > On Sun, Sep 17, 2006 at 06:07:57PM +0200, Pierre Habouzit wrote: > > Le dim 17 septembre 2006 16:11, Pierre Habouzit a écrit : > > > Upstream Author : Name <[EMAIL PROTECTED]> > > > > bah stupid template... > > > > reportbug should barf when such things are forgotten :| > > > > anyway the package is in NEW, and debian/copyright is ok > > Have you checked out these threads? > > http://lists.debian.org/debian-devel/2005/05/msg00681.html > http://lists.debian.org/debian-mentors/2005/05/msg00148.html > http://lists.debian.org/debian-mentors/2005/09/msg00440.html > http://lists.debian.org/debian-legal/2004/11/msg00078.html > http://lists.debian.org/debian-legal/2005/01/msg00130.html > > Basically, I tried to package this more than a year ago and was > basically not able to finish. So, unless the legal issues have been > resolved, this package will likely not be possible. The root of the > problem is that the GPL is not compatible with the PHP license. > There is no way around it, other than a clean rewrite of eacclerator > by people who have not seen the mmchache-derived code. hmm, right. the thing is, the code has been rewriten for the most part of it, so they are not tied with the turck-mmcache copyright holders anymore (afaict). so maybe it's possible to discuss it with upstream. so basically, what has to be done? they must just explain that they allow anyone to build their GPL software against php, is that it ? the situations changed in the sense that we are not tied because of the past anymore. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpOb7SZEW5es.pgp Description: PGP signature
Bug#387926: ITP: eaccelerator -- PHP opcode cacher and compilation optimizer
Le dim 17 septembre 2006 16:11, Pierre Habouzit a écrit : > Upstream Author : Name <[EMAIL PROTECTED]> bah stupid template... reportbug should barf when such things are forgotten :| anyway the package is in NEW, and debian/copyright is ok -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpVUFgu7QGc8.pgp Description: PGP signature
Bug#387926: ITP: eaccelerator -- PHP opcode cacher and compilation optimizer
Package: wnpp Severity: wishlist Owner: Pierre Habouzit <[EMAIL PROTECTED]> * Package name: eaccelerator Version : 0.9.5~rc1 Upstream Author : Name <[EMAIL PROTECTED]> * URL : http://www.eaccelerator.net/ * License : GPL V2 Programming Lang: C Description : PHP opcode cacher and compilation optimizer eAccelerator is a free open-source PHP accelerator, optimizer, encoder and dynamic content cache. It increases the performance of PHP scripts by caching them in their compiled state, so that the overhead of compiling is almost completely eliminated. It also optimizes scripts to speed up their execution. eAccelerator typically reduces server load and increases the speed of your PHP code by 1-10 times. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#274732: RFA: messagewall -- An SMTP proxy daemon, designed to help keep out unwanted email
retitle 274732 O: messagewall -- An SMTP proxy daemon, designed to help keep out unwanted email thanks with the old maintainer permission. a QA upload will follow soon. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org signature.asc Description: Digital signature
Bug#366618: ITP: cdck -- A simple program to verify CD/DVD quality
merge 366618 366554 thanks Le Mar 9 Mai 2006 23:50, Sandro Tosi a écrit : > Package: wnpp > Severity: wishlist > Owner: Sandro Tosi <[EMAIL PROTECTED]> > > * Package name: cdck > Version : 0.5.2 > Upstream Author : Alexey Semenoff <[EMAIL PROTECTED]> > * URL : http://www.example.org/ > * License : GPL > Description : A simple program to verify CD/DVD quality > > Actually cdck is a simple program to verify CD/DVD quality. The > known fact is that even if all files on the disc are readable, some > sectors having bad timing can easily turn into unreadable ones in the > future. . > To get an idea about disc cdck reads it sector by sector, keeping > all reading timings and then tells you its verdict. Optionally it > can write timing table into text file usable by gnuplot(1) > program, so you can draw some graphs out of it. > . > http://swaj.net/unix/#cdck > > -- System Information: > Debian Release: 3.1 > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.15-1-686-smp > Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpG5QSpB4naA.pgp Description: PGP signature
Bug#366328: ITP: bsp -- nodes builder for doom-engine levels
Le Dim 7 Mai 2006 15:07, Jon Dowland a écrit : > Package: wnpp > Severity: wishlist > Owner: Jon Dowland <[EMAIL PROTECTED]> > > * Package name: bsp given that the upstream name seems to be doombsp, and that bsp is a common tla: Bug Squash Party, Binary Space Partition, ... it seems more adequate to name it doomdsp to avoid namespace clashes. > Version : 5.1 > Upstream Author : Colin Phipps > * URL : http://doombsp.sourceforge.net/ > * License : GPL > Description : nodes builder for doom-engine levels > > BSP is a tool for calculating the Binary Space Partition > (BSP) for doom-engine levels. The result is stored in the > NODES lump for the level. Levels need a NODES lump in order > to be playable. > . > BSP also exploits some corner-cases of the doom rendering > engine to provide special effects such as transparent doors. > > -- System Information: > Debian Release: 3.1 > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: i386 (i686) > Kernel: Linux 2.6.17-rc3-jmtd6 > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpuNQ23BnXhS.pgp Description: PGP signature
Bug#353117: ITP: libphp-xajax -- A PHP library to develop Ajax applications
Le Jeu 16 Février 2006 11:21, David Gil a écrit : > Package: wnpp > Severity: wishlist > Owner: David Gil <[EMAIL PROTECTED]> > > * Package name : libphp-xajax should be : php-xajax. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpcIwJXzLjaz.pgp Description: PGP signature
Bug#348728: ITP: php-net-imap -- PHP PEAR module implementing IMAP protocol
Le Mer 18 Janvier 2006 20:58, Steffen Joeris a écrit : > > You should be aware that per the current REJECT_FAQ [1] > > your package will be automatically rejected because it uses the PHP > > License. Several weeks ago I emailed the FTP Masters[2], requesting > > that they accept the PHP Licence for all PHP Group software, backed > > up by extensive debian-legal discussion. They were explicitely > > invited to either modify their rejection criteria, or continue the > > debian-legal debate, both of which they have failed to do. I am now > > re-extending that invitation. > > > > Charles > > > >1. http://ftp-master.debian.org/REJECT-FAQ.html > >2. http://lists.debian.org/debian-legal/2006/01/msg00066.html > > Hi > > Thanks for the information. I haven't noticed it before because I saw > various packages in Debian using the PHP license. > I told my sponsor to wait with the upload. I will ask him for upload > when PHP license is DFSG compatible or tell him to drop it if the > project disagree with the PHP license. Nevertheless i think the > project should make a decision. Waiting for it now ... > > Greetings and thanks for info > Steffen the project decision is clear IMHO : read the php license, you'll see it can only apply to the main and official PHP distribution. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpC6b2cwqADP.pgp Description: PGP signature
Bug#333805: ITP: php-json-ext -- json serialiser for PHP4/5
On Fri, Oct 14, 2005 at 12:13:45AM +0200, Piotr Roszatycki wrote: > > * Package name: php-json-ext > > Why php-json-ext instead of simply php-json? just to match upstream source package name. binary packages are php4/5-json of course -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org signature.asc Description: Digital signature
Bug#333805: ITP: php-json-ext -- json serialiser for PHP4/5
Package: wnpp Severity: wishlist Owner: Pierre Habouzit <[EMAIL PROTECTED]> * Package name: php-json-ext Version : 1.0.7 Upstream Author : Omar Kilani <[EMAIL PROTECTED]> * URL : http://www.aurore.net/projects/php-json/ * License : LGPL Description : json serialiser for PHP4/5 php-json is an extremely fast PHP C extension for JSON (JavaScript Object Notation) serialisation. . documentation on the website: http://www.aurore.net/projects/php-json/ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.13.4 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#324296: ITP: ldapscripts -- Add and remove user and groups stored (using ldap)
Package: reportbug Version: 3.15 Severity: important Le Dim 21 Août 2005 17:02, Benjamin Seidenberg a écrit : > Pierre Habouzit wrote: > > owner 324296 [EMAIL PROTECTED] submitter 324296 > > [EMAIL PROTECTED] thanks > > > > damned, why don't reportbug honour DEBEMAIL ? > > Had same issue, check your ~/.reportbugrc, it sets variables in that > file when you first run it. DEBBUGEMAIL will override it (or you can > just change the file). I had 2 people jump on me from debian-devel, > even though I had already fixed it. :-) I consider it a bug, an important one even. Reportbug never asked me for any information except the "experience" level I had, so if it was able to guess my information once, it should *NOT* store it. Such an information can change, and the user won't know that static settings have been set, and when he changes EMAIL, he won't receive mails from the maintainers back. Reportbug should : * either get EMAIL/DEBEMAIL/DEBBUGSEMAIL/... each time it is run * or ask the user to give such information (and then store it, since the user *KNOW* reportbug asked it to him) This bug really is important because it can result in a permanent lost communication between a reporter and a package maintainer. btw, I've not checked the reportbug man page, if such a behaviour is documented or not, but even if it is, since no "normal" user would ever need to read this manpage, such a behaviour still remains hidden, and thus is IMHO a bug. So *even* adding a note about such a behaviour in the manpage (or elsewhere) is not sufficient. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpAWjghAAHQF.pgp Description: PGP signature
Bug#324296: ITP: ldapscripts -- Add and remove user and groups stored (using ldap)
owner 324296 [EMAIL PROTECTED] submitter 324296 [EMAIL PROTECTED] thanks damned, why don't reportbug honour DEBEMAIL ? -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpjipk9zrBuR.pgp Description: PGP signature
Bug#324296: ITP: ldapscripts -- Add and remove user and groups stored (using ldap)
Package: wnpp Severity: wishlist Owner: Pierre Habouzit <[EMAIL PROTECTED]> * Package name: ldapscripts Version : 1.2 Upstream Author : Ganaël LAPLANCHE <[EMAIL PROTECTED]> * URL : http://contribs.martymac.com/ * License : GPL Description : Add and remove user and groups stored (using ldap) Ldapscripts are shell scripts that allow to manage POSIX accounts (users, groups, machines) on an LDAP directory. They are similar to smbldap-tools but are written in shellscript, not in PERL. They only require OpenLDAP client commands (ldapadd, ldapdelete, ldapsearch, ldapmodify, slappasswd) and make administrator's work a lot easier avoiding him to configure PERL and each library dependencies (e.g. Net::LDAP). These scripts are very simple to configure by not requiring any Samba-related information (SID, profiles, homes, ...) : management of Samba attributes is entirely done by standard commands (net, smbpasswd et pdbedit) used together with the scripts. Moreover, most of the configuration is guessed from the one of libpam-ldap, and everything should work out from the box for most users. The scripts may be used independently - within command lines - or automatically by Samba (like smbldap-tools), to handle POSIX information within accounts before adding Samba information.
Bug#323855: ITP: opencvs -- OpenBSD CVS implementation with special emphasis in security
Le Ven 19 Août 2005 11:36, Javier Fernández-Sanguino Peña a écrit : > Also notice that some of our services (web pages, documentation > project) use CVS and will do so for a long time. Having a CVS server > available to switch to if a security issue in the current standard > CVS server is found is something that would be useful to prevent > downtime of those services if the debian admins have to switch them > off. > > I say go for it. seconded. moreover, there is a lot of *nix users that uses CVS because they don't want to use anything else (whatever the good or bad reasons are) and that impose to their sysadmin to secure the CVS server ... if we can make that task easier, let's do it. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpw9rvNtQ435.pgp Description: PGP signature
Bug#320844: RFP: mbuni -- Multimedia Messaging Service Gateway
On Mon, Aug 01, 2005 at 09:55:49PM +, W. Borgert wrote: > Package: wnpp > Severity: wishlist > > Package name: mbuni > Version : 1.0.0 > Upstream Author : Digital Solutions Ltd. > URL : http://www.mbuni.org/ > License : GPL > Description : Multimedia Messaging Service Gateway > > >>From the web page: > > " Mbuni is a fully-fledged Open Source MMS gateway (MMSC) > suitable for operators and MMS VAS providers." > > Seems to conform to ETSI standard TS 123 140. > > MMS - Multimedia Messaging Service > MMSC - Multimedia Messaging Service Centre > VAS - Value Added Service Note for the guy / girl that will package mbuni : * mbuni require a patched kannel, I don't know if it impacts the functionnalities of mainstream kannel, so some coordination with the maintainer of kannel (Paul Dwerryhouse <[EMAIL PROTECTED]>) * mbuni seems to rely on and AMR encoder/decoder, and the only one hinted by the upstream is clearly not free (3GPP AMR encoder/decoder). * it needs lame and mpg123 (maybe mpg321 is ok) which are not free either. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org signature.asc Description: Digital signature
Bug#317751: ITP: proxsmtp -- multi purpose SMTP Proxy
Package: wnpp Severity: wishlist Owner: Pierre Habouzit <[EMAIL PROTECTED]> * Package name: proxsmtp Version : 1.2.1 Upstream Author : Nate Nielsen <[EMAIL PROTECTED]> * URL : http://www.example.org/ * License : BSD (http://memberwebs.com/nielsen/bsd_license.html) Description : multi purpose SMTP Proxy ProxSMTP is a flexible tool that allows you to reject, change or log email based on arbitrary critera. It accepts SMTP connections and forwards the SMTP commands and responses to another SMTP server. The 'DATA' email body is intercepted and filtered before forwarding. . You need to be able to write the filtering scripts that integrate it with your particular needs. If you're looking for something that does virus filtering, take a look at ClamSMTP which behaves similarly and uses a similar code base. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.11.6 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#312309: ITP: whitelister -- a Postfix Whitelister daemon
Package: wnpp Severity: wishlist Owner: Pierre Habouzit <[EMAIL PROTECTED]> * Package name: whitelister Version : 0.4 Upstream Author : Pierre Habouzit <[EMAIL PROTECTED]> * URL : https://projects.aaege.net/mailtools/wiki/Project.Whitelister * License : GPL v2 Description : a Postfix Whitelister daemon whitelister is a Postfix whitelister Policy Daemon aimed to whitelist mails that come from clean hosts wrt rbl/rhbl in order to let suspicious mails go through evil treatments like greylisting -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-9-amd64-k8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#311150: ITP: twinkle -- VoIP Softphone
Le Dim 29 Mai 2005 11:38, Mark Purcell a écrit : > * URL : http://www.twinklephone.org/ I guess you meant .com ? the .org one does not exists. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpMOvrLJJUha.pgp Description: PGP signature
Bug#303366: ITP: vimcdoc -- Chinese Translation of Vim Online Help Documents
Le Mercredi 6 Avril 2005 13:08, Carlos Z.F. Liu a écrit : > 2. No commercial use of this software are allowed without written > permission from the author. For written permission, please contact > [EMAIL PROTECTED] at least this one means that vimdoc cannot be in main. that's sad. -- ·O· Pierre Habouzit ··O OOOhttp://www.madism.org pgpVqswDvHyY0.pgp Description: PGP signature
Bug#303190: RFP: php4-tidy -- tidy PECL Binding for php4
Package: wnpp Severity: wishlist * Package name: php4-tidy Version : 1.1 Upstream Author : John Coggeshall <[EMAIL PROTECTED]>, Ilia Alshanetsky <[EMAIL PROTECTED]> * URL : http://pecl.php.net/package/tidy * License : PHP Description : tidy PECL Binding for php4 Tidy is a binding for the Tidy HTML clean and repair utility which allows you to not only clean and otherwise manipulate HTML documents, but also traverse the document tree. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#299446: RFH: vim -- Vi IMproved - enhanced vi editor
Le Lun 14 Mars 2005 08:35, Norbert Tretkowski a écrit : > Package: wnpp > Severity: normal > > I'm looking for someone who wants to co-maintain vim, since I > realized that I'm currently unable to take care of the package alone. > There are a lot of open bugs that should be fixed, and there's also > the upcoming vim 7.0 package which is a complete rewrite of the > packaging. It should be easy to work on the package together, there's > a project on alioth using subversion already. > > Drop me a mail if you're interested. > > The package description is: > Vim is an almost compatible version of the UNIX editor Vi. Many new > features have been added: multi level undo, syntax highlighting, > command line history, on-line help, filename completion, block > operations, folding, Unicode support, etc. I am. IANADD *yet* but I am quite near to be one (I'm the 5th from the end, in the DAM Approval waiting guys, was approved by joerg on Feb 15th, and only wait for my account creation) I'm quite a big vim user, and believe I may help. -- ·O· Pierre Habouzit ··O OOOhttp://www.madism.org pgpn5mYMgJpIW.pgp Description: PGP signature
Bug#299024: ITP: dh-zope -- debhelper script for zope packaging
Le Vendredi 11 Mars 2005 14:03, Gustavo Noronha Silva a ÃcritÂ: > Em Sex, 2005-03-11 Ãs 09:48 +0100, Fabio Tranchitella escreveu: > > The package contains the dh_installzope debhelper script used > > for zope packaging tasks. > > Any specific reason to not include this script in debhelper instead? maybe because it has unnecessary dependencies in order to be functionnal ? IIRC, there is some dh_* scripts that are not shiped within debhelper for such reasons [habouzit amaretto] apt-cache search dh-|grep dh dh-buildinfo - Debhelper addon to track package versions used to build a package dh-consoledata - Debhelper-based script to help packaging console data file dh-kpatches - Debhelper script to help packaging kernel patches dh-make - Debianizing Tool for debhelper dh-make-perl - Create debian packages from perl modules and it seems to be quite sensible. -- ÂOÂ Pierre Habouzit ÂÂO OOOhttp://www.madism.org pgpkblHXQ4Zv4.pgp Description: PGP signature
Bug#274816: kdebindings 3.3.0 packages available
Le Jeudi 7 Octobre 2004 12:31, Adeodato Simó a écrit : > note that if you have libqt-perl installed, you'll have to > --force-overwrite libsmokeqt1 and libsmokeqt-dev (#274779). uho taht's bad you have to make either a conflict or a diversion !! -- Pierre Habouzit http://www.madism.org/ -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- gpg : 1024D/A1EE761C 6045 409E 5CB5 2CEA 3E70 F17E C41E 995C C98C 90BE spam: [EMAIL PROTECTED] pgpZEzfh7gdUH.pgp Description: PGP signature
Bug#264051: ITP: php-mdb -- a database abstraction layer
Package: wnpp Severity: wishlist * Package name: php-mdb Version : 1.3.0 Upstream Author : Lukas Kahwe Smith <[EMAIL PROTECTED]> * URL : http://pear.php.net/package/MDB * License : BSD style Description : a database abstraction layer PEAR MDB is a merge of the PEAR DB and Metabase php database abstraction layers. It provides a common API for all support RDBMS. The main difference to most other DB abstraction packages is that MDB goes much further to ensure portability. . Among other things MDB features: . * An OO-style query API * A DSN (data source name) or array format for specifying database servers * Datatype abstraction and on demand datatype conversion * Portable error codes * Sequential and non sequential row fetching as well as bulk fetching * Ordered array and associative array for the fetched rows * Prepare/execute (bind) emulation * Sequence emulation * Replace emulation * Limited Subselect emulation * Row limit support * Transactions support * Large Object support * Index/Unique support * Module Framework to load advanced functionality on demand * Table information interface * RDBMS management methods (creating, dropping, altering) * RDBMS independent xml based schema definition management * Altering of a DB from a changed xml schema * Reverse engineering of xml schemas from an existing DB (currently only MySQL) * Full integration into the PEAR Framework * Wrappers for the PEAR DB and Metabase APIs * PHPDoc API documentation . Currently supported RDBMS: . * MySQL * PostGreSQL * Oracle * Frontbase * Querysim * Interbase/Firebird * MSSQL -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (995, 'unstable'), (990, 'experimental'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7-ck5 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (ignored: LC_ALL set to [EMAIL PROTECTED])
Bug#258356: ITP: flyspray -- a light Bug Tracking System (BTS) in php
Package: wnpp Severity: wishlist * Package name: flyspray Version : 0.9.5 Upstream Author : Tony Collins * URL : http://flyspray.rocks.cc/ * License : GPL Description : a light Bug Tracking System (BTS) in php Description: a light Bug Tracking System (BTS) in php Flyspray is an easy to use BTS for those who don't require all the complexities of something like Bugzilla. Developed for the Psi project, Flyspray is now available for everyone to download and use for their own projects. . Features : * Multiple user groups with a wide variety of permissions * Internationalisation support * Comment posting and File attachments * Unlimited related tasks * Notifications tab for keeping up-to-date with tasks * Multiple Projects, with per-project settings. * Email or Jabber notifications system * Security by regular expression filtering user-submitted data * Theme system using CSS -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (995, 'unstable'), (500, 'experimental'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (ignored: LC_ALL set to [EMAIL PROTECTED])
Bug#195948: dspam packaging status ?
> v2.x being a compilation-based featureset program was due to be a > complete nightmare. DSPAM 3 seems to be much easier. not at all :/ it's still configure driven, and .. well, for packaging, it sucks :/ The major problem is in fact not in the storage backend (since I guess that with some smart modifications of Makefiles, we can be able to link dynamically to libdspam, and then have the same dpsam binady-package for each backend). The thing I can't well understand is how to be able to let the user choose between in header signature, or in body, virtual-users or not ... without having some 2^n different packages ;) > Keep in mind that not only one, but all four SQLite, MySQL, PostgreSQL > and BDB4 *have to be supported*... and this is a lot of work ( i know > from experience, packaging Bacula ). Yeah, I guessed that btw, I talked to Jonathan today, and he said to me he recomended SQLite (which is not part of 3.0.0 but will be soon in stable branch) and MySQL, but that others backend are not that interesting (even really bad -- like bdb4 that has concurency issues) > If you ask because you intend to "adopt" the ITP, i suggest we > cooperated (some help could possibly be very useful). No, I don't want to adopt at all, if work is already done, I can maybe help, and it would be great. > I don't know how much packaging experience you have, but this does not > seem to be suitable for a "first package" effort... well, It's not my first but my second package ? well, I think I can learn very very very quick. And IMHO the bad part is not in the debian-policy-compliance part, but in the `find a way to package this damn thing to provide some configurability to the user' one ... > I am lately considering posting a RFH to help with the > packaging/maintenance, well, I can help, but I miss some experience, so I think even if you are interested in my help, a third person cannot be bad. > since Jonathan Zdiarski (upstream) is a real "release machine". yeah, it seems so ;) Well, to be honest, I'm co-admin of a alumni website, and we do email forwarding. So i'm really interested in the dspam webmail features, and other stuff like that. So I really have motivation to make it work :) (in fact I plan to use it for me too) -- Pierre Habouzit http://www.madism.org/ signature.asc Description: Digital signature
Bug#195948: dspam packaging status ?
Hi what is the current status of dspam packaging ? Is there some work done ? or is this ITP orpharned ? best regards, -- Pierre Habouzit http://www.madism.org/ signature.asc Description: Digital signature
Bug#251871: reassign
submitter 251871 [EMAIL PROTECTED] thanks -- Pierre Habouzit http://www.madism.org/
Bug#255517: ITP: kickpim -- KickPIM is a panel applet for quickly editing and accessing the KDE addressbook or sending emails to your contacts. It shows also a list of upcoming birthdays and waiting emails of multiple email-accounts.
On Tue, Jun 22, 2004 at 09:36:07AM +1000, Matthew Palmer wrote: > On Mon, Jun 21, 2004 at 05:07:22PM +0200, Pierre Habouzit wrote: > > * Package name: kickpim > > Version : x.y.z > > Hmm... > > > Upstream Author : Name <[EMAIL PROTECTED]> > > HMM... > > > * URL : http://www.example.org/ > > Errr > > > * License : (GPL, LGPL, BSD, MIT/X, etc.) > > Ahem. > > - Matt hi Matt ! sorry, i should have bee really inattentive while filling this ITP ... g here is the correct informations : * pakcage Name: KickPIM version : 0.5.3-1 * Upstream Author : Bert Speckels * URL : http://kickpim.sourceforge.net/ * License : GPL I already did a first shot on http://www.kalyxo.org/debian/ but the package needs a lot work to be done, since it's atm not KDE compliant. I'm waiting for the upstream author to answer me :) -- Pierre Habouzit http://www.madism.org/ signature.asc Description: Digital signature
Bug#255517: ITP: kickpim -- KickPIM is a panel applet for quickly editing and accessing the KDE addressbook or sending emails to your contacts. It shows also a list of upcoming birthdays and waiting emails of multiple email-accounts.
Package: wnpp Severity: wishlist * Package name: kickpim Version : x.y.z Upstream Author : Name <[EMAIL PROTECTED]> * URL : http://www.example.org/ * License : (GPL, LGPL, BSD, MIT/X, etc.) Description : kde kicker applet to access addressbook KickPIM is a panel applet for quickly editing and accessing the KDE addressbook or sending emails to your contacts. It shows also a list of upcoming birthdays and waiting emails of multiple email-accounts. project page is here : http://kickpim.sourceforge.net/ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (995, 'unstable'), (500, 'experimental'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.5 Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set to [EMAIL PROTECTED])
