Description:

On running pacman -Syu with nginx-mainline installed, I get a complaint about not being able to resolve a dependency on mailcap. Some searching reveals that this is because mailcap is in the testing repository. Given the "here be dragons" warnings surrounding [testing], it doesn't seem like enabling that repository should be necessary to be able to use packages in [community].

Digging through the history of the nginx-mainline package, two commits stand out: one adding the dependency on mailcap, the other moving the affected version of the package from [community-testing] to [community], the second being the most recent commit, at less than an hour old.

commit adding mailcap dependency: https://git.archlinux.org/svntogit/community.git/commit/?h=packages/nginx-mainline&id=a5771a731499d227c5eb75f8caa4f98c6c064aa4
commit db-moving from community-testing to community: https://git.archlinux.org/svntogit/community.git/commit/?h=packages/nginx-mainline&id=158a3e50f036779e657f3ca537b7de8404332e83

Package version: 1.13.7-2
Log, prompts edited for GMT and stripped username@hostname. current date 2017-11-30:
[13:15 ~]$ sudo pacman -Syu
:: Synchronising package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
:: Replace gtk3-print-backends with extra/gtk3? [Y/n]
resolving dependencies...
warning: cannot resolve "mailcap", a dependency of "nginx-mainline"
:: The following package cannot be upgraded due to unresolvable dependencies:
nginx-mainline

:: Do you want to skip the above package for this upgrade? [y/N]
error: failed to prepare transaction (could not satisfy dependencies)
:: nginx-mainline: requires mailcap
[13:15 ~]$



Steps to reproduce:
1. Do not have the testing repository enabled, nor mailcap dependency satisfied through some other means.
2. Have nginx-mainline installed.
3. Run pacman -Syu
Alternatively, untried:
2. Don't have nginx-mainline installed
3. run pacman -Syu
4. run pacman -S nginx-mainline