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

packageOverrides no longer respected by aliases #18316

Closed
edolstra opened this issue Sep 5, 2016 · 3 comments
Closed

packageOverrides no longer respected by aliases #18316

edolstra opened this issue Sep 5, 2016 · 3 comments
Assignees
Labels
0.kind: regression Something that worked before working no longer 1.severity: blocker
Milestone

Comments

@edolstra
Copy link
Member

edolstra commented Sep 5, 2016

For example, in all-packages.nix we have:

dbus_tools = self.dbus.out;
dbus_daemon = self.dbus.daemon;

while in nixos/modules/config/no-x-libs.nix we have:

nixpkgs.config.packageOverrides = pkgs:
  { dbus = pkgs.dbus.override { x11Support = false; }; };

In NixOS 16.09, the override to dbus is no longer propagated to dbus_tools and dbus_daemon. Thus these continue to use libX11. This is a regression from 16.03. (Workaround in ba70ce2.)

Changing self back to pkgs restores the 16.03 behaviour, where overrides did propagate properly.

So should we change self back to pkgs everywhere, or should self be fixed?

@edolstra edolstra added this to the 16.09 milestone Sep 5, 2016
@domenkozar
Copy link
Member

@nbp

@edolstra edolstra added 1.severity: blocker 0.kind: regression Something that worked before working no longer and removed 0.kind: bug labels Sep 5, 2016
@nbp
Copy link
Member

nbp commented Sep 5, 2016

I left a comment on ba70ce2#commitcomment-18902806 .

The easiest solution for the release would be to revert to patches that made these aliases, and add a test to ensure that aliases are expected to alias the overwritten packages, and not the original packages.

To solve this issue, we would either have to move aliases.nix after customOverride, or maybe add a second fix-point to resolve dependencies separately.

@nbp
Copy link
Member

nbp commented Sep 5, 2016

This issue is caused by #14398

@bjornfor bjornfor added 0.kind: regression Something that worked before working no longer and removed 0.kind: regression Something that worked before working no longer labels Sep 6, 2016
@nbp nbp self-assigned this Sep 10, 2016
bjornfor pushed a commit to bjornfor/nixpkgs that referenced this issue Sep 23, 2016
…rriden packages.

(cherry picked from commit 5c6bcee)

There weres some conflicts, I fixed them.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0.kind: regression Something that worked before working no longer 1.severity: blocker
Projects
None yet
Development

No branches or pull requests

4 participants