Hi all plz add my ID for link exhcagne

2009-06-16 Thread King Khan
-- Thanks & Regards King Khan A SEO executive n LB New Delhi

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Sune Vuorela
On 2009-06-16, Paul Wise wrote: > On Tue, Jun 16, 2009 at 7:20 AM, Charles Plessy wrote: > >> The dh_make template for debian/copyright induces many developers to put >> their >> packaging work under the GPL, and I have already seen packages whose license >> is >> otherwise BSD-ish with such pat

Re: lrmi vs new kernels vs libx86

2009-06-16 Thread David Paleino
Sorry for re-triggering an old thread, On Sun, 8 Mar 2009 21:07:29 +0100, David Paleino wrote: > On Sun, 8 Mar 2009 16:49:33 +0100, Evgeni Golov wrote: > > > [..] > > David, is there any chance that libx86 will be updated someday? Esp > > because upstream of v86d has an updated 0.10 in his git a

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Thijs Kinkhorst
Hi Raphaël, On Mon, June 15, 2009 18:12, Raphael Hertzog wrote: > please find below a first draft of DEP-3 that I called Patch Tagging > Guidelines. The idea is to standardize a set of meta-information to embed > in patches that we apply. Please review, share your comments and ideas > of enhancem

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Mark Brown
On Mon, Jun 15, 2009 at 11:31:51PM +0200, Carsten Hey wrote: > On Mon, Jun 15, 2009 at 10:15:16PM +0100, Mark Brown wrote: > > On Mon, Jun 15, 2009 at 11:10:14PM +0200, Carsten Hey wrote: > > > I currently don't see a relevant benefit in this above just using the > > > changelog entry, which you n

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Carsten Hey
On Tue, Jun 16, 2009 at 10:05:40AM +0100, Mark Brown wrote: > On Mon, Jun 15, 2009 at 11:31:51PM +0200, Carsten Hey wrote: > > If an integration of the information in the patch headers into UDD would > > be planned which could be used to query patches not applied upstream or > > similar, I would at

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Reinhard Tartler
"Thijs Kinkhorst" writes: > Hi Raphaël, > > On Mon, June 15, 2009 18:12, Raphael Hertzog wrote: >> please find below a first draft of DEP-3 that I called Patch Tagging >> Guidelines. The idea is to standardize a set of meta-information to embed >> in patches that we apply. Please review, share y

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Mark Brown
On Tue, Jun 16, 2009 at 11:23:17AM +0200, Reinhard Tartler wrote: > "Thijs Kinkhorst" writes: > > above the patch? That works fine for me. Every formalisation has a cost > > and I'm not sure here that it's offset by the (which?) benefits. > Possible benefits (partly mentioned in the spec) > -

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Thijs Kinkhorst
On Tue, June 16, 2009 11:23, Reinhard Tartler wrote: > "Thijs Kinkhorst" writes: > > >> Hi Raphaël, >> >> >> On Mon, June 15, 2009 18:12, Raphael Hertzog wrote: >> >>> please find below a first draft of DEP-3 that I called Patch Tagging >>> Guidelines. The idea is to standardize a set of meta-inf

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Reinhard Tartler
"Thijs Kinkhorst" writes: >> Possible benefits (partly mentioned in the spec) >> >> - tools can be adapted/crafted to maintain these fields >> - streamline development practice to faciliate team communication >> - (web)tools can analyse and produce statistics.. > > This is still quite abstract: "

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Felipe Sateler
Carsten Hey wrote: > On Tue, Jun 16, 2009 at 10:05:40AM +0100, Mark Brown wrote: >> On Mon, Jun 15, 2009 at 11:31:51PM +0200, Carsten Hey wrote: >> > If an integration of the information in the patch headers into UDD >> > would be planned which could be used to query patches not applied >> > upstr

Re: good way to change a name of a package

2009-06-16 Thread Atsuhito Kohda
On Mon, 15 Jun 2009 19:06:26 -0300, Mauro Lizaur wrote: > Here's an example of how to do that: > http://wiki.debian.org/Renaming_a_Package Thanks for your advise. It might be better if there are explanations on debconf transition and changelog handling. Regards, 2009-6-

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread sean finney
hi, (yay for group reply) On Mon, Jun 15, 2009 at 06:12:49PM +0200, Raphael Hertzog wrote: > * `Description` (required) > > This obligatory field contains at least a short description on the > first line. Supplementary lines can be used to provide a longer > explanation of the patc

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Lucas Nussbaum
On 16/06/09 at 17:18 +0200, sean finney wrote: > On Mon, Jun 15, 2009 at 06:27:45PM +0200, Lucas Nussbaum wrote: > > > (possibly fixed by the patch). The `Bug` field is reserved > > > for the bug URL(s) in the upstream bug tracker. > > > > What about using Debian: (like Ubuntu's Patch Tagg

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread sean finney
On Tue, Jun 16, 2009 at 05:44:55PM +0200, Lucas Nussbaum wrote: > > * `Debian-Specific` (optional) > > > >Is this patch a debian-specific patch that is not intended to be > >shared with upstream? For example, changes to specify Debian-specific > >application paths, configuration file

usplash up to adoption

2009-06-16 Thread maximilian attems
no time to sync with ubuntu upstream, latest Debian can be found in git://git.debian.org/collab-maint/usplash.git -- maks ps please keep on Cc, thanks! -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.

Bug#533348: ITP: udev-extras -- a collection of udev rules and helper programs

2009-06-16 Thread Marco d'Itri
Package: wnpp Severity: wishlist Owner: "Marco d'Itri" http://git.kernel.org/?p=linux/hotplug/udev-extras.git;a=summary It will be uploaded next month, I expect that it will not differ much from the Ubuntu package. -- ciao, Marco signature.asc Description: Digital signature

Maps within Debian

2009-06-16 Thread Alastair McKinstry
Hi, I am working on some packages for Debian Meteorology (http://wiki.debian.org/DebianScience/Meteorology): magics++ , a plotting / graphics library / scripting system , and zyGrib, a GRIB (met. format) file viewer. They both include some coastline maps from "gshhs" (http://www.ngdc.noaa.gov

maps / coastline files within Debian

2009-06-16 Thread Alastair McKinstry
Hi, I am working on some packages for Debian Meteorology (http://wiki.debian.org/DebianScience/Meteorology): magics++ , a plotting / graphics library / scripting system , and zyGrib, a GRIB (met. format) file viewer. They both include some coastline maps from "gshhs" (http://www.ngdc.noaa.gov

Re: Maps within Debian

2009-06-16 Thread Sandro Tosi
On Tue, Jun 16, 2009 at 22:51, Alastair McKinstry wrote: > Hi, > > I am working on some packages for Debian Meteorology > (http://wiki.debian.org/DebianScience/Meteorology): > magics++ , a plotting / graphics library / scripting system , and zyGrib, a > GRIB (met. format) file viewer. > They both i

Bug#533369: ITP: tinycalc -- Command line calculator for developers

2009-06-16 Thread Rocco Folino
Package: wnpp Severity: wishlist Owner: Rocco Folino * Package name: tinycalc Version : 0.1 Upstream Author : Rocco Folino * URL : http://tinycalc.sourceforge.net * License : GPL Programming Lang: C Description : Command line calculator for developers

Re: Bug#533369: ITP: tinycalc -- Command line calculator for developers

2009-06-16 Thread Ben Pfaff
Rocco Folino writes: > Tiny Calculator is a command line calculator for developers. > It can resolve a complex expression mixing decimal, esadecimal an binary > number. > The result is automatic converted in decimal, esadecimal ad binary format. I suspect: s/esadecimal/hexadecimal/. And "and"

Bug#533388: ITP: drcom-pum -- fully GUI configurable X drcom-client using GTK+

2009-06-16 Thread Henry Huang
Package: wnpp Severity: wishlist Owner: Henry Huang * Package name: drcom-pum Version : 1.0 Upstream Author : Wheelz Henry Huang Longshow * URL : http://www.drcom-client.org/ * License : GPLv2 Programming Lang: C, Py

Re: RFC: DEP-3: Patch Tagging Guidelines

2009-06-16 Thread Ben Finney
Raphael Hertzog writes: > * `Origin` (required) > > This field should document the origin of the patch. It can have the > following standard values: "upstream" (in the case of a patch > cherry-picked > from the upstream VCS), "backport" (in the case of an upstream patch > that