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-June/005326.html | 150 +++++++++++++++++++++++++++++++ 1 file changed, 150 insertions(+) create mode 100644 zarb-ml/mageia-dev/2011-June/005326.html (limited to 'zarb-ml/mageia-dev/2011-June/005326.html') diff --git a/zarb-ml/mageia-dev/2011-June/005326.html b/zarb-ml/mageia-dev/2011-June/005326.html new file mode 100644 index 000000000..c113a5684 --- /dev/null +++ b/zarb-ml/mageia-dev/2011-June/005326.html @@ -0,0 +1,150 @@ + + + + [Mageia-dev] Missing packages in Mageia 1. How to backport? + + + + + + + + + +

[Mageia-dev] Missing packages in Mageia 1. How to backport?

+ Michael Scherer + misc at zarb.org +
+ Fri Jun 10 12:29:28 CEST 2011 +

+
+ +
Le vendredi 10 juin 2011 à 09:56 +0100, Colin Guthrie a écrit :
+> 'Twas brillig, and Ahmad Samir at 09/06/11 17:42 did gyre and gimble:
+
+> > But if new package can go directly to updates.. that doesn't look
+> > right to me, because at which point will "new" packages stop going to
+> > a stable release */updates? if it goes on and on, then we're talking
+> > about a semi-cauldron-like repo.
+> 
+> So just svn cp it to the /1/updates tree in svn and job's a good 'un.
+> (well svn cp is no longer just one step due to source separation, but
+> the principle is the same!).
+
+The bin repository is a different svn, so it will not work.
+
+
+-- 
+Michael Scherer
+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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