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/007904.html | 78 +++++++++++++++++++++++++++ 1 file changed, 78 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-September/007904.html (limited to 'zarb-ml/mageia-dev/2011-September/007904.html') diff --git a/zarb-ml/mageia-dev/2011-September/007904.html b/zarb-ml/mageia-dev/2011-September/007904.html new file mode 100644 index 000000000..f49dc7786 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-September/007904.html @@ -0,0 +1,78 @@ + + + + [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:29:21 CEST 2011 +

+
+ +
On Thu, 08 Sep 2011 11:32:39 -0400, Samuel Verschelde <stormi at laposte.net> wrote:
+
+> Maybe my question was not clear : qt4-database-plugin-
+> sqlite-4.7.3-1.mga1.i586.rpm is needed *as a new requirement* of another
+> updated package. Do we link only qt4-database-plugin-
+> sqlite-4.7.3-1.mga1.i586.rpm from Core Release to Updates, or do we link all
+> packages from its SRPM, which is qt4 ?
+>
+> Said otherwise : must we keep a coherence between RPMs and SRPMs in Core
+> Updates ?
+
+If we don't keep the coherence, the procedure for pushing from Updates Testing
+to Updates will have to be changed as well.
+
+Currently the sysadmin team is given a list of srpm packages to push.
+
+ + + + + + + + + + +
+

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