summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-September/007931.html
diff options
context:
space:
mode:
authorNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
committerNicolas Vigier <boklm@mageia.org>2013-04-14 13:46:12 +0000
commit1be510f9529cb082f802408b472a77d074b394c0 (patch)
treeb175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2011-September/007931.html
parentfa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff)
downloadarchives-master.tar
archives-master.tar.gz
archives-master.tar.bz2
archives-master.tar.xz
archives-master.zip
Add zarb MLs html archivesHEADmaster
Diffstat (limited to 'zarb-ml/mageia-dev/2011-September/007931.html')
-rw-r--r--zarb-ml/mageia-dev/2011-September/007931.html93
1 files changed, 93 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-September/007931.html b/zarb-ml/mageia-dev/2011-September/007931.html
new file mode 100644
index 000000000..67937f58b
--- /dev/null
+++ b/zarb-ml/mageia-dev/2011-September/007931.html
@@ -0,0 +1,93 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Copying dependencies from Release to Updates Testing
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Copying%20dependencies%20from%20Release%20to%20Updates%0A%09Testing&In-Reply-To=%3C201109091056.03735.stormi%40laposte.net%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="007904.html">
+ <LINK REL="Next" HREF="007903.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Copying dependencies from Release to Updates Testing</H1>
+ <B>Samuel Verschelde</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Copying%20dependencies%20from%20Release%20to%20Updates%0A%09Testing&In-Reply-To=%3C201109091056.03735.stormi%40laposte.net%3E"
+ TITLE="[Mageia-dev] Copying dependencies from Release to Updates Testing">stormi at laposte.net
+ </A><BR>
+ <I>Fri Sep 9 10:56:03 CEST 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="007904.html">[Mageia-dev] Copying dependencies from Release to Updates Testing
+</A></li>
+ <LI>Next message: <A HREF="007903.html">[Mageia-dev] Copying dependencies from Release to Updates Testing
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7931">[ date ]</a>
+ <a href="thread.html#7931">[ thread ]</a>
+ <a href="subject.html#7931">[ subject ]</a>
+ <a href="author.html#7931">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le vendredi 9 septembre 2011 04:29:21, David W. Hodgins a &#233;crit :
+&gt;<i> On Thu, 08 Sep 2011 11:32:39 -0400, Samuel Verschelde &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>&gt;
+</I>wrote:
+&gt;<i> &gt; Maybe my question was not clear : qt4-database-plugin-
+</I>&gt;<i> &gt; sqlite-4.7.3-1.mga1.i586.rpm is needed *as a new requirement* of another
+</I>&gt;<i> &gt; updated package. Do we link only qt4-database-plugin-
+</I>&gt;<i> &gt; sqlite-4.7.3-1.mga1.i586.rpm from Core Release to Updates, or do we link
+</I>&gt;<i> &gt; all packages from its SRPM, which is qt4 ?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; Said otherwise : must we keep a coherence between RPMs and SRPMs in Core
+</I>&gt;<i> &gt; Updates ?
+</I>&gt;<i>
+</I>&gt;<i> If we don't keep the coherence, the procedure for pushing from Updates
+</I>&gt;<i> Testing to Updates will have to be changed as well.
+</I>&gt;<i>
+</I>&gt;<i> Currently the sysadmin team is given a list of srpm packages to push.
+</I>
+In fact, if we don't keep the coherence, we are going to have mixed
+situations. The scripts used to move updates from Updates Testing to Updates
+will have to :
+- rely on the SRPMs for &quot;built&quot; updates (I'm calling &quot;built&quot; updates packages
+that went through the build system from the 1/updates branch)
+- rely on a by arch RPM list for &quot;copied&quot; dependencies (as package name can
+depend on the arch)
+
+Also, I don't know what will happen if a &quot;copied&quot; dependency gets a real
+update in the future. The scripts should recognize this situation, remove the
+copied deps and add the 'built' ones (more complexity in move scripts).
+
+This all gets complicated, maybe more than fixing MageiaUpdate in the end :)
+
+Samuel
+</PRE>
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="007904.html">[Mageia-dev] Copying dependencies from Release to Updates Testing
+</A></li>
+ <LI>Next message: <A HREF="007903.html">[Mageia-dev] Copying dependencies from Release to Updates Testing
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#7931">[ date ]</a>
+ <a href="thread.html#7931">[ thread ]</a>
+ <a href="subject.html#7931">[ subject ]</a>
+ <a href="author.html#7931">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>