Bug#503591: Bug #503591: Please don't include yet another copy of tzdata in the archive

On Sat, Jul 07, 2012 at 02:13:16PM -0700, shawn wrote: this has languished an entire release and I believe it at least needs a justification on why it has not been fixed yet. Bugfix was uploaded to pkg-ruby-extras repo so I hope you'll help to test it. -- To UNSUBSCRIBE, email to

Bug#685188: gummi doesn't work if enchant isn't installed

Package: gummi Version: 0.6.3-1+b1 Severity: serious Justification: Policy 3.5 Dear Maintainer, When package enchant isn't installed gummi refuses to start with message ``Failed to execute child process enchant-lsmod (No such file or directory)''. And when you press ``Ok'' button it doesn't

Bug#669015: samba4-common-bin: Can't upgrade samba4 because of broken /usr/share/samba/setoption.py

Package: samba4-common-bin Version: 4.0.0~alpha19+dfsg1-3 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, there is an error in /usr/share/samba/setoption.py line 35: re.match has only 1 argument instead of 2. -- System Information: Debian Release: wheezy/sid

Bug#570516: we encountered this bug

Just my 2 cents. Yesterday we were upgrading our old Debian server form Lenny to Squeeze and encountered this bug. We were warned by mdadm post-install scripts that UUID was changed, so we upgraded our mdadm.conf, but forgot to re-run update-initramfs :), so the system was unbootable with

Bug#718288: javascript-common: postinstall script tries to remove unexistant /etc/apache2/conf.d

Package: javascript-common Version: 10 Severity: grave Justification: renders package unusable Dear Maintainer, javascript-common.postinst tries to remove directory /etc/apache2/conf.d which doesn't exist on my system so package configuration fails. -- System Information: Debian Release:

Bug#734451: fuse4bsd-dkms: package does not ship sources inside

Package: fuse4bsd-dkms Version: 0.3.9~pre1.20080208-8 Severity: grave Justification: renders package unusable Dear Maintainer, fuse4bsd-dkms from sid does not have archive with sources for kernel module inside. Version from stable has them, also 0.3.9~pre1.20080208-4 is built for all, while

Bug#786669: decreasing severity

control: command -1 tags moreinfo unreproducible control: command -1 severity normal Hi, during preparation of nmu of 0.16.0-3 I ran testsuite about ten times and I was unable to reproduce your failure. I think it's related to jenkins environment, so I decrease its severity. -- To UNSUBSCRIBE,

Bug#786669: Info received (decreasing severity)

control: tags -1 moreinfo unreproducible control: severity -1 normal -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#786617: ruby-fog: should not require 'fog/vmfusion'

Package: ruby-fog Version: 1.28.0-2 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, ruby -e require 'fog' /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- fog/vmfusion (LoadError) from

Bug#816882: ruby-websocket-driver: must depend on ruby-websocket-extensions

Package: ruby-websocket-driver Version: 0.6.3-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, ruby-websocket-driver has missing dependency on ruby-websocket-extensions, so it's impossible to use it. -- System Information: Debian Release: 8.3 APT prefers

Bug#836735: ruby-aruba: uninitialized constant Aruba::CommandMonitor::Utils

Package: ruby-aruba Version: 0.14.2-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, Upstream bug https://github.com/cucumber/aruba/issues/346 still affects debian package. This makes ruby-aruba unusable.

Bug#850994: [DRE-maint] Bug#850994: berkshelf: FTBFS: ERROR: Test "ruby2.3" failed.

Hi Lucas. On 1/11/17, Lucas Nussbaum wrote: >> (::) failed steps (::) >> >> cache_manager not running (Berkshelf::API::NotStartedError) >> features/commands/vendor.feature:3:in `* the Berkshelf API server's cache >> is empty' >> >> Failing Scenarios: >> cucumber

Bug#870753: marked as pending

a36006f0cf24ab3a546de0cf2b063efaabaae29e Author: Hleb Valoshka <375...@gmail.com> Date: Thu Aug 10 15:47:32 2017 +0300 Release 2.0.0-1 diff --git a/debian/changelog b/debian/changelog index b15836d..d231248 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,15 @@ +ruby-buff-config (2

Bug#869919: [DRE-maint] Bug#869919: remove ruby-berkshelf-api-client?

On 7/27/17, Pirate Praveen wrote: > Upstream readme has this "This gem has been fully deprecated, and its > API has been moved inside the berkshelf gem itself." > > I bumped into this package when trying to update ruby-faraday as its > gemspec declares a tight

Bug#869919: [DRE-maint] Bug#869919: remove ruby-berkshelf-api-client?

On 1/21/18, Balasankar "Balu" C wrote: > Any update on this? Was the berkshelf update done? Can we remove this > package? Unfortunately, I had no enough time to prepare a new berkshelf, but you can request removal of ruby-berkshelf-api-client if it prevents other packages

Bug#918916: Unicorn not reporting proper version for gemfile?

On 1/12/19, Dominik George wrote: >>The problem is not in Unicorn. The problem is in gem2deb which >>generated incorrect unicorn-0.gemspec for the package. > > OK... But, why was it fixed when I rebuilt with the patch? Different gem2deb versions? Have you tried to rebuild it without that patch?

Bug#918916: Unicorn not reporting proper version for gemfile?

On 1/10/19, Eric Wong wrote: >> +- s.version = (ENV['VERSION'] || '5.4.1').dup >> ++ s.version = '5.4.1' > > Why is ignoring ENV['VERSION'] necessary for the Debian build? > I can probably remove that check if desired from the upstream > package before the 5.5.0 release. I've checked debian's

Bug#918916: [DRE-maint] Bug#918916: Unicorn not reporting proper version for gemfile?

On 1/13/19, Julian Calaby wrote: > As a workaround, changing _both_ versions in the shipped gemspec and the > version in the filename from 0 to 5.4.1 fixes packages which depend on > this, e.g. gitlab. Thanks for the hint. Actually the problem was in d/rules file.

Bug#918916: Bug #918916 in unicorn marked as pending

Control: tag -1 pending Hello, Bug #918916 in unicorn reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: