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/003873.html | |
| parent | fa5098cf210b23ab4f419913e28af7b1b07dafb2 (diff) | |
| download | archives-1be510f9529cb082f802408b472a77d074b394c0.tar archives-1be510f9529cb082f802408b472a77d074b394c0.tar.gz archives-1be510f9529cb082f802408b472a77d074b394c0.tar.bz2 archives-1be510f9529cb082f802408b472a77d074b394c0.tar.xz archives-1be510f9529cb082f802408b472a77d074b394c0.zip | |
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-August/003873.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2011-August/003873.html | 113 |
1 files changed, 113 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-August/003873.html b/zarb-ml/mageia-sysadm/2011-August/003873.html new file mode 100644 index 000000000..fd80888b2 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-August/003873.html @@ -0,0 +1,113 @@ +<!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=%3CCABV-EOvAr_1q7afqhn0nBWHXkMXWEmRkk3qYbAhELU5XK%3DAcRg%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="003872.html"> + <LINK REL="Next" HREF="003874.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Possible failure in our update process</H1> + <B>John Balcaen</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Possible%20failure%20in%20our%20update%20process&In-Reply-To=%3CCABV-EOvAr_1q7afqhn0nBWHXkMXWEmRkk3qYbAhELU5XK%3DAcRg%40mail.gmail.com%3E" + TITLE="[Mageia-sysadm] Possible failure in our update process">mikala at mageia.org + </A><BR> + <I>Thu Aug 18 17:46:06 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003872.html">[Mageia-sysadm] Error on LO side this night +</A></li> + <LI>Next message: <A HREF="003874.html">[Mageia-sysadm] Possible failure in our update process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3873">[ date ]</a> + <a href="thread.html#3873">[ thread ]</a> + <a href="subject.html#3873">[ subject ]</a> + <a href="author.html#3873">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Hello, + +I noticed a problem with our update process thanks to bug #2450 [1] +Here we pushed a update to kipi-plugins package (due to a missing +requires) but the update ends up in a totally broken installation for +the end user which was not noticed by me (first in fault) & later by +QA. + +Currently every package built for updates are done against +core/release, core/updates and core/updates_testing, here when i +pushed kipi-plugins update, KDE 4.6.5 was already available in +core/updates_testing so as expected kipi-plugins get linked against +KDE 4.6.5 & not against KDE 4.6.3 (available in core/release) +Since most of actors of the QA are simply installing all packages from +core/updates_testing (like me) none of us noticed that it would break + without KDE 4.6.5 installed and when probably for first updates +people are using a « fresh Mageia 1» , with several packages in +updates_testing in the same moment we can't really expect them to +removed or reinstall/restore a Mageia 1 for every package available in +testing. + +A workaround (which could also ease work for QA people) would be to +have some temporary repositories as suggested by bolkm on irc, it +could be based on SRPM package name but for some project like KDE it +would need more hacks since RPMS needed to be builded in a specific +order. + +The QA user will be able to simply add a new media (like +urpmi.addmedia $mirror/core/updates_testing/packagetotest/ ) so it +will be more easy to test a package & *only* this one. + +Another solution is to rebuild the package when moving in on +core/updates_release but in that case the package tested by QA is of +course not the same as the one available previously in testing. + +What do you think ? + + + + + + + +[1] <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2450">https://bugs.mageia.org/show_bug.cgi?id=2450</A> + + +-- +Balcaen John +Jabber-id: <A HREF="https://www.mageia.org/mailman/listinfo/mageia-sysadm">mikala at jabber.littleboboy.net</A> +</PRE> + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003872.html">[Mageia-sysadm] Error on LO side this night +</A></li> + <LI>Next message: <A HREF="003874.html">[Mageia-sysadm] Possible failure in our update process +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3873">[ date ]</a> + <a href="thread.html#3873">[ thread ]</a> + <a href="subject.html#3873">[ subject ]</a> + <a href="author.html#3873">[ 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> |