Bug 396463

Summary:	sys-apps/portage-2.1.10.41: emerge-webrsync gets wrong local timestamp
Product:	Portage Development	Reporter:	Johannes Buchner <buchner.johannes>
Component:	Unclassified	Assignee:	Portage team <dev-portage>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	Normal
Version:	2.1
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Johannes Buchner 2011-12-29 22:56:02 UTC

The timestamp returned by date +%s isn't the same emerge-webrsync calculates.

myhost ~ # date; date +%s; emerge-webrsync
Thu Dec 29 23:51:22 CET 2011
1325199082
Fetching most recent snapshot ...
 * Latest snapshot date: 20111228
 * 
 * Approximate snapshot timestamp: 1325123100
 *        Current local timestamp: 1325118901
 * 
 * The current local timestamp is possibly identical to the
 * timestamp of the latest snapshot. In order to force sync, use
 * the --revert option or remove the timestamp file located at
 * '/mnt/portage/metadata/timestamp.x'.


Subsequently, no update is performed.

Reproducible: Always

Comment 1 Zac Medico gentoo-dev

2011-12-30 03:57:01 UTC

It's not supposed to use your system time. It's supposed to compare the times from the timestamp.x files contained in the trees. It doesn't sync if the timestamps are less than 1 day apart. Your timestamps are less than 1 day (86400 seconds) apart:

   1325123100 - 1325118901 = 4199

Comment 2 Johannes Buchner 2011-12-30 17:57:53 UTC

I see -- thanks.