│  ├─ libgdal [3.5.3|3.6.0] would require
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  └─ openssl >=1.1.1s,<1.1.2a , which can be installed;
│  ├─ libgdal [3.5.3|3.6.0] would require
│  │  ├─ cfitsio >=4.1.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.0,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ hdf5 >=1.12.2,<<IP_ADDRESS>a0  with the potential options
│  │  │  ├─ hdf5 1.12.2, which can be installed (as previously explained);
│  │  │  ├─ hdf5 1.12.2 conflicts with any installable versions previously reported;
│  │  │  └─ hdf5 [1.12.2|1.14.0], which can be installed (as previously explained);
│  │  ├─ libpq >=14.5,<15.0a0  with the potential options
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.12, which cannot be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  └─ libpq 14.5, which can be installed (as previously explained);
│  │  ├─ poppler >=22.11.0,<22.12.0a0 , which can be installed;
│  │  └─ proj >=9.1.0,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal [3.4.3|3.5.3|3.6.0|3.6.1|3.6.2] would require
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ openssl >=1.1.1s,<1.1.2a , which can be installed;
│  │  └─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  ├─ libgdal 3.4.3 would require
│  │  ├─ cfitsio >=4.1.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.1.0,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal [3.5.3|3.6.0|3.6.1|3.6.2] would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.1.0,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal [3.5.3|3.6.1|3.6.2|3.6.3] would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.1.1,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal [3.5.3|3.6.3|3.6.4|3.7.0] would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.2,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.2.0,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal [3.5.3|3.6.3] would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.2,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.1.1,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal 3.5.3 would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ hdf5 >=1.12.2,<<IP_ADDRESS>a0  with the potential options
│  │  │  ├─ hdf5 1.12.2, which can be installed (as previously explained);
│  │  │  ├─ hdf5 1.12.2 conflicts with any installable versions previously reported;
│  │  │  └─ hdf5 [1.12.2|1.14.0], which can be installed (as previously explained);
│  │  ├─ poppler >=22.11.0,<22.12.0a0 , which can be installed;
│  │  └─ proj >=9.1.0,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal 3.5.3 would require
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ openssl >=1.1.1s,<1.1.2a , which can be installed;
│  │  └─ pcre2 >=10.37,<10.38.0a0 , which conflicts with any installable versions previously reported;
│  ├─ libgdal 3.5.3 would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ hdf5 >=1.12.2,<<IP_ADDRESS>a0  with the potential options
│  │  │  ├─ hdf5 1.12.2, which can be installed (as previously explained);
│  │  │  ├─ hdf5 1.12.2 conflicts with any installable versions previously reported;
│  │  │  └─ hdf5 [1.12.2|1.14.0], which can be installed (as previously explained);
│  │  ├─ libpq >=14.5,<15.0a0  with the potential options
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.12, which cannot be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  └─ libpq 14.5, which can be installed (as previously explained);
│  │  ├─ poppler >=22.11.0,<22.12.0a0 , which can be installed;
│  │  └─ proj >=9.1.0,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal 3.5.3 would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.37,<10.38.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.1.0,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal 3.6.0 would require
│  │  ├─ cfitsio >=4.1.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ libpq >=14.5,<15.0a0  with the potential options
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.12, which cannot be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  └─ libpq 14.5, which can be installed (as previously explained);
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.1.0,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal 3.6.0 would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.1,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ libpq >=14.5,<15.0a0  with the potential options
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.12, which cannot be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  ├─ libpq 14.5, which can be installed (as previously explained);
│  │  │  └─ libpq 14.5, which can be installed (as previously explained);
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.1.0,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal 3.6.4 would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.12.0,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.3.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  ├─ libgdal [3.6.4|3.7.0|3.7.1] would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.12.0,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.2.1,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal [3.6.4|3.7.0] would require
│  │  ├─ cfitsio >=4.2.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.11.2,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.2.1,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal [3.7.1|3.7.2] would require
│  │  ├─ cfitsio >=4.3.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.12.0,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.2.1,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgdal [3.7.2|3.7.3|3.8.0] would require
│  │  ├─ cfitsio >=4.3.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.12.0,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ pcre2 >=10.40,<10.41.0a0 , which conflicts with any installable versions previously reported;
│  │  └─ proj >=9.3.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  ├─ libgdal 3.7.3 would require
│  │  ├─ cfitsio >=4.4.0,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ libexpat >=2.6.2,<3.0a0 , which cannot be installed (as previously explained);
│  │  ├─ pcre2 >=10.43,<10.44.0a0 , which can be installed;
│  │  ├─ proj >=9.3.1,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  └─ tiledb [>=2.21.0,<2.22.0a0 |>=2.21.1,<2.22.0a0 ] with the potential options
│  │     ├─ tiledb [2.21.0|2.21.1|2.21.2|2.22.0], which can be installed (as previously explained);
│  │     └─ tiledb [2.21.2|2.22.0|...|2.25.0], which cannot be installed (as previously explained);
│  ├─ libgdal 3.7.3 would require
│  │  ├─ cfitsio >=4.4.0,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ libexpat >=2.6.2,<3.0a0 , which cannot be installed (as previously explained);
│  │  ├─ openssl >=3.3.0,<4.0a0 , which conflicts with any installable versions previously reported;
│  │  ├─ pcre2 >=10.43,<10.44.0a0 , which can be installed;
│  │  ├─ proj >=9.4.0,<<IP_ADDRESS>a0  with the potential options
│  │  │  ├─ proj 9.4.0, which can be installed;
│  │  │  └─ proj [9.4.0|9.4.1], which cannot be installed (as previously explained);
│  │  └─ tiledb [>=2.21.1,<2.22.0a0 |>=2.22.0,<2.23.0a0 ] with the potential options
│  │     ├─ tiledb [2.21.0|2.21.1|2.21.2|2.22.0], which can be installed (as previously explained);
│  │     ├─ tiledb [2.21.2|2.22.0|...|2.25.0], which cannot be installed (as previously explained);
│  │     └─ tiledb [2.22.0|2.23.0|2.24.0], which cannot be installed (as previously explained);
│  ├─ libgdal 3.7.3 would require
│  │  ├─ cfitsio >=4.4.0,<<IP_ADDRESS>a0 , which can be installed;
│  │  ├─ libexpat >=2.6.1,<3.0a0 , which cannot be installed (as previously explained);
│  │  ├─ pcre2 >=10.43,<10.44.0a0 , which can be installed;
│  │  └─ proj >=9.3.1,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  ├─ libgdal [3.7.3|3.8.0] would require
│  │  ├─ cfitsio >=4.3.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ geos >=3.12.0,<<IP_ADDRESS>a0 , which can be installed;
│  │  └─ pcre2 >=10.42,<10.43.0a0 , which conflicts with any installable versions previously reported;
│  ├─ libgdal 3.7.3 would require
│  │  ├─ cfitsio >=4.3.1,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ libexpat >=2.6.1,<3.0a0 , which cannot be installed (as previously explained);
│  │  ├─ pcre2 >=10.43,<10.44.0a0 , which can be installed;
│  │  └─ proj >=9.3.1,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  ├─ libgdal [3.7.3|3.8.0] would require
│  │  ├─ cfitsio >=4.3.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  └─ pcre2 >=10.42,<10.43.0a0 , which conflicts with any installable versions previously reported;
│  ├─ libgdal 3.9.0, which cannot be installed (as previously explained);
│  └─ libgdal 3.9.1, which cannot be installed (as previously explained);
├─ libgoogle-cloud is installable with the potential options
│  ├─ libgoogle-cloud 2.26.0, which cannot be installed (as previously explained);
│  ├─ libgoogle-cloud 2.23.0, which cannot be installed (as previously explained);
│  ├─ libgoogle-cloud 2.24.0, which cannot be installed (as previously explained);
│  ├─ libgoogle-cloud 2.25.0, which cannot be installed (as previously explained);
│  ├─ libgoogle-cloud [2.12.0|2.17.0] would require
│  │  └─ libprotobuf >=4.24.4,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgoogle-cloud 1.35.0 would require
│  │  └─ libprotobuf >=3.19.3,<3.20.0a0 , which can be installed;
│  ├─ libgoogle-cloud [1.36.0|1.37.0|1.38.0|1.39.0] would require
│  │  └─ libprotobuf >=3.19.4,<3.20.0a0 , which can be installed;
│  ├─ libgoogle-cloud [1.39.0|1.39.1] would require
│  │  └─ libprotobuf >=3.20.0,<3.21.0a0 , which can be installed;
│  ├─ libgoogle-cloud [1.40.0|1.40.1|...|2.1.0] would require
│  │  └─ libprotobuf >=3.20.1,<3.21.0a0 , which can be installed;
│  ├─ libgoogle-cloud [2.1.0|2.2.0] would require
│  │  └─ libprotobuf >=3.21.5,<3.22.0a0 , which can be installed;
│  ├─ libgoogle-cloud 2.2.0 would require
│  │  └─ libprotobuf >=3.21.6,<3.22.0a0 , which can be installed;
│  ├─ libgoogle-cloud 2.3.0 would require
│  │  └─ libprotobuf >=3.21.7,<3.22.0a0 , which can be installed;
│  ├─ libgoogle-cloud [2.3.0|2.4.0] would require
│  │  └─ libprotobuf >=3.21.9,<3.22.0a0 , which can be installed;
│  ├─ libgoogle-cloud [2.10.0|2.10.1|...|2.9.1] would require
│  │  └─ libprotobuf >=3.21.12,<3.22.0a0 , which can be installed;
│  ├─ libgoogle-cloud [2.11.0|2.12.0] would require
│  │  └─ libprotobuf >=4.23.2,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgoogle-cloud [2.12.0|2.17.0] would require
│  │  └─ libprotobuf >=4.24.3,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgoogle-cloud 2.12.0 would require
│  │  └─ libprotobuf >=4.23.3,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgoogle-cloud 2.12.0 would require
│  │  └─ libprotobuf >=4.23.4,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgoogle-cloud [2.12.0|2.17.0|2.21.0] would require
│  │  └─ libprotobuf >=4.25.1,<<IP_ADDRESS>a0 , which cannot be installed (as previously explained);
│  ├─ libgoogle-cloud [2.21.0|2.22.0] would require
│  │  └─ libprotobuf >=4.25.2,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgoogle-cloud 2.22.0 would require
│  │  └─ openssl >=3.2.1,<4.0a0 , which conflicts with any installable versions previously reported;
│  └─ libgoogle-cloud 2.5.0 would require
│     └─ libprotobuf >=3.21.10,<3.22.0a0 , which can be installed;
├─ libgrpc is installable with the potential options
│  ├─ libgrpc 1.62.2, which cannot be installed (as previously explained);
│  ├─ libgrpc [1.59.1|1.59.2|1.59.3|1.60.0] would require
│  │  └─ libprotobuf >=4.24.4,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgrpc 1.49.1 would require
│  │  └─ libprotobuf >=3.21.9,<3.22.0a0 , which can be installed;
│  ├─ libgrpc [1.50.1|1.51.1] would require
│  │  └─ libprotobuf >=3.21.10,<3.22.0a0 , which can be installed;
│  ├─ libgrpc [1.50.1|1.51.1|...|1.54.3] would require
│  │  └─ libprotobuf >=3.21.12,<3.22.0a0 , which can be installed;
│  ├─ libgrpc 1.55.0 would require
│  │  └─ libprotobuf >=4.23.1,<4.24.0a0 , which can be installed;
│  ├─ libgrpc [1.55.0|1.55.1|1.56.0] would require
│  │  └─ libprotobuf >=4.23.2,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgrpc [1.56.0|1.56.1|1.56.2|1.57.0] would require
│  │  └─ libprotobuf >=4.23.3,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgrpc [1.57.0|1.57.1] would require
│  │  └─ libprotobuf >=4.23.4,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgrpc [1.58.1|1.58.2] would require
│  │  └─ libprotobuf >=4.24.3,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgrpc [1.60.0|1.60.1] would require
│  │  └─ libprotobuf >=4.25.1,<<IP_ADDRESS>a0 , which cannot be installed (as previously explained);
│  ├─ libgrpc [1.61.0|1.61.1|1.61.2] would require
│  │  └─ libprotobuf >=4.25.2,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libgrpc [1.62.0|1.62.1] would require
│  │  └─ openssl >=3.2.1,<4.0a0 , which conflicts with any installable versions previously reported;
│  ├─ libgrpc 1.63.1 would require
│  │  └─ libprotobuf >=5.26.1,<<IP_ADDRESS>a0 , which can be installed;
│  └─ libgrpc 1.64.2 would require
│     └─ libprotobuf >=5.27.2,<<IP_ADDRESS>a0 , which can be installed;
├─ libignition-fuel-tools4 is installable with the potential options
│  ├─ libignition-fuel-tools4 4.6.0 would require
│  │  └─ libignition-common3 >=3.15.1,<4.0a0  with the potential options
│  │     ├─ libignition-common3 3.15.1 would require
│  │     │  └─ libglib >=2.80.0,<3.0a0  with the potential options
│  │     │     ├─ libglib [2.80.2|2.80.3], which cannot be installed (as previously explained);
│  │     │     └─ libglib [2.78.4|2.80.0|2.80.1|2.80.2], which can be installed (as previously explained);
│  │     ├─ libignition-common3 3.15.1 would require
│  │     │  └─ tinyxml2 >=9.0.0,<10.0a0 , which can be installed;
│  │     └─ libignition-common3 3.15.1 would require
│  │        └─ libglib >=2.78.3,<3.0a0  with the potential options
│  │           ├─ libglib [2.80.2|2.80.3], which cannot be installed (as previously explained);
│  │           ├─ libglib [2.78.4|2.80.0|2.80.1|2.80.2], which can be installed (as previously explained);
│  │           └─ libglib [2.78.3|2.78.4] would require
│  │              └─ pcre2 >=10.42,<10.43.0a0 , which conflicts with any installable versions previously reported;
│  ├─ libignition-fuel-tools4 4.6.0 would require
│  │  └─ libprotobuf >=4.24.4,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.0.0 would require
│  │  └─ libprotobuf >=3.11.2,<3.12.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 [4.0.0|4.1.0] would require
│  │  └─ libprotobuf >=3.11.4,<3.12.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.1.0 would require
│  │  └─ libprotobuf >=3.12.1,<3.13.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 [4.1.0|4.2.1] would require
│  │  └─ libprotobuf >=3.13.0,<3.14.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.2.1 would require
│  │  └─ libprotobuf >=<IP_ADDRESS>,<3.14.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.3.0 would require
│  │  └─ libprotobuf >=3.14.0,<3.15.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 [4.3.0|4.4.0] would require
│  │  └─ libprotobuf >=3.16.0,<3.17.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.3.0 would require
│  │  └─ libprotobuf >=3.15.1,<3.16.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.4.0 would require
│  │  └─ libprotobuf >=3.21.5,<3.22.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.4.0 would require
│  │  └─ libprotobuf >=3.20.0,<3.21.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.4.0 would require
│  │  └─ libprotobuf >=3.18.0,<3.19.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.4.0 would require
│  │  └─ libprotobuf >=3.19.1,<3.20.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.4.0 would require
│  │  └─ libprotobuf >=3.19.4,<3.20.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.6.0 would require
│  │  └─ libprotobuf >=3.21.6,<3.22.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.6.0 would require
│  │  └─ libprotobuf >=3.21.12,<3.22.0a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.6.0 would require
│  │  └─ libprotobuf >=4.25.2,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.6.0 would require
│  │  └─ libprotobuf >=4.25.1,<<IP_ADDRESS>a0 , which cannot be installed (as previously explained);
│  ├─ libignition-fuel-tools4 4.6.0 would require
│  │  └─ libprotobuf >=4.24.3,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.6.0 would require
│  │  └─ libprotobuf >=4.23.2,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libignition-fuel-tools4 4.6.0 would require
│  │  └─ libprotobuf >=4.23.4,<<IP_ADDRESS>a0 , which can be installed;
│  └─ libignition-fuel-tools4 4.6.0 would require
│     └─ libprotobuf >=4.23.3,<<IP_ADDRESS>a0 , which can be installed;
├─ libignition-msgs5 is installable with the potential options
│  ├─ libignition-msgs5 5.11.0 would require
│  │  └─ tinyxml2 >=10.0.0,<11.0a0 , which conflicts with any installable versions previously reported;
│  ├─ libignition-msgs5 5.11.0 would require
│  │  └─ libprotobuf >=4.24.4,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libignition-msgs5 5.1.0 would require
│  │  └─ libprotobuf >=3.12.1,<3.13.0a0 , which can be installed;
│  ├─ libignition-msgs5 [5.1.0|5.3.0] would require
│  │  └─ libprotobuf >=3.12.3,<3.13.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.1.0 would require
│  │  └─ libprotobuf >=3.11.2,<3.12.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.1.0 would require
│  │  └─ libprotobuf >=3.11.4,<3.12.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.3.0 would require
│  │  └─ libprotobuf >=3.14.0,<3.15.0a0 , which can be installed;
│  ├─ libignition-msgs5 [5.3.0|5.7.0] would require
│  │  └─ libprotobuf >=3.16.0,<3.17.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.3.0 would require
│  │  └─ libprotobuf >=<IP_ADDRESS>,<3.14.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.3.0 would require
│  │  └─ libprotobuf >=3.13.0,<3.14.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.3.0 would require
│  │  └─ libprotobuf >=3.15.1,<3.16.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.7.0 would require
│  │  └─ libprotobuf >=3.19.1,<3.20.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.7.0 would require
│  │  └─ libprotobuf >=3.18.0,<3.19.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.9.0 would require
│  │  └─ libprotobuf >=3.21.5,<3.22.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.9.0 would require
│  │  └─ libprotobuf >=3.20.0,<3.21.0a0 , which can be installed;
│  ├─ libignition-msgs5 5.11.0 would require
│  │  └─ libprotobuf >=4.23.4,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libignition-msgs5 5.11.0 would require
│  │  └─ libprotobuf >=4.23.3,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libignition-msgs5 5.11.0 would require
│  │  └─ libprotobuf >=4.24.3,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libignition-msgs5 5.11.0 would require
│  │  └─ libprotobuf >=4.25.2,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libignition-msgs5 [5.11.0|5.9.0] would require
│  │  └─ libprotobuf >=3.21.12,<3.22.0a0 , which can be installed;
│  ├─ libignition-msgs5 [5.11.0|5.9.0] would require
│  │  └─ libprotobuf >=4.23.2,<<IP_ADDRESS>a0 , which can be installed;
│  └─ libignition-msgs5 5.11.0 would require
│     └─ libprotobuf >=4.25.1,<<IP_ADDRESS>a0 , which cannot be installed (as previously explained);
├─ libopencv is installable with the potential options
│  ├─ libopencv [4.10.0|4.9.0] would require
│  │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
│  │  └─ libglib [>=2.80.0,<3.0a0 |>=2.80.2,<3.0a0 ] with the potential options
│  │     ├─ libglib [2.80.2|2.80.3], which cannot be installed (as previously explained);
│  │     └─ libglib [2.78.4|2.80.0|2.80.1|2.80.2], which can be installed (as previously explained);
│  ├─ libopencv 4.10.0 would require
│  │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
│  │  └─ libglib >=2.80.3,<3.0a0 , which cannot be installed (as previously explained);
│  ├─ libopencv 4.10.0 would require
│  │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
│  │  └─ qt6-main >=6.7.2,<6.8.0a0  but there are no viable options
│  │     ├─ qt6-main 6.7.2 would require
│  │     │  ├─ alsa-lib >=1.2.12,<1.3.0a0 , which conflicts with any installable versions previously reported;
│  │     │  ├─ libxcb >=1.16,<1.17.0a0 , which conflicts with any installable versions previously reported;
│  │     │  ├─ openssl >=3.3.1,<4.0a0 , which conflicts with any installable versions previously reported;
│  │     │  └─ pcre2 >=10.43,<10.44.0a0 , which can be installed;
│  │     ├─ qt6-main 6.7.2 would require
│  │     │  ├─ alsa-lib >=1.2.12,<1.3.0a0 , which conflicts with any installable versions previously reported;
│  │     │  ├─ libxcb >=1.15,<1.16.0a0 , which can be installed;
│  │     │  ├─ openssl >=3.3.1,<4.0a0 , which conflicts with any installable versions previously reported;
│  │     │  └─ pcre2 >=10.43,<10.44.0a0 , which can be installed;
│  │     └─ qt6-main 6.7.2 would require
│  │        ├─ alsa-lib >=1.2.12,<1.3.0a0 , which conflicts with any installable versions previously reported;
│  │        ├─ icu >=75.1,<76.0a0 , which can be installed;
│  │        ├─ libxcb >=1.16,<1.17.0a0 , which conflicts with any installable versions previously reported;
│  │        └─ openssl >=3.3.1,<4.0a0 , which conflicts with any installable versions previously reported;
│  ├─ libopencv 4.9.0 would require
│  │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
│  │  ├─ libglib >=2.80.0,<3.0a0  with the potential options
│  │  │  ├─ libglib [2.80.2|2.80.3], which cannot be installed (as previously explained);
│  │  │  └─ libglib [2.78.4|2.80.0|2.80.1|2.80.2], which can be installed (as previously explained);
│  │  └─ qt6-main >=6.6.2,<6.7.0a0  but there are no viable options
│  │     ├─ qt6-main [6.6.2|6.6.3] would require
│  │     │  ├─ alsa-lib >=1.2.11,<1.3.0a0 , which conflicts with any installable versions previously reported;
│  │     │  └─ libxcb >=1.15,<1.16.0a0 , which can be installed;
│  │     └─ qt6-main 6.6.2 would require
│  │        ├─ alsa-lib >=1.2.10,<<IP_ADDRESS>a0  with the potential options
│  │        │  ├─ alsa-lib 1.2.12 conflicts with any installable versions previously reported;
│  │        │  ├─ alsa-lib 1.2.11 conflicts with any installable versions previously reported;
│  │        │  └─ alsa-lib 1.2.10, which can be installed;
│  │        └─ pcre2 >=10.42,<10.43.0a0 , which conflicts with any installable versions previously reported;
│  ├─ libopencv 4.9.0 would require
│  │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
│  │  └─ qt6-main >=6.6.3,<6.7.0a0 , which cannot be installed (as previously explained);
│  ├─ libopencv [4.10.0|4.9.0] would require
│  │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
│  │  └─ qt6-main [>=6.7.0,<6.8.0a0 |>=6.7.1,<6.8.0a0 ] but there are no viable options
│  │     ├─ qt6-main 6.7.2, which cannot be installed (as previously explained);
│  │     ├─ qt6-main 6.7.2, which cannot be installed (as previously explained);
│  │     ├─ qt6-main 6.7.2, which cannot be installed (as previously explained);
│  │     ├─ qt6-main 6.7.1 would require
│  │     │  ├─ alsa-lib >=1.2.11,<1.3.0a0 , which conflicts with any installable versions previously reported;
│  │     │  ├─ libxcb >=1.15,<1.16.0a0 , which can be installed;
│  │     │  ├─ openssl >=3.3.0,<4.0a0 , which conflicts with any installable versions previously reported;
│  │     │  └─ pcre2 >=10.43,<10.44.0a0 , which can be installed;
│  │     ├─ qt6-main 6.7.0 would require
│  │     │  ├─ alsa-lib >=1.2.11,<1.3.0a0 , which conflicts with any installable versions previously reported;
│  │     │  └─ openssl >=3.3.0,<4.0a0 , which conflicts with any installable versions previously reported;
│  │     └─ qt6-main 6.7.0 would require
│  │        └─ alsa-lib >=1.2.11,<1.3.0a0 , which conflicts with any installable versions previously reported;
│  ├─ libopencv [4.8.1|4.9.0] would require
│  │  └─ libprotobuf >=4.24.4,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libopencv [3.4.7|3.4.8|...|4.5.1] would require
│  │  └─ qt [5.12.* |>=5.12.1,<5.13.0a0 ], which can be installed (as previously explained);
│  ├─ libopencv [4.2.0|4.5.0] would require
│  │  └─ python_abi 3.6.* *_cp36m, which requires
│  │     └─ python 3.6.* , which can be installed;
│  ├─ libopencv [4.2.0|4.3.0|4.4.0] would require
│  │  └─ pypy3.6 >=7.3.1  with the potential options
│  │     ├─ pypy3.6 7.3.1 would require
│  │     │  └─ openssl >=1.1.1f,<1.1.2a , which can be installed;
│  │     ├─ pypy3.6 7.3.2 would require
│  │     │  └─ openssl >=1.1.1h,<1.1.2a , which can be installed;
│  │     └─ pypy3.6 7.3.3 would require
│  │        └─ openssl >=1.1.1i,<1.1.2a , which can be installed;
│  ├─ libopencv [4.4.0|4.5.0] would require
│  │  └─ pypy3.6 >=7.3.2 , which can be installed (as previously explained);
│  ├─ libopencv 4.5.1 would require
│  │  └─ libprotobuf >=3.15.6,<3.16.0a0 , which can be installed;
│  ├─ libopencv 4.5.2 would require
│  │  └─ libprotobuf >=3.15.8,<3.16.0a0 , which can be installed;
│  ├─ libopencv [4.5.2|4.5.3] would require
│  │  └─ libprotobuf >=3.16.0,<3.17.0a0 , which can be installed;
│  ├─ libopencv 4.5.3 would require
│  │  └─ libprotobuf >=3.18.1,<3.19.0a0 , which can be installed;
│  ├─ libopencv 4.5.3 would require
│  │  └─ libprotobuf >=3.19.1,<3.20.0a0 , which can be installed;
│  ├─ libopencv [4.5.5|4.6.0] would require
│  │  └─ libprotobuf >=3.20.1,<3.21.0a0 , which can be installed;
│  ├─ libopencv 4.5.5 would require
│  │  └─ libprotobuf >=3.20.0,<3.21.0a0 , which can be installed;
│  ├─ libopencv 4.5.5 would require
│  │  └─ libprotobuf >=3.19.4,<3.20.0a0 , which can be installed;
│  ├─ libopencv 4.5.5 would require
│  │  └─ libprotobuf >=3.19.3,<3.20.0a0 , which can be installed;
│  ├─ libopencv 4.6.0 would require
│  │  └─ libprotobuf >=3.21.8,<3.22.0a0 , which can be installed;
│  ├─ libopencv 4.6.0 would require
│  │  └─ libprotobuf >=3.21.5,<3.22.0a0 , which can be installed;
│  ├─ libopencv [4.10.0|4.9.0] would require
│  │  └─ libglib [>=2.80.0,<3.0a0 |>=2.80.2,<3.0a0 ] with the potential options
│  │     ├─ libglib [2.80.2|2.80.3], which cannot be installed (as previously explained);
│  │     └─ libglib [2.78.4|2.80.0|2.80.1|2.80.2], which can be installed (as previously explained);
│  ├─ libopencv [4.10.0|4.9.0] would require
│  │  └─ ffmpeg [>=7.0.0,<8.0a0 |>=7.0.1,<8.0a0 ], which cannot be installed (as previously explained);
│  ├─ libopencv 4.10.0 would require
│  │  └─ libglib >=2.80.3,<3.0a0 , which cannot be installed (as previously explained);
│  ├─ libopencv 4.10.0 would require
│  │  └─ qt6-main >=6.7.2,<6.8.0a0 , which cannot be installed (as previously explained);
│  ├─ libopencv [4.10.0|4.9.0] would require
│  │  └─ qt6-main [>=6.7.0,<6.8.0a0 |>=6.7.1,<6.8.0a0 ], which cannot be installed (as previously explained);
│  ├─ libopencv [4.5.3|4.6.0|...|4.9.0] would require
│  │  └─ libprotobuf >=3.21.12,<3.22.0a0 , which can be installed;
│  ├─ libopencv 4.7.0 would require
│  │  └─ libprotobuf >=4.23.2,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libopencv [4.7.0|4.8.0] would require
│  │  └─ libprotobuf >=4.23.3,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libopencv [4.8.0|4.8.1] would require
│  │  └─ libprotobuf >=4.23.4,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libopencv 4.8.1 would require
│  │  └─ libprotobuf >=4.24.3,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libopencv 4.9.0 would require
│  │  └─ libprotobuf >=4.25.2,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ libopencv 4.9.0 would require
│  │  └─ libprotobuf >=4.25.1,<<IP_ADDRESS>a0 , which cannot be installed (as previously explained);
│  ├─ libopencv 4.9.0 would require
│  │  └─ qt6-main >=6.6.3,<6.7.0a0 , which cannot be installed (as previously explained);
│  └─ libopencv 4.9.0 would require
│     └─ qt6-main >=6.6.2,<6.7.0a0 , which cannot be installed (as previously explained);
├─ libspral is installable with the potential options
│  ├─ libspral [2023.09.07|2024.01.18|2024.05.08], which cannot be installed (as previously explained);
│  ├─ libspral 2023.08.02 would require
│  │  └─ libhwloc >=2.9.1,<<IP_ADDRESS>a0  but there are no viable options
│  │     ├─ libhwloc [2.10.0|2.11.0|2.11.1|2.9.1|2.9.3], which cannot be installed (as previously explained);
│  │     └─ libhwloc 2.9.1 conflicts with any installable versions previously reported;
│  ├─ libspral 2024.05.08 would require
│  │  └─ libhwloc >=2.10.0,<<IP_ADDRESS>a0  with the potential options
│  │     ├─ libhwloc [2.10.0|2.11.0|2.11.1|2.9.1|2.9.3], which cannot be installed (as previously explained);
│  │     └─ libhwloc 2.10.0, which can be installed;
│  └─ libspral 2024.05.08 would require
│     └─ libhwloc >=2.11.0,<<IP_ADDRESS>a0  with the potential options
│        ├─ libhwloc [2.10.0|2.11.0|2.11.1|2.9.1|2.9.3], which cannot be installed (as previously explained);
│        └─ libhwloc 2.11.0, which can be installed;
├─ pcl is installable with the potential options
│  ├─ pcl [1.13.1|1.14.0|1.14.1] would require
│  │  └─ vtk-base >=9.2.6,<<IP_ADDRESS>a0  with the potential options
│  │     ├─ vtk-base 9.2.6 would require
│  │     │  └─ proj >=9.3.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ vtk-base [9.2.6|9.3.0|9.3.1] would require
│  │     │  └─ python >=3.10,<3.11.0a0 , which can be installed;
│  │     ├─ vtk-base [9.2.6|9.3.0|9.3.1] would require
│  │     │  └─ python >=3.11,<3.12.0a0 , which can be installed;
│  │     ├─ vtk-base 9.2.6 would require
│  │     │  ├─ libexpat >=2.5.0,<2.6.0a0 , which requires
│  │     │  │  └─ expat 2.5.0.* , which conflicts with any installable versions previously reported;
│  │     │  └─ proj >=9.3.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ vtk-base 9.2.6 would require
│  │     │  ├─ libexpat [<2.6 |>=2.5.0,<2.6.0a0 ], which cannot be installed (as previously explained);
│  │     │  └─ proj >=9.3.1,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ vtk-base [9.2.6|9.3.0|9.3.1] would require
│  │     │  └─ python >=3.8,<3.9.0a0 , which can be installed;
│  │     └─ vtk-base [9.2.6|9.3.0|9.3.1] would require
│  │        └─ python >=3.9,<3.10.0a0 , which can be installed;
│  ├─ pcl [1.11.1|1.12.0] would require
│  │  └─ vtk [>=9.0.1,<<IP_ADDRESS>a0 |>=9.0.3,<<IP_ADDRESS>a0 ] with the potential options
│  │     ├─ vtk [9.0.1|9.0.3|...|9.3.1] would require
│  │     │  ├─ python >=3.10,<3.11.0a0 , which can be installed;
│  │     │  └─ vtk-base [9.2.6 egl_py310h1234567_10|9.2.6 egl_py310h1234567_11|...|9.3.1 qt_py310he980d54_201], which can be installed (as previously explained);
│  │     ├─ vtk [8.1.2|8.2.0|...|9.2.2] would require
│  │     │  └─ python >=3.7,<3.8.0a0 , which can be installed;
│  │     ├─ vtk [8.2.0|9.0.0|...|9.3.1] would require
│  │     │  ├─ python >=3.8,<3.9.0a0 , which can be installed;
│  │     │  └─ vtk-base [9.2.6 egl_py38h1234567_10|9.2.6 egl_py38h1234567_11|...|9.3.1 qt_py38hf539ebd_201], which can be installed (as previously explained);
│  │     ├─ vtk [9.0.1|9.0.3|...|9.3.1] would require
│  │     │  ├─ python >=3.9,<3.10.0a0 , which can be installed;
│  │     │  └─ vtk-base [9.2.6 egl_py39h1234567_10|9.2.6 egl_py39h1234567_11|...|9.3.1 qt_py39h8542954_202], which can be installed (as previously explained);
│  │     └─ vtk [8.1.0|8.1.1|...|9.0.3] would require
│  │        └─ python >=3.6,<3.7.0a0 , which can be installed;
│  ├─ pcl [1.11.1|1.9.1] would require
│  │  ├─ boost-cpp >=1.72.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  └─ flann >=1.9.1,<<IP_ADDRESS>a0  but there are no viable options
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 1.8.18|1.8.18.* , which conflicts with any installable versions previously reported;
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 >=1.10.1,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 >=1.10.6,<<IP_ADDRESS>a0  with the potential options
│  │     │     ├─ hdf5 [1.10.5|1.10.6] would require
│  │     │     │  └─ openssl >=1.1.1h,<1.1.2a , which can be installed;
│  │     │     ├─ hdf5 1.10.6 would require
│  │     │     │  └─ openssl >=1.1.1i,<1.1.2a , which can be installed;
│  │     │     └─ hdf5 1.10.6 conflicts with any installable versions previously reported;
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 >=1.10.3,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 >=1.10.2,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 >=1.10.5,<<IP_ADDRESS>a0  with the potential options
│  │     │     ├─ hdf5 1.10.5 conflicts with any installable versions previously reported;
│  │     │     └─ hdf5 [1.10.5|1.10.6], which can be installed (as previously explained);
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 >=1.10.4,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 >=1.12.2,<<IP_ADDRESS>a0  with the potential options
│  │     │     ├─ hdf5 1.12.2, which can be installed (as previously explained);
│  │     │     ├─ hdf5 1.12.2 conflicts with any installable versions previously reported;
│  │     │     └─ hdf5 [1.12.2|1.14.0], which can be installed (as previously explained);
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 >=1.12.1,<<IP_ADDRESS>a0  with the potential options
│  │     │     ├─ hdf5 1.12.1, which can be installed (as previously explained);
│  │     │     ├─ hdf5 1.12.1 conflicts with any installable versions previously reported;
│  │     │     └─ hdf5 1.12.1, which can be installed (as previously explained);
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 >=1.14.0,<<IP_ADDRESS>a0  with the potential options
│  │     │     ├─ hdf5 [1.12.2|1.14.0], which can be installed (as previously explained);
│  │     │     ├─ hdf5 1.14.0 would require
│  │     │     │  └─ openssl >=1.1.1t,<1.1.2a , which can be installed;
│  │     │     └─ hdf5 1.14.0 conflicts with any installable versions previously reported;
│  │     ├─ flann 1.9.1 would require
│  │     │  └─ hdf5 >=1.14.1,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     └─ flann 1.9.1 conflicts with any installable versions previously reported;
│  ├─ pcl 1.11.1 would require
│  │  ├─ boost-cpp >=1.74.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  └─ flann >=1.9.1,<<IP_ADDRESS>a0  but there are no viable options
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     └─ flann 1.9.1 conflicts with any installable versions previously reported;
│  ├─ pcl [1.12.0|1.12.1] would require
│  │  └─ vtk >=9.1.0,<<IP_ADDRESS>a0 , which can be installed (as previously explained);
│  ├─ pcl [1.12.1|1.13.0] would require
│  │  └─ vtk >=9.2.2,<<IP_ADDRESS>a0  with the potential options
│  │     ├─ vtk [9.0.1|9.0.3|...|9.3.1], which can be installed (as previously explained);
│  │     ├─ vtk [8.1.2|8.2.0|...|9.2.2], which can be installed (as previously explained);
│  │     ├─ vtk [8.2.0|9.0.0|...|9.3.1], which can be installed (as previously explained);
│  │     ├─ vtk [9.0.1|9.0.3|...|9.3.1], which can be installed (as previously explained);
│  │     └─ vtk [9.2.2|9.2.5|9.2.6|9.3.0|9.3.1] would require
│  │        ├─ python >=3.11,<3.12.0a0 , which can be installed;
│  │        └─ vtk-base [9.2.6 egl_py311h1234567_10|9.2.6 egl_py311h1234567_11|...|9.3.1 qt_py311h82d2dff_201], which can be installed (as previously explained);
│  ├─ pcl [1.13.1|1.8.1] would require
│  │  └─ flann >=1.9.1,<<IP_ADDRESS>a0  but there are no viable options
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     └─ flann 1.9.1 conflicts with any installable versions previously reported;
│  ├─ pcl [1.8.1|1.9.1] would require
│  │  ├─ boost-cpp >=1.68.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  └─ flann >=1.9.1,<<IP_ADDRESS>a0  but there are no viable options
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     └─ flann 1.9.1 conflicts with any installable versions previously reported;
│  ├─ pcl 1.8.1 would require
│  │  ├─ boost-cpp >=1.66.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  └─ flann >=1.9.1,<<IP_ADDRESS>a0  but there are no viable options
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     └─ flann 1.9.1 conflicts with any installable versions previously reported;
│  ├─ pcl 1.8.1 would require
│  │  ├─ boost-cpp >=1.67.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  └─ flann >=1.9.1,<<IP_ADDRESS>a0  but there are no viable options
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     └─ flann 1.9.1 conflicts with any installable versions previously reported;
│  ├─ pcl 1.9.1 would require
│  │  ├─ boost-cpp >=1.70.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  └─ flann >=1.9.1,<<IP_ADDRESS>a0  but there are no viable options
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     └─ flann 1.9.1 conflicts with any installable versions previously reported;
│  ├─ pcl [1.13.0|1.13.1] would require
│  │  └─ vtk >=9.2.5,<<IP_ADDRESS>a0 , which can be installed (as previously explained);
│  ├─ pcl 1.13.1 would require
│  │  ├─ boost-cpp >=1.78.0,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  └─ flann >=1.9.1,<<IP_ADDRESS>a0  but there are no viable options
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     ├─ flann 1.9.1, which cannot be installed (as previously explained);
│  │     └─ flann 1.9.1 conflicts with any installable versions previously reported;
│  └─ pcl 1.14.1 would require
│     ├─ libboost >=1.84.0,<1.85.0a0  with the potential options
│     │  ├─ libboost 1.84.0, which can be installed;
│     │  └─ libboost 1.84.0, which can be installed (as previously explained);
│     ├─ qt6-main [>=6.7.1,<6.8.0a0 |>=6.7.2,<6.8.0a0 ], which cannot be installed (as previously explained);
│     └─ vtk-base >=9.3.0,<<IP_ADDRESS>a0  with the potential options
│        ├─ vtk-base [9.2.6|9.3.0|9.3.1], which can be installed (as previously explained);
│        ├─ vtk-base [9.2.6|9.3.0|9.3.1], which can be installed (as previously explained);
│        ├─ vtk-base [9.2.6|9.3.0|9.3.1], which can be installed (as previously explained);
│        ├─ vtk-base [9.2.6|9.3.0|9.3.1], which can be installed (as previously explained);
│        ├─ vtk-base [9.3.0|9.3.1] would require
│        │  ├─ libexpat >=2.6.2,<3.0a0 , which cannot be installed (as previously explained);
│        │  ├─ proj >=9.3.1,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│        │  └─ tbb >=2021.12.0  with the potential options
│        │     ├─ tbb 2021.12.0, which can be installed (as previously explained);
│        │     ├─ tbb 2021.12.0, which can be installed (as previously explained);
│        │     └─ tbb 2021.12.0, which cannot be installed (as previously explained);
│        └─ vtk-base 9.3.0 would require
│           ├─ libexpat >=2.6.2,<3.0a0 , which cannot be installed (as previously explained);
│           ├─ libxcb >=1.15,<1.16.0a0 , which can be installed;
│           ├─ proj >=9.3.1,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│           ├─ qt6-main >=6.7.1,<6.8.0a0 , which cannot be installed (as previously explained);
│           └─ tbb >=2021.12.0  with the potential options
│              ├─ tbb 2021.12.0, which can be installed (as previously explained);
│              ├─ tbb 2021.12.0, which can be installed (as previously explained);
│              └─ tbb 2021.12.0, which cannot be installed (as previously explained);
├─ py-opencv is installable with the potential options
│  ├─ py-opencv [4.8.1|4.9.0] would require
│  │  └─ libprotobuf >=4.24.4,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ py-opencv [3.4.7|3.4.8|...|4.2.0] would require
│  │  └─ python >=2.7,<2.8.0a0 , which can be installed;
│  ├─ py-opencv [3.4.7|3.4.8|...|4.5.3] would require
│  │  └─ python >=3.6,<3.7.0a0 , which can be installed;
│  ├─ py-opencv [3.4.7|3.4.8|...|4.6.0] would require
│  │  └─ python >=3.7,<3.8.0a0 , which can be installed;
│  ├─ py-opencv [3.4.7|3.4.8|...|4.9.0] would require
│  │  └─ python >=3.8,<3.9.0a0 , which can be installed;
│  ├─ py-opencv 4.2.0 would require
│  │  └─ libopencv 4.2.0 py36_5, which does not exist (perhaps a missing channel);
│  ├─ py-opencv [4.10.0|4.4.0|...|4.9.0] would require
│  │  └─ python >=3.9,<3.10.0a0 , which can be installed;
│  ├─ py-opencv 4.5.0 would require
│  │  └─ libopencv 4.5.0 py36_5, which does not exist (perhaps a missing channel);
│  ├─ py-opencv 4.5.0 would require
│  │  └─ libopencv 4.5.0 py36_6, which does not exist (perhaps a missing channel);
│  ├─ py-opencv [4.10.0|4.5.3|...|4.9.0] would require
│  │  └─ python >=3.10,<3.11.0a0 , which can be installed;
│  ├─ py-opencv [4.10.0|4.6.0|...|4.9.0] would require
│  │  └─ python >=3.11,<3.12.0a0 , which can be installed;
│  ├─ py-opencv [4.10.0|4.9.0] would require
│  │  └─ libopencv [4.10.0 headless_py312h8908fee_0|4.10.0 headless_py312hc5075ff_1|...|4.9.0 qt5_py312h80b410e_512], which cannot be installed (as previously explained);
│  ├─ py-opencv 4.10.0 would require
│  │  └─ libopencv [4.10.0 headless_py312h8fedf79_2|4.10.0 qt5_py312h567d6bf_502], which cannot be installed (as previously explained);
│  ├─ py-opencv [4.10.0|4.9.0] would require
│  │  └─ libopencv [4.10.0 qt6_py312h21e1ac6_600|4.9.0 qt6_py312h711d6c5_615], which cannot be installed (as previously explained);
│  ├─ py-opencv 4.10.0 would require
│  │  └─ libopencv [4.10.0 qt6_py312h131ea51_601|4.10.0 qt6_py312h8d92a61_602], which cannot be installed (as previously explained);
│  ├─ py-opencv 4.8.1 would require
│  │  ├─ libopencv 4.8.1 py312hd874328_3, which can be installed (as previously explained);
│  │  └─ libprotobuf >=4.24.3,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ py-opencv [4.8.1|4.9.0] would require
│  │  └─ libprotobuf >=3.21.12,<3.22.0a0 , which can be installed;
│  ├─ py-opencv 4.9.0 would require
│  │  └─ libprotobuf >=4.25.2,<<IP_ADDRESS>a0 , which can be installed;
│  ├─ py-opencv 4.9.0 would require
│  │  └─ libprotobuf >=4.25.1,<<IP_ADDRESS>a0 , which cannot be installed (as previously explained);
│  ├─ py-opencv 4.9.0 would require
│  │  └─ libopencv 4.9.0 qt6_py312h0a0470b_612, which cannot be installed (as previously explained);
│  └─ py-opencv 4.9.0 would require
│     └─ libopencv [4.9.0 qt6_py312h400c3b0_614|4.9.0 qt6_py312h6dfe67a_613], which cannot be installed (as previously explained);
├─ qt-main is installable with the potential options
│  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  ├─ qt-main 5.15.2 would require
│  │  └─ openssl >=1.1.1l,<1.1.2a , which can be installed;
│  ├─ qt-main 5.15.3 would require
│  │  └─ openssl >=1.1.1n,<1.1.2a , which can be installed;
│  ├─ qt-main [5.15.3|5.15.4] would require
│  │  └─ openssl >=1.1.1o,<1.1.2a , which can be installed;
│  ├─ qt-main 5.15.6 would require
│  │  └─ openssl >=1.1.1q,<1.1.2a , which can be installed;
│  ├─ qt-main 5.15.6 would require
│  │  └─ openssl >=1.1.1s,<1.1.2a , which can be installed;
│  ├─ qt-main [5.15.6|5.15.8], which cannot be installed (as previously explained);
│  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  ├─ qt-main 5.15.8, which cannot be installed (as previously explained);
│  └─ qt-main 5.15.8, which cannot be installed (as previously explained);
├─ qt-webengine is installable with the potential options
│  ├─ qt-webengine 5.15.8 would require
│  │  └─ libxcb >=1.15,<1.16.0a0 , which can be installed;
│  ├─ qt-webengine 5.15.4 would require
│  │  ├─ libxcb >=1.13,<1.14.0a0 , which can be installed;
│  │  └─ pulseaudio >=14.0,<14.1.0a0  with the potential options
│  │     ├─ pulseaudio 14.0 would require
│  │     │  └─ openssl >=1.1.1q,<1.1.2a , which can be installed;
│  │     ├─ pulseaudio 14.0 would require
│  │     │  └─ alsa-lib >=<IP_ADDRESS>,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ pulseaudio 14.0 would require
│  │     │  └─ alsa-lib >=<IP_ADDRESS>,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ pulseaudio 14.0 would require
│  │     │  └─ alsa-lib >=<IP_ADDRESS>,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ pulseaudio 14.0 would require
│  │     │  └─ alsa-lib >=1.2.8,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │     ├─ pulseaudio 14.0 would require
│  │     │  └─ openssl >=1.1.1o,<1.1.2a , which can be installed;
│  │     ├─ pulseaudio 14.0 would require
│  │     │  └─ orc >=1.6.5,<<IP_ADDRESS>a0  with the potential options
│  │     │     ├─ orc 1.6.5 would require
│  │     │     │  └─ libprotobuf >=3.13.0,<3.14.0a0 , which can be installed;
│  │     │     └─ orc [1.6.5|1.6.6] would require
│  │     │        └─ libprotobuf >=3.14.0,<3.15.0a0 , which can be installed;
│  │     ├─ pulseaudio 14.0 would require
│  │     │  └─ orc >=1.6.6,<<IP_ADDRESS>a0 , which can be installed (as previously explained);
│  │     └─ pulseaudio 14.0 would require
│  │        └─ alsa-lib >=1.2.3,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  ├─ qt-webengine 5.15.8 would require
│  │  └─ libxcb >=1.13,<1.14.0a0 , which can be installed;
│  ├─ qt-webengine [5.15.4|5.15.8] would require
│  │  ├─ alsa-lib >=1.2.8,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  ├─ gst-plugins-base >=1.21.2,<1.22.0a0 , which cannot be installed (as previously explained);
│  │  └─ libxcb >=1.13,<1.14.0a0 , which can be installed;
│  ├─ qt-webengine 5.15.8 would require
│  │  ├─ alsa-lib >=1.2.8,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│  │  └─ libxcb >=1.15,<1.16.0a0 , which can be installed;
│  ├─ qt-webengine 5.15.8 would require
│  │  └─ alsa-lib >=1.2.11,<1.3.0a0 , which conflicts with any installable versions previously reported;
│  ├─ qt-webengine 5.15.8 would require
│  │  └─ alsa-lib >=1.2.12,<1.3.0a0 , which conflicts with any installable versions previously reported;
│  └─ qt-webengine 5.15.8 would require
│     ├─ alsa-lib >=1.2.9,<<IP_ADDRESS>a0 , which conflicts with any installable versions previously reported;
│     └─ libxcb >=1.15,<1.16.0a0 , which can be installed;
├─ vtk is installable with the potential options
│  ├─ vtk [9.0.1|9.0.3|...|9.3.1], which can be installed (as previously explained);
│  ├─ vtk [8.1.2|8.2.0|...|9.2.2], which can be installed (as previously explained);
│  ├─ vtk [8.2.0|9.0.0|...|9.3.1], which can be installed (as previously explained);
│  ├─ vtk [9.0.1|9.0.3|...|9.3.1], which can be installed (as previously explained);
│  ├─ vtk [8.1.0|8.1.1|...|9.0.3], which can be installed (as previously explained);
│  ├─ vtk [9.2.2|9.2.5|9.2.6|9.3.0|9.3.1], which can be installed (as previously explained);
│  ├─ vtk 9.2.6 would require
│  │  └─ vtk-base [9.2.6 egl_py312h1234567_18|9.2.6 egl_py312h1234567_19|...|9.2.6 qt_py312h1234567_219], which cannot be installed (as previously explained);
│  ├─ vtk [7.0.0|7.1.0|...|8.2.0] would require
│  │  └─ python [2.7* |>=2.7,<2.8.0a0 ], which can be installed;
│  ├─ vtk [7.0.0|7.1.0|...|8.1.1] would require
│  │  └─ python [3.5* |>=3.5,<3.6.0a0 ], which can be installed;
│  ├─ vtk [7.1.0|7.1.1|8.0.1|8.1.0] would require
│  │  └─ python 3.6* , which can be installed;
│  ├─ vtk 9.2.6 would require
│  │  └─ vtk-base [9.2.6 egl_py312h1234567_20|9.2.6 egl_py312h1234567_21|...|9.2.6 qt_py312h1234567_223], which cannot be installed (as previously explained);
│  ├─ vtk [9.3.0|9.3.1] would require
│  │  └─ vtk-base [9.3.0 egl_py312h1234567_0|9.3.1 osmesa_py312h1234567_100|9.3.1 osmesa_py312hb25cddc_101], which cannot be installed (as previously explained);
│  ├─ vtk 9.3.0 would require
│  │  ├─ vtk-base 9.3.0 osmesa_py312h1234567_100, which cannot be installed (as previously explained);
│  │  └─ vtk-io-ffmpeg 9.3.0 osmesa_py312h1234567_100, which requires
│  │     ├─ ffmpeg >=7.0.1,<8.0a0 , which cannot be installed (as previously explained);
│  │     └─ vtk-base [9.3.0 osmesa_py312h1234567_100|9.3.1 osmesa_py312h33d2d6c_101], which cannot be installed (as previously explained);
│  ├─ vtk 9.3.0 would require
│  │  └─ vtk-base 9.3.0 qt_py312h1234567_200, which cannot be installed (as previously explained);
│  ├─ vtk 9.3.1 would require
│  │  ├─ vtk-base 9.3.1 egl_py312h1234567_0, which requires
│  │  │  ├─ libxcb >=1.16,<1.17.0a0 , which conflicts with any installable versions previously reported;
│  │  │  └─ tbb >=2021.12.0  with the potential options
│  │  │     ├─ tbb 2021.12.0, which can be installed (as previously explained);
│  │  │     ├─ tbb 2021.12.0, which can be installed (as previously explained);
│  │  │     └─ tbb 2021.12.0, which cannot be installed (as previously explained);
│  │  └─ vtk-io-ffmpeg 9.3.1 egl_py312h1234567_0, which requires
│  │     ├─ ffmpeg >=7.0.1,<8.0a0 , which cannot be installed (as previously explained);
│  │     └─ vtk-base [9.3.1 egl_py312h1234567_0|9.3.1 egl_py312h6d27e6a_1], which cannot be installed (as previously explained);
│  ├─ vtk 9.3.1 would require
│  │  └─ vtk-base 9.3.1 egl_py312h16fb7b0_1, which cannot be installed (as previously explained);
│  ├─ vtk 9.3.1 would require
│  │  └─ vtk-base 9.3.1 egl_py312hc69c4c9_2, which requires
│  │     ├─ libxcb >=1.16,<1.17.0a0 , which conflicts with any installable versions previously reported;
│  │     ├─ proj >=9.4.1,<9.5.0a0 , which cannot be installed (as previously explained);
│  │     └─ tbb >=2021.12.0  with the potential options
│  │        ├─ tbb 2021.12.0, which can be installed (as previously explained);
│  │        ├─ tbb 2021.12.0, which can be installed (as previously explained);
│  │        └─ tbb 2021.12.0, which cannot be installed (as previously explained);
│  ├─ vtk 9.3.1 would require
│  │  └─ vtk-base 9.3.1 osmesa_py312h5b0cd0c_102, which requires
│  │     ├─ libexpat >=2.6.2,<3.0a0 , which cannot be installed (as previously explained);
│  │     ├─ libzlib >=1.3.1,<2.0a0 , which can be installed;
│  │     ├─ proj >=9.4.1,<9.5.0a0 , which cannot be installed (as previously explained);
│  │     └─ tbb >=2021.12.0  with the potential options
│  │        ├─ tbb 2021.12.0, which can be installed (as previously explained);
│  │        ├─ tbb 2021.12.0, which can be installed (as previously explained);
│  │        └─ tbb 2021.12.0, which cannot be installed (as previously explained);
│  ├─ vtk 9.3.1 would require
│  │  └─ vtk-base 9.3.1 qt_py312h1234567_200, which requires
│  │     ├─ libxcb >=1.16,<1.17.0a0 , which conflicts with any installable versions previously reported;
│  │     ├─ qt6-main >=6.7.2,<6.8.0a0 , which cannot be installed (as previously explained);
│  │     └─ tbb >=2021.12.0  with the potential options
│  │        ├─ tbb 2021.12.0, which can be installed (as previously explained);
│  │        ├─ tbb 2021.12.0, which can be installed (as previously explained);
│  │        └─ tbb 2021.12.0, which cannot be installed (as previously explained);
│  └─ vtk 9.3.1 would require
│     ├─ vtk-base [9.3.1 qt_py312h86f6322_201|9.3.1 qt_py312hb690231_202], which cannot be installed (as previously explained);
│     └─ vtk-io-ffmpeg [9.3.1 qt_py312he1e5eab_201|9.3.1 qt_py312he1e5eab_202], which requires
│        ├─ ffmpeg >=7.0.1,<8.0a0 , which cannot be installed (as previously explained);
│        └─ vtk-base [9.3.1 qt_py312h86f6322_201|9.3.1 qt_py312hb690231_202], which cannot be installed (as previously explained);
├─ vtk-base is installable with the potential options
│  ├─ vtk-base 9.2.6, which cannot be installed (as previously explained);
│  ├─ vtk-base [9.2.6|9.3.0|9.3.1], which can be installed (as previously explained);
│  ├─ vtk-base [9.2.6|9.3.0|9.3.1], which can be installed (as previously explained);
│  ├─ vtk-base 9.2.6, which cannot be installed (as previously explained);
│  ├─ vtk-base 9.2.6, which cannot be installed (as previously explained);
│  ├─ vtk-base [9.2.6|9.3.0|9.3.1], which can be installed (as previously explained);
│  ├─ vtk-base [9.2.6|9.3.0|9.3.1], which can be installed (as previously explained);
│  ├─ vtk-base [9.3.0|9.3.1], which cannot be installed (as previously explained);
│  ├─ vtk-base 9.3.0, which cannot be installed (as previously explained);
│  ├─ vtk-base 9.3.1, which cannot be installed (as previously explained);
│  ├─ vtk-base 9.3.1, which cannot be installed (as previously explained);
│  ├─ vtk-base 9.3.1, which cannot be installed (as previously explained);
│  └─ vtk-base 9.3.1, which cannot be installed (as previously explained);
└─ vtk-io-ffmpeg is installable with the potential options
 ├─ vtk-io-ffmpeg 9.2.6 would require
 │  ├─ ffmpeg >=6.1.0,<7.0a0  with the potential options
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.0 would require
 │  │  │  └─ aom >=3.7.1,<3.8.0a0 , which conflicts with any installable versions previously reported;
 │  │  ├─ ffmpeg [4.4.2|5.1.2|6.0.0|6.0.1|6.1.0], which can be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.0 would require
 │  │  │  └─ aom >=3.7.0,<3.8.0a0  with the potential options
 │  │  │     ├─ aom 3.7.1 conflicts with any installable versions previously reported;
 │  │  │     └─ aom 3.7.0, which can be installed;
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  └─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  └─ vtk-base [9.2.6 egl_py312h1234567_19|9.2.6 osmesa_py312h1234567_119|9.2.6 qt_py312h1234567_219], which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg [9.2.6|9.3.0|9.3.1] would require
 │  └─ vtk-base [9.2.6 egl_py310h1234567_10|9.2.6 egl_py310h1234567_11|...|9.3.1 qt_py310he980d54_201], which can be installed (as previously explained);
 ├─ vtk-io-ffmpeg [9.2.6|9.3.0|9.3.1] would require
 │  └─ vtk-base [9.2.6 egl_py311h1234567_10|9.2.6 egl_py311h1234567_11|...|9.3.1 qt_py311hb261c1e_202], which can be installed (as previously explained);
 ├─ vtk-io-ffmpeg 9.2.6 would require
 │  ├─ ffmpeg >=6.0.0,<7.0a0  with the potential options
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.0, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg [4.4.2|5.1.2|6.0.0|6.0.1|6.1.0], which can be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.0, which can be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  └─ ffmpeg [4.4.2|5.1.2|6.0.0], which can be installed (as previously explained);
 │  └─ vtk-base [9.2.6 egl_py312h1234567_18|9.2.6 osmesa_py312h1234567_118|9.2.6 qt_py312h1234567_218], which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg 9.2.6 would require
 │  ├─ ffmpeg >=6.1.0,<7.0a0  with the potential options
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.0, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg [4.4.2|5.1.2|6.0.0|6.0.1|6.1.0], which can be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.0, which can be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  ├─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  │  └─ ffmpeg 6.1.1, which cannot be installed (as previously explained);
 │  └─ vtk-base [9.2.6 egl_py312h1234567_20|9.2.6 osmesa_py312h1234567_120|9.2.6 qt_py312h1234567_220], which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg 9.2.6 would require
 │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
 │  └─ vtk-base [9.2.6 egl_py312h1234567_21|9.2.6 egl_py312h1234567_22|...|9.2.6 qt_py312h1234567_223], which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg [9.2.6|9.3.0|9.3.1] would require
 │  └─ vtk-base [9.2.6 egl_py38h1234567_10|9.2.6 egl_py38h1234567_11|...|9.3.1 qt_py38hf539ebd_201], which can be installed (as previously explained);
 ├─ vtk-io-ffmpeg [9.2.6|9.3.0|9.3.1] would require
 │  └─ vtk-base [9.2.6 egl_py39h1234567_10|9.2.6 egl_py39h1234567_11|...|9.3.1 qt_py39h974aab6_202], which can be installed (as previously explained);
 ├─ vtk-io-ffmpeg [9.3.0|9.3.1] would require
 │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
 │  └─ vtk-base [9.3.0 egl_py312h1234567_0|9.3.1 osmesa_py312h1234567_100|9.3.1 osmesa_py312hb25cddc_101], which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg [9.3.0|9.3.1], which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg 9.3.0 would require
 │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
 │  └─ vtk-base 9.3.0 qt_py312h1234567_200, which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg 9.3.1, which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg 9.3.1 would require
 │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
 │  └─ vtk-base 9.3.1 egl_py312h16fb7b0_1, which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg 9.3.1 would require
 │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
 │  └─ vtk-base [9.3.1 egl_py312hc69c4c9_2|9.3.1 osmesa_py312h5b0cd0c_102], which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg 9.3.1 would require
 │  ├─ ffmpeg >=7.0.1,<8.0a0 , which cannot be installed (as previously explained);
 │  └─ vtk-base 9.3.1 egl_py312h92a6ba4_2, which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg 9.3.1 would require
 │  ├─ ffmpeg >=7.0.1,<8.0a0 , which cannot be installed (as previously explained);
 │  └─ vtk-base 9.3.1 osmesa_py312hde7e526_102, which cannot be installed (as previously explained);
 ├─ vtk-io-ffmpeg 9.3.1 would require
 │  ├─ ffmpeg >=6.1.1,<7.0a0 , which cannot be installed (as previously explained);
 │  └─ vtk-base [9.3.1 qt_py312h1234567_200|9.3.1 qt_py312h9816b39_201|9.3.1 qt_py312hf523409_202], which cannot be installed (as previously explained);
 └─ vtk-io-ffmpeg 9.3.1, which cannot be installed (as previously explained).

Not sure what is the difference w.r.t. to your setup, but in my case this is the output:
(testlo24) traversaro@IITBMP014LW012:~$ conda install -c conda-forge gz-sim-yarp-plugins
Channels:
 - conda-forge
Platform: linux-64
Collecting package metadata (repodata.json): done
Solving environment: failed

LibMambaUnsatisfiableError: Encountered problems while solving:
  - package gz-sim-yarp-plugins-0.2.0-ha770c72_0 requires libgz-sim-yarp-plugins 0.2.0 h41785cb_0, but none of the providers can be installed

Could not solve for environment specs
The following packages are incompatible
├─ gz-sim-yarp-plugins is installable with the potential options
│  ├─ gz-sim-yarp-plugins [0.1.1|0.2.0] would require
│  │  └─ libgz-sim-yarp-plugins [0.1.1 h41785cb_0|0.2.0 h41785cb_0|0.2.0 h41785cb_1], which requires
│  │     └─ libgz-sim8 >=8.1.0,<9.0a0  with the potential options
│  │        ├─ libgz-sim8 [8.1.0|8.2.0|8.3.0] would require
│  │        │  └─ libprotobuf >=4.25.3,<<IP_ADDRESS>a0 , which can be installed;
│  │        └─ libgz-sim8 8.1.0 would require
│  │           └─ tinyxml2 >=10.0.0,<11.0a0 , which can be installed;
│  └─ gz-sim-yarp-plugins 0.2.0 would require
│     └─ libgz-sim-yarp-plugins 0.2.0 h6e67749_2, which requires
│        └─ libprotobuf >=4.25.3,<<IP_ADDRESS>a0 , which can be installed;
├─ libprotobuf 4.24.4.*  is not installable because it conflicts with any installable versions previously reported;
└─ tinyxml2 9.0.0.*  is not installable because it conflicts with any installable versions previously reported.

so there error is more clear, you have some old versions of protobuf and tinyxml2 . My conda version is:
traversaro@IITBMP014LW012:~$ conda info

     active environment : None
            shell level : 0
       user config file : /home/traversaro/.condarc
 populated config files : /home/traversaro/miniforge3/.condarc
                          /home/traversaro/.condarc
          conda version : 24.5.0
    conda-build version : 24.5.1
         python version : 3.10.14.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=skylake
                          __conda=24.5.0=0
                          __cuda=12.3=0
                          __glibc=2.39=0
                          __linux=<IP_ADDRESS>=0
                          __unix=0=0
       base environment : /home/traversaro/miniforge3  (writable)
      conda av data dir : /home/traversaro/miniforge3/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /home/traversaro/miniforge3/pkgs
                          /home/traversaro/.conda/pkgs
       envs directories : /home/traversaro/miniforge3/envs
                          /home/traversaro/.conda/envs
               platform : linux-64
             user-agent : conda/24.5.0 requests/2.31.0 CPython/3.10.14 Linux/<IP_ADDRESS>-microsoft-standard-WSL2 ubuntu/24.04 glibc/2.39 solver/libmamba conda-libmamba-solver/24.1.0 libmambapy/1.5.8
                UID:GID : 1002:1002
             netrc file : None
           offline mode : False

I was installing gz-sim-yarp-plugins in a conda environment which was not empty, since it was containing all the dependencies of the robotology-superbuild.
I will proceed by installing gz-sim-yarp-plugins from the robotology-superbuild.
Closing this issue, thanks @traversaro.


@angular/service-worker overlapping functionality with other sw libraries

Currently the beta of @angular/service-worker is out, however Google already has sw-precache/toolbox and Workbox. I believe with @angular/service-worker it would create confusion to the users.
I was hoping that @angular library would use either of the two libraries underneath with some added functionality. But doesnt seems to be the case. Even the ngsw-manifest specification seems to be different then what sw-precache and workbox would expect.
I guess I am missing something :) Can you please throw some light how this library would be different then the other two and the advantage of using this.

Angular Service Worker is not designed to be mixed with any other SW library. It's fully self-standing and doesn't use neither sw-precache nor its newer version Workbox. In terms of PWA tooling for your Angular application you can use one of the approaches (both work fine):

Go for Angular Service Worker (here is the current documentation: https://bit.ly/pwa-angularsummit-2017 )
Go for other lib (I'd prefer Workbox)

I am using firebase for push notification and its uses firebase-messaging-sw.js file for background notification. I am using @angular/service-worker": "^1.0.0-beta.16 for generating service worker(for resource caching), now how to make these two service workers work together?
currently in application tab(chrome), its showing 2 service workers


Misspelt words in about

A vritual filesystem, specifically made for games   instead of A virtual filesystem, specifically made for games

I can't see a difference between the two, what did you change?

Damn i must be blind, virtual is misspelt @sokorototo


Added Dockerfile that builds the image hosted on Docker Hub

Run from docker hub with docker run -it --rm -p <IP_ADDRESS>:<IP_ADDRESS> jpfa/semanticmodels:stretch
Or download the Dockerfile and run docker build . -t semanticmodels:stretch then docker run -it -p <IP_ADDRESS>:<IP_ADDRESS> semanticmodels:stretch

Can we add Jupytext to the build step so that the Jupyterlab can open .jl files as if they were notebooks?

Added jupytext to the build


pkgsLLVM.stdenv: use lld again

PR #122778 allowed the linker being chosen independently from useLLVM
which also affected pkgsLLVM where we were relying on this behavior.
For platform sets assembled from scratch useLLVM still implies
linker == "lld", however in the case of pkgsLLVM we update the current
platform via the set update operator which means that linker won't
be re-evaluated. Using ld.bfd with pkgsLLVM is okay to a certain extent,
but with C++ things begin to break.
We fix this by setting linker explicitly.

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] 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 nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@ofborg build pkgsLLVM.hello


Memory leak in MQTT callback function

https://github.com/toblum/McLighting/blob/4820d584422f595cf78ceb40c38ea5aab443f503/Arduino/McLighting/request_handlers.h#L310
The use of "malloc" without "free"ing up the result causes a memory leak - free heap space drops steadily with each received mqqt message, eventually resulting in heap overflow and chip reset. Suggest avoiding the use of malloc entirely. Just use "payload_in" instead of defining and copying the contents.

You're right. I missed that. Will have a look at it as soon I find time.
Thank you!

Dear @nimbl,
I tried using payload_in directly but had problems, so I ended up using free().
--> https://github.com/toblum/McLighting/commit/ab9253abde7350ba504fa5a21a38ee7aa7ccc5c2
Thanks again!
Regards
Tobias