action #92128
closed
- Description updated (diff)
- Subject changed from openQA-devel broken on Leap 15.2 (Cpanel::JSON::XS dependency) to openQA-(common|devel) broken on Leap 15.2 (Cpanel::JSON::XS dependency)
- Description updated (diff)
- Project changed from QA to openQA Project
- Subject changed from openQA-(common|devel) broken on Leap 15.2 (Cpanel::JSON::XS dependency) to openQA-devel broken on Leap 15.2 (Cpanel::JSON::XS dependency)
- Description updated (diff)
- Category set to Regressions/Crashes
Oh, now I get it. So you would want to have updated dependencies be automatically pulled in by the official Leap package openQA-devel to build a current openQA? Ok, I think that we really can not do. Anyone has an idea how we could make that obvious maybe within the package openQA-devel? Or maybe we can put something into our source code of the update package to fail with an explicit message? Like a version check within openQA that parses cpanfile?
- Description updated (diff)
- Subject changed from openQA-devel broken on Leap 15.2 (Cpanel::JSON::XS dependency) to openQA-(common|devel) broken on Leap 15.2 (Cpanel::JSON::XS dependency)
@okurz It's both openqa-common and openqa-devel. I edited the title and it got overwritten by your change.
The version requirement is already fixed in the latest openQA, so I'm not sure what you mean by a version check within openQA that parses cpanfile.
The version requirement simply was not specified before in the .spec file and dependencies.yaml and cpanfile.
The thing is when we execute openQA from git but within openSUSE Leap 15.2 with the old package version of dependencies then we hit that problem, right? So I thought of a check within the source code that would be executed when running with old dependencies.
The code in question is already in openQA 4.6.1589882993.dd2749ac3-lp152.1.15
On a fresh Leap 15.2:
% zypper in openQA
...
% grep allow_dupkeys /usr/share/openqa/lib/OpenQA/Command.pm
->stringify_infnan->escape_slash->allow_dupkeys->pretty;
- Priority changed from Normal to Low
- Target version changed from Ready to future
- Status changed from New to Resolved
- Assignee set to okurz
Meanwhile resolved at least on openSUSE Leap 15.3
Also available in: Atom
PDF