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/016714.html | 141 +++++++++++++++++++++++++++++++ 1 file changed, 141 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-June/016714.html (limited to 'zarb-ml/mageia-dev/2012-June/016714.html') diff --git a/zarb-ml/mageia-dev/2012-June/016714.html b/zarb-ml/mageia-dev/2012-June/016714.html new file mode 100644 index 000000000..3e36b22bf --- /dev/null +++ b/zarb-ml/mageia-dev/2012-June/016714.html @@ -0,0 +1,141 @@ + + + + [Mageia-dev] bug 2317 revisited: --update option should behave like --search-media + + + + + + + + + +

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

+ AL13N + alien at rmail.be +
+ Thu Jun 21 19:39:25 CEST 2012 +

+
+ +
Op donderdag 21 juni 2012 17:36:58 schreef Thierry Vignaud:
+> On 21 June 2012 17:27, AL13N <alien at rmail.be> wrote:
+> >> You claim that it's not  supported.
+> >> But cherry picking one backport is usually what people do.
+> >> 
+> >> Denying the reality won't help you make progress...
+> > 
+> > well, this time we agreed to have supported backports.
+> > 
+> > it is true that almost all devs are cherry-picking backports, but are real
+> > users going to do that? i doubt it, but we don't have any data about this
+> > in any case.
+> 
+> End users do not know about urpmi.
+> They knows about mgaupdate which shows them updates and about
+> rpmdrake which shows everything.
+> Thy _ONLY_ way for them to get a backport package installed is to
+> manually select one.
+> Period.
+
+actually, that could change, i think it was stormi who proposed to adjust 
+mgaapplet to handle "backports for end users".
+
+> > the reality is that if you want supported backports, there's literally no
+> > way of testing if all combinations of cherrypicking will work or not.
+> > thus, there is no other way solution than to support only having backports
+> > or not.
+> 
+> That's bogus.
+> The truth is and always has been: if you install a backport package, it's
+> unsupported, it's at your own risks.
+> Claiming we support backports would be a like: we won't retest all existing
+> backported packages when pushing a new one.
+
+this is exactly my point. but it's been decided several times in several 
+meetings (even since before mga1) that backports would be supported now.
+
+There's even a policy accepted about QA on backports. I guess you didn't 
+follow the meetings or read up on the meeting logs?
+
+[...]
+> NACK. That's totally bogus.
+> Enabling the backport media DOES NOT imply "I want to install every
+> backports".
+> You're twisting the reality and the existing experience in order to match
+> your goals. That won't work...
+
+i'm not twisting anything.
+
+the only way you ever have supported backports, is that you only support 
+installing all backports that have packages in release.
+
+If you find another way to support backports, please let us know.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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