Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#45122 - [util-linux] Update error

Attached to Project: Arch Linux
Opened by Sven Engström (zw3n) - Thursday, 28 May 2015, 16:26 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 28 May 2015, 18:16 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When updating system (pacman -Syu) including util-linux from 2.26.1-3 to 2.26.2-1 I get an error regarding overwriting /usr/bin/lsblk. Running pacman again seems to have installed the package even though it gave the same error again. Happened on x86_64 but i can't why this would be architecture dependent.

Additional info:
util-linux 2.26.1-3 -> 2.26.2-1

pacman error:
...
(15/22) upgrading util-linux [######################] 100%
error: extract: not overwriting dir with file /usr/bin/lsblk
error: problem occurred while upgrading util-linux
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.


Steps to reproduce:
Run pacman -Syu on system running util-linux 2.26.1-3
   pacman.log (8.2 KiB)
This task depends upon

Closed by  Dave Reisner (falconindy)
Thursday, 28 May 2015, 18:16 GMT
Reason for closing:  Not a bug
Additional comments about closing:  User error, not a packaging bug.
Comment by Dave Reisner (falconindy) - Thursday, 28 May 2015, 16:38 GMT
Why is /usr/bin/lsblk a directory on your system? You should see a file type mismatch if you run 'pacman -Qkk util-linux'.

Your pacman.log also shows another problem:

[2015-05-28 18:04] [ALPM] error: cannot remove /usr/include/sys/ (Not a directory)

Doubtful this is a packaging problem...
Comment by Sven Engström (zw3n) - Thursday, 28 May 2015, 18:06 GMT
Probably isn't, after a reboot i ended up with having to do a manual fsck. Closing report.

Loading...