David R. Morrison wrote:
[]
Anyway, my conclusion from all of this is that the two-exit-code
status of tar is here to stay, at least for now. And while Apple is
currently using tar-1.15.x, we have no control over when they might
change to tar-1.16.x. Thus, switching to /usr/bin/tar
On 05 Mar 2007, at 06:23, David R. Morrison wrote:
That thread was from October 2006...
sorry !
JF
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to
My interpretation of the early test results reported here is that tar
is indeed detecting a change in ctime and nothing more serious.
There are two possible solutions to this: patch tar, or patch dpkg.
I'm going to advocate that we patch dpkg.
My reasoning goes like this: the decision to
On 05 Mar 2007, at 02:30, David R. Morrison wrote:
My interpretation of the early test results reported here is that tar
is indeed detecting a change in ctime and nothing more serious.
There are two possible solutions to this: patch tar, or patch dpkg.
I'm going to advocate that we patch
On Mar 4, 2007, at 7:15 PM, Jean-François Mertens wrote:
Except that in the thread mentioned by dmacks, it is mentioned that
a new version of tar was due yesterday (sorry _ had no time to check,
really have for personal reasons no time for at least a week except
for the most urgent things),
