Hi Ian,
Ian Goldberg wrote (01 Nov 2014 18:15:28 GMT) :
> But don't you *want* programs compiled against, say, 4.2, not to be able
> to run with, say, 4.0? If it's compiled against 4.2, even if it doesn't
> use functions added in 4.2, it may use data structures that have
> changed.
Sure.
When r
On Sat, Nov 01, 2014 at 06:19:16PM +0100, intrigeri wrote:
> > * Generate and maintain a symbols file.
>
> Note that this is enough if, and only if, we don't reintroduce
> upstream's runtime version check (which we're going to remove for
> Jessie). If we reintroduce this check, reverse-deps comp
> * Generate and maintain a symbols file.
Note that this is enough if, and only if, we don't reintroduce
upstream's runtime version check (which we're going to remove for
Jessie). If we reintroduce this check, reverse-deps compiled against
a new version of the library won't be able to run agains
Package: libotr5
Version: 4.1.0-1
Severity: important
For Jessie+1, in order to avoid issues like #767230 and #767075 from
happening again, we need to do (at least?) one of:
* Pass dh_makeshlibs the -V option, with or without an argument.
WIP on the "shlibs" branch in the packaging reposito
4 matches
Mail list logo
