[Bug 489926] New: build-compare: difference in .note.gnu.build-id and .gnu_debuglink
https://bugzilla.novell.com/show_bug.cgi?id=489926 Summary: build-compare: difference in .note.gnu.build-id and .gnu_debuglink Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: coolo@novell.com ReportedBy: vuntz@novell.com QAContact: qa@suse.de Found By: --- Here's a build-compare output from vinagre in GNOME:Factory compare /.build.oldpackages/vinagre-2.26.0-22.2.src.rpm /usr/src/packages/SRPMS/vinagre-2.26.0-22.3 src.rpm compare /.build.oldpackages/vinagre-2.26.0-22.2.x86_64.rpm /usr/src/packages/RPMS/x86_64/vinagre-2. 26.0-22.3.x86_64.rpm /usr/bin/vinagre differs in ELF sections --- /tmp/tmp.LPRRwLCWKg 2009-03-21 18:40:00.000000000 +0000 +++ /tmp/tmp.YvCffRVmqh 2009-03-21 18:40:00.000000000 +0000 @@ -12,8 +12,8 @@ 400284 00000000 01000a02 ........ Contents of section .note.gnu.build-id: 40028c 04000000 14000000 03000000 474e5500 ............GNU. - 40029c a7587db9 36f3be3f a739d816 1adc9f78 .X}.6..?.9.....x - 4002ac 09829141 ...A + 40029c 1a92b19b 91f18bdc 9a6ce72b 8fa4d0a7 .........l.+.... + 4002ac d98bd033 ...3 Contents of section .hash: 4002b0 09020000 31020000 00000000 00000000 ....1........... 4002c0 00000000 19010000 00000000 1b010000 ................ @@ -11309,4 +11309,4 @@ 0000 4f735057 4700 OsPWG. Contents of section .gnu_debuglink: 0000 76696e61 6772652e 64656275 67000000 vinagre.debug... - 0010 6a768cc6 jv.. + 0010 ba6084b8 .`.. As far as I can tell, it's expected that .note.gnu.build-id is different. See: http://en.opensuse.org/Build_ID http://fedoraproject.org/wiki/Releases/FeatureBuildId#Unique_build_ID http://sources.redhat.com/gdb/current/onlinedocs/gdb_17.html#SEC166 So this section should probably be ignored. As for the .gnu_debuglink part, what's different is the checksum. My understanding is that the different build id could cause the different checksum. Not sure if it's enough to ignore it, though... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489926
User vuntz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=489926#c1
--- Comment #1 from Vincent Untz
https://bugzilla.novell.com/show_bug.cgi?id=489926
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=489926#c2
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=489926
User vuntz@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=489926#c3
--- Comment #3 from Vincent Untz
What's different in glibc are the sources. glibc generates several files with build dates in there. What makes this hard to understand for the one looking at the logs is that you only see the first diff - and that's very often the buildid.
s/glibc/glib/ ;-) But you're probably right here.
For vinagre I would think it's the actual binary that's different due to different includes or libraries. So if you'd look past the different build ids, you would see different assembler - otherwise the build id wouldn't be different as it's a hash over the assembler (ok, compiled assembler).
Hrm. But the assembler output is before the elf sections output. So if build-compare doesn't find a difference in the assembler but find one in the elf sections only for the build id, then I have the feeling it's doing something wrong. (and this is happening for really a lot of packages, fwiw) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=489926
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=489926#c4
--- Comment #4 from Stephan Kulow
participants (1)
-
bugzilla_noreply＠novell.com