Чт 23 апр 2020 @ 13:05 Jonas Smedegaard <jo...@jones.dk>: > Quoting Jonas Smedegaard (2020-04-23 12:56:23) >> Quoting Lev Lamberov (2020-04-23 12:15:12) >> > Чт 23 апр 2020 @ 11:58 Jonas Smedegaard <jo...@jones.dk>: >> > >> > > Quoting Lev Lamberov (2020-04-23 11:38:36) >> > >> > >> Чт 23 апр 2020 @ 10:59 Paul Gevers <elb...@debian.org>: >> > >> > >> > [Release team member hat on] >> > >> > >> > >> > On 21-04-2020 23:48, Debian FTP Masters wrote: >> > >> >> eye (20.0411.2226~ds-1) unstable; urgency=medium >> > >> >> . >> > >> >> [ upstream ] >> > >> >> * new release(s) >> > >> >> + FIXED: process_create/3: stderr was sent to stdout. >> > >> >> closes: Bug#958419, thanks to Paul Gevers >> > >> > >> > >> > It seems that this fix works with swi-prolog in unstable, but not >> > >> > with swi-prolog in testing. Which means that you're missing a >> > >> > versioned (test) dependency somewhere. Now *both* packages are not >> > >> > migrating. If this is *only* an autopkgtest issue, I'm willing to >> > >> > trigger the combination manually, but I prefer you fix the (test) >> > >> > dependencies. >> > >> >> > >> one of the reasons why swi-prolog does not migrate to testing is >> > >> binary upload, I will prepare source-only upload of the latest >> > >> upstream version in the next couple of days. >> > > >> > > That would be nice, but seems unrelated to the issue with eye. >> > > >> > > @Lev: Do you have an ida why eye fails like this: >> > > >> > > incompatible VM-signature (file: 0xde23899e; Prolog: 0x10c53d6a)] >> > > >> > > See bottom of >> > > https://ci.debian.net/data/autopkgtest/testing/amd64/e/eye/5106659/log.gz >> > >> > Hmmm... I'm not sure, but my guess is as follows. Since (1) parts of >> > tests are downloaded during testing, and (2) as I can see upstream >> > developers of eye recently changed tests to comply with swi-prolog >> > 8.1.28 (see, upstream commit >> > eb3f074a11c8be9d82950f7a98c5d1d12fcc0254), (3) testing currently >> > contains swi-prolog 8.0.3 and autopkgtests fail with it, and (4) eye >> > in unstable (with swi-prolog 8.1.28) passes autopkgtests, then I think >> > that to fix it we need newer swi-prolog in testing. >> >> Ohh, the test failure I reference was for _testing_ - I thought it was >> for _unstable_ and was puzzled why it also failed there. >> >> Yes, I agree that this looks like just an autopkgtest issue (but makes >> me wonder if eye should include Build-Using:). > > No wait: It causes "FATAL ERROR" of "incompatible VM-signature" when an > image shipped with eye was produced by a different version of swi-prolog > than is currently installed. That's a different issue which requires > eye to tighten its dependency on swi-prolog-nox.
Ohhh, I see. Let me upload (source-only) 8.1.29 to unstable. Will be OK for you? Regards, Lev
