#1019643 ruby-omniauth-oauth2-generic: FTBFS with ruby3.1: ERROR: Test "ruby3.0" failed: Failure/Error: expect(last_response.headers["Location"]).to match(%r{redirect_uri=https%3A%2F%2Fmy_server.com%2Foauth%2Fcallback&})

Package:
src:ruby-omniauth-oauth2-generic
Source:
ruby-omniauth-oauth2-generic
Submitter:
Antonio Terceiro
Date:
2023-03-22 15:39:03 UTC
Severity:
important
Tags:
#1019643#5
Date:
2022-09-13 01:08:30 UTC
From:
To:
Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-omniauth-oauth2-generic with ruby3.1 enabled, the build
failed. This does not look related to ruby3.1 though, as the failure
happens yet at the ruby3.0 tests.

Relevant part of the build log (hopefully):
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-omniauth-oauth2-generic/ruby-omniauth-oauth2-generic_0.2.2-1.1+rebuild1663007915_amd64-2022-09-12T18:38:36Z.build

If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
#1019643#12
Date:
2023-03-22 13:59:53 UTC
From:
To:
On Mon, 12 Sep 2022 22:08:30 -0300 Antonio Terceiro  <terceiro@debian.org> wrote:
 > We are about to start the ruby3.1 transition in unstable. While
trying to
 > rebuild ruby-omniauth-oauth2-generic with ruby3.1 enabled, the build
 > failed. This does not look related to ruby3.1 though, as the failure
 > happens yet at the ruby3.0 tests.

This looks like a test only failure as gitlab confirmed everything
works with ruby 3.0 here
https://gitlab.com/gitlab-org/gitlab/-/issues/386908

The upstream seems inactive though, still reported as
https://gitlab.com/satorix/omniauth-oauth2-generic/-/issues/37