portsnap didn't properly update www/neon

[Daniel Morante]

I have a system that started as FreeBSD 5.x. Throughout the years it has been updated and upgraded. Today's it's currently at 9.3-RELEASE.

Recently:

"The port www/neon29 was renamed to www/neon and updated to version 0.30.1"

Back in 2008:





 :/usr/ports/www/neon # ls -larths
total 78
 2 drwxr-xr-x     2 root  wheel   512B Apr 28  2008 files
 2 -rw-r--r--     1 root  wheel   821B Jan 22  2014 pkg-descr
 6 -rw-r--r--     1 root  wheel     6k Dec 24 01:03 pkg-plist
 2 -rw-r--r--     1 root  wheel   130B Dec 24 01:03 distinfo
 2 -rw-r--r--     1 root  wheel   1.8k Dec 24 01:03 Makefile
62 drwxr-xr-x  2332 root  wheel    61k Feb 22 12:32 ..
 2 drwxr-xr-x     3 root  wheel   512B Feb 22 13:37 .

 ls -larths files/
total 8
2 -rw-r--r--  1 root  wheel   503B Mar 16  2007 patch-ltmain.sh
2 -rw-r--r--  1 root  wheel   683B Mar 16  2007 patch-Makefile.in
2 drwxr-xr-x  2 root  wheel   512B Apr 28  2008 .
2 drwxr-xr-x  3 root  wheel   512B Feb 22 13:37 ..



===>  Applying FreeBSD patches for neon-0.30.1
1 out of 1 hunks failed--saving rejects to ltmain.sh.rej
=> Patch patch-ltmain.sh failed to apply cleanly.
=> Patch(es) patch-Makefile.in applied cleanly.
*** [do-patch] Error code 1

Stop in /usr/ports/www/neon.
*** [install] Error code 1

Stop in /usr/ports/www/neon.

To fix, I delete the 'files' directory.

"Rename www/neon to www/neon26 to make the integration of www/neon28 possible" Not sure what happened between no and then, but yesterday portsnap failed to properly update the port skeleton under /usr/ports/www/neon. There were still some left over files from the last time the port was named neon. Which of course would cause the port install to fail since those patches are outdated:

smime.p7s
Description: S/MIME Cryptographic Signature