Fossil Forum

"bundle import" misbehaves with non-existing bundle file
Login

"bundle import" misbehaves with non-existing bundle file

"bundle import" misbehaves with non-existing bundle file

(1) By PChemGuy on 2024-04-16 11:28:05 [source]

If non-existing bundle file is provided to "bundle import", Fossil creates a new database file instead of reporting an error. Database connection settings used by "bundle import" should be adjusted to fail on missing database file rather than creating a new one.

(2) By Daniel Dumitriu (danield) on 2024-04-16 12:03:02 in reply to 1 [link] [source]

This is fixed in the first trunk version after your post.