Package Details: stgit 2.0.3-1

Git Clone URL: (read-only, click to copy)
Package Base: stgit
Description: Pushing/popping patches to/from a stack on top of Git, similar to Quilt
Upstream URL:
Licenses: GPL2
Submitter: None
Maintainer: jpgrayson
Last Packager: jpgrayson
Votes: 21
Popularity: 0.000905
First Submitted: 2007-03-31 20:22 (UTC)
Last Updated: 2022-11-21 05:32 (UTC)

Latest Comments

1 2 Next › Last »

Necoro commented on 2022-11-07 23:27 (UTC)

Thanks @jpgrayson for the fixes (also over at GitHub)!

Regarding the build: Have you by chance the static lib lying around somewhere? Or the built crate?

I'm building inside empty containers (using makechrootpkg) and I can't see a way how it could link statically, because it cannot fetch the libgit2-library out of thin air.

jpgrayson commented on 2022-11-07 21:10 (UTC)

I've added libgit2, bzip2, and curl as explicit dependencies in 2.0.0-2.

What I've found is that if, for example, libgit2 is not installed, the StGit build does work, but with libgit2 statically linked. So I am not able to reproduce the build failure.

Nonetheless, I think it is better for this package to have dynamic link dependencies and it will make builds consistent.

Thanks for pointing out this issue, @Necoro.

Necoro commented on 2022-11-07 10:59 (UTC)

A dependency to libgit2 is missing. Without this, compiling the git2 rust crate fails with messages like:

/usr/bin/ld: /build/stgit/src/stgit-2.0.0/target/release/deps/stg-d78e3aa44a4f9436.stg.f6b8ba36-cgu.10.rcgu.o: in function `git2::treebuilder::TreeBuilder::insert':
          stg.f6b8ba36-cgu.10:(.text._ZN4git211treebuilder11TreeBuilder6insert17hdb3493544d0fa99dE+0xac): undefined reference to `git_treebuilder_insert

Also, the claim in the README (the resulting binary being statically linked) is not correct, so libgit2 really is a dependency, not only a makedep.

terinjokes commented on 2021-09-27 21:15 (UTC)

Hello again. I'm working on stgit 1.3 right now, hope to get it to you shortly.

terinjokes commented on 2021-02-14 16:15 (UTC)

Sorry, been on holiday. Will work on update today.

jpgrayson commented on 2018-11-22 05:10 (UTC)

@terinjokes I did not realize that GitHub archive tarballs were not deterministic. Thanks for the heads-up.

I have made a proper release for v0.19 on GitHub:

The release contains an sdist tarball that I generated and uploaded with the release:

It's sha256sum is:


Thanks again for your help!

immae commented on 2018-11-21 18:45 (UTC)

So quick, thanks :)

terinjokes commented on 2018-11-21 18:40 (UTC)

I copied it to /usr/share/bash-completion/completions/stg. Keeping a copy in the previous location for now, in case it's being sourced manually.

immae commented on 2018-11-21 17:38 (UTC)

Hi @terinjokes, I see that the completion file for stgit is in /usr/share/stgit/completion/stgit-completion.bash, would it maybe make sense to move it to the standard location /usr/share/bash-completion/completions/, so that it is automatically found by bash scripts?

terinjokes commented on 2018-11-19 19:09 (UTC)

@jpgrayson GitHub archive tarballs are not guaranteed to be deterministic. (Likewise, tarballs generated by Git are also not deterministic).

I'll fix this package, but it would be great if definitive release tarballs could be uploaded somewhere.