Is the project abandoned? I cannot install it on Ubuntu 16.04!

[cablop]

It is too hard to install it on Ubuntu 16.04.
Is this project abandoned?

[coevolving]

I found a procedure described at http://www.noobslab.com/2017/08/these-rename-utilities-can-help-you.html , and it worked with Kubuntu 17.10.

I ran across a dependency issue, so python-exif should be installed first.

$ sudo dpkg -i metamorphose2.deb
Selecting previously unselected package metamorphose2.
(Reading database ... 465936 files and directories currently installed.)
Preparing to unpack metamorphose2.deb ...
Unpacking metamorphose2 (0.8.4+git20160722-1~webupd8~xenial4) ...
dpkg: dependency problems prevent configuration of metamorphose2:
 metamorphose2 depends on python-exif (>= 2.1.1); however:
  Package python-exif is not installed.

dpkg: error processing package metamorphose2 (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Errors were encountered while processing:
 metamorphose2
$ sudo apt-get install python-exif

Then, the directed terminal commands worked:

wget -O metamorphose2.deb https://goo.gl/eSSDMz
sudo dpkg -i metamorphose2.deb
sudo apt-get -f install

This worked after I had tried to previously install using gdebi on the download.

$ sudo gdebi metamorphose2_0.8.2-1_all.deb
[sudo] password: 
Reading package lists... Done
Building dependency tree        
Reading state information... Done
Reading state information... Done
This package is uninstallable
Dependency is not satisfiable: python-wxgtk2.8 (>= 2.8)

I've gotten used to using Metamorphose for a long time, so there's less cognitive load if I don't switch!

[coevolving]

Unfortunately, while renaming files with specified letters or numbers works, specifying Exif results in a spinning icon that doesn't stop. I've taken to using Thunar Bulk Renamer, instead. http://www.webupd8.org/2016/03/quickly-batch-rename-files-in-linux.html

[xpelican]

In respect to the other question, I sure hope this project isn't abandoned - and if it is, it'd be a shame if none of us try to keep it going - IMO Metamorphose is the quintessential file renamer out there - I was working on another program that was supposed to work exactly like it - but Metamorphose is so much better. I've looked at all the other batch renamers out there, and this is certainly the best.

GUI support, terminal support, multiplatform, does everything you'd want... Simply perfect.

I'd be more than willing to help out here and there if other people are willing to keep this project going. I'm afraid I just don't have the expertise to pull it off on my own, but this is a great program. Would be a shame to see it go to waste.

[artmg]

Theoretically it would not be too hard to set up a Launchpad auto-build, that creates a PPA for you to install from. Once set up It takes minimal effort every 6 months to include new Ubuntu versions. Get in touch if you'd like to know how, and I can guide you. However my main OS for now is Mac, so I would not get actively involved myself.

[savoury1]

@artmg if you are still up for guiding someone on a Launchpad auto-build process then I am certainly very interested. Having been creating various deb packages for personal use in the past year or so (including one for Metamorphose2) I have several times considered starting a Launchpad PPA for certain projects such as this one.

It would be great to have a properly working Metamorphose2 available for Ubuntu users as I do agree that this is the best file renamer available. See #16 (comment) for details of a single line code patch that fixes #16 such that I have been able to use Metamorphose2 without any glitches on a Ubuntu 16.04 LTS based system for the past year.

So it's time to get this fix and a new build of Metamorphose2 available for other Ubuntu users, as the build in the nilarimogard PPA at https://launchpad.net/~nilarimogard/+archive/ubuntu/test/+build/11919363 (with this PPA being referenced in numerous blog articles describing how to install Metamorphose2) still has the #16 bug. And I'm willing to do the work on a new PPA, so any guidelines you can provide would be great!

[careca1970]

Hi there!
Yes, I follow this project since long time.
Former developer does not maintain it anymore. Nevertheless he wins my very much Thanks for his work!

Now, if any project follower would be able to retake it (or ask someone who would do it to), and update everything to comply to up to date OS's language-/GUI-environment that would be really great!

Unfortunately I am NO programmer. I can even understand code, and program any small things, but I can not take this task.

Let's hope anyone wants to help all of us, and overtake it!

[artmg]

To anyone interested in keeping metamorphose2 alive...

Hi @savoury1 @xpelican @careca1970 and anyone else interested in keeping this project alive. There are quite a number of things you can do, and not all of them involve programming.

It starts with a New Fork

However, the most fundamental thing is that someone creates a fork in github. Preferably someone with some vague understanding of python, at least enough of an understanding to make this code actually run. It's quite straightforward to create a fork here. Once you have forked it then you have magically given yourself rights to add new code, unlocking the potential to keep the project going.

Experience with git source code management is useful, but if you have no experience yet then trying it out is one way to get experience fast! If you want later, you can grant other coders the right to accept pull requests, so you don't have to be on your own.

However, someone needs to be brave enough to start. Go ahead, click that Fork button!

FYI the original project was licensed under GPL3, so that would be an option for the new license to use going forward.

include any known fixes

Have a look at the issues on this project. Can you add those fixes into your new fork? If you understand git branches, you can include fixes from another fork. Have a look at this article explaining how to create a branch from another upstream fork. If you have a look at the Insight / Network of this repo you will find a suitable branch from uggla which purports to fix issue #12 - try including that code yourself.

Even if you can't code to save your live, you can test what someone else has tried to fix, so help is always welcome.

contact people who might be interested

This is another good task for non-programmers who want to help. One side of it is contacting the original dev, and that it the first recommendation in both these answers:

1. https://softwareengineering.stackexchange.com/a/273176
2. https://softwareengineering.stackexchange.com/a/130882

I have seen recent contributions from @ianare on other projects, so he might well respond with advice or suggestions. If you make PRs (see below) that's another way to get the dev's attention.

As well as contacting the dev, you can contact others. If you fix issues in the original repo, you can mention your fork in the conversation about those issues, and people will start to come to your new fork instead. Get in touch with others who have made contributions in the past. If you make the package work again properly you can even comment on pages that speak about it, or complain about it not working anymore. This all brings attention to the fresh work you are putting into it.

Update the documentation

So another person who is NOT a developer could fork the new fork, and at least contribute to the documentation in the README. Or they could begin to flesh out explanations in the Wiki. Github is rich with ways for others to get involved, so as soon as a dev is keen enough to contribute to a new fork, then people can start helping out.

create new auto builds

All the clever stuff for debian packages is already in the source, so once a dev is ready to start autobuilds with launchpad, I can make suggestions of what to set up in there to make it work.

keep making Pull Requests

if you have made useful contributions to the code, then making Pull Requests (PR) is an easy way for the original developer to help your work reach a wider audience. If they decide they are happy for you to take over the project instead, then a later PR could mention your new fork in the README. PRs also help people to find the new contributions you are putting out there.

volunteer please step forward

So, who is up for leading a new fork of this well-respected code? Hit the Fork button and see how many people follow you! Drop an link in a comment here.

[savoury1]

See #26 for a patched PPA build (at last). Soon a forked Github copy also, with patches pre-applied!

[artmg]

Ciao @SalvaFiorenza8

Great that you might be interested in being involved with this project. If you want to fork and work on it you should know that maintainer of this original fork can n longer dedicate his time to it, but @savoury1 has forked it at:

https://github.com/savoury1/metamorphose2

and has added some recent commits since summertime, as well as creating an Ubuntu PPA. If you want to contribute to metamorphose2 then you might get more response if you fork from that newer repo linked above. Thanks

[SalvaFiorenza8]

Hi @artmg yeah I read @savoury1 comment after adding mine, because of that I deleted my comment, I'm still interested in helping to maintain of the project, especially since python 2.7 will be deprecated next month and I'd like to have this tool around in the future. I'll fork his repo then, greetings.

[timinaust]

It would be sad to see this die - it has been a great tool for me. So, there is a fork here with a branch that works with the latest Python 3.9 and WXPython 4.1 that I have been using for the last 8 months on Debian Bullseye. I don't have much experience with packaging, github etc so only rely on the manual install instructions.