[Dev] [PATCH] Iceweasl 77.0.1 update

[grizzlyuser]

On Thursday, June 25, 2020 7:09 AM, bill-auger <bill-auger at peers.community> wrote:
>     On Wed, 03 Jun 2020 21:04:29 +0000 grizzlyuser wrote:
>
>
> > const release = {
> > -- title: "What’s New in DevTools (Firefox 76)",
> > -+ title: "What’s New in DevTools (Iceweasel 76)",
> > +- title: "What’s New in DevTools (Firefox 77)",
> > ++ title: "What’s New in DevTools (Iceweasel 77)",
> > linkText: "Read more",
> >
> > -   linkUrl: `https://developer.mozilla.org/docs/Mozilla/Firefox/Releases/76?${utmParams}`,
> >
> > -   linkUrl: `https://developer.mozilla.org/docs/Mozilla/Firefox/Releases/77?${utmParams}`,
> >     features: [
> >
>
> presumably, those literal version numbers are going to require
> maintenance for every release - it may be better to process that
> file (devtools/client/whats-new/src/main.js) with sed after
> patching, like: sed 's|Firefox |Iceweasel |'
>
> On Wed, 03 Jun 2020 21:04:29 +0000 grizzlyuser wrote:
>
> > const dev = {
> > title: "Experimental Features in Firefox Developer Edition",
> > linkUrl: `https://www.mozilla.org/firefox/developer/?${utmParams}`,
> >
> > -   linkText: "Get DevEdition",
> > -   features: [
> > -   {
> >     -- header: `Full Asynchronous Stacks in Debugger`,
> >     -- description: `Step through event, timeout and ....`,
> >     -- href: `https://developer.mozilla.org/ ....`,
> >     +- header: `Cross-browser CSS compatibility audit`,
> >     +- description: `Analyze your CSS for cross-browser ....`,
> >     +- href: `https://discourse.mozilla.org/ ....`,
> >
> > -   },
>
> likewise with that 'dev' struct - to minimize future maintenance,
> maybe its better to leave it mainly in tact, but to clobber its
> definition, something like:
>
> -   const dev = {
>
> -   const dev = {} ; const dsfg_dev = {
>
>     or if that causes problems, just clobber the important data, like:
>
>     const dev = {
>     const dev = {
>     ....
>
>
> -   };
>
> -   }.merge( { linkUrl: '', linkText: '' , features: [] } ) ;

Good points. I'm not happy either with this manual patch updates
each new release. Will try to rework that after a new release,
that is expected in Tuesday. Meanwhile, if anybody wants, feel
free to change it even before that.

>     On Wed, 03 Jun 2020 21:04:29 +0000 grizzlyuser wrote:
>
>
> > Removed them for now. Could also change the URLs to open the Lockwise
> > website, but although libre licensed, it still has large links to
> > nonfree app stores and Firefox on the front page, so that wouldn't be a
> > huge improvement.
>
> i dunno what Lockwise is - is it a built-in or default feature; and
> is it so difficult to use that it needs documentation? - we could
> add an article on the parabola wiki explaining it; or maybe its fine
> without any URL in that slot

Lockwise is a new password manager. It's built into Firefox, and
also has companion apps for iOS and Android. The apps appear to
be free software, but they are hosted on Google and Apple app
stores and on GitHub. It looks like all these websites serve
nonfree JS, so being unable to find good replacement URLs, I
just removed links and menu items that open these websites.
Whoever wants the apps is still free to search the web to find
them.

On Thursday, June 25, 2020 2:28 PM, bill-auger <bill-auger at peers.community> wrote:

> at least one of the patches do not apply onto firefox 77.0.1
>
> | 1 out of 1 hunk FAILED -- saving rejects to file
> browser/locales/en-US/browser/protections.ftl.rej
>
> the patches in this thread are applied onto the master
> branches of abslibre and the iceweasel branding git repo now,
> and the branding package is in place on the repp server; but it
> appears that at least one of the patches in abslibre will need
> re-working to allow the build start

I checked out the commit before these changes, then downloaded
my patch from Dev ML archives and applied it. prepare() ran
without errors. Then ran a diff between patched version and the
one from the origin/HEAD. It looks like whitespace has been
munged at some point before applying it to the master branch. I
guess either whitespace has to be fixed, or libre.patch has to
be applied in PKGBUILD with -l option, like this:

patch -lNp1 -i "$srcdir/libre.patch"