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/2011-June/005407.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-1be510f9529cb082f802408b472a77d074b394c0.tar archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2 archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz archives-1be510f9529cb082f802408b472a77d074b394c0.zip | |
Diffstat (limited to 'zarb-ml/mageia-dev/2011-June/005407.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-June/005407.html | 190 |
1 files changed, 190 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-June/005407.html b/zarb-ml/mageia-dev/2011-June/005407.html new file mode 100644 index 000000000..cff41daab --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005407.html @@ -0,0 +1,190 @@ +<!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=%3C201106111655.00878.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="005404.html"> + <LINK REL="Next" HREF="005409.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Missing packages in Mageia 1. How to backport?</H1> + <B>Samuel Verschelde</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=%3C201106111655.00878.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] Missing packages in Mageia 1. How to backport?">stormi at laposte.net + </A><BR> + <I>Sat Jun 11 16:55:00 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="005404.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI>Next message: <A HREF="005409.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5407">[ date ]</a> + <a href="thread.html#5407">[ thread ]</a> + <a href="subject.html#5407">[ subject ]</a> + <a href="author.html#5407">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le samedi 11 juin 2011 14:26:19, Maarten Vanraes a écrit : +><i> Op zaterdag 11 juni 2011 13:14:29 schreef Samuel Verschelde: +</I>><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 +</I>><i> > > > few people want everything to be newer ( ie, now one run backports +</I>><i> > > > as a update media, I think ). So as much as I am against asking to +</I>><i> > > > users questions, we must show them the choice somewhere, in a non +</I>><i> > > > obstrusive 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 +</I>><i> > > to install a new VM with mga1, update it, and install only those +</I>><i> > > 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 +</I>><i> > is 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>><i> +</I>><i> imho this creates more work for packagers or qa team to support backports, +</I>><i> i'm not really in favor of this solution +</I> +So it someone has a problem with a package you backported and reports it in +bugzilla, you'll answer "not supported" and close the door ? Then we have not +a single chance to have users accept to use backports rather than ask for a +rolling release (supposing that we want to stay with stable releases model, +which hasn't been decided yet). + +In my opinion, a backport must be either supported or not exist. Even in +Mandriva, where everybody keep saying "backports ain't supported", usually +people try to solve the problems caused by backports. + +However, the level of support can be different between backports and updates, +as I said in my previous message. The differences are yet to define, but here +are some I see : +- when a critical bug in a backport exists, you can simply update to a newer +version and see if it's solved +- if the program already is in its the latest version and has an upstream bug, +you can answer "report the bug upstream" and stop there until upstream solves +the bug. For packages in release or updates, ideally you have to try to help +fixing it or work it around because the bug is considered part of the whole +distribution. + +Best regards + +Samuel +-------------- next part -------------- +An HTML attachment was scrubbed... +URL: </pipermail/mageia-dev/attachments/20110611/e0b9ab4a/attachment.html> +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="005404.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI>Next message: <A HREF="005409.html">[Mageia-dev] Missing packages in Mageia 1. How to backport? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#5407">[ date ]</a> + <a href="thread.html#5407">[ thread ]</a> + <a href="subject.html#5407">[ subject ]</a> + <a href="author.html#5407">[ 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> |