Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
mariadb-10.1.9 won't install because of conflicting mysql_config binaries #12072
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
linuxfood
Jan 1, 2016
Contributor
For now I've locally forked the config for mariadb to change the cp to a mv.
|
For now I've locally forked the config for mariadb to change the |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
would changing mysql_config to mariadb_config be the right fix? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
linuxfood
Jan 2, 2016
Contributor
@mogorman The two programs are literally identical. As far as I can tell, it's just invalid to have it in both output paths. The comment in the commit doesn't make sense to me. @wkennington could you elaborate a little on the intended purpose of the change?
My trivial one line change of 'cp' -> 'mv' at least makes it possible to create the user environment, but, I don't know if I've broken something else since I haven't tried to build any other expression that depends on mariadb yet.
|
@mogorman The two programs are literally identical. As far as I can tell, it's just invalid to have it in both output paths. The comment in the commit doesn't make sense to me. @wkennington could you elaborate a little on the intended purpose of the change? My trivial one line change of 'cp' -> 'mv' at least makes it possible to create the user environment, but, I don't know if I've broken something else since I haven't tried to build any other expression that depends on mariadb yet. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vcunat
Jan 2, 2016
Member
I assume that you don't need mariadb.lib in the user env and mariadb.out is enough, but that's rather a side step.
|
I assume that you don't need |
referenced
this issue
Jan 9, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
retrry
Mar 2, 2016
Contributor
I do too get this error still and I can't install mysql to user profile.
$ nix-env -iA nixos.mysql
installing ‘mariadb-10.1.9’
building path(s) ‘/nix/store/0l8vqmcqng2ykiws4hxhavpzzh4mq4sh-user-environment’
Wide character in die at /nix/store/64jc9gd2rkbgdb4yjx3nrgc91bpjj5ky-buildenv.pl line 79.
collision between ‘/nix/store/b9799ll2ji4s505s6vy27wsh8zy8wsnz-mariadb-10.1.9-lib/bin/mysql_config’ and ‘/nix/store/6833bdiydb9ldv1j5dzgzqg1y1yh514d-mariadb-10.1.9/bin/mysql_config’; use ‘nix-env --set-flag priority NUMBER PKGNAME’ to change the priority of one of the conflicting packages
builder for ‘/nix/store/vv3akfnfbvbqym1p50iind80l5q2wfd0-user-environment.drv’ failed with exit code 255
error: build of ‘/nix/store/vv3akfnfbvbqym1p50iind80l5q2wfd0-user-environment.drv’ failed
|
I do too get this error still and I can't install mysql to user profile.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vcunat
Mar 6, 2016
Member
NixOS/nix#815 will give us a nice tool to specify that we only want mariadb.out when installing into a user env.
|
NixOS/nix#815 will give us a nice tool to specify that we only want |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
HittingSmoke
Mar 13, 2016
Is there still no fix for this aside from forking the config? Trying to get Nix setup to handle my web servers.
HittingSmoke
commented
Mar 13, 2016
|
Is there still no fix for this aside from forking the config? Trying to get Nix setup to handle my web servers. |
This was referenced Apr 18, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
nicholasknight
Apr 28, 2016
I started playing with Nix and quickly ran into this on OS X. :(
Is this heavily dependent on internal development work in Nix, or is there something I, as someone not familiar with the internals, can do to move it forward?
If the answer is "take over MariaDB maintenance in nixpkgs because the current maintainer(s) lack time", that's something I'm willing to try. I just really don't want to maintain a separate fork and make all our engineers use it for an indeterminate period of time.
nicholasknight
commented
Apr 28, 2016
|
I started playing with Nix and quickly ran into this on OS X. :( Is this heavily dependent on internal development work in Nix, or is there something I, as someone not familiar with the internals, can do to move it forward? If the answer is "take over MariaDB maintenance in nixpkgs because the current maintainer(s) lack time", that's something I'm willing to try. I just really don't want to maintain a separate fork and make all our engineers use it for an indeterminate period of time. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
davidak
Apr 28, 2016
Contributor
@nicholasknight in general, you can fix issues and create pull requests.
but this is not a build problem. it's a collision of two outputs. i think you need deep understanding of how nix works to fix this.
|
@nicholasknight in general, you can fix issues and create pull requests. but this is not a build problem. it's a collision of two outputs. i think you need deep understanding of how nix works to fix this. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment|
how hard would it be to wrap one of the outputs with |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vcunat
May 16, 2016
Member
The problem is that nix installs all outputs by default. That is changeable with recent nix, after NixOS/nix#815.
|
The problem is that nix installs all outputs by default. That is changeable with recent nix, after NixOS/nix#815. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
domenkozar
Jun 1, 2016
Owner
@vcunat do we have a workaround for this except for reverting multiple outputs?
|
@vcunat do we have a workaround for this except for reverting multiple outputs? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vcunat
Jun 2, 2016
Member
nix-env -f . -iA mariadb works for me now. I think it's because of NixOS/nix#815.
Note: this problem was there long before merging the closure-size branch.
|
Note: this problem was there long before merging the closure-size branch. |
vcunat
closed this
Jun 2, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
vcunat
Jun 2, 2016
Member
Note: it "works" because now only .out is installed and not .lib. If you forced installing both, you would run into this problem again, but I can't see why someone might want both outputs in their user env.
|
Note: it "works" because now only |
linuxfood commentedJan 1, 2016
Seems like some days ago there was a split of the output paths for mariadb that makes it impossible to install or upgrade mariadb as near as I can tell.
This is the commit: e97b63a
collision between ‘/nix/store/mkmiziygv2v9hsq14xjs4lyjj12ncgsc-mariadb-10.1.9-lib/bin/mysql_config’ and ‘/nix/store/kbl8fh8mpdmisrhbaarg14v17024mbnq-mariadb-10.1.9/bin/mysql_config’; use ‘nix-env --set-flag priority NUMBER PKGNAME’ to change the priority of one of the conflicting packagesThe suggested fix doesn't work because there's only one package in question.