<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=7805&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / mythTv - compatibility devuan]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=7805</link>
		<description><![CDATA[The most recent posts in mythTv - compatibility devuan.]]></description>
		<lastBuildDate>Sun, 07 Jun 2026 23:16:07 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: mythTv - compatibility devuan]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=64194#p64194</link>
			<description><![CDATA[<p>260607<br />I have successfully compiled MythTV .deb packages on Devuan and have run<br /> mythfrontend for a couple of weeks with no issues. I have not installed <br /> a MythTV backend, and have no intentions to do so at this time.</p><p>Below is my experience. Any errors/omissions are solely mine. What, if<br /> anything one does with this information is on them. I do everything from a<br /> terminal.</p><p>A second experiment is listed under &#039;SYSTEMD&#039; below. Other than some add-on<br /> expected breakages, other issues are unknown. With the listed changes, the<br /> .deb packages were compiled, but not installed by me. I make absolutely no<br /> guarantee as to what might happen with your machine if you try this <br /> second experiment (or the first experiment for that matter).</p><p>Suggest a backup be made before proceeding. Have another means of booting your<br /> computer should something go wrong. Try not to do this on a production<br /> computer.<br />...</p><p>Environment: Devuan Excalibur with only the default repositories enabled and<br /> used. Work was done within the XFCE environment.</p><p>Instructions for compiling MythTV on Debian from mythtv.org are assumed, and<br />only changes I made are noted here.<br /><a href="https://wiki.mythtv.org/wiki/Installing_MythTV_on_Debian" rel="nofollow">https://wiki.mythtv.org/wiki/Installing … _on_Debian</a><br />last edited &quot;3 May 2026&quot;</p><p>Problem: error below returned and compile halted.<br /> conflict between libsystemd0 and ...elogin...</p><p>I ran:</p><div class="codebox"><pre><code>`DEBIAN_SUFFIX=&#039;devuan&#039; ./build-debs.sh fixes/36`</code></pre></div><p>&#160; &#160;Note: this will include &#039;devuan&#039; in the package names. I suggest adding your<br />&#160; &#160;initials as well (Ex. devuanABC).</p><p>build-debs.sh runs `dpkg-checkbuilddeps` against debian/control. A &#039;zero&#039;<br /> return indicates all dependencies are met. We can run the above manually from<br /> the directory we executed `build-debs.sh`</p><div class="codebox"><pre><code>dpkg-checkbuilddeps</code></pre></div><p>dpkg-checkbuilddeps: error: unmet build dependencies: build-essential:native ccache default-libmysqlclient-dev | libmysqlclient-dev <br />...</p><p>For me, lower down in this list is &#039;libsystemd-dev&#039;. I manually installed<br /> files listed above as user &#039;root&#039; or with `sudo` in several steps until <br /> libsystemd-dev was about the only unmet dependency left. <br />Note that the &#039;|&#039; in the output means to install either the .deb left of<br /> the &#039;|&#039; or the .deb package right of &#039;|&#039;</p><p>I made a list of installed .deb packages to help with this task.</p><div class="codebox"><pre><code>dpkg-query -l &gt; myinstalled.debs.txt</code></pre></div><p>I can for instance run: `grep libmysqlclient myinstalled.debs.txt`<br />Note the &#039;-dev&#039; is omitted in the search.</p><p>For &#039;-dev&#039; dependencies needed, this might tell you which &#039;-dev&#039; packages you<br /> need. If nothing is returned, you can try to install both, and `apt` will<br /> complain about one .deb not being found. Remove that .deb package from your<br /> &#039;apt install&#039; command and try again. This is the main reason I install<br /> dependencies slowly and resolve libsystemd-dev last; it avoids confusion.</p><p>I ran:</p><div class="codebox"><pre><code>apt install libsystemd-dev</code></pre></div><p>...<br />Installing:<br />&#160; libsystemd-dev</p><p>Installing dependencies:<br />&#160; dummy-logind&#160; libcap-dev&#160; libsystemd0</p><p>REMOVING:<br />&#160; desktop-base&#160; libelogind-compat&#160; libpam-elogind&#160; task-desktop&#160; task-xfce-desktop</p><p>preceeded by over one hundred packages that were &#039;no longer required&#039;. Note that<br /> *desktop* files are minimal .deb packages that install other .deb packages.<br />Removing, for instance, task-xfce-desktop does not delete the XFCE desktop.</p><p>Note the .deb packages listed below &#039;Installing:&#039;, &#039;Installing dependencies:&#039;, and<br /> &#039;REMOVING:&#039; as these changes will be later reversed.</p><p>I accepted install of libsystemd-dev. Do not log out or reboot once<br /> libsystemd-dev is installed.</p><p>I ran `dpkg-checkbuilddeps` until its only output was a prompt return.</p><p>Now we are ready to retry the ./build-debs.sh command (See above).<br />This command successfully created .deb packages in the packaging/deb/<br /> directory.</p><p>Follow the MythTV instructions for creating a repository listing and install<br /> you desired packages. Note MythTV urges ...mythtv.list should be removed<br /> once the packages are installed.</p><p>Reverse the changes we made to allow MythTV to compile. In my case:</p><div class="codebox"><pre><code>apt install desktop-base  libelogind-compat  libpam-elogind  task-desktop \
 task-xfce-desktop</code></pre></div><p>REMOVING:<br />&#160; dummy-logind&#160; libsystemd-dev&#160; libsystemd0</p><p>I accepted this change, to revert changes to the computer made earlier.<br />-----</p><p>I ran:</p><div class="codebox"><pre><code>apt install mythtv-frontend</code></pre></div><p>(my MythTV backend runs on a systemd enabled operating system at this time).</p><p>When I first ran `mythfrontend`, it complained that the user did not have<br /> &#039;mythtv&#039; in the user&#039;s groups listing. Following the prompting of the <br /> pop-up window, this was attempted, but failed. The complaint was not <br /> being able to run `systemctl daemon-reload`. I had to manually add &#039;mythtv&#039;<br /> to the users group (Ex. usermod -a -G mythtv myuser # subbing for myuser), <br /> then log out for the change to be committed.</p><p>Done!<br />-----<br />SYSTEMD<br />I ran:</p><div class="codebox"><pre><code>grep systemd packaging/deb/mythtv/mythtv/configure</code></pre></div><p>and it listed:<br />--disable-systemd_notify <br />--disable-systemd_journal</p><p>as possible inputs to the configure script. These can be added to<br />&#039;packaging/deb/debian/rules&#039; before beginning the compile (backup the<br />&#039;rules&#039; file before changing).</p><p>Searching the &#039;control&#039; file, there are two mentions of systemd:<br />libsystemd-dev&#160; is within the base &#039;Build-Depends:&#039;<br />python3-systemd is within &#039;Package: libmyth-python&#039;<br /> &quot;This package contains files needed for some python MythTV add-ons.&quot;</p><p>So can we not build the libmyth-python package and accept loss of some MythTV<br /> add-ons? Can we simply remove &#039;libsystemd-dev&#039; as a dependency?<br /> &#039;libmyth-python&#039; is listed as a dependency of &#039;Package: mythtv-frontend&#039;<br />Lets try it!!</p><p>Backup the control file. Within the &#039;control&#039; file:<br />Delete the &#039;libsystemd-dev&#039; dependency<br />Delete the &#039;Package: libmyth-python&#039; section (we have made a backup!)<br />Delete &#039;libmyth-python&#039; dependency within &#039;Package: mythtv-frontend&#039;<br /> and &#039;Package: mythtv-backend&#039;</p><p>Run `build-debs.sh` as indicated above</p><p>The compile ran to completion and created .deb packages. As expected,<br />a &#039;libmyth-python&#039; .deb package was not created. I have not installed this<br /> compile, and will not install at this time. </p><p>-----</p><p>MythTV seems tied to systemd (at least weakly). I intent to file a feature<br /> request to add a &#039;--disable-systemd&#039; to the `configure` script and see if the<br /> MythTV developers deem this something worth their time to pursue.</p><p>If the feature is accepted, I will test and report back on this post.</p>]]></description>
			<author><![CDATA[dummy@example.com (royboy626)]]></author>
			<pubDate>Sun, 07 Jun 2026 23:16:07 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=64194#p64194</guid>
		</item>
		<item>
			<title><![CDATA[mythTv - compatibility devuan]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=62126#p62126</link>
			<description><![CDATA[<p>Hello ,</p><p>since long wanted to test this software but never came quite to it</p><p>now had opportunity to try on workstation, but it seems there is a difficulty in &quot;build deps&quot;</p><p><a href="https://wiki.mythtv.org/wiki/Installing_MythTV_on_Debian" rel="nofollow">https://wiki.mythtv.org/wiki/Installing … _on_Debian</a></p><p>error is with version 36 when compiling build-debs</p><div class="codebox"><pre><code>./build-debs.sh fixes/36 </code></pre></div><div class="quotebox"><blockquote><div><p>not satisfied dependencies &gt; libelogind-compat is in conflct with: libsystemd0</p></div></blockquote></div><p>maybe you can tell how to overcome the error,</p><p>thanks.</p>]]></description>
			<author><![CDATA[dummy@example.com (kapqa)]]></author>
			<pubDate>Fri, 13 Feb 2026 12:30:01 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=62126#p62126</guid>
		</item>
	</channel>
</rss>
