<!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>><i> 21.06.2012 14:30, Maarten Vanraes kirjutas:
</I>[...]
><i> Well, AFAIK there is still no stance on backports policy (are we
</I>><i> backporting from cauldron
</I>><i> (n) to n-2 or not - if we do, we break upgradability here!).
</I>><i> Cherry-picking backports is
</I>><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.
><i> And i don't think that the packager who is creating update should
</I>><i> check all possible backports.
</I>
no, since cherrypicking is not supported, only needs to be test with
backports and without.
><i> What if that backport comes into play later? When the update is
</I>><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.
><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.
><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>