Fedora 37 builds hanging in limbo
Hey there, I recently enabled Fedora 37 (which was published recently) on two projects on OBS [1-2]. They build just fine, but then get stuck in the finished state. I have no idea why that is the case. Seems like no worker is picking the finished builds up and deploys them. Unfortunately, this blocks all other package builds in the project, too. I suppose this might be a (configuration?) bug within OBS. Could you please tell me whether Fedora 37 is fully supported as of yet? We'd really like to publish software for this distribution. Kind regards, Fabian P.S.: I tried to rebuild the packages already (aborting the builds didn't do anything, so I removed and re-added the packages from the metadata, which caused OBS to trigger new builds which ended up stuck in finished state again). [1] https://build.opensuse.org/project/monitor/isv:ownCloud:Qt51210?arch_x86_64=1&defaults=0&finished=1&repo_Fedora_37=1 [2] https://build.opensuse.org/project/monitor/isv:ownCloud:Qt5152?arch_x86_64=1&defaults=0&finished=1&repo_Fedora_37=1 -- Store. Share. Work. https://owncloud.com Fabian Müller Engineering - Team Desktop & Mobile email: fmueller@owncloud.org ownCloud GmbH Rathsbergstrasse 17 90411 Nuremberg, Germany Managing Directors: Tobias Gerlinger, Holger Dyroff Court of Registry: Amtsgericht Nuremberg Commercial Register No.: 28050
On Nov 22 2022, Fabian Müller wrote:
I recently enabled Fedora 37 (which was published recently) on two projects on OBS [1-2]. They build just fine, but then get stuck in the finished state.
That can happen when the scheduler is busy serving other projects. It will be finalized eventually, though the repository setup is currently broken: Fedora_37 x86_64 (broken details: unresolvable preinstalls: have choice for libsqlite3.so.0()(64bit) needed by rpm-libs: ocqt51210-libsqlite3-0 sqlite-libs) -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
On 23.11.22 00:37, Andreas Schwab wrote:> That can happen when the scheduler is busy serving other projects. True that, but it's unusual that the scheduler doesn't pick up any builds from that one distribution while others don't seem to be affected. I can't tell for sure, but I'm relatively certain this was the case with previous distribution releases as well.
It will be finalized eventually, though the repository setup is currently broken:
Fedora_37 x86_64 (broken details: unresolvable preinstalls: have choice for libsqlite3.so.0()(64bit) needed by rpm-libs: ocqt51210-libsqlite3-0 sqlite-libs)
I'll have a look, thanks. That shouldn't affect the finished builds, though, it just prevents the build of some other packages. Regards Fabian -- Store. Share. Work. https://owncloud.com Fabian Müller Engineering - Team Desktop & Mobile email: fmueller@owncloud.org ownCloud GmbH Rathsbergstrasse 17 90411 Nuremberg, Germany Managing Directors: Tobias Gerlinger, Holger Dyroff Court of Registry: Amtsgericht Nuremberg Commercial Register No.: 28050
Fabian Müller wrote:
On 23.11.22 00:37, Andreas Schwab wrote: ... It will be finalized eventually, though the repository setup is currently broken: Fedora_37 x86_64 (broken details: unresolvable preinstalls: have choice for libsqlite3.so.0()(64bit) needed by rpm-libs: ocqt51210-libsqlite3-0 sqlite-libs) I'll have a look, thanks. That shouldn't affect the finished builds, though, it just prevents the build of some other packages. Regards Fabian
Hi Fabian, that's not exactly the whole truth. If you go to one of the affected packages [1] and click on the question mark, next to the red triangle for the "Fedora 37" repo, on the right side panel we see:
The package has been built and signed, but has not yet been picked up by the scheduler. This is an intermediate state prior to 'succeeded' or 'failed'.
The repository setup is broken, build or publish not possible
finished: succeeded
[1] https://build.opensuse.org/package/show/isv:ownCloud:Qt51210/ocqt51210-qt5-q...
Luciano Santos wrote:
Fabian Müller wrote:
On 23.11.22 00:37, Andreas Schwab wrote: ... It will be finalized eventually, though the repository setup is currently broken: Fedora_37 x86_64 (broken details: unresolvable preinstalls: have choice for libsqlite3.so.0()(64bit) needed by rpm-libs: ocqt51210-libsqlite3-0 sqlite-libs) I'll have a look, thanks. That shouldn't affect the finished builds, though, it just prevents the build of some other packages. Regards Fabian Hi Fabian, that's not exactly the whole truth. If you go to one of the affected packages [1] and click on the question mark, next to the red triangle for the "Fedora 37" repo, on the right side panel we see: The package has been built and signed, but has not yet been picked up by the scheduler. This is an intermediate state prior to 'succeeded' or 'failed'. The repository setup is broken, build or publish not possible finished: succeeded [1] https://build.opensuse.org/package/show/isv:ownCloud:Qt51210/ocqt51210-qt5-q...
A possible fix for this issue would be to change the following conditional in the project configuration [1]:
%if "%_repository" == "Fedora_33" || "%_repository" == "Fedora_34" || "%_repository" == "Fedora_35"
To:
%if "%_repository" == "Fedora_33" || "%_repository" == "Fedora_34" || "%_repository" == "Fedora_35" || "%_repository" == "Fedora_37"
[1] https://build.opensuse.org/projects/isv:ownCloud:Qt51210/prjconf Kind regards, Luciano
Hi Luciano,
A possible fix for this issue would be to change the following conditional in the project configuration [1]:
%if "%_repository" == "Fedora_33" || "%_repository" == "Fedora_34" || "%_repository" == "Fedora_35"
To:
%if "%_repository" == "Fedora_33" || "%_repository" == "Fedora_34" || "%_repository" == "Fedora_35" || "%_repository" == "Fedora_37"
[1] https://build.opensuse.org/projects/isv:ownCloud:Qt51210/prjconf
Thank you, I just implemented your suggestion. May I ask where you saw that error message? I vaguely remember I had to fix some of this when I added another Fedora release to the project. I did see the message that the repository setup was broken, but no specific details, therefore concluded that this might have been a scheduler problem. In any case, we will see if the build works now in around an hour. Kind regards Fabian -- Store. Share. Work. https://owncloud.com Fabian Müller Engineering - Team Desktop & Mobile email: fmueller@owncloud.org ownCloud GmbH Rathsbergstrasse 17 90411 Nuremberg, Germany Managing Directors: Tobias Gerlinger, Holger Dyroff Court of Registry: Amtsgericht Nuremberg Commercial Register No.: 28050
Fabian Müller wrote:
May I ask where you saw that error message?
In the web UI there's the right panel with two tabs: "Build Results" and "RPM Lint". In the "Build Results" we have a layout with the repositories we configured as build targets, and right below it the architectures with the result of the build next to it, something like:
Fedora_37 green_truck x86_64 (?) succeeded Linux_Mint_19 green_truck x86_64 (?) failed
If you hover your mouse cursor over the question mark (?), it will explain the current build status. In the Monitor tab of any project you have the button "Legend" that'll show you build statuses and there meaning as well, but not extra information, like when there's the red triangule.
On Mittwoch, 23. November 2022, 16:24:28 CET Fabian Müller wrote:
On 23.11.22 00:37, Andreas Schwab wrote:> That can happen when the scheduler is busy serving other projects.
True that, but it's unusual that the scheduler doesn't pick up any builds from that one distribution while others don't seem to be affected. I can't tell for sure, but I'm relatively certain this was the case with previous distribution releases as well.
It will be finalized eventually, though the repository setup is currently broken:
Fedora_37 x86_64 (broken details: unresolvable preinstalls: have choice for libsqlite3.so.0()(64bit) needed by rpm-libs: ocqt51210-libsqlite3-0 sqlite-libs)
I'll have a look, thanks. That shouldn't affect the finished builds, though, it just prevents the build of some other packages.
But you noticed that you created your problem yourself in your project?
You build another sqlite package which belongs to the base setup. So
a new build environment can not get calculdated anymore.
Not sure why you build this version, but you need to make a decision
in your dependencies (either in spec file or in your build config
of the project) which one to take.
--
Adrian Schroeter
On 25.11.22 11:02, Adrian Schröter wrote:
But you noticed that you created your problem yourself in your project?
You build another sqlite package which belongs to the base setup. So a new build environment can not get calculdated anymore.
Sure, that got clear after Luciano and Andreas found this error description. That issue has been fixed by now. I think OBS could be clearer on this kind of issue, though. I still have not found out where OBS reports these dependency issues (hovering over the question mark, as suggested earlier, just showed a message that suggested the packages just had to be picked up, while in reality there was a homemade configuration problem). Thanks everyone, though. Especially thanks to Luciano, your fix worked perfectly. The remaining issues required the usual back-and-forth when porting those packages to new distributions. Everything is working fine now. Best regards Fabian -- Store. Share. Work. https://owncloud.com Fabian Müller Engineering - Team Desktop & Mobile email: fmueller@owncloud.org ownCloud GmbH Rathsbergstrasse 17 90411 Nuremberg, Germany Managing Directors: Tobias Gerlinger, Holger Dyroff Court of Registry: Amtsgericht Nuremberg Commercial Register No.: 28050
participants (4)
-
Adrian Schröter -
Andreas Schwab -
Fabian Müller -
Luciano Santos