[15:11] realtime-neil: Did you try something along the lines of the apt offline howto that I pointed at? [15:12] realtime-neil: apt will certainly respect version requirements [15:21] cjwatson: I'm looking at that now [15:22] cjwatson: I'm looking at this 21-year-old documentation and firmly believe that everything old is new again [15:28] cjwatson: I ran into some search interference with `apt-offline`, which seems like a completely different tool inspired by the documentation you linked. [16:27] realtime-neil: It's certainly possible that apt-offline is better. I was suggesting that documentation mainly as a toolkit of ideas for how to drive apt in the right way rather than necessarily as a fully-tested script [16:28] cjwatson: understood, and I'm working my way through the documented example as a way to familiarize myself with The Right Way. I'll move on to `apt-offline` once I master the basics. [16:36] You can also give it a fake status file (maybe even an empty one) to force apt to really download everything, though it's possible that might get a bit confused; probably better if it at least has essential packages to go on [16:38] I'll try it with a straight copy and then an empty to see what happens with the `*.list` files I give it. [17:08] cjwatson: would it make sense to "seed" this kind of faked offline installation with a "bare-bones" `/var/lib/dpkg/status`; i.e., a dpkg status file that represents the minimal set of packages on a vanilla installation? [17:08] cjwatson: If so, how would one acquire such a minimal dpkg status file? [17:36] realtime-neil: Maybe. I guess I might start by running an existing system's file through "grep-dctrl -wFTask ubuntu-minimal" or some such. [17:38] cjwatson: I had the idea of using deboostrap to generate a minimal rootfs and then harvest the `/var/lib/dpkg/status` from that, but your idea seems better