Re-promote gcc-3.3 to main

libstdc++5 has been added to fglrx-installer build-depends

Is there a reason not to fix this using a debian/shlibs.local file? It's a kludge, but unless libstdc++5 is needed to be part of main at run-time, I think it's better that than promoting (and supporting) gcc-3.3.

Also, which package is in restricted, here? I only see packages in multiverse; did someone (wrongly) demote fglrx-installer in response to the build failure?

It is needed at runtime as well for this library in question.

On Mon, Sep 22, 2008 at 19:51, Steve Langasek
<email address hidden>wrote:

> Is there a reason not to fix this using a debian/shlibs.local file?
> It's a kludge, but unless libstdc++5 is needed to be part of main at
> run-time, I think it's better that than promoting (and supporting)
> gcc-3.3.
>
> Also, which package is in restricted, here? I only see packages in
> multiverse; did someone (wrongly) demote fglrx-installer in response to
> the build failure?
>
> --
> Re-promote gcc-3.3 to main
> https://bugs.launchpad.net/bugs/271794
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Mario Limonciello
<email address hidden>

Mario Limonciello schrieb:
> It is needed at runtime as well for this library in question.

 - "this": which one?
 - why is it needed in main?

I do not want to have gcc-3-3 back in main.

libAMDXvBA.so.1.0

On Tue, Sep 23, 2008 at 00:17, Matthias Klose <email address hidden> wrote:

> Mario Limonciello schrieb:
> > It is needed at runtime as well for this library in question.
>
> - "this": which one?
> - why is it needed in main?
>
> I do not want to have gcc-3-3 back in main.
>
> --
> Re-promote gcc-3.3 to main
> https://bugs.launchpad.net/bugs/271794
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Mario Limonciello
<email address hidden>

It would be needed in main if the fglrx package were to continue to live in
the restricted component.

On Tue, Sep 23, 2008 at 01:07, Mario Limonciello <email address hidden> wrote:

> libAMDXvBA.so.1.0
>
>
>
> On Tue, Sep 23, 2008 at 00:17, Matthias Klose <email address hidden> wrote:
>
>> Mario Limonciello schrieb:
>> > It is needed at runtime as well for this library in question.
>>
>> - "this": which one?
>> - why is it needed in main?
>>
>> I do not want to have gcc-3-3 back in main.
>>
>> --
>> Re-promote gcc-3.3 to main
>> https://bugs.launchpad.net/bugs/271794
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
>
> --
> Mario Limonciello
> <email address hidden>
>

--
Mario Limonciello
<email address hidden>

Well, it looks like someone has done component-mismatch cleanup on the archive, and xorg-driver-fglrx is currently in multiverse. :/

I don't think we should move gcc-3.3 back into main, but it would be nice to be able to get xorg-driver-fglrx back into restricted. What uses libAMDXvBA at runtime, and how does it use it? I can't find anything else in this package which is linked to it; does something dlopen it?

gcc-3.3 isn't coming back to main, so To combat this problem, i've split the library in question into it's own package.

This bug was fixed in the package fglrx-installer - 2:8.543-0ubuntu3

---------------
fglrx-installer (2:8.543-0ubuntu3) intrepid; urgency=low

  * debian/control:
    - Drop build-depends on libstdc++5. (LP: #271794)
    - Drop build-depends on ia32-libs
    - Install libAMDXvBA.so* into it's own package.
  * debian/rules:
    - Work around missing libstdc++5 at build-depends time.
  * Add the following files to support this new binary package:
    - debian/libamdxvba.postinst
    - debian/libamdxvba.install.in

 -- Mario Limonciello <email address hidden> Thu, 16 Oct 2008 15:04:46 -0500