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.

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

canceling a package upgrade with the confirmation check removes the package from chocolatey #780

Closed
elirnm opened this issue Jun 8, 2016 · 3 comments

Comments

@elirnm
Copy link

elirnm commented Jun 8, 2016

What You Are Seeing?

With git and git.install installed and outdated (going from 2.8.3 to 2.8.4), I ran 'cup git' and when the installation confirmation message was shown for git.install (which ran before git) I entered '2' to cancel the update. git.install canceled, but the git package updated without prompting for confirmation itself. After the update completed, chocolatey has lost its record of git.install being a chocolatey package, although the program is still installed on my computer.

What is Expected?

For chocolatey to remember packages despite canceled updates.

How Did You Get This To Happen? (Steps to Reproduce)

install git and git.install
run 'cup git'
when prompted for confirmation, enter 2 to cancel
notice that chocolatey thinks git.install is not installed

Output Log

https://gist.github.com/elirnm/2730b14f2900f793bfa8a83028950dcc

Screenshot

capture

@bartgenuit
Copy link

I had something similar while upgrading libreoffice. I forgot the '-y' switch, and halfway I decided I was tired of confirming all packages manually, so I bailed out (CTRL-C) to retry with the '-y'. However, by bailing out, chocolatey forgot about libreoffice completely.

Steps to reproduce:

> choco upgrade all
bail out by pressing CTRL-C at the confirmation dialog (in order to restart using -y switch)
> choco upgrade libreoffice
libreoffice is not installed. Installing...

My log: https://gist.github.com/bartgenuit/a9b3b192820c42f3bfafd7747187f772

@ferventcoder
Copy link
Member

@bartgenuit although you end up with the same result, your issue is a bit different. You were using control+c, where this person was using prompts and ran into an error.

For correctly handling control+c, we have #619

@pauby
Copy link
Member

pauby commented Aug 28, 2024

Duplicate of #619

@pauby pauby marked this as a duplicate of #619 Aug 28, 2024
@pauby pauby closed this as not planned Won't fix, can't repro, duplicate, stale Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants