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-August/018389.html | 72 ++++++++++++++++++++++++++++++ 1 file changed, 72 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-August/018389.html (limited to 'zarb-ml/mageia-dev/2012-August/018389.html') diff --git a/zarb-ml/mageia-dev/2012-August/018389.html b/zarb-ml/mageia-dev/2012-August/018389.html new file mode 100644 index 000000000..7da544ab0 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-August/018389.html @@ -0,0 +1,72 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release telepathy-kde-common-internals-0.5.0-1.mga3 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release telepathy-kde-common-internals-0.5.0-1.mga3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Aug 31 11:50:13 CEST 2012 +

+
+ +
On 31 August 2012 11:38, John Balcaen <mikala at mageia.org> wrote:
+>> mikala <mikala> 0.5.0-1.mga3:
+>> + Revision: 285939
+>> - use conflicts instead of obsoletes to allow update
+> [...]
+> Hello thierry (& others :p ),
+> Do you have any ideas why i'm forced to used a conflicts to ensure
+> upgrade of packages here ?
+> Some files where added in %{name} package but since thoses files are
+> noarch i moved them in a noarch package.
+> However from my local test it seems that a noarch package can't
+> obsolete an arch package
+> aka if i'm adding in the %{name}-core an obsoletes: %{name} < 0.5.0,
+> urpmi will prevent the upgrade due to files conflicts between
+> %{name}-0.4.0 & %{name}-core-0.5.0
+
+Always use both Conflicts & Obsoletes.
+
+ + +
+

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