Le lundi 14 février 2011, à 12:25 +0100, Stephan Kulow a écrit :
Am Sonntag, 13. Februar 2011 schrieb Vincent Untz:
Just to avoid some security-maintenance nightmares, I'm leaning towards staying with 1.3.x and updating libsoup.
I'm not worried about webkitgtk, but libsoup is a package that quite some other packages depend upon, so I wouldn't want that update right now.
Understood.
If it's required later for maintenance updates because 1.2 is no longer maintained we will have to live with it, but by then libsoup is at least no unstable release anymore.
Perhaps I should clarify what the prerelease freeze is for: it's for fixing the top 5% of bugs, not to push unstable libraries to add new bugs to prepare for possible future problems.
In general yes, but it also depends on how possible is "possible" ;-) In this case, based on my experience with webkit in the past 2-3 releases, I'm 99% sure it will happen, so it's something we'll have to deal with. There's still a choice to be made, though: 1.2.x and 1.3.x are not ABI compatible (the library has even a different name; 1.3.x is API compatible with 1.2.x, though). This means we can choose to use the current 1.3.10 for 11.4 and we can update to newer versions for security issues, or we stay with 1.2.x for the whole 11.4 lifecycle (or if we choose to update 1.3.x/1.4.x as a security update, we'll have to rebuild a dozen of other packages). FWIW, upstream just told me that the 1.2.x branch won't be actively maintained once 1.4.0 is out, which should occur in April. Based on this, I'd really like to avoid going back to 1.2.x... Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org