55962 2004-07-03 06:46 0000 hylafax ebuild not using CONFIG_PROTECT 2005-08-04 14:11:25 0000 1 1 1 Unclassified Gentoo Linux Ebuilds unspecified All All RESOLVED FIXED P5 trivial --- 1 stan@saticed.me.uk nerdboy@gentoo.org stan@saticed.me.uk 2004-07-03 06:46:43 0000 during an upgrade of hylafax files like /var/spool/fax/etc/hosts.hfaxd and /var/spool/fax/etc/xferfaxlog are overwritten creating a /etc/env.d/XXhylafax like the bind ebuild does is a possible solution, containing CONFIG_PROTECT="/var/spool/fax/etc" nerdboy@gentoo.org 2004-07-04 19:46:25 0000 Ok, it's in portage as 4.1.8-r4, but the effect is silent with the export in the ebuild (I couldn't get the env.d thing to work without an env-update and source /etc/profile). The export should preserve the files in /var/spool/fax/etc for upgrades, and then it can be removed at a later date. Try it out. xmerlin@gentoo.org 2005-03-18 03:41:03 0000 actually hylafax has the same problem, please add an env file with config protect. xmerlin@gentoo.org 2005-03-18 03:47:59 0000 I've done a partial mistake, we have the problem when we upgrade old installations. jakub@gentoo.org 2005-08-04 14:11:25 0000 No idea why was this reopened. Closing as fixed. *hylafax-4.1.8-r4 (04 Jul 2004) 04 Jul 2004; Steve Arnold <nerdboy@gentoo.org> +files/99hylafax, +hylafax-4.1.8-r4.ebuild: added updated ebuild with env.d entry to fix bug #55962