Re: [opensuse] update repo very slow
On 07/25/2017 10:46 AM, Felix Miata wrote:
Anton Aylward composed on 2017-07-25 09:03 (UTC-0400):
David C. Rankin wrote:
In the interim, pick one of the update mirrors that works for you and just create a new update_whatever.repo file in /etc/zypp/repos.d, then just call it by name (e.g. whatever you put between [....]) with zypper up -r .... (where .... is the name for the repo) and use that mirror directly.
Pick your mirror from one of: <http://download.opensuse.org/update/leap/42.2/oss/openSUSE:Leap:42.2:Update.repo.mirrorlist>
"I'm sorry, Dave ..."
I'm well aware of the other mirrors As another thread mentioned, I am capable of going to a repository and downloading by hand a specific RPM using wget or cURL, but that's not the way most of us work. and not a healthy way to update. It's tedious and a 'step and repeat process. Most ff us use Yast or Zypper.
Sadly, that means mirrorbrain makes the selection for us.
I'm unaware of any way I can load up /etc/zypp/<somenthing> to blacklist a specific repository or prioritize others.
I hope there is some mechanism available.
Using MC, it's a simple matter to enable, disable or switch a repo to a specific pre-configured mirror, and little more effort to enable a specific new mirror: -rw-r--r-- 1 246 Jan 1 2014 BaseSystem.repo -rw-r--r-- 1 246 Jan 1 2014 BaseSystem.repoD -rw-r--r-- 1 254 Jan 1 2014 BaseSystem.repo-gwdg -rw-r--r-- 1 244 Jan 1 2014 BaseSystem.repoW -rw-rw-r-- 1 318 Mar 14 2014 homeTobijkBranchesX11XOrg.repo -rw-r--r-- 1 264 May 16 2013 homeTobijk-X11.repo -rw-r--r-- 1 284 May 13 2013 homeTobijk-X11XOrg.repoD -rw-r--r-- 1 298 May 16 2013 homeTobijkX11XOrg-subset.repo -rw-rw-r-- 1 248 Nov 1 2015 KDE3.repo -rw-rw-r-- 1 248 Nov 1 2015 KDE3.repoD -rw-rw-r-- 1 248 Nov 1 2015 KDE3.repoFD -rw-rw-r-- 1 252 Nov 1 2015 KDE3.repo-gwdg -rw-rw-r-- 1 246 Nov 1 2015 KDE3.repoW -rw-r--r-- 1 244 Jan 1 2014 KernelHead.repoD -rw-rw-r-- 1 256 Jan 1 2014 KernelNext.repoD -rw-r--r-- 1 244 Oct 1 2012 KernelStableStd.repoD -rw-r--r-- 1 150 Nov 1 2015 Libdvdcss.repoD -rw-rw-r-- 1 179 May 16 2013 MozillaBeta.repoD -rw-rw-r-- 1 178 May 16 2013 MozillaBeta.repoW -rw-rw-r-- 1 167 Jan 1 2014 Mozilla.repoD -rw-rw-r-- 1 171 Jan 1 2014 Mozilla.repo-gwdg -rw-rw-r-- 1 166 Jan 1 2014 Mozilla.repoW -rw-rw-r-- 1 141 Jan 1 2015 Non-OSS.repo -rw-rw-r-- 1 141 Jan 1 2015 Non-OSS.repoD -rw-rw-r-- 1 145 Jan 1 2015 Non-OSS.repo-gwdg -rw-rw-r-- 1 150 Jan 1 2015 Non-OSS.repoK -rw-rw-r-- 1 140 Jan 1 2015 Non-OSS.repoW -rw-rw-r-- 1 129 Jan 1 2015 OSS.repo -rw-rw-r-- 1 129 Jan 1 2015 OSS.repoD -rw-rw-r-- 1 133 Jan 1 2015 OSS.repo-gwdg -rw-rw-r-- 1 138 Jan 1 2015 OSS.repoK -rw-rw-r-- 1 138 Jan 1 2015 OSS.repoW -rw-rw-r-- 1 119 Oct 1 2012 Packman.repo-inodeat2012 -rw-rw-r-- 1 222 Nov 1 2015 Packman.repo-inodeatD -rw-rw-r-- 1 131 Jan 1 2015 Packman.repo-inodeatP -rw-rw-r-- 1 243 Jan 1 2015 Tools.repoD -rw-r--r-- 1 135 Jan 1 2015 Update.repo -rw-r--r-- 1 135 Jan 1 2015 Update.repoD -rw-rw-r-- 1 238 May 16 2013 Utilities.repoD -rw-rw-r-- 1 117 May 16 2013 VideoLAN.repoD -rw-rw-r-- 1 254 Nov 1 2015 X11XOrg.repoD
Very strange. locate can't find ANY of those files on my 42.2 system and you didn't bother to tell us what directory those are in. And for some reason you responded off list? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/25/2017 12:53 PM, John Andersen wrote:
Very strange. locate can't find ANY of those files on my 42.2 system and you didn't bother to tell us what directory those are in.
John, No mystery, you either create them by hand (copying one to the other and changing the name between [....] to your new name and specifying the new 'baseurl' with the new url -- or -- you use 'zypper ar' (add repo) and specify the url and short_name (which it puts between the [...] for you :) The .repo files are simple text files. Example, here are the two I have for 'update' the original and my 'updatetx' specifying the Texas mirror, (default update using mirrorbrain) $ cat /etc/zypp/repos.d/download.opensuse.org-oss_1.repo [update] name=Main Update Repository enabled=1 autorefresh=1 baseurl=http://download.opensuse.org/update/leap/42.2/oss path=/ type=rpm-md keeppackages=0 (custom update with fixed url) $ cat /etc/zypp/repos.d/updatetx.repo [updatetx] name=Main Update Repository enabled=1 autorefresh=1 baseurl=http://ftp.utexas.edu/opensuse/update/leap/42.2/oss path=/ type=rpm-md keeppackages=0 When you 'zypper lr' (list repos), zypper just scans the /etc/zypp/repos.d directory and includes what it finds. The `'enabled` flag in each file tells zypper whether the repo is enabled or not. Really quite simple once you make friends with it. Take the dir out for a beer.... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
David C. Rankin composed on 2017-07-25 15:16 (UTC-0400): ...
When you 'zypper lr' (list repos), zypper just scans the /etc/zypp/repos.d directory and includes what it finds. The `'enabled` flag in each file tells zypper whether the repo is enabled or not.
While undeniably true, your response describes nothing like what I was trying to convey to John that you found in John's onlist reply to my private email to him. I create on my LAN server one set of .repo files and timestamp all with the date of a distribution release. All installations here at some early point get their /etc/zypp/repos.d/ content from the LAN server. Those copied (except for TW's) are never, unless in the rare case that I desire a temporary change in priority, subsequently changed before support for that release expires. Repos here are enabled or disabled by changing which files end in .repo or not, either by copying a file that does not end in .repo to one that does in order to enable /or/ to change an applicable baseurl, or by deleting a .repo file to disable. WRT libzypp, all files in /etc/zypp/repos.d/ that do not end in .repo are inert, ignored, irrelevant, etc., just as if their content was in any relevant way invalid. Repo caching for me, and locking/unlocking particularly, in openSUSE works fabulously, as does the vast majority of the zypp-based system. Other package management systems by comparison I find hopelessly deficient. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/26/2017 12:03 AM, Felix Miata wrote:
Repo caching for me, and locking/unlocking particularly, in openSUSE works fabulously, as does the vast majority of the zypp-based system. Other package management systems by comparison I find hopelessly deficient.
Very interesting. If I had more than one currently updating box (I have a half-dozen+ with working installs back to SuSE 9.0 in the bone-yard), I would revisit my local update server setup. In the 10.x - 11.0 days (and days of 1M WAN -- or heaven forbid dial-up) when running all SuSE/openSuSE boxes, I did full-repo package caching with full local repo hosting with createrepo, repo-signing, etc..., and it worked flawlessly. Basically all packages installed or updated (with download.use_deltarpm=false, keeppackages=1 set on local boxes) were rsynced to my local web-server, duplicates removed and createrepo run and the repo signed for each release and made available via apache. (not mirroring the full repos, just adding to my repo all packages that were downloading during the normal install or update process) That made new setups (which I did much more frequently in the past) a breeze with all needed (and updated) packages available via the LAN. Looking, 11.1 was the last release I did that for, I've never tried anything similar with apt, but for pacman, the exact same thing can be done with no more (and now arguably less) effort than caching for zypper. (essentially you can set to poll and update from any machine on your LAN and pacman will choose the repo based on timestamps) So there is hope for others :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
David C. Rankin -
Felix Miata -
John Andersen