summaryrefslogtreecommitdiff
path: root/doc/forum/chroot_issue_when_upgrading/comment_5_fe9deffb0cd356787fed33a373115f73._comment
blob: 43f12d0fc43d13feacbc83408107bc2a411b69f5 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
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)

"""]]