Hi Everyone,
A new release, 2.39.0, and a patch release 2.38.2 are now available on the ITUGLIB website for the usual build targets.
2.38.2 is a back-port of fixes through 2.39.0.
Regards,
Randall Becker
On Behalf of the ITUGLIB Technical Committee
On Wednesday, December 14, 2022 at 3:06:40 a.m. UTC-5, Randall wrote:appears to be a workaround. Another workaround, without reverting is playing with the value of the configuration variable 'protocol.file.allow' to not be 'user' (the default). Setting the value to 'always' should allow the submodule operation that would
Hi Everyone,
A new release, 2.39.0, and a patch release 2.38.2 are now available on the ITUGLIB website for the usual build targets.
2.38.2 is a back-port of fixes through 2.39.0.
Regards,I found an edge condition in releases newer than 2.36.0 relating to local sub-volumes that causes git to limit functionality. If you are using submodules with a clone of a local repository, your submodule operations may fail. Reverting to 2.36.0
Randall Becker
On Behalf of the ITUGLIB Technical Committee
Regards.
Randall
On Wednesday, December 28, 2022 at 9:28:20 a.m. UTC-5, Randall wrote:appears to be a workaround. Another workaround, without reverting is playing with the value of the configuration variable 'protocol.file.allow' to not be 'user' (the default). Setting the value to 'always' should allow the submodule operation that would
On Wednesday, December 14, 2022 at 3:06:40 a.m. UTC-5, Randall wrote:
Hi Everyone,
A new release, 2.39.0, and a patch release 2.38.2 are now available on the ITUGLIB website for the usual build targets.
2.38.2 is a back-port of fixes through 2.39.0.
Regards,I found an edge condition in releases newer than 2.36.0 relating to local sub-volumes that causes git to limit functionality. If you are using submodules with a clone of a local repository, your submodule operations may fail. Reverting to 2.36.0
Randall Becker
On Behalf of the ITUGLIB Technical Committee
Regards.Nope, the config values do not fix the problem, so if you encounter "fatal: transport 'file' not allowed" during a submodule operation, the defect above has happened, and you probably need to revert. I am hopeful for a fix shortly and will report back.
Randall
On Wednesday, December 28, 2022 at 9:47:52 a.m. UTC-5, Randall wrote:appears to be a workaround. Another workaround, without reverting is playing with the value of the configuration variable 'protocol.file.allow' to not be 'user' (the default). Setting the value to 'always' should allow the submodule operation that would
On Wednesday, December 28, 2022 at 9:28:20 a.m. UTC-5, Randall wrote:
On Wednesday, December 14, 2022 at 3:06:40 a.m. UTC-5, Randall wrote:
Hi Everyone,
A new release, 2.39.0, and a patch release 2.38.2 are now available on the ITUGLIB website for the usual build targets.
2.38.2 is a back-port of fixes through 2.39.0.
Regards,I found an edge condition in releases newer than 2.36.0 relating to local sub-volumes that causes git to limit functionality. If you are using submodules with a clone of a local repository, your submodule operations may fail. Reverting to 2.36.0
Randall Becker
On Behalf of the ITUGLIB Technical Committee
back.Regards.Nope, the config values do not fix the problem, so if you encounter "fatal: transport 'file' not allowed" during a submodule operation, the defect above has happened, and you probably need to revert. I am hopeful for a fix shortly and will report
Randall
No root cause has yet been identified - not for lack of trying. As soon as I hear anything, I will post news. The key point is that if you are a submodule user, your upstream needs to be remote not local. If you are purely remote, you will not beimpacted. Otherwise, you will need to revert to 2.36.0 or earlier. Do not use 2.36.1 or newer as those have the change that causes this.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 307 |
Nodes: | 16 (2 / 14) |
Uptime: | 93:05:29 |
Calls: | 6,849 |
Files: | 12,352 |
Messages: | 5,414,683 |