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/2011-September/007903.html | 82 +++++++++++++++++++++++++++ 1 file changed, 82 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-September/007903.html (limited to 'zarb-ml/mageia-dev/2011-September/007903.html') diff --git a/zarb-ml/mageia-dev/2011-September/007903.html b/zarb-ml/mageia-dev/2011-September/007903.html new file mode 100644 index 000000000..cb088f5b0 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/007903.html @@ -0,0 +1,82 @@ + + + + [Mageia-dev] Copying dependencies from Release to Updates Testing + + + + + + + + + +

[Mageia-dev] Copying dependencies from Release to Updates Testing

+ David W. Hodgins + davidwhodgins at gmail.com +
+ Fri Sep 9 04:23:39 CEST 2011 +

+
+ +
On Thu, 08 Sep 2011 08:24:38 -0400, Thierry Vignaud <thierry.vignaud at gmail.com> wrote:
+
+> No that would be only the *new requirements* of the updated package.
+> Eg: if amarok doesn't with XYZ devices work because we forgot to link it
+> with libXYZ, we should only copy libXYZ when uploading new amarok
+> package into updates
+
+That may not cover all of the cases.
+
+If a dependency from mandriva did not get updated in the upgrade,
+due to being required by a package missing from Mageia 1, and when
+the Mageia 1 package is created, it requires a newer version of the
+dependency, that is available in Core Release, that package will have
+to be linked as well.
+
+Ensuring we catch every case is going to be difficult.
+
+Regards, Dave Hodgins
+
+ + + + + + + + + + + +
+

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