Description of problem: VAD Sticker vad_dav.xml creation... VAD Sticker vad_fs.xml creation... Virtuoso.ini creation... Waiting Virtuoso Server start on port 1111... PASSED: Virtuoso Server successfully started on port 1111 ***FAILED: starting DB.DBA.VAD_PACK('vad_fs.xml', '.', 'rdf_mappers_filesystem.vad') ***FAILED: starting commit work ***FAILED: starting checkpoint ***FAILED: starting DB.DBA.VAD_PACK('vad_dav.xml', '.', 'rdf_mappers_dav.vad') ***FAILED: starting commit work ***FAILED: starting checkpoint Shutdown Virtuoso Server... chmod: cannot access `rdf_mappers_dav.vad': No such file or directory ===================================================================== = Checking log file /builddir/build/BUILD/virtuoso-opensource-6.1.3/binsrc/rdf_mappers/make_rdf_mappers_vad.log for statistics: = = Total number of tests PASSED : 1 = Total number of tests FAILED : 6 = Total number of tests ABORTED : 0 Version-Release number of selected component (if applicable): virtuoso-opensource-6.1.3-1.fc16 How reproducible: always Steps to Reproduce: 1. ppc-koji build --scratch dist-f16 virtuoso-opensource-6.1.3-1.fc16.src.rpm 2. 3. Actual results: http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=259607
confirmed still occurs with 6.1.3-3 (with gawk4 patch), http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=299243 ):
*** Bug 749550 has been marked as a duplicate of this bug. ***
seems to be a 64bit problem only, ppc32 completed: http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=306634
What's your primary arch for ppc? 32 or 64bit? (Hoping perhaps we could get away with ExcludeArch: ppc in the short-term).
our primary arch is ppc64. But here are the packages that require virtuoso-opensource, those and its dependants need to be either patched to not require virtuoso or the need to be disabled, too: avogadro ghemical gnome-chemistry-utils kalzium kdeedu soprano xdrawchem At least soprano can't be removed from the ppc as we'd have to drop the whole KDE stack.
Fwiw, only soprano should depend on virtuoso-opensource according to my repo query (though there's a fair number of kde apps that pulls in soprano, and thus virtuoso indirectly). Anyway, I'll redouble my efforts to resolve this.
Short-term (hopefully) workaround it seems is to build with --disable-all-vads like older virtuoso builds did (that didn't FTBFS on ppc/ppc64), %changelog * Wed Nov 02 2011 Rex Dieter <rdieter> 6.1.4-2 - --disable-all-vads on ppc/ppc64 to workaround FTBFS (#725347) build underway: http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=311921
virtuoso-opensource-6.1.4-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/virtuoso-opensource-6.1.4-2.fc16
Package virtuoso-opensource-6.1.4-2.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing virtuoso-opensource-6.1.4-2.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-15428 then log in and leave karma (feedback).
virtuoso-opensource-6.1.4-2.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.