From 1c2f42b0e8f189425e3b65e196ef58008a20b58f Mon Sep 17 00:00:00 2001 From: sigil-03 Date: Sat, 19 Jul 2025 00:25:44 -0600 Subject: [PATCH] create new issue cc7c13a6220f963436dcf29274dc45c5 --- cc7c13a6220f963436dcf29274dc45c5/description | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 cc7c13a6220f963436dcf29274dc45c5/description diff --git a/cc7c13a6220f963436dcf29274dc45c5/description b/cc7c13a6220f963436dcf29274dc45c5/description new file mode 100644 index 0000000..316867e --- /dev/null +++ b/cc7c13a6220f963436dcf29274dc45c5/description @@ -0,0 +1,12 @@ +changes to the ent filesystem break older versions of ent + + +recently with the dependency API, i updated the ent DB with an entry which contains a dependency, and has an updated method of storing them (files inside of a directory instead of a file with a list of dependencies) + +this has caused a problem with mainline `ent` showing the following error: + +because mainline `ent` expects there to be a file with a list of dependencies, and when it goes to open the file, it errors, since it's actually a directory with the same name as what it expects the file to be named. + +we should probably make it so if `ent` doesn't understand something, it does not completely exit... at least in some cases? + +or enforce some kind of versioning on the DB or something... not entirely sure.