On Thu, Feb 19, 2015 at 8:28 AM, Dave Johansen <davejohansen@xxxxxxxxx> wrote:
On Wed, Feb 18, 2015 at 9:54 AM, Marcin Juszkiewicz <mjuszkiewicz@xxxxxxxxxx> wrote:On 18.02.2015 16:31, Miroslav Suchý wrote:
> On 02/18/2015 04:12 PM, Dave Johansen wrote:
>> I'm running into an issue where odb won't build on rawhide ( http://koji.fedoraproject.org/koji/taskinfo?taskID=8966447
>> ) and I need to be able to take a look at the config.log file but it's not available from the standard koji output.
>>
>> So what's the easiest way for me to get access to that file? Do I have to install rawhide in a virtual machine and do
>> the build myself? Or is there a simpler way to get access to other outputs from a build?
>
> mock -r fedora-rawhide-x86_64 --no-cleanup-after your.src.rpm
>
> and then investigate
> /var/lib/mock/fedora-rawhide-x86_64/root/builddir/build/BUILD/
>
> or
> mock -r fedora-rawhide-x86_64 --shell
> and you are inside of that build chroot.
For such situations I have simple script:
-----------------------------------------------------------------------------
#!/bin/bash
SRCRPM=$1
X=X
LC_ALL=C LANG=C mock $SRCRPM \
--resultdir=~mjuszkie/rpmbuild/mock/`basename $SRCRPM` \
--verbose \
--no-cleanup-after \
--uniqueext=$SRCRPM $2 && X=Y
if [ $X == X ]; then
echo ""
mock --shell --uniqueext=$SRCRPM $2
fi
mock --clean --uniqueext=$SRCRPM $2
-----------------------------------------------------------------------------
Use is simple: "hrwmock.sh *.src.rpm" (to change build target I just add
"-r fedora-21-aarch64").Using mock did the trick.
I'm looking into another issue on F22 but there's no .cfg for that. Is that still just coming down the pipeline since the branch just recently happened? Or is there a way I can manually create the .cfg file?
Thanks,
Dave
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
