In FreeBSD10 receiving the following error.

File /usr/local/lib/python2.7/gettext.py line 469, in translation raise IOError(ENOENT, 'No Translation file found for domain', domain) IOError: [Error 2] No Translation file found for domain: u'metamorphose2'

On Freebsd when running metamorphose2.py

Traceback (most recent call last): File "/usr/share/metamorphose2/metamorphose2.py", line 53, in import MainWindow File "/usr/share/metamorphose2/MainWindow/init.py", line 39, in import sorting File "/usr/share/metamorphose2/sorting/init.py", line 25, in from exif import EXIF ImportError: cannot import name EXIF

$ pkg info|grep exif py27-exif-0.9_1 Python library to extract EXIF metadata from JPEG and TIFF image files.

$ ls src/exif/ $

Looks like exif did not get pulled with git. Will try again when internet is available. But a different exif module is installed with pkg. Labelled as bug for now pending further testing.

Following https://github.com/NixOS/nixpkgs/pull/17171, I decided to clean up the Makefile upstream.

Summary:

1. make PREFIX=/foo/bar should now work for any directory so long as the install path is absolute (NOT: make PREFIX= ../../out). Default is still /usr.
2. messages/Makefile replaces messages/update_langs.sh for all purposes.
3. app.py's hardcoded path is adjusted using the PREFIX.
4. The metamorphose2 shell script path is adjusted using the PREFIX.
5. metamorphose2.desktop path is adjusted using the PREFIX.

Metamorphose2 is not building due to some missing .html files. According to the Makefile it's just a doc file. Commenting out line 108 of the Makefile bypasses the problem. Tested on Mac OS X Yosemite 10.10.3, Python 2.7.6, wxPython 3.0.2 cocoa.

Running latest git snapshot on arch linux x64. As far as I know, PIL was replaced by pillow (and there is no PIL package in the repos or the AUR anymore), so I have installed python2-pillow from the official repositories:

community/python2-pillow 2.7.0-2 [installed]
    Python Imaging Library (PIL) fork. Python2 version.

Yet I'm still getting a PIL not found error message at startup. What could be wrong here?

Removed the FBSD related files as they don't seem to be used by anyone and I'm no longer running the OS to test on. Improved cross shell compatibility since some distros are no longer using Bash nor do they necessarily install things in the same locations.

I realise this project has been dormant for some time but I have been a long time user of metamorphose2, and many thanks to ianare for developing it and looking after it while he had the time.

When I switched to Debian Bullseye a year ago, I made the changes needed to run it with Python3.9 and wxPython 4.1 and I have finally found my way round github to share the outcome.

You can find this version on a fork/branch here.

The are a lot of changes related to the new Python/wxPython, but it doesn't introduce any new functionality or fix any bugs. I haven't the knowledge to create new deb packages, but you can find the simple steps I took to get it to run on clean Linux and Windows systems in the issues, and the instructions in the readme have been updated.

Most of my use/testing is on Debian Bullseye using Python 3.9 and wxPython4.1.1, but I expect it will work with any Python 3 and wxPython4. I have run it on Windows 10, as a quick check. Sorry - I don't have access to a Mac. I am not sure how this will co-exist with earlier versions, so setting up for this new version will potentially break the previous one.

I hope this may help those who have used metamorphose2 in the past and found it as useful as I have.

Had to reinstall a machine with UM 18.04.5 from its .iso and, since then, editing rules is largely compromised: when in the Renamer tab, I can click within each box and position the cursor, but keypresses are no longer detected (can't move with arrow keys, can't add or delete characters). Weirder than that, I can define new rules (and - as long as I stay within the new rule - keyboard works as it should; but as soon as I exit the rule, and return after having clicked elsewhere or having added another one, that same new rule cannot be edited anymore).

However, rename operations, as well as deleting existing rules and other mouse-driven actions, work as intended.

Presently on metamorphose2_0.9.0.beta-1sav0_all.deb, installed via Gdebi (obviously, no missing dependencies); fun thing is that until the reinstall (when I already was on UM 18.04.5, but coming from an upgrade path from 18.04.2) functioning was nominal.

Launched the program with -d parameter, no log whatsoever (neither in ~/.metamorphose, nor in /var/log); FWIW, permissions on all .cfg files are standard 644, file ownership is $USER, and iBus/keyboard configurations have no customizations.

Any suggestion on how to overcome this weirdness is greatly appreciated.

Simply a workaround to ensure the call to locale.getlocale returns a valid locale. Not sure if this the best solution (not a Python programmer -- yet!) but it works. Have used this patch fine for 2 years now on my own Ubuntu 16.04 based system.

tl;dr -- Metamorphose2 PPA for Ubuntu

This is not an issue, rather a log in the record here on what appears to be unmaintained software (especially given various other issues about installing). Finally got around to creating a new PPA with a build that patches #16 (credit to Alin Andrei for publishing a version of the software with some needed patches already applied).

So for all who are trying to get Metamorphose2 working on a Ubuntu-based system, check the PPA for a Xenial build that may well work fine with newer series too (perhaps someone can report on that here, as and when they get to trying the new build on a series newer than Xenial). Soon a forked Github copy of the program, that will have all the patches already applied.

I am using version 0.9.0 of Metamorphose 2 on Ubuntu 18.04.2. I am attempting to rename the cover art jpg file for a series of albums. I am using the replace function, what to replace "cover" and replace with "folder". This appears to be causing some sort of glitch as the preview gives a warning for all matches showing original name of "cover.jpg" and new name of ".jpg", basically removing the file name. If I use some other text in place of "folder", like "somename", it works just fine.