* Robert Lemmen <rober...@semistable.com>, 2013-06-10, 17:50:
--- 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?
It's a real problem. If you try to install check:i386 and check:armel,
you get this:
Unpacking check:armel (from .../check_0.9.10-1_armel.deb) ...
dpkg: error processing /var/cache/apt/archives/check_0.9.10-1_armel.deb
(--unpack):
trying to overwrite shared '/usr/include/check_stdint.h', which is different
from other instances of package check:armel
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
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,
That's what I would do, too. :)
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.
Indeed.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
