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/20101130/001536.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/20101130/001536.html')
| -rw-r--r-- | zarb-ml/mageia-dev/20101130/001536.html | 171 |
1 files changed, 171 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101130/001536.html b/zarb-ml/mageia-dev/20101130/001536.html new file mode 100644 index 000000000..809c8435b --- /dev/null +++ b/zarb-ml/mageia-dev/20101130/001536.html @@ -0,0 +1,171 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Mirror layout, round two + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF48BAD.1080302%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001533.html"> + <LINK REL="Next" HREF="001537.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Mirror layout, round two</H1> + <B>andre999</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Mirror%20layout%2C%20round%20two&In-Reply-To=%3C4CF48BAD.1080302%40laposte.net%3E" + TITLE="[Mageia-dev] Mirror layout, round two">andr55 at laposte.net + </A><BR> + <I>Tue Nov 30 06:29:17 CET 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001533.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001537.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1536">[ date ]</a> + <a href="thread.html#1536">[ thread ]</a> + <a href="subject.html#1536">[ subject ]</a> + <a href="author.html#1536">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Michael Scherer a écrit : +><i> Le lundi 29 novembre 2010 à 20:54 -0500, andre999 a écrit : +</I>><i> +</I>>><i> Yann Ciret a écrit : +</I>>><i> +</I>>><i> +</I>>>><i> I dislike the main/contrib separation in some case. +</I>>>><i> The first example is with Mozilla Thunderbird packages. Some extension +</I>>>><i> packages are in contrib. So each time thunderbird received security +</I>>>><i> update, the update cannot be installed because of non automatically +</I>>>><i> rebuild of his contrib package. And each time I see a bug report of user +</I>>>><i> asking a manual rebuilt. With only one core media, this situation will +</I>>>><i> disapear (I hope). +</I>>>><i> +</I>>>><i> +</I>>><i> Unlikely. This problem is not at all related to separate repositories. +</I>>><i> +</I>><i> It is. It is exactly related to the fact that thunderbird is supported, +</I>><i> and that extension are not despites depending on it. +</I>><i> +</I>In this case it is evident that you don't understand how extensions work +with mozilla products. Thunderbird will function correctly with no +extensions installed. So why should any extension block the update of +Thunderbird ? +Additionally, modules installed will continue to work as long as the +major version doesn't change. (Actually slightly more complicated.) +In some cases one won't be able to newly install a module because a +config file inside the module - equivalent to the spec file in rpm +packages - hasn't been updated for compatible versions. (In fact, the +versions were probably improperly specified.) But installed modules +will continue to function. +It is possible that the packager did not realise this - or for whatever +reason did not properly set up a spec file - but this issue has nothing +at all to do with separate sets of repositories. + +><i> That precisely because we tell "security and bugfixes occurs only on +</I>><i> main" that contribs got broken, since the security team do not care to +</I>><i> not break contribs packages. +</I>><i> +</I>The crux of this problem is that core (in the general sense) packages +are dependant on packages that are not recognized as core. +That again has nothing to do with repositories as such. + +>><i> Rather that one package was updated, and an optional installed module +</I>>><i> was not. +</I>>><i> The fact that the module is optional is the key point. +</I>>><i> The installer should be flexible enough to give a warning in this case, +</I>>><i> and ask if you wish to continue the installation. +</I>>><i> +</I>><i> So basically, you want a --nodeps ? +</I>><i> If there is a requires, there is usually a good reason. Engineering is +</I>><i> not randomly adding line to a file until it work. +</I>><i> +</I>How about better configured spec files ? +A better definition (in general) of core packages ? +A focus on ensuring that core packages are maintained ? +Basically my idea behind a core sandbox. +But if you have a better idea ... + +Just remember, eliminating a supported core breaks the sandbox. +So removing repositories does have secondary effects. +And they should be seriously considered and discussed by those proposing +to remove the repositories. + +>><i> As well, in the case of Thunderbird, it is almost certain that the +</I>>><i> installed module was in fact compatible with newer version of +</I>>><i> Thunderbird. (A security problem may directly impact Thunderbird or the +</I>>><i> module, but highly unlikely both packages.) +</I>>><i> Rpm tags should have been set so that Thunderbird would recognize that +</I>>><i> the module was appropriate in the newer version. +</I>>><i> +</I>><i> No. If there is stricter dependency, it is precisely because there is no +</I>><i> guarantee of any kind of ABI between thunderbird versions. The same goes +</I>><i> for firefox. +</I>><i> +</I>Overly restrictive compatibility specification is a very a common error +in Mozilla extension packaging. (It's mentioned in their development +guides.) +But the rpm packager should be knowledgable enough to recognize it. +But such errors do happen. +>><i> So in sum, this was probably only a packaging problem. Whatever the +</I>>><i> repository. +</I>>><i> +</I>><i> No. Not at all. +</I>><i> The problem is linked to the difference of support between main and +</I>><i> contribs. +</I>><i> +</I> +In this case, it is inappropriate packaging. +Other cases could be a difference of support. + +There is no reason that extensions should ever block the upgrade of +Thunderbird, unless when one passes from one major version to another. +In that case, the extension will have to be rewritten, a development +function. +(That has only happened a few times since the beginning of Mozilla.) + +The essence of our disagreement seems to be how to ensure that core +packages are properly supported. +My point is that a sandbox will facilitate proper support. Which would +be facilitated by keeping the 2 sets of free repositories. And +restricting what should be considered core. +We both know that Mandriva is moving in that direction. Evidently +recognising that they weren't restrictive enough in the past. + +Your focus is removing 1 of these repository sets, and thus the sandbox. +But I don't see your solution for giving priority to maintaining core +packages ? +These factors are undeniably linked. + +By the way, I'm very willing to be convinced. Just give me the logic. + +regards + +- André +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001533.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI>Next message: <A HREF="001537.html">[Mageia-dev] Mirror layout, round two +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1536">[ date ]</a> + <a href="thread.html#1536">[ thread ]</a> + <a href="subject.html#1536">[ subject ]</a> + <a href="author.html#1536">[ 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> |