Your message dated Fri, 27 Feb 2026 01:00:13 +0000
with message-id <[email protected]>
and subject line Bug#1061772: fixed in jujutsu 0.30.0-1
has caused the Debian Bug report #1061772,
regarding RFP: jujutsu -- Git-compatible VCS that is both simple and powerful
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1061772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061772
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: [email protected]
* Package name : jujutsu
Version : 0.13.0
Upstream Contact: Martin von Zweigbergk <https://github.com/martinvonz>
* URL : https://martinvonz.github.io/jj/
* License : Apache-2.0
Programming Lang: Rust
Description : Git-compatible VCS that is both simple and powerful
Jujutsu is a powerful version control system for software
projects. You use it to get a copy of your code, track changes to the
code, and finally publish those changes for others to see and use. It
is designed from the ground up to be easy to use—whether you're new or
experienced, working on brand new projects alone, or large scale
software projects with large histories and teams.
Jujutsu is unlike most other systems, because internally it abstracts
the user interface and version control algorithms from the storage
systems used to serve your content. This allows it to serve as a VCS
with many possible physical backends, that may have their own data or
networking models—like Mercurial or Breezy, or hybrid systems like
Google's cloud-based design, Piper/CitC.
Today, we use Git repositories as a storage layer to serve and track
content, making it compatible with many of your favorite Git-based
tools, right now! All core developers use Jujutsu to develop Jujutsu,
right here on GitHub. But it should hopefully work with your favorite
Git forges, too.
We combine many distinct design choices and concepts from other
version control systems into a single tool. Some of those sources of
inspiration include:
* Git: We make an effort to be fast—with a snappy UX, efficient
algorithms, correct data structures, and good-old-fashioned
attention to detail. The default storage backend uses Git
repositories for "physical storage", for wide interoperability and
ease of onboarding.
* Mercurial & Sapling: There are many Mercurial-inspired features,
such as the revset language to select commits. There is no explicit
index or staging area. Branches are "anonymous" like Mercurial, so
you don't need to make up a name for each small change. Primitives
for rewriting history are powerful and simple. Formatting output is
done with a robust template language that can be configured by the
user.
* Pijul & Darcs: Jujutsu keeps track of conflicts as first-class
objects in its model; they are first-class in the same way commits
are, while alternatives like Git simply think of conflicts as
textual diffs. While not as rigorous as systems like Darcs and
Pijul (which are based on a formalized theory of patches, as
opposed to snapshots), the effect is that many forms of conflict
resolution can be performed and propagated automatically.
And it adds several innovative, useful features of its own:
* Working-copy-as-a-commit: Changes to files are recorded
automatically as normal commits, and amended on every subsequent
change. This "snapshot" design simplifies the user-facing data
model (commits are the only visible object), simplifies internal
algorithms, and completely subsumes features like Git's stashes or
the index/staging-area.
* Operation log & undo: Jujutsu records every operation that is
performed on the repository, from commits, to pulls, to
pushes. This makes debugging problems like "what just happened?" or
"how did I end up here?" easier, especially when you're helping
your coworker answer those questions about their repository! And
because everything is recorded, you can undo that mistake you just
made with ease. Version control has finally entered the 1960s!
* Automatic rebase and conflict resolution: When you modify a commit,
every descendent is automatically rebased on top of the
freshly-modified one. This makes "patch-based" workflows a
breeze. If you resolve a conflict in a commit, the resolution of
that conflict is also propagated through descendants as well. In
effect, this is a completely transparent version of git rebase
--update-refs combined with git rerere, supported by design.
[!WARNING] The following features are available for use, but experimental; they
may have bugs, backwards incompatible storage changes, and user-interface
changes!
* Safe, concurrent replication: Have you ever wanted to store your
version controlled repositories inside a Dropbox folder? Or
continuously backup repositories to S3? No? Well, now you can!
The fundamental problem with using filesystems like Dropbox and
backup tools like rsync on your typical Git/Mercurial repositories
is that that they rely on local filesystem operations being atomic,
serialized, and non-concurrent with respect to other reads and
writes—which is not true when operating on distributed file
systems, or when operations like concurrent file copies (for
backup) happen while lock files are being held.
Jujutsu is instead designed to be safe under concurrent scenarios;
simply using rsync or Dropbox and then using that resulting
repository should never result in a repository in a corrupt
state. The worst that should happen is that it will expose
conflicts between the local and remote state, leaving you to
resolve them.
The command-line tool is called jj for now because it's easy to type
and easy to replace (rare in English). The project is called "Jujutsu"
because it matches "jj".
----
There's been many attempts at "redoing" Git out there and indeed jj
lists a few in:
https://martinvonz.github.io/jj/v0.13.0/related-work/
... some are even possibly packaged in Debian (e.g. gitless). But none
go so far as jj *while being compatible with git* (except maybe
sapling).
I find the idea of automated working-tree commits to be quite
intruiguing and i love the backwards compatibility with git. So I
wonder when we should packge this in Debian. :)
--- End Message ---
--- Begin Message ---
Source: jujutsu
Source-Version: 0.30.0-1
Done: Federico Ceratto <[email protected]>
We believe that the bug you reported is fixed in the latest version of
jujutsu, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Federico Ceratto <[email protected]> (supplier of updated jujutsu package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 14 Feb 2026 18:05:25 +0100
Source: jujutsu
Binary: jujutsu jujutsu-dbgsym
Architecture: source amd64
Version: 0.30.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
<[email protected]>
Changed-By: Federico Ceratto <[email protected]>
Description:
jujutsu - Git-compatible version control system
Closes: 1061772
Changes:
jujutsu (0.30.0-1) unstable; urgency=medium
.
* Initial release. (Closes: #1061772)
Checksums-Sha1:
fd2810ffe370324b9d7361f7351069b10273ee0c 1976 jujutsu_0.30.0-1.dsc
005e66375f43744afb1ef2495e9d66912b428ef2 1977551 jujutsu_0.30.0.orig.tar.gz
e90fd8da1ebcb7559746514dc085f6306442e6cd 6736 jujutsu_0.30.0-1.debian.tar.xz
a1b1951e32059542bf66b573a63fc74389e5a756 58532948
jujutsu-dbgsym_0.30.0-1_amd64.deb
1a95e34a83d75ba354a755ae76c4ba863bf43f3d 6722 jujutsu_0.30.0-1_amd64.buildinfo
11eeec091c77e605d853e32e4a25d456c09f5977 5796400 jujutsu_0.30.0-1_amd64.deb
Checksums-Sha256:
56a2e77dae00de3005a2def9217904da03d06f4ee88ca1379b37412d31740042 1976
jujutsu_0.30.0-1.dsc
86f8df1e4e76c6a4bcdb728fa74876bacf931641157d16f6e93ebeb5bac0151c 1977551
jujutsu_0.30.0.orig.tar.gz
995de1387f618751ec54e326df19d471bb7f2d3410eef8ffcb7fe562d3d91a74 6736
jujutsu_0.30.0-1.debian.tar.xz
c98818b34c693edd707deb2f62b1ffed2a422146ed2f835930538f0e218ae2ee 58532948
jujutsu-dbgsym_0.30.0-1_amd64.deb
e2f453fdd216ad398d83982650a37dbd9469eec6709975935689bec392e4c0e6 6722
jujutsu_0.30.0-1_amd64.buildinfo
770b98b0518c9c47400c07382bc596280ef4d00e01b0b1641fb9d8bb118ef063 5796400
jujutsu_0.30.0-1_amd64.deb
Files:
6f3aab63febb5d26d46d5871e2b51135 1976 utils optional jujutsu_0.30.0-1.dsc
d1a364d2f52e4818fc5207630efc890c 1977551 utils optional
jujutsu_0.30.0.orig.tar.gz
59de9cc31b1730e76340bb72e93317dd 6736 utils optional
jujutsu_0.30.0-1.debian.tar.xz
27180d99ecec18a294df6c36f034212a 58532948 debug optional
jujutsu-dbgsym_0.30.0-1_amd64.deb
ff61fc9c46799fa4476b01e2ed5e75d3 6722 utils optional
jujutsu_0.30.0-1_amd64.buildinfo
176e51a3d031aa5900a4f188683bc6dc 5796400 utils optional
jujutsu_0.30.0-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCgAyFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAmmQrf4UHGZlZGVyaWNv
QGRlYmlhbi5vcmcACgkQbzG8RPUXfapB4A/+LiQbn9ISE9flw4eblG+WlCo8/ydj
3COPLoQrJicA3VaU9y5Ypo/AjepA0Rwswop05neXyYpfqjlrFFYBoNalY2bWCT4R
p6VXZ0jZKI61R41S74jbSIr8fL9V47cC681sCHr73UC7SdewVo1FoWjQFa1kp8A2
zihQSVHlUY3qp1+CwYiBTSBkphVqetpS1F6zODJd1P54nnQUGovZ/h0xgdnFqluX
ZaRo6/91ibmKaUKllCP8wxI+bY4EqA1nfMl9pTCHbQQ9HIAfDEM77OIju4GrnQwP
sf+k91wRXviOkd9Y57849wd0S5/I4uYArlGfhiEfM9uvJR2RfSHn4nINsvzvt7GN
Tk7FuOmkL6TzA4gYj/Oh6FLccQYpb0Kge7CpI/vxA0K4vtRSI10Vn/Uv5EfzQap7
Is0jV5bkF4l1EZP3p0YOsaLYg7iAE7WsCj1LorJz/Pwt3RKh7wQfl6EJtGmG6Etz
sTxevVL5Ibx6PN1qTN/PA/m0P7SkkX0QwBo9Ef39JEXtDeHHx8nrrw0zsB8CMNIx
7u+zjqWMae8cVIs4NlPdI3iQKwxJ2MhN5rsvZa6hrm9sp0eMJm2Ve71Q6fJv4B1t
9diZWUWov0p4Dcq1agNM3nvbLVVgJKWOpCc+bCTAayXC8iKeeGPPqxeH2MfdV5qb
KW3trKCMxclwh2k=
=j8Ir
-----END PGP SIGNATURE-----
pgpN3ut7wylNu.pgp
Description: PGP signature
--- End Message ---
