Have to load Trinity on a new machine with Debian 6, with internet - no problems. Also have to update some machines running deb 5 KDE where there is no internet and have a identical machine with internet access. Update no problems (reload with wad of DVD's), not sure how to load Trinity
My linux/unix knowledge is not good although have used linux as a prime desktop for 12 years but with not much debian experience.
Only idea at present is to run apt-get -d install desktop-base-trinity kde-trinity >tdeload. followed by /var/cache/apt/archives to a DVD then - on another machine to HD at /var/cache/apt/archives
EITHER put /var/cache/apt/archives in sources.list apt-get -install desktop-base-trinity kde-trinity
OR cd /var/cache/apt/archives dpkg -i desktop-base-trinity dpkg -i kde-trinity
OR redo tdeload. as script, in order, for dpkg
There is probably a better/easier method which I haven't thought of and don't want to find problems which involve satphones ($$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ worse than that seattle mob)
On Sunday 19 February 2012 13:16:33 jc wrote:
Have to load Trinity on a new machine with Debian 6, with internet - no problems. Also have to update some machines running deb 5 KDE where there is no internet and have a identical machine with internet access. Update no problems (reload with wad of DVD's), not sure how to load Trinity
IMHO, it should be sufficient to just copy the whole /var/cache/apt directory from an up-to-date machine with trinity installed to one without internet connection. then just do apt-get install desktop-base-trinity kde-trinity there. will of course only work with same debian version on target machine (same sources.list configuration also recommended) and complete /var/cache/apt/archives directory (including .deb packages for dependencies).
werner
On Sunday 19 February 2012 13:34:04 Werner Joss wrote:
IMHO, it should be sufficient to just copy the whole /var/cache/apt directory from an up-to-date machine with trinity installed to one without internet connection.
additional note: /var/lib/apt/lists/* should also be copied to the target. the *.bin files in /var/cache/apt are not really necessary, as it seems.
werner
On Sunday 19 February 2012 12:34:04 Werner Joss wrote:
On Sunday 19 February 2012 13:16:33 jc wrote:
Have to load Trinity on a new machine with Debian 6, with internet - no problems. Also have to update some machines running deb 5 KDE where there is no internet and have a identical machine with internet access. Update no problems (reload with wad of DVD's), not sure how to load Trinity
IMHO, it should be sufficient to just copy the whole /var/cache/apt directory from an up-to-date machine with trinity installed to one without internet connection. then just do apt-get install desktop-base-trinity kde-trinity there. will of course only work with same debian version on target machine (same sources.list configuration also recommended) and complete /var/cache/apt/archives directory (including .deb packages for dependencies).
werner
I think you'll find that apt-get will need some controlling package list files to identify the TDE packages to work.
However, once you've upgraded the base Debian installation I think you should be able to just install all of the TDE packages using dpkg.
Try copying all of the TDE .deb packages into an empty/new temporary folder somewhere, cd into that folder and then do: dpkg -i *.deb
This _should_ work but I make no promises. However, this is what I had to do this when I upgraded to TDE 3.5.13 and then needed to downgrade back to 3.5.12 after finding a few important problems.
I though I'd try the easiest option first, so I located all of the TDE 3.5.12 .deb package files, copied them into a folder on their own (so I wasn't installing anything else) and then used dpkg -i *.deb to install all of the (3.5.12) .deb packages in that folder (if you have any other non-tde .deb packages in that folder then dpkg -i *.deb will try to install those as well, which may not be a good idea.
Note that I was doing a downgrade, which meant that any dependencies for 3.5.12 might have been met by the existing 3.5.13 versions, whereas if you're upgrading you might hit some dependency issues. If this happens then rerunning the dpkg -i command should eventually get them all sorted out; although some packages may not be installed due to dependency issues during a run of dpkg -i the packages that they are dependent upon should install ok. Depending upon how many levels of dependency there are you may need to run the dpkg -i command several times.
Like I said though - no promises - and try it on a non-critical system first!!!
LeeE
-
jc -
leee -
Werner Joss