Package Details: mimeo 2019.7-1

Git Clone URL: (read-only)
Package Base: mimeo
Description: Open files by MIME-type or file name using regular expressions.
Upstream URL:
Keywords: utilities
Licenses: GPL
Submitter: Xyne
Maintainer: Xyne
Last Packager: Xyne
Votes: 128
Popularity: 1.079885
First Submitted: 2009-12-16 02:54
Last Updated: 2019-07-17 21:42

Latest Comments

1 2 3 4 5 6 ... Next › Last »

lesiserfg commented on 2019-05-24 05:52

Can you use /usr/bin/python3 instead of python3 cause it makes impossible to use mimeo inside of a virtualenvironment, please?

Xyne commented on 2018-05-30 15:49


What's the output of the following commands?

pacman -Qi mimeo
pacman -Ql mimeo

Ataraxy commented on 2018-05-20 07:47

At install time I see:

running install_egg_info
Writing /home/ravi/.cache/pacaur/mimeo/pkg/mimeo/usr/lib/python3.6/site-packages/Mimeo-2017.

But something seems to be awry:

$ type mimeo
mimeo is hashed (/usr/bin/mimeo)
$ mimeo
/home/ravi/.local/share/miniconda3/bin/python3: No module named Mimeo

Xyne commented on 2017-09-09 15:20

Downloaded source files that you build and install should be verified to minimize security risks. Most AUR packages rely on checksums (and most of those are checksums generated by the maintainer when the package is updated, not provided by upstream). PGP signatures provide better security than checksums which is why support was added with the recent updates to the AUR website. Most packages still don't use them yet, either because upstream doesn't provide signed sources or because the maintainer simply hasn't updated to use them.

As for why you have to install the key instead of letting makepkg do it automatically, it provides a little more security. If the file had been intentionally corrupted, then it would be easy to sign it with the attacker's key and makepkg wouldn't even notice. As it is now, users who want security can carefully verify public keys before trusting them (or just run a simple command to import them without caring).

Btw, my key is in the Arch Linux keyring. Feel free to suggest on the pacman-dev list that makepkg first check with pacman-key before using the user's keyring ;)

Anonymous comment on 2017-09-09 09:50

==> Verifying source file signatures with gpg...
mimeo-2017.6.6.tar.xz ... FAILED (unknown public key 1D1F0DC78F173680)
==> ERROR: One or more PGP signatures could not be verified!
==> ERROR: Makepkg was unable to build mimeo.

sorry for being a noob but why does every other AUR-package install fine and for this one I have to go to the trouble of adding keys?

JP-Ellis commented on 2017-05-30 07:39

@Xyne Sorry I didn't see you replied. Python should always be installed to /usr/bin/python3 (at least on Arch Linux), so there is no harm in hard-coding this. This would also solve the issue encountered by @cswoodruff.

Virtual environments are actually fairly common, especially for people who need to have multiple versions of Python installed (or Python libraries). You probably haven't had people raise the issue because the fix is so simple... but I still think it would be better if mimeo ensured that the system installation of Python is used every time as opposed to explicitly using "whichever bash prefers" even if it isn't the one where the Mimeo library is installed.

Anonymous comment on 2017-03-10 17:44

It would be good if the PKGBUILD could be changed so that it uses an explicit call to python3. This ensures that python3 is always used during the build process for people like me that have a link in their path overriding the default python (/home/user/bin/python --> /usr/bin/python2).

Xyne commented on 2017-01-29 12:41

Looks like a temporary key server error. Try a different server or try again later.

toketin commented on 2017-01-22 21:07

$ gpg --recv-keys --keyserver hkp:// 1D1F0DC78F173680
gpg: ricezione dal keyserver fallita: Server indicated a failure

NuSkool commented on 2016-10-20 15:49

gpg --recv-keys --keyserver hkp:// 1D1F0DC78F173680