mbs-build local --add-local-build MODULE:STREAM adds locally built MODULE:STREAM to repositories available in mock environment. The problem is that the MODULE:STREAM's module-build-macros package is kept there, so we have two module-build-macros packages in the mock available. The MODULE:STREAM's one and the one of the currently being built module. The module-build-macros packages have this version 0.1-1.module_XXXXXXXX.noarch. The versions differ only in the context XXXXXXXX hash. Because the hashed are pseudorandom, it can happen, and it happens on my system, that MODULE:STREAM's package is higher and is installed into the buildroot. This completely breaks building the layered module: ~/modulebuild/builds/module-autoconf-master-20170831072511/results$ grep -e 'module-build-macros.*noarch' *-stderr* autoconf-mock-stderr.log:DEBUG: Installing : module-build-macros-0.1-1.module_7f52030a.noarch 158/158 autoconf-mock-stderr.log:DEBUG: Verifying : module-build-macros-0.1-1.module_7f52030a.noarch 152/158 autoconf-mock-stderr.log:DEBUG: module-build-macros.noarch 0.1-1.module_7f52030a autoconf-mock-stderr.log:DEBUG: module-build-macros-0.1-1.module_7f52030a.noarch module-build-macros-mock-stderr.log:DEBUG: Processing files: module-build-macros-0.1-1.module_6b4d8d18.noarch module-build-macros-mock-stderr.log:DEBUG: Zapsáno: /builddir/build/RPMS/module-build-macros-0.1-1.module_6b4d8d18.noarch.rpm Here you can see building autoconf:master. First module-build-macros-0.1-1.module_7f52030a.noarch is built and then when building autoconf, module-build-macros-0.1-1.module_7f52030a.noarch is used instead. The wrong packages comes from a build-required module I built locally before and specificed via --add-local-build option. Either you must install module-build-macros by full NEVRA into the build root, or delete module-build-macros from --add-local-build specified repositories, or you should make the hashes comparable as I proposed four months ago <https://pagure.io/fm-orchestrator/issue/494>. Affected package: module-build-service-1.3.26-3.fc26.noarch.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.