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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] Re : Re : Re : E17 packaging
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Re%20%3A%20%20Re%20%3A%20%20Re%20%3A%20%20E17%20packaging&In-Reply-To=%3C1320080214.69242.YahooMailNeo%40web29501.mail.ird.yahoo.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="009240.html">
<LINK REL="Next" HREF="009258.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] Re : Re : Re : E17 packaging</H1>
<B>Philippe Reynes</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Re%20%3A%20%20Re%20%3A%20%20Re%20%3A%20%20E17%20packaging&In-Reply-To=%3C1320080214.69242.YahooMailNeo%40web29501.mail.ird.yahoo.com%3E"
TITLE="[Mageia-dev] Re : Re : Re : E17 packaging">tremyfr at yahoo.fr
</A><BR>
<I>Mon Oct 31 17:56:54 CET 2011</I>
<P><UL>
<LI>Previous message: <A HREF="009240.html">[Mageia-dev] Re : Re : E17 packaging
</A></li>
<LI>Next message: <A HREF="009258.html">[Mageia-dev] Re : Re : Re : E17 packaging
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9241">[ date ]</a>
<a href="thread.html#9241">[ thread ]</a>
<a href="subject.html#9241">[ subject ]</a>
<a href="author.html#9241">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>><i> Ok so there is a bug to fix in e17, what do you do ?
</I>
I report it to upstream team (on irc or on the ML)
><i> Or a security issue like the one I found ( and that should be fixed I
</I>><i> hope soon, after reporting it 3 times upstream ).
</I>
Same way, report it upstream.
If upstream don't fix a bug (or security issue), this bug isn't fixed.
unless packager become a dev and fix the bug himself.
><i> if the answer is "we ship a newer snapshot who requires to rebuild
</I>><i> everything regarding e17 because there is no guarantee of binary
</I>><i> stability ( ie, ABI wise ) and that will introduce unwanted changes",
</I>><i> then the problem is here. 
</I>
I was thinking about something like this.
><i> Unless the snapshot are bugfixes only ( and they are not ), that's a
</I>><i> problem. That's already annoying to have to do it for chrome, firefox
</I>><i> and thunderbird to not happily increase our burden with a whole desktop
</I>><i> environnement.
</I>
Without stable release, and upstream team doing fix release. I don't know
how to do manage package.
><i> So far, I have asked the question 3 times. No one answered at all.
</I>
I hope it's done this time.
><i> Also, please do not top post. 
</I>
Sorry, will try ...
So, yes, there isn't any way to manage bug/security issue in a very easy way
when upstream team don't provide stable tarball. So, what is the mageia 
policy in this case ? no packaging at all ? "private" packaging ?
regards,
trem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/mageia-dev/attachments/20111031/490a36ee/attachment.html>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="009240.html">[Mageia-dev] Re : Re : E17 packaging
</A></li>
<LI>Next message: <A HREF="009258.html">[Mageia-dev] Re : Re : Re : E17 packaging
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#9241">[ date ]</a>
<a href="thread.html#9241">[ thread ]</a>
<a href="subject.html#9241">[ subject ]</a>
<a href="author.html#9241">[ 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>
|
