[EPEL-devel] Re: Requesting branches for epel9
On Mon, Dec 13, 2021 at 09:40:19AM -0500, Stephen John Smoogen wrote: > It is a fairly manual process where a person volunteers to sit in > front of the firehose every day and deal with these requests. The > person who has to process them has a checklist of policy items they > have to confirm/check to make sure the branch is possible. Where is that checklist? I found https://docs.pagure.org/releng/sop_process_dist_git_requests.html, but it refers to a tool which is deprecated in favor of another one, at https://pagure.io/fedscm-admin/, but none of those places have a clear articulation of the policy items. I get human sanity check of new package requests is good, although really ideally I would hope that wouldn't fall to the rel-eng/scm firehose volunteers. But it seems like "request an EPEL branch" should generally be either "Okay! Doing that automatically now" or "Oh, this is in EL, sorry"*. What are the other cases? * I'm very sad that this isn't "So, would you like to do it anyway, and then make a module?", but c'est la vie -- Matthew Miller Fedora Project Leader ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Builds for EPEL9
On Sat, Dec 11, 2021 at 08:58:15PM +1100, Frank Crawford wrote: > Folks, > > I'm looking at building a package that currently exists in EPEL8 for > EPEL9. I have a new branch epel9 branch for my package, but when I try > to do a mock build or scratch build it fails with the error: > > Error: Error downloading packages: > Status code: 404 for > https://infrastructure.fedoraproject.org/repo/centos/centos-9-stream/x86_64/toplink/packages/basesystem/11/13.el9/noarch/basesystem-11-13.el9.noarch.rpm > (IP: 38.145.60.16) > > Am I doing anything wrong here, is it just that we can't currently > build for EPEL9? builds were broken for a short time. We started syncing the centos-9-stream 'release' repos, and it accidentally deleted the existing centos-9-stream buildroot repos we have been building against. I resynced the buildroot repos and made sure it wasn't going to delete them, so it should be all back to working. If you have the non working repodata cached, you make need to do a mock --clean or the like. We still need to adjust koji to use the 'release' repos for epel9. kevin signature.asc Description: PGP signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Builds for EPEL9
On Mon, 2021-12-13 at 22:30 +1100, Frank Crawford wrote: > On Mon, 2021-12-13 at 06:18 -0500, Neal Gompa wrote: > > On Mon, Dec 13, 2021 at 6:13 AM Troy Dawson > > wrote: > > > > > > > > > > > > On Sat, Dec 11, 2021 at 1:58 AM Frank Crawford > > > wrote: > > > > > > > > Folks, > > > > > > > > I'm looking at building a package that currently exists in EPEL8 > > > > for > > > > EPEL9. I have a new branch epel9 branch for my package, but when > > > > I try > > > > to do a mock build or scratch build it fails with the error: > > > > > > > > Error: Error downloading packages: > > > > Status code: 404 for > > > > https://infrastructure.fedoraproject.org/repo/centos/centos-9- > > > > stream/x86_64/toplink/packages/basesystem/11/13.el9/noarch/basesy > > > > stem-11-13.el9.noarch.rpm > > > > (IP: 38.145.60.16) > > > > > > > > Am I doing anything wrong here, is it just that we can't > > > > currently > > > > build for EPEL9? > > > > > > > > > You certainly can build for epel9. > > > But you haven't said what command(s) you are doing that gives that > > > output. > > > Let us know what you are doing, and that will make it possible for > > > us to help. > > > > > > > I have the same problem using fedpkg-1.41-2.fc35. > > > > Using "fedpkg --release epel9 mockbuild" fails with that error > > consistently. I tried to test builds of a couple of packages locally > > before doing branch requests and I couldn't. > > Yeah sorry about that, I tried two different things, in the EPEL9 > branch of my code: > > fedpkg mockbuild with --verbose output fedpkg -v mockbuild (...) Mock config /etc/mock/epel-9-x86_64.cfg was not found. Going to request koji to create new one. New mock config directory: /tmp/epel-9-x86_64.lwxt33udmockconfig (...) and basesystem is installed , have you any /etc/mock/epel-9-x86_64.cfg ? > and also > > fedpkg scratch-build > > Both cases came out with pretty much the same error, i.e. couldn't get > basesystem. > > Regards > Frank > ___ > epel-devel mailing list -- epel-devel@lists.fedoraproject.org > To unsubscribe send an email to > epel-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/epel-devel@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure -- Sérgio M. B. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Requesting branches for epel9
On Mon, 13 Dec 2021 at 09:25, Miroslav Suchý wrote: > > Hi. > > I have two questions regarding epel9: > > 1) I have requested dozen of epe9 branches for my packages. It was 20+ hours > ago. E.g. > https://pagure.io/releng/fedora-scm-requests/issue/39402 > Is it manual process? Or is the automation broken? > It is a fairly manual process where a person volunteers to sit in front of the firehose every day and deal with these requests. The person who has to process them has a checklist of policy items they have to confirm/check to make sure the branch is possible. > 2) It was quite pain to go through all my packages and find which ones > actually have EPEL version. And which ones are in > RHEL9 now. I would actually appreciate if there were mass package request. > Closing such BZ as WONTFIX is a) rare b) much > easier than come up with the list. Does someone plan to do such mass report > for EPEL9? Or should I do that? Or is it bad > idea? > No idea on this one. -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Requesting branches for epel9
On 13. 12. 21 15:25, Miroslav Suchý wrote: Hi. I have two questions regarding epel9: 1) I have requested dozen of epe9 branches for my packages. It was 20+ hours ago. E.g. https://pagure.io/releng/fedora-scm-requests/issue/39402 Is it manual process? Or is the automation broken? The tickets are processed by automated scripts that are run manually by a couple of heroes. This quite unfortunately combines disadvantages of both automated and manual approach: - it takes a long time for requests to be processed - nobody needs to check the requests for sanity A FESCo ticket that touches this topic is https://pagure.io/fesco/issue/2115 2) It was quite pain to go through all my packages and find which ones actually have EPEL version. And which ones are in RHEL9 now... Note that fedpkg request-branch epel9 *should* fail if the component is already present in CentOS Stream 9: [python3.9 (rawhide)]$ fedpkg request-branch epel9 Could not execute request_branch: This package is already an EL package, therefore it cannot be in EPEL. If this is a mistake or you have an exception, please contact the Release Engineering team. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Requesting branches for epel9
Hi. I have two questions regarding epel9: 1) I have requested dozen of epe9 branches for my packages. It was 20+ hours ago. E.g. https://pagure.io/releng/fedora-scm-requests/issue/39402 Is it manual process? Or is the automation broken? 2) It was quite pain to go through all my packages and find which ones actually have EPEL version. And which ones are in RHEL9 now. I would actually appreciate if there were mass package request. Closing such BZ as WONTFIX is a) rare b) much easier than come up with the list. Does someone plan to do such mass report for EPEL9? Or should I do that? Or is it bad idea? Miroslav ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] EPEL 9 vs EPEL 9 Next buildroot
Hello. Considering that EPEL 9 Next repo is an **additional** repo to EPEL 9 (is that still the case?), should EPEL 9 overrides be visible for EPEL 9 Next builds? They are currently not. Also, consider 2 different builds of package foo: - foo-1.0-1.el9.next in stable EPEL 9 Next - foo-1.0-2.el9 in stable EPEL 9 EPEL 9 Next users will get foo-1.0-2.el9 because it is > foo-1.0-1.el9.next. However, is this also true for the EPEL 9 Next buildroot? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Builds for EPEL9
On Mon, 13 Dec 2021 at 06:21, Neal Gompa wrote: > > On Mon, Dec 13, 2021 at 6:13 AM Troy Dawson wrote: > > > > > > > > On Sat, Dec 11, 2021 at 1:58 AM Frank Crawford > > wrote: > >> > >> Folks, > >> > >> I'm looking at building a package that currently exists in EPEL8 for > >> EPEL9. I have a new branch epel9 branch for my package, but when I try > >> to do a mock build or scratch build it fails with the error: > >> > >> Error: Error downloading packages: > >> Status code: 404 for > >> https://infrastructure.fedoraproject.org/repo/centos/centos-9-stream/x86_64/toplink/packages/basesystem/11/13.el9/noarch/basesystem-11-13.el9.noarch.rpm > >> (IP: 38.145.60.16) > >> > >> Am I doing anything wrong here, is it just that we can't currently > >> build for EPEL9? > > > > > > You certainly can build for epel9. > > But you haven't said what command(s) you are doing that gives that output. > > Let us know what you are doing, and that will make it possible for us to > > help. > > > > I have the same problem using fedpkg-1.41-2.fc35. > > Using "fedpkg --release epel9 mockbuild" fails with that error > consistently. I tried to test builds of a couple of packages locally > before doing branch requests and I couldn't. The file is there ``` $ ls -lZ /mnt/fedora/app/fi-repo/centos/centos-9-stream/x86_64/toplink/packages/basesystem/11/13.el9/noarch/ total 8 -rw-r--r--. 1 root root system_u:object_r:nfs_t:s0 7065 2021-12-11 22:24 basesystem-11-13.el9.noarch.rpm ``` I see 404's internal and external on Dec 11 but on Dec 13 it looks like it is working with 200's. ``` - - [11/Dec/2021:21:58:23 +] "GET /repo/centos/centos-9-stream/x86_64/toplink/packages/basesystem/11/13.el9/noarch/basesystem-11-13.el9.noarch.rpm HTTP/1.1" 404 196 "-" "libdnf (Fedora Linux 35; generic; Linux.x86_64)" - - [13/Dec/2021:11:21:10 +] "GET /repo/centos/centos-9-stream/x86_64/toplink/packages/basesystem/11/13.el9/noarch/basesystem-11-13.el9.noarch.rpm HTTP/1.1" 200 7065 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.74 Safari/537.36 Edg/79.0.309.43" ``` -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Builds for EPEL9
On Mon, 2021-12-13 at 06:18 -0500, Neal Gompa wrote: > On Mon, Dec 13, 2021 at 6:13 AM Troy Dawson > wrote: > > > > > > > > On Sat, Dec 11, 2021 at 1:58 AM Frank Crawford > > wrote: > > > > > > Folks, > > > > > > I'm looking at building a package that currently exists in EPEL8 > > > for > > > EPEL9. I have a new branch epel9 branch for my package, but when > > > I try > > > to do a mock build or scratch build it fails with the error: > > > > > > Error: Error downloading packages: > > > Status code: 404 for > > > https://infrastructure.fedoraproject.org/repo/centos/centos-9- > > > stream/x86_64/toplink/packages/basesystem/11/13.el9/noarch/basesy > > > stem-11-13.el9.noarch.rpm > > > (IP: 38.145.60.16) > > > > > > Am I doing anything wrong here, is it just that we can't > > > currently > > > build for EPEL9? > > > > > > You certainly can build for epel9. > > But you haven't said what command(s) you are doing that gives that > > output. > > Let us know what you are doing, and that will make it possible for > > us to help. > > > > I have the same problem using fedpkg-1.41-2.fc35. > > Using "fedpkg --release epel9 mockbuild" fails with that error > consistently. I tried to test builds of a couple of packages locally > before doing branch requests and I couldn't. Yeah sorry about that, I tried two different things, in the EPEL9 branch of my code: fedpkg mockbuild and also fedpkg scratch-build Both cases came out with pretty much the same error, i.e. couldn't get basesystem. Regards Frank ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Builds for EPEL9
On Mon, Dec 13, 2021 at 6:13 AM Troy Dawson wrote: > > > > On Sat, Dec 11, 2021 at 1:58 AM Frank Crawford > wrote: >> >> Folks, >> >> I'm looking at building a package that currently exists in EPEL8 for >> EPEL9. I have a new branch epel9 branch for my package, but when I try >> to do a mock build or scratch build it fails with the error: >> >> Error: Error downloading packages: >> Status code: 404 for >> https://infrastructure.fedoraproject.org/repo/centos/centos-9-stream/x86_64/toplink/packages/basesystem/11/13.el9/noarch/basesystem-11-13.el9.noarch.rpm >> (IP: 38.145.60.16) >> >> Am I doing anything wrong here, is it just that we can't currently >> build for EPEL9? > > > You certainly can build for epel9. > But you haven't said what command(s) you are doing that gives that output. > Let us know what you are doing, and that will make it possible for us to help. > I have the same problem using fedpkg-1.41-2.fc35. Using "fedpkg --release epel9 mockbuild" fails with that error consistently. I tried to test builds of a couple of packages locally before doing branch requests and I couldn't. -- 真実はいつも一つ！/ Always, there's only one truth! ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
