# 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 #
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
J Leslie Turriff composed on 2025-02-06 13:10 (UTC-0600):
Felix Miata 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
Does this happen only on Tumbleweed installations?
I don't remember. I suspect it may be only those and Slowroll, but on all, there's a suspicious recurrence of same package versions being reinstalled over and over again on those two and Leap.
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?
I don't know anything about "capability" selection. My only suspicion about these package reinstallations, a tenuous one, has to do with my TW and SR repo caches being on bind mounts, not local, with rpm file ownerships not being 0:0.
Felix Miata composed on 2025-02-06 14:36 (UTC-0500):
J Leslie Turriff composed on 2025-02-06 13:10 (UTC-0600):
Felix Miata 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
Does this happen only on Tumbleweed installations?
I don't remember. I suspect it may be only those and Slowroll, but on all, there's a suspicious recurrence of same package versions being reinstalled over and over again on those two and Leap.
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?
I don't know anything about "capability" selection. My only suspicion about these package reinstallations, a tenuous one, has to do with my TW and SR repo caches being on bind mounts, not local, with rpm file ownerships not being 0:0.
Force installing the package changes nothing apparent: # rpm -Uvh --force trinity-filesystem-14.1.3-1.osstw.noarch.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:trinity-filesystem-14.1.3-1.osstw################################# [ 50%] Cleaning up / removing... 2:trinity-filesystem-14.1.3-1.osstw################################# [100%] # zypper --no-refresh se -s y-files | grep -v '32bit|debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort -f il | trinity-filesystem | package | 14.1.3-1.osstw | noarch | (System Packages) vl | trinity-filesystem | package | 14.1.3-1.osstw | noarch | TDEnoarch #
Felix Miata composed on 2025-02-11 23:06 (UTC-0500):
Felix Miata composed on 2025-02-06 14:36 (UTC-0500):
J Leslie Turriff composed on 2025-02-06 13:10 (UTC-0600):
Felix Miata 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
Does this happen only on Tumbleweed installations?
I don't remember. I suspect it may be only those and Slowroll, but on all, there's a suspicious recurrence of same package versions being reinstalled over and over again on those two and Leap.
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?
I don't know anything about "capability" selection. My only suspicion about these package reinstallations, a tenuous one, has to do with my TW and SR repo caches being on bind mounts, not local, with rpm file ownerships not being 0:0.
Force installing the package changes nothing apparent: # rpm -Uvh --force trinity-filesystem-14.1.3-1.osstw.noarch.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:trinity-filesystem-14.1.3-1.osstw################################# [ 50%] Cleaning up / removing... 2:trinity-filesystem-14.1.3-1.osstw################################# [100%] # zypper --no-refresh se -s y-files | grep -v '32bit|debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort -f il | trinity-filesystem | package | 14.1.3-1.osstw | noarch | (System Packages) vl | trinity-filesystem | package | 14.1.3-1.osstw | noarch | TDEnoarch #
The puzzle continues: # zypper --no-refresh se -s ty-files | grep -v '32bit|debug|devel|srcp|openSUSE-20' | egrep 'x86|noarch'| sort -f i+ | trinity-filesystem | package | 14.1.3-1.osstw | noarch | (System Packages) v | trinity-filesystem | package | 14.1.3-1.osstw | noarch | TDEnoarch # zypper -v in trinity-filesystem Verbosity: 2 Non-option program arguments: 'trinity-filesystem' Initializing Target Checking whether to refresh metadata for Non-OSS Checking whether to refresh metadata for OSS Checking whether to refresh metadata for Update Loading repository data... Reading installed packages... 'trinity-filesystem' is already installed. No update candidate for 'trinity-filesystem-14.1.3-1.osstw.noarch'. The highest available version is already installed. Resolving package dependencies... Force resolution: No Nothing to do. # zypper -v in -f -d trinity-filesystem Verbosity: 2 Non-option program arguments: 'trinity-filesystem' Initializing Target Checking whether to refresh metadata for Non-OSS Checking whether to refresh metadata for OSS Checking whether to refresh metadata for Update Loading repository data... Reading installed packages... Forcing installation of 'trinity-filesystem-14.1.3-1.osstw.noarch' from repository 'TDEnoarch'. Resolving package dependencies... Force resolution: No
The following package is going to be reinstalled: trinity-filesystem 14.1.3-1.osstw
1 package to reinstall.
Package download size: 56.9 KiB
Download only.
Backend: classic_rpmtrans --download-only Continue? [y/n/v/...? shows all options] (y): y committing Retrieving: trinity-filesystem-14.1.3-1.osstw.noarch (TDEnoarch) (1/1), 56.9 KiB Retrieving: trinity-filesystem-14.1.3-1.osstw.noarch.rpm .................................................................................................................[done (43.4 KiB/s)] Failed to provide Package trinity-filesystem-14.1.3-1.osstw.noarch (TDEnoarch). Do you want to retry retrieval?
[TDEnoarch|http://archive.trinitydesktop.net/trinity/rpm/osstw/trinity-r14/RPMS/noarch] Can't provide file './trinity-filesystem-14.1.3-1.osstw.noarch.rpm' from repository 'TDEnoarch' History: - Can't hardlink/copy /var/tmp/AP_0xK6G459/trinity-filesystem-14.1.3-1.osstw.noarch.rpm to /var/cache/zypp/packages/TDEnoarch - Can't provide ./trinity-filesystem-14.1.3-1.osstw.noarch.rpm Abort, retry, ignore? [a/r/i] (a): i CommitResult (total 1, done 0, error 1, skipped 0, updateMessages 0) Installation has completed with error. # rpm -Uvh tmp/trinity-filesystem-14.1.3-1.osstw.noarch.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] package trinity-filesystem-14.1.3-1.osstw.noarch is already installed ab85m:~ # rpm -Uvh --nodeps --oldpackage tmp/trinity-filesystem-14.1.3-1.osstw.noarch.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] package trinity-filesystem-14.1.3-1.osstw.noarch is already installed ab85m:~ # rpm -Uvh --force --nodeps --oldpackage tmp/trinity-filesystem-14.1.3-1.osstw.noarch.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:trinity-filesystem-14.1.3-1.osstw################################# [ 50%] Cleaning up / removing... 2:trinity-filesystem-14.1.3-1.osstw################################# [100%] # ls -gG tmp total 114 -rw-rw-r-- 1 58262 Jan 26 05:34 trinity-filesystem-14.1.3-1.osstw.noarch.rpm -r--r--r-- 1 58076 Oct 29 03:30 trinity-filesystem-14.1.3-1.osstw.noarch.rpm202412 #
-
Felix Miata -
J Leslie Turriff