<?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=6509&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Dependency trees on pkginfo.devuan.org are unstable]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=6509</link>
		<description><![CDATA[The most recent posts in Dependency trees on pkginfo.devuan.org are unstable.]]></description>
		<lastBuildDate>Thu, 21 Mar 2024 19:36:03 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Dependency trees on pkginfo.devuan.org are unstable]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=49070#p49070</link>
			<description><![CDATA[<p>I noticed the debtree link for Chimaera and Daedalus packages go to the same page, even when there are differing dependencies.</p><p>Looking at the <a href="https://manpages.debian.org/bookworm/debtree/debtree.1.en.html" rel="nofollow">debtree</a> man page, I&#039;m guessing this is a limitation of that software:</p><div class="quotebox"><cite>man debtree wrote:</cite><blockquote><div><p>If multiple versions of a package are available, the dependency information for the highest available version will be used</p></div></blockquote></div><p>Which, given the way pkginfo.devuan.org is setup, suggests that the debtree is always going to represent the newest packages - i.e. whatever is in Ceres/unstable - and checking (e.g.) <a href="https://pkginfo.devuan.org/xserver-xorg-core" rel="nofollow">xserver-xorg-core</a> confirms this to be the case.</p><p>I&#039;m assuming that resolving this would be non-trivial, but it should be easy enough to add a suitable clarification to the output generated by the debtree-query.html script?</p>]]></description>
			<author><![CDATA[dummy@example.com (boughtonp)]]></author>
			<pubDate>Thu, 21 Mar 2024 19:36:03 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=49070#p49070</guid>
		</item>
	</channel>
</rss>
