Page MenuHomeFreeBSD

nanobsd: Add _xxx_pkg_db_vacuum
AbandonedPublic

Authored by senguptaangshuman17_gmail.com on Thu, Aug 20, 12:22 PM.
Tags
None
Referenced Files
F168503403: D59046.diff
Fri, Aug 28, 5:37 PM
F168490980: D59046.id184999.diff
Fri, Aug 28, 4:10 PM
Unknown Object (File)
Thu, Aug 27, 5:54 AM
Unknown Object (File)
Thu, Aug 27, 3:21 AM
Unknown Object (File)
Wed, Aug 26, 5:32 PM
Unknown Object (File)
Wed, Aug 26, 3:28 PM
Unknown Object (File)
Wed, Aug 26, 1:47 PM
Unknown Object (File)
Wed, Aug 26, 4:19 AM
Subscribers

Details

Reviewers
jlduran
jrm
ashish
Summary

Compact and verify the target pkg database after manual edits
(metalog fixups, trigger runs, etc).

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 76086
Build 72969: arc lint + arc unit

Event Timeline

Address review comments: normalize comment to # XXX:

I think this should only do a vacuum (integrity check).
So far we have not been able to create deterministic pkgbase images.

I think this should only do a vacuum (integrity check).
So far we have not been able to create deterministic pkgbase images.

As per my understanding, I'd like to keep the dump rather than dropping it, the function just dumps the db as a precondition for someday diffing/reproducing images. Once pkgbase builds are reproducible, this becomes the hook that lets us verify it, without another patch reintroducing it then.
Please let me know your view on this, then will change accordingly.

I think this should only do a vacuum (integrity check).
So far we have not been able to create deterministic pkgbase images.

As per my understanding, I'd like to keep the dump rather than dropping it, the function just dumps the db as a precondition for someday diffing/reproducing images.

OK. Then, this must be stated in the commit message, and clarified in the comment above the function. I'm not sure if that is even possible.

Once pkgbase builds are reproducible, this becomes the hook that lets us verify it, without another patch reintroducing it then.

The pkgbase builds are currently reproducible. The installations are not. Since we are installing (pkg install), and that process populates an sqlite3 database, the resulting database file is not deterministic.

senguptaangshuman17_gmail.com retitled this revision from nanobsd: Add _xxx_pkg_db_dump_or_vacuum to nanobsd: Add _xxx_pkg_db_vacuum.Tue, Aug 25, 6:14 AM