[zypp-devel] packagekit's zypp-dev backend dependencies?
hi, with, libzypp-6.5.2-20.1 aria2-1.3.3-3.1 zypper-1.1.2-53.1 @ zypper in PackageKit ... The following NEW packages are going to be installed: libpackagekit-glib10 PackageKit The following package is going to be upgraded: libqdialogsolver1 The following packages are going to be downgraded: libzypp satsolver-tools yast2-gtk yast2-ncurses-pkg yast2-pkg-bindings yast2-qt-pkg 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-ncurses-pkg openSUSE Build Service -> openSUSE yast2-pkg-bindings openSUSE Build Service -> openSUSE yast2-qt-pkg openSUSE Build Service -> openSUSE zypper openSUSE Build Service -> openSUSE which repo, if any, solves the 'new' zypp backend deps for PackageKit? likely, the next version of OS ... or GNOME Factory req'd ? -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Thu, May 14, 2009 at 12:23:32PM -0700, PGNet Dev wrote:
The following NEW packages are going to be installed: libpackagekit-glib10 PackageKit
The following package is going to be upgraded: libqdialogsolver1
The following packages are going to be downgraded: libzypp satsolver-tools yast2-gtk yast2-ncurses-pkg yast2-pkg-bindings yast2-qt-pkg 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-ncurses-pkg openSUSE Build Service -> openSUSE yast2-pkg-bindings openSUSE Build Service -> openSUSE yast2-qt-pkg openSUSE Build Service -> openSUSE zypper openSUSE Build Service -> openSUSE
I know that this is unrelated, but can zypper's output be improved? 1) It doesn't print the version changes in the upgrade/downgrade list. Personally, I prefer to see the version changes. 2) It shouldn't use that much output to display the vendor/arch changes, it should display it like The following packages are going to change vendor from 'openSUSE Build Service' to 'openSUSE': libqdialogsolver1 libzypp satsolver-tools yast2-gtk yast2-ncurses-pkg yast2-pkg-bindings yast2-qt-pkg zypper Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Michael Schroeder wrote:
On Thu, May 14, 2009 at 12:23:32PM -0700, PGNet Dev wrote:
The following NEW packages are going to be installed: libpackagekit-glib10 PackageKit
The following package is going to be upgraded: libqdialogsolver1
The following packages are going to be downgraded: libzypp satsolver-tools yast2-gtk yast2-ncurses-pkg yast2-pkg-bindings yast2-qt-pkg 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-ncurses-pkg openSUSE Build Service -> openSUSE yast2-pkg-bindings openSUSE Build Service -> openSUSE yast2-qt-pkg openSUSE Build Service -> openSUSE zypper openSUSE Build Service -> openSUSE
I know that this is unrelated, but can zypper's output be improved?
Sure :O)
1) It doesn't print the version changes in the upgrade/downgrade list. Personally, I prefer to see the version changes.
Enter '?' at the 'Continue?' prompt, you'll see some more display options. Note that this is git HEAD version from OBS, it hasn't been released to factory yet.
2) It shouldn't use that much output to display the vendor/arch changes, it should display it like
The following packages are going to change vendor from 'openSUSE Build Service' to 'openSUSE': libqdialogsolver1 libzypp satsolver-tools yast2-gtk yast2-ncurses-pkg yast2-pkg-bindings yast2-qt-pkg zypper
Yup, might be better, but what if there are, say 4 different vendor changes? You'd get four such 'sections' with fewer packages, instead of one 'vendor change' section with a list like above. I'm not sure what would be more readable. -- cheers, jano Ján Kupec YaST team ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz ---------------------------------------------------------(EOF)---
participants (3)
-
Jano Kupec
-
Michael Schroeder
-
PGNet Dev