generates a file repodata.json, saved to each repository directory, which conda uses to get the metadata for the packages in the channel. � Note Each time you add or modify a package in the channel, you have set up your private repository correctly, you get the following output: Fetching package metadata: . . . . This is followed by a list of the conda packages found. This verifies that you have set Chapter 4. Contributors welcome conda, Release 25.1.2.dev1 $ conda search flask Fetching package metadata: Error: URL 'http://repo.anaconda.com/pkgs/pro/osx-64/' not in allowed channels. Allowed channels

generates a file repodata.json, saved to each repository directory, which conda uses to get the metadata for the packages in the channel. � Note Each time you add or modify a package in the channel, you have set up your private repository correctly, you get the following output: Fetching package metadata: . . . . This is followed by a list of the conda packages found. This verifies that you have set Chapter 4. Contributors welcome conda, Release 24.11.3.dev2 $ conda search flask Fetching package metadata: Error: URL 'http://repo.anaconda.com/pkgs/pro/osx-64/' not in allowed channels. Allowed channels

generates a file repodata.json, saved to each repository directory, which conda uses to get the metadata for the packages in the channel. � Note Each time you add or modify a package in the channel, you have set up your private repository correctly, you get the following output: Fetching package metadata: . . . . This is followed by a list of the conda packages found. This verifies that you have set they get a message telling them what channels are allowed: $ conda search flask Fetching package metadata: Error: URL 'http://repo.anaconda.com/pkgs/pro/osx-64/' not in allowed channels. Allowed channels

generates a file repodata.json, saved to each repository directory, which conda uses to get the metadata for the packages in the channel. � Note Each time you add or modify a package in the channel, you have set up your private repository correctly, you get the following output: Fetching package metadata: . . . . 46 Chapter 4. Contributors welcome conda, Release 24.7.1 This is followed by a list they get a message telling them what channels are allowed: $ conda search flask Fetching package metadata: Error: URL 'http://repo.anaconda.com/pkgs/pro/osx-64/' not in allowed channels. Allowed channels

generates a file repodata.json, saved to each repository directory, which conda uses to get the metadata for the packages in the channel. Note: Each time you add or modify a package in the channel, you you have set up your private repository correctly, you get the following output: Fetching package metadata: . . . . This is followed by a list of the conda packages found. This verifies that you have set Chapter 4. Contributors welcome conda, Release 24.3.1.dev2 $ conda search flask Fetching package metadata: Error: URL 'http://repo.anaconda.com/pkgs/pro/osx-64/' not in allowed channels. Allowed channels

generates a file repodata.json, saved to each repository directory, which conda uses to get the metadata for the packages in the channel. Note: Each time you add or modify a package in the channel, you you have set up your private repository correctly, you get the following output: Fetching package metadata: . . . . This is followed by a list of the conda packages found. This verifies that you have set Chapter 4. Contributors welcome conda, Release 24.3.1.dev7 $ conda search flask Fetching package metadata: Error: URL 'http://repo.anaconda.com/pkgs/pro/osx-64/' not in allowed channels. Allowed channels

generates a file repodata.json, saved to each repository directory, which conda uses to get the metadata for the packages in the channel. Note: Each time you add or modify a package in the channel, you you have set up your private repository correctly, you get the following output: Fetching package metadata: . . . . This is followed by a list of the conda packages found. This verifies that you have set Chapter 4. Contributors welcome conda, Release 24.5.1.dev1 $ conda search flask Fetching package metadata: Error: URL 'http://repo.anaconda.com/pkgs/pro/osx-64/' not in allowed channels. Allowed channels

generates a file repodata.json, saved to each repository directory, which conda uses to get the metadata for the packages in the channel. Note: Each time you add or modify a package in the channel, you you have set up your private repository correctly, you get the following output: Fetching package metadata: . . . . This is followed by a list of the conda packages found. This verifies that you have set Chapter 4. Contributors welcome conda, Release 24.1.2.dev2 $ conda search flask Fetching package metadata: Error: URL 'http://repo.anaconda.com/pkgs/pro/osx-64/' not in allowed channels. Allowed channels

system-level libraries. • Python or other modules. • executable programs and other components. • metadata under the info/ directory. • a collection of files that are installed directly into an install relevant library files (eg. the .py files). • info contains package metadata. Metapackages When a conda package is used for metadata alone and does not contain any files, it is referred to as a metapackage software files that are automatically downloaded when executed. Metapackages are used to capture metadata and make complicated package specifications simpler. An example of a metapackage is "anaconda,"

system-level libraries. • Python or other modules. • executable programs and other components. • metadata under the info/ directory. • a collection of files that are installed directly into an install relevant library files (eg. the .py files). • info contains package metadata. Metapackages When a conda package is used for metadata alone and does not contain any files, it is referred to as a metapackage software files that are automatically downloaded when executed. Metapackages are used to capture metadata and make complicated package specifications simpler. An example of a metapackage is "anaconda,"