--- Comment #13 from idf31(a)protonmail.com ---
(In reply to leigh scott from comment #11)
The current srpm fails to build in mock or koji.
$ koji build --scratch f30 tty-clock-2.3-1.fc29.src.rpm
Uploading srpm: tty-clock-2.3-1.fc29.src.rpm
[====================================] 100% 00:00:00 14.34 KiB 38.07
KiB/sec
Created task: 32774225
Task info:
https://koji.fedoraproject.org/koji/taskinfo?taskID=32774225
Watching tasks (this may be safely interrupted)...
32774225 build (f30, tty-clock-2.3-1.fc29.src.rpm): free
32774225 build (f30, tty-clock-2.3-1.fc29.src.rpm): free -> open
(
buildvm-19.phx2.fedoraproject.org)
32774231 buildArch (tty-clock-2.3-1.fc29.src.rpm, s390x): free
32774230 buildArch (tty-clock-2.3-1.fc29.src.rpm, i686): free
32774232 buildArch (tty-clock-2.3-1.fc29.src.rpm, armv7hl): free
32774229 buildArch (tty-clock-2.3-1.fc29.src.rpm, aarch64): free
32774228 buildArch (tty-clock-2.3-1.fc29.src.rpm, ppc64le): free
32774227 buildArch (tty-clock-2.3-1.fc29.src.rpm, x86_64): free
32774231 buildArch (tty-clock-2.3-1.fc29.src.rpm, s390x): free -> open
(
buildvm-s390x-05.s390.fedoraproject.org)
32774230 buildArch (tty-clock-2.3-1.fc29.src.rpm, i686): free -> open
(
buildvm-05.phx2.fedoraproject.org)
32774229 buildArch (tty-clock-2.3-1.fc29.src.rpm, aarch64): free -> open
(
buildhw-aarch64-06.arm.fedoraproject.org)
32774228 buildArch (tty-clock-2.3-1.fc29.src.rpm, ppc64le): free -> open
(
buildvm-ppc64le-17.ppc.fedoraproject.org)
32774227 buildArch (tty-clock-2.3-1.fc29.src.rpm, x86_64): free -> open
(
buildvm-04.phx2.fedoraproject.org)
32774232 buildArch (tty-clock-2.3-1.fc29.src.rpm, armv7hl): free -> open
(
buildvm-armv7-24.arm.fedoraproject.org)
32774227 buildArch (tty-clock-2.3-1.fc29.src.rpm, x86_64): open
(
buildvm-04.phx2.fedoraproject.org) -> FAILED: BuildError: error building
package (arch x86_64), mock exited with status 1; see build.log for more
information
0 free 6 open 0 done 1 failed
32774231 buildArch (tty-clock-2.3-1.fc29.src.rpm, s390x): open
(
buildvm-s390x-05.s390.fedoraproject.org) -> FAILED: BuildError: error
building package (arch s390x), mock exited with status 1; see build.log for
more information
0 free 5 open 0 done 2 failed
32774230 buildArch (tty-clock-2.3-1.fc29.src.rpm, i686): open
(
buildvm-05.phx2.fedoraproject.org) -> FAILED: BuildError: error building
package (arch i686), mock exited with status 1; see build.log for more
information
0 free 4 open 0 done 3 failed
32774228 buildArch (tty-clock-2.3-1.fc29.src.rpm, ppc64le): open
(
buildvm-ppc64le-17.ppc.fedoraproject.org) -> FAILED: BuildError: error
building package (arch ppc64le), mock exited with status 1; see build.log
for more information
0 free 3 open 0 done 4 failed
32774229 buildArch (tty-clock-2.3-1.fc29.src.rpm, aarch64): open
(
buildhw-aarch64-06.arm.fedoraproject.org) -> FAILED: BuildError: error
building package (arch aarch64), mock exited with status 1; see build.log
for more information
0 free 2 open 0 done 5 failed
32774232 buildArch (tty-clock-2.3-1.fc29.src.rpm, armv7hl): open
(
buildvm-armv7-24.arm.fedoraproject.org) -> FAILED: BuildError: error
building package (arch armv7hl), mock exited with status 1; see build.log
for more information
0 free 1 open 0 done 6 failed
32774225 build (f30, tty-clock-2.3-1.fc29.src.rpm): open
(
buildvm-19.phx2.fedoraproject.org) -> FAILED: BuildError: error building
package (arch x86_64), mock exited with status 1; see build.log for more
information
0 free 0 open 0 done 7 failed
32774225 build (f30, tty-clock-2.3-1.fc29.src.rpm) failed
building ttyclock.c
cc -Wall -g $(pkg-config --cflags ncurses) ttyclock.c -o tty-clock
$(pkg-config --libs ncurses)
BUILDSTDERR: /bin/sh: cc: command not found
BUILDSTDERR: make: *** [Makefile:26: tty-clock] Error 127
RPM build errors:
BUILDSTDERR: error: Bad exit status from /var/tmp/rpm-tmp.tVSsLr (%build)
BUILDSTDERR: bogus date in %changelog: Mon Feb 12 2019 IDF
<idf31(a)protonmail.com> - 0.1-2
BUILDSTDERR: Bad exit status from /var/tmp/rpm-tmp.tVSsLr (%build)
Child return code was: 1
EXCEPTION: [Error()]
Sorry for this, I think it was caused by a typo in the changelog.
It should work now.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component