I was able to get past this error after removing the output of md5sum in
debian/rules. But, I still see the following TAR related errors when the
build process attempts to do DPKG_DEB. I think these errors are trivial and
wanted to know if there is any way DPKG_DEB can ignore these errors from
TAR?
Thanks
Dinesh
cd debian/tmp && \
md5sum `find * -type f ! -regex "DEBIAN/.*"`
83d871499a66bef9a295f4b7e9333bf3 usr/share/doc/zip/copyright
741a5c7cd7d38417ba05aa4f0b9e2554 usr/share/doc/zip/CHANGES.gz
e5b8342076d84aee71423a253875bfcb usr/share/doc/zip/TODO
73d46099c25930311f8b1417d3ad0561 usr/share/doc/zip/WHATSNEW
218d337bd2f0c8cc3a63ee139dccbc75 usr/share/doc/zip/changelog.Debian.gz
7ba24ed1067fd4c6ebfb6d914673b1b0 usr/share/man/man1/zip.1.gz
a25e39fa3841b916837f96a329f24a31 usr/bin/zip
77f920e0022dd0d4880faecb3ecb0c4b usr/bin/zipnote
ae232328473d4b5eac135c5bdd12a58f usr/bin/zipsplit
fc6fc0d50fb52fa78d58120e53fd2ff0 usr/bin/zipcloak
chown -R root:root debian/tmp
chmod -R u+w,go=rX debian/tmp
dpkg --build debian/tmp ..
dpkg-deb: building package `zip' in `../zip_2.32-1_armel.deb'.
tar: ./usr/share/doc/zip/copyright: file changed as we read it
tar: ./usr/share/doc/zip/CHANGES.gz: file changed as we read it
tar: ./usr/share/doc/zip/TODO: file changed as we read it
tar: ./usr/share/doc/zip/WHATSNEW: file changed as we read it
tar: ./usr/share/doc/zip/changelog.Debian.gz: file changed as we read it
tar: ./usr/share/man/man1/zip.1.gz: file changed as we read it
tar: ./usr/bin/zip: file changed as we read it
tar: ./usr/bin/zipnote: file changed as we read it
tar: ./usr/bin/zipsplit: file changed as we read it
tar: ./usr/bin/zipcloak: file changed as we read it
dpkg-deb: subprocess tar -cf returned error exit status 1
make: *** [binary-arch] Error 2
dpkg-buildpackage: failure: fakeroot debian/rules binary gave error exit
status 2
On Mon, Jul 21, 2008 at 1:32 PM, Dinesh D <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I was compiling the "Zip" library - the unstable SID version, using
> dpkg-buildpackage -rfakeroot.
> I got the following error, and was wondering if anyone would have seen it
> before:
>
> *Error: File ./md5sums changed as we read it.*
>
> I do see the DEB file generated, but the file is empty (0 bytes). I sense I
> am pretty close to generating the DEB file, but am not sure how to correct
> the last error.
>
> Any help would be appreciated,
> Thanks
> Dinesh
>
>
