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

Renaming passwords and directories fail #487

Closed
hannes08 opened this issue Oct 10, 2019 · 8 comments · Fixed by #532
Closed

Renaming passwords and directories fail #487

hannes08 opened this issue Oct 10, 2019 · 8 comments · Fixed by #532

Comments

@hannes08
Copy link

On renaming of a directory:
fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths
Git status shows an uncommited but staged change for the folder

On renaming of a file:
fatal: empty string is not a valid pathspec. please use . instead if you meant to match all paths
Git status shows an uncommited but staged change for the file. The file is unencrypted!

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.96. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot issue-label-bot bot added the bug label Oct 10, 2019
@annejan
Copy link
Member

annejan commented Oct 10, 2019

Hi @hannes08 that is very unfortunate.

I'd like to ask a couple of questions to help in debugging this issue.

  1. What OS are you using ?
    It would really help if I knew this was a Windows, macOS or Linux thing since all three handle files and folders a bit differently 😉

  2. Are you using QtPass with "native" gpg support or via pass?

  3. Do you have git support enables?
    This changes a lot of file manipulation behaviour.

@hannes08
Copy link
Author

Sorry I forgot to mention! :-)

  1. OS is Windows 10 (1709)
  2. Yes QTPass with "native" gpg
  3. Git support is enabled with Automatically push and pull and "add .gpg-id"

On drag and drop of a password the same isse arises (it's moved pyhiscally, staged in git but not committed or pushed). Side note: on moving, all passwords in destination folder will be reencrypted, but these changes are neither staged nor committed nor pushed.

@annejan
Copy link
Member

annejan commented Oct 10, 2019

Time for operation: No OS Left Behind

Since most issues on macOS and Linux/BSD now seem fixed . . it's once again time for me to dive into the wonderful world of Windows 🕺

@schmunk42
Copy link

I had a similar issue ... when renaming password QtPass removes .gpg and they disappear from the UI. I have to rename them manually and commit them.

Arch Linux, qtpass 1.3.2

@jwhonce
Copy link

jwhonce commented Mar 3, 2020

Same as @schmunk42 using: Fedora 31, qtpass 1.3.2-1.fc31

@orxobo
Copy link

orxobo commented Mar 16, 2020

Getting the same problem as @schmunk42.
Using Ubuntu 18.04 with fresh compile of master as of yesterday.

Also unable to delete a folder and i'm getting:
fatal: pathspec '/absolutepathtothefoldertodelete/' did not match any files
Where absolutepathtothefoldertodelete is the absolute path of the folder to delete, not a literal from the error.

Side note: when compiling i have to comment out the qmake automatic file naming of your translation files from main/main.cpp:
Q_INIT_RESOURCE(qmake_qmake_qm_files); // qmake names the file
otherwise it fails with unable to resolve qmake_qmake_qm_files

Regards,
Matt

@gardenappl
Copy link

+1 for @schmunk42, same issue on Windows 10, qtpass v1.3.2
I'm also commenting here because I believe that issue #520 is related to this.

I don't use Git integration and I don't have native Pass installed.

ChaoticEnigma added a commit to ChaoticEnigma/QtPass that referenced this issue Jun 26, 2020
Rewrite ImitatePass Move method
If no file is provided to ImitatePass GitCommit, do not pass --
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants