Project

General

Profile

action #92128

openQA-(common|devel) broken on Leap 15.2 (Cpanel::JSON::XS dependency)

Added by tinita 3 months ago. Updated 16 days ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Concrete Bugs
Target version:
Start date:
2021-05-04
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

zypper info --requires openQA-common | grep Cpanel
    perl(Cpanel::JSON::XS)

Same for openQA-devel

But our code which is already in Leap 15.2 is using the allow_dupkeys feature, which was added in 4.09: https://metacpan.org/source/RURBAN/Cpanel-JSON-XS-4.26/Changes#L109
And Leap 15.2 only has Cpanel::JSON::XS 4.02

History

#1 Updated by tinita 3 months ago

  • Description updated (diff)

#2 Updated by tinita 3 months ago

  • 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)

#3 Updated by okurz 3 months ago

  • 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 Concrete Bugs

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?

#4 Updated by okurz 3 months ago

  • Description updated (diff)

#5 Updated by tinita 3 months ago

  • 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)

#6 Updated by tinita 3 months ago

okurz It's both openqa-common and openqa-devel. I edited the title and it got overwritten by your change.

#7 Updated by tinita 3 months ago

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.

#8 Updated by okurz 3 months ago

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.

#9 Updated by tinita 3 months ago

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;

#10 Updated by okurz 16 days ago

  • Priority changed from Normal to Low
  • Target version changed from Ready to future

No work on this since two months has shown that something is unclear here.

tinita could you please update the ticket according to https://progress.opensuse.org/projects/openqav3/wiki/#Defects ?

Also available in: Atom PDF