public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lina Pezzella <j4rg0n@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] (media-video) ffmpeg and a52dec
Date: Mon, 18 Apr 2005 21:32:25 -0400	[thread overview]
Message-ID: <a4d8fa5d904e0f62eaf285174bc84874@gentoo.org> (raw)
In-Reply-To: <200504182329.52782@enterprise.flameeyes.is-a-geek.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>> Marking the newer
>> ffmpeg stable relies on marking a52dec-0.7.4-r4 stable as well.  From
>> what I can see in bgo, this seems like a reasonable thing to do...
> Seems like the only bug open for last ffmpeg is aac-related and is an 
> upstream
> bug which is present also in older version. Still there's my ebuild 
> cleanup
> which I'd like to merge asap, but I don't think can be made stable for 
> now.
> And there's just a prelink problem with a52dec.

If you do an ebuild cleanup, please look at the following bug and 
please *please* don't break my patch - it's huge and took forever to 
make:

http://bugs.gentoo.org/show_bug.cgi?id=73542

I'm waiting on trying to figure out the oggvorbis problem before 
putting those patches in portage for ppc-macos.

- --Lina Pezzella
Ebuild/Porting Co-Lead
Gentoo for Mac OS X
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFCZF+pNJ9STR9DbYERAkH3AKCWCTEu0mZ7qai/+dkk9U58CKwNnQCfTx/i
9NYL5+yZLL1FYjCHUl2BvSU=
=NmMc
-----END PGP SIGNATURE-----

-- 
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-04-19  1:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 20:55 [gentoo-dev] (media-video) ffmpeg and a52dec Aron Griffis
2005-04-18 21:26 ` Aron Griffis
2005-04-19  0:34   ` Diego 'Flameeyes' Pettenò
2005-04-19 11:40     ` Luca Barbato
2005-04-18 21:29 ` Diego 'Flameeyes' Pettenò
2005-04-18 21:35   ` Aron Griffis
2005-04-19  1:32   ` Lina Pezzella [this message]
2005-04-20 21:34 ` Vibhav Garg
2005-04-20 22:20   ` Aron Griffis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a4d8fa5d904e0f62eaf285174bc84874@gentoo.org \
    --to=j4rg0n@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox