Hide Forgot
Description of problem: Previous versions of hylafax RPM's (not from Fedora, but from the vendor) symlinked /var/spool/hylafax/bin/ps2fax to ps2fax.gs. When I uninstalled the old versions and put in the Fedora hylafax+ rpm, sending faxes via the Hylafax Windows printer driver (that previously worked great) would fail with "could not find script" errors. I determined it was because my config's setup.cache had this line: DPSRIP='/var/spool/hylafax/bin/ps2fax' when that file does not exist in Fedora's RPM. Making a symlink from ps2fax -> ps2fax.gs (which is in the RPM) solves the problem. I realize that the problem could be caused by my old (but previously working) setup.cache, but I wiped it and tried making a new one and the new setup scripts look for ps2fax as well. Is there a reason old hylafax's included this symlink but Fedora's does not? The same problem may also apply to tiff2fax. Version-Release number of selected component (if applicable): hylafax+-5.5.4-1.fc19.i686 How reproducible: always Steps to Reproduce: 1. Be a previous user of Hylafax 2. Install Fedora's new Hylafax rpm 3. Try an action (printing from Windows client) that acts on a ps file. Actual results: Error, script not found, fax is not sent. Expected results: fax is converted and sent Additional info:
It would seem that your old RPM owned the symlink when it shouldn't have (or at least that it removed them at uninstall). The ps2fax and pdf2fax symlinks are created by faxsetup after the installation and really shouldn't be owned by the RPM package as they amount to configuration. I suppose that one could argue that the symlinks should be owned by the package since pdf2fax.gs and ps2fax.gs are, but that complicates things seemingly without need. The symlinks would have been recreated (along with other configuration bits) automatically rerunning faxsetup.
I somewhat disagree. Let's say you've already setup hylafax on an existing system, or another system, and install the rpm on a new system. Then instead of running faxsetup, you simply copy over the config files from your previous setup. This is essentially what I was doing. In that case, those symlinks will still be missing, and hylfax will fail in a strange way without any useful debug info (hence the difficulty I had in finding the workaround). I do agree, it's a bit of a weird case, but not all that weird, considering many people do this all the time for myriad other daemons. Also, it is kind of unprecedented (and odd) for a daemon's rpm to be missing an required file or link in a "bin" dir, and having a setup script create it. Granted, this is more a hylafax problem than a fedora packaging problem, but in this case we could make sure no one gets bit by this by simply including the symlinks in the rpm. Lastly, I'm not sure if the setup script can result in any other state than the exact symlinks I outlined above? Can they point to different binaries/scripts? Would they ever on a normal Fedora system? It seems to me the setup script is doing what ./configure should be doing before compile time, which would hardcode these paths into the binaries in a Fedora-specific way. Again, that points to an upstream (if any exists) tweak/bug solution. Just some thoughts. In any case, closing is fine, the bugzilla entry will sit here demonstrating my workaround for any future victim of this problem.