Re: latest xine-lib in Debian unstable

Uwe Bugla <[email protected]> writes:
>
> Yes, earlier versions of xine-lib worked _purrrrrrfect_, in so far it _is_ a 
> regression in xine-lib, definitely!

Which version did work for you correctly? I'd suggest that you hg bisect
in order to find the exact hg commit which caused the regression.

Since I don't use xine for dvb, I fear that I cannot help you with that.

> I am working with a small not yet released self-built TCL/TK/Iwidgets-4.0 
> project using time-shifting: dvbstream records something, then the system 
> sleeps a couple of seconds, then the player starts to play back the recorded 
> material. That way recording engine and playback engine _race_ against each 
> other (like two cars - time-shifted).

sounds interesting. Please CC me when you release your first version!

> If the sleep timing is too short, the whole thing dies after a couple of 
> minutes (usually two or three - but never in this life after half an hour!).
>
> As a consequence I can definitely exclude the timing issue as possible case 
> for the breakdown.
>
> Thus the regression in xine-lib is the only possible reason for the crash, at 
> least in my perception.
>
> See: If you are recording real nice rarities (like the legendary Rockpalast 
> gig of _Grateful Dead_ in 1981 f. ex. last night), and the recording breaks 
> down after a while that really bothers you as some events do _not_ appear too 
> often on TV - especially the legendary jewelry that is being broadcasted once 
> in ten or twenty years :(

I'm sorry :(

>>
>> > Please do your best to make that lib stable, so that such an accident
>> > does not happen again.
>>
>> Hints how to do that would help. Offer for help as well.
>
> Ain't no programmer, but I do my best to describe the issues as precise as 
> possible :)
>
> Let's try to activate the xine maintainers and developers :)

Yes, lets see if someone of them can comment on this.

>
> I guess xine-lib was moved from experimental to unstable in a far to early 
> state, wasn't it?

No, it was in experimental because the new version was not fit for the
'etch' release. Since lenny is not frozen yet, new upstream versions are
fine for 'unstable'.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/