Description of problem: After (re)building isdn4k-utils, there is a directory left named /var/tmp/isdnk4k-utils'/usr/share/doc/vbox' (the two single quotes are actually part of the directory name!!) with two files in it, vbox.txt and vbox.sgml. So, something goes horribly wrong with quoting during the buildroot install, creating a second buildroot with the quotes at some point. Version-Release number of selected component (if applicable): 3.2-18.p1.1 Additional info: I will try to find the problem and submit a fix.
The culprit is the make install part of the spec file together with the way the directories are defined in the .config file. .config hast the directories enclosed by single quotes. The make install part creates the directory enclosed by double quotes, thus making the single quotes part of the directory name. Making install in de make[3]: Entering directory `/usr/src/redhat/BUILD/isdn4k-utils-CVS-2003-09-23/vbox/doc/de' make[4]: Entering directory `/usr/src/redhat/BUILD/isdn4k-utils-CVS-2003-09-23/vbox/doc/de' make[4]: Nothing to be done for `install-exec-am'. test -z "'/usr/share/doc/vbox'" || mkdir -p -- "/var/tmp/isdn4k-utils-root'/usr/share/doc/vbox'" /usr/bin/install -c -m 644 'vbox.sgml' '/var/tmp/isdn4k-utils-root'/usr/share/doc/vbox'/vbox.sgml' /usr/bin/install -c -m 644 'vbox.txt' '/var/tmp/isdn4k-utils-root'/usr/share/doc/vbox'/vbox.txt' Additionally, line 136 of the specfile is bogus: ( cd %{_builddir}/isdn4k-utils/linux-2.4 && ln -s /usr/include . ) the directory, the specfile changes to is non-existant.
I've made a small patch to solve both problems (will attach it here). Note that the hack to avoid the quotes in the directory is a big hack, but a more structural solution probably has a high impact on several configure/Makefiles and should be done upstream.
Created attachment 114436 [details] Patch for spec file to solve both described problems
I have already added the hack in rawhide for a long time, and it's in RHEL4-CVS too. If we update isdn4k-utils for RHEL4 in the future, it will include this fix. Many thanks for your report.
Unfortunately this issue did not get resolved in RHEL 4.9. If this is still a concern, please contact your Red Hat Support representative to request an exception.