Mailinglist Archive: zypp-devel (58 mails)

[PGNet Dev <pgnet.dev+osyast@xxxxxxxxx>]

and, here we go again ....


The following packages are going to be upgraded:
  libstorage python-satsolver

The following packages are going to be downgraded:
  libqdialogsolver1 libzypp satsolver-tools yast2-gtk yast2-pkg-bindings zypper

The following packages are going to change vendor:
  libqdialogsolver1   openSUSE Build Service -> openSUSE
  libzypp             openSUSE Build Service -> openSUSE
  satsolver-tools     openSUSE Build Service -> openSUSE
  yast2-gtk           openSUSE Build Service -> openSUSE
  yast2-pkg-bindings  openSUSE Build Service -> openSUSE
  zypper              openSUSE Build Service -> openSUSE


2 packages to upgrade, 6 to downgrade, 6  to change vendor.
Overall download size: 5.9 MiB. After the operation, 6.8 MiB will be freed.
Continue? [y/n/?] (y):


is there a possibility of getting 'new' zypp & aria into a semi-stable
repo?  something that, perhaps, changes a bit less frequently?

atm, the only option seems to be use 'new' zypper and suffer the
consequences of 'this', or use old zypper, and lose the features that
we're testing/tracking ...

well aware the answer may be 'no' ...
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx