Re: gitlab for stretch-backports - call for testing

[Pirate Praveen]

On 02/05/18 6:30 PM, Pirate Praveen wrote:
> Hi team,
> 
> I have rebuilt gitlab and all dependencies for stretch-backports and
> uploaded here https://people.debian.org/~praveen/gitlab/ (about 157 ruby
> packages were rebuilt).

An update on the current status of this effort. After a long wait
protobuf 3.6 is available in unstable, once it moves to testing, I
gitlab can reach testing. Except for packages depending on protobuf, all
other dependencies are now available in stretch-backports (ruby-ed25519
which was a recent addition when ruby-net-ssh was updated to 5.x is in
backports-NEW).

> It starting fine with an initial test, but found some errors in
> production.log. Any help in testing this would be welcome as I hope to
> provide stretch-backports as an upgrade path for gitlab currently in
> stretch (backporting security fixes to 8.13 is very difficult as code
> has diverged too much).

10.8.7 is the last gitlab version supporting ruby 2.3 and it still has
15 security issues against it. We either need to keep backporting the
security issues or update ruby also in stretch-bckports (it means
rebuilding all native ruby gems about 43 of them with an update to gem2deb).

I will wait till 10.8.7 enters stretch-backports before I work on
updating gitlab to more recent versions.

In the short term, help in backport the security issues welcome.

> My initial hope was to provide updates via stretch-backports, but sudden
> explosion of nodejs front end dependencies made that impossible. Now all
> nodejs modules are installed via npm/yarn and gitlab is moved to contrib.
> 
> More than a 100 node module packages are stuck in NEW for over 5-7
> months and not sure how to get it back in main. If you'd like to help,
> please volunteer with ftp team and help process the node modules.

Also the node packages are getting attention from ftp masters with the
decision to reject small packages that should be embedded as per
https://wiki.debian.org/Javascript/Nodejs/NEW

There is also a recent call from ftp masters for more help.



signature.asc
Description: OpenPGP digital signature

Re: gitlab for stretch-backports - call for testing

[Dominik George]

Hi,

> This issue is now fixed (for some time) with a patch from gitlab
> upstream. git.fosscommunity.in is now running with gitlab 10. So far no
> issues reported.

Thanks!

> 
> Current status: libgit2 transition has started.
> 
> protobuf transition is tricky, we need to port apps using protobuf-c to
> use protobluff instead. See
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901015#12 for more
> details. If you are good in C, help with this would be great.
> 

Unfortunately not alt all :D.

But I am available fortesting, as always.

Cheers,
Nik


signature.asc
Description: PGP signature

Re: gitlab for stretch-backports - call for testing

[Pirate Praveen]

On Friday 15 June 2018 02:48 PM, Dominik George wrote:
>>> I was able to update from gitlab 8 in stretch to gitlab 10 in my repo
>>> (https://people.debian.org/~praveen/gitlab/) without any issues.
>>
>> Tested again - same error as before (which I expected, as the migration 
>> scripts did not change).
> 
> I felt lucky and removed the failing migration:
> 
>   
> /usr/share/gitlab/db/post_migrate/20170525140254_rename_all_reserved_paths_again.rb
> 
> Everything else ran without errors, and GitLab seems entirely happy… I have
> no idea what I broke with that, but I'm sure someone will find out :D.

I got this error now too with real db of git.fosscommunity.in (earlier
it was an install from scratch with just one project).

I opened an issue upstream

https://gitlab.com/gitlab-org/gitlab-ce/issues/48040



signature.asc
Description: OpenPGP digital signature

Re: gitlab for stretch-backports - call for testing

[Dominik George]

> > I was able to update from gitlab 8 in stretch to gitlab 10 in my repo
> > (https://people.debian.org/~praveen/gitlab/) without any issues.
> 
> Tested again - same error as before (which I expected, as the migration 
> scripts did not change).

I felt lucky and removed the failing migration:

  
/usr/share/gitlab/db/post_migrate/20170525140254_rename_all_reserved_paths_again.rb

Everything else ran without errors, and GitLab seems entirely happy… I have
no idea what I broke with that, but I'm sure someone will find out :D.

-nik



signature.asc
Description: PGP signature

Re: gitlab for stretch-backports - call for testing

[Dominik George]

Hi,

> I was able to update from gitlab 8 in stretch to gitlab 10 in my repo
> (https://people.debian.org/~praveen/gitlab/) without any issues.

Tested again - same error as before (which I expected, as the migration scripts 
did not change).

-nik


signature.asc
Description: PGP signature

Re: gitlab for stretch-backports - call for testing

[Pirate Praveen]

On Tuesday 05 June 2018 12:19 PM, Dominik George wrote:
> Hi,
> 
>> I was able to install it on a new machine and test basic functionality.
>> Next in my TODO list is testing updgrade from stretch version.
> 
> Did anything except the suite change?  Because upgrade from the stretch
> version is exactly what failed here, and testing if that wasn't fixed seems
> unnecessary ;).

Dominik,

I was able to update from gitlab 8 in stretch to gitlab 10 in my repo
(https://people.debian.org/~praveen/gitlab/) without any issues.

All,

You can see it running at https://gitlab10.fosscommunity.in/ (it was
working fine with a clean install before).

Blockers for getting it to official repo is
https://salsa.debian.org/ruby-team/gitlab/wikis/stretch-backports (3
transitions and 4 rc bugs). Any help welcome.

Especially, this ruby-encryptor bug ->
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880276 has been there
for a long time and upstream is not responding.

Thanks
Praveen



signature.asc
Description: OpenPGP digital signature

Re: gitlab for stretch-backports - call for testing

[Dominik George]

Hi,

> I was able to install it on a new machine and test basic functionality.
> Next in my TODO list is testing updgrade from stretch version.

Did anything except the suite change?  Because upgrade from the stretch
version is exactly what failed here, and testing if that wasn't fixed seems
unnecessary ;).

-nik


signature.asc
Description: PGP signature

Re: gitlab for stretch-backports - call for testing

[Pirate Praveen]

On Monday 04 June 2018 08:01 PM, Dominik George wrote:
> Any news about that migration, so I could test again?

Please try again from (update apt url, stretch changed to
stretch-backports) https://people.debian.org/~praveen/gitlab/

Many dependencies are now in official stretch-backports, but it will
take some more time before all dependencies are uploaded/accepted.

I was able to install it on a new machine and test basic functionality.
Next in my TODO list is testing updgrade from stretch version.



signature.asc
Description: OpenPGP digital signature

Re: gitlab for stretch-backports - call for testing

[Dominik George]

Hi,

On Sun, May 20, 2018 at 05:44:48PM +0200, Dominik George wrote:
> Quick note, upgrade path from stretch:
> 
> Caused by:
>  
> ActiveRecord::StatementInvalid: PG::UndefinedTable: ERROR:  relation 
> "features" does not exist
> LINE 5:WHERE a.attrelid = '"features"'::regclass  
>  
>   ^   
> 
> :   SELECT a.attname, format_type(a.atttypid, a.atttypmod),   
>  
>  pg_get_expr(d.adbin, d.adrelid), a.attnotnull, 
> a.atttypid, a.atttypmod
> FROM pg_attribute a LEFT JOIN pg_attrdef d
>  
>   ON a.attrelid = d.adrelid AND a.attnum = d.adnum
>  
>WHERE a.attrelid = '"features"'::regclass  
>  
>  AND a.attnum > 0 AND NOT a.attisdropped  
>  
>ORDER BY a.attnum
> 

Any news about that migration, so I could test again?

Cheers,
Nik


signature.asc
Description: PGP signature

Re: gitlab for stretch-backports - call for testing

[Pirate Praveen]

On ചൊവ്വ 08 മേയ് 2018 09:25 വൈകു, Pirate Praveen wrote:
> gitaly required ruby-rugged 0.27 and hence I updated ruby-rugged to
> 0.27. I'm in the process of updating gitlab to 10.7.3 which will work
> with ruby-rugged 0.27.

I have uploaded gitlab 10.7.3 and installation should work now, please
try again.



signature.asc
Description: OpenPGP digital signature

Re: gitlab for stretch-backports - call for testing

[Pirate Praveen]

On ചൊ, മേയ് 8, 2018 at 8:21 വൈകു, Dominik George 
 wrote:

Hi,

I cannot install gitlab from your repository:


Thanks for the report. I'm aware of this particular issue. See 
https://salsa.debian.org/ruby-team/gitlab/wikis/stretch-backports




Could not find gem 'rugged (~> 0.26.0)' in any of the gem sources 
listed in your

Gemfile or available on this machine.

ruby-rugged 0.27.0 is installed, though.



gitaly required ruby-rugged 0.27 and hence I updated ruby-rugged to 
0.27. I'm in the process of updating gitlab to 10.7.3 which will work 
with ruby-rugged 0.27.

Re: gitlab for stretch-backports - call for testing

[Dominik George]

Hi,

I cannot install gitlab from your repository:

Could not find gem 'rugged (~> 0.26.0)' in any of the gem sources listed in your
Gemfile or available on this machine.

ruby-rugged 0.27.0 is installed, though.

-nik


signature.asc
Description: PGP signature

Re: gitlab for stretch-backports - call for testing

[Pirate Praveen]

On ബു, മേയ് 2, 2018 at 6:30 വൈകു, Pirate Praveen 
 wrote:
I have rebuilt gitlab and all dependencies for stretch-backports and 
uploaded here https://people.debian.org/~praveen/gitlab/ (about 157 
ruby packages were rebuilt).


I'm tracking the blockers here 
https://salsa.debian.org/ruby-team/gitlab/wikis/home


Specifically, help with libgit2 update would be great. See 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869665#87 and 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897560#27


We need to disable linking with OpenSSL and it seems the option used 
with earlier version is no longer working.

Re: gitlab for stretch-backports - call for testing

[Pirate Praveen]

On വ്യാ, മേയ് 3, 2018 at 11:46 രാവിലെ, 
Leopold Palomo-Avellaneda  wrote:
Are you asking help for testing the package right? The bugs found 
reported via

bugs in debian or mails to the list?



You can report them as bugs. I have already found some more ruby 
packages for gitaly needs an update (strangely we did not notice this 
issue in unstable).


https://salsa.debian.org/go-team/packages/gitaly/blob/master/ruby/Gemfile 
(rugged, grpc and google-protobuf)


 My initial hope was to provide updates via stretch-backports, but 
sudden
 explosion of nodejs front end dependencies made that impossible. 
Now all
 nodejs modules are installed via npm/yarn and gitlab is moved to 
contrib.


But is this situation temporally? or do you plan to continue in this 
way in Buster?


I hope we will be in a better position in buster as I don't expect such 
huge jumps like this one. But we may need to do the same for buster 
depending on two factors 1. how hard the backporting really is, 2. how 
desperately we need the new features.





 More than a 100 node module packages are stuck in NEW for over 5-7
 months and not sure how to get it back in main. If you'd like to 
help,

 please volunteer with ftp team and help process the node modules.


I understand that when this packages were in main, gitlab will move 
to main

again. Is this correct?


Yes, these packages in NEW plus some more yet to be packaged. 
https://wiki.debian.org/Javascript/Nodejs/Tasks/gitlab has the status 
of dependencies. I hope to do the remaining once the packages in NEW 
starts moving again.

Re: gitlab for stretch-backports - call for testing

[Leopold Palomo-Avellaneda]

Hi!!

On 02/05/18 15:00, Pirate Praveen wrote:
> Hi team,
> 
> I have rebuilt gitlab and all dependencies for stretch-backports and
> uploaded here https://people.debian.org/~praveen/gitlab/ (about 157 ruby
> packages were rebuilt).


great


> It starting fine with an initial test, but found some errors in
> production.log. Any help in testing this would be welcome as I hope to
> provide stretch-backports as an upgrade path for gitlab currently in
> stretch (backporting security fixes to 8.13 is very difficult as code
> has diverged too much).

Are you asking help for testing the package right? The bugs found reported via
bugs in debian or mails to the list?

> My initial hope was to provide updates via stretch-backports, but sudden
> explosion of nodejs front end dependencies made that impossible. Now all
> nodejs modules are installed via npm/yarn and gitlab is moved to contrib.

But is this situation temporally? or do you plan to continue in this way in 
Buster?

> More than a 100 node module packages are stuck in NEW for over 5-7
> months and not sure how to get it back in main. If you'd like to help,
> please volunteer with ftp team and help process the node modules.

I understand that when this packages were in main, gitlab will move to main
again. Is this correct?

Best regards,

Leopold
-- 
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?



signature.asc
Description: OpenPGP digital signature

Re: gitlab for stretch-backports - call for testing

[Pirate Praveen]

[dropping -backports]

On ബുധന്‍ 02 മേയ് 2018 06:30 വൈകു, Pirate Praveen wrote:
> Hi team,
> 
> I have rebuilt gitlab and all dependencies for stretch-backports and
> uploaded here https://people.debian.org/~praveen/gitlab/ (about 157 ruby
> packages were rebuilt).

Bundler::GemNotFound: Your bundle is locked to i18n (0.8.1), but that
version could not be found in any of the sources listed in your Gemfile.

This looks like an issue with gem version mismatch. ButI wonder why this
was not an issue in sid even though ruby-i18n is still
0.7.0 there.

Any ideas?




signature.asc
Description: OpenPGP digital signature