Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#76748 - [libbluray] Do not touch global git config
Attached to Project:
Arch Linux
Opened by Siegfried Metz (NiceGuy) - Monday, 05 December 2022, 17:06 GMT
Last edited by Toolybird (Toolybird) - Monday, 05 December 2022, 20:54 GMT
Opened by Siegfried Metz (NiceGuy) - Monday, 05 December 2022, 17:06 GMT
Last edited by Toolybird (Toolybird) - Monday, 05 December 2022, 20:54 GMT
|
Details-1.3.4libbluray incorporated changes which should be avoided. As can be seen with an example of gnome-settings-daemon commit [1], global git config modification should be avoided within a PKGBUILD.
"git -c protocol.file.allow=always submodule update" like documented in the official VSC guide [2] should be used, or something similar. This avoids touching users git config global settings. [1]: https://github.com/archlinux/svntogit-packages/commit/2d9d8a60bbea430a1c3cee8e9ef3609e67788fca [2]: https://wiki.archlinux.org/title/VCS_package_guidelines#Git_submodules Additional info: * libbluray-1.3.4 Steps to reproduce: Just a minor glitch in the matrix ;) git changed behavior for security, in order to use submodules, protocol.file.allow=always has to be used, but should be taken care of not to use --global scope. |
This task depends upon
I see your point. Then again, maybe it was just overlooked. My intent was to point out how it's officially documented.
Somehow it is set for other PGKBUILDs this way. Either way, I'm ok with it. I really wish it is uniformly handled, that's all. :)