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 #