Bug#921050: marked as done (RM: ruby-protected-attributes/1.1.4-2)
Your message dated Tue, 5 Feb 2019 11:38:48 +0100
with message-id <071a0312-6464-2aed-c37e-c194c09fa8c7@debian.org>
and subject line Re: Bug#921050: RM: ruby-protected-attributes/1.1.4-2
has caused the Debian Bug report #921050,
regarding RM: ruby-protected-attributes/1.1.4-2
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.)
--
921050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921050
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
This package is not compatible with rails 5, but redmine 3 still depends
on it, so it cannot be removed from unstable till redmine is updated
(which is still in progress). Since this is blocking rails 5 migration
to testing, it should be removed from testing to facilitate this
migration.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ml_IN.UTF-8, LC_CTYPE=ml_IN.UTF-8 (charmap=UTF-8),
LANGUAGE=ml_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On 01/02/2019 05:31, Pirate Praveen wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: rm
>
> This package is not compatible with rails 5, but redmine 3 still depends
> on it, so it cannot be removed from unstable till redmine is updated
> (which is still in progress). Since this is blocking rails 5 migration
> to testing, it should be removed from testing to facilitate this
> migration.
Done.
Emilio
--- End Message ---
Reply to: