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#16090 - [fftw] Cannot update

Attached to Project: Arch Linux
Opened by Alexander Kojevnikov (alexk) - Tuesday, 08 September 2009, 01:13 GMT
Last edited by Ronald van Haren (pressh) - Tuesday, 08 September 2009, 05:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ronald van Haren (pressh)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

$ sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...

Targets (1): fftw-3.2.2-1

Total Download Size: 0.00 MB
Total Installed Size: 9.36 MB

Proceed with installation? [Y/n]
checking package integrity...
(1/1) checking for file conflicts [#####################] 100%
error: failed to commit transaction (conflicting files)
fftw: /usr/share/info/dir exists in filesystem
Errors occurred, no packages were upgraded.
This task depends upon

Closed by  Ronald van Haren (pressh)
Tuesday, 08 September 2009, 05:46 GMT
Reason for closing:  None
Additional comments about closing:  please re-open if more people run into problems, see my comment
Comment by Allan McRae (Allan) - Tuesday, 08 September 2009, 01:45 GMT
pressh: make sure you have merged your makepkg.conf from pacman-3.3. That automatically removes this file.
Comment by Alexander Kojevnikov (alexk) - Tuesday, 08 September 2009, 04:45 GMT
I just tried again, and this time the upgrade worked. I don't see any changes in SVN log so it might have been a local issue.
Comment by Ronald van Haren (pressh) - Tuesday, 08 September 2009, 05:46 GMT
@allan, yes I know, I noticed I didn't yet do it in this particular chroot. I did directly a rebuild within 15 minutes or so so I figured it wouldn't get picked up by any mirrors and such .... how wrong can I be.

Either way, if more people run into problems let me know and I bump the pkgrel. closing for now




Loading...