Re: Fedora 33 Mass Rebuild
Mohan, Could you please check the script filling out the FTBFS tickets is doing the right thing? There was reported this ticket against Ruby: https://bugzilla.redhat.com/show_bug.cgi?id=1865667 But I have rebuild Ruby already on Friday 31st: https://koji.fedoraproject.org/koji/buildinfo?buildID=1567804 while the ticket references some failed ELN build: https://koji.fedoraproject.org/koji/taskinfo?taskID=48384772 Thanks Vít Dne 02. 08. 20 v 0:57 Mohan Boddu napsal(a): > Hi all, > > Per the Fedora 33 schedule[1] we started a mass rebuild for Fedora 33 > on Jul 27th 2017. We did a mass rebuild for Fedora 33 for the changes listed > in: > > https://pagure.io/releng/issue/9616 > > Mass rebuild was done in a side tag (f33-rebuild) and moved over to f33. > > Failures can be seen > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > Things still needing rebuilt > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html > > 18002 builds have been tagged into f33, there are currently 2811 failed > builds that need to be addressed by the package maintainers. > > Mass rebuildling of modules and FTBFS bugs will be filed shortly. > > Please be sure to let releng know if you see any bugs in the > reporting. You can contact releng in #fedora-releng on freenode, by > dropping an email to our list[2] or filing an issue in pagure[3] > > Regards, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html > [2] > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > [3] https://pagure.io/releng/ > > On Wed, Jul 22, 2020 at 10:59 AM Mohan Boddu wrote: >> Hi all, >> >> The mass rebuild is postponed to next Monday 27th July 2020 since a >> couple of changes haven't landed yet. >> >> For more information, please look at https://pagure.io/fesco/issue/2451 >> >> We will keep you posted if anything changes. >> >> Thanks. >> >> On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote: >>> Mohan Boddu >>> >>> 4:32 PM (1 hour ago) >>> to devel-announce >>> Hi all, >>> >>> Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 >>> on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the >>> changes listed in: >>> >>> https://pagure.io/releng/issues?status=Open=mass+rebuild >>> >>> Mass rebuild will be done in a side tag (f33-rebuild) and moved over >>> when completed. >>> >>> Failures can be seen >>> https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html >>> >>> Things still needing rebuilt >>> https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html >>> >>> FTBFS bugs will be filed shortly. >>> >>> Please be sure to let releng know if you see any bugs in the >>> reporting. You can contact releng in #fedora-releng on freenode, by >>> dropping an email to our list[2] or filing an issue in pagure[3] >>> >>> Regards, >>> Mohan Boddu. >>> >>> [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html >>> [2] >>> https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ >>> [3] https://pagure.io/releng/ > ___ > devel-announce mailing list -- devel-annou...@lists.fedoraproject.org > To unsubscribe send an email to devel-announce-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-annou...@lists.fedoraproject.org > ___ > 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 ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 7:04 PM Nicolas Chauvet wrote: > > Le lun. 3 août 2020 à 23:18, Neal Gompa a écrit : > > > > On Mon, Aug 3, 2020 at 3:59 PM Nicolas Chauvet wrote: > > > > > > Le lun. 3 août 2020 à 19:37, Neal Gompa a écrit : > > > > > > > > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster > > > > wrote: > > > > > > > > > > On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes > > > > > wrote: > > > > > > > > > > > Most of those are the libcroco->gettext breakage, no? > > > > > > > > > > From a very cursory scan (not at all scientific), > > > > > some percentage are the cmake macro changes. > > > > > > > > CMake macros are documented in the packaging guidelines: > > > > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > > > > > > > Here's an example of how to adjust it: > > > > https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f > > > > > > Can you show an example that work across all maintained releases ? > > > (aka inclusing epel7). > > > > > > > I don't have a package off-hand that is maintained across EPEL7, > > EPEL8, and Fedora, but the macros are all implemented, provided you > > are using cmake3 for EPEL7. > > > > If you don't care whether it's in-source or out-of-source build, then > > you only need to concern yourself with %cmake, %cmake_build, and > > %cmake_install (for EPEL7, %cmake3 is the prefix instead of %cmake). > > The problem is that I care and usually use out of source build > (manually creating build dir and etc), but having to define > __cmake_in_source_build 1 looks miss-named if already using a > dedicated build sub-directory. > If I'm using %cmake macros without a build sub-directory, then I'm > losing the source tree versus build tree there. This is possible, but > a little backward. > > Or did I miss something ? In Fedora 33 and newer, __cmake_in_source_build is *not defined*, so it defaults to out of source builds. In Fedora 32 and older, including EPEL7 and EPEL8, it *is defined*, so it defaults to in-source builds. Doing "%undefine __cmake_in_source_build" will make the F33+ behavior apply on older Fedora and EPEL8. You'll additionally want to do "%undefine __cmake3_in_source_build" to make this work with EPEL7's cmake3 package. -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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
Re: Fedora 33 Mass Rebuild
Le lun. 3 août 2020 à 23:18, Neal Gompa a écrit : > > On Mon, Aug 3, 2020 at 3:59 PM Nicolas Chauvet wrote: > > > > Le lun. 3 août 2020 à 19:37, Neal Gompa a écrit : > > > > > > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster > > > wrote: > > > > > > > > On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes > > > > wrote: > > > > > > > > > Most of those are the libcroco->gettext breakage, no? > > > > > > > > From a very cursory scan (not at all scientific), > > > > some percentage are the cmake macro changes. > > > > > > CMake macros are documented in the packaging guidelines: > > > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > > > > > Here's an example of how to adjust it: > > > https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f > > > > Can you show an example that work across all maintained releases ? > > (aka inclusing epel7). > > > > I don't have a package off-hand that is maintained across EPEL7, > EPEL8, and Fedora, but the macros are all implemented, provided you > are using cmake3 for EPEL7. > > If you don't care whether it's in-source or out-of-source build, then > you only need to concern yourself with %cmake, %cmake_build, and > %cmake_install (for EPEL7, %cmake3 is the prefix instead of %cmake). The problem is that I care and usually use out of source build (manually creating build dir and etc), but having to define __cmake_in_source_build 1 looks miss-named if already using a dedicated build sub-directory. If I'm using %cmake macros without a build sub-directory, then I'm losing the source tree versus build tree there. This is possible, but a little backward. Or did I miss something ? ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 10:32 AM Jaroslav Skarvada wrote: > > > > - Original Message - > > On 8/3/2020 9:42 AM, Neal Gompa wrote: > > > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster > > > wrote: > > >> On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes > > >> wrote: > > >> > > >>> Most of those are the libcroco->gettext breakage, no? > > >> From a very cursory scan (not at all scientific), > > >> some percentage are the cmake macro changes. > > > CMake macros are documented in the packaging guidelines: > > > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > > > > > Here's an example of how to adjust it: > > > https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f > > > > Indeed, using this example appears to have fixed at least one of my > > packages. > > > > > > Erich Eickmeyer > > Fedora Jam Maintainer > > > > > > > > ___ > > 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 > > > > Most of my FTBFSs are in form: > BuildrootError: Requested repo (1785390) is DELETED > > Wtf? > > E.g.: > https://bugzilla.redhat.com/show_bug.cgi?id=1863168 > https://bugzilla.redhat.com/show_bug.cgi?id=1863196 > https://bugzilla.redhat.com/show_bug.cgi?id=1863197 > https://bugzilla.redhat.com/show_bug.cgi?id=1863273 > These are what I call "transient s390x errors", even though it's not always s390x. I've had a couple, and they just required a rebuild with no changes. I have no idea of the technical reason for the error, just that I was able to successfully rebuild. ___ 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
Re: Fedora 33 Mass Rebuild
On 03/08/2020 22:32, Alexander Ploumistos wrote: Thanks, going for %define felt like trying to postpone adjusting to the new guidelines. What about any "make target1 target2" between the %cmake* macros? Do they remain as they are? A "make target" can be replaced with "%cmake_build --target target". Tom -- Tom Hughes (t...@compton.nu) http://compton.nu/ ___ 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
Re: Fedora 33 Mass Rebuild
On Tue, Aug 4, 2020 at 12:20 AM Neal Gompa wrote: > > On Mon, Aug 3, 2020 at 4:21 PM Alexander Ploumistos > wrote: > > > > Hi Neal, > > > > On Mon, Aug 3, 2020 at 8:37 PM Neal Gompa wrote: > > > > > > CMake macros are documented in the packaging guidelines: > > > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > > > So if a spec file is supposed to work on F31 to F33, "%undefine > > __cmake_in_source_build" is all that's required? > > The %undefine will make Fedora 31 and Fedora 32 CMake behave the same > way as Fedora 33 CMake. > > After that, you can switch %make_build and %make_install macros to > %cmake_build and %cmake_install. > > Alternatively, if you %define __cmake_in_source_build 1, this will > make Fedora 33 CMake behave the same way as Fedora 31 and Fedora 32 > CMake, and then the old command flow works as before. > > I recommend using the %undefine behavior and switching to the new > macros, but you can make your own judgement. Thanks, going for %define felt like trying to postpone adjusting to the new guidelines. What about any "make target1 target2" between the %cmake* macros? Do they remain as they are? For the past couple of hours I've been testing every possible combination of the macros while trying to fix liborigin (which has a completely flat tree, save for its documentation) and no matter what I choose, I always end up with a directory or file being inaccessible to cmake. It is driving me crazy. ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, 2020-08-03 at 15:39 -0400, Neal Gompa wrote: > On Mon, Aug 3, 2020 at 3:32 PM Peter Robinson > wrote: > > > > > Most of those are the libcroco->gettext breakage, no? > > > > > > > > From a very cursory scan (not at all scientific), > > > > some percentage are the cmake macro changes. > > > > > > CMake macros are documented in the packaging guidelines: > > > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > > > > > Here's an example of how to adjust it: > > > https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f > > > > The changes should have landed _BEFORE_ mass rebuild, if the change > > owner didn't have the permissions they should have done PRs for all > > the packages rather than having zero direct comms to affected > > package > > owners and having them find out of a change needed post mass > > rebuild > > when they get generic FTBFS bugs. > > > > Now people have even more work to do for the unexpected mess :-( > > For what it's worth, I've spent almost every single weekend > alternating between this change and the Btrfs one. I wound up also > having to implement the EPEL7 and EPEL8 macros (that were out of > scope > of the change, but I did it anyway because people complained). Igor > and myself had been working on doing the updates each weekend we > could, however my internet connectivity to Dist-Git and Koji had been > troublesome for the past few weekends, and that has made working on > it > hard. Thanks for doing the EPEL macros! That was one of the major concerns with the initial change proposal, if I recall the discussion. I'm fixing one of my package now (et) since there's an update for it last week that I want to push out anyway, and being able to use the same macros on EPEL8 is really nice. Regards, -- Michel Alexandre Salim profile: https://keybase.io/michel_slm chat via email: https://delta.chat/ GPG key: 5DCE 2E7E 9C3B 1CFF D335 C1D7 8B22 9D2F 7CCC 04F2 signature.asc Description: This is a digitally signed message part ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 4:22 PM Miro Hrončok wrote: > > On 03. 08. 20 22:19, Neal Gompa wrote: > > If you don't care whether it's in-source or out-of-source build, then > > you only need to concern yourself with %cmake, %cmake_build, and > > %cmake_install (for EPEL7, %cmake3 is the prefix instead of %cmake). > > Neal, can I safely use this on EPEL7 and Fedora? > > %undefine __cmake_in_source_build > %cmake3 > %cmake3_build > %cmake3_install > > ? You'll need one more for EPEL7: %undefine __cmake3_in_source_build But otherwise, yes, provided you "BuildRequires: cmake3" for EPEL7. -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 4:21 PM Alexander Ploumistos wrote: > > Hi Neal, > > On Mon, Aug 3, 2020 at 8:37 PM Neal Gompa wrote: > > > > CMake macros are documented in the packaging guidelines: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > So if a spec file is supposed to work on F31 to F33, "%undefine > __cmake_in_source_build" is all that's required? The %undefine will make Fedora 31 and Fedora 32 CMake behave the same way as Fedora 33 CMake. After that, you can switch %make_build and %make_install macros to %cmake_build and %cmake_install. Alternatively, if you %define __cmake_in_source_build 1, this will make Fedora 33 CMake behave the same way as Fedora 31 and Fedora 32 CMake, and then the old command flow works as before. I recommend using the %undefine behavior and switching to the new macros, but you can make your own judgement. -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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
Re: Fedora 33 Mass Rebuild
On 03. 08. 20 22:19, Neal Gompa wrote: If you don't care whether it's in-source or out-of-source build, then you only need to concern yourself with %cmake, %cmake_build, and %cmake_install (for EPEL7, %cmake3 is the prefix instead of %cmake). Neal, can I safely use this on EPEL7 and Fedora? %undefine __cmake_in_source_build %cmake3 %cmake3_build %cmake3_install ? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 3:59 PM Nicolas Chauvet wrote: > > Le lun. 3 août 2020 à 19:37, Neal Gompa a écrit : > > > > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster > > wrote: > > > > > > On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote: > > > > > > > Most of those are the libcroco->gettext breakage, no? > > > > > > From a very cursory scan (not at all scientific), > > > some percentage are the cmake macro changes. > > > > CMake macros are documented in the packaging guidelines: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > > > Here's an example of how to adjust it: > > https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f > > Can you show an example that work across all maintained releases ? > (aka inclusing epel7). > I don't have a package off-hand that is maintained across EPEL7, EPEL8, and Fedora, but the macros are all implemented, provided you are using cmake3 for EPEL7. If you don't care whether it's in-source or out-of-source build, then you only need to concern yourself with %cmake, %cmake_build, and %cmake_install (for EPEL7, %cmake3 is the prefix instead of %cmake). -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 7:32 PM Peter Robinson wrote: > The changes should have landed _BEFORE_ mass rebuild, if the change > owner didn't have the permissions they should have done PRs for all > the packages rather than having zero direct comms to affected package > owners and having them find out of a change needed post mass rebuild > when they get generic FTBFS bugs. > > Now people have even more work to do for the unexpected mess :-( Since the changes did not land before the mass rebuild (which I agree should have been the requirement), I would presume that a responsible change owner, who agreed in the proposal to make the required changes to packages, would also take ownership of each and every related FTBFS bugzilla entry and mark it ASSIGNED (to themselves). They (knowingly) broke it, they own it. And the best way to make the packagers aware the the change owners are taking their responsibilities seriously is update the FTBFS bugzillas. ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 3:32 PM Peter Robinson wrote: > > > > > Most of those are the libcroco->gettext breakage, no? > > > > > > From a very cursory scan (not at all scientific), > > > some percentage are the cmake macro changes. > > > > CMake macros are documented in the packaging guidelines: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > > > Here's an example of how to adjust it: > > https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f > > The changes should have landed _BEFORE_ mass rebuild, if the change > owner didn't have the permissions they should have done PRs for all > the packages rather than having zero direct comms to affected package > owners and having them find out of a change needed post mass rebuild > when they get generic FTBFS bugs. > > Now people have even more work to do for the unexpected mess :-( For what it's worth, I've spent almost every single weekend alternating between this change and the Btrfs one. I wound up also having to implement the EPEL7 and EPEL8 macros (that were out of scope of the change, but I did it anyway because people complained). Igor and myself had been working on doing the updates each weekend we could, however my internet connectivity to Dist-Git and Koji had been troublesome for the past few weekends, and that has made working on it hard. Even with all that, we did already fix somewhere close to 500 of the 1469 packages that required updates. Do not insinuate that we are not trying! The sheer number of packages to fix, combined with everybody using CMake slightly differently, has made this not as straightforward as I wanted it to be. -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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
Re: Fedora 33 Mass Rebuild
On 03. 08. 20 21:02, Nicolas Chauvet wrote: Can you show an example that work across all maintained releases ? (aka inclusing epel7). https://src.fedoraproject.org/rpms/lib3mf/c/69ac5cb696456d7f5478f47bf2bcf234ab77ba56?branch=master -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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
Re: Fedora 33 Mass Rebuild
Hi Neal, On Mon, Aug 3, 2020 at 8:37 PM Neal Gompa wrote: > > CMake macros are documented in the packaging guidelines: > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ So if a spec file is supposed to work on F31 to F33, "%undefine __cmake_in_source_build" is all that's required? ___ 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
Re: Fedora 33 Mass Rebuild
Le lun. 3 août 2020 à 19:37, Neal Gompa a écrit : > > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster > wrote: > > > > On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote: > > > > > Most of those are the libcroco->gettext breakage, no? > > > > From a very cursory scan (not at all scientific), > > some percentage are the cmake macro changes. > > CMake macros are documented in the packaging guidelines: > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > Here's an example of how to adjust it: > https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f Can you show an example that work across all maintained releases ? (aka inclusing epel7). Thanks in advance. ___ 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
Re: Fedora 33 Mass Rebuild
> > > Most of those are the libcroco->gettext breakage, no? > > > > From a very cursory scan (not at all scientific), > > some percentage are the cmake macro changes. > > CMake macros are documented in the packaging guidelines: > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > Here's an example of how to adjust it: > https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f The changes should have landed _BEFORE_ mass rebuild, if the change owner didn't have the permissions they should have done PRs for all the packages rather than having zero direct comms to affected package owners and having them find out of a change needed post mass rebuild when they get generic FTBFS bugs. Now people have even more work to do for the unexpected mess :-( ___ 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
Re: Fedora 33 Mass Rebuild
- Original Message - > On Mon, Aug 03, 2020 at 01:30:56PM -0400, Jaroslav Skarvada wrote: > > > > Most of my FTBFSs are in form: > > BuildrootError: Requested repo (1785390) is DELETED > > > > Wtf? > > > > E.g.: > > https://bugzilla.redhat.com/show_bug.cgi?id=1863168 > > https://bugzilla.redhat.com/show_bug.cgi?id=1863196 > > https://bugzilla.redhat.com/show_bug.cgi?id=1863197 > > https://bugzilla.redhat.com/show_bug.cgi?id=1863273 > > > > Jaroslav > > This error is from the very beginning of the mass rebuild (more than a > week ago now). I had kojira deleting repos that were expired for more > than 5min. But of course the f33 repo regenerates all the time so it was > not sufficent for the builds when they got around to building, that repo > was gone. > > However, the fails to build from source bug filing script is mistakenly > adding the first rebuild failure, instead of the second one. ;( > > decathorpes script should resubmit these if they are caused by transient > s390x issues. > > kevin > > ___ > 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 > It seems it is not just s390x, but also armv7hl sometimes, maybe more arches, I hadn't time to go through all of them Jaroslav ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 03, 2020 at 01:30:56PM -0400, Jaroslav Skarvada wrote: > > Most of my FTBFSs are in form: > BuildrootError: Requested repo (1785390) is DELETED > > Wtf? > > E.g.: > https://bugzilla.redhat.com/show_bug.cgi?id=1863168 > https://bugzilla.redhat.com/show_bug.cgi?id=1863196 > https://bugzilla.redhat.com/show_bug.cgi?id=1863197 > https://bugzilla.redhat.com/show_bug.cgi?id=1863273 > > Jaroslav This error is from the very beginning of the mass rebuild (more than a week ago now). I had kojira deleting repos that were expired for more than 5min. But of course the f33 repo regenerates all the time so it was not sufficent for the builds when they got around to building, that repo was gone. However, the fails to build from source bug filing script is mistakenly adding the first rebuild failure, instead of the second one. ;( decathorpes script should resubmit these if they are caused by transient s390x issues. kevin signature.asc Description: PGP signature ___ 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
Re: Fedora 33 Mass Rebuild
- Original Message - > On 8/3/2020 9:42 AM, Neal Gompa wrote: > > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster > > wrote: > >> On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote: > >> > >>> Most of those are the libcroco->gettext breakage, no? > >> From a very cursory scan (not at all scientific), > >> some percentage are the cmake macro changes. > > CMake macros are documented in the packaging guidelines: > > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > > > Here's an example of how to adjust it: > > https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f > > Indeed, using this example appears to have fixed at least one of my > packages. > > > Erich Eickmeyer > Fedora Jam Maintainer > > > > ___ > 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 > Most of my FTBFSs are in form: BuildrootError: Requested repo (1785390) is DELETED Wtf? E.g.: https://bugzilla.redhat.com/show_bug.cgi?id=1863168 https://bugzilla.redhat.com/show_bug.cgi?id=1863196 https://bugzilla.redhat.com/show_bug.cgi?id=1863197 https://bugzilla.redhat.com/show_bug.cgi?id=1863273 Jaroslav ___ 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
Re: Fedora 33 Mass Rebuild
On 8/3/2020 9:42 AM, Neal Gompa wrote: > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster > wrote: >> On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote: >> >>> Most of those are the libcroco->gettext breakage, no? >> From a very cursory scan (not at all scientific), >> some percentage are the cmake macro changes. > CMake macros are documented in the packaging guidelines: > https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ > > Here's an example of how to adjust it: > https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f Indeed, using this example appears to have fixed at least one of my packages. Erich Eickmeyer Fedora Jam Maintainer pEpkey.asc Description: application/pgp-keys ___ 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
Re: Fedora 33 Mass Rebuild
On 8/3/2020 9:38 AM, Gary Buhrmaster wrote: > On Mon, Aug 3, 2020 at 4:24 PM Peter Robinson wrote: > >> There's also a bunch of CMake related ones and I'm not even sure how >> to deal with that. > The proposal owners stated that: > > Existing packages can (and most likely will) become FTBFS, but > proposal owners will fix as many Fedora packages as possible. > > I interpret that as the proposal owners are about to push > a bunch of fixes RSN and rebuild the impacted packages. I certainly hope so. All of my FTBFS packages are due to the cmake issue. This is not good, and I have zero knowledge of how to fix them. - Erich Eickmeyer Fedora Jam Maintainer pEpkey.asc Description: application/pgp-keys ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster wrote: > > On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote: > > > Most of those are the libcroco->gettext breakage, no? > > From a very cursory scan (not at all scientific), > some percentage are the cmake macro changes. CMake macros are documented in the packaging guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/CMake/ Here's an example of how to adjust it: https://src.fedoraproject.org/rpms/alembic/c/83812e6c762c28c7e2141860711a3598c101256f -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 4:24 PM Peter Robinson wrote: > There's also a bunch of CMake related ones and I'm not even sure how > to deal with that. The proposal owners stated that: Existing packages can (and most likely will) become FTBFS, but proposal owners will fix as many Fedora packages as possible. I interpret that as the proposal owners are about to push a bunch of fixes RSN and rebuild the impacted packages. ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 5:15 PM Richard Hughes wrote: > > On Mon, 3 Aug 2020 at 14:02, Mohan Boddu wrote: > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > Most of those are the libcroco->gettext breakage, no? We're not going > to be rebuilding all affected packages manually are we?! No, at this point, most breakage (~1000 packages) stems from CMake macro changes. Regarding FTBFS issues that were caused by the transient gettext / annobin / binutils issues in the buildroot, I've been resubmitting almost all of those already, and still have a script running that will resubmit the rest of them too. Fabio ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote: > Most of those are the libcroco->gettext breakage, no? From a very cursory scan (not at all scientific), some percentage are the cmake macro changes. ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, Aug 3, 2020 at 4:15 PM Richard Hughes wrote: > > On Mon, 3 Aug 2020 at 14:02, Mohan Boddu wrote: > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > Most of those are the libcroco->gettext breakage, no? We're not going > to be rebuilding all affected packages manually are we?! There's also a bunch of CMake related ones and I'm not even sure how to deal with that. ___ 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
Re: Fedora 33 Mass Rebuild
Many of this are cmake change breakage. пн, 3 авг. 2020 г., 18:15 Richard Hughes : > On Mon, 3 Aug 2020 at 14:02, Mohan Boddu wrote: > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > Most of those are the libcroco->gettext breakage, no? We're not going > to be rebuilding all affected packages manually are we?! > > Richard./ > ___ > 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 > ___ 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
Re: Fedora 33 Mass Rebuild
On Mon, 3 Aug 2020 at 14:02, Mohan Boddu wrote: > Failures can be seen > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html Most of those are the libcroco->gettext breakage, no? We're not going to be rebuilding all affected packages manually are we?! Richard./ ___ 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
Re: Fedora 33 Mass Rebuild
Hi all, Per the Fedora 33 schedule[1] we started a mass rebuild for Fedora 33 on Jul 27th 2017. We did a mass rebuild for Fedora 33 for the changes listed in: https://pagure.io/releng/issue/9616 Mass rebuild was done in a side tag (f33-rebuild) and moved over to f33. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html 18002 builds have been tagged into f33, there are currently 2811 failed builds that need to be addressed by the package maintainers. Mass rebuildling of modules and FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ On Wed, Jul 22, 2020 at 10:59 AM Mohan Boddu wrote: > > Hi all, > > The mass rebuild is postponed to next Monday 27th July 2020 since a > couple of changes haven't landed yet. > > For more information, please look at https://pagure.io/fesco/issue/2451 > > We will keep you posted if anything changes. > > Thanks. > > On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote: > > > > Mohan Boddu > > > > 4:32 PM (1 hour ago) > > to devel-announce > > Hi all, > > > > Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 > > on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the > > changes listed in: > > > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > > > Mass rebuild will be done in a side tag (f33-rebuild) and moved over > > when completed. > > > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > > > Things still needing rebuilt > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html > > > > FTBFS bugs will be filed shortly. > > > > Please be sure to let releng know if you see any bugs in the > > reporting. You can contact releng in #fedora-releng on freenode, by > > dropping an email to our list[2] or filing an issue in pagure[3] > > > > Regards, > > Mohan Boddu. > > > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html > > [2] > > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > > [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-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-annou...@lists.fedoraproject.org ___ 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
Re: Fedora 33 Mass Rebuild
Hi all, Per the Fedora 33 schedule[1] we started a mass rebuild for Fedora 33 on Jul 27th 2017. We did a mass rebuild for Fedora 33 for the changes listed in: https://pagure.io/releng/issue/9616 Mass rebuild was done in a side tag (f33-rebuild) and moved over to f33. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html 18002 builds have been tagged into f33, there are currently 2811 failed builds that need to be addressed by the package maintainers. Mass rebuildling of modules and FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ On Wed, Jul 22, 2020 at 10:59 AM Mohan Boddu wrote: > > Hi all, > > The mass rebuild is postponed to next Monday 27th July 2020 since a > couple of changes haven't landed yet. > > For more information, please look at https://pagure.io/fesco/issue/2451 > > We will keep you posted if anything changes. > > Thanks. > > On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote: > > > > Mohan Boddu > > > > 4:32 PM (1 hour ago) > > to devel-announce > > Hi all, > > > > Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 > > on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the > > changes listed in: > > > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > > > Mass rebuild will be done in a side tag (f33-rebuild) and moved over > > when completed. > > > > Failures can be seen > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > > > Things still needing rebuilt > > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html > > > > FTBFS bugs will be filed shortly. > > > > Please be sure to let releng know if you see any bugs in the > > reporting. You can contact releng in #fedora-releng on freenode, by > > dropping an email to our list[2] or filing an issue in pagure[3] > > > > Regards, > > Mohan Boddu. > > > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html > > [2] > > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > > [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-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-announce@lists.fedoraproject.org
Re: Fedora 33 Mass Rebuild
Hi all, The mass rebuild is postponed to next Monday 27th July 2020 since a couple of changes haven't landed yet. For more information, please look at https://pagure.io/fesco/issue/2451 We will keep you posted if anything changes. Thanks. On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote: > > Mohan Boddu > > 4:32 PM (1 hour ago) > to devel-announce > Hi all, > > Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 > on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the > changes listed in: > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > Mass rebuild will be done in a side tag (f33-rebuild) and moved over > when completed. > > Failures can be seen > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > Things still needing rebuilt > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html > > FTBFS bugs will be filed shortly. > > Please be sure to let releng know if you see any bugs in the > reporting. You can contact releng in #fedora-releng on freenode, by > dropping an email to our list[2] or filing an issue in pagure[3] > > Regards, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html > [2] > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-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-announce@lists.fedoraproject.org
Re: Fedora 33 Mass Rebuild
Hi all, The mass rebuild is postponed to next Monday 27th July 2020 since a couple of changes haven't landed yet. For more information, please look at https://pagure.io/fesco/issue/2451 We will keep you posted if anything changes. Thanks. On Mon, Jul 20, 2020 at 5:38 PM Mohan Boddu wrote: > > Mohan Boddu > > 4:32 PM (1 hour ago) > to devel-announce > Hi all, > > Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 > on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the > changes listed in: > > https://pagure.io/releng/issues?status=Open=mass+rebuild > > Mass rebuild will be done in a side tag (f33-rebuild) and moved over > when completed. > > Failures can be seen > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html > > Things still needing rebuilt > https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html > > FTBFS bugs will be filed shortly. > > Please be sure to let releng know if you see any bugs in the > reporting. You can contact releng in #fedora-releng on freenode, by > dropping an email to our list[2] or filing an issue in pagure[3] > > Regards, > Mohan Boddu. > > [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html > [2] > https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ > [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-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-annou...@lists.fedoraproject.org ___ 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
Fedora 33 Mass Rebuild
Mohan Boddu 4:32 PM (1 hour ago) to devel-announce Hi all, Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild Mass rebuild will be done in a side tag (f33-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-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-annou...@lists.fedoraproject.org ___ 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
Fedora 33 Mass Rebuild
Mohan Boddu 4:32 PM (1 hour ago) to devel-announce Hi all, Per the Fedora 33 schedule[1] we will start a mass rebuild for Fedora 33 on Jul 22nd 2020. We will run a mass rebuild for Fedora 33 for the changes listed in: https://pagure.io/releng/issues?status=Open=mass+rebuild Mass rebuild will be done in a side tag (f33-rebuild) and moved over when completed. Failures can be seen https://kojipkgs.fedoraproject.org/mass-rebuild/f33-failures.html Things still needing rebuilt https://kojipkgs.fedoraproject.org/mass-rebuild/f33-need-rebuild.html FTBFS bugs will be filed shortly. Please be sure to let releng know if you see any bugs in the reporting. You can contact releng in #fedora-releng on freenode, by dropping an email to our list[2] or filing an issue in pagure[3] Regards, Mohan Boddu. [1] https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html [2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/ [3] https://pagure.io/releng/ ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-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-announce@lists.fedoraproject.org
