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/20110323/003514.html | 102 ++++++++++++++++++++++++++++++++ 1 file changed, 102 insertions(+) create mode 100644 zarb-ml/mageia-dev/20110323/003514.html (limited to 'zarb-ml/mageia-dev/20110323/003514.html') diff --git a/zarb-ml/mageia-dev/20110323/003514.html b/zarb-ml/mageia-dev/20110323/003514.html new file mode 100644 index 000000000..e03ea53e2 --- /dev/null +++ b/zarb-ml/mageia-dev/20110323/003514.html @@ -0,0 +1,102 @@ + + + + [Mageia-dev] vbox/vboxadditions conflicts question + + + + + + + + + +

[Mageia-dev] vbox/vboxadditions conflicts question

+ Frank Griffin + ftg at roadrunner.com +
+ Wed Mar 23 14:19:14 CET 2011 +

+
+ +
On 03/23/2011 08:45 AM, Olivier Blin wrote:
+>
+> Don't you have x11 packages for vbox guest installed?
+>
+That was it, thanks.
+
+Apparently virtualbox-additions and the x11 package were forced on 
+during my post-installation processing.  Is there an rpm or urpmq query 
+that will highlight conflicts between installed packages on a system ?  
+For example, if I installed dkms-virtualbox and then installed 
+dkms-vboxadditions with --force, is there a query which would report 
+that these two are in conflict ?
+
+My post-installation processing installs over 1000 additional packages 
+to bring a fresh system up to the state of the system it is replacing, 
+and --force is necessary to prevent scores of bogus prompts.  It would 
+be convenient to be able to detect the remaining conflicts once the dust 
+has settled and the installs are finished so that any remaining 
+conflicts can be addressed manually.
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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