-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NuGet pack "The DateTimeOffset specified cannot be converted into a Zip file timestamp" #7001
Comments
The A NuGet solution could be:
There is precedence for this approach. |
I ran across this issue on a Mac OS 10.14 running dotnet 2.2 and nuget 4.8. can anyone tell me how to do a work around please? thank you. |
There is a fix for this problem? |
Also running into this. Modified date looks like |
That's a workaround for the bug, not a bugfix :) Both |
Updated the comment. From fix to workaround ;) |
Also hit by this. Running simple Here's the environment:
|
…users in GMT >0 timezones Workaround NuGet/Home#7001
…users in GMT >0 timezones Workaround NuGet/Home#7001
…users in UTC >0 timezones Workaround NuGet/Home#7001, NuGet/Home#8603
With the deterministic work, this becomes a higher priority |
Folks that are hitting this issue, I'd be curious to understand how the assemblies in your scenarios ended up with a 1980 date. When implementing deterministic pack we set the date for all the files in the package to 1980/1/1 and hitting this issue became more common. We'd be curious to learn which tooling was used that ended up creating assemblies with those dates. |
In my case, I just used the |
Thanks for letting us know @wazzamatazz That means you're in the
group, so we understand the root cause in that specific scenario :) |
Ref the above as it says the issue is resolved in nuget. |
The issue dotnet/core#3388 is referring to is #8599. This is a bug in the same problem space. |
@teroneko , @theolivenbaum In my case update to newer version of Microsoft.Extensions.* packages (from 3.1.0 to 3.1.4) fixed the problem, see : dotnet/extensions#2750 |
@maciej-izak Thanks for the advice. I will check it out later. |
…fied cannot be converted into a Zip file timestamp' (NuGet/Home#7001); Disable GitVersion capabilities: Teronis.MSBuild.GitVersionCache needs only the package reference; You can now specify config file and config file evaluation in GetVersionCache-task implemented; Wrapped SimpleExec.NonZeroExitCodeExcetion; Fixed conditionals regarding SemVer 2.0 format; Added missing 'PrivateAssets="all"' to *.Fody packages; The incremental build informations created when generating filesystem package is now deleted when rebuilding
Confirmed. Still happens as described. There are plenty of files microsoft *dlls which do not have a last changed date ('LastWriteTime'). For me all of them have been reference assemblies which i included in my dev packages and which i am skipping now. |
For me a problem as well, with |
I just ran into this issue as well after upgrading from 4.1.0 to 5.7.0. Any idea when this will be fixed? |
This is a workaround for a bug in NuGet. See NuGet/Home#7001
This is a workaround for a bug in NuGet. See NuGet/Home#7001.
I would appreciate a fix of this issue. It's currently breaking the Windows build of Ezra Project. |
Still happening - please fix this as it's breaking my CI. |
I'm interested in this one as my first 'nuget pack' challenge during "Customer sprint". |
Problem: When you install Microsoft.EntityFrameworkCore.Sqlite 3.1.0 you can see dlls without modify date. It cause to "The DateTimeOffset specified cannot be converted into a Zip file timestamp" when you try to pack my program. Solution: Update lib version related problem NuGetPackageExplorer/NuGetPackageExplorer#269 OrchardCMS/OrchardCore#4477 NuGet/Home#7001
…users in UTC >0 timezones Workaround NuGet/Home#7001, NuGet/Home#8603
Details about Problem
Running nuget pack .nuspec fails with the message
"The DateTimeOffset specified cannot be converted into a Zip file timestamp."
It happens with nuget 4.6.2 for a .dll file that has
LastWriteTime
31/12/1979 23:00:00 +00:00NuGet product used (NuGet.exe | VS UI | Package Manager Console | dotnet.exe):
NuGet.exe
version (4.6.2.5055)
OS version (i.e. win10 v1607 (14393.321)):
Windows 10 v 1803 Build 17134.81
Worked before? If so, with which NuGet version:
Works with v. 4.5.1.4879
Detailed repro steps so we can see the same problem
Run
nuget pack NuGetDateTimeOffsetIssue.nuspec
in the attached sample projecton nuget.exe v. 4.6 or higher.
Or:
Make a class library that includes NuGet log4net.Ext.Json v. 1.2.15.14586
Run
nuget spec <lib-name>
Run
nuget pack <.nuspec>
Verbose Logs
Sample Project
NuGetDateTimeOffsetIssue.zip
After fix (PR is in review)
Input file for test:
Now this file modified in 1959 after packing looks like this:
The text was updated successfully, but these errors were encountered: