<?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=2467&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / wrong dbus after migration from stretch ?]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=2467</link>
		<description><![CDATA[The most recent posts in wrong dbus after migration from stretch ?.]]></description>
		<lastBuildDate>Mon, 05 Nov 2018 11:50:43 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[wrong dbus after migration from stretch ?]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=12647#p12647</link>
			<description><![CDATA[<p>Hi,<br />&#160; &#160; just some feedback after migrating from debian stretch.</p><p>After the upgrade, I found that I still had the debian version of dbus (plus libdbus and dbus-x11) installed,<br />despite devuan replacements being available. (IIRC this was manifesting as problems with xserver<br />trying to access a system login service or something.)</p><p>The installed one was 1.10.24 (I think) which the system presumably decided to preserve rather than<br />using the devuan 1.10.22 versions. (I see that debian stretch now offers 1.10.26 - it had probably been<br />a while since I had updated stretch prior to the migration.)</p><p>Forcibly installing the 3 packages at the devuan revision numbers downgraded them.</p><p>I see that bug #95 was a similar problem a while back.&#160; Perhaps the newer version is already<br />in a queue to get added to ascii.</p>]]></description>
			<author><![CDATA[dummy@example.com (divenal)]]></author>
			<pubDate>Mon, 05 Nov 2018 11:50:43 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=12647#p12647</guid>
		</item>
	</channel>
</rss>
