<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://dev1galaxy.org/extern.php?action=feed&amp;tid=6461&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / my snaoshot Devuan Crown 64 bit: testing or ceres? libsystemd0]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=6461</link>
		<description><![CDATA[The most recent posts in my snaoshot Devuan Crown 64 bit: testing or ceres? libsystemd0.]]></description>
		<lastBuildDate>Tue, 26 Mar 2024 22:09:04 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: my snaoshot Devuan Crown 64 bit: testing or ceres? libsystemd0]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=49189#p49189</link>
			<description><![CDATA[<p>I did meet a simple answer:</p><p>all installations frontend&#039;s for Debian are not really equivalent. In&#160; graphic mode, prefer synaptic!</p><p>I, myself, I use better apt because you can redirect the apt output to a file and compare it with other days later! I don&#039;t know how to redirect and archive the output of synaptic. but synaptic avoid some installations problems.</p><p>but I did have today the experience, it can be the opposite also! If synaptic refuses, you can try apt or aptitude...</p><p>for synaptic, libsystemd0 seems to be no problem and after the use you never more hear somewhat from this ugly component!</p><p>in very tricky situations, dpkg can also help... the problem: you have a lot to learn if you want to use it so...</p>]]></description>
			<author><![CDATA[dummy@example.com (oui)]]></author>
			<pubDate>Tue, 26 Mar 2024 22:09:04 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=49189#p49189</guid>
		</item>
		<item>
			<title><![CDATA[Re: my snaoshot Devuan Crown 64 bit: testing or ceres? libsystemd0]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=49180#p49180</link>
			<description><![CDATA[<p>Even if that&#039;s a bit late: Purge libelogind-compat and do a dist-upgrade again. You&#039;ll find some more gotchas while upgrading to ceres - I just went through that the last days, too.</p>]]></description>
			<author><![CDATA[dummy@example.com (samhain)]]></author>
			<pubDate>Tue, 26 Mar 2024 19:04:15 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=49180#p49180</guid>
		</item>
		<item>
			<title><![CDATA[Re: my snaoshot Devuan Crown 64 bit: testing or ceres? libsystemd0]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=48614#p48614</link>
			<description><![CDATA[<p>I ran into this problem yesterday while trying to do an upgrade of a ceres install.&#160; This is my daily driver so it gets updated almost daily.&#160; Therefore it was current to within a one to two day period.&#160; When trying to do an apt upgrade I get this:</p><div class="quotebox"><blockquote><div><p>The following packages have unmet dependencies:<br /> libelogind-compat : Conflicts: libsystemd0<br />E: Broken packages</p></div></blockquote></div><p>If I try to do an apt dist-upgrade, I get this:</p><div class="quotebox"><blockquote><div><p>The following packages have unmet dependencies:<br /> libegl1 : Depends: libegl-mesa0 but it is not going to be installed<br /> libgnutls-dane0 : Depends: libgnutls30 (= 3.8.3-1)<br />E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.</p></div></blockquote></div><p>There are no held packages.&#160; The command &quot;apt-mark showhold&quot; produces no output, and there are no locked packages in synaptic as I do not use synaptic in ceres.</p><p>I know there was a lot of work done in the past to eliminate libsystemd0 from our system and I wonder if something new is trying to pull it back in?</p><p><em>Edit: added the held package information.</em></p>]]></description>
			<author><![CDATA[dummy@example.com (nixer)]]></author>
			<pubDate>Sat, 02 Mar 2024 11:34:29 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=48614#p48614</guid>
		</item>
		<item>
			<title><![CDATA[my snaoshot Devuan Crown 64 bit: testing or ceres? libsystemd0]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=48611#p48611</link>
			<description><![CDATA[<p>I&#160; did have last year a valid snapshot from me Devuan Crown 64 bit Ceres (was at the time where Daedalus was testing). And the ugly story with the new kernels did happen.</p><p>I did now &quot;convert&quot; it as I do since years. It is about the same as my snapshot Devian Star 32 bit&#160; from the parallel thread.</p><p>But nothing to do, the last step is not possible</p><p>because somewhat in relation with</p><p>libsystemd0 !</p><p>at Devuan...</p><p>The rest of my snapshot seems to be ok! It would give an image with a size of about 2 GB with comparable stuff but 64 bit, and, over that (not available in 32 bit at all) ANDBOX!</p><p>What is to do?</p><div class="quotebox"><blockquote><div><p>$ sudo apt upgrade<br />Reading package lists... Done<br />Building dependency tree... Done<br />Reading state information... Done<br />Calculating upgrade... Done<br />Some packages could not be installed. This may mean that you have<br />requested an impossible situation or if you are using the unstable<br />distribution that some required packages have not yet been created<br />or been moved out of Incoming.<br />The following information may help to resolve the situation:</p><p>The following packages have unmet dependencies:<br /> libelogind-compat : Conflicts: libsystemd0<br />E: Broken package</p></div></blockquote></div>]]></description>
			<author><![CDATA[dummy@example.com (oui)]]></author>
			<pubDate>Sat, 02 Mar 2024 10:12:24 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=48611#p48611</guid>
		</item>
	</channel>
</rss>
