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-January/011398.html | 102 ++++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-January/011398.html (limited to 'zarb-ml/mageia-dev/2012-January/011398.html') diff --git a/zarb-ml/mageia-dev/2012-January/011398.html b/zarb-ml/mageia-dev/2012-January/011398.html new file mode 100644 index 000000000..14d1a0f4e --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011398.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] mga1 tainted/updates has exact same x264 packages as mga1 tainted/release + + + + + + + + + +

[Mageia-dev] mga1 tainted/updates has exact same x264 packages as mga1 tainted/release

+ Thomas Backlund + tmb at mageia.org +
+ Mon Jan 16 14:53:27 CET 2012 +

+
+ +
Florian Hubold skrev 16.1.2012 15:46:
+> Just stumbled upon the fact that mga1 tainted/updates carries the
+> exact same x264 packages as mga1 tainted/release. As we had
+> no x264 updates for mga1 so far (IIRC fwang only wanted to
+> push new x264 when trying to update ffmpeg for mga1 to 0.7)
+> can someone take a look how those packages got there and why?
+
+It's intended.
+
+It's a fallout of https://bugs.mageia.org/show_bug.cgi?id=2317
+
+MageiaUpdate only checks for deps in update media, so anytime a package
+in /updates requires something from /release we will hardlink it.
+
+
+>
+> And shouldn't they be removed from tainted/updates?
+
+
+Nope.
+
+But we must fix bug 2317 before Mageia 2 is out.
+
+--
+Thomas
+
+ + + + + + + + + + + + + + + + + + + + + + + + +
+

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