You are not logged in.
Hi
after an update of Audacious package to the newsest version
audacious failed to start. The problem is that the maintainer didn't include libmcs in the
requirements array in the PKGBUILD file.
Offline
Yes and also because of "fluidsynth" depends, it install jack-audio-connection-kit. audacious-plugins-1.2.5-3 version jack is optional!
Offline
just edit the audacious plugins pkgbuild to your needs. i ve doing that since i switched to audacious and the update worked just fine
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
I would seriously recommend the maintainer to actually read whats new (audacious-media-player.org) to avoid this kind of mistakes in the future...
I quote;
Also, you should note that 1.3 requires libmcs in order to build and run.
You shouldn't have to edit a PKGBUILD this way, to make a package in "extra" to run. Where's the quality control?
"Your beliefs can be like fences that surround you.
You must first see them or you will not even realize that you are not free, simply because you will not see beyond the fences.
They will represent the boundaries of your experience."
SETH / Jane Roberts
Offline
Chill please.
A bug has been reported, and a fix is on the way.
You've never made a mistake?
Offline
only humans make mistakes
edit: btw was it just me or did the player start as if it was running for the first time? settings lost etc. probably cause i launched it the 1st time with the 1.2.5 plugins
Last edited by dolby (2007-03-07 20:50:57)
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
edit: btw was it just me or did the player start as if it was running for the first time? settings lost etc.
same here
Offline
You shouldn't have to edit a PKGBUILD this way, to make a package in "extra" to run. Where's the quality control?
Apologies - if you notice, I did bring libmcs from AUR/unsupported into [extra] for this very purpose, I just accidentally listed it as a makedepend instead of a full dependency. Small mistake, I'm fixing now.
Offline
Yes and also because of "fluidsynth" depends, it install jack-audio-connection-kit. audacious-plugins-1.2.5-3 version jack is optional!
Arg - jack is supposed to be optional, I don't know why I put fluidsynth in there. It's removed in the coming fix... I must have been mighty tired when I packaged up this update.
Offline
Having another weird problem too: for some reason it's no longer finding the custom skins that I have installed in ~/.audacious/Skins
Anyone have any idea?
Offline
Having another weird problem too: for some reason it's no longer finding the custom skins that I have installed in ~/.audacious/Skins
Anyone have any idea?
FYI - the skins are .wsz files. Should that make a difference? (I'd think no, since they always worked in the past, but you never know.)
Last edited by darose (2007-03-08 16:50:29)
Offline
also i noticed that playlist transarency is no longer supported? still the player works many times better than the previous release. congrats to the dev team
edit: skins work like they did before here
Last edited by dolby (2007-03-08 16:56:21)
There shouldn't be any reason to learn more editor types than emacs or vi -- mg (1)
[You learn that sarcasm does not often work well in international forums. That is why we avoid it. -- ewaller (arch linux forum moderator)
Offline
edit: skins work like they did before here
Dolby - what did you mean by this? Skins are working for you?
Offline
Never mind - problem solved. They moved the audacious config directory from ~/.audacious to ~/.local/share/audacious
Offline