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

Checkout issue #350

Open
gvanem opened this issue Feb 7, 2025 · 3 comments
Open

Checkout issue #350

gvanem opened this issue Feb 7, 2025 · 3 comments

Comments

@gvanem
Copy link

gvanem commented Feb 7, 2025

A problem with a git clone of this project.
I'm on Win-10 and did:

md Git-latest
cd Git-latest
git clone https://github.com/JvanKatwijk/qt-dab.git .
Cloning into '.'...
remote: Enumerating objects: 20424, done.
remote: Counting objects: 100% (1975/1975), done.
remote: Compressing objects: 100% (689/689), done.
remote: Total 20424 (delta 1471), reused 1393 (delta 1286), pack-reused 18449 (from 3)
Receiving objects: 100% (20424/20424), 549.85 MiB | 29.33 MiB/s, done.
Resolving deltas: 100% (15614/15614), done.
error: invalid path 'includes/backend/*.cpp'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

And a git restore --source=HEAD :/ also fails.

What's this? A path/filename issue on Windows only?

@JvanKatwijk
Copy link
Owner

JvanKatwijk commented Feb 7, 2025 via email

@gvanem
Copy link
Author

gvanem commented Feb 8, 2025

I never work with Windows (other than crosscompiling and testing).

Yet you want Qt-DAB to work on Windows?
When downloading a .zip from this repo, WinZip reports this:
Image

And 7z l qt-dab-master.zip shows:

...
2025-02-05 12:52:51 D....            0            0  qt-dab-master\includes\backend
2025-02-05 12:52:51 .....            0            0  qt-dab-master\includes\backend\*.cpp
...

Which 7z extracted as includes\backend\_.cpp. There should be no *.cpp files
under includes/, no? You have done a bad git command AFAICS.

Please fix this.

@JvanKatwijk
Copy link
Owner

JvanKatwijk commented Feb 8, 2025 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants