[opensuse] Caching updates locally/Local update server
Hi Everyone, I need to update my opensuse machines at times, and the uplink is not so good as it through VSAT links. I was looking for a place where the online updater stores its files, but I could not find any location. The files seemed to be temporarily stored in /var/adm/mount/..., but then once the update was over, these files got automatically removed. If there is no option for creating an automated local update server, I think I would have to manage with locally cached rpms, but then, even for locally cached rpms, which location can I find them in, and what would be a good idea to manage my updates for a LAN? The funny thing is: in Yast2, when I go to Patch->All in this list, I see that the option Keep has been selected. However, the rpms do not seem to appear anywhere. Can anyone help me out with this? Thanks, Prajjwal Message Disclaimer: This electronic message may contain confidential information. If you have received it in error, please immediately inform the sender and delete the mail and any attachments. Unless it relates to the official business of UMN, any opinions, views and other information expressed in this document are those of the individual sender. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, 2007-04-13 at 15:07 +0545, Prajjwal Devkota wrote:
Can anyone help me out with this?
I have seen them in /var/lib/YaST2/you/mnt But, you must be sure that you have not checked the button in YAST that causes them to be deleted after they are installed. I have a script that makes a CD of this directory. Then I can use that CD to do the update in systems not on the 'net. The only downside is that when an update is updated, both updates will be here. Yast will still do the right thing, but the amount of data can get big. I never found a way to weed out updates in this directory that are no longer needed. I think you can also export this directory locally and add it as a source on other systems. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Tel: Int +46 8-615 60 20 Fax: Int +46 8-31 42 23 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Roger, Thanks for your reply.
I have seen them in /var/lib/YaST2/you/mnt
I tried to find rpm files in the following locations: /var/lib/Yast2, /var/lib/zypp, and /var/lib/zmd: none seem to have any rpms. The command I used was find. The directory /var/lib/Yast2 does exist, but it only has two subdirectories: imported, and backup_boot_sectors. No directory called you exists within Yast2.
But, you must be sure that you have not checked the button in YAST that causes them to be deleted after they are installed.
Here is what I did: 1. Go to Yast2->Online Updates 2. Made sure that the "Keep" was checked in the "Patch" menu and the "Package" menu. However, that seems to be related with keeping an installed package. I cannot find any other option to do so. I am still looking around.
I have a script that makes a CD of this directory. Then I can use that CD to do the update in systems not on the 'net.
I would love to use your script if you could share it after my update rpms are found and kept).
The only downside is that when an update is updated, both updates will be here. Yast will still do the right thing, but the amount of data can get big. I never found a way to weed out updates in this directory that are no longer needed.
I had a similar script for Fedora Core5, so I might be able to figure that out hopefully :).
I think you can also export this directory locally and add it as a source on other systems.
Thanks for your help. I hope to hear from you soon, Prajjwal Message Disclaimer: This electronic message may contain confidential information. If you have received it in error, please immediately inform the sender and delete the mail and any attachments. Unless it relates to the official business of UMN, any opinions, views and other information expressed in this document are those of the individual sender. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-04-13 at 13:14 +0200, Roger Oberholtzer wrote:
I have seen them in /var/lib/YaST2/you/mnt
But, you must be sure that you have not checked the button in YAST that causes them to be deleted after they are installed.
No matter what I do, they are always deleted. That click box is ignored :-/ - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGJmFetTMYHG2NR9URArGKAJ4uZiYYVscfgozzE0640z2bV9f/9ACgg/Kp /83kovLHIDNJyz4JfyT/kBI= =ITiQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
That is an inconvenience: I found out that I need to update every opensuse 10.2 system for the following reasons: a. After joining to a windows domain, removable device access fails (apparently HAL policy problem) b. Evolution keeps asking for password when connecting to Microsoft Exchange Lets see if I can isolate the patches required, or find another way to cache updates. Does anyone have any idea about using yum/smart to do the same? I plan to look into that soon. Prajjwal On Wed, 2007-04-18 at 20:20 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2007-04-13 at 13:14 +0200, Roger Oberholtzer wrote:
I have seen them in /var/lib/YaST2/you/mnt
But, you must be sure that you have not checked the button in YAST that causes them to be deleted after they are installed.
No matter what I do, they are always deleted. That click box is ignored :-/
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFGJmFetTMYHG2NR9URArGKAJ4uZiYYVscfgozzE0640z2bV9f/9ACgg/Kp /83kovLHIDNJyz4JfyT/kBI= =ITiQ -----END PGP SIGNATURE-----
Message Disclaimer: This electronic message may contain confidential information. If you have received it in error, please immediately inform the sender and delete the mail and any attachments. Unless it relates to the official business of UMN, any opinions, views and other information expressed in this document are those of the individual sender. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Everyone, I am just using this script as a starting point: just pulling all the patch rpms that are available in the updates repository. Maybe I will rewrite it to pull only the installed rpms later, but I hope it will work as a starting point to get things working. My HAL cdrom access problem is already solved this way: patchdownload.sh #!/bin/bash BASEURL="http://ftp5.gwdg.de/pub/suse/update/10.2/rpm/i586/" WORKDIR=/usr/local/src/updates/patchrpms/ cd $WORKDIR #get list of rpms from the patch directory wget -c $BASEURL #compile a list of patch rpms awk -Fhref= '/patch.rpm/{print $2}' index.html|awk -F\" '{print $2}'>list #and pull rpms while read line do wget -c $BASEURL/$line done<list Let me know if I am doing something the "too long" way round. Prajjwal On Fri, 2007-04-20 at 08:47 +0545, Prajjwal Devkota wrote:
That is an inconvenience: I found out that I need to update every opensuse 10.2 system for the following reasons: a. After joining to a windows domain, removable device access fails (apparently HAL policy problem) b. Evolution keeps asking for password when connecting to Microsoft Exchange Lets see if I can isolate the patches required, or find another way to cache updates. Does anyone have any idea about using yum/smart to do the same? I plan to look into that soon.
Prajjwal
On Wed, 2007-04-18 at 20:20 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2007-04-13 at 13:14 +0200, Roger Oberholtzer wrote:
I have seen them in /var/lib/YaST2/you/mnt
But, you must be sure that you have not checked the button in YAST that causes them to be deleted after they are installed.
No matter what I do, they are always deleted. That click box is ignored :-/
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFGJmFetTMYHG2NR9URArGKAJ4uZiYYVscfgozzE0640z2bV9f/9ACgg/Kp /83kovLHIDNJyz4JfyT/kBI= =ITiQ -----END PGP SIGNATURE-----
Message Disclaimer: This electronic message may contain confidential information. If you have received it in error, please immediately inform the sender and delete the mail and any attachments. Unless it relates to the official business of UMN, any opinions, views and other information expressed in this document are those of the individual sender.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Prajjwal Devkota wrote:
#!/bin/bash
BASEURL="http://ftp5.gwdg.de/pub/suse/update/10.2/rpm/i586/" WORKDIR=/usr/local/src/updates/patchrpms/
cd $WORKDIR #get list of rpms from the patch directory wget -c $BASEURL #compile a list of patch rpms awk -Fhref= '/patch.rpm/{print $2}' index.html|awk -F\" '{print $2}'>list #and pull rpms while read line do wget -c $BASEURL/$line done<list
Let me know if I am doing something the "too long" way round.
Prajjwal
rsync -av --partial --progress --delete-after rsync://ftp5.gwdg.de/pub/suse/update/10.2/rpm/i586/ /usr/local/src/updates/patchrpms/ should do the same job Chris -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Thanks Rauch, it seems I was really taking the long way round! rsync -av --include=*.patch.rpm --exclude=* --partial --progress --delete-after rsync://ftp5.gwdg.de/pub/suse/update/10.2/rpm/i586/ /usr/local/src/update/patchrpms I just added exclude and include patterns to the command you gave me, and it seems to be working :). Prajjwal On Fri, 2007-04-20 at 10:21 +0200, Rauch Christian wrote:
Prajjwal Devkota wrote:
#!/bin/bash
BASEURL="http://ftp5.gwdg.de/pub/suse/update/10.2/rpm/i586/" WORKDIR=/usr/local/src/updates/patchrpms/
cd $WORKDIR #get list of rpms from the patch directory wget -c $BASEURL #compile a list of patch rpms awk -Fhref= '/patch.rpm/{print $2}' index.html|awk -F\" '{print $2}'>list #and pull rpms while read line do wget -c $BASEURL/$line done<list
Let me know if I am doing something the "too long" way round.
Prajjwal
rsync -av --partial --progress --delete-after rsync://ftp5.gwdg.de/pub/suse/update/10.2/rpm/i586/ /usr/local/src/updates/patchrpms/ should do the same job
Chris
Message Disclaimer: This electronic message may contain confidential information. If you have received it in error, please immediately inform the sender and delete the mail and any attachments. Unless it relates to the official business of UMN, any opinions, views and other information expressed in this document are those of the individual sender. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Apr 20, 2007 at 03:03:33PM +0545, Prajjwal Devkota wrote:
Thanks Rauch, it seems I was really taking the long way round!
rsync -av --include=*.patch.rpm --exclude=* --partial --progress --delete-after rsync://ftp5.gwdg.de/pub/suse/update/10.2/rpm/i586/ /usr/local/src/update/patchrpms
I just added exclude and include patterns to the command you gave me, and it seems to be working :).
You should perhaps know that fixes also arrive in .delta.rpms and sometime there just are the FULL rpms. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
You should perhaps know that fixes also arrive in .delta.rpms and sometime there just are the FULL rpms.
When you mention it, yes. But I got my problem fixed with the patch rpm, which is why I was fixated on the patch rpms. I am scared about the number of FULL rpms I will have to download-- bandwidth is something that I would not like too congested. However, delta rpms should be included as well I guess. Regarding delta rpms, could anyone explain to me when deltas are released, when patches are released, and when full rpms are released? I am assuming full ones would be the most significant changes, then patch rpms, then deltas. I do not plan to upgrade everything, just the rpms causing problems as far as possible, and I am going to add a filter to the rsync script for this. I guess there is a lot of documentation to go through for me! Prajjwal Message Disclaimer: This electronic message may contain confidential information. If you have received it in error, please immediately inform the sender and delete the mail and any attachments. Unless it relates to the official business of UMN, any opinions, views and other information expressed in this document are those of the individual sender. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Apr 20, 2007 at 03:39:17PM +0545, Prajjwal Devkota wrote:
You should perhaps know that fixes also arrive in .delta.rpms and sometime there just are the FULL rpms.
When you mention it, yes. But I got my problem fixed with the patch rpm, which is why I was fixated on the patch rpms. I am scared about the number of FULL rpms I will have to download-- bandwidth is something that I would not like too congested. However, delta rpms should be included as well I guess.
Regarding delta rpms, could anyone explain to me when deltas are released, when patches are released, and when full rpms are released? I am assuming full ones would be the most significant changes, then patch rpms, then deltas. I do not plan to upgrade everything, just the rpms causing problems as far as possible, and I am going to add a filter to the rsync script for this. I guess there is a lot of documentation to go through for me!
Both deltas and patch RPMs are generated internally. If the deltasize is approximately the size of the patch rpm, only the patch RPM is used. Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Both deltas and patch RPMs are generated internally. If the deltasize is approximately the size of the patch rpm, only the patch RPM is used.
Thanks Marcus. Prajjwal Message Disclaimer: This electronic message may contain confidential information. If you have received it in error, please immediately inform the sender and delete the mail and any attachments. Unless it relates to the official business of UMN, any opinions, views and other information expressed in this document are those of the individual sender. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Based on the rsync script, the fact that patch, delta, and full rpms may all be important, and to save bandwidth by preventing unnecessary files, my new script is the one below: #!/bin/bash PATCHDIR=/usr/local/src/update/patches RSYNCDIR=rsync://ftp5.gwdg.de/pub/suse/update/10.2/rpm/i586/ INCLUDEFILE=$PATCHDIR/files/rpmlist #Create list of rpms rpm -qa|awk -F-[0-9] '{print $1}' > $INCLUDEFILE sed -i 's/$/-[0-9]*.rpm/g' $INCLUDEFILE #No longer used-- I want not only patch rpms, but the delta and full ones as well #rsync -av --include=*.patch.rpm --exclude=* --partial --progress --delete-after $RSYNCDIR $PATCHDIR #rsync required patches with the server: exclude any packages if they have not been installed yet rsync -av --include-from=$INCLUDEFILE --exclude=* --partial --progress --delete-after $RSYNCDIR $PATCHDIR If some installed packages are going to need new packages to be installed during upgrade, thats up to the sysadmin to pull manually. Prajjwal On Fri, 2007-04-20 at 12:39 +0200, Marcus Meissner wrote:
On Fri, Apr 20, 2007 at 03:39:17PM +0545, Prajjwal Devkota wrote:
You should perhaps know that fixes also arrive in .delta.rpms and sometime there just are the FULL rpms.
When you mention it, yes. But I got my problem fixed with the patch rpm, which is why I was fixated on the patch rpms. I am scared about the number of FULL rpms I will have to download-- bandwidth is something that I would not like too congested. However, delta rpms should be included as well I guess.
Regarding delta rpms, could anyone explain to me when deltas are released, when patches are released, and when full rpms are released? I am assuming full ones would be the most significant changes, then patch rpms, then deltas. I do not plan to upgrade everything, just the rpms causing problems as far as possible, and I am going to add a filter to the rsync script for this. I guess there is a lot of documentation to go through for me!
Both deltas and patch RPMs are generated internally. If the deltasize is approximately the size of the patch rpm, only the patch RPM is used.
Ciao, Marcus
Message Disclaimer: This electronic message may contain confidential information. If you have received it in error, please immediately inform the sender and delete the mail and any attachments. Unless it relates to the official business of UMN, any opinions, views and other information expressed in this document are those of the individual sender. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Prajjwal Devkota schrieb:
Based on the rsync script, the fact that patch, delta, and full rpms may ...
If some installed packages are going to need new packages to be installed during upgrade, thats up to the sysadmin to pull manually.
I think this link could be usefull to generate a real local caching repository: http://en.opensuse.org/SDB%3AGenerating_YaST_Installation_Sources -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I think this link could be usefull to generate a real local caching repository: http://en.opensuse.org/SDB%3AGenerating_YaST_Installation_Sources
Thanks for the link Michael. I found just a bit of extra information on this one: http://en.opensuse.org/Creating_YaST_Installation_Sources -- nearly similar, but this one includes a bit more it seems. Anyways, I tried to generate a Yast Source, couldn't get it working according to the instructions given in the wiki (and quite a bit of hacking around as well), so I gave up and used createrepo to create a yum source. Yast recognises my yum repository, and it can pull a list of packages, but the funny thing is, I could not find a way to make the updates appear in the "Online Update" section. When I click on "Online Update", it does read from my yum update source (comments that it is unsigned, but I advise it to ignore the unsigned part forever), but it does not show any available patches. My temporary solution is to go to "Software Management", click on the packages I want, and choose "Update" (the Z like icon). Can anyone help me out with getting the update repository working without me having to go about this way? Thanks a lot for your help, Prajjwal Message Disclaimer: This electronic message may contain confidential information. If you have received it in error, please immediately inform the sender and delete the mail and any attachments. Unless it relates to the official business of UMN, any opinions, views and other information expressed in this document are those of the individual sender. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-04-20 at 15:39 +0545, Prajjwal Devkota wrote:
I am scared about the number of FULL rpms I will have to download-- bandwidth is something that I would not like too congested.
Then limit the bandwidth: --bwlimit=KBPS limit I/O bandwidth; KBytes per second - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGKLLUtTMYHG2NR9URAn5PAJkB3iiA2w5DpNrb7C5DXl4HbdqZQACdGabU czYoFv2GnOtap+bmBi10jUs= =M56Z -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-04-20 at 08:47 +0545, Prajjwal Devkota wrote:
Lets see if I can isolate the patches required, or find another way to cache updates. Does anyone have any idea about using yum/smart to do the same? I plan to look into that soon.
You can use a proxy cache, and set every install to use the same remote server so that it can be chached. Or, create a local update mirror. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGKINgtTMYHG2NR9URAoVwAJ9lhqOTUMEfqJmOrb6YIyw1+KmRXQCeJSsp zMjF6Gcn0h952jwyUGmzODk= =rA0x -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am back at this after a long time: finally got some spare time to play around again. I think I will have to follow your suggestion Carlos, if I cannot create a zypp source and add it using the suseRegister.conf file (update configuration?). Prajjwal On Fri, 2007-04-20 at 11:09 +0200, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2007-04-20 at 08:47 +0545, Prajjwal Devkota wrote:
Lets see if I can isolate the patches required, or find another way to cache updates. Does anyone have any idea about using yum/smart to do the same? I plan to look into that soon.
You can use a proxy cache, and set every install to use the same remote server so that it can be chached.
Or, create a local update mirror.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFGKINgtTMYHG2NR9URAoVwAJ9lhqOTUMEfqJmOrb6YIyw1+KmRXQCeJSsp zMjF6Gcn0h952jwyUGmzODk= =rA0x -----END PGP SIGNATURE-----
Message Disclaimer: This electronic message may contain confidential information. If you have received it in error, please immediately inform the sender and delete the mail and any attachments. Unless it relates to the official business of UMN, any opinions, views and other information expressed in this document are those of the individual sender. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R. -
Marcus Meissner -
Michael Riess -
Prajjwal Devkota -
Rauch Christian -
Roger Oberholtzer