Bug#956205: gitlab: Problem installing 12.8.8-6

2020-04-08 Thread David L
Package: gitlab Version: 12.8.8-6+fto10+1 Severity: grave Justification: renders package unusable Hi, Gitlab 12.8.8 installation fails. Log: Bundle complete! 198 Gemfile dependencies, 362 gems now installed. Gems in the groups development and test were not installed. Use `bundle info

Bug#944596: gitlab: Upgrading to 12.2.9-1 fails

2019-11-15 Thread David L
Package: gitlab Version: 12.2.9-1+fto10+1 Followup-For: Bug #944596 More info about the bug: - Deleting file active_record_mysql_timestamp.rb, fails on active_record_mysql_timestamp.rb, because the same error, "undefined method mysql?". Error MSG: NoMethodError: undefined method

Bug#944596: gitlab: Upgrading to 12.2.9-1 fails

2019-11-15 Thread David L
Package: gitlab Version: 12.2.9-1+fto10+1 Followup-For: Bug #944596 Hi, I have exactly the same problem. Installation are originally on gitlab 8, until yesterday working without problem on 12.1 NoMethodError: undefined method `mysql?' for Gitlab::Database:Module

Bug#914496: gitlab-shell: Fail on gitlab-shell on git push

2018-11-23 Thread David L
Package: gitlab-shell Version: 8.3.3+dfsg-1 Severity: grave Justification: renders package unusable Doing a git push on a repository connected to gitlab, I receive this error: BloudFire:repository maqui$ git push origin /usr/share/gitlab-shell/bin/gitlab-shell:10:in `require_relative': cannot

Bug#898228: ruby-gitaly: Required dependency not specified on deb package

2018-05-08 Thread David L
Package: ruby-gitaly Version: 0.99.0+dfsg-1 Severity: grave Justification: renders package unusable Gitaly gem requires grpc gem in version 1.10 to work, but, deb package doesn't force installation of this package. In that case, ruby-gitaly is unusable. Error message: Bundler could not find

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

2018-03-26 Thread David L
Package: gitlab Version: 10.5.6+dfsg-1 Severity: grave Justification: renders package unusable Hi, Installing gitlab 10.5.6 do not work because a problem on sprockets. This error is also on old 10.5.5 and 9.5.4 versions. Thanks, Precompiling assets...

Bug#893867: gitlab: Dpkg fail to configure gitlab package. Problem with some Ruby Gems on 10.5

2018-03-23 Thread David L
Package: gitlab Version: 10.5.5+dfsg-2 Severity: grave Justification: renders package unusable Gitlab 10.5.5+dfsg-1 and 10.5.5+dfsg-2 fails to install. The machine have a gitlab 9.5.4 installed (since Experimental upload), upgrading to 10.5.5 on unstable. This is the error on installation:

Bug#763148: Prevent migration to jessie

2014-10-06 Thread David L. Craig
On 14Oct05:2254+0200, Andreas Barth wrote: Also, the re-evaluation happened. It however didn't had the outcome you wanted (basically because the web browser needs so many security updates which only could be done by backporting all of it that the embedded copy doesn't make any difference -

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-24 Thread David L. Craig
On 14Sep24:1951+0200, Michael Biebl wrote: Am 24.09.2014 um 18:45 schrieb Michael Biebl: Craig was so kind and provided me with access to the VM images. With that image I was able to reproduce the upgrade failure. I checked the systemd state before the upgrade and noticed that

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-24 Thread David L. Craig
On 14Sep24:1424-0400, David L. Craig wrote: Maybe I should be a full-time tester--I seem to be pretty good at it. I built another vm from the D-I beta, pointed sources.list at sid, and ran aptitude update, all as before. This time, though, I held all updates while installing dbus 1.8.8-1

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-23 Thread David L. Craig
On 14Sep23:0023+0200, Michael Biebl wrote: Yeah, this would be perfect By way of a feasibility test, I had virt-manager Shut Down == Save the a762146 vm at its ready for first login state and have put the tarball of the 124MB file it created in /var/lib/libvirt/qemu/save up at

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-23 Thread David L. Craig
On 14Sep23:0956-0400, David L. Craig wrote: By way of a feasibility test, I had virt-manager Shut Down == Save the a762146 vm at its ready for first login state and have put the tarball of the 124MB file it created in /var/lib/libvirt/qemu/save up at http://dlc.casita.net/~dlc/762146

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-23 Thread David L. Craig
Another datum: I decided to try switching back to systemd-sysv on my primary bare-metal Sid and the update was textbook: ii libpam-systemd:amd64 215-4 ii libsystemd-id128-0:amd64 215-4 ii libsystemd-journal0:amd64 215-4 ii libsystemd-login0:amd64 215-4 ii libsystemd-login0:i386

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-23 Thread David L. Craig
On 14Sep23:1719-0400, David L. Craig wrote: Another datum: I decided to try switching back to systemd-sysv on my primary bare-metal Sid and the update was textbook: ii libpam-systemd:amd64 215-4 ii libsystemd-id128-0:amd64 215-4 ii libsystemd-journal0:amd64 215-4 ii libsystemd

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-22 Thread David L. Craig
On 14Sep21:2011+0200, Michael Biebl wrote: What were the exact error messages you got? Please provide the dpkg log and the output from journalctl -alb I ran the test case again and obtained the same results from aptitude dist-upgrade and began receiving the kernel messages about journald as

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-22 Thread David L. Craig
On 14Sep23:0016+0200, Michael Biebl wrote: Am 22.09.2014 um 23:23 schrieb David L. Craig: On 14Sep21:2011+0200, Michael Biebl wrote: What were the exact error messages you got? Please provide the dpkg log and the output from journalctl -alb I ran the test case again and obtained

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-21 Thread David L. Craig
On 14Sep22:0005+0200, Michael Biebl wrote: Am 21.09.2014 um 23:28 schrieb David L. Craig: No, but, as the report mentioned, the vm failure was preceded by a similar result doing the daily update of the main non-vm Sid instance on the box, which is why I reproduced it using reproducible

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-18 Thread David L. Craig
Package: udev Version: 215-4 Severity: grave Installed Beta 1 D-I amd64 netinst without mirror or standard utils in preparation for dist-upgrade to Sid using aptitude with sources.list: deb ftp://debian.csail.mit.edu/debian/ sid main udev and aptitude reported replacing 208-6. udev fails first

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

2014-09-18 Thread David L. Craig
Correction: udev and systemd reported replacing 208-6. ^^^ not aptitude -- not cent from sell May the LORD God bless you exceedingly abundantly! Dave_Craig__ So the universe is not quite as you thought it was. You'd better rearrange your

Bug#684952: nvidia-glx: startx blackens screen, keyboard ineffective save for altSysReq

2012-08-15 Thread David L. Craig
On 12Aug15:1037+0200, Andreas Beckmann wrote: On 2012-08-15 09:48, David L. Craig wrote: I updated all the nvidia packages when I saw the new versions but the problem persists. I am including the most recent kern.log Kernel: Linux 3.2.0-3-rt-amd64 (SMP w/4 CPU cores; PREEMPT) Please

Bug#684952: nvidia-glx: startx blackens screen, keyboard ineffective save for altSysReq

2012-08-14 Thread David L. Craig
Package: nvidia-glx Version: 302.17-3 Severity: critical Justification: breaks the whole system I had installed Sid into an available partition and X was happy with nouveau. nvidia was functioning well under Linux Mint Xfce 13. After installing the nvidia packages and porting the Mint xorg.conf

Bug#326416: kimdaba: build-depends on LIBRARIES and Priority: required packages

2005-09-03 Thread David L. Moreno
a helpuful bug report. This bug will be fixed when the new upstream version is packaged and uploaded, I expect this process to last no more than five days. Thank you for reporting this bug, David L. Moreno On 9/3/05, Adeodato Simó [EMAIL PROTECTED] wrote: Package: kimdaba Version: 2.0-4