I have net-dialup/capisuite-0.4.5-r6 installed which was working fine. Recently sending faxes stopped working: result was 349f,3319 I will attach a verbose output of the session. I ask some experienced people if they see things which may lead into such an error. What I did recently was to add a webserver to the machine and some packages therefore where updated also which may interfere with capisuite. sfftobmp and tiff where update also ghostscript-gpl from app-text/ghostscript-gpl-8.63 to app-text/ghostscript-gpl-8.71-r1. Can this yield into a coding error? In spite of that I can view the generated sff files (ghostscript does this) after converting them with "sfftobmp -j ..." fine, creating bmp from the generated sff files gives garbage in the image viewer though. May be someone experienced knows a common problem which may cause this. Please Help!
Created attachment 240561 [details] detailed /var/log/capisuite.log output yielding into coding error
I am not sure if this or any other bugs that will appear will ever be fixed because looks like this is unmaintained for ages as I see in its homepage :/
Some our patches(among with others) were merged upstream[1] I think we should probably add snapshot ebuild and resend this bug upstream [1] - https://github.com/larsimmisch/capisuite
I'm using capisuite as answering machine only, and it still works very well. I'm even about to install it onto a new Gentoo server. I know it's pretty old, and some functions may not work well any more, but I do like the answering machine with different announcements for different phone extensions and mailing the audio file to my e-mail account - it's very powerful and flexible, even today. On the other hand, I do understand that you want a "clean and working" portage tree and are forced to remove it. So how can I... - ensure that it will remain working on my servers? (I guess, existing installations will just remain unchanged?) - perhaps install it onto another server in the future? - get rid of those "The following installed packages are masked" message (and, later, probably, "package not found") at every "emerge -uv @world"?
You can try to copy existing ebuilds to a local portage overlay (usually at /usr/local/portage) and keep ebuilds there for the future
removed
