Greg KH writes:
Which is why it is failing, I understand that problem. I don't understand Achim's original question as Tumbleweed shouldn't be the issue here.
This is what zypper se -e NetworkManager tells me (slightly edited for brevity): i | NetworkManager | 0.9.1.90-4.8.1 | openSUSE-current Updates v | NetworkManager | 0.9.1.90-4.6.1 | openSUSE-current Updates v | NetworkManager | 0.9.1.90-4.3.1 | openSUSE-current Updates v | NetworkManager | 0.9.1.90-4.1.3 | openSUSE-current OSS v | NetworkManager-kde4-libs | 0.9.0.2-4.2 | Tumbleweed i | NetworkManager-kde4-libs | 0.9.1+0.9.0-1.6.1 | openSUSE-current Updates v | NetworkManager-kde4-libs | 0.9.1git20111027-1.3.1 | openSUSE-current Updates v | NetworkManager-kde4-libs | 0.9.1git20111027-1.1.2 | openSUSE-current OSS v | NetworkManager-kde4-libs-lang | 0.9.0.2-4.2 | Tumbleweed i | NetworkManager-kde4-libs-lang | 0.9.1+0.9.0-1.6.1 | openSUSE-current Updates v | NetworkManager-kde4-libs-lang | 0.9.1git20111027-1.3.1 | openSUSE-current Updates v | NetworkManager-kde4-libs-lang | 0.9.1git20111027-1.1.2 | openSUSE-current OSS So if I do a "dup --from Tumbleweed", it installs the two packages from Tumbleweed (with vendor change): The following packages are going to be downgraded: NetworkManager-kde4-libs NetworkManager-kde4-libs-lang ...which then triggers another install of patch 535 which installs the packages from the update repo again. As I said, I can lock either the packages in Tumbleweed or the patch to prevent that, but the two packages should probably not be in Tumbleweed just like the rest of NetworkManager? Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org