On Mon, Feb 17, 2003 at 07:40:56PM +0200, Antti-Juhani Kaijanaho wrote:
On 20030213T213418+, Jonathan McDowell wrote:
The only drawback I can see is changes in the packaging between
releases leads to a whole new src tarball to upload to the archive
rather than just a new diff, but
On 20030213T213418+, Jonathan McDowell wrote:
The only drawback I can see is changes in
the packaging between releases leads to a whole new src tarball to
upload to the archive rather than just a new diff, but hopefully this
shouldn't happen too often.
I once did this, and usually I let
On Mon, Feb 17, 2003 at 07:40:56PM +0200, Antti-Juhani Kaijanaho wrote:
On 20030213T213418+, Jonathan McDowell wrote:
The only drawback I can see is changes in the packaging between
releases leads to a whole new src tarball to upload to the archive
rather than just a new diff, but
Bas Zoetekouw [EMAIL PROTECTED] writes:
Hi Jonathan!
You wrote:
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there any
good
On Thu, Feb 13, 2003 at 09:34:18PM +, Jonathan McDowell wrote:
I'm sure I've seen this hashed over in the past, so feel free to point me
at list archives.
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been asked
by upstream if I want to maintain the debian/ directory in
Jonathan McDowell wrote:
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there any
good reason not to do this?
I think others have presented
This one time, at band camp, Jonathan McDowell wrote:
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there any
good reason not to do this? It
On Sat, 2003-02-15 at 12:35, Martin Baehr wrote:
On Fri, Feb 14, 2003 at 07:40:31PM -0500, John Belmonte wrote:
It turned out he agreed to omit the debian tree from his tarballs at my
request, but I also suggested he could just rename the directory to
debian_sample. In this way there
On Sat, 15 Feb 2003, Martin Baehr wrote:
On Fri, Feb 14, 2003 at 07:40:31PM -0500, John Belmonte wrote:
It turned out he agreed to omit the debian tree from his tarballs at my
request, but I also suggested he could just rename the directory to
debian_sample. In this way there would be no
On Fri, Feb 14, 2003 at 04:19:29PM -0500, Matt Zimmerman wrote:
On Thu, Feb 13, 2003 at 09:34:18PM +, Jonathan McDowell wrote:
I'm sure I've seen this hashed over in the past, so feel free to point me
at list archives.
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've
Bas Zoetekouw [EMAIL PROTECTED] writes:
Hi Jonathan!
You wrote:
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there any
good
On Thu, Feb 13, 2003 at 09:34:18PM +, Jonathan McDowell wrote:
I'm sure I've seen this hashed over in the past, so feel free to point me
at list archives.
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been asked
by upstream if I want to maintain the debian/ directory in
Jonathan McDowell wrote:
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there any
good reason not to do this?
I think others have presented
This one time, at band camp, Jonathan McDowell wrote:
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there any
good reason not to do this? It
On Fri, Feb 14, 2003 at 07:40:31PM -0500, John Belmonte wrote:
It turned out he agreed to omit the debian tree from his tarballs at my
request, but I also suggested he could just rename the directory to
debian_sample. In this way there would be no interference with my work,
and he could
On Sat, 15 Feb 2003, Martin Baehr wrote:
On Fri, Feb 14, 2003 at 07:40:31PM -0500, John Belmonte wrote:
It turned out he agreed to omit the debian tree from his tarballs at my
request, but I also suggested he could just rename the directory to
debian_sample. In this way there would be no
On Fri, Feb 14, 2003 at 04:19:29PM -0500, Matt Zimmerman wrote:
On Thu, Feb 13, 2003 at 09:34:18PM +, Jonathan McDowell wrote:
I'm sure I've seen this hashed over in the past, so feel free to point me
at list archives.
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've
I'm sure I've seen this hashed over in the past, so feel free to point
me at list archives.
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there
Hi Jonathan!
You wrote:
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there any
good reason not to do this?
I see very few problems with
I'm sure I've seen this hashed over in the past, so feel free to point
me at list archives.
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there
Hi Jonathan!
You wrote:
I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been
asked by upstream if I want to maintain the debian/ directory in the
project's CVS. The RPM .spec file is already done this way. Is there any
good reason not to do this?
I see very few problems with
21 matches
Mail list logo
