Hi Mark,
On Wed, Feb 12, 2014 at 01:46:31PM -0600, Mark Hatle wrote:
On 2/12/14, 12:54 PM, Laurentiu Palcu wrote:
For some odd reason (at least I couldn't find an explanation to this,
yet), if a multilib version of a package is installed after the main one
(that is: in a different smart
On Wed, 2014-02-12 at 20:54 +0200, Laurentiu Palcu wrote:
For some odd reason (at least I couldn't find an explanation to this,
yet), if a multilib version of a package is installed after the main one
(that is: in a different smart session), the main package binaries are
not overwritten.
On Thu, Feb 13, 2014 at 11:32:36AM +, Richard Purdie wrote:
On Wed, 2014-02-12 at 20:54 +0200, Laurentiu Palcu wrote:
For some odd reason (at least I couldn't find an explanation to this,
yet), if a multilib version of a package is installed after the main one
(that is: in a different
For some odd reason (at least I couldn't find an explanation to this,
yet), if a multilib version of a package is installed after the main one
(that is: in a different smart session), the main package binaries are
not overwritten.
This commit restores the functionality to the original one, before
On 2/12/14, 12:54 PM, Laurentiu Palcu wrote:
For some odd reason (at least I couldn't find an explanation to this,
yet), if a multilib version of a package is installed after the main one
(that is: in a different smart session), the main package binaries are
not overwritten.
For two packages
