Re: Proposed MBF: packages defining useless RPATH's

2008-02-19 Thread Raphael Hertzog
On Mon, 18 Feb 2008, Raphael Geissert wrote: > Besides of what Stephen Gran already said on his message I believe there's > no chance of NMU's to take place if the bugs aren't reported :). I would never NMU just to correct an harmless rpath. Thus if I NMU such a package, it's because of something

Re: Proposed MBF: Debian upstream version higher than watch file-reported upstream version

2008-02-19 Thread Michal Čihař
Hi On Mon, 18 Feb 2008 19:20:18 -0600 Raphael Geissert <[EMAIL PROTECTED]> wrote: > Seems like I forgot to make sure to list only those affecting packages in > unstable. But it would anyway be nice to keep both watch files working :) I know, but I tend to forgot to this when I upload package to

Re: Debian mirror CDN had launched.

2008-02-19 Thread ARAKI Yasuhiro
Florian Weimer: * ARAKI Yasuhiro: Do you like cdn.debian.net's idea and implementation? Sorry if I sound like a broken record. What kind of software do you use? Is this just DNS-Balance plus a handful of scripts? Patially right. cdn.d.n is consisted by -(modifiled) DNS-balance to return DN

Upstream API breakage question

2008-02-19 Thread William Pitcock
Hi, libprojectM upstream are soon releasing libprojectM 1.1 which makes the following breakage: public: PCM *projectM::pcm is replaced by: public: const inline PCM *projectM::pcm() { return _pcm; } So, is this the proper solution: * libprojectm1 -> libprojectm2 * libprojectm-dev -> libproject

Re: Upstream API breakage question

2008-02-19 Thread Michal Čihař
Hi On Tue, 19 Feb 2008 03:43:09 -0600 William Pitcock <[EMAIL PROTECTED]> wrote: > libprojectM upstream are soon releasing libprojectM 1.1 which makes the > following breakage: > > public: PCM *projectM::pcm > > is replaced by: > > public: const inline PCM *projectM::pcm() { return _pcm; } >

Re: Upstream API breakage question

2008-02-19 Thread Hamish Moffatt
On Tue, Feb 19, 2008 at 03:43:09AM -0600, William Pitcock wrote: > libprojectM upstream are soon releasing libprojectM 1.1 which makes the > following breakage: > > public: PCM *projectM::pcm > > is replaced by: > > public: const inline PCM *projectM::pcm() { return _pcm; } > > So, is this the

Bug#466536: ITP: ecore -- Core abstraction layer for enlightenment DR 0.17

2008-02-19 Thread Albin Tonnerre
Package: wnpp Severity: wishlist Owner: Debian Pkg-e Team <[EMAIL PROTECTED]> * Package name: ecore Version : 0.9.9.042 Upstream Author : Carsten Haitzler and the e17 devel team <[EMAIL PROTECTED]> * URL : http://www.enlightenment.org * License : BSD Programm

Bug#466542: ITP: task-spooler -- local batch job queue

2008-02-19 Thread Alexander V. Inyukhin
Package: wnpp Severity: wishlist Owner: "Alexander V. Inyukhin" <[EMAIL PROTECTED]> * Package name: task-spooler Version : 0.5.3 Upstream Author : Lluц╜s Batlle i Rossel [EMAIL PROTECTED]> * URL : http://vicerveza.homeunix.net/~viric/soft/ts/ * License : GPL P

Bug#466544: ITP: eeepc-acpi-scripts -- Scripts to support suspend and hotkeys on the Asus Eee PC laptop

2008-02-19 Thread Nico Golde
Package: wnpp Severity: wishlist Owner: Nico Golde <[EMAIL PROTECTED]> * Package name: eeepc-acpi-scripts Version : 1.0 Upstream Author : Debian EeePC Team <[EMAIL PROTECTED]> * URL : http://alioth.debian.org/projects/debian-eeepc/ * License : GPL Programming

Bug#466556: ITP: python-mvpa -- multivariate pattern recognition with Python

2008-02-19 Thread Michael Hanke
Package: wnpp Severity: wishlist Owner: Michael Hanke <[EMAIL PROTECTED]> * Package name: python-mvpa Version : 0.1.0 Upstream Author : Michael Hanke <[EMAIL PROTECTED]>, Yaroslav Halchenko <[EMAIL PROTECTED]> * URL : http://pkg-exppsy.alioth.debian

Re: Bug#466433: ITP: dkfilter -- implements domainKeys message signing and verification

2008-02-19 Thread Scott Kitterman
On Mon, 18 Feb 2008 20:14:16 +0100 Yves-Alexis Perez <[EMAIL PROTECTED]> wrote: >On mar, 2008-02-19 at 02:20 +0800, Thomas GOIRAND wrote: >> As Yahoo! requests DomainKeys to be implemented for sending mail to >> them, it's quite urgent that this package reaches SID asap to allow >> people to be ab

Re: Debian mirror CDN had launched.

2008-02-19 Thread Gunnar Wolf
Yasuhiro Araki dijo [Tue, Feb 19, 2008 at 07:53:21AM +0900]: > Example of configuration lines are followings for unam.mx. > > $addr_db = { > "133.248.0.0/16" => { # => Request from 133.248.0.0/16 >#For example, DNS client's IP is >

Re: Upstream API breakage question

2008-02-19 Thread Bernhard R. Link
* William Pitcock <[EMAIL PROTECTED]> [080219 10:40]: > libprojectM upstream are soon releasing libprojectM 1.1 which makes the > following breakage: > > public: PCM *projectM::pcm > > is replaced by: > > public: const inline PCM *projectM::pcm() { return _pcm; } > > So, is this the proper solu

Bug#466562: ITP: lxpanel -- a lightweight desktop panel for X

2008-02-19 Thread Andrew Lee
Package: wnpp Severity: wishlist Owner: Andrew Lee <[EMAIL PROTECTED]> * Package name: lxpanel Version : 0.2.5 Upstream Author : Hong Jen Yee(PCMan) <[EMAIL PROTECTED]> * URL : http://www.gnomefiles.org/app.php/LXPanel * License : (GPL, LGPL) Programming Lang:

Bug#466583: ITP: ganeti-instance-debian-etch -- instance OS definition for ganeti

2008-02-19 Thread Iustin Pop
Package: wnpp Severity: wishlist Owner: Iustin Pop <[EMAIL PROTECTED]> * Package name: ganeti-instance-debian-etch Version : 0.4 Upstream Author : Google Inc. <[EMAIL PROTECTED]> * URL : http://code.google.com/p/ganeti * License : GPL Programming Lang: Shell

Re: Proposed MBF: packages defining useless RPATH's

2008-02-19 Thread Raphael Geissert
Raphael Hertzog wrote: > On Mon, 18 Feb 2008, Raphael Geissert wrote: >> Besides of what Stephen Gran already said on his message I believe >> there's no chance of NMU's to take place if the bugs aren't reported :). > > I would never NMU just to correct an harmless rpath. Thus if I NMU such a > p

liblockfile L_PID behavior and use of stat atime

2008-02-19 Thread Rob Browning
Someone reported a bug against lockfile-progs, and while investigating I noticed a couple of things about liblockfile that didn't seem quite right. First of all, if you run "lockfile-create foo", which calls lockfile_create() without the L_PID flag, you'll see that the resulting foo.lock file con