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
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 (>=
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
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,
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.
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
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
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
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
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
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
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
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
13 matches
Mail list logo
