Hello,
we have just disabled Fedora 30 chroots in Copr.
According to the Fedora wiki [1], Fedora 30 reached the end of its life
on 2020-05-26 and therefore we are disabling it in Copr.
That effectively means that from this moment, it is no longer possible
to submit builds for the following chroots:
- fedora-30-x86_64
- fedora-30-i386
- fedora-30-ppc64le
- fedora-30-aarch64
- fedora-30-armhfp
[1] https://fedoraproject.org/wiki/End_of_life
Jakub
Hello. I am trying to build sagemath from dist git in Copr.
https://copr.fedorainfracloud.org/coprs/churchyard/parso-0.8/build/1730316/https://copr.fedorainfracloud.org/coprs/churchyard/parso-0.8/build/1733717/
I get this when the SRPM is created:
RPM build errors:
stderr: error: create archive failed on file
/tmp/copr-rpmbuild-2o1bpkg6/sage-9.1.tar.gz: cpio: write failed - No space left
on device
create archive failed on file /tmp/copr-rpmbuild-2o1bpkg6/sage-9.1.tar.gz:
cpio: write failed - No space left on device
Failed to execute command.
Is it too big for copr or can the space be allocated somehow?
Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
Do the COPR environments either support faccessat2 or fail with ENOSYS?
I've been told that we put in a workaround in glibc for the bogus EPERM
error from systemd-nspawn specifically to support COPR:
<https://bugzilla.redhat.com/show_bug.cgi?id=1869030>
And we really need to remove that workaround again because EPERM is an
ambiguous error code and applies to situations where we *do not* want to
perform the fallback implementation (because it cannot perform
permission checks accurately).
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill