diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005404.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005404.html | 161 |
1 files changed, 161 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005404.html b/zarb-ml/mageia-dev/2011-June/005404.html new file mode 100644 index 000000000..8cf5652ef --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005404.html @@ -0,0 +1,161 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Missing packages in Mageia 1. How to backport? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missing%20packages%20in%20Mageia%201.%20How%20to%20backport%3F&In-Reply-To=%3C201106111426.19913.maarten.vanraes%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="005400.html"> + <LINK REL="Next" HREF="005407.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Missing packages in Mageia 1. How to backport?</H1> + <B>Maarten Vanraes</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Missing%20packages%20in%20Mageia%201.%20How%20to%20backport%3F&In-Reply-To=%3C201106111426.19913.maarten.vanraes%40gmail.com%3E" + TITLE="[Mageia-dev] Missing packages in Mageia 1. How to backport?">maarten.vanraes at gmail.com + </A><BR> + <I>Sat Jun 11 14:26:19 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005400.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI>Next message: <A HREF="005407.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5404">[ date ]</a> + <a href="thread.html#5404">[ thread ]</a> + <a href="subject.html#5404">[ subject ]</a> + <a href="author.html#5404">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Op zaterdag 11 juni 2011 13:14:29 schreef Samuel Verschelde: +><i> Le samedi 11 juin 2011 12:06:55, Christiaan Welvaart a écrit : +</I>><i> > On Fri, 10 Jun 2011, Michael Scherer wrote: +</I>><i> > > We can agree that everybody want something newer for some rpms, but few +</I>><i> > > people want everything to be newer ( ie, now one run backports as a +</I>><i> > > update media, I think ). So as much as I am against asking to users +</I>><i> > > questions, we must show them the choice somewhere, in a non obstrusive +</I>><i> > > way. +</I>><i> > +</I>><i> > Maybe, but how would be "support" this? We must be able to reproduce a +</I>><i> > reported problem. This becomes complicated when we don't know what is +</I>><i> > installed on the user's system. A guideline for bug reporters is (or +</I>><i> > should be) "make sure you installed the latest updates". What would be +</I>><i> > the equivalent for backports? I'm afraid it should be "if you installed +</I>><i> > any backports, make sure you installed all backports that are relevant +</I>><i> > for your system". If someone has a problem with any other combination, +</I>><i> > the bug report might be rejected. How would QA even work when only +</I>><i> > selected packages are upgraded from backports, or integration testing: +</I>><i> > integration with what? +</I>><i> > +</I>><i> > So the only combinations we can support are: +</I>><i> > - release + updates +</I>><i> > - release + updates + backports +</I>><i> > +</I>><i> > More practical: for mga1 I have a VM that I can keep updated. For mga1 +</I>><i> > backports I can install another VM with backports enabled. But for bugs +</I>><i> > reported with only selected backports installed I suppose I would have to +</I>><i> > install a new VM with mga1, update it, and install only those backports - +</I>><i> +</I>><i> > for each bug report. But maybe I'm missing something, please explain. (: +</I>><i> If we suppose that either updates or backports are supported (with a +</I>><i> support level to be defined), the situation is simpler to me : a good +</I>><i> backport must work with all its dependencies coming from updates or +</I>><i> release OR it must explicitly require higher versions, found only in the +</I>><i> backports media and so automatically pulled. +</I>><i> +</I>><i> So I don't think that having picked up only certain backported packages is +</I>><i> a problem for the maintainer's support. Maybe I over-simplified the +</I>><i> situation, but I don't think it will be as complex as you say. +</I>><i> +</I>><i> Samuel +</I> +imho this creates more work for packagers or qa team to support backports, i'm +not really in favor of this solution +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005400.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI>Next message: <A HREF="005407.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5404">[ date ]</a> + <a href="thread.html#5404">[ thread ]</a> + <a href="subject.html#5404">[ subject ]</a> + <a href="author.html#5404">[ 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> |