[opensuse-packaging] SONAME question
I just updated filesystems:ntfs-3g_ntfsprogs to have a new SONAME (83 -> 84) Do I need to add a Obsoletes: statement? Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
El 23/05/13 21:51, Greg Freemyer escribió:
I just updated to have a new SONAME (83 -> 84)
Do I need to add a Obsoletes: statement?
No, no Obsoletes for the case of shared libraries, ever ;-) by that I mean libfoo84 should never obsolete libfoo83 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Thu, May 23, 2013 at 10:27 PM, Cristian Rodríguez <crrodriguez@opensuse.org> wrote:
El 23/05/13 21:51, Greg Freemyer escribió:
I just updated to have a new SONAME (83 -> 84)
Do I need to add a Obsoletes: statement?
No, no Obsoletes for the case of shared libraries, ever ;-) by that I mean libfoo84 should never obsolete libfoo83
Christian, I have to ask for clarification. I maintain a package that changed the library/sub-package name from libtsk3 to libtsk. They changed the soname from 9 to 10 with the rename. So on my test machine now I have both libtsk3-9 and libtsk10 installed. (libtsk3-9 was a factory/security project only release. libtsk3-3 was in 12.3) Is having both installed simultaneously a bug? Or just the way it works? libtsk3-3 is in openSUSE 12.3 and libtsk-10 is in factory. For normal users I assume a zypper dup will leave libtsk3-3 in place forever. Again, I don't know if that is a bug or not. Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
El 27/08/13 16:56, Greg Freemyer escribió:
Is having both installed simultaneously a bug? Or just the way it works?
For normal users I assume a zypper dup will leave libtsk3-3 in place forever. Again, I don't know if that is a bug or not.
No, it is not a bug, it is exactly how it should work. Cleaning up unused old libraries after upgrade is a task that needs to be implemented in the package manager itself. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Tuesday 2013-08-27 23:26, Cristian Rodríguez wrote:
El 27/08/13 16:56, Greg Freemyer escribió:
Is having both installed simultaneously a bug? Or just the way it works?
For normal users I assume a zypper dup will leave libtsk3-3 in place forever. Again, I don't know if that is a bug or not.
No, it is not a bug, it is exactly how it should work.
Cleaning up unused old libraries after upgrade is a task that needs to be implemented in the package manager itself.
Aren’t there special obsolete lists in the yast2-type metadata (basically a diff between 12.2 and 12.3 package lists, for example), which hint zypper to see whether {an old library can be removed without generating a dependency problem}? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Jan Engelhardt <jengelh@inai.de> writes:
Aren’t there special obsolete lists in the yast2-type metadata (basically a diff between 12.2 and 12.3 package lists, for example), which hint zypper to see whether {an old library can be removed without generating a dependency problem}?
There is never a need to obsolete a pure library package. Once no other package requires it any more it can safely be removed. This is even true for library packages that still exist. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Quoting Andreas Schwab <schwab@suse.de>:
Jan Engelhardt <jengelh@inai.de> writes:
Aren’t there special obsolete lists in the yast2-type metadata (basically a diff between 12.2 and 12.3 package lists, for example), which hint zypper to see whether {an old library can be removed without generating a dependency problem}?
There is never a need to obsolete a pure library package. Once no other package requires it any more it can safely be removed. This is even true for library packages that still exist.
Whereas this statement is true, it needs to be noted that zypper* / yast do not currently have a 'cleanup of no longer needed libs' functionality (and rpmoorphan is a little bit too enthusiastic: LIBreoffice is not a lib :) ) * I actually recently discovered that zypper DOES have cleanup, but you need to do the right things. so instead of 'zypper rm <package>', you'd use 'zypper rm -u <package>' which triggers removal of packages that were left only for this package (as last consumer) on the system... this should become default imho! Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 28 August 2013 08:16, Dominique Leuenberger a.k.a. Dimstar <dimstar@opensuse.org> wrote:
* I actually recently discovered that zypper DOES have cleanup, but you need to do the right things. so instead of 'zypper rm <package>', you'd use 'zypper rm -u <package>' which triggers removal of packages that were left only for this package (as last consumer) on the system... this should become default imho!
$ fgrep solver.cleandepsOnRemove -B15 /etc/zypp/zypp.conf ## ## EXPERTS ONLY: Cleanup when deleting packages. Whether the solver should ## per default try to remove packages exclusively required by the ones he's ## asked to delete. ## ## This option should be used on a case by case basis, enabled via ## command line options or switches the applications offer. Changing ## the global default on a system where unattended actions are performed, ## may easily damage your system. ## ## CHANGING THE DEFAULT IS NOT RECOMMENDED. ## ## Valid values: boolean ## Default value: false ## solver.cleandepsOnRemove = true Also, there is a bug report I can't find any more about how this works. Last time I checked it depended on parsing the whole /var/log/zypp/history file. A flag in the RPM database sounds nicer. And the semantics about the "InstallationImage" entries where not very clear. IIRC the problem was about some entries containing a "root@opensuse" column and others an empty column. In any case, it would be something to suggest in the zypp-devel list. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Wednesday 2013-08-28 09:00, Andreas Schwab wrote:
Jan Engelhardt <jengelh@inai.de> writes:
Aren’t there special obsolete lists in the yast2-type metadata (basically a diff between 12.2 and 12.3 package lists, for example), which hint zypper to see whether {an old library can be removed without generating a dependency problem}?
There is never a need to obsolete a pure library package. Once no other package requires it any more it can safely be removed. This is even true for library packages that still exist.
I did not mean to imply that an Obsolete: was in play. Rather, if you upgraded your system using methods other than `zypper dup` (for example, by only doing `zypper up`, and for downgrades/arch changes `zypper in`), then, what I seem to remember is that a subsequent `zypper dup` will suggest library packages for removal - but not all of the unused ones. I’ll just have to watch the next upgrade. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (6)
-
Andreas Schwab -
Cristian Morales Vega -
Cristian Rodríguez -
Dominique Leuenberger a.k.a. Dimstar -
Greg Freemyer -
Jan Engelhardt