People,
A while ago I posted a note on the Devise forum asking if anyone was going to build an RPM for Fedora but didn't get any responses at all - no-one even viewed the post! What happens with Gems in this category? Am I supposed to do anything? Add a request somewhere? Use the Gem instead of an RPM while I wait for someone to do the work for creating the RPM? Should I bite the bullet and see how to produce the RPM myself?
Regards,
Phil.
Dne 25.2.2013 22:01, Philip Rhoades napsal(a):
People,
A while ago I posted a note on the Devise forum asking if anyone was going to build an RPM for Fedora but didn't get any responses at all - no-one even viewed the post! What happens with Gems in this category? Am I supposed to do anything? Add a request somewhere?
This will get probably the same attention as the post on Devise forum. Sorry.
Use the Gem instead of an RPM while I wait for someone to do the work for creating the RPM?
This is definitely option.
Should I bite the bullet and see how to produce the RPM myself?
And this is the best possibility. You can start here [1] and I'll be happy to sponsor you.
Vít
[1] https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
I'm no expert here but I'd like to add my two cents.
http://isitfedoraruby.com is a project started last summer. It is intended to give an overview of the progress of gem->rpm conversions on fedora.
We used to have a section called Most Wanted Gems whose purpose is exactly to provide a way for people to vote for gems they want, but haven't been converted into rpms yet. Hopefully with more votes, developers will pay more attention to those highly wanted gems.
(Well, at least this is what we've planned initially.)
Although the website is still pretty much in progress, and unfortunately it only tracks gems with rpms currently (instead of the whole bunch from rubygems.org), maybe we will roll out the feature soon if people do find that useful.
Zuhao
On Tuesday, 26 February, 2013 at 4:42 PM, Vít Ondruch wrote:
Dne 25.2.2013 22:01, Philip Rhoades napsal(a):
People,
A while ago I posted a note on the Devise forum asking if anyone was going to build an RPM for Fedora but didn't get any responses at all - no-one even viewed the post! What happens with Gems in this category? Am I supposed to do anything? Add a request somewhere?
This will get probably the same attention as the post on Devise forum. Sorry.
Use the Gem instead of an RPM while I wait for someone to do the work for creating the RPM?
This is definitely option.
Should I bite the bullet and see how to produce the RPM myself?
And this is the best possibility. You can start here [1] and I'll be happy to sponsor you.
Vít
[1] https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
ruby-sig mailing list ruby-sig@lists.fedoraproject.org (mailto:ruby-sig@lists.fedoraproject.org) https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
People,
Thanks to the people who responded - see inline comments:
On 2013-02-26 21:14, Nathan Wan wrote:
I'm no expert here but I'd like to add my two cents.
http://isitfedoraruby.com [3] is a project started last summer. It is intended to give an overview of the progress of gem->rpm conversions on fedora.
Nice site!
We used to have a section called Most Wanted Gems whose purpose is exactly to provide a way for people to vote for gems they want, but haven't been converted into rpms yet. Hopefully with more votes, developers will pay more attention to those highly wanted gems.
(Well, at least this is what we've planned initially.)
That table is still there on the home page but how do I add to it?
Although the website is still pretty much in progress, and unfortunately it only tracks gems with rpms currently (instead of the whole bunch from rubygems.org), maybe we will roll out the feature soon if people do find that useful.
I think it is a great idea for the whole Gem=>RPM project.
I don't have an immediate need for "devise" at the moment but I'm sure I will have the need in a few months time - I will attempt the conversion process (maybe on a simple gem first?) after I have moved house in a month or so - but the process does look cumbersome - maybe it is not as bad as it looks?
Regards,
Phil.
Zuhao
On Tuesday, 26 February, 2013 at 4:42 PM, Vít Ondruch wrote:
Dne 25.2.2013 22:01, Philip Rhoades napsal(a):
People,
A while ago I posted a note on the Devise forum asking if anyone was going to build an RPM for Fedora but didn't get any responses at all
no-one even viewed the post! What happens with Gems in this category? Am I supposed to do anything? Add a request somewhere?
This will get probably the same attention as the post on Devise forum. Sorry.
Use the Gem instead of an RPM while I wait for someone to do the work for creating the RPM?
This is definitely option.
Should I bite the bullet and see how to produc
/blockquote>
And this is the best possibility. You can
] and I'll be happy to sponsor you.
Vít
[1] https://fedoraproject.org/wiki/Join_the_package_collection_maintainers [1]
ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig [2]
Links:
[1] https://fedoraproject.org/wiki/Join_the_package_collection_maintainers [2] https://admin.fedoraproject.org/mailman/listinfo/ruby-sig [3] http://isitfedoraruby.com
ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
On 02/26/2013 11:21 AM, Philip Rhoades wrote:
People,
Thanks to the people who responded - see inline comments:
On 2013-02-26 21:14, Nathan Wan wrote:
I'm no expert here but I'd like to add my two cents.
http://isitfedoraruby.com [3] is a project started last summer. It is intended to give an overview of the progress of gem->rpm conversions on fedora.
Nice site!
We used to have a section called Most Wanted Gems whose purpose is exactly to provide a way for people to vote for gems they want, but haven't been converted into rpms yet. Hopefully with more votes, developers will pay more attention to those highly wanted gems.
(Well, at least this is what we've planned initially.)
That table is still there on the home page but how do I add to it?
Although the website is still pretty much in progress, and unfortunately it only tracks gems with rpms currently (instead of the whole bunch from rubygems.org), maybe we will roll out the feature soon if people do find that useful.
I think it is a great idea for the whole Gem=>RPM project.
I don't have an immediate need for "devise" at the moment but I'm sure I will have the need in a few months time - I will attempt the conversion process (maybe on a simple gem first?) after I have moved house in a month or so - but the process does look cumbersome - maybe it is not as bad as it looks?
Regards,
Phil.
Yes I'd personally love to see this happen. Stuff like automating the conversion on a gem being published, setting up hosted yum repos, and deeper gem inspection so as to pull the maximum that we can from a gem package. It's a tricky project but is sorely needed / would be well used.
If you need any help getting started w/ the isitfedoraruby codebase just ask, be sure to also check out gem2rpm. [1]
-Mo
Vít,
On 2013-02-26 19:42, Vít Ondruch wrote:
Dne 25.2.2013 22:01, Philip Rhoades napsal(a):
People,
A while ago I posted a note on the Devise forum asking if anyone was going to build an RPM for Fedora but didn't get any responses at all - no-one even viewed the post! What happens with Gems in this category? Am I supposed to do anything? Add a request somewhere?
This will get probably the same attention as the post on Devise forum. Sorry.
Use the Gem instead of an RPM while I wait for someone to do the work for creating the RPM?
This is definitely option.
Should I bite the bullet and see how to produce the RPM myself?
And this is the best possibility. You can start here [1] and I'll be happy to sponsor you.
OK, I bit the bullet - after having to sort out a problem with installing the dev tools on F18, I got gem2rpm to produce the spec file for devise and following the instructions at:
http://fedoraproject.org/wiki/How_to_create_an_RPM_package
produced a lot of stuff but no SRPMS or RPMS - the issue seems to be:
error: Installed (but unpackaged) file(s) found: /usr/share/gems/gems/devise-2.2.4/.gitignore /usr/share/gems/gems/devise-2.2.4/.travis.yml /usr/share/gems/gems/devise-2.2.4/.yardopts /usr/share/gems/gems/devise-2.2.4/CHANGELOG.rdoc /usr/share/gems/gems/devise-2.2.4/CONTRIBUTING.md /usr/share/gems/gems/devise-2.2.4/Gemfile /usr/share/gems/gems/devise-2.2.4/Gemfile.lock /usr/share/gems/gems/devise-2.2.4/MIT-LICENSE /usr/share/gems/gems/devise-2.2.4/README.md /usr/share/gems/gems/devise-2.2.4/Rakefile /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb . . RPM build errors: Installed (but unpackaged) file(s) found: /usr/share/gems/gems/devise-2.2.4/.gitignore /usr/share/gems/gems/devise-2.2.4/.travis.yml /usr/share/gems/gems/devise-2.2.4/.yardopts /usr/share/gems/gems/devise-2.2.4/CHANGELOG.rdoc /usr/share/gems/gems/devise-2.2.4/CONTRIBUTING.md /usr/share/gems/gems/devise-2.2.4/Gemfile /usr/share/gems/gems/devise-2.2.4/Gemfile.lock /usr/share/gems/gems/devise-2.2.4/MIT-LICENSE /usr/share/gems/gems/devise-2.2.4/README.md /usr/share/gems/gems/devise-2.2.4/Rakefile
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb . .
Where to from here?
Thanks,
Phil. -- Philip Rhoades
GPO Box 3411 Sydney NSW 2001 Australia E-mail: phil@pricom.com.au
Hey Philip,
On 06/29/2013 01:09 AM, Philip Rhoades wrote:
Vít,
On 2013-02-26 19:42, Vít Ondruch wrote:
Dne 25.2.2013 22:01, Philip Rhoades napsal(a):
People,
A while ago I posted a note on the Devise forum asking if anyone was going to build an RPM for Fedora but didn't get any responses at all
- no-one even viewed the post! What happens with Gems in this
category? Am I supposed to do anything? Add a request somewhere?
This will get probably the same attention as the post on Devise forum. Sorry.
Use the Gem instead of an RPM while I wait for someone to do the work for creating the RPM?
This is definitely option.
The devise gem is on the TODO list of the packaging process about GitLab. I was planning to get it done this week. I see that one of its dependencies (orm_adapter) is not yet packaged for Fedora so, you'll have to package it too. If you could wait one day or two that's fine otherwise this is a nice chance to start and learn about the packaging process :)
Should I bite the bullet and see how to produce the RPM myself?
And this is the best possibility. You can start here [1] and I'll be happy to sponsor you.
OK, I bit the bullet - after having to sort out a problem with installing the dev tools on F18, I got gem2rpm to produce the spec file for devise and following the instructions at:
http://fedoraproject.org/wiki/How_to_create_an_RPM_package
produced a lot of stuff but no SRPMS or RPMS - the issue seems to be:
error: Installed (but unpackaged) file(s) found: /usr/share/gems/gems/devise-2.2.4/.gitignore /usr/share/gems/gems/devise-2.2.4/.travis.yml /usr/share/gems/gems/devise-2.2.4/.yardopts /usr/share/gems/gems/devise-2.2.4/CHANGELOG.rdoc /usr/share/gems/gems/devise-2.2.4/CONTRIBUTING.md /usr/share/gems/gems/devise-2.2.4/Gemfile /usr/share/gems/gems/devise-2.2.4/Gemfile.lock /usr/share/gems/gems/devise-2.2.4/MIT-LICENSE /usr/share/gems/gems/devise-2.2.4/README.md /usr/share/gems/gems/devise-2.2.4/Rakefile /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb
Now, running gem2rpm you have a nice template to start working on, but it needs further tinkering to get it working.
Here's what I have learned these past months.
After the %prep, %build, %install and %check macros there is one called %files. According to the rpm-guide [0], the %files list indicates to RPM which files on the build system are to be packaged.
On the other hand, the section `%files doc` denotes what the subpackage -doc will include as well. In there you can put everything the gem owns except for the lib/ dir and the LICENSE l(icense should always be declared in `%files` macro). But again that is not a strict rule and is under the packager's discretion if he wants to include files like the Rakefile/Gemfile. These should not be marked as documentation files (%doc).
So, in your case these sections would be like:
----------
%files %dir %{gem_instdir} %{gem_libdir} %{gem_spec} %doc %{gem_instdir}/MIT-LICENSE %exclude %{gem_cache} %exclude %{gem_instdir}/.*
%files doc %doc %{gem_docdir} %doc %{gem_instdir}/CHANGELOG.rdoc %doc %{gem_instdir}/CONTRIBUTING.md %doc %{gem_instdir}/README.md %{gem_instdir}/Rakefile %{gem_instdir}/Gemfile %{gem_instdir}/Gemfile.lock %{gem_instdir}/gemfiles/ %{gem_instdir}/test/ %{gem_instdir}/%{gem_name}.gemspec
----------
But again, maybe devise should be packaged as an app[1] since it contains an app folder. Unfortunately I haven't packaged an app before to know how to proceed from here. Someone with greater experience care to elaborate on that?
[0] http://www.rpm.org/max-rpm/s1-rpm-inside-files-list.html [1] https://fedoraproject.org/wiki/Packaging:Ruby#Applications
Axilleas,
See inline comments:
On 2013-06-30 20:03, Axilleas Pi wrote:
Hey Philip,
On 06/29/2013 01:09 AM, Philip Rhoades wrote:
Vít,
On 2013-02-26 19:42, Vít Ondruch wrote:
Dne 25.2.2013 22:01, Philip Rhoades napsal(a):
People,
A while ago I posted a note on the Devise forum asking if anyone was going to build an RPM for Fedora but didn't get any responses at all
- no-one even viewed the post! What happens with Gems in this
category? Am I supposed to do anything? Add a request somewhere?
This will get probably the same attention as the post on Devise forum. Sorry.
Use the Gem instead of an RPM while I wait for someone to do the work for creating the RPM?
This is definitely option.
The devise gem is on the TODO list of the packaging process about GitLab. I was planning to get it done this week. I see that one of its dependencies (orm_adapter) is not yet packaged for Fedora so, you'll have to package it too. If you could wait one day or two that's fine otherwise this is a nice chance to start and learn about the packaging process :)
It would be nice to make some progress now that I have started the exercise . . but in the end, if someone can get it going (me or someone else), I will be happy . .
Should I bite the bullet and see how to produce the RPM myself?
And this is the best possibility. You can start here [1] and I'll be happy to sponsor you.
OK, I bit the bullet - after having to sort out a problem with installing the dev tools on F18, I got gem2rpm to produce the spec file for devise and following the instructions at:
http://fedoraproject.org/wiki/How_to_create_an_RPM_package
produced a lot of stuff but no SRPMS or RPMS - the issue seems to be:
error: Installed (but unpackaged) file(s) found: /usr/share/gems/gems/devise-2.2.4/.gitignore /usr/share/gems/gems/devise-2.2.4/.travis.yml /usr/share/gems/gems/devise-2.2.4/.yardopts /usr/share/gems/gems/devise-2.2.4/CHANGELOG.rdoc /usr/share/gems/gems/devise-2.2.4/CONTRIBUTING.md /usr/share/gems/gems/devise-2.2.4/Gemfile /usr/share/gems/gems/devise-2.2.4/Gemfile.lock /usr/share/gems/gems/devise-2.2.4/MIT-LICENSE /usr/share/gems/gems/devise-2.2.4/README.md /usr/share/gems/gems/devise-2.2.4/Rakefile /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb
Now, running gem2rpm you have a nice template to start working on, but it needs further tinkering to get it working.
Here's what I have learned these past months.
After the %prep, %build, %install and %check macros there is one called %files. According to the rpm-guide [0], the %files list indicates to RPM which files on the build system are to be packaged.
On the other hand, the section `%files doc` denotes what the subpackage -doc will include as well. In there you can put everything the gem owns except for the lib/ dir and the LICENSE l(icense should always be declared in `%files` macro). But again that is not a strict rule and is under the packager's discretion if he wants to include files like the Rakefile/Gemfile. These should not be marked as documentation files (%doc).
So, in your case these sections would be like:
%files %dir %{gem_instdir} %{gem_libdir} %{gem_spec} %doc %{gem_instdir}/MIT-LICENSE %exclude %{gem_cache} %exclude %{gem_instdir}/.*
%files doc %doc %{gem_docdir} %doc %{gem_instdir}/CHANGELOG.rdoc %doc %{gem_instdir}/CONTRIBUTING.md %doc %{gem_instdir}/README.md %{gem_instdir}/Rakefile %{gem_instdir}/Gemfile %{gem_instdir}/Gemfile.lock %{gem_instdir}/gemfiles/ %{gem_instdir}/test/ %{gem_instdir}/%{gem_name}.gemspec
But again, maybe devise should be packaged as an app[1] since it contains an app folder. Unfortunately I haven't packaged an app before to know how to proceed from here. Someone with greater experience care to elaborate on that?
I tried changing the sections as you suggested but the errors are still the same . .
Thanks,
Phil.
Dne 30.6.2013 17:17, Philip Rhoades napsal(a):
I tried changing the sections as you suggested but the errors are still the same . .
Have you rebuild your SRPM actually? That must works. Show us your SRPM.
Vít
Vít,
On 2013-07-01 16:52, Vít Ondruch wrote:
Dne 30.6.2013 17:17, Philip Rhoades napsal(a):
I tried changing the sections as you suggested but the errors are still the same . .
Have you rebuild your SRPM actually? That must works. Show us your SRPM.
It seems that is not getting built either:
BUILD/: total 12 drwxrwxr-x 3 makerpm makerpm 4096 Jun 29 07:49 . drwxrwxr-x 8 makerpm makerpm 4096 Jun 29 07:48 .. drwxr-xr-x 8 makerpm makerpm 4096 Jul 1 01:11 devise-2.2.4
BUILDROOT/: total 12 drwxr-xr-x 3 makerpm makerpm 4096 Jul 1 01:11 . drwxrwxr-x 8 makerpm makerpm 4096 Jun 29 07:48 .. drwxr-xr-x 3 makerpm makerpm 4096 Jul 1 01:11 rubygem-devise-2.2.4-1.fc18.x86_64
RPMS/: total 8 drwxrwxr-x 2 makerpm makerpm 4096 Jun 29 07:42 . drwxrwxr-x 8 makerpm makerpm 4096 Jun 29 07:48 ..
SOURCES/: total 156 drwxrwxr-x 2 makerpm makerpm 4096 Jun 29 07:50 . drwxrwxr-x 8 makerpm makerpm 4096 Jun 29 07:48 .. -rw-rw-r-- 1 makerpm makerpm 148480 Jun 24 19:28 devise-2.2.4.gem
SPECS/: total 20 drwxrwxr-x 2 makerpm makerpm 4096 Jul 1 01:12 . drwxrwxr-x 8 makerpm makerpm 4096 Jun 29 07:48 .. -rw-rw-r-- 1 makerpm makerpm 6545 Jul 1 01:11 rpmbuild_rubygem-devise.out -rw-rw-r-- 1 makerpm makerpm 2307 Jul 1 01:06 rubygem-devise.spec
SRPMS/: total 8 drwxrwxr-x 2 makerpm makerpm 4096 Jun 29 07:42 . drwxrwxr-x 8 makerpm makerpm 4096 Jun 29 07:48 ..
Thanks,
Phil.
Dne 2.7.2013 00:27, Philip Rhoades napsal(a):
Vít,
On 2013-07-01 16:52, Vít Ondruch wrote:
Dne 30.6.2013 17:17, Philip Rhoades napsal(a):
I tried changing the sections as you suggested but the errors are still the same . .
Have you rebuild your SRPM actually? That must works. Show us your SRPM.
It seems that is not getting built either:
You can build SRPM from .spec file using "fedpkg --dist f20 srpm".
Vít
Vít,
On 2013-07-02 15:47, Vít Ondruch wrote:
Dne 2.7.2013 00:27, Philip Rhoades napsal(a):
Vít,
On 2013-07-01 16:52, Vít Ondruch wrote:
Dne 30.6.2013 17:17, Philip Rhoades napsal(a):
I tried changing the sections as you suggested but the errors are still the same . .
Have you rebuild your SRPM actually? That must works. Show us your SRPM.
It seems that is not getting built either:
You can build SRPM from .spec file using "fedpkg --dist f20 srpm".
Whatever dir I execute that in, I get something like:
Could not execute srpm: dirx is not a valid repo: [Errno 2] No such file or directory: 'dirx/sources'
BTW, that should be f18 in my case I think.
Since the gem file has a tar.gz format, I thought that should go in the SOURCES dir - should I actually find the devise tar.gz file and put that there?
Thanks,
Phil.
Dne 2.7.2013 18:48, Philip Rhoades napsal(a):
Vít,
On 2013-07-02 15:47, Vít Ondruch wrote:
Dne 2.7.2013 00:27, Philip Rhoades napsal(a):
Vít,
On 2013-07-01 16:52, Vít Ondruch wrote:
Dne 30.6.2013 17:17, Philip Rhoades napsal(a):
I tried changing the sections as you suggested but the errors are still the same . .
Have you rebuild your SRPM actually? That must works. Show us your SRPM.
It seems that is not getting built either:
You can build SRPM from .spec file using "fedpkg --dist f20 srpm".
Whatever dir I execute that in, I get something like:
Could not execute srpm: dirx is not a valid repo: [Errno 2] No such file or directory: 'dirx/sources'
It complains you don't have the "sources" file in your directory. "touch sources" should fix this issue.
BTW, that should be f18 in my case I think.
Since the gem file has a tar.gz format, I thought that should go in the SOURCES dir - should I actually find the devise tar.gz file and put that there?
fedpkg is looking for sources in the same directory as the .spec file, no SOURCES directory is needed.
BTW gem with .tar.gz? Looks extraordinary. I would not recommend to follow this path.
Vít
Vít,
On 2013-07-04 15:31, Vít Ondruch wrote:
Dne 2.7.2013 18:48, Philip Rhoades napsal(a):
Vít,
On 2013-07-02 15:47, Vít Ondruch wrote:
Dne 2.7.2013 00:27, Philip Rhoades napsal(a):
Vít,
On 2013-07-01 16:52, Vít Ondruch wrote:
Dne 30.6.2013 17:17, Philip Rhoades napsal(a):
I tried changing the sections as you suggested but the errors are still the same . .
Have you rebuild your SRPM actually? That must works. Show us your SRPM.
It seems that is not getting built either:
You can build SRPM from .spec file using "fedpkg --dist f20 srpm".
Whatever dir I execute that in, I get something like:
Could not execute srpm: dirx is not a valid repo: [Errno 2] No such file or directory: 'dirx/sources'
It complains you don't have the "sources" file in your directory. "touch sources" should fix this issue.
OK, the src.rpm now builds OK.
BTW, that should be f18 in my case I think.
Since the gem file has a tar.gz format, I thought that should go in the SOURCES dir - should I actually find the devise tar.gz file and put that there?
fedpkg is looking for sources in the same directory as the .spec file, no SOURCES directory is needed.
Seems confusing - why are unnecessary dirs being created?
BTW gem with .tar.gz? Looks extraordinary. I would not recommend to follow this path.
But with:
rpmbuild -ba rubygem-devise.spec
I still get the original problems:
Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/makerpm/rpmbuild/BUILDROOT/rubygem-devise-2.2.4-1.fc18.x86_64 error: Installed (but unpackaged) file(s) found:
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/omniauth_callbacks_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/passwords_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/registrations_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/sessions_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/unlocks_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise_controller.rb /usr/share/gems/gems/devise-2.2.4/app/helpers/devise_helper.rb /usr/share/gems/gems/devise-2.2.4/app/mailers/devise/mailer.rb /usr/share/gems/gems/devise-2.2.4/app/views/devise/_links.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/confirmations/new.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/confirmation_instructions.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/reset_password_instructions.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/unlock_instructions.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/passwords/edit.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/passwords/new.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/registrations/edit.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/registrations/new.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/sessions/new.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/shared/_links.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/unlocks/new.html.erb /usr/share/gems/gems/devise-2.2.4/config/locales/en.yml /usr/share/gems/gems/devise-2.2.4/devise.png
RPM build errors: Installed (but unpackaged) file(s) found:
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/omniauth_callbacks_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/passwords_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/registrations_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/sessions_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/unlocks_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise_controller.rb /usr/share/gems/gems/devise-2.2.4/app/helpers/devise_helper.rb /usr/share/gems/gems/devise-2.2.4/app/mailers/devise/mailer.rb /usr/share/gems/gems/devise-2.2.4/app/views/devise/_links.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/confirmations/new.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/confirmation_instructions.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/reset_password_instructions.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/unlock_instructions.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/passwords/edit.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/passwords/new.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/registrations/edit.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/registrations/new.html.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/sessions/new.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/shared/_links.erb
/usr/share/gems/gems/devise-2.2.4/app/views/devise/unlocks/new.html.erb /usr/share/gems/gems/devise-2.2.4/config/locales/en.yml /usr/share/gems/gems/devise-2.2.4/devise.png
Thanks,
Phil.
On 07/04/2013 09:50 PM, Philip Rhoades wrote:
Vít,
On 2013-07-04 15:31, Vít Ondruch wrote:
Dne 2.7.2013 18:48, Philip Rhoades napsal(a):
Vít,
On 2013-07-02 15:47, Vít Ondruch wrote:
Dne 2.7.2013 00:27, Philip Rhoades napsal(a):
Vít,
On 2013-07-01 16:52, Vít Ondruch wrote:
Dne 30.6.2013 17:17, Philip Rhoades napsal(a): > > > I tried changing the sections as you suggested but the errors are > still the same . .
Have you rebuild your SRPM actually? That must works. Show us your SRPM.
It seems that is not getting built either:
You can build SRPM from .spec file using "fedpkg --dist f20 srpm".
Whatever dir I execute that in, I get something like:
Could not execute srpm: dirx is not a valid repo: [Errno 2] No such file or directory: 'dirx/sources'
It complains you don't have the "sources" file in your directory. "touch sources" should fix this issue.
OK, the src.rpm now builds OK.
BTW, that should be f18 in my case I think.
Since the gem file has a tar.gz format, I thought that should go in the SOURCES dir - should I actually find the devise tar.gz file and put that there?
fedpkg is looking for sources in the same directory as the .spec file, no SOURCES directory is needed.
Seems confusing - why are unnecessary dirs being created?
If you followed this guide [0], then when you ran rpmdev-setuptree, it should have created the ~/rpmbuild directory and a set of subdirectories. One of them is SOURCES. With this structure you use rpmbuild. This is one tool of the 'many' you can use to build a package. fedpkg is a different one, which I am not familiar with yet.
But with:
rpmbuild -ba rubygem-devise.spec
I still get the original problems:
Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/makerpm/rpmbuild/BUILDROOT/rubygem-devise-2.2.4-1.fc18.x86_64 error: Installed (but unpackaged) file(s) found: /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/omniauth_callbacks_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/passwords_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/registrations_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/sessions_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/unlocks_controller.rb
...snip
Can you please post somewhere your spec file? Mine is here[1] so that you can compare.
[0] https://fedoraproject.org/wiki/How_to_create_an_RPM_package#Preparing_your_s... [1] http://axilleas.fedorapeople.org/pkgs/rubygem-devise/rubygem-devise.spec
Axilleas,
On 2013-07-05 07:19, Axilleas Pipinellis wrote:
But with:
rpmbuild -ba rubygem-devise.spec
I still get the original problems:
Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/makerpm/rpmbuild/BUILDROOT/rubygem-devise-2.2.4-1.fc18.x86_64 error: Installed (but unpackaged) file(s) found: /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/omniauth_callbacks_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/passwords_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/registrations_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/sessions_controller.rb
/usr/share/gems/gems/devise-2.2.4/app/controllers/devise/unlocks_controller.rb
...snip
Can you please post somewhere your spec file? Mine is here[1] so that you can compare.
Although the Gem RPMS you have produced seem to be working fine, now that I have started this exercise I will persist with trying to make the Devise RPM . .
I have downloaded your spec file so I can see how far I get with that - after some minor editing, it seems the next requirement is to install gems to fulfill:
BuildRequires: rubygem(minitest) BuildRequires: rubygem(activerecord) BuildRequires: rubygem(rake) BuildRequires: rubygem(multi_json)
?
Thanks,
Phil.
On 07/05/2013 09:38 PM, Philip Rhoades wrote:
Although the Gem RPMS you have produced seem to be working fine, now that I have started this exercise I will persist with trying to make the Devise RPM . .
I have downloaded your spec file so I can see how far I get with that
- after some minor editing, it seems the next requirement is to
install gems to fulfill:
BuildRequires: rubygem(minitest) BuildRequires: rubygem(activerecord) BuildRequires: rubygem(rake) BuildRequires: rubygem(multi_json)
?
Thanks,
Phil.
Yes, most of BuildRequires are needed for the tests to run (at least that's what I have encountered so far). If you run rpmbuild on the spec file and a dependency of a BuildRequires is not met, it will halt with a message like:
error: Failed build dependencies: rubygem(activerecord) is needed by rubygem-devise-2.2.4-1.fc19.noarch rubygem(multi_json) is needed by rubygem-devise-2.2.4-1.fc19.noarch
So, the next step would be to install what you are missing.
Dne 4.7.2013 20:50, Philip Rhoades napsal(a):
BTW, that should be f18 in my case I think.
Since the gem file has a tar.gz format, I thought that should go in the SOURCES dir - should I actually find the devise tar.gz file and put that there?
fedpkg is looking for sources in the same directory as the .spec file, no SOURCES directory is needed.
Seems confusing - why are unnecessary dirs being created?
Well, if you are using rpmbuild, then they are necessary.
Nevertheless, I don't suggest to use rpmbuild directly. I always suggest to use mock [1]. Mock allows you to build packages isolated from your system and it may prevent issues such as missing BuildRequires, etc. fedpkg is wrapper above rpmbuild, git, etc and it allows some nice tricks, such checkout of package sources from Fedora's dist git, building SRPM from this sources, etc.
BTW gem with .tar.gz? Looks extraordinary. I would not recommend to follow this path.
But with:
rpmbuild -ba rubygem-devise.spec
I still get the original problems:
Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/makerpm/rpmbuild/BUILDROOT/rubygem-devise-2.2.4-1.fc18.x86_64 error: Installed (but unpackaged) file(s) found: /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/omniauth_callbacks_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/passwords_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/registrations_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/sessions_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/unlocks_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise_controller.rb /usr/share/gems/gems/devise-2.2.4/app/helpers/devise_helper.rb /usr/share/gems/gems/devise-2.2.4/app/mailers/devise/mailer.rb /usr/share/gems/gems/devise-2.2.4/app/views/devise/_links.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/confirmations/new.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/confirmation_instructions.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/reset_password_instructions.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/unlock_instructions.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/passwords/edit.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/passwords/new.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/registrations/edit.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/registrations/new.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/sessions/new.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/shared/_links.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/unlocks/new.html.erb /usr/share/gems/gems/devise-2.2.4/config/locales/en.yml /usr/share/gems/gems/devise-2.2.4/devise.png
RPM build errors: Installed (but unpackaged) file(s) found: /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/omniauth_callbacks_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/passwords_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/registrations_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/sessions_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/unlocks_controller.rb /usr/share/gems/gems/devise-2.2.4/app/controllers/devise_controller.rb /usr/share/gems/gems/devise-2.2.4/app/helpers/devise_helper.rb /usr/share/gems/gems/devise-2.2.4/app/mailers/devise/mailer.rb /usr/share/gems/gems/devise-2.2.4/app/views/devise/_links.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/confirmations/new.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/confirmation_instructions.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/reset_password_instructions.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/mailer/unlock_instructions.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/passwords/edit.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/passwords/new.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/registrations/edit.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/registrations/new.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/sessions/new.html.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/shared/_links.erb /usr/share/gems/gems/devise-2.2.4/app/views/devise/unlocks/new.html.erb /usr/share/gems/gems/devise-2.2.4/config/locales/en.yml /usr/share/gems/gems/devise-2.2.4/devise.png
Thanks,
You have to fix your %files section, but unless you provide us with your .spec file or better with your SRPM, it is hard to guess what is wrong.
Vít
Dne 30.6.2013 12:03, Axilleas Pi napsal(a):
Hey Philip,
On 06/29/2013 01:09 AM, Philip Rhoades wrote:
Vít,
On 2013-02-26 19:42, Vít Ondruch wrote:
Dne 25.2.2013 22:01, Philip Rhoades napsal(a):
People,
A while ago I posted a note on the Devise forum asking if anyone was going to build an RPM for Fedora but didn't get any responses at all
- no-one even viewed the post! What happens with Gems in this
category? Am I supposed to do anything? Add a request somewhere?
This will get probably the same attention as the post on Devise forum. Sorry.
Use the Gem instead of an RPM while I wait for someone to do the work for creating the RPM?
This is definitely option.
The devise gem is on the TODO list of the packaging process about GitLab. I was planning to get it done this week. I see that one of its dependencies (orm_adapter) is not yet packaged for Fedora so, you'll have to package it too. If you could wait one day or two that's fine otherwise this is a nice chance to start and learn about the packaging process :)
Should I bite the bullet and see how to produce the RPM myself?
And this is the best possibility. You can start here [1] and I'll be happy to sponsor you.
OK, I bit the bullet - after having to sort out a problem with installing the dev tools on F18, I got gem2rpm to produce the spec file for devise and following the instructions at:
http://fedoraproject.org/wiki/How_to_create_an_RPM_package
produced a lot of stuff but no SRPMS or RPMS - the issue seems to be:
error: Installed (but unpackaged) file(s) found: /usr/share/gems/gems/devise-2.2.4/.gitignore /usr/share/gems/gems/devise-2.2.4/.travis.yml /usr/share/gems/gems/devise-2.2.4/.yardopts /usr/share/gems/gems/devise-2.2.4/CHANGELOG.rdoc /usr/share/gems/gems/devise-2.2.4/CONTRIBUTING.md /usr/share/gems/gems/devise-2.2.4/Gemfile /usr/share/gems/gems/devise-2.2.4/Gemfile.lock /usr/share/gems/gems/devise-2.2.4/MIT-LICENSE /usr/share/gems/gems/devise-2.2.4/README.md /usr/share/gems/gems/devise-2.2.4/Rakefile /usr/share/gems/gems/devise-2.2.4/app/controllers/devise/confirmations_controller.rb
Now, running gem2rpm you have a nice template to start working on, but it needs further tinkering to get it working.
Here's what I have learned these past months.
After the %prep, %build, %install and %check macros there is one called %files. According to the rpm-guide [0], the %files list indicates to RPM which files on the build system are to be packaged.
On the other hand, the section `%files doc` denotes what the subpackage -doc will include as well. In there you can put everything the gem owns except for the lib/ dir and the LICENSE l(icense should always be declared in `%files` macro). But again that is not a strict rule and is under the packager's discretion if he wants to include files like the Rakefile/Gemfile. These should not be marked as documentation files (%doc).
So, in your case these sections would be like:
%files %dir %{gem_instdir} %{gem_libdir} %{gem_spec} %doc %{gem_instdir}/MIT-LICENSE %exclude %{gem_cache} %exclude %{gem_instdir}/.*
%files doc %doc %{gem_docdir} %doc %{gem_instdir}/CHANGELOG.rdoc %doc %{gem_instdir}/CONTRIBUTING.md %doc %{gem_instdir}/README.md %{gem_instdir}/Rakefile %{gem_instdir}/Gemfile %{gem_instdir}/Gemfile.lock %{gem_instdir}/gemfiles/ %{gem_instdir}/test/ %{gem_instdir}/%{gem_name}.gemspec
That is perfect.
But again, maybe devise should be packaged as an app[1] since it contains an app folder.
No, definitely not. Application has nothing to do with app folder. Not sure what is app folder good for in Devise, but it looks to be as a Rails Engine or something.
Vít
On Tue, Feb 26, 2013 at 08:01:44AM +1100, Philip Rhoades wrote:
People,
A while ago I posted a note on the Devise forum asking if anyone was going to build an RPM for Fedora but didn't get any responses at all
- no-one even viewed the post! What happens with Gems in this
category? Am I supposed to do anything? Add a request somewhere? Use the Gem instead of an RPM while I wait for someone to do the work for creating the RPM? Should I bite the bullet and see how to produce the RPM myself?
Yes.
I won't speak for others, but will say that I only package gems that I personally find a need for and which aren't already present in Fedora. If you have a need for this package in Fedora, perhaps you could take the plunge and join us as a package maintainer and manage that package for Fedora?
ruby-sig@lists.fedoraproject.org
-
Achilleas Pipinellis -
Darryl L. Pierce -
Mo Morsi -
Nathan Wan -
Philip Rhoades -
Vít Ondruch