Paul Gevers <elbrus@debian.org> writes: > Source: compat-el > Version: 30.1.0.0+dfsg-1 > Severity: serious > User: debian-ci@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > Your package has an autopkgtest, great. However, it fails. Can you > please investigate the situation and fix it? I copied some of the output > at the bottom of this report. > > The release team has announced [1] that failing autopkgtest on amd64 and > arm64 are considered RC in testing. > > More information about this bug and the reason for filing it can be > found on > https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation > > Paul > > [1] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html > > https://ci.debian.net/packages/c/compat-el/testing/amd64/63554754/ > > 24s autopkgtest [20:50:45]: test dh-elpa-test-autopkgtest: > [----------------------- > 25s bash: line 1: dh_elpa_test: command not found > 25s autopkgtest [20:50:46]: test dh-elpa-test-autopkgtest: > -----------------------] It looks like this is due to the recent change in emacs that adds breaks/replaces/provides for built-in packages which includes compat. Looking at the "test dh-elpa-test-autopkgtest: preparing testbed" step, both dh-elpa and emacs were removed as a result, causing the dh_elpa_test command not found. This is working as intended. So this is how this works now: when compat-el upgrades to a version higher than the one provided by Emacs (e.g. 30.2.x.x), it can enter Forky. And if later a newer Emacs version provides that higher version of compat, compat-el should be kept out of Forky again. -- Regards, Xiyue Deng
Attachment:
signature.asc
Description: PGP signature