Your message dated Sun, 3 Jan 2016 09:32:41 -0800
with message-id <[email protected]>
and subject line Bug #135964: no longer clobbers anything
has caused the Debian Bug report #135964,
regarding autoconf clobbers autoconf files in /usr/bin
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
135964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=135964
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: autoconf
Version: 2.52-6
Severity: important

I just tried to use autoconf and it gave some error about not being able to 
find the autoconf2.52 file so I
investigated and found that the file didn't exist, although autoconf2.13 
existed. I reinstalled both autoconfs
and now have autoconf2.52 there but obviously something is flakey in the 
install process.

frankie




-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux frankie 2.4.18 #1 Tue Feb 26 18:50:41 GMT 2002 i586
Locale: LANG=C, LC_CTYPE=C

Versions of packages autoconf depends on:
ii  autoconf2.13                  2.13-39    automatic configure script builder
ii  debianutils                   1.15       Miscellaneous utilities specific t
ii  m4                            1.4-14     a macro processing language
ii  perl                          5.6.1-7    Larry Wall's Practical Extraction 



--- End Message ---
--- Begin Message ---
This bug, which no one ever reported reproducing, claimed that
autoconf2.13 clobbered files from autoconf.  Since then, autoconf2.13
has stopped doing anything tricky with diversions and its files are
entirely disjoint from those in the autoconf package (all the
autoconf2.13 files now contain "2.13" somewhere in the name) so it seems
very unlikely that it could still be true.  I'm closing the bug (with
this message).

If you still see a problem, please reopen the bug (with an explanation,
please).

Thanks,

Ben.

--- End Message ---

Reply via email to