Categories

New copr-frontend release

I am sending these release notes also to fedora-devel list (and not just
copr-devel list as usually) because they contain information
about upcoming Fedora branching and what features COPR provides to move the
set of packages from your rawhide chroots into the newly branched ones.

We have just released copr-frontend-1.118. Mainly this release prepares for
the upcoming branching by adding two features:

- Batch package rebuilding ("Rebuild all" button in Packages view) so
that you can rebuild all your packages in the new chroots.
If you have build dependencies placed in you copr chroot as well, I
recommend linking the rawhide chroot first in "Repos"
setting ("Edit" button next to the chroot name in project settings) or
in "External repositories" field to be found in your project settings.
Otherwise you will probably need to click the "Rebuild all packages"
button a few times to get all the packages built successfully
(alas manual mockchain). We plan to introduce automatic build ordering
(based on BuildRequires) to optimize this feature in the foreseeing future.

- "Follow Fedora branching" project switch that (if enabled) makes COPR
fork your rawhide chroots into the newly branched ones
and hence user will have your packages available in their f27 systems
and they will also be available for your upcoming builds
(meaning you don't need to bootstrap anything from scratch). It might
take a few days after branching for this to actually take effect because
the new chroots need to be enabled in COPR first (and they should also
be in mock for that as well so that building in them works).

You can enable the "Follow Fedora branching" option in project settings and
it will basically ensure that your rawhide builds will be copied
into the new fedora-27-* ones when they become available in COPR.

Also, we have added syntax highlighting in code blocks in project
description and instructions and we switched the used library for markdown
rendering
(now python-CommonMark, before python-markdown).

Comments

Michal Novotny wrote:
Unfortunately, this feature is less useful than I had expected, it does not
work for uploaded SRPMs or SRPMs fetched from URLs. In that case, I would
have expected it to just copy the dist-git contents from the build that is
being rebuilt (even for the URL case, I would not expect it to try to
refetch the URL, which may no longer be valid). Instead, I got an error
message that it does not have any sources to fetch.

I ended up passing the output SRPMs of the Copr builds as the SRPM URLs for
new builds as a workaround.

(I prefer the automatic forking option, but unfortunately, the F26 branching
happened before it was introduced, so it used the old model, where rawhide
was renamed to f26 and the rawhide chroot started up empty. So I had to do
rebuilds for Rawhide.)

It actually works like you expect for uploaded SRPMs and URL SRPMs.
For both these build types, imported copr-dist-git sources are being used.
This will be a bug somewhere else. You can contact me personally or here
with the details.

I ended up passing the output SRPMs of the Copr builds as the SRPM URLs for

On Monday, August 21, 2017 10:42:00 AM CEST Michal Novotny wrote:
It would look like use-case for new check-box; aka rebuild all packages during
fedora-branching time.

+1 for having this enabled by default; IMO that's non-issue if that option
doesn't affect non-fedora buildroots.

Also small issue report: from the description of the checkbox is unclear whether
just new chroot is created in frontend database, or also build-results are
copyied from rawhide to branched on "backend" (binary packages).