On Fri, May 13, 2016 at 01:13:34PM +0200, Sebastian Ramacher wrote:
> (Please CC me, I'm not subscribed.)
>
> Hi
>
> On 2016-05-02 20:46:37, Brian May wrote:
> > Raphael Hertzog writes:
> >
> > > There's also an alternate way to go forward... continue to support
> > > the current version with p
(Please CC me, I'm not subscribed.)
Hi
On 2016-05-02 20:46:37, Brian May wrote:
> Raphael Hertzog writes:
>
> > There's also an alternate way to go forward... continue to support
> > the current version with paid external help if needed.
>
> Starting to look like it will be a better approach.
On Tue, 03 May 2016, Brian May wrote:
> I have a suspicion that many of these installs may be due libav being
> installed to satisfy dependancies. There are a large number of packages
> that do depend on libav.
Yes, that's obvious, a library is usually installed by way of
dependencies. But if you
Raphael Hertzog writes:
> We have 15% of the sponsors listing at least one of the binary packages
> built by libav in their package list. That's relatively close to Xen
> (17.4%) where we are going to spend money for external help. That said
> none of the customers expressed their reliance on thi
Hi,
On Mon, 02 May 2016, Holger Levsen wrote:
> have you asked the libav maintainers for support / feedback? They might
> not be able to do the work, but I could imagine they would help with
> hints and reviews or such…
FYI
https://lists.debian.org/2015205942.ga14...@ramacher.at
https://list
Hi,
have you asked the libav maintainers for support / feedback? They might
not be able to do the work, but I could imagine they would help with
hints and reviews or such…
--
cheers,
Holger
signature.asc
Description: Digital signature
Raphael Hertzog writes:
> There's also an alternate way to go forward... continue to support
> the current version with paid external help if needed.
Starting to look like it will be a better approach. Have been attempting
to compile random dependancies manually, and so far only one of them has
Hello,
On Sun, 13 Mar 2016, Brian May wrote:
> > 2. Spend some time on investigating what it takes to backport
> > libav from jessie to wheezy. 11.x is still supported by
>
> Looks like the SONAME has changed. Presumably this means anything
> depending on libav will need to be rebuilt?
There's a
