[DRE-maint] Bug#1009954: gitlab: Cannot install experimental or unstable version due to ruby-omniauth dependency

[Pirate Praveen]

2022, ഏപ്രിൽ 22 11:20:37 PM IST, Eric Valette <eric.valette at free.fr>ൽ എഴുതി
>On 21/04/2022 14:12, Pirate Praveen wrote:
>> 
>> 
>> 2022, ഏപ്രിൽ 21 5:27:25 PM IST, "Éric Valette" <eric.valette at free.fr>ൽ എഴുതി
>>>
>>> The breakage is there for more than 8 months. I tried to install regularly.
>> 
>> Even if I want to, I'm not able to support gitlab in unstable or experimental. That is the reason why I had to create fasttrack.debian.net
>> 
>> Gitlab changes too fast for unstable or experimental.
>
>I would say the contrary : experimental version are always above what 
>gitlab expects. experiùmental is way faster than gitlab.

It goes both ways, sometimes gitlab wants newer versions and sometimes other maintainers don't want to wait for gitlab. In this case omniauth was updated before gitlab supports the new version because it was needed for some time.

>Putting gitlab related packages in experimental or unstable that you 
>know cannot install is just frustrating. People have someting cretaed 
>private packages version.

Unstable or experimental is for development, these are never supported or recommended for production systems.

I can understand the frustration, but there is nothing more I can offer here.

>
>> In this specific case multiple upstream gems needs to updated to work with omniauth 2.0. There are upstream bugs filed already. I can't step in as upstream maintainers of all those gems. More help is always welcome.
>>   
>>> I does not work either if you bstarted from a testing ISO.

>> Yes, only stable is currently supported. More volunteers to support testing, unstable or experimental welcome.
>
>Ben then why do yopu publsih pacakages that have no chnace to install 
>for unstable and experimental.

It works most of the time, the breakage happens during transitions when other maintainers don't want to wait for gitlab. If gitlab gets updated to work with newer omniauth, it will start working again.

I hope things will get fixed before next stable release, if not I will try other work arounds.
>> 
>> Even outside gitlab, only stable is officially supported, unstable remains broken for many days during transitions.
>> 
>>>
>>>     
>>>>
>>>>        See wiki.debian.org/gitlab
>>>>       
>>>>   
>>>>      
>>>
>>>     
>>> Been ther done that. No way to make it work. FIX your package dependency. Its broken for as long as 1.9.1-1 has been in unstable meaning April 2020 see https://tracker.debian.org/pkg/ruby-omniauth
>> 
>> I meant follow the recommended option, that is bullseye-fasttrack.
>
>Evne with buleyes fastrack, once you installed a testing iso and updated 
>  you are scewed.

Updating to testing is not supported, by the time testing becomes stable, the migration to next stable release will be supported. I have been doing this for last many releases. So buster-fasttrack to bullseye-fasttrack is supported. When current testing becomes next stable, upgrading to bookworm-fasttrack will be supported.


>>> Could you please follow the rules and publish in experimental things that works with a debian unstable system.
>> 
>> I'm not able to do this alone, even if I want to, this is too much work for a single maintainer. At this point only bullseye-fasttrack I can reasonably support.
>
>Then avoid publishing package for other debian version.

I explained above, it works most of the times and breaks during transitions and fixing will take time. There is no guarantee that it will not break in unstable.

Also I need this till next stable version is released.
>
>-- eric

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