-
Notifications
You must be signed in to change notification settings - Fork 32
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
build not possible for a long time #286
Comments
i just attempted to build, and it worked. this could be something with your |
I don't have ~/.gitconfig. It is the pure clone of your repo. I have not
changed anything.
Am 05.11.24 um 17:09 schrieb garrettjwilke:
…
i just attempted to build, and it worked. this could be something with
your |~/.gitconfig| file.
i would backup that file, and try removing it. it might be trying to
update/clone using https rather than ssh.
—
Reply to this email directly, view it on GitHub
<#286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKGJLRMFO6WHSFC4XAZOTT3Z7DUSBAVCNFSM6AAAAABRG3NCOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJXGU4TCNRTGU>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
on Pop_OS! 22.04 i just tested on a clean install with nothing else on it.
also what distro/OS are you running? |
Distro is Debian SID. My last build about 2 - 3 weeks ago ran without
errors. But since then it doesn't work anymore.
Am 05.11.24 um 17:38 schrieb garrettjwilke:
…
on Pop_OS! 22.04 i just tested on a clean install with nothing else on it.
perhaps you could clone the repo in another directory and try again?
i made sure to have |rustup|, |debhelper|, |just|, and
|libxkbcommon-dev| installed. then i ran the following:
|dpkg-buildpackage -b -d |
also what distro/OS are you running?
—
Reply to this email directly, view it on GitHub
<#286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKGJLRP6UCA4USDYGZ5ANR3Z7DYCHAVCNFSM6AAAAABRG3NCOSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJXGY3DENRUGU>.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I can do what I want here, this error remains. Otherwise it always
worked without errors
....
|
push |
I have a solution, but I don't understand why it works like this.
Maybe one of you knows?
rust-lang/cargo#6513 (comment)
Thanks ...
|
If it was a configuration problem, I'm going to go ahead and close this bug report. It's clearly an isolated occurrence. As it says in that link, the protocol doesn't work well with that poster's proxy. If the same solution works for you, then your situation is probably similar. |
Since some time cosmic-panel cannot be built because a git-checkout always fails. By the way, the same thing also happens with cosmic-settings.
The text was updated successfully, but these errors were encountered: