On 3/23/2011 10:07 AM, Ben Pfaff wrote:
"John E. Malmberg"<wb8...@qsl.net> writes:
On 3/23/2011 8:24 AM, Ben Pfaff wrote:
"John E. Malmberg"<wb8...@qsl.net> writes:
The curl package is using Debian autoconf to generate its configure
script, and I was advised to report this issue here for tracking and
possible resolution by the curl team.
If you expect the curl team to track and resolve the problem,
then you should assign it to the curl package. I'm reassigning
this to "curl" (with this message).
The curl team advised me that the change is needed in the Autoconf
package, not curl, and that is why they requested that I submit a
Debian Autoconf bug so that you would be aware of this issue.
What curl team is this, by the way? I don't understand why the
Debian maintainers of curl would be considering OpenVMS issues.
http://curl.haxx.se/ Specifically Daniel Stenberg.
His logic was that curl was using the Debian autoconf, so that
notification of the issue should be reported to Debian autoconf as a
first step in providing feedback to the autoconf project, as curl is
probably going to continue to be maintained on Debian systems.
http://curl.haxx.se/mail/lib-2011-03/0070.html
By the way, Debian "stable" has version 2.67 of Autoconf, not
version 2.63.
The issue was first observed in Autoconf 2.63. The use of Autoconf
2.61 does not have this issue.
Does it occur with Autoconf 2.67?
I do not know. I can not do any additional checks until this evening.
The issue is present in the configure scripts currently being generated
and placed in the curl daily snapshots.
Regards,
-John
wb8...@qsl.net
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
