[zypp-devel] 'new' zypp repos, out of sync?
with 'new' zypp/aria2 repos, .../YaST:/Head/openSUSE_11.1 .../zypp:/Head/openSUSE_11.1 .../network:/utilities/openSUSE_11.1 today's zypper dup offers, The following packages are going to be upgraded: libpcap1 libpixman-1-0 libpixman-1-0-32bit libqdialogsolver1 libsnmp15 Mesa python-gobject2 python-satsolver snmp-mibs tcpdump The following packages are going to be downgraded: libzypp satsolver-tools 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-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 simply out of sync repos ? or has something else changed ? -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Thursday 28 May 2009 17:55:04 PGNet Dev wrote:
with 'new' zypp/aria2 repos,
.../YaST:/Head/openSUSE_11.1 .../zypp:/Head/openSUSE_11.1 .../network:/utilities/openSUSE_11.1
today's
zypper dup
offers,
The following packages are going to be upgraded: libpcap1 libpixman-1-0 libpixman-1-0-32bit libqdialogsolver1 libsnmp15 Mesa python-gobject2 python-satsolver snmp-mibs tcpdump
The following packages are going to be downgraded: libzypp satsolver-tools 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-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
simply out of sync repos ? or has something else changed ?
'dup' adjust everything according to the repo priorities. If your openSUSE repo has higher priority than *:/Head the result is probably 'dup' should do. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Fri, May 29, 2009 at 12:20 AM, Michael Andres
'dup' adjust everything according to the repo priorities. If your openSUSE repo has higher priority than *:/Head the result is probably 'dup' should do.
heh, yes, of course. each of
.../YaST:/Head/openSUSE_11.1 .../zypp:/Head/openSUSE_11.1 .../network:/utilities/openSUSE_11.1
have prio == 10 the distro repos have prio == 99. hence, my question ... -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
hrm. ok, can anyone explain why this 'downgrade' is being forced? if it's obvious from the info below, i'm missing the obvious. :-/ current offer is, The following packages are going to be downgraded: libzypp satsolver-tools 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-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 where, on my sys, v | libzypp | package | 6.6.0-6.1 | x86_64 | ZyppHEAD v | libzypp | package | 6.6.0-6.1 | i586 | ZyppHEAD v | libzypp | package | 5.29.6-0.1.1 | x86_64 | OS11-update v | libzypp | package | 5.25.3-0.1.2 | x86_64 | OS11-update v | libzypp | package | 5.29.6-0.1.1 | i586 | OS11-update v | libzypp | package | 5.25.3-0.1.2 | i586 | OS11-update v | libzypp | package | 5.24.5-1.1 | x86_64 | OS11-oss v | libzypp | package | 5.24.5-1.1 | i586 | OS11-oss i | libzypp | package | 6.5.2-38.1 | x86_64 | (System Packages) | libzypp | srcpackage | 6.6.0-6.1 | noarch | ZyppHEAD | libzypp | srcpackage | 5.29.6-0.1.1 | noarch | OS11-update | libzypp-bindings | srcpackage | 0.4.8-77.109 | noarch | ZyppHEAD v | satsolver-tools | package | 0.14.1-59.1 | x86_64 | ZyppHEAD v | satsolver-tools | package | 0.14.1-59.1 | i586 | ZyppHEAD v | satsolver-tools | package | 0.13.6-0.1.1 | x86_64 | OS11-update v | satsolver-tools | package | 0.13.2-0.1.1 | x86_64 | OS11-update v | satsolver-tools | package | 0.13.6-0.1.1 | i586 | OS11-update v | satsolver-tools | package | 0.13.2-0.1.1 | i586 | OS11-update v | satsolver-tools | package | 0.13.0-3.3 | x86_64 | OS11-oss v | satsolver-tools | package | 0.13.0-3.3 | i586 | OS11-oss i | satsolver-tools | package | 0.14.1-52.1 | x86_64 | (System Packages) v | yast2-ncurses-pkg | package | 2.18.4-5.1 | x86_64 | YastHEAD v | yast2-ncurses-pkg | package | 2.18.4-5.1 | i586 | YastHEAD v | yast2-ncurses-pkg | package | 2.17.10-1.20 | x86_64 | OS11-oss v | yast2-ncurses-pkg | package | 2.17.10-1.24 | i586 | OS11-oss i | yast2-ncurses-pkg | package | 2.18.3-3.1 | x86_64 | (System Packages) | yast2-ncurses-pkg | srcpackage | 2.18.4-5.1 | noarch | YastHEAD v | yast2-pkg-bindings | package | 2.18.4-2.25 | x86_64 | YastHEAD v | yast2-pkg-bindings | package | 2.18.4-2.25 | i586 | YastHEAD v | yast2-pkg-bindings | package | 2.17.38-0.1.1 | x86_64 | OS11-update v | yast2-pkg-bindings | package | 2.17.31-1.2.10| x86_64 | OS11-update v | yast2-pkg-bindings | package | 2.17.38-0.1.1 | i586 | OS11-update v | yast2-pkg-bindings | package | 2.17.31-1.2.10| i586 | OS11-update v | yast2-pkg-bindings | package | 2.17.29-1.7 | x86_64 | OS11-oss v | yast2-pkg-bindings | package | 2.17.29-1.9 | i586 | OS11-oss i | yast2-pkg-bindings | package | 2.18.4-2.23 | x86_64 | (System Packages) | yast2-pkg-bindings | srcpackage | 2.18.4-2.25 | noarch | YastHEAD | yast2-pkg-bindings | srcpackage | 2.17.38-0.1.1 | noarch | OS11-update v | yast2-qt-pkg | package | 2.18.9-1.3 | x86_64 | YastHEAD v | yast2-qt-pkg | package | 2.18.9-1.3 | i586 | YastHEAD v | yast2-qt-pkg | package | 2.17.27-0.1.1 | x86_64 | OS11-update v | yast2-qt-pkg | package | 2.17.25-1.1 | x86_64 | OS11-update v | yast2-qt-pkg | package | 2.17.27-0.1.1 | i586 | OS11-update v | yast2-qt-pkg | package | 2.17.25-1.1 | i586 | OS11-update v | yast2-qt-pkg | package | 2.17.22-1.1 | x86_64 | OS11-oss v | yast2-qt-pkg | package | 2.17.22-1.1 | i586 | OS11-oss i | yast2-qt-pkg | package | 2.18.8-2.24 | x86_64 | (System Packages) | yast2-qt-pkg | srcpackage | 2.18.9-1.3 | noarch | YastHEAD | yast2-qt-pkg | srcpackage | 2.17.27-0.1.1 | noarch | OS11-update i | yast2-qt-pkg | patch | 385 | noarch | OS11-update v | zypper | package | 1.1.2-79.1 | x86_64 | ZyppHEAD v | zypper | package | 1.1.2-79.1 | i586 | ZyppHEAD v | zypper | package | 1.0.9-0.1.1 | x86_64 | OS11-update v | zypper | package | 1.0.5-2.1.2 | x86_64 | OS11-update v | zypper | package | 1.0.9-0.1.1 | i586 | OS11-update v | zypper | package | 1.0.5-2.1.2 | i586 | OS11-update v | zypper | package | 1.0.2-1.5 | x86_64 | OS11-oss v | zypper | package | 1.0.2-1.5 | i586 | OS11-oss i | zypper | package | 1.1.2-70.1 | x86_64 | (System Packages) | zypper | srcpackage | 1.1.2-79.1 | noarch | ZyppHEAD | zypper | srcpackage | 1.0.9-0.1.1 | noarch | OS11-update -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
hi, just fyi ... as of 06/04/09, the stale-repo issue's, apparently, resolved, zypper se -s | egrep ^i | egrep " zypper| libzypp| aria" i | aria2 | package | 1.4.0-1.1 | x86_64 | Netutils i | libzypp | package | 6.7.0-14.1 | x86_64 | ZyppHEAD i | zypper | package | 1.1.2-93.1 | x86_64 | ZyppHEAD so, 'back in business' with latest repos. thanks! -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
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@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (2)
-
Michael Andres
-
PGNet Dev