Dirk - Ping on this?
If you do not have the time, let me know. I'll do a NMU for tiledb to revert to
prev version and also file an unblock request.
On 3/10/23 20:53, Nilesh Patra wrote:
Quoting Andreas Tille:
your recent upload of tiledb 2.15.0-1 into unstable is quite unfortunate
in freeze policy. You should have waited at least until 2.14.1-2 fixing
this bug to migrate to testing. You would need to ask release team for
migration of 2.15.0 which will probably be refused
The changes between 2.14 and 2.15 are non-trivial and are likely to be rejected
by
release team at the moment, considering there are no autopkgtests either.
even if you would be
able to fix the regression in autopkgtest[1].
This is because the version of tiledb-py is not compatible with tiledb 2.15.0.
Uploading
a new version of tiledb-py would fix this, but:
- It'd be useless unless tiledb 2.15.0 migrates.
- It seems to need pyarrow for tests, and other functionalities, which is
un-packaged.
So current situation is:
* tiledb 2.14.1-1 in testing (and next stable) is marked for auto-removal.
* consequently, tiledb-py is also marked for autoremoval.
* tiledb 2.15.0-1 can't migrate because of freeze policy.
What a freaking mess!
Dirk, we could have avoided all of it if you had quite literally ** waited **
for a few hours
to let tiledb migrate on the 8th of March. I'm sad to see such mess-ups
happening at this time as I
had put quite some efforts on tiledb-py myself too.
The solution right now is what Andreas said:
My recommendation would be to upload a version
2.15.0-2+really_2.14.1
Dirk, please fix this so tiledb can make a (valid) stable release.
[1]: https://tracker.debian.org/pkg/tiledb
