Thanks for the idea, I'm not in a hurry and don't have a desire to
hand-jam upstream versions of firefox onto desktops. I just need to
track progress on the patch release and report an ETA to our cyber
security team.
I just figured CentOS had a fancy devops CI/CD system somewhere that I
could keep tabs on to watch what's going on as patches get built,
tested and published. Seems like all the cool kids are doing that
kind of stuff these days.
> From: Alice Wonder <alice@xxxxxxxxxxxxxx>
> To: centos@xxxxxxxxxx
> Cc:
> Bcc:
> Date: Mon, 2 Jul 2018 07:31:20 -0700
> Subject: Re: Firefox 60.0.1.0 ESR Progress?
> On 07/02/2018 06:57 AM, Sean wrote:
> > Is there a way to track CentOS's progress on RHSA-2018-2113?
> >
> > https://access.redhat.com/errata/RHSA-2018:2113
> >
> > Thanks!
> > _______________________________________________
> > CentOS mailing list
> > CentOS@xxxxxxxxxx
> > https://lists.centos.org/mailman/listinfo/centos
> >
>
> This is what I do and it works well, script run as root after
> downloading compiled tarball from upstream.
>
> ------
> #!/bin/bash
>
> TMP=`mktemp -d /tmp/ff.XXXXXXXX`
> mv $1 ${TMP}/
>
> pushd ${TMP}
>
> FFOX=`echo $1 |sed -e s?"\.tar\.bz2"?""?`
>
> tar -jxf ${1}
>
> chown -R root:root firefox
>
> mv firefox /usr/local/${FFOX}
>
> popd
>
> pushd /usr/local
>
> rm -f firefox && ln -s ${FFOX} firefox
>
> popd
>
> rm -rf ${TMP}
> ---------
>
> $1 is the FireFox downloaded from upstream (compiled)
>
> Installing it as root means I am safe from malware over-writing bits of
> it, but I do have to manually download.
>
> /usr/local/firefox/firefox then starts it - and old versions are
> preserved in case something breaks (I just change which one the
> /usr/local/firefox link points to - though I almost never have to revert)
>
> It's not RPM but there are too many advantages to newer FireFox for me
> to wait.
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
