Bug #41013
Updated by Ernesto Puerta almost 5 years ago
After @ensure_decent_gcc_on_rh@, the command "@grep -q -i error: $DIR/yum-builddep.out@" wrongly catches the following string @"ValueError: SELinux policy is not managed or store cannot be accessed"@ as error (despite devtoolset is properly updated). That workaround comes cames from @739ef0f9a3a065dbb1a584f8c324b86e5dbfea68@ where @yum-builddep@ was not returning proper error codes. To fix it it'd be necessary used to find the whole "error" string. However, running @strings@ on yum-builddep does not reveal any @"error"@ string, so that error message will come from another tool. My suggestion would be to disable the current error catching mechanism, while being watchful at possible issues until install deps. As we verify are now using @yum@, let's hope that no failures are happening. it returns status code accordingly.