On Sat, Sep 5, 2020 at 17:25, Jonas Smedegaard <jo...@jones.dk> wrote:
Apples and oranges...: An autopkgtest failure is a regression that is treated as release critical by default, yes. This is not an autopkgtest regression.
gitlab installation works with lower versions of ruby-grpc, ruby-google-protobuf and libsass1. Just because grpc also caused a regression does not mean libsass did not cause it. Both caused regressions.
I do not reconize _this_ issue as a release critical regression.
Alright. So I guess you just refuse to accept arguments just because you are the maintainer here. I thought we are supposed to be collaborating together with debian policy as a baseline. May be I'm mistaken.
