Package: sup-mail
Version: 0.20.0-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I searched in sup via '\' all messages for the paragraph sign '§'.
and got the message:
Problem: Redwood::Index::ParseError!
* What exactly did you do (or not do) that was
Hi,
as there is no progress here, I assume a typo in the Depends:-line.
So please reupload a corrected version.
Thanks!
Thorsten
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
On 6/22/15, Dmitry Smirnov only...@debian.org wrote:
Perhaps it might be better to make sure that daemon is not enabled after
first install of the package?
It sounds reasonably.
I realised that dh_installinit --no-start still enables automatic start
of
daemon so I've added workaround to
FYI: The status of the ruby-http-accept-language source package
in Debian's testing distribution has changed.
Previous version: 2.0.5-2
Current version: 2.0.5-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
FYI: The status of the ruby-get-process-mem source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.2.0-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times
Processing commands for cont...@bugs.debian.org:
fixed 764664 asciidoctor/1.5.2-2
Bug #764664 [asciidoctor] asciidoctor: new upstream version
Marked as fixed in versions asciidoctor/1.5.2-2.
This issue is fixed with the upload of version 1.5.2-2 into unstable.
Unknown command or malformed
Your message dated Mon, 22 Jun 2015 18:20:11 +0200
with message-id
CANvh_fbg=RNFAiCg2o28J1RThQFYwP=wsdW__=4h1gfChY=t...@mail.gmail.com
and subject line fixed 764664 asciidoctor/1.5.2-2
has caused the Debian Bug report #764664,
regarding asciidoctor: new upstream version
to be marked as done.
Hi Hleb,
I marked your package for accept, but why did you do that lintian override?
As you didn't close an ITP bug, the lintian warning is rather correct.
Thorsten
___
Pkg-ruby-extras-maintainers mailing list
ruby-retryable_2.0.1-1_amd64.changes uploaded successfully to localhost
along with the files:
ruby-retryable_2.0.1-1.dsc
ruby-retryable_2.0.1.orig.tar.gz
ruby-retryable_2.0.1-1.debian.tar.xz
ruby-retryable_2.0.1-1_all.deb
Greetings,
Your Debian queue daemon (running on host
On Mon, 22 Jun 2015 19:45:23 Hleb Valoshka wrote:
It seems that --update-rcd-params=disable (or remove) is the solution.
I tried that but it does not work and produces error on installation of the
package...
I don't want to lose transparent upgrade feature and it's not possible
with default
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 29 May 2015 12:47:44 +0300
Source: ruby-cleanroom
Binary: ruby-cleanroom
Architecture: source all
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Package: cucumber
Version: 2.0.0-1
Severity: grave
Hi,
after upgrading my sid system today, running cucumber with a sample
.feature file as an argument fails:
$ cucumber features/build.feature
/usr/bin/cucumber:4:in `load': cannot load such file --
/usr/spec/simplecov_setup.rb (LoadError)
Mapping sid to unstable.
binary:ruby-retryable is NEW.
source:ruby-retryable is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be
ruby-sidetiq 0.6.3-4 is marked for autoremoval from testing on 2015-07-11
It (build-)depends on packages with these RC bugs:
786669: ruby-celluloid: tests sometimes fail, causing ftbfs sometimes
___
Pkg-ruby-extras-maintainers mailing list
cucumber_2.0.0-2_amd64.changes uploaded successfully to localhost
along with the files:
cucumber_2.0.0-2.dsc
cucumber_2.0.0-2.debian.tar.xz
cucumber_2.0.0-2_all.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
Processing control commands:
tag -1 pending
Bug #789585 [cucumber] cucumber: `load': cannot load such file --
/usr/spec/simplecov_setup.rb (LoadError)
Added tag(s) pending.
--
789585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789585
Debian Bug Tracking System
Contact
Control: tag -1 pending
On Mon, Jun 22, 2015 at 12:46:12PM +0200, intrig...@debian.org wrote:
after upgrading my sid system today, running cucumber with a sample
.feature file as an argument fails:
$ cucumber features/build.feature
/usr/bin/cucumber:4:in `load': cannot load such file --
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 22 Jun 2015 14:15:05 +0200
Source: cucumber
Binary: cucumber
Architecture: source all
Version: 2.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 22 Jun 2015 17:59:50 +0530
Source: ruby-redis-rack
Binary: ruby-redis-rack
Architecture: source all
Version: 1.5.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
ruby-redis-rack_1.5.0-6_i386.changes uploaded successfully to localhost
along with the files:
ruby-redis-rack_1.5.0-6.dsc
ruby-redis-rack_1.5.0-6.debian.tar.xz
ruby-redis-rack_1.5.0-6_all.deb
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
Your message dated Mon, 22 Jun 2015 12:33:51 +
with message-id e1z70v9-n1...@franck.debian.org
and subject line Bug#789585: fixed in cucumber 2.0.0-2
has caused the Debian Bug report #789585,
regarding cucumber: `load': cannot load such file --
/usr/spec/simplecov_setup.rb (LoadError)
to
21 matches
Mail list logo
