Summary: | =dev-qt/qtcore-4.8.5 collisions on downgrade from 4.8.6 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rick Farina (Zero_Chaos) <zerochaos> |
Component: | [OLD] Development | Assignee: | Qt Bug Alias <qt> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rick Farina (Zero_Chaos)
2015-03-27 15:55:04 UTC
qt4-build.eclass has this gem: ewarn "Downgrading Qt is completely unsupported and can break your system!" So if you attempt that, you're on your own anyway. That said, I'm not against adding the blocker for completeness. (In reply to Ben de Groot from comment #1) > > ewarn "Downgrading Qt is completely unsupported and can break your system!" That's mostly for historical reasons, and mainly refers to potential breakages (missing symbols) at the ABI level when downgrading, i.e. something outside our control. The file collision is a packaging bug instead, and must be fixed. 29 Mar 2015; Davide Pesavento <pesa@gentoo.org> qtcore-4.8.5-r2.ebuild: Add blocker to prevent file collision on downgrade, thanks to Zero_Chaos in bug #544666. |