[DRE-maint] Bug#916306: gitlab: Error during gitlab installation
Package: gitlab Version: 11.3.11+dfsg-1 Followup-For: Bug #916306 Here is the config after purging postgresql and gitlab, gitaly and trying to install gitlab. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (450, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii asciidoctor 1.5.8-1 ii bc1.07.1-2+b1 ii bundler 1.16.1-3 ii bzip2 1.0.6-9 ii dbconfig-pgsql2.0.10 ii debconf [debconf-2.0] 1.5.69 ii gitlab-common 11.3.11+dfsg-1 ii gitlab-shell 8.3.3+dfsg-2 ii gitlab-workhorse 7.4.0+debian-2 ii lsb-base 10.2018112800 ii nginx 1.14.1-1 ii nginx-extras [nginx] 1.14.1-1 ii nodejs8.11.2~dfsg-1 ii npm 5.8.0+ds6-2 ii openssh-client1:7.9p1-4 ii postgresql-client 11+197 ii postgresql-client-11 [postgresql-client] 11.1-1+b2 ii postgresql-contrib11+197 ii rake 12.3.1-3 ii redis-server 5:5.0.2-1 ii ruby 1:2.5.1 ii ruby-ace-rails-ap 4.1.1-1 ii ruby-acts-as-taggable-on 5.0.0-2 ii ruby-addressable 2.5.2-1 ii ruby-akismet 2.0.0-1 ii ruby-arel 6.0.4-1 ii ruby-asana0.6.0-1 ii ruby-asciidoctor-plantuml 0.0.8-1 ii ruby-asset-sync 2.4.0-1 ii ruby-attr-encrypted 3.1.0-1 ii ruby-babosa 1.0.2-2 ii ruby-base32 0.3.2-3 ii ruby-batch-loader 1.2.1-1 ii ruby-bcrypt-pbkdf 1.0.0-2 ii ruby-bootstrap-form 2.7.0-1 ii ruby-browser 2.5.3-1 ii ruby-carrierwave 1.2.3-1 ii ruby-charlock-holmes 0.7.6-1 ii ruby-chronic 0.10.2-3 ii ruby-chronic-duration 0.10.6-1 ii ruby-commonmarker 0.17.9-1 ii ruby-connection-pool 2.2.2-1 ii ruby-creole 0.5.0-2 ii ruby-default-value-for3.1.0-1 ii ruby-device-detector 1.0.1-2 ii ruby-devise 4.4.3-1 ii ruby-devise-two-factor3.0.3-1 ii ruby-diffy3.2.1-1 ii ruby-doorkeeper 4.4.2-1 ii ruby-doorkeeper-openid-connect1.5.2-1 ii ruby-dropzonejs-rails 0.8.2-1 ii ruby-ed25519 1.2.4-1 ii ruby-email-reply-trimmer 0.1.6-1 ii ruby-escape-utils 1.2.1-1+b1 ii ruby-excon0.60.0-1 ii ruby-faraday 0.13.1-2 ii ruby-fast-blank 1.0.0-1+b1 ii ruby-flipper 0.13.0-3 pn ruby-flipper-active-record pn ruby-flipper-active-support-cache-store ii ruby-fog-aliyun 0.2.0-1 ii ruby-fog-aws 2.0.1-1 ii ruby-fog-core 1.45.0-2 ii ruby-fog-google 1.8.1-2 ii ruby-fog-local0.3.0-1 ii ruby-fog-openstack0.1.6-4 ii ruby-fog-rackspace0.1.1-4 ii ruby-fogbugz 0.2.1-3 ii ruby-font-awesome-rails 4.7.0.4-1 ii ruby-gemojione3.3.0-1 ii ruby-gettext-i18n-rails 1.8.0-1 ii ruby-gettext-i18n-rails-js1.3.0+dfsg-2 pn ruby-gitaly-proto ii ruby-github-linguist 5.3.3-1 ii ruby-github-markup1.7.0+dfsg-2 ii ruby-gitlab-flowdock-git-hook 1.0.1-4 ii ruby-gollum-lib 4.2.7.5-3 ii ruby-gollum-rugged-adapter0.4.4.1-2 ii ruby-gon 6.2.1-1 ii ruby-google-api-client
[DRE-maint] Bug#915136: Test are working
On 12/13/18 4:39 AM, David López Zajara (Er_Maqui) wrote: > I've leaved the git installation untouched for if you need to do more > tests. Now, I know if I do a clean reinstall will be working, but I > think we need to check it and find the problem. > > @praveen, if you suggest me to do the reinstall and close the bug, I'll > do it. Or maybe we can do another test, or move the failing machine to a > VM for further testing. I don't know. But I see clear the problem are: > or a problem from OS (maybe some old ruby gems installed on machine?) or > a problem on gitlab, generated by itself by using it. > > I can do comparisions of "anything" you need. Please let me know how to > proceed now. It can be a combination of many local changes so I don't think keeping that is much useful as we are not able to reproduce it on a clean install. I suggest you do a clean reinstall and we close this bug. signature.asc Description: OpenPGP digital signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#916306: gitlab: Error during gitlab installation
Purging still does not fix this. $ sudo apt-get purge gitaly\* gitlab\* Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'gitaly' for glob 'gitaly*' Note, selecting 'gitlab-shell' for glob 'gitlab*' Note, selecting 'gitlab-common' for glob 'gitlab*' Note, selecting 'gitlab-cli' for glob 'gitlab*' Note, selecting 'gitlab' for glob 'gitlab*' Note, selecting 'gitlab-runner' for glob 'gitlab*' Note, selecting 'gitlab-workhorse' for glob 'gitlab*' Note, selecting 'gitlab-ci-multi-runner' for glob 'gitlab*' Note, selecting 'gitlab-runner' instead of 'gitlab-ci-multi-runner' Package 'gitlab-cli' is not installed, so not removed Package 'gitlab-runner' is not installed, so not removed ... The following packages will be REMOVED: gitaly* gitlab* gitlab-common* gitlab-shell* gitlab-workhorse* 0 upgraded, 0 newly installed, 5 to remove and 37 not upgraded. 1 not fully installed or removed. After this operation, 165 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 766431 files and directories currently installed.) Removing gitlab (11.3.11+dfsg-1) ... /etc/gitlab/gitlab-debian.conf not found. Not removing anything. Removing gitaly (0.125.1+debian-3) ... Removing gitlab-common (11.3.11+dfsg-1) ... Removing gitlab-shell (8.3.3+dfsg-2) ... Removing gitlab-workhorse (7.4.0+debian-2) ... (Reading database ... 749351 files and directories currently installed.) Purging configuration files for gitlab-common (11.3.11+dfsg-1) ... Removing user: gitlab 127 userdel: gitlab mail spool (/var/mail/gitlab) not found Purging configuration files for gitlab (11.3.11+dfsg-1) ... /var/lib/gitlab-common/gitlab-common.defaults not found. Not removing anything. dpkg: warning: while removing gitlab, directory '/var/log/gitlab' not empty so not removed Purging configuration files for gitaly (0.125.1+debian-3) ... Processing triggers for systemd (239-13) ... Now trying to install gitlab: $ sudo apt-get install gitlab Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: ecj ecj-gcj ecj1 gcj-6-jre-lib libantlr-java libecj-java libecj-java-gcj libgcj-bc libgcj-common libgcj17 libqt4-dbus libqt4-xml libqtcore4 libqtdbus4 libqtgui4 qdbus qt-at-spi qtcore4-l10n Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: gitaly gitlab-common gitlab-shell gitlab-workhorse The following NEW packages will be installed: gitaly gitlab gitlab-common gitlab-shell gitlab-workhorse 0 upgraded, 5 newly installed, 0 to remove and 37 not upgraded. Need to get 0 B/56.7 MB of archives. After this operation, 165 MB of additional disk space will be used. Do you want to continue? [Y/n] Preconfiguring packages ... Selecting previously unselected package gitlab-common. (Reading database ... 749170 files and directories currently installed.) Preparing to unpack .../gitlab-common_11.3.11+dfsg-1_all.deb ... Unpacking gitlab-common (11.3.11+dfsg-1) ... Selecting previously unselected package gitaly. Preparing to unpack .../gitaly_0.125.1+debian-3_amd64.deb ... Unpacking gitaly (0.125.1+debian-3) ... Selecting previously unselected package gitlab-shell. Preparing to unpack .../gitlab-shell_8.3.3+dfsg-2_amd64.deb ... Unpacking gitlab-shell (8.3.3+dfsg-2) ... Selecting previously unselected package gitlab-workhorse. Preparing to unpack .../gitlab-workhorse_7.4.0+debian-2_amd64.deb ... Unpacking gitlab-workhorse (7.4.0+debian-2) ... Selecting previously unselected package gitlab. Preparing to unpack .../gitlab_11.3.11+dfsg-1_all.deb ... Unpacking gitlab (11.3.11+dfsg-1) ... Setting up gitlab-common (11.3.11+dfsg-1) ... Creating/updating gitlab user account... adduser: Warning: The home directory `/var/lib/gitlab' does not belong to the user you are currently creating. Registering /etc/gitlab-common/gitlab-common.conf via ucf Creating config file /etc/gitlab-common/gitlab-common.conf with new version Setting up gitaly (0.125.1+debian-3) ... Resolving dependencies... Using concurrent-ruby 1.1.3 Following files may not be writable, so sudo is needed: /usr/local/bin /var/lib/gems/2.5.0 /var/lib/gems/2.5.0/build_info /var/lib/gems/2.5.0/cache /var/lib/gems/2.5.0/doc /var/lib/gems/2.5.0/extensions /var/lib/gems/2.5.0/gems /var/lib/gems/2.5.0/specifications Using i18n 1.1.1 Using minitest 5.11.3 Using thread_safe 0.3.6 Using tzinfo 1.2.5 Using activesupport 5.2.2 Using bundler 1.17.1 Using charlock_holmes 0.7.6 Using crass 1.0.4 Using escape_utils 1.2.1 Using multipart-post 2.0.0 Using faraday 0.15.4 Using json 2.1.0 Using gemojione 3.3.0 Using google-protobuf 3.6.1 Using googleapis-common-protos-types 1.0.2 Using grpc 1.17.0 (x86_64-linux) Using gitaly-proto 0.118.1 Using mime-types-data 3.2018.0812 Using mime-types 3.2.2 Using rugged 0.27.7 Using github-linguist 5.3.3 Using github-markup 1.7.0 Using gitlab-gollum-rug
[DRE-maint] Bug#916306: gitlab: Error during gitlab installation
On Wed, 12 Dec 2018 12:49:37 -0800 Pranith Kumar wrote: > Package: gitlab > Version: 11.3.11+dfsg-1 > Severity: normal > > Dear Maintainer, > > While installing gitlab, I am getting the following error. Please fix. > > Setting up gitlab (11.3.11+dfsg-1) ... > Creating runtime directories for gitlab... > Updating file permissions... > Configuring hostname and email... > sed: -e expression #1, char 41: unknown option to `s' > dpkg: error processing package gitlab (--configure): > installed gitlab package post-installation script subprocess returned error > exit status 1 > Errors were encountered while processing: > gitlab > E: Sub-process /usr/bin/dpkg returned an error code (1) > I think the previous choices are still interfering in new installation. For example, * gitlab/remote/host: localhost gitlab/db/app-user: www-data@localhost I suggest you do a purge and then install gitlab again. signature.asc Description: OpenPGP digital signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-parallel 1.12.1-2 MIGRATED to testing
FYI: The status of the ruby-parallel source package in Debian's testing distribution has changed. Previous version: 1.12.0-1 Current version: 1.12.1-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] schleuder is marked for autoremoval from testing
schleuder 3.3.0-6 is marked for autoremoval from testing on 2018-12-29 It (build-)depends on packages with these RC bugs: 913843: ruby-mail-gpg: ruby-mail-gpg FTBFS with gpgme 1.12.0 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-kramdown-rfc2629 1.2.9-2 MIGRATED to testing
FYI: The status of the ruby-kramdown-rfc2629 source package in Debian's testing distribution has changed. Previous version: 1.2.9-1 Current version: 1.2.9-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] ruby-mail-gpg is marked for autoremoval from testing
ruby-mail-gpg 0.4.0-1 is marked for autoremoval from testing on 2018-12-29 It is affected by these RC bugs: 913843: ruby-mail-gpg: ruby-mail-gpg FTBFS with gpgme 1.12.0 ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#915136: Test are working
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I've created a VM with debian-unstable and do a clean install. After it, I've moved repositories, uploads, ssh keys, and database. A difference between my installation and the test installation: On the test installation (let's call it git-test) database are owned by postgresql user, and on my original installation (let's call git), database is owned by gitlab user. I've tested accessing the git-test web. It's working OK. I've try to move /var/lib/gitlab to /home/gitlab and I've placed a symlink on their place. I didn't change any config for doing it. After restart gitlab all is working OK. gitlab:check also do all OK. I've diffed the /etc/gitlab of git-test and /etc/gitlab of git. There's the result: (/etc/gitlab folder are "git" and gitlab one are "git-test") kanade:~# diff /etc/gitlab gitlab Common subdirectories: /etc/gitlab/environments and gitlab/environments diff /etc/gitlab/gitlab-debian.conf gitlab/gitlab-debian.conf 9,10c9,10 < GITLAB_HOST="git.example.net" < GITLAB_EMAIL_FROM="no-re...@git.example.net" - --- > GITLAB_HOST="git-test.example.net" > GITLAB_EMAIL_FROM="no-re...@git-test.example.net" 12,15c12,14 < GITLAB_EMAIL_REPLY_TO="no-re...@git.example.net" < GITLAB_HTTPS="true" < gitlab_letsencrypt="true" < gitlab_letsencrypt_email="doma...@example.net" - --- > GITLAB_EMAIL_REPLY_TO="no-re...@git-test.example.net" > GITLAB_HTTPS="false" > gitlab_letsencrypt="false" diff /etc/gitlab/gitlab.yml gitlab/gitlab.yml 35,36c35,36 < port: 443 # Set to 443 if using HTTPS, see installation.md#using-https for additional HTTPS configuration details < https: true # Set to true if using HTTPS, see installation.md#using-https for additional HTTPS configuration details - --- > #port: 80 # Set to 443 if using HTTPS, see installation.md#using-https for additional HTTPS configuration details > https: false # Set to true if using HTTPS, see installation.md#using-https for additional HTTPS configuration details 62,63c62 < #user_home: /var/lib/gitlab < user_home: /home/gitlab - --- > user_home: /var/lib/gitlab 164c163 < https: true # Set to true if you serve the pages with HTTPS - --- > https: false # Set to true if you serve the pages with HTTPS 511,512c510 < #path: /var/lib/gitlab/repositories/ < path: /home/gitlab/repositories/ - --- > path: /var/lib/gitlab/repositories/ Common subdirectories: /etc/gitlab/initializers and gitlab/initializers Common subdirectories: /etc/gitlab/locales and gitlab/locales Common subdirectories: /etc/gitlab/prometheus and gitlab/prometheus Common subdirectories: /etc/gitlab/routes and gitlab/routes Only in /etc/gitlab: ssl kanade:~# I've leaved the git installation untouched for if you need to do more tests. Now, I know if I do a clean reinstall will be working, but I think we need to check it and find the problem. @praveen, if you suggest me to do the reinstall and close the bug, I'll do it. Or maybe we can do another test, or move the failing machine to a VM for further testing. I don't know. But I see clear the problem are: or a problem from OS (maybe some old ruby gems installed on machine?) or a problem on gitlab, generated by itself by using it. I can do comparisions of "anything" you need. Please let me know how to proceed now. Thanks, https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres somos esclavos de la historia -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYf0F71OtDykDsKZdCU2zE9sy6H8FAlwRlQsACgkQCU2zE9sy 6H+XdQ//fh44Fi+ALctCVnvDYUUanUpSxebGJZiJrR5Han7ejGywkqlJfmS1Zy/F RoRcgjF4Tn9Bh+wqOA+eFQWqjI2tUNVgnc3+XFvug9KeGl8rPLzbj8HpPDRfolS1 z01ejOq+d+wO5CzEJE1wyScDSkw9W0HgjHg7zUF053LJIl0hwgMt37m2UzPsiUzm CO7pzZet3mUIWGFCnkxRgyML+fUlylts+emGdbRGO2uwWfxrIIPT2GhR+t4O89MX XwTvLvagmcAUiipPqzHujVOyIyrpf4HfAQQOS0m1D0tLY/y6JkJLtQA1rcfBSwUf xW31VcJqqvxGrJ3irdU6GobwLoRJawH3ZTDzo/l5+bmxx5Btxo5aZ62oA9r+E5c8 0rFe0wIQuKS2OSzUa4QyYTFqWA+FwmhRKpZEnEHb7wBJbNgcgIPdWj37JVucADcX ETJKRBRjKspvcdU5fHD/yIW9MW0SvT2JG7u80CH8hEU6JtkHg4o7G9TIOTkzBWao hwYj7aRYcJvQmfQUxd/9sipj5SYe48j2ws/qUtkGMx+RYLyFL0b6CVIWkAgCjtKe Kpo4Gplivs1kQH5fQsgwk+OlBzvzw0X4yOQE4P3LtiXQTQYDV4QYdcmKixG7s9/7 hkTHGbpf0NgJn1QyDumR2Qe9K+5ZxnvEQX9C4zCjqmmB2672teM= =gBtW -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Processed: forcibly merging 916243 916306
Processing commands for cont...@bugs.debian.org: > forcemerge 916243 916306 Bug #916243 [gitlab] gitlab installation failure Bug #916306 [gitlab] gitlab: Error during gitlab installation Severity set to 'important' from 'normal' Merged 916243 916306 > thanks Stopping processing here. Please contact me if you need assistance. -- 916243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916243 916306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916306 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#916306: gitlab: Error during gitlab installation
Package: gitlab Version: 11.3.11+dfsg-1 Severity: normal Dear Maintainer, While installing gitlab, I am getting the following error. Please fix. Setting up gitlab (11.3.11+dfsg-1) ... Creating runtime directories for gitlab... Updating file permissions... Configuring hostname and email... sed: -e expression #1, char 41: unknown option to `s' dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: gitlab E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (450, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii asciidoctor 1.5.8-1 ii bc1.07.1-2+b1 ii bundler 1.16.1-3 ii bzip2 1.0.6-9 ii dbconfig-pgsql2.0.10 ii debconf [debconf-2.0] 1.5.69 ii gitlab-common 11.3.11+dfsg-1 ii gitlab-shell 8.3.3+dfsg-2 ii gitlab-workhorse 7.4.0+debian-2 ii lsb-base 10.2018112800 ii nginx 1.14.1-1 ii nginx-extras [nginx] 1.14.1-1 ii nodejs8.11.2~dfsg-1 ii npm 5.8.0+ds6-2 ii openssh-client1:7.9p1-4 ii postgresql-client 11+197 ii postgresql-client-11 [postgresql-client] 11.1-1+b2 ii postgresql-contrib11+197 ii rake 12.3.1-3 ii redis-server 5:5.0.2-1 ii ruby 1:2.5.1 ii ruby-ace-rails-ap 4.1.1-1 ii ruby-acts-as-taggable-on 5.0.0-2 ii ruby-addressable 2.5.2-1 ii ruby-akismet 2.0.0-1 ii ruby-arel 6.0.4-1 ii ruby-asana0.6.0-1 ii ruby-asciidoctor-plantuml 0.0.8-1 ii ruby-asset-sync 2.4.0-1 ii ruby-attr-encrypted 3.1.0-1 ii ruby-babosa 1.0.2-2 ii ruby-base32 0.3.2-3 ii ruby-batch-loader 1.2.1-1 ii ruby-bcrypt-pbkdf 1.0.0-2 ii ruby-bootstrap-form 2.7.0-1 ii ruby-browser 2.5.3-1 ii ruby-carrierwave 1.2.3-1 ii ruby-charlock-holmes 0.7.6-1 ii ruby-chronic 0.10.2-3 ii ruby-chronic-duration 0.10.6-1 ii ruby-commonmarker 0.17.9-1 ii ruby-connection-pool 2.2.2-1 ii ruby-creole 0.5.0-2 ii ruby-default-value-for3.1.0-1 ii ruby-device-detector 1.0.1-2 ii ruby-devise 4.4.3-1 ii ruby-devise-two-factor3.0.3-1 ii ruby-diffy3.2.1-1 ii ruby-doorkeeper 4.4.2-1 ii ruby-doorkeeper-openid-connect1.5.2-1 ii ruby-dropzonejs-rails 0.8.2-1 ii ruby-ed25519 1.2.4-1 ii ruby-email-reply-trimmer 0.1.6-1 ii ruby-escape-utils 1.2.1-1+b1 ii ruby-excon0.60.0-1 ii ruby-faraday 0.13.1-2 ii ruby-fast-blank 1.0.0-1+b1 ii ruby-flipper 0.13.0-3 pn ruby-flipper-active-record pn ruby-flipper-active-support-cache-store ii ruby-fog-aliyun 0.2.0-1 ii ruby-fog-aws 2.0.1-1 ii ruby-fog-core 1.45.0-2 ii ruby-fog-google 1.8.1-2 ii ruby-fog-local0.3.0-1 ii ruby-fog-openstack0.1.6-4 ii ruby-fog-rackspace0.1.1-4 ii ruby-fogbugz 0.2.1-3 ii ruby-font-awesome-rails 4.7.0.4-1 ii ruby-gemojione3.3.0-1 ii ruby-gettext-i18n-rails 1.8.0-1 ii ruby-gettext-i18n-rails-js1
[DRE-maint] Bug#915136: Solution not applicable
On 12/12/18 9:09 PM, David López Zajara (Er_Maqui) wrote: > Maybe I should try to uninstall gitlab and reinstall it? I think you can try that. Try to take the database to a different machine and do a clean install. One possibility is any files left over in /etc/gitlab which were subsequently removed from gitlab. Try comparing the files in gitlab package source repo's config directory and your /etc/gitlab. signature.asc Description: OpenPGP digital signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#915136: Solution not applicable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Thanks for the response. Unfortunately, my /var/lib/gems/2.5.0 is empty. kanade:/var/lib/gems# ls 2.5.0/ -la total 8 drwxr-xr-x 2 root root 4096 Mar 4 2018 . drwxr-xr-x 3 root root 4096 Dec 12 16:02 .. (I didn't have another folder on /var/lib/gems too). If there's any other place where I can check please tell me. Doing a dpkg-reconfigure gitlab, I have these debug: kanade:/var/lib/gems# dpkg-reconfigure gitlab Creating runtime directories for gitlab... Updating file permissions... Configuring hostname and email... Configuring nginx with HTTPS... Configuring gitlab with HTTPS... Updating gitlab_url in gitlab-shell configuration... Configuring letsencrypt... Let's encrypt certificate already present. Registering /usr/lib/tmpfiles.d/gitlab.conf via ucf /etc/systemd/system/gitlab-mailroom.service.d/override.conf already exist /etc/systemd/system/gitlab-unicorn.service.d/override.conf already exist /etc/systemd/system/gitlab-sidekiq.service.d/override.conf already exist /etc/systemd/system/gitlab-workhorse.service.d/override.conf already exist Registering /etc/gitlab-shell/config.yml via ucf Registering /etc/gitlab/gitlab.yml via ucf Registering /etc/gitlab/gitlab-debian.conf via ucf Reloading nginx configuration... dbconfig-common: writing config to /etc/dbconfig-common/gitlab.conf dbconfig-common: flushing administrative password NOTICE: extension "pg_trgm" already exists, skipping CREATE EXTENSION Verifying we have all required libraries... Resolving dependencies. Bundle complete! 172 Gemfile dependencies, 316 gems now installed. Gems in the groups development and test were not installed. Use `bundle info [gemname]` to see where a bundled gem is installed. Running final rake tasks and tweaks... gitlab_production database is not empty, skipping gitlab setup Installing node modules... npm WARN saveError ENOENT: no such file or directory, open '/home/gitlab/yarn/package.json' npm WARN enoent ENOENT: no such file or directory, open '/home/gitlab/yarn/package.json' npm WARN yarn No description npm WARN yarn No repository field. npm WARN yarn No README data npm WARN yarn No license field. + yarn@1.12.3 updated 1 package in 1.811s yarn install v1.12.3 [1/4] Resolving packages... [2/4] Fetching packages... info fsevents@1.2.4: The platform "linux" is incompatible with this module. info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from installation. [3/4] Linking dependencies... [4/4] Building fresh packages... $ node ./scripts/frontend/postinstall.js success Dependency postinstall check passed. Done in 10.37s. Precompiling locales... All files created, make sure they are being added to your assets. If they are not, you can add them with this line (configurable): //= require_tree ./locale //= require gettext/all Precompiling assets... Webpacking... Hash: 30cea2a0e07bbb61dcaa Version: webpack 4.19.1 Time: 46916ms Built at: 12/12/2018 4:19:15 PM Running rake checks... Check if Gitlab is configured correctly... Maybe I should try to uninstall gitlab and reinstall it? https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres somos esclavos de la historia -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYf0F71OtDykDsKZdCU2zE9sy6H8FAlwRK7IACgkQCU2zE9sy 6H8XjA//Uy7DcuwNsrHeJOiS/kOxinzu+20/bx78aiBSNiR9ETsJ8n8SEsl6wJM7 YVM4gfChistQSA/P6Wo7+ivhS2erhBnrIpKnJZ/wAwQ0x9qF6aaYYpnRQ0xJRD9+ Pmm0IAdEoXUEXizb4Aw5iX7Ef/jeE4JgkzUwp7+c+OBFZUn3Kf5US2L0JjtijI02 eQqqGqX11hcR++HbElz4NQGiYdPYCU1o9VzmiDkMVlKMD/lE+0hlADWUzDR4gYa9 4jJcc8LoUoWdWJl024iqJCsJFFuWrNdcnWH8Z9d93E5ko8fLGyw9W9WlFX8kcI9s ZbP5/gHcRugW8AmmCfgI1OyBh/AR3cYXM/nJdH+7ObH1+of+bwXyM1AUDfSYrgQx tFkj+z6evopRBM9jRGPj3kmM96gGelXv9t94q6RzG+LvRpK/WtQ7RKKQShRMDoxW RoMuBKIb8TXh/8XCqw1KhfxbNvYFWoZVf5l5Dnsq/Fqq1pvu7eEA+3TYDRQBZ+HH MvIM/IiYtNaJ220KTsO6cfQ/GA2xuKvp/sjkXTjhFxw3mBI/BXfrHmcu06twVcHP rg7IjIkhnewrnizoyI+6XaczqhAOP1ijPUz0vxvTBpWAAhpbKJf8z8+39dG/WLZa btX9ppmo0kiohFlNDu/3YX9+u3Diur9ogv10NLOu2FKh9mzLB9Y= =GdDI -END PGP SIGNATURE- ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#915053: marked as done (gitlab: Err 500 when go to the project page(any project))
Your message dated Wed, 12 Dec 2018 17:58:57 +0530
with message-id <5d7e0674-8c30-9db2-aca7-91e087d2c...@onenetbeyond.org>
and subject line Re: Bug#915053: gitlab: Err 500 when go to the project
page(any project)
has caused the Debian Bug report #915053,
regarding gitlab: Err 500 when go to the project page(any project)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
915053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 11.3.10+dfsg-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When go to any project receive Err 500:
Started GET "/meteo/meteo" for 192.168.3.1 at 2018-11-29 21:43:55 +0200
Processing by ProjectsController#show as HTML
Parameters: {"namespace_id"=>"meteo", "id"=>"meteo"}
Read fragment
views/meteo/meteo/master/e34a8d6d6e4ae0c037caaf297bcf3f92877c76f5/application_settings/1-20181024143448558017000/false/false/success/en/9fe84ac8dd39e3a1ffb63dffbd2d29da
(1.3ms)
Completed 500 Internal Server Error in 4925ms (ActiveRecord: 253.8ms)
ActionView::Template::Error (wrong number of arguments (given 1, expected 2)):
38: = sprite_icon('ellipsis_h', size: 12)
39:
40: .commiter
41: - commit_author_link = commit_author_link(commit, avatar:
false, size: 24)
42: - commit_timeago =
time_ago_with_tooltip(commit.authored_date, placement: 'bottom')
43: - commit_text = _('%{commit_author_link} authored
%{commit_timeago}') % { commit_author_link: commit_author_link, commit_timeago:
commit_timeago }
44: #{ commit_text.html_safe }
app/helpers/commits_helper.rb:210:in `clean'
app/helpers/commits_helper.rb:136:in `commit_person_link'
app/helpers/commits_helper.rb:10:in `commit_author_link'
app/views/projects/commits/_commit.html.haml:41:in `block in
_app_views_projects_commits__commit_html_haml__4510560646380060465_47275137929220'
app/views/projects/commits/_commit.html.haml:18:in
`_app_views_projects_commits__commit_html_haml__4510560646380060465_47275137929220'
app/views/shared/_commit_well.html.haml:4:in
`_app_views_shared__commit_well_html_haml__116673998689084462_47275138176200'
app/views/projects/_files.html.haml:11:in
`_app_views_projects__files_html_haml___338566813562587368_47275142850220'
app/views/projects/show.html.haml:44:in
`_app_views_projects_show_html_haml___1738900495709899687_47275132961580'
lib/gitlab/i18n.rb:53:in `with_locale'
lib/gitlab/i18n.rb:59:in `with_user_locale'
app/controllers/application_controller.rb:412:in `set_locale'
lib/gitlab/middleware/multipart.rb:101:in `call'
lib/gitlab/request_profiler/middleware.rb:14:in `call'
lib/gitlab/middleware/go.rb:17:in `call'
lib/gitlab/etag_caching/middleware.rb:11:in `call'
lib/gitlab/middleware/read_only/controller.rb:38:in `call'
lib/gitlab/middleware/read_only.rb:16:in `call'
lib/gitlab/middleware/basic_health_check.rb:25:in `call'
lib/gitlab/request_context.rb:18:in `call'
lib/gitlab/metrics/requests_rack_middleware.rb:27:in `call'
lib/gitlab/middleware/release_env.rb:10:in `call'
I cannot see details about projects, activity, etc.
Expect to see the project page.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gitlab depends on:
ii asciidoctor 1.5.7.1-1
ii bc1.07.1-2+b1
ii bundler 1.16.1-3
ii bzip2 1.0.6-9
ii dbconfig-pgsql2.0.10
ii debconf [debconf-2.0] 1.5.69
ii gitlab-common 11.3.10+dfsg-2
ii gitlab-shell 8.3.3+dfsg-1
ii gitlab-workhorse 6.1.1+debian-3
ii lsb-base 9.20170808
ii nginx 1.14.1-1
ii nginx-full [nginx]1.14.1-1
ii nodejs8.11.2~dfsg-1
ii npm 5.8.0+ds6-2
ii openssh-client1:7.9p1-4
ii postfix [mail-transport-agent]
[DRE-maint] Bug#915136: More info
On 12/11/18 9:51 AM, Pirate Praveen wrote: >> Maybe we need to report the bug to upstream too? I think, probably the >> bug >> are debian-specific but they can give us some new information. > > Yes, I think only upstream can help here. Try the solution mentioned here, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915053#67 signature.asc Description: OpenPGP digital signature ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#915053: gitlab: Err 500 when go to the project page(any project)
Maby is a good idea to add a check task to see if /var/lib/gems is
incompatible wit gitlab.
Dragos Jarca
On 12.12.2018 13:09, Dragos Jarca wrote:
Ok...after a lot of research of my problem, solved it!
Th problem was /var/lib/gems/2.5.0 that have multiple vesrsions of
same gem. I renamed this dir and reconfigured gitlab. Now all is ok!
Just wait to next varsion(11.5.3) in experimental. The last version in
experimental I think is a goog option.
Dragos Jarca
On 09.12.2018 11:36, Dragos Jarca wrote:
Hi
Updated to 11.4.9, but the problem exists.
Seems tat gitlab API not work in all forms described in documentation.
root@omv:/etc/gitlab# curl --header 'PRIVATE-TOKEN: ***'
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd%2Esql/raw?ref=master
alter table ws add column if not exists isactive TINYINT not null
default 0;
alter table ws add column if not exists apikey varchar(128);
root@omv:/etc/gitlab# curl
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd%2Esql/raw?ref=master?private_token=***
{"message":"404 Project Not Found"}
root@omv:/etc/gitlab# curl --header '_gitlab_session=*'
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd%2Esql/raw?ref=master
{"message":"404 Project Not Found"}
In web interface _gitlab_session is responsable, and seems not no work.
Strange is that:
https://gitlab.dynamicpuzzle.ro/meteo/meteo/blob/master/db/upd.sql
not work and return ERR 500
and
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd.sql/raw?ref=master
work and return content of file.
I can work in external git clients, but cannot see thhe project files
and commits in the web interface.
Dragos Jarca
On 06.12.2018 10:00, Pirate Praveen wrote:
On 12/4/18 10:03 PM, Dragos Jarca wrote:
Yes, tried on different browsers, different os, different browsers on
moile phones, smart tb browser, etc.
I have just uploaded gitlab 11.4.9 to experimental. See if that fixes
the issues.
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#915053: gitlab: Err 500 when go to the project page(any project)
Ok...after a lot of research of my problem, solved it!
Th problem was /var/lib/gems/2.5.0 that have multiple vesrsions of same
gem. I renamed this dir and reconfigured gitlab. Now all is ok!
Just wait to next varsion(11.5.3) in experimental. The last version in
experimental I think is a goog option.
Dragos Jarca
On 09.12.2018 11:36, Dragos Jarca wrote:
Hi
Updated to 11.4.9, but the problem exists.
Seems tat gitlab API not work in all forms described in documentation.
root@omv:/etc/gitlab# curl --header 'PRIVATE-TOKEN: ***'
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd%2Esql/raw?ref=master
alter table ws add column if not exists isactive TINYINT not null
default 0;
alter table ws add column if not exists apikey varchar(128);
root@omv:/etc/gitlab# curl
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd%2Esql/raw?ref=master?private_token=***
{"message":"404 Project Not Found"}
root@omv:/etc/gitlab# curl --header '_gitlab_session=*'
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd%2Esql/raw?ref=master
{"message":"404 Project Not Found"}
In web interface _gitlab_session is responsable, and seems not no work.
Strange is that:
https://gitlab.dynamicpuzzle.ro/meteo/meteo/blob/master/db/upd.sql
not work and return ERR 500
and
https://gitlab.dynamicpuzzle.ro/api/v4/projects/14/repository/files/db%2Fupd.sql/raw?ref=master
work and return content of file.
I can work in external git clients, but cannot see thhe project files
and commits in the web interface.
Dragos Jarca
On 06.12.2018 10:00, Pirate Praveen wrote:
On 12/4/18 10:03 PM, Dragos Jarca wrote:
Yes, tried on different browsers, different os, different browsers on
moile phones, smart tb browser, etc.
I have just uploaded gitlab 11.4.9 to experimental. See if that fixes
the issues.
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Bug#915787: marked as done (gitlab: Installation failure)
Your message dated Wed, 12 Dec 2018 13:31:56 +0530 with message-id <2ab53393-500f-4477-bd7f-b0d39d5d6...@onenetbeyond.org> and subject line Re: has caused the Debian Bug report #915787, regarding gitlab: Installation failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 915787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915787 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gitlab Version: 11.3.11+dfsg-1 Severity: important Dear Maintainer, When trying to install gitlab using "apt install gitlab", it fails with the following error message. The user chosen to run gitlab was 'www-data'. Setting up gitlab (11.3.11+dfsg-1) ... /usr/local/bin/bundle:22:in `load': cannot load such file -- /usr/share/rubygems-integration/all/gems/bundler-1.16.1/exe/bundle (LoadError) from /usr/local/bin/bundle:22:in `' dpkg: error processing package gitlab (--configure): installed gitlab package post-installation script subprocess returned error exit status 1 Setting up gitaly (0.120.1+debian-2) ... /etc/systemd/system/gitaly.service.d/override.conf already exist /usr/local/bin/bundle:22:in `load': cannot load such file -- /usr/share/rubygems-integration/all/gems/bundler-1.16.1/exe/bundle (LoadError) from /usr/local/bin/bundle:22:in `' dpkg: error processing package gitaly (--configure): installed gitaly package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: gitlab gitaly E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (450, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii asciidoctor1.5.8-1 ii bc 1.07.1-2+b1 ii bundler1.16.1-3 ii bzip2 1.0.6-9 ii dbconfig-pgsql 2.0.10 ii debconf [debconf-2.0] 1.5.69 ii exim4-daemon-light [mail-transport-agent] 4.91-8+b1 ii gitlab-common 11.3.11+dfsg-1 ii gitlab-shell 8.3.3+dfsg-2 ii gitlab-workhorse 6.1.1+debian-3 ii lsb-base 10.2018112800 ii nginx 1.14.1-1 ii nginx-extras [nginx] 1.14.1-1 ii nodejs 8.11.2~dfsg-1 ii npm5.8.0+ds6-2 ii openssh-client 1:7.9p1-4 ii postgresql-client 11+197 ii postgresql-client-11 [postgresql-client] 11.1-1+b2 ii postgresql-contrib 11+197 ii rake 12.3.1-3 ii redis-server 5:5.0.2-1 ii ruby 1:2.5.1 ii ruby-ace-rails-ap 4.1.1-1 ii ruby-acts-as-taggable-on 5.0.0-2 ii ruby-addressable 2.5.2-1 ii ruby-akismet 2.0.0-1 ii ruby-arel 6.0.4-1 ii ruby-asana 0.6.0-1 ii ruby-asciidoctor-plantuml 0.0.8-1 ii ruby-asset-sync2.4.0-1 ii ruby-attr-encrypted3.1.0-1 ii ruby-babosa1.0.2-2 ii ruby-base320.3.2-3 ii ruby-batch-loader 1.2.1-1 ii ruby-bcrypt-pbkdf 1.0.0-2 ii ruby-bootstrap-form2.7.0-1 ii ruby-browser 2.5.3-1 ii ruby-carrierwave 1.2.3-1 ii ruby-charlock-holmes 0.7.6-1 ii ruby-chronic 0.10.2-3 ii ruby-chronic-duration 0.10.6-1 ii ruby-commonmarker 0.17.9-1 ii ruby-connection-pool 2.2.2-1 ii ruby-creole0.5.0-2 ii ruby-default-value-for 3.1.0-1 ii ruby-device-detector
[DRE-maint] Bug#916243: gitlab installation failure
Control: severity -1 important On Tue, 11 Dec 2018 14:18:30 -0800 Pranith Kumar wrote: > Package: gitlab > Version: 11.3.11+dfsg-1 > Severity: important > > Dear Maintainer, > > Trying to install gitlab throws the following error, please fix. > > Setting up gitlab (11.3.11+dfsg-1) ... > `/var/www` is not writable. You should create a new dedicated user for gitlab. You are trying to reuse an existing user which has its own different home directory and permissions. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
[DRE-maint] Processed: Re: gitlab installation failure
Processing control commands: > severity -1 important Bug #916243 [gitlab] gitlab installation failure Severity set to 'important' from 'serious' -- 916243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-ruby-extras-maintainers mailing list Pkg-ruby-extras-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
