possible problem receiving with ctm on current

[Montgomery-Smith, Stephen]

On 02/04/2018 04:41 PM, Julian H. Stacey wrote:
> Hi ctm-users at freebsd.org
> A current box was some weeks old, so I just did a make world & now see:
> 
> On current box:
>   uname -a
>   FreeBSD lapr.js.berklix.net 12.0-CURRENT FreeBSD 12.0-CURRENT #0:
>   Sun Feb  4 03:03:45 CET 2018
>   jhs at lapr.js.berklix.net:/data/release/s4/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64
>   
>   md5 /pub/FreeBSD/development/CTM/svn-cur/svn-cur.06383.xz
>   MD5 (/pub/FreeBSD/development/CTM/svn-cur/svn-cur.06383.xz) = a3ea38b3d22451ac0653214db5279784
> 
>   ctm /pub/FreeBSD/development/CTM/svn-cur/svn-cur.06383.xz
>   /pub/FreeBSD/development/CTM/svn-cur/svn-cur.06383.xz Fatal error: Probably not a CTM-patch at all.
>   ctm: exit(65)
> 
>   gzip -d !$
>   gzip -d /pub/FreeBSD/development/CTM/svn-cur/svn-cur.06383.xz
> 
>   ctm /pub/FreeBSD/development/CTM/svn-cur/svn-cur.06383
>   /pub/FreeBSD/development/CTM/svn-cur/svn-cur.06383 Fatal error: Expected CTM keyword.
>   Got [CTMSV]
>   ctm: exit(65)
> 
> & yet svn-cur.06383.xz applied on my older 9.2-RELEASE where I'm up to date
>         /pub/FreeBSD/development/CTM/svn-cur            svn-cur.06386.xz
>         /pub/FreeBSD/development/FreeBSD-SVN            svn-cur 6386 
>         /pri/FreeBSD/development/FreeBSD-SVN            svn-cur 6386 
>         /usr/svn                                        svn-cur 6386 
> 
> my local svn-cur.06383.xz (delivered from freebsd.org mail list)
> has same md5 as that delivered by Stephen's rsync to
> ftp://ctm.berklix.org/pub/FreeBSD/development/CTM/svn-cur/svn-cur.06383.xz
> MD5 (/pub/FreeBSD/development/CTM/svn-cur/svn-cur.06383.xz) = a3ea38b3d22451ac0653214db5279784
> 
> Anyone else receiving ctm on current see this problem ?
> 
> Cheers,
> Julian
> 

Did you remember to apply the patch to ctm when you rebuilt everything?

ftp://ctm.berklix.org/pub/FreeBSD/development/CTM/svn-cur/patch-for-ctm-v09