I found the following workaround: 1. add the following to /etc/apt/sources.list (add hardy repository): deb http://archive.ubuntu.com/ubuntu hardy main restricted universe multiverse
2. add to/create the file /etc/apt/preferences (make sure only packages you manually upgrade from the hardy repo get upgraded, not all of them): Package: * Pin: release a=hardy Pin-Priority: 400 3. run apt-get update 4. run the following: sudo apt-get install -t hardy beid-tools The last step will update a lot of things, amongst which libc6. So far, this has not caused problems for me, but ymmv. I guess this also makes this package unsuited for backporting. I also had to do a reboot before the new packages would work, but since then all eid-supported stuff runs flawless: signing mails in thunderbird, logging on to taxonweb, .... You may also want to remove the hardy repository from sources and the lines in the preferences file after the upgrade, as it may cause some trouble when you should decide to upgrade your ubuntu in the future. In case you run into problems and want to rollback the changes: 1. Make sure you don't have the Hardy repositories present in your "/etc/apt/sources.list" (see step 1 of installation.) 2. Edit "/etc/apt/preferences" to contain the following, and delete any references to Hardy: Package: * Pin: release v=7.10 Pin-Priority: 1100 Note that the release should be changed for whatever release you are using (eg., 7.04 for feisty, 7.10 as shown for gutsy.) You should specify this by version number and not by name because otherwise you need separate entries for gutsy, gutsy-updates, etc. 3. Run "apt-get dist-upgrade". This will downgrade your packages. 4. Edit "/etc/apt/preferences" and remove the pin you added in step 2, or just remove the file completely. You should now be back at your current release. ps: most of the above info comes from this thread on ubuntu forums: http://ubuntuforums.org/showpost.php?p=4293754&postcount=325 -- beid segfault in 64 bits mode https://bugs.launchpad.net/bugs/115984 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
