Bugzilla Bug 80425

Having following installed
*  sys-devel/autoconf :
        [  I] 2.13 (2.1)
        [  I] 2.59-r5 (2.5)
        [   ] 2.59-r6 (2.5)
*  sys-devel/autoconf-wrapper :
        [  I] 2 (0)
and emerging new autoconf (=autoconf-2.59-r6), the symlinks in /usr/bin/ e.g. autoconf pointing to 
../lib/misc/ac-wrapper.sh are disappearing

Reproducible: Always
Steps to Reproduce:
Starting with above,
1. emerge =autoconf-2.59-r6
I get 
*  sys-devel/autoconf :
        [  I] 2.13 (2.1)
        [   ] 2.59-r5 (2.5)
        [  I] 2.59-r6 (2.5)
But only /usr/bin/autoconf-2.59 exists, not /usr/bin/autoconf
Actual Results:  
No /usr/bin/autoconf

Expected Results:  
/usr/bin/autoconf: symbolic link to `../lib/misc/ac-wrapper.sh'


Since this end January marking stable for -r6, we got bug-reports of packages, which failed to 
emerge. Notably Bug #80344 and Bug #78814

Created an attachment (id=50197) [details]
autoconf-2.59-r6.ebuild.diff

Patch which solves this problem

Created an attachment (id=50198) [details]
Output of emerge info

autoconf doesnt create the symlinks, autoconf-wrapper does

Sorry, autoconf-2.59-r5 indeed creates this symlinks, 
but autoconf-2.59-r6 does not. Check the following:
(Assuming autoconf-wrapper 2 is already installed)
1. emerge =autoconf-2.59-r5
2. emerge =autoconf-2.59-r6
So when doing this update, removing autoconf.2.59-r5 deletes these files,
and emerging then autoconf-2.59-r6 does not recreate them.

If it's intentional, that only autconf-wrapper has to create /usr/bin/autoconf, then for a transitional period autoconf-wrapper should be re-emerged.
.

i know what packages create what symlinks, i maintain them (read the ChangeLog)

figure out why the symlinks disappeared on your system if you like and propose a fix for that; symlink creation is not going back into autoconf-2.59-r6

Created an attachment (id=50253) [details]
Shell script demonstrating this bug

Can someone verify/falsify that? Thanks

Mike, it might be possible that if he merged the wrapper before -r5, that
upgrading to -r6 might have removed the symlinks ...

How about a new autoconf-wrapper revision that -r6 (or maybe a new -r7) depends
on?  This should fix any such nitty bugs ...

Fine, that's it.

Suggestions:
1. -r5 should be removed from portage, otherwise 2.
2. if -r5 can't be removed from portage, then make a 
    a) dummy autoconf-wrapper-0 which just doesn't install that symlinks and
        RDEPEND="<sys-devel/autoconf-2.59-r6
    b) -r5 then DEPEND on =autoconf-wrapper-0
    c) make -r6 depend on >=autoconf-wrapper-2
    This works here
3. For the old cases, just updating to -r6, but having emerged then old revisions of -r5
    in pkg_postinst() test /usr/bin/automake and if missing then ewarn that he should
    (re)emerge autoconf-wrapper.

Created an attachment (id=50254) [details]
Concatened diff's for that suggestions

Apropos, we have same problem with exactly (and only) automake-1.8.5-r1
Somebody unmerging that, /usr/bin/automake disappears.

Thanks for silently nuking automake-1.8.5-r1
Thanks for silently nuking autoconf-2.59-r5
Thanks for autoconf-wrapper-2-r1
Thanks for automake-wrapper-1-r1
Hopeful, this works for anybody

Today sync:

checking whether autoconf is installed... no
configure: error: Autoconf 2.58 or better is required.
    Please make sure it is installed and in your PATH.

!!! Please attach the config.log to your bug report:
!!! /var/tmp/portage/automake-1.8.5-r3/work/automake-1.8.5/config.log

!!! ERROR: sys-devel/automake-1.8.5-r3 failed.
!!! Function econf, Line 485, Exitcode 0

Solution is to emerge -u autoconf-wrapper
to 2-r1, which creates symlinks. But can't autoconf-2.59-r6 depends on autoconf-wrapper-2-r1? wrapper depends on autoconf.