Automatic AArch64 bootstrap daily update for July 17, 2013

[Brendan Conoboy]

Number of candidate source rpms: 13606

Number of source rpms built in stage 4: 11280

Number of packages built in stage4 with aarch64 components: 4724

Currently building packages
Singular-3.1.5-5.fc19.src.rpm
alienarena-7.65-2.fc19.src.rpm
amsn-0.98.9-7.fc19.src.rpm
argyllcms-1.5.1-1.fc19.src.rpm
diet-2.8.1-5.fc19.src.rpm
dnf-0.3.7-1.gitf8bdc98.fc19.src.rpm
fmt-ptrn-1.3.21-5.fc19.src.rpm
globus-usage-3.1-6.fc19.src.rpm
gnomad2-2.9.6-6.fc19.src.rpm
gstreamer-plugins-fc-0.2-7.fc19.src.rpm
libaccounts-qt-1.6-2.fc19.src.rpm
libqxt-0.6.2-4.fc19.src.rpm
lv2-c++-tools-1.0.4-7.fc19.src.rpm
openstack-glance-2013.1-2.fc19.src.rpm
psimedia-1.0.3-11.fc19.src.rpm
python-cliapp-1.20130424-1.fc19.src.rpm
qbittorrent-3.0.9-1.fc19.src.rpm
qca2-2.0.3-5.fc19.src.rpm
qcodeedit-2.2.3-10.fc19.src.rpm
qcomicbook-0.9.0-2.fc19.src.rpm
qt-at-spi-0.3.1-4.fc19.src.rpm
tagainijisho-0.9.4-5.fc19.src.rpm
wt-3.2.3-2.fc19.src.rpm
xteddy-2.0.1-12.fc19.src.rpm

Packages building since previous report (which might be stuck or crashed)
Singular-3.1.5-5.fc19.src.rpm
alienarena-7.65-2.fc19.src.rpm
amsn-0.98.9-7.fc19.src.rpm
argyllcms-1.5.1-1.fc19.src.rpm
globus-usage-3.1-6.fc19.src.rpm
gnomad2-2.9.6-6.fc19.src.rpm
gstreamer-plugins-fc-0.2-7.fc19.src.rpm
libaccounts-qt-1.6-2.fc19.src.rpm
libqxt-0.6.2-4.fc19.src.rpm
lv2-c++-tools-1.0.4-7.fc19.src.rpm
psimedia-1.0.3-11.fc19.src.rpm
qbittorrent-3.0.9-1.fc19.src.rpm
qca2-2.0.3-5.fc19.src.rpm
qcodeedit-2.2.3-10.fc19.src.rpm
qcomicbook-0.9.0-2.fc19.src.rpm
qt-at-spi-0.3.1-4.fc19.src.rpm
tagainijisho-0.9.4-5.fc19.src.rpm
wt-3.2.3-2.fc19.src.rpm

Total current build failure count: 653 failed

Build failures from unsatisfied dependencies: 190 failed-dep-rpms
See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-dep-rpms for complete list.

Build failures after dependency resolution: 463 failed-build-rpms
See http://arm-temp.ausil.us/pub/fedora-arm/data/failed-build-rpms for complete list.

Naive Top 10 dependency issues
    192 ghc-Cabal-devel
    114 java-devel
    103 kdelibs4-devel
     81 kdelibs4-devel >= 4.10.4
     60 java-devel >= 1:1.6.0
     59 nodejs-devel
     43 mono-devel
     41 mingw32-gcc
     40 libkdegames-devel >= 4.10.4
     35 wxGTK-devel

Previously broken builds that are now fixed:
armacycles-ad-0.2.8.3.2-4.fc19
armacycles-ad-0.2.8.3.2-4.x1.fc19
globus-gfork-3.2-5.fc19
ibus-kkc-1.5.13-1.fc19
ibus-panel-extensions-1.4.99.20111207-6.fc19
ibus-rawcode-1.3.2-1.fc19
ibus-skk-1.4.1-4.fc19
ibus-typing-booster-0.0.32-1.fc19
perl-Sane-0.05-4.fc19
python-pbr-0.5.8-1.fc19
python-simplejson-3.2.0-1.fc19
zathura-0.2.2-1.fc19

Newly attempted builds that failed:
abrt-2.1.4-3.fc19
dsniff-2.4-0.15.b1.fc19
httpie-0.5.0-2.fc19
ibus-cangjie-1.0-3.fc19
ibus-sayura-1.3.2-1.fc19
initial-setup-0.3.6-2.fc19
js-of-ocaml-1.2-3.fc19
linkchecker-6.5-6.fc19
openstack-swift-1.8.0-2.fc19
python-traitsui-4.3.0-2.fc19
s3ql-1.13.2-1.fc19
tabled-0.5.1-0.5.g33595340.fc18
udis86-1.7.1-1.fc19
uhd-3.5.3-1.fc19

[Guy Streeter]

On 07/17/2013 07:08 AM, Brendan Conoboy wrote:
...
>  Packages building since previous report (which might be stuck or
> crashed) 
...
>  psimedia-1.0.3-11.fc19.src.rpm 
The psimedia build was stuck in the configure step on my system for about a
week before I noticed. I didn't have time to investigate further, as I needed
to reboot. Nothing in the logs gave any indication of the problem.

I don't have any idea even what this package is. Are there documented steps
for manually pulling and building a package for debugging the build?

--Guy

[Brendan Conoboy]

On 07/17/2013 07:50 AM, Guy Streeter wrote:
>  The psimedia build was stuck in the configure step on my system for
> about a
>  week before I noticed. I didn't have time to investigate further, as I needed
>  to reboot. Nothing in the logs gave any indication of the problem.
>
>  I don't have any idea even what this package is. Are there documented steps
>  for manually pulling and building a package for debugging the build? 
It's like any package, you can build it locally with mock, or rpmbuild, 
or run through the steps in the spec file by hand.  The arm-rebuild 
script just grabs packages from a queue, runs mock, and returns the result.

-- 
Brendan Conoboy / Red Hat, Inc. / blc(a)redhat.com

[Guy Streeter]

On 07/17/2013 09:53 AM, Brendan Conoboy wrote:
>  On 07/17/2013 07:50 AM, Guy Streeter wrote:
> > The psimedia build was stuck in the configure step on my system for about a
> > week before I noticed. I didn't have time to investigate further, as I needed
> > to reboot. Nothing in the logs gave any indication of the problem.
> >
> > I don't have any idea even what this package is. Are there documented steps
> > for manually pulling and building a package for debugging the build?
>  
>  It's like any package, you can build it locally with mock, or rpmbuild, or run
>  through the steps in the spec file by hand.  The arm-rebuild script just grabs
>  packages from a queue, runs mock, and returns the result.
>   
Part of my question was where to get the src rpm.

I have no idea how to use mock.

--Guy

[Brendan Conoboy]

On 07/17/2013 07:56 AM, Guy Streeter wrote:
>  Part of my question was where to get the src rpm. 
I suggest using the latest Fedora 19 source.  If you're an active Fedora 
developer use fedpkg and the f19 branch.  If you're not involved in 
Fedora, grab it from one of the Fedora mirrors or the koji server.  We 
are using the same source rpms as x86, so anything will work.

>  I have no idea how to use mock. 
Run "/usr/bin/mock -r stage4-aarch64 /path/to/package.src.rpm".  Mock 
will create a chroot under /var/lib/mock/stage4-aarch64/root where the 
complete list of dependencies will be installed.  Once the complete tree 
is setup, mock will loopback mount filesystems like /proc, chroot into 
the new directory tree, and run rpmbuild on the specified source rpm. 
The logs for what is taking place are stored in 
/var/lib/mock/stage4-aarch64/result, as well as the rpms if the build 
succeeds.

-- 
Brendan Conoboy / Red Hat, Inc. / blc(a)redhat.com