summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016696.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016696.html')
-rw-r--r--zarb-ml/mageia-dev/2012-June/016696.html126
1 files changed, 126 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016696.html b/zarb-ml/mageia-dev/2012-June/016696.html
new file mode 100644
index 000000000..073403813
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-June/016696.html
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3Cbb5cc8e93d2b81e7785024e9e422a124.squirrel%40mail.rmail.be%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="016699.html">
+ <LINK REL="Next" HREF="016697.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1>
+ <B>Maarten Vanraes</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%0A%20like%20--search-media&In-Reply-To=%3Cbb5cc8e93d2b81e7785024e9e422a124.squirrel%40mail.rmail.be%3E"
+ TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">maarten.vanraes at gmail.com
+ </A><BR>
+ <I>Thu Jun 21 13:30:10 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="016699.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI>Next message: <A HREF="016697.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16696">[ date ]</a>
+ <a href="thread.html#16696">[ thread ]</a>
+ <a href="subject.html#16696">[ subject ]</a>
+ <a href="author.html#16696">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>&gt;<i> 21.06.2012 13:35, AL13N kirjutas:
+</I>&gt;&gt;<i> B. fetch dependencies only from enabled repositories
+</I>&gt;&gt;<i> Problems:
+</I>&gt;&gt;<i> - if backports are enabled, dependencies could come from backports
+</I>&gt;&gt;<i> instead of release.
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> Solutions for this:
+</I>&gt;&gt;<i> - this can be prevented in various ways: even as simple as the backport
+</I>&gt;&gt;<i> packager to bump an update with stricter requires so that the backport
+</I>&gt;&gt;<i> wouldn't be fetched (_IF_ it indeed would be incompatible) AND the
+</I>&gt;&gt;<i> update
+</I>&gt;&gt;<i> could have stricter requires for that new dependency.
+</I>&gt;<i> I still can't see how are you going to solve this case:
+</I>&gt;<i> I have backports enabled. There are packages that are newer than the one
+</I>&gt;<i> in release. I
+</I>&gt;<i> haven't installed them. Now new update requires such package that is both
+</I>&gt;<i> in release and in
+</I>&gt;<i> backports. Update will pull package from enabled backports as they are
+</I>&gt;<i> newer - i didn't want
+</I>&gt;<i> that. And you can't just submit new backport that blocks it. Older
+</I>&gt;<i> backports are still
+</I>&gt;<i> there. So you can install those if new backport doesn't work for you (the
+</I>&gt;<i> same we have for
+</I>&gt;<i> updates at the moment).
+</I>
+IF the update cannot work with the backported new dependency, it should be
+strict required in the update. in that case, the one from release will be
+used.
+
+if the update does work with the backport, then i don't see why you
+wouldn't want that, since you enabled backports.
+==&gt; this sounds like cherry-picking backports.
+
+in other words, you're advanced enough to find out what you want, because
+i don't think we can support all forms of cherry-picking backports.
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="016699.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI>Next message: <A HREF="016697.html">[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#16696">[ date ]</a>
+ <a href="thread.html#16696">[ thread ]</a>
+ <a href="subject.html#16696">[ subject ]</a>
+ <a href="author.html#16696">[ 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>