Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 69509 - gstreamer-0.8.7 is released since 06-Oct-2004
Summary: gstreamer-0.8.7 is released since 06-Oct-2004
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All All
: High enhancement (vote)
Assignee: GStreamer package maintainers
URL: http://gstreamer.freedesktop.org/rele...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-30 08:32 UTC by Dick Marinus
Modified: 2004-10-30 16:58 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dick Marinus 2004-10-30 08:32:35 UTC 
gstreamer-0.8.7 is released since 06-Oct-2004, gstreamer-0.8.5 is in portage
please update

Features:
    * spider, queue fixes
    * fakesrc and identity now have a datarate property
    * dataprotocol threadsafety fix
    * Parallel installability with 0.6.x series
    * Internationalization
    * important thread fix for playback
    * typefind fix
Comment 1 foser (RETIRED) gentoo-dev 2004-10-30 11:03:53 UTC 
there's requests and requests, but this beats them all.

*** This bug has been marked as a duplicate of 65210 ***
Comment 2 Dick Marinus 2004-10-30 11:11:37 UTC 
I'm asking for 0.8.7, *not* 0.8.5 (#65210), which is already in portage...
I suppose this isn't a duplicate of #65210 ... if not, please reopen #65210
Comment 3 foser (RETIRED) gentoo-dev 2004-10-30 13:46:39 UTC 
*sigh* are you really blind ?

and dont CC me without asking & don't reopen without checking facts, you are making a fool of yourself in this whole report.
Comment 4 Zaheer Abbas Merali (RETIRED) gentoo-dev 2004-10-30 16:58:45 UTC 
Basically, go to http://packages.gentoo.org and search for gstreamer.  You will see that the latest gstreamer in portage is 0.8.7.  It is just masked as ~x86 so you would only notice it if you have ~x86 keyword.

That is why the bug is closed.