Thanks. Running “pristine-tar checkout
google-cloud-print-connector_1.12.orig.tar.gz” indeed gets me further.
Could a check for the orig tarball be added to “dgit build-source”?
The current dpkg-source message is confusing:
• it mentions a generic “orig.tar” instead of the actual filename it expects
• it mentions “debian.tar”, which I assume doesn’t apply here
• it claims my package uses source format v2.0, but I’m using v3.0
On Fri, Oct 13, 2017 at 10:37 AM, Ian Jackson
<ijack...@chiark.greenend.org.uk> wrote:
> Michael Stapelberg writes ("Bug#878433: dgit-maint-merge(7) workflow for
> converting an existing package does not work"):
>> Package: dgit
>> Version: 3.12
>> Severity: normal
>>
>> I read the following section of the dgit-maint-merge(7):
>> https://manpages.debian.org/stretch/dgit/dgit-maint-merge.7.en.html#Existing_git_history_using_another_workflow
>
> I'm currently on a train and can't dig properly, but:
>
>> And tried to apply it to one of my packages:
>>
>> % gbp clone
>> git+ssh://git.debian.org/git/pkg-go/packages/google-cloud-print-connector.git
>> gbp:info: Cloning from
>> 'git+ssh://git.debian.org/git/pkg-go/packages/google-cloud-print-connector.git'
>> % cd google-cloud-print-connector
> ...
>> % dgit build-source
>> Format `3.0 (quilt)', need to check/update patch stack
>> examining quilt state (multiple patches, linear mode)
>> dpkg-source: error: missing orig.tar or debian.tar file in v2.0 source
>> package
>
> I don't know how the dgit-maint-merge workflow is supposed to generate
> the .orig, but before yo do this you need to somehow have
> ../google-cloud-print-connector_UPSTREAMVERSION.orig.tar.gz
> or similar.
>
> In the absence of a better answer from me, maybe Sean can enlighten
> you ?
>
> Ian.
--
Best regards,
Michael
