Sean Whitton writes ("Bug#869146: dgit: should never add .orig to the .changes
more than once"):
> On Tue, Jun 26 2018, Ian Jackson wrote:
> > Of course if you had followed dgit's advice you would not have
> > experienced this but :-)
>
> I must have been sure
Hello,
On Tue, Jun 26 2018, Ian Jackson wrote:
> Of course if you had followed dgit's advice you would not have
> experienced this but :-)
I must have been sure that dgit was wrong to tell me to do that in this
case. Next time it comes up for me, I'll file a bug saying exactly why
I think the
Ian Jackson writes ("dgit: should never add .orig to the .changes more than
once"):
> Anyway, I will fix the bug.
Having investigated, I have discovered that this might also happen if
you didn't use dgit build, and whatever build process you used
included some .origs. dgit would probably try to
Control: tags -1 confirmed
I managed to repro this in the test suite by passing
-cdgit-distro.test-dummy.git-url=file:///dev/enoent/fail
(It's quite a lot of faff to arrange a situation where
--deliberately-include-questionable-history would help,
but when it is needed its lack also causes
Package: dgit
Version: 3.10
Severity: minor
Hello,
Today I did:
% dgit push --new
followed by:
% dgit push --new --deliberately-include-questionable-history
Each of these commands added the .orig to the .changes file, so I got a
non-fatal error from dput that ftp-master wouldn't let
5 matches
Mail list logo