FS#7741 - unresolved enet package file conflicts

Attached to Project: Arch Linux
Opened by Stefan O. (hybrid) - Saturday, 04 August 2007, 19:44 GMT
Last edited by Jan de Groot (JGC) - Saturday, 04 August 2007, 21:41 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

This is the output that pacman -Sy enet gives me:

(1/1) checking for file conflicts [#####################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
enet: /usr/include/enet/callbacks.h exists in filesystem
enet: /usr/include/enet/enet.h exists in filesystem
enet: /usr/include/enet/list.h exists in filesystem
enet: /usr/include/enet/protocol.h exists in filesystem
enet: /usr/include/enet/time.h exists in filesystem
enet: /usr/include/enet/types.h exists in filesystem
enet: /usr/include/enet/unix.h exists in filesystem
enet: /usr/include/enet/utility.h exists in filesystem
enet: /usr/include/enet/win32.h exists in filesystem
enet: /usr/lib/libenet.a exists in filesystem

errors occurred, no packages were upgraded


k, simple, files already exist. But no package owns these files and I have no idea where they are from; pacman -Qos enet does not come up with anything.
Honestly I have no idea where these files come from. I know I could use pacman -Syf to force the installation, but maybe some package is broken like it installs the files but doesn't write them in the database.
If you think it helps I could post all currently installed packages.
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 04 August 2007, 21:41 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Saturday, 04 August 2007, 21:41 GMT
First of all, enet is a community package. Second, these files came to your system in some way. I guess it's a piece of software you compiled from source once, either by intention, or because of a bug in the PKGBUILD you used to build it with.

Loading...