On Fri, 29 Aug 2014, Johannes Schauer wrote: > Hi, > > Quoting Raphael Hertzog (2014-08-29 21:16:06) > > If that is ever implemented, it must apply only on dependencies that can be > > parsed on the source's debian/control because I would not be happy to have > > warnings on library dependencies generated by dpkg-shlibdeps. > > How can it happen that library dependencies generated by dpkg-shlibdeps create > a dependency on a package version older than in old stable?
When a library has a symbols file that has evolved over more than 2 releases (like libc6)... see /var/lib/dpkg/info/libc6:amd64.symbols it references versions as old as 2.2.5 when oldstable currently has 2.11. > You mean the sentence "Versioned dependencies are problematic for > bootstrapping > because versioned compiler dependencies have to be translated and the versions > of binary packages is not known a priori during a bootstrap from zero." Yes. > compiling. The other is all other "versions of binary packages" because they > have to be associated to source packages but it cannot be known from which > version of a source package they build. This is a wrong problem given that in the majority of the case a given binary package will only be produced by a single source package. The binary package might be referenced multiple times in some rare cases of binary packages moving between source packages but I hardly doubt that this is a serious problem for bootstrapping a new architecture. It doesn't happen that often. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
