Bug 62895 – upgrading ypserv can overwrite user-seetings in /var/yp/Makefile

Bug 62895 - upgrading ypserv can overwrite user-seetings in /var/yp/Makefile

Summary:	upgrading ypserv can overwrite user-seetings in /var/yp/Makefile

Status:	CLOSED DUPLICATE of bug 60377

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	ypserv (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	All Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Alexander Larsson
QA Contact:	Aaron Brown
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-04-07 07:30 EDT by Bernhard Weisshuhn
Modified:	2007-04-18 12:41 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-04-07 07:30:58 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Bernhard Weisshuhn 2002-04-07 07:30:54 EDT

Description of problem:
Upgrades of ypserv overwrite /var/yp/Makefile which may contain customized
Infomation (which maps to build, NOPUSH etc)

Version-Release number of selected component (if applicable): ypserv-2.2-7


How reproducible:
Sometimes

Steps to Reproduce:
install yperv-2.2.3, edit /var/yp/Makefile, upgrade to ypserv-2.2.7.

Actual Results:  Changes in /var/yp/Makefile are lost.

Expected Results:  new Makefile should be created as /var/yp/Makefile.rpmnew, or
at least the old version should be preserved as Makefile.rpmold

Additional info:

When I tried to reproduce it, my changes to Makefile were preserved, but no
rpmnew was created. But I know that I lost my changes when I upgraded from 2.2.3
to 2.2.7. Sorry to be so vague on this.

The obvious fix should be to make /var/yp/Makefile %config(noreplace) in the
specfile.

Comment 1 Alexander Larsson 2002-04-07 17:42:16 EDT


*** This bug has been marked as a duplicate of 60377 ***

Note You need to log in before you can comment on or make changes to this bug.