Hello John and Peter, * John Goerzen <[EMAIL PROTECTED]>, [2005-09-07 15:50 -0500]: > On Wed, Sep 07, 2005 at 10:02:41PM +0200, Peter Van Eynde wrote: > > It cannot recreate the exact same .orig.tar.gz file, so the upload will > > fail. > > True. > > > The system should detect that when there is no .orig.tar.gz file and it > > is creating a higher version release (ie not -1) it should bail out or > > (better) use apt-get source to get the .orig.tar.gz file. > > I'm not so sure about this part. Perhaps an all-caps warning is in > order, but for me, part of the allure of this tool is the ability to go > back in time and build working source and binary packages. Uploading > them to Debian isn't always the end goal. There is also no guarantee > that a user's apt-get would be configured in such a way that it can > obtain the source for the version in question. > > So I'm inclined to tag this one wontfix and set it to wishlist, but I'm > interested in your thoughts on what I've said.
I agree with you, and everything works fine if one switches to
darcs-buildpackage for a new upstream release or an initial
debianization.
But is a full source upload the correct way for switching to
darcs-buildpackage for a > 1 Debian revision?
If so, why not stating it into the docs?
Maybe even an all-caps warning at the end of the building process which
informs you that the .orig.tar.gz has been changed could be very
helpful.
ciao,
ema
signature.asc
Description: Digital signature
