This is a more current release of hylafax. Not to be confused with the HylaFAX from hylafax.org. This one is from sourceforge, it's more up to date and the PDF attachments work. A small note, I had to emerge setserial and setup the serial ports to get faxgetty to connect to the serial modem. On top of that you can put faxgetty in the inittab to get it respawned. Though I made my own init file for it. Please review the ebuild and init file and make any appropriate changes that need to be done. Reproducible: Always
Created attachment 111704 [details] ebuild for v5.1.0 I am not sure if I did the SRC_URI variable correctly. This seems to be the url sourceforge puts for download.
Created attachment 111705 [details] sample faxgetty init script This is an init script I wrote for faxgetty. The serial device is hardcoded because I am not a big scripter so I don't know how to do anything more advanced than this. If someone can figure out how to make it get the ttySx from /var/spool/fax/FIFO.ttySx file or have this run from within the hylafax init script. this depends on killproc
(In reply to comment #1) > I am not sure if I did the SRC_URI variable correctly. This seems to be the url > sourceforge puts for download. > No, it should be mirror://sourceforge/${PN}/${P}.tar.gz" or whatever similar.
(In reply to comment #0) > This is a more current release of hylafax. Not to be confused with the HylaFAX > from hylafax.org. This one is from sourceforge, it's more up to date and the > PDF attachments work. George, To be more precise, HylaFAX+ is a fork of HylaFAX. There's a lot of shared code between the efforts but people should understand that there are incompatibilities between the projects already, and there will be more as the codebases diverge. The reason the PDF MIMEConverters are not yet available in the 4.3.2 release of a couple of weeks ago and won't be available in our 4.3.3 release coming out this week is that the code that has been proposed is not, when I last checked, operating system independent. We don't generally mainline code that doesn't work on most variants of UNIX. Of course, because it works fine on linux there's no problems on Gentoo. Anyway, I think it's great to offer a HylaFAX+ package, just don't confuse it with HylaFAX and ideally, offer end users the choice. -Darren
Created attachment 111711 [details] update hylafax+ ebuild updated the uri thing. Changed the name of the ebuild to hylafax+ it should go in /usr/portage/net-misc/hylafax+/
No problem Darren. From the beginning I mentioned that this is not the same as hylafax. I changed the ebuild name to add a + at the end of it.
(In reply to comment #6) > > I changed the ebuild name to add a + at the end of it. Much appreciated! -d
Created attachment 112692 [details] hylafax+-5.1.1.ebuild updated to 5.1.1. Replaced MIRROR with SRC_URI or else it won't compile. When changing the name to hylafax+ I had to untar and repackage the source tarbal so that it's source folder has the '+' sign in it. If I don't do this then it won't find the configure file. This is really a fault of hylafax+ packagers. They should do everything with a + in it. Either that or I don't know how to tell the ebuild not to expect everything to be named just like the ebuild file.
Created attachment 112693 [details] faxgetty-5.1 Sample of the faxgetty init script. Someone's gotta change it so that the ttySx device are done automatically. I just hardcode my ttySx device into the script.
Created attachment 123596 [details] net-misc/hylafax+/hylafax+-5.1.5.ebuild" i have upgraded the ebuild to v5.1.5 and fixed some bad ebuild usage: - hylafax+ cannot be keyworded as "hppa" because package "taylor-uucp" is not provided from the hppa profile. - fixed the SRC_URI to use the SF mirrors (as required by devmanual docs to be portage compliant) - fixed package name handling (as required by devmanual docs to be portage compliant) - fixed syntax errors on line 23 and 138 - renamed USE "html" as "doc" (as required by devmanual docs to be portage compliant) - blocked package net-misc/hylafax into the DEPENDS. accordling to the site, hylafax and hylafax+ cannot be installed at the same time. - removed cflag filtering for #74457. the compilation issue with gcc3.4.3 has been fixed upstream and actualy the stable gcc release for the hardened profile is 3.4.6, so there is not need to filter flags. package compile and run fine on an hardened profile so i have removed the not necessary eclasses from the ebuild.
What about those files (99hylafax-5.1 and hylafax-5.1) referenced by the end of the ebuild? Should we just rename 99hylafax-4.2 and hylafax-4.2 coming from the standard hylafax ebuild? PS: what about adding those enhancements I proposed in bug #138393? I had no luck (yet) with hylafax, but I still have hopes with hylafax+! ;-)
(In reply to comment #11) > What about those files (99hylafax-5.1 and hylafax-5.1) referenced by the end of > the ebuild? Should we just rename 99hylafax-4.2 and hylafax-4.2 coming from the > standard hylafax ebuild? FYI No, you should not! As was explained above, we are talking about two different packages here (hylafax+ and hylafax). These cannot be installed at the same time. So, ideally: installing the hylafax ebuild will put 99hylafax-4.2 and hylafax-4.2 into etc installing the hylafax+ ebuild will put 99hylafax-5.1 and hylafax-5.1 into etc uninstalling the hylafax ebuild will remove 99hylafax-4.2 and hylafax-4.2 into etc uninstalling the hylafax+ ebuild will remove 99hylafax-5.1 and hylafax-5.1 into etc There will be no version colliding ever (if both packages have 5.1 e.g.), since they must not be installed at the same time. When Gentoo Devs accept hylafax+ ebuild, people can finally go on and file bugs according to the variant of HylaFAX they use. This confusion arises since the discussion/bug/ebuild stuff of the two variants all occurs in this hylafax thread where it should not. Let's look forward ;-) Regards, cmuelle8
Shame on me, I can see your point, Alessandro. Since George just adapted the hylafax ebuild, you're wondering where these 5.1 conf files should come from, as they are not there yet (just the 4.2 for original hylafax ones). Well, my guess would be that PATH="/var/spool/fax/bin" CONFIG_PROTECT="/var/spool/fax/etc /usr/lib/fax" is also valid for hylafax+ 5.1 (since CONFIG_PROTECT is just a means for portage/paludis to know not to overwrite stuff automatically), the question remains for the hylafax-4.2 (can we use this init script for hylafax+ too) regards
Last thing for today (shutting up now ;-): can this patch please be incorporated into any hylafax build (all variants), since paludis does not merge fifos (to be created in the post/preinst functions it says in the docs) --- ../gentoo/net-misc/hylafax/hylafax-4.3.1.ebuild 2007-04-29 00:35:57.000000000 +0200 +++ ./net-misc/hylafax/hylafax-4.3.1.ebuild 2007-07-31 02:32:48.000000000 +0200 @@ -137,10 +137,23 @@ dodoc CHANGES CONTRIBUTORS COPYRIGHT README TODO } +pkg_preinst() { + rm -f ${D}/var/spool/fax/FIFO +} + pkg_postinst() { + cd /var/spool/fax + rm -f /var/spool/fax/FIFO + mkfifo -m 600 FIFO + chown uucp.uucp FIFO + echo einfo "See the docs and man pages for detailed configuration info." echo einfo "Now run faxsetup and (if necessary) faxaddmodem." echo } + +pkg_prerm() { + rm -f /var/spool/fax/FIFO +}
Created attachment 126509 [details] hylafax+-5.1.6.ebuild This is basically the same ebuild as 5.1.5 except it'll install v5.1.6 of hylafax+. Just want to say thanks to equilibrium@gechi.it for patching up the old ebuild I put up. This one works great :) I still use the same 99hylafax-4.2 hylafax-4.2 files for hylafax+, thats why I just renamed them. They still work and i've had no problems with them. The only problem I see now is with the faxgetty-5.1 file I made. There are 2 ways of doing this. Either putting faxgetty in the /etc/inittab for each defined serial port or to use /etc/init.d/faxgetty to stop and start them. Each has it's advantages. I use the faxgetty init.d script on some machines and the inittab version on others. The only thing is that the user has to edit the files to specify which serial port to use. I heard that the debian init script automatically runs faxgetty for all working ttySx devices (or maybe we can add them in a /etc/conf.d/hylafax+ conf file ? Also what would be a nice would be to automatically add hylafax syslog-ng entry --- filter f_hylafax { facility(local0);}; destination hylafax{file("/var/log/hylafax.log" perm(0640) owner(root) group(uucp));}; log { source(src); filter(f_hylafax); destination(hylafax);}; ---
Created attachment 141103 [details] hylafax+-5.2.1-r1 Latest version plus class1 rhnocarrier patch
Created attachment 141104 [details, diff] hylafax-class1-rhnocarrier.patch class1 rh no carrier patch. Improves resiliency for hylafax (patch by Lee)
Version bump to 5.2.2 ------------------------- HylaFAX+ 5.2.2 includes the following developments beyond version 5.2.1 New Changes * make faxmail decode RFC2047-encoded headers (10 Feb 2008) * add ModemRaiseATCommands configuration feature (8 Feb 2008) * make parseQfile read $faxname and $faxnumber (7 Feb 2008) * fix the initialization of CallID types when using CIDName or CIDNumber (7 Feb 2008) * pass Content-Description, Content-ID, Content-Disposition information along to the faxmail MIMEConverters (7 Feb 2008) * extend high-speed receive carrier when possible (5 Feb 2008) * add support for (31 Jan 2008) * more socklen_t adjustments for HP-UX 11 (31 Jan 2008) * remove "old" protocol support (30 Jan 2008) * make the server trust the client's specified document type (26 Jan 2008) * make pcl2fax produce TIFF output directly (25 Jan 2008) * escape double-quotes in client communication before passing them to the server (25 Jan 2008) * improve resiliency after a AT+FRH=3, NO CARRIER condition (16 Jan 2008) * employ "intelligent" RTFCC to use MH format when it is better than 2-D compressions (10, 12 Jan 2008) * pass jobid into *2fax converters (8, 11 Jan 2008)
Created attachment 145977 [details] hylafax+-5.2.2.ebuild Updated ebuild to 5.2.2
hi! sorry for interrupting your discussion but i am very interested in hylafax+ cause the version of hylafx in portage is stuck at 4.3.0 - the latest available version is 4.4.4... can anyone tell me when the new hylafax+ will be added to the portage tree? or is the attached ebuild ready for install? thx snIP3r
(In reply to comment #20) > hi! > > sorry for interrupting your discussion but i am very interested in hylafax+ > cause the version of hylafx in portage is stuck at 4.3.0 - the latest available > version is 4.4.4... > can anyone tell me when the new hylafax+ will be added to the portage tree? or > is the attached ebuild ready for install? > > thx > snIP3r > It's pretty much ready to go. I dunno why it's not in the portage tree yet. Basically make a dir in /usr/portage/net-misc/hylafax+ copy/paste the ebuild inside there. Download the source, put it in /usr/portage/distfiles, go to /usr/portage/net-misc/hylafax+ and run ebuild hylafax+-5.2.2.ebuild manifest. Then your ready to emerge hylafax+
(In reply to comment #21) > (In reply to comment #20) > > hi! > > > > sorry for interrupting your discussion but i am very interested in hylafax+ > > cause the version of hylafx in portage is stuck at 4.3.0 - the latest available > > version is 4.4.4... > > can anyone tell me when the new hylafax+ will be added to the portage tree? or > > is the attached ebuild ready for install? > > > > thx > > snIP3r > > > > It's pretty much ready to go. I dunno why it's not in the portage tree yet. > Basically make a dir in /usr/portage/net-misc/hylafax+ copy/paste the ebuild > inside there. Download the source, put it in /usr/portage/distfiles, go to > /usr/portage/net-misc/hylafax+ and run ebuild hylafax+-5.2.2.ebuild manifest. > Then your ready to emerge hylafax+ > hi all! installation runs perfect. but i do not have any start/stop scripts. instead i get these messages: * Adding env.d entry for Hylafax cp: cannot stat `/usr/portage/net-misc/hylafax+/files/99hylafax-5.1': No such file or directory * Adding init.d entry for Hylafax cp: cannot stat `/usr/portage/net-misc/hylafax+/files/hylafax-5.1': No such file or directory * Adding init.d entry for Faxgetty cp: cannot stat `/usr/portage/net-misc/hylafax+/files/faxgetty-5.1': No such file or directory where can i get these (start/stop) scripts/files? for faxgetty i do not need them because i start faxgetty via /etc/inittab greets snIP3r
(In reply to comment #22) > (In reply to comment #21) > > (In reply to comment #20) > > > hi! > > > > > > sorry for interrupting your discussion but i am very interested in hylafax+ > > > cause the version of hylafx in portage is stuck at 4.3.0 - the latest available > > > version is 4.4.4... > > > can anyone tell me when the new hylafax+ will be added to the portage tree? or > > > is the attached ebuild ready for install? > > > > > > thx > > > snIP3r > > > > > > > It's pretty much ready to go. I dunno why it's not in the portage tree yet. > > Basically make a dir in /usr/portage/net-misc/hylafax+ copy/paste the ebuild > > inside there. Download the source, put it in /usr/portage/distfiles, go to > > /usr/portage/net-misc/hylafax+ and run ebuild hylafax+-5.2.2.ebuild manifest. > > Then your ready to emerge hylafax+ > > > > hi all! > > installation runs perfect. but i do not have any start/stop scripts. instead i > get these messages: > > * Adding env.d entry for Hylafax > cp: cannot stat `/usr/portage/net-misc/hylafax+/files/99hylafax-5.1': No such > file or directory > * Adding init.d entry for Hylafax > cp: cannot stat `/usr/portage/net-misc/hylafax+/files/hylafax-5.1': No such > file or directory > * Adding init.d entry for Faxgetty > cp: cannot stat `/usr/portage/net-misc/hylafax+/files/faxgetty-5.1': No such > file or directory > > > where can i get these (start/stop) scripts/files? for faxgetty i do not need > them because i start faxgetty via /etc/inittab > > greets > snIP3r > Hi, the file is listed in the table above "faxgetty-5.1" download it and put it in the "files" directory in portage. It's just an init script I put together that starts faxgetty. I don't even use it cos I do like you and put in the inittab entries.
(In reply to comment #23) > (In reply to comment #22) > > (In reply to comment #21) > > > (In reply to comment #20) > > > > hi! > > > > > > > > sorry for interrupting your discussion but i am very interested in hylafax+ > > > > cause the version of hylafx in portage is stuck at 4.3.0 - the latest available > > > > version is 4.4.4... > > > > can anyone tell me when the new hylafax+ will be added to the portage tree? or > > > > is the attached ebuild ready for install? > > > > > > > > thx > > > > snIP3r > > > > > > > > > > It's pretty much ready to go. I dunno why it's not in the portage tree yet. > > > Basically make a dir in /usr/portage/net-misc/hylafax+ copy/paste the ebuild > > > inside there. Download the source, put it in /usr/portage/distfiles, go to > > > /usr/portage/net-misc/hylafax+ and run ebuild hylafax+-5.2.2.ebuild manifest. > > > Then your ready to emerge hylafax+ > > > > > > > hi all! > > > > installation runs perfect. but i do not have any start/stop scripts. instead i > > get these messages: > > > > * Adding env.d entry for Hylafax > > cp: cannot stat `/usr/portage/net-misc/hylafax+/files/99hylafax-5.1': No such > > file or directory > > * Adding init.d entry for Hylafax > > cp: cannot stat `/usr/portage/net-misc/hylafax+/files/hylafax-5.1': No such > > file or directory > > * Adding init.d entry for Faxgetty > > cp: cannot stat `/usr/portage/net-misc/hylafax+/files/faxgetty-5.1': No such > > file or directory > > > > > > where can i get these (start/stop) scripts/files? for faxgetty i do not need > > them because i start faxgetty via /etc/inittab > > > > greets > > snIP3r > > > > Hi, the file is listed in the table above "faxgetty-5.1" download it and put it > in the "files" directory in portage. It's just an init script I put together > that starts faxgetty. I don't even use it cos I do like you and put in the > inittab entries. > hi george! ok, thx. but i only need the file for starting hylafax in init.d: * Adding init.d entry for Hylafax cp: cannot stat `/usr/portage/net-misc/hylafax+/files/hylafax-5.1': No such file or directory can i get this somewhere? snIP3r
You can copy the file from /usr/portage/net-misc/hylafax/files/hylafax-4.2. It seems that the one I have for hylafax+ is the exact same copy.
Apparently wrong assignee...
I'm putting together a new phone server in a couple weeks. I'm currently using hylafax 4.3.1, but I'd be happy to test out hylafax+ 5.x. Can someone get it into portage as ~amd64 (or into portage at all)? (By the way, the current version of hylafax+ is 5.2.5 according to http://hylafax.sourceforge.net/ )
Created attachment 161157 [details] hylafax+-5.2.4.ebuild Hylafax+ v5.2.4 adds support for LDAP, so I've modified George's ebuild file to include a USE flag to enable/disable it. Tested with v5.2.4 to v5.2.6, all using the same file but only with -ldap though.
Created attachment 176587 [details] hylafax-5.2.8.ebuild From official hylafax-4.4.4-r2 Support disable/enable ldap, jbig Fix optimice double CCFLAGS change /usr/lib/fax to /etc/hylafax and fix CONFIG_PROTECT in x86_64 when /usr/lib64/fax no /usr/lib/fax require virtual/mta for send notifications
Created attachment 176589 [details] configure.diff patch to Support disable/enable ldap, jbig
Created attachment 178642 [details] hylafax-5.2.8.ebuild fix /etc/hylafax install
Hi Franzisco. I think it would be better to keep the plus within the ebuild. I changed that. Beside of that everything seem to work. Thank you.
Created attachment 189862 [details] hylafax-5.2.9.ebuild Update and commit fix to hylafax
(In reply to comment #33) > Created an attachment (id=189862) [details] > hylafax-5.2.9.ebuild > > Update and commit fix to hylafax > after the recent update of media-libs/jpeg-7 to media-libs/jpeg-8 and due to the latest gcc updates i cannot reinstall my working installation of version 5.2.2 so i tried to update to 5.2.9. but when trying to create te new manifest for version 5.2.9 i get this error: area52 hylafax+ # ebuild hylafax-5.2.9.ebuild manifest !!! /usr/portage/net-misc/hylafax+/hylafax-5.2.9.ebuild does not seem to have a valid PORTDIR structure. heres my emerge info: area52 hylafax+ # emerge --info Portage 2.1.7.16 (default/linux/amd64/10.0, gcc-4.3.4, glibc-2.10.1-r1, 2.6.30-gentoo-r5 x86_64) ================================================================= System uname: Linux-2.6.30-gentoo-r5-x86_64-AMD_Athlon-tm-_Dual_Core_Processor_4450e-with-gentoo-1.12.13 Timestamp of tree: Sun, 14 Feb 2010 07:30:01 +0000 app-shells/bash: 4.0_p35 dev-lang/python: 2.4.6, 2.5.4-r3, 2.6.4 dev-python/pycrypto: 2.0.1-r6 dev-util/cmake: 2.6.4-r3 sys-apps/baselayout: 1.12.13 sys-apps/sandbox: 1.6-r2 sys-devel/autoconf: 2.13, 2.63-r1 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.2 sys-devel/binutils: 2.18-r3 sys-devel/gcc: 4.1.2, 4.3.4 sys-devel/gcc-config: 1.4.1 sys-devel/libtool: 2.2.6b virtual/os-headers: 2.6.30-r1 ACCEPT_KEYWORDS="amd64" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=k8 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/udev/rules.d" CXXFLAGS="-O2 -march=k8 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests distlocks fixpackages news parallel-fetch protect-owned sandbox sfperms strict unmerge-logs unmerge-orphans userfetch" GENTOO_MIRRORS="ftp://de-mirror.org/distro/gentoo/ http://ftp.club-internet.fr/pub/mirrors/gentoo ftp://gentoo.tiscali.nl/pub/mirror/gentoo/ http://mirror.qubenet.net/mirror/gentoo/ http://mirror.switch.ch/ftp/mirror/gentoo/ http://mirror.bih.net.ba/gentoo/ http://gentoo.inode.at/ http://mirror.ing.unibo.it/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://gentoo.modulix.net/gentoo/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo http://mirror.etf.bg.ac.yu/gentoo http://linux.rz.ruhr-uni-bochum.de/download/gentoo-mirror/ http://mirror.muntinternet.net/pub/gentoo/ ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo http://gentoo.mneisen.org/ ftp://ftp.mneisen.org/gentoo http://gentoo.tiscali.nl/ http://mirror.ovh.net/gentoo-distfiles/ rsync://rsync.europe.gentoo.org/gentoo-portage/" LDFLAGS="-Wl,-O1" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow acl acpi amd64 apache2 apm berkdb bzip2 clearpasswd cli cracklib crypt cups curl cxx dri dvd fortran gdbm gmp gpm iconv ipv6 jbig logrotate mmx modules mudflap multilib mysql ncurses nls nodroproot nptl nptlonly oav openmp pam pcre perl pppd python readline reflection samba sasl session smartcard spl sse sse2 ssl sysfs tcpd unicode usb xml xml2 xorg xvid zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic auth_digest authn_anon authn_dbd authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs dav_lock dbd deflate dir disk_cache env expires ext_filter file_cache filter headers ident imagemap include info log_config logio mem_cache mime mime_magic negotiation proxy proxy_ajp proxy_balancer proxy_connect proxy_http rewrite setenvif so speling status unique_id userdir usertrack vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="fbdev glint intel mach64 mga neomagic nv r128 radeon savage sis tdfx trident vesa via vmware voodoo" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, FFLAGS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY perhaps someone could help me with this issue?? greets wolfgang
(In reply to comment #33) > Created an attachment (id=189862) [details] > hylafax-5.2.9.ebuild > > Update and commit fix to hylafax > will there ever be a chance for hylafax+ to be added to official portage tree?
Created attachment 230945 [details] hylafax+ 5.4.2 Because i needed this myself i created an updated ebuild. Ebuild goes to for example /usr/local/portage/net-misc/hylafax+ Init script and conf file also included. cheers t.
Created attachment 230947 [details] hylafax+ init
Created attachment 230949 [details] hylafax+ conf
Could Hylafax+ be included in the Sunrise overlay? Or is it already in another overlay I don't know about?
(In reply to comment #36) > Created an attachment (id=230945) [details] > hylafax+ 5.4.2 > > Because i needed this myself i created an updated ebuild. Ebuild goes to for > example /usr/local/portage/net-misc/hylafax+ > > Init script and conf file also included. > > cheers > t. > hi thomas! i cannot get your new package started. after successfull install of 5.4.2 i get this in /var/log/messages: Aug 30 19:59:03 area52 FaxQueuer[18277]: HylaFAX (tm) Version 5.4.2 Aug 30 19:59:03 area52 FaxQueuer[18277]: Copyright (c) 1990-1996 Sam Leffler Aug 30 19:59:03 area52 FaxQueuer[18277]: Copyright (c) 1991-1996 Silicon Graphics, Inc. Aug 30 19:59:03 area52 FaxGetty[3223]: HELLO Aug 30 19:59:03 area52 HylaFAX[18286]: HylaFAX INET: bind (port 4559): Address already in use Aug 30 19:59:03 area52 HylaFAX[18286]: HylaFAX INET: Unable to init server, trying again in 5 seconds. Aug 30 19:59:08 area52 HylaFAX[18286]: HylaFAX INET: bind (port 4559): Address already in use Aug 30 19:59:08 area52 HylaFAX[18286]: HylaFAX INET: Unable to init server, trying again in 10 seconds. Aug 30 19:59:18 area52 HylaFAX[18286]: HylaFAX INET: bind (port 4559): Address already in use Aug 30 19:59:18 area52 HylaFAX[18286]: HylaFAX INET: Unable to init server, trying again in 15 seconds. the init script displayes this: area52 ~ # /etc/init.d/hylafax+ start * Check hylafax server configuration... ... * Use spool directory /var/spool/fax * Starting HylaFAX server daemons ... * Starting /usr/sbin/faxq ... * Starting /usr/sbin/hfaxd with args -l 127.0.0.1 -q /var/spool/fax -i hylafax -d [ ok but i see no application running port 4557... perhaps someone can help me with this? thx wolfgang
(In reply to comment #40) > (In reply to comment #36) > > Created an attachment (id=230945) [details] [details] > > hylafax+ 5.4.2 > > > > Because i needed this myself i created an updated ebuild. Ebuild goes to for > > example /usr/local/portage/net-misc/hylafax+ > > > > Init script and conf file also included. > > > > cheers > > t. > > > hi thomas! > > i cannot get your new package started. after successfull install of 5.4.2 i get > this in /var/log/messages: > > Aug 30 19:59:03 area52 FaxQueuer[18277]: HylaFAX (tm) Version 5.4.2 > Aug 30 19:59:03 area52 FaxQueuer[18277]: Copyright (c) 1990-1996 Sam Leffler > Aug 30 19:59:03 area52 FaxQueuer[18277]: Copyright (c) 1991-1996 Silicon > Graphics, Inc. > Aug 30 19:59:03 area52 FaxGetty[3223]: HELLO > Aug 30 19:59:03 area52 HylaFAX[18286]: HylaFAX INET: bind (port 4559): Address > already in use > Aug 30 19:59:03 area52 HylaFAX[18286]: HylaFAX INET: Unable to init server, > trying again in 5 seconds. > Aug 30 19:59:08 area52 HylaFAX[18286]: HylaFAX INET: bind (port 4559): Address > already in use > Aug 30 19:59:08 area52 HylaFAX[18286]: HylaFAX INET: Unable to init server, > trying again in 10 seconds. > Aug 30 19:59:18 area52 HylaFAX[18286]: HylaFAX INET: bind (port 4559): Address > already in use > Aug 30 19:59:18 area52 HylaFAX[18286]: HylaFAX INET: Unable to init server, > trying again in 15 seconds. > > > the init script displayes this: > area52 ~ # /etc/init.d/hylafax+ start > * Check hylafax server configuration... ... > * Use spool directory /var/spool/fax > * Starting HylaFAX server daemons ... > * Starting /usr/sbin/faxq ... > * Starting /usr/sbin/hfaxd with args -l 127.0.0.1 -q /var/spool/fax -i hylafax > -d [ ok > > but i see no application running port 4557... > perhaps someone can help me with this? > thx > wolfgang > sorry for the interruption, problem is solved by killing a not-beeing-killed hfaxd...
Created attachment 246428 [details] hylafax+-5.4.2.ebuild updated a little in the hope that one day it gets into the official portage tree. removed the c++ header changes because they don't seem to apply (or do they?). using conf.d / initd files directly from hylafax since they are the same and upgrading/merging from hylafax to hylafax+ is straightforward.
I see that the bug is assigned to nerdboy@g.o. Anyway, I could pick up the maintainership and commit to tree.
It seems there's more work to this than just adding the ebuild. I believe that a virtual will have to be created for "hylafax" as there are other ebuilds that require hylafax || hylafax+ (eg. net-print/fax4cups).
5.4.3 is available upstream
Created attachment 297393 [details, diff] Makefile patch patch in FILESDIR
Created attachment 297395 [details] hylafax+ 5.5.0 ebuild
Created attachment 300229 [details] Patch for tiff-4.x support Version bump: hylafax+ 5.5.1 released on 2012-01-02 Just rename the old ebuild to hylafax+-5.5.1.ebuild and run patch over it as tiff-4 support already included since hylafax+ 5.4.0 :)
One of my boxes is showing this: !!! The following installed packages are masked: - net-misc/hylafax-6.0.3::gentoo (masked by: package.mask) /usr/portage/profiles/package.mask: # Samuli Suominen <ssuominen@gentoo.org> (26 Jan 2012) # No support for stable TIFF 4.x wrt #400925 with multiple # other issues wrt #297150, #356083, #335864 and #318485. # Version bump request been open since 2011-03-30 wrt #361187 # Unless fixed, removal in 30 days Now, is Gentoo going to replace net-misc/hylafax with net-misc/hylafax+ in the official repo, or will people running a fax box end having to do all the cut-and-paste work to put together a decently-running local overlay with the hylafax+ stuff stealed from this bug? It is not even in sunrise...
(In reply to comment #49) > is Gentoo going to replace net-misc/hylafax with net-misc/hylafax+ I wouldn't want Gentoo to replace hylafax with hylafax+. Just add the hylafax+ ebuild and create a virtual.
Created attachment 300589 [details] updated ebuild ebuild for latest version. changes: - respects tiff-4 - moved from media-libs/jpeg to virtual/jpeg in DEPEND
Given that hylafax seems on the way out -- is there a wiki article or anything that would help gentoo users running hylafax to switch to hylafax+? howto?
(In reply to comment #52) > Given that hylafax seems on the way out -- is there a wiki article or anything > that would help gentoo users running hylafax to switch to hylafax+? howto? Actually it's quite easy. Just create a backup of your hylafax config files and any custom scripts you made. Install hylafax+ and move your old config files back. That worked for me from a long time ago till now. Hylafax+ will work like that and it can take newer scripts. I'm still surprised its been 5 years since I posted this and its still not in portage.
Yeah, the one at RedHat/Fedora is nearly a year older, and politics have slowed it up there... https://bugzilla.redhat.com/show_bug.cgi?id=188542
I might be wrong but I don't see the big deal. A gentoo virtual such as virtual/hylafax would allow the user to choose between net-misc/hyalfax and net-misc/hylafax+, mutually exclusive. Any other package relying on hylafax would "require" virtual/hylafax. Possible binary file name collisions would be the same as with the hylafax(.org) ebuild already in portage.
Has anybody written an overlay for this for layman?
I've added this ebuild to my overlay "paddymac".
If the upstream is in good shape and there are no other issues precluding it from being added, I'd be willing to maintain this and put in portage tree. I assumed that someone else would have taken it over by now, but if not - no prob as I actually use it.
Upstream HylaFAX+ (http://hylafax.sourceforge.net) is in good shape.
(In reply to comment #57) > I've added this ebuild to my overlay "paddymac". How do I get this overlay "paddymac" to layman?
OK, I've added this "paddymac" to layman but how does it relates to "hylafax"?
I've install "hylafax+" from layman paddymac but it does not install start/stop scrip in: /etc/initd.d/ What is the solustion?
Created attachment 306887 [details] hylafax+ startup script hylafax+ installs OK from overlay "paddymac" but it is missing /etc/init.d/ start/stop script. I've coppied old startup script "hylafax" to /etc/init.d/ and it is working OK. Here is a copy. Correct me anybody if this is not the way to do it.
I'll have ebuild in portage tree this weekend....testing currently on my own workstation. Initial package will be without keywords, users can feel free to add it to their keywords file. If we go a week or two without any bugs, I'll unmask it with ~x86 ~amd64 flags.
(In reply to comment #64) > I'll have ebuild in portage tree this weekend....testing currently on my own > workstation. > Initial package will be without keywords, users can feel free to add it to > their keywords file. > If we go a week or two without any bugs, I'll unmask it with ~x86 ~amd64 > flags. I would like to test it. How do I add the keywords file? :-/ I'm not a programmer.
Ebuild is now in tree. No keywords - masked. I had to make some modest changes to get past all the standard QA tests. The biggest concern being the requirement to compile with -j1 which is substantially frowned upon. I need to verify if this is still required. The init script may also need significant changes. I may have broken something while patching/qa'ing but if so I'll fix it on the next bump and I anticipate I'll be bumping every 2-3 days for the next few weeks while fine tuning the ebuild. Note that package has been created as 'hylafaxplus' not 'hylafax' or 'hylafax+', although the binary names/etc remain the same....just all gentoo references to the package name or init/conf scripts are changed. I added the license as hylafaxplus, and copied the COPYRIGHT file as the license but I'd like to clarify further that upstream considers the contents of COPYRIGHT as the complete and current license. Marking this bug as resolved. If there are any issues, please open up a new bug. note to test the ebuild while it is masked, just append to /etc/portage/package.keywords as you would normally do for ~amd64/~x86 only packages, but use ** as arch instead of ~amd64/~x86.