| Ticket Hash: | e9573e2d123878771cb83fc5e1adee565b2dbc77 | |||
| Title: | NuGet (3) 'pack' command breaks package restore (and maybe other features) | |||
| Status: | Closed | Type: | Packaging | |
| Severity: | Important | Priority: | Blocker | |
| Subsystem: | NuGetPackage | Resolution: | External_Bug | |
| Last Modified: | 2016-10-07 19:22:02 | |||
| Version Found In: | 1.0.103.0 | |||
| User Comments: | ||||
mistachkin added on 2016-10-05 05:57:12:
(text/x-fossil-plain)
NuGet issue appears to be [https://github.com/NuGet/Home/issues/3050]. mistachkin added on 2016-10-05 06:00:53: (text/x-fossil-plain) List of possible workarounds: 1. Wait for an upstream fixes to NuGet 3.x. 2. Stop using NuGet 3.x for official release builds of the NuGet packages. 3. Continue using NuGet 3.x for official release builds of the NuGet packages and then manually patch the contained nuspec files to re-add the trailing zero. mistachkin added on 2016-10-05 21:16:09: (text/x-fossil-plain) Further findings: 1. There is no clean way to replace the existing (semi-broken) NuGet packages. 2. It looks like the path forward is to use NuGet 2.x only for the foreseeable future. mistachkin added on 2016-10-07 19:22:02: (text/x-fossil-plain) Workaround activated on trunk via check-in [bb7d27069fb38310]. This issue is now closed. | ||||
