[Mageia-dev] [RPM] cauldron core/release valgrind-3.6.1-3.mga2

Thu Jun 23 19:17:59 CEST 2011

Am 22.06.2011 21:45, schrieb Ahmad Samir:
+> On 22 June 2011 20:18, nicolas vigier<boklm at mars-attacks.org>  wrote:
+>> On Wed, 22 Jun 2011, Florian Hubold wrote:
+>>
+>>> Am 22.06.2011 07:40, schrieb Ahmad Samir:
+>>>> On 20 June 2011 11:24, Thierry Vignaud<thierry.vignaud at gmail.com>    wrote:
+>>>>> On 7 June 2011 16:10, Mageia Team<buildsystem-daemon at mageia.org>    wrote:
+>>>>>> dmorgan<dmorgan>    3.6.1-3.mga1:
+>>>>>> + Revision: 101519
+>>>>>> - Provide devel subpackage  ( partial merge of mdv commit 659516)
+>>>>> As always, when one moves files between subpackages or to a new subpackage,
+>>>>> conflicts tags should be added in order to ensure urpmi will put both packages
+>>>>> in the same transaction:
+>>>>>
+>>>>> Installation failed:
+>>>>>      file /usr/include/valgrind/memcheck.h from install of
+>>>>> valgrind-devel-3.6.1-3.mga2.x86_64 conflicts with file from package
+>>>>> valgrind-3.6.0-2.mga1.x86_64
+>>>>>      file /usr/lib64/pkgconfig/valgrind.pc from install of
+>>>>> valgrind-devel-3.6.1-3.mga2.x86_64 conflicts with file from package
+>>>>> valgrind-3.6.0-2.mga1.x86_64
+>>>>>
+>>>> Done.
+>>>>
+>>> Minor nitpick: BuildRequires for xulrunner were changed after the split,
+>>> for firefox5 not.
+>>> Is there any special reason for this? Just wondering ...
+>> Because the devel files are now in valgrind-devel.
+Yes, i know about the split, you told me in IRC ;)
+>>
+> Yeah, there're two types of BR here, just 'valgrind' if the build
+> requires only the binary (/usr/bin/valgrind) and valgrind-devel if the
+> build requires the valgrind header files; AFAICS for firefox, it
+> doesn't require the valgrind headers (i.e. I don't see any checks for
+> the headers failing in the build log).
+>
+Alright, just wanted to mention it. Could also have been an oversight ...
+