Your message dated Wed, 25 Jul 2012 16:56:22 +0200
with message-id <[email protected]>
and subject line 1.4.1 uploaded in April 2012
has caused the Debian Bug report #668498,
regarding ruby-rack: Upgrade to 1.4.1 to fix a session bug
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
668498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668498
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ruby-rack
Version: 1.4.0-1
Severity: wishlist


Version 1.4.0 holds a bug with sessions 
(https://github.com/rack/rack/issues/299)
 fixed in v1.4.1

Could you please update the release.

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ruby-rack depends on:
ii  ruby                         4.8         Transitional package for ruby1.8
ii  ruby1.8 [ruby-interpreter]   1.8.7.352-2 Interpreter of object-oriented scr
ii  ruby1.9.1 [ruby-interpreter] 1.9.3.0-2   Interpreter of object-oriented scr

ruby-rack recommends no packages.

ruby-rack suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Hi!

According to snapshot.debian.org [1] and to a message from ftp
masters [2], the first upload of ruby-rack 1.4.1 happened on April, 23rd
2012.

  1: http://snapshot.debian.org/package/ruby-rack/1.4.1-1/
  2: 
http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2012-April/010566.html

I am thus closing this bug report.

Cheers,

Cédric

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to