hacktheworld
Active Member
Have a nice day guys!
Why can't I download the file to install Audacious 4.4.2 on Debian 12?
Why can't I download the file to install Audacious 4.4.2 on Debian 12?
Note that the versions of Audacious available in Debian stable and Ubuntu LTS releases tend to be rather out of date. Panda Jim of ubuntuhandbook.org maintains a PPA with newer versions for Ubuntu users.
Really too complicate for me, I have tried to install Audacious from the source, butIDK about pkgs.org since I don't use the site, but I will warn this: Audacious 4.4-2 is not compatible with Debian 12, even if you install deps from backports -- not all are up to date.
Also, I'll warn that installing outside your repos is a bad idea and I don't just mean security-wise, you can break stuff. This is one of many reasons why AppImages and Flatpaks/Snaps exist (though I only use AppImages).
If you must, must, must have the latest...
Grab it from Linux Portable Apps as an AppImage. Here's the build script:
(You don't have to install AM/Appman unless you want Appimages managed -- then see the main git).Database-of-pkg2appimaged-packages/audacious at main · ivan-hc/Database-of-pkg2appimaged-packages
Various AppImage packages for AM and AppMan. Contribute to ivan-hc/Database-of-pkg2appimaged-packages development by creating an account on GitHub.github.com
Just download/copy+paste the script, run it as a normal user, and it'll build the latest upstream into an Appimage. It may take a while depending on your internet. I haven't tried this particular build, but so far everything else I grab from there just plain works -- at the cost of disk space -- so it's my go-to now.
PS: You can't guarantee an AppImage 100%. They're not perfect, but they are pretty good.
dnf install audacious
Thank you,Suggest merge with thread:
Install Audacious on Linux | Snap Store
Get the latest version of Audacious for Linux - Lightweight audio playersnapcraft.io
If you're running fedora
Code:dnf install audacious
preferably
from the source,
Thank you very much and Merry Christmas!This isn't quick and simple... the first thing you need to do is install the compiler suite.
This covers most of it, you don't really need git or cvs, so you can skip that part for now.
You don't really need an IDE either, so you can skip the part about Visual Studio and Eclipse.
After all that's done, download the zip file from - https://github.com/audacious-media-player/audacious/tree/master
There is a drop-down menu near the top that has a "Download zip file" option.
Download and unzip the file, it doesn't really matter where, but usually you would do this in your home directory.
Open a command line console and cd into the audacious directory that you unzipped.
audacious/INSTALL at master · audacious-media-player/audacious
A lightweight and versatile audio player. Contribute to audacious-media-player/audacious development by creating an account on GitHub.github.com
Then you run some "make" commands.
Linux make Command with Examples - GeeksforGeeks
A Computer Science portal for geeks. It contains well written, well thought and well explained computer science and programming articles, quizzes and practice/competitive programming/company interview Questions.www.geeksforgeeks.org
Usually you run "make clean" first, to get rid of any weird junk.
Then you need to run the "./configure" command.
An Introduction to the "./configure" Command: Compiling Source Code in Linux – TecAdmin
The ./configure command is a common way to configure and prepare software source code for compilation on Linux systems. This command is typically run before the make command, which actually compiles the software. Understanding the options available with the ./configure command can give you more...tecadmin.net
There are some options associated with this, like where you want the compiled program to live.
Then, once you get all the configure options like you want them, just run "make"
This is where the actual compile happens.
Now you may get lucky, and this may compile on the first try. Or you may get some errors, and it may tell you
that you need to install some more development packages. This part is a little trial and error.
If the compile was successful, you would then do a "make install".
Depending on where you told the configure program that you wanted the binary to be installed,
you would then go to.. say.. /usr/local/bin/ for example, and then just type "./audacious"
Assuming all that works, you can add an icon to your launcher menu.
I have downloaded the files fromThis isn't quick and simple... the first thing you need to do is install the compiler suite.
This covers most of it, you don't really need git or cvs, so you can skip that part for now.
You don't really need an IDE either, so you can skip the part about Visual Studio and Eclipse.
After all that's done, download the zip file from - https://github.com/audacious-media-player/audacious/tree/master
There is a drop-down menu near the top that has a "Download zip file" option.
Download and unzip the file, it doesn't really matter where, but usually you would do this in your home directory.
Open a command line console and cd into the audacious directory that you unzipped.
audacious/INSTALL at master · audacious-media-player/audacious
A lightweight and versatile audio player. Contribute to audacious-media-player/audacious development by creating an account on GitHub.github.com
Then you run some "make" commands.
Linux make Command with Examples - GeeksforGeeks
A Computer Science portal for geeks. It contains well written, well thought and well explained computer science and programming articles, quizzes and practice/competitive programming/company interview Questions.www.geeksforgeeks.org
Usually you run "make clean" first, to get rid of any weird junk.
Then you need to run the "./configure" command.
An Introduction to the "./configure" Command: Compiling Source Code in Linux – TecAdmin
The ./configure command is a common way to configure and prepare software source code for compilation on Linux systems. This command is typically run before the make command, which actually compiles the software. Understanding the options available with the ./configure command can give you more...tecadmin.net
There are some options associated with this, like where you want the compiled program to live.
Then, once you get all the configure options like you want them, just run "make"
This is where the actual compile happens.
Now you may get lucky, and this may compile on the first try. Or you may get some errors, and it may tell you
that you need to install some more development packages. This part is a little trial and error.
If the compile was successful, you would then do a "make install".
Depending on where you told the configure program that you wanted the binary to be installed,
you would then go to.. say.. /usr/local/bin/ for example, and then just type "./audacious"
Assuming all that works, you can add an icon to your launcher menu.
Installconfigure: error: The pkg-config script could not be found or is too old.
pkg-config
:sudo apt update
sudo apt install pkg-config
Thank you,Installpkg-config
:
Code:sudo apt update sudo apt install pkg-config
Then run configure again
glib-2.0 is missing, gtk+-3.0 is missing,
sudo apt install glib2.0 gtk+3.0
Thank you very much!
Both include development packages as dependency, simply run:
Bash:sudo apt install glib2.0 gtk+3.0
If you still have missing packages, google them out, in this example I googled for:
"gtk+-3.0 dev debian" and "glib2.0 dev debian"
This is what I meant about trial and error, and adding more development packages.
Note: after a failed attempt to compile, always run "make clean" again to clear out all the failed stuff.
Then run the ./configure command again.
To be honest, I don't have any Debian installs right now, and I can't remember the names of all the packages,
so maybe someone else can step in and help with that part. But for Fedora, the packages are named...
gtk+-devel.x86_64: Development tools for GTK+ (GIMP ToolKit) applications
gtk3-devel.x86_64: Development files for GTK+
PackageKit-glib-devel.x86_64: GLib Libraries and headers for PackageKit
glib-devel.x86_64: Libraries and header files for glib development
Every Distro names their packages slightly different, but they will be similar to these.
You probably already have glib and gtk+ installed on your computer, but you don't have the
development packages for them installed. ( the header files, and things needed to compile them ).
The thing is, some of these packages sometimes require other packages. So after you install these,
it may tell you that you need to install some other packages. The other thing that can happen, is that sometimes
the development version of packages available for your specific distro, may be too old to compile newer
versions of applications.
AppImages and Snap may seem like a lot of work, but they are much easier than compiling your own.