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

build not possible for a long time #286

Closed
misterhsp opened this issue Nov 5, 2024 · 8 comments
Closed

build not possible for a long time #286

misterhsp opened this issue Nov 5, 2024 · 8 comments

Comments

@misterhsp
Copy link

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.

if ! ischroot && test "1" = "1"; then \
	mkdir -p .cargo; \
	cargo vendor --sync Cargo.toml | head -n -1 > .cargo/config; \
	echo 'directory = "vendor"' >> .cargo/config; \
	tar pcf vendor.tar vendor; \
	rm -rf vendor; \
fi
warning: `/media/dummy/build/cosmic-panel/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
warning: patch for `smithay-client-toolkit` uses the features mechanism. default-features and features will not take effect because the patch dependency does not support this mechanism
    Updating git repository `https://github.com/Smithay/client-toolkit//`
warning: spurious network error (3 tries remaining): failed to receive HTTP 200 response: got 404; class=Net (12)
warning: spurious network error (2 tries remaining): failed to receive HTTP 200 response: got 404; class=Net (12)
warning: spurious network error (1 tries remaining): failed to receive HTTP 200 response: got 404; class=Net (12)
error: failed to sync

Caused by:
  failed to load pkg lockfile

Caused by:
  failed to load source for dependency `smithay-client-toolkit`

Caused by:
  Unable to update https://github.com/Smithay/client-toolkit//#618a8764

Caused by:
  failed to clone into: /home/holgi/.cargo/git/db/_empty-f31853f5765173d8

Caused by:
  network failure seems to have happened
  if a proxy or similar is necessary `net.git-fetch-with-cli` may help here
  https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli

Caused by:
  failed to receive HTTP 200 response: got 404; class=Net (12)
make[1]: Verzeichnis „/media/dummy/build/cosmic-panel“ wird verlassen
   dh_clean
 dpkg-source -b .
dpkg-source: Information: Quellformat »3.0 (native)« wird verwendet
dpkg-source: Information: cosmic-panel wird in cosmic-panel_0.1.0.tar.xz gebaut
dpkg-source: Information: cosmic-panel wird in cosmic-panel_0.1.0.dsc gebaut
 debian/rules build
dh build
   dh_update_autotools_config
   dh_autoreconf
   debian/rules override_dh_auto_build
make[1]: Verzeichnis „/media/dummy/build/cosmic-panel“ wird betreten
just build-vendored
cargo build --release --frozen --offline 
warning: `/media/dummy/build/cosmic-panel/.cargo/config` is deprecated in favor of `config.toml`
note: if you need to support cargo 1.38 or earlier, you can symlink `config` to `config.toml`
warning: patch for `smithay-client-toolkit` uses the features mechanism. default-features and features will not take effect because the patch dependency does not support this mechanism
error: failed to load source for dependency `smithay-client-toolkit`

Caused by:
  Unable to update https://github.com/Smithay/client-toolkit//#618a8764

Caused by:
  can't checkout from 'https://github.com/Smithay/client-toolkit//': you are in the offline mode (--offline)
error: Recipe `build-debug` failed on line 29 with exit code 101
make[1]: *** [debian/rules:27: override_dh_auto_build] Fehler 101
make[1]: Verzeichnis „/media/dummy/build/cosmic-panel“ wird verlassen
make: *** [debian/rules:8: build] Fehler 2
dpkg-buildpackage: Fehler: Unterprozess debian/rules build lieferte Exitstatus 2
@garrettjwilke
Copy link

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.

@misterhsp
Copy link
Author

misterhsp commented Nov 5, 2024 via email

@garrettjwilke
Copy link

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?

@misterhsp
Copy link
Author

misterhsp commented Nov 5, 2024 via email

@misterhsp
Copy link
Author

misterhsp commented Nov 6, 2024 via email

@misterhsp
Copy link
Author

push

@misterhsp
Copy link
Author

misterhsp commented Nov 9, 2024 via email

@leviport
Copy link
Member

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.

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

3 participants