Yet blueprint.sh still includes:
mkdir -p "/etc"
cat >"/etc/hosts" <<EOF
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
And doesn't include a second sources entry
I've been looking into this issue and can't reproduce it. I do, however, have a couple of ideas.
First things first: make sure you're running blueprint-create as root, probably via sudo. It may fail (with a message saying as much) to grab source directories if it isn't root.
It's possible you're on a system with a version of sudo that doesn't do what I expect with regard to environment variables, particularly HOME. Could you try moving ~/.blueprintignore to /etc/blueprintignore and see if you get the same behavior? If it works that way, let me know what operating system and version you're using so I can try to do the right thing there by default.
Hope one of those helps! If not, find me in #devstructure on Freenode and let's get to the bottom of this.
I had the same issue. Moving it to /etc/blueprintignore as suggested worked.
I'm on Debian 6 and this is happening when I'm logged in as root directly (not sure if that matters or not but thought I'd mention it).
I think I just observed the same problem on Ubuntu.
$ cat /etc/lsb-release
DISTRIB_DESCRIPTION="Ubuntu 12.04.1 LTS"