Bug#975207: trapperkeeper-scheduler-clojure: FTBFS: Could not locate schema/utils__init.class, schema/utils.clj or schema/utils.cljc on classpath.

[Lucas Nussbaum]

Source: trapperkeeper-scheduler-clojure
Version: 0.1.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> mkdir test/target
> (cd test && find . -name "*.clj" | \
> 	xargs --verbose clojure -cp /<<PKGBUILDDIR>>/trapperkeeper-scheduler.jar:/usr/share/java/clojure.jar:/usr/share/java/trapperkeeper.jar:/usr/share/java/kitchensink.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/at-at.jar:/usr/share/java/tools.namespace.jar:/usr/share/java/trapperkeeper-test.jar:/usr/share/java/kitchensink-test.jar)
> clojure -cp /<<PKGBUILDDIR>>/trapperkeeper-scheduler.jar:/usr/share/java/clojure.jar:/usr/share/java/trapperkeeper.jar:/usr/share/java/kitchensink.jar:/usr/share/java/prismatic-schema.jar:/usr/share/java/at-at.jar:/usr/share/java/tools.namespace.jar:/usr/share/java/trapperkeeper-test.jar:/usr/share/java/kitchensink-test.jar ./integration/puppetlabs/trapperkeeper/services/scheduler/scheduler_service_test.clj ./unit/puppetlabs/trapperkeeper/services/scheduler/scheduler_core_test.clj
> Syntax error (FileNotFoundException) compiling at (plumbing/core.clj:1:1).
> Could not locate schema/utils__init.class, schema/utils.clj or schema/utils.cljc on classpath.
> 
> Full report at:
> /tmp/clojure-10791242790452340697.edn
> make[1]: *** [debian/rules:35: override_dh_auto_test] Error 123

The full build log is available from:
   http://qa-logs.debian.net/2020/11/19/trapperkeeper-scheduler-clojure_0.1.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.