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-dev/2011-December/010418.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-dev/2011-December/010418.html')
| -rw-r--r-- | zarb-ml/mageia-dev/2011-December/010418.html | 153 |
1 files changed, 153 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2011-December/010418.html b/zarb-ml/mageia-dev/2011-December/010418.html new file mode 100644 index 000000000..397f73764 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-December/010418.html @@ -0,0 +1,153 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-dev] How broken are RPM dependencies allowed to be? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20broken%20are%20RPM%20dependencies%20allowed%20to%20be%3F&In-Reply-To=%3CCA%2BCX%2BbjrYaSc%2BMm5ER5HME5UPHTf5gE%3DsrJXyWJeSF-hawckpA%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="010416.html"> + <LINK REL="Next" HREF="010429.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-dev] How broken are RPM dependencies allowed to be?</H1> + <B>Pascal Terjan</B> + <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20How%20broken%20are%20RPM%20dependencies%20allowed%20to%20be%3F&In-Reply-To=%3CCA%2BCX%2BbjrYaSc%2BMm5ER5HME5UPHTf5gE%3DsrJXyWJeSF-hawckpA%40mail.gmail.com%3E" + TITLE="[Mageia-dev] How broken are RPM dependencies allowed to be?">pterjan at gmail.com + </A><BR> + <I>Wed Dec 14 12:30:33 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="010416.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI>Next message: <A HREF="010429.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10418">[ date ]</a> + <a href="thread.html#10418">[ thread ]</a> + <a href="subject.html#10418">[ subject ]</a> + <a href="author.html#10418">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>On Wed, Dec 14, 2011 at 09:14, Dan Fandrich <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dan at coneharvesters.com</A>> wrote: +><i> On Wed, Dec 14, 2011 at 09:49:15AM +0200, Buchan Milne wrote: +</I>>><i> This is unsupported. Maybe you should instead contribute documentation that +</I>>><i> makes this more explicitly obvious, but it is a well-known rule in Mandriva and +</I>>><i> Mageia (and usually applies to other distros as well). +</I>><i> +</I>><i> I can understand that my particular case is unsupported, but I described +</I>><i> a different, supported, scenario that would also fail due to this problem. +</I>><i> To reiterate, a distribution upgrade from 1 to 2 (once it's finalized) +</I>><i> could involve urpmi first upgrading the perl-dependent package but avoid +</I>><i> installing the new perl itself until the end of the upgrade, which could be +</I>><i> hours or (if interrupted) days later. +</I> +During an upgrade urpmi starts by updating what it uses (perl, rpm, +few other things, itself) and then restarts. + +><i> During the entirety of that time, +</I>><i> that package would be unusable. If that package happened to be a key CGI +</I>><i> script for a web site, the entire site would be down for that entire time. +</I> +That would not be prevented. The result would be that you need to +install thousands of packages in the same transaction as they are all +required by each other, and nothing would prevent your CGI from being +at the end of the transaction which will happen hours or days later. + +>><i> If this weren't the case, there wouldn't be a need for backports ... +</I>><i> +</I>><i> Backports are nice in that they are leaf packages that don't generally +</I>><i> require a ton of newer libraries be installed as well. Installing a +</I>><i> single package of any complexity from a newer distribution often results +</I>><i> in a cascading series of new packages to resolve all the dependencies. +</I>><i> But it's often expeditious to upgrade simpler packages in that way in +</I>><i> cases when the system can't completely upgraded right away. +</I>><i> +</I>><i> It's possible to handle that kind of case reliably, but I understand that +</I>><i> it would be more work to get the dependencies just right. Many library +</I>><i> authors put plenty of effort into maintaining binary compatibility across +</I>><i> releases just so this sort of thing is possible. But even if this isn't an +</I>><i> officially-supported mode of operation, problems like the one I described +</I>><i> above can still result in broken systems if the dependencies aren't +</I>><i> correctly described. +</I>><i> +</I>>><i> Installing packages individually from one release on another release is not +</I>>><i> supported. Either upgrade the entire distro first, or stick to packages from +</I>>><i> the version you are on. However 'upgrade from release to Cauldron', when done +</I>>><i> correctly, should usually work as expected. +</I>><i> +</I>><i> Yes, "usually". Is Mageia the operating system that works reliably 95% of the +</I>><i> time? +</I>><i> +</I>>><i> But, in supported use cases, urpmi *does* ensure that all the pieces to keep +</I>>><i> urpmi are upgraded in one transaction. +</I>><i> +</I>><i> But only if the dependencies are set correctly. And my original bug report on +</I>><i> that has just now been closed as WONTFIX. +</I>><i> +</I>>><i> Supporting the use case of installing any random package from a different +</I>>><i> release will take more effort than just adding and maintaining a version on one +</I>>><i> perl-base dependency. +</I>><i> +</I>><i> Yes, it will, but it can be automated to a certain extent. There just has to be +</I>><i> a will to make sure that even the corner cases work. +</I>><i> +</I>>>>><i> Dan +</I></PRE> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="010416.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI>Next message: <A HREF="010429.html">[Mageia-dev] How broken are RPM dependencies allowed to be? +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#10418">[ date ]</a> + <a href="thread.html#10418">[ thread ]</a> + <a href="subject.html#10418">[ subject ]</a> + <a href="author.html#10418">[ 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> |