diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2012-January/011263.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2012-January/011263.html | 135 |
1 files changed, 135 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-January/011263.html b/zarb-ml/mageia-dev/2012-January/011263.html new file mode 100644 index 000000000..404f7e573 --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/011263.html @@ -0,0 +1,135 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] please stop doing "bugs" for updating magia 1 + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20please%20stop%20doing%20%22bugs%22%20for%20updating%20magia%201&In-Reply-To=%3CCAPZ-hqQ7%3DXWTZTLMpx-PeE_Vwn_EhFOOrwpe2CNg28iXArkXEA%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="011258.html"> + <LINK REL="Next" HREF="011294.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] please stop doing "bugs" for updating magia 1</H1> + <B>Juan Luis Baptiste</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20please%20stop%20doing%20%22bugs%22%20for%20updating%20magia%201&In-Reply-To=%3CCAPZ-hqQ7%3DXWTZTLMpx-PeE_Vwn_EhFOOrwpe2CNg28iXArkXEA%40mail.gmail.com%3E" + TITLE="[Mageia-dev] please stop doing "bugs" for updating magia 1">juancho at mageia.org + </A><BR> + <I>Wed Jan 11 22:09:56 CET 2012</I> + <P><UL> + <LI>Previous message: <A HREF="011258.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI>Next message: <A HREF="011294.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#11263">[ date ]</a> + <a href="thread.html#11263">[ thread ]</a> + <a href="subject.html#11263">[ subject ]</a> + <a href="author.html#11263">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, Jan 11, 2012 at 3:53 PM, Christian Lohmaier +<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">lohmaier+mageia at googlemail.com</A>> wrote: +><i> adding patches to the packages and releasing them instead of waiting +</I>><i> for a new upstream release is different from having the policy to +</I>><i> stick with whatever release was used when releasing the distro and +</I>><i> then only apply fixes via patches. +</I>><i> +</I> +Some times you can't wait for an upstream release, think for example +of a security update. Also not all projects do bugfix only releases, +but include new features as well so per our policy, we can't update to +that version and that's when we have to cherry pick updates to apply +to package in the stable version of mga. The problem seems to be that +that isn't clear on the policy. + +><i> I'm not saying that you must not use patches to fix bugs. There are +</I>><i> cases where a bug is homegrown/specific to the distro and thus not +</I>><i> suitable for fixing upstream, there are cases where development cylce +</I>><i> is too slow/it is not sensible to wait for upstream. +</I>><i> +</I> +Exactly, plus the other case I just said. + +><i> It is not a question whether it is possible. It is a question whether +</I>><i> it makes sense in the first place. +</I>><i> And no doubt it creates a lot more work for package maintainers. +</I>><i> Both for initially hunting for the commit that fixes the bug, and +</I>><i> later when patches conflict, and later when a package is updated to a +</I>><i> new release. +</I> +As I said, no one is talking about picking up a fix if there's a bug +fix only release, it's for when it isn't and we need to reduce the +chance of regressions by taking the modifications that *exactly* fix +that bug. + +><i> +</I>>><i> Because as I said earlier, we backport the "commit" that fixes that +</I>>><i> single issue, +</I>><i> +</I>><i> Every change, also those that introduce a regression is a "commit". +</I>><i> So implicitly you're saying that you will only fix the "easy" bugs, +</I>><i> but anything that involves more than touching 10lines of code will not +</I>><i> be chosen, since it might introduce regressions. +</I>><i> +</I> +No, I'm saying that we will look for the commit that fixes the issue +in question and not anything else, it doesn't matter if the fix is +one, 10, 50 lines and/or touches 1, 2 or 10 files. + +And again, if there's a bugfix *only* release available when we are +working on a bug, or we know that there will be one soon, then we can +update to that version. In the other cases we have to go the long +route and patch the packges with individual fixes. + +-- +Juancho +</PRE> + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="011258.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI>Next message: <A HREF="011294.html">[Mageia-dev] please stop doing "bugs" for updating magia 1 +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#11263">[ date ]</a> + <a href="thread.html#11263">[ thread ]</a> + <a href="subject.html#11263">[ subject ]</a> + <a href="author.html#11263">[ 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> |