- openSUSE Ruby

[opensuse-ruby] Packaging rails applications for openSUSE
by Nanuk Krinner 03 Aug '12

03 Aug '12

Hi, Currently I try to package a Rails application for openSUSE. I ran into a problem and I wonder how to deal with it. Some Rails applications have their gems with them, which we don't want. We want the gems to be in their own package each. Now comes my problem: My Rails app needs a certain gem, say haml-3.1.2. In d:l:r:e we have haml-3.1.6. Now I could use the newer version from d:l:r:e and differ from upstream, and I would have to do this for almost every single gem the application needs. This would also require a lot of testing if the application doesn't run properly which is not so unlikely when it uses gems it was not designed for. Or I could package haml-3.1.2 and submit it to d:l:r:e. But rubygem.org lists 125 different versions of haml. As a worst case we might end up with 125 different haml packages in d:l:r:e. Or I could create a package that has all the needed gems in its vendor directory. Which is against our packaging policy AFAIK. So, what should I do? Is there a way to make it easier to package Rails applications for openSUSE? The alternative would be to tell the users to get their Rails applications somewhere else. As I understand it this is the consequence of the current policy. Or am I totally wrong? What about the idea of having a separate repository where we allow Rails applications with packaged gems? Regards, Nanuk -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

4 6

[opensuse-ruby] Packaging schema.rb for rails applications
by Josef Reidinger 30 Jul '12

30 Jul '12

Hi, I now face one design issue we have in SLMS. We mark schema.rb as non-config and handle failed write during db:migration. I think that it is not good approach and schema.rb should contain correct state of database. How do you handle such situation? mark schema.rb as config or symlink somewhere in /var/lib? Ignore it? Josef -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

3 2

[opensuse-ruby] Makeup mirror suppliers shared photos with you
by Makeup mirror suppliers 21 Jul '12

21 Jul '12

Dear: We have obtained your name and address from internet search,I know you sell fashion and promotion item,and we are writing to inquire whether you would be willing to establish business relations with us. We have been manufacturing promotion gift for many years now.our main products have makeup mirror,cosmetic brush,hair comb/brush,manicure sets, bottle opener,measuring tape etc.At present we are interested in extending our overseas market and would appreciate your respond. Considering our competitive prices and high quality,we expect to establish a long-term partnership With you. We look forward to your early reply. Thanks Best Regards! ------------------------------------ Ike Sale Manager Ningbo Yinzhou Victy Craft Factory

1 0

Re: [opensuse-ruby] Fwd: [obs submit-request 127033] openSUSE:Factory/puppet-dashboard:, declined by coolo
by Sascha Peilicke 17 Jul '12

17 Jul '12

Hi guys, From what I got from the discussion so far is that shipping bundled gems in-tree instead of using packages seems to help mostly the packager in that he doesn't have to fiddle with all the masses of ever-changing / don't-look-backwards gems du jour. Studio seems to have made their experiences with that, altough I think ~200 bleeding-edge-n-monkey-patching-everything gems are just a maintenance nightmare in any form, be it packages or bundles gems. OBS broke due to behavior changes even in patch-level gem updates. As we don't have the time to look at every commit in every gem, we are rather conservative with introducing new gem dependencies (or updating old ones). As long as we can upstream gem fixes, I see no real problem with bundled gems (besides our packaging policies maybe). But how about SUSE-specific gem patches that are not upstreamable / rejected? Do you branch gems on github and use those instead of upstream ones? What about SUSE-confidential changes, e.g. for SLE (if there are any)? I think this would remain an issue even if zypper would support gems (which would be great). Using packages certainly has an advantage here. @James: How does Studio handle such situations? However, I don't really see anybody except SUSE products actually using (or more precisely 'caring for') packaged gems for the same reasons we struggle with them. The Ruby community just doesn't care and probably never will, enterprise (or 'stable') isn't a fancy word in the webby world. So we should either bribe Ryan Bates to not present fancy new gems anymore or we do just what suits ourselves. Actually, we (as in coolo, adrian & me) only touch gems/packages if OBS (and maybe software-o-o) needs it. Studio seems to use the same approach when it comes to devel:languages:ruby:extensions. Therefore, openSUSE mostly went the Ruby-1.9 / Rails-3.2 road with packaged gems and doesn't care for anything else anymore. As Studio won't be shipped with / supported by openSUSE any time soon, openSUSE would just gain nothing by shipping Studio's gem dependencies (or even caring for compatibility). Thus openSUSE should retain its current policies. As long as the security and maintenance teams are ok, the Studio team should continue doing whatever suits it and it's customers best. But again, you should really try to keep the fancyness level low. OBS already depends on far (far far far) to many gems (hey, it's Rails and it's supposed to be cool), but 200+ for Studio just seems like screaming madness to me. Linking dynamically or statically to 200 C libraries would be calling for trouble too! BTW. sorry for not replying to the thread, I just subscribed and Thunderbird doesnt' allow to inject "In-Reply-To" in the compose view :-) -- Viele Grüße, Sascha Peilicke

4 8

[opensuse-ruby] Fwd: [obs submit-request 127033] openSUSE:Factory/puppet-dashboard: declined by coolo
by Stephan Kulow 16 Jul '12

16 Jul '12

Hi, I declined this because IMO we shouldn't allow rails apps with bundled gems in factory. It's fine in whatever project, but there is no point in packaging gems if all apps then just call bundle package. What do you think? Does this make sense? Is that realistic? Greetings, Stephan -------- Original-Nachricht -------- Betreff: [obs submit-request 127033] openSUSE:Factory/puppet-dashboard: declined by coolo Datum: Thu, 5 Jul 2012 08:27:45 +0000 Von: coolo(a)suse.com Antwort an: coolo(a)suse.com An: coolo(a)suse.com State of submit-request #127033 was changed by coolo: review -> declined Comment: this package contains copies of all gems, this is not how openSUSE packages work I think. And it requires ruby(abi) = 1.8, which does not exist on factory https://build.opensuse.org/request/diff/127033 Source project: systemsmanagement:puppet package: puppet-dashboard revision: 1 Target: project: openSUSE:Factory package: puppet-dashboard -- Hermes messaging (http://hermes.opensuse.org) openSUSE Build Service (https://build.opensuse.org/) -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

3 6

[opensuse-ruby] couchdb broken
by James Tan 12 Jul '12

12 Jul '12

Hi, Not sure if this is the right list, but couchdb is broken: https://build.opensuse.org/package/show?package=couchdb&project=server%3Ada…. Is someone fixing this? Thanks, James T. -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

1 1

[opensuse-ruby] Failing rubygem-ohai for factory
by James Tan 11 Jul '12

11 Jul '12

Hi, The rubygem-ohai package that was working fine last week now fails to build in Factory. Any ideas why? https://build.opensuse.org/package/live_build_log?arch=i586&package=rubygem… Thanks, James T. -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

2 2

[opensuse-ruby] [RUG-N] Tomorrow evening @ SUSE HQ
by Dominik Bamberger 03 Jul '12

03 Jul '12

[German version below] Hey everybody, RUG-N (Ruby User Group Nuremberg) meets tomorrow evening at SUSE's HQ in Nuremberg. Since there was very little non-German participation the last times, I'll only say so much in English: If you are interested in Ruby and want to meet other people that are alike, please join us tomorrow at 7pm @ Maxtorhof. ==== German (extended) version ==== Ahoi Ruby-Freunde, ich werde zukünftig keine weiteren Einladungen zur Ruby User Group Nürnberg (RUG-N) auf diese Mailing Liste posten. Da wir uns morgen Abend aber im SUSE HQ in der Maxfeldstraße treffen, wollte ich alle die nicht eh schon Bescheid wissen, hiermit nochmals herzlichst einladen. Wir treffen uns ab 19:00 Uhr in der All-hands Area des Maxtorhofs. Themen haben wir auch diesmal wieder zwei am Start: Einerseits erzählt uns Henning Koch von der makandra GmbH etwas über bizarre Berechtigungsprobleme und deren Lösungen. Andererseits werde ich zeigen, wie man Pull Requests (auf GitHub) schon vorab testen kann. Wenn Ihr auch zukünftig auf dem Laufenden bleiben wollt, dann solltet Ihr Euch ein Lesezeichen auf unsere Homepage http://rug-n.de setzen oder dank der Infos, die Ihr dort findet, userer Google Group beitreten oder unserem Twitter Feed folgen. Bis bald, Dominik / Bamboo PS: Natürlich dürft Ihr diese Mail gerne weiterleiten. ;-) -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

1 0

[opensuse-ruby] Problem with segfaulting ruby C bindings in factory (1.9)
by Josef Reidinger 12 Jun '12

12 Jun '12

Hi, when I port of yast2-ruby-bindings to ruby 1.9 as we use in factory I face segfault when require string from C api. When I attach gdb I don't see anything special. I pass common c string to rb_require method and it segfault. Program received signal SIGSEGV, Segmentation fault. 0x00007ffff5527858 in __longjmp_chk () from /lib64/libc.so.6 (gdb) up #1 0x00007ffff3dd9a5c in rb_require_safe () from /usr/lib64/libruby1.9.so.1.9 (gdb) up #2 0x00007ffff4199e9c in YRuby::loadModule (argList=...) at /home/abuild/rpmbuild/BUILD/yast2-ruby-bindings-0.3.10/src/ruby/YRuby.cc:145 145 VALUE result = rb_require(module_path.c_str()); (gdb) p module_path $1 = "/home/abuild/rpmbuild/BUILD/yast2-ruby-bindings-0.3.10/tests/ycp/URI" To play with it do local osc build and then chroot into it with osc chroot ( I have extra packages for osc vim and gdb ). then if you rebuild package with make DEBUG=1 and make DIST=/home/abuild/rpmbuild/BUILDROOT/yast2-ruby-bindings-0.3.11/ then simple do this: cd /home/abuild/rpmbuild/BUILD/yast2-ruby-bindings-0.3.11/tests export Y2DIR=/home/abuild/rpmbuild/BUILDROOT/yast2-ruby-bindings-0.3.11/usr/lib64/YaST2/ gdb /usr/lib/YaST2/bin/y2base run -l - -M . ./ruby_object.ycp UI and you face also segfault. Do you have any hints what could be wrong? Josef -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-ruby+owner(a)opensuse.org

3 5

[opensuse-ruby] led display Suppliers shared photos with you
by led display Suppliers 10 Jun '12

10 Jun '12

Dear Mr/Miss, Still be puzzling about looking for best led display supplier? Now it will be miles easier working with KEROSA! Here you can find competitive price and excellent quality with a best mix. We"ve been in led display career for many years. We know your market and your country well. Our business is flexible which something is more likely to be a friend chat. We never waste your time. Our conversation will be very efficient base on our good communication. Please reply as soon as possible .if you are working on some led display project. We are ready to make you a satisfied offer! Samuel Shezhen Krosa Techology Co.,Ltd. Address: Building 3,Park,Guanguang road,Bao"an District,Shenzhen,China. post 518000

1 0