On Mon, May 5, 2014 at 12:37 PM, Tom Roche <tom_ro...@pobox.com> wrote:
> > summary: > > 1. Repo=debian-testing was the fix. > 2. Where to put bug on package=icedtea-netx ? > 3. Pointers to recommended docs on setting up a VM for running a VPN are > appreciated. > > details: > > https://lists.debian.org/debian-user/2014/05/msg00294.html [Sven Joachim > Sun, 04 May 2014 22:21:45 +0200] > >>> [you have an] older version of libgif4 than the one in jessie/sid[, > >>> since] Multiarch support was enabled in 4.1.6-11 back in December 2013. > > https://lists.debian.org/debian-user/2014/05/msg00302.html [Tom Roche > Sun, 04 May 2014 17:10:28 -0400] > >> [So] > > >> 1. add [repository=`deb http://ftp.debian.org/debian/ testing main > contrib non-free`] > >> 2. update packages > >> 3. update package=libgif4:i386 > >> 4. install package=icedtea-7-plugin:i386 > >> 5. remove repository > > >> [correct?] > > It was. After > > NEW_REPO_LINE='deb http://ftp.debian.org/debian/ testing main contrib > non-free' > NEW_REPO_LIST_FN='debian-testing.list' # files in .../sources.list.d/ need > extension=list > REPO_LIST_DIR='/etc/apt/sources.list.d' > > NEW_REPO_LIST_FP="${REPO_LIST_DIR}/${NEW_REPO_LIST_FN}" > sudo touch ${NEW_REPO_LIST_FP} > #sudo echo -e "${NEW_REPO_LINE}\n" > ${NEW_REPO_LIST_FP} > # above fails: gotta run the whole thing as `sudo`: > #sudo sh -c "echo -e '${NEW_REPO_LINE}\n' > ${NEW_REPO_LIST_FP}" > # above fails: prepends '-e ' > sudo sh -c "echo '${NEW_REPO_LINE}\n' > ${NEW_REPO_LIST_FP}" > cat ${NEW_REPO_LIST_FP} > sudo aptitude update > > I was able to install {libgif4:amd64 , libgif4:i386} cleanly. Installing > java for the F5NAP was a bit more annoying--package=icedtea-netx handles > file=/usr/bin/policyeditor IMHO buggily--but I got that installed, and > symlinked the appropriate IcedTeaPlugin.so for firefox-3.6.28. Not > particularly clean, but now the VPN (F5NAP plus 32-bit firefox) works. (And > still works, after backing out the repository change, and re-updating > packages.) > Glad it worked for you. > I would like to know where to report the problem with {icedtea-netx , > /usr/bin/policyeditor} to prevent problems for OP, so, if you know, please > lemme know where/how best to do that. > Use your own judgement. It's not a mortal sin to have the devs decide the problem is not where you thought it was. > Regarding the suggestions to install the VPN via a 32-bit VM and "network > appropriately": the problem is, I don't know how to do that. I would > appreciate pointers to doc "for next time," or for OP who might stumble > upon this thread. By contrast, I knew I could make the above/multiarch > approach work, since I'd done it before. Unfortunately, I hadn't > *documented* it before, but I did this time. Hopefully multiarch support > will be {even better, more transparent} in future. > > FWIW, Tom Roche <tom_ro...@pobox.com> > https://wiki.debian.org/SystemVirtualization Admittedly, it does take some time to wade through, so, yeah, starting now to get ready for next time is a good idea. And good luck with getting the people at work to help you update the VPN tools. -- Joel Rees Be careful where you see conspiracy. Look first in your own heart.
