[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[DC22] Ruby team BoF notes



Hi everyone,

Thanks for those who attended our BoF last week, below is a copy&paste of the notes we took on the etherpad to also keep a record here in our mailing list:

======================================

# Ruby team BoF

## Agenda

- Team statistics
  + http://blends.debian.net/liststats/authorstat_debian-ruby.png
  + http://blends.debian.net/liststats/bugs_pkg-ruby.png
  + http://blends.debian.net/liststats/commitstat_ruby-team.png
  + http://blends.debian.net/liststats/maintainer_per_package_ruby-team.png
  + http://blends.debian.net/liststats/uploaders_pkg-ruby.png
  + http://blends.debian.net/liststats/wnpp_pkg-ruby.png

- Ruby 3.1 transition
   + Could it start in unstable after 25 August (Debian import freeze in Ubuntu)?
   + Useful changelog https://rubyreferences.github.io/rubychanges/3.1.html
   + Rebuild of reverse dependencies
       - https://people.debian.org/~kanashiro/ruby3.1/
       - Only 33 build failures \o/ reasonably low number of failures
         several of them are related to the fact that Psych now uses safe_load behavior for load, and the class Gem::specification is not allowed to be parsed with psych by gem2deb.
         
                   /usr/bin/ruby3.1 /usr/lib/ruby/vendor_ruby/gem2deb/extension_builder.rb /<<PKGBUILDDIR>> debian/ruby-fusefs
         These are for packages having a metadata.yml file and a binary extension. The fix should go in gem2deb for that
- NEW in gem2deb 2.0
- Praveen will be doing less work on ruby packages due to the termination of the Gitlab financial support
  - rails will be affected
  - security team not happy about the state of rails in stable
  - opencollective.com/debian-gitlab
  - need to get the right people to pitch in there
- RuboCop::Packaging update! \o/
- Next sprint ?
- Sponsoring work
- Goals for the next release ?
  - ruby3.1
  - rails 6.1.4 -> 6.1.6 (or latest 6.x release by November or so)
    - not rails 7 for bookworm
- Briefly look at bugs
  There are a certain number of patterns:
      - omniauth related bugs
      - coffeescript related bugs (nanoc, ruby-hamlit, ruby-sprocket,...)
      - bugs with errors:  FTBFS: installing symlink 'XXX' pointing to parent path /usr/share/_javascript_/XXX of /<<PKGBUILDDIR>>/debian/ruby-jquery-atwho-rails/usr/share/rubygems-integration/all/gems/XXX is not allowed

======================================

-- 
Lucas Kanashiro

Reply to: