<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/crates/tor-dirmgr/Cargo.toml, branch arti-v0.4.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v0.4.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2022-05-27T14:18:52Z</updated>
<entry>
<title>Regenerate version bump from previous commit.</title>
<updated>2022-05-27T14:18:52Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-27T14:18:52Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4326aa1de9875ea399c3a608c0320bbe4b214a42'/>
<id>urn:sha1:4326aa1de9875ea399c3a608c0320bbe4b214a42</id>
<content type='text'>
This commit was made by reverting the previous commit, then
re-running the script I used to generate it.  In theory there should
be no semantic changes: only changes due to improved formatting from
cargo edit.
</content>
</entry>
<entry>
<title>Semantic version changes for Arti 0.4.0 release</title>
<updated>2022-05-27T13:01:20Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-27T13:01:20Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b232365a75249d6f767127feb2a47286f9ece762'/>
<id>urn:sha1:b232365a75249d6f767127feb2a47286f9ece762</id>
<content type='text'>
I followed the following procedure to make these changes:

* I used maint/changed_crates to find out which crates had changed
  since 0.3.0.
* I used grep and maint/list_crates to sort those crates in
  topological (dependency) order.
* I looked through semver_status to find which crates were listed as
  having semver-relevant changes (new APIs and breaking changes).
* I scanned through the git logs of the crates with no
  semver-relevant changes listed to confirm that, indeed, they had
  no changes.  For those crates, I incremented their patch-level
  version _without_ changing the version that other crates depend on.
* I scanned through the git logs of the crates with no
  semver-relevant changes listed to confirm that, indeed, they had
  no obvious breaking changes.
* I treated all crates that depend on `arti` and/or `arti-client` as
  having breaking changes.
* I identified crates that depend on crates that have changed, even
  if they have not changed themselves, and identified them as having
  a non-breaking change.
* For all of the crates, I used `cargo set-version -p $CRATE --bump
  $STATUS` (where `STATUS` is `patch` or `minor`) to update the
  versions, and the depended-upon versions.
</content>
</entry>
<entry>
<title>tor-dirmgr/state.rs: feed through additional parameters, use them</title>
<updated>2022-05-10T10:48:56Z</updated>
<author>
<name>eta</name>
<email>tor@eta.st</email>
</author>
<published>2022-05-04T15:48:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=cad815e31dbd1f7830e0965321ac52ac3333a390'/>
<id>urn:sha1:cad815e31dbd1f7830e0965321ac52ac3333a390</id>
<content type='text'>
- The additional parameters passed to GetConsensusState are now passed
  through all the states, and used as well.
- WriteNetDir doesn't have a now() or config() method any more, since
  the states now get this from the runtime or the config parameters.
- This required modifying the tests to make a mocked runtime and custom
  config directly, instead of using DirRcv for this purpose.
- Additionally, because we don't have to upgrade a weak reference for
  DirState::dl_config(), that function no longer wraps its return value
  in Result.
- (A bunch of the FIXMEs from the previous commit that introduced the
  additional parameters have now been rectified as a result.)
</content>
</entry>
<entry>
<title>Merge branch 'use-fs-mistrust'</title>
<updated>2022-05-09T19:27:25Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-09T19:27:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=4262e9d0ecca5f77f6ee2e0b00fb8c35d65f01e3'/>
<id>urn:sha1:4262e9d0ecca5f77f6ee2e0b00fb8c35d65f01e3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Update tor-dirmgr to use fs-mistrust.</title>
<updated>2022-05-09T18:40:29Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-03T17:08:18Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=20a85061b6c7c5a88b98497aabdf986cd6a462df'/>
<id>urn:sha1:20a85061b6c7c5a88b98497aabdf986cd6a462df</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Bump the version of every* crate to 0.3.0</title>
<updated>2022-05-06T14:03:15Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-05-06T14:03:15Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=7b93091f57f43ec8543a17052d60a2c8f7f2b0cc'/>
<id>urn:sha1:7b93091f57f43ec8543a17052d60a2c8f7f2b0cc</id>
<content type='text'>
* Except for safelog and fs-mistrust, which are new.
</content>
</entry>
<entry>
<title>Switch to derive_builder_arti_fork</title>
<updated>2022-05-06T12:36:40Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-05-06T12:18:03Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=030289481f79d7b1de4084e485b1793042b36ee8'/>
<id>urn:sha1:030289481f79d7b1de4084e485b1793042b36ee8</id>
<content type='text'>
For reference, the git source for this crate (and the others in its
workspace) currently lives in my personal github account (ijackson).
If this fork turns out to be long-lived and gains features and/or
users, it would be good to move it to a gitlab somewhere.

I have granted Nick crate ownership on the crates.io system.
</content>
</entry>
<entry>
<title>Merge branch 'derive-builder-git-fixup' into 'main'</title>
<updated>2022-04-27T14:31:08Z</updated>
<author>
<name>eta</name>
<email>tor@eta.st</email>
</author>
<published>2022-04-27T14:31:08Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=6f787e1e7707c2125a5d0df457e7894f944f4aa6'/>
<id>urn:sha1:6f787e1e7707c2125a5d0df457e7894f944f4aa6</id>
<content type='text'>
derive_builder: Use git dep everywhere, rather than cargo patch

See merge request tpo/core/arti!477</content>
</entry>
<entry>
<title>derive_builder: Use git dep everywhere, rather than cargo patch</title>
<updated>2022-04-27T13:57:59Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2022-04-27T13:44:59Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=a97ad69855cdf1931e29cc024a79336448f50990'/>
<id>urn:sha1:a97ad69855cdf1931e29cc024a79336448f50990</id>
<content type='text'>
The `[patch]` approach causes the tree not to build when used as a
dependency, unless the `[patch]` is replicated into the depending
project.

Instead, replace our `derive_builer =` dependencies with a reference
to a specific git commit:

  perl -i~ -pe 'next unless m/^derive_builder/; s#"(0\.11\.2)"#{ version = "$1", git = "https://github.com/ijackson/rust-derive-builder", rev = "ba0c1a5311bd9f93ddf5f5b8ec2a5f6f03b22fbe" }#' crates/*/Cargo.toml

Note that the commitid has changed.  This is because derive_builder is
in fact a workspace of 4 crates.  3 of them are of interest to arti
itself (the 4th exists only for testing).  So the same "add git
revision" treatment had to be done to the `derive_builder` and
`derive_builder_macro` crates.  Each dependency edge involves a new
commit in the derive_builder workspace, since we can't create a git
commit containing its own commitid.  (We want to use commits, rather
than a branch, so that what we are depending on is actually properly
defined, and not subject to the whims of my personal github
namespace.)

There are no actual code changes in derive_builder.
</content>
</entry>
<entry>
<title>Upgrade to Postage 0.5.0</title>
<updated>2022-04-26T16:16:22Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2022-04-25T20:06:31Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5586f0d039fc7b1fdec0e08579d5ecde3dcaa0a0'/>
<id>urn:sha1:5586f0d039fc7b1fdec0e08579d5ecde3dcaa0a0</id>
<content type='text'>
</content>
</entry>
</feed>
