commit 0efb877b570d40cfe48b1145f901d284d69a4f2d
Author: Oliver Reiche <oliver.reiche@gmail.com>
Date: Wed Apr 22 15:04:59 2026 +0100
Update changelog and standards version
commit 04f411e57b7fdd8c5c96a422e1859dace5fc57c9
Author: Oliver Reiche <oliver.reiche@gmail.com>
Date: Wed Apr 22 16:01:38 2026 +0100
Add basic autopkgtest
commit d14311456c909e17e0cb233c899c6a6162bdedd4
Author: Adrian Bunk <bunk@debian.org>
Date: Wed Apr 22 12:06:49 2026 +0300
Non-maintainer upload
commit 81d9540bfb7b7a163c5b11e00fc589197e2c9f1a
Merge: 1675bc5 b1fb5fa
Author: Oliver Reiche <oliver.reiche@gmail.com>
Date: Wed Apr 22 15:02:02 2026 +0100
Merge branch 'upstream' into master
commit b1fb5fac3440ae2f3eb54e2da8f4f09e11666ce5
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Tue Apr 7 21:14:41 2026 +0200
Release 1.6.5
commit 292e08f617b970535e86d863a23b421574e3b746
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Apr 4 13:20:40 2026 +0200
CHANGELOG: mention --remote-instance-name and new default value
commit e7114714668b4d3381af0963f1f571641d4ec1c6
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Apr 4 12:14:44 2026 +0200
just-mr: support --remote-instance-name
commit 40c1b3719302d5ebc31bbe5b93b70ccb2928f1f2
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Apr 4 10:57:25 2026 +0200
just serve: allow setting remote instance name
commit e85952c3d2dfc3ddc32b4436f76ffa7d0ada9157
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Apr 4 10:54:06 2026 +0200
Extend simple execution-service test to also instance name is set
commit dcb1b702b283043af96f46518af1a4db4dbde313
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Apr 4 10:13:53 2026 +0200
just: add option --remote-instance-name
... to allow setting the instance name of the remote-execution service
used. Hard-coding that string to "remote-execution" is not correct and
does not work in all setups.
commit 667d51b983fcb5a7d56c0a53cb56c2a44e1bfdf7
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Apr 4 10:00:15 2026 +0200
just execute: log all requests at debug level
In this way, `just execute` can be used to debug the way a
remote-execution client presents itself at the interface. Also log
the instance name the client requested (even though we ignore this
value in `just execute`).
commit 93cf8b59cf33f566b5d2e0a9e0ee4141df0f568a
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Wed Mar 4 21:52:50 2026 +0100
CHANGELOG: document recent changes to `just execute`
commit 2985d7f843a70d7a713f11a17b54558cc735ec17
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Wed Mar 4 21:42:35 2026 +0100
just execute: unconditionally add the empty blob to CAS
Some build tools assume that the empty blob can always be referenced
on remote execution (also indireclty, e.g., as part of an action
description). This could occasionally cause build failures if the
empty blob was referenced before it was added to remote execution
for other reasons. Fix this by adding the empty blob right on start
up of the remote execution.
commit 5bf20cc883dedd0e59e663b144d96c5457e68ee2
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sun Mar 1 16:11:24 2026 +0100
just execute: log command line at debug level
In this way, `just execute` can also be used for debugging
remote-execution clients that might rewrite the command line before
sending it to remote execution.
commit 6beabac02e387d877b44124da7abfa93c41bb402
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sun Mar 1 16:32:59 2026 +0100
bytestream utils: support instance names that are not precisely one segment large
The specification says
`instance_name` is an identifier used to distinguish between
the various instances on the server. Syntax and semantics of
this field are defined by the server; Clients must not make
any assumptions about it (e.g., whether it spans multiple
path segments or not). If it is the empty path, the leading
slash is omitted, so that the `resource_name` becomes
`uploads/{uuid}/blobs/{digest_function/}{hash}/{size}{/optional_metadata}`.
To simplify parsing, a path segment cannot equal any of the
following keywords: `blobs`, `uploads`, `actions`, `actionResults`,
`operations`, `capabilities` or `compressed-blobs`.
however our implementation assumes that the instance name is
precisely one path segment wide. Allow arbitrary-width segments.
commit d893c4cafee91e3c8418f6adb0f08f612d03998d
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Feb 14 12:37:58 2026 +0100
Start 1.6.5 development cycle
commit 48df896cd76d7bbc6606d6fd551d707e0e31151e
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Feb 14 12:34:55 2026 +0100
Release 1.6.4
commit 72b52265f616fee0ce7b3a556b4d6744b38932f7
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Feb 14 12:33:40 2026 +0100
Update CHANGELOG
commit 1b84653c882291d395120a7d74a37502a373249b
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Feb 7 19:07:04 2026 +0100
Extend tree-ops test to verify the empty overlay
commit 0324a0978eb0d5113b17b83d0a9fe58b07da8584
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Sat Feb 7 19:17:53 2026 +0100
tree overlay action: correctly handle the case of overlaying no trees
The code for executing tree-overlay actions was folding the list of
trees to overlay starting with the first entry instead of using the
neutral element, i.e., the empty tree. While this is correct for
non-empty lists of trees to overlay, it would lead to a segmentation
fault in case of an empty list. Fix this.
commit 1675bc50dacf56ada7e049d6821d10c0d02a4769
Author: Oliver Reiche <oliver.reiche@gmail.com>
Date: Tue Jan 27 13:10:14 2026 +0100
Add Salsa CI
commit c54a46de7df0c6b26b7d8f4a10d380103da634fb
Author: Klaus T. Aehlig <aehlig@linta.de>
Date: Mon Oct 20 14:29:22 2025 +0200
BlobTree{,Ptr}: add instance of std::hash
As we're using instances of std::unordered_set<BlobTree> we need
the corresponding hash instances. As hashes are allowed to have
collisions, it is sound to only use the blob for hashing. Moreover,
in the intended use case, that blob even describes the data uniquely.
This omission was discovered when updating from gcc 14.2 to gcc 14.3
together with the corresponding C++ libraries.
commit 0802f713308b199d8815f9766b0bca17e2f3849a
Author: Oliver Reiche <oliver.reiche@huawei.com>
Date: Tue Sep 9 12:21:12 2025 +0200
Fix typos
commit a25e176c245a520f2545e64885e794efe7ebbdee
Author: Klaus Aehlig <klaus.aehlig@huawei.com>
Date: Wed Aug 20 14:08:16 2025 +0200
Add test verifying just-mr error reporting
... and, in particular, verify that we can use exit codes to distinguish
between the most common cases.
commit 9be92df77dbf80c6bb338dabda4b2f79238d6b90
Author: Klaus Aehlig <klaus.aehlig@huawei.com>
Date: Wed Aug 20 14:59:54 2025 +0200
just-mr(1): clarify the meaning of exit code 66
A missing or unknown subcommand is a syntactical error of the command
line and hence reported as 67. The only place where exit code 66 is
reported is if we could parse command line but failed to implement
that newly added subcommand. For compatibility reason, leave the
exit codes as they are, but document that 66 is an internal error
in the implementation of `just-mr`.
commit 11669610524a645972eecc2bdb2650f82bfc1dc3
Author: Klaus Aehlig <klaus.aehlig@huawei.com>
Date: Wed Aug 20 14:46:51 2025 +0200
just-mr: gracefully handle empty path string
The empty string is not a valid path. So, if a "file" repository
sets the empty string as value for "path" we can either report
an error or tacitly treat is as "." as we do for module paths; in
any case we should not crash. Fix the crash by treating "" as if
it were ".".
commit 00141288005c5157ff3baa420c7d98af4c634644
Author: Klaus Aehlig <klaus.aehlig@huawei.com>
Date: Mon Aug 11 14:41:35 2025 +0200
Start 1.6.4 development cycle
Among the 3 debian patches available in version 1.6.5-0.1 of the package, we noticed the following issues:
![[bug history graph]](https://qa.debian.org/data/bts/graphs/j/justbuild.png){kind=link}