<?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=7481&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [SOLVED] apt problem - cannot update upower package to newer version]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=7481</link>
		<description><![CDATA[The most recent posts in [SOLVED] apt problem - cannot update upower package to newer version.]]></description>
		<lastBuildDate>Fri, 24 Oct 2025 01:04:28 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: [SOLVED] apt problem - cannot update upower package to newer version]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=58758#p58758</link>
			<description><![CDATA[<p>thanks @fsmithred, your recommendation worked! providing the release name to apt-install did the trick.</p><p>i guess apt got confused by the package numbering. the old ascii package was modified by devuan, so had a different (greater?) version string than the new, un-modified daedalus package.</p><p>and, yes, apt DID consider it a downgrade.</p><p>thanks @RedGreen925 for explaining what the &#039;epoch&#039; colon is for.&#160; to elaborate on my intent here, i want to upgrade this vm to excalibur and the debian release notes suggests removing obsolete packages (section 4.9). did not expect to find any obsolete packages; was surprised to see that there was one. trying to remove it led me down this rabbit hole.</p><p>just for completeness, here is the install log. it shows that apt swaps out the obsolete libupower-glib1 for the current libupower-glib3 and downgrades upower to the current (newer) version:</p><div class="codebox"><pre class="vscroll"><code>&gt; sudo apt install upower/daedalus   
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version &#039;0.99.20-2&#039; (Devuan:5.0/stable [amd64]) for &#039;upower&#039;
The following packages were automatically installed and are no longer required:
  ethtool libdbus-glib-1-2 libupower-glib1 libx86-1 pm-utils vbetool
Use &#039;sudo apt autoremove&#039; to remove them.
The following additional packages will be installed:
  libupower-glib3
The following NEW packages will be installed:
  libupower-glib3
The following packages will be DOWNGRADED:
  upower
0 upgraded, 1 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
Need to get 118 kB of archives.
After this operation, 82.9 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://deb.devuan.org/merged daedalus/main amd64 libupower-glib3 amd64 0.99.20-2 [36.4 kB]
Get:2 http://deb.devuan.org/merged daedalus/main amd64 upower amd64 0.99.20-2 [81.2 kB]
Fetched 118 kB in 1s (146 kB/s)
Selecting previously unselected package libupower-glib3:amd64.
(Reading database ... 193098 files and directories currently installed.)
Preparing to unpack .../libupower-glib3_0.99.20-2_amd64.deb ...
Unpacking libupower-glib3:amd64 (0.99.20-2) ...
dpkg: warning: downgrading upower from 1:0.9.23-2+devuan1.3 to 0.99.20-2
Preparing to unpack .../upower_0.99.20-2_amd64.deb ...
Unpacking upower (0.99.20-2) over (1:0.9.23-2+devuan1.3) ...
Setting up libupower-glib3:amd64 (0.99.20-2) ...
Setting up upower (0.99.20-2) ...
Installing new version of config file /etc/UPower/UPower.conf ...
Processing triggers for dbus (1.14.10-1~deb12u1devuan1) ...
Processing triggers for eudev (3.2.12-4+deb12u1) ...
Processing triggers for libc-bin (2.36-9+deb12u13) ...
Processing triggers for man-db (2.11.2-2) ...</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (grunchy)]]></author>
			<pubDate>Fri, 24 Oct 2025 01:04:28 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=58758#p58758</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] apt problem - cannot update upower package to newer version]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=58757#p58757</link>
			<description><![CDATA[<p>We no longer fork upower. The version you have installed is for ascii. One or more of the following should work.</p><div class="codebox"><pre><code>apt install upower/daedalus</code></pre></div><p>If that doesn&#039;t work, download the deb package and install it with dpkg.</p><div class="codebox"><pre><code>apt download upower    #if you get the ascii version with this, then you need to remove ascii from sources.list or sources.list.d/

#you could also do this to download the right version:
apt download upower/daedalus

dpkg --force-downgrade -i upower_0.99.20-2_amd64.deb</code></pre></div><p>We all know it&#039;s not really a downgrade, but apt thinks the one with the epoch is newer.</p>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Fri, 24 Oct 2025 00:07:50 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=58757#p58757</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] apt problem - cannot update upower package to newer version]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=58756#p58756</link>
			<description><![CDATA[<div class="quotebox"><blockquote><div><p>i can&#039;t get apt to update from the obsolete libupower-glib1 to libupower-glib3, something is borked in this vm but not sure what. maybe the version &quot;number&quot; is confusing apt due to the presence of the colon?</p></div></blockquote></div><p>That is called an epoch in debian packaging terms it is used when there is a mis match in the package numbers. In addition your package you want to replace has a devuan in the name which means it has been edited by the maintainers to ensure it works on the system. Trying to replace it because you think you know better what packaging is needed than the people who put together the system is a bad idea. I have not seen one mention of why this replacement is needed by you other than it is outdated, on a system that is working properly with it installed at that version.</p><div class="quotebox"><blockquote><div><p>for kde, upower is a &#039;depends&#039; and not a &#039;recommends&#039; so it cannot be removed:<br />apt will remove the entire desktop when purging upower:</p></div></blockquote></div><p>It most certainly can be removed/purged without losing the KDE desktop.</p><div class="codebox"><pre><code>root@9600k:~# apt -s purge upower

The following package was automatically installed and is no longer required:
  libupower-glib3
Use &#039;apt autoremove&#039; to remove it.

REMOVING:
  upower*

Summary:
  Upgrading: 0, Installing: 0, Removing: 1, Not Upgrading: 0
Purg upower [1.90.9-5]</code></pre></div><div class="codebox"><pre class="vscroll"><code>root@9600k:~# apt policy plasma-desktop plasma-workspace kde-plasma-desktop kde-standard task-kde-desktop
plasma-desktop:
  Installed: 4:6.3.6-1
  Candidate: 4:6.3.6-1
  Version table:
 *** 4:6.3.6-1 990
        990 http://gnlug.org/pub/devuan/merged excalibur/main amd64 Packages
        100 /var/lib/dpkg/status
plasma-workspace:
  Installed: 4:6.3.6-2
  Candidate: 4:6.3.6-2
  Version table:
 *** 4:6.3.6-2 990
        990 http://gnlug.org/pub/devuan/merged excalibur/main amd64 Packages
        100 /var/lib/dpkg/status
kde-plasma-desktop:
  Installed: (none)
  Candidate: 5:162
  Version table:
     5:162 990
        990 http://gnlug.org/pub/devuan/merged excalibur/main amd64 Packages
kde-standard:
  Installed: (none)
  Candidate: 5:162
  Version table:
     5:162 990
        990 http://gnlug.org/pub/devuan/merged excalibur/main amd64 Packages
task-kde-desktop:
  Installed: (none)
  Candidate: 3.81devuan1
  Version table:
     3.81devuan1 990
        990 http://gnlug.org/pub/devuan/merged excalibur/main amd64 Packages</code></pre></div><p>What is going to be removed by your command is the meta packages which bring in the complete set of packages for those tasks. If it was removing all of them packages you would see hundreds of them being removed not the grand total of&#160; four it will remove with your simulation. In short your desktop would still be intact without them but without the upower being used. It is time to accept the people who put this system together know what they are doing with the version of the software they install on it to get and keep it running.</p>]]></description>
			<author><![CDATA[dummy@example.com (RedGreen925)]]></author>
			<pubDate>Thu, 23 Oct 2025 23:33:34 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=58756#p58756</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] apt problem - cannot update upower package to newer version]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=58754#p58754</link>
			<description><![CDATA[<p>Hello:</p><div class="quotebox"><cite>grunchy wrote:</cite><blockquote><div><p>thanks ...</p></div></blockquote></div><p>You&#039;re welcome</p><div class="quotebox"><cite>grunchy wrote:</cite><blockquote><div><p>... can&#039;t get apt to update from the obsolete libupower-glib1 ...</p></div></blockquote></div><p>I see ...<br />And if you try to purge it, it nukes the whole shebang.<br />A sticky wicket ...</p><p>Just an idea:<br />Since <span class="bbc">apt</span> will not (for whatever reason) update <span class="bbc">libupower-glib1</span>, you may want to try some other way to do it.</p><p>First check that your <span class="bbc">etc/apt/sources.list</span> file does not have anything but <span class="bbc">daedalus</span> repositories.&#160; <br />ie: sometimes shit <em>does</em> happen. 8^°</p><p>Then see if you can get around <span class="bbc">apt upgrade</span> not doing the job by resorting to <span class="bbc">apt install</span>: <br />eg:</p><div class="codebox"><pre><code>apt install -s libupower-glib3   # &lt;- simulation mode</code></pre></div><p>It may well replace the old version. (?) </p><p>Please let us know how you fared.<br />Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Thu, 23 Oct 2025 22:49:34 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=58754#p58754</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] apt problem - cannot update upower package to newer version]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=58753#p58753</link>
			<description><![CDATA[<p>thanks for the feedback @Altoid</p><p>yes, libupower-glib3 is the correct version. i can&#039;t get apt to update from the obsolete libupower-glib1 to libupower-glib3, something is borked in this vm but not sure what.</p><p>the version apt thinks is current is from ascii, at lease according to devuan package search:</p><div class="codebox"><pre><code>upower
1:0.99.4-4+devuan3
   http://archive.devuan.org/merged ascii-proposed-updates/main amd64
1:0.9.23-2+devuan1.3                                  ** OLD **
   http://archive.devuan.org/merged ascii/main amd64  ** OLD **
1:0.9.23-2+devuan1.2
   http://archive.devuan.org/merged jessie/main amd64
1.90.10-1
   http://deb.devuan.org/merged ceres/main amd64
1.90.9-1
   http://deb.devuan.org/merged excalibur/main amd64
0.99.20-2                                             ** NEW **
   http://deb.devuan.org/merged daedalus/main amd64   ** NEW **
0.99.11-2
   http://deb.devuan.org/merged chimaera/main amd64
0.99.10-1
   http://archive.devuan.org/merged beowulf/main amd64</code></pre></div><p>maybe the version &quot;number&quot; is confusing apt due to the presence of the colon?</p><div class="quotebox"><blockquote><div><p>Being a recommends and not a hard dependency, you probably don&#039;t need it.</p></div></blockquote></div><p>for kde, upower is a &#039;depends&#039; and not a &#039;recommends&#039; so it cannot be removed:</p><div class="codebox"><pre><code>&gt; aptitude why libupower-glib1
i   task-kde-desktop   Depends kde-standard
i A kde-standard       Depends kde-plasma-desktop (&gt;= 5:142)
i A kde-plasma-desktop Depends upower
i A upower             Depends libupower-glib1 (&gt;= 0.9.2)</code></pre></div><p>apt will remove the entire desktop when purging upower:</p><div class="codebox"><pre><code>&gt; apt -s purge upower
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don&#039;t depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  espeak-ng-data ethtool festival festival-freebsoft-utils festlex-cmu festlex-poslex festvox-kallpc16k gir1.2-atspi-2.0
  gir1.2-gstreamer-1.0 gir1.2-wnck-3.0 kdeaccessibility kmag kmousetool kmouth kontrast libatk-adaptor libbrlapi0.8
  libdbus-glib-1-2 libdotconf0 libespeak-ng1 libestools2.5 libpcaudio0 libqt5opengl5 libreoffice-help-common
  libreoffice-help-en-us libreoffice-kf5 libreoffice-plasma libreoffice-qt5 libsonic0 libspeechd2 libstartup-notification0
  libupower-glib1 libwnck-3-0 libwnck-3-common libx86-1 node-clipboard node-normalize.css node-prismjs orca perl-tk
  pm-utils print-manager python3-brlapi python3-louis python3-pyatspi python3-speechd python3-xdg qtgstreamer-plugins-qt5
  sound-icons speech-dispatcher speech-dispatcher-audio-plugins speech-dispatcher-espeak-ng speech-dispatcher-festival
  vbetool xbrlapi xkbset
Use &#039;apt autoremove&#039; to remove them.
The following packages will be REMOVED:
  kde-plasma-desktop* kde-standard* task-kde-desktop* upower*
0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
Purg task-kde-desktop [3.73devuan1]
Purg kde-standard [5:142]
Purg kde-plasma-desktop [5:142]
Purg upower [1:0.9.23-2+devuan1.3]</code></pre></div><p>i&#039;ll keep digging. the apt-get man page has nothing about debugging it&#039;s behavior, so i guess that is not possible :-(</p>]]></description>
			<author><![CDATA[dummy@example.com (grunchy)]]></author>
			<pubDate>Thu, 23 Oct 2025 22:14:05 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=58753#p58753</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] apt problem - cannot update upower package to newer version]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=58751#p58751</link>
			<description><![CDATA[<p>Hello:</p><div class="quotebox"><cite>grunchy wrote:</cite><blockquote><div><p>my daedalus vm has been upgraded since ascii.</p></div></blockquote></div><p>Same for my Daedalus installation with the exception of it not being a VM.</p><div class="codebox"><pre><code>$ uname -a
Linux devuan 6.1.0-40-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.153-1 (2025-09-20) x86_64 GNU/Linux
$ </code></pre></div><div class="quotebox"><cite>grunchy wrote:</cite><blockquote><div><p>... checked for obsolete packages ...</p></div></blockquote></div><p>For whatever reason, I have quite a few of those packages ...</p><div class="codebox"><pre><code>$ apt list &#039;~o&#039; 
--- snip ---
libssl1.1/now 1.1.1w-0+deb11u1 amd64 [installed,local]
libswresample3/now 7:4.3.6-0+deb11u1 amd64 [installed,local]
######  &lt;--- would have been listed here
libvpx6/now 1.9.0-1+deb11u2 amd64 [installed,local]
libwebp6/now 0.6.1-2.1+deb11u2 amd64 [installed,local]
--- snip ---
$ </code></pre></div><p>...&#160; but <span class="bbc">libupower-glib1</span> is not one of them.</p><div class="codebox"><pre><code>$ apt list &#039;~o&#039; | grep libupower-glib1
--- snip ---
$ </code></pre></div><p>That said, I <span class="bbu">do</span> have <span class="bbc">libupower-glib3</span> installed ...</p><div class="codebox"><pre><code>$ apt list | grep installed | grep libupower
--- snip ---
libupower-glib3/stable,now 0.99.20-2 amd64 [installed,automatic]
$ </code></pre></div><div class="codebox"><pre><code>$ aptitude why libupower-glib3
i   task-desktop   Depends    xorg                                                              
i A xorg           Depends    xinit                                                             
i A xinit          Recommends xterm | x-session-manager | x-window-manager | x-terminal-emulator
i A xfce4-session  Provides   x-session-manager                                                 
i A xfce4-session  Depends    xfce4-settings                                                    
i A xfce4-settings Depends    libupower-glib3 (&gt;= 0.99.0)                                       
$ </code></pre></div><p>... but no <span class="bbc">upower</span>:</p><div class="codebox"><pre><code>$ apt list | grep installed | grep upower
--- snip ---
libcpupower1/stable-security,now 6.1.153-1 amd64 [installed,automatic]
libupower-glib3/stable,now 0.99.20-2 amd64 [installed,automatic]
linux-cpupower/stable-security,now 6.1.153-1 amd64 [installed]
$ </code></pre></div><div class="codebox"><pre><code>$ apt-cache policy upower
upower:
  Installed: (none)
  Candidate: 0.99.20-2
  Version table:
     0.99.20-2 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages
$ </code></pre></div><p>That <span class="bbc">upower</span> package is a recommends from the <span class="bbc">hw-probe</span> package which I do have installed ...</p><div class="codebox"><pre><code>$ apt list | grep installed | grep hw-probe
--- snip ---
hw-probe/stable,stable,now 1.6.5-1 all [installed]
$ </code></pre></div><div class="codebox"><pre><code>$ aptitude why upower
i   hw-probe Recommends upower
$ </code></pre></div><p>... but I do not allow recommends in my system.</p><p>Unless I am mistaken, your &#039;Installed&#039; version is the same as your &#039;Candidate&#039; version:<br />ie: <span class="bbc">apt</span> says that is the <span class="bbu">correct</span> version to have in your system.</p><div class="codebox"><pre><code>Installed: 1:0.9.23-2+devuan1.3
Candidate: 1:0.9.23-2+devuan1.3</code></pre></div><p>Being a recommends and not a hard dependency, you probably don&#039;t need it.<br />You may want to try purging the <span class="bbc">upower</span> package and see if the obsolete package gets purged along with it.</p><p>Then if you get complaints from the system, just reinstall it and see what gets dragged in along with it.</p><p>Please let us know how you fared.</p><p>Best,</p><p>A.</p>]]></description>
			<author><![CDATA[dummy@example.com (Altoid)]]></author>
			<pubDate>Thu, 23 Oct 2025 12:50:59 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=58751#p58751</guid>
		</item>
		<item>
			<title><![CDATA[[SOLVED] apt problem - cannot update upower package to newer version]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=58747#p58747</link>
			<description><![CDATA[<p>my daedalus vm has been upgraded since ascii.</p><p>i just checked for obsolete packages with &quot;apt list &#039;~o&#039;&quot; and libupower-glib1 is the only obsolete package installed.</p><p>checking further, i see that libupower-glib1 cannot be upgraded to libupower-glib3 as it is depended on by package upower.</p><p>according to apt-cache, the version of upower currently installed is old and a newer version is available:</p><div class="codebox"><pre><code>&gt; apt-cache policy upower
upower:
  Installed: 1:0.9.23-2+devuan1.3
  Candidate: 1:0.9.23-2+devuan1.3
  Version table:
 *** 1:0.9.23-2+devuan1.3 100
        100 /var/lib/dpkg/status
     0.99.20-2 500
        500 http://deb.devuan.org/merged daedalus/main amd64 Packages</code></pre></div><p>apt refuses to upgrade to the newer version.</p><p>what needs to be done to get apt to upgrade the upower package to the current version?</p>]]></description>
			<author><![CDATA[dummy@example.com (grunchy)]]></author>
			<pubDate>Wed, 22 Oct 2025 22:06:52 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=58747#p58747</guid>
		</item>
	</channel>
</rss>
