Debian Bug report logs - #985057
gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Maximilian Stein <m@steiny.biz>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Date: Fri, 12 Mar 2021 10:57:45 +0100

Package: gitlab-apt-pin-preferences
Version: 2021.03.09
Severity: normal

Dear Maintainer,

I am experimenting with gitlab-apt-pin-preferences to get Gitlab's
dependencies right. However, I noticed that now ruby-doorkeeper breaks
Gitlab.

In /etc/apt/preferences.d/99gitlab ruby-doorkeeper is pinned to
"release n=buster-backports", however, this also matches packages from
buster-backports in fasttrack such as ruby-doorkeeper 5.5.0-1~bpo10+1
which now breaks Gitlab. Consequently, I would suggest to pin these
packages more tightly. E.g., ruby-doorkeeper should be pinned to
"n=buster-backports,l=Debian Backports" instead of just
"n=buster-backports". This would avoid premature updates of gitlab's
dependencies.

Best,
Maximilian

Message #10 received at 985057-done@bugs.debian.org (full text, mbox, reply):

From: Andrei POPESCU <andreimpopescu@gmail.com>

To: Maximilian Stein <m@steiny.biz>, 985057-done@bugs.debian.org

Subject: Re: Bug#985057: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Date: Fri, 12 Mar 2021 15:56:13 +0200

[Message part 1 (text/plain, inline)]

On Vi, 12 mar 21, 10:57:45, Maximilian Stein wrote:
> Package: gitlab-apt-pin-preferences
> Version: 2021.03.09
> Severity: normal

Hello,

There is no such package in Debian, please report any issues to where 
you obtained it from.
 
> Dear Maintainer,
> 
> I am experimenting with gitlab-apt-pin-preferences to get Gitlab's
> dependencies right. However, I noticed that now ruby-doorkeeper breaks
> Gitlab.
> 
> In /etc/apt/preferences.d/99gitlab ruby-doorkeeper is pinned to
> "release n=buster-backports", however, this also matches packages from
> buster-backports in fasttrack such as ruby-doorkeeper 5.5.0-1~bpo10+1
> which now breaks Gitlab. Consequently, I would suggest to pin these
> packages more tightly. E.g., ruby-doorkeeper should be pinned to
> "n=buster-backports,l=Debian Backports" instead of just
> "n=buster-backports". This would avoid premature updates of gitlab's
> dependencies.
> 
> Best,
> Maximilian

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 985057-done@bugs.debian.org (full text, mbox, reply):

From: Maximilian Stein <m@steiny.biz>

To: Andrei POPESCU <andreimpopescu@gmail.com>, 985057-done@bugs.debian.org

Cc: Pirate Praveen <praveen@onenetbeyond.org>

Subject: Re: Bug#985057: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Date: Fri, 12 Mar 2021 16:04:16 +0100

[Message part 1 (text/plain, inline)]

Hello,

This package is part of Debian Fasttrack. Its source is hosted on Salsa: 
https://salsa.debian.org/fasttrack-team/gitlab-apt-pin-preferences/-/tree/master, 
and maintainer is Praveen Arimbrathodiyil (in CC).

Best,
Maximilian

[OpenPGP_signature (application/pgp-signature, attachment)]

Message #16 received at 985057@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: 985057@bugs.debian.org

Cc: Maximilian Stein <m@steiny.biz>

Subject: Re: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Date: Fri, 12 Mar 2021 22:02:32 +0530

On Fri, 12 Mar 2021 10:57:45 +0100 Maximilian Stein <m@steiny.biz> 
wrote:
> Package: gitlab-apt-pin-preferences
> Version: 2021.03.09
> Severity: normal
>
> Dear Maintainer,
>
> I am experimenting with gitlab-apt-pin-preferences to get Gitlab's
> dependencies right. However, I noticed that now ruby-doorkeeper 
breaks
> Gitlab.
>
> In /etc/apt/preferences.d/99gitlab ruby-doorkeeper is pinned to
> "release n=buster-backports", however, this also matches packages 
from
> buster-backports in fasttrack such as ruby-doorkeeper 5.5.0-1~bpo10+1
> which now breaks Gitlab. Consequently, I would suggest to pin these
> packages more tightly. E.g., ruby-doorkeeper should be pinned to
> "n=buster-backports,l=Debian Backports" instead of just
> "n=buster-backports". This would avoid premature updates of gitlab's
> dependencies.

This matching is expected.

Can you share the error message? ruby-doorkeeper 5.3 to 5.5 update is 
not supposed to break gitlab.

Message #21 received at 985057@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: 985057@bugs.debian.org

Cc: Maximilian Stein <m@steiny.biz>

Subject: Re: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Date: Fri, 12 Mar 2021 22:15:20 +0530

Control: reassign -1 gitlab

On Fri, Mar 12, 2021 at 10:02 pm, Pirate Praveen 
<praveen@onenetbeyond.org> wrote:
> On Fri, 12 Mar 2021 10:57:45 +0100 Maximilian Stein <m@steiny.biz> 
> wrote:
> > Package: gitlab-apt-pin-preferences
> > Version: 2021.03.09
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > I am experimenting with gitlab-apt-pin-preferences to get Gitlab's
> > dependencies right. However, I noticed that now ruby-doorkeeper 
> breaks
> > Gitlab.
> >
> > In /etc/apt/preferences.d/99gitlab ruby-doorkeeper is pinned to
> > "release n=buster-backports", however, this also matches packages 
> from
> > buster-backports in fasttrack such as ruby-doorkeeper 
> 5.5.0-1~bpo10+1
> > which now breaks Gitlab. Consequently, I would suggest to pin these
> > packages more tightly. E.g., ruby-doorkeeper should be pinned to
> > "n=buster-backports,l=Debian Backports" instead of just
> > "n=buster-backports". This would avoid premature updates of gitlab's
> > dependencies.
> 
> This matching is expected.
> 
> Can you share the error message? ruby-doorkeeper 5.3 to 5.5 update is 
> not supposed to break gitlab.
> 

ok, I can reproduce the error.

Could not find gem 'doorkeeper (~> 5.3.0)' in any of the gem sources 
listed in your
Gemfile.

This is a bug in gitlab, it should not keep such strict dependencies. I 
usually relax the dependency but I seem to have missed this gem while 
relaxing the dependencies.

This should be fixed in gitlab 13.9. For now, you can manually install 
the older version.

Message #30 received at 985057@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: Maximilian Stein <m@steiny.biz>

Cc: 985057@bugs.debian.org

Subject: Re: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Date: Fri, 12 Mar 2021 22:26:06 +0530

On Fri, Mar 12, 2021 at 5:52 pm, Maximilian Stein <m@steiny.biz> wrote:
> 
>> This matching is expected.
>> 
>> Can you share the error message? ruby-doorkeeper 5.3 to 5.5 update 
>> is not supposed to break gitlab.
> 
> Basically, the rake commands (check, backup, ...) started to fail:
> 
> $ gitlab-rake gitlab:check :(
> Check if Gitlab is configured correctly...
> fatal: Kein Git-Repository (oder irgendein Elternverzeichnis bis zum 
> Einhängepunkt /)
> Stoppe bei Dateisystemgrenze (GIT_DISCOVERY_ACROSS_FILESYSTEM nicht 
> gesetzt).
> fatal: Kein Git-Repository (oder irgendein Elternverzeichnis bis zum 
> Einhängepunkt /)
> Stoppe bei Dateisystemgrenze (GIT_DISCOVERY_ACROSS_FILESYSTEM nicht 
> gesetzt).
> Could not find gem 'doorkeeper (~> 5.3.0)' in any of the gem sources 
> listed in your Gemfile.
> Run `bundle install` to install missing gems.
> 
> 
> Running gitlab-update-gemfile-lock did not help, unfortunately.
> 

apt install ruby-doorkeeper=5.3.0-2~bpo10+1

should fix it and I will be uploading gitlab 13.9.3 to fasttrack soon, 
which will fix this.

> Best,
> Maximilian
> 
> 

Message #35 received at 985057@bugs.debian.org (full text, mbox, reply):

From: Maximilian Stein <m@steiny.biz>

To: Pirate Praveen <praveen@onenetbeyond.org>, 985057@bugs.debian.org

Subject: Re: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Date: Fri, 12 Mar 2021 17:52:24 +0100

[Message part 1 (text/plain, inline)]

> This matching is expected.
>
> Can you share the error message? ruby-doorkeeper 5.3 to 5.5 update is 
> not supposed to break gitlab.

Basically, the rake commands (check, backup, ...) started to fail:

$ gitlab-rake gitlab:check :(
Check if Gitlab is configured correctly...
fatal: Kein Git-Repository (oder irgendein Elternverzeichnis bis zum 
Einhängepunkt /)
Stoppe bei Dateisystemgrenze (GIT_DISCOVERY_ACROSS_FILESYSTEM nicht 
gesetzt).
fatal: Kein Git-Repository (oder irgendein Elternverzeichnis bis zum 
Einhängepunkt /)
Stoppe bei Dateisystemgrenze (GIT_DISCOVERY_ACROSS_FILESYSTEM nicht 
gesetzt).
Could not find gem 'doorkeeper (~> 5.3.0)' in any of the gem sources 
listed in your Gemfile.
Run `bundle install` to install missing gems.


Running gitlab-update-gemfile-lock did not help, unfortunately.

Best,
Maximilian

[OpenPGP_signature (application/pgp-signature, attachment)]

Message #38 received at 985057@bugs.debian.org (full text, mbox, reply):

From: Andrei POPESCU <andreimpopescu@gmail.com>

To: Maximilian Stein <m@steiny.biz>

Cc: 985057@bugs.debian.org, Pirate Praveen <praveen@onenetbeyond.org>

Subject: Re: Bug#985057: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Date: Sat, 13 Mar 2021 08:53:47 +0200

[Message part 1 (text/plain, inline)]

On Vi, 12 mar 21, 16:04:16, Maximilian Stein wrote:
> Hello,
> 
> This package is part of Debian Fasttrack. Its source is hosted on Salsa: https://salsa.debian.org/fasttrack-team/gitlab-apt-pin-preferences/-/tree/master,
> and maintainer is Praveen Arimbrathodiyil (in CC).

As far as I know Fasttrack is (still) an unofficial service, and the BTS 
doesn't have any knowledge of packages that exist only in there.

Even for Backports (that contains only packages known to the BTS) the 
rule is to report bugs to Backports Maintainer instead of the BTS, 
because the "regular" package could be maintained by someone else.

Hope this explains,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages

[signature.asc (application/pgp-signature, inline)]

Message #43 received at 985057@bugs.debian.org (full text, mbox, reply):

From: Maximilian Stein <m@steiny.biz>

To: Pirate Praveen <praveen@onenetbeyond.org>

Cc: 985057@bugs.debian.org

Subject: Re: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Date: Sat, 13 Mar 2021 09:46:09 +0100

[Message part 1 (text/plain, inline)]

> apt install ruby-doorkeeper=5.3.0-2~bpo10+1
>
> should fix it and I will be uploading gitlab 13.9.3 to fasttrack soon, 
> which will fix this.
Awesome, thanks a lot!

[OpenPGP_signature (application/pgp-signature, attachment)]

Message #44 received at 985057-done@bugs.debian.org (full text, mbox, reply):

From: Pirate Praveen <praveen@onenetbeyond.org>

To: Maximilian Stein <m@steiny.biz>

Cc: 985057-done@bugs.debian.org

Subject: Re: gitlab-apt-pin-preferences: Pin not specific enough to prevent breaking Gitlab

Date: Mon, 15 Mar 2021 14:20:56 +0530

On Sat, Mar 13, 2021 at 9:46 am, Maximilian Stein <m@steiny.biz> wrote:
> 
>> apt install ruby-doorkeeper=5.3.0-2~bpo10+1
>> 
>> should fix it and I will be uploading gitlab 13.9.3 to fasttrack 
>> soon, which will fix this.
> Awesome, thanks a lot!
> 

Fixed in gitlab 13.8.5+ds1-2~fto10+2 (as gitlab 13.9 seems to have 
issues with ruby-rugged update).

Send a report that this bug log contains spam.