~/.blueprintignore not respected #99

Open
opie4624 opened this Issue Nov 1, 2011 · 3 comments

Comments

Projects
None yet
4 participants
@opie4624

opie4624 commented Nov 1, 2011

~/.blueprintignore contents:

:file:/etc/hosts
!:source:/opt

Yet blueprint.sh still includes:

mkdir -p "/etc"
cat >"/etc/hosts" <<EOF
127.0.0.1       localhost

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
EOF

And doesn't include a second sources entry

@rcrowley

This comment has been minimized.

Show comment
Hide comment
@rcrowley

rcrowley Nov 3, 2011

Member

Hi @opie4624,

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.

Member

rcrowley commented Nov 3, 2011

Hi @opie4624,

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.

@pix2D

This comment has been minimized.

Show comment
Hide comment
@pix2D

pix2D Nov 27, 2011

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).

pix2D commented Nov 27, 2011

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).

@rstacruz

This comment has been minimized.

Show comment
Hide comment
@rstacruz

rstacruz Dec 25, 2012

I think I just observed the same problem on Ubuntu.

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.1 LTS"

I think I just observed the same problem on Ubuntu.

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.1 LTS"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment