hi jakub,

that out of the way, let's look at the other one:

On Sat, Jun 08, 2013 at 12:03:48AM +0200, Jakub Wilk wrote:
> --- check_0.9.10-1_i386/usr/include/check_stdint.h    2013-06-07 
> 13:37:33.000000000 +0200
> +++ check_0.9.10-1_armel/usr/include/check_stdint.h   2013-06-07 
> 14:52:41.000000000 +0200
> @@ -2,7 +2,7 @@
>  #define _CHECK_CHECK_STDINT_H 1
>  #ifndef _GENERATED_STDINT_H
>  #define _GENERATED_STDINT_H "check 0.9.10"
> -/* generated using gnu compiler gcc (Debian 4.7.3-4) 4.7.3 */
> +/* generated using gnu compiler gcc (Debian 4.6.4-2) 4.6.4 */
>  #define _STDINT_HAVE_STDINT_H 1
>  #include <stdint.h>
>  #endif

as you can see the two files are effectively identical, it is only a
comment that differs. is that actually a problem for multi-arch, or is
it just a false positive of the test?

if this is a problem, then I am not sure how to fix it. of course I
could patch out that line after creating the file, but it seems a bit
hackish to do that. essentially it boils down to the fact that no
Multi-Arch: same packages may ever contain any file that differs based
on where/when it is built. I could imagine that is quite a lot of
packages, e.g. build timestamps seem to be quite popular. in this case
this file is generated by autotools, again I would assume quite a few
libraries use the same macro...

regards  robert

-- 
Robert Lemmen                               http://www.semistable.com 

Attachment: signature.asc
Description: Digital signature

Reply via email to