<?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=7869&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [SOLVED] Trouble migrating from sid to ceres]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=7869</link>
		<description><![CDATA[The most recent posts in [SOLVED] Trouble migrating from sid to ceres.]]></description>
		<lastBuildDate>Sat, 28 Mar 2026 04:44:29 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: [SOLVED] Trouble migrating from sid to ceres]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=62920#p62920</link>
			<description><![CDATA[<p>Amprolla synchronizes repo versions bi-minutely, i.e. every 2 minutes. It also runs &quot;collections synchronization&quot; daily, and a major cleanup weekly.</p><p>Note that &quot;Devuan repositories&quot; comprise *meta files* only. It is those that &quot;define&quot; the Devuan repositories. They have the &quot;pointers&quot; (URLs) to the deb files that one install, and most debs are directly sourced from Debian&#039;s package pools.</p><p>The Devuan package pools have a comparatively small number of packages that replace and add to the Debian package pools. Those that are forks of same-named Debian packages are of course regularly behind their origins, since it takes developer effort to roll in origin updates.</p>]]></description>
			<author><![CDATA[dummy@example.com (ralph.ronnquist)]]></author>
			<pubDate>Sat, 28 Mar 2026 04:44:29 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=62920#p62920</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Trouble migrating from sid to ceres]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=62917#p62917</link>
			<description><![CDATA[<div class="quotebox"><blockquote><div><p>My understanding is that Amprolla (what makes Devuan&#039;s repositories) runs several hours behind Debian&#039;s servers.</p></div></blockquote></div><p>I figured it was something like that. Thanks!</p>]]></description>
			<author><![CDATA[dummy@example.com (JnvSor)]]></author>
			<pubDate>Fri, 27 Mar 2026 22:49:57 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=62917#p62917</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Trouble migrating from sid to ceres]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=62915#p62915</link>
			<description><![CDATA[<p>While Ceres isn&#039;t a &quot;real&quot; Devuan release, it is still the foundation of every new release. The more folks who use Ceres, the more they can help Devuan&#039;s developers and maintainers.</p><p>I don&#039;t track Ceres anymore (I switched it to Daedalus in early 2023 when it was in the testing freeze), but anytime I ran into an issue like that (i.e. unmet dependencies due to a package unavailability), waiting it out for up to a week usually solved the issue. My understanding is that Amprolla (what makes Devuan&#039;s repositories) runs several hours behind Debian&#039;s servers.</p>]]></description>
			<author><![CDATA[dummy@example.com (brocashelm)]]></author>
			<pubDate>Fri, 27 Mar 2026 21:17:40 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=62915#p62915</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Trouble migrating from sid to ceres]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=62914#p62914</link>
			<description><![CDATA[<p>FWIW . . . I have never heard of anyone trying to migrate from sid (Debian unstable) to ceres (Devuan unstable). sid and ceres are not &quot;releases&quot;. They are the &quot;unstable&quot; branches of their respective distributions.</p>]]></description>
			<author><![CDATA[dummy@example.com (golinux)]]></author>
			<pubDate>Fri, 27 Mar 2026 20:56:22 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=62914#p62914</guid>
		</item>
		<item>
			<title><![CDATA[[SOLVED] Trouble migrating from sid to ceres]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=62913#p62913</link>
			<description><![CDATA[<p>My daily driver is a long-running sid install I&#039;ve been putting off migrating for too long now. Following the installation steps I get a number of 404 errors. Seems some packages are missing and update and upgrade aren&#039;t in sync:</p><div class="codebox"><pre><code>E: Failed to fetch http://deb.devuan.org/merged/pool/DEBIAN/main/i/isl/libisl23_0.27-2_amd64.deb  404  Not Found [IP: 2001:638:a000:1021:21::1 80]
E: Failed to fetch http://deb.devuan.org/merged/pool/DEBIAN/main/m/mpfr4/libmpfr6_4.2.2-3_amd64.deb  404  Not Found [IP: 2001:638:a000:1021:21::1 80]
E: Failed to fetch http://deb.devuan.org/merged/pool/DEBIAN/main/m/mpclib3/libmpc3_1.3.1-3_amd64.deb  404  Not Found [IP: 2001:638:a000:1021:21::1 80]
E: Failed to fetch http://deb.devuan.org/merged/pool/DEBIAN/main/d/dwz/dwz_0.16-4_amd64.deb  404  Not Found [IP: 2001:638:a000:1021:21::1 80]
E: Failed to fetch http://deb.devuan.org/merged/pool/DEBIAN/main/libf/libffi/libffi-dev_3.5.2-4_amd64.deb  404  Not Found [IP: 2001:638:a000:1021:21::1 80]
E: Failed to fetch http://deb.devuan.org/merged/pool/DEBIAN/main/libf/libffi/libffi8_3.5.2-4_i386.deb  404  Not Found [IP: 2001:638:a000:1021:21::1 80]
E: Failed to fetch http://deb.devuan.org/merged/pool/DEBIAN/main/libf/libffi/libffi8_3.5.2-4_amd64.deb  404  Not Found [IP: 2001:638:a000:1021:21::1 80]
E: Failed to fetch http://deb.devuan.org/merged/pool/DEBIAN/main/g/gssdp/libgssdp-1.6-0_1.6.4-6_amd64.deb  404  Not Found [IP: 2001:638:a000:1021:21::1 80]</code></pre></div><p>A quick browse through the pool shows a version very close to this is in there for the first one, so I presume they&#039;ll just land in ceres after a delay. Is that correct or is there something I have to actually fix here?</p>]]></description>
			<author><![CDATA[dummy@example.com (JnvSor)]]></author>
			<pubDate>Fri, 27 Mar 2026 19:37:12 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=62913#p62913</guid>
		</item>
	</channel>
</rss>
