Re: Why branched config pointed to rolling config?
On Wed, 2024-02-14 at 15:38 +, Sérgio Basto wrote: > On Wed, 2024-02-14 at 13:38 +, Mikhail Gavrilov wrote: > > Why branched config pointed to rolling config? > > # ls -ln | grep fedora-40 > > lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-aarch64.cfg -> > > fedora-rawhide-aarch64.cfg > > lrwxrwxrwx. 1 0 135 23 Jan 11 20:46 fedora-40-i386.cfg -> fedora- > > rawhide-i386.cfg > > lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-ppc64le.cfg -> > > fedora-rawhide-ppc64le.cfg > > lrwxrwxrwx. 1 0 135 24 Jan 11 20:46 fedora-40-s390x.cfg -> > > fedora- > > rawhide-s390x.cfg > > lrwxrwxrwx. 1 0 135 25 Jan 11 20:46 fedora-40-x86_64.cfg -> > > fedora- > > rawhide-x86_64.cfg > > > > I build every day mesa snapshot, but today `mock -r fedora-rawhide- > > i386 ...` beginning create packages of 41 branch. And I can't fix > > it > > by `mock -r fedora-40-i386 ...` because 40 means rawhide now :( > > we need update mock-core-configs, but is not yet available , I'm > going > check it with Fedora Build System group After update mock-core-configs with [1] the problem should be fixed [1] dnf update --enablerepo=updates-testing --refresh mock-core-configs -- Sérgio M. B. -- ___ devel mailing list -- devel@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Why branched config pointed to rolling config?
Dne 15. 02. 24 v 6:38 Mikhail Gavrilov napsal(a): I think that getting the f41 package with fedora-40 config looks at least odd. And one of the solutions is making rolling config pointed to branch config rather than the other way around. Than you will get f40 packages with rawhide config. There is no clean winner in this race. -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys -- ___ devel mailing list -- devel@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Why branched config pointed to rolling config?
I think that getting the f41 package with fedora-40 config looks at least odd. And one of the solutions is making rolling config pointed to branch config rather than the other way around. -- Best Regards, Mike Gavrilov. -- ___ devel mailing list -- devel@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Why branched config pointed to rolling config?
Dne 14. 02. 24 v 14:56 Michael J Gruber napsal(a): Why branched config pointed to rolling config? # ls -ln | grep fedora-40 lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-aarch64.cfg -> fedora-rawhide-aarch64.cfg lrwxrwxrwx. 1 0 135 23 Jan 11 20:46 fedora-40-i386.cfg -> fedora-rawhide-i386.cfg lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-ppc64le.cfg -> fedora-rawhide-ppc64le.cfg lrwxrwxrwx. 1 0 135 24 Jan 11 20:46 fedora-40-s390x.cfg -> fedora-rawhide-s390x.cfg lrwxrwxrwx. 1 0 135 25 Jan 11 20:46 fedora-40-x86_64.cfg -> fedora-rawhide-x86_64.cfg ... because on Jan 25th, f40 was rawhide. We branched yesterday. So, either you wait for updated mock-config to land in f40, or you roll it yourself. It's no mock science And if you check Bodhi, it is sitting there and waiting for you guys :) https://bodhi.fedoraproject.org/updates/?search=mock-core-configs -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys -- ___ devel mailing list -- devel@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Why branched config pointed to rolling config?
On Wed, 2024-02-14 at 13:38 +, Mikhail Gavrilov wrote: > Why branched config pointed to rolling config? > # ls -ln | grep fedora-40 > lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-aarch64.cfg -> > fedora-rawhide-aarch64.cfg > lrwxrwxrwx. 1 0 135 23 Jan 11 20:46 fedora-40-i386.cfg -> fedora- > rawhide-i386.cfg > lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-ppc64le.cfg -> > fedora-rawhide-ppc64le.cfg > lrwxrwxrwx. 1 0 135 24 Jan 11 20:46 fedora-40-s390x.cfg -> fedora- > rawhide-s390x.cfg > lrwxrwxrwx. 1 0 135 25 Jan 11 20:46 fedora-40-x86_64.cfg -> fedora- > rawhide-x86_64.cfg > > I build every day mesa snapshot, but today `mock -r fedora-rawhide- > i386 ...` beginning create packages of 41 branch. And I can't fix it > by `mock -r fedora-40-i386 ...` because 40 means rawhide now :( we need update mock-core-configs, but is not yet available , I'm going check it with Fedora Build System group -- Sérgio M. B. -- ___ devel mailing list -- devel@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Why branched config pointed to rolling config?
Am Mi., 14. Feb. 2024 um 14:48 Uhr schrieb Mikhail Gavrilov : > > Why branched config pointed to rolling config? > # ls -ln | grep fedora-40 > lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-aarch64.cfg -> > fedora-rawhide-aarch64.cfg > lrwxrwxrwx. 1 0 135 23 Jan 11 20:46 fedora-40-i386.cfg -> > fedora-rawhide-i386.cfg > lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-ppc64le.cfg -> > fedora-rawhide-ppc64le.cfg > lrwxrwxrwx. 1 0 135 24 Jan 11 20:46 fedora-40-s390x.cfg -> > fedora-rawhide-s390x.cfg > lrwxrwxrwx. 1 0 135 25 Jan 11 20:46 fedora-40-x86_64.cfg -> > fedora-rawhide-x86_64.cfg ... because on Jan 25th, f40 was rawhide. We branched yesterday. So, either you wait for updated mock-config to land in f40, or you roll it yourself. It's no mock science :) Michael -- ___ devel mailing list -- devel@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Why branched config pointed to rolling config?
Why branched config pointed to rolling config? # ls -ln | grep fedora-40 lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-aarch64.cfg -> fedora-rawhide-aarch64.cfg lrwxrwxrwx. 1 0 135 23 Jan 11 20:46 fedora-40-i386.cfg -> fedora-rawhide-i386.cfg lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-ppc64le.cfg -> fedora-rawhide-ppc64le.cfg lrwxrwxrwx. 1 0 135 24 Jan 11 20:46 fedora-40-s390x.cfg -> fedora-rawhide-s390x.cfg lrwxrwxrwx. 1 0 135 25 Jan 11 20:46 fedora-40-x86_64.cfg -> fedora-rawhide-x86_64.cfg I build every day mesa snapshot, but today `mock -r fedora-rawhide-i386 ...` beginning create packages of 41 branch. And I can't fix it by `mock -r fedora-40-i386 ...` because 40 means rawhide now :( -- ___ devel mailing list -- devel@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Why branched config pointed to rolling config?
Why branched config pointed to rolling config? # ls -ln | grep fedora-40 lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-aarch64.cfg -> fedora-rawhide-aarch64.cfg lrwxrwxrwx. 1 0 135 23 Jan 11 20:46 fedora-40-i386.cfg -> fedora-rawhide-i386.cfg lrwxrwxrwx. 1 0 135 26 Jan 11 20:46 fedora-40-ppc64le.cfg -> fedora-rawhide-ppc64le.cfg lrwxrwxrwx. 1 0 135 24 Jan 11 20:46 fedora-40-s390x.cfg -> fedora-rawhide-s390x.cfg lrwxrwxrwx. 1 0 135 25 Jan 11 20:46 fedora-40-x86_64.cfg -> fedora-rawhide-x86_64.cfg I build every day mesa snapshot, but today `mock -r fedora-rawhide-i386 ...` beginning create packages of 41 branch. And I can't fix it by `mock -r fedora-40-i386 ...` because 40 means rawhide now :( -- ___ devel mailing list -- devel@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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
