You are not logged in.
New version 4.0.7-3 does work on both i686 and x86_64 - so this is fixed properly now.
Can this thread be marked [SOLVED] now?
Last edited by mcloaked (2013-07-04 18:45:27)
Mike C
Offline
A few hours ago I did a 'pacman -Syu'. A few updates were shown. I confirmed that I wanted the upgrades and let the system get on with it.
Ended up with a failure. Error as below:
error: failed to commit transaction (conflicting files)
/usr/bin/ldbadd exists in both 'ldb' and 'samba'
/usr/bin/ldbdel exists in both 'ldb' and 'samba'
/usr/bin/ldbedit exists in both 'ldb' and 'samba'
/usr/bin/ldbmodify exists in both 'ldb' and 'samba'
/usr/bin/ldbrename exists in both 'ldb' and 'samba'
/usr/bin/ldbsearch exists in both 'ldb' and 'samba'
/usr/lib/python2.7/site-packages/ldb.so exists in both 'ldb' and 'samba'
/usr/share/man/man1/ldbadd.1.gz exists in both 'ldb' and 'samba'
/usr/share/man/man1/ldbdel.1.gz exists in both 'ldb' and 'samba'
/usr/share/man/man1/ldbedit.1.gz exists in both 'ldb' and 'samba'
/usr/share/man/man1/ldbmodify.1.gz exists in both 'ldb' and 'samba'
/usr/share/man/man1/ldbrename.1.gz exists in both 'ldb' and 'samba'
/usr/share/man/man1/ldbsearch.1.gz exists in both 'ldb' and 'samba'
/usr/share/man/man3/ldb.3.gz exists in both 'ldb' and 'samba'
Errors occurred, no packages were upgraded.ldb is listed as a Samba dependency, so I went and checked the packages. So far as I can see, the error is quite correct, and the problem seems to be in the samba-4.0.7-1-x86_64 package. Looking at the last samba package (samba-4.0.6-1-x86_64), the extra files do not appear there.
I'd report the error to the maintainer (same maintainer is listed for both), but I don't see an email address for him, and I'm not sure if I should be reporting it elsewhere?
Paul.
Offline
Merging with the exisiting thread.
Please search before posting...
Offline
This has been fixed already, make sure you are using an up to date mirror.
In the future, instead of trying to email a maintainer directly, it is probably a better idea to file a bug report (after searching in an effort to avoid duplication of course). This is open-source, so live everything else, reported issues should be... open.
Offline