-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andrew Joakimsen さんは書きました: | On Thu, Oct 30, 2008 at 10:02 PM, Andrew Joakimsen wrote: | | Sorry for the flood of messages. I think my post was a little | confusing -- I have used the Squid proxy server and it does work, I | have just never tested it for downloading openSUSE updatates -- so I | am not 100% certain it will reduce your bandwidth usage as you desire, | but in theory it should. You might have to increase the default cache | size and cache object setting to insure the larger updates are cached | by it. Using squid would likely work but it seems that it would add at least one more update run to the whole process to get updates unique to each box. It's worth considering but I would like to keep the process as simple and straightforward as possible. == jd -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFJCwHghpL3F+HeDrIRAueaAJ4jpsHtPYaetlFZi0+2uacW/zpunQCgsjAB vGNXdGwI9iRRVqe42d1taoU= =LMF9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

On Thursday, 2008-10-30 at 19:01 -0700, j debert wrote:

...

How can I fetch all the updates required for both boxes once without having to become a repository and download everything--which would far exceed isp's limits. This would probably be some sort of proxy agent that can read the installed database for each box then fetch each package once and only once for both boxes. Is there yet a utility to do that?

This was a feature of Yast some versions back, but it has been lost. I believe that zypper can store permanently downloaded packages somewhere, but I don't recall how. I think this could be used to to the update first in one computer, copy over the downloaded rpms to the other machine, then run zypper again on that.

The zypper manual doesn't mention this :-?

-- Cheers, Carlos E. R.

Libzypp (yast and zypper) can keep packages in /var/cache/zypp/packages/ in a directory that matches the repository the rpms were downloaded from. For example if the file /etc/zypp/repos.d/packman.repo was the repository description file for http://ftp.skynet.be/pub/packman/suse/11.0/ and the section in the file keeppackages was set to keeppackages=1 then the directory /var/cache/zypp/packages/packman/i586 wil contain all rpms that libzypp downloads from http://ftp.skynet.be/pub/packman/suse/11.0/i586/ . These packages can be moved to another directory and that directory turned into a local repository with the createrepo command. zypper has a -k option used with zypper ar to add repos with keeppackages set to 1 Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R. wrote:

On Friday, 2008-10-31 at 14:10 +0200, Dave Plater wrote:

...

Libzypp (yast and zypper) can keep packages in /var/cache/zypp/packages/ in a directory that matches the repository the rpms were downloaded from. For example if the file /etc/zypp/repos.d/packman.repo was the repository description file for http://ftp.skynet.be/pub/packman/suse/11.0/ and the section in the file keeppackages was set to keeppackages=1 then the directory /var/cache/zypp/packages/packman/i586 wil contain all rpms that libzypp downloads from http://ftp.skynet.be/pub/packman/suse/11.0/i586/ . These packages can be moved to another directory and that directory turned into a local repository with the createrepo command. zypper has a -k option used with zypper ar to add repos with keeppackages set to 1

Ahhhh! That's it.

And... if i manually copy the files from /var/cache/zypp/packages/packman/i586 from one computer to another, will those be picked locally instead of downloaded?

A trick we used time ago was to publish that directory rw via nfs, and use it on all the computers, but i don't know how willthat work with libzyp :-?

-- Cheers, Carlos E. R.

You can specify where the cache directory is in /etc/zypp/zypp.conf but I don't think the reuse cached files was working properly in 11.0. In 11.1 libzypp checks if the file is in the cache already and doesn't download it again, with this feature you could specify a common cache on a server for all machines and as long as you don't do simultaneous updates the packages will be reused. Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos E. R. さんは書きました: | | This was a feature of Yast some versions back, but it has been lost. I | believe that zypper can store permanently downloaded packages somewhere, | but I don't recall how. I think this could be used to to the update | first in one computer, copy over the downloaded rpms to the other | machine, then run zypper again on that. | I remember it from 9.something. It was gone by 10.something. If zypper can keep packages, it doesn't say how to tell it to. Even if zypper can keep packages it is still a chore to sort out which packages are common with the other box, copy them there, run the updates, update the installed db, then run yast again to fetch the remaining updates and hopefully not download the common packages again. I've attempted to do something like this before and yast never failed to download and install already installed packages. IIRC, the reason seemed to be that the repo db was not updated or did not agree with the installed db. What I had in mind, I think, is a proxy to get the repo db and package updates and redistribute them to each box by either pretending to be a repo or by pushing the updates onto each box or something. Whatever way is simpler, easier, elegant, less time consuming, etc. The boxes are not identical and perhaps about 90% of the packages are the same. == jd -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFJCwnnhpL3F+HeDrIRAhjTAJ93+MInYj58gYxFuzPQbdtgPIPfNwCgsSHM +EnxsWdWdvYa7org/7sAo/0= =+5Bt -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org