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/2011-July/006717.html | 140 +++++++++++++++++++++++++++++++ 1 file changed, 140 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-July/006717.html (limited to 'zarb-ml/mageia-dev/2011-July/006717.html') diff --git a/zarb-ml/mageia-dev/2011-July/006717.html b/zarb-ml/mageia-dev/2011-July/006717.html new file mode 100644 index 000000000..f1aba1c0f --- /dev/null +++ b/zarb-ml/mageia-dev/2011-July/006717.html @@ -0,0 +1,140 @@ + + + + [Mageia-dev] How to forbid submission of some tainted packages to core ? + + + + + + + + + +

[Mageia-dev] How to forbid submission of some tainted packages to core ?

+ Samuel Verschelde + stormi at laposte.net +
+ Sat Jul 16 12:16:51 CEST 2011 +

+
+ +
Le samedi 16 juillet 2011 12:12:15, Michael Scherer a écrit :
+> Le samedi 16 juillet 2011 à 11:42 +0200, Samuel Verschelde a écrit :
+> > Le samedi 16 juillet 2011 02:45:04, Michael Scherer a écrit :
+> > > Le samedi 16 juillet 2011 à 01:17 +0200, Samuel Verschelde a écrit :
+> > > > Some packages must be submitted only to tainted. Is there already a
+> > > > way to prevent a wrong submit to the core section, when a package
+> > > > builds without buildrequires in tainted ?
+> > > > 
+> > > > If yes, what is the way, and if not, shouldn't we define a standard
+> > > > way to do that in the spec files ?
+> > > 
+> > > We could add a requies to some dummy rpm that is present in tainted
+> > > only.
+> > > 
+> > > But I think this problem would not occurs often. If someone push it
+> > > without saying where to go, it should go to the proper repository.
+> > > 
+> > > And if someone push it to core, we should assume that he know what he
+> > > does. There is no way to push by error to core, as you would need to
+> > > add specific option ( iirc ).
+> > 
+> > You mean that I can type "mdvsys submit transcode" and it will know that
+> > it must not go to core but to tainted ? Based on what information ?
+> 
+> Based on the fact the package is already in tainted, iirc.
+> 
+> It was the case in mandriva for contribs/main, so it should still work.
+
+Can I test ? And if the package lands into core, are you ready to delete it ? 
+:)
+
+Samuel
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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