Search Criteria
Package Details: git-machete 3.18.3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/git-machete.git (read-only, click to copy) |
|---|---|
| Package Base: | git-machete |
| Description: | Probably the sharpest git repository organizer & rebase/merge workflow automation tool you've ever seen |
| Upstream URL: | https://github.com/VirtusLab/git-machete |
| Keywords: | branches git rebase |
| Licenses: | MIT |
| Submitter: | alt0160 |
| Maintainer: | ilai |
| Last Packager: | ilai |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2019-05-17 08:04 (UTC) |
| Last Updated: | 2023-09-22 15:25 (UTC) |
Dependencies (11)
- git (git-vfs, git-run-command-patch-git, git-git, git-fc)
- python (python36, python32, python37, python39, python38, python310, python312)
- python-build (make)
- python-installer (python-installer-git) (make)
- python-setuptools (make)
- python-wheel (make)
- python-pytest (check)
- python-pytest-mock (check)
- bash (bash-devel-static-git, bash-git, bash-xdg, bash-devel-git, busybox-coreutils) (optional) – bash completion
- fish (fish-git) (optional) – fish completion
- zsh (zsh-git, zsh-fix-winchanged-git) (optional) – zsh completion
Latest Comments
1 2 Next › Last »
PawelLipski commented on 2023-08-09 19:10 (UTC)
Btw... @chrislea as I probably can't commit here directly (?), could you do the following:
Add fish completion (completion/git-machete.fish), probably under "$pkgdir/usr/share/fish/vendor_completions.d" - see https://git.alpinelinux.org/aports/tree/community/git-machete/APKBUILD
Add man page (docs/man/git-machete.1)... not sure what should be the target directory, but it's probably some pretty standard one :)
Best, Paweł
chrislea commented on 2023-05-16 16:46 (UTC)
Yup, @PawelLipski, looks good now. Just built 3.17.4 and everything worked correctly. Thanks!
PawelLipski commented on 2023-05-13 05:29 (UTC)
Think @chrislea, I think I've identified the problem now - pls check
makepkg ...for v3.17.4 (should be already released now that you're reading this comment)chrislea commented on 2023-05-10 12:51 (UTC)
@pawelLipski sure, here you go (sorry for the long output). This is with
pycheck -vvbuilding 3.17.3.PawelLipski commented on 2023-05-03 14:25 (UTC)
Huh okay... one more thing, could you change the
pytestinvocation incheck()topytest -vvand then runmakepkg -s -i -c? I hope for more useful output (stack traces etc.) showing up this waychrislea commented on 2023-05-02 16:27 (UTC)
@PawelLipski here is the complete log output up to where it outputs the specific error info from my local machine. Please note that I am not running this as root / sudo, which it looks like you were in your docker build. I'm not sure if that should make any difference.
chrislea commented on 2023-05-02 16:14 (UTC)
Hello @PawelLipski, sorry for the late reply. The failure just happens on my local machine. I'm running the basic command
in the directory where the PKGBUILD is. In the PKGBUILD, it looks like it's just running pytest.
Please let me know if there's any additional information I can provide.
PawelLipski commented on 2023-04-11 18:05 (UTC)
This means that either the tests are flaky, or, more likely, that the Dockerfile that I've cooked up doesn't simulate the actual build environment well ;D @chrislea, how did you run the check that reproduced the failure in
test_githubas of 3.16.1? was it a log from your local machine, or from some AUR build system?Also, how is it possible that an updated version of the package (3.16.1) is published despite the failure happening in
test_githubANDcheckfunction in PKGBUILD still having a call topytest?PawelLipski commented on 2023-04-11 18:02 (UTC)
Hmmm FWIW I've just tried reproducing the problems locally, using the following Dockerfile:
but the build apparently passed:
chrislea commented on 2023-04-05 17:19 (UTC)
@PawelLipski I just checked and as of 3.16.1 there is still an error in
test_github.py. If you'd like more information please let me know what I can get to you.1 2 Next › Last »