Package: apt-clone
Version: 0.4.1
Severity: wishlist
Dear Maintainer,
* What led up to the situation?
Wanted to clone a preconfigured system where the source does use 1 package
and 3-4 dependencies from newer release only by using apt-pinning,
aswell some packages from 3rd party sources valid for sources current release
* What exactly did you do (or not do) that was effective (or
ineffective)?
followed the instructions to create apt-clone archive, which perfectly
saved preferences file and sources lists,
tried to apt-clone restore .tar.gz
* What was the outcome of this action?
first attempt it ignored apt-pinning and then pulled stuff preferable from
newer release
tampering with preference file lead to apt-clone not installing any package
at all because apt was feared of breaking stuff
* What outcome did you expect instead?
restore apt-preferences file and install packages as they were selected on
source e.g. source had package 1 from stable
so install that from stable aswell, package2 from unstable so install that
from unstable aswell ...
-- System Information:
Debian Release: 9.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (499, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.4.83-1-pve (SMP w/8 CPU cores)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages apt-clone depends on:
ii lsb-release 9.20161125
ii python3 3.5.3-1
ii python3-apt 1.4.0~beta3
Versions of packages apt-clone recommends:
ii dpkg-repack 1.43
apt-clone suggests no packages.
-- debconf information excluded
