From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-July/017069.html | 110 +++++++++++++++++++++++++++++++ 1 file changed, 110 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-July/017069.html (limited to 'zarb-ml/mageia-dev/2012-July/017069.html') diff --git a/zarb-ml/mageia-dev/2012-July/017069.html b/zarb-ml/mageia-dev/2012-July/017069.html new file mode 100644 index 000000000..4df78b01f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-July/017069.html @@ -0,0 +1,110 @@ + + + + [Mageia-dev] missing upload lib64edataserverui4-3.5.3.1-2.mga3 + + + + + + + + + +

[Mageia-dev] missing upload lib64edataserverui4-3.5.3.1-2.mga3

+ Thomas Backlund + tmb at mageia.org +
+ Sun Jul 1 21:48:40 CEST 2012 +

+
+ +
01.07.2012 22:44, Jani Välimaa skrev:
+> On 01.07.2012 22:37, Thomas Backlund wrote:
+>> 01.07.2012 22:33, Jani Välimaa skrev:
+>>> On 01.07.2012 22:20, Olav Vitters wrote:
+>>>> On Sun, Jul 01, 2012 at 08:41:15PM +0300, Jani Välimaa wrote:
+>>>>> I guess the .spec needs some cleaning as there's more unneeded
+>>>>> obsoletes/defines. E.g. 'Obsoletes: %oldlibname2006' obsoletes lib which
+>>>>> was available in mdv 2006.0.
+>>>>
+>>>> Only cleaned the Obsoletes thing for lib64edataserverui4. Still facing
+>>>> issues :-(
+>>>>
+>>>> Installation failed:    lib64edataserverui4 is obsoleted by (installed)
+>>>> lib64edataserverui1-3.4.3-1.mga3.x86_64
+>>>>
+>>>>
+>>>> How can I avoid that?
+>>>>
+>>>
+>>> I guess that's because the old obsoletes wasn't versioned. If the old
+>>> lib isn't needed by any other pkg, you could remove it first.
+>>>
+>>>
+>>
+>> Trouble is it will hit us during upgrade from mga2 to mga3.
+>>
+>> So I guess it need a versioned conflict to force the upgrade
+>>
+> 
+> Another possible solution would be an updated mga2 pkg to core/updates.
+> 
+
+Indeed, and with the planned GNOME updates for mga2, this can be fixed
+
+
+> However that doesn't fix the update problem if user doesn't update
+> his/hers mga2 up-to-date before ugrading to mga3.
+> 
+
+True, but most will probably jump on the update for mga2,
+for the rest we need to add a versioned conflict.
+
+--
+Thomas
+
+
+
+ + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1