* Jan Engelhardt [01-10-16 18:58]:

On Monday 2016-01-11 00:54, Patrick Shanahan wrote:

...

Appears there have been several packages replaced but not removed from system in last few updates, re:

Did you actually use `zypper dup` during your update?

zypper -v dup Yes. -- (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

* Andrei Borzenkov [01-10-16 22:24]:

11.01.2016 02:54, Patrick Shanahan пишет:

...

Appears there have been several packages replaced but not removed from system in last few updates, re:

All of them are versionned library packages. With my bacgkground I'd say it is normal and expected. That is exact reason to create versionned package in the first place - so multiple versions can coexist.

...

I have removed all of the above w/o seeing any ill effects (so far).

Good for you. Now imagine you compiled a program using one of these versions ...

*If* I had, my system should have a *requirement* for *that* package which it did/does not. And the *extra* versions are not even available for download from software.opensuse.org now. They should have been removed when the newer packages were installed since there were no local requirements for them. -- (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

On 11.01.2016 11:29, Andrei Borzenkov wrote:

On Mon, Jan 11, 2016 at 7:16 AM, Patrick Shanahan wrote:

How should system know you compiled something using this specific library version?

If that's something a distribution wants to support then it should make a hack for its packager with which it searches for all executables on root and checks their library dependencies. Or if it doesn't want to use a hack but wants to have non-packaged executables then it shouldn't remove anything ever. The only ones who would want to have something like this is lazy developers who don't want to bother to package their software or even recompile it on updates, which they should be doing so their software wouldn't become incompatible with newer versions. This is not something that normal users should be glad about.

...

And the *extra* versions are not even available for download from software.opensuse.org now. They should have been removed

No, they should not.

Yes, they should. Especially if libraries are removed from their repo. Personally, I always open Yast and remove "orphaned packages" after an update but it would be nice to have that as a zypper option. Along with an option to install translations without "recommended" and "suggested" stuff.

...

when the newer packages were installed since there were no local requirements for them.

That is something packaging tools cannot know.

If packaging tool doesn't track an executable then it should be removed or put into /use/local or /opt. But maintenance of such executables is entirely on hands of its creators. What is it, some kind of Windows ? We don't need dll-hell around here.

On Mon, 2016-01-11 at 09:59 +0100, Jan Engelhardt wrote:

On Monday 2016-01-11 07:29, Andrei Borzenkov wrote:

...

On Mon, Jan 11, 2016 at 7:16 AM, Patrick Shanahan wrote:

...

 And the *extra* versions are not even available for download from software.opensuse.org now.  They should have been removed

No, they should not.

Check your facts - of course they should. There is a list of these packages, but apparently that was not updated.

_product:openSUSE-release/openSUSE-release.spec:

Provides: weakremover(libboost_wave1_46_1) Provides: weakremover(libboost_wave1_46_1-32bit) [...] Provides: weakremover(yast2-boot-server) [...]

I *think( (need to confirm) that the problem here is that the list of removes is based on released products vs the latest snapshot... it does not take different TW Snapshots into account (as the list is completely created 'from scratch' all over, which means for old TW snapshots there is no 'list' of what has even been available, making such a list quite difficult to be recreated (and be able t0 be recreated). Cheers, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org