diff options
| author | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
|---|---|---|
| committer | Nicolas Vigier <boklm@mageia.org> | 2013-04-14 13:46:12 +0000 |
| commit | 1be510f9529cb082f802408b472a77d074b394c0 (patch) | |
| tree | b175f9d5fcb107576dabc768e7bd04d4a3e491a0 /zarb-ml/mageia-sysadm/2011-August/003874.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-master.tar archives-master.tar.gz archives-master.tar.bz2 archives-master.tar.xz archives-master.zip | |
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-August/003874.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2011-August/003874.html | 102 |
1 files changed, 102 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-August/003874.html b/zarb-ml/mageia-sysadm/2011-August/003874.html new file mode 100644 index 000000000..4684e2295 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-August/003874.html @@ -0,0 +1,102 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] Possible failure in our update process + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Possible%20failure%20in%20our%20update%20process&In-Reply-To=%3Cop.v0fcn1xkn7mcit%40hodgins.homeip.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="003873.html"> + <LINK REL="Next" HREF="003875.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Possible failure in our update process</H1> + <B>David W. Hodgins</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Possible%20failure%20in%20our%20update%20process&In-Reply-To=%3Cop.v0fcn1xkn7mcit%40hodgins.homeip.net%3E" + TITLE="[Mageia-sysadm] Possible failure in our update process">davidwhodgins at gmail.com + </A><BR> + <I>Thu Aug 18 21:34:39 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003873.html">[Mageia-sysadm] Possible failure in our update process +</A></li> + <LI>Next message: <A HREF="003875.html">[Mageia-sysadm] Package removal request: jgraphx +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3874">[ date ]</a> + <a href="thread.html#3874">[ thread ]</a> + <a href="subject.html#3874">[ subject ]</a> + <a href="author.html#3874">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Thu, 18 Aug 2011 11:46:06 -0400, John Balcaen <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">mikala at mageia.org</A>> wrote: + +><i> Since most of actors of the QA are simply installing all packages from +</I>><i> core/updates_testing (like me) none of us noticed that it would break +</I>><i> without KDE 4.6.5 installed and when probably for first updates +</I>><i> people are using a « fresh Mageia 1» , with several packages in +</I>><i> updates_testing in the same moment we can't really expect them to +</I>><i> removed or reinstall/restore a Mageia 1 for every package available in +</I>><i> testing. +</I> +Ouch. Guilty. + +Proper testing would require keeping an image that only gets updated when +packages are pushed from Testing to Updates, and always using that as a +starting point when installing an update from Testing. + +For people who can run Mageia under VirtualBox, it would simply be a matter +of using snapshots, to maintain the testing environment (for updates that +don't require access to real hardware). For those of us who can't, we'll +have to handle that with equivalent imaging/restore. + +In most cases updates don't interfere with each other, and the current +system is ok. + +Large updates, like kde, which affect a large number of packages, and take +quite a bit of time to test, are different. + +Creating a separate repository, just for that type update, is a very good +idea, as it makes it much easier to install all of that update, and only that +update, and would simplify ensuring all needed packages are selected, when +pushing from updates testing to updates. + +I'm in favour of using a separate repository. If mostly automated, that +would be good for all updates. If it's going to require more work for +the developers though, it may be better to only use the separate repository +for large updates like kde. + +Regards, Dave Hodgins +</PRE> + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003873.html">[Mageia-sysadm] Possible failure in our update process +</A></li> + <LI>Next message: <A HREF="003875.html">[Mageia-sysadm] Package removal request: jgraphx +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3874">[ date ]</a> + <a href="thread.html#3874">[ thread ]</a> + <a href="subject.html#3874">[ subject ]</a> + <a href="author.html#3874">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |