Wednesday, October 29, 2008

More W{,h}ine

In my last post, I discussed the criticisms made by a Wine supporter. However, there was one criticism that I did not address. Apparently, you can download older releases. Well, I will try one out now. Since I do not want to compile my Wine, I would like a precompiled binary. Let's see what I can find.

I now present my handy-dandy guide to Wine installation on Ubuntu!

Alright, first we will navigate to

Now, we will look at the page to see where we can download Wine binaries. Then, we click on "Get Wine Now" in the "Download" panel on the left-hand side of the screen.

Now, we arrive at the download page. We will look through all the offered binaries to find which one we want.

Since Ubuntu is the distribution I use, we will click on that one.

Now, we are at the download page for Ubuntu binaries. Everything looks good, right.

Hmmm... Let's read the fine print.

Warning: These are beta packages

The packages here are beta packages. This means they will periodically suffer from regressions, and as a result an update may break functionality in Wine. If the latest stable release of Wine (currently Wine 1.0.1) works for you, then you may not want to use these beta packages.

Hmm... These packages must be the kissing cousin of the one that broke audio in Fallout 2. Well, I guess I could try them if I really had to, but let's see what else is available.

At the very bottom of the page, we find something interesting.

Older .deb packages

Since the APT repository can only hold the latest packages, older versions of the packages are available at the WineHQ .deb packages archive.

You can install downloaded packages by double-clicking on them.

Well now, apparently you can install older, more stable versions. They just mention them only at the very bottom because . . .

Now, click on the link

As of (2008-10-29-08-48 EST), you will see the following page.

Well, that's no good! I guess we will have to try the beta packages after all!

After scrolling to the top of the page, we will read the directions.

Open the Software Sources menu by going to System->Administration->Software Sources. Then select the Third Party Software tab and click Add.

Administration->Software Sources->Third Party Software" border="0">

Then, copy and paste one of the lines below depending on which version you are running.

For Ubuntu Intrepid (8.10):
deb intrepid main #WineHQ - Ubuntu 8.10 "Intrepid Ibex"

For Ubuntu Hardy (8.04):
deb hardy main #WineHQ - Ubuntu 8.04 "Hardy Heron"

For Debian Lenny (5.0):
deb lenny main #WineHQ - Debian 5.0 "Lenny"

Well, that looks easy enough! Since I am using 8.04, our entry should look like this.

Swell, now that should do it, but not quite. Let's read more instructions.

After adding the repository, you also need to add the key for the repository to your system's list of trusted keys.

Download and save Scott Ritchie's key to your desktop. Then open the Authenticationimport key file, and select the key file you just saved (Scott Ritchie.gpg). It is safe to delete this file after doing this step. tab, click

Administration->Software Sources->Authentication" border="0">

Click close to finish, and then reload the package information. If you have Wine installed, the system's update manager will now inform you of the latest Wine beta release and prompt you to upgrade. If you haven't installed Wine yet, go to Applications->Add/Remove and search for Wine.

So, we have to download a GPG key, eh? Okay, let's download it the key As of (2008-10-29-09-06 EST), you should see the following:

$ wget
=> `Scott Ritchie.gpg'
Connecting to||:80... connected.
HTTP request sent, awaiting response... Read error (Connection reset by peer) in headers.

(try: 2) => `Scott Ritchie.gpg'
Connecting to||:80...
Repeat ad infinitum

Well, now that is no good! Maybe, APT can work without it. Let's find out. Click the "Close" button in the bottom-right corner of the "Software Sources" window. Then, click the "Reload" button in the menu that pops up.

Click on the "Close" button in the two windows to complete the installation.

That wasn't too hard, was it? Now, you should have a stable, fully functional Wine that is capable of running any Platinum-rated application you throw at it . . . . . or not.

EDIT: I changed the parentheses to curly-brackets to better reflect a list of possible matches in a regular expression. Comment if this is not correct.


oiaohm said...

Boy you are unlucky/lucky I don't know how to put it.

Server kinda has been doing the running and not running at the moment. Thinking that all chatter to the server is done threw http: .

Basically your were purely lucky to get down current beta at the moment.

Server is a little run on limit resources. Only reason why the Ubuntu third party repo exists is the issues we have had with the main Ubuntu repo shipping out defect with backport patches equaling broken stuff and they don't allow wine package maintainer to submit packages straight to there repo.

Audio not working is noted in the FAQ of wine. Don't install with pulseaudio. Latest beta and 1.0.1 does have some patches that remove most of that issue.

Now ask yourself why can we not add installation warning messages to deb packages. We would of course love to. Warning updating this package may cause you application to stop working in wine.

oiaohm said...

Little extra note when you do get threw to the server. Now this is what you call just evil bad luck. If a server was going to have it once and 12 months play up it would have to happen when a reporter or blogger is there.

Turns out that older ubuntu wine packages do install perfectly on newer ubuntu's. Like hardy on current. Of course newer on old don't work.

Simple example that there is some ABI compatibility there. Since wine packages are all signed with own key we get around the key lock of ubuntu and debian. Lot of cases its just 1 package for all a particular deb systems. Only limitation is the features wine users.

Lack of ABI in Linux is a Distribution created problem. Its mostly installer. Lot of libs in Linux do have a stable ABI.

thepld said...

Server kinda has been doing the running and not running at the moment. Thinking that all chatter to the server is done threw http: .

When the hell has that ever been a problem with an Apple or MS project? More excuses.

If a closed source company was even partially this incompetent, they would be bankrupt.

oiaohm said...

Number 1 the binaries provided to Ubuntu is the only one sitting on at that location without a simple work around.

Mandrivas Sits on no issue on Mandriva when you click on a rpm package installer comes up first.

Slackware ok same tgz file clicked on comes up with option of installer or archive manager so it can live on source forge.

Even Debian allows wine developers to submit directly into there SID branch. I cannot redirect you to SID because SID packages will not work on Ubuntu without chrooting.

Ubuntu is a little wrong click on deb and instead of installer you get archive manager. You have to right click select. To prevent that for new users we have used APT storage that gives users a option to select in synaptic current stable ie 1.0.1 and current beta. We have no fast way to restore that.

I am sorry to have to say that domain name has been attacked many times. Parties behind the attacks are unknown. These attacks have been traffic redirection to even fake servers. This time it is black holing of the packets.

First messages were before it was confirmed the server is still up and not under major load. Server gone unstable have happened once before and would have be corrected by now.

Over the complete of that location providing the wine files for ubuntu it would have been only the second glitch caused by hardware failure. This is the 20 attack. Last time we were lucky that some people could get to the correct server and if you go the correct IP you could get there too. This time they have stepped it up a level.

Thinking that repo has only existed due to private donation independent to codeweavers.

Now I really don't know who would bother attacking wine. It also some of those attacks synced with when ever past Linuxhater talked about Wine. So the cause has followed here.

Yes many closed source companies get destroyed this way. For wine its a pest.

Reason for the long term plan to move to LSB 4.0/1 installers so we can use larger harder to attack mirror systems.

thepld said...

"Now I really don't know who would bother attacking wine. It also some of those attacks synced with when ever past Linuxhater talked about Wine. So the cause has followed here."

So now you're blaming it on a conspiracy of people who hate Linux? Your illogic knows no bounds.

oiaohm said...

Something that has happened many times over.

Its not illogical. Single site being picked on. I repeat single site. Yet out of the all the events the longest lasting ones all synced with Linux Haters blog. Lot of the smaller events seams to have been trial runs testing that it worked before the trigger.

Its either a really strange bad luck or someone following the blog did it.

Then as soon as this Blog covered Wine short time following again it happened again.

Also funny enough problem causer disappeared fairly quickly after 2 message here.

I did not say someone who hated Linux. The target is Wine or that host. Strange for that host that its only the wine site effected. That is for sure Linux Hater could talk about all other projects and there weakest points would not get hit.

There are many reason why someone could be doing it. There are more questions than answers. Why would someone waste so much effort. It is not like wine is perfect or anything.

It is not like MS update server never has been blocked before by attackers. It has. Internet is the internet from time to time you get pest who just upset things.

Some of those pests when caught are simply insane working off triggering events.

Now if you cannot work out what my message before this one is about. Its simple undermining. The attack itself is long term pointless. To attackers you have to be blunt.

Catching them is not the only way to get rid of a network pest. If something I say seams illogical there is a reason. Either I know something you don't or I am bluffing.

Anonymous said... what you're saying is Wine sux because a webserver was down? Is this your time on the Internet or something? Donation-driven sites sometimes don't have six nines of uptime. Geez, I'm lucky to get 95% uptime out of my actual ISP, in a major metropolitan area.

C'mon, there's plenty about wine to criticize without stooping to this kid's stuff.