Bug #16338

gemspec stub EOF separators throw warning

Added by MSP-Greg (Greg L) over 1 year ago. Updated 5 days ago.

Target version:
ruby -v:
ruby 2.7.0dev (2019-11-11T03:09:19Z master 6f9be8505d) [x64-mingw32]


Some recent commits generate a warning when comments contain EOF characters, and any extension gems that create more than one *.so file have EOF characters in the stub portion of the gemspec. I noticed it with ruby-loco logs when json is loaded.

This may be intentional, but I hate seeing warning generated by files included with master. There are comments in RubyGems about it, but I didn't see a resolution.

Also, I didn't look thru the CI logs here, and often RubyGems is disabled. (?)

Please close if intentional...

Updated by hsbt (Hiroshi SHIBATA) about 1 year ago

  • Assignee set to hsbt (Hiroshi SHIBATA)
  • Status changed from Open to Assigned

Can you point the "some recent commits"?

Updated by hsbt (Hiroshi SHIBATA) 5 days ago

  • Status changed from Assigned to Closed

There is no feedback over the 1year.

Updated by nobu (Nobuyoshi Nakada) 5 days ago

  • Backport changed from 2.5: UNKNOWN, 2.6: UNKNOWN to 2.5: DONTNEED, 2.6: DONTNEED, 2.7: DONTNEED, 3.0: DONTNEED

It's 69ec3f70fab0c1c537c68fb135cc315181b1d750, and had been reverted already soon.

Also available in: Atom PDF