summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-discuss/attachments/20120524/0ae6db84
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-discuss/attachments/20120524/0ae6db84')
-rw-r--r--zarb-ml/mageia-discuss/attachments/20120524/0ae6db84/attachment-0001.html5
-rw-r--r--zarb-ml/mageia-discuss/attachments/20120524/0ae6db84/attachment.html5
2 files changed, 10 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/attachments/20120524/0ae6db84/attachment-0001.html b/zarb-ml/mageia-discuss/attachments/20120524/0ae6db84/attachment-0001.html
new file mode 100644
index 000000000..2a44ff3ab
--- /dev/null
+++ b/zarb-ml/mageia-discuss/attachments/20120524/0ae6db84/attachment-0001.html
@@ -0,0 +1,5 @@
+Hi all,<br><br>yesterday, as expected, I got on my desktop the notification that a new release was available. When I launched the upgrade, a window opened with two checkboxes: one for downloading all the packages before starting to install them, and one for something else which I don&#39;t remember right now.<br>
+
+<br>I checked none, but I guess I should have checked the &quot;download first&quot; one. Never mind about this.<br><br>As it was late, and it was going to be a long task, I went to sleep hoping to find my system upgraded in the morning. In the morning I found a small window saying that the installation of 2 packages had failed and buttons to abort or continue. I clicked on continue and the task went on. That window blocked the whole installation during most of the night.<br>
+<br>Now I&#39;m at work hoping to find my system upgraded at the end of the day, but I&#39;m afraid that the window waiting for an answer pops up again and blocks my upgrade.<br><br>So I wonder if it would be possible to avoid this situation for the next mayor release (Mageia 3). I can imagine that the initial window could have a third checkbox that users could check to tell the applet (or urpmi, I don&#39;t know which handles this) to continue on errors (just as it they had pressed the Continue button) and show a list of errors at the end; but other solutions might also work.<br>
+<br>Well, this is my proposition. What do you people think about it?<br><br><br>Alejandro.<br>
diff --git a/zarb-ml/mageia-discuss/attachments/20120524/0ae6db84/attachment.html b/zarb-ml/mageia-discuss/attachments/20120524/0ae6db84/attachment.html
new file mode 100644
index 000000000..2a44ff3ab
--- /dev/null
+++ b/zarb-ml/mageia-discuss/attachments/20120524/0ae6db84/attachment.html
@@ -0,0 +1,5 @@
+Hi all,<br><br>yesterday, as expected, I got on my desktop the notification that a new release was available. When I launched the upgrade, a window opened with two checkboxes: one for downloading all the packages before starting to install them, and one for something else which I don&#39;t remember right now.<br>
+
+<br>I checked none, but I guess I should have checked the &quot;download first&quot; one. Never mind about this.<br><br>As it was late, and it was going to be a long task, I went to sleep hoping to find my system upgraded in the morning. In the morning I found a small window saying that the installation of 2 packages had failed and buttons to abort or continue. I clicked on continue and the task went on. That window blocked the whole installation during most of the night.<br>
+<br>Now I&#39;m at work hoping to find my system upgraded at the end of the day, but I&#39;m afraid that the window waiting for an answer pops up again and blocks my upgrade.<br><br>So I wonder if it would be possible to avoid this situation for the next mayor release (Mageia 3). I can imagine that the initial window could have a third checkbox that users could check to tell the applet (or urpmi, I don&#39;t know which handles this) to continue on errors (just as it they had pressed the Continue button) and show a list of errors at the end; but other solutions might also work.<br>
+<br>Well, this is my proposition. What do you people think about it?<br><br><br>Alejandro.<br>