> Does it handle pristine upstream source?
Yes, via the cvs-upgrade program. See /usr/doc/cvs-buildpackage/HOWTO.gz
Will
--
| [EMAIL PROTECTED] [EMAIL PROTECTED] [E
On Wed, Feb 23, 2000 at 02:41:50PM +0100, Roland Rosenfeld wrote:
> tree. The only disadvantage of cvs-buildpackage is, that it has
> problems with links in the upstream source package.
Does it handle pristine upstream source?
--
%%% Antti-Juhani Kaijanaho % [EMAIL PROTECTED] % http://www.iki.f
On Wed, Feb 23, 2000 at 02:29:17PM +0200, Edvard Majakari wrote:
> > "AK" == Antti-Juhani Kaijanaho <[EMAIL PROTECTED]> writes:
>
> AK> I'm assuming you mean packaging a new upstream release, not
> AK> creating a new Debian revision of the same upstream source.
>
> I meant both :)
Making
> Your .changes file must say you are uploading the .orig.tar.gz
> else dinstall has no reason to look for it. I think the option to
> dpkg-buildpackage is -sa or similar.
Indeed, this was the problem. I solved the problem by passing the -sa
option into cvs-buildpackage, which passed it on to dpk
On Wed, 23 Feb 2000, Antti-Juhani Kaijanaho wrote:
> The natural way of doing this is unpacking the new upstream source,
> and patching it with the latest Debian diff, and adding a new
> changelog entry. The "uupdate" program (in devscripts) automates
> this. You then need to resolve any conflicts
> "AK" == Antti-Juhani Kaijanaho <[EMAIL PROTECTED]> writes:
AK> I'm assuming you mean packaging a new upstream release, not
AK> creating a new Debian revision of the same upstream source.
I meant both :)
AK> The natural way of doing this is unpacking the new upstream
AK> source, and pa
On Wed, Feb 23, 2000 at 12:54:48PM +0200, Edvard Majakari wrote:
> how to create a new debian version out of the already debianized
> package - so far I've created package from the scratch every time (of
> course, some of the old debian files like rules, dirs etc can often be
> used as is with the
Ok, here we go.. the problem: I see the new Debian package maintainers
guide quite a good document, but it isn't obvious (at least to me :)
how to create a new debian version out of the already debianized
package - so far I've created package from the scratch every time (of
course, some of the ol
On Mon, Feb 21, 2000 at 03:09:19PM -0500, Will Lowe wrote:
> I uploaded a new version of fsviewer a while back, and got this from
> dinstall:
>
> > Rejected: md5sum for
> > dists/potato/main/source/x11/fsviewer_0.2.3.orig.tar.gz doesn't match
> > fsviewer_0.2.3-2.dsc. Rejected: md5sum for
> > di
I've packed Mktclapp for Debian. From the control file:
Mktclapp is a utility that helps you mix C/C++ with Tcl/Tk.
Mktclapp was written by the same author of ET, and it has the same
goals of ET but it is simpler and has a much cleaner interface. Its
author encourages all ET users
Michael Vogt wrote:
> If there is no prerm, it just uses this one. But this is sh, I use tcsh.
> My solution is to add a prerm file, that has a "#!/bin/sh" on top.
> What do you think? Is this a bug in debhelper? Or is it documented somewhere?
Debhelper adds "#/bin/sh -e" to the top of any script
11 matches
Mail list logo
