On Friday, July 22, 2016 9:24:06 PM WIB Patrick Shanahan wrote:

* C. Brouerius van Nidek [07-22-16 21:21]:

...

With todays zypper dup I got following results.

13 packages to upgrade, 93 to downgrade, 53 to change vendor. Overall download size: 77.3 MiB. Already cached: 0 B. After the operation, additional 4.6 MiB will be used. Continue? [y/n/? shows all options] (y):

93 downgrades seems a little over the top so I abstained from this update unless I get some reassurances and a explanation that nothing is amiss.

Rocket science.

Do up's instead of dups when you see excessive operations in the wrong direction, until they have all built. When the next build is announced, it should be correct.

Thanks for the reminder. A sole 23 updates is the result. As I have a relatively slow internet connection I do a daily update in order not to get all at onec with a snapshot.This is the first time that I got s abnormal result wit zypper dup. -- Linux User 183145 using Tumbleweed on a Pentium IV System : Linux 4.6.4-1-default Distro : openSUSE 20160720 (x86_64) Desktop: KDE Frameworks: 5.24.0 and Plasma 5.7.0 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Saturday 2016-07-23 03:41, Patrick Shanahan wrote:

* C. Brouerius van Nidek [07-22-16 21:36]: [...]

...

Thanks for the reminder. A sole 23 updates is the result.

As I have a relatively slow internet connection I do a daily update in order not to get all at onec with a snapshot.This is the first time that I got s abnormal result wit zypper dup.

I have seen it before, usually when an update has not yet completed build, iiuc.

If an update has not built yet, then you cannot upgrade to it. But that also means there is nothing to downgrade to, because you are already on the old version. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Thomas Langkamp [07-23-16 05:00]:

Am 23.07.2016 um 10:17 schrieb Jan Engelhardt:

...

On Saturday 2016-07-23 03:41, Patrick Shanahan wrote:

...

* C. Brouerius van Nidek [07-22-16 21:36]: [...]

...

Thanks for the reminder. A sole 23 updates is the result.

As I have a relatively slow internet connection I do a daily update in order not to get all at onec with a snapshot.This is the first time that I got s abnormal result wit zypper dup.

I have seen it before, usually when an update has not yet completed build, iiuc.

If an update has not built yet, then you cannot upgrade to it. But that also means there is nothing to downgrade to, because you are already on the old version.

the following applies only to packman-repo-users:

The downgrades for me were caused mostly by ffmpeg 3.x to 2.x downgrade and thus quite some other stuff had to downgrade too and also quite some stuff switched from packman to official repo without a "real" downgrade. Only the buildnumbers were lower. So a zypper dup is still the right thing to do - otherwise you will stay with ffmpeg 3.x and get new packages at the same time that expect ffmpeg 2.x. they might not work together fully.

how did I find out? I ran zypper -v dup instead of zypper dup and looked closely. I think zypper -v dup should be the default. Same as running zypper inside screen should be the default. But there might be technical reasons against this I am not aware of - I am only a mere mortal user, not a dev ;)

You must remember that these "upgrades" actually provide packages w/o the functions provided by packman which are encombered by law/license and not provided by opensuse. USing "up" vs "dup" for these cases allows the process to complete w/o loosing desired function. And in my case, lowering the preference number for packaman is not sufficient to use "dup" w/o the vendor change. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Schöne Grüße Axel Braun -- Written from cell phone - excuses for typos Am 23. Juli 2016 15:39:51 MESZ, schrieb "Carlos E. R." :

On 2016-07-23 10:58, Thomas Langkamp wrote:

...

the following applies only to packman-repo-users:

The downgrades for me were caused mostly by ffmpeg 3.x to 2.x downgrade and thus quite some other stuff had to downgrade too and also quite some stuff switched from packman to official repo without a "real" downgrade. Only the buildnumbers were lower. So a zypper dup is still the right thing to do - otherwise you will stay with ffmpeg 3.x and get new packages at the same time that expect ffmpeg 2.x. they might not work together fully.

how did I find out? I ran zypper -v dup instead of zypper dup and looked closely. I think zypper -v dup should be the default. Same as running zypper inside screen should be the default. But there might be technical reasons against this I am not aware of - I am only a mere mortal user, not a dev ;)

Try this instead:

export SOLVER_FLAG_DUP_ALLOW_VENDORCHANGE=0 zypper dup

That way zypper will not switch packman packages to oss packages or the other way round. It will respect vendor stickiness.

I do not know if there is a command line switch to do the same. The feature was experimental about may 2015.

Out of my head: --no-vendor-change -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Saturday, July 23, 2016 6:22:47 PM WIB Oliver Kurz wrote:

On Saturday 23 July 2016 17:50:46 Axel Braun wrote:

...

...

On 2016-07-23 10:58, Thomas Langkamp wrote:

...

the following applies only to packman-repo-users: […]

...

That way zypper will not switch packman packages to oss packages or the other way round. It will respect vendor stickiness.

I do not know if there is a command line switch to do the same. The feature was experimental about may 2015.

Out of my head: --no-vendor-change

Something like this. What I use as a normal upgrade alias is

zp dup --no-allow-vendor-change

which is doing the right thing by default.

In my case it "only" shows 53 problems for which you have to answer '1' or skip, retry or cancel [1/s/r/c] (c):, 53 times. Not a workable solution. ------------------------------------------- Computing upgrade... 53 Problems: Problem: problem with installed package gstreamer-1.8.2-75.13.x86_64 Problem: problem with installed package gstreamer-0_10-0.10.36-21.7.x86_64 Problem: problem with installed package gstreamer-0_10- lang-0.10.36-21.7.noarch Problem: problem with installed package gstreamer-0_10-plugin- esd-0.10.31-89.19.x86_64 Problem: problem with installed package gstreamer-0_10-plugins- base-0.10.36-17.1.x86_64 Problem: problem with installed package gstreamer-0_10-plugins- base-32bit-0.10.36-17.1.x86_64 Problem: problem with installed package gstreamer-0_10-plugins-base- lang-0.10.36-17.1.noarch Problem: problem with installed package gstreamer-0_10-plugins- good-0.10.31-89.19.x86_64 Problem: problem with installed package gstreamer-0_10-plugins- good-32bit-0.10.31-89.19.x86_64 Problem: problem with installed package gstreamer-0_10-plugins-good- extra-0.10.31-89.19.x86_64 Problem: problem with installed package gstreamer-0_10-plugins-good- extra-32bit-0.10.31-89.19.x86_64 Problem: problem with installed package gstreamer-0_10-plugins-good- lang-0.10.31-89.19.noarch Problem: problem with installed package gstreamer-32bit-1.8.2-75.13.x86_64 Problem: problem with installed package gstreamer-lang-1.8.2-75.13.noarch Problem: problem with installed package gstreamer-plugins- base-1.8.2-72.11.x86_64 Problem: problem with installed package gstreamer-plugins- base-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package gstreamer-plugins- good-1.8.2-81.3.x86_64 Problem: problem with installed package gstreamer-plugins- good-32bit-1.8.2-81.3.x86_64 Problem: problem with installed package gstreamer-plugins-good- extra-1.8.2-81.3.x86_64 Problem: problem with installed package gstreamer-plugins-good- extra-32bit-1.8.2-81.3.x86_64 Problem: problem with installed package libchromaprint1-1.3.1-30.7.x86_64 Problem: problem with installed package libgstallocators-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgstallocators-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libgstapp-0_10-0-0.10.36-17.1.x86_64 Problem: problem with installed package libgstapp-0_10-0-32bit-0.10.36-17.1.x86_64 Problem: problem with installed package libgstapp-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgstapp-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libgstaudio-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgstaudio-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libgstfft-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgstfft-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libgstinterfaces-0_10-0-0.10.36-17.1.x86_64 Problem: problem with installed package libgstinterfaces-0_10-0-32bit-0.10.36-17.1.x86_64 Problem: problem with installed package libgstpbutils-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgstpbutils-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libgstreamer-0_10-0-0.10.36-21.7.x86_64 Problem: problem with installed package libgstreamer-0_10-0-32bit-0.10.36-21.7.x86_64 Problem: problem with installed package libgstreamer-1_0-0-1.8.2-75.13.x86_64 Problem: problem with installed package libgstreamer-1_0-0-32bit-1.8.2-75.13.x86_64 Problem: problem with installed package libgstriff-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgstriff-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libgstrtp-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgstrtp-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libgstrtsp-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgstrtsp-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libgstsdp-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgstsdp-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libgsttag-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgsttag-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libgstvideo-1_0-0-1.8.2-72.11.x86_64 Problem: problem with installed package libgstvideo-1_0-0-32bit-1.8.2-72.11.x86_64 Problem: problem with installed package libopencv3_1-3.1.0-88.30.x86_64 Problem: freshplayerplugin-0.3.5-2.1.x86_64 conflicts with flash-player provided by flash-player-11.2.202.626-2.1.x86_64 Problem: problem with installed package gstreamer-1.8.2-75.13.x86_64 Solution 1: install gstreamer-1.8.2-1.1.x86_64 (with vendor change) http://packman.links2linux.de --> openSUSE Choose the above solution using '1' or skip, retry or cancel [1/s/r/c] (c): -- Linux User 183145 using Tumbleweed on a Pentium IV System : Linux 4.6.4-1-default Distro : openSUSE 20160720 (x86_64) Desktop: KDE Frameworks: 5.24.0 and Plasma 5.7.0 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2016-07-23 19:07, C. Brouerius van Nidek wrote:

On Saturday, July 23, 2016 6:22:47 PM WIB Oliver Kurz wrote:

...

On Saturday 23 July 2016 17:50:46 Axel Braun wrote:

...

...

On 2016-07-23 10:58, Thomas Langkamp wrote:

...

Something like this. What I use as a normal upgrade alias is

zp dup --no-allow-vendor-change

which is doing the right thing by default.

In my case it "only" shows 53 problems for which you have to answer '1' or skip, retry or cancel [1/s/r/c] (c):, 53 times. Not a workable solution.

At the time when the feature started, they asked for comments. So, just report the issue you found in a bugzilla. -- Cheers / Saludos, Carlos E. R. (from openSUSE Leap 42.1 x86_64 (test)) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

"Used to be" one only restarted his linux system to install a new kernel, but seems now that restart is also necessary for dbus. Is there a method w/o restart or .... And why is "systemctl restart dbus" provided if it is not to be used? tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am 23. Juli 2016 17:52:25 MESZ , schrieb "C. Brouerius van Nidek" :

Here follows the result which does not give me any clue but may give you an idea what is wrong:

There is nothing wrong with this list, it just looks scary. Very few packages need to come from packman since the uncoordinated effort to provide ffmpeg via OBS started. Since that time many packages were provided by both sides. Packman uses the sources from the devel projects, which is fine. But this caused trouble for TW recently when ffmpeg was upgraded to ffmpeg3 without pushing that version to factory. To simplify the transition either hit "1" so many times, or call zypper with --allow-vendor-change if the repo list on that system allows it. Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 23/07/2016 21:39, Jan Engelhardt wrote:

On Saturday 2016-07-23 20:41, Olaf Hering wrote:

...

Am 23. Juli 2016 17:52:25 MESZ , schrieb "C. Brouerius van Nidek" :

...

Here follows the result which does not give me any clue but may give you an idea what is wrong: Packman uses the sources from the devel projects, which is fine. But this caused trouble for TW recently when ffmpeg was upgraded to ffmpeg3 without pushing that version to factory. So maybe PM should use the source in Factory instead…

If the ff-using packages in Factory are not ready, likely the ones in pm aren't either. I submitted the last package that didn't build with ffmpeg 3 to network:telephony openmcu. Every other package does. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 23/07/2016 23:26, Jan Engelhardt wrote:

On Saturday 2016-07-23 21:54, Dave Plater wrote:

...

...

...

Packman uses the sources from the devel projects, which is fine. But this caused trouble for TW recently when ffmpeg was upgraded to ffmpeg3 without pushing that version to factory. So maybe PM should use the source in Factory instead… If the ff-using packages in Factory are not ready, likely the ones in pm aren't either. I submitted the last package that didn't build with ffmpeg 3 to network:telephony openmcu. Every other package does. Oh I was speaking in abstract views. Because surely, there will be a future ffmpeg version which requires API changes in vlc, etc. again. From what I saw patching openmcu, ffmpeg depreciates the functions across one abi version then removes them. If the developers read the depreciation warnings and acted on them there wouldn't be a problem. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org