You are not logged in.
runned sudo pacman -Syu, part of pacman log:
[2011-10-21 14:04] Running 'pacman -Syu'
[2011-10-21 14:04] synchronizing package lists
[2011-10-21 14:05] starting full system upgrade
[2011-10-21 14:05] Running 'pacman -S libltdl'
[2011-10-21 14:05] Running 'pacman -S libtool'
[2011-10-21 14:06] removed libtool-multilib (2.4-5)
[2011-10-21 14:06] upgraded libltdl (2.4-5 -> 2.4.2-1)
[2011-10-21 14:06] installed libtool (2.4.2-1)
and now i can't install libtool-multilib
$ sudo pacman -S libtool-multilib
resolving dependencies...
warning: cannot resolve "libltdl=2.4", a dependency of "libtool-multilib"
:: The following package cannot be upgraded due to unresolvable dependencies:
libtool-multilib
Do you want to skip the above package for this upgrade? [y/N]
$ sudo pacman -Q libltdl
libltdl 2.4.2-1
libldtl is up-to-date and needed version
mirror is up-to-date
:: imagemagick: requires libltdl
:: lib32-libltdl: requires libltdl
:: libtool: requires libltdl=2.4.2
:: unixodbc: requires libltdl
so i reinstalled them.
what else i can do to solve this problem?
Last edited by gymka (2011-10-21 16:18:15)
Offline
I have the same problem; I can't figure out how to fix it either.
Offline
I have the same problem; I can't figure out how to fix it either.
Have you treid removing the versioned ependency i.e. change
package_libtool-multilib() {
depends=('sh' "libltdl=$pkgver" 'tar' "gcc-multilib=$_gccver" "lib32-libltdl=$pkgver")
to
package_libtool-multilib() {
depends=('sh' "libltdl" 'tar' "gcc-multilib=$_gccver" "lib32-libltdl=$pkgver")
in the PKGBUILD http://projects.archlinux.org/svntogit/ … l-multilib
Offline
Have you treid removing the versioned ependency
such version installs, but will it work as it should? maybe and other packages will complain about this?
Last edited by gymka (2011-10-21 16:01:56)
Offline
karol wrote:Have you treid removing the versioned ependency
such version installs, but will it work as it should? maybe and other packages will complain about this?
I have no idea ;P
I think you should open a bug report on this.
Offline
I have no idea ;P
I think you should open a bug report on this.
i'll wait, maybe developers will say something about this issue.
Offline
what can i say. thanks a lot for not reporting this bug.</sarcasm>
libtool-multilib moved from multilib-testing to multilib
Give what you have. To someone, it may be better than you dare to think.
Offline
what can i say. thanks a lot for not reporting this bug.</sarcasm>
libtool-multilib moved from multilib-testing to multilib
it's hard to see difference between bug and my own fault, so bug report is last thing which comes to my mind:)
Offline
what can i say. thanks a lot for not reporting this bug.</sarcasm>
libtool-multilib moved from multilib-testing to multilib
I saw that both packages link to the same PKGBUILD that said pkgver=2.4.2 even though the version in multilib should be libtool-multilib 2.4-5.
Why?
Offline
wonder wrote:what can i say. thanks a lot for not reporting this bug.</sarcasm>
libtool-multilib moved from multilib-testing to multilib
I saw that both packages link to the same PKGBUILD that said pkgver=2.4.2 even though the version in multilib should be libtool-multilib 2.4-5.
Why?
well now the "new" interface only have a link to trunk. logically it is 2.4.2 in there
Give what you have. To someone, it may be better than you dare to think.
Offline
karol wrote:wonder wrote:what can i say. thanks a lot for not reporting this bug.</sarcasm>
libtool-multilib moved from multilib-testing to multilib
I saw that both packages link to the same PKGBUILD that said pkgver=2.4.2 even though the version in multilib should be libtool-multilib 2.4-5.
Why?well now the "new" interface only have a link to trunk. logically it is 2.4.2 in there
I saw that 20 minutes before your post: https://bbs.archlinux.org/viewtopic.php … 3#p1006503 ,so I didn't know you've fixed it already and only the online interface needs time to adjust.
Offline