+++ Thibaut Paumard [2014-03-10 10:59 +0100]: > Hi, > > Le 10/03/2014 10:45, Andrey Rahmatullin a écrit : > > On Mon, Mar 10, 2014 at 10:19:29AM +0100, Thibaut Paumard wrote: > >> What I would try is to compile the package on two distinct architectures > >> (or more) and compare the result. That would work unless the build for > >> these files is non-deterministic or includes timestamps or information > >> on the build machine. > > ... or files can be same on some different architectures and different on > > others (e.g. because of endianness). > > Thanks for clarifying that. Indeed you need to check the files at least > on a 32bit arch, a 64bit arch, a little-endian arch and a big-endian arch. > > Actually one way to go would be to upload the package without making the > split, downloading all the binaries, and comparing the files. This is > easier than manually building on porterboxes and covers all the > architectures on which the package compiles.
This service exists to help you find such issues: http://dedup.debian.net/ So far as I know it only works on things already uploaded to the archive, so you can't use it to check things are correct before the first upload. But I could be wrong - check the wiki. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140310105007.gq10...@stoneboat.aleph1.co.uk
