summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2011-December/010418.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2011-December/010418.html')
-rw-r--r--zarb-ml/mageia-dev/2011-December/010418.html153
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 &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">dan at coneharvesters.com</A>&gt; wrote:
+&gt;<i> On Wed, Dec 14, 2011 at 09:49:15AM +0200, Buchan Milne wrote:
+</I>&gt;&gt;<i> This is unsupported. Maybe you should instead contribute documentation that
+</I>&gt;&gt;<i> makes this more explicitly obvious, but it is a well-known rule in Mandriva and
+</I>&gt;&gt;<i> Mageia (and usually applies to other distros as well).
+</I>&gt;<i>
+</I>&gt;<i> I can understand that my particular case is unsupported, but I described
+</I>&gt;<i> a different, supported, scenario that would also fail due to this problem.
+</I>&gt;<i> To reiterate, a distribution upgrade from 1 to 2 (once it's finalized)
+</I>&gt;<i> could involve urpmi first upgrading the perl-dependent package but avoid
+</I>&gt;<i> installing the new perl itself until the end of the upgrade, which could be
+</I>&gt;<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.
+
+&gt;<i> During the entirety of that time,
+</I>&gt;<i> that package would be unusable. If that package happened to be a key CGI
+</I>&gt;<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.
+
+&gt;&gt;<i> If this weren't the case, there wouldn't be a need for backports ...
+</I>&gt;<i>
+</I>&gt;<i> Backports are nice in that they are leaf packages that don't generally
+</I>&gt;<i> require a ton of newer libraries be installed as well. Installing a
+</I>&gt;<i> single package of any complexity from a newer distribution often results
+</I>&gt;<i> in a cascading series of new packages to resolve all the dependencies.
+</I>&gt;<i> But it's often expeditious to upgrade simpler packages in that way in
+</I>&gt;<i> cases when the system can't completely upgraded right away.
+</I>&gt;<i>
+</I>&gt;<i> It's possible to handle that kind of case reliably, but I understand that
+</I>&gt;<i> it would be more work to get the dependencies just right. Many library
+</I>&gt;<i> authors put plenty of effort into maintaining binary compatibility across
+</I>&gt;<i> releases just so this sort of thing is possible. But even if this isn't an
+</I>&gt;<i> officially-supported mode of operation, problems like the one I described
+</I>&gt;<i> above can still result in broken systems if the dependencies aren't
+</I>&gt;<i> correctly described.
+</I>&gt;<i>
+</I>&gt;&gt;<i> Installing packages individually from one release on another release is not
+</I>&gt;&gt;<i> supported. Either upgrade the entire distro first, or stick to packages from
+</I>&gt;&gt;<i> the version you are on. However 'upgrade from release to Cauldron', when done
+</I>&gt;&gt;<i> correctly, should usually work as expected.
+</I>&gt;<i>
+</I>&gt;<i> Yes, &quot;usually&quot;. Is Mageia the operating system that works reliably 95% of the
+</I>&gt;<i> time?
+</I>&gt;<i>
+</I>&gt;&gt;<i> But, in supported use cases, urpmi *does* ensure that all the pieces to keep
+</I>&gt;&gt;<i> urpmi are upgraded in one transaction.
+</I>&gt;<i>
+</I>&gt;<i> But only if the dependencies are set correctly. And my original bug report on
+</I>&gt;<i> that has just now been closed as WONTFIX.
+</I>&gt;<i>
+</I>&gt;&gt;<i> Supporting the use case of installing any random package from a different
+</I>&gt;&gt;<i> release will take more effort than just adding and maintaining a version on one
+</I>&gt;&gt;<i> perl-base dependency.
+</I>&gt;<i>
+</I>&gt;<i> Yes, it will, but it can be automated to a certain extent. There just has to be
+</I>&gt;<i> a will to make sure that even the corner cases work.
+</I>&gt;<i>
+</I>&gt;&gt;&gt;&gt;<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>