<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, Feb 19, 2025 at 4:19 PM James Abernathy <<a href="mailto:jfabernathy@gmail.com">jfabernathy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 19, 2025 at 4:06 PM James Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 19, 2025 at 3:52 PM Roland Ernst <<a href="mailto:rcrernst@gmail.com" target="_blank">rcrernst@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 19, 2025 at 9:39 PM James Abernathy <<a href="mailto:jfabernathy@gmail.com" target="_blank">jfabernathy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 19, 2025 at 3:30 PM Roland Ernst <<a href="mailto:rcrernst@gmail.com" target="_blank">rcrernst@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div>It is already there, see<br><a href="https://github.com/MythTV/mythtv/commit/3a2980a3b96e2c6b128b9c4bb88db2b83aec9bdd" target="_blank">https://github.com/MythTV/mythtv/commit/3a2980a3b96e2c6b128b9c4bb88db2b83aec9bdd</a></div><div><br></div><div>Roland <br></div></div></div><br></blockquote><div><br></div><div>If I'm reading the commit correctly, it's only in master and not fixes/35. Could that be why it's failing for me?</div><div><br></div><div>JIm A</div><div> <br></div></div></div></blockquote><div>It is on the fixes/35 branch as well. Github only shows the tags, not the branches.</div><div>What is exactly failing on for you?</div><div><br></div><div>Roland</div><div> <br></div></div></div></blockquote><div><br></div><div>I'm testing on a fresh system right now, but this morning on v35, it was not building or placing the python bindings anywhere. Not only was find_orphans.py not working but the user job lookup metadata failed.</div><div><br></div><div>So on this build, besides the ansible dependencies, I also added python-pip, but I'm not using the -DMYTH_BINDINGS_INSTALL_ROOT=/</div><div></div><div><br></div><div>Once I rebuilt with Bill's recommendation of -DMYTH_BINDINGS_INSTALL_ROOT=/ I got the bindings and stuff started working.</div><div><br></div><div>We'll see what works this time.</div><div><br></div><div>Jim A</div></div></div></blockquote><div><br></div><div>Okay on a clean system cmake building from master after building there are no mythtv python bindings anywhere on the computer.</div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"><br></span></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">plocate site-packages grep -i mythtv</span></span></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"><br></span></span></div><div>produces nothing. If I look at the console of the sudo cmake --build build-qt5 I see the error:</div><div><br></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">error: externally-managed-environment</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br>
<br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">× This environment is externally managed</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">╰─> To install Python packages system-wide, try 'pacman -S</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> python-xyz', where xyz is the package you are trying to</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> install.</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> </span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> </span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> If you wish to install a non-Arch-packaged Python package,</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> create a virtual environment using 'python -m venv path/to/venv'.</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> Then use path/to/venv/bin/python and path/to/venv/bin/pip.</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> </span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> </span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> If you wish to install a non-Arch packaged Python application,</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> it may be easiest to use 'pipx install xyz', which will manage a</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> virtual environment for you. Make sure you have python-pipx</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)"> installed via pacman.</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br>
<br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python in</span><br>stallation or OS, by passing --break-system-packages.<span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">hint: See PEP 668 for the detailed specification.</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span></span></div><div><br></div><div>Jim A</div></div></div></blockquote><div><br></div><div>I went back and delete build-qt5 directory and rebuilt but with both options:</div><div><br></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">sudo cmake --preset qt5 -DMYTH_BINDINGS_INSTALL_ROOT=/ -DCMAKE_INSTALL_PREFIX=/usr</span><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">sudo cmake --build build-qt5</span><br><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">
</span><br></span></div><div>This time <span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">plocate site-packages | grep -i mythtv produces a lot of output.</span></span></div><div><br><span style="font-family:monospace"></span></div><div><span style="font-family:monospace">But it also shows this instead of the last PEP668 error. This time it's a warning.</span></div><div><br></div><div><br></div><div><span style="font-family:monospace"><span style="color:rgb(0,0,0);background-color:rgb(255,255,255)">WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusabl</span><br>e. It is recommended to use a virtual environment instead: <a href="https://pip.pypa.io/warnings/venv">https://pip.pypa.io/warnings/venv</a>. Use the --root-user-action option if you know what you are doing and want to<br> suppress this warning.<br></span></div><div><br></div><div>Jim A</div></div></div>