2011/10/3 solarflow99 <[email protected]>: > I have a strange problem here, my package will build fine, but if anyone > tries to run it, the dam thing just hangs. > I can build in mock on my own system and it runs just fine. Others are > starting to report this bug against the package so know its not just me. > > https://bugzilla.rpmfusion.org/show_bug.cgi?id=1959 > > > I can compare the binary is different from rpmfusion and my own build: > > 1828572 Oct 3 02:39 /usr/bin/dosemu.bin > 1834428 Sep 9 01:07 /usr/bin/dosemu.bin - The bad one from rpmfusion > build > > The build logs seem almost identical. Does anyone know why there might be > something different? Are all updates applied on the builder? I see some > minor version differences, however the bad binary was compiled almost a > month ago. > > Any suggestions at all?
Does this appear on all target or only for F-16 ? Can you resubmit a job? build.log can be the same but root.log are probably not. That's a more probable path before to consider a problem on the builder. Right now we have the updates-testing repository enabled. This probably shouldn't be kept. This has helped a lot when building kernel modules and others packages that would have needed an override, but has leaded to issues with packages hardcode a matching version (perl qt mostly). Nicolas (kwizart)
