[MPlayer-users] Re: Recoring this *.ram to WAV with mplayer works while logged in but not from at.
inverseparadox at comcast.net
Tue Apr 11 17:44:42 CEST 2006
Adam Funk wrote:
> On 2006-04-11, The Wanderer <inverseparadox at comcast.net> wrote:
>> Adam Funk wrote:
>>> I said that because last week was the first time I had any
>>> problems with the script that uses that command. I have to admit
>>> the version numbering confuses me:
>>> 1.0-pre7-0.0 <-- the Debian package version .deb I have installed
>>> (this now says upgradeable, so I'll try it)
>>> 1.0pre7-3.3.5 <-- what I have acc. to mplayer's output
> 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.
> Debian package:
> mplayer output:
> MPlayer dev-CVS--4.0.3 (C) 2000-2006 MPlayer Team
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.
It's not your fault - it's the fault of the person who packages MPlayer
for Debian, who is Christian Marillat IIRC. That doesn't change the
> 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.
>> MPlayer was the first program I ever obtained and installed from
>> CVS, and I've never seriously regretted it.
> 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.
>>> 1.0pre7try2 <-- now on the download page of www.mplayerhq.hu
> You have to admit, that version number is a bit confusing too. Does
> it mean the second attempt to get ready for release 7 of version 1.0?
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.
Warning: Simply because I argue an issue does not mean I agree with any
side of it.
Secrecy is the beginning of tyranny.
More information about the MPlayer-users