Is there something else I need to do to get aplus-fsf back into
testing? I uploaded the fixed version 16 days ago, and AFAIK did
everything in the "Rules to get your changes into Wheezy" section of the
Wheezy freeze policy, but haven't seen any response or other change. If
the reason is that people are busy, that's fine; I just want to be sure
the next step is not something I need to do.
Thanks.
On 08/04/2012 11:48 AM, Neil Roeth wrote:
Hi, d-r.
Several packages built from aplus-fsf source (aplus-fsf,
aplus-fsf-doc, aplus-fsf-el, aplus-fsf-dev, xfronts-kapl) were removed
from TESTING because there was a dependency on xemacs21-nomule, which
in turn was removed from TESTING because of bug 670292. Most of
aplus-fsf does not require xemacs21-nomule, just the aplus-fsf-el
package. It appears to me that xemacs21 will not likely be restored,
so in order to continue to make the rest of aplus-fsf available for
users, I removed the functionality that depends on xemacs21-nomule
from aplus-fsf, removed xemacs21-nomule from the Depends of the
package, and uploaded that. I restricted the changes to that plus the
addition of a NEWS file that says the functionality has been removed.
Attached is the debdiff output for the source.
Since the bug 670292 is not in aplus-fsf itself but in the
xemacs21-nomule package, I did not close it via the changelog. I did
file an unblock bug for aplus-fsf; it is 683831.
Thanks.
--
Neil Roeth
--
Neil Roeth
