Project

General

Profile

Bug #13097

MRB falls back to defaultquals when it can't find an exact match

Added by Eric Flumerfelt over 3 years ago. Updated over 3 years ago.

Status:
Accepted
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
07/01/2016
Due date:
% Done:

0%

Estimated time:
20.00 h
Duration:

Description

When using MRB for the artdaq_demo, I'm running into an issue where some of the packages try and set up conflicting versions of dependent products. I believe this is due to the fact that not all of the package qualifiers match exactly.

To reproduce:

mkdir artdaq-mrb-base
cd artdaq-mrb-base
export MRB_PROJECT=artdaq_demo
mrb newDev -v v2_08_00 -q e10:s35:eth:prof
source localProducts*/setup
cd srcs
mrb gitCheckout -d artdaq_utilities http://cdcvs.fnal.gov/projects/artdaq-utilities
mrb gitCheckout -d artdaq_core http://cdcvs.fnal.gov/projects/artdaq-core
mrb gitCheckout -d artdaq_core_demo http://cdcvs.fnal.gov/projects/artdaq-core-demo
mrb gitCheckout http://cdcvs.fnal.gov/projects/artdaq
mrb gitCheckout -d artdaq_demo http://cdcvs.fnal.gov/projects/artdaq-demo
mrb z
mrbsetenv <== Error message about non-matching products

artdaq_demo and artdaq have the eth/ib qualifier, while the rest of the products do not. Also, artdaq_utilities and artdaq_core are not setup directly by artdaq_demo but by artdaq (though I see the correct qualifiers being used for the artdaq_epics_plugin and artdaq_ganglia_plugin UPS products, which are also setup by artdaq). MRB appears to be trying to setup default_qual in this case, but the default qualifiers for these packages are e9:s21, which is where the conflicts are coming from.

artdaq_demo-v2_08_00 (2.01 KB) artdaq_demo-v2_08_00 Eric Flumerfelt, 07/01/2016 10:56 AM

History

#1 Updated by Lynn Garren over 3 years ago

This is a known problem.

#2 Updated by Lynn Garren over 3 years ago

  • Status changed from New to Accepted
  • Estimated time set to 20.00 h


Also available in: Atom PDF