Wine packages missing from Debian repos [SOLVED]

[wolverine_tech]

Do you have 'checkinstall' installed?

You need that for the command to execute.

[wolverine_tech]

Don't comment out the unstable repository before you've installed Wine.
If you keep getting an error, you could try simply 'make install' instead of 'checkinstall make install'. But that'll make uninstalling Wine a messy job.
I'm not sure why you would get an error with checkinstall.
Did the make command generate a .deb package?

Also, are you on a 32-bit system or a 64-bit system?

[JoeInMN]

OK, so it does work on LMDE then. Here's a suggestion - Perhaps it'll be a good idea to write-up:

what steps you took (in their proper sequence),
what changes you made to your source list,
which file you downloaded,
your hardware info, your OS info (64-bit, 32-bit...)
any other details that you might feel are important...
include appropriate screenshots and bash code outputs

and post it at the end of this thread, or even better, as a separate thread, coz the previous posts (including mine) are too 'sparse' for beginners. I am still finding my way around Linux and the steps involved above were quite overwhelming when I tried them first.

My system:
MSI Wind U100 netbook
1.60 GHz Atom (two processors)
1 gig RAM
Mint Debian 32-bit, Update Pack 3
3.0.0-1-686-pae kernal
Currently running LXDE installed over GNOME (shouldn't matter)

Here are my steps as well as I can remember. Note that step 6 may take a while; it took a couple of hours to complete on my netbook, though it probably goes much faster on a beefier system. Anyway allow some time:

1) Install checkinstall if you don't have it already. This should be available via Synaptic.

2) Download the source file from http://dev.carbon-project.org/debian/wine-unstable/... The one that worked for me was the first file in the "Source package" section, which at the moment is wine-unstable_1.3.33.orig.tar.bz2. The second file currently there, which looks like it should be for Debian, is apparently something else; I don't know yet what its purpose is.

3) Extract the source file. This should result in a directory called wine-1.3.33.

4) Start up a terminal and cd into that directory (or go into it with your file manager and use the "Open terminal here" menu option if your file manager has one).

5) In the terminal enter:

Code: Select all

./configure

Several messages about missing codecs etc. appeared at the end of that, but apparently they weren't things that I needed for my purposes. I didn't record what they were.

6) When that finishes, enter:

Code: Select all

make

7) When that finally completes, enter:

Code: Select all

sudo checkinstall make install

That should be it, for the base WINE install anyway. Try running something. If an error box pops up about some missing component, the easiest way to get it is probably to use winetricks, a script which is available through Synaptic, or read about other sources here: http://wiki.winehq.org/winetricks. I needed WINE to run some old Visual Basic things that I wrote years ago, and I was missing vb6run (got no error message about that, but I knew about it from past experience) and comdlg32ocx. In winetricks the tickboxes for these and others are found via "Select the default wineprefix" and then "Install a Windows DLL or component."

And that's all I can offer about my own experience. I'm not knowledgeable enough myself to help with any additional issues that anyone might run into with this, but hopefully it will be of some help to someone.

[wolverine_tech]

hopefully it will be of some help to someone.

JoeInMN, Much appreciated.

(Hey, you are one post away from graduating to level 2! )

[Anthrogue]

ok.... thanks wolverine_tech and JoeInMN, I think I have it. This post immediately above appears to collate relevant info. My most recent problem came in forgetting (I think) the "sudo" in:

sudo checkinstall make install

I had to get libfreetype6-dev in order to run ./configure by adding a "deb-src http://ftp.ca.debian.org/debian sid main contrib non-free" line to /etc/apt/sources.list << and I'm deleting this entry now because of these comments by wolverine_tech.

lol, thanks again. I figure wine is installed vis a vis the message:

Done. The new package has been installed and saved to

/home/anthrogue/Downloads/wine-1.3.33/wine_1.3.33-1_i386.deb

[wolverine_tech]

Glad to hear that it worked. (Save that .deb file for future should you end up with a fresh install of LMDE!)

[fredwarren]

Here is what worked for me. I built the packages from scratch using the source code found at http://dev.carbon-project.org/debian/wine-unstable/

The following is pretty much a cut and paste job of what needs to be done to build the Debian 64-bit packages. If you are building for 32-bit just leave out the apt-get with all of the ia32 and lib32 stuff.

Code: Select all

#Essentials for building packages
sudo apt-get install build-essential devscripts fakeroot

#Wine dependencies
sudo apt-get install  libxt-dev libxkbfile-dev libxxf86dga-dev libxxf86vm-dev freeglut3-dev libxmu-dev libncurses5-dev libcups2-dev libopenal-dev libasound2-dev oss4-dev libsane-dev libusb-dev libgsm1-dev libmpg123-dev libcapi20-dev libhal-dev libdbus-1-dev libgphoto2-2-dev liblcms1-dev libldap2-dev libgnutls-dev libxslt1-dev unixodbc-dev prelink sharutils gcc-multilib libgstreamer-plugins-base0.10-dev

#Wine 64bit additional dependencies
sudo apt-get install ia32-libs-dev lib32z1-dev lib32v4l-dev lib32ncurses5-dev lib32asound2-dev

mkdir winebuild
cd winbuild


# Wine source for debian as of Dec 1, 2012
# found at: http://dev.carbon-project.org/debian/wine-unstable/
# this portion here will require adjustment for newer versions of wine

wget http://dev.carbon-project.org/debian/wine-unstable/wine-unstable_1.3.33.orig.tar.bz2
wget http://dev.carbon-project.org/debian/wine-unstable/wine-unstable_1.3.33-0.1.debian.tar.bz2
wget http://dev.carbon-project.org/debian/wine-unstable/wine-unstable_1.3.33-0.1.dsc
tar xzvf wine-unstable_1.3.33.orig.tar.bz2
cd wine-1.3.33
tar xzvf ../wine-unstable_1.3.33-0.1.debian.tar.bz2

#Perform the actual build
debuild -uc -us

cd ..

#Install the packages
sudo dpkg -i *.deb

[Kittysong]

Hi! Nothing in this thread worked out for me and I'm sure that's the case for someone besides me, so I thought I'd post this solution. I'm using Mint 10 with Debian and also Gnome, so it should work for anyone who's the same, at least.

There's a list of mirrors here!: http://packages.debian.org/squeeze/i386/wine/download

Open a terminal, and type: sudo gedit /etc/apt/sources.list

Start a new line and write: deb http://ftp.de.debian.org/debian squeeze main only replace the underlined part with one of the urls you see listed on the mirrors page. Remember to include the http:// part. Like this: deb http://ftp.us.debian.org/debian squeeze main (if that doesn't work out for you, try just temporarily erasing every source and have the text file be only this single source.)

Save that, close it, and then go back to terminal and write: sudo apt-get update

When it's done updating, type: sudo apt-get install wine

When I did that, it told me that there were still missing dependencies. Do sudo apt-get install [missing dependency] and write in one of the missing dependencies. It will probably have missing dependencies, too, so try those as well. Eventually one won't be dependent on something! I don't know if this would be the same for everyone, but I had to do this:

sudo apt-get install libwine
sudo apt-get install wine-bin
sudo apt-get install wine --fix-missing

Then Wine was a thing, yay!

And then you should probably fix your sources if you deleted them all.

[titaniumtux]

@Kittysong,

You're installing an old version of wine. I'm sure it gets the job done, but I did succeed using the Lamaresh Wine Repository for Debian. It seems to be the recommended repository for installing the latest version of Wine in any Debian distro (LMDE, #!, etc.).

I installed Wine using the Lamaresh repo, and I had a real wine installed, however it didn't automatically add itself to the apps menu (basically I didn't "see" Wine in the GUI, so I didn't know if it was installed correctly). After installing something in Wine, its shortcut was added in the Wine apps menu, but Wine Config was never added (I could manually add it), so I had to run it by executing winecfg. Forgive me for being used to using Ubuntu, but I figured winecfg would automatically be added to the window.

At any rate, this seems to be the most "official" way to install Wine in LMDE, it'll get you Wine. I didn't test DirectX or any other fancy stuff, but the installation "just worked." Also I'm running LMDE in VirtualBox (host is Ubuntu...for now), despite this I had no graphics problems in Wine.

[Miloose]

I know it's' bad, I know that by computer will probably burn, I know that I will go to hell, I know that and all the rest, but I'm using the ubuntu ppa without any problems. And it's'also the case for the chrome daily-builds, and I also use the ubuntu-security ppa for some issues (that's'where I get my firefox version).

Up till now, with a bit of care and manual updates, everything is fine. But yeah, the day Satan is coming to pick me up, I'll know why...

[zerozero]

@Miloose,
when we see, for example the troubles that a simple pkg like libpixman (look for it in synaptic) that was patched into LMDE from an Ubuntu pkg
search.php?st=0&sk=t&sd=d&sr=posts&keywords=libpixman
(and with time instead of patching the fonts this pkg breaks xorg, breaks updates, leaves users without functional systems)

Let's be very clear here: it's not if, it's when it is going to break, and it will;
but it's your system, it's your linux, it's your freedom to do with it what you want
it is not fine to suggest that to others.

[Waha]

I apologize for the necro but this thread is easily found from Google and I, for one, do not consider it solved.

I tried adding frickleplatz repo but it is very out of date. It saddens me that the only person that seems to be willing to package these files is someone with such an irritating moral conviction as to not release them in repo form. This, as mentioned previously.

My irritation at updating from this (mostly in the time it takes to download all the packages then remember the rainbows install order to use the GUI...) has led me to automate it, instead, and I've come to share the script for the benefit of those, who, like me, are annoyed by this arduous task.

With all due respect to the packager, please read the page before using this script. Specifically the quote below:

Originally posted by Curan

• If you don't know me, you shouldn't trust me. Installation of binary packages from unknown sources is strongly discouraged! If you still want the Debian package below, download the source package (the source package is signed with my OpenPGP key, which is signed by several Debian Developers and can be obtained from keyring.debian.org, which only distributes keys of Debian Maintainers and Debian Developers) and verify the changes I've made in the .debian.tar.bz2. The .orig.tar.bz2 should have the same MD5 hash (c9242ff56223186124c1d42ceb03afe4) as upstream's tarball (if not, download the .tar.bz2 tarball from winehq.org and use it as the .orig.tar.bz2). Then build the binary yourself.
• As I get quite a few e-mails about this: no I won't set up an APT repository for these packages, because I don't want to encourage people to install binary packages from third parties without thinking about what they're doing.

Personally I saved this to /usr/bin/updatewine but you can put it wherever you like (maybe sbin since it can only be run as root? But then you can't tab the name when using sudo).

Code: Select all

#!/bin/bash

# To use:
#  Read the warnings on: http://dev.carbon-project.org/debian/wine-unstable/
#  Run as root or with sudo
#  This will use arch to automatically guess your architecture, but you may
#   override it by passing the architecture in the command line. Either: amd64
#   or i386

# Run as root!
if [ $(id -u) -ne 0 ]; then
    echo "$0 must be run as root"
    exit 1
fi

if [ "$1" == 'amd64' ] || [ "$1" == 'i386' ]; then arch="$1"
elif [ "$1" == '64' ]; then arch="amd64"
elif [ "$1" == '32' ]; then arch="i386"
elif [ -n "$1" ]; then echo "Unknown/unusable architecture"; exit 1
else
   arch=`arch || uname -m`
   if [ "$arch" == "x86_64" ]; then arch='amd64'
   elif [ "${arch:0:1}" == "i" ] && [ "${arch:2}" == "86" ]; then arch='i386'
   fi
fi
cd /tmp
wget --base="http://dev.carbon-project.org/debian/wine-unstable/" -nd \
 "http://dev.carbon-project.org/debian/wine-unstable/" -F -c \
 -A "_$arch.deb" -e robots=off --ignore-tags=link -r -l 1
dpkg -i libwine-*.deb wine*.deb
rm libwine-*.deb wine*.deb

As a side note, if he is to release something other than wine in this as some sort of response to my sharing this script, that's on his own head. I'm doing what I can to respect his wishes while being less inconvenient. I'm thinking of those crazies in TV shows that release a terrible [living] virus onto the population just to show how serious of a threat it is and how we should add it to our terrorism prevention, even if we waste enough money on that already and the probability of anyone using the virus is less than 1% anyway. >_> Totally unrelated, sorry.

[äxl]

Thanks, Waha! Also for putting his "irritating moral conviction" here.
Though I think the smallest part of the script is to download and install the packages.

[pazuzuthewise]

Please somebody post easy to follow instructions for this installation.
I followed the link that tdockery mentioned, but found instructions too advanced for my present level.

OK, here goes:

1. Look for the list of packages for your architecture (32bit or 64bit)
2. Download each file in the list (there will be 18-19 files)
3. In your Downloads directory there will now be 18-19 .deb files
4. While in the Downloads directory, right-click on a blank space and select open in Terminal
5. Your command prompt should now look something like: tom@tom-laptop:~/Downloads$
6. Enter the following command:

Code: Select all

sudo dpkg -i *.deb

7. All of those .deb files in Downloads will now be installed
8. Once it is done installing, you can delete all the .deb files in Downloads
9. Enjoy Wine 1.3

I successfully installed wine unstable 1.5 for 32 bit using this method - downloading the binaries from http://dev.carbon-project.org/debian/wine-unstable/ - on LMDE with update pack 4.
Clarification for point 1: you only need the binary packages listed for your architecture (32 or 64 bit), not the source package, nor the changes files.
The installation did not go successfully at first, because there were two missing dependencies:

Code: Select all

libwine-dev-unstable depends on libgettextpo0
libwine-capi-unstable depends on libcapi20-3

When I've tried to install libgettextpo0 using apt-get, the output suggested that I run

Code: Select all

sudo apt-get -f install

Following this suggestion seemed to install the missing dependencies, but to be on the safe side, I reinstalled the wine packages by repeating the step 6 from above.
Now wine works, I've tested it both by running "wine configuration" from the menu and by running a windows program (my dvd catalog program, whereisit).

[NeoMint]

If I haven't said already, just use Playonlinux.

[gosa]

If I haven't said already, just use Playonlinux.

Correct me if I'm wrong (and please do, because this is a subject where I'd like to be wrong)...

I don't think Playonlinux offer Wine in it's repositories - it just downloads the version that you need for the specific application/game you want to install from your distributions repository.
- So if there's no Wine in your repository Playonlinux will fail. (I'm just saying, because I'm quite sure I tried to take that route back when UP3 came out)

[rickabillie]

I used the frickelplatz method and now I get the following error in Mint update.
http://pastebin.com/PyZUMF71
I suppose I could just comment it out, but was wondering if there was an easy way to fix it.
I am not entirely sophisticated with the command line, but I can follow instructions.
LMDE
Thanks, Richard

[i8igmac]

Ok, so i have run into this wine problem and found this thread... im currently downloading all the deb files and im about to install them... is this going to break my os?

i see the word solved... maybe lets make the first post with clear instructions with warnings

as i am confused and not sure if i should go threw with this install

[craigevil]

using checkinstall is messy and does not always work properly. If you must built a package rather than just using the wine packages from http://dev.carbon-project.org/debian/wine-unstable/ , download the necessary sources package from the carbon-project :

Then follow the guide and do it right:
Debian User Forums • View topic - HowTo Build a Package from Source the Smart Way : http://forums.debian.net/viewtopic.php?f=16&t=38976

Or just download the wine package from the Mepis 11 repo
http://main.mepis-deb.org/mepiscr/testr ... 1_i386.deb
http://main.mepis-deb.org/mepiscr/testr ... _amd64.deb
You also need the wine-gecko package from the repo as well.

Linux Mint Forums • View topic - Wine packages missing from Debian repos [SOLVED] : http://forums.linuxmint.com/viewtopic.p ... hilit=wine