Bug#770618: strange behaviour when building twitter-text
On Saturday 22 November 2014 10:47 PM, Pirate Praveen wrote: when I use git-buildpackage I can get the rubygems-integration folder, but when built with pbuilder, I don;t see it. My local gem2deb version is uptodate (0.10). http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770618 I think its a problem with gem2deb. I found out ruby-fog-core also does not have a gemspec installed. I think this happens when metadata.yml is missing in the source. signature.asc Description: OpenPGP digital signature
Bug#770618: strange behaviour when building twitter-text
On Sunday 23 November 2014 04:11 AM, Pirate Praveen wrote: On Saturday 22 November 2014 10:47 PM, Pirate Praveen wrote: when I use git-buildpackage I can get the rubygems-integration folder, but when built with pbuilder, I don;t see it. My local gem2deb version is uptodate (0.10). http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770618 I think its a problem with gem2deb. I found out ruby-fog-core also does not have a gemspec installed. I think this happens when metadata.yml is missing in the source. I found the root cause, Invalid gemspec in [fog-core.gemspec]: No such file or directory - git signature.asc Description: OpenPGP digital signature
Bug#770618: strange behaviour when building twitter-text
severity -1 wishlist retitle -1 warn when gemspec file is invalid On Sunday 23 November 2014 04:33 AM, Pirate Praveen wrote: On Sunday 23 November 2014 04:11 AM, Pirate Praveen wrote: On Saturday 22 November 2014 10:47 PM, Pirate Praveen wrote: when I use git-buildpackage I can get the rubygems-integration folder, but when built with pbuilder, I don;t see it. My local gem2deb version is uptodate (0.10). http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770618 I think its a problem with gem2deb. I found out ruby-fog-core also does not have a gemspec installed. I think this happens when metadata.yml is missing in the source. I found the root cause, Invalid gemspec in [fog-core.gemspec]: No such file or directory - git I think we should catch this similar to how we catch rubygems usage. signature.asc Description: OpenPGP digital signature
