Age | Commit message (Collapse) | Author |
|
|
|
the upstream name is 'open-comic-font'
the FSDG does not require software names to be changed
|
|
sources no longer available
|
|
these libre replacement packages do not seem to modify or remove anything important
|
|
|
|
|
|
|
|
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
Build fails without them. Haven't found any binary blobs in these paths.
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
|
|
Because data reporting is now hopefully disabled via build config
options, reviewed some of the related preference overrides:
Removed the following preferences:
datareporting.healthreport.uploadEnabled
defined only if MOZ_SERVICES_HEALTHREPORT is defined,
see modules/libpref/init/all.js
datareporting.healthreport.about.reportUrl
Removed upstream, see:
https://bugzilla.mozilla.org/show_bug.cgi?id=1352497
Can be found only in some test files
datareporting.healthreport.documentServerURI
Probably have been removed too, documentServerURI can
now be found only in obsolete documentation and some tests
healthreport.uploadEnabled
cannot be found alone in source tree.
Only datareporting.healthreport.uploadEnabled can be found.
datareporting.policy.dataSubmissionEnabled
defined only if MOZ_DATA_REPORTING is defined,
see modules/libpref/init/all.js
datareporting.healthreport.service.enabled
could find only in some test files
datareporting.policy.firstRunTime
datareporting.policy.dataSubmissionPolicyVersion
could not find in source tree
Also checked the following preferences:
toolkit.telemetry*
still available in the code, so have not removed them
pref("toolkit.telemetry.server_owner", "User");
This is just a nitpicking probably, because upstream preference says
"Mozilla" instead. And that is not true, because of the following
override in vendor.js :)
pref("toolkit.telemetry.server", "127.0.0.1");
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
|
|
MOZ_SERVICES_HEALTHREPORT and MOZ_NORMANDY are two missing bits to
undefine MOZ_DATA_REPORTING, which is defined if any one of
healthreporting, crashreporting, telemetry reporting, or Normandy are
set. Crashreporting and telemetry reporting have been already disabled.
Some data reporting related preferences and code are enabled when
MOZ_DATA_REPORTING is defined, for example.
These "features" are for Mozilla users only, they don't make much sense
for Iceweasel users. Probably even harmful for them and Mozilla too,
because I don't think Mozilla is interested in data reporting spam from
non-Firefox users.
I'm not sure if these features can be classified as back doors or
spyware in GNU FSDG terms, but that's another thing to consider.
Also added a check that fails the build if some of those features are
not disabled in configuration.
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
|
|
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
|
|
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
|
|
Apart from upstream updates to list.json, there is also a bit of
preparation for the next significant change of how search engines are
handled upstream. 78.0 enabled this new mechanism, but 78.0.1 disabled
it again because of [1]. For details see [2]. It looks like Mozilla
can now update the list of available and visible search engines
remotely. So removing all engines except Wikipedia and DuckDuckGo just
to avoid surprises in future.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1649393
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1542235
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
|
|
This is to reduce maintenance burden. The tab is going to have new
content in each new release, and as can be seen with this release, some
news items can contain references or mention nonfree stuff. Instead of
patching each new release, just removing it for now. Those who want to
see the news can find them (and more) on the upstream release notes
webpage.
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
|
|
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
|
|
Signed-off-by: Andreas Grapentin <andreas@grapentin.org>
|
|
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
|
|
too old, non-git version more updated, there's no interest/importance in this pkg
Signed-off-by: David P <megver83@parabola.nu>
|
|
the non-git version is more updated, it seems there's no interest nor importance in this pkg
Signed-off-by: David P <megver83@parabola.nu>
|
|
the non-git version is more up-to-date, it seems there's no interest in this pkg
Signed-off-by: David P <megver83@parabola.nu>
|
|
|
|
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The changes were imported from the AUR package.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
Instead of fixing checksums each time the kernel
configuration is updated, we can simply skip them as they
come from the same git repository than the PKGBUILD itself,
so it should introduce any security issues.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
This regression was introduced by the following commits:
63359d4f8 kernels: re-enable the b43 and b43-legacy drivers
2e94284f5 kernels: re-enable the tg3 driver
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The b43 and b43-legacy drivers were removed because their
corresponding upstream drivers loads a nonfree firmware.
However linux-libre-firmware has a free firmware
(ucode5.fw) that is used by both drivers.
The b43 and b43-legacy driver are also typically enabled
by Trisquel and Jason Self's linux-libre repository.
Note that some kernel parameters like qos=0 might be
necessary to make it work.
This regression was introduced in linux-libre by the
following commit:
32075365d upgpkg: libre/linux-libre 4.16.9_gnu-1
The drivers were added back by importing affected parts
from the following upstream kernels and configurations:
- config in linux-armv7 from Arch Linux ARM
- config.i686 in linux from Arch Linux 32
- config from linux from Arch Linux
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
The tg3 driver was removed because its upstream driver
loads a nonfree firmware. However with linux-libre, the
driver works fine without any nonfree firmware, at least
on some computers like the HP NC6320.
That driver is also typically enabled by Trisquel and
Jason Self's linux-libre repository.
This regression was introduced in linux-libre by the
following commit:
32075365d upgpkg: libre/linux-libre 4.16.9_gnu-1
The following configuration:
CONFIG_TIGON3=m
CONFIG_TIGON3_HWMON=y
is used in the following upstream kernels and
configurations:
- config in linux-armv7 from Arch Linux ARM
- config.i686 in linux from Arch Linux 32
- config from linux from Arch Linux
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
|
|
|
|
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
Signed-off-by: David P <megver83@parabola.nu>
|
|
_x86_64_skip_pgo can still be flipped manually for faster builds if
anybody wants that. Let's just follow upstream by default.
|
|
|
|
|
|
While Firefox Lockwise itself is libre-licensed (apps, website, etc),
the references to Android and iOS versions lead to Google Play and Apple
app stores, all of which execute some JavaScript that is not clearly
licensed, so can be considered nonfree.
These references can be found on about:logins page as items in "..."
menu, and on about:protections page in promo cards.
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.
|
|
Apart from the update according to the upstream changes, also removed
the reference to Firefox Developer Edition on Google Play because:
1. It appears to have the same freedom issues as regular Firefox;
2. Google Play webpage executes some JavaScript that's not clearly
licensed, so can be considered nonfree.
|
|
|