[Bug 299486] New: zypper: infinite loop on missing pkg.
https://bugzilla.novell.com/show_bug.cgi?id=299486
Summary: zypper: infinite loop on missing pkg.
Product: openSUSE 10.3
Version: Beta 1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: libzypp
AssignedTo: kkaempf@novell.com
ReportedBy: mmeeks@novell.com
QAContact: kkaempf@novell.com
Found By: ---
I tried to run:
sudo zypper --non-interactive in -y OpenOffice_org-debuginfo glibc-debuginfo
gtk2-debuginfo glib2-debuginfo fontconfig-debuginfo xorg-x11-debuginfo
* Reading repository 'stable' cache
* Reading installed packages [100%]
.. <very long wait> ...
I have:
sudo zypper sl
# | Enabled | Refresh | Type | Name
| URI
--+---------+---------+-------+-----------------------------------------------------------------------------------+----------------------------------------------------------------------------------
1 | No | Yes | yast2 |
http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ext...
|
http://download.opensuse.org/distribution/SL-Factory-non-oss/inst-source-ext...
2 | Yes | Yes | yast2 | stable
| ftp://dist.suse.de/install/stable-x86
3 | No | Yes | yast2 |
http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/
| http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/
4 | No | Yes | yast2 |
http://download.opensuse.org/distribution/SL-OSS-factory-debug/inst-source-d...
|
http://download.opensuse.org/distribution/SL-OSS-factory-debug/inst-source-d...
ie. only 'stable' enabled.
I attach the 136Mb log-file (gzipped) the basic repeat is:
2007-08-10 21:28:23 <2> t60p(4457) [zypp] ResolverContext.cc(addError):1251
******** Error: ResolverInfo
https://bugzilla.novell.com/show_bug.cgi?id=299486#c1
--- Comment #1 from Michael Meeks
https://bugzilla.novell.com/show_bug.cgi?id=299486
Klaus Kämpf
https://bugzilla.novell.com/show_bug.cgi?id=299486#c2
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=299486#c3
Peter Buschbacher
https://bugzilla.novell.com/show_bug.cgi?id=299486#c4
--- Comment #4 from Ján Kupec
Is there a relationship to bug #297611 ? I can't tell, because it's not public.
No, bug #297611 is about repos stealing metadata of other repos from libzypp's cache. I made the bug public now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299486#c5
--- Comment #5 from Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=299486#c6
Stefan Schubert
https://bugzilla.novell.com/show_bug.cgi?id=299486#c7
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=299486#c8
Stefan Schubert
https://bugzilla.novell.com/show_bug.cgi?id=299486#c9
Stefan Schubert
https://bugzilla.novell.com/show_bug.cgi?id=299486#c10
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=299486#c11
Ján Kupec
Are you using svn version of zypper? Are you sure the enigma wasn't installed?
I've recently added a fix for zypper install foo, where if foo is installed addRequires("foo>installed_version") is used instead of addRequires("foo").
..and it contains a bug, fixed in svn r6638 (In reply to comment #9 from Stefan Schubert)
This call will be intepreded : ResolverQueue.cc(processOnce):227 =====> 1st pass: [[Require: [package] (namedcap) enigma>0.92-48]]
That's the reason why the solver does not find a solution.
But this is exactly how the solver bug demonstrates, a requirements has been set, which can't be satisfied by the pool. addRequires() should report that (by an exception or so). And even if it fails to do so, resolve() should report that as a problem. It does not currently. resolve() fails, but no problem reported. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299486#c12
--- Comment #12 from Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=299486#c13
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=299486#c14
--- Comment #14 from Stefan Schubert
It does not currently. resolve() fails, but no problem reported.
That's the point. I will check it.... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299486#c15
--- Comment #15 from Ján Kupec
It does not currently. resolve() fails, but no problem reported.
That's the point. I will check it....
Yes, but most important IMO is what i'm trying to say in comment #12... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299486#c16 --- Comment #16 from Stefan Schubert2007-08-15 02:38:07 MST --- comment #14 I can reproduce. It is a bug. comment #12 > If not, application must wait for resolve() and problems() (after it is fixed > to work with non-existent injected capabilities) to get dependency problems, > which is not ideal. That's the normal way how the solver bahave. - Tell the solver what you want - Let the solver evaluate a solution. - If it fails, ask why it has failed. Every application which uses the solver expect this behaviour. None does handle solver exceptions right now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299486#c17
--- Comment #17 from Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=299486#c18
Stefan Schubert
https://bugzilla.novell.com/show_bug.cgi?id=299486#c19
--- Comment #19 from Ján Kupec
comment #17 "- Tell the solver what you want" Thats the way how you tell the solver. It is already correct in zypper;-)
No, it isn't :O( currently zypper displays all solver problems with one function. If addRequires() and addConflicts() are to be used this way, zypper must be able to tell the solver problems apart caused by these apart from the others and handle them differently, e.g.: display "package or capability asdf not found" or continue with package removal without displaying the solver problem (example 2). Can this be achieved with the current solver or is a change needed? If so, how do we do it? ---example-1----START---- $ sudo src/zypper install asdf * Reading repository 'factory' cache * Reading installed packages [100%] 1 Problems: Problem: Requirememt asdf cannot be fulfilled. Problem: Requirememt asdf cannot be fulfilled. There are no installable providers of asdf ---example-1----END---- ---example-2----START---- $ sudo src/zypper remove mysql * Reading repository 'factory' cache * Reading installed packages [100%] 1 Problems: Problem: mysql-5.0.27-8.x86_64 conflicts with Problem: mysql-5.0.27-8.x86_64 conflicts with mysql-5.0.27-8.x86_64 conflicts with: Solution 1: delete mysql delete mysql-5.0.27-8.x86_64 Solution 2: Do not install or delete the resolvables concerned Solution 3: Ignore this conflict of mysql number, (r)etry or (c)ancel> 1 Applying solution 1 The following package is going to be REMOVED: mysql Overall download size: 0 B. After the operation, 33.1 M will be freed. Continue? [y/n]: n ---example-2----END---- Again, don't want a solver problem here. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=299486#c20
--- Comment #20 from Martin Vidner
https://bugzilla.novell.com/show_bug.cgi?id=299486#c21
--- Comment #21 from Stefan Schubert
https://bugzilla.novell.com/show_bug.cgi?id=299486#c22
Ján Kupec
participants (1)
-
bugzilla_noreply@novell.com