-
-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different directory name inside the Forge package #151
Comments
Hi, Sorry about that. I just rebuilt the package and released 1.15.1, which should fix that. Does it work now? |
Yes, it does work now. Just out of interest, how did you build the previous package? Simply with |
Basically yes, I downloaded the .tar.gz from Github. Why that doesn't work with forge (and they don't check the uploads properly) is beyond me. Anyway, thanks for the bug report! |
It does work with the Forge, just not with my caching method :) As far as I can tell, you did nothing wrong, just different. ;) I'll leave the FORGE ticket open, so that they can take a statement about whether such a release is valid or invalid in their eyes. |
Hi there,
I'm currently having problems using your 1.15.0 Forge package with my r10k clone (https://github.com/xorpaul/g10k), because it doesn't have the same directory name pattern than all other Forge packages.
It also look like that this Forge package was probably not generate with the standard
puppet module build
as described here https://docs.puppet.com/puppet/latest/modules_publishing.html#build-your-moduleBuilding your module with
puppet module build
does create the correct directory namevshn-gitlab-1.15.0/
inside the package, but the currently uploaded package does have a directorypuppet module build
inside.Did you build your package with
puppet module build
or with something else?I'm not entirely sure if the Puppetlabs Forge should be validating uploaded packages for this stuff, but I'll open a FORGE ticket and ask them.
Edit: https://tickets.puppetlabs.com/browse/FORGE-386
The text was updated successfully, but these errors were encountered: