On 2011-07-31, Matthias Kilian k...@outback.escape.de wrote:
On Sun, Jul 31, 2011 at 04:36:00PM +0200, Jasper Lievisse Adriaanse wrote:
Have it your way if this works. I've gone blind on those markers already..
Sure, but why does @conflict ossp-uuid-1.6.2p1 work while @conflict
On Thu, Jul 28, 2011 at 05:37:58PM +0100, Mikolaj Kucharski wrote:
I think it should have additional conflict marker with
ossp-uuid-=1.6.2. I've also changed uuid conflict marker to cover any
version of uuid package to match it with packaging list of ossp-uuid
package (see conflict markers in
Have it your way if this works. I've gone blind on those markers already..
Thanks.
On Jul 31, 2011 4:34 PM, Matthias Kilian k...@outback.escape.de wrote:
On Thu, Jul 28, 2011 at 05:37:58PM +0100, Mikolaj Kucharski wrote:
I think it should have additional conflict marker with
ossp-uuid-=1.6.2.
On Sun, Jul 31, 2011 at 04:36:00PM +0200, Jasper Lievisse Adriaanse wrote:
Have it your way if this works. I've gone blind on those markers already..
Sure, but why does @conflict ossp-uuid-1.6.2p1 work while @conflict
ossp-uuid-=1.6.2 doesnt?
Ciao,
Kili
On Sun, Jul 31, 2011 at 04:46:43PM +0200, Matthias Kilian wrote:
On Sun, Jul 31, 2011 at 04:36:00PM +0200, Jasper Lievisse Adriaanse wrote:
Have it your way if this works. I've gone blind on those markers already..
Sure, but why does @conflict ossp-uuid-1.6.2p1 work while @conflict
Hi,
During upgrade on one of the machines I got following error:
Collision in e2fsprogs-1.41.4p4-e2fsprogs-1.41.4p5: the following files
already exist
/usr/local/lib/pkgconfig/uuid.pc (ossp-uuid-1.6.2)
Update candidates: e2fsprogs-1.41.4p4 - e2fsprogs-1.41.4p5 ()
I think it should
