(In reply to Ludwig Nussel from comment #4) > let me guess, libgcj48 needs to be updated too to pick up the > %product_libs_gcc_ver_libgcj_bc1 macro Sure. And then people will still see the conflict resolution on update as we have libgcj_bc1-gcc48 installed and libgcj_bc1 and libgcj_bc1-gcc[56](?) as update candidates. Avoiding that needs to mess with gcc itself providing obsoletes/provides (not sth I would suggest). So admit failure and accept the conflict dialogue. There's a gcc48 update for SLE12 pending (not yet submitted).