conda-forge / ibm_db-feedstock

A conda-smithy repository for ibm_db.

About ibm_db-feedstock

Feedstock license: BSD-3-Clause

Home: https://pypi.org/project/ibm-db/

Package license: Apache-2.0

Summary: Python DBI driver for DB2 (LUW, zOS, i5) and IDS

Development: https://github.com/ibmdb/python-ibmdb

Documentation: https://github.com/ibmdb/python-ibmdb/wiki

This extension is the implementation of Python Database API Specification v2.0 The extension supports DB2 (LUW, zOS, i5) and IDS (Informix Dynamic Server)

Current build status

Azure

Variant Status linux_64_python3.10.____cpython linux_64_python3.11.____cpython linux_64_python3.12.____cpython linux_64_python3.8.____cpython linux_64_python3.9.____cpython linux_ppc64le_python3.10.____cpython linux_ppc64le_python3.11.____cpython linux_ppc64le_python3.12.____cpython linux_ppc64le_python3.8.____cpython linux_ppc64le_python3.9.____cpython win_64_python3.10.____cpython win_64_python3.12.____cpython win_64_python3.8.____cpython win_64_python3.9.____cpython

Current release info

Name	Downloads	Version	Platforms

Installing ibm_db

Installing ibm_db from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

Once the conda-forge channel has been enabled, ibm_db can be installed with conda:

conda install ibm_db

or with mamba:

mamba install ibm_db

It is possible to list all of the versions of ibm_db available on your platform with conda:

conda search ibm_db --channel conda-forge

or with mamba:

mamba search ibm_db --channel conda-forge

Alternatively, mamba repoquery may provide more information:

# Search all versions available on your platform:
mamba repoquery search ibm_db --channel conda-forge

# List packages depending on `ibm_db`:
mamba repoquery whoneeds ibm_db --channel conda-forge

# List dependencies of `ibm_db`:
mamba repoquery depends ibm_db --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating ibm_db-feedstock

If you would like to improve the ibm_db recipe or build a new package version, please fork this repository and submit a PR. Upon submission, your changes will be run on the appropriate platforms to give the reviewer an opportunity to confirm that the changes result in a successful build. Once merged, the recipe will be re-built and uploaded automatically to the conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/ibm_db-feedstock are immediately built and any created packages are uploaded, so PRs should be based on branches in forks and branches in the main repository should only be used to build distinct package versions.

In order to produce a uniquely identifiable distribution:

• If the version of a package is not being increased, please add or increase the build/number.
• If the version of a package is being increased, please remember to return the build/number back to 0.

Feedstock Maintainers

• @SabaKauser
• @amukherjee28
• @xhochy

ibm_db-feedstock's Issues

How to update new release of ibm_db 3.0.2

Issue:

Environment (conda list):

$ conda list

Details about conda and system ( conda info ): A new release of ibm_db with version number 3.0.2 is made and I needed to know what exact set of changes are needed to get this reflecting. I see there is PR already opened but it seem to be failing on windows. Can you kindly assist with this!

Failing PR: #7
failing build: https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=175487&view=logs&j=171a126d-c574-5c8c-1269-ff3b989e923d&t=1183ba29-a0b5-5324-8463-2a49ace9e213&l=397

Please note that with the new release, meta.yaml no longer requires the text in bold this:
script: "rm -r -f ${SP_DIR}/tests && {{ PYTHON }} -m pip install . -vv"
Thanks!

$ conda info

Python 3.8 build is missing

Issue:
I noticed that the Python 3.8 build is missing. Officially ibm_db 3.0.2 is now compatible with Python 3.8.

> conda search ibm_db -c conda-forge --override-channels

Loading channels: done
# Name                       Version           Build  Channel
ibm_db                         3.0.1  py27h0c8e037_0  conda-forge
ibm_db                         3.0.1  py27h0c8e037_1  conda-forge
ibm_db                         3.0.1  py36hfa6e2cd_0  conda-forge
ibm_db                         3.0.1  py36hfa6e2cd_1  conda-forge
ibm_db                         3.0.1  py37hfa6e2cd_0  conda-forge
ibm_db                         3.0.1  py37hfa6e2cd_1  conda-forge
ibm_db                         3.0.2  py36h779f372_1  conda-forge
ibm_db                         3.0.2  py37h4ab8f01_1  conda-forge

Support Python 3.11 and ibm_db version 3.2.0

Comment:

My miniforge3 Python 3.11 environments currently can't use ibm_db, not sure why it's restricted to <= 3.10. Can 3.11 support be added? Could also update to latest ibm_db version.

Conflict with JSON5 package

@conda-forge/core

This was reported to me by the maintainer for ibm_db:

When you install this package on top of the JSON5 package, there will be a merge error on __init__.py file. This issue is not present when using pip. Details:

(base) phils-MBP:Downloads phil.downey$ conda install json5
Collecting package metadata (current_repodata.json): done
Solving environment: done

## Package Plan ##

environment location: //anaconda3

added / updated specs:
- json5


The following NEW packages will be INSTALLED:

json5 pkgs/main/noarch::json5-0.8.4-py_0


Proceed ([y]/n)? y

Preparing transaction: done
Verifying transaction: done
Executing transaction: done
(base) phils-MBP:Downloads phil.downey$ conda install -c conda-forge ibm_db
Collecting package metadata (current_repodata.json): done
Solving environment: done

## Package Plan ##

environment location: //anaconda3

added / updated specs:
- ibm_db


The following NEW packages will be INSTALLED:

ibm_db conda-forge/osx-64::ibm_db-3.0.1-py37h01d97ff_0

The following packages will be UPDATED:

ca-certificates pkgs/main::ca-certificates-2019.5.15-0 --> conda-forge::ca-certificates-2019.6.16-hecc5488_0

The following packages will be SUPERSEDED by a higher-priority channel:

certifi pkgs/main --> conda-forge
conda pkgs/main --> conda-forge
openssl pkgs/main::openssl-1.1.1c-h1de35cc_1 --> conda-forge::openssl-1.1.1c-h01d97ff_0


Proceed ([y]/n)? y

Preparing transaction: done
Verifying transaction: failed

ClobberError: The package 'conda-forge::ibm_db-3.0.1-py37h01d97ff_0' cannot be installed due to a
path collision for 'lib/python3.7/site-packages/tests/__init__.py'.
This path already exists in the target prefix, and it won't be removed by
an uninstall action in this transaction. The path appears to be coming from
the package 'defaults::json5-0.8.4-py_0', which is already installed in the prefix.


ClobberError: The package 'conda-forge::ibm_db-3.0.1-py37h01d97ff_0' cannot be installed due to a
path collision for 'lib/python3.7/site-packages/tests/__pycache__/__init__.cpython-37.pyc'.
This path already exists in the target prefix, and it won't be removed by
an uninstall action in this transaction. The path appears to be coming from
the package 'defaults::json5-0.8.4-py_0', which is already installed in the prefix.


CondaVerificationError: The package for ibm_db located at //anaconda3/pkgs/ibm_db-3.0.1-py37h01d97ff_0
appears to be corrupted. The path 'lib/python3.7/site-packages/clidriver/db2dump/._db2diag.log'
specified in the package manifest cannot be found.

How exactly should we address this?

Thanks.