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

Jump to bottom

[WIP] Mesa and xorg updates #56005

Closed
wants to merge 13 commits into from
Closed

[WIP] Mesa and xorg updates #56005

wants to merge 13 commits into from

Conversation

ikervagyok
Copy link
Contributor

Motivation for this change

update graphics stack before 19.03 gets split off.

Things done

most of this is already tested, but only on a single amd apu.

working on getting mesa-19.0-rc4 into shape, would be a nice thing to have mesa 19 imho, if it gets released in time.

  • 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.

@ikervagyok
Copy link
Contributor Author

@lheckemann should we try to get mesa 19.0 into nixpkgs for the 19.03 release or rather stay with 18.3.3 and update to 18.3.4 if it gets released?

@rnhmjoj
Copy link
Contributor

rnhmjoj commented Feb 18, 2019

We usually update mesa only when it reaches the x.y.1. 19.0.0 is considered a development release.

@ikervagyok
Copy link
Contributor Author

@rnhmjoj thanks for this info - so i'll just stick to mesa 18.x.y in this pr

@vcunat
Copy link
Member

vcunat commented Feb 18, 2019

18.3.4 was released today.

@vcunat
Copy link
Member

vcunat commented Feb 18, 2019

BTW, these updates are too large rebuilds to go to master directly, IIRC.

@ikervagyok ikervagyok mentioned this pull request Feb 18, 2019
Merged
10 tasks
@ikervagyok
Copy link
Contributor Author

rebased onto staging, new pr is #56022

@ikervagyok ikervagyok closed this Feb 19, 2019
@vcunat
Copy link
Member

vcunat commented Feb 19, 2019

For future reference, it's possible to do everything without closing a PR. Force-pushing is allowed, and when you edit the title you can change the target branch.

@ikervagyok
Copy link
Contributor Author

@vcunat didn't know i could change the branch - thanks! will remember for the next time ;)

@ikervagyok ikervagyok mentioned this pull request Feb 21, 2019
Closed
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@lovek323 lovek323 Awaiting requested review from lovek323

@vcunat vcunat Awaiting requested review from vcunat

Assignees
No one assigned
Labels
8.has: package (new) 10.rebuild-darwin: 501+ 10.rebuild-darwin: 1001-2500 10.rebuild-linux: 501+ 10.rebuild-linux: 5001+
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@ikervagyok @rnhmjoj @vcunat @GrahamcOfBorg