I know this is almost hilariously minor, but when building things in mock /bin/hostname is generally not present unless pulled in as a build dependency, and lack of /bin/hostname causes some annoying spew in the resulting build logs: /etc/profile: line 38: /bin/hostname: No such file or directory I think it suffices to change HOSTNAME=`/bin/hostname` to HOSTNAME=`/bin/hostname 2>/dev/null` in /etc/profile to quiet the error but I'm far from an expert in sh; I guess it might be cleaner to conditionalize things based on the presense of /bin/hostname. I did patch this into my local setup package and everything seemed to work well.
Hi Jason. If i remember correctly this has been fixed by now with better dependencies and a proper basic set of packages for mock, right? If not, let me know and i'll see what i can do. Completely suppressing the error message here might not be desirable. Read ya, Phil
Currently in rawhide, nothing in the default buildroot has a dependency on net-tools, and so every mock build will still start out with /etc/profile: line 38: /bin/hostname: No such file or directory Like I said, hilariously minor, but it is indeed still around.
Bash might already set this var automatically: HOSTNAME Automatically set to the name of the current host.
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Added 2>/dev/null in rawhide, built as setup-2.7.4-2.fc11.
setup-2.6.18-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/setup-2.6.18-1.fc9
setup-2.6.18-1.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update setup'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-9727
setup-2.6.18-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.