[opensuse-factory] Tumbleweed: dependency problem for mercurial
Hello, Trying to install mercurial on my system. Here is the pop-up I get when checking it's box in Yast : http://wstaw.org/m/2011/08/10/plasma-desktopOr2388.jpg I choose to break it's dependencies and it installed. After that, it seems working as I managed to clone a repository with it. Just wanted to let you know. -- Valentin Rusu (valir) KSecretsService (former KSecretService, KWallet replacement) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Wed, Aug 10, 2011 at 12:58:14PM +0200, Valentin Rusu wrote:
Hello,
Trying to install mercurial on my system. Here is the pop-up I get when checking it's box in Yast : http://wstaw.org/m/2011/08/10/plasma-desktopOr2388.jpg
That's not a problem. Try installing rcs, or doing 'zypper install mecurial' on the command line, and that would install it properly. greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 08/10/2011 04:48 PM, Greg KH wrote:
On Wed, Aug 10, 2011 at 12:58:14PM +0200, Valentin Rusu wrote:
Hello,
Trying to install mercurial on my system. Here is the pop-up I get when checking it's box in Yast : http://wstaw.org/m/2011/08/10/plasma-desktopOr2388.jpg That's not a problem.
Try installing rcs, or doing 'zypper install mecurial' on the command line, and that would install it properly. Well, here is the output when trying to install rcs :
(remember I previously messed with the factory repo, but I now deactivated it) ~ # zypper install rcs Retrieving repository 'Tumbleweed' metadata [done] Building repository 'Tumbleweed' cache [done] Retrieving repository 'google-chrome' metadata [done] Building repository 'google-chrome' cache [done] Retrieving repository 'openSUSE-11.4-Update-Debug' metadata [done] Building repository 'openSUSE-11.4-Update-Debug' cache [done] Loading repository data... Reading installed packages... 'rcs' not found in package names. Trying capabilities. No provider of 'rcs' found. Resolving package dependencies... Nothing to do. ~ # zypper lr # | Alias | Name | Enabled | Refresh ---+-------------------------+----------------------------+---------+-------- 1 | KDE_Unstable | KDE_Unstable | No | No 2 | KDE_Unstable_Extra_Apps | KDE_Unstable_Extra_Apps | No | No 3 | Tumbleweed | Tumbleweed | Yes | Yes 4 | VLC | VLC | Yes | Yes 5 | devel:tools | devel:tools | No | No 6 | google-chrome | google-chrome | Yes | Yes 7 | repo-debug | openSUSE-11.4-Debug | Yes | Yes 8 | repo-debug-update | openSUSE-11.4-Update-Debug | Yes | Yes 9 | repo-non-oss | openSUSE-11.4-Non-Oss | No | No 10 | repo-oss | openSUSE-11.4-Oss | No | No 11 | repo-source | openSUSE-11.4-Source | No | No 12 | repo-update | openSUSE-11.4-Update | Yes | No -- Valentin Rusu (valir) KSecretsService (former KSecretService, KWallet replacement) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thu, Aug 11, 2011 at 07:00:10PM +0200, Valentin Rusu wrote:
On 08/10/2011 04:48 PM, Greg KH wrote:
On Wed, Aug 10, 2011 at 12:58:14PM +0200, Valentin Rusu wrote:
Hello,
Trying to install mercurial on my system. Here is the pop-up I get when checking it's box in Yast : http://wstaw.org/m/2011/08/10/plasma-desktopOr2388.jpg That's not a problem.
Try installing rcs, or doing 'zypper install mecurial' on the command line, and that would install it properly. Well, here is the output when trying to install rcs :
(remember I previously messed with the factory repo, but I now deactivated it)
Oh, that could mess your system up massively, you better know what you are doing here...
~ # zypper install rcs Retrieving repository 'Tumbleweed' metadata [done] Building repository 'Tumbleweed' cache [done] Retrieving repository 'google-chrome' metadata [done] Building repository 'google-chrome' cache [done] Retrieving repository 'openSUSE-11.4-Update-Debug' metadata [done] Building repository 'openSUSE-11.4-Update-Debug' cache [done] Loading repository data... Reading installed packages... 'rcs' not found in package names. Trying capabilities. No provider of 'rcs' found.
That's because you disabled where it lives:
9 | repo-non-oss | openSUSE-11.4-Non-Oss | No | No 10 | repo-oss | openSUSE-11.4-Oss | No | No 11 | repo-source | openSUSE-11.4-Source | No | No 12 | repo-update | openSUSE-11.4-Update | Yes | No
Why are all of these "No"? You really don't want to install any new software, do you? :) greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Thursday, August 11, 2011 12:00:10 PM Valentin Rusu wrote:
7 | repo-debug | openSUSE-11.4-Debug | Yes | Yes ... 9 | repo-non-oss | openSUSE-11.4-Non-Oss | No | No 10 | repo-oss | openSUSE-11.4-Oss | No | No 11 | repo-source | openSUSE-11.4-Source | No | No
Above repos don't change since release day, so having them refreshed is waste of time: Enabled = yes Autorefresh = No
12 | repo-update | openSUSE-11.4-Update | Yes | No
The Update repo is changing and needs autorefresh, so: Enabled = yes Autorefresh = yes -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 08/12/2011 06:48 AM, Rajko M. wrote:
On Thursday, August 11, 2011 12:00:10 PM Valentin Rusu wrote:
Above repos don't change since release day, so having them refreshed is waste of time: Enabled = yes Autorefresh = No Thanks for that!
12 | repo-update | openSUSE-11.4-Update | Yes | No The Update repo is changing and needs autorefresh, so: Enabled = yes Autorefresh = yes
Ok, and if I only want to get security updates, will a "zypper up" do or should I always use "zypper dup"? -- Valentin Rusu (valir) KSecretsService (former KSecretService, KWallet replacement) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Friday, August 12, 2011 07:04:20 AM Valentin Rusu wrote:
Ok, and if I only want to get security updates, will a "zypper up" do or should I always use "zypper dup"?
Udate repo has only security and critical updates. They are issued as patches and as packages, all residing at: http://download.opensuse.org/update/11.4/ To get only security and critical updates use: zypper up -t patch As no other then update repo has patches, this will install only security and critical updates. The default of plain 'zypper up' is the same as: zypper up -t package This will install updates for all packages in all enabled repos and as update has packages that offer the same updates as patches, it will install security and critical updates. Importat is to know: zyper up updates packages to the highest version from the same vendor. In other words if package belongs to vendor openSUSE, it will not switch to some other vendor without asking for permission. It is also configured to ask for permission only if there is no other way to fulfill your request for some package. If it can install updates without switching vendors, it will not ask, even if newer version is available from another vendor, and you would like to use that version. zypper dup updates packages to the highest version from any vendor, and it doesn't ask any questions along the way. This comes handy with Tumbleweed that is considered different vendor then openSUSE, but Tumbleweed repository is created with properties of 'zypper dup' in mind. It will use openSUSE or Tumblweed without bugging users about vendor change. Adding any other repository to the mix of openSUSE and Tumbleweed is call for trouble, as many that did not follow the advice found out. How to know which repo belongs to openSUSE? I use the rule of thumb: All at http://download.opensuse.org/ is vendor openSUSE with exception of http://download.opensuse.org/repositories/ where each project is one vendor. It is not waterproof, but it works most of the time. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Many thanks for your thorough explanation. On 08/12/2011 03:48 PM, Rajko M. wrote:
On Friday, August 12, 2011 07:04:20 AM Valentin Rusu wrote:
Ok, and if I only want to get security updates, will a "zypper up" do or should I always use "zypper dup"? Udate repo has only security and critical updates. They are issued as patches and as packages, all residing at: http://download.opensuse.org/update/11.4/
To get only security and critical updates use: zypper up -t patch As no other then update repo has patches, this will install only security and critical updates.
The default of plain 'zypper up' is the same as: zypper up -t package This will install updates for all packages in all enabled repos and as update has packages that offer the same updates as patches, it will install security and critical updates.
Importat is to know:
zyper up updates packages to the highest version from the same vendor.
In other words if package belongs to vendor openSUSE, it will not switch to some other vendor without asking for permission. It is also configured to ask for permission only if there is no other way to fulfill your request for some package. If it can install updates without switching vendors, it will not ask, even if newer version is available from another vendor, and you would like to use that version.
zypper dup updates packages to the highest version from any vendor, and it doesn't ask any questions along the way.
This comes handy with Tumbleweed that is considered different vendor then openSUSE, but Tumbleweed repository is created with properties of 'zypper dup' in mind. It will use openSUSE or Tumblweed without bugging users about vendor change. Adding any other repository to the mix of openSUSE and Tumbleweed is call for trouble, as many that did not follow the advice found out.
How to know which repo belongs to openSUSE? I use the rule of thumb: All at http://download.opensuse.org/ is vendor openSUSE with exception of http://download.opensuse.org/repositories/ where each project is one vendor. It is not waterproof, but it works most of the time.
-- Valentin Rusu (valir) KSecretsService (former KSecretService, KWallet replacement) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 08/12/2011 12:48 AM, Rajko M. pecked at the keyboard and wrote:
On Thursday, August 11, 2011 12:00:10 PM Valentin Rusu wrote:
7 | repo-debug | openSUSE-11.4-Debug | Yes | Yes ... 9 | repo-non-oss | openSUSE-11.4-Non-Oss | No | No 10 | repo-oss | openSUSE-11.4-Oss | No | No 11 | repo-source | openSUSE-11.4-Source | No | No
Above repos don't change since release day, so having them refreshed is waste of time: Enabled = yes Autorefresh = No
12 | repo-update | openSUSE-11.4-Update | Yes | No
The Update repo is changing and needs autorefresh, so: Enabled = yes Autorefresh = yes
But they are _not_ enabled as they show No | No where they should show Yes | No. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (4)
-
Greg KH -
Ken Schneider - openSUSE -
Rajko M. -
Valentin Rusu