summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2012-June/016692.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2012-June/016692.html')
-rw-r--r--zarb-ml/mageia-dev/2012-June/016692.html138
1 files changed, 138 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2012-June/016692.html b/zarb-ml/mageia-dev/2012-June/016692.html
new file mode 100644
index 000000000..e70f96963
--- /dev/null
+++ b/zarb-ml/mageia-dev/2012-June/016692.html
@@ -0,0 +1,138 @@
+<!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%20like%0A%20--search-media&In-Reply-To=%3Cf6aad89cbaf59290b807296ea7465136.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="016686.html">
+ <LINK REL="Next" HREF="016693.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media</H1>
+ <B>AL13N</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20bug%202317%20revisited%3A%20--update%20option%20should%20behave%20like%0A%20--search-media&In-Reply-To=%3Cf6aad89cbaf59290b807296ea7465136.squirrel%40mail.rmail.be%3E"
+ TITLE="[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media">alien at rmail.be
+ </A><BR>
+ <I>Thu Jun 21 12:35:59 CEST 2012</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="016686.html">[Mageia-dev] Problems with package versions
+</A></li>
+ <LI>Next message: <A HREF="016693.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#16692">[ date ]</a>
+ <a href="thread.html#16692">[ thread ]</a>
+ <a href="subject.html#16692">[ subject ]</a>
+ <a href="author.html#16692">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>see <A HREF="https://bugs.mageia.org/show_bug.cgi?id=2317">https://bugs.mageia.org/show_bug.cgi?id=2317</A>
+
+in short:
+I've provided a patch which does this, but there is discussion about it.
+Since the patch seems to indicate a change of behavior, people there
+requested this be mailed to -dev ML.
+
+so, it's about having new dependencies when you're doing updates and those
+dependencies are not in the update media.
+
+The way I see it, there 2 opinions:
+A. fetch dependencies only from enabled release/update repositories
+Problems:
+ - patch doesn't exist yet and code complexity is alot higher
+ - if backports are enabled, a dependency fetched from release could
+conflict with other installed (from backports or other). thus the update
+would fail.
+
+Solutions for this:
+ - this is not cleanly solvable, we would have to remove the backport.
+
+B. fetch dependencies only from enabled repositories
+Problems:
+ - if backports are enabled, dependencies could come from backports
+instead of release.
+
+Solutions for this:
+ - this can be prevented in various ways: even as simple as the backport
+packager to bump an update with stricter requires so that the backport
+wouldn't be fetched (_IF_ it indeed would be incompatible) AND the update
+could have stricter requires for that new dependency.
+
+
+IMHO, it's very simple: we should choose B because if you have backports
+enabled, you'd want the backport to be pulled for new dependency (IF it
+doesn't conflict).
+
+(in the above i state backports, but it could be any enabled repository,
+like testing, or even 3rd party repos.)
+
+In short, we shouldn't be thinking of cherrypicking backports, and if
+users are trusting repositories, we should be using them.
+
+since QA is waiting for a fix for this for a long time (pre-mga1), we
+should get this fixed asap.
+
+PS: since we're enabling backports, we should make sure that the update
+validation process would have one of both required tests for validation
+with backports enabled and the other disabled.
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="016686.html">[Mageia-dev] Problems with package versions
+</A></li>
+ <LI>Next message: <A HREF="016693.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#16692">[ date ]</a>
+ <a href="thread.html#16692">[ thread ]</a>
+ <a href="subject.html#16692">[ subject ]</a>
+ <a href="author.html#16692">[ 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>