diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-dev/2012-June/016743.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016743.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-June/016743.html | 169 |
1 files changed, 169 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016743.html b/zarb-ml/mageia-dev/2012-June/016743.html new file mode 100644 index 000000000..41d9d5f4f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016743.html @@ -0,0 +1,169 @@ +<!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=%3C5466876b00bd21c39b01016287970494.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="016738.html"> + <LINK REL="Next" HREF="016745.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=%3C5466876b00bd21c39b01016287970494.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>Fri Jun 22 12:42:46 CEST 2012</I> + <P><UL> + <LI>Previous message: <A HREF="016738.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media +</A></li> + <LI>Next message: <A HREF="016745.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#16743">[ date ]</a> + <a href="thread.html#16743">[ thread ]</a> + <a href="subject.html#16743">[ subject ]</a> + <a href="author.html#16743">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>><i> On 21/06/12 22:01, AL13N wrote: +</I>[...] +><i> All this assumes that backport media will be treated as a normal update +</I>><i> media. That is certainly not my impression. My impression of backports +</I>><i> are being able to install a new blender for example, not having a system +</I>><i> where backports are just another update media and replace everything +</I>><i> available. The QA task for that scenario would be ridiculously huge. If +</I>><i> you want to have backports which go any further than backports testing +</I>><i> then you seriously need to rethink this idea. +</I>[...] +><i> The aim of fixing this bug is to reduce the complexity and extra +</I>><i> workload of working around it for QA. This assumption and solution +</I>><i> actually has the opposite effect, dramatically increasing the complexity +</I>><i> and workload. As I've explained, that is simply not possible if we want +</I>><i> to release timely updates. +</I>><i> +</I>><i> I hope this makes the situation clearer. There is a workable solution +</I>><i> but I'm afraid it isn't this one, for the reasons given above. +</I> +No offense, but i think it didn't make myself clear and as a result i +think you are not understanding this properly. + +my proposal is actually to make sure QA only needs to test twice for each +package (both updates and backports). + +"My impression of backports are being able to install a new blender for +example" + +this exact idea that you have, will make QA testing unworkable. let me try +to explain: + +suppose that only blender and firefox and gimp and java is backported. any +kind of combination would have to be tested to be able to support +backports: +- testing backports blender on a system without backports +- testing backports blender on a system with backports and only firefox +installed from backports +- testing backports blender on a system with backports and only gimp +installed from backports +- testing backports blender on a system with backports and only java +installed from backports +- testing backports blender on a system with backports and both firefox +and gimp installed from backports +- testing backports blender on a system with backports and both firefox +and java installed from backports +- testing backports blender on a system with backports and both gimp and +java installed from backports +- testing backports blender on a system with backports and firefox and +gimp and java installed from backports + +This for each arch: thus 16 tests. + +This amount of tests is a direct result of trying to support backports +when you can have any single backported package installed, that you want. + +you'd have to test this because in case of new dependencies, it could even +conflict during installation!!! + +and the biggest problem is that the same problem exists when having an +update that has a new dependency. Thus, the same tests should be done for +updates as well. + +all of this, just to support backports being cherry-picked. + +I'd rather have unsupported backports. + +My proposal (B2) is a compromise that has only supporting backports if you +use it for everything, and has only 2 tests per package. THE SAME AS WE DO +NOW! + +to repeat: i'm trying to propose a solution that makes QA have NO INCREASE +of workload. + +the only extra point, is that for validating: + +right now, you're asking if it's tested for both i586 and x86_64. + +for B2, this is still the same, except that i586 should have backports +disabled and x86_64 have backports enabled. + +I hope this is clearer now +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="016738.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media +</A></li> + <LI>Next message: <A HREF="016745.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#16743">[ date ]</a> + <a href="thread.html#16743">[ thread ]</a> + <a href="subject.html#16743">[ subject ]</a> + <a href="author.html#16743">[ 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> |