Dear all On 20-06-18 22:21, Paul Gevers wrote: > With a recent upload of kombu the autopkgtest of celery version 4.1.0-4 > started to fail. See: > https://ci.debian.net/packages/c/celery/testing/amd64/ > and > https://qa.debian.org/excuses.php?package=kombu > > I looked at the test and it the autopkgtest of celery seems to use > modules from kombu that are no longer available. See the log copied below. > > Currently this regression is delaying the migration of kombu to > testing by 13 days. Could we please discuss together what the best way > forward is for this regression in testing?
I see that a new version of celery has been uploaded. Unfortunately, that still fails¹. As it seems the attempt is to have celery work with the newer version of kombu, I think the right course of action is that kombu now adds a "Breaks: celery (<< 4.2.1-1~)". If that happens, I'll help ci.d.n to test the right combination, because due to bug #896023 (autopkgtest) just adding the breaks will not automatically do the right thing. What do you think? Paul ¹ https://ci.debian.net/data/autopkgtest/testing/amd64/c/celery/491725/log.gz
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Python-modules-team mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
