On Tue, 2022-10-11 at 09:57 +0200, Yadd wrote: > On 11/10/2022 09:27, Sebastian Ramacher wrote: > > On 2022-10-11 06:50:09 +0200, Yadd wrote: > > > node-jest is still blocked in unstable but I can't understand > > > why: > > > * tracker.d.o reports nothing > > > * Britney output is unintelligible > > > > > > trying: node-ts-jest node-jest > > > skipped: node-ts-jest node-jest (0, 56, 23) > > > got: 22+0: a-4:a-17:a-0:a-0:i-0:m-0:m-0:p-0:s-1 > > > * amd64: jest, node-jest-react, ts-jest > > > > Britney is trying to migrate node-js-jest and node-jest together > > (trying: ...), but it fails to do so since migrating those two > > source > > packages would cause new uninstallable packages in testing (amd64: > > ...) > > Thanks, but I still don't understand. node-jest-react depends on any > version of jest, has already migrate and all of those packages are > arch:all. I tried to install ts-jest 29 and jest 29 on a testing > schroot > with node-jest-react, no problem found...
I'm not sure how you managed that. A quick dose run using the current packages files shows that jest 29.1.2~ds1+~cs70.47.21-1 depends on node-cjs-module-lexer, which isn't in testing. Checking the changelog also shows: node-jest (29.1.1~ds1+~cs70.47.20-1) unstable; urgency=medium * Replace component by dependency: cjs-module-lexer (Closes: #1019355) Regards, Adam
