How did you set avast to update?
In fact I did nothing, I’ve just install it, typed the serial number and that’s all. Maybe it’s worth to mention that deb file which I downloaded from avast webpage didn’t want to install, so I created another deb using alien (from rmp archive) and that time it was successful.
That's rather a cosmetic problem:
- Debian on x86 was for ages i386-backward-compatible. Thus, all *.deb packages were expected to contain "i386" in the architecture tag. Our package uses this tag as well (and thus can be installed on these classic Debian distributions).
- but, recently, many new and quite immature distributions adopted the *.deb format, but they deliberately changed the x86 compatibility level - and expect different architecture tags.
The package contents or our package stays the same, but if You re-generate the *.deb on Your distribution, Your alien will insert that "amd64" or similar tag there, instead of original "i386", and thus "solves" the problem (better solution is to use --force-architecture switch for dpkg).
If You think about it, Your re-generated package isn't correct - our package contains x86 IA-32 parts, and thus was properly labelled "i386" to be compatible with original Debian x86 distributions. All later x86 derivates such as Ubuntu, Kubuntu or whatever else _should_take_ this architecture as well, because they claim backward compatibility. We can, of course, offer also pre-cooked packages for such cases, but they will differ in the tag only (will be labelled "amd64" instead of "i386", although they are internally "i386").
===============
In my humble opinion, I see no extra profit in usage of 64-bit distributions on 64-bit machines nowadays. The performance gain is usually minimal or even negative, binaries are larger, and for the majority of applications it's not important how big the virtual address space is. And, You will face ABI-compatibility problems with many binary-distributed applications.
PC
