Re: Updating policy
Josip Rodin wrote:
> They do, the shlibs file needs modification for a safe upgrade, see Julian's
> message in the log for this bug (#55730).
He said:
| How do we ensure that someone upgrading a package from potato to woody
| pulls in all of the required libraries? As a "concrete" example,
| /usr/bin/foo in the foo package depends upon libbar directly and
| libbar depends upon libbaz indirectly. In potato, libbar does not
| declare a dependency upon libbaz, although it will in woody.
However, this is untrue: If libbar is built with debhelper, the potato
version already has the dependancy on libbaz, since debhelper already
ran dpkg-shlibdeps on libbar.so. Julian's idea to use the shlibs file
seems uncalled for in this case.
| Now the user decides that they wish to install foo, for some reason
| they choose to install the unstable foo. Now they will need to
| install libbar to fulfill foo's dependencies, but the potato libbar
| doesn't depend upon libbaz.
--
see shy jo
Reply to: