Drieam / LtiLauncher

An extraction layer to simplify the setup and launching of LTI tools.
https://drieam.github.io/LtiLauncher/
MIT License
7 stars 1 forks source link

Build failed: "Your bundle is locked to mimemagic (0.3.5), but that version could not be found" #43

Closed buckett closed 3 years ago

buckett commented 3 years ago

This was when I was trying to do a docker-compose up:

 => [1/7] FROM docker.io/library/ruby:2.7.1-alpine@sha256:73814d17e9f746ca21a67a4cde96ab81e858bbe9e6bf78257fbb5def033f2b82                                                      15.4s
 => => resolve docker.io/library/ruby:2.7.1-alpine@sha256:73814d17e9f746ca21a67a4cde96ab81e858bbe9e6bf78257fbb5def033f2b82                                                       0.0s
 => => sha256:73814d17e9f746ca21a67a4cde96ab81e858bbe9e6bf78257fbb5def033f2b82 977B / 977B                                                                                       0.0s
 => => sha256:c8ec71e10dc234f68afe8db9ec02d5b646072c18f635135656167cfa8f174a86 1.36kB / 1.36kB                                                                                   0.0s
 => => sha256:b46ea0bc598477695ca9c92f364a1883b0edf8f14626f232318fe5869a4fcef3 6.09kB / 6.09kB                                                                                   0.0s
 => => sha256:df20fa9351a15782c64e6dddb2d4a6f50bf6d3688060a34c4014b0d9a752eb4c 2.80MB / 2.80MB                                                                                   5.7s
 => => sha256:b79bab524d4c7596bab2a0d94b0494aad2674ee594f2a88174d16511611c047e 1.20MB / 1.20MB                                                                                   0.7s
 => => sha256:8f5dd72031b5c8bc3105b90aaaad951884e13662394e1d6ce098e498a87cc197 196B / 196B                                                                                       0.7s
 => => sha256:bea36b8d88deb6212ab18e989477c938b12af1c1f029ec2428a83ae1eed07c81 23.65MB / 23.65MB                                                                                13.9s
 => => sha256:3396c77940f8abd21ea5b4d15cf6df2fa4f5b3163403accb86be4805e8c1b51e 140B / 140B                                                                                       6.0s
 => => extracting sha256:df20fa9351a15782c64e6dddb2d4a6f50bf6d3688060a34c4014b0d9a752eb4c                                                                                        0.2s
 => => extracting sha256:b79bab524d4c7596bab2a0d94b0494aad2674ee594f2a88174d16511611c047e                                                                                        0.1s
 => => extracting sha256:8f5dd72031b5c8bc3105b90aaaad951884e13662394e1d6ce098e498a87cc197                                                                                        0.0s
 => => extracting sha256:bea36b8d88deb6212ab18e989477c938b12af1c1f029ec2428a83ae1eed07c81                                                                                        1.1s
 => => extracting sha256:3396c77940f8abd21ea5b4d15cf6df2fa4f5b3163403accb86be4805e8c1b51e                                                                                        0.0s
 => [internal] load build context                                                                                                                                                0.1s
 => => transferring context: 382.01kB                                                                                                                                            0.1s
 => [2/7] WORKDIR /app                                                                                                                                                           0.2s
 => [3/7] RUN gem install bundler:2.1.4     && apk add --update build-base postgresql-dev tzdata # nodejs                                                                       20.6s
 => [4/7] COPY Gemfile Gemfile.lock /app/                                                                                                                                        0.1s
 => ERROR [5/7] RUN bundle config set deployment 'true'     && bundle config set path '/gems'     && bundle install                                                              6.5s
------                                                                                                                                                                                
 > [5/7] RUN bundle config set deployment 'true'     && bundle config set path '/gems'     && bundle install:                                                                         
#10 1.271 The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x86-mswin32, x64-mingw32, java. To add those platforms to the bundle, run `bundle lock --add-platform x86-mingw32 x86-mswin32 x64-mingw32 java`.                                   
#10 2.655 Fetching gem metadata from https://rubygems.org/.........                                                                                                                   
#10 5.835 Your bundle is locked to mimemagic (0.3.5), but that version could not be found                                                                                             
#10 5.835 in any of the sources listed in your Gemfile. If you haven't changed sources,
#10 5.835 that means the author of mimemagic (0.3.5) has removed it. You'll need to update
#10 5.835 your bundle to a version other than mimemagic (0.3.5) that hasn't been removed
#10 5.835 in order to install.
------
executor failed running [/bin/sh -c bundle config set deployment 'true'     && bundle config set path '/gems'     && bundle install]: exit code: 7
ERROR: Service 'web' failed to build

This looks to be related to: https://github.com/rails/rails/issues/41757

StefSchenkelaars commented 3 years ago

@buckett Yea this is some licensing problem with a gem about mime types. Probably a bundle update will fix it. Let me have a look today 👍

buckett commented 3 years ago

docker-compose up now completes successfully, thanks.

buckett commented 3 years ago

Don't know if it's worth adding a scheduled CI run to catch these in the future? https://docs.github.com/en/actions/reference/events-that-trigger-workflows#schedule

Only problem we see is that the notifications for these failures goes to the last person who modified the cron schedule.