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

[Hleb Valoshka]

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

[Hleb Valoshka]

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:

https://salsa.debian.org/ruby-team/unicorn/commit/38ed47ee28ae98caaa528c53fe3e81f7d734385d


Don't setup VERSION in d/rules (Closes: #918916)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/918916

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

[Hleb Valoshka]

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?

[Hleb Valoshka]

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 git, this patch was introduced when
ENV["VERSION"] was required to use the gemspec. Now as the upstream
gemspec provides the same it's not required.

The problem is not in Unicorn. The problem is in gem2deb which
generated incorrect unicorn-0.gemspec for the package.

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

[Hleb Valoshka]

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 updates.

Bug#870753: marked as pending

[Hleb Valoshka]

tag 870753 pending
thanks

Hello,

Bug #870753 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-buff-config.git/commit/?id=a36006f

---
commit 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.0.0-1) unstable; urgency=medium
+
+  * New upstream version (Closes: #870753).
+  * Drop not required anymore patches:
+- 001-Convert-specs-to-RSpec-3.3.2-syntax-with-Transpec.patch
+- relax-varia-model-dependency 
+  * Update dependencies.
+  * Bump standards version to 4.0.0 (no changes).
+  * Add myself to uploaders.
+
+ -- Hleb Valoshka <375...@gmail.com>  Thu, 10 Aug 2017 15:57:51 +0300
+
 ruby-buff-config (1.0.1-2) unstable; urgency=medium
 
   * Team upload.

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

[Hleb Valoshka]

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 dependency on faraday ~> 0.9.1
>
> Can we remove this package from debian?

Yes we can but a bit later when I prepare an updated berkshelf, I'm
working on its dependencies now.

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

[Hleb Valoshka]

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 features/commands/vendor.feature:24 # Scenario: vendoring a
>> Berksfile with a metadata demand

Lucas, what build software are you using for rebuild? I'm unable to
reproduce this failure in cowbuilder running on Jessie.

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

[Hleb Valoshka]

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#816882: ruby-websocket-driver: must depend on ruby-websocket-extensions

[Hleb Valoshka]

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 stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=be_BY.utf8, LC_CTYPE=be_BY.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Bug#786669: decreasing severity

[Hleb Valoshka]

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, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#786669: Info received (decreasing severity)

[Hleb Valoshka]

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'

[Hleb Valoshka]

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 /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  from /usr/lib/ruby/vendor_ruby/fog.rb:60:in `top (required)'
  from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  from /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  from -e:1:in `main'


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=be_BY.UTF-8, LC_CTYPE=be_BY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages ruby-fog depends on:
ii  ruby1:2.1.5+z
ii  ruby-fog-atmos  0.1.0-2
ii  ruby-fog-aws0.1.2-2
ii  ruby-fog-brightbox  0.7.1-2
ii  ruby-fog-core   1.30.0-2
ii  ruby-fog-ecloud 0.0.2-2
ii  ruby-fog-json   1.0.0-1
ii  ruby-fog-profitbricks   0.0.1-2
ii  ruby-fog-radosgw0.0.3-2
ii  ruby-fog-riakcs 0.1.0-2
ii  ruby-fog-sakuracloud0.1.1-3
ii  ruby-fog-serverlove 0.1.1-2
ii  ruby-fog-softlayer  0.3.17-1
ii  ruby-fog-storm-on-demand0.1.1-1
ii  ruby-fog-terremark  0.0.3-2
ii  ruby-fog-voxel  0.0.2-2
ii  ruby-inflecto   0.0.2-1
ii  ruby-ipaddress  0.8.0-3
ii  ruby-nokogiri   1.6.6.2+ds-2
ii  ruby2.1 [ruby-interpreter]  2.1.5-3

Versions of packages ruby-fog recommends:
ii  ruby-libvirt  0.5.1-3+b1

ruby-fog suggests no packages.

-- no debconf information


0005-disable-require-of-fog-vmfusion.patch
Description: /etc/magic

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

[Hleb Valoshka]

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 current version is built for kfreebsd-(amd64|i386).


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#570516: we encountered this bug

[Hleb Valoshka]

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 kernel 2.6.32, but (what is interesting) 
it was bootable with 2.2.26.


That raid has version 0.90 (I think it was made in Etch ages). Initramfs 
for kernel 2.6.26 was changed last time on Mar 12  2012, mdadm.conf was 
created 18 Nov 2008, and previous reboot was 6 Aug 2013.


Today's transition to Wheezy was successful.


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Hleb Valoshka]

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: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=be_BY.UTF-8, LC_CTYPE=be_BY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

javascript-common depends on no packages.

javascript-common recommends no packages.

Versions of packages javascript-common suggests:
ii  nginx-light [httpd]  1.4.1-3

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Hleb Valoshka]

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 exit correctly but stays in memory.

So it must depend on enchant.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=be_BY.UTF-8, LC_CTYPE=be_BY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages gummi depends on:
ii  libc6  2.13-35
ii  libcairo2  1.10.2-7
ii  libgdk-pixbuf2.0-0 2.26.1-1
ii  libglib2.0-0   2.32.3-1
ii  libgtk2.0-02.24.10-2
ii  libgtksourceview2.0-0  2.10.4-1
ii  libgtkspell0   2.0.16-1
ii  libpango1.0-0  1.30.0-1
ii  libpoppler-glib8   0.18.4-3
ii  zlib1g 1:1.2.7.dfsg-13

Versions of packages gummi recommends:
pn  texlive-extra-utils  none
ii  texlive-latex-base   2012.20120611-3
ii  texlive-xetex2012.20120611-3

gummi suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Hleb Valoshka]

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 debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

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

[Hleb Valoshka]

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
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=be_BY.UTF-8, LC_CTYPE=be_BY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages samba4-common-bin depends on:
ii  python2.7.2-10
ii  python-samba  4.0.0~alpha19+dfsg1-3
ii  samba-common  2:3.6.4-1

samba4-common-bin recommends no packages.

samba4-common-bin suggests no packages.

-- no debconf information
--- /usr/share/samba/setoption.py.orig	2012-04-16 18:01:34.0 +0300
+++ /usr/share/samba/setoption.py	2012-04-16 18:01:46.0 +0300
@@ -32,7 +32,7 @@
 outf.write(  %s = %s\n % (key, value))
 done = True
 inglobal = (m.groups(1)[0] in (global, globals))
-elif inglobal and re.match(r^(\s*) + key + r(\s*)=.*$):
+elif inglobal and re.match(r^(\s*) + key + r(\s*)=.*$, l):
 l = re.sub(r^(\s*) + key + r(\s*)=.*$,
 r\1 + key + r\2=\2 + value, l)
 done = True