summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016421.html
blob: 61133188a648e7669c849d2510f3523887b6de63 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [Mageia-dev] Backports policy clarification (and discussion)
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3Cko7ja9-lc3.ln1%40psd.motzarella.org%3E">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="016335.html">
   <LINK REL="Next"  HREF="016420.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[Mageia-dev] Backports policy clarification (and discussion)</H1>
    <B>blind Pete</B> 
    <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20policy%20clarification%20%28and%20discussion%29&In-Reply-To=%3Cko7ja9-lc3.ln1%40psd.motzarella.org%3E"
       TITLE="[Mageia-dev] Backports policy clarification (and discussion)">0123peter at gmail.com
       </A><BR>
    <I>Tue Jun 12 09:29:56 CEST 2012</I>
    <P><UL>
        <LI>Previous message: <A HREF="016335.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
        <LI>Next message: <A HREF="016420.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16421">[ date ]</a>
              <a href="thread.html#16421">[ thread ]</a>
              <a href="subject.html#16421">[ subject ]</a>
              <a href="author.html#16421">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>Sander Lepik wrote:

&gt;<i> 09.06.2012 13:29, andre999 kirjutas:
</I>&gt;&gt;<i> OK.  To backport from Cauldron to mga1, we have to backport from Cauldron
</I>&gt;&gt;<i> to mga2, (bumping the revision in cauldron to ensure that is is higher),
</I>&gt;&gt;<i> then backport from mga2 to
</I>&gt;&gt;<i> mga1, ensuring that the revision is lower in mga1 than in mga2.    (e.g.
</I>&gt;&gt;<i> revision x.1 in
</I>&gt;&gt;<i> cauldron, x.0.1 in mga2, x.0.0.1 in mga1)  Pretty straight forward.
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> - Cherry-picking refers to the users' option to install a backport, which
</I>&gt;&gt;<i> has nothing to do with the packaging itself.
</I>&gt;&gt;<i>
</I>&gt;&gt;<i> - Ensure that upgrades never fail :  Properly packaged, there is no
</I>&gt;&gt;<i> reason why any available backports will not install properly, as long as
</I>&gt;&gt;<i> the tools are appropriately
</I>&gt;&gt;<i> adjusted.  Backports should install just as reliably as regular updates.
</I>&gt;&gt;<i> Of course, if a particular backport or update is not available, it won't
</I>&gt;&gt;<i> install. Packages requiring it should not install either, which may not
</I>&gt;&gt;<i> always be the case now. (This should be verified - for backports and
</I>&gt;&gt;<i> updates.)
</I>&gt;<i> I see backports as the way to get some new stuff from cauldron before
</I>&gt;<i> cauldron is fully stable. There is no point to backport from cauldron to
</I>&gt;<i> n-2 (mga1 at the moment). If the user wants so much newer stuff s/he
</I>&gt;<i> better upgrade to latest stable.
</I>&gt;<i> 
</I>&gt;<i> To not fail upgrade you must make sure that n-1 backports are not newer
</I>&gt;<i> than n +n's updates. You can't enable backports repo at upgrade time or it
</I>&gt;<i> would upgrade all possible packages from backports repo. I'm quite sure
</I>&gt;<i> most users don't want that to happen! Cherry-picking for me means that i
</I>&gt;<i> can upgrade some packages from backports and then disable the repo. After
</I>&gt;<i> that i'm still able to upgrade to fully stable next release (w/o
</I>&gt;<i> backports).
</I>
Create a key word &quot;cherry-picking&quot; for urpmi.cfg?  

&gt;<i> --
</I>&gt;<i> Sander
</I>
-- 
blind Pete
Sig goes here...  

</PRE>































<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="016335.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
	<LI>Next message: <A HREF="016420.html">[Mageia-dev] Backports policy clarification (and discussion)
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#16421">[ date ]</a>
              <a href="thread.html#16421">[ thread ]</a>
              <a href="subject.html#16421">[ subject ]</a>
              <a href="author.html#16421">[ 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>