https://bugzilla.novell.com/show_bug.cgi?id=354880 User meissner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354880#c2 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@novell.com --- Comment #2 from Marcus Meissner 2008-01-19 07:04:50 MST --- we might have reused the same release/version. try zypper lu -t package to see if it has not applied package updates? -- 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=354880 User chrubis@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354880#c4 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |tgoettlicher@novell.com --- Comment #4 from Cyril Hrubis 2008-01-28 06:27:23 MST --- As far as I understand this, zypper detect new package version but opensuseupdater doesn't install it after user ask to do so. Reassigning to opensuse-updater-kde maintainer. -- 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=354880 User jkupec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354880#c6 Ján Kupec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkupec@novell.com AssignedTo|jkupec@novell.com |schubi@novell.com --- Comment #6 from Ján Kupec 2008-02-01 06:37:21 MST --- looks like a solve bug, see the summary - the SAME shareset patch version is scheduled to be uninstalled and installed instead of 'nothing to do' conclusion. I guess that's also the reason why it reports the patch as needed in 'zypper lu'. 2008-01-18 21:00:24 <1> cboltz(9917) [zypper] zypper-misc.cc(show_summary):576 Pool contains 29910 items. 2008-01-18 21:00:24 <0> cboltz(9917) [zypper] zypper-misc.cc(show_summary):577 3852 resolvables readInstall summary: 2008-01-18 21:00:24 <0> cboltz(9917) [zypper] zypper-misc.cc(show_summary):616 <install> [S1:0][patch]file shareset-4865-0.noarch 2008-01-18 21:00:24 <0> cboltz(9917) [zypper] zypper-misc.cc(show_summary):616 <uninstall> [S0:0][patch]file shareset-4865-0.noarch -- 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=354880 User suse-beta@cboltz.de added comment https://bugzilla.novell.com/show_bug.cgi?id=354880#c8 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|suse-beta@cboltz.de | --- Comment #8 from Christian Boltz 2008-04-23 05:53:49 MST --- (In reply to comment #7 from Stefan Schubert)

Christian is this still a problem ? If yes can you repeat it with YOU and attach a testcase please ?

Your questions is some days late :-( - I have updated to 11.0 beta1 in the meantime. Unfortunately I also can't remember if the patch was still listed. On the positive side, I have a backup of the 10.3 installation (on my server, available via NFS) in which I can chroot and test it. Wait a minute... (mount --bind /dev, /sys, /proc, chroot) Argh - zypper only displays "A Zypp transaction is already in progress.". /var/run/zypp.pid is created with a size of 0 bytes. Seems zypper doesn't work with /var/run on nfs :-( Log from a "zypper lu" run (remember the whole 10.3 system is mounted via NFS and I chrooted into it): 2008-04-23 13:40:44 <1> cboltz(7625) [zypper] zypper.cc(main):1663 Hi, me zypper 0.8.25 built Oct 10 2007 15:58:36 2008-04-23 13:40:44 <1> cboltz(7625) [zypper] zypper.cc(one_command):731 System sources enabled 2008-04-23 13:40:44 <1> cboltz(7625) [zypp] ZYppFactory.cc(zyppLocked):250 no lockfile /var/run/zypp.pid found 2008-04-23 13:40:44 <1> cboltz(7625) [zypp] ZYppFactory.cc(zyppLocked):253 running as root. Will attempt to create /var/run/zypp.pid 2008-04-23 13:40:44 <5> cboltz(7625) [zypp] Exception.cc(log):119 ZYppFactory.cc(exLockFile):126 THROW: ZYppFactory.cc(exLockFile):126: Cant get exclusive lock 2008-04-23 13:40:44 <5> cboltz(7625) [zypp] Exception.cc(log):119 zypper.cc(one_command):760 CAUGHT: ZYppFactory.cc(exLockFile):126: Cant get exclusive lock 2008-04-23 13:40:44 <3> cboltz(7625) [zypper] zypper.cc(one_command):761 A ZYpp transaction is already in progress. 2008-04-23 13:40:44 <1> cboltz(7625) [zypp] ZYppFactory.cc(unLockFile):139 unlocked Sounds like I should file a bugreport "Zypper doesn't work on NFS-mounted /var" :-( I tried to copy some directories (/var/run, then /var/lib/rpm) to the local harddisk and mount --bind it into the chroot, but each time another problem appeared (next is the zypp cache). I'll try to copy and mount --bind the whole /var tonight. If you have an easier solution, please tell me ;-) -- 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=354880 User tgoettlicher@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=354880#c10 Thomas Göttlicher changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|tgoettlicher@novell.com |jkupec@novell.com --- Comment #10 from Thomas Göttlicher 2008-04-23 06:47:11 MST --- (In reply to comment #9 from Stefan Schubert)

The patch will be selected although it is satisfied: USTu_[S1:0][patch]fileshareset-4865-0.noarch

The question is why the patch will be suggested for installation. Why does zypper select the patch although it is satisfied?

-- 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.