Affected packages

Packages affected by device-mapper-libs upgrade from 7:1.02.164-7.el7_8.1 to 7:1.02.164-7.el7_8.2 (in EPEL 7)
Package Current state Build Distance Build time
python34 build 4 2 months ago
root build 4 2 months ago
rubygem-execjs build None 18 days ago
rubygem-coffee-script build None 18 days ago
rubygem-uglifier build None 18 days ago
nodejs-jsonstream build None 19 days ago
js-sizzle build None 19 days ago
js-jquery1 build None 19 days ago
js-jquery build None 19 days ago
python-locket build None 19 days ago
rubygem-tilt build None 19 days ago
nodejs-require-all build None 19 days ago
nodejs-hashish build None 19 days ago
nodejs-deep-equal build None 19 days ago
nodejs-bignumber-js build None 19 days ago
nodejs-tinycolor build None 19 days ago
nodejs-underscore-dot-string build None 19 days ago
nodejs-optimist build None 19 days ago
nodejs-options build None 19 days ago
nodejs-defined build None 19 days ago
nodejs-amdefine build None 19 days ago
debhelper build None 19 days ago
php-guzzlehttp-guzzle build None 19 days ago
php-guzzle-Guzzle build None a month ago
votca-csg build None 2 months ago
thrift build None 2 months ago

Disclaimer

This page shows packages in EPEL 7 which buildability was possibly affected by device-mapper-libs upgrade from 7:1.02.164-7.el7_8.1 to 7:1.02.164-7.el7_8.2.
Please keep in mind that there were many other dependency changes happening in parallel that could have caused any particular failure.