http://bugzilla.novell.com/show_bug.cgi?id=597101 http://bugzilla.novell.com/show_bug.cgi?id=597101#c2 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |ma@novell.com InfoProvider| |a3349542@owlpic.com --- Comment #2 from Michael Andres 2010-04-16 14:30:08 UTC --- There seems to be something broken on your system. The attached logs contain a zypper.log with just 10MB of zeros. If /var/log/zypper.log looks the same on your system, you should remove it. 1) Please run (as root): zypper up --debug-solver Check whether /var/log/zypper.log actually contains readable data. If so collecta and attach the logs again (/var/log/zypper.log and /var/log/zypper.solverTestCase/). 2) Please run: ls -l /etc/zypp/locks Lock definition are kept in the file /etc/zypp/locks. Attach the ls output and the file itself. -- The zypper commands locks, addlock, removelock and cleanlocks can be used to manipulate the package locks (see 'man zypper' for more details). If you're sure you do not want to keep any lock at all, you can also simply remove the file /etc/zypp/locks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=597101 http://bugzilla.novell.com/show_bug.cgi?id=597101#c4 Judge Judy changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #354789|0 |1 is obsolete| | Status|NEEDINFO |NEW InfoProvider|a3349542@owlpic.com | --- Comment #4 from Judge Judy 2010-04-16 17:06:27 UTC --- Created an attachment (id=355052) --> (http://bugzilla.novell.com/attachment.cgi?id=355052) yast logs, 2 (In reply to comment #2) Here's what I did; a lot of it may not be necessary, but I'm trying to do this step-by-step, zypper clean --all rpm --rebuilddb zypper lr -u # | Alias | Name | Enabled | Refresh | URI --+----------+----------+---------+---------+-------------------------------------------------------- 1 | OS11-oss | OS11-oss | Yes | Yes | http://download.opensuse.org/distribution/11.2/repo/oss cd ~ rm -rf /var/tmp/zypp* rm -rf /var/cache/zypp* rm -rf /var/lib/zypp* zypper ref zypper ve Dependencies of all installed packages are satisfied. ls -l /etc/zypp/locks -rw-r--r-- 1 root root 277 2010-04-15 19:39 /etc/zypp/locks zypper ll # | Name | Type | Repository --+--------------+---------+----------- 1 | flash-player | package | (any) 2 | opera | package | (any) 3 | apparmor | pattern | (any) cat /etc/zypp/locks type: package match_type: glob case_sensitive: on solvable_name: flash-player type: package match_type: exact solvable_arch: x86_64 solvable_name: opera type: pattern match_type: exact case_sensitive: on solvable_name: apparmor rm /var/log/zypper.log rm -rf /var/log/zypp rm -rf /var/log/zypper.solverTestCase rm -rf ~/zypper_bug rm ~/zypper_bug.tar.gz zypper up --debug-solver mkdir -p ~/zypper_bug mv /var/log/{zypper.solverTestCase,zypper.log} ~/zypper_bug/ cd ~/zypper_bug cd ~/zypper_bug head -n 5 zypper.log 2010-04-16 09:35:25 <1> jjdesk(27498) [zypper] main.cc(main):75 ===== Hi, me zypper 1.2.8 built Nov 2 2009 17:44:30 ===== 2010-04-16 09:35:25 <1> jjdesk(27498) [zconfig] ZConfig.cc(_autodetectSystemArchitecture):57 Uname architecture is 'x86_64' 2010-04-16 09:35:25 <1> jjdesk(27498) [zconfig] ZConfig.cc(_autodetectTextLocale):121 Found LANG=en_US.UTF-8 2010-04-16 09:35:25 <1> jjdesk(27498) [zconfig] ZConfig.cc(_autodetectTextLocale):128 Default text locale is 'en_US' 2010-04-16 09:35:25 <1> jjdesk(27498) [zconfig] ZConfig.cc(Impl):234 libzypp: 6.21.2 built Nov 2 2009 17:29:51 zypper se -s | grep ^i > ~/zypper_bug/is_installed.txt /sbin/yast2 --install click -> 'Installation Summary' right-click, select -> 'Export this list to text file ...' >> ~/zypper_bug/pkglist.txt (this shows all the Locked/Protected & Taboo'd files) cd ~ tar -zcvf ~/zypper_bug.tar.gz ~/zypper_bug ATTACHED: zypper_bug.tar.gz -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=597101 http://bugzilla.novell.com/show_bug.cgi?id=597101#c6 --- Comment #6 from Judge Judy 2010-04-16 17:49:14 UTC --- Fyi, even if I remove all the locks, or just remove the locks file, in the package manager I still see Locked & Taboo'd files. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=597101 http://bugzilla.novell.com/show_bug.cgi?id=597101#c8 --- Comment #8 from Judge Judy 2010-04-16 21:55:25 UTC --- (In reply to comment #7)

cat /etc/zypp/locks ... type: package match_type: exact - solvable_arch: x86_64 solvable_name: opera ...

I did not recognize it at first sight. The attributes in /etc/zypp/locks are 'OR'ed, so the above matches all packages named opera OR with arch x86_64. That's why it matches almost all packages.

Removing the 'solvable_arch: x86_64' line (or the whole file) should help.

And voila! it does. I'm a little confused why the notes I'm staring at, where I rm'd the locks file, did NOT fix this problem. Maybe something was cached? *This* time around, as above, I was a lot more careful about cleaning-house ...

@Judy: Do you remember how this ebtry was created? By zypper, yast or manually editing the file?

This one was manually installed -- as directed in one of the *suse IRC channels a while back, after lots of discussion and trial-n-error with globs, query strings, etc. It was based, iirc, on reading this: http://en.opensuse.org/Libzypp/Locksfile#Two_locks which states, "... all objects which contains kde(only low letters) in name and description and second lock for everything which have x11 keyword ..." which reads as "AND", rather than "OR", to me. The specific 'problem' I was trying to solve is the "Hulu vs Flash64-bit" issue. I've Firefox 64bit, with Flash 64 bit installed. Hulu doesn't work, atm. So, we installed Opera 32 bit, with Flash 32-bit in its opera-specific plugin dir. Works great to use Opera32+Flash32 for Hulu use. That said, this lock was the only way we found -- so far -- to make zypper/pkg mgr stop trying to up/down grade to opera64 bit, AND, to track the opera32 bit available in the repos ... Is there another/better way? That won't break this again? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=597101 http://bugzilla.novell.com/show_bug.cgi?id=597101#c10 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #10 from Michael Andres 2010-04-19 11:41:44 UTC --- (In reply to comment #8)

It was based, iirc, on reading this:

http://en.opensuse.org/Libzypp/Locksfile#Two_locks

which states,

"... all objects which contains kde(only low letters) in name and description and second lock for everything which have x11 keyword ..."

which reads as "AND", rather than "OR", to me.

Yes it does, but it's wrong. I'll fix this.

Works great to use Opera32+Flash32 for Hulu use. That said, this lock was the only way we found -- so far -- to make zypper/pkg mgr stop trying to up/down grade to opera64 bit, AND, to track the opera32 bit available in the repos ...

Is there another/better way? That won't break this again?

It sometimes helps looking for unique 'provides': opera-10.00-7.1.1.i586 provides: opera(x86-32) = 10.00-7.1.1 opera-10.00-7.1.1.x86_64 provides: opera(x86-64) = 10.00-7.1.1 So locking all packages providing 'opera(x86-64)' might be what you want: type: package match_type: exact solvable_provides: opera(x86-64) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.