blob: 52895e709fcb707d28f3939bda7ccd19aafc73a3 (
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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] mysql CVE's in mga1 => have it update to mariadb
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mysql%20CVE%27s%20in%20mga1%20%3D%3E%20have%20it%20update%20to%20mariadb&In-Reply-To=%3C201204131811.05189.alien%40rmail.be%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="014242.html">
<LINK REL="Next" HREF="014246.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] mysql CVE's in mga1 => have it update to mariadb</H1>
<B>Maarten Vanraes</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20mysql%20CVE%27s%20in%20mga1%20%3D%3E%20have%20it%20update%20to%20mariadb&In-Reply-To=%3C201204131811.05189.alien%40rmail.be%3E"
TITLE="[Mageia-dev] mysql CVE's in mga1 => have it update to mariadb">alien at rmail.be
</A><BR>
<I>Fri Apr 13 18:11:05 CEST 2012</I>
<P><UL>
<LI>Previous message: <A HREF="014242.html">[Mageia-dev] mysql CVE's in mga1 => have it update to mariadb
</A></li>
<LI>Next message: <A HREF="014246.html">[Mageia-dev] mysql CVE's in mga1 => have it update to mariadb
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#14245">[ date ]</a>
<a href="thread.html#14245">[ thread ]</a>
<a href="subject.html#14245">[ subject ]</a>
<a href="author.html#14245">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Op vrijdag 13 april 2012 13:12:08 schreef AL13N:
[....]
i guess most packagers want option 2 here.
i don't think this is a good idea in general and i was of the opinion that the
diff between migrating mysql 5.5.22 and mariadb 5.5.23 were quite the same...
nonetheless, the package naming difference could have effects on it on a stable
version, so i concede to this solution.
however, i'll note that mariadb likely contains extra bugfixes, which this
mysql 5.5.22 will not have.
i guess this is the step where this is more or less decided and some packager
steps in and does the actual work. any volunteers? perhaps that person can
also become maintainer of it?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="014242.html">[Mageia-dev] mysql CVE's in mga1 => have it update to mariadb
</A></li>
<LI>Next message: <A HREF="014246.html">[Mageia-dev] mysql CVE's in mga1 => have it update to mariadb
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#14245">[ date ]</a>
<a href="thread.html#14245">[ thread ]</a>
<a href="subject.html#14245">[ subject ]</a>
<a href="author.html#14245">[ 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>
|