diff options
Diffstat (limited to 'zarb-ml/mageia-dev/20101009')
27 files changed, 2995 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/20101009/001049.html b/zarb-ml/mageia-dev/20101009/001049.html new file mode 100644 index 000000000..f5d4715f5 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001049.html @@ -0,0 +1,73 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF9794.8010509%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + + <LINK REL="Next" HREF="001050.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAF9794.8010509%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Sat Oct 9 00:13:40 CEST 2010</I> + <P><UL> + + <LI>Next message: <A HREF="001050.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1049">[ date ]</a> + <a href="thread.html#1049">[ thread ]</a> + <a href="subject.html#1049">[ subject ]</a> + <a href="author.html#1049">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré wrote: +><i> +</I>><i> Thanks. So this thread is to see if there were a possibility to +</I>><i> programme a more efficient roll-back option so that it would be more +</I>><i> "aware" of the previous "dependencies" needs for the previous version. +</I>><i> Having "double dependencies" is not so much of a problem, it is the +</I>><i> rollback to a previous version where the dependency confusion may +</I>><i> occur, and, ONLY, if an upgraded type of "dependency" thread had been +</I>><i> installed. (Sorry I may have used the wrong terms in the last sentence). +</I> +Well, sort of. It's not an issue of efficiency, but of convenience and +just making it possible to do without resorting to manual use of the rpm +command. + +The rpm command "knows" that a new version replacing the old version +supplies the same things that the old one did, so it will quietly allow +the upgrade. It will also do what we need, i.e. go the other way and +replace a newer version with an older one if you use the --oldpackage +keyword. We just need urpmi to support its use. +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + + <LI>Next message: <A HREF="001050.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1049">[ date ]</a> + <a href="thread.html#1049">[ thread ]</a> + <a href="subject.html#1049">[ subject ]</a> + <a href="author.html#1049">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001050.html b/zarb-ml/mageia-dev/20101009/001050.html new file mode 100644 index 000000000..f060b4a48 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001050.html @@ -0,0 +1,109 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAFE54C.2030501%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001049.html"> + <LINK REL="Next" HREF="001051.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>andré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CAFE54C.2030501%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">andr55 at laposte.net + </A><BR> + <I>Sat Oct 9 05:45:16 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001049.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001051.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1050">[ date ]</a> + <a href="thread.html#1050">[ thread ]</a> + <a href="subject.html#1050">[ subject ]</a> + <a href="author.html#1050">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Frank Griffin a écrit : +><i> Marc Paré wrote: +</I>><i> +</I>>><i> Thanks. So this thread is to see if there were a possibility to +</I>>><i> programme a more efficient roll-back option so that it would be more +</I>>><i> "aware" of the previous "dependencies" needs for the previous version. +</I>>><i> Having "double dependencies" is not so much of a problem, it is the +</I>>><i> rollback to a previous version where the dependency confusion may +</I>>><i> occur, and, ONLY, if an upgraded type of "dependency" thread had been +</I>>><i> installed. (Sorry I may have used the wrong terms in the last sentence). +</I>>><i> +</I>><i> Well, sort of. It's not an issue of efficiency, but of convenience and +</I>><i> just making it possible to do without resorting to manual use of the rpm +</I>><i> command. +</I>><i> +</I>><i> The rpm command "knows" that a new version replacing the old version +</I>><i> supplies the same things that the old one did, so it will quietly allow +</I>><i> the upgrade. It will also do what we need, i.e. go the other way and +</I>><i> replace a newer version with an older one if you use the --oldpackage +</I>><i> keyword. We just need urpmi to support its use +</I> +One thing that could facilitate this process, if the computer has a lot +of free disk space, is to rename the files being removed (copying the +configuration files), instead of erasing them. Although they will +probably have to be erased eventually, since no computer has unlimited +disk space. Keeping them long enough that a roll-back is no longer +probable could be workable. +Then a roll-back could be done very quickly, since the files are already +on disk, and presumably reliably. Of course, if new data has been +entered, and the format has been changed, this could be problematic. +Note that configuration files that have been changed from the +installation default are often already saved. (Generally ".old" is +appended to the configuration file name, sometimes ".new" to the new +configuration file.) +This of course adds the maintenance task of removing the old files at +some point - it could be done automatically according to some criteria, +or the user could have to do it manually, perhaps after being prompted +about it. + +(This rollback capability occurs with Microsoft products. The saved +files are only removed manually, on user initiative, which partly +explains the bloated size of a Microsoft installation over time.) + +If renaming-instead-of-deleting is implemented, perhaps a "do not keep +old program files (useful if limited disk space)" checkbox option would +be useful for computers with less free disk space. +Of course how much disk space is usable to save old programs on a +computer depends on the disk space usage for other purposes over time. + +my 2 cents :) + +- André (andre999) + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001049.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001051.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1050">[ date ]</a> + <a href="thread.html#1050">[ thread ]</a> + <a href="subject.html#1050">[ subject ]</a> + <a href="author.html#1050">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001051.html b/zarb-ml/mageia-dev/20101009/001051.html new file mode 100644 index 000000000..4979fa2fb --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001051.html @@ -0,0 +1,134 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8orhs%248q9%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001050.html"> + <LINK REL="Next" HREF="001052.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8orhs%248q9%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">marc at marcpare.com + </A><BR> + <I>Sat Oct 9 06:37:15 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001050.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001052.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1051">[ date ]</a> + <a href="thread.html#1051">[ thread ]</a> + <a href="subject.html#1051">[ subject ]</a> + <a href="author.html#1051">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-10-08 23:45, andré a écrit : +><i> Frank Griffin a écrit : +</I>>><i> Marc Paré wrote: +</I>>>><i> Thanks. So this thread is to see if there were a possibility to +</I>>>><i> programme a more efficient roll-back option so that it would be more +</I>>>><i> "aware" of the previous "dependencies" needs for the previous version. +</I>>>><i> Having "double dependencies" is not so much of a problem, it is the +</I>>>><i> rollback to a previous version where the dependency confusion may +</I>>>><i> occur, and, ONLY, if an upgraded type of "dependency" thread had been +</I>>>><i> installed. (Sorry I may have used the wrong terms in the last sentence). +</I>>><i> Well, sort of. It's not an issue of efficiency, but of convenience and +</I>>><i> just making it possible to do without resorting to manual use of the rpm +</I>>><i> command. +</I>>><i> +</I>>><i> The rpm command "knows" that a new version replacing the old version +</I>>><i> supplies the same things that the old one did, so it will quietly allow +</I>>><i> the upgrade. It will also do what we need, i.e. go the other way and +</I>>><i> replace a newer version with an older one if you use the --oldpackage +</I>>><i> keyword. We just need urpmi to support its use +</I>><i> +</I>><i> One thing that could facilitate this process, if the computer has a lot +</I>><i> of free disk space, is to rename the files being removed (copying the +</I>><i> configuration files), instead of erasing them. Although they will +</I>><i> probably have to be erased eventually, since no computer has unlimited +</I>><i> disk space. Keeping them long enough that a roll-back is no longer +</I>><i> probable could be workable. +</I>><i> Then a roll-back could be done very quickly, since the files are already +</I>><i> on disk, and presumably reliably. Of course, if new data has been +</I>><i> entered, and the format has been changed, this could be problematic. +</I>><i> Note that configuration files that have been changed from the +</I>><i> installation default are often already saved. (Generally ".old" is +</I>><i> appended to the configuration file name, sometimes ".new" to the new +</I>><i> configuration file.) +</I>><i> This of course adds the maintenance task of removing the old files at +</I>><i> some point - it could be done automatically according to some criteria, +</I>><i> or the user could have to do it manually, perhaps after being prompted +</I>><i> about it. +</I>><i> +</I>><i> (This rollback capability occurs with Microsoft products. The saved +</I>><i> files are only removed manually, on user initiative, which partly +</I>><i> explains the bloated size of a Microsoft installation over time.) +</I>><i> +</I>><i> If renaming-instead-of-deleting is implemented, perhaps a "do not keep +</I>><i> old program files (useful if limited disk space)" checkbox option would +</I>><i> be useful for computers with less free disk space. +</I>><i> Of course how much disk space is usable to save old programs on a +</I>><i> computer depends on the disk space usage for other purposes over time. +</I>><i> +</I>><i> my 2 cents :) +</I>><i> +</I>><i> - André (andre999) +</I>><i> +</I>><i> +</I> +Not sure about this process. Instead of making it easier for a user, +this would now make it more difficult to do and add another layer of +knowledge for the new user. It would have to be a little more seamless +than this. + +If there were a way at setup to establish the amount of remaining disk +space at installation time, and if there were enough space to allow +rollbacks without compromising the installation, then I guess the +rollback could then be activated. The user could then be advised at this +point that this was activated. If there was not enought disk space, a +message could warn the user that software rollbacks would not be +possible for lack lack of diskspace. + +I guess then, in the MCC, if a user used the Backports and installed +backported software, the rollback amount of diskspace could also be +monitored at this level with perhaps an option to delete old programs +that are now working well in their updated form. + +I guess this would take a bit of coding. But at least the use of +Backports would make a little more sense with a rollback option in case +an updated software installation did not work out. + +Marc + +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001050.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001052.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1051">[ date ]</a> + <a href="thread.html#1051">[ thread ]</a> + <a href="subject.html#1051">[ subject ]</a> + <a href="author.html#1051">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001052.html b/zarb-ml/mageia-dev/20101009/001052.html new file mode 100644 index 000000000..5e9c17b72 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001052.html @@ -0,0 +1,172 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB00876.9070001%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001051.html"> + <LINK REL="Next" HREF="001053.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>andré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB00876.9070001%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">andr55 at laposte.net + </A><BR> + <I>Sat Oct 9 08:15:18 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001051.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001053.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1052">[ date ]</a> + <a href="thread.html#1052">[ thread ]</a> + <a href="subject.html#1052">[ subject ]</a> + <a href="author.html#1052">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré a écrit : +><i> +</I>><i> Le 2010-10-08 23:45, andré a écrit : +</I>>><i> Frank Griffin a écrit : +</I>>>><i> Marc Paré wrote: +</I>>>>><i> Thanks. So this thread is to see if there were a possibility to +</I>>>>><i> programme a more efficient roll-back option so that it would be more +</I>>>>><i> "aware" of the previous "dependencies" needs for the previous version. +</I>>>>><i> Having "double dependencies" is not so much of a problem, it is the +</I>>>>><i> rollback to a previous version where the dependency confusion may +</I>>>>><i> occur, and, ONLY, if an upgraded type of "dependency" thread had been +</I>>>>><i> installed. (Sorry I may have used the wrong terms in the last +</I>>>>><i> sentence). +</I>>>><i> Well, sort of. It's not an issue of efficiency, but of convenience and +</I>>>><i> just making it possible to do without resorting to manual use of the +</I>>>><i> rpm +</I>>>><i> command. +</I>>>><i> +</I>>>><i> The rpm command "knows" that a new version replacing the old version +</I>>>><i> supplies the same things that the old one did, so it will quietly allow +</I>>>><i> the upgrade. It will also do what we need, i.e. go the other way and +</I>>>><i> replace a newer version with an older one if you use the --oldpackage +</I>>>><i> keyword. We just need urpmi to support its use +</I>>><i> +</I>>><i> One thing that could facilitate this process, if the computer has a lot +</I>>><i> of free disk space, is to rename the files being removed (copying the +</I>>><i> configuration files), instead of erasing them. Although they will +</I>>><i> probably have to be erased eventually, since no computer has unlimited +</I>>><i> disk space. Keeping them long enough that a roll-back is no longer +</I>>><i> probable could be workable. +</I>>><i> Then a roll-back could be done very quickly, since the files are already +</I>>><i> on disk, and presumably reliably. Of course, if new data has been +</I>>><i> entered, and the format has been changed, this could be problematic. +</I>>><i> Note that configuration files that have been changed from the +</I>>><i> installation default are often already saved. (Generally ".old" is +</I>>><i> appended to the configuration file name, sometimes ".new" to the new +</I>>><i> configuration file.) +</I>>><i> This of course adds the maintenance task of removing the old files at +</I>>><i> some point - it could be done automatically according to some criteria, +</I>>><i> or the user could have to do it manually, perhaps after being prompted +</I>>><i> about it. +</I>>><i> +</I>>><i> (This rollback capability occurs with Microsoft products. The saved +</I>>><i> files are only removed manually, on user initiative, which partly +</I>>><i> explains the bloated size of a Microsoft installation over time.) +</I>>><i> +</I>>><i> If renaming-instead-of-deleting is implemented, perhaps a "do not keep +</I>>><i> old program files (useful if limited disk space)" checkbox option would +</I>>><i> be useful for computers with less free disk space. +</I>>><i> Of course how much disk space is usable to save old programs on a +</I>>><i> computer depends on the disk space usage for other purposes over time. +</I>>><i> +</I>>><i> my 2 cents :) +</I>>><i> +</I>>><i> - André (andre999) +</I>><i> +</I>><i> Not sure about this process. Instead of making it easier for a user, +</I>><i> this would now make it more difficult to do and add another layer of +</I>><i> knowledge for the new user. It would have to be a little more seamless +</I>><i> than this. +</I>><i> +</I>><i> If there were a way at setup to establish the amount of remaining disk +</I>><i> space at installation time, and if there were enough space to allow +</I>><i> rollbacks without compromising the installation, then I guess the +</I>><i> rollback could then be activated. The user could then be advised at +</I>><i> this point that this was activated. If there was not enought disk +</I>><i> space, a message could warn the user that software rollbacks would not +</I>><i> be possible for lack lack of diskspace. +</I>The problem is not establishing the current free disk space, but how +much to leave for use as temporary disk space for other applications. +For example, if an enduser likes editing numerous large video files at +the same time (maybe he makes movies), he could need a very large amount +of temporary free disk space. Another user, with the same programs +installed, might do primarily word processing and Internet, and only +occasionally edit small videos, thus only needing a relatively small +amount of temporary disk space. +Of course, there could be an automatic default, adjustable via a +configuration file. +><i> +</I>><i> I guess then, in the MCC, if a user used the Backports and installed +</I>><i> backported software, the rollback amount of diskspace could also be +</I>><i> monitored at this level with perhaps an option to delete old programs +</I>><i> that are now working well in their updated form. +</I>This sort of makes sense -- but it is not only the newly installed +program which is of concern, but also other programs which may have the +same dependancies (not counting the versions). +It could take a considerable time before these other programs are +executed, so it becomes a bit tricky. +Probably why Microsoft decided to keep such programs by default. + +Essentially that is why I would prefer backports to use versions of +dependancies which correspond to the distro release. A bit more work +for packagers, but a much more stable system. +Then the rollback system would only affect the backported program and +any programs directly dependant on that version. The problem becomes +much simpler. +Once the backported and dependant programs (which would be known in the +database) have all been run without crashing, the user could be asked if +the programs all worked satifactorily and it was ok to delete the backup. + +><i> I guess this would take a bit of coding. But at least the use of +</I>><i> Backports would make a little more sense with a rollback option in +</I>><i> case an updated software installation did not work out. +</I>I definitely like the idea of a rollback option. +However, another option which I would like to see is simply leaving the +old program in place where possible without conflicts - and prompting +for its deletion after the backport and dependancies have been run (with +the same sort of information displayed) -- when rpmdrake/urpmi is +subsequently accessed. +In the case of problems with the backport, one would simply run the old +program, which is still in place. +Of course, there will often be conficts such that the old program can +not be left in place, making rollbacks still useful. +><i> +</I>><i> Marc +</I>- André (andre999) +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001051.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001053.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1052">[ date ]</a> + <a href="thread.html#1052">[ thread ]</a> + <a href="subject.html#1052">[ subject ]</a> + <a href="author.html#1052">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001053.html b/zarb-ml/mageia-dev/20101009/001053.html new file mode 100644 index 000000000..0e6bc6f46 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001053.html @@ -0,0 +1,210 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101009080508.39422de1%40otfordduckscomputers.co.uk%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001052.html"> + <LINK REL="Next" HREF="001054.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Margot</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101009080508.39422de1%40otfordduckscomputers.co.uk%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">margot at otfordduckscomputers.co.uk + </A><BR> + <I>Sat Oct 9 09:05:08 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001052.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001054.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1053">[ date ]</a> + <a href="thread.html#1053">[ thread ]</a> + <a href="subject.html#1053">[ subject ]</a> + <a href="author.html#1053">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, 09 Oct 2010 02:15:18 -0400 +andré <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">andr55 at laposte.net</A>> wrote: + +><i> Marc Paré a écrit : +</I>><i> > +</I>><i> > Le 2010-10-08 23:45, andré a écrit : +</I>><i> >> Frank Griffin a écrit : +</I>><i> >>> Marc Paré wrote: +</I>><i> >>>> Thanks. So this thread is to see if there were a possibility +</I>><i> >>>> to programme a more efficient roll-back option so that it +</I>><i> >>>> would be more "aware" of the previous "dependencies" needs +</I>><i> >>>> for the previous version. Having "double dependencies" is +</I>><i> >>>> not so much of a problem, it is the rollback to a previous +</I>><i> >>>> version where the dependency confusion may occur, and, ONLY, +</I>><i> >>>> if an upgraded type of "dependency" thread had been +</I>><i> >>>> installed. (Sorry I may have used the wrong terms in the +</I>><i> >>>> last sentence). +</I>><i> >>> Well, sort of. It's not an issue of efficiency, but of +</I>><i> >>> convenience and just making it possible to do without +</I>><i> >>> resorting to manual use of the rpm +</I>><i> >>> command. +</I>><i> >>> +</I>><i> >>> The rpm command "knows" that a new version replacing the old +</I>><i> >>> version supplies the same things that the old one did, so it +</I>><i> >>> will quietly allow the upgrade. It will also do what we need, +</I>><i> >>> i.e. go the other way and replace a newer version with an +</I>><i> >>> older one if you use the --oldpackage keyword. We just need +</I>><i> >>> urpmi to support its use +</I>><i> >> +</I>><i> >> One thing that could facilitate this process, if the computer +</I>><i> >> has a lot of free disk space, is to rename the files being +</I>><i> >> removed (copying the configuration files), instead of erasing +</I>><i> >> them. Although they will probably have to be erased +</I>><i> >> eventually, since no computer has unlimited disk space. +</I>><i> >> Keeping them long enough that a roll-back is no longer +</I>><i> >> probable could be workable. Then a roll-back could be done +</I>><i> >> very quickly, since the files are already on disk, and +</I>><i> >> presumably reliably. Of course, if new data has been entered, +</I>><i> >> and the format has been changed, this could be problematic. +</I>><i> >> Note that configuration files that have been changed from the +</I>><i> >> installation default are often already saved. (Generally +</I>><i> >> ".old" is appended to the configuration file name, sometimes +</I>><i> >> ".new" to the new configuration file.) This of course adds the +</I>><i> >> maintenance task of removing the old files at some point - it +</I>><i> >> could be done automatically according to some criteria, or the +</I>><i> >> user could have to do it manually, perhaps after being +</I>><i> >> prompted about it. +</I>><i> >> +</I>><i> >> (This rollback capability occurs with Microsoft products. The +</I>><i> >> saved files are only removed manually, on user initiative, +</I>><i> >> which partly explains the bloated size of a Microsoft +</I>><i> >> installation over time.) +</I>><i> >> +</I>><i> >> If renaming-instead-of-deleting is implemented, perhaps a "do +</I>><i> >> not keep old program files (useful if limited disk space)" +</I>><i> >> checkbox option would be useful for computers with less free +</I>><i> >> disk space. Of course how much disk space is usable to save +</I>><i> >> old programs on a computer depends on the disk space usage for +</I>><i> >> other purposes over time. +</I>><i> >> +</I>><i> >> my 2 cents :) +</I>><i> >> +</I>><i> >> - André (andre999) +</I>><i> > +</I>><i> > Not sure about this process. Instead of making it easier for a +</I>><i> > user, this would now make it more difficult to do and add +</I>><i> > another layer of knowledge for the new user. It would have to +</I>><i> > be a little more seamless than this. +</I>><i> > +</I>><i> > If there were a way at setup to establish the amount of +</I>><i> > remaining disk space at installation time, and if there were +</I>><i> > enough space to allow rollbacks without compromising the +</I>><i> > installation, then I guess the rollback could then be +</I>><i> > activated. The user could then be advised at this point that +</I>><i> > this was activated. If there was not enought disk space, a +</I>><i> > message could warn the user that software rollbacks would not +</I>><i> > be possible for lack lack of diskspace. +</I>><i> The problem is not establishing the current free disk space, but +</I>><i> how much to leave for use as temporary disk space for other +</I>><i> applications. For example, if an enduser likes editing numerous +</I>><i> large video files at the same time (maybe he makes movies), he +</I>><i> could need a very large amount of temporary free disk space. +</I>><i> Another user, with the same programs installed, might do +</I>><i> primarily word processing and Internet, and only occasionally +</I>><i> edit small videos, thus only needing a relatively small amount of +</I>><i> temporary disk space. Of course, there could be an automatic +</I>><i> default, adjustable via a configuration file. +</I>><i> > +</I>><i> > I guess then, in the MCC, if a user used the Backports and +</I>><i> > installed backported software, the rollback amount of diskspace +</I>><i> > could also be monitored at this level with perhaps an option to +</I>><i> > delete old programs that are now working well in their updated +</I>><i> > form. +</I>><i> This sort of makes sense -- but it is not only the newly +</I>><i> installed program which is of concern, but also other programs +</I>><i> which may have the same dependancies (not counting the versions). +</I>><i> It could take a considerable time before these other programs are +</I>><i> executed, so it becomes a bit tricky. +</I>><i> Probably why Microsoft decided to keep such programs by default. +</I>><i> +</I>><i> Essentially that is why I would prefer backports to use versions +</I>><i> of dependancies which correspond to the distro release. A bit +</I>><i> more work for packagers, but a much more stable system. +</I>><i> Then the rollback system would only affect the backported program +</I>><i> and any programs directly dependant on that version. The problem +</I>><i> becomes much simpler. +</I>><i> Once the backported and dependant programs (which would be known +</I>><i> in the database) have all been run without crashing, the user +</I>><i> could be asked if the programs all worked satifactorily and it +</I>><i> was ok to delete the backup. +</I>><i> +</I>><i> > I guess this would take a bit of coding. But at least the use +</I>><i> > of Backports would make a little more sense with a rollback +</I>><i> > option in case an updated software installation did not work +</I>><i> > out. +</I>><i> I definitely like the idea of a rollback option. +</I>><i> However, another option which I would like to see is simply +</I>><i> leaving the old program in place where possible without conflicts +</I>><i> - and prompting for its deletion after the backport and +</I>><i> dependancies have been run (with the same sort of information +</I>><i> displayed) -- when rpmdrake/urpmi is subsequently accessed. +</I>><i> In the case of problems with the backport, one would simply run +</I>><i> the old program, which is still in place. +</I>><i> Of course, there will often be conficts such that the old program +</I>><i> can not be left in place, making rollbacks still useful. +</I>><i> > +</I>><i> > Marc +</I>><i> - André (andre999) +</I> +There are already various options which can be run with urpmi, such +as --noclean and --repackage (see man urpmi) and perhaps these +could be incorporated into the GUI - with full simple explanations +for the user on exactly what will happen if those options are +chosen. + +For example: +"Select this option if you want to save the old version of the +package that is being updated. If there is a problem with the new +version, you will be able to uninstall it and go back to the older +version. Warning: this option will use extra space on your disk." + +There could then be a list available showing all the saved older +versions of packages - if, for instance, a user had saved 10 older +versions of Firefox and knew that the most recent one worked +perfectly, they could then safely delete the 9 older versions to +reclaim some disk space. + +-- +Margot +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +**Otford Ducks Computers** +We teach, you learn... +...and, if you don't do your homework, we set the cat on you! +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001052.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001054.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1053">[ date ]</a> + <a href="thread.html#1053">[ thread ]</a> + <a href="subject.html#1053">[ subject ]</a> + <a href="author.html#1053">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001054.html b/zarb-ml/mageia-dev/20101009/001054.html new file mode 100644 index 000000000..db6fdb099 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001054.html @@ -0,0 +1,217 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8p4l8%241b9%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001053.html"> + <LINK REL="Next" HREF="001070.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3Ci8p4l8%241b9%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">marc at marcpare.com + </A><BR> + <I>Sat Oct 9 09:12:39 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001053.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001070.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1054">[ date ]</a> + <a href="thread.html#1054">[ thread ]</a> + <a href="subject.html#1054">[ subject ]</a> + <a href="author.html#1054">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-10-09 03:05, Margot a écrit : +><i> On Sat, 09 Oct 2010 02:15:18 -0400 +</I>><i> andré<<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">andr55 at laposte.net</A>> wrote: +</I>><i> +</I>>><i> Marc Paré a écrit : +</I>>>><i> +</I>>>><i> Le 2010-10-08 23:45, andré a écrit : +</I>>>>><i> Frank Griffin a écrit : +</I>>>>>><i> Marc Paré wrote: +</I>>>>>>><i> Thanks. So this thread is to see if there were a possibility +</I>>>>>>><i> to programme a more efficient roll-back option so that it +</I>>>>>>><i> would be more "aware" of the previous "dependencies" needs +</I>>>>>>><i> for the previous version. Having "double dependencies" is +</I>>>>>>><i> not so much of a problem, it is the rollback to a previous +</I>>>>>>><i> version where the dependency confusion may occur, and, ONLY, +</I>>>>>>><i> if an upgraded type of "dependency" thread had been +</I>>>>>>><i> installed. (Sorry I may have used the wrong terms in the +</I>>>>>>><i> last sentence). +</I>>>>>><i> Well, sort of. It's not an issue of efficiency, but of +</I>>>>>><i> convenience and just making it possible to do without +</I>>>>>><i> resorting to manual use of the rpm +</I>>>>>><i> command. +</I>>>>>><i> +</I>>>>>><i> The rpm command "knows" that a new version replacing the old +</I>>>>>><i> version supplies the same things that the old one did, so it +</I>>>>>><i> will quietly allow the upgrade. It will also do what we need, +</I>>>>>><i> i.e. go the other way and replace a newer version with an +</I>>>>>><i> older one if you use the --oldpackage keyword. We just need +</I>>>>>><i> urpmi to support its use +</I>>>>><i> +</I>>>>><i> One thing that could facilitate this process, if the computer +</I>>>>><i> has a lot of free disk space, is to rename the files being +</I>>>>><i> removed (copying the configuration files), instead of erasing +</I>>>>><i> them. Although they will probably have to be erased +</I>>>>><i> eventually, since no computer has unlimited disk space. +</I>>>>><i> Keeping them long enough that a roll-back is no longer +</I>>>>><i> probable could be workable. Then a roll-back could be done +</I>>>>><i> very quickly, since the files are already on disk, and +</I>>>>><i> presumably reliably. Of course, if new data has been entered, +</I>>>>><i> and the format has been changed, this could be problematic. +</I>>>>><i> Note that configuration files that have been changed from the +</I>>>>><i> installation default are often already saved. (Generally +</I>>>>><i> ".old" is appended to the configuration file name, sometimes +</I>>>>><i> ".new" to the new configuration file.) This of course adds the +</I>>>>><i> maintenance task of removing the old files at some point - it +</I>>>>><i> could be done automatically according to some criteria, or the +</I>>>>><i> user could have to do it manually, perhaps after being +</I>>>>><i> prompted about it. +</I>>>>><i> +</I>>>>><i> (This rollback capability occurs with Microsoft products. The +</I>>>>><i> saved files are only removed manually, on user initiative, +</I>>>>><i> which partly explains the bloated size of a Microsoft +</I>>>>><i> installation over time.) +</I>>>>><i> +</I>>>>><i> If renaming-instead-of-deleting is implemented, perhaps a "do +</I>>>>><i> not keep old program files (useful if limited disk space)" +</I>>>>><i> checkbox option would be useful for computers with less free +</I>>>>><i> disk space. Of course how much disk space is usable to save +</I>>>>><i> old programs on a computer depends on the disk space usage for +</I>>>>><i> other purposes over time. +</I>>>>><i> +</I>>>>><i> my 2 cents :) +</I>>>>><i> +</I>>>>><i> - André (andre999) +</I>>>><i> +</I>>>><i> Not sure about this process. Instead of making it easier for a +</I>>>><i> user, this would now make it more difficult to do and add +</I>>>><i> another layer of knowledge for the new user. It would have to +</I>>>><i> be a little more seamless than this. +</I>>>><i> +</I>>>><i> If there were a way at setup to establish the amount of +</I>>>><i> remaining disk space at installation time, and if there were +</I>>>><i> enough space to allow rollbacks without compromising the +</I>>>><i> installation, then I guess the rollback could then be +</I>>>><i> activated. The user could then be advised at this point that +</I>>>><i> this was activated. If there was not enought disk space, a +</I>>>><i> message could warn the user that software rollbacks would not +</I>>>><i> be possible for lack lack of diskspace. +</I>>><i> The problem is not establishing the current free disk space, but +</I>>><i> how much to leave for use as temporary disk space for other +</I>>><i> applications. For example, if an enduser likes editing numerous +</I>>><i> large video files at the same time (maybe he makes movies), he +</I>>><i> could need a very large amount of temporary free disk space. +</I>>><i> Another user, with the same programs installed, might do +</I>>><i> primarily word processing and Internet, and only occasionally +</I>>><i> edit small videos, thus only needing a relatively small amount of +</I>>><i> temporary disk space. Of course, there could be an automatic +</I>>><i> default, adjustable via a configuration file. +</I>>>><i> +</I>>>><i> I guess then, in the MCC, if a user used the Backports and +</I>>>><i> installed backported software, the rollback amount of diskspace +</I>>>><i> could also be monitored at this level with perhaps an option to +</I>>>><i> delete old programs that are now working well in their updated +</I>>>><i> form. +</I>>><i> This sort of makes sense -- but it is not only the newly +</I>>><i> installed program which is of concern, but also other programs +</I>>><i> which may have the same dependancies (not counting the versions). +</I>>><i> It could take a considerable time before these other programs are +</I>>><i> executed, so it becomes a bit tricky. +</I>>><i> Probably why Microsoft decided to keep such programs by default. +</I>>><i> +</I>>><i> Essentially that is why I would prefer backports to use versions +</I>>><i> of dependancies which correspond to the distro release. A bit +</I>>><i> more work for packagers, but a much more stable system. +</I>>><i> Then the rollback system would only affect the backported program +</I>>><i> and any programs directly dependant on that version. The problem +</I>>><i> becomes much simpler. +</I>>><i> Once the backported and dependant programs (which would be known +</I>>><i> in the database) have all been run without crashing, the user +</I>>><i> could be asked if the programs all worked satifactorily and it +</I>>><i> was ok to delete the backup. +</I>>><i> +</I>>>><i> I guess this would take a bit of coding. But at least the use +</I>>>><i> of Backports would make a little more sense with a rollback +</I>>>><i> option in case an updated software installation did not work +</I>>>><i> out. +</I>>><i> I definitely like the idea of a rollback option. +</I>>><i> However, another option which I would like to see is simply +</I>>><i> leaving the old program in place where possible without conflicts +</I>>><i> - and prompting for its deletion after the backport and +</I>>><i> dependancies have been run (with the same sort of information +</I>>><i> displayed) -- when rpmdrake/urpmi is subsequently accessed. +</I>>><i> In the case of problems with the backport, one would simply run +</I>>><i> the old program, which is still in place. +</I>>><i> Of course, there will often be conficts such that the old program +</I>>><i> can not be left in place, making rollbacks still useful. +</I>>>><i> +</I>>>><i> Marc +</I>>><i> - André (andre999) +</I>><i> +</I>><i> There are already various options which can be run with urpmi, such +</I>><i> as --noclean and --repackage (see man urpmi) and perhaps these +</I>><i> could be incorporated into the GUI - with full simple explanations +</I>><i> for the user on exactly what will happen if those options are +</I>><i> chosen. +</I>><i> +</I>><i> For example: +</I>><i> "Select this option if you want to save the old version of the +</I>><i> package that is being updated. If there is a problem with the new +</I>><i> version, you will be able to uninstall it and go back to the older +</I>><i> version. Warning: this option will use extra space on your disk." +</I>><i> +</I>><i> There could then be a list available showing all the saved older +</I>><i> versions of packages - if, for instance, a user had saved 10 older +</I>><i> versions of Firefox and knew that the most recent one worked +</I>><i> perfectly, they could then safely delete the 9 older versions to +</I>><i> reclaim some disk space. +</I>><i> +</I> +I guess both of your suggestions would work André and Margot. + +So, this sounds like it could be something that could be worked out. I +would prefer, as a user, Margot's process. Of course the user would have +to be able to see the usage and re-claimed space due to his use or +Backports. Just to keep informed. + +Marc + +</PRE> + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001053.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001070.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1054">[ date ]</a> + <a href="thread.html#1054">[ thread ]</a> + <a href="subject.html#1054">[ subject ]</a> + <a href="author.html#1054">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001055.html b/zarb-ml/mageia-dev/20101009/001055.html new file mode 100644 index 000000000..5ee146f43 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001055.html @@ -0,0 +1,104 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Release cycle - what is actually POSSIBLE? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycle%20-%20what%20is%20actually%20POSSIBLE%3F&In-Reply-To=%3C20101009085702.1b9e1ca5%40otfordduckscomputers.co.uk%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001069.html"> + <LINK REL="Next" HREF="001056.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Release cycle - what is actually POSSIBLE?</H1> + <B>Margot</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycle%20-%20what%20is%20actually%20POSSIBLE%3F&In-Reply-To=%3C20101009085702.1b9e1ca5%40otfordduckscomputers.co.uk%3E" + TITLE="[Mageia-dev] Release cycle - what is actually POSSIBLE?">margot at otfordduckscomputers.co.uk + </A><BR> + <I>Sat Oct 9 09:57:02 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001069.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001056.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1055">[ date ]</a> + <a href="thread.html#1055">[ thread ]</a> + <a href="subject.html#1055">[ subject ]</a> + <a href="author.html#1055">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>There has been a lengthy debate about users' wishes for the Mageia +release cycle, but one important voice has been missing from this +debate: the collective voice of the devs who will be responsible +for producing the releases. + +Before we start having polls and surveys, it would be useful to +hear from our devs. I'm hoping that they have already been +communicating with one another in the background (IRC? private +emails?) and working out what can actually be done. + +As this is supposed to be a community-based distro, why do I think +that the devs' opinion is so important? + +(a) They are the ones with the experience, they know how many +person-hours it will take to produce a releasable version of +Mageia. +(b) They are the ones who know how many hours they each have +available to personally commit to Mageia - some may be able to work +full-time on Mageia, others will have other work or family +commitments, and even those who can work full-time on Mageia will +occasionally need to sleep and eat! + +We have two targets: +1) A cauldron version for experienced users to test, and +2) A stable (as much as possible!) version for less experienced +end-users. + +So, devs, please draw on your experience and your knowledge, and +tell us what will actually be possible. + +-- +Margot +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +**Otford Ducks Computers** +We teach, you learn... +...and, if you don't do your homework, we set the cat on you! +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001069.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001056.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1055">[ date ]</a> + <a href="thread.html#1055">[ thread ]</a> + <a href="subject.html#1055">[ subject ]</a> + <a href="author.html#1055">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001056.html b/zarb-ml/mageia-dev/20101009/001056.html new file mode 100644 index 000000000..a589123b7 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001056.html @@ -0,0 +1,139 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Release cycle - what is actually POSSIBLE? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycle%20-%20what%20is%20actually%20POSSIBLE%3F&In-Reply-To=%3Ci8p8g4%24cmi%241%40dough.gmane.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001055.html"> + <LINK REL="Next" HREF="001057.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Release cycle - what is actually POSSIBLE?</H1> + <B>Marc Paré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycle%20-%20what%20is%20actually%20POSSIBLE%3F&In-Reply-To=%3Ci8p8g4%24cmi%241%40dough.gmane.org%3E" + TITLE="[Mageia-dev] Release cycle - what is actually POSSIBLE?">marc at marcpare.com + </A><BR> + <I>Sat Oct 9 10:18:12 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001055.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI>Next message: <A HREF="001057.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1056">[ date ]</a> + <a href="thread.html#1056">[ thread ]</a> + <a href="subject.html#1056">[ subject ]</a> + <a href="author.html#1056">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le 2010-10-09 03:57, Margot a écrit : +><i> There has been a lengthy debate about users' wishes for the Mageia +</I>><i> release cycle, but one important voice has been missing from this +</I>><i> debate: the collective voice of the devs who will be responsible +</I>><i> for producing the releases. +</I>><i> +</I>><i> Before we start having polls and surveys, it would be useful to +</I>><i> hear from our devs. I'm hoping that they have already been +</I>><i> communicating with one another in the background (IRC? private +</I>><i> emails?) and working out what can actually be done. +</I>><i> +</I>><i> As this is supposed to be a community-based distro, why do I think +</I>><i> that the devs' opinion is so important? +</I>><i> +</I>><i> (a) They are the ones with the experience, they know how many +</I>><i> person-hours it will take to produce a releasable version of +</I>><i> Mageia. +</I>><i> (b) They are the ones who know how many hours they each have +</I>><i> available to personally commit to Mageia - some may be able to work +</I>><i> full-time on Mageia, others will have other work or family +</I>><i> commitments, and even those who can work full-time on Mageia will +</I>><i> occasionally need to sleep and eat! +</I>><i> +</I>><i> We have two targets: +</I>><i> 1) A cauldron version for experienced users to test, and +</I>><i> 2) A stable (as much as possible!) version for less experienced +</I>><i> end-users. +</I>><i> +</I>><i> So, devs, please draw on your experience and your knowledge, and +</I>><i> tell us what will actually be possible. +</I>><i> +</I> +Hi Margot: + +Romain suggested this on one of those lenghty threads: + +--------------------- + +It has been posted before but I guess it's a good read for anyone +willing to push an argument in this debate: +<A HREF="http://mairin.wordpress.com/2010/09/01/a-story-about-updates-and-people/">http://mairin.wordpress.com/2010/09/01/a-story-about-updates-and-people/</A> + +It is a nice post explaining the existing different point of views +(bonus to clever points about updates frequency and presentation). + +Now, in the same vein, let's put the discussion at rest a little and +have each interested person write down an article with arguments for +the why's and how's. So here is a page for that: +<A HREF="http://mageia.org/wiki/doku.php?id=rollingdebate">http://mageia.org/wiki/doku.php?id=rollingdebate</A> + +Please write down your point of view, detail it as explained on the +wiki page, link it and a week from now, everyone involved in the +discussion can have a look at it for a summary. + +That won't trigger a change decision at once (way too soon anyway, we +have to roll a first release to assess our new build system and +infrastructure and organisation) but it may at least lay down all +arguments and allow to have a better view of what everyone understand, +agree on definitions and see what is really at stake here. For later +reference, discussion and decision. + +Thanks a lot. + +Cheers, + +Romain + +--------------------- + +Marc + + +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001055.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI>Next message: <A HREF="001057.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1056">[ date ]</a> + <a href="thread.html#1056">[ thread ]</a> + <a href="subject.html#1056">[ subject ]</a> + <a href="author.html#1056">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001057.html b/zarb-ml/mageia-dev/20101009/001057.html new file mode 100644 index 000000000..71b1f9749 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001057.html @@ -0,0 +1,77 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Release cycle - what is actually POSSIBLE? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycle%20-%20what%20is%20actually%20POSSIBLE%3F&In-Reply-To=%3C201010091042.53280.oliver.bgr%40googlemail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001056.html"> + <LINK REL="Next" HREF="001063.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Release cycle - what is actually POSSIBLE?</H1> + <B>Oliver Burger</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Release%20cycle%20-%20what%20is%20actually%20POSSIBLE%3F&In-Reply-To=%3C201010091042.53280.oliver.bgr%40googlemail.com%3E" + TITLE="[Mageia-dev] Release cycle - what is actually POSSIBLE?">oliver.bgr at googlemail.com + </A><BR> + <I>Sat Oct 9 10:42:53 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001056.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI>Next message: <A HREF="001063.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1057">[ date ]</a> + <a href="thread.html#1057">[ thread ]</a> + <a href="subject.html#1057">[ subject ]</a> + <a href="author.html#1057">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">marc at marcpare.com</A>> schrieb am 2010-10-09 +><i> > Before we start having polls and surveys, it would be useful to +</I>><i> > hear from our devs. I'm hoping that they have already been +</I>><i> > communicating with one another in the background (IRC? private +</I>><i> > emails?) and working out what can actually be done. +</I>I can remember, Michael (misc) telling at least once but I do think several +times: Let's do one release, then we'll see, how much time we have and what we +can do... + +Oliver +</PRE> + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001056.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI>Next message: <A HREF="001063.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1057">[ date ]</a> + <a href="thread.html#1057">[ thread ]</a> + <a href="subject.html#1057">[ subject ]</a> + <a href="author.html#1057">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001058.html b/zarb-ml/mageia-dev/20101009/001058.html new file mode 100644 index 000000000..91f4809a6 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001058.html @@ -0,0 +1,84 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C201010091110.36989.r.h.michel%2Bmageia%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001068.html"> + <LINK REL="Next" HREF="001060.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Renaud MICHEL</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C201010091110.36989.r.h.michel%2Bmageia%40gmail.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">r.h.michel+mageia at gmail.com + </A><BR> + <I>Sat Oct 9 11:10:36 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001068.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001060.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1058">[ date ]</a> + <a href="thread.html#1058">[ thread ]</a> + <a href="subject.html#1058">[ subject ]</a> + <a href="author.html#1058">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On samedi 09 octobre 2010 at 05:45, andré wrote : +><i> Note that configuration files that have been changed from the +</I>><i> installation default are often already saved. (Generally ".old" is +</I>><i> appended to the configuration file name, sometimes ".new" to the new +</I>><i> configuration file.) +</I> +But here you are only talking about system-wide configuration files, which +are known of rpm as they are part of the package and marked as config files. +But what about user specific configuration files? +For the easy kind, where a program will have a single configuration file (or +dedicated directory), a pre-inst script could find it in the home of each +users and backup them. But you have cases of programs which have +configuration scattered in multiple shared directories (like KDE), or even +non-deterministic configuration files and it can become very tricky to find +all the files to backup. +And you have the really hard kind, where the same configuration file may be +shared by different packages. For example, plasma applet configurations are +stored in a few ~/.kde4/share/config/plasma* files. + +-- +Renaud Michel +</PRE> + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001068.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001060.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1058">[ date ]</a> + <a href="thread.html#1058">[ thread ]</a> + <a href="subject.html#1058">[ subject ]</a> + <a href="author.html#1058">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001059.html b/zarb-ml/mageia-dev/20101009/001059.html new file mode 100644 index 000000000..17dc12924 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001059.html @@ -0,0 +1,69 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101009102844.GC21566%40maude.comedia.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001070.html"> + <LINK REL="Next" HREF="001061.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Luca Berra</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101009102844.GC21566%40maude.comedia.it%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">bluca at vodka.it + </A><BR> + <I>Sat Oct 9 12:28:44 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001070.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001061.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1059">[ date ]</a> + <a href="thread.html#1059">[ thread ]</a> + <a href="subject.html#1059">[ subject ]</a> + <a href="author.html#1059">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Oct 09, 2010 at 08:05:08AM +0100, Margot wrote: +><i>There are already various options which can be run with urpmi, such +</I>><i>as --noclean and --repackage (see man urpmi) and perhaps these +</I>><i>could be incorporated into the GUI - with full simple explanations +</I>><i>for the user on exactly what will happen if those options are +</I>><i>chosen. +</I>man page is wrong, +--repackage has been dropped from urpmi since it has been dropped from +rpm 4.6 + +-- +Luca Berra -- <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bluca at vodka.it</A> +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001070.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001061.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1059">[ date ]</a> + <a href="thread.html#1059">[ thread ]</a> + <a href="subject.html#1059">[ subject ]</a> + <a href="author.html#1059">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001060.html b/zarb-ml/mageia-dev/20101009/001060.html new file mode 100644 index 000000000..ad3d306b4 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001060.html @@ -0,0 +1,87 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101009103244.GD21566%40maude.comedia.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001058.html"> + <LINK REL="Next" HREF="001062.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Luca Berra</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101009103244.GD21566%40maude.comedia.it%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">bluca at vodka.it + </A><BR> + <I>Sat Oct 9 12:32:44 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001058.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001062.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1060">[ date ]</a> + <a href="thread.html#1060">[ thread ]</a> + <a href="subject.html#1060">[ subject ]</a> + <a href="author.html#1060">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Oct 09, 2010 at 11:10:36AM +0200, Renaud MICHEL wrote: +><i>On samedi 09 octobre 2010 at 05:45, andré wrote : +</I>>><i> Note that configuration files that have been changed from the +</I>>><i> installation default are often already saved. (Generally ".old" is +</I>>><i> appended to the configuration file name, sometimes ".new" to the new +</I>>><i> configuration file.) +</I>><i> +</I>><i>But here you are only talking about system-wide configuration files, which +</I>><i>are known of rpm as they are part of the package and marked as config files. +</I>><i>But what about user specific configuration files? +</I>><i>For the easy kind, where a program will have a single configuration file (or +</I>><i>dedicated directory), a pre-inst script could find it in the home of each +</I>><i>users and backup them. But you have cases of programs which have +</I>><i>configuration scattered in multiple shared directories (like KDE), or even +</I>><i>non-deterministic configuration files and it can become very tricky to find +</I>><i>all the files to backup. +</I>><i>And you have the really hard kind, where the same configuration file may be +</I>><i>shared by different packages. For example, plasma applet configurations are +</I>><i>stored in a few ~/.kde4/share/config/plasma* files. +</I> ++1 +this is the very problem why i believe rollbacks are not that easy + +-- +Luca Berra -- <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bluca at vodka.it</A> +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001058.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001062.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1060">[ date ]</a> + <a href="thread.html#1060">[ thread ]</a> + <a href="subject.html#1060">[ subject ]</a> + <a href="author.html#1060">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001061.html b/zarb-ml/mageia-dev/20101009/001061.html new file mode 100644 index 000000000..0506a9a73 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001061.html @@ -0,0 +1,67 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C201010091316.o99DGAmf087251%40smtp-vbr15.xs4all.nl%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001059.html"> + <LINK REL="Next" HREF="001065.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Dick Gevers</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C201010091316.o99DGAmf087251%40smtp-vbr15.xs4all.nl%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">dvgevers at xs4all.nl + </A><BR> + <I>Sat Oct 9 15:16:09 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001059.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001065.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1061">[ date ]</a> + <a href="thread.html#1061">[ thread ]</a> + <a href="subject.html#1061">[ subject ]</a> + <a href="author.html#1061">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, 9 Oct 2010 12:28:44 +0200, Luca Berra wrote about Re: [Mageia-dev] +Proposal: Updating released versions (long post): + +><i>--repackage has been dropped from urpmi since it has been dropped from +</I>><i>rpm 4.6 +</I> +Will you post it in Mdv Bugzilla? + +TIA +=Dick Gevers= +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001059.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001065.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1061">[ date ]</a> + <a href="thread.html#1061">[ thread ]</a> + <a href="subject.html#1061">[ subject ]</a> + <a href="author.html#1061">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001062.html b/zarb-ml/mageia-dev/20101009/001062.html new file mode 100644 index 000000000..ba1e991e4 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001062.html @@ -0,0 +1,109 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB07220.2060404%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001060.html"> + <LINK REL="Next" HREF="001069.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>andré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB07220.2060404%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">andr55 at laposte.net + </A><BR> + <I>Sat Oct 9 15:46:08 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001060.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001069.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1062">[ date ]</a> + <a href="thread.html#1062">[ thread ]</a> + <a href="subject.html#1062">[ subject ]</a> + <a href="author.html#1062">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Luca Berra a écrit : +><i> +</I>><i> On Sat, Oct 09, 2010 at 11:10:36AM +0200, Renaud MICHEL wrote: +</I>>><i> On samedi 09 octobre 2010 at 05:45, andré wrote : +</I>>>><i> Note that configuration files that have been changed from the +</I>>>><i> installation default are often already saved. (Generally ".old" is +</I>>>><i> appended to the configuration file name, sometimes ".new" to the new +</I>>>><i> configuration file.) +</I>>><i> +</I>>><i> But here you are only talking about system-wide configuration files, +</I>>><i> which are known of rpm as they are part of the package and marked as +</I>>><i> config files. +</I>>><i> But what about user specific configuration files? +</I>>><i> For the easy kind, where a program will have a single configuration +</I>>><i> file (or dedicated directory), a pre-inst script could find it in the +</I>>><i> home of each users and backup them. But you have cases of programs +</I>>><i> which have configuration scattered in multiple shared directories +</I>>><i> (like KDE), or even non-deterministic configuration files and it can +</I>>><i> become very tricky to find all the files to backup. +</I>>><i> And you have the really hard kind, where the same configuration file +</I>>><i> may be shared by different packages. For example, plasma applet +</I>>><i> configurations are stored in a few ~/.kde4/share/config/plasma* files. +</I>Good point. So user-specific configuration files would have to be taken +into account. +BTW, there is a similar complication for some Gnome packages. +So it would take a lot more time and effort to accommodate such rollbacks. +However most packages would be much simpler to reliably roll back. +So it seems useful that packages be marked as suitable for rollback (or +not). +><i> +1 +</I>><i> this is the very problem why i believe rollbacks are not that easy +</I>><i> +</I>Because the rollback will be automatic and must be very reliable, it is +not something to be taken lightly. A malfunctioning rollback would be +considerably worse than the current manual rollback process. + +Note that insisting that all backports depend on the same versions of +required packages as the distro release for which the backport is made +will considerably reduce one potential source of problems. As well, if +a new version of a particular application has important format changes, +perhaps there should be a policy of not making backports for it. +So candidates for rollbacks would be mostly restricted to applications +developped and tested for the current release of the distro. +Thus the utility of automated rollbacks would be considerably reduced. + +Another 2 cents :) + +- André (andre999) +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001060.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001069.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1062">[ date ]</a> + <a href="thread.html#1062">[ thread ]</a> + <a href="subject.html#1062">[ subject ]</a> + <a href="author.html#1062">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001063.html b/zarb-ml/mageia-dev/20101009/001063.html new file mode 100644 index 000000000..97045db1b --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001063.html @@ -0,0 +1,155 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB07F16.2000203%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001057.html"> + <LINK REL="Next" HREF="001064.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>andré</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB07F16.2000203%40laposte.net%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">andr55 at laposte.net + </A><BR> + <I>Sat Oct 9 16:41:26 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001057.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI>Next message: <A HREF="001064.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1063">[ date ]</a> + <a href="thread.html#1063">[ thread ]</a> + <a href="subject.html#1063">[ subject ]</a> + <a href="author.html#1063">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Frank Griffin a écrit : +><i> Part of the recent thread about what the desirable release cycle should +</I>><i> be devolved into a discussion of how backports works and whether or not +</I>><i> it's suitable. I'd like to examine this issue. +</I>><i> +</I>><i> The current urpmi repository architecture serves purposes that were +</I>><i> meaningful to Mandriva. It segregates main from contrib for statement +</I>><i> of support reasons, it separates non-free from main for philosophical +</I>><i> reasons, and it separates restricted from main for legal and business +</I>><i> reasons. +</I>><i> +</I>><i> This works pretty well for cooker, where you either want a particular +</I>><i> category of package considered or you don't, but the reuse of this model +</I>><i> for updates, backports, and testing in released versions isn't as good a +</I>><i> fit. +</I>><i> +</I>><i> The root of the problem is that the user base is different. Users of +</I>><i> cooker want the latest and greatest of everything, and have accepted +</I>><i> that if something breaks in cooker, it may stay broken for awhile. +</I>><i> Users of released versions vary all over the map, from people who never +</I>><i> want anything to change to people who want some specific updates to +</I>><i> people who want everything new but want it stable. Users of cooker +</I>><i> rarely think about security updates, because in grabbing everything +</I>><i> available constantly, the security updates are "just there". With users +</I>><i> of released versions, they may have to opt-in for security updates, and +</I>><i> usually want to treat other updates differently. +</I>><i> +</I>But wouldn't most users of cooker just take some packages from cooker to +install on their stable release ? Even if it's a computer used only for +testing purposes ? +><i> I'd like to propose the following model for updating released versions: +</I>><i> +</I>><i> 1) Users should not have to see, except in minor ways, the different +</I>><i> repositories. Urpmi may see them, and advanced or ideologically polar +</I>><i> users may care about them (e.g. free vs non-free), but most users +</I>><i> won't. Instead, let urpmi or rpmdrake have knowledge about all +</I>><i> repositories whether enabled or not, and display the offerings with an +</I>><i> icon, tooltip, or extra column that indicates the status of the package. +</I>><i> +</I>Lets assume that the GUI rpmdrake is used. +Instead of hiding the repositories (or partially hiding them as now done), +let's display the current selection on entering rpmdrake, BEFORE taking +the time to load and analyse the list of packages installed and +available on the selected repositories. +Add a checkbox to update for each repository. +They should be listed with a brief description, or have a description +available with context help. +The user then adjusts the selection as desired, before the loading/analysis. +If the user doesn't want to change the selection, they just press return. +Quick, easy - and the user always knows the options available and what +is selected. +And indeed, in the package list displayed it would be useful to have a +column for the source repository. +><i> 2) The update tool we give these users should distinguish between +</I>><i> security updates and backports/testing, but present them both. This is +</I>><i> very much like the Windows Update model, where all available fixes are +</I>><i> divided into "Critical System Updates" and "Software Updates". We don't +</I>><i> really have the same support constraints as Mandriva, and there's no +</I>><i> need to automatically disable backports across the board, and not even +</I>><i> present the backports as possibilities. +</I>><i> +</I>With a column displaying the source repository, only an option to +display updates is necessary, instead of the current "all updates", +"security updates", "correction of anomolies", and "general updates". +I would keep backports separate, as they are necessarily more problematic. +However I would make the remaining display options with checkboxes : +all, meta packages, graphic applications, updates, and backports. +as well, I would add all/installed/non-installed options to each line. +All these options to remember the last selection, for ease of use. +This way, the user sees all the display options in an easy to follow table. +><i> 3) Users should be able to enable options for each category +</I>><i> independently. Most users would probably want security updates applied +</I>><i> automatically, but would want to be notified of availability of +</I>><i> backports or testing and choose those manually. +</I>><i> +</I>For automatic selection of packages to install, that is how it works +now, which is fine. But the user should always have the option to +override the automatic selection. + +For example, gedit, the gnome default editor has an extention where the +latest version doesn't work properly for my purposes. An automatic +update installs the newer version, every time there is any type of +update to gedit. I had to use certain options of the command-line tool +to override this to reinstall the working version. And have to ensure +that the non-working extension is not installed during updates. + +BTW, a feature to blacklist the installation of a particular version of +a package would be very useful. I.e. an option "never install this +package" or "never select automatically this package". +This would prevent a package found to be problematic on a particular +system from being accidentally later installed on the system in question. + +- André (andre999) +</PRE> + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001057.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI>Next message: <A HREF="001064.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1063">[ date ]</a> + <a href="thread.html#1063">[ thread ]</a> + <a href="subject.html#1063">[ subject ]</a> + <a href="author.html#1063">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001064.html b/zarb-ml/mageia-dev/20101009/001064.html new file mode 100644 index 000000000..d0ba0f8cb --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001064.html @@ -0,0 +1,71 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB08183.9000108%40iki.fi%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001063.html"> + + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Thomas Backlund</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB08183.9000108%40iki.fi%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">tmb at iki.fi + </A><BR> + <I>Sat Oct 9 16:51:47 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001063.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1064">[ date ]</a> + <a href="thread.html#1064">[ thread ]</a> + <a href="subject.html#1064">[ subject ]</a> + <a href="author.html#1064">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>andré skrev 9.10.2010 17:41: +><i> BTW, a feature to blacklist the installation of a particular version of +</I>><i> a package would be very useful. I.e. an option "never install this +</I>><i> package" or "never select automatically this package". +</I>><i> This would prevent a package found to be problematic on a particular +</I>><i> system from being accidentally later installed on the system in question. +</I> +urpmi already have /etc/urpmi/skip.list, +so I guess a gui part is only missing. + +-- +Thomas +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001063.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + + <LI> <B>Messages sorted by:</B> + <a href="date.html#1064">[ date ]</a> + <a href="thread.html#1064">[ thread ]</a> + <a href="subject.html#1064">[ subject ]</a> + <a href="author.html#1064">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001065.html b/zarb-ml/mageia-dev/20101009/001065.html new file mode 100644 index 000000000..e1af7b1bb --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001065.html @@ -0,0 +1,70 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101009164225.GA18437%40maude.comedia.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001061.html"> + <LINK REL="Next" HREF="001066.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Luca Berra</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101009164225.GA18437%40maude.comedia.it%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">bluca at vodka.it + </A><BR> + <I>Sat Oct 9 18:42:25 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001061.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001066.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1065">[ date ]</a> + <a href="thread.html#1065">[ thread ]</a> + <a href="subject.html#1065">[ subject ]</a> + <a href="author.html#1065">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Oct 09, 2010 at 01:16:09PM +0000, Dick Gevers wrote: +><i>On Sat, 9 Oct 2010 12:28:44 +0200, Luca Berra wrote about Re: [Mageia-dev] +</I>><i>Proposal: Updating released versions (long post): +</I>><i> +</I>>><i>--repackage has been dropped from urpmi since it has been dropped from +</I>>><i>rpm 4.6 +</I>><i> +</I>><i>Will you post it in Mdv Bugzilla? +</I> +what for? + +-- +Luca Berra -- <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bluca at vodka.it</A> +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001061.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001066.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1065">[ date ]</a> + <a href="thread.html#1065">[ thread ]</a> + <a href="subject.html#1065">[ subject ]</a> + <a href="author.html#1065">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001066.html b/zarb-ml/mageia-dev/20101009/001066.html new file mode 100644 index 000000000..77ec6e4b8 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001066.html @@ -0,0 +1,73 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C201010091848.o99ImgL8068906%40smtp-vbr5.xs4all.nl%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001065.html"> + <LINK REL="Next" HREF="001067.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Dick Gevers</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C201010091848.o99ImgL8068906%40smtp-vbr5.xs4all.nl%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">dvgevers at xs4all.nl + </A><BR> + <I>Sat Oct 9 20:48:40 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001065.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001067.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1066">[ date ]</a> + <a href="thread.html#1066">[ thread ]</a> + <a href="subject.html#1066">[ subject ]</a> + <a href="author.html#1066">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, 9 Oct 2010 18:42:25 +0200, Luca Berra wrote about Re: [Mageia-dev] +Proposal: Updating released versions (long post): + +>>><i>--repackage has been dropped from urpmi since it has been dropped from +</I>>>><i>rpm 4.6 +</I>>><i> +</I>>><i>Will you post it in Mdv Bugzilla? +</I>><i> +</I>><i>what for? +</I> +To request / remember that urpmi should be fixed in this respect ? + +What else? :) + +Cheers, +=Dick Gevers= +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001065.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001067.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1066">[ date ]</a> + <a href="thread.html#1066">[ thread ]</a> + <a href="subject.html#1066">[ subject ]</a> + <a href="author.html#1066">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001067.html b/zarb-ml/mageia-dev/20101009/001067.html new file mode 100644 index 000000000..f6c55857a --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001067.html @@ -0,0 +1,81 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3CAANLkTi%3D-wD7dy7O4yhXuc0P7ePO5ob0eir_c_-UhD28e%40mail.gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001066.html"> + <LINK REL="Next" HREF="001068.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Ahmad Samir</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3CAANLkTi%3D-wD7dy7O4yhXuc0P7ePO5ob0eir_c_-UhD28e%40mail.gmail.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ahmadsamir3891 at gmail.com + </A><BR> + <I>Sat Oct 9 20:56:57 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001066.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001068.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1067">[ date ]</a> + <a href="thread.html#1067">[ thread ]</a> + <a href="subject.html#1067">[ subject ]</a> + <a href="author.html#1067">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On 9 October 2010 20:48, Dick Gevers <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dvgevers at xs4all.nl</A>> wrote: +><i> On Sat, 9 Oct 2010 18:42:25 +0200, Luca Berra wrote about Re: [Mageia-dev] +</I>><i> Proposal: Updating released versions (long post): +</I>><i> +</I>>>>><i>--repackage has been dropped from urpmi since it has been dropped from +</I>>>>><i>rpm 4.6 +</I>>>><i> +</I>>>><i>Will you post it in Mdv Bugzilla? +</I>>><i> +</I>>><i>what for? +</I>><i> +</I>><i> To request / remember that urpmi should be fixed in this respect ? +</I>><i> +</I>><i> What else?    :) +</I>><i> +</I>><i> Cheers, +</I>><i> =Dick Gevers= +</I>><i> +</I> +There is nothing to fix, rpm doesn't have the --repackage option any +more; urpmi can't use a feature that doesn't exist.... + +-- +Ahmad Samir +</PRE> + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001066.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001068.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1067">[ date ]</a> + <a href="thread.html#1067">[ thread ]</a> + <a href="subject.html#1067">[ subject ]</a> + <a href="author.html#1067">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001068.html b/zarb-ml/mageia-dev/20101009/001068.html new file mode 100644 index 000000000..ee41025ee --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001068.html @@ -0,0 +1,73 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101009190131.GA14796%40maude.comedia.it%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001067.html"> + <LINK REL="Next" HREF="001058.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Luca Berra</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C20101009190131.GA14796%40maude.comedia.it%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">bluca at vodka.it + </A><BR> + <I>Sat Oct 9 21:01:31 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001067.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001058.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1068">[ date ]</a> + <a href="thread.html#1068">[ thread ]</a> + <a href="subject.html#1068">[ subject ]</a> + <a href="author.html#1068">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Sat, Oct 09, 2010 at 06:48:40PM +0000, Dick Gevers wrote: +><i>On Sat, 9 Oct 2010 18:42:25 +0200, Luca Berra wrote about Re: [Mageia-dev] +</I>><i>Proposal: Updating released versions (long post): +</I>><i> +</I>>>>><i>--repackage has been dropped from urpmi since it has been dropped from +</I>>>>><i>rpm 4.6 +</I>>>><i> +</I>>>><i>Will you post it in Mdv Bugzilla? +</I>>><i> +</I>>><i>what for? +</I>><i> +</I>><i>To request / remember that urpmi should be fixed in this respect ? +</I>><i> +</I><A HREF="https://qa.mandriva.com/show_bug.cgi?id=61226">https://qa.mandriva.com/show_bug.cgi?id=61226</A> + +-- +Luca Berra -- <A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">bluca at vodka.it</A> +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001067.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001058.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1068">[ date ]</a> + <a href="thread.html#1068">[ thread ]</a> + <a href="subject.html#1068">[ subject ]</a> + <a href="author.html#1068">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001069.html b/zarb-ml/mageia-dev/20101009/001069.html new file mode 100644 index 000000000..eb29fe6ca --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001069.html @@ -0,0 +1,77 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB0CC4B.3030208%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001062.html"> + <LINK REL="Next" HREF="001055.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB0CC4B.3030208%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Sat Oct 9 22:10:51 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001062.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001055.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1069">[ date ]</a> + <a href="thread.html#1069">[ thread ]</a> + <a href="subject.html#1069">[ subject ]</a> + <a href="author.html#1069">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Luca Berra wrote: +><i> On Sat, Oct 09, 2010 at 11:10:36AM +0200, Renaud MICHEL wrote: +</I>>><i> +</I>>><i> But here you are only talking about system-wide configuration files, +</I>>><i> which are known of rpm as they are part of the package and marked as +</I>>><i> config files. +</I>>><i> But what about user specific configuration files? +</I>><i> +</I>><i> +1 +</I>><i> this is the very problem why i believe rollbacks are not that easy +</I>><i> +</I>The proposal included a recommendation for this, having the package +scripts do the equivalent of an "rpmnew"/"rpmold", but with +package-specific names. Note that in a rollback, any changes made to +the newer file would be lost, but that's unavoidable in any case since +they may not be supported by the old format. + +Fortunately, the number of packages that do this reformatting is +relatively small, and some of them (like NetBeans) create the newer +versions in new-release-specific subdirectories, leaving the old ones +intact. +</PRE> + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001062.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001055.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1069">[ date ]</a> + <a href="thread.html#1069">[ thread ]</a> + <a href="subject.html#1069">[ subject ]</a> + <a href="author.html#1069">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/001070.html b/zarb-ml/mageia-dev/20101009/001070.html new file mode 100644 index 000000000..dd4c5cc02 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/001070.html @@ -0,0 +1,79 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] Proposal: Updating released versions (long post) + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB0CE6C.8010908%40roadrunner.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="001054.html"> + <LINK REL="Next" HREF="001059.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] Proposal: Updating released versions (long post)</H1> + <B>Frank Griffin</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Proposal%3A%20Updating%20released%20versions%20%28long%20post%29&In-Reply-To=%3C4CB0CE6C.8010908%40roadrunner.com%3E" + TITLE="[Mageia-dev] Proposal: Updating released versions (long post)">ftg at roadrunner.com + </A><BR> + <I>Sat Oct 9 22:19:56 CEST 2010</I> + <P><UL> + <LI>Previous message: <A HREF="001054.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001059.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1070">[ date ]</a> + <a href="thread.html#1070">[ thread ]</a> + <a href="subject.html#1070">[ subject ]</a> + <a href="author.html#1070">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Marc Paré wrote: +><i> +</I>><i> I guess both of your suggestions would work André and Margot. +</I>><i> +</I>><i> So, this sounds like it could be something that could be worked out. I +</I>><i> would prefer, as a user, Margot's process. Of course the user would +</I>><i> have to be able to see the usage and re-claimed space due to his use +</I>><i> or Backports. Just to keep informed. +</I>All of this is way more complicated than it needs to be. + +The original proposal included a provision for leaving the post-release +backports packages on the backports mirror when a newer backport of that +package arrived, so that the older version could be downloaded if needed +for a rollback. + +I left out the option to cache old packages on the user's system +precisely to avoid arguments about space, but if you combine the two, +i.e. check the user's system and go to the mirror if it's not there, +then you can do something relatively simple, such as automatically +deleting local versions of packages after a certain amount of time. + +No need to prompt the user since the old package can always be retrieved +from the mirror, and it will be transparent to the user (except for +slightly slower response) where the package came from. +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="001054.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI>Next message: <A HREF="001059.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#1070">[ date ]</a> + <a href="thread.html#1070">[ thread ]</a> + <a href="subject.html#1070">[ subject ]</a> + <a href="author.html#1070">[ 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> diff --git a/zarb-ml/mageia-dev/20101009/author.html b/zarb-ml/mageia-dev/20101009/author.html new file mode 100644 index 000000000..b5f97d961 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/author.html @@ -0,0 +1,157 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 9 October 2010 Archive by author</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>9 October 2010 Archives by author</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Sat Oct 9 00:13:40 CEST 2010</i><br> + <b>Ending:</b> <i>Sat Oct 9 22:19:56 CEST 2010</i><br> + <b>Messages:</b> 22<p> + <ul> + +<LI><A HREF="001064.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1064"> </A> +<I>Thomas Backlund +</I> + +<LI><A HREF="001059.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1059"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001060.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1060"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001065.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1065"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001068.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1068"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001057.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1057"> </A> +<I>Oliver Burger +</I> + +<LI><A HREF="001061.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1061"> </A> +<I>Dick Gevers +</I> + +<LI><A HREF="001066.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1066"> </A> +<I>Dick Gevers +</I> + +<LI><A HREF="001049.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1049"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001069.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1069"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001070.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1070"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001058.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1058"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001053.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1053"> </A> +<I>Margot +</I> + +<LI><A HREF="001055.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1055"> </A> +<I>Margot +</I> + +<LI><A HREF="001051.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1051"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001054.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1054"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001056.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1056"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001067.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1067"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001050.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1050"> </A> +<I>andré +</I> + +<LI><A HREF="001052.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1052"> </A> +<I>andré +</I> + +<LI><A HREF="001062.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1062"> </A> +<I>andré +</I> + +<LI><A HREF="001063.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1063"> </A> +<I>andré +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Sat Oct 9 22:19:56 CEST 2010</i><br> + <b>Archived on:</b> <i>Sat Oct 9 22:20:03 CEST 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101009/date.html b/zarb-ml/mageia-dev/20101009/date.html new file mode 100644 index 000000000..0776da448 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/date.html @@ -0,0 +1,157 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 9 October 2010 Archive by date</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>9 October 2010 Archives by date</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Sat Oct 9 00:13:40 CEST 2010</i><br> + <b>Ending:</b> <i>Sat Oct 9 22:19:56 CEST 2010</i><br> + <b>Messages:</b> 22<p> + <ul> + +<LI><A HREF="001049.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1049"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001050.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1050"> </A> +<I>andré +</I> + +<LI><A HREF="001051.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1051"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001052.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1052"> </A> +<I>andré +</I> + +<LI><A HREF="001053.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1053"> </A> +<I>Margot +</I> + +<LI><A HREF="001054.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1054"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001055.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1055"> </A> +<I>Margot +</I> + +<LI><A HREF="001056.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1056"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001057.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1057"> </A> +<I>Oliver Burger +</I> + +<LI><A HREF="001058.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1058"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001059.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1059"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001060.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1060"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001061.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1061"> </A> +<I>Dick Gevers +</I> + +<LI><A HREF="001062.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1062"> </A> +<I>andré +</I> + +<LI><A HREF="001063.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1063"> </A> +<I>andré +</I> + +<LI><A HREF="001064.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1064"> </A> +<I>Thomas Backlund +</I> + +<LI><A HREF="001065.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1065"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001066.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1066"> </A> +<I>Dick Gevers +</I> + +<LI><A HREF="001067.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1067"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001068.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1068"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001069.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1069"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001070.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1070"> </A> +<I>Frank Griffin +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Sat Oct 9 22:19:56 CEST 2010</i><br> + <b>Archived on:</b> <i>Sat Oct 9 22:20:03 CEST 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101009/index.html b/zarb-ml/mageia-dev/20101009/index.html new file mode 120000 index 000000000..db4b46f72 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/index.html @@ -0,0 +1 @@ +thread.html
\ No newline at end of file diff --git a/zarb-ml/mageia-dev/20101009/subject.html b/zarb-ml/mageia-dev/20101009/subject.html new file mode 100644 index 000000000..a38587c20 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/subject.html @@ -0,0 +1,157 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 9 October 2010 Archive by subject</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>9 October 2010 Archives by subject</h1> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Sat Oct 9 00:13:40 CEST 2010</i><br> + <b>Ending:</b> <i>Sat Oct 9 22:19:56 CEST 2010</i><br> + <b>Messages:</b> 22<p> + <ul> + +<LI><A HREF="001049.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1049"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001050.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1050"> </A> +<I>andré +</I> + +<LI><A HREF="001051.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1051"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001052.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1052"> </A> +<I>andré +</I> + +<LI><A HREF="001053.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1053"> </A> +<I>Margot +</I> + +<LI><A HREF="001054.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1054"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001058.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1058"> </A> +<I>Renaud MICHEL +</I> + +<LI><A HREF="001059.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1059"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001060.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1060"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001061.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1061"> </A> +<I>Dick Gevers +</I> + +<LI><A HREF="001062.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1062"> </A> +<I>andré +</I> + +<LI><A HREF="001063.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1063"> </A> +<I>andré +</I> + +<LI><A HREF="001064.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1064"> </A> +<I>Thomas Backlund +</I> + +<LI><A HREF="001065.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1065"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001066.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1066"> </A> +<I>Dick Gevers +</I> + +<LI><A HREF="001067.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1067"> </A> +<I>Ahmad Samir +</I> + +<LI><A HREF="001068.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1068"> </A> +<I>Luca Berra +</I> + +<LI><A HREF="001069.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1069"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001070.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1070"> </A> +<I>Frank Griffin +</I> + +<LI><A HREF="001055.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1055"> </A> +<I>Margot +</I> + +<LI><A HREF="001056.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1056"> </A> +<I>Marc Paré +</I> + +<LI><A HREF="001057.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1057"> </A> +<I>Oliver Burger +</I> + + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Sat Oct 9 22:19:56 CEST 2010</i><br> + <b>Archived on:</b> <i>Sat Oct 9 22:20:03 CEST 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + <a href="thread.html#start">[ thread ]</a> + + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + diff --git a/zarb-ml/mageia-dev/20101009/thread.html b/zarb-ml/mageia-dev/20101009/thread.html new file mode 100644 index 000000000..6317e41d4 --- /dev/null +++ b/zarb-ml/mageia-dev/20101009/thread.html @@ -0,0 +1,193 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <title>The Mageia-dev 9 October 2010 Archive by thread</title> + <META NAME="robots" CONTENT="noindex,follow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <a name="start"></A> + <h1>9 October 2010 Archives by thread</h1> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p><b>Starting:</b> <i>Sat Oct 9 00:13:40 CEST 2010</i><br> + <b>Ending:</b> <i>Sat Oct 9 22:19:56 CEST 2010</i><br> + <b>Messages:</b> 22<p> + <ul> + +<!--0 01286576020- --> +<LI><A HREF="001049.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1049"> </A> +<I>Frank Griffin +</I> + +<UL> +<!--1 01286576020-01286595916- --> +<LI><A HREF="001050.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1050"> </A> +<I>andré +</I> + +<UL> +<!--2 01286576020-01286595916-01286599035- --> +<LI><A HREF="001051.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1051"> </A> +<I>Marc Paré +</I> + +<UL> +<!--3 01286576020-01286595916-01286599035-01286604918- --> +<LI><A HREF="001052.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1052"> </A> +<I>andré +</I> + +<!--3 01286576020-01286595916-01286599035-01286604918-01286607908- --> +<LI><A HREF="001053.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1053"> </A> +<I>Margot +</I> + +<!--3 01286576020-01286595916-01286599035-01286604918-01286607908-01286608359- --> +<LI><A HREF="001054.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1054"> </A> +<I>Marc Paré +</I> + +<!--3 01286576020-01286595916-01286599035-01286604918-01286607908-01286608359-01286655596- --> +<LI><A HREF="001070.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1070"> </A> +<I>Frank Griffin +</I> + +<!--3 01286576020-01286595916-01286599035-01286604918-01286607908-01286620124- --> +<LI><A HREF="001059.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1059"> </A> +<I>Luca Berra +</I> + +<!--3 01286576020-01286595916-01286599035-01286604918-01286607908-01286620124-01286630169- --> +<LI><A HREF="001061.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1061"> </A> +<I>Dick Gevers +</I> + +<!--3 01286576020-01286595916-01286599035-01286604918-01286607908-01286620124-01286630169-01286642545- --> +<LI><A HREF="001065.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1065"> </A> +<I>Luca Berra +</I> + +<!--3 01286576020-01286595916-01286599035-01286604918-01286607908-01286620124-01286630169-01286642545-01286650120- --> +<LI><A HREF="001066.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1066"> </A> +<I>Dick Gevers +</I> + +<!--3 01286576020-01286595916-01286599035-01286604918-01286607908-01286620124-01286630169-01286642545-01286650120-01286650617- --> +<LI><A HREF="001067.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1067"> </A> +<I>Ahmad Samir +</I> + +<!--3 01286576020-01286595916-01286599035-01286604918-01286607908-01286620124-01286630169-01286642545-01286650120-01286650891- --> +<LI><A HREF="001068.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1068"> </A> +<I>Luca Berra +</I> + +</UL> +<!--2 01286576020-01286595916-01286615436- --> +<LI><A HREF="001058.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1058"> </A> +<I>Renaud MICHEL +</I> + +<UL> +<!--3 01286576020-01286595916-01286615436-01286620364- --> +<LI><A HREF="001060.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1060"> </A> +<I>Luca Berra +</I> + +<!--3 01286576020-01286595916-01286615436-01286620364-01286631968- --> +<LI><A HREF="001062.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1062"> </A> +<I>andré +</I> + +<!--3 01286576020-01286595916-01286615436-01286620364-01286655051- --> +<LI><A HREF="001069.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1069"> </A> +<I>Frank Griffin +</I> + +</UL> +</UL> +</UL> +<!--0 01286611022- --> +<LI><A HREF="001055.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1055"> </A> +<I>Margot +</I> + +<UL> +<!--1 01286611022-01286612292- --> +<LI><A HREF="001056.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1056"> </A> +<I>Marc Paré +</I> + +<UL> +<!--2 01286611022-01286612292-01286613773- --> +<LI><A HREF="001057.html">[Mageia-dev] Release cycle - what is actually POSSIBLE? +</A><A NAME="1057"> </A> +<I>Oliver Burger +</I> + +</UL> +</UL> +<!--0 01286635286- --> +<LI><A HREF="001063.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1063"> </A> +<I>andré +</I> + +<UL> +<!--1 01286635286-01286635907- --> +<LI><A HREF="001064.html">[Mageia-dev] Proposal: Updating released versions (long post) +</A><A NAME="1064"> </A> +<I>Thomas Backlund +</I> + +</UL> + </ul> + <p> + <a name="end"><b>Last message date:</b></a> + <i>Sat Oct 9 22:19:56 CEST 2010</i><br> + <b>Archived on:</b> <i>Sat Oct 9 22:20:03 CEST 2010</i> + <p> + <ul> + <li> <b>Messages sorted by:</b> + + <a href="subject.html#start">[ subject ]</a> + <a href="author.html#start">[ author ]</a> + <a href="date.html#start">[ date ]</a> + <li><b><a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More info on this list... + </a></b></li> + </ul> + <p> + <hr> + <i>This archive was generated by + Pipermail 0.09 (Mailman edition).</i> + </BODY> +</HTML> + |