1
2
3
|
<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"><div>> Ok so there is a bug to fix in e17, what do you do ?</div><div><br></div><div>I report it to upstream team (on irc or on the ML)<br><br>> Or a security issue like the one I found ( and that should be fixed I<br>> hope soon, after reporting it 3 times upstream ).</div><div><br></div><div>Same way, report it upstream.</div><div>If upstream don't fix a bug (or security issue), this bug isn't fixed.</div><div>unless packager become a dev and fix the bug himself.</div><div><br>> if the answer is "we ship a newer snapshot who requires to rebuild<br>> everything regarding e17 because there is no guarantee of binary<br>> stability ( ie, ABI wise ) and that will introduce unwanted changes",<br>> then the problem is here. </div><div><br></div><div>I was thinking about something like this.<br><br>> Unless
the snapshot are bugfixes only ( and they are not ), that's a<br>> problem. That's already annoying to have to do it for chrome, firefox<br>> and thunderbird to not happily increase our burden with a whole desktop<br>> environnement.</div><div><br></div><div>Without stable release, and upstream team doing fix release. I don't know</div><div>how to do manage package.</div><div><br>> So far, I have asked the question 3 times. No one answered at all.<br></div><div><br></div><div>I hope it's done this time.<br><br>> Also, please do not top post. <br><br>Sorry, will try ...</div><div><br></div><div><br></div><div>So, yes, there isn't any way to manage bug/security issue in a very easy way</div><div>when upstream team don't provide stable tarball. So, what is the mageia </div><div>policy in this case ? no packaging at all ? "private" packaging
?</div><div><br></div><div><br></div><div>regards,</div><div>trem<br></div><div><br></div></div></body></html>
|
