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-April/014941.html | 91 +++++++++++++++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 zarb-ml/mageia-dev/2012-April/014941.html (limited to 'zarb-ml/mageia-dev/2012-April/014941.html') diff --git a/zarb-ml/mageia-dev/2012-April/014941.html b/zarb-ml/mageia-dev/2012-April/014941.html new file mode 100644 index 000000000..2306f781f --- /dev/null +++ b/zarb-ml/mageia-dev/2012-April/014941.html @@ -0,0 +1,91 @@ + + + + [Mageia-dev] testing beta3 + + + + + + + + + +

[Mageia-dev] testing beta3

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Fri Apr 27 10:34:46 CEST 2012 +

+
+ +
On 27 April 2012 10:04, Alberto Girlando <girlando at unipr.it> wrote:
+> 2) After finishing the installation, I clicked on the
+> possibility to upgrade to the latest version of the
+> software before rebooting. Although, being in VirtulaBox
+> with wired connection, the internet was on, the system
+> was unable to upgrade the software and went to a loop (bringing
+> up the network, then failed to upgrade, then retrying to bring
+> up the network and so on) so I simply shut down the machine. But on
+> reboot and logging, the system was unable to find the
+> database for the upgrade. So I reinstalled, and made the
+> upgrade after the first log in.
+
+You should have keep the install logs then open a bug report
+and attach those logs to this bug.
+Too late now :-(
+
+> I remember that also Mandriva had such a problem,
+> which I simply avoided making the upgrade after the
+> first log in. I believe that rather than tracking back
+> the bug, it is simply better to cancel the option to
+> upgrade the packages at the end of installation.
+
+No it should be fixed.
+
+ + + + + + + + + + + + + + + +
+

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