Vit, > > I don't own any packages of anything. > > I have never used the Fedora Koji system for anything but I am versed in > Koji usage b/c I have my own. Is account perms and creation synced with the > FeSCO account I created a while back? i.e. can I do scratch builds? But if the > build works in mock, there's a high probability it will work in Koji but every > now and then, that's not true. > > Hmm, not 100% sure if you can do scratch builds without being sponsored > as a package. Nevertheless, I am attaching my mock config I am using. >
The mock config is a good start but how would I feed dependencies into those repositories without creating my own repository somewhere? I have been playing around with COPR of late to build GNOME 3.12 for Fedora 19. Do you think COPR be used for this process? Also, I could put off worrying about this until I come across packages which have these dependencies. > > > > Also, you are missing my favorite: bundler. You'll need updated Thor and > rpsec 3.0.0.beta2 for it to pass its tests. > > Bundler has no binary extension, therefore it is not on the list. But > there might be some updates needed. Ah, OK that explains a lot, ext's only in the etherpad/PiratePad list. Let's take JSON for instance. You have JSON 1.7.7 listed in etherpad/PiratePad but there's newer versions (1.8.1). As part of this process, do want updates? Or just updates to make things (test suites) run for the combination of Ruby/RubyGems/gem targeting Fedora 21? If you'd update JSON, you'd update json_pure and multi_json. Are those included in this process? Or is the goal to get what's in that list built against Ruby 2.1.1 / RubyGems 2.2.2? /allen ________________________________ Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender. _______________________________________________ ruby-sig mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
