Mailinglist Archive: zypp-devel (227 mails)

[Josef Reidinger <jreidinger@xxxxxxx>]

Hi,
I have few question about solver.
I test zypper in one bug (not related and fixed) and find this behavior.
Is it correct? (I done refresh before tests)

first try - normal 3ddiag (output snipped)

zypper -vvvv in --force-resolution off 3ddiag
0 items locked
Force resolution: No
Resolving dependencies...

The following package is going to be upgraded:
  3ddiag-0.740-85.x86_64  (Main Repository (OSS))


same result with force on...but in both case I have in repo newer 
package. Is correct if solver doesn't try newer?

zypper -vvvv in --force-resolution on 3ddiag
0 items locked
Force resolution: Yes
Resolving dependencies...

The following package is going to be upgraded:
  3ddiag-0.740-85.x86_64  (Main Repository (OSS))

Now force off and the newest version of package

zypper -vvvv in --force-resolution on -C 3ddiag=0.742
0 items locked
Force resolution: Yes
Resolving dependencies...

The following packages are going to be upgraded:
  yast2-hardware-detection-2.16.1-26.x86_64  (factory)
  kio_sysinfo-11.0-75.x86_64  (factory)
  hwinfo-devel-14.11-5.x86_64  (factory)
  hwinfo-14.11-5.x86_64  (factory)
  3ddiag-0.742-10.x86_64  (factory)


The following packages are going to be REMOVED:
  kdebase3-SuSE-10.3-152.x86_64  (@System)
  sax2-gui-8.1-258.x86_64  (@System)
  sax2-8.1-258.x86_64  (@System)

and with force-resolution off
zypper -vvvv in --force-resolution off -C 3ddiag=0.742
Verbosity: 4
Non-option program arguments: '3ddiag=0.742'
Initializing Target
Checking whether to refresh metadata for factory
Reading installed packages...
0 items locked
Force resolution: No
Resolving dependencies...

The following packages are going to be upgraded:
  zypper-0.10.4-12.x86_64  (factory)
  yast2-qt-2.16.33-8.x86_64  (factory)
  yast2-pkg-bindings-2.16.22-4.x86_64  (factory)
  yast2-perl-bindings-2.16.5-2.x86_64  (factory)
  yast2-ncurses-2.16.20-7.x86_64  (factory)
  yast2-hardware-detection-2.16.1-26.x86_64  (factory)
  yast2-core-2.16.41-2.x86_64  (factory)
  spamassassin-3.2.4-19.x86_64  (factory)
 <snip> too much package </snip>
  3ddiag-0.742-10.x86_64  (factory)


The following NEW packages are going to be installed:
  yast2-ycp-ui-bindings-2.16.39-7.x86_64  (factory)
  yast2-libyui-2.16.39-7.x86_64  (factory)
  yast2-core-devel-2.16.41-2.x86_64  (factory)
  libsatsolver-devel-0.0.24-2.x86_64  (factory)
  libblocxx6-2.1.0.342-5.x86_64  (factory)
  libblocxx-devel-2.1.0.342-5.x86_64  (factory)
  frozen-bubble-server-2.1.0-138.x86_64  (factory) ( looks like my 
linux like playing :)
  yast2-theme-openSUSE-Oxygen-2.16.17-16.noarch  (factory)
  desktop-data-openSUSE-11.0-36.noarch  (factory)
  bundle-lang-kde-ar-11.0-86.noarch  (factory)


The following packages are going to be REMOVED:
  desktop-data-SuSE-10.3-88.noarch  (@System)
  blocxx-devel-1.0.0-79.x86_64  (@System)
  CheckHardware-0.1-1088.x86_64  (@System)
  perl-IO-Zlib-1.06-13.x86_64  (@System)
  perl-IO-Compress-Zlib-2.005-16.x86_64  (@System)
  perl-IO-Compress-Base-2.005-17.x86_64  (@System)
  perl-Compress-Zlib-2.005-13.x86_64  (@System)
  perl-Compress-Raw-Zlib-2.005-17.x86_64  (@System)
  perl-Archive-Tar-1.32-18.x86_64  (@System)
  liby2util-devel-2.14.0-65.x86_64  (@System)
  liby2util-2.14.0-65.x86_64  (@System)

so is it correct or bug to report?
Maybe I am only misunderstood what is force-resolution

Pepa
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx