On 2025-02-06 12:33:55 Felix Miata via tde-devels wrote:
# zypper se -sx trinity-filesystem | grep files i | trinity-filesystem | package | 14.1.3-1.osstw | noarch | (System Packages) v | trinity-filesystem | package | 14.1.3-1.osstw | noarch | TDEnoarch # rpm -e --nodeps trinity-filesystem # rpm -qa | grep y-files # rpm -ivh /var/cache/zypp/packages/TDEnoarch/trinity-filesystem-14.1.3-1.osstw.noarch .rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:trinity-filesystem-14.1.3-1.osstw################################# [100%] # zypper se -sx trinity-filesystem | grep files i | trinity-filesystem | package | 14.1.3-1.osstw | noarch | (System Packages) v | trinity-filesystem | package | 14.1.3-1.osstw | noarch | TDEnoarch #
Whether installation by zypper or rpm, the above sequence of events has been the state of affairs on multiple installations for more than a month, perhaps more than four.
There's also this: # grep y-files /var/log/zypp/history | tail -n3 2024-03-23 21:47:47|install|trinity-filesystem|14.1.1-1.osstw|noarch||TDEnoarch|98abd… 2024-05-19 02:27:49|install|trinity-filesystem|14.1.2-1.osstw|noarch||TDEnoarch|1326e… 2024-10-31 01:04:49|install|trinity-filesystem|14.1.3-1.osstw|noarch||TDEnoarch|79367…
The result should resemble approximately the following:
# zypper se -sx trinity-tdm | grep tdm i | trinity-tdm | package | 14.1.3-1.osstw | x86_64 | TDE #
Does this happen only on Tumbleweed installations? If so, it looks like some sort of weirdness in the repository (or repository content) definitions. I suppose that using a capability selector (e.g. 'trinity-filesystem<=14.1.3', etc.) shows the same?
Leslie