bug#11524: ping on automake bug#11524

Hi Stefano, Am 21.11.2012 um 11:11 schrieb Stefano Lattarini : > Reference: > > > Any news on this bug? Can it still be reproduced with Automake 1.12.5? > Can it be reproduced with the development version of Automake from the > 'master' branch

bug#12184: Testsuite on Solaris 10 Sparc

> Any news on this? How is the testsuite of the latest Automake behaving > on your system? I'm in the process of culling old bug reports from the > Automake bug tracker, so, since most of the failures seen in this > thread were spurious or related to setup problems, I'll close this > report in

bug#10227: Python installation fails for Python 3

On 21 November 2012 13:41, Stefano Lattarini wrote: > tags 10227 + moreinfo > thanks > > Hi Roumen, Reuben. > > I'm going through old open bugs, and I've noticed this one. Is the > problem still present, after the recent updates to the python support? > (They should be already merged in the maint

bug#10227: Python installation fails for Python 3

tags 10227 + moreinfo thanks Hi Roumen, Reuben. On 12/06/2011 12:16 AM, Roumen Petrov wrote: > Reuben Thomas wrote: >> The code currently used to get the python package directory is wrong >> for Python 3: >> > from distutils import sysconfig; print > (sysconfig.get_python_lib(0,0,'/us

bug#8847: [PATCH 0/8] tests: support for PEP-3147, and testsuite fixes

On 11/19/2012 11:12 PM, Stefano Lattarini wrote: > Original patch: > > > Yaakov Selkowitz (1): > python: improve support for modern python (CPython 3.2 and PyPy) > > Stefano Lattarini (7): > news: document fix for bug#

bug#12184: Testsuite on Solaris 10 Sparc

Reference: Hi Dennis. Any news on this? How is the testsuite of the latest Automake behaving on your system? I'm in the process of culling old bug reports from the Automake bug tracker, so, since most of the failures seen in this thread were

bug#11532: automake-1.12.0b self test failures: t/remake8b & t/remake9c

Reference: On 07/23/2012 05:37 PM, Stefano Lattarini wrote: > On 07/23/2012 05:26 PM, Simon Josefsson wrote: >> Stefano Lattarini writes: >> >>> severity 11532 minor >>> tags 11532 + moreinfo >>> thanks >>> >>> Reference: >>>

bug#12009: Autoconf testsuite failure (likely spurious) with the development version of Automake

tags 12009 notabug close 12009 thanks On 07/21/2012 06:05 PM, Stefano Lattarini wrote: > AUtoconf test 035 "autom4te preselections" is failing when run with > developement versions of aclocal and automake installed in $PATH: > > [SNIP] > Nothing serious: we had merely forgotten to update the list

bug#11833: Testsuite summary for GNU Automake 1.12.1 # FAIL: 2

Reference: On 07/06/2012 11:01 PM, Stefano Lattarini wrote: > tags 11833 + moreinfo > severity 11833 minor > thanks > > Hi Dennis, sorry for the delay. > > On 07/01/2012 08:33 PM, Dennis Clarke wrote: >> >> on debian 6.0.5 amd64 : >> >> . >>

bug#7862: Cygwin test failure of parallel-am.test

[+cc Peter Rosin] Reference: It has been a long time since this report, and regular testing by Peter hasn't (AFAIK) tickled similar failures in any modern Automake+Cygwin combination. So I'm closing this report, to avoid keeping the bug tracker

bug#11401: Automake, Libtool and AM_PROG_AR (was: Re: bug#11401: automake-1.12 (incorrectly?) complains about missing AM_PROG_AR)

References: On 05/11/2012 01:37 PM, Stefano Lattarini wrote: > On 05/04/2012 09:19 PM, Mike Frysinger wrote: >> On Friday 04 May 2012 03:20:10 Peter Rosin wrote: >>> On 2012-05-0

bug#12177: mdate-sh scriptversion=2009-04-28.21; # UTC

Reference: On 08/12/2012 10:56 AM, Stefano Lattarini wrote: > Hi Doug, thanks for the report. > > On 08/11/2012 02:59 AM, doug wrote: >> This file is found in make-3.82 and autotools packages. >> > Which Automake version? > >> It runs forever

bug#11306: Automake 1.11d on MacOS X

Reference: On 04/21/2012 08:52 PM, Stefano Lattarini wrote: > Hi Bruno, thanks for the report. > > On 04/21/2012 08:13 PM, Bruno Haible wrote: >> >> Apparently, the "automake-1.11d ..." command [run with the AUTOMAKE_JOBS >> environment variabl

bug#11618: Automake 1.12.0b test release

tags 11618 + wontfix severity 11618 minor close 11618 stop Reference: Several months have passed since this report, the thread has seen no activity (my bad, mostly), and the Automake testsuite has undergone several changes and bugfixes in the m

bug#11524: ping on automake bug#11524

Reference: On 09/12/2012 09:33 AM, Stefano Lattarini wrote: > On 09/12/2012 09:12 AM, Dagobert Michelsen wrote: >> Hi Stefano, >> > Hi Dagobert, thanks for not giving up on this. > >> Am 11.09.2012 um 17:29 schrieb Dagobert Michelsen : >>> Am 1

bug#11204: automake-1.11.4 test failures, powerpc-darwin8

Reference: On 04/13/2012 10:45 AM, Stefano Lattarini wrote: > On 04/13/2012 10:33 AM, David Fang wrote: >> >> Stefano Lattarini wrote: >> >>> What happens if you use GNU info instead? Do the testsuite failures >>> persist? >> >> Already using G

bug#12064: distclean failure with Automake 1.12.2

Reference: Since I've seen no further reports of similar problems, and since we have concluded the issue in question wasn't due to an Automake bug, but rather to a legitimate-but-slightly-backward-incompatible change in Automake's behaviour (cha

bug#7922: 1.11 doesn't add sources with nonstandard suffixes when making a binary

close 7922 stop Reference: On 02/15/2011 03:32 PM, Юрий Пухальский wrote: > Good day, Ralf! > > Yes, adding .pc.c rule seems to fix the issue - now .pc sources are > added to the TAGS. But as this rule is unused, it's superfluous... > Going thr