Bug 1220730 - virtiofsd update 1.10-2.1 -> 1.101-3.1 does not take place
Summary: virtiofsd update 1.10-2.1 -> 1.101-3.1 does not take place
Status: RESOLVED DUPLICATE of bug 1220592
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Virtualization:Other (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: virt-bugs list
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-01 08:18 UTC by Peltonen
Modified: 2024-03-01 14:22 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
LibreOffice .odt file with 2 screenshots about the reported problem (60.09 KB, application/vnd.oasis.opendocument.text)
2024-03-01 08:18 UTC, Peltonen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peltonen 2024-03-01 08:18:19 UTC
Created attachment 873147 [details]
LibreOffice .odt file with 2 screenshots about the reported problem

I tried to update this 29..2.2024 evening and now 1.3.2024 once again, but I get the error massage, please see attachment (LibreOffice odt file with 2 screenshots about the problem).
Comment 1 Michael Pujos 2024-03-01 13:13:30 UTC
Confirming this issue:

unpacking of archive failed on file /usr/libexec/virtiofsd;65e1d00f: cpio:
File from package already exists as a directory in system
error: virtiofsd-1.10.1-3.1.x86_64: install failed
error: virtiofsd-1.10.1-2.1.x86_64: erase skipped
(139/414) Installing: virtiofsd-1.10.1-3.1.x86_64
.......................................................................................................................................................................................
[error]Installation of virtiofsd-1.10.1-3.1.x86_64 failed:
Error: Subprocess failed. Error: RPM failed: Command exited with status 1.
Comment 2 James Fehlig 2024-03-01 14:22:10 UTC
Dup of bug#1220592

*** This bug has been marked as a duplicate of bug 1220592 ***