We need the equivalent of https://code.puri.sm/pureos/firefox-esr/src/master/browser/branding/official/content/about.png.

Regarding license: Please open Document properties, and fill out "Metadata" and "License".

Thanks! That SVG is usable as-is to generate all but one of the PNGs.

I don't understand which timeline you are talking about.

If you have an SVG image then I need that, yes.

This issue is believed fixed with the recent upgrade of PureBrowsr to version 52.5.0esr-1pureos1.

texlive-full in PureOS green is now 2017.20171128-1.

PureBrowser has been repackaged, based on a newer Firefox: Please test if this issue persist.

@mak I believe you are the one orchestrating what constitutes "default install of PureOS".

@mak I believe you are the one orchestrating what constitutes "default install of PureOS".

@mak I believe you are the one orchestrating what constitutes "default install of PureOS".

@mak I believe you are the one orchestrating what constitutes "default install of PureOS".

For the record, I do not personally agree with this issue (I don't use said addon myself): This issue is derived from T147 which in turn is derived from a request by @zlatan.todoric

Consider this issue to be about privacy (T110 is about nonfree services which duckduckgo is as well)

While it might be colateral, this issue is separate from issue T147 tracking the PureBrowser package restructuring.

As explained by Matthias on irc, package ban is source-specific: Banning Debian as source of firefox-esr continue to make sense and does not block upload of same-named firefox-esr ourselves.

Package purebrowser now (since release 52.5.0esr-1pureos1) depends on neither xul-ext-ublock-origin nor xul-ext-adblock-plus.

Package purebrowser used to depend on package xul-ext-ublock-origin (and xul-ext-adblock-plus too? See issue T108), but we better solver this independently from PureBrowser, to provide the freedom of opt-out to _not_ installing the plugin.

This issue was originally reported as part of issue T108 but separated: We better solver this independently from PureBrowser, to provide the freedom of opt-out to _not_ installing the plugin.

This issue was originally reported as T108 but separated: We better solver this independently from PureBrowser, to provide the freedom of opt-out to _not_ installing the plugin.

Inclusion of Privacy Badger now tracked as separate issue T271.

Inclusion of LibreJS addon now tracked as separate issue T270.

Now that PureBrowser has bumped to version 52.5.0, please test if this issue still persist.

Those PNG images look like they were generated from a vector-based source. Also, they lack information about copyright holder and licensing.

Thanks, I will check out those files, and get back to you...

whoops, sorry - meant to ping @francois

@geppuzo ping!

@francois can you have a look at this?

Ok, I take over from here. Pick something fun to work on (or take a break, I am sure noone minds!).

Thanks for reporting this!

Reason for my cautious wording of comment T147#4606 was concern for you: You have fought this issue for a long time and mentioned frustration about it on irc recently. I want to help but am genuinely uncertain what you consider helpful here.

Thanks for raising the issue here.

I see 3 options:

@chris.lamb Please do tell me if you would like me to finalize the packaging that I have succesfully test-built.

Previus comment updated to clarify the sloppy and confusing use of "fail".

No as in not-how-Debian-maintainer-intended-for-sid - e.g. causing rendering artifacts.

It seems *only* renaming package will fail (EDIT: or so I guess - it regenerates control file dropping build-dependency on gcc-6) due to our change of target suite, and (at least, haven't tried yet) this patch is needed:

This issue seems _not_ solved: Current povray package in PureOS green is 1:3.7.0.4-2pureos1 (the version which I explicitly requested to _drop_ as part of this issue).

I am planning plenty more cleanup of that kind, but wait until _after_ we get endorsement from FSF to not confuse things.

Status "invalid" more accurate than "closed".