summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016700.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/2012-June/016700.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/2012-June/016700.html')
-rw-r--r--zarb-ml/mageia-dev/2012-June/016700.html131
1 files changed, 131 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016700.html b/zarb-ml/mageia-dev/2012-June/016700.html
new file mode 100644
index 000000000..9483f12d0
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-June/016700.html
@@ -0,0 +1,131 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3C7f16133a9e6245ef41683fbf1e6d1784.squirrel%40mail.rmail.be%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="016697.html">
+ <LINK REL="Next" HREF="016706.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1>
+ <B>AL13N</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3C7f16133a9e6245ef41683fbf1e6d1784.squirrel%40mail.rmail.be%3E"
+ TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">alien at rmail.be
+ </A><BR>
+ <I>Thu Jun 21 14:28:40 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="016697.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI>Next message: <A HREF="016706.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16700">[ date ]</a>
+ <a href="thread.html#16700">[ thread ]</a>
+ <a href="subject.html#16700">[ subject ]</a>
+ <a href="author.html#16700">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>&gt;<i> 21.06.2012 14:30, Maarten Vanraes kirjutas:
+</I>[...]
+&gt;<i> Well, AFAIK there is still no stance on backports policy (are we
+</I>&gt;<i> backporting from cauldron
+</I>&gt;<i> (n) to n-2 or not - if we do, we break upgradability here!).
+</I>&gt;<i> Cherry-picking backports is
+</I>&gt;<i> needed.
+</I>
+This is true, but has to be solved anyway, no bearing on this problem. and
+cherry-picking should not be needed(since it's not supported), so that's a
+different problem.
+
+&gt;<i> And i don't think that the packager who is creating update should
+</I>&gt;<i> check all possible backports.
+</I>
+no, since cherrypicking is not supported, only needs to be test with
+backports and without.
+
+&gt;<i> What if that backport comes into play later? When the update is
+</I>&gt;<i> already released?
+</I>
+then the backport packager needs to make sure his backport works, and
+since he's part of QA (according to policy), he'll need to test with and
+without backports.
+
+&gt;<i> I still think that backports should not be used during updates.
+</I>
+you're free to think so, but with your skills, i'm sure you can make that
+easily happen, like keeping backports disabled, unless you need something.
+
+&gt;<i> And it doesn't make QA work any easier here.
+</I>[...]
+
+actually, i think it is easier for QA, because cherry-picking cannot be
+supported, and the backport packager is responsible for his backport
+testing. for updates, only needs to be tested with or without backports.
+so, since they need 2 tests anyway (i586 and x86_64), if one of them is
+with backports enabled and the other is without, it doesn't need any more
+testing than before.
+
+
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="016697.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI>Next message: <A HREF="016706.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16700">[ date ]</a>
+ <a href="thread.html#16700">[ thread ]</a>
+ <a href="subject.html#16700">[ subject ]</a>
+ <a href="author.html#16700">[ 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>