Summary: | dev-ruby/maxitest-1.5.4 : file collision with net-mail/uw-mailutils-2007f:0::gentoo | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | net-mail+disabled |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-ruby:maxitest-1.5.4:20160102-203435.log
emerge-history.txt |
Description
Toralf Förster
![]() Created attachment 421676 [details]
dev-ruby:maxitest-1.5.4:20160102-203435.log
Created attachment 421678 [details]
emerge-history.txt
I had a look at uw-mailutils and I'm wondering if mtest should be installed by it at all. Quoting from the FAQ: However, the mtest program is only a demonstration program, a model of a very basic application program using c-client. It is not something that you would install, much less run in any security-sensitive context. mtest has numerous other shortcuts that you wouldn't want to do in a real application program. mtest only has two legitimate uses. It's a useful testbed for me when debugging new versions of c-client, and it's useful as a model for someone writing a simple c-client application to see how the various calls work. So my suggested resolution for this bug is for net-mail/uw-mailutils not to install the mtest binary. |