[MacPorts] #49498: Switching to a mirror causes a complete rebuild of the port index

MacPorts noreply at macports.org
Wed Oct 28 20:04:16 PDT 2015


#49498: Switching to a mirror causes a complete rebuild of the port index
-----------------------------+---------------------
  Reporter:  lpancescu@…     |      Owner:  admin@…
      Type:  defect          |     Status:  new
  Priority:  Low             |  Milestone:
 Component:  server/hosting  |    Version:
Resolution:                  |   Keywords:
      Port:                  |
-----------------------------+---------------------
Changes (by ryandesign@…):

 * priority:  Normal => Low
 * cc: ryandesign@… (added)


Comment:

 The primary rsync server in California contains the master copy of the
 data. The master data is created in various ways, depending on the rsync
 module in question. For distfiles, these are fetched after each port is
 committed. For packages, these are uploaded by the buildbot builders after
 every build. For ports and base, the
 [browser:trunk/base/portmgr/jobs/mprsyncup mprsyncup script] is used to
 create a tarball every 30 minutes by getting the latest information from
 the correct subdirectory of the Subversion repository.

 The mirror servers create an identical copy of the master. There's nothing
 involved in this other than running the appropriate `rsync` commands to
 copy the data from the master's various rsync modules. The mirror servers
 each have their own schedule for when and how often they sync, at the
 discretion of that mirror's administrator. So although the master updates
 every half hour, one mirror might only sync every hour, another every four
 hours. So the reason for the differences you observed is likely because
 the tarball you got from the mirror was older than the tarball on the
 master.

 You've apparently discovered that the timestamps of some of the files in
 the tarball change every time the tarball is recreated, even if there are
 no changes to the content. Possibly that could be optimized somehow. I
 have not read the mprsyncup script before so I haven't yet fully
 understood all of what it does.

 The only reason why this appears to be a problem for you is that it causes
 the portindex to be regenerated. This is only happening because a server-
 side index for El Capitan does not exist yet. The mprsyncup script has
 already been modified to generate an index for El Capitan in r140729, but
 the administrator of the master server needs to apply that change to the
 server. We have requested this in #49050. Once this is done, this
 timestamp problem shouldn't really matter.

-- 
Ticket URL: <https://trac.macports.org/ticket/49498#comment:1>
MacPorts <https://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list