last day (14 days later) » 

21:19
0
A: Partial (specific releases) mirror of Ubuntu Archive via rsync only

sbergeronif you can install anything on the machine you are USING to transfer, try dpkg-repack, it will put all of the applications into .deb files that you can install on site on any debian based system on the transfer machine, run these commands $ sudo apt-get install dpkg-repack fakeroot $ mkdir ~/dp...

The box I am doing the download from is a Synology NAS. I don't have specific packages to install, but rather want to have the whole universe available for many machines on the isolated network
even on a one tb drive, I don't know how much of it will fit
That's a valid point; I have found references that "the Ubuntu Archive takes up about 680 GB of space." (help.ubuntu.com/community/Rsyncmirror) Not sure if that includes all of the available releases.
or dependencies, along with the fact that not all installs ONLY require the ubuntu repository
Also true; I plan on having to bring in some additional things, but would like to have as many of the core packages already there.
21:19
don't know how you would mirror that, it might just be better to get the package files instead of mirroring the repository in its own right
The mirroring process is not the issue, really.
I just want to find a way to limit the rsync to the portions that I need and make sure that it won't interfere with the way ubuntu will refer to the mirror
looks like lucid-updates was about 5GB
there isn't all that much difference in compatibility between 12 and 14, if you have the space then you could mirror the whole thing and the machines running 12 will automatically weed out the incompatible programs from view
right -- but for time and space sake, I'm trying to avoid mirroring the whole thing.
as in the difference is a matter of 2% of the total, all the others are unified I believe
does the rsync use links to avoid downloading multiple times?
(these are the types of things I'm not really sure of)
if that is the case, then I don't even really save much time by restricting the release.
but if it just downloads the same "unified" packages multiple times to put it once in /dist/precise and once in /dist/trusty ....
21:31
it is much like an APK file on android, it supports a certain range of versions, with ones for specific releases getting the folder of the earliest system they are supported on
ok
i think i see
also, the lts releases more or less have the same packages, or support for the same packages, just so that ubuntu can keep up supporting them
it doesn't download a separate package for 12.04, 12.10, 13.04, 13.10, 14.04, it just simplifies it by combining packages that are the same and puts them in the earliest place they are supported, with a marker if it does not support a specific release that comes later
i see.
so i suppose that is the work that debmirror is doing, to make sure that if you are syncing just a specific release, earlier support packages are also pulled in?
if you search for packages for a specific release, they could even be coming from the repo directory for an earlier release, but is still "supported" by your later release
so yes

last day (14 days later) »