Skip to content
Snippets Groups Projects

Fix FTBFS in Debian unstable

All threads resolved!

Merge request reports

Closed by Lucas KanashiroLucas Kanashiro 6 years ago (Sep 7, 2018 1:20pm UTC)

Merge details

  • The changes were not merged into .

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • added 1 commit

    Compare with previous version

  • Lucas Kanashiro resolved all discussions

    resolved all discussions

  • @alee I do not think so. Call ruby or ruby2.5 has the same effect, ruby is always a symlink to some specific version, in stretch ruby -> ruby2.3 and in buster ruby -> ruby2.5. And we do not have two versions of ruby at the same time in the same release (just during the transition). I chose use non-versioned ruby call to avoid patch updates in the future (and FTBFS). If the rails app breaks with that specific ruby version we have to fix it as we are doing now.

  • In such case, can we have versioned ruby depends in debian/control instead? As I didn't use the versioned ruby as depends, so that folks who that removed ruby2.3 didn't detected the rdepends for open-build-service package.

    BTW, this patch and discuss we should move to debian's git repo as it's a FTBFS fix in Debian. Not for CCU's OBS.

  • @kanashiro Would you mind to close this merge request and use one on salsa.d.o instead? Thanks

  • You should not depend on versioned ruby, usually rails apps depend on ruby | ruby-interpreter. During the transition all packages that depend on ruby are rebuilt.

    And yes, let's do this on salsa :)

  • Please register or sign in to reply
    Loading