From owner-ctm-users@freebsd.org Sun Nov 6 23:55:27 2016 Return-Path: Delivered-To: ctm-users@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7239EC34568 for ; Sun, 6 Nov 2016 23:55:27 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from um-nip4-missouri-out.um.umsystem.edu (um-nip4-missouri-out.um.umsystem.edu [198.209.49.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "um-tip1.um.umsystem.edu", Issuer "InCommon RSA Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FD233D5 for ; Sun, 6 Nov 2016 23:55:26 +0000 (UTC) (envelope-from stephen@missouri.edu) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2E0CQDOwR9Y/9KeoM9dGwEBAQMBAQEJA?= =?us-ascii?q?QEBgy4BAQEBAR9YKlIHAaQwlloBIIYDAoIJQxABAgEBAQEBAQEDXx0Lg0ssLj0?= =?us-ascii?q?BAQSBCQIBCBgWARcyJQIEDQYCAQGIVLMHiBEBBoMvASSIO4JYgSKDDxZIAYUXB?= =?us-ascii?q?YhCh0+ENoVgAYY0hgOUHI0qhAY1IHqDMRyBXXKFQw0XgQoBgQsBAQE?= X-IPAS-Result: =?us-ascii?q?A2E0CQDOwR9Y/9KeoM9dGwEBAQMBAQEJAQEBgy4BAQEBAR9?= =?us-ascii?q?YKlIHAaQwlloBIIYDAoIJQxABAgEBAQEBAQEDXx0Lg0ssLj0BAQSBCQIBCBgWA?= =?us-ascii?q?RcyJQIEDQYCAQGIVLMHiBEBBoMvASSIO4JYgSKDDxZIAYUXBYhCh0+ENoVgAYY?= =?us-ascii?q?0hgOUHI0qhAY1IHqDMRyBXXKFQw0XgQoBgQsBAQE?= Received: from um-ncas5.um.umsystem.edu ([207.160.158.210]) by um-nip4-exch-relay.um.umsystem.edu with ESMTP; 06 Nov 2016 17:54:16 -0600 Received: from UM-MBX-N02.um.umsystem.edu ([169.254.5.4]) by UM-NCAS5.um.umsystem.edu ([207.160.158.210]) with mapi id 14.03.0266.001; Sun, 6 Nov 2016 17:54:15 -0600 From: "Montgomery-Smith, Stephen" To: "ctm-users@freebsd.org" Subject: Re: current ctm reports: Fatal error: Probably not a CTM-patch at all. Thread-Topic: current ctm reports: Fatal error: Probably not a CTM-patch at all. Thread-Index: AQHSN3rhpxHrR6EOWE+WtH6dmZFWK6DNB8iA Date: Sun, 6 Nov 2016 23:54:15 +0000 Message-ID: References: <201611051539.uA5FdbMK005641@fire.js.berklix.net> In-Reply-To: <201611051539.uA5FdbMK005641@fire.js.berklix.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 x-originating-ip: [128.206.49.160] Content-Type: text/plain; charset="Windows-1252" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Nov 2016 23:55:27 -0000 On 11/05/2016 10:39 AM, Julian H. Stacey wrote: > Hi ctm-users@freebsd.org > Anyone else seeing similar strangeness ? ... > No problem running on 9.2-RELEASE, but on today's current : > ( /usr/src .svn_revision 308280 .ctm_status src-cur 12727 ) > after an installworld & kernel ) >=20 > cd /usr/svn; cat .ctm_status > svn-cur 5081 > ctm -q /pub/FreeBSD/development/CTM/svn-cur/svn-cur.05[0-9][0-9][0-9].xz > /pub/FreeBSD/development/CTM/svn-cur/svn-cur.05000.xz \ > Fatal error: Probably not a CTM-patch at all. > # Yes I know I dont need earlier deltas, but its a cut & paste > # suggestion from my standard script > # The point is, ctm always used to just skip past deltas it didnt need, > # including those it now doesnt recognise as deltas. > # ctm also fails on delta it does need, see below: > # Both these fail: > ctm /pub/FreeBSD/development/CTM/svn-cur/svn-cur.05082.xz > ctm -v /pub/FreeBSD/development/CTM/svn-cur/svn-cur.05082.xz > Fatal error: Probably not a CTM-patch at all. > ctm: exit(65) >=20 > Delta is not corrupt: >=20 > cd /pub/FreeBSD/development/CTM/svn-cur > sha256 svn-cur.05082.xz > SHA256 (svn-cur.05082.xz) =3D d2b20f44265cca77a811eb074abdbe58466bf72d8f= 5f3a39113a7b82a5a0b1b8 >=20 > ssh ctm.berklix.org (or as no public login, ftp & sha256 localy) > cd /pub/FreeBSD/development/CTM/svn-cur > sha256 svn-cur.05082.xz > SHA256 (svn-cur.05082.xz) =3D d2b20f44265cca77a811eb074abdbe58466bf72d8f= 5f3a39113a7b82a5a0b1b8 >=20 > Proof that its not delta at fault, but ctm command: >=20 > cd /pub/FreeBSD/development/CTM/svn-cur; pwd > /.amd_mnt/fire/0s4/ftp/pub/FreeBSD/development/CTM/svn-cur > cd /usr/svn;pwd > /data/usr/ftp/pri/FreeBSD/development/FreeBSD-SVN >=20 > ssh fire # 9.2 host > cd /host/lapr/data/usr/ftp/pri/FreeBSD/development/FreeBSD-SVN > ctm /0s4/ftp/pub/FreeBSD/development/CTM/svn-cur/svn-cur.05082.xz > ctm: .ctm_status: Permission denied > # OK, i just auto apply deltas from /etc/aliases, hence > # it complaining about ownerships, but not about delta content. >=20 > ssh -l mailnull-csh localhost # still on 9.2 host > cd /host/lapr/data/usr/ftp/pri/FreeBSD/development/FreeBSD-SVN > ctm /0s4/ftp/pub/FreeBSD/development/CTM/svn-cur/svn-cur.05082.xz > > FS .ctm_status > > SV > svnadmin: E000045: Can't get exclusive lock on file 'base/db/txn-current= -lock': Operation not supported > Broken pipe > # OK that's some NFS problem applying delta, but at least old > # 9.2 ctm command accepts delta to apply, unlike current ctm >=20 > Curiously I am not seeing same problem running on 12 current file system > & 12 current bin/ctm, applying deltas to src-cur/ > cat .ctm_status > src-cur 12727 > ctm -q /pub/FreeBSD/development/CTM/src-cur/src-*.1[0-9][0-9][0-9][0-9].g= z > cat .ctm_status > src-cur 12729 >=20 > Cheers, > Julian >=20 Let me look into this. I did accidentally reboot the delta creating server a few days ago at an inopportune time. That might be the cause of the error. Sorry.=