diff options
Diffstat (limited to 'zarb-ml/mageia-dev/2011-October/008867.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-October/008867.html | 160 |
1 files changed, 160 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-October/008867.html b/zarb-ml/mageia-dev/2011-October/008867.html new file mode 100644 index 000000000..361e6ab9e --- /dev/null +++ b/zarb-ml/mageia-dev/2011-October/008867.html @@ -0,0 +1,160 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] [qa-discuss] Packages requiring linking for updates already in Core Updates + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bqa-discuss%5D%20Packages%20requiring%20linking%20for%0A%09updates%20already%20in%20Core%20Updates&In-Reply-To=%3C201110150024.57708.stormi%40laposte.net%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="008692.html"> + <LINK REL="Next" HREF="008962.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] [qa-discuss] Packages requiring linking for updates already in Core Updates</H1> + <B>Samuel Verschelde</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bqa-discuss%5D%20Packages%20requiring%20linking%20for%0A%09updates%20already%20in%20Core%20Updates&In-Reply-To=%3C201110150024.57708.stormi%40laposte.net%3E" + TITLE="[Mageia-dev] [qa-discuss] Packages requiring linking for updates already in Core Updates">stormi at laposte.net + </A><BR> + <I>Sat Oct 15 00:24:57 CEST 2011</I> + <P><UL> + <LI>Previous message: <A HREF="008692.html">[Mageia-dev] [qa-discuss] Packages requiring linking for updates already in Core Updates +</A></li> + <LI>Next message: <A HREF="008962.html">[Mageia-dev] [qa-discuss] Packages requiring linking for updates already in Core Updates +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8867">[ date ]</a> + <a href="thread.html#8867">[ thread ]</a> + <a href="subject.html#8867">[ subject ]</a> + <a href="author.html#8867">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Le samedi 8 octobre 2011 22:55:49, vous avez écrit : +><i> On Sat, Oct 8, 2011 at 10:56 AM, Samuel Verschelde <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">stormi at laposte.net</A>> +</I>wrote: +><i> > Hi, +</I>><i> > +</I>><i> > I ran Claire's depcheck script (in its latest version) against all +</I>><i> > packages in Core Updates. It ran almost all night, and here are the +</I>><i> > results: +</I>><i> > +</I>[...] +><i> +</I>><i> i beg to disagree with all this because you act like if ppl were +</I>><i> installing from scratch the rpms from updates. +</I> +That's not true: we're doing as if the people only have basesystem-minimal + X ++ rpmdrake + the package being updated and all its dependencies, recursively. +Except in case of a bug in our script, the listed packages are not present in +such a system before the update, and are required from Release media for the +update. + +If we were doing as if people were installing from scratch, the list would be +the output of urpmq --requires-recursive, just test and check that there's a +really huge difference :) + + +><i> ( like : +</I>><i> +</I>><i> +</I>><i> *** kdebase4-workspace-devel *** +</I>><i> ---------------------------------------- +</I>><i> Running checks for "kdebase4-workspace-devel" using media +</I>><i> "Core Release" and "Core Updates". +</I>><i> ---------------------------------------- +</I>><i> Mageia release 1 (Official) for i586 +</I>><i> Latest version found in "Core Release" is kdebase4-workspace- +</I>><i> devel-4.6.3-7.mga1 +</I>><i> Latest version found in "Core Updates" is kdebase4-workspace- +</I>><i> devel-4.6.5-1.3.mga1 +</I>><i> ---------------------------------------- +</I>><i> The following packages will require linking: +</I>><i> +</I>><i> canberra-common-0.27-2.mga1 (Core Release) +</I>><i> libbluez3-4.92-1.mga1 (Core Release) +</I>><i> libcanberra0-0.27-2.mga1 (Core Release) +</I>><i> libcln6-1.3.1-2.mga1 (Core Release) +</I>><i> libdmtx0-0.7.2-1.mga1 (Core Release) +</I>><i> libgpsd19-2.95-4.mga1 (Core Release) +</I>><i> liblm_sensors4-3.2.0-1.mga1 (Core Release) +</I>><i> libpolkit-qt-agent-1_1-0.99.0-1.mga1 (Core Release) +</I>><i> libqalculate5-0.9.7-7.mga1 (Core Release) +</I>><i> libqalculate-data-0.9.7-7.mga1 (Core Release) +</I>><i> libqimageblitz4-0.0.6-3.mga1 (Core Release) +</I>><i> libsmbclient0-3.5.8-1.mga1 (Core Release) +</I>><i> libssh4-0.4.7-1.mga1 (Core Release) +</I>><i> libtalloc2-2.0.5-2.mga1 (Core Release) +</I>><i> libwbclient0-3.5.8-1.mga1 (Core Release) +</I>><i> mageia-kde-translation-1-2.mga1 (Core Release) +</I>><i> polkit-kde-agent-1-0.99.0-2.mga1 (Core Release) +</I>><i> sound-theme-freedesktop-0.7-5.mga1 (Core Release) +</I>><i> xmessage-1.0.3-2.mga1 (Core Release) +</I>><i> +</I>><i> +</I>><i> mageia-kde-translation is for ex alrady required by kde in mageia and +</I>><i> not only added in updates, so ALL ppl having kde install WILL have it +</I>><i> installed so linking this is useless, and i think this can be valid +</I>><i> for a lot of deps listed too. +</I> +Either there's a bug in our script, or kdebase4-workspace-devel in Core +Release didn't require any of those packages, directly or via its +dependencies. + +Now, we probably can find lots of cases where there's a "high" chance that some +of the listed packages are already present on the user system, and those can +be discussed. But the QA team already put hours and hours of work trying to +workaround bug #2317 so I hope it's not a big deal if we link a few packages +more than what is really needed for most users. Trying to be more precise (and +we already are quite precise) would just make us go insane (and next step we'd +all stop validating packages to go learn perl and rpmdrake internals in order +to change MageiaUpdate's behaviour). + + +><i> +</I>><i> For vuze: +</I>><i> +</I>><i> apache-commons-cli-1.2-5.mga1 (Core Release) +</I>><i> liblog4j-java-1.2.16-13.mga1 (Core Release) +</I>><i> log4j-1.2.16-13.mga1 (Core Release) +</I>><i> xml-commons-apis-1.4.01-5.mga1 (Core Release) +</I>><i> +</I>><i> i think ( i can be wrong ) that all those packages were already +</I>><i> required by vuze ) +</I>><i> because then, why not add java6 too :) +</I> +They weren't required according to urpmq --requires-recursive, but there's a +limitation in urpmq --requires-recursive when there are alternatives : if +package A requires B or C, then urpmq won't list the dependencies of B and C +recursively. Some call that a bug, I prefer to call that a "how the hell could +we do differently?" feature :) + +Best regards + +Samuel +</PRE> + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="008692.html">[Mageia-dev] [qa-discuss] Packages requiring linking for updates already in Core Updates +</A></li> + <LI>Next message: <A HREF="008962.html">[Mageia-dev] [qa-discuss] Packages requiring linking for updates already in Core Updates +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#8867">[ date ]</a> + <a href="thread.html#8867">[ thread ]</a> + <a href="subject.html#8867">[ subject ]</a> + <a href="author.html#8867">[ 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> |