gemvault 0.2.7 → 0.2.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: d8478b689eb6f6b68e0c18872f4b2ca47034b1bd93ef9d0d16ecb92e8666de85
4
- data.tar.gz: cb7f53a602a6b55a1a0593eda146635197e79dadb7366ca930a1e67b5b40d80d
3
+ metadata.gz: 4c4c2aeb84aac101aa2c4ae181f0ebdf5a43acb389fa17767b40b6576a31b145
4
+ data.tar.gz: 2957a3fe7f80f195361807e05da571b644f1bb559f7ca8aecac9c96a1f2c7370
5
5
  SHA512:
6
- metadata.gz: afa47c5b978c008d5fe46fb7399a3d1625505c8ad502d7e86e54c2f59a74b20b77077db8a31e60c70e294beeb54d51e8b808e005196c0b42f5e7e5cba0237574
7
- data.tar.gz: b9a93c14eaeb496f1a46e78494b6129faeb8501333f678a85e8d1d07afb1a14465b32f7cc941eed294eae0bb7c319dcbbd5a0264305843394a4f1a1113a62530
6
+ metadata.gz: adeda26a0e1a046f853bd2abce8e79c3522349b5aa9cc724e4a7e188614108c760158cdbc8e966cf245f6ccdbc19a9e5a1e2fb2956ec6ea9872cdcad7c14517d
7
+ data.tar.gz: 21439aa35d96aec76ba562abce0fd7ec25f3fc00b5a5d0f291801cfe5db1e5c9f5c60304cfbdab7ff7987ba24a3704d360ceff65a76f8d2992fd783cd602c93c
data/Dockerfile.test CHANGED
@@ -27,7 +27,7 @@ RUN dnf \
27
27
  # Keep this in step with the `BUNDLED WITH` line the project's own lockfile
28
28
  # carries. The plugin machinery these specs exercise is Bundler's own, so a
29
29
  # stale version silently tests different code.
30
- RUN gem install --no-document bundler -v 4.0.17
30
+ RUN gem install --no-document bundler -v 4.0.23
31
31
 
32
32
  # sqlite3 is not a gemvault runtime dependency; install it here so the upgrade
33
33
  # integration test can read the committed legacy SQLite (Dbvault) fixture it
data/issues.rec CHANGED
@@ -750,10 +750,10 @@ Id: 14
750
750
  Updated: Wed, 29 Jul 2026 16:41:11 -0400
751
751
  Name: gemvault doctor fails when bundler/inline is used
752
752
  Description: Loudly fails with 2 errors, one of which is "can't find gemfile"
753
- +
753
+ +
754
754
  + RESOLUTION: both errors reproduced in podman, and doctor turned out to be
755
755
  + broken twice over rather than once.
756
- +
756
+ +
757
757
  + (1) "Plugin bundler-source-vault is not installed". bundler/inline sets
758
758
  + BUNDLE_GEMFILE to a bare "Gemfile" for the life of the script (bundler
759
759
  + inline.rb:53), so Bundler.root is the script's working directory and the plugin
@@ -762,11 +762,11 @@ Description: Loudly fails with 2 errors, one of which is "can't find gemfile"
762
762
  + local_root only when SharedHelpers.in_bundle?, global_root otherwise
763
763
  + (plugin.rb:162) -- falls back to ~/.bundle/plugin. The uninstall therefore
764
764
  + looked in the wrong root and repaired nothing, silently.
765
- +
765
+ +
766
766
  + (2) "Could not locate Gemfile". doctor then exec'd `bundle install`, which with
767
767
  + no Gemfile prints its entire usage screen and exits 10 -- reading as gemvault
768
768
  + itself failing, after the repair it was asked for had already not happened.
769
- +
769
+ +
770
770
  + doctor now runs the uninstall with BUNDLE_GEMFILE="Gemfile" when the project
771
771
  + owns a plugin root Bundler would ignore, which is bundler/inline's own trick and
772
772
  + needs no file to exist; verified against the real thing (plain uninstall says
@@ -775,7 +775,7 @@ Description: Loudly fails with 2 errors, one of which is "can't find gemfile"
775
775
  + skips the reinstall and says so, exiting 0, because clearing the entry is the
776
776
  + repair and only the reinstall is unavailable -- an inline gemfile reinstalls the
777
777
  + plugin the next time the script runs.
778
- +
778
+ +
779
779
  + Gemvault::BundlerGemfile mirrors SharedHelpers#find_gemfile and
780
780
  + Gemvault::BundlerPluginRoot mirrors Plugin.root, both reimplemented rather than
781
781
  + delegated because bundler is deliberately not a dependency and doctor runs
@@ -818,7 +818,7 @@ Id: 16
818
818
  Updated: Wed, 29 Jul 2026 18:25:48 -0400
819
819
  Name: Add jruby-ci workflow
820
820
  Description: It should be already set up on the jruby-support branch. It just needs to be picked from it. DO NOT use the other code in that - it is very outdated
821
- +
821
+ +
822
822
  + RESOLUTION: shipped in commit 635ba41 ("ci: add JRuby test job") -- the jruby
823
823
  + job in .github/workflows/ci.yml runs the minitest suite on jruby-10.1.0.0 and
824
824
  + is green on CI.
@@ -1011,7 +1011,7 @@ Description: [dev@rstore]/workspace% bundle install
1011
1011
  + from /usr/local/bin/bundle:25:in '<main>'
1012
1012
  +
1013
1013
  + Though I will add that gemvault doctor followed by bundle install fixed the issue
1014
- +
1014
+ +
1015
1015
  + RESOLUTION: the broken-plugin-path wreck, recovered exactly as reported --
1016
1016
  + gemvault doctor then bundle install. The plugin index entry pointed into a
1017
1017
  + reinstalled rbenv ruby's gem home; bundler does not revalidate stored plugin
@@ -1066,7 +1066,7 @@ Name: Gemvault spams warnings on bundle install
1066
1066
  Description: /workspace/.bundle/plugin/gems/bundler-source-vault-0.2.2/gemvault_load_path.rb:31: warning: already initialized constant BundlerSourceVault::GemvaultLoadPath::GEM
1067
1067
  + /workspace/.bundle/plugin/gems/bundler-source-vault-0.2.2/gemvault_load_path.rb:32: warning: already initialized constant BundlerSourceVault::GemvaultLoadPath::SHIM
1068
1068
  + /workspace/.bundle/plugin/gems/bundler-source-vault-0.2.2/gemvault_load_path.rb:33: warning: already initialized constant BundlerSourceVault::GemvaultLoadPath::VAULT_SOURCE
1069
- +
1069
+ +
1070
1070
  + RESOLUTION: bundler can evaluate two installed copies of the shim in one
1071
1071
  + process -- an upgrade resolving a newer bundler-source-vault while the index
1072
1072
  + still names the old one, the dual-version plugin root the failure report
@@ -1148,7 +1148,7 @@ Id: 24
1148
1148
  Updated: Mon, 10 Aug 2026 23:16:35 +0000
1149
1149
  Name: doctor prints a backtrace when the plugin uninstall step fails
1150
1150
  Description: gemvault doctor's `bundle plugin uninstall` step runs with exception: true; a nonzero exit raises RuntimeError and a missing bundle raises Errno::ENOENT, and both escape Command#run to command_kit's ExceptionHandler, which prints error.full_message -- a full backtrace -- violating the one-line-and-exit-1 convention issue #15 established. Adjacent to issue #14 (doctor failing under bundler/inline). The ghost-specification sweep added for issue #23 reports its own failures as one line; the uninstall step should match.
1151
- +
1151
+ +
1152
1152
  + RESOLUTION: fixed alongside issue #27's transactional rework. The uninstall
1153
1153
  + step no longer runs with exception: true; a failing or missing bundle is one
1154
1154
  + line on stderr ("doctor: bundle plugin uninstall bundler-source-vault
@@ -1163,7 +1163,7 @@ Description: Project with Gemfile + locked json version + gemvault throws "bundl
1163
1163
  + /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.18/lib/bundler/runtime.rb:328:in 'Bundler::Runtime#check_for_activated_spec!': You have already activated json 2.21.2, but your Gemfile requires json 2.19.7. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)"
1164
1164
  +
1165
1165
  + I believe this error to be coming from gemvault's dependency on JSON. It is clear that dependencies are cursed in this project, whether its the added load time for reinstalling them on every `bundle install`, or errors like this one. Rather than rely on JSON, I think it would be better to just marshal our own manifest, or use some other serialization tool if any that rubygems already provides.
1166
- +
1166
+ +
1167
1167
  + RESOLUTION: gemvault no longer loads json, and the manifest is no longer a
1168
1168
  + JSON document. Whether gemvault's require was the activator on the reported
1169
1169
  + machine cannot be settled from here -- on the Fedora reproduction stack
@@ -1172,7 +1172,7 @@ Description: Project with Gemfile + locked json version + gemvault throws "bundl
1172
1172
  + stacks require does activate, gemvault held a live require in its
1173
1173
  + vault-read path, and it can no longer be the component that detonates
1174
1174
  + check_for_activated_spec!.
1175
- +
1175
+ +
1176
1176
  + Marshal was considered as the reporter suggested and rejected: a .gemv is a
1177
1177
  + file that arrives from elsewhere, the manifest is the root of trust (the
1178
1178
  + SHA256 digests live inside it, so nothing verifies it first), and
@@ -1181,7 +1181,7 @@ Description: Project with Gemfile + locked json version + gemvault throws "bundl
1181
1181
  + result. `gemvault list` on an untrusted vault would become arbitrary code
1182
1182
  + execution, and Marshal's versioned wire format would break the portability
1183
1183
  + a .gemv exists for.
1184
- +
1184
+ +
1185
1185
  + What replaced JSON is neither: the manifest was never document-shaped. It is
1186
1186
  + a table -- a header plus fixed-arity records of scalars, no nesting, no free
1187
1187
  + text -- and every field is drawn from an alphabet without whitespace once
@@ -1193,9 +1193,9 @@ Description: Project with Gemfile + locked json version + gemvault throws "bundl
1193
1193
  + and rejects everything else, because the file comes from elsewhere; writing
1194
1194
  + trusts the value objects this library constructed. Precedent is rubygems'
1195
1195
  + own compact index and Gemfile.lock, both line-oriented text.
1196
- +
1196
+ +
1197
1197
  + Format version 3; vaults are inspectable with `tar -xOf v.gemv manifest`.
1198
- +
1198
+ +
1199
1199
  + An existing format-2 vault keeps working. Gemvault::LegacyTarvault opens one
1200
1200
  + read-only, exactly as Dbvault does for SQLite, so `gemvault upgrade` migrates
1201
1201
  + it through the ordinary pipeline rather than leaving its gems stranded behind
@@ -1209,7 +1209,7 @@ Description: Project with Gemfile + locked json version + gemvault throws "bundl
1209
1209
  + Covered end to end by spec/integration/cli/commands/legacy_tarvault_spec.rb
1210
1210
  + against a committed format-2 fixture: list, extract, refused add, upgrade,
1211
1211
  + and writing to the upgraded vault.
1212
- +
1212
+ +
1213
1213
  + Settled after all: the Fedora image reproduces the rbenv-style stack once
1214
1214
  + the unbundled stdlib json is cleared away -- require then resolves through
1215
1215
  + gem activation, exactly the reported semantics.
@@ -1236,7 +1236,7 @@ Description: Reported from a container where bundle install could not succeed
1236
1236
  + index rather than exec'ing into `bundle install`, so a failed dependency
1237
1237
  + install cannot take the plugin down with it; or restore the previous index
1238
1238
  + when the step after the uninstall fails.
1239
- +
1239
+ +
1240
1240
  + RESOLUTION: the uninstall-reinstall pair is now transactional. doctor
1241
1241
  + snapshots the plugin index bundler will consult (Gemvault::BundlerPluginIndex
1242
1242
  + over BundlerPluginRoot#consulted) before clearing it, runs `bundle install`
@@ -1278,3 +1278,86 @@ Description: bundler-source-vault-0.2.4 survived in the plugin root's gems/,
1278
1278
  + Bundler's doing rather than the plugin's, but doctor is well placed to sweep
1279
1279
  + plugin-root versions the index no longer references.
1280
1280
  Status: open
1281
+
1282
+ Id: 30
1283
+ Updated: Fri, 14 Aug 2026 22:15:19 -0400
1284
+ Name: This message has many problems
1285
+ Description: 1. severity is unclear
1286
+ + 2. it doesn't make sense gramatically and contextually. what is "2" serving here? Is that the version number? I don't understand. horrible messaging
1287
+ + gemvault: format 2 vaults are read-only, and their stored times cannot be recovered. Migrate /workspace/update-gemvault-0.2.6/vendor/vendored_gems.gemv with: gemvault upgrade /workspace/update-gemvault-0.2.6/vendor/vendored_gems.gemv
1288
+ + sidekiq-ent-7.3.1
1289
+ + sidekiq-pro-7.3.4
1290
+ + stripe-ruby-mock-3.1.0.rc3
1291
+ Status: open
1292
+
1293
+ Id: 31
1294
+ Updated: Tue, 18 Aug 2026 12:33:27 -0400
1295
+ Name: CRITICAL REGRESSION Gems installed with "gem install --source myvault.gemv" no longer work
1296
+ Description: See the following sequence of commands and the error message. This path used to work
1297
+ +
1298
+ + gem install --source ~/repos/vault/rubylib/myvault.gemv reversal-store
1299
+ + Successfully installed reversal-store-0.2.4
1300
+ + Parsing documentation for reversal-store-0.2.4
1301
+ + Installing ri documentation for reversal-store-0.2.4
1302
+ + Done installing documentation for reversal-store after 0 seconds
1303
+ + 1 gem installed
1304
+ + UNIX-2021% gemvault -V
1305
+ + gemvault 0.2.7
1306
+ + UNIX-2021% rstore list
1307
+ + /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/source_list.rb:59:in 'Bundler::SourceList#add_plugin_source': undefined method 'new' for nil (NoMethodError)
1308
+ +
1309
+ + add_source_to_list Plugin.source(source).new(options), @plugin_sources
1310
+ + ^^^^
1311
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/dsl.rb:131:in 'Bundler::Dsl#source'
1312
+ + from /Users/davidgillis/repos/reversal-store/Gemfile:20:in 'block in Bundler::Dsl#eval_gemfile'
1313
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/dsl.rb:49:in 'BasicObject#instance_eval'
1314
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/dsl.rb:49:in 'block in Bundler::Dsl#eval_gemfile'
1315
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/dsl.rb:326:in 'Bundler::Dsl#with_gemfile'
1316
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/dsl.rb:47:in 'Bundler::Dsl#eval_gemfile'
1317
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/dsl.rb:13:in 'Bundler::Dsl.evaluate'
1318
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/definition.rb:40:in 'Bundler::Definition.build'
1319
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler.rb:234:in 'Bundler.definition'
1320
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler.rb:159:in 'Bundler.setup'
1321
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/setup.rb:16:in 'block in <top (required)>'
1322
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/ui/shell.rb:177:in 'Bundler::UI::Shell#with_level'
1323
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/ui/shell.rb:122:in 'Bundler::UI::Shell#silence'
1324
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.3/lib/bundler/setup.rb:16:in '<top (required)>'
1325
+ + from /usr/local/bin/rstore:8:in 'Kernel#require'
1326
+ + from /usr/local/bin/rstore:8:in '<main>'
1327
+ Status: open
1328
+
1329
+ Id: 32
1330
+ Updated: Wed, 26 Aug 2026 09:43:42 -0400
1331
+ Name: Error still arises when switching platform. Do not try and self heal. Find and fix root problem
1332
+ Description: Installing bundler-source-vault 0.2.7
1333
+ + The following plugin paths don't exist: /workspace/spool/.bundle/plugin/gems/bundler-source-vault-0.2.7/..
1334
+ +
1335
+ + This can happen if the plugin was installed with a different version of Ruby that has since been uninstalled.
1336
+ +
1337
+ + If you would like to reinstall the plugin, run:
1338
+ +
1339
+ + bundler plugin uninstall bundler-source-vault && bundler plugin install bundler-source-vault
1340
+ +
1341
+ + Continuing without installing plugin bundler-source-vault.
1342
+ + /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.18/lib/bundler/source_list.rb:65:in 'Bundler::SourceList#add_plugin_source': undefined method 'new' for nil (NoMethodError)
1343
+ +
1344
+ + add_source_to_list Plugin.source(source).new(options), @plugin_sources
1345
+ Status: open
1346
+
1347
+ Id: 33
1348
+ Updated: Wed, 26 Aug 2026 21:59:22 -0400
1349
+ Name: Gemvault no longer works on bundler/inline
1350
+ Description: /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.18/lib/bundler/resolver.rb:367:in 'Bundler::Resolver#raise_not_found!': Could not find gem 'bundler-source-vault' in locally installed gems. (Bundler::GemNotFound)
1351
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.18/lib/bundler/resolver.rb:529:in 'block in Bundler::Resolver#prepare_dependencies'
1352
+ + from /Users/davidgillis/.rbenv/versions/4.0.1/lib/ruby/gems/4.0.0/gems/bundler-4.0.18/lib/bundler/resolver.rb:504:in 'Hash#each'
1353
+ Status: open
1354
+
1355
+ Id: 34
1356
+ Updated: Sat, 05 Sep 2026 17:06:16 -0400
1357
+ Name: the recurring add_plugin_source error is not fixed. Running `doctor` is not an adequate solution. Fix the root problem
1358
+ Description: Error:
1359
+ +
1360
+ + /private/tmp/local/reversal-store/reversal-store/vendor/ruby/4.0.0/gems/bundler-4.0.20/lib/bundler/source_list.rb:65:in 'Bundler::SourceList#add_plugin_source': undefined method 'new' for nil (NoMethodError)
1361
+ +
1362
+ + add_source_to_list Plugin.source(source).new(options), @plugin_sources
1363
+ Status: open
@@ -1,3 +1,3 @@
1
1
  module Gemvault
2
- VERSION = "0.2.7".freeze
2
+ VERSION = "0.2.8".freeze
3
3
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: gemvault
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.7
4
+ version: 0.2.8
5
5
  platform: ruby
6
6
  authors:
7
7
  - David Gillis
@@ -115,7 +115,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
115
115
  - !ruby/object:Gem::Version
116
116
  version: '0'
117
117
  requirements: []
118
- rubygems_version: 4.0.18
118
+ rubygems_version: 4.0.24
119
119
  specification_version: 4
120
120
  summary: Multi-gem portable archives — a gem server in a file
121
121
  test_files: []