Re: Same hashfiles for files that should be different from each other?

["Thomas Schmitt" <scdbackup@gmx.net>]

Hi,

i wrote:
> > The same checksum duplicity can be seen with
> >   5849124a0e25d1318a880e98b9a8123f debian-live-9.8.0-amd64-cinnamon.contents
> >   5849124a0e25d1318a880e98b9a8123f debian-live-9.8.0-amd64-gnome.contents

Andy Simpkins <rattusrattus@debian.org> wrote:
> That is exactly what Kuijpers has just pointed out.

Evert Kuijpers pointed to "lxde" and "mate" on "i386" and "amd64".
My run of program "sort" reveiled that "cinnamon" and "gnome" form a pair,
too (at least on "amd64").


> the issue could be in one of several places. [...]
> (2) we are building the content of the ISOs
> correctly, but incorrectly reporting the manifest

This can be ruled out.
I downloaded debian-live-9.8.0-amd64-lxde.iso and
debian-live-9.8.0-amd64-mate.iso. Mounted them at /mnt/iso and compared
the outputs of
  find /mnt/iso | sed -e 's/^\/mnt\/iso//' | sort

They are identical.

The results of "find" differ from the identical .content files only by
the paths "/isolinux/boot.cat", for which there is a plausible explanation
in the ISO production process.


> (3) we are reporting the
> manifest correctly and we are reporting incorrect checksums

This can be ruled out.
"md5sum" confirms the MD5s. "diff" confirms that the .content files have
identical content.


Have a nice day :)

Thomas