Re: The future Fedora Copr "rolling" chroot cleanup policy
On pondělí 15. července 2024 12:10:58, SELČ Sandro via devel wrote: > On 15-07-2024 10:24, Pavel Raiskup wrote: > > TL;DR: We plan to start monitoring build activity in Copr projects. > > If no builds appear for a long time in these "rolling" chroots (such as > > Fedora Rawhide), we'll disable such chroots, preserve the built results > > for a while, and then delete them if no action is taken by the user. > > Thanks for the very early heads up. Will you provide more details > regarding build retention? Without it it's kinda hard to judge the impact. > > I can think of at least one project I'm looking after that won't see > many updates. It's kind of there for convenience. Thank you for the reply. The current idea is to have a 6-months period of inactivity (when no build appears in given rolling chroot), then another 6-months period when we keep the build results, but we notify the user about the future removal (e-mail, and web-UI hints). Then (if no action taken) remove the chroot/build results. > I'm regularly using the _delete after_ option as well as _max number of > builds_ for packages being automatically rebuilt. I'd like to see a > project wide option allowing me to specify max builds to keep regardless > of age or an option to rebuild for rawhide when its associated release > is incremented. The latter sounds more difficult to implement and may > have unintended side effects if not thought through. Sure, there's an "epic" issue https://github.com/fedora-copr/copr/issues/2541 that would probably cover your configuration use-case. If you need something peculiar, feel free to submit RFE (or patch, that's preferred). Pavel > -- Sandro > > signature.asc Description: This is a digitally signed message part. -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
The future Fedora Copr "rolling" chroot cleanup policy
Hello maintainers. This is a gentle heads-up (at least a year in advance) that we plan to address Fedora Copr storage consumption related to Fedora Rawhide builds. Currently, Rawhide build results are kept indefinitely, but this is going to change in the future. For the full story, see the blog post: https://fedora-copr.github.io/posts/cleanup-rawhide-builds TL;DR: We plan to start monitoring build activity in Copr projects. If no builds appear for a long time in these "rolling" chroots (such as Fedora Rawhide), we'll disable such chroots, preserve the built results for a while, and then delete them if no action is taken by the user. Hope this isn't going to cause too much inconvenience. Feel free to discuss this here or under the blog post. Pavel signature.asc Description: This is a digitally signed message part. -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Duplicate NEVRAs in Copr repositories - future breakage
Hello maintainers, the Copr project is in the process of implementing the PULP storage backend (RPM repo management technology): https://github.com/fedora-copr/copr/issues/2533 We expect that this change will be slow and incremental (we will not move all projects to PULP at once) and that it is going to be almost an 1:1 replacement. See that tracker link above if you want more info. There's one technical detail/change that seems to be clear right now and is worth announcing in advance - the way we handle the duplicate NEVRAs in the same repos is going to change (a bit). Before or after the switch, Copr simply allows you to build packages with the same/duplicate NEVRAs into the same repository. There's no reason to fail the build process. The current (old) behavior though is that Copr keeps all the duplicates in the RPM repository - and DNF is confused (when asked to install one of such duplicate NEVRAs, it picks one of them by random, or by package ID, or it is DNF version specific behavior, or - I don't really now). Project administrators can then come anytime later and decide which particular build ID they want to keep, and delete the rest of the duplicate builds. So the confusion can be resolved pretty easily. The new (with PULP) behavior will be that the newer duplicates will override the previous - this is on one hand good, because DNF is not confused - always sees the latest "duplicate" NEVRA to install. But on the other hand this also means that, when the latest NEVRA build is removed, Copr will drop the NEVRA from the metadata (it will not present the older builds). This is just a headsup for you, feel free to comment here or ideally in the corresponding Copr issue https://github.com/fedora-copr/copr/issues/3262 Thank you, and happy building! P.S. When you build only for the purpose of building (to check there's no FTBFS) you are not affected. If you bump Release regularly (you should), you won't be affected. Pavel signature.asc Description: This is a digitally signed message part. -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Disabling Fedora 38 chroots in Copr
Hello, tl;dr, we have just disabled Fedora 38 chroots in Copr. According to the Fedora wiki [1], Fedora 38 reached the end of its life [4] 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-38-x86_64 - fedora-38-i386 - fedora-38-ppc64le - fedora-38-aarch64 - fedora-38-armhfp - fedora-38-s390x Additionally, according to Outdated chroots removal policy [2], Copr is going to preserve existing build results in those chroots for another 180 days and then automatically remove them unless you take an action and prolong the chroots life span in your projects. Read more about this feature in the Copr - Removing outdated chroots blog post [3]. [1] https://fedoraproject.org/wiki/End_of_life [2] https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html [3] http://frostyx.cz/posts/copr-removing-outdated-chroots [4] https://fedorapeople.org/groups/schedule/f-40/f-40-all-tasks.html Pavel -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Copr Outage - Updating to a March 2024 Version
Hello Michael, On čtvrtek 7. března 2024 16:31:14 CET Michael J Gruber wrote: > Am Do., 7. März 2024 um 13:09 Uhr schrieb Pavel Raiskup : > > > > And the outage is over. Release notes here: > > > > https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html > > > > Special Highlight: Jakub added an exciting new feature in this release, > > allowing users to SSH to Copr builders. This is exciting news! > > > > Happy building! > > Pavel > > Thanks, that is neat indeed :) > > Would it make sense to have the "rebuild with ssh access" call mock > with "--no-clean-after"? Without that, there is not that much more to > inspect than the chroot itself, is there? Or is the idea that we run > mock again? Yes, we originally meant that the build would be resubmitted. Though the idea with --no-clean-after sounds like a reasonable RFE ;) Feel free to open a ticket https://github.com/fedora-copr/copr/issues Pavel > Michael > -- > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Copr Outage - Updating to a March 2024 Version
And the outage is over. Release notes here: https://docs.pagure.org/copr.copr/release-notes/2024-03-07.html Special Highlight: Jakub added an exciting new feature in this release, allowing users to SSH to Copr builders. This is exciting news! Happy building! Pavel On pondělí 4. března 2024 17:53:13 CET Pavel Raiskup wrote: > There will be a Fedora Copr outage starting at > > $ date --date '2024-03-07 11:30 UTC' > > The outage will last approximately 2 hours. The build queue processing will > be stopped during the outage, and the Frontend/Web-UI will be down most of > the time (no new tasks accepted). > > The DNF packages and repositories (hosted on copr-backend) will be available > during this outage. > > Reason for outage: > We will update the infrastructure machines to the latest packages that are > currently being developed. > > Affected Services: > https://copr.fedorainfracloud.org/ > https://download.copr.fedorainfracloud.org/results/ > > Upstream ticket: > https://github.com/fedora-copr/copr/issues/3151 > > Infrastructure ticket: > https://pagure.io/fedora-infrastructure/issue/11808 > > Please join Fedora Build System Matrix channel: > https://matrix.to/#/#buildsys:fedoraproject.org > > Outage Contacts: > @praiskup (Pavel Raiskup) / @frostyx (Jakub Kadlčík) > signature.asc Description: This is a digitally signed message part. -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Copr Outage - Updating to a March 2024 Version
There will be a Fedora Copr outage starting at $ date --date '2024-03-07 11:30 UTC' The outage will last approximately 2 hours. The build queue processing will be stopped during the outage, and the Frontend/Web-UI will be down most of the time (no new tasks accepted). The DNF packages and repositories (hosted on copr-backend) will be available during this outage. Reason for outage: We will update the infrastructure machines to the latest packages that are currently being developed. Affected Services: https://copr.fedorainfracloud.org/ https://download.copr.fedorainfracloud.org/results/ Upstream ticket: https://github.com/fedora-copr/copr/issues/3151 Infrastructure ticket: https://pagure.io/fedora-infrastructure/issue/11808 Please join Fedora Build System Matrix channel: https://matrix.to/#/#buildsys:fedoraproject.org Outage Contacts: @praiskup (Pavel Raiskup) / @frostyx (Jakub Kadlčík) -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Mock v5.5 released (and mock-core-configs v40.1)
Hello maintainers! Let me announce a new release of Mock v5.5, the chroot build environment manager for building RPMs. First and foremost, this update ships with updated mock-core-configs v40.1, bringing Fedora 40 configs as "branched" separately from Fedora Rawhide (Fedora 41 now equals to Fedora Rawhide). The Mock 5.5 release then mostly brings a few important bug-fixes (fix for bash-completion multi-argument options, fixing in-chroot file and process group ownership, root_cache invalidation by configuration changes), but there are also a few new (rather small) features. Since we needed to fix fedora-rawhide builds, this update also landed Fedora Copr production yesterday. In case of any trouble, please report issues upstream: https://github.com/rpm-software-management/mock/issues Full release notes: https://rpm-software-management.github.io/mock/Release-Notes-5.5 The updated packages are in Bodhi: [Fedora 39]: https://bodhi.fedoraproject.org/updates/FEDORA-2024-1171d69465 [Fedora 38]: https://bodhi.fedoraproject.org/updates/FEDORA-2024-15b5461dd0 [EPEL 9]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-fd971ca651 [EPEL 8]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-e9e1b2dad6 Happy building! Pavel signature.asc Description: This is a digitally signed message part. -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Mock Configs v39.3 released - DNF5 used for F40+ builds
On pátek 5. ledna 2024 10:06:34 CET Pavel Raiskup wrote: > On čtvrtek 4. ledna 2024 19:20:46 CET Pavel Raiskup wrote: > > On středa 3. ledna 2024 8:46:22 CET Pavel Raiskup wrote: > > > I just wanted to give you a quick heads-up that I plan to enable the > > > BuildWithDNF5 change in Fedora Copr as soon as the new Rawhide compose > > > gets distributed to mirrors. > > > > This has happened now. Fedora Copr builds F40 (Rawhide) with DNF5 now. > > Should you face any issue, please report it. > > Two more hints: > > - I noticed that `dnf5` on Fedora Copr builders (F38) was buggy (old > version) because the latest update was not yet in the stable > repository. This was breaking Rawhide builds in Copr projects with > `bootstrap=off` (using dnf5 on host). This is no longer the case, the > DNF5 package has been updated to v5.1.10. If you observed a > suspicious problem, please consider `bootstrap=on` or at least check > that DNF v5.1.10 is used. > > - DNF5 isn't downloading filelists (resource cost optimization), which > in turn means that the packages can not (build)depend on random file > paths. So just a small reminder that, per the updated packaging > guidelines https://pagure.io/packaging-committee/pull-request/1321 , > you MUST NOT do things like `BuildRequires: /some/random/file/name`. I just want to bump this thread; @kevin updated Fedora Koji today - the Fedora 40+ (current Rawhide) builds are already handled with DNF5. Happy (faster) building! And should you face any issue, please report. Pavel signature.asc Description: This is a digitally signed message part. -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Mock Configs v39.3 released - DNF5 used for F40+ builds
On čtvrtek 4. ledna 2024 19:20:46 CET Pavel Raiskup wrote: > On středa 3. ledna 2024 8:46:22 CET Pavel Raiskup wrote: > > I just wanted to give you a quick heads-up that I plan to enable the > > BuildWithDNF5 change in Fedora Copr as soon as the new Rawhide compose > > gets distributed to mirrors. > > This has happened now. Fedora Copr builds F40 (Rawhide) with DNF5 now. > Should you face any issue, please report it. Two more hints: - I noticed that `dnf5` on Fedora Copr builders (F38) was buggy (old version) because the latest update was not yet in the stable repository. This was breaking Rawhide builds in Copr projects with `bootstrap=off` (using dnf5 on host). This is no longer the case, the DNF5 package has been updated to v5.1.10. If you observed a suspicious problem, please consider `bootstrap=on` or at least check that DNF v5.1.10 is used. - DNF5 isn't downloading filelists (resource cost optimization), which in turn means that the packages can not (build)depend on random file paths. So just a small reminder that, per the updated packaging guidelines https://pagure.io/packaging-committee/pull-request/1321 , you MUST NOT do things like `BuildRequires: /some/random/file/name`. Pavel signature.asc Description: This is a digitally signed message part. -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Mock Configs v39.3 released - DNF5 used for F40+ builds
On středa 3. ledna 2024 8:46:22 CET Pavel Raiskup wrote: > I just wanted to give you a quick heads-up that I plan to enable the > BuildWithDNF5 change in Fedora Copr as soon as the new Rawhide compose > gets distributed to mirrors. This has happened now. Fedora Copr builds F40 (Rawhide) with DNF5 now. Should you face any issue, please report it. Thanks! Pavel signature.asc Description: This is a digitally signed message part. -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Mock Configs v39.3 released - DNF5 used for F40+ builds
On pondělí 18. prosince 2023 10:08:06 CET Pavel Raiskup wrote:
> On pátek 1. prosince 2023 15:04:10 CET Pavel Raiskup wrote:
> > Hello maintainers!
> >
> > Let me announce a new release of Mock Core Configs v39.3, aka
> > the configuration files for Mock, the chroot build environment manager
> > for building RPMs.
> >
> > The notable change in this release is that we are switching the default
> > package_manager from DNF4 to DNF5, according to the F40 change:
> > https://fedoraproject.org/wiki/Changes/BuildWithDNF5
> > Full release notes:
> >https://rpm-software-management.github.io/mock/Release-Notes-Configs-39.3
> >
> > We plan to push this update into Fedora Copr to get some early testing
> > next week. Then, depending on the releng team, we might push this into
> > Koji soon. The Bodhi updates links are here:
> >
> > F39 https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a947db1d0
> > F38 https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ef1e12930
> > F37 https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd9c489f40
> > EL9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c2c4082053
> > EL8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eab5217f46
> >
> > Note that we **will not** push these updates into Fedora stable earlier
> > than on Monday 2023-12-18 (but very likely we'll wait till the next
> > year, depending on the feedback).
>
> And the push eventually happened, despite that I did not want it to
> happen, yet. I probably messed up the Bodhi updates (I thought I
> disabled the stable-by-time feature). Sorry, folks.
>
> The builds often just work. But there are two issues that blocks us
> from letting this update go to Fedora Copr at least:
>
> - the builddep globbing issue
> https://github.com/rpm-software-management/dnf5/pull/1088 which is
> going to be fixed by a new release (just a new DNF5 release into
> Rawhide means the problem is fixed)
>
> - the weird hangs against Fedora Copr repositories
> https://github.com/fedora-copr/copr/issues/3067 - this will probably
> not hit you locally, but I am not sure yet.
>
> In any case, if you need to - stay with DNF4 for a while - either do
>
> $ cat ~/.config/mock/fedora-rawhide-x86_64.cfg
> include("/etc/mock/fedora-rawhide-x86_64.cfg")
> config_opts["package_manager"] = "dnf"
>
> ... or stay with the `mock-core-configs v39.2` a bit longer please.
Just a quick update, we already have DNF5 5.1.10 submitted for Fedora
Rawhide repos (should be in mirrors tomorrow). This DNF5 release has no
known "blocker" issues.
I just wanted to give you a quick heads-up that I plan to enable the
BuildWithDNF5 change in Fedora Copr as soon as the new Rawhide compose
gets distributed to mirrors.
Pavel
signature.asc
Description: This is a digitally signed message part.
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Mock Configs v39.3 released - DNF5 used for F40+ builds
On pondělí 18. prosince 2023 11:46:07 CET Miro Hrončok wrote:
> On 18. 12. 23 10:08, Pavel Raiskup wrote:
> > In any case, if you need to - stay with DNF4 for a while - either do
> >
> > $ cat ~/.config/mock/fedora-rawhide-x86_64.cfg
> > include("/etc/mock/fedora-rawhide-x86_64.cfg")
> > config_opts["package_manager"] = "dnf"
> >
> > ... or stay with the `mock-core-configs v39.2` a bit longer please.
>
>
> Hi Pavel,
> this works locally, but not in Copr.
>
> Our Python 3.13 Copr builds started failing today with the builddep globbing
> issue.
>
> What do we do?
I should work again actually, so no explicit action is needed.
I reverted the change for Fedora Copr, per
https://github.com/fedora-copr/copr/issues/3067
Pavel
signature.asc
Description: This is a digitally signed message part.
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Mock Configs v39.3 released - DNF5 used for F40+ builds
On pátek 1. prosince 2023 15:04:10 CET Pavel Raiskup wrote:
> Hello maintainers!
>
> Let me announce a new release of Mock Core Configs v39.3, aka
> the configuration files for Mock, the chroot build environment manager
> for building RPMs.
>
> The notable change in this release is that we are switching the default
> package_manager from DNF4 to DNF5, according to the F40 change:
> https://fedoraproject.org/wiki/Changes/BuildWithDNF5
> Full release notes:
>https://rpm-software-management.github.io/mock/Release-Notes-Configs-39.3
>
> We plan to push this update into Fedora Copr to get some early testing
> next week. Then, depending on the releng team, we might push this into
> Koji soon. The Bodhi updates links are here:
>
> F39 https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a947db1d0
> F38 https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ef1e12930
> F37 https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd9c489f40
> EL9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c2c4082053
> EL8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eab5217f46
>
> Note that we **will not** push these updates into Fedora stable earlier
> than on Monday 2023-12-18 (but very likely we'll wait till the next
> year, depending on the feedback).
And the push eventually happened, despite that I did not want it to
happen, yet. I probably messed up the Bodhi updates (I thought I
disabled the stable-by-time feature). Sorry, folks.
The builds often just work. But there are two issues that blocks us
from letting this update go to Fedora Copr at least:
- the builddep globbing issue
https://github.com/rpm-software-management/dnf5/pull/1088 which is
going to be fixed by a new release (just a new DNF5 release into
Rawhide means the problem is fixed)
- the weird hangs against Fedora Copr repositories
https://github.com/fedora-copr/copr/issues/3067 - this will probably
not hit you locally, but I am not sure yet.
In any case, if you need to - stay with DNF4 for a while - either do
$ cat ~/.config/mock/fedora-rawhide-x86_64.cfg
include("/etc/mock/fedora-rawhide-x86_64.cfg")
config_opts["package_manager"] = "dnf"
... or stay with the `mock-core-configs v39.2` a bit longer please.
Sorry again for the inconvenience,
Pavel
signature.asc
Description: This is a digitally signed message part.
--
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 37 is EOL
Hello maintainers! Fedora 37 has been EOL for a few days now: https://fedorapeople.org/groups/schedule/f-39/f-39-all-tasks.html So I have disabled the Fedora 37 chroots, which started the standard build removal policy. For more info take a look at docs: https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html Pavel On úterý 5. prosince 2023 18:45:48 CET Tomas Hrcka wrote: > Hello all, > > Fedora Linux 37 has gone end of life for updates and support on 2023-12-05. > No more updates of any kind, including security updates or security > announcements, will be available for Fedora Linux 37 after the said > date. All the updates of Fedora Linux 37 being pushed to stable will be > stopped as well. > > Fedora Linux 38 will continue to receive updates until approximately > one month after the release of Fedora Linux 40. The maintenance > schedule of Fedora Linux releases is documented on the Fedora Project > wiki [1]. The Fedora Project wiki also contains instructions[2] on how > to upgrade from a previous release of Fedora Linux to a version > receiving updates. > > This email template is also in https://pagure.io/releng if you wish to > propose improvements or changes to it. > > > Regards, > Tomas Hrcka > Fedora Release Engineering > > [1] - > https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule > [2] - https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades > [3] - https://pagure.io/releng > > -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Copr / Mock) team is moving from IRC to Matrix
Hello maintainers! You might have noticed that the Fedora Matrix <-> IRC bridge has been inactive for quite some time and is unlikely to be restored soon. Monitoring both channels has become expensive for our team. I have personally noticed (as an IRC-only person until recently) that Matrix has already been more active these days, especially concerning the build system topics. Fedora Infrastructure also seems to transitioning (meetings, etc). Henceforth, you can find us on the "Fedora Build System" channel at: https://matrix.to/#/#buildsys:fedoraproject.org We'll try to monitor the old IRC room for a while, but please note that the Matrix channel is now the correct place for your questions. Pavel -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Mock Configs v39.3 released - DNF5 used for F40+ builds
Hello maintainers! Let me announce a new release of Mock Core Configs v39.3, aka the configuration files for Mock, the chroot build environment manager for building RPMs. The notable change in this release is that we are switching the default package_manager from DNF4 to DNF5, according to the F40 change: https://fedoraproject.org/wiki/Changes/BuildWithDNF5 Full release notes: https://rpm-software-management.github.io/mock/Release-Notes-Configs-39.3 We plan to push this update into Fedora Copr to get some early testing next week. Then, depending on the releng team, we might push this into Koji soon. The Bodhi updates links are here: F39 https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a947db1d0 F38 https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ef1e12930 F37 https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd9c489f40 EL9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c2c4082053 EL8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eab5217f46 Note that we **will not** push these updates into Fedora stable earlier than on Monday 2023-12-18 (but very likely we'll wait till the next year, depending on the feedback). Happy (faster) building! Pavel signature.asc Description: This is a digitally signed message part. -- ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fwd: broken building for rhel/epel on COPR today (RHEL release day)
Hello, just forwarding the message. Thank you for the info Petr. -- Forwarded Message -- Subject: broken building for rhel/epel on COPR today (RHEL release day) Date: úterý 14. listopadu 2023, 11:04:33 CET From: Petr Stodulka Hi, building on COPR will be broken today for several hours. Today is release day of RHEL 8.9, and everyone (including customers) is seeing 404 not found error when trying to access RHEL 8 repositories (without the locked release). I expect from previous experience that all repos will be pushed & fully synchronized in another 4-7h. So in case you see some failed builds, just wait for couple of hours. The same is applied if you try in-place upgrades with RHSM in upcoming hours. Another solution is to lock system (or upgrade with leapp) to RHEL 8.8 if you do not need to do anything with RHEl 8.9 really. Cheers, -- Petr Stodulka OS & Application Modernization IRC nicks: pstodulk, skytak Principal Software Engineer Red Hat Czech s.r.o. - signature.asc Description: This is a digitally signed message part. ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: hellocopr: ERROR: Error running command: rpmbuild
Hello Osama, On pondělí 30. října 2023 18:44:39 CET Osama Albahrani wrote: > I following > https://docs.fedoraproject.org/en-US/quick-docs/publish-rpm-on-copr/#_step_1_creating_the_package_using_tito > and got the error below when running `tito build --rpm --test`. Any ideas > what I might be missing? Nice, thank you for the reference! > ... > Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.1a8Sp6 > + umask 022 > + cd /tmp/tito/rpmbuild-hellocoprxgamrmkk/BUILD > + cd hellocopr-git-2.92e675f > ... > + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g > -grecord-gcc-switches -pipe -Wall -Werror=format-security > -Werror=implicit-function-declaration -Werror=implicit-int > -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS > -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong > -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic > -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection > -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' > + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now > -specs=/usr/lib/rpm/redhat/redhat-hardened-ld > -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 > -specs=/usr/lib/rpm/redhat/redhat-package-notes ' > + /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP' > /usr/bin/python3: can't open file > '/tmp/tito/rpmbuild-hellocoprxgamrmkk/BUILD/hellocopr-git-2.92e675f/setup.py': > [Errno 2] No such file or directory This indicates that `setup.py` is missing in the SourceN: tarball. Which in turn means that `setup.py` is missing in the source git repository (because `tito` generates the tarball from git). Pavel signature.asc Description: This is a digitally signed message part. ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: KiCad builds failing
Thank you Steven for the report,
On sobota 16. září 2023 19:47:10 CEST Steven A. Falco wrote:
> For the last two days I've been seeing build errors like [1] and [2]:
>
> ERROR: Command failed:
> # mount -n -t tmpfs -o mode=0755 -o nr_inodes=0 -o size=140g
> mock_chroot_tmpfs /var/lib/mock/fedora-38-x86_64-1694797525.338111/root
>
> Prior to this, the KiCad builds have been running pretty smoothly. If
> someone could take a look and suggest what the problem might be, I'd
> appreciate it.
This is a bug in Mock 5.1, discussed e.g. here:
https://github.com/fedora-copr/copr/issues/2916
We are working on a fix, it should be ready in production today or
tomorrow. Work-around is to switch your bootstrap configuration to ON
or to the default ("use the defaults from mock-core-configs package").
Pavel
>
> Steve
>
> [1] https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/6407099/
> [2]
> https://copr.fedorainfracloud.org/coprs/g/kicad/kicad-testing/build/6410081/
> ___
> copr-devel mailing list -- copr-devel@lists.fedorahosted.org
> To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Fedora Copr - Mock v5.1
Hello again, just a quick update that Mock 5.1 has been deployed into Fedora Copr, too. While on it, openSUSE Leap 15.3 is now EOL and 15.5 added. Happy building! Pavel On pátek 15. září 2023 14:05:19 CEST Pavel Raiskup wrote: > Hello maintainers! > > Let me announce a new release of Mock v5.1 (the chroot build environment > manager for building RPMs). > > Mock 5.1 further stabilizes the (now default) --use-bootstrap-image > feature, and adds a "fallback" mechanism which turns the feature OFF > if Podman can not be used. In case of temporary network issues, Mock > repeatedly tries to "podman pull" the image. It contains a > compatibility fix with the new systemd-nspawn (rhbz#2238820) which was > painful during the recent days. > > In case of any trouble, please report issues upstream: > https://github.com/rpm-software-management/mock/issues > > Full release notes: > https://rpm-software-management.github.io/mock/Release-Notes-5.1 > > The updated packages are in Bodhi: > > [Fedora 39]: > https://bodhi.fedoraproject.org/updates/FEDORA-2023-245c858aed > [Fedora 38]: > https://bodhi.fedoraproject.org/updates/FEDORA-2023-67a714a252 > [Fedora 37]: > https://bodhi.fedoraproject.org/updates/FEDORA-2023-fb5ab02f5e > [EPEL 9]: > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-72c92e599a > [EPEL 8]: > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-45ace77fca > > Happy building! > Pavel > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
OUTAGE: Fedora Copr - updating to a new August 2023 version
There will be an outage starting at date --date "2023-08-16 12:30 UTC" it will last approximately 2 hours. The build queue processing will be stopped. During the outage time, we expect a very short downtime for the DNF package storage (== copr-backend, download.copr.f.o, less than 10 minutes). Reason for outage: We will update the infrastructure machines to the latest packages that are currently being developed. Affected Services: https://copr.fedorainfracloud.org/ https://download.copr.fedorainfracloud.org/results/ Fedora Infra ticket: https://pagure.io/fedora-infrastructure/issue/11468 Upstream ticket: https://github.com/fedora-copr/copr/issues/2824 Please join #fedora-buildsys, #fedora-admin or #fedora-noc on irc.libera.chat or add comments to this ticket. Copr Team ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Copr has Fedora 39 now, Was: Re: Disabling rawhide builds during branching - happening in 2hrs
On úterý 8. srpna 2023 19:12:36 CEST Tomas Hrcka wrote: > Fedora Linux 39 is going to be branched in the upcoming hours as per > the previous discussion[1] we are going to disable new koji builds for > the duration of this event. > > All builds that will be running at that time for the rawhide will be > canceled and can be resubmitted by maintainers after the branching. > > All rawhide updates that are in a pending state for rawhide will be unpushed. > > Once Fedora Linux 39 is branched we will reenable builds in koji with > notification to this list. Just a quick update; we branched Rawhide to Fedora 39 in Fedora Copr yesterday, and recently made the chroots available. Happy building! Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Mock v5.0 released (and mock-core-configs v39)
Hello maintainers! Let me announce a new release of Mock v5.0 (the chroot build environment manager for building RPMs). This release release brings lots of changes, though the one that I'd like to underline is that we turned --use-bootstrap-image ON by default. This effectively means that Mock uses Podman to pull the bootstrap image from image registries (instead of installing it from scratch with `dnf --installroot`). Thus Podman is now in `Recommends:`, not just `Suggests:`. Should you have any issues, you can temporarily revert this change with `--no-bootstrap-image` (--scrub=all first!). Alternatively set `config_opts["use_bootstrap_image"] = False` in configuration. Mock 5.0 also stops using '/sbin/useradd' inside the chroot, but uses '/sbin/useradd --prefix ' _on host_ to modify the in-chroot /etc/passwd. This change passed all our testing, but there's a potential for bugs. The mock-core-configs-v39 brings also the Fedora 39 configuration as it is now branched from Rawhide (Rawhide is 40 now in Mock). Several folks already reported that Fedora Copr builds are broken for fedora-rawhide-*, sorry for inconveniences. This is being resolved right now, we are pushing mock-5.0 into the Fedora Copr production. In case of any trouble, please report issues upstream: https://github.com/rpm-software-management/mock/issues Full release notes: https://rpm-software-management.github.io/mock/Release-Notes-5.0 The updated packages are in Bodhi: [Fedora 38]: https://bodhi.fedoraproject.org/updates/FEDORA-2023-0ca9df2164 [Fedora 37]: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c65d483a5c [EPEL 9]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-e03c59145d [EPEL 8]: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-a5c155a6c0 Happy building! Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Copr builders updated to Fedora 38
On středa 14. června 2023 12:37:24 CEST Pavel Raiskup wrote: > On čtvrtek 8. června 2023 17:42:13 CEST Pavel Raiskup wrote: > > Hello maintainers! > > > > Copr builders have been updated to Fedora 38 today (some old builders > > might still be running F37 ATM, but when they finish the task(s) they > > work on, they will be deleted). Our testsuite is passing just fine, so > > you _should_ be fine too :-). Please let us know if you have some > > troubles. > > > > There was one important change in Fedora 38 - RPM switched to the > > Sequoia crypto backend. It refuses SHA-1 in crypto; which basically > > disallows Mock to properly check EL6 GPG signatures. To allow further > > builds, we switched to gpgcheck=0 for all epel-6 chroots. If you know a > > better work-around, let me know. > > As it turns out, epel-6 config was based on CentOS 6 and EPEL 6, and the > problem was with the CentOS 6 certificate (not EPEL 6). With the 1-line > change [1], epel-6 chroots were changed to RHEL+EPEL instead of > CentOS+EPEL, so we can again use `gpgcheck=1` (even on F38). > > [1] > https://pagure.io/fedora-infra/ansible/c/b9c69f5cac314c18a539c42d1ca3bf28e59dd51e FTR, with DNF5 things just work for some reason. Which was especially confusing to me (dnf5 is the default package manager on my workstation): https://github.com/rpm-software-management/dnf5/issues/617 Seems like the policy is entirely ignored with dnf5? I'm not sure, but if anything - worth debugging. BTW. without the original problem in hand, this would be spotted much later. Pavel > Pavel > > > > > Pavel > > > > > > > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Copr builders updated to Fedora 38
On čtvrtek 8. června 2023 17:42:13 CEST Pavel Raiskup wrote: > Hello maintainers! > > Copr builders have been updated to Fedora 38 today (some old builders > might still be running F37 ATM, but when they finish the task(s) they > work on, they will be deleted). Our testsuite is passing just fine, so > you _should_ be fine too :-). Please let us know if you have some > troubles. > > There was one important change in Fedora 38 - RPM switched to the > Sequoia crypto backend. It refuses SHA-1 in crypto; which basically > disallows Mock to properly check EL6 GPG signatures. To allow further > builds, we switched to gpgcheck=0 for all epel-6 chroots. If you know a > better work-around, let me know. As it turns out, epel-6 config was based on CentOS 6 and EPEL 6, and the problem was with the CentOS 6 certificate (not EPEL 6). With the 1-line change [1], epel-6 chroots were changed to RHEL+EPEL instead of CentOS+EPEL, so we can again use `gpgcheck=1` (even on F38). [1] https://pagure.io/fedora-infra/ansible/c/b9c69f5cac314c18a539c42d1ca3bf28e59dd51e Pavel > Pavel > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Copr builders updated to Fedora 38
On úterý 13. června 2023 16:57:42 CEST Neal H. Walfield wrote: > On Thu, 08 Jun 2023 21:37:09 +0200, > Ondřej Budai wrote: > > RPM Sequoia's crypto policies can be configured, so you should be able to > > re-enable SHA-1. However, this would > > be a global change, not only for EL6... See > > https://docs.rs/sequoia-policy-config/latest/sequoia_policy_config/#hash-functions > > ... > > On Thu, Jun 8, 2023 at 5:42 PM Pavel Raiskup wrote: > > > > Hello maintainers! > > > > Copr builders have been updated to Fedora 38 today (some old builders > > might still be running F37 ATM, but when they finish the task(s) they > > work on, they will be deleted). Our testsuite is passing just fine, so > > you _should_ be fine too :-). Please let us know if you have some > > troubles. > > > > There was one important change in Fedora 38 - RPM switched to the > > Sequoia crypto backend. It refuses SHA-1 in crypto; which basically > > disallows Mock to properly check EL6 GPG signatures. To allow further > > builds, we switched to gpgcheck=0 for all epel-6 chroots. If you know a > > better work-around, let me know. > > I find this behavior surprising. The default policy as set by > fedora-crypto-policies is for rpm-sequoia is to accept SHA-1 (and > DSA-1024, ...): > > > https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/blob/master/policies/FEDORA38.pol#L75 > > What policy are you using? I was wrong. The problem was *not* with the EPEL-6 signatures, but with CentOS 6 signatures. It is a bit harder to analyse, as `sq-keyring-linter` is silent for that one: $ sq-keyring-linter < /usr/share/distribution-gpg-keys/centos/RPM-GPG-KEY-CentOS-6 $ echo $? 0 Pavel > Neal ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Copr builders updated to Fedora 38
On úterý 13. června 2023 16:57:42 CEST Neal H. Walfield wrote: > On Thu, 08 Jun 2023 21:37:09 +0200, > Ondřej Budai wrote: > > RPM Sequoia's crypto policies can be configured, so you should be able to > > re-enable SHA-1. However, this would > > be a global change, not only for EL6... See > > https://docs.rs/sequoia-policy-config/latest/sequoia_policy_config/#hash-functions > > ... > > On Thu, Jun 8, 2023 at 5:42 PM Pavel Raiskup wrote: > > > > Hello maintainers! > > > > Copr builders have been updated to Fedora 38 today (some old builders > > might still be running F37 ATM, but when they finish the task(s) they > > work on, they will be deleted). Our testsuite is passing just fine, so > > you _should_ be fine too :-). Please let us know if you have some > > troubles. > > > > There was one important change in Fedora 38 - RPM switched to the > > Sequoia crypto backend. It refuses SHA-1 in crypto; which basically > > disallows Mock to properly check EL6 GPG signatures. To allow further > > builds, we switched to gpgcheck=0 for all epel-6 chroots. If you know a > > better work-around, let me know. > > I find this behavior surprising. The default policy as set by > fedora-crypto-policies is for rpm-sequoia is to accept SHA-1 (and > DSA-1024, ...): > > > https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/blob/master/policies/FEDORA38.pol#L75 > > What policy are you using? The `DEFAULT:SHA1`, but it is weird - I can not reproduce the build failure now. Is something changing in the backgrounds? So lemme try to revert back to the nogpgcheck=1 variant. Thank you for the hint, Neal! Pavel > > Neal > ___ > devel mailing list -- de...@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Copr builders updated to Fedora 38
On čtvrtek 8. června 2023 21:37:09 CEST Ondřej Budai wrote: > RPM Sequoia's crypto policies can be configured, so you should be able to > re-enable SHA-1. However, this would be a global change, not only for > EL6... See > https://docs.rs/sequoia-policy-config/latest/sequoia_policy_config/#hash-functions > > Cheers, > Ondřej Thank you very much for the reference, Odřej! I'm not strongly against anything; but rather than weaker policy for everything I slightly prefer keeping the _stricter default policy_ with _disabled gpgcheck for EL6_ (we should phase epel-6 out entirely anyway since it's long time EOL, but we still keep it for the distro upgrade team(s)). This is up to the community to decide, let us know in our issue tracker if you are concerned. Pavel > On Thu, Jun 8, 2023 at 5:42 PM Pavel Raiskup wrote: > > > Hello maintainers! > > > > Copr builders have been updated to Fedora 38 today (some old builders > > might still be running F37 ATM, but when they finish the task(s) they > > work on, they will be deleted). Our testsuite is passing just fine, so > > you _should_ be fine too :-). Please let us know if you have some > > troubles. > > > > There was one important change in Fedora 38 - RPM switched to the > > Sequoia crypto backend. It refuses SHA-1 in crypto; which basically > > disallows Mock to properly check EL6 GPG signatures. To allow further > > builds, we switched to gpgcheck=0 for all epel-6 chroots. If you know a > > better work-around, let me know. > > > > Pavel > > > > > > ___ > > devel mailing list -- de...@lists.fedoraproject.org > > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org > > Do not reply to spam, report it: > > https://pagure.io/fedora-infrastructure/new_issue > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora Copr builders updated to Fedora 38
Hello maintainers! Copr builders have been updated to Fedora 38 today (some old builders might still be running F37 ATM, but when they finish the task(s) they work on, they will be deleted). Our testsuite is passing just fine, so you _should_ be fine too :-). Please let us know if you have some troubles. There was one important change in Fedora 38 - RPM switched to the Sequoia crypto backend. It refuses SHA-1 in crypto; which basically disallows Mock to properly check EL6 GPG signatures. To allow further builds, we switched to gpgcheck=0 for all epel-6 chroots. If you know a better work-around, let me know. Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Outage: Upgrade of Copr servers - 2023-04-05 12:00 UTC
And here is the link to the release-notes, sorry for the delay: https://docs.pagure.org/copr.copr/release-notes/2023-04-05.html Happy building, Pavel On pondělí 3. dubna 2023 19:21:48 CEST Jiri Kyjovsky wrote: > Hello, > > There will be an outage starting at: > > $ date --date '2023-04-05 12:00 UTC' > > The outage will last approximately 3 hours. The copr-backend storage (copr > build results) will stay mostly online during this outage but some downtime > is expected. > > Reason for outage: > We're updating copr packages to the new versions which will bring new > features and bugfixes. > > Affected Services: > copr-frontend - https://copr.fedorainfracloud.org > copr-backend - https://copr-be.cloud.fedoraproject.org/ > > Ticket: > https://pagure.io/fedora-infrastructure/issue/11201 > > Contact persons: > @frostyx / @praiskup / @nikromen > > Please join #fedora-admin in irc.libera.chat or add comments to the ticket > for > this outage above. > > JIri ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Can a Copr group be migrated to a different FAS group?
On pátek 3. března 2023 11:25:09 CET Miro Hrončok wrote: > we have recently migrated our packaging use case from the python-sig FAS group > to python-packagers-sig. > > Is it possible, perhaps by adjusting the datat in the database, to > migrate the copr @python group from python-sig to python-packagers-sig > FAS group? Thanks. As long as - we can keep the '@python' naming Copr-side, and - you have no other Copr group defined for the `python-packagers-sig` FAS group already it should be possible. Ping me off-list next week and we can test this first on stg.* and do the change. Pavel > https://copr.fedorainfracloud.org/groups/g/python/coprs/ > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora Linux 38 branched
On pátek 10. února 2023 11:38:25 CET Iñaki Ucar wrote: > On Fri, 10 Feb 2023 at 11:35, Peter Robinson wrote: > > > > On Fri, Feb 10, 2023 at 10:27 AM Iñaki Ucar wrote: > > > > > > On Fri, 10 Feb 2023 at 09:44, Jakub Kadlcik wrote: > > > > > > > > Hello Tomas, > > > > thank you for the announcement. > > > > > > > > We also branched Fedora 38 in Copr so that everybody can submit builds > > > > for it by now. Also, all projects with the "Follow Fedora branching" > > > > option configured in their project settings have F38 chroots > > > > automatically enabled and they contain the last build results from > > > > Fedora Rawhide before the branch. > > > > > > Is this still ongoing? I don't see F38 in my projects. > > > > I do in all of my packages, you should just need to do a git pull to > > get the new branches. > > I meant in Copr. Just confirming - Copr branching is a two-phase process; we first link the RPMs from rawhide to the branched release, and then we enable (when we know the chroot is building fine). https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-process When Jakub announced, we just had those packages hardlinked, and RPMs available on backend. But the 38 chroots got enabled later (next day). Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Copr backend unplanned outage
Hello all, our RAID storage got stuck this night (CET). Likely some deadlock caused by high I/O - caused by the periodic "RAID check" process together with the Fedora Rawhide => F38 branching task that has been done yesterday. But the actual cause is unknown (if this looks familiar to you, let us know). We ended up with about 400 processes hanged, waiting for disk (kill -9 has no effect). This is the second time this happened on F37 but "echo idle > /sys/block/md127/md/sync_action" did not help now (nor 'frozen'), only hard reboot using the AWS console helped eventually. We were more than 7 hours offline (the team was sleeping): https://pagure.io/fedora-infrastructure/issue/11120 Sorry for the inconvenience, and thank you for all the reports! Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: copr.fedorainfracloud.org: Can not create storage directory for uploaded file: [Errno 13] Permission denied: '/var/lib/copr/data/srpm_storage/tmpXXX' -> '/var/lib/copr/data/srpm_storage/tmpYYY/ZZZ
Hi Ivan, thank you for your e-mail! On úterý 29. listopadu 2022 23:33:11 CET Ivan Mironov wrote: > For more than a day I am seeing following when trying to upload SRPM into > copr.fedorainfracloud.org: > > Error 500: Unknown error > Can not create storage directory for uploaded file: [Errno 13] Permission > denied: '/var/lib/copr/data/srpm_storage/tmpXXX' -> > '/var/lib/copr/data/srpm_storage/tmpYYY/ZZZ' > > This happens with both copr-cli and the web interface. On čtvrtek 1. prosince 2022 2:57:22 CET Ivan Mironov wrote: > Okay, seems it was fixed. This was a temporary SELinux issue: https://github.com/fedora-copr/copr/pull/2403 > (If this is not the right place o report such problems then please provide a > link to the right one.) Correct place! Maybe even slightly better is our issue tracker: https://github.com/fedora-copr/copr/issues Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Outage: Upgrade of Copr servers - 2022-11-28 12:00 UTC
aaand finally this long outage is over. This wasn't ideal, sorry for any inconveniences. There were some PEBKAC problems while migrating the storage to a new F37 instance, some signature problems (a few builds failed because of sign error, please resubmit them) and some failed to import (resubmit as well). Otherwise, we are finally fully on F37 (builders and infrastructure) and everything appears to be working. It was a long day so we'll continue tomorrow with remaining stuff, e.g. sending updated cli packages and providing release notes. Happy building. Copr Team On neděle 27. listopadu 2022 2:15:28 CET Jakub Kadlčík wrote: > > frostyx reported a new issue against the project: `fedora-infrastructure` > that you are following: > `` > There will be an outage starting at: > > ``` > $ date --date '2022-11-28 13:30 UTC' > ``` > > The outage will last approximately 3 hours. The copr-backend storage (copr > build results) will stay mostly online during this outage but some downtime > is expected. > > Reason for outage: > We're updating copr packages to the new versions which will bring new > features and bugfixes. We are also upgrading our servers to F37. > > Affected Services: > copr-frontend - https://copr.fedorainfracloud.org > copr-backend - https://copr-be.cloud.fedoraproject.org/ > > Contact persons: > @frostyx / @praiskup / @nikromen > > Please join #fedora-admin in irc.libera.chat or add comments to the ticket for > this outage above. > `` > > To reply, visit the link below or just reply to this email > https://pagure.io/fedora-infrastructure/issue/11011 > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Outage: Upgrading the Fedora Copr backend storage, 2022-10-28 -- 2022-10-30
And the outage is over, everything should be back online and working. The outage eventually took little less than 7 hours (stopped queue), and were about 5-10 minutes fully down (no yum repos available). We'll send more detailed email the next week (or dump a blog post or something). Happy building! Copr Team On Friday, October 28, 2022 9:28:05 PM CET Pavel Raiskup wrote: > The outage just began. Copr is still running, but with a limitted quota. > Please delay long builds and bigger rebuilds till Sunday evening. > > Have a nice weekend, > Pavel > > On Friday, October 21, 2022 3:17:20 PM CEST Pavel Raiskup wrote: > > We need to replace the volume hosting our RPM/YUM repo data with a larger > > one. > > > > As a consequence, we'll have to stop the build queue processing for about 20 > > hours, and we'll have two "full" (but short) outages (2x5 minutes) when the > > yum > > repositories will be unavailable. > > > > The anticipated start of the outage (queue stops processing) is Saturday > > 2022-10-29: > > > > $ date --date "2022-10-29 17:00 UTC" > > Sat Oct 29 07:00:00 PM CEST 2022 > > > > But a few hours before, we'll lower the build throughput a bit to > > prioritize the > > I/O we have on the data migration task.. > > > > We'd like to kindly ask you to minimize the build throughput in the Fedora > > Copr build service during the weekend in question — just to allow us to > > make the transition as smooth as possible. It would be ideal if you could > > e.g. delay your mass rebuilding and other large data modifications tasks > > until the storage movement is over. That said, we don't plan to turn the > > frontend machine off (API and web-UI) during the whole outage period. > > > > For more info, see the more detailed schedule: > > https://docs.google.com/spreadsheets/d/1URopuw2R533H6i4vSTH8Nt47EIhs3ubWcLUXvRcxTRQ/edit#gid=0 > > > > Affected services: > > - Copr service (frontend): > > https://copr.fedorainfracloud.org > > - Copr (backend) repositories: > > https://download.copr.fedorainfracloud.org/ (AWS CloudFront proxy) > > https://copr-be.cloud.fedoraproject.org/ (storage) > > > > Sorry for the inconvenience, > > Copr Team > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Outage: Upgrading the Fedora Copr backend storage, 2022-10-28 -- 2022-10-30
The outage just began. Copr is still running, but with a limitted quota. Please delay long builds and bigger rebuilds till Sunday evening. Have a nice weekend, Pavel On Friday, October 21, 2022 3:17:20 PM CEST Pavel Raiskup wrote: > We need to replace the volume hosting our RPM/YUM repo data with a larger one. > > As a consequence, we'll have to stop the build queue processing for about 20 > hours, and we'll have two "full" (but short) outages (2x5 minutes) when the > yum > repositories will be unavailable. > > The anticipated start of the outage (queue stops processing) is Saturday > 2022-10-29: > > $ date --date "2022-10-29 17:00 UTC" > Sat Oct 29 07:00:00 PM CEST 2022 > > But a few hours before, we'll lower the build throughput a bit to prioritize > the > I/O we have on the data migration task.. > > We'd like to kindly ask you to minimize the build throughput in the Fedora > Copr build service during the weekend in question — just to allow us to > make the transition as smooth as possible. It would be ideal if you could > e.g. delay your mass rebuilding and other large data modifications tasks > until the storage movement is over. That said, we don't plan to turn the > frontend machine off (API and web-UI) during the whole outage period. > > For more info, see the more detailed schedule: > https://docs.google.com/spreadsheets/d/1URopuw2R533H6i4vSTH8Nt47EIhs3ubWcLUXvRcxTRQ/edit#gid=0 > > Affected services: > - Copr service (frontend): > https://copr.fedorainfracloud.org > - Copr (backend) repositories: > https://download.copr.fedorainfracloud.org/ (AWS CloudFront proxy) > https://copr-be.cloud.fedoraproject.org/ (storage) > > Sorry for the inconvenience, > Copr Team > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: reporting a a very old bug (now sending to ML)
On Monday, October 24, 2022 3:53:09 PM CEST Sérgio Basto wrote: > On Mon, 2022-10-24 at 13:54 +0200, Miroslav Suchý wrote: > > Dne 23. 10. 22 v 5:55 Sérgio Basto napsal(a): > > > The bug is after web page of results show the firsts results, the > > > web > > > page is cached and is never updated again. While new files of log > > > are > > > > Ctrl+Shift+R > > > > https://answersdb.com/browser/what-is-difference-between-ctrl-r-and-ctrl-shift-r.html > > > > Should the trick. > > It doesn't, I tried before sent this email, even tried with a > different browser . It indeed doesn't. We always need to wait till the cache entry expires. The 'builder-live.log' file is though excluded from caching entirely; what _is_ cached is the _directory listing_. That said, if you go directly to the log (log.gz) file (or even rpm file), it should work. Pavel > > We are using AWS CloudFront as a CDN. And it should honor the browser > > http header to invalidate headers. But anything in > > the chain browser-CDN-Copr can break it. > > ___ > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > > To unsubscribe send an email to > > copr-devel-le...@lists.fedorahosted.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: > > https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > > Do not reply to spam, report it: > > https://pagure.io/fedora-infrastructure/new_issue > > > -- > Sérgio M. B. > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: reporting a a very old bug
On Monday, October 24, 2022 10:58:44 AM CEST Tomas Tomecek wrote: > Pavel, would this help here? > https://github.com/packit/packit-service/issues/1714 (SRPM build log should > point at builder-live.log, not builder-live.log.gz) I think that we are already mixing 3 "problems" into a single one (Packit, local-copr use-case, and CloudFront in Fedora Copr). But yes, it is better to access 'builder-live.log' - because once that disappears, Backend is able to redirect to 'builder-live.log.gz'. Pavel > On Sun, Oct 23, 2022 at 5:59 AM Sérgio Basto wrote: > > > Hi, > > The bug is simply to report, I found it some months ago it with help of > > FrostyX IIRC, after install my own corp build in a laptop . > > > > The bug is after web page of results show the firsts results, the web > > page is cached and is never updated again. While new files of log are > > accessible the web page doesn't show it , this happens to me a lot when > > I'm looking at builder-live.log.gz file while building is happening . > > > > For example > > > > https://download.copr.fedorainfracloud.org/results/sergiomb/vboxfor23/fedora-36-x86_64/04962643-kBuild/ > > doesn't show any build.log.gz and build.log.gz is there in the same > > place ase usual > > > > https://download.copr.fedorainfracloud.org/results/sergiomb/vboxfor23/fedora-36-x86_64/04962643-kBuild/build.log.gz > > > > > > Thanks , > > -- > > Sérgio M. B. > > ___ > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > > Do not reply to spam, report it: > > https://pagure.io/fedora-infrastructure/new_issue > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: reporting a a very old bug
Hello Sérgio, thank you for the question! On Sunday, October 23, 2022 5:55:05 AM CEST Sérgio Basto wrote: > The bug is simply to report, I found it some months ago it with help of > FrostyX IIRC, after install my own corp build in a laptop . is this a local-only behavior? I'm getting confused. > The bug is after web page of results show the firsts results, the web > page is cached and is never updated again. The behavior is documented here: https://docs.pagure.org/copr.copr/user_documentation.html#build-succeeded-but-i-don-t-see-the-built-results But this only ever happens on download.copr.* page, because it is cached through AWS CloudFront. This is not what is happening on your local machine! > While new files of log are accessible the web page doesn't show it , this > happens to me a lot when I'm looking at builder-live.log.gz file while > building is happening . Sure, the compressed file doesn't exist while build is done. We "stream" the live log from backend, and once the bulid finishes we compress it. Which basically means that 'builder-live.log' is renamed to 'builder-live.log.gz'. Frontend knows about this, so it provides a valid log URL. Later, we have a lighttpd-based redirect from '*.log' to '*.log.gz' when the '.log' file doesn't exist. Certainly you can not download the compressed when it doesn't exist yet. > For example > https://download.copr.fedorainfracloud.org/results/sergiomb/vboxfor23/fedora-36-x86_64/04962643-kBuild/ > doesn't show any build.log.gz and build.log.gz is there in the same > place ase usual > https://download.copr.fedorainfracloud.org/results/sergiomb/vboxfor23/fedora-36-x86_64/04962643-kBuild/build.log.gz This doesn't seem related to your local machine use-case? Here continues my confusion. Pavel > > Thanks , > -- > Sérgio M. B. > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Outage: Upgrading the Fedora Copr backend storage, 2022-10-28 -- 2022-10-30
We need to replace the volume hosting our RPM/YUM repo data with a larger one. As a consequence, we'll have to stop the build queue processing for about 20 hours, and we'll have two "full" (but short) outages (2x5 minutes) when the yum repositories will be unavailable. The anticipated start of the outage (queue stops processing) is Saturday 2022-10-29: $ date --date "2022-10-29 17:00 UTC" Sat Oct 29 07:00:00 PM CEST 2022 But a few hours before, we'll lower the build throughput a bit to prioritize the I/O we have on the data migration task.. We'd like to kindly ask you to minimize the build throughput in the Fedora Copr build service during the weekend in question — just to allow us to make the transition as smooth as possible. It would be ideal if you could e.g. delay your mass rebuilding and other large data modifications tasks until the storage movement is over. That said, we don't plan to turn the frontend machine off (API and web-UI) during the whole outage period. For more info, see the more detailed schedule: https://docs.google.com/spreadsheets/d/1URopuw2R533H6i4vSTH8Nt47EIhs3ubWcLUXvRcxTRQ/edit#gid=0 Affected services: - Copr service (frontend): https://copr.fedorainfracloud.org - Copr (backend) repositories: https://download.copr.fedorainfracloud.org/ (AWS CloudFront proxy) https://copr-be.cloud.fedoraproject.org/ (storage) Sorry for the inconvenience, Copr Team ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: ATTENTION: Copr will be temporarily deleting failed and outdated builds after 7 days
On Friday, October 21, 2022 11:48:43 AM CEST Miro Hrončok wrote: > On 30. 09. 22 18:05, Jiri Kyjovsky wrote: > > Hello, > > > > Due to problems with free disk storage, Copr will be temporarily deleting > > failed and outdated builds after 7 days instead of the default 14 days > > until > > migration to another disk storage takes place. > > Hey, is there any ETA for the migration? We are still working on the schedule. It will very likely happen during the weekend 2022-10-28 — 2022-10-30. We'll keep you posted. Pavel > Thanks, > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
OUTAGE: Fedora Copr enlarging the backend infra VM
We plan to power-cycle one virtual machine in our infrastructure and boost the computational power there. In thurn the build results (RPMs/metadata) are going to be offline for a short period of time (up to 10 minutes). More info on #fedora-buildsys irc channel (libera chat). Links: https://pagure.io/fedora-infrastructure/issue/10943 https://status.fedoraproject.org/ Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Inconsistency of bash behaviour on fedora aarch64 and x86_64 images
On Tuesday, September 6, 2022 1:38:56 PM CEST TommyLike Hu wrote: > I mean this command [1] below doesn't work well on the aarch64 container, > it's not related to the file/directory permissions at all. What makes you think so? What is the output from: $ stat "$directory" $ [ -w "$directory" ] ; echo $? > ``` > if [ -w $directory ] ; then echo 'Success!' ; fi > ``` > Maybe I should report an issue on related package [2] ? Yes, the binary is owned by coreutils: $ rpm -qf /usr/bin/\[ coreutils-9.0-8.fc36.x86_64 But '[' is also a Bash built-in. Pavel > > [1]: https://man7.org/linux/man-pages/man1/test.1.html > [2]: https://src.fedoraproject.org/rpms/coreutils > > On Tue, Sep 6, 2022 at 4:35 PM Pavel Raiskup wrote: > > > On Tuesday, September 6, 2022 1:35:30 AM CEST TommyLike Hu wrote: > > > Sure, that would be easy to test this on an arm instance with script > > > something like this: > > > ``` > > > > > > if [ -w $directory ] ; then echo 'Success!' ; fi > > > > What path is held by the $directory / $REPODIR variables? > > > > Pavel > > > > P.S. double-quote > > > > > ``` > > > > > > On Tue, Sep 6, 2022 at 5:27 AM Jakub Kadlcik > > wrote: > > > > > > > Hello TommyLike, > > > > a disclaimer first - I have never tried to run the Copr containers on > > > > an arm architecture, and I am not really a bash person. But > > > > > > > > if [ ! -w $REPODIR ] ; then > > > > > > > > Checks if a file (or I guess a directory) is writable. Are you sure > > > > you have the correct permissions for $REPODIR ? > > > > > > > > Jakub > > > > > > > > On Mon, Sep 5, 2022 at 4:59 PM TommyLike Hu > > wrote: > > > > > > > > > > Hey COPR Developers, > > > > > Recently, I am trying to deploy COPR containers on an arm > > instance, > > > > except for the base image and resalloc pool tag issues, I also found > > there > > > > is a strange thing on bash command, check this code from dist-git [1] > > below: > > > > > ``` > > > > > if [ ! -w $REPODIR ] ; then > > > > > echo "ERROR: You can not write to $REPODIR" > > > > > echo "ERROR: You can not create repos" > > > > > exit -1 > > > > > fi > > > > > ``` > > > > > This would always fail in an aarch64 container which uses the > > identical > > > > dockerfile as the x86 ones. > > > > > ``` > > > > > > > > > > FROM registry.fedoraproject.org/fedora:35 > > > > > MAINTAINER copr-devel@lists.fedorahosted.org > > > > > > > > > > ``` > > > > > Could this be a fedora issue? Considering I tried fedora 35/36/37 > > which > > > > all failed. > > > > > > > > > > > > > > > [1]: > > > > > > https://github.com/release-engineering/dist-git/blob/738dc51b8dff6f06a3d4be5f0f480aebf36b1480/scripts/dist-git/setup_git_package#L72 > > > > > > > > > > ___ > > > > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > > > > > To unsubscribe send an email to > > copr-devel-le...@lists.fedorahosted.org > > > > > Fedora Code of Conduct: > > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > > > > List Guidelines: > > https://fedoraproject.org/wiki/Mailing_list_guidelines > > > > > List Archives: > > > > > > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > > > > > Do not reply to spam, report it: > > > > https://pagure.io/fedora-infrastructure/new_issue > > > > ___ > > > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > > > > To unsubscribe send an email to > > copr-devel-le...@lists.fedorahosted.org > > > > Fedora Code of Conduct: > > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > > > List Guidelines: > > https://fedoraproject.org/wiki/Mailing_list_guidelines > > > > List Archives: > > > > > > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > > > > Do not reply to spam, report it: > > > > https://pagure.io/fedora-infrastructure/new_issue > > > > > > > > > > > > > > > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Inconsistency of bash behaviour on fedora aarch64 and x86_64 images
On Tuesday, September 6, 2022 1:35:30 AM CEST TommyLike Hu wrote: > Sure, that would be easy to test this on an arm instance with script > something like this: > ``` > > if [ -w $directory ] ; then echo 'Success!' ; fi What path is held by the $directory / $REPODIR variables? Pavel P.S. double-quote > ``` > > On Tue, Sep 6, 2022 at 5:27 AM Jakub Kadlcik wrote: > > > Hello TommyLike, > > a disclaimer first - I have never tried to run the Copr containers on > > an arm architecture, and I am not really a bash person. But > > > > if [ ! -w $REPODIR ] ; then > > > > Checks if a file (or I guess a directory) is writable. Are you sure > > you have the correct permissions for $REPODIR ? > > > > Jakub > > > > On Mon, Sep 5, 2022 at 4:59 PM TommyLike Hu wrote: > > > > > > Hey COPR Developers, > > > Recently, I am trying to deploy COPR containers on an arm instance, > > except for the base image and resalloc pool tag issues, I also found there > > is a strange thing on bash command, check this code from dist-git [1] below: > > > ``` > > > if [ ! -w $REPODIR ] ; then > > > echo "ERROR: You can not write to $REPODIR" > > > echo "ERROR: You can not create repos" > > > exit -1 > > > fi > > > ``` > > > This would always fail in an aarch64 container which uses the identical > > dockerfile as the x86 ones. > > > ``` > > > > > > FROM registry.fedoraproject.org/fedora:35 > > > MAINTAINER copr-devel@lists.fedorahosted.org > > > > > > ``` > > > Could this be a fedora issue? Considering I tried fedora 35/36/37 which > > all failed. > > > > > > > > > [1]: > > https://github.com/release-engineering/dist-git/blob/738dc51b8dff6f06a3d4be5f0f480aebf36b1480/scripts/dist-git/setup_git_package#L72 > > > > > > ___ > > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > > > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > > List Archives: > > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > > > Do not reply to spam, report it: > > https://pagure.io/fedora-infrastructure/new_issue > > ___ > > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > > Do not reply to spam, report it: > > https://pagure.io/fedora-infrastructure/new_issue > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 37 branched
On Wednesday, August 10, 2022 2:42:38 PM CEST Pavel Raiskup wrote: > Hi, Fedora 37 has been branched recently. We started the branching process: > https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-process > > ATM we submitted a task for copying fedora-rawhide builds into fedora-37, this > should be finished in about 24 hours. > > Currently, updates for mock-core-configs (with F37 configs) are being > submitted > to Bodhi. But note that we can not enable F37 in Copr till there's a working > compose and mirrors work (not at this moment). (a) repositories were copied in Copr (b) there seems to be a working compose for F37 The Fedora 37 chroot was enabled in Copr, happy building! Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Fedora 37 branched
Hi, Fedora 37 has been branched recently. We started the branching process: https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-process ATM we submitted a task for copying fedora-rawhide builds into fedora-37, this should be finished in about 24 hours. Currently, updates for mock-core-configs (with F37 configs) are being submitted to Bodhi. But note that we can not enable F37 in Copr till there's a working compose and mirrors work (not at this moment). Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: [Copr] flug_m/duo_unix: flugm4 is requesting permissions change
On Thursday, July 28, 2022 11:14:21 PM CEST Matthew Roth wrote: > yes Hello Matthew, you can grant the requested permissions via web-UI or via copr cli: $ copr edit-permissions --builder/--admin flug_m/duo_unix Pavel > > On Jul 28, 2022, at 4:08 PM, r...@copr-fe.aws.fedoraproject.org wrote: > > > > flugm4 asked for these changes: > > > > Admin: nothing -> request > > > > Project: flug_m/duo_unix > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Unplanned Copr outage - 2022-07-08 and 2022-07-09
Copr failed to allocate VMs and assign VMs to the build task for several hours now, which lead to many build failures. Please restart the builds if you were affected. The issue is tracked here: https://pagure.io/copr/copr/issue/2066 Sorry for inconveniences. Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
No more builds for Fedora 34, EOL
Hello maintainers! Fedora 34 has been EOL for some time already: https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html I disabled the Fedora 34 chroots now, which started the standard build removal policy, for more info take a look at docs: https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Oracle Linux chroots (temporarily) available in Fedora Copr
After more then a year, the teams who previously needed these chroots already stopped using them. So the plan is to drop the oraclelinux* chroots by the end of this month (July 2022). Please let us know if you need more time. Pavel On Tuesday, August 3, 2021 10:21:51 AM CEST Pavel Raiskup wrote: > Hello, > > just a quick note - we enabled Oracle Linux chroots in Fedora Copr today, > this is temporarily needed by OAMG/LEAPP team for their CI/CD system. > Feel free to test those chroots, but please don't heavily depend on them > as we don't know when we'll again drop them (preferably use > epel/centos-stream chroots instead, they should provide similar build > results). > > Pavel > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
The epel-9 chroots moved to rhel+epel
The post- RHEL 9 GA time allowed us to move the epel-9-* chroots to the official RHEL 9 + EPEL content (from previous CentOS Stream 9 + EPEL 9). Should you have any problems with RHEL+EPEL 9, please report. Just to recap, it means that EPEL 9 chroots use similar principles to previously moved EPEL 8, while EPEL 7 still uses (supported) CentOS 7: https://lists.fedoraproject.org/archives/list/copr-devel@lists.fedorahosted.org/thread/6J2SADUV5SF5I63COQR5HBQNO64IBS2X/ Description in the "project -> settings" (and "$ copr list-chroots") were updated accordingly to self-document. Happy building, Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora Copr, new Power9 builders
Hello all, Fedora infra folks recently racked for a new Power9 machine for Fedora Copr, and we now finished the installation. The new machine is hosting ~30 production builder VMs). This machine is going to replace the two older Power8 boxes. To fixup some startup issues we had to provide a new golden image, so while on it—golden images for all our infrastructure locations were regenerated (all architectures). This is JFYI e-mail, should you have any issues please report them. Happy building! Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Problem with PPC builders
Hello Steve, On Saturday, May 14, 2022 5:08:05 PM CEST Steven A. Falco wrote: > Over the last few days there seems to be a bottleneck on the PPC builders. > > For example, please see [1], [2], and [3]. The x86_64 builds all finished > promptly, but the ppc64le builds are taking a very long time to even get > started. > > If someone with admin privileges could take a look, I'd appreciate it. this was probably a combination of several problems: - one of the two ppc64le machines went down - we have some storage slowdown on ppc64le machines - there was some generic Fedora Copr outage at the time your builds below were started Overall, the immediate problems with ppc64le arch should be gone, and the situation should become better in the following days—we plan to finish configuration of a new Power9 machine that will be used for ppc64le builds. Sorry for inconveniences, Pavel > Thanks, Steve > > [1] https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/4412264/ > [2] https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/4412263/ > [3] https://copr.fedorainfracloud.org/coprs/g/kicad/kicad/build/4407059/ > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora Copr - highlights from the 2022-04-05 release
Hello. We are pleased to announce that we deployed a new Fedora Copr release. This time we added GSSAPI/Kerberos authentication support, we optimized the backend side for the large task queues we face last months, and fixed several bugs. More info: https://docs.pagure.org/copr.copr/release-notes/2022-04-05.html Happy building! Copr Team ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Outage: Upgrade of Copr servers - 2022-03-21 08:15 UTC
On Monday, March 21, 2022 10:37:56 AM CET Jakub Kadlčík wrote: > The outage is over now, everything should work as expected. > > For anyone interested, the release notes can be found here: > https://docs.pagure.org/copr.copr/release-notes/2022-03-21.html And just a small final update; we've just finished the re-signing of all the Enterprise Linux 9 packages with SHA256 hashalgo¹ (epel-9 and centos-stream-9 chroots). For more info see https://bugzilla.redhat.com/show_bug.cgi?id=2059101 This should mean that all the re-signed packages have compatible signature with EL9 systems. Should you still have any issues with signatures on EL9, please let us know. Pavel ¹ There are still two leftovers (@rubygems/rubygems and @copr/PyPI that are being done separately). > Happy building, > Jakub > > > Jakub Kadlčík writes: > > > Hello, > > > > There will be an outage starting at: > > > > date --date '2022-03-21 08:15 UTC' > > > > The outage will last approximately 2 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 and bugfixes. > > > > Affected Services: > > copr-frontend - https://copr.fedorainfracloud.org > > copr-backend - https://copr-be.cloud.fedoraproject.org/ > > > > Contact persons: > > @praiskup / @frostyx > > > > Ticket: > > https://pagure.io/fedora-infrastructure/issue/10595 > > > > > > Jakub > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Drop fedora-rawhide-armhfp config?
On Friday, February 18, 2022 12:40:47 PM CET Miro Hrončok wrote: > Fedora 37 no longer has armhfp/armv7hl compose nor Koji repo. > > Could you please remove the Copr chroot? > > I've opened https://github.com/rpm-software-management/mock/pull/867 for > mock-core-configs. Thanks for the info. Chroot have been made EOL in Copr. That means users can not enable that chroot anymore, and old builds will be removed after 180 days (unless explicitly prolonged by project administrators). Pavel > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Fedora 36 being branched right now in Fedora Copr
Fedora 36 enabled in Copr Production. Rawhide builds with fc37 already. Happy building! Pavel On Tuesday, February 8, 2022 1:49:57 PM CET Pavel Raiskup wrote: > Hello maintainers, and release engineering! > > According to the F36 schedule [1], Fedora 36 is going to be branched from > Rawhide today. > > So we started copying the Rawhide builds to Fedora 36 on Copr > right now [2]. I expect that everything will be finished no later than > tomorrow morning (2022-02-09 GMT). Feel free to monitor the progress in > the Actions graph [3]. > > I am now thinking about enabling the F36 chroot a little bit earlier in > Fedora Copr than usually. Even though Fedora 36 doesn't have it's > own (non-rawhide) compose yet, the configuration shipped in the > mock-core-configs works fine now (so do mirrors) — even though the effect > is that F36 builds are actually done against the Fedora Rawhide. > > There shouldn't be any harm in this, we'll just basically duplicate the > Fedora Rawhide builds into the F36 chroots, till there's a separate > compose. > > Any idea why I shouldn't enable F36 once the copy action finishes > tomorrow? > > [1] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html > [2] > https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-process > [3] https://copr.fedorainfracloud.org/status/stats/ > > Pavel > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Fedora 36 being branched right now in Fedora Copr
Hello maintainers, and release engineering! According to the F36 schedule [1], Fedora 36 is going to be branched from Rawhide today. So we started copying the Rawhide builds to Fedora 36 on Copr right now [2]. I expect that everything will be finished no later than tomorrow morning (2022-02-09 GMT). Feel free to monitor the progress in the Actions graph [3]. I am now thinking about enabling the F36 chroot a little bit earlier in Fedora Copr than usually. Even though Fedora 36 doesn't have it's own (non-rawhide) compose yet, the configuration shipped in the mock-core-configs works fine now (so do mirrors) — even though the effect is that F36 builds are actually done against the Fedora Rawhide. There shouldn't be any harm in this, we'll just basically duplicate the Fedora Rawhide builds into the F36 chroots, till there's a separate compose. Any idea why I shouldn't enable F36 once the copy action finishes tomorrow? [1] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html [2] https://docs.pagure.org/copr.copr/how_to_manage_chroots.html#branching-process [3] https://copr.fedorainfracloud.org/status/stats/ Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
F35 builders deployed to Fedora Copr
Finally! All the builders were moved to Fedora 35. Test are passing on staging, so hopefully everything goes simiarly well in production. Happy building! Pavell On Wednesday, January 26, 2022 9:50:18 PM CET Pavel Raiskup wrote: > On Tuesday, January 25, 2022 5:16:31 PM CET Pavel Raiskup wrote: > > Hello maintainers, > > > > seems like we are finally able to migrate to Fedora 35. If all the > > necessary test pass, we should be OK to migrate tomorrow, 2022-01-25. > > We couldn't finish testing today. There are too many issues with the new > F35 qcow2 images (rpkg-util incompatibilities and spawning delays). > > This is to be deployed as soon as possible (tomorrow hopefully), I will > notify here once we are done with this. > > Pavel > > > > This also means that we'll finally run against rpkg-util v3+ == no way > > back to auto_pack feature. > > > > Pavel > > > > On Friday, December 17, 2021 12:32:37 PM CET Pavel Raiskup wrote: > > > Hello all, > > > > > > just a quick update on this topic. This took a bit more time than I > > > originally expected, but I was able to test that configuration. > > > > > > Please expect that step 2 happens on Monday, 2021-12-20 (I don't want to > > > break things just when weekend starts). > > > > > > For more info see the previous email, and we should be able to help you > > > next week with the migration on #fedora-buildsys, when needed. > > > > > > Also, the step 3 will be delayed at least by 20 days, so you still have > > > the > > > 1-month transition period. > > > > > > Sorry for inconvenience, > > > Pavel > > > > > > On Friday, November 19, 2021 9:44:51 AM CET Pavel Raiskup wrote: > > > > we are currently preparing Copr build system for migration to Fedora 35, > > > > including the builder workers. > > > > > > > > There's though, at least from the builder perspective, a major > > > > `rpkg-util` > > > > behavior change [1] (removal of `auto_pack` feature) that many of the > > > > Copr > > > > projects rely on. This is a bit unexpected as `auto_pack = True` has > > > > been > > > > the default in Copr for a long time, and the rpkg-util upstream > > > > intentions > > > > behind the feature were generally misunderstood (even in Copr team). > > > > > > > > That being said, some of the currently working builds on F34 would fail > > > > after the migration to F35. > > > > > > > > In order to make the migration a bit less dramatic, we plan to migrate > > > > in > > > > the following steps: > > > > > > > > 1. Document the feature drop and possible fixes/workarounds see [1], > > > > and > > > > properly announce the change in advance (here we are _now_). > > > > > > > > 2. Change the default, and turn off the `auto_pack` feature for > > > > relatively short period of time on the current F34 builders > > > > (ie autopack=False). This will happen soon in December 2021. > > > > The change will naturally trigger the build failures, but a bit > > > > earlier so users will be informed sooner ... with a _temporary_ > > > > work-around in hand => everyone can provide the file > > > > /rpkg.conf upstream, and opt-in the old behavior with > > > > with > > > > content like: > > > > > > > > [rpkg] > > > > # temporary work-around for rpkg-util v2, auto_pack is going to be > > > > # removed soon! See: > > > > # > > > > https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 > > > > auto_pack = True > > > > > > > > 3. Migrate to Fedora 35, early in January 2022. This will make the > > > > `auto_pack = True` work-around non-working, and users will have to > > > > adapt, again, see [1]. > > > > > > > > Of course, anyone is encouraged to migrate to the new syntax **right > > > > now**, > > > > sooner the better. If done correctly, package can be built both with > > > > rpkg-util > > > > v2 and v3 [2]. > > > > > > > > Sorry for inconvenience! Any comment, idea or help is welcome! > > > > > > > > [1] https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 > > > > [2] > > > > https://pagure.io/copr/copr-hello/c/739ff9910ee8a9c76d7e97de2f6176106dc19a09?branch=rpkg-util > > > > > > > > Pavel > > > > > > > > > > > > > > > > > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: rpkg-util v3 change, moving copr builders to F35
On Tuesday, January 25, 2022 5:16:31 PM CET Pavel Raiskup wrote: > Hello maintainers, > > seems like we are finally able to migrate to Fedora 35. If all the > necessary test pass, we should be OK to migrate tomorrow, 2022-01-25. We couldn't finish testing today. There are too many issues with the new F35 qcow2 images (rpkg-util incompatibilities and spawning delays). This is to be deployed as soon as possible (tomorrow hopefully), I will notify here once we are done with this. Pavel > This also means that we'll finally run against rpkg-util v3+ == no way > back to auto_pack feature. > > Pavel > > On Friday, December 17, 2021 12:32:37 PM CET Pavel Raiskup wrote: > > Hello all, > > > > just a quick update on this topic. This took a bit more time than I > > originally expected, but I was able to test that configuration. > > > > Please expect that step 2 happens on Monday, 2021-12-20 (I don't want to > > break things just when weekend starts). > > > > For more info see the previous email, and we should be able to help you > > next week with the migration on #fedora-buildsys, when needed. > > > > Also, the step 3 will be delayed at least by 20 days, so you still have the > > 1-month transition period. > > > > Sorry for inconvenience, > > Pavel > > > > On Friday, November 19, 2021 9:44:51 AM CET Pavel Raiskup wrote: > > > we are currently preparing Copr build system for migration to Fedora 35, > > > including the builder workers. > > > > > > There's though, at least from the builder perspective, a major `rpkg-util` > > > behavior change [1] (removal of `auto_pack` feature) that many of the Copr > > > projects rely on. This is a bit unexpected as `auto_pack = True` has been > > > the default in Copr for a long time, and the rpkg-util upstream intentions > > > behind the feature were generally misunderstood (even in Copr team). > > > > > > That being said, some of the currently working builds on F34 would fail > > > after the migration to F35. > > > > > > In order to make the migration a bit less dramatic, we plan to migrate in > > > the following steps: > > > > > > 1. Document the feature drop and possible fixes/workarounds see [1], and > > > properly announce the change in advance (here we are _now_). > > > > > > 2. Change the default, and turn off the `auto_pack` feature for > > > relatively short period of time on the current F34 builders > > > (ie autopack=False). This will happen soon in December 2021. > > > The change will naturally trigger the build failures, but a bit > > > earlier so users will be informed sooner ... with a _temporary_ > > > work-around in hand => everyone can provide the file > > > /rpkg.conf upstream, and opt-in the old behavior with with > > > content like: > > > > > > [rpkg] > > > # temporary work-around for rpkg-util v2, auto_pack is going to be > > > # removed soon! See: > > > # > > > https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 > > > auto_pack = True > > > > > > 3. Migrate to Fedora 35, early in January 2022. This will make the > > > `auto_pack = True` work-around non-working, and users will have to > > > adapt, again, see [1]. > > > > > > Of course, anyone is encouraged to migrate to the new syntax **right > > > now**, > > > sooner the better. If done correctly, package can be built both with > > > rpkg-util > > > v2 and v3 [2]. > > > > > > Sorry for inconvenience! Any comment, idea or help is welcome! > > > > > > [1] https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 > > > [2] > > > https://pagure.io/copr/copr-hello/c/739ff9910ee8a9c76d7e97de2f6176106dc19a09?branch=rpkg-util > > > > > > Pavel > > > > > > > > > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: rpkg-util v3 change, moving copr builders to F35
Hello maintainers, seems like we are finally able to migrate to Fedora 35. If all the necessary test pass, we should be OK to migrate tomorrow, 2022-01-25. This also means that we'll finally run against rpkg-util v3+ == no way back to auto_pack feature. Pavel On Friday, December 17, 2021 12:32:37 PM CET Pavel Raiskup wrote: > Hello all, > > just a quick update on this topic. This took a bit more time than I > originally expected, but I was able to test that configuration. > > Please expect that step 2 happens on Monday, 2021-12-20 (I don't want to > break things just when weekend starts). > > For more info see the previous email, and we should be able to help you > next week with the migration on #fedora-buildsys, when needed. > > Also, the step 3 will be delayed at least by 20 days, so you still have the > 1-month transition period. > > Sorry for inconvenience, > Pavel > > On Friday, November 19, 2021 9:44:51 AM CET Pavel Raiskup wrote: > > we are currently preparing Copr build system for migration to Fedora 35, > > including the builder workers. > > > > There's though, at least from the builder perspective, a major `rpkg-util` > > behavior change [1] (removal of `auto_pack` feature) that many of the Copr > > projects rely on. This is a bit unexpected as `auto_pack = True` has been > > the default in Copr for a long time, and the rpkg-util upstream intentions > > behind the feature were generally misunderstood (even in Copr team). > > > > That being said, some of the currently working builds on F34 would fail > > after the migration to F35. > > > > In order to make the migration a bit less dramatic, we plan to migrate in > > the following steps: > > > > 1. Document the feature drop and possible fixes/workarounds see [1], and > > properly announce the change in advance (here we are _now_). > > > > 2. Change the default, and turn off the `auto_pack` feature for > > relatively short period of time on the current F34 builders > > (ie autopack=False). This will happen soon in December 2021. > > The change will naturally trigger the build failures, but a bit > > earlier so users will be informed sooner ... with a _temporary_ > > work-around in hand => everyone can provide the file > > /rpkg.conf upstream, and opt-in the old behavior with with > > content like: > > > > [rpkg] > > # temporary work-around for rpkg-util v2, auto_pack is going to be > > # removed soon! See: > > # https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 > > auto_pack = True > > > > 3. Migrate to Fedora 35, early in January 2022. This will make the > > `auto_pack = True` work-around non-working, and users will have to > > adapt, again, see [1]. > > > > Of course, anyone is encouraged to migrate to the new syntax **right now**, > > sooner the better. If done correctly, package can be built both with > > rpkg-util > > v2 and v3 [2]. > > > > Sorry for inconvenience! Any comment, idea or help is welcome! > > > > [1] https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 > > [2] > > https://pagure.io/copr/copr-hello/c/739ff9910ee8a9c76d7e97de2f6176106dc19a09?branch=rpkg-util > > > > Pavel > > > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: On copr.fedorainfracloud.org, is the filesystem where the package is built local?
On Thursday, January 6, 2022 5:20:40 PM CET Miro Hrončok wrote: > Hello Copr, > > > just a quick question. When I build a package in Copr (the Fedora one) on > x86_64, is the mock chroot located on a local filesystem, or a NFS? Local, it is tmpfs. Pavel > Thanks, > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: my own copr-server
On Wednesday, January 5, 2022 12:42:40 PM CET Sérgio Basto wrote:
> On Wed, 2022-01-05 at 09:01 +0100, Pavel Raiskup wrote:
> > On Wednesday, January 5, 2022 1:03:51 AM CET Sérgio Basto wrote:
> > > On Tue, 2022-01-04 at 22:58 +, Sérgio Basto wrote:
> > > > On Tue, 2022-01-04 at 10:35 +0100, Silvie Chlupova wrote:
> > > > > Hi Sérgio,
> > > > > I can reproduce your problem by deleting the database in the
> > > > > copr_database_1 container and then running init-database.sh in
> > > > > the
> > > > > frontend container. You are missing the relations in
> > > > > copr_database_1.
> > > > > You can download the database dump here
> > > > > https://copr.fedorainfracloud.org/db_dumps/. Copy the extracted
> > > > > db
> > > > > dump
> > > > > into copr_database_1 and run psql coprdb < your_dump. Or try to
> > > > > delete
> > > > > the docker containers and images and then run docker-compose up -
> > > > > d
> > > > > once
> > > > > again. After successful completion, the relations in
> > > > > copr_database_1
> > > > > should be created, and after running init-database.sh, it should
> > > > > show
> > > > > text that some of the chroots that the script is trying to create
> > > > > already exist.
> > > >
> > > > wget -4
> > > > https://copr.fedorainfracloud.org/db_dumps/copr_db-2022-01-04_03-36.gz
> > > >
> > > > zcat copr_db-2022-01-04_03-36.gz | docker exec -i copr_database_1
> > > > psql
> > > > coprdb (the technique is use exec -i and not exec -it)
> > > >
> > > > now I have the all database of copr production but I want a clean
> > > > Database and configure my builders ( which is only one x86_64 )
> > > >
> > > >
> > > > I can't get rid of SQL: INSERT INTO dist_git_instance (name,
> > > > clone_url,
> > > > clone_package_uri, priority, default_namespace) VALUES (%(name)s,
> > > > %(clone_url)s, %(clone_package_uri)s, %(priority)s,
> > > > %(default_namespace)s) RETURNING dist_git_instance.id]
> > > > [parameters: {'name': 'fedora', 'clone_url':
> > > > 'https://src.fedoraproject.or
> > > >
> > > > where this is defined this insert ? or I make it to ignore it ?
> > > > where
> > > > is defined the schema of database ?
> > > >
> > > >
> > >
> > > From the backups give me by Silvie, I could extract the database
> > > schema
> > > , I drop all and just create the database schema with empty tables, I
> > > ran [2] without errors and things seems ready (after add the repos
> > > with
> > > [3])
> > > But now build 0001 failed with a sign problem [1] , any tip ?
> > >
> > > [1]
> > > [2022-01-04 23:45:00,757][ INFO][PID:10] Calling '/bin/sign -u
> > > sergiomb#first_...@copr.fedorahosted.org -p' (attempt #1)
> > > [2022-01-04 23:45:01,362][ INFO][PID:10] Calling '/bin/sign -u
> > > sergiomb#first_...@copr.fedorahosted.org -r
> > > /var/lib/copr/public_html/results/sergiomb/first_one/srpm-
> > > builds/0001/mlt-6.26.1-2.fc35.src.rpm' (attempt #1)
> > > [2022-01-04 23:45:02,026][ ERROR][PID:10] failed to sign rpm:
> > > /var/lib/copr/public_html/results/sergiomb/first_one/srpm-
> > > builds/0001/mlt-6.26.1-2.fc35.src.rpm (in
> > > /usr/lib/python3.10/site-
> > > packages/copr_backend/sign.py:88)
> > > [2022-01-04 23:45:02,028][ INFO][PID:10] Finished build: id=1
> > > failed=True timeout=3600
> > > destdir=/var/lib/copr/public_html/results/sergiomb/first_one
> > > chroot=srpm-builds
> > > [2022-01-04 23:45:02,031][ ERROR][PID:10] Copr GPG signing problems:
> > > Rpm sign failed, affected rpms:
> > > ['/var/lib/copr/public_html/results/sergiomb/first_one/srpm-
> > > builds/0001/mlt-6.26.1-2.fc35.src.rpm']
> >
> > Not easy to tell. Please try to check the logs in the keygen
> > container,
> > and perhaps run the `sign` commands manually.
> >
>
> /bin/sign -u sergiomb#first_...@copr.fedorahosted.org -r
> /var/lib/copr/public_html/results/sergiomb/first_one/srpm-
> builds/0001/mlt-6.26.1-2.fc35.src.rpm --verbose
> gpg: O j: Assertion "sig->version >= 4" in
> mk_notation_policy_etc failed (sign.c:89)
&
Re: my own copr-server
On Wednesday, January 5, 2022 1:03:51 AM CET Sérgio Basto wrote:
> On Tue, 2022-01-04 at 22:58 +, Sérgio Basto wrote:
> > On Tue, 2022-01-04 at 10:35 +0100, Silvie Chlupova wrote:
> > > Hi Sérgio,
> > > I can reproduce your problem by deleting the database in the
> > > copr_database_1 container and then running init-database.sh in the
> > > frontend container. You are missing the relations in copr_database_1.
> > > You can download the database dump here
> > > https://copr.fedorainfracloud.org/db_dumps/. Copy the extracted db
> > > dump
> > > into copr_database_1 and run psql coprdb < your_dump. Or try to
> > > delete
> > > the docker containers and images and then run docker-compose up -d
> > > once
> > > again. After successful completion, the relations in copr_database_1
> > > should be created, and after running init-database.sh, it should show
> > > text that some of the chroots that the script is trying to create
> > > already exist.
> >
> > wget -4
> > https://copr.fedorainfracloud.org/db_dumps/copr_db-2022-01-04_03-36.gz
> >
> > zcat copr_db-2022-01-04_03-36.gz | docker exec -i copr_database_1 psql
> > coprdb (the technique is use exec -i and not exec -it)
> >
> > now I have the all database of copr production but I want a clean
> > Database and configure my builders ( which is only one x86_64 )
> >
> >
> > I can't get rid of SQL: INSERT INTO dist_git_instance (name, clone_url,
> > clone_package_uri, priority, default_namespace) VALUES (%(name)s,
> > %(clone_url)s, %(clone_package_uri)s, %(priority)s,
> > %(default_namespace)s) RETURNING dist_git_instance.id]
> > [parameters: {'name': 'fedora', 'clone_url':
> > 'https://src.fedoraproject.or
> >
> > where this is defined this insert ? or I make it to ignore it ? where
> > is defined the schema of database ?
> >
> >
>
> From the backups give me by Silvie, I could extract the database schema
> , I drop all and just create the database schema with empty tables, I
> ran [2] without errors and things seems ready (after add the repos with
> [3])
> But now build 0001 failed with a sign problem [1] , any tip ?
>
> [1]
> [2022-01-04 23:45:00,757][ INFO][PID:10] Calling '/bin/sign -u
> sergiomb#first_...@copr.fedorahosted.org -p' (attempt #1)
> [2022-01-04 23:45:01,362][ INFO][PID:10] Calling '/bin/sign -u
> sergiomb#first_...@copr.fedorahosted.org -r
> /var/lib/copr/public_html/results/sergiomb/first_one/srpm-
> builds/0001/mlt-6.26.1-2.fc35.src.rpm' (attempt #1)
> [2022-01-04 23:45:02,026][ ERROR][PID:10] failed to sign rpm:
> /var/lib/copr/public_html/results/sergiomb/first_one/srpm-
> builds/0001/mlt-6.26.1-2.fc35.src.rpm (in /usr/lib/python3.10/site-
> packages/copr_backend/sign.py:88)
> [2022-01-04 23:45:02,028][ INFO][PID:10] Finished build: id=1
> failed=True timeout=3600
> destdir=/var/lib/copr/public_html/results/sergiomb/first_one
> chroot=srpm-builds
> [2022-01-04 23:45:02,031][ ERROR][PID:10] Copr GPG signing problems:
> Rpm sign failed, affected rpms:
> ['/var/lib/copr/public_html/results/sergiomb/first_one/srpm-
> builds/0001/mlt-6.26.1-2.fc35.src.rpm']
Not easy to tell. Please try to check the logs in the keygen container,
and perhaps run the `sign` commands manually.
Pavel
>
> [2]
> cd /usr/share/copr/coprs_frontend/ && copr-frontend create-db --alembic
> alembic.ini
> [2022-01-04 23:37:07,318] INFO in log: logging configuration finished
> INFO [alembic.runtime.migration] Context impl PostgresqlImpl.
> INFO [alembic.runtime.migration] Will assume transactional DDL.
> INFO [alembic.runtime.migration] Running stamp_revision ->
> 55d1e8962a93
>
> [3]
> copr-frontend create-chroot $(ls /etc/mock/fedora-*-{i386,x86_64}.cfg
> |xargs -I{} -n1 basename {} .cfg)
> copr-frontend create-chroot $(ls /etc/mock/epel-*-x86_64.cfg |xargs -
> I{} -n1 basename {} .cfg)
>
>
> > Thank you
> >
> >
> >
> > > Silvie
> > >
> > > On 1/4/22 00:03, Sérgio Basto wrote:
> > >
> > > > Hi,
> > > > I started to build my own copr , I follow
> > > > the http://frostyx.cz/posts/copr-docker-compose-without-supervisord
> > > >
> > > > but can't pass the init-database.sh [1], I'm using
> > > > https://pagure.io/copr/copr.git 30 dec 2021 commit (f18faf4f)
> > > >
> > > > any tip ?
> > > >
> > > >
> > > > [1]
> > > > docker exec -it copr_frontend_1 bash
> > > > cd /usr/share/copr/coprs_frontend/ && copr-frontend create-db --
> > > > alembic
> > > > alembic.ini
> > > > [2022-01-03 23:01:38,665] INFO in log: logging configuration
> > > > finished
> > > > /usr/share/copr/coprs_frontend/coprs/models.py:2445: SAWarning:
> > > > relationship 'Build.package' will copy column package.id to column
> > > > build.package_id, whichconflicts with relationship(s):
> > > > 'Package.builds'
> > > > (copies package.id to build.package_id). If this is not the
> > > > intention,
> > > > consider if these relationships should be linked with
> > > > back_populates,
> > > > or if viewonly=True should be applied to one or more if they
Re: my own copr-server
Hi Sérgio,
On Tuesday, January 4, 2022 11:58:32 PM CET Sérgio Basto wrote:
> now I have the all database of copr production but I want a clean
> Database and configure my builders ( which is only one x86_64 )
>
> I can't get rid of SQL: INSERT INTO dist_git_instance (name, clone_url,
> clone_package_uri, priority, default_namespace) VALUES (%(name)s,
> %(clone_url)s, %(clone_package_uri)s, %(priority)s,
> %(default_namespace)s) RETURNING dist_git_instance.id]
> [parameters: {'name': 'fedora', 'clone_url':
> 'https://src.fedoraproject.or
>
> where this is defined this insert ? or I make it to ignore it ? where
> is defined the schema of database ?
it appears we are hitting some SQLAlchemy change, after migrating to
Fedora 35. The new version uncovers a Copr bug. Proposed fix is:
https://pagure.io/fork/praiskup/copr/copr/c/df240a62ad6e7743c608d6b0b732803d78c52b44
Pavel
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: copr.fedorainfracloud.org down?
On Saturday, January 1, 2022 2:41:41 PM CET Miro Hrončok wrote: > It seems that copr.fedorainfracloud.org is down. > I don't recall any planned outages. It happened several times after migration to F35, sorry for complications. I now realized that systemd-oomd does this, but httpd (some api path) clearly has some resource leak (ending up with 15G consumption). We'll monitor that, for now I installed: Restart=on-failure RestartSec=5s Already happened once today, so it brings the service up again. At least we shouldn't face long outages till we find the real issue... Pavel > > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Updated mock-core-configs v36.4 deployed to Fedora Copr
On Tuesday, December 21, 2021 12:29:53 PM CET Pavel Raiskup wrote: > This though also gave us an opportunity to add EPEL 9 configs. Feel free > to experiment with them. Note though Enterprise Linux 9 is not yet > available - so the EPEL 9 chroots are currently built against CentOS > Stream 9 + EPEL 9 (similarly to what is done officially in Koji ATM). I forgot to point out ... Only 'epel-9-x86_64' and 'epel-9-aarch64' is enabled for now. The reason for this is - we can not emulate appropriately new Z/Power architectures on our Fedora 34 builders, QEMU on Fedora 35 is needed (migration to F35 is expected early in 2022) - we don't have Z and Power 9 builders, it is WIP (should be available early in 2022 too) But still, we believe that those two chroots give you some place for experiments/pre-release development, Happy building, Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Updated mock-core-configs v36.4 deployed to Fedora Copr
Hello maintainers, just heads-up (on breakage today, I hope). To bring several config fixes (especially for the broken centos-stream chroots), the mock-core-configs was updated today. This though also gave us an opportunity to add EPEL 9 configs. Feel free to experiment with them. Note though Enterprise Linux 9 is not yet available - so the EPEL 9 chroots are currently built against CentOS Stream 9 + EPEL 9 (similarly to what is done officially in Koji ATM). This update also means that 'epel-8' configs disappeared from the package [1]. To avoid build failures - for now - we provide a compat symlink from 'epel-8' config to 'centos+epel-8' in Copr. This basically means EPEL 8 configs haven't been changed at all, for now. Some time early in 2022 we will try to re-configure EPEL 8 chroots against RHEL 8 (subscribed content) + EPEL 8. That's because CentOS 8 goes EOL, [2]. [1] Mock release notes: https://rpm-software-management.github.io/mock/Release-Notes-2.16 [2] RHEL+EPEL Fedora devel discussion: https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/7T5N6SCPCWHNAUIFPFD54Z6CTLLZMJ6F/ Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: rpkg-util v3 change, moving copr builders to F35
On Friday, December 17, 2021 12:32:37 PM CET Pavel Raiskup wrote: > Hello all, > > just a quick update on this topic. This took a bit more time than I > originally expected, but I was able to test that configuration. > > Please expect that step 2 happens on Monday, 2021-12-20 (I don't want to > break things just when weekend starts). Hello, this is deployed now, once more the link: [1] https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html And feel free to ask on #fedora-buildsys. Pavel > For more info see the previous email, and we should be able to help you > next week with the migration on #fedora-buildsys, when needed. > > Also, the step 3 will be delayed at least by 20 days, so you still have the > 1-month transition period. > > Sorry for inconvenience, > Pavel > > On Friday, November 19, 2021 9:44:51 AM CET Pavel Raiskup wrote: > > we are currently preparing Copr build system for migration to Fedora 35, > > including the builder workers. > > > > There's though, at least from the builder perspective, a major `rpkg-util` > > behavior change [1] (removal of `auto_pack` feature) that many of the Copr > > projects rely on. This is a bit unexpected as `auto_pack = True` has been > > the default in Copr for a long time, and the rpkg-util upstream intentions > > behind the feature were generally misunderstood (even in Copr team). > > > > That being said, some of the currently working builds on F34 would fail > > after the migration to F35. > > > > In order to make the migration a bit less dramatic, we plan to migrate in > > the following steps: > > > > 1. Document the feature drop and possible fixes/workarounds see [1], and > > properly announce the change in advance (here we are _now_). > > > > 2. Change the default, and turn off the `auto_pack` feature for > > relatively short period of time on the current F34 builders > > (ie autopack=False). This will happen soon in December 2021. > > The change will naturally trigger the build failures, but a bit > > earlier so users will be informed sooner ... with a _temporary_ > > work-around in hand => everyone can provide the file > > /rpkg.conf upstream, and opt-in the old behavior with with > > content like: > > > > [rpkg] > > # temporary work-around for rpkg-util v2, auto_pack is going to be > > # removed soon! See: > > # https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 > > auto_pack = True > > > > 3. Migrate to Fedora 35, early in January 2022. This will make the > > `auto_pack = True` work-around non-working, and users will have to > > adapt, again, see [1]. > > > > Of course, anyone is encouraged to migrate to the new syntax **right now**, > > sooner the better. If done correctly, package can be built both with > > rpkg-util > > v2 and v3 [2]. > > > > Sorry for inconvenience! Any comment, idea or help is welcome! > > > > [1] https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 > > [2] > > https://pagure.io/copr/copr-hello/c/739ff9910ee8a9c76d7e97de2f6176106dc19a09?branch=rpkg-util > > > > Pavel > > > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: rpkg-util v3 change, moving copr builders to F35
Hello all, just a quick update on this topic. This took a bit more time than I originally expected, but I was able to test that configuration. Please expect that step 2 happens on Monday, 2021-12-20 (I don't want to break things just when weekend starts). For more info see the previous email, and we should be able to help you next week with the migration on #fedora-buildsys, when needed. Also, the step 3 will be delayed at least by 20 days, so you still have the 1-month transition period. Sorry for inconvenience, Pavel On Friday, November 19, 2021 9:44:51 AM CET Pavel Raiskup wrote: > we are currently preparing Copr build system for migration to Fedora 35, > including the builder workers. > > There's though, at least from the builder perspective, a major `rpkg-util` > behavior change [1] (removal of `auto_pack` feature) that many of the Copr > projects rely on. This is a bit unexpected as `auto_pack = True` has been > the default in Copr for a long time, and the rpkg-util upstream intentions > behind the feature were generally misunderstood (even in Copr team). > > That being said, some of the currently working builds on F34 would fail > after the migration to F35. > > In order to make the migration a bit less dramatic, we plan to migrate in > the following steps: > > 1. Document the feature drop and possible fixes/workarounds see [1], and > properly announce the change in advance (here we are _now_). > > 2. Change the default, and turn off the `auto_pack` feature for > relatively short period of time on the current F34 builders > (ie autopack=False). This will happen soon in December 2021. > The change will naturally trigger the build failures, but a bit > earlier so users will be informed sooner ... with a _temporary_ > work-around in hand => everyone can provide the file > /rpkg.conf upstream, and opt-in the old behavior with with > content like: > > [rpkg] > # temporary work-around for rpkg-util v2, auto_pack is going to be > # removed soon! See: > # https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 > auto_pack = True > > 3. Migrate to Fedora 35, early in January 2022. This will make the > `auto_pack = True` work-around non-working, and users will have to > adapt, again, see [1]. > > Of course, anyone is encouraged to migrate to the new syntax **right now**, > sooner the better. If done correctly, package can be built both with > rpkg-util > v2 and v3 [2]. > > Sorry for inconvenience! Any comment, idea or help is welcome! > > [1] https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 > [2] > https://pagure.io/copr/copr-hello/c/739ff9910ee8a9c76d7e97de2f6176106dc19a09?branch=rpkg-util > > Pavel > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
No more builds for Fedora 33, EOL
Hello maintainers! Fedora 33 has been EOL for two weeks already: https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html So I disabled the Fedora 33 chroots now, which started the standard build removal policy, for more info take a look at docs: https://docs.pagure.org/copr.copr/copr_outdated_chroots_removal_policy.html Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
fedora-eln-ppc64le added
Hello, just a quick update, I was asked why ELN ppc64le isn't available in Copr - the reason probably was that at the time we were adding other fedora-eln chroots we didn't have ppc64le builders in hands... And when we re-enabled ppc64le builders, we forgot about adding ELN chroot. So I created that chroot a few minutes back. Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Mock/Copr default epel-8-* configuration to be changed
Hello Fedora EPEL maintainers! First I don't feel comfortable announcing this, I'm not happy about the situation and so I don't want to be the lightning rod :-). But I believe that we can come to acceptable Copr/Mock solution and this needs to be discussed... so here we are. By the end of the year 2021 we have to fix our default EPEL 8 Mock configuration (mock-core-configs.rpm, /etc/mock/epel-8-*.cfg) as CentOS 8 goes EOL by then. The same thing needs to happen in Fedora Copr, with the epel-8-* chroots (side note, in Fedora Copr we use the mock-core-configs package for builds without any deployment specific modifications). I am proposing (as PR against mock upstream ATM [1]) to switch the default epel-* configuration from CentOS+EPEL to RHEL+EPEL as soon as possible (see the pull request [1]). This would bring some consequences, namely newly with epel-8* chroots, - builds will require a valid Red Hat subscription (the no-cost variant is OK as well, though [2]) - we will miss some build-time packages that Red Hat is not shipping, at least at the beginning till they are added (to RHEL CRB, or other currently unknown place). - cross-arch compilation can not be used, Red Hat subscriptions don't allow that (using QEMU and rpm --forcearch), [3] The positive thing is that the default configuration will be much closer to the official EPEL builds (because Fedora Koji EPEL builds are actually done also against RHEL). For the Fedora Copr builders, we already have the necessary Red Hat subscriptions in hand (will be deployed by the end of the year). So we will only loose the opportunity to build on emulated epel-8-armhfp permanently, and epel-8-s390x temporarily (as we already work on the native s390x support). Any thoughts? Feedback is needed here. [1] https://github.com/rpm-software-management/mock/pull/802 [2] https://rpm-software-management.github.io/mock/Feature-rhelchroots [3] https://bugzilla.redhat.com/show_bug.cgi?id=1912847 Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
rpkg-util v3 change, moving copr builders to F35
Hello, we are currently preparing Copr build system for migration to Fedora 35, including the builder workers. There's though, at least from the builder perspective, a major `rpkg-util` behavior change [1] (removal of `auto_pack` feature) that many of the Copr projects rely on. This is a bit unexpected as `auto_pack = True` has been the default in Copr for a long time, and the rpkg-util upstream intentions behind the feature were generally misunderstood (even in Copr team). That being said, some of the currently working builds on F34 would fail after the migration to F35. In order to make the migration a bit less dramatic, we plan to migrate in the following steps: 1. Document the feature drop and possible fixes/workarounds see [1], and properly announce the change in advance (here we are _now_). 2. Change the default, and turn off the `auto_pack` feature for relatively short period of time on the current F34 builders (ie autopack=False). This will happen soon in December 2021. The change will naturally trigger the build failures, but a bit earlier so users will be informed sooner ... with a _temporary_ work-around in hand => everyone can provide the file /rpkg.conf upstream, and opt-in the old behavior with with content like: [rpkg] # temporary work-around for rpkg-util v2, auto_pack is going to be # removed soon! See: # https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 auto_pack = True 3. Migrate to Fedora 35, early in January 2022. This will make the `auto_pack = True` work-around non-working, and users will have to adapt, again, see [1]. Of course, anyone is encouraged to migrate to the new syntax **right now**, sooner the better. If done correctly, package can be built both with rpkg-util v2 and v3 [2]. Sorry for inconvenience! Any comment, idea or help is welcome! [1] https://docs.pagure.org/copr.copr/rpkg_util_2_vs_3.html#rpkg-util-v3 [2] https://pagure.io/copr/copr-hello/c/739ff9910ee8a9c76d7e97de2f6176106dc19a09?branch=rpkg-util Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Build Monitor "Minimal" view?
On Thursday, October 21, 2021 6:14:08 PM CEST John Boero wrote: > Hi I've been a huge fan of COPR for years now but as projects and platforms > grow I always wished there were a "Minimal" view along with "Simple" and > "Detailed" where Minimal just shows the red/green/gray icon. Is there any > way we can get this third option added for simplicity? Thank you for the suggestion. I was too thinking about this before, as some of my projects have too large tables. The only caveat is that the text in the table headers would have to be oriented vertically, I think. Can you fill an issue please, so we keep this tracked? https://pagure.io/copr/copr/issues Thanks, Pavel > Thanks > JohnnyB > > [image: screenshot2.png] > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Bad exit status from %prep during chmod -Rf a+rX,u+w,g-w,o-w .
Hm, the options don't look invalid, so two-problems IMO: - chmod looks to be buggy (when the process has the permissions to extract the tarball, fixing permissions shouldn't be problem as on Linux unprivileged user can not give the files away). - rpmbuild should print-out the stderr output from chmod process Pavel On Monday, October 4, 2021 11:57:50 AM CEST Miro Hrončok wrote: > On 04. 10. 21 11:49, Miro Hrončok wrote: > > Hello, > > > > I see this failure in dnf: > > > > https://copr.fedorainfracloud.org/coprs/churchyard/patch251/build/2872812/ > > > > Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.x8REO2 > > + umask 022 > > + cd /builddir/build/BUILD > > + cd /builddir/build/BUILD > > + rm -rf dnf-4.9.0 > > + /usr/bin/gzip -dc /builddir/build/SOURCES/dnf-4.9.0.tar.gz > > + /usr/bin/tar -xof - > > + STATUS=0 > > + '[' 0 -ne 0 ']' > > + cd dnf-4.9.0 > > + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . > > error: Bad exit status from /var/tmp/rpm-tmp.x8REO2 (%prep) > > Bad exit status from /var/tmp/rpm-tmp.x8REO2 (%prep) > > > > I am perplexed with the error. > > Could it be some problem with Copr builders? > > Unlikely, I've reproduced this in Koji: > > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/GO3LFGR3IDOUVFRZYD4LY2D6LV252I2S/ > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > copr-devel mailing list -- copr-devel@lists.fedorahosted.org > To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: khm/plan9port: new build request
Hello Fabian, On Monday, September 27, 2021 3:36:18 PM CEST Fabian wrote: > On Monday, September 27th, 2021 at 7:22 PM, Fabian > wrote: > > > It's been a while since the last build, consider pushing a new > > build to recent version. > > > > Thanks! > > It turns out that shomehow khm/plan9port don't have plan9port, > dnf says no package fonund. The 'copr-devel' list is generic communication channel for the Copr platform, not particular Copr projects. If you want to contact the project maintainer, please take a look at the 'plan9port' project owner's page: https://copr.fedorainfracloud.org/coprs/khm/ Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Outage: Upgrade of Copr servers - 2021-08-26 7:30 UTC
And the outage is over! Link to release notes is here: https://docs.pagure.org/copr.copr/release-notes/2021-08-26.html Happy building! Pavel On Monday, August 23, 2021 10:53:49 PM CEST Pavel Raiskup wrote: > There will be an outage starting at: > > $ date --date '2021-08-26 7:30 UTC' > > The outage will last approximately 2 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 and bugfixes. > > Affected Services: > copr-frontend - https://copr.fedorainfracloud.org > copr-backend - https://copr-be.cloud.fedoraproject.org/ > > Contact persons: > @praiskup / @frostyx > > Ticket: > https://pagure.io/fedora-infrastructure/issue/10179 > > In case of any questions, please join the #fedora-buildsys channel > on libera.chat or add comments to the ticket above. > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Outage: Upgrade of Copr servers - 2021-08-26 7:30 UTC
There will be an outage starting at: $ date --date '2021-08-26 7:30 UTC' The outage will last approximately 2 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 and bugfixes. Affected Services: copr-frontend - https://copr.fedorainfracloud.org copr-backend - https://copr-be.cloud.fedoraproject.org/ Contact persons: @praiskup / @frostyx Ticket: https://pagure.io/fedora-infrastructure/issue/10179 In case of any questions, please join the #fedora-buildsys channel on libera.chat or add comments to the ticket above. ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
mock-core-configs-35-1 released
Hello, I've just released the new mock-core-configs package: https://github.com/rpm-software-management/mock/releases/tag/mock-core-configs-35-1 Updates are in Bodhi. The new package ships Fedora 35 configuration; and since we seem to already have the composes available - I deployed the new configs to Fedora Copr and enabled the Fedora 35 chroots (prepared by Jakub Kadlčík). This update should also fix the recent Fedora Rawhide build failures, sorry for the delay. Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Oracle Linux chroots (temporarily) available in Fedora Copr
Hello, just a quick note - we enabled Oracle Linux chroots in Fedora Copr today, this is temporarily needed by OAMG/LEAPP team for their CI/CD system. Feel free to test those chroots, but please don't heavily depend on them as we don't know when we'll again drop them (preferably use epel/centos-stream chroots instead, they should provide similar build results). Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: CentOS Sream 9 pre-release chroots added to Fedora Copr
On Friday, July 23, 2021 5:09:57 PM CEST Daniel P. Berrangé wrote: > On Fri, Jul 23, 2021 at 03:25:15PM +0100, Daniel P. Berrangé wrote: > > On Fri, Jul 23, 2021 at 04:03:06PM +0200, Pavel Raiskup wrote: > > > The ppc64le doesn't seem to build on Power8 hardware we have [2], and > > > s390x has some troubles with qemu emulation [3]. So those architectures > > > are at least for now disabled. > > > > > > > [3] Fatal glibc error: CPU lacks VXE support (z14 or later required), > > > > > > https://download.copr-dev.fedorainfracloud.org/results/praiskup/ping/centos-stream-9-s390x/02135293-dummy-pkg/builder-live.log.gz > > > > I'm trying to find out from the s390x QEMU maintainers about the > > likely fix requird to make this work. > > It will be fixed in QEMU 6.1.0 which is coming out in a month-ish: > > https://wiki.qemu.org/Planning/6.1 > > and will be addressed by this patch series > > https://lore.kernel.org/qemu-devel/20210517142739.38597-1-da...@redhat.com/ > > This futur QEMU release will go into f35 rawhide, and virt-preview repo > can be used if you will need it for f34 Nice, thank you for the reference! I'm curious... couldn't we run CentOS Stream 9 ppc64le builds through qemu emulation as well? Pavel > Regards, > Daniel > -- > |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| > |: https://libvirt.org -o-https://fstop138.berrange.com :| > |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :| > ___ > devel mailing list -- de...@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
CentOS Sream 9 pre-release chroots added to Fedora Copr
Hi all, just for the info, we enabled the `centos-stream-9-x86_64` and `centos-stream-9-aarch64` chroots in Fedora Copr. Note that we build directly from composes [1] without mirrors (some failures can expected), and that the packages are not GPG-signed. You have been warned :-) The ppc64le doesn't seem to build on Power8 hardware we have [2], and s390x has some troubles with qemu emulation [3]. So those architectures are at least for now disabled. [1] https://github.com/rpm-software-management/mock/pull/751 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1985364 [3] Fatal glibc error: CPU lacks VXE support (z14 or later required), https://download.copr-dev.fedorainfracloud.org/results/praiskup/ping/centos-stream-9-s390x/02135293-dummy-pkg/builder-live.log.gz Happy building! Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Can't login to copr
On Thursday, July 22, 2021 10:05:59 PM CEST harbottle wrote: > I get redirected to Fedora accounts (id.fedoraproject.org), enter my username > (harbottle) and password and click "Log in", thennothing. I can login > directly to my Fedora account at > [accounts.fedoraproject.org](https://accounts.fedoraproject.org/) just fine. I > have tried changing my password. Please help! Thank you for the question. Can you please try to cleanup all cookies for copr.fedorainfracloud.org and for id.fedoraproject.org and re-try? An alternative is to configure negotiate in your browser, and take a kerberos token with the 'fkinit' tool. There's one issue we track [1] though that one is related to a mail+pass attempt, not a nick+pass attempt. If the cleanup above doesn't help, please try to report a new issue against the Fedora Infrastructure team [2]. In case you can not even log-in into the pagure.io tracker, I am OK to fill the issue on your behalf ... just please provide the detailed report to me first off-list. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1943925 [2] https://pagure.io/fedora-infrastructure/issues Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Architecture "ppc64le" again in Fedora Copr
Hi all, I'm glad I can announce that we have again (native) support for ppc64le builds in Fedora Copr. Currently we have two Power8 boxes (in RDU): https://pagure.io/fedora-infrastructure/issue/9059 The ppc64le chroots were re-enabled, feel free to use them. I noticed several build failures caused by missing repodata in ppc64le chroots, please re-generate the repodata manually if you happen to see those problems. Happy building! Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Excluding older builds of packages from Fedora when testing new ones in Copr
On Friday, July 9, 2021 11:36:09 AM CEST Miro Hrončok wrote:
> On 09. 07. 21 11:30, Pavel Raiskup wrote:
> > On Friday, July 9, 2021 10:19:57 AM CEST Miro Hrončok wrote:
> >> On 09. 07. 21 9:46, Pavel Raiskup wrote:
> >>> This is pre-production experiment, right? Couldn't you just specify
> >>> "Provides: python3dist(click) = 7.9"?
> >>
> >> It is, but it would not help me. By manually providing this, I would:
> >>
> >>- confuse %pyproject_buildrequires generator -- Python would think
> >> 'click <
> >> 8' is not satisfied, by RPM/dnf would insist it is.
> >>- still not get a root.log resolution failure I want
> >>- still not "satisfy" packages that BR "python3click" instead of
> >> "python3dist(click)"
> >>
> >> I wonder if adding Obsoletes: python3-click < %{version} helps, but I don't
> >> think so.
> >>
> >>> We have an RFEhttps://pagure.io/copr/copr/issue/1336 that could help you
> >>> if you
> >>> could specify dnf.conf excludepkgs= option for the rawhide repo. But
> >>> this is
> >>> not an easy one.
> >>
> >> Yes, this would work.
> >
> > Another idea...
> > What if you had a syntetic package, say "click-blocker", with 'Conflicts:
> > python3-click < XYZ'? That package could be added as always-installed
> > package
> > into "Packages" field (chroot Edit form).
> >
> > Or maybe it could simply require 'python3-click >= XYZ', too?
>
> Is "Packages" always-installed or initially-installed? What prevents dnf to
> downgrade it?
>
> I'll test this approach thou, seems reasonable.
You are right, it is always "initially installed".. It is definitely
interesting topic, please share the results of the experiment :-)
If DNF really removes the artificial package because it depends on a _newer_
click package (than the following transaction requires) -- we could probably
consider an upstream report..
Pavel
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Excluding older builds of packages from Fedora when testing new ones in Copr
On Friday, July 9, 2021 10:19:57 AM CEST Miro Hrončok wrote:
> On 09. 07. 21 9:46, Pavel Raiskup wrote:
> > This is pre-production experiment, right? Couldn't you just specify
> > "Provides: python3dist(click) = 7.9"?
>
> It is, but it would not help me. By manually providing this, I would:
>
> - confuse %pyproject_buildrequires generator -- Python would think 'click <
> 8' is not satisfied, by RPM/dnf would insist it is.
> - still not get a root.log resolution failure I want
> - still not "satisfy" packages that BR "python3click" instead of
> "python3dist(click)"
>
> I wonder if adding Obsoletes: python3-click < %{version} helps, but I don't
> think so.
>
> > We have an RFEhttps://pagure.io/copr/copr/issue/1336 that could help you
> > if you
> > could specify dnf.conf excludepkgs= option for the rawhide repo. But this
> > is
> > not an easy one.
>
> Yes, this would work.
Another idea...
What if you had a syntetic package, say "click-blocker", with 'Conflicts:
python3-click < XYZ'? That package could be added as always-installed package
into "Packages" field (chroot Edit form).
Or maybe it could simply require 'python3-click >= XYZ', too?
Pavel
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Excluding older builds of packages from Fedora when testing new ones in Copr
On Thursday, July 8, 2021 3:47:56 PM CEST Miro Hrončok wrote:
> Hello Copr users and developers.
>
>
> When we update packages in Fedora, we regularly use Copr to test the impact
> of
> the upgrade.
>
> For me, the procedure usually goes like this:
>
> 1) create a new copr with Fedora rawhide x86_64 chroot (and added Koji repo)
>
> $ copr create $COPR
> --repo='http://kojipkgs.fedoraproject.org/repos/rawhide/latest/$basearch/'
> --chroot fedora-rawhide-x86_64 --delete-after-days 30
>
>
> 2) define and build the updated package in the copr
>
> $ copr add-package-distgit $COPR --name $PKG --webhook-rebuild on
> --commit
> $BRANCH --namespace forks/$(whoami)
> $ copr build-package $COPR --name $PKG
>
>
> 3) get the list of dependent packages
>
> $ repoquery -q --repo=rawhide{,-source} [--whatrequires $spkg for each
> subpackage] --recursive | grep src$ | pkgname
>
>
> 4) define and build the depended packages in the copr
>
> $ parallel copr add-package-distgit $COPR --webhook-rebuild on --commit
> rawhide --name -- $(repoquery from above ...)
> $ parallel copr build-package $COPR --nowait --background --name --
> $(repoquery from above ...)
>
>
> 5) analyze build failures, do a "control" rebuild in another copr if needed
>
>
>
> However, this procedure has a flaw. Let's say I'm working on upgrading
> python-click from 7.x to 8.x. And let's say a package (even transitively)
> BuildRequires:
>
> python3dist(click) < 8
>
> The way that dnf dependency resolution works, that package will be built with
> Rawhide's python3-click 7.x and it will be marked as successful. However, I'd
> like to see a failure here to be notified that such package cannot be build
> and
> will be negatively impacted by the update.
>
>
> Is there a way to solve this?
I thought that 'best=1' is about to help here, but since we use that config
in mock-core-configs it is not.
> I have couple ideas, but none of them is fully
> working:
>
> A) Compose my own repo with the updated package and Rawhide content without
> it,
> use that repo in the copr.
>
> Pros:
>
> - this is similar to what will happen in Koji once the package is updated
>
> Cons:
>
> - this requires tooling that I don't think exists
> - this requires a place to put that repo to
> - the repo creation could take a lot of time and would need to be repeated
> on-demand each time rawhide changes
> - Copr's Fedora chroots always include Fedora repos (maybe I can use
> custom-1-x86_64 chroot?)
>
> B) Create a Fedora side tag, explicitly block the package from it, use that
> side tag's Koji repo.
>
> Pros:
>
> - same as (A)
>
> Cons:
>
> - I don't think on-demand side tags allow users to block packages
> - Copr's Fedora chroots always include Fedora repos (same as (A))
> - this wastes Koji's resources a bit
> - requires waiting for the initial Koji regen-repo
>
>
> C) Block (exclude) python3-click < 8 from the chroot.
>
> Pros:
>
> - no custom repos required
> - no resources overhead
> - no time overhead
>
> Cons:
>
> - There is no way exclude packages in chroot settings. Mock settings
> possibly
> allow me to do this in config_opts['dnf.conf'].
> - The exclude could obfuscate root.log resolution problems logs.
> - Packager needs to figure out what exactly to exclude (possibly need to
> exclude all subpackage's NEVRAs from rawhide compose (and Koji buildroot if
> they differ))
>
>
> Is there another way? If not, I think (C) is easiest to actually implement,
> if
> the chroot settings page in copr gains an "excludes" option.
This is pre-production experiment, right? Couldn't you just specify
"Provides: python3dist(click) = 7.9"?
We have an RFE https://pagure.io/copr/copr/issue/1336 that could help you if you
could specify dnf.conf excludepkgs= option for the rawhide repo. But this is
not an easy one.
Pavel
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Unused PR directories removed Re: Outage: Upgrade of Copr servers - 2021-06-16 6:00 UTC
The unused CoprDirs are now removed. Per release note: > Pull request CoprDirs are automatically deleted after inactivity > > > Copr supports webhooks and automatically builds packages from PRs within > an upstream project. Such builds were kept indefinitely, and the user > interface could get cluttered. We now automatically delete all PR-related > content after 40 days of inactivity in that pull request. This should not > be a problem for long-term unfinished PRs because once the work is > resumed, everything will be rebuilt in Copr again. > > This feature is now paused, and we’ll re-enable it by the end of June. In > the meantime, please update your pull-requests to prolong your existing > builds (the red-labeled build-filtering buttons denote builds that would > be otherwise already removed). Pavel On Wednesday, June 16, 2021 9:28:37 AM CEST Pavel Raiskup wrote: > And the outage is over! > > Release notes for the release are here: > https://docs.pagure.org/copr.copr/release-notes/2021-06-16.html > > Happy building! > Copr Team > > On Tuesday, June 15, 2021 8:44:28 AM CEST Pavel Raiskup wrote: > > There will be an outage starting at: > > > > $ date --date '2021-06-16 6:00 UTC' > > > > The outage will last approximately 2 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 and bugfixes. > > > > Affected Services: > > copr-frontend - https://copr.fedorainfracloud.org > > copr-backend - https://copr-be.cloud.fedoraproject.org/ > > > > Contact persons: > > @praiskup / @frostyx > > > > Ticket: > > https://pagure.io/fedora-infrastructure/issue/10034 > > > > In case of any questions, please join the #fedora-buildsys channel > > on libera.chat or add comments to the ticket above. > > > > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Legal flag raised on discord
On Friday, June 25, 2021 3:09:39 AM CEST r...@copr-fe.aws.fedoraproject.org wrote: > Discord is proprietary, it shouldn't be in copr. > Navigate to https://copr.fedorainfracloud.org/admin/legal-flag/ Dear owner, I have to remove the proprietary software. Please see: https://docs.pagure.org/copr.copr/user_documentation.html#what-i-can-build-in-copr Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Repeated builds of misconfigured test package
Thank you for the report! On Monday, June 21, 2021 10:25:10 AM CEST Iñaki Ucar wrote: > There's a repo [1] (owner in CC) that, during the last 2 days, is > sending hundreds of builds of the same misconfigured package, taking > resources and then failing with a timeout. Not sure what is triggering > so many builds, but more builds certainly won't improve the situation. > :) > > [1] https://copr.fedorainfracloud.org/coprs/ndthanh7/test/ This looks like some attempt for crypto mining. Dear submitter, Fedora Copr build system is not supposed to be used for mining. Copr is for wide packager audience, and such behavior eats the quota and hurts the whole Copr user base. I've removed the builds, and removed the project. And we will give you permanent BAN in case of any other similar attempt. Also note that Copr Build system is by design a public service - we don't obfuscate build logs. So any credentials, or similar stuff you could need for authentication when mining would be visible to general public - there's a chance anyone could use those credentials to deplete accounts, etc. Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Outage: Upgrade of Copr servers - 2021-06-16 6:00 UTC
And the outage is over! Release notes for the release are here: https://docs.pagure.org/copr.copr/release-notes/2021-06-16.html Happy building! Copr Team On Tuesday, June 15, 2021 8:44:28 AM CEST Pavel Raiskup wrote: > There will be an outage starting at: > > $ date --date '2021-06-16 6:00 UTC' > > The outage will last approximately 2 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 and bugfixes. > > Affected Services: > copr-frontend - https://copr.fedorainfracloud.org > copr-backend - https://copr-be.cloud.fedoraproject.org/ > > Contact persons: > @praiskup / @frostyx > > Ticket: > https://pagure.io/fedora-infrastructure/issue/10034 > > In case of any questions, please join the #fedora-buildsys channel > on libera.chat or add comments to the ticket above. > ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Outage: Upgrade of Copr servers - 2021-06-16 6:00 UTC
There will be an outage starting at: $ date --date '2021-06-16 6:00 UTC' The outage will last approximately 2 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 and bugfixes. Affected Services: copr-frontend - https://copr.fedorainfracloud.org copr-backend - https://copr-be.cloud.fedoraproject.org/ Contact persons: @praiskup / @frostyx Ticket: https://pagure.io/fedora-infrastructure/issue/10034 In case of any questions, please join the #fedora-buildsys channel on libera.chat or add comments to the ticket above. ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Disabling Fedora 32 chroots in Copr
Hello, I have just disabled Fedora 32 chroots in Copr. According to the Fedora wiki [1], Fedora 32 reached the end of its life on 2021-05-25 (buils for i386 already failed anyway). This effectively means that from this moment, it is no longer possible to submit builds for the following chroots: - fedora-32-x86_64 - fedora-32-i386 - fedora-32-s390x - fedora-32-aarch64 - fedora-32-armhfp The existing build results for F32 chroots will be automatically removed after 180 days, but feel free to individually prolong your Copr chroots. [1] https://fedoraproject.org/wiki/End_of_life Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Disabling the "postgresql" module before building
On Thursday, June 3, 2021 10:22:55 PM CEST Daniel Farina wrote: > I am trying to build some extensions to Postgres on COPR. One of the things > that has made life more complex after EL8 or so is the "module" system. It is > obligatory to disable the "postgresql" module to be able to install PGDG > packages, e.g. > https://people.planetpostgresql.org/devrim/index.php?/archives/100-Installing-PostgreSQL-on-RHEL-8.html > > I will need to do something similar to build a package with dependencies on > postgresql13-devel, and so on. > > Unfortunately, I don't see a good way to affect the build chroot in COPR in > this way, to disable the included-with-EL8 postgresql module, making adding > the Postgres YUM repo (aka "pgdg repo") not useful. > > Is there a solution for this? You can disable particular MODULE:STREAM in the UI: log-in => project => Settings => (near particular chroot) Edit button => Modules: field => specify `!MODULE:STREAM`. To add a repository, you can use the "Repos:" field on the very same page. Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: What's the best way to compile Fedora's kernel rpms on copr?
On Thursday, June 3, 2021 7:49:22 PM CEST Daniel Farina wrote: > How about the simplest? Is it not possible to build directly from the > src.fedoraproject.org repositories, without modification? $ copr build-distgit --name foo Note that this method clones package "foo" from the Fedora DistGit 'main' branch - and Copr then creates a source RPM from that and builds it in all chroots. So if each of the chroots requires a separate branch, more builds need to be submitted (see the --commit option). Some info in the announcement: https://docs.pagure.org/copr.copr/release-notes/2020-11-13.html#simplified-builds-from-distgit Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
OpenSUSE Leap 15.3 added
Hi, just a quick update about $Subject, and warning that version Leap 15.1 was now marked as EOL (build results will be removed after ~6 months if not prolonged). Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Copr builders upgraded to Fedora 34
Hello, I'm glad I can announce that Fedora Copr builders are now on Fedora 34. There are no known problems at this moment, as all our integration testing passed. At the same time we finally deployed a new set of x86_64 hyperviors in Fedora lab, where we start about 60 builders at this moment (and the quota should increase by another 60 VMs during the next week or two). The lab we host the new VMs in doesn't have enough public IPv4 addresses so we control builds there over IPv6 (and builds are done over NATed ipv4). This is a new setup and bugs are not unexpected; so please report them as always: https://pagure.io/copr/copr/issues Happy building! Pavel ___ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
