Re: Request to fast track gitlab dependencies
On 2019, മാർച്ച് 3 3:04:19 PM IST, Alexander Wirt <formorer@formorer.de> wrote:
>On Sun, 03 Mar 2019, Pirate Praveen wrote:
>
>>
>>
>> On 2019, മാർച്ച് 3 2:15:27 PM IST, Alexander Wirt
><formorer@formorer.de> wrote:
>> >On Mon, 07 Jan 2019, Pirate Praveen wrote:
>> >
>> >> On 12/20/18 9:50 AM, Pirate Praveen wrote:
>> >> > I have also asked gitlab about their commitment to continue
>funding
>> >even
>> >> > if I stop working on it. I have also asked them if they are open
>to
>> >> > funding a team instead of just me.
>> >> >
>> >> > I will update here once they respond.
>> >>
>> >> Just an update: gitlab team has agreed to expand the team and now
>> >> Abhijith and Sruthi can get paid to work on gitlab maintenance. So
>> >now 3
>> >> people are funded by Gitlab Inc to maintain gitlab in Debian.
>> >I came to my attention that the gitlab package isn't in testing
>> >anymore. That
>> >means it will get removed from backports soon, are there any plans
>to
>> >get it
>> >back to testing?
>>
>> It is blocked by security team because they don't want it in stable.
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915050
>>
>> It'd be disappointing to have it removed from backports now. I
>thought the plan to remove it from testing was already known when
>gitlab was accepted into backports.
>And we always told you that we will remove it when it leaves testing,
>you
>just ignored the fact.
>
>Alex
>
The bug that caused removal from testing was a meta bug to keep gitlab out of buster. If that can be considered a valid excuse to keep gitlab in stretch-backports, please do. The package in backports-new fixes all open rc bugs.
As for bullseye, I hope to get gitlab back in testing by closing that bug. During the bullseye cycle, I hope a separate repository can be setup as per the discussions we already had.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Reply to: