Fwd: Build Error (Job 5006): sdlmame-data-0134-1_fc12 on fedora-development-rpmfusion_nonfree

[Julian Sikorski]

W dniu 19.09.2009 21:50, Mamoru Tasaka pisze:
> Julian Sikorski wrote, at 09/20/2009 04:12 AM +9:00:
>> Hi,
>>
>> I have no idea what is going on here. It says unrar not found, but it
>> gets installed according to root.log. Please help.
>>
>> Julian
>>
>> ------ Wiadomość oryginalna ------
>> Temat: Build Error (Job 5006): sdlmame-data-0134-1_fc12 on
>> fedora-development-rpmfusion_nonfree
>> Data: Sat, 19 Sep 2009 21:10:30 +0200 (CEST)
>> Nadawca:
>> rpmfusion-buildsys at lists.rpmfusion.org
>> Adresat: belegdol at gmail.com
>>
>> Job failed on arch noarch
>>
>>          Build logs may be found at
>> http://buildsys.rpmfusion.org/logs/fedora-development-rpmfusion_nonfree/5006-sdlmame-data-0134-1.fc12/
>>
>>
>> -------------------------------------------------
>>
> 
> <snip>
> 
>> + unrar x /builddir/build/SOURCES/ctrlr.rar
>> /builddir/build/BUILDROOT/sdlmame-data-0134-1.fc12.noarch/usr/share/mame
>> /var/tmp/rpm-tmp.pTsqn7: line 38: unrar: command not found
>> RPM build errors:
>> error: Bad exit status from /var/tmp/rpm-tmp.pTsqn7 (%install)
>>     Bad exit status from /var/tmp/rpm-tmp.pTsqn7 (%install)
>> Child returncode was: 1
>> EXCEPTION: Command failed. See logs for output.
> 
> My first guess is that from root.log:
> ------------------------------------------------------------------
> DEBUG util.py:256:  /var/tmp/rpm-tmp.kgoj5Y: line 2:
> /usr/sbin/alternatives: No such file or directory
> ------------------------------------------------------------------
> 
> On my system (with unrar reinstalled for sure) /usr/bin/unrar is
> a symlink created by alternatives mechanism. However on this build
> due to /usr/sbin/alternatives (in chkconfig) missing this symlink was
> not correctly created. (note that in unrar binary rpm /usr/bin/unrar has
> 0 size).
> 
> Note that every package calling /usr/sbin/alternatives should have
> Requires(post): /usr/sbin/alternatives and so on.
> 
> Regards
> Mamoru
> 
OK, looks like a bug in unrar then. It worked on other branches, though,
so the difference in packaging between those must be the culprit.
Who's the unrar maintainer?

Julian