[Pkg-scicomp-devel] Fixing atlas on debian/Ubuntu

[David Cournapeau]

On Wed, Sep 9, 2009 at 9:03 PM, Sylvestre Ledru <sylvestre at debian.org> wrote:
> Le mercredi 09 septembre 2009 à 09:22 +0900, David Cournapeau a écrit :
>> On Mon, Sep 7, 2009 at 2:59 PM, Sylvestre Ledru<sylvestre at debian.org> wrote:
>
>> > However, I gonna have to wait for one or two weeks before of the upload
>> > because there are some large transitions in Debian going on [1] & [2].
>>
>> Ok, but the patches can be integrated in svn now, right ? This way, I
>> could quickly test them and help making the integration if problem
>> remain.
> Yep, I just committed all of them.
> They are available in the pkg-scicomp repository. If you want, you can
> applied to the team to have the write permissions on the svn.

I will track the project from git for now. I am afraid of applying to
one more thing for the time being :)

I saw you started integrating my patches - please note that the
NOSSE/SSE1/SSE2 support on 32 bits arch requires some new arch
defaults (the upstream arch default would fail with the first patch).

>
>> I am unfamiliar with debian release process: once you upload the
>> package, do people running unstable see their package updated ?
> Yes and no.
> With a standard application, yes.
> Here, no because we are dealing with a massive change of an important
> library with ABI changes.

Which ABI changes ? A package built against 3.6.20 should run against
3.8.3, normally.

I was also wondering about the -dev -> -dbg renaming: what's the
rationale ? isn't dbg reserved for debug packages ?

cheers,

David