|
Bugzilla – Full Text Bug Listing |
| Summary: | open build service raises 'Failed build dependencies' when new BuildRequires tag added to the .spec file by the _service during runtime, instead installing build requirements | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE.org | Reporter: | huakim tylyktar <fijik19> |
| Component: | BuildService | Assignee: | E-mail List <screening-team-bugs> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Adrian Schröter <adrian.schroeter> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | fijik19, mcepl |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | log file indicating what happened during build process | ||
|
Description
huakim tylyktar
2024-07-02 16:03:34 UTC
Created attachment 875834 [details]
log file indicating what happened during build process
yes, it is too late to do that at build time. The VM has no network and the dependencies can not pre-calculated. Either do that in default mode, so the change gets commited to the source. Alternative is to use dynamic build dependency implementation where another build job gets started in case dependencies are changing. That is a generic rpm feature, supported by OBS by respawning a new job. https://fedoraproject.org/wiki/Changes/DynamicBuildRequires closing as works as designed. (In reply to Adrian Schröter from comment #2) > yes, it is too late to do that at build time. The VM has no network and the > dependencies can not pre-calculated. > > Either do that in default mode, so the change gets commited to the source. > > Alternative is to use dynamic build dependency implementation where another > build job gets started in case dependencies are changing. That is a generic > rpm feature, supported by OBS by respawning a new job. > https://fedoraproject.org/wiki/Changes/DynamicBuildRequires > > > closing as works as designed. But, maybe, we just need to add the feauture to order to respawn a new job before rpmbuild? (In reply to huakim tylyktar from comment #3) > (In reply to Adrian Schröter from comment #2) > > yes, it is too late to do that at build time. The VM has no network and the > > dependencies can not pre-calculated. > > > > Either do that in default mode, so the change gets commited to the source. > > > > Alternative is to use dynamic build dependency implementation where another > > build job gets started in case dependencies are changing. That is a generic > > rpm feature, supported by OBS by respawning a new job. > > https://fedoraproject.org/wiki/Changes/DynamicBuildRequires > > > > > > closing as works as designed. > > But, maybe, we just need to add the feauture to order to respawn a new job > before rpmbuild? And, of course, with keeping generic rpm feauture. this is already supported by OBS. It restarts the build when dependencies are changing. (In reply to Adrian Schröter from comment #5) > this is already supported by OBS. It restarts the build when dependencies > are changing. There are also error that prevent from building: unresolvable: nothing provides %{lua_module, nothing provides luarocks}, nothing provides devel} The lua-module macro is provided in lua-rpm-macros package I added lua-rpm-macros to project configuration (In reply to huakim tylyktar from comment #6) > (In reply to Adrian Schröter from comment #5) > > this is already supported by OBS. It restarts the build when dependencies > > are changing. > > There are also error that prevent from building: > unresolvable: nothing provides %{lua_module, nothing provides luarocks}, > nothing provides devel} > The lua-module macro is provided in lua-rpm-macros package > I added lua-rpm-macros to project configuration The .spec file contains line BulidRequires: %{lua_module} |