[DRE-maint] Bug#988108: gitlab: Repeated issues resolving dependencies on upgrade

[Pirate Praveen]

On 2021, മേയ് 6 9:47:21 PM IST, Maximilian Stein <m at steiny.biz> wrote:
>Hi,
>
>> You should be installing gitlab 13.11.2. You need to add contrib section to people.debian.org/~praveen/gitaly. This is mentioned in https://wiki.debian.org/gitlab/#New_changes
>>
>> All dependencies are compatible with this version.
>>
>Thanks for the hint, I hadn't gotton this.
>
>However, this actually doesn't not fully solves the basic problem: 
>Basically, I am forced to always update to the newest gitlab version as 
>fast as possible or otherwise risking that updates of a dependency 
>package breaks my installation. So, actually, the problems boils down 
>to: The Gitlab dependencies are tighter in the Gemfile than in the 
>package. That's why dependency packages are upgraded although they break 
>another package which is not upgraded.
>
>
>What about generating the required dependencies from the Gemfile? 
>Basically that is what I am doing manually: The ruby package "example" 
>is found in the Debian package "ruby-example" and then I only need to 
>get the version right.

We cannot support more than one version of gitlab at any time. Gitlab by nature has fast releases and only way to keep up is keep updating gitlab. Only if upstream provides a long term supported version, we can support a gitlab version for longer than a month. Currently our goal is to go along with the upstream releases.

If there are more volunteers we can probably extend it up to 3 months. Even more resources will be required if we want to provide support for more than that.

>Best,
>Maximilian
>
>

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.