On Jan 03 2017, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote:
> Nikolaus Rath writes ("Bug#850005: dgit push without dgit build-source"):
>> Package: dgit
>> Version: 2.13
>> Severity: normal
> ...
>> $ dgit --dpm build-source
>> [...]
>> dpkg-checkbuilddeps: Unmet build dependencies: python-pytest-catchlog
>> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
>> aborting
>> dpkg-buildpackage: warning: (Use -d flag to override.)
>> dgit: failed command: dpkg-buildpackage '-i'\\'.git/' -I.git -T clean
>> dgit: subprocess failed with error exit status 3
>
> This is because building the source package runs the package clean
> target (by default).
>
> I think maybe what you wanted was --clean=dpkg-source-d aka -wdd ?
>
> Or, perhaps, --clean=git-force aka -wgf ...
Not sure:
$ dgit --dpm --clean=git build-source
Format `3.0 (quilt)', need to check/update patch stack
examining quilt state (multiple patches, dpm mode)
dgit: split brain (separate dgit view) may be needed (--quilt=dpm).
dgit: base trees orig=c8ab943f37df17d83f09 o+d/p=9e2aab849fc3a861ab5a
dgit: quilt differences: src: ## orig ## gitignores: == orig ==
dgit: quilt differences: HEAD ## o+d/p HEAD == o+d/p
dgit: --quilt=dpm specified, implying patches-applied git tree
dgit: but git tree differs from result of applying debian/patches to upstream
Adding -D gave a lot more output, but it didn't help me that much.
Is there a way to see what differences dgit is concerned about? The
patches have been generated by git-dpm, so I believe they should match
exactly...
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
