[Mageia-dev] [changelog] [RPM] cauldron core/release evolution-3.5.3.1-1.mga3

Mon Jul 2 14:07:52 CEST 2012

On Mon, Jul 02, 2012 at 01:05:40PM +0100, Colin Guthrie wrote:
+> 'Twas brillig, and Christiaan Welvaart at 02/07/12 12:59 did gyre and
+> gimble:
+> > On Mon, 2 Jul 2012, Colin Guthrie wrote:
+> > 
+> >> 'Twas brillig, and Olav Vitters at 02/07/12 08:04 did gyre and gimble:
+> >>> On Sun, Jul 01, 2012 at 09:04:48PM -0400, Charles A Edwards wrote:
+> >>>> On Mon,  2 Jul 2012 01:07:39 +0200 (CEST)
+> >>>> ovitters wrote:
+> >>>>
+> >>>>> Name        : evolution                    Relocations: (not
+> >>>>> relocatable) Version     : 3.5.3.1                           Vendor:
+> >>>>> Mageia.Org Release     : 1.mga3                        Build Date:
+> >>>>> Mon Jul  2 00:55:38 2012 Install Date: (not installed)
+> >>>>> Build Host: ecosse.mageia.org Group       :
+> >>>>> Networking/Mail               Source RPM: (none) Size        :
+> >>>>> 12051792                         License: LGPLv2+ Signature   : (none)
+> >>>>> Packager    : ovitters <ovitters>
+> >>>>
+> >>>>
+> >>>> Installation failed:    lib64edataserverui4 is obsoleted by
+> >>>> (installed) lib64edataserverui1-3.4.3-1.mga3.x86_64
+> >>>
+> >>> New evolution-data-server should fix this (-4).
+> >>>
+> >>> Note: various evolution stuff doesn't build yet (-groupwise, -exchange,
+> >>> etc). No 3.5.3 version has been released for those yet, so not much I
+> >>> can do.
+> >>
+> >> The old library (lib[64]edataserverui1) will need to be nuked on the
+> >> server as it's obsoletes means that the current installation is borked,
+> >> likely leading to problems building other stuff too.
+> > 
+> > Isn't this whole mess caused by violation of the library policy? The
+> > previous packages should have been called: lib(64)edataserverui3.0_1
+> > and the new ones lib(64)edataserveruit3.0_4 . So any obsoletes of
+> > 'lib(64)edataserverui4' should not matter (and was likely added because
+> > of the same policy violation).
+> 
+> Yup seems so.
+
+Could someone fix the spec? Nobody maintains it atm.
+
+-- 
+Regards,
+Olav
+