Merge branch 'master' into typed-os-requirements

5 files changed, 85 insertions, 0 deletions

diff --git a/doc/forum/chroot_issue_when_upgrading/comment_2_be3846f1cf7853beb486afc2077cd8b2._comment b/doc/forum/chroot_issue_when_upgrading/comment_2_be3846f1cf7853beb486afc2077cd8b2._comment
new file mode 100644
index 00000000..6999ceb1
--- /dev/null
+++ b/doc/forum/chroot_issue_when_upgrading/comment_2_be3846f1cf7853beb486afc2077cd8b2._comment
@@ -0,0 +1,29 @@
+[[!comment format=mdwn
+ username="picca"
+ subject="comment 2"
+ date="2016-03-29T16:58:05Z"
+ content="""
+Hello, joey now that I installed 2.17.1 I can test the fix but...
+
+    [2016-03-29 16:50:06 UTC] call: apt-get [\"update\"]
+    [2016-03-29 16:50:06 UTC] fgProcess (\"apt-get\",[\"update\"])
+    E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. 
+    [2016-03-29 16:50:07 UTC] fgProcess done (\"apt-get\",[\"update\"])
+    [2016-03-29 16:50:07 UTC] process done ExitFailure 100
+
+my property is
+
+    chroot = Chroot.debootstrapped Debootstrap.BuilddD chrootdir
+             & os system
+             & case proxy of
+                  (Just p) -> \"/etc/apt/apt.conf.d/01proxy\" `File.hasContent` [\"Acquire::http::Proxy \\"\" ++ p ++ \"\\";\"]
+                  Nothing -> doNothing
+             & Apt.installed [\"apt-transport-https\"]
+             & Apt.stdSourcesList
+             & Apt.update `onChange` Apt.upgrade
+             & Apt.cacheCleaned
+
+so it failes in the Apt.update and do not reach Apt.upgrade
+so it seems that update should be fixed also :)
+
+"""]]
diff --git a/doc/forum/chroot_issue_when_upgrading/comment_3_f902730900901dccdf2e290a176458f9._comment b/doc/forum/chroot_issue_when_upgrading/comment_3_f902730900901dccdf2e290a176458f9._comment
new file mode 100644
index 00000000..17c02fe7
--- /dev/null
+++ b/doc/forum/chroot_issue_when_upgrading/comment_3_f902730900901dccdf2e290a176458f9._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2016-03-29T20:49:32Z"
+ content="""
+Hmm, I don't ever remember seeing apt-get update need dpkg --configure -a.
+It's rather weird that it would; the files it updates are fully independent
+of the files dpkg does AIUI.
+"""]]
diff --git a/doc/forum/chroot_issue_when_upgrading/comment_4_4004abde37eb4bc7d845fb7bba2c635d._comment b/doc/forum/chroot_issue_when_upgrading/comment_4_4004abde37eb4bc7d845fb7bba2c635d._comment
new file mode 100644
index 00000000..65ca065e
--- /dev/null
+++ b/doc/forum/chroot_issue_when_upgrading/comment_4_4004abde37eb4bc7d845fb7bba2c635d._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="picca"
+ subject="comment 4"
+ date="2016-03-29T21:36:11Z"
+ content="""
+I found this in the apt code
+
+    #: apt-pkg/deb/debsystem.cc:82
+    msgid \"\"
+    \"dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct \"
+    \"the problem. \"
+    msgstr \"\"
+
+"""]]
diff --git a/doc/forum/chroot_issue_when_upgrading/comment_5_fe9deffb0cd356787fed33a373115f73._comment b/doc/forum/chroot_issue_when_upgrading/comment_5_fe9deffb0cd356787fed33a373115f73._comment
new file mode 100644
index 00000000..43f12d0f
--- /dev/null
+++ b/doc/forum/chroot_issue_when_upgrading/comment_5_fe9deffb0cd356787fed33a373115f73._comment
@@ -0,0 +1,26 @@
+[[!comment format=mdwn
+ username="picca"
+ subject="comment 5"
+ date="2016-03-29T21:41:50Z"
+ content="""
+Here the c++ code of apt
+
+    // See if we need to abort with a dirty journal
+    if (CheckUpdates() == true)
+    {
+       close(d->LockFD);
+       d->LockFD = -1;
+       const char *cmd;
+       if (getenv(\"SUDO_USER\") != NULL)
+          cmd = \"sudo dpkg --configure -a\";
+       else
+          cmd = \"dpkg --configure -a\";
+       // TRANSLATORS: the %s contains the recovery command, usually
+       //              dpkg --configure -a
+       return _error->Error(_(\"dpkg was interrupted, you must manually \"
+                              \"run '%s' to correct the problem. \"), cmd);
+    }
+
+so there is a dirty journal. (maybe due to a power off during the chroot update)
+
+"""]]
diff --git a/doc/forum/chroot_issue_when_upgrading/comment_6_262df826e5bbd0130964e0433fb172f2._comment b/doc/forum/chroot_issue_when_upgrading/comment_6_262df826e5bbd0130964e0433fb172f2._comment
new file mode 100644
index 00000000..00a282bf
--- /dev/null
+++ b/doc/forum/chroot_issue_when_upgrading/comment_6_262df826e5bbd0130964e0433fb172f2._comment
@@ -0,0 +1,7 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 6"""
+ date="2016-03-30T14:44:03Z"
+ content="""
+All right then, I've combined pendingConfigured into Apt.update.
+"""]]