blob: 694a12a75730e3830b3ef0f6296bc89a852bcd15 (
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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Backports Summary
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEAD94F.3030505%40linux.it%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="016896.html">
<LINK REL="Next" HREF="016889.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Backports Summary</H1>
<B>Angelo Naselli</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Backports%20Summary&In-Reply-To=%3C4FEAD94F.3030505%40linux.it%3E"
TITLE="[Mageia-dev] Backports Summary">anaselli at linux.it
</A><BR>
<I>Wed Jun 27 11:58:39 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="016896.html">[Mageia-dev] Backports Summary
</A></li>
<LI>Next message: <A HREF="016889.html">[Mageia-dev] Backports Summary
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16888">[ date ]</a>
<a href="thread.html#16888">[ thread ]</a>
<a href="subject.html#16888">[ subject ]</a>
<a href="author.html#16888">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Il 27/06/2012 10:23, Thomas Backlund ha scritto:
><i> It's not supposed to be flagged as an update repo as that would
</I>><i> make it upgrade all packages it find in the system with matching
</I>><i> backports packages.
</I>Why not? Just let the user to decide, who does want it, just enable it.
Who wants cherry-peeking it just enable the bp repo and disable it
after.
The real problem is how to make people understanding that a bp has
been released as bug or security fixing of an already backported
package... No problems if you enable bp as updates, while you
have problems if you cherry-peek a package...
Angelo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - <A HREF="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</A>
iEYEARECAAYFAk/q2U8ACgkQqEs9DA4DquCFawCdHTQXC0L4cxQCgEo8a1relOyc
ZEIAnibkaY/4PAlvpHmfsKCyu2LECDzZ
=pf4G
-----END PGP SIGNATURE-----
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="016896.html">[Mageia-dev] Backports Summary
</A></li>
<LI>Next message: <A HREF="016889.html">[Mageia-dev] Backports Summary
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#16888">[ date ]</a>
<a href="thread.html#16888">[ thread ]</a>
<a href="subject.html#16888">[ subject ]</a>
<a href="author.html#16888">[ 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>
|
