Gitaly-upload-pack: Fatal: Upload-pack Failed Fatal: Could Not Read From Remote Repository.
Debian Bug written report logs - #942633
gitlab ssh access cleaved with protobuf 3.10
Toggle useless messages
Study forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-crimson-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Sabbatum, 19 Oct 2019 09:21:05 GMT) (full text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
New Bug report received and forwarded. Copy sent to Debian Ruby Extras Maintainers <pkg-blood-red-extras-maintainers@lists.alioth.debian.org>. (Sat, 19 October 2019 09:21:05 GMT) (full text, mbox, link).
Message #five received at submit@bugs.debian.org (full text, mbox, reply):
Package: gitlab Version: 12.1.14-1 Severity: important Dear Maintainer, During the installation of the packet, this warning is displayed: GitLab Beat out: ... GitLab Shell version >= 9.3.0 ? ... FAIL. Delight update gitlab-beat out to 9.3.0 from 9.one.0 But currently the latest version of gitlab-vanquish available in experimental is 9.1.0. Information technology is not possible anymore to collaborate with the repository through ssh: $ git fetch gitaly-upload-pack: fatal: error: %v fatal: Could not read from remote repository. Please make sure you take the correct access rights and the repository exists. $ Server-side, this fault is displayed in gitlab-shell logs: time="2019-ten-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" fourth dimension="2019-ten-19T11:04:07+02:00" level=info msg="executing git command" command="gitaly-upload-pack unix:/run/gitlab/sockets/individual/gitaly.socket {\"repository\":{},\"gl_repository\":\"project-two\",\"gl_project_path\":\"romain/weboob\",\"gl_id\":\"key-3\",\"gl_username\":\"romain\",\"git_config_options\":[],\"git_protocol\":aught}" pid=426 user="user with id key-three" time="2019-10-19T11:04:07+02:00" level=error msg="error: %v" fault="rpc error: code = InvalidArgument desc = Storage can not be found by name ''" pid=426 I don't know if the two issues are related, only there is a adept hazard. The solution would be to parcel 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-viii, LC_CTYPE=en_US.UTF-8 (charmap=UTF-eight), Language=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/nuance Init: systemd (via /run/systemd/arrangement) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii asciidoctor 2.0.ten-2 2 bc 1.07.1-two+b2 ii bundler 1.17.3-3 ii bzip2 i.0.eight-2 ii dbconfig-pgsql ii.0.13 two debconf [debconf-2.0] 1.five.73 two gitlab-common 12.1.14-1 ii gitlab-workhorse 8.5.2+debian-1 ii libjs-bootstrap4 [node-bootstrap] 4.3.1+dfsg2-1 ii libjs-pdf one.5.188+dfsg-1 ii libjs-popper.js [node-popper.js] one.14.6+ds2-2 ii libjs-uglify two.8.29-6 ii lsb-base 11.1.0 two nginx 1.xvi.1-ii ii nginx-extras [nginx] 1.16.1-2 ii node-autosize four.0.ii~dfsg1-three ii node-axios 0.xix.0+dfsg-ii ii node-brace-expansion 1.1.8-1 ii node-enshroud-loader ii.0.ane-ii ii node-chart.js two.7.3+dfsg-5 two node-cadre-js 2.4.ane-2 ii node-css-loader 1.0.ane-ane ii node-d3 4.13.0-10 2 node-d3-array 1.2.iv-2 ii node-d3-axis ane.0.12-ii ii node-d3-brush 1.0.6-three ii node-d3-ease one.0.5-2 2 node-d3-scale one.0.7-vi ii node-d3-pick i.4.0-v 2 node-d3-shape ane.3.v-two two node-d3-time one.0.eleven-3 two node-d3-time-format 2.1.three-2 ii node-d3-transition ane.2.0-four ii node-dateformat 3.0.0-1 ii node-exports-loader 0.7.0-two ii node-file-loader 3.0.i-1 ii node-fuzzaldrin-plus 0.5.0+dfsg-three ii node-glob 7.1.3-2 ii node-imports-loader 0.8.0-ii ii node-jed 1.1.1-1 two node-jquery 3.4.0+dfsg-i ii node-jquery-ujs 1.2.two-two 2 node-jquery.waitforimages 2.4.0+ds-one two node-js-cookie ii.2.0-ii ii node-jszip three.two.2+dfsg-1 ii node-jszip-utils 0.0.2+dfsg-i two node-mousetrap 1.half-dozen.one+ds-1 two node-pikaday one.8.0-1 ii node-raven-js 3.22.1+dfsg-2 ii node-raw-loader i.0.0-2 ii node-three-orbit-controls 82.1.0-2 ii node-three-stl-loader one.0.vi-2 ii node-timeago.js 3.0.2+dfsg-5 ii node-underscore 1.9.ane~dfsg-ane ii node-url-loader 2.0.1-1 ii node-vue-resource 1.5.ane+dfsg-v ii node-webpack-stats-plugin 0.2.1-1 two node-worker-loader 2.0.0-2 ii nodejs 10.xv.2~dfsg-2 ii openssh-client 1:8.1p1-i 2 postfix [post-send-agent] 3.4.7-ane two postgresql-customer xi+207 ii postgresql-client-11 [postgresql-customer] 11.5-3sid2 ii postgresql-client-ix.6 [postgresql-client] ix.6.10-0+deb9u1 2 postgresql-contrib xi+207 ii puma 3.12.0-2+b1 two rake 12.3.3-1 two redis-server five:five.0.vi-1 two ruby 1:2.v.two 2 ruby-ace-rails-ap iv.ane.ane-1 ii red-pinnacle-client 2.0.3-two ii ruby-activerecord-explain-analyze 0.1.0-2 ii ruby-acts-as-taggable-on 6.0.0-3 ii ruby-addressable two.5.2-1 ii ruby-akismet two.0.0-1 ii carmine-apollo-upload-server 2.0.0~beta3-1 ii ruby-asana 0.8.i-2 ii ruby-asciidoctor-include-ext 0.iii.1-2 ii ruby-asciidoctor-plantuml 0.0.9-ane 2 ruby-attr-encrypted 3.one.0-2 ii reddish-babosa ane.0.ii-ii ii ruby-base32 0.3.2-four 2 crimson-batch-loader 1.iv.1+dfsg.1-1 two ruby-bcrypt-pbkdf i.0.1-one ii ruby-criterion-ips ii.seven.two-1 ii ruby-criterion-memory 0.i.2-2 2 ruby-bootstrap-form 4.ii.0-ane two ruby-red-browser 2.v.3-one ii cherry-red-carrierwave i.3.1-two two ruby-charlock-holmes 0.7.6-i ii ruby-red-chronic 0.10.2-3 ii ruby-chronic-duration 0.10.vi-one two cerise-commonmarker 0.17.nine-1+b1 ii ruby-connection-pool two.2.2-1 2 ruby-creole 0.5.0-2 ii ruby-default-value-for three.2.0-1 ii ruby-device-detector one.0.ane-2 ii red-devise 4.6.2-1 ii ruby-devise-ii-gene 3.0.3-2 2 ruby-diffy three.two.1-1 ii cerise-discordrb-webhooks 3.3.0-1 two cerise-doorkeeper 4.4.2-1 ii ruby-doorkeeper-openid-connect 1.5.5-1 ii crimson-ed25519 i.ii.4-one+b1 ii ruby-email-respond-trimmer 0.i.vi-one ii ruby-escape-utils i.2.1-one+b1 2 ruby-excon 0.lx.0-1 2 ruddy-faraday 0.15.iv-3 ii crimson-fast-blank ane.0.0-1+b1 ii ruby-flipper [crimson-flipper-active-support-enshroud-store] 0.13.0-three pn ruby-flipper-active-record <none> two ruddy-flowdock 0.7.1-1 ii ruby-fog-aliyun 0.3.2-3 ii ruby-fog-aws iii.5.2-ane 2 ruby-fog-core two.one.0-three ii ruby-fog-google 1.8.2-2 ii ruby-fog-local 0.half dozen.0-1 2 ruby-fog-openstack 1.0.8-ii ii ruby-fog-rackspace 0.1.half-dozen-2 ii cherry-fogbugz 0.2.one-3 ii ruby-font-awesome-rails 4.7.0.4-1 ii red-fugit i.3.3+gh-1 ii ruby-gemojione 3.3.0-i two ruby-gettext-i18n-rails 1.eight.0-1 ii cherry-red-gettext-i18n-runway-js 1.3.0+dfsg-2 2 ruby-gitaly [scarlet-gitaly-proto] 1.37.0+dfsg-1 ii ruby-github-markup ane.vii.0+dfsg-2 ii ruddy-gitlab-labkit 0.iv.2-i two ruddy-gitlab-sidekiq-fetcher 0.4.0-2 ii crimson-gon half dozen.2.1-1 ii ruby-google-api-client 0.28.4-1 two reddish-google-protobuf three.ten.0-1 ii ruby-googleauth 0.viii.0-2 two reddish-gpgme ii.0.nineteen-1 two scarlet-grape 1.i.0-2 2 ruby-grape-entity 0.7.1-1 two ruby-grape-logging one.7.0-1 2 crimson-grape-path-helpers 1.one.0-1 2 ruby-graphiql-rails one.4.10-1 ii ruby-graphql 1.8.4-1 ii ruby-grpc 1.23.0-1 ii crimson-hamlit 2.ix.two-ii ii ruby-hangouts-chat 0.0.5-2 ii cherry-hashie-forbidden-attributes 0.1.1-1 two blood-red-health-check 2.6.0-1 two red-hipchat 1.5.2-three ii ruby-html-pipeline 2.eight.4-ane two ruby-html2text 0.2.0-one ii ruby-httparty 0.17.0-1 2 cerise-icalendar ii.iv.1-2 two blood-red-influxdb 0.ii.three-2 2 ruby-jira i.five.0-ane ii ruby-jquery-atwho-rails 1.5.4+dfsg-1 ii ruby-js-regex three.one.1-1 two ruby-jwt two.1.0-i ii ruby-kaminari 1.0.one-iv 2 ruby-kgio ii.11.2-ane+b1 2 cherry-kubeclient 4.3.0-one 2 cherry-licensee 8.nine.ii-i ii reddish-lograge 0.ten.0-one two crimson-loofah 2.ii.3+dfsg-one ii ruby-post-room 0.ix.one-ii ii ruby-memory-profiler 0.9.fourteen-2 ii crimson-method-source 0.9.ii-i two ruby-mimemagic 0.3.ii+dfsg-i ii ruby-mini-magick 4.9.2-one.i ii ruby-nakayoshi-fork 0.0.4-1 2 ruby-net-ldap 0.16.1-1 ii ruby-net-ssh 1:5.2.0-1 two ruby-nokogiri 1.10.4+dfsg1-1 2 ruby-ntlm 0.6.1-2 ii reddish-oauth2 1.4.1-2 two ruddy-octokit 4.13.0+gh-i two cherry-omniauth 1.8.1-1 2 scarlet-omniauth-auth0 2.0.0-1 ii ruby-omniauth-authentiq 0.3.iii-1 ii crimson-omniauth-azure-oauth2 0.0.10-ane 2 carmine-omniauth-cas3 1.ane.4-2 2 ruby-omniauth-crowd 2.4.0-i 2 ruddy-omniauth-facebook four.0.0-2 ii blood-red-omniauth-github ane.iii.0-1 ii ruby-omniauth-gitlab ane.0.2-1 ii ruby-omniauth-google-oauth2 0.6.0-one two ruby-omniauth-kerberos 0.3.0-3 2 ruby-omniauth-ldap 2.1.ane-ane two ruby-omniauth-oauth2-generic 0.two.2-1 ii crimson-omniauth-openid-connect 0.iii.ane-1 ii ruby-omniauth-salesforce 1.0.5-2 2 ruby-omniauth-saml 1.10.0-1 ii ruddy-omniauth-shibboleth 1.3.0-1 ii carmine-omniauth-twitter one.4.0-1 two ruby-omniauth-ultraauth 0.0.2-1.1 ii ruby-org 0.9.12-ii 2 ruby-parser 3.xi.0-1 ii ruby-peek 1.0.i-one ii cherry-red-peek-gc 0.0.2-1 two ruby-peek-pg 1.3.0-1 2 reddish-peek-rblineprof 0.2.0-1 ii scarlet-peek-redis 1.two.0-one two reddish-pg 1.1.three-3+b1 ii cherry-red-posix-spawn 0.3.13-2+b1 ii ruby-premailer-rails 1.10.3-1 ii ruby-prof 0.17.0+dfsg-three+b1 two carmine-progressbar 1.9.0-ii ii cerise-prometheus-client-mmap 0.9.x-i two ruby-rack two.0.seven-2 ii crimson-rack-attack iv.4.one-ane ii ruby-rack-cors 1.0.2-1 ii ruby-rack-oauth2 one.nine.3-ii ii ruby-rack-proxy 0.half-dozen.one-two ii ruby-rails 2:5.ii.three+dfsg-1 ii cerise-rail-deprecated-sanitizer 1.0.iii-3 ii cherry-runway-i18n v.1.2-2 ii ruby-rainbow iii.0.0-ii 2 red-raindrops 0.nineteen.0-i+b2 ii ruby-rbtrace 0.four.x-ane+b1 2 ruby-re2 ane.1.i-2+b3 ii ruby-recaptcha four.11.1-2 ii ruby-redcloth 4.3.2-3+b1 two ruby-redis 3.3.5-1 2 blood-red-redis-namespace i.6.0-one ii ruby-redis-rails v.0.ii-3 two ruby-request-store 1.3.0-1 two ruby-responders 2.4.0-3 two ruby-rouge 3.eight.0-1 ii scarlet-rqrcode-rails3 0.i.7-1 two ruby-red-rugged 0.28.1+ds-1 ii scarlet-sanitize iv.6.6-two two ruby-sassc ii.0.i-2 ii ruby-sassc-runway two.ane.2-3 ii ruby-seed-fu ii.3.7-3 2 ruby-sentry-raven 2.9.0-1 two red-settingslogic 2.0.9-three ii ruby-sidekiq v.2.seven+dfsg-one 2 ruby-sidekiq-cron 1.i.0-three two ruby-slack-notifier one.5.i-2 ii cherry-red-sprockets iii.seven.two-1 two carmine-sshkey two.0.0-i ii ruby-red-state-machines-activerecord 0.5.1-ii two blood-red-sys-filesystem 1.1.7-2 ii cherry-chore-list 2.2.0-1 ii ruby-toml-rb 1.0.0-2 ii crimson-truncato 0.7.xi-1 two ruby-u2f 0.2.one-ii ii ruddy-uglifier ii.7.two+dfsg-two 2 ruby-unf 0.i.4-2 ii red-unf-ext 0.0.vii.v-1+b1 2 ruby-unicorn-worker-killer 0.4.4-one two ruby-validates-hostname 1.0.7-i ii ruby-version-sorter ii.2.four-i ii cherry-red-virtus ane.0.5-3 ii cherry-red-vmstat 2.3.0-2+b1 ii ruby-webpack-rails 0.9.11+git-1 ii blood-red-wikicloth 0.8.i+dfsg-4 two ruby-red-cipher i.2.2-1 2 ucf 3.0038+nmu1 2 unicorn v.iv.1-two ii webpack four.vii.0-3 ii yarnpkg one.13.0-iii Versions of packages gitlab recommends: two certbot 0.39.0-ane ii gitaly 1.47.3+debian-1 gitlab suggests no packages. -- debconf information: * gitlab/database-type: pgsql * gitlab/ssl: true gitlab/pgsql/changeconf: simulated gitlab/purge_data: true gitlab/install-error: arrest gitlab/remove-error: abort gitlab/internal/skip-preseed: simulated * gitlab/letsencrypt: false gitlab/missing-db-packet-error: abort gitlab/upgrade-fault: arrest 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: truthful gitlab/pgsql/authmethod-user: password * gitlab/dbconfig-install: true gitlab/upgrade-backup: true gitlab/dbconfig-upgrade: true 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-do-non-match: gitlab/internal/reconfiguring: imitation gitlab/remote/port: Bulletin sent on to Romain Bignon <romain@symlink.me>:
Bug#942633. (Mon, 21 Oct 2019 14:06:06 GMT) (full text, mbox, link).
Message #8 received at 942633-submitter@bugs.debian.org (full text, mbox, reply):
[Message role i (text/plain, inline)]
Hi, this fri I as well tried to upgrade our setup from 11.5.10+dfsg-1 to 12.0.8 and 12.ii.viii-1, both with the result, that cloning about http still works, only ssh was not useable anymore with the same error. From the gitlab-vanquish 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/individual/gitaly.socket {\"repository\":{},\"gl_repository\":\"projection-49\",\"gl_project_path\":\"client/XXXXX\",\"gl_id\":\"key-44\",\"gl_username\":\"YYYYYYY\",\"git_config_options\":[],\"git_protocol\":null}" pid=7378 user="user with id cardinal-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 proper noun ''" pid=7378 And that with both versions (12.0 and 12.2). I tried also to gear up information technology by packaging gitlab-shell 9.3 for my own, just it didn't helped.. -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Programmer Blog: http://www.linux-dev.org/ Email: pmatthaei@debian.org patrick@linux-dev.org */ [Message part 2 (text/html, inline)]
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Carmine Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Monday, 21 Oct 2019 15:42:02 GMT) (full 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:42:02 GMT) (total text, mbox, link).
Bulletin #xiii received at 942633@bugs.debian.org (full text, mbox, reply):
On Mon, 21 Oct 2019 15:47:47 +0200 =?UTF-eight?Q?Patrick_Matth=c3=a4i?= <pmatthaei@debian.org> wrote: > Hi, > > this fri I also tried to upgrade our setup from 11.five.10+dfsg-1 to > 12.0.eight and 12.2.viii-1, both with the result, that cloning nigh http withal > works, only ssh was non 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 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\":\"key-44\",\"gl_username\":\"YYYYYYY\",\"git_config_options\":[],\"git_protocol\":goose egg}" > pid=7378 user="user with id key-44" > time="2019-10-18T15:54:35+02:00" level=error msg="error: %v" mistake="rpc > error: code = InvalidArgument desc = Storage tin non be establish by name > ''" pid=7378 It could exist a new choice either in gitaly or gitlab configurations. Are you using gitaly on the same server? Practice you have the required version of gitaly? At least for Romain that seems to be the problem. ii gitaly 1.47.3+debian-i $ apt policy gitaly gitaly: Installed: 1.53.three+debian-1~bpo10+i Candidate: 1.53.3+debian-1~bpo10+one Version table: *** 1.53.3+debian-i~bpo10+one 500 500 https://people.debian.org/~praveen/gitlab buster-backports/chief amd64 Packages 100 /var/lib/dpkg/status > And that with both versions (12.0 and 12.2). I tried also to fix information technology by > packaging gitlab-shell nine.3 for my own, but it didn't helped.. > > -- > /* > Mit freundlichem Gruß / With kind regards, > Patrick Matthäi > GNU/Linux Debian Developer > > Weblog: http://www.linux-dev.org/ > East-Mail: pmatthaei@debian.org > patrick@linux-dev.org > */ > Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-red-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Parcel gitlab. (Monday, 21 Oct 2019 15:54: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 Scarlet Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Mon, 21 October 2019 fifteen:54:03 GMT) (full text, mbox, link).
Message #xviii received at 942633@bugs.debian.org (full text, mbox, reply):
[Message part i (text/evidently, inline)]
On Mon, Oct 21, 2019 at 21:09, Pirate Praveen <praveen@onenetbeyond.org> wrote: > At to the lowest degree for Romain that seems to be the problem. > > ii gitaly 1.47.three+debian-1 > > $ apt policy gitaly > gitaly: > Installed: one.53.3+debian-i~bpo10+1 > Candidate: one.53.3+debian-1~bpo10+ane > Version table: > *** 1.53.iii+debian-ane~bpo10+1 500 > 500 <https://people.debian.org/~praveen/gitlab> > 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.
[Message role ii (text/html, inline)]
Changed Problems championship to 'update minimum version of gitaly to >= 1.53.3' from 'gitlab: Experimental gitlab requires gitshell nine.3.0 but simply 9.1.0 is packaged'. Asking was from Pirate Praveen <praveen@onenetbeyond.org> to control@bugs.debian.org. (Mon, 21 October 2019 17:12:03 GMT) (full text, mbox, link).
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Cherry Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Problems#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 Blood-red Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Tue, 22 Oct 2019 13:03:06 GMT) (full text, mbox, link).
Message #25 received at 942633@bugs.debian.org (total text, mbox, reply):
Hi, On 21/Oct - 21:21, Pirate Praveen wrote: > > At least for Romain that seems to exist the problem. > > > > ii gitaly ane.47.3+debian-1 > > > > $ apt policy gitaly > > gitaly: > > Installed: 1.53.3+debian-one~bpo10+one > > Candidate: 1.53.3+debian-1~bpo10+1 > > Version table: > > *** i.53.3+debian-1~bpo10+1 500 > > 500 <https://people.debian.org/~praveen/gitlab> > > buster-backports/principal amd64 Packages > > 100 /var/lib/dpkg/condition > > This is actually a bug every bit minimum version for gitaly was non updated in > gitlab. i.47.3+debian-one is the latest version available on Debian experimental.
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Scarlet Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Issues#942633; Package gitlab. (Tue, 22 Oct 2019 13:09: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 Ruby Extras Maintainers <pkg-carmine-extras-maintainers@lists.alioth.debian.org>. (Tue, 22 Oct 2019 13:09:03 GMT) (full text, mbox, link).
Message #30 received at 942633@bugs.debian.org (full text, mbox, answer):
[Message part ane (text/plain, inline)]
On Tue, Oct 22, 2019 at 14:54, Romain Bignon <romain@symlink.me> wrote: > Hullo, > > On 21/October - 21:21, Pirate Praveen wrote: >> > At least for Romain that seems to be the trouble. >> > >> > ii gitaly 1.47.3+debian-i >> > >> > $ apt policy gitaly >> > gitaly: >> > Installed: 1.53.three+debian-1~bpo10+1 >> > Candidate: 1.53.three+debian-1~bpo10+1 >> > Version table: >> > *** one.53.three+debian-one~bpo10+i 500 >> > 500 <<https://people.debian.org/~praveen/gitlab>> >> > buster-backports/master amd64 Packages >> > 100 /var/lib/dpkg/status >> >> This is really 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 i.58.0+dfsg-i build failed https://buildd.debian.org/status/fetch.php?pkg=gitaly&arch=amd64&ver=1.58.0%2Bdfsg-1&stamp=1571598656&raw=0
[Message part 2 (text/html, inline)]
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Blood-red Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Packet 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 listing. Copy sent to Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Tue, 22 Oct 2019 13:51:03 GMT) (full text, mbox, link).
Message #35 received at 942633@bugs.debian.org (full text, mbox, reply):
On Tue, 22 Oct 2019 18:36:20 +0530 Pirate Praveen <praveen@onenetbeyond.org> wrote:> Information technology seems 1.58.0+dfsg-one build failed > > https://buildd.debian.org/status/fetch.php?pkg=gitaly&arch=amd64&ver=one.58.0%2Bdfsg-1&stamp=1571598656&raw=0 > This is building fine on my organization. So uploaded binary included as work around.
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Parcel gitlab. (Tue, 22 October 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 #twoscore received at 942633@bugs.debian.org (full text, mbox, reply):
On 22/October - 19:xviii, Pirate Praveen wrote: > This is building fine on my system. So uploaded binary included as piece of work > around. Note that I run into a newer version of gitlb available: root@weboob ~ # apt-enshroud policy gitlab gitlab: Installed: 12.1.14-1 Candidate: 12.1.14-1 Version table: 12.ii.8-ane 1 1 http://ftp.de.debian.org/debian experimental/contrib amd64 Packages *** 12.1.14-1 100 100 /var/lib/dpkg/status xi.8.10+dfsg-ane -one -1 http://ftp.de.debian.org/debian unstable/contrib amd64 Packages Just it is non possible to install it every bit there are broken dependencies: root@weboob ~ # apt install gitlab/experimental Reading package lists... Done Building dependency tree Reading state information... Washed Selected version '12.two.8-1' (Debian:experimental [all]) for 'gitlab' Some packages could not exist installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have non yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages take unmet dependencies: gitlab : Depends: ruby-invisible-captcha (>= 0.12.1~) merely information technology is non installable Depends: reddish-gitlab-sidekiq-fetcher (>= 0.5.1~) but 0.4.0-2 is to be installed Depends: red-redis (>= 4.0~) but 3.three.five-1 is to exist installed Depends: ruby-gitlab-labkit (>= 0.four.two-2~) but 0.four.2-1 is to exist installed Depends: ruby-statistics merely it is non installable Depends: ruby-gitaly (>= 1.58~) simply 1.37.0+dfsg-1 is to be installed E: Unable to correct issues, you have held broken packages. Practise you think you'll exist able to upload a newer fixed version of gitaly before long? Or is there whatever workaround? Romain
Data forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Packet gitlab. (Tue, 22 Oct 2019 17:21:09 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 Reddish Extras Maintainers <pkg-crimson-extras-maintainers@lists.alioth.debian.org>. (Tue, 22 October 2019 17:21:09 GMT) (full text, mbox, link).
Message #45 received at 942633@bugs.debian.org (full text, mbox, answer):
[Message function 1 (text/plain, inline)]
On Tue, Oct 22, 2019 at 19:02, Romain Bignon <romain@symlink.me> wrote: > On 22/Oct - 19:xviii, Pirate Praveen wrote: >> This is building fine on my arrangement. And so uploaded binary included every bit >> work >> around. > > Note that I meet a newer version of gitlb available: > > root@weboob ~ # apt-cache policy gitlab > gitlab: > Installed: 12.1.14-1 > Candidate: 12.one.fourteen-1 > Version table: > 12.2.8-i 1 > i <http://ftp.de.debian.org/debian> experimental/contrib > amd64 Packages > *** 12.ane.14-one 100 > 100 /var/lib/dpkg/status > 11.viii.10+dfsg-one -one > -1 <http://ftp.de.debian.org/debian> unstable/contrib amd64 > Packages > > Only it is non possible to install information technology as there are cleaved dependencies: > > root@weboob ~ # apt install gitlab/experimental > Reading package lists... Done > Edifice dependency tree > Reading state information... Done > Selected version '12.ii.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 non all the same 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 information technology is not > installable > Depends: ruby-gitlab-sidekiq-fetcher (>= 0.five.ane~) just > 0.iv.0-ii is to be installed > Depends: ruby-redis (>= 4.0~) merely iii.3.5-i is to be installed > Depends: ruddy-gitlab-labkit (>= 0.4.2-ii~) simply 0.4.2-1 is to > be installed > Depends: ruddy-statistics but information technology is non installable > Depends: cerise-gitaly (>= 1.58~) merely 1.37.0+dfsg-1 is to be > installed > E: Unable to correct bug, you have held broken packages. > > Practice you retrieve yous'll be able to upload a newer fixed version of gitaly > soon? Or > is in that location whatsoever workaround? > All those packages are available in experimental. I have updated https://wiki.debian.org/gitlab with these packages added to the listing of pcakges needed from experimental. > Romain
[Message office 2 (text/html, inline)]
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Carmine Extras Maintainers <pkg-carmine-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Wed, 23 Oct 2019 07:45:03 GMT) (total text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
Actress info received and forwarded to list. Copy sent to Debian Crimson Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Midweek, 23 Oct 2019 07:45:03 GMT) (full text, mbox, link).
Bulletin #50 received at 942633@bugs.debian.org (full text, mbox, answer):
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 even so exists… What can I do to help debugging? Romain
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-reddish-extras-maintainers@lists.alioth.debian.org>:
Issues#942633; Package gitlab. (Wed, 23 Oct 2019 09:03: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 Ruby Extras Maintainers <pkg-scarlet-extras-maintainers@lists.alioth.debian.org>. (Wed, 23 October 2019 09:03:03 GMT) (full text, mbox, link).
Bulletin #55 received at 942633@bugs.debian.org (full text, mbox, reply):
[Bulletin function 1 (text/plain, inline)]
On Wed, October 23, 2019 at 09:twoscore, Romain Bignon <romain@symlink.me> wrote: > On 22/Oct - 22:47, Pirate Praveen wrote: >> All those packages are available in experimental. I accept 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, fifty-fifty gitlab-trounce, and the problem notwithstanding exists… > > What can I do to assist debugging? > merely share apt policy gitaly for confirmation and the error messages again (after yous restart gitaly and gitlab services). > Romain >
[Message part 2 (text/html, inline)]
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Scarlet Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Wed, 23 October 2019 13:57:03 GMT) (total 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>. (Wed, 23 Oct 2019 13:57:03 GMT) (full text, mbox, link).
Message #threescore received at 942633@bugs.debian.org (total text, mbox, respond):
On 23/October - 14:31, Pirate Praveen wrote: > just share apt policy gitaly for confirmation and the error messages in one case > more than (later yous restart gitaly and gitlab services). gitaly: Installed: 1.58.0+dfsg-2 Candidate: 1.58.0+dfsg-two Version tabular array: *** 1.58.0+dfsg-2 100 ane http://ftp.de.debian.org/debian experimental/main amd64 Packages 100 /var/lib/dpkg/condition one.20.0+debian-i+b1 -1 -i http://ftp.de.debian.org/debian unstable/main amd64 Packages And the mistake bulletin client side: $ git fetch gitaly-upload-pack: fatal: error: %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=POST pid=8834 url="http://localhost:8080/api/v4/internal/allowed" time="2019-10-23T15:53:54+02:00" level=info msg="executing git control" control="gitaly-upload-pack unix:/run/gitlab/sockets/private/gitaly.socket {\"repository\":{},\"gl_repository\":\"project-2\",\"gl_project_path\":\"romain/weboob\",\"gl_id\":\"central-3\",\"gl_username\":\"romain\",\"git_config_options\":[],\"git_protocol\":naught}" pid=8834 user="user with id cardinal-3" time="2019-ten-23T15:53:54+02:00" level=error msg="mistake: %v" error="rpc error: lawmaking = InvalidArgument desc = Storage can non exist institute by name ''" pid=8834 Data forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Problems#942633; Parcel gitlab. (Sabbatum, 02 November 2019 13:54: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 Ruby Extras Maintainers <pkg-reddish-extras-maintainers@lists.alioth.debian.org>. (Sat, 02 November 2019 13:54:03 GMT) (full text, mbox, link).
Message #65 received at 942633@bugs.debian.org (full text, mbox, reply):
Hello, The problem is still hither, and is so not related to compatibility between versions of gitlab/gitlab-shell/gitality… Is there anything I can do to discover the origin of this issue? Romain
Information forwarded to debian-bugs-dist@lists.debian.org, Debian Blood-red Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Monday, eleven Nov 2019 16:48:03 GMT) (total text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Actress info received and forwarded to list. Copy sent to Debian Cerise Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Monday, 11 November 2019 16:48:03 GMT) (full text, mbox, link).
Message #seventy received at 942633@bugs.debian.org (full text, mbox, reply):
Control: retitle -1 ssh access fails with gitaly-upload-pack: fatal: fault: %v On Sat, 2 Nov 2019 14:51:42 +0100 Romain Bignon <romain@symlink.me> wrote: > Hello, > > The trouble is still here, and is then non related to compatibility between > versions of gitlab/gitlab-trounce/gitality… > > Is there anything I can exercise to find the origin of this issue? Fortunately or unfortunately the same error striking my case equally well. I'm earthworks deeper into it now. As a workaround yous can use https access till we fix this (simply ssh access is afflicted).
Changed Bug title to 'ssh access fails with gitaly-upload-pack: fatal:' from 'update minimum version of gitaly to >= ane.53.3'. Request was from Pirate Praveen <praveen@onenetbeyond.org> to 942633-submit@bugs.debian.org. (Mon, 11 November 2019 xvi:48:03 GMT) (full text, mbox, link).
Severity prepare to 'grave' from 'important' Request was from Pirate Praveen <praveen@onenetbeyond.org> to command@bugs.debian.org. (Mon, 11 Nov 2019 17:00:06 GMT) (full text, mbox, link).
Data forwarded to debian-bugs-dist@lists.debian.org, Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Wed, 13 November 2019 18:xviii:03 GMT) (full text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Actress info received and forwarded to list. Copy sent to Debian Cerise Extras Maintainers <pkg-carmine-extras-maintainers@lists.alioth.debian.org>. (Wed, xiii Nov 2019 18:eighteen:03 GMT) (full text, mbox, link).
Message #81 received at 942633@bugs.debian.org (total text, mbox, answer):
On Mon, 11 Nov 2019 22:15:twenty +0530 Pirate Praveen <praveen@onenetbeyond.org> wrote: > 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: > > Hullo, > > > > The trouble is still hither, and is so not related to compatibility between > > versions of gitlab/gitlab-shell/gitality… > > > > Is there anything I tin practise to observe the origin of this event? > > Fortunately or unfortunately the same error hitting my instance as well. I'grand > excavation deeper into it at present. > > Every bit a workaround you lot can use https access till we ready this (but ssh > access is affected). Plant the root cause to be carmine-google-protobuf update from 3.7 to three.10. But to actually go it work is tricky. If we downgrade ruby-google-protobuf to 3.7.1, and 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>:
Issues#942633; Packet gitlab. (Thu, 14 Nov 2019 02:21:07 GMT) (total text, mbox, link).
Acknowledgement sent to Pirate Praveen <praveen@onenetbeyond.org>:
Actress info received and forwarded to listing. Copy sent to Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Thu, 14 Nov 2019 02:21:07 GMT) (total text, mbox, link).
Message #86 received at 942633@bugs.debian.org (full text, mbox, reply):
[Message function 1 (text/plain, inline)]
Control: retitle -i gitlab ssh access cleaved with protobuf iii.x Control: severity -i serious On ബു, Nov 13, 2019 at 23:44, Pirate Praveen <praveen@onenetbeyond.org> wrote: > On Mon, eleven November 2019 22:xv:20 +0530 Pirate Praveen > <praveen@onenetbeyond.org <mailto:praveen@onenetbeyond.org>> wrote: >> Command: retitle -1 ssh access fails with gitaly-upload-pack: fatal: >> error: %v >> On Sabbatum, 2 Nov 2019 14:51:42 +0100 Romain Bignon <romain@symlink.me >> <mailto:romain@symlink.me>> wrote: >> > Hello, >> > >> > The problem is still here, and is and so non related to compatibility >> between >> > versions of gitlab/gitlab-shell/gitality… >> > >> > Is in that location annihilation I can do to find the origin of this issue? >> >> Fortunately or unfortunately the same mistake hit my instance every bit >> well. I'm >> digging deeper into it at present. >> >> Equally a workaround you can use https access till we ready this (only ssh >> admission is affected). > > Found the root cause to exist blood-red-google-protobuf update from three.7 to > three.ten. > Only to really become it work is tricky. > > If we downgrade ruby-google-protobuf to 3.vii.1, then gitaly fails to > build. <https://people.debian.org/~praveen/gitlab/> has protobuf 3.7 and grpc one.19. You lot need to downgrade both and use gitaly ane.59.3+dfsg-1~bpo10+2 (which allows these versions). And because of <https://bugs.debian.org/cgi-bin/bugreport.cgi?issues=944698> 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 utilize a separate repo with protobuf iii.10 and grpc 1.23 -> https://people.debian.org/~praveen/protobuf/ to build gitaly I'grand keeping this bug open till we can use aforementioned version of protobuf for both gitaly build and gitlab. I have opened https://gitlab.com/gitlab-org/gitaly/bug/2164 to piece of 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, xiv Nov 2019 02:21:07 GMT) (full text, mbox, link).
Severity set to 'serious' from 'grave' Asking was from Pirate Praveen <praveen@onenetbeyond.org> to 942633-submit@bugs.debian.org. (Thu, 14 Nov 2019 02:21:08 GMT) (full text, mbox, link).
Data forwarded to debian-bugs-dist@lists.debian.org, Debian Ruddy Extras Maintainers <pkg-red-extras-maintainers@lists.alioth.debian.org>:
Bug#942633; Package gitlab. (Thu, 14 November 2019 11:15:03 GMT) (total text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
Extra info received and forwarded to list. Copy sent to Debian Cerise Extras Maintainers <pkg-carmine-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 (full text, mbox, answer):
On 14/Nov - 07:45, Pirate Praveen wrote: > <https://people.debian.org/~praveen/gitlab/> has protobuf 3.7 and grpc 1.19. > You need to downgrade both and employ gitaly ane.59.3+dfsg-1~bpo10+2 (which > allows these versions). > > And because of <https://bugs.debian.org/cgi-bin/bugreport.cgi?issues=944698> > you may need to regenrate Gemfile.lock > > # cd /usr/share/gitlab > # sudo -u gitlab truncate -s0 Gemfile.lock > # sudo -u gitlab package 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 up till we tin can use same version of protobuf for both > gitaly build and gitlab. I have opened > https://gitlab.com/gitlab-org/gitaly/issues/2164 to piece of work with upstream on > this Great it works, cheers. Please tell us when the issue is fixed in the experimental repository and that nosotros can upgrade all versions from this repository, as it is currently somewhat a hot prepare. Romain
Data forwarded to debian-bugs-dist@lists.debian.org, Debian Cerise Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>:
Problems#942633; Package gitlab. (Wed, 20 Nov 2019 12:09:03 GMT) (total 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-blood-red-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, reply):
On Thu, 14 November 2019 12:07:52 +0100 Romain Bignon <romain@symlink.me> wrote: > Great it works, give thanks you. Please tell us when the issue is fixed in the > experimental repository and that nosotros tin upgrade all versions from this > repository, every bit it is currently somewhat a hot gear up. 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.xi (currently at three.10.i), and then 2. grpc demand to update its embedded copy of protobuf to this version, then 3. gitlab and gitaly needs to update red-grpc-tools, ruby-grpc, protoc and protobuf to this version, and so 4. debian's version of protobuf and grpc should be updated to this version So equally a piece of work around I have uploaded older versions of protobuf and grpc to my personal repo. 1. Add together the following lines to your sources.list deb https://people.debian.org/~praveen/protobuf/ experimental main contrib two. Add my gpg keys to apt trusted keys # wget https://people.debian.org/~praveen/gitlab/praveen.key.asc # apt-key add praveen.cardinal.asc # apt update 3. Downgrade cherry-grpc, ruby-google-protobuf and update gitaly # apt install ruby-google-protobuf=3.7.ane-1 cherry-grpc=ane.19.1-1 # apt install gitaly/experimental Make certain gitaly version is at least 1.59.3+dfsg-2 (just uploaded, it will take some hours to evidence 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
Added tag(southward) stock-still-upstream. Request was from debian-bts-link@lists.debian.org to control@bugs.debian.org. (Thu, 21 Nov 2019 17:27:12 GMT) (total text, mbox, link).
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. (Wed, 27 Nov 2019 08:39:03 GMT) (total text, mbox, link).
Acknowledgement sent to Romain Bignon <romain@symlink.me>:
Actress info received and forwarded to list. Copy sent to Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>. (Wed, 27 Nov 2019 08:39:03 GMT) (total text, mbox, link).
Bulletin #109 received at 942633@bugs.debian.org (full text, mbox, reply):
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]: [organisation] Activating via systemd: service proper noun='org.freedesktop.PackageKit' unit='packagekit.service' requested past ':i.10456' (uid=0 pid=28562 comm="/usr/bin/gdbus telephone call --arrangement --dest org.freedeskto") Nov 27 06:32:18 weboob systemd[one]: Starting PackageKit Daemon... Nov 27 06:32:18 weboob PackageKit: daemon offset 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. November 27 06:32:eighteen weboob gitlab-workhorse[20628]: git.weboob.org 46.229.168.139 - - [2019/11/27:06:32:eighteen +0100] "Become /P4ncake/devel/tree/6f5f41fe574ad35b11e024b7c10bb2950d0689b2 HTTP/1.one" 200 40794 "" "Mozilla/5.0 (uniform; 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:nineteen weboob systemd[1]: Configuration file /etc/systemd/system/postfix.service.d/override.conf is marked world-inaccessible. This has no issue equally configuration data is accessible via APIs without restrictions. Proceeding anyway. Nov 27 06:32:xix weboob systemd[1]: /lib/systemd/organisation/gitlab-sidekiq.service:eighteen: Ignoring unknown escape sequences: "for i in 4 iv iv 4 iv 4 4 four; do sleep $i; (ps -h -o command -p $MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; washed" Nov 27 06:32:19 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; delight update the unit file appropriately. Nov 27 06:32:twenty weboob systemd[ane]: Reloading. Nov 27 06:32:twenty weboob systemd[1]: /lib/systemd/organization/dbus.socket:v: 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 earth-inaccessible. This has no event as configuration data is accessible via APIs without restrictions. Proceeding anyway. Nov 27 06:32:20 weboob systemd[1]: /lib/systemd/organisation/gitlab-sidekiq.service:18: Ignoring unknown escape sequences: "for i in four 4 iv four 4 four iv iv; 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/organization/docker.socket:vi: ListenStream= references a path beneath 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[ane]: Reloading. November 27 06:32:twenty weboob systemd[1]: /lib/systemd/organisation/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 of measurement file appropriately. Nov 27 06:32:20 weboob systemd[1]: Configuration file /etc/systemd/organisation/postfix.service.d/override.conf is marked world-inaccessible. This has no effect as configuration data is attainable via APIs without restrictions. Proceeding anyway. Nov 27 06:32:20 weboob systemd[one]: /lib/systemd/system/gitlab-sidekiq.service:eighteen: Ignoring unknown escape sequences: "for i in 4 four four 4 4 4 4 four; do slumber $i; (ps -h -o command -p $MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && exit 0; washed" Nov 27 06:32:twenty 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=fault msg="lstat /var/lib/gitlab/repositories/+gitaly/cache: no such file or directory" storage=default Nov 27 06:32:20 weboob systemd[1]: Reloading. November 27 06:32:21 weboob systemd[i]: /lib/systemd/system/dbus.socket:five: 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 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 issue as configuration data is accessible via APIs without restrictions. Proceeding anyhow. November 27 06:32:21 weboob systemd[1]: /lib/systemd/organization/gitlab-sidekiq.service:xviii: Ignoring unknown escape sequences: "for i in 4 four iv 4 4 4 iv 4; do sleep $i; (ps -h -o command -p $MAINPID | grep -q -P "sidekiq \d\.\d\.\d") && go out 0; washed" Nov 27 06:32:21 weboob systemd[i]: /lib/systemd/system/docker.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; delight update the unit file appropriately. November 27 06:32:21 weboob systemd[i]: Stopped target GitLab Service. Nov 27 06:32:21 weboob systemd[1]: Stopping GitLab Service. Nov 27 06:32:21 weboob systemd[i]: gitlab.service: Succeeded. Nov 27 06:32:21 weboob systemd[1]: Stopped GitLab Services. Nov 27 06:32:21 weboob systemd[one]: Stopping GitLab Services... November 27 06:32:21 weboob systemd[one]: Stopping Gitlab mailroom Worker... Nov 27 06:32:21 weboob systemd[one]: Stopping GitLab Sidekiq Worker... Nov 27 06:32:21 weboob systemd[1]: Stopping Gitlab Workhorse handles boring 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 November 27 06:32:21 weboob gitlab-sidekiq[20644]: 2019-11-27T05:32:21.133Z 20644 TID-goin08v3c INFO: Scheduler exiting... Nov 27 06:32:21 weboob gitlab-sidekiq[20644]: 2019-11-27T05:32:21.133Z 20644 TID-goijjrii4 INFO: Terminating quiet workers Nov 27 06:32:21 weboob gitlab-sidekiq[20644]: 2019-11-27T05:32:21.135Z 20644 TID-goin0a0a0 INFO: Scheduler exiting... Nov 27 06:32:21 weboob systemd[i]: gitlab-workhorse.service: Succeeded. November 27 06:32:21 weboob systemd[1]: Stopped Gitlab Workhorse handles irksome HTTP requests for Gitlab.. Nov 27 06:32:21 weboob systemd[1]: gitlab-mailroom.service: Succeeded. Nov 27 06:32:21 weboob systemd[i]: Stopped Gitlab mailroom Worker. Nov 27 06:32:21 weboob systemd[i]: Stopping GitLab Unicorn Server... Nov 27 06:32:21 weboob systemd[1]: gitlab-unicorn.service: Succeeded. Nov 27 06:32:21 weboob systemd[1]: Stopped GitLab Unicorn Server. November 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-11-27T05:32:23.639Z 20644 TID-goijjrii4 INFO: Good day! November 27 06:32:23 weboob systemd[1]: gitlab-sidekiq.service: Succeeded. Nov 27 06:32:23 weboob systemd[1]: Stopped GitLab Sidekiq Worker. Nov 27 06:32:23 weboob systemd[1]: Stopping Advanced key-value store... November 27 06:32:24 weboob systemd[1]: redis-server.service: Succeeded. Nov 27 06:32:24 weboob systemd[1]: Stopped Advanced key-value store. November 27 06:32:24 weboob systemd[ane]: Starting Avant-garde fundamental-value store... Nov 27 06:32:24 weboob systemd[ane]: redis-server.service: Tin't open PID file /run/redis/redis-server.pid (yet?) after start: No such file or directory November 27 06:32:24 weboob systemd[1]: Started Avant-garde key-value store. November 27 06:32:24 weboob systemd[1]: Starting GitLab Sidekiq Worker... Nov 27 06:32:24 weboob systemd[1]: gitlab-unicorn.service: Ignoring invalid surroundings assignment '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 surround consignment 'consign app_user=${gitlab_user}': /etc/default/gitlab Nov 27 06:32:24 weboob systemd[1]: Started GitLab Unicorn Server. Nov 27 06:32:24 weboob systemd[1]: Started Gitlab mailroom Worker. Nov 27 06:32:24 weboob systemd[ane]: 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 whatsoever 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 discover precious stone 'rubyzip (>= 1.two.2, ~> 1.ii)' in whatsoever of the gem sources listed in your Gemfile. November 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.3/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.iii/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-1.17.3/lib/bundler/resolver.rb:49:in `start' Nov 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.three/lib/bundler/definition.rb:170:in `specs' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.three/lib/bundler/definition.rb:237:in `specs_for' Nov 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.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.3/lib/bundler/runtime.rb:20:in `setup' November 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-1.17.three/lib/bundler.rb:107:in `setup' November 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/share/rubygems-integration/all/gems/bundler-ane.17.3/lib/bundler/setup.rb:20:in `<top (required)>' November 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' November 27 06:32:24 weboob gitlab-unicorn[28831]: /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `crave' Nov 27 06:32:24 weboob systemd[one]: gitlab-unicorn.service: Main process exited, code=exited, status=1/FAILURE November 27 06:32:24 weboob systemd[1]: gitlab-unicorn.service: Failed with upshot 'go out-lawmaking'. Nov 27 06:32:24 weboob gitlab-mailroom[28832]: fatal: not a git repository (or whatsoever of the parent directories): .git Nov 27 06:32:24 weboob gitlab-mailroom[28832]: fatal: not a git repository (or any of the parent directories): .git Nov 27 06:32:24 weboob gitlab-sidekiq[28829]: fatal: non 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 November 27 06:32:24 weboob gitlab-mailroom[28832]: /usr/share/rubygems-integration/all/gems/bundler-one.17.3/lib/bundler/resolver.rb:287:in `block in verify_gemfile_dependencies_are_found!': Could non detect gem 'rubyzip (>= 1.2.ii, ~> 1.ii)' in any of the precious stone sources listed in your Gemfile. (Bundler::GemNotFound) November 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-ane.17.3/lib/bundler/resolver.rb:255:in `verify_gemfile_dependencies_are_found!' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-one.17.3/lib/bundler/resolver.rb:49:in `offset' November 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-one.17.3/lib/bundler/resolver.rb:22:in `resolve' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-1.17.iii/lib/bundler/definition.rb:258:in `resolve' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-ane.17.3/lib/bundler/definition.rb:170:in `specs' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-one.17.iii/lib/bundler/definition.rb:237:in `specs_for' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-1.17.iii/lib/bundler/definition.rb:226:in `requested_specs' November 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-i.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-1.17.iii/lib/bundler/runtime.rb:20:in `setup' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/share/rubygems-integration/all/gems/bundler-i.17.3/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:xx:in `<meridian (required)>' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/lib/ruby/ii.five.0/rubygems/core_ext/kernel_require.rb:59:in `require' Nov 27 06:32:24 weboob gitlab-mailroom[28832]: #011from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require' Nov 27 06:32:24 weboob systemd[1]: gitlab-mailroom.service: Main process exited, lawmaking=exited, status=1/FAILURE November 27 06:32:24 weboob systemd[1]: gitlab-mailroom.service: Failed with upshot 'exit-lawmaking'. I had to install manually rubyzip with gem at the right version to fix gitlab. To sympathize, packagekit has updated something? 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. (Wed, 27 November 2019 09:03:06 GMT) (full 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>. (Wed, 27 Nov 2019 09:03:06 GMT) (full text, mbox, link).
Bulletin #114 received at 942633@bugs.debian.org (total text, mbox, reply):
On 2019, നവംബർ 27 2:04:xix PM IST, Romain Bignon <romain@symlink.me> wrote: >Hi, > >A new strange affair, I don't know if you encountered that, today at >6h32 >packagekit run, tried to restart gitlab, and failed: Information technology'd be a proficient thought to plow off unattended upgrades in unstable. >Nov 27 06:32:24 weboob gitlab-unicorn[28831]: Bundler::GemNotFound: >Could non detect jewel 'rubyzip (>= 1.ii.2, ~> 1.2)' in any of the gem >sources listed in your Gemfile. carmine-zip was updated to 2.0.0. >I had to install manually rubyzip with gem at the correct version to fix >gitlab. > >To empathize, packagekit has updated something? This should be fixed in latest version of gitlab. >Romain -- Sent from my Android device with Chiliad-9 Mail. Please excuse my brevity.
Respond sent to Pirate Praveen <praveen@debian.org>:
You lot have taken responsibleness. (Thu, 26 Mar 2020 12:24:05 GMT) (full text, mbox, link).
Notification sent to Romain Bignon <romain@symlink.me>:
Bug acknowledged by developer. (Thu, 26 Mar 2020 12:24:05 GMT) (total text, mbox, link).
Message #119 received at 942633-close@bugs.debian.org (full text, mbox, reply):
Source: gitlab Source-Version: 12.viii.6-1 Done: Pirate Praveen <praveen@debian.org> Nosotros believe that the bug you lot 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. Give thanks you lot for reporting the bug, which will now exist closed. If you accept further comments please accost them to 942633@bugs.debian.org, and the maintainer volition reopen the issues written report if appropriate. Debian distribution maintenance software pp. Pirate Praveen <praveen@debian.org> (supplier of updated gitlab bundle) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators past mailing ftpmaster@ftp-chief.debian.org) -----Begin PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Engagement: Thu, 26 Mar 2020 17:25:38 +0530 Source: gitlab Compages: source Version: 12.eight.six-1 Distribution: experimental Urgency: medium Maintainer: Debian Ruby-red Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org> Changed-By: Pirate Praveen <praveen@debian.org> Closes: 942633 Changes: gitlab (12.8.half-dozen-i) experimental; urgency=medium . [ Sruthi Chandran ] * New upstream version 12.viii.6 * Update embedded module versions * Remove embedded doorkeeper every bit it is available in experimental * Deleted patches already applied upstream - 0488-relax-rdoc.patch, 0670-let-doorkeepr-4_3.patch, 0770-crash-land-node-d3.patch * Refresh patches . [ Pirate Praveen ] * Add cherry-red-stackprof as dependency * Drib unused patch files * Drib patch to lower minimum blood-red version (already satsfied in buster) * Removed now unused d3 modules from dependencies * Tighten dependency on carmine-method-source and ruby-grape * Carmine pick patch from upstream merge asking to support grape 1.3 * Fix protobuf compatibility outcome with patch (Closes: #942633) * Tighten dependency on blood-red-rack and red-rail Checksums-Sha1: 67b3490d084c27b3e14d1fc91a91eec292026a52 3827 gitlab_12.eight.6-one.dsc e390c501c2fc7151fae513dee6e258abc5e35c0c 107994 gitlab_12.8.6.orig-batty-benchmarks.tar.gz 942802797a2b2fe9eaeda9201f7aab523398a3e0 60811 gitlab_12.viii.vi.orig-elasticsearch-model.tar.gz 59ed12f1366b37dd6cfe492cf22f2c312ce40386 4255484 gitlab_12.8.6.orig-elasticsearch-runway.tar.gz 2e241f72dfa80489beba2e473b1fa04fddfed71f 3755 gitlab_12.8.6.orig-faraday-middleware-aws-signers-v4.tar.gz aacfb7721bc0bd05de4b3b4291e5b4da3d49179a 88783952 gitlab_12.8.vi.orig.tar.gz 522a22e3c5e37d3594e8aee4251049fd42116d06 83908 gitlab_12.8.half-dozen-1.debian.tar.xz 334a3609a6310926fc895a70086c776012dc6ed7 8910 gitlab_12.8.6-1_amd64.buildinfo Checksums-Sha256: 8d431050553409f1fa8fc4db1b80180485906d0f3ee513301e9746699e3d5627 3827 gitlab_12.8.six-one.dsc 865bf3c44c94c034d0160fa11d523767e2ad93adddb26912f6fa816e7028b0ac 107994 gitlab_12.eight.6.orig-batty-benchmarks.tar.gz 2a941205948d46f6e2898efcf654374273df1352d51ceb1275353297b6291515 60811 gitlab_12.eight.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.8.half dozen-1_amd64.buildinfo Files: f5f53c9b2c31f5f9053f04f8c45ca671 3827 cyberspace optional gitlab_12.viii.half-dozen-i.dsc 86272733445219b43964f8c427f55a7a 107994 cyberspace optional gitlab_12.8.6.orig-derailed-benchmarks.tar.gz 26325adc0c160cad7b465f4629c82ad2 60811 net optional gitlab_12.viii.6.orig-elasticsearch-model.tar.gz bb2d2fab33c50b0cada8a5ab54146e4e 4255484 cyberspace optional gitlab_12.8.6.orig-elasticsearch-rails.tar.gz 16d290ed265b6d0e686ba38043bae007 3755 net optional gitlab_12.8.6.orig-faraday-middleware-aws-signers-v4.tar.gz 1eae463f1c9fd008d951411bda95e1b8 88783952 net optional gitlab_12.8.6.orig.tar.gz 094b5b318bfeab01b6c1a408080e99f5 83908 cyberspace optional gitlab_12.8.6-i.debian.tar.xz d1110e7633c005e2acbbc85622635966 8910 internet optional gitlab_12.8.half-dozen-1_amd64.buildinfo -----Brainstorm PGP SIGNATURE----- iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAl58mlwACgkQj1PgGTsp S3Wh9xAApEYK/nVBATSm0hqjZ5zndfhLvD6JxCxQYDya8zi/bD/N8dIeGx6mfd2Z kzXXoHX34xW1s8KpQsFj2sDJQHOOXzWzo+f6nZPN3i2a9e3BIsrFJrcTh8UqcO/I 9lDO5xdEywE1s5iDE6V7+DlmMJXJBSBKUz172CR5nypum57O8BKfjVW/gtHf+WjW /xJeJt7reiBlT4KPor+ZUdNu3NmxOOK/A3TZfqtx0H3jhvZYhZbWxe7YIClRZVgB ra0XpdHWxaihe868CDxNPltpEljEEDwVq8o76n7Dl2oD7QDebLkXoG9dw0v1XBky Krw1xyXsf8UTNcYbv8qqI5V5YDz7GqhI9EtT8mwWuACTB8ml5aKpJ1Mkqa3HZgqG y0OlCCf8mYOuZfI7tG4jF9QlOE0WQzrKk/NIUd9Yk8kcSgR3tAhsa9SjKYBXaF/d Due west/QlsFtWDdFs/uTGbChzrgjcBR8xrFX69VgWQFutU2O37rt+iJF3XMKSGq6dw83F A02JW5yY8DjkG/ODbL5KJA4Ymkth12xtjKn32qVQ3JtSYII1H6XsTTslnx0armhl tJ/D9o33dz/lOn2z29iVF3Os2cpoaokLHR+mww5zMpIFY1Q9tBOHgmsLQCPj7UqF I8HppNGRNm0HaHBN9nxxX+7lvjnQqSAV9w58O73u/98kaPtM7pU= =nS7M -----Cease PGP SIGNATURE-----
Bug archived. Asking was from Debbugs Internal Request <possessor@bugs.debian.org> to internal_control@bugs.debian.org. (Wed, 12 Aug 2020 07:26:22 GMT) (total text, mbox, link).
Transport a study that this issues log contains spam.
Debian problems tracking system ambassador <owner@bugs.debian.org>. Last modified: Sat April 16 01:35:51 2022 ; Machine Name: buxtehude
Debian Bug tracking system
Debbugs is complimentary software and licensed under the terms of the GNU Public License version two. 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."
Enviar um comentário