Automatic AArch64 bootstrap daily update for May 11, 2013

[Brendan Conoboy]

Number of candidate source rpms: 13348

Number of source rpms built in stage 4: 8503

Number of packages built in stage4 with aarch64 components: 2114

Currently building packages
ClanLib-2.3.6-9.fc19.src.rpm
atlas-3.8.4-8.fc19.src.rpm
drgeo-1.1.0-24.fc19.src.rpm
dump-0.4-0.19.b44.fc19.src.rpm
e16-1.0.11-2.fc19.src.rpm
fence-agents-4.0.0-3.fc19.src.rpm
freenx-server-0.7.3-31.fc19.src.rpm
gdb-7.6-28.fc19.src.rpm
gpsd-3.8-1.fc19.src.rpm
isns-utils-0.93-2.fc19.src.rpm
jansson-2.4-2.fc19.src.rpm
liblouis-2.5.2-3.fc19.src.rpm
mariadb-5.5.30-1.fc19.src.rpm
mate-polkit-1.6.0-1.fc19.src.rpm
mingw-binutils-2.23.52.0.1-1.fc19.src.rpm
nano-2.3.1-7.fc19.src.rpm
nas-1.9.3-6.fc19.src.rpm
nc6-1.0-16.fc19.src.rpm
perl-B-Utils-0.21-4.fc19.src.rpm
perl-PDF-Haru-1.00-9.fc19.src.rpm
perl-Socket-GetAddrInfo-0.19-4.fc19.src.rpm
perl-Sys-Syslog-0.32-1.fc19.src.rpm
perl-Taint-Runtime-0.03-18.fc19.src.rpm
perl-XML-LibXML-2.0014-2.fc19.src.rpm
perl-mecab-0.996-1.fc19.src.rpm
python-ethtool-0.8-1.fc19.src.rpm
python-mwlib-0.14.3-1.fc19.src.rpm
python-simplejson-3.1.3-1.fc19.src.rpm
rubygem-krb5-auth-0.7-9.fc19.src.rpm
sombok-2.2.1-3.fc19.src.rpm
trac-xmlrpc-plugin-1.2.0-0.4.r10183.fc19.src.rpm
trytond-account-invoice-line-standalone-2.6.0-2.fc19.src.rpm
ucarp-1.5.2-8.fc19.src.rpm
urlwatch-1.15-4.fc19.src.rpm
usermode-1.111-2.fc19.src.rpm
vim-command-t-1.4-4.fc19.src.rpm
wiggle-0.8-5.fc19.src.rpm
wmpager-1.2-1.20130401git88ece7e5.fc19.src.rpm
wqy-bitmap-fonts-1.0.0-0.5.rc1.fc19.src.rpm
xkeyboard-config-2.8-1.fc19.src.rpm
xorg-x11-fonts-7.5-8.fc19.src.rpm

Packages building since previous report (which might be stuck or crashed)
atlas-3.8.4-8.fc19.src.rpm
drgeo-1.1.0-24.fc19.src.rpm
gdb-7.6-28.fc19.src.rpm
mariadb-5.5.30-1.fc19.src.rpm
usermode-1.111-2.fc19.src.rpm
wiggle-0.8-5.fc19.src.rpm

Total current build failure count: 606 failed

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

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

Naive Top 10 dependency issues
     18 doxygen
      8 gpm-1.20.6-29.fc19.aarch64 (stage4) linuxconsoletools
      6 asciidoc-8.6.8-1.fc19.noarch (stage4) graphviz vim-filesystem
      5 java-devel
      5 cim-server sblim-cmpi-base-1.6.2-2.fc19.aarch64 (stage4)
      4 java-devel >= 1:1.6.0
      4 fakeroot rpmdevtools-8.3-3.fc19.noarch (stage4)
      4 /usr/include/pcap.h
      3 gtk2-devel
      3 ghostscript-fonts-5.50-30.fc19.noarch (stage4) urw-fonts-2.4-14.fc19.noarch
(stage4) xorg-x11-font-utils

Previously broken builds that are now fixed:
dlm-4.0.1-1.x1.fc19
libaccounts-glib-1.8-1.fc19
libgtop2-2.28.4-4.fc19
liblangtag-0.4.0-3.fc19
librcc-0.2.10-1.fc19
libwiimote-0.4-13.fc19
libyuv-0-0.19.20121221svn522.fc19
perl-version-0.99.02-1.fc19

Newly attempted builds that failed:
archimedes-2.0.0-3.fc18
cddlib-094g-8.fc19
cln-1.3.2-6.fc19.1
compat-gcc-296-2.96-145
ctdb-2.1-2.fc19
curlpp-0.7.3-13.fc19
device-mapper-persistent-data-0.1.4-3.fc19
dracut-027-36.git20130418.fc19
flint-1.6-6.fc19
fontconfig-2.10.92-3.fc19
gappa-0.16.6-1.fc19
globus-core-8.9-3.fc19
jack-audio-connection-kit-1.9.9.5-2.x1.fc19
krb5-appl-1.0.3-4.fc19
ladvd-1.0.4-3.fc19
libindicator-0.4.94-4.fc19
ltrace-0.7.2-5.fc19
lua-event-0.4.3-2.fc19
mailman-2.1.15-12.fc19
mate-conf-1.4.0-22.fc19
pari-2.5.3-2.fc19
perl-Class-Load-XS-0.06-2.fc19
perl-Crypt-OpenSSL-Bignum-0.04-17.fc19
perl-Crypt-OpenSSL-X509-1.800.2-6.fc19
perl-Crypt-Rijndael-1.11-2.fc19
perl-Crypt-SMIME-0.10-4.fc19
perl-Digest-JHash-0.07-6.fc19
perl-FileHandle-Fmode-0.09-17.fc19
perl-HTML-Strip-1.06-11.fc19
perl-JSON-XS-2.33-2.fc19
perl-Mail-Box-Parser-C-3.007-1.fc19
perl-Math-FFT-1.28-12.fc19
perl-Math-Random-MT-Auto-6.22-2.fc19
perl-PAR-Packer-1.014-2.fc19
perl-Params-Util-1.07-5.fc19
perl-PerlIO-eol-0.14-16.fc19
perl-Perlbal-XS-HTTPHeaders-0.20-10.fc19
perl-YAML-LibYAML-0.41-1.fc19
perl-autovivification-0.11-1.fc19
pp3-1.3.3-7.fc18
python-cheetah-2.4.4-4.fc19
python-pysctp-0.3.1-14.fc19
rubygem-gherkin-2.11.6-2.fc19
sectool-0.9.5-10.fc19
ssldump-0.9-0.7.b3.fc19
system-config-audit-0.4.21-2.fc19
tig-1.0-3.fc19
tlomt-orbitron-fonts-1.000-7.fc19
trac-iniadmin-plugin-0.2-5.20120808svn11914.fc19
trac-mercurial-plugin-1.0.0.1-1.fc19
trac-xmlrpc-plugin-1.2.0-0.4.r10183.fc19
tryton-2.6.1-3.fc19
trytond-analytic-purchase-2.6.1-2.fc19
trytond-stock-location-sequence-2.6.0-2.fc19
typemade-josefinsansstd-light-fonts-1.000-7.fc19
v8-3.14.5.8-1.fc19
vegastrike-data-0.5.1-3.r1.fc19
vollkorn-fonts-2.1-2.fc19
weld-parent-17-7.fc19
werken-xpath-0.9.4-10.beta.12.4.fc19
wine-docs-1.4-2.fc18
wmclock-1.0.14-3.fc19
ws-commons-util-1.0.1-26.fc19
xorg-x11-twm-1.0.7-4.fc19
xorg-x11-xsm-1.0.2-21.fc19
xpp2-2.1.10-15.fc19
xpp3-1.1.3.8-8.fc19
zhcon-0.2.6-22.fc19
zsh-5.0.2-2.fc19

[Mark Salter]

On Sat, 2013-05-11 at 08:05 -0400, Brendan Conoboy wrote:

>  Packages building since previous report (which might be stuck or
> crashed)
>  atlas-3.8.4-8.fc19.src.rpm
>  drgeo-1.1.0-24.fc19.src.rpm
>  gdb-7.6-28.fc19.src.rpm
>  mariadb-5.5.30-1.fc19.src.rpm 
mariadb is churning along on one of my builders. Should be done today.

>  usermode-1.111-2.fc19.src.rpm
>  wiggle-0.8-5.fc19.src.rpm 
Why isn't gcc on this list? I had been working on this, but after the
last failure a few days ago, I patched it and requeued it. Some other
builder grabbed it before I could, so I have lost track of it, but I
suspect it is building somewhere. Maybe it is detected as a failure.

>  Naive Top 10 dependency issues
>       18 doxygen
>        8 gpm-1.20.6-29.fc19.aarch64 (stage4) linuxconsoletools
>        6 asciidoc-8.6.8-1.fc19.noarch (stage4) graphviz vim-filesystem
>        5 java-devel
>        5 cim-server sblim-cmpi-base-1.6.2-2.fc19.aarch64 (stage4)
>        4 java-devel >= 1:1.6.0
>        4 fakeroot rpmdevtools-8.3-3.fc19.noarch (stage4)
>        4 /usr/include/pcap.h
>        3 gtk2-devel
>        3 ghostscript-fonts-5.50-30.fc19.noarch (stage4) urw-fonts-2.4-14.fc19.noarch
> (stage4) xorg-x11-font-utils 
This list is inaccurate for some reason. gtk2-devel has been available
since April 29. xorg-x11-font-utils has been around since May 7.

[Brendan Conoboy]

On 05/11/2013 10:36 AM, Mark Salter wrote:
>  Why isn't gcc on this list? I had been working on this, but after
> the
>  last failure a few days ago, I patched it and requeued it. Some other
>  builder grabbed it before I could, so I have lost track of it, but I
>  suspect it is building somewhere. Maybe it is detected as a failure. 
Yes, build failed with the following error:

g++   -g -DIN_GCC   -fno-exceptions -fno-rtti 
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings 
-Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long 
-Wno-variadic-macros -Wno-overlength-strings   -DHAVE_CONFIG_H 
-DGENERATOR_FILE  -o build/gengtype \
     build/gengtype.o build/errors.o build/gengtype-lex.o 
build/gengtype-parse.o build/gengtype-state.o build/version.o 
../build-aarch64-redhat-linux/libiberty/libiberty.a
build/gengtype.o: In function `create_optional_field_':
/builddir/build/BUILD/gcc-4.8.0-20130507/obj-aarch64-redhat-linux/gcc/../../gcc/gengtype.c:963:

undefined reference to `lexer_line'

>  This list is inaccurate for some reason. gtk2-devel has been
> available
>  since April 29. xorg-x11-font-utils has been around since May 7. 
It's not so much inaccurate as it is naive.  The builds failed because 
of those dependencies.  If they're filled now the enqueueing script will 
send them back into the fray.  Until the rebuild is complete or failed, 
it will currently display the complete set of dependency issues that 
caused the build to fail previously.  There are 206 builds in the queue 
right now, so it'll be a day or two before everything whose dependencies 
are fulfilled actually gets a new build attempt.  The script could stand 
to be improved.

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

[Mark Salter]

On Sun, 2013-05-12 at 20:15 -0700, Brendan Conoboy wrote:
>  On 05/11/2013 10:36 AM, Mark Salter wrote:
>  > Why isn't gcc on this list? I had been working on this, but after the
>  > last failure a few days ago, I patched it and requeued it. Some other
>  > builder grabbed it before I could, so I have lost track of it, but I
>  > suspect it is building somewhere. Maybe it is detected as a failure.
>  
>  Yes, build failed with the following error: 
Right, and I fixed that and requeued it but another builder grabbed it
before I could. Since there are no newer build logs for that package
I assume it is still building somewhere. Either that or the builder that
grabbed it crashed/stopped without updating the build logs.

There really isn't any way to tell if something that previously failed
is currently being rebuilt. I wish we had a daemon on the builders to
check in with something on the server periodically so that we know for
sure what builds are currently in progress. I'll have to wait until end
of this week to know for certain about gcc.