| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
1.Upgrade python-psycopg2 from 2.6.2 to 2.7.4.
2.Modify remove-pg-config.patch, since the data has been changed.
Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
| |
1) Upgrade python-psycopg2 from 2.6.1 to 2.6.2.
2) Modify remove-pg-config.patch, since the data has been changed.
Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
When building we get an error:
Error: pg_config executable not found.
Previously there was a patch that removed references to pg_config.
This patch was dropped during the version uprev for an unknown
reason. Reinstate this patch with minor updates to allow it to patch
the new version of python-psycopg2 and get the build working again.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
|
|
| |
pg-config is not provided as a native tool, so if called, the host version
will be found. Since the values that are typically returned by pg-config
can be determined in our build environment, we can safely remove the calls
completely.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
| |
|
|
|
|
|
| |
Added the reason for why it is necessary and the UpstreamStatus
to the patch.
Signed-off-by: Mihai Prica <prica.mihai@gmail.com>
|
|
|
Signed-off-by: Mihai Prica <prica.mihai@gmail.com>
|
