Re: dpkg-source --commit fails to find local changes
Hi!
On Sun, 2014-08-17 at 14:43:47 +0200, Sebastian Ramacher wrote:
> Package: dpkg-dev
> Version: 1.17.11
> Severity: important
> Control: submitter -1 Neil Williams <codehelp@debian.org>
> On 2014-08-15 17:49:53, Guillem Jover wrote:
> > On Fri, 2014-08-15 at 15:34:09 +0100, Neil Williams wrote:
> > > I'm unable to get dpkg-source to see that I have changed files in a
> > > python source package format 3.0 (quilt):
> > >
> > > dpkg-source: info: there are no local changes to record
> > >
> > > No matter what I seem to do inside the json-schema-validator package,
> > > dpkg refuses to spot the change, even renaming the package in setup.py
> > > or changing the .py files. I get no warning on building and I have to
> > > create the patch manually.
> > >
> > > Is this a regression or is there something different about the
> > > json-schema-validator and versiontools packages?
> > >
> > > This happened with 1.17.11 and 1.17.12.
> >
> > This looks like it might be a regression yes, I'm checking the obvious
> > culprits now.
>
> I'm turning this into a bug report. Today I've encountered the same bug
> and wondered what's wrongs since there is nothing in the BTS.
>
> I've bisected the commits between 1.17.10 and 1.17.12 and it seems that
> changes detection is broken since
> 543ac69d2470e39f6b95a59b82fee116bc1b90d7.
Yeah, thanks, had already fixed this yesterday, but when I got time to
prepare the release was quite late and I was too tired to operate
correctly. :) Will be uploading now.
Thanks,
Guillem
Reply to: