Package Details: mimeo 2019.7-2

Git Clone URL: (read-only, click to copy)
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: 132
Popularity: 0.45
First Submitted: 2009-12-16 02:54
Last Updated: 2019-11-19 01:13

Latest Comments

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

ttoirrah commented on 2019-11-28 12:59 Status "It's not just you! is down." Hoping this is temporary...

Fandekasp commented on 2019-11-19 00:12

@Xyne indeed, sorry about that. I thought I had tried rebuilding the package, but I was wrong. Rebuilding the package fixed it, thanks for the quick support!

Xyne commented on 2019-11-18 23:55

@Fandekasp The AUR only provides PKGBUILDs, not built packages. It's up to the user to rebuild them when necessary. The PKGBUILD itself is not out-of-date. You just need to run makepkg again.

Nevertheless, I may bump the pkgrel when I rebuild the packages for my repo.

Fandekasp commented on 2019-11-18 00:44

Not sure if I should have not flagged the package out-of-date, but it's currently unusable since upgrading the system python from 3.7 to 3.8

$ mimeo /usr/bin/python3: No module named Mimeo

As per this comment: We need to rebuild mimeo against Python 3.8

ReekyMarko commented on 2019-11-07 09:08

Is there a completion file for zsh available?

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?