[MPlayer-users] Re: Recoring this *.ram to WAV with mplayer works while logged in but not from at.
a24061 at yahoo.com
Tue Apr 11 18:04:00 CEST 2006
On 2006-04-11, The Wanderer <inverseparadox at comcast.net> wrote:
>> After a bit of messing around with aptitude (some dependency
>> confusion, probably of my own making, I am now here:
> I've noticed that aptitude can do that to you.
What do you use/recommend?
> Be warned that this version number will get you ignored if you attempt
> to make any bug reports; it eliminated the date of the CVS timestamp
> (which should have been in the middle of that double hyphen), which is
> contrary to MPlayer's packaging guidelines and means that people who
> might otherwise handle such a report will have no idea what version of
> the code you're actually using.
I don't think I'm close enough to grasping all this stuff yet to make
>> This upgrade seems to have fixed the problem I originally reported.
>> I don't understand that, however, since the problem first occurred
>> very recently.
> Can't help you there, I'm afraid.
That's OK, I don't need any help now that it works again!
>> OK, when I'm feeling a little brave I'll try it.
> Unless you try to install Debian packages which depend on the MPlayer
> package (unlikely, since the MPlayer package itself is unofficial),
> there should be no problems with having MPlayer installed via a non-deb
> means; I've certainly never had any problem with it. Also, unlike many
> projects, the CVS of MPlayer is intended to be in stable, usable
> condition at all times; there should be no need for concern about using
> a "development" version.
OK, when I've got some time to mess with it, I'll try it!
> It means "well, we already released the seventh prerelease of version
> 1.0, but something was wrong - here's the second try at that release".
> IIRC, what was wrong was a security hole, which was identified and
> patched quickly enough after the release that a second update was felt
> to be warranted.
More information about the MPlayer-users