Return-Path: X-Original-To: apmail-subversion-dev-archive@minotaur.apache.org Delivered-To: apmail-subversion-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0426219051 for ; Tue, 26 Apr 2016 11:16:10 +0000 (UTC) Received: (qmail 84346 invoked by uid 500); 26 Apr 2016 11:16:09 -0000 Delivered-To: apmail-subversion-dev-archive@subversion.apache.org Received: (qmail 84292 invoked by uid 500); 26 Apr 2016 11:16:09 -0000 Mailing-List: contact dev-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@subversion.apache.org Received: (qmail 84282 invoked by uid 99); 26 Apr 2016 11:16:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Apr 2016 11:16:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D9F2A1A03E7 for ; Tue, 26 Apr 2016 11:16:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.999 X-Spam-Level: * X-Spam-Status: No, score=1.999 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id Fx5mDsFfqsSL for ; Tue, 26 Apr 2016 11:16:06 +0000 (UTC) Received: from deepth.de (deepth.de [81.169.159.190]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 16C575F24E for ; Tue, 26 Apr 2016 11:16:06 +0000 (UTC) Received: from b2b-130-180-18-42.unitymedia.biz ([130.180.18.42] helo=[192.168.3.124]) by deepth.de with esmtpa (Exim 4.72) (envelope-from ) id 1av0yL-0006WF-M0 for dev@subversion.apache.org; Tue, 26 Apr 2016 13:16:05 +0200 Subject: Re: inconsistent timestamps/headers in tarballs and repository To: dev@subversion.apache.org References: <284f6151-bebd-7aef-6109-3b4046907af4@gmx.de> From: Stefan Hett Message-ID: <51fd9746-b424-005d-2cd1-5c9a16abb8fc@egosoft.com> Date: Tue, 26 Apr 2016 13:16:05 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------D3092C0C207CA92DCD28502B" This is a multi-part message in MIME format. --------------D3092C0C207CA92DCD28502B Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 4/26/2016 1:08 PM, Evgeny Kotkov wrote: > Stefan Hett writes: > >> Hi, >> >> during the verification process of the tarballs I spotted that some files >> have a different HeadURL and/or different timestamp records in the files >> when comparing the archives with the content from the tagged revisions. >> >> Is that expected? >> >> For instance win-tests.py in 1.8.16: >> >> zip file: >> >> # $HeadURL: >> http://svn.apache.org/repos/asf/subversion/branches/1.8.x/win-tests.py $ >> >> tag: >> >> # $HeadURL: >> https://svn.apache.org/repos/asf/subversion/tags/1.8.16/win-tests.py $ > The procedure is described in the Community Guide. > (https://subversion.apache.org/docs/community-guide/releasing.html#rolling-release) > > Tarballs are rolled from the branch, the RM tests and signs them, and then > creates a tag. Existing tarballs follow this pattern as well. Hence, the > differences you mentioned are expected. Thanks for clarifying, Evgeny. -- Regards, Stefan Hett --------------D3092C0C207CA92DCD28502B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
On 4/26/2016 1:08 PM, Evgeny Kotkov wrote:
Stefan Hett <luke1410@gmx.de> writes:

Hi,

during the verification process of the tarballs I spotted that some files
have a different HeadURL and/or different timestamp records in the files
when comparing the archives with the content from the tagged revisions.

Is that expected?

For instance win-tests.py in 1.8.16:

zip file:

# $HeadURL:
http://svn.apache.org/repos/asf/subversion/branches/1.8.x/win-tests.py $

tag:

# $HeadURL:
https://svn.apache.org/repos/asf/subversion/tags/1.8.16/win-tests.py $
The procedure is described in the Community Guide.
(https://subversion.apache.org/docs/community-guide/releasing.html#rolling-release)

Tarballs are rolled from the branch, the RM tests and signs them, and then
creates a tag.  Existing tarballs follow this pattern as well.  Hence, the
differences you mentioned are expected.
Thanks for clarifying, Evgeny.

-- 
Regards,
Stefan Hett
--------------D3092C0C207CA92DCD28502B--