Gitaly-upload-pack: Fatal: Upload-pack Failed Fatal: Could Not Read From Remote Repository.
Debian Problems written report logs - #942633
gitlab ssh access broken with protobuf three.10
Toggle useless messages
Written report forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Problems#942633; Package gitlab. (Sabbatum, 19 Oct 2019 09:21:05 GMT) (total text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
New Bug written report received and forwarded. Copy sent to Debian Scarlet Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Sat, nineteen October 2019 09:21:05 GMT) (full text, mbox, link).
Message #5 received at submit@bugs.debian.org (full text, mbox, respond):
Package: gitlab Version: 12.1.14-1 Severity: important Dearest Maintainer, During the installation of the package, this alarm is displayed: GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... Neglect. Please update gitlab-vanquish to ix.iii.0 from nine.one.0 Merely currently the latest version of gitlab-shell bachelor 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: %5 fatal: Could not read from remote repository. Please make sure you take the correct admission rights and the repository exists. $ Server-side, this mistake is displayed in gitlab-shell logs: time="2019-10-19T11:04:07+02:00" level=info msg="finished HTTP request" elapsing=0.014533625 gitaly_embedded=false method=Mail service pid=426 url="http://localhost:8080/api/v4/internal/allowed" fourth dimension="2019-ten-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\":\"projection-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-three" time="2019-10-19T11:04:07+02:00" level=fault msg="mistake: %v" error="rpc error: lawmaking = InvalidArgument desc = Storage tin can not be establish by name ''" pid=426 I don't know if the ii issues are related, but at that place is a good adventure. The solution would exist to packet gitlab-shell 9.3.0 in experimental. All-time regards, Romain -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable'), (i, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux four.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-viii, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), Linguistic communication=en_US:en (charmap=UTF-8) Vanquish: /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.one-2+b2 2 bundler i.17.3-3 2 bzip2 1.0.8-2 two dbconfig-pgsql ii.0.thirteen ii debconf [debconf-2.0] 1.v.73 ii gitlab-mutual 12.1.xiv-1 ii gitlab-workhorse 8.5.2+debian-i ii libjs-bootstrap4 [node-bootstrap] 4.3.1+dfsg2-1 ii libjs-pdf 1.5.188+dfsg-1 two libjs-popper.js [node-popper.js] 1.14.vi+ds2-2 ii libjs-uglify 2.eight.29-six ii lsb-base of operations 11.1.0 ii nginx 1.16.1-2 ii nginx-extras [nginx] 1.xvi.ane-2 two node-autosize iv.0.2~dfsg1-3 ii node-axios 0.19.0+dfsg-2 2 node-brace-expansion 1.1.8-1 ii node-cache-loader 2.0.1-2 ii node-chart.js 2.7.3+dfsg-5 ii node-core-js two.4.1-ii two node-css-loader 1.0.i-1 two node-d3 4.13.0-x ii node-d3-array i.2.iv-ii two node-d3-centrality i.0.12-2 ii node-d3-brush one.0.vi-3 ii node-d3-ease 1.0.5-ii two node-d3-calibration 1.0.7-half dozen ii node-d3-choice 1.4.0-5 ii node-d3-shape 1.3.5-2 ii node-d3-fourth dimension i.0.11-3 two node-d3-time-format 2.1.iii-2 2 node-d3-transition 1.ii.0-4 ii node-dateformat 3.0.0-i ii node-exports-loader 0.7.0-two 2 node-file-loader 3.0.one-1 two node-fuzzaldrin-plus 0.5.0+dfsg-3 two node-glob 7.1.iii-2 ii node-imports-loader 0.8.0-2 ii node-jed 1.1.1-one 2 node-jquery 3.4.0+dfsg-1 ii node-jquery-ujs one.2.2-2 2 node-jquery.waitforimages 2.4.0+ds-1 ii node-js-cookie ii.two.0-ii ii node-jszip 3.2.two+dfsg-1 ii node-jszip-utils 0.0.2+dfsg-one ii node-mousetrap ane.6.1+ds-i ii node-pikaday ane.8.0-1 two node-raven-js 3.22.1+dfsg-2 ii node-raw-loader 1.0.0-2 two node-iii-orbit-controls 82.i.0-ii ii node-three-stl-loader 1.0.half dozen-2 2 node-timeago.js 3.0.ii+dfsg-5 two node-underscore 1.nine.1~dfsg-i 2 node-url-loader 2.0.i-ane ii node-vue-resources 1.five.i+dfsg-five 2 node-webpack-stats-plugin 0.two.1-1 ii node-worker-loader 2.0.0-2 ii nodejs 10.15.2~dfsg-2 ii openssh-customer ane:eight.1p1-one ii postfix [mail-ship-agent] 3.4.seven-1 two postgresql-customer eleven+207 two postgresql-client-eleven [postgresql-client] 11.5-3sid2 2 postgresql-client-nine.six [postgresql-client] ix.vi.ten-0+deb9u1 ii postgresql-contrib 11+207 ii puma iii.12.0-2+b1 ii rake 12.3.iii-ane two redis-server v:v.0.six-one ii scarlet 1:2.5.2 ii ruby-ace-rails-ap 4.ane.i-i ii ruby-acme-client 2.0.3-2 ii ruddy-activerecord-explain-analyze 0.one.0-ii 2 ruby-acts-every bit-taggable-on half-dozen.0.0-3 two ruby-addressable 2.5.2-1 ii ruby-akismet two.0.0-1 ii red-apollo-upload-server 2.0.0~beta3-1 ii red-asana 0.8.1-two ii ruby-asciidoctor-include-ext 0.3.one-2 ii ruby-asciidoctor-plantuml 0.0.9-1 2 ruby-attr-encrypted 3.1.0-2 2 ruby-babosa i.0.two-2 ii blood-red-base32 0.3.two-four ii ruby-batch-loader ane.4.1+dfsg.i-1 ii ruby-bcrypt-pbkdf 1.0.one-1 2 ruby-benchmark-ips 2.seven.ii-1 ii ruby-benchmark-memory 0.i.two-2 ii cerise-bootstrap-form iv.two.0-1 two scarlet-browser 2.5.3-ane ii crimson-carrierwave 1.3.1-2 ii carmine-charlock-holmes 0.seven.6-1 ii cherry-red-chronic 0.10.ii-three 2 ruby-chronic-duration 0.10.vi-1 2 ruby-commonmarker 0.17.ix-1+b1 ii scarlet-connection-pool 2.2.2-ane ii crimson-creole 0.5.0-2 2 blood-red-default-value-for 3.2.0-1 ii cherry-red-device-detector 1.0.1-ii ii ruby-devise four.vi.2-i ii ruby-devise-two-factor 3.0.3-2 two carmine-diffy 3.ii.1-1 two ruby-discordrb-webhooks 3.3.0-1 ii ruby-doorkeeper 4.4.2-i ii ruby-doorkeeper-openid-connect one.five.5-1 ii ruby-ed25519 1.2.four-1+b1 two ruby-email-reply-trimmer 0.1.6-i ii crimson-escape-utils one.2.ane-i+b1 two carmine-excon 0.60.0-1 2 ruby-faraday 0.15.4-3 2 reddish-fast-bare 1.0.0-1+b1 two carmine-flipper [ruby-flipper-active-support-cache-store] 0.13.0-3 pn ruby-red-flipper-active-record <none> ii cerise-flowdock 0.vii.i-one two ruddy-fog-aliyun 0.three.2-3 two reddish-fog-aws three.v.ii-1 two ruby-fog-cadre 2.1.0-three ii cherry-fog-google one.8.2-2 ii blood-red-fog-local 0.6.0-ane ii crimson-fog-openstack ane.0.8-ii ii ruby-fog-rackspace 0.1.6-2 ii ruby-red-fogbugz 0.2.1-three ii crimson-font-crawly-rails four.seven.0.iv-ane ii cerise-fugit 1.three.3+gh-1 ii ruby-gemojione 3.three.0-1 ii cerise-gettext-i18n-rails ane.8.0-1 ii ruby-gettext-i18n-runway-js 1.iii.0+dfsg-2 ii ruby-gitaly [cerise-gitaly-proto] i.37.0+dfsg-1 ii ruddy-github-markup ane.7.0+dfsg-ii 2 ruby-gitlab-labkit 0.4.ii-one ii ruby-red-gitlab-sidekiq-fetcher 0.4.0-2 two scarlet-gon vi.two.1-ane ii blood-red-google-api-customer 0.28.iv-i ii ruby-google-protobuf iii.10.0-i two ruby-red-googleauth 0.8.0-2 ii red-gpgme 2.0.19-1 2 cherry-red-grape one.1.0-two 2 cerise-grape-entity 0.7.1-ane 2 ruby-grape-logging i.vii.0-1 ii cherry-grape-path-helpers 1.1.0-1 ii ruby-graphiql-track 1.4.x-1 ii ruby-graphql 1.viii.4-ane 2 cerise-grpc 1.23.0-1 ii cherry-red-hamlit 2.9.ii-2 two ruby-hangouts-chat 0.0.5-2 ii ruby-hashie-forbidden-attributes 0.1.1-1 two ruby-health-cheque 2.6.0-ane ii ruby-hipchat 1.5.2-three ii ruby-red-html-pipeline 2.8.4-ane two ruby-html2text 0.2.0-1 ii scarlet-httparty 0.17.0-1 ii ruby-icalendar 2.4.i-2 two ruddy-influxdb 0.2.iii-2 ii ruby-jira 1.5.0-one ii crimson-jquery-atwho-rail 1.5.4+dfsg-1 two reddish-js-regex 3.ane.1-1 ii ruby-jwt 2.1.0-1 ii carmine-kaminari one.0.one-4 2 scarlet-kgio 2.11.two-1+b1 two scarlet-kubeclient 4.3.0-1 2 ruby-licensee 8.9.two-one ii ruby-lograge 0.10.0-1 ii ruby-loofah 2.2.three+dfsg-1 ii blood-red-mail-room 0.nine.1-2 ii red-retentiveness-profiler 0.ix.xiv-2 ii ruby-method-source 0.9.two-1 ii ruby-mimemagic 0.iii.2+dfsg-one ii ruby-mini-magick 4.9.2-1.ane 2 ruby-nakayoshi-fork 0.0.iv-1 two crimson-internet-ldap 0.16.1-i 2 ruby-internet-ssh 1:5.two.0-1 ii ruby-nokogiri 1.10.4+dfsg1-i ii cerise-ntlm 0.6.1-2 ii blood-red-oauth2 i.4.1-2 ii ruby-octokit 4.13.0+gh-1 ii ruby-omniauth 1.8.1-1 2 carmine-omniauth-auth0 2.0.0-ane ii ruby-omniauth-authentiq 0.iii.3-1 ii scarlet-omniauth-azure-oauth2 0.0.10-1 2 ruby-omniauth-cas3 1.1.4-2 ii scarlet-omniauth-oversupply 2.4.0-1 ii ruby-omniauth-facebook 4.0.0-2 ii ruby-omniauth-github i.3.0-1 two scarlet-omniauth-gitlab 1.0.2-ane ii ruby-red-omniauth-google-oauth2 0.half-dozen.0-one ii crimson-omniauth-kerberos 0.3.0-3 ii ruby-omniauth-ldap 2.1.ane-1 ii cherry-omniauth-oauth2-generic 0.2.2-i 2 red-omniauth-openid-connect 0.3.1-ane 2 red-omniauth-salesforce one.0.5-2 two ruby-omniauth-saml 1.10.0-1 ii blood-red-omniauth-shibboleth 1.3.0-one two ruby-omniauth-twitter 1.4.0-ane 2 crimson-omniauth-ultraauth 0.0.two-1.one 2 ruddy-org 0.ix.12-2 ii ruby-parser iii.11.0-one ii ruddy-peek 1.0.1-1 2 ruby-peek-gc 0.0.ii-i ii ruby-peek-pg 1.three.0-1 2 ruby-peek-rblineprof 0.2.0-ane ii ruby-peek-redis ane.two.0-1 ii carmine-pg 1.i.3-3+b1 ii blood-red-posix-spawn 0.three.thirteen-2+b1 ii ruby-premailer-runway 1.10.three-1 2 ruby-prof 0.17.0+dfsg-3+b1 ii cherry-red-progressbar 1.9.0-2 ii ruby-prometheus-client-mmap 0.nine.x-1 ii blood-red-rack 2.0.7-2 ii ruby-rack-attack iv.four.1-1 ii ruby-rack-cors one.0.ii-one ii cherry-red-rack-oauth2 1.nine.3-2 ii ruby-rack-proxy 0.half dozen.1-2 ii ruby-runway two:v.2.3+dfsg-1 ii ruddy-rails-deprecated-sanitizer 1.0.three-3 ii red-rails-i18n 5.i.2-2 ii ruby-rainbow iii.0.0-two ii ruby-raindrops 0.19.0-ane+b2 ii ruby-rbtrace 0.four.10-1+b1 two reddish-re2 one.1.ane-two+b3 ii carmine-recaptcha 4.xi.1-ii ii carmine-redcloth 4.3.2-iii+b1 ii red-redis 3.3.5-1 ii ruby-redis-namespace 1.6.0-1 2 cherry-red-redis-rail v.0.2-three two red-asking-store one.three.0-ane ii scarlet-responders 2.4.0-3 ii red-rouge 3.8.0-1 ii ruby-rqrcode-rails3 0.i.seven-1 ii ruby-rugged 0.28.1+ds-one two red-sanitize 4.half dozen.six-two ii ruddy-sassc two.0.1-2 ii ruby-sassc-runway ii.1.2-3 ii ruby-seed-fu 2.three.7-3 ii red-spotter-raven 2.9.0-1 ii ruby-settingslogic 2.0.9-iii ii cerise-sidekiq 5.2.7+dfsg-1 ii ruby-sidekiq-cron 1.i.0-iii two ruddy-slack-notifier i.5.1-2 ii ruby-sprockets 3.7.2-1 ii ruddy-sshkey ii.0.0-1 ii ruby-state-machines-activerecord 0.v.i-2 2 red-sys-filesystem 1.ane.vii-2 ii cherry-red-job-list 2.2.0-1 ii ruby-toml-rb 1.0.0-2 2 ruby-truncato 0.seven.eleven-one 2 cherry-red-u2f 0.2.i-2 ii carmine-uglifier 2.vii.2+dfsg-2 ii ruby-unf 0.1.4-2 two carmine-unf-ext 0.0.vii.5-1+b1 ii ruby-unicorn-worker-killer 0.4.iv-1 ii ruby-validates-hostname one.0.7-i ii reddish-version-sorter 2.two.four-ane ii ruby-virtus 1.0.5-3 ii ruby-vmstat two.3.0-2+b1 ii ruby-webpack-rails 0.ix.11+git-1 ii ruby-wikicloth 0.8.1+dfsg-4 two cerise-cipher 1.two.two-1 ii ucf 3.0038+nmu1 two unicorn five.4.1-2 ii webpack 4.vii.0-3 ii yarnpkg 1.13.0-iii Versions of packages gitlab recommends: ii certbot 0.39.0-1 ii gitaly ane.47.3+debian-i gitlab suggests no packages. -- debconf information: * gitlab/database-type: pgsql * gitlab/ssl: true gitlab/pgsql/changeconf: imitation gitlab/purge_data: truthful gitlab/install-mistake: arrest gitlab/remove-error: abort gitlab/internal/skip-preseed: false * gitlab/letsencrypt: false gitlab/missing-db-package-mistake: abort gitlab/upgrade-error: abort gitlab/pgsql/authmethod-admin: ident gitlab/remote/newhost: localhost gitlab/db/dbname: gitlab_production gitlab/pgsql/admin-user: postgres gitlab/purge: false gitlab/pgsql/method: TCP/IP gitlab/dbconfig-remove: true gitlab/pgsql/authmethod-user: password * gitlab/dbconfig-install: true gitlab/upgrade-backup: true gitlab/dbconfig-upgrade: truthful gitlab/dbconfig-reinstall: false * gitlab/fqdn: git.weboob.org * gitlab/user: gitlab gitlab/db/app-user: gitlab@localhost gitlab/pgsql/manualconf: * gitlab/remote/host: localhost gitlab/letsencrypt_email: gitlab/pgsql/no-empty-passwords: gitlab/passwords-practice-not-match: gitlab/internal/reconfiguring: false gitlab/remote/port: Message sent on to Romain Bignon <romain@symlink.me>:
Problems#942633. (Mon, 21 Oct 2019 xiv:06:06 GMT) (full text, mbox, link).
Message #8 received at 942633-submitter@bugs.debian.org (full text, mbox, respond):
[Bulletin part ane (text/plain, inline)]
Hi, this friday I also tried to upgrade our setup from 11.5.10+dfsg-ane to 12.0.viii and 12.2.8-1, both with the result, that cloning almost http still works, but ssh was not useable anymore with the aforementioned error. From the gitlab-beat out log I only go: 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\":\"projection-49\",\"gl_project_path\":\"customer/XXXXX\",\"gl_id\":\"central-44\",\"gl_username\":\"YYYYYYY\",\"git_config_options\":[],\"git_protocol\":zilch}" pid=7378 user="user with id fundamental-44" time="2019-10-18T15:54:35+02:00" level=error msg="error: %v" error="rpc fault: code = InvalidArgument desc = Storage can not be constitute by name ''" pid=7378 And that with both versions (12.0 and 12.2). I tried likewise 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/ Electronic mail: pmatthaei@debian.org patrick@linux-dev.org */ [Message part 2 (text/html, inline)]
Data forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby-red Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Mon, 21 October 2019 15:42:02 GMT) (total text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Extra info received and forwarded to list. Copy sent to Debian Scarlet Extras Maintainers <pkg-scarlet-extras-maintainers@lists.alioth.debian.org>. (Mon, 21 Oct 2019 15:42:02 GMT) (total text, mbox, link).
Message #13 received at 942633@bugs.debian.org (full text, mbox, answer):
On Mon, 21 October 2019 xv:47:47 +0200 =?UTF-8?Q?Patrick_Matth=c3=a4i?= <pmatthaei@debian.org> wrote: > Hello, > > this friday I besides tried to upgrade our setup from 11.v.10+dfsg-1 to > 12.0.8 and 12.2.8-ane, both with the result, that cloning most http yet > works, only ssh was not useable anymore with the same mistake. I'thou running the same version in https://git.fosscommunity.in and git clone over ssh even so works. > From the gitlab-shell log I only 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/XXXXX\",\"gl_id\":\"primal-44\",\"gl_username\":\"YYYYYYY\",\"git_config_options\":[],\"git_protocol\":null}" > pid=7378 user="user with id primal-44" > time="2019-10-18T15:54:35+02:00" level=error msg="mistake: %v" error="rpc > error: code = InvalidArgument desc = Storage can non exist found past name > ''" pid=7378 It could be a new option either in gitaly or gitlab configurations. Are y'all 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 ane.47.iii+debian-1 $ apt policy gitaly gitaly: Installed: ane.53.3+debian-1~bpo10+1 Candidate: 1.53.three+debian-i~bpo10+1 Version table: *** one.53.3+debian-ane~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-trounce 9.3 for my own, only it didn't helped.. > > -- > /* > Mit freundlichem Gruß / With kind regards, > Patrick Matthäi > GNU/Linux Debian Programmer > > Blog: http://www.linux-dev.org/ > E-Mail: pmatthaei@debian.org > patrick@linux-dev.org > */ > Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Monday, 21 Oct 2019 15:54:03 GMT) (total text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Extra info received and forwarded to list. Copy sent to Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Mon, 21 Oct 2019 15:54:03 GMT) (full text, mbox, link).
Message #18 received at 942633@bugs.debian.org (full text, mbox, reply):
[Message role 1 (text/plain, inline)]
On Mon, Oct 21, 2019 at 21:09, Pirate Praveen <praveen@onenetbeyond.org> wrote: > At least for Romain that seems to be the problem. > > 2 gitaly 1.47.3+debian-ane > > $ apt policy gitaly > gitaly: > Installed: 1.53.iii+debian-1~bpo10+1 > Candidate: 1.53.iii+debian-1~bpo10+1 > Version tabular array: > *** 1.53.3+debian-1~bpo10+1 500 > 500 <https://people.debian.org/~praveen/gitlab> > buster-backports/primary amd64 Packages > 100 /var/lib/dpkg/status This is actually a issues as minimum version for gitaly was not updated in gitlab.
[Message part 2 (text/html, inline)]
Inverse Bug championship to 'update minimum version of gitaly to >= 1.53.3' from 'gitlab: Experimental gitlab requires gitshell 9.three.0 but only 9.one.0 is packaged'. Request was from Pirate Praveen <praveen@onenetbeyond.org> to command@bugs.debian.org. (Mon, 21 Oct 2019 17:12:03 GMT) (full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby-red Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Tue, 22 Oct 2019 13:03:06 GMT) (full text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
Extra info received and forwarded to listing. Copy sent to Debian Ruby Extras Maintainers <pkg-cherry-red-extras-maintainers@lists.alioth.debian.org>. (Tue, 22 October 2019 xiii:03:06 GMT) (full text, mbox, link).
Message #25 received at 942633@bugs.debian.org (total text, mbox, reply):
How-do-you-do, On 21/Oct - 21:21, Pirate Praveen wrote: > > At to the lowest degree for Romain that seems to be the problem. > > > > ii gitaly 1.47.3+debian-i > > > > $ apt policy gitaly > > gitaly: > > Installed: one.53.3+debian-ane~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/chief amd64 Packages > > 100 /var/lib/dpkg/status > > This is actually a problems equally minimum version for gitaly was not updated in > gitlab. 1.47.three+debian-1 is the latest version bachelor on Debian experimental.
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Cerise Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Problems#942633; Package gitlab. (Tue, 22 Oct 2019 thirteen:09:03 GMT) (full text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Extra info received and forwarded to list. Copy sent to Debian Crimson Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Tue, 22 October 2019 13:09:03 GMT) (full text, mbox, link).
Message #30 received at 942633@bugs.debian.org (full text, mbox, answer):
[Bulletin part 1 (text/plain, inline)]
On Tue, Oct 22, 2019 at 14:54, Romain Bignon <romain@symlink.me> wrote: > Howdy, > > On 21/Oct - 21:21, Pirate Praveen wrote: >> > At to the lowest degree for Romain that seems to be the problem. >> > >> > ii gitaly ane.47.three+debian-1 >> > >> > $ apt policy gitaly >> > gitaly: >> > Installed: 1.53.3+debian-i~bpo10+one >> > Candidate: one.53.3+debian-i~bpo10+one >> > Version tabular array: >> > *** 1.53.3+debian-1~bpo10+i 500 >> > 500 <<https://people.debian.org/~praveen/gitlab>> >> > buster-backports/chief amd64 Packages >> > 100 /var/lib/dpkg/status >> >> This is really a problems every bit minimum version for gitaly was not >> updated in >> gitlab. > > one.47.3+debian-1 is the latest version available on Debian > experimental. It seems ane.58.0+dfsg-1 build failed https://buildd.debian.org/status/fetch.php?pkg=gitaly&arch=amd64&ver=i.58.0%2Bdfsg-1&stamp=1571598656&raw=0
[Bulletin part 2 (text/html, inline)]
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-scarlet-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Bundle gitlab. (Tue, 22 Oct 2019 13:51:03 GMT) (full text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Extra info received and forwarded to list. Re-create sent to Debian Cerise Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Tue, 22 Oct 2019 thirteen:51:03 GMT) (total text, mbox, link).
Message #35 received at 942633@bugs.debian.org (full text, mbox, reply):
On Tue, 22 Oct 2019 xviii:36:20 +0530 Pirate Praveen <praveen@onenetbeyond.org> wrote:> It seems 1.58.0+dfsg-1 build failed > > https://buildd.debian.org/condition/fetch.php?pkg=gitaly&arch=amd64&ver=one.58.0%2Bdfsg-1&stamp=1571598656&raw=0 > This is edifice fine on my arrangement. So uploaded binary included as piece of work around.
Data forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Problems#942633; Bundle gitlab. (Tue, 22 Oct 2019 17:03:07 GMT) (full text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
Extra info received and forwarded to list. Copy sent to Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Tue, 22 Oct 2019 17:03:07 GMT) (total text, mbox, link).
Message #40 received at 942633@bugs.debian.org (total text, mbox, reply):
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 run into a newer version of gitlb bachelor: root@weboob ~ # apt-cache policy gitlab gitlab: Installed: 12.1.14-one Candidate: 12.1.14-1 Version table: 12.two.8-ane one 1 http://ftp.de.debian.org/debian experimental/contrib amd64 Packages *** 12.1.14-1 100 100 /var/lib/dpkg/status 11.viii.10+dfsg-1 -one -1 http://ftp.de.debian.org/debian unstable/contrib amd64 Packages But information technology 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 land data... Done Selected version '12.2.eight-1' (Debian:experimental [all]) for 'gitlab' Some packages could not be installed. This may hateful that yous accept requested an impossible state of affairs or if yous are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The post-obit information may help to resolve the situation: The following packages have unmet dependencies: gitlab : Depends: crimson-invisible-captcha (>= 0.12.one~) but information technology is not installable Depends: ruby-gitlab-sidekiq-fetcher (>= 0.5.1~) simply 0.4.0-2 is to exist installed Depends: cherry-redis (>= 4.0~) but 3.3.five-1 is to exist installed Depends: reddish-gitlab-labkit (>= 0.four.2-two~) simply 0.iv.ii-1 is to be installed Depends: ruby-statistics but it is non installable Depends: ruby-red-gitaly (>= ane.58~) but 1.37.0+dfsg-1 is to exist installed Eastward: Unable to right problems, you have held broken packages. Practise you call up yous'll be able to upload a newer fixed version of gitaly shortly? Or is at that place any workaround? Romain
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-crimson-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Parcel gitlab. (Tue, 22 Oct 2019 17:21:09 GMT) (full text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Actress info received and forwarded to list. Copy sent to Debian Ruby Extras Maintainers <pkg-cherry-extras-maintainers@lists.alioth.debian.org>. (Tue, 22 Oct 2019 17:21:09 GMT) (full text, mbox, link).
Message #45 received at 942633@bugs.debian.org (full text, mbox, reply):
[Message function 1 (text/patently, inline)]
On Tue, Oct 22, 2019 at nineteen:02, Romain Bignon <romain@symlink.me> wrote: > On 22/Oct - xix:eighteen, Pirate Praveen wrote: >> This is building fine on my system. So uploaded binary included as >> work >> effectually. > > Note that I meet a newer version of gitlb bachelor: > > root@weboob ~ # apt-enshroud policy gitlab > gitlab: > Installed: 12.ane.fourteen-1 > Candidate: 12.1.fourteen-1 > Version tabular array: > 12.2.eight-1 1 > ane <http://ftp.de.debian.org/debian> experimental/contrib > amd64 Packages > *** 12.one.14-one 100 > 100 /var/lib/dpkg/condition > 11.8.ten+dfsg-1 -1 > -1 <http://ftp.de.debian.org/debian> unstable/contrib amd64 > Packages > > But it is not possible to install information technology as there are broken dependencies: > > root@weboob ~ # apt install gitlab/experimental > Reading package lists... Washed > Building dependency tree > Reading state information... Done > Selected version '12.2.8-ane' (Debian:experimental [all]) for 'gitlab' > Some packages could not be installed. This may hateful that you lot have > requested an incommunicable state of affairs or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The post-obit information may help to resolve the situation: > > The post-obit packages have unmet dependencies: > gitlab : Depends: scarlet-invisible-captcha (>= 0.12.1~) merely it is not > installable > Depends: ruby-gitlab-sidekiq-fetcher (>= 0.v.ane~) merely > 0.four.0-two is to be installed > Depends: blood-red-redis (>= 4.0~) merely three.3.5-1 is to be installed > Depends: ruby-gitlab-labkit (>= 0.4.ii-ii~) but 0.four.2-1 is to > exist installed > Depends: carmine-statistics but information technology is not installable > Depends: ruby-gitaly (>= 1.58~) but one.37.0+dfsg-ane is to be > installed > E: Unable to correct problems, you lot have held cleaved 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 accept updated https://wiki.debian.org/gitlab with these packages added to the list of pcakges needed from experimental. > Romain
[Message function 2 (text/html, inline)]
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Cherry-red Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Wednesday, 23 Oct 2019 07:45:03 GMT) (full text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
Actress info received and forwarded to list. Re-create sent to Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Wed, 23 Oct 2019 07:45:03 GMT) (full text, mbox, link).
Message #50 received at 942633@bugs.debian.org (full text, mbox, respond):
On 22/Oct - 22:47, Pirate Praveen wrote: > All those packages are available in experimental. I take updated > https://wiki.debian.org/gitlab with these packages added to the listing of > pcakges needed from experimental. I've installed these packages and correctly upgraded gitlab and all dependencies, even gitlab-trounce, and the problem even so exists… What can I exercise to assistance debugging? Romain
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-reddish-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Wednesday, 23 October 2019 09:03:03 GMT) (full text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Extra info received and forwarded to list. Copy sent to Debian Reddish Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Wednesday, 23 October 2019 09:03:03 GMT) (full text, mbox, link).
Bulletin #55 received at 942633@bugs.debian.org (total text, mbox, answer):
[Message role 1 (text/manifestly, inline)]
On Midweek, Oct 23, 2019 at 09:40, Romain Bignon <romain@symlink.me> wrote: > 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-beat, and the problem nonetheless exists… > > What can I do to help debugging? > just share apt policy gitaly for confirmation and the fault messages once again (subsequently you restart gitaly and gitlab services). > Romain >
[Bulletin function 2 (text/html, inline)]
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-red-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Wed, 23 Oct 2019 13:57:03 GMT) (full text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
Extra info received and forwarded to list. Copy sent to Debian Ruby Extras Maintainers <pkg-scarlet-extras-maintainers@lists.alioth.debian.org>. (Wed, 23 Oct 2019 13:57:03 GMT) (full text, mbox, link).
Message #sixty received at 942633@bugs.debian.org (full text, mbox, reply):
On 23/Oct - xiv:31, Pirate Praveen wrote: > but share apt policy gitaly for confirmation and the error letters 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 i.20.0+debian-ane+b1 -1 -one http://ftp.de.debian.org/debian unstable/main amd64 Packages And the error bulletin customer side: $ git fetch gitaly-upload-pack: fatal: fault: %v fatal: Could not read from remote repository. Server side: time="2019-x-23T15:53:54+02:00" level=info msg="finished HTTP request" duration=0.03395727 gitaly_embedded=false method=Mail service pid=8834 url="http://localhost:8080/api/v4/internal/allowed" fourth dimension="2019-10-23T15:53:54+02:00" level=info msg="executing git command" command="gitaly-upload-pack unix:/run/gitlab/sockets/individual/gitaly.socket {\"repository\":{},\"gl_repository\":\"project-ii\",\"gl_project_path\":\"romain/weboob\",\"gl_id\":\"key-3\",\"gl_username\":\"romain\",\"git_config_options\":[],\"git_protocol\":null}" pid=8834 user="user with id central-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 Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Sat, 02 Nov 2019 xiii:54:03 GMT) (total text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
Extra info received and forwarded to listing. Re-create sent to Debian Ruby Extras Maintainers <pkg-reddish-extras-maintainers@lists.alioth.debian.org>. (Sat, 02 November 2019 13:54:03 GMT) (total text, mbox, link).
Message #65 received at 942633@bugs.debian.org (full text, mbox, respond):
Howdy, The problem is however here, and is so not related to compatibility betwixt versions of gitlab/gitlab-shell/gitality… Is at that place anything I can practice to find the origin of this result? Romain
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Monday, eleven Nov 2019 16:48:03 GMT) (full text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Extra info received and forwarded to list. Re-create sent to Debian Cherry-red Extras Maintainers <pkg-blood-red-extras-maintainers@lists.alioth.debian.org>. (Mon, 11 Nov 2019 xvi:48:03 GMT) (full text, mbox, link).
Message #70 received at 942633@bugs.debian.org (full text, mbox, reply):
Control: retitle -1 ssh access fails with gitaly-upload-pack: fatal: error: %v On Sat, ii Nov 2019 14:51:42 +0100 Romain Bignon <romain@symlink.me> wrote: > Hello, > > The problem is still hither, and is and then not related to compatibility between > versions of gitlab/gitlab-shell/gitality… > > Is at that place anything I tin can practice to find the origin of this issue? Fortunately or unfortunately the same error hit my instance equally well. I'm excavation deeper into it now. As a workaround you tin can use https access till we fix this (but ssh access is afflicted).
Changed Problems title to 'ssh access fails with gitaly-upload-pack: fatal:' from 'update minimum version of gitaly to >= 1.53.3'. Asking was from Pirate Praveen <praveen@onenetbeyond.org> to 942633-submit@bugs.debian.org. (Mon, 11 Nov 2019 16:48:03 GMT) (full text, mbox, link).
Severity gear up to 'grave' from 'important' Request was from Pirate Praveen <praveen@onenetbeyond.org> to control@bugs.debian.org. (Mon, 11 Nov 2019 17:00:06 GMT) (full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Issues#942633; Packet gitlab. (Wed, thirteen Nov 2019 18:18:03 GMT) (full text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Extra info received and forwarded to list. Copy sent to Debian Crimson Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Midweek, xiii Nov 2019 xviii:xviii:03 GMT) (total text, mbox, link).
Message #81 received at 942633@bugs.debian.org (full text, mbox, reply):
On Mon, xi Nov 2019 22:xv:20 +0530 Pirate Praveen <praveen@onenetbeyond.org> wrote: > Control: retitle -1 ssh access fails with gitaly-upload-pack: fatal: > error: %5 > On Sat, 2 Nov 2019 14:51:42 +0100 Romain Bignon <romain@symlink.me> wrote: > > Hello, > > > > The problem is all the same here, and is so non related to compatibility between > > versions of gitlab/gitlab-shell/gitality… > > > > Is at that place annihilation I can practise to find the origin of this issue? > > Fortunately or unfortunately the same error hit my instance as well. I'm > excavation deeper into it now. > > Every bit a workaround you can use https access till nosotros set this (only ssh > access is affected). Establish the root cause to be blood-red-google-protobuf update from iii.7 to 3.ten. Merely to actually become information technology work is catchy. If we downgrade carmine-google-protobuf to 3.vii.1, then gitaly fails to build.
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Thu, xiv November 2019 02:21:07 GMT) (full text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Extra info received and forwarded to list. Re-create sent to Debian Carmine Extras Maintainers <pkg-cherry-red-extras-maintainers@lists.alioth.debian.org>. (Thu, xiv November 2019 02:21:07 GMT) (total text, mbox, link).
Message #86 received at 942633@bugs.debian.org (full text, mbox, reply):
[Message part 1 (text/apparently, inline)]
Command: retitle -1 gitlab ssh access cleaved with protobuf 3.10 Control: severity -i serious On ബു, Nov 13, 2019 at 23:44, Pirate Praveen <praveen@onenetbeyond.org> wrote: > On Mon, 11 Nov 2019 22:15:20 +0530 Pirate Praveen > <praveen@onenetbeyond.org <mailto:praveen@onenetbeyond.org>> wrote: >> Command: retitle -ane ssh access fails with gitaly-upload-pack: fatal: >> error: %v >> On Sat, 2 Nov 2019 14:51:42 +0100 Romain Bignon <romain@symlink.me >> <mailto:romain@symlink.me>> wrote: >> > Howdy, >> > >> > The trouble is withal here, and is so non related to compatibility >> between >> > versions of gitlab/gitlab-shell/gitality… >> > >> > Is there anything I can do to find the origin of this upshot? >> >> Fortunately or unfortunately the same error hit my example every bit >> well. I'chiliad >> digging deeper into it now. >> >> As a workaround y'all tin can use https access till nosotros fix this (only ssh >> access is afflicted). > > Constitute the root cause to be carmine-google-protobuf update from 3.7 to > 3.10. > But to actually go it piece of work is tricky. > > If we downgrade ruby-google-protobuf to 3.7.1, then gitaly fails to > build. <https://people.debian.org/~praveen/gitlab/> has protobuf 3.7 and grpc 1.nineteen. You need to downgrade both and use gitaly 1.59.3+dfsg-i~bpo10+2 (which allows these versions). And because of <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944698> you lot 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 split up repo with protobuf 3.10 and grpc ane.23 -> https://people.debian.org/~praveen/protobuf/ to build gitaly I'm keeping this bug open up till we tin can apply 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
[Message part 2 (text/html, inline)]
Changed Bug title to 'gitlab ssh access broken with protobuf 3.10' from 'ssh access fails with gitaly-upload-pack: fatal:'. Request was from Pirate Praveen <praveen@onenetbeyond.org> to 942633-submit@bugs.debian.org. (Thu, 14 November 2019 02:21:07 GMT) (full text, mbox, link).
Severity set to 'serious' from 'grave' Request was from Pirate Praveen <praveen@onenetbeyond.org> to 942633-submit@bugs.debian.org. (Thu, xiv November 2019 02:21:08 GMT) (full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby-red Extras Maintainers <pkg-carmine-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Thu, 14 Nov 2019 11:xv:03 GMT) (full text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
Actress info received and forwarded to list. Copy sent to Debian Carmine Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Thu, fourteen Nov 2019 11:15:03 GMT) (full text, mbox, link).
Message #95 received at 942633@bugs.debian.org (total text, mbox, reply):
On 14/Nov - 07:45, Pirate Praveen wrote: > <https://people.debian.org/~praveen/gitlab/> has protobuf 3.vii 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 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944698> > yous 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 utilize a carve up repo with protobuf 3.10 and grpc 1.23 -> > https://people.debian.org/~praveen/protobuf/ to build gitaly > > I'm keeping this issues open till we tin use same version of protobuf for both > gitaly build and gitlab. I have opened > https://gitlab.com/gitlab-org/gitaly/bug/2164 to work with upstream on > this Great information technology works, thanks. Please tell united states when the consequence is stock-still in the experimental repository and that we can upgrade all versions from this repository, as it is currently somewhat a hot fix. Romain
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Scarlet Extras Maintainers <pkg-carmine-extras-maintainers@lists.alioth.debian.org>:
Issues#942633; Bundle gitlab. (Wed, twenty November 2019 12:09:03 GMT) (full text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Extra info received and forwarded to listing. Copy sent to Debian Ruby-red Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Wed, 20 Nov 2019 12:09:03 GMT) (total text, mbox, link).
Message #102 received at 942633@bugs.debian.org (full text, mbox, answer):
On Thu, 14 Nov 2019 12:07:52 +0100 Romain Bignon <romain@symlink.me> wrote: > Great information technology works, thank you. Please tell us when the issue is stock-still in the > experimental repository and that nosotros tin upgrade all versions from this > repository, as it is currently somewhat a hot fix. We are blocked in multiple projects to get a proper ready, Run across https://github.com/grpc/grpc/issues/21226 1. protobuf needs to release version 3.11 (currently at iii.10.i), so 2. grpc demand to update its embedded re-create of protobuf to this version, then 3. gitlab and gitaly needs to update ruby-grpc-tools, ruby-red-grpc, protoc and protobuf to this version, then 4. debian's version of protobuf and grpc should exist updated to this version So as a work around I have uploaded older versions of protobuf and grpc to my personal repo. i. Add the post-obit lines to your sources.listing 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.fundamental.asc # apt-primal add praveen.key.asc # apt update 3. Downgrade ruby-grpc, ruby-google-protobuf and update gitaly # apt install carmine-google-protobuf=three.7.1-1 scarlet-grpc=1.nineteen.1-ane # apt install gitaly/experimental Brand sure gitaly version is at to the lowest degree 1.59.3+dfsg-2 (just uploaded, it will take some hours to show upwards 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
Added tag(due south) stock-still-upstream. Request was from debian-bts-link@lists.debian.org to command@bugs.debian.org. (Thu, 21 November 2019 17:27:12 GMT) (full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby-red Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Wed, 27 Nov 2019 08:39:03 GMT) (full text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
Extra info received and forwarded to list. Re-create sent to Debian Blood-red Extras Maintainers <pkg-crimson-extras-maintainers@lists.alioth.debian.org>. (Wed, 27 Nov 2019 08:39:03 GMT) (full text, mbox, link).
Message #109 received at 942633@bugs.debian.org (total text, mbox, reply):
Hi, A new foreign affair, I don't know if yous encountered that, today at 6h32 packagekit run, tried to restart gitlab, and failed: November 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:eighteen weboob systemd[i]: Starting PackageKit Daemon... Nov 27 06:32:xviii weboob PackageKit: daemon showtime Nov 27 06:32:eighteen weboob dbus-daemon[464]: [system] Successfully activated service 'org.freedesktop.PackageKit' November 27 06:32:18 weboob systemd[one]: Started PackageKit Daemon. Nov 27 06:32:xviii 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.i" 200 40794 "" "Mozilla/5.0 (compatible; SemrushBot/6~bl; +http://www.semrush.com/bot.html)" %!f(int64=108) Nov 27 06:32:nineteen weboob systemd[1]: Reloading. November 27 06:32:19 weboob systemd[1]: /lib/systemd/system/dbus.socket:v: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; delight update the unit file accordingly. Nov 27 06:32:nineteen weboob systemd[ane]: Configuration file /etc/systemd/system/postfix.service.d/override.conf is marked globe-inaccessible. This has no effect as configuration information is attainable via APIs without restrictions. Proceeding anyway. November 27 06:32:19 weboob systemd[i]: /lib/systemd/organization/gitlab-sidekiq.service:eighteen: Ignoring unknown escape sequences: "for i in four iv 4 4 iv four 4 4; do sleep $i; (ps -h -o command -p $MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && get out 0; done" November 27 06:32:xix weboob systemd[1]: /lib/systemd/arrangement/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. November 27 06:32:20 weboob systemd[1]: Reloading. Nov 27 06:32:20 weboob systemd[one]: /lib/systemd/system/dbus.socket:five: 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:xx weboob systemd[ane]: Configuration file /etc/systemd/organisation/postfix.service.d/override.conf is marked world-inaccessible. This has no outcome as configuration data is accessible via APIs without restrictions. Proceeding anyway. Nov 27 06:32:twenty weboob systemd[one]: /lib/systemd/arrangement/gitlab-sidekiq.service:eighteen: Ignoring unknown escape sequences: "for i in 4 iv four 4 4 4 4 four; do sleep $i; (ps -h -o command -p $MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; done" Nov 27 06:32:xx weboob systemd[one]: /lib/systemd/system/docker.socket:six: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; delight update the unit of measurement file accordingly. Nov 27 06:32:20 weboob systemd[one]: Reloading. November 27 06:32:twenty weboob systemd[1]: /lib/systemd/system/dbus.socket:five: 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 upshot 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:xviii: Ignoring unknown escape sequences: "for i in 4 iv 4 four four 4 4 4; exercise sleep $i; (ps -h -o control -p $MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && leave 0; washed" Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/organization/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. November 27 06:32:twenty 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 November 27 06:32:20 weboob systemd[one]: Reloading. Nov 27 06:32:21 weboob systemd[ane]: /lib/systemd/organization/dbus.socket:5: ListenStream= references a path beneath legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file appropriately. Nov 27 06:32:21 weboob systemd[1]: Configuration file /etc/systemd/organisation/postfix.service.d/override.conf is marked world-inaccessible. This has no effect as configuration information is accessible via APIs without restrictions. Proceeding anyhow. Nov 27 06:32:21 weboob systemd[1]: /lib/systemd/system/gitlab-sidekiq.service:18: Ignoring unknown escape sequences: "for i in iv 4 4 iv iv 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 systemd[ane]: /lib/systemd/arrangement/docker.socket:six: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file appropriately. Nov 27 06:32:21 weboob systemd[1]: Stopped target GitLab Service. Nov 27 06:32:21 weboob systemd[1]: Stopping GitLab Service. Nov 27 06:32:21 weboob systemd[1]: gitlab.service: Succeeded. Nov 27 06:32:21 weboob systemd[ane]: Stopped GitLab Services. Nov 27 06:32:21 weboob systemd[1]: Stopping GitLab Services... Nov 27 06:32:21 weboob systemd[1]: Stopping Gitlab mailroom Worker... Nov 27 06:32:21 weboob systemd[1]: Stopping GitLab Sidekiq Worker... Nov 27 06:32:21 weboob systemd[one]: Stopping Gitlab Workhorse handles ho-hum HTTP requests for Gitlab.... Nov 27 06:32:21 weboob gitlab-sidekiq[20644]: 2019-11-27T05:32:21.133Z 20644 TID-goijjrii4 INFO: Shutting down Nov 27 06:32:21 weboob gitlab-sidekiq[20644]: 2019-eleven-27T05:32:21.133Z 20644 TID-goin08v3c INFO: Scheduler exiting... November 27 06:32:21 weboob gitlab-sidekiq[20644]: 2019-xi-27T05:32:21.133Z 20644 TID-goijjrii4 INFO: Terminating placidity workers Nov 27 06:32:21 weboob gitlab-sidekiq[20644]: 2019-xi-27T05:32:21.135Z 20644 TID-goin0a0a0 INFO: Scheduler exiting... Nov 27 06:32:21 weboob systemd[i]: gitlab-workhorse.service: Succeeded. Nov 27 06:32:21 weboob systemd[i]: Stopped Gitlab Workhorse handles slow HTTP requests for Gitlab.. Nov 27 06:32:21 weboob systemd[1]: gitlab-mailroom.service: Succeeded. Nov 27 06:32:21 weboob systemd[1]: Stopped Gitlab mailroom Worker. November 27 06:32:21 weboob systemd[i]: Stopping GitLab Unicorn Server... November 27 06:32:21 weboob systemd[1]: gitlab-unicorn.service: Succeeded. Nov 27 06:32:21 weboob systemd[1]: Stopped GitLab Unicorn Server. Nov 27 06:32:21 weboob gitlab-sidekiq[20644]: 2019-11-27T05:32:21.635Z 20644 TID-goijjrii4 INFO: Pausing to allow workers to finish... Nov 27 06:32:23 weboob gitlab-sidekiq[20644]: 2019-eleven-27T05:32:23.639Z 20644 TID-goijjrii4 INFO: Bye! Nov 27 06:32:23 weboob systemd[1]: gitlab-sidekiq.service: Succeeded. Nov 27 06:32:23 weboob systemd[1]: Stopped GitLab Sidekiq Worker. November 27 06:32:23 weboob systemd[1]: Stopping Advanced key-value store... Nov 27 06:32:24 weboob systemd[one]: redis-server.service: Succeeded. Nov 27 06:32:24 weboob systemd[1]: Stopped Advanced key-value shop. Nov 27 06:32:24 weboob systemd[i]: Starting Advanced key-value store... Nov 27 06:32:24 weboob systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) afterwards starting time: No such file or directory Nov 27 06:32:24 weboob systemd[1]: Started Avant-garde key-value shop. November 27 06:32:24 weboob systemd[i]: Starting GitLab Sidekiq Worker... Nov 27 06:32:24 weboob systemd[1]: gitlab-unicorn.service: Ignoring invalid environment consignment 'for i in $(grep -v '#' /etc/gitlab/gitlab-debian.conf | cut -d=-f 1)': /etc/default/gitlab Nov 27 06:32:24 weboob systemd[1]: gitlab-unicorn.service: Ignoring invalid environment assignment 'consign app_user=${gitlab_user}': /etc/default/gitlab Nov 27 06:32:24 weboob systemd[1]: Started GitLab Unicorn Server. November 27 06:32:24 weboob systemd[i]: Started Gitlab mailroom Worker. Nov 27 06:32:24 weboob systemd[one]: Started Gitlab Workhorse handles slow HTTP requests for Gitlab.. Nov 27 06:32:24 weboob gitlab-workhorse[28833]: time="2019-11-27T06:32:24+01:00" level=info msg=Starting version="gitlab-workhorse (unknown version)" Nov 27 06:32:24 weboob gitlab-unicorn[28831]: fatal: not a git repository (or any of the parent directories): .git Nov 27 06:32:24 weboob gitlab-unicorn[28831]: fatal: not a git repository (or any of the parent directories): .git Nov 27 06:32:24 weboob gitlab-unicorn[28831]: bundler: failed to load control: unicorn_rails (/usr/local/bin/unicorn_rails) Nov 27 06:32:24 weboob gitlab-unicorn[28831]: Bundler::GemNotFound: Could not observe gem 'rubyzip (>= 1.2.2, ~> 1.2)' in any of the jewel sources listed in your Gemfile. Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-one.17.iii/lib/bundler/resolver.rb:287:in `block in verify_gemfile_dependencies_are_found!' November 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/resolver.rb:255:in `each' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/resolver.rb:255:in `verify_gemfile_dependencies_are_found!' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-ane.17.3/lib/bundler/resolver.rb:49:in `outset' November 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/resolver.rb:22:in `resolve' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/definition.rb:258:in `resolve' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.iii/lib/bundler/definition.rb:170:in `specs' November 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/definition.rb:237:in `specs_for' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-one.17.3/lib/bundler/definition.rb:226:in `requested_specs' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-one.17.3/lib/bundler/runtime.rb:108:in `block in definition_method' November 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.three/lib/bundler/runtime.rb:20:in `setup' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-i.17.3/lib/bundler.rb:107:in `setup' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/setup.rb:20:in `<top (required)>' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/lib/cherry/2.v.0/rubygems/core_ext/kernel_require.rb:59:in `crave' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/lib/blood-red/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' Nov 27 06:32:24 weboob systemd[ane]: gitlab-unicorn.service: Master process exited, lawmaking=exited, status=1/FAILURE November 27 06:32:24 weboob systemd[1]: gitlab-unicorn.service: Failed with outcome 'go out-code'. November 27 06:32:24 weboob gitlab-mailroom[28832]: fatal: not a git repository (or any of the parent directories): .git November 27 06:32:24 weboob gitlab-mailroom[28832]: fatal: not a git repository (or any of the parent directories): .git November 27 06:32:24 weboob gitlab-sidekiq[28829]: fatal: not a git repository (or any of the parent directories): .git Nov 27 06:32:24 weboob gitlab-sidekiq[28829]: fatal: not a git repository (or whatever of the parent directories): .git Nov 27 06:32:24 weboob gitlab-mailroom[28832]: /usr/share/rubygems-integration/all/gems/bundler-i.17.3/lib/bundler/resolver.rb:287:in `block in verify_gemfile_dependencies_are_found!': Could not discover jewel 'rubyzip (>= ane.ii.two, ~> one.ii)' in whatever of the gem sources listed in your Gemfile. (Bundler::GemNotFound) Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/resolver.rb:255:in `each' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-one.17.3/lib/bundler/resolver.rb:255:in `verify_gemfile_dependencies_are_found!' November 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/resolver.rb:49:in `start' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-one.17.three/lib/bundler/resolver.rb:22:in `resolve' November 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-ane.17.3/lib/bundler/definition.rb:258:in `resolve' November 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-ane.17.iii/lib/bundler/definition.rb:170:in `specs' November 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/definition.rb:237:in `specs_for' November 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-one.17.3/lib/bundler/definition.rb:226:in `requested_specs' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:108:in `block in definition_method' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-i.17.3/lib/bundler/runtime.rb:xx:in `setup' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-ane.17.iii/lib/bundler.rb:107:in `setup' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-1.17.3/lib/bundler/setup.rb:twenty:in `<superlative (required)>' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/lib/ruby/ii.5.0/rubygems/core_ext/kernel_require.rb:59:in `crave' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/lib/ruby/2.v.0/rubygems/core_ext/kernel_require.rb:59:in `require' Nov 27 06:32:24 weboob systemd[ane]: gitlab-mailroom.service: Primary process exited, code=exited, status=one/FAILURE Nov 27 06:32:24 weboob systemd[1]: gitlab-mailroom.service: Failed with outcome 'exit-code'. I had to install manually rubyzip with gem at the right version to fix gitlab. To understand, packagekit has updated something? Romain Information forwarded to debian-bugs-dist@lists.debian.org, Debian Carmine Extras Maintainers <pkg-cerise-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Midweek, 27 Nov 2019 09:03:06 GMT) (full text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Actress info received and forwarded to list. Copy sent to Debian Reddish Extras Maintainers <pkg-scarlet-extras-maintainers@lists.alioth.debian.org>. (Midweek, 27 Nov 2019 09:03:06 GMT) (full text, mbox, link).
Message #114 received at 942633@bugs.debian.org (total text, mbox, reply):
On 2019, നവംബർ 27 2:04:19 PM IST, Romain Bignon <romain@symlink.me> wrote: >Hi, > >A new foreign thing, I don't know if you encountered that, today at >6h32 >packagekit run, tried to restart gitlab, and failed: It'd be a expert idea to plow off unattended upgrades in unstable. >Nov 27 06:32:24 weboob gitlab-unicorn[28831]: Bundler::GemNotFound: >Could not discover precious stone 'rubyzip (>= one.2.two, ~> ane.2)' in any of the jewel >sources listed in your Gemfile. ruby-zip was updated to ii.0.0. >I had to install manually rubyzip with gem at the right version to fix >gitlab. > >To sympathise, packagekit has updated something? This should be fixed in latest version of gitlab. >Romain -- Sent from my Android device with Grand-9 Mail. Delight alibi my brevity.
Reply sent to Pirate Praveen <praveen@debian.org>:
You lot have taken responsibility. (Thu, 26 Mar 2020 12:24:05 GMT) (full text, mbox, link).
Notification sent to Romain Bignon <romain@symlink.me>:
Bug acknowledged past programmer. (Thu, 26 Mar 2020 12:24:05 GMT) (full text, mbox, link).
Message #119 received at 942633-close@bugs.debian.org (full text, mbox, answer):
Source: gitlab Source-Version: 12.8.vi-1 Washed: Pirate Praveen <praveen@debian.org> We believe that the bug you reported is fixed in the latest version of gitlab, which is due to be installed in the Debian FTP archive. A summary of the changes betwixt this version and the previous one is attached. Thank you for reporting the bug, which will at present be closed. If you have further comments please address them to 942633@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen <praveen@debian.org> (supplier of updated gitlab package) (This bulletin was generated automatically at their asking; if you believe that there is a problem with it please contact the archive administrators past mailing ftpmaster@ftp-primary.debian.org) -----Brainstorm PGP SIGNED Message----- Hash: SHA512 Format: 1.viii Engagement: Thu, 26 Mar 2020 17:25:38 +0530 Source: gitlab Compages: source Version: 12.8.vi-1 Distribution: experimental Urgency: medium Maintainer: Debian Cherry-red Extras Maintainers <pkg-cherry-red-extras-maintainers@lists.alioth.debian.org> Inverse-By: Pirate Praveen <praveen@debian.org> Closes: 942633 Changes: gitlab (12.viii.half dozen-1) experimental; urgency=medium . [ Sruthi Chandran ] * New upstream version 12.8.six * Update embedded module versions * Remove embedded doorkeeper as it is bachelor in experimental * Deleted patches already applied upstream - 0488-relax-rdoc.patch, 0670-allow-doorkeepr-4_3.patch, 0770-crash-land-node-d3.patch * Refresh patches . [ Pirate Praveen ] * Add together ruby-stackprof equally dependency * Drop unused patch files * Driblet patch to lower minimum cherry-red version (already satsfied in buster) * Removed at present unused d3 modules from dependencies * Tighten dependency on ruby-method-source and cerise-grape * Ruddy selection patch from upstream merge request to support grape 1.3 * Fix protobuf compatibility issue with patch (Closes: #942633) * Tighten dependency on reddish-rack and cherry-rails Checksums-Sha1: 67b3490d084c27b3e14d1fc91a91eec292026a52 3827 gitlab_12.8.half-dozen-one.dsc e390c501c2fc7151fae513dee6e258abc5e35c0c 107994 gitlab_12.8.half dozen.orig-batty-benchmarks.tar.gz 942802797a2b2fe9eaeda9201f7aab523398a3e0 60811 gitlab_12.eight.6.orig-elasticsearch-model.tar.gz 59ed12f1366b37dd6cfe492cf22f2c312ce40386 4255484 gitlab_12.8.vi.orig-elasticsearch-rails.tar.gz 2e241f72dfa80489beba2e473b1fa04fddfed71f 3755 gitlab_12.eight.6.orig-faraday-middleware-aws-signers-v4.tar.gz aacfb7721bc0bd05de4b3b4291e5b4da3d49179a 88783952 gitlab_12.8.6.orig.tar.gz 522a22e3c5e37d3594e8aee4251049fd42116d06 83908 gitlab_12.8.half dozen-1.debian.tar.xz 334a3609a6310926fc895a70086c776012dc6ed7 8910 gitlab_12.8.six-1_amd64.buildinfo Checksums-Sha256: 8d431050553409f1fa8fc4db1b80180485906d0f3ee513301e9746699e3d5627 3827 gitlab_12.8.6-1.dsc 865bf3c44c94c034d0160fa11d523767e2ad93adddb26912f6fa816e7028b0ac 107994 gitlab_12.8.6.orig-batty-benchmarks.tar.gz 2a941205948d46f6e2898efcf654374273df1352d51ceb1275353297b6291515 60811 gitlab_12.8.6.orig-elasticsearch-model.tar.gz cfa52e8c11647e4f776953f59fcdc821d55065a4afbf19505c8a25fda7d545de 4255484 gitlab_12.8.6.orig-elasticsearch-rails.tar.gz 243a41b9cdaa3608437eb698df3c8f10ca412483f9d034f123246fddf25dfb2c 3755 gitlab_12.8.half-dozen.orig-faraday-middleware-aws-signers-v4.tar.gz 6a4435f08c247ecfca8ff29257da15223d206e003ece4acc5e07454544e4b96f 88783952 gitlab_12.8.6.orig.tar.gz d1f87c18a782b8c12d8f1fe89d76fe0fcff68f885c19a70e3875e2accb557280 83908 gitlab_12.8.6-1.debian.tar.xz 63966c279334134004fd529928f1c2f3f70c88a6362d776588a8dde331c15b47 8910 gitlab_12.viii.six-1_amd64.buildinfo Files: f5f53c9b2c31f5f9053f04f8c45ca671 3827 cyberspace optional gitlab_12.eight.6-one.dsc 86272733445219b43964f8c427f55a7a 107994 net optional gitlab_12.8.six.orig-batty-benchmarks.tar.gz 26325adc0c160cad7b465f4629c82ad2 60811 net optional gitlab_12.8.six.orig-elasticsearch-model.tar.gz bb2d2fab33c50b0cada8a5ab54146e4e 4255484 net optional gitlab_12.8.6.orig-elasticsearch-rails.tar.gz 16d290ed265b6d0e686ba38043bae007 3755 net optional gitlab_12.8.half dozen.orig-faraday-middleware-aws-signers-v4.tar.gz 1eae463f1c9fd008d951411bda95e1b8 88783952 net optional gitlab_12.8.6.orig.tar.gz 094b5b318bfeab01b6c1a408080e99f5 83908 net optional gitlab_12.viii.6-1.debian.tar.xz d1110e7633c005e2acbbc85622635966 8910 net optional gitlab_12.eight.6-1_amd64.buildinfo -----Begin PGP SIGNATURE----- iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl58mlwACgkQj1PgGTsp S3Wh9xAApEYK/nVBATSm0hqjZ5zndfhLvD6JxCxQYDya8zi/bD/N8dIeGx6mfd2Z kzXXoHX34xW1s8KpQsFj2sDJQHOOXzWzo+f6nZPN3i2a9e3BIsrFJrcTh8UqcO/I 9lDO5xdEywE1s5iDE6V7+DlmMJXJBSBKUz172CR5nypum57O8BKfjVW/gtHf+WjW /xJeJt7reiBlT4KPor+ZUdNu3NmxOOK/A3TZfqtx0H3jhvZYhZbWxe7YIClRZVgB ra0XpdHWxaihe868CDxNPltpEljEEDwVq8o76n7Dl2oD7QDebLkXoG9dw0v1XBky Krw1xyXsf8UTNcYbv8qqI5V5YDz7GqhI9EtT8mwWuACTB8ml5aKpJ1Mkqa3HZgqG y0OlCCf8mYOuZfI7tG4jF9QlOE0WQzrKk/NIUd9Yk8kcSgR3tAhsa9SjKYBXaF/d West/QlsFtWDdFs/uTGbChzrgjcBR8xrFX69VgWQFutU2O37rt+iJF3XMKSGq6dw83F A02JW5yY8DjkG/ODbL5KJA4Ymkth12xtjKn32qVQ3JtSYII1H6XsTTslnx0armhl tJ/D9o33dz/lOn2z29iVF3Os2cpoaokLHR+mww5zMpIFY1Q9tBOHgmsLQCPj7UqF I8HppNGRNm0HaHBN9nxxX+7lvjnQqSAV9w58O73u/98kaPtM7pU= =nS7M -----END PGP SIGNATURE-----
Bug archived. Request was from Debbugs Internal Request <possessor@bugs.debian.org> to internal_control@bugs.debian.org. (Wed, 12 Aug 2020 07:26:22 GMT) (full text, mbox, link).
Send a report that this issues log contains spam.
Debian issues tracking system administrator <owner@bugs.debian.org>. Last modified: Sabbatum April 16 01:42:10 2022 ; Machine Proper noun: bembo
Debian Bug tracking system
Debbugs is free software and licensed nether the terms of the GNU Public License version ii. The current version can be obtained from https://bugs.debian.org/debbugs-source/.
Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.
Source: https://bugs.debian.org/942633
0 Response to "Gitaly-upload-pack: Fatal: Upload-pack Failed Fatal: Could Not Read From Remote Repository."
Publicar un comentario