bug: updating home configuration blocked by insecure python packages.

[aleeusgr]

Are you following the right branch?

• [X] My Nixpkgs and Home Manager versions are in sync

Is there an existing issue for this?

• [X] I have searched the existing issues

Issue description

My goal is to update my system to have latest package versions.

to do this I run nix flake update and then #nixos-rebuild switch

At last update I got an error described at Issue 65 I could get around by adding python to permittedInsecurePackages

Following the discussion here I could trace the problem to a referrer package:

11:00 $ nix-store -q --referrers /nix/store/ab6lv49nxl8gw4xjijhqla1lqcrg73j5-home-manager-path
/nix/store/fkvwjbfdsv5rkh4532nszyn4jiym7qqi-hm_fontconfigconf.d10hmfonts.conf

more details are in the Issue 65 linked above.

what I could do to avoid depending on python2?

Thanks

Maintainer CC

No response

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.1.52, NixOS, 23.11 (Tapir), 23.11.20230911.3a2786e`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - channels(root): `"nixos-22.11"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

[zmrocze]

I'm on 23.11 as well and getting:

error: builder for '/nix/store/bjzmj9xzs90jd95wlaaxrk9vmwa15p7j-home-manager-path.drv' failed with exit code 25;
       last 1 log lines:
       > error: collision between `/nix/store/qp5zys77biz7imbk6yy85q5pdv7qk84j-python3-3.11.6/bin/pydoc' and `/nix/store/f9466pgc2mpmn4xlm90pj9ajgkjjdvvj-python3-3.11.6-env/bin/pydoc'
       For full logs, run 'nix log /nix/store/bjzmj9xzs90jd95wlaaxrk9vmwa15p7j-home-manager-path.drv'.
error: 1 dependencies of derivation '/nix/store/bzdnb68smmd2qkmwxwybzjgs5bzayydd-home-manager-generation.drv' failed to build

related?

[stale[bot]]

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.