<?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=6065&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Obsolete packages in Raspberry Pi image]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=6065</link>
		<description><![CDATA[The most recent posts in Obsolete packages in Raspberry Pi image.]]></description>
		<lastBuildDate>Sat, 14 Oct 2023 10:18:36 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: Obsolete packages in Raspberry Pi image]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=44876#p44876</link>
			<description><![CDATA[<p>Just FYI: I&#039;ve installed Debian OS image <a href="https://raspi.debian.net/tested/20230612_raspi_3_bookworm.img.xz" rel="nofollow">https://raspi.debian.net/tested/2023061 … orm.img.xz</a> and it has no obsolete packages.</p><p>After the first boot, I successfully updated all the packages, including Linux kernel:</p><div class="codebox"><pre><code>root@rpi3-20230612:~# uname -a
Linux rpi3-20230612 6.1.0-9-arm64 #1 SMP Debian 6.1.27-1 (2023-05-08) aarch64 GNU/Linux</code></pre></div><div class="codebox"><pre><code>root@rpi3-20230612:~# apt-get -V --no-install-recommends dist-upgrade
…
The following NEW packages will be installed:
   linux-image-6.1.0-13-arm64 (6.1.55-1)
The following packages will be upgraded:
   base-files (12.4 =&gt; 12.4+deb12u2)
…
   linux-image-arm64 (6.1.27-1 =&gt; 6.1.55-1)</code></pre></div><p>After reboot:</p><div class="codebox"><pre><code>root@rpi3-20230612:~# uname -a
Linux rpi3-20230612 6.1.0-13-arm64 #1 SMP Debian 6.1.55-1 (2023-09-29) aarch64 GNU/Linux</code></pre></div><div class="codebox"><pre><code>root@rpi3-20230612:~# apt-cache policy linux-image-6.1.0-13-arm64
linux-image-6.1.0-13-arm64:
  Installed: 6.1.55-1
  Candidate: 6.1.55-1
  Version table:
 *** 6.1.55-1 500
        500 http://deb.debian.org/debian bookworm/main arm64 Packages
        100 /var/lib/dpkg/status</code></pre></div><p>Firmware packages:</p><div class="codebox"><pre><code>root@rpi3-20230612:~# dpkg -l|grep -i firmware
ii  bluez-firmware               1.2-9                  all          Firmware for Bluetooth devices
ii  firmware-brcm80211           20230210-5             all          Binary firmware for Broadcom/Cypress 802.11 wireless cards
ii  firmware-linux-free          20200122-1             all          Binary firmware for various drivers in the Linux kernel
ii  raspi-firmware               1.20220830+ds-1        all          Raspberry Pi family GPU firmware and bootloaders</code></pre></div><p>Their <span class="bbc">/etc/apt/sources.list</span> is</p><div class="codebox"><pre><code>deb http://deb.debian.org/debian bookworm main non-free-firmware non-free
deb http://deb.debian.org/debian bookworm-updates main non-free-firmware non-free
deb http://security.debian.org/debian-security bookworm-security main non-free-firmware non-free
# Backports are _not_ enabled by default.
# Enable them by uncommenting the following line:
# deb http://deb.debian.org/debian bookworm-backports main non-free-firmware</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (vazhnov)]]></author>
			<pubDate>Sat, 14 Oct 2023 10:18:36 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=44876#p44876</guid>
		</item>
		<item>
			<title><![CDATA[Re: Obsolete packages in Raspberry Pi image]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=44843#p44843</link>
			<description><![CDATA[<p>Thanks also for the additional insights on <strong>eeprom</strong>, <strong>pi-bluetooth</strong> and <strong>sys-mods</strong>, c0rnelius, they are appreciated.</p>]]></description>
			<author><![CDATA[dummy@example.com (ExposeGlobalistsMadness)]]></author>
			<pubDate>Thu, 12 Oct 2023 04:18:10 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=44843#p44843</guid>
		</item>
		<item>
			<title><![CDATA[Re: Obsolete packages in Raspberry Pi image]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=44841#p44841</link>
			<description><![CDATA[<p>The kernel can be updated if you build it ur self using the github repo. There is also a deb-eeprom script on the pi4 images that can be used to update the eeprom package. Warning: I no longer have a Pi4, so I have no idea how well it works anymore and honestly I&#039;m sure the script needs to be updated and made easier to use.</p><p>As for pi-bluetooth and sys-mods. There isn&#039;t much to do there, as they are basically just debs that install scripts and udev rules and such.</p>]]></description>
			<author><![CDATA[dummy@example.com (c0rnelius)]]></author>
			<pubDate>Wed, 11 Oct 2023 20:05:43 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=44841#p44841</guid>
		</item>
		<item>
			<title><![CDATA[Re: Obsolete packages in Raspberry Pi image]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=44840#p44840</link>
			<description><![CDATA[<p><a href="https://dev1galaxy.org/profile.php?id=5980" rel="nofollow">c0rnelius</a> c0rnelius, thank you for links!</p><p>So, these Raspberry PI builds doesn&#039;t have possibility to update these custom-made packages automatically (as other packages, with <span class="bbc">apt</span>). Sad. I think this should be described somewhere in chapter &quot;Known issues&quot;.</p>]]></description>
			<author><![CDATA[dummy@example.com (vazhnov)]]></author>
			<pubDate>Wed, 11 Oct 2023 19:51:42 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=44840#p44840</guid>
		</item>
		<item>
			<title><![CDATA[Re: Obsolete packages in Raspberry Pi image]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=44839#p44839</link>
			<description><![CDATA[<p>It&#039;s a community build. The packages aren&#039;t obsolete, but custom made. Meaning, they aren&#039;t officially supported.</p><p>Source; <a href="https://github.com/pyavitz/rpi-img-builder" rel="nofollow">https://github.com/pyavitz/rpi-img-builder</a><br />Devuan fork; <a href="https://github.com/dyne/rpi-img-builder" rel="nofollow">https://github.com/dyne/rpi-img-builder</a></p>]]></description>
			<author><![CDATA[dummy@example.com (c0rnelius)]]></author>
			<pubDate>Wed, 11 Oct 2023 17:08:26 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=44839#p44839</guid>
		</item>
		<item>
			<title><![CDATA[Re: Obsolete packages in Raspberry Pi image]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=44816#p44816</link>
			<description><![CDATA[<p>1. I too have obsoleted packages, all pi-specific, having also installed one of the arm64 .zip images for Daedalus recently (an <span class="bbc">rpi-4-devuan-daedalus .... .zip</span> for my Pi 400:</p><div class="codebox"><pre><code>$ apt list &#039;?obsolete&#039;
Listing... Done
linux-headers-bcm2711-rpi-4/now 6.1.54-1 arm64 [installed,local]
linux-image-bcm2711-rpi-4/now 6.1.54-1 arm64 [installed,local]
pi-bluetooth/now 0.1.13 all [installed,local]
raspberrypi-sys-mods/now 20220224 arm64 [installed,local]
rpi-eeprom-images/now 16.1-1 arm64 [installed,local]
rpi-eeprom/now 16.1-1 arm64 [installed,local]</code></pre></div><p>Yet I do not recall instructing any specific pi packages to be upgraded unless it was part of the proposed apt updates/upgrades.</p><p>I noted earlier, at about the time that some linux headers didn&#039;t install/upgrade (although I can&#039;t remember whether it was during my previous installation --an attempted upgrade from Devuan Chimaera to Daedalus or during this Daedalus zip installation) that there were one or more failures reported with the <strong>initramfs</strong>, including at reboot.&#160; So perhaps these images or upgrades don&#039;t work fully automatically for Pis?&#160; There is no <span class="bbc">/boot/cmdline.txt</span> at present in my <span class="bbc">/boot</span> directory, somehow;&#160; a line in that file is perhaps akin to the <a href="https://raspberrytips.com/raspberry-pi-cmdline-txt/" rel="nofollow">kernel line</a> in non-Raspberry Linux systems.&#160; Yet that <span class="bbc">cmdline.txt</span> has been useful in part to get <strong>apparmor</strong> activated in the previous installation, when the file was present (adding&#160; lsm=&quot;apparmor&quot; in that file, as indicated <a href="https://github.com/raspberrypi/linux/commit/ceea6dc03e90c230495227eb6f267ad1dd388730" rel="nofollow">elsewhere</a>).&#160; Maybe, in part, if the <span class="bbc">cmdline.txt</span> were present, perhaps the initramfs would help to avoid obsoleted linux-header packages?&#160; </p><p>2. Do you need the backports line in the <span class="bbc">sources.list</span>?&#160; I wonder if that is also impeding some from packages from getting upgraded;&#160; I thought I had read that the backports repo is a more recent addition to the stable Daedalus release.&#160; I suppose however that you might have had to instruct <em>apt</em> to use a backport for some specific packages, anyway --it&#039;s just a thought.&#160; </p><p>Could anyone else chime in to help <a href="https://dev1galaxy.org/profile.php?id=2" rel="nofollow">vazhnov</a>, please?&#160; Thank you.</p>]]></description>
			<author><![CDATA[dummy@example.com (ExposeGlobalistsMadness)]]></author>
			<pubDate>Tue, 10 Oct 2023 22:14:09 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=44816#p44816</guid>
		</item>
		<item>
			<title><![CDATA[Obsolete packages in Raspberry Pi image]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=44811#p44811</link>
			<description><![CDATA[<p>Hello!</p><p>I&#039;ve downloaded an image <a href="https://arm-files.devuan.org/RaspberryPi%20Latest%20Builds/rpi-3-devuan-daedalus-6.1.54-arm64-ext4-2023-10-02-0243.zip" rel="nofollow">https://arm-files.devuan.org/RaspberryP … 2-0243.zip</a> and installed it. It works fine, but I see 3 obsolete packages:</p><div class="codebox"><pre><code>root@devuanpi:~# apt list &#039;?obsolete&#039;
Listing... Done
linux-headers-bcm2710-rpi-3/now 6.1.54-1 arm64 [installed,local]
linux-image-bcm2710-rpi-3/now 6.1.54-1 arm64 [installed,local]
raspberrypi-sys-mods/now 20220224 arm64 [installed,local]

root@devuanpi:~# apt-cache policy linux-image-bcm2710-rpi-3
linux-image-bcm2710-rpi-3:
  Installed: 6.1.54-1
  Candidate: 6.1.54-1
  Version table:
 *** 6.1.54-1 100
        100 /var/lib/dpkg/status
…</code></pre></div><p>The sources file <span class="bbc">/etc/apt/sources.list</span> was:</p><div class="codebox"><pre><code>deb http://deb.devuan.org/merged daedalus main contrib non-free non-free-firmware</code></pre></div><p>I replaced it with</p><div class="codebox"><pre><code>deb http://pl.deb.devuan.org/merged daedalus main contrib non-free non-free-firmware
deb http://pl.deb.devuan.org/merged daedalus-updates main contrib non-free non-free-firmware
deb http://pl.deb.devuan.org/merged daedalus-security main contrib non-free non-free-firmware
deb http://pl.deb.devuan.org/merged daedalus-backports main contrib non-free non-free-firmware</code></pre></div><p>but still the same — 3 obsolete packages.</p><p>I&#039;m afraid they will never be updated.</p><p>Is there any way to add an official repository for them?</p><p>Also, where can I found script/pipeline which creates these images? could you please add this information into <a href="https://arm-files.devuan.org/README.txt" rel="nofollow">https://arm-files.devuan.org/README.txt</a>?</p>]]></description>
			<author><![CDATA[dummy@example.com (vazhnov)]]></author>
			<pubDate>Tue, 10 Oct 2023 18:54:10 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=44811#p44811</guid>
		</item>
	</channel>
</rss>
