Closed JOJ0 closed 1 year ago
Thanks for the report. These look like two different errors. The first appears to be a permissions problem and is likely the result of a recent change I made to the PKGBUILD for musicplayerplus. I was told not to use sudo
in PKGBUILD but it appears it may be needed in this case (?). The second is a missing dependency and I have not seen this before.
I will investigate both.
@JOJ0 I was unable to replicate your errors on my first try but re-examining your logs I note that at the end of the text console attempt there was an error: Read-only file system
. The failures in both attempts are occurring when attempting to write to /usr/lib/
in the graphical install and /.cargo/...
in the text install.
Does your system have a read-only root filesystem?
I will continue to look into this but wanted to confirm with you the state of the root filesystem.
Hi, thanks for looking into it. I double checked:
$ mount | grep root
/dev/mapper/manjaro-root on / type ext4 (rw,noatime)
$ df -h | grep root
/dev/mapper/manjaro-root 63G 57G 3,8G 94% /
I'm realising that /.cargo/....
is a very untypical path to write to in general. Usually no hidden dirs in /
Thanks for confirming the root filesystem is read/write. I guess that error message was misleading.
Yes, the /.cargo/...
path is weird. The PKGBUILD performs a Cargo build of blissify
and bliss-analyze
. Cargo packages are downloaded as part of those builds but they should go in $HOME/.cargo/...
. It could be another misleading error message.
I have been working on a major new release of MusicPlayerPlus in which many of the components are split out into their own separate packages. This modular approach moves much of the over-complicated prep and build out of PKGBUILD and into the mppinit
utility used to perform initial configuration of MusicPlayerPlus. It also gives users more flexibility and control over which components get installed - don't want or need Blissify, don't install it.
This revised modular architecture will address the issues you raise here. I'm pretty close to having MusicPlayerPlus version 3 ready but need to run it through test. I should have something by end of year (i'm unavailable for some of the holidays).
When packaging the Bliss binary builds for Arch I tried to follow the package guidelines at https://wiki.archlinux.org/title/Rust_package_guidelines
I'm reviewing these and leaving this note here for myself when I get time to investigate further. Note that the guidelines state that Arch repository packages are built in chroot
environments with default settings. This may be the source of the /.cargo/...
path in the log. Or, perhaps this build is not being performed in a chrooted env and thus the permissions errors.
Version 3.0.0 Release 2 may avoid this issue. See https://github.com/doctorfree/MusicPlayerPlus/releases/tag/v3.0.0r2
Hi, I just removed all the old mpplus packages and downloaded 3.0.0.r2 and installed as stated in the release notes. I'm missing the essentia_streaming_extractor stuff now. You once mentionend that it is now in an extra package, right? Where to find that package? Cheers!
Found it. This almost did the trick. Getting a signature error:
$ sudo pamac install https://github.com/doctorfree/mpplus-essentia/releases/download/v1.0.1r1/mpplus-essentia-v1.0.1r1-1-x86_64.pkg.tar.zst
Preparing...
Downloading mpplus-essentia (v1.0.1r1-1)...
Error: Failed to prepare transaction: package missing required signature
First downloading and then installing from there works fine:
$ sudo pamac install Downloads/mpplus-essentia-v1.0.1r1-1-x86_64.pkg.tar.zst
Preparing...
Resolving dependencies...
Checking inter-conflicts...
To install (1):
mpplus-essentia v1.0.1r1-1
Total installed size: 160,0 MB
Apply transaction ? [y/N] y
Checking keyring... [1/1]
Checking integrity... [1/1]
Loading packages files... [1/1]
Checking file conflicts... [1/1]
Checking available disk space... [1/1]
Installing mpplus-essentia (v1.0.1r1-1)... [1/1]
Additional info at:
- https://github.com/doctorfree/mpplus-essentia#readme
Running post-transaction hooks...
Arming ConditionNeedsUpdate... [1/2]
Refreshing PackageKit... [2/2]
Transaction successfully finished.
I closed this one since the initially reported error is fixed. Probably a new one should be openend for the missing dependency/optional dependdncy to mpplus-essentia?
Yes, a new issue regarding mpplus-essentia installation may be necessary. It is supposed to get installed when mppinit
is run after completing the MusicPlayerPlus
package install. I will do some testing today to see why that didn't happen.
Did mpcplus
get installed?
I was initially unable to replicate the mpplus-essentia failure to install you report here. The mpplus-essentia
package was successfully installed during mppinit
after installing the MusicPlayerPlus package. When you run mppinit
you should see something like the following:
Initializing MusicPlayerPlus, please wait ...
Installing mpcplus ...
Installing mpplus-essentia ...
Installing mpplus-bliss ...
Please open an issue if this continues to be a problem or if you have additional details of the mppinit
run that might be helpful.
I will continue to investigate and I did find other things that need to be corrected so there will be a new package in a few days.
Ok, I was able to replicate the mpplus-essentia install error. It seems to be a missing signature causing the install to fail. I was able to replicate the problem by rolling my Arch VM back to an initial state before testing.
I will open an issue and begin work on this tomorrow. Thanks for bringing this to my attention, I would not have encountered this on my own. Feel free to school me on how to distribute signed Arch packages.
@JOJ0 the mpplus-essentia installation on Arch has been fixed in MusicPlayerPlus version 3.0.1 release 1 along with your PR providing support for Manjaro and other Arch-like platforms.
Hi! sorry for being brief and unspecific. I just updated my Manjaro and got this compile error. I'm not sure if it's rather my own fault, than having anything to do with the arch package from AUR. I'm not even sure if that's provided by you or someone else. So sorry again! Just wanted to quickly report, I might find time later to move on with investigations. I saved the rest of the log in a textfile locally, this is just the end of what pamac threw on a system upgrade. HTH and speak soon, all the best
Above's error was while using pamac graphical interface.
I tried again on text console,
but that threw a different error: