On Fri, Mar 02, 2012 at 07:44:48AM +0900, Norbert Preining wrote:
> On Do, 01 Mär 2012, Julian Andres Klode wrote:
> > > dpkg-source: info: local changes detected, the modified files are:
> > >  texlive-bin-2011.20120226/configure
> > >  texlive-bin-2011.20120226/libs/gd/configure
> > >  texlive-bin-2011.20120226/texk/afm2pl/configure
> > >  texlive-bin-2011.20120226/texk/bibtex8/configure
> > >  ...
> > 
> > > 
> > > So I suppose that dh_autoreconf* should fix the above errors, but it 
> > > didn't.
> > > 
> > > I suppose there is something I have overlooked completely.
> > 
> > It should remove those files if they were changed by the command executed
> > by dh_autoreconf and they're not symbolic links[1]. You could grep the
> > before and after lists for those files and check that the checksums are
> > different. In order to be removed, a file must have one of the following:
> 
> Ok, from what you wrote I guess that dh_reautoconf is *removing* the
> files and relying on the fact that dpkg-source ignores removed files.
> So it does NOT revert changes I assume?

Correct. Playing the backup/restore game did not seem like a good
idea when I wrote the code, and deleting is just a more simple
way.

> 
> Anyway, as clearly seen above the files *have* been changed, but seems
> to not have been removed.

Yes. The only explanation I have is that the files were changed after
dh_autoreconf ran and not by the command ran by dh_autoreconf.

> 
> >     (a) not in the before list, but in the after list
> >     (b) different checksum in the after list
> 
> It seems that (b) didn't work out, since it clearly must have different
> checksums, as dpkg-source complained about modified files.
> 
> So how can one debug this?

As I wrote. A good starting point would be to run dh_autoreconf
and then check debian/autoreconf.{before,after}. You can send
them to me as well.

If you want to debug it yourself, dh_autoreconf_clean is the
script responsible for removing the files. It reads in the
debian/autoreconf.{before,after} files which have the format
        md5sum file

and builds a perl hash 
        file => md5sum
of the before state and then reads the after file and deletes
all files not in the old hash or where the checksum changed
compared to the old hash.
-- 
Julian Andres Klode  - Debian Developer, Ubuntu Member

See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to