E: Error file: apt-build/main i386 Packages File not found

[Jerry L Kreps]

I downloaded some deb packages (TeamView, Skype, and others) and installed them using Gdebi and dpkg. Afterward I began getting the msg in the subject line of this post when I did "sudo apt-get update". (I've used visudo to add myself to the sudoers file.)

The problem was that using Gdebi or dpkg to install downloaded deb packages like Skype causes an entry to be put into the sources listed in the repository:
"file:/var/cache/apt-build/repository apt-build main"

I unchecked that line, closed the dialog, and reloaded the repository. The error msg went away. Another option is to add a "main" directory in the location indicated but I don't want to modify the system file structure under /var.

(Edit: I should add that several were i386 packages.)

[Euan Thoms]

Which architeceture are you using 64bit or 32bit? Do you mean Teamview or Teamviewer?

I know from other people (never used it myself) that Skype installation can be tricky on 64bit debian. It's perhaps best to use smxi. There's a wiki entry for smxi on the Kwheezy website. It will (or should) do the hard work for you, perhaps checking dependencies and avoiding known issues.

Teamviewer should be more straight-forward, version 7 is already installed in Kwheezy.

Some of these commercial app packagers do funny things. They don't really know how to package properly in some cases.

Thanks for sharing the workaround/fix.

[Jerry L Kreps]

Duh! Typo! Teamviewer.

I'm so used to apps like Teamviewer NOT being pre-installed on a distro that I didn't even bother to look for it. I just went to the site and downloaded ver 7 for 64 bit Debian. Works great.

I've taken more time to look around KWheezy and it is amazingly well populated with a wide variety of apps and tools. More than any distro I've previously used, and I've been using Linux since May of 1998.

I'm running 64bit.

The skype installation was easy once I found the Debian version, skype-debian_4.2.0.11-1_i386.deb Works great as well.

Since I installed the Liqourix 3.11.8 kernel I wanted to use the SystemSettings grub editor to set my previous kernel to be the default boot, so I installed kcm-grub2_0.6.4-wheezy3_amd64.deb and it works great as well.

I'm really enjoying KWheezy, and talking it up with my friends.

Euan, you've done a fantastic job with it!

[Euan Thoms]

Thanks for the praise. I'm glad it's working well for you.

I tried out the liquorix 3.10.x kernel last night in virtualbox. Unfortaunately there was a few DKMS modules failing to build. In particular; neither virtualbox from stable or backports will build their kernel modules. The ATI?AMD fglrx driver also fails to build. I hope these isssues can be fixed / worked around soon. I will wait a bit longer then have another try, perhaps make an update script for Kwheezy to get onto a 3.10 kernel. I had placnned to make a GUI utility to get onto backports smoothly, we'll have to see how easy that will be. I'll wait for backports to mature a bit more yet.

[Jerry L Kreps]

"I'll wait for backports to mature a bit more yet."

Sounds like a wise approach. It will certainly avoid wasting time doing something that someone upstream is already doing.