Re: Proposal to add and maintain the epstool package

On Fri, Jan 07, 2005 at 02:41:37PM -0800, [EMAIL PROTECTED] wrote: >--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > >> >> The format of setup.ini is easy enough to understand. You don't need a >> special program to test this. >> > >OK, you have to use unix style path separators - I figured t

Re: Proposal to add and maintain the epstool package

--- Christopher Faylor <[EMAIL PROTECTED]> wrote: > > The format of setup.ini is easy enough to understand. You don't need a > special program to test this. > OK, you have to use unix style path separators - I figured that out, so setup.ini parses successfully. I got the file sizes and the m

Re: multiple Unison packages?

> The archive format is an on-disk thing, and not really relevant to network > compatibility. > The reason for the (overly) strict initial version check is to avoid any > need for versioning or compatibility in the protocol that follows the > initial greeting. Ah, okay. > Debian seem to be packag

Setup: hardlinks & percentages. (+patches)

Hallo, Two little patches: When setup is making hardlinks, it doesn't use the prefixPath. It is therefore just luck that hardlinks in normal packages ``work''. Hardlinks in source-packages however don't, currently. (case in point: rcs.) 2005-01-07 Bas van Gompel <[EMAIL PROTECTED]> *

Re: Proposal to add and maintain the epstool package

[EMAIL PROTECTED] wrote: I am interested in becoming a package maintainer for the package epstool. You may be interested to take a look at the version taht was packaged by Charles Wilson: http://cygutils.fruitbat.org/testing/ADOPT-ME/epstool/ Gerrit -- =^..^=

Re: multiple Unison packages?

[EMAIL PROTECTED] wrote: Different versions of Unison won't talk to each other. For example, if I have version 2.10.2 (current beta) installed on my local Cygwin host, I can't synchronize with a server that's running version 2.9.1 (current stable). The version numbers have to be exactly the same,

Re: Proposal to add and maintain the epstool package

On Fri, Jan 07, 2005 at 12:20:50PM -0800, [EMAIL PROTECTED] wrote: >I have source and binary packages available, but am unable to test >setup.hint due to the non-availability of upset. The format of setup.ini is easy enough to understand. You don't need a special program to test this.

Proposal to add and maintain the epstool package

Hi, I am interested in becoming a package maintainer for the package epstool. The current version of upstream is located at ftp://mirror.cs.wisc.edu/pub/mirrors/ghost/ghostgum/epstool-3.06.tar.gz epstool is GPL'ed, and is available in Debian. I have source and binary packages available, but am

multiple Unison packages?

Different versions of Unison won't talk to each other. For example, if I have version 2.10.2 (current beta) installed on my local Cygwin host, I can't synchronize with a server that's running version 2.9.1 (current stable). The version numbers have to be exactly the same, or Unison will issue an

[ITP] cvsutils

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I would like to add cvsutils to my growing list of maintained packages. Debian lists it as stable, packages.debian.org/stable/devel/cvsutils. sdesc: "CVS client utilities for offline work." ldesc: "Client-side tools for interacting with CVS, performing

Re: what about a "Security" category?

On Thu, Jan 06, 2005 at 06:19:25PM +0100, Lapo Luchini wrote: > Personally I'd choose any program that uses cryptography directly (e.g. > I wound't include autossh as it is "simply" an openssh frontend) and/or > is useful to secure a system (an antivirus). > But of course the difference is subtle,