There are "mgetty" and "faxonly" use flags. They are not processed properly. Look: If I set "mgetty -faxonly" - net-dialup/mgetty is emerged automagically. And that is of course correct. If I set "-mgetty faxonly" - net-dialup/mgetty is not emerged. And that is also correct. If I set both flags ("mgetty faxonly") - emerging fails. That is correct too! But if I set none of above mentioned use flags ("-mgetty -faxonly"), hylafax still depends on net-dialup/mgetty! See: ~ # USE=-faxonly emerge -pv hylafax These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-dialup/mgetty-1.1.35-r2 USE="-doc -fidonet" 1,000 kB [ebuild R ] net-misc/hylafax-4.3.0 USE="jbig pam -faxonly* -html -mgetty" 0 kB Total: 2 packages (1 new, 1 reinstall), Size of downloads: 1,000 kB Solution: Remove depentency "!faxonly? ( net-dialup/mgetty )". It is not necessary for hylafax to work! Reproducible: Always Steps to Reproduce:
*** Bug 183991 has been marked as a duplicate of this bug. ***
This is even more ugly now that the latest version of mgetty blocks hylafax. emerge -pv hylafax These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-dialup/mgetty-1.1.36-r1 USE="doc fax -fidonet" 1,022 kB [ebuild N ] app-arch/sharutils-4.6.3 USE="doc nls" 0 kB [ebuild N ] net-mail/metamail-2.7.45.3-r1 0 kB [ebuild N ] net-misc/hylafax-4.3.0 USE="html jbig pam -faxonly -mgetty" 0 kB [blocks B ] net-misc/hylafax (is blocking net-dialup/mgetty-1.1.36-r1)
Fixed in the latest testing versions of Hylafax, with minor cleanup in mgetty. Test away...
(In reply to comment #3) > Fixed in the latest testing versions of Hylafax, with minor cleanup in mgetty. > Test away... When you say "testing versions of Hylafax", I presume you mean ones that are not in Portage, as all the versions in Portage up to 4.4.4 (i.e. including unstable) fail with this blocking on mgetty.
I guess I'm not sure what you're talking about; on a fresh install I get this with the mgetty USE flag: emerge -pv hylafax These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-dialup/mgetty-1.1.36-r2 USE="-doc -fax -fidonet" 0 kB [ebuild N ] net-mail/metamail-2.7.45.3-r1 0 kB [ebuild N ] net-misc/hylafax-4.4.4 USE="jbig mgetty pam -html" 0 kB Total: 3 packages (3 new), Size of downloads: 0 kB and this without it: USE="-mgetty" emerge -pv hylafax These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] net-mail/metamail-2.7.45.3-r1 0 kB [ebuild N ] net-misc/hylafax-4.4.4 USE="jbig pam -html -mgetty" 0 kB Total: 2 packages (2 new), Size of downloads: 0 kB Is it different on your system?
(In reply to comment #5) > I guess I'm not sure what you're talking about; on a fresh install I get this > with the mgetty USE flag: The key proved to be the fax/-fax USE flag on mgetty: When used as -fax, the overall installation works; when used as fax, mgetty blocks Hylafax.
