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.
On Aug 12 2020, a new Copr release landed production. Here is the list
of visible changes:
- Project karma implemented; Logged-in users can give
thumbs-up/thumbs-down to the existing copr projects. This is just
another way to give feedback about a particular Copr project quality.
This is merely subjective. We do not give you guidance what "thumbs
up/down" means. When it is good for you - for whatever reason - give it
thumbs up. It may be just feedback for the maintainer or other users.
Or we may automatically select and group high-quality projects in the
future - and e.g. revive the idea of the Playground [1]. The options
are open. We would like to hear your feedback about this feature!
- Copr newly provides a build-time macro %buildtag. Its format is
`.copr<BUILD_ID>` and is useable for auto-incrementing the package's NVR
in subsequent builds. It may be used in spec file like:
Release: 1%{?dist}%{?buildtag}
It could be useful as good-enough alternative for the Release
auto-bumping proposal. See the fedora devel discussion [2] for more
info. This is not any kind of encouragement to use it. We added it
there to easy testing your ideas about the automatic filling of the
Release tag.
- The /status page has a new "Starting" tab [3] which shows all the binary
builds where the worker process is already started, but appropriate
builder VM is not yet assigned to it (issue/1429).
- Group avatars (user-icons assigned to an e-mail) were fixed to
really use the groups' emails, not the administrators' (issue/1419).
- Command-line interface for the project package listing was significantly
optimized, and should now be faster than the web-UI on large projects
(issue/757).
- All the background jobs have now a lower priority than normal jobs.
Previously, background source builds were still prioritized over normal
builds. This should be the last step towards a fair build scheduler.
- Support for a new command 'copr-cli list-builds <project>' was added.
It lists each build on a separate line, as a tab-separated list of
<BUILD_ID> <PACKAGE_NAME> <BUILD_STATUS> items.
Related copr client Fedora/EPEL updates:
F32 - https://bodhi.fedoraproject.org/updates/FEDORA-2020-ce81a9539d
F31 - https://bodhi.fedoraproject.org/updates/FEDORA-2020-76bfc383c3
EPEL8 - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-4c313586d8
EPEL7 - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-6a77e31d06
EPEL6 - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-78e089fe70
Should you have any related issues, please report them to us as usual.
[1] https://fedoraproject.org/wiki/Playground
[2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
[3] https://copr.fedorainfracloud.org/status/starting/
Happy building!
Copr Team
There will be an outage starting at:
$ date --date '2020-08-12 7:00 UTC'
The outage will last approximately 3 hours. The copr-backend storage (copr
build results) will stay online during this outage.
Reason for outage:
We're updating copr packages to the new versions which will bring new
features, bugfixes but especially better performance.
Affected Services:
copr-frontend - https://copr.fedorainfracloud.org
copr-backend - https://copr-be.cloud.fedoraproject.org/
Contact persons:
@praiskup/@frostyx
Please join #fedora-admin in irc.freenode.net or add comments to the ticket for
this outage above.
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/9218
Jakub