You are not logged in.
Pages: 1
When I try to run pacman -Sy wine it says that the package is not found in the database. I'm using Arch 64. This is weird never had this happen before using arch.
"Once you go Arch you will never go back"
Offline
When I try to run pacman -Sy wine it says that the package is not found in the database. I'm using Arch 64. This is weird never had this happen before using arch.
It's not in the 64 bit repos because it's a 32 bit program. There's bin32-wine in AUR.
Offline
You could just grab the 32bit package from a mirror, download it, and # pacman -U wine.i686.pkg.etc
Offline
You could just grab the 32bit package from a mirror, download it, and # pacman -U wine.i686.pkg.etc
Does that work??
![]()
Offline
fumbles wrote:You could just grab the 32bit package from a mirror, download it, and # pacman -U wine.i686.pkg.etc
Does that work??
Sure, if you have all of the supporting lib32 libraries to go with it.
Offline
sand_man wrote:fumbles wrote:You could just grab the 32bit package from a mirror, download it, and # pacman -U wine.i686.pkg.etc
Does that work??
Sure, if you have all of the supporting lib32 libraries to go with it.
In noob-friendly terms (Since I fscked this up once), DON'T. You would need all the required lib32 packages, from the AUR. You can't use packages straight from the i686 mirrors for that, as they will mess up your native x86_64 libs. At that point, there is no point - using bin32-wine from the AUR means your dependencies are all nice and handled, nothing to worry about. There's even a binary package of it for people who hate compiling in the archlinuxfr repo, but it's often outdated.
Offline
In noob-friendly terms (Since I fscked this up once), DON'T. You would need all the required lib32 packages, from the AUR. You can't use packages straight from the i686 mirrors for that, as they will mess up your native x86_64 libs. At that point, there is no point - using bin32-wine from the AUR means your dependencies are all nice and handled, nothing to worry about. There's even a binary package of it for people who hate compiling in the archlinuxfr repo, but it's often outdated.
I was only referring to Wine itself, not its dependencies. But, there's a certain level of satisfaction that can only be achieved by installing a 32 bit glibc accidentally on a 64 bit system. I know; I've done it.
***If you're not confident, do as Ranguvar suggests***
Offline
yaourt -S bin32-wine --aur. Done.
Offline
What's the difference between the Suse and normal versions from AUR? It's not mentioned there.
ARCH64 | XMonad | Configs | myAURpkgs | ArchWiki Contribs | Screenies
Offline
Suse ???? Sorry, this is Archinux. ![]()
My Linux Blog - http://TheSmallerBang.wordpress.com/
Offline
Suse ???? Sorry, this is Archinux.
Ye.. I was referring to bin32-wine-suse 1.1.13.2-1 and bin32-wine 1.1.13-1
ARCH64 | XMonad | Configs | myAURpkgs | ArchWiki Contribs | Screenies
Offline
From what I can gather, this may have something to do with it...
Most linux distributions these days support 64-bit. The problem is that not all distributions handle 64-bit in the same way. Distributions like Fedora/Suse chose to extend their 32-bit distribution to 64-bit by installing 64-bit libraries into /usr/lib64 and installing 32-bit libraries in /usr/lib while distributions like Debian chose to install only 64bit libraries. The 64-bit libraries are installed in /usr/lib and /usr/lib64 is a symlink to /usr/lib.
I'm just guessing though. Perhaps a 'pacman -Ql' would provide further info?
Offline
From what I can gather, this may have something to do with it...
http://wiki.winehq.org/WineOn64bit wrote:Most linux distributions these days support 64-bit. The problem is that not all distributions handle 64-bit in the same way. Distributions like Fedora/Suse chose to extend their 32-bit distribution to 64-bit by installing 64-bit libraries into /usr/lib64 and installing 32-bit libraries in /usr/lib while distributions like Debian chose to install only 64bit libraries. The 64-bit libraries are installed in /usr/lib and /usr/lib64 is a symlink to /usr/lib.
I'm just guessing though. Perhaps a 'pacman -Ql' would provide further info?
The point of bin32-wine-suse is to provide up-to-date, working wine on *x86_64*.
[...]
SuSE is used because they provide up-to-date binaries.
Last edited by Wintervenom (2009-01-22 22:11:50)
Offline
I'd like to chip in here.
Questions like "how come I can install wine_64bit in every other distro I tried, including Gentoo?" aside,
I run into a brick wall here. Neither bin32-wine nor bin32-wine-suse seem to exist on their servers anymore.
In both cases the makepkg command stops letting me know that the file to be downloaded can't be found...
That's... not helpful, I guess...
Offline
I'd like to chip in here.
Questions like "how come I can install wine_64bit in every other distro I tried, including Gentoo?" aside,
I run into a brick wall here. Neither bin32-wine nor bin32-wine-suse seem to exist on their servers anymore.
In both cases the makepkg command stops letting me know that the file to be downloaded can't be found...That's... not helpful, I guess...
I upgraded wine on my 64-bit laptop yesterday...worked fine. Check to make sure the version number in the PKGBUILD represents the one that's actually in the repos
![]()
Offline
hum... here's the dumb newbie question of the day: How do I find that out? ![]()
Offline
I found that the ftp-server has the 1.1.17 version. Thats so most recent, so that would be fine with me.
I changed the pkbuild to reflect that and now it downloads fine.
Unfortunatly right after the download it checks the md5sum, and, bit surprise, that does not check out..
what can I do now? I have no idea what md5sum code to put into the pkbuild to make that work...
Offline
Remove the line with md5sum from PKGBUILD
Offline
That did it.. thank you ![]()
Offline
Pages: 1