renamerepo (nr) [options] <alias|#|URI> <new-alias>
Assign new alias to the repository specified by alias, number or URI.
This command has no additional options.
e.g.
zypper nr "Packman Repository" Packman
Note you need to quote “Packman Repository” or escape it Packman\ Repository because or word splitting by the shell.
It first see Packman and process it but there is no Packman repository/directory (but Packman Repository) so it will spit out an error.
On 2015-01-21 00:26, jetchisel wrote:
>
> Hi,
>
> You can rename the repositories via zypper too.
There is a complication, because zypper uses two names per repository:
the name and the alias. The name is just a name, but it is the alias
which is used for directory and file names around the system. When I add
repos I take care that the alias does not have spaces or colons,
although zypper escapes them, to avoid complications.
All the definitions are stored in files in /etc/zypp/repos.d/*
The file names seem to be the original alias name of the repository. The
current alias is inside, in brackets:
Just did an online update. It had a patch for rpm. The description said something about fixing response to filenames with spaces in them. Of xourse, I can’t get the description again because it’s updated, but I thought it was worth mentioning.
You can: Open YaST->Online Update and choose to display “All Patches” or “Unneeded Patches”. Then the already installed patches should be shown as well, and you can view the description again.
“zypper info -t patch openSUSE-2015-45” would show it as well, but for this you need to know the patch number obviously.
# zypper info -t patch openSUSE-2015-45
Loading repository data...
Reading installed packages...
Information for patch openSUSE-2015-45:
---------------------------------------
Name: openSUSE-2015-45
Version: 1
Arch: noarch
Vendor: maint-coord@suse.de
Status: Installed
Category: recommended
Severity: moderate
Created On: Tue 13 Jan 2015 17:29:34 CET
Reboot Required: No
Package Manager Restart Required: No
Interactive: No
Summary: recommended update for rpm
Description:
This recommended udpate for rpm fixes the following issue:
- boo#911228: fix noglob patch, which broke files with spaces
...
Or just look at the RPM changelog, either in YaST (“Changelog” tab) or with “rpm -q --changelog xxx”:
# rpm -q --changelog rpm | head
* Thu Jan 08 2015 mls@suse.de
- fix noglob patch, it broke files with spaces [bnc#911228]
* Wed Dec 10 2014 mls@suse.de
- honor --noglob in install mode [bnc#892431]
new patch: installnoglob.diff
- check for bad invalid name sizes [bnc#908128] [CVE-2014-8118]
new patch: cpionamesize.diff
- create files with mode 0 [bnc#906803] [CVE-2013-6435]
new patch: unpackmode0.diff
That “–noglob” option is only used since the latest zypper update, that’s why the problem only showed up now.
Yes, because zypper did not use rpm’s “–noglobs” option before that update, as I wrote in my previous post.
But there has been an update to rpm yesterday which should fix that option, and the problem.
Wrong.
On a standard installation, there is no space in the update repo’s name. It is called “repo-update”, so no problem there.
I recommend somehow modify zypper RPM spec, that it could not to update, unless this RPM update is installed first!
And how would this help?
How should people install a zypper update, if they can’t install any update?
And how?
I’d say, people that have a space in the update repo’s name are a very small minority. And those that installed the zypper update before the rpm update are probably even less.
Unfortunately I see no solution for them, other than downloading/installing the rpm update manually, or maybe switching zypper back to the version from the standard repo (which hopefully doesn’t have a space in the name).
Right, you can, sorry.
AFAIR you couldn’t before the bugzilla update a few months ago though, but I’m not completely sure.
Fixed or not, I can’t say, but the bug is in “new” status.
It is “RESOLVED FIXED” since Thursday.
But the bug in rpm was fixed by the update on Tuesday already. The problem was that the rpm update was not tagged as software stack update by mistake, so only the zypper update got installed making it impossible to install the rpm update as well if your update repo contained spaces (which it normally doesn’t).
This has been resolved by removing the zypper update (done on Tuesday already), correctly tagging the rpm update, and re-releasing the zypper update.
People who already installed the zypper but not the rpm update and have spaces in their update repo’s name will have to download and install the rpm update manually though. There’s nothing that can be done about that I suppose, but this shouldn’t affect many people anyway.
On 2015-01-29 18:26, kamrava wrote:
>
> Hi
>
> I’m trying to install “dkms” pacckage by :
If it is the same error as described in this thread (see wolfi323’s
posts), you have to wget the rpm update, then apply it with ‘rpm’.
Zypper will fail.
You can verify if you have this problem by examining the rpm changelog,
as described in another post (ie, does it have the noglob patch?).
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Not necessarily.
That would only have to be done if the standard update repo has spaces in the name.
But as dkms is not available in the standard update repo, this doesn’t have to be the case here.
So it might still be able to normally install the rpm update via YaST->Online Update, zypper patch/up, or the desktop’s updater. If necessary disable the “Packman Repository” (likely the problem I’d guess, as dkms is available from there) temporarily.
