Your message dated Sat, 16 Mar 2013 16:32:39 +0100
with message-id <20130316153239.gp5...@radis.cristau.org>
and subject line Re: Bug#680335: unblock: scim/1.4.14-2
has caused the Debian Bug report #680335,
regarding unblock: scim/1.4.14-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 ow...@bugs.debian.org
immediately.)
--
680335: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
Hi release managers (and scim and scim-anthy maintainers),
I've checked RC bug in scim-anthy in Wheezy (Bug#687401).
The changes in newest scim-anthy 1.2.7-5 is here.
> - scim (>= 1.4.6), libscim-dev (>= 1.4.6), autotools-dev, pkg-config,
> + scim (>= 1.4.6), libscim-dev (>= 1.4.14-2), autotools-dev, pkg-config,
The reason is scim-anthy was unblocked (Bug#685036) and migrated
to testing but scim (1.4.14-2) still stops in unstable.
So, release managers, can you consider to unblock scim to fix RC as well?
--
Regards,
Hideki Yamane henrich @ debian.or.jp/org
http://wiki.debian.org/HidekiYamane
--- End Message ---
--- Begin Message ---
On Thu, Sep 20, 2012 at 22:55:28 +0900, Rolf Leggewie wrote:
> On 20.09.2012 14:52, Hideki Yamane wrote:
> > The reason is scim-anthy was unblocked (Bug#685036) and migrated to
> > testing but scim (1.4.14-2) still stops in unstable. So, release
> > managers, can you consider to unblock scim to fix RC as well?
>
> Yamane-San,
>
> thank you for your report. Hello from Tokyo, how are you? Your
> analysis is spot on, scim-anthy fails to build from scratch due to a
> newer scim version not having migrated yet from unstable to testing.
> I'll answer here hoping to save the release team a bit of time.
>
> Scim already has an unblock request open for a while (bug 680335 which
> also has some background information) . The problem was externally
> induced by a concurrent upload of a build dependency just before the
> freeze, leading to an FTBFS for the version we uploaded just before the
> deadline. The fix for this was simple enough yet it went in after the
> freeze, meaning that the release team now needs to review not only this
> small fix but the changes we uploaded just before the freeze as well
> :-( For this they need more time, but I can assure you that they are
> aware of the situation.
>
We're not going to unblock a new upstream release of scim, I'm afraid.
If there are RC issues in wheezy then they'll need package removals or
targetted fixes.
Cheers,
Julien
signature.asc
Description: Digital signature
--- End Message ---
