Can't install any ISO mounting utility

I have some windows-based software which can only be installed (under Wine) by first mounting its ISO file onto a separate drive. This used to be child’s play under Windows as there are so many good free utilities for ISO mounting, but apparently not so under Linux…

I found several utilities that should do this job (e.g. open-fuse-iso and acetone-iso). But, whenever I try to install these utlities on my laptop (Manjaro Xfce), I get this error:

Building mounter2-git...
==> Making package: mounter2-git f254a261.4.2-2 (Mon 17 Jan 2022 07:47:58 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
==> Removing existing $srcdir/ directory...
==> Extracting sources...
==> Starting pkgver()...
/var/tmp/pamac-build-blueflame5/mounter2-git/PKGBUILD: line 18: cd: /var/tmp/pamac-build-blueflame5/mounter2-git/src/mounter2: No such file or directory
==> ERROR: A failure occurred in pkgver().
    Aborting...

So it seems that “mounter2” or “mounter2-git” needs to be installed for pretty much any application that promises to mount ISO files, but the installation of this “mounter2-git” thing always fails on my system without much of an explanation as to why. I tried both Official releases and those on AUR, and they all fail with this same error message.

I updated the system recently via Pamac, but that apparently didn’t solve this issue.

Does someone have any idea how can I fix this issue and hopefully install some graphical ISO mounting utility?

Nothing requires mounter2-git, why are you attempting to install it? The AUR package has not been touched since 2015 and there hasn’t been an upstream release since 2013.

Did you mean acetoneiso2? :thinking:

It’s not really me who is trying to install mounter2-git :slight_smile:

I believe that it’s “open-fuse-iso” that wants to install that package, over and over again.

Yes you’re right about acetone, it’s “acetoneiso2”, and apparently it has been installed onto my system even though it complained about that missing package. I will check now to see if it works correctly. :slight_smile:

Both open-fuse-iso and acetoneiso2 use fuseiso as a backend. acetoneiso2 is in the Arch community repo, it does not depend on any AUR package let alone mounter2-git.

Please post the output of the package transaction that is attempting to pull in mounter2-git.

you mount an .iso file like this:
sudo mount -o loop /path/to/your.iso /path/to/mountpoint

Doesn’t this approach work for you?
The mountpoint could be any directory … which is convenient to use to access it via wine.

Or do you actually require a graphical utility for this probably one shot event?

1 Like

Here’s the complete log of my today’s attempts to install several ISO-Mounting applications via Pamac.

If memory serves me well, the first app I tried to install was “fuseiso”. I think I tried to install “mounter2-git” after that (from Official repository). I also tried acetoneiso2. Fuseiso and acetoneiso2 seem to be installed now, although I got error messages about the problem with installing “mounter2-git” on both occasions. I suppose it was Pamac that was trying to install mounter2-git over and over again.

Please see the log.

gCDEmu is in the AUR. It works fine. I recently switched from acetoneiso2

It appears you’re using Add/Remove Software (Pamac). The log does not tell us what you selected to install. From what you said, you were trying to install open-fuse-iso, but again mounter2-git is completely unrelated as nothing depends on it.

Try with another AUR helper like yay:

pamac install yay
yay -S open-fuse-iso

Ok, I installed yay and when I type the command for installing open-fuse-iso, this is what I get:

yay -S open-fuse-iso
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  open-fuse-iso-1.1-1

  1 open-fuse-iso                            (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 

Which option should I choose?

Just press Enter, None is default.

Press 1 or just enter

What is Clean Build though?

Yay keeps a cache of each package it builds either in $XDG__CACHE_HOME/yay or $HOME/.cache/yay (if $XDG_CACHE_HOME is unset). Cleanbuilding will remove all cached files from the last build before it downloads and builds the package.

The cache is generally useful since it speeds up build times.

Ok, I got acetoneiso2 to work as it should. I am able to mount an ISO file now.
I can also try mounting this ISO file via terminal as Nachlese suggested (thanks).

But for the sake of this thread, here’s the output of the yay log:

yay -S open-fuse-iso
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1]  open-fuse-iso-1.1-1

  1 open-fuse-iso                            (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: PKGBUILD up to date, Skipping (1/0): open-fuse-iso
  1 open-fuse-iso                            (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: (1/1) Parsing SRCINFO: open-fuse-iso
==> Making package: open-fuse-iso 1.1-1 (Mon 17 Jan 2022 08:49:09 PM CET)
==> Retrieving sources...
  -> Cloning open-fuse-iso git repo...
Cloning into bare repository '/home/blueflame5/.cache/yay/open-fuse-iso/open-fuse-iso'...
remote: Enumerating objects: 35, done.
remote: Total 35 (delta 0), reused 0 (delta 0), pack-reused 35
Receiving objects: 100% (35/35), 10.81 KiB | 138.00 KiB/s, done.
Resolving deltas: 100% (14/14), done.
==> Validating source files with md5sums...
    open-fuse-iso ... Skipped
==> Making package: open-fuse-iso 1.1-1 (Mon 17 Jan 2022 08:49:12 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating open-fuse-iso git repo...
Fetching origin
==> Validating source files with md5sums...
    open-fuse-iso ... Skipped
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Creating working copy of open-fuse-iso git repo...
Cloning into 'open-fuse-iso'...
done.
==> Sources are ready.
==> Making package: open-fuse-iso 1.1-1 (Mon 17 Jan 2022 08:49:16 PM CET)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "open-fuse-iso"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Adding install file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: open-fuse-iso 1.1-1 (Mon 17 Jan 2022 08:50:03 PM CET)
==> Cleaning up...
 -> Found git repo: github.com/alexandruianu/open-fuse-iso
 -> /var/lib/pacman/db.lck is present.
 -> There may be another Pacman instance running. Waiting...
[sudo] password for blueflame5: 
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) open-fuse-iso-1.1-1

Total Installed Size:  0.00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                     [######################] 100%
(1/1) checking package integrity                   [######################] 100%
(1/1) loading package files                        [######################] 100%
(1/1) checking for file conflicts                  [######################] 100%
(1/1) checking available disk space                [######################] 100%
:: Processing package changes...
(1/1) installing open-fuse-iso                     [######################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the desktop file MIME type cache...
[blueflame5@blueflame5-inspiron3521 ~]$ 

You likely can not only try, but also … just do it.
I was just curious why one would go to such lengths to install a tool
that was not even needed to do the job it was going to be used for …

Sorry for the interference!