Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-11-27 Thread Pirate Praveen 



On 2019, നവംബർ 27 2:04:19 PM IST, Romain Bignon  wrote:
>Hi,
>
>A new strange thing, I don't know if you encountered that, today at
>6h32
>packagekit run, tried to restart gitlab, and failed:

It'd be a good idea to turn off unattended upgrades in unstable. 
  
>Nov 27 06:32:24 weboob gitlab-unicorn[28831]: Bundler::GemNotFound:
>Could not find gem 'rubyzip (>= 1.2.2, ~> 1.2)' in any of the gem
>sources listed in your Gemfile.

ruby-zip was updated to 2.0.0.

>I had to install manually rubyzip with gem at the right version to fix
>gitlab.
>
>To understand, packagekit has updated something?

This should be fixed in latest version of gitlab.

>Romain

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

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-11-27 Thread Romain Bignon 
Hi,

A new strange thing, I don't know if you encountered that, today at 6h32
packagekit run, tried to restart gitlab, and failed:

Nov 27 06:32:18 weboob dbus-daemon[464]: [system] Activating via systemd: 
service name='org.freedesktop.PackageKit' unit='packagekit.service' requested 
by ':1.10456' (uid=0 pid=28562 comm="/usr/bin/gdbus call --system --dest 
org.freedeskto")
Nov 27 06:32:18 weboob systemd[1]: Starting PackageKit Daemon...
Nov 27 06:32:18 weboob PackageKit: daemon start
Nov 27 06:32:18 weboob dbus-daemon[464]: [system] Successfully activated 
service 'org.freedesktop.PackageKit'
Nov 27 06:32:18 weboob systemd[1]: Started PackageKit Daemon.
Nov 27 06:32:18 weboob gitlab-workhorse[20628]: git.weboob.org 46.229.168.139 - 
- [2019/11/27:06:32:18 +0100] "GET 
/P4ncake/devel/tree/6f5f41fe574ad35b11e024b7c10bb2950d0689b2 HTTP/1.1" 200 
40794 "" "Mozilla/5.0 (compatible; SemrushBot/6~bl; 
+http://www.semrush.com/bot.html)" %!f(int64=108)
Nov 27 06:32:19 weboob systemd[1]: Reloading.
Nov 27 06:32:19 weboob systemd[1]: /lib/systemd/system/dbus.socket:5: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update 
the unit file accordingly.
Nov 27 06:32:19 weboob systemd[1]: Configuration file 
/etc/systemd/system/postfix.service.d/override.conf is marked 
world-inaccessible. This has no effect as configuration data is accessible via 
APIs without restrictions. Proceeding anyway.
Nov 27 06:32:19 weboob systemd[1]: 
/lib/systemd/system/gitlab-sidekiq.service:18: Ignoring unknown escape 
sequences: "for i in 4 4 4 4 4 4 4 4; do sleep $i; (ps -h -o command -p 
$MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; done"
Nov 27 06:32:19 weboob systemd[1]: /lib/systemd/system/docker.socket:6: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/docker.sock → /run/docker.sock; please update the unit file 
accordingly.
Nov 27 06:32:20 weboob systemd[1]: Reloading.
Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/system/dbus.socket:5: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update 
the unit file accordingly.
Nov 27 06:32:20 weboob systemd[1]: Configuration file 
/etc/systemd/system/postfix.service.d/override.conf is marked 
world-inaccessible. This has no effect as configuration data is accessible via 
APIs without restrictions. Proceeding anyway.
Nov 27 06:32:20 weboob systemd[1]: 
/lib/systemd/system/gitlab-sidekiq.service:18: Ignoring unknown escape 
sequences: "for i in 4 4 4 4 4 4 4 4; do sleep $i; (ps -h -o command -p 
$MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; done"
Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/system/docker.socket:6: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/docker.sock → /run/docker.sock; please update the unit file 
accordingly.
Nov 27 06:32:20 weboob systemd[1]: Reloading.
Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/system/dbus.socket:5: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update 
the unit file accordingly.
Nov 27 06:32:20 weboob systemd[1]: Configuration file 
/etc/systemd/system/postfix.service.d/override.conf is marked 
world-inaccessible. This has no effect as configuration data is accessible via 
APIs without restrictions. Proceeding anyway.
Nov 27 06:32:20 weboob systemd[1]: 
/lib/systemd/system/gitlab-sidekiq.service:18: Ignoring unknown escape 
sequences: "for i in 4 4 4 4 4 4 4 4; do sleep $i; (ps -h -o command -p 
$MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; done"
Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/system/docker.socket:6: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/docker.sock → /run/docker.sock; please update the unit file 
accordingly.
Nov 27 06:32:20 weboob gitaly[20604]: time="2019-11-27T06:32:20+01:00" 
level=error msg="lstat /var/lib/gitlab/repositories/+gitaly/cache: no such file 
or directory" storage=default
Nov 27 06:32:20 weboob systemd[1]: Reloading.
Nov 27 06:32:21 weboob systemd[1]: /lib/systemd/system/dbus.socket:5: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update 
the unit file accordingly.
Nov 27 06:32:21 weboob systemd[1]: Configuration file 
/etc/systemd/system/postfix.service.d/override.conf is marked 
world-inaccessible. This has no effect as configuration data is accessible via 
APIs without restrictions. Proceeding anyway.
Nov 27 06:32:21 weboob systemd[1]: 
/lib/systemd/system/gitlab-sidekiq.service:18: Ignoring unknown escape 
sequences: "for i in 4 4 4 4 4 4 4 4; do sleep $i; (ps -h -o command -p 
$MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; done"
Nov 27 06:32:21 weboob

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-11-20 Thread Pirate Praveen 

On Thu, 14 Nov 2019 12:07:52 +0100 Romain Bignon  wrote:

Great it works, thank you. Please tell us when the issue is fixed in the
experimental repository and that we can upgrade all versions from this
repository, as it is currently somewhat a hot fix.


We are blocked in multiple projects to get a proper fix,

See https://github.com/grpc/grpc/issues/21226

1. protobuf needs to release version 3.11 (currently at 3.10.1),
then
2. grpc need to update its embedded copy of protobuf to this version,
then
3. gitlab and gitaly needs to update ruby-grpc-tools, ruby-grpc, protoc 
and protobuf to this version,

then
4. debian's version of protobuf and grpc should be updated to this version

So as a work around I have uploaded older versions of protobuf and grpc 
to my personal repo.


1. Add the following lines to your sources.list

deb https://people.debian.org/~praveen/protobuf/ experimental main contrib

2. Add my gpg keys to apt trusted keys

# wget https://people.debian.org/~praveen/gitlab/praveen.key.asc
# apt-key add praveen.key.asc
# apt update

3. Downgrade ruby-grpc, ruby-google-protobuf and update gitaly
# apt install ruby-google-protobuf=3.7.1-1 ruby-grpc=1.19.1-1
# apt install gitaly/experimental

Make sure gitaly version is at least 1.59.3+dfsg-2 (just uploaded, it 
will take some hours to show up in the archives)


4. Manually update Gemfile.lock and restart services.

# cd /usr/share/gitlab
# sudo -u gitlab truncate -s0 Gemfile.lock
# sudo -u gitlab bundle install --local
# systemctl restart gitlab-sidekiq
# systemctl restart gitlab gitaly

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-11-14 Thread Romain Bignon 
On 14/Nov - 07:45, Pirate Praveen wrote:
>  has protobuf 3.7 and grpc 1.19.
> You need to downgrade both and use gitaly 1.59.3+dfsg-1~bpo10+2 (which
> allows these versions).
> 
> And because of 
> you may need to regenrate Gemfile.lock
> 
> # cd /usr/share/gitlab
> # sudo -u gitlab truncate -s0 Gemfile.lock
> # sudo -u gitlab bundle install --local
> # systemctl restart gitlab-sidekiq
> # systemctl restart gitlab gitaly
> 
> I had to use a separate repo with protobuf 3.10 and grpc 1.23 ->
> https://people.debian.org/~praveen/protobuf/ to build gitaly
> 
> I'm keeping this bug open till we can use same version of protobuf for both
> gitaly build and gitlab. I have opened
> https://gitlab.com/gitlab-org/gitaly/issues/2164 to work with upstream on
> this

Great it works, thank you. Please tell us when the issue is fixed in the
experimental repository and that we can upgrade all versions from this
repository, as it is currently somewhat a hot fix.

Romain

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-11-13 Thread Pirate Praveen 

Control: retitle -1 gitlab ssh access broken with protobuf 3.10
Control: severity -1 serious

On ബു, Nov 13, 2019 at 23:44, Pirate Praveen 
 wrote:

On Mon, 11 Nov 2019 22:15:20 +0530 Pirate Praveen
mailto:prav...@onenetbeyond.org>> wrote:

 Control: retitle -1 ssh access fails with gitaly-upload-pack: fatal:
 error: %v
 On Sat, 2 Nov 2019 14:51:42 +0100 Romain Bignon > wrote:

 > Hello,
 >
 > The problem is still here, and is so not related to compatibility 
between

 > versions of gitlab/gitlab-shell/gitality…
 >
 > Is there anything I can do to find the origin of this issue?

 Fortunately or unfortunately the same error hit my instance as 
well. I'm

 digging deeper into it now.

 As a workaround you can use https access till we fix this (only ssh
 access is affected).


Found the root cause to be ruby-google-protobuf update from 3.7 to 
3.10.

But to actually get it work is tricky.

If we downgrade ruby-google-protobuf to 3.7.1, then gitaly fails to 
build.


 has protobuf 3.7 and grpc 
1.19. You need to downgrade both and use gitaly 1.59.3+dfsg-1~bpo10+2 
(which allows these versions).


And because of 
 you may need 
to regenrate Gemfile.lock


# cd /usr/share/gitlab
# sudo -u gitlab truncate -s0 Gemfile.lock
# sudo -u gitlab bundle install --local
# systemctl restart gitlab-sidekiq
# systemctl restart gitlab gitaly

I had to use a separate repo with protobuf 3.10 and grpc 1.23 -> 
https://people.debian.org/~praveen/protobuf/ to build gitaly


I'm keeping this bug open till we can use same version of protobuf for 
both gitaly build and gitlab. I have opened 
https://gitlab.com/gitlab-org/gitaly/issues/2164 to work with upstream 
on this

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-11-13 Thread Pirate Praveen 
On Mon, 11 Nov 2019 22:15:20 +0530 Pirate Praveen
 wrote:
> Control: retitle -1 ssh access fails with gitaly-upload-pack: fatal:
> error: %v
> On Sat, 2 Nov 2019 14:51:42 +0100 Romain Bignon  wrote:
> > Hello,
> > 
> > The problem is still here, and is so not related to compatibility between
> > versions of gitlab/gitlab-shell/gitality…
> > 
> > Is there anything I can do to find the origin of this issue?
> 
> Fortunately or unfortunately the same error hit my instance as well. I'm
> digging deeper into it now.
> 
> As a workaround you can use https access till we fix this (only ssh
> access is affected).

Found the root cause to be ruby-google-protobuf update from 3.7 to 3.10.
But to actually get it work is tricky.

If we downgrade ruby-google-protobuf to 3.7.1, then gitaly fails to build.

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-11-11 Thread Pirate Praveen 
Control: retitle -1 ssh access fails with gitaly-upload-pack: fatal:
error: %v
On Sat, 2 Nov 2019 14:51:42 +0100 Romain Bignon  wrote:
> Hello,
> 
> The problem is still here, and is so not related to compatibility between
> versions of gitlab/gitlab-shell/gitality…
> 
> Is there anything I can do to find the origin of this issue?

Fortunately or unfortunately the same error hit my instance as well. I'm
digging deeper into it now.

As a workaround you can use https access till we fix this (only ssh
access is affected).

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-11-02 Thread Romain Bignon 
Hello,

The problem is still here, and is so not related to compatibility between
versions of gitlab/gitlab-shell/gitality…

Is there anything I can do to find the origin of this issue?

Romain

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-23 Thread Romain Bignon 
On 23/Oct - 14:31, Pirate Praveen wrote:
> just share apt policy gitaly for confirmation and the error messages once
> more (after you restart gitaly and gitlab services).

gitaly:
  Installed: 1.58.0+dfsg-2
  Candidate: 1.58.0+dfsg-2
  Version table:
 *** 1.58.0+dfsg-2 100
  1 http://ftp.de.debian.org/debian experimental/main amd64 Packages
100 /var/lib/dpkg/status
 1.20.0+debian-1+b1 -1
 -1 http://ftp.de.debian.org/debian unstable/main amd64 Packages

And the error message client side:

$ git fetch
gitaly-upload-pack: fatal: error: %v
fatal: Could not read from remote repository.

Server side:

time="2019-10-23T15:53:54+02:00" level=info msg="finished HTTP request" 
duration=0.03395727 gitaly_embedded=false method=POST pid=8834 
url="http://localhost:8080/api/v4/internal/allowed;
time="2019-10-23T15:53:54+02:00" level=info msg="executing git command" 
command="gitaly-upload-pack unix:/run/gitlab/sockets/private/gitaly.socket 
{\"repository\":{},\"gl_repository\":\"project-2\",\"gl_project_path\":\"romain/weboob\",\"gl_id\":\"key-3\",\"gl_username\":\"romain\",\"git_config_options\":[],\"git_protocol\":null}"
 pid=8834 user="user with id key-3"
time="2019-10-23T15:53:54+02:00" level=error msg="error: %v" error="rpc error: 
code = InvalidArgument desc = Storage can not be found by name ''" pid=8834

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-23 Thread Pirate Praveen 



On Wed, Oct 23, 2019 at 09:40, Romain Bignon  wrote:

On 22/Oct - 22:47, Pirate Praveen wrote:

 All those packages are available in experimental. I have updated
  with these packages added to the 
list of

 pcakges needed from experimental.


I've installed these packages and correctly upgraded gitlab and all
dependencies, even gitlab-shell, and the problem still exists…

What can I do to help debugging?



just share apt policy gitaly for confirmation and the error messages 
once more (after you restart gitaly and gitlab services).



Romain

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-23 Thread Romain Bignon 
On 22/Oct - 22:47, Pirate Praveen wrote:
> All those packages are available in experimental. I have updated
> https://wiki.debian.org/gitlab with these packages added to the list of
> pcakges needed from experimental.

I've installed these packages and correctly upgraded gitlab and all
dependencies, even gitlab-shell, and the problem still exists…

What can I do to help debugging?

Romain

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-22 Thread Pirate Praveen 



On Tue, Oct 22, 2019 at 19:02, Romain Bignon  wrote:

On 22/Oct - 19:18, Pirate Praveen wrote:
 This is building fine on my system. So uploaded binary included as 
work

 around.


Note that I see a newer version of gitlb available:

 root@weboob ~ # apt-cache policy gitlab
gitlab:
  Installed: 12.1.14-1
  Candidate: 12.1.14-1
  Version table:
 12.2.8-1 1
  1  experimental/contrib 
amd64 Packages

 *** 12.1.14-1 100
100 /var/lib/dpkg/status
 11.8.10+dfsg-1 -1
 -1  unstable/contrib amd64 
Packages


But it is not possible to install it as there are broken dependencies:

 root@weboob ~ # apt install gitlab/experimental
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '12.2.8-1' (Debian:experimental [all]) for 'gitlab'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gitlab : Depends: ruby-invisible-captcha (>= 0.12.1~) but it is not 
installable
  Depends: ruby-gitlab-sidekiq-fetcher (>= 0.5.1~) but 
0.4.0-2 is to be installed

  Depends: ruby-redis (>= 4.0~) but 3.3.5-1 is to be installed
  Depends: ruby-gitlab-labkit (>= 0.4.2-2~) but 0.4.2-1 is to 
be installed

  Depends: ruby-statistics but it is not installable
  Depends: ruby-gitaly (>= 1.58~) but 1.37.0+dfsg-1 is to be 
installed

E: Unable to correct problems, you have held broken packages.

Do you think you'll be able to upload a newer fixed version of gitaly 
soon? Or

is there any workaround?

All those packages are available in experimental. I have updated 
https://wiki.debian.org/gitlab with these packages added to the list of 
pcakges needed from experimental.



Romain

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-22 Thread Romain Bignon 
On 22/Oct - 19:18, Pirate Praveen wrote:
> This is building fine on my system. So uploaded binary included as work
> around.

Note that I see a newer version of gitlb available:

 root@weboob ~ # apt-cache policy gitlab
gitlab:
  Installed: 12.1.14-1
  Candidate: 12.1.14-1
  Version table:
 12.2.8-1 1
  1 http://ftp.de.debian.org/debian experimental/contrib amd64 Packages
 *** 12.1.14-1 100
100 /var/lib/dpkg/status
 11.8.10+dfsg-1 -1
 -1 http://ftp.de.debian.org/debian unstable/contrib amd64 Packages

But it is not possible to install it as there are broken dependencies:

 root@weboob ~ # apt install gitlab/experimental
Reading package lists... Done
Building dependency tree
Reading state information... Done
Selected version '12.2.8-1' (Debian:experimental [all]) for 'gitlab'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gitlab : Depends: ruby-invisible-captcha (>= 0.12.1~) but it is not installable
  Depends: ruby-gitlab-sidekiq-fetcher (>= 0.5.1~) but 0.4.0-2 is to be 
installed
  Depends: ruby-redis (>= 4.0~) but 3.3.5-1 is to be installed
  Depends: ruby-gitlab-labkit (>= 0.4.2-2~) but 0.4.2-1 is to be 
installed
  Depends: ruby-statistics but it is not installable
  Depends: ruby-gitaly (>= 1.58~) but 1.37.0+dfsg-1 is to be installed
E: Unable to correct problems, you have held broken packages.

Do you think you'll be able to upload a newer fixed version of gitaly soon? Or
is there any workaround?

Romain

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-22 Thread Pirate Praveen 
On Tue, 22 Oct 2019 18:36:20 +0530 Pirate Praveen
 wrote:> It seems 1.58.0+dfsg-1 build failed
> 
> https://buildd.debian.org/status/fetch.php?pkg=gitaly=amd64=1.58.0%2Bdfsg-1=1571598656=0
> 

This is building fine on my system. So uploaded binary included as work
around.

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-22 Thread Pirate Praveen 



On Tue, Oct 22, 2019 at 14:54, Romain Bignon  wrote:

Hi,

On 21/Oct - 21:21, Pirate Praveen wrote:

 > At least for Romain that seems to be the problem.
 >
 > ii  gitaly   1.47.3+debian-1
 >
 > $ apt policy gitaly
 > gitaly:
 >   Installed: 1.53.3+debian-1~bpo10+1
 >   Candidate: 1.53.3+debian-1~bpo10+1
 >   Version table:
 >  *** 1.53.3+debian-1~bpo10+1 500
 > 500 <>
 > buster-backports/main amd64 Packages
 > 100 /var/lib/dpkg/status

 This is actually a bug as minimum version for gitaly was not 
updated in

 gitlab.


1.47.3+debian-1 is the latest version available on Debian 
experimental.


It seems 1.58.0+dfsg-1 build failed

https://buildd.debian.org/status/fetch.php?pkg=gitaly=amd64=1.58.0%2Bdfsg-1=1571598656=0

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-22 Thread Romain Bignon 
Hi,

On 21/Oct - 21:21, Pirate Praveen wrote:
> > At least for Romain that seems to be the problem.
> > 
> > ii  gitaly   1.47.3+debian-1
> > 
> > $ apt policy gitaly
> > gitaly:
> >   Installed: 1.53.3+debian-1~bpo10+1
> >   Candidate: 1.53.3+debian-1~bpo10+1
> >   Version table:
> >  *** 1.53.3+debian-1~bpo10+1 500
> > 500 
> > buster-backports/main amd64 Packages
> > 100 /var/lib/dpkg/status
> 
> This is actually a bug as minimum version for gitaly was not updated in
> gitlab.

1.47.3+debian-1 is the latest version available on Debian experimental.

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-21 Thread Pirate Praveen 



On Mon, Oct 21, 2019 at 21:09, Pirate Praveen 
 wrote:

At least for Romain that seems to be the problem.

ii  gitaly   1.47.3+debian-1

$ apt policy gitaly
gitaly:
  Installed: 1.53.3+debian-1~bpo10+1
  Candidate: 1.53.3+debian-1~bpo10+1
  Version table:
 *** 1.53.3+debian-1~bpo10+1 500
500 
buster-backports/main amd64 Packages
100 /var/lib/dpkg/status


This is actually a bug as minimum version for gitaly was not updated in 
gitlab.

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-21 Thread Pirate Praveen 
On Mon, 21 Oct 2019 15:47:47 +0200 =?UTF-8?Q?Patrick_Matth=c3=a4i?=
 wrote:
> Hi,
> 
> this friday I also tried to upgrade our setup from 11.5.10+dfsg-1 to
> 12.0.8 and 12.2.8-1, both with the result, that cloning about http still
> works, but ssh was not useable anymore with the same error.

I'm running the same version in https://git.fosscommunity.in and git
clone over ssh still works.

> From the gitlab-shell log I just get:
> 
> time="2019-10-18T15:54:35+02:00" level=info msg="executing git command"
> command="gitaly-upload-pack
> unix:/run/gitlab/sockets/private/gitaly.socket
> {\"repository\":{},\"gl_repository\":\"project-49\",\"gl_project_path\":\"customer/X\",\"gl_id\":\"key-44\",\"gl_username\":\"YYY\",\"git_config_options\":[],\"git_protocol\":null}"
> pid=7378 user="user with id key-44"
> time="2019-10-18T15:54:35+02:00" level=error msg="error: %v" error="rpc
> error: code = InvalidArgument desc = Storage can not be found by name
> ''" pid=7378

It could be a new option either in gitaly or gitlab configurations. Are
you using gitaly on the same server? Do you have the required version of
gitaly?

At least for Romain that seems to be the problem.

ii  gitaly   1.47.3+debian-1

$ apt policy gitaly
gitaly:
  Installed: 1.53.3+debian-1~bpo10+1
  Candidate: 1.53.3+debian-1~bpo10+1
  Version table:
 *** 1.53.3+debian-1~bpo10+1 500
500 https://people.debian.org/~praveen/gitlab
buster-backports/main amd64 Packages
100 /var/lib/dpkg/status

> And that with both versions (12.0 and 12.2). I tried also to fix it by
> packaging gitlab-shell 9.3 for my own, but it didn't helped..
> 
> -- 
> /*
> Mit freundlichem Gruß / With kind regards,
>  Patrick Matthäi
>  GNU/Linux Debian Developer
> 
>   Blog: http://www.linux-dev.org/
> E-Mail: pmatth...@debian.org
> patr...@linux-dev.org
> */
>

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-10-19 Thread Romain Bignon 
Package: gitlab
Version: 12.1.14-1
Severity: important

Dear Maintainer,

During the installation of the package, this warning is displayed:

GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... FAIL. Please update 
gitlab-shell to 9.3.0 from 9.1.0

But currently the latest version of gitlab-shell available in
experimental is 9.1.0.

It is not possible anymore to interact with the repository through ssh:

$ git fetch
gitaly-upload-pack: fatal: error: %v
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
$

Server-side, this error is displayed in gitlab-shell logs:

time="2019-10-19T11:04:07+02:00" level=info msg="finished HTTP request" 
duration=0.014533625 gitaly_embedded=false method=POST pid=426 
url="http://localhost:8080/api/v4/internal/allowed;
time="2019-10-19T11:04:07+02:00" level=info msg="executing git command" 
command="gitaly-upload-pack unix:/run/gitlab/sockets/private/gitaly.socket 
{\"repository\":{},\"gl_repository\":\"project-2\",\"gl_project_path\":\"romain/weboob\",\"gl_id\":\"key-3\",\"gl_username\":\"romain\",\"git_config_options\":[],\"git_protocol\":null}"
 pid=426 user="user with id key-3"
time="2019-10-19T11:04:07+02:00" level=error msg="error: %v" error="rpc error: 
code = InvalidArgument desc = Storage can not be found by name ''" pid=426

I don't know if the two issues are related, but there is a good chance.

The solution would be to package gitlab-shell 9.3.0 in experimental.

Best regards,

Romain

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gitlab depends on:
ii  asciidoctor 2.0.10-2
ii  bc  1.07.1-2+b2
ii  bundler 1.17.3-3
ii  bzip2   1.0.8-2
ii  dbconfig-pgsql  2.0.13
ii  debconf [debconf-2.0]   1.5.73
ii  gitlab-common   12.1.14-1
ii  gitlab-workhorse8.5.2+debian-1
ii  libjs-bootstrap4 [node-bootstrap]   4.3.1+dfsg2-1
ii  libjs-pdf   1.5.188+dfsg-1
ii  libjs-popper.js [node-popper.js]1.14.6+ds2-2
ii  libjs-uglify2.8.29-6
ii  lsb-base11.1.0
ii  nginx   1.16.1-2
ii  nginx-extras [nginx]1.16.1-2
ii  node-autosize   4.0.2~dfsg1-3
ii  node-axios  0.19.0+dfsg-2
ii  node-brace-expansion1.1.8-1
ii  node-cache-loader   2.0.1-2
ii  node-chart.js   2.7.3+dfsg-5
ii  node-core-js2.4.1-2
ii  node-css-loader 1.0.1-1
ii  node-d3 4.13.0-10
ii  node-d3-array   1.2.4-2
ii  node-d3-axis1.0.12-2
ii  node-d3-brush   1.0.6-3
ii  node-d3-ease1.0.5-2
ii  node-d3-scale   1.0.7-6
ii  node-d3-selection   1.4.0-5
ii  node-d3-shape   1.3.5-2
ii  node-d3-time1.0.11-3
ii  node-d3-time-format 2.1.3-2
ii  node-d3-transition  1.2.0-4
ii  node-dateformat 3.0.0-1
ii  node-exports-loader 0.7.0-2
ii  node-file-loader3.0.1-1
ii  node-fuzzaldrin-plus0.5.0+dfsg-3
ii  node-glob   7.1.3-2
ii  node-imports-loader 0.8.0-2
ii  node-jed1.1.1-1
ii  node-jquery 3.4.0+dfsg-1
ii  node-jquery-ujs 1.2.2-2
ii  node-jquery.waitforimages   2.4.0+ds-1
ii