On Wed, Dec 18, 2013 at 05:35:14PM -0500, Lennart Sorensen wrote:
> On Fri, Dec 13, 2013 at 07:54:13PM +0000, Bart Martens wrote:
> > It may not be how you expect it to be, but security updates are supported :
> >
> > update-flashplugin-nonfree --install
> > update-pepperflashplugin-nonfree --install
>
> Is that supposd to do something?
>
> lennartsorensen:/tmp# update-pepperflashplugin-nonfree --install
> lennartsorensen:/tmp# update-pepperflashplugin-nonfree --status
> lennartsorensen:/tmp#
>
> I am confused. The pepperflashplugin sounds interesting to try, but I
> don't see it doing anything.
>
> Maybe this gives a clue:
>
> lennartsorensen:/tmp# update-pepperflashplugin-nonfree --install
> + trap return_0 0
> + whoami
> + [ root = root ]
> + getopt -o iusfvq --long
> install,uninstall,status,fast,verbose,quiet,beta,unstable,unverified -n
> update-pepperflashplugin-nonfree -- --install
> + getopt_temp= --install --
> + eval set -- --install --
> + set -- --install --
> + ACTION=none
> + fast=no
> + verbose=no
> + quiet=no
> + variant=stable
> + verified=yes
> + [ true ]
> + ACTION=--install
> + shift
> + [ true ]
> + shift
> + break
> + [ --install != none -a 0 -eq 0 ]
> + [ no != yes ]
> + [ no != yes ]
> + latestfile=latest-stable-verified.txt
> + [ yes != no ]
> + mktemp -d /tmp/pepperflashplugin-nonfree.XXXXXXXXXX
> + UNPACKDIR=/tmp/pepperflashplugin-nonfree.zCzZvamIvV
> + grep -q ^/tmp/pepperflashplugin-nonfree\.
> + echo /tmp/pepperflashplugin-nonfree.zCzZvamIvV
> + cd /tmp/pepperflashplugin-nonfree.zCzZvamIvV
> + [ no != yes ]
> + trap die_hard_with_a_cleanup interrupted INT
> + cachedir=/var/cache/pepperflashplugin-nonfree
> + wgetquiet= -q
> + wgetfast=-t 3 -T 15
> + wgetalways= -nd -P .
> + wgetprogress= -v --progress=dot:default
> + [ --install = --install -o --install = --status ]
> + + sedcut -d -e s/,/./g -f
> 2
> + grep LNX
> + strings /usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so
> + installed=
> + [ -f /var/cache/pepperflashplugin-nonfree/latest-stable-verified.txt ]
> + chromeversion=0
> + flashversion=0
> + mkdir -p var/lib/apt/lists var/cache/apt/archives etc/apt/apt.conf.d
> etc/apt/preferences.d
> + cat
> + cat
> + gpg --quiet --no-permission-warning --homedir etc/apt --import
> /usr/lib/pepperflashplugin-nonfree/pubkey-google.txt
> + [ no != yes ]
> + APT_CONFIG=apt.conf apt-get --quiet --quiet update
> + stdouterr=W: Failed to fetch
> http://dl.google.com/linux/chrome/deb/dists/stable/Release Unable to find
> expected entry 'main/binary-powerpc/Packages' in Release file (Wrong
> sources.list entry or malformed file)
>
> E: Some index files failed to download. They have been ignored, or old ones
> used instead.
> + return_0
> + return 0
>
> Oh yes, the google chrome archive doesn't like multiarch. Would have
> been nice with some kind of output in case of an error.
Changing:
cat > etc/apt/sources.list <<-EOF
deb http://dl.google.com/linux/chrome/deb/ stable main
EOF
into:
cat > etc/apt/sources.list <<-EOF
deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
EOF
has fixed it. amd64 could of course be i386 or something else too,
whichever Debian architecture it is run on.
Should I go file a bug report?
--
Len Sorensen
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
