diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010251.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010251.html | 203 |
1 files changed, 203 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010251.html b/zarb-ml/mageia-dev/2011-December/010251.html new file mode 100644 index 000000000..33993836f --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010251.html @@ -0,0 +1,203 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] RFC: Opening Backports (once again...) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20Opening%20Backports%20%28once%20again...%29&In-Reply-To=%3C4EDFB91C.1050105%40mageia.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="010221.html"> + <LINK REL="Next" HREF="010253.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] RFC: Opening Backports (once again...)</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20RFC%3A%20Opening%20Backports%20%28once%20again...%29&In-Reply-To=%3C4EDFB91C.1050105%40mageia.org%3E" + TITLE="[Mageia-dev] RFC: Opening Backports (once again...)">tmb at mageia.org + </A><BR> + <I>Wed Dec 7 20:06:04 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010221.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI>Next message: <A HREF="010253.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10251">[ date ]</a> + <a href="thread.html#10251">[ thread ]</a> + <a href="subject.html#10251">[ subject ]</a> + <a href="author.html#10251">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Anssi Hannula skrev 6.12.2011 01:29: +><i> On 06.12.2011 00:56, Thomas Backlund wrote: +</I>>><i> +</I>>><i> Now, +</I>>><i> +</I>>><i> here comes the question about backports once again. +</I>>><i> +</I>>><i> We are now 6+ months into Mageia 1, and we are nowhere closer to opening +</I>>><i> backports that we were at Mageia 1 release time. +</I>>><i> +</I>>><i> Because of that there are 3rdparty repos popping up everywhere..., +</I>>><i> something we hoped to avoid atleast partly when starting this project. +</I>>><i> +</I>>><i> And at current rate we will probably release Mageia "infinity" +</I>>><i> before backports is opened. +</I>>><i> +</I>>><i> +</I>>><i> It has been delayed because of needed infrastructure changes, +</I>>><i> something no-one have had time to do so far... +</I>>><i> +</I>>><i> I know there is "only some coding missing" and "someone should +</I>>><i> do it", buth truthfully there are only a few that knows the +</I>>><i> code used in the buildsystem enough to actually make it happend, +</I>>><i> and they are already othervise busy or overloaded... +</I>>><i> (this is no rant against them, as all here are using their +</I>>><i> personal free time to help out) +</I>><i> +</I>><i> The biggest problem for me is that it is really difficult to test any +</I>><i> changes, one'd need a mockup of the whole buildsystem... and I don't +</I>><i> want to propose any patches blind :) +</I>><i> +</I>>><i> And to be honest I dont see that changing anytime soon... +</I>>><i> +</I>>><i> +</I>>><i> So here is a suggestion to get some value to our endusers: +</I>>><i> +</I>>><i> we add a backports branch on svn +</I>>><i> +</I>>><i> So packages for backports would use: +</I>>><i> +</I>>><i> svn.mageia.org/packages/backports/1/<package>/{current,pristine,releases} +</I>>><i> +</I>>><i> and allow that to be used for backports. +</I>>><i> +</I>>><i> Using a separate branch is also a cleaner way of providing +</I>>><i> backports, and makes it easy to separate changes needed only +</I>>><i> for Cauldron (or backports). +</I>><i> +</I>><i> Hm, how does this help with enabling backports (i.e. compared to simply +</I>><i> using cauldron repo)? +</I>><i> +</I> +It was suggested to prevent direct submissions from cauldron as +current BS is not capable of blocking cauldron -> updates_testing +if we add cauldron to supported url + +So a separate backports branch would be created to "work around" this. +(yes I know you could do svn cp and then submit, but atleast it would + prevent submissions done by mistake) + +And if we want to extend the checks, maybe mgarepo could be updated to +only allow submission to backports_testing from backports branch until +server side checking is in place. (the same "connection" could probably +be done between updates_testing and updates too) + + +><i> Anyway, would the above branch work like this: +</I>><i> +</I>><i> e.g. lets imagine I want to, in order: +</I>><i> 1. provide foobar 1.1 to backports. +</I>><i> 2. cauldron foobar upgraded to 1.2, some patches added, some removed, +</I>><i> and other changes +</I>><i> 3. provide foobar 1.2 to backports +</I>><i> 4. 1.3 to cauldron and backports +</I>><i> +</I>><i> To backport foobar 1.1, I guess I'd simply do +</I>><i> svn copy svn+<A HREF="ssh://svn.mageia.org/svn/packages/cauldron/foobar">ssh://svn.mageia.org/svn/packages/cauldron/foobar</A> \ +</I>><i> svn+<A HREF="ssh://svn.mageia.org/svn/packages/backports/1/foobar">ssh://svn.mageia.org/svn/packages/backports/1/foobar</A> +</I>><i> and then the submit command. +</I>><i> +</I>><i> When time comes to provide foobar 1.2 to backports, the options are: +</I>><i> Option 1: +</I>><i> svn del svn+<A HREF="ssh://svn.mageia.org/svn/packages/backports/1/foobar">ssh://svn.mageia.org/svn/packages/backports/1/foobar</A> +</I>><i> svn copy svn+<A HREF="ssh://svn.mageia.org/svn/packages/cauldron/foobar">ssh://svn.mageia.org/svn/packages/cauldron/foobar</A> \ +</I>><i> svn+<A HREF="ssh://svn.mageia.org/svn/packages/backports/1/foobar">ssh://svn.mageia.org/svn/packages/backports/1/foobar</A> +</I>><i> and submit. Changelog is the same as in cauldron. +</I>><i> +</I>><i> Option 2: +</I>><i> svn checkout \ +</I>><i> svn+<A HREF="ssh://svn.mageia.org/svn/packages/backports/1/foobar/current">ssh://svn.mageia.org/svn/packages/backports/1/foobar/current</A> \ +</I>><i> foobar +</I>><i> cd foobar&& svn merge -r prevrev:HEAD \ +</I>><i> svn+<A HREF="ssh://svn.mageia.org/svn/packages/cauldron/foobar/current">ssh://svn.mageia.org/svn/packages/cauldron/foobar/current</A> +</I>><i> svn commit +</I>><i> # copy all the log entries from the cauldron interval to the log msg +</I>><i> and submit. +</I>><i> Note: results in broken changelogs unless one does manual +</I>><i> markreleases, but changelogs are already broken both in mga1 updates +</I>><i> and in cauldron (youri issue [1]). This is more notable here, though, +</I>><i> as backports happen generally more often multiple times than updates. +</I>><i> +</I>><i> Repeat with 1.3. +</I>><i> +</I>><i> Correct? +</I>><i> +</I> +I guess this is up to the maintainer how he/she wants to maintain the +backports of his package as it can also be Option 3: maintain backports +branch separately (depending on package). + +For example, for me I'd like to provide kernel-rt-3.0.x as backports, +but would probably not provide 3.2.x at all for Mageia 1. + +(sidenote, kernel-rt is a little tricky here as it was available as + 2.6.33 series in 2010.2, so it could go to updates. but since it + would also need backported nvidia/fglrx (if they work that is), + and the /proc/net/route info changed in 2.6.39 so it would "break" + network detection too, and version 3.* could break some scripts + checking for 2.*, so I'd rather submit it as a backport.) + +><i> [1] <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2633">https://bugs.mageia.org/show_bug.cgi?id=2633</A> +</I>><i> +</I> +Yeah, this is another thing that needs to be fixed regardless of +what we do with backports. for now we have just disabled markrel +for updates so it does not mess up the changelogs even more. + +-- +Thomas +</PRE> + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010221.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI>Next message: <A HREF="010253.html">[Mageia-dev] RFC: Opening Backports (once again...) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10251">[ date ]</a> + <a href="thread.html#10251">[ thread ]</a> + <a href="subject.html#10251">[ subject ]</a> + <a href="author.html#10251">[ 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> |