Bug#780116: backuppc: httpd should not be required

Package: backuppc Version: 3.3.0-2 Severity: minor Dear Maintainer, I think this app are a interesting option for mantain some backups, but, having some httpd package as required you're requesting to install an additional service on some servers who doesn't require it. As I can read on

Bug#897444: Updates on this problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, There's any information about this problem? I've tried to move all /usr/lib/gitlab to /home/gitlab and change path on /etc/gitlab/gitlab.yml and /etc/gitlab/gitlab-debian.conf without any change. As I've reported on initial bug, I can see all

Bug#894272: Some fixes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 re fixed by bug report #895871 / fix https://salsa.debian.org/ruby-team/gitlab/commit/42a8e904e211a78c9dd018637e339d6562fb2f4a But this bug / solution does not mention fail with 2FA or with GPG signatures. Regards, https://maqui.darkbolt.net/

Bug#894138: gitlab: 10.5.6 Problem compiling assets on post-install

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 @praveen I leave you here the "mostly" complete debug of a uninstall - purge - reinstall of 10.5.6 version. If you need any test, please tell me. rin:~# apt-get remove gitlab Reading package lists... Done Building dependency tree Reading state

Bug#894138: gitlab: 10.5.6 Problem compiling assets on post-install

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, These are the output. rin:~# ll /var/lib/gems/2.5.0/ total 40 drwxr-xr-x 2 root root 4096 Mar 8 17:02 build_info drwxr-xr-x 2 root root 12288 Mar 22 10:28 cache drwxr-xr-x 3 root root 4096 Mar 8 17:05 doc drwxr-xr-x 3 root root

Bug#894138: gitlab: 10.5.6 Problem compiling assets on post-install

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, The error after emptying folder are this: Bundle complete! 172 Gemfile dependencies, 312 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.

Bug#880276: ruby-encryptor: FTBFS: ERROR: Bug is still present?

Hi, Are this bug still present with ruby2.5? https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres somos esclavos de la historia

Bug#894272: gitlab: Problem migrating database from old installation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi praveen, I've deleted the binary specified. Now installation are completed. Installation give me a error checking gitlab API. There is it: Running /usr/share/gitlab-shell/bin/check Check GitLab API access: FAILED. code: 401 gitlab-shell

Bug#894272: Gitlab: Bug#894272: Some problems fixed.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, After latest updates (Including gitlab-workhorse), login page are working now. I've recovered the old database and repositories now. Gitlab detected it and it's working. I have two problems now. First: Gitlab API is not working. Error 401:

Bug#894272: Another test

Hi, After another reinstall (uninstall & purge), with a clean database and repository, same error trying to login. All binaries from /usr/local/bin are deleted. I've tried to uninstall 10.5.6 and installing clean 10.5.5+dfsg-3. Same error. I don't know if this information can help you on this

Bug#893867: Problem continues with 10.5.5+dfsg-3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, After deleting gitlab installation (apt-get remove + dpkg --purge), I detect another error when installing. That's the same error reported on the first message for 9.5.4 version, but, on gitlab 10.5.5+dfsg-3 The message are: Precompiling

Bug#894072: gitlab: postinst fails with "/var/lib/gitlab/yarn/node_modules/.bin/yarn: not found"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 This are referenced at this bug: #893867 @Praveen: This bug appears from uploading from 9.5.4 installation. If you do a purge && reinstall, it solves the problem. https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at

Bug#893867: Solution not working for already installed 10.5.5 version

Hi, I've checked, this solution does not work if you have installed or half-installed already Gitlab 10.5.5. Deleting manually the file, these error does not appears. Regards, http://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres

Bug#894272: More info about the error

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, > You will need to start gitaly manually. We are trying to do that automatically, but facing some issues currently. How can I start gitaly? I0ve installed gitaly package (it isn't installed yet). Now I have this packages: kanade:/home# dpkg

Bug#894138: gitlab: 10.5.6 Problem compiling assets on post-install

Hi, Problem appears on first instance on 9.5.4 version. Same problem appears on 10.5.5+dfsg-3 After uninstall - purge - reinstall, same problem (with 10.5.5+dfsg-3) Updating 10.5.5 to 10.5.6, same problem too. Thanks, https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys

Bug#913581: Bug still present

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After a full reinstallation with gitlab 11.1.8, bug is still present. Here is the final install log with the error: Running rake checks... Check if Gitlab is configured correctly... Checking GitLab Shell ... GitLab Shell version >= 7.1.4 ? ... OK

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

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

Bug#915136: bug 915136 is forwarded to https://gitlab.com/gitlab-org/gitlab-ce/issues/55184

forwarded -1 https://gitlab.com/gitlab-org/gitlab-ce/issues/55184 thanks -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I've created a new issue on gitlab-ce for this bug. I've do some new checks and put on them new logs. @praveen,

Bug#915136: Push is also not working

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm testing about this bug if a new commit resolve the problem. But commit && push does not work on the affected repository (i haven't checked other repositories). The message on the GIT client are: BloudFire: maqui$ git push Enumerando objetos:

Bug#914159: More information

Control: tag -1 upstream -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've tested this problem one more time. Apparently, the problem are on gitlab itself. Maybe some change between gitlab 10 and 11. I've tested on gitlab 11.5.1 .deb package (from packages.gitlab.com), the problem are

Bug#914159: Bug reported to upstream

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've reported the bug to the upstream. The report are: https://gitlab.com/gitlab-org/gitlab-ce/issues/54615 https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres somos esclavos de

Bug#915136: Problem appears on all repositories

Control: severity -1 grave thanks. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I've done some more tests, the problem accesing repository on gitlab interface appears on all repositories. Here's the error message: Processing by ProjectsController#show as HTML Parameters:

Bug#915136: Follow-up

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, There's any new data about this bug? 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-

Bug#915136: Bug not resolved

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I've updated gitlab-shell to 8.3.3+dfsg-2. #914496 is resolved, but, #915136 is still present. I cannot view repositories from gitlab web interface. Error message in production.log is still the same. Thanks, https://maqui.darkbolt.net/

Bug#914159: Update of ruby-gpgme

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 @praveen I've done some research, and as I've see on gitlab upstream issues, upgrading ruby-gpgme is not a problem. Check this MR: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23491 But, I don't know if this is only working on gitlab

Bug#915136: Versions are ok

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Here's the version report: kanade:~# dpkg -l | grep gitlab ii gitlab 11.3.11+dfsg-1all git powered software platform to collaborate on code (non-omnibus) ii gitlab-common 11.3.11+dfsg-1all

Bug#915136: More info

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I've do some more tests on installation, here's the result: kanade:~# gitlab-rake gitlab:git:fsck Check if Gitlab is configured correctly... Performed integrity check for Project/Repo [...] Same message repeated for all repositories The

Bug#914159: Problem still present

The problem is still present on Gitlab 11.3.10 https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres somos esclavos de la historia

Bug#914159: Is not working

Hi, Thanks for the response. I've tested installing ruby-gpgme 2.0.13 as you suggested. Here's the relevant log: kanade:~# dpkg -i ruby-gpgme_2.0.13-1_amd64.deb dpkg: warning: downgrading ruby-gpgme from 2.0.16-1+b1 to 2.0.13-1 (Reading database ... 210214 files and directories currently

Bug#914159: Problem still present

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After upgrade to 11.2, gitlab is not giving a 500 internal server error when configuring GPG key. But, is only getting one email identity from the key, and it isn't the identity registered in the user. On gitlab 10.5, configuring GPG key gives all

Bug#914159: Follow up

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, There's any news about this? @praveen, will you report it to gitlab-ce, or you prefer to do it by myself? Thanks, https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres somos

Bug#913581: More information

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After some investigation, I've found this old bug report on gitlab: https://gitlab.com/gitlab-org/gitlab-ce/issues/25009 I've found the secret file on the gitlab-shell folder, who is: lrwxrwxrwx 1 gitlab gitlab36 Apr 26 2017

Bug#913581: Problem solved

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After information on the last bug report, I've tried to populate .gitlab_shell_secret file with a random key. After doing this and a gitlab restart, I've tried check and it's working. Doing suggested check on your last message (I'm sorry, when I've

Bug#917084: Possible fix?

Hi, Maybe on next release this bug have been resolved? I'm already waiting for testing if it's ok or not. If there's not any work on this release for this bug, or it's going to take "long time" the release, then I need to find a workaround for re-enabling gitlab (I have only SSL access to the

Bug#915136: Problem still present

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I've tried to upgrade to 11.4.9 and I have the same problem. Error 503 with same log when I try to access to any view of the repository. https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2

Bug#915136: Follow up

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, @praveen, how can I help you to find and/or resolve the bug? I cannot understand the problem itself, but I try to explain in some more detail how the bug have appeared. Installation: - The installation itself is a database migrated from

Bug#947754: Follow-up 947754

Package: gitlab Version: 12.6.7-1+fto10+1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Bug is still present (and checked) on 12.6.7. I haven't done any configuration changes. https://maqui.darkbolt.net/ Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2

Bug#947754: Follow-up 947754

Control: notfixed -1 12.6.2-2+fto10+1 Package: gitlab Version: 12.6.4-1+fto10+1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Bug is still present on 12.6.4 too. Same error message as 12.6.2 I've only tested it with Sonar oauth. https://maqui.darkbolt.net/ Linux registered user ~#363219

Bug#947754: doorkeeper update

Hi @praveen, Apparently, there's some work already done for updating gem: Update doorkeeper to 4.4 version: https://gitlab.com/gitlab-org/gitlab/merge_requests/20953 Update doorkeeper to 5 version: https://gitlab.com/gitlab-org/gitlab/merge_requests/21173 Maybe the problem are deleting the

Bug#436550: RFA: glipper - A clipboard manager for GNOME

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 You can orphan the package, or make a request for help. Neil Williams wrote: Package: wnpp Severity: normal X-Debbugs-CC: [EMAIL PROTECTED] Glipper is currently my package in Debian at 0.95.1-3 and that version is written in C and uses a

Bug#432182: Bug

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 3 months later and the bug still here. Now, found on 100.14.19. And, now I have broken the apt-get because nvidia-glx searches for nvidia-kernel 100.14.19, and my module version is 100.14.09 (functional). If correct these fail, the system uninstall

Bug#432182: System freezes with 2.6.21-6

. Er_Maqui. -- Linux registered user ~#363219 PGP keys avaiables at KeyServ. ID: 0x4233E9F2 Los hombres somos esclavos de la historia -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#432182: nvidia-kernel-source 100.14.11 bug

changing the package owner of this bug. Regards. Er_Maqui. - -- [EMAIL PROTECTED] || http://maqui.darkbolt.net Linux registered user number: #363219 PGP key avaliable at KeyServ. KeyID: 0x4233E9F2 - -- Los hombres somos esclavos de

Bug#433272: nvidia module fails to load on normal init

info contact me. Regards. Er_Maqui. - -- [EMAIL PROTECTED] || http://maqui.darkbolt.net Linux registered user number: #363219 PGP key avaliable at KeyServ. KeyID: 0x4233E9F2 - -- Los hombres somos esclavos de la historia

Bug#412217: New upsteam release

, and doesn't know if debian-games it's supporting now. If isn't correct, please orphan the package or send a call for help, we can have some mantainers to this package (the old mantainer, for example) who can verify the bug list and mantains them. Thanks. Er_Maqui. - -- [EMAIL PROTECTED] || http