tag 449190 + pending
thanks
Added Daniel's HOWTO (with minor modifications) to my git repo, it will
be part of the next upload.
--
|8]
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Independent from the ongoing discussion at debian-devel I attach a small
README, that explains how to use dpatch with svn-buildpackage in
mergeWithUpstream mode. Please don't hesitate to send feedback,
suggestions or critics.
Maybe with this README, this bug can be closed.
Regards, Daniel
HOWTO
Hi,
I've written a small blog [1] entry for this question (and I already
sent a hint to the OP of this report). Maybe you want to use the example
from my blog to explain, how to use dpatch with svn-buildpackage. JFTR:
I give no warranty and I give unlimited permission to copy, use,
distribute and
On Sun, Nov 04, 2007 at 12:44:23AM +0100, Sandro Tosi wrote:
So, there is need a way to merge upstream code with the one kept in svn
Is there something wrong with dpatch-edit-patch's --debianonly option?
Greetings
Marc
--
Is there something wrong with dpatch-edit-patch's --debianonly option?
Mh, maybe not, it's only that I didn't know about that and no
documentation talks of this as a way to handle svn package in mergeWO
mode.
Maybe we can keep this bug as a way to improve doc about that (and in
general) or
Package: dpatch
Version: 2.0.28
Severity: wishlist
Hello,
there are packages using svn-buildpackage that are set to use
mergeWithUpstream tag, so taht only debian files are kept into svn
repository and merged at build-time with upstream code.
For such packages, dpatch-e-p fails since upstream
6 matches
Mail list logo
