> Hi Eirik,
> 
> I was unable to reproduce your issue in Puppet 5.5.6 (aka SHA 60de165 from 
> https://github.com/puppetlabs/puppet/releases):
> 
> kris.bosland@kris:puppet % git checkout 60de165                               
>                                                                               
>                        ±[5.5.6^0]
> HEAD is now at 60de165b86... Merge pull request #7007 from 
> justinstoller/maint-pin-rake-more
> kris.bosland@kris:puppet % cat ../tmp/test/bash/manifests/init.pp             
>                                                                               
>                        ±[5.5.6^0]
> class bash {
>     package { "shells/bash":
>         ensure => installed,
>     }
> }
> 
> class smash {
>     package { "shells/bash":
>         ensure => installed,
>     }
> }
> kris.bosland@kris:puppet % bx puppet apply --modulepath ../tmp/test -e 'class 
> test { include bash }; include test'                                          
>                        ±[5.5.6^0]
> Warning: Unacceptable location. The name 'smash' is unacceptable in file 
> '/Users/kris.bosland/work/tmp/test/bash/manifests/init.pp' (file: 
> /Users/kris.bosland/work/tmp/test/bash/manifests/init.pp, line: 7, column: 1)
> Notice: Compiled catalog for kris.bosland-c02kf9eafft1 in environment 
> production in 0.56 seconds
> Error: Mac OS X PKG DMGs must specify a package source.
> Error: /Stage[main]/Bash/Package[shells/bash]/ensure: change from 'absent' to 
> 'present' failed: Mac OS X PKG DMGs must specify a package source.
> Notice: Applied catalog in 0.02 seconds
> kris.bosland@kris:puppet %
> 
> Note that Puppet complains about the class 'smash' in the 'bash' module, but 
> not the class 'bash'.

I would expect that too - not that I like it (it will still require a load of 
work to clean up our puppetserver.log), but in our end it complains even about 
'bash'..


> Can you provide a more detailed example that fails for you?

I'm not sure how much more detail I can give? Most of our in-house modules are 
relatively simple, much like my original example. It complains about - it 
seems, but I haven't counted - every module we have written.

One possible issue might be that we have several module directories - all 
listed in basemodulepath:
/usr/local/etc/puppet/modules - anything installed using 'puppet module...'
/usr/local/etc/puppet/modules.common - all in-house modules that apply to all 
our environments
 - This is where the bash module (and git, sudo, nano, vim, etc....all 
suffering from the same) lives
/usr/local/etc/puppet/nodes.common - all node classes and definitions that are 
the same across all our environments

We're on FreeBSD and running unmodified puppetserver from the ports tree. 
Puppet server is v5.3.5

Does this help? Any information I can collect that would shed light on this?


Thanks,
/Eirik

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/3A1D3608-9A23-44FE-A2B5-A3351266BFD2%40anduin.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to