** Changed in: asyncpg (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850136
Title:
FTBFS in Focal with PG-12 present
To manage notifications about this
Resolved with 0.20.0-1
** Changed in: asyncpg (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850136
Title:
FTBFS in Focal with PG-12 present
To ma
I did work on 0.20 a bit, but it still fails to build
It can be found at: https://salsa.debian.org/paelzer-
guest/asyncpg/commits/debian-update-from-upstream
But I'm afraid we might need to properly split and package pgproto into
its own package and then (re-)build 0.20.0 again.
But that is prob
Fixes got merged in https://github.com/MagicStack/asyncpg/pull/504
And upstream tagged 20.0
https://github.com/MagicStack/asyncpg/releases/tag/v0.20.0
TODO: test if packaging that makes it work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: asyncpg (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850136
Title:
FTBFS in Focal with PG-12 present
To manage notifications about this bug g
Updated the Debian bug and opened Salsa MRs with the work so far in [1]
and its siblings.
[1]: https://salsa.debian.org/python-
team/modules/asyncpg/merge_requests/2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Yeah, as assumed it seems to by py3.8, here from upstream on my issue:
"Python 3.8 is not supported yet."
I wondered if we should remove it for now, but there are more packages
to this.
Recommends: silver-platter -> lintian-brush -> python3-asyncpg
Surely we could reduce this to a suggest and th
Oh doko was faster and reported the initial (test fail) issue already. I'll
chime in there.
=> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943832
** Also affects: asyncpg (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943832
Importance: Unknown
Status: Unknown
FYI I filed https://github.com/MagicStack/asyncpg/issues/501
** Bug watch added: github.com/MagicStack/asyncpg/issues #501
https://github.com/MagicStack/asyncpg/issues/501
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
It builds further now and might be ok, but it has other build breakage.
I might need someone with more python-foo for this to help me.
I have pushed the interim state to [1]
Breaking buildlog at [2]
[1]: https://salsa.debian.org/paelzer-guest/asyncpg/tree/package-19.0
[2]: http://paste.ubuntu.com
It might be incompatible with postgresql-12 python bindings.
There is a asyncpg (upstream) v0.19.0 which includes among other things:
* Add PostgreSQL 12 support
(by @elprans in 23261532)
We might either need go to full 0.19.0 [1] or backport the fix [2] it it
works as-is.
[1]: https://github
While more of the postgresql migration goes on the former bug is resolved.
Just to hit another FTBFS which effectively means it still fails to build.
One solved, more to go ...
The new error is about:
1529 E asyncpg.cluster.ClusterError: pg_ctl stop exited with status
1: pg_ctl: PID fil
Synced postgresql-common after Debian got the change for 20.04 that we need.
Lets give this a night to trigger tests and then we might need to re-trigger
all kind of hanging proposed migrations with custom triggers to pass.
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package postgresql-common - 208
---
postgresql-common (208) unstable; urgency=medium
[ Christoph Berg ]
* gitlab/gitlab-ci.yml: Too many packages fail because reprotest runs the
build as root, disable for now.
* README.Debian: Redirect reference to
postgresql-11 already has:
* Stop building lib packages, postgresql-12 is already in unstable.
(Closes: #941845)
Those come from postgresql-12 now.
This here might already show things are going further towards v12.
The reason it looks there is in attribute self._pg_bin_dir =
Ok, after analyzing the case it was clear that it is a mismatch between
defaults e.g. postgresql -> postgresql-12 while at the same time e.g.
libpq-dev already pointing to 12.
That will be resolved via a coming upload of postgresql-common to Debian
(and a matching sync to Ubuntu to drop.
Adding a
It misses the pg-12 version, but has PG-11 installed:
$ find /usr/ -name pg_ctl
/usr/lib/postgresql/11/bin/pg_ctl
There are a lot of tests, but it is enough to run just e.g.:
$ cd
$ cd .pybuild/cpython3_3.8_asyncpg/build
$ python3.8 -m pytest -k-test_flake8 tests/test__environment.py
There is n
I had this running in background, first of all this confirmed that this builds
fine for Eoan but fails for Focal.
Therefore we know it is reproducible and dependent on the changes in Focal to
trigger.
** Changed in: asyncpg (Ubuntu)
Status: New => Confirmed
--
You received this bug noti
18 matches
Mail list logo
