apt-clone makes changes to non-cloned environment
Bug #308640 reported by
Tim Spriggs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nexenta Operating System |
In Progress
|
Undecided
|
Erast |
Bug Description
While attempting an upgrade from elatte-unstable (fully updated) to hardy-unstable apt/dpkg are upgraded in the current environment and not the cloned env. apt/dpkg break from bad dependencies and the live root env is badly broken. apt-clone should not touch apt/dpkg in the live installation, only the clone environment.
To post a comment you must log in.
By default, apt-clone will only try to switch to "safe" upgrade mode if some of the core/important packages detected. In all other cases it will not be different from apt-get dist-upgrade + some manual tweaking. To force apt-clone always use ZFS clone for "safe" operation use provided "-s" flag.