K4sum1

How did you patch Pyinstaller 4.10 to work with XP? I first tried 6.1.0 because it was what the project I use originally supported and had only a few missing functions. I patched the source code, rebuilt and used it but I just get a blank Unhandled exception in script error when it's opened. Then I found this and decided to try 4.10, but it still has one of the things I need to patch So I carried that patch over to 4.10, and it built fine, but when installing it, I get this error and I'm not sure what to do. (env_build) C:\Users\Admin\Documents\GitHub\xl-converter\misc\pyinstaller>pip install . Processing c:\users\admin\documents\github\xl-converter\misc\pyinstaller Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... error error: subprocess-exited-with-error × Preparing metadata (pyproject.toml) did not run successfully. │ exit code: 1 ╰─> [41 lines of output] Traceback (most recent call last): File "C:\Users\Admin\Documents\GitHub\xl-converter\env_build\lib\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 363, in <module> main() File "C:\Users\Admin\Documents\GitHub\xl-converter\env_build\lib\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 345, in main json_out['return_val'] = hook(**hook_input['kwargs']) File "C:\Users\Admin\Documents\GitHub\xl-converter\env_build\lib\site-packages\pip\_vendor\pep517\in_process\_in_process.py", line 164, in prepare_metadata_for_build_wheel return hook(metadata_directory, config_settings) File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\build_meta.py", line 376, in prepare_metadata_for_build_wheel self.run_setup() File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\build_meta.py", line 521, in run_setup super().run_setup(setup_script=setup_script) File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\build_meta.py", line 319, in run_setup exec(code, locals()) File "<string>", line 249, in <module> File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\__init__.py", line 117, in setup return distutils.core.setup(**attrs) File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\_distutils\core.py", line 157, in setup dist.parse_config_files() File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\dist.py", line 651, in parse_config_files setupcfg.parse_configuration( File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\config\setupcfg.py", line 199, in parse_configuration meta.parse() File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\config\setupcfg.py", line 512, in parse section_parser_method(section_options) File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\config\setupcfg.py", line 487, in parse_section self[name] = value File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\config\setupcfg.py", line 305, in __setitem__ parsed = self.parsers.get(option_name, lambda x: x)(value) File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\config\setupcfg.py", line 604, in _parse_version return expand.version(self._parse_attr(value, self.package_dir, self.root_dir)) File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\config\setupcfg.py", line 429, in _parse_attr return expand.read_attr(attr_desc, package_dir, root_dir) File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\config\expand.py", line 186, in read_attr module = _load_spec(spec, module_name) File "C:\Users\Admin\AppData\Local\Temp\pip-build-env-5axojfce\overlay\Lib\site-packages\setuptools\config\expand.py", line 207, in _load_spec spec.loader.exec_module(module) File "<frozen importlib._bootstrap_external>", line 843, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "C:\Users\Admin\Documents\GitHub\xl-converter\misc\pyinstaller\PyInstaller.py", line 15, in <module> from PyInstaller.__main__ import run ModuleNotFoundError: No module named 'PyInstaller.__main__'; 'PyInstaller' is not a package [end of output] note: This error originates from a subprocess, and is likely not a problem with pip. error: metadata-generation-failed × Encountered error while generating package metadata. ╰─> See above for output. note: This is an issue with the package mentioned above, not pip. hint: See above for details.

Could try https://catbox.moe/ for quick uploads, or https://archive.org/ for longer term storage.

Try going to about:support and click the Clear Startup Cache button. If the issue still occurs, try the browser without the userChrome.css theme you have.

Gonna need a little more info than that. What version, OS, and OS theme?

I'll be getting ESR 128.7.0 out before 135. I'm doing some research that required me to work on the 128 branch, and while I'm here I figure I'll make 128.7.0 while I'm at it. Don't know when 128.8 will come out, that depends on Mozilla, and then for me to have time for it. I think this is a Firefox feature. If you use the r3dfox theme, the icons should be separate.

https://github.com/Eclipse-Community/r3dfox/releases/tag/v128.6.0

I probably won't make a 134 or a true new version for a while, but I figured I would update ESR since that's a simple rebase. I fired up the ESR VM, and apparently I made a 128.5 and never published it. I don't remember if there was something wrong or if I just forgot I did it. I guess I'll just rebase to latest 128 ESR and build that and see what it's like.

I forgot there was a thread like this here. I only got notified now that I'm in the process of configuring an email server again and I got some emails now. Basically I had to migrate to another server while I was still in the process of setting it up, which means there's some bugs. Periodically giving an error 500 is one of these bugs. I'm not sure what causes this exactly, but my temp workaround is to cron job restart the server every so often. So if it occurs, the server will automatically restart the process and fix the issue after a bit.

I did try previously modding the DanielK driver to work with any controller and it didn't go too well. My VM BSOD'd at shutdown after installing, and when I tried adding it to setup with txtsetup.oem it bluescreens on Ryzen.

smh my head

idk github is funny I don't think my modifications are extensive enough to modify any real code count by more than like 0.1%

accessibility.force_disabled I build with ac_add_options --disable-accessibility, so not applicable here. app.shield.optoutstudies.enabled is already set to false. beacon.enabled is still true since it seems to be a web standard, and I don't want to break anything that may use it. However if it is bad let me know. browser.laterrun.enabled is already set to false. browser.shell.checkDefaultBrowser I want to keep at true because I don't want to confuse new users if they want to set as default and are used to the prompt. browser.slowStartup.notificationDisabled has no mention in the Firefox source code, so would be useless to set. browser.uitour.enabled again seems like something that could confuse new users if disabled, so I'd rather keep it on. default-browser-agent.enabled I build with ac_add_options --disable-default-browser-agent, so not applicable here. extensions.update.* Automatic extension updates are fine, some just need to update like uBlock Origin with everything YouTube is trying to do. I'd rather not mess with rendering stuffs and anger people if the defaults work fine for most.

I assume Mozilla has a reason to not enable this by default. It's not telemetry or anything malicious. The update stuff does not matter here since the updater component is disabled at compile.

idk anything about Chromium, that includes CentBrowser.

Mozilla devs do not revert changes unless it breaks building the browser. Even if the change sucks and nobody likes it.