Bug 55962

Summary:	hylafax ebuild not using CONFIG_PROTECT
Product:	Gentoo Linux	Reporter:	stan <stan>
Component:	New packages	Assignee:	Steve Arnold <nerdboy>
Status:	RESOLVED FIXED
Severity:	trivial
Priority:	Lowest
Version:	unspecified
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description stan 2004-07-03 06:46:43 UTC

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"

Comment 1 Steve Arnold archtester

2004-07-04 19:46:25 UTC

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.

Comment 2 Christian Zoffoli (RETIRED) gentoo-dev

2005-03-18 03:41:03 UTC

actually hylafax has the same problem, please add an env file with config protect.

Comment 3 Christian Zoffoli (RETIRED) gentoo-dev

2005-03-18 03:47:59 UTC

I've done a partial mistake, we have the problem when we upgrade old installations.

Comment 4 Jakub Moc (RETIRED) gentoo-dev

2005-08-04 14:11:25 UTC

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