Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pharo 7 with Firefox's moz2d #56935

Closed
wants to merge 83 commits into from
Closed

Pharo 7 with Firefox's moz2d #56935

wants to merge 83 commits into from

Conversation

rydnr
Copy link
Contributor

@rydnr rydnr commented Mar 6, 2019

Motivation for this change

Current Pharo package does not work with Pharo 7+ images.
It needs a more recent VM, and many Pharo packages need moz2d to be available for them to work on Pharo 7 or later. For example, GToolkit.

With this PR Pharo 7 or 8
Unfortunately, I've been unable to make Pharo 7 or 8 work on i686. The VM segfaults when performing calls to freetype library. However, that doesn't work with the current Pharo package either. I'll create a new PR once I solve it.

Things done

I added "pharo-cog", "pharo-spur32" and "pharo-spur64" to my NixOS environment.systemPackages.
Once the system is rebuilt, I tested both 32b and 64b images:

for arch in 64 32; do
  mkdir ${arch};
  pushd ${arch};
  if [ "${arch}" == "32" ]; then path=""; else path="64/"; fi
  for version in 6 7 8; do
    curl get.pharo.org/${path}/${version}0 | bash && mv Pharo.image ${arch}-${version}.image && mv Pharo.changes ${arch}-${version}.changes
  done
  popd;
done

I then tried to open each 32b Pharo images with pharo-spur32, and the 64b images with pharo-spur64.

  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

lheckemann and others added 30 commits February 25, 2019 22:50
Master commit: e52396c.  It's bugfixes, basically.
treewide: use runtimeShell instead of stdenv.shell whenever possible for 19.03
It used to be huge, but current measurements reveal a 48mb NAR

(cherry picked from commit 0ea3b395372cc1e400340c8b04d17c1277bf3f03)
System rebuilds currently fail due to collisions.
See also #56432.

(cherry picked from commit 029adf9)
has been broken by dadc7eb

(cherry picked from commit 1d1c909)
nvidia_x11 and persistenced were modified to provide binaries which can be
mounted inside a docker-container to be executed there.

most ldconfig-based discovery of bundled nvidia libraries is patched out

ldconfig itself is patched to be able to deal with patchelf'ed libraries
See https://sourceware.org/bugzilla/show_bug.cgi?id=23964
(cherry picked from commit 515be3b)
(cherry picked from commit 48f1455)
(cherry picked from commit fce6329)
(cherry picked from commit 1a7c2b3)
This reverts commit 0b91fa4, reversing
changes made to 183919a.
(cherry picked from commit 23b2a60)
[19.03] Mark Riak and Riak-cs as insecure
(cherry picked from commit 6ad4e3e)
It's basically just bugfixes, and 19.03 hasn't even been released yet.
... into release-19.03.  (Cherry-picked from 35cf2c8.)
The branch is affected by the stdenv change differentiating the numbers,
and I believe consistency with master will be good here.
(cherry picked from commit 52ea2f5)
With the openssl upgrade to 1.0.2r / 1.1.1b the tinc pre-release version
stopped working due to a bug in tinc where an encryption function was
used during decryption. I submitted a patch upstream [1] but that wasn't
released yet.

[1] http://git.tinc-vpn.org/git/browse?p=tinc;a=commit;h=2b0aeec02d64bb4724da9ff1dbc19b7d35d7c904

(cherry picked from commit 447c210)
a vlaue between 0 and 4 to help debug problems

(cherry picked from commit 20bbfc3)
The overwriteprotocol option can be used to force Nextcloud to generate
URLs with the given protocol. This is useful for instances behind
reverse proxies that serve Nextcloud with HTTPS.

In this case Nextcloud can't determine the proper protocol and it needs
to be configured manually.

(cherry picked from commit b42c24f)
First release in over a year, not sure of changelog.

Release announcement:
http://lists.litech.org/pipermail/radvd-announce-l/2019-February/000045.html

(cherry picked from commit e8f4e5a)
(cherry picked from commit bc7d45e)
taku0 and others added 22 commits March 2, 2019 12:01
(cherry picked from commit 03bbab8)
(cherry picked from commit d59a40c)
(cherry picked from commit 692a763)
(cherry picked from commit b01302b)
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/ibus-typing-booster/versions

(cherry picked from commit 6766409)
Signed-off-by: Maximilian Bosch <maximilian@mbosch.me>
redmine: 3.4.8 -> 3.4.9 & 4.0.1 -> 4.0.2
(cherry picked from commit 7093aa5)
According to xsecurelock's configure.ac file, each of the add
dependencies are used to:

- libXrandr: XRandR provides information about monitor layouts and is
strongly recommended on systems which can use more than one monitor
(which includes most laptops).
- libXext: The X Synchronization extension is used to get per-device idle
times. Used by until_nonidle only.
- libXScrnSaver: The X11 Screen Saver extension is used to turn off the
screen saver when X11 handles screen blanking (e.g. via timeout) anyway.
Saves CPU power.

Adding libXrandr fixes an issue where locking a screen in a multi
monitor setup results in the prompt information to not be in the middle
of the screen. The other dependencies are not tested if they fixed
something, however since upstream recommends than I think it is fair to
include them also.

(cherry picked from commit d2d7fed)
Semi-automatic update generated by
https://github.com/ryantm/nixpkgs-update tools. This update was made
based on information from
https://repology.org/metapackage/brave/versions

(cherry picked from commit edccde3)
(cherry picked from commit df77847)
(cherry picked from commit 86199e0)
(cherry picked from commit 63bd0d5)
(cherry picked from commit 81b6dd7)
graylog-plugin-aggregates: 2.3.0 -> 2.4.0
graylog-plugin-auth-sso: 2.4.2 -> 3.0.0
(cherry picked from commit 76b3c57)
(cherry picked from commit 9efddfa)
If our old Nix can’t evaluate the Nixpkgs channel, try the fallback
from the new channel /first/. That way we can upgrade Nix to a newer
version and support breaking changes to Nix (like seen in the upgrade
o Nix 2.0).

This change should be backported to older NixOS versions!

(cherry picked from commit 475c8aa)
…l further testing, since it is currently broken (segfaults)
@rydnr rydnr requested a review from infinisil as a code owner March 6, 2019 07:42
@rydnr
Copy link
Contributor Author

rydnr commented Mar 6, 2019

I should have done a rebase instead of a merge, sorry.

@rydnr
Copy link
Contributor Author

rydnr commented Mar 7, 2019

I'm closing it and create a new one.

@rydnr rydnr closed this Mar 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet