-
Notifications
You must be signed in to change notification settings - Fork 2
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
Build does not pack all files #14
Comments
Hi, I didn't push the new release yet...so the problem lays in the old version. I am refactoring nodejs-fixdep and nodejs-symlink-deps (the only two files left)...so I think a new version should be available for testing before this weekend. BTW, |
Thanks! |
@coogor @illuusio @hurricanehrndz Hi, the latest available for testing is at https://build.opensuse.org/project/show/home:MargueriteSu:nodejs you can make your own testing prj, in its
to have the latest nodejs-packaging. NOTE: because the
feel free to open any issue you met... because I don't know your personal projects. I will massively test against the existing ones in devel:languages:nodejs like jscs... Greetings Marguerite |
There's no transfer from old |
Thanks for update.. testing it now and run these problems:
Is nodejs6 current nodejs (Should it be just nodejs) and can't find nodejs-rpm-macros which is nodejs-packaging is suppose but doesn't provide such dependency. |
Hello, there's also nodejs7 in tumbleweed. I asked adamm, the SUSE maintainer for nodejs, he told me those are not co-existentable So it depends on yourself to select the best suitable nodejs version. and maybe also define it in repo's proj file with Prefer. Actually my tool doesn't require any nodejs theoretically. Because it is written in ruby. The only case it requires nodejs will be when you want to build nodejs C bindings (node-gyp). All those stuff (nodejs-devel, npm, gcc-c++, python) are required under that case only. So if you like, I can also fix it the other way. But it will be yourself to manually add such buildrequires when needed. So what do you think? |
but where to find 'nodejs-rpm-macros'? is it a something that doesnt exist or something i need to get somewhere? |
Provides: nodejs-rpm-macros it's currently provided by the nodejs-packaging in home:MargueriteSu:nodejs |
I'm currently testing this for Leap 42.3, and still run into the same issue. |
I have now build against your above repo https://build.opensuse.org/project/show/home:MargueriteSu:nodejs [ 34s] error: Bad exit status from /var/tmp/rpm-tmp.0hTWqB (%prep) |
@coogor Hi, I am back and I will fix it tomorrow |
@coogor looks like you didn't use the generated specfile from node2rpm because your current specfile contains some customizations. then rpmspec gem don't know how to deal with that. but anyway I'll modify the gem to satisfy your current specfile :-) |
You mean the name-version tag in |
you didn't make anything wrong. It's my duty to make the parser strong enough. |
Hi, I made a few commits and now tryton-sao builds. Now the filelist created by nodejs-packaging is located at builddir/tryton-sao.list, so you have to replace |
Excellent, cant wait to test! Current nodejs-packaging in https://build.opensuse.org/package/show/home:MargueriteSu:nodejs/nodejs-packaging does not reflect the change so far? |
those commits have already landed in home:MargueriteSu:nodejs before I comment here:-) |
I checked the builds, but files in /usr/lib/node-modules/tryton-sao still missing :-( |
You didn't update the .json file. it's still version 4.2.0. but you have uploaded 4.2.6 source. node2rpm is json based, so if it can't find 4.2.0, it will not copy anything. maybe I should raise an error for this case. and please repackage |
Ah, thanks for the hint! Did not have the .json file on he radar.... [ 20s] + cd /home/abuild/rpmbuild/BUILD |
it was caused by my bower-related codes. after I fixed it, another error jumped. It turned out to be the directory hierarchy incompatibility between the old 'bower_components.tar.gz' and the new '.tgz' So I added some backward compatibility for node2rpm today. But finally I realized you didnt change the obs working directory from the old nodejs-packaging to the new one. Maybe you just uploaded newer 'tryton-sao-%{version}.tgz' and left other things unchanged. It will fail for sure. Because bower_components' content, that is the modules in bower.json, also changed among releases. So I just ran 'node2rpm -m tryton-sao -v 4.2.6' for you (see my obs SR) Now it builds and succeeds. I recommend you to do such things for 3.8, 4.0 and 4.4. And 3 jobs left for me to prevent such tragedies from happening in the future:-)
|
The above jobs mentioned are done in [rubygem-node2rpm](https://github.com/marguerite/ruby gen-node2rpm), closed #14. If you meet an error like this:
It means your bower_components.tgz is not consistent. The components themselves may include a bower.json that brings new bower components, which was not handled by node2rpm before. So you have to run 'node2rpm -m tryton -v 4.2.6' with latest node2rpm or put a rightly versioned 'tether' into bower_components.tgz by yourself. There is a similar check for the generated json too. It compares the package names and versions in the json with the sources. It will be helpful when you forget to upload new sources. If everything is correct, you will just see 'Passed: module' messages. Marguerite |
Did not change the spec file on OBS, but recently I noticed that the rpm contains only directories bower_components and node_modules, but not the other files (index.html etc) of the source package.
Affects all builds of tryton-sao
The text was updated successfully, but these errors were encountered: