Bug#986254: gem2deb creates gemspec file as a binary file for ruby-magic-static? gem

2021-04-07 Thread Pirate Praveen
On Wed, 7 Apr 2021 14:36:25 -0300 Antonio Terceiro wrote: > On Wed, Apr 07, 2021 at 02:20:34PM -0300, Antonio Terceiro wrote: > > On Wed, Apr 07, 2021 at 04:49:38PM +0530, Nilesh Patra wrote: > > > And I tried changing the second "-lib" entry to ruby-lib (it does not > > > mean anything, this is a

Bug#986254: gem2deb creates gemspec file as a binary file for ruby-magic-static? gem

2021-04-07 Thread Antonio Terceiro
On Wed, Apr 07, 2021 at 02:20:34PM -0300, Antonio Terceiro wrote: > On Wed, Apr 07, 2021 at 04:49:38PM +0530, Nilesh Patra wrote: > > And I tried changing the second "-lib" entry to ruby-lib (it does not > > mean anything, this is a random example) > > > > and I get the same offending term: ruby l

Bug#986254: gem2deb creates gemspec file as a binary file for ruby-magic-static? gem

2021-04-07 Thread Antonio Terceiro
On Wed, Apr 07, 2021 at 04:49:38PM +0530, Nilesh Patra wrote: > And I tried changing the second "-lib" entry to ruby-lib (it does not > mean anything, this is a random example) > > and I get the same offending term: ruby lib^@ruby-lib > attaching the output, for ref > > So it looks like more than

Bug#986254: gem2deb creates gemspec file as a binary file for ruby-magic-static? gem

2021-04-07 Thread Nilesh Patra
On Wed, Apr 07, 2021 at 04:42:21PM +0530, Nilesh Patra wrote: > I did a bit of debugging on this, and it looks like for this case, the > culprit is yaml instead. > * Now, I have the metadata.yml - I just wrote a snippet of code to check the > behaviour of gemspec w.r.t metadata file > Here it is

Bug#986254: gem2deb creates gemspec file as a binary file for ruby-magic-static? gem

2021-04-07 Thread Nilesh Patra
And I tried changing the second "-lib" entry to ruby-lib (it does not mean anything, this is a random example) and I get the same offending term: ruby lib^@ruby-lib attaching the output, for ref So it looks like more than one entry in "require_paths" outputs a "binary" gemspec which is troublesom

Bug#986254: gem2deb creates gemspec file as a binary file for ruby-magic-static? gem

2021-04-07 Thread Nilesh Patra
I did a bit of debugging on this, and it looks like for this case, the culprit is yaml instead. This is what I did: * patched the gem2deb code to _not_ delete metadata.yml diff --git a/lib/gem2deb/gem2tgz.rb b/lib/gem2deb/gem2tgz.rb index d03452f..aac5162 100644 --- a/lib/gem2deb/gem2tgz.rb +++

Bug#986254: gem2deb creates gemspec file as a binary file for ruby-magic-static gem

2021-04-07 Thread Pirate Praveen
On Thu, 01 Apr 2021 22:42:26 +0530 Pirate Praveen wrote: > Package: gem2deb > Version: 1.4 > > Since the gemspec file has some binary data quilt is failing to create > a patch. Attached is the generated gemspec file. I had to manually > remove the offending characters using gedit and add it as

Bug#986254: gem2deb creates gemspec file as a binary file for ruby-magic-static gem

2021-04-01 Thread Pirate Praveen
Package: gem2deb Version: 1.4 Since the gemspec file has some binary data quilt is failing to create a patch. Attached is the generated gemspec file. I had to manually remove the offending characters using gedit and add it as debian/gemspec for the build to work. I'm not sure if it is really