Packages prepared using EL8 chroot are not available for CentOS8
by Eugene Akhmetkhanov
Hi guys,
I have qemu-kvm-4.2.0 packages prepared for CentOS 8 on COPR https://copr.fedorainfracloud.org/coprs/axmetishe/qemu-kvm/packages/
using git repository with spec and I'm trying to install them via repository but dnf from CentOS 8
container can't find them, but src only:
dnf info qemu-kvm --showduplicates
Name : qemu-kvm
Epoch : 15
Version : 4.2.0
Release : 68.el8
Architecture : src
Size : 59 M
Source : None
Repository : copr:copr.fedorainfracloud.org:axmetishe:qemu-kvm
Summary : QEMU is a machine emulator and virtualizer
URL : http://www.qemu.org/
License : GPLv2 and GPLv2+ and CC-BY
Description : qemu-kvm is an open source virtualizer that provides hardware
: emulation for the KVM hypervisor. qemu-kvm acts as a virtual
: machine monitor together with the KVM kernel modules, and emulates
: the hardware for a full system such as a PC and its associated
: peripherals.
This is wierd because a month ago I was able to bootstrap one instance via kickstart with this package installation.
On the other hand the same command on Fedora 31 show me the packages:
dnf info qemu-kvm --showduplicates
Name : qemu-kvm
Epoch : 15
Version : 4.2.0
Release : 68.el8
Architecture : x86_64
Size : 7.2 k
Source : qemu-kvm-4.2.0-68.el8.src.rpm
Repository : copr:copr.fedorainfracloud.org:axmetishe:qemu-kvm
Summary : QEMU is a machine emulator and virtualizer
URL : http://www.qemu.org/
License : GPLv2 and GPLv2+ and CC-BY
Description : qemu-kvm is an open source virtualizer that provides hardware
: emulation for the KVM hypervisor. qemu-kvm acts as a virtual
: machine monitor together with the KVM kernel modules, and emulates
: the hardware for a full system such as a PC and its associated
: peripherals.
Additionally I have the libssh2 package which I'm able to install in this container.
I'm new with COPR and can't get the point why this happens.
Would someone point me to the right direction please?
Thank you in advance.
3 years, 8 months
Highlights from the latest Copr release
by Tomas Hrnciar
Hello,
recently (on Jan 16, 2020) a new Copr release landed production.
Here is the list of visible changes:
- We contributed to createrepo_c to speed up Copr for building large
projects. Building large projects should be significantly faster.
- Web-UI <project>/builds and <project>/packages queries were also reworked
to be faster.
- There is a new comand in copr-cli, "list-chroots" to list all available
chroots in Copr.
- To the statistics section were added new graphs to help us monitor how
many actions were processed and how many of them failed. Actions are one
of: generate GPG key, delete package, delete project, etc. Builds are not
counted there as they have separate graph.
- The frontend (web-UI, api) RAM was doubled because of the increasing load.
- Builder VM images were updated to get in several bugfixes, like terminal
color sequences in live logs, not enough free space under /tmp and
/var/lib/copr-rpmbuild, increased number maximum opened file descriptors to
10240.
- We enabled automatic createrepo_c run after build removal in very large
projects.
- Removing of multiple builds in @group projects was fixed.
- Sometimes, after project creation, the initial createrepo run failed and
it then blocked our build dispatcher process (until user manually
re-created the metadata), this bug has been fixed.
Happy building!
Tomas
3 years, 8 months
What does "Rebuild all" do with SCM packages?
by Miro Hrončok
Hello. I have noticed the "Rebuild all" button on packages page.
Does "Rebuild all" pull from committish with SCM packages, or does it rebuilt
the latest SRPM?
Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
3 years, 8 months
Automated builds possible?
by Richard Shaw
I just had a thought and wondered if it were possible.
I have an upstream that posts alpha and beta releases to a specific URL.
What I'd like copr (or something) to do is:
1. Monitor those URLs so it knows when a new alpha is pushed
2. Pull the spec file from fedora rawhide (master)
3. Run rpmdev-bumpspec -n <version> -c "Update to <version>." <spec>
4. Create a build in my COPR project using the new source.
Is this possible?
Thanks,
Richard
3 years, 8 months
