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-January/010999.html | 95 +++++++++++++++++++++++++++++ 1 file changed, 95 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-January/010999.html (limited to 'zarb-ml/mageia-dev/2012-January/010999.html') diff --git a/zarb-ml/mageia-dev/2012-January/010999.html b/zarb-ml/mageia-dev/2012-January/010999.html new file mode 100644 index 000000000..1bd509b2d --- /dev/null +++ b/zarb-ml/mageia-dev/2012-January/010999.html @@ -0,0 +1,95 @@ + + + + [Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2 + + + + + + + + + +

[Mageia-dev] [changelog] [RPM] cauldron core/release dsniff-2.4-0.b1.1.mga2

+ Angelo Naselli + anaselli at linux.it +
+ Thu Jan 5 23:58:26 CET 2012 +

+
+ +
> 1 week ago, anyone who would have upgraded to mga2 with dsniff installed
+> from mdv would have been in the exact same situation than now, except
+> nobody cared at all. And the proof that nobody cared is that nobody
+> pushed the rpm sooner. Would it have been pushed to 1, yes, that would
+> have breached what we agreed to do. But it was not pushed to 1 ( and I
+> would say "likely on purpose" ). So the only change with this upload is
+> for people installing dsniff later.
+mga1 is not dead yet, so if someone who install mga1 now, could ask for dsniff
+and that should go to update since it is in mdv2010, right? That could be a 
+problem imho... there always could be one person who upgrade from mdv2010 
+later... 
+
+-- 
+	Angelo
+-------------- next part --------------
+A non-text attachment was scrubbed...
+Name: not available
+Type: application/pgp-signature
+Size: 198 bytes
+Desc: This is a digitally signed message part.
+URL: </pipermail/mageia-dev/attachments/20120105/582967df/attachment.asc>
+
+ + + + + + + + + + + + + + + + + + + + + +
+

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