-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 11 Nov 2009 22:39:00 -0600
Source: libhaml-ruby
Binary: libhaml-ruby1.8 libhaml-ruby libhaml-ruby-doc haml-elisp
Architecture: source all
Version: 2.2.14-1
Distribution: unstable
Urgency: low
Maintainer: Gunnar Wolf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 24 Nov 2009 17:06:18 -0600
Source: libprawn-ruby
Binary: libprawn-ruby1.8 libprawn-ruby1.9 libprawn-ruby libprawn-ruby-common
Architecture: source all
Version: 0.6.3+dfsg-1
Distribution: unstable
Urgency: low
Maintainer:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 24 Nov 2009 20:38:15 -0600
Source: mongrel-cluster
Binary: mongrel-cluster
Architecture: source all
Version: 1.0.5-3
Distribution: unstable
Urgency: low
Maintainer: Jeremy Lainé jeremy.la...@m4x.org
Changed-By: Gunnar Wolf
There are disparities between your recently accepted upload and the
override file for the following file(s):
mongrel-cluster_1.0.5-3_all.deb: package says section is web, override says
httpd.
Please note that a list of new sections were recently added to the
archive: cli-mono, database, debug,
Your message dated Wed, 25 Nov 2009 10:30:54 +
with message-id e1ndf9c-0004la...@ries.debian.org
and subject line Bug#542457: fixed in libprawn-ruby 0.6.3+dfsg-1
has caused the Debian Bug report #542457,
regarding libprawn-ruby-common: long description no sentence
to be marked as done.
This
Your message dated Wed, 25 Nov 2009 10:30:33 +
with message-id e1ndf8r-0004ak...@ries.debian.org
and subject line Bug#557190: fixed in libhaml-ruby 2.2.14-1
has caused the Debian Bug report #557190,
regarding [haml-elisp] should depend on ruby-elisp
to be marked as done.
This means that you
Your message dated Wed, 25 Nov 2009 10:35:05 +
with message-id e1ndfdf-00068b...@ries.debian.org
and subject line Bug#550539: fixed in mongrel-cluster 1.0.5-3
has caused the Debian Bug report #550539,
regarding mongrel-cluster: Incorrect init.d script dependencies and runlevels
to be marked as
tags 557023 = pending
thanks
Hmm... Looking more closely to your submitted patches: The second part
makes sense (using an empty string when a nil is presented), although
its correctness might be stylistic (i.e. some authors prefer to raise
an exception on an anomalous condition, which you can
Processing commands for cont...@bugs.debian.org:
tags 557023 = pending
Bug #557023 [libbarby-ruby1.8] Barby::Code128: private method split called for
nil
Removed tag(s) upstream and patch.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system
Processing commands for cont...@bugs.debian.org:
tags 557023 = upstream, patch
Bug #557023 [libbarby-ruby1.8] Barby::Code128: private method split called for
nil
Added tag(s) upstream and patch; removed tag(s) pending.
thanks
Stopping processing here.
Please contact me if you need assistance.
10 matches
Mail list logo