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

[Mageia-dev] vbox/vboxadditions conflicts question

+ Olivier Blin + mageia at blino.org +
+ Wed Mar 23 13:45:40 CET 2011 +

+
+ +
Frank Griffin <ftg at roadrunner.com> writes:
+
+> I understand that virtualbox and vbox additions cannot both be
+> installed on the same system because of conflicts.  But why, when I
+> try to update a system with virtualbox installed and vboxadditions not
+> installed, do I get prompts about vboxadditions not being installable
+> ?  What is asking for it ?
+>
+> For example:
+>
+> [root at ftgme2 release]# rpm -qa dkms-vboxadditions
+> [root at ftgme2 release]# rpm -qa dkms-virtualbox
+> dkms-virtualbox-4.0.4-6.mga1
+> [root at ftgme2 release]# urpmi --auto-select --keep
+> A requested package cannot be installed:
+> dkms-vboxadditions-4.0.4-6.mga1.x86_64 (in order to keep
+> dkms-virtualbox-4.0.4-6.mga1.x86_64)
+> Continue installation anyway? (Y/n)
+
+Don't you have x11 packages for vbox guest installed?
+
+-- 
+Olivier Blin - blino
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+

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