Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Bug]: error: File does not exist (true) while executing dotnet nuget push command #11601

Closed
renemadsen opened this issue Feb 16, 2022 · 4 comments
Closed

[Bug]: error: File does not exist (true) while executing dotnet nuget push command #11601

renemadsen opened this issue Feb 16, 2022 · 4 comments
Labels
Category:BreakingChange Functionality:Push Product:dotnet.exe RegressionDuringThisVersion A regression which broke since last RTM, and was fixed before the next RTM. Resolution:ByDesign This issue appears to be ByDesign

Comments

@renemadsen
Copy link

renemadsen commented Feb 16, 2022 •
edited
Loading

NuGet Product Used

dotnet.exe

Product Version

dotnet Version: 6.0.200

Worked before?

dotnet version: 6.0.102

Impact

Breaks github build scripts, since it's erroring out, even thought there is no problem.

Repro Steps & Context

Publish a package to nuget.org with the commad like:

dotnet nuget push /home/runner/work/eform-sdk-dotnet/eform-sdk-dotnet/artifacts/Microting.eForm.5.4.30.nupkg -k ${{secrets.NUGET_SECRET_KEY}} -s https://api.nuget.org/v3/index.json --skip-duplicate --no-symbols true

Working edition can be see here: https://github.com/microting/eform-sdk-dotnet/runs/5204099665?check_suite_focus=true#step:8:1

Broken can be seen here: https://github.com/microting/eform-sdk-dotnet/runs/5219100462?check_suite_focus=true#step:8:1

Doing the above, results in an error: "error: File does not exist (true)." even thought the package was pushed and published as expected.

Verbose Logs

No response
@Piedone Piedone mentioned this issue Feb 16, 2022
Closed
@Piedone
Copy link

Piedone commented Feb 16, 2022 •
edited
Loading

Noticed with Orchard Core too. It's definitely a 6.0.102 -> 6.0.200 bug.

You don't need to try to push to a remote feed, local publishing has the same error: dotnet nuget push 'src/**/*.nupkg' -n true -s C:\local-path --skip-duplicate

This is only coming up when -n true is specified. Workaround: just specify -n.

davidkallesen added a commit to atc-net/atc-coding-rules-updater that referenced this issue Feb 16, 2022
@davidkallesen
Remove true from --no-symbols du to suggestion: NuGet/Home#11601
2550865
@davidkallesen davidkallesen mentioned this issue Feb 16, 2022
Merged
davidkallesen added a commit to atc-net/atc-rest-api-generator that referenced this issue Feb 17, 2022
@davidkallesen
Remove true from --no-symbols due to suggestion
b594c47 
NuGet/Home#11601
@davidkallesen davidkallesen mentioned this issue Feb 17, 2022
Merged
davidkallesen added a commit to atc-net/atc that referenced this issue Feb 17, 2022
@davidkallesen
Remove true from --no-symbols due to suggestion NuGet/Home#11601
2a67b91
@davidkallesen davidkallesen mentioned this issue Feb 17, 2022
Merged
davidkallesen added a commit to atc-net/atc-blazor that referenced this issue Feb 17, 2022
@davidkallesen
Remove true from --no-symbols due to suggestion NuGet/Home#11601
59905c3
@davidkallesen davidkallesen mentioned this issue Feb 17, 2022
Merged
davidkallesen added a commit to atc-net/atc-template-dotnet-package that referenced this issue Feb 17, 2022
@davidkallesen
Remove true from --no-symbols due to suggestion NuGet/Home#11601
cb34abd
davidkallesen added a commit to atc-net/atc-test that referenced this issue Feb 17, 2022
@davidkallesen
Remove true from --no-symbols due to suggestion NuGet/Home#11601
745140a
@davidkallesen davidkallesen mentioned this issue Feb 17, 2022
Merged
@kartheekp-ms kartheekp-ms changed the title [Bug]: error: File does not exist (true). [Bug]: error: File does not exist (true) while executing dotnet nuget push command Feb 17, 2022
@kartheekp-ms
Copy link
Contributor

kartheekp-ms commented Feb 17, 2022 •
edited
Loading

In NuGet/NuGet.Client#4326 PR, we removed accepting values for --no-symbols and --disable-buffering options in dotnet nuget push command because they the values were not useful. I think it will be good to check why the command is throwing error: File does not exist (true). after the package has been pushed.

@kartheekp-ms kartheekp-ms added Functionality:Push Product:dotnet.exe RegressionDuringThisVersion A regression which broke since last RTM, and was fixed before the next RTM. and removed Triage:Untriaged labels Feb 17, 2022
LordMike added a commit to LordMike/MBW.Utilities.IPAddresses that referenced this issue Feb 18, 2022
@LordMike
Update SDK for nuget release too, fix regression for nuget push cmdline
900b0f3 
NuGet/Home#11601
rogerk-unifysquare added a commit to Unisys/NSign that referenced this issue Feb 21, 2022
@rogerk-unifysquare
Fix nuget push according to NuGet/Home#11601
2e19394
renemadsen added a commit to microting/eform-angular-frontend-base that referenced this issue Feb 21, 2022
@renemadsen
Removing true as end argument for --no-symbols according to NuGet/Hom…
4a238a1 
…e#11601
PathogenDavid added a commit to MochiLibraries/Biohazrd that referenced this issue Feb 21, 2022
@PathogenDavid
[CI] Fixed bogus error when pushing packages to GitHub.
c01d32c 
See NuGet/Home#11601
@Rebel028 Rebel028 mentioned this issue Feb 22, 2022
Merged
@capdiem capdiem mentioned this issue Feb 22, 2022
Open
@xqrzd xqrzd mentioned this issue Feb 24, 2022
Merged
@StefH StefH mentioned this issue Feb 25, 2022
Merged
degory added a commit to degory/ghul-targets that referenced this issue Feb 27, 2022
@degory
Remove 'true' from nuget push --no-symbols parameter (see NuGet/Home#…
0484c57 
…11601)
michael-brouchoud added a commit to woopsa-protocol/Woopsa that referenced this issue Mar 7, 2022
@michael-brouchoud
remove "true" value after --no-symbols parameters
744905b 
boolean is not required anymore NuGet/Home#11601
koenbeuk added a commit to koenbeuk/EntityFrameworkCore.Triggered that referenced this issue Mar 10, 2022
@koenbeuk
Fixed build.yml
c6d9546 
See: NuGet/Home#11601
Kurounin added a commit to Kurounin/publish-nuget that referenced this issue Mar 10, 2022
@Kurounin
fix: file not found error when using latest dotnet 6.0.2
27d5fff 
Details in NuGet/Home#11601 (comment)
@Kurounin Kurounin mentioned this issue Mar 11, 2022
Merged
lpreiner added a commit to lpreiner/BraceExpander that referenced this issue Mar 22, 2022
@lpreiner
Update dotnet.yml
db46cd4 
Updated nuget push command per NuGet/Home#11601
StevenTCramer added a commit to TimeWarpEngineering/timewarp-architecture that referenced this issue Mar 27, 2022
@StevenTCramer
One more attempt to solve github Action error
e990941 
NuGet/Home#11601
@StevenTCramer StevenTCramer mentioned this issue Mar 27, 2022
Merged
mdekrey added a commit to PrincipleStudios/principle-studios-openapi-generators that referenced this issue Apr 1, 2022
@mdekrey
Correct build failure
672fba0 
Remove parameter from `--no-symbols`

See NuGet/Home#11601 (comment)
@dharmaturtle dharmaturtle mentioned this issue Apr 3, 2022
Closed
@rprouse rprouse mentioned this issue Apr 18, 2022
Closed
Svek added a commit to ceronus/magic-packet that referenced this issue Jul 7, 2022
@Svek
Fixed the flags
32833d0 
NuGet/Home#11601 (comment)
Svek added a commit to ceronus/medius that referenced this issue Jul 7, 2022
@Svek
Fixed invalid flag
36e980c 
NuGet/Home#11601 (comment)
@yaqian256 yaqian256 mentioned this issue Jul 12, 2022
Merged
Mpdreamz added a commit to nullean/release-notes that referenced this issue Aug 11, 2022
@Mpdreamz
Fixes push failing after succesful push
8d70712 
See: NuGet/Home#11601
@Mpdreamz Mpdreamz mentioned this issue Aug 11, 2022
Merged
peache85 pushed a commit to woopsa-protocol/Woopsa that referenced this issue Aug 23, 2022
@P-H-Maillefer
Fix Client dispose bug + v1.3.2
e22b676 
commit 5b5d883
Author: Paul-Henri Maillefer <[email protected]>
Date:   Tue Aug 23 11:34:35 2022 +0200

    Add unit to check client dispose + Change version to 1.3.2

commit 440dcb0
Author: PeopleCanFly <[email protected]>
Date:   Tue Aug 23 11:33:33 2022 +0200

    Bugfix for Dispose (#81)

    Co-authored-by: David Rey <[email protected]>

commit 0262d23
Author: michael-brouchoud <[email protected]>
Date:   Mon Mar 7 09:28:09 2022 +0100

    remove "true" value after --no-symbols parameters

    boolean is not required anymore NuGet/Home#11601

commit 36c2144
Author: michael-brouchoud <[email protected]>
Date:   Mon Mar 7 09:27:52 2022 +0100

    remove "true" value after --no-symbols parameters

    boolean is not required anymore NuGet/Home#11601
mscottford added a commit to corgibytes/freshli-lib that referenced this issue Sep 8, 2022
@mscottford
Work around NuGet bug
f4c2b53 
Specifying `-n true` appears to cause problems. See NuGet/Home#11601 (comment)
cz-dev-ge added a commit to ZEISS-PiWeb/PiWeb-Formplots that referenced this issue Sep 14, 2022
@cz-dev-ge
fix: Removes parameter value due to change in .NET 6.0.200
977850f 
see NuGet/Home#11601
@cz-dev-ge cz-dev-ge mentioned this issue Sep 14, 2022
Merged
benmccallum referenced this issue in benmccallum/dotnet-references Oct 14, 2022
@benmccallum
Update nuget-push.yml
57a5b91
@abelbraaksma abelbraaksma mentioned this issue Nov 30, 2022
Closed
5 tasks
pmiossec added a commit to pmiossec/Gitextensions.AzureDevOpsCommitMessage that referenced this issue Dec 8, 2022
@pmiossec
fix error when pushing the nuget package to nuget.org
ca57d37 
The push worked but the build failed with error:
 "Your package was pushed. error: File does not exist (true)."

According to this (not tested), the fix is to remove "true"
NuGet/Home#11601 (comment)
This was referenced Dec 22, 2022
Merged
Merged
@aman-goel aman-goel mentioned this issue Mar 10, 2023
Merged
firenero added a commit to firenero/TypeId that referenced this issue Jul 22, 2023
@firenero
Update build scripts to use --no-symbols flag for NuGet push
58ca314 
Previously `-n 1` was used and it was causing the error:
NuGet/Home#11601
skukshaus added a commit to skukshaus/logger that referenced this issue Mar 23, 2024
@skukshaus
BUGFIX: nuget deployement should not crash
3c4aa14 
NuGet/Home#11601
@Dwicahya94 Dwicahya94 mentioned this issue Oct 22, 2024
Merged
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Category:BreakingChange Functionality:Push Product:dotnet.exe RegressionDuringThisVersion A regression which broke since last RTM, and was fixed before the next RTM. Resolution:ByDesign This issue appears to be ByDesign
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@renemadsen @Piedone @nkolev92 @erdembayar @kartheekp-ms