rpm builds failing with "Installed (but unpackaged) file(s) found"

[Iain Arnell]

On Fri, Jul 15, 2011 at 4:16 PM, Rex Dieter <rdieter at math.unl.edu> wrote:
> Panu Matilainen wrote:
>
>>
>> FYI, there appears to be a bug in the just-released rpm-4.9.1 which
>> causes legitimate specs to fail with "Installed (but unpackaged) file(s)
>> found" errors. This happens when recursively included directories in
>> %files are marked with trailing /, eg
>>
>> %{_includedir}/mypkg works everywhere, but %{_includedir}/mypkg/ is now
>> failing in rawhide.
>>
>> This is NOT intentional, don't start changing your packages. Somebody
>> please untag rpm-4.9.1 from rawhide, I'll deal with the issue later on.
>
> done,

I see that we now have rpm-4.9.1-2.fc16, but it still doesn't seem
quite right. Previously, httpd (for example) used to have files:

/etc/httpd
/etc/httpd/conf
/etc/httpd/conf.d
/etc/httpd/conf.d/README
/etc/httpd/conf.d/welcome.conf
/etc/httpd/conf/httpd.conf
/etc/httpd/conf/magic
/etc/httpd/logs
...

But since being rebuilt yesterday with the new 4.9.1, some of those
directories are now listed with the trailing slash:

/etc/httpd/
/etc/httpd/conf.d/
/etc/httpd/conf.d/README
/etc/httpd/conf.d/welcome.conf
/etc/httpd/conf/
/etc/httpd/conf/httpd.conf
/etc/httpd/conf/magic
/etc/httpd/logs

Which has broken at least one package that requires /etc/httpd/conf.d

Is listing the trailing slash intended behaviour and the dependent
package(s) now needs fixing?

-- 
Iain.