[DRE-maint] Bug#894248: ruby-sprockets: warning during update of any ruby package

2018-03-27 Thread Jörg-Volker Peetz 
Package: ruby-sprockets
Version: 3.7.0-1
Severity: minor

Dear Debian Ruby Extras Maintainers,

having installed redmine and its ruby dependency packages, these
warnings appear

/usr/lib/ruby/vendor_ruby/sprockets/digest_utils.rb:47: warning: constant
::Fixnum is deprecated
/usr/lib/ruby/vendor_ruby/sprockets/digest_utils.rb:51: warning: constant
::Bignum is deprecated
/usr/lib/ruby/vendor_ruby/sprockets/processor_utils.rb:110: warning: constant
::Fixnum is deprecated
/usr/lib/ruby/vendor_ruby/sprockets/processor_utils.rb:111: warning: constant
::Bignum is deprecated

when updating any of the ruby packages.
Would it help to use the newer upstream version of ruby-sprockets?

Regards,
Jörg.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.10 (SMP w/8 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ruby-sprockets depends on:
ii  ruby 1:2.5.1
ii  ruby-concurrent  1.0.5-1
ii  ruby-hike1.2.1-3
ii  ruby-multi-json  1.12.1-1
ii  ruby-rack1.6.4-4
ii  ruby-tilt2.0.1-2

ruby-sprockets recommends no packages.

ruby-sprockets suggests no packages.

-- no debconf information

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#829171: ruby-nokogiri: breaks redmine

2016-07-01 Thread Jörg-Volker Peetz 
Package: ruby-nokogiri
Version: 1.6.8-1
Severity: normal

Hi Antonio,

upgrading to this version doesn't work and throws the following error
message:

.
.
Processing triggers for redmine (3.2.3-1) ...
Bundler could not find compatible versions for gem "pkg-config":
  In Gemfile:
nokogiri (>= 1.6.7.2) was resolved to 1.6.8, which depends on
  pkg-config (~> 1.1.7)

Could not find gem 'pkg-config (~> 1.1.7)', which is required by gem 'nokogiri
(>= 1.6.7.2)', in any of the sources.
dpkg: error processing package redmine (--unpack):
 subprocess installed post-installation script returned error exit status 6
Processing triggers for mime-support (3.60) ...
Errors were encountered while processing:
 redmine
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up ruby-nokogiri (1.6.8-1) ...
Setting up redmine (3.2.3-1) ...
Bundler could not find compatible versions for gem "pkg-config":
  In Gemfile:
nokogiri (>= 1.6.7.2) was resolved to 1.6.8, which depends on
  pkg-config (~> 1.1.7)

Could not find gem 'pkg-config (~> 1.1.7)', which is required by gem 'nokogiri
(>= 1.6.7.2)', in any of the sources.
dpkg: error processing package redmine (--configure):
 subprocess installed post-installation script returned error exit status 6
.
.

The version of redmine is 3.2.3-1 and of ruby-bundler 1.12.5-1.
I downgraded to the previous version 1.6.7.2-3 with

  dpkg -i ruby-nokogiri_1.6.7.2-3_amd64.deb
  dpkg --configure redmine

Should I have waited for some other package to be upgraded?

Best regards,
jvp.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.3 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ruby-nokogiri depends on:
ii  libc6   2.22-12
ii  libgmp102:6.1.1+dfsg-1
ii  libruby2.3  2.3.1-3
ii  libxml2 2.9.3+dfsg1-1.2
ii  libxslt1.1  1.1.28-4
ii  ruby1:2.3.0+4

ruby-nokogiri recommends no packages.

ruby-nokogiri suggests no packages.

-- no debconf information

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#792361: redmine: dpkg --configure broken when installing ruby packages

2015-07-14 Thread Jörg-Volker Peetz 
Antonio Terceiro wrote on 07/14/2015 15:03:
 Control: reassign -1 ruby-jquery-rails
 Control: notfound -1 3.1.2-6
 Control: found -1 4.0.4-1
 Control: ruby-jquery-rails: new version breaks redmine dependencies
 Control: affects -1 + redmine
 
 On Tue, Jul 14, 2015 at 10:04:19AM +0200, Jörg-Volker Peetz wrote:
 Package: redmine
 Version: 3.0~20140825-8
 Severity: serious

 Dear Antonio, dear maintainers,

 thanks for the new redmine version. Installing it on my stretch/sid
 Debian worked without problem.

 After that I tried to update the ruby packages ruby-jquery-rails,
 ruby-kgio, and ruby-raindrops.
 This does not work. The following is an extract from the aptitude
 output:

 ...
 Setting up ruby-jquery-rails (4.0.4-1) ...
 Setting up ruby-kgio (2.9.3-1) ...
 Setting up ruby-raindrops (0.14.0-1) ...
 Processing triggers for redmine (3.0~20140825-8) ...
 Could not find gem 'jquery-rails (~ 3.1.1) ruby' in any of the gem sources
 listed in your Gemfile or available on this machine.
 dpkg: error processing package redmine (--configure):
  subprocess installed post-installation script returned error exit status 7
 Errors were encountered while processing:
  redmine
 E: Sub-process /usr/bin/dpkg returned an error code (1)
 Failed to perform requested operation on package.  Trying to recover:
 Setting up redmine (3.0~20140825-8) ...
 Could not find gem 'jquery-rails (~ 3.1.1) ruby' in any of the gem sources
 listed in your Gemfile or available on this machine.
 dpkg: error processing package redmine (--configure):
  subprocess installed post-installation script returned error exit status 7
 Errors were encountered while processing:
  redmine
 
 This has nothing to do with redmine, but with the fact that
 ruby-jquery-rails was upgraded to a version that breaks the redmine
 dependency checking.
 
Yes indeed, going back to version 3.1.2-2 of ruby-jquery-rails fixes the problem
on my stretch/sid system.
Thanks, Antonio.

 To the Ruby team: seriously, we need to find a way to check these things
 *before* uploading. It's not like we can't move forward, but this type
 of thing needs to be at least coordinated!
 
-- 
Regards,
Jörg.

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#783696: ruby-redcarpet: breaks unicorn serving redmine

2015-04-29 Thread Jörg-Volker Peetz 
Package: ruby-redcarpet
Version: 3.2.0-2
Severity: important

Dear Maintainer(s),

this new version breaks my redmine (3.0~20140825-5) on unicorn (4.8.3-1)
configuration on a mixed testing unstable system. Unicorn doesn't start.
The following appears in the error logs of unicorn:

I, [2015-04-28T09:48:09.23 #1027]  INFO -- : Refreshing Gem list
/usr/lib/ruby/vendor_ruby/bundler/resolver.rb:357:in `resolve': Could not find
gem 'redcarpet (~ 3.1.2) ruby' in the gems available on this machine.
(Bundler::GemNotFound)
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:164:in `start'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:129:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:193:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:132:in `specs'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:177:in `specs_for'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:166:in 
`requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:18:in 
`requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:13:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler.rb:121:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:17: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 /usr/share/redmine/config/boot.rb:4: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 /usr/share/redmine/config/application.rb:1: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 /usr/share/redmine/config/environment.rb:2: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 config.ru:4:in `block in main'
from /usr/lib/ruby/vendor_ruby/rack/builder.rb:55:in `instance_eval'
from /usr/lib/ruby/vendor_ruby/rack/builder.rb:55:in `initialize'
from config.ru:1:in `new'
from config.ru:1:in `main'
from /usr/lib/ruby/vendor_ruby/unicorn.rb:48:in `eval'
from /usr/lib/ruby/vendor_ruby/unicorn.rb:48:in `block in builder'
from /usr/lib/ruby/vendor_ruby/unicorn/http_server.rb:764:in `call'
from /usr/lib/ruby/vendor_ruby/unicorn/http_server.rb:764:in 
`build_app!'
from /usr/lib/ruby/vendor_ruby/unicorn/http_server.rb:137:in `start'
from /usr/bin/unicorn:126:in `main'

Or is it a problem in unicorn?
--
Regards,
jvp.


-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable'), (5, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages ruby-redcarpet depends on:
ii  libc6   2.19-18
ii  libgmp102:6.0.0+dfsg-6
ii  libruby2.1  2.1.5-3
ii  ruby1:2.1.5
ii  ruby2.1 [ruby-interpreter]  2.1.5-3

-- no debconf information

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#653350: problem solved with rubygems 1.8.15-1

2012-02-11 Thread Jörg-Volker Peetz 
Package: redmine
Version: 1.3.0+dfsg1-2

With rubygems 1.8.15-1 from unstable redmine is (re-)installable/upgradable
again. I tried a reinstall with redmine 1.3.0+dfsg1-1 as well as an upgrade to
version 1.3.0+dfsg1-2. Both worked despite the messages about
Gem::SourceIndex#add_spec is deprecated. The bug can be closed.

Many thanks.
-- 
Best regards,
Jörg-Volker.


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

Kernel: Linux 3.2.0 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages redmine depends on:
ii  dbconfig-common1.8.47+nmu1
ii  debconf [debconf-2.0]  1.5.41
ii  rails  2.3.14.1
ii  redmine-sqlite 1.3.0+dfsg1-2
ii  ruby-coderay   0.9.8-1
ii  ruby-net-ldap  0.0.4-1
ii  ruby-rails-2.3 2.3.14-2
ii  ruby1.81.8.7.352-2

redmine recommends no packages.

Versions of packages redmine suggests:
pn  libopenid-ruby  none
pn  libsvn-ruby none
pn  ruby-rmagicknone

Version of package rubygems:
ii  rubygems   1.8.15-1

-- debconf information:
  redmine/instances/default/passwords-do-not-match:
  redmine/instances/default/remote/newhost:
* redmine/instances/default/db/basepath: /var/lib/redmine/default/db
  redmine/instances/default/pgsql/changeconf: false
  redmine/instances/default/missing-db-package-error: abort
  redmine/default-language: ${defaultLocale}
  redmine/instances/default/pgsql/no-empty-passwords:
  redmine/instances/default/pgsql/method: unix socket
* redmine/instances/default/database-type: sqlite3
  redmine/instances/default/pgsql/manualconf:
  redmine/instances/default/pgsql/authmethod-admin: ident
  redmine/instances/default/pgsql/admin-user: postgres
  redmine/missing-redmine-package:
  redmine/instances/default/pgsql/authmethod-user: password
  redmine/instances/default/dbconfig-reinstall: false
  redmine/instances/default/db/app-user: redmine
* redmine/instances/default/default-language: en
  redmine/notify-migration:
  redmine/old-instances:
  redmine/instances/default/upgrade-error: abort
* redmine/instances/default/db/dbname: redmine.sqlite
  redmine/instances/default/purge: false
* redmine/current-instances: default
  redmine/instances/default/remote/host:
  redmine/instances/default/dbconfig-upgrade: true
  redmine/instances/default/internal/reconfiguring: false
  redmine/instances/default/upgrade-backup: true
  redmine/instances/default/install-error: abort
  redmine/instances/default/mysql/admin-user: root
  redmine/instances/default/mysql/method: unix socket
  redmine/instances/default/internal/skip-preseed: false
  redmine/instances/default/remove-error: abort
  redmine/instances/default/dbconfig-remove:
  redmine/instances/default/remote/port:
* redmine/instances/default/dbconfig-install: true




___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#653350: redmine: redmine won't install with rubygems 1.8.12-1

2012-01-22 Thread Jörg-Volker Peetz 
Jérémy Lal wrote, on 12/29/11 14:04:
 On 27/12/2011 12:25, Jörg-Volker Peetz wrote:
 Package: redmine
 ...
 uninitialized constant Gem::SyckDefaultKey
 ...
 
 gem2deb's fix is to call Gem.load_yaml before require 'yaml' is called 
 elsewhere.
 
 Using that fix on redmine works too, in /usr/share/redmine/config/boot.rb :
 
   class VendorBoot  Boot
 def load_initializer
   require 'rubygems'   # Syck-ness, see
   Gem.load_yaml# http://bugs.debian.org/653350
   require #{RAILS_ROOT}/vendor/rails/railties/lib/initializer
   Rails::Initializer.run(:install_gem_spec_stubs)
   Rails::GemDependency.add_frozen_gem_path
 end
   end
 
 Is it really up to other apps to work around that rubygems bug ?

I also think: no.
I saw that you reassigned this bug to rubygems 1.8.12-1.
To me it seems to be a bug in package ruby-rails-2.3 2.3.14-2 since the file
/usr/share/redmine/config/../vendor/rails/railties/lib/rails/gem_dependency.rb
which is /usr/lib/ruby/vendor_ruby/rails/gem_dependency.rb and which still uses
Gem.source_index belongs to package ruby-rails-2.3.

Best regards,
Jörg-Volker.

 
 Jérémy.
 
 





___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#651503: rake: dependency on virtual package rdoc pulls in transitional package ruby

2011-12-09 Thread Jörg-Volker Peetz 
Package: rake
Version: 0.9.2.2-2
Severity: minor

Dear Maintainer,

the new dependency on virtual package rdoc pulls in transitional package ruby.
I'm not sure if this package is to blame. But to me it seems the package rdoc
and the versioned packages rdoc1.8 and rdoc1.9.1 are virtual packages provided
by the ruby* packages. Therefore, the dependency on ruby | ruby-interpreter
should be sufficient.
-- 
Best regards,
Jörg-Volker.


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

Kernel: Linux 3.1.3 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages rake depends on:
ii  ruby [rdoc] 4.8
ii  ruby1.8 [ruby-interpreter]  1.8.7.352-2
ii  rubygems1.8.10-1

Versions of packages rake recommends:
ii  zip  3.0-4

rake suggests no packages.

-- no debconf information



___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#645139: redmine: fails to install also in testing; downgrade to previous version 1.1.3-4 also fails

2011-10-25 Thread Jörg-Volker Peetz 
Package: redmine
Version: 1.2.1+dfsg2-2


Dear maintainer,

redmine 1.2.1+dfsg2-2 entered testing and also fails to install here. Even a
downgrade to the previous version of redmine fails with the same symptoms:

# dpkg -r redmine-sqlite redmine
# dpkg -i redmine_1.1.3-4_all.deb redmine-sqlite_1.1.3-4_all.deb
...
Missing these required gems:
  rubytree  = 0

You're running:
  ruby 1.8.7.352 at /usr/bin/ruby1.8
  rubygems 1.8.10 at /var/lib/gems/1.8, /root/.gem/ruby/1.8

Run `rake gems:install` to install the missing gems.
Error when running rake db:migrate, check database configuration.
/var/lib/dpkg/info/redmine.postinst: 271: exit: Illegal number: -1
dpkg: error processing redmine (--install):
 subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
 redmine


Also, the recommended

# (cd /usr/share/redmine; rake gems:install)

doesn't repair the system.

-- 
Best regards,
Jörg-Volker.


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

Kernel: Linux 3.0.7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages redmine depends on:
ii  dbconfig-common1.8.47
ii  debconf [debconf-2.0]  1.5.40
ii  rails  2.3.14.1
ii  redmine-sqlite 1.2.1+dfsg2-2
ii  ruby-coderay   0.9.8-1
ii  ruby-net-ldap  0.0.4-1
ii  ruby-rails-2.3 2.3.14-2
ii  ruby1.81.8.7.352-2

redmine recommends no packages.

Versions of packages redmine suggests:
pn  libopenid-ruby  none
pn  libsvn-ruby none
pn  ruby-rmagicknone

-- debconf information:
  redmine/instances/default/passwords-do-not-match:
  redmine/instances/default/remote/newhost:
* redmine/instances/default/db/basepath: /var/lib/redmine/default/db
  redmine/instances/default/pgsql/changeconf: false
* redmine/instances/default/missing-db-package-error: ignore
  redmine/default-language: ${defaultLocale}
  redmine/instances/default/pgsql/no-empty-passwords:
  redmine/instances/default/pgsql/method: unix socket
* redmine/instances/default/database-type: sqlite3
  redmine/instances/default/pgsql/manualconf:
  redmine/instances/default/pgsql/authmethod-admin: ident
  redmine/instances/default/pgsql/admin-user: postgres
  redmine/missing-redmine-package:
  redmine/instances/default/pgsql/authmethod-user: password
  redmine/instances/default/dbconfig-reinstall: false
  redmine/instances/default/db/app-user: redmine
* redmine/instances/default/default-language: en
  redmine/notify-migration:
  redmine/old-instances:
  redmine/instances/default/upgrade-error: abort
* redmine/instances/default/db/dbname: redmine.sqlite
  redmine/instances/default/purge: false
* redmine/current-instances: default
  redmine/instances/default/remote/host:
  redmine/instances/default/dbconfig-upgrade: true
  redmine/instances/default/internal/reconfiguring: false
  redmine/instances/default/upgrade-backup: true
* redmine/instances/default/install-error: ignore
  redmine/instances/default/mysql/admin-user: root
  redmine/instances/default/mysql/method: unix socket
  redmine/instances/default/internal/skip-preseed: false
  redmine/instances/default/remove-error: abort
* redmine/instances/default/dbconfig-remove:
  redmine/instances/default/remote/port:
* redmine/instances/default/dbconfig-install: true




___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#645139: redmine: fails to install also in testing; downgrade to previous version 1.1.3-4 also fails

2011-10-25 Thread Jörg-Volker Peetz 
Jérémy Lal wrote, on 10/23/11 12:55:
 It seems .specification file is not forward compatible with rubygems 1.8.10 :
   cd /usr/share/redmine/vendor/gems
   rm rubytree-0.5.2/.specification
   rake gems:refresh_specs
 does the job.
 
 I'll update .specification in package today.
 
 Jérémy.
 

Dear Jérémy,

yes indeed, after following the procedure you propose

# dpkg --configure redmine

completes the update to redmine version 1.2.1+dfsg2-2.

Thank you very much.
-- 
Best regards,
Jörg-Volker.






___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Dubious subscription notification

2011-08-20 Thread Jörg-Volker Peetz 
Dear maintainers(s),

recently, I receive a lot of e-mails with subject beginning with [DRE-maint] .
The two last ones about subscription confirmation and a web subscription for
coderay package, which I definitly not sent.
Could you please give me some information how to unsubscribe from all these
mailing lists?
-- 
Best regards,
Jörg-Volker.

___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#631058: Bug#631058: doesn't work with new /run directory

2011-07-12 Thread Jörg-Volker Peetz 
Since the fcgi sockets don't need to remember anything during reboot, I think
/run is just the right place for them (/tmp would also be o.k., I think, see,
e.g., /tmp/.X11-unix/X0).
By now, I'm circumventing the problem by using the directory /run/lighttpd as
the location for the fcgi sockets since lighttpd creates this directory on start
with owner:group www-data:www-data. I use the following in
/etc/lighttpd/lighttpd.conf:

socket = /run/redmine/sockets/ + var.X_DEBIAN_SITEID + 
/fcgi.socket,

This works for me (with lighttpd 1.4.28-5 on amd64).
But I don't have any idea how to create the sockets with the WEBrick web server.
-- 
Best regards,
Jörg-Volker.




___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#631058: Bug#631058: doesn't work with new /run directory

2011-07-12 Thread Jörg-Volker Peetz 
Sorry for the confusion, I have to correct my last e-mail in one point:

Jörg-Volker Peetz wrote, on 07/02/11 20:19:
 Since the fcgi sockets don't need to remember anything during reboot, I think
 /run is just the right place for them (/tmp would also be o.k., I think, see,
 e.g., /tmp/.X11-unix/X0).
 By now, I'm circumventing the problem by using the directory /run/lighttpd as
 the location for the fcgi sockets since lighttpd creates this directory on 
 start
 with owner:group www-data:www-data. I use the following in
 /etc/lighttpd/lighttpd.conf:
 
   socket = /run/redmine/sockets/ + var.X_DEBIAN_SITEID + 
 /fcgi.socket,

this should read:

socket = /run/lighttpd/redmine- + var.X_DEBIAN_SITEID + 
-fcgi.socket,

 
 This works for me (with lighttpd 1.4.28-5 on amd64).
 But I don't have any idea how to create the sockets with the WEBrick web 
 server.
-- 
Best regards,
Jörg-Volker.




___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

[DRE-maint] Bug#631058: redmine doesn't work with new /run directory

2011-07-01 Thread Jörg-Volker Peetz 
Package: redmine
Version: 1.1.3-1
Severity: normal

User: rle...@debian.org
Usertags: run-transition

I added the above two tags due to the proposal in
http://wiki.debian.org/ReleaseGoals/RunDirectory#Bug_reports


With the new /run directory all contents of /var/run (linked to /run) gets lost
with a reboot. For redmine this means, that the directory
/var/run/redmine/sockets/${lInstance}, created once during installation in the
postinst script, is no longer available after the first reboot after 
installation.
Due to the missing directory on my system the daemon lighttpd can't start any 
more.

If the directory /var/run/redmine/sockets/${lInstance} does not exist should it
instead be created by the ruby file /usr/share/redmine/public/dispatch.fcgi?

Best regards,
Jörg-Volker.


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

Kernel: Linux 2.6.39.1 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages redmine depends on:
ii  dbconfig-common  1.8.47  common framework for packaging dat
ii  debconf [debconf-2.0]1.5.39  Debian configuration management sy
ii  libactionmailer-ruby 2.3.11-0.1  Framework for generation of custom
ii  libactionpack-ruby   2.3.11-0.1  Controller and View framework used
ii  libactiveresource-ruby   2.3.11-0.1  Connects objects and REST web serv
ii  libactivesupport-ruby2.3.11-0.1  utility classes and extensions (Ru
ii  libjs-scriptaculous  1.9.0-2 JavaScript library for dynamic web
ii  rails2.3.11-0.1  MVC ruby based framework geared fo
ii  redmine-sqlite   1.1.3-1 metapackage providing sqlite depen
ii  ruby 4.8 Transitional package for ruby1.8
ii  ruby1.8 [ruby]   1.8.7.334-4 Interpreter of object-oriented scr

redmine recommends no packages.

Versions of packages redmine suggests:
pn  libopenid-rubynone (no description available)
pn  librmagick-ruby   none (no description available)
pn  libsvn-ruby   none (no description available)

-- debconf information:
  redmine/instances/default/passwords-do-not-match:
  redmine/instances/default/remote/newhost:
* redmine/instances/default/db/basepath: /var/lib/redmine/default/db
  redmine/instances/default/pgsql/changeconf: false
  redmine/instances/default/missing-db-package-error: abort
  redmine/default-language: ${defaultLocale}
  redmine/instances/default/pgsql/no-empty-passwords:
  redmine/instances/default/pgsql/method: unix socket
* redmine/instances/default/database-type: sqlite3
  redmine/instances/default/pgsql/manualconf:
  redmine/instances/default/pgsql/authmethod-admin: ident
  redmine/instances/default/pgsql/admin-user: postgres
  redmine/missing-redmine-package:
  redmine/instances/default/pgsql/authmethod-user: password
  redmine/instances/default/dbconfig-reinstall: false
  redmine/instances/default/db/app-user: redmine
* redmine/instances/default/default-language: en
  redmine/notify-migration:
  redmine/old-instances:
  redmine/instances/default/upgrade-error: abort
* redmine/instances/default/db/dbname: redmine.sqlite
  redmine/instances/default/purge: false
* redmine/current-instances: default
  redmine/instances/default/remote/host:
  redmine/instances/default/dbconfig-upgrade: true
  redmine/instances/default/internal/reconfiguring: false
  redmine/instances/default/upgrade-backup: true
  redmine/instances/default/install-error: abort
  redmine/instances/default/mysql/admin-user: root
  redmine/instances/default/mysql/method: unix socket
  redmine/instances/default/internal/skip-preseed: false
  redmine/instances/default/remove-error: abort
  redmine/instances/default/dbconfig-remove:
  redmine/instances/default/remote/port:
* redmine/instances/default/dbconfig-install: true




___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers