<br><br><div class="gmail_quote">2009/8/3 Christian Krause <span dir="ltr"><<a href="mailto:chkr@fedoraproject.org">chkr@fedoraproject.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi,<br>
<div class="im"><br>
Paul Lange wrote:<br>
> Am Sonntag, den 02.08.2009, 19:29 +0200 schrieb David Nielsen:<br>
>> 2009/8/2 Paul Lange <<a href="mailto:palango@gmx.de">palango@gmx.de</a>><br>
</div><div class="im">>> I'm trying to update boo to the latest version (0.9.1).<br>
>><br>
>> Most things work fine but I get a strange stacktrace while<br>
>> trying to<br>
>> register some assemblies into the gac.<br>
>><br>
>> You can find the src-rpm package and the mock build.log here:<br>
>> <a href="http://palango.fedorapeople.org/boo/" target="_blank">http://palango.fedorapeople.org/boo/</a><br>
>><br>
</div><div class="im">>> does gacutil fail on your system if you invoke it manually to test?<br>
><br>
> I have to build it with mock because the build with rpmbuild didn't work<br>
> because of some boo 0.8.1 stuff in the gac.<br>
<br>
</div>Probably you could just de-install the boo 0.8.1 temporarily and use<br>
then rpmbuild for testing purposes...<br>
<div class="im"><br>
> So I don't know if I can run commands in mock to test. However 'gacutil'<br>
> works when I run it without parameters.<br>
<br>
</div>IMHO there are 2 options:<br>
<br>
- When I was hunting issues which only appeared in mock, I've just added<br>
some test commands directly to the spec file of the package.<br>
<br>
- Additionally you could run mock with the "--no-cleanup-after" command<br>
and later use "mock --shell" to get a shell within the chroot<br>
environment. Then you can try e.g. the problematic gacutil command manually.</blockquote><div><br></div><div>If the problem is that it finds an older boo in the gac why now simply use gacutil to uninstall it prior to the build?</div>
<div><br></div><div>something like:</div><div>gacutil -u path-to-boo.dll -f -boo -root %{buildroot}%{_libdir}</div><div><br></div><div>or am I misunderstanding the current path of debugging?</div></div>