Wine packages missing from Debian repos [SOLVED]

[sloto]

I got it working fine using this info, however after booting or something, I had no wine. none of my wine programs would initiate...sloto

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[/quote]

[michaelboord]

Hi,

with dpkg -i on all the packages I can install wine and wine is working fine.

But the big problem is apt-get update or the update manager menu is not working anymore.

apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
libwine-bin-unstable : Depends: libtinfo5 but it is not installable
N: Ignoring file 'opera.list.save' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Ignoring file 'opera.list.save' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
E: Unmet dependencies. Try using -f.


And if I do a apt-get -f install to fix this then Wine gets uninstalled.. .


So it's either a working wine of a working update system ????

Anyone knows a nice way of installing wine?
Or to let apt-get ignore libwine-bin-unstable?


Cheers,

[wyrdoak]

if your froggy you could install libtinfo5 http://packages.debian.org/sid/main/libtinfo5
and see if that help cure your dep's.

[JoeInMN]

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 get 16 binaries there for 32bit, actually, not 18 or 19. Throwing the the terminal command at those files results in "dependency problems - leaving unconfigured" errors for libwine-bin-unstable, wine-bin-unstable and wine-unstable. I thought maybe the wine-unstable_1.3.33-0.1.debian.tar.bz2 source there might be necessary too, but after extracting it, I don't know what I should do with it.

Gents,

May i propose a simpler solution.

1- go to wineHQ website

2- downloads section

3- Debian ( you will be redirected to sourceforge website

4- you'll find right above all old debian packages the latest RPM package ( just find it on page )

5- install "alien" and convert it to a .deb file using alien

6- open it with oackage installed

7-send me a big thank you "just kiddin here" ;D

hope it works for you guys

Sherief

This seems to take me to the same place as the first method, not to wherever it was that you saw an RPM file.

A perceptive reader may detect a somewhat frustrated tone here. I'm a long-time Ubuntu user who finally had to abandon both it and Ubuntu-based Mint for various reasons, and it annoys me a bit that everybody seems to put up easy PPAs to install or update just about every package that I need, but only for Ubuntu. Is there any chance that a usable Wine package will move any time soon into the repos where we can obtain it the way we do with everything else? It's a kind of important thing, I would think. Or can someone point me to whatever step I've missed here, so I can try again?

Thanks.

[wolverine_tech]

@ JoeInMN

Hi, did you try the steps mentioned on the following link:
http://forums.debian.net/viewtopic.php?f=10&t=68770
(Read till the very end. In there, a couple of the steps listed by s3a need to be switched. Also, In compiling from source, the "make" step takes a while in this case.)

It worked for me on Debian Testing. Haven't tried it on LMDE.

Hope this helps.

[JoeInMN]

Step 2 on that page (third step actually, thanks for the heads-up) yields:

Code: Select all

jpl@jpl-u100-mint-debian ~/Downloads/wine/debian $ make
make: *** No targets specified and no makefile found.  Stop.

I had the notion that one was supposed to do "configure" first, which may or may not be the case, but anyway:

Code: Select all

jpl@jpl-u100-mint-debian ~/Downloads/wine/debian $ configure
configure: command not found


[wolverine_tech]

You are right. I needed to "configure" first.

After adding "deb-src http://ftp.ca.debian.org/debian sid main contrib non-free" (sans quotes) and updating the source list, I did the following:

cd into the appropriate folder. I don't remember if that's Downloads/wine/ or Downloads/wine/Debian.
./configure
make
sudo checkinstall make install

(I had the "checkinstall" package installed before - makes for easy, clean uninstalls.)

Try the ./configure first... if you are in the right folder, hopefully that should work.

Also, don't forget to remove the newly added source (deb-src http://ftp.ca.debian.org/debian sid main contrib non-free) unless you plan on tracking Debian Sid.

[BTW, I have saved the .deb file (wine_1.3.29-1_i386.deb). It's 21.2 MB suitable for a 32-bit OS, unless multiarch supported. I could upload it someplace for your to download, not sure where. (Although, it might not be prudent downloading executable files from strangers on the internet )]

[JoeInMN]

/home/jpl/Downloads/wine/debian is the directory where the source was extracted. The "configure" command just returns a "command not found" message, which puzzles me.

Code: Select all

jpl@jpl-u100-mint-debian ~/Downloads/wine/debian $ ./configure
bash: ./configure: No such file or directory
jpl@jpl-u100-mint-debian ~/Downloads/wine/debian $ configure
configure: command not found
jpl@jpl-u100-mint-debian ~/Downloads/wine/debian $ sudo ./configure
[sudo] password for jpl:
sudo: ./configure: command not found


Edit: OK, after a bit of googling... There is no "configure" file in the directory, which I suppose is why nothing is happening. Could the necessary file be there under a different name? Though I wouldn't think that would be a good idea on the packager's part. Here's the directory:

Code: Select all

jpl@jpl-u100-mint-debian ~/Downloads/wine/debian $ ls
bug                               maint
changelog                         marlett.mensis
cleandeps.sh                      mime-info.keys
clean-install.sh                  mime-info.mime
compat                            multiarch-control.sh
control                           noexec.diff
control.in                        patches
copyright                         prep-control.sh
doclink.sh                        prep-control-transit.sh
extradep.c                        prep-install.sh
fnt2bdf.man                       README.Debian
gendeps.sh                        recs.sh
ia32.libs                         rules
ia32.sh                           source
libwine-bin.deps                  split.sh
libwine-bin.install-common        uninstaller.desktop
libwine-bin.install-modules       watch
libwine-capi.deps                 wine-auto.man
libwine.config-common             wine-bin.config-common
libwine.deps                      wine.binfmt
libwine-dev.install-common        wine-bin.install-common
libwine.docs-common               wine-bin.links-common
libwine-gl.deps                   wine-bin.lintian-overrides-common
libwine.install-common            wine-bin.manpages-common
libwine.install-modules           wine-bin.mime-common
libwine.install-platform          wine-bin.postinst-common
libwine.lintian-overrides-common  wine-bin.prerm-common
libwine-openal.deps               winecfg.desktop
libwine.postinst-common           wine.config-common
libwine-print.deps                wine-font-convert.man
libwine-print.install-common      wine.install-common
libwine-print.install-modules     winelauncher
libwine.recs                      wine.lintian-overrides-common
libwine-sane.deps                 wine.postinst-common
libwine.split                     wine-safe.man


[wolverine_tech]

Are you using the source file (the tar.bz2 file) from this link?
http://dev.carbon-project.org/debian/wine-unstable/

That's where I got the source file from.

[JoeInMN]

Are you using the source file (the tar.bz2 file) from this link?
http://dev.carbon-project.org/debian/wine-unstable/

That's where I got the source file from.

Yes. I re-downloaded and re-extracted it just now, just in case, but no difference. Maybe the current package itself is faulty, missing what it needs for configuring?

[Anthrogue]

Echo JoeInMN .... keep looking in this "solved" thread for some complete, logical explanation on how to put wine on LMDE. Part of me just wants to go Linux Mint 12 and forget about the headache. And yet, I hate to bail on LMDE at the first scent of an apparently irresolvable difficulty.

[wolverine_tech]

I think we are looking at two different .tar.bz2 files.

Are you using the wine-unstable_1.3.33.orig.tar.bz2 file - the one that's listed very first under Available files under Source package?

(Available files >> Source package >> wine-unstable_1.3.33.orig.tar.bz2)

It's an 18.9 MB file. After extracting, it'll show a folder named wine-1.3.33.
The folder contains 30 items and there's no subfolder named Debian or debian. It does contain a file named configure.

I tried it again just now on my Debian Wheezy box: (without even adding the unstable source to my source list, but you might need to do that)
1. cd into the folder wine-1.3.33 (So the path, in my case is wolverine@debian:~/Downloads/wine-1.3.33$
2. Then ran ./configure
3. It generated a whole bunch of lines and an error message about not finding some sound file. But it said I could run "make".
4. I then typed in "make" (sans quotes). Pressed enter.
5. It'll churn through a lot of code - took more than 15 minutes.
6. I then ran "checkinstall make install" (sans quotes) - I had had checkinstall installed earlier. Highly recommended.

This installed wine via the package management in Debian and generated a .deb file too. I think the .tar.bz2 file has been updated, but works fine as I just checked this.

It did not let me do this on my Mint 12 RC 64 bit setup. But worked smoothly on the 32-bit Debian setup. Hopefully, this will work on your LMDE setup too.

[JoeInMN]

I think we are looking at two different .tar.bz2 files.

Are you using the wine-unstable_1.3.33.orig.tar.bz2 file - the one that's listed very first under Available files under Source package?

(Available files >> Source package >> wine-unstable_1.3.33.orig.tar.bz2)

It's an 18.9 MB file. After extracting, it'll show a folder named wine-1.3.33.
The folder contains 30 items and there's no subfolder named Debian or debian. It does contain a file named configure.

I tried it again just now on my Debian Wheezy box: (without even adding the unstable source to my source list, but you might need to do that)
1. cd into the folder wine-1.3.33 (So the path, in my case is wolverine@debian:~/Downloads/wine-1.3.33$
2. Then ran ./configure
3. It generated a whole bunch of lines and an error message about not finding some sound file. But it said I could run "make".
4. I then typed in "make" (sans quotes). Pressed enter.
5. It'll churn through a lot of code - took more than 15 minutes.
6. I then ran "checkinstall make install" (sans quotes) - I had had checkinstall installed earlier. Highly recommended.

This installed wine via the package management in Debian and generated a .deb file too. I think the .tar.bz2 file has been updated, but works fine as I just checked this.

It did not let me do this on my Mint 12 RC 64 bit setup. But worked smoothly on the 32-bit Debian setup. Hopefully, this will work on your LMDE setup too.

Huh... No, I was actually using the second one, named wine-unstable_1.3.33-0.1.debian.tar.bz2, as I assumed (rather intuitively, I think) that it was the appropriate one for my Debian system. I downloaded the first one instead and ran ./configure successfully; it gave me several messages about unsupported codecs and such, but hopefully nothing too vital for what I need. The terminal is grinding through make as I type this. I'll wait for it...

Well, that took a long time on my Atom netbook. Seems to have gone OK. Next step...

I have checkinstall, and that step worked as well, though I had to do it twice because I didn't remember to use "sudo" until it was too late to stop my finger from pushing the ENTER key, heh.

Used the winetricks script to get the vb6 and comdlg32ocx components, and now I can run my old Visual Basic things again. That's all I have to test it with at the moment.

That was a bit of a struggle, but apparently it's all good, so far anyway. Thank You so much for all of your help.

[wolverine_tech]

You're welcome! Yeah, those .tar.bz2 files have confusing names. I downloaded the wrong file while trying it yesterday too.

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.

I'm sure a lot of LMDE users will appreciate your effort, coz my posts were specific to pure Debian install and your experience with LMDE may have subtle, important differences.

Happy 'Wine-ing' (drink responsibly!)

[JoeInMN]

Echo JoeInMN .... keep looking in this "solved" thread for some complete, logical explanation on how to put wine on LMDE. Part of me just wants to go Linux Mint 12 and forget about the headache. And yet, I hate to bail on LMDE at the first scent of an apparently irresolvable difficulty.

I didn't have a lot of hope for the SOLVED thread either, but thought I'd make sure there was no hope at all here before starting up what essentially would have been a duplicate thread. And hey, it worked out! So far. Thanks again to wolverine_tech.

Yeah, I've been close to bailing out on the Debian Edition a few times myself, but I'm sufficiently disenchanted with Ubuntu that I'm determined to stick with this. And it is getting better; I've found solutions for almost all of the significant issues that I've run into (still can't reconnect to ethernet after suspension), and feel confident that the smaller things will work out too.

[wolverine_tech]

Echo JoeInMN .... keep looking in this "solved" thread for some complete, logical explanation on how to put wine on LMDE. Part of me just wants to go Linux Mint 12 and forget about the headache. And yet, I hate to bail on LMDE at the first scent of an apparently irresolvable difficulty.

.... (still can't reconnect to ethernet after suspension), and feel confident that the smaller things will work out too.

Might be worth trying wicd instead of network manager. I had issues with network-manager on GNOME 2.x on Debian Squeeze, Testing and Mint 9 (kept asking for the password instead of automatically connecting). But network-manager works fine on LM 12 RC.

If you do try wicd, remember to completely purge network manager. Also, I think wicd does not support VPN connections (yet).

[Anthrogue]

I think we are looking at two different .tar.bz2 files.

Are you using the wine-unstable_1.3.33.orig.tar.bz2 file - the one that's listed very first under Available files under Source package?

(Available files >> Source package >> wine-unstable_1.3.33.orig.tar.bz2)

It's an 18.9 MB file. After extracting, it'll show a folder named wine-1.3.33.
The folder contains 30 items and there's no subfolder named Debian or debian. It does contain a file named configure.

I tried it again just now on my Debian Wheezy box: (without even adding the unstable source to my source list, but you might need to do that)
1. cd into the folder wine-1.3.33 (So the path, in my case is wolverine@debian:~/Downloads/wine-1.3.33$
2. Then ran ./configure
3. It generated a whole bunch of lines and an error message about not finding some sound file. But it said I could run "make".
4. I then typed in "make" (sans quotes). Pressed enter.
5. It'll churn through a lot of code - took more than 15 minutes.
6. I then ran "checkinstall make install" (sans quotes) - I had had checkinstall installed earlier. Highly recommended.

This installed wine via the package management in Debian and generated a .deb file too. I think the .tar.bz2 file has been updated, but works fine as I just checked this.

It did not let me do this on my Mint 12 RC 64 bit setup. But worked smoothly on the 32-bit Debian setup. Hopefully, this will work on your LMDE setup too.

ok.. I got wine-unstable_1.3.33.orig.tar.bz2 and extracted it into a directory. Ran ./config and ended up with:

checking for freetype-config... no
checking for freetype2-config... no
checking for -lfreetype... not found
configure: error: FreeType development files not found. Fonts will not be built.
Use the --without-freetype option if you really want this.
citizenzed@debianzed ~/Downloads/wine-1.3.33 $ make
make: *** No targets specified and no makefile found. Stop.

So, as per above it never "said I could run 'make'" and there's what happens when I try. Am I supposed to load that wine-1.3.33 folder with other stuff too? There were a lot of lines and quite a few said "no"

[wolverine_tech]

I had the exact same error when compiling on Debian Wheezy. I added the proper 'sid' repository, updated the source list and installed libfreetype6 (or perhaps libfreetype6-dev). Tried compiling again & went through without any glitch.

Look for my post on http://forums.debian.net/viewtopic.php? ... ne#p389774
See if that helps.

[Anthrogue]

I had the exact same error when compiling on Debian Wheezy. I added the proper 'sid' repository, updated the source list and installed libfreetype6 (or perhaps libfreetype6-dev). Tried compiling again & went through without any glitch.

Look for my post on http://forums.debian.net/viewtopic.php? ... ne#p389774
See if that helps.

Cool... followed those instructions to add the 'sid' repository. I was missing libfreetype6-dev. Now configure executed and "make" is still running in terminal. A question about this from the other thread:

Also, I commented out (#) the "deb-src http://ftp.ca.debian.org/debian sid main contrib non-free" line /etc/apt/sources.list as I want to keep tracking testing. (Hope that does not break anything.)

What does that mean exactly? That once you installed libfretype6-dev, you then blocked that in the /ect/apt/sources.list? Put a # in front of entry? Wanted to understand logic and syntax behind this remark. What moves one to comment out the thing?

Ok.. so "make" worked. I then acquired checkinstall and ran the "checkinstall make install"

======================== Installation successful ==========================

Copying documentation directory...
./
./LICENSE
./VERSION
./AUTHORS
./README
./ANNOUNCE
./COPYING.LIB
chown: changing ownership of `/var/tmp/tmp.2EaRcoY3s1/package//usr/share/doc/wine/VERSION': Operation not permitted
chown: changing ownership of `/var/tmp/tmp.2EaRcoY3s1/package//usr/share/doc/wine/LICENSE': Operation not permitted
chown: changing ownership of `/var/tmp/tmp.2EaRcoY3s1/package//usr/share/doc/wine/ANNOUNCE': Operation not permitted
chown: changing ownership of `/var/tmp/tmp.2EaRcoY3s1/package//usr/share/doc/wine/AUTHORS': Operation not permitted
chown: changing ownership of `/var/tmp/tmp.2EaRcoY3s1/package//usr/share/doc/wine/COPYING.LIB': Operation not permitted
chown: changing ownership of `/var/tmp/tmp.2EaRcoY3s1/package//usr/share/doc/wine/README': Operation not permitted
chown: changing ownership of `/var/tmp/tmp.2EaRcoY3s1/package//usr/share/doc/wine': Operation not permitted

Copying files to the temporary directory...OK

Stripping ELF binaries and libraries...OK

Compressing man pages...OK

Building file list...OK

Building Debian package...OK

Installing Debian package... FAILED!

*** Failed to install the package

Do you want to see the log file?

Not sure what happened. Everything seemed ok and then "FAILED!"

[wolverine_tech]

I had the exact same error when compiling on Debian Wheezy. I added the proper 'sid' repository, updated the source list and installed libfreetype6 (or perhaps libfreetype6-dev). Tried compiling again & went through without any glitch.



[quote....What moves one to comment out the thing?

That is a very good question. Thanks for asking.

I wanted to keep tracking the testing repository after installing wine. Since the libfreetype6 package was in the unstable ('sid') repository at that time, we needed add it to install libfreetype6. But after compiling Wine, I wanted to ensure that my source list points to the testing repository only (and not the 'sid' repository). Hence I commented out that line. (One could also simply delete that repository from the source list.) Using Debian I've always felt it's a bad idea to one's source list pointing to stable, testing and unstable at the same time. Mixing these repositories results in a wrecked system sooner or later.

My system with Debian Testing installed has been running like a champ since the first installation, For a pure Debian install, you could install apt-listbugs and ensure that not buggy updates are installed without prompting for a confirmation first. But I guess with Mint's update packs for LMDE, the updates are well tested compared to vanilla debian updates.

(Although I do not use LMDE, it is Mint's most promising project. If Debian's CUT (Constantly Usable Testing) project does not materialize, I'll probably switch to LMDE soon.)

I hope I could answer your question.