=?iso-8859-15?q?/usr/bin/autoscan=3A_autoscan_Cannot_open_macros/aclocal-?= =?iso-8859-15?q?include=2Em4=3A_No=0D=0Asuch_file_or_directory?=

[Debian Bug Importer]

Automatically imported from Debian bug report #270521 http://bugs.debian.org/270521

[Ben Pfaff (blp-cs)]

severity 270521 normal
thanks

Bob Tanner <email address hidden> writes:

> Package: autoconf
> Version: 2.59-7
> Severity: grave
> File: /usr/bin/autoscan
> Justification: renders package unusable

Don't be ridiculous. This is nowhere near `grave' because
autoscan is not an important part of Autoconf. 99% of the time,
using Autoconf does not entail running autoscan. The autoscan
utility could be completely removed from Autoconf and it would
still be useful software.

I am downgrading the severity of this bug (with this mail).

> $ autoscan
> aclocal.m4:1432: /usr/bin/m4: Cannot open macros/aclocal-include.m4: No such
> file or directory
> autom4te: /usr/bin/m4 failed with exit status: 1
> autoscan: /usr/bin/autom4te failed with exit status: 1

I don't see these messages with the two random packages I tried
autoscan on just now (GNU doschk, GNU hello). (That's another
sign that this is not a grave bug, because it doesn't even render
autoscan unusable.) You'll have to tell me how to reproduce this
bug or I won't be able to do anything about it.
--
Aim to please, shoot to kill.

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #270521 http://bugs.debian.org/270521

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Tue, 07 Sep 2004 13:35:25 -0500
From: Bob Tanner <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: =?iso-8859-15?q?/usr/bin/autoscan=3A_autoscan_Cannot_open_macros/aclocal-?=
 =?iso-8859-15?q?include=2Em4=3A_No=0D=0Asuch_file_or_directory?=

Package: autoconf
Version: 2.59-7
Severity: grave
File: /usr/bin/autoscan
Justification: renders package unusable

$ autoscan
aclocal.m4:1432: /usr/bin/m4: Cannot open macros/aclocal-include.m4: No such
file or directory
autom4te: /usr/bin/m4 failed with exit status: 1
autoscan: /usr/bin/autom4te failed with exit status: 1

I see aclocal-include.m4 in the following packages:

gnome/gnome-common
devel/anjuta-common
gnome/glade-gnome

But autoconf doesn't suggest or recommend any of those packages.

It might be project specific, but the error is showing up under 4 different
source trees, so I'm opening the bug.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-1-686
Locale: LANG=C, LC_CTYPE=C

Versions of packages autoconf depends on:
ii debianutils 2.8.4 Miscellaneous utilities specific t
ii m4 1.4.1-1 a macro processing language
ii perl 5.8.4-2 Larry Wall's Practical Extraction

-- no debconf information

[Ben Pfaff (blp-cs)]

Bob Tanner <email address hidden> writes:

> Quoting Ben Pfaff (<email address hidden>):
>> > Justification: renders package unusable
>>
>> Don't be ridiculous. This is nowhere near `grave' because
>> autoscan is not an important part of Autoconf. 99% of the time,
>> using Autoconf does not entail running autoscan. The autoscan
>> utility could be completely removed from Autoconf and it would
>> still be useful software.
>
> Calm down. Learn to see a bug report from the user (me) stand-point.
>
> Leave negative comments for #debian.
>
> From my standpoint the package is -unusable-. It doesn't work.

Well, that's tough. You're not a normal user. Most users of
Autoconf use it for purposes different from autoscan. Most users
of Autoconf, I daresay, never use autoscan at all.

> As a new debian user (long time redhat user) reading the descriptions for
> Severity, grave match my problem exactly.

"unusable or mostly so" doesn't mean for *one* user. It means
for *most* users. If it was unusable for most users, I would
have heard about it before now.

>> I don't see these messages with the two random packages I tried
>> autoscan on just now (GNU doschk, GNU hello). (That's another
>> sign that this is not a grave bug, because it doesn't even render
>> autoscan unusable.) You'll have to tell me how to reproduce this
>> bug or I won't be able to do anything about it.
>
> Download:
> http://umn.dl.sourceforge.net/sourceforge/crossfire/crossfire-client-1.7.0.tar.gz
>
> cd crossfire-client-1.7.
> autoscan

The aclocal.m4 in that package was generated by the aclocal tool
that comes with automake, as are most aclocal.m4 files. Thus, if
there's any bug here, it has to be in automake, and I'm closing
this bug.
--
"I admire him, I frankly confess it; and when his time comes
 I shall buy a piece of the rope for a keepsake."
--Mark Twain

[Matt Zimmerman (mdz)]

Can't reproduce this on Warty, and autoscan isn't really critical functionality
for autoconf. Downgrading

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 07 Sep 2004 12:06:11 -0700
From: Ben Pfaff <email address hidden>
To: Bob Tanner <email address hidden>
Cc: <email address hidden>
CC: <email address hidden>
Subject: Re: Bug#270521: /usr/bin/autoscan: autoscan Cannot open
 macros/aclocal-include.m4: No such file or directory

severity 270521 normal
thanks

Bob Tanner <email address hidden> writes:

> Package: autoconf
> Version: 2.59-7
> Severity: grave
> File: /usr/bin/autoscan
> Justification: renders package unusable

Don't be ridiculous. This is nowhere near `grave' because
autoscan is not an important part of Autoconf. 99% of the time,
using Autoconf does not entail running autoscan. The autoscan
utility could be completely removed from Autoconf and it would
still be useful software.

I am downgrading the severity of this bug (with this mail).

> $ autoscan
> aclocal.m4:1432: /usr/bin/m4: Cannot open macros/aclocal-include.m4: No such
> file or directory
> autom4te: /usr/bin/m4 failed with exit status: 1
> autoscan: /usr/bin/autom4te failed with exit status: 1

I don't see these messages with the two random packages I tried
autoscan on just now (GNU doschk, GNU hello). (That's another
sign that this is not a grave bug, because it doesn't even render
autoscan unusable.) You'll have to tell me how to reproduce this
bug or I won't be able to do anything about it.
--
Aim to please, shoot to kill.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 07 Sep 2004 13:19:30 -0700
From: Ben Pfaff <email address hidden>
To: <email address hidden>
CC: <email address hidden>
Subject: Re: Bug#270521: /usr/bin/autoscan: autoscan Cannot open
 macros/aclocal-include.m4: No such file or directory

Bob Tanner <email address hidden> writes:

> Quoting Ben Pfaff (<email address hidden>):
>> > Justification: renders package unusable
>>
>> Don't be ridiculous. This is nowhere near `grave' because
>> autoscan is not an important part of Autoconf. 99% of the time,
>> using Autoconf does not entail running autoscan. The autoscan
>> utility could be completely removed from Autoconf and it would
>> still be useful software.
>
> Calm down. Learn to see a bug report from the user (me) stand-point.
>
> Leave negative comments for #debian.
>
> From my standpoint the package is -unusable-. It doesn't work.

Well, that's tough. You're not a normal user. Most users of
Autoconf use it for purposes different from autoscan. Most users
of Autoconf, I daresay, never use autoscan at all.

> As a new debian user (long time redhat user) reading the descriptions for
> Severity, grave match my problem exactly.

"unusable or mostly so" doesn't mean for *one* user. It means
for *most* users. If it was unusable for most users, I would
have heard about it before now.

>> I don't see these messages with the two random packages I tried
>> autoscan on just now (GNU doschk, GNU hello). (That's another
>> sign that this is not a grave bug, because it doesn't even render
>> autoscan unusable.) You'll have to tell me how to reproduce this
>> bug or I won't be able to do anything about it.
>
> Download:
> http://umn.dl.sourceforge.net/sourceforge/crossfire/crossfire-client-1.7.0.tar.gz
>
> cd crossfire-client-1.7.
> autoscan

The aclocal.m4 in that package was generated by the aclocal tool
that comes with automake, as are most aclocal.m4 files. Thus, if
there's any bug here, it has to be in automake, and I'm closing
this bug.
--
"I admire him, I frankly confess it; and when his time comes
 I shall buy a piece of the rope for a keepsake."
--Mark Twain

[Thom May (thombot)]

user getting *very* eager with reportbug