>> >
>> > In fact it seems that the problem lies somewhere in your configuration.
>> > Consider the following transcript which I have just obtained:
>> >
>>> lots of rpm
A rather 'dated' system (updated over time, orig install was 8.2):
12:51 shanghai:../RPMS/noarch # rpm -Uhv dumb-a-0-0.noarch.rpm
Preparing... ########################################### [100%]
1:dumb-a ########################################### [100%]
12:51 shanghai:../RPMS/noarch # rpm -ql dumb-a
/etc/dumb
/etc/dumb/stamp
12:51 shanghai:../RPMS/noarch # cat /etc/dumb/stamp
dumb-a
12:51 shanghai:../RPMS/noarch # rpm -Uhv dumb-b-0-0.noarch.rpm
Preparing... ########################################### [100%]
file /etc/dumb/stamp from install of dumb-b-0-0 conflicts with file
from package dumb-a-0-0
12:51 shanghai:../RPMS/noarch # rpm -ihv dumb-b-0-0.noarch.rpm
Preparing... ########################################### [100%]
file /etc/dumb/stamp from install of dumb-b-0-0 conflicts with file
from package dumb-a-0-0
12:51 shanghai:../RPMS/noarch # rpm -q rpm
rpm-4.4.2-40
Question of the month: What does the pristine rpm source tarball do?
Maybe we have a patch in SUSE's rpm that reverts to the DTRT behavior.
dumb.spec:
Name: dumb-a
Version: 0
Release: 0
License: WTFPL
Summary: Foo
Group: What
BuildRoot: %_tmppath/%name-%version-%build
%description
%install
mkdir -p "%{buildroot}/etc/dumb";
echo %name >"%{buildroot}/etc/dumb/stamp";
%files
/etc/dumb
You might try with that.
Jan Engelhardt
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
