Copr Buildsystem¶
Copr is designed to be a lightweight buildsystem that allows contributors to create packages, put them in repositories, and make it easy for users to install the packages onto their system. Within the Fedora Project it is used to allow packagers to create third party repositories.
Content¶
- User Documentation
- Quick start
- Tutorial
- How to enable copr repository?
- Public Copr instances
- Build Source Types
- Working with Packages
- Reproducing the builds locally
- SSH access to Copr builders
- Temporary projects
- Webhooks
- Pagure Integration
- Custom-location Webhooks
- Links
- Multilib
- Advanced searching
- Status Badges
- Mass rebuilds
- Build batches
- Automatic run of Fedora Review tool
- RPM Macros
- Creating repositories manually
- High Performance Builders
- Subprojects
- Modularity
- FAQ
- Upstream Release Notes
- Highlights from 2024-10-03 release
- Highlights from 2024-05-22 release
- Highlights from 2024-04-12 release
- Highlights from 2024-03-07 release
- Fixes in the 2023-11-28 release
- Highlights from 2023-08-16 release
- Highlights from 2023-05-25 release
- Highlights from 2023-04-05 release
- Highlights from 2023-01-25 release
- Highlights from 2022-11-30 release
- Highlights from 2022-11-28 release
- Highlights from 2022-09-21 release
- Highlights from 2022-08-18 release
- Highlights from 2022-07-27 release
- Highlights from 2022-06-22 release
- Highlights from 2022-04-05 release
- Highlights from 2022-03-21 release
- Highlights from 2022-02-03 release
- Highlights from 2021-11-11 release
- Highlights from 2021-10-01 release
- Highlights from 2021-08-26 release
- Highlights from 2021-06-16 release
- Highlights from 2021-04-28 release
- Highlights from 2021-03-17 release
- Highlights from 2021-01-21 release
- Highlights from 2020-12-01 release
- Highlights from 2020-11-13 release
- Developer Documentation
- Maintenance Documentation
- How to release copr RPM packages
- How to upgrade builders
- How to Upgrade Fedora Copr Persistent VMs (Amazon AWS)
- How to manage active chroots
- How to rename chroots
- Fedora Copr hypervisors
- Fedora Copr outage announcements
- Fedora Copr credentials
- AWS Tips-and-Tricks
- How to enlarge disk partitions
- How to manage RAID 10 on copr-backend
- Recovery from backups
- Database backups
- PostgreSQL Upgrade
- Populate DB with production data
- Running Sanity tests against local dev instance
- Beaker tests
- Resalloc
- When do we run createrepo
- Fedora Magazine
- Email templates
- Sending notifications and removing data from outdated chroots
- Monitoring the service
- Maintaining DistGit machine
- Downloads
- Brainbox
- Features
The main subsections of this wiki:
User Documentation: Learn more about how to use Copr. Quick tutorial, FAQ.
Developer Documentation: Learn how to work on and build Copr, and how Copr is put together.
Downloads: Find out how to check out the source code and get RPM releases.
Brainbox: Some ideas that might end up in the roadmap. Just a page to collect them.
Features: An index page of ideas that have graduated from the Brainbox to become features.
Communication¶
Copr is discussed on Fedora Build System Matrix channel.
Copr also has a mailing list for discussion: copr-devel@lists.fedorahosted.org (signup) (archives)
Source¶
Copr comes in several pieces. You can browse the source here:
The source for Copr itself: https://github.com/fedora-copr/copr
Instances¶
https://copr.fedorainfracloud.org/ (preferred)
http://copr.stg.fedoraproject.org/ (staging instance, broken most of the time).
Need To Edit This Wiki?¶
All the sources for this wiki are placed in our repository at https://github.com/fedora-copr/copr in “doc” directory. If you have commit rights, then you can to directly edit the files and then follow procedure described here: https://docs.pagure.org/pagure/usage/using_doc.html to push the modified html files into the docs repo. Even without commit rights, you can contribute. Just send us the patch of the modified doc files and we will apply it for you (see Patch process).
Want to File a Bug/RFE?¶
Search for bugs here: If it has, feel free to add yourself to Cc list of that bugzilla and add comments with more details, logs, etc.
Report a new bug: If it has not, then please report it here with all the detail you can muster.
Get a Bugzilla account: You will need an account in bugzilla to add comments or file new bugzillas.