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
On 08/04/2012 01:15 PM, Peter Samuelson wrote:
[Neil Roeth]
diff -u aplus-fsf-4.22.1/config/config.sub aplus-fsf-4.22.1/config/config.sub
--- aplus-fsf-4.22.1/config/config.sub
+++ aplus-fsf-4.22.1/config/config.sub
@@ -4,7 +4,7 @@
# 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009
[Neil Roeth]
> diff -u aplus-fsf-4.22.1/config/config.sub aplus-fsf-4.22.1/config/config.sub
> --- aplus-fsf-4.22.1/config/config.sub
> +++ aplus-fsf-4.22.1/config/config.sub
> @@ -4,7 +4,7 @@
> # 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010,
> # 2011, 2012 Free Software
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
re
4 matches
Mail list logo