Re: What is the best place for package meta-data ?

Le Thu, Aug 06, 2009 at 09:17:22PM +0200, Paul Wise a écrit : > > I'd put the homepage in a "user" category and the VCS URLs in a > "developer" category. > > The data in that database is gathered from .changes files and binary > and source packages uploaded to ftp-master, except for debtags and >

Bug#540458: ITP: eiskaltdc -- Direct Connect protocol client (Valknut fork)

Package: wnpp Severity: wishlist Owner: Tataranovich Andrey * Package name: eiskaltdc Version : 0.5a Upstream Author : Mathias Küster * URL : http://sourceforge.net/projects/eiskaltdc/ * License : GPL, LGPLv3 Programming Lang: C++ Description : Direct

Re: Bug#540332: ITP: at-spi2-core -- Assistive Technology Service Provider Interface (Core) - dbus

Oh yes, you're right, I didn't notice there were already preliminary packages for new at-spi, since they are just released recently. I'm terribly sorry to duplicate your jobs. I think I should close this bug, but how? :) Sorry again, please ignore my reports. :) On Fri, Aug 7, 2009 at 6:37 PM,

Bug#540513: ITP: stxxl -- C++ Standard Template Library (STL) for extra large datasets

Package: wnpp Severity: wishlist Owner: "d.haley" * Package name: stxxl Version : 1.2.1 Upstream Author : Andreas Beckmann * URL : http://stxxl.sourceforge.net * License : Boost Software License - Version 1.0 - August 17th, 2003 Programming Lang: C++

Re: piuparts-MBF: overwriting other packages files

On Fri, Aug 07 2009, Holger Levsen wrote: > On Freitag, 7. August 2009, Manoj Srivastava wrote: >> While it is good to discover these bugs, is puiparts the correct >> place to do this check? Won't puiparts only report on packages >> installed on the machine on which the test is run, and

Bug#540545: ITP: grads -- Grid Analysis and Display System for earth science data

Package: wnpp Severity: wishlist Owner: Alastair McKinstry * Package name: grads Version : 2.0 Upstream Author : NASA Advanced Information Systems Research Program * URL : http://www.iges.org/grads/ * License : GPL Programming Lang: C Description : Grid

Re: Automatic Debug Packages

[ Moving to debian-policy ] Manoj Srivastava wrote: > On Fri, Jul 31 2009, Emilio Pozuelo Monfort wrote: > >> Manoj Srivastava wrote: >>> We do not want to have different helper package start inventing >>> a helper specific way of building ddebs, with no clear standard tha >>> they are

Re: Automatic Debug Packages

On Sat, Aug 08 2009, Emilio Pozuelo Monfort wrote: > [ Moving to debian-policy ] > > Manoj Srivastava wrote: >> On Fri, Jul 31 2009, Emilio Pozuelo Monfort wrote: >> >>> Manoj Srivastava wrote: We do not want to have different helper package start inventing a helper specific wa

Re: Automatic Debug Packages

Manoj Srivastava wrote: > On Sat, Aug 08 2009, Emilio Pozuelo Monfort wrote: >> I've documented the .ddeb format in the wiki page [1] ("DDeb Format", >> which is short since the format is basically that of .debs). Do we >> really need this to be documented in policy? > > Not if that is all

Re: Automatic Debug Packages

Emilio Pozuelo Monfort writes: > You can build a .ddeb manually, yes. However for some cases > (e.g. packages using debhelper and building ELF binaries) a .ddeb will > be automatically created (if none is created manually) and detached > debugging symbols will be put there. I'll try to automatize

Re: Automatic Debug Packages

On Sat, Aug 08 2009, Emilio Pozuelo Monfort wrote: > Manoj Srivastava wrote: >> On Sat, Aug 08 2009, Emilio Pozuelo Monfort wrote: >>> I've documented the .ddeb format in the wiki page [1] ("DDeb Format", >>> which is short since the format is basically that of .debs). Do we >>> really need this t

Re: Automatic Debug Packages

Manoj Srivastava writes: > On Sat, Aug 08 2009, Emilio Pozuelo Monfort wrote: > >> Manoj Srivastava wrote: >>> On Sat, Aug 08 2009, Emilio Pozuelo Monfort wrote: I've documented the .ddeb format in the wiki page [1] ("DDeb Format", which is short since the format is basically that of .d