-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
error building RPM re manpage 3 content #1277
Comments
Already fixed by #1262. |
BTW, "pip install argparse" is doable on older platforms and will work around this problem w/o the pull request. We're still going to fix it though, as I understand not everyone knows about that and distros are probably not going to package argparse. |
Please let me know when the fix will be released because the current version is still broken. |
Nothing is broken, you are just missing a build dependency and the pull easy_install pip Simple! On Wed, Oct 10, 2012 at 10:46 AM, Nicola Asuni notifications@github.comwrote:
|
3 days ago the make rpm was working and now is not working anymore. I checked the ansible.spec and I commenting out two lines related to documentation dirs, the system is working again. Are we talking about the same problem? |
I have installed the missing packages but I am getting the same error:
This because the ansible.spec is not yet fixed. |
NOTE: this bug is not related to #1262. |
Dag is talking about something else, which confused me also. Please paste the actual error message you are seeing from the latest git. |
Nevermind, saw your last post, thanks I think I have some unpushed changes on my computer -- will investigate later. This is a result of merging the repos. |
Look at the patch! The fix is in the patch linked to that PR. The fix is both a change to the Makefile to include the docs-target in the sdist-target as well as a fix to the hacking/module_formatter.py script so the man3 pages are in fact created and part of the tarball that is used by the SPEC file. |
Unless of course you do not want the man3 pages in the SPEC file, but what's the purpose of having these man-pages if they are not being part of the package ? |
I do want them in. |
Merged stuff in, but currently getting this: Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/mdehaan/ansible/rpm-build/BUILDROOT/ansible-0.8-0.git201210110009.el6.x86_64 Any ideas @dagwieers or @tbielawa ? Thanks!!! |
@nicolafubra @mpdehaan I'm checking this out now. But first I must run to the store for beer. |
Unfortunately in my initial attempts I could not reproduce this bug. Build result here: http://koji.fedoraproject.org/koji/taskinfo?taskID=4580033 Built from 6d2f003 using @mpdehaan @nicolafubra @dagwieers Can one or more of you (who can reproduce) please provide:
I have also tested using mock to build the SRPM and then the subsequent RPM:
The results are pretty long, so here they are linked offsite: http://lnx.cx/~tbielawa/ansible-SRPM-epel-6-x86_64-mockbuild.log http://lnx.cx/~tbielawa/ansible-RPM-epel-6-x86_64-mockbuild.log http://lnx.cx/~tbielawa/ansible-RPM-epel-6-x86_64-rpmfile-contents.log |
Tip also and CentOS 6.2 for me. No user rpm macro config or anything. Will get logs. Sent from my iPad On Oct 10, 2012, at 10:12 PM, tbielawa notifications@github.com wrote:
|
Works fine for me on RHEL6.3:
|
Now the situation seems worse than before: [root@rpmbuild makerpm]# su -c 'cd /home/makerpm && git clone git://github.com/ansible/ansible.git' makerpm [root@rpmbuild ansible]# git log -1 [root@rpmbuild ansible]# cat /etc/redhat-release [root@rpmbuild ansible]# uname -a [root@rpmbuild makerpm]# su -c 'cd /home/makerpm/ansible && make rpm' makerpm |
This bug seems now fixed: |
Ansible uses asciidoc to generate a working tarball with documentation included, because of this it should not be/become a BuilldRequires to the RPM package. |
Correct, asciidoc generated things are checked in to source control. I still see "make rpm" on my environment complaining about modules that are not installed, however, but this appears to be only happening to me and not in Fedora, so... perhaps something I just need to figure out :) RPM build errors: etc |
Reproduced with @dhozac's insight on IRC today. Setting |
Well there's your problem:
This is saying to install the contents of ./library into What we're trying to resolve now is finding a method that (roughly) supports:
Here's a diff that would fix things to just installing into /usr/share/ansible/:
But in a way it's pointless, because ansible modules will go into location1 while when ansible runs it will look in location2 (set via |
yep, I think we can safely replace this with os.getcwd() versus the On Thu, Oct 11, 2012 at 12:41 PM, tbielawa notifications@github.com wrote:
|
It's crazy simpler than that patch, actually. Make setup.py just look at os.getcwd() and not constants.py An application should never run live code from the application to build |
hmm, nm, I think you are correct, it's just about the constant, not yes. |
|
==Translated from Russian:== rm: impossible to delete `rst/*_module.rst': No such file or directory |
The "make rpm" command is failing because of errors on file
ansible / packaging / rpm /ansible.spec
To make it working I had to comment lines 45 and 60.
The text was updated successfully, but these errors were encountered: