[pacman-dev] [GIT] pacman branch, master now at v3.0.0-434-g48bf088
Hello,
This is an automated email from the git hooks/update script, it was
generated because a ref change was pushed to the repository.
Updating branch, master,
via 48bf088e65403049dc430fadf360355a8d5dc07d (commit)
via b86479cf9b584c62dbda967902cee2a81678c9ef (commit)
via 4942d216323cbe2f099c43893cc95368a3cd1197 (commit)
via 50bb16e0151e31479cb2602c9749ffe18f7a3592 (commit)
via cb3c3a920d976942fbc72b2d9dbff5320ca9415c (commit)
via f2f4ada1d6cfee83674684b948e5698049479f95 (commit)
via 47622eef4dd8fd86a0aa0e3ebdb7b33f7c9d6804 (commit)
from 219808714f94788a66a430786c552f60e95b1a01 (commit)
- Log -----------------------------------------------------------------
commit 48bf088e65403049dc430fadf360355a8d5dc07d
Author: Aaron Griffin
On Fri, Sep 28, 2007 at 01:26:58AM -0400, Aaron Griffin wrote:
commit 47622eef4dd8fd86a0aa0e3ebdb7b33f7c9d6804 Author: Aaron Griffin
Date: Wed Sep 19 00:21:56 2007 -0500 Support for localized times in metadata
Packages and DBs now support using the UNIX epoch (seconds since Jan 1, 1970) for use in builddate and installdate. This will only affect newly built packages. Old existing packages with the text format are still supported, but this is deprecated.
In the case of removal of text time support, this code will fail gracefully, returning the start of the epoch for broken packages.
Signed-off-by: Aaron Griffin
What about packages built with 3.0 that are installed / upgraded with 3.1 ? Apparently, for these packages, the build time isn't copied over to the local database. But the install date is generated and stored, in UNIX epoch. I am not saying this behavior is bad or anything, I rather just want to check this is the intended behavior :)
On 10/2/07, Xavier
What about packages built with 3.0 that are installed / upgraded with 3.1 ? Apparently, for these packages, the build time isn't copied over to the local database. But the install date is generated and stored, in UNIX epoch.
I am not saying this behavior is bad or anything, I rather just want to check this is the intended behavior :)
Just to see if I understand you - builddate is only valid for remote packages?
On Tue, Oct 02, 2007 at 04:06:32PM -0500, Aaron Griffin wrote:
On 10/2/07, Xavier
wrote: What about packages built with 3.0 that are installed / upgraded with 3.1 ? Apparently, for these packages, the build time isn't copied over to the local database. But the install date is generated and stored, in UNIX epoch.
I am not saying this behavior is bad or anything, I rather just want to check this is the intended behavior :)
Just to see if I understand you - builddate is only valid for remote packages?
Well, now, I don't understand the question. Let me try with an example : 1) package built and installed with 3.0 : $ cat /var/lib/pacman/local/sdl-1.2.12-1/desc | grep DATE -A1 %BUILDDATE% Sun Aug 5 13:37:03 2007 -- %INSTALLDATE% Mon Aug 6 19:59:09 2007 2) package built with 3.0 but installed with git : $ cat /var/lib/pacman/local/git-1.5.3.3-1/desc | grep DATE -A1 %INSTALLDATE% 1191220054 3) package built and installed with git : $ cat /var/lib/pacman/local/moc-2.5.0_alpha2-1/desc | grep DATE -A1 %BUILDDATE% 1191172788 -- %INSTALLDATE% 1191173034 No problems with 1 and 3. About 2, I don't think it's wrong, but there might also be other ways to handle this case, so I was just asking.
On 10/2/07, Xavier
On Tue, Oct 02, 2007 at 04:06:32PM -0500, Aaron Griffin wrote:
On 10/2/07, Xavier
wrote: What about packages built with 3.0 that are installed / upgraded with 3.1 ? Apparently, for these packages, the build time isn't copied over to the local database. But the install date is generated and stored, in UNIX epoch.
I am not saying this behavior is bad or anything, I rather just want to check this is the intended behavior :)
Just to see if I understand you - builddate is only valid for remote packages?
Well, now, I don't understand the question. Let me try with an example :
1) package built and installed with 3.0 :
$ cat /var/lib/pacman/local/sdl-1.2.12-1/desc | grep DATE -A1 %BUILDDATE% Sun Aug 5 13:37:03 2007 -- %INSTALLDATE% Mon Aug 6 19:59:09 2007
2) package built with 3.0 but installed with git :
$ cat /var/lib/pacman/local/git-1.5.3.3-1/desc | grep DATE -A1 %INSTALLDATE% 1191220054
3) package built and installed with git :
$ cat /var/lib/pacman/local/moc-2.5.0_alpha2-1/desc | grep DATE -A1 %BUILDDATE% 1191172788 -- %INSTALLDATE% 1191173034
Should be fixed in GIT, we just looked into it. -Dan
participants (3)
-
Aaron Griffin
-
Dan McGee
-
Xavier