From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2012-June/016755.html | 118 +++++++++++++++++++++++++++++++ 1 file changed, 118 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-June/016755.html (limited to 'zarb-ml/mageia-dev/2012-June/016755.html') diff --git a/zarb-ml/mageia-dev/2012-June/016755.html b/zarb-ml/mageia-dev/2012-June/016755.html new file mode 100644 index 000000000..997560c7c --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016755.html @@ -0,0 +1,118 @@ + + + + [Mageia-dev] bug 2317 revisited: --update option should behave like --search-media + + + + + + + + + +

[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media

+ Claire Robinson + eeeemail at gmail.com +
+ Fri Jun 22 18:29:19 CEST 2012 +

+
+ +
On 22/06/12 17:00, AL13N wrote:
+> Op vrijdag 22 juni 2012 14:46:17 schreef Sander Lepik:
+>> 22.06.2012 13:53, AL13N kirjutas
+>>
+>>> I do agree with you here, except that i'm trying to prevent this from
+>>> happening, because it's not something that can be easily fixed.
+>>>
+>>> 1. package A is backported into X
+>>> 1b. package A-foo is backported into X-foo (subpackage)
+>>> 2. package B is updated into Y at a later date
+>>> 3. package update Y has a new dependency A-foo
+>>> 4. person has X installed; but didn't install X-foo.
+>>> 5. person updates B into Y
+>>>
+>>> result is that Y pulls in as new dependency A-foo
+>>>
+>>> but X conflicts with A-foo
+>>>
+>>> so the update does not happen, and you get an ugly error.
+>>
+>> Yes, that's what happens when you use backports. But this case can be
+>> solved. Person having this problem will install X-foo from backports and
+>> case is probably closed (yes! this is what you have to do if you are using
+>> backports). If not then s/he is still on his/her own as we are dealing with
+>> backports. It's not something you can make bulletproof (and we really
+>> shouldn't waste too much time on it).
+>
+> which is exactly my point, this is not being "supported" at all...
+
+Perhaps "tested" is a better word :)
+
+Claire
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1