[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#807762: marked as done (RM: ruby-rash/0.4.0-1)

Your message dated Mon, 14 Dec 2015 18:29:25 +0100
with message-id <566EFC75.8090407@debian.org>
and subject line Re: Bug#807762: RM: ruby-rash/0.4.0-1
has caused the Debian Bug report #807762,
regarding RM: ruby-rash/0.4.0-1
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 owner@bugs.debian.org
immediately.)


-- 
807762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807762
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: rm

ruby-hash invades the namespace of ruby-hashie, and at this point there
is no solution at the upstream level.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792548

Depends on how the situation is fixed upstream, ruby-rash could come
back. But there is no sign of that happening any time soon, so I am not
requesting a complete removal from the archive.

So, for now please remove ruby-rash from testing so that ruby-hashie can
move on.

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

Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Antonio Terceiro <terceiro@debian.org>

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
On 12/12/15 19:04, Antonio Terceiro wrote:
> On Sat, Dec 12, 2015 at 04:44:43PM +0100, Emilio Pozuelo Monfort wrote:
>> On 12/12/15 15:31, Antonio Terceiro wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian.org@packages.debian.org
>>> Usertags: rm
>>>
>>> ruby-hash invades the namespace of ruby-hashie, and at this point there
>>> is no solution at the upstream level.
>>>
>>> See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792548
>>>
>>> Depends on how the situation is fixed upstream, ruby-rash could come
>>> back. But there is no sign of that happening any time soon, so I am not
>>> requesting a complete removal from the archive.
>>>
>>> So, for now please remove ruby-rash from testing so that ruby-hashie can
>>> move on.
>>
>> That's not going to help until the RC bug is fixed:
>>
>> ruby-hashie (2.0.5-1 to 3.4.2-2)
>>     Maintainer: Debian Ruby Extras Maintainers
>>     128 days old (needed 5 days)
>>     ruby-hashie (source, amd64, i386, arm64, armel, armhf, mips, mipsel,
>> powerpc, ppc64el, s390x) has new bugs!
>>     Updating ruby-hashie introduces new bugs: #796514
>>     Not considered
> 
> Yes, I know. I was working on a fix for that very bug and stopped to
> make this request. I have just uploaded it.

Hint added.

Cheers,
Emilio

--- End Message ---
Reply to: